From owner-freebsd-current Sun Jan 3 00:33:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA28845 for freebsd-current-outgoing; Sun, 3 Jan 1999 00:33:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from k6n1.znh.org (dialup8.gaffaneys.com [208.155.161.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA28840 for ; Sun, 3 Jan 1999 00:33:42 -0800 (PST) (envelope-from zach@gaffaneys.com) Received: (from zach@localhost) by k6n1.znh.org (8.9.1/8.9.1) id IAA37818; Sun, 3 Jan 1999 08:34:11 GMT (envelope-from zach) Message-ID: <19990103023411.A37772@znh.org> Date: Sun, 3 Jan 1999 02:34:11 -0600 From: Zach Heilig To: Wiliam Woods , FBSD_CURRENT Subject: Re: 3.0 release tag for cvsup ??? References: <004b01be36b0$cc319ca0$f301040a@c063.beaverton.stream.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <004b01be36b0$cc319ca0$f301040a@c063.beaverton.stream.com>; from Wiliam Woods on Sat, Jan 02, 1999 at 04:34:11PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 02, 1999 at 04:34:11PM -0800, Wiliam Woods wrote: > OK, from what I understand, the correct upgrade path to go from 2.2.6 to > 3.0 -Current is: > 1) Go from 2.2.6 --> 2.2.8 > 2) Go from 2.2.8 --> 3.0 _Release > 3) Go from 3.0 -Release to 3.0 -Current > I already tried to go straight from 2.2.6 to 3.0 -Current and that was a bad > joke...so I figured that I would try this upgrade path. The reason I would > like to go current is for the SMP support. > Is this correct? If so then what is the correct tag to cvsup 3.0 -Release? I don't know about the previous stuff, but the tag you are looking for is: RELENG_3_0_0_RELEASE You can find a list of all [important] tags by looking at: ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-CVS/src/COPYRIGHT,v (for example, just about any file in that directory will have every important tag -- that is just one of the smaller files). -- Zach Heilig (zach@gaffaneys.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 3 00:53:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA00234 for freebsd-current-outgoing; Sun, 3 Jan 1999 00:53:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA00229 for ; Sun, 3 Jan 1999 00:53:16 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id HAA26076; Sun, 3 Jan 1999 07:44:42 +0100 From: Luigi Rizzo Message-Id: <199901030644.HAA26076@labinfo.iet.unipi.it> Subject: Re: SoundBlaster 128 To: dchapman@houabg.com (David W. Chapman Jr.) Date: Sun, 3 Jan 1999 07:44:41 +0100 (MET) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <368EB07D.7E0A2C8B@houabg.com> from "David W. Chapman Jr." at Jan 2, 99 05:48:58 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm trying to get my soundblaster 128 working with 3.0-current, would > anyone tell me if they have got it working? there "pcm" driver now in current should support it. luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 00:53:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA00486 for freebsd-current-outgoing; Sun, 3 Jan 1999 00:53:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA00481 for ; Sun, 3 Jan 1999 00:53:46 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca3-217.ix.netcom.com [209.109.233.217]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id AAA04822; Sun, 3 Jan 1999 00:53:18 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.8.8/8.6.9) id AAA19134; Sun, 3 Jan 1999 00:52:51 -0800 (PST) Date: Sun, 3 Jan 1999 00:52:51 -0800 (PST) Message-Id: <199901030852.AAA19134@silvia.hip.berkeley.edu> To: chris@netmonger.net CC: current@FreeBSD.ORG In-reply-to: <19990102143728.A23411@netmonger.net> (message from Christopher Masto on Sat, 2 Jan 1999 14:37:28 -0500) Subject: Re: wanton Atticizing is bad From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Christopher Masto * What I'm getting at is that if we want to stand a chance of being able * to increase FreeBSD's visibility, it has to be _useful_ to _more_ * people. It seems like some of these drivers are being removed simply * because nobody on the core team uses them. Hell, I don't use most of Whoa! Not so fast my friend. It was not the core consensus to remove them, and some of them have already been ressurected, with others pending discussion. We have every intent to keep drivers that people are using, please don't jump to conclusions just because a couple of core members went overboard with their cvs priviledges. ;) 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 3 01:11:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA01211 for freebsd-current-outgoing; Sun, 3 Jan 1999 01:11:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (sj-dsl-9-129-138.dspeed.net [209.249.129.138]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA01204; Sun, 3 Jan 1999 01:11:24 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id BAA59068; Sun, 3 Jan 1999 01:10:29 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199901030910.BAA59068@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: asami@FreeBSD.ORG (Satoshi Asami) cc: chris@netmonger.net, current@FreeBSD.ORG Subject: Re: wanton Atticizing is bad In-reply-to: Your message of "Sun, 03 Jan 1999 00:52:51 PST." <199901030852.AAA19134@silvia.hip.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 03 Jan 1999 01:10:29 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > * From: Christopher Masto > > * What I'm getting at is that if we want to stand a chance of being able > * to increase FreeBSD's visibility, it has to be _useful_ to _more_ > * people. It seems like some of these drivers are being removed simply > * because nobody on the core team uses them. Hell, I don't use most of > > Whoa! Not so fast my friend. It was not the core consensus to remove > them, and some of them have already been ressurected, with others > pending discussion. > > We have every intent to keep drivers that people are using, please > don't jump to conclusions just because a couple of core members went > overboard with their cvs priviledges. ;) > Actually, at least one of those core members went over board in the past with their commit priviliges. This is my *second* request for a form or procedure to deal with -core members when they step over their boundaries specially when the code in question is not theirs nor is their field of expertise. The result of my little fiasco with -core caused me my cvs commit priviliges and I voluntarily ceased all multimedia work for FreeBSD because I couldn't defend the multimedia's group code in the source tree against -core. Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 01:14:01 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA01524 for freebsd-current-outgoing; Sun, 3 Jan 1999 01:14:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA01459 for ; Sun, 3 Jan 1999 01:12:14 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca3-217.ix.netcom.com [209.109.233.217]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id BAA04842; Sun, 3 Jan 1999 01:08:36 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.8.8/8.6.9) id BAA19167; Sun, 3 Jan 1999 01:06:08 -0800 (PST) Date: Sun, 3 Jan 1999 01:06:08 -0800 (PST) Message-Id: <199901030906.BAA19167@silvia.hip.berkeley.edu> To: jkh@zippy.cdrom.com CC: jb@cimlogic.com.au, mike@smith.net.au, andreas@klemm.gtn.com, current@FreeBSD.ORG In-reply-to: <8020.915327044@zippy.cdrom.com> (jkh@zippy.cdrom.com) Subject: Re: make aout-to-elf failures (from 2.2.7-RELEASE to -current ELF) From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: "Jordan K. Hubbard" * I think you're reading too much into our decision to go ELF. That * does not preclude an interest in the aout-to-elf target working * properly. Absolutely. If anything, the switchover of the 3.0 branch to -stable status makes it even more imperative to have the 2.2 -> 3.0 source upgrade working, as we can expect many server systems (without easy console access) to upgrade then. Satoshi (I know, I jumped myself a while ago, and it worked flawlessly) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 01:35:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA02895 for freebsd-current-outgoing; Sun, 3 Jan 1999 01:35:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.gtn.com (mail.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA02820 for ; Sun, 3 Jan 1999 01:33:44 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by mail.gtn.com (8.8.6/8.8.6) with UUCP id KAA19975; Sun, 3 Jan 1999 10:30:04 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.1/8.9.1) id KAA26573; Sun, 3 Jan 1999 10:02:37 +0100 (CET) (envelope-from andreas) Message-ID: <19990103100236.B20942@klemm.gtn.com> Date: Sun, 3 Jan 1999 10:02:36 +0100 From: Andreas Klemm To: Peter Wemm , John Birrell Cc: Mike Smith , current@FreeBSD.ORG Subject: Re: make aout-to-elf failures (from 2.2.7-RELEASE to -current ELF) References: <199901022344.KAA08296@cimlogic.com.au> <199901030317.LAA06894@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199901030317.LAA06894@spinner.netplex.com.au>; from Peter Wemm on Sun, Jan 03, 1999 at 11:17:20AM +0800 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 03, 1999 at 11:17:20AM +0800, Peter Wemm wrote: > > But this isn't an excuse for aout-to-elf failing.. We need to fix it if > it's still broken (I think it's been fixed now). Getting more people on > board should help. Now I tried the following, seems to run better: I build a 2.2.8-STABLE system first and did a make -ki aout-to-elf |& tee make.log It's still running and seems to install the elf binaries ... stay tuned. If you like I can put the results on freefall .... -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 01:45:42 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA03854 for freebsd-current-outgoing; Sun, 3 Jan 1999 01:45:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.gtn.com (mail.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA03756 for ; Sun, 3 Jan 1999 01:44:18 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by mail.gtn.com (8.8.6/8.8.6) with UUCP id KAA19997; Sun, 3 Jan 1999 10:31:42 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.1/8.9.1) id KAA27185; Sun, 3 Jan 1999 10:22:39 +0100 (CET) (envelope-from andreas) Message-ID: <19990103102237.A27170@klemm.gtn.com> Date: Sun, 3 Jan 1999 10:22:37 +0100 From: Andreas Klemm To: Peter Wemm , John Birrell Cc: Mike Smith , current@FreeBSD.ORG Subject: Re: make aout-to-elf failures (from 2.2.7-RELEASE to -current ELF) References: <199901022344.KAA08296@cimlogic.com.au> <199901030317.LAA06894@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199901030317.LAA06894@spinner.netplex.com.au>; from Peter Wemm on Sun, Jan 03, 1999 at 11:17:20AM +0800 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmm, I wanted to make the transcript of make aout-to-elf available. Well, somehow the installation of the ELF kernel failed. Since I ran the upgrade process with "make -ki", the system automatically rebooted and now I have a non working system :-/ Well I suggest the last thing of a make aout-to-elf should be a message like: an now reboot your system after making sure, that the ELF kernel has been installed properly Or is that not possible anymore, since the ELF programs can't be executed ??? But how does "install" work until the last second ... *sigh* not an easy job these upgrades ;-) -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 02:31:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA06668 for freebsd-current-outgoing; Sun, 3 Jan 1999 02:31:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA06663 for ; Sun, 3 Jan 1999 02:31:53 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.52]) by smtp05.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA5209 for ; Sun, 3 Jan 1999 11:31:28 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sun, 03 Jan 1999 11:38:37 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: FreeBSD Current Subject: Bootblocks / Bootloader Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi guys, ok, on this ELF system: FreeBSD daemon.ninth-circle.org 3.0-CURRENT FreeBSD 3.0-CURRENT #1: Sat Jan 2 09:14:28 CET 1999 asmodai@daemon.ninth-circle.org:/usr/src/sys/compile/DAEMON i386 I installed the new bootblocks and bootloader and it works like a charm. However the directions that were given in a previous mail about the steps required are enough to get it working but lack in some things (which I unfortunately have no idea about how to fix, yet). 1) I have the /boot.config file but the loader complains about /boot/boot.config, so should boot.config not be in /boot? 2) after the bootloader continues to load I get a warning that my kernel's symbol table doesn't match. I didn't have this problem before the new blocks. 3) I also got a complaint from the loader about another missing config file which I can't remember the name from. Looking through boot(8) reveals /boot.config, so why does the loader complain about /boot/boot.config? Also, it's hard to review how the boot process went because nothing gets logged in /var/log/messages. Any hints, tips or other RTFM stuff greatly appreciated =) Oh btw, make world also installs bootstraps and such, does it leave the new bootblocks alone or do I have to add a flag to my make worlds ? regards, --- Jeroen Ruigrok van der Werven Life is the only Pain asmodai(at)wxs.nl we endeavour... Network/Security Specialist BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 02:40:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA07467 for freebsd-current-outgoing; Sun, 3 Jan 1999 02:40:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles333.castles.com [208.214.167.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA07456 for ; Sun, 3 Jan 1999 02:40:17 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id CAA04475; Sun, 3 Jan 1999 02:37:10 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901031037.CAA04475@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Jeroen Ruigrok/Asmodai cc: FreeBSD Current Subject: Re: Bootblocks / Bootloader In-reply-to: Your message of "Sun, 03 Jan 1999 11:38:37 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 03 Jan 1999 02:37:09 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please wrap your messages to sensible margins. > ok, on this ELF system: > FreeBSD daemon.ninth-circle.org 3.0-CURRENT > FreeBSD 3.0-CURRENT #1: Sat Jan 2 09:14:28 CET 1999 > asmodai@daemon.ninth-circle.org:/usr/src/sys/compile/DAEMON i386 > I installed the new bootblocks and bootloader and it works like a > charm. However the directions that were given in a previous mail about > the steps required are enough to get it working but lack in some things > (which I unfortunately have no idea about how to fix, yet). > 1) I have the /boot.config file but the loader complains about /boot/ > boot.config, so should boot.config not be in /boot? It doesn't, as I believe I've already mentioned to you in a previous message. The loader reads /boot/boot.conf, which is a totally different animal. /boot.config is only required if you have not upgraded the bootblocks; it should *not* be generally used. > 2) after the bootloader continues to load I get a warning that my > kernel's symbol table doesn't match. I didn't have this problem before > the new blocks. Please quote the exact message that you get. This report is useless. > 3) I also got a complaint from the loader about another missing config > file which I can't remember the name from. Please quote the exact message that you get. This report is useless. > Oh btw, make world also installs bootstraps and such, does it leave the new > bootblocks alone or do I have to add a flag to my make worlds ? The world build installs a new loader, but it does not replace the bootblocks. You have to do that by hand (disklabel -B). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 02:51:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA08196 for freebsd-current-outgoing; Sun, 3 Jan 1999 02:51:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Wit401305.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA08188 for ; Sun, 3 Jan 1999 02:51:28 -0800 (PST) (envelope-from daeron@Wit401305.student.utwente.nl) Received: from localhost (daeron@localhost) by Wit401305.student.utwente.nl (8.9.1/8.9.1) with ESMTP id LAA18683; Sun, 3 Jan 1999 11:50:40 +0100 (CET) (envelope-from daeron@Wit401305.student.utwente.nl) Date: Sun, 3 Jan 1999 11:50:36 +0100 (CET) From: Pascal Hofstee To: Mike Smith cc: Jeroen Ruigrok/Asmodai , FreeBSD Current Subject: How to install the new bootblocks In-Reply-To: <199901031037.CAA04475@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been running a nice ELF kernel for a hwile now on 3.0-CURRENT and with this continuous talk about the new bootblocks and all I would like to know what I would need to do to install those. ------------------ Pascal Hofstee daeron@shadowmere.student.utwente.nl "Time is a drug. Too much of it kills you." -- Small Gods, Terry Pratchet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 03:06:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA10280 for freebsd-current-outgoing; Sun, 3 Jan 1999 03:06:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from baerenklau.de.freebsd.org (baerenklau.de.freebsd.org [195.185.195.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA10272 for ; Sun, 3 Jan 1999 03:06:23 -0800 (PST) (envelope-from w@panke.de.freebsd.org) Received: (from uucp@localhost) by baerenklau.de.freebsd.org (8.8.8/8.8.8) with UUCP id MAA09551; Sun, 3 Jan 1999 12:05:45 +0100 (CET) (envelope-from w@panke.de.freebsd.org) Received: (from w@localhost) by campa.panke.de.freebsd.org (8.8.8/8.8.8) id LAA28941; Sun, 3 Jan 1999 11:36:56 +0100 (MET) (envelope-from w) Message-ID: <19990103113655.A28932@panke.de.freebsd.org> Date: Sun, 3 Jan 1999 11:36:55 +0100 From: Wolfram Schneider To: David Bushong , freebsd-current@FreeBSD.ORG Subject: Re: more recent archive? References: <199901030150.RAA19671@soda.CSUA.Berkeley.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199901030150.RAA19671@soda.CSUA.Berkeley.EDU>; from David Bushong on Sat, Jan 02, 1999 at 05:50:17PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-01-02 17:50:17 -0800, David Bushong wrote: > Is there a more recent archive somewhere of freebsd-current? The searchable > archive on www.freebsd.org doesn't seem to have anything more recent than > 12/16/1998, and I'm trying to reread all of the stuff about elf kernels > and updating your boot loader.. http://www.freebsd.org/mail/ -- Wolfram Schneider http://freebsd.org/~w/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 03:13:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA11171 for freebsd-current-outgoing; Sun, 3 Jan 1999 03:13:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA11146 for ; Sun, 3 Jan 1999 03:13:48 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.52]) by smtp02.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA6974; Sun, 3 Jan 1999 12:13:23 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199901031037.CAA04475@dingo.cdrom.com> Date: Sun, 03 Jan 1999 12:20:31 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Mike Smith Subject: Re: Bootblocks / Bootloader Cc: FreeBSD Current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-Jan-99 Mike Smith wrote: >> I installed the new bootblocks and bootloader and it works like a >> charm. However the directions that were given in a previous mail about >> the steps required are enough to get it working but lack in some things >> (which I unfortunately have no idea about how to fix, yet). > >> 1) I have the /boot.config file but the loader complains about /boot/ >> boot.config, so should boot.config not be in /boot? > > It doesn't, as I believe I've already mentioned to you in a previous > message. The loader reads /boot/boot.conf, which is a totally different > animal. /boot.config is only required if you have not upgraded the > bootblocks; it should *not* be generally used. Wasn't me who ye talked to =) OK, so I can just safely remove boot.config soon, but where can I get info about what to put in boot.conf? I have found no manual pages of some sort yet. >> 2) after the bootloader continues to load I get a warning that my >> kernel's symbol table doesn't match. I didn't have this problem before >> the new blocks. > > Please quote the exact message that you get. This report is useless. I would, but I have found no way in which the boot stage gets logged in some sort, but I will see what I can write down. >> 3) I also got a complaint from the loader about another missing config >> file which I can't remember the name from. > > Please quote the exact message that you get. This report is useless. Yeah I will, as soon as I reboot here... Surely I am missing some logfile hidden somewhere and any pointers are welcomed. /var/log/messages is not the one, and I haven't been able to find another one. Does it get logged in the first place? --- Jeroen Ruigrok van der Werven Life is the only Pain asmodai(at)wxs.nl we endeavour... Network/Security Specialist BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 03:30:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA12811 for freebsd-current-outgoing; Sun, 3 Jan 1999 03:30:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA12802 for ; Sun, 3 Jan 1999 03:30:16 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.48]) by smtp03.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA4645; Sun, 3 Jan 1999 12:29:41 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199901031037.CAA04475@dingo.cdrom.com> Date: Sun, 03 Jan 1999 12:36:45 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Mike Smith Subject: Re: Bootblocks / Bootloader Cc: FreeBSD Current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-Jan-99 Mike Smith wrote: >> I installed the new bootblocks and bootloader and it works like a >> charm. However the directions that were given in a previous mail about >> the steps required are enough to get it working but lack in some things >> (which I unfortunately have no idea about how to fix, yet). > >> 1) I have the /boot.config file but the loader complains about /boot/ >> boot.config, so should boot.config not be in /boot? > > It doesn't, as I believe I've already mentioned to you in a previous > message. The loader reads /boot/boot.conf, which is a totally different > animal. /boot.config is only required if you have not upgraded the > bootblocks; it should *not* be generally used. True, sorry, I mixed up boot.conf and loader.config, see below. >> 2) after the bootloader continues to load I get a warning that my >> kernel's symbol table doesn't match. I didn't have this problem before >> the new blocks. > > Please quote the exact message that you get. This report is useless. See below >> 3) I also got a complaint from the loader about another missing config >> file which I can't remember the name from. > > Please quote the exact message that you get. This report is useless. OK, just rebooted and wrote down some things: boot: Booting 0:da(0,a)/boot/loader @ 0x100000 text=0x1000 data=0x1c000 bss=0x00 symbols=[0x0+0x4+0x0+0x4+0xff8c] Can't find file /boot/loader.config total=0x12cf94 entry point=0x100000 BTX loader ... [looks good] bootstrap loader revision 0.2 Can't open /boot/boot.conf: no such file or directory ... [booting kernel] [kernel symbol table not valid] OK, so the reason for the files missing is logical since they don't exist. Btw, when I go to the CLI of the booter the ? works to get the commands and the commands itself work as well, great job. Is the symbol table not valid related to the posts I have seen about a.out kernels and ELF kernels? Any hints regarding loader.config and boot.conf are I think the last hurdles I face with the loader... [ Wishful thinking mayhaps ;) ] --- Jeroen Ruigrok van der Werven Life is the only Pain asmodai(at)wxs.nl we endeavour... Network/Security Specialist BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 03:32:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA13389 for freebsd-current-outgoing; Sun, 3 Jan 1999 03:32:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA13362 for ; Sun, 3 Jan 1999 03:32:23 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.48]) by smtp03.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA47D8; Sun, 3 Jan 1999 12:31:54 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sun, 03 Jan 1999 12:39:03 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Pascal Hofstee Subject: RE: How to install the new bootblocks Cc: FreeBSD Current , Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-Jan-99 Pascal Hofstee wrote: > I have been running a nice ELF kernel for a hwile now on > 3.0-CURRENT and with this continuous talk about the new bootblocks and all > I would like to know what I would need to do to install those. Mike and other might want to rectify this, but this worked for me: disklabel -B the boot.config file step is a unnecessary one as Mike was kind enough to explain to me. But there are some extra steps needed, such as the files I am referring to in my posts. --- Jeroen Ruigrok van der Werven Life is the only Pain asmodai(at)wxs.nl we endeavour... Network/Security Specialist BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 04:08:43 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA19502 for freebsd-current-outgoing; Sun, 3 Jan 1999 04:08:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-45-dbn.dial-up.net [196.34.155.109]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA19491 for ; Sun, 3 Jan 1999 04:08:38 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id NAA02431; Sun, 3 Jan 1999 13:20:30 +0200 (SAT) From: Robert Nordier Message-Id: <199901031120.NAA02431@ceia.nordier.com> Subject: Re: make release (almost) disklabel failure In-Reply-To: <8119.915328145@zippy.cdrom.com> from "Jordan K. Hubbard" at "Jan 2, 99 05:49:05 pm" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Sun, 3 Jan 1999 13:20:28 +0200 (SAT) Cc: jwd@unx.sas.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan K. Hubbard wrote: > > ps: Do we have any official doc on boot1 & boot2 yet? > > Not to my knowledge. :) The boot blocks are currently documented in src/sbin/reboot/boot_${ARCH}.8 though only boot_i386.8 (relating to the old, aout-only boot blocks) exists. This man page probably needs to be moved, by repository copy, to /sys/i386/boot/biosboot and a new man page created in /sys/boot/i386/boot2 However, while the old boot blocks continue to be part of a make world, "man boot" is still going to bring up the old, aout-only information because the old stuff is installed later. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 04:15:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA20110 for freebsd-current-outgoing; Sun, 3 Jan 1999 04:15:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-45-dbn.dial-up.net [196.34.155.109]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA20104 for ; Sun, 3 Jan 1999 04:15:09 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id OAA02670; Sun, 3 Jan 1999 14:13:12 +0200 (SAT) From: Robert Nordier Message-Id: <199901031213.OAA02670@ceia.nordier.com> Subject: Re: Bootblocks / Bootloader In-Reply-To: from Jeroen Ruigrok/Asmodai at "Jan 3, 99 12:36:45 pm" To: asmodai@wxs.nl (Jeroen Ruigrok/Asmodai) Date: Sun, 3 Jan 1999 14:13:10 +0200 (SAT) Cc: mike@smith.net.au, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeroen Ruigrok/Asmodai wrote: > On 03-Jan-99 Mike Smith wrote: > > >> I installed the new bootblocks and bootloader and it works like a > >> charm. However the directions that were given in a previous mail about > >> the steps required are enough to get it working but lack in some things > >> (which I unfortunately have no idea about how to fix, yet). > > > >> 1) I have the /boot.config file but the loader complains about /boot/ > >> boot.config, so should boot.config not be in /boot? > > > > It doesn't, as I believe I've already mentioned to you in a previous > > message. The loader reads /boot/boot.conf, which is a totally different > > animal. /boot.config is only required if you have not upgraded the > > bootblocks; it should *not* be generally used. However, if you have only a serial console attached, you may want to have serial options in /boot.config anyway (particularly for remote administration). > >> 3) I also got a complaint from the loader about another missing config > >> file which I can't remember the name from. > > > > Please quote the exact message that you get. This report is useless. > > OK, just rebooted and wrote down some things: > > > boot: > > Booting 0:da(0,a)/boot/loader @ 0x100000 > text=0x1000 data=0x1c000 bss=0x00 symbols=[0x0+0x4+0x0+0x4+0xff8c] > > Can't find file /boot/loader.config > total=0x12cf94 entry point=0x100000 > > BTX loader > > ... [looks good] > bootstrap loader revision 0.2 These messages indicate that you *don't* have the new boot blocks installed, but the old ones. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 05:07:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA23586 for freebsd-current-outgoing; Sun, 3 Jan 1999 05:07:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA23581 for ; Sun, 3 Jan 1999 05:07:53 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id IAA02105; Sun, 3 Jan 1999 08:07:01 -0500 (EST) Date: Sun, 3 Jan 1999 08:07:01 -0500 (EST) From: Daniel Eischen Message-Id: <199901031307.IAA02105@pcnet1.pcnet.com> To: asmodai@wxs.nl, mike@smith.net.au Subject: Re: Bootblocks / Bootloader Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Oh btw, make world also installs bootstraps and such, does it leave the new > > bootblocks alone or do I have to add a flag to my make worlds ? > > The world build installs a new loader, but it does not replace the > bootblocks. You have to do that by hand (disklabel -B). I think R. Nordier mentioned in another Email that you don't have the new boot blocks installed. I thought I had them installed also, but "disklabel -B {da0|wd0}" alone won't do it, as it will install the default boot blocks from /usr/mdec (I assume that at some point disklabel will be changed?). Here's what worked for me: disklabel -B -b /boot/boot1 -s /boot/boot2 /dev/da0s3c where FreeBSD exists on my third partition. I'm not sure if disklabel is smart enough to work with "da0" as the disk in this case. BTW, a make aout-to-elf-install works with CVS checked out from date "December 18, 1998". Dan Eischen eischen@pcnet.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 3 05:14:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA24163 for freebsd-current-outgoing; Sun, 3 Jan 1999 05:14:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA24151 for ; Sun, 3 Jan 1999 05:14:43 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id PAA00370; Sun, 3 Jan 1999 15:14:10 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id PAA14432; Sun, 3 Jan 1999 15:14:11 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199901031314.PAA14432@greenpeace.grondar.za> To: Daniel Eischen cc: current@FreeBSD.ORG Subject: Re: Bootblocks / Bootloader In-Reply-To: Your message of " Sun, 03 Jan 1999 08:07:01 EST." <199901031307.IAA02105@pcnet1.pcnet.com> References: <199901031307.IAA02105@pcnet1.pcnet.com> Date: Sun, 03 Jan 1999 15:14:09 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel Eischen wrote: > also, but "disklabel -B {da0|wd0}" alone won't do it, as it will > install the default boot blocks from /usr/mdec (I assume that at > some point disklabel will be changed?). *BZZT!* Check the source! :-) 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 3 05:39:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA26344 for freebsd-current-outgoing; Sun, 3 Jan 1999 05:39:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ihgw2.lucent.com (ihgw2.lucent.com [207.19.48.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA26334 for ; Sun, 3 Jan 1999 05:39:27 -0800 (PST) (envelope-from dmobrien@ihgw2.lucent.com) Cc: Eric Chet Received: from llama.bazzle.com by ihig2.firewall.lucent.com (SMI-8.6/EMS-L sol2) id HAA18681; Sun, 3 Jan 1999 07:26:49 -0600 Received: from localhost (dob@localhost) by llama.bazzle.com (8.9.1/8.6.12) with SMTP id IAA23813; Sun, 3 Jan 1999 08:38:54 -0500 (EST) X-Authentication-Warning: llama.bazzle.com: dob owned process doing -bs Date: Sun, 3 Jan 1999 08:38:53 -0500 (EST) From: "Dan O'Brien" X-Sender: dmobrien@localhost To: current@FreeBSD.ORG Original-cc: Eric Chet Subject: Me too: aout-to-elf build failure, 31 December Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Count me in the number of folks blewing up in aout-to-elf (on the elf side) for 12/31 cvsup. cc -O -malign-loops=2 -malign-jumps=2 -malign-functions=2 -pipe -I/usr/src/usr.sbin/i4b/isdnd/../isdnmonitor -I/usr/src/usr.sbin/i4b/isdnd/../isdntel -I/usr/obj/elf/usr/src/usr.sbin/i4b/isdnd -DDEBUG -DUSE_RTPRIO -DUSE_CURSES -DI4B_EXTERNAL_MONITOR -I/usr/obj/elf/usr/src/tmp/usr/include -o isdnd rc_parse.o rc_scan.o main.o rc_config.o log.o curses.o process.o rates.o msghdl.o fsm.o support.o timer.o exec.o dial.o monitor.o pcause.o controller.o alias.o -lcurses /usr/obj/aout/usr/src/tmp/usr/libexec/elf/ld: warning: libtermcap.so.2, needed by /usr/obj/elf/usr/src/tmp/usr/lib/libcurses.so, not found (try using --rpath) /usr/obj/elf/usr/src/tmp/usr/lib/libcurses.so: undefined reference to `tgetnum' /usr/obj/elf/usr/src/tmp/usr/lib/libcurses.so: undefined reference to `tgoto' /usr/obj/elf/usr/src/tmp/usr/lib/libcurses.so: undefined reference to `tgetflag' /usr/obj/elf/usr/src/tmp/usr/lib/libcurses.so: undefined reference to `tputs' /usr/obj/elf/usr/src/tmp/usr/lib/libcurses.so: undefined reference to `tgetent' /usr/obj/elf/usr/src/tmp/usr/lib/libcurses.so: undefined reference to `tgetstr' *** Error code 1 My aout system is current as of 12/31. Trying to go to elf... Cheers, Dan O'Brien Work: 614-860-2392 Page: 614-520-5001 Home: 740-927-2178 Home2: 740-927-2955 ---------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 05:42:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA26846 for freebsd-current-outgoing; Sun, 3 Jan 1999 05:42:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wraith.uswest.net (adsla195.dnvr.uswest.net [209.180.248.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA26840 for ; Sun, 3 Jan 1999 05:42:55 -0800 (PST) (envelope-from tod.morrison@usa.net) Received: from usa.net (localhost.dnvr.uswest.net [127.0.0.1]) by wraith.uswest.net (8.9.1/8.9.1) with ESMTP id GAA08279 for ; Sun, 3 Jan 1999 06:43:19 -0700 (MST) (envelope-from tod.morrison@usa.net) Message-ID: <368F73F7.B2972F6D@usa.net> Date: Sun, 03 Jan 1999 06:43:19 -0700 From: Tod Morrison X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 CC: freebsd-current@FreeBSD.ORG Subject: Re: SoundBlaster 128 References: <199901030644.HAA26076@labinfo.iet.unipi.it> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The pcm driver works nicely, except for that the module doesn't register if there are not any isa devices (? - I don't really understand the problem, I just found a patch in the mailing list archives to fix it ). Actually, I wound up applying the changes by hand since the driver has evolved since the original posting of the patch. Tring to get my PCI128 to work nearly drove me insane till I found that post. "es1" and "pcm1" were showing up at boot, but /dev/sndstat etc... kept returning "device not configured". Tod Morrison Luigi Rizzo wrote: > > > I'm trying to get my soundblaster 128 working with 3.0-current, would > > anyone tell me if they have got it working? > > there "pcm" driver now in current should support it. > > luigi > > 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 3 06:09:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA28676 for freebsd-current-outgoing; Sun, 3 Jan 1999 06:09:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-41-dbn.dial-up.net [196.34.155.41]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA28671 for ; Sun, 3 Jan 1999 06:09:28 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id QAA03360; Sun, 3 Jan 1999 16:07:32 +0200 (SAT) From: Robert Nordier Message-Id: <199901031407.QAA03360@ceia.nordier.com> Subject: Re: make aout-to-elf failures (from 2.2.7-RELEASE to -current ELF) In-Reply-To: <199901030408.UAA44371@ix.netcom.com> from Thomas Dean at "Jan 2, 99 08:08:35 pm" To: tomdean@ix.netcom.com (Thomas Dean) Date: Sun, 3 Jan 1999 16:07:29 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas Dean wrote: > I am in the midst of updating the bootblocks. I have two SCSI disks, > da0 is WINNT and da1 is -current. I am currently using OS-BS. I am > reading in the archives, attempting to upgrade. So far, I have > backed-up and made new boot and fixit floppies. > > I found in the archives: > > cp /usr/mdec/boot? /boot > echo '/boot/loader' > /boot.config > disklabel -B bootdevices > > Also a reference to make in /sys/boot. > > Will 'make && make install' in /sys/boot do all that is needed? > > After I figure out the bootblocks, I will try aout-to-elf-build, then > aout-to-elf-install, followed with building an elf kernel. > > Any pointers to doc's on upgrade the bootblocks? All that's really needed is: # Ensure that /boot exists mkdir -p /boot # Install latest bootblocks in /boot cd /sys/boot make all install # Upgrade bootblocks for each target slice disklabel -B -b /boot/boot1 -s /boot/boot2 $SLICE NOTES: o You probably want to delete /boot.config after upgrading, though having one or more of the serial options -h -D -P in /boot.config may still be useful. o For recent versions of disklabel(8), the -b and -s options can be omitted (RTFM/UTSL to check defaults). o If you have only one FreeBSD slice per drive, you can specify the drive (eg. da1) rather than the slice (eg. da1s1) in the disklabel command. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 06:15:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA29261 for freebsd-current-outgoing; Sun, 3 Jan 1999 06:15:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA29256 for ; Sun, 3 Jan 1999 06:15:46 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id NAA26575; Sun, 3 Jan 1999 13:07:16 +0100 From: Luigi Rizzo Message-Id: <199901031207.NAA26575@labinfo.iet.unipi.it> Subject: Re: SoundBlaster 128 To: tod.morrison@usa.net (Tod Morrison) Date: Sun, 3 Jan 1999 13:07:16 +0100 (MET) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <368F73F7.B2972F6D@usa.net> from "Tod Morrison" at Jan 3, 99 06:43:00 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The pcm driver works nicely, except for that the module doesn't register > if there are not any isa devices (? - I don't really understand the > problem, I just found a patch in the mailing list archives to fix it ). can you send me the patch (original one or your modified one). Unfortunately my test machine has an onboard ISA audio card so i cannot easily reproduce the problem. thanks luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 06:20:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA29755 for freebsd-current-outgoing; Sun, 3 Jan 1999 06:20:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ras-s84.nyc.transwire.net (ras-s84.nyc.transwire.net [199.105.68.85]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA29742 for ; Sun, 3 Jan 1999 06:20:01 -0800 (PST) (envelope-from oghost@ras-s84.nyc.transwire.net) Received: (qmail 863 invoked by uid 13909); 31 Dec 1998 23:46:06 -0000 From: "Ben Grubin" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <13964.3262.90717.900266@ras-s84.nyc.transwire.net> Date: Thu, 31 Dec 1998 18:46:06 -0500 (EST) To: Scott Barron Cc: Richard Seaman , current@FreeBSD.ORG, "Kevin G. Eliuk" Subject: Re: Trouble with Staroffice5.0 In-Reply-To: References: <19981231165447.A2862@tar.com> X-Mailer: VM 6.62 under Emacs 20.3.1 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK. THIS IS A PUBLIC SERVICE ANNOUNCEMENT. EVERYBODY GO GET DRUNK IMMEDIATELY. THANK YOU FOR YOUR PATIENCE. HAPPY NEW YEARS. Scott Barron writes: > > On 31-Dec-98 Richard Seaman wrote: > > On Thu, Dec 31, 1998 at 10:43:58AM -0800, Kevin G. Eliuk wrote: > > > > [SNIP] > > >> Any ideas on where I can go from here. > > > > Only one. I should note that I'm not a StarOffice guru by any means. > > I've only tried it out as a test case of the linux threads emulation > > code. > > > > The idea is that StarOffice is a resource hog, and you don't have much > > RAM. I'm not smart enought to read the output you sent to find how > > much swap space you have. Is is possible you're just running out of > > resources? When I run soffice, just the initial program, without > > actually doing anything, shows 24MB of resident memory and 32MB of > > total vm memory under "top". And, this is with my vm stack patches > > applied. I'd guess the vm memory would jump another 10MB without > > them. > > > > You presumably have an X server running, plus whatever else, so is > > it possible you just need more RAM? I've only tried it on a > > machine with 256MB of RAM and 512MB of swap. :) > > > > -- > > I would like to add a note here. I had the same problem described > while running Linux. My box has 96M RAM and about 130M of swap space. Star > Office would freeze in about the same place, but I was not so lucky to have > regained control of my keyboard and hence had to do a cold boot. After doing > it twice I decided to heck with it and downloaded word perfect 8. I have not > tried anything on FreeBSD yet. Has anyone attempted running WP8 on FreeBSD? > It was a lot less resource hungry than SO4 on Linux. > > -Scott > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 06:21:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA00234 for freebsd-current-outgoing; Sun, 3 Jan 1999 06:21:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA00229 for ; Sun, 3 Jan 1999 06:21:11 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id PAA08742 for ; Sun, 3 Jan 1999 15:21:53 +0100 (MET) Date: Sun, 3 Jan 1999 15:20:41 +0100 (MET) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: FreeBSD current mailing list Subject: subjects in posted changes in a PR Message-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 would be useful to add the synopsis to the Subject of the posted message. The message below show that the subject only contains the PR number and not the synopsis. Makes discussions easier if you do not have to look into every message to see whether the message is of interest. Subject: Re: misc/5082 should be Subject: Re: misc/5082 - Permit upgrade of multi-disk system,... IMHO. Don't know where to post this change request, as I do not know what software produces this message. Nick -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy ---------- Forwarded message ---------- Date: Tue, 29 Dec 1998 20:04:16 -0800 From: Mark Newton To: newton@atdot.dotat.org, newton@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG Subject: Re: misc/5082 Synopsis: Permit upgrade of multi-disk system, or document workaround State-Changed-From-To: open-closed State-Changed-By: newton State-Changed-When: Tue Dec 29 20:03:23 PST 1998 State-Changed-Why: Fixed sometime before may '98 when sysinstall's label editor started to provide info about all attached disks when doing an upgrade To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" 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 3 07:13:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA03042 for freebsd-current-outgoing; Sun, 3 Jan 1999 07:13:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA03035 for ; Sun, 3 Jan 1999 07:13:42 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id KAA23930 for ; Sun, 3 Jan 1999 10:13:17 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA20571; Sun, 3 Jan 1999 10:13:17 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id KAA12555 for freebsd-current@freebsd.org; Sun, 3 Jan 1999 10:13:06 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199901031513.KAA12555@bb01f39.unx.sas.com> Subject: make release (almost) No space left on device To: freebsd-current@FreeBSD.ORG Date: Sun, 3 Jan 1999 10:13:06 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Well, it seems over the last 24 hours we've grown the boot floppy just a "little" too much... sh -e /usr/src/release/scripts/doFS.sh /R/stage /mnt 1440 /R/stage/boot.std 80000 fd1440 disklabel: ioctl DIOCWLABEL: Operation not supported by device /dev/rvn0c: 2880 sectors in 80 cylinders of 2 tracks, 18 sectors 1.4MB in 5 cyl groups (16 c/g, 0.28MB/g, 32 i/g) super-block backups (for fsck -b #) at: 32, 632, 1184, 1784, 2336, cpio: write error: No space left on device *** Error code 1 Maybe we can move to having a network installation floppy and a disk media installation floppy... I personally do not want to see a multidisk boot process. I've used it on other systems, and it really hurts. Comments, Critiques, and other ideas are always welcome. Thanks! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 08:05:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA07005 for freebsd-current-outgoing; Sun, 3 Jan 1999 08:05:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA07000 for ; Sun, 3 Jan 1999 08:05:26 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.156]) by smtp02.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA3A70; Sun, 3 Jan 1999 17:04:59 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199901031213.OAA02670@ceia.nordier.com> Date: Sun, 03 Jan 1999 17:12:08 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Robert Nordier Subject: Re: Bootblocks / Bootloader Cc: current@FreeBSD.ORG, mike@smith.net.au Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-Jan-99 Robert Nordier wrote: > Jeroen Ruigrok/Asmodai wrote: >> On 03-Jan-99 Mike Smith wrote: >> > Please quote the exact message that you get. This report is useless. >> >> OK, just rebooted and wrote down some things: >> >> >> boot: >> >> Booting 0:da(0,a)/boot/loader @ 0x100000 >> text=0x1000 data=0x1c000 bss=0x00 symbols=[0x0+0x4+0x0+0x4+0xff8c] >> >> Can't find file /boot/loader.config >> total=0x12cf94 entry point=0x100000 >> >> BTX loader >> >> ... [looks good] >> bootstrap loader revision 0.2 > > These messages indicate that you *don't* have the new boot blocks > installed, but the old ones. Now I don't know anymore... I do however have a totally different boot process than I had before... So now I am lost... I was about to write a short document about it, but I guess that will now be incorrect ;) Any hints/tips? --- Jeroen Ruigrok van der Werven A veil of smoke is what I am, asmodai(at)wxs.nl I wait and I wait... Network/Security Specialist BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 08:13:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA07919 for freebsd-current-outgoing; Sun, 3 Jan 1999 08:13:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lint.cisco.com (lint.cisco.com [171.68.224.209]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA07908; Sun, 3 Jan 1999 08:13:26 -0800 (PST) (envelope-from rsargent@cisco.com) Received: (rsargent@localhost) by lint.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) id LAA02711; Sun, 3 Jan 1999 11:13:02 -0500 (EST) From: Robert Sargent Message-Id: <199901031613.LAA02711@lint.cisco.com> Subject: 3.0-19981226-SNAP/src/ssys.ac is corrupt To: freebsd-current@FreeBSD.ORG Date: Sun, 3 Jan 1999 11:13:02 -0500 (EST) Cc: freebsd-admin@FreeBSD.ORG X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I am trying to download pub/FreeBSD/3.0-19981226-SNAP/src/ssys.ac (from current.freebsd.org) and it gets about 75% done and stalls every time (tried 6 or 7 times): ftp> get ssys.ac local: ssys.ac remote: ssys.ac 227 Entering Passive Mode (209,180,6,226,216,73) 150 Opening BINARY mode data connection for 'ssys.ac' (240640 bytes). 69% |********************************** | 163 KB - stalled - Can someone fix this? and perhaps guide me as to where there might be a mirror that is not corrupt? (I hope the CD wasn't cut from this src). Thanks- Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 08:31:02 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA09471 for freebsd-current-outgoing; Sun, 3 Jan 1999 08:31:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lint.cisco.com (lint.cisco.com [171.68.224.209]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA09455; Sun, 3 Jan 1999 08:30:37 -0800 (PST) (envelope-from rsargent@knox6195.CISCO.COM) Received: from knox6195.CISCO.COM (mail@knox6195.cisco.com [161.44.216.195]) by lint.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id IAA05259; Sun, 3 Jan 1999 08:30:12 -0800 (PST) Message-ID: <19990103113008.F21893@Sgt-Sun.Cisco.COM> Date: Sun, 3 Jan 1999 11:30:08 -0500 From: Robert Sargent To: Robert Sargent , freebsd-current@FreeBSD.ORG Cc: freebsd-admin@FreeBSD.ORG Subject: Re: 3.0-19981226-SNAP/src/ssys.ac is corrupt Reply-To: Robert Sargent References: <199901031613.LAA02711@lint.cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199901031613.LAA02711@lint.cisco.com>; from Robert Sargent on Sun, Jan 03, 1999 at 11:13:02AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I found a mirror (ftp2 is hosed also) so I got the file, but you might want to repair the copy on current.freebsd.org. Thanks- Rob On Sun, Jan 03, 1999 at 11:13:02AM -0500, Robert Sargent wrote: > Hi, > > I am trying to download pub/FreeBSD/3.0-19981226-SNAP/src/ssys.ac (from > current.freebsd.org) and it gets about 75% done and stalls every time > (tried 6 or 7 times): > > ftp> get ssys.ac > local: ssys.ac remote: ssys.ac > 227 Entering Passive Mode (209,180,6,226,216,73) > 150 Opening BINARY mode data connection for 'ssys.ac' (240640 bytes). > 69% |********************************** | 163 KB - stalled - > > Can someone fix this? and perhaps guide me as to where there might be a > mirror that is not corrupt? (I hope the CD wasn't cut from this src). > > Thanks- > Rob > > 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 3 08:36:57 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA09954 for freebsd-current-outgoing; Sun, 3 Jan 1999 08:36:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA09949 for ; Sun, 3 Jan 1999 08:36:53 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id RAA25587 for current@FreeBSD.ORG; Sun, 3 Jan 1999 17:36:27 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 0DE011509; Sun, 3 Jan 1999 13:48:44 +0100 (CET) Date: Sun, 3 Jan 1999 13:48:44 +0100 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: make aout-to-elf failures (from 2.2.7-RELEASE to -current ELF) Message-ID: <19990103134844.A2409@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.ORG References: <199901022344.KAA08296@cimlogic.com.au> <199901030317.LAA06894@spinner.netplex.com.au> <19990103102237.A27170@klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <19990103102237.A27170@klemm.gtn.com>; from Andreas Klemm on Sun, Jan 03, 1999 at 10:22:37AM +0100 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4931 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Andreas Klemm: > Well I suggest the last thing of a make aout-to-elf should be > a message like: > an now reboot your system after making sure, that > the ELF kernel has been installed properly "make aout-to-elf-build" is your friend :-) -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #67: Tue Dec 29 20:24:02 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 08:44:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11304 for freebsd-current-outgoing; Sun, 3 Jan 1999 08:44:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from galaxy.support.stream.com (galaxy.support.stream.com [208.13.180.22]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA11286; Sun, 3 Jan 1999 08:44:51 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from c063.beaverton.stream.com ([208.13.191.137]) by galaxy.support.stream.com (Lotus SMTP MTA Internal build v4.6.2 (651.2 6-10-1998)) with SMTP id 852566EE.005BE572; Sun, 3 Jan 1999 11:43:45 -0500 Message-ID: <005501be3737$d091d620$f301040a@c063.beaverton.stream.com> From: "Wiliam Woods" To: "FBSD_QUESTIONS" , "FBSD_CURRENT" Subject: pgcc-1.1.1 Date: Sun, 3 Jan 1999 08:40:41 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anyone here useing pgcc-1.1.1 as their compiler of choice, to replace gcc? I have been debating playing with this on my "spare" system. Any reports from someone useing this, good or bad? Thanks, Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 08:45:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11363 for freebsd-current-outgoing; Sun, 3 Jan 1999 08:45:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA11277; Sun, 3 Jan 1999 08:44:47 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id IAA70031; Sun, 3 Jan 1999 08:44:08 -0800 (PST) To: Robert Sargent cc: freebsd-current@FreeBSD.ORG, freebsd-admin@FreeBSD.ORG Subject: Re: 3.0-19981226-SNAP/src/ssys.ac is corrupt In-reply-to: Your message of "Sun, 03 Jan 1999 11:13:02 EST." <199901031613.LAA02711@lint.cisco.com> Date: Sun, 03 Jan 1999 08:44:08 -0800 Message-ID: <70028.915381848@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Can someone fix this? and perhaps guide me as to where there might be a > mirror that is not corrupt? (I hope the CD wasn't cut from this src). There's nothing wrong with this file - the problem is somewhere on your end, or between our two sites. There's absolutely nothing we can do about it here. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 08:46:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11545 for freebsd-current-outgoing; Sun, 3 Jan 1999 08:46:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA11512; Sun, 3 Jan 1999 08:46:11 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id IAA70054; Sun, 3 Jan 1999 08:45:33 -0800 (PST) To: Robert Sargent cc: freebsd-current@FreeBSD.ORG, freebsd-admin@FreeBSD.ORG Subject: Re: 3.0-19981226-SNAP/src/ssys.ac is corrupt In-reply-to: Your message of "Sun, 03 Jan 1999 11:30:08 EST." <19990103113008.F21893@Sgt-Sun.Cisco.COM> Date: Sun, 03 Jan 1999 08:45:32 -0800 Message-ID: <70051.915381932@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I found a mirror (ftp2 is hosed also) so I got the file, > but you might want to repair the copy on current.freebsd.org. Sigh. There is absolutely nothing to fix. If you're actually doing this from cisco, I know for a fact that cisco's internal network rarely works properly (I've tried to use it on any number of occasions) due to people testing stuff. Go yell at your admins. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 08:55:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA12396 for freebsd-current-outgoing; Sun, 3 Jan 1999 08:55:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA12389 for ; Sun, 3 Jan 1999 08:55:56 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id LAA46464 for ; Sun, 3 Jan 1999 11:59:37 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Sun, 3 Jan 1999 11:59:37 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: freebsd-current@FreeBSD.ORG Subject: make release without source? In-Reply-To: <199901031513.KAA12555@bb01f39.unx.sas.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 tried defining NOSRC on the make release command line, but it insists on running cvs to grab the source tree.... any pointers? I do NOT want to include the source in my distribution as i already have 3 local trees here :) thanks, Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 09:03:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13173 for freebsd-current-outgoing; Sun, 3 Jan 1999 09:03:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13167 for ; Sun, 3 Jan 1999 09:03:05 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id MAA21374; Sun, 3 Jan 1999 12:02:20 -0500 (EST) Date: Sun, 3 Jan 1999 12:02:20 -0500 (EST) From: Daniel Eischen Message-Id: <199901031702.MAA21374@pcnet1.pcnet.com> To: eischen@vigrid.com, mark@grondar.za Subject: Re: Bootblocks / Bootloader Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Murray wrote: > Daniel Eischen wrote: > > also, but "disklabel -B {da0|wd0}" alone won't do it, as it will > > install the default boot blocks from /usr/mdec (I assume that at > > some point disklabel will be changed?). > > *BZZT!* Check the source! :-) Ahh, I was using perforce to sync to plutotech's -current, and I guess I didn't have my client set up correctly (so src/sbin wasn't getting properly updated). Thanks for the wake-up call :-) 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 Sun Jan 3 09:03:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13408 for freebsd-current-outgoing; Sun, 3 Jan 1999 09:03:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa17-47.ix.netcom.com [207.93.156.47]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13402 for ; Sun, 3 Jan 1999 09:03:21 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.1/8.8.8) id JAA64234; Sun, 3 Jan 1999 09:02:35 -0800 (PST) (envelope-from tomdean) Date: Sun, 3 Jan 1999 09:02:35 -0800 (PST) Message-Id: <199901031702.JAA64234@ix.netcom.com> From: Thomas Dean To: rnordier@nordier.com CC: freebsd-current@FreeBSD.ORG In-reply-to: <199901031407.QAA03360@ceia.nordier.com> (message from Robert Nordier on Sun, 3 Jan 1999 16:07:29 +0200 (SAT)) Subject: Re: make aout-to-elf failures (from 2.2.7-RELEASE to -current ELF) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I did an aout-to-elf-build. It appeared to run to completion, although there was no console message about completion. It just stopped after making etc/freebsd.cf. I am running an aout SMP system, cvsup'ed and built yesterday. Building the boot blocks failed. objcopy is in /usr/bin, not /usr/libexec as make complains. I attachd the messages. tomdean ================================================================ # cd /sys/boot # make all install ===> i386/btx/btxldr cc --assembler-with-cpp -c -o btxldr.o /usr/src/sys/boot/i386/btx/btxldr/btxldr.s ld -nostdlib -N -s -T 0x100000 -o btxldr.out btxldr.o dd if=btxldr.out of=btxldr ibs=32 skip=1 37+1 records in 2+1 records out 1200 bytes transferred in 0.004696 secs (255536 bytes/sec) Warning: Object directory not changed from original /usr/src/sys/boot/i386/btx/btxldr ===> i386/btx/lib as -elf -o btxcsu.o btxcsu.s as -elf -o btxsys.o btxsys.s as -elf -o btxv86.o btxv86.s ld -elf -i -o crt0.o btxcsu.o btxsys.o btxv86.o Warning: Object directory not changed from original /usr/src/sys/boot/i386/btx/lib ===> i386/boot2 (cd /usr/src/sys/boot/i386/boot2; m4 boot1.m4 boot1.s) | as -o boot1.o ld -nostdlib -static -N -e start -Ttext 0x7c00 -o boot1.out boot1.o objcopy -S -O binary boot1.out boot1 objcopy: could not exec aout/objcopy in /usr/libexec: No such file or directory *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 09:16:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14663 for freebsd-current-outgoing; Sun, 3 Jan 1999 09:16:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA14645; Sun, 3 Jan 1999 09:16:05 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id DAA08206; Mon, 4 Jan 1999 03:45:39 +1030 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA15403; Mon, 4 Jan 1999 03:45:38 +1030 Date: Mon, 4 Jan 1999 03:45:38 +1030 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: Wiliam Woods Cc: FBSD_QUESTIONS , FBSD_CURRENT Subject: Re: pgcc-1.1.1 In-Reply-To: <005501be3737$d091d620$f301040a@c063.beaverton.stream.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, 3 Jan 1999, Wiliam Woods wrote: > Anyone here useing pgcc-1.1.1 as their compiler of choice, to replace gcc? I > have been debating playing with this on my "spare" system. > Any reports from someone useing this, good or bad? I use egcs-1.1.1 (on which pgcc is based) to compile most of my stuff here, including the world. There are a few small "gotchas", namely bits of the system which will not compile (for me): lib/libc lib/libc_r lib/libstand games/rogue libexec/rtld-elf games/bs gnu/lib/libg++ gnu/lib/libstdc++ gnu/usr.bin/groff sys/boot/ sys/modules I have a small script which recompiles these using CC and CFLAGS and the system gcc, and then just do my usual make depend/make all -j4 cycle to do the rest. The kernel is also not compilable with egcs due to FreeBSD-specific extensions in our gcc compiler. There are the odd one or two ports I've come across which can't be compiled using egcs, but for the most part it works very nicely. A quick-n-dirty benchmark: # dd if=/dev/random of=/usr2/bigfile bs=1024k count=30 # cp /usr2/bigfile /usr2/bigfile2 # /usr/bin/time gzip-486 -9 /usr2/bigfile 26.06 real 20.46 user 1.17 sys # /usr/bin/time gzip-pent -9 /usr2/bigfile2 23.12 real 18.58 user 1.20 sys i.e. a speedup of about 12% gzip-486 was compiled with the stock gcc, -O2 -mno-486 gzip-pentium was compiled with egcs-1.1.1 from the ports collection, -O2 -mpentium -march-pentium Incidentally, the dd command spammed the heck out of my machine..good DoS, anyone? :) Kris > > Thanks, > > Bill > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ----- (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 09:23:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA15370 for freebsd-current-outgoing; Sun, 3 Jan 1999 09:23:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp.enteract.com (thor.enteract.com [207.229.143.11]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA15362 for ; Sun, 3 Jan 1999 09:23:38 -0800 (PST) (envelope-from jrs@enteract.com) Received: (qmail 2466 invoked from network); 3 Jan 1999 17:23:13 -0000 Received: from adam.enteract.com (jrs@206.54.252.1) by thor.enteract.com with SMTP; 3 Jan 1999 17:23:13 -0000 Date: Sun, 3 Jan 1999 11:23:13 -0600 (CST) From: John Sconiers To: freebsd-current@FreeBSD.ORG Subject: PR's for 3.0 only Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings... I went to the bug report page however it has pr for all versions of freebsd. Is there one just for 3.0 or do I have to wade through all of them. Thanks JOHN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 09:25:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA15754 for freebsd-current-outgoing; Sun, 3 Jan 1999 09:25:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from galaxy.support.stream.com (galaxy.support.stream.com [208.13.180.22]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA15730; Sun, 3 Jan 1999 09:25:31 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from c063.beaverton.stream.com ([208.13.191.137]) by galaxy.support.stream.com (Lotus SMTP MTA Internal build v4.6.2 (651.2 6-10-1998)) with SMTP id 852566EE.005F9D9B; Sun, 3 Jan 1999 12:24:23 -0500 Message-ID: <007a01be373d$7d6d4b40$f301040a@c063.beaverton.stream.com> From: "Wiliam Woods" To: "Kris Kennaway" Cc: "FBSD_QUESTIONS" , "FBSD_CURRENT" Subject: Re: pgcc-1.1.1 Date: Sun, 3 Jan 1999 09:21:18 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So, I assume that pgcc will not compile the kernel either then, correct ? -----Original Message----- From: Kris Kennaway To: Wiliam Woods Cc: FBSD_QUESTIONS ; FBSD_CURRENT Date: Sunday, January 03, 1999 9:17 AM Subject: Re: pgcc-1.1.1 >On Sun, 3 Jan 1999, Wiliam Woods wrote: > >> Anyone here useing pgcc-1.1.1 as their compiler of choice, to replace gcc? I >> have been debating playing with this on my "spare" system. >> Any reports from someone useing this, good or bad? > >I use egcs-1.1.1 (on which pgcc is based) to compile most of my stuff here, >including the world. There are a few small "gotchas", namely bits of the >system which will not compile (for me): > >lib/libc lib/libc_r lib/libstand games/rogue libexec/rtld-elf games/bs >gnu/lib/libg++ gnu/lib/libstdc++ gnu/usr.bin/groff sys/boot/ sys/modules > >I have a small script which recompiles these using CC and CFLAGS and the >system gcc, and then just do my usual make depend/make all -j4 cycle to do the >rest. The kernel is also not compilable with egcs due to FreeBSD-specific >extensions in our gcc compiler. > >There are the odd one or two ports I've come across which can't be compiled >using egcs, but for the most part it works very nicely. A quick-n-dirty >benchmark: > ># dd if=/dev/random of=/usr2/bigfile bs=1024k count=30 ># cp /usr2/bigfile /usr2/bigfile2 ># /usr/bin/time gzip-486 -9 /usr2/bigfile > 26.06 real 20.46 user 1.17 sys ># /usr/bin/time gzip-pent -9 /usr2/bigfile2 > 23.12 real 18.58 user 1.20 sys > >i.e. a speedup of about 12% > >gzip-486 was compiled with the stock gcc, -O2 -mno-486 >gzip-pentium was compiled with egcs-1.1.1 from the ports collection, -O2 >-mpentium -march-pentium > >Incidentally, the dd command spammed the heck out of my machine..good DoS, >anyone? :) > >Kris > > > > >> Thanks, >> >> Bill >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-current" in the body of the message >> > >----- >(ASP) Microsoft Corporation (MSFT) announced today that the release of its >productivity suite, Office 2000, will be delayed until the first quarter >of 1901. > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 09:35:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA16518 for freebsd-current-outgoing; Sun, 3 Jan 1999 09:35:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA16513 for ; Sun, 3 Jan 1999 09:35:17 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.101]) by smtp05.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA3495; Sun, 3 Jan 1999 18:34:52 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sun, 03 Jan 1999 18:42:04 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: John Sconiers Subject: RE: PR's for 3.0 only Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-Jan-99 John Sconiers wrote: > Greetings... > > I went to the bug report page however it has pr for all versions of > freebsd. Is there one just for 3.0 or do I have to wade through all of > them. Thanks It's the entire bug repository... For all versions... --- Jeroen Ruigrok van der Werven A veil of smoke is what I am, asmodai(at)wxs.nl I wait and I wait... Network/Security Specialist BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 09:37:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA16827 for freebsd-current-outgoing; Sun, 3 Jan 1999 09:37:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA16822; Sun, 3 Jan 1999 09:37:39 -0800 (PST) (envelope-from narvi@haldjas.folklore.ee) Received: from haldjas.folklore.ee (haldjas.folklore.ee [172.17.2.1] (may be forged)) by haldjas.folklore.ee (8.8.8/8.8.4) with SMTP id TAA19472; Sun, 3 Jan 1999 19:37:12 +0200 (EET) Date: Sun, 3 Jan 1999 19:37:12 +0200 (EET) From: Narvi To: Gary Palmer cc: Jonathan Smith , current@FreeBSD.ORG Subject: Re: Y2K, Y 2038? In-Reply-To: <75916.915304507@gjp.erols.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 2 Jan 1999, Gary Palmer wrote: > Jonathan Smith wrote in message ID > : > > the world is freaking out over it. Perhaps an introduction of a 64 bit > > time, or larger under a different name, and have BSD start working over > > towards the new name now and deprecating the old time variable? > > While the world is still using 32bit CPUs the move to 64bit time_t will be > expensive in terms of performance. We could probably make the move on the DEC > Alpha, but until ppl move to the Merced (or whatever 64bit P.O.S. Intel > produces) I don't think many people will like to take the performance > degredation now. > Will it really? We are using 64 bit file offsets now (for a good reason, I might add), and these are definately more widely used than dates. What actually uses the date code widely? Make? > Personally, my thoughs on how to do this are to have new syscalls which return > 64 bit time_t variables, and you choose at compile time which ones you get > (i.e. sorta like the way solaris 7 has done things) > > Gary > -- > Gary Palmer FreeBSD Core Team Member > FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info > Sander There is no love, no good, no happiness and no future - all these are just illusions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 09:40:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA17472 for freebsd-current-outgoing; Sun, 3 Jan 1999 09:40:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17452; Sun, 3 Jan 1999 09:40:40 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id DAA08225; Mon, 4 Jan 1999 03:59:13 +1030 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA24182; Mon, 4 Jan 1999 03:59:12 +1030 Date: Mon, 4 Jan 1999 03:59:12 +1030 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: Wiliam Woods Cc: FBSD_QUESTIONS , FBSD_CURRENT Subject: Re: pgcc-1.1.1 In-Reply-To: <007a01be373d$7d6d4b40$f301040a@c063.beaverton.stream.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, 3 Jan 1999, Wiliam Woods wrote: > So, I assume that pgcc will not compile the kernel either then, correct ? pgcc would lack the same freebsd-local compiler extensions, I would imagine, yes. Kris ----- (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 09:50:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18476 for freebsd-current-outgoing; Sun, 3 Jan 1999 09:50:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-2-dbn.dial-up.net [196.34.155.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA18467 for ; Sun, 3 Jan 1999 09:50:52 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id TAA04737; Sun, 3 Jan 1999 19:49:08 +0200 (SAT) From: Robert Nordier Message-Id: <199901031749.TAA04737@ceia.nordier.com> Subject: Re: Bootblocks / Bootloader In-Reply-To: from Jeroen Ruigrok/Asmodai at "Jan 3, 99 05:12:08 pm" To: asmodai@wxs.nl (Jeroen Ruigrok/Asmodai) Date: Sun, 3 Jan 1999 19:49:05 +0200 (SAT) Cc: rnordier@nordier.com, current@FreeBSD.ORG, mike@smith.net.au X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeroen Ruigrok/Asmodai wrote: > >> boot: > >> > >> Booting 0:da(0,a)/boot/loader @ 0x100000 > >> text=0x1000 data=0x1c000 bss=0x00 symbols=[0x0+0x4+0x0+0x4+0xff8c] > >> > >> Can't find file /boot/loader.config > >> total=0x12cf94 entry point=0x100000 > >> > >> BTX loader > >> > >> ... [looks good] > >> bootstrap loader revision 0.2 > > > > These messages indicate that you *don't* have the new boot blocks > > installed, but the old ones. > > Now I don't know anymore... I do however have a totally different boot > process than I had before... So now I am lost... I was about to write a short > document about it, but I guess that will now be incorrect ;) > > Any hints/tips? I've put up some brief instructions on updating the boot blocks at http://www.freebsd.org/~rnordier/boot.txt though I'll try to expand these in the next ~8 hours. I'd suggest just redoing the steps mentioned there, and you'll probably pick up where things went wrong. Bear in mind that, most of the time, the new boot blocks simply pass control to /boot/loader. You can use *recent* versions of the old boot blocks to start /boot/loader as well. A primary advantage of installing the new boot blocks is that they can load both aout and ELF kernels themselves, if necessary. So, if /boot/loader is temporarily broken, or your root file system is corrupted, you have a better chance of booting. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 10:53:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24301 for freebsd-current-outgoing; Sun, 3 Jan 1999 10:53:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-28-dbn.dial-up.net [196.34.155.92]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24199 for ; Sun, 3 Jan 1999 10:53:12 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id UAA05074; Sun, 3 Jan 1999 20:51:31 +0200 (SAT) From: Robert Nordier Message-Id: <199901031851.UAA05074@ceia.nordier.com> Subject: Re: make aout-to-elf failures (from 2.2.7-RELEASE to -current ELF) In-Reply-To: <199901031702.JAA64234@ix.netcom.com> from Thomas Dean at "Jan 3, 99 09:02:35 am" To: tomdean@ix.netcom.com (Thomas Dean) Date: Sun, 3 Jan 1999 20:51:29 +0200 (SAT) Cc: rnordier@nordier.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas Dean wrote: > I did an aout-to-elf-build. It appeared to run to completion, > although there was no console message about completion. It just > stopped after making etc/freebsd.cf. > > I am running an aout SMP system, cvsup'ed and built yesterday. > Building the boot blocks failed. objcopy is in /usr/bin, not > /usr/libexec as make complains. I attachd the messages. > > tomdean > > ================================================================ > > # cd /sys/boot > # make all install > > ===> i386/btx/btxldr > cc --assembler-with-cpp -c -o btxldr.o /usr/src/sys/boot/i386/btx/btxldr/btxldr.s > ld -nostdlib -N -s -T 0x100000 -o btxldr.out btxldr.o > dd if=btxldr.out of=btxldr ibs=32 skip=1 > 37+1 records in > 2+1 records out > 1200 bytes transferred in 0.004696 secs (255536 bytes/sec) > Warning: Object directory not changed from original /usr/src/sys/boot/i386/btx/btxldr > ===> i386/btx/lib > as -elf -o btxcsu.o btxcsu.s > as -elf -o btxsys.o btxsys.s > as -elf -o btxv86.o btxv86.s > ld -elf -i -o crt0.o btxcsu.o btxsys.o btxv86.o > Warning: Object directory not changed from original /usr/src/sys/boot/i386/btx/lib > ===> i386/boot2 > (cd /usr/src/sys/boot/i386/boot2; m4 boot1.m4 boot1.s) | as -o boot1.o > ld -nostdlib -static -N -e start -Ttext 0x7c00 -o boot1.out boot1.o > objcopy -S -O binary boot1.out boot1 > objcopy: could not exec aout/objcopy in /usr/libexec: No such file or directory > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > This indicates that the new boot code is being built in a.out rather than ELF format. You need ELF for this. It's a long time since I did an aout-to-elf upgrade, but it seems your system hasn't been properly or completely upgraded to ELF. You could try setting OBJFORMAT to ELF explicitly. If that works, you have an ELF world but most likely an incorrect setting somewhere. Otherwise you'll have to retry the aout-to-elf upgrade. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 10:58:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24668 for freebsd-current-outgoing; Sun, 3 Jan 1999 10:58:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.westbend.net (ns1.westbend.net [156.46.203.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24637 for ; Sun, 3 Jan 1999 10:58:11 -0800 (PST) (envelope-from hetzels@westbend.net) Received: from admin (wbiS11.westbend.net [156.46.203.26]) by mail.westbend.net (8.8.8/8.8.8) with SMTP id MAA00868; Sun, 3 Jan 1999 12:57:34 -0600 (CST) (envelope-from hetzels@westbend.net) Message-ID: <00ea01be374a$b11fa020$1acb2e9c@westbend.net> From: "Scot W. Hetzel" To: "Barrett Richardson" , "Erick Baum" Cc: "FreeBSD-Current" References: Subject: Re: FrontPage Extensions Date: Sun, 3 Jan 1999 12:35:35 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.1012.1001 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.1012.1001 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Barrett Richardson > On Sat, 2 Jan 1999, Erick Baum wrote: > > > I've seen some previous posts about the FrontPage Extensions for FreeBSD > > opening up some major security holes. Can someone tell me what kind of > > security issues they are? > > > > Also, I have been having trouble getting the extensions to work on FreeBSD > > 2.2.6. Does anyone know if there is something special I have to do? > > > > Any input is appreciated. Thanks. > > > > -Erick > > > > I was digging thru the frontpage module and discovered that it wants > a geteuid() == 0 before it will launch any of the cgi's that will > do glorious things for your users. The cgi's end up running on > behalf of a user, but the mechanism (as much of it as I understand) > that makes that happen leaves opportunity for problems. The module > checks the ownership of a "webroot" directory (appears to be the > document root from the little I've seen thus far) and compares > it to the ownership of /_vti_pvt and sees if they match. If they > do, environment variables FPUID and FPGID are set to the uid and > gid of these directories. A suid wrapper, fpexe, sets its > uid and gid based on FPUID and FPGID that it inherited from the > webserver. The wrapper, fpexe, only can run a predetermined set > of progs (the suite of frontpage stuff). From what little info > I have found, the cgi scripts then authenticate the user it is > already running as from some info stashed away in some *.pwd > files. I found no authentication in the frontpage module or > in fpexe.c. > That is because the FP module uses the authentication methods of the Apache Server. > From the information I have about how it operates, I don't > understand why the server must be run as root. Also I don't > understand how the frontpage cgi's could authenticate from > files with safe permissions if they are indeed being run > from a wrapper which sets appropriate uid/gid before launching > them. I found a recent posting in -security that mentioned > that the authentication files must be readable by the > uid of the webserver -- but still, if the cgi scripts > authenticate themselves and a suid wrapper sets their > uid/gid, the uid of the webserver should be out of the > picture. The uid of the server doesn't matter, I have my server runnig as user/group www. But the Apache server still needs to be able to read the contents of the root/user/virtual webs so that it can send the proper file to the browser or frontpage client. > > I thinking of using it by putting some authentication in > the wrapper (via a cookie, I think, and use https) before > the setuid()/setgid() are done. At any rate, I wouldn't > dare use it as it is until I find some more definitive > information about how it authenticates. > No need as authentication is done by the Apache server. Also, if you are going to let users/virual webs have access to the FP Exts, it is best to install the suexec program to prevent any security holes from users running their own CGI programs. Currently, the FP Exts are run as CGI scripts, with out the "Options ExecCGI" added to the user/virtual web Directory directive they will not run. Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 11:14:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA26256 for freebsd-current-outgoing; Sun, 3 Jan 1999 11:14:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dns.webwizard.net.mx (webwizard.net.mx [148.245.50.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA26244 for ; Sun, 3 Jan 1999 11:14:14 -0800 (PST) (envelope-from eculp@webwizard.org.mx) Received: from webwizard.org.mx (webwizard.net.mx [148.245.50.27]) by dns.webwizard.net.mx (8.9.1/8.9.1) with ESMTP id NAA57990 for ; Sun, 3 Jan 1999 13:13:48 -0600 (CST) (envelope-from eculp@webwizard.org.mx) Message-ID: <368FC16C.C15AF00@webwizard.org.mx> Date: Sun, 03 Jan 1999 13:13:48 -0600 From: Edwin Culp X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-current@FreeBSD.ORG" Subject: Disk space for a make release. 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 tried to Make a Release with about 1.1 GB in my release partition and it ran out of space. Does anyone know how much is needed now? I hadn't made on since the beginning of December. I don't remember the space it took because I always just newfs the partition to make a new one. Thanks 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 3 11:27:02 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27405 for freebsd-current-outgoing; Sun, 3 Jan 1999 11:27:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa17-47.ix.netcom.com [207.93.156.47]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27400 for ; Sun, 3 Jan 1999 11:27:00 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.1/8.8.8) id LAA87195; Sun, 3 Jan 1999 11:26:13 -0800 (PST) (envelope-from tomdean) Date: Sun, 3 Jan 1999 11:26:13 -0800 (PST) Message-Id: <199901031926.LAA87195@ix.netcom.com> From: Thomas Dean To: rnordier@nordier.com CC: rnordier@nordier.com, freebsd-current@FreeBSD.ORG In-reply-to: <199901031851.UAA05074@ceia.nordier.com> (message from Robert Nordier on Sun, 3 Jan 1999 20:51:29 +0200 (SAT)) Subject: Re: make aout-to-elf failures (from 2.2.7-RELEASE to -current ELF) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for the reply. I, incorrectly, understood that the bootblocks could be updated from aout. So, I only did the build part of aout-to-elf. I will do the aout-to-elf-install and retry to make/install the bootblocks. tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 11:30:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27789 for freebsd-current-outgoing; Sun, 3 Jan 1999 11:30:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from megaweapon.zigg.com (megaweapon.zigg.com [206.114.60.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27780 for ; Sun, 3 Jan 1999 11:30:46 -0800 (PST) (envelope-from matt@megaweapon.zigg.com) Received: from localhost (matt@localhost) by megaweapon.zigg.com (8.8.8/8.8.8) with ESMTP id OAA07329 for ; Sun, 3 Jan 1999 14:30:20 -0500 (EST) (envelope-from matt@megaweapon.zigg.com) Date: Sun, 3 Jan 1999 14:30:20 -0500 (EST) From: Matt Behrens To: current@FreeBSD.ORG Subject: How's the latest -SNAP? Message-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 smoothly as aout-to-elf seems to be going along, I'm going to be hitting the sysinstall freshly when I'm ready to move my main machine to 3.0 in a couple weeks. (Reasoning is too long to go into here, but they include more garbage than is worth tracking down from ports that have misbehaved in the past and left files strewn all about /usr/local as well as the need for a different partitioning scheme to faciliate new hard drives I'm bringing in.) My questions are these: 1. Are the SNAPs fully ELF? 2. Are the new bootloaders used? 3. What is the shape of installing from the SNAP in general? Any gotchas? TIA. (I couldn't find much from the archives.) - Matt "Zigg" Behrens Network Administrator, zigg.com Engineer, Nameless IRC Network To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 11:34:16 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA28364 for freebsd-current-outgoing; Sun, 3 Jan 1999 11:34:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles317.castles.com [208.214.167.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA28351 for ; Sun, 3 Jan 1999 11:34:13 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id LAA06745; Sun, 3 Jan 1999 11:30:50 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901031930.LAA06745@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Jeroen Ruigrok/Asmodai cc: FreeBSD Current Subject: Re: Bootblocks / Bootloader In-reply-to: Your message of "Sun, 03 Jan 1999 12:36:45 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 03 Jan 1999 11:30:49 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > OK, just rebooted and wrote down some things: > > > boot: > > Booting 0:da(0,a)/boot/loader @ 0x100000 > text=0x1000 data=0x1c000 bss=0x00 symbols=[0x0+0x4+0x0+0x4+0xff8c] > > Can't find file /boot/loader.config > total=0x12cf94 entry point=0x100000 > > BTX loader > > ... [looks good] > > bootstrap loader revision 0.2 > Can't open /boot/boot.conf: no such file or directory Ok, this is harmless. It emits this message for the same reason that the old bootblocks complained about boot.config and boot.help - so that you know that it would be using them if they were there. We could suppress this, or you could just touch the file; I'm easy either way. > ... [booting kernel] > > [kernel symbol table not valid] This is actually DDB complaining that your a.out symbol table is not valid. You may have over-aggressively stripped your kernel, or we may have something going wrong that's eaten it in the load process. > Any hints regarding loader.config and boot.conf are I think the last hurdles > I face with the loader... [ Wishful thinking mayhaps ;) ] Hints for "loader.config" are easy - it doesn't exist. The online help in the loader is your best reference (for now) for boot.conf (soon to be loader.rc). It's still in flux, although I expect to have to freeze it soon for 3.0.x. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 11:47:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA00361 for freebsd-current-outgoing; Sun, 3 Jan 1999 11:47:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA00356 for ; Sun, 3 Jan 1999 11:47:53 -0800 (PST) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.9.2/8.9.2) with ESMTP id OAA86745; Sun, 3 Jan 1999 14:47:20 -0500 (EST) Date: Sun, 3 Jan 1999 14:47:20 -0500 (EST) From: jack To: Edwin Culp cc: "freebsd-current@FreeBSD.ORG" Subject: Re: Disk space for a make release. In-Reply-To: <368FC16C.C15AF00@webwizard.org.mx> Message-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, 3 Jan 1999, Edwin Culp wrote: > I just tried to Make a Release with about 1.1 GB in my release partition > and it ran out of space. Does anyone know how much is needed now? I That's more than enough. You probable copied your entire /usr/ports/distfiles directory. Look in release/Makefile for # Set this to wherever the distfiles required by ${DOCPORTS} live. DISTFILES?= ${.CURDIR}/../../ports/distfiles and point that to some other directory that contains only the sources needed by textproc/docproj. I'm told it's a feature. :) -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 11:54:02 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA00775 for freebsd-current-outgoing; Sun, 3 Jan 1999 11:54:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bouvreuil.cybercable.fr (bouvreuil.cybercable.fr [212.198.3.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA00761 for ; Sun, 3 Jan 1999 11:54:00 -0800 (PST) (envelope-from herbelot@cybercable.fr) Received: (qmail 1380 invoked from network); 3 Jan 1999 19:46:37 -0000 Received: from d003.paris-21.cybercable.fr (HELO cybercable.fr) (212.198.21.3) by bouvreuil.cybercable.fr with SMTP; 3 Jan 1999 19:46:37 -0000 Message-ID: <368FC908.1D728596@cybercable.fr> Date: Sun, 03 Jan 1999 20:46:17 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Is my /dev/random broken ? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, This is a follow-on to a post by Kris Kennaway (Re pgcc-1.1.1). I have a recent -Current (cvsupped on Dec 19 13:01) with an a.out kernel and an elf userland and I have tried to duplicate Kris' test : # dd if=/dev/random of=/usr2/bigfile bs=1024k count=30 # cp /usr2/bigfile /usr2/bigfile2 # /usr/bin/time gzip-486 -9 /usr2/bigfile 26.06 real 20.46 user 1.17 sys # /usr/bin/time gzip-pent -9 /usr2/bigfile2 23.12 real 18.58 user 1.20 sys But the first line gives the following : #dd if=/dev/random of=bigfile bs=1024k count=30 0+2 records in 0+2 records out 6 bytes transferred in 0.000387 secs (15506 bytes/sec) # repeated executions give **random** numbers of "bytes transferred" (but never the right number) dd seems to work (I have used it to copy parts of the Generic kernel), so /dev/random must be broken ??? I could live without /dev/random, but what next ? TfH To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 12:04:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01657 for freebsd-current-outgoing; Sun, 3 Jan 1999 12:04:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcpsj.pfcs.com (harlan.clark.net [168.143.10.179]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA01652 for ; Sun, 3 Jan 1999 12:04:11 -0800 (PST) (envelope-from Harlan.Stenn@pfcs.com) Received: from mumps.pfcs.com [192.52.69.11] (HELO mumps.pfcs.com) by pcpsj.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Sun, 3 Jan 1999 15:03:19 -0500 (EST) Received: from brown.pfcs.com [192.52.69.44] (HELO brown.pfcs.com) by mumps.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Sun, 3 Jan 1999 12:03:18 -0800 (PST) Received: from localhost [127.0.0.1] (HELO brown.pfcs.com) by brown.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Sun, 3 Jan 1999 15:03:18 -0500 (EST) X-Mailer: exmh version 2.0.2 2/24/98 To: Thierry Herbelot cc: current@FreeBSD.ORG Subject: Re: Is my /dev/random broken ? In-Reply-To: Thierry Herbelot's (herbelot@cybercable.fr) message dated Sun, 03 Jan 1999 20:46:17. <368FC908.1D728596@cybercable.fr> X-Face: "csXK}xnnsH\h_ce`T#|pM]tG,6Xu.{3Rb\]&XJgVyTS'w{E+|-(}n:c(Cc* $cbtusxDP6T)Hr'k&zrwq0.3&~bAI~YJco[r.mE+K|(q]F=ZNXug:s6tyOk{VTqARy0#axm6BWti9C d Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 03 Jan 1999 15:03:17 -0500 Message-ID: <856.915393797@brown.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG man 4 random To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 12:05:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01829 for freebsd-current-outgoing; Sun, 3 Jan 1999 12:05:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bingsun2.cc.binghamton.edu (bingsun2.cc.binghamton.edu [128.226.1.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA01824 for ; Sun, 3 Jan 1999 12:05:45 -0800 (PST) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun2.cc.binghamton.edu (8.8.7/8.6.9) with SMTP id PAA23462; Sun, 3 Jan 1999 15:04:57 -0500 (EST) Date: Sun, 3 Jan 1999 15:04:57 -0500 (EST) From: zhihuizhang X-Sender: bf20761@bingsun2 To: Thierry Herbelot cc: current@FreeBSD.ORG Subject: Re: Is my /dev/random broken ? In-Reply-To: <368FC908.1D728596@cybercable.fr> Message-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, 3 Jan 1999, Thierry Herbelot wrote: > Hello, > > This is a follow-on to a post by Kris Kennaway (Re pgcc-1.1.1). > > I have a recent -Current (cvsupped on Dec 19 13:01) with an a.out kernel > and an elf userland and I have tried to duplicate Kris' test : > > # dd if=/dev/random of=/usr2/bigfile bs=1024k count=30 > # cp /usr2/bigfile /usr2/bigfile2 > # /usr/bin/time gzip-486 -9 /usr2/bigfile > 26.06 real 20.46 user 1.17 sys > # /usr/bin/time gzip-pent -9 /usr2/bigfile2 > 23.12 real 18.58 user 1.20 sys > > But the first line gives the following : > > #dd if=/dev/random of=bigfile bs=1024k count=30 > 0+2 records in > 0+2 records out > 6 bytes transferred in 0.000387 secs (15506 bytes/sec) > # > repeated executions give **random** numbers of "bytes transferred" (but > never the right number) > > dd seems to work (I have used it to copy parts of the Generic kernel), > so /dev/random must be broken ??? > > I could live without /dev/random, but what next ? > I guess that you should use /dev/urandom instead of /dev/random. /dev/random only return a maximum of the number of bits of random contained in the entropy pool. /dev/urandom returns as many bytes as you requested. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 12:10:38 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA02167 for freebsd-current-outgoing; Sun, 3 Jan 1999 12:10:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA02162 for ; Sun, 3 Jan 1999 12:10:37 -0800 (PST) (envelope-from kdsfjuie@gre.ac.uk) From: kdsfjuie@gre.ac.uk Received: from dellcity.com ([207.243.98.34]) by freefall.freebsd.org (8.8.8/8.8.5) with SMTP id MAA06610 for ; Sun, 3 Jan 1999 12:10:30 -0800 (PST) Received: from default by dellcity.com (SMI-8.6/SMI-SVR4) id MAA15233; Sun, 3 Jan 1999 12:47:20 -0700 Date: Sun, 3 Jan 1999 12:47:20 -0700 Message-Id: <199901031947.MAA15233@dellcity.com> To: kdsfjuie@gre.ac.uk Subject: Unlimited Income Opportunity Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Look, we don't want to waste your time....or ours. If you are 100% SERIOUS about earning a solid, six-figure income from home, and you're not afraid to work for it WE CAN HELP YOU! * NOT MLM or GLOBAL * Completely Legitimate Home-Based Business * Registered with D&B and BBB * Professional Training and Fantastic Support * Work Entirely From Home (no personal selling) Grab your share of the 3.4 Trillion Dollar Travel Industry NOW! CALL TOLL FREE 888-693-3317 (24 Hour Recorded 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 3 12:15:41 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA02672 for freebsd-current-outgoing; Sun, 3 Jan 1999 12:15:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from houcbs2.houabg.com (houabg.com [206.109.247.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA02667 for ; Sun, 3 Jan 1999 12:15:39 -0800 (PST) (envelope-from dchapman@houabg.com) Received: from sdn-ar-004txhousP268.dialsprint.net by houcbs2.houabg.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1457.7) id ZBAFFAYH; Sun, 3 Jan 1999 14:21:53 -0600 Message-ID: <368FD021.4C0CC43A@houabg.com> Date: Sun, 03 Jan 1999 14:16:33 -0600 From: "David W. Chapman Jr." X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current Subject: Advertisement Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why would anyone in here want to listen to that crappy scam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 12:23:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA03469 for freebsd-current-outgoing; Sun, 3 Jan 1999 12:23:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA03328 for ; Sun, 3 Jan 1999 12:23:08 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id MAA70712; Sun, 3 Jan 1999 12:22:34 -0800 (PST) To: Matt Behrens cc: current@FreeBSD.ORG Subject: Re: How's the latest -SNAP? In-reply-to: Your message of "Sun, 03 Jan 1999 14:30:20 EST." Date: Sun, 03 Jan 1999 12:22:34 -0800 Message-ID: <70708.915394954@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 1. Are the SNAPs fully ELF? Not the kernels. Not until the 6th. > 2. Are the new bootloaders used? Yes. > 3. What is the shape of installing from the SNAP in general? Any > gotchas? Should work. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 12:24:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA03602 for freebsd-current-outgoing; Sun, 3 Jan 1999 12:24:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles317.castles.com [208.214.167.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA03597 for ; Sun, 3 Jan 1999 12:24:45 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA07058; Sun, 3 Jan 1999 12:21:14 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901032021.MAA07058@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Thomas Dean cc: peter@netplex.com.au, mike@smith.net.au, freebsd-current@FreeBSD.ORG Subject: Re: make aout-to-elf failures (from 2.2.7-RELEASE to -current ELF) In-reply-to: Your message of "Sat, 02 Jan 1999 20:08:35 PST." <199901030408.UAA44371@ix.netcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 03 Jan 1999 12:21:13 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have a -current system that just completed an aout 'make world' from > sources of about 19990102 1400 PST. Is this the SMP system you were holding back with? If so, I'm very happy to hear it came through alright. At this phase, I would be strongly recommending that you look at migrating to ELF. There's a very succinct and AFAIK still accurate description of the process at the top of src/Makefile, which hopefully should answer any questions you have on this topic. > I am in the midst of updating the bootblocks. I have two SCSI disks, > da0 is WINNT and da1 is -current. I am currently using OS-BS. I am > reading in the archives, attempting to upgrade. So far, I have > backed-up and made new boot and fixit floppies. Note that you can refrain from updating the bootblocks until you convert to an ELF kernel; before that point there's no need to convert. > I found in the archives: > > cp /usr/mdec/boot? /boot Aigh! I don't know where you got that one from, but definitely don't do that. /boot is populated directly by an ELF 'make world'. > echo '/boot/loader' > /boot.config > disklabel -B bootdevices > > Also a reference to make in /sys/boot. > > Will 'make && make install' in /sys/boot do all that is needed? Not in an a.out world. Once you have completed the a.out to ELF conversion, /boot will be correctly populated. > Any pointers to doc's on upgrade the bootblocks? There have been some succinct descriptions past here on -current in the last day or so; if in doubt, listen to everything that Robert Nordier has had to say. He wrote the replacement boot0/1/2 modules as well as the really nasty bits of the loader, and can generally be counted on to be right about what's going on. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 12:25:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA03696 for freebsd-current-outgoing; Sun, 3 Jan 1999 12:25:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www1.interdestination.net (www1.interdestination.net [209.12.127.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA03690 for ; Sun, 3 Jan 1999 12:25:33 -0800 (PST) (envelope-from zapper@idsmail.com) Received: from idsmail.com (zapper@id3.dialup.interdestination.com [209.12.192.83]) by www1.interdestination.net (8.9.1/8.9.1) with ESMTP id OAA18753 for ; Sun, 3 Jan 1999 14:32:04 -0600 (CST) Message-ID: <368FD169.4BC88D65@idsmail.com> Date: Sun, 03 Jan 1999 14:22:02 -0600 From: Zapper X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: FreeBSD Current Subject: Multiple Partions Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have Win 95 and FreeBSD 3.0-Current installed on my computer. I have 2 hard drives installed with the Win95 OS on the "master" a 1.5G Western Digital and FreeBSD on the "slave" a 4.3G Quantum Bigfoot. The 4.3 is partitioned with about 2.5G of space for FreeBSD with the remaining space allocated to Win 95 programs. When I installed FreeBSD from the cd I created a "slice" so I could boot to either Win95 or FreeBSD i.e.: F1 DOS F5 FreeBSD Win95 crashed and I was forced to reinstall it, which I did without formatting so as not to mess up my boot partition or so I had hoped. To make a long story short, while I am still able to boot to FreeBSD and run it, I keep having problems that have just started since I reinstalled Win95. Problems are, when I do "make buildworld" in /usr/src , it crashes, but the errors are different everytime with the most popular error being cc: Internal compiler error: program cc1 got fatal signal 11 *** Error code 1 Stop. I've tried "make buildword" , "make -DNOCLEAN buildword" and just plain ole "make world" with no success. 2nd problem is, when I try to compile a new kernel it crashes also with pretty much different errors everytime. Keep in mind that I have had relatively "no" real problems until I reinstalled Win 95 so having said all that, my question is, is there a way to reinstall the slice or redefine the partition? Also, since it now looks like I'm going to have to "fully" reinstall Win 95 with format I know I will totally obliterate my slice. Is there a way to save my slice and partition info? I'm still kinda new to FreeBSD and Unix so try not to be to critical ... I am "trying" :) Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 12:41:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA05080 for freebsd-current-outgoing; Sun, 3 Jan 1999 12:41:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from camel7.mindspring.com (camel7.mindspring.com [207.69.200.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA05072 for ; Sun, 3 Jan 1999 12:41:17 -0800 (PST) (envelope-from brdean@mindspring.com) Received: from vger.foo.com (user-38ld95u.dialup.mindspring.com [209.86.164.190]) by camel7.mindspring.com (8.8.5/8.8.5) with ESMTP id PAA24477; Sun, 3 Jan 1999 15:40:51 -0500 (EST) Received: (from bsd@localhost) by vger.foo.com (8.9.1/8.9.1) id PAA68739; Sun, 3 Jan 1999 15:39:45 -0500 (EST) (envelope-from bsd) From: Brian Dean Message-Id: <199901032039.PAA68739@vger.foo.com> Subject: Re: make release (almost) No space left on device In-Reply-To: <199901031513.KAA12555@bb01f39.unx.sas.com> from "John W. DeBoskey" at "Jan 3, 1999 10:13: 6 am" To: jwd@unx.sas.com (John W. DeBoskey) Date: Sun, 3 Jan 1999 15:39:45 -0500 (EST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Folks, > sh -e /usr/src/release/scripts/doFS.sh /R/stage /mnt 1440 /R/stage/boot.std 80000 fd1440 > disklabel: ioctl DIOCWLABEL: Operation not supported by device > /dev/rvn0c: 2880 sectors in 80 cylinders of 2 tracks, 18 sectors > 1.4MB in 5 cyl groups (16 c/g, 0.28MB/g, 32 i/g) > super-block backups (for fsck -b #) at: > 32, 632, 1184, 1784, 2336, > cpio: write error: No space left on device > *** Error code 1 > > > Maybe we can move to having a network installation floppy and a > disk media installation floppy... I personally do not want to see > a multidisk boot process. I've used it on other systems, and it > really hurts. I second this suggestion. Please avoid having a two (or more - ouch!) floppy install process. I typically install up to 30 machines at a time and a two floppy install will make this chore almost unbearable! Thanks, -Brian -- Brian Dean brdean@mindspring.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 3 12:45:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA05825 for freebsd-current-outgoing; Sun, 3 Jan 1999 12:45:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA05820 for ; Sun, 3 Jan 1999 12:45:34 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.57.15]) by smtp05.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA5345; Sun, 3 Jan 1999 21:45:08 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199901031930.LAA06745@dingo.cdrom.com> Date: Sun, 03 Jan 1999 21:52:19 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Mike Smith Subject: Re: Bootblocks / Bootloader Cc: FreeBSD Current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-Jan-99 Mike Smith wrote: >> ... [booting kernel] >> >> [kernel symbol table not valid] > > This is actually DDB complaining that your a.out symbol table is not > valid. You may have over-aggressively stripped your kernel, or we may > have something going wrong that's eaten it in the load process. I never stripped my kernels... And this is an ELF kernel from the 2nd and it's still giving the notice after I installed the real new bootblocks... At least that's what I am presuming since the whole system is ELF ;) >> Any hints regarding loader.config and boot.conf are I think the last >> hurdles >> I face with the loader... [ Wishful thinking mayhaps ;) ] > > Hints for "loader.config" are easy - it doesn't exist. > > The online help in the loader is your best reference (for now) for > boot.conf (soon to be loader.rc). It's still in flux, although I > expect to have to freeze it soon for 3.0.x. OK, that explains some more =) I have been reading a bit about the boot process while messing around with it... I have to say the 4.4 BSD book is a handy insight to have... thanks, --- Jeroen Ruigrok van der Werven A veil of smoke is what I am, asmodai(at)wxs.nl I wait and I wait... Network/Security Specialist BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 12:46:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA05848 for freebsd-current-outgoing; Sun, 3 Jan 1999 12:45:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA05835 for ; Sun, 3 Jan 1999 12:45:40 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.57.15]) by smtp05.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA5359; Sun, 3 Jan 1999 21:45:10 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199901031749.TAA04737@ceia.nordier.com> Date: Sun, 03 Jan 1999 21:52:21 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Robert Nordier Subject: Re: Bootblocks / Bootloader Cc: mike@smith.net.au, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-Jan-99 Robert Nordier wrote: > I've put up some brief instructions on updating the boot blocks at > > http://www.freebsd.org/~rnordier/boot.txt OK, that helped... > I'd suggest just redoing the steps mentioned there, and you'll > probably pick up where things went wrong. > > Bear in mind that, most of the time, the new boot blocks simply > pass control to /boot/loader. You can use *recent* versions of > the old boot blocks to start /boot/loader as well. Weird thing is that the first time it displayed the FreeBSD/i386 Boot message and after I rm'ed /boot.config I never saw it again, and I rebooted two/three times... --- Jeroen Ruigrok van der Werven A veil of smoke is what I am, asmodai(at)wxs.nl I wait and I wait... Network/Security Specialist BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 12:47:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA05999 for freebsd-current-outgoing; Sun, 3 Jan 1999 12:47:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles317.castles.com [208.214.167.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA05994 for ; Sun, 3 Jan 1999 12:47:05 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA07228; Sun, 3 Jan 1999 12:43:51 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901032043.MAA07228@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Dean cc: jwd@unx.sas.com (John W. DeBoskey), freebsd-current@FreeBSD.ORG Subject: Re: make release (almost) No space left on device In-reply-to: Your message of "Sun, 03 Jan 1999 15:39:45 EST." <199901032039.PAA68739@vger.foo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 03 Jan 1999 12:43:50 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Maybe we can move to having a network installation floppy and a > > disk media installation floppy... I personally do not want to see > > a multidisk boot process. I've used it on other systems, and it > > really hurts. > > I second this suggestion. > > Please avoid having a two (or more - ouch!) floppy install process. I > typically install up to 30 machines at a time and a two floppy install > will make this chore almost unbearable! We'll do what we can, but consider using a bootable CDROM instead of floppies for your installs. Much faster. There's a limit to what we can pack onto a floppy, unfortunately. 8( -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 12:56:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA06901 for freebsd-current-outgoing; Sun, 3 Jan 1999 12:56:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles317.castles.com [208.214.167.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA06896 for ; Sun, 3 Jan 1999 12:56:19 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA07318; Sun, 3 Jan 1999 12:52:45 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901032052.MAA07318@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Jeroen Ruigrok/Asmodai cc: Robert Nordier , mike@smith.net.au, current@FreeBSD.ORG Subject: Re: Bootblocks / Bootloader In-reply-to: Your message of "Sun, 03 Jan 1999 21:52:21 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 03 Jan 1999 12:52:44 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Bear in mind that, most of the time, the new boot blocks simply > > pass control to /boot/loader. You can use *recent* versions of > > the old boot blocks to start /boot/loader as well. > > Weird thing is that the first time it displayed the FreeBSD/i386 Boot > message and after I rm'ed /boot.config I never saw it again, and I rebooted > two/three times... That's normal; the "old" help is only displayed in "compatibility" mode. Without a /boot.config, the bootblocks try to be as quiet as possible. You may notice the spinner stop for a couple of seconds; if you hit a key at that point, you'll drop back into "compatibility" mode again. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 12:58:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07009 for freebsd-current-outgoing; Sun, 3 Jan 1999 12:58:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles317.castles.com [208.214.167.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07004 for ; Sun, 3 Jan 1999 12:58:35 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA07348; Sun, 3 Jan 1999 12:55:19 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901032055.MAA07348@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Jeroen Ruigrok/Asmodai cc: Mike Smith , FreeBSD Current Subject: Re: Bootblocks / Bootloader In-reply-to: Your message of "Sun, 03 Jan 1999 21:52:19 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 03 Jan 1999 12:55:19 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On 03-Jan-99 Mike Smith wrote: > > >> ... [booting kernel] > >> > >> [kernel symbol table not valid] > > > > This is actually DDB complaining that your a.out symbol table is not > > valid. You may have over-aggressively stripped your kernel, or we may > > have something going wrong that's eaten it in the load process. > > I never stripped my kernels... And this is an ELF kernel from the 2nd and > it's still giving the notice after I installed the real new bootblocks... At > least that's what I am presuming since the whole system is ELF ;) Unless you have KERNFORMAT=elf set, your kernel is still a.out. More to the point, the message that you're seeing there comes from line 99 in sys/ddb/db_aout.c. So if you have an ELF kernel going, I'm not sure why that code is being run at all. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 12:59:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07089 for freebsd-current-outgoing; Sun, 3 Jan 1999 12:59:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dns.webwizard.net.mx (webwizard.net.mx [148.245.50.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07081 for ; Sun, 3 Jan 1999 12:59:43 -0800 (PST) (envelope-from eculp@webwizard.org.mx) Received: from webwizard.org.mx (webwizard.net.mx [148.245.50.27]) by dns.webwizard.net.mx (8.9.1/8.9.1) with ESMTP id OAA70179; Sun, 3 Jan 1999 14:59:11 -0600 (CST) (envelope-from eculp@webwizard.org.mx) Message-ID: <368FDA1E.7496D0CC@webwizard.org.mx> Date: Sun, 03 Jan 1999 14:59:11 -0600 From: Edwin Culp X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: jack CC: "freebsd-current@FreeBSD.ORG" Subject: Re: Disk space for a make release. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG jack wrote: > On Sun, 3 Jan 1999, Edwin Culp wrote: > > > I just tried to Make a Release with about 1.1 GB in my release partition > > and it ran out of space. Does anyone know how much is needed now? I > > That's more than enough. You probable copied your entire > /usr/ports/distfiles directory. Look in release/Makefile for > > # Set this to wherever the distfiles required by ${DOCPORTS} > live. > DISTFILES?= ${.CURDIR}/../../ports/distfiles > > and point that to some other directory that contains only the > sources needed by textproc/docproj. > > I'm told it's a feature. :) How dumb that makes me feel. Thanks for the tip, I never contemplated this feature:-). I'm making a new release now. 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 3 13:00:16 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA07176 for freebsd-current-outgoing; Sun, 3 Jan 1999 13:00:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles317.castles.com [208.214.167.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA07171 for ; Sun, 3 Jan 1999 13:00:14 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA07373; Sun, 3 Jan 1999 12:57:00 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901032057.MAA07373@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Dufault cc: current@FreeBSD.ORG Subject: Re: if_ep probe failures related to reading back settings In-reply-to: Your message of "Sat, 02 Jan 1999 09:09:42 EST." <199901021409.JAA18234@hda.hda.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 03 Jan 1999 12:56:59 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have trouble properly reading the settings back from a 3C509 on > a 180MHz Cyrix MediaGX crash box. The result is that it won't > always probe in at boot. > > I find that by increasing the DELAY by a factor of 10 and more > importantly adding a delay before reading each serial bit of data > (I assume we're reading back a serial EEPROM): ... > Can someone check if we may be violating timings on reading that > serial bus, or is it likely that this Cyrix has an inw that is too > fast and I have to monkey with some BIOS settings? If Bill Paul can't help you (I think he has the '509 documentation), then I would just bump the delays and be done with it. I don't see reading it too slowly as being a problem, and erring on the side of caution is always desirable. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 13:10:22 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08107 for freebsd-current-outgoing; Sun, 3 Jan 1999 13:10:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hda.hda.com (hda-bicnet.bicnet.net [209.244.238.132] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA08102 for ; Sun, 3 Jan 1999 13:10:20 -0800 (PST) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id QAA21190; Sun, 3 Jan 1999 16:06:23 -0500 (EST) From: Peter Dufault Message-Id: <199901032106.QAA21190@hda.hda.com> Subject: Re: if_ep probe failures related to reading back settings In-Reply-To: <199901032057.MAA07373@dingo.cdrom.com> from Mike Smith at "Jan 3, 99 12:56:59 pm" To: mike@smith.net.au (Mike Smith) Date: Sun, 3 Jan 1999 16:06:23 -0500 (EST) Cc: dufault@hda.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I have trouble properly reading the settings back from a 3C509 on > > a 180MHz Cyrix MediaGX crash box. The result is that it won't > > always probe in at boot. > > > > I find that by increasing the DELAY by a factor of 10 and more > > importantly adding a delay before reading each serial bit of data > > (I assume we're reading back a serial EEPROM): > ... > > Can someone check if we may be violating timings on reading that > > serial bus, or is it likely that this Cyrix has an inw that is too > > fast and I have to monkey with some BIOS settings? > > If Bill Paul can't help you (I think he has the '509 documentation), > then I would just bump the delays and be done with it. I don't see > reading it too slowly as being a problem, and erring on the side of > caution is always desirable. I could do that, but since this is the only ISA card I have on this thing and I'm unlikely to add any others it may not help anyone other than me and it may miss general problems with the Cyrix. I'll wait to hear if it makes sense that the delay be moved inside the loop. Then the "times 10" doesn't bother me one bit if it is used only during probe. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 13:11:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08155 for freebsd-current-outgoing; Sun, 3 Jan 1999 13:11:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from numeri.campus.luth.se (numeri.campus.luth.se [130.240.197.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA08147 for ; Sun, 3 Jan 1999 13:10:59 -0800 (PST) (envelope-from k@numeri.campus.luth.se) Received: from numeri.campus.luth.se (localhost [127.0.0.1]) by numeri.campus.luth.se (8.9.1/8.9.1) with ESMTP id WAA10101 for ; Sun, 3 Jan 1999 22:14:31 GMT (envelope-from k@numeri.campus.luth.se) Message-Id: <199901032214.WAA10101@numeri.campus.luth.se> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG Subject: PR conf/7705: Flags to rwhod in rc.* (before new branch) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 03 Jan 1999 22:14:31 +0000 From: Johan Karlsson Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Can someone please take a look at PR conf/7705 before the new branch in created. Since rwhod can use flags I think this patch should go into the tree. Please either apply the patch or explain to me why this should not be done. Either way close the PR. /Johan K New patches for current src as of Jan 2 1999 =============== *** src/etc/rc.conf.orig Sat Jan 2 21:31:56 1999 --- src/etc/rc.conf Sun Jan 3 21:42:56 1999 *************** *** 58,63 **** --- 58,64 ---- # a slave kerberos server kerberos_stash="" # Is the kerberos master key stashed? rwhod_enable="NO" # Run the rwho daemon (or NO). + rwhod_flags="" # Flags for rwhod amd_enable="NO" # Run amd service with $amd_flags (or NO). amd_flags="-a /net -c 1800 -k i386 -d my.domain -l syslog /host /etc/amd.map" amd_map_program="NO" # Can be set to "ypcat -k amd.master" *** src/etc/rc.network.orig Fri Nov 27 07:06:11 1998 --- src/etc/rc.network Sun Jan 3 21:43:25 1999 *************** *** 273,279 **** fi if [ "X${rwhod_enable}" = X"YES" ]; then ! echo -n ' rwhod'; rwhod fi # Kerberos runs ONLY on the Kerberos server machine --- 273,279 ---- fi if [ "X${rwhod_enable}" = X"YES" ]; then ! echo -n ' rwhod'; rwhod ${rwhod_flags} fi # Kerberos runs ONLY on the Kerberos server machine ============ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 13:14:50 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08347 for freebsd-current-outgoing; Sun, 3 Jan 1999 13:14:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dewdrop2.mindspring.com (dewdrop2.mindspring.com [207.69.200.82]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA08342 for ; Sun, 3 Jan 1999 13:14:49 -0800 (PST) (envelope-from brdean@mindspring.com) Received: from vger.foo.com (user-38ld95u.dialup.mindspring.com [209.86.164.190]) by dewdrop2.mindspring.com (8.8.5/8.8.5) with ESMTP id QAA11922; Sun, 3 Jan 1999 16:14:18 -0500 (EST) Received: (from bsd@localhost) by vger.foo.com (8.9.1/8.9.1) id QAA68859; Sun, 3 Jan 1999 16:13:12 -0500 (EST) (envelope-from bsd) From: Brian Dean Message-Id: <199901032113.QAA68859@vger.foo.com> Subject: Re: make release (almost) No space left on device In-Reply-To: <199901032043.MAA07228@dingo.cdrom.com> from Mike Smith at "Jan 3, 1999 12:43:50 pm" To: mike@smith.net.au (Mike Smith) Date: Sun, 3 Jan 1999 16:13:12 -0500 (EST) Cc: brdean@mindspring.com, jwd@unx.sas.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Maybe we can move to having a network installation floppy and a > > > disk media installation floppy... I personally do not want to see > > > a multidisk boot process. I've used it on other systems, and it > > > really hurts. > > > > I second this suggestion. > > > > Please avoid having a two (or more - ouch!) floppy install process. I > > typically install up to 30 machines at a time and a two floppy install > > will make this chore almost unbearable! > > We'll do what we can, but consider using a bootable CDROM instead of > floppies for your installs. Much faster. > > There's a limit to what we can pack onto a floppy, unfortunately. 8( I only use the floppy to boot. For the distribution media, I use NFS or FTP from a local server. I generate 30 or so boot floppies with a sysinstall configuration file for each system and boot them all in parallel. If I don't install the ports, I can usually be completely done with all of the machines in less than 40 minutes. A multiple floppy boot would throw this off quite a bit, and I could never do it in that amount of time by visiting each machine sequentially with a CDROM boot (and I can't reasonably burn 30 CD's). Every day you keep the single-floppy boot, you have my gratitude! -Brian -- Brian Dean brdean@mindspring.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 3 13:16:52 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08630 for freebsd-current-outgoing; Sun, 3 Jan 1999 13:16:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ozz.etrust.ru ([195.2.84.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA08619 for ; Sun, 3 Jan 1999 13:16:45 -0800 (PST) (envelope-from osa@etrust.ru) Received: from localhost (localhost [127.0.0.1]) by ozz.etrust.ru (8.9.1/8.9.1) with ESMTP id AAA00569; Mon, 4 Jan 1999 00:09:57 +0300 (MSK) (envelope-from osa@etrust.ru) Date: Mon, 4 Jan 1999 00:09:57 +0300 (MSK) From: oZZ!!! To: Matt Behrens cc: current@FreeBSD.ORG Subject: Re: How's the latest -SNAP? 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, 3 Jan 1999, Matt Behrens wrote: > As smoothly as aout-to-elf seems to be going along, I'm going to > be hitting the sysinstall freshly when I'm ready to move my main > machine to 3.0 in a couple weeks. (Reasoning is too long to go > into here, but they include more garbage than is worth tracking > down from ports that have misbehaved in the past and left files > strewn all about /usr/local as well as the need for a different > partitioning scheme to faciliate new hard drives I'm bringing in.) > > My questions are these: > > 1. Are the SNAPs fully ELF? all SNAPs after 3.0 in ELF > > 2. Are the new bootloaders used? yes & what do think when you say "new bootloaders"? > > 3. What is the shape of installing from the SNAP in general? Any > gotchas? > > TIA. (I couldn't find much from the archives.) > > - Matt "Zigg" Behrens > Network Administrator, zigg.com > Engineer, Nameless IRC Network > Rgdz, Osokin Sergey aka oZZ, osa@etrust.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 13:31:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09907 for freebsd-current-outgoing; Sun, 3 Jan 1999 13:31:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA09900 for ; Sun, 3 Jan 1999 13:31:28 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id NAA52511; Sun, 3 Jan 1999 13:30:53 -0800 (PST) (envelope-from dillon) Date: Sun, 3 Jan 1999 13:30:53 -0800 (PST) From: Matthew Dillon Message-Id: <199901032130.NAA52511@apollo.backplane.com> To: Brian Dean Cc: mike@smith.net.au (Mike Smith), brdean@mindspring.com, jwd@unx.sas.com, freebsd-current@FreeBSD.ORG Subject: Re: make release (almost) No space left on device References: <199901032113.QAA68859@vger.foo.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> > will make this chore almost unbearable! :> :> We'll do what we can, but consider using a bootable CDROM instead of :> floppies for your installs. Much faster. :> :> There's a limit to what we can pack onto a floppy, unfortunately. 8( : :I only use the floppy to boot. For the distribution media, I use NFS :or FTP from a local server. I generate 30 or so boot floppies with a :sysinstall configuration file for each system and boot them all in :parallel. If I don't install the ports, I can usually be completely :done with all of the machines in less than 40 minutes. A multiple :... : :-Brian :-- :Brian Dean brdean@mindspring.com I just disklabel a floppy, installing bootblocks on it (of course), then compile up a BOOTP kernel and throw it onto the floppy. I kzip the kernel on the floppy if necessary. Then I simply run dhcpd on my main server and NFS-export (read-only) / and /usr and adjust /etc/rc to notice a bootp boot and the a bootp-specific rc startup. Hell, I can even configure NFS based swap, though it requires exporting the swap files read+write. host test1 { hardware ethernet 00:a0:b0:d3:38:25; fixed-address 209.157.86.111; option root-path "209.157.86.62:/"; option option-128 "209.157.86.62:/images/swap"; } host test2 { hardware ethernet 00:e0:31:1d:16:09; fixed-address 209.157.86.112; option root-path "209.157.86.62:/"; option option-128 "209.157.86.62:/images/swap"; } apollo:/usr/src/sys# ls -la /images/swap total 229514 drwxr-xr-x 2 root wheel 512 Dec 28 07:00 . drwxr-xr-x 8 root wheel 512 Dec 26 18:58 .. -rw-r--r-- 1 lander wheel 33554432 Dec 23 14:35 swap.209.157.86.111 -rw-r--r-- 1 lander wheel 67108864 Jan 2 12:25 swap.209.157.86.112 -rw-r--r-- 1 lander wheel 134217728 Jan 2 03:26 swap.209.157.86.6 My bootp-specific rc script does general setup of the machine - mainly involving creating MFS filesystems for /dev, /home, /var/tmp, /var/db, /var/run, and so forth (I suppoes I could have just done /var), initializing the contents of those systems, and doing various other things. It also figures out the IP address of the machine and runs a machine-specific config. lander:/home/dillon> df Filesystem 1K-blocks Used Avail Capacity Mounted on 209.157.86.2:/ 63503 42613 15810 73% / 209.157.86.2:/usr 508143 315662 151830 68% /usr 209.157.86.2:/var 63503 11685 46738 20% /var 209.157.86.2:/images 1397423 434131 851499 34% /images mfs:31 959 72 811 8% /var/run mfs:33 7903 540 6731 7% /var/db mfs:35 31743 8 29196 0% /var/tmp mfs:37 31743 7 29197 0% /var/spool procfs 4 4 0 100% /proc mfs:57 1511 58 1333 4% /dev mfs:61 31743 1990 27214 7% /home lander:/home/dillon> The kernel configuration parameters necessary to do a BOOTP kernel are: options BOOTP # Use BOOTP to obtain IP address/hostname options BOOTP_NFSROOT # NFS mount root filesystem using BOOTP info options "BOOTP_NFSV3" # Use NFS v3 to NFS mount rootoptions options BOOTP_COMPAT # Workaround for broken bootp daemons. #options "BOOTP_WIRED_TO=xxx" #options NFS_NOSERVER #Disable the NFS-server code. options NFS #Network Filesystem options NFS_ROOT The only requirement is that the DHCPD server be on the same LAN as the machines you boot from it, since it uses a low level ethernet protocol to do its stuff. The coolest thing is that all the sophistication resides on my main server - the floppy has nothing on it but a kernel, so I can make changes to the booting sequence without having to rewrite the floppy. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 13:35:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10644 for freebsd-current-outgoing; Sun, 3 Jan 1999 13:35:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa16-34.ix.netcom.com [207.93.148.162]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA10639 for ; Sun, 3 Jan 1999 13:35:15 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.1/8.8.8) id NAA01739; Sun, 3 Jan 1999 13:34:26 -0800 (PST) (envelope-from tomdean) Date: Sun, 3 Jan 1999 13:34:26 -0800 (PST) Message-Id: <199901032134.NAA01739@ix.netcom.com> From: Thomas Dean To: mark@grondar.za CC: freebsd-current@FreeBSD.ORG Subject: Perl gv.h Problem Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am running an SMP -current system, as of yesterday. In bringing the system up-to-date, as aout, I encountered a problem. In doing a make world, and, when attempting to do make aout-to-elf, I had to use -DNOPERL to complete. Here is a log clip from the aout-to-elf make. I lost the output from make world, but, I believe it was the same. Is this a new problem? I can retry this, anytime. Thanks, tomdean ===> gnu/usr.bin/perl/perl install -c -s -o root -g wheel -m 555 perl /usr/bin /usr/bin/perl5 -> /usr/bin/perl /usr/bin/perl5.00502 -> /usr/bin/perl cd /usr/obj/aout/usr/src/gnu/usr.bin/perl/perl/ext/B ; make -B install \ INSTALLPRIVLIB=/usr/libdata/perl/5.00502 \ INSTALLARCHLIB=/usr/libdata/perl/5.00502/mach make: don't know how to make /usr/obj/aout/usr/src/gnu/usr.bin/perl/perl/gv.h. Stop *** Error code 2 Stop. *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 13:37:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10746 for freebsd-current-outgoing; Sun, 3 Jan 1999 13:37:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA10738 for ; Sun, 3 Jan 1999 13:37:34 -0800 (PST) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.9.2/8.9.2) with ESMTP id QAA33887; Sun, 3 Jan 1999 16:36:53 -0500 (EST) Date: Sun, 3 Jan 1999 16:36:52 -0500 (EST) From: jack To: Edwin Culp cc: "freebsd-current@FreeBSD.ORG" Subject: Re: Disk space for a make release. In-Reply-To: <368FDA1E.7496D0CC@webwizard.org.mx> Message-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, 3 Jan 1999, Edwin Culp wrote: > > and point that to some other directory that contains only the > > sources needed by textproc/docproj. > > > > I'm told it's a feature. :) > > How dumb that makes me feel. Thanks for the tip, I never contemplated this > feature:-). I'm making a new release now. I know _exactly_ how you feel, you weren't the first and probably won't be the last. Suggestion: Since we already have several ports using their own subdirectories under ports/distfiles, how about ports/distfiles/docproj? -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 13:59:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA12617 for freebsd-current-outgoing; Sun, 3 Jan 1999 13:59:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA12610 for ; Sun, 3 Jan 1999 13:59:03 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zwvXb-0002wo-00; Sun, 3 Jan 1999 14:58:31 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id OAA57593; Sun, 3 Jan 1999 14:56:31 -0700 (MST) Message-Id: <199901032156.OAA57593@harmony.village.org> To: Clark Gaylord Subject: Re: aha fix-thank you! Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Fri, 01 Jan 1999 15:25:25 EST." <199901012025.PAA00554@gaylord.async.vt.edu> References: <199901012025.PAA00554@gaylord.async.vt.edu> Date: Sun, 03 Jan 1999 14:56:31 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199901012025.PAA00554@gaylord.async.vt.edu> Clark Gaylord writes: : BTW, I have a 1542B, unknown firmware ... is there a FreeBSD util : for reading/loading firmware on these puppies? I recall there : being a DOS util, but I can't find that (though I suppose I can : probably get it from Adaptec's web site). Right now my drives are : <=1GB, but I will probably buy a 4GB soon and I'm not sure I have : the right firmware. I don't think so. Looking at the chips on my AHA-1542B leads me to believe that they are EPROMS that need UV light to erase and then a EPROM burner to reprogram. I think the <= 1G is only for booting and DOS. The driver uses low level scsi commands and thus is immune from the 1G limit. 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 3 14:03:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13065 for freebsd-current-outgoing; Sun, 3 Jan 1999 14:03:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hyperreal.org (taz.hyperreal.org [209.133.83.16]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA13058 for ; Sun, 3 Jan 1999 14:03:11 -0800 (PST) (envelope-from brian@hyperreal.org) Received: (qmail 3903 invoked by uid 24); 3 Jan 1999 22:02:47 -0000 Message-Id: <4.1.19990103134322.00bfa530@hyperreal.org> X-Sender: brian@hyperreal.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sun, 03 Jan 1999 13:44:02 -0800 To: "Jonathan M. Bresler" From: Brian Behlendorf Subject: Re: sendmail throughput (was: HEADS UP: Postfix is coming. new uid, gid required.) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <199901030324.TAA06170@hub.freebsd.org> References: <19990102055658.A5621@la.best.com> <199901011525.HAA22294@hub.freebsd.org> <19990102055658.A5621@la.best.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 07:24 PM 1/2/99 -0800, Jonathan M. Bresler wrote: > news seems to have even more flamage than the mailing lists. > with mail i can control spam, with news everyone would have to > control spam. Unless you run a localized newsserver. news://news.freebsd.org/ for example. Brian --=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-- History is made at night; brian@hyperreal.org character is what you are in the dark. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 14:15:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13732 for freebsd-current-outgoing; Sun, 3 Jan 1999 14:15:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.kar.net (n178.cdialup.kar.net [195.178.130.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13716; Sun, 3 Jan 1999 14:15:10 -0800 (PST) (envelope-from kushn@mail.kar.net) Received: from localhost (volodya@localhost) by mail.kar.net (8.9.1/8.8.8) with ESMTP id AAA34445; Mon, 4 Jan 1999 00:13:52 +0200 (EET) (envelope-from kushn@mail.kar.net) Date: Mon, 4 Jan 1999 00:13:51 +0200 (EET) From: Vladimir Kushnir X-Sender: volodya@kushnir.kiev.ua To: Wiliam Woods cc: FBSD_QUESTIONS , FBSD_CURRENT Subject: Re: pgcc-1.1.1 In-Reply-To: <005501be3737$d091d620$f301040a@c063.beaverton.stream.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, 3 Jan 1999, Wiliam Woods wrote: > Anyone here useing pgcc-1.1.1 as their compiler of choice, to replace gcc? I > have been debating playing with this on my "spare" system. > Any reports from someone useing this, good or bad? Not sure if I'd like to replace gcc, especially for kernel, but I'm using pgcc (both C, and C++, and g77) for userland here, mostly as a matter of speed-up (yep, I know that's not what egcs is intended for, but all the same some of us need fast code). Works fine. Only question: does anybody know why Linux cross-compiled (within emulation) code runs _much_ faster? > > Thanks, > > Bill > > Regards, Vladimir ===========================|======================= Vladimir Kushnir | kushn@mail.kar.net, | Powered by FreeBSD kushnir@ap3.bitp.kiev.ua | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 14:24:41 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14868 for freebsd-current-outgoing; Sun, 3 Jan 1999 14:24:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14783 for ; Sun, 3 Jan 1999 14:24:38 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id OAA71151; Sun, 3 Jan 1999 14:23:04 -0800 (PST) To: Vladimir Kushnir cc: Wiliam Woods , FBSD_CURRENT Subject: Re: pgcc-1.1.1 In-reply-to: Your message of "Mon, 04 Jan 1999 00:13:51 +0200." Date: Sun, 03 Jan 1999 14:23:03 -0800 Message-ID: <71148.915402183@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > same some of us need fast code). Works fine. Only question: does anybody > know why Linux cross-compiled (within emulation) code runs _much_ faster? 1. Please don't cross-post to both -current and -questions, whether you originated the cross-post or not. 2. Without any details, even speculating on this question is a meaningless exercise and a waste of time. What code? Compiled how? Etc. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 15:01:38 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA18892 for freebsd-current-outgoing; Sun, 3 Jan 1999 15:01:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA18886 for ; Sun, 3 Jan 1999 15:01:36 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id SAA05512 for ; Sun, 3 Jan 1999 18:01:10 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA13583; Sun, 3 Jan 1999 18:01:09 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id SAA14463; Sun, 3 Jan 1999 18:01:04 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199901032301.SAA14463@bb01f39.unx.sas.com> Subject: Re: make release (almost) No space left on device In-Reply-To: <199901032039.PAA68739@vger.foo.com> from Brian Dean at "Jan 3, 99 03:39:45 pm" To: freebsd-current@FreeBSD.ORG Date: Sun, 3 Jan 1999 18:01:04 -0500 (EST) Cc: brdean@unx.sas.com (Brian Dean) X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, In trying to figure out what grew too large... I've started getting confused. I modified doFS.sh to print out what is being copied onto the floppy... What I find is: + mount /dev/vn0c /mnt + [ -d /R/stage/boot.std ] + set -e + cd /R/stage/boot.std + find . -print . ./boot ./boot/boot0 ./boot/nb8390.rom ./boot/nb8390.com ./boot/nb3c509.rom ./boot/nb3c509.com ./boot/loader ./boot/fbsdboot.exe ./boot/cdboot ./boot/boot2 ./boot/boot1 ./boot/rawboot ./boot/boot.conf ./boot/loader.config ./boot.config ./kernel.gz ./boot.help ./kernel.config + set -e + cd /R/stage/boot.std + find+ cpio . -dump -print /mnt /mnt: write failed, file system is full cpio: write error: No space left on device *** Error code 1 Well, cdboot by itself is a major problem.... It seems to me we're not putting what we think we are onto the floppy... Either doFS.sh needs to be smarter, or someone is starting to populate the boot subdir with things that didn't used to be there... Comments? Critiques? Helpful clues? Thanks! John > Folks, > > > sh -e /usr/src/release/scripts/doFS.sh /R/stage /mnt 1440 /R/stage/boot.std 80000 fd1440 > > disklabel: ioctl DIOCWLABEL: Operation not supported by device > > /dev/rvn0c: 2880 sectors in 80 cylinders of 2 tracks, 18 sectors > > 1.4MB in 5 cyl groups (16 c/g, 0.28MB/g, 32 i/g) > > super-block backups (for fsck -b #) at: > > 32, 632, 1184, 1784, 2336, > > cpio: write error: No space left on device > > *** Error code 1 > > > > > > Maybe we can move to having a network installation floppy and a > > disk media installation floppy... I personally do not want to see > > a multidisk boot process. I've used it on other systems, and it > > really hurts. > > I second this suggestion. > > Please avoid having a two (or more - ouch!) floppy install process. I > typically install up to 30 machines at a time and a two floppy install > will make this chore almost unbearable! > > Thanks, > -Brian > -- > Brian Dean brdean@mindspring.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 3 15:22:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20516 for freebsd-current-outgoing; Sun, 3 Jan 1999 15:22:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-24-dbn.dial-up.net [196.34.155.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20506 for ; Sun, 3 Jan 1999 15:22:22 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id BAA01063; Mon, 4 Jan 1999 01:20:45 +0200 (SAT) From: Robert Nordier Message-Id: <199901032320.BAA01063@ceia.nordier.com> Subject: Re: make release (almost) No space left on device In-Reply-To: <199901032301.SAA14463@bb01f39.unx.sas.com> from "John W. DeBoskey" at "Jan 3, 99 06:01:04 pm" To: jwd@unx.sas.com (John W. DeBoskey) Date: Mon, 4 Jan 1999 01:20:43 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG, brdean@unx.sas.com X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id PAA20512 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John W. DeBoskey wrote: > In trying to figure out what grew too large... I've started getting > confused. I modified doFS.sh to print out what is being copied onto > the floppy... What I find is: > > + mount /dev/vn0c /mnt > + [ -d /R/stage/boot.std ] > + set -e > + cd /R/stage/boot.std > + find . -print > . ./boot ./boot/boot0 ./boot/nb8390.rom ./boot/nb8390.com ./boot/nb3c509.rom ./boot/nb3c509.com ./boot/loader ./boot/fbsdboot.exe ./boot/cdboot ./boot/boot2 ./boot/boot1 ./boot/rawboot ./boot/boot.conf ./boot/loader.config ./boot.config ./kernel.gz ./boot.help ./kernel.config + set -e > + cd /R/stage/boot.std > + find+ cpio . -dump -print /mnt > > > /mnt: write failed, file system is full > cpio: write error: No space left on device > *** Error code 1 > > > Well, cdboot by itself is a major problem.... It seems to me we're not > putting what we think we are onto the floppy... Either doFS.sh needs to > be smarter, or someone is starting to populate the boot subdir with > things that didn't used to be there... > > Comments? Critiques? Helpful clues? You may need to clean out your /boot directory. There was a brief period recently when the old boot code was installed to /boot by mistake; and a "make world" during that time would have populated it incorrectly. (See src/sys/i386/boot/Makefile.inc 1.4.) -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 15:27:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA21105 for freebsd-current-outgoing; Sun, 3 Jan 1999 15:27:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa17-35.ix.netcom.com [207.93.156.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA21100 for ; Sun, 3 Jan 1999 15:27:38 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.1/8.8.8) id PAA00422; Sun, 3 Jan 1999 15:26:47 -0800 (PST) (envelope-from tomdean) Date: Sun, 3 Jan 1999 15:26:47 -0800 (PST) Message-Id: <199901032326.PAA00422@ix.netcom.com> From: Thomas Dean To: mike@smith.net.au, rnordier@nordier.com CC: freebsd-current@FreeBSD.ORG Subject: aout-to-elf and bootblocks Success Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just completed an upgrade from a 9/1998 -current to 1/2/1999 elf -current. The new bootblocks work and the elf kernel works. Thanks to the core team for the hard work, and especially Mike Smith for all the help he gave me, and, to Robert Nordier for the bootblock help. tomdean ==================================================== The steps were: 1. Upgrade to the latest -current cvsup make world Note: I used make -DNOGAMES -DNOPERL world to save time and to get around a missing gv.h. I will look for this when I do the last make world. rebuild and install a new kernel 2. make -DNOGAMES -DNOPERL aout-to-elf Again, time and gv.h actually, I used aout-to-elf-build and aout-to-elf-install It would be nice if Makefile.upgrade told the world it was successful, after touching the /usr/obj/do* file. 3. reboot. 4. install the new bootblocks. cd /sys/boot make sure 'objformat' returns elf if necessary, setenv OBJFORMAT elf make all install disklabel -B -b /boot/boot1 -s /boot/boot2 da1 5. reboot 6. build a new kernel and install it cd /sys/compile/ make clean make KERNFORMAT=elf depend make KERNFORMAT=elf mv kernel kernel.elf install -c -m 555 -o root -g wheel -fschg kernel.elf / 7. reboot The first time through, I booted kernel reboot This time, I booted kernel.elf I can build and execute elf's. # g++ hello.cpp -o hello # file hello hello: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD),\ dynamically linked, not stripped I have 3 steps left, but, they should be easier. At least I understand these. 8. make world to be sure all the problems are out of the sources. 9. rebuild and install an elf kernel, to catch-up after 8. 10. rebuild all the ports and applications... to convert to elf. Are there any tools to catch all the ports that are installed and rebuild them? I planned to go through /var/db/pkg. There are some duplications, like XFree86-3.3.1 and XFree86-3.3.2. If I create a tool, based on /var/db/pkg or pkg_info, I will send it along. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 15:30:41 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA21570 for freebsd-current-outgoing; Sun, 3 Jan 1999 15:30:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from houcbs2.houabg.com (houabg.com [206.109.247.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA21565 for ; Sun, 3 Jan 1999 15:30:38 -0800 (PST) (envelope-from dchapman@houabg.com) Received: from sdn-ar-004txhousP268.dialsprint.net by houcbs2.houabg.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1457.7) id ZBAFFAZM; Sun, 3 Jan 1999 17:36:53 -0600 Message-ID: <368FFDD4.14E34657@houabg.com> Date: Sun, 03 Jan 1999 17:31:32 -0600 From: "David W. Chapman Jr." X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current Subject: Re: Advertisement References: 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 <368FD021.4C0CC43A@houabg.com>, "David W. Chapman Jr." wrote: > } Why would anyone in here want to listen to that crappy scam > > I don't know. Why would they want to listen to you complain about a > crappy scam? > > -- > Jon Hamilton > hamilton@pobox.com I don't know but I sure don't want to listen to you complain about me complaining. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 15:32:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA21800 for freebsd-current-outgoing; Sun, 3 Jan 1999 15:32:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.gtn.com (mail.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA21779 for ; Sun, 3 Jan 1999 15:32:01 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by mail.gtn.com (8.8.6/8.8.6) with UUCP id AAA01663 for current@FreeBSD.ORG; Mon, 4 Jan 1999 00:30:06 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.1/8.9.1) id AAA19995 for current@FreeBSD.ORG; Mon, 4 Jan 1999 00:29:36 +0100 (CET) (envelope-from andreas) Message-ID: <19990104002935.A19706@klemm.gtn.com> Date: Mon, 4 Jan 1999 00:29:35 +0100 From: Andreas Klemm To: current@FreeBSD.ORG Subject: boot.flp not bootable, kernel missing ? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ! Did a make release and burned a FreeBSD cd-rom from /disk2/release/R/cdrom/disc1 subdir. BTW, didn't build doc and ports ... Created a bootfloppy, used the boot.flp disc image. The floppy isn't bootable... First message that looks strange: No /boot/loader [...] Examples: [...] boot: No /kernel >> FreeBSD/i386 BOOT Default: 0:fd(0,a)/kernel boot: ? . .. boot.help boot.config kernel.config >> FreeBSD/i386 BOOT Default: 0:fd(0,a)/kernel boot: Looks like the floppy isn't complete ... -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 15:32:52 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA21924 for freebsd-current-outgoing; Sun, 3 Jan 1999 15:32:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA21915 for ; Sun, 3 Jan 1999 15:32:50 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id PAA71644; Sun, 3 Jan 1999 15:32:20 -0800 (PST) To: "John W. DeBoskey" cc: freebsd-current@FreeBSD.ORG, brdean@unx.sas.com (Brian Dean) Subject: Re: make release (almost) No space left on device In-reply-to: Your message of "Sun, 03 Jan 1999 18:01:04 EST." <199901032301.SAA14463@bb01f39.unx.sas.com> Date: Sun, 03 Jan 1999 15:32:20 -0800 Message-ID: <71640.915406340@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ./boot/nb8390.rom > ./boot/nb8390.com > ./boot/nb3c509.rom > ./boot/nb3c509.com Interesting. This must have been a transitory effect of one of my backed-out changes to Makefile.inc. It's certainly not this full in my own SNAP release directory here. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 15:35:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA22085 for freebsd-current-outgoing; Sun, 3 Jan 1999 15:35:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA22080 for ; Sun, 3 Jan 1999 15:35:05 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id SAA08770; Sun, 3 Jan 1999 18:34:20 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA15067; Sun, 3 Jan 1999 18:34:19 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id SAA14543; Sun, 3 Jan 1999 18:34:09 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199901032334.SAA14543@bb01f39.unx.sas.com> Subject: Re: make release (almost) No space left on device In-Reply-To: <199901032320.BAA01063@ceia.nordier.com> from Robert Nordier at "Jan 4, 99 01:20:43 am" To: rnordier@nordier.com (Robert Nordier) Date: Sun, 3 Jan 1999 18:34:09 -0500 (EST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > > > Well, cdboot by itself is a major problem.... It seems to me we're not > > putting what we think we are onto the floppy... Either doFS.sh needs to > > be smarter, or someone is starting to populate the boot subdir with > > things that didn't used to be there... > > > > Comments? Critiques? Helpful clues? > > You may need to clean out your /boot directory. There was a brief > period recently when the old boot code was installed to /boot by > mistake; and a "make world" during that time would have populated it > incorrectly. (See src/sys/i386/boot/Makefile.inc 1.4.) > > -- > Robert Nordier This is from a 'make release'. It is built from scratch everyday. My sources are current for this build as of 2am Sunday morning EST. Also, this didn't fail like this on Saturday's 'make release'. Thanks, John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 15:48:53 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA23398 for freebsd-current-outgoing; Sun, 3 Jan 1999 15:48:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.kar.net (n178.cdialup.kar.net [195.178.130.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA23387 for ; Sun, 3 Jan 1999 15:48:39 -0800 (PST) (envelope-from kushn@mail.kar.net) Received: from localhost (volodya@localhost) by mail.kar.net (8.9.1/8.8.8) with ESMTP id BAA38788; Mon, 4 Jan 1999 01:47:22 +0200 (EET) (envelope-from kushn@mail.kar.net) Date: Mon, 4 Jan 1999 01:47:22 +0200 (EET) From: Vladimir Kushnir X-Sender: volodya@kushnir.kiev.ua To: "Jordan K. Hubbard" cc: FBSD_CURRENT Subject: Re: pgcc-1.1.1 In-Reply-To: <71148.915402183@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 3 Jan 1999, Jordan K. Hubbard wrote: > > same some of us need fast code). Works fine. Only question: does anybody > > know why Linux cross-compiled (within emulation) code runs _much_ faster? > > 1. Please don't cross-post to both -current and -questions, whether you > originated the cross-post or not. > Sorry for cross-posting - it wasn't intended. My fault. > 2. Without any details, even speculating on this question is a meaningless > exercise and a waste of time. What code? Compiled how? Etc. Just an example: parts of the BYTE benchmark (nbench) compiled with pgcc-1.1.1 from ports collection (first) and with pgcc-1.1-1.i586.rpm for glibc (second): Native FreeBSD pgcc: /usr/local/bin/nbench: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), statically linked, stripped BYTEmark* Native Mode Benchmark ver. 2 (10/95) Index-split by Andrew D. Balsa (11/97) Linux/Unix* port by Uwe F. Mayer (12/96,11/97) TEST : Iterations/sec. : Old Index : New Index : : Pentium 90* : AMD K6/233* --------------------:------------------:-------------:------------ NUMERIC SORT : 46.961 : 1.20 : 0.40 STRING SORT : 2.4854 : 1.11 : 0.17 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ BITFIELD : 6.3344e+06 : 1.09 : 0.23 FP EMULATION : 2.721 : 1.31 : 0.30 FOURIER : 663.85 : 0.75 : 0.42 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ASSIGNMENT : 0.40413 : 1.54 : 0.40 IDEA : 59.795 : 0.91 : 0.27 HUFFMAN : 37.112 : 1.03 : 0.33 NEURAL NET : 0.69246 : 1.11 : 0.47 Part of Linux pgcc: file nbench nbench: ELF 32-bit LSB executable, Intel 80386, version 1 (Linux), statically linked, stripped BYTEmark* Native Mode Benchmark ver. 2 (10/95) Index-split by Andrew D. Balsa (11/97) Linux/Unix* port by Uwe F. Mayer (12/96,11/97) TEST : Iterations/sec. : Old Index : New Index : : Pentium 90* : AMD K6/233* --------------------:------------------:-------------:------------ NUMERIC SORT : 46.744 : 1.20 : 0.39 STRING SORT : 3.4938 : 1.56 : 0.24 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ BITFIELD : 6.3761e+06 : 1.09 : 0.23 FP EMULATION : 2.794 : 1.34 : 0.31 FOURIER : 1143.7 : 1.30 : 0.73 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For some reason (can't say yet why) here Linux binary stopped, but pls note an that while most of the benchmarks are of the same value, in some cases (underlined values here) linux binary runs essentially faster. Besides, I had more or less the same experience with g77 (can't provide with precise numbers now, but sometimes difference was around 20-30%). Could it be that there're some linux specific optimizations that we don't use? > > - Jordan > > Regards, Vladimir ===========================|======================= Vladimir Kushnir | kushn@mail.kar.net, | Powered by FreeBSD kushnir@ap3.bitp.kiev.ua | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 15:52:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA23884 for freebsd-current-outgoing; Sun, 3 Jan 1999 15:52:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.kar.net (n178.cdialup.kar.net [195.178.130.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA23871 for ; Sun, 3 Jan 1999 15:52:07 -0800 (PST) (envelope-from kushn@mail.kar.net) Received: from localhost (volodya@localhost) by mail.kar.net (8.9.1/8.8.8) with ESMTP id BAA38803 for ; Mon, 4 Jan 1999 01:51:37 +0200 (EET) (envelope-from kushn@mail.kar.net) Date: Mon, 4 Jan 1999 01:51:36 +0200 (EET) From: Vladimir Kushnir X-Sender: volodya@kushnir.kiev.ua To: FBSD_CURRENT Subject: Re: pgcc-1.1.1 Message-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, 3 Jan 1999, Jordan K. Hubbard wrote: > > same some of us need fast code). Works fine. Only question: does anybody > > know why Linux cross-compiled (within emulation) code runs _much_ faster? > > 1. Please don't cross-post to both -current and -questions, whether you > originated the cross-post or not. > Sorry for cross-posting - it wasn't intended. My fault. > 2. Without any details, even speculating on this question is a meaningless > exercise and a waste of time. What code? Compiled how? Etc. Just an example: parts of the BYTE benchmark (nbench) compiled with pgcc-1.1.1 from ports collection (first) and with pgcc-1.1-1.i586.rpm for glibc (second). Compilation options from the port: CFLAGS = -s -static -Wall -O3 Native FreeBSD pgcc: /usr/local/bin/nbench: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), statically linked, stripped BYTEmark* Native Mode Benchmark ver. 2 (10/95) Index-split by Andrew D. Balsa (11/97) Linux/Unix* port by Uwe F. Mayer (12/96,11/97) TEST : Iterations/sec. : Old Index : New Index : : Pentium 90* : AMD K6/233* --------------------:------------------:-------------:------------ NUMERIC SORT : 46.961 : 1.20 : 0.40 STRING SORT : 2.4854 : 1.11 : 0.17 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ BITFIELD : 6.3344e+06 : 1.09 : 0.23 FP EMULATION : 2.721 : 1.31 : 0.30 FOURIER : 663.85 : 0.75 : 0.42 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ASSIGNMENT : 0.40413 : 1.54 : 0.40 IDEA : 59.795 : 0.91 : 0.27 HUFFMAN : 37.112 : 1.03 : 0.33 NEURAL NET : 0.69246 : 1.11 : 0.47 Part of Linux pgcc: file nbench nbench: ELF 32-bit LSB executable, Intel 80386, version 1 (Linux), statically linked, stripped BYTEmark* Native Mode Benchmark ver. 2 (10/95) Index-split by Andrew D. Balsa (11/97) Linux/Unix* port by Uwe F. Mayer (12/96,11/97) TEST : Iterations/sec. : Old Index : New Index : : Pentium 90* : AMD K6/233* --------------------:------------------:-------------:------------ NUMERIC SORT : 46.744 : 1.20 : 0.39 STRING SORT : 3.4938 : 1.56 : 0.24 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ BITFIELD : 6.3761e+06 : 1.09 : 0.23 FP EMULATION : 2.794 : 1.34 : 0.31 FOURIER : 1143.7 : 1.30 : 0.73 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For some reason (can't say yet why) here Linux binary stopped, but pls note an that while most of the benchmarks are of the same value, in some cases (underlined values here) linux binary runs essentially faster. Besides, I had more or less the same experience with g77 (can't provide with precise numbers now, but sometimes difference was around 20-30%). Could it be that there're some linux specific optimizations that we don't use? > > - Jordan > > Regards, Vladimir ===========================|======================= Vladimir Kushnir | kushn@mail.kar.net, | Powered by FreeBSD kushnir@ap3.bitp.kiev.ua | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 16:04:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA25826 for freebsd-current-outgoing; Sun, 3 Jan 1999 16:04:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from houcbs2.houabg.com (houabg.com [206.109.247.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA25809 for ; Sun, 3 Jan 1999 16:04:05 -0800 (PST) (envelope-from dchapman@houabg.com) Received: from sdn-ar-004txhousP268.dialsprint.net by houcbs2.houabg.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1457.7) id ZBAFFAZ7; Sun, 3 Jan 1999 18:10:21 -0600 Message-ID: <369005AD.FC440AAC@houabg.com> Date: Sun, 03 Jan 1999 18:05:01 -0600 From: "David W. Chapman Jr." X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current Subject: Wine-Latest Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anyone been able to compile the latest version of wine with egcs-1.1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 16:35:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA00419 for freebsd-current-outgoing; Sun, 3 Jan 1999 16:35:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA00414 for ; Sun, 3 Jan 1999 16:35:17 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id JAA01193; Mon, 4 Jan 1999 09:34:51 +0900 (JST) Message-ID: <36900AE7.FB3AD249@newsguy.com> Date: Mon, 04 Jan 1999 09:27:19 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: FICL & Perl Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any interest in getting rid of the perl script in the ficl build? It is a very legible script indeed, but not being able to set NOPERL is quite a nuisance for me. (As a bonus, my alternative doesn't have a small bug in Mr. Sadler's script :). -- Daniel C. Sobral (8-DCS) dcs@newsguy.com "Heart like a Gabriel, pure and white as ivory, soul like a lucifer, black and cold as a piece of lead." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 16:38:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA00897 for freebsd-current-outgoing; Sun, 3 Jan 1999 16:38:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sicily.odyssey.cs.cmu.edu (SICILY.ODYSSEY.CS.CMU.EDU [128.2.185.138]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA00889 for ; Sun, 3 Jan 1999 16:38:10 -0800 (PST) (envelope-from rvb+@sicily.odyssey.cs.cmu.edu) To: current@FreeBSD.ORG Subject: New boot blocks for serial console ... From: "Robert V. Baron" Date: 03 Jan 1999 19:37:13 -0500 Message-ID: Lines: 29 X-Mailer: Gnus v5.4.46/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You've forced me to use the new scheme. I have a laptop with the serial line on com2(0x2f8) and use 56700 baud. A long time ago I built a boot1/boot2 to do this. In seems that things have changed in the new scheme. It looks like that in sys/boot/i386/Makefile, I need to change: B2SIOPRT?= 0x3f8 B2SIOFMT?= 0x3 B2SIODIV?= 0xc to B2SIOPRT?= 0x2f8 B2SIOFMT?= 0x3 B2SIODIV?= 0x2 This is a bit cryptic and could use a comment or two. But there are more loaders today. It looks like sys/boot/i386/libi386/comconsole.c needs to be handed edited: #define COMPORT 0x3f8 #define COMSPEED 9600 to #define COMPORT 0x2f8 #define COMSPEED 57600 I guess that this should be pulled out to the makefile building the lib. The two files above are the only ones that contain "3f8" so I guess that nothing else needs to be changed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 16:42:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01393 for freebsd-current-outgoing; Sun, 3 Jan 1999 16:42:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail4.aracnet.com (mail4.aracnet.com [205.159.88.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA01385 for ; Sun, 3 Jan 1999 16:42:30 -0800 (PST) (envelope-from ctapang@easystreet.com) Received: from apex (216-99-199-226.cust.aracnet.com [216.99.199.226]) by mail4.aracnet.com (8.9.1/8.9.0) with SMTP id QAA03726 for ; Sun, 3 Jan 1999 16:42:06 -0800 Message-ID: <004001be3783$35dcf870$0d787880@apex.tapang> From: "Carlos C. Tapang" To: Subject: Re: aout-to-elf and bootblocks Success Date: Sun, 3 Jan 1999 17:40:29 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Same here. I upgraded from RELENG_3_0_0_RELEASE (the cd 3.0 release) to a cvsup done on 1/1/1999. It works, but see below. (I've worked in large commercial software projects, and your accomplishments here make me somewhat embarrassed to have been paid so well. I know that for some of you this is "just a hobby" you love to do.) Carlos C. Tapang http://www.genericwindows.com >I just completed an upgrade from a 9/1998 -current to 1/2/1999 elf >-current. The new bootblocks work and the elf kernel works. > >Thanks to the core team for the hard work, and especially Mike Smith >for all the help he gave me, and, to Robert Nordier for the bootblock >help. > >tomdean > >==================================================== > >The steps were: > >1. Upgrade to the latest -current > cvsup > make world > Note: I used make -DNOGAMES -DNOPERL world to save time and > to get around a missing gv.h. I will look for this > when I do the last make world. Another note: make sure you already have Perl installed. If you don't, and you use NOPERL, then compilation of ficl fails. > rebuild and install a new kernel > >2. make -DNOGAMES -DNOPERL aout-to-elf > Again, time and gv.h > actually, I used aout-to-elf-build and aout-to-elf-install > It would be nice if Makefile.upgrade told the world it was > successful, after touching the /usr/obj/do* file. > >3. reboot. > >4. install the new bootblocks. > cd /sys/boot > make sure 'objformat' returns elf > if necessary, setenv OBJFORMAT elf > make all install > disklabel -B -b /boot/boot1 -s /boot/boot2 da1 This was the most tricky part. There's no way to tell that what you really have in /boot are the elf capable boot blocks. Test it first on a floppy. In my case, I disklabeled a floppy and pointed boot.config to 1:da(0,a)kernel because my elf kernel is in my SCSI drive. > >5. reboot > >6. build a new kernel and install it > cd /sys/compile/ > make clean > make KERNFORMAT=elf depend > make KERNFORMAT=elf > mv kernel kernel.elf > install -c -m 555 -o root -g wheel -fschg kernel.elf / My kernel would not fit in a floppy, so I could not test this first using a floppy. But I was able to try the 3 stage boot using boot/loader. > >7. reboot > The first time through, I booted kernel > reboot > This time, I booted kernel.elf > >I can build and execute elf's. ># g++ hello.cpp -o hello ># file hello >hello: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD),\ > dynamically linked, not stripped > >I have 3 steps left, but, they should be easier. At least I >understand these. > >8. make world to be sure all the problems are out of the sources. > >9. rebuild and install an elf kernel, to catch-up after 8. > >10. rebuild all the ports and applications... to convert to elf. > Are there any tools to catch all the ports that are installed > and rebuild them? I planned to go through /var/db/pkg. There > are some duplications, like XFree86-3.3.1 and XFree86-3.3.2. > If I create a tool, based on /var/db/pkg or pkg_info, I will > send it along. > >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 3 16:46:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01716 for freebsd-current-outgoing; Sun, 3 Jan 1999 16:46:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA01694; Sun, 3 Jan 1999 16:46:16 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id BAA21303; Mon, 4 Jan 1999 01:45:46 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id BAA02197; Mon, 4 Jan 1999 01:45:45 +0100 (MET) Message-ID: <19990104014545.E88411@follo.net> Date: Mon, 4 Jan 1999 01:45:45 +0100 From: Eivind Eklund To: "Daniel C. Sobral" Cc: hackers@FreeBSD.ORG Subject: Re: FICL & Perl References: <36900AE7.FB3AD249@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <36900AE7.FB3AD249@newsguy.com>; from Daniel C. Sobral on Mon, Jan 04, 1999 at 09:27:19AM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm moving this to -hackers where it belong. -current is getting TWICE THE FREAKING TRAFFIC of -hackers these days. On Mon, Jan 04, 1999 at 09:27:19AM +0900, Daniel C. Sobral wrote: > Is there any interest in getting rid of the perl script in the ficl > build? It is a very legible script indeed, but not being able to set > NOPERL is quite a nuisance for me. (As a bonus, my alternative > doesn't have a small bug in Mr. Sadler's script :). Depends on the size and clarity of the replacement. Be aware that we use perl5 in other parts of the build process, too - e.g, the device config generation in the kernel build. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 16:46:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01751 for freebsd-current-outgoing; Sun, 3 Jan 1999 16:46:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles317.castles.com [208.214.167.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA01745 for ; Sun, 3 Jan 1999 16:46:34 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA08542; Sun, 3 Jan 1999 16:43:24 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901040043.QAA08542@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Carlos C. Tapang" cc: freebsd-current@FreeBSD.ORG Subject: Re: aout-to-elf and bootblocks Success In-reply-to: Your message of "Sun, 03 Jan 1999 17:40:29 PST." <004001be3783$35dcf870$0d787880@apex.tapang> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 03 Jan 1999 16:43:23 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >1. Upgrade to the latest -current > > cvsup > > make world > > Note: I used make -DNOGAMES -DNOPERL world to save time and > > to get around a missing gv.h. I will look for this > > when I do the last make world. > > Another note: make sure you already have Perl installed. If you don't, and > you use NOPERL, then compilation of ficl fails. We've had requests to deal with this; I'm trying to come up with a workaround, as there are a couple of places at the moment where the bootstrap really needs Perl around (generating the helpfile is another one). > >6. build a new kernel and install it > > cd /sys/compile/ > > make clean > > make KERNFORMAT=elf depend > > make KERNFORMAT=elf > > mv kernel kernel.elf > > install -c -m 555 -o root -g wheel -fschg kernel.elf / > > My kernel would not fit in a floppy, so I could not test this first using a > floppy. But I was able to try the 3 stage boot using boot/loader. The loader will happily load a 'kernel.gz' file if asked to boot 'kernel' and the latter doesn't exist. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 16:56:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02628 for freebsd-current-outgoing; Sun, 3 Jan 1999 16:56:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pinhead.parag.codegen.com (ppp-sfx201--082.sirius.net [205.134.235.82]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA02620 for ; Sun, 3 Jan 1999 16:56:06 -0800 (PST) (envelope-from parag@cgt.com) Received: from pinhead.parag.codegen.com (localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.9.1/8.8.8) with ESMTP id QAA21093 for ; Sun, 3 Jan 1999 16:55:12 -0800 (PST) (envelope-from parag@pinhead.parag.codegen.com) Message-Id: <199901040055.QAA21093@pinhead.parag.codegen.com> To: freebsd-current@FreeBSD.ORG Subject: 3.0-CURRENT CAM vs scanner problems X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm X-URL: http://www.codegen.com Date: Sun, 03 Jan 1999 16:55:12 -0800 From: Parag Patel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am getting errors like these from the CAM subsystem when I try to scan a rather small image using GIMP and the SANE 1.0 port and my UMAX: cam_periph_mapmem: attempt to map 130851 bytes, which is greater than DFLTPHYS(65536) cam_periph_mapmem: attempt to map 130820 bytes, which is greater than DFLTPHYS(65536) cam_periph_mapmem: attempt to map 131016 bytes, which is greater than DFLTPHYS(65536) cam_periph_mapmem: attempt to map 129444 bytes, which is greater than DFLTPHYS(65536) cam_periph_mapmem: attempt to map 131029 bytes, which is greater than DFLTPHYS(65536) The scan does not succeed in either lineart, gray, or color modes, although the preview does. The comment in cam/cam_periph.c implies that the DFLTPHYS should be MAXPHYS but perhaps the comment is wrong? Or perhaps SANE should be using DFLTPHYS instead of MAXPHYS? For now, I added a patch to the sane-1.0 sanei/sanei_scsi.c file to use DFLTPHYS instead of MAXPHYS, and it is scanning nicely. Still, I don't know if it's a SANE bug or a CAM bug and so don't who to report it to. Thanks in advance. -- Parag Patel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 16:59:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02953 for freebsd-current-outgoing; Sun, 3 Jan 1999 16:59:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail4.aracnet.com (mail4.aracnet.com [205.159.88.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA02946; Sun, 3 Jan 1999 16:59:24 -0800 (PST) (envelope-from ctapang@easystreet.com) Received: from apex (216-99-199-226.cust.aracnet.com [216.99.199.226]) by mail4.aracnet.com (8.9.1/8.9.0) with SMTP id QAA04416; Sun, 3 Jan 1999 16:59:01 -0800 Message-ID: <004801be3785$92b11750$0d787880@apex.tapang> From: "Carlos C. Tapang" To: Cc: Subject: Fix for PR #i386/8567 Date: Sun, 3 Jan 1999 17:57:23 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A couple of months ago I submitted a fix for the Intel Pro/10+ driver. I just noticed that the fix has not been committed yet. I cvsupped 1.13 of this driver, and here is the diff between that and my version of the driver. This version will correctly distinguish between Pro/10 and Pro/10+. If you have a Pro/10, please let me know if it worked for you. Carlos C. Tapang http://www.genericwindows.com ps. There are 2 diffs. One for if_ex.c and another for if_exreg.h --------------------------------------- Index: if_ex.c =================================================================== RCS file: /usr/CVSROOT/src/sys/i386/isa/if_ex.c,v retrieving revision 1.13 diff -c -r1.13 if_ex.c *** if_ex.c 1998/10/22 05:58:39 1.13 --- if_ex.c 1999/01/03 15:36:57 *************** *** 23,30 **** * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. - * - * $Id: if_ex.c,v 1.13 1998/10/22 05:58:39 bde Exp $ */ /* --- 23,28 ---- *************** *** 43,57 **** --- 41,63 ---- #include #include + #include #include + #include #include #include #include + #include #include + #include + #include #ifdef INET #include + #include + #include + #include #include #endif *************** *** 67,72 **** --- 73,79 ---- #if NBPFILTER > 0 #include + #include #endif #include *************** *** 93,98 **** --- 100,106 ---- struct ex_softc { struct arpcom arpcom; /* Ethernet common data */ u_int iobase; /* I/O base address. */ + u_short chip_stepping; /* either TX or FX (FX is used in Pro/10+) */ u_short connector; /* Connector type. */ u_short irq_no; /* IRQ number. */ char *irq2ee; /* irq <-> internal representation conversion */ *************** *** 187,192 **** --- 195,204 ---- outb(iobase + CMD_REG, Reset_CMD); DELAY(400); + outb(iobase + CMD_REG, Bank2_Sel); + tmp = inb(iobase + EEPROM_REG); + sc->chip_stepping = (tmp & i82595_Stepping) >> 5; + /* * Fill in several fields of the softc structure: * - I/O base address. *************** *** 207,215 **** tmp = eeprom_read(iobase, EE_IRQ_No) & IRQ_No_Mask; /* work out which set of irq <-> internal tables to use */ ! if (sc->arpcom.ac_enaddr[0] == 0x00 && ! sc->arpcom.ac_enaddr[1] == 0xA0 && ! sc->arpcom.ac_enaddr[2] == 0xC9) { /* it's a 10+ */ sc->irq2ee = plus_irq2eemap; sc->ee2irq = plus_ee2irqmap; } else { /* it's an ordinary 10 */ --- 219,225 ---- tmp = eeprom_read(iobase, EE_IRQ_No) & IRQ_No_Mask; /* work out which set of irq <-> internal tables to use */ ! if (sc->chip_stepping >= FX_Stepping) { /* it's a Pro/10 Plus */ sc->irq2ee = plus_irq2eemap; sc->ee2irq = plus_ee2irqmap; } else { /* it's an ordinary 10 */ *************** *** 277,288 **** if_attach(ifp); ether_ifattach(ifp); ! if (sc->arpcom.ac_enaddr[0] == 0x00 && ! sc->arpcom.ac_enaddr[1] == 0xA0 && ! sc->arpcom.ac_enaddr[2] == 0xC9) { ! printf("ex%d: Intel EtherExpress Pro/10+, address %6D, connector ", dev->id_unit, sc->arpcom.ac_enaddr, ":"); } else { ! printf("ex%d: Intel EtherExpress Pro/10, address %6D, connector ", dev->id_unit, sc->arpcom.ac_enaddr, ":"); } switch(sc->connector) { case Conn_TPE: printf("TPE\n"); break; --- 287,296 ---- if_attach(ifp); ether_ifattach(ifp); ! if (sc->chip_stepping >= FX_Stepping) { ! printf("ex%d: Intel EtherExpr Pro/10+, address %6D, step %d, connector ", dev->id_unit, sc->arpcom.ac_enaddr, ":", sc->chip_stepping); } else { ! printf("ex%d: Intel EtherExpress Pro/10, address %6D, step %d, connector ", dev->id_unit, sc->arpcom.ac_enaddr, ":", sc->chip_stepping); } switch(sc->connector) { case Conn_TPE: printf("TPE\n"); break; Index: if_exreg.h =================================================================== RCS file: /usr/CVSROOT/src/sys/i386/isa/if_exreg.h,v retrieving revision 1.1 diff -c -r1.1 if_exreg.h *** if_exreg.h 1997/01/16 12:19:21 1.1 --- if_exreg.h 1999/01/03 02:12:43 *************** *** 121,126 **** --- 121,128 ---- #define I_ADDR_REG0 4 #define EEPROM_REG 10 #define Trnoff_Enable 0x10 + #define i82595_Stepping 0xE0 + #define FX_Stepping 4 /* EEPROM memory positions (16-bit wide). */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 17:06:02 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA03436 for freebsd-current-outgoing; Sun, 3 Jan 1999 17:06:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA03430; Sun, 3 Jan 1999 17:06:01 -0800 (PST) (envelope-from jmb) Date: Sun, 3 Jan 1999 17:06:01 -0800 (PST) Message-Id: <199901040106.RAA03430@hub.freebsd.org> From: "Jonathan M. Bresler" To: brian@hyperreal.org CC: freebsd-current@FreeBSD.ORG In-reply-to: <4.1.19990103134322.00bfa530@hyperreal.org> (message from Brian Behlendorf on Sun, 03 Jan 1999 13:44:02 -0800) Subject: Re: sendmail throughput (was: HEADS UP: Postfix is coming. new uid, gid required.) References: <19990102055658.A5621@la.best.com> <199901011525.HAA22294@hub.freebsd.org> <19990102055658.A5621@la.best.com> <4.1.19990103134322.00bfa530@hyperreal.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > X-Sender: brian@hyperreal.org > Date: Sun, 03 Jan 1999 13:44:02 -0800 > From: Brian Behlendorf > Cc: freebsd-current@FreeBSD.ORG > Content-Type: text/plain; charset="us-ascii" > > At 07:24 PM 1/2/99 -0800, Jonathan M. Bresler wrote: > > news seems to have even more flamage than the mailing lists. > > with mail i can control spam, with news everyone would have to > > control spam. > > Unless you run a localized newsserver. news://news.freebsd.org/ for example. all news servers would hvae to send all news to news://news.freebsd.org/ and only news://news.freebsd.org/ would be allowed to send news to any other site......there's that bottleneck again....now it'll be larger quantities of news (rather than mail) less frequently. perhaps i have misunderstood. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 17:10:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA04055 for freebsd-current-outgoing; Sun, 3 Jan 1999 17:10:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA04030 for ; Sun, 3 Jan 1999 17:10:24 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (doconnor@lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA23731; Mon, 4 Jan 1999 11:39:25 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199901040055.QAA21093@pinhead.parag.codegen.com> Date: Mon, 04 Jan 1999 11:49:36 +1030 (CST) From: "Daniel O'Connor" To: Parag Patel Subject: RE: 3.0-CURRENT CAM vs scanner problems Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 04-Jan-99 Parag Patel wrote: > cam_periph_mapmem: attempt to map 131029 bytes, which is greater than DFLTPHYS(65536) > > The scan does not succeed in either lineart, gray, or color modes, > although the preview does. > > The comment in cam/cam_periph.c implies that the DFLTPHYS should be > MAXPHYS but perhaps the comment is wrong? Or perhaps SANE should be > using DFLTPHYS instead of MAXPHYS? > > For now, I added a patch to the sane-1.0 sanei/sanei_scsi.c file to use > DFLTPHYS instead of MAXPHYS, and it is scanning nicely. Still, I don't > know if it's a SANE bug or a CAM bug and so don't who to report it to. There is a problem with CAM if you try to share data >64k in size (ie cdrecord ring buffer, and cdda2wav ring buffer) so it has been limited to prevent crashes.. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 17:15:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA04301 for freebsd-current-outgoing; Sun, 3 Jan 1999 17:15:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cbgw1.lucent.com (cbgw1.lucent.com [207.24.196.51]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA04296 for ; Sun, 3 Jan 1999 17:15:23 -0800 (PST) (envelope-from dmobrien@cbgw1.lucent.com) Cc: Eric Chet Received: from llama.bazzle.com by cbig1.firewall.lucent.com (SMI-8.6/EMS-L sol2) id UAA00759; Sun, 3 Jan 1999 20:12:11 -0500 Received: from localhost (dob@localhost) by llama.bazzle.com (8.9.1/8.6.12) with SMTP id UAA00394; Sun, 3 Jan 1999 20:14:45 -0500 (EST) X-Authentication-Warning: llama.bazzle.com: dob owned process doing -bs Date: Sun, 3 Jan 1999 20:14:44 -0500 (EST) From: "Dan O'Brien" X-Sender: dmobrien@localhost To: current@FreeBSD.ORG Original-cc: Eric Chet Subject: ELF at last! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With some handholding (thanks, EricC!) and a fresh cvsup from this AM (1/3), I'm now totally Elf from an aout system last built on July 12th. /home/dob: file /kernel /kernel: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), dynamically linked, not stripped /home/dob: cat /etc/objformat OBJFORMAT=elf /home/dob: file /bin/cat /bin/cat: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), statically linked, stripped I second what someone else had written earlier: "aout-to-elf-build is your friend!" Thanks, Dan O'Brien Work: 614-860-2392 Page: 614-520-5001 Home: 740-927-2178 Home2: 740-927-2955 ---------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 17:20:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA04796 for freebsd-current-outgoing; Sun, 3 Jan 1999 17:20:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fw.bby.com.au (ns.bby.com.au [192.83.119.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA04774 for ; Sun, 3 Jan 1999 17:20:07 -0800 (PST) (envelope-from gnb@bby.com.au) Received: (from daemon@localhost) by fw.bby.com.au (8.8.8/8.6.9) id MAA28727 for ; Mon, 4 Jan 1999 12:19:40 +1100 (EST) Received: from melba.bby.com.au(192.43.186.1) via SMTP by fw.bby.com.au, id smtpd028725; Mon Jan 4 01:19:33 1999 Received: from lightning (lightning.itga.com.au [192.168.71.20]) by melba.bby.com.au (8.8.2/8.8.2) with ESMTP id MAA04768 for ; Mon, 4 Jan 1999 12:20:06 +1100 (EST) Message-Id: <199901040120.MAA04768@melba.bby.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: current@FreeBSD.ORG Subject: installworld dies in boot stuff Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 04 Jan 1999 12:19:30 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Current as of about 199901040100 UTC ===> sys/boot/i386/loader install -C -o root -g wheel -m 444 /usr/src/sys/boot/i386/loader/loader.help /b oot install: /usr/src/sys/boot/i386/loader/loader.help: No such file or directory *** Error code 71 Stop. *** Error code 1 The file seems to be called "help.i386" in the directory. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 17:26:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA05269 for freebsd-current-outgoing; Sun, 3 Jan 1999 17:26:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles317.castles.com [208.214.167.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA05264 for ; Sun, 3 Jan 1999 17:26:05 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id RAA08795; Sun, 3 Jan 1999 17:22:46 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901040122.RAA08795@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Gregory Bond cc: current@FreeBSD.ORG Subject: Re: installworld dies in boot stuff In-reply-to: Your message of "Mon, 04 Jan 1999 12:19:30 +1100." <199901040120.MAA04768@melba.bby.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 03 Jan 1999 17:22:45 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Current as of about 199901040100 UTC > > > ===> sys/boot/i386/loader > install -C -o root -g wheel -m 444 /usr/src/sys/boot/i386/loader/loader.help /b > oot > install: /usr/src/sys/boot/i386/loader/loader.help: No such file or directory > *** Error code 71 > > Stop. > *** Error code 1 > > The file seems to be called "help.i386" in the directory. No, that's a different file. My error; remove the '#' from the ${BASE}: line in the Makefile, or wait an hour or so and then CVSup again, -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 17:50:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA07532 for freebsd-current-outgoing; Sun, 3 Jan 1999 17:50:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA07527 for ; Sun, 3 Jan 1999 17:50:23 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id KAA04890; Mon, 4 Jan 1999 10:49:57 +0900 (JST) Message-ID: <36901D40.2B3E7896@newsguy.com> Date: Mon, 04 Jan 1999 10:45:36 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: aout-to-elf and bootblocks Success References: <199901040043.QAA08542@dingo.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 > > Another note: make sure you already have Perl installed. If you don't, and > > you use NOPERL, then compilation of ficl fails. Funny. I had perl installed, but ficl still complained about perl not existing. I assumed it *had* to be on the obj/ tree. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com "Heart like a Gabriel, pure and white as ivory, soul like a lucifer, black and cold as a piece of lead." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 18:17:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA09452 for freebsd-current-outgoing; Sun, 3 Jan 1999 18:17:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pobox.com (mercury-2-21.mdm.mkt.execpc.com [169.207.87.149]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA09447 for ; Sun, 3 Jan 1999 18:17:51 -0800 (PST) (envelope-from hamilton@pobox.com) Message-Id: <199901040217.SAA09447@hub.freebsd.org> Received: (qmail 23395 invoked from network); 3 Jan 1999 20:17:19 -0600 Received: from localhost (HELO pobox.com) (127.0.0.1) by localhost with SMTP; 3 Jan 1999 20:17:19 -0600 To: "David W. Chapman Jr." cc: freebsd-current Subject: Re: Advertisement In-reply-to: Your message of "Sun, 03 Jan 1999 17:31:32 CST." <368FFDD4.14E34657@houabg.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 03 Jan 1999 20:17:19 -0600 From: Jon Hamilton Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <368FFDD4.14E34657@houabg.com>, "David W. Chapman Jr." wrote: } Jon Hamilton wrote: } } > In message <368FD021.4C0CC43A@houabg.com>, "David W. Chapman Jr." wrote: } > } Why would anyone in here want to listen to that crappy scam } > } > I don't know. Why would they want to listen to you complain about a } > crappy scam? } } I don't know but I sure don't want to listen to you complain about me } complaining. I'm sure everyone else doesn't want to listen to you complain about me complaining about you complaining, either. One difference between my complaint and yours is that I had the courtesy to *not* copy the mailing list on my original reply. -- 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 Sun Jan 3 18:55:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA12445 for freebsd-current-outgoing; Sun, 3 Jan 1999 18:55:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dt087nac.san.rr.com (dt087nac.san.rr.com [24.94.19.172]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA12440 for ; Sun, 3 Jan 1999 18:55:57 -0800 (PST) (envelope-from Studded@gorean.org) Received: from localhost (doug@localhost) by dt087nac.san.rr.com (8.8.8/8.8.8) with ESMTP id SAA15161; Sun, 3 Jan 1999 18:55:40 -0800 (PST) (envelope-from Studded@gorean.org) Date: Sun, 3 Jan 1999 18:55:40 -0800 (PST) From: Studded X-Sender: doug@dt087nac.san.rr.com To: "Daniel C. Sobral" cc: current@FreeBSD.ORG Subject: Re: FICL & Perl In-Reply-To: <36900AE7.FB3AD249@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 4 Jan 1999, Daniel C. Sobral wrote: > Is there any interest in getting rid of the perl script in the ficl > build? Anything that reduces the dependence on perl during install is a Good Thing in my opinion.... not that my opinion counts for much. :) Doug -- *** Chief Operations Officer, DALnet IRC network *** Like desperadoes waiting for a train . . . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 19:26:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA14954 for freebsd-current-outgoing; Sun, 3 Jan 1999 19:26:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA14949 for ; Sun, 3 Jan 1999 19:26:16 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id NAA11742; Mon, 4 Jan 1999 13:55:49 +1030 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA16325; Mon, 4 Jan 1999 13:55:48 +1030 Date: Mon, 4 Jan 1999 13:55:48 +1030 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: Thierry Herbelot Cc: current@FreeBSD.ORG Subject: Re: Is my /dev/random broken ? In-Reply-To: <368FC908.1D728596@cybercable.fr> Message-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, 3 Jan 1999, Thierry Herbelot wrote: > This is a follow-on to a post by Kris Kennaway (Re pgcc-1.1.1). > > I have a recent -Current (cvsupped on Dec 19 13:01) with an a.out kernel > and an elf userland and I have tried to duplicate Kris' test : > > # dd if=/dev/random of=/usr2/bigfile bs=1024k count=30 ^^^^^^^^^^^ /dev/urandom, sorry. I typed that too late last night :-) Kris ----- (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 19:42:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA17175 for freebsd-current-outgoing; Sun, 3 Jan 1999 19:42:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA17168 for ; Sun, 3 Jan 1999 19:42:24 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id OAA11948; Mon, 4 Jan 1999 14:11:57 +1030 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA19174; Mon, 4 Jan 1999 14:11:56 +1030 Date: Mon, 4 Jan 1999 14:11:56 +1030 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: "David W. Chapman Jr." Cc: freebsd-current Subject: Re: Wine-Latest In-Reply-To: <369005AD.FC440AAC@houabg.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, 3 Jan 1999, David W. Chapman Jr. wrote: > Anyone been able to compile the latest version of wine with egcs-1.1 If you mean the version in ports, then yes.. (egcs version from ports also). Kris ----- (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 19:44:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA17414 for freebsd-current-outgoing; Sun, 3 Jan 1999 19:44:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from houcbs2.houabg.com (houabg.com [206.109.247.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA17401 for ; Sun, 3 Jan 1999 19:44:01 -0800 (PST) (envelope-from dchapman@houabg.com) Received: from sdn-ar-004txhousP268.dialsprint.net by houcbs2.houabg.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1457.7) id ZBAFFA5Z; Sun, 3 Jan 1999 21:50:18 -0600 Message-ID: <3690393A.70743F75@houabg.com> Date: Sun, 03 Jan 1999 21:44:58 -0600 From: "David W. Chapman Jr." X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway CC: freebsd-current Subject: Re: Wine-Latest 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, 3 Jan 1999, David W. Chapman Jr. wrote: > > > Anyone been able to compile the latest version of wine with egcs-1.1 > > If you mean the version in ports, then yes.. (egcs version from ports also). > > Kris > > ----- > (ASP) Microsoft Corporation (MSFT) announced today that the release of its > productivity suite, Office 2000, will be delayed until the first quarter > of 1901. I should have asked in better details, the version from www.winehq.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 3 21:23:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA25147 for freebsd-current-outgoing; Sun, 3 Jan 1999 21:23:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp11.bellglobal.com (smtp11.bellglobal.com [204.101.251.53]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA25142 for ; Sun, 3 Jan 1999 21:23:18 -0800 (PST) (envelope-from minako@supernet.ca) Received: from supernet.ca (HSE-MTL-ppp4760.qc.sympatico.ca [209.226.107.197]) by smtp11.bellglobal.com (8.8.5/8.8.5) with ESMTP id AAA21545 for ; Mon, 4 Jan 1999 00:24:24 -0500 (EST) Message-ID: <36905067.245FA0E@supernet.ca> Date: Mon, 04 Jan 1999 00:23:51 -0500 From: Mike Reply-To: minako@supernet.ca X-Mailer: Mozilla 4.5 [en] (Win98; U) X-Accept-Language: en-GB,en-US,fr,fr-BE,fr-CA,fr-FR,fr-CH,pt,pt-BR,es MIME-Version: 1.0 To: FreeBSD-current@FreeBSD.ORG Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 21:33:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA25855 for freebsd-current-outgoing; Sun, 3 Jan 1999 21:33:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (nat0050.mpoweredpc.net [142.177.188.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA25848; Sun, 3 Jan 1999 21:33:44 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id BAA16176; Mon, 4 Jan 1999 01:32:56 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Mon, 4 Jan 1999 01:32:55 -0400 (AST) From: The Hermit Hacker To: Ollivier Robert cc: committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. In-Reply-To: <19990103021730.A31313@keltia.freenix.fr> Message-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, 3 Jan 1999, Ollivier Robert wrote: > Having it in contrib shows a bit more that we're providing an alternative > to sendmail. Removing them both would show more, IMHO...put them both into ports and make it such that the installer has to make a choice. Then, there is no bias' exhibited by anyone... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 21:36:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA26237 for freebsd-current-outgoing; Sun, 3 Jan 1999 21:36:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (nat0050.mpoweredpc.net [142.177.188.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA26231; Sun, 3 Jan 1999 21:36:12 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id BAA16184; Mon, 4 Jan 1999 01:35:43 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Mon, 4 Jan 1999 01:35:43 -0400 (AST) From: The Hermit Hacker To: "Jonathan M. Bresler" cc: brian@hyperreal.org, freebsd-current@FreeBSD.ORG Subject: Re: sendmail throughput (was: HEADS UP: Postfix is coming. new uid, gid required.) In-Reply-To: <199901040106.RAA03430@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 3 Jan 1999, Jonathan M. Bresler wrote: > > X-Sender: brian@hyperreal.org > > Date: Sun, 03 Jan 1999 13:44:02 -0800 > > From: Brian Behlendorf > > Cc: freebsd-current@FreeBSD.ORG > > Content-Type: text/plain; charset="us-ascii" > > > > At 07:24 PM 1/2/99 -0800, Jonathan M. Bresler wrote: > > > news seems to have even more flamage than the mailing lists. > > > with mail i can control spam, with news everyone would have to > > > control spam. > > > > Unless you run a localized newsserver. news://news.freebsd.org/ for example. > > all news servers would hvae to send all news to > news://news.freebsd.org/ and only news://news.freebsd.org/ would be > allowed to send news to any other site......there's that bottleneck > again....now it'll be larger quantities of news (rather than mail) > less frequently. > > perhaps i have misunderstood. I think he was suggesting setting up a local news server that everyone can connect to to read a "freebsd.*" set of newsgroups... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 21:42:39 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA26915 for freebsd-current-outgoing; Sun, 3 Jan 1999 21:42:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from houcbs2.houabg.com (houabg.com [206.109.247.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA26897 for ; Sun, 3 Jan 1999 21:42:36 -0800 (PST) (envelope-from dchapman@houabg.com) Received: from sdn-ar-004txhousP268.dialsprint.net by houcbs2.houabg.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1457.7) id ZBAFFA6B; Sun, 3 Jan 1999 23:48:53 -0600 Message-ID: <36905506.1B4F3BDC@houabg.com> Date: Sun, 03 Jan 1999 23:43:34 -0600 From: "David W. Chapman Jr." X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current Subject: Re: sendmail throughput (was: HEADS UP: Postfix is coming. new uid,gid required.) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The Hermit Hacker wrote: > On Sun, 3 Jan 1999, Jonathan M. Bresler wrote: > > > > X-Sender: brian@hyperreal.org > > > Date: Sun, 03 Jan 1999 13:44:02 -0800 > > > From: Brian Behlendorf > > > Cc: freebsd-current@FreeBSD.ORG > > > Content-Type: text/plain; charset="us-ascii" > > > > > > At 07:24 PM 1/2/99 -0800, Jonathan M. Bresler wrote: > > > > news seems to have even more flamage than the mailing lists. > > > > with mail i can control spam, with news everyone would have to > > > > control spam. > > > > > > Unless you run a localized newsserver. news://news.freebsd.org/ for example. > > > > all news servers would hvae to send all news to > > news://news.freebsd.org/ and only news://news.freebsd.org/ would be > > allowed to send news to any other site......there's that bottleneck > > again....now it'll be larger quantities of news (rather than mail) > > less frequently. > > > > perhaps i have misunderstood. > > I think he was suggesting setting up a local news server that everyone can > connect to to read a "freebsd.*" set of newsgroups... > > Marc G. Fournier > Systems Administrator @ hub.org > primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message I personally would like this so I could just ignore people flaming me. But really, I have to check my email every 2 hours or it fills up. I would like a news server. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 21:48:41 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA27659 for freebsd-current-outgoing; Sun, 3 Jan 1999 21:48:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA27653; Sun, 3 Jan 1999 21:48:39 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id VAA36610; Sun, 3 Jan 1999 21:48:03 -0800 (PST) To: The Hermit Hacker cc: "Jonathan M. Bresler" , brian@hyperreal.org, freebsd-current@FreeBSD.ORG Subject: Re: sendmail throughput (was: HEADS UP: Postfix is coming. new uid, gid required.) In-reply-to: Your message of "Mon, 04 Jan 1999 01:35:43 -0400." Date: Sun, 03 Jan 1999 21:48:02 -0800 Message-ID: <36607.915428882@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think he was suggesting setting up a local news server that everyone can > connect to to read a "freebsd.*" set of newsgroups... Oh, well, if somebody does do this and wants a cname for news.freebsd.org, they have only to contact hostmaster@freebsd.org (not me) and it shall be done! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 22:00:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA28662 for freebsd-current-outgoing; Sun, 3 Jan 1999 22:00:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA28657 for ; Sun, 3 Jan 1999 22:00:31 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id IAA02794; Mon, 4 Jan 1999 08:00:02 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id IAA18579; Mon, 4 Jan 1999 08:00:01 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199901040600.IAA18579@greenpeace.grondar.za> To: Thomas Dean cc: freebsd-current@FreeBSD.ORG Subject: Re: Perl gv.h Problem In-Reply-To: Your message of " Sun, 03 Jan 1999 13:34:26 PST." <199901032134.NAA01739@ix.netcom.com> References: <199901032134.NAA01739@ix.netcom.com> Date: Mon, 04 Jan 1999 07:59:59 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas Dean wrote: > I am running an SMP -current system, as of yesterday. In bringing the > system up-to-date, as aout, I encountered a problem. > > In doing a make world, and, when attempting to do make aout-to-elf, I > had to use -DNOPERL to complete. Here is a log clip from the > aout-to-elf make. I lost the output from make world, but, I believe > it was the same. > > Is this a new problem? I can retry this, anytime. There is something wrong in your source tree; I did a aout-to-elf this weekend, and this problem did not happen. Are you sure you have no turds left over from previous versions, compiles etc? 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 3 22:02:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA28652 for freebsd-current-outgoing; Sun, 3 Jan 1999 22:00:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fw.bby.com.au (ns.bby.com.au [192.83.119.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA28647 for ; Sun, 3 Jan 1999 22:00:21 -0800 (PST) (envelope-from gnb@itga.com.au) Received: (from daemon@localhost) by fw.bby.com.au (8.8.8/8.6.9) id QAA00740 for ; Mon, 4 Jan 1999 16:59:52 +1100 (EST) Received: from melba.bby.com.au(192.43.186.1) via SMTP by fw.bby.com.au, id smtpd000738; Mon Jan 4 05:59:45 1999 Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by melba.bby.com.au (8.8.2/8.8.2) with ESMTP id RAA13764 for ; Mon, 4 Jan 1999 17:00:18 +1100 (EST) Received: from lightning (lightning [192.168.71.20]) by lightning.itga.com.au (8.9.1a/8.9.1) with ESMTP id QAA25674; Mon, 4 Jan 1999 16:59:42 +1100 (EST) Message-Id: <199901040559.QAA25674@lightning.itga.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: current@freebsd.org Subject: SOFTUPDATES hangs keyboard Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="==_Exmh_-10978362240" Date: Mon, 04 Jan 1999 16:59:41 +1100 Sender: owner-freebsd-current@freebsd.org Precedence: bulk X-Loop: FreeBSD.ORG This is a multipart MIME message. --==_Exmh_-10978362240 Content-Type: text/plain; charset=us-ascii Current as at 199901040100UTC (but has happened since 3.0R when I started on 3.0). HP KAYAK XA (P-II 400, BX Mboard, Matrox G200 AGP, PS/2 mouse, HP keyboard with a bunch of extra buttons.) This is happening quite consistently. - boot -s, turn softupdates on on (unmounted) /var. - ^D to boot multi-user, system comes up. - Alt-F2 to switch to second vt - log in as root >From this point on, the keyboard stops working - perhaps because this is the first time a write to /var occurs? - Hitting any "normal" key has no effect at all. - Alt-Fn will swap to another vt - after a bunch of keypresses (dunno if it is the number of 'normal" keys or the number of Alt-Fn presses), then beahviour changes again: - normal keys still to nothing - Alt-Fn keys now elicit a beep just like DOS does when the KB buffer is full. - At this point, the only solution is C-A-Del, boot single user, run fsck on the /var partition (usually somewhat mangled), turn off soft updates, ^D to start up, and the system is fine. Very repeatable, very clearly a SOFTUPDATES problem. Any hints about how I can help fix this? Config file attached. --==_Exmh_-10978362240 Content-Type: text/plain ; name="Hellcat"; charset=us-ascii Content-Description: Hellcat Content-Disposition: attachment; filename="Hellcat" # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # For more information read the handbook part System Administration -> # Configuring the FreeBSD Kernel -> The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id: GENERIC,v 1.125 1998/10/16 01:30:11 obrien Exp $ machine "i386" cpu "I686_CPU" ident Hellcat maxusers 32 options "NO_F00F_HACK" # Got a read P2!! #options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem #options MFS_ROOT #MFS usable as root device, "MFS" req'ed options NFS #Network Filesystem #options NFS_ROOT #NFS usable as root device, "NFS" req'ed options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options "CD9660_ROOT" #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options SOFTUPDATES config kernel root on wd0 controller isa0 #controller eisa0 controller pci0 controller pnp0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 #disk fd1 at fdc0 drive 1 # Unless you know very well what you're doing, leave ft0 at drive 2, or # remove the line entirely if you don't need it. Trying to configure # it on another unit might cause surprises, see PR kern/7176. #tape ft0 at fdc0 drive 2 options "CMD640" # work around CMD640 chip deficiency controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 #disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 vector wdintr #disk wd2 at wdc1 drive 0 #disk wd3 at wdc1 drive 1 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM device wcd0 #IDE CD-ROM #device wfd0 #IDE Floppy (e.g. LS-120) # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" conflicts tty irq 1 vector scintr options MAXCONS=4 # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? port "IO_KBD" conflicts tty irq 1 vector pcrint #options XSERVER # support for X server #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr #device sio2 at isa? disable port "IO_COM3" tty irq 5 vector siointr #device sio3 at isa? disable port "IO_COM4" tty irq 9 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. device xl0 pseudo-device loop pseudo-device ether #pseudo-device sl 1 #pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 64 pseudo-device gzip # Exec gzipped a.out's # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing # This provides support for System V shared memory. # (used for XF86 server) options SYSVSHM # The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. pseudo-device bpfilter 4 #Berkeley packet filter #device pcm0 at isa? port 0x530 tty irq 5 drq 0 flags 0x13 vector pcmintr device pcm0 at isa? port 0x220 tty irq 10 drq 1 flags 0x0 vector pcmintr # joy: joystick device joy0 at isa? port "IO_GAME" --==_Exmh_-10978362240-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 22:10:38 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA29308 for freebsd-current-outgoing; Sun, 3 Jan 1999 22:10:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA29300 for ; Sun, 3 Jan 1999 22:10:36 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with SMTP id AAA25364; Mon, 4 Jan 1999 00:10:07 -0600 (CST) Date: Mon, 4 Jan 1999 00:10:07 -0600 (CST) From: Steve Price To: Gregory Bond cc: current@FreeBSD.ORG Subject: Re: SOFTUPDATES hangs keyboard In-Reply-To: <199901040559.QAA25674@lightning.itga.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 4 Jan 1999, Gregory Bond wrote: [...] # - At this point, the only solution is C-A-Del, boot single user, run fsck on # the /var partition (usually somewhat mangled), turn off soft updates, ^D to # start up, and the system is fine. # # Very repeatable, very clearly a SOFTUPDATES problem. Many people are having this problem. I can only speak for myself but I don't run SOFTUPDATES so I doubt very seriously this problem is related to that. The problem most likely is in the terminal code somewhere, and has everything to do with switching vtys and having a PS/2 keyboard. # Any hints about how I can help fix this? Sorry, wish I knew. I've had three lockups like this today alone. :( -steve # Config file attached. # # To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 22:13:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA29686 for freebsd-current-outgoing; Sun, 3 Jan 1999 22:13:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peacock.tci.com (coral.tci.com [198.178.8.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA29680 for ; Sun, 3 Jan 1999 22:13:34 -0800 (PST) (envelope-from chris@tci.com) Received: from oreo.tci.com (co-chris-pc01.tci.com [172.18.27.65]) by peacock.tci.com (8.9.0/8.9.0) with ESMTP id XAA10512 for ; Sun, 3 Jan 1999 23:13:05 -0700 (MST) Received: from tci.com (localhost [127.0.0.1]) by oreo.tci.com (8.9.1b+Sun/8.9.1) with ESMTP id XAA02145 for ; Sun, 3 Jan 1999 23:12:45 -0700 (MST) Message-ID: <36905BDC.EF293117@tci.com> Date: Sun, 03 Jan 1999 23:12:44 -0700 From: Chris Tubutis Organization: Tele-Communications, Inc. X-Mailer: Mozilla 4.5 [en] (X11; U; SunOS 5.7 sun4m) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current Subject: Re: sendmail throughput (was: HEADS UP: Postfix is coming. new uid,gid required.) References: <36905506.1B4F3BDC@houabg.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David W. Chapman Jr." wrote: > > The Hermit Hacker wrote: > > > On Sun, 3 Jan 1999, Jonathan M. Bresler wrote: > > > > > > X-Sender: brian@hyperreal.org > > > > Date: Sun, 03 Jan 1999 13:44:02 -0800 > > > > From: Brian Behlendorf > > > > Cc: freebsd-current@FreeBSD.ORG > > > > Content-Type: text/plain; charset="us-ascii" > > > > > > > > At 07:24 PM 1/2/99 -0800, Jonathan M. Bresler wrote: > > > > > news seems to have even more flamage than the mailing lists. > > > > > with mail i can control spam, with news everyone would have to > > > > > control spam. > > > > > > > > Unless you run a localized newsserver. news://news.freebsd.org/ for example. > > > > > > all news servers would hvae to send all news to > > > news://news.freebsd.org/ and only news://news.freebsd.org/ would be > > > allowed to send news to any other site......there's that bottleneck > > > again....now it'll be larger quantities of news (rather than mail) > > > less frequently. > > > > > > perhaps i have misunderstood. > > > > I think he was suggesting setting up a local news server that everyone can > > connect to to read a "freebsd.*" set of newsgroups... > > > > Marc G. Fournier > > Systems Administrator @ hub.org > > primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > I personally would like this so I could just ignore people flaming me. But really, > I have to check my email every 2 hours or it fills up. I would like a news server. I can empathize, and I therefore also like the idea of a News server - ideally one with groups that are gatewayed to the e-mail lists (and vice versa). I only recently joined a couple of the FreeBSD lists (-questions, -current, maybe -announce [don't remember for sure right now]) and am experiencing the same situation as stated directly above by Mr. Chapman. Having stuff pushed to me is nice, but there's a limit as to how much niceness I can take.... :) chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 22:16:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA00218 for freebsd-current-outgoing; Sun, 3 Jan 1999 22:16:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-20-dbn.dial-up.net [196.34.155.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA00204 for ; Sun, 3 Jan 1999 22:16:25 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id IAA01365; Mon, 4 Jan 1999 08:15:22 +0200 (SAT) From: Robert Nordier Message-Id: <199901040615.IAA01365@ceia.nordier.com> Subject: Re: New boot blocks for serial console ... In-Reply-To: from "Robert V. Baron" at "Jan 3, 99 07:37:13 pm" To: rvb@cs.cmu.edu (Robert V. Baron) Date: Mon, 4 Jan 1999 08:15:18 +0200 (SAT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert V. Baron wrote: > You've forced me to use the new scheme. I have a laptop with the > serial line on com2(0x2f8) and use 56700 baud. A long time ago > I built a boot1/boot2 to do this. In seems that things have changed > in the new scheme. It looks like that in sys/boot/i386/Makefile, I > need to change: > B2SIOPRT?= 0x3f8 > B2SIOFMT?= 0x3 > B2SIODIV?= 0xc > to > B2SIOPRT?= 0x2f8 > B2SIOFMT?= 0x3 > B2SIODIV?= 0x2 > > This is a bit cryptic and could use a comment or two. > > But there are more loaders today. It looks like > sys/boot/i386/libi386/comconsole.c > needs to be handed edited: > #define COMPORT 0x3f8 > #define COMSPEED 9600 > to > #define COMPORT 0x2f8 > #define COMSPEED 57600 > > I guess that this should be pulled out to the makefile building the > lib. > > The two files above are the only ones that contain "3f8" so I guess > that nothing else needs to be changed. Those should be the only modifications required. Otherwise, your comments are reasonable and should be taken into account during an upcoming revision. Though, of course, you'd be welcome to simply commit the suggested improvements yourself. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 22:25:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA00899 for freebsd-current-outgoing; Sun, 3 Jan 1999 22:25:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles317.castles.com [208.214.167.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA00894 for ; Sun, 3 Jan 1999 22:25:44 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id WAA10270; Sun, 3 Jan 1999 22:22:23 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901040622.WAA10270@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Gregory Bond cc: current@FreeBSD.ORG Subject: Re: SOFTUPDATES hangs keyboard In-reply-to: Your message of "Mon, 04 Jan 1999 16:59:41 +1100." <199901040559.QAA25674@lightning.itga.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 03 Jan 1999 22:22:23 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Current as at 199901040100UTC (but has happened since 3.0R when I started on > 3.0). > > HP KAYAK XA (P-II 400, BX Mboard, Matrox G200 AGP, PS/2 mouse, HP keyboard > with a bunch of extra buttons.) > > This is happening quite consistently. > > - boot -s, turn softupdates on on (unmounted) /var. > - ^D to boot multi-user, system comes up. > - Alt-F2 to switch to second vt > - log in as root > > >From this point on, the keyboard stops working - perhaps because this is the > first time a write to /var occurs? > > - Hitting any "normal" key has no effect at all. > - Alt-Fn will swap to another vt > - after a bunch of keypresses (dunno if it is the number of 'normal" keys or > the number of Alt-Fn presses), then beahviour changes again: > - normal keys still to nothing > - Alt-Fn keys now elicit a beep just like DOS does when the KB buffer > is full. > > - At this point, the only solution is C-A-Del, boot single user, run fsck on > the /var partition (usually somewhat mangled), turn off soft updates, ^D to > start up, and the system is fine. > > Very repeatable, very clearly a SOFTUPDATES problem. How is it "clearly a SOFTUPDATES problem"? What's clear is that you have something spinning in an interrupt handler. Soft updates may be triggering this, but there's no guarantee that it's the cause of the problem. Start off by making sure that your softupdates files are symlinks to the real thing, not stale copies. Then add DDB to your kernel config, and when the system wedges, hit alt-ctrl-escape, then type "trace" to get a traceback. If you can do this with a debug kernel (config -g ...) that would be even better. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 22:27:53 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA01236 for freebsd-current-outgoing; Sun, 3 Jan 1999 22:27:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA01220 for ; Sun, 3 Jan 1999 22:27:51 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.65]) by smtp05.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA55A9; Mon, 4 Jan 1999 07:27:24 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199901032052.MAA07318@dingo.cdrom.com> Date: Mon, 04 Jan 1999 07:34:36 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Mike Smith Subject: Re: Bootblocks / Bootloader Cc: current@FreeBSD.ORG, Robert Nordier Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-Jan-99 Mike Smith wrote: >> > Bear in mind that, most of the time, the new boot blocks simply >> > pass control to /boot/loader. You can use *recent* versions of >> > the old boot blocks to start /boot/loader as well. >> >> Weird thing is that the first time it displayed the FreeBSD/i386 Boot >> message and after I rm'ed /boot.config I never saw it again, and I >> rebooted two/three times... > > That's normal; the "old" help is only displayed in "compatibility" > mode. Without a /boot.config, the bootblocks try to be as quiet as > possible. You may notice the spinner stop for a couple of seconds; if > you hit a key at that point, you'll drop back into "compatibility" mode > again. Well, it struck me as odd after reading Robert's tips about installing the bootblocks. He explicitly referred to the old boot message with the hex adresses in it, and the other consisting only of the message FreeBSD/i386 Boot. Hence I got to wonder about it. Yes I did notice the waiting of the spinner. Is that fallback a permanent one of just one to get through the transition time of a.out > elf? Just in case the bootblocks mess up for people. --- Jeroen Ruigrok van der Werven A veil of smoke is what I am, asmodai(at)wxs.nl I wait and I wait... Network/Security Specialist BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 22:27:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA01251 for freebsd-current-outgoing; Sun, 3 Jan 1999 22:27:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA01235 for ; Sun, 3 Jan 1999 22:27:53 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.65]) by smtp01.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA239F; Mon, 4 Jan 1999 07:27:27 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199901032055.MAA07348@dingo.cdrom.com> Date: Mon, 04 Jan 1999 07:34:38 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Mike Smith Subject: Re: Bootblocks / Bootloader Cc: FreeBSD Current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-Jan-99 Mike Smith wrote: >> On 03-Jan-99 Mike Smith wrote: >> >> >> ... [booting kernel] >> >> >> >> [kernel symbol table not valid] >> > >> > This is actually DDB complaining that your a.out symbol table is not >> > valid. You may have over-aggressively stripped your kernel, or we may >> > have something going wrong that's eaten it in the load process. >> >> I never stripped my kernels... And this is an ELF kernel from the 2nd and >> it's still giving the notice after I installed the real new bootblocks... >> At >> least that's what I am presuming since the whole system is ELF ;) > > Unless you have KERNFORMAT=elf set, your kernel is still a.out. More > to the point, the message that you're seeing there comes from line 99 > in sys/ddb/db_aout.c. So if you have an ELF kernel going, I'm not sure > why that code is being run at all. OK, another mess up... I was only checking /etc/objformat, while I forgot that the /usr/src/sys/i386/conf/Makefile.i386 wasn't set to elf... So I am now compiling a true ELF kernel... But it still strikes me as odd that before I installed the new bootblocks my a.out kernel never gave me the symbol table message and afterwards it did. --- Jeroen Ruigrok van der Werven A veil of smoke is what I am, asmodai(at)wxs.nl I wait and I wait... Network/Security Specialist BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 22:33:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA01694 for freebsd-current-outgoing; Sun, 3 Jan 1999 22:33:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles317.castles.com [208.214.167.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA01686 for ; Sun, 3 Jan 1999 22:33:30 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id WAA10329 for ; Sun, 3 Jan 1999 22:30:22 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901040630.WAA10329@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: Re: Bootblocks / Bootloader In-reply-to: Your message of "Mon, 04 Jan 1999 07:34:36 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 03 Jan 1999 22:30:21 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On 03-Jan-99 Mike Smith wrote: > >> > Bear in mind that, most of the time, the new boot blocks simply > >> > pass control to /boot/loader. You can use *recent* versions of > >> > the old boot blocks to start /boot/loader as well. > >> > >> Weird thing is that the first time it displayed the FreeBSD/i386 Boot > >> message and after I rm'ed /boot.config I never saw it again, and I > >> rebooted two/three times... > > > > That's normal; the "old" help is only displayed in "compatibility" > > mode. Without a /boot.config, the bootblocks try to be as quiet as > > possible. You may notice the spinner stop for a couple of seconds; if > > you hit a key at that point, you'll drop back into "compatibility" mode > > again. > > Well, it struck me as odd after reading Robert's tips about installing the > bootblocks. He explicitly referred to the old boot message with the hex > adresses in it, and the other consisting only of the message FreeBSD/i386 > Boot. Hence I got to wonder about it. You'll only get the message from the new boot2 if you drop into it. > Yes I did notice the waiting of the spinner. Is that fallback a permanent one > of just one to get through the transition time of a.out > elf? Just in case > the bootblocks mess up for people. It's permanent; you can use it to load a monolithic ELF kernel for rescue purposes. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 23:11:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA05925 for freebsd-current-outgoing; Sun, 3 Jan 1999 23:11:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dnvrpop2.dnvr.uswest.net (dnvrpop2.dnvr.uswest.net [206.196.128.4]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA05915 for ; Sun, 3 Jan 1999 23:11:51 -0800 (PST) (envelope-from tmorrison@uswest.net) Received: (qmail 9680 invoked by alias); 4 Jan 1999 07:11:23 -0000 Delivered-To: fixup-freebsd-current@FreeBSD.ORG@fixme Received: (qmail 9639 invoked by uid 0); 4 Jan 1999 07:11:22 -0000 Received: from adsla195.dnvr.uswest.net (HELO uswest.net) (209.180.248.194) by dnvrpop2.dnvr.uswest.net with SMTP; 4 Jan 1999 07:11:22 -0000 Message-ID: <369069CE.BF488BCC@uswest.net> Date: Mon, 04 Jan 1999 00:12:14 -0700 From: Tod Morrison Reply-To: tod.morrison@usa.net X-Mailer: Mozilla 4.5 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Luigi Rizzo CC: Tod Morrison , freebsd-current@FreeBSD.ORG Subject: Re: SoundBlaster 128 References: <199901031207.NAA26575@labinfo.iet.unipi.it> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luigi Rizzo wrote: > > > The pcm driver works nicely, except for that the module doesn't register > > if there are not any isa devices (? - I don't really understand the > > problem, I just found a patch in the mailing list archives to fix it ). > > can you send me the patch (original one or your modified one). > Unfortunately my test machine has an onboard ISA audio card so i cannot > easily reproduce the problem. > > thanks > luigi > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message Here's a copy of the original posting from the archive, it won't apply as is but its only changing a few lines in one file so it shouldn't be to hard to do by hand. Tod ------------ The following patch (to be added to my other patches) removes the bug that the cdevsw entry was not added when there was no ISA card attached: --- sound.c.orig Mon Nov 23 18:07:35 1998 +++ sound.c Mon Nov 23 18:06:04 1998 @@ -239,7 +239,6 @@ snddev_info *d = NULL ; struct isa_device *dvp; int stat = 0; - dev_t isadev; dev->id_ointr = pcmintr; @@ -284,9 +283,6 @@ if (FULL_DUPLEX(d)) isa_dma_acquire(d->dbuf_in.chan); - isadev = makedev(CDEV_MAJOR, 0); - cdevsw_add(&isadev, &snd_cdevsw, NULL); - /* * should try and find a suitable value for id_id, otherwise * the interrupt is not registered and dispatched properly. @@ -331,6 +327,10 @@ pcminit(snddev_info *d, int unit) { void *cookie; + dev_t dev; + + dev = makedev(CDEV_MAJOR, 0); + cdevsw_add(&dev, &snd_cdevsw, NULL); /* * initialize standard parameters for the device. This can be cu Jo --------------------------------------------------------------------- Pray that there's intelligent life Joachim Kuebart Somewhere up in space Stuttgart, Germany 'Cause there's bugger all down here on earth. --- Monty Python To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 23:15:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA06453 for freebsd-current-outgoing; Sun, 3 Jan 1999 23:15:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fw.bby.com.au (ns.bby.com.au [192.83.119.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA06446 for ; Sun, 3 Jan 1999 23:15:10 -0800 (PST) (envelope-from gnb@itga.com.au) Received: (from daemon@localhost) by fw.bby.com.au (8.8.8/8.6.9) id SAA01310; Mon, 4 Jan 1999 18:13:32 +1100 (EST) Received: from melba.bby.com.au(192.43.186.1) via SMTP by fw.bby.com.au, id smtpd001308; Mon Jan 4 07:13:23 1999 Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by melba.bby.com.au (8.8.2/8.8.2) with ESMTP id SAA15352; Mon, 4 Jan 1999 18:13:57 +1100 (EST) Received: from lightning (lightning [192.168.71.20]) by lightning.itga.com.au (8.9.1a/8.9.1) with ESMTP id SAA26417; Mon, 4 Jan 1999 18:13:20 +1100 (EST) Message-Id: <199901040713.SAA26417@lightning.itga.com.au> From: Gregory Bond To: Mike Smith Cc: current@FreeBSD.ORG Subject: Re: SOFTUPDATES hangs keyboard In-reply-to: Your message of Sun, 03 Jan 1999 22:22:23 -0800. Date: Mon, 04 Jan 1999 18:13:20 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike sez: >What's clear is that you have something spinning in an interrupt >handler. Soft updates may be triggering this, but there's no guarantee >that it's the cause of the problem. > >Start off by making sure that your softupdates files are symlinks to >the real thing, not stale copies. Then add DDB to your kernel config, >and when the system wedges, hit alt-ctrl-escape, then type "trace" to >get a traceback. If you can do this with a debug kernel (config -g >...) that would be even better. My apologies for unwarranted assumptions. OK, I've compiled up with DDB and -g and I get the following (transcribed by hand, so mind the typos!): _Debugger(msg=f01fa58f) at _Debugger+0x37 [../../i386/i386/db_interface.c:66] _scgetc(flags=2) at _scgetc+0xd9f [../../i386/isa/syscons.c:3738] _scintr(unit=0) at _scintr+0x17 [../../i386/isa/syscons.c:861] Xresume1() at Xresume1+0x2b --- interrupt, eip = 0xf01d0760, esp = 0xf482aeb8, ebp = 0xf482ad68 --- _doreti(f482af88) at _doreti _sched_sync() at _sched_sync+0xa4 [../../kern/vfs_subr.c:499] _kproc_start(udata=f02283ac) at _kproc_start+0x32 [../../kern/init_main.c:311] _fork_trampoline(21cc1589,c766f025,2521ce05,800008f0,2521d025) at _fork_trampoline+0x30 Asking DB for a panic at this point just hangs the system at the "syncing disks..." prompt. I assume that is the same problem. FWIW: All this time, the Alt-Fn still works, until I tried to Alt-Fn to the Xserver. Then it all hung. Anything else I can try? Greg. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 3 23:28:34 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA07633 for freebsd-current-outgoing; Sun, 3 Jan 1999 23:28:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA07627 for ; Sun, 3 Jan 1999 23:28:31 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id AAA56886; Mon, 4 Jan 1999 00:26:41 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199901040726.AAA56886@panzer.plutotech.com> Subject: Re: 3.0-CURRENT CAM vs scanner problems In-Reply-To: <199901040055.QAA21093@pinhead.parag.codegen.com> from Parag Patel at "Jan 3, 99 04:55:12 pm" To: parag@cgt.com (Parag Patel) Date: Mon, 4 Jan 1999 00:26:40 -0700 (MST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (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 Parag Patel wrote... > > I am getting errors like these from the CAM subsystem when I try to scan > a rather small image using GIMP and the SANE 1.0 port and my UMAX: > > cam_periph_mapmem: attempt to map 130851 bytes, which is greater than DFLTPHYS(65536) > cam_periph_mapmem: attempt to map 130820 bytes, which is greater than DFLTPHYS(65536) > cam_periph_mapmem: attempt to map 131016 bytes, which is greater than DFLTPHYS(65536) > cam_periph_mapmem: attempt to map 129444 bytes, which is greater than DFLTPHYS(65536) > cam_periph_mapmem: attempt to map 131029 bytes, which is greater than DFLTPHYS(65536) > > The scan does not succeed in either lineart, gray, or color modes, > although the preview does. > > The comment in cam/cam_periph.c implies that the DFLTPHYS should be > MAXPHYS but perhaps the comment is wrong? Or perhaps SANE should be > using DFLTPHYS instead of MAXPHYS? > > For now, I added a patch to the sane-1.0 sanei/sanei_scsi.c file to use > DFLTPHYS instead of MAXPHYS, and it is scanning nicely. Still, I don't > know if it's a SANE bug or a CAM bug and so don't who to report it to. This is a SANE bug, sort of. quick background info: ======== The crashes that folks have been seeing with cdda2wav were caused by cdda2wav doing non-page-aligned reads that were within a page of 128K in size. Because the VM system deals with things on page boundaries, this ended up causing more than 128K to get mapped in, which exceeded the size of the system buffers (they're MAXPHYS size, and MAXPHYS == 128K). So, I first put in the proper check to make sure that transfers near 128K were page aligned. This "fixed" the cdda2wav crashes, by causing the program not to work by default. (because its transfers were too big) Justin then suggested that I change the check to be against DFLTPHYS (64K), since some controllers can't handle transfer sizes larger than that. Bruce then pointed out that controllers have always had to be able to handle DFLTPHYS/PAGE_SIZE - 1 page transfers, to handle the non-aligned case. I need to check that with Justin, though. That obviously assumes, however, that MAXPHYS > DFLTPHYS, and not MAXPHYS >= DFLTPHYS. So, it's possible I may take out the alignment check, and you may be able to transfer slightly more than 64K in the non-aligned case. Eventually, we'll have a field in probably the path inquiry CCB that indicates the maximum transfer size the controller can handle. Then applications can use that to set their maximum transfer size, rather than a fixed value. ======== For now, SANE should be changed to use the following transfer size calculation. This will work in all cases, and it will work even after we make future changes: DFLTPHYS - PAGE_SIZE (i.e., 60K for i386, and 56K for alpha) The cdrecord port has been changed to use that value, and Joerg Schilling will be putting that into his cdrecord/libscg source tree, so cdda2wav and cdrecord will be using that value in the future as well. I imagine that this is more than you wanted to hear, but at least it sort of explains the problem. :) Ken -- Kenneth Merry ken@plutotech.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 3 23:41:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA08999 for freebsd-current-outgoing; Sun, 3 Jan 1999 23:41:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA08991 for ; Sun, 3 Jan 1999 23:41:20 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id XAA83407; Sun, 3 Jan 1999 23:40:46 -0800 (PST) (envelope-from dillon) Date: Sun, 3 Jan 1999 23:40:46 -0800 (PST) From: Matthew Dillon Message-Id: <199901040740.XAA83407@apollo.backplane.com> To: Gregory Bond Cc: Mike Smith , current@FreeBSD.ORG Subject: Re: SOFTUPDATES hangs keyboard References: <199901040713.SAA26417@lightning.itga.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :My apologies for unwarranted assumptions. : :OK, I've compiled up with DDB and -g and I get the following :(transcribed by hand, so mind the typos!): : :_Debugger(msg=f01fa58f) at _Debugger+0x37 [../../i386/i386/db_interface.c:66] :_scgetc(flags=2) at _scgetc+0xd9f [../../i386/isa/syscons.c:3738] :_scintr(unit=0) at _scintr+0x17 [../../i386/isa/syscons.c:861] :Xresume1() at Xresume1+0x2b :--- interrupt, eip = 0xf01d0760, esp = 0xf482aeb8, ebp = 0xf482ad68 --- :_doreti(f482af88) at _doreti :_sched_sync() at _sched_sync+0xa4 [../../kern/vfs_subr.c:499] :_kproc_start(udata=f02283ac) at _kproc_start+0x32 [../../kern/init_main.c:311] :_fork_trampoline(21cc1589,c766f025,2521ce05,800008f0,2521d025) at _fork_trampoline+0x30 : :Asking DB for a panic at this point just hangs the system at the :"syncing disks..." prompt. I assume that is the same problem. : :FWIW: All this time, the Alt-Fn still works, until I tried to Alt-Fn :to the Xserver. Then it all hung. : :Anything else I can try? Yah, do a 'ps' from DDB. If Alt-Fn still works the interrupts still work which means it is probably a sleep/wait lockup of some sort. DDB's ps will tell you what processes are waiting on, similar to what 'ps axl' from a shell prompt does. -Matt :Greg. : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-current" in the body of the message : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 00:05:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA12131 for freebsd-current-outgoing; Mon, 4 Jan 1999 00:05:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fep1-orange.clear.net.nz (fep1-orange.clear.net.nz [203.97.32.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA12123; Mon, 4 Jan 1999 00:05:24 -0800 (PST) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep1-orange.clear.net.nz (1.5/1.11) with ESMTP id VAA22588; Mon, 4 Jan 1999 21:04:56 +1300 (NZDT) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.1/8.9.1) id VAA08516; Mon, 4 Jan 1999 21:04:54 +1300 (NZDT) (envelope-from jabley) Date: Mon, 4 Jan 1999 21:04:54 +1300 From: Joe Abley To: "Jordan K. Hubbard" Cc: The Hermit Hacker , "Jonathan M. Bresler" , brian@hyperreal.org, freebsd-current@FreeBSD.ORG, jabley@clear.co.nz Subject: Re: sendmail throughput (was: HEADS UP: Postfix is coming. new uid, gid required.) Message-ID: <19990104210454.A8479@clear.co.nz> References: <36607.915428882@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <36607.915428882@zippy.cdrom.com>; from Jordan K. Hubbard on Sun, Jan 03, 1999 at 09:48:02PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 03, 1999 at 09:48:02PM -0800, Jordan K. Hubbard wrote: > > I think he was suggesting setting up a local news server that everyone can > > connect to to read a "freebsd.*" set of newsgroups... > > Oh, well, if somebody does do this and wants a cname for > news.freebsd.org, they have only to contact hostmaster@freebsd.org > (not me) and it shall be done! Just out of interest... What volume of messages typically flow through the freebsd-* lists? Out of all the subscribers of all the freebsd lists, how many unique subscriber addresses are there? Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 00:10:16 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA12731 for freebsd-current-outgoing; Mon, 4 Jan 1999 00:10:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from houcbs2.houabg.com (houabg.com [206.109.247.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA12720 for ; Mon, 4 Jan 1999 00:10:14 -0800 (PST) (envelope-from dchapman@houabg.com) Received: from sdn-ar-004txhousP268.dialsprint.net by houcbs2.houabg.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1457.7) id ZBAFFA7A; Mon, 4 Jan 1999 02:16:32 -0600 Message-ID: <369077A1.3E637E35@houabg.com> Date: Mon, 04 Jan 1999 02:11:13 -0600 From: "David W. Chapman Jr." X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current Subject: Re: sendmail throughput (was: HEADS UP: Postfix is coming. new uid,gid required.) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey wrote: > On Sun, 3 Jan 1999, David W. Chapman Jr. wrote: > > > I personally would like this so I could just ignore people flaming > > me. But really, I have to check my email every 2 hours or it fills > > up. I would like a news server. > > Privately, this gets suggested once about every year, and nearly > everyone in committers ignores it, because of the greatly increased > noise level rampant on nearly all newsgroups. No one has to ride herd > on these lists, and if it went to newsgroups, to shut down the noise it > would have to be monitored. You *can't* ignore trash, you have to at > least look at it, else you can't tell which ones are the interesting > ones, and no one feels like wading thru hundreds of trash messages. > > I read the FreeBSD newsgroups a great long while back, but stopped > because of the noise; I only started back up when I discovered the lower > noise level on the mailing lists. No one feels like opening up the > lists to extra noise. > > Several people *do* gate their mail into newsgroups you can use to > peruse with, but FreeBSD doesn't allow those groups to post, and isn't > really likely to. > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > > ----------------------------+----------------------------------------------- > Chuck Robey | Interests include any kind of voice or data > chuckr@glue.umd.edu | communications topic, C programming, and Unix. > 213 Lakeside Drive Apt T-1 | > Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) > (301) 220-2114 | and jaunt (NetBSD). > ----------------------------+----------------------------------------------- I see where your comming from, but as I believe Mr Tubutis put it, the ideal setup would to have the mail list "link" the the news server. Therefore those who still would like the email, can keep it, those who like the news group could also use that. I guess filtering spam or junk mail isn't my primary reason for wanting to switch, I think I can keep my mouth shut when another one comes along. I like the newsgroup because when I go to check my email, I don't have to wait a couple of minutes for them all to download. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 00:28:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA14236 for freebsd-current-outgoing; Mon, 4 Jan 1999 00:28:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA14223 for ; Mon, 4 Jan 1999 00:28:16 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id RAA06643; Mon, 4 Jan 1999 17:27:47 +0900 (JST) Message-ID: <369074F2.3D15977@newsguy.com> Date: Mon, 04 Jan 1999 16:59:46 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: How's the latest -SNAP? References: <70708.915394954@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: > > > 2. Are the new bootloaders used? > > Yes. I installed from the 19981226 snap, and it did *not* initialized my hd with the new bootstrap. > > 3. What is the shape of installing from the SNAP in general? Any > > gotchas? > > Should work. Yeah, unless you are behind a Cisco or something? :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com "Heart like a Gabriel, pure and white as ivory, soul like a lucifer, black and cold as a piece of lead." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 00:28:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA14482 for freebsd-current-outgoing; Mon, 4 Jan 1999 00:28:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA14214; Mon, 4 Jan 1999 00:28:13 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id RAA06636; Mon, 4 Jan 1999 17:27:44 +0900 (JST) Message-ID: <36906E81.D5AB960A@newsguy.com> Date: Mon, 04 Jan 1999 16:32:17 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: "Jordan K. Hubbard" , freebsd-current@FreeBSD.ORG, freebsd-admin@FreeBSD.ORG Subject: Re: 3.0-19981226-SNAP/src/ssys.ac is corrupt References: <70028.915381848@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: > > > Can someone fix this? and perhaps guide me as to where there might be a > > mirror that is not corrupt? (I hope the CD wasn't cut from this src). > > There's nothing wrong with this file - the problem is somewhere on > your end, or between our two sites. There's absolutely nothing we > can do about it here. Err... I happen to have seen the exact same problem. I tried four times to install the sys sources, and each time the connection would stop at the precise same point. Maybe my provider uses a Cisco, as you suggest on another message, who knows... But having the connection stop at the precise point four times with me, and at least one more time with the person above (I can't be sure it was the same point with him, but it looks like the same file, at least), while every thing else on a developer install with full sources came correctly... how could that be? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com "Heart like a Gabriel, pure and white as ivory, soul like a lucifer, black and cold as a piece of lead." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 00:34:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA14966 for freebsd-current-outgoing; Mon, 4 Jan 1999 00:34:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from houcbs2.houabg.com (houabg.com [206.109.247.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA14960 for ; Mon, 4 Jan 1999 00:34:05 -0800 (PST) (envelope-from dchapman@houabg.com) Received: from sdn-ar-004txhousP268.dialsprint.net by houcbs2.houabg.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1457.7) id ZBAFFA7J; Mon, 4 Jan 1999 02:40:24 -0600 Message-ID: <36907D39.A49114FE@houabg.com> Date: Mon, 04 Jan 1999 02:35:05 -0600 From: "David W. Chapman Jr." X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current Subject: News Server Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I guess the solution that I'm looking for is to have the mail list post to the news server if we do get one. I don't mind posting to freebsd-current@freebsd.org. But it would better suit me to read from the news server. With news server it I can read messages in retrospect of me initially signing on to the mailing list, and wouldn't have to ask of say the status of the es1370 sound driver. For the people that like to get the new messages in their inbox, they shouldn't notice any difference. Anyone interest in a news server please email me so I can get an idea of whether it is worth pursuing. Please don't cc the mailing list, I don't want to fill up anybody's mailbox who doesn't care about this issue. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 00:35:42 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA15334 for freebsd-current-outgoing; Mon, 4 Jan 1999 00:35:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles324.castles.com [208.214.167.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA15293; Mon, 4 Jan 1999 00:35:23 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id AAA11061; Mon, 4 Jan 1999 00:32:07 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901040832.AAA11061@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel C. Sobral" cc: "Jordan K. Hubbard" , freebsd-current@FreeBSD.ORG, freebsd-admin@FreeBSD.ORG Subject: Re: 3.0-19981226-SNAP/src/ssys.ac is corrupt In-reply-to: Your message of "Mon, 04 Jan 1999 16:32:17 +0900." <36906E81.D5AB960A@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 04 Jan 1999 00:32:06 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > "Jordan K. Hubbard" wrote: > > > > > Can someone fix this? and perhaps guide me as to where there might be a > > > mirror that is not corrupt? (I hope the CD wasn't cut from this src). > > > > There's nothing wrong with this file - the problem is somewhere on > > your end, or between our two sites. There's absolutely nothing we > > can do about it here. > > Err... I happen to have seen the exact same problem. I tried four > times to install the sys sources, and each time the connection would > stop at the precise same point. > > Maybe my provider uses a Cisco, as you suggest on another message, > who knows... But having the connection stop at the precise point > four times with me, and at least one more time with the person above > (I can't be sure it was the same point with him, but it looks like > the same file, at least), while every thing else on a developer > install with full sources came correctly... how could that be? This is usually a "magic byte sequence" which blows the brains out of something in the transit path. We've seen a few of these. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 00:40:39 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA15883 for freebsd-current-outgoing; Mon, 4 Jan 1999 00:40:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oreo.adsu.bellsouth.com (dialup88.adsu.bellsouth.com [205.152.173.88]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA15745; Mon, 4 Jan 1999 00:39:47 -0800 (PST) (envelope-from ck@oreo.adsu.bellsouth.com) Received: (from ck@localhost) by oreo.adsu.bellsouth.com (8.9.1/8.9.1) id DAA52273; Mon, 4 Jan 1999 03:36:56 -0500 (EST) (envelope-from ck) Date: Mon, 4 Jan 1999 03:36:55 -0500 From: Christian Kuhtz To: "Daniel C. Sobral" Cc: "Jordan K. Hubbard" , freebsd-current@FreeBSD.ORG, freebsd-admin@FreeBSD.ORG Subject: Re: 3.0-19981226-SNAP/src/ssys.ac is corrupt Message-ID: <19990104033655.S25538@oreo.adsu.bellsouth.com> References: <70028.915381848@zippy.cdrom.com> <36906E81.D5AB960A@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <36906E81.D5AB960A@newsguy.com>; from Daniel C. Sobral on Mon, Jan 04, 1999 at 04:32:17PM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 01:04:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA19073 for freebsd-current-outgoing; Mon, 4 Jan 1999 01:04:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from enterprise.sanyusan.se (enterprise.sanyusan.se [195.24.160.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA19068 for ; Mon, 4 Jan 1999 01:04:35 -0800 (PST) (envelope-from synker@enterprise.sanyusan.se) Received: (from synker@localhost) by enterprise.sanyusan.se (8.8.8/8.8.8) id KAA14802 for current@freebsd.org; Mon, 4 Jan 1999 10:03:16 +0100 (CET) (envelope-from synker) Date: Mon, 4 Jan 1999 10:03:16 +0100 From: synker To: current@FreeBSD.ORG Subject: Update bootblocks with dedicated disks? Message-ID: <19990104100315.B14764@sanyusan.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any difference in updating my boot blocks because I run all my machines with 'dangerously dedicated' disks. Or could I just follow Robert Nordier's boot.txt? When I installed my boxes I choosed dedicated disks and just marked the root disks bootable during setup. Myabe this is not the right place for this question but I am not sure where to ask it otherwise. My machines run, -current, -stable, 3.0-RELEASE, 2.2.5-RELEASE. === synker - synker@sanyusan.se To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 01:05:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA19154 for freebsd-current-outgoing; Mon, 4 Jan 1999 01:05:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA19146 for ; Mon, 4 Jan 1999 01:05:17 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 24750 invoked by uid 1001); 4 Jan 1999 09:04:51 +0000 (GMT) To: mike@smith.net.au Cc: dcs@newsguy.com, jkh@zippy.cdrom.com, freebsd-current@FreeBSD.ORG, freebsd-admin@FreeBSD.ORG Subject: Re: 3.0-19981226-SNAP/src/ssys.ac is corrupt In-Reply-To: Your message of "Mon, 04 Jan 1999 00:32:06 -0800" References: <199901040832.AAA11061@dingo.cdrom.com> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Mon, 04 Jan 1999 10:04:51 +0100 Message-ID: <24748.915440691@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > There's nothing wrong with this file - the problem is somewhere on > > > your end, or between our two sites. There's absolutely nothing we > > > can do about it here. > > > > Err... I happen to have seen the exact same problem. I tried four > > times to install the sys sources, and each time the connection would > > stop at the precise same point. ... > This is usually a "magic byte sequence" which blows the brains out of > something in the transit path. We've seen a few of these. Maybe it should be investigated more closely. I see the same problem from three different hosts here in Norway, connected via two different ISPs and using very different paths: 1. From hegre.uninett.no: traceroute to usw2.freebsd.org (209.180.6.226), 30 hops max, 40 byte packets 1 unit-gw.unit.no (129.241.1.2) 2.010 ms 3.109 ms 1.165 ms 2 trdS-gw (129.241.181.15) 1.670 ms 5.680 ms 1.326 ms 3 osloS-gw (128.39.46.1) 8.051 ms 8.014 ms 9.111 ms 4 no-gw2.nordu.net (128.39.2.1) 9.539 ms 8.289 ms 8.386 ms 5 sw-gw.nordu.net (193.10.252.149) 19.024 ms 18.836 ms 19.853 ms 6 us-gw.nordu.net (193.10.252.138) 116.364 ms 118.197 ms 117.190 ms 7 gin-nyy-core1.Teleglobe.net (207.45.202.17) 117.310 ms 118.283 ms 117.313 ms 8 gin-nyy-bb1.Teleglobe.net (207.45.223.170) 117.740 ms 119.055 ms 120.379 ms 9 Serial1-0-1.GW2.NYC2.ALTER.NET (157.130.5.217) 120.275 ms Serial0-1-0.GW2.NYC2.ALTER.NET (157.130.4.165) 119.525 ms Serial1-0-1.GW2.NYC2.ALTER.NET (157.130.5.217) 118.513 ms 10 144.ATM2-0.XR2.NYC1.ALTER.NET (146.188.178.150) 122.257 ms 118.006 ms 119.339 ms 11 194.ATM3-0.TR2.NYC1.ALTER.NET (146.188.178.198) 119.394 ms 118.765 ms 121.182 ms 12 104.ATM7-0.TR2.CHI4.ALTER.NET (146.188.136.153) 141.189 ms 141.879 ms 140.252 ms 13 198.ATM6-0.XR2.CHI6.ALTER.NET (146.188.209.1) 141.568 ms 141.105 ms 140.681 ms 14 190.ATM8-0-0.GW2.MSP1.ALTER.NET (146.188.209.125) 154.812 ms 154.971 ms 155.309 ms 15 uswmsp-gw.customer.ALTER.NET (157.130.96.166) 149.941 ms 149.431 ms 150.794 ms 16 207.225.159.220 (207.225.159.220) 150.013 ms 149.056 ms 148.990 ms 17 usw2.freebsd.org (209.180.6.226) 150.841 ms 149.249 ms 151.275 ms 2. From newsfeed1.telia.no: traceroute to usw2.freebsd.org (209.180.6.226), 30 hops max, 40 byte packets 1 194.19.1.49 (194.19.1.49) 0.963 ms 0.854 ms 0.834 ms 2 194.19.1.94 (194.19.1.94) 1.441 ms 1.665 ms 1.308 ms 3 194.19.1.146 (194.19.1.146) 19.590 ms 20.661 ms 19.916 ms 4 apv-c2-fddi5-0-core.stockholm.telia.net (194.22.194.253) 15.771 ms 14.808 ms 14.310 ms 5 apv-i1-feth4-0-0-ix.stockholm.telia.net (195.67.232.8) 14.443 ms 16.892 ms 15.514 ms 6 ny-i1-pos4-0-0-int-newyork.telia.net (194.17.0.250) 111.639 ms 110.964 ms 110.338 ms 7 209.95.130.138 (209.95.130.138) 112.581 ms 113.056 ms 111.801 ms 8 MAE-East-hssi2-0-int.vienna.telia.net (209.95.128.37) 119.952 ms 118.003 ms 117.990 ms 9 maeeast2.bbnplanet.net (198.32.186.2) 131.367 ms 123.608 ms 127.574 ms 10 p2-2.vienna1-nbr2.bbnplanet.net (4.0.1.93) 123.232 ms 117.797 ms 120.134 ms 11 p3-1.nyc4-nbr2.bbnplanet.net (4.0.3.130) 120.709 ms 127.382 ms 121.752 ms 12 p1-0.nyc4-nbr3.bbnplanet.net (4.0.5.26) 123.863 ms 124.764 ms 123.996 ms 13 p2-1.chicago1-nbr1.bbnplanet.net (4.0.3.121) 146.194 ms 144.213 ms 140.665 ms 14 p10-0-0.chicago1-br1.bbnplanet.net (4.0.5.89) 150.874 ms 139.794 ms 138.179 ms 15 h1-0.minneapol1-cr1.bbnplanet.net (4.0.2.18) 151.672 ms 150.914 ms 151.956 ms 16 h1-0.uswest-mn.bbnplanet.net (4.0.246.254) 154.703 ms 148.461 ms 148.034 ms 17 207.225.159.220 (207.225.159.220) 149.299 ms 154.605 ms 151.377 ms 18 usw2.freebsd.org (209.180.6.226) 167.212 ms 156.491 ms * The only points in common for these two traceroutes are usw2.freebsd.org, and the router at 207.225.159.220. That should narrow the field sufficiently that it's possible to investigate. It's the same file I'm trying to fetch (3.0-19981226-SNAP/src/ssys.ac). Also, I've tried it from both FreeBSD and SunOS 4.1.4 clients. Same problem. A tcpdump shows no packets from usw2.freebsd.org after a certain point, which is consistent with the FTP session hanging: ... 10:01:22.655241 209.180.6.226.59113 > 129.241.1.42.1169: . 156985:158433(1448) ack 1 win 17376 (DF) [tos 0x8] 10:01:22.655569 209.180.6.226.59113 > 129.241.1.42.1169: . 158433:159881(1448) ack 1 win 17376 (DF) [tos 0x8] 10:01:22.658650 209.180.6.226.59113 > 129.241.1.42.1169: . 159881:161329(1448) ack 1 win 17376 (DF) [tos 0x8] 10:01:22.659172 209.180.6.226.59113 > 129.241.1.42.1169: . 161329:162777(1448) ack 1 win 17376 (DF) [tos 0x8] 10:01:22.665906 129.241.1.42.1169 > 209.180.6.226.59113: . ack 159881 win 17376 (DF) [tos 0x8] 10:01:22.669349 129.241.1.42.1169 > 209.180.6.226.59113: . ack 162777 win 17376 (DF) [tos 0x8] 10:01:22.679161 209.180.6.226.59113 > 129.241.1.42.1169: . 162777:164225(1448) ack 1 win 17376 (DF) [tos 0x8] 10:01:22.680143 209.180.6.226.59113 > 129.241.1.42.1169: . 164225:165673(1448) ack 1 win 17376 (DF) [tos 0x8] 10:01:22.695234 129.241.1.42.1169 > 209.180.6.226.59113: . ack 165673 win 17376 (DF) [tos 0x8] 10:01:22.789428 209.180.6.226.59113 > 129.241.1.42.1169: P 165673:167121(1448) ack 1 win 17376 (DF) [tos 0x8] 10:01:22.914620 129.241.1.42.1169 > 209.180.6.226.59113: . ack 167121 win 17376 (DF) [tos 0x8] (no more from the remote end. Always at the same point.) Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 01:12:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA19591 for freebsd-current-outgoing; Mon, 4 Jan 1999 01:12:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from top.worldcontrol.com (snblitz.sc.scruznet.com [165.227.132.84]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA19586 for ; Mon, 4 Jan 1999 01:12:10 -0800 (PST) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 2037 invoked by uid 100); 4 Jan 1999 09:22:57 -0000 Date: Mon, 4 Jan 1999 01:22:57 -0800 To: "David W. Chapman Jr." Cc: freebsd-current Subject: Re: Wine-Latest Message-ID: <19990104012257.A2028@top.worldcontrol.com> Mail-Followup-To: "David W. Chapman Jr." , freebsd-current References: <369005AD.FC440AAC@houabg.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <369005AD.FC440AAC@houabg.com>; from David W. Chapman Jr. on Sun, Jan 03, 1999 at 06:05:01PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 03, 1999 at 06:05:01PM -0600, David W. Chapman Jr. wrote: > Anyone been able to compile the latest version of wine with egcs-1.1 I compile the cvs version of wine about twice a week with pgcs 1.1.1, which I realize isn't really answering your question. Also, what do you mean by "the latest version"? -- Brian Litzinger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 01:33:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA21267 for freebsd-current-outgoing; Mon, 4 Jan 1999 01:33:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (root.com [208.221.12.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA21262 for ; Mon, 4 Jan 1999 01:33:06 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id BAA23794; Mon, 4 Jan 1999 01:30:23 -0800 (PST) Message-Id: <199901040930.BAA23794@implode.root.com> To: sthaug@nethelp.no cc: freebsd-current@FreeBSD.ORG Subject: Re: 3.0-19981226-SNAP/src/ssys.ac is corrupt In-reply-to: Your message of "Mon, 04 Jan 1999 10:04:51 +0100." <24748.915440691@verdi.nethelp.no> From: David Greenman Reply-To: dg@root.com Date: Mon, 04 Jan 1999 01:30:23 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Maybe it should be investigated more closely. I see the same problem >from three different hosts here in Norway, connected via two different >ISPs and using very different paths: > >1. From hegre.uninett.no: > >traceroute to usw2.freebsd.org (209.180.6.226), 30 hops max, 40 byte packets > 1 unit-gw.unit.no (129.241.1.2) 2.010 ms 3.109 ms 1.165 ms > 2 trdS-gw (129.241.181.15) 1.670 ms 5.680 ms 1.326 ms > 3 osloS-gw (128.39.46.1) 8.051 ms 8.014 ms 9.111 ms > 4 no-gw2.nordu.net (128.39.2.1) 9.539 ms 8.289 ms 8.386 ms > 5 sw-gw.nordu.net (193.10.252.149) 19.024 ms 18.836 ms 19.853 ms > 6 us-gw.nordu.net (193.10.252.138) 116.364 ms 118.197 ms 117.190 ms > 7 gin-nyy-core1.Teleglobe.net (207.45.202.17) 117.310 ms 118.283 ms 117.313 ms > 8 gin-nyy-bb1.Teleglobe.net (207.45.223.170) 117.740 ms 119.055 ms 120.379 ms > 9 Serial1-0-1.GW2.NYC2.ALTER.NET (157.130.5.217) 120.275 ms Serial0-1-0.GW2.NYC2.ALTER.NET (157.130.4.165) 119.525 ms Serial1-0-1.GW2.NYC2.ALTER.NET (157.130.5.217) 118.513 ms >10 144.ATM2-0.XR2.NYC1.ALTER.NET (146.188.178.150) 122.257 ms 118.006 ms 119.339 ms >11 194.ATM3-0.TR2.NYC1.ALTER.NET (146.188.178.198) 119.394 ms 118.765 ms 121.182 ms >12 104.ATM7-0.TR2.CHI4.ALTER.NET (146.188.136.153) 141.189 ms 141.879 ms 140.252 ms >13 198.ATM6-0.XR2.CHI6.ALTER.NET (146.188.209.1) 141.568 ms 141.105 ms 140.681 ms >14 190.ATM8-0-0.GW2.MSP1.ALTER.NET (146.188.209.125) 154.812 ms 154.971 ms 155.309 ms >15 uswmsp-gw.customer.ALTER.NET (157.130.96.166) 149.941 ms 149.431 ms 150.794 ms >16 207.225.159.220 (207.225.159.220) 150.013 ms 149.056 ms 148.990 ms >17 usw2.freebsd.org (209.180.6.226) 150.841 ms 149.249 ms 151.275 ms > >2. From newsfeed1.telia.no: > >traceroute to usw2.freebsd.org (209.180.6.226), 30 hops max, 40 byte packets > 1 194.19.1.49 (194.19.1.49) 0.963 ms 0.854 ms 0.834 ms > 2 194.19.1.94 (194.19.1.94) 1.441 ms 1.665 ms 1.308 ms > 3 194.19.1.146 (194.19.1.146) 19.590 ms 20.661 ms 19.916 ms > 4 apv-c2-fddi5-0-core.stockholm.telia.net (194.22.194.253) 15.771 ms 14.808 ms 14.310 ms > 5 apv-i1-feth4-0-0-ix.stockholm.telia.net (195.67.232.8) 14.443 ms 16.892 ms 15.514 ms > 6 ny-i1-pos4-0-0-int-newyork.telia.net (194.17.0.250) 111.639 ms 110.964 ms 110.338 ms > 7 209.95.130.138 (209.95.130.138) 112.581 ms 113.056 ms 111.801 ms > 8 MAE-East-hssi2-0-int.vienna.telia.net (209.95.128.37) 119.952 ms 118.003 ms 117.990 ms > 9 maeeast2.bbnplanet.net (198.32.186.2) 131.367 ms 123.608 ms 127.574 ms >10 p2-2.vienna1-nbr2.bbnplanet.net (4.0.1.93) 123.232 ms 117.797 ms 120.134 ms >11 p3-1.nyc4-nbr2.bbnplanet.net (4.0.3.130) 120.709 ms 127.382 ms 121.752 ms >12 p1-0.nyc4-nbr3.bbnplanet.net (4.0.5.26) 123.863 ms 124.764 ms 123.996 ms >13 p2-1.chicago1-nbr1.bbnplanet.net (4.0.3.121) 146.194 ms 144.213 ms 140.665 ms >14 p10-0-0.chicago1-br1.bbnplanet.net (4.0.5.89) 150.874 ms 139.794 ms 138.179 ms >15 h1-0.minneapol1-cr1.bbnplanet.net (4.0.2.18) 151.672 ms 150.914 ms 151.956 ms >16 h1-0.uswest-mn.bbnplanet.net (4.0.246.254) 154.703 ms 148.461 ms 148.034 ms >17 207.225.159.220 (207.225.159.220) 149.299 ms 154.605 ms 151.377 ms >18 usw2.freebsd.org (209.180.6.226) 167.212 ms 156.491 ms * > >The only points in common for these two traceroutes are usw2.freebsd.org, >and the router at 207.225.159.220. That should narrow the field >sufficiently that it's possible to investigate. It's the same file I'm It's not the inbound path that needs to be analyzed - it's the outbound path. Someone on the usw2 machine will need to do traces to your different IPs and see what is common. I'll guess that a lot more is common than just the machine and one router. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 01:46:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA22301 for freebsd-current-outgoing; Mon, 4 Jan 1999 01:46:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-27-dbn.dial-up.net [196.34.155.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA22289 for ; Mon, 4 Jan 1999 01:46:22 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id LAA02842; Mon, 4 Jan 1999 11:44:52 +0200 (SAT) From: Robert Nordier Message-Id: <199901040944.LAA02842@ceia.nordier.com> Subject: Re: Update bootblocks with dedicated disks? In-Reply-To: <19990104100315.B14764@sanyusan.se> from synker at "Jan 4, 99 10:03:16 am" To: synker@sanyusan.se (synker) Date: Mon, 4 Jan 1999 11:44:48 +0200 (SAT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG synker wrote: > Is there any difference in updating my boot blocks because I run all my > machines with 'dangerously dedicated' disks. > > Or could I just follow Robert Nordier's boot.txt? > > When I installed my boxes I choosed dedicated disks and just marked the > root disks bootable during setup. The disklabel command should handle this transparently. I've updated boot.txt to mention dangerously dedicated disks. > > Myabe this is not the right place for this question but I am not sure > where to ask it otherwise. This is probably the right place, at least until everything is fully- documented. > > My machines run, -current, -stable, 3.0-RELEASE, 2.2.5-RELEASE. I've used the new boot blocks, together with /boot/loader, on a 2.2.5 machine myself. So, once you have the binaries, you could even install them on all the machines, if you wanted to. Though, apart from consistency (or if you want multiple FreeBSD slices per disk), I guess there's really no compelling reason to do this. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 01:58:59 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA23892 for freebsd-current-outgoing; Mon, 4 Jan 1999 01:58:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from enterprise.sanyusan.se (enterprise.sanyusan.se [195.24.160.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA23883 for ; Mon, 4 Jan 1999 01:58:54 -0800 (PST) (envelope-from synker@enterprise.sanyusan.se) Received: (from synker@localhost) by enterprise.sanyusan.se (8.8.8/8.8.8) id KAA15343; Mon, 4 Jan 1999 10:57:20 +0100 (CET) (envelope-from synker) Date: Mon, 4 Jan 1999 10:57:20 +0100 From: synker To: Robert Nordier Cc: current@FreeBSD.ORG Subject: Re: Update bootblocks with dedicated disks? Message-ID: <19990104105719.A15320@sanyusan.se> References: <19990104100315.B14764@sanyusan.se> <199901040944.LAA02842@ceia.nordier.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: =?iso-8859-1?Q?=3C199901040944=2ELAA02842=40ceia=2Enordier=2Ecom=3E=3B_f?= =?iso-8859-1?Q?rom_Robert_Nordier_on_M=E5n=2C_Jan_04=2C_1999_at_11:44:48?= =?iso-8859-1?Q?am_+0200?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maybe I could also ask if it recommended to use 'dangerously dedicated' disks on a FreeBSD server or not. Some ppl in both freebsd mailinglista and in news said that it is not recommended to use the 'dangerrously dedicated' disks since there have been some reported trouble with those? Anybody know of what kind of trouble? And if I should use 'standard' disks with slices instead how can I get FreeBSD to boot? Last time I tried this 'BootEasy' popped up after reboot and showed: F1: BSD F2: ???? or something... Since FreeBSd is the only OS on my boxes I couldnt boot by pressing F1. I had to use a floppy and type in the kernel location by hand at the boot prompt. Best regards, === synker - synker@sanyusan.se To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 02:09:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA24975 for freebsd-current-outgoing; Mon, 4 Jan 1999 02:09:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA24964 for ; Mon, 4 Jan 1999 02:09:47 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id VAA30233; Mon, 4 Jan 1999 21:09:19 +1100 Date: Mon, 4 Jan 1999 21:09:19 +1100 From: Bruce Evans Message-Id: <199901041009.VAA30233@godzilla.zeta.org.au> To: rnordier@nordier.com, rvb@cs.cmu.edu Subject: Re: New boot blocks for serial console ... Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> But there are more loaders today. It looks like >> sys/boot/i386/libi386/comconsole.c >> needs to be handed edited: >> #define COMPORT 0x3f8 >> #define COMSPEED 9600 >> to >> #define COMPORT 0x2f8 >> #define COMSPEED 57600 >> >> I guess that this should be pulled out to the makefile building the >> lib. >> >> The two files above are the only ones that contain "3f8" so I guess >> that nothing else needs to be changed. > >Those should be the only modifications required. > >Otherwise, your comments are reasonable and should be taken into >account during an upcoming revision. Though, of course, you'd be >welcome to simply commit the suggested improvements yourself. The port number and speed should be named BOOT_COMCONSOLE_PORT and BOOT_COMCONSOLE_SPEED, and should be settable /etc/make.conf[.local]. This is documented in etc/make.conf and biosboot/README.serial. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 02:37:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA26801 for freebsd-current-outgoing; Mon, 4 Jan 1999 02:37:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-40-dbn.dial-up.net [196.34.155.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA26785 for ; Mon, 4 Jan 1999 02:36:41 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id MAA00391; Mon, 4 Jan 1999 12:34:02 +0200 (SAT) From: Robert Nordier Message-Id: <199901041034.MAA00391@ceia.nordier.com> Subject: Re: New boot blocks for serial console ... In-Reply-To: <199901041009.VAA30233@godzilla.zeta.org.au> from Bruce Evans at "Jan 4, 99 09:09:19 pm" To: bde@zeta.org.au (Bruce Evans) Date: Mon, 4 Jan 1999 12:33:55 +0200 (SAT) Cc: rnordier@nordier.com, rvb@cs.cmu.edu, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > >> But there are more loaders today. It looks like > >> sys/boot/i386/libi386/comconsole.c > >> needs to be handed edited: > >> #define COMPORT 0x3f8 > >> #define COMSPEED 9600 > >> to > >> #define COMPORT 0x2f8 > >> #define COMSPEED 57600 > >> > >> I guess that this should be pulled out to the makefile building the > >> lib. > >> > >> The two files above are the only ones that contain "3f8" so I guess > >> that nothing else needs to be changed. > > > >Those should be the only modifications required. > > > >Otherwise, your comments are reasonable and should be taken into > >account during an upcoming revision. Though, of course, you'd be > >welcome to simply commit the suggested improvements yourself. > > The port number and speed should be named BOOT_COMCONSOLE_PORT and > BOOT_COMCONSOLE_SPEED, and should be settable /etc/make.conf[.local]. > This is documented in etc/make.conf and biosboot/README.serial. Thanks, I wasn't aware that etc/make.conf settings affected the old boot blocks. I'll bring the new stuff into line. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 03:18:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA00404 for freebsd-current-outgoing; Mon, 4 Jan 1999 03:18:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-10-dbn.dial-up.net [196.34.155.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA00399 for ; Mon, 4 Jan 1999 03:18:32 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id NAA00747; Mon, 4 Jan 1999 13:16:39 +0200 (SAT) From: Robert Nordier Message-Id: <199901041116.NAA00747@ceia.nordier.com> Subject: Re: Update bootblocks with dedicated disks? In-Reply-To: <19990104105719.A15320@sanyusan.se> from synker at "Jan 4, 99 10:57:20 am" To: synker@sanyusan.se (synker) Date: Mon, 4 Jan 1999 13:16:36 +0200 (SAT) Cc: rnordier@nordier.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG synker wrote: > Maybe I could also ask if it recommended to use 'dangerously dedicated' > disks on a FreeBSD server or not. > > Some ppl in both freebsd mailinglista and in news said that it is not > recommended to use the 'dangerrously dedicated' disks since there have been > some reported trouble with those? Anybody know of what kind of trouble? The trouble with "dangerously dedicated" disks is that they appear, to everything besides FreeBSD, to contain a corrupted "partition" table (slice table, in BSD terms). If you let some non-FreeBSD disk utility near the disk, it may decide to "fix" the damage. Also, according to the FAQ, some BIOSes may refuse to boot a disk if they believe the table is invalid. Folks who are more orientated to UNIX on non-PC hardware may prefer an unsliced (dangerously dedicated) disk for consistency. So, unless you are strongly in favor of unsliced disks, you probably don't want to use them. > > And if I should use 'standard' disks with slices instead how can I get FreeBSD > to boot? Last time I tried this 'BootEasy' popped up after reboot and showed: > > F1: BSD > F2: ???? or something... > > Since FreeBSd is the only OS on my boxes I couldnt boot by pressing F1. I had > to use a floppy and type in the kernel location by hand at the boot prompt. You probably want the sysinstall "Standard MBR" option, or the fdisk equivalent, rather than boot0/booteasy. With this option, the disk is dedicated to one OS, but not dangerously so. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 03:39:50 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA01882 for freebsd-current-outgoing; Mon, 4 Jan 1999 03:39:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA01873 for ; Mon, 4 Jan 1999 03:39:28 -0800 (PST) (envelope-from netchild@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.1a/1998121400) with ESMTP id MAA12654; Mon, 4 Jan 1999 12:37:51 +0100 (CET) Received: from wurzelausix (quadratix.cs.uni-sb.de [134.96.222.2]) by cs.uni-sb.de (8.9.1a/1998121400) with ESMTP id MAA20958; Mon, 4 Jan 1999 12:37:46 +0100 (CET) Received: from wurzelausix.cs.uni-sb.de (IDENT:3Bd2sLzxE1lWxWEufAbheFpPXllgocv1@localhost [127.0.0.1]) by wurzelausix (8.9.1/wjp/19980821) with ESMTP id MAA10608; Mon, 4 Jan 1999 12:37:32 +0100 (CET) Message-Id: <199901041137.MAA10608@wurzelausix> Date: Mon, 4 Jan 1999 12:37:29 +0100 (CET) From: Alexander Leidinger Subject: Re: nlpt & polling mode didn't work To: nsouch@teaser.fr cc: current@FreeBSD.ORG, joerg_wunsch@uriah.heep.sax.de In-Reply-To: <19981229221203.55044@breizh.prism.uvsq.fr> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 29 Dec, Nicolas Souchu wrote: >>$Subject anymore after cvsup (98.12.24). >>The working one is around release (sorry, can't be more specific). > > September, October...? ~1 day before release. >>The problem: >>It takes a looooong time to send data to the printer. > > Printing is ok? I think (nobody wants to wait more than 15 minutes for the page). BTW: I have only 3rd person access to it. Its the system of my brother, and hi is only an user. > This is polling... and interrupts? Its an additional 3rd party interface card (a little bit old). Only polling possible (no modern features like e.g. ECP). Over the motherboard chipset everything is fine (only interrupts tested). > What's your chipset? The 3rd party cards have MP101D HC138 ALS00A 17KD (Texas Instruments?) and HM82C11C 9739 C79N5 on them. Joerg Wunsch wrote: > Btw., the question about which printer also belongs here. There are two printers connected, a HP OfficeJet 635 via the on board chipset and a Kyocera FS-600 (laser) via the 3rd party card. Connecting the laser to the motherboard port works fine, but on the 3rd party card it needs ages to print a page. As already mentioned, this didn't happen with ~3.0-release. Bye, Alexander. -- http://netchild.home.pages.de A.Leidinger @ wurzelausix.cs.uni-sb.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 04:17:39 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA07037 for freebsd-current-outgoing; Mon, 4 Jan 1999 04:17:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gw1.pl.cp (redion.nttmcl.com [216.69.69.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA07032 for ; Mon, 4 Jan 1999 04:17:37 -0800 (PST) (envelope-from astralblue@usa.net) Received: from localhost (gene@localhost) by gw1.pl.cp (8.9.1/8.9.1) with SMTP id EAA06421 for ; Mon, 4 Jan 1999 04:17:07 -0800 (PST) (envelope-from astralblue@usa.net) X-Authentication-Warning: gw1.pl.cp: gene owned process doing -bs Date: Mon, 4 Jan 1999 04:17:07 -0800 (PST) From: "Eugene M. Kim" X-Sender: gene@gw1.pl.cp To: FreeBSD-current Mailing List Subject: bin/3246: mtree -c should escape special and whitespace characters Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Could anybody please review and commit the patch in the followup of bin/3246? It enables the URL-style escaping and unescaping of certain characters in mtree(8) filenames so that mtree can handle filenames with special or whitespace characters. For example, the filename "I have spaces" will be recorded as "I%20have%20spaces" in the mtree spec file. There is an incompatibility issue regarding preexisting mtree spec files, which is addressed as well in the followup. Thanks, Eugene -- Eugene M. Kim "Is your music unpopular? Make it popular; make music which people like, or make people who like your music." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 05:44:43 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA14688 for freebsd-current-outgoing; Mon, 4 Jan 1999 05:44:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dns.webwizard.net.mx (webwizard.net.mx [148.245.50.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA14681 for ; Mon, 4 Jan 1999 05:44:40 -0800 (PST) (envelope-from eculp@webwizard.org.mx) Received: from webwizard.org.mx (webwizard.net.mx [148.245.50.27]) by dns.webwizard.net.mx (8.9.1/8.9.1) with ESMTP id HAA33368 for ; Mon, 4 Jan 1999 07:44:12 -0600 (CST) (envelope-from eculp@webwizard.org.mx) Message-ID: <3690C5AB.67B7D987@webwizard.org.mx> Date: Mon, 04 Jan 1999 07:44:12 -0600 From: Edwin Culp X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-current@FreeBSD.ORG" Subject: Make world this morning. Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Found a problem with this morning´s freshly cvsuped sources, just in case no one else has seen it. /usr/obj/elf/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr -o boot2.ld -P 1 boot2.bin kernel: ver=0.87 size=6d0 load=9000 entry=9010 map=16M pgctl=1:1 client: fmt=bin size=143c text=0 data=0 bss=0 entry=0 output: fmt=bin size=1d0c text=200 data=1b0c org=0 entry=0 244 bytes available dd if=boot2.ld of=boot2 obs=7680 conv=osync 2>/dev/null ===> sys/boot/i386/libi386 make: don't know how to make machine/ansi.h. Stop *** Error code 2 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Thanks ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 05:52:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA15977 for freebsd-current-outgoing; Mon, 4 Jan 1999 05:52:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ozz.etrust.ru ([195.2.84.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA15966 for ; Mon, 4 Jan 1999 05:52:16 -0800 (PST) (envelope-from osa@etrust.ru) Received: from localhost (localhost [127.0.0.1]) by ozz.etrust.ru (8.9.1/8.9.1) with ESMTP id QAA38227 for ; Mon, 4 Jan 1999 16:51:23 +0300 (MSK) (envelope-from osa@etrust.ru) Date: Mon, 4 Jan 1999 16:51:22 +0300 (MSK) From: oZZ!!! To: current@FreeBSD.ORG Subject: Can't compile ELF 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! Today, after cvsup source tree for my 3.0-CURRENT i try to compile kernel in ELF ..... loading kernel ad1848.o: In function `ad1816_attach': ad1848.o(.text+0x1a3): undefined reference to `ad1816_write' ad1848.o(.text+0x1b0): undefined reference to `ad1816_write' ad1848.o(.text+0x1bd): undefined reference to `ad1816_write' ad1848.o(.text+0x1cd): undefined reference to `ad1816_write' ad1848.o(.text+0x1da): undefined reference to `ad1816_write' ad1848.o(.text+0x1e7): more undefined references to `ad1816_write' follow ad1848.o: In function `ad1816_attach': ad1848.o(.text+0x1fd): undefined reference to `ad1816_reinit' ad1848.o(.text+0x203): undefined reference to `ad1816_mixer_reset' *** Error code 1 Stop. Rgdz, Osokin Sergey aka oZZ, osa@etrust.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 05:56:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA16406 for freebsd-current-outgoing; Mon, 4 Jan 1999 05:56:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-59-dbn.dial-up.net [196.34.155.123]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA16400 for ; Mon, 4 Jan 1999 05:56:18 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id PAA02020; Mon, 4 Jan 1999 15:54:35 +0200 (SAT) From: Robert Nordier Message-Id: <199901041354.PAA02020@ceia.nordier.com> Subject: Re: Multiple Partions In-Reply-To: <368FD169.4BC88D65@idsmail.com> from Zapper at "Jan 3, 99 02:22:02 pm" To: zapper@idsmail.com (Zapper) Date: Mon, 4 Jan 1999 15:54:31 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Zapper wrote: > I have Win 95 and FreeBSD 3.0-Current installed on my computer. I have > 2 hard drives installed with the Win95 OS on the "master" a 1.5G > Western Digital and FreeBSD on the "slave" a 4.3G Quantum Bigfoot. The > 4.3 is partitioned with about 2.5G of space for FreeBSD with the > remaining space allocated to Win 95 programs. When I installed FreeBSD > from the cd I created a "slice" so I could boot to either Win95 or > FreeBSD i.e.: > > F1 DOS > F5 FreeBSD > > Win95 crashed and I was forced to reinstall it, which I did without > formatting so as not to mess up my boot partition or so I had hoped. > To make a long story short, while I am still able to boot to FreeBSD > and run it, I keep having problems that have just started since I > reinstalled Win95. > Problems are, when I do "make buildworld" in /usr/src , it crashes, > but the errors are different everytime with the most popular error being > > cc: Internal compiler error: program cc1 got fatal signal 11 > *** Error code 1 > > Stop. > > I've tried "make buildword" , "make -DNOCLEAN buildword" and just > plain ole "make world" with no success. > > 2nd problem is, when I try to compile a new kernel it crashes also > with pretty much different errors everytime. I'd suspect that these errors (and perhaps even the original Win 95 crash) may be due to hardware problems, quite likely memory-related. It is fairly common to find that FreeBSD (and other UNIX-like OSes) will crash in these circumstances, even though other OSes seem to run OK, as UNIX is just more of a "workout" for the hardware. > Keep in mind that I have had relatively "no" real problems until I > reinstalled Win 95 so having said all that, my question is, is there a > way to reinstall the slice or redefine the partition? By using the FreeBSD dmesg, fdisk, and disklabel commands, you should be able to display enough information about the disk, slices, and partitions to decide whether the parameters are reasonable. And you can use fdisk and disklabel to correct any problems, if necessary. I'd be fairly surprised if slice/partition problems caused the errors you are seeing, though. > Also, since it > now looks like I'm going to have to "fully" reinstall Win 95 with format > I know I will totally obliterate my slice. Is there a way to save my > slice and partition info? Windows will probably overwrite your boot manager, but is unlikely otherwise to cause problems, as long as you don't allow it to "delete partitions" or "use whole disk" or something. Even after a format, the FreeBSD slice should remain intact. You can use the Windows fdisk utility to activate the FreeBSD partition, boot FreeBSD, and then use sysinstall to reinstall the boot manager. You could save your raw slice and partition info using dd(1), for example, something like dd if=/dev/rwd1 of=slice.keep count=1 dd if=/dev/rwd1a of=part.keep skip=1 count=1 should do it. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 05:59:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA16855 for freebsd-current-outgoing; Mon, 4 Jan 1999 05:59:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA16846; Mon, 4 Jan 1999 05:58:56 -0800 (PST) (envelope-from jmb) Date: Mon, 4 Jan 1999 05:58:56 -0800 (PST) Message-Id: <199901041358.FAA16846@hub.freebsd.org> From: "Jonathan M. Bresler" To: jabley@clear.co.nz CC: jkh@zippy.cdrom.com, scrappy@hub.org, brian@hyperreal.org, freebsd-current@FreeBSD.ORG, jabley@clear.co.nz In-reply-to: <19990104210454.A8479@clear.co.nz> (message from Joe Abley on Mon, 4 Jan 1999 21:04:54 +1300) Subject: Re: sendmail throughput (was: HEADS UP: Postfix is coming. new uid, gid required.) References: <36607.915428882@zippy.cdrom.com> <19990104210454.A8479@clear.co.nz> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Date: Mon, 4 Jan 1999 21:04:54 +1300 > From: Joe Abley > > Just out of interest... What volume of messages typically flow through the > freebsd-* lists? Out of all the subscribers of all the freebsd lists, how > many unique subscriber addresses are there? over 22,000 unique email addresses. Volume: posfix (for all of yesterday, sunday jan 3rd) sent: 329956 deferred: 241607 bounced: 2167 Statistics from Tue Dec 29 15:00:06 1998 M msgsfr bytes_from msgsto bytes_to Mailer 0 0 0K 9671 26368K prog 1 0 0K 3934 17934K *file* 3 54308 213977K 27341 116440K local 4 25 52K 969 4274K smtp 5 962 3853K 12480 54824K esmtp 6 8570 33944K 171456 652675K smtp8 ======================================== T 63865 251826K 225851 872515K jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 06:08:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA18139 for freebsd-current-outgoing; Mon, 4 Jan 1999 06:08:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-12-dbn.dial-up.net [196.34.155.76]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA18130 for ; Mon, 4 Jan 1999 06:08:19 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id QAA02285; Mon, 4 Jan 1999 16:06:39 +0200 (SAT) From: Robert Nordier Message-Id: <199901041406.QAA02285@ceia.nordier.com> Subject: Re: Make world this morning. In-Reply-To: <3690C5AB.67B7D987@webwizard.org.mx> from Edwin Culp at "Jan 4, 99 07:44:12 am" To: eculp@webwizard.org.mx (Edwin Culp) Date: Mon, 4 Jan 1999 16:06:37 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Edwin Culp wrote: > Found a problem with this morning´s freshly cvsuped sources, just in > case no one else has seen it. > > /usr/obj/elf/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr -o > boot2.ld > -P 1 boot2.bin > kernel: ver=0.87 size=6d0 load=9000 entry=9010 map=16M pgctl=1:1 > client: fmt=bin size=143c text=0 data=0 bss=0 entry=0 > output: fmt=bin size=1d0c text=200 data=1b0c org=0 entry=0 > 244 bytes available > dd if=boot2.ld of=boot2 obs=7680 conv=osync 2>/dev/null > ===> sys/boot/i386/libi386 > make: don't know how to make machine/ansi.h. Stop > *** Error code 2 > > Stop. > *** Error code 1 Try changing to /sys/boot and doing a "make cleandepend". That usually sorts this out. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 06:42:41 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA21653 for freebsd-current-outgoing; Mon, 4 Jan 1999 06:42:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bfc.dk ([194.192.110.140]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA21645 for ; Mon, 4 Jan 1999 06:42:35 -0800 (PST) (envelope-from npe@bfc.dk) From: npe@bfc.dk Received: by bfc.dk(Lotus SMTP MTA SMTP v4.6 (462.2 9-3-1997)) id 412566EF.00505510 ; Mon, 4 Jan 1999 15:37:26 +0100 X-Lotus-FromDomain: BFC-DATA@BFC To: freebsd-current@FreeBSD.ORG Message-ID: <412566EF.004E9F27.00@bfc.dk> Date: Mon, 4 Jan 1999 15:37:30 +0100 Subject: Kernel configurator Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Would a thing like a kernel configurator with a user interface be appreciated ? Personally I think that it would be a great plus for new users.. .(The linux thing is really easy to use..) If I get enough positive respons then I'll start making a user interface that works and is easy configureable for new options. Regards, Nicolai Petri To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 06:46:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA22042 for freebsd-current-outgoing; Mon, 4 Jan 1999 06:46:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fourier.physics.purdue.edu (fourier.physics.purdue.edu [128.210.146.43]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA22033 for ; Mon, 4 Jan 1999 06:46:52 -0800 (PST) (envelope-from jonsmith@fourier.physics.purdue.edu) Received: from localhost (jonsmith@localhost) by fourier.physics.purdue.edu (8.8.8/8.8.8) with SMTP id JAA08525; Mon, 4 Jan 1999 09:40:34 GMT (envelope-from jonsmith@fourier.physics.purdue.edu) Date: Mon, 4 Jan 1999 09:40:34 +0000 (GMT) From: Jonathan Smith To: npe@bfc.dk cc: freebsd-current@FreeBSD.ORG Subject: Re: Kernel configurator In-Reply-To: <412566EF.004E9F27.00@bfc.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 Personally, I think it would be nice. I've been doing my own kernels by hand, but it would be nicer. Howerver, my complaint with the Linux one is that it is graphical only. Perhaps one that would attempt an X connection then default to curses in a text wnindow? j "If kisses could kill (gulp), that one would have flattened several small towns...." Vir Cotto, Babylon 5 "Tu was du willst." Die Unendliche Geschichte, von Michael Ende "Do as you wish." The Neverending Story, by Michael Ende The Microsoft Soloution, "newfs && make reinstall" Jon C. Smith (765)49-48628 PHYS 31h jonsmith@fourier.physics.purdue.edu 1396 Physics Building, West lafayette Purdue Univesity, Indiana 47906-1396 On Mon, 4 Jan 1999 npe@bfc.dk wrote: > Would a thing like a kernel configurator with a user interface be > appreciated ? > Personally I think that it would be a great plus for new users.. .(The > linux thing is really easy to use..) > > If I get enough positive respons then I'll start making a user interface > that works and is easy configureable for new options. > > > Regards, > Nicolai Petri > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 06:57:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23339 for freebsd-current-outgoing; Mon, 4 Jan 1999 06:57:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from maulwurf.franken.de (maulwurf.franken.de [193.141.110.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA23333 for ; Mon, 4 Jan 1999 06:57:41 -0800 (PST) (envelope-from gaspode.franken.de!tanis@maulwurf.franken.de) Received: by maulwurf.franken.de via rmail with stdio id for freebsd-current@FreeBSD.org; Mon, 4 Jan 1999 15:56:38 +0100 (MET) (Smail-3.2 1996-Jul-4 #1 built DST-May-30) Received: (from tanis@localhost) by gaspode.franken.de (8.9.1/8.8.8) id PAA14258; Mon, 4 Jan 1999 15:54:28 +0100 (CET) (envelope-from tanis) Message-ID: <19990104155427.A11667@gaspode.franken.de> Date: Mon, 4 Jan 1999 15:54:27 +0100 From: German Tischler To: osa@etrust.ru Cc: freebsd-current@FreeBSD.ORG Subject: Re: Can't compile ELF kernel... References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from majordom@FreeBSD.ORG on Mon, Jan 04, 1999 at 04:51:22PM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 04, 1999 at 04:51:22PM +0300, majordom@FreeBSD.ORG wrote: > > Hello! > Today, after cvsup source tree for my 3.0-CURRENT i try to compile > kernel in ELF > ..... > loading kernel > ad1848.o: In function `ad1816_attach': > ad1848.o(.text+0x1a3): undefined reference to `ad1816_write' > ad1848.o(.text+0x1b0): undefined reference to `ad1816_write' > ad1848.o(.text+0x1bd): undefined reference to `ad1816_write' > ad1848.o(.text+0x1cd): undefined reference to `ad1816_write' > ad1848.o(.text+0x1da): undefined reference to `ad1816_write' > ad1848.o(.text+0x1e7): more undefined references to `ad1816_write' follow > ad1848.o: In function `ad1816_attach': > ad1848.o(.text+0x1fd): undefined reference to `ad1816_reinit' > ad1848.o(.text+0x203): undefined reference to `ad1816_mixer_reset' > *** Error code 1 > > Stop. Just tried with a freshly checked out source tree and it worked. Try to clean up. -- German Tischler tanis@gaspode.franken.de Apple eaten (core dumped) tanis@cip.informatik.uni-wuerzburg.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 06:58:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23569 for freebsd-current-outgoing; Mon, 4 Jan 1999 06:58:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dns.webwizard.net.mx (webwizard.net.mx [148.245.50.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA23557 for ; Mon, 4 Jan 1999 06:58:12 -0800 (PST) (envelope-from eculp@webwizard.org.mx) Received: from webwizard.org.mx (webwizard.net.mx [148.245.50.27]) by dns.webwizard.net.mx (8.9.1/8.9.1) with ESMTP id IAA40557; Mon, 4 Jan 1999 08:57:07 -0600 (CST) (envelope-from eculp@webwizard.org.mx) Message-ID: <3690D6C3.21656968@webwizard.org.mx> Date: Mon, 04 Jan 1999 08:57:07 -0600 From: Edwin Culp X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Robert Nordier CC: freebsd-current@FreeBSD.ORG Subject: Re: Make world this morning. References: <199901041406.QAA02285@ceia.nordier.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert Nordier wrote: > Edwin Culp wrote: > > > Found a problem with this morning´s freshly cvsuped sources, just in > > case no one else has seen it. > > > > /usr/obj/elf/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr -o > > boot2.ld > > -P 1 boot2.bin > > kernel: ver=0.87 size=6d0 load=9000 entry=9010 map=16M pgctl=1:1 > > client: fmt=bin size=143c text=0 data=0 bss=0 entry=0 > > output: fmt=bin size=1d0c text=200 data=1b0c org=0 entry=0 > > 244 bytes available > > dd if=boot2.ld of=boot2 obs=7680 conv=osync 2>/dev/null > > ===> sys/boot/i386/libi386 > > make: don't know how to make machine/ansi.h. Stop > > *** Error code 2 > > > > Stop. > > *** Error code 1 > > Try changing to /sys/boot and doing a "make cleandepend". That > usually sorts this out. > > -- > Robert Nordier Probably so, I installed boot blocks, yesterday. Thanks. ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 07:25:22 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA25875 for freebsd-current-outgoing; Mon, 4 Jan 1999 07:25:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (nat0050.mpoweredpc.net [142.177.188.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA25691; Mon, 4 Jan 1999 07:25:17 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id LAA19685; Mon, 4 Jan 1999 11:24:50 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Mon, 4 Jan 1999 11:24:49 -0400 (AST) From: The Hermit Hacker To: "Jonathan M. Bresler" cc: jabley@clear.co.nz, jkh@zippy.cdrom.com, brian@hyperreal.org, freebsd-current@FreeBSD.ORG Subject: Re: sendmail throughput (was: HEADS UP: Postfix is coming. new uid, gid required.) In-Reply-To: <199901041358.FAA16846@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 4 Jan 1999, Jonathan M. Bresler wrote: > > Date: Mon, 4 Jan 1999 21:04:54 +1300 > > From: Joe Abley > > > > Just out of interest... What volume of messages typically flow through the > > freebsd-* lists? Out of all the subscribers of all the freebsd lists, how > > many unique subscriber addresses are there? > > over 22,000 unique email addresses. > > Volume: > > posfix (for all of yesterday, sunday jan 3rd) > sent: 329956 > deferred: 241607 > bounced: 2167 How many distinct email messages, or is that what htis number represents? Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 07:32:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA26428 for freebsd-current-outgoing; Mon, 4 Jan 1999 07:32:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ozz.etrust.ru ([195.2.84.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA26422 for ; Mon, 4 Jan 1999 07:32:15 -0800 (PST) (envelope-from osa@etrust.ru) Received: from localhost (localhost [127.0.0.1]) by ozz.etrust.ru (8.9.1/8.9.1) with ESMTP id SAA40000 for ; Mon, 4 Jan 1999 18:21:53 +0300 (MSK) (envelope-from osa@etrust.ru) Date: Mon, 4 Jan 1999 18:21:52 +0300 (MSK) From: oZZ!!! To: current@FreeBSD.ORG Subject: sendmail-8.9.2 released 31.12.1998 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=KOI8-R Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! Sendmail-8.9.2 released. When i can see it in -current source tree ? Rgdz, ïÓÏËÉÎ óÅÒÇÅÊ aka oZZ, osa@etrust.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 07:39:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA27288 for freebsd-current-outgoing; Mon, 4 Jan 1999 07:39:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from phoenix.welearn.com.au (welearn.com.au [139.130.44.81] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA27283 for ; Mon, 4 Jan 1999 07:39:29 -0800 (PST) (envelope-from sue@phoenix.welearn.com.au) Received: (from sue@localhost) by phoenix.welearn.com.au (8.9.1/8.9.0) id CAA19011; Tue, 5 Jan 1999 02:38:50 +1100 (EST) Message-ID: <19990105023845.24430@welearn.com.au> Date: Tue, 5 Jan 1999 02:38:45 +1100 From: Sue Blake To: npe@bfc.dk Cc: freebsd-current@FreeBSD.ORG Subject: Re: Kernel configurator References: <412566EF.004E9F27.00@bfc.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <412566EF.004E9F27.00@bfc.dk>; from npe@bfc.dk on Mon, Jan 04, 1999 at 03:37:30PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 04, 1999 at 03:37:30PM +0100, npe@bfc.dk wrote: > Would a thing like a kernel configurator with a user interface be > appreciated ? > Personally I think that it would be a great plus for new users.. . Well... why don't you ask them? The newbies who can read have a mailing list where they decide what would be best for -current users to try :-) -- Regards, -*Sue*- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 08:00:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA29710 for freebsd-current-outgoing; Mon, 4 Jan 1999 08:00:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA29703 for ; Mon, 4 Jan 1999 08:00:29 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac9.wam.umd.edu ((IDENT root)@rac9.wam.umd.edu [128.8.10.149]) by po4.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id LAA14904; Mon, 4 Jan 1999 11:00:40 -0500 (EST) Received: from rac9.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1]) by rac9.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id KAA12725; Mon, 4 Jan 1999 10:59:24 -0500 (EST) Received: from localhost by rac9.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id KAA12720; Mon, 4 Jan 1999 10:59:23 -0500 (EST) X-Authentication-Warning: rac9.wam.umd.edu: culverk owned process doing -bs Date: Mon, 4 Jan 1999 10:59:23 -0500 (EST) From: Kenneth Wayne Culver To: Sue Blake cc: npe@bfc.dk, freebsd-current@FreeBSD.ORG Subject: Re: Kernel configurator In-Reply-To: <19990105023845.24430@welearn.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, Jan 04, 1999 at 03:37:30PM +0100, npe@bfc.dk wrote: > > Would a thing like a kernel configurator with a user interface be > > appreciated ? > > Personally I think that it would be a great plus for new users.. . > > Well... why don't you ask them? The newbies who can read have a mailing > list where they decide what would be best for -current users to try :-) > Unless I'm mistaken, don't the options USERCONFIG, and its visual counterpart already implement a "Kernel Configurator??" It's my understanding that they do. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 08:12:02 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00750 for freebsd-current-outgoing; Mon, 4 Jan 1999 08:12:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chiark.greenend.org.uk (chiark.greenend.org.uk [195.224.76.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00716 for ; Mon, 4 Jan 1999 08:12:00 -0800 (PST) (envelope-from fanf@chiark.greenend.org.uk) Received: from fanf by chiark.greenend.org.uk with local (Exim 2.02 #1) id 0zxCbK-0001B8-00 (Debian); Mon, 4 Jan 1999 16:11:30 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <13968.59442.333361.736693@chiark.greenend.org.uk> Date: Mon, 4 Jan 1999 16:11:30 +0000 (GMT) In-Reply-To: <19990103181034.A5354@clear.co.nz> References: <002001be369c$239ad3e0$098a3fd1@ws1.gvn.net> From: Tony Finch To: current@FreeBSD.ORG Subject: Re: FrontPage Extensions Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joe Abley wrote: > >Check out Zeus Technology at http://www.zeus.co.uk/ - they have an >extremely fast and nice web server (with binaries available for FreeBSD >2.2.x) and incorporate their own FrontPage hosting without needing a lot >(all?) of the nasty Microsoft bloat. Not quite -- Zeus uses the nasty Microsoft Frontpage CGIs (which are distributed in binary form) but they have implemented a friendly installer and their own equivalent of the MSFP Apache module (which is distributed as source code). Tony. -- f.a.n.finch dot@dotat.at fanf@demon.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 4 08:12:57 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00820 for freebsd-current-outgoing; Mon, 4 Jan 1999 08:12:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00809; Mon, 4 Jan 1999 08:12:51 -0800 (PST) (envelope-from jmb) Date: Mon, 4 Jan 1999 08:12:51 -0800 (PST) Message-Id: <199901041612.IAA00809@hub.freebsd.org> From: "Jonathan M. Bresler" To: scrappy@hub.org CC: jabley@clear.co.nz, jkh@zippy.cdrom.com, brian@hyperreal.org, freebsd-current@FreeBSD.ORG In-reply-to: (message from The Hermit Hacker on Mon, 4 Jan 1999 11:24:49 -0400 (AST)) Subject: Re: sendmail throughput (was: HEADS UP: Postfix is coming. new uid, gid required.) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Date: Mon, 4 Jan 1999 11:24:49 -0400 (AST) > From: The Hermit Hacker > > > > Volume: > > > > posfix (for all of yesterday, sunday jan 3rd) > > sent: 329956 > > deferred: 241607 > > bounced: 2167 > > How many distinct email messages, or is that what htis number represents? all three are numbers of messsages sent, deferred or bounced. deferred means we were not able to deliver the message. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 08:33:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA03115 for freebsd-current-outgoing; Mon, 4 Jan 1999 08:33:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from maulwurf.franken.de (maulwurf.franken.de [193.141.110.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA03110 for ; Mon, 4 Jan 1999 08:33:45 -0800 (PST) (envelope-from gaspode.franken.de!tanis@maulwurf.franken.de) Received: by maulwurf.franken.de via rmail with stdio id for current@FreeBSD.ORG; Mon, 4 Jan 1999 17:33:01 +0100 (MET) (Smail-3.2 1996-Jul-4 #1 built DST-May-30) Received: (from tanis@localhost) by gaspode.franken.de (8.9.1/8.8.8) id RAA52891; Mon, 4 Jan 1999 17:30:41 +0100 (CET) (envelope-from tanis) Message-ID: <19990104173039.A16036@gaspode.franken.de> Date: Mon, 4 Jan 1999 17:30:39 +0100 From: German Tischler To: osa@etrust.ru Cc: current@FreeBSD.ORG, luigi@labinfo.iet.unipi.it Subject: Re: Can't compile ELF kernel... References: <19990104155427.A11667@gaspode.franken.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from osa@etrust.ru on Mon, Jan 04, 1999 at 06:33:55PM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 04, 1999 at 06:33:55PM +0300, osa@etrust.ru wrote: > > On Mon, 4 Jan 1999, German Tischler wrote: > > > On Mon, Jan 04, 1999 at 04:51:22PM +0300, majordom@FreeBSD.ORG wrote: > > > > > > Hello! > > > Today, after cvsup source tree for my 3.0-CURRENT i try to compile > > > kernel in ELF > > > ..... > > > loading kernel > > > ad1848.o: In function `ad1816_attach': > > > ad1848.o(.text+0x1a3): undefined reference to `ad1816_write' > > > ad1848.o(.text+0x1b0): undefined reference to `ad1816_write' > > > ad1848.o(.text+0x1bd): undefined reference to `ad1816_write' > > > ad1848.o(.text+0x1cd): undefined reference to `ad1816_write' > > > ad1848.o(.text+0x1da): undefined reference to `ad1816_write' > > > ad1848.o(.text+0x1e7): more undefined references to `ad1816_write' follow > > > ad1848.o: In function `ad1816_attach': > > > ad1848.o(.text+0x1fd): undefined reference to `ad1816_reinit' > > > ad1848.o(.text+0x203): undefined reference to `ad1816_mixer_reset' > > > *** Error code 1 > > > > > > Stop. > > > > Just tried with a freshly checked out source tree and it worked. > > Try to clean up. > > > what i must clean up? > > # cd /sys/i386/conf > # setenv KERNFORMAT elf > # config -r > # cd ../../compile/ > # make depend > # make > then i c that messages... I just found the bug. Please try the following diff for ad1848.c : (the ad1816 code is only compiles if you config pnp ). --- ad1848.c.orig Mon Jan 4 11:40:13 1999 +++ ad1848.c Mon Jan 4 17:23:15 1999 @@ -79,6 +79,7 @@ static void ad_write_cnt(snddev_info *d, int reg, u_short data); static int ad_read(snddev_info *d, int reg); +#if NPNP > 0 /* ad1816 prototypes */ /* IO primitives */ @@ -97,6 +98,7 @@ static void ad1816_mixer_reset(snddev_info * d); /* ad1816 prototypes end */ +#endif /* * device descriptors for the boards supported by this module. @@ -202,6 +204,8 @@ return mss_detect(dev) ? 8 : 0 ; /* mss uses 8 regs */ } +#if NPNP > 0 + static int ad1816_attach(struct isa_device *dev) { @@ -227,6 +231,8 @@ return 0 ; } +#endif + /* * the address passed as io_base for mss_attach is also the old * MSS base address (e.g. 0x530). The codec is four locations ahead. @@ -243,8 +249,10 @@ d->name, dev->id_unit, d->io_base, d->irq, d->dbuf_out.chan, d->dbuf_in.chan, dev->id_flags); +#if NPNP > 0 if (d->bd_id == MD_AD1816) return ad1816_attach(dev); +#endif dev->id_alive = 8 ; /* number of io ports */ /* should be already set but just in 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 4 08:45:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA04075 for freebsd-current-outgoing; Mon, 4 Jan 1999 08:45:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA04068 for ; Mon, 4 Jan 1999 08:45:34 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id LAA08520; Mon, 4 Jan 1999 11:44:52 -0500 (EST) (envelope-from wollman) Date: Mon, 4 Jan 1999 11:44:52 -0500 (EST) From: Garrett Wollman Message-Id: <199901041644.LAA08520@khavrinen.lcs.mit.edu> To: Robert Nordier Cc: bde@zeta.org.au (Bruce Evans), rvb@cs.cmu.edu, current@FreeBSD.ORG Subject: Re: New boot blocks for serial console ... In-Reply-To: <199901041034.MAA00391@ceia.nordier.com> References: <199901041009.VAA30233@godzilla.zeta.org.au> <199901041034.MAA00391@ceia.nordier.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Thanks, I wasn't aware that etc/make.conf settings affected the > old boot blocks. I'll bring the new stuff into line. While you're at it, please make it possible to build bootblocks which *don't* allow user interruption. As they stand now, the ability to let any old person walk up to a machine and tell it what to boot represents a serious weakness. -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 Mon Jan 4 08:50:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA04738 for freebsd-current-outgoing; Mon, 4 Jan 1999 08:50:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA04723 for ; Mon, 4 Jan 1999 08:50:17 -0800 (PST) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id IAA22147; Mon, 4 Jan 1999 08:49:26 -0800 (PST) Date: Mon, 4 Jan 1999 08:49:28 -0800 (PST) From: Tom Bartol To: Garrett Wollman cc: Robert Nordier , Bruce Evans , rvb@cs.cmu.edu, current@FreeBSD.ORG Subject: Re: New boot blocks for serial console ... In-Reply-To: <199901041644.LAA08520@khavrinen.lcs.mit.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, 4 Jan 1999, Garrett Wollman wrote: > < said: > > > Thanks, I wasn't aware that etc/make.conf settings affected the > > old boot blocks. I'll bring the new stuff into line. > > While you're at it, please make it possible to build bootblocks which > *don't* allow user interruption. As they stand now, the ability to > let any old person walk up to a machine and tell it what to boot > represents a serious weakness. > > -GAWollman > Actually, the weakness is "letting any old person walk up to a machine" in the first place --possibly with a floppy disk, floppy disk drive, assorted cables, and screwdriver in hand! Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 08:56:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA05679 for freebsd-current-outgoing; Mon, 4 Jan 1999 08:56:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA05673 for ; Mon, 4 Jan 1999 08:56:21 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id LAA08566; Mon, 4 Jan 1999 11:55:54 -0500 (EST) (envelope-from wollman) Date: Mon, 4 Jan 1999 11:55:54 -0500 (EST) From: Garrett Wollman Message-Id: <199901041655.LAA08566@khavrinen.lcs.mit.edu> To: Tom Bartol Cc: current@FreeBSD.ORG Subject: Re: New boot blocks for serial console ... In-Reply-To: References: <199901041644.LAA08520@khavrinen.lcs.mit.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Actually, the weakness is "letting any old person walk up to a machine" > in the first place --possibly with a floppy disk, floppy disk drive, > assorted cables, and screwdriver in hand! Not at all. Ever heard of a padlock? -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 Mon Jan 4 09:02:02 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06244 for freebsd-current-outgoing; Mon, 4 Jan 1999 09:02:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06198 for ; Mon, 4 Jan 1999 09:01:59 -0800 (PST) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id JAA22457; Mon, 4 Jan 1999 09:01:33 -0800 (PST) Date: Mon, 4 Jan 1999 09:01:34 -0800 (PST) From: Tom Bartol To: Garrett Wollman cc: current@FreeBSD.ORG Subject: Re: New boot blocks for serial console ... In-Reply-To: <199901041655.LAA08566@khavrinen.lcs.mit.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, 4 Jan 1999, Garrett Wollman wrote: > < said: > > > > Actually, the weakness is "letting any old person walk up to a machine" > > in the first place --possibly with a floppy disk, floppy disk drive, > > assorted cables, and screwdriver in hand! > > Not at all. Ever heard of a padlock? > Well, then, there's your solution! Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 09:03:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06573 for freebsd-current-outgoing; Mon, 4 Jan 1999 09:03:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06567 for ; Mon, 4 Jan 1999 09:03:34 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id MAA08597; Mon, 4 Jan 1999 12:03:07 -0500 (EST) (envelope-from wollman) Date: Mon, 4 Jan 1999 12:03:07 -0500 (EST) From: Garrett Wollman Message-Id: <199901041703.MAA08597@khavrinen.lcs.mit.edu> To: Tom Bartol Cc: Garrett Wollman , current@FreeBSD.ORG Subject: Re: New boot blocks for serial console ... In-Reply-To: References: <199901041655.LAA08566@khavrinen.lcs.mit.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: >> Not at all. Ever heard of a padlock? > Well, then, there's your solution! No, because it still doesn't prevent someone from walking up to the machine and telling it to boot something it shouldn't. What we're trying to achieve is an environment where the worst thing someone could do is cause the machine to reboot. -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 Mon Jan 4 09:13:02 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07336 for freebsd-current-outgoing; Mon, 4 Jan 1999 09:13:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp-gw.BayNetworks.COM (ns2.BayNetworks.COM [134.177.3.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07312 for ; Mon, 4 Jan 1999 09:12:48 -0800 (PST) (envelope-from thomma@BayNetworks.COM) Received: from mailhost.BayNetworks.COM (h016b.s86b1.BayNetworks.COM [134.177.1.107] (may be forged)) by smtp-gw.BayNetworks.COM (8.9.1/BNET-98/09/30-E) with ESMTP id IAA20227; Mon, 4 Jan 1999 08:04:52 -0800 (PST) Received: from fedex.engwest.baynetworks.com (fedex.engwest.baynetworks.com [134.177.110.46]) by mailhost.BayNetworks.COM (8.9.1/8.8.8) with SMTP id IAA11336; Mon, 4 Jan 1999 08:04:20 -0800 (PST) Received: from carrera.engwest (carrera.engwest.baynetworks.com) by fedex.engwest.baynetworks.com (4.1/SMI-4.1) Received: from localhost by carrera.engwest (SMI-8.6/SMI-SVR4) id HAA06449; Mon, 4 Jan 1999 07:59:27 -0800 To: mike@smith.net.au Cc: rjlynn@rjlynn.ddns.org, FreeBSD-current@FreeBSD.ORG Subject: Re: IDE Problem In-Reply-To: Your message of "Fri, 01 Jan 1999 18:49:09 -0800" <199901020249.SAA06391@dingo.cdrom.com> References: <199901020249.SAA06391@dingo.cdrom.com> X-Mailer: Mew version 1.92 on Emacs 19.28 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990104075927E.thomma@baynetworks.com> Date: Mon, 04 Jan 1999 07:59:27 -0800 From: Tamiji Homma X-Dispatcher: imput version 971024 Lines: 29 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I'm just starting out on -Current and heard theres been a problem with wd > > disks since Christmas, is that true? > > No. There's an outstanding problem with secondary IDE channels on some > motherboards, but the problem has been with us for quite some time. As just datapoint, two of my systems started having wd timeout problem sometime around Christmas. It has been working for about year or so with DMA on. The system are: FIC PA-2007 wd0: Quantum 6.4G Fireball (flags was 0xb0ff, yes LBA is on, now 0x90ff) wd1: none wd2: Maxtor 11G DiamondMax (flags was 0xa0ff, and it is 0xa0ff) wd3: Mitsumi IDE CDROM FIC PA-2007 wd0: IBM 6.4G Deskstar (flags 0xa0ff, it is 0x80ff) boot disk wd1: none wd2: none wd3: none ccd0: 2.1G x 2 on NCR 875 Sometime after Christmas, I had to turn off DMA on wd0 to bring up the system. The kernel before Christmas (mid December 1998) doesn't have this problem. Funny thing is that wd2 Maxtor doesn't show the problem even though it shares the bus with old IDE CDROM. Tammy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 09:14:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07549 for freebsd-current-outgoing; Mon, 4 Jan 1999 09:14:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07544 for ; Mon, 4 Jan 1999 09:14:05 -0800 (PST) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id JAA22814; Mon, 4 Jan 1999 09:13:39 -0800 (PST) Date: Mon, 4 Jan 1999 09:13:40 -0800 (PST) From: Tom Bartol To: Garrett Wollman cc: current@FreeBSD.ORG Subject: Re: New boot blocks for serial console ... In-Reply-To: <199901041703.MAA08597@khavrinen.lcs.mit.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, 4 Jan 1999, Garrett Wollman wrote: > < said: > > >> Not at all. Ever heard of a padlock? > > > Well, then, there's your solution! > > No, because it still doesn't prevent someone from walking up to the > machine and telling it to boot something it shouldn't. > > What we're trying to achieve is an environment where the worst thing > someone could do is cause the machine to reboot. > Then what you need is an untouchable machine in the hardware AND software sense. Padlock the room where the machine sits, get a UPS with plenty reserve power, and don't put it the machine on the net. Probably not a very useful machine when you're all done doing that :-) Sorry, I'm just jerking you around here, you're original idea about have a streamlined boot process is a good one, I'm just pointing out that this is really just a deterrent, like all other security measures as there really is no absolute solution to achieve absolute security. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 09:30:39 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08665 for freebsd-current-outgoing; Mon, 4 Jan 1999 09:30:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA08660 for ; Mon, 4 Jan 1999 09:30:38 -0800 (PST) (envelope-from ssiyer@cs.rice.edu) Received: (from ssiyer@localhost) by cs.rice.edu (8.9.0/8.9.0) id LAA06566; Mon, 4 Jan 1999 11:29:35 -0600 (CST) Message-ID: <19990104112935.A6256@cs.rice.edu> Date: Mon, 4 Jan 1999 11:29:35 -0600 From: Sitaram Iyer To: Bruce Evans , luigi@labinfo.iet.unipi.it, mike@smith.net.au Cc: current@FreeBSD.ORG Subject: Re: -DKERNEL option when compiling kernels ? Reply-To: Sitaram Iyer References: <199901011115.WAA22595@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199901011115.WAA22595@godzilla.zeta.org.au>; from Bruce Evans on Fri, Jan 01, 1999 at 10:15:09PM +1100 X-url: http://www.cs.rice.edu/~ssiyer/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus, Bruce Evans wrote... > >well it is just a very minor thing, anyways. Now if there was a > >way to put all compile options somewhere so that the make output > >does not show three lines for each file... > >cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs > >-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline > >-Wuninitialized -Wformat -Wunused -fformat-extensions -ansi -nostdinc -I- > >-I. -I../.. -I../../../include -DKERNEL -include opt_global.h -aout vers.c > If you can solve that, then -DKERNEL is worth hiding too. how about something trivial like cc -c -O `cat .CFLAGS` ... -- Sitaram Iyer http://www.cs.rice.edu/~ssiyer/ Phone: Office: (713) 527-8750 x3291 (direct dial), Res: (713) 630-9260 Fresh graduate student in the Computer Science dept at Rice University To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 09:33:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09166 for freebsd-current-outgoing; Mon, 4 Jan 1999 09:33:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA09160 for ; Mon, 4 Jan 1999 09:33:52 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id MAA02254; Mon, 4 Jan 1999 12:33:27 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.1/8.9.1) id MAA27505; Mon, 4 Jan 1999 12:32:32 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 4 Jan 1999 12:32:32 -0500 (EST) To: sthaug@nethelp.no Cc: freebsd-current@FreeBSD.ORG Subject: Re: NOW/MOSIX/Beowulf In-Reply-To: <10550.915066584@verdi.nethelp.no> References: <13962.46346.872709.715074@grasshopper.cs.duke.edu> <10550.915066584@verdi.nethelp.no> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13968.64130.379928.608792@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sthaug@nethelp.no writes: > > This is rather off topic, but does anybody know what the cheapest > > route to a 64-bit PCI slot on an Intel platform is? I know the 450NX > > chipset supports 64-bit PCI, but the last time I checked, machines > > using the 450NX chipset were only available in high-margin servers > > from Dell. Does anybody know of any 3rd-party x86 motherboard that > > has a 64-bit slot? > > Micron Powerdigm XSU has a 64 bit PCI slot, see > > http://www.zdnet.com/products/content/pcmg/1704/269178.html > > for some info. (No recommendation - I have no experience with this > system.) As far as I know, you can't buy the motherboard only. Thanks, but I think they're long gone. I cannot find any mention of them on the Micron web site (except in their service section). Altavista turned up those pages, plus a few (stale) hits at Micron resellers. Thanks anyway, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 09:44:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10311 for freebsd-current-outgoing; Mon, 4 Jan 1999 09:44:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA10302 for ; Mon, 4 Jan 1999 09:44:53 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id MAA20640; Mon, 4 Jan 1999 12:40:58 -0500 (EST) Date: Mon, 4 Jan 1999 12:40:58 -0500 (EST) From: Chuck Robey To: "David W. Chapman Jr." cc: freebsd-current Subject: Re: sendmail throughput (was: HEADS UP: Postfix is coming. new uid,gid required.) In-Reply-To: <369077A1.3E637E35@houabg.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, 4 Jan 1999, David W. Chapman Jr. wrote: > I see where your comming from, but as I believe Mr Tubutis put it, the ideal > setup would to have the mail list "link" the the news server. Therefore those > who still would like the email, can keep it, those who like the news group > could also use that. I guess filtering spam or junk mail isn't my primary > reason for wanting to switch, I think I can keep my mouth shut when another one > comes along. I like the newsgroup because when I go to check my email, I don't > have to wait a couple of minutes for them all to download. Yeah, it'd be nice to find a middle ground, but the mailing lists have to find *some* way of accomplishing the filtering action without requiring a moderator. Now it's because most "jerks" (if you understand the category I'm only roughly defining) haven't got enough long-term interest to subscribe to a mailing list, although they will drop in and cause all sorts of problems with a newsgroup. The sheer volume of plain profanity on usenet is appalling. Anyone who can come up with a method like that, well, they'd have a *much* firmer case to make for newsgroups, then. Just establishing a newsgroup, that's going to go over like a lead balloon. I really hate watching a thread descend to namecalling. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 09:44:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10325 for freebsd-current-outgoing; Mon, 4 Jan 1999 09:44:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mortar.carlson.com (mortar.carlson.com [208.240.12.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA10306 for ; Mon, 4 Jan 1999 09:44:55 -0800 (PST) (envelope-from veldy@visi.com) Received: from mortar.carlson.com (root@localhost) by mortar.carlson.com with ESMTP id LAA02706 for ; Mon, 4 Jan 1999 11:43:46 -0600 (CST) Received: from w142844 ([172.25.99.35]) by mortar.carlson.com with SMTP id LAA02702 for ; Mon, 4 Jan 1999 11:43:45 -0600 (CST) Message-ID: <01de01be380a$01064890$236319ac@w142844.carlson.com> From: "Thomas T. Veldhouse" To: "FreeBSD-Current" Subject: New BOOT Blocks - installation docs? Date: Mon, 4 Jan 1999 11:45:22 -0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_01DB_01BE37D7.B62113F0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_01DB_01BE37D7.B62113F0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Does anybody know if there is any documentation (or a step-by-step = procedure) for installing the new boot blocks and then an elf kernel. I = have not had any luck in the past (perhaps because I am booting off of = the secondary master IDE drive). It seems to me that it shouldn't be = very hard to do, but without documentation I am just going to mess up my = system. I am a bit worried since the system is supposed to go all ELF = in two days. I have been trying to track current for various reasons, = so I really need this one. Thanks in advance, Tom Veldhouse veldy@visi.com ------=_NextPart_000_01DB_01BE37D7.B62113F0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Does anybody know if there is any documentation (or = a=20 step-by-step procedure) for installing the new boot blocks and then an = elf=20 kernel.  I have not had any luck in the past (perhaps because I am = booting=20 off of the secondary master IDE drive).  It seems to me that it = shouldn't=20 be very hard to do, but without documentation I am just going to mess up = my=20 system.  I am a bit worried since the system is supposed to go all = ELF in=20 two days.  I have been trying to track current for various reasons, = so I=20 really need this one.
 
Thanks in advance,
 
Tom Veldhouse
veldy@visi.com
 
------=_NextPart_000_01DB_01BE37D7.B62113F0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 10:04:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13283 for freebsd-current-outgoing; Mon, 4 Jan 1999 10:04:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA13278 for ; Mon, 4 Jan 1999 10:04:16 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id KAA38336; Mon, 4 Jan 1999 10:03:44 -0800 (PST) To: "Daniel C. Sobral" cc: freebsd-current@FreeBSD.ORG Subject: Re: 3.0-19981226-SNAP/src/ssys.ac is corrupt In-reply-to: Your message of "Mon, 04 Jan 1999 16:32:17 +0900." <36906E81.D5AB960A@newsguy.com> Date: Mon, 04 Jan 1999 10:03:44 -0800 Message-ID: <38332.915473024@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Err... I happen to have seen the exact same problem. I tried four > times to install the sys sources, and each time the connection would > stop at the precise same point. Perhaps there's a data-sensitive router somewhere in the path, e.g. one which flakes when certain bit patterns fly by. I've seen it happen with terminal servers of various types but rarely a full-blown cisco router. All I know is that when I verified the files on this end, they were fine. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 10:04:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13311 for freebsd-current-outgoing; Mon, 4 Jan 1999 10:04:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA13304 for ; Mon, 4 Jan 1999 10:04:31 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id NAA48108; Mon, 4 Jan 1999 13:08:16 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Mon, 4 Jan 1999 13:08:16 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: "Thomas T. Veldhouse" cc: FreeBSD-Current Subject: Re: New BOOT Blocks - installation docs? In-Reply-To: <01de01be380a$01064890$236319ac@w142844.carlson.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, 4 Jan 1999, Thomas T. Veldhouse wrote: > Does anybody know if there is any documentation (or a step-by-step > procedure) for installing the new boot blocks and then an elf kernel. > I have not had any luck in the past (perhaps because I am booting off > of the secondary master IDE drive). It seems to me that it shouldn't > be very hard to do, but without documentation I am just going to mess > up my system. I am a bit worried since the system is supposed to go > all ELF in two days. I have been trying to track current for various > reasons, so I really need this one. > > Thanks in advance, > > Tom Veldhouse > veldy@visi.com check the date on the files in /boot to make sure they have been installed properly, then: disklabel -B -b /boot/boot1 -s /boot/boot2 (i assume you know how to compile a kernel) to compile an ELF kernel you need to set the enviorment variable KERNFORMAT to 'elf' setenv KERNFORMAT elf -or- export KERNFORMAT=elf then in the compile/kernelname dir: make clean make depend make all make install reboot. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 10:07:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13604 for freebsd-current-outgoing; Mon, 4 Jan 1999 10:07:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA13576 for ; Mon, 4 Jan 1999 10:07:02 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.205]) by smtp05.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA371 for ; Mon, 4 Jan 1999 19:06:30 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 04 Jan 1999 19:13:35 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: FreeBSD Current Subject: READ if ye want the new bootblocks / ELF kernel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just to make sure I got the attention. Robert was kind enough to make this page to enable people to install the new bootblocks: http://www.freebsd.org/~rnordier/boot.txt Also, just edit the Makefile.i386 and set OBJFORMAT to elf instead of a.out to compile an ELF kernel. Thanks to Robert and Mike for the pointers... It all runs smoothly here... --- Jeroen Ruigrok van der Werven A veil of smoke is what I am, asmodai(at)wxs.nl I wait and I wait... Network/Security Specialist BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 10:07:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13623 for freebsd-current-outgoing; Mon, 4 Jan 1999 10:07:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA13606 for ; Mon, 4 Jan 1999 10:07:06 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id KAA38364; Mon, 4 Jan 1999 10:05:19 -0800 (PST) To: "David W. Chapman Jr." cc: freebsd-current Subject: Re: News Server In-reply-to: Your message of "Mon, 04 Jan 1999 02:35:05 CST." <36907D39.A49114FE@houabg.com> Date: Mon, 04 Jan 1999 10:05:19 -0800 Message-ID: <38361.915473119@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > freebsd-current@freebsd.org. But it would better suit me to read from > the news server. With news server it I can read messages in retrospect I don't think anyone has any objections, just so long as postings don't make it back to the mailing list. E.g. if it's strictly one-way, nobody on the lists will have any objections. Things posted to the news server should probably just stay there for other news readers to read. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 10:09:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13809 for freebsd-current-outgoing; Mon, 4 Jan 1999 10:09:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA13804 for ; Mon, 4 Jan 1999 10:09:43 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id KAA38401; Mon, 4 Jan 1999 10:09:05 -0800 (PST) To: Garrett Wollman cc: Tom Bartol , current@FreeBSD.ORG Subject: Re: New boot blocks for serial console ... In-reply-to: Your message of "Mon, 04 Jan 1999 11:55:54 EST." <199901041655.LAA08566@khavrinen.lcs.mit.edu> Date: Mon, 04 Jan 1999 10:09:05 -0800 Message-ID: <38397.915473345@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Not at all. Ever heard of a padlock? Give me physical access to your machine, with or without a padlock, and I'll have root on that baby before you have a chance to come back from lunch. I think the original comment that there's no security without physical security has definite merit. The NSA learned this decades ago! :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 10:10:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13928 for freebsd-current-outgoing; Mon, 4 Jan 1999 10:10:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA13923 for ; Mon, 4 Jan 1999 10:10:32 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id KAA38419; Mon, 4 Jan 1999 10:09:56 -0800 (PST) To: Garrett Wollman cc: Tom Bartol , current@FreeBSD.ORG Subject: Re: New boot blocks for serial console ... In-reply-to: Your message of "Mon, 04 Jan 1999 12:03:07 EST." <199901041703.MAA08597@khavrinen.lcs.mit.edu> Date: Mon, 04 Jan 1999 10:09:56 -0800 Message-ID: <38416.915473396@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What we're trying to achieve is an environment where the worst thing > someone could do is cause the machine to reboot. Then lock the machine in a room. You're not going to get anywhere close to that by changing the boot blocks and flagging it as an issue in this case is simply waving a red herring. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 10:15:01 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14240 for freebsd-current-outgoing; Mon, 4 Jan 1999 10:15:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dinah.coastalnet.com (dinah.coastalnet.com [204.183.40.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14206 for ; Mon, 4 Jan 1999 10:14:59 -0800 (PST) (envelope-from ryany@dinah.coastalnet.com) Received: (from ryany@localhost) by dinah.coastalnet.com (8.8.8/8.8.8) id NAA02303; Mon, 4 Jan 1999 13:13:58 -0500 (EST) (envelope-from ryany) Message-Id: <199901041813.NAA02303@dinah.coastalnet.com> Subject: Re: Kernel configurator In-Reply-To: from Kenneth Wayne Culver at "Jan 4, 1999 10:59:23 am" To: culverk@wam.umd.edu (Kenneth Wayne Culver) Date: Mon, 4 Jan 1999 13:13:58 -0500 (EST) Cc: sue@welearn.com.au, npe@bfc.dk, freebsd-current@FreeBSD.ORG From: Ryan Younce 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 > > On Mon, Jan 04, 1999 at 03:37:30PM +0100, npe@bfc.dk wrote: > > > Would a thing like a kernel configurator with a user interface be > > > appreciated ? > > > Personally I think that it would be a great plus for new users.. . > > > > Well... why don't you ask them? The newbies who can read have a mailing > > list where they decide what would be best for -current users to try :-) > > > Unless I'm mistaken, don't the options USERCONFIG, and its visual > counterpart already implement a "Kernel Configurator??" It's my > understanding that they do. That was my understanding also. I think the original author might have meant a pre-compilation utility which spawns a TCL or Curses based configuration tool that gives a runthrough of all the options, similar to Linux's 'make xconfig' or 'make menuconfig' (assuming, of course, that they haven't changed it in the two-plus years since I quit using Linux). Ryan Younce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 10:16:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14450 for freebsd-current-outgoing; Mon, 4 Jan 1999 10:16:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mortar.carlson.com (mortar.carlson.com [208.240.12.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14438 for ; Mon, 4 Jan 1999 10:16:11 -0800 (PST) (envelope-from veldy@visi.com) Received: from mortar.carlson.com (root@localhost) by mortar.carlson.com with ESMTP id MAA02934; Mon, 4 Jan 1999 12:15:03 -0600 (CST) Received: from w142844 ([172.25.99.35]) by mortar.carlson.com with SMTP id MAA02930; Mon, 4 Jan 1999 12:15:03 -0600 (CST) Message-ID: <023101be380e$6030efb0$236319ac@w142844.carlson.com> From: "Thomas T. Veldhouse" To: "Alfred Perlstein" Cc: "FreeBSD-Current" Subject: Re: New BOOT Blocks - installation docs? Date: Mon, 4 Jan 1999 12:16:40 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks. The disklabel part is what I was missing. Has anybody created an online document for Jan 6? >check the date on the files in /boot to make sure they have been installed >properly, then: > >disklabel -B -b /boot/boot1 -s /boot/boot2 > > > >(i assume you know how to compile a kernel) > >to compile an ELF kernel you need to set the enviorment variable >KERNFORMAT to 'elf' > >setenv KERNFORMAT elf >-or- >export KERNFORMAT=elf > >then in the compile/kernelname dir: >make clean >make depend >make all >make install > >reboot. > >-Alfred > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 10:20:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14765 for freebsd-current-outgoing; Mon, 4 Jan 1999 10:20:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14760 for ; Mon, 4 Jan 1999 10:20:08 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id NAA48135; Mon, 4 Jan 1999 13:23:39 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Mon, 4 Jan 1999 13:23:39 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: "Jordan K. Hubbard" cc: Garrett Wollman , Tom Bartol , current@FreeBSD.ORG Subject: Re: New boot blocks for serial console ... In-Reply-To: <38416.915473396@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 Mon, 4 Jan 1999, Jordan K. Hubbard wrote: > > What we're trying to achieve is an environment where the worst thing > > someone could do is cause the machine to reboot. > > Then lock the machine in a room. You're not going to get anywhere > close to that by changing the boot blocks and flagging it as an issue > in this case is simply waving a red herring. the bootblocks aren't all that complicated, i'm sure you can mostly just comment out the code that prompts for a kernel and hardcode it in. perhaps a feature of the bootblocks may be something in boot.conf(?) that restrics the boot device sorta like ipfw, "allow boot wd0"... has anyone thought of the implications of sticking a faux kernel in /tmp and well... nevermind :) you can also play with the /etc/rc script to disallow annoying lab students the priviledge of ^C'ing your starup scripts. look at the 'sh' manpage and search for syntax on 'trap' i think the point is so that some wiseass doesn't stick a floppy in the machine and boot a rouge userland, most bios's come with an option to disable the boot floppy for convience and a false sense of security -Alfred > > - Jordan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 10:20:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14992 for freebsd-current-outgoing; Mon, 4 Jan 1999 10:20:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14987 for ; Mon, 4 Jan 1999 10:20:41 -0800 (PST) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id KAA24913; Mon, 4 Jan 1999 10:20:06 -0800 (PST) Date: Mon, 4 Jan 1999 10:20:09 -0800 (PST) From: Tom Bartol To: "Jordan K. Hubbard" cc: Garrett Wollman , current@FreeBSD.ORG Subject: Re: New boot blocks for serial console ... In-Reply-To: <38397.915473345@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 Mon, 4 Jan 1999, Jordan K. Hubbard wrote: > > Not at all. Ever heard of a padlock? > > Give me physical access to your machine, with or without a padlock, > and I'll have root on that baby before you have a chance to come back > from lunch. > > I think the original comment that there's no security without physical > security has definite merit. Thanks! >The NSA learned this decades ago! :) > Indeed, they have learned the hard way that the Laws of Physics (and the shortsightedness of human beings) put precious little restriction on what the imagination can dream up and actually implement to gain "physical access" to a given machine. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 10:31:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15654 for freebsd-current-outgoing; Mon, 4 Jan 1999 10:31:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA15579; Mon, 4 Jan 1999 10:30:27 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id UAA04689; Mon, 4 Jan 1999 20:07:21 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id UAA20683; Mon, 4 Jan 1999 20:07:16 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199901041807.UAA20683@greenpeace.grondar.za> To: Mike Smith cc: "Daniel C. Sobral" , "Jordan K. Hubbard" , freebsd-current@FreeBSD.ORG, freebsd-admin@FreeBSD.ORG Subject: Re: 3.0-19981226-SNAP/src/ssys.ac is corrupt In-Reply-To: Your message of " Mon, 04 Jan 1999 00:32:06 PST." <199901040832.AAA11061@dingo.cdrom.com> References: <199901040832.AAA11061@dingo.cdrom.com> Date: Mon, 04 Jan 1999 20:07:15 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > Maybe my provider uses a Cisco, as you suggest on another message, > > who knows... But having the connection stop at the precise point > > four times with me, and at least one more time with the person above > > (I can't be sure it was the same point with him, but it looks like > > the same file, at least), while every thing else on a developer > > install with full sources came correctly... how could that be? > > This is usually a "magic byte sequence" which blows the brains out of > something in the transit path. We've seen a few of these. This could explain a similar proble I am having. I do a "cd /usr/ports; make fetch" for the benefit of .za, and certain ports "just hang". They'll get to n% of the download, and buggerall retries will help. At the same "n" - stop. It usually takes manual intervention and a different route to obtain the tarball. Big tarballs like mysql and netscape are more susceptible. (Statistics, I suppose). 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 Mon Jan 4 10:31:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15705 for freebsd-current-outgoing; Mon, 4 Jan 1999 10:31:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from silver.gn.iaf.nl (silver.gn.iaf.nl [193.67.144.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA15686 for ; Mon, 4 Jan 1999 10:31:32 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by silver.gn.iaf.nl (8.8.8/8.8.8) with SMTP id TAA23982; Mon, 4 Jan 1999 19:30:37 +0100 Received: by uni4nn.gn.iaf.nl with UUCP id AA07811 (5.67b/IDA-1.5); Mon, 4 Jan 1999 19:08:30 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id AAA04420; Mon, 4 Jan 1999 00:02:06 +0100 (CET) From: Wilko Bulte Message-Id: <199901032302.AAA04420@yedi.iaf.nl> Subject: Re: aha fix-thank you! In-Reply-To: <199901032156.OAA57593@harmony.village.org> from Warner Losh at "Jan 3, 99 02:56:31 pm" To: imp@village.org (Warner Losh) Date: Mon, 4 Jan 1999 00:02:05 +0100 (CET) Cc: gaylord@gaylord.async.vt.edu, freebsd-current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Warner Losh wrote... > In message <199901012025.PAA00554@gaylord.async.vt.edu> Clark Gaylord writes: > : BTW, I have a 1542B, unknown firmware ... is there a FreeBSD util > : for reading/loading firmware on these puppies? I recall there > : being a DOS util, but I can't find that (though I suppose I can > : probably get it from Adaptec's web site). Right now my drives are > : <=1GB, but I will probably buy a 4GB soon and I'm not sure I have > : the right firmware. > > I don't think so. Looking at the chips on my AHA-1542B leads me to > believe that they are EPROMS that need UV light to erase and then a > EPROM burner to reprogram. Right. All the 1542B I've seen use EPROMS, so you need an UV eraser and an EPROM programmer yo upgrade them Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 10:42:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA16873 for freebsd-current-outgoing; Mon, 4 Jan 1999 10:42:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA16859 for ; Mon, 4 Jan 1999 10:42:26 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id TAA14876; Mon, 4 Jan 1999 19:38:47 +0100 (CET) To: "Jordan K. Hubbard" cc: Garrett Wollman , Tom Bartol , current@FreeBSD.ORG Subject: Re: New boot blocks for serial console ... In-reply-to: Your message of "Mon, 04 Jan 1999 10:09:05 PST." <38397.915473345@zippy.cdrom.com> Date: Mon, 04 Jan 1999 19:38:46 +0100 Message-ID: <14874.915475126@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <38397.915473345@zippy.cdrom.com>, "Jordan K. Hubbard" writes: >> Not at all. Ever heard of a padlock? > >Give me physical access to your machine, with or without a padlock, >and I'll have root on that baby before you have a chance to come back >from lunch. > >I think the original comment that there's no security without physical >security has definite merit. The NSA learned this decades ago! :) Uhm, well there is, but it is called "tamper-proof hardware" and costs a fortune. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 10:57:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17846 for freebsd-current-outgoing; Mon, 4 Jan 1999 10:57:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17840 for ; Mon, 4 Jan 1999 10:57:25 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id KAA07919; Mon, 4 Jan 1999 10:56:58 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id KAA24163; Mon, 4 Jan 1999 10:56:57 -0800 (PST) (envelope-from jdp@polstra.com) Date: Mon, 4 Jan 1999 10:56:57 -0800 (PST) Message-Id: <199901041856.KAA24163@vashon.polstra.com> To: zach@gaffaneys.com Subject: Re: 3.0 release tag for cvsup ??? Newsgroups: polstra.freebsd.current In-Reply-To: <19990103023411.A37772@znh.org> References: <004b01be36b0$cc319ca0$f301040a@c063.beaverton.stream.com> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You can find a list of all [important] tags by looking at: > > ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-CVS/src/COPYRIGHT,v They are also listed in the CVSup section of the FreeBSD Handbook. Currently, that's section 18.3.3. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 11:05:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19603 for freebsd-current-outgoing; Mon, 4 Jan 1999 11:05:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles165.castles.com [208.214.165.165]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19596 for ; Mon, 4 Jan 1999 11:05:49 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id KAA14013; Mon, 4 Jan 1999 10:58:56 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901041858.KAA14013@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Poul-Henning Kamp cc: "Jordan K. Hubbard" , Garrett Wollman , Tom Bartol , current@FreeBSD.ORG Subject: Re: New boot blocks for serial console ... In-reply-to: Your message of "Mon, 04 Jan 1999 19:38:46 +0100." <14874.915475126@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 04 Jan 1999 10:58:55 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <38397.915473345@zippy.cdrom.com>, "Jordan K. Hubbard" writes: > >> Not at all. Ever heard of a padlock? > > > >Give me physical access to your machine, with or without a padlock, > >and I'll have root on that baby before you have a chance to come back > >from lunch. > > > >I think the original comment that there's no security without physical > >security has definite merit. The NSA learned this decades ago! :) > > Uhm, well there is, but it is called "tamper-proof hardware" and costs > a fortune. It's not "tamper-proof", it's "tamper-resistant", and I can suggest a wide range of "tampering" hardware that it won't stand up to for long. But Garrett's point is actually quite valid; there's a fairly wide gap between "I will just fiddle with the console" and "I will walk into the server room with a pair of bolt cutters", and all that's required to close that gap is changing boot2 to not wait that couple of seconds before launching the loader, or to ignore the keyboard while it is. The latter would actually be easier, given its current design; add a '-X' option to /boot.config to disable the keyboard. Diffs happily accepted. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 11:06:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19708 for freebsd-current-outgoing; Mon, 4 Jan 1999 11:06:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from distance.net (distance.net [209.142.224.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19641 for ; Mon, 4 Jan 1999 11:06:01 -0800 (PST) (envelope-from spam@distance.net) Received: from distance.net (zula@fl-mi-pm-port-124.lsl.com [209.69.166.124]) by distance.net (8.8.8/8.8.8) with ESMTP id OAA06397; Mon, 4 Jan 1999 14:05:34 -0500 (EST) (envelope-from spam@distance.net) Message-ID: <36911151.DC9FD1DE@distance.net> Date: Mon, 04 Jan 1999 14:06:57 -0500 From: Ryan Duda X-Mailer: Mozilla 4.08 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG CC: spam@distance.net Subject: (pw) command hanging in -C. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG - Is there a reason why "pw usermod username -h 0" would be hanging? This seems to work fine in 2_2-STABLE. Thanks, -RPD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 11:15:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20887 for freebsd-current-outgoing; Mon, 4 Jan 1999 11:15:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pinhead.parag.codegen.com (ppp-sfx201--019.sirius.net [205.134.235.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20880 for ; Mon, 4 Jan 1999 11:15:08 -0800 (PST) (envelope-from parag@cgt.com) Received: from pinhead.parag.codegen.com (localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.9.1/8.8.8) with ESMTP id LAA41108 for ; Mon, 4 Jan 1999 11:14:48 -0800 (PST) (envelope-from parag@pinhead.parag.codegen.com) Message-Id: <199901041914.LAA41108@pinhead.parag.codegen.com> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG Subject: Re: 3.0-CURRENT CAM vs scanner problems In-Reply-To: Message from "Daniel O'Connor" of "Mon, 04 Jan 1999 11:49:36 +1030." X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm X-URL: http://www.codegen.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 04 Jan 1999 11:14:48 -0800 From: Parag Patel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks to Daniel O'Conner and Cory Kempf. I have sent the patch to the SANE folks and hope it will be incorporated soon. For anyone else having scanning problems with 3.0-CURRENT and SANE, add this simple patch to the sane port and rebuild it. -- Parag Patel *** sanei/sanei_scsi.c-org Sun Jan 3 16:37:08 1999 --- sanei/sanei_scsi.c Sun Jan 3 16:37:11 1999 *************** *** 186,192 **** #endif #if USE == FREEBSD_CAM_INTERFACE ! # define MAX_DATA MAXPHYS #endif #ifndef MAX_DATA --- 186,192 ---- #endif #if USE == FREEBSD_CAM_INTERFACE ! # define MAX_DATA DFLTPHYS #endif #ifndef MAX_DATA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 11:17:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA21183 for freebsd-current-outgoing; Mon, 4 Jan 1999 11:17:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA21176 for ; Mon, 4 Jan 1999 11:17:09 -0800 (PST) (envelope-from randy@psg.com) Received: from localhost (1204 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Mon, 4 Jan 1999 11:16:44 -0800 (PST) (Smail-3.2.0.101 1997-Dec-17 #1 built 1998-Oct-13) Message-Id: Date: Mon, 4 Jan 1999 11:16:44 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Randy Bush To: freebsd-current@FreeBSD.ORG Subject: read DMA channel unavailable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jan 2 10:57:34 rip /kernel: sorry, read DMA channel unavailable Jan 2 11:04:05 rip /kernel: sorry, read DMA channel unavailable Jan 2 12:48:33 rip /kernel: sorry, read DMA channel unavailable Jan 2 12:53:56 rip /kernel: sorry, read DMA channel unavailable Jan 2 12:55:37 rip /kernel: sorry, read DMA channel unavailable Jan 2 16:15:30 rip /kernel: sorry, read DMA channel unavailable Jan 2 16:20:06 rip /kernel: sorry, read DMA channel unavailable Jan 2 16:23:52 rip /kernel: sorry, read DMA channel unavailable Jan 2 16:57:32 rip /kernel: sorry, read DMA channel unavailable Jan 2 17:26:42 rip /kernel: sorry, read DMA channel unavailable Jan 2 17:35:33 rip /kernel: sorry, read DMA channel unavailable Jan 2 17:39:19 rip /kernel: sorry, read DMA channel unavailable Jan 2 17:48:41 rip /kernel: sorry, read DMA channel unavailable Jan 2 18:07:12 rip /kernel: sorry, read DMA channel unavailable should i be concerned? randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 11:19:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA21401 for freebsd-current-outgoing; Mon, 4 Jan 1999 11:19:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA21387 for ; Mon, 4 Jan 1999 11:19:08 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id UAA15159; Mon, 4 Jan 1999 20:14:25 +0100 (CET) To: Mike Smith cc: "Jordan K. Hubbard" , Garrett Wollman , Tom Bartol , current@FreeBSD.ORG Subject: Re: New boot blocks for serial console ... In-reply-to: Your message of "Mon, 04 Jan 1999 10:58:55 PST." <199901041858.KAA14013@dingo.cdrom.com> Date: Mon, 04 Jan 1999 20:14:25 +0100 Message-ID: <15157.915477265@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199901041858.KAA14013@dingo.cdrom.com>, Mike Smith writes: >> In message <38397.915473345@zippy.cdrom.com>, "Jordan K. Hubbard" writes: >> >> Not at all. Ever heard of a padlock? >> > >> >Give me physical access to your machine, with or without a padlock, >> >and I'll have root on that baby before you have a chance to come back >> >from lunch. >> > >> >I think the original comment that there's no security without physical >> >security has definite merit. The NSA learned this decades ago! :) >> >> Uhm, well there is, but it is called "tamper-proof hardware" and costs >> a fortune. > >It's not "tamper-proof", it's "tamper-resistant", and I can suggest a >wide range of "tampering" hardware that it won't stand up to for long. No, you bet it is tamper-PROOF. They will guarantee that you will not get access to anything in the computer. Last perimeter will inject 220V (mains) through vital bits of the computer (including your flash disk) if broken. By the time you have gotten through the 10mm steel plate, the computer is dead. And quite likely you as well, they have versions with poison-gas release and all sorts of nasties. Primary market: ATM & Banking terminals. Smallest model and the closest they have to a portable in the catalog I have here weighs 450 kg (thats 900 pounds), sports 10mm steel casing (both the outher case and the CPU module case inside it) it comes with optional holes in the bottom so you can bolt it to a foundation. It is also IP67 watertight and they will paint it in any color you like. Price: $CALL. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 11:23:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA21847 for freebsd-current-outgoing; Mon, 4 Jan 1999 11:23:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA21839 for ; Mon, 4 Jan 1999 11:23:31 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.44]) by smtp03.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA139B for ; Mon, 4 Jan 1999 20:21:43 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 04 Jan 1999 20:29:00 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: FreeBSD Current Subject: RE: READ if ye want the new bootblocks / ELF kernel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 04-Jan-99 Jeroen Ruigrok/Asmodai wrote: > Also, just edit the Makefile.i386 and set OBJFORMAT to elf instead of a.out > to compile an ELF kernel. I meant KERNFORMAT offcourse... But as Alfred suggested, an environment variable might work as well... --- Jeroen Ruigrok van der Werven A veil of smoke is what I am, asmodai(at)wxs.nl I wait and I wait... Network/Security Specialist BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 11:28:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA22233 for freebsd-current-outgoing; Mon, 4 Jan 1999 11:28:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA22226 for ; Mon, 4 Jan 1999 11:28:12 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (peter@localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Netplex) with ESMTP id DAA16810 for ; Tue, 5 Jan 1999 03:27:44 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199901041927.DAA16810@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: Re: UPCOMING FLAG DAY (Jan 6) Date: Tue, 05 Jan 1999 03:27:43 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've updated the notes I originally used in the mail about the upcoming next stage of the ELF transition. In case you missed it or skipped too many articles in catchup after the break, the nutshell version is that we are planning on forcing the rest of the ELF changeover - a.out 'make world's are going to be disabled and we're going to switch the default kernel format to elf. Anyway, there is a (hopefully) better copy now at: http://www.freebsd.org/~peter/elfday.html Also, I have made a 3.5 inch disk image that can be used to create a preinstalled floppy with a generic kernel.gz. It boots to the point of starting /sbin/init. I strongly recommend people grab this and test out the basic stuff on it. As a footnote, the disk I created above has a slight tweek to the boot1/ boot2 code. One of my machines has a BT545S in it and it's int 0x13 BIOS hooks trash a bit of scratch memory that BTX uses. The tweaked version on the disk above uses a different relocation and callback address. This is not yet resolved, the hack I did could be making things worse, so don't shoot me yet. :-) I have not activated bootforth on the disks.. I guess the /usr/share/examples/bootforth/*.4th files would do as a starter. 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 4 11:34:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA23024 for freebsd-current-outgoing; Mon, 4 Jan 1999 11:34:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-24-dbn.dial-up.net [196.34.155.88]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA22974 for ; Mon, 4 Jan 1999 11:33:57 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id VAA04070; Mon, 4 Jan 1999 21:32:08 +0200 (SAT) From: Robert Nordier Message-Id: <199901041932.VAA04070@ceia.nordier.com> Subject: Re: New boot blocks for serial console ... In-Reply-To: <199901041644.LAA08520@khavrinen.lcs.mit.edu> from Garrett Wollman at "Jan 4, 99 11:44:52 am" To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Mon, 4 Jan 1999 21:32:05 +0200 (SAT) Cc: rnordier@nordier.com, bde@zeta.org.au, rvb@cs.cmu.edu, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garrett Wollman wrote: > < said: > > > Thanks, I wasn't aware that etc/make.conf settings affected the > > old boot blocks. I'll bring the new stuff into line. > > While you're at it, please make it possible to build bootblocks which > *don't* allow user interruption. As they stand now, the ability to > let any old person walk up to a machine and tell it what to boot > represents a serious weakness. I think non-interactive bootblocks have various potential uses, notwithstanding various comments elsewhere. Looking at related functionality, sysinstall presently provides two options for disk slice selection o Boot Manager o Standard MBR where the essential difference is that one is interactive and the other isn't. Given that, providing a non-interactive build option for the bootblocks doesn't seem unreasonable. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 11:34:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA23067 for freebsd-current-outgoing; Mon, 4 Jan 1999 11:34:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles165.castles.com [208.214.165.165]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA23042 for ; Mon, 4 Jan 1999 11:34:08 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id LAA14171; Mon, 4 Jan 1999 11:26:09 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901041926.LAA14171@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Poul-Henning Kamp cc: Mike Smith , "Jordan K. Hubbard" , Garrett Wollman , Tom Bartol , current@FreeBSD.ORG Subject: Re: New boot blocks for serial console ... In-reply-to: Your message of "Mon, 04 Jan 1999 20:14:25 +0100." <15157.915477265@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 04 Jan 1999 11:26:09 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <199901041858.KAA14013@dingo.cdrom.com>, Mike Smith writes: > >> In message <38397.915473345@zippy.cdrom.com>, "Jordan K. Hubbard" writes: > >> >> Not at all. Ever heard of a padlock? > >> > > >> >Give me physical access to your machine, with or without a padlock, > >> >and I'll have root on that baby before you have a chance to come back > >> >from lunch. > >> > > >> >I think the original comment that there's no security without physical > >> >security has definite merit. The NSA learned this decades ago! :) > >> > >> Uhm, well there is, but it is called "tamper-proof hardware" and costs > >> a fortune. > > > >It's not "tamper-proof", it's "tamper-resistant", and I can suggest a > >wide range of "tampering" hardware that it won't stand up to for long. > > No, you bet it is tamper-PROOF. > > They will guarantee that you will not get access to anything in > the computer. Last perimeter will inject 220V (mains) through > vital bits of the computer (including your flash disk) if broken. > > By the time you have gotten through the 10mm steel plate, the computer > is dead. And quite likely you as well, they have versions with > poison-gas release and all sorts of nasties. > > Primary market: ATM & Banking terminals. > > Smallest model and the closest they have to a portable in the > catalog I have here weighs 450 kg (thats 900 pounds), sports 10mm > steel casing (both the outher case and the CPU module case inside > it) it comes with optional holes in the bottom so you can bolt it > to a foundation. It is also IP67 watertight and they will paint > it in any color you like. Price: $CALL. I recommend you find and read a copy of the very excellent, if somewhat dated, "Danger UXB" before being quite so certain. And consider; you still have to be able to open it for maintenance - if a direct physical approach is inefficient, hack the supporting organisation. I could also point out that I have a family background that covers financial IT, and I've seen the aftermath of a number of ATM takeovers both successful and otherwise. I was old enough to be very interested while my father was building a new datacentre (his third, and the second for this company), and got some fairly interesting holiday work in that organisation. 8) Believe me; it doesn't matter how much Heath Robinson hardware you attach to a device to "secure" it - people will still get in. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 11:38:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA23591 for freebsd-current-outgoing; Mon, 4 Jan 1999 11:38:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA23584 for ; Mon, 4 Jan 1999 11:38:28 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id OAA48279; Mon, 4 Jan 1999 14:42:02 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Mon, 4 Jan 1999 14:42:02 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Randy Bush cc: freebsd-current@FreeBSD.ORG Subject: Re: read DMA channel unavailable 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, 4 Jan 1999, Randy Bush wrote: > Jan 2 10:57:34 rip /kernel: sorry, read DMA channel unavailable > Jan 2 11:04:05 rip /kernel: sorry, read DMA channel unavailable > Jan 2 12:48:33 rip /kernel: sorry, read DMA channel unavailable > Jan 2 12:53:56 rip /kernel: sorry, read DMA channel unavailable > Jan 2 12:55:37 rip /kernel: sorry, read DMA channel unavailable > Jan 2 16:15:30 rip /kernel: sorry, read DMA channel unavailable > Jan 2 16:20:06 rip /kernel: sorry, read DMA channel unavailable > Jan 2 16:23:52 rip /kernel: sorry, read DMA channel unavailable > Jan 2 16:57:32 rip /kernel: sorry, read DMA channel unavailable > Jan 2 17:26:42 rip /kernel: sorry, read DMA channel unavailable > Jan 2 17:35:33 rip /kernel: sorry, read DMA channel unavailable > Jan 2 17:39:19 rip /kernel: sorry, read DMA channel unavailable > Jan 2 17:48:41 rip /kernel: sorry, read DMA channel unavailable > Jan 2 18:07:12 rip /kernel: sorry, read DMA channel unavailable > > should i be concerned? It's helpful to summarize the hardware in your PC when including such output, a mail like this stands a pretty good chance of getting you ignored or flamed. with that said, and having experianced the same 'problem' i would say: No, don't worry if you have a sound card and get this message when doing audio work (pcm driver). I don't know why this appeared, but it started showing up on my home machine a month or so ago, it happens everytime i tell x11amp to play a mp3. (it plays fine though) everytime i play something i get 3 of theses messages on my consol, i spoke to Luigi about it and he said it's because sometimes soundblasters flip status registers, and that i shouldn't be concerned. So, if you are using a soundblaster (mine is a SB16) and the pcm driver and get this when playing audio, then ignore it, otherwise send a more verbose mail explaining what hardware is in your system and when these messages get spewed out. thanks, -Alfred > > randy > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 11:39:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA23743 for freebsd-current-outgoing; Mon, 4 Jan 1999 11:39:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA23737 for ; Mon, 4 Jan 1999 11:39:43 -0800 (PST) (envelope-from randy@psg.com) Received: from localhost (940 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Mon, 4 Jan 1999 11:39:18 -0800 (PST) (Smail-3.2.0.101 1997-Dec-17 #1 built 1998-Oct-13) Message-Id: Date: Mon, 4 Jan 1999 11:39:18 -0800 (PST) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Alfred Perlstein Cc: freebsd-current@FreeBSD.ORG Subject: Re: read DMA channel unavailable References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Jan 2 10:57:34 rip /kernel: sorry, read DMA channel unavailable >> Jan 2 11:04:05 rip /kernel: sorry, read DMA channel unavailable > It's helpful to summarize the hardware in your PC when including such > output sorry > No, don't worry if you have a sound card and get this message when doing > audio work (pcm driver). I don't know why this appeared, but it started > showing up on my home machine a month or so ago, it happens everytime i > tell x11amp to play a mp3. (it plays fine though) precisely. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 11:39:52 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA23763 for freebsd-current-outgoing; Mon, 4 Jan 1999 11:39:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA23752 for ; Mon, 4 Jan 1999 11:39:47 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id UAA15271; Mon, 4 Jan 1999 20:36:01 +0100 (CET) To: Mike Smith cc: "Jordan K. Hubbard" , Garrett Wollman , Tom Bartol , current@FreeBSD.ORG Subject: Re: New boot blocks for serial console ... In-reply-to: Your message of "Mon, 04 Jan 1999 11:26:09 PST." <199901041926.LAA14171@dingo.cdrom.com> Date: Mon, 04 Jan 1999 20:35:59 +0100 Message-ID: <15269.915478559@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199901041926.LAA14171@dingo.cdrom.com>, Mike Smith writes: >> >> No, you bet it is tamper-PROOF. >> >> They will guarantee that you will not get access to anything in >> the computer. Last perimeter will inject 220V (mains) through >> vital bits of the computer (including your flash disk) if broken. >> >I recommend you find and read a copy of the very excellent, if somewhat >dated, "Danger UXB" before being quite so certain. And consider; you >still have to be able to open it for maintenance - if a direct physical >approach is inefficient, hack the supporting organisation. That was not what we discussed, we discussed if you could get tamper-PROOF hardware :-) -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 11:44:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA24314 for freebsd-current-outgoing; Mon, 4 Jan 1999 11:44:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from schizo.cdsnet.net (schizo.cdsnet.net [204.118.244.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA24309 for ; Mon, 4 Jan 1999 11:44:37 -0800 (PST) (envelope-from mrcpu@internetcds.com) Received: from localhost (mrcpu@localhost) by schizo.cdsnet.net (8.8.8/8.7.3) with SMTP id LAA07156; Mon, 4 Jan 1999 11:40:02 -0800 (PST) Date: Mon, 4 Jan 1999 11:40:02 -0800 (PST) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: "David W. Chapman Jr." cc: freebsd-current Subject: Re: News Server In-Reply-To: <36907D39.A49114FE@houabg.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 Funny, I was just going to offer to do this... Perhaps we can get this squared away. It would be more useful for me as well. On Mon, 4 Jan 1999, David W. Chapman Jr. wrote: > I guess the solution that I'm looking for is to have the mail list post > to the news server if we do get one. I don't mind posting to > freebsd-current@freebsd.org. But it would better suit me to read from > the news server. With news server it I can read messages in retrospect > of me initially signing on to the mailing list, and wouldn't have to ask > of say the status of the es1370 sound driver. For the people that like > to get the new messages in their inbox, they shouldn't notice any > difference. Anyone interest in a news server please email me so I can > get an idea of whether it is worth pursuing. Please don't cc the > mailing list, I don't want to fill up anybody's mailbox who doesn't care > about this issue. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 11:51:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25331 for freebsd-current-outgoing; Mon, 4 Jan 1999 11:51:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa17-35.ix.netcom.com [207.93.156.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25307 for ; Mon, 4 Jan 1999 11:51:04 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.1/8.8.8) id LAA13474; Mon, 4 Jan 1999 11:20:05 -0800 (PST) (envelope-from tomdean) Date: Mon, 4 Jan 1999 11:20:05 -0800 (PST) Message-Id: <199901041920.LAA13474@ix.netcom.com> From: Thomas Dean To: mark@grondar.za CC: freebsd-current@FreeBSD.ORG In-reply-to: <199901040600.IAA18579@greenpeace.grondar.za> (message from Mark Murray on Mon, 04 Jan 1999 07:59:59 +0200) Subject: make clean problem (was: Perl gv.h Problem) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > From: Mark Murray > There is something wrong in your source tree; I did a aout-to-elf this Maybe I have more problems than gv.h. I am running SMP, elf, -current, as of yesterday. elf binaries and kernel. My source tree is more than 2 years old, being updated weekly with cvsup, except for the last three months of '98. In the past couple of days, I came up-to-date, cvsup-wise as of today. I had to use -DNOPERL to do the aout-to-elf conversion. I want to do a 'make world' and rebuild all the elf binaries to be sure there are no cobwebs. I decided to clean the obj tree, to get rid of the aout things from long ago. 'make clean' does not remove ANY files from /usr/obj/...! It appears to be working in src, not obj. tomdean =============================================== # whoami root # pwd /usr/src # make clean ===> share/info ===> include rm -f osreldate.h version vers.c ===> include/rpcsvc rm -f key_prot.h klm_prot.h mount.h nfs_prot.h nlm_prot.h rex.h rnusers.h rquota.h rstat.h rwall.h sm_inter.h spray.h yppasswd.h yp.h ypxfrd.h ypupdate_prot.h nis.h nis_cache.h nis_callback.h bootparam_prot.h crypt.h ===> lib ===> lib/csu/i386-elf rm -f a.out crt1.o crtbegin.o crtend.o crti.o crtn.o gcrt1.o crt1.o crtbegin.o crtend.o crti.o crtn.o crt1.o.tmp crtbegin.o.tmp crtend.o.tmp crti.o.tmp crtn.o.tmp gcrt1.o.tmp crt1.o.tmp crtbegin.o.tmp crtend.o.tmp crti.o.tmp crtn.o.tmp rm -f lib.a # llib-l.ln rm -f crt1.po crtbegin.po crtend.po crti.po crtn.po gcrt1.po crt1.po crtbegin.po crtend.po crti.po crtn.po crt1.po.tmp crtbegin.po.tmp crtend.po.tmp crti.po.tmp crtn.po.tmp gcrt1.po.tmp crt1.po.tmp crtbegin.po.tmp crtend.po.tmp crti.po.tmp crtn.po.tmp lib_p.a ... # ls /usr/obj/{aout,elf,usr}/usr/src/lib/csu/i386-elf ls: /usr/obj/aout/usr/src/lib/csu/i386-elf: No such file or directory ls: /usr/obj/usr/usr/src/lib/csu/i386-elf: No such file or directory /usr/obj/elf/usr/src/lib/csu/i386-elf: crt1.o crtbegin.so crtend.so crtn.o crtbegin.o crtend.o crti.o gcrt1.o To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 11:53:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25687 for freebsd-current-outgoing; Mon, 4 Jan 1999 11:53:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25392 for ; Mon, 4 Jan 1999 11:51:24 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id VAA04848; Mon, 4 Jan 1999 21:50:33 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id VAA21115; Mon, 4 Jan 1999 21:50:31 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199901041950.VAA21115@greenpeace.grondar.za> To: Thomas Dean cc: freebsd-current@FreeBSD.ORG Subject: Re: make clean problem (was: Perl gv.h Problem) In-Reply-To: Your message of " Mon, 04 Jan 1999 11:20:05 PST." <199901041920.LAA13474@ix.netcom.com> References: <199901041920.LAA13474@ix.netcom.com> Date: Mon, 04 Jan 1999 21:50:30 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas Dean wrote: > I decided to clean the obj tree, to get rid of the aout things from > long ago. 'make clean' does not remove ANY files from /usr/obj/...! > It appears to be working in src, not obj. Something is hosed. Do this: # cd /usr/obj # chflags -R 0 . # rm -rf * # cd /usr/src # make cleandir; make cleandir # cvsup # MAKE 100% SURE YOUR SUPFILE IS CORRECT!! # make aout-to-elf-buildworld # ... etc You may want to consider a clean checkout of the sources at cvsup time; replace the "make cleandir; make cleandir" line with "rm -rf *". 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 Mon Jan 4 12:00:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26561 for freebsd-current-outgoing; Mon, 4 Jan 1999 12:00:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pinhead.parag.codegen.com (ppp-sfx201--019.sirius.net [205.134.235.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA26556 for ; Mon, 4 Jan 1999 12:00:54 -0800 (PST) (envelope-from parag@cgt.com) Received: from pinhead.parag.codegen.com (localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.9.1/8.8.8) with ESMTP id MAA63518 for ; Mon, 4 Jan 1999 12:00:36 -0800 (PST) (envelope-from parag@pinhead.parag.codegen.com) Message-Id: <199901042000.MAA63518@pinhead.parag.codegen.com> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG Subject: Re: 3.0-CURRENT CAM vs scanner problems In-Reply-To: Message from "Kenneth D. Merry" of "Mon, 04 Jan 1999 00:26:40 MST." <199901040726.AAA56886@panzer.plutotech.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 X-URL: http://www.codegen.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 04 Jan 1999 12:00:35 -0800 From: Parag Patel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Whoops - please ignore my previous post - I had not see Kenneth Merry's not about this. Here's the new patch for SANE. I'll resend it to the SANE folks. Thanks again! -- Parag Patel *** sanei/sanei_scsi.c-org Sun Jan 3 16:37:08 1999 - --- sanei/sanei_scsi.c Sun Jan 3 16:37:11 1999 *************** *** 186,192 **** #endif #if USE == FREEBSD_CAM_INTERFACE ! # define MAX_DATA MAXPHYS #endif #ifndef MAX_DATA - --- 186,192 ---- #endif #if USE == FREEBSD_CAM_INTERFACE ! # define MAX_DATA (DFLTPHYS - PAGE_SIZE) #endif #ifndef MAX_DATA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 12:20:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA28674 for freebsd-current-outgoing; Mon, 4 Jan 1999 12:20:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nagual.pp.ru (lsd.relcom.eu.net [193.125.27.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA28656 for ; Mon, 4 Jan 1999 12:20:14 -0800 (PST) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.1/8.9.1) id XAA35611; Mon, 4 Jan 1999 23:19:33 +0300 (MSK) (envelope-from ache) Message-ID: <19990104231932.A34859@nagual.pp.ru> Date: Mon, 4 Jan 1999 23:19:32 +0300 From: "Andrey A. Chernov" To: Randy Bush , Alfred Perlstein Cc: freebsd-current@FreeBSD.ORG Subject: Re: read DMA channel unavailable Mail-Followup-To: Randy Bush , Alfred Perlstein , freebsd-current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from randy@psg.com on Mon, Jan 04, 1999 at 11:39:18AM -0800 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 04, 1999 at 11:39:18AM -0800, Randy Bush wrote: > > No, don't worry if you have a sound card and get this message when doing > > audio work (pcm driver). I don't know why this appeared, but it started > > showing up on my home machine a month or so ago, it happens everytime i > > tell x11amp to play a mp3. (it plays fine though) I have the same messages with my SB16 (AWE32) while running timidity, just recently wrote Luigi about that. -- Andrey A. Chernov ache@null.net MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 12:26:43 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA29526 for freebsd-current-outgoing; Mon, 4 Jan 1999 12:26:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA29520 for ; Mon, 4 Jan 1999 12:26:40 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id MAA39045; Mon, 4 Jan 1999 12:21:52 -0800 (PST) To: Poul-Henning Kamp cc: Mike Smith , Garrett Wollman , Tom Bartol , current@FreeBSD.ORG Subject: Re: New boot blocks for serial console ... In-reply-to: Your message of "Mon, 04 Jan 1999 20:14:25 +0100." <15157.915477265@critter.freebsd.dk> Date: Mon, 04 Jan 1999 12:21:51 -0800 Message-ID: <39041.915481311@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > They will guarantee that you will not get access to anything in > the computer. Last perimeter will inject 220V (mains) through > vital bits of the computer (including your flash disk) if broken. I'm curious how many codicils there are in their contract about "tamper-proof", however. Let's suggest, for example, that the mains power is cut first and then the box is carefully breached by someone highly skilled at bomb disposal and the disabling of anti-handling devices and such. If they can remove the flash disk, they've pretty effectively compromised the data if not the machine's ongoing operations. Is that specifically excluded by their contract, or what exactly? - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 12:34:39 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA00619 for freebsd-current-outgoing; Mon, 4 Jan 1999 12:34:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sasquatch.dannyland.org (sasquatch.dannyland.org [207.229.158.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA00460 for ; Mon, 4 Jan 1999 12:34:36 -0800 (PST) (envelope-from dannyman@sasquatch.dannyland.org) Received: (qmail 17412 invoked by uid 1000); 4 Jan 1999 20:34:34 -0000 Date: Mon, 4 Jan 1999 14:34:34 -0600 From: dannyman To: Ryan Duda Cc: freebsd-current@FreeBSD.ORG Subject: Re: (pw) command hanging in -C. Message-ID: <19990104143433.B16326@enteract.com> References: <36911151.DC9FD1DE@distance.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <36911151.DC9FD1DE@distance.net>; from Ryan Duda on Mon, Jan 04, 1999 at 02:06:57PM -0500 X-Loop: djhoward@uiuc.edu X-URL: http://www.dannyland.org/~dannyman/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 04, 1999 at 02:06:57PM -0500, Ryan Duda wrote: > Is there a reason why "pw usermod username -h 0" would be hanging? This > seems to work fine in 2_2-STABLE. If you're running 2.2, then this question is not apropos to -current. Try -questions next time. How is it hanging? You do understand that it will attempt to read a string from stdin to set the password to, ya? If it is hanging, most likely you have another pwd_mkdb running around somewhere, or you are running a script with does not properly pass it the password. Why are you using pw to set a user password anyway? passwd does a fine job of it, imho. ;) -danny -- ___ http://www.dannyland.org/~dannyman/ dannyman yori aiokomete /___\ University of Illinois: Our Honored Symbol Merits Honored Retirement (o\ | /o) // Beetles and Amigas - I'm a sucker for outdated, unsupported U"""""U \\/ hardware which has retained it's unique personality and grace. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 12:36:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA00798 for freebsd-current-outgoing; Mon, 4 Jan 1999 12:36:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lambic.physics.montana.edu (lambic.physics.montana.edu [153.90.192.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA00790 for ; Mon, 4 Jan 1999 12:36:43 -0800 (PST) (envelope-from handy@lambic.physics.montana.edu) Received: from localhost (handy@localhost) by lambic.physics.montana.edu (8.8.8/8.8.7) with ESMTP id NAA05053; Mon, 4 Jan 1999 13:31:23 -0700 (MST) (envelope-from handy@lambic.physics.montana.edu) Date: Mon, 4 Jan 1999 13:31:23 -0700 (MST) From: Brian Handy To: "Jordan K. Hubbard" cc: Poul-Henning Kamp , Mike Smith , Garrett Wollman , Tom Bartol , current@FreeBSD.ORG Subject: Re: New boot blocks for serial console ... In-Reply-To: <39041.915481311@zippy.cdrom.com> Message-ID: X-files: The truth is out there MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> They will guarantee that you will not get access to anything in >> the computer. Last perimeter will inject 220V (mains) through >> vital bits of the computer (including your flash disk) if broken. > >I'm curious how many codicils there are in their contract about >"tamper-proof", however. [...] What colors does it come in? Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 12:43:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01420 for freebsd-current-outgoing; Mon, 4 Jan 1999 12:43:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA01413 for ; Mon, 4 Jan 1999 12:43:26 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id VAA15579; Mon, 4 Jan 1999 21:37:38 +0100 (CET) To: Brian Handy cc: "Jordan K. Hubbard" , Mike Smith , Garrett Wollman , Tom Bartol , current@FreeBSD.ORG Subject: Re: New boot blocks for serial console ... In-reply-to: Your message of "Mon, 04 Jan 1999 13:31:23 MST." Date: Mon, 04 Jan 1999 21:37:37 +0100 Message-ID: <15577.915482257@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Brian Handy writes: >>> They will guarantee that you will not get access to anything in >>> the computer. Last perimeter will inject 220V (mains) through >>> vital bits of the computer (including your flash disk) if broken. >> >>I'm curious how many codicils there are in their contract about >>"tamper-proof", however. [...] > >What colors does it come in? I think I already said that: any color you like. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 12:52:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA02597 for freebsd-current-outgoing; Mon, 4 Jan 1999 12:52:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa17-35.ix.netcom.com [207.93.156.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA02586 for ; Mon, 4 Jan 1999 12:52:15 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.1/8.8.8) id MAA17167; Mon, 4 Jan 1999 12:51:24 -0800 (PST) (envelope-from tomdean) Date: Mon, 4 Jan 1999 12:51:24 -0800 (PST) Message-Id: <199901042051.MAA17167@ix.netcom.com> From: Thomas Dean To: mark@grondar.za CC: freebsd-current@FreeBSD.ORG In-reply-to: <199901041950.VAA21115@greenpeace.grondar.za> (message from Mark Murray on Mon, 04 Jan 1999 21:50:30 +0200) Subject: Re: make clean problem (was: Perl gv.h Problem) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Something is hosed. cvsup says the files are up-to-date. I moved the Makefiles and the mk files to tmp, and, did a cvsup. The cvsup'ed files are the same. *default host=cvsup.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix *default compress src-all src-eBones src-secure ports-all > Do this: > > # cd /usr/obj > # chflags -R 0 . Most of the files in /usr/obj/... do not have flags set. I did not check all, just the ones make said it removed. > # rm -rf * I know how to delete the obj tree. However, 'make clean' should do it. It looks like the make files do not have the directory structure correct. > # cd /usr/src > # make cleandir; make cleandir If the first 'make cleandir' doesn't do it, the second one will not do better. > # cvsup # MAKE 100% SURE YOUR SUPFILE IS CORRECT!! > # make aout-to-elf-buildworld As I said earlier, I am running an elf kernel and elf binaries. I just want to report a suspected problem with the make structure. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 12:54:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA03122 for freebsd-current-outgoing; Mon, 4 Jan 1999 12:54:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA03112 for ; Mon, 4 Jan 1999 12:54:11 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40325>; Tue, 5 Jan 1999 07:52:56 +1100 Date: Tue, 5 Jan 1999 07:53:36 +1100 From: Peter Jeremy Subject: Re: New boot blocks for serial console ... To: current@FreeBSD.ORG Message-Id: <99Jan5.075256est.40325@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: >> They will guarantee that you will not get access to anything in >> the computer. Last perimeter will inject 220V (mains) through >> vital bits of the computer (including your flash disk) if broken. > >I'm curious how many codicils there are in their contract about >"tamper-proof", however. Probably no more than the software vendor puts in theirs :-). > Let's suggest, for example, that the mains >power is cut first The energy required to adequately fry the semiconductors could be easily stored in capacitors within the box - and even rigged to trigger immediately if the mains disappears (maybe only if the appropriate incantation is not provided beforehand). > If they can remove the flash disk, they've pretty >effectively compromised the data Alternatively, you store the data in volatile RAM. That means the attacker has to maintain power to the RAM whilst removing power from the defenses/offenses. EFTPOS PINpads normally have the DES key stored in volatile RAM inside an epoxy blob with the power wires woven through it to discourage copying. (Against which, I've seen an interesting article (maybe in comp.risks) about volatile RAM having sufficient remanence to allow most of the key to be recovered anyway). 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 4 12:55:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA03360 for freebsd-current-outgoing; Mon, 4 Jan 1999 12:55:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA03345 for ; Mon, 4 Jan 1999 12:55:16 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id VAA21251; Mon, 4 Jan 1999 21:53:51 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Mon, 4 Jan 1999 21:53:51 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Poul-Henning Kamp cc: Brian Handy , "Jordan K. Hubbard" , Mike Smith , Garrett Wollman , Tom Bartol , current@FreeBSD.ORG Subject: Re: New boot blocks for serial console ... In-Reply-To: <15577.915482257@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 4 Jan 1999, Poul-Henning Kamp wrote: > In message > , Brian Handy writes: > >>> I suggest changing subject to "New boot blows" and moving it to -chat. Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 13:00:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04003 for freebsd-current-outgoing; Mon, 4 Jan 1999 13:00:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from exchange1.autotote.com (exchange1.autotote.com [209.118.1.225]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA03989 for ; Mon, 4 Jan 1999 13:00:08 -0800 (PST) (envelope-from tom@wact.net) Received: from wact.net (192.168.10.251 [192.168.10.251]) by exchange1.autotote.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2232.9) id CFJAVW3A; Mon, 4 Jan 1999 15:56:05 -0500 Message-ID: <36912BF5.FDF7260D@wact.net> Date: Mon, 04 Jan 1999 16:00:37 -0500 From: Tom Uffner Organization: POEE X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en, es, de MIME-Version: 1.0 To: "Kevin G. Eliuk" CC: freebsd-current@FreeBSD.ORG Subject: Re: IDE controller Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Probing for devices on PCI bus 0: > chip0: rev 0xb3 on pci0.0.0 > chip1: rev 0xb4 on pci0.2.0 > vga0: rev 0x06 int a irq 0 on pci0.6.0 > ide_pci0: rev 0x20 int a irq 0 on pci0.11.0 > ide_pci: controller is simplex, no DMA on secondary channel > Has anyone have access to the design papers for this cheapset? i have a very similar chipset, for which a workaround Doug White mentioned restored the devices on the secondary controller. recent -current code has a kernel option to disable the probe--you still get the message but the devices work. options DISABLE_PCI_IDE 3.0-CURRENT FreeBSD 3.0-CURRENT #2: Tue Dec 29 10:18:43 EST 1998 Probing for devices on PCI bus 0: chip0: rev 0xb3 on pci0.0.0 chip1: rev 0xb4 on pci0.2.0 vga0: rev 0x01 int a irq 0 on pci0.4.0 ide_pci0: rev 0x20 int a irq 0 on pci0. 11.0 ide_pci: controller is simplex, no DMA on secondary channel . . . wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, accel, dma, iordis wcd0: 4125KB/sec, 128KB cache, audio play, 256 volume levels, ejectable tray wcd0: no disc inside, unlocked -- Tom Uffner tom@wact.net Themes were useless! Destiny was here and the foot pedals were bleeding! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 13:01:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04151 for freebsd-current-outgoing; Mon, 4 Jan 1999 13:01:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA04126 for ; Mon, 4 Jan 1999 13:01:07 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id VAA15627; Mon, 4 Jan 1999 21:44:22 +0100 (CET) To: "Jordan K. Hubbard" cc: Mike Smith , Garrett Wollman , Tom Bartol , current@FreeBSD.ORG Subject: Re: New boot blocks for serial console ... In-reply-to: Your message of "Mon, 04 Jan 1999 12:21:51 PST." <39041.915481311@zippy.cdrom.com> Date: Mon, 04 Jan 1999 21:44:21 +0100 Message-ID: <15625.915482661@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <39041.915481311@zippy.cdrom.com>, "Jordan K. Hubbard" writes: >> They will guarantee that you will not get access to anything in >> the computer. Last perimeter will inject 220V (mains) through >> vital bits of the computer (including your flash disk) if broken. > >I'm curious how many codicils there are in their contract about >"tamper-proof", however. They are graded like bank safes, "number of hours minimum resistance to best known state of the art attack", starting at 4 going up to 168 in this somewhat old catalog". But I think we're getting sidetracked from bootcode here aren't we ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 13:03:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04644 for freebsd-current-outgoing; Mon, 4 Jan 1999 13:03:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from houcbs2.houabg.com (houabg.com [206.109.247.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA04639 for ; Mon, 4 Jan 1999 13:03:12 -0800 (PST) (envelope-from DChapman@houabg.com) Received: by houabg.com with Internet Mail Service (5.0.1457.3) id ; Mon, 4 Jan 1999 14:53:40 -0600 Message-ID: <10DCC1CB8DC5D111A6850040950179A4877E@houabg.com> From: David Chapman To: freebsd-current@FreeBSD.ORG Subject: ELF Date: Mon, 4 Jan 1999 14:53:37 -0600 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1457.3) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As of Jan 6 is FreeBSD totally elf including the kernel? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 13:03:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04672 for freebsd-current-outgoing; Mon, 4 Jan 1999 13:03:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA04656 for ; Mon, 4 Jan 1999 13:03:18 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA202822677; Mon, 4 Jan 1999 10:11:17 -0500 Date: Mon, 4 Jan 1999 10:11:17 -0500 (EST) From: Bill Fumerola To: Peter Jeremy Cc: current@FreeBSD.ORG Subject: Re: New boot blocks for serial console ... In-Reply-To: <99Jan5.075256est.40325@border.alcanet.com.au> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 5 Jan 1999, Peter Jeremy wrote: > The energy required to adequately fry the semiconductors could be > easily stored in capacitors within the box - and even rigged to > trigger immediately if the mains disappears (maybe only if the > appropriate incantation is not provided beforehand). So killing the power would destroy the computer. That is one helluva denial of service attack. Screw nestea2 and the script kiddies, all I need is a pair of bolt cutters. - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 13:08:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05130 for freebsd-current-outgoing; Mon, 4 Jan 1999 13:08:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from distance.net (distance.net [209.142.224.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05123 for ; Mon, 4 Jan 1999 13:08:08 -0800 (PST) (envelope-from spam@distance.net) Received: from distance.net (zula@fl-mi-pm-port-124.lsl.com [209.69.166.124]) by distance.net (8.8.8/8.8.8) with ESMTP id QAA06745; Mon, 4 Jan 1999 16:07:32 -0500 (EST) (envelope-from spam@distance.net) Message-ID: <36912DE2.9EF289CC@distance.net> Date: Mon, 04 Jan 1999 16:08:50 -0500 From: Ryan Duda X-Mailer: Mozilla 4.08 [en] (Win95; I) MIME-Version: 1.0 To: dannyman CC: freebsd-current@FreeBSD.ORG Subject: Re: (pw) command hanging in -C. References: <36911151.DC9FD1DE@distance.net> <19990104143433.B16326@enteract.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am using -CURRENT, I am just stating that this command works fine in 2_2 and is not working in -CURRENT. I want to know if anyone else is having the same problem with the pw command. I am using pw to set 1 string passwords. -RPD dannyman wrote: > > On Mon, Jan 04, 1999 at 02:06:57PM -0500, Ryan Duda wrote: > > > Is there a reason why "pw usermod username -h 0" would be hanging? This > > seems to work fine in 2_2-STABLE. > > If you're running 2.2, then this question is not apropos to -current. Try > -questions next time. > > How is it hanging? You do understand that it will attempt to read a string > from stdin to set the password to, ya? If it is hanging, most likely you have > another pwd_mkdb running around somewhere, or you are running a script with > does not properly pass it the password. > > Why are you using pw to set a user password anyway? passwd does a fine job of > it, imho. ;) > > -danny > > -- > ___ http://www.dannyland.org/~dannyman/ dannyman yori aiokomete > /___\ University of Illinois: Our Honored Symbol Merits Honored Retirement > (o\ | /o) // Beetles and Amigas - I'm a sucker for outdated, unsupported > U"""""U \\/ hardware which has retained it's unique personality and grace. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 13:09:57 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05309 for freebsd-current-outgoing; Mon, 4 Jan 1999 13:09:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from schizo.cdsnet.net (schizo.cdsnet.net [204.118.244.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05300; Mon, 4 Jan 1999 13:09:55 -0800 (PST) (envelope-from mrcpu@internetcds.com) Received: from localhost (mrcpu@localhost) by schizo.cdsnet.net (8.8.8/8.7.3) with SMTP id NAA07638; Mon, 4 Jan 1999 13:05:12 -0800 (PST) Date: Mon, 4 Jan 1999 13:05:12 -0800 (PST) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: dannyman cc: Ryan Duda , freebsd-current@FreeBSD.ORG, port@FreeBSD.ORG Subject: qmail not-installable -- wasRe: (pw) command hanging in -C. In-Reply-To: <19990104143433.B16326@enteract.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 current port of qmail will not install on a very recent -current box (fresh install), if the qmail users do not already exist. For me, pwd_mkdb -C is hanging, hence pw never returns. If you kill the pwd_mkdb, then the line is added to the master.passwd file, and running pwd_mkdb manually will get it intot he proper .db files. Running the exact command from the command line works fine. I don't know what this "read a string from stdin" mumbojumbo is from, pw certainly doesn't read anything from stdin that I know of. It can be forced to read a password from a different file descriptor, but that's not the case here. On Mon, 4 Jan 1999, dannyman wrote: > On Mon, Jan 04, 1999 at 02:06:57PM -0500, Ryan Duda wrote: > > > Is there a reason why "pw usermod username -h 0" would be hanging? This > > seems to work fine in 2_2-STABLE. > > If you're running 2.2, then this question is not apropos to -current. Try > -questions next time. > > How is it hanging? You do understand that it will attempt to read a string > from stdin to set the password to, ya? If it is hanging, most likely you have > another pwd_mkdb running around somewhere, or you are running a script with > does not properly pass it the password. > > Why are you using pw to set a user password anyway? passwd does a fine job of > it, imho. ;) > > -danny > > -- > ___ http://www.dannyland.org/~dannyman/ dannyman yori aiokomete > /___\ University of Illinois: Our Honored Symbol Merits Honored Retirement > (o\ | /o) // Beetles and Amigas - I'm a sucker for outdated, unsupported > U"""""U \\/ hardware which has retained it's unique personality and grace. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 13:12:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05615 for freebsd-current-outgoing; Mon, 4 Jan 1999 13:12:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sasquatch.dannyland.org (sasquatch.dannyland.org [207.229.158.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA05604 for ; Mon, 4 Jan 1999 13:12:39 -0800 (PST) (envelope-from dannyman@sasquatch.dannyland.org) Received: (qmail 17781 invoked by uid 1000); 4 Jan 1999 21:12:38 -0000 Date: Mon, 4 Jan 1999 15:12:38 -0600 From: dannyman To: Jaye Mathisen Cc: Ryan Duda , freebsd-current@FreeBSD.ORG, port@FreeBSD.ORG Subject: Re: qmail not-installable -- wasRe: (pw) command hanging in -C. Message-ID: <19990104151238.F16326@enteract.com> References: <19990104143433.B16326@enteract.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Jaye Mathisen on Mon, Jan 04, 1999 at 01:05:12PM -0800 X-Loop: djhoward@uiuc.edu X-URL: http://www.dannyland.org/~dannyman/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 04, 1999 at 01:05:12PM -0800, Jaye Mathisen wrote: > I don't know what this "read a string from stdin" mumbojumbo is from, pw > certainly doesn't read anything from stdin that I know of. It can be > forced to read a password from a different file descriptor, but that's not > the case here. 'pw usermod user -h 0' means to read password from stdin. -d -- ___ http://www.dannyland.org/~dannyman/ dannyman yori aiokomete /___\ University of Illinois: Our Honored Symbol Merits Honored Retirement (o\ | /o) // Beetles and Amigas - I'm a sucker for outdated, unsupported U"""""U \\/ hardware which has retained it's unique personality and grace. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 13:12:53 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05743 for freebsd-current-outgoing; Mon, 4 Jan 1999 13:12:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05731 for ; Mon, 4 Jan 1999 13:12:50 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id WAA15921; Mon, 4 Jan 1999 22:11:26 +0100 (CET) To: Bill Fumerola cc: Peter Jeremy , current@FreeBSD.ORG Subject: Re: New boot blocks for serial console ... In-reply-to: Your message of "Mon, 04 Jan 1999 10:11:17 EST." Date: Mon, 04 Jan 1999 22:11:26 +0100 Message-ID: <15919.915484286@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Bill Fumerola writes: >On Tue, 5 Jan 1999, Peter Jeremy wrote: > >> The energy required to adequately fry the semiconductors could be >> easily stored in capacitors within the box - and even rigged to >> trigger immediately if the mains disappears (maybe only if the >> appropriate incantation is not provided beforehand). > >So killing the power would destroy the computer. That is one helluva >denial of service attack. Screw nestea2 and the script kiddies, all I need >is a pair of bolt cutters. Well, to some people that is better than them getting access to the data. Usually though, you'll also need a very large crane to lift the thing and the concrete foundation it is bolted onto to get to the wires... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 13:20:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06525 for freebsd-current-outgoing; Mon, 4 Jan 1999 13:20:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA06520 for ; Mon, 4 Jan 1999 13:20:10 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA20362 for ; Mon, 4 Jan 1999 13:15:16 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdu20354; Mon Jan 4 21:15:11 1999 Date: Mon, 4 Jan 1999 13:15:03 -0800 (PST) From: Julian Elischer Reply-To: Julian Elischer To: current@FreeBSD.ORG Subject: [Commit RFC] More Threads patches. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There are soem more patches to make FreeBSD's thread support more real. I would like to add these to those already committed. Note that this functionality is also useful for FreeBSD native threading and the native FreeBSD port of the Linuxthreads package. The patches are a present conditional on the existance of VM_STACK and VM_USE_STACK_FOR_EXEC and VM_USE_STACK. This provides a level of safety to users who are not experimenting with this code by allowing them to create kernels that are "unchanged". The patches I propose to add are at: http://lt.tar.com/vmsdiff with further descriptions availabel at: http://lt.tar.com/ promise to test them better this time :-) here's the description: Growable stack patches: These patches are not required but highly desirable. Without them, each thread consumes 2MB of virtual memory for its stack regardless of how much it really needs. With them, each thread stack will grow (up to 2MB) only as needed. However, they are also more adventuresome. See the discussion below to understand what they do. These patches were updated December 29, and should be fully compatible with COMPAT_LINUX_THREADS. If you apply these patches, they will only be turned on if you recompile your kernal and do a "make world" with the option VM_STACK enabled. It is suggested that you add -DVM_STACK to both CFLAGS and COPTFLAGS in your /etc/make.conf to accomplish this. Further discussion: Growable Stack The changes in this patch are designed to implement vm regions that can "auto grow" as stacks. As noted above, linux threads expects to be able to mmap "auto grow" stacks that become the user stacks of its cloned processes. More generally, I think any thread in FreeBSD, whether a "user thread" or a "kernel thread" would benefit by having an auto grow stack. While linux does not appear to formally restrict the maximum size of its autogrow stacks, I think a limit is highly desireable. The concept of autogrow stacks is supported by adding a MAP_STACK flag to the mmap call. When mmap is called with this option, the region specified (ie. from addr to addr+len) is taken to be the maximum sized stack. The top portion (SGROWSIZ) of the region is initially mapped, and then the region can auto grow down to the bottom (represented by the addr passed in to mmap). This is supported by two new vm calls, vm_map_stack and vm_grow_stack in vm_map.c. The function "grow" is replaced by a similar function "grow_stack" in vm_machdep.c There are many ways to implement growable memory regions to be used as stacks. In fact, this is the second implemenation I have tried. Both appear to work, but the one listed here is better, I think. In the current kernel, there is only one user stack recognised by the kernel, and it is the only "auto grow" memory region. It is created as part of the execve call. When an rfork process is created that shares memory with its creator, this stack region comes along as part of the shared vmspace, and is the stack of the first process in the chain of processes that share the vmspace. When a rfork process is created it needs its own user stack(if it executes in user space). Currently the way this is normally handled is that a fixed size memory region (created by malloc or mmap) is created and grafted onto the rfork process with a little userland assembly code magic. My first implementation of an auto grow stack region involved pulling the stack related elements out of the vmspace structure and making them part of the proc structure, so that user stacks were related to processes and not the (possibly shared) vmspace. Each could have its own. The autogrow feature was implemented by mimicking the existing autogrow code using the stack attributes that moved into the proc structure. This worked fine, and it was fairly easy to see by inspection what the code changes did. However, in considering a threads model in which not every thread corresponded to a kernel process of some kind, I felt that it would be better if the autogrow feature was an attribute of the memory region itself. This way, "user threads", which the kernel might not know about at all, could also have autogrow stacks. This has been implemented by adding an element to the vm_map_entry structure which represents the amount the vm_map_entry could be extended downward. Whenever a page fault is generated that would have resulted in possible call to the existing grow function, the adjoining vm_map_entry region is checked to see if the region can be extended. If so, the region is grown. It is intended that this implementation will not change the existing behaviour of any process unless it is an rforked process which "grafts" itself to a memory region mmaped with the MAP_STACK option (or unless it is an execve'ed process that generates its user stack via vm_map_stack). It is also intended that no memory region will be any different from the existing code unless it is mmaped with the MAP_STACK option. However, it is not necessarily obvious (to me, anyway) that this is so without some study. There are also two levels to the current implementation. One one level (if both VM_USE_STACK and VM_USE_STACK_FOR_EXEC are defined in vm_map.h) the vmspace stack that is normally created in the exec call uses the new vm_map_stack call, and the region is managed by the new vm_grow_stack and grow_stack calls. On the second level (only VM_USE_STACK is defined) the vm_map_stack call is only used for regions mmaped with the MAP_STACK option. The vmspace process stack is created as usual, and is managed by the usual grow function. I hope people will study, critique and test this code. I have run it without problem for about 2 weeks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 13:22:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06730 for freebsd-current-outgoing; Mon, 4 Jan 1999 13:22:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from isds.duke.edu (davinci.isds.duke.edu [152.3.22.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA06721 for ; Mon, 4 Jan 1999 13:22:11 -0800 (PST) (envelope-from sto@stat.Duke.EDU) Received: from cayenne.isds.duke.edu (cayenne.isds.duke.edu [152.3.22.11]) by isds.duke.edu (8.8.8/8.8.8) with ESMTP id QAA11678 for ; Mon, 4 Jan 1999 16:21:44 -0500 (EST) Received: (from sto@localhost) by cayenne.isds.duke.edu (8.8.8/8.8.8) id QAA01226 for freebsd-current@FreeBSD.ORG; Mon, 4 Jan 1999 16:21:44 -0500 (EST) Message-ID: <19990104162143.B25523@stat.Duke.EDU> Date: Mon, 4 Jan 1999 16:21:43 -0500 From: "Sean O'Connell" To: FreeBSD current Subject: procfs fix for cmdlin Reply-To: "Sean O'Connell" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 X-Organization: Institute of Statistics and Decision Sciences Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All- I was just wondering if there was any movement afoot to incorporate these into the tree (at least as a build world option in /etc/make.conf). Are these patches "ready for primetime" or is there a better way? It would sure be nice to have this available as it get's tougher and tougher to sell FreeBSD to my users vis-a-vis that "other *ix" and the weight of applications that it brings to bear. Thanks and keep up the good work. I ask this not to start a flame war rather as a sysadmin who dearly likes FreeBSD and wants to see it prosper. S -- ------------------------------------------------------------------------- Sean O'Connell Email: sean@stat.Duke.EDU Institute of Statistics and Decision Sciences Phone: (919) 684-5419 Duke University Fax: (919) 684-8594 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 13:24:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06891 for freebsd-current-outgoing; Mon, 4 Jan 1999 13:24:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA06876 for ; Mon, 4 Jan 1999 13:24:05 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA209823624; Mon, 4 Jan 1999 10:27:04 -0500 Date: Mon, 4 Jan 1999 10:27:04 -0500 (EST) From: Bill Fumerola To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: New boot blocks for serial console ... In-Reply-To: <15919.915484286@critter.freebsd.dk> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 4 Jan 1999, Poul-Henning Kamp wrote: > >So killing the power would destroy the computer. That is one helluva > >denial of service attack. Screw nestea2 and the script kiddies, all I need > >is a pair of bolt cutters. > > Well, to some people that is better than them getting access to > the data. Usually though, you'll also need a very large crane to > lift the thing and the concrete foundation it is bolted onto to > get to the wires... I'd laugh the first time some construction weenie across the street took out the block's power with a backhoe. We're digressing from boot blocks though... - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 13:29:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA07608 for freebsd-current-outgoing; Mon, 4 Jan 1999 13:29:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA07586 for ; Mon, 4 Jan 1999 13:29:13 -0800 (PST) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id NAA01425; Mon, 4 Jan 1999 13:25:52 -0800 (PST) Date: Mon, 4 Jan 1999 13:25:55 -0800 (PST) From: Tom Bartol To: Poul-Henning Kamp cc: Bill Fumerola , Peter Jeremy , current@FreeBSD.ORG Subject: Re: New boot blocks for serial console ... In-Reply-To: <15919.915484286@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 4 Jan 1999, Poul-Henning Kamp wrote: > In message , Bill Fumerola writes: > >On Tue, 5 Jan 1999, Peter Jeremy wrote: > > > >> The energy required to adequately fry the semiconductors could be > >> easily stored in capacitors within the box - and even rigged to > >> trigger immediately if the mains disappears (maybe only if the > >> appropriate incantation is not provided beforehand). > > > >So killing the power would destroy the computer. That is one helluva > >denial of service attack. Screw nestea2 and the script kiddies, all I need > >is a pair of bolt cutters. > > Well, to some people that is better than them getting access to > the data. Usually though, you'll also need a very large crane to > lift the thing and the concrete foundation it is bolted onto to > get to the wires... > Naaaa! Just whip up a big batch of thermite or shaped charge. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 14:05:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11581 for freebsd-current-outgoing; Mon, 4 Jan 1999 14:05:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11553 for ; Mon, 4 Jan 1999 14:05:02 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id XAA24612 for freebsd-current@FreeBSD.ORG; Mon, 4 Jan 1999 23:04:12 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id DC56B155A; Mon, 4 Jan 1999 21:41:20 +0100 (CET) Date: Mon, 4 Jan 1999 21:41:20 +0100 From: Ollivier Robert To: freebsd-current Subject: Re: sendmail throughput (was: HEADS UP: Postfix is coming. new uid,gid required.) Message-ID: <19990104214120.A29542@keltia.freenix.fr> Mail-Followup-To: freebsd-current References: <36905506.1B4F3BDC@houabg.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <36905506.1B4F3BDC@houabg.com>; from David W. Chapman Jr. on Sun, Jan 03, 1999 at 11:43:34PM -0600 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4931 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to David W. Chapman Jr.: > I personally would like this so I could just ignore people flaming me. > But really, I have to check my email every 2 hours or it fills up. I > would like a news server. Just install a news server and mail2news software. That's very easy. Here is the Perl script I wrote to do just this. Create the groups as moderated ones before. You can subscribe either with a special alias or use + as address. With this alias in /etc/{mail,postfix}/aliases (if you choose to use separate aliases for each list): -=-=- # News::Gateway support # freebsd-test: "|/build/perl/mail2news/freebsd-list freebsd.test" lists: roberto -=-=- moderators (that way, followups go to the lists) -=-=- freebsd.*:%s@freebsd.org -=-=- freebsd-list -=-=- #! /usr/local/bin/perl -w #-*-Perl-*- # mail2news for the FreeBSD lists # # Based on News::Gateway # # $Id$ # require 5.004; use News::Gateway; my $gateway = new News::Gateway 1, 'lists-owner@REPLACE.WITH.YOUR.HOST'; $gateway->modules ('newsgroups', 'headers', mailtonews => [$ARGV[0] || 'freebsd.test'], 'cleanbody'); $gateway->config_file (\*DATA); $gateway->read (\*STDIN); my $error = $gateway->apply (); if ($error) { $gateway->error ($error) } $error = $gateway->post (); if ($error) { $gateway->error ($error) } __END__ header comment replace $n $v header approved replace lists-owner@REPLACE.WITH.YOUR.HOST header cc drop header content-length drop header delivered-to drop header path drop header return-path drop header sender drop header status drop header to drop header date rename group freebsd.announce /(freebsd-|)announce\@freebsd/ group freebsd.bugs /(freebsd-|)bugs\@freebsd/ group freebsd.chat /(freebsd-|)chat\@freebsd/ group freebsd.config /(freebsd-|)config\@freebsd/ group freebsd.current /(freebsd-|)current\@freebsd/ group freebsd.cvs /(freebsd-|)cvs\@freebsd/ group freebsd.doc /(freebsd-|)doc\@freebsd/ group freebsd.fs /(freebsd-|)fs\@freebsd/ group freebsd.hackers /(freebsd-|)hackers\@freebsd/ group freebsd.hardware /(freebsd-|)hardware\@freebsd/ group freebsd.hubs /(freebsd-|)hubs\@freebsd/ group freebsd.mobile /(freebsd-|)mobile\@freebsd/ group freebsd.net /(freebsd-|)net\@freebsd/ group freebsd.ports /(freebsd-|)ports\@freebsd/ group freebsd.scsi /(freebsd-|)scsi\@freebsd/ group freebsd.security /(freebsd-|)security\@freebsd/ group freebsd.smp /(freebsd-|)smp\@freebsd/ -=-=- -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #67: Tue Dec 29 20:24:02 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 14:16:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA12907 for freebsd-current-outgoing; Mon, 4 Jan 1999 14:16:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA12863 for ; Mon, 4 Jan 1999 14:15:58 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id AAA05176; Tue, 5 Jan 1999 00:15:27 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id AAA21694; Tue, 5 Jan 1999 00:15:26 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199901042215.AAA21694@greenpeace.grondar.za> To: Thomas Dean cc: freebsd-current@FreeBSD.ORG Subject: Re: make clean problem (was: Perl gv.h Problem) In-Reply-To: Your message of " Mon, 04 Jan 1999 12:51:24 PST." <199901042051.MAA17167@ix.netcom.com> References: <199901042051.MAA17167@ix.netcom.com> Date: Tue, 05 Jan 1999 00:15:25 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please follow my procedure. I'll explain why as we go along. Thomas Dean wrote: > > Do this: > > > > # cd /usr/obj > > # chflags -R 0 . > > Most of the files in /usr/obj/... do not have flags set. I did not > check all, just the ones make said it removed. I know. This is necessary for the next step. > > # rm -rf * > > I know how to delete the obj tree. However, 'make clean' should do it. > It looks like the make files do not have the directory structure correct. I know. I am getting anally correct here, as you have a problem I do not. "Make clean" has some limitations. > > # cd /usr/src > > # make cleandir; make cleandir > > If the first 'make cleandir' doesn't do it, the second one will not do > better. Crap. The first one cleans out the obj/ structure, the second one, not finding the obj/ dir cleans out the current directory. The rm -rf * above helps to force the issue. I do not know what symlinks you may have, so I am being conservative. > > # cvsup # MAKE 100% SURE YOUR SUPFILE IS CORRECT!! > > # make aout-to-elf-buildworld > > As I said earlier, I am running an elf kernel and elf binaries. I > just want to report a suspected problem with the make structure. I think there is no such problem, I think you have turds in your source tree. 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 Mon Jan 4 14:25:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14117 for freebsd-current-outgoing; Mon, 4 Jan 1999 14:25:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vanessa.eliuk.org (pme117.sunshine.net [209.17.178.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14108 for ; Mon, 4 Jan 1999 14:25:22 -0800 (PST) (envelope-from kevin_eliuk@sunshine.net) Received: from localhost (cagey@localhost) by vanessa.eliuk.org (8.9.1/8.8.8) with SMTP id OAA00786; Mon, 4 Jan 1999 14:24:50 -0800 (PST) (envelope-from cagey@vanessa.eliuk.org) Date: Mon, 4 Jan 1999 14:24:19 -0800 (PST) From: "Kevin G. Eliuk" Reply-To: "Kevin G. Eliuk" To: Tom Uffner cc: current@FreeBSD.ORG Subject: Re: IDE controller In-Reply-To: <36912BF5.FDF7260D@wact.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 4 Jan 1999, Tom Uffner wrote: > i have a very similar chipset, for which a workaround Doug White > mentioned restored the devices on the secondary controller. > recent -current code has a kernel option to disable the probe--you still > get the message but the devices work. > > options DISABLE_PCI_IDE > > 3.0-CURRENT FreeBSD 3.0-CURRENT #2: Tue Dec 29 10:18:43 EST 1998 > > Probing for devices on PCI bus 0: > chip0: rev 0xb3 on pci0.0.0 > chip1: rev 0xb4 on pci0.2.0 > vga0: rev 0x01 int a irq 0 on > pci0.4.0 > ide_pci0: rev 0x20 int a irq 0 on > pci0. > 11.0 > ide_pci: controller is simplex, no DMA on secondary channel > . > . > . > wdc1 at 0x170-0x177 irq 15 on isa > wdc1: unit 0 (atapi): , removable, accel, dma, iordis > wcd0: 4125KB/sec, 128KB cache, audio play, 256 volume levels, ejectable > tray > wcd0: no disc inside, unlocked I'll try that, thanks. Umm, but it doesn't appear to be in the options.i386. Does that matter, or do I have to add it there too? -- Regards, Kevin G. Eliuk Discover Rock Solid, Discover FreeBSD | http://www.FreeBSD.Org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 14:29:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14649 for freebsd-current-outgoing; Mon, 4 Jan 1999 14:29:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (pm3-19.ppp.wenet.net [206.15.85.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14640 for ; Mon, 4 Jan 1999 14:29:21 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.9.1/8.8.8) with ESMTP id OAA00499; Mon, 4 Jan 1999 14:31:18 -0800 (PST) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Mon, 4 Jan 1999 14:31:17 -0800 (PST) From: Alex Zepeda X-Sender: garbanzo@zippy.dyn.ml.org To: Mike Smith cc: Jeroen Ruigrok/Asmodai , Robert Nordier , current@FreeBSD.ORG Subject: Re: Bootblocks / Bootloader In-Reply-To: <199901032052.MAA07318@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 3 Jan 1999, Mike Smith wrote: > That's normal; the "old" help is only displayed in "compatibility" > mode. Without a /boot.config, the bootblocks try to be as quiet as > possible. You may notice the spinner stop for a couple of seconds; if > you hit a key at that point, you'll drop back into "compatibility" mode > again. Oh cool! I was wondering about that for a while, and thought perhaps I still had the old boot blocks installed. How can I reduce the time that it stops the spinner, as I've got little or no use for compat. mode? - 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 4 14:43:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16521 for freebsd-current-outgoing; Mon, 4 Jan 1999 14:43:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (pm3-19.ppp.wenet.net [206.15.85.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA16514 for ; Mon, 4 Jan 1999 14:43:05 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.9.1/8.8.8) with ESMTP id OAA01385; Mon, 4 Jan 1999 14:44:48 -0800 (PST) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Mon, 4 Jan 1999 14:44:48 -0800 (PST) From: Alex Zepeda X-Sender: garbanzo@zippy.dyn.ml.org To: Kenneth Wayne Culver cc: Sue Blake , npe@bfc.dk, freebsd-current@FreeBSD.ORG Subject: Re: Kernel configurator 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 > Unless I'm mistaken, don't the options USERCONFIG, and its visual > counterpart already implement a "Kernel Configurator??" It's my > understanding that they do. Yes, and no. It allows one to configure a pre-made kernel, what the original post was most likely talking about was something used to determine what devices go into the kernel to begin w/. - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD http://www.freebsd.org/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 14:53:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17786 for freebsd-current-outgoing; Mon, 4 Jan 1999 14:53:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA17780 for ; Mon, 4 Jan 1999 14:53:47 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id HAA24421; Tue, 5 Jan 1999 07:47:59 +0900 (JST) Message-ID: <36914512.88F25E22@newsguy.com> Date: Tue, 05 Jan 1999 07:47:46 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Poul-Henning Kamp CC: "Jordan K. Hubbard" , Mike Smith , Garrett Wollman , Tom Bartol , current@FreeBSD.ORG Subject: Re: New boot blocks for serial console ... References: <15625.915482661@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > > In message <39041.915481311@zippy.cdrom.com>, "Jordan K. Hubbard" writes: > >> They will guarantee that you will not get access to anything in > >> the computer. Last perimeter will inject 220V (mains) through > >> vital bits of the computer (including your flash disk) if broken. > > > >I'm curious how many codicils there are in their contract about > >"tamper-proof", however. > > They are graded like bank safes, "number of hours minimum resistance > to best known state of the art attack", starting at 4 going up to > 168 in this somewhat old catalog". > > But I think we're getting sidetracked from bootcode here aren't we ? True enough. How do these things boot? And will they run FreeBSD? :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com "Heart like a Gabriel, pure and white as ivory, soul like a lucifer, black and cold as a piece of lead." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 15:02:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA18762 for freebsd-current-outgoing; Mon, 4 Jan 1999 15:02:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA18755 for ; Mon, 4 Jan 1999 15:02:02 -0800 (PST) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (lxpx37.lx.ehu.es [158.227.99.37]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id AAA01506; Tue, 5 Jan 1999 00:01:32 +0100 (MET) Message-ID: <3691484B.132C56F3@we.lc.ehu.es> Date: Tue, 05 Jan 1999 00:01:31 +0100 From: "José Mª Alcaide" Organization: Universidad del País Vasco - Dept. Electricidad y Electrónica X-Mailer: Mozilla 4.07 [en] (X11; U; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Jeroen Ruigrok/Asmodai CC: FreeBSD Current Subject: Re: READ if ye want the new bootblocks / ELF kernel 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 Jeroen Ruigrok/Asmodai wrote: > > On 04-Jan-99 Jeroen Ruigrok/Asmodai wrote: > > Also, just edit the Makefile.i386 and set OBJFORMAT to elf instead of a.out > > to compile an ELF kernel. > > I meant KERNFORMAT offcourse... > > But as Alfred suggested, an environment variable might work as well... > I think that it's better to edit /etc/make.conf and modify the KERNFORMAT variable. This file is not rewritten when the /usr/src tree is updated by CVSup, while the Makefile.i386 is. -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | http://www.we.lc.ehu.es/~jose Dpto. de Electricidad y Electrónica | Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139 ----------------------------------------------------------------------- "Go ahead... make my day." - H. Callahan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 15:28:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA21764 for freebsd-current-outgoing; Mon, 4 Jan 1999 15:28:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA21756 for ; Mon, 4 Jan 1999 15:28:22 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.8.8/8.8.8) id UAA05580; Mon, 4 Jan 1999 20:40:58 GMT (envelope-from nik) Date: Mon, 4 Jan 1999 20:40:58 +0000 From: Nik Clayton To: jack Cc: Edwin Culp , "freebsd-current@FreeBSD.ORG" Subject: Re: Disk space for a make release. Message-ID: <19990104204058.A5159@catkin.nothing-going-on.org> References: <368FDA1E.7496D0CC@webwizard.org.mx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from jack on Sun, Jan 03, 1999 at 04:36:52PM -0500 Organization: Nik at home, where there's nothing going on Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 03, 1999 at 04:36:52PM -0500, jack wrote: > On Sun, 3 Jan 1999, Edwin Culp wrote: > > > and point that to some other directory that contains only the > > > sources needed by textproc/docproj. > > > > > > I'm told it's a feature. :) > > > > How dumb that makes me feel. Thanks for the tip, I never contemplated this > > feature:-). I'm making a new release now. > > I know _exactly_ how you feel, you weren't the first and probably > won't be the last. > > Suggestion: > Since we already have several ports using their own > subdirectories under ports/distfiles, how about > ports/distfiles/docproj? [Quotes kept for context] Sounds good. Unless someone beats me to it, I'll get to it on Wednesday (patches mailed to me will get acted on even faster :-) ) N -- subterra superque womblia liber To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 15:39:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA22696 for freebsd-current-outgoing; Mon, 4 Jan 1999 15:39:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [207.149.232.62]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA22673 for ; Mon, 4 Jan 1999 15:38:49 -0800 (PST) (envelope-from rgrimes@GndRsh.aac.dev.com) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.8/8.8.8) id PAA28889; Mon, 4 Jan 1999 15:35:15 -0800 (PST) (envelope-from rgrimes) From: "Rodney W. Grimes" Message-Id: <199901042335.PAA28889@GndRsh.aac.dev.com> Subject: Re: aha fix-thank you! In-Reply-To: <199901032302.AAA04420@yedi.iaf.nl> from Wilko Bulte at "Jan 4, 99 00:02:05 am" To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Mon, 4 Jan 1999 15:35:07 -0800 (PST) Cc: imp@village.org, gaylord@gaylord.async.vt.edu, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As Warner Losh wrote... > > In message <199901012025.PAA00554@gaylord.async.vt.edu> Clark Gaylord writes: > > : BTW, I have a 1542B, unknown firmware ... is there a FreeBSD util > > : for reading/loading firmware on these puppies? I recall there > > : being a DOS util, but I can't find that (though I suppose I can > > : probably get it from Adaptec's web site). Right now my drives are > > : <=1GB, but I will probably buy a 4GB soon and I'm not sure I have > > : the right firmware. > > > > I don't think so. Looking at the chips on my AHA-1542B leads me to > > believe that they are EPROMS that need UV light to erase and then a > > EPROM burner to reprogram. > > Right. All the 1542B I've seen use EPROMS, so you need an UV eraser and > an EPROM programmer yo upgrade them I've got the tools and plenty of old EPROMS around if anyone needs a set burned (there are 2 27C128 proms, one is the scsi firware, the other is the host bios). I've probably even got the image files sitting on the HD of the EPROM burner still. I've also done this for 174x's and lots of other cards. -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD http://www.aai.dnsmgr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 16:00:52 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA26210 for freebsd-current-outgoing; Mon, 4 Jan 1999 16:00:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA26202 for ; Mon, 4 Jan 1999 16:00:50 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac4.wam.umd.edu ((IDENT root)@rac4.wam.umd.edu [128.8.10.144]) by po3.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id RAA24677; Mon, 4 Jan 1999 17:56:52 -0500 (EST) Received: from rac4.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1]) by rac4.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id RAA22446; Mon, 4 Jan 1999 17:56:49 -0500 (EST) Received: from localhost by rac4.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id RAA22441; Mon, 4 Jan 1999 17:56:48 -0500 (EST) X-Authentication-Warning: rac4.wam.umd.edu: culverk owned process doing -bs Date: Mon, 4 Jan 1999 17:56:48 -0500 (EST) From: Kenneth Wayne Culver To: Alex Zepeda cc: Sue Blake , npe@bfc.dk, freebsd-current@FreeBSD.ORG Subject: Re: Kernel configurator 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 > > Unless I'm mistaken, don't the options USERCONFIG, and its visual > > counterpart already implement a "Kernel Configurator??" It's my > > understanding that they do. > > Yes, and no. It allows one to configure a pre-made kernel, what the > original post was most likely talking about was something used to > determine what devices go into the kernel to begin w/. That's what I thought, I just wasn't sure. It was my impression however that UNIX wasn't supposed to be that simple. It was supposed to be more stable. besides, unless the people know what they are doing when they look at the configurator program (similar to some Linux dists) they may be even more confused, and it's not that hard to make a custom kernel in the first place. I personally don't think we need a kernel configurator. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 16:27:52 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA00140 for freebsd-current-outgoing; Mon, 4 Jan 1999 16:27:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bsd.mbp.ee (bsd.mbp.ee [194.204.12.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA00133 for ; Mon, 4 Jan 1999 16:27:48 -0800 (PST) (envelope-from mauri@aripaev.ee) Received: from lant.mbp.ee (lant.mbp.ee [194.204.12.41]) by bsd.mbp.ee (8.9.1/8.9.1) with ESMTP id CAA11817 for ; Tue, 5 Jan 1999 02:27:18 +0200 (EET) (envelope-from mauri@aripaev.ee) Received: by lant.mbp.ee with Internet Mail Service (5.5.2232.9) id ; Tue, 5 Jan 1999 02:27:53 +0200 Message-ID: <554419C71610D211B3F8080036362802045E90@lant.mbp.ee> From: Lauri Laupmaa To: "'current@freebsd.org'" Subject: GENERIC compile broken in aic7 ? Date: Tue, 5 Jan 1999 02:27:48 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Thats what I get: ../../dev/aic7xxx/aicasm_gram.y:478: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:479: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:509: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:533: dereferencing pointer to incomplete type *** Error code 1 Stop. *** Error code 1 _____ Lauri To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 16:34:43 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01106 for freebsd-current-outgoing; Mon, 4 Jan 1999 16:34:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gordius.gordian.com (gordius.gordian.com [192.73.220.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA01101 for ; Mon, 4 Jan 1999 16:34:41 -0800 (PST) (envelope-from steve@gordian.com) X-bait: aablmeh@gordian.com,mmblmeh@gordian.com,zzblmeh@gordian.com Received: from delphi.gordian.com (delphi.gordian.com [192.73.220.125]) by gordius.gordian.com (8.9.0.Beta3/8.9.0.Beta3) with ESMTP id QAA22602 for ; Mon, 4 Jan 1999 16:34:15 -0800 (PST) Received: from gordian.com (asclepius [192.73.220.254]) by delphi.gordian.com (8.7.2/8.6.9) with ESMTP id QAA08147 for ; Mon, 4 Jan 1999 16:34:14 -0800 (PST) Message-ID: <36915E05.ADF9C54E@gordian.com> Date: Mon, 04 Jan 1999 16:34:13 -0800 From: Steve Khoo Organization: Gordian; Santa Ana Heights, CA X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 2.2.8-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: DPT SmartRAID V family of RAID Controllers supported? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I know the older SmartRAID IV family is supported, but I was wondering if the new cards are also supported, especially the Fibre Channel controllers. Also, is DLM(Distributed Lock Manager) available on current yet? How about a FreeBSD native dptmgr; I'd prefer not to boot to DOS to run it. I'd appreciate any info. SEK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 16:35:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01377 for freebsd-current-outgoing; Mon, 4 Jan 1999 16:35:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from second.dialup.access.net (lsmarso.dialup.access.net [166.84.254.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA01341 for ; Mon, 4 Jan 1999 16:34:59 -0800 (PST) (envelope-from larry@marso.com) Received: (from larry@localhost) by second.dialup.access.net (8.9.1/8.8.8) id TAA19980 for freebsd-current@freebsd.org; Mon, 4 Jan 1999 19:31:05 -0500 (EST) (envelope-from larry) Date: Mon, 4 Jan 1999 19:31:04 -0500 From: "Larry S. Marso" To: freebsd-current@FreeBSD.ORG Subject: XFree86 elf fails "can't open default font fixed" Message-ID: <19990104193104.H18496@marso.com> Mime-Version: 1.0 Content-Type: multipart/encrypted; protocol="application/pgp-encrypted"; boundary="MGu/vTNewDGZ7tmp" X-Mailer: Mutt 0.94.13i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --MGu/vTNewDGZ7tmp Content-Type: application/pgp-encrypted Version: 1 --MGu/vTNewDGZ7tmp Content-Type: application/octet-stream -----BEGIN PGP MESSAGE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: QywXrumj+baQBJHGxQIEsoz1BwDtUNvg hQEMA8uecfyBRpbdAQf+I7FmarRLsD57vc0wrMcf9OjvorsSTcyD9Re/LG0OhjZA ps27eeelUZ7TD4bn77i0gzpBxXJvgEWmTK1hrJaaPVkdQvflCm3lpg/UMiZuwBpW pWY05d0Zthf58oJxCfo3+/hAxXuaymb4YTCKVldPblXdKX/bMs1GzOvbcjTvHAvu qVLaNiBG5WtQ5oRx+7CnD91VNa3EW1JmD5zEBL/Apx0BEEmGe4UnhBqxu+UV8KWN oB+nI9qVn2SI/0HWlKmlraQgFYTNvoRtvcQu8bLMvKdu6XOTDRoeiYoWGyLXMXTk 4PFrOQwoFBKuJe3vurTavoNGF4VKeRvo9WX8HV8QWIUBDAO48TIXcJ2JYQEIAJIl aPu7Xs5N/DtqNnQJ6TidsASPrA1pK38j+thzqBZP8X31o0sMR9ViCzTNMrM6zCqG G+/+cXA0mdFGEdR3JVAWrYhMDKK8amKXhcj3yeB1xU7Ij1k6hIHBXY5SW8YutWYD NPxjXSx3nuoSXpOmocCxQJR/vw+mWZrzF6spCA36ooyHlh7lAF4iFF/nTMEeSKqg mcb1MHsN97kR7pyjICBfqRgT/gFqyrfqYNqv0C5cc7Kw9K0TcYKrTBo3MiHq18u1 4A6wcyyvW5wdycUkKutmYWJuaULlbrll17uv/c/0SvvHjlOa7AuUWOVRdi9VvNSc wq/qvt7xFhTo29hlqPulAT4MMumdV6QNHe1KeaU228M/AkkwwDz783lCuacF1ouh e1KsGeV7XQl+TWx/UvgnzSxneCm7rbxDooqnhFqej9X9zaflIWSM4TQWrVteCuaM lwzu1zQ5tZEGACt/NTWjGMsnjfaFcL6C/7s8OiAqeuti/N7OdtiunjoquqQQN4ER XvpWNGjXHfxQ0x0n9MZhtITGrbZR7xOajjOQV/ph8TtsmXMqGeYhvjnfCFfj6yem 6ksfMqYv+dNvLSs4/UxUwqZQY5ADsxVVqpyB2aYEglif4c2i+5RAVGSKc5OyqP/5 cV/uPdCGE/UT287EgVEgMvCf8FGzbh9DkeHOWHbKaJGOFBXMgQjSxACvsXfVLcEt EoVlDXbbewQwbsn8zn+5YXwughVSgQQIQC+SvM6TDsSG6o7/s6dvu02IageVBWI= =ZTXW -----END PGP MESSAGE----- --MGu/vTNewDGZ7tmp-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 16:38:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01609 for freebsd-current-outgoing; Mon, 4 Jan 1999 16:38:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from second.dialup.access.net (lsmarso.dialup.access.net [166.84.254.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA01604 for ; Mon, 4 Jan 1999 16:38:31 -0800 (PST) (envelope-from larry@marso.com) Received: (from larry@localhost) by second.dialup.access.net (8.9.1/8.8.8) id TAA19998 for freebsd-current@freebsd.org; Mon, 4 Jan 1999 19:34:42 -0500 (EST) (envelope-from larry) Date: Mon, 4 Jan 1999 19:34:42 -0500 From: "Larry S. Marso" To: freebsd-current@FreeBSD.ORG Subject: XFree86 elf fails "can't open default" Message-ID: <19990104193442.A19990@marso.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.13i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've moved to 3.0-elf. Compiled and installed XFree86 from the ports, the SVGA filter. Now I'm getting: Fatal server error: could not open default font 'fixed' This error appears at the very end, the moment it would launch X. Weird, it worked fine under aout; I haven't changed the config files. Best regards -- Larry S. Marso PS Sorry about sending the "encrypted" version, which was a mistake To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 16:45:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02064 for freebsd-current-outgoing; Mon, 4 Jan 1999 16:45:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA02051 for ; Mon, 4 Jan 1999 16:45:10 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id LAA04556; Tue, 5 Jan 1999 11:14:14 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id LAA73590; Tue, 5 Jan 1999 11:14:20 +1030 (CST) Message-ID: <19990105111420.I70886@freebie.lemis.com> Date: Tue, 5 Jan 1999 11:14:20 +1030 From: Greg Lehey To: "Larry S. Marso" , freebsd-current@FreeBSD.ORG Subject: PGP decryption fails (was: XFree86 elf fails "can't open default font fixed") References: <19990104193104.H18496@marso.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19990104193104.H18496@marso.com>; from Larry S. Marso on Mon, Jan 04, 1999 at 07:31:04PM -0500 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 4 January 1999 at 19:31:04 -0500, Larry S. Marso wrote: > [-- PGP output follows (current time: Tue Jan 5 11:12:56 1999) --] > Warning: Unrecognized ASCII armor header label "MessageID:" ignored. > > This message can only be read by: > keyID: 709D8961 > keyID: 814696DD > > ^GYou do not have the secret key needed to decrypt this file. > > For a usage summary, type: pgp -h > For more detailed help, consult the PGP User's Guide. > [-- End of PGP output --] > > [-- The following data is PGP/MIME encrypted --] > > > [-- End of PGP/MIME encrypted data --] I don't know what's so secret about this message that you need to encrypt it, but I'd guess that you've effectively ensured that nobody will read the message. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 16:56:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03998 for freebsd-current-outgoing; Mon, 4 Jan 1999 16:56:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03989 for ; Mon, 4 Jan 1999 16:56:33 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id LAA04617; Tue, 5 Jan 1999 11:25:23 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id LAA76205; Tue, 5 Jan 1999 11:24:42 +1030 (CST) Message-ID: <19990105112406.J70886@freebie.lemis.com> Date: Tue, 5 Jan 1999 11:24:06 +1030 From: Greg Lehey To: Steve Khoo , freebsd-current@FreeBSD.ORG Subject: Re: DPT SmartRAID V family of RAID Controllers supported? References: <36915E05.ADF9C54E@gordian.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <36915E05.ADF9C54E@gordian.com>; from Steve Khoo on Mon, Jan 04, 1999 at 04:34:13PM -0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 4 January 1999 at 16:34:13 -0800, Steve Khoo wrote: > I know the older SmartRAID IV family is supported, but I was wondering if the > new cards are also supported, especially the Fibre Channel controllers. Not yet. The earliest date is likely to be about April, and that date is not confirmed. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 17:06:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA05551 for freebsd-current-outgoing; Mon, 4 Jan 1999 17:06:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA05546 for ; Mon, 4 Jan 1999 17:06:20 -0800 (PST) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.9.2/8.9.2) with ESMTP id UAA16373; Mon, 4 Jan 1999 20:05:45 -0500 (EST) Date: Mon, 4 Jan 1999 20:05:45 -0500 (EST) From: jack To: Nik Clayton cc: "freebsd-current@FreeBSD.ORG" Subject: Re: Disk space for a make release. In-Reply-To: <19990104204058.A5159@catkin.nothing-going-on.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 4 Jan 1999, Nik Clayton wrote: > Sounds good. Unless someone beats me to it, I'll get to it on Wednesday > (patches mailed to me will get acted on even faster :-) ) I'll send them to you as soon as they're done. -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 17:16:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06777 for freebsd-current-outgoing; Mon, 4 Jan 1999 17:16:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from emu.melbpc.org.au (emu.melbpc.org.au [203.12.152.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA06771 for ; Mon, 4 Jan 1999 17:16:12 -0800 (PST) (envelope-from rsss@melbpc.org.au) Received: from bilby227.melbpc.org.au (bilby227.melbpc.org.au [203.12.153.227]) by emu.melbpc.org.au (8.9.0/8.9.0) with SMTP id MAA22160; Tue, 5 Jan 1999 12:15:40 +1100 (EST) From: rsss@melbpc.org.au (Richard Solly) To: current@FreeBSD.ORG Cc: rnordier@nordier.com Subject: Panic: Changing default root with the elf loader/kernel Date: Tue, 05 Jan 1999 01:15:40 GMT Reply-To: rsss@melbpc.org.au Message-ID: <369166ce.6856128@smtp.melbpc.org.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Following the helpful discussions recently, I converted my recent 3.0 kernel which I thought was elf (but in fact was aout) to genuine elf. Installed the boot loader OK as per Robert Nordier's helpful instructions and booted the kernel. Now one big problem, the boot disk is in fact the 2nd scsi disk (da1) (as well as an IDE disk). It boots OK from what in fact is the 3rd disk, but root always defaults back to the first scsi (da0) and of course the kernel panics when it can't find root. The perturbation which resulted in a default root change with the aout loader/kernel, 2:da(1,a)kernel, is rejected by the new loader. So to avoid a panic with the system and myself (as presently I can't run the elf kenel), how does one change the default root with the new loader. Even better, how does one save this information so it boots automatically and does not require manual input. Richard Solly To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 17:22:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA07393 for freebsd-current-outgoing; Mon, 4 Jan 1999 17:22:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gordius.gordian.com (gordius.gordian.com [192.73.220.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA07388 for ; Mon, 4 Jan 1999 17:21:58 -0800 (PST) (envelope-from steve@gordian.com) X-bait: aablmeh@gordian.com,mmblmeh@gordian.com,zzblmeh@gordian.com Received: from delphi.gordian.com (delphi.gordian.com [192.73.220.125]) by gordius.gordian.com (8.9.0.Beta3/8.9.0.Beta3) with ESMTP id RAA22776; Mon, 4 Jan 1999 17:21:31 -0800 (PST) Received: from gordian.com (asclepius [192.73.220.254]) by delphi.gordian.com (8.7.2/8.6.9) with ESMTP id RAA08633; Mon, 4 Jan 1999 17:21:29 -0800 (PST) Message-ID: <36916918.F8C20BE3@gordian.com> Date: Mon, 04 Jan 1999 17:21:28 -0800 From: Steve Khoo Organization: Gordian; Santa Ana Heights, CA X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 2.2.8-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Greg Lehey CC: freebsd-current@FreeBSD.ORG Subject: Re: DPT SmartRAID V family of RAID Controllers supported? References: <36915E05.ADF9C54E@gordian.com> <19990105112406.J70886@freebie.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > > On Monday, 4 January 1999 at 16:34:13 -0800, Steve Khoo wrote: > > I know the older SmartRAID IV family is supported, but I was wondering if the > > new cards are also supported, especially the Fibre Channel > controllers. > > Not yet. The earliest date is likely to be about April, and that date > is not confirmed. > > Greg > -- > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key Hmmm... That's too bad. How about DLM and dptmgr for FreeBSD? Any idea when they'll be available? Thanks for the info. SEK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 17:30:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08292 for freebsd-current-outgoing; Mon, 4 Jan 1999 17:30:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from schizo.cdsnet.net (schizo.cdsnet.net [204.118.244.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA08271 for ; Mon, 4 Jan 1999 17:30:09 -0800 (PST) (envelope-from mrcpu@internetcds.com) Received: from localhost (mrcpu@localhost) by schizo.cdsnet.net (8.8.8/8.7.3) with SMTP id RAA09018 for ; Mon, 4 Jan 1999 17:25:35 -0800 (PST) Date: Mon, 4 Jan 1999 17:25:34 -0800 (PST) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: current@FreeBSD.ORG Subject: How's 3.0-current as an NFS client? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Back a few months ago, there was some concern about the stability/robustness of 3.x wrt NFS. I'm about to upgrade a box that for us is semi-mission-critical, to 3.0-current, since it's running an old 3.x just peachy, but wanted to make sure that there weren't any current NFS gotcha'sthat I've missed in the mailing lists. Thanks in advance. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 17:56:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA10935 for freebsd-current-outgoing; Mon, 4 Jan 1999 17:56:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (korea-139.ppp.hooked.net [206.169.225.139]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA10927 for ; Mon, 4 Jan 1999 17:56:12 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.9.1/8.8.8) with ESMTP id OAA01379; Mon, 4 Jan 1999 14:44:07 -0800 (PST) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Mon, 4 Jan 1999 14:44:06 -0800 (PST) From: Alex Zepeda X-Sender: garbanzo@zippy.dyn.ml.org To: Jonathan Smith cc: npe@bfc.dk, freebsd-current@FreeBSD.ORG Subject: Re: Kernel configurator 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, 4 Jan 1999, Jonathan Smith wrote: > Personally, I think it would be nice. I've been doing my own kernels by > hand, but it would be nicer. Howerver, my complaint with the Linux one is > that it is graphical only. Perhaps one that would attempt an X connection > then default to curses in a text wnindow? Uhh, no. It's not, not in the least is it graphical only. Try make config sometime. Or you can edit the files by hand (or w/ script) to your satisfaction to change the defaults, etc. - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD http://www.freebsd.org/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 17:57:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA11043 for freebsd-current-outgoing; Mon, 4 Jan 1999 17:57:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA11038 for ; Mon, 4 Jan 1999 17:57:28 -0800 (PST) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.9.1/8.8.7) with ESMTP id UAA18392; Mon, 4 Jan 1999 20:56:48 -0500 (EST) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: "Jordan K. Hubbard" cc: "Daniel C. Sobral" , freebsd-current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: 3.0-19981226-SNAP/src/ssys.ac is corrupt In-reply-to: Your message of "Mon, 04 Jan 1999 10:03:44 PST." <38332.915473024@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 04 Jan 1999 20:56:47 -0500 Message-ID: <18388.915501407@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote in message ID <38332.915473024@zippy.cdrom.com>: > Perhaps there's a data-sensitive router somewhere in the path, > e.g. one which flakes when certain bit patterns fly by. I've seen it > happen with terminal servers of various types but rarely a full-blown > cisco router. All I know is that when I verified the files on > this end, they were fine. Or it could be they're all traversing the same link which has a bad CSU/DSU or repeater and can't maintain ones density for that particular bit pattern. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 17:57:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA11061 for freebsd-current-outgoing; Mon, 4 Jan 1999 17:57:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA11055 for ; Mon, 4 Jan 1999 17:57:33 -0800 (PST) (envelope-from dbushong@CSUA.Berkeley.EDU) Received: (from dbushong@localhost) by soda.CSUA.Berkeley.EDU (8.8.8/) id RAA16062; Mon, 4 Jan 1999 17:57:01 -0800 (PST) env-from (dbushong) From: dbushong@CSUA.Berkeley.EDU (David Bushong) Message-Id: <199901050157.RAA16062@soda.CSUA.Berkeley.EDU> Subject: Re: GENERIC compile broken in aic7 ? In-Reply-To: <554419C71610D211B3F8080036362802045E90@lant.mbp.ee> from Lauri Laupmaa at "Jan 5, 99 02:27:48 am" To: mauri@aripaev.ee (Lauri Laupmaa) Date: Mon, 4 Jan 1999 17:57:01 -0800 (PST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think this is using some new yacc syntax. Do an installworld first, then it will work (or just make sure you have the most recent installed make, yacc, gcc, etc etc) --David Bushong > Hi > > Thats what I get: > > ../../dev/aic7xxx/aicasm_gram.y:478: dereferencing pointer to incomplete > type > ../../dev/aic7xxx/aicasm_gram.y:479: dereferencing pointer to incomplete > type > ../../dev/aic7xxx/aicasm_gram.y:509: dereferencing pointer to incomplete > type > ../../dev/aic7xxx/aicasm_gram.y:533: dereferencing pointer to incomplete > type > *** Error code 1 > > Stop. > *** Error code 1 > > _____ > Lauri > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 18:44:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA15466 for freebsd-current-outgoing; Mon, 4 Jan 1999 18:44:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA15461; Mon, 4 Jan 1999 18:44:06 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id VAA12558; Mon, 4 Jan 1999 21:43:22 -0500 (EST) Date: Mon, 4 Jan 1999 21:43:22 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Kris Kennaway cc: Wiliam Woods , FBSD_QUESTIONS , FBSD_CURRENT Subject: Re: pgcc-1.1.1 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, 4 Jan 1999, Kris Kennaway wrote: > On Sun, 3 Jan 1999, Wiliam Woods wrote: > > > Anyone here useing pgcc-1.1.1 as their compiler of choice, to replace gcc? I > > have been debating playing with this on my "spare" system. > > Any reports from someone useing this, good or bad? > > I use egcs-1.1.1 (on which pgcc is based) to compile most of my stuff here, > including the world. There are a few small "gotchas", namely bits of the > system which will not compile (for me): > > lib/libc lib/libc_r lib/libstand games/rogue libexec/rtld-elf games/bs > gnu/lib/libg++ gnu/lib/libstdc++ gnu/usr.bin/groff sys/boot/ sys/modules > > I have a small script which recompiles these using CC and CFLAGS and the > system gcc, and then just do my usual make depend/make all -j4 cycle to do the > rest. The kernel is also not compilable with egcs due to FreeBSD-specific > extensions in our gcc compiler. > > There are the odd one or two ports I've come across which can't be compiled > using egcs, but for the most part it works very nicely. A quick-n-dirty > benchmark: > > # dd if=/dev/random of=/usr2/bigfile bs=1024k count=30 > # cp /usr2/bigfile /usr2/bigfile2 > # /usr/bin/time gzip-486 -9 /usr2/bigfile > 26.06 real 20.46 user 1.17 sys > # /usr/bin/time gzip-pent -9 /usr2/bigfile2 > 23.12 real 18.58 user 1.20 sys > > i.e. a speedup of about 12% > > gzip-486 was compiled with the stock gcc, -O2 -mno-486 > gzip-pentium was compiled with egcs-1.1.1 from the ports collection, -O2 > -mpentium -march-pentium > > Incidentally, the dd command spammed the heck out of my machine..good DoS, > anyone? :) --- src/sys/i386/i386/mem.c.orig Wed Dec 30 13:21:32 1998 +++ src/sys/i386/i386/mem.c Wed Dec 30 13:26:37 1998 @@ -287,6 +287,11 @@ c = iov->iov_len; break; } + if ((error = CURSIG(curproc)) != 0) { + postsig(error); + error = EINTR; + break; + } if (buf == NULL) buf = (caddr_t) malloc(PAGE_SIZE, M_TEMP, M_WAITOK); @@ -300,6 +305,11 @@ case 12: if (uio->uio_rw == UIO_WRITE) { c = iov->iov_len; + break; + } + if ((error = CURSIG(curproc)) != 0) { + postsig(error); + error = EINTR; break; } if (zbuf == NULL) { > > Kris > > > > > > Thanks, > > > > Bill > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > ----- > (ASP) Microsoft Corporation (MSFT) announced today that the release of its > productivity suite, Office 2000, will be delayed until the first quarter > of 1901. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 18:58:02 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA16941 for freebsd-current-outgoing; Mon, 4 Jan 1999 18:58:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from as5200-01-254.no.neosoft.com (as5200-01-254.no.neosoft.com [206.27.167.254]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA16926 for ; Mon, 4 Jan 1999 18:57:54 -0800 (PST) (envelope-from conrads@as5200-01-254.no.neosoft.com) Received: (from conrads@localhost) by as5200-01-254.no.neosoft.com (8.9.1/8.8.7) id UAA01256; Mon, 4 Jan 1999 20:55:17 -0600 (CST) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 04 Jan 1999 20:55:16 -0600 (CST) Reply-To: conrads@neosoft.com From: Conrad Sabatier To: Leif Neland Subject: Re: user-ppp broken since a few days ago? Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm seeing the same problem with a recently-built kernel (cvsup 1/3/99). Have to revert back to my old kernel for now just to get connected. It seems the authenticate phase is never being reached for some reason. Weird. > On Fri, 27 Nov 1998, Leif Neland wrote: > >> I usually run cvsup and make world every night (don't want the poor >> machine to get bored...) >> >> A few mornings ago I couldn't connect anymore with ppp. >> Luckily I got the idea of using /stand/ppp, and it works. >> >> -r-xr-xr-x 19 root bin 1171456 24 Jul 06:59 /stand/ppp >> -r-sr-xr-- 1 root network 193212 26 Nov 04:54 >> /usr/sbin/ppp >> >> Logfile of current ppp: >> Nov 27 02:24:00 gina ppp[222]: tun0: Phase: deflink: dial -> login >> Nov 27 02:24:00 gina ppp[222]: tun0: Phase: deflink: login -> lcp >> Nov 27 02:24:00 gina ppp[222]: tun0: LCP: FSM: Using "deflink" as a >> transport >> Nov 27 02:24:00 gina ppp[222]: tun0: LCP: deflink: State change Initial >> --> Closed >> Nov 27 02:24:00 gina ppp[222]: tun0: LCP: deflink: State change Closed >> --> Stopped >> Nov 27 02:24:02 gina ppp[222]: tun0: Phase: Unknown protocol 0x0801 >> (unrecognised protocol) >> Nov 27 02:24:02 gina ppp[222]: tun0: LCP: deflink: SendProtocolRej(1) >> state = Stopped >> Nov 27 02:24:03 gina ppp[222]: tun0: LCP: deflink: LayerStart >> Nov 27 02:24:03 gina ppp[222]: tun0: LCP: deflink: SendConfigReq(1) >> state = Stopped >> Nov 27 02:24:03 gina ppp[222]: tun0: LCP: ACFCOMP[2] >> Nov 27 02:24:03 gina ppp[222]: tun0: LCP: PROTOCOMP[2] >> Nov 27 02:24:03 gina ppp[222]: tun0: LCP: ACCMAP[6] 0x00000000 >> Nov 27 02:24:03 gina ppp[222]: tun0: LCP: MRU[4] 1500 >> Nov 27 02:24:03 gina ppp[222]: tun0: LCP: MAGICNUM[6] 0x71f4a124 >> Nov 27 02:24:03 gina ppp[222]: tun0: LCP: deflink: State change Stopped >> --> Req-Sent >> Nov 27 02:24:05 gina ppp[222]: tun0: Phase: deflink: Carrier lost >> Nov 27 02:24:05 gina ppp[222]: tun0: LCP: deflink: State change Req-Sent >> --> Starting >> Nov 27 02:24:05 gina ppp[222]: tun0: LCP: deflink: LayerFinish >> Nov 27 02:24:05 gina ppp[222]: tun0: LCP: deflink: State change Starting >> --> Initial >> Nov 27 02:24:05 gina ppp[222]: tun0: Phase: deflink: Disconnected! >> Nov 27 02:24:05 gina ppp[222]: tun0: Phase: deflink: lcp -> hangup >> Nov 27 02:24:05 gina ppp[222]: tun0: Phase: deflink: Connect time: 9 >> secs: 23 octets in, 74 octets out >> Nov 27 02:24:05 gina ppp[222]: tun0: Phase: total 10 bytes/sec, peak 19 >> bytes/sec on Fri Nov 27 02:24:05 1998 >> Nov 27 02:24:05 gina ppp[222]: tun0: Phase: deflink: hangup -> closed >> Nov 27 02:24:05 gina ppp[222]: tun0: Phase: bundle: Dead >> >> /stand/ppp: >> >> Nov 27 02:26:07 gina ppp[560]: tun0: Connect: CONNECT >> Nov 27 02:26:07 gina ppp[560]: tun0: IPCP: Using trigger address 0.0.0.0 >> Nov 27 02:26:07 gina ppp[560]: tun0: LCP: State change Initial --> >> Closed >> Nov 27 02:26:07 gina ppp[560]: tun0: LCP: State change Closed --> >> Stopped >> Nov 27 02:26:09 gina ppp[560]: tun0: LCP: LcpSendConfigReq >> Nov 27 02:26:09 gina ppp[560]: tun0: LCP: ACFCOMP[2] >> Nov 27 02:26:09 gina ppp[560]: tun0: LCP: PROTOCOMP[2] >> Nov 27 02:26:09 gina ppp[560]: tun0: LCP: ACCMAP[6] 0x00000000 >> Nov 27 02:26:09 gina ppp[560]: tun0: LCP: MRU[4] 1500 >> Nov 27 02:26:09 gina ppp[560]: tun0: LCP: MAGICNUM[6] 0x1ddb61c0 >> Nov 27 02:26:09 gina ppp[560]: tun0: LCP: State change Stopped --> >> Req-Sent >> Nov 27 02:26:09 gina ppp[560]: tun0: LCP: Received Configure Reject (1) >> state = Req-Sent (6) >> Nov 27 02:26:09 gina ppp[560]: tun0: LCP: RecvConfigRej. >> Nov 27 02:26:09 gina ppp[560]: tun0: LCP: PROTOCOMP[2] >> Nov 27 02:26:09 gina ppp[560]: tun0: LCP: ACFCOMP[2] >> Nov 27 02:26:09 gina ppp[560]: tun0: LCP: LcpSendConfigReq >> Nov 27 02:26:09 gina ppp[560]: tun0: LCP: ACCMAP[6] 0x00000000 >> Nov 27 02:26:09 gina ppp[560]: tun0: LCP: MRU[4] 1500 >> Nov 27 02:26:09 gina ppp[560]: tun0: LCP: MAGICNUM[6] 0x1ddb61c0 >> Nov 27 02:26:10 gina ppp[560]: tun0: LCP: Received Configure Ack (2) >> state = Req-Sent (6) >> Nov 27 02:26:10 gina ppp[560]: tun0: LCP: State change Req-Sent --> >> Ack-Rcvd >> Nov 27 02:26:10 gina ppp[560]: tun0: LCP: Received Configure Request (1) >> state = Ack-Rcvd (7) >> Nov 27 02:26:10 gina ppp[560]: tun0: LCP: ACCMAP[6] 0x00000000 >> Nov 27 02:26:10 gina ppp[560]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) >> Nov 27 02:26:10 gina ppp[560]: tun0: LCP: MAGICNUM[6] 0x0267d36b >> Nov 27 02:26:10 gina ppp[560]: tun0: LCP: SendConfigAck(Ack-Rcvd) >> Nov 27 02:26:10 gina ppp[560]: tun0: LCP: ACCMAP[6] 0x00000000 >> Nov 27 02:26:10 gina ppp[560]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) >> Nov 27 02:26:10 gina ppp[560]: tun0: LCP: MAGICNUM[6] 0x0267d36b >> Nov 27 02:26:10 gina ppp[560]: tun0: LCP: State change Ack-Rcvd --> >> Opened >> Nov 27 02:26:10 gina ppp[560]: tun0: LCP: LcpLayerUp >> Nov 27 02:26:10 gina ppp[560]: tun0: Phase: NewPhase: Authenticate >> Nov 27 02:26:10 gina ppp[560]: tun0: Phase: his = PAP, mine = none >> Nov 27 02:26:10 gina ppp[560]: tun0: Phase: PAP: idk70486 >> Nov 27 02:26:10 gina ppp[560]: tun0: Phase: PapInput: ACK >> Nov 27 02:26:10 gina ppp[560]: tun0: Phase: Received PAP_ACK (Login >> Succeeded) >> Nov 27 02:26:10 gina ppp[560]: tun0: Phase: NewPhase: Network >> Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: State change Initial --> >> Closed >> Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: IPCP Up event!! >> Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: IpcpSendConfigReq >> Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: IPADDR[6] 0.0.0.0 >> Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: COMPPROTO[6] 16 VJ slots >> with slot compres >> Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: State change Closed --> >> Req-Sent >> Nov 27 02:26:10 gina ppp[560]: tun0: CCP: State change Initial --> >> Closed >> Nov 27 02:26:10 gina ppp[560]: tun0: CCP: CCP Up event!! >> Nov 27 02:26:10 gina ppp[560]: tun0: CCP: CcpSendConfigReq >> Nov 27 02:26:10 gina ppp[560]: tun0: CCP: DEFLATE[4] win 15 >> Nov 27 02:26:10 gina ppp[560]: tun0: CCP: PRED1[2] >> Nov 27 02:26:10 gina ppp[560]: tun0: CCP: State change Closed --> >> Req-Sent >> Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: Received Configure Request >> (1) state = Req-Sent (6) >> Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: COMPPROTO[6] 16 VJ slots >> without slot compression >> Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: IPADDR[6] 194.19.140.21 >> Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: SendConfigAck(Req-Sent) >> Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: COMPPROTO[6] 16 VJ slots >> without slot compression >> Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: IPADDR[6] 194.19.140.21 >> Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: State change Req-Sent --> >> Ack-Sent >> Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: Received Configure Nak (1) >> state = Ack-Sent (8) >> Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: IPADDR[6] 194.255.12.232 >> Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: IPADDR[6] changing address: >> 0.0.0.0 --> 194.255.12.232 >> Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: IpcpSendConfigReq >> Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: IPADDR[6] 194.255.12.232 >> Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: COMPPROTO[6] 16 VJ slots >> with slot compres >> Nov 27 02:26:10 gina ppp[560]: tun0: LCP: Received Protocol Reject (2) >> state = Opened (9) >> Nov 27 02:26:10 gina ppp[560]: tun0: LCP: -- Protocol (80fd) was >> rejected. >> Nov 27 02:26:10 gina ppp[560]: tun0: CCP: CcpLayerFinish. >> Nov 27 02:26:10 gina ppp[560]: tun0: CCP: State change Req-Sent --> >> Stopped >> Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: Received Configure Ack (2) >> state = Ack-Sent (8) >> Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: State change Ack-Sent --> >> Opened >> Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: IpcpLayerUp(9). >> Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: myaddr = 194.255.12.232 >> hisaddr = 194.19.140.21 >> Nov 27 02:26:10 gina ppp[560]: tun0: LCP: OsLinkup: 194.19.140.21 >> >> What's up? Why only me? Or are the others who are hit by this unable to >> get connected at all and tell us? :-) >> >> Leif -- Conrad Sabatier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 19:45:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA21055 for freebsd-current-outgoing; Mon, 4 Jan 1999 19:45:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from megaweapon.zigg.com (megaweapon.zigg.com [206.114.60.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA21045 for ; Mon, 4 Jan 1999 19:45:06 -0800 (PST) (envelope-from matt@megaweapon.zigg.com) Received: from localhost (matt@localhost) by megaweapon.zigg.com (8.8.8/8.8.8) with ESMTP id WAA11838 for ; Mon, 4 Jan 1999 22:44:36 -0500 (EST) (envelope-from matt@megaweapon.zigg.com) Date: Mon, 4 Jan 1999 22:44:35 -0500 (EST) From: Matt Behrens To: current@FreeBSD.ORG Subject: Re: New boot blocks for serial console ... In-Reply-To: <15577.915482257@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 4 Jan 1999, Poul-Henning Kamp wrote: In message , Brian Handy writes: : >What colors does it come in? : I think I already said that: any color you like. As long as it's putty. (apologies to Mr. Ford) - Matt Behrens Network Administrator, zigg.com Engineer, Nameless IRC Network To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 20:09:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA23894 for freebsd-current-outgoing; Mon, 4 Jan 1999 20:09:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA23889 for ; Mon, 4 Jan 1999 20:09:55 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id UAA91110; Mon, 4 Jan 1999 20:09:25 -0800 (PST) (envelope-from dillon) Date: Mon, 4 Jan 1999 20:09:25 -0800 (PST) From: Matthew Dillon Message-Id: <199901050409.UAA91110@apollo.backplane.com> To: Julian Elischer Cc: current@FreeBSD.ORG Subject: Re: [Commit RFC] More Threads patches. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :There are soem more patches to make FreeBSD's thread support more real. :I would like to add these to those already committed. :Note that this functionality is also useful for FreeBSD native threading :and the native FreeBSD port of the Linuxthreads package. : :The patches are a present conditional on the existance of VM_STACK :and VM_USE_STACK_FOR_EXEC and VM_USE_STACK. This provides a level of :safety to users who are not experimenting with this code by allowing :them to create kernels that are "unchanged". : :The patches I propose to add are at: :http://lt.tar.com/vmsdiff :with :further descriptions availabel at: :http://lt.tar.com/ : :promise to test them better this time :-) I think this would be perfect for the new -current, post-split. There are a bunch of people, including me, who are holding onto pretty major patchsets to commit into the new -current after the split. I'm not crossing my fingers on stability -- I fully expect there to be some problems considering that you, me, Eivind, and I think John intend to do some serious commits into the new -current branch. I expect in about 6-12 months the revamped VM system in the new -current will be moved into the new -stable wholesale. This is my dream, anyway :-) In anycase, you have the opportunity to get your stuff into a true test kernel, allow other people to munch on it for a month or two, and then (considering the relative simplicity of your changes), fold it into the new -stable. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 20:32:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA25494 for freebsd-current-outgoing; Mon, 4 Jan 1999 20:30:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA25488 for ; Mon, 4 Jan 1999 20:30:43 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (peter@localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Netplex) with ESMTP id MAA18887; Tue, 5 Jan 1999 12:29:54 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199901050429.MAA18887@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon cc: Julian Elischer , current@FreeBSD.ORG Subject: Re: [Commit RFC] More Threads patches. In-reply-to: Your message of "Mon, 04 Jan 1999 20:09:25 PST." <199901050409.UAA91110@apollo.backplane.com> Date: Tue, 05 Jan 1999 12:29:52 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > : > :There are soem more patches to make FreeBSD's thread support more real. > :I would like to add these to those already committed. > :Note that this functionality is also useful for FreeBSD native threading > :and the native FreeBSD port of the Linuxthreads package. > : > :The patches are a present conditional on the existance of VM_STACK > :and VM_USE_STACK_FOR_EXEC and VM_USE_STACK. This provides a level of > :safety to users who are not experimenting with this code by allowing > :them to create kernels that are "unchanged". > : > :The patches I propose to add are at: > :http://lt.tar.com/vmsdiff > :with > :further descriptions availabel at: > :http://lt.tar.com/ > : > :promise to test them better this time :-) > > I think this would be perfect for the new -current, post-split. There > are a bunch of people, including me, who are holding onto pretty major > patchsets to commit into the new -current after the split. I'm not > crossing my fingers on stability -- I fully expect there to be some > problems considering that you, me, Eivind, and I think John intend to do > some serious commits into the new -current branch. We can't halt progress just for developer convenience.. I have around 6 (or 7) branches from -current that I maintain and keep up to date. One has about 200K lines of diffs and probably won't see the light of day in that form, but is coming out piecemeal. Things like perforce make this fairly easy to do and stay sane at the same time. The patches above seem to work fairly well, apart from some design tradeoffs (moving sigacts out of struct user always, for example). 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 4 21:14:57 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA29390 for freebsd-current-outgoing; Mon, 4 Jan 1999 21:14:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles182.castles.com [208.214.165.182]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA29385 for ; Mon, 4 Jan 1999 21:14:54 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id VAA00479; Mon, 4 Jan 1999 21:11:30 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901050511.VAA00479@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: rsss@melbpc.org.au cc: current@FreeBSD.ORG Subject: Re: Panic: Changing default root with the elf loader/kernel In-reply-to: Your message of "Tue, 05 Jan 1999 01:15:40 GMT." <369166ce.6856128@smtp.melbpc.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 04 Jan 1999 21:11:29 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Following the helpful discussions recently, I converted my > recent 3.0 kernel which I thought was elf (but in fact was > aout) to genuine elf. Installed the boot loader OK as per > Robert Nordier's helpful instructions and booted the > kernel. > > Now one big problem, the boot disk is in fact the 2nd scsi > disk (da1) (as well as an IDE disk). It boots OK from what > in fact is the 3rd disk, but root always defaults back to > the first scsi (da0) and of course the kernel panics when it > can't find root. > > The perturbation which resulted in a default root change > with the aout loader/kernel, 2:da(1,a)kernel, is rejected > by the new loader. > > So to avoid a panic with the system and myself (as presently > I can't run the elf kenel), how does one change the default > root with the new loader. Even better, how does one save > this information so it boots automatically and does not > require manual input. Start by breaking to the loader commandline, and say set num_ide_disks=1 boot You may need: set currdev=disk3s1a: if it hasn't already set the current device correctly. Please let me know how you go with this; I don't have such a senario to test with at the moment, but will definitely do whatever is required to make it work properly. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 21:29:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA01145 for freebsd-current-outgoing; Mon, 4 Jan 1999 21:29:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chmls11.mediaone.net (chmls11.mediaone.net [24.128.1.112]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA01140 for ; Mon, 4 Jan 1999 21:29:50 -0800 (PST) (envelope-from veldy@visi.com) Received: from visi.com (h-181-76.mn.mediaone.net [209.32.181.76]) by chmls11.mediaone.net (8.8.7/8.8.7) with ESMTP id AAA27671; Tue, 5 Jan 1999 00:28:39 -0500 (EST) Message-ID: <3691A33F.B2F8C67B@visi.com> Date: Mon, 04 Jan 1999 23:29:35 -0600 From: "Thomas T. Veldhouse" X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith CC: rsss@melbpc.org.au, current@FreeBSD.ORG Subject: Re: Panic: Changing default root with the elf loader/kernel References: <199901050511.VAA00479@dingo.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: > > > > Following the helpful discussions recently, I converted my > > recent 3.0 kernel which I thought was elf (but in fact was > > aout) to genuine elf. Installed the boot loader OK as per > > Robert Nordier's helpful instructions and booted the > > kernel. > > > > Now one big problem, the boot disk is in fact the 2nd scsi > > disk (da1) (as well as an IDE disk). It boots OK from what > > in fact is the 3rd disk, but root always defaults back to > > the first scsi (da0) and of course the kernel panics when it > > can't find root. > > > > The perturbation which resulted in a default root change > > with the aout loader/kernel, 2:da(1,a)kernel, is rejected > > by the new loader. > > > > So to avoid a panic with the system and myself (as presently > > I can't run the elf kenel), how does one change the default > > root with the new loader. Even better, how does one save > > this information so it boots automatically and does not > > require manual input. > > Start by breaking to the loader commandline, and say > > set num_ide_disks=1 > boot > > You may need: > > set currdev=disk3s1a: > > if it hasn't already set the current device correctly. > > Please let me know how you go with this; I don't have such a senario to > test with at the moment, but will definitely do whatever is required to > make it work properly. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message I had the same problem with my system, except I have two IDE drives and root is on wd2. Is there a way to configure this for autoboot (no user interaction)? Tom Veldhouse veldy@visi.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 4 21:37:22 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA01654 for freebsd-current-outgoing; Mon, 4 Jan 1999 21:37:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles182.castles.com [208.214.165.182]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA01646 for ; Mon, 4 Jan 1999 21:37:20 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id VAA00618; Mon, 4 Jan 1999 21:33:36 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901050533.VAA00618@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Thomas T. Veldhouse" cc: Mike Smith , rsss@melbpc.org.au, current@FreeBSD.ORG Subject: Re: Panic: Changing default root with the elf loader/kernel In-reply-to: Your message of "Mon, 04 Jan 1999 23:29:35 CST." <3691A33F.B2F8C67B@visi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 04 Jan 1999 21:33:35 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I had the same problem with my system, except I have two IDE drives and > root is on wd2. Is there a way to configure this for autoboot (no user > interaction)? You can put loader commands in /boot/boot.conf -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 22:21:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA05763 for freebsd-current-outgoing; Mon, 4 Jan 1999 22:21:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa16-53.ix.netcom.com [207.93.148.181]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA05758 for ; Mon, 4 Jan 1999 22:20:58 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.1/8.8.8) id WAA04878; Mon, 4 Jan 1999 22:20:29 -0800 (PST) (envelope-from tomdean) Date: Mon, 4 Jan 1999 22:20:29 -0800 (PST) Message-Id: <199901050620.WAA04878@ix.netcom.com> From: Thomas Dean To: current@FreeBSD.ORG Subject: elf make world Success Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am running a complete elf system, SMP -current as of today. I just completed the aout-to-elf conversion, including boot blocks and kernel, yesterday. Today, I cleaned-up the installed ports, eliminating about half and rebuilding as elf, the remainder. 'make -j4 world' just completed, cleanly, as did rebuilding the kernel and rebooting. Next step is to drop all the aout stuff and recapture about 100MB disk space. One aside, When I first installed FreeBSD, I think version 0.1, I had a 10MB disk that was 50% full. Now, I have a 3GB disk that is 90% full! tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 23:27:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA10980 for freebsd-current-outgoing; Mon, 4 Jan 1999 23:27:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fw.bby.com.au (ns.bby.com.au [192.83.119.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA10973 for ; Mon, 4 Jan 1999 23:27:03 -0800 (PST) (envelope-from gnb@itga.com.au) Received: (from daemon@localhost) by fw.bby.com.au (8.8.8/8.6.9) id SAA11326 for ; Tue, 5 Jan 1999 18:26:35 +1100 (EST) Received: from melba.bby.com.au(192.43.186.1) via SMTP by fw.bby.com.au, id smtpd011324; Tue Jan 5 07:26:32 1999 Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by melba.bby.com.au (8.8.2/8.8.2) with ESMTP id SAA11547 for ; Tue, 5 Jan 1999 18:27:07 +1100 (EST) Received: from lightning (lightning [192.168.71.20]) by lightning.itga.com.au (8.9.1a/8.9.1) with ESMTP id SAA08427; Tue, 5 Jan 1999 18:26:29 +1100 (EST) Message-Id: <199901050726.SAA08427@lightning.itga.com.au> From: Gregory Bond To: current@FreeBSD.ORG Subject: Note: wcd has gone away! Date: Tue, 05 Jan 1999 18:26:29 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Some time in the last week, the wcd driver (ATAPI CD-ROM) has gone away and been replaced by acd. config will happily process a "device wcd0" line, the kernel will compile and build, but will fail to probe the CD, leaving you with unexpected "device not configured" errors when you try and use it! If dmesg includes "ATAPI CD-ROMs not configured" then you need to update your kernel config to change wcd0 to acd0. Greg. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 4 23:47:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA12350 for freebsd-current-outgoing; Mon, 4 Jan 1999 23:47:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fw.bby.com.au (ns.bby.com.au [192.83.119.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA12345 for ; Mon, 4 Jan 1999 23:47:38 -0800 (PST) (envelope-from gnb@itga.com.au) Received: (from daemon@localhost) by fw.bby.com.au (8.8.8/8.6.9) id SAA11412; Tue, 5 Jan 1999 18:46:46 +1100 (EST) Received: from melba.bby.com.au(192.43.186.1) via SMTP by fw.bby.com.au, id smtpd011410; Tue Jan 5 07:46:43 1999 Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by melba.bby.com.au (8.8.2/8.8.2) with ESMTP id SAA11792; Tue, 5 Jan 1999 18:47:18 +1100 (EST) Received: from lightning (lightning [192.168.71.20]) by lightning.itga.com.au (8.9.1a/8.9.1) with ESMTP id SAA08498; Tue, 5 Jan 1999 18:46:40 +1100 (EST) Message-Id: <199901050746.SAA08498@lightning.itga.com.au> From: Gregory Bond To: Matthew Dillon Cc: Mike Smith , current@FreeBSD.ORG, gnb@itga.com.au Subject: Re: SOFTUPDATES hangs keyboard In-reply-to: Your message of Sun, 03 Jan 1999 23:40:46 -0800. Date: Tue, 05 Jan 1999 18:46:40 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, it's happened again. I was doing a make on a partition with softupdates and swapping vtys. Traceback: _Debugger(msg=f01fa58f) at _Debugger+0x37 [../../i386/i386/db_interface.c:66] _scgetc(flags=2) at _scgetc+0xd9f [syscons.c:3738] _scintr(unit=0) at _scintr+0x17 [syscons.c:861] Xresume1() at Xresume1+0x2b --- interrupt, eip=0xf020221d, esp=0xf4802e50, ebp=0xf4801e6c --- _wdwait(du=f1039e00,bits_wanted=0,timeout=2710) at _wdwait+0x55 [wc.c:179] _wdintr(unit=0) at _wdint+0x10c [wd.c:1111] _add_interrupt_randomness(vsc=f0251100) at _add_interrupt_randomness+0xe [random_machdep.c:233] Xresume14() at XResume14+0x2b -- interrup[t, eip=0xxf01d08ea, esp=0xf4801efc, ebp=0xf4801f68 --- vec14(f4801f88) at vec14+0x2 _sched_sync(0 at _sched_sync+0xa4 [vfs_subr.c:499] _kproc_start(udata=f022b3ac) at _kproc_start+0x32 [init_main.c:311] _fork_trampoline(52701589,c766f025,25527205,800008f0,25527425) at -fork_trampoline+0x30 PS list: (it's quite long and I can't cut-n-pase from here so I'll summarise) pid proc flag wmsg wchan cmd 1203 f47f3d00 0016 cc 1202 f47f3bc0 4006 cpp 1201 f47f3f80 4006 ppwait f47f3f80 cc 1192 f47f40c0 4086 wait f47f40c0 make 762 f47f4200 4086 wait f47f4200 sh [..] 154 f47f4fc0 0084 nanslp f023d5a8 cron 35 f47f5600 0284 mfsidl f47ee340 mount_mfs 4 f47f5b00 0204 syncer 3 f47f5c40 0204 psleep f024fb38 vmdaemon 2 f47f5d80 0604 pagedaemon 1 f47f5ec0 4048 wait f47f5ec0 init 0 f0259248 0204 shed f0259248 swapper apart from that, all are sleeping on the obvious things: select, ttyin, wait, pause, etc. Hope this helps, Greg. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 00:06:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA14349 for freebsd-current-outgoing; Tue, 5 Jan 1999 00:06:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA14344 for ; Tue, 5 Jan 1999 00:06:01 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id AAA92306; Tue, 5 Jan 1999 00:05:20 -0800 (PST) (envelope-from dillon) Date: Tue, 5 Jan 1999 00:05:20 -0800 (PST) From: Matthew Dillon Message-Id: <199901050805.AAA92306@apollo.backplane.com> To: Gregory Bond Cc: Mike Smith , current@FreeBSD.ORG, gnb@itga.com.au Subject: Re: SOFTUPDATES hangs keyboard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :OK, it's happened again. I was doing a make on a partition with softupdates :and swapping vtys. : :Traceback: : :_wdwait(du=f1039e00,bits_wanted=0,timeout=2710) at _wdwait+0x55 [wc.c:179] :_wdintr(unit=0) at _wdint+0x10c [wd.c:1111] :_add_interrupt_randomness(vsc=f0251100) at _add_interrupt_randomness+0xe [random_machdep.c:233] :Xresume14() at XResume14+0x2b EEek. :PS list: :(it's quite long and I can't cut-n-pase from here so I'll summarise) : :pid proc flag wmsg wchan cmd :1203 f47f3d00 0016 cc :1202 f47f3bc0 4006 cpp :... : :35 f47f5600 0284 mfsidl f47ee340 mount_mfs :... :4 f47f5b00 0204 syncer :3 f47f5c40 0204 psleep f024fb38 vmdaemon :2 f47f5d80 0604 pagedaemon :1 f47f5ec0 4048 wait f47f5ec0 init :0 f0259248 0204 shed f0259248 swapper : :apart from that, all are sleeping on the obvious things: select, ttyin, :wait, pause, etc. You have an MFS partition? Maybe you'd better describe the full machine configuration. Memory, disks, swap configuration, and so forth. It looks to me like it's running out of memory, but it is very odd to see the pagedaemon and syncer both in a run state. I don't think it is softupdates per say, but softupdates could be exasperating some other problem. Just for the hell of it, try reducing debug.max_softdeps with a sysctl to something relatively small, like 100 or 200. -Matt :Hope this helps, : :Greg. : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-current" in the body of the message : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 01:46:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA22555 for freebsd-current-outgoing; Tue, 5 Jan 1999 01:46:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA22549 for ; Tue, 5 Jan 1999 01:46:30 -0800 (PST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id KAA09337 for ; Tue, 5 Jan 1999 10:46:03 +0100 (MET) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma009335; Tue, 5 Jan 99 10:46:03 +0100 Received: from dibbs1.eur.cis.philips.com (dibbs1.eur.cis.philips.com [130.139.33.66]) by smtprelay-nl1.philips.com (8.8.5/8.6.10-1.2.2m-970826) with ESMTP id KAA18571 for ; Tue, 5 Jan 1999 10:46:02 +0100 (MET) Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by dibbs1.eur.cis.philips.com (8.8.8/8.8.8) with SMTP id KAA28355 for ; Tue, 5 Jan 1999 10:46:02 +0100 (MET) Received: (qmail 730 invoked by uid 666); 5 Jan 1999 09:46:23 -0000 Date: Tue, 5 Jan 1999 10:46:23 +0100 From: Jos Backus To: Jaye Mathisen Cc: dannyman , Ryan Duda , freebsd-current@FreeBSD.ORG, port@FreeBSD.ORG Subject: Re: qmail not-installable -- wasRe: (pw) command hanging in -C. Message-ID: <19990105104623.B99381@hal.mpn.cp.philips.com> Reply-To: Jos Backus References: <19990104143433.B16326@enteract.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: ; from Jaye Mathisen on Mon, Jan 04, 1999 at 01:05:12PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 04, 1999 at 01:05:12PM -0800, Jaye Mathisen wrote: > For me, pwd_mkdb -C is hanging, hence pw never returns. If you kill the > pwd_mkdb, then the line is added to the master.passwd file, and running > pwd_mkdb manually will get it intot he proper .db files. See PR bin/9247, I have just submitted a fix (not a pretty one but a fix nonetheless). Cheers, -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 02:00:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA24536 for freebsd-current-outgoing; Tue, 5 Jan 1999 02:00:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA24526 for ; Tue, 5 Jan 1999 02:00:48 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40326>; Tue, 5 Jan 1999 20:59:31 +1100 Date: Tue, 5 Jan 1999 21:00:12 +1100 From: Peter Jeremy Subject: Re: Y2K, Y 2038? To: current@FreeBSD.ORG Message-Id: <99Jan5.205931est.40326@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jonathan Smith wrote: > Deal with it _now_ before the Y2038 Emergency is upon us and >the world is freaking out over it. Perhaps an introduction of a 64 bit >time, A much simpler change is to make time_t an unsigned long - that gives us another 68 years grace - by which time I doubt many of us will be overly concerned :-). There was a very similar discussion some months ago regarding the timestamp field in the inode (on -hackers from memory). I don't think the discussion went anywhere fruitful. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 02:17:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA26092 for freebsd-current-outgoing; Tue, 5 Jan 1999 02:17:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA26086 for ; Tue, 5 Jan 1999 02:17:32 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id KAA11189; Tue, 5 Jan 1999 10:17:01 GMT Date: Tue, 5 Jan 1999 10:17:01 +0000 (GMT) From: Doug Rabson To: Richard Seaman cc: Brian Feldman , Wiliam Woods , "Kevin G. Eliuk" , current@FreeBSD.ORG Subject: Re: Trouble with Staroffice5.0 In-Reply-To: <19990102111905.I2862@tar.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, 2 Jan 1999, Richard Seaman wrote: > On Sat, Jan 02, 1999 at 11:18:26AM +0000, Doug Rabson wrote: > > > > I finally got it up and running too, but I had to do a lot voodoo :] It > > > won't work, as it errs in the middle of its BASIC registration script. Does > > > anyone have a registration code they can share, or some other way to get one? > > > > I had that. From the newsgroups, this is a common failure. Try running > > setup again and telling it to repair your installation. Failing that, try > > uninstalling and reinstalling. Worked for me, YMMV. > > When I had problems with registration, I unistalled, reinstalled, and then > set the default PATH to include the Office50/bin directory. I had assumed > that the reason it worked the second time was that I managed to set the > PATH variable. But, maybe the deinstall/reinstall did something too. > > I'm also interested in a message you posted a few days ago, that SO50 runs > on an SMP machine without threads. I guess I (and others) had assumed the > reason SO50 hadn't worked before was because it needed a functioning > linux_clone and the rest of the linux threads emulation to work. Perhaps > this wasn't true. In working on the linux threads emulation, and also > on SO50, a bug in linux_pipe was discovered and fixed. Perhaps this was > all that kept SO50 from running? Maybe it just needs the fixed linux_pipe > and thats all? > > I haven't tried SO50 without the linux threads patches, but it might > be interesting for someone to try it with the linux_pipe patches > (included by default in -current sources after about Dec 10) but without > any of the other linux threads patches enabled (ie. compiled without > COMPAT_LINUX_THREADS). Presumably you would still need the proc > cmdline patches. Sorry for the delay in replying - I've been recovering from the 'flu. I haven't yet tested the SO50 install on an SMP machine (I was using a UP kernel when originally installing and using SO). The kernel is compiled with the COMPAT_LINUX_THREADS option but I doubt if it makes a difference. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 02:24:53 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA26980 for freebsd-current-outgoing; Tue, 5 Jan 1999 02:24:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA26972 for ; Tue, 5 Jan 1999 02:24:50 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id KAA11317; Tue, 5 Jan 1999 10:24:33 GMT Date: Tue, 5 Jan 1999 10:24:33 +0000 (GMT) From: Doug Rabson To: Garrett Wollman cc: Warner Losh , Bill Paul , current@FreeBSD.ORG Subject: Re: bus_space_foo and bus_dmamap_foo In-Reply-To: <199812312058.PAA07052@khavrinen.lcs.mit.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 Thu, 31 Dec 1998, Garrett Wollman wrote: > < said: > > > It was my understanding from talking to Justin that these areas were > > basically orthoginal. busspace and busdma are used to talk to the > > hardware, while DFR's new bus stuff is more a configuration thing > > rather than talking to the actual hardware. > > How you talk to the hardware depends on where it is in the > configuration graph. > > > How do you view this integration? I'm confused... What needs to be > > integrated? > > When you activate a memory or I/O resource, the appropriate magic > should happen such that included in the stuff you get back is > something which can be used to access that resource quickly. Stuff > like bus_space_alloc should be handled by the bus driver in > coordination with the resource manager. (It should be implemented as > a method call on the device's parent, so that it has all the necessary > context pre-computed.) I think that this is the right approach. The interface for PCI busses should have methods to manage the various device resources and these will be able to provide bus_space handles as necessary. The resources should not need to be mapped directly by the pci driver. I'm currently prototyping the new PCI interface (or I will be as soon as I can get that wretched sysinstall program working properly on the alpha) and I'll add something like this. Are there any manpages for bus_space and bus_dma in NetBSD which we can take? -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 02:37:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA27682 for freebsd-current-outgoing; Tue, 5 Jan 1999 02:37:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA27677 for ; Tue, 5 Jan 1999 02:37:30 -0800 (PST) (envelope-from matt@camtech.com.au) Received: from dialup-ad-15-61.camtech.net.au (dialup-ad-15-61.camtech.net.au [203.55.243.61]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id VAA23797; Tue, 5 Jan 1999 21:05:58 +1030 (CST) Date: Tue, 5 Jan 1999 21:05:20 +1030 (CST) From: Matthew Thyer X-Sender: matt@localhost To: "David W. Chapman Jr." cc: freebsd-current Subject: Re: sendmail throughput (was: HEADS UP: Postfix is coming. new uid,gid required.) In-Reply-To: <369077A1.3E637E35@houabg.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 It sounds like you want to setup the same thing that I have. I am a dialup user who wishes to read mail by several different methods: - Pine on a dumb terminal (on the dinner table!). - Netscape 4.08 on the X server (in the computer room). - Remotely from other sites. What I have done is: - Get mail with the 'popclient' port - pipe the above to procmail which creates my folder structure - serve up the folders with an IMAP server (the 'imap-uw-4.4' port) - Read the mail with Pine, Netscape 4.08, whatever This is quite quick as IMAP only sends the subject lines when you open a folder..... much like news. I find this works very well except Netscape Communicator 4.08 is the only Netscape that seems to work with 'imap-uw'. Netscape 4.5 never connects and neither did 4.07. Further immplementation details below. 1) My 'DownloadMail' script: /usr/local/bin/popclient -c -u thyerm pop.camtech.com.au | /usr/local/bin/formail -s /usr/local/bin/procmail 2) The FreeBSD bits of my .procmailrc: PATH=/bin:/usr/bin:/usr/local/bin MAILDIR=$HOME/imapmail DEFAULT=Inbox :0 * ^Subject: .*ja_JP.* Trash :0 * ^Subject: .*cvs commit: (doc/ja|www/ja|src/sys/pc98|ports/japanese|ports/korean|ports/chinese|ports/vietnamese|ports/german|ports/russian).* Trash :0 * ^Subject: .*- Imported sources.* "FreeBSD/Imported sources" :0 * ^Subject: .*cvs commit: CVSROOT.* FreeBSD/cvs-all/CVSROOT :0 * ^Subject: .*cvs commit: ports.* FreeBSD/cvs-ports :0 * ^Subject: .*cvs commit: www.* FreeBSD/cvs-all/www :0 * ^Subject: .*cvs commit: src/release/picobsd.* FreeBSD/cvs-all/picoBSD :0 * ^Subject: .*cvs commit:.* FreeBSD/cvs-all/cvs-all :0 * ^(To|Cc): .*(current@FreeBSD\.org|current@freefall\.cdrom\.com|committers@FreeBSD\.org).* FreeBSD/CURRENT :0 * ^From: .*FreeBSD Security Officer.* "FreeBSD/FreeBSD Security" :0 * ^Subject: .*FreeBSD Security Advisory.* "FreeBSD/FreeBSD Security" On Mon, 4 Jan 1999, David W. Chapman Jr. wrote: > I see where your comming from, but as I believe Mr Tubutis put it, the ideal > setup would to have the mail list "link" the the news server. Therefore those > who still would like the email, can keep it, those who like the news group > could also use that. I guess filtering spam or junk mail isn't my primary > reason for wanting to switch, I think I can keep my mouth shut when another one > comes along. I like the newsgroup because when I go to check my email, I don't > have to wait a couple of minutes for them all to download. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > /=====================================================================\ |Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au| \=====================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 02:49:34 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA28584 for freebsd-current-outgoing; Tue, 5 Jan 1999 02:49:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from emu.melbpc.org.au (emu.melbpc.org.au [203.12.152.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA28556 for ; Tue, 5 Jan 1999 02:49:22 -0800 (PST) (envelope-from rsss@melbpc.org.au) Received: from bilby227.melbpc.org.au (bilby227.melbpc.org.au [203.12.153.227]) by emu.melbpc.org.au (8.9.0/8.9.0) with SMTP id VAA09621; Tue, 5 Jan 1999 21:48:43 +1100 (EST) From: rsss@melbpc.org.au (Richard Solly) To: current@FreeBSD.ORG Cc: Mike Smith , "Thomas T. Veldhouse" Subject: Re: Panic: Changing default root with the elf loader/kernel Date: Tue, 05 Jan 1999 10:50:24 GMT Reply-To: rsss@melbpc.org.au Message-ID: <3691e66c.3513752@smtp.melbpc.org.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From: Mike Smith >Richard Solly wrote >> Following the helpful discussions recently, I converted my >> recent 3.0 kernel which I thought was elf (but in fact was >> aout) to genuine elf. Installed the boot loader OK as per >> Robert Nordier's helpful instructions and booted the >> kernel. >> Now one big problem, the boot disk is in fact the 2nd scsi >> disk (da1) (as well as an IDE disk). It boots OK from what >> in fact is the 3rd disk, but root always defaults back to >> the first scsi (da0) and of course the kernel panics when it >> can't find root. >You may need: > set currdev=disk3s1a: >if it hasn't already set the current device correctly. In fact it already had currdev=disk3s3a and the loader gives a "disk3s3a" prompt. (Slices 1 and 2 contain another operating system). >Start by breaking to the loader commandline, and say > set num_ide_disks=1 > boot This was done and the elf kernal (GENERIC compile) booted from da1s3a like a charm. >You can put loader commands in /boot/boot.conf I created /boot/boot.conf and added: set num_ide_disks=1 which is read by the loader and now the whole system boots without human intervention. (Well it would if the boot selector on the IDE disk had the FreeBSD system as default). >Please let me know how you go with this; I don't have such a senario to >test with at the moment, but will definitely do whatever is required to >make it work properly. \\ Sometimes you're ahead, \\ Mike Smith Thanks to you for your helpful comments which worked "out of the message". General instructions to change the default root device for the elf loader/kernel would be helpful. What is the required set statement if one boots from the second scsi disk without an IDE disk or the second of two IDE disks ? Richard Solly To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 04:40:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA10865 for freebsd-current-outgoing; Tue, 5 Jan 1999 04:40:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from stade.demon.co.uk (stade.demon.co.uk [158.152.29.164]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA10682 for ; Tue, 5 Jan 1999 04:40:43 -0800 (PST) (envelope-from aw1@stade.co.uk) Received: (from aw1@localhost) by stade.demon.co.uk (8.9.1/8.9.1) id MAA87248 for freebsd-current@FreeBSD.ORG; Tue, 5 Jan 1999 12:08:08 GMT (envelope-from aw1) Date: Tue, 5 Jan 1999 12:08:08 +0000 From: Adrian Wontroba To: freebsd-current Subject: high volume lists (was Re: sendmail throughput (was: HEADS UP: Postfix is coming. new uid,gid required.)) Message-ID: <19990105120807.B84950@titus.stade.co.uk> Reply-To: aw1@stade.co.uk References: <36905506.1B4F3BDC@houabg.com> <36905BDC.EF293117@tci.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <36905BDC.EF293117@tci.com>; from Chris Tubutis on Sun, Jan 03, 1999 at 11:12:44PM -0700 Organization: Stade Computers Ltd, UK X-Phone: +(44) 121 681 6677 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 03, 1999 at 11:12:44PM -0700, Chris Tubutis wrote: > Having stuff pushed to me is nice, but there's a limit as to how much > niceness I can take.... :) procmail and mutt considerably increased the limit for me (8-) -- Adrian Wontroba, Stade Computers Limited. phone: (+44) 121 681 6677 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 04:42:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA10970 for freebsd-current-outgoing; Tue, 5 Jan 1999 04:42:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA10956 for ; Tue, 5 Jan 1999 04:42:19 -0800 (PST) (envelope-from vallo@myhakas.matti.ee) Received: from myhakas.matti.ee (myhakas [194.126.98.150]) by solaris.matti.ee (8.8.8/8.8.8.s) with ESMTP id OAA12515; Tue, 5 Jan 1999 14:41:43 +0200 (EET) Received: (from vallo@localhost) by myhakas.matti.ee (8.9.1/8.9.1) id OAA23359; Tue, 5 Jan 1999 14:41:39 +0200 (EET) (envelope-from vallo) Message-ID: <19990105144139.A23264@matti.ee> Date: Tue, 5 Jan 1999 14:41:39 +0200 From: Vallo Kallaste To: Christian Kuhtz Cc: current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. Reply-To: vallo@matti.ee References: <199812311807.KAA27750@hub.freebsd.org> <199812311832.KAA01002@hub.freebsd.org> <19981231135547.W4306@ns1.adsu.bellsouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19981231135547.W4306@ns1.adsu.bellsouth.com>; from Christian Kuhtz on Thu, Dec 31, 1998 at 01:55:47PM -0500 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 31, 1998 at 01:55:47PM -0500, Christian Kuhtz wrote: > beta into a release is not a part of careful code base maintenance, IMHO. > If memory serves, Postfix would indeed be the only thing in /usr/src/contrib > which is beta. Isn't softupdates under /usr/src/contrib/sys/softupdates still beta ? Am I misunderstanding something ? Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 05:31:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA15155 for freebsd-current-outgoing; Tue, 5 Jan 1999 05:31:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.oeno.com (ns.oeno.com [194.100.99.145]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA15147 for ; Tue, 5 Jan 1999 05:31:54 -0800 (PST) (envelope-from will@ns.oeno.com) Received: (qmail 16856 invoked by uid 1001); 5 Jan 1999 13:31:25 -0000 To: Greg Lehey Cc: current@FreeBSD.ORG Subject: Re: GPL (was: HEADS UP: Postfix is coming. new uid, gid required.) References: <199901010217.SAA20264@hub.freebsd.org> <19990101125656.C41841@freebie.lemis.com.newsgate.clinet.fi> From: Ville-Pertti Keinonen Date: 05 Jan 1999 15:30:51 +0200 In-Reply-To: Greg Lehey's message of "1 Jan 1999 04:49:38 +0200" Message-ID: <8690fhc0dw.fsf@not.oeno.com> Lines: 47 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey writes: > area. The way I see it, the decision is whether the GPL'd part of the > software is indivisible from the rest. Otherwise you take FreeBSD, If the GPL'd parts of the FreeBSD base system would be considered indivisible from FreeBSD, FreeBSD would have to be entirely GPL'd (not just distributed for free). Which is not possible, because parts of FreeBSD have conflicting license terms (source code under a BSD license cannot be part of a GPL'd product by adding the restrictions of the GPL, unless it's a variant of the BSD license with the advertising clause omitted). So clearly the *BSD projects have decided beforehand that such a broad interpretation is not valid, otherwise they wouldn't be able to act legally. Still, I think the current policy (preference of less restrictive free software licenses over the GPL) is good. > including exim, make modifications and sell the result, explicitly > excluding exim from the part of the software which has been bought > (``also includes--*free*--exim and all those GNU packages you know and > love''). It's not selling that the GPL prohibits, but withholding source code and placing additional restrictions on distribution. As long as the package you sell includes the source code to any GPL'd software included or you offer to provide source code on request, you're fine. Distributing the sources along with the binaries is naturally the easiest, the three year obligation to provide the source code to anyone who wants it is annoying. (It can even be reason enough not to use the GPL voluntarily, I certainly don't want to make promises that I might not be able to keep. I also do not want to place additional restrictions on my freedom to e.g. decide to never touch a computer again in my life -- not that I would be free to do that in the near future, anyhow, but in principle.) > Last September, Stallman was bitching about people like Caldera who > sell their product and put GNU utilities on the same CD-ROM. But I Which should have absolutely nothing to do with the GPL, unless there are other factors involved. This is explicitly stated in the GPL. RMS's critique is often moral rather than legal. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 05:51:57 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA16787 for freebsd-current-outgoing; Tue, 5 Jan 1999 05:51:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from as5200-01-254.no.neosoft.com (as5200-01-254.no.neosoft.com [206.27.167.254]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA16777 for ; Tue, 5 Jan 1999 05:51:52 -0800 (PST) (envelope-from conrads@as5200-01-254.no.neosoft.com) Received: (from conrads@localhost) by as5200-01-254.no.neosoft.com (8.9.1/8.8.7) id HAA00588; Tue, 5 Jan 1999 07:50:34 -0600 (CST) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 05 Jan 1999 07:50:33 -0600 (CST) Reply-To: conrads@neosoft.com From: Conrad Sabatier To: Conrad Sabatier Subject: Re: user-ppp broken since a few days ago? Cc: freebsd-current@FreeBSD.ORG, Leif Neland Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Jan-99 Conrad Sabatier wrote: > I'm seeing the same problem with a recently-built kernel (cvsup 1/3/99). > Have to revert back to my old kernel for now just to get connected. It > seems the authenticate phase is never being reached for some reason. > > Weird. Well, I'm pleased to report that after cvsup'ing again yesterday evening (1/4/99) and rebuilding the world and kernel, ppp is back to working again. Whew! :-) -- Conrad Sabatier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 06:17:59 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA18973 for freebsd-current-outgoing; Tue, 5 Jan 1999 06:17:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA18967 for ; Tue, 5 Jan 1999 06:17:56 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id PAA15842; Tue, 5 Jan 1999 15:17:27 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id PAA14950; Tue, 5 Jan 1999 15:17:23 +0100 (MET) Message-ID: <19990105151722.B14101@follo.net> Date: Tue, 5 Jan 1999 15:17:22 +0100 From: Eivind Eklund To: Steve Khoo , freebsd-current@FreeBSD.ORG Subject: Re: DPT SmartRAID V family of RAID Controllers supported? References: <36915E05.ADF9C54E@gordian.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <36915E05.ADF9C54E@gordian.com>; from Steve Khoo on Mon, Jan 04, 1999 at 04:34:13PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 04, 1999 at 04:34:13PM -0800, Steve Khoo wrote: > I know the older SmartRAID IV family is supported, but I was wondering if the > new cards are also supported, especially the Fibre Channel controllers. > > Also, is DLM(Distributed Lock Manager) available on current yet? No. This is blocked by Yours Truly not being able to make heads or tail of somebody's comments WRT spl problems with the implementation, and said somebody never coming up with the finished fixes he promised. > How about a FreeBSD native dptmgr; I'd prefer not to boot to DOS to > run it. The only likely alternative is to run the SCO version under emulation. This is farther from being possible after the CAM integration, as the hooks for this was removed. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 06:25:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA19820 for freebsd-current-outgoing; Tue, 5 Jan 1999 06:25:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mortar.carlson.com (mortar.carlson.com [208.240.12.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA19815 for ; Tue, 5 Jan 1999 06:25:47 -0800 (PST) (envelope-from veldy@visi.com) Received: from mortar.carlson.com (root@localhost) by mortar.carlson.com with ESMTP id IAA01562 for ; Tue, 5 Jan 1999 08:24:40 -0600 (CST) Received: from w142844 ([172.25.99.35]) by mortar.carlson.com with SMTP id IAA01558 for ; Tue, 5 Jan 1999 08:24:39 -0600 (CST) Message-ID: <001201be38b7$38917520$236319ac@w142844.carlson.com> From: "Thomas T. Veldhouse" To: "FreeBSD-Current" Subject: Bootblock and Disklabel problem!!! READ THIS!!! Date: Tue, 5 Jan 1999 08:25:18 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I did a CVSUP on 12/29/98 and rebuilt world. Everything works great. Yesterday, I followed some instructions to put the new bootblocks and an ELF kernel on my system and things went bad. I have two IDE drives with Windows98 (8 Gigs) on my first drive and my second drive has two slices, the first is FreeBSD (4 Gigs) and the second is a DOS staging partition (2 Gigs). Here is what I did. I put the following in my /boot/boot.conf(ig) file: set currdev = disk2s1a load /kernel boot I then compiled and installed a new ELF kernel. That worked fine. I then ran disklabel: disklabel -B -b /boot/boot1 -s /boot/boot2 wd2 (according to http://www.freebsd.org/~rnordier/boot.txt) I rebooted. I was not happy to see the boot loader on my primary drive, but it was now there. When I tried to boot FreeBSD, it found the kernel and booted it, but the Kernel tried to mount the root partion on the first drive, which is wrong. Why is that? Worse, I found that I now had a FreeBSD partition and a DOS partition on my first drive also (obviously it had the old Windows98 information in it and not a true filesystem). It appears to me that the partition information from my second disk was copied to my first disk. Worse yet, my Windows 98 system became totally unbootable, even after I reset the partition information (using Linux bootdisks). My system was hosed (except for FreeBSD thank God!!!). Today I will have to rebuild my Windows 98 system again. Was all of this a known problem and fixed in recent days (since 12/29) or have I stumbled on something unique here? Tom Veldhouse veldy@visi.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 06:56:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23086 for freebsd-current-outgoing; Tue, 5 Jan 1999 06:56:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA23079 for ; Tue, 5 Jan 1999 06:56:19 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id JAA16518 for ; Tue, 5 Jan 1999 09:55:50 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA01864; Tue, 5 Jan 1999 09:55:50 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id JAA12833 for freebsd-current@freebsd.org; Tue, 5 Jan 1999 09:55:50 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199901051455.JAA12833@bb01f39.unx.sas.com> Subject: make release (Almost! snag in stage area) To: freebsd-current@FreeBSD.ORG Date: Tue, 5 Jan 1999 09:55:49 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Well, we made it past the boot floppies (though one had an ignored return code).. Anyways... touch release.9 Setting up CDROM distribution area 0 blocks 0 blocks ln: /R/stage/kernels/MFSKERNEL.std: No such file or directory *** Error code 1 Stop. *** Error code 1 It's looking better! Thanks, John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 07:59:39 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA29656 for freebsd-current-outgoing; Tue, 5 Jan 1999 07:59:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from server.amis.net (server.amis.net [195.10.52.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA29649 for ; Tue, 5 Jan 1999 07:59:36 -0800 (PST) (envelope-from blaz@gold.amis.net) Received: (from uucp@localhost) by server.amis.net (8.8.8/8.8.8) with UUCP id QAA08238 for freebsd-current@freebsd.org; Tue, 5 Jan 1999 16:58:57 +0100 (CET) Received: (qmail 3910 invoked by uid 1000); 5 Jan 1999 15:58:22 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 5 Jan 1999 15:58:22 -0000 Date: Tue, 5 Jan 1999 16:58:22 +0100 (CET) From: Blaz Zupan To: freebsd-current@FreeBSD.ORG Subject: Kernel cannot mount root with new bootblocks In-Reply-To: <199901050511.VAA00479@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here is my setup. I have two SCSI disks connected to an Adaptec 2940, the first is a Quantum 540MB (SCSI ID 0), containing Windows 95, the second is a NEC 1.5GB (SCSI ID 1) containing FreeBSD: da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.0MB/s transfers (10.0MHz, offset 8) da0: 516MB (1057616 512 byte sectors: 64H 32S/T 516C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.0MB/s transfers (10.0MHz, offset 15) da1: 1547MB (3170160 512 byte sectors: 255H 63S/T 197C) /home/blaz> df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da1s4a 31775 15447 13786 53% / /dev/da1s4f 1401271 923795 365375 72% /usr /dev/da1s4e 29727 24415 2934 89% /var /dev/da0s4 528208 162112 366096 31% /dos/c procfs 4 4 0 100% /proc Usually I have os-bs installed on the Quantum so that I can select between Win95 and FreeBSD and this works just fine with the new FreeBSD bootloader for quite some time now. Then I decided to dump Win95 and put some other stuff in, so I needed to boot off the FreeBSD disk directly, without using os-bs. I selected SCSI ID 1 as the boot drive in the Adaptec BIOS. After the kernel boots, I get a panic saying "cannot mount root". I cannot seem to find the right "set currdev" command. When I boot the usual way, currdev is set to disk2s4a, which I guess is right (i.e. it works). When I select the FreeBSD disk as the boot disk, it tries to boot from disk1s4a (which I guess is correct, as the FreeBSD disk is now BIOS drive C:), but the kernel fails to mount root. This is -current as of yesterday, with the latest boot code (installed with "disklabel -B da1" and empty /boot/boot.conf). FreeBSD disk was originally installed dangerously dedicated. Suggestions on how to fix this will be much appreciated. Blaz Zupan, blaz@medinet.si, http://home.amis.net/blaz Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 08:08:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00870 for freebsd-current-outgoing; Tue, 5 Jan 1999 08:08:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00863 for ; Tue, 5 Jan 1999 08:08:35 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id LAA49720; Tue, 5 Jan 1999 11:12:16 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Tue, 5 Jan 1999 11:12:16 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Blaz Zupan cc: freebsd-current@FreeBSD.ORG Subject: Re: Kernel cannot mount root with new bootblocks In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 5 Jan 1999, Blaz Zupan wrote: > Here is my setup. I have two SCSI disks connected to an Adaptec 2940, the > first is a Quantum 540MB (SCSI ID 0), containing Windows 95, the second > is a NEC 1.5GB (SCSI ID 1) containing FreeBSD: [snip] > This is -current as of yesterday, with the latest boot code (installed > with "disklabel -B da1" and empty /boot/boot.conf). FreeBSD disk was > originally installed dangerously dedicated. > > Suggestions on how to fix this will be much appreciated. If someone else doesn't have a better solution you can try wiring the scsi devices down, look in LINT for this, a really bad hack is defining the: "kernel on XXX" line. good luck, -Alfred > Blaz Zupan, blaz@medinet.si, http://home.amis.net/blaz > Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 08:12:34 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA01249 for freebsd-current-outgoing; Tue, 5 Jan 1999 08:12:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mortar.carlson.com (mortar.carlson.com [208.240.12.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA01223 for ; Tue, 5 Jan 1999 08:12:28 -0800 (PST) (envelope-from veldy@visi.com) Received: from mortar.carlson.com (root@localhost) by mortar.carlson.com with ESMTP id KAA03361; Tue, 5 Jan 1999 10:11:20 -0600 (CST) Received: from w142844 ([172.25.99.35]) by mortar.carlson.com with SMTP id KAA03357; Tue, 5 Jan 1999 10:11:19 -0600 (CST) Message-ID: <00d001be38c6$200aeea0$236319ac@w142844.carlson.com> From: "Thomas T. Veldhouse" To: "Alfred Perlstein" , "Blaz Zupan" Cc: Subject: Re: Kernel cannot mount root with new bootblocks Date: Tue, 5 Jan 1999 10:11:58 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In light of all the boot problems I have seen, are there still plans to go ELF Kernel tomorrow? I think you will see that people are going to take a wait and see aproach with CURRENT if this happens. Tom Veldhouse veldy@visi.com -----Original Message----- From: Alfred Perlstein To: Blaz Zupan Cc: freebsd-current@FreeBSD.ORG Date: Tuesday, January 05, 1999 10:08 AM Subject: Re: Kernel cannot mount root with new bootblocks > >On Tue, 5 Jan 1999, Blaz Zupan wrote: > >> Here is my setup. I have two SCSI disks connected to an Adaptec 2940, the >> first is a Quantum 540MB (SCSI ID 0), containing Windows 95, the second >> is a NEC 1.5GB (SCSI ID 1) containing FreeBSD: > >[snip] > >> This is -current as of yesterday, with the latest boot code (installed >> with "disklabel -B da1" and empty /boot/boot.conf). FreeBSD disk was >> originally installed dangerously dedicated. >> >> Suggestions on how to fix this will be much appreciated. > >If someone else doesn't have a better solution you can try wiring the scsi >devices down, look in LINT for this, a really bad hack is defining the: >"kernel on XXX" line. > >good luck, >-Alfred > > > >> Blaz Zupan, blaz@medinet.si, http://home.amis.net/blaz >> Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia >> >> >> 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 08:17:34 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA01924 for freebsd-current-outgoing; Tue, 5 Jan 1999 08:17:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cassiopeia.caprica.com ([208.153.245.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA01919 for ; Tue, 5 Jan 1999 08:17:33 -0800 (PST) (envelope-from frank@exit.com) Received: from exit.com (uucp@localhost) by cassiopeia.caprica.com (8.8.8/8.8.8) with UUCP id IAA19282 for current@freebsd.org; Tue, 5 Jan 1999 08:17:19 -0800 (PST) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime.exit.com [206.223.0.5]) by tinker.exit.com (8.8.8/8.8.8) with ESMTP id IAA01274 for ; Tue, 5 Jan 1999 08:16:33 -0800 (PST) (envelope-from frank@tinker.exit.com) Received: (from frank@localhost) by realtime.exit.com (8.9.1/8.9.1) id IAA01125 for current@freebsd.org; Tue, 5 Jan 1999 08:16:33 -0800 (PST) (envelope-from frank) From: Frank Mayhar Message-Id: <199901051616.IAA01125@realtime.exit.com> Subject: Why won't 3.0-current remember my config? To: current@FreeBSD.ORG Date: Tue, 5 Jan 1999 01:08:33 -0800 (PST) Reply-To: frank@exit.com 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 I've RTFM, I've UTSL, and from all I can tell, when I give the 'pnp 1 1 os...' command to userconfig during boot, later, during /etc/rc, dset should pick up that change and record it in /kernel. Well, it ain't happening. I assume I'm doing something wrong, but on the off chance it's busted, I thought I would post here. What gives? I'm trying to configure a soundcard. The userconfig line I give is: pnp 1 1 os enable port0 0x534 port2 0x220 port3 0xe0d irq0 10 drq0 1 drq1 6 That makes the soundcard work fine. Unfortunately, a reboot of the kernel forgets it every time. -- Frank Mayhar frank@exit.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 08:20:22 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA02279 for freebsd-current-outgoing; Tue, 5 Jan 1999 08:20:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA02272 for ; Tue, 5 Jan 1999 08:20:19 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id LAA49735; Tue, 5 Jan 1999 11:24:00 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Tue, 5 Jan 1999 11:24:00 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Frank Mayhar cc: current@FreeBSD.ORG Subject: Re: Why won't 3.0-current remember my config? In-Reply-To: <199901051616.IAA01125@realtime.exit.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 /kernel.config (i think) -perhaps- /boot.config Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current On Tue, 5 Jan 1999, Frank Mayhar wrote: > I've RTFM, I've UTSL, and from all I can tell, when I give the 'pnp 1 1 os...' > command to userconfig during boot, later, during /etc/rc, dset should pick > up that change and record it in /kernel. > > Well, it ain't happening. I assume I'm doing something wrong, but on the > off chance it's busted, I thought I would post here. What gives? > > I'm trying to configure a soundcard. The userconfig line I give is: > > pnp 1 1 os enable port0 0x534 port2 0x220 port3 0xe0d irq0 10 drq0 1 drq1 6 > > That makes the soundcard work fine. Unfortunately, a reboot of the kernel > forgets it every time. > -- > Frank Mayhar frank@exit.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 08:24:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA02512 for freebsd-current-outgoing; Tue, 5 Jan 1999 08:24:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA02507 for ; Tue, 5 Jan 1999 08:24:10 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id LAA49743; Tue, 5 Jan 1999 11:27:52 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Tue, 5 Jan 1999 11:27:52 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: "Thomas T. Veldhouse" cc: Blaz Zupan , freebsd-current@FreeBSD.ORG Subject: Re: Kernel cannot mount root with new bootblocks In-Reply-To: <00d001be38c6$200aeea0$236319ac@w142844.carlson.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, 5 Jan 1999, Thomas T. Veldhouse wrote: > In light of all the boot problems I have seen, are there still plans to go > ELF Kernel tomorrow? I think you will see that people are going to take a > wait and see aproach with CURRENT if this happens. Naw, lets have the commiters walking on eggshells supporting both targets until the next release. I'm sure they're really keen on that. :) I've noticed most all the problems people have been experiancing can be attributed to user error, not programming error, the boot blocks work fine and are extremely configuable. Unfortunatly the only documentation available at this point is this list archive. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 08:32:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA03554 for freebsd-current-outgoing; Tue, 5 Jan 1999 08:32:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles198.castles.com [208.214.165.198]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA03549 for ; Tue, 5 Jan 1999 08:32:45 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id IAA03868; Tue, 5 Jan 1999 08:29:14 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901051629.IAA03868@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Thomas T. Veldhouse" cc: "Alfred Perlstein" , "Blaz Zupan" , freebsd-current@FreeBSD.ORG Subject: Re: Kernel cannot mount root with new bootblocks In-reply-to: Your message of "Tue, 05 Jan 1999 10:11:58 CST." <00d001be38c6$200aeea0$236319ac@w142844.carlson.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 05 Jan 1999 08:29:13 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In light of all the boot problems I have seen, are there still plans to go > ELF Kernel tomorrow? I think you will see that people are going to take a > wait and see aproach with CURRENT if this happens. Most of the problems with booting are finger trouble at the moment; I can't see any reason why we shouldn't go ahead as planned. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 08:39:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA04262 for freebsd-current-outgoing; Tue, 5 Jan 1999 08:39:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Terry.Dorm10.NCTU.edu.tw (Terry.Dorm10.NCTU.edu.tw [140.113.122.99]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA04248 for ; Tue, 5 Jan 1999 08:39:17 -0800 (PST) (envelope-from ijliao@Terry.Dorm10.NCTU.edu.tw) Received: (from ijliao@localhost) by Terry.Dorm10.NCTU.edu.tw (8.9.1/8.9.1) id AAA13444; Wed, 6 Jan 1999 00:37:36 +0800 (CST) Date: Wed, 6 Jan 1999 00:37:36 +0800 From: Ying-Chieh Liao To: Frank Mayhar Cc: current@FreeBSD.ORG Subject: Re: Why won't 3.0-current remember my config? Message-ID: <19990106003736.A13394@terry.dragon2.net> References: <199901051616.IAA01125@realtime.exit.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199901051616.IAA01125@realtime.exit.com>; from "Frank Mayhar" on Tue, Jan 05, 1999 at 01:08:33 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 05, 1999 at 01:08:33 -0800, Frank Mayhar wrote: > That makes the soundcard work fine. Unfortunately, a reboot of the kernel > forgets it every time. i think that you can put this config in /kernel.config and in /boot/boot.conf, add one line : load -t userconfig_script /kernel.config this works fine on my machine -- mailto:ijliao@dragon2.net?subject="send pgp key" to get my pgp public key key finger print : FA 38 7E 91 FA 22 FA F6 63 04 E3 B5 A1 9F 0C CD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 08:50:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA05442 for freebsd-current-outgoing; Tue, 5 Jan 1999 08:50:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from assurance.rstcorp.com (assurance.rstcorp.com [206.29.49.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA05434 for ; Tue, 5 Jan 1999 08:50:47 -0800 (PST) (envelope-from vshah@rstcorp.com) Received: (from uucp@localhost) by assurance.rstcorp.com (8.8.8/8.8.8) id LAA17118; Tue, 5 Jan 1999 11:50:08 -0500 Received: from sandbox.rstcorp.com(206.29.49.63) by assurance.rstcorp.com via smap (V2.0) id xma017110; Tue, 5 Jan 99 11:49:37 -0500 Received: from jabberwock.rstcorp.com (jabberwock [206.29.49.98]) by sandbox.rstcorp.com (8.8.8/8.8.8) with ESMTP id LAA13482; Tue, 5 Jan 1999 11:49:35 -0500 (EST) Received: (from vshah@localhost) by jabberwock.rstcorp.com (8.9.1/8.8.8) id LAA04700; Tue, 5 Jan 1999 11:49:36 -0500 (EST) Date: Tue, 5 Jan 1999 11:49:36 -0500 (EST) Message-Id: <199901051649.LAA04700@jabberwock.rstcorp.com> From: "Viren R. Shah" To: frank@exit.com Cc: current@FreeBSD.ORG Subject: Re:Why won't 3.0-current remember my config? In-Reply-To: <199901051616.IAA01125@realtime.exit.com> References: <199901051616.IAA01125@realtime.exit.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: "Viren R. Shah" X-Face: )~y+U*K:yzjz{q<5lzpI_SVef'U.])9g[C9`1N@]u3,MHY7f*l7C)[_NjM4y4K8$uIUh|\u (K&&HS6,M!61&GMTk'mqmB/Qg]]X}"?TzsFl]"2v!bl8']dma.:^IY^a[lbOI>U:b<~FyK3q-p{HmZ mn~g.`~BE!5{2D:}Yi+\_KkWe?XaHj9$ko1k8iKLYv5*_2c8"G=?Up[}hn+7RNM(bzBZ_wWk6!Pf&B ?3Tcm7M7B~W%K/I0aX3]*=jP?aM]H6HBPT`oLk+0n^_;N\2\%|Rhy;p}34Q.jEsM\qtnxcm;ag%Nq Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Frank" == Frank Mayhar writes: Frank> I've RTFM, I've UTSL, and from all I can tell, when I give the Frank> 'pnp 1 1 os...' command to userconfig during boot, later, Frank> during /etc/rc, dset should pick up that change and record it Frank> in /kernel. I had the same problem, but in my case it is probably attributable to the whacko hardware (pnpscan -v at boottime gives me nothing -- this is an old compaq eisa machine) Frank> I'm trying to configure a soundcard. The userconfig line I give is: >pnp 1 1 os enable port0 0x534 port2 0x220 port3 0xe0d irq0 10 drq0 1 drq1 6 Put your pnp config line above in a file (say /boot/pnp.config ) like: USERCONFIG pnp 1 1 os enable port0 0x534 port2 0x220 port3 0xe0d irq0 10 drq0 1 drq1 6 quit and in /boot/boot.conf put in the line load -t userconfig_script /boot/pnp.config Viren -- Viren R. Shah | "Are those numbers measured values, viren@rstcorp.com | or are you engaging in proctonumerology?" http://www.rstcorp.com/~vshah/ | -- Bill Garrett in raswrj To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 09:02:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06813 for freebsd-current-outgoing; Tue, 5 Jan 1999 09:02:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06803 for ; Tue, 5 Jan 1999 09:02:46 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id JAA21280; Tue, 5 Jan 1999 09:00:11 -0800 Date: Tue, 5 Jan 1999 09:00:10 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Doug Rabson cc: Garrett Wollman , Warner Losh , Bill Paul , current@FreeBSD.ORG Subject: Re: bus_space_foo and bus_dmamap_foo 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 > > > How do you view this integration? I'm confused... What needs to be > > > integrated? > > > > When you activate a memory or I/O resource, the appropriate magic > > should happen such that included in the stuff you get back is > > something which can be used to access that resource quickly. Stuff > > like bus_space_alloc should be handled by the bus driver in > > coordination with the resource manager. (It should be implemented as > > a method call on the device's parent, so that it has all the necessary > > context pre-computed.) > > I think that this is the right approach. The interface for PCI busses > should have methods to manage the various device resources and these will > be able to provide bus_space handles as necessary. The resources should > not need to be mapped directly by the pci driver. I'm currently > prototyping the new PCI interface (or I will be as soon as I can get that > wretched sysinstall program working properly on the alpha) and I'll add > something like this. > Sounds like the Solaris DKI/DDI. Will you be making the bus_space handles hierarchical and bidirectional? That is, you can do bus_space_XXX for a CPU's access to i/o or memory space on a PCI device, but can you also see about a PCI device's view of memory (or another PCI device) such that dma handles are managed similarily? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 09:12:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07783 for freebsd-current-outgoing; Tue, 5 Jan 1999 09:12:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07778 for ; Tue, 5 Jan 1999 09:12:16 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id JAA05684; Tue, 5 Jan 1999 09:11:35 -0800 (PST) To: "John W. DeBoskey" cc: freebsd-current@FreeBSD.ORG Subject: Re: make release (Almost! snag in stage area) In-reply-to: Your message of "Tue, 05 Jan 1999 09:55:49 EST." <199901051455.JAA12833@bb01f39.unx.sas.com> Date: Tue, 05 Jan 1999 09:11:35 -0800 Message-ID: <5680.915556295@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, we made it past the boot floppies (though one had an ignored > return code).. Anyways... Yeah, one I missed. Fixed it this morning. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 09:15:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08455 for freebsd-current-outgoing; Tue, 5 Jan 1999 09:15:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA08447 for ; Tue, 5 Jan 1999 09:15:24 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id JAA05743; Tue, 5 Jan 1999 09:14:19 -0800 (PST) To: "Thomas T. Veldhouse" cc: "Alfred Perlstein" , "Blaz Zupan" , freebsd-current@FreeBSD.ORG Subject: Re: Kernel cannot mount root with new bootblocks In-reply-to: Your message of "Tue, 05 Jan 1999 10:11:58 CST." <00d001be38c6$200aeea0$236319ac@w142844.carlson.com> Date: Tue, 05 Jan 1999 09:14:19 -0800 Message-ID: <5740.915556459@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In light of all the boot problems I have seen, are there still plans to go > ELF Kernel tomorrow? I think you will see that people are going to take a > wait and see aproach with CURRENT if this happens. That's never a bad idea with -current anyway. People have gotten too complacent. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 09:38:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10873 for freebsd-current-outgoing; Tue, 5 Jan 1999 09:38:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from camel14.mindspring.com (camel14.mindspring.com [207.69.200.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA10816 for ; Tue, 5 Jan 1999 09:37:57 -0800 (PST) (envelope-from stevensl@mindspring.net) Received: from freelove.mindspring.net (freelove.mindspring.net [207.69.192.92]) by camel14.mindspring.com (8.8.5/8.8.5) with SMTP id MAA21424 for ; Tue, 5 Jan 1999 12:37:28 -0500 (EST) Date: Tue, 5 Jan 1999 12:37:54 -0500 (EST) From: steven To: current@FreeBSD.ORG Subject: Re: So we're stuck with using timidity now? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just curious.. what the status on the vm/oss "bug"? I see posts here saying its fixed (from early dec98) others saying its still fubar'd. Posts on Usenet are contradictory also. I got OSS's latest version ossfreebsd391i-30x I'm using Current from Dec 27 1998 which has their patch running anything in X with OSS just kills the whole system, Quake, Fxtv, X11Amp, mpg123.. you name it Steven S. 403forbidden.net "My Sister opened a computer store in Hawaii. She sells C shells down by the seashore." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 09:50:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA12305 for freebsd-current-outgoing; Tue, 5 Jan 1999 09:50:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12300 for ; Tue, 5 Jan 1999 09:50:51 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id MAA49877; Tue, 5 Jan 1999 12:54:37 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Tue, 5 Jan 1999 12:54:37 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: steven cc: current@FreeBSD.ORG Subject: Re: So we're stuck with using timidity now? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 5 Jan 1999, steven wrote: > > Just curious.. what the status on the vm/oss "bug"? > > I see posts here saying its fixed (from early dec98) others > saying its still fubar'd. Posts on Usenet are contradictory > also. > > I got OSS's latest version ossfreebsd391i-30x > I'm using Current from Dec 27 1998 which has their patch > > running anything in X with OSS just kills the whole system, > Quake, Fxtv, X11Amp, mpg123.. you name it Not to knock such an inexpensive and interesting product ( i used it on 2.2.x a while back ) but how come my drivers don't panic my system? (i'm using Luigi's) the problem from what i understand is that OSS dynamically requests large regeons of contiguous memory, after X is running memory is most likely quite fragmented and the request hangs wedging the system. way back when (a year ago) it seemed to only try to alloc the a buffer when the module was loaded, however it may have changed, either that or you are trying to load it after memory is way too fragmented. also having contig_malloc() a bit more robust would be a nice feature... there were some fixes to help contig_malloc specifically with OSS. -Alfred > > > Steven S. > 403forbidden.net > > "My Sister opened a computer store in Hawaii. > She sells C shells down by the seashore." > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 09:57:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA12802 for freebsd-current-outgoing; Tue, 5 Jan 1999 09:57:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12794 for ; Tue, 5 Jan 1999 09:57:12 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id MAA15998; Tue, 5 Jan 1999 12:56:33 -0500 (EST) Message-ID: <19990105125633.A15584@netmonger.net> Date: Tue, 5 Jan 1999 12:56:33 -0500 From: Christopher Masto To: freebsd-current@FreeBSD.ORG Subject: Re: Kernel configurator Mail-Followup-To: freebsd-current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Kenneth Wayne Culver on Mon, Jan 04, 1999 at 05:56:48PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 04, 1999 at 05:56:48PM -0500, Kenneth Wayne Culver wrote: > That's what I thought, I just wasn't sure. It was my impression however > that UNIX wasn't supposed to be that simple. It was supposed to be more > stable. besides, unless the people know what they are doing when they look > at the configurator program (similar to some Linux dists) they may be even > more confused, and it's not that hard to make a custom kernel in the first > place. I personally don't think we need a kernel configurator. Well, we could try to think about what could be improved on the current scheme. It can be a bit tricky to deal with changes such as new devices, new names for old devices, the xxintr stuff going away, etc. I don't really have an answer, except that I think it might involve dropping the idea of "copy GENERIC, then edit" and changing to more of a split system such as rc.conf/rc.local is now. I think that once it's sufficiently improved for the "edit a file by hand" case, it will be easier to make an optional fancy front-end. -- Christopher Masto Director of Operations NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net "Good tools allow users to do stupid things." -- Clay Shirky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 10:08:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14349 for freebsd-current-outgoing; Tue, 5 Jan 1999 10:08:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14308 for ; Tue, 5 Jan 1999 10:08:44 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id SAA12610; Tue, 5 Jan 1999 18:08:19 GMT Date: Tue, 5 Jan 1999 18:08:19 +0000 (GMT) From: Doug Rabson To: Matthew Jacob cc: Garrett Wollman , Warner Losh , Bill Paul , current@FreeBSD.ORG Subject: Re: bus_space_foo and bus_dmamap_foo In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 5 Jan 1999, Matthew Jacob wrote: > > > > How do you view this integration? I'm confused... What needs to be > > > > integrated? > > > > > > When you activate a memory or I/O resource, the appropriate magic > > > should happen such that included in the stuff you get back is > > > something which can be used to access that resource quickly. Stuff > > > like bus_space_alloc should be handled by the bus driver in > > > coordination with the resource manager. (It should be implemented as > > > a method call on the device's parent, so that it has all the necessary > > > context pre-computed.) > > > > I think that this is the right approach. The interface for PCI busses > > should have methods to manage the various device resources and these will > > be able to provide bus_space handles as necessary. The resources should > > not need to be mapped directly by the pci driver. I'm currently > > prototyping the new PCI interface (or I will be as soon as I can get that > > wretched sysinstall program working properly on the alpha) and I'll add > > something like this. > > > > Sounds like the Solaris DKI/DDI. Will you be making the bus_space handles > hierarchical and bidirectional? That is, you can do bus_space_XXX for > a CPU's access to i/o or memory space on a PCI device, but can you also > see about a PCI device's view of memory (or another PCI device) such that > dma handles are managed similarily? I'm not sure that this fits with the existing bus_dma apis which we have taken from NetBSD. I wasn't planning to change that api much if at all. It does make sense for the two to be at least similar though. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 10:10:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14736 for freebsd-current-outgoing; Tue, 5 Jan 1999 10:10:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA14722 for ; Tue, 5 Jan 1999 10:10:02 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zxav1-0004KV-00; Tue, 5 Jan 1999 11:09:27 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id LAA13658; Tue, 5 Jan 1999 11:07:24 -0700 (MST) Message-Id: <199901051807.LAA13658@harmony.village.org> To: Doug Rabson Subject: Re: bus_space_foo and bus_dmamap_foo Cc: Garrett Wollman , Bill Paul , current@FreeBSD.ORG In-reply-to: Your message of "Tue, 05 Jan 1999 10:24:33 GMT." References: Date: Tue, 05 Jan 1999 11:07:24 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Doug Rabson writes: : Are there any manpages for bus_space and bus_dma in NetBSD which we can : take? Yes. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 10:12:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15073 for freebsd-current-outgoing; Tue, 5 Jan 1999 10:12:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA15067 for ; Tue, 5 Jan 1999 10:12:29 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id KAA21494; Tue, 5 Jan 1999 10:11:34 -0800 Date: Tue, 5 Jan 1999 10:11:34 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Doug Rabson cc: Garrett Wollman , Warner Losh , Bill Paul , current@FreeBSD.ORG Subject: Re: bus_space_foo and bus_dmamap_foo 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 > > > > Sounds like the Solaris DKI/DDI. Will you be making the bus_space handles > > hierarchical and bidirectional? That is, you can do bus_space_XXX for > > a CPU's access to i/o or memory space on a PCI device, but can you also > > see about a PCI device's view of memory (or another PCI device) such that > > dma handles are managed similarily? > > I'm not sure that this fits with the existing bus_dma apis which we have > taken from NetBSD. I wasn't planning to change that api much if at all. No, it doesn't fit with the existing NetBSD model. > It does make sense for the two to be at least similar though. To quote Eric Allman, "Well, *I* would certainly think so". -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 10:36:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17489 for freebsd-current-outgoing; Tue, 5 Jan 1999 10:36:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17484 for ; Tue, 5 Jan 1999 10:36:04 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id DAA00493; Wed, 6 Jan 1999 03:35:34 +0900 (JST) Message-ID: <36925780.75AB6581@newsguy.com> Date: Wed, 06 Jan 1999 03:18:40 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: current@FreeBSD.ORG, Mike Smith , "Jordan K. Hubbard" , Andrzej Bialecki Subject: /boot/boot.rc && /boot/rc.d Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was thinking about possible on-comings "patches" in boot.rc (currently known as boot.conf :), when I realized that for third-party drivers or ports making use of loader it would better to source files from a boot/rc.d directory. Is this already planned? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com "Heart like a Gabriel, pure and white as ivory, soul like a lucifer, black and cold as a piece of lead." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 10:36:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17647 for freebsd-current-outgoing; Tue, 5 Jan 1999 10:36:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17635 for ; Tue, 5 Jan 1999 10:36:18 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id DAA00501; Wed, 6 Jan 1999 03:35:44 +0900 (JST) Message-ID: <369258F9.92BA60AE@newsguy.com> Date: Wed, 06 Jan 1999 03:24:57 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Alfred Perlstein CC: Frank Mayhar , current@FreeBSD.ORG Subject: Re: Why won't 3.0-current remember my config? References: 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: > > /kernel.config (i think) > -perhaps- > /boot.config > > > I'm trying to configure a soundcard. The userconfig line I give is: > > > > pnp 1 1 os enable port0 0x534 port2 0x220 port3 0xe0d irq0 10 drq0 1 drq1 6 Err... that would be correct. If you place the line in the file /boot/boot.conf (soon to be /boot/boot.rc, I'm told), it will always get executed during boot (unless you forgone running loader), in the new three stage boot loader. I might add it has the added benefit of being easier to change, and being somewhat documental... :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com "Heart like a Gabriel, pure and white as ivory, soul like a lucifer, black and cold as a piece of lead." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 10:36:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17654 for freebsd-current-outgoing; Tue, 5 Jan 1999 10:36:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17636 for ; Tue, 5 Jan 1999 10:36:18 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id DAA00510; Wed, 6 Jan 1999 03:35:48 +0900 (JST) Message-ID: <36925944.EF33F5DB@newsguy.com> Date: Wed, 06 Jan 1999 03:26:12 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Alfred Perlstein , current@FreeBSD.ORG Subject: Re: Kernel cannot mount root with new bootblocks References: 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've noticed most all the problems people have been experiancing can be > attributed to user error, not programming error, the boot blocks work fine > and are extremely configuable. Unfortunatly the only documentation > available at this point is this list archive. That being a far greater problem than anything else I have seen so far... -- Daniel C. Sobral (8-DCS) dcs@newsguy.com "Heart like a Gabriel, pure and white as ivory, soul like a lucifer, black and cold as a piece of lead." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 10:36:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17720 for freebsd-current-outgoing; Tue, 5 Jan 1999 10:36:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17706 for ; Tue, 5 Jan 1999 10:36:28 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id DAA00525; Wed, 6 Jan 1999 03:35:56 +0900 (JST) Message-ID: <36925ABF.9DDEE200@newsguy.com> Date: Wed, 06 Jan 1999 03:32:31 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: Kernel cannot mount root with new bootblocks References: <5740.915556459@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: > > > In light of all the boot problems I have seen, are there still plans to go > > ELF Kernel tomorrow? I think you will see that people are going to take a > > wait and see aproach with CURRENT if this happens. > > That's never a bad idea with -current anyway. People have gotten > too complacent. :) Don't worry. I'm running out of fingers counting the number of massive, dramatic changes that will get in following the branch... :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com "Heart like a Gabriel, pure and white as ivory, soul like a lucifer, black and cold as a piece of lead." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 10:43:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18329 for freebsd-current-outgoing; Tue, 5 Jan 1999 10:43:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18310 for ; Tue, 5 Jan 1999 10:43:26 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id KAA06089; Tue, 5 Jan 1999 10:42:47 -0800 (PST) To: "Daniel C. Sobral" cc: current@FreeBSD.ORG, Mike Smith , Andrzej Bialecki Subject: Re: /boot/boot.rc && /boot/rc.d In-reply-to: Your message of "Wed, 06 Jan 1999 03:18:40 +0900." <36925780.75AB6581@newsguy.com> Date: Tue, 05 Jan 1999 10:42:46 -0800 Message-ID: <6086.915561766@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I was thinking about possible on-comings "patches" in boot.rc > (currently known as boot.conf :), when I realized that for > third-party drivers or ports making use of loader it would better to > source files from a boot/rc.d directory. > > Is this already planned? We hadn't really thought this far ahead, but I see no reason why following such a "hook chain" couldn't be a part of the system. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 10:52:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA19446 for freebsd-current-outgoing; Tue, 5 Jan 1999 10:52:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gongshow.masterplan.org (masterplan.powersurfr.com [24.108.38.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA19441 for ; Tue, 5 Jan 1999 10:52:22 -0800 (PST) (envelope-from jbg@masterplan.org) Received: from infomat (infomat [192.168.4.2]) by gongshow.masterplan.org (8.8.8/8.8.8) with SMTP id LAA01601 for ; Tue, 5 Jan 1999 11:51:52 -0700 (MST) (envelope-from jbg@masterplan.org) Message-Id: <199901051851.LAA01601@gongshow.masterplan.org> From: jbg@masterplan.org (Jason George) To: freebsd-current@FreeBSD.ORG Subject: Re: News Server Organization: The Master Plan Always Fails... Date: Tue, 05 Jan 1999 18:51:55 GMT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been running a mail2news read-only gateway for a few months now. (I'm not gating all the lists, but do have most of them...) It's available at atomic-playboy.masterplan.org (207.167.12.181). There are a couple of holes in the threads, but I took care of the script error this morning, so everything should fill in fine from here on in. Drop me a note if you have any questions or comments. --Jason j.b.georgeieee.org jbgmasterplan.org > >Funny, I was just going to offer to do this... Perhaps we can get this >squared away. It would be more useful for me as well. > >On Mon, 4 Jan 1999, David W. Chapman Jr. wrote: > >> I guess the solution that I'm looking for is to have the mail list post >> to the news server if we do get one. I don't mind posting to >> freebsd-current@freebsd.org. But it would better suit me to read from >> the news server. With news server it I can read messages in retrospect >> of me initially signing on to the mailing list, and wouldn't have to ask >> of say the status of the es1370 sound driver. For the people that like >> to get the new messages in their inbox, they shouldn't notice any >> difference. Anyone interest in a news server please email me so I can >> get an idea of whether it is worth pursuing. Please don't cc the >> mailing list, I don't want to fill up anybody's mailbox who doesn't care >> about this issue. >> >> >> 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 10:59:53 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA20558 for freebsd-current-outgoing; Tue, 5 Jan 1999 10:59:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA20553 for ; Tue, 5 Jan 1999 10:59:52 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id KAA06207; Tue, 5 Jan 1999 10:59:11 -0800 (PST) To: jbg@masterplan.org (Jason George) cc: freebsd-current@FreeBSD.ORG Subject: Re: News Server In-reply-to: Your message of "Tue, 05 Jan 1999 18:51:55 GMT." <199901051851.LAA01601@gongshow.masterplan.org> Date: Tue, 05 Jan 1999 10:59:11 -0800 Message-ID: <6203.915562751@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've been running a mail2news read-only gateway for a few months now. > (I'm not gating all the lists, but do have most of them...) > > It's available at atomic-playboy.masterplan.org (207.167.12.181). Wow, this seems to work fine... How about just pointing news.freebsd.org at this site? :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 11:00:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20726 for freebsd-current-outgoing; Tue, 5 Jan 1999 11:00:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20718 for ; Tue, 5 Jan 1999 11:00:54 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.233]) by smtp02.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA68E7 for ; Tue, 5 Jan 1999 20:00:28 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 05 Jan 1999 20:07:43 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: FreeBSD Current Subject: Some weird problem with ELF kernel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I let my system compile a new world last night and also made a new ELF kernel (last one was from 2 January) and this is what I got on booting: rc.i386 configuring syscons: keyrate blank_time screensaverld: /kernel: malformed input file (not rel or archive) modload: /usr/bin/ld: return code 1 moused. I have literally no clue what this means... Is this the lkm/ld transition ? --- Jeroen Ruigrok van der Werven A veil of smoke is what I am, asmodai(at)wxs.nl I wait and I wait... Network/Security Specialist BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 11:14:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA21989 for freebsd-current-outgoing; Tue, 5 Jan 1999 11:14:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA21983 for ; Tue, 5 Jan 1999 11:14:26 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id UAA20829; Tue, 5 Jan 1999 20:11:47 +0100 (CET) To: "Jordan K. Hubbard" cc: jbg@masterplan.org (Jason George), freebsd-current@FreeBSD.ORG Subject: Re: News Server In-reply-to: Your message of "Tue, 05 Jan 1999 10:59:11 PST." <6203.915562751@zippy.cdrom.com> Date: Tue, 05 Jan 1999 20:11:47 +0100 Message-ID: <20827.915563507@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <6203.915562751@zippy.cdrom.com>, "Jordan K. Hubbard" writes: >> I've been running a mail2news read-only gateway for a few months now. >> (I'm not gating all the lists, but do have most of them...) >> >> It's available at atomic-playboy.masterplan.org (207.167.12.181). > >Wow, this seems to work fine... How about just pointing >news.freebsd.org at this site? :-) Indeed. A service like this would probably mean I got to see more of the stuff that goes on than if it arrives in my mailbox. But why don't we just create a freebsd.* hierachy for selective and elective distribution ? -- 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 Tue Jan 5 11:18:50 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA22533 for freebsd-current-outgoing; Tue, 5 Jan 1999 11:18:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA22527 for ; Tue, 5 Jan 1999 11:18:49 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id LAA06313; Tue, 5 Jan 1999 11:14:20 -0800 (PST) To: Poul-Henning Kamp cc: jbg@masterplan.org (Jason George), freebsd-current@FreeBSD.ORG Subject: Re: News Server In-reply-to: Your message of "Tue, 05 Jan 1999 20:11:47 +0100." <20827.915563507@critter.freebsd.dk> Date: Tue, 05 Jan 1999 11:14:19 -0800 Message-ID: <6309.915563659@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > But why don't we just create a > freebsd.* > hierachy for selective and elective distribution ? Because I believe that requires buy-in by the backbone cabal, and who wants to spend 3 weeks mud-wrestling with Joel Furr? :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 11:23:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA23168 for freebsd-current-outgoing; Tue, 5 Jan 1999 11:23:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA23162 for ; Tue, 5 Jan 1999 11:23:11 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id UAA20875; Tue, 5 Jan 1999 20:20:45 +0100 (CET) To: "Jordan K. Hubbard" cc: jbg@masterplan.org (Jason George), freebsd-current@FreeBSD.ORG Subject: Re: News Server In-reply-to: Your message of "Tue, 05 Jan 1999 11:14:19 PST." <6309.915563659@zippy.cdrom.com> Date: Tue, 05 Jan 1999 20:20:44 +0100 Message-ID: <20873.915564044@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <6309.915563659@zippy.cdrom.com>, "Jordan K. Hubbard" writes: >> But why don't we just create a >> freebsd.* >> hierachy for selective and elective distribution ? > >Because I believe that requires buy-in by the backbone cabal, and >who wants to spend 3 weeks mud-wrestling with Joel Furr? :-) I don't really see the need, people can pick it up someplace and if they don't want it they can say no. I guess alt.freebsd.* could be a more legal alternative ? -- 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 Tue Jan 5 11:26:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA23716 for freebsd-current-outgoing; Tue, 5 Jan 1999 11:26:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA23710 for ; Tue, 5 Jan 1999 11:26:38 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id OAA18839; Tue, 5 Jan 1999 14:23:00 -0500 (EST) (envelope-from wollman) Date: Tue, 5 Jan 1999 14:23:00 -0500 (EST) From: Garrett Wollman Message-Id: <199901051923.OAA18839@khavrinen.lcs.mit.edu> To: Poul-Henning Kamp Cc: "Jordan K. Hubbard" , jbg@masterplan.org (Jason George), freebsd-current@FreeBSD.ORG Subject: Re: News Server In-Reply-To: <20827.915563507@critter.freebsd.dk> References: <6203.915562751@zippy.cdrom.com> <20827.915563507@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > But why don't we just create a > freebsd.* > hierachy for selective and elective distribution ? Because the state of news transport makes this very difficult. -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 Tue Jan 5 11:27:41 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA23876 for freebsd-current-outgoing; Tue, 5 Jan 1999 11:27:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from o-o.org (o-o.org [207.252.201.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA23864 for ; Tue, 5 Jan 1999 11:27:38 -0800 (PST) (envelope-from licia@o-o.org) Received: from localhost (root@localhost) by o-o.org (8.8.8/8.8.7) with SMTP id NAA17281 for ; Tue, 5 Jan 1999 13:27:10 -0600 (CST) Date: Tue, 5 Jan 1999 13:27:10 -0600 (CST) From: Licia To: freebsd-current@FreeBSD.ORG Subject: Re: News Server In-Reply-To: <20873.915564044@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How hard would it be to set up a standalone news server specifically for FreeBSD, not connected to usenet in any way? On Tue, 5 Jan 1999, Poul-Henning Kamp wrote: > In message <6309.915563659@zippy.cdrom.com>, "Jordan K. Hubbard" writes: > >> But why don't we just create a > >> freebsd.* > >> hierachy for selective and elective distribution ? > > > >Because I believe that requires buy-in by the backbone cabal, and > >who wants to spend 3 weeks mud-wrestling with Joel Furr? :-) > > I don't really see the need, people can pick it up someplace > and if they don't want it they can say no. > > I guess alt.freebsd.* could be a more legal alternative ? > > -- > 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 > [ licia@o-o.org ] [ http://www.o-o.org/ ] [ IrcNick : Licia ] [ A happy user of FreeBSD : http://www.freebsd.org/ ] [ Why crawl through windows when you can walk through a door? ] [ This user boycotts all Microsoft products and services ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 11:43:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25718 for freebsd-current-outgoing; Tue, 5 Jan 1999 11:43:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25713 for ; Tue, 5 Jan 1999 11:43:02 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id LAA06448; Tue, 5 Jan 1999 11:42:05 -0800 (PST) To: Licia cc: freebsd-current@FreeBSD.ORG Subject: Re: News Server In-reply-to: Your message of "Tue, 05 Jan 1999 13:27:10 CST." Date: Tue, 05 Jan 1999 11:42:05 -0800 Message-ID: <6445.915565325@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > How hard would it be to set up a standalone news server specifically for > FreeBSD, not connected to usenet in any way? That's sort of what the atomic playboy (great name BTW!) site has done, I believe. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 11:45:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA26271 for freebsd-current-outgoing; Tue, 5 Jan 1999 11:45:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA26262 for ; Tue, 5 Jan 1999 11:45:19 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id LAA06436; Tue, 5 Jan 1999 11:41:31 -0800 (PST) To: Poul-Henning Kamp cc: jbg@masterplan.org (Jason George), freebsd-current@FreeBSD.ORG Subject: Re: News Server In-reply-to: Your message of "Tue, 05 Jan 1999 20:20:44 +0100." <20873.915564044@critter.freebsd.dk> Date: Tue, 05 Jan 1999 11:41:30 -0800 Message-ID: <6432.915565290@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I don't really see the need, people can pick it up someplace > and if they don't want it they can say no. Yeah, but Joel will send out rmgroup messages to all and sundry for anything which doesn't meet his (prior) approval. > I guess alt.freebsd.* could be a more legal alternative ? Yes. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 12:29:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA02606 for freebsd-current-outgoing; Tue, 5 Jan 1999 12:29:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA02593 for ; Tue, 5 Jan 1999 12:29:16 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id MAA24936; Tue, 5 Jan 1999 12:23:03 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdP24931; Tue Jan 5 20:23:01 1999 Date: Tue, 5 Jan 1999 12:22:54 -0800 (PST) From: Julian Elischer To: freebsd-svr4@atdot.dotat.org cc: current@FreeBSD.ORG Subject: Re: [freebsd-svr4] KLD conversion done; state of the world In-Reply-To: <19990105103550.D26523@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 I agree.... this is -current dammit.. get it in.... I'm sure you'll find backers... this should go in asap so people can start using solaris binaries. On Tue, 5 Jan 1999, David O'Brien wrote: > > - I have commit privs, but I'm waiting for the 3.0.1 split before I > > import anything due to the cruft-culling that's going on now, the > > Please bring this up with core (if you haven't already). If you wait to > commit this to 3.1-CURRENT, it will be over a year until the average > FreeBSDer will see SVR4 emulation. > > -- > -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 12:38:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA04158 for freebsd-current-outgoing; Tue, 5 Jan 1999 12:38:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-15-dbn.dial-up.net [196.34.155.79]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA04146 for ; Tue, 5 Jan 1999 12:38:15 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id WAA10760; Tue, 5 Jan 1999 22:19:25 +0200 (SAT) From: Robert Nordier Message-Id: <199901052019.WAA10760@ceia.nordier.com> Subject: Re: Bootblocks / Bootloader In-Reply-To: from Alex Zepeda at "Jan 4, 99 02:31:17 pm" To: garbanzo@hooked.net (Alex Zepeda) Date: Tue, 5 Jan 1999 22:19:24 +0200 (SAT) Cc: mike@smith.net.au, asmodai@wxs.nl, rnordier@nordier.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alex Zepeda wrote: > On Sun, 3 Jan 1999, Mike Smith wrote: > > > That's normal; the "old" help is only displayed in "compatibility" > > mode. Without a /boot.config, the bootblocks try to be as quiet as > > possible. You may notice the spinner stop for a couple of seconds; if > > you hit a key at that point, you'll drop back into "compatibility" mode > > again. > > Oh cool! I was wondering about that for a while, and thought perhaps I > still had the old boot blocks installed. How can I reduce the time that > it stops the spinner, as I've got little or no use for compat. mode? If you want to patch the code: Index: boot2.c =================================================================== RCS file: /home/ncvs/src/sys/boot/i386/boot2/boot2.c,v retrieving revision 1.16 diff -u -r1.16 boot2.c --- boot2.c 1998/11/08 18:37:28 1.16 +++ boot2.c 1999/01/05 20:14:59 @@ -165,7 +165,7 @@ if (autoboot && !*kname) { if (autoboot == 2) { memcpy(kname, PATH_BOOT3, sizeof(PATH_BOOT3)); - if (!keyhit(0x37)) { + if (!keyhit(0x1)) { load(kname); autoboot = 1; } but I'm looking at adding a non-interactive build option which should invoke /boot/loader immediately, (though it would still fall back to compat. mode if /boot/loader doesn't exist). -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 12:53:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA05908 for freebsd-current-outgoing; Tue, 5 Jan 1999 12:53:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA05898 for ; Tue, 5 Jan 1999 12:53:12 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA00796; Tue, 5 Jan 1999 12:49:10 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901052049.MAA00796@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Jeroen Ruigrok/Asmodai cc: FreeBSD Current Subject: Re: Some weird problem with ELF kernel In-reply-to: Your message of "Tue, 05 Jan 1999 20:07:43 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 05 Jan 1999 12:49:10 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I let my system compile a new world last night and also made a new ELF kernel > (last one was from 2 January) > > and this is what I got on booting: > > rc.i386 configuring syscons: keyrate blank_time screensaverld: /kernel: > malformed input file (not rel or archive) > modload: /usr/bin/ld: return code 1 > moused. > > I have literally no clue what this means... Is this the lkm/ld transition ? You need to update your /etc/rc* files. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 12:55:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA06797 for freebsd-current-outgoing; Tue, 5 Jan 1999 12:55:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA06783 for ; Tue, 5 Jan 1999 12:55:17 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.233]) by smtp05.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA606E; Tue, 5 Jan 1999 21:54:41 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199901052049.MAA00796@dingo.cdrom.com> Date: Tue, 05 Jan 1999 22:01:59 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Mike Smith Subject: Re: Some weird problem with ELF kernel Cc: FreeBSD Current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Jan-99 Mike Smith wrote: >> rc.i386 configuring syscons: keyrate blank_time screensaverld: /kernel: >> malformed input file (not rel or archive) >> modload: /usr/bin/ld: return code 1 >> moused. > You need to update your /etc/rc* files. Thanks Mike, I was getting scared I missed another compilation flag/setting... I will diff the src/*/etc with the /etc... --- Jeroen Ruigrok van der Werven A veil of smoke is what I am, asmodai(at)wxs.nl I wait and I wait... Network/Security Specialist BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 12:56:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07038 for freebsd-current-outgoing; Tue, 5 Jan 1999 12:56:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07025 for ; Tue, 5 Jan 1999 12:56:20 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA00642; Tue, 5 Jan 1999 12:29:35 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901052029.MAA00642@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Julian Elischer cc: freebsd-svr4@atdot.dotat.org, current@FreeBSD.ORG Subject: Re: [freebsd-svr4] KLD conversion done; state of the world In-reply-to: Your message of "Tue, 05 Jan 1999 12:22:54 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 05 Jan 1999 12:29:34 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I agree.... > this is -current dammit.. > get it in.... > I'm sure you'll find backers... > this should go in asap so people can start using solaris binaries. > > > On Tue, 5 Jan 1999, David O'Brien wrote: > > > > - I have commit privs, but I'm waiting for the 3.0.1 split before I > > > import anything due to the cruft-culling that's going on now, the > > > > Please bring this up with core (if you haven't already). If you wait to > > commit this to 3.1-CURRENT, it will be over a year until the average > > FreeBSDer will see SVR4 emulation. If it goes into 3.1-current and is found useful and stable, it will be backmigrated to 3.0-stable. I'm not sure it's material for a commit just a few days before the branch. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 13:01:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA07613 for freebsd-current-outgoing; Tue, 5 Jan 1999 13:01:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA07604 for ; Tue, 5 Jan 1999 13:01:33 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id MAA26126; Tue, 5 Jan 1999 12:58:24 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdP26120; Tue Jan 5 20:58:16 1999 Date: Tue, 5 Jan 1999 12:58:06 -0800 (PST) From: Julian Elischer To: Mike Smith cc: freebsd-svr4@atdot.dotat.org, current@FreeBSD.ORG Subject: Re: [freebsd-svr4] KLD conversion done; state of the world In-Reply-To: <199901052029.MAA00642@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's mostly addition code (it's a KLD module). how can it hurt? remember it's not breaking old code.. it's adding new functionality. Consider also that quite a few people have tried it out.. On Tue, 5 Jan 1999, Mike Smith wrote: > > I agree.... > > this is -current dammit.. > > get it in.... > > I'm sure you'll find backers... > > this should go in asap so people can start using solaris binaries. > > > > > > On Tue, 5 Jan 1999, David O'Brien wrote: > > > > > > - I have commit privs, but I'm waiting for the 3.0.1 split before I > > > > import anything due to the cruft-culling that's going on now, the > > > > > > Please bring this up with core (if you haven't already). If you wait to > > > commit this to 3.1-CURRENT, it will be over a year until the average > > > FreeBSDer will see SVR4 emulation. > > If it goes into 3.1-current and is found useful and stable, it will be > backmigrated to 3.0-stable. I'm not sure it's material for a commit > just a few days before the branch. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 13:09:42 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08490 for freebsd-current-outgoing; Tue, 5 Jan 1999 13:09:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA08481 for ; Tue, 5 Jan 1999 13:09:37 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id HAA09344; Wed, 6 Jan 1999 07:38:36 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id HAA81240; Wed, 6 Jan 1999 07:38:42 +1030 (CST) Date: Wed, 6 Jan 1999 07:38:42 +1030 From: Greg Lehey To: Peter Jeremy Cc: current@FreeBSD.ORG Subject: Re: Y2K, Y 2038? Message-ID: <19990106073842.M78349@freebie.lemis.com> References: <99Jan5.205931est.40326@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <99Jan5.205931est.40326@border.alcanet.com.au>; from Peter Jeremy on Tue, Jan 05, 1999 at 09:00:12PM +1100 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 5 January 1999 at 21:00:12 +1100, Peter Jeremy wrote: > Jonathan Smith wrote: >> Deal with it _now_ before the Y2038 Emergency is upon us and >> the world is freaking out over it. Perhaps an introduction of a 64 bit >> time, > > A much simpler change is to make time_t an unsigned long - that gives > us another 68 years grace - by which time I doubt many of us will be > overly concerned :-). > > There was a very similar discussion some months ago regarding the > timestamp field in the inode (on -hackers from memory). I don't > think the discussion went anywhere fruitful. Part of that discussion was concerned with the fact that, correctly or incorrectly, people use negative time_t's. This would break that for a comparatively minor benefit. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 13:15:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09209 for freebsd-current-outgoing; Tue, 5 Jan 1999 13:15:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gordius.gordian.com (gordius.gordian.com [192.73.220.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA09156; Tue, 5 Jan 1999 13:14:58 -0800 (PST) (envelope-from steve@gordian.com) X-bait: aablmeh@gordian.com,mmblmeh@gordian.com,zzblmeh@gordian.com Received: from delphi.gordian.com (delphi.gordian.com [192.73.220.125]) by gordius.gordian.com (8.9.0.Beta3/8.9.0.Beta3) with ESMTP id NAA25409; Tue, 5 Jan 1999 13:14:30 -0800 (PST) Received: from gordian.com (asclepius [192.73.220.254]) by delphi.gordian.com (8.7.2/8.6.9) with ESMTP id NAA00067; Tue, 5 Jan 1999 13:14:29 -0800 (PST) Message-ID: <369280B4.449FFA56@gordian.com> Date: Tue, 05 Jan 1999 13:14:28 -0800 From: Steve Khoo Organization: Gordian; Santa Ana Heights, CA X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 2.2.8-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Eivind Eklund CC: freebsd-current@FreeBSD.ORG Subject: Re: DPT SmartRAID V family of RAID Controllers supported? References: <36915E05.ADF9C54E@gordian.com> <19990105151722.B14101@follo.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eivind Eklund wrote: > > On Mon, Jan 04, 1999 at 04:34:13PM -0800, Steve Khoo wrote: > > I know the older SmartRAID IV family is supported, but I was wondering if the > > new cards are also supported, especially the Fibre Channel controllers. > > > > Also, is DLM(Distributed Lock Manager) available on current yet? > > No. This is blocked by Yours Truly not being able to make heads or > tail of somebody's comments WRT spl problems with the implementation, > and said somebody never coming up with the finished fixes he promised. > > > How about a FreeBSD native dptmgr; I'd prefer not to boot to DOS to > > run it. > > The only likely alternative is to run the SCO version under emulation. > This is farther from being possible after the CAM integration, as the > hooks for this was removed. > > Eivind. Hmmm... That's too bad. I really like the DPT controllers. We have one in our FreeBSD server here. I wonder how many out there use DPT controllers in their FreeBSD servers, and if there is enough demand would DPT port dptmgr to FreeBSD? SEK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 13:18:01 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09539 for freebsd-current-outgoing; Tue, 5 Jan 1999 13:18:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcpsj.pfcs.com (harlan.clark.net [168.143.10.179]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA09516 for ; Tue, 5 Jan 1999 13:17:57 -0800 (PST) (envelope-from Harlan.Stenn@pfcs.com) Received: from mumps.pfcs.com [192.52.69.11] (HELO mumps.pfcs.com) by pcpsj.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Tue, 5 Jan 1999 16:12:32 -0500 (EST) Received: from brown.pfcs.com [192.52.69.44] (HELO brown.pfcs.com) by mumps.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Tue, 5 Jan 1999 13:12:30 -0800 (PST) Received: from localhost [127.0.0.1] (HELO brown.pfcs.com) by brown.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Tue, 5 Jan 1999 16:12:30 -0500 (EST) X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" cc: Poul-Henning Kamp , jbg@masterplan.org (Jason George), freebsd-current@FreeBSD.ORG Subject: Re: News Server In-Reply-To: "Jordan K. Hubbard"'s (jkh@zippy.cdrom.com) message dated Tue, 05 Jan 1999 11:14:19. <6309.915563659@zippy.cdrom.com> X-Face: "csXK}xnnsH\h_ce`T#|pM]tG,6Xu.{3Rb\]&XJgVyTS'w{E+|-(}n:c(Cc* $cbtusxDP6T)Hr'k&zrwq0.3&~bAI~YJco[r.mE+K|(q]F=ZNXug:s6tyOk{VTqARy0#axm6BWti9C d Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 05 Jan 1999 16:12:30 -0500 Message-ID: <22897.915570750@brown.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If an alt.freebsd heirarachy is created, please make sure it's moderated (even robo-moderated). H To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 13:19:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09689 for freebsd-current-outgoing; Tue, 5 Jan 1999 13:19:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA09681 for ; Tue, 5 Jan 1999 13:19:53 -0800 (PST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id WAA08756 for ; Tue, 5 Jan 1999 22:19:24 +0100 (MET) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma008752; Tue, 5 Jan 99 22:19:24 +0100 Received: from dibbs1.eur.cis.philips.com (dibbs1.eur.cis.philips.com [130.139.33.66]) by smtprelay-nl1.philips.com (8.8.5/8.6.10-1.2.2m-970826) with ESMTP id WAA26236 for ; Tue, 5 Jan 1999 22:19:23 +0100 (MET) Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by dibbs1.eur.cis.philips.com (8.8.8/8.8.8) with SMTP id WAA27318 for ; Tue, 5 Jan 1999 22:19:23 +0100 (MET) Received: (qmail 5258 invoked by uid 666); 5 Jan 1999 21:19:45 -0000 Date: Tue, 5 Jan 1999 22:19:45 +0100 From: Jos Backus To: freebsd-svr4@atdot.dotat.org, current@FreeBSD.ORG Subject: Re: [freebsd-svr4] KLD conversion done; state of the world Message-ID: <19990105221945.A5025@hal.mpn.cp.philips.com> Reply-To: Jos Backus 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 I'd love to know whether this at some point is able to run the SCO5 or Solaris version of the Progress 4GL/RDBMS... -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 13:27:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10772 for freebsd-current-outgoing; Tue, 5 Jan 1999 13:27:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA10762 for ; Tue, 5 Jan 1999 13:27:43 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA104760518; Tue, 5 Jan 1999 10:35:18 -0500 Date: Tue, 5 Jan 1999 10:35:18 -0500 (EST) From: Bill Fumerola To: Vallo Kallaste Cc: Christian Kuhtz , current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. In-Reply-To: <19990105144139.A23264@matti.ee> Message-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, 5 Jan 1999, Vallo Kallaste wrote: > On Thu, Dec 31, 1998 at 01:55:47PM -0500, Christian Kuhtz wrote: > > > beta into a release is not a part of careful code base maintenance, IMHO. > > If memory serves, Postfix would indeed be the only thing in /usr/src/contrib > > which is beta. > > Isn't softupdates under /usr/src/contrib/sys/softupdates still beta ? > Am I misunderstanding something ? No. It's just restricted how we redistribute it. - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 13:39:57 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA13300 for freebsd-current-outgoing; Tue, 5 Jan 1999 13:39:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA13291 for ; Tue, 5 Jan 1999 13:39:55 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA01045; Tue, 5 Jan 1999 13:35:27 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901052135.NAA01045@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel C. Sobral" cc: current@FreeBSD.ORG, Mike Smith , "Jordan K. Hubbard" , Andrzej Bialecki Subject: Re: /boot/boot.rc && /boot/rc.d In-reply-to: Your message of "Wed, 06 Jan 1999 03:18:40 +0900." <36925780.75AB6581@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 05 Jan 1999 13:35:27 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I was thinking about possible on-comings "patches" in boot.rc > (currently known as boot.conf :), when I realized that for > third-party drivers or ports making use of loader it would better to > source files from a boot/rc.d directory. > > Is this already planned? I've been pondering different organisations for this stuff; there are a few things to consider here. The most significant being that there's a potentially valid set of reasons to want to load different module profiles, so you need a mechanism that allows you to have several different collections of module startup files. One approach, I call this the "macintosh" technique because it's similar to the way that inits/extensions are managed there: Modules live in /modules as *.ko (active) and *.kx (inactive) module initialiser scripts live as separate files alongside the modules, ie. as *.kinit. Load procedure is to simply scan the directory, and for every .ko file, read the .kinit file (if present) for the load command or simply load it with no args (and if not already loaded). This approach is nice because it's simple. You can make "profiles" by having module subdirectories with links back to the modules that you want to load (the loader groks symlinks) - there are wrinkles here. Another approach is to leave all of the .ko and .kinit files in /modules, and use a script file of some sort to nominate the modules to load/arguments etc. (overriding the .kinit files?). This makes it easy to swap profiles, one script per profile. While throwing these opposites around, consider also that some modules are going to be demand-loaded, so you only want to be listing/ nominating ones that are optional, and even then only ones that are required before the system boots. Thus I wonder if it's really necessary to have a particularly complex mechanism... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 13:41:53 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA13569 for freebsd-current-outgoing; Tue, 5 Jan 1999 13:41:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA13557 for ; Tue, 5 Jan 1999 13:41:47 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac9.wam.umd.edu ((IDENT root)@rac9.wam.umd.edu [128.8.10.149]) by po4.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id QAA28157; Tue, 5 Jan 1999 16:42:30 -0500 (EST) Received: from rac9.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1]) by rac9.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id QAA21113; Tue, 5 Jan 1999 16:41:08 -0500 (EST) Received: from localhost by rac9.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id QAA21102; Tue, 5 Jan 1999 16:41:06 -0500 (EST) X-Authentication-Warning: rac9.wam.umd.edu: culverk owned process doing -bs Date: Tue, 5 Jan 1999 16:41:06 -0500 (EST) From: Kenneth Wayne Culver To: steven cc: current@FreeBSD.ORG Subject: Re: So we're stuck with using timidity now? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Just curious.. what the status on the vm/oss "bug"? there is a fix on OSS's website that you must use on FreeBSD-3.0 release > > I see posts here saying its fixed (from early dec98) others > saying its still fubar'd. Posts on Usenet are contradictory > also. > > I got OSS's latest version ossfreebsd391i-30x > I'm using Current from Dec 27 1998 which has their patch > > running anything in X with OSS just kills the whole system, > Quake, Fxtv, X11Amp, mpg123.. you name it > That's wierd I don't have that problem. I am running the same thing you are, and I barely ever crash. (The last time I crashed was 3 weeks ago.) The problem still isn't completely fixed, but according to Dev (one of the main programmers of OSS) the problem is with FreeBSD's vm code. If I were you I would check to make sure that the patch you applied worked. If it did, you should be getting the same results that I get. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 13:51:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA15292 for freebsd-current-outgoing; Tue, 5 Jan 1999 13:51:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from camel7.mindspring.com (camel7.mindspring.com [207.69.200.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA15257 for ; Tue, 5 Jan 1999 13:50:55 -0800 (PST) (envelope-from stevensl@mindspring.net) Received: from freelove.mindspring.net (freelove.mindspring.net [207.69.192.92]) by camel7.mindspring.com (8.8.5/8.8.5) with SMTP id QAA17923; Tue, 5 Jan 1999 16:50:18 -0500 (EST) Date: Tue, 5 Jan 1999 16:50:45 -0500 (EST) From: steven To: Kenneth Wayne Culver cc: current@FreeBSD.ORG Subject: Re: So we're stuck with using timidity now? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 5 Jan 1999, Kenneth Wayne Culver wrote: > > Just curious.. what the status on the vm/oss "bug"? > > there is a fix on OSS's website that you must use on FreeBSD-3.0 release This was commited to CVS > are, and I barely ever crash. (The last time I crashed was 3 weeks ago.) > The problem still isn't completely fixed, but according to Dev (one of the > main programmers of OSS) the problem is with FreeBSD's vm code. If I were > you I would check to make sure that the patch you applied worked. If it > did, you should be getting the same results that I get. > Lucky! I've got a SB16. Wonder if PNP might be effecting it. Since the patch is in the CVS, and its definatly in my swap_pager.c and i made world since i updated. Someone mentioned they have the Dec30 current so maybe some changes were made between then? thanks for the ideas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 13:51:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA15606 for freebsd-current-outgoing; Tue, 5 Jan 1999 13:51:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gongshow.masterplan.org (masterplan.powersurfr.com [24.108.38.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA15590 for ; Tue, 5 Jan 1999 13:51:46 -0800 (PST) (envelope-from jbg@masterplan.org) Received: from infomat (infomat [192.168.4.2]) by gongshow.masterplan.org (8.8.8/8.8.8) with SMTP id OAA06423 for ; Tue, 5 Jan 1999 14:51:12 -0700 (MST) (envelope-from jbg@masterplan.org) Message-Id: <199901052151.OAA06423@gongshow.masterplan.org> From: jbg@masterplan.org (Jason George) To: freebsd-current@FreeBSD.ORG Subject: Re: News Server Organization: The Master Plan Always Fails... Date: Tue, 05 Jan 1999 21:51:16 GMT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> How hard would it be to set up a standalone news server specifically for >> FreeBSD, not connected to usenet in any way? > >That's sort of what the atomic playboy (great name BTW!) site has >done, I believe. > >- Jordan That's exactly what is it. This box is on a dedicated and fast SDSL line, but until I got my cablemodem recently, my access from home to mail and news was largely via UUCP-over-TCP on a 28.8. Instead of going through the hassle of setting up a proper news feed, I just grab the small number of groups that I want from my upstream provider. I use the suck port to do this. I rarely post, so a back channel isn't all that critical to me. Because forwarding the FreeBSD lists via UUCP home would be evil (especially on a dial-on-demand setup) and because I hate having to continuously clean my in-box, I hunted around for some other mechanism. The gated lists are the end result. Articles are added within about 2 seconds of hitting my alias file. There are a few caveats about the NNTP version of the lists. 1) I'm missing about 5MB of the ~75MB I've gated since September. This was due to inews chucking articles that quoted too much and added too little. This wasn't a big concern for me. I recompiled inews and nnrpd without that option this morning, so everything from here on in should be a-ok. 2) Not all the lists are gated. This can be corrected, of course. 3) The scripts do not like cross-posts at all. Only one group will get the post. Anyone wanting to hack the code to correct this should contact me. I don't have the time or resources to do this. I'd like some feedback on the performance of this setup. The box is routed into a 2Mbit SDSL line which is a handful of hops and a T-3 away from Sprint's Cheyenne, Wyoming POP. The actual location is in Edmonton, Alberta in western Canada, where it is snowing fairly heavily, and where the temperature will have dropped from just below freezing yesterday to below -30C by Thursday. Offers to save me from the Frozen Northern Wasteland are encouraged! ;-) Anyone wanting to yard down the groups to their own server is more than welcome. Please just inform me that you're going to be doing it, and please do it off-business hours Mountain (GMT-7). --Jason j.b.georgeieee.org jbgmasterplan.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 13:53:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA15950 for freebsd-current-outgoing; Tue, 5 Jan 1999 13:53:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA15934 for ; Tue, 5 Jan 1999 13:53:05 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id NAA14979 for ; Tue, 5 Jan 1999 13:52:37 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id NAA28205 for current@freebsd.org; Tue, 5 Jan 1999 13:52:36 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 05 Jan 1999 13:52:36 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: current@FreeBSD.ORG Subject: HEADS UP: Suffix change for PIC object files Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I want to commit a change which I believe will have zero impact on anybody. The change is broad in scope, so I thought I'd better check to make sure it won't cause unanticipated problems. What I want to do is modify and a couple of assorted Makefiles, to change the filename suffix for PIC object files used in building shared libraries from ".so" to ".So". The reason is that the existing suffix conflicts with the standard suffix for shared libraries that are loaded with dlopen(). One example of that is PAM modules. Even ignoring PAM, we can expect to see more and more use of dlopen() in our tree as time goes on. Now, just to make this crystal clear, I'm not talking about changing the suffix for shared libraries, or for anything that actually gets installed by "make world". All I want to change is the suffix of the intermediate PIC object files that make up the shared libraries. The PIC object files exist only during the build process, and they never escape the "/usr/obj" tree. This won't change what's on installed systems one bit. Modules to be loaded using dlopen() have traditionally been named "*.so" in all Unix variants I'm aware of. This usage of ".so" predates FreeBSD's use of the same suffix for PIC object files. The suffixes need to be different to avoid clobbering files when building dynamically loaded modules. I should also stress that this won't affect 3rd party applications (including ports) at all. They don't use , and they are free to use any suffix they want to for their PIC object files. I've tested this change through several "make world" cycles, and it hasn't caused any problems that I can see. If any of you can think of a compelling reason not to make this change, please let me know. I'll commit it this coming weekend otherwise. One final note. Questions like this often lead to interminable threads consisting mainly of squabbles about peripheral and inconsequential issues. I and all of the other readers would greatly appreciate it if you'd confine your responses to _compelling_ reasons not to make the change. If you simply don't like changes, or don't like my choice of suffix, then please spare us a long and pointless diversion. Thanks, John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 14:00:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17383 for freebsd-current-outgoing; Tue, 5 Jan 1999 14:00:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA17369 for ; Tue, 5 Jan 1999 14:00:44 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.1/8.9.1) with ESMTP id QAA40131; Tue, 5 Jan 1999 16:57:32 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <199901052157.QAA40131@whizzo.transsys.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John Polstra cc: current@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: HEADS UP: Suffix change for PIC object files References: In-reply-to: Your message of "Tue, 05 Jan 1999 13:52:36 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 05 Jan 1999 16:57:31 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I want to commit a change which I believe will have zero impact on > anybody. The change is broad in scope, so I thought I'd better check > to make sure it won't cause unanticipated problems. > > What I want to do is modify and a couple of assorted > Makefiles, to change the filename suffix for PIC object files used in > building shared libraries from ".so" to ".So". The reason is that > the existing suffix conflicts with the standard suffix for shared > libraries that are loaded with dlopen(). One example of that is PAM > modules. Even ignoring PAM, we can expect to see more and more use of > dlopen() in our tree as time goes on. Sounds OK to me, for all that means. I'd suggest that it might be useful for the 'clean' target to nuke the old suffix for a while. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 14:01:52 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17516 for freebsd-current-outgoing; Tue, 5 Jan 1999 14:01:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA17505 for ; Tue, 5 Jan 1999 14:01:49 -0800 (PST) (envelope-from vallo@myhakas.matti.ee) Received: from myhakas.matti.ee (myhakas [194.126.98.150]) by solaris.matti.ee (8.8.8/8.8.8.s) with ESMTP id AAA09497; Wed, 6 Jan 1999 00:01:16 +0200 (EET) Received: (from vallo@localhost) by myhakas.matti.ee (8.9.1/8.9.1) id AAA54014; Wed, 6 Jan 1999 00:01:15 +0200 (EET) (envelope-from vallo) Message-ID: <19990106000115.A53948@matti.ee> Date: Wed, 6 Jan 1999 00:01:15 +0200 From: Vallo Kallaste To: Bill Fumerola Cc: Christian Kuhtz , current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. Reply-To: vallo@matti.ee References: <19990105144139.A23264@matti.ee> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Bill Fumerola on Tue, Jan 05, 1999 at 10:35:18AM -0500 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 05, 1999 at 10:35:18AM -0500, Bill Fumerola wrote: > > > beta into a release is not a part of careful code base maintenance, IMHO. > > > If memory serves, Postfix would indeed be the only thing in /usr/src/contrib > > > which is beta. > > > > Isn't softupdates under /usr/src/contrib/sys/softupdates still beta ? > > Am I misunderstanding something ? > > No. It's just restricted how we redistribute it. Yes I know it's under contrib because of licensing restrictions (as anybody can read off the LINT). My main question is is softupdates considered stable ? Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 14:10:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA18302 for freebsd-current-outgoing; Tue, 5 Jan 1999 14:10:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA18297 for ; Tue, 5 Jan 1999 14:10:28 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id OAA15078; Tue, 5 Jan 1999 14:09:59 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id OAA28275; Tue, 5 Jan 1999 14:09:59 -0800 (PST) (envelope-from jdp@polstra.com) Date: Tue, 5 Jan 1999 14:09:59 -0800 (PST) Message-Id: <199901052209.OAA28275@vashon.polstra.com> To: louie@TransSys.COM Subject: Re: HEADS UP: Suffix change for PIC object files Newsgroups: polstra.freebsd.current In-Reply-To: <199901052157.QAA40131@whizzo.transsys.com> References: Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199901052157.QAA40131@whizzo.transsys.com>, Louis A. Mamakos wrote: > > Sounds OK to me, for all that means. I'd suggest that it might be useful > for the 'clean' target to nuke the old suffix for a while. Good point. It does exactly that. Sorry I forgot to mention it in the original message. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 14:26:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20142 for freebsd-current-outgoing; Tue, 5 Jan 1999 14:26:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hjgaofa.getmoretraffic.com (CBL-panamerican.hs.earthlink.net [208.233.115.216]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA20023 for ; Tue, 5 Jan 1999 14:26:11 -0800 (PST) (envelope-from getmoretraffic@getmoretraffic.com) Subject: Protecting Your Assets from Legal Attack Content-Type: text/plain; charset=ISO-8859-1 Message-ID: To: freebsd-current@FreeBSD.ORG Date: Tue, 05 Jan 1999 17:25:10 -0500 From: cbgqwbpq@getmoretraffic.com Reply-To: getmoretraffic@getmoretraffic.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG IMPORTANT INFORMATION ON HOW TO PRESERVE YOUR ASSETS YOU WORKED HARD TO ACQUIRE THEM--- NOW LEARN HOW TO PROTECT THEM USING ASSET PROTECTION TRUSTS In our litigious society where baseless lawsuits are commonplace, it is no longer enough to simply worry about wealth accumulation. Wealth Preservation and Asset Protection Planning are now real issues. With the possibility of a single lawsuit wiping away a lifetime of savings, individuals (especially those with families), have made concerted efforts to preserve assets and assure the family estate for future generations. Experts agree that the one of the best ways to do so is with the aid of Asset Protection Trusts. An Asset Protection Trust is not the ideal plan for everyone, but where it is a good solution, professionals (doctors, lawyers, stockbrokers, etc.), owners of closely held businesses, and others who have spent a lifetime accumulating wealth can now put up formidable barriers to thwart potential creditor suits and other civil litigation. If you want to learn more about this legal option and the possibility of providing a more comprehensive protection for you and your family, just click below to obtain FREE additional information. There is NO OBLIGATION and you will receive no follow-up calls or further correspondence unless you specifically request it. All inquiries are kept CONFIDENTIAL and if requested, you are assured a response by a member of our legal staff within forty-eight (48) hours. Click on the link below and find out whether or not an Asset Protection Trust is right for you: http://getmoretraffic.com/offshorelaw ************************************************************************************* If you wish to be removed from our mailing list, we will gladly do so. Please click the REPLY button and put the word “REMOVE” in the subject line to have your name promptly deleted. ************************************************************************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 14:38:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA22350 for freebsd-current-outgoing; Tue, 5 Jan 1999 14:38:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fourier.physics.purdue.edu (fourier.physics.purdue.edu [128.210.146.43]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA22341 for ; Tue, 5 Jan 1999 14:38:44 -0800 (PST) (envelope-from jonsmith@fourier.physics.purdue.edu) Received: from localhost (jonsmith@localhost) by fourier.physics.purdue.edu (8.8.8/8.8.8) with SMTP id RAA13036 for ; Tue, 5 Jan 1999 17:33:56 -0500 (EST) (envelope-from jonsmith@fourier.physics.purdue.edu) Date: Tue, 5 Jan 1999 17:33:56 -0500 (EST) From: Jonathan Smith To: freebsd-current@FreeBSD.ORG Subject: Read this, and use appropriately, one and all 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 NOTICE TO BULK EMAILER(S): Pursuant to US Code, Title 47, Chapter 5, Subchapter II, 227, any and all unsolicited commercial e-mail sent to this address is subject to a download and archival fee in the amount of $500 US Dollars. E-Mailing denotes acceptance of these terms. "If kisses could kill (gulp), that one would have flattened several small towns...." Vir Cotto, Babylon 5 "Tu was du willst." Die Unendliche Geschichte, von Michael Ende "Do as you wish." The Neverending Story, by Michael Ende The Microsoft Soloution, "newfs && make reinstall" Jon C. Smith (765)49-48628 PHYS 31h jonsmith@fourier.physics.purdue.edu 1396 Physics Building, West lafayette Purdue Univesity, Indiana 47906-1396 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 14:44:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23089 for freebsd-current-outgoing; Tue, 5 Jan 1999 14:44:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23072 for ; Tue, 5 Jan 1999 14:44:04 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id OAA97949; Tue, 5 Jan 1999 14:43:27 -0800 (PST) (envelope-from dillon) Date: Tue, 5 Jan 1999 14:43:27 -0800 (PST) From: Matthew Dillon Message-Id: <199901052243.OAA97949@apollo.backplane.com> To: Greg Lehey Cc: Peter Jeremy , current@FreeBSD.ORG Subject: Re: Y2K, Y 2038? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> overly concerned :-). :> :> There was a very similar discussion some months ago regarding the :> timestamp field in the inode (on -hackers from memory). I don't :> think the discussion went anywhere fruitful. : :Part of that discussion was concerned with the fact that, correctly or :incorrectly, people use negative time_t's. This would break that for :a comparatively minor benefit. It isn't so much that people use negative time_t's as it is people comparing time_t's and assuming a *signed* result. If time_t is unsigned, the result will be unsigned. This screws up relative compares in a lot of legacy code. Neither can time_t simply magically become 64 bits on systems where it was 32 bits before - that would be a disaster. A lot of software stores time_t in binary form in databases and such - for all sorts of reasons. It would be a disaster an order of magnitude greater then the mess that occured when 4.4 first started using 64 bit file offsets and a lot of legacy software didn't compare because it manually extern'd system functions rather then #include the correct header file. I would prefer NOT making *two* hacks to the time system. We should just move to 64 bit 'ltime_t' or something like that. It is not a big deal. Then we'll have 30 years to translate the legacy time_t's useage into the new ltime_t useage. -Matt :Greg :-- :See complete headers for address, home page and phone numbers :finger grog@lemis.com for PGP public key : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-current" in the body of the message : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 14:46:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23544 for freebsd-current-outgoing; Tue, 5 Jan 1999 14:46:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23539 for ; Tue, 5 Jan 1999 14:46:32 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id OAA97990; Tue, 5 Jan 1999 14:46:00 -0800 (PST) (envelope-from dillon) Date: Tue, 5 Jan 1999 14:46:00 -0800 (PST) From: Matthew Dillon Message-Id: <199901052246.OAA97990@apollo.backplane.com> To: Jonathan Smith Cc: freebsd-current@FreeBSD.ORG Subject: Re: Read this, and use appropriately, one and all Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG People, you realize that spamming is only going to get worse. I managed several *thousand* mailing lists on BEST.COM. One after another these lists were infiltrated by spammers and had to be turned into closed-systems (only subscribers to the list could post). These cute little 'legal' noticed don't mean shit to the spammers. They don't read the lists, they just post to them. -Matt : :NOTICE TO BULK EMAILER(S): Pursuant to US Code, Title 47, Chapter 5, :Subchapter II, 227, any and all unsolicited commercial e-mail sent to this :address is subject to a download and archival fee in the amount of $500 US :Dollars. E-Mailing denotes acceptance of these terms. :... Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 14:49:57 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24123 for freebsd-current-outgoing; Tue, 5 Jan 1999 14:49:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24107 for ; Tue, 5 Jan 1999 14:49:53 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id OAA98074; Tue, 5 Jan 1999 14:49:25 -0800 (PST) (envelope-from dillon) Date: Tue, 5 Jan 1999 14:49:25 -0800 (PST) From: Matthew Dillon Message-Id: <199901052249.OAA98074@apollo.backplane.com> To: Julian Elischer Cc: freebsd-svr4@atdot.dotat.org, current@FreeBSD.ORG Subject: Re: [freebsd-svr4] KLD conversion done; state of the world Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I agree.... :this is -current dammit.. :get it in.... :I'm sure you'll find backers... :this should go in asap so people can start using solaris binaries. : : :On Tue, 5 Jan 1999, David O'Brien wrote: : :> > - I have commit privs, but I'm waiting for the 3.0.1 split before I :> > import anything due to the cruft-culling that's going on now, the :> :> Please bring this up with core (if you haven't already). If you wait to :> commit this to 3.1-CURRENT, it will be over a year until the average :> FreeBSDer will see SVR4 emulation. :> :> -- :> -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) Heh. Uncle! Uncle! Ah, what the hell. commit it I say, commit it now, before the sky starts to fall! -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 14:52:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24870 for freebsd-current-outgoing; Tue, 5 Jan 1999 14:52:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24862 for ; Tue, 5 Jan 1999 14:52:14 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id OAA98102; Tue, 5 Jan 1999 14:51:45 -0800 (PST) (envelope-from dillon) Date: Tue, 5 Jan 1999 14:51:45 -0800 (PST) From: Matthew Dillon Message-Id: <199901052251.OAA98102@apollo.backplane.com> To: "Jordan K. Hubbard" Cc: Licia , freebsd-current@FreeBSD.ORG Subject: Re: News Server Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> How hard would it be to set up a standalone news server specifically for :> FreeBSD, not connected to usenet in any way? : :That's sort of what the atomic playboy (great name BTW!) site has :done, I believe. : :- Jordan Trivial to do this, especially if the group is read-only and locally controlled (i.e. direct mailing list feed-in). If other people don't get it done by Feb 1, someone remind me and I'll do it. One justs sets it up such that a 'R'eply-to-sender in the news client emails the right people and such a system would be very useable. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 15:13:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27991 for freebsd-current-outgoing; Tue, 5 Jan 1999 15:13:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ogurok.com (ogurok.com [208.212.72.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA27983 for ; Tue, 5 Jan 1999 15:13:08 -0800 (PST) (envelope-from oleg@ogurok.com) Received: from localhost (oleg@localhost) by ogurok.com (8.9.1/8.9.1) with ESMTP id SAA28360 for ; Tue, 5 Jan 1999 18:22:27 -0500 (EST) (envelope-from oleg@ogurok.com) Date: Tue, 5 Jan 1999 18:22:27 -0500 (EST) From: Oleg Ogurok To: current@FreeBSD.ORG Subject: elf kernel and screensaverld: /kernel malformed input file Message-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 there. I am running CURRENT cvsup'ed 3-4 days ago. I uncommented string KERNFORMAT=elf in /etc/make.conf and compiled kernel. Then I rebooted and typed "/boot/loader" in boot prompt. Everything seems to work fine except I am getting error: screensaverld: /kernel malformed input file (no rel on archive) Looks like screensaver module doesn't work anymore, right? Where can I find information about ELF kernel and files such /boot.config and /boot/loader.conf ? Oleg Ogurok oleg@ogurok.com http://www.ogurok.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 15:16:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28842 for freebsd-current-outgoing; Tue, 5 Jan 1999 15:16:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lorax.ubergeeks.com (lorax.ubergeeks.com [206.205.41.241]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA28834 for ; Tue, 5 Jan 1999 15:16:27 -0800 (PST) (envelope-from adrian@lorax.ubergeeks.com) Received: from localhost (adrian@localhost) by lorax.ubergeeks.com (8.8.8/8.8.8) with SMTP id SAA01815; Tue, 5 Jan 1999 18:15:09 -0500 (EST) (envelope-from adrian@lorax.ubergeeks.com) Date: Tue, 5 Jan 1999 18:15:09 -0500 (EST) From: ADRIAN Filipi-Martin Reply-To: Adrian Filipi-Martin To: Alfred Perlstein cc: "Thomas T. Veldhouse" , Blaz Zupan , freebsd-current@FreeBSD.ORG Subject: Re: Kernel cannot mount root with new bootblocks In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 5 Jan 1999, Alfred Perlstein wrote: > > On Tue, 5 Jan 1999, Thomas T. Veldhouse wrote: > > > In light of all the boot problems I have seen, are there still plans to go > > ELF Kernel tomorrow? I think you will see that people are going to take a > > wait and see aproach with CURRENT if this happens. > > Naw, lets have the commiters walking on eggshells supporting both targets > until the next release. I'm sure they're really keen on that. :) > > I've noticed most all the problems people have been experiancing can be > attributed to user error, not programming error, the boot blocks work fine > and are extremely configuable. Unfortunatly the only documentation > available at this point is this list archive. > > -Alfred Not true. I've already notified Robert Nordier about a problem. It looks like the boot blocks don't work well when the first bios disk is not da0, but da1. This is the case when you swap the channels on a dual channel controller. All in all I do agree with dumping the old blocks in favor of the new. As a temporary work around I put "0:da(1,a)kernel" in /boot.config, yes, boot.config. The original pposter might try this or something similar. Note, I think the proper fix, and I may look into this, is to detect that the channels are swapped and thereby swap ahc0 and ahc1, which would make the bios and the unit number agree. Adrian -- [ adrian@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 15:17:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28941 for freebsd-current-outgoing; Tue, 5 Jan 1999 15:17:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alushta.NL.net (alushta.NL.net [193.78.240.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA28933 for ; Tue, 5 Jan 1999 15:17:53 -0800 (PST) (envelope-from benst@terminus.stuyts.nl) Received: from stuyts by alushta.NL.net with UUCP id <5039-19507>; Wed, 6 Jan 1999 00:16:55 +0100 Received: from daneel.stuyts.nl (daneel.stuyts.nl [193.78.231.7]) by terminus.stuyts.nl (8.9.1/8.9.1) with ESMTP id AAA00809 for ; Wed, 6 Jan 1999 00:15:52 +0100 (MET) (envelope-from benst) Received: (from benst@localhost) by daneel.stuyts.nl (8.8.5/8.8.5) id AAA07950 for current@freebsd.org; Wed, 6 Jan 1999 00:15:48 +0100 (MET) Message-Id: <199901052315.AAA07950@daneel.stuyts.nl> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 3.3 v118.2) X-Nextstep-Mailer: Mail 3.3 (Enhance 1.2) Received: by NeXT.Mailer (1.118.2) From: Ben Stuyts Date: Wed, 6 Jan 99 00:15:46 +0100 To: current@FreeBSD.ORG Subject: Trouble booting from WinNT with new boot loader Reply-To: ben@stuyts.nl Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I am using the WinNT boot menu to load freebsd. This worked fine until the latest batch of updates I did. This is a Gigabyte 586DX with dual P166MMX, 64 meg ram, one IDE drive and 2 scsi drives. WinNT is installed on the IDE drive. FreeBSD is installed on da0 (/) and da1 using the onboard scsi controller. I have installed the new bootblocks on da0, and copied the bootsector for the WinNT boot loader. I have installed an elf kernel. All this is recent up to Jan 3. If I disable the onboard IDE, and boot directly from da0, everything works fine. Now, when the WinNT boot loader boots FreeBSD, it loads the kernel, but then panics with a message that it cannot load init. It looks like it has the wrong boot device or something like that? currdev is set to disk2s1a, which is correct I think. disk1s1a is the IDE drive, right? I have appended my kernel config below, and a dmesg when booting without WinNT. Any help appreciated, Ben [terminus.stuyts.nl i386/conf]14: cat TERMINUS-SMP machine "i386" cpu "I586_CPU" ident TERMINUS-NOSMP maxusers 32 # Create a SMP capable kernel (mandatory options): options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Lets always enable the kernel debugger for SMP. options DDB options INET #InterNETworking options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem #options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options "CD9660_ROOT" #CD-ROM usable as root device options FFS_ROOT #FFS usable as root device [keep this!] # Allow the FFS to use Softupdates technology. # To do this you need to copy the two files # /sys/ufs/ffs/softdep.h and /sys/ufs/ffs/ffs_softdep.c # from /usr/src/contrib/sys/softupdates # and understand the licensing restrictions. # You should also check on the FreeBSD website for newer versions. options SOFTUPDATES options NFS_ROOT #NFS usable as root device options PROCFS #Process filesystem options MFS #Memory File System options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=5000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor # These three options provide support for System V Interface # Definition-style interprocess communication, in the form of shared # memory, semaphores, and message queues, respectively. # options SYSVSHM options SYSVSEM options SYSVMSG config kernel root on da0 controller isa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 # A single entry for any of these controllers (ncr, ahb, ahc, amd) is # sufficient for any number of installed devices. controller ncr0 controller ahc0 controller scbus0 device da0 device sa0 device pass0 device cd0 #Only need one of these, the code dynamically grows # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" conflicts tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device sio2 at isa? port "IO_COM3" tty irq 10 vector siointr # device sio3 at isa? port 0x3e0 tty irq 10 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. device de0 pseudo-device loop pseudo-device ether pseudo-device sl 1 # ijppp uses tun instead of ppp device #pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 16 #pseudo-device gzip # Exec gzipped a.out's pseudo-device bpfilter 4 #Berkeley packet filter pseudo-device vn #Vnode driver (turns a file into a device) # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing # Controls all sound devices controller snd0 device sb0 at isa? port 0x220 irq 5 conflicts drq 1 vector sbintr device sbxvi0 at isa? drq 5 device sbmidi0 at isa? port 0x300 device awe0 at isa? port 0x620 device opl0 at isa? port 0x388 # Firewall support: options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about # dropped packets # options "IPFIREWALL_VERBOSE_LIMIT=100" #limit verbosity options IPDIVERT #divert sockets device joy0 at isa? port "IO_GAME" [terminus.stuyts.nl i386/conf]15: dmesg Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #0: Sun Jan 3 20:59:10 MET 1999 benst@terminus.stuyts.nl:/usr/source/src/sys/compile/TERMINUS-SMP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P55C (586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping=3 Features=0x8003bf real memory = 67108864 (65536K bytes) config> quit avail memory = 62238720 (60780K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00030010, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00030010, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xf02e2000. Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 ide_pci0: rev 0x00 on pci0.7.1 ncr0: rev 0x12 int a irq 16 on pci0.8.0 de0: rev 0x11 int a irq 17 on pci0.9.0 de0: SMC 21041 [10Mb/s] pass 1.1 de0: address 00:00:c0:1f:54:e8 vga0: rev 0x02 int a irq 18 on pci0.10.0 ahc0: rev 0x00 int a irq 19 on pci0.12.0 ahc0: Using left over BIOS settings ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio2 at 0x3e8-0x3ef irq 10 on isa sio2: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S npx0 on motherboard npx0: INT 16 interface sb0 at 0x220 irq 5 drq 1 on isa snd0: sbxvi0 at drq 5 on isa snd0: sbmidi0 at 0x300 on isa snd0: awe0 at 0x620 on isa AWE32: not detected opl0 at 0x388 on isa snd0: joy0 at 0x201 on isa joy0: joystick Intel Pentium detected, installing workaround for F00F bug APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 IP packet filtering initialized, divert enabled, rule-based forwarding disabled, unlimited logging Waiting 5 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! da1 at ahc0 bus 0 target 3 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.0MB/s transfers (10.0MHz, offset 8) da1: 810MB (1660299 512 byte sectors: 64H 32S/T 810C) changing root device to da0s1a cd0 at ahc0 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.0MB/s transfers (10.0MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present da0 at ahc0 bus 0 target 1 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4134MB (8467200 512 byte sectors: 64H 32S/T 4134C) ffs_mountfs: superblock updated for soft updates cd1 at ahc0 bus 0 target 5 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 3.300MB/s transfers cd1: Attempt to query device size failed: NOT READY, Logical unit not ready, cause not reportable To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 15:21:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29567 for freebsd-current-outgoing; Tue, 5 Jan 1999 15:21:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA29562 for ; Tue, 5 Jan 1999 15:21:54 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA01625; Tue, 5 Jan 1999 15:17:53 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901052317.PAA01625@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: ben@stuyts.nl cc: current@FreeBSD.ORG Subject: Re: Trouble booting from WinNT with new boot loader In-reply-to: Your message of "Wed, 06 Jan 1999 00:15:46 +0100." <199901052315.AAA07950@daneel.stuyts.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 05 Jan 1999 15:17:53 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is a Gigabyte 586DX with dual P166MMX, 64 meg ram, one IDE drive and 2 > scsi drives. WinNT is installed on the IDE drive. FreeBSD is installed on da0 > (/) and da1 using the onboard scsi controller. You need "set num_ide_disks=1" in /boot/boot.conf; you can also break to the loader commandline and issue the command directly to test it out first. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 15:45:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03198 for freebsd-current-outgoing; Tue, 5 Jan 1999 15:45:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lorax.ubergeeks.com (lorax.ubergeeks.com [206.205.41.241]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03188 for ; Tue, 5 Jan 1999 15:45:49 -0800 (PST) (envelope-from adrian@lorax.ubergeeks.com) Received: from localhost (adrian@localhost) by lorax.ubergeeks.com (8.8.8/8.8.8) with SMTP id SAA01910; Tue, 5 Jan 1999 18:45:16 -0500 (EST) (envelope-from adrian@lorax.ubergeeks.com) Date: Tue, 5 Jan 1999 18:45:16 -0500 (EST) From: ADRIAN Filipi-Martin Reply-To: Adrian Filipi-Martin To: Peter Jeremy cc: current@FreeBSD.ORG Subject: Re: Y2K, Y 2038? In-Reply-To: <99Jan5.205931est.40326@border.alcanet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 5 Jan 1999, Peter Jeremy wrote: > Jonathan Smith wrote: > > Deal with it _now_ before the Y2038 Emergency is upon us and > >the world is freaking out over it. Perhaps an introduction of a 64 bit > >time, > A much simpler change is to make time_t an unsigned long - that gives > us another 68 years grace - by which time I doubt many of us will be > overly concerned :-). Cannot do that. Believe it or not, but you should be able to do calculations involving dates prior to 1/1/70. Perhaps if you first moved the Unix epoch back 30-40 years, but then you're back where you started. Adrian -- [ adrian@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 15:52:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04436 for freebsd-current-outgoing; Tue, 5 Jan 1999 15:52:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sicily.odyssey.cs.cmu.edu (SICILY.ODYSSEY.CS.CMU.EDU [128.2.185.138]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA04410 for ; Tue, 5 Jan 1999 15:52:41 -0800 (PST) (envelope-from rvb+@sicily.odyssey.cs.cmu.edu) To: current@FreeBSD.ORG Subject: i386/conf/PCCARD From: "Robert V. Baron" Date: 05 Jan 1999 18:51:26 -0500 Message-ID: Lines: 4 X-Mailer: Gnus v5.4.46/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been wondering, of late, how well/if laptops are supported in -current. It seems that the configuration, PCCARD, has recently (since mid December) has gone away. Is this the answer? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 16:00:02 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05903 for freebsd-current-outgoing; Tue, 5 Jan 1999 15:58:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sicily.odyssey.cs.cmu.edu (SICILY.ODYSSEY.CS.CMU.EDU [128.2.185.138]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA05898 for ; Tue, 5 Jan 1999 15:58:46 -0800 (PST) (envelope-from rvb+@sicily.odyssey.cs.cmu.edu) To: current@freebsd.org Subject: building boot From: "Robert V. Baron" Date: 05 Jan 1999 18:57:41 -0500 Message-ID: Lines: 10 X-Mailer: Gnus v5.4.46/Emacs 19.34 Sender: owner-freebsd-current@freebsd.org Precedence: bulk X-Loop: FreeBSD.ORG I recently pulled down a new src/sys and tried to build boot. This did not work too well, because the app environment and includes files were a month old. Basically, the machine/ansi.h was missing the __int typedefs. So should boot/ be treated like the kernel and just use kernel relative headers or should it be like any old user program and just depend on /usr/include. Currently boot/ does both. It can pull in things from sys/sys relative to the the kernel src. But it also tries to get things relative to machine -- which is not otherwise defined so it pulls from /usr/include/machine. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 16:07:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA08534 for freebsd-current-outgoing; Tue, 5 Jan 1999 16:07:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from anthrax.speck (cx19313-a.nwptn1.va.home.com [24.2.49.151]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA08529 for ; Tue, 5 Jan 1999 16:07:35 -0800 (PST) (envelope-from jedgar@speck.ml.org) Received: from localhost (jedgar@localhost) by anthrax.speck (8.9.1/8.9.1) with ESMTP id TAA02277 for ; Tue, 5 Jan 1999 19:06:59 -0500 (EST) (envelope-from jedgar@speck.ml.org) X-Authentication-Warning: anthrax.speck: jedgar owned process doing -bs Date: Tue, 5 Jan 1999 19:06:59 -0500 (EST) From: "Chris D. Faulhaber" X-Sender: jedgar@anthrax.speck To: current@FreeBSD.ORG Subject: Re: i386/conf/PCCARD 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 5 Jan 1999, Robert V. Baron wrote: > > I've been wondering, of late, how well/if laptops are supported in > -current. It seems that the configuration, PCCARD, has recently > (since mid December) has gone away. Is this the answer? > I've been running 3.0-CURRENT on my laptop since 3.0-RELEASE came out without any problems. Now that you mention it, PCCARD is gone; but I've been updating my current config since -RELEASE. So far, no problems have arisen; apm support is there, XFree86-3.3.3 supports the NeoMagic chipsets (standard in many models), and as long as your pcmcia chipset/cards are supported by default, everything should work ok. -Chris All the true gurus I've met never claimed they were one, and always pointed to someone better. -Anonymous To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 16:10:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA09108 for freebsd-current-outgoing; Tue, 5 Jan 1999 16:10:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA09099 for ; Tue, 5 Jan 1999 16:10:54 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA04059; Tue, 5 Jan 1999 16:07:39 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdEE4053; Wed Jan 6 00:07:33 1999 Date: Tue, 5 Jan 1999 16:07:30 -0800 (PST) From: Julian Elischer To: "Robert V. Baron" cc: current@FreeBSD.ORG Subject: Re: building boot In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG you may need to do "make includes" in /usr/src On 5 Jan 1999, Robert V. Baron wrote: > > I recently pulled down a new src/sys and tried to build boot. This > did not work too well, because the app environment and includes files > were a month old. Basically, the machine/ansi.h was missing the __int > typedefs. So should boot/ be treated like the kernel and just use > kernel relative headers or should it be like any old user program and > just depend on /usr/include. Currently boot/ does both. It can > pull in things from sys/sys relative to the the kernel src. But > it also tries to get things relative to machine -- which is not > otherwise defined so it pulls from /usr/include/machine. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 16:42:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA13079 for freebsd-current-outgoing; Tue, 5 Jan 1999 16:42:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from jason02.u.washington.edu (jason02.u.washington.edu [140.142.76.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA13073 for ; Tue, 5 Jan 1999 16:42:31 -0800 (PST) (envelope-from jcwells@u.washington.edu) Received: from saul10.u.washington.edu (root@saul10.u.washington.edu [140.142.13.73]) by jason02.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA32908 for ; Tue, 5 Jan 1999 16:42:03 -0800 Received: from S8-37-26.student.washington.edu (S8-37-26.student.washington.edu [128.208.37.26]) by saul10.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA07844 for ; Tue, 5 Jan 1999 16:42:02 -0800 (PST) Date: Tue, 5 Jan 1999 16:41:30 -0800 (PST) From: "Jason C. Wells" X-Sender: jason@s8-37-26.student.washington.edu Reply-To: "Jason C. Wells" To: FreeBSD-current Subject: Splashkit-980202 on 3.0-RELEASE Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG All of the changes in kbdcontrol.diff seem to have ended up included in 3.0-RELEASE source code except for one. RCS file: /src/CVS/src/usr.sbin/kbdcontrol/lex.l,v retrieving revision 1.6 diff -u -r1.6 lex.l --- lex.l 1998/01/07 08:43:28 1.6 +++ lex.l 1998/01/29 13:14:38 @@ -59,6 +59,7 @@ boot { return TRBT; } debug { return TDBG; } susp { return TSUSP; } +splash { return TSPSC; } NUL|nul { number = 0; return TNUM; } SOH|soh { number = 1; return TNUM; } >From the 3.0-RELEASE version of lex.l we see the version number 1.8 is greater than the 1.6 in the splaskit diff. * $Id: lex.l,v 1.8 1998/08/06 09:44:23 yokota Exp $ I assume that the "splash { return TSPSC; }" code is still needed. Was it forgotten during the change of lex.l from 1.6 to 1.8 or am I missing something? I know splashkit is for -current. It seems by looking at the version numbers that this diff should already be in 3.0-release. Catchya Later, | UW Mechanical Engineering Jason Wells | http://weber.u.washington.edu/~jcwells/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 16:45:59 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA13776 for freebsd-current-outgoing; Tue, 5 Jan 1999 16:45:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp1.erols.com (smtp1.erols.com [207.172.3.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA13764 for ; Tue, 5 Jan 1999 16:45:57 -0800 (PST) (envelope-from shmit@natasya.noc.erols.net) Received: from natasya.noc.erols.net (natasya.noc.erols.net [207.172.25.236]) by smtp1.erols.com (8.8.8/8.8.5) with ESMTP id TAA08505; Tue, 5 Jan 1999 19:45:05 -0500 (EST) Received: (from shmit@localhost) by natasya.noc.erols.net (8.9.1/8.9.1) id TAA53721; Tue, 5 Jan 1999 19:45:01 -0500 (EST) Message-ID: <19990105194501.O2451@kublai.com> Date: Tue, 5 Jan 1999 19:45:01 -0500 From: Brian Cully To: Poul-Henning Kamp , Brian Handy Cc: "Jordan K. Hubbard" , Mike Smith , Garrett Wollman , Tom Bartol , current@FreeBSD.ORG Subject: Re: New boot blocks for serial console ... Reply-To: shmit@kublai.com References: <15577.915482257@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <15577.915482257@critter.freebsd.dk>; from Poul-Henning Kamp on Mon, Jan 04, 1999 at 09:37:37PM +0100 X-Sender: If your mailer pays attention to this, it's broken. X-PGP-Info: finger shmit@kublai.com for my public key. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 04, 1999 at 09:37:37PM +0100, Poul-Henning Kamp wrote: > >>I'm curious how many codicils there are in their contract about > >>"tamper-proof", however. [...] > > > >What colors does it come in? > > I think I already said that: any color you like. As long as it's black. -- Brian Cully You think you're queer? I'll tell you something: we're all queer. If you get befuddled by a middle class morality, get shut of it. Shut it out.... Is there an absolute morality? I don't think so. You think that? Act that way. -- Glengarry Glen Ross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 16:47:43 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14415 for freebsd-current-outgoing; Tue, 5 Jan 1999 16:47:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fw.bby.com.au (ns.bby.com.au [192.83.119.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14388 for ; Tue, 5 Jan 1999 16:47:39 -0800 (PST) (envelope-from gnb@itga.com.au) Received: (from daemon@localhost) by fw.bby.com.au (8.8.8/8.6.9) id LAA18197; Wed, 6 Jan 1999 11:46:53 +1100 (EST) Received: from melba.bby.com.au(192.43.186.1) via SMTP by fw.bby.com.au, id smtpd018195; Wed Jan 6 00:46:44 1999 Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by melba.bby.com.au (8.8.2/8.8.2) with ESMTP id LAA06657; Wed, 6 Jan 1999 11:46:45 +1100 (EST) Received: from lightning (lightning [192.168.71.20]) by lightning.itga.com.au (8.9.1a/8.9.1) with ESMTP id LAA14162; Wed, 6 Jan 1999 11:46:40 +1100 (EST) Message-Id: <199901060046.LAA14162@lightning.itga.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: Matthew Dillon Cc: Mike Smith , current@FreeBSD.ORG Subject: Re: SOFTUPDATES hangs keyboard In-reply-to: Your message of Tue, 05 Jan 1999 00:05:20 -0800. Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="==_Exmh_9457342980" Date: Wed, 06 Jan 1999 11:46:40 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multipart MIME message. --==_Exmh_9457342980 Content-Type: text/plain; charset=us-ascii System: HP KAYAK XA, BX M/b, P-II 400, 64Mb, 1x4G on 1st IDE, CD-ROM on second IDE, matrox G200 AGP, 3-button+roller PS/2 intellimouse, funny HP keyboard (ps2-style connector), 3c905b, funny HP-supplied AZTECH ISA PnP soundcard that I can't quite get working. I have softupdates enabled in the kernel but not on the filesystems. I can cause the panic by enabling them on /usr/src, cd'ing to /usr/src/games, typing make, then alt-Fn around a bit. Usually fails within 20 seconds. Often, I can't get it to panic, and then fsck often finds 'unexpected softupdates inconsistency'and I get a fair amount of disk damage. Hence I'm not too keen to play with this too much! Disk has a slice from FreeBSD and a slice as yet unused. hellcat## disklabel wd0 # /dev/rwd0c: type: ESDI disk: wd0s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 240 sectors/cylinder: 15120 cylinders: 467 sectors/unit: 7076097 rpm: 3600 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] a: 65536 0 4.2BSD 0 0 0 # (Cyl. 0 - 4*) b: 281264 65536 swap # (Cyl. 4*- 22*) c: 7076097 0 unused 0 0 # (Cyl. 0 - 467*) e: 61440 346800 4.2BSD 0 0 0 # (Cyl. 22*- 26*) f: 2000000 408240 4.2BSD 0 0 0 # (Cyl. 27 - 159*) g: 4667857 2408240 4.2BSD 0 0 0 # (Cyl. 159*- 467*) hellcat## a = / b = swap e = /var f = /usr g = /usr/src (and /usr/ports via symlink) tmp on mfs /proc [yes, I know there's not enough swap space, not enough / or /var space. When the 3.0.1 CDs arrive I'll do it properly!] Config and Dmesg output attached. --==_Exmh_9457342980 Content-Type: text/plain ; name="dmsg"; charset=us-ascii Content-Description: dmsg Content-Disposition: attachment; filename="dmsg" Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #2: Tue Jan 5 18:07:29 EST 1999 root@:/usr/src/sys/compile/Hellcat Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 398270540 Hz CPU: Pentium II (quarter-micron) (398.27-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping=2 Features=0x183f9ff> real memory = 67108864 (65536K bytes) config> quit avail memory = 53542912 (52288K bytes) Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x02 on pci0.1.0 chip2: rev 0x02 on pci0.7.0 ide_pci0: rev 0x01 on pci0.7.1 chip3: rev 0x02 on pci0.7.3 xl0: <3Com 3c905B Fast Etherlink XL 10/100BaseTX> rev 0x00 int a irq 11 on pci0.17.0 xl0: Ethernet address: 00:10:5a:a9:84:33 xl0: autoneg complete, link status good (full-duplex, 100Mbps) Probing for devices on PCI bus 1: vga0: rev 0x01 int a irq 9 on pci1.0.0 Probing for PnP devices: CSN 1 Vendor ID: AZT1008 [0x08105407] Serial 0xffffffff Comp ID: @@@0000 [0x00000000] Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <4 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 at 0x60-0x64 irq 12 on motherboard psm0: model MouseMan+, device ID 0 pcm0 at 0x220 irq 10 drq 1 on isa Unknown card 0x0 0x0 -- hope it is SBPRO fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 4104MB (8405775 sectors), 8895 cyls, 15 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, accel, ovlap, dma, iordis acd0: drive speed 5512KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA, packet track acd0: Audio: play, 16 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked npx0 on motherboard npx0: INT 16 interface joy0 at 0x201 on isa joy0: joystick changing root device to wd0s1a --==_Exmh_9457342980 Content-Type: text/plain ; name="Hellcat"; charset=us-ascii Content-Description: Hellcat Content-Disposition: attachment; filename="Hellcat" # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # For more information read the handbook part System Administration -> # Configuring the FreeBSD Kernel -> The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id: GENERIC,v 1.125 1998/10/16 01:30:11 obrien Exp $ machine "i386" cpu "I686_CPU" ident Hellcat maxusers 32 options "NO_F00F_HACK" # Got a read P2!! #options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem #options MFS_ROOT #MFS usable as root device, "MFS" req'ed options NFS #Network Filesystem #options NFS_ROOT #NFS usable as root device, "NFS" req'ed options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options "CD9660_ROOT" #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options SOFTUPDATES config kernel root on wd0 controller isa0 #controller eisa0 controller pci0 controller pnp0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 #disk fd1 at fdc0 drive 1 # Unless you know very well what you're doing, leave ft0 at drive 2, or # remove the line entirely if you don't need it. Trying to configure # it on another unit might cause surprises, see PR kern/7176. #tape ft0 at fdc0 drive 2 options "CMD640" # work around CMD640 chip deficiency controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 #disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 vector wdintr #disk wd2 at wdc1 drive 0 #disk wd3 at wdc1 drive 1 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM device acd0 #IDE CD-ROM #device wfd0 #IDE Floppy (e.g. LS-120) # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" conflicts tty irq 1 vector scintr options MAXCONS=4 device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr #device sio2 at isa? disable port "IO_COM3" tty irq 5 vector siointr #device sio3 at isa? disable port "IO_COM4" tty irq 9 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. device xl0 pseudo-device loop pseudo-device ether #pseudo-device sl 1 #pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 64 pseudo-device gzip # Exec gzipped a.out's # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing # This provides support for System V shared memory. # (used for XF86 server) options SYSVSHM # The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. pseudo-device bpfilter 4 #Berkeley packet filter #device pcm0 at isa? port 0x530 tty irq 5 drq 0 flags 0x13 vector pcmintr device pcm0 at isa? port 0x220 tty irq 10 drq 1 flags 0x0 vector pcmintr # joy: joystick device joy0 at isa? port "IO_GAME" # Track down the keyboard error! options DDB --==_Exmh_9457342980-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 17:09:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17028 for freebsd-current-outgoing; Tue, 5 Jan 1999 17:09:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ogurok.com (ogurok.com [208.212.72.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17022 for ; Tue, 5 Jan 1999 17:08:57 -0800 (PST) (envelope-from oleg@ogurok.com) Received: from localhost (oleg@localhost) by ogurok.com (8.9.1/8.9.1) with ESMTP id UAA28598 for ; Tue, 5 Jan 1999 20:18:19 -0500 (EST) (envelope-from oleg@ogurok.com) Date: Tue, 5 Jan 1999 20:18:19 -0500 (EST) From: Oleg Ogurok To: current@FreeBSD.ORG Subject: cannot load any lkm with ELF 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 Hi all. I am running CURRENT, compiled ELF kernel, and now I can't load any of LKMs. ------- su-2.02# modload star_saver_mod.o ld: /kernel: malformed input file (not rel or archive) modload: /usr/bin/ld: return code 1 ------- The same error I'm getting while booting up. When I do "modstat" I don't see any modules loaded. Oleg Ogurok oleg@ogurok.com http://www.ogurok.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 17:27:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA19784 for freebsd-current-outgoing; Tue, 5 Jan 1999 17:27:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kate.nws.fsu.edu (kate.nws.fsu.edu [146.201.16.80]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA19779 for ; Tue, 5 Jan 1999 17:27:03 -0800 (PST) (envelope-from dave@nws.fsu.edu) Received: from localhost (dave@localhost) by kate.nws.fsu.edu (8.9.1/8.9.1) with SMTP id UAA25918; Tue, 5 Jan 1999 20:26:39 -0500 (EST) Date: Tue, 5 Jan 1999 20:26:39 -0500 (EST) From: David Faciane To: current@FreeBSD.ORG, Richard Solly Subject: Re: Panic: Changing default root with the elf loader/kernel In-Reply-To: <369166ce.6856128@smtp.melbpc.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 5 Jan 1999, Richard Solly wrote: > Following the helpful discussions recently, I converted my > recent 3.0 kernel which I thought was elf (but in fact was > aout) to genuine elf. Installed the boot loader OK as per > Robert Nordier's helpful instructions and booted the > kernel. > > Now one big problem, the boot disk is in fact the 2nd scsi > disk (da1) (as well as an IDE disk). It boots OK from what > in fact is the 3rd disk, but root always defaults back to > the first scsi (da0) and of course the kernel panics when it > can't find root. > > The perturbation which resulted in a default root change > with the aout loader/kernel, 2:da(1,a)kernel, is rejected > by the new loader. > [snippage] You need to set num_ide_disks. Here is my /boot/boot.conf (for booting FreeBSD off the 2nd disk (which is the 1st SCSI disk, da0). set num_ide_disks=1 autoboot 3 set no_autoboot=1 That will also handle your requirement for autoboot. HTH David Faciane |web: http://www.nws.fsu.edu/ NOAA National Weather Service |Real-Time Worldwide Marine Weather Reports Tallahassee, FL | http://www.nws.fsu.edu/buoy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 17:30:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA20356 for freebsd-current-outgoing; Tue, 5 Jan 1999 17:30:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA20323 for ; Tue, 5 Jan 1999 17:30:01 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id CAA13904 for freebsd-current@FreeBSD.ORG; Wed, 6 Jan 1999 02:29:13 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id E6A771728; Wed, 6 Jan 1999 02:04:46 +0100 (CET) Date: Wed, 6 Jan 1999 02:04:46 +0100 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: News Server Message-ID: <19990106020446.A44757@keltia.freenix.fr> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <20827.915563507@critter.freebsd.dk> <6309.915563659@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <6309.915563659@zippy.cdrom.com>; from Jordan K. Hubbard on Tue, Jan 05, 1999 at 11:14:19AM -0800 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4931 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Jordan K. Hubbard: > Because I believe that requires buy-in by the backbone cabal, and > who wants to spend 3 weeks mud-wrestling with Joel Furr? :-) This is not mandatory. We could establish a network of news sites carrying freebsd.*. Anyway, if someone has access to a Sprint-fed server, the muc.* private (ha!) hierarchy contains the freebsd mailing-lists and is distributed almost everywhere... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #67: Tue Dec 29 20:24:02 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 17:45:43 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA22241 for freebsd-current-outgoing; Tue, 5 Jan 1999 17:45:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alushta.NL.net (alushta.NL.net [193.78.240.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA22236 for ; Tue, 5 Jan 1999 17:45:41 -0800 (PST) (envelope-from benst@terminus.stuyts.nl) Received: from stuyts by alushta.NL.net with UUCP id <5560-23342>; Wed, 6 Jan 1999 02:45:05 +0100 Received: from daneel.stuyts.nl (daneel.stuyts.nl [193.78.231.7]) by terminus.stuyts.nl (8.9.1/8.9.1) with ESMTP id BAA00361; Wed, 6 Jan 1999 01:46:27 +0100 (MET) (envelope-from benst) Received: (from benst@localhost) by daneel.stuyts.nl (8.8.5/8.8.5) id BAA08041; Wed, 6 Jan 1999 01:46:24 +0100 (MET) Message-Id: <199901060046.BAA08041@daneel.stuyts.nl> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 3.3 v118.2) In-Reply-To: <199901052317.PAA01625@dingo.cdrom.com> X-Nextstep-Mailer: Mail 3.3 (Enhance 1.2) Received: by NeXT.Mailer (1.118.2) From: Ben Stuyts Date: Wed, 6 Jan 99 01:46:22 +0100 To: Mike Smith Subject: Re: Trouble booting from WinNT with new boot loader cc: current@FreeBSD.ORG Reply-To: ben@stuyts.nl References: <199901052317.PAA01625@dingo.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 05 Jan 1999, Mike Smith wrote: > > This is a Gigabyte 586DX with dual P166MMX, 64 meg ram, one IDE drive and 2 > > scsi drives. WinNT is installed on the IDE drive. FreeBSD is installed on > da0 > (/) and da1 using the onboard scsi controller. > > You need "set num_ide_disks=1" in /boot/boot.conf; you can also break > to the loader commandline and issue the command directly to test it out > first. Wonderful! Thanks Mike, it works now. Are there any more options like this? I can't seem to find the documentation about this. (man loader?) Thanks, Ben To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 17:46:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA22408 for freebsd-current-outgoing; Tue, 5 Jan 1999 17:46:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from eterna.binary.net (eterna.binary.net [12.13.120.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA22366 for ; Tue, 5 Jan 1999 17:46:01 -0800 (PST) (envelope-from nathan@rtfm.net) Received: from matrix.binary.net (nathan@matrix.binary.net [12.13.120.2]) by eterna.binary.net (8.9.1a/8.9.1) with ESMTP id TAA17845; Tue, 5 Jan 1999 19:45:33 -0600 (CST) Received: (from nathan@localhost) by matrix.binary.net (8.9.1a/8.9.1) id TAA19137; Tue, 5 Jan 1999 19:45:32 -0600 (CST) Message-ID: <19990105204532.C16219@rtfm.net> Date: Tue, 5 Jan 1999 20:45:32 -0500 From: Nathan Dorfman To: "Chris D. Faulhaber" , current@FreeBSD.ORG Subject: Re: i386/conf/PCCARD References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Chris D. Faulhaber on Tue, Jan 05, 1999 at 07:06:59PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 05, 1999 at 07:06:59PM -0500, Chris D. Faulhaber wrote: > On 5 Jan 1999, Robert V. Baron wrote: > > > > > I've been wondering, of late, how well/if laptops are supported in > > -current. It seems that the configuration, PCCARD, has recently > > (since mid December) has gone away. Is this the answer? > > > I've been running 3.0-CURRENT on my laptop since 3.0-RELEASE came out > without any problems. Now that you mention it, PCCARD is gone; but I've > been updating my current config since -RELEASE. > > So far, no problems have arisen; apm support is there, XFree86-3.3.3 > supports the NeoMagic chipsets (standard in many models), and as long as > your pcmcia chipset/cards are supported by default, everything should work > ok. > > -Chris 3.0's pcic0 driver doesn't seem to like my PCCARD controller. At all. I get all sorts of problems with it like inserting a card will hang the machine (with the slot access light on) until I eject the card, at which point the driver attach will fail and the machine will resume working fine. There's also no way to tell it which IRQs to use or not to use. I snagged the pao3 sources via cvs from jaz.jp.freebsd.org, and have been running fine with PAO on 3.0-R since then. However, this sticks me at 3.0-R, something I'm not happy at all about. If anyone workong on the pcic code is hearing me, this is dmesg output (with PAO3 kernel): pcic0: rev 0x02 int a irq 9 on pci0.19.0 pcic1: rev 0x02 int b irq 9 on pci0.19.1 pcic0 at 0x3e0-0x3e1 irq 9 on isa pcic0: slot 0 controller I/O address 0x3e0 pcic0: slot 1 controller I/O address 0x3e0 IRQ 09 is what 'doze assigns to the controller as well (and 11 to the NIC card, a combination which works great under FreeBSD). PAO tries to assign 11 by default to the controller but I can change it to 9 so I can set the card to 11 (I can't change this value with 3.0-R's pcic). 3.0-R's pcic tries to assign it values like 3 or 5, does this matter? Anyway, plenty of other people have said that their PCMCIA works fine with -current, so I'm assumming it must be something with support for my controller. Anyone have any ideas? I really hate to be tied to -RELEASE because of PAO. > All the true gurus I've met never claimed they were one, and always > pointed to someone better. > -Anonymous > -- ________________ ___________________________________________ / Nathan Dorfman \ / "`IE4 brings the web to UNIX'? *laughing* / nathan@rtfm.net \/ Isn't that similar to Ronald McDonald bringing / finger for PGP key \ religion to the pope?" -Jamie Bowden To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 17:47:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA22541 for freebsd-current-outgoing; Tue, 5 Jan 1999 17:47:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from speck.ml.org (cx19313-a.nwptn1.va.home.com [24.2.49.151]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA22535 for ; Tue, 5 Jan 1999 17:47:30 -0800 (PST) (envelope-from jedgar@speck.ml.org) Received: from anthrax.speck (jedgar@anthrax.speck [192.168.2.23]) by speck.ml.org (8.9.1/8.9.1) with ESMTP id UAA07697 for ; Tue, 5 Jan 1999 20:46:53 -0500 (EST) (envelope-from jedgar@speck.ml.org) Date: Tue, 5 Jan 1999 20:46:53 -0500 (EST) From: "Chris D. Faulhaber" X-Sender: jedgar@anthrax.speck To: current@FreeBSD.ORG Subject: Re: cannot load any lkm with ELF kernel In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 5 Jan 1999, Oleg Ogurok wrote: > Hi all. > Hi :) > I am running CURRENT, compiled ELF kernel, and now I can't load any of > LKMs. > ------- > su-2.02# modload star_saver_mod.o > ld: /kernel: malformed input file (not rel or archive) > modload: /usr/bin/ld: return code 1 > ------- > The same error I'm getting while booting up. When I do "modstat" I don't > see any modules loaded. > That would be because (correct me if I'm wrong) lkm's are a.out. With an elf kernel, use dynamically-linkable modules (kld's) located in /modules. man kldload/kldunload/kldstat for usage. -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 18:28:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA26948 for freebsd-current-outgoing; Tue, 5 Jan 1999 18:28:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA26942 for ; Tue, 5 Jan 1999 18:28:38 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id SAA16325; Tue, 5 Jan 1999 18:28:06 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id SAA29116; Tue, 5 Jan 1999 18:28:04 -0800 (PST) (envelope-from jdp@polstra.com) Date: Tue, 5 Jan 1999 18:28:04 -0800 (PST) Message-Id: <199901060228.SAA29116@vashon.polstra.com> To: tomdean@ix.netcom.com Subject: Re: elf make world Success Newsgroups: polstra.freebsd.current In-Reply-To: <199901050620.WAA04878@ix.netcom.com> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199901050620.WAA04878@ix.netcom.com>, Thomas Dean wrote: > > When I first installed FreeBSD, I think version 0.1, I had a 10MB > disk that was 50% full. Now, I have a 3GB disk that is 90% full! But I bet your 3GB disk cost you less than the 10MB disk. :-) John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 18:50:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA28955 for freebsd-current-outgoing; Tue, 5 Jan 1999 18:50:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oldnews.quick.net ([207.212.170.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA28863 for ; Tue, 5 Jan 1999 18:49:52 -0800 (PST) (envelope-from donegan@oldnews.quick.net) Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id SAA14187; Tue, 5 Jan 1999 18:49:17 -0800 (PST) Date: Tue, 5 Jan 1999 18:49:17 -0800 (PST) From: "Steven P. Donegan" To: current@FreeBSD.ORG Subject: Elf Conversion Message-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, I did the stated elf upgrade: cvsup from today make aout-to-elf-build (no errors) make aout-to-elf-install (no errors) reboot startx now results in: ld.so failed: Can't find shared library "libXmu.so.6.0" Since X is kind of important to me any pointers on what to do next? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 18:56:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA29678 for freebsd-current-outgoing; Tue, 5 Jan 1999 18:56:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from netcom1.netcom.com (lax-ca66-06.ix.netcom.com [207.223.161.70]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA29671 for ; Tue, 5 Jan 1999 18:56:16 -0800 (PST) (envelope-from mvh@ix.netcom.com) Received: (from mvh@localhost) by netcom1.netcom.com (8.9.1/8.9.1) id SAA14371; Tue, 5 Jan 1999 18:54:30 -0800 (PST) (envelope-from mvh) Date: Tue, 5 Jan 1999 18:54:30 -0800 (PST) From: "Michael V. Harding" Message-Id: <199901060254.SAA14371@netcom1.netcom.com> To: donegan@quick.net CC: current@FreeBSD.ORG In-reply-to: (donegan@quick.net) Subject: Re: Elf Conversion References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The install hid your old a.out shared libraries - you should run 'mergemaster' or equivalent to update your /etc/rc stuff so that they can be found in their new locations. Date: Tue, 5 Jan 1999 18:49:17 -0800 (PST) From: "Steven P. Donegan" Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-RULES: lists OK, I did the stated elf upgrade: cvsup from today make aout-to-elf-build (no errors) make aout-to-elf-install (no errors) reboot startx now results in: ld.so failed: Can't find shared library "libXmu.so.6.0" Since X is kind of important to me any pointers on what to do next? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 19:03:16 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA00687 for freebsd-current-outgoing; Tue, 5 Jan 1999 19:03:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa15-59.ix.netcom.com [207.93.148.59]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA00681 for ; Tue, 5 Jan 1999 19:03:13 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.1/8.8.8) id TAA89361; Tue, 5 Jan 1999 19:01:53 -0800 (PST) (envelope-from tomdean) Date: Tue, 5 Jan 1999 19:01:53 -0800 (PST) Message-Id: <199901060301.TAA89361@ix.netcom.com> From: Thomas Dean To: jdp@polstra.com CC: current@FreeBSD.ORG In-reply-to: <199901060228.SAA29116@vashon.polstra.com> (message from John Polstra on Tue, 5 Jan 1999 18:28:04 -0800 (PST)) Subject: Re: elf make world Success Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, about half, if memory serves. tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 19:05:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA01124 for freebsd-current-outgoing; Tue, 5 Jan 1999 19:05:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA01114 for ; Tue, 5 Jan 1999 19:05:33 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id TAA16436; Tue, 5 Jan 1999 19:04:26 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id TAA36807; Tue, 5 Jan 1999 19:04:23 -0800 (PST) (envelope-from jdp@polstra.com) Date: Tue, 5 Jan 1999 19:04:23 -0800 (PST) Message-Id: <199901060304.TAA36807@vashon.polstra.com> To: hgoldste@bbs.mpcs.com Subject: Re: ELF interpreter /usr/lib/libc.so.1 not found (on 3.0-CURRENT 12/20/98) Newsgroups: polstra.freebsd.hackers In-Reply-To: <13962.6777.503181.771874@penny.south.mpcs.com> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <13962.6777.503181.771874@penny.south.mpcs.com>, Howard Goldstein wrote: > > My own program seems to be calling for a shared library I didn't link > it against, at runtime. I don't recall having this happen when > running everything through cc, but alas I don't have that option since > one of the modules had to be ported from masm to nasm, so here I am.... > > > slice:~/src/develop$ ./v2show > ELF interpreter /usr/lib/libc.so.1 not found > Abort trap Add "-dynamic-linker /usr/libexec/ld-elf.so.1" to your "ld" command. The "ELF interpreter" is the dynamic linker that the kernel is trying to load. Its pathname defaults (in the linker) to "/usr/lib/libc.so.1", which is the old SVR4 version. This must be overridden on the linker command line. "cc" automatically does that. You really should try to use "cc" for linking, because there's lots of non-obvious stuff that needs to go onto the command line for "ld". Take some simple program "hello.c", and do this: cc -v hello.c You'll see the generated linker command at the end. It's pretty complicated. I don't understand why your masm/nasm problem would affect linking. The linker only deals with object files, not with assembly language sources. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 19:13:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA01856 for freebsd-current-outgoing; Tue, 5 Jan 1999 19:13:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA01849; Tue, 5 Jan 1999 19:12:58 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:sfjEyRaJWM3Mm4JJd/6DjQzMgz+JEqdt@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id MAA14345; Wed, 6 Jan 1999 12:12:29 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id MAA27736; Wed, 6 Jan 1999 12:14:51 +0900 (JST) Message-Id: <199901060314.MAA27736@zodiac.mech.utsunomiya-u.ac.jp> To: sos@FreeBSD.ORG, msmith@FreeBSD.ORG cc: current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: syscons update - when? Date: Wed, 06 Jan 1999 12:14:45 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I announced before, reorganization of syscons code is under way and I intend to commit changes in three stages. Stage 1: keyboard driver split Stage 2: video driver split, splash screen Stage 3: other reorganization The new code has been running on my -current box for quite a while. Now, -stable branch date is coming up. The question is how much change we should commit before the branch? We can defer commit after the branch and later backport the new code from -current to -stable. However, there is a snug. At stage 1 and 2, the users will be forced to change their kernel configuration files because keyboard and video drivers become separate from syscons. Such change is probably too much, if suddenly introduced to -stable well after the branch. So, probably our options are: a) Commit stage 1 and 2 changes now. Stage 3 changes may be backported to -stable from -current later. b) Don't commit any changes now, but commit them to -current after the branch. Don't backport the changes to -stable at all. When the next branch (3.1-STABLE?) comes, let it have the new code. I prefer the option a). But, I have to expect rough ride after commits, as changes of this scale will have many initial glitches... What do you think? Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 19:16:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02199 for freebsd-current-outgoing; Tue, 5 Jan 1999 19:16:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa15-59.ix.netcom.com [207.93.148.59]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02194 for ; Tue, 5 Jan 1999 19:16:57 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.1/8.8.8) id TAA89443; Tue, 5 Jan 1999 19:15:23 -0800 (PST) (envelope-from tomdean) Date: Tue, 5 Jan 1999 19:15:23 -0800 (PST) Message-Id: <199901060315.TAA89443@ix.netcom.com> From: Thomas Dean To: donegan@quick.net CC: current@FreeBSD.ORG In-reply-to: (donegan@quick.net) Subject: Re: Elf Conversion Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Look at the rc* files in /usr/src/etc. These are updates to the /etc/rc* files. You should NOT just copy the files from /usr/src/etc to /etc. There are some tools on the web to merge the files. The /etc/rc files are VERY critical to starting and using your system. I prefer to manually merge the files, using diff and an editor. Now, to your problem. The shared libraries are located via ldconfig hints. Look at ldconfig in /usr/src/etc/rc.conf. in /etc/rc, the hints are set with 'ldconfig -R '. In my /etc/rc*, ldconfig_path is set in rc.conf. These words are conditionally transferred to LDC in rc. LDC is used to set the hints. To get started, you can do this manually, as root. You can view the hints with 'ldconfig -r'. tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 19:21:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02669 for freebsd-current-outgoing; Tue, 5 Jan 1999 19:21:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02653 for ; Tue, 5 Jan 1999 19:21:42 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:0iuLNYLmUAKFARrJRXaN/VZXWVfGVtMP@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id MAA14822; Wed, 6 Jan 1999 12:21:14 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id MAA28132; Wed, 6 Jan 1999 12:23:35 +0900 (JST) Message-Id: <199901060323.MAA28132@zodiac.mech.utsunomiya-u.ac.jp> To: current@FreeBSD.ORG cc: nick.hibma@jrc.it, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Request for a char device major number Date: Wed, 06 Jan 1999 12:23:34 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I need one CDEV major number for the keyboard driver (kbd). Both the AT keyboard and the USB keyboard will use the same major number. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 19:30:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA03906 for freebsd-current-outgoing; Tue, 5 Jan 1999 19:30:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from buffy.tpgi.com.au (buffy.tpgi.com.au [203.12.160.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA03901 for ; Tue, 5 Jan 1999 19:30:03 -0800 (PST) (envelope-from eirvine@tpgi.com.au) Received: (from smtpd@localhost) by buffy.tpgi.com.au (8.8.7/8.8.7) id OAA06239 for ; Wed, 6 Jan 1999 14:32:36 +1100 Received: from kmidc71-142.ecopost.com.au(203.28.71.142), claiming to be "tpgi.com.au" via SMTP by buffy.tpgi.com.au, id smtpda06185; Wed Jan 6 14:32:29 1999 Message-ID: <3692D945.5A09B394@tpgi.com.au> Date: Wed, 06 Jan 1999 14:32:21 +1100 From: Eddie Irvine X-Mailer: Mozilla 4.03 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Installed 3.0 CD. Flag day? 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 installed the 3.0 CD. I've done a few recent cvsup's and make worlds, and will continue to do so. I've built a custom kernel and will continue to do so. It seems to me that everything apart from the kernel is in elf format. So, does this mean I don't need to do the "a.out to elf upgrade"? How about the kernel? How about the bootblocks? Will I need to do a disklabel -B $SLICE ?? Eddie. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 19:54:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA06064 for freebsd-current-outgoing; Tue, 5 Jan 1999 19:54:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sicily.odyssey.cs.cmu.edu (SICILY.ODYSSEY.CS.CMU.EDU [128.2.185.138]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA06055 for ; Tue, 5 Jan 1999 19:54:24 -0800 (PST) (envelope-from rvb+@sicily.odyssey.cs.cmu.edu) To: Julian Elischer Cc: "Robert V. Baron" , current@FreeBSD.ORG Subject: Re: building boot References: From: "Robert V. Baron" Date: 05 Jan 1999 22:53:08 -0500 In-Reply-To: Julian Elischer's message of Tue, 5 Jan 1999 16:07:30 -0800 (PST) Message-ID: Lines: 35 X-Mailer: Gnus v5.4.46/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer writes: > you may need to do "make includes" > in /usr/src Well yes, that does work. But in fact, building the kernel also failed because of the same __int stuff. I didn't analyze what was wrong before I did the make includes. It was very early in the the *aic* related code. My model of bootstrapping says you build a new kernel first, with compatability on for the old kernel features. Then you boot it; then you build/install the new app environment. The forced make includes before the kernel build seems out of place. (Especially since I might want a new kernel but not new apps and installing new includes would be the wrong thing to do. > > > On 5 Jan 1999, Robert V. Baron wrote: > > > > > I recently pulled down a new src/sys and tried to build boot. This > > did not work too well, because the app environment and includes files > > were a month old. Basically, the machine/ansi.h was missing the __int > > typedefs. So should boot/ be treated like the kernel and just use > > kernel relative headers or should it be like any old user program and > > just depend on /usr/include. Currently boot/ does both. It can > > pull in things from sys/sys relative to the the kernel src. But > > it also tries to get things relative to machine -- which is not > > otherwise defined so it pulls from /usr/include/machine. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 20:12:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA07770 for freebsd-current-outgoing; Tue, 5 Jan 1999 20:12:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from superior.mooseriver.com (ip55244.transbay.net [209.133.55.244]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA07765 for ; Tue, 5 Jan 1999 20:12:12 -0800 (PST) (envelope-from jgrosch@superior.mooseriver.com) Received: (from jgrosch@localhost) by superior.mooseriver.com (8.8.8/8.8.8) id UAA11633; Tue, 5 Jan 1999 20:08:18 -0800 (PST) (envelope-from jgrosch) Message-ID: <19990105200817.A11603@mooseriver.com> Date: Tue, 5 Jan 1999 20:08:17 -0800 From: Josef Grosch To: "Jordan K. Hubbard" , Poul-Henning Kamp Cc: Jason George , freebsd-current@FreeBSD.ORG Subject: Re: News Server Reply-To: jgrosch@mooseriver.com References: <20827.915563507@critter.freebsd.dk> <6309.915563659@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <6309.915563659@zippy.cdrom.com>; from Jordan K. Hubbard on Tue, Jan 05, 1999 at 11:14:19AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 05, 1999 at 11:14:19AM -0800, Jordan K. Hubbard wrote: > > But why don't we just create a > > freebsd.* > > hierachy for selective and elective distribution ? > > Because I believe that requires buy-in by the backbone cabal, and > who wants to spend 3 weeks mud-wrestling with Joel Furr? :-) Only if it involves lampreys and lemurs ;-) Josef -- Josef Grosch | Another day closer to a | FreeBSD 3.0 jgrosch@MooseRiver.com | Micro$oft free world | UNIX for the masses To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 20:30:59 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA10273 for freebsd-current-outgoing; Tue, 5 Jan 1999 20:30:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from daphne.bogus (dialup8.black-hole.com [206.145.13.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA09803 for ; Tue, 5 Jan 1999 20:27:34 -0800 (PST) (envelope-from hank@black-hole.com) Received: from localhost (hank@localhost) by daphne.bogus (8.9.1/8.8.8) with SMTP id XAA04496; Tue, 5 Jan 1999 23:00:33 -0600 (CST) (envelope-from hank@black-hole.com) X-Authentication-Warning: daphne.bogus: hank owned process doing -bs Date: Tue, 5 Jan 1999 23:00:33 -0600 (CST) From: Henry Miller X-Sender: hank@daphne.bogus To: "Jordan K. Hubbard" cc: Poul-Henning Kamp , Jason George , freebsd-current@FreeBSD.ORG Subject: Re: News Server In-Reply-To: <6432.915565290@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 5 Jan 1999, Jordan K. Hubbard wrote: > > I don't really see the need, people can pick it up someplace > > and if they don't want it they can say no. > > Yeah, but Joel will send out rmgroup messages to all and sundry for > anything which doesn't meet his (prior) approval. right, but I thought the point of this was a private news system not connected to USENET. In that light, if anyone connects to usenet, and probagates the freebsd.* groups they should get an rmgroup. Of course the servers want won't honor the rmgroup, but the rest of USENET will. Connecting to USENET opens everything up to spammers. If they refuse to propagate our groups, that is good for us. (I'm not trying to say that USENET is bad, but for those who want it stick to comp.os.freebsd or whatever it is called now) -- http://blugill.home.ml.org/ hank@black-hole.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 20:44:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA11365 for freebsd-current-outgoing; Tue, 5 Jan 1999 20:44:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oldnews.quick.net ([207.212.170.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA11355 for ; Tue, 5 Jan 1999 20:44:40 -0800 (PST) (envelope-from donegan@oldnews.quick.net) Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id UAA14394; Tue, 5 Jan 1999 20:43:13 -0800 (PST) Date: Tue, 5 Jan 1999 20:43:13 -0800 (PST) From: "Steven P. Donegan" To: Eddie Irvine cc: freebsd-current@FreeBSD.ORG Subject: Re: Installed 3.0 CD. Flag day? In-Reply-To: <3692D945.5A09B394@tpgi.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 6 Jan 1999, Eddie Irvine wrote: > I've installed the 3.0 CD. > I've done a few recent cvsup's and make worlds, > and will continue to do so. > I've built a custom kernel and will continue to > do so. > > It seems to me that everything apart from the kernel is > in elf format. > > So, does this mean I don't need to do the "a.out to elf upgrade"? > I did a full aout to elf conversion - at this moment I'm replying to this email from a BSDI UNIX system - the conversion totally trashed my system - many drivers died (ethernet de0 was the killer). Based on past experience I think I'll just snarf a current floppy set and install from the net over my old system. As it's a development system it's not a biggie - but it is annoying. I use it as my very fast X terminal :-) In short - no matter how much push is on to do the elf conversion - advance at your own risk - I personally don't sweat my toy SMP system being down - no biggie - it's an acceptable risk for experimentation - but if you have any intent that your system will be available - well you are taking big risks at present. BTW - mergemaster really caused fun here. It's only a 1 user system beyond root - and it trashed passwd, group etc. Not that it matters to me - I'm just going to rebuild from clean partitions - but others would probably be unhappy :-| Ah well - who cares - it's just techy play anyway :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 21:09:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA14209 for freebsd-current-outgoing; Tue, 5 Jan 1999 21:09:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gongshow.masterplan.org (masterplan.powersurfr.com [24.108.38.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA14204 for ; Tue, 5 Jan 1999 21:09:34 -0800 (PST) (envelope-from jbg@masterplan.org) Received: from infomat (infomat [192.168.4.2]) by gongshow.masterplan.org (8.8.8/8.8.8) with SMTP id WAA18232 for ; Tue, 5 Jan 1999 22:09:02 -0700 (MST) (envelope-from jbg@masterplan.org) Message-Id: <199901060509.WAA18232@gongshow.masterplan.org> From: jbg@masterplan.org (Jason George) To: freebsd-current@FreeBSD.ORG Subject: Re: News Server Organization: The Master Plan Always Fails... Date: Wed, 06 Jan 1999 05:09:04 GMT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Because I believe that requires buy-in by the backbone cabal, and >> who wants to spend 3 weeks mud-wrestling with Joel Furr? :-) > >This is not mandatory. We could establish a network of news sites carrying >freebsd.*. Anyway, if someone has access to a Sprint-fed server, the muc.* >private (ha!) hierarchy contains the freebsd mailing-lists and is >distributed almost everywhere... Well, my upstream is Supernews/Remarq, so I figure that they should have a pretty comprehensive feedstock, being a commercial Usenet provider. Here's all I can get from them: muc.lists.freebsd.bugs muc.lists.freebsd.commit muc.lists.freebsd.current muc.lists.freebsd.hackers muc.lists.freebsd.hardware muc.lists.freebsd.isp muc.lists.freebsd.security I am using a sed script to munge the Newsgroups: line so I can pipe the muc.lists.freebsd.* in to my list.freebsd.* groups. The propagation of these lists seems spotty at best. I've only ever been able to get a handful of articles per day. My attempt was at "filling in" any holes left by the mail2news script which, for one reason or another, was directing stuff into the bit bucket. I tried using the muc lists before I setup the gateway. Too bad the number of articles available causes the evaluation of the implementation to register at a Suck Factor of 9.5. ;-) --J To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 21:26:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA16356 for freebsd-current-outgoing; Tue, 5 Jan 1999 21:26:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA16344 for ; Tue, 5 Jan 1999 21:26:29 -0800 (PST) (envelope-from bwoods@cybcon.com) Received: from cybcon.com (bwoods@cybcon.com [205.147.64.49]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id VAA20877 for ; Tue, 5 Jan 1999 21:26:02 -0800 (PST) Date: Tue, 5 Jan 1999 21:26:01 -0800 (PST) From: Bill Woods To: current@FreeBSD.ORG Subject: kdesupport11 port build problems on -current elf Message-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 tried to compile the kdesupport11 port on a FreeBSD 3.0-current elf system today, and this is what I got, any ideas? -------------------------------------------------------------- /bin/sh ../libtool --mode=compile c++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/X11R6/include/X11/qt -O -pipe -c QwCluster.cpp c++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/X11R6/include/X11/qt -O -pipe -c -fPIC -DPIC QwCluster.cpp mv -f QwCluster.o QwCluster.lo c++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/X11R6/include/X11/qt -O -pipe -c QwCluster.cpp >/dev/null 2>&1 /bin/sh ../libtool --mode=link c++ -O -pipe -L/usr/X11R6/lib -o libQwSpriteField.la -rpath /usr/local/lib -version-info 5:2:4 -lqt -lX11 QwSpriteField.lo QwSpriteField-double.lo QwSpriteField-int.lo QwSpriteField-mobdouble.lo QwSpriteField-mobint.lo QwCluster.lo mkdir .libs c++ -shared -Wl,-soname -Wl,libQwSpriteField.so.5 -o .libs/libQwSpriteField.so.5 QwSpriteField.lo QwSpriteField-double.lo QwSpriteField-int.lo QwSpriteField-mobdouble.lo QwSpriteField-mobint.lo QwCluster.lo (cd .libs && ln -s libQwSpriteField.so.5 libQwSpriteField.so) ar cru .libs/libQwSpriteField.a QwSpriteField.o QwSpriteField-double.o QwSpriteField-int.o QwSpriteField-mobdouble.o QwSpriteField-mobint.o QwCluster.o ranlib .libs/libQwSpriteField.a creating libQwSpriteField.la (cd .libs && ln -s ../libQwSpriteField.la libQwSpriteField.la) c++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/X11R6/include/X11/qt -O -pipe -c example.cpp /bin/sh ../libtool --mode=link c++ -O -pipe -L/usr/X11R6/lib -o example example.o libQwSpriteField.la -lqt -lX11 c++ -O -pipe -L/usr/X11R6/lib -o .libs/example example.o -Wl,--rpath -Wl,/usr/local/lib .libs/libQwSpriteField.so -L/usr/X11R6/lib -lqt -lX11 -lqt -lX11 /usr/libexec/elf/ld: warning: libXext.so.6, needed by /usr/X11R6/lib/libqt.so, not found (try using --rpath) /usr/X11R6/lib/libqt.so: undefined reference to `XShapeCombineRegion' /usr/X11R6/lib/libqt.so: undefined reference to `XShapeCombineMask' *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop -------------------------------- Ideas please? Thanks, Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 21:26:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA16417 for freebsd-current-outgoing; Tue, 5 Jan 1999 21:26:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA16412 for ; Tue, 5 Jan 1999 21:26:51 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id VAA74024; Tue, 5 Jan 1999 21:25:52 -0800 (PST) To: Kazutaka YOKOTA cc: current@FreeBSD.ORG, nick.hibma@jrc.it Subject: Re: Request for a char device major number In-reply-to: Your message of "Wed, 06 Jan 1999 12:23:34 +0900." <199901060323.MAA28132@zodiac.mech.utsunomiya-u.ac.jp> Date: Tue, 05 Jan 1999 21:25:51 -0800 Message-ID: <74020.915600351@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Committers should just grab one for themselves - we don't mind. There's not really a FreeBSD Assigned Numbers Authority. :-) - Jordan > I need one CDEV major number for the keyboard driver (kbd). Both the > AT keyboard and the USB keyboard will use the same major number. > > Kazu > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 21:27:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA16482 for freebsd-current-outgoing; Tue, 5 Jan 1999 21:27:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa15-59.ix.netcom.com [207.93.148.59]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA16474 for ; Tue, 5 Jan 1999 21:27:25 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.1/8.8.8) id VAA89584; Tue, 5 Jan 1999 21:26:43 -0800 (PST) (envelope-from tomdean) Date: Tue, 5 Jan 1999 21:26:43 -0800 (PST) Message-Id: <199901060526.VAA89584@ix.netcom.com> From: Thomas Dean To: donegan@quick.net, freebsd-current@FreeBSD.ORG In-reply-to: (donegan@quick.net) Subject: Re: Installed 3.0 CD. Flag day? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The details of your installation, hardware and software before the conversion and the steps you took in the aout-to-elf conversion are interesting. Maybe a para on your hardware, a para on your pre-conversion software, and, three para's on what steps you took in the conversion and any error messages you saw. Did the 'make aout-to-elf' complete without error? What did you mean by '- many drivers died (ethernet de0 was the killer)'? Could this have been trashing /etc/rc* while using mergemaster? As I said in a different thread, I worry VERY MUCH about things that muck with the rc scripts. IMHO, by hand, ONLY! Can you preserve the rc* files before scribbling on the disk? Boot a floppy, mount the hard disk, and, look at /etc/rc*? If they are trashed, you may not have to do a new install. tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 21:32:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA17073 for freebsd-current-outgoing; Tue, 5 Jan 1999 21:32:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA17068 for ; Tue, 5 Jan 1999 21:32:30 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id AAA50867; Wed, 6 Jan 1999 00:36:17 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Wed, 6 Jan 1999 00:36:17 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Bill Woods cc: current@FreeBSD.ORG Subject: aout to ELF people: READ THIS!! Re: kdesupport11 port build problems on -current elf 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 Anyone who's done a recent aout-elf convertion should realize that they should be now generating ELF programs. If you want to compile X programs, recompile XFree86 as elf you need the libraries. If you are using 3rd party libraries and need new programs you will have to make sure the libraries that are depended on are recompiled and installed as ELF. thanks. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current On Tue, 5 Jan 1999, Bill Woods wrote: > > I tried to compile the kdesupport11 port on a FreeBSD 3.0-current elf > system today, and this is what I got, any ideas? > > -------------------------------------------------------------- > /bin/sh ../libtool --mode=compile c++ -DHAVE_CONFIG_H -I. -I. -I.. > -I/usr/X11R6/include/X11/qt -O -pipe -c QwCluster.cpp > c++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/X11R6/include/X11/qt -O -pipe -c > -fPIC -DPIC QwCluster.cpp > mv -f QwCluster.o QwCluster.lo > c++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/X11R6/include/X11/qt -O -pipe -c > QwCluster.cpp >/dev/null 2>&1 > /bin/sh ../libtool --mode=link c++ -O -pipe -L/usr/X11R6/lib -o > libQwSpriteField.la -rpath /usr/local/lib -version-info 5:2:4 -lqt -lX11 > QwSpriteField.lo QwSpriteField-double.lo QwSpriteField-int.lo > QwSpriteField-mobdouble.lo QwSpriteField-mobint.lo QwCluster.lo > mkdir .libs > c++ -shared -Wl,-soname -Wl,libQwSpriteField.so.5 -o > .libs/libQwSpriteField.so.5 QwSpriteField.lo QwSpriteField-double.lo > QwSpriteField-int.lo QwSpriteField-mobdouble.lo QwSpriteField-mobint.lo > QwCluster.lo > (cd .libs && ln -s libQwSpriteField.so.5 libQwSpriteField.so) > ar cru .libs/libQwSpriteField.a QwSpriteField.o QwSpriteField-double.o > QwSpriteField-int.o QwSpriteField-mobdouble.o QwSpriteField-mobint.o > QwCluster.o > ranlib .libs/libQwSpriteField.a > creating libQwSpriteField.la > (cd .libs && ln -s ../libQwSpriteField.la libQwSpriteField.la) > c++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/X11R6/include/X11/qt -O -pipe -c > example.cpp > /bin/sh ../libtool --mode=link c++ -O -pipe -L/usr/X11R6/lib -o example > example.o libQwSpriteField.la -lqt -lX11 > c++ -O -pipe -L/usr/X11R6/lib -o .libs/example example.o -Wl,--rpath > -Wl,/usr/local/lib .libs/libQwSpriteField.so -L/usr/X11R6/lib -lqt -lX11 > -lqt -lX11 > /usr/libexec/elf/ld: warning: libXext.so.6, needed by > /usr/X11R6/lib/libqt.so, not found (try using --rpath) > /usr/X11R6/lib/libqt.so: undefined reference to `XShapeCombineRegion' > /usr/X11R6/lib/libqt.so: undefined reference to `XShapeCombineMask' > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop > -------------------------------- > > Ideas please? > > Thanks, > > Bill > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 21:32:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA17224 for freebsd-current-outgoing; Tue, 5 Jan 1999 21:32:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dewdrop2.mindspring.com (dewdrop2.mindspring.com [207.69.200.82]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA17217 for ; Tue, 5 Jan 1999 21:32:48 -0800 (PST) (envelope-from stevensl@mindspring.net) Received: from freelove.mindspring.net (freelove.mindspring.net [207.69.192.92]) by dewdrop2.mindspring.com (8.8.5/8.8.5) with SMTP id AAA31419 for ; Wed, 6 Jan 1999 00:32:19 -0500 (EST) Date: Wed, 6 Jan 1999 00:32:47 -0500 (EST) From: steven To: current@FreeBSD.ORG Subject: Update: Re: So we're stuck with using timidity now? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well i cvsup'd my sources to the latest.. todays source. one of the files updated was indeed the swap_pager.c so i recompiled the kernel. Made sure i was using the right version of OSS, the "i" version still locks up... mpg123 seems to run fine, so does Fxtv. but the main reason for OSS is to get sound out of quake and use x11amp. So should i just get a real soundcard ;-) Steven S. 403forbidden.net "My Sister opened a computer store in Hawaii. She sells C shells down by the seashore." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 21:39:43 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA17717 for freebsd-current-outgoing; Tue, 5 Jan 1999 21:39:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA17710 for ; Tue, 5 Jan 1999 21:39:42 -0800 (PST) (envelope-from bwoods@cybcon.com) Received: from cybcon.com (bwoods@cybcon.com [205.147.64.49]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id VAA21620; Tue, 5 Jan 1999 21:39:13 -0800 (PST) Date: Tue, 5 Jan 1999 21:39:13 -0800 (PST) From: Bill Woods To: Alfred Perlstein cc: current@FreeBSD.ORG Subject: Re: aout to ELF people: READ THIS!! Re: kdesupport11 port build problems on -current elf 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 Ahh........I have re-compiled XFree as elf....so, what am I missing? On Wed, 6 Jan 1999, Alfred Perlstein wrote: > > Anyone who's done a recent aout-elf convertion should realize that they > should be now generating ELF programs. > > If you want to compile X programs, recompile XFree86 as elf you need the > libraries. If you are using 3rd party libraries and need new programs you > will have to make sure the libraries that are depended on are recompiled > and installed as ELF. > > thanks. > Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com > -- There are operating systems, and then there's FreeBSD. > -- http://www.freebsd.org/ 3.0-current > > On Tue, 5 Jan 1999, Bill Woods wrote: > > > > > I tried to compile the kdesupport11 port on a FreeBSD 3.0-current elf > > system today, and this is what I got, any ideas? > > > > -------------------------------------------------------------- > > /bin/sh ../libtool --mode=compile c++ -DHAVE_CONFIG_H -I. -I. -I.. > > -I/usr/X11R6/include/X11/qt -O -pipe -c QwCluster.cpp > > c++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/X11R6/include/X11/qt -O -pipe -c > > -fPIC -DPIC QwCluster.cpp > > mv -f QwCluster.o QwCluster.lo > > c++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/X11R6/include/X11/qt -O -pipe -c > > QwCluster.cpp >/dev/null 2>&1 > > /bin/sh ../libtool --mode=link c++ -O -pipe -L/usr/X11R6/lib -o > > libQwSpriteField.la -rpath /usr/local/lib -version-info 5:2:4 -lqt -lX11 > > QwSpriteField.lo QwSpriteField-double.lo QwSpriteField-int.lo > > QwSpriteField-mobdouble.lo QwSpriteField-mobint.lo QwCluster.lo > > mkdir .libs > > c++ -shared -Wl,-soname -Wl,libQwSpriteField.so.5 -o > > .libs/libQwSpriteField.so.5 QwSpriteField.lo QwSpriteField-double.lo > > QwSpriteField-int.lo QwSpriteField-mobdouble.lo QwSpriteField-mobint.lo > > QwCluster.lo > > (cd .libs && ln -s libQwSpriteField.so.5 libQwSpriteField.so) > > ar cru .libs/libQwSpriteField.a QwSpriteField.o QwSpriteField-double.o > > QwSpriteField-int.o QwSpriteField-mobdouble.o QwSpriteField-mobint.o > > QwCluster.o > > ranlib .libs/libQwSpriteField.a > > creating libQwSpriteField.la > > (cd .libs && ln -s ../libQwSpriteField.la libQwSpriteField.la) > > c++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/X11R6/include/X11/qt -O -pipe -c > > example.cpp > > /bin/sh ../libtool --mode=link c++ -O -pipe -L/usr/X11R6/lib -o example > > example.o libQwSpriteField.la -lqt -lX11 > > c++ -O -pipe -L/usr/X11R6/lib -o .libs/example example.o -Wl,--rpath > > -Wl,/usr/local/lib .libs/libQwSpriteField.so -L/usr/X11R6/lib -lqt -lX11 > > -lqt -lX11 > > /usr/libexec/elf/ld: warning: libXext.so.6, needed by > > /usr/X11R6/lib/libqt.so, not found (try using --rpath) > > /usr/X11R6/lib/libqt.so: undefined reference to `XShapeCombineRegion' > > /usr/X11R6/lib/libqt.so: undefined reference to `XShapeCombineMask' > > *** Error code 1 > > > > Stop. > > *** Error code 1 > > > > Stop. > > *** Error code 1 > > > > Stop. > > *** Error code 1 > > > > Stop. > > *** Error code 1 > > > > Stop. > > *** Error code 1 > > > > Stop > > -------------------------------- > > > > Ideas please? > > > > Thanks, > > > > Bill > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 21:50:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA18875 for freebsd-current-outgoing; Tue, 5 Jan 1999 21:50:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA18865 for ; Tue, 5 Jan 1999 21:50:11 -0800 (PST) (envelope-from brdean@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id AAA02142 for ; Wed, 6 Jan 1999 00:49:43 -0500 (EST) Received: from dean.pc.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA23931; Wed, 6 Jan 1999 00:49:42 -0500 Received: (from brdean@localhost) by dean.pc.sas.com (8.9.1/8.9.1) id AAA20034; Wed, 6 Jan 1999 00:49:41 -0500 (EST) (envelope-from brdean) From: Brian Dean Message-Id: <199901060549.AAA20034@dean.pc.sas.com> Subject: Filesystem overflow ... can it be done? To: freebsd-current@FreeBSD.ORG Date: Wed, 6 Jan 1999 00:49:41 -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 Hi, Once a filesystem fills up, is there a way to have it "overflow" into another filesystem or area of storage? I want build a machine whose filesystem is memory-base, i.e., MFS_ROOT, where root, usr, var, etc, etc, is all memory based. However, I expect a goodly amount of temporary data to have to be dealt with in /tmp, but not all of the time. The primary reason for this is for fast data and program access. The machine could be booted with a BOOTP kernel, and everything downloaded into it's MFS when it comes up. The problem is that /tmp can fill up at peak times, because I can't put enough RAM in the machine to cover the expected maximum. I would be willing to lose performance in this case by having my /tmp overflow onto disk-based storage when necessary, but I wouldn't want to use disk storage all the time. For a long time now, I've used /tmp as a memory based filesystem, and the rest of the OS on disk with good performance results. I'd like to experiment with putting more of my heavily hit code into MFS and maybe take this to the extreme end of the spectrum of having everything in MFS, while still leaving enough RAM to run my processes. Some of my questions are: 1) Can nearly the same results be achieved by dedicating large amounts of memory for disk buffers? 2) I don't like the idea of consuming RAM with programs in the MFS, only to get loaded into RAM again to be executed. Gzipping my executables will help, however, this will increase the activation time, and I don't want to go to all this work to have performance lost by decompression. Maybe the answer to this would be covered in part by the first question? 3) Is this even doable with the filesystem technology in FreeBSD? A while back I remember discussions about stackable filesystems which I think might be relevant here. Thanks for any help and suggestions. -Brian -- Brian Dean Process Engineering brdean@unx.sas.com (x5235) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 22:00:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA20011 for freebsd-current-outgoing; Tue, 5 Jan 1999 22:00:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA19995; Tue, 5 Jan 1999 22:00:08 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id QAA30571; Wed, 6 Jan 1999 16:29:37 +1030 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA09382; Wed, 6 Jan 1999 16:29:36 +1030 Date: Wed, 6 Jan 1999 16:29:36 +1030 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: Bill Woods Cc: current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: kdesupport11 port build problems on -current elf In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 5 Jan 1999, Bill Woods wrote: > c++ -O -pipe -L/usr/X11R6/lib -o .libs/example example.o -Wl,--rpath > -Wl,/usr/local/lib .libs/libQwSpriteField.so -L/usr/X11R6/lib -lqt -lX11 > -lqt -lX11 > /usr/libexec/elf/ld: warning: libXext.so.6, needed by > /usr/X11R6/lib/libqt.so, not found (try using --rpath) > /usr/X11R6/lib/libqt.so: undefined reference to `XShapeCombineRegion' > /usr/X11R6/lib/libqt.so: undefined reference to `XShapeCombineMask' > *** Error code 1 This seems common for ports using libqt - for some reason they don't see libXext in /usr/X11R6/lib (but not for everyone, apparently, since the thing was committed in the first place). If you add -lXext to the linker link above, it links fine. I don't know how to use the --rpath option suggested, but I suspect this is it. Any hints, anyone? This should probably also have gone to freebsd-ports@freebsd.org, where I'm redirecting replies. Kris ----- (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 22:02:22 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA20497 for freebsd-current-outgoing; Tue, 5 Jan 1999 22:02:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA20486 for ; Tue, 5 Jan 1999 22:02:17 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id QAA30737; Wed, 6 Jan 1999 16:31:48 +1030 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA21998; Wed, 6 Jan 1999 16:31:47 +1030 Date: Wed, 6 Jan 1999 16:31:47 +1030 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: Alfred Perlstein Cc: Bill Woods , current@FreeBSD.ORG Subject: Re: aout to ELF people: READ THIS!! Re: kdesupport11 port build problems on -current elf 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, 6 Jan 1999, Alfred Perlstein wrote: > Anyone who's done a recent aout-elf convertion should realize that they > should be now generating ELF programs. Fine advice, but I don't think it applies in this case. My system is fully ELF yet I see the above errors when compiling at least several ports (the fix I mentioned in my previous message works), but there must be a better way to do it. Kris ----- (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 22:05:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA20722 for freebsd-current-outgoing; Tue, 5 Jan 1999 22:05:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA20717 for ; Tue, 5 Jan 1999 22:05:09 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac7.wam.umd.edu ((IDENT root)@rac7.wam.umd.edu [128.8.10.147]) by po4.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id BAA17921; Wed, 6 Jan 1999 01:05:55 -0500 (EST) Received: from rac7.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1]) by rac7.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id BAA13583; Wed, 6 Jan 1999 01:04:34 -0500 (EST) Received: from localhost by rac7.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id BAA13577; Wed, 6 Jan 1999 01:04:33 -0500 (EST) X-Authentication-Warning: rac7.wam.umd.edu: culverk owned process doing -bs Date: Wed, 6 Jan 1999 01:04:32 -0500 (EST) From: Kenneth Wayne Culver To: Bill Woods cc: current@FreeBSD.ORG Subject: Re: kdesupport11 port build problems on -current elf 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 tried to compile the kdesupport11 port on a FreeBSD 3.0-current elf > system today, and this is what I got, any ideas? check to see if libqt is in your ldconfig path for elf. do this by logging in as root, and then typing: ldconfig -elf -r look for libqt in there, if it isn't there, you need to put it into one of the directories that is in the ldconfig path, and type: ldconfig -elf -R Kenneth Culver > > -------------------------------------------------------------- > /bin/sh ../libtool --mode=compile c++ -DHAVE_CONFIG_H -I. -I. -I.. > -I/usr/X11R6/include/X11/qt -O -pipe -c QwCluster.cpp > c++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/X11R6/include/X11/qt -O -pipe -c > -fPIC -DPIC QwCluster.cpp > mv -f QwCluster.o QwCluster.lo > c++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/X11R6/include/X11/qt -O -pipe -c > QwCluster.cpp >/dev/null 2>&1 > /bin/sh ../libtool --mode=link c++ -O -pipe -L/usr/X11R6/lib -o > libQwSpriteField.la -rpath /usr/local/lib -version-info 5:2:4 -lqt -lX11 > QwSpriteField.lo QwSpriteField-double.lo QwSpriteField-int.lo > QwSpriteField-mobdouble.lo QwSpriteField-mobint.lo QwCluster.lo > mkdir .libs > c++ -shared -Wl,-soname -Wl,libQwSpriteField.so.5 -o > .libs/libQwSpriteField.so.5 QwSpriteField.lo QwSpriteField-double.lo > QwSpriteField-int.lo QwSpriteField-mobdouble.lo QwSpriteField-mobint.lo > QwCluster.lo > (cd .libs && ln -s libQwSpriteField.so.5 libQwSpriteField.so) > ar cru .libs/libQwSpriteField.a QwSpriteField.o QwSpriteField-double.o > QwSpriteField-int.o QwSpriteField-mobdouble.o QwSpriteField-mobint.o > QwCluster.o > ranlib .libs/libQwSpriteField.a > creating libQwSpriteField.la > (cd .libs && ln -s ../libQwSpriteField.la libQwSpriteField.la) > c++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/X11R6/include/X11/qt -O -pipe -c > example.cpp > /bin/sh ../libtool --mode=link c++ -O -pipe -L/usr/X11R6/lib -o example > example.o libQwSpriteField.la -lqt -lX11 > c++ -O -pipe -L/usr/X11R6/lib -o .libs/example example.o -Wl,--rpath > -Wl,/usr/local/lib .libs/libQwSpriteField.so -L/usr/X11R6/lib -lqt -lX11 > -lqt -lX11 > /usr/libexec/elf/ld: warning: libXext.so.6, needed by > /usr/X11R6/lib/libqt.so, not found (try using --rpath) > /usr/X11R6/lib/libqt.so: undefined reference to `XShapeCombineRegion' > /usr/X11R6/lib/libqt.so: undefined reference to `XShapeCombineMask' > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop > -------------------------------- > > Ideas please? > > Thanks, > > Bill > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 22:07:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA20929 for freebsd-current-outgoing; Tue, 5 Jan 1999 22:07:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA20924 for ; Tue, 5 Jan 1999 22:07:29 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac7.wam.umd.edu ((IDENT root)@rac7.wam.umd.edu [128.8.10.147]) by po4.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id BAA17998; Wed, 6 Jan 1999 01:08:18 -0500 (EST) Received: from rac7.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1]) by rac7.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id BAA13745; Wed, 6 Jan 1999 01:06:58 -0500 (EST) Received: from localhost by rac7.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id BAA13740; Wed, 6 Jan 1999 01:06:56 -0500 (EST) X-Authentication-Warning: rac7.wam.umd.edu: culverk owned process doing -bs Date: Wed, 6 Jan 1999 01:06:56 -0500 (EST) From: Kenneth Wayne Culver To: steven cc: current@FreeBSD.ORG Subject: Re: Update: Re: So we're stuck with using timidity now? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well i cvsup'd my sources to the latest.. todays source. > one of the files updated was indeed the swap_pager.c > > so i recompiled the kernel. Made sure i was using the right version > of OSS, the "i" version > > still locks up... mpg123 seems to run fine, so does Fxtv. but the > main reason for OSS is to get sound out of quake and use x11amp. > > So should i just get a real soundcard ;-) > I don't know what is going on... I am using FreeBSD 3.0-RELEASE, which could be why my computer doesn't have the problems that yours does. The OSS website recommends using the 11/23/98 snapshot of FreeBSD 3.0 in order to achieve the greatest stabilty, but I have not had any problem getting x11amp, or quake working. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 22:12:01 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA21433 for freebsd-current-outgoing; Tue, 5 Jan 1999 22:12:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA21413 for ; Tue, 5 Jan 1999 22:12:00 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id WAA23628; Tue, 5 Jan 1999 22:11:17 -0800 Date: Tue, 5 Jan 1999 22:11:17 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Brian Dean cc: freebsd-current@FreeBSD.ORG Subject: Re: Filesystem overflow ... can it be done? In-Reply-To: <199901060549.AAA20034@dean.pc.sas.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 answer is what Transarc built. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 22:21:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA22507 for freebsd-current-outgoing; Tue, 5 Jan 1999 22:21:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cassiopeia.caprica.com ([208.153.245.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA22502 for ; Tue, 5 Jan 1999 22:21:55 -0800 (PST) (envelope-from frank@exit.com) Received: from exit.com (uucp@localhost) by cassiopeia.caprica.com (8.8.8/8.8.8) with UUCP id WAA21473; Tue, 5 Jan 1999 22:21:41 -0800 (PST) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime.exit.com [206.223.0.5]) by tinker.exit.com (8.8.8/8.8.8) with ESMTP id WAA04003; Tue, 5 Jan 1999 22:15:47 -0800 (PST) (envelope-from frank@tinker.exit.com) Received: (from frank@localhost) by realtime.exit.com (8.9.1/8.9.1) id WAA00326; Tue, 5 Jan 1999 22:15:47 -0800 (PST) (envelope-from frank) From: Frank Mayhar Message-Id: <199901060615.WAA00326@realtime.exit.com> Subject: Re: Why won't 3.0-current remember my config? In-Reply-To: <199901051649.LAA04700@jabberwock.rstcorp.com> from "Viren R. Shah" at "Jan 5, 1999 11:49:36 am" To: viren@rstcorp.com Date: Tue, 5 Jan 1999 22:15:47 -0800 (PST) Cc: frank@tinker.exit.com, current@FreeBSD.ORG Reply-To: frank@exit.com 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 Viren R. Shah wrote: > >>>>> "Frank" == Frank Mayhar writes: > Frank> I've RTFM, I've UTSL, and from all I can tell, when I give the > Frank> 'pnp 1 1 os...' command to userconfig during boot, later, > Frank> during /etc/rc, dset should pick up that change and record it > Frank> in /kernel. > Frank> I'm trying to configure a soundcard. The userconfig line I give is: > > >pnp 1 1 os enable port0 0x534 port2 0x220 port3 0xe0d irq0 10 drq0 1 drq1 6 > > Put your pnp config line above in a file (say /boot/pnp.config ) like: > > USERCONFIG > pnp 1 1 os enable port0 0x534 port2 0x220 port3 0xe0d irq0 10 drq0 1 drq1 6 > quit > > and in > /boot/boot.conf put in the line > load -t userconfig_script /boot/pnp.config Okay, this worked, with the added caveat that putting _just_ that line in /boot/boot.conf results in the message "load: can't load file before kernel" and the command being ignored. I preceded that line with the line "load kernel" and everything appears to be working fine. Many thanks. -- Frank Mayhar frank@exit.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 22:29:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA23385 for freebsd-current-outgoing; Tue, 5 Jan 1999 22:29:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA23369; Tue, 5 Jan 1999 22:29:43 -0800 (PST) (envelope-from bwoods@cybcon.com) Received: from cybcon.com (bwoods@cybcon.com [205.147.64.49]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id WAA24325; Tue, 5 Jan 1999 22:25:31 -0800 (PST) Date: Tue, 5 Jan 1999 22:25:31 -0800 (PST) From: Bill Woods To: Kris Kennaway cc: current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: kdesupport11 port build problems on -current elf 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, that sounds good....ahh..oh yea, what do you mean by "if you add -lXext to the linker link above" . What do I add and where ? On Wed, 6 Jan 1999, Kris Kennaway wrote: > On Tue, 5 Jan 1999, Bill Woods wrote: > > > c++ -O -pipe -L/usr/X11R6/lib -o .libs/example example.o -Wl,--rpath > > -Wl,/usr/local/lib .libs/libQwSpriteField.so -L/usr/X11R6/lib -lqt -lX11 > > -lqt -lX11 > > /usr/libexec/elf/ld: warning: libXext.so.6, needed by > > /usr/X11R6/lib/libqt.so, not found (try using --rpath) > > /usr/X11R6/lib/libqt.so: undefined reference to `XShapeCombineRegion' > > /usr/X11R6/lib/libqt.so: undefined reference to `XShapeCombineMask' > > *** Error code 1 > > This seems common for ports using libqt - for some reason they don't see > libXext in /usr/X11R6/lib (but not for everyone, apparently, since the thing > was committed in the first place). If you add -lXext to the linker link above, > it links fine. I don't know how to use the --rpath option suggested, but I > suspect this is it. Any hints, anyone? > > This should probably also have gone to freebsd-ports@freebsd.org, where I'm > redirecting replies. > > Kris > > ----- > (ASP) Microsoft Corporation (MSFT) announced today that the release of its > productivity suite, Office 2000, will be delayed until the first quarter > of 1901. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 22:42:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA24478 for freebsd-current-outgoing; Tue, 5 Jan 1999 22:42:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA24461; Tue, 5 Jan 1999 22:41:56 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac3.wam.umd.edu ((IDENT root)@rac3.wam.umd.edu [128.8.10.143]) by po4.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id BAA18961; Wed, 6 Jan 1999 01:42:36 -0500 (EST) Received: from rac3.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1]) by rac3.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id BAA17196; Wed, 6 Jan 1999 01:41:15 -0500 (EST) Received: from localhost by rac3.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id BAA17191; Wed, 6 Jan 1999 01:41:14 -0500 (EST) X-Authentication-Warning: rac3.wam.umd.edu: culverk owned process doing -bs Date: Wed, 6 Jan 1999 01:41:14 -0500 (EST) From: Kenneth Wayne Culver To: Bill Woods cc: Kris Kennaway , current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: kdesupport11 port build problems on -current elf 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, that sounds good....ahh..oh yea, what do you mean by "if you add > -lXext to the linker link above" . What do I add and where ? > add it to the line in the Makefile with -lqt and -lX11 on it, and add -lXext. > On Wed, 6 Jan 1999, Kris Kennaway wrote: > > > On Tue, 5 Jan 1999, Bill Woods wrote: > > > > > c++ -O -pipe -L/usr/X11R6/lib -o .libs/example example.o -Wl,--rpath > > > -Wl,/usr/local/lib .libs/libQwSpriteField.so -L/usr/X11R6/lib -lqt -lX11 > > > -lqt -lX11 > > > /usr/libexec/elf/ld: warning: libXext.so.6, needed by > > > /usr/X11R6/lib/libqt.so, not found (try using --rpath) > > > /usr/X11R6/lib/libqt.so: undefined reference to `XShapeCombineRegion' > > > /usr/X11R6/lib/libqt.so: undefined reference to `XShapeCombineMask' > > > *** Error code 1 > > > > This seems common for ports using libqt - for some reason they don't see > > libXext in /usr/X11R6/lib (but not for everyone, apparently, since the thing > > was committed in the first place). If you add -lXext to the linker link above, > > it links fine. I don't know how to use the --rpath option suggested, but I > > suspect this is it. Any hints, anyone? > > > > This should probably also have gone to freebsd-ports@freebsd.org, where I'm > > redirecting replies. > > > > Kris > > > > ----- > > (ASP) Microsoft Corporation (MSFT) announced today that the release of its > > productivity suite, Office 2000, will be delayed until the first quarter > > of 1901. > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 22:55:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA26161 for freebsd-current-outgoing; Tue, 5 Jan 1999 22:55:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from paert.tse-online.de (paert.tse-online.de [194.97.69.172]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA26154 for ; Tue, 5 Jan 1999 22:55:16 -0800 (PST) (envelope-from ab@paert.tse-online.de) Received: (qmail 3012 invoked by uid 1000); 6 Jan 1999 06:53:34 -0000 Message-ID: <19990106075334.A715@paert.tse-online.de> Date: Wed, 6 Jan 1999 07:53:34 +0100 From: Andreas Braukmann To: current@FreeBSD.ORG Subject: Re: Trouble booting from WinNT with new boot loader Mail-Followup-To: current@FreeBSD.ORG References: <199901052315.AAA07950@daneel.stuyts.nl> <199901052317.PAA01625@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <199901052317.PAA01625@dingo.cdrom.com>; from Mike Smith on Tue, Jan 05, 1999 at 03:17:53PM -0800 Organization: TSE TeleService GmbH Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, (and a happy new year, ... still ...) On Tue, Jan 05, 1999 at 03:17:53PM -0800, Mike Smith wrote: > > This is a Gigabyte 586DX with dual P166MMX, 64 meg ram, one IDE drive and 2 > > scsi drives. WinNT is installed on the IDE drive. FreeBSD is installed on da0 > > (/) and da1 using the onboard scsi controller. > > You need "set num_ide_disks=1" in /boot/boot.conf; you can also break > to the loader commandline and issue the command directly to test it out > first. I'm having a quite similar problem, but I have to suppose that the num_ide-thingie won't help. My home-system purely scsi-based with two disks (2 x IBM DDRS 9 GB); the disks are partitioned^h^h^h^h^h^h^h^h^h^h^hsliced like this: :: paert# fdisk da0 :: ******* Working on device /dev/rda0 ******* [...] :: Media sector size is 512 :: Warning: BIOS sector numbering starts with sector 1 :: Information from DOS bootblock is: :: The data for partition 1 is: :: sysid 6,(Primary 'big' DOS (> 32MB)) :: start 63, size 1060227 (517 Meg), flag 80 (active) :: beg: cyl 0/ sector 1/ head 1; :: end: cyl 65/ sector 63/ head 254 :: The data for partition 2 is: :: sysid 5,(Extended DOS) :: start 1060290, size 7405965 (3616 Meg), flag 0 :: beg: cyl 66/ sector 1/ head 0; :: end: cyl 526/ sector 63/ head 254 :: The data for partition 3 is: :: sysid 165,(FreeBSD/NetBSD/386BSD) :: start 8466255, size 9381960 (4581 Meg), flag 0 :: beg: cyl 527/ sector 1/ head 0; :: end: cyl 1023/ sector 63/ head 254 :: paert# fdisk da1 :: ******* Working on device /dev/rda1 ******* [...} :: Media sector size is 512 :: Warning: BIOS sector numbering starts with sector 1 :: Information from DOS bootblock is: :: The data for partition 1 is: :: sysid 165,(FreeBSD/NetBSD/386BSD) :: start 63, size 12578832 (6142 Meg), flag 80 (active) :: beg: cyl 0/ sector 1/ head 1; :: end: cyl 782/ sector 63/ head 254 :: The data for partition 2 is: :: sysid 5,(Extended DOS) :: start 12578895, size 3871665 (1890 Meg), flag 0 :: beg: cyl 783/ sector 1/ head 0; :: end: cyl 1023/ sector 63/ head 254 ... and partitioned as :: paert# disklabel da0 :: # size offset fstype [fsize bsize bps/cpg] :: b: 786432 2097152 swap # (Cyl. 130*- 179*) :: c: 9381960 0 unused 0 0 # (Cyl. 0 - 583) :: e: 2097152 0 4.2BSD 0 0 0 # (Cyl. 0 - 130*) :: f: 6498376 2883584 4.2BSD 0 0 0 # (Cyl. 179*- 583*) :: paert# disklabel da1 :: # size offset fstype [fsize bsize bps/cpg] :: a: 524288 0 4.2BSD 0 0 0 # (Cyl. 0 - 32*) :: b: 786432 524288 swap # (Cyl. 32*- 81*) :: c: 12578832 0 unused 0 0 # (Cyl. 0 - 782*) :: e: 2097152 1310720 4.2BSD 0 0 0 # (Cyl. 81*- 212*) :: f: 2097152 3407872 4.2BSD 0 0 0 # (Cyl. 212*- 342*) :: g: 7073808 5505024 4.2BSD 0 0 0 # (Cyl. 342*- 782*) I'm used to boot the system by the NT BootLoader (since fbsdboot chokes on vm86 ...). The (freebsd) root filesystem lives on da1s1a. Both bsd-slices are disklabeled to the new blocks, too. I made an entry in the NT boot.ini for the new fbsd bootblock and the system boots. ... But the new boot block gives the warning 'no ufs' first. It seems to me, that the boot-code just tries to make use of the first partitions in the first found freebsd-slice (da0s3) for going on. (e.g. looking for /boot/* ) Since the da0s3b partition is a swap-partition, .... this approach has to fail ... Any hints? Kind regards and tia, Andreas -- : TSE TeleService GmbH : Gsf: Arne Reuter : : : Hovestrasse 14 : Andreas Braukmann : We do it with : : D-48351 Everswinkel : HRB: 1430, AG WAF : FreeBSD/SMP : :--------------------------------------------------------------------: : PGP-Key: http://www.tse-online.de/~ab/public-key : : Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 23:00:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA27208 for freebsd-current-outgoing; Tue, 5 Jan 1999 23:00:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from paert.tse-online.de (paert.tse-online.de [194.97.69.172]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA27202 for ; Tue, 5 Jan 1999 23:00:43 -0800 (PST) (envelope-from ab@paert.tse-online.de) Received: (qmail 3020 invoked by uid 1000); 6 Jan 1999 06:59:01 -0000 Message-ID: <19990106075901.B715@paert.tse-online.de> Date: Wed, 6 Jan 1999 07:59:01 +0100 From: Andreas Braukmann To: current@FreeBSD.ORG Subject: Re: elf make world Success Mail-Followup-To: current@FreeBSD.ORG References: <199901050620.WAA04878@ix.netcom.com> <199901060228.SAA29116@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <199901060228.SAA29116@vashon.polstra.com>; from John Polstra on Tue, Jan 05, 1999 at 06:28:04PM -0800 Organization: TSE TeleService GmbH Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Tue, Jan 05, 1999 at 06:28:04PM -0800, John Polstra wrote: > In article <199901050620.WAA04878@ix.netcom.com>, > Thomas Dean wrote: > > > > When I first installed FreeBSD, I think version 0.1, I had a 10MB > > disk that was 50% full. Now, I have a 3GB disk that is 90% full! > > But I bet your 3GB disk cost you less than the 10MB disk. :-) ... late in the eighties I invested (yes, ... invested seems to be the right word :) ) in a new disk for my first approaches to unix (Interactive SVR3 ;) ) and 'commercial' software-developing. It was a 330 MByte ESDI disk and my dad had to give me loan about somewhat like 3000.00 DM (ca. 1500.00 Euro :) ) for it. phhh. -ab -- : TSE TeleService GmbH : Gsf: Arne Reuter : : : Hovestrasse 14 : Andreas Braukmann : We do it with : : D-48351 Everswinkel : HRB: 1430, AG WAF : FreeBSD/SMP : :--------------------------------------------------------------------: : PGP-Key: http://www.tse-online.de/~ab/public-key : : Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 23:04:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA27561 for freebsd-current-outgoing; Tue, 5 Jan 1999 23:04:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA27554 for ; Tue, 5 Jan 1999 23:04:10 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zxn0A-0004lM-00; Wed, 6 Jan 1999 00:03:34 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id AAA31358; Wed, 6 Jan 1999 00:01:38 -0700 (MST) Message-Id: <199901060701.AAA31358@harmony.village.org> To: "Steven P. Donegan" Subject: Re: Elf Conversion Cc: current@FreeBSD.ORG In-reply-to: Your message of "Tue, 05 Jan 1999 18:49:17 PST." References: Date: Wed, 06 Jan 1999 00:01:37 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Steven P. Donegan" writes: : ld.so failed: Can't find shared library "libXmu.so.6.0" Update to a newer set of /etc/rc files. This is caused when ldconfig can't find a.out libraries. make aout-to-elf moves them to */aout. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 23:09:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA28092 for freebsd-current-outgoing; Tue, 5 Jan 1999 23:09:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA28076 for ; Tue, 5 Jan 1999 23:09:08 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zxn4u-0004lW-00; Wed, 6 Jan 1999 00:08:28 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id AAA31404; Wed, 6 Jan 1999 00:06:32 -0700 (MST) Message-Id: <199901060706.AAA31404@harmony.village.org> To: "Robert V. Baron" Subject: Re: i386/conf/PCCARD Cc: current@FreeBSD.ORG In-reply-to: Your message of "05 Jan 1999 18:51:26 EST." References: Date: Wed, 06 Jan 1999 00:06:31 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Robert V. Baron" writes: : I've been wondering, of late, how well/if laptops are supported in : -current. It seems that the configuration, PCCARD, has recently : (since mid December) has gone away. Is this the answer? Laptops are well supported in -current. In the cleaning frenzy that overtook the tree, PCCARD was removed because it was claimed to be out of date. Nothing has taken its place, sadly, but GENERIC with a few lines from LINT (the ones talking about card and pcic) will work great. I'm running approx Jan 1 on my Libretto 50CT. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 23:16:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA28764 for freebsd-current-outgoing; Tue, 5 Jan 1999 23:16:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from xwin.nmhtech.com (xwin.nmhtech.com [208.138.46.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA28753 for ; Tue, 5 Jan 1999 23:16:14 -0800 (PST) (envelope-from nicole@xwin.nmhtech.com) Received: by xwin.nmhtech.com (Postfix, from userid 1001) id 5ED932EE28; Tue, 5 Jan 1999 23:15:46 -0800 (PST) Message-ID: X-Mailer: XFMail 1.2 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 In-Reply-To: Date: Tue, 05 Jan 1999 23:15:46 -0800 (PST) From: Nicole Harrington To: Tom Bartol Subject: Re: New boot blocks for serial console ... Cc: current@FreeBSD.ORG, Garrett Wollman Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id XAA28757 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 04-Jan-99 Tom Bartol wisely wrote: > > > On Mon, 4 Jan 1999, Garrett Wollman wrote: > >> < >> said: >> >> >> Not at all. Ever heard of a padlock? >> >> > Well, then, there's your solution! >> >> No, because it still doesn't prevent someone from walking up to the >> machine and telling it to boot something it shouldn't. >> >> What we're trying to achieve is an environment where the worst thing >> someone could do is cause the machine to reboot. >> > > Then what you need is an untouchable machine in the hardware AND software > sense. Padlock the room where the machine sits, get a UPS with plenty > reserve power, and don't put it the machine on the net. Probably not a > very useful machine when you're all done doing that :-) > Say.. Isn't that how MS NT got its security rating Nicole > Sorry, I'm just jerking you around here, you're original idea about have a > streamlined boot process is a good one, I'm just pointing out that this is > really just a deterrent, like all other security measures as there really > is no absolute solution to achieve absolute security. > > Tom > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message |\ __ /| (`\ | o_o |__ ) ) // \\ nicole@nmhtech.com | http://www.webweaver.net/ webmistress@dangermouse.org | http://www.dangermouse.org -------------------------(((---(((----------------------- - Powered by Coka Cola and FreeBSD - - Stong enough for a man - But made for a Woman - - I'm not ADD - I'm just MultiThreaded - - Microsoft: What bug would you like today? - ---------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 5 23:16:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA28785 for freebsd-current-outgoing; Tue, 5 Jan 1999 23:16:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA28778 for ; Tue, 5 Jan 1999 23:16:25 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id CAA51140; Wed, 6 Jan 1999 02:20:19 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Wed, 6 Jan 1999 02:20:19 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Brian Dean cc: freebsd-current@FreeBSD.ORG Subject: Re: Filesystem overflow ... can it be done? In-Reply-To: <199901060549.AAA20034@dean.pc.sas.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, 6 Jan 1999, Brian Dean wrote: > Hi, > > Once a filesystem fills up, is there a way to have it "overflow" into > another filesystem or area of storage? > > I want build a machine whose filesystem is memory-base, i.e., > MFS_ROOT, where root, usr, var, etc, etc, is all memory based. > However, I expect a goodly amount of temporary data to have to be > dealt with in /tmp, but not all of the time. The primary reason for > this is for fast data and program access. The machine could be booted > with a BOOTP kernel, and everything downloaded into it's MFS when it > comes up. > > The problem is that /tmp can fill up at peak times, because I can't > put enough RAM in the machine to cover the expected maximum. I would > be willing to lose performance in this case by having my /tmp overflow > onto disk-based storage when necessary, but I wouldn't want to use > disk storage all the time. > > For a long time now, I've used /tmp as a memory based filesystem, and > the rest of the OS on disk with good performance results. I'd like to > experiment with putting more of my heavily hit code into MFS and maybe > take this to the extreme end of the spectrum of having everything in > MFS, while still leaving enough RAM to run my processes. > > Some of my questions are: > > 1) Can nearly the same results be achieved by dedicating large > amounts of memory for disk buffers? Design and implementation dismisses this idea as a bad one. > > 2) I don't like the idea of consuming RAM with programs in the > MFS, only to get loaded into RAM again to be executed. > Gzipping my executables will help, however, this will > increase the activation time, and I don't want to go to all > this work to have performance lost by decompression. Maybe > the answer to this would be covered in part by the first > question? I'm not sure if MFS uses the text image in memory as the text segment, if it did that would be nice, check the source. gzipping sounds like a bad idea. > > 3) Is this even doable with the filesystem technology in > FreeBSD? A while back I remember discussions about > stackable filesystems which I think might be relevant > here. Sort of, MFS uses swap as a backing store, so with enough swap you can have a LOT of MFS, however be advised that if you run through your MFS data and eat a lot of RAM you'll thrash pretty severly. the only "trick" i could think of was to hook some sort of way of having many vn devices and dynamically adding them to swap (unfortunatly once allocated they can't be free until the machine is rebooted, then the temp files used for swapping can be cleared) -Alfred > > Thanks for any help and suggestions. > > -Brian > -- > Brian Dean Process Engineering brdean@unx.sas.com (x5235) > > 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 Jan 6 00:40:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA07693 for freebsd-current-outgoing; Wed, 6 Jan 1999 00:40:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from postal.interaccess.com (postal.interaccess.com [207.208.133.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA07672; Wed, 6 Jan 1999 00:40:06 -0800 (PST) (envelope-from wepublish1099@att.com) Received: from bsbpub (d15.focal8.interaccess.com [207.208.189.15]) by postal.interaccess.com (8.9.0/8.9.0) with SMTP id CAA02056; Wed, 6 Jan 1999 02:39:26 -0600 (CST) Date: Wed, 6 Jan 1999 02:39:26 -0600 (CST) Message-Id: <199901060839.CAA02056@postal.interaccess.com> From: "BSB Publishing Co." To: Subject: New Book - "How To Juggle Women: Without Getting Killed or Going Broke" 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 Women all over America have said, "Burn This Book!!!" CALL TO ORDER YOUR COPY - (800) 830-2047 [24hrs] Juggling Women: Without Getting Killed or Going Broke by Stefan Feller ISBN:0-9658299-4-4 Price: $12.00 This book is an essential guide for the seasoned dating man who needs help organizing the women in his life. Women are constantly grabbing your interest and attention. Do you have to choose on over the other? Of Course not! Stop letting opportunities like these go to waste. Why not date them all? This is a must-read for men who are active on the dating scene. Not only will you learn how to juggle several females at a time, you will also improve your overall chances with women, including where to meet them and how to do the little things to keep them happy. You will learn time-saving techniques that will maximize your availability, and allow you to spend time with several ladies a day. The author details scheduling methods so you never have two dates at the same time. You will also learn money-saving tips so you can date aggressively and still have money left to by necessities like beer. Forget the saying,"For every man there is a woman out there." Now it will be, "For every man there are at least three women." -------------------------------------------------------- CHAPTER TITLES Chapter One - Getting to Know You Chapter Two - Categories of Women Chapter Three - Where to Find Them Chapter Four - The Rotation Chapter Five - Prior Planning Chapter Six - How to Keep Them Happy and Away From Each Other Chapter Seven - Fiscally Fit Chapter Eight - Personnel Changes -------------------------------------------------------- Juggling Women: Without Getting Killed or Going Broke by Stefan Feller ISBN:0-9658299-4-4 Price: $12.00 $3.00 Shipping individuals - COD Charges are free for a limited time. Wholesale Discounts Available --------------------------------------------------------- Order by Phone 1 (800)830-2047 24 hours a day --------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 00:49:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA09068 for freebsd-current-outgoing; Wed, 6 Jan 1999 00:49:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA09061 for ; Wed, 6 Jan 1999 00:49:24 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id JAA23342; Wed, 6 Jan 1999 09:48:16 +0100 (CET) To: Kazutaka YOKOTA cc: current@FreeBSD.ORG, nick.hibma@jrc.it Subject: Re: Request for a char device major number In-reply-to: Your message of "Wed, 06 Jan 1999 12:23:34 +0900." <199901060323.MAA28132@zodiac.mech.utsunomiya-u.ac.jp> Date: Wed, 06 Jan 1999 09:48:15 +0100 Message-ID: <23340.915612495@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199901060323.MAA28132@zodiac.mech.utsunomiya-u.ac.jp>, Kazutaka YOKOTA writes: >I need one CDEV major number for the keyboard driver (kbd). Both the >AT keyboard and the USB keyboard will use the same major number. > grab one in: src/sys/i386/conf/major.i386 -- 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 Wed Jan 6 00:59:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA10367 for freebsd-current-outgoing; Wed, 6 Jan 1999 00:59:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shale.csir.co.za (shale.csir.co.za [146.64.46.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA10300; Wed, 6 Jan 1999 00:58:26 -0800 (PST) (envelope-from reg@shale.csir.co.za) Received: (from reg@localhost) by shale.csir.co.za (8.9.1/8.9.1) id KAA57420; Wed, 6 Jan 1999 10:51:15 +0200 (SAT) (envelope-from reg) Date: Wed, 6 Jan 1999 10:51:15 +0200 From: Jeremy Lea To: Bill Woods Cc: Kris Kennaway , current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: kdesupport11 port build problems on -current elf Message-ID: <19990106105115.C16622@shale.csir.co.za> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: ; from Bill Woods on Tue, Jan 05, 1999 at 10:25:31PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Tue, Jan 05, 1999 at 10:25:31PM -0800, Bill Woods wrote: > OK, that sounds good....ahh..oh yea, what do you mean by "if you add > -lXext to the linker link above" . What do I add and where ? Firstly, you shouldn't be using the 11 ports yet. If you see ports apear in your tree without commit e-mail, then these are repository copies and haven't been upgrded yet. Give people a little chance. Use this patch (sent to the maintainer several weeks ago) as kdesupport/patches/patch-a3: --- QwSpriteField/Makefile.in~ Fri Nov 27 16:23:32 1998 +++ QwSpriteField/Makefile.in Fri Nov 27 16:23:53 1998 @@ -139,7 +139,7 @@ # the difference between the first and the last, is the major number # the last is the minor number # the number in the middle is the minor-minor number -libQwSpriteField_la_LDFLAGS = -version-info 5:2:4 -lqt -lX11 $(LIBSOCKET) +libQwSpriteField_la_LDFLAGS = -version-info 5:2:4 -lqt -lXext -lX11 $(LIBSOCKET) INCLUDES = $(QT_INCLUDES) lib_LTLIBRARIES = libQwSpriteField.la @@ -157,7 +157,7 @@ noinst_PROGRAMS = example example_SOURCES = example.cpp -example_LDADD = libQwSpriteField.la -lqt -lX11 $(LIBSOCKET) +example_LDADD = libQwSpriteField.la -lqt -lXext -lX11 $(LIBSOCKET) mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs CONFIG_HEADER = ../config.h CONFIG_CLEAN_FILES = Regards, -Jeremy -- | "I could be anything I wanted to, but one things true --+-- Never gonna be as big as Jesus, never gonna hold the world in my hand | Never gonna be as big as Jesus, never gonna build a promised land | But that's, that's all right, OK with me..." -Audio Adrenaline To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 03:34:16 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA00168 for freebsd-current-outgoing; Wed, 6 Jan 1999 03:34:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.42.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA00159; Wed, 6 Jan 1999 03:34:08 -0800 (PST) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.9.1/8.9.1) id MAA05593; Wed, 6 Jan 1999 12:32:20 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199901061132.MAA05593@sos.freebsd.dk> Subject: Re: syscons update - when? In-Reply-To: <199901060314.MAA27736@zodiac.mech.utsunomiya-u.ac.jp> from Kazutaka YOKOTA at "Jan 6, 1999 12:14:45 pm" To: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA) Date: Wed, 6 Jan 1999 12:32:20 +0100 (CET) Cc: sos@FreeBSD.ORG, msmith@FreeBSD.ORG, current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Kazutaka YOKOTA wrote: > As I announced before, reorganization of syscons code is under way and > I intend to commit changes in three stages. > > Stage 1: keyboard driver split > Stage 2: video driver split, splash screen > Stage 3: other reorganization > > The new code has been running on my -current box for quite a while. > > Now, -stable branch date is coming up. The question is how much > change we should commit before the branch? We can defer commit after > the branch and later backport the new code from -current to -stable. > However, there is a snug. > > At stage 1 and 2, the users will be forced to change their kernel > configuration files because keyboard and video drivers become separate > from syscons. Such change is probably too much, if suddenly > introduced to -stable well after the branch. > > So, probably our options are: > > a) Commit stage 1 and 2 changes now. Stage 3 changes may be backported > to -stable from -current later. > b) Don't commit any changes now, but commit them to -current after the > branch. Don't backport the changes to -stable at all. When the next > branch (3.1-STABLE?) comes, let it have the new code. > > I prefer the option a). But, I have to expect rough ride after > commits, as changes of this scale will have many initial glitches... I prefer option a) also. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@freebsd.org) FreeBSD Core Team member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 04:06:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA07290 for freebsd-current-outgoing; Wed, 6 Jan 1999 04:06:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bfc.dk ([194.192.110.140]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA07239 for ; Wed, 6 Jan 1999 04:06:26 -0800 (PST) (envelope-from npe@bfc.dk) From: npe@bfc.dk Received: by bfc.dk(Lotus SMTP MTA SMTP v4.6 (462.2 9-3-1997)) id 412566F1.00420840 ; Wed, 6 Jan 1999 13:01:14 +0100 X-Lotus-FromDomain: BFC-DATA@BFC To: Freebsd-current@FreeBSD.ORG Message-ID: <412566F1.00413EBE.00@bfc.dk> Date: Wed, 6 Jan 1999 13:01:14 +0100 Subject: Re: Kernel configurator 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, Jan 04, 1999 at 03:37:30PM +0100, npe@bfc.dk wrote: > > > > Would a thing like a kernel configurator with a user interface be > > > > appreciated ? > > > > Personally I think that it would be a great plus for new users.. . > > > > > > Well... why don't you ask them? The newbies who can read have a mailing > > > list where they decide what would be best for -current users to try :-) > > > > > Unless I'm mistaken, don't the options USERCONFIG, and its visual > > counterpart already implement a "Kernel Configurator??" It's my > > understanding that they do. > > That was my understanding also. I think the original author might have meant > a pre-compilation utility which spawns a TCL or Curses based configuration > tool that gives a runthrough of all the options, similar to Linux's 'make > xconfig' or 'make menuconfig' (assuming, of course, that they haven't changed > it in the two-plus years since I quit using Linux). Exactly... The bootup utility works just fine. But for the precompile thingy it would be much easier for newbies to use a tool for it with have descriptions and comments about all the options and devices. I'm currently thinking of a configuration file format suitable for this thing and wondered if there where some standard on that.. I'm currently working on a kind of .ini style where you build up all the menus and options in the file.. And maybe it would be smart to make specific options available in advanced mode only.. (CPU hacks and etc.) Regards, Nicolai Petri To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 04:21:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA09497 for freebsd-current-outgoing; Wed, 6 Jan 1999 04:21:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA09474; Wed, 6 Jan 1999 04:21:18 -0800 (PST) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (lxpxdo.lx.ehu.es [158.227.99.192]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id NAA04501; Wed, 6 Jan 1999 13:20:26 +0100 (MET) Message-ID: <36935509.E2969CF3@we.lc.ehu.es> Date: Wed, 06 Jan 1999 13:20:25 +0100 From: "José Mª Alcaide" Organization: Universidad del País Vasco - Dept. Electricidad y Electrónica X-Mailer: Mozilla 4.07 [en] (X11; U; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Alfred Perlstein CC: Bill Woods , current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: aout to ELF people: READ THIS!! Re: kdesupport11 port build problems on -current elf 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 Alfred Perlstein wrote: > > Anyone who's done a recent aout-elf convertion should realize that they > should be now generating ELF programs. > > If you want to compile X programs, recompile XFree86 as elf you need the > libraries. If you are using 3rd party libraries and need new programs you > will have to make sure the libraries that are depended on are recompiled > and installed as ELF. > My system is fully ELF, but kdesupport 1.0 does not compile anyway. (I rebuilt _everything_: XFree86 3.3.3, qt 1.41, etc.). The only a.out executable I have is CVSup. -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | http://www.we.lc.ehu.es/~jose Dpto. de Electricidad y Electrónica | Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139 ----------------------------------------------------------------------- "Go ahead... make my day." - H. Callahan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 05:02:16 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA13429 for freebsd-current-outgoing; Wed, 6 Jan 1999 05:02:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from assurance.rstcorp.com (assurance.rstcorp.com [206.29.49.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA13424 for ; Wed, 6 Jan 1999 05:02:15 -0800 (PST) (envelope-from vshah@rstcorp.com) Received: (from uucp@localhost) by assurance.rstcorp.com (8.8.8/8.8.8) id IAA26082; Wed, 6 Jan 1999 08:01:46 -0500 Received: from sandbox.rstcorp.com(206.29.49.63) by assurance.rstcorp.com via smap (V2.0) id xma026080; Wed, 6 Jan 99 08:01:22 -0500 Received: from jabberwock.rstcorp.com (jabberwock [206.29.49.98]) by sandbox.rstcorp.com (8.8.8/8.8.8) with ESMTP id IAA02825; Wed, 6 Jan 1999 08:01:22 -0500 (EST) Received: (from vshah@localhost) by jabberwock.rstcorp.com (8.9.1/8.8.8) id IAA34177; Wed, 6 Jan 1999 08:01:21 -0500 (EST) Date: Wed, 6 Jan 1999 08:01:21 -0500 (EST) Message-Id: <199901061301.IAA34177@jabberwock.rstcorp.com> From: "Viren R. Shah" To: "Steven P. Donegan" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Installed 3.0 CD. Flag day? In-Reply-To: References: <3692D945.5A09B394@tpgi.com.au> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: "Viren R. Shah" X-Face: )~y+U*K:yzjz{q<5lzpI_SVef'U.])9g[C9`1N@]u3,MHY7f*l7C)[_NjM4y4K8$uIUh|\u (K&&HS6,M!61&GMTk'mqmB/Qg]]X}"?TzsFl]"2v!bl8']dma.:^IY^a[lbOI>U:b<~FyK3q-p{HmZ mn~g.`~BE!5{2D:}Yi+\_KkWe?XaHj9$ko1k8iKLYv5*_2c8"G=?Up[}hn+7RNM(bzBZ_wWk6!Pf&B ?3Tcm7M7B~W%K/I0aX3]*=jP?aM]H6HBPT`oLk+0n^_;N\2\%|Rhy;p}34Q.jEsM\qtnxcm;ag%Nq Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Steven" == Steven P Donegan writes: Steven> BTW - mergemaster really caused fun here. It's only a 1 user system Steven> beyond root - and it trashed passwd, group etc. Not that it Steven> matters to me - I'm just going to rebuild from clean Steven> partitions - but others would probably be unhappy :-| I'm curious, how did that happen? Did you actually let mergemaster replace the passwd files in /etc? I use mergemaster quite often, and there are a few files that I don't let it touch. It wouldbe nice if mergemaster has an option to let you specify files that you don't want it to look at. But, all in all, mergemaster is a big help when keeping up with -current. Viren -- Viren R. Shah, {viren @ rstcorp . com} http://www.rstcorp.com/~vshah/ ====== FreeBSD: It's free, it's fast, it's fun. ====== "3 syncs represent the trinity - init, the child and the eternal zombie process." -- Jordan Hubbard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 05:13:38 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA14402 for freebsd-current-outgoing; Wed, 6 Jan 1999 05:13:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA14396 for ; Wed, 6 Jan 1999 05:13:37 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id WAA11520; Wed, 6 Jan 1999 22:13:00 +0900 (JST) Message-ID: <36934886.865DBCCE@newsguy.com> Date: Wed, 06 Jan 1999 20:27:02 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Mike Smith CC: current@FreeBSD.ORG, "Jordan K. Hubbard" , Andrzej Bialecki Subject: Re: /boot/boot.rc && /boot/rc.d References: <199901052135.NAA01045@dingo.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: > > While throwing these opposites around, consider also that some modules > are going to be demand-loaded, so you only want to be listing/ > nominating ones that are optional, and even then only ones that are > required before the system boots. Thus I wonder if it's really > necessary to have a particularly complex mechanism... My main concern is enabling a port to be installed/uninstalled. Editing boot.rc would be... not the way. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com "Heart like a Gabriel, pure and white as ivory, soul like a lucifer, black and cold as a piece of lead." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 05:13:52 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA14629 for freebsd-current-outgoing; Wed, 6 Jan 1999 05:13:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA14436 for ; Wed, 6 Jan 1999 05:13:43 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id WAA11550; Wed, 6 Jan 1999 22:13:08 +0900 (JST) Message-ID: <36935747.2A39852D@newsguy.com> Date: Wed, 06 Jan 1999 21:29:59 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Mike Smith CC: current@FreeBSD.ORG Subject: Re: Trouble booting from WinNT with new boot loader References: <199901052317.PAA01625@dingo.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: > > You need "set num_ide_disks=1" in /boot/boot.conf; you can also break > to the loader commandline and issue the command directly to test it out > first. This has just become a FAQ... Where is (is?) num_ide_disks documented? Also, Nordier's (Nordier's?) "new boot blocks" tutorial ought to mention it. Finally... Is it possible to make it not-necessary? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com "Heart like a Gabriel, pure and white as ivory, soul like a lucifer, black and cold as a piece of lead." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 06:10:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA19219 for freebsd-current-outgoing; Wed, 6 Jan 1999 06:10:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from skraldespand.demos.su (skraldespand.demos.su [194.87.5.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA19213 for ; Wed, 6 Jan 1999 06:10:19 -0800 (PST) (envelope-from mishania@skraldespand.demos.su) Received: by skraldespand.demos.su id RAA12906; (8.8.8/D) Wed, 6 Jan 1999 17:05:50 +0300 (MSK) Message-ID: <19990106170549.22835@demos.su> Date: Wed, 6 Jan 1999 17:05:49 +0300 From: "Mikhail A. Sokolov" To: Poul-Henning Kamp Cc: "Jordan K. Hubbard" , Jason George , freebsd-current@FreeBSD.ORG Subject: Re: News Server References: <6309.915563659@zippy.cdrom.com> <20873.915564044@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20873.915564044@critter.freebsd.dk>; from Poul-Henning Kamp on Tue, Jan 05, 1999 at 08:20:44PM +0100 Organization: Demos Company, Ltd., Moscow, Russian Federation. X-Point-of-View: Gravity is myth, - the earth sucks. X-Useless-Header: Look ma! It's a # sign! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 05, 1999 at 08:20:44PM +0100, Poul-Henning Kamp wrote: # In message <6309.915563659@zippy.cdrom.com>, "Jordan K. Hubbard" writes: # >> But why don't we just create a # >> freebsd.* # >> hierachy for selective and elective distribution ? # > # >Because I believe that requires buy-in by the backbone cabal, and # >who wants to spend 3 weeks mud-wrestling with Joel Furr? :-) # # I guess alt.freebsd.* could be a more legal alternative ? Actually, comp.{lists.freebsd,freebsd}, why alt.*? # -- # 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! -- -mishania I don't have anything against penguins, as long as they stay in the Antarctica, swim around, catch fishes and do the usual penguin stuff. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 06:28:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA21430 for freebsd-current-outgoing; Wed, 6 Jan 1999 06:28:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from postoffice.aeonflux.net (postoffice.aeonflux.net [208.139.254.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA21425 for ; Wed, 6 Jan 1999 06:28:13 -0800 (PST) (envelope-from hg@ParView.com) Received: (from uucp@localhost) by postoffice.aeonflux.net (8.8.8/8.8.7/PCS9711a) with UUCP id JAA00103; Wed, 6 Jan 1999 09:27:11 -0500 (EST) Received: (from hg@localhost) by ParView.com (8.9.1/8.8.8/n2wx) id JAA09861; Wed, 6 Jan 1999 09:25:25 -0500 (EST) (envelope-from hg) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <13971.29268.338874.138338@slice.parview.com> Date: Wed, 6 Jan 1999 09:25:24 -0500 (EST) From: hgoldste@bbs.mpcs.com To: John Polstra Cc: current@FreeBSD.ORG Subject: Re: ELF interpreter /usr/lib/libc.so.1 not found (on 3.0-CURRENT 12/20/98) Newsgroups: polstra.freebsd.hackers In-Reply-To: <199901060304.TAA36807@vashon.polstra.com> References: <13962.6777.503181.771874@penny.south.mpcs.com> <199901060304.TAA36807@vashon.polstra.com> X-Mailer: VM 6.56 under Emacs 19.34.1 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra writes: > In article <13962.6777.503181.771874@penny.south.mpcs.com>, > Howard Goldstein wrote: > > slice:~/src/develop$ ./v2show > > ELF interpreter /usr/lib/libc.so.1 not found > > Abort trap > > Add "-dynamic-linker /usr/libexec/ld-elf.so.1" to your "ld" > command. The "ELF interpreter" is the dynamic linker that the > kernel is trying to load. Its pathname defaults (in the linker) to > "/usr/lib/libc.so.1", which is the old SVR4 version. This must be > overridden on the linker command line. "cc" automatically does that. This probably accounts for some of the reason why I couldn't get an ld executable built anyway other than as a -Bstatic. Some of those init/end modules are also different (no surprise to you folks who do this all the time) > You really should try to use "cc" for linking, because there's lots > of non-obvious stuff that needs to go onto the command line for > "ld". Take some simple program "hello.c", and do this: > > cc -v hello.c Yow lots of extra stuff. Where are these overrides set in cc/gcc? > I don't understand why your masm/nasm problem would affect linking. They don't directly affect it. The problem was my failure to use cc as a frontend to the linker. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 06:37:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA22351 for freebsd-current-outgoing; Wed, 6 Jan 1999 06:37:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA22333; Wed, 6 Jan 1999 06:37:15 -0800 (PST) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.9.2/8.9.2) with ESMTP id JAA01668; Wed, 6 Jan 1999 09:36:34 -0500 (EST) Date: Wed, 6 Jan 1999 09:36:34 -0500 (EST) From: jack To: Kris Kennaway cc: Bill Woods , current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: kdesupport11 port build problems on -current elf 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, 6 Jan 1999, Kris Kennaway wrote: > > /usr/X11R6/lib/libqt.so: undefined reference to `XShapeCombineRegion' > > /usr/X11R6/lib/libqt.so: undefined reference to `XShapeCombineMask' > > *** Error code 1 > > This seems common for ports using libqt - for some reason they don't see > libXext in /usr/X11R6/lib (but not for everyone, apparently, since the thing > was committed in the first place). If you add -lXext to the linker link above, > it links fine. I don't know how to use the --rpath option suggested, but I > suspect this is it. Any hints, anyone? I haven't tried the kde 1.1 stuff, but for 1.0 I could only get it to compile using qt-1.40. -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 06:46:59 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23468 for freebsd-current-outgoing; Wed, 6 Jan 1999 06:46:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from second.dialup.access.net (lsmarso.dialup.access.net [166.84.254.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA23463 for ; Wed, 6 Jan 1999 06:46:56 -0800 (PST) (envelope-from larry@marso.com) Received: (from larry@localhost) by second.dialup.access.net (8.9.1/8.8.8) id JAA25502 for freebsd-current@freebsd.org; Wed, 6 Jan 1999 09:43:42 -0500 (EST) (envelope-from larry) Date: Tue, 5 Jan 1999 23:16:39 -0500 From: "Larry S. Marso" To: ports-freebsd@FreeBSD.ORG Subject: gimp1 compile fails; elf 3.0-current Message-ID: <19990105231639.N22712@marso.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.13i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Compiling gimp1 (after a fresh gtk-1.0.6 build) fails in the plug-in MapObject subdirectory. Here's what's left in my scrollback buffer: //////////////////////////////////////////////////////////////////// /usr/X11R6/include/gtk/gtkclist.h:100: parse error before `gconstpointer' In file included from /usr/X11R6/include/gtk/gtkcolorsel.h:25, from /usr/X11R6/include/gtk/gtk.h:40, from ../../plug-ins/libgck/gck/gck.h:27, from mapobject_shade.h:8, from mapobject_apply.c:5: /usr/X11R6/include/gtk/gtkpreview.h:52: parse error before `GdkRgbDither' /usr/X11R6/include/gtk/gtkpreview.h:52: warning: no semicolon at end of struct or union /usr/X11R6/include/gtk/gtkpreview.h:54: parse error before `:' /usr/X11R6/include/gtk/gtkpreview.h:55: parse error before `:' /usr/X11R6/include/gtk/gtkpreview.h:121: parse error before `GdkRgbDither' In file included from /usr/X11R6/include/gtk/gtk.h:43, from ../../plug-ins/libgck/gck/gck.h:27, from mapobject_shade.h:8, from mapobject_apply.c:5: /usr/X11R6/include/gtk/gtkctree.h:89: parse error before `GNode' /usr/X11R6/include/gtk/gtkctree.h:202: parse error before `GNode' /usr/X11R6/include/gtk/gtkctree.h:205: parse error before `*' /usr/X11R6/include/gtk/gtkctree.h:206: parse error before `GNode' /usr/X11R6/include/gtk/gtkctree.h:210: warning: data definition has no type or storage class In file included from /usr/X11R6/include/gtk/gtk.h:47, from ../../plug-ins/libgck/gck/gck.h:27, from mapobject_apply.c:5: /usr/X11R6/include/gtk/gtkitemfactory.h:60: field `object' has incomplete type In file included from ../../plug-ins/libgck/gck/gck.h:37, from mapobject_shade.h:8, from mapobject_apply.c:5: ../../plug-ins/libgck/gck/gcktypes.h:122: parse error before `GtkAcceleratorTable' ../../plug-ins/libgck/gck/gcktypes.h:122: warning: no semicolon at end of struct or union ../../plug-ins/libgck/gck/gcktypes.h:124: parse error before `}' ../../plug-ins/libgck/gck/gcktypes.h:124: warning: data definition has no type or storage class In file included from ../../plug-ins/libgck/gck/gck.h:41, from mapobject_shade.h:8, from mapobject_apply.c:5: ../../plug-ins/libgck/gck/gckui.h:36: parse error before `*' ../../plug-ins/libgck/gck/gckui.h:36: warning: data definition has no type or storage class ../../plug-ins/libgck/gck/gckui.h:37: parse error before `*' ../../plug-ins/libgck/gck/gckui.h:129: parse error before `GtkAcceleratorTable' ../../plug-ins/libgck/gck/gckui.h:132: parse error before `GtkAcceleratorTable' In file included from mapobject_main.h:13, from mapobject_shade.h:10, from mapobject_apply.c:5: mapobject_ui.h:20: warning: data definition has no type or storage class gmake[3]: *** [mapobject_apply.o] Error 1 gmake[3]: Leaving directory `/jaz/ports/graphics/gimp1/work/gimp-1.0.2/plug-ins/MapObject' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/jaz/ports/graphics/gimp1/work/gimp-1.0.2/plug-ins' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/jaz/ports/graphics/gimp1/work/gimp-1.0.2' gmake: *** [all-recursive-am] Error 2 *** Error code 2 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. root@lsmarso> Best regards -- Larry S. Marso larry@marso.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 07:05:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA25293 for freebsd-current-outgoing; Wed, 6 Jan 1999 07:05:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-24-dbn.dial-up.net [196.34.155.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA25248 for ; Wed, 6 Jan 1999 07:04:58 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id RAA00693; Wed, 6 Jan 1999 17:02:34 +0200 (SAT) From: Robert Nordier Message-Id: <199901061502.RAA00693@ceia.nordier.com> Subject: Re: Trouble booting from WinNT with new boot loader In-Reply-To: <36935747.2A39852D@newsguy.com> from "Daniel C. Sobral" at "Jan 6, 99 09:29:59 pm" To: dcs@newsguy.com (Daniel C. Sobral) Date: Wed, 6 Jan 1999 17:02:30 +0200 (SAT) Cc: mike@smith.net.au, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel C. Sobral wrote: > Mike Smith wrote: > > > > You need "set num_ide_disks=1" in /boot/boot.conf; you can also break > > to the loader commandline and issue the command directly to test it out > > first. > > This has just become a FAQ... Where is (is?) num_ide_disks > documented? Also, Nordier's (Nordier's?) "new boot blocks" tutorial > ought to mention it. The "new boot blocks" tutorial limits itself to the "boot blocks": that is, the hidden first and second stages of the bootstrap which are written to the disk by disklabel(8). The /boot/loader program really falls into a separate category; and I can't speak with any authority on /boot/boot.conf settings as I've never worked on those parts of the code. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 07:25:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA27371 for freebsd-current-outgoing; Wed, 6 Jan 1999 07:25:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from osiris.kuniv.edu.kw ([139.141.220.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA27313 for ; Wed, 6 Jan 1999 07:24:52 -0800 (PST) (envelope-from root@isis.dynip.com) Received: from osiris.kuniv.edu.kw (localhost.kuniv.edu.kw [127.0.0.1]) by osiris.kuniv.edu.kw (8.9.1/8.9.1) with SMTP id SAA08998 for ; Wed, 6 Jan 1999 18:23:52 +0300 (AST) (envelope-from root@isis.dynip.com) From: Joss Roots To: freebsd-current@FreeBSD.ORG Subject: How to Build & Run ELF Kernel Reply-To: root@isis.dynip.com X-Mailer: KMail [version 0.4.3] Date: Wed, 6 Jan 1999 18:20:19 +0300 MIME-Version: 1.0 Message-Id: <99010618235201.08944@osiris.kuniv.edu.kw> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, I recently installed a FreeBSD-30.CURRENT system and was unable to boot with the ELF kernel "MYKERNEL" the system is configured to link ELF by default any help is highly appreciated. I hear that CURRENT-people must build this as soon as possible to accomodate recent changes to come any pointers to docs, etc, is highly appreciated Thanks in advance. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 07:46:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA28733 for freebsd-current-outgoing; Wed, 6 Jan 1999 07:46:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lab321.ru (anonymous1.omsk.net.ru [62.76.128.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA28653 for ; Wed, 6 Jan 1999 07:44:28 -0800 (PST) (envelope-from kev@lab321.ru) Received: from www.lab321.ru (kev@www.lab321.ru [62.76.129.65]) by lab321.ru (8.8.8/8.9.1a) with SMTP id VAA11155 for ; Wed, 6 Jan 1999 21:43:36 +0600 (OS) Date: Wed, 6 Jan 1999 21:43:36 +0600 (OS) From: Eugeny Kuzakov To: current@FreeBSD.ORG Subject: g++ bug ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I tryed to compile this code ( it uses in groff configure): #include "confdefs.h" #ifdef __cplusplus extern "C" void exit(int); #endif extern "C" { void _exit(int); } int i; struct A { char dummy; A() { i = 1; } ~A() { if (i == 1) _exit(0); } }; A a; int main() { return 1; } Under 2.2.8-stable gcc 2.7.2.1 and 2.8.1(from ports) this code compilde Ok. And when I run it, It should return 0. Tested - Ok. Under -current - not to be Ok. gcc 2.7.2.1, gcc 2.8.1 and egcs 1.1.1 compiled Ok, but when I run it code, it return 1. -- Best wishes, Eugeny Kuzakov Laboratory 321 ( Omsk, Russia ) kev@lab321.ru ICQ#: 5885106 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 07:51:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA29399 for freebsd-current-outgoing; Wed, 6 Jan 1999 07:51:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Terry.Dorm10.NCTU.edu.tw (Terry.Dorm10.NCTU.edu.tw [140.113.122.99]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA29391 for ; Wed, 6 Jan 1999 07:51:31 -0800 (PST) (envelope-from ijliao@Terry.Dorm10.NCTU.edu.tw) Received: (from ijliao@localhost) by Terry.Dorm10.NCTU.edu.tw (8.9.1/8.9.1) id XAA26524; Wed, 6 Jan 1999 23:43:54 +0800 (CST) Date: Wed, 6 Jan 1999 23:43:54 +0800 From: Ying-Chieh Liao To: Joss Roots Cc: freebsd-current@FreeBSD.ORG Subject: Re: How to Build & Run ELF Kernel Message-ID: <19990106234354.A26489@terry.dragon2.net> References: <99010618235201.08944@osiris.kuniv.edu.kw> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <99010618235201.08944@osiris.kuniv.edu.kw>; from "Joss Roots" on Wed, Jan 06, 1999 at 18:20:19 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 06, 1999 at 18:20:19 +0300, Joss Roots wrote: > any pointers to docs, etc, is highly appreciated put this in your /etc/make.conf KERNFORMAT= elf then, cd /sys/i386/conf ; config -r MYKERNEL ; cd ../../compile/MYKERNEL make depend all install -- mailto:ijliao@dragon2.net?subject="send pgp key" to get my pgp public key key finger print : FA 38 7E 91 FA 22 FA F6 63 04 E3 B5 A1 9F 0C CD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 08:02:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00758 for freebsd-current-outgoing; Wed, 6 Jan 1999 08:02:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00753 for ; Wed, 6 Jan 1999 08:02:15 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id LAA51597; Wed, 6 Jan 1999 11:02:22 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Wed, 6 Jan 1999 11:02:22 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Ying-Chieh Liao cc: Joss Roots , freebsd-current@FreeBSD.ORG Subject: Re: How to Build & Run ELF Kernel In-Reply-To: <19990106234354.A26489@terry.dragon2.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 6 Jan 1999, Ying-Chieh Liao wrote: > On Wed, Jan 06, 1999 at 18:20:19 +0300, Joss Roots wrote: > > any pointers to docs, etc, is highly appreciated > > put this in your /etc/make.conf > KERNFORMAT= elf > > then, > cd /sys/i386/conf ; config -r MYKERNEL ; cd ../../compile/MYKERNEL > make depend all install You should also be aware that you need to install the new bootblocks, after a make world: disklabel -B -b /boot/boot1 -s /boot/boot2 disk is wd0, wd1, sd2 etc..., although could anyone clarify for me if it's possible just to do update boot1 without messing with the boot sector? or does disklabel not even really touch that? -Alfred > -- > mailto:ijliao@dragon2.net?subject="send pgp key" to get my pgp public key > key finger print : FA 38 7E 91 FA 22 FA F6 63 04 E3 B5 A1 9F 0C CD > > 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 Jan 6 08:04:52 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00929 for freebsd-current-outgoing; Wed, 6 Jan 1999 08:04:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sicily.odyssey.cs.cmu.edu (SICILY.ODYSSEY.CS.CMU.EDU [128.2.185.138]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA00924 for ; Wed, 6 Jan 1999 08:04:50 -0800 (PST) (envelope-from rvb+@sicily.odyssey.cs.cmu.edu) To: Warner Losh Cc: "Robert V. Baron" , current@FreeBSD.ORG Subject: Re: i386/conf/PCCARD References: <199901060706.AAA31404@harmony.village.org> From: "Robert V. Baron" Date: 06 Jan 1999 11:04:04 -0500 In-Reply-To: Warner Losh's message of Wed, 06 Jan 1999 00:06:31 -0700 Message-ID: Lines: 24 X-Mailer: Gnus v5.4.46/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh writes: > In message "Robert > V. Baron" writes: > : I've been wondering, of late, how well/if laptops are supported in > : -current. It seems that the configuration, PCCARD, has recently > : (since mid December) has gone away. Is this the answer? > > Laptops are well supported in -current. In the cleaning frenzy that > overtook the tree, PCCARD was removed because it was claimed to be out > of date. Nothing has taken its place, sadly, but GENERIC with a few > lines from LINT (the ones talking about card and pcic) will work > great. > > I'm running approx Jan 1 on my Libretto 50CT. > > Warner I'm not arguing whether laptops work. I have a TP 560 and have been using it. But the packaging of laptop support with the -current (and -stable) is lacking and removing PCCARD seems to be going in the wrong direction. (Example: to install on a laptop you use GENERIC and the zp/ze drivers; then do some manual magic including insalling a new kernel to switch over to a pccardd based scheme.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 08:14:53 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA01579 for freebsd-current-outgoing; Wed, 6 Jan 1999 08:14:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.clintondale.com (boris.clintondale.com [206.88.120.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA01568 for ; Wed, 6 Jan 1999 08:14:50 -0800 (PST) (envelope-from matt@clintondale.com) Received: from matt (helo=localhost) by mail.clintondale.com with local-esmtp (Exim 2.04 #2) id 0zxvat-0007IX-00; Wed, 6 Jan 1999 11:14:03 -0500 Date: Wed, 6 Jan 1999 11:14:03 -0500 (EST) From: Matt Hamilton To: jbg@masterplan.org cc: freebsd-current@FreeBSD.ORG Subject: Re: News Server In-Reply-To: <6203.915562751@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 > > I've been running a mail2news read-only gateway for a few months now. > > (I'm not gating all the lists, but do have most of them...) > > > > It's available at atomic-playboy.masterplan.org (207.167.12.181). Hi, I am working on a mailing list archive that encompases FreeBSD, Linux, NetBSD, OpenBSD, and a range of opensource projects. Would it be possible for me to bulk-pull the news articles from your server to back-fill our FreeBSD archive? Our machine is currently only of a 56k circuit at the moment during development, so I would hardly take up all your bandwidth :) Just thought I'd ask before I fire suck up :) -Matt ------------------------------------------------------------------------------- Matt Hamilton Clintondale Aviation matt@clintondale.com http://www.clintondale.com ------------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 08:43:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA04236 for freebsd-current-outgoing; Wed, 6 Jan 1999 08:43:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shell2.la.best.com (shell2.la.best.com [209.24.216.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA04227 for ; Wed, 6 Jan 1999 08:43:30 -0800 (PST) (envelope-from nugundam@shell2.la.best.com) Received: (from nugundam@localhost) by shell2.la.best.com (8.9.1/8.9.0/best.sh) id IAA15866; Wed, 6 Jan 1999 08:42:59 -0800 (PST) Message-ID: <19990106084259.C11477@la.best.com> Date: Wed, 6 Jan 1999 08:42:59 -0800 From: "Joseph T. Lee" To: Jason George , freebsd-current@FreeBSD.ORG Subject: Re: News Server References: <199901052151.OAA06423@gongshow.masterplan.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199901052151.OAA06423@gongshow.masterplan.org>; from Jason George on Tue, Jan 05, 1999 at 09:51:16PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 05, 1999 at 09:51:16PM +0000, Jason George wrote: > There are a few caveats about the NNTP version of the lists. > > 1) I'm missing about 5MB of the ~75MB I've gated since September. This > was due to inews chucking articles that quoted too much and added too > little. This wasn't a big concern for me. I recompiled inews and nnrpd This isn't a bad thing. Encourages editing by posters. :) How difficult would it be to set it with auto-moderation allows only people on a subscribed listing to read/post? Maybe, a login part for accessing the news server. This would deal with the spammer/troll problem. Otherwise, it's great that this news format idea is going places. :) -- Joseph nugundam =best=com==/==\=IIGS=/==\=Playstation=/==\=Civic HX CVT=/==\ # Anime Expo 1998 >> www.anime-expo.org/ > # Redline Games >> www.redlinegames.com/ > # Cal-Animage Epsilon >> www.best.com/~nugundam/epsilon/ > # EX: The Online World of Anime & Manga >> www.ex.org/ / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 09:02:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06804 for freebsd-current-outgoing; Wed, 6 Jan 1999 09:02:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06798 for ; Wed, 6 Jan 1999 09:02:38 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id CAA03395; Thu, 7 Jan 1999 02:01:59 +0900 (JST) Message-ID: <369396FB.E46D454@newsguy.com> Date: Thu, 07 Jan 1999 02:01:47 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Robert Nordier , current@FreeBSD.ORG Subject: Re: Trouble booting from WinNT with new boot loader References: <199901061502.RAA00693@ceia.nordier.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert Nordier wrote: > > The "new boot blocks" tutorial limits itself to the "boot blocks": > that is, the hidden first and second stages of the bootstrap which > are written to the disk by disklabel(8). > > The /boot/loader program really falls into a separate category; > and I can't speak with any authority on /boot/boot.conf settings > as I've never worked on those parts of the code. But... but... this seems to be fault of the first two stages! :-) Since we don't know how the disk types, we don't have any way of know what is the first SCSI. Because of this, one has to put: set num_ide_disks=N in the /boot/boot.conf (soon to be boot.rc). -- Daniel C. Sobral (8-DCS) dcs@newsguy.com "Heart like a Gabriel, pure and white as ivory, soul like a lucifer, black and cold as a piece of lead." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 09:10:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07925 for freebsd-current-outgoing; Wed, 6 Jan 1999 09:10:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from server.amis.net (server.amis.net [195.10.52.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07870 for ; Wed, 6 Jan 1999 09:10:06 -0800 (PST) (envelope-from blaz@gold.amis.net) Received: (from uucp@localhost) by server.amis.net (8.8.8/8.8.8) with UUCP id SAA20097 for freebsd-current@FreeBSD.ORG; Wed, 6 Jan 1999 18:09:29 +0100 (CET) Received: (qmail 266 invoked by uid 1000); 6 Jan 1999 17:07:21 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 6 Jan 1999 17:07:21 -0000 Date: Wed, 6 Jan 1999 18:07:21 +0100 (CET) From: Blaz Zupan To: ADRIAN Filipi-Martin cc: Alfred Perlstein , "Thomas T. Veldhouse" , freebsd-current@FreeBSD.ORG Subject: Re: Kernel cannot mount root with new bootblocks 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 > All in all I do agree with dumping the old blocks in favor of the > new. As a temporary work around I put "0:da(1,a)kernel" in /boot.config, > yes, boot.config. The original pposter might try this or something > similar. Yes, this actually works. I notice that the boot code tries to boot 0:da(0,a)/boot/loader. So I tried 0:da(1,a)/boot/loader which brought up the loader, but then it could not find the kernel again and I had to type boot disk1s4a:/kernel to boot the kernel, which then again failed after trying to go multiuser, because it said I'm not remounting the same root partition. Something's really broken with the boot code in this respect. I guess Alfreds solution with wiring down the devices would help as well, but for now the above solution works for me and it works without recompiling the kernel (which is painfull on a 486). Although I'm getting more and more confused by the PC architecture booting process and I'm really starting to appreciate Mr. Nordier's work ;) Blaz Zupan, blaz@medinet.si, http://home.amis.net/blaz Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 09:28:39 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09857 for freebsd-current-outgoing; Wed, 6 Jan 1999 09:28:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from galaxy.support.stream.com (galaxy.support.stream.com [208.13.180.22]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA09840; Wed, 6 Jan 1999 09:28:28 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from c063.beaverton.stream.com ([208.13.191.137]) by galaxy.support.stream.com (Lotus SMTP MTA v4.6.3 (733.2 10-16-1998)) with SMTP id 852566F1.005FDA31; Wed, 6 Jan 1999 12:26:58 -0500 Message-ID: <004c01be3999$585caa40$f301040a@c063.beaverton.stream.com> From: "Wiliam Woods" To: "jack" , "Kris Kennaway" Cc: "Bill Woods" , , Subject: Re: kdesupport11 port build problems on -current elf Date: Wed, 6 Jan 1999 09:23:52 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmmm......yea, but it looks like qt-1.40 has been taken out of the ports and qt-1.41 put in..... -----Original Message----- From: jack To: Kris Kennaway Cc: Bill Woods ; current@FreeBSD.ORG ; ports@FreeBSD.ORG Date: Wednesday, January 06, 1999 6:36 AM Subject: Re: kdesupport11 port build problems on -current elf >On Wed, 6 Jan 1999, Kris Kennaway wrote: > >> > /usr/X11R6/lib/libqt.so: undefined reference to `XShapeCombineRegion' >> > /usr/X11R6/lib/libqt.so: undefined reference to `XShapeCombineMask' >> > *** Error code 1 >> >> This seems common for ports using libqt - for some reason they don't see >> libXext in /usr/X11R6/lib (but not for everyone, apparently, since the thing >> was committed in the first place). If you add -lXext to the linker link above, >> it links fine. I don't know how to use the --rpath option suggested, but I >> suspect this is it. Any hints, anyone? > >I haven't tried the kde 1.1 stuff, but for 1.0 I could only get >it to compile using qt-1.40. > >-------------------------------------------------------------------------- >Jack O'Neill Systems Administrator / Systems Analyst >jack@germanium.xtalwind.net Crystal Wind Communications, Inc. > Finger jack@germanium.xtalwind.net for my PGP key. > PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD > enriched, vcard, HTML messages > /dev/null >-------------------------------------------------------------------------- > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 09:32:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10623 for freebsd-current-outgoing; Wed, 6 Jan 1999 09:32:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from galaxy.support.stream.com (galaxy.support.stream.com [208.13.180.22]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA10618; Wed, 6 Jan 1999 09:32:10 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from c063.beaverton.stream.com ([208.13.191.137]) by galaxy.support.stream.com (Lotus SMTP MTA v4.6.3 (733.2 10-16-1998)) with SMTP id 852566F1.006038F1; Wed, 6 Jan 1999 12:31:01 -0500 Message-ID: <005501be3999$e8eedba0$f301040a@c063.beaverton.stream.com> From: "Wiliam Woods" To: "Jeremy Lea" , "Bill Woods" Cc: "Kris Kennaway" , , Subject: Re: kdesupport11 port build problems on -current elf Date: Wed, 6 Jan 1999 09:27:54 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why shouldent I use the 11 ports yet? They are in the ports tree....and as a side note, I got the same error with the regular kdesupport port. -----Original Message----- From: Jeremy Lea To: Bill Woods Cc: Kris Kennaway ; current@FreeBSD.ORG ; ports@FreeBSD.ORG Date: Wednesday, January 06, 1999 12:59 AM Subject: Re: kdesupport11 port build problems on -current elf >Hi, > >On Tue, Jan 05, 1999 at 10:25:31PM -0800, Bill Woods wrote: >> OK, that sounds good....ahh..oh yea, what do you mean by "if you add >> -lXext to the linker link above" . What do I add and where ? > >Firstly, you shouldn't be using the 11 ports yet. If you see ports apear in >your tree without commit e-mail, then these are repository copies and >haven't been upgrded yet. Give people a little chance. > >Use this patch (sent to the maintainer several weeks ago) as >kdesupport/patches/patch-a3: > >--- QwSpriteField/Makefile.in~ Fri Nov 27 16:23:32 1998 >+++ QwSpriteField/Makefile.in Fri Nov 27 16:23:53 1998 >@@ -139,7 +139,7 @@ > # the difference between the first and the last, is the major number > # the last is the minor number > # the number in the middle is the minor-minor number >-libQwSpriteField_la_LDFLAGS = -version-info 5:2:4 -lqt -lX11 $(LIBSOCKET) >+libQwSpriteField_la_LDFLAGS = -version-info 5:2:4 -lqt -lXext -lX11 $(LIBSOCKET) > > INCLUDES = $(QT_INCLUDES) > lib_LTLIBRARIES = libQwSpriteField.la >@@ -157,7 +157,7 @@ > > noinst_PROGRAMS = example > example_SOURCES = example.cpp >-example_LDADD = libQwSpriteField.la -lqt -lX11 $(LIBSOCKET) >+example_LDADD = libQwSpriteField.la -lqt -lXext -lX11 $(LIBSOCKET) > mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs > CONFIG_HEADER = ../config.h > CONFIG_CLEAN_FILES = > >Regards, > -Jeremy > >-- > | "I could be anything I wanted to, but one things true >--+-- Never gonna be as big as Jesus, never gonna hold the world in my hand > | Never gonna be as big as Jesus, never gonna build a promised land > | But that's, that's all right, OK with me..." -Audio Adrenaline > >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 Jan 6 09:42:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA11473 for freebsd-current-outgoing; Wed, 6 Jan 1999 09:42:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from jason04.u.washington.edu (jason04.u.washington.edu [140.142.78.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA11468; Wed, 6 Jan 1999 09:42:47 -0800 (PST) (envelope-from jcwells@u.washington.edu) Received: from saul2.u.washington.edu (root@saul2.u.washington.edu [140.142.56.21]) by jason04.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA20846; Wed, 6 Jan 1999 09:42:19 -0800 Received: from S8-37-26.student.washington.edu (S8-37-26.student.washington.edu [128.208.37.26]) by saul2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA06839; Wed, 6 Jan 1999 09:42:18 -0800 (PST) Date: Wed, 6 Jan 1999 09:41:47 -0800 (PST) From: "Jason C. Wells" X-Sender: jason@s8-37-26.student.washington.edu Reply-To: "Jason C. Wells" To: Wiliam Woods cc: Jeremy Lea , Bill Woods , Kris Kennaway , current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: kdesupport11 port build problems on -current elf In-Reply-To: <005501be3999$e8eedba0$f301040a@c063.beaverton.stream.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 received this email regarding kdesupport problem report that I submitted. In my pr I believe I included a fix, but don't quote me. The pr is ports/9018. ******* Jason, >From the looks of the error messages in the PR it was dying in the Qt port build. Can you try the following and see if it helps? 1) remove any old version of libtool and re-install from the latest port? 2) do the same for the qt-1.41 port 3) try the kdesupport port again Let me know what you find. Thanks. ***** Hope this helps. Jason Wells | http://weber.u.washington.edu/~jcwells/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 09:53:52 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13376 for freebsd-current-outgoing; Wed, 6 Jan 1999 09:53:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from transfer.usit.net (transfer.usit.net [208.10.171.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13371 for ; Wed, 6 Jan 1999 09:53:49 -0800 (PST) (envelope-from Asimov@oldwarez.com) Received: from omiam (DIALUP39.TNKNO2.USIT.NET [216.80.145.39]) by transfer.usit.net (8.8.7/8.8.5) with SMTP id MAA04692 for ; Wed, 6 Jan 1999 12:53:20 -0500 (EST) Message-ID: <001601be399d$59afe160$0200a8c0@omiam.usit.net> From: "Asimov" To: Date: Wed, 6 Jan 1999 12:52:37 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG auth 1fbf5a05 subscribe freebsd-current Asimov@oldwarez.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 09:57:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13733 for freebsd-current-outgoing; Wed, 6 Jan 1999 09:57:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13720; Wed, 6 Jan 1999 09:57:10 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id RAA16414; Wed, 6 Jan 1999 17:04:20 GMT Date: Wed, 6 Jan 1999 17:02:55 +0000 (GMT) From: Doug Rabson To: Sren Schmidt cc: Kazutaka YOKOTA , sos@FreeBSD.ORG, msmith@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: syscons update - when? In-Reply-To: <199901061132.MAA05593@sos.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 Wed, 6 Jan 1999, Sren Schmidt wrote: > It seems Kazutaka YOKOTA wrote: > > As I announced before, reorganization of syscons code is under way and > > I intend to commit changes in three stages. > > > > Stage 1: keyboard driver split > > Stage 2: video driver split, splash screen > > Stage 3: other reorganization > > > > The new code has been running on my -current box for quite a while. > > > > Now, -stable branch date is coming up. The question is how much > > change we should commit before the branch? We can defer commit after > > the branch and later backport the new code from -current to -stable. > > However, there is a snug. > > > > At stage 1 and 2, the users will be forced to change their kernel > > configuration files because keyboard and video drivers become separate > > from syscons. Such change is probably too much, if suddenly > > introduced to -stable well after the branch. > > > > So, probably our options are: > > > > a) Commit stage 1 and 2 changes now. Stage 3 changes may be backported > > to -stable from -current later. > > b) Don't commit any changes now, but commit them to -current after the > > branch. Don't backport the changes to -stable at all. When the next > > branch (3.1-STABLE?) comes, let it have the new code. > > > > I prefer the option a). But, I have to expect rough ride after > > commits, as changes of this scale will have many initial glitches... > > I prefer option a) also. If option a) also includes repo-copying the code out of the i386 tree into an architecture neutral place, then I think that is the right way to go. I'd rather not perform that kind of code movement after the split. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 10:07:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15178 for freebsd-current-outgoing; Wed, 6 Jan 1999 10:07:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from second.dialup.access.net (lsmarso.dialup.access.net [166.84.254.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA15170 for ; Wed, 6 Jan 1999 10:07:03 -0800 (PST) (envelope-from larry@marso.com) Received: (from larry@localhost) by second.dialup.access.net (8.9.1/8.8.8) id MAA26104 for freebsd-current@freebsd.org; Wed, 6 Jan 1999 12:54:33 -0500 (EST) (envelope-from larry) Date: Wed, 6 Jan 1999 12:54:32 -0500 From: "Larry S. Marso" To: freebsd-current@FreeBSD.ORG Subject: bootblocks: once or each time? Message-ID: <19990106125432.K24384@marso.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.13i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I updated to 3.0-current elf a few days ago. I installed the new bootblocks. I just updated my sources again, and note that there are more changes to sys/boot. If I do a fresh buildworld, should I be installing new bootblocks again, as well as a make installworld? Best regards -- Larry S. Marso larry@marso.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 10:10:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15674 for freebsd-current-outgoing; Wed, 6 Jan 1999 10:10:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dns.webwizard.net.mx (webwizard.net.mx [148.245.50.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA15638; Wed, 6 Jan 1999 10:10:05 -0800 (PST) (envelope-from eculp@webwizard.org.mx) Received: from webwizard.org.mx (webwizard.net.mx [148.245.50.27]) by dns.webwizard.net.mx (8.9.1/8.9.1) with ESMTP id MAA63874; Wed, 6 Jan 1999 12:08:59 -0600 (CST) (envelope-from eculp@webwizard.org.mx) Message-ID: <3693A6BB.19A63949@webwizard.org.mx> Date: Wed, 06 Jan 1999 12:08:59 -0600 From: Edwin Culp X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: jack CC: Kris Kennaway , Bill Woods , current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: kdesupport11 port build problems on -current elf References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG jack wrote: > On Wed, 6 Jan 1999, Kris Kennaway wrote: > > > > /usr/X11R6/lib/libqt.so: undefined reference to `XShapeCombineRegion' > > > /usr/X11R6/lib/libqt.so: undefined reference to `XShapeCombineMask' > > > *** Error code 1 > > I just did a ln -s /usr/X11R6/lib/libXext.so.6 /usr/local/lib and problem solved. I've just left it there for updates:-) ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 10:25:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17962 for freebsd-current-outgoing; Wed, 6 Jan 1999 10:25:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mortar.carlson.com (mortar.carlson.com [208.240.12.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17957 for ; Wed, 6 Jan 1999 10:25:29 -0800 (PST) (envelope-from veldy@visi.com) Received: from mortar.carlson.com (root@localhost) by mortar.carlson.com with ESMTP id MAA02761; Wed, 6 Jan 1999 12:24:17 -0600 (CST) Received: from w142844 ([172.25.99.35]) by mortar.carlson.com with SMTP id MAA02757; Wed, 6 Jan 1999 12:24:03 -0600 (CST) Message-ID: <019f01be39a1$dc9eb8e0$236319ac@w142844.carlson.com> From: "Thomas T. Veldhouse" To: "Larry S. Marso" , Subject: Re: bootblocks: once or each time? Date: Wed, 6 Jan 1999 12:24:42 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You could go to /usr/src/sys/boot and then do: make all install clean You shouldn't need to do a build world unless some of the includes have changed. It has worked for me in the past. I am curious to know if the new boot blocks will mount root correctly or rather, will it try to mount the correct root. It seemed to ignore rootdev before and always subtracted one or from currdev (or simply default to disk1s1a). Tom Veldhouse veldy@visi.com -----Original Message----- From: Larry S. Marso To: freebsd-current@FreeBSD.ORG Date: Wednesday, January 06, 1999 12:06 PM Subject: bootblocks: once or each time? >I updated to 3.0-current elf a few days ago. I installed the new >bootblocks. > >I just updated my sources again, and note that there are more changes >to sys/boot. If I do a fresh buildworld, should I be installing new >bootblocks again, as well as a make installworld? > >Best regards >-- >Larry S. Marso >larry@marso.com > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 10:33:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18696 for freebsd-current-outgoing; Wed, 6 Jan 1999 10:33:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18691 for ; Wed, 6 Jan 1999 10:33:33 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id DAA05907; Thu, 7 Jan 1999 03:32:56 +0900 (JST) Message-ID: <3693673A.3F5F212B@newsguy.com> Date: Wed, 06 Jan 1999 22:38:02 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: "Chris D. Faulhaber" CC: current@FreeBSD.ORG Subject: Re: cannot load any lkm with ELF kernel References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Chris D. Faulhaber" wrote: > > That would be because (correct me if I'm wrong) lkm's are a.out. With an > elf kernel, use dynamically-linkable modules (kld's) located in /modules. > man kldload/kldunload/kldstat for usage. A previous message gave me the impression that you can still load a.out lkms with elf kernels (thus protecting third-party a.out module's investment). More likely, I'd think is that FreeBSD doesn't come with lkm's anymore, having all been replaced by lkds. Possibly, a revision problem exists that prevent the old lkms installed from being loaded. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com "Heart like a Gabriel, pure and white as ivory, soul like a lucifer, black and cold as a piece of lead." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 10:48:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA19840 for freebsd-current-outgoing; Wed, 6 Jan 1999 10:48:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA19835 for ; Wed, 6 Jan 1999 10:48:17 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (peter@localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Netplex) with ESMTP id CAA31937; Thu, 7 Jan 1999 02:47:22 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199901061847.CAA31937@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel C. Sobral" cc: "Chris D. Faulhaber" , current@FreeBSD.ORG Subject: Re: cannot load any lkm with ELF kernel In-reply-to: Your message of "Wed, 06 Jan 1999 22:38:02 +0900." <3693673A.3F5F212B@newsguy.com> Date: Thu, 07 Jan 1999 02:47:20 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel C. Sobral" wrote: > "Chris D. Faulhaber" wrote: > > > > That would be because (correct me if I'm wrong) lkm's are a.out. With an > > elf kernel, use dynamically-linkable modules (kld's) located in /modules. > > man kldload/kldunload/kldstat for usage. > > A previous message gave me the impression that you can still load > a.out lkms with elf kernels (thus protecting third-party a.out > module's investment). More likely, I'd think is that FreeBSD doesn't > come with lkm's anymore, having all been replaced by lkds. If people are worried about OSS, I've been talking to them and have suggested some sample code and given them a few hints. If things work out, there should have a KLD OSS module within a couple of days. KLD modules of either format can be loaded on either format kernel. LKM's cannot. > Possibly, a revision problem exists that prevent the old lkms > installed from being loaded. Yes. It's quite likely that any old LKM's laying around would need to be recompiled soon anyway, depending on whether the shared signal stuff is cleaned up and becomes default so that we can support kernel-assisted threads. 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 Jan 6 11:06:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA22294 for freebsd-current-outgoing; Wed, 6 Jan 1999 11:06:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA22284 for ; Wed, 6 Jan 1999 11:06:29 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id UAA03422; Wed, 6 Jan 1999 20:11:07 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Wed, 6 Jan 1999 20:11:07 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Mike Smith cc: "Daniel C. Sobral" , current@FreeBSD.ORG, "Jordan K. Hubbard" Subject: Re: /boot/boot.rc && /boot/rc.d In-Reply-To: <199901052135.NAA01045@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 5 Jan 1999, Mike Smith wrote: > Modules live in /modules as *.ko (active) and *.kx (inactive) > module initialiser scripts live as separate files alongside the > modules, ie. as *.kinit. Load procedure is to simply scan the I'd suggest using *.ki suffix - it's easier to handle with such crippled FS-es as DOSFS... Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 11:09:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA22770 for freebsd-current-outgoing; Wed, 6 Jan 1999 11:09:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA22765 for ; Wed, 6 Jan 1999 11:09:56 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id LAA20245; Wed, 6 Jan 1999 11:09:28 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id LAA38398; Wed, 6 Jan 1999 11:09:27 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <13971.29268.338874.138338@slice.parview.com> Date: Wed, 06 Jan 1999 11:09:27 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: hgoldste@bbs.mpcs.com Subject: Re: ELF interpreter /usr/lib/libc.so.1 not found (on 3.0-CURRENT Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 06-Jan-99 hgoldste@bbs.mpcs.com wrote: > > cc -v hello.c > > Yow lots of extra stuff. Where are these overrides set in cc/gcc? Mostly in "/usr/src/contrib/gcc/config/i386/freebsd.h", in the *_SPEC macros. To learn how to decipher the specs, read the giant comment in "/usr/src/contrib/gcc/gcc.c", around line 323. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 11:20:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA23903 for freebsd-current-outgoing; Wed, 6 Jan 1999 11:20:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA23894 for ; Wed, 6 Jan 1999 11:20:49 -0800 (PST) (envelope-from narvi@haldjas.folklore.ee) Received: from haldjas.folklore.ee (haldjas.folklore.ee [172.17.2.1] (may be forged)) by haldjas.folklore.ee (8.8.8/8.8.4) with SMTP id VAA25187 for ; Wed, 6 Jan 1999 21:20:15 +0200 (EET) Date: Wed, 6 Jan 1999 21:20:15 +0200 (EET) From: Narvi To: current@FreeBSD.ORG Subject: X & loading modules Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone tried to have the X server load some extension or pointer device shared object? My attempts fail with unknown error (when trying to load pex5). Environement - relataively new current + XFree 3.3.3 Sander There is no love, no good, no happiness and no future - all these are just illusions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 11:21:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA23989 for freebsd-current-outgoing; Wed, 6 Jan 1999 11:21:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from schizo.cdsnet.net (schizo.cdsnet.net [204.118.244.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA23982 for ; Wed, 6 Jan 1999 11:21:21 -0800 (PST) (envelope-from mrcpu@internetcds.com) Received: from localhost (mrcpu@localhost) by schizo.cdsnet.net (8.8.8/8.7.3) with SMTP id LAA19801 for ; Wed, 6 Jan 1999 11:15:56 -0800 (PST) Date: Wed, 6 Jan 1999 11:15:46 -0800 (PST) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: current@FreeBSD.ORG Subject: mergemaster should be merged in to the main tree. Message-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 utility is too valuable for all the update not to at least have a mention of it. At the very least, references should be made to it in /usr/src/Makefile as part of the conversion process, and inthe /usr/src/UPDATING file. I would be willing to get permission from the author if people think it's a good idea. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 11:25:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA24406 for freebsd-current-outgoing; Wed, 6 Jan 1999 11:25:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sicily.odyssey.cs.cmu.edu (SICILY.ODYSSEY.CS.CMU.EDU [128.2.185.138]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA24401 for ; Wed, 6 Jan 1999 11:25:29 -0800 (PST) (envelope-from rvb+@sicily.odyssey.cs.cmu.edu) To: Robert Nordier Cc: "Daniel C. Sobral" , mike@smith.net.au, current@FreeBSD.ORG Subject: Re: new boot loader ... documentation References: <199901061502.RAA00693@ceia.nordier.com> From: "Robert V. Baron" Date: 06 Jan 1999 14:24:36 -0500 In-Reply-To: Robert Nordier's message of Wed, 6 Jan 1999 17:02:30 +0200 (SAT) Message-ID: Lines: 10 X-Mailer: Gnus v5.4.46/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert Nordier writes: > Daniel C. Sobral wrote: > > The "new boot blocks" tutorial limits itself to the "boot blocks": > that is, the hidden first and second stages of the bootstrap which > are written to the disk by disklabel(8). What would be equally interesting is a tutorial/overview on btxld, btxldr, and btx. How full an OS is btx? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 11:38:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25953 for freebsd-current-outgoing; Wed, 6 Jan 1999 11:38:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25948 for ; Wed, 6 Jan 1999 11:38:28 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id UAA08299; Wed, 6 Jan 1999 20:41:59 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Wed, 6 Jan 1999 20:41:59 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: "Robert V. Baron" cc: Robert Nordier , "Daniel C. Sobral" , mike@smith.net.au, current@FreeBSD.ORG Subject: Re: new boot loader ... documentation 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 6 Jan 1999, Robert V. Baron wrote: > Robert Nordier writes: > > > Daniel C. Sobral wrote: > > > > The "new boot blocks" tutorial limits itself to the "boot blocks": > > that is, the hidden first and second stages of the bootstrap which > > are written to the disk by disklabel(8). > > What would be equally interesting is a tutorial/overview on btxld, > btxldr, and btx. How full an OS is btx? Oh, yes, pleeez... Write something about it - even quite general concepts would be helpful, not to mention the usage and arguments. Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 12:04:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA00626 for freebsd-current-outgoing; Wed, 6 Jan 1999 12:04:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from server.noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA00619 for ; Wed, 6 Jan 1999 12:04:44 -0800 (PST) (envelope-from fanf@demon.net) Received: by server.noc.demon.net; id UAA10328; Wed, 6 Jan 1999 20:04:15 GMT Received: from fanf.noc.demon.net(195.11.55.83) by inside.noc.demon.net via smap (3.2) id xma010306; Wed, 6 Jan 99 20:04:00 GMT Received: from fanf by fanf.noc.demon.net with local (Exim 1.73 #2) id 0zxzBQ-0007Tt-00; Wed, 6 Jan 1999 20:04:00 +0000 To: current@FreeBSD.ORG From: Tony Finch Subject: Squid + linuxthreads in action Message-Id: Date: Wed, 6 Jan 1999 20:04:00 +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We've been trying out Squid compiled to use async-io with linuxthreads on FreeBSD-current today. It required a bit of fiddling to work around incorrect assumptions in Squid's build and configuration stuff: To CFLAGS I added: -D_THREAD_SAFE -DLINUXTHREADS -I/usr/local/include To XTRA_LIBS I added: -kthread I modified src/aiops.c and src/main.c to test for _SQUID_LINUX_THREADS_ instead of (defined(_SQUID_LINUX_) && USE_ASYNC_IO) and altered include/config.h.in to define _SQUID_LINUX_THREADS_ in the appropriate situations. After running `configure` I had to edit src/Makefile to remove -pthread from LDFLAGS. (It would be better for the long term to alter configure.in and rebuild configure, but...) Squid then compiles and runs OK, apart from a few things: When the parent Squid process shuts down it leaves behind a pile of orphan processes (the async-io handler threads). A glance at the aio code reveals that Squid expects the pthread library to kill them -- they just loop indefinitely. They also keep the listen socket open, so the RunCache script can't restart Squid :-( Also, it crashed hard after several minutes under load. This might have been due to us using softupdates with ccd rather than the threads stuff. Tony. -- f.a.n.finch dot@dotat.at fanf@demon.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 12:14:42 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA02236 for freebsd-current-outgoing; Wed, 6 Jan 1999 12:14:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA02224 for ; Wed, 6 Jan 1999 12:14:36 -0800 (PST) (envelope-from randy@psg.com) Received: from localhost (5838 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Wed, 6 Jan 1999 12:14:06 -0800 (PST) (Smail-3.2.0.101 1997-Dec-17 #1 built 1998-Oct-13) Message-Id: Date: Wed, 6 Jan 1999 12:14:06 -0800 (PST) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Thomas T. Veldhouse" Cc: freebsd-current@FreeBSD.ORG Subject: Re: bootblocks: once or each time? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You could go to /usr/src/sys/boot and then do: make all install clean people keep telling me this. but, on a completely new cvsupped source of 98.12.31 i get the appended. rip.psg.com:/usr/src/sys/boot# make clean ===> ficl rm -f a.out dict.o ficl.o math64.o stack.o sysdep.o vm.o words.o softcore.o dict.o.tmp ficl.o.tmp math64.o.tmp stack.o.tmp sysdep.o.tmp vm.o.tmp words.o.tmp softcore.o.tmp softcore.c testmain rm -f libficl.a # llib-lficl.ln rm -f dict.po ficl.po math64.po stack.po sysdep.po vm.po words.po softcore.po dict.po.tmp ficl.po.tmp math64.po.tmp stack.po.tmp sysdep.po.tmp vm.po.tmp words.po.tmp softcore.po.tmp libficl_p.a rm -f dict.so ficl.so math64.so stack.so sysdep.so vm.so words.so softcore.so dict.so.tmp ficl.so.tmp math64.so.tmp stack.so.tmp sysdep.so.tmp vm.so.tmp words.so.tmp softcore.so.tmp libficl.so.* libficl.so libficl_pic.a ===> i386 ===> i386/boot0 rm -f boot0.out boot0.o boot0 ===> i386/btx ===> i386/btx/btx rm -f btx btx.out btx.o ===> i386/btx/btxldr rm -f btxldr btxldr.out btxldr.o ===> i386/btx/lib rm -f a.out btxcsu.o btxsys.o btxv86.o btxcsu.o.tmp btxsys.o.tmp btxv86.o.tmp crt0.o rm -f lib.a # llib-l.ln rm -f btxcsu.po btxsys.po btxv86.po btxcsu.po.tmp btxsys.po.tmp btxv86.po.tmp lib_p.a rm -f btxcsu.so btxsys.so btxv86.so btxcsu.so.tmp btxsys.so.tmp btxv86.so.tmp lib.so.* lib.so lib_pic.a ===> i386/boot2 rm -f boot1 boot1.out boot1.o boot2.ldr boot2.bin boot2.ld boot2.out boot2.o sio.o boot2 ===> i386/libi386 rm -f a.out aout_freebsd.o biosdisk.o biosmem.o biospnp.o biospci.o bootinfo.o comconsole.o devicename.o elf_freebsd.o gatea20.o i386_copy.o i386_module.o time.o vidconsole.o aout_freebsd.o.tmp biosdisk.o.tmp biosmem.o.tmp biospnp.o.tmp biospci.o.tmp bootinfo.o.tmp comconsole.o.tmp devicename.o.tmp elf_freebsd.o.tmp gatea20.o.tmp i386_copy.o.tmp i386_module.o.tmp time.o.tmp vidconsole.o.tmp machine rm -f libi386.a # llib-li386.ln rm -f aout_freebsd.po biosdisk.po biosmem.po biospnp.po biospci.po bootinfo.po comconsole.po devicename.po elf_freebsd.po gatea20.po i386_copy.po i386_module.po time.po vidconsole.po aout_freebsd.po.tmp biosdisk.po.tmp biosmem.po.tmp biospnp.po.tmp biospci.po.tmp bootinfo.po.tmp comconsole.po.tmp devicename.po.tmp elf_freebsd.po.tmp gatea20.po.tmp i386_copy.po.tmp i386_module.po.tmp time.po.tmp vidconsole.po.tmp libi386_p.a rm -f aout_freebsd.so biosdisk.so biosmem.so biospnp.so biospci.so bootinfo.so comconsole.so devicename.so elf_freebsd.so gatea20.so i386_copy.so i386_module.so time.so vidconsole.so aout_freebsd.so.tmp biosdisk.so.tmp biosmem.so.tmp biospnp.so.tmp biospci.so.tmp bootinfo.so.tmp comconsole.so.tmp devicename.so.tmp elf_freebsd.so.tmp gatea20.so.tmp i386_copy.so.tmp i386_module.so.tmp time.so.tmp vidconsole.so.tmp libi386.so.* libi386.so libi386_pic.a ===> i386/loader rm -f vers.c vers.o loader.list loader.bin loader.sym loader.help loader main.o conf.o bcache.o boot.o commands.o console.o devopen.o interp.o interp_backslash.o interp_parse.o load_aout.o load_elf.o ls.o misc.o module.o panic.o isapnp.o pnp.o interp_forth.o machine rip.psg.com:/usr/src/sys/boot# make all ===> ficl Warning: Object directory not changed from original /usr/src/sys/boot/ficl cc -O -pipe -I/usr/src/sys/boot/ficl -c dict.c -o dict.o cc -O -pipe -I/usr/src/sys/boot/ficl -c ficl.c -o ficl.o cc -O -pipe -I/usr/src/sys/boot/ficl -c math64.c -o math64.o cc -O -pipe -I/usr/src/sys/boot/ficl -c stack.c -o stack.o cc -O -pipe -I/usr/src/sys/boot/ficl -c sysdep.c -o sysdep.o cc -O -pipe -I/usr/src/sys/boot/ficl -c vm.c -o vm.o cc -O -pipe -I/usr/src/sys/boot/ficl -c words.c -o words.o (cd /usr/src/sys/boot/ficl/softwords; perl softcore.pl softcore.fr jhlocal.fr marker.fr) > softcore.c cc -O -pipe -I/usr/src/sys/boot/ficl -c softcore.c -o softcore.o building standard ficl library ranlib libficl.a ===> i386 ===> i386/boot0 Warning: Object directory not changed from original /usr/src/sys/boot/i386/boot0 (cd /usr/src/sys/boot/i386/boot0; m4 -DFLAGS=0x0 -DTICKS=0xb6 boot0.m4 boot0.s) | as -o boot0.o ld -N -s -T 0x600 -o boot0.out boot0.o dd if=boot0.out of=boot0 ibs=32 skip=1 16+0 records in 1+0 records out 512 bytes transferred in 0.000264 secs (1939037 bytes/sec) ===> i386/btx ===> i386/btx/btx (cd /usr/src/sys/boot/i386/btx/btx; m4 btx.m4 btx.s) | as -o btx.o ld -nostdlib -N -s -T 0x9000 -o btx.out btx.o dd if=btx.out of=btx ibs=32 skip=1 54+1 records in 3+1 records out 1744 bytes transferred in 0.000620 secs (2812869 bytes/sec) Warning: Object directory not changed from original /usr/src/sys/boot/i386/btx/btx ===> i386/btx/btxldr cc --assembler-with-cpp -c -o btxldr.o /usr/src/sys/boot/i386/btx/btxldr/btxldr.s ld -nostdlib -N -s -T 0x100000 -o btxldr.out btxldr.o dd if=btxldr.out of=btxldr ibs=32 skip=1 37+1 records in 2+1 records out 1200 bytes transferred in 0.000471 secs (2547793 bytes/sec) Warning: Object directory not changed from original /usr/src/sys/boot/i386/btx/btxldr ===> i386/btx/lib as -elf -o btxcsu.o btxcsu.s as -elf -o btxsys.o btxsys.s as -elf -o btxv86.o btxv86.s ld -elf -i -o crt0.o btxcsu.o btxsys.o btxv86.o Warning: Object directory not changed from original /usr/src/sys/boot/i386/btx/lib ===> i386/boot2 (cd /usr/src/sys/boot/i386/boot2; m4 boot1.m4 boot1.s) | as -o boot1.o ld -nostdlib -static -N -e start -Ttext 0x7c00 -o boot1.out boot1.o objcopy -S -O binary boot1.out boot1 objcopy: could not exec aout/objcopy in /usr/libexec: No such file or directory *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 12:19:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA02848 for freebsd-current-outgoing; Wed, 6 Jan 1999 12:19:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-24-dbn.dial-up.net [196.34.155.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA02818 for ; Wed, 6 Jan 1999 12:19:29 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id WAA02147; Wed, 6 Jan 1999 22:18:13 +0200 (SAT) From: Robert Nordier Message-Id: <199901062018.WAA02147@ceia.nordier.com> Subject: Re: Trouble booting from WinNT with new boot loader In-Reply-To: <369396FB.E46D454@newsguy.com> from "Daniel C. Sobral" at "Jan 7, 99 02:01:47 am" To: dcs@newsguy.com (Daniel C. Sobral) Date: Wed, 6 Jan 1999 22:18:11 +0200 (SAT) Cc: rnordier@nordier.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel C. Sobral wrote: > Robert Nordier wrote: > > > > The "new boot blocks" tutorial limits itself to the "boot blocks": > > that is, the hidden first and second stages of the bootstrap which > > are written to the disk by disklabel(8). > > > > The /boot/loader program really falls into a separate category; > > and I can't speak with any authority on /boot/boot.conf settings > > as I've never worked on those parts of the code. > > But... but... this seems to be fault of the first two stages! :-) Except when operating in "compatibility mode" (ie. like the old boot blocks), all the first two stages do is pass control to the third stage (/boot/loader). It is not a part of their intended function to analyze the hardware on /boot/loader's behalf. :) > Since we don't know how the disk types, we don't have any way of > know what is the first SCSI. Because of this, one has to put: > > set num_ide_disks=N > > in the /boot/boot.conf (soon to be boot.rc). -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 12:19:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA02887 for freebsd-current-outgoing; Wed, 6 Jan 1999 12:19:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA02540 for ; Wed, 6 Jan 1999 12:17:09 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.10 #1) id 0zxzE1-00027c-00; Wed, 6 Jan 1999 22:06:41 +0200 From: Sheldon Hearn To: Jaye Mathisen cc: current@FreeBSD.ORG Subject: Re: mergemaster should be merged in to the main tree. In-reply-to: Your message of "Wed, 06 Jan 1999 11:15:46 PST." Date: Wed, 06 Jan 1999 22:06:41 +0200 Message-ID: <8159.915653201@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 06 Jan 1999 11:15:46 PST, Jaye Mathisen wrote: > I would be willing to get permission from the author if people think it's > a good idea. HINT: find out who the author is, then search the FreeBSD web page for mention of him. :-) 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 Jan 6 12:23:22 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA03354 for freebsd-current-outgoing; Wed, 6 Jan 1999 12:23:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA03347 for ; Wed, 6 Jan 1999 12:23:19 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.1/8.9.1) id OAA01855; Wed, 6 Jan 1999 14:22:40 -0600 (CST) (envelope-from dick) Date: Wed, 6 Jan 1999 14:22:40 -0600 From: "Richard Seaman, Jr." To: Tony Finch Cc: current@FreeBSD.ORG Subject: Re: Squid + linuxthreads in action Message-ID: <19990106142240.A375@tar.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Tony Finch on Wed, Jan 06, 1999 at 08:04:00PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 06, 1999 at 08:04:00PM +0000, Tony Finch wrote: > When the parent Squid process shuts down it leaves behind a pile of > orphan processes (the async-io handler threads). A glance at the aio > code reveals that Squid expects the pthread library to kill them -- > they just loop indefinitely. They also keep the listen socket open, so > the RunCache script can't restart Squid :-( A clarification question -- the async-io threads you're referring to are threads created with pthread_create from the linux threads library, and not threads created by the FreeBSD aio routines, correct? If so, this would indicate a bug in the linux threads port and/or the shared signal handling code -- all threads are supposed to be killed when the "main thread" exits. -- Richard Seamman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 12:57:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07603 for freebsd-current-outgoing; Wed, 6 Jan 1999 12:57:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-2-dbn.dial-up.net [196.34.155.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07598 for ; Wed, 6 Jan 1999 12:57:00 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id WAA02578; Wed, 6 Jan 1999 22:55:34 +0200 (SAT) From: Robert Nordier Message-Id: <199901062055.WAA02578@ceia.nordier.com> Subject: Re: Trouble booting from WinNT with new boot loader In-Reply-To: <19990106075334.A715@paert.tse-online.de> from Andreas Braukmann at "Jan 6, 99 07:53:34 am" To: braukmann@tse-online.de (Andreas Braukmann) Date: Wed, 6 Jan 1999 22:55:31 +0200 (SAT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id MAA07599 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andreas Braukmann wrote: > I'm having a quite similar problem, but I have to suppose that the > num_ide-thingie won't help. > My home-system purely scsi-based with two disks (2 x IBM DDRS 9 GB); > the disks are partitioned^h^h^h^h^h^h^h^h^h^h^hsliced like this: > > > :: paert# fdisk da0 > :: ******* Working on device /dev/rda0 ******* > [...] > :: Media sector size is 512 > :: Warning: BIOS sector numbering starts with sector 1 > :: Information from DOS bootblock is: > :: The data for partition 1 is: > :: sysid 6,(Primary 'big' DOS (> 32MB)) > :: start 63, size 1060227 (517 Meg), flag 80 (active) > :: beg: cyl 0/ sector 1/ head 1; > :: end: cyl 65/ sector 63/ head 254 > :: The data for partition 2 is: > :: sysid 5,(Extended DOS) > :: start 1060290, size 7405965 (3616 Meg), flag 0 > :: beg: cyl 66/ sector 1/ head 0; > :: end: cyl 526/ sector 63/ head 254 > :: The data for partition 3 is: > :: sysid 165,(FreeBSD/NetBSD/386BSD) > :: start 8466255, size 9381960 (4581 Meg), flag 0 > :: beg: cyl 527/ sector 1/ head 0; > :: end: cyl 1023/ sector 63/ head 254 > > :: paert# fdisk da1 > :: ******* Working on device /dev/rda1 ******* > [...} > :: Media sector size is 512 > :: Warning: BIOS sector numbering starts with sector 1 > :: Information from DOS bootblock is: > :: The data for partition 1 is: > :: sysid 165,(FreeBSD/NetBSD/386BSD) > :: start 63, size 12578832 (6142 Meg), flag 80 (active) > :: beg: cyl 0/ sector 1/ head 1; > :: end: cyl 782/ sector 63/ head 254 > :: The data for partition 2 is: > :: sysid 5,(Extended DOS) > :: start 12578895, size 3871665 (1890 Meg), flag 0 > :: beg: cyl 783/ sector 1/ head 0; > :: end: cyl 1023/ sector 63/ head 254 > > ... and partitioned as :: paert# disklabel da0 > :: # size offset fstype [fsize bsize bps/cpg] > :: b: 786432 2097152 swap # (Cyl. 130*- 179*) > :: c: 9381960 0 unused 0 0 # (Cyl. 0 - 583) > :: e: 2097152 0 4.2BSD 0 0 0 # (Cyl. 0 - 130*) > :: f: 6498376 2883584 4.2BSD 0 0 0 # (Cyl. 179*- 583*) > > > :: paert# disklabel da1 > :: # size offset fstype [fsize bsize bps/cpg] > :: a: 524288 0 4.2BSD 0 0 0 # (Cyl. 0 - 32*) > :: b: 786432 524288 swap # (Cyl. 32*- 81*) > :: c: 12578832 0 unused 0 0 # (Cyl. 0 - 782*) > :: e: 2097152 1310720 4.2BSD 0 0 0 # (Cyl. 81*- 212*) > :: f: 2097152 3407872 4.2BSD 0 0 0 # (Cyl. 212*- 342*) > :: g: 7073808 5505024 4.2BSD 0 0 0 # (Cyl. 342*- 782*) > > > I'm used to boot the system by the NT BootLoader (since fbsdboot chokes > on vm86 ...). The (freebsd) root filesystem lives on da1s1a. > Both bsd-slices are disklabeled to the new blocks, too. > > I made an entry in the NT boot.ini for the new fbsd bootblock and > the system boots. ... But the new boot block gives the warning > 'no ufs' first. It seems to me, that the boot-code just tries to make > use of the first partitions in the first found freebsd-slice (da0s3) > for going on. (e.g. looking for /boot/* ) > Since the da0s3b partition is a swap-partition, .... this approach > has to fail ... The obvious approach seems to be to boot da1, but I assume you can't tell NT BootLoader to do that. The trouble with a setup like this is that it's not compatible with default bootblock behavior, and there's also no place to put a /boot.config to change that behavior. You could patch /sys/boot/i386/boot2/boot2.c to look for everything on da1, I guess. But the basic problem seems to be that you're trying to boot from an unbootable disk. (If the root filesystem is on da1, you need to boot da1 not da0.) -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 12:59:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08083 for freebsd-current-outgoing; Wed, 6 Jan 1999 12:59:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA08076; Wed, 6 Jan 1999 12:59:05 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id MAA04732; Wed, 6 Jan 1999 12:46:12 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdWZ4716; Wed Jan 6 20:46:04 1999 Date: Wed, 6 Jan 1999 12:45:59 -0800 (PST) From: Julian Elischer To: S?ren Schmidt cc: Kazutaka YOKOTA , sos@FreeBSD.ORG, msmith@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: syscons update - when? In-Reply-To: <199901061132.MAA05593@sos.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id MAA08077 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG option a in my opinion.. On Wed, 6 Jan 1999, S?ren Schmidt wrote: > It seems Kazutaka YOKOTA wrote: > > As I announced before, reorganization of syscons code is under way and > > I intend to commit changes in three stages. > > > > Stage 1: keyboard driver split > > Stage 2: video driver split, splash screen > > Stage 3: other reorganization > > > > The new code has been running on my -current box for quite a while. > > > > Now, -stable branch date is coming up. The question is how much > > change we should commit before the branch? We can defer commit after > > the branch and later backport the new code from -current to -stable. > > However, there is a snug. > > > > At stage 1 and 2, the users will be forced to change their kernel > > configuration files because keyboard and video drivers become separate > > from syscons. Such change is probably too much, if suddenly > > introduced to -stable well after the branch. > > > > So, probably our options are: > > > > a) Commit stage 1 and 2 changes now. Stage 3 changes may be backported > > to -stable from -current later. > > b) Don't commit any changes now, but commit them to -current after the > > branch. Don't backport the changes to -stable at all. When the next > > branch (3.1-STABLE?) comes, let it have the new code. > > > > I prefer the option a). But, I have to expect rough ride after > > commits, as changes of this scale will have many initial glitches... > > I prefer option a) also. > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Søren Schmidt (sos@freebsd.org) FreeBSD Core Team member > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 13:05:39 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08609 for freebsd-current-outgoing; Wed, 6 Jan 1999 13:05:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from server.noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA08604 for ; Wed, 6 Jan 1999 13:05:38 -0800 (PST) (envelope-from fanf@demon.net) Received: by server.noc.demon.net; id VAA14373; Wed, 6 Jan 1999 21:05:09 GMT Received: from fanf.noc.demon.net(195.11.55.83) by inside.noc.demon.net via smap (3.2) id xmaa14370; Wed, 6 Jan 99 21:05:07 GMT Received: from fanf by fanf.noc.demon.net with local (Exim 1.73 #2) id 0zy08Z-0007Wm-00; Wed, 6 Jan 1999 21:05:07 +0000 To: current@FreeBSD.ORG From: Tony Finch Subject: Re: Squid + linuxthreads in action In-Reply-To: <19990106142240.A375@tar.com> References: Message-Id: Date: Wed, 6 Jan 1999 21:05:07 +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Richard Seaman, Jr." wrote: >On Wed, Jan 06, 1999 at 08:04:00PM +0000, Tony Finch wrote: > >> When the parent Squid process shuts down it leaves behind a pile of >> orphan processes (the async-io handler threads). A glance at the aio >> code reveals that Squid expects the pthread library to kill them -- >> they just loop indefinitely. > >A clarification question -- the async-io threads you're referring to >are threads created with pthread_create from the linux threads library, >and not threads created by the FreeBSD aio routines, correct? That's right. (The aio_* routines use threads? I thought they were just syscalls.) >If so, this would indicate a bug in the linux threads port and/or the >shared signal handling code -- all threads are supposed to be killed >when the "main thread" exits. That's what it looks like. Tony. -- f.a.n.finch dot@dotat.at fanf@demon.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 13:10:52 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09312 for freebsd-current-outgoing; Wed, 6 Jan 1999 13:10:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa15-59.ix.netcom.com [207.93.148.59]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA09304 for ; Wed, 6 Jan 1999 13:10:49 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.1/8.8.8) id NAA90881; Wed, 6 Jan 1999 13:09:46 -0800 (PST) (envelope-from tomdean) Date: Wed, 6 Jan 1999 13:09:46 -0800 (PST) Message-Id: <199901062109.NAA90881@ix.netcom.com> From: Thomas Dean To: randy@psg.com CC: freebsd-current@FreeBSD.ORG In-reply-to: (message from Randy Bush on Wed, 6 Jan 1999 12:14:06 -0800 (PST)) Subject: Re: bootblocks: once or each time? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had the objcopy problem, BEFORE I converted to elf. You have to get the binaries to elf first. tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 13:18:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09878 for freebsd-current-outgoing; Wed, 6 Jan 1999 13:18:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA09873 for ; Wed, 6 Jan 1999 13:18:01 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.1/8.9.1) id PAA01088 for current@FreeBSD.ORG; Wed, 6 Jan 1999 15:17:32 -0600 (CST) (envelope-from dick) Date: Wed, 6 Jan 1999 15:17:32 -0600 From: "Richard Seaman, Jr." To: current@FreeBSD.ORG Subject: Re: Squid + linuxthreads in action Message-ID: <19990106151732.A752@tar.com> References: <19990106142240.A375@tar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Tony Finch on Wed, Jan 06, 1999 at 09:05:07PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 06, 1999 at 09:05:07PM +0000, Tony Finch wrote: > "Richard Seaman, Jr." wrote: > >On Wed, Jan 06, 1999 at 08:04:00PM +0000, Tony Finch wrote: > > > >> When the parent Squid process shuts down it leaves behind a pile of > >> orphan processes (the async-io handler threads). A glance at the aio > >> code reveals that Squid expects the pthread library to kill them -- > >> they just loop indefinitely. > > > >A clarification question -- the async-io threads you're referring to > >are threads created with pthread_create from the linux threads library, > >and not threads created by the FreeBSD aio routines, correct? > > That's right. (The aio_* routines use threads? I thought they were > just syscalls.) In a sense they are just syscalls. But I think they use "kernel threads" inside the kernel. I'm not sure the threads are accessible in user space. > >If so, this would indicate a bug in the linux threads port and/or the > >shared signal handling code -- all threads are supposed to be killed > >when the "main thread" exits. > > That's what it looks like. Ok. I'll try to work on it. -- Richard Seamman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 13:18:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09962 for freebsd-current-outgoing; Wed, 6 Jan 1999 13:18:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-58-dbn.dial-up.net [196.34.155.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA09950 for ; Wed, 6 Jan 1999 13:18:24 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id XAA02647; Wed, 6 Jan 1999 23:15:54 +0200 (SAT) From: Robert Nordier Message-Id: <199901062115.XAA02647@ceia.nordier.com> Subject: Re: bootblocks: once or each time? In-Reply-To: <19990106125432.K24384@marso.com> from "Larry S. Marso" at "Jan 6, 99 12:54:32 pm" To: larry@marso.com (Larry S. Marso) Date: Wed, 6 Jan 1999 23:15:52 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Larry S. Marso wrote: > I updated to 3.0-current elf a few days ago. I installed the new > bootblocks. > > I just updated my sources again, and note that there are more changes > to sys/boot. If I do a fresh buildworld, should I be installing new > bootblocks again, as well as a make installworld? If /boot/boot1 or /boot/boot2 change, you'll need to do a disklabel -B $DISK_OR_SLICE if you want to update the bootblocks you're actually using. The /boot/boot[12] files themselves aren't executed: they're just data for disklabel, which creates hidden boot *blocks* at the start of the disk/slice. Apart from boot1/boot2 (and boot0, which is another special case), the other sys/boot code just needs a "make installworld", or equivalent. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 13:20:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10062 for freebsd-current-outgoing; Wed, 6 Jan 1999 13:20:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA10057 for ; Wed, 6 Jan 1999 13:19:57 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA05466; Wed, 6 Jan 1999 13:10:04 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdUk5442; Wed Jan 6 21:09:50 1999 Date: Wed, 6 Jan 1999 13:09:43 -0800 (PST) From: Julian Elischer To: Robert Nordier cc: Andreas Braukmann , current@FreeBSD.ORG Subject: Re: Trouble booting from WinNT with new boot loader In-Reply-To: <199901062055.WAA02578@ceia.nordier.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is exactly why at whistle we use the 2nd block of the first disk to store this stuff. (see 'nextboot(8)') the bootblocks on da0 load a default from da0-block1, which specify: da(1,........ I am thinking of adding code to actually make the 2nd block require to be in it's own slice type (not 165) so that it is marked as being in-use rather than using a 'free' block like we do now.. I've added a 4th slice below that shows what it would look like.... what do you think? julian On Wed, 6 Jan 1999, Robert Nordier wrote: > Andreas Braukmann wrote: > > > I'm having a quite similar problem, but I have to suppose that the > > num_ide-thingie won't help. > > My home-system purely scsi-based with two disks (2 x IBM DDRS 9 GB); > > the disks are partitioned^h^h^h^h^h^h^h^h^h^h^hsliced like this: > > > > > > :: paert# fdisk da0 > > :: ******* Working on device /dev/rda0 ******* > > [...] > > :: Media sector size is 512 > > :: Warning: BIOS sector numbering starts with sector 1 > > :: Information from DOS bootblock is: > > :: The data for partition 1 is: > > :: sysid 6,(Primary 'big' DOS (> 32MB)) > > :: start 63, size 1060227 (517 Meg), flag 80 (active) > > :: beg: cyl 0/ sector 1/ head 1; > > :: end: cyl 65/ sector 63/ head 254 > > :: The data for partition 2 is: > > :: sysid 5,(Extended DOS) > > :: start 1060290, size 7405965 (3616 Meg), flag 0 > > :: beg: cyl 66/ sector 1/ head 0; > > :: end: cyl 526/ sector 63/ head 254 > > :: The data for partition 3 is: > > :: sysid 165,(FreeBSD/NetBSD/386BSD) > > :: start 8466255, size 9381960 (4581 Meg), flag 0 > > :: beg: cyl 527/ sector 1/ head 0; > > :: end: cyl 1023/ sector 63/ head 254 The data for partition 3 is: sysid 201,(FreeBSD bootspec) start 1, size 1 (0 Meg), flag 0 beg: cyl 0/ sector 2/ head 0; end: cyl 0/ sector 2/ head 0 > > > > :: paert# fdisk da1 > > :: ******* Working on device /dev/rda1 ******* > > [...} > > :: Media sector size is 512 > > :: Warning: BIOS sector numbering starts with sector 1 > > :: Information from DOS bootblock is: > > :: The data for partition 1 is: > > :: sysid 165,(FreeBSD/NetBSD/386BSD) > > :: start 63, size 12578832 (6142 Meg), flag 80 (active) > > :: beg: cyl 0/ sector 1/ head 1; > > :: end: cyl 782/ sector 63/ head 254 > > :: The data for partition 2 is: > > :: sysid 5,(Extended DOS) > > :: start 12578895, size 3871665 (1890 Meg), flag 0 > > :: beg: cyl 783/ sector 1/ head 0; > > :: end: cyl 1023/ sector 63/ head 254 > > > > ... and partitioned as:: paert# disklabel da0 > > :: # size offset fstype [fsize bsize bps/cpg] > > :: b: 786432 2097152 swap # (Cyl. 130*- 179*) > > :: c: 9381960 0 unused 0 0 # (Cyl. 0 - 583) > > :: e: 2097152 0 4.2BSD 0 0 0 # (Cyl. 0 - 130*) > > :: f: 6498376 2883584 4.2BSD 0 0 0 # (Cyl. 179*- 583*) > > > > > > :: paert# disklabel da1 > > :: # size offset fstype [fsize bsize bps/cpg] > > :: a: 524288 0 4.2BSD 0 0 0 # (Cyl. 0 - 32*) > > :: b: 786432 524288 swap # (Cyl. 32*- 81*) > > :: c: 12578832 0 unused 0 0 # (Cyl. 0 - 782*) > > :: e: 2097152 1310720 4.2BSD 0 0 0 # (Cyl. 81*- 212*) > > :: f: 2097152 3407872 4.2BSD 0 0 0 # (Cyl. 212*- 342*) > > :: g: 7073808 5505024 4.2BSD 0 0 0 # (Cyl. 342*- 782*) > > > > > > I'm used to boot the system by the NT BootLoader (since fbsdboot chokes > > on vm86 ...). The (freebsd) root filesystem lives on da1s1a. > > Both bsd-slices are disklabeled to the new blocks, too. > > > > I made an entry in the NT boot.ini for the new fbsd bootblock and > > the system boots. ... But the new boot block gives the warning > > 'no ufs' first. It seems to me, that the boot-code just tries to make > > use of the first partitions in the first found freebsd-slice (da0s3) > > for going on. (e.g. looking for /boot/* ) > > Since the da0s3b partition is a swap-partition, .... this approach > > has to fail ... > > The obvious approach seems to be to boot da1, but I assume you can't > tell NT BootLoader to do that. > > The trouble with a setup like this is that it's not compatible with > default bootblock behavior, and there's also no place to put a > /boot.config to change that behavior. > > You could patch /sys/boot/i386/boot2/boot2.c to look for everything > on da1, I guess. But the basic problem seems to be that you're > trying to boot from an unbootable disk. (If the root filesystem > is on da1, you need to boot da1 not da0.) > > -- > Robert Nordier > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 13:33:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA11061 for freebsd-current-outgoing; Wed, 6 Jan 1999 13:33:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sicily.odyssey.cs.cmu.edu (SICILY.ODYSSEY.CS.CMU.EDU [128.2.185.138]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA11056 for ; Wed, 6 Jan 1999 13:33:23 -0800 (PST) (envelope-from rvb+@sicily.odyssey.cs.cmu.edu) To: "Daniel C. Sobral" Cc: current@FreeBSD.ORG, Mike Smith , "Jordan K. Hubbard" , Andrzej Bialecki Subject: Re: /boot/boot.rc && /boot/rc.d References: <36925780.75AB6581@newsguy.com> From: "Robert V. Baron" Date: 06 Jan 1999 16:32:22 -0500 In-Reply-To: "Daniel C. Sobral"'s message of Wed, 06 Jan 1999 03:18:40 +0900 Message-ID: Lines: 10 X-Mailer: Gnus v5.4.46/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel C. Sobral" writes: > I was thinking about possible on-comings "patches" in boot.rc > (currently known as boot.conf :), when I realized that for > third-party drivers or ports making use of loader it would better to > source files from a boot/rc.d directory. I was wondering whether boot.rc should be named loader.rc. It seems to me that /boot.config has to hang around for a while to set flags for boot2. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 13:44:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA12193 for freebsd-current-outgoing; Wed, 6 Jan 1999 13:44:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA12188 for ; Wed, 6 Jan 1999 13:44:29 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA00594; Wed, 6 Jan 1999 13:40:01 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901062140.NAA00594@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Julian Elischer cc: Robert Nordier , Andreas Braukmann , current@FreeBSD.ORG Subject: Re: Trouble booting from WinNT with new boot loader In-reply-to: Your message of "Wed, 06 Jan 1999 13:09:43 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 06 Jan 1999 13:40:01 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is exactly why at whistle we use the 2nd block of the first > disk to store this stuff. (see 'nextboot(8)') > the bootblocks on da0 load a default from da0-block1, > which specify: > da(1,........ > > I am thinking of adding code to actually make the 2nd block require to be > in it's own slice type (not 165) so that it is marked as being in-use > rather than using a 'free' block like we do now.. > > I've added a 4th slice below that shows what it would look like.... > what do you think? It wouldn't help in this situation; the NT bootloader is passing 0x80 in as the "current disk" I think, and so the first sector is all at sea. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 13:49:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA12455 for freebsd-current-outgoing; Wed, 6 Jan 1999 13:49:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA12448 for ; Wed, 6 Jan 1999 13:49:07 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA00496; Wed, 6 Jan 1999 13:22:21 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901062122.NAA00496@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Thomas T. Veldhouse" cc: "Larry S. Marso" , freebsd-current@FreeBSD.ORG Subject: Re: bootblocks: once or each time? In-reply-to: Your message of "Wed, 06 Jan 1999 12:24:42 CST." <019f01be39a1$dc9eb8e0$236319ac@w142844.carlson.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 06 Jan 1999 13:22:20 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am curious to know if the new boot blocks will mount root correctly or > rather, will it try to mount the correct root. It seemed to ignore rootdev > before and always subtracted one or from currdev (or simply default to > disk1s1a). The new bootblocks don't mount anything. The loader sets $rootdev, but the kernel doesn't currently do anything with it. As has been explained here before in excruciating detail, the problem is quite difficult to solve "properly", and it also looks like the current partial solutions aren't enough for people with weird setups. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 15:07:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19409 for freebsd-current-outgoing; Wed, 6 Jan 1999 15:07:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA19404 for ; Wed, 6 Jan 1999 15:07:31 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca7-163.ix.netcom.com [209.109.235.163]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id PAA10018; Wed, 6 Jan 1999 15:07:02 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.1/8.6.9) id PAA47473; Wed, 6 Jan 1999 15:06:52 -0800 (PST) Date: Wed, 6 Jan 1999 15:06:52 -0800 (PST) Message-Id: <199901062306.PAA47473@silvia.hip.berkeley.edu> To: bde@zeta.org.au CC: freebsd-current@FreeBSD.ORG In-reply-to: (message from Alfred Perlstein on Wed, 6 Jan 1999 11:02:22 -0500 (EST)) Subject: Re: How to Build & Run ELF Kernel From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * disklabel -B -b /boot/boot1 -s /boot/boot2 I did this and one of my machines have trouble reading the bootblocks. It just says "read error" after OS-BS selects the disk. I tried it with disklabel -B /dev/rsd0s2c disklabel -B -b sd0s2 disklabel -B -b /boot/boot1 -s /boot/boot2 sd0s2 etc. It's always the same, disklabel exits without an error but it fails during reboot. Any ideas? Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 15:12:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20117 for freebsd-current-outgoing; Wed, 6 Jan 1999 15:12:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20110 for ; Wed, 6 Jan 1999 15:12:54 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id PAA09910; Wed, 6 Jan 1999 15:08:41 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdHQ9890; Wed Jan 6 23:08:35 1999 Date: Wed, 6 Jan 1999 15:08:24 -0800 (PST) From: Julian Elischer To: Mike Smith cc: Robert Nordier , Andreas Braukmann , current@FreeBSD.ORG Subject: Re: Trouble booting from WinNT with new boot loader In-Reply-To: <199901062140.NAA00594@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG if the first sector passes 0x80 then that is just fine. the bootblocks in da0 will be run and they will pick up the changed spec in the second block.. On Wed, 6 Jan 1999, Mike Smith wrote: > > This is exactly why at whistle we use the 2nd block of the first > > disk to store this stuff. (see 'nextboot(8)') > > the bootblocks on da0 load a default from da0-block1, > > which specify: > > da(1,........ > > > > I am thinking of adding code to actually make the 2nd block require to be > > in it's own slice type (not 165) so that it is marked as being in-use > > rather than using a 'free' block like we do now.. > > > > I've added a 4th slice below that shows what it would look like.... > > what do you think? > > It wouldn't help in this situation; the NT bootloader is passing 0x80 > in as the "current disk" I think, and so the first sector is all at sea. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 15:14:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20226 for freebsd-current-outgoing; Wed, 6 Jan 1999 15:14:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-54-dbn.dial-up.net [196.34.155.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20221 for ; Wed, 6 Jan 1999 15:14:02 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id BAA03150; Thu, 7 Jan 1999 01:10:13 +0200 (SAT) From: Robert Nordier Message-Id: <199901062310.BAA03150@ceia.nordier.com> Subject: Re: Trouble booting from WinNT with new boot loader In-Reply-To: from Julian Elischer at "Jan 6, 99 01:09:43 pm" To: julian@whistle.com (Julian Elischer) Date: Thu, 7 Jan 1999 01:10:12 +0200 (SAT) Cc: rnordier@nordier.com, braukmann@tse-online.de, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer wrote: > This is exactly why at whistle we use the 2nd block of the first > disk to store this stuff. (see 'nextboot(8)') > the bootblocks on da0 load a default from da0-block1, > which specify: > da(1,........ I've come to quite like the nextboot concept, the more I've thought about it. One advantage seems that it's just much easier for external programs (which may not be UFS-aware) to set up the bootblocks, or maybe just pass arguments to them. > I am thinking of adding code to actually make the 2nd block require to be > in it's own slice type (not 165) so that it is marked as being in-use > rather than using a 'free' block like we do now.. > > I've added a 4th slice below that shows what it would look like.... > what do you think? > The data for partition 3 is: > sysid 201,(FreeBSD bootspec) > start 1, size 1 (0 Meg), flag 0 > beg: cyl 0/ sector 2/ head 0; > end: cyl 0/ sector 2/ head 0 It could have the advantage of warning off other software. Modern versions of fdisk should allocate slices aligned to head boundaries; and the IBM/Microsoft OSes have a convention of ignoring any slice smaller than 64 sectors, anyway. Though there seems to be a mostly-accepted convention that all of cyl=0 head=0 is reserved for the boot manager these days, so that might be the only thing to worry about. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 15:15:39 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20524 for freebsd-current-outgoing; Wed, 6 Jan 1999 15:15:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-54-dbn.dial-up.net [196.34.155.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20518 for ; Wed, 6 Jan 1999 15:15:35 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id AAA03048; Thu, 7 Jan 1999 00:27:41 +0200 (SAT) From: Robert Nordier Message-Id: <199901062227.AAA03048@ceia.nordier.com> Subject: Re: new boot loader ... documentation In-Reply-To: from "Robert V. Baron" at "Jan 6, 99 02:24:36 pm" To: rvb@cs.cmu.edu (Robert V. Baron) Date: Thu, 7 Jan 1999 00:27:39 +0200 (SAT) Cc: rnordier@nordier.com, dcs@newsguy.com, mike@smith.net.au, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert V. Baron wrote: > Robert Nordier writes: > > > Daniel C. Sobral wrote: > > > > The "new boot blocks" tutorial limits itself to the "boot blocks": > > that is, the hidden first and second stages of the bootstrap which > > are written to the disk by disklabel(8). > > What would be equally interesting is a tutorial/overview on btxld, > btxldr, and btx. How full an OS is btx? The FreeBSD version in use at the moment is extremely minimalist. Essentially, everything that the new boot code can do without isn't there. The main constraint is the 8K of disk space available to the bootblocks, as the same version of btx hosts both the second and third stages of the bootstrap. However, a more capable version, that can (primitively) support its own edit/assemble/link development cycle, is waiting in the wings; and I guess /boot/loader may need additional facilities at some stage. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 15:16:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20649 for freebsd-current-outgoing; Wed, 6 Jan 1999 15:16:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-54-dbn.dial-up.net [196.34.155.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20641 for ; Wed, 6 Jan 1999 15:16:42 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id AAA03059; Thu, 7 Jan 1999 00:31:58 +0200 (SAT) From: Robert Nordier Message-Id: <199901062231.AAA03059@ceia.nordier.com> Subject: Re: new boot loader ... documentation In-Reply-To: from Andrzej Bialecki at "Jan 6, 99 08:41:59 pm" To: abial@nask.pl (Andrzej Bialecki) Date: Thu, 7 Jan 1999 00:31:57 +0200 (SAT) Cc: rvb@cs.cmu.edu, rnordier@nordier.com, dcs@newsguy.com, mike@smith.net.au, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki wrote: > On 6 Jan 1999, Robert V. Baron wrote: > > > Robert Nordier writes: > > > > > Daniel C. Sobral wrote: > > > > > > The "new boot blocks" tutorial limits itself to the "boot blocks": > > > that is, the hidden first and second stages of the bootstrap which > > > are written to the disk by disklabel(8). > > > > What would be equally interesting is a tutorial/overview on btxld, > > btxldr, and btx. How full an OS is btx? > > Oh, yes, pleeez... Write something about it - even quite general concepts > would be helpful, not to mention the usage and arguments. I hadn't really thought about the need for this; but I'll certainly try to put something together in the next few weeks. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 15:17:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20789 for freebsd-current-outgoing; Wed, 6 Jan 1999 15:17:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20755; Wed, 6 Jan 1999 15:17:10 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca7-163.ix.netcom.com [209.109.235.163]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id PAA10036; Wed, 6 Jan 1999 15:15:02 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.1/8.6.9) id PAA55218; Wed, 6 Jan 1999 15:14:52 -0800 (PST) Date: Wed, 6 Jan 1999 15:14:52 -0800 (PST) Message-Id: <199901062314.PAA55218@silvia.hip.berkeley.edu> To: jcwells@u.washington.edu CC: wwoods@cybcon.com, reg@shale.csir.co.za, bwoods@cybcon.com, kkennawa@physics.adelaide.edu.au, current@FreeBSD.ORG, ports@FreeBSD.ORG In-reply-to: (jcwells@u.washington.edu) Subject: Re: kdesupport11 port build problems on -current elf From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * The pr is ports/9018. Thanks, I assigned the PR to Stefan Esser (maintainer of kde* ports). Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 15:59:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25375 for freebsd-current-outgoing; Wed, 6 Jan 1999 15:59:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-23-dbn.dial-up.net [196.34.155.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA25361; Wed, 6 Jan 1999 15:58:53 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id BAA03690; Thu, 7 Jan 1999 01:57:38 +0200 (SAT) From: Robert Nordier Message-Id: <199901062357.BAA03690@ceia.nordier.com> Subject: Re: How to Build & Run ELF Kernel In-Reply-To: <199901062306.PAA47473@silvia.hip.berkeley.edu> from Satoshi Asami at "Jan 6, 99 03:06:52 pm" To: asami@FreeBSD.ORG (Satoshi Asami) Date: Thu, 7 Jan 1999 01:57:35 +0200 (SAT) Cc: bde@zeta.org.au, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Satoshi Asami wrote: > * disklabel -B -b /boot/boot1 -s /boot/boot2 > > I did this and one of my machines have trouble reading the > bootblocks. It just says "read error" after OS-BS selects the disk. > > I tried it with > > disklabel -B /dev/rsd0s2c > disklabel -B -b sd0s2 > disklabel -B -b /boot/boot1 -s /boot/boot2 sd0s2 > > etc. It's always the same, disklabel exits without an error but it > fails during reboot. > > Any ideas? The new boot1 will report a "Read error" on any of the following: o Can't get the disk geometry from the BIOS o The disk geometry would cause division by zero o The derived cylinder number exceeds 1023 o BIOS fails to read a sector on five consecutive attempts I'd check particularly whether the FreeBSD slice entry is 100% correct. The old bootblocks use the CHS value (257/1/1 below) to determine the slice offset, whereas the new bootblocks use the start value (4128768 below) and the disk geometry reported by the BIOS to derive a CHS: [Sample fdisk output] sysid 165,(FreeBSD/NetBSD/386BSD) start 4128768, size 4305357 (2102 Meg), flag 80 (active) beg: cyl 257/ sector 1/ head 1; end: cyl 524/ sector 63/ head 254 sector = 4128768 % 63 + 1 = 1 head = 4128768 / 63 % 255 = 1 cyl = 4128768 / 63 / 255 = 257 -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 16:18:39 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA28868 for freebsd-current-outgoing; Wed, 6 Jan 1999 16:18:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA28863 for ; Wed, 6 Jan 1999 16:18:39 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca7-163.ix.netcom.com [209.109.235.163]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id QAA10084; Wed, 6 Jan 1999 16:17:58 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.1/8.6.9) id QAA02235; Wed, 6 Jan 1999 16:17:36 -0800 (PST) Date: Wed, 6 Jan 1999 16:17:36 -0800 (PST) Message-Id: <199901070017.QAA02235@silvia.hip.berkeley.edu> To: rnordier@nordier.com CC: bde@zeta.org.au, freebsd-current@FreeBSD.ORG In-reply-to: <199901062357.BAA03690@ceia.nordier.com> (message from Robert Nordier on Thu, 7 Jan 1999 01:57:35 +0200 (SAT)) Subject: Re: How to Build & Run ELF Kernel From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert, thanks for your reply. * I'd check particularly whether the FreeBSD slice entry is 100% * correct. * * The old bootblocks use the CHS value (257/1/1 below) to determine * the slice offset, whereas the new bootblocks use the start value * (4128768 below) and the disk geometry reported by the BIOS to derive * a CHS: * * [Sample fdisk output] * sysid 165,(FreeBSD/NetBSD/386BSD) * start 4128768, size 4305357 (2102 Meg), flag 80 (active) * beg: cyl 257/ sector 1/ head 1; * end: cyl 524/ sector 63/ head 254 * * sector = 4128768 % 63 + 1 = 1 * head = 4128768 / 63 % 255 = 1 * cyl = 4128768 / 63 / 255 = 257 Hmm. All my disks have a FreeBSD partition starting at sector 63 (start of second track of first cylinder). Here's the one that doesn't work: === ## fdisk sd0 ******* Working on device /dev/rsd0 ******* parameters extracted from in-core disklabel are: cylinders=263 heads=255 sectors/track=63 (16065 blks/cyl) parameters to be used for BIOS calculations are: cylinders=263 heads=255 sectors/track=63 (16065 blks/cyl) : The data for partition 2 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 63, size 4225032 (2063 Meg), flag 80 (active) beg: cyl 0/ sector 1/ head 1; end: cyl 262/ sector 63/ head 254 === and the one that does work, on the same machine: === ## fdisk sd1 ******* Working on device /dev/rsd1 ******* parameters extracted from in-core disklabel are: cylinders=274 heads=255 sectors/track=63 (16065 blks/cyl) parameters to be used for BIOS calculations are: cylinders=274 heads=255 sectors/track=63 (16065 blks/cyl) : The data for partition 2 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 63, size 4401747 (2149 Meg), flag 80 (active) beg: cyl 0/ sector 1/ head 1; end: cyl 273/ sector 63/ head 254 === As you can see, they are almost identical. The only difference is the size of the disk/partitions. As for other items on your checklist (reproduced here): * o Can't get the disk geometry from the BIOS It did boot before with the old bootblocks, so it is getting the geometry, right? * o The disk geometry would cause division by zero * o The derived cylinder number exceeds 1023 Both of these shouldn't apply to this case. * o BIOS fails to read a sector on five consecutive attempts === ## dd if=/dev/rsd0 of=/dev/null bs=512 count=2048 2048+0 records in 2048+0 records out 1048576 bytes transferred in 1.827534 secs (573765 bytes/sec) ## tail /var/log/messages : Jan 6 15:00:25 baloon sudo: asami : TTY=ttyp0 ; PWD=/s/c/home/piedmont/asami ; USER=root ; COMMAND=/usr/local/bin/bash === At least it seems quite readable from the FreeBSD kernel. And again, it was booting fine before I rewrote the bootblocks. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 16:53:57 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03184 for freebsd-current-outgoing; Wed, 6 Jan 1999 16:53:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03178 for ; Wed, 6 Jan 1999 16:53:56 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA01493; Wed, 6 Jan 1999 16:49:02 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901070049.QAA01493@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Julian Elischer cc: Mike Smith , Robert Nordier , Andreas Braukmann , current@FreeBSD.ORG Subject: Re: Trouble booting from WinNT with new boot loader In-reply-to: Your message of "Wed, 06 Jan 1999 15:08:24 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 06 Jan 1999 16:49:02 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > if the first sector passes 0x80 > then that is just fine. > the bootblocks in da0 will be run and they will pick up the changed spec > in the second block.. Except that in this case there are probably no bootblocks on da0 (swap partition, remember), and the "second block" is on da1 where the bootblocks won't be looking... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 17:29:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08260 for freebsd-current-outgoing; Wed, 6 Jan 1999 17:29:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA08247; Wed, 6 Jan 1999 17:29:38 -0800 (PST) (envelope-from se@dialup124.zpr.uni-koeln.de) Received: from dialup124.zpr.Uni-Koeln.DE (dialup124.zpr.Uni-Koeln.DE [134.95.219.124]) by Sisyphos.MI.Uni-Koeln.DE (8.8.7/8.8.7) with ESMTP id CAA18958; Thu, 7 Jan 1999 02:29:03 +0100 (MET) Received: (from se@localhost) by dialup124.zpr.Uni-Koeln.DE (8.9.1/8.6.9) id CAA12439; Thu, 7 Jan 1999 02:29:16 +0100 (CET) Date: Thu, 7 Jan 1999 02:29:15 +0100 From: Stefan Esser To: Wiliam Woods Cc: Jeremy Lea , Bill Woods , Kris Kennaway , current@FreeBSD.ORG, ports@FreeBSD.ORG, Stefan Esser Subject: Re: kdesupport11 port build problems on -current elf Message-ID: <19990107022915.B12325@dialup124.mi.uni-koeln.de> Reply-To: se@FreeBSD.ORG Mail-Followup-To: Wiliam Woods , Jeremy Lea , Bill Woods , Kris Kennaway , current@FreeBSD.ORG, ports@FreeBSD.ORG References: <005501be3999$e8eedba0$f301040a@c063.beaverton.stream.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <005501be3999$e8eedba0$f301040a@c063.beaverton.stream.com>; from Wiliam Woods on Wed, Jan 06, 1999 at 09:27:54AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-01-06 09:27 -0800, Wiliam Woods wrote: > Why shouldent I use the 11 ports yet? They are in the ports tree....and as a > side note, I got the same error with the regular kdesupport port. The kde*11 ports were identical to kde*, upto just a few minutes ago ... (The kde* ports had been copied in preparation of the 1.1 commit, but I didn't have time to actually put the changes into the repository ...) Regards, STefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 17:35:53 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA09017 for freebsd-current-outgoing; Wed, 6 Jan 1999 17:35:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from galaxy.support.stream.com (galaxy.support.stream.com [208.13.180.22]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA09000; Wed, 6 Jan 1999 17:35:44 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from c063.beaverton.stream.com ([208.13.191.137]) by galaxy.support.stream.com (Lotus SMTP MTA v4.6.3 (733.2 10-16-1998)) with SMTP id 852566F2.0008AA23; Wed, 6 Jan 1999 20:34:39 -0500 Message-ID: <013401be39dd$77b5a060$f301040a@c063.beaverton.stream.com> Reply-To: "Wiliam Woods" From: "Wiliam Woods" To: Cc: "Jeremy Lea" , "Bill Woods" , "Kris Kennaway" , , , "Stefan Esser" Subject: Re: kdesupport11 port build problems on -current elf Date: Wed, 6 Jan 1999 17:31:30 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does this mean they work now :)........ -----Original Message----- From: Stefan Esser To: Wiliam Woods Cc: Jeremy Lea ; Bill Woods ; Kris Kennaway ; current@FreeBSD.ORG ; ports@FreeBSD.ORG ; Stefan Esser Date: Wednesday, January 06, 1999 5:30 PM Subject: Re: kdesupport11 port build problems on -current elf >On 1999-01-06 09:27 -0800, Wiliam Woods wrote: >> Why shouldent I use the 11 ports yet? They are in the ports tree....and as a >> side note, I got the same error with the regular kdesupport port. > >The kde*11 ports were identical to kde*, upto just a few minutes >ago ... (The kde* ports had been copied in preparation of the 1.1 >commit, but I didn't have time to actually put the changes into >the repository ...) > >Regards, STefan > >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 Jan 6 18:09:41 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA12832 for freebsd-current-outgoing; Wed, 6 Jan 1999 18:09:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA12827 for ; Wed, 6 Jan 1999 18:09:39 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id VAA28254; Wed, 6 Jan 1999 21:09:07 -0500 (EST) Date: Wed, 6 Jan 1999 21:09:06 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: "Jordan K. Hubbard" cc: Garrett Wollman , Tom Bartol , current@FreeBSD.ORG Subject: Re: New boot blocks for serial console ... In-Reply-To: <38416.915473396@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 Mon, 4 Jan 1999, Jordan K. Hubbard wrote: > > What we're trying to achieve is an environment where the worst thing > > someone could do is cause the machine to reboot. > > Then lock the machine in a room. You're not going to get anywhere > close to that by changing the boot blocks and flagging it as an issue > in this case is simply waving a red herring. It might be nice to have a root-password-required feature for booting single user, as I believe OpenBSD has, and maybe a "trusted kernel" path... With this, disabling booting from other media, and passwording the BIOS, it would be impossible to crack the machine without having to open the case. This would usually keep a machine in open view secure, as people would NOT be expecting someone to open up the case in . Then again, a case won't necessarily be a deterrent anyway, but these things could help. > > - Jordan Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 18:41:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA15214 for freebsd-current-outgoing; Wed, 6 Jan 1999 18:41:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA15198 for ; Wed, 6 Jan 1999 18:40:57 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id NAA06705; Thu, 7 Jan 1999 13:10:27 +1030 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA02462; Thu, 7 Jan 1999 13:10:26 +1030 Date: Thu, 7 Jan 1999 13:10:25 +1030 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: Wiliam Woods Cc: current@FreeBSD.ORG Subject: Re: kdesupport11 port build problems on -current elf In-Reply-To: <013401be39dd$77b5a060$f301040a@c063.beaverton.stream.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, 6 Jan 1999, Wiliam Woods wrote: > Does this mean they work now :)........ If you're running -current, you really must be subscribed to both freebsd-current (which you are, obviously), and cvs-all@freebsd.org (or an appropriate sublist, but I don't think the broken-up versions were ever brought back). If you're listening to the latter, then you'd know when the ports were upgraded, as well as when changes happen to the -current codebase which affect you. Kris ----- (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 18:47:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA15760 for freebsd-current-outgoing; Wed, 6 Jan 1999 18:47:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA15750 for ; Wed, 6 Jan 1999 18:47:01 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA02030; Wed, 6 Jan 1999 18:41:34 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901070241.SAA02030@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Feldman cc: "Jordan K. Hubbard" , Garrett Wollman , Tom Bartol , current@FreeBSD.ORG Subject: Re: New boot blocks for serial console ... In-reply-to: Your message of "Wed, 06 Jan 1999 21:09:06 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 06 Jan 1999 18:41:33 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, 4 Jan 1999, Jordan K. Hubbard wrote: > > > > What we're trying to achieve is an environment where the worst thing > > > someone could do is cause the machine to reboot. > > > > Then lock the machine in a room. You're not going to get anywhere > > close to that by changing the boot blocks and flagging it as an issue > > in this case is simply waving a red herring. > > It might be nice to have a root-password-required feature for > booting single user, Mark the console as insecure, of course. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 18:57:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA16964 for freebsd-current-outgoing; Wed, 6 Jan 1999 18:57:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from galaxy.support.stream.com (galaxy.support.stream.com [208.13.180.22]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA16959 for ; Wed, 6 Jan 1999 18:57:56 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from c063.beaverton.stream.com ([208.13.191.137]) by galaxy.support.stream.com (Lotus SMTP MTA v4.6.3 (733.2 10-16-1998)) with SMTP id 852566F2.00102FAD; Wed, 6 Jan 1999 21:56:48 -0500 Message-ID: <015801be39e8$f1348720$f301040a@c063.beaverton.stream.com> Reply-To: "Wiliam Woods" From: "Wiliam Woods" To: "Kris Kennaway" Cc: Subject: Re: kdesupport11 port build problems on -current elf Date: Wed, 6 Jan 1999 18:53:39 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, OK, I appreciate the advice, I just subscribbed, but what about my question ? -----Original Message----- From: Kris Kennaway To: Wiliam Woods Cc: current@freebsd.org Date: Wednesday, January 06, 1999 6:40 PM Subject: Re: kdesupport11 port build problems on -current elf >On Wed, 6 Jan 1999, Wiliam Woods wrote: > >> Does this mean they work now :)........ > >If you're running -current, you really must be subscribed to both >freebsd-current (which you are, obviously), and cvs-all@freebsd.org (or an >appropriate sublist, but I don't think the broken-up versions were ever >brought back). If you're listening to the latter, then you'd know when the >ports were upgraded, as well as when changes happen to the -current codebase >which affect you. > >Kris > >----- >(ASP) Microsoft Corporation (MSFT) announced today that the release of its >productivity suite, Office 2000, will be delayed until the first quarter >of 1901. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 20:29:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA00135 for freebsd-current-outgoing; Wed, 6 Jan 1999 20:29:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Vorlon.odc.net (Vorlon.odc.net [207.137.42.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA00130 for ; Wed, 6 Jan 1999 20:29:18 -0800 (PST) (envelope-from nwestfal@Vorlon.odc.net) Received: from localhost (nwestfal@localhost) by Vorlon.odc.net (8.8.7/8.8.7) with ESMTP id UAA00421; Wed, 6 Jan 1999 20:28:27 -0800 Date: Wed, 6 Jan 1999 20:28:26 -0800 (PST) From: Neal Westfall To: Sheldon Hearn cc: Jaye Mathisen , current@FreeBSD.ORG Subject: Re: mergemaster should be merged in to the main tree. In-Reply-To: <8159.915653201@axl.noc.iafrica.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 So where would a person get this mergemaster? Thanks. -- Neal Westfall mailto:nwestfal@odc.net http://www.odc.net/~nwestfal/ FreeBSD: The Power To Serve! http://www.freebsd.org/ $Id: dot.signature,v 1.2 1998/12/30 08:23:13 nwestfal Exp nwestfal $ On Wed, 6 Jan 1999, Sheldon Hearn wrote: > > > On Wed, 06 Jan 1999 11:15:46 PST, Jaye Mathisen wrote: > > > I would be willing to get permission from the author if people think it's > > a good idea. > > HINT: find out who the author is, then search the FreeBSD web page for > mention of him. :-) > > Ciao, > Sheldon. > > 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 Jan 6 20:46:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA01876 for freebsd-current-outgoing; Wed, 6 Jan 1999 20:46:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail11.digital.com (mail11.digital.com [192.208.46.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA01871 for ; Wed, 6 Jan 1999 20:46:19 -0800 (PST) (envelope-from perry@zso.dec.com) Received: from yakko.zso.dec.com (yakko.zso.dec.com [16.64.16.191]) by mail11.digital.com (8.9.1a/8.9.1/WV2.0c) with ESMTP id XAA15982; Wed, 6 Jan 1999 23:46:42 -0500 (EST) Received: from localhost (perry@localhost) by yakko.zso.dec.com (8.9.1/8.9.1) with SMTP id UAA30153; Wed, 6 Jan 1999 20:45:44 -0800 (PST) Message-Id: <199901070445.UAA30153@yakko.zso.dec.com> X-Authentication-Warning: yakko.zso.dec.com: perry@localhost didn't use HELO protocol To: Mike Smith cc: freebsd-current@FreeBSD.ORG Reply-To: perry@zso.dec.com Subject: Re: Kernel cannot mount root with new bootblocks In-reply-to: Message from Mike Smith of "Tue, 05 Jan 1999 08:29:13 PST." <199901051629.IAA03868@dingo.cdrom.com> Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: Wed, 06 Jan 1999 20:45:43 -0800 From: "Reginald S. Perry" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >"Mike" == Mike Smith writes: > Most of the problems with booting are finger trouble at the moment; > I can't see any reason why we shouldn't go ahead as planned. Hi Mike, I have a vintage 1994 486/66 machine on which I tested the new bootblocks using the test floppy method described on -current. I verified that it worked on my dual pentium box before I tested on the 486. The machine is running the Award bios v4.50G on a Genoa Turboexpress 486VLG-X2 (Ver A) motherboard. When I try to boot from floppy, I get a register dump: int=0000000e err=00000007 efl=00030296 eip=00005000 eax=0000918d ebx=00000000 ecx=00000000 edx=00000100 esi=00000000 edi=0000a809 ebp=000003fc esp=000003fe cs=0000 ds=0000 es=a809 fs=0000 gs=0000 ss=9e82 cs:eip=67 00 00 00 67 10 00 00-25 20 00 00 25 30 00 00 ss:esp=00 00 fc 03 0c 04 00 00-00 01 00 00 8d 91 2d 2f And the system then halts. If you build new floppy images, I am willing to test them and report the results, but I do not have enough knowledge of how to debug at this level to be of any help. -Reggie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 20:56:41 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA02774 for freebsd-current-outgoing; Wed, 6 Jan 1999 20:56:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA02762 for ; Wed, 6 Jan 1999 20:56:37 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id PAA07468; Thu, 7 Jan 1999 15:26:06 +1030 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA23174; Thu, 7 Jan 1999 15:26:05 +1030 Date: Thu, 7 Jan 1999 15:26:04 +1030 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: Neal Westfall Cc: current@FreeBSD.ORG Subject: Re: mergemaster should be merged in to the main tree. 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, 6 Jan 1999, Neal Westfall wrote: > So where would a person get this mergemaster? Thanks. /usr/ports/sysutils/mergemaster Kris ----- (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 21:13:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA04226 for freebsd-current-outgoing; Wed, 6 Jan 1999 21:13:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA04221 for ; Wed, 6 Jan 1999 21:13:04 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id VAA22770; Wed, 6 Jan 1999 21:12:35 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id VAA39741; Wed, 6 Jan 1999 21:12:35 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 06 Jan 1999 21:12:35 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Chris Timmons Subject: Re: CVS issues Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 30-Dec-98 Chris Timmons wrote: > > Different CVSup servers allow different numbers of connections. I can't > remember what you said would happen when the client gets connection > refused and has more A records to try; will it go to the next one? I think so. That's what the code is supposed to do, but I've never actually set up a test to try it out. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 21:14:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA04483 for freebsd-current-outgoing; Wed, 6 Jan 1999 21:14:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA04474 for ; Wed, 6 Jan 1999 21:14:22 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id VAA22783; Wed, 6 Jan 1999 21:13:53 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id VAA39746; Wed, 6 Jan 1999 21:13:52 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19981220185338.A363@halcyon.com> Date: Wed, 06 Jan 1999 21:13:52 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: "William R. Somsky" Subject: Re: syncing 3.0-src tree with current Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 21-Dec-98 William R. Somsky wrote: > > The one thing I wish CVSup had was a way for it to tell you when > there are _extra_ files in /usr/src (or whatever it's syncing) that > it's not touching. Agreed. It's on my to-do list. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 21:19:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA04979 for freebsd-current-outgoing; Wed, 6 Jan 1999 21:19:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA04972 for ; Wed, 6 Jan 1999 21:18:59 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id VAA22815; Wed, 6 Jan 1999 21:18:26 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id VAA39758; Wed, 6 Jan 1999 21:18:25 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <86lnjoabw5.fsf@not.oeno.com> Date: Wed, 06 Jan 1999 21:18:25 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Ville-Pertti Keinonen Subject: Re: CVS issues Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 31-Dec-98 Ville-Pertti Keinonen wrote: > > John Polstra writes: [about multiple DNS records for cvsup.freebsd.org] >> The reason I haven't done it so far is because the mirrors differ >> in some of the little-used collections that they carry. They all > > Are you sure there are no other reasons for not doing it? > > What happens if you cvsup from a site that has an older version of the > tree than you do? Since the relevant mirror sites all update themselves hourly from freefall, that's unlikely. You would have to run cvsup twice in an hour for it to happen. It could still happen if you lost the connection and then reconnected to a different server. But even then the damage would be fairly small. Any changes that existed on the first server but not on the second server would be taken away. But normally, not much happens in an hour in the FreeBSD repository. And those changes that were removed would come back again on your next update. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 21:20:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA05175 for freebsd-current-outgoing; Wed, 6 Jan 1999 21:20:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA05170 for ; Wed, 6 Jan 1999 21:20:34 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id VAA22833; Wed, 6 Jan 1999 21:20:01 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id VAA39770; Wed, 6 Jan 1999 21:20:01 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <368B10FA.9D87CD46@san.rr.com> Date: Wed, 06 Jan 1999 21:20:01 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Doug Subject: Re: CVS issues Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 31-Dec-98 Doug wrote: > Chris Timmons wrote: >> >> Different CVSup servers allow different numbers of connections. I can't >> remember what you said would happen when the client gets connection >> refused and has more A records to try; will it go to the next one? > > All well written network clients of any kind should do just that. :) That's pretty stringent. What about a well-written client that just happens to have one little bug? :-) John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 21:25:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA05512 for freebsd-current-outgoing; Wed, 6 Jan 1999 21:25:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (congo-65.ppp.hooked.net [206.169.227.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA05494; Wed, 6 Jan 1999 21:25:48 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@zippy.dyn.ml.org [127.0.0.1]) by zippy.dyn.ml.org (8.9.1/8.8.8) with ESMTP id VAA02881; Wed, 6 Jan 1999 21:26:45 -0800 (PST) (envelope-from garbanzo@hooked.net) Date: Wed, 6 Jan 1999 21:26:45 -0800 (PST) From: Alex Zepeda X-Sender: garbanzo@zippy.dyn.ml.org To: jack cc: Kris Kennaway , Bill Woods , current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: kdesupport11 port build problems on -current elf 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, 6 Jan 1999, jack wrote: > I haven't tried the kde 1.1 stuff, but for 1.0 I could only get > it to compile using qt-1.40. KDE 1.1 _will_ require Qt 1.42. Technically 1.41 or higher will link, etc, etc, but 1.42 fixes some bugs that makes kpanel [more] usable. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 21:41:53 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA07414 for freebsd-current-outgoing; Wed, 6 Jan 1999 21:41:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from assaris2.pdc.kth.se (assaris2.pdc.kth.se [130.237.221.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA07409 for ; Wed, 6 Jan 1999 21:41:51 -0800 (PST) (envelope-from assar@sics.se) Received: (from assar@localhost) by assaris2.pdc.kth.se (8.9.1/8.7.3) id GAA13778; Thu, 7 Jan 1999 06:42:54 +0100 (CET) To: current@FreeBSD.ORG Subject: KLD modules support for loading syscalls Mime-Version: 1.0 (generated by tm-edit 7.68) Content-Type: text/plain; charset=US-ASCII From: Assar Westerlund Date: 07 Jan 1999 06:42:53 +0100 Message-ID: <5lsodneizm.fsf@assaris2.pdc.kth.se> Lines: 7 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I added support for loading system calls from KLD modules. The patches are in PR kern/9359. Questions, comments, bugs, and commits are welcome. /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 21:48:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA08328 for freebsd-current-outgoing; Wed, 6 Jan 1999 21:48:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA08306 for ; Wed, 6 Jan 1999 21:48:18 -0800 (PST) (envelope-from sef@kithrup.com) Received: (from sef@localhost) by kithrup.com (8.8.8/8.8.8) id VAA11410; Wed, 6 Jan 1999 21:47:50 -0800 (PST) (envelope-from sef) Date: Wed, 6 Jan 1999 21:47:50 -0800 (PST) From: Sean Eric Fagan Message-Id: <199901070547.VAA11410@kithrup.com> To: current@FreeBSD.ORG Subject: Re: KLD modules support for loading syscalls In-Reply-To: <5lsodneizm.fsf.kithrup.freebsd.current@assaris2.pdc.kth.se> Organization: Kithrup Enterprises, Ltd. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <5lsodneizm.fsf.kithrup.freebsd.current@assaris2.pdc.kth.se> you write: >Questions, comments, bugs, and commits are welcome. Yeah. Did you give any thought how ktrace and truss are supposed to work with this? :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 21:48:34 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA08476 for freebsd-current-outgoing; Wed, 6 Jan 1999 21:48:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ayukawa.aus.org (ayukawa.aus.org [199.166.246.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA08471 for ; Wed, 6 Jan 1999 21:48:32 -0800 (PST) (envelope-from lh@aus.org) Received: from bsd.aus.org (lh@bsd.aus.org [199.166.246.189]) by ayukawa.aus.org (8.8.7/8.7.3) with ESMTP id AAA14795 for ; Thu, 7 Jan 1999 00:29:08 -0500 (EST) Message-Id: <199901070529.AAA14795@ayukawa.aus.org> X-Mailer: XFMail 1.3-beta-042198 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 07 Jan 1999 00:47:53 -0500 (EST) Reply-To: lh@aus.org From: Luke To: current@FreeBSD.ORG Subject: CVS release tages for 3.0 anomaly Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was wondering how come in the src tree theres a RELENG_3_0_0_RELEASE tag for cvs, then in the ports tree theres RELEASE_3_0_0 ? Is it on purpose? --- E-Mail: Luke Sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 22:39:57 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA14352 for freebsd-current-outgoing; Wed, 6 Jan 1999 22:39:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.oeno.com (ns.oeno.com [194.100.99.145]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA14337 for ; Wed, 6 Jan 1999 22:39:52 -0800 (PST) (envelope-from will@ns.oeno.com) Received: (qmail 26802 invoked by uid 1001); 7 Jan 1999 06:39:22 -0000 To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: Y2K, Y 2038? References: <199901052243.OAA97949@apollo.backplane.com.newsgate.clinet.fi> From: Ville-Pertti Keinonen Date: 07 Jan 1999 08:38:45 +0200 In-Reply-To: Matthew Dillon's message of "6 Jan 1999 01:18:55 +0200" Message-ID: <86u2y3lh8q.fsf@not.oeno.com> Lines: 31 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon writes: > I would prefer NOT making *two* hacks to the time system. We should > just move to 64 bit 'ltime_t' or something like that. It is not > a big deal. Then we'll have 30 years to translate the legacy time_t's > useage into the new ltime_t useage. Such a change would be incompatible with other systems and nobody would be likely to use it for new code. It would not do any good for old code that relies on time_t for storing arbitrary dates. It also wouldn't help the library code, all of the interfaces use either time_t or struct tm, and there isn't really that much internal processing going on (struct tm has a reasonable range). Then there's struct timeval. And struct stat, although it's unlikely to be something that anyone stores as binary data in a file. IMHO FreeBSD or any other current operating system should not rush to provide a new API to facilitate writing date-robust code, unless such an API is standardized (or just implemented by sufficiently many other systems). An internal API to allow the kernel, libraries and base system utilities to deal with dates better would naturally be ok, but currently one would not be very useful since the core system doesn't generally need to deal with arbitrary dates and fixing it can easily wait until there is a standardized API to do it. And I don't think a standard API for reliably representing dates in general should look much like the C time.h interfaces. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 6 23:54:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA20827 for freebsd-current-outgoing; Wed, 6 Jan 1999 23:54:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.oeno.com (ns.oeno.com [194.100.99.145]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA20819 for ; Wed, 6 Jan 1999 23:54:46 -0800 (PST) (envelope-from will@ns.oeno.com) Received: (qmail 28810 invoked by uid 1001); 7 Jan 1999 07:47:32 -0000 Date: 7 Jan 1999 07:47:32 -0000 Message-ID: <19990107074732.28807.qmail@ns.oeno.com> From: Ville-Pertti Keinonen To: jdp@polstra.com CC: current@FreeBSD.ORG In-reply-to: (message from John Polstra on Wed, 06 Jan 1999 21:18:25 -0800 (PST)) Subject: Re: CVS issues Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > What happens if you cvsup from a site that has an older version of the > > tree than you do? > Since the relevant mirror sites all update themselves hourly from > freefall, that's unlikely. You would have to run cvsup twice in > an hour for it to happen. It could still happen if you lost the > connection and then reconnected to a different server. But even then > the damage would be fairly small. Any changes that existed on the > first server but not on the second server would be taken away. But > normally, not much happens in an hour in the FreeBSD repository. And > those changes that were removed would come back again on your next > update. That's when everything is working right. If all of the mirror sites are basically independent, there's no way to know for sure that all of the mirror sites are working properly, one of them may even be several days behind, for whatever reason (like broken networks isolating it from freefall). I would prefer to know that when I run cvsup, I'm going to get a newer version of the FreeBSD repository, not an older one. When using a specific mirror, something has to get *really* screwed up for that to happen. Of course I don't use any of the US mirrors myself, anyhow, but I suspect that losing changes may cause unexpected problems. Use your imagination. ;--) At the very least, problems with one mirror could cause significant increases in traffic on all mirrors. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 02:17:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA03324 for freebsd-current-outgoing; Thu, 7 Jan 1999 02:17:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA03319 for ; Thu, 7 Jan 1999 02:17:09 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.2/8.9.2) with ESMTP id KAA81049 for ; Thu, 7 Jan 1999 10:16:39 GMT Message-ID: <3694895D.37DEEE92@tdx.co.uk> Date: Thu, 07 Jan 1999 10:15:57 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Problem with -current, SMP and multiple 'nice' processes? 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'm running -current as of a few days ago, and I've 'rediscovered' a long standing problem I've had... I run the RC5 client on my machine (OK, it's probably not that a 'technically correct' program). The machine is a dual PPro-200 (256Mb RAM), running an SMP a.out kernel... I've noticed this in the past, but thought it might have been 'fixed' or changed by now... If I run the client once (the client warns threads under FreeBSD aren't SMP aware etc. - so I tell it I have 1 CPU, and follow their other instructions {keep reading}).. With this 1 client running at a 'nice' priority level, the load average goes up to 1.0 - and everything is fine... If I run the client again {as per RC5's instructions for SMP FreeBSD machines} the load average goes up to 2.0 (as I'd guess you'd expect), and the machine performs like a dog... I have samba, sendmail + a few other bits & pieces running on the machine... Samba's performance drops from just under 5Mb's a second (via a 100Mb FDX link) to around 30-40k/sec). Everything else on the machine just 'judders' along very slowly... I've noticed this happening when I've been running other 'compute' intensive apps as well (I have a number of home-brew number crunching programs as well) - no amount of fiddling with 'nice' and priority levels seems to work... Is this just a 'symptom' of -current's present handling of SMP? - I know the machine will bottleneck around the kernel, but none of the programs I'm running are I/O or Kernel bound... If the concensus is that it's RC5's client that's 'bad' in someway, I might go on to write some more 'controlled' test programs etc. -Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 02:49:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA05903 for freebsd-current-outgoing; Thu, 7 Jan 1999 02:49:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from assaris.sics.se (assaris.sics.se [193.10.66.108]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA05898 for ; Thu, 7 Jan 1999 02:49:54 -0800 (PST) (envelope-from assar@sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.1/8.7.3) id LAA14240; Thu, 7 Jan 1999 11:50:54 +0100 (CET) To: current@FreeBSD.ORG Subject: Re: KLD modules support for loading syscalls References: <199901070547.VAA11410@kithrup.com> Mime-Version: 1.0 (generated by tm-edit 7.68) Content-Type: text/plain; charset=US-ASCII From: Assar Westerlund Date: 07 Jan 1999 11:50:53 +0100 In-Reply-To: Sean Eric Fagan's message of "Wed, 6 Jan 1999 21:47:50 -0800 (PST)" Message-ID: <5l67aj8igh.fsf@assaris.sics.se> Lines: 21 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sean Eric Fagan writes: > In article <5lsodneizm.fsf.kithrup.freebsd.current@assaris2.pdc.kth.se> you write: > >Questions, comments, bugs, and commits are welcome. > > Yeah. Did you give any thought how ktrace and truss are supposed to > work with this? :) No. But that doesn't have very much to do with how you add the system calls, only that they aren't in syscalls.master, right? Right now, it seems you get something like: syscall lkmnosys(0x14,0x0,0x800c5603,0xefbfd6cc,0x0) errno 22 'Invalid argument' which isn't that bad, even through the name and number would be better. Should we add a sysctl (or something else) interface for getting the syscall names? Moving the name into `struct sysent' seems to me like it would make sense anyway. /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 03:46:59 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA09574 for freebsd-current-outgoing; Thu, 7 Jan 1999 03:46:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hda.hda.com (hda-bicnet.bicnet.net [209.244.238.132] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA09569 for ; Thu, 7 Jan 1999 03:46:55 -0800 (PST) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id GAA02126; Thu, 7 Jan 1999 06:42:35 -0500 (EST) From: Peter Dufault Message-Id: <199901071142.GAA02126@hda.hda.com> Subject: Re: Problem with -current, SMP and multiple 'nice' processes? In-Reply-To: <3694895D.37DEEE92@tdx.co.uk> from Karl Pielorz at "Jan 7, 99 10:15:57 am" To: kpielorz@tdx.co.uk (Karl Pielorz) Date: Thu, 7 Jan 1999 06:42:35 -0500 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (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 > If I run the client again {as per RC5's instructions for SMP FreeBSD machines} > the load average goes up to 2.0 (as I'd guess you'd expect), and the machine > performs like a dog... I think "maybe_resched()" doesn't work for SMP. It is called by wakeup(). It is checking curproc directly. For now it probably needs to do an unconditional need_resched() in the SMP case. Note that there is a revised version on ftp.freebsd.org in pub/FreeBSD/development/misc/PATCHES.sched. It doesn't fix this problem, but if someone is going to trace through things I'd appreciate them working through that. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 03:56:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA10427 for freebsd-current-outgoing; Thu, 7 Jan 1999 03:56:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA10394 for ; Thu, 7 Jan 1999 03:55:51 -0800 (PST) (envelope-from narvi@haldjas.folklore.ee) Received: from haldjas.folklore.ee (haldjas.folklore.ee [172.17.2.1] (may be forged)) by haldjas.folklore.ee (8.8.8/8.8.4) with SMTP id NAA05891; Thu, 7 Jan 1999 13:54:21 +0200 (EET) Date: Thu, 7 Jan 1999 13:54:21 +0200 (EET) From: Narvi To: "Jordan K. Hubbard" cc: freebsd-current@FreeBSD.ORG Subject: Re: News Server In-Reply-To: <6432.915565290@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 [cc: list trimmed. It's a stupid message anyways] On Tue, 5 Jan 1999, Jordan K. Hubbard wrote: > > I don't really see the need, people can pick it up someplace > > and if they don't want it they can say no. > > Yeah, but Joel will send out rmgroup messages to all and sundry for > anything which doesn't meet his (prior) approval. > Can I sell you a bad idea? A really bad idea that just might work? Include a patch on www.freebsd.org for the news system (inn, etc.) that disables group operations for freebsd.* with a message that it is needed if you want to have the feed. > > I guess alt.freebsd.* could be a more legal alternative ? > > Yes. > > - Jordan > Sander There is no love, no good, no happiness and no future - all these are just illusions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 06:13:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA20927 for freebsd-current-outgoing; Thu, 7 Jan 1999 06:13:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA20922 for ; Thu, 7 Jan 1999 06:13:45 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id XAA24660; Thu, 7 Jan 1999 23:13:11 +0900 (JST) Message-ID: <3694BE0B.DA353B2@newsguy.com> Date: Thu, 07 Jan 1999 23:00:43 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: John Polstra , current@FreeBSD.ORG Subject: Re: CVS issues References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > > On 31-Dec-98 Doug wrote: > > Chris Timmons wrote: > >> > >> Different CVSup servers allow different numbers of connections. I can't > >> remember what you said would happen when the client gets connection > >> refused and has more A records to try; will it go to the next one? > > > > All well written network clients of any kind should do just that. :) > > That's pretty stringent. What about a well-written client that just > happens to have one little bug? :-) Well, you can always say it *DOES* that, but, because of a little bug (the code is not there), it isn't doing it right now (or all the previous versions). Still, it is not a design error, it is just a bug! :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com "Heart like a Gabriel, pure and white as ivory, soul like a lucifer, black and cold as a piece of lead." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 06:48:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA24956 for freebsd-current-outgoing; Thu, 7 Jan 1999 06:48:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA24951 for ; Thu, 7 Jan 1999 06:48:21 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id PAA24637 for ; Thu, 7 Jan 1999 15:47:52 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id PAA35406 for current@freebsd.org; Thu, 7 Jan 1999 15:47:52 +0100 (MET) Message-ID: <19990107154627.L16187@follo.net> Date: Thu, 7 Jan 1999 15:46:27 +0100 From: Eivind Eklund To: hackers@FreeBSD.ORG Subject: Adding KASSERT() - DIAGNOSTIC split Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm planning to split DIAGNOSTIC and add KASSERT(assertion, ("Panic message", ...)); to the kernel (based on discussion on -hackers about 1/2 year ago). The changes are: - Add KASSERT() - Split DIAGNOSTIC into three options - DIAGNOSTIC, INVARIANTS and INVARIANT_SUPPORT. 'INVARIANTS' will take over the documented (but not real) meaning of DIAGNOSTIC - activating kernel invariants. INVARIANT_SUPPORT is to make it possible to activate INVARIANTS for any single file in the system - it enable the compilation of functions made for checking data structures, but doesn't enable the actual checks. DIAGNOSTIC will be used to cover extra diagnostic messages, but not to enable extra panic()s. - Change the occurances of #ifdef DIAGNOSTIC in kern/ and vm/ to to #ifdef INVARIANTS, #ifdef INVARIANT_SUPPORT, #ifdef DIAGNOSTIC or KASSERT() as appropriate. Patches for all of this is already at http://www.freebsd.org/~eivind/KASSERT.patch I'll commit these changes within a couple of days unless I get objections; be warned that I'm converting a lot of DIAGNOSTIC stuff to KASSERT() form, so if I'm unlucky there may be changes in behaviour (AKA bugs) in the invariants. Consider this your heads-up WRT that. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 09:01:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07947 for freebsd-current-outgoing; Thu, 7 Jan 1999 09:01:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www.scancall.no (www.scancall.no [195.139.183.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA07938 for ; Thu, 7 Jan 1999 09:01:24 -0800 (PST) (envelope-from Marius.Bendiksen@scancall.no) Received: from super2.langesund.scancall.no [195.139.183.29] by www with smtp id BBYGLLOJ; Thu, 07 Jan 99 17:00:54 GMT (PowerWeb version 4.04r6) Message-Id: <3.0.5.32.19990107180054.00a41b70@mail.scancall.no> X-Sender: Marius@mail.scancall.no X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Thu, 07 Jan 1999 18:00:54 +0100 To: Kenneth Wayne Culver , Sue Blake From: Marius Bendiksen Subject: Re: Kernel configurator Cc: npe@bfc.dk, freebsd-current@FreeBSD.ORG In-Reply-To: References: <19990105023845.24430@welearn.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Unless I'm mistaken, don't the options USERCONFIG, and its visual >counterpart already implement a "Kernel Configurator??" It's my >understanding that they do. I believe he's referring to something which makes a kernel configuration file for you, and then compiles and installs the new kernel. --- Marius Bendiksen, IT-Trainee, ScanCall AS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 09:02:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08309 for freebsd-current-outgoing; Thu, 7 Jan 1999 09:02:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www.scancall.no (www.scancall.no [195.139.183.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA08301 for ; Thu, 7 Jan 1999 09:02:56 -0800 (PST) (envelope-from Marius.Bendiksen@scancall.no) Received: from super2.langesund.scancall.no [195.139.183.29] by www with smtp id BBYGVAGJ; Thu, 07 Jan 99 17:02:27 GMT (PowerWeb version 4.04r6) Message-Id: <3.0.5.32.19990107180227.00a77390@mail.scancall.no> X-Sender: Marius@mail.scancall.no X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Thu, 07 Jan 1999 18:02:27 +0100 To: npe@bfc.dk, Freebsd-current@FreeBSD.ORG From: Marius Bendiksen Subject: Re: Kernel configurator In-Reply-To: <412566F1.00413EBE.00@bfc.dk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This sounds like a very good idea, to me. --- Marius Bendiksen, IT-Trainee, ScanCall AS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 09:11:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09086 for freebsd-current-outgoing; Thu, 7 Jan 1999 09:11:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dt087nac.san.rr.com (dt051n92.san.rr.com [204.210.32.146]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA09081 for ; Thu, 7 Jan 1999 09:11:10 -0800 (PST) (envelope-from Studded@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt087nac.san.rr.com (8.8.8/8.8.8) with ESMTP id JAA09231; Thu, 7 Jan 1999 09:11:00 -0800 (PST) (envelope-from Studded@gorean.org) Message-ID: <36939924.BDD55914@gorean.org> Date: Wed, 06 Jan 1999 09:11:00 -0800 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: John Polstra CC: current@FreeBSD.ORG Subject: Re: CVS issues References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > > On 31-Dec-98 Doug wrote: > > Chris Timmons wrote: > >> > >> Different CVSup servers allow different numbers of connections. I can't > >> remember what you said would happen when the client gets connection > >> refused and has more A records to try; will it go to the next one? > > > > All well written network clients of any kind should do just that. :) > > That's pretty stringent. What about a well-written client that just > happens to have one little bug? :-) *Chuckle* Thence the smiley. This is actually something that many client programs don't do. :-/ The good news is that it's usually easy to fix. Doug -- *** Chief Operations Officer, DALnet IRC network *** Like desperadoes waiting for a train . . . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 09:18:41 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09923 for freebsd-current-outgoing; Thu, 7 Jan 1999 09:18:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA09913 for ; Thu, 7 Jan 1999 09:18:38 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id JAA25727; Thu, 7 Jan 1999 09:18:09 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id JAA40685; Thu, 7 Jan 1999 09:18:09 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990107074732.28807.qmail@ns.oeno.com> Date: Thu, 07 Jan 1999 09:18:08 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Ville-Pertti Keinonen Subject: Re: CVS issues Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 07-Jan-99 Ville-Pertti Keinonen wrote: > > That's when everything is working right. > > If all of the mirror sites are basically independent, there's no way > to know for sure that all of the mirror sites are working properly, > one of them may even be several days behind, for whatever reason (like > broken networks isolating it from freefall). > > I would prefer to know that when I run cvsup, I'm going to get a newer > version of the FreeBSD repository, not an older one. I have to admit, you've got a point. I can see how to enhance CVSup to guard against that problem. But it would require a new version of CVSup, of course. Maybe the round-robin DNS idea should wait until that's available. > When using a specific mirror, something has to get *really* screwed > up for that to happen. Right. The mirror maintainer would really have to make an effort to screw things up that badly. :-) > At the very least, problems with one mirror could cause significant > increases in traffic on all mirrors. I'm not too worried about that, since it happens anyway (manually). Also, all the mirrors can and do limit their traffic by means of the cvsupd.access file. Thanks for your comments. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 09:20:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10189 for freebsd-current-outgoing; Thu, 7 Jan 1999 09:20:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA10179 for ; Thu, 7 Jan 1999 09:20:34 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id JAA25761; Thu, 7 Jan 1999 09:20:05 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id JAA40693; Thu, 7 Jan 1999 09:20:04 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <36939924.BDD55914@gorean.org> Date: Thu, 07 Jan 1999 09:20:04 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Studded Subject: Re: CVS issues Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 06-Jan-99 Studded wrote: >> >> That's pretty stringent. What about a well-written client that just >> happens to have one little bug? :-) > > *Chuckle* Thence the smiley. This is actually something that many > client programs don't do. :-/ CVSup does it right, but only by virtue of good luck. :-) John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 09:21:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10271 for freebsd-current-outgoing; Thu, 7 Jan 1999 09:21:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from server.noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA10259 for ; Thu, 7 Jan 1999 09:21:14 -0800 (PST) (envelope-from geoffb@gti.noc.demon.net) Received: by server.noc.demon.net; id RAA02326; Thu, 7 Jan 1999 17:20:44 GMT Received: from gti.noc.demon.net(195.11.55.101) by inside.noc.demon.net via smap (3.2) id xma002314; Thu, 7 Jan 99 17:20:29 GMT Received: (from geoffb@localhost) by gti.noc.demon.net (8.8.8/8.8.8) id RAA26658; Thu, 7 Jan 1999 17:20:25 GMT Message-ID: <19990107172024.A25899@gti.noc.demon.net> Date: Thu, 7 Jan 1999 17:20:24 +0000 From: Geoff Buckingham To: "Richard Seaman, Jr." , current@FreeBSD.ORG Subject: Re: Squid + linuxthreads in action wrt crash Reply-To: Geoff Buckingham References: <19990106142240.A375@tar.com> <19990106151732.A752@tar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990106151732.A752@tar.com>; from Richard Seaman, Jr. on Wed, Jan 06, 1999 at 03:17:32PM -0600 Organisation: Demon Internet Ltd Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG More on the crash we had: We reproduces it again today and captured some core. Now I'm way out of my depth here but... (kgdb) bt #0 0xf0131e9f in boot () #1 0xf01321c8 in at_shutdown () #2 0xf01ba9ad in trap_fatal () #3 0xf01ba443 in trap_pfault () #4 0xf01ba0d6 in trap () #5 0xf01b933f in generic_bzero () #6 0xf01a7344 in vm_object_allocate () #7 0xf01ac824 in vnode_pager_alloc () #8 0xf01587e7 in vfs_object_create () #9 0xf015d2b2 in vn_open () #10 0xf0159d1d in open () #11 0xf01bac3f in syscall () #12 0xf01b124c in Xint0x80_syscall () #13 0x804ebd6 in ?? () #14 0x280df990 in ?? () #15 0x280dff49 in ?? () #16 0x280dff09 in ?? () #17 0x280dfb47 in ?? () #18 0x400 in ?? () #19 0x83ffffd0 in ?? () (kgdb) This is current plus linux threads softupdates and ccd, are any of them particularly implicated by the above? Also I had trouble geting the above as the kernel is a.out and has no debugging symbols. I got to the above by recompiling the kernel that crashed after a config -g and using that as 'symbol-file' for kgdb and the actual kernel as 'exec-file' on a second, older machine with an a.out gdb. How unsafe was this? For anyone wishing to try and reproduce this or just interested in the potential of kthreads and squid, the following is the output of systat at the time of the crash, the system had been running under this load for about 10 mins: 3 users Load 1.02 1.00 0.76 Thu Jan 7 12:50 Mem:KB REAL VIRTUAL VN PAGER SWAP PAGER Tot Share Tot Share Free in out in out Act 113856 2072 156124 4392 95996 count All 935636 6712 1640992 10392 pages cow Interrupts Proc:r p d s w Csw Trp Sys Int Sof Flt zfod 1658 total 1 6 23 1330 928 5639 1659 679 9 75484 wire 100 clk0 irq0 118608 act 128 rtc0 irq8 50.1%Sys 6.8%Intr 35.7%User 0.0%Nice 7.4%Idl 739080 inact 110 pci irq10 | | | | | | | | | | cache 1285 pci irq11 =========================+++>>>>>>>>>>>>>>>>>> 95996 free fdc0 irq6 daefr 35 sio0 irq4 Namei Name-cache Dir-cache prcfr sio1 irq3 Calls hits % hits % react 1191 920 77 24 2 pdwake pdpgs Discs da0 da1 da2 da3 da4 da5 ccd0 intrn KB/t 21.11 8.66 6.91 6.81 8.40 8.90 7.49 8345 buf tps 2 16 37 35 10 12 111 72689 desiredvnodes MB/s 0.04 0.14 0.25 0.23 0.08 0.11 0.81 69461 numvnodes 28 freevnodes I will attempt to do this again in the next few days without ccd and softupdates. Is debugging going to be made easier or immposible by switching to an elf kernel? -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 10:09:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15915 for freebsd-current-outgoing; Thu, 7 Jan 1999 10:09:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA15910 for ; Thu, 7 Jan 1999 10:09:12 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac10.wam.umd.edu ((IDENT root)@rac10.wam.umd.edu [128.8.10.150]) by po3.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id NAA13993; Thu, 7 Jan 1999 13:08:26 -0500 (EST) Received: from rac10.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1]) by rac10.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id NAA20801; Thu, 7 Jan 1999 13:08:24 -0500 (EST) Received: from localhost by rac10.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id NAA20796; Thu, 7 Jan 1999 13:08:22 -0500 (EST) X-Authentication-Warning: rac10.wam.umd.edu: culverk owned process doing -bs Date: Thu, 7 Jan 1999 13:08:22 -0500 (EST) From: Kenneth Wayne Culver To: Marius Bendiksen cc: npe@bfc.dk, Freebsd-current@FreeBSD.ORG Subject: Re: Kernel configurator In-Reply-To: <3.0.5.32.19990107180227.00a77390@mail.scancall.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > This sounds like a very good idea, to me. > It would be a pain. Every time a new kernel option or device got added, the program would have to be changed. It would seem to me that this is just another thing to remember to update. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 10:15:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA16610 for freebsd-current-outgoing; Thu, 7 Jan 1999 10:15:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rt2.synx.com (tech.boostworks.com [194.167.81.239]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA16601 for ; Thu, 7 Jan 1999 10:15:08 -0800 (PST) (envelope-from root@synx.com) Received: from synx.com (rn.synx.com [192.1.1.241]) by rt2.synx.com (8.9.1/8.9.1) with ESMTP id TAA00741; Thu, 7 Jan 1999 19:19:56 +0100 (CET) Message-Id: <199901071819.TAA00741@rt2.synx.com> Date: Thu, 7 Jan 1999 19:13:28 +0100 (CET) From: Remy Nonnenmacher Reply-To: remy@synx.com Subject: Re: Kernel configurator To: culverk@wam.umd.edu 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 On 7 Jan, Kenneth Wayne Culver wrote: >> >> This sounds like a very good idea, to me. >> > It would be a pain. Every time a new kernel option or device got added, > the program would have to be changed. It would seem to me that this is > just another thing to remember to update. > And what about having the device or option surrounded with special comments in the LINT file. The configurator would be able to extract informations/constraints/values from there !. (Just a though, as the LINT file serves me as a reference for parameters). RN. IhM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 10:17:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA16997 for freebsd-current-outgoing; Thu, 7 Jan 1999 10:17:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mortar.carlson.com (mortar.carlson.com [208.240.12.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA16992 for ; Thu, 7 Jan 1999 10:17:35 -0800 (PST) (envelope-from veldy@visi.com) Received: from mortar.carlson.com (root@localhost) by mortar.carlson.com with ESMTP id MAA16783 for ; Thu, 7 Jan 1999 12:16:26 -0600 (CST) Received: from w142844 ([172.25.99.35]) by mortar.carlson.com with SMTP id MAA16719 for ; Thu, 7 Jan 1999 12:16:23 -0600 (CST) Message-ID: <00d001be3a69$f54c0690$236319ac@w142844.carlson.com> From: "Thomas T. Veldhouse" To: "FreeBSD-Current" Subject: Re: Kernel configurator Date: Thu, 7 Jan 1999 12:17:15 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would think that this sort of thing would only be "required" to be updated for RELEASE and STABLE. The rest of the time there may be a lag if you use the configurator. Tom Veldhouse veldy@visi.com -----Original Message----- From: Kenneth Wayne Culver To: Marius Bendiksen Cc: npe@bfc.dk ; Freebsd-current@FreeBSD.ORG Date: Thursday, January 07, 1999 12:09 PM Subject: Re: Kernel configurator >> >> This sounds like a very good idea, to me. >> >It would be a pain. Every time a new kernel option or device got added, >the program would have to be changed. It would seem to me that this is >just another thing to remember to update. > >Kenneth Culver > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 10:31:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18381 for freebsd-current-outgoing; Thu, 7 Jan 1999 10:31:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from boco.fee.vutbr.cz (boco.fee.vutbr.cz [147.229.9.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18374 for ; Thu, 7 Jan 1999 10:31:31 -0800 (PST) (envelope-from cejkar@dcse.fee.vutbr.cz) Received: from kazi.dcse.fee.vutbr.cz (kazi.dcse.fee.vutbr.cz [147.229.8.12]) by boco.fee.vutbr.cz (8.9.2/8.9.2) with ESMTP id TAA52859 for ; Thu, 7 Jan 1999 19:30:56 +0100 (CET) Received: (from cejkar@localhost) by kazi.dcse.fee.vutbr.cz (8.9.2/8.9.2) id TAA26342 for freebsd-current@freebsd.org; Thu, 7 Jan 1999 19:30:55 +0100 (CET) From: Cejka Rudolf Message-Id: <199901071830.TAA26342@kazi.dcse.fee.vutbr.cz> Subject: Why doscmd isn't builded by default? To: freebsd-current@FreeBSD.ORG (freebsd-current@freebsd.org) Date: Thu, 7 Jan 1999 19:30:55 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm looking into -CURRENT src/usr.bin/Makefile and there isn't any information about doscmd so it isn't builded by default. Is there any reason not to build doscmd by default? --=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=-- Rudolf Cejka (cejkar@dcse.fee.vutbr.cz; http://www.fee.vutbr.cz/~cejkar) Technical University of Brno, Faculty of El. Engineering and Comp. Science Bozetechova 2, 612 66 Brno, Czech Republic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 10:33:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18742 for freebsd-current-outgoing; Thu, 7 Jan 1999 10:33:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18727 for ; Thu, 7 Jan 1999 10:32:58 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac7.wam.umd.edu ((IDENT root)@rac7.wam.umd.edu [128.8.10.147]) by po4.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id NAA12616; Thu, 7 Jan 1999 13:33:39 -0500 (EST) Received: from rac7.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1]) by rac7.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id NAA28399; Thu, 7 Jan 1999 13:32:14 -0500 (EST) Received: from localhost by rac7.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id NAA28394; Thu, 7 Jan 1999 13:32:13 -0500 (EST) X-Authentication-Warning: rac7.wam.umd.edu: culverk owned process doing -bs Date: Thu, 7 Jan 1999 13:32:12 -0500 (EST) From: Kenneth Wayne Culver To: Remy Nonnenmacher cc: Freebsd-current@FreeBSD.ORG Subject: Re: Kernel configurator In-Reply-To: <199901071819.TAA00741@rt2.synx.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 sounds like a very good idea, to me. > >> > > It would be a pain. Every time a new kernel option or device got added, > > the program would have to be changed. It would seem to me that this is > > just another thing to remember to update. > > > > And what about having the device or option surrounded with special > comments in the LINT file. The configurator would be able to extract > informations/constraints/values from there !. > > (Just a though, as the LINT file serves me as a reference for > parameters). > It could be possible, I guess, although I'm sure that there would have to be some sort of way to explain each of the device drivers. Are we talking about doing this the same way that sysinstall looks, or are we talking about an X program? Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 10:35:42 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18962 for freebsd-current-outgoing; Thu, 7 Jan 1999 10:35:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18957 for ; Thu, 7 Jan 1999 10:35:40 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac7.wam.umd.edu ((IDENT root)@rac7.wam.umd.edu [128.8.10.147]) by po4.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id NAA12818; Thu, 7 Jan 1999 13:36:14 -0500 (EST) Received: from rac7.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1]) by rac7.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id NAA28508; Thu, 7 Jan 1999 13:34:49 -0500 (EST) Received: from localhost by rac7.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id NAA28503; Thu, 7 Jan 1999 13:34:47 -0500 (EST) X-Authentication-Warning: rac7.wam.umd.edu: culverk owned process doing -bs Date: Thu, 7 Jan 1999 13:34:47 -0500 (EST) From: Kenneth Wayne Culver To: "Thomas T. Veldhouse" cc: FreeBSD-Current Subject: Re: Kernel configurator In-Reply-To: <00d001be3a69$f54c0690$236319ac@w142844.carlson.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, 7 Jan 1999, Thomas T. Veldhouse wrote: > I would think that this sort of thing would only be "required" to be updated > for RELEASE and STABLE. The rest of the time there may be a lag if you use > the configurator. > > Tom Veldhouse > veldy@visi.com Well, I don't think that would be a problem, I guess all the devices could be read from LINT, that way we wouldn't have to hardcode the devices into the configurator program. That idea came from someone else on this mailing list, I neglected to look at that person's name, but I can't take credit. Kenneth Culver > > -----Original Message----- > From: Kenneth Wayne Culver > To: Marius Bendiksen > Cc: npe@bfc.dk ; Freebsd-current@FreeBSD.ORG > > Date: Thursday, January 07, 1999 12:09 PM > Subject: Re: Kernel configurator > > > >> > >> This sounds like a very good idea, to me. > >> > >It would be a pain. Every time a new kernel option or device got added, > >the program would have to be changed. It would seem to me that this is > >just another thing to remember to update. > > > >Kenneth Culver > > > > > >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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 10:36:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA19053 for freebsd-current-outgoing; Thu, 7 Jan 1999 10:36:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA19045 for ; Thu, 7 Jan 1999 10:36:11 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id NAA57590; Thu, 7 Jan 1999 13:40:04 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Thu, 7 Jan 1999 13:40:04 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Cejka Rudolf cc: "freebsd-current@freebsd.org" Subject: Re: Why doscmd isn't builded by default? In-Reply-To: <199901071830.TAA26342@kazi.dcse.fee.vutbr.cz> Message-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, 7 Jan 1999, Cejka Rudolf wrote: > > I'm looking into -CURRENT src/usr.bin/Makefile and there isn't any > information about doscmd so it isn't builded by default. > Is there any reason not to build doscmd by default? It requires X. -Alfred > > --=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=-- > Rudolf Cejka (cejkar@dcse.fee.vutbr.cz; http://www.fee.vutbr.cz/~cejkar) > Technical University of Brno, Faculty of El. Engineering and Comp. Science > Bozetechova 2, 612 66 Brno, Czech Republic > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 11:58:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27651 for freebsd-current-outgoing; Thu, 7 Jan 1999 11:58:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from virtualmaster3-int.prodigy.net (virtualmaster3-ext.prodigy.net [207.115.59.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27645 for ; Thu, 7 Jan 1999 11:58:27 -0800 (PST) (envelope-from publish9923@att.com) Received: from bsbpub (CHCGB103-41.splitrock.net [209.156.10.87]) by virtualmaster3-int.prodigy.net (8.8.5/8.8.5) with SMTP id OAA90066; Thu, 7 Jan 1999 14:57:37 -0500 Date: Thu, 7 Jan 1999 14:57:37 -0500 Message-Id: <199901071957.OAA90066@virtualmaster3-int.prodigy.net> From: "BSB Publishing Co." To: Subject: New Book - "How To Juggle Women: Without Getting Killed or Going Broke" 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 Women all over America have said, "Burn This Book!!!" CALL TO ORDER YOUR COPY - (800) 830-2047 [24hrs] How To Juggle Women: Without Getting Killed or Going Broke by Stefan Feller ISBN:0-9658299-4-4 Price: $12.00 This book is an essential guide for the seasoned dating man who needs help organizing the women in his life. Women are constantly grabbing your interest and attention. Do you have to choose on over the other? Of Course not! Stop letting opportunities like these go to waste. Why not date them all? This is a must-read for men who are active on the dating scene. Not only will you learn how to juggle several females at a time, you will also improve your overall chances with women, including where to meet them and how to do the little things to keep them happy. You will learn time-saving techniques that will maximize your availability, and allow you to spend time with several ladies a day. The author details scheduling methods so you never have two dates at the same time. You will also learn money-saving tips so you can date aggressively and still have money left to by necessities like beer. Forget the saying,"For every man there is a woman out there." Now it will be, "For every man there are at least three women." -------------------------------------------------------- CHAPTER TITLES Chapter One - Getting to Know You Chapter Two - Categories of Women Chapter Three - Where to Find Them Chapter Four - The Rotation Chapter Five - Prior Planning Chapter Six - How to Keep Them Happy and Away From Each Other Chapter Seven - Fiscally Fit Chapter Eight - Personnel Changes -------------------------------------------------------- Juggling Women: Without Getting Killed or Going Broke by Stefan Feller ISBN:0-9658299-4-4 Price: $12.00 $3.00 Shipping individuals - COD Charges are free for a limited time. Wholesale Discounts Available --------------------------------------------------------- Order by Phone 1 (800)830-2047 24 hours a day --------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 12:00:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA28053 for freebsd-current-outgoing; Thu, 7 Jan 1999 12:00:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA28046 for ; Thu, 7 Jan 1999 12:00:09 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA09956; Thu, 7 Jan 1999 11:55:18 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdrq9952; Thu Jan 7 19:55:11 1999 Date: Thu, 7 Jan 1999 11:55:08 -0800 (PST) From: Julian Elischer To: Ville-Pertti Keinonen cc: jdp@polstra.com, current@FreeBSD.ORG Subject: Re: CVS issues In-Reply-To: <19990107074732.28807.qmail@ns.oeno.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 there should be a file in the central repository that is changed every hour by a cron job... that would give us a good way to check whether a particular mirror is up-to date, and to check the lag. the file would simply contain the time in GMT.. On 7 Jan 1999, Ville-Pertti Keinonen wrote: > > > > What happens if you cvsup from a site that has an older version of the > > > tree than you do? > > > Since the relevant mirror sites all update themselves hourly from > > freefall, that's unlikely. You would have to run cvsup twice in > > an hour for it to happen. It could still happen if you lost the > > connection and then reconnected to a different server. But even then > > the damage would be fairly small. Any changes that existed on the > > first server but not on the second server would be taken away. But > > normally, not much happens in an hour in the FreeBSD repository. And > > those changes that were removed would come back again on your next > > update. > > That's when everything is working right. > > If all of the mirror sites are basically independent, there's no way > to know for sure that all of the mirror sites are working properly, > one of them may even be several days behind, for whatever reason (like > broken networks isolating it from freefall). > > I would prefer to know that when I run cvsup, I'm going to get a newer > version of the FreeBSD repository, not an older one. When using a > specific mirror, something has to get *really* screwed up for that to > happen. Of course I don't use any of the US mirrors myself, anyhow, > but I suspect that losing changes may cause unexpected problems. Use > your imagination. ;--) > > At the very least, problems with one mirror could cause significant > increases in traffic on all mirrors. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 12:31:59 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA02044 for freebsd-current-outgoing; Thu, 7 Jan 1999 12:31:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alushta.NL.net (alushta.NL.net [193.78.240.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA02026 for ; Thu, 7 Jan 1999 12:31:54 -0800 (PST) (envelope-from benst@terminus.stuyts.nl) Received: from stuyts by alushta.NL.net with UUCP id <10676-13572>; Thu, 7 Jan 1999 21:30:53 +0100 Received: from daneel.stuyts.nl (daneel.stuyts.nl [193.78.231.7]) by terminus.stuyts.nl (8.9.1/8.9.1) with ESMTP id VAA01181 for ; Thu, 7 Jan 1999 21:15:54 +0100 (MET) (envelope-from benst) Received: (from benst@localhost) by daneel.stuyts.nl (8.8.5/8.8.5) id VAA09302 for current@freebsd.org; Thu, 7 Jan 1999 21:15:50 +0100 (MET) Message-Id: <199901072015.VAA09302@daneel.stuyts.nl> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 3.3 v118.2) X-Nextstep-Mailer: Mail 3.3 (Enhance 1.2) Received: by NeXT.Mailer (1.118.2) From: Ben Stuyts Date: Thu, 7 Jan 99 21:15:47 +0100 To: current@FreeBSD.ORG Subject: Timedout SCB handled by another timeout Reply-To: ben@stuyts.nl Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, My SMP system was wedged with the message in the subject about 10 times on the console. What does that mean? Is this pointing towards a hardware failure or is it software related? This is a Gigabyte 586DX with dual P166MMX and 64 MB ram. Below is a dmesg output. Thanks, Ben Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #0: Sun Jan 3 20:59:10 MET 1999 benst@terminus.stuyts.nl:/usr/source/src/sys/compile/TERMINUS-SMP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P55C (586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping=3 Features=0x8003bf real memory = 67108864 (65536K bytes) config> quit avail memory = 62238720 (60780K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00030010, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00030010, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xf02e2000. Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 ide_pci0: rev 0x00 on pci0.7.1 ncr0: rev 0x12 int a irq 16 on pci0.8.0 de0: rev 0x11 int a irq 17 on pci0.9.0 de0: SMC 21041 [10Mb/s] pass 1.1 de0: address 00:00:c0:1f:54:e8 vga0: rev 0x02 int a irq 18 on pci0.10.0 ahc0: rev 0x00 int a irq 19 on pci0.12.0 ahc0: Using left over BIOS settings ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio2 at 0x3e8-0x3ef irq 10 on isa sio2: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S npx0 on motherboard npx0: INT 16 interface sb0 at 0x220 irq 5 drq 1 on isa snd0: sbxvi0 at drq 5 on isa snd0: sbmidi0 at 0x300 on isa snd0: awe0 at 0x620 on isa AWE32: not detected opl0 at 0x388 on isa snd0: joy0 at 0x201 on isa joy0: joystick Intel Pentium detected, installing workaround for F00F bug APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 IP packet filtering initialized, divert enabled, rule-based forwarding disabled, unlimited logging Waiting 5 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! da1 at ahc0 bus 0 target 3 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.0MB/s transfers (10.0MHz, offset 8) da1: 810MB (1660299 512 byte sectors: 64H 32S/T 810C) changing root device to da0s1a cd0 at ahc0 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.0MB/s transfers (10.0MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present da0 at ahc0 bus 0 target 1 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4134MB (8467200 512 byte sectors: 64H 32S/T 4134C) WARNING: / was not properly dismounted de0: enabling BNC port cd1 at ahc0 bus 0 target 5 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 3.300MB/s transfers cd1: Attempt to query device size failed: NOT READY, Logical unit not ready, cause not reportable ffs_mountfs: superblock updated for soft updates To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 12:45:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA03539 for freebsd-current-outgoing; Thu, 7 Jan 1999 12:45:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.gtn.com (mail.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA03534 for ; Thu, 7 Jan 1999 12:45:45 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by mail.gtn.com (8.8.6/8.8.6) with UUCP id VAA14645 for current@FreeBSD.ORG; Thu, 7 Jan 1999 21:45:03 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.1/8.9.1) id VAA20523 for current@FreeBSD.ORG; Thu, 7 Jan 1999 21:33:55 +0100 (CET) (envelope-from andreas) Date: Thu, 7 Jan 1999 21:33:55 +0100 From: Andreas Klemm To: current@FreeBSD.ORG Subject: can't boot from CD and floppy after make release Message-ID: <19990107213355.A20076@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There is still something wrong... The boot floppy loads and loads and loads, then: Warning: malloc wrapped Booting from CD-Rom isn't successfull, halts after loading kernel ... Current from 2 days before (990105) -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 13:12:43 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08403 for freebsd-current-outgoing; Thu, 7 Jan 1999 13:12:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from soleil.uvsq.fr (soleil.uvsq.fr [193.51.24.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA08393 for ; Thu, 7 Jan 1999 13:12:41 -0800 (PST) (envelope-from son@teaser.fr) Received: from teaser.fr (rtc103.reseau.uvsq.fr [193.51.24.19]) by soleil.uvsq.fr (8.9.1/jtpda-5.3.1) with ESMTP id WAA16617 ; Thu, 7 Jan 1999 22:12:06 +0100 (MET) Received: (from son@localhost) by teaser.fr (8.9.1/8.9.1) id XAA00853; Thu, 7 Jan 1999 23:15:44 GMT (envelope-from son) Message-ID: <19990107231544.61205@breizh.prism.uvsq.fr> Date: Thu, 7 Jan 1999 23:15:44 +0000 From: Nicolas Souchu To: Alexander Leidinger Cc: current@FreeBSD.ORG Subject: Re: nlpt & polling mode didn't work References: <19981229221203.55044@breizh.prism.uvsq.fr> <199901041137.MAA10608@wurzelausix> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199901041137.MAA10608@wurzelausix>; from Alexander Leidinger on Mon, Jan 04, 1999 at 12:37:29PM +0100 X-Operating-System: FreeBSD breizh 3.0-CURRENT FreeBSD 3.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 04, 1999 at 12:37:29PM +0100, Alexander Leidinger wrote: > >On 29 Dec, Nicolas Souchu wrote: > >>>$Subject anymore after cvsup (98.12.24). >>>The working one is around release (sorry, can't be more specific). >> >> September, October...? > >~1 day before release. > >>>The problem: >>>It takes a looooong time to send data to the printer. >> >> Printing is ok? > >I think (nobody wants to wait more than 15 minutes for the page). >BTW: I have only 3rd person access to it. Its the system of my brother, >and hi is only an user. And I imagine the old-lpt code works. > >> This is polling... and interrupts? > >Its an additional 3rd party interface card (a little bit old). Only >polling possible (no modern features like e.g. ECP). >Over the motherboard chipset everything is fine (only interrupts >tested). > >> What's your chipset? > >The 3rd party cards have >MP101D >HC138 >ALS00A 17KD (Texas Instruments?) >and >HM82C11C 9739 C79N5 >on them. I recognize none. > >Joerg Wunsch wrote: >> Btw., the question about which printer also belongs here. > >There are two printers connected, a HP OfficeJet 635 via the on board >chipset and a Kyocera FS-600 (laser) via the 3rd party card. Connecting >the laser to the motherboard port works fine, but on the 3rd party card >it needs ages to print a page. As already mentioned, this didn't happen >with ~3.0-release. You may add printfs to the /sys/dev/ppbus/nlpt.c to check where it fails. > >Bye, >Alexander. > >-- >http://netchild.home.pages.de A.Leidinger @ wurzelausix.cs.uni-sb.de > > -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 13:17:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09093 for freebsd-current-outgoing; Thu, 7 Jan 1999 13:17:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com ([139.92.122.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA09086 for ; Thu, 7 Jan 1999 13:17:27 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id XAA08193; Thu, 7 Jan 1999 23:13:27 +0200 (SAT) From: Robert Nordier Message-Id: <199901072113.XAA08193@ceia.nordier.com> Subject: Re: Kernel cannot mount root with new bootblocks In-Reply-To: <199901070445.UAA30153@yakko.zso.dec.com> from "Reginald S. Perry" at "Jan 6, 99 08:45:43 pm" To: perry@zso.dec.com Date: Thu, 7 Jan 1999 23:13:25 +0200 (SAT) Cc: mike@smith.net.au, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Reginald S. Perry wrote: > I have a vintage 1994 486/66 machine on which I tested the new > bootblocks using the test floppy method described on -current. I > verified that it worked on my dual pentium box before I tested on the > 486. The machine is running the Award bios v4.50G on a Genoa > Turboexpress 486VLG-X2 (Ver A) motherboard. When I try to boot from > floppy, I get a register dump: > > int=0000000e err=00000007 efl=00030296 eip=00005000 > eax=0000918d ebx=00000000 ecx=00000000 edx=00000100 > esi=00000000 edi=0000a809 ebp=000003fc esp=000003fe > cs=0000 ds=0000 es=a809 fs=0000 gs=0000 ss=9e82 > cs:eip=67 00 00 00 67 10 00 00-25 20 00 00 25 30 00 00 > ss:esp=00 00 fc 03 0c 04 00 00-00 01 00 00 8d 91 2d 2f > > > And the system then halts. If you build new floppy images, I am > willing to test them and report the results, but I do not have enough > knowledge of how to debug at this level to be of any help. >From the register dump, this looks like the same problem Peter Wemm had and devised a fix for. Do you have a SCSI controller in the 486 machine? It would be a help if you could try the custom floppy mentioned on his ELF Day page http://www.freebsd.org/~peter/elfday.html and let us know whether this works for you. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 13:25:57 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10135 for freebsd-current-outgoing; Thu, 7 Jan 1999 13:25:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.gtn.com (mail.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA10130 for ; Thu, 7 Jan 1999 13:25:53 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by mail.gtn.com (8.8.6/8.8.6) with UUCP id WAA15224 for current@FreeBSD.ORG; Thu, 7 Jan 1999 22:15:17 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.1/8.9.1) id WAA42474 for current@FreeBSD.ORG; Thu, 7 Jan 1999 22:13:37 +0100 (CET) (envelope-from andreas) Date: Thu, 7 Jan 1999 21:33:55 +0100 From: Andreas Klemm To: current@FreeBSD.ORG Subject: can't boot from CD and floppy after make release Message-ID: <19990107213355.A20076@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There is still something wrong... The boot floppy loads and loads and loads, then: Warning: malloc wrapped Booting from CD-Rom isn't successfull, halts after loading kernel ... Current from 2 days before (990105) -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 13:30:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10842 for freebsd-current-outgoing; Thu, 7 Jan 1999 13:30:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA10834 for ; Thu, 7 Jan 1999 13:30:50 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA01299; Thu, 7 Jan 1999 13:26:31 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901072126.NAA01299@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andreas Klemm cc: current@FreeBSD.ORG Subject: Re: can't boot from CD and floppy after make release In-reply-to: Your message of "Thu, 07 Jan 1999 21:33:55 +0100." <19990107213355.A20076@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 07 Jan 1999 13:26:31 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > There is still something wrong... > The boot floppy loads and loads and loads, then: > Warning: malloc wrapped You're booting a kzipped kernel. Don't do that. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 13:35:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA11510 for freebsd-current-outgoing; Thu, 7 Jan 1999 13:35:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA11505 for ; Thu, 7 Jan 1999 13:35:46 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id NAA34615; Thu, 7 Jan 1999 13:35:02 -0800 (PST) (envelope-from dillon) Date: Thu, 7 Jan 1999 13:35:02 -0800 (PST) From: Matthew Dillon Message-Id: <199901072135.NAA34615@apollo.backplane.com> To: Mike Smith Cc: Andreas Klemm , current@FreeBSD.ORG Subject: Re: can't boot from CD and floppy after make release Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> There is still something wrong... :> The boot floppy loads and loads and loads, then: :> Warning: malloc wrapped : :You're booting a kzipped kernel. Don't do that. kzip is broken now? I *need* kzip for my BOOTP based diskless workstations! -Matt : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 13:42:57 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA12331 for freebsd-current-outgoing; Thu, 7 Jan 1999 13:42:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA12323 for ; Thu, 7 Jan 1999 13:42:55 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA01395; Thu, 7 Jan 1999 13:37:51 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901072137.NAA01395@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon cc: Mike Smith , Andreas Klemm , current@FreeBSD.ORG Subject: Re: can't boot from CD and floppy after make release In-reply-to: Your message of "Thu, 07 Jan 1999 13:35:02 PST." <199901072135.NAA34615@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 07 Jan 1999 13:37:51 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :> There is still something wrong... > :> The boot floppy loads and loads and loads, then: > :> Warning: malloc wrapped > : > :You're booting a kzipped kernel. Don't do that. > > kzip is broken now? I *need* kzip for my BOOTP based > diskless workstations! Kzip doesn't work with the new loader (not properly, anyway). It will still work with a.out kernels loaded via netboot. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 14:16:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17054 for freebsd-current-outgoing; Thu, 7 Jan 1999 14:16:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.gtn.com (mail.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA17044 for ; Thu, 7 Jan 1999 14:16:07 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by mail.gtn.com (8.8.6/8.8.6) with UUCP id XAA16444; Thu, 7 Jan 1999 23:15:03 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.1/8.9.1) id XAA44742; Thu, 7 Jan 1999 23:10:27 +0100 (CET) (envelope-from andreas) Date: Thu, 7 Jan 1999 23:10:27 +0100 From: Andreas Klemm To: Mike Smith Cc: Matthew Dillon , Andreas Klemm , current@FreeBSD.ORG Subject: Re: can't boot from CD and floppy after make release Message-ID: <19990107231027.A44720@titan.klemm.gtn.com> References: <199901072135.NAA34615@apollo.backplane.com> <199901072137.NAA01395@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199901072137.NAA01395@dingo.cdrom.com>; from Mike Smith on Thu, Jan 07, 1999 at 01:37:51PM -0800 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 07, 1999 at 01:37:51PM -0800, Mike Smith wrote: > > :> There is still something wrong... > > :> The boot floppy loads and loads and loads, then: > > :> Warning: malloc wrapped > > : > > :You're booting a kzipped kernel. Don't do that. Hmm, make release brought that ,infrastructure'. So it's still broken. -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 14:18:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17255 for freebsd-current-outgoing; Thu, 7 Jan 1999 14:18:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com ([139.92.122.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA17241; Thu, 7 Jan 1999 14:18:04 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id AAA08638; Fri, 8 Jan 1999 00:16:54 +0200 (SAT) From: Robert Nordier Message-Id: <199901072216.AAA08638@ceia.nordier.com> Subject: Re: How to Build & Run ELF Kernel In-Reply-To: <199901070017.QAA02235@silvia.hip.berkeley.edu> from Satoshi Asami at "Jan 6, 99 04:17:36 pm" To: asami@FreeBSD.ORG (Satoshi Asami) Date: Fri, 8 Jan 1999 00:16:52 +0200 (SAT) Cc: rnordier@nordier.com, bde@zeta.org.au, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Satoshi Asami wrote: > Hmm. All my disks have a FreeBSD partition starting at sector 63 > (start of second track of first cylinder). Here's the one that > doesn't work: > > === > ## fdisk sd0 > ******* Working on device /dev/rsd0 ******* > parameters extracted from in-core disklabel are: > cylinders=263 heads=255 sectors/track=63 (16065 blks/cyl) > > parameters to be used for BIOS calculations are: > cylinders=263 heads=255 sectors/track=63 (16065 blks/cyl) > : > The data for partition 2 is: > sysid 165,(FreeBSD/NetBSD/386BSD) > start 63, size 4225032 (2063 Meg), flag 80 (active) > beg: cyl 0/ sector 1/ head 1; > end: cyl 262/ sector 63/ head 254 > === > > and the one that does work, on the same machine: > > === > ## fdisk sd1 > ******* Working on device /dev/rsd1 ******* > parameters extracted from in-core disklabel are: > cylinders=274 heads=255 sectors/track=63 (16065 blks/cyl) > > parameters to be used for BIOS calculations are: > cylinders=274 heads=255 sectors/track=63 (16065 blks/cyl) > : > The data for partition 2 is: > sysid 165,(FreeBSD/NetBSD/386BSD) > start 63, size 4401747 (2149 Meg), flag 80 (active) > beg: cyl 0/ sector 1/ head 1; > end: cyl 273/ sector 63/ head 254 > === > > As you can see, they are almost identical. The only difference is the > size of the disk/partitions. > > As for other items on your checklist (reproduced here): > > * o Can't get the disk geometry from the BIOS > > It did boot before with the old bootblocks, so it is getting the > geometry, right? > > * o The disk geometry would cause division by zero > * o The derived cylinder number exceeds 1023 > > Both of these shouldn't apply to this case. > > * o BIOS fails to read a sector on five consecutive attempts > > === > ## dd if=/dev/rsd0 of=/dev/null bs=512 count=2048 > 2048+0 records in > 2048+0 records out > 1048576 bytes transferred in 1.827534 secs (573765 bytes/sec) > ## tail /var/log/messages > : > Jan 6 15:00:25 baloon sudo: asami : TTY=ttyp0 ; PWD=/s/c/home/piedmont/asami ; USER=root ; COMMAND=/usr/local/bin/bash > === > > At least it seems quite readable from the FreeBSD kernel. And again, > it was booting fine before I rewrote the bootblocks. Thanks. Though certainly nothing there to suggest the cause of the problem. If you still have the new bootblocks installed, I'd be interested to see if these hexdumps reveal anything: dd if=/dev/rsd0 count=1 | hexdump -C dd if=/dev/rsd0s2a count=17 | hexdump -C dd if=/dev/rsd1 count=1 | hexdump -C dd if=/dev/rsd1s2a count=17 | hexdump -C Maybe there's some slight difference somewhere there that boot1 can't handle. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 14:45:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20596 for freebsd-current-outgoing; Thu, 7 Jan 1999 14:45:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA20591 for ; Thu, 7 Jan 1999 14:45:43 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id OAA67842; Thu, 7 Jan 1999 14:44:50 -0800 (PST) To: Matthew Dillon cc: Mike Smith , Andreas Klemm , current@FreeBSD.ORG Subject: Re: can't boot from CD and floppy after make release In-reply-to: Your message of "Thu, 07 Jan 1999 13:35:02 PST." <199901072135.NAA34615@apollo.backplane.com> Date: Thu, 07 Jan 1999 14:44:50 -0800 Message-ID: <67838.915749090@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > kzip is broken now? I *need* kzip for my BOOTP based > diskless workstations! Then you'll need to port it to ELF. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 14:52:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA21246 for freebsd-current-outgoing; Thu, 7 Jan 1999 14:52:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from proxy.vvm.com (proxy.vvm.com [204.71.94.238]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA21241 for ; Thu, 7 Jan 1999 14:52:24 -0800 (PST) (envelope-from sbarron@vvm.com) Received: from ns.vvm.com (IDENT:root@ns.vvm.com [204.71.94.1]) by proxy.vvm.com (8.9.1/8.9.1) with ESMTP id QAA08793 for ; Thu, 7 Jan 1999 16:53:59 -0600 Received: from avalon.abalonesoft.com (kain@206-97-174-113.vvm.com [206.97.174.113]) by ns.vvm.com (8.9.2/8.9.2) with ESMTP id QAA00844 for ; Thu, 7 Jan 1999 16:51:51 -0600 (EST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 07 Jan 1999 16:52:02 -0600 (CST) From: Scott Barron To: FreeBSD Current Subject: Booting to single user Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, How does one boot to single user mode with the new boot loader? The old one took -s but the help doesn't show anything about it on the new loader. Thanks, Scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 14:55:39 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA21638 for freebsd-current-outgoing; Thu, 7 Jan 1999 14:55:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA21631 for ; Thu, 7 Jan 1999 14:55:38 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA01756; Thu, 7 Jan 1999 14:51:44 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901072251.OAA01756@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Scott Barron cc: FreeBSD Current Subject: Re: Booting to single user In-reply-to: Your message of "Thu, 07 Jan 1999 16:52:02 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 07 Jan 1999 14:51:44 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > How does one boot to single user mode with the new boot loader? The > old one took -s but the help doesn't show anything about it on the new loader. See 'help set boot_single', or just pass '-s' to the boot command or when loading the kernel. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 14:56:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA21976 for freebsd-current-outgoing; Thu, 7 Jan 1999 14:56:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Vorlon.odc.net (Vorlon.odc.net [207.137.42.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA21970 for ; Thu, 7 Jan 1999 14:56:46 -0800 (PST) (envelope-from nwestfal@Vorlon.odc.net) Received: from localhost (nwestfal@localhost) by Vorlon.odc.net (8.8.7/8.8.7) with ESMTP id OAA23777; Thu, 7 Jan 1999 14:56:06 -0800 Date: Thu, 7 Jan 1999 14:56:06 -0800 (PST) From: Neal Westfall To: Scott Barron cc: FreeBSD Current Subject: Re: Booting to single user 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 believe I used "boot -s" to do this.. -- Neal Westfall mailto:nwestfal@odc.net http://www.odc.net/~nwestfal/ FreeBSD: The Power To Serve! http://www.freebsd.org/ $Id: dot.signature,v 1.2 1998/12/30 08:23:13 nwestfal Exp nwestfal $ On Thu, 7 Jan 1999, Scott Barron wrote: > Hello, > > How does one boot to single user mode with the new boot loader? The > old one took -s but the help doesn't show anything about it on the new loader. > > Thanks, > Scott > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 14:58:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA22082 for freebsd-current-outgoing; Thu, 7 Jan 1999 14:58:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from orion.stargate.org (orion.stargate.org [204.181.4.201]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA22077 for ; Thu, 7 Jan 1999 14:58:02 -0800 (PST) (envelope-from ted@stargate.org) Received: from localhost (ted@localhost) by orion.stargate.org (8.9.1/8.9.1) with ESMTP id RAA01250 for ; Thu, 7 Jan 1999 17:01:43 -0500 (EST) (envelope-from ted@stargate.org) Date: Thu, 7 Jan 1999 17:01:42 -0500 (EST) From: "T.D. Brace" To: freebsd-current@FreeBSD.ORG Subject: inetd problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Can anyone tell me if the inetd realloc (and other) problems have been fixed yet? Searching Deja News shows conflicting reports. I checked the current diffs, and built version 1.46 - is this a safe version to use? It's been running on my local workstation for a few days now, but it really doesn't have any load on it. I'd like to copy it up to our webservers, but thought I would ask first. Thank you. -TD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 15:11:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA23150 for freebsd-current-outgoing; Thu, 7 Jan 1999 15:11:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA23145 for ; Thu, 7 Jan 1999 15:11:28 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id PAA35393; Thu, 7 Jan 1999 15:10:58 -0800 (PST) (envelope-from dillon) Date: Thu, 7 Jan 1999 15:10:58 -0800 (PST) From: Matthew Dillon Message-Id: <199901072310.PAA35393@apollo.backplane.com> To: "Jordan K. Hubbard" Cc: Mike Smith , Andreas Klemm , current@FreeBSD.ORG Subject: Re: can't boot from CD and floppy after make release References: <67838.915749090@zippy.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :> kzip is broken now? I *need* kzip for my BOOTP based :> diskless workstations! : :Then you'll need to port it to ELF. : :- Jordan I've got 3 months worth of VM work that needs to be done. I am *not* going to spend a month learning how ELF works just to port kzip. I can barely fit a minimal uncompressed kernel on a floppy now, and then only if I use every last block on the floppy. Add in a minimal number of sound drivers and it becomes impossible. If you guys move to ELF kernels without a working kzip, it will screw over a lot of people, not just me. If you don't break a.out kernel compilation then we can continue to make a.out kernels. But if you break a.out kernel compilation ( make it elf or nothing) it puts a whole bunch of people into a bind. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 15:37:52 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25101 for freebsd-current-outgoing; Thu, 7 Jan 1999 15:37:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA25090 for ; Thu, 7 Jan 1999 15:37:48 -0800 (PST) (envelope-from naddy@mips.rhein-neckar.de) Received: from mips.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id AAA02409 for freebsd-current@freebsd.org; Fri, 8 Jan 1999 00:37:27 +0100 (CET) (envelope-from naddy@mips.rhein-neckar.de) Received: by mips.rhein-neckar.de id m0zyM6w-000WyaC (Debian Smail-3.2.0.101 1997-Dec-17 #2); Thu, 7 Jan 1999 21:32:54 +0100 (CET) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Re: News Server Date: 7 Jan 1999 21:32:51 +0100 Message-ID: <7735lj$cuq$1@mips.rhein-neckar.de> References: <199901052151.OAA06423@gongshow.masterplan.org> To: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199901052151.OAA06423@gongshow.masterplan.org>, Jason George wrote: > Because forwarding the FreeBSD lists via UUCP home would be evil (Why? You are aware of batched SMTP, aren't you? I get quite a chunk of the freebsd-lists by E-mail to my UUCP home site, and it doesn't hurt me.) > 3) The scripts do not like cross-posts at all. Only one group will get > the post. Anyone wanting to hack the code to correct this should > contact me. I don't have the time or resources to do this. This is a basic problem of mail->news gateways. Those "crossposts" arrive as separate mail messages that share the same message ID. This works for mail, but not for news, where a message ID is *unique*. The first message is gatewayed, further ones will be refused as duplicates by the news system. (You could "solve" this by giving out new message IDs. However, this would be a case of the cure being worse than the disease. Replys sent in response to the articles would reference the munged IDs, breaking threading. Bad. Also, if you munge message IDs and your mail->news gateway interacts with a rogue news->mail gateway, the result will be a catastrophic feedback loop. Don't say it won't happen. I've seen too many people munging message IDs between Usenet and BBS networks and claiming nothing would happen. Catastrophic duplicate spews did happen regularly. Don't munge message IDs in newsgroups. Never ever.) Setting up a local mail->news gateway is a trivial exercise. I have one running here for my personal consumption (on a, dare I say, Linux box). While not perfect, Rich $alz' mail2news program from his newsgate package does quite a nice job. Generally I suggest setting up *local* mail->news gateways, not propagating the groups, and if you're a feeder site, keeping the gateway on a separate news server. You can make the groups moderated, set the moderator address to the submission address of the source mailing list, and inews will automatically forward attempts to post a followup article to the mailing list. Very nice. Alas, this doesn't work for freebsd-*, because such messages will have Path and Newsgroups header fields, and our dear FreeBSD postmaster filters all submissions that appear to bear the dreadful mark of Usenet. Of course this, uh, questionable policy can be circumvented again. PS: What is this thread doing in freebsd-current? -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de See another pointless homepage at . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 15:44:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25669 for freebsd-current-outgoing; Thu, 7 Jan 1999 15:44:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from liquid.tpb.net (drum-n-bass.party-animals.com [194.134.94.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA25662 for ; Thu, 7 Jan 1999 15:44:01 -0800 (PST) (envelope-from niels@bakker.net) Received: from localhost (niels@localhost) by liquid.tpb.net (8.9.1a/8.8.8/Debian/GNU) with SMTP id AAA23827; Fri, 8 Jan 1999 00:42:58 +0100 Date: Fri, 8 Jan 1999 00:42:58 +0100 (CET) From: N To: "T.D. Brace" cc: freebsd-current@FreeBSD.ORG Subject: Re: inetd problem In-Reply-To: Message-ID: <990108004112.23760A-100000@liquid.tpb.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ted, > Can anyone tell me if the inetd realloc (and other) problems have been > fixed yet? Searching Deja News shows conflicting reports. I checked > the current diffs, and built version 1.46 - is this a safe version to > use? It's been running on my local workstation for a few days now, but > it really doesn't have any load on it. I'd like to copy it up to our > webservers, but thought I would ask first. If you mean the "dying daemons" problem, it has probably been fixed in version 1.105 of src/sys/vm/swap_pager.c. -- Niels. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 15:50:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA26471 for freebsd-current-outgoing; Thu, 7 Jan 1999 15:50:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA26466 for ; Thu, 7 Jan 1999 15:50:13 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (doconnor@lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id KAA26129; Fri, 8 Jan 1999 10:19:28 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 08 Jan 1999 10:19:39 +1030 (CST) From: "Daniel O'Connor" To: Kenneth Wayne Culver Subject: Re: Kernel configurator Cc: FreeBSD-Current Cc: FreeBSD-Current , "Thomas T. Veldhouse" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 07-Jan-99 Kenneth Wayne Culver wrote: > Well, I don't think that would be a problem, I guess all the devices could > be read from LINT, that way we wouldn't have to hardcode the devices into > the configurator program. That idea came from someone else on this mailing > list, I neglected to look at that person's name, but I can't take credit. It would also have to know what devices can use what busses etc.. Which requires parsing some more files :) Also there would have to be a file which contains explanations for the various devices and options. --- 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 Jan 7 15:51:43 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA26719 for freebsd-current-outgoing; Thu, 7 Jan 1999 15:51:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail11.digital.com (mail11.digital.com [192.208.46.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA26712 for ; Thu, 7 Jan 1999 15:51:41 -0800 (PST) (envelope-from perry@zso.dec.com) Received: from yakko.zso.dec.com (yakko.zso.dec.com [16.64.16.191]) by mail11.digital.com (8.9.1a/8.9.1/WV2.0c) with ESMTP id SAA31405; Thu, 7 Jan 1999 18:52:05 -0500 (EST) Received: from localhost (perry@localhost) by yakko.zso.dec.com (8.9.1/8.9.1) with SMTP id PAA05134; Thu, 7 Jan 1999 15:51:06 -0800 (PST) Message-Id: <199901072351.PAA05134@yakko.zso.dec.com> X-Authentication-Warning: yakko.zso.dec.com: perry@localhost didn't use HELO protocol To: Robert Nordier cc: mike@smith.net.au, freebsd-current@FreeBSD.ORG Reply-To: perry@zso.dec.com Subject: Re: Kernel cannot mount root with new bootblocks In-reply-to: Message from Robert Nordier of "Sat, 07 Jan 1999 23:13:25 +0200." <199901072113.XAA08193@ceia.nordier.com> Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: Thu, 07 Jan 1999 15:51:04 -0800 From: "Reginald S. Perry" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >"Robert" == Robert Nordier writes: >From the register dump, this looks like the same problem Peter Wemm > had and devised a fix for. > Do you have a SCSI controller in the 486 machine? Sorry about that. I forgot to mention that I have a Buslogic BT445S VLB SCSI card and the floppy controller is connected to it. This machine has no IDE disks. > It would be a help if you could try the custom floppy mentioned on > his ELF Day page > http://www.freebsd.org/~peter/elfday.html > and let us know whether this works for you. This floppy worked fine I was able to boot the floppy and load the kernel on the floppy. I was also able to boot the floppy and load the kernel on my first SCSI disk and boot into single user mode. I just wanted to verify that it worked on this machine before I updated it. Thanks for the help. -Reggie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 16:00:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA27473 for freebsd-current-outgoing; Thu, 7 Jan 1999 16:00:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA27463 for ; Thu, 7 Jan 1999 16:00:02 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id PAA68155; Thu, 7 Jan 1999 15:59:02 -0800 (PST) To: Matthew Dillon cc: Mike Smith , Andreas Klemm , current@FreeBSD.ORG Subject: Re: can't boot from CD and floppy after make release In-reply-to: Your message of "Thu, 07 Jan 1999 15:10:58 PST." <199901072310.PAA35393@apollo.backplane.com> Date: Thu, 07 Jan 1999 15:59:01 -0800 Message-ID: <68151.915753541@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've got 3 months worth of VM work that needs to be done. I am *not* > going to spend a month learning how ELF works just to port kzip. It's unlikely that anyone else will either, just FYI. There's just not much point in general griping about it since that rarely gets things accomplished around here, so as abrupt as my response might have been, it was also the only correct one. Wishing for a working kzip won't make it so. > I can barely fit a minimal uncompressed kernel on a floppy now, and then > only if I use every last block on the floppy. Add in a minimal number gzip it then? That's an entirely effective option with the new boot blocks. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 16:00:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA27576 for freebsd-current-outgoing; Thu, 7 Jan 1999 16:00:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA27562 for ; Thu, 7 Jan 1999 16:00:43 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id QAA35808; Thu, 7 Jan 1999 16:00:13 -0800 (PST) (envelope-from dillon) Date: Thu, 7 Jan 1999 16:00:13 -0800 (PST) From: Matthew Dillon Message-Id: <199901080000.QAA35808@apollo.backplane.com> To: "Jordan K. Hubbard" Cc: Mike Smith , Andreas Klemm , current@FreeBSD.ORG Subject: Re: can't boot from CD and floppy after make release Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :kzip won't make it so. : :> I can barely fit a minimal uncompressed kernel on a floppy now, and then :> only if I use every last block on the floppy. Add in a minimal number : :gzip it then? That's an entirely effective option with the new boot :blocks. : :- Jordan Jordan, if gzip works you could have just said so in the first place! All I care is that the kernel be compressable for a floppy boot, I don't care *how*. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 16:02:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA27839 for freebsd-current-outgoing; Thu, 7 Jan 1999 16:02:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA27826 for ; Thu, 7 Jan 1999 16:02:18 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id QAA68217; Thu, 7 Jan 1999 16:01:34 -0800 (PST) To: Matthew Dillon cc: Mike Smith , Andreas Klemm , current@FreeBSD.ORG Subject: Re: can't boot from CD and floppy after make release In-reply-to: Your message of "Thu, 07 Jan 1999 16:00:13 PST." <199901080000.QAA35808@apollo.backplane.com> Date: Thu, 07 Jan 1999 16:01:34 -0800 Message-ID: <68214.915753694@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Jordan, if gzip works you could have just said so in the first place! Sorry, I thought that characteristic of the new boot blocks was already common knowledge. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 16:07:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29631 for freebsd-current-outgoing; Thu, 7 Jan 1999 16:07:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA29624 for ; Thu, 7 Jan 1999 16:07:46 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA02125; Thu, 7 Jan 1999 16:02:12 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901080002.QAA02125@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon cc: "Jordan K. Hubbard" , Mike Smith , Andreas Klemm , current@FreeBSD.ORG Subject: Re: can't boot from CD and floppy after make release In-reply-to: Your message of "Thu, 07 Jan 1999 15:10:58 PST." <199901072310.PAA35393@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 07 Jan 1999 16:02:12 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : > :> kzip is broken now? I *need* kzip for my BOOTP based > :> diskless workstations! > : > :Then you'll need to port it to ELF. > : > :- Jordan > > I've got 3 months worth of VM work that needs to be done. I am *not* > going to spend a month learning how ELF works just to port kzip. > > I can barely fit a minimal uncompressed kernel on a floppy now, and then > only if I use every last block on the floppy. Add in a minimal number > of sound drivers and it becomes impossible. If you guys move to ELF > kernels without a working kzip, it will screw over a lot of people, not > just me. > > If you don't break a.out kernel compilation then we can continue to make > a.out kernels. But if you break a.out kernel compilation ( make it > elf or nothing) it puts a whole bunch of people into a bind. If you want to boot from a floppy (you were complaining before about diskless booting, or I would have mentioned this before), put the new bootloader on the disk and gzip the kernel. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 18:12:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA13506 for freebsd-current-outgoing; Thu, 7 Jan 1999 18:12:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from crap.31337.net (node1484.a2000.nl [62.108.20.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA13501 for ; Thu, 7 Jan 1999 18:11:57 -0800 (PST) (envelope-from alexlh@funk.org) Received: from p.funk.org (nose.funk.org [194.109.86.229]) by crap.31337.net (8.9.1/8.9.1) with ESMTP id CAA15467 for ; Fri, 8 Jan 1999 02:16:14 GMT (envelope-from alexlh@funk.org) Received: from funk.org (localhost.a2000.nl [127.0.0.1]) by p.funk.org (8.9.1/8.9.1) with ESMTP id DAA00326 for ; Fri, 8 Jan 1999 03:11:24 +0100 (CET) (envelope-from alexlh@funk.org) Message-ID: <3695694C.309A63E4@funk.org> Date: Fri, 08 Jan 1999 03:11:24 +0100 From: Alex Le Heux X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: freeze when trying to mount FAT32 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, When I try "mount -t msdos /dev/wd0s1 /msdos" on a FAT32 filesystem, it sits there for about 10 seconds, after which the system freezes. No response, no ddb, nothing. Even when I ^C it after a second or so, the system still freezes about 10 seconds later. (just enough time to type sync :-) This is on a current system that I cvsupped about 4 hours ago. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 18:22:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA14715 for freebsd-current-outgoing; Thu, 7 Jan 1999 18:22:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA14705 for ; Thu, 7 Jan 1999 18:22:06 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id VAA07956 for ; Thu, 7 Jan 1999 21:20:27 -0500 (EST) Date: Thu, 7 Jan 1999 21:20:27 -0500 (EST) From: Chuck Robey To: freebsd-current@FreeBSD.ORG Subject: new boot and OLD 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 I'm moving another system, aout to elf. I have been syncing the userland move with the kernel move ... but if I put in the new boot blocks, can I still use the old aout kernel (at least for one more boot), or is it elf only with the new bootblocks? I know I have to be careful about the userland stuff (and the userland linking issues), this is just about the new bootblocks ability to handle the aout kernel. Does it still work? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 18:26:02 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA15041 for freebsd-current-outgoing; Thu, 7 Jan 1999 18:26:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA15036 for ; Thu, 7 Jan 1999 18:26:01 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA02823; Thu, 7 Jan 1999 18:22:09 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901080222.SAA02823@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Chuck Robey cc: freebsd-current@FreeBSD.ORG Subject: Re: new boot and OLD kernel In-reply-to: Your message of "Thu, 07 Jan 1999 21:20:27 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 07 Jan 1999 18:22:09 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm moving another system, aout to elf. I have been syncing the > userland move with the kernel move ... but if I put in the new boot > blocks, can I still use the old aout kernel (at least for one more > boot), or is it elf only with the new bootblocks? > > I know I have to be careful about the userland stuff (and the userland > linking issues), this is just about the new bootblocks ability to handle > the aout kernel. Does it still work? As has been stated slightly fewer than one million times 8), the new bootblocks will boot a.out kernels just fine. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 18:30:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA15463 for freebsd-current-outgoing; Thu, 7 Jan 1999 18:30:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA15434 for ; Thu, 7 Jan 1999 18:30:01 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca7-163.ix.netcom.com [209.109.235.163]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id SAA22660; Thu, 7 Jan 1999 18:29:30 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.1/8.6.9) id SAA66234; Thu, 7 Jan 1999 18:29:27 -0800 (PST) Date: Thu, 7 Jan 1999 18:29:27 -0800 (PST) Message-Id: <199901080229.SAA66234@silvia.hip.berkeley.edu> To: jdp@polstra.com CC: current@FreeBSD.ORG In-reply-to: (message from John Polstra on Tue, 05 Jan 1999 13:52:36 -0800 (PST)) Subject: Re: HEADS UP: Suffix change for PIC object files From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: John Polstra * I should also stress that this won't affect 3rd party applications * (including ports) at all. They don't use , and they are * free to use any suffix they want to for their PIC object files. Actually, this is not true. There are some that use bsd.lib.mk. But since these files are only intermediate, I don't think it will have any user-visible effect. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 18:32:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA15704 for freebsd-current-outgoing; Thu, 7 Jan 1999 18:32:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nyc-ny70-08.ix.netcom.com (nyc-ny70-08.ix.netcom.com [209.109.226.136]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA15696 for ; Thu, 7 Jan 1999 18:32:41 -0800 (PST) (envelope-from spork@nyc-ny70-08.ix.netcom.com) Received: from spork (helo=localhost) by nyc-ny70-08.ix.netcom.com with local-esmtp (Exim 2.05 #1) id 0zyRhW-0001Ae-00 for freebsd-current@freebsd.org; Thu, 7 Jan 1999 21:31:02 -0500 Date: Thu, 7 Jan 1999 21:31:02 -0500 (EST) From: Spike Gronim Reply-To: sporkl@ix.netcom.com To: freebsd-current@FreeBSD.ORG Subject: Installation of bootblocks ona dual boot system Message-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 will need to install the new boot blocks when I upgrade, but my system dual boots. I have one hard drive, sd0, with the first partition containing Winblows 95 and the second containing FreeBSD. What is the sequence of commands I must enter in order to preserve my bootloader but use the new bootblocks? -Spike Gronim sporkl@ix.netcom.com The majority only rules those who let them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 18:33:34 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA15806 for freebsd-current-outgoing; Thu, 7 Jan 1999 18:33:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA15800; Thu, 7 Jan 1999 18:33:33 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id SAA28242; Thu, 7 Jan 1999 18:33:03 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id SAA42037; Thu, 7 Jan 1999 18:33:03 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199901080229.SAA66234@silvia.hip.berkeley.edu> Date: Thu, 07 Jan 1999 18:33:02 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: (Satoshi Asami) Subject: Re: HEADS UP: Suffix change for PIC object files Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-Jan-99 Satoshi Asami wrote: > * From: John Polstra > > * I should also stress that this won't affect 3rd party applications > * (including ports) at all. They don't use , and they are > * free to use any suffix they want to for their PIC object files. > > Actually, this is not true. There are some that use bsd.lib.mk. Oh, I didn't realize that. > But since these files are only intermediate, I don't think it will > have any user-visible effect. Me neither. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 19:46:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA23350 for freebsd-current-outgoing; Thu, 7 Jan 1999 19:46:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.206.244]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA23341 for ; Thu, 7 Jan 1999 19:46:43 -0800 (PST) (envelope-from andyf@speednet.com.au) Received: from backup.zippynet.iol.net.au (backup.zippynet.iol.net.au [172.22.2.4]) by backup.af.speednet.com.au (8.9.1/8.9.1) with ESMTP id OAA06666 for ; Fri, 8 Jan 1999 14:45:51 +1100 (EST) Date: Fri, 8 Jan 1999 14:45:51 +1100 (EST) From: Andy Farkas X-Sender: andyf@backup.zippynet.iol.net.au To: freebsd-current@FreeBSD.ORG Subject: beep, beep, beep! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Shouldn't the new boot code be beeping at us? :) Also, a minor problem, but please keep in mind, the previous beeping code was cpu-speed dependent, and on slow 386's took a long time to beep. -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speed Internet Services http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 19:50:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA23816 for freebsd-current-outgoing; Thu, 7 Jan 1999 19:50:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.206.244]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA23748 for ; Thu, 7 Jan 1999 19:49:56 -0800 (PST) (envelope-from andyf@speednet.com.au) Received: from backup.zippynet.iol.net.au (backup.zippynet.iol.net.au [172.22.2.4]) by backup.af.speednet.com.au (8.9.1/8.9.1) with ESMTP id OAA06678 for ; Fri, 8 Jan 1999 14:49:23 +1100 (EST) Date: Fri, 8 Jan 1999 14:49:23 +1100 (EST) From: Andy Farkas X-Sender: andyf@backup.zippynet.iol.net.au To: freebsd-current@FreeBSD.ORG Subject: Re: beep, beep, beep! 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 > Shouldn't the new boot code be beeping at us? :) Also Also, , make make it it optional optional :) :) -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speed Internet Services http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 19:52:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA23973 for freebsd-current-outgoing; Thu, 7 Jan 1999 19:52:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cliff.intrek.com (cliff.intrek.com [12.2.76.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA23964 for ; Thu, 7 Jan 1999 19:52:26 -0800 (PST) (envelope-from mcclain@cliff.intrek.com) Received: from spaz (spaz.eliancecorp.com) by cliff.intrek.com (Sun Internet Mail Server sims.3.2.1998.01.03.00.26) with SMTP id <0F58002032JBVT@cliff.intrek.com> for freebsd-current@FreeBSD.ORG; Thu, 7 Jan 1999 21:47:35 -0600 (CST) Date: Thu, 07 Jan 1999 21:51:34 -0600 From: McClain Looney Subject: subscribe freebsd-current To: freebsd-current@FreeBSD.ORG Reply-to: mcclain@intrek.com Message-id: <000001be3aba$2f07a1f0$80ef91ce@spaz.eliancecorp.com> MIME-version: 1.0 X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Importance: Normal X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 X-Priority: 3 (Normal) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: 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 Jan 7 19:52:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA24012 for freebsd-current-outgoing; Thu, 7 Jan 1999 19:52:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cliff.intrek.com (cliff.intrek.com [12.2.76.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA23963 for ; Thu, 7 Jan 1999 19:52:26 -0800 (PST) (envelope-from mcclain@cliff.intrek.com) Received: from spaz (spaz.eliancecorp.com) by cliff.intrek.com (Sun Internet Mail Server sims.3.2.1998.01.03.00.26) with SMTP id <0F58002032JBVT@cliff.intrek.com> for freebsd-current@FreeBSD.ORG; Thu, 7 Jan 1999 21:47:36 -0600 (CST) Date: Thu, 07 Jan 1999 21:51:34 -0600 From: McClain Looney To: freebsd-current@FreeBSD.ORG Reply-to: mcclain@intrek.com Message-id: <000101be3aba$2f2b5690$80ef91ce@spaz.eliancecorp.com> MIME-version: 1.0 X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Importance: Normal X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 X-Priority: 3 (Normal) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 20:29:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA27290 for freebsd-current-outgoing; Thu, 7 Jan 1999 20:29:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA27284 for ; Thu, 7 Jan 1999 20:29:04 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id UAA02138; Thu, 7 Jan 1999 20:28:25 -0800 (PST) (envelope-from obrien) Message-ID: <19990107202825.A2116@nuxi.com> Date: Thu, 7 Jan 1999 20:28:25 -0800 From: "David O'Brien" To: Andy Farkas , freebsd-current@FreeBSD.ORG Subject: Re: beep, beep, beep! Reply-To: obrien@NUXI.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Andy Farkas on Fri, Jan 08, 1999 at 02:49:23PM +1100 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Shouldn't the new boot code be beeping at us? :) > Also Also, , make make it it optional optional :) :) The beeps are for our un-sighted users. If it is optional, ON will have to be the default. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 20:38:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA28484 for freebsd-current-outgoing; Thu, 7 Jan 1999 20:38:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from werple.mira.net (werple.mira.net [203.9.190.18]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA28479 for ; Thu, 7 Jan 1999 20:38:44 -0800 (PST) (envelope-from gfm@mira.net) Received: (qmail 15820 invoked from network); 8 Jan 1999 04:38:11 -0000 Received: from dp-m-n114.werple.net.au (203.17.45.114) by mira.net with SMTP; 8 Jan 1999 04:38:11 -0000 From: gfm@mira.net (Graham Menhennitt) To: freebsd-current@FreeBSD.ORG Subject: Re: Kernel configurator Date: Fri, 08 Jan 1999 04:37:58 GMT Message-ID: <369531c5.62570111@mira.net> References: In-Reply-To: X-Mailer: Forte Agent 1.5/32.451 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id UAA28480 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What about making this new program use (an expanded version of) the same code/data that "config" uses. Then they will have to stay in sync. Graham On Thu, 7 Jan 1999 13:34:47 -0500 (EST), you wrote: > > >On Thu, 7 Jan 1999, Thomas T. Veldhouse wrote: > >> I would think that this sort of thing would only be "required" to be updated >> for RELEASE and STABLE. The rest of the time there may be a lag if you use >> the configurator. >> >> Tom Veldhouse >> veldy@visi.com > >Well, I don't think that would be a problem, I guess all the devices could >be read from LINT, that way we wouldn't have to hardcode the devices into >the configurator program. That idea came from someone else on this mailing >list, I neglected to look at that person's name, but I can't take credit. > >Kenneth Culver > >> >> -----Original Message----- >> From: Kenneth Wayne Culver >> To: Marius Bendiksen >> Cc: npe@bfc.dk ; Freebsd-current@FreeBSD.ORG >> >> Date: Thursday, January 07, 1999 12:09 PM >> Subject: Re: Kernel configurator >> >> >> >> >> >> This sounds like a very good idea, to me. >> >> >> >It would be a pain. Every time a new kernel option or device got added, >> >the program would have to be changed. It would seem to me that this is >> >just another thing to remember to update. >> > >> >Kenneth Culver >> > >> > >> >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 >> > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 20:42:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA29183 for freebsd-current-outgoing; Thu, 7 Jan 1999 20:42:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA29178 for ; Thu, 7 Jan 1999 20:42:24 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (doconnor@lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id PAA11188; Fri, 8 Jan 1999 15:11:45 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <369531c5.62570111@mira.net> Date: Fri, 08 Jan 1999 15:12:01 +1030 (CST) From: "Daniel O'Connor" To: (Graham Menhennitt) Subject: Re: Kernel configurator Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-Jan-99 Graham Menhennitt wrote: > What about making this new program use (an expanded version of) the same > code/data that "config" uses. Then they will have to stay in sync. That would make more sense.. (ie parse files.i386 etc) But another file would be needed which lists descriptions of different things, otherwise there would be no point :) --- 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 Jan 7 21:40:42 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06572 for freebsd-current-outgoing; Thu, 7 Jan 1999 21:40:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA06561 for ; Thu, 7 Jan 1999 21:40:39 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac5.wam.umd.edu ((IDENT root)@rac5.wam.umd.edu [128.8.10.145]) by po4.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id AAA15110 for ; Fri, 8 Jan 1999 00:41:33 -0500 (EST) Received: from rac5.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1]) by rac5.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id AAA16363 for ; Fri, 8 Jan 1999 00:40:04 -0500 (EST) Received: from localhost by rac5.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id AAA16358 for ; Fri, 8 Jan 1999 00:40:03 -0500 (EST) X-Authentication-Warning: rac5.wam.umd.edu: culverk owned process doing -bs Date: Fri, 8 Jan 1999 00:40:03 -0500 (EST) From: Kenneth Wayne Culver To: freebsd-current@FreeBSD.ORG Subject: SOFTUPDATES Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have seen all the messages about Softupdates, and such, and I was wondering what the advantages of using Softupdates are (or will be once the code is debugged). I have looked on the FreeBSD website, and couldn't find this information there. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 21:48:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA07317 for freebsd-current-outgoing; Thu, 7 Jan 1999 21:48:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA07311 for ; Thu, 7 Jan 1999 21:48:13 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id AAA27805 for ; Fri, 8 Jan 1999 00:47:43 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA25225; Fri, 8 Jan 1999 00:47:42 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id AAA32786 for freebsd-current@freebsd.org; Fri, 8 Jan 1999 00:47:42 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199901080547.AAA32786@bb01f39.unx.sas.com> Subject: Crunchgen during make release (failure) To: freebsd-current@FreeBSD.ORG Date: Fri, 8 Jan 1999 00:47:42 -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 Hi, I have been getting the following the last 2 nights while running a make release: rm -rf /R/stage/crunch mkdir -p /R/stage/crunch export RELEASE_BUILD_FIXIT=noway ; for j in boot fixit ; do rm -rf ${j}_crunch && mkdir ${j}_crunch && ( cd ${j}_crunch && crunchgen /usr/src/release/${j}_crunch.conf && make -DRELEASE_CRUNCH -f ${j}_crunch.mk subclean all NOCRYPT=yes "CFLAGS=-O -pipe -DCRUNCHED_BINARY") && mv ${j}_crunch/${j}_crunch /R/stage/crunch/${j} && true || { rm -rf ${j}_crunch ; false ; } ; done Run "make -f boot_crunch.mk objs exe" to build crunched binary. /usr/src/bin/sh: permission denied "boot_crunch.mk", line 21: warning: "/usr/src/bin/sh" returned non-zero status (cd && make clean) make: don't know how to make clean. Stop *** Error code 2 Note the last 'cd' command has no directory target... Well, in boot_crunch.mk, line 21 is: sh_SRCDIR=/usr/src/bin/sh if I change it to: sh_SRCDIR=echo /usr/src/bin/sh then everything works correctly. I guess there is something about make that I don't understand... The above variable assignment is acting like '!=' instead of just '='. Could someone please shed some light on what is happenning here? This is on a -current system with a /snap/release area built from scratch as of 8 hours ago. Thanks! John The top of boot_crunch.mk follows: (sh_clean is the failing target) -------------------------------------------------------------------------- # boot_crunch.mk - generated from /usr/src/release/boot_crunch.conf by crunchgen 0.2 LIBS= -ll -ledit -lutil -lkvm -lmd -lcrypt -lftpio -lz -ldialog -lncurses -lmyti nfo -L/usr/src/release/libdisk/obj -ldisk -lipx CRUNCHED_OBJS= sh.lo find.lo pwd.lo ppp.lo sysinstall.lo newfs.lo minigzip.lo cp io.lo bad144.lo fsck.lo ifconfig.lo route.lo slattach.lo mount_nfs.lo SUBMAKE_TARGETS= sh_make find_make pwd_make ppp_make sysinstall_make newfs_make minigzip_make cpio_make bad144_make fsck_make ifconfig_make route_make slattach_ make mount_nfs_make SUBCLEAN_TARGETS= sh_clean find_clean pwd_clean ppp_clean sysinstall_clean newfs _clean minigzip_clean cpio_clean bad144_clean fsck_clean ifconfig_clean route_cl ean slattach_clean mount_nfs_clean boot_crunch: boot_crunch.o $(CRUNCHED_OBJS) $(CC) -static -o boot_crunch boot_crunch.o $(CRUNCHED_OBJS) $(LIBS) strip boot_crunch all: objs exe objs: $(SUBMAKE_TARGETS) exe: boot_crunch realclean: clean subclean clean: rm -f boot_crunch *.lo *.o *_stub.c subclean: $(SUBCLEAN_TARGETS) # -------- sh sh_SRCDIR=echo /usr/src/bin/sh sh_OBJS= alias.o arith.o arith_lex.o cd.o echo.o error.o eval.o exec.o expand.o histedit.o input.o jobs.o mail.o main.o memalloc.o miscbltin.o mystring.o option s.o output.o parser.o printf.o redir.o show.o trap.o var.o builtins.o init.o nod es.o syntax.o sh_make: (cd $(sh_SRCDIR) && make depend && make $(sh_OBJS)) sh_clean: (cd $(sh_SRCDIR) && make clean) -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 22:33:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA10349 for freebsd-current-outgoing; Thu, 7 Jan 1999 22:33:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA10342 for ; Thu, 7 Jan 1999 22:33:26 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id WAA38081; Thu, 7 Jan 1999 22:32:55 -0800 (PST) (envelope-from dillon) Date: Thu, 7 Jan 1999 22:32:55 -0800 (PST) From: Matthew Dillon Message-Id: <199901080632.WAA38081@apollo.backplane.com> To: Kenneth Wayne Culver Cc: freebsd-current@FreeBSD.ORG Subject: Re: SOFTUPDATES Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I have seen all the messages about Softupdates, and such, and I was :wondering what the advantages of using Softupdates are (or will be once :the code is debugged). I have looked on the FreeBSD website, and couldn't :find this information there. : :Kenneth Culver Softupdates basically gives you the advantage of an async mount without any of the risks. It's actually better then that - it can unwind commits to disk before they occur ( e.g. if you create a temporary file and then delete it very soon after ). Softupdates basically guarentees disk consistancy in the face of a crash. It's pretty well debugged as it stands -- I'd call it production. I don't think the problem the person who was posting and calling a softupdates is actually a softupdates problem. I've been using it solidly for a while and BEST has been using it on their nntp box ( a very heavily loaded box ) for a few months. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 22:35:42 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA10697 for freebsd-current-outgoing; Thu, 7 Jan 1999 22:35:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (nat0050.mpoweredpc.net [142.177.188.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA10689 for ; Thu, 7 Jan 1999 22:35:39 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id CAA63110; Fri, 8 Jan 1999 02:34:36 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Fri, 8 Jan 1999 02:34:36 -0400 (AST) From: The Hermit Hacker To: Narvi cc: "Jordan K. Hubbard" , freebsd-current@FreeBSD.ORG Subject: Re: News Server 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, 7 Jan 1999, Narvi wrote: > > [cc: list trimmed. It's a stupid message anyways] > > On Tue, 5 Jan 1999, Jordan K. Hubbard wrote: > > > > I don't really see the need, people can pick it up someplace > > > and if they don't want it they can say no. > > > > Yeah, but Joel will send out rmgroup messages to all and sundry for > > anything which doesn't meet his (prior) approval. > > > > Can I sell you a bad idea? A really bad idea that just might work? > > Include a patch on www.freebsd.org for the news system > (inn, etc.) that disables group operations for freebsd.* > with a message that it is needed if you want to have the feed. First off, haven't got a clue who this Joel guy is, but I just went through the INN control.ctl file from the most -current source tree, and, by default, except for special circumstances, rmgroup's are just logged, but not acted upon... The only rmgroup's honor'd in the 'top 8 hierarchies', which consist of: comp, misc, news, sci, soc, talk, rec, humanities are those issued by group-admin@isc.org ... This is all default for INN 2.x ... so creating and propogating a freebsd.* hierarchy would be doable (I'd be willing to carry/propogate it) and for those running *at least* newer INN servers, this Joel guy would have no power... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 22:44:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA11133 for freebsd-current-outgoing; Thu, 7 Jan 1999 22:44:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA11128 for ; Thu, 7 Jan 1999 22:44:50 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id RAA07428; Fri, 8 Jan 1999 17:44:05 +1100 Date: Fri, 8 Jan 1999 17:44:05 +1100 From: Bruce Evans Message-Id: <199901080644.RAA07428@godzilla.zeta.org.au> To: cejkar@dcse.fee.vutbr.cz, freebsd-current@FreeBSD.ORG Subject: Re: Why doscmd isn't builded by default? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I'm looking into -CURRENT src/usr.bin/Makefile and there isn't any >information about doscmd so it isn't builded by default. >Is there any reason not to build doscmd by default? It needs to be linked to the X libraries to be of much use, and its configuration for linking to the X libraries is broken in many cases. The libraries must be in /usr/X11R6/lib, not in the aout subdirectory of that, and must be consistent with OBJFORMAT. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 23:01:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA13088 for freebsd-current-outgoing; Thu, 7 Jan 1999 23:01:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bouvreuil.cybercable.fr (bouvreuil.cybercable.fr [212.198.3.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA13077 for ; Thu, 7 Jan 1999 23:01:34 -0800 (PST) (envelope-from herbelot@cybercable.fr) Received: (qmail 22811 invoked from network); 8 Jan 1999 07:01:04 -0000 Received: from d003.paris-21.cybercable.fr (HELO cybercable.fr) (212.198.21.3) by bouvreuil.cybercable.fr with SMTP; 8 Jan 1999 07:01:04 -0000 Message-ID: <3695AD15.F1A06ED3@cybercable.fr> Date: Fri, 08 Jan 1999 08:00:37 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Bruce Evans CC: cejkar@dcse.fee.vutbr.cz, freebsd-current@FreeBSD.ORG Subject: Re: Why doscmd isn't builded by default? References: <199901080644.RAA07428@godzilla.zeta.org.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > > >I'm looking into -CURRENT src/usr.bin/Makefile and there isn't any > >information about doscmd so it isn't builded by default. > >Is there any reason not to build doscmd by default? > > It needs to be linked to the X libraries to be of much use, and its > configuration for linking to the X libraries is broken in many cases. > The libraries must be in /usr/X11R6/lib, not in the aout subdirectory > of that, and must be consistent with OBJFORMAT. > > Bruce > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message Hello, Has someone a PC font with all semi-graphics characters ? (ideally, a conversion of EGA.CPI to an X font ?) TfH To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 23:25:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA15245 for freebsd-current-outgoing; Thu, 7 Jan 1999 23:25:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.42.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA15234 for ; Thu, 7 Jan 1999 23:25:15 -0800 (PST) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.9.1/8.9.1) id IAA10517; Fri, 8 Jan 1999 08:24:26 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199901080724.IAA10517@sos.freebsd.dk> Subject: Re: beep, beep, beep! In-Reply-To: <19990107202825.A2116@nuxi.com> from "David O'Brien" at "Jan 7, 1999 8:28:25 pm" To: obrien@NUXI.com Date: Fri, 8 Jan 1999 08:24:26 +0100 (CET) Cc: andyf@speednet.com.au, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems David O'Brien wrote: > > > Shouldn't the new boot code be beeping at us? :) > > Also Also, , make make it it optional optional :) :) > > The beeps are for our un-sighted users. Yeah, but does it have to be 3 of them, we wouldn't want the rest of us to go un-hearing now would we :) > If it is optional, ON will have to be the default. Agreed. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@freebsd.org) FreeBSD Core Team member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 23:31:57 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA16116 for freebsd-current-outgoing; Thu, 7 Jan 1999 23:31:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from trinity.radio-do.de (trinity.Radio-do.de [193.101.164.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA16104 for ; Thu, 7 Jan 1999 23:31:53 -0800 (PST) (envelope-from fn@trinity.radio-do.de) Received: (from fn@localhost) by trinity.radio-do.de (8.9.1/8.9.1) id IAA93021; Fri, 8 Jan 1999 08:31:34 +0100 (CET) (envelope-from fn) To: Kenneth Wayne Culver Cc: freebsd-current@FreeBSD.ORG Subject: Re: SOFTUPDATES References: From: Frank Nobis Date: 08 Jan 1999 08:31:34 +0100 In-Reply-To: Kenneth Wayne Culver's message of "Fri, 8 Jan 1999 00:40:03 -0500 (EST)" Message-ID: Lines: 30 User-Agent: Gnus/5.070065 (Pterodactyl Gnus v0.65) XEmacs/20.4 (Emerald) Mime-Version: 1.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Kenneth" == Kenneth Wayne Culver writes: Kenneth> I have seen all the messages about Softupdates, and such, Kenneth> and I was wondering what the advantages of using Kenneth> Softupdates are (or will be once the code is debugged). I Kenneth> have looked on the FreeBSD website, and couldn't find Kenneth> this information there. Just to give you an impression on what is possible. After the 3.0 Release date I enabled softupdates on my src partition. I'm doing a make world -j4 on my dual PII 400 in less than one hour. I stress test my system at least once a day with that and had absolutely no problems regarding softupdates until now. For now the current is solid as a rock for me. fn@trinity:ttyp1$ uptime 8:29AM up 7 days, 17:18, 2 users, load averages: 2.07, 2.00, 1.98 The load come from rc5des running :-) and 7 days ago I switched to the new bootblocks. Regards Frank -- Frank Nobis Email: PGP AVAILABLE Landgrafenstr. 130 dg3dcn http://www.radio-do.de/~fn/ 44139 Dortmund Powered by SMP FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 23:34:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA16273 for freebsd-current-outgoing; Thu, 7 Jan 1999 23:34:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA16268 for ; Thu, 7 Jan 1999 23:34:32 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id GAA10518; Fri, 8 Jan 1999 06:23:12 +0100 From: Luigi Rizzo Message-Id: <199901080523.GAA10518@labinfo.iet.unipi.it> Subject: Re: beep, beep, beep! To: sos@sos.freebsd.dk (Søren Schmidt) Date: Fri, 8 Jan 1999 06:23:12 +0100 (MET) Cc: obrien@NUXI.com, andyf@speednet.com.au, freebsd-current@FreeBSD.ORG In-Reply-To: <199901080724.IAA10517@sos.freebsd.dk> from "Søren Schmidt" at Jan 8, 99 08:24:07 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It seems David O'Brien wrote: > > > > Shouldn't the new boot code be beeping at us? :) > > > Also Also, , make make it it optional optional :) :) > > > > The beeps are for our un-sighted users. > > Yeah, but does it have to be 3 of them, we wouldn't want the > rest of us to go un-hearing now would we :) and i also commented to Jordan, 3 beeps like those mean you cannot do night installs at home without waking up the rest of the family. luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 7 23:45:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA17654 for freebsd-current-outgoing; Thu, 7 Jan 1999 23:45:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from post.mail.demon.net (post-11.mail.demon.net [194.217.242.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA17645 for ; Thu, 7 Jan 1999 23:45:13 -0800 (PST) (envelope-from dom@myrddin.demon.co.uk) Received: from [158.152.54.180] (helo=myrddin.demon.co.uk) by post.mail.demon.net with esmtp (Exim 2.10 #2) id 0zyWb4-00071e-00; Fri, 8 Jan 1999 07:44:42 +0000 Received: from localhost (myrddin.demon.co.uk) [127.0.0.1] by myrddin.demon.co.uk with esmtp (Exim 1.92 #1) id 0zyAiU-00004K-00; Thu, 7 Jan 1999 08:22:54 +0000 To: Jaye Mathisen Cc: current@FreeBSD.ORG Subject: Re: How's 3.0-current as an NFS client? References: From: Dom Mitchell In-Reply-To: Jaye Mathisen's message of "Mon, 4 Jan 1999 17:25:34 -0800 (PST)" X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Date: Thu, 07 Jan 1999 08:22:54 +0000 Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jaye Mathisen writes: > Back a few months ago, there was some concern about the > stability/robustness of 3.x wrt NFS. > > I'm about to upgrade a box that for us is semi-mission-critical, to > 3.0-current, since it's running an old 3.x just peachy, but wanted to make > sure that there weren't any current NFS gotcha'sthat I've missed in the > mailing lists. Personally, I'd still describe it as a tad flaky. It works for most things, but at present, there are at least 3 things I can do with an nfs mounted home directory that cause the box to hang. These include starting netscape or xcopilot and sending mail with MH (a bit bizzare that last one, I'll admit). These are mostly just minor annyoances for me at the moment which I can live with, but I'd beware of putting a heavy NFS load on it. This is with a current compiled each Monday morning. -- When I said "we", officer, I was referring to myself, the four young ladies, and, of course, the goat. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 00:18:41 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA21001 for freebsd-current-outgoing; Fri, 8 Jan 1999 00:18:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA20985; Fri, 8 Jan 1999 00:18:38 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id DAA25151; Fri, 8 Jan 1999 03:18:08 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA04714; Fri, 8 Jan 1999 03:18:08 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id DAA33723; Fri, 8 Jan 1999 03:18:04 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199901080818.DAA33723@bb01f39.unx.sas.com> Subject: Bug in make affecting release crunchs To: freebsd-current@FreeBSD.ORG Date: Fri, 8 Jan 1999 03:18:04 -0500 (EST) Cc: jkh@zippy.cdrom.com, freebsd-bugs@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Folks, Jordan, I found the problem with the boot_crunch in make release.. Basically, Parse_IsVar() in parse.c contains the following code snippet: default: #ifdef SUNSHCMD while (*opc != ':') if (--opc < line) break; Well, this allows opc to end up pointing to the character just prior to line... ie: opc == 0807e2ff line == 0807e300 Then this code: if (strncmp(opc, ":sh", 3) == 0) { type = VAR_SHELL; *opc = '\0'; break; } #endif ends up comparing true if that 1 character in front of the variable line happens to be a ':' and we are trying to set the variable named 'sh_SRCDIR'. (What a bummer...) The simple fix (diff -u): diff -u parse.c.orig parse.c --- parse.c.orig Sun May 31 02:23:33 1998 +++ parse.c Fri Jan 8 03:05:23 1999 @@ -1412,8 +1412,10 @@ default: #ifdef SUNSHCMD while (*opc != ':') - if (--opc < line) + if (--opc < line) { + ++opc; break; + } if (strncmp(opc, ":sh", 3) == 0) { type = VAR_SHELL; Would some nice committer please commit this? Thanks! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 00:39:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA23267 for freebsd-current-outgoing; Fri, 8 Jan 1999 00:39:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA23251; Fri, 8 Jan 1999 00:39:09 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id AAA71750; Fri, 8 Jan 1999 00:38:40 -0800 (PST) To: "John W. DeBoskey" cc: freebsd-current@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG Subject: Re: Bug in make affecting release crunchs In-reply-to: Your message of "Fri, 08 Jan 1999 03:18:04 EST." <199901080818.DAA33723@bb01f39.unx.sas.com> Date: Fri, 08 Jan 1999 00:38:39 -0800 Message-ID: <71746.915784719@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Basically, Parse_IsVar() in parse.c contains the following > code snippet: I can't parse this since I don't even know what directory you're in or what file you're talking about. parse.c, yes. WHAT parse.c? :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 01:42:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA29452 for freebsd-current-outgoing; Fri, 8 Jan 1999 01:42:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from aire.open.ac.uk (aire.open.ac.uk [137.108.40.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA29446 for ; Fri, 8 Jan 1999 01:42:16 -0800 (PST) (envelope-from A.M.Zanker@open.ac.uk) Received: from mallard.open.ac.uk ([137.108.40.50] helo=mallard) by aire.open.ac.uk with smtp (Exim 2.05 #1) id 0zyYQM-00035G-00 for current@freebsd.org; Fri, 8 Jan 1999 09:41:46 +0000 Message-Id: <4.1.19990108091416.00a61e30@aire.open.ac.uk> X-Sender: mikez@aire.open.ac.uk X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Fri, 08 Jan 1999 09:41:45 +0000 To: current@FreeBSD.ORG From: Mike Zanker Subject: Moving from 2.2.8-STABLE to ELF 3.0-CURRENT (success) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Morning folks, I thought that I would share my experiences of moving from 2.2.8-STABLE to 3.0-CURRENT ELF in the hope that it may help or encourage anyone still wary of making the change. I've been tracking 2.2-STABLE since my initial install of 2.2.2. I wouldn't call myself a programmer, but then again I'm not frightened of failed makes and enjoy getting my hands dirty trying to figure out what the problems are. Anyway, I was getting a bit bored following the 2.2 branch - there were only a few source changes now and then and I wasn't having any problems "making the world". I decided that it was time to move to 3.0 and ELF so I developed a plan of action, taking things one step at a time. First of all I decided to go via 3.0-RELEASE rather than straight to CURRENT so I cvsup'd RELENG_3_0_0_RELEASE. I guess that I could have gone straight for an aout-to-elf at this stage but I wanted to make doubly sure that /dev and /etc were up-to-date so I built a 3.0-RELEASE aout system. This went just as smoothly as my previous 2.2 builds had gone. The only problem I had at this stage was that I tried to install the new boot blocks. However, they wouldn't build due to them needing the ELF objcopy. So far so good, so I did an aout-to-elf-build - which went OK - and an aout-to-elf-install. The only problem I had following the reboot was that some of the aout libraries from /usr/local/lib didn't get moved to /usr/local/lib/aout. I'm not too concerned, though, because I'm going to rebuild my ports as ELF. A quick solution was making sure that the aout ldconfig included /usr/local/lib as well as /usr/local/lib/aout. At this point the new boot blocks installed fine. I didn't bother with trying them out on a floppy first (because my system is fairly easy to recover) but I would recommend anyone else doing so (per Peter Wemm's document). I then went on an built an ELF kernel - again, no problems. Finally I cvsup'd against 3.0-CURRENT and did a make world to bring everything up-to-date. All I need to do now is install the ELF Xfree86 and recompile my ports. Anyway, apologies for rambling on a bit and I hope that one or two more wary people may be encouraged to take the plunge. Regards, Mike -- Mike Zanker | Email: A.M.Zanker@open.ac.uk Network and Computer Services Group | Tel : +44 1908 652726 The Open University | Fax : +44 1908 652193 Milton Keynes, UK | PGP public key available To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 01:53:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA00895 for freebsd-current-outgoing; Fri, 8 Jan 1999 01:53:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA00888 for ; Fri, 8 Jan 1999 01:53:08 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.2/8.9.2) with ESMTP id JAA04920 for ; Fri, 8 Jan 1999 09:52:38 GMT Message-ID: <3695D539.FCDBE542@tdx.co.uk> Date: Fri, 08 Jan 1999 09:51:53 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: dmesg: namelist: msgbufp not found? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All, I've just finally gotten round to running my first ELF kernel - The changeover worked nicely (big thanks to those involved, I like the "This is the first time you've built an ELF kernel, check your bootblocks now" bit ) The system works fine, it was CVS'upd yesterday - and the buildworld/installworld went fine (the system has been running ELF binaries for a long time now, but the ELF kernel is new). I only have 2 problems with it, the first of which is when I run dmesg I get: caladan# dmesg dmesg: namelist: msgbufp not found Any suggestions? - The kernel & userlands are in sync (which was the only thing I could think of)... -Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 02:06:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA02431 for freebsd-current-outgoing; Fri, 8 Jan 1999 02:06:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.sat.t.u-tokyo.ac.jp (dryad.sat.t.u-tokyo.ac.jp [133.11.156.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA02423 for ; Fri, 8 Jan 1999 02:06:24 -0800 (PST) (envelope-from simokawa@sat.t.u-tokyo.ac.jp) Received: from ett.sat.t.u-tokyo.ac.jp (ett.sat.t.u-tokyo.ac.jp [133.11.156.43]) by mail.sat.t.u-tokyo.ac.jp (8.8.6/3.4Wbeta6-SAT1.0) with ESMTP id TAA23671; Fri, 8 Jan 1999 19:04:54 +0900 (JST) (envelope-from simokawa@sat.t.u-tokyo.ac.jp) Received: from localhost by ett.sat.t.u-tokyo.ac.jp (8.8.8/sat-V0.6) id TAA04813; Fri, 8 Jan 1999 19:04:53 +0900 (JST) To: jkh@zippy.cdrom.com Cc: jbg@masterplan.org (Jason George), freebsd-current@FreeBSD.ORG Subject: Re: News Server In-Reply-To: Your message of "Tue, 05 Jan 1999 10:59:11 -0800" <6203.915562751@zippy.cdrom.com> References: <6203.915562751@zippy.cdrom.com> X-Face: OE([KxWyJI0r[R~S/>7ia}SJ)i%a,$-9%7{*yihQk|]gl}2p#"oXmX/fT}Bn7:#j7i14gu$ jgR\S*&C3R/pJX Date: Fri, 08 Jan 1999 19:04:52 +0900 From: Hidetoshi Shimokawa X-Dispatcher: imput version 980905(IM100) Lines: 15 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG jkh> > I've been running a mail2news read-only gateway for a few months now. jkh> > (I'm not gating all the lists, but do have most of them...) jkh> > jkh> > It's available at atomic-playboy.masterplan.org (207.167.12.181). jkh> jkh> Wow, this seems to work fine... How about just pointing jkh> news.freebsd.org at this site? :-) news.jp.freebsd.org has been working for more than a year. ^^ It has most of freebsd-* lists and lists in jp.freebsd.org. /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: finger -l simokawa@sat.t.u-tokyo.ac.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 02:34:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA04918 for freebsd-current-outgoing; Fri, 8 Jan 1999 02:34:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA04912 for ; Fri, 8 Jan 1999 02:34:39 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.10 #1) id 0zyZEe-0000gm-00; Fri, 8 Jan 1999 12:33:44 +0200 From: Sheldon Hearn To: Mike Zanker cc: current@FreeBSD.ORG Subject: Re: Moving from 2.2.8-STABLE to ELF 3.0-CURRENT (success) In-reply-to: Your message of "Fri, 08 Jan 1999 09:41:45 GMT." <4.1.19990108091416.00a61e30@aire.open.ac.uk> Date: Fri, 08 Jan 1999 12:33:41 +0200 Message-ID: <2650.915791621@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 08 Jan 1999 09:41:45 GMT, Mike Zanker wrote: > I thought that I would share my experiences of moving from 2.2.8-STABLE to > 3.0-CURRENT ELF in the hope that it may help or encourage anyone still wary > of making the change. Hi Mike, Thanks for the encouragement. I'm busy doing this myself and it looks like we both chose the same upgrade plan. > So far so good, so I did an aout-to-elf-build - which went OK - and an > aout-to-elf-install. The only problem I had following the reboot was that > some of the aout libraries from /usr/local/lib didn't get moved to > /usr/local/lib/aout. Can you tell us exactly what you mean by "some of the aout libraries ... didn't get moved"? Judging from the timestamps on those files, can you determine whether they were libraries generated during the aout-to-elf installation, or whether they were leftovers from your RELENG_3_0_0_RELEASE build? If they were leftovers, then we're probably talking "acceptable behaviour" on this one. If they were installed by the aout-to-elf install, then it's something John Birrell might be interested in hearing. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 02:45:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA05663 for freebsd-current-outgoing; Fri, 8 Jan 1999 02:45:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA05630 for ; Fri, 8 Jan 1999 02:44:45 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.10 #1) id 0zyZOV-0000iA-00; Fri, 8 Jan 1999 12:43:56 +0200 From: Sheldon Hearn To: Mike Zanker cc: current@FreeBSD.ORG Subject: Re: Moving from 2.2.8-STABLE to ELF 3.0-CURRENT (success) In-reply-to: Your message of "Fri, 08 Jan 1999 12:33:41 +0200." <2650.915791621@axl.noc.iafrica.com> Date: Fri, 08 Jan 1999 12:43:55 +0200 Message-ID: <2737.915792235@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 08 Jan 1999 12:33:41 +0200, Sheldon Hearn wrote: > If they were leftovers, then we're probably talking "acceptable > behaviour" on this one. If they were installed by the aout-to-elf > install, then it's something John Birrell might be interested in > hearing. Assuming, of course, that you noticed and used the target which guys like you and me miss: # move-aout-libs - Move the a.out libraries into an aout sub-directory # of each elf library sub-directory. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 02:46:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA06055 for freebsd-current-outgoing; Fri, 8 Jan 1999 02:46:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA06032 for ; Fri, 8 Jan 1999 02:46:00 -0800 (PST) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (tiburon [158.227.6.111]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id LAA09125; Fri, 8 Jan 1999 11:41:22 +0100 (MET) Message-ID: <3695E0D2.2A837D2A@we.lc.ehu.es> Date: Fri, 08 Jan 1999 11:41:22 +0100 From: "José Mª Alcaide" Organization: Universidad del País Vasco - Dept. de Electricidad y Electrónica X-Mailer: Mozilla 4.07 [en] (X11; U; FreeBSD 2.2.8-RELEASE i386) MIME-Version: 1.0 To: Matthew Dillon CC: freebsd-current@FreeBSD.ORG Subject: Re: SOFTUPDATES References: <199901080632.WAA38081@apollo.backplane.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 Matthew Dillon wrote: > > Softupdates basically gives you the advantage of an async mount without > any of the risks. It's actually better then that - it can unwind commits > to disk before they occur ( e.g. if you create a temporary file and then > delete it very soon after ). Softupdates basically guarentees disk > consistancy in the face of a crash. > > It's pretty well debugged as it stands -- I'd call it production. I don't > think the problem the person who was posting and calling a softupdates > is actually a softupdates problem. I've been using it solidly for a while > and BEST has been using it on their nntp box ( a very heavily loaded box ) > for a few months. > The main problem I see with softupdates is the lack of information. I read the tunefs(8) manpage and I found the "-n" option. However, there is no mention to the need of the SOFTUPDATES kernel option (I bumped into it while reading LINT). I think that a little tutorial about what softupdates is, and how to turn it on, should be very useful for many users (like me :-) ). -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | http://www.we.lc.ehu.es/~jose Dpto. de Electricidad y Electrónica | Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139 ----------------------------------------------------------------------- "Go ahead... make my day." - H. Callahan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 02:52:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA06588 for freebsd-current-outgoing; Fri, 8 Jan 1999 02:52:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from aire.open.ac.uk (aire.open.ac.uk [137.108.40.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA06580 for ; Fri, 8 Jan 1999 02:52:19 -0800 (PST) (envelope-from A.M.Zanker@open.ac.uk) Received: from mallard.open.ac.uk ([137.108.40.50] helo=mallard) by aire.open.ac.uk with smtp (Exim 2.05 #1) id 0zyZVw-000395-00; Fri, 8 Jan 1999 10:51:37 +0000 Message-Id: <4.1.19990108104454.00ab8da0@aire.open.ac.uk> X-Sender: mikez@aire.open.ac.uk X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Fri, 08 Jan 1999 10:51:36 +0000 To: Sheldon Hearn From: Mike Zanker Subject: Re: Moving from 2.2.8-STABLE to ELF 3.0-CURRENT (success) Cc: current@FreeBSD.ORG In-Reply-To: <2650.915791621@axl.noc.iafrica.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:33 08/01/99 , Sheldon Hearn wrote: >Can you tell us exactly what you mean by "some of the aout libraries >... didn't get moved"? Judging from the timestamps on those files, >can you determine whether they were libraries generated during the >aout-to-elf installation, or whether they were leftovers from your >RELENG_3_0_0_RELEASE build? I meant the libraries in /usr/local/lib built from the ports collection. For example, libgif and libjpeg were moved but libtiff wasn't for some reason. This happened during the aout-to-elf-install. Regards, Mike -- Mike Zanker | Email: A.M.Zanker@open.ac.uk Network and Computer Services Group | Tel : +44 1908 652726 The Open University | Fax : +44 1908 652193 Milton Keynes, UK | PGP public key available To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 02:54:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA06971 for freebsd-current-outgoing; Fri, 8 Jan 1999 02:54:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from aire.open.ac.uk (aire.open.ac.uk [137.108.40.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA06951 for ; Fri, 8 Jan 1999 02:53:59 -0800 (PST) (envelope-from A.M.Zanker@open.ac.uk) Received: from mallard.open.ac.uk ([137.108.40.50] helo=mallard) by aire.open.ac.uk with smtp (Exim 2.05 #1) id 0zyZXZ-00039L-00; Fri, 8 Jan 1999 10:53:18 +0000 Message-Id: <4.1.19990108105155.00aba8b0@aire.open.ac.uk> X-Sender: mikez@aire.open.ac.uk X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Fri, 08 Jan 1999 10:53:17 +0000 To: Sheldon Hearn From: Mike Zanker Subject: Re: Moving from 2.2.8-STABLE to ELF 3.0-CURRENT (success) Cc: current@FreeBSD.ORG In-Reply-To: <2737.915792235@axl.noc.iafrica.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:43 08/01/99 , Sheldon Hearn wrote: >Assuming, of course, that you noticed and used the target which guys >like you and me miss: > ># move-aout-libs - Move the a.out libraries into an aout sub-directory ># of each elf library sub-directory. That's called by the aout-to-elf-install target anyway so there should be no need to run it separately. Regards, Mike -- Mike Zanker | Email: A.M.Zanker@open.ac.uk Network and Computer Services Group | Tel : +44 1908 652726 The Open University | Fax : +44 1908 652193 Milton Keynes, UK | PGP public key available To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 02:58:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA07362 for freebsd-current-outgoing; Fri, 8 Jan 1999 02:58:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA07294 for ; Fri, 8 Jan 1999 02:57:54 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.10 #1) id 0zyZbA-0000kh-00; Fri, 8 Jan 1999 12:57:00 +0200 From: Sheldon Hearn To: Mike Zanker cc: current@FreeBSD.ORG Subject: Re: Moving from 2.2.8-STABLE to ELF 3.0-CURRENT (success) In-reply-to: Your message of "Fri, 08 Jan 1999 10:51:36 GMT." <4.1.19990108104454.00ab8da0@aire.open.ac.uk> Date: Fri, 08 Jan 1999 12:57:00 +0200 Message-ID: <2894.915793020@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 08 Jan 1999 10:51:36 GMT, Mike Zanker wrote: > I meant the libraries in /usr/local/lib built from the ports > collection. Ah, great. This is encouraging, because it means that it's something which a normal ports rebuild and find -ctime will sort out. Thanks again for the feedback to the list. I hate "me too" posts as much as the next guy, so y'all can assume it went well for me too if you don't see mail from me within the next few days. ;-) Later, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 03:02:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA07733 for freebsd-current-outgoing; Fri, 8 Jan 1999 03:02:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fep2-orange.clear.net.nz (fep2-orange.clear.net.nz [203.97.32.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA07728 for ; Fri, 8 Jan 1999 03:02:30 -0800 (PST) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep2-orange.clear.net.nz (1.5/1.9) with ESMTP id AAA05485; Sat, 9 Jan 1999 00:01:59 +1300 (NZDT) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.1/8.9.1) id AAA18021; Sat, 9 Jan 1999 00:01:56 +1300 (NZDT) (envelope-from jabley) Date: Sat, 9 Jan 1999 00:01:56 +1300 From: Joe Abley To: Dom Mitchell Cc: Jaye Mathisen , current@FreeBSD.ORG, jabley@clear.co.nz Subject: Re: How's 3.0-current as an NFS client? Message-ID: <19990109000156.B17962@clear.co.nz> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Dom Mitchell on Thu, Jan 07, 1999 at 08:22:54AM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 07, 1999 at 08:22:54AM +0000, Dom Mitchell wrote: > > Personally, I'd still describe it as a tad flaky. It works for most > things, but at present, there are at least 3 things I can do with an > nfs mounted home directory that cause the box to hang. These include > starting netscape or xcopilot and sending mail with MH (a bit bizzare > that last one, I'll admit). These are mostly just minor annyoances > for me at the moment which I can live with, but I'd beware of putting > a heavy NFS load on it. > > This is with a current compiled each Monday morning. I run 3.0 about as current as you every day as an NFS client, and I have seen no issues for months. The NFS server in my case is a SPARC Solaris 2.5.1 box, and I am running NFSv2/UDP. What's your server? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 03:29:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA10025 for freebsd-current-outgoing; Fri, 8 Jan 1999 03:29:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gw1.pl.cp (redion.nttmcl.com [216.69.69.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA10020 for ; Fri, 8 Jan 1999 03:29:42 -0800 (PST) (envelope-from astralblue@usa.net) Received: from localhost (gene@localhost) by gw1.pl.cp (8.9.1/8.9.1) with SMTP id DAA06974; Fri, 8 Jan 1999 03:28:07 -0800 (PST) (envelope-from astralblue@usa.net) X-Authentication-Warning: gw1.pl.cp: gene owned process doing -bs Date: Fri, 8 Jan 1999 03:28:07 -0800 (PST) From: "Eugene M. Kim" X-Sender: gene@gw1.pl.cp To: Alex Le Heux cc: freebsd-current@FreeBSD.ORG Subject: Re: freeze when trying to mount FAT32 In-Reply-To: <3695694C.309A63E4@funk.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had the same problem today; do you statically comple MSDOS filesystem into your kernel? If not, as in my case, you must rebuild /modules/msdos.ko before mounting any FAT32 filesystem: cd /usr/src/sys/modules/msdos MAKEOBJDIRPREFIX=/usr/obj/`objformat` ; export MAKEOBJDIRPREFIX make clean cleandepend make obj make depend all install Hope this helps, Eugene On Fri, 8 Jan 1999, Alex Le Heux wrote: | Hi, | | When I try "mount -t msdos /dev/wd0s1 /msdos" on a FAT32 filesystem, it | sits there for about 10 seconds, after which the system freezes. No | response, no ddb, nothing. | | Even when I ^C it after a second or so, the system still freezes about | 10 seconds later. (just enough time to type sync :-) | | This is on a current system that I cvsupped about 4 hours ago. | | Alex -- Eugene M. Kim "Is your music unpopular? Make it popular; make music which people like, or make people who like your music." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 03:42:41 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA11070 for freebsd-current-outgoing; Fri, 8 Jan 1999 03:42:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (slip139-92-122-62.joh.za.ibm.net [139.92.122.62]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA11065 for ; Fri, 8 Jan 1999 03:42:37 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id NAA00507; Fri, 8 Jan 1999 13:39:32 +0200 (SAT) From: Robert Nordier Message-Id: <199901081139.NAA00507@ceia.nordier.com> Subject: Re: Installation of bootblocks ona dual boot system In-Reply-To: from Spike Gronim at "Jan 7, 99 09:31:02 pm" To: sporkl@ix.netcom.com Date: Fri, 8 Jan 1999 13:39:30 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Spike Gronim wrote: > I will need to install the new boot blocks when I upgrade, but my > system dual boots. I have one hard drive, sd0, with the first partition > containing Winblows 95 and the second containing FreeBSD. What is the > sequence of commands I must enter in order to preserve my bootloader but > use the new bootblocks? See http://www.freebsd.org/~rnordier/boot.txt The fact that your system dual boots should not matter. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 04:18:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA16500 for freebsd-current-outgoing; Fri, 8 Jan 1999 04:18:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA16495; Fri, 8 Jan 1999 04:18:45 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id HAA02114; Fri, 8 Jan 1999 07:18:42 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.1/8.8.5) with ESMTP id IAA10531; Fri, 8 Jan 1999 08:02:07 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.1/8.6.9) id HAA02256; Fri, 8 Jan 1999 07:18:50 -0500 (EST) Date: Fri, 8 Jan 1999 07:18:50 -0500 (EST) From: Thomas David Rivers Message-Id: <199901081218.HAA02256@lakes.dignus.com> To: jkh@zippy.cdrom.com, jwd@unx.sas.com Subject: Re: Bug in make affecting release crunchs Cc: freebsd-bugs@FreeBSD.ORG, freebsd-current@FreeBSD.ORG In-Reply-To: <71746.915784719@zippy.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Basically, Parse_IsVar() in parse.c contains the following > > code snippet: > > I can't parse this since I don't even know what directory you're in or > what file you're talking about. parse.c, yes. WHAT parse.c? :-) > > - Jordan Jordan - I believe he's talking about the make(1) program, in particular, /usr/src/usr.bin/make/parse.c - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 04:21:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA17059 for freebsd-current-outgoing; Fri, 8 Jan 1999 04:21:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA17048 for ; Fri, 8 Jan 1999 04:20:56 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.10 #1) id 0zyatp-0004eK-00 for current@freebsd.org; Fri, 8 Jan 1999 14:20:21 +0200 From: Sheldon Hearn To: current@FreeBSD.ORG Subject: Enabling Softupdates with symlinks? Date: Fri, 08 Jan 1999 14:20:21 +0200 Message-ID: <17875.915798021@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, LINT says this: # Allow the FFS to use Softupdates technology. # To do this you need to copy the two files # /sys/ufs/ffs/softdep.h and /sys/ufs/ffs/ffs_softdep.c # from /usr/src/contrib/sys/softupdates # and understand the licensing restrictions. # You should also check on the FreeBSD website for newer versions. #options SOFTUPDATES If I follow these isntructions and cp the files, I need to repeat the procedure any time the softupdates code is changed. Is it not feasible to use symbolic links to the files in the softupdates directory instead? i.e.: cd /sys/ufs/ffs ln -s /usr/src/contrib/sys/softupdates/softdep.h ln -s /usr/src/contrib/sys/softupdates/ffs_softdep.h This would require less thinking later on. Thanks, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 04:24:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA17292 for freebsd-current-outgoing; Fri, 8 Jan 1999 04:24:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA17284 for ; Fri, 8 Jan 1999 04:24:10 -0800 (PST) (envelope-from netchild@wurzelausix.cs.uni-sb.de) Received: from Vodix.CS.Uni-SB.de (acc1-137.telip.uni-sb.de [134.96.113.137]) by uni-sb.de (8.9.2/1999010400) with ESMTP id NAA07575; Fri, 8 Jan 1999 13:23:28 +0100 (CET) Received: from wurzelausix.cs.uni-sb.de (localhost [127.0.0.1]) by Vodix.CS.Uni-SB.de (8.9.1/8.9.1) with ESMTP id NAA01555; Fri, 8 Jan 1999 13:18:54 +0100 (CET) (envelope-from netchild@wurzelausix.cs.uni-sb.de) Message-Id: <199901081218.NAA01555@Vodix.CS.Uni-SB.de> Date: Fri, 8 Jan 1999 13:18:52 +0100 (CET) From: Alexander Leidinger Subject: Re: nlpt & polling mode didn't work To: nsouch@teaser.fr cc: current@FreeBSD.ORG In-Reply-To: <19990107231544.61205@breizh.prism.uvsq.fr> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 7 Jan, Nicolas Souchu wrote: >>>>The problem: >>>>It takes a looooong time to send data to the printer. >>> >>> Printing is ok? >> >>I think (nobody wants to wait more than 15 minutes for the page). >>BTW: I have only 3rd person access to it. Its the system of my brother, >>and hi is only an user. > > And I imagine the old-lpt code works. No. lpt didn't work, but I remember it didn't work the first time I tried it too. It worked only with nlpt. > You may add printfs to the /sys/dev/ppbus/nlpt.c to check where it fails. To nlpt_pushbytes()? What am I looking for? Bye, Alexander. -- "Darth Vader sleeps with a Teddywookie." Fortune cookie http://netchild.home.pages.de/ A.Leidinger @ wurzelausix.cs.uni-sb.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 04:33:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA17939 for freebsd-current-outgoing; Fri, 8 Jan 1999 04:33:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA17838; Fri, 8 Jan 1999 04:33:00 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:jukc2MIPIVqkd/lVk70jL/ZVZE95C8HC@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id VAA27174; Fri, 8 Jan 1999 21:32:10 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id VAA13287; Fri, 8 Jan 1999 21:34:34 +0900 (JST) Message-Id: <199901081234.VAA13287@zodiac.mech.utsunomiya-u.ac.jp> To: Doug Rabson cc: sos@FreeBSD.ORG, msmith@FreeBSD.ORG, current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: syscons update - when? In-reply-to: Your message of "Wed, 06 Jan 1999 17:02:55 GMT." References: Date: Fri, 08 Jan 1999 21:34:33 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> > I prefer the option a). But, I have to expect rough ride after >> > commits, as changes of this scale will have many initial glitches... >> >> I prefer option a) also. > >If option a) also includes repo-copying the code out of the i386 tree into >an architecture neutral place, then I think that is the right way to go. >I'd rather not perform that kind of code movement after the split. Ok, here is my plan. Stage 0. ------------------------------------------------------ This weekend I will commit the following new files. i386/isa/atkbd_isa.c i386/isa/atkbdc_isa.c i386/isa/vga_isa.c dev/kbd/kbd.c dev/kbd/kbdreg.h dev/kbd/atkbd.c dev/kbd/atkbdreg.h dev/kbd/atkbdc.c dev/kbd/atkbdcreg.h dev/fb/fb.c dev/fb/fbreg.c dev/fb/splash.c dev/fb/splashreg.c dev/fb/vgareg.c The following files are repository-copied from i386/isa and updated in preparation for the next stage. i386/isa/syscons.[ch] and i386/isa/sc*ctl.c are not yet deleted. dev/syscons/syscons.c dev/syscons/syscons.h dev/syscons/scvesactl.c dev/syscons/scvidctl.c The new drivers are not yet activated. The users will be still using existing syscons at this point. Stage 1. ------------------------------------------------------ On Sunday evening, the new keyboard driver will be activated. The following files will be updated. i386/conf/GENERIC i386/conf/LINT i386/conf/files.i386 i386/conf/options.i386 i386/include/console.h i386/isa/pcvt/* i386/isa/psm.c usr.sbin/kbdcontrol/kbdcontrol.c The users are REQUIRED to update their kernel configuration files to include the new keyboard driver. I will send out "HEADS UP" on this. NOTE: the new keyboard driver files will be registered to i386/conf/files.i386 at this time, althouth some of them are placed in an architecture neutral directly dev/kbd. This is because they are not yet ported alpha. Stage 2. ------------------------------------------------------ On 14, the new video card driver (and splash screen) will be activated. The following files will be added. modules/splash/bmp/Makefile modules/splash/bmp/splash_bmp.c The following files will be updated. dev/syscons/syscons.c dev/syscons/syscons.h dev/syscons/scvesactl.c dev/syscons/scvidctl.c i386/conf/GENERIC i386/conf/LINT i386/conf/files.i386 i386/conf/options.i386 i386/include/console.h i386/include/pc/vesa.h i386/isa/vesa.c modules/syscons/* modules/vesa/Makefile usr.sbin/vidcontrol/vidcontrol.c The users are REQUIRED to update their kernel configuration files to include the new driver, again. I will send out "HEADS UP" on this too. NOTE: although syscons.[ch], sc*ctl.c and some video driver files are placed in architecture neutral directories dev/syscons and dev/fb, they are not yet runnable on alpha yet. Once they are ported, the files in dev/syscons, dev/fb and dev/kbd should be registered to sys/conf/files rather than sys/i386/conf/files.i386. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 04:40:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA18677 for freebsd-current-outgoing; Fri, 8 Jan 1999 04:40:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freya.circle.net (freya.circle.net [209.95.95.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA18669 for ; Fri, 8 Jan 1999 04:40:06 -0800 (PST) (envelope-from tcobb@staff.circle.net) From: tcobb@staff.circle.net Received: by FREYA with Internet Mail Service (5.5.2232.9) id ; Fri, 8 Jan 1999 07:34:05 -0500 Message-ID: To: freebsd-current@FreeBSD.ORG Subject: 3.0-19981121-SNAP Date: Fri, 8 Jan 1999 07:34:03 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been successfully using the 11/21/98 SNAP on 10+ machines, but unfortunately did not download and save an archived copy of this SNAP. Now, suddenly, it appears that ftp://current.freebsd.org has deleted it (and everything else from 1998!). Does anyone know of another location to retrieve a copy of this SNAP? -Troy Cobb Circle Net, Inc. http://www.circle.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 05:06:41 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA20735 for freebsd-current-outgoing; Fri, 8 Jan 1999 05:06:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA20492 for ; Fri, 8 Jan 1999 05:06:17 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id OAA22827; Fri, 8 Jan 1999 14:11:17 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Fri, 8 Jan 1999 14:11:17 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Andreas Klemm cc: current@FreeBSD.ORG Subject: Re: can't boot from CD and floppy after make release In-Reply-To: <19990107213355.A20076@titan.klemm.gtn.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, 7 Jan 1999, Andreas Klemm wrote: > There is still something wrong... > The boot floppy loads and loads and loads, then: > Warning: malloc wrapped > > Booting from CD-Rom isn't successfull, halts after loading > kernel ... > > Current from 2 days before (990105) This is still with a.out kernel? With the new bootloader, or the old one? Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 05:11:50 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA21254 for freebsd-current-outgoing; Fri, 8 Jan 1999 05:11:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from asteroid.svib.ru (asteroid.svib.ru [195.151.166.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA21243 for ; Fri, 8 Jan 1999 05:11:46 -0800 (PST) (envelope-from tarkhil@asteroid.svib.ru) Received: from minas-tirith.pol.ru (root@shuttle.svib.ru [195.151.166.144]) by asteroid.svib.ru (8.9.1a/8.9.1) with ESMTP id QAA05928 for ; Fri, 8 Jan 1999 16:11:14 +0300 (MSK) Received: from minas-tirith.pol.ru (tarkhil@minas-tirith.pol.ru [127.0.0.1]) by minas-tirith.pol.ru (8.8.8/8.8.8) with ESMTP id QAA09080 for ; Fri, 8 Jan 1999 16:11:43 +0300 (MSK) (envelope-from tarkhil@minas-tirith.pol.ru) Message-Id: <199901081311.QAA09080@minas-tirith.pol.ru> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Reply-To: tarkhil@asteroid.svib.ru Subject: Problems with 486SX X-URL: http://freebsd.svib.ru Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Date: Fri, 08 Jan 1999 16:11:42 +0300 From: Alex Povolotsky Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I've tried to install 3.0-RELEASE on HP's 486SX. I've compiled (on much better machine) kernel with math emulator turned on, and tried to run. Many programs (fsck, w, top, squid) exits on signal 8 or 10, and sometimes kernel panics. In past two years I've installed FreeBSD on about a dozen computers, but never experienced such behavior. OTOH, I don't remember myself installing anything on system w/o coprocessor. What should I investigate? Alex. -- Alexander B. Povolotsky [ICQ 18277558] [2:5020/145] [http://freebsd.svib.ru] [tarkhil@asteroid.svib.ru] [Urgent messages: 234-9696 ÁÂ.#35442 or tarkhil@pager.express.ru] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 05:12:38 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA21422 for freebsd-current-outgoing; Fri, 8 Jan 1999 05:12:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA21397 for ; Fri, 8 Jan 1999 05:12:34 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id OAA23304; Fri, 8 Jan 1999 14:15:15 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Fri, 8 Jan 1999 14:15:14 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: "Jordan K. Hubbard" cc: Matthew Dillon , Mike Smith , Andreas Klemm , current@FreeBSD.ORG Subject: Re: can't boot from CD and floppy after make release In-Reply-To: <68214.915753694@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 Thu, 7 Jan 1999, Jordan K. Hubbard wrote: > > Jordan, if gzip works you could have just said so in the first place! > > Sorry, I thought that characteristic of the new boot blocks was already > common knowledge. Bear in mind, though, that you'll need additional 100kB of place on the floppy (that's approx. the difference between kzip stubs and the /boot/loader). In this light it makes sense to do what rnordier suggested - namely, to write a small BTX application which would only be able to load kernel.gz. I _may_ embark on such a project if I have some docs about how to use BTX. Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 05:20:02 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA22471 for freebsd-current-outgoing; Fri, 8 Jan 1999 05:20:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dns.webwizard.net.mx (webwizard.net.mx [148.245.50.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA22414 for ; Fri, 8 Jan 1999 05:19:59 -0800 (PST) (envelope-from eculp@webwizard.org.mx) Received: from webwizard.org.mx (webwizard.net.mx [148.245.50.27]) by dns.webwizard.net.mx (8.9.1/8.9.1) with ESMTP id HAA12485; Fri, 8 Jan 1999 07:19:17 -0600 (CST) (envelope-from eculp@webwizard.org.mx) Message-ID: <369605D3.C9523819@webwizard.org.mx> Date: Fri, 08 Jan 1999 07:19:16 -0600 From: Edwin Culp X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Sheldon Hearn CC: current@FreeBSD.ORG Subject: Re: Enabling Softupdates with symlinks? References: <17875.915798021@axl.noc.iafrica.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > Hi there, > > LINT says this: > > # Allow the FFS to use Softupdates technology. > # To do this you need to copy the two files > # /sys/ufs/ffs/softdep.h and /sys/ufs/ffs/ffs_softdep.c > # from /usr/src/contrib/sys/softupdates > # and understand the licensing restrictions. > # You should also check on the FreeBSD website for newer versions. > #options SOFTUPDATES > > If I follow these isntructions and cp the files, I need to repeat the > procedure any time the softupdates code is changed. > > Is it not feasible to use symbolic links to the files in the softupdates > directory instead? i.e.: > > cd /sys/ufs/ffs > ln -s /usr/src/contrib/sys/softupdates/softdep.h > ln -s /usr/src/contrib/sys/softupdates/ffs_softdep.h > > This would require less thinking later on. > > Thanks, > Sheldon. I suggest you look at /usr/src/sys/ufs/ffs/README.softupdates. You could almost have written it:-) For legal reasons the two active files for using Soft Updates are in /usr/src/contrib/sys/softupdates. To enable the feature in your kernel, link the files into this directory as follows: cd /usr/src/sys/ufs/ffs ln -s ../../../contrib/sys/softupdates/*.[ch] . and add option SOFTUPDATES to your kernel configuration. You should also read the copyrights in the sources and the README file in /usr/src/contrib/sys/softupdates before enabling this feature to ensure that you are acting legally. The stub file provided here is only enough to allow the system to function without this option being turned on. Once you're running a kernel with soft update support, you need to enable it for whichever filesystems you wish to run with the soft update policy. This is done with the -n option to tunefs(8) on the UNMOUNTED filesystems, e.g. from single-user mode you'd do something like: tunefs -n enable /dev/rsd0s1d To permanently enable soft updates on that filesystem (or at least until a corresponding ``tunefs -n disable'' is done). ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 05:21:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA22607 for freebsd-current-outgoing; Fri, 8 Jan 1999 05:21:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA22595 for ; Fri, 8 Jan 1999 05:21:52 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.1/8.9.1) id OAA97154; Fri, 8 Jan 1999 14:20:46 +0100 (CET) (envelope-from des) To: frank@exit.com Cc: viren@rstcorp.com, frank@tinker.exit.com, current@FreeBSD.ORG Subject: Re: Why won't 3.0-current remember my config? References: <199901060615.WAA00326@realtime.exit.com> From: Dag-Erling Smorgrav Date: 08 Jan 1999 14:20:45 +0100 In-Reply-To: Frank Mayhar's message of "Tue, 5 Jan 1999 22:15:47 -0800 (PST)" Message-ID: Lines: 22 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Frank Mayhar writes: > > Put your pnp config line above in a file (say /boot/pnp.config ) like: > > > > USERCONFIG > > pnp 1 1 os enable port0 0x534 port2 0x220 port3 0xe0d irq0 10 drq0 1 drq1 6 > > quit > > > > and in > > /boot/boot.conf put in the line > > load -t userconfig_script /boot/pnp.config > > Okay, this worked, with the added caveat that putting _just_ that line > in /boot/boot.conf results in the message "load: can't load file before > kernel" and the command being ignored. I preceded that line with the line > "load kernel" and everything appears to be working fine. Many thanks. Remove the "USERCONFIG" and "quit" lines from /boot/pnp.config. And you might want to add "autoboot 5" at the end of /boot/boot.conf. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 05:21:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA22624 for freebsd-current-outgoing; Fri, 8 Jan 1999 05:21:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.42.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA22591; Fri, 8 Jan 1999 05:21:51 -0800 (PST) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.9.1/8.9.1) id OAA11253; Fri, 8 Jan 1999 14:21:03 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199901081321.OAA11253@sos.freebsd.dk> Subject: Re: syscons update - when? In-Reply-To: <199901081234.VAA13287@zodiac.mech.utsunomiya-u.ac.jp> from Kazutaka YOKOTA at "Jan 8, 1999 9:34:33 pm" To: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA) Date: Fri, 8 Jan 1999 14:21:03 +0100 (CET) Cc: dfr@nlsystems.com, sos@FreeBSD.ORG, msmith@FreeBSD.ORG, current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Kazutaka YOKOTA wrote: > > Ok, here is my plan. [plan deleted] Sounds great too me!! I finally got my USB keyboard, so I can get on with that too... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@freebsd.org) FreeBSD Core Team member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 05:29:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA23329 for freebsd-current-outgoing; Fri, 8 Jan 1999 05:29:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA23324 for ; Fri, 8 Jan 1999 05:29:45 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.1/8.9.1) id OAA97174; Fri, 8 Jan 1999 14:29:03 +0100 (CET) (envelope-from des) To: lh@aus.org Cc: current@FreeBSD.ORG Subject: Re: CVS release tages for 3.0 anomaly References: <199901070529.AAA14795@ayukawa.aus.org> From: Dag-Erling Smorgrav Date: 08 Jan 1999 14:29:01 +0100 In-Reply-To: Luke's message of "Thu, 07 Jan 1999 00:47:53 -0500 (EST)" Message-ID: Lines: 10 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luke writes: > I was wondering how come in the src tree theres a > RELENG_3_0_0_RELEASE tag for cvs, then in the ports tree theres > RELEASE_3_0_0 ? Is it on purpose? Histerical raisins. Besides, the ports tree isn't branched. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 05:31:34 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA23557 for freebsd-current-outgoing; Fri, 8 Jan 1999 05:31:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA23551 for ; Fri, 8 Jan 1999 05:31:32 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.1/8.9.1) id OAA97139; Fri, 8 Jan 1999 14:16:49 +0100 (CET) (envelope-from des) To: Eddie Irvine Cc: freebsd-current@FreeBSD.ORG Subject: Re: Installed 3.0 CD. Flag day? References: <3692D945.5A09B394@tpgi.com.au> From: Dag-Erling Smorgrav Date: 08 Jan 1999 14:16:48 +0100 In-Reply-To: Eddie Irvine's message of "Wed, 06 Jan 1999 14:32:21 +1100" Message-ID: Lines: 8 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eddie Irvine writes: > So, does this mean I don't need to do the "a.out to elf upgrade"? 3.0-RELEASE is already Elf. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 05:36:22 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA23968 for freebsd-current-outgoing; Fri, 8 Jan 1999 05:36:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from megaweapon.zigg.com (megaweapon.zigg.com [206.114.60.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA23963 for ; Fri, 8 Jan 1999 05:36:19 -0800 (PST) (envelope-from matt@megaweapon.zigg.com) Received: from localhost (matt@localhost) by megaweapon.zigg.com (8.8.8/8.8.8) with ESMTP id IAA00485; Fri, 8 Jan 1999 08:30:46 -0500 (EST) (envelope-from matt@megaweapon.zigg.com) Date: Fri, 8 Jan 1999 08:30:46 -0500 (EST) From: Matt Behrens To: Luigi Rizzo cc: =?X-UNKNOWN?Q?S=F8ren_Schmidt?= , obrien@NUXI.com, andyf@speednet.com.au, freebsd-current@FreeBSD.ORG Subject: Re: beep, beep, beep! In-Reply-To: <199901080523.GAA10518@labinfo.iet.unipi.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 8 Jan 1999, Luigi Rizzo wrote: : > It seems David O'Brien wrote: : > > > > Shouldn't the new boot code be beeping at us? :) : > > > Also Also, , make make it it optional optional :) :) : > > : > > The beeps are for our un-sighted users. : > : > Yeah, but does it have to be 3 of them, we wouldn't want the : > rest of us to go un-hearing now would we :) : : and i also commented to Jordan, 3 beeps like those mean you cannot : do night installs at home without waking up the rest of the family. It's called unplugging the speaker. ;) - Matt Behrens Network Administrator, zigg.com Engineer, Nameless IRC Network To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 05:37:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA24243 for freebsd-current-outgoing; Fri, 8 Jan 1999 05:37:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA24235 for ; Fri, 8 Jan 1999 05:37:02 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.1/8.9.1) id OAA97196; Fri, 8 Jan 1999 14:36:17 +0100 (CET) (envelope-from des) To: N Cc: "T.D. Brace" , freebsd-current@FreeBSD.ORG Subject: Re: inetd problem References: <990108004112.23760A-100000@liquid.tpb.net> From: Dag-Erling Smorgrav Date: 08 Jan 1999 14:36:16 +0100 In-Reply-To: N's message of "Fri, 8 Jan 1999 00:42:58 +0100 (CET)" Message-ID: Lines: 24 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG N writes: > > Can anyone tell me if the inetd realloc (and other) problems have been > > fixed yet? Searching Deja News shows conflicting reports. I checked > > the current diffs, and built version 1.46 - is this a safe version to > > use? It's been running on my local workstation for a few days now, but > > it really doesn't have any load on it. I'd like to copy it up to our > > webservers, but thought I would ask first. > > If you mean the "dying daemons" problem, it has probably been fixed in > version 1.105 of src/sys/vm/swap_pager.c. No. People are constantly confused over this issue. There is (was) a bug in inetd related to the way it handles signals, which caused it to output "junk pointer: too low to make sense" (or sometimes "too high to make sense") when under heavy load. It is not the same bug as the dying daemons bug. There have been two attemps to fix the inetd bug: one by Matt Dillon in rev. 1.42 and 1.43, and one by me (based on patches submitted by Graham Wheeler) in rev. 1.44 and 1.45. I haven't heard any complaints about the inetd bug lately, so I'll tentatively postulate that I succeeded. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 05:37:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA24312 for freebsd-current-outgoing; Fri, 8 Jan 1999 05:37:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA24300 for ; Fri, 8 Jan 1999 05:37:51 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 24506 invoked by uid 1001); 8 Jan 1999 13:37:14 +0000 (GMT) To: tcobb@staff.circle.net Cc: freebsd-current@FreeBSD.ORG Subject: Re: 3.0-19981121-SNAP In-Reply-To: Your message of "Fri, 8 Jan 1999 07:34:03 -0500 " References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Fri, 08 Jan 1999 14:37:14 +0100 Message-ID: <24504.915802634@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've been successfully using the 11/21/98 SNAP on 10+ machines, > but unfortunately did not download and save an archived copy of this > SNAP. Now, suddenly, it appears that ftp://current.freebsd.org has deleted > it (and everything else from 1998!). > > Does anyone know of another location to retrieve a copy of this SNAP? No hits using ftpsearch. But the 19981123 SNAP is available at: ftp://trane.uninett.no/pub/FreeBSD/3.0-19981123-SNAP/ and that may be as close as you'll get. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 05:39:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA24467 for freebsd-current-outgoing; Fri, 8 Jan 1999 05:39:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.206.244]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA24459 for ; Fri, 8 Jan 1999 05:39:08 -0800 (PST) (envelope-from andyf@speednet.com.au) Received: from backup.zippynet.iol.net.au (backup.zippynet.iol.net.au [172.22.2.4]) by backup.af.speednet.com.au (8.9.1/8.9.1) with ESMTP id AAA07708 for ; Sat, 9 Jan 1999 00:38:31 +1100 (EST) Date: Sat, 9 Jan 1999 00:38:31 +1100 (EST) From: Andy Farkas X-Sender: andyf@backup.zippynet.iol.net.au To: freebsd-current@FreeBSD.ORG Subject: Re: beep, beep, beep! 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, 8 Jan 1999, Andy Farkas wrote: > Shouldn't the new boot code be beeping at us? :) > Seeing as how I mentioned it, here is my effort: patch to /usr/src/sys/boot/common/boot.c: --- common/boot.c 1999/01/08 08:23:01 1.1 +++ common/boot.c 1999/01/08 13:13:34 @@ -23,7 +23,7 @@ * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. * - * $Id: boot.c,v 1.1 1999/01/08 08:23:01 root Exp $ + * $Id: boot.c,v 1.5 1999/01/08 13:12:59 root Exp root $ */ /* @@ -155,11 +155,22 @@ void autoboot_maybe() { - char *cp; + unsigned int beeps = 3; + char *cp, *ep; cp = getenv("autoboot_delay"); - if ((autoboot_tried == 0) && ((cp == NULL) || strcasecmp(cp, "NO"))) + if ((autoboot_tried == 0) && ((cp == NULL) || strcasecmp(cp, "NO"))) { + if ((cp = getenv("autoboot_beeps"))) { + beeps = strtol(cp, &ep, 0); + if ((cp == ep) || (beeps > 3)) + beeps = 3; + } + + while (beeps--) + printf("\a"); + autoboot(-1, NULL); /* try to boot automatically */ + } } int [end patch] -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speed Internet Services http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 05:39:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA24501 for freebsd-current-outgoing; Fri, 8 Jan 1999 05:39:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA24495 for ; Fri, 8 Jan 1999 05:39:41 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id OAA29693; Fri, 8 Jan 1999 14:38:40 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id OAA03865; Fri, 8 Jan 1999 14:38:39 +0100 (MET) Message-ID: <19990108143839.G348@follo.net> Date: Fri, 8 Jan 1999 14:38:39 +0100 From: Eivind Eklund To: "T.D. Brace" , freebsd-current@FreeBSD.ORG Subject: Re: inetd problem References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from T.D. Brace on Thu, Jan 07, 1999 at 05:01:42PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 07, 1999 at 05:01:42PM -0500, T.D. Brace wrote: > > Hello, > > Can anyone tell me if the inetd realloc (and other) problems have been > fixed yet? Searching Deja News shows conflicting reports. I checked > the current diffs, and built version 1.46 - is this a safe version to > use? It's been running on my local workstation for a few days now, but > it really doesn't have any load on it. I'd like to copy it up to our > webservers, but thought I would ask first. 1.46 should be safe. It has a fix for the 'realloc' problem that does not rely on undocumented behaviour, and AFAIK works quite well. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 05:41:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA24869 for freebsd-current-outgoing; Fri, 8 Jan 1999 05:41:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA24864 for ; Fri, 8 Jan 1999 05:41:32 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.1/8.9.1) id OAA97223; Fri, 8 Jan 1999 14:40:45 +0100 (CET) (envelope-from des) To: Luigi Rizzo Cc: sos@sos.freebsd.dk (Søren Schmidt), obrien@NUXI.com, andyf@speednet.com.au, freebsd-current@FreeBSD.ORG Subject: Re: beep, beep, beep! References: <199901080523.GAA10518@labinfo.iet.unipi.it> From: Dag-Erling Smorgrav Date: 08 Jan 1999 14:40:44 +0100 In-Reply-To: Luigi Rizzo's message of "Fri, 8 Jan 1999 06:23:12 +0100 (MET)" Message-ID: Lines: 20 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luigi Rizzo writes: > > It seems David O'Brien wrote: > > > > > Shouldn't the new boot code be beeping at us? :) > > > > Also Also, , make make it it optional optional :) :) > > > The beeps are for our un-sighted users. > > Yeah, but does it have to be 3 of them, we wouldn't want the > > rest of us to go un-hearing now would we :) > and i also commented to Jordan, 3 beeps like those mean you cannot > do night installs at home without waking up the rest of the family. Is that a widespread problem? :) On a more serious note, I'd love it if Somebody (tm) patched the kernel to beep a couple of times after shutting down (when it displays the "press any key to reboot" prompt). Useful when doing maintenance on headless machines. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 05:44:53 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA25128 for freebsd-current-outgoing; Fri, 8 Jan 1999 05:44:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA25123 for ; Fri, 8 Jan 1999 05:44:50 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id WAA04995; Fri, 8 Jan 1999 22:43:20 +0900 (JST) Message-ID: <3695F491.130B71D7@newsguy.com> Date: Fri, 08 Jan 1999 21:05:37 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Mike Zanker CC: current@FreeBSD.ORG Subject: Re: Moving from 2.2.8-STABLE to ELF 3.0-CURRENT (success) References: <4.1.19990108091416.00a61e30@aire.open.ac.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Zanker wrote: > > Anyway, I was getting a bit bored following the 2.2 branch - there were > only a few source changes now and then and I wasn't having any problems > "making the world". I decided that it was time to move to 3.0 and ELF so I > developed a plan of action, taking things one step at a time. I do not recall "being bored and not having any problems" as one of the reasons listed in the handbook for going current... maybe we should add it? :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com "Heart like a Gabriel, pure and white as ivory, soul like a lucifer, black and cold as a piece of lead." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 05:45:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA25225 for freebsd-current-outgoing; Fri, 8 Jan 1999 05:45:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.206.244]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA25213 for ; Fri, 8 Jan 1999 05:45:31 -0800 (PST) (envelope-from andyf@speednet.com.au) Received: from backup.zippynet.iol.net.au (backup.zippynet.iol.net.au [172.22.2.4]) by backup.af.speednet.com.au (8.9.1/8.9.1) with ESMTP id AAA07744 for ; Sat, 9 Jan 1999 00:44:56 +1100 (EST) Date: Sat, 9 Jan 1999 00:44:56 +1100 (EST) From: Andy Farkas X-Sender: andyf@backup.zippynet.iol.net.au To: freebsd-current@FreeBSD.ORG Subject: Re: beep, beep, beep! 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 > Seeing as how I mentioned it, here is my effort: > Forgot the instructions: Add to your /boot/boot.conf 'set autoboot_beeps=[0-3]' -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speed Internet Services http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 05:48:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA25564 for freebsd-current-outgoing; Fri, 8 Jan 1999 05:48:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (slip139-92-122-82.joh.za.ibm.net [139.92.122.82]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA25553 for ; Fri, 8 Jan 1999 05:48:39 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id PAA01890; Fri, 8 Jan 1999 15:44:54 +0200 (SAT) From: Robert Nordier Message-Id: <199901081344.PAA01890@ceia.nordier.com> Subject: Re: can't boot from CD and floppy after make release In-Reply-To: from Andrzej Bialecki at "Jan 8, 99 02:15:14 pm" To: abial@nask.pl (Andrzej Bialecki) Date: Fri, 8 Jan 1999 15:44:51 +0200 (SAT) Cc: jkh@zippy.cdrom.com, dillon@apollo.backplane.com, mike@smith.net.au, andreas@klemm.gtn.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki wrote: > On Thu, 7 Jan 1999, Jordan K. Hubbard wrote: > > > > Jordan, if gzip works you could have just said so in the first place! > > > > Sorry, I thought that characteristic of the new boot blocks was already > > common knowledge. > > Bear in mind, though, that you'll need additional 100kB of place on the > floppy (that's approx. the difference between kzip stubs and the > /boot/loader). > > In this light it makes sense to do what rnordier suggested - namely, to > write a small BTX application which would only be able to load kernel.gz. > I _may_ embark on such a project if I have some docs about how to use BTX. If it's likely to be used, I don't mind writing this. It might make a good example application for the BTX docs I'm trying to write. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 05:54:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA26350 for freebsd-current-outgoing; Fri, 8 Jan 1999 05:54:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA26345; Fri, 8 Jan 1999 05:54:09 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id IAA09240; Fri, 8 Jan 1999 08:53:27 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA05380; Fri, 8 Jan 1999 08:53:26 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id IAA39632; Fri, 8 Jan 1999 08:53:26 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199901081353.IAA39632@bb01f39.unx.sas.com> Subject: Re: Bug in make affecting release crunchs In-Reply-To: <199901081218.HAA02256@lakes.dignus.com> from Thomas David Rivers at "Jan 8, 1999 7:18:50 am" To: rivers@dignus.com (Thomas David Rivers) Date: Fri, 8 Jan 1999 08:53:26 -0500 (EST) Cc: jkh@zippy.cdrom.com, jwd@unx.sas.com, freebsd-bugs@FreeBSD.ORG, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gee... Silly me... Dave is correct: /usr/src/usr.bin/make/parse.c and the diff again: --------------------------------------------------------------- --- /usr/src/usr.bin/make/parse.c.orig Sun May 31 02:23:33 1998 +++ /usr/src/usr.bin/make/parse.c Fri Jan 8 03:05:23 1999 @@ -1412,8 +1412,10 @@ default: #ifdef SUNSHCMD while (*opc != ':') - if (--opc < line) + if (--opc < line) { + ++opc; break; + } if (strncmp(opc, ":sh", 3) == 0) { type = VAR_SHELL; --------------------------------------------------------------- > > > Basically, Parse_IsVar() in parse.c contains the following > > > code snippet: > > > > I can't parse this since I don't even know what directory you're in or > > what file you're talking about. parse.c, yes. WHAT parse.c? :-) > > > > - Jordan > > Jordan - > > I believe he's talking about the make(1) program, > in particular, /usr/src/usr.bin/make/parse.c > > - Dave Rivers - > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 07:22:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA05699 for freebsd-current-outgoing; Fri, 8 Jan 1999 07:22:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA05694 for ; Fri, 8 Jan 1999 07:22:22 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.1/8.9.1) id JAA18484; Fri, 8 Jan 1999 09:21:48 -0600 (CST) (envelope-from dick) Date: Fri, 8 Jan 1999 09:21:48 -0600 From: "Richard Seaman, Jr." To: Tony Finch Cc: current@FreeBSD.ORG Subject: Re: Squid + linuxthreads in action Message-ID: <19990108092148.A377@tar.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Tony Finch on Wed, Jan 06, 1999 at 08:04:00PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 06, 1999 at 08:04:00PM +0000, Tony Finch wrote: > We've been trying out Squid compiled to use async-io with linuxthreads > on FreeBSD-current today. It required a bit of fiddling to work around > incorrect assumptions in Squid's build and configuration stuff: > > To CFLAGS I added: -D_THREAD_SAFE -DLINUXTHREADS -I/usr/local/include > To XTRA_LIBS I added: -kthread > > I modified src/aiops.c and src/main.c to test for _SQUID_LINUX_THREADS_ > instead of (defined(_SQUID_LINUX_) && USE_ASYNC_IO) and altered > include/config.h.in to define _SQUID_LINUX_THREADS_ in the appropriate > situations. > > After running `configure` I had to edit src/Makefile to remove > -pthread from LDFLAGS. (It would be better for the long term to alter > configure.in and rebuild configure, but...) > > Squid then compiles and runs OK, apart from a few things: > > When the parent Squid process shuts down it leaves behind a pile of > orphan processes (the async-io handler threads). A glance at the aio > code reveals that Squid expects the pthread library to kill them -- > they just loop indefinitely. They also keep the listen socket open, so > the RunCache script can't restart Squid :-( Ok. I finally got squid compiled and running. When I do any of the following: squid -k shutdown squid -k kill squid -k interrupt all the squid processes get killed. After a short time squid restarts (I assume this is RunCache that does this). I seem to get 18 processes (threads) going. When you say you get orphan processes, is this what you're doing? -- Richard Seamman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 07:33:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA07438 for freebsd-current-outgoing; Fri, 8 Jan 1999 07:33:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mortar.carlson.com (mortar.carlson.com [208.240.12.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA07433 for ; Fri, 8 Jan 1999 07:33:19 -0800 (PST) (envelope-from veldy@visi.com) Received: from mortar.carlson.com (root@localhost) by mortar.carlson.com with ESMTP id JAA01728; Fri, 8 Jan 1999 09:32:11 -0600 (CST) Received: from w142844 ([172.25.99.35]) by mortar.carlson.com with SMTP id JAA01724; Fri, 8 Jan 1999 09:32:04 -0600 (CST) Message-ID: <003a01be3b1c$250f5f00$236319ac@w142844.carlson.com> From: "Thomas T. Veldhouse" To: "=?iso-8859-1?B?Sm9z6SBNqiBBbGNhaWRl?=" Cc: "FreeBSD-Current" Subject: Re: SOFTUPDATES Date: Fri, 8 Jan 1999 09:32:36 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There is a nice readme file in the contrib directory mentioned in LINT. Follow the directions in that instead. It states to link the files instead of copy them. That makes more sense to me because when a CVSUP takes place, your source is automatically updated (a copy would still be old). Tom Veldhouse veldy@visi.com -----Original Message----- From: José Mª Alcaide To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Date: Friday, January 08, 1999 4:45 AM Subject: Re: SOFTUPDATES >Matthew Dillon wrote: >> >> Softupdates basically gives you the advantage of an async mount without >> any of the risks. It's actually better then that - it can unwind commits >> to disk before they occur ( e.g. if you create a temporary file and then >> delete it very soon after ). Softupdates basically guarentees disk >> consistancy in the face of a crash. >> >> It's pretty well debugged as it stands -- I'd call it production. I don't >> think the problem the person who was posting and calling a softupdates >> is actually a softupdates problem. I've been using it solidly for a while >> and BEST has been using it on their nntp box ( a very heavily loaded box ) >> for a few months. >> > >The main problem I see with softupdates is the lack of information. >I read the tunefs(8) manpage and I found the "-n" option. However, >there is no mention to the need of the SOFTUPDATES kernel option >(I bumped into it while reading LINT). > >I think that a little tutorial about what softupdates is, and how >to turn it on, should be very useful for many users (like me :-) ). > >-- JMA >----------------------------------------------------------------------- >José Mª Alcaide | mailto:jose@we.lc.ehu.es >Universidad del País Vasco | http://www.we.lc.ehu.es/~jose >Dpto. de Electricidad y Electrónica | >Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 >48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139 >----------------------------------------------------------------------- > "Go ahead... make my day." - H. Callahan > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 07:40:50 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08535 for freebsd-current-outgoing; Fri, 8 Jan 1999 07:40:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08530 for ; Fri, 8 Jan 1999 07:40:48 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id AAA17077; Sat, 9 Jan 1999 00:40:08 +0900 (JST) Message-ID: <36960CF0.D4F2A1C1@newsguy.com> Date: Fri, 08 Jan 1999 22:49:36 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Sheldon Hearn , current@FreeBSD.ORG Subject: Re: Enabling Softupdates with symlinks? References: <17875.915798021@axl.noc.iafrica.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > > Is it not feasible to use symbolic links to the files in the softupdates > directory instead? i.e.: > > cd /sys/ufs/ffs > ln -s /usr/src/contrib/sys/softupdates/softdep.h > ln -s /usr/src/contrib/sys/softupdates/ffs_softdep.h > > This would require less thinking later on. Possible and, even, recommended (at least it was recommended to me by Mike Smith). Guess it would take the fun out of it, though... :-) (Hey, who said he was upgrading to -current because he wasn't having any problems with -stable, and was bored? :) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com "Heart like a Gabriel, pure and white as ivory, soul like a lucifer, black and cold as a piece of lead." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 07:55:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA09854 for freebsd-current-outgoing; Fri, 8 Jan 1999 07:55:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA09849 for ; Fri, 8 Jan 1999 07:55:35 -0800 (PST) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.1/8.9.1) id HAA07883 for freebsd-current@FreeBSD.ORG; Fri, 8 Jan 1999 07:54:06 -0800 (PST) (envelope-from dhw) Date: Fri, 8 Jan 1999 07:54:06 -0800 (PST) From: David Wolfskill Message-Id: <199901081554.HAA07883@pau-amma.whistle.com> Subject: Re: inetd problem Cc: freebsd-current@FreeBSD.ORG In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From: Dag-Erling Smorgrav >Date: 08 Jan 1999 14:36:16 +0100 >No. People are constantly confused over this issue. There is (was) a >bug in inetd related to the way it handles signals, which caused it to >output "junk pointer: too low to make sense" (or sometimes "too high >to make sense") when under heavy load. It is not the same bug as the >dying daemons bug. There have been two attemps to fix the inetd bug: >one by Matt Dillon in rev. 1.42 and 1.43, and one by me (based on >patches submitted by Graham Wheeler) in rev. 1.44 and 1.45. I haven't >heard any complaints about the inetd bug lately, so I'll tentatively >postulate that I succeeded. One of my colleagues (Doug Ambrisko) has a desktop machine which has been exhibiting the symptom as recently as 1.43, thankss to the combination of things he does with the (abused?) machine and the load I put on it in the wee small hours of the morning using amanda (driving dump) to back it up. We were closed for the week between Christmas & New Year's (i.e., the first 8 days of Christmas), and he didn't get back to the office 'til the following Tuesday. I ran backups that week anyhow, but that wasn't enough to trigger the symptoms. The latest recurrence of the problem was yesterday (using the 1.43 rev. of the code); he said he would be applying DES' patches; I *thought* he meant that afternoon. Based on the results from this morning's backups, it looks as if he may have neglected to re-start inetd; I'll chat with him once he gets in. (Foggy here this AM, so he may be delayed getting in.) Historically, the failures have taken from 3-7 days to recur under the load mentioned above. david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 08:13:22 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA12660 for freebsd-current-outgoing; Fri, 8 Jan 1999 08:13:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles244.castles.com [208.214.165.244]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA12654 for ; Fri, 8 Jan 1999 08:13:20 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id IAA02956; Fri, 8 Jan 1999 08:08:38 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901081608.IAA02956@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Robert Nordier cc: abial@nask.pl (Andrzej Bialecki), jkh@zippy.cdrom.com, dillon@apollo.backplane.com, mike@smith.net.au, andreas@klemm.gtn.com, current@FreeBSD.ORG Subject: Re: can't boot from CD and floppy after make release In-reply-to: Your message of "Sat, 08 Jan 1999 15:44:51 +0200." <199901081344.PAA01890@ceia.nordier.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 Jan 1999 08:08:38 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Bear in mind, though, that you'll need additional 100kB of place on the > > floppy (that's approx. the difference between kzip stubs and the > > /boot/loader). > > > > In this light it makes sense to do what rnordier suggested - namely, to > > write a small BTX application which would only be able to load kernel.gz. > > I _may_ embark on such a project if I have some docs about how to use BTX. > > If it's likely to be used, I don't mind writing this. It might make a > good example application for the BTX docs I'm trying to write. It'd definitely be useful for the PicoBSD people, and anyone else that didn't need the loader's functionality. I'd also be interested in knowing if you have any compression/decompression tools suitable for use with BTX eg. to compress the application data/expand it when BTX relocates. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 08:34:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16011 for freebsd-current-outgoing; Fri, 8 Jan 1999 08:34:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chiark.greenend.org.uk (chiark.greenend.org.uk [195.224.76.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA15995 for ; Fri, 8 Jan 1999 08:34:28 -0800 (PST) (envelope-from fanf@chiark.greenend.org.uk) Received: from fanf by chiark.greenend.org.uk with local (Exim 2.02 #1) id 0zyerB-0005ey-00 (Debian); Fri, 8 Jan 1999 16:33:53 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <13974.13169.69838.513388@chiark.greenend.org.uk> Date: Fri, 8 Jan 1999 16:33:53 +0000 (GMT) From: Tony Finch To: "Richard Seaman, Jr." cc: current@FreeBSD.ORG Subject: Re: Squid + linuxthreads in action In-Reply-To: <19990108092148.A377@tar.com> References: <19990108092148.A377@tar.com> X-Mailer: VM 6.47 under Emacs 19.34.1 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Richard Seaman, Jr. writes: > Tony Finch wrote: > > > > We've been trying out Squid compiled to use async-io with linuxthreads > > on FreeBSD-current today. > > > > When the parent Squid process shuts down it leaves behind a pile of > > orphan processes (the async-io handler threads). A glance at the aio > > code reveals that Squid expects the pthread library to kill them -- > > they just loop indefinitely. They also keep the listen socket open, so > > the RunCache script can't restart Squid :-( > > Ok. I finally got squid compiled and running. When I do any of the > following: > > squid -k shutdown > squid -k kill > squid -k interrupt > > all the squid processes get killed. After a short time squid > restarts (I assume this is RunCache that does this). I seem > to get 18 processes (threads) going. That sounds right -- the main process, a management thread, and 16 IO pumps. > When you say you get orphan processes, is this what you're > doing? Yes. Or at least is was, but I can't reproduce it now. Sorry for causing trouble :-( Tony. -- f.a.n.finch fanf@demon.net dot@dotat.at To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 08:38:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16406 for freebsd-current-outgoing; Fri, 8 Jan 1999 08:38:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles244.castles.com [208.214.165.244]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA16386 for ; Fri, 8 Jan 1999 08:38:01 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id IAA03132; Fri, 8 Jan 1999 08:34:32 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901081634.IAA03132@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Kazutaka YOKOTA cc: current@FreeBSD.ORG Subject: Re: syscons update - when? In-reply-to: Your message of "Fri, 08 Jan 1999 21:34:33 +0900." <199901081234.VAA13287@zodiac.mech.utsunomiya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 Jan 1999 08:34:31 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ok, here is my plan. This all looks pretty good. > Stage 0. ------------------------------------------------------ > > This weekend I will commit the following new files. ... > dev/fb/fb.c > dev/fb/fbreg.c > dev/fb/splash.c > dev/fb/splashreg.c > dev/fb/vgareg.c Do we want to go ahead with the splash separate from the screensaver architecture? I guess it costs us nothing to back it out. > The new drivers are not yet activated. The users will be still using > existing syscons at this point. > > Stage 1. ------------------------------------------------------ > > On Sunday evening, the new keyboard driver will be activated. ... > The users are REQUIRED to update their kernel configuration files > to include the new keyboard driver. I will send out "HEADS UP" on > this. ... > Stage 2. ------------------------------------------------------ > > On 14, the new video card driver (and splash screen) will be > activated. ... > The users are REQUIRED to update their kernel configuration files to > include the new driver, again. I will send out "HEADS UP" on this > too. Is there a good reason not to group these two change sets together? I realise that they separate neatly, but it would seem from here that you could probably just group them together and be done with it. Apart from that: Yay! Go Kazu! -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 08:38:52 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16500 for freebsd-current-outgoing; Fri, 8 Jan 1999 08:38:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles244.castles.com [208.214.165.244]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA16492 for ; Fri, 8 Jan 1999 08:38:50 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id IAA03149; Fri, 8 Jan 1999 08:35:06 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901081635.IAA03149@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: tarkhil@asteroid.svib.ru cc: current@FreeBSD.ORG Subject: Re: Problems with 486SX In-reply-to: Your message of "Fri, 08 Jan 1999 16:11:42 +0300." <199901081311.QAA09080@minas-tirith.pol.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Fri, 08 Jan 1999 08:35:05 -0800 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id IAA16495 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello! > > I've tried to install 3.0-RELEASE on HP's 486SX. I've compiled (on much better > machine) kernel with math emulator turned on, and tried to run. You will have to update; 3.0-RELEASE code will not run on systems with no FPU. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 08:40:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16754 for freebsd-current-outgoing; Fri, 8 Jan 1999 08:40:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles244.castles.com [208.214.165.244]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA16726 for ; Fri, 8 Jan 1999 08:40:12 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id IAA03169; Fri, 8 Jan 1999 08:36:42 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901081636.IAA03169@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andy Farkas cc: freebsd-current@FreeBSD.ORG Subject: Re: beep, beep, beep! In-reply-to: Your message of "Sat, 09 Jan 1999 00:38:31 +1100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 Jan 1999 08:36:42 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Fri, 8 Jan 1999, Andy Farkas wrote: > > > Shouldn't the new boot code be beeping at us? :) > > > > Seeing as how I mentioned it, here is my effort: Thanks, but it would be much easier just to put echo ^G^G^G in boot.conf on the install floppy, and fix the video console driver to understand ^G -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 08:44:22 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA17338 for freebsd-current-outgoing; Fri, 8 Jan 1999 08:44:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles244.castles.com [208.214.165.244]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA17329 for ; Fri, 8 Jan 1999 08:44:20 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id IAA03185; Fri, 8 Jan 1999 08:37:25 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901081637.IAA03185@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Dag-Erling Smorgrav cc: Luigi Rizzo , sos@sos.freebsd.dk (=?iso-8859-1?Q?S=F8ren?= Schmidt), obrien@NUXI.com, andyf@speednet.com.au, freebsd-current@FreeBSD.ORG Subject: Re: beep, beep, beep! In-reply-to: Your message of "08 Jan 1999 14:40:44 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Fri, 08 Jan 1999 08:37:24 -0800 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id IAA17330 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On a more serious note, I'd love it if Somebody (tm) patched the > kernel to beep a couple of times after shutting down (when it displays > the "press any key to reboot" prompt). Useful when doing maintenance > on headless machines. Add an at_shutdown hook and a sysctl to tune it. Should only take a couple of minutes. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 08:45:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA17622 for freebsd-current-outgoing; Fri, 8 Jan 1999 08:45:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mortar.carlson.com (mortar.carlson.com [208.240.12.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA17616 for ; Fri, 8 Jan 1999 08:45:54 -0800 (PST) (envelope-from veldy@visi.com) Received: from mortar.carlson.com (root@localhost) by mortar.carlson.com with ESMTP id KAA02121 for ; Fri, 8 Jan 1999 10:44:36 -0600 (CST) Received: from w142844 ([172.25.99.35]) by mortar.carlson.com with SMTP id KAA02117 for ; Fri, 8 Jan 1999 10:44:36 -0600 (CST) Message-ID: <005801be3b26$43afbfe0$236319ac@w142844.carlson.com> From: "Thomas T. Veldhouse" To: "FreeBSD-Current" Subject: CVSUP - Source from 01/05/1999? Date: Fri, 8 Jan 1999 10:45:13 -0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0055_01BE3AF3.F8BB21F0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0055_01BE3AF3.F8BB21F0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, I am trying to pull down the source from 1-5-1999 using CVSUP and my = supfile has the following in it: # Defaults that apply to all the collections *default host=3Dcvsup.FreeBSD.org *default base=3D/usr *default prefix=3D/usr *default release=3Dcvs tag=3D. *default date=3D99.01.05.03.00.00 *default delete use-rel-suffix It apears to still be pulling the current (1-8-99) source code. I have = tried changing the tag=3D3.0.0-19990105-SNAP to no avail. I was = wondering why CVSUP is pulling the current code when I gave it the date = according to the man file. Does anybody know what I am doing wrong? Tom Veldhouse veldy@visi.com ------=_NextPart_000_0055_01BE3AF3.F8BB21F0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello,
 
    I am trying to = pull down the=20 source from 1-5-1999 using CVSUP and my supfile has the following in=20 it:
 
# Defaults that apply to all the=20 collections
*default host=3Dcvsup.FreeBSD.org
*default = base=3D/usr
*default=20 prefix=3D/usr
*default release=3Dcvs     =20 tag=3D.
*default date=3D99.01.05.03.00.00
*default delete=20 use-rel-suffix
 
It apears to still be pulling the = current=20 (1-8-99) source code.  I have tried changing the = tag=3D3.0.0-19990105-SNAP to=20 no avail.  I was wondering why CVSUP is pulling the current code = when I=20 gave it the date according to the man file.  Does anybody know what = I am=20 doing wrong?
 
Tom Veldhouse
veldy@visi.com
------=_NextPart_000_0055_01BE3AF3.F8BB21F0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 08:56:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA19200 for freebsd-current-outgoing; Fri, 8 Jan 1999 08:56:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.rdc1.nj.home.com (ha1.rdc1.nj.home.com [24.3.128.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA19190 for ; Fri, 8 Jan 1999 08:56:18 -0800 (PST) (envelope-from damascus@eden.rutgers.edu) Received: from athena ([24.3.219.36]) by mail.rdc1.nj.home.com (InterMail v4.0 201-221-107) with SMTP id <19990108165548.OTKZ2583.mail.rdc1.nj.home.com@athena>; Fri, 8 Jan 1999 08:55:48 -0800 Message-Id: <4.1.19990108113447.00b8d220@email.eden.rutgers.edu> X-Sender: damascus@email.eden.rutgers.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Fri, 08 Jan 1999 11:37:48 -0500 To: Alex Le Heux , freebsd-current@FreeBSD.ORG From: Carroll Kong Subject: Re: freeze when trying to mount FAT32 In-Reply-To: <3695694C.309A63E4@funk.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 03:11 AM 1/8/99 +0100, Alex Le Heux wrote: >Hi, > >When I try "mount -t msdos /dev/wd0s1 /msdos" on a FAT32 filesystem, it >sits there for about 10 seconds, after which the system freezes. No >response, no ddb, nothing. > >Even when I ^C it after a second or so, the system still freezes about >10 seconds later. (just enough time to type sync :-) > >This is on a current system that I cvsupped about 4 hours ago. > >Alex > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message This happened to me a few times in current. Seemed to happen to me only if I accidentally typed in mount /dev/wd0s1 /msdos first. (this was not fat32.. but still i got the lock up). And then i typed in mount -t msdos /dev/wd0s1 /msdos.. and it froze. hardlock. mount_msdos /dev/wd0s1 /msdos the first time always seems to work for me. -Carroll Kong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 09:03:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20478 for freebsd-current-outgoing; Fri, 8 Jan 1999 09:03:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from biceps.gymnet.com (biceps.gymnet.com [204.216.82.50]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA20471 for ; Fri, 8 Jan 1999 09:03:53 -0800 (PST) (envelope-from rwl@gymnet.com) Message-Id: <199901081703.JAA20471@hub.freebsd.org> Received: (qmail 4281 invoked from network); 8 Jan 1999 17:02:56 -0000 Received: from triceps.gymnet.com (HELO triceps) (204.216.82.51) by biceps.gymnet.com with SMTP; 8 Jan 1999 17:02:56 -0000 From: "Robert Luce" To: "freebsd-current@freebsd.org" Date: Fri, 08 Jan 1999 09:03:17 -0800 Reply-To: "Robert Luce" X-Mailer: PMMail 98 Professional (2.01.1600) For Windows 98 (4.10.1998) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: boot single with new loader? Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id JAA20472 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a wonderful all elf system now, upgraded the boot blocks, added a /boot/boot.conf to allow it to locate my SB16-PNP and all works just great EXCEPT I cannot figure out how to boot in single user mode so I can enable softupdates. Hitting at the first prompt gives me the old boot help and -s just boots normally. If I drop into the loader prompt then I can do lots of other neat stuff but can't seem to run tunefs. Any pointers would certainly help! ---- Robert Luce "Il faut supporter deux ou trois chenilles System/News Administrator si on veut connaŒtre les papillons.." - Antoine de Saint-Exup‚ry Finger rwl@gymnet.com for PGP Public Key Block To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 09:08:41 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21046 for freebsd-current-outgoing; Fri, 8 Jan 1999 09:08:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21036 for ; Fri, 8 Jan 1999 09:08:35 -0800 (PST) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (lxpxds.lx.ehu.es [158.227.99.196]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id SAA10341; Fri, 8 Jan 1999 18:07:32 +0100 (MET) Message-ID: <36963B51.9932270A@we.lc.ehu.es> Date: Fri, 08 Jan 1999 18:07:29 +0100 From: "José Mª Alcaide" Organization: Universidad del País Vasco - Dept. Electricidad y Electrónica X-Mailer: Mozilla 4.07 [en] (X11; U; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: "Thomas T. Veldhouse" CC: FreeBSD-Current Subject: Re: SOFTUPDATES References: <003a01be3b1c$250f5f00$236319ac@w142844.carlson.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 Thomas T. Veldhouse wrote: > > There is a nice readme file in the contrib directory mentioned in LINT. > Follow the directions in that instead. It states to link the files instead > of copy them. That makes more sense to me because when a CVSUP takes place, > your source is automatically updated (a copy would still be old). > This is exactly what I'm referring to. That README (nice, indeed) is hidden into the /usr/src tree. I think that it should be transformed in a tutorial, handbook chapter, or perhaps a FAQ (I mean, the answer to a new FAQ :-) ). BTW, I have enabled softupdates and it works fine. No problems. -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | http://www.we.lc.ehu.es/~jose Dpto. de Electricidad y Electrónica | Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139 ----------------------------------------------------------------------- "Go ahead... make my day." - H. Callahan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 09:19:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22258 for freebsd-current-outgoing; Fri, 8 Jan 1999 09:19:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22253 for ; Fri, 8 Jan 1999 09:19:48 -0800 (PST) (envelope-from dbushong@CSUA.Berkeley.EDU) Received: (from dbushong@localhost) by soda.CSUA.Berkeley.EDU (8.8.8/) id JAA14533; Fri, 8 Jan 1999 09:19:16 -0800 (PST) env-from (dbushong) From: dbushong@CSUA.Berkeley.EDU (David Bushong) Message-Id: <199901081719.JAA14533@soda.CSUA.Berkeley.EDU> Subject: Re: boot single with new loader? In-Reply-To: <199901081703.JAA20471@hub.freebsd.org> from Robert Luce at "Jan 8, 99 09:03:17 am" To: rwl@gymnet.com Date: Fri, 8 Jan 1999 09:19:16 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=KOI8-R X-MIME-Autoconverted: from 8bit to quoted-printable by soda.CSUA.Berkeley.EDU id JAA14533 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id JAA22254 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You can't enable soft updates from single user; the disk has to be completely unmounted. Either boot from a floppy, and run it on the hard disk, or do what I did (being to lazy to make a floppy), and boot the machine; run tunefs on the live disk, type sync 5 times, and smack the power switch. After all, it's not actually that the disk must be unmounted; it's that the act of unmounting it would reset the tunefs flag in the superblock; erasing what you did. If you were to set it on a mounted filesystem and reboot normally, it would unmount the fs normally, undoing your work. As for how to boot into single user; minimizing the danger of powercycling the machine; I don't know, sorry; I haven't tried it since I switched to the new boot blocks. --David Bushong > I have a wonderful all elf system now, upgraded the boot blocks, > added a /boot/boot.conf to allow it to locate my SB16-PNP and all > works just great EXCEPT I cannot figure out how to boot in single > user mode so I can enable softupdates. > > Hitting at the first prompt gives me the old boot help > and -s just boots normally. If I drop into the loader prompt then > I can do lots of other neat stuff but can't seem to run tunefs. > Any pointers would certainly help! > > > ---- > Robert Luce "Il faut supporter deux ou trois chenilles > System/News Administrator si on veut connaŒtre les papillons.." > - Antoine de Saint-Exup‚ry > Finger rwl@gymnet.com for PGP Public Key Block > > > > 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 Jan 8 09:31:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24273 for freebsd-current-outgoing; Fri, 8 Jan 1999 09:31:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mortar.carlson.com (mortar.carlson.com [208.240.12.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA24268 for ; Fri, 8 Jan 1999 09:30:58 -0800 (PST) (envelope-from veldy@visi.com) Received: from mortar.carlson.com (root@localhost) by mortar.carlson.com with ESMTP id LAA02384; Fri, 8 Jan 1999 11:29:46 -0600 (CST) Received: from w142844 ([172.25.99.35]) by mortar.carlson.com with SMTP id LAA02380; Fri, 8 Jan 1999 11:29:41 -0600 (CST) Message-ID: <009c01be3b2c$92e60320$236319ac@w142844.carlson.com> From: "Thomas T. Veldhouse" To: "David Bushong" , Cc: Subject: Re: boot single with new loader? Date: Fri, 8 Jan 1999 11:30:19 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just dropped to single-user (shutdown now) and simply unmounted the slices except for root. I then ran tunefs on each of the unmounted slices. I left the root slice as sync. I figured it was safer, and it wasn't that important to me to have that particular slice on softupdates anyway. Tom Veldhouse veldy@visi.com -----Original Message----- From: David Bushong To: rwl@gymnet.com Cc: freebsd-current@FreeBSD.ORG Date: Friday, January 08, 1999 11:19 AM Subject: Re: boot single with new loader? >You can't enable soft updates from single user; the disk has to be completely >unmounted. Yes you can ... umount /usr ... umount /var ... etc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 09:45:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA26519 for freebsd-current-outgoing; Fri, 8 Jan 1999 09:45:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from h24-64-221-247.gv.wave.shaw.ca (h24-64-221-247.gv.wave.shaw.ca [24.64.221.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA26512 for ; Fri, 8 Jan 1999 09:45:48 -0800 (PST) (envelope-from jake@h24-64-221-247.gv.wave.shaw.ca) Received: from h24-64-221-247.gv.wave.shaw.ca (localhost [127.0.0.1]) by h24-64-221-247.gv.wave.shaw.ca (8.9.1/8.9.1) with ESMTP id JAA78390 for ; Fri, 8 Jan 1999 09:45:14 -0800 (PST) (envelope-from jake@h24-64-221-247.gv.wave.shaw.ca) Message-Id: <199901081745.JAA78390@h24-64-221-247.gv.wave.shaw.ca> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: Re: boot single with new loader? In-reply-to: Your message of "Fri, 08 Jan 1999 11:30:19 CST." <009c01be3b2c$92e60320$236319ac@w142844.carlson.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 Jan 1999 09:45:13 -0800 From: Jake Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yes you can ... umount /usr ... umount /var ... etc > If you copy tunefs to /usr or something, you can boot off the install floppy, use the fixit floppy to get a shell, and the run it on your unmounted root. A picobsd disk also works well. I've even got softupdates enabled on my vinum volume :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 09:45:59 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA26547 for freebsd-current-outgoing; Fri, 8 Jan 1999 09:45:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA26532 for ; Fri, 8 Jan 1999 09:45:56 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id JAA73771; Fri, 8 Jan 1999 09:44:30 -0800 (PST) To: Robert Nordier cc: abial@nask.pl (Andrzej Bialecki), dillon@apollo.backplane.com, mike@smith.net.au, andreas@klemm.gtn.com, current@FreeBSD.ORG Subject: Re: can't boot from CD and floppy after make release In-reply-to: Your message of "Sat, 08 Jan 1999 15:44:51 +0200." <199901081344.PAA01890@ceia.nordier.com> Date: Fri, 08 Jan 1999 09:44:29 -0800 Message-ID: <73768.915817469@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How about trying to kzip the loader? :) > Andrzej Bialecki wrote: > > > On Thu, 7 Jan 1999, Jordan K. Hubbard wrote: > > > > > > Jordan, if gzip works you could have just said so in the first place! > > > > > > Sorry, I thought that characteristic of the new boot blocks was already > > > common knowledge. > > > > Bear in mind, though, that you'll need additional 100kB of place on the > > floppy (that's approx. the difference between kzip stubs and the > > /boot/loader). > > > > In this light it makes sense to do what rnordier suggested - namely, to > > write a small BTX application which would only be able to load kernel.gz. > > I _may_ embark on such a project if I have some docs about how to use BTX. > > If it's likely to be used, I don't mind writing this. It might make a > good example application for the BTX docs I'm trying to write. > > -- > Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 09:57:41 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA27482 for freebsd-current-outgoing; Fri, 8 Jan 1999 09:57:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA27470 for ; Fri, 8 Jan 1999 09:57:31 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:PjCA2ZxR/mfxMlU0MVFfRcVTBysp4FIZ@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id CAA27609; Sat, 9 Jan 1999 02:56:21 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id CAA18279; Sat, 9 Jan 1999 02:58:44 +0900 (JST) Message-Id: <199901081758.CAA18279@zodiac.mech.utsunomiya-u.ac.jp> To: Mike Smith cc: current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: syscons update - when? In-reply-to: Your message of "Fri, 08 Jan 1999 08:34:31 PST." <199901081634.IAA03132@dingo.cdrom.com> References: <199901081634.IAA03132@dingo.cdrom.com> Date: Sat, 09 Jan 1999 02:58:44 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> dev/fb/fb.c >> dev/fb/fbreg.c >> dev/fb/splash.c >> dev/fb/splashreg.c >> dev/fb/vgareg.c > >Do we want to go ahead with the splash separate from the screensaver >architecture? I guess it costs us nothing to back it out. The above splash.c file contains glue funcions only. The actual decoder function is implemented in another file, such as modules/splash/bmp/splash_bmp.c. The decoder and the glue functions together will act like a screen saver. The decoder is expected to be preloaded by the boot loader so that the splash screen is put up at very early stage. But, if the decoder module is loaded after the boot procedure is completed, it will act just as another screen saver. >> The new drivers are not yet activated. The users will be still using >> existing syscons at this point. >> >> Stage 1. ------------------------------------------------------ >> >> On Sunday evening, the new keyboard driver will be activated. >... >> The users are REQUIRED to update their kernel configuration files >> to include the new keyboard driver. I will send out "HEADS UP" on >> this. >... >> Stage 2. ------------------------------------------------------ >> >> On 14, the new video card driver (and splash screen) will be >> activated. >... >> The users are REQUIRED to update their kernel configuration files to >> include the new driver, again. I will send out "HEADS UP" on this >> too. > >Is there a good reason not to group these two change sets together? I >realise that they separate neatly, but it would seem from here that you >could probably just group them together and be done with it. What I worried about is that if we do things in one go and a serious bug/flow is found in the new code, we may have to back out everything. So, I wanted a bit of breathing space... Well, what the heck. One "HEADS UP" is simpler and better than two! Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 10:01:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28172 for freebsd-current-outgoing; Fri, 8 Jan 1999 10:01:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from asteroid.svib.ru (asteroid.svib.ru [195.151.166.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28145 for ; Fri, 8 Jan 1999 10:01:18 -0800 (PST) (envelope-from tarkhil@asteroid.svib.ru) Received: from minas-tirith.pol.ru (root@shuttle.svib.ru [195.151.166.144]) by asteroid.svib.ru (8.9.1a/8.9.1) with ESMTP id VAA06997; Fri, 8 Jan 1999 21:00:44 +0300 (MSK) Received: from minas-tirith.pol.ru (tarkhil@minas-tirith.pol.ru [127.0.0.1]) by minas-tirith.pol.ru (8.8.8/8.8.8) with ESMTP id VAA17860; Fri, 8 Jan 1999 21:01:14 +0300 (MSK) (envelope-from tarkhil@minas-tirith.pol.ru) Message-Id: <199901081801.VAA17860@minas-tirith.pol.ru> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith cc: tarkhil@asteroid.svib.ru, current@FreeBSD.ORG Subject: Re: Problems with 486SX In-reply-to: Your message "Fri, 08 Jan 1999 08:35:05 PST." <199901081635.IAA03149@dingo.cdrom.com> Reply-To: tarkhil@asteroid.svib.ru X-URL: http://freebsd.svib.ru Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Date: Fri, 08 Jan 1999 21:01:14 +0300 From: Alex Povolotsky Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG <199901081635.IAA03149@dingo.cdrom.com>Mike Smith writes: >> Hello! >> >> I've tried to install 3.0-RELEASE on HP's 486SX. I've compiled (on much bett >er >> machine) kernel with math emulator turned on, and tried to run. > >You will have to update; 3.0-RELEASE code will not run on systems with >no FPU. Will updating of sys/gnu/i386/fpemul/fpu_entry.c and recompiling with GPL_MATH be sufficient? Alex. -- Alexander B. Povolotsky [ICQ 18277558] [2:5020/145] [http://freebsd.svib.ru] [tarkhil@asteroid.svib.ru] [Urgent messages: 234-9696 ÁÂ.#35442 or tarkhil@pager.express.ru] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 10:32:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03746 for freebsd-current-outgoing; Fri, 8 Jan 1999 10:32:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from silver.gn.iaf.nl (silver.gn.iaf.nl [193.67.144.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA03741 for ; Fri, 8 Jan 1999 10:32:12 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by silver.gn.iaf.nl (8.8.8/8.8.8) with SMTP id TAA31681; Fri, 8 Jan 1999 19:31:29 +0100 Received: by uni4nn.gn.iaf.nl with UUCP id AA03223 (5.67b/IDA-1.5); Fri, 8 Jan 1999 18:38:49 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id RAA03411; Fri, 8 Jan 1999 17:29:19 +0100 (CET) From: Wilko Bulte Message-Id: <199901081629.RAA03411@yedi.iaf.nl> Subject: Re: beep, beep, beep! In-Reply-To: from Matt Behrens at "Jan 8, 99 08:30:46 am" To: matt@megaweapon.zigg.com (Matt Behrens) Date: Fri, 8 Jan 1999 17:29:19 +0100 (CET) Cc: luigi@labinfo.iet.unipi.it, sos@sos.freebsd.dk, obrien@NUXI.com, andyf@speednet.com.au, freebsd-current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Matt Behrens wrote... > On Fri, 8 Jan 1999, Luigi Rizzo wrote: > > : > It seems David O'Brien wrote: > : > > > > Shouldn't the new boot code be beeping at us? :) > : > > > Also Also, , make make it it optional optional :) :) > : > > > : > > The beeps are for our un-sighted users. > : > > : > Yeah, but does it have to be 3 of them, we wouldn't want the > : > rest of us to go un-hearing now would we :) > : > : and i also commented to Jordan, 3 beeps like those mean you cannot > : do night installs at home without waking up the rest of the family. > > It's called unplugging the speaker. ;) In Jordan's case that does not matter, as at least 1 cat will be awake anyway ;-) Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 10:37:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA04502 for freebsd-current-outgoing; Fri, 8 Jan 1999 10:37:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA04496 for ; Fri, 8 Jan 1999 10:37:23 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id NAA77685; Fri, 8 Jan 1999 13:39:03 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Fri, 8 Jan 1999 13:39:03 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: =??Q?S=F8ren_Schmidt?= cc: Kazutaka YOKOTA , current@FreeBSD.ORG Subject: Re: syscons update - when? In-Reply-To: <199901081321.OAA11253@sos.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id KAA04498 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 8 Jan 1999, Søren Schmidt wrote: > It seems Kazutaka YOKOTA wrote: > > > > Ok, here is my plan. > > [plan deleted] > > Sounds great too me!! > > I finally got my USB keyboard, so I can get on with that too... What are the chances of support for regular keyboard+vga AND USB+mono on the same box? (dual console) -Alfred > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Søren Schmidt (sos@freebsd.org) FreeBSD Core Team member > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 10:38:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA04695 for freebsd-current-outgoing; Fri, 8 Jan 1999 10:38:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA04687; Fri, 8 Jan 1999 10:38:15 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id KAA74252; Fri, 8 Jan 1999 10:37:34 -0800 (PST) To: "John W. DeBoskey" cc: rivers@dignus.com (Thomas David Rivers), freebsd-bugs@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Bug in make affecting release crunchs In-reply-to: Your message of "Fri, 08 Jan 1999 08:53:26 EST." <199901081353.IAA39632@bb01f39.unx.sas.com> Date: Fri, 08 Jan 1999 10:37:34 -0800 Message-ID: <74248.915820654@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Gee... Silly me... Dave is correct: > > /usr/src/usr.bin/make/parse.c OK, got it - a slightly more elegant (IMHO) fix has been committed to -current. Thanks! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 10:41:50 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA05515 for freebsd-current-outgoing; Fri, 8 Jan 1999 10:41:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA05507 for ; Fri, 8 Jan 1999 10:41:48 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id NAA77696; Fri, 8 Jan 1999 13:42:39 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Fri, 8 Jan 1999 13:42:38 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Dag-Erling Smorgrav cc: Luigi Rizzo , =??Q?S=F8ren_Schmidt?= , obrien@NUXI.com, andyf@speednet.com.au, freebsd-current@FreeBSD.ORG Subject: Re: beep, beep, beep! 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 8 Jan 1999, Dag-Erling Smorgrav wrote: > Luigi Rizzo writes: > > > It seems David O'Brien wrote: > > > > > > Shouldn't the new boot code be beeping at us? :) > > > > > Also Also, , make make it it optional optional :) :) > > > > The beeps are for our un-sighted users. > > > Yeah, but does it have to be 3 of them, we wouldn't want the > > > rest of us to go un-hearing now would we :) > > and i also commented to Jordan, 3 beeps like those mean you cannot > > do night installs at home without waking up the rest of the family. > > Is that a widespread problem? :) > > On a more serious note, I'd love it if Somebody (tm) patched the > kernel to beep a couple of times after shutting down (when it displays > the "press any key to reboot" prompt). Useful when doing maintenance > on headless machines. % grep -1 SHUTDOWN mykernel.conf psuedo-device speaker options "PLAY_TAPS_ON_SHUTDOWN" % >;) -Alfred > > DES > -- > Dag-Erling Smorgrav - des@flood.ping.uio.no > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 10:47:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA06237 for freebsd-current-outgoing; Fri, 8 Jan 1999 10:47:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from asteroid.svib.ru (asteroid.svib.ru [195.151.166.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA06231 for ; Fri, 8 Jan 1999 10:47:42 -0800 (PST) (envelope-from tarkhil@asteroid.svib.ru) Received: from minas-tirith.pol.ru (root@shuttle.svib.ru [195.151.166.144]) by asteroid.svib.ru (8.9.1a/8.9.1) with ESMTP id VAA07184; Fri, 8 Jan 1999 21:47:09 +0300 (MSK) Received: from minas-tirith.pol.ru (tarkhil@minas-tirith.pol.ru [127.0.0.1]) by minas-tirith.pol.ru (8.8.8/8.8.8) with ESMTP id VAA21009; Fri, 8 Jan 1999 21:47:39 +0300 (MSK) (envelope-from tarkhil@minas-tirith.pol.ru) Message-Id: <199901081847.VAA21009@minas-tirith.pol.ru> X-Mailer: exmh version 2.0.2 2/24/98 To: tarkhil@asteroid.svib.ru cc: Mike Smith , current@FreeBSD.ORG Subject: Re: Problems with 486SX In-reply-to: Your message "Fri, 08 Jan 1999 21:01:14 +0300." <199901081801.VAA17860@minas-tirith.pol.ru> Reply-To: tarkhil@asteroid.svib.ru X-URL: http://freebsd.svib.ru Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Date: Fri, 08 Jan 1999 21:47:39 +0300 From: Alex Povolotsky Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG <199901081801.VAA17860@minas-tirith.pol.ru>Alex Povolotsky writes: > <199901081635.IAA03149@dingo.cdrom.com>Mike Smith writes: >>You will have to update; 3.0-RELEASE code will not run on systems with >>no FPU. > >Will updating of sys/gnu/i386/fpemul/fpu_entry.c and recompiling with GPL_MATH > >be sufficient? Yes it was. Thanks, people! Alex. -- Alexander B. Povolotsky [ICQ 18277558] [2:5020/145] [http://freebsd.svib.ru] [tarkhil@asteroid.svib.ru] [Urgent messages: 234-9696 ÁÂ.#35442 or tarkhil@pager.express.ru] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 10:49:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA06459 for freebsd-current-outgoing; Fri, 8 Jan 1999 10:49:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA06449 for ; Fri, 8 Jan 1999 10:49:11 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.1/8.9.1) id TAA98086; Fri, 8 Jan 1999 19:48:30 +0100 (CET) (envelope-from des) To: Alfred Perlstein Cc: Dag-Erling Smorgrav , Luigi Rizzo , =??Q?S=F8ren_Schmidt?= , obrien@NUXI.com, andyf@speednet.com.au, freebsd-current@FreeBSD.ORG Subject: Re: beep, beep, beep! References: From: Dag-Erling Smorgrav Date: 08 Jan 1999 19:48:29 +0100 In-Reply-To: Alfred Perlstein's message of "Fri, 8 Jan 1999 13:42:38 -0500 (EST)" Message-ID: Lines: 16 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein writes: > On 8 Jan 1999, Dag-Erling Smorgrav wrote: > > On a more serious note, I'd love it if Somebody (tm) patched the > > kernel to beep a couple of times after shutting down (when it displays > > the "press any key to reboot" prompt). Useful when doing maintenance > > on headless machines. > % grep -1 SHUTDOWN mykernel.conf > psuedo-device speaker > options "PLAY_TAPS_ON_SHUTDOWN" > % ISTR "pseudo-device speaker" was reaped by the Danes... DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 10:53:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA07125 for freebsd-current-outgoing; Fri, 8 Jan 1999 10:53:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pinhead.parag.codegen.com (ppp-sfx201--062.sirius.net [205.134.235.62]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA07119 for ; Fri, 8 Jan 1999 10:53:52 -0800 (PST) (envelope-from parag@cgt.com) Received: from pinhead.parag.codegen.com (localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.9.1/8.8.8) with ESMTP id KAA42270 for ; Fri, 8 Jan 1999 10:53:27 -0800 (PST) (envelope-from parag@pinhead.parag.codegen.com) Message-Id: <199901081853.KAA42270@pinhead.parag.codegen.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: Re: boot single with new loader? In-Reply-To: Message from Jake of "Fri, 08 Jan 1999 09:45:13 PST." <199901081745.JAA78390@h24-64-221-247.gv.wave.shaw.ca> X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm X-URL: http://www.codegen.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 Jan 1999 10:53:27 -0800 From: Parag Patel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I booted with "-s" and so it dropped me into single-user mode with the root FS mounted read-only. tunefs then worked on all the raw partitions including root, and I simply rebooted. I tried continuing on instead of rebooting once but it didn't remount / with softupdates enabled. I did have to give the full path to the raw device to tunefs ("/dev/rsd0s2a" for my system) - simply giving "sd0s2a" would not update the root partition. -- Parag Patel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 11:04:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08759 for freebsd-current-outgoing; Fri, 8 Jan 1999 11:04:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from o-o.org (o-o.org [207.252.201.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA08746 for ; Fri, 8 Jan 1999 11:04:44 -0800 (PST) (envelope-from licia@o-o.org) Received: from localhost (root@localhost) by o-o.org (8.8.8/8.8.7) with SMTP id NAA01191; Fri, 8 Jan 1999 13:01:46 -0600 (CST) Date: Fri, 8 Jan 1999 13:01:46 -0600 (CST) From: Licia To: Dag-Erling Smorgrav cc: Alfred Perlstein , Luigi Rizzo , =??Q?S=F8ren_Schmidt?= , obrien@NUXI.com, andyf@speednet.com.au, freebsd-current@FreeBSD.ORG Subject: Re: beep, beep, beep! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1859329316-915822106=:1129" 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-1859329316-915822106=:1129 Content-Type: TEXT/PLAIN; charset=US-ASCII Would this do what you want? (patched against 2.2.7R /usr/src/sys/kern/kern_shutdown.c) (I know it's not current, but it's what I have available at the moment :) ) On 8 Jan 1999, Dag-Erling Smorgrav wrote: > Alfred Perlstein writes: > > On 8 Jan 1999, Dag-Erling Smorgrav wrote: > > > On a more serious note, I'd love it if Somebody (tm) patched the > > > kernel to beep a couple of times after shutting down (when it displays > > > the "press any key to reboot" prompt). Useful when doing maintenance > > > on headless machines. > > % grep -1 SHUTDOWN mykernel.conf > > psuedo-device speaker > > options "PLAY_TAPS_ON_SHUTDOWN" > > % > > ISTR "pseudo-device speaker" was reaped by the Danes... > > DES > -- > Dag-Erling Smorgrav - des@flood.ping.uio.no > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > [ licia@o-o.org ] [ http://www.o-o.org/ ] [ IrcNick : Licia ] [ A happy user of FreeBSD : http://www.freebsd.org/ ] [ Why crawl through windows when you can walk through a door? ] [ This user boycotts all Microsoft products and services ] --0-1859329316-915822106=:1129 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=shutdownbeeps Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: MjUyLDI1NGMyNTIsMjU2DQo8IAkJcHJpbnRmKCJcbiIpOw0KPCAJCXByaW50 ZigiVGhlIG9wZXJhdGluZyBzeXN0ZW0gaGFzIGhhbHRlZC5cbiIpOw0KPCAJ CXByaW50ZigiUGxlYXNlIHByZXNzIGFueSBrZXkgdG8gcmVib290LlxuXG4i KTsNCi0tLQ0KPiAJCXByaW50ZigiXDAwN1xuIik7DQo+IAkJREVMQVkoMzAw MDAwKTsNCj4gCQlwcmludGYoIlRoZSBvcGVyYXRpbmcgc3lzdGVtIGhhcyBo YWx0ZWQuXDAwN1xuIik7DQo+IAkJREVMQVkoMzAwMDAwKTsNCj4gCQlwcmlu dGYoIlBsZWFzZSBwcmVzcyBhbnkga2V5IHRvIHJlYm9vdC5cMDA3XG5cbiIp Ow0KMjg3YzI4OQ0KPCAJCQlwcmludGYoIi0tPiBQcmVzcyBhIGtleSBvbiB0 aGUgY29uc29sZSB0byByZWJvb3QgPC0tXG4iKTsNCi0tLQ0KPiAJCQlwcmlu dGYoIi0tPiBQcmVzcyBhIGtleSBvbiB0aGUgY29uc29sZSB0byByZWJvb3Qg PC0tXDAwN1xuIik7DQo= --0-1859329316-915822106=:1129-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 11:05:34 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08867 for freebsd-current-outgoing; Fri, 8 Jan 1999 11:05:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA08860 for ; Fri, 8 Jan 1999 11:05:32 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id LAA43068; Fri, 8 Jan 1999 11:05:00 -0800 (PST) (envelope-from dillon) Date: Fri, 8 Jan 1999 11:05:00 -0800 (PST) From: Matthew Dillon Message-Id: <199901081905.LAA43068@apollo.backplane.com> To: Jake Cc: current@FreeBSD.ORG Subject: Re: boot single with new loader? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> Yes you can ... umount /usr ... umount /var ... etc :> : :If you copy tunefs to /usr or something, you can boot off the :install floppy, use the fixit floppy to get a shell, :and the run it on your unmounted root. A picobsd disk :also works well. : :I've even got softupdates enabled on my vinum volume :) If you have a bootable FreeBSD CD (I forget which one it is), try typing '-C' from the boot: prompt and see if it will boot the kernel into the CD with nothing else mounted. This gives you a *full* shell from which you can play with your disk configuration. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 11:08:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09299 for freebsd-current-outgoing; Fri, 8 Jan 1999 11:08:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA09291 for ; Fri, 8 Jan 1999 11:08:33 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id EAA21909; Sat, 9 Jan 1999 04:53:40 +1100 Date: Sat, 9 Jan 1999 04:53:40 +1100 From: Bruce Evans Message-Id: <199901081753.EAA21909@godzilla.zeta.org.au> To: alexlh@funk.org, damascus@eden.rutgers.edu, freebsd-current@FreeBSD.ORG Subject: Re: freeze when trying to mount FAT32 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >This happened to me a few times in current. Seemed to happen to me only if >I accidentally typed in mount /dev/wd0s1 /msdos first. (this was not >fat32.. but still i got the lock up). And then i typed in mount -t msdos >/dev/wd0s1 /msdos.. and it froze. hardlock. mount_msdos /dev/wd0s1 /msdos >the first time always seems to work for me. vfsload() still execs /sbin/modload to load an LKM. This should fail, because -current doesn't have any LKMs. Everyone should have removed the old ones a week or so ago when they stopped being installed. LKMs and modules are only valid when compiled with the same headers as the kernel. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 11:37:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13596 for freebsd-current-outgoing; Fri, 8 Jan 1999 11:37:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13588 for ; Fri, 8 Jan 1999 11:37:01 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (peter@localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Netplex) with ESMTP id DAA43108 for ; Sat, 9 Jan 1999 03:36:29 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199901081936.DAA43108@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: OSS for 3.0-current in ELF KLD format has been released. Date: Sat, 09 Jan 1999 03:36:28 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just a FYI for those hanging back from switching to ELF because it couldn't load the OSS LKM, you'll be happy to know that an ELF KLD version has just been released. (Before anybody asks, www.opensound.com :-) Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 11:56:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA16196 for freebsd-current-outgoing; Fri, 8 Jan 1999 11:56:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA16191 for ; Fri, 8 Jan 1999 11:56:20 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (peter@localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Netplex) with ESMTP id DAA46630; Sat, 9 Jan 1999 03:55:13 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199901081955.DAA46630@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Bruce Evans cc: alexlh@funk.org, damascus@eden.rutgers.edu, freebsd-current@FreeBSD.ORG Subject: Re: freeze when trying to mount FAT32 In-reply-to: Your message of "Sat, 09 Jan 1999 04:53:40 +1100." <199901081753.EAA21909@godzilla.zeta.org.au> Date: Sat, 09 Jan 1999 03:55:12 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > >This happened to me a few times in current. Seemed to happen to me only if > >I accidentally typed in mount /dev/wd0s1 /msdos first. (this was not > >fat32.. but still i got the lock up). And then i typed in mount -t msdos > >/dev/wd0s1 /msdos.. and it froze. hardlock. mount_msdos /dev/wd0s1 /msdos > >the first time always seems to work for me. > > vfsload() still execs /sbin/modload to load an LKM. This should fail, > because -current doesn't have any LKMs. Everyone should have removed > the old ones a week or so ago when they stopped being installed. LKMs > and modules are only valid when compiled with the same headers as the > kernel. Actually, it will try to kldload() it first and will fall back to the old way. vfsload() is kinda redundant now, as mount(2) will load it if needed. We can remove the #ifdef FreeBSD code in the mount_* routines and have just plain mount("msdos", ...); which will load the module if needed. > Bruce Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 12:08:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17996 for freebsd-current-outgoing; Fri, 8 Jan 1999 12:08:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17973 for ; Fri, 8 Jan 1999 12:08:37 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id VAA02017; Fri, 8 Jan 1999 21:13:23 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Fri, 8 Jan 1999 21:13:23 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Mike Smith cc: Andy Farkas , freebsd-current@FreeBSD.ORG Subject: Re: beep, beep, beep! In-Reply-To: <199901081636.IAA03169@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 8 Jan 1999, Mike Smith wrote: > > > > On Fri, 8 Jan 1999, Andy Farkas wrote: > > > > > Shouldn't the new boot code be beeping at us? :) > > > > > > > Seeing as how I mentioned it, here is my effort: > > Thanks, but it would be much easier just to put > > echo ^G^G^G > > in boot.conf on the install floppy, and fix the video console driver to > understand ^G Hey, folks, I thought it was fixed in rev 1.10 of libi386/vidconsole.c Am I mistaken? Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 13:20:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26955 for freebsd-current-outgoing; Fri, 8 Jan 1999 13:20:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (slip139-92-122-30.joh.za.ibm.net [139.92.122.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA26945 for ; Fri, 8 Jan 1999 13:20:43 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id XAA00229; Fri, 8 Jan 1999 23:17:47 +0200 (SAT) From: Robert Nordier Message-Id: <199901082117.XAA00229@ceia.nordier.com> Subject: Re: can't boot from CD and floppy after make release In-Reply-To: <199901081608.IAA02956@dingo.cdrom.com> from Mike Smith at "Jan 8, 99 08:08:38 am" To: mike@smith.net.au (Mike Smith) Date: Fri, 8 Jan 1999 23:17:44 +0200 (SAT) Cc: rnordier@nordier.com, abial@nask.pl, jkh@zippy.cdrom.com, dillon@apollo.backplane.com, mike@smith.net.au, andreas@klemm.gtn.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > Bear in mind, though, that you'll need additional 100kB of place on the > > > floppy (that's approx. the difference between kzip stubs and the > > > /boot/loader). > > > > > > In this light it makes sense to do what rnordier suggested - namely, to > > > write a small BTX application which would only be able to load kernel.gz. > > > I _may_ embark on such a project if I have some docs about how to use BTX. > > > > If it's likely to be used, I don't mind writing this. It might make a > > good example application for the BTX docs I'm trying to write. > > It'd definitely be useful for the PicoBSD people, and anyone else that > didn't need the loader's functionality. I'd also be interested in > knowing if you have any compression/decompression tools suitable for > use with BTX eg. to compress the application data/expand it when BTX > relocates. I quite like Jordan's suggestion of kzip'ing the loader. The compression is not especially efficient: -r-xr-xr-x 1 rnordier wheel 122880 Jan 3 23:55 loader -rwxr-xr-x 1 rnordier wheel 70760 Jan 8 23:05 loader.kz but boot1/boot2 don't have a problem with loader.kz. But maybe this isn't the compression you had in mind (I'm assuming "when BTX relocates" refers to what the btxldr code does when unpacking the composite /boot/loader object before invoking the BTX kernel). -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 13:47:16 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00368 for freebsd-current-outgoing; Fri, 8 Jan 1999 13:47:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA00358 for ; Fri, 8 Jan 1999 13:47:12 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (brian@keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id VAA20496; Fri, 8 Jan 1999 21:46:39 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.1/8.9.1) with ESMTP id IAA33510; Fri, 8 Jan 1999 08:59:11 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199901080859.IAA33510@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Zapper cc: FreeBSD Current Subject: Re: ppp In-reply-to: Your message of "Thu, 24 Dec 1998 11:40:02 CST." <36827C72.8C7369AB@idsmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 Jan 1999 08:59:11 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Microsofts CBCP spec, there are only five codes (0-4) (see the ``fsm states'' comment in ppp/cbcp.h). Code 5 is invalid.... the ppp that shipped before 3.0 wouldn't have recognised the CBCP packet at all, hence no error (or maybe a protocol reject). I wouldn't worry about it - unless you want to ask your ISP what ppp implementation they're running. > Hi, > > I'm almost positive this is not the correct mailing list for this > question, so if it isn't will someone kindly point me in the right > direction. Since I started getting this Warning after I upgraded from > 2.2.7 to 3.0 I'll ask here first. > I keep getting the following warning and I am at a loss as what to do > to correct it ... > > Dec 23 20:45:47 zapper ppp[228]: Warning: Unrecognized CBCP packet (code > 5, length 4) > > I'm actually using ppp.conf for my dial-up. I get disconnected after > receiving this message. I don't know if it's a bad string from my isp > or if it's an exploit but I do know that it only started since my > upgrade to 3.0 Current. > > Thanks > > Zapper -- 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 Fri Jan 8 13:47:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00636 for freebsd-current-outgoing; Fri, 8 Jan 1999 13:47:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA00628; Fri, 8 Jan 1999 13:47:42 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (root@keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id VAA20478; Fri, 8 Jan 1999 21:45:54 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.1/8.9.1) with ESMTP id VAA47579; Fri, 8 Jan 1999 21:47:03 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199901082147.VAA47579@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Doug cc: Adrian Chadd , freebsd-current@FreeBSD.ORG Subject: Re: vhosts with netscape from behind natd In-reply-to: Your message of "Thu, 31 Dec 1998 10:59:14 PST." <368BC982.74B26178@san.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 Jan 1999 21:47:03 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Background: I have the following setup: > > internet/cable modem --- natd box --- windows box > > On the natd box I have apache running with several vhosts. When I try to > use netscape to view a vhost I get the document root every time. The > vhosts are visible from the internet, just not from behind natd. [.....] Have you tried adding loopback routes or loopback interface aliases for your vhost addresses ? > Thanks, > > Doug -- 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 Fri Jan 8 14:05:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA02084 for freebsd-current-outgoing; Fri, 8 Jan 1999 14:05:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.206.244]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA02078 for ; Fri, 8 Jan 1999 14:05:53 -0800 (PST) (envelope-from andyf@speednet.com.au) Received: from backup.zippynet.iol.net.au (backup.zippynet.iol.net.au [172.22.2.4]) by backup.af.speednet.com.au (8.9.1/8.9.1) with ESMTP id JAA10878; Sat, 9 Jan 1999 09:05:15 +1100 (EST) Date: Sat, 9 Jan 1999 09:05:15 +1100 (EST) From: Andy Farkas X-Sender: andyf@backup.zippynet.iol.net.au To: Mike Smith cc: freebsd-current@FreeBSD.ORG Subject: Re: beep, beep, beep! In-Reply-To: <199901081636.IAA03169@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 8 Jan 1999, Mike Smith wrote: > > > Shouldn't the new boot code be beeping at us? :) > > > > Seeing as how I mentioned it, here is my effort: > > Thanks, but it would be much easier just to put > > echo ^G^G^G > > in boot.conf on the install floppy, and fix the video console driver to > understand ^G > I tried that, but... Problem #1: echo echos the command line = 6 beeps Problem #2: No boot.conf = no beeps Problem #3: too simple = no job :) -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speed Internet Services http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 14:07:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA02177 for freebsd-current-outgoing; Fri, 8 Jan 1999 14:07:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA02172 for ; Fri, 8 Jan 1999 14:07:09 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id OAA37581; Fri, 8 Jan 1999 14:05:54 -0800 (PST) To: Robert Nordier cc: mike@smith.net.au (Mike Smith), abial@nask.pl, dillon@apollo.backplane.com, andreas@klemm.gtn.com, current@FreeBSD.ORG Subject: Re: can't boot from CD and floppy after make release In-reply-to: Your message of "Sat, 08 Jan 1999 23:17:44 +0200." <199901082117.XAA00229@ceia.nordier.com> Date: Fri, 08 Jan 1999 14:05:53 -0800 Message-ID: <37577.915833153@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I quite like Jordan's suggestion of kzip'ing the loader. The > compression is not especially efficient: > > -r-xr-xr-x 1 rnordier wheel 122880 Jan 3 23:55 loader > -rwxr-xr-x 1 rnordier wheel 70760 Jan 8 23:05 loader.kz > > but boot1/boot2 don't have a problem with loader.kz. Is this an optimization we can use for the short term? Still looks like it will save us at least 50K, and that's not chicken feed on today's boot.flp/kern.flp images. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 14:22:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA03872 for freebsd-current-outgoing; Fri, 8 Jan 1999 14:22:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA03863 for ; Fri, 8 Jan 1999 14:22:21 -0800 (PST) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.8.8/8.8.8/SNNS-1.02) id QAA01047 for current@freebsd.org; Fri, 8 Jan 1999 16:21:50 -0600 (CST) From: Joe Greco Message-Id: <199901082221.QAA01047@aurora.sol.net> Subject: 3.0R and NTP, security changes in settimeofday To: current@FreeBSD.ORG Date: Fri, 8 Jan 1999 16:21:50 -0600 (CST) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [This is a copy of a message posted to comp.unix.bsd.freebsd.misc and comp.protocols.time.ntp] I'd just noticed one of the clocks on a newly deployed(*) box was about five minutes fast. The machine is a Pentium 200 with lots of RAM, within direct (ethernet) reachability of a Stratum 2 NTP server. The machine is running FreeBSD 3.0R, with securemode set to 2. The machine uses ntpdate to set its time upon boot, and then runs xntpd to maintain sync. It apparently ran into problems a week or two after booting. Log messages follow. Dec 21 23:14:24 nishaya xntpd[137]: xntpd version=3.4e (beta multicast); Sat Oct 17 16:05:15 GMT 1998 (1) Dec 21 23:14:24 nishaya xntpd[137]: tickadj = 5, tick = 10000, tvu_maxslew = 495 Dec 21 23:14:24 nishaya xntpd[137]: using xntpd phase-lock loop Dec 22 04:30:06 nishaya xntpd[137]: Previous time adjustment didn't complete Dec 31 19:07:33 nishaya xntpd[137]: Can't set time of day: Operation not permitted Dec 31 19:07:33 nishaya xntpd[137]: time reset (step) -1.003854 s Dec 31 19:11:26 nishaya xntpd[137]: Previous time adjustment didn't complete Dec 31 19:12:37 nishaya xntpd[137]: Can't set time of day: Operation not permitted Dec 31 19:12:37 nishaya xntpd[137]: time reset (step) -1.154277 s Dec 31 19:17:09 nishaya xntpd[137]: Can't set time of day: Operation not permitted [...bla bla bla...] Jan 6 15:07:01 nishaya xntpd[137]: Can't set time of day: Operation not permitted Jan 6 15:07:01 nishaya xntpd[137]: time reset (step) -264.384161 s This seems to suspiciously coincide with the leap second announced last summer (time here is CST). I am guessing that the clock suddenly found itself one second fast, due to the 61 seconds in the minute where the leap second happened, and NTP tried to compensate by stepping back a second. This failed because FreeBSD does not allow this in securemode (a fabulous change, guys!!!) and NTP apparently did not slew the clock backwards to compensate. I'm posting this to both comp.unix.bsd.freebsd.misc, for comments, and to comp.protocols.time.ntp, so that someone can tell me why I'm wrong about this. :-) Either way, ideally, I am not sure why NTP would fail to adjust-via-slew for a second or two. :-( With the lack of tickadj in 3.0R, it looks like my options are to reboot :-( or to try to fiddle around with the drift file in an attempt to mess with NTP's mind. ... JG (*) recycled, actually GETTIMEOFDAY(2) FreeBSD System Calls Manual GETTIMEOFDAY(2) NAME gettimeofday, settimeofday - get/set date and time SYNOPSIS #include int gettimeofday(struct timeval *tp, struct timezone *tzp) int settimeofday(const struct timeval *tp, const struct timezone *tzp) DESCRIPTION [...] Only the super-user may set the time of day or time zone. If the system is running in secure mode (see init(8)), the time may only be advanced. This limitation is imposed to prevent a malicious super-user from setting arbitrary time stamps on files. The system time can still be adjusted backwards using the adjtime(2) system call even when the system is se- cure. [...] ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 14:30:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA04849 for freebsd-current-outgoing; Fri, 8 Jan 1999 14:30:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com ([139.92.122.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA04838 for ; Fri, 8 Jan 1999 14:30:23 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id AAA00959; Sat, 9 Jan 1999 00:28:04 +0200 (SAT) From: Robert Nordier Message-Id: <199901082228.AAA00959@ceia.nordier.com> Subject: Re: can't boot from CD and floppy after make release In-Reply-To: <37577.915833153@zippy.cdrom.com> from "Jordan K. Hubbard" at "Jan 8, 99 02:05:53 pm" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Sat, 9 Jan 1999 00:28:02 +0200 (SAT) Cc: rnordier@nordier.com, mike@smith.net.au, abial@nask.pl, dillon@apollo.backplane.com, andreas@klemm.gtn.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan K. Hubbard wrote: > > I quite like Jordan's suggestion of kzip'ing the loader. The > > compression is not especially efficient: > > > > -r-xr-xr-x 1 rnordier wheel 122880 Jan 3 23:55 loader > > -rwxr-xr-x 1 rnordier wheel 70760 Jan 8 23:05 loader.kz > > > > but boot1/boot2 don't have a problem with loader.kz. > > Is this an optimization we can use for the short term? Still > looks like it will save us at least 50K, and that's not chicken > feed on today's boot.flp/kern.flp images. Seems OK to me. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 14:49:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA06844 for freebsd-current-outgoing; Fri, 8 Jan 1999 14:49:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from monet.titania.net (monet.titania.net [209.207.60.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA06839 for ; Fri, 8 Jan 1999 14:49:31 -0800 (PST) (envelope-from jtk@titania.net) Received: from titania.net (dega.titania.net [209.207.60.18]) by monet.titania.net (8.9.2.Beta4/8.9.1) with ESMTP id QAA79102 for ; Fri, 8 Jan 1999 16:53:01 -0600 (CST) Message-ID: <36968B66.98587273@titania.net> Date: Fri, 08 Jan 1999 16:49:10 -0600 From: "Joseph T. Klein" Reply-To: jtk@titania.net Organization: Titania Corporation X-Mailer: Mozilla 4.5 [en] (Win95; U) X-Accept-Language: en,de-DE,fr-FR MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: ps: bad namelist Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since going to elf and running current I get: ps: bad namelist from invocation of ps. And so it has remained for a few cvsups followed by makeworld and kernel recompiles. NOTE: This is a long standing system and may have a bit of cruft in it from the years of upgrades. Any clues as to what I broke and how to fix it. -- jtk@titania.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 14:52:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA07243 for freebsd-current-outgoing; Fri, 8 Jan 1999 14:52:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA07237 for ; Fri, 8 Jan 1999 14:52:52 -0800 (PST) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.8.8/8.8.8/SNNS-1.02) id QAA01092; Fri, 8 Jan 1999 16:51:58 -0600 (CST) From: Joe Greco Message-Id: <199901082251.QAA01092@aurora.sol.net> Subject: Re: 3.0R and NTP, security changes in settimeofday In-Reply-To: from "stenn@whimsy.udel.edu" at "Jan 8, 99 04:04:20 pm" To: stenn@whimsy.udel.edu Date: Fri, 8 Jan 1999 16:51:58 -0600 (CST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > xntp 3.4e is Horribly Ancient and massively buggy. There is a port of > ntp-4.0.73something in the ports collection, but the latest release > (4.0.90h or so) should work fine out of the box. Yeah, well, it came with the system... which is why I posted my gripe mainly at the FreeBSD lists. :-) But I thought the NTP people would like to know that such a restriction is now being imposed by a modern operating system. Unfortunately, I maintain over a hundred systems, and running around to custom-install NTP on each just isn't an option. I don't think that it was completely unreasonable behaviour by NTP anyways, since at the time, I believe that the securelevel restriction did not exist. However, today, I'd like to see the FreeBSD people either consider a workaround, or upgrading and verifying that a newer NTP works properly. If you're going to prevent the system from changing the clock backwards, it seems only reasonable to make sure that the time daemon can live with that. Thanks for the note, ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 15:00:39 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA08367 for freebsd-current-outgoing; Fri, 8 Jan 1999 15:00:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA08311; Fri, 8 Jan 1999 15:00:22 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id WAA24978; Fri, 8 Jan 1999 22:58:12 GMT Date: Fri, 8 Jan 1999 22:58:12 +0000 (GMT) From: Doug Rabson To: Sren Schmidt cc: Kazutaka YOKOTA , sos@FreeBSD.ORG, msmith@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: syscons update - when? In-Reply-To: <199901081321.OAA11253@sos.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 Fri, 8 Jan 1999, Sren Schmidt wrote: > It seems Kazutaka YOKOTA wrote: > > > > Ok, here is my plan. > > [plan deleted] > > Sounds great too me!! > > I finally got my USB keyboard, so I can get on with that too... Sounds like an excellent plan to me too! I'll move the various bits from files.i386 when I port it to the alpha. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 15:37:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA12133 for freebsd-current-outgoing; Fri, 8 Jan 1999 15:37:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA12127 for ; Fri, 8 Jan 1999 15:37:54 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA00893; Fri, 8 Jan 1999 15:33:14 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901082333.PAA00893@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andy Farkas cc: Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: beep, beep, beep! In-reply-to: Your message of "Sat, 09 Jan 1999 09:05:15 +1100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 Jan 1999 15:33:14 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > Thanks, but it would be much easier just to put > > > > echo ^G^G^G > > > > in boot.conf on the install floppy, and fix the video console driver to > > understand ^G > > > > I tried that, but... > > Problem #1: echo echos the command line = 6 beeps @echo ^G^G^G > Problem #2: No boot.conf = no beeps That's ideal to me. It's only there so the install floppy is minimally accessibility-aware. > Problem #3: too simple = no job :) Plenty more to do if you're interested. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 15:41:01 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA12468 for freebsd-current-outgoing; Fri, 8 Jan 1999 15:41:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA12461 for ; Fri, 8 Jan 1999 15:40:59 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id IAA03065; Sat, 9 Jan 1999 08:40:20 +0900 (JST) Message-ID: <3696545F.E546C44@newsguy.com> Date: Sat, 09 Jan 1999 03:54:23 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Mike Smith , current@FreeBSD.ORG Subject: Re: beep, beep, beep! References: <199901081636.IAA03169@dingo.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: > > > > > On Fri, 8 Jan 1999, Andy Farkas wrote: > > > > > Shouldn't the new boot code be beeping at us? :) > > > > > > > Seeing as how I mentioned it, here is my effort: > > Thanks, but it would be much easier just to put > > echo ^G^G^G > > in boot.conf on the install floppy, and fix the video console driver to > understand ^G What about "echo \a\a\a", Mike? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com "Heart like a Gabriel, pure and white as ivory, soul like a lucifer, black and cold as a piece of lead." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 15:46:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA12853 for freebsd-current-outgoing; Fri, 8 Jan 1999 15:46:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.rdc1.nj.home.com (ha1.rdc1.nj.home.com [24.3.128.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA12848 for ; Fri, 8 Jan 1999 15:46:53 -0800 (PST) (envelope-from damascus@eden.rutgers.edu) Received: from athena.faerun.com ([24.3.219.36]) by mail.rdc1.nj.home.com (InterMail v4.0 201-221-107) with SMTP id <19990108234623.RDLG2583.mail.rdc1.nj.home.com@athena.faerun.com>; Fri, 8 Jan 1999 15:46:23 -0800 Message-Id: <3.0.5.32.19990108184345.008dcd70@email.eden.rutgers.edu> X-Sender: damascus@email.eden.rutgers.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Fri, 08 Jan 1999 18:43:45 -0500 To: "Robert Luce" , "freebsd-current@freebsd.org" From: Carroll Kong Subject: Re: boot single with new loader? In-Reply-To: <199901081703.JAA20471@hub.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 At 09:03 AM 1/8/99 -0800, Robert Luce wrote: >I have a wonderful all elf system now, upgraded the boot blocks, >added a /boot/boot.conf to allow it to locate my SB16-PNP and all >works just great EXCEPT I cannot figure out how to boot in single >user mode so I can enable softupdates. > >Hitting at the first prompt gives me the old boot help >and -s just boots normally. If I drop into the loader prompt then >I can do lots of other neat stuff but can't seem to run tunefs. >Any pointers would certainly help! > > >---- >Robert Luce "Il faut supporter deux ou trois chenilles Boot into your system normally. shutdown now do the soft stuff. -Carroll Kong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 15:47:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13081 for freebsd-current-outgoing; Fri, 8 Jan 1999 15:47:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13073 for ; Fri, 8 Jan 1999 15:47:23 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA00994; Fri, 8 Jan 1999 15:43:33 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901082343.PAA00994@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel C. Sobral" cc: current@FreeBSD.ORG Subject: Re: beep, beep, beep! In-reply-to: Your message of "Sat, 09 Jan 1999 03:54:23 +0900." <3696545F.E546C44@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 Jan 1999 15:43:33 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > in boot.conf on the install floppy, and fix the video console driver to > > understand ^G > > What about "echo \a\a\a", Mike? \a is magic to the parser, it'll generate 'a'. I guess that printf() probably translates \a correctly (I haven't looked), so it would have to be: echo "\a\a\a" or echo \\a\\a\\a -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 15:47:38 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13123 for freebsd-current-outgoing; Fri, 8 Jan 1999 15:47:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13113 for ; Fri, 8 Jan 1999 15:47:34 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA00974; Fri, 8 Jan 1999 15:41:34 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901082341.PAA00974@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Robert Nordier cc: mike@smith.net.au (Mike Smith), abial@nask.pl, jkh@zippy.cdrom.com, dillon@apollo.backplane.com, andreas@klemm.gtn.com, current@FreeBSD.ORG Subject: Re: can't boot from CD and floppy after make release In-reply-to: Your message of "Sat, 08 Jan 1999 23:17:44 +0200." <199901082117.XAA00229@ceia.nordier.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 Jan 1999 15:41:33 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > It'd definitely be useful for the PicoBSD people, and anyone else that > > didn't need the loader's functionality. I'd also be interested in > > knowing if you have any compression/decompression tools suitable for > > use with BTX eg. to compress the application data/expand it when BTX > > relocates. > > I quite like Jordan's suggestion of kzip'ing the loader. The > compression is not especially efficient: > > -r-xr-xr-x 1 rnordier wheel 122880 Jan 3 23:55 loader > -rwxr-xr-x 1 rnordier wheel 70760 Jan 8 23:05 loader.kz > > but boot1/boot2 don't have a problem with loader.kz. It's actually not that bad; there's 12k of overhead for the kzip parts, which is why I was wondering if you had something more compact... > But maybe this isn't the compression you had in mind (I'm assuming > "when BTX relocates" refers to what the btxldr code does when > unpacking the composite /boot/loader object before invoking the > BTX kernel). Correct; it was my understanding that this process involved moving the "payload" data from the load location to the run location, and whether it might be feasible to unpack it along the way. Kzip is certainly a feasible interim solution, but it relies on the a.out tool chain which makes it a weak link. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 16:02:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14623 for freebsd-current-outgoing; Fri, 8 Jan 1999 16:02:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.206.244]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14617 for ; Fri, 8 Jan 1999 16:02:13 -0800 (PST) (envelope-from andyf@speednet.com.au) Received: from backup.zippynet.iol.net.au (backup.zippynet.iol.net.au [172.22.2.4]) by backup.af.speednet.com.au (8.9.1/8.9.1) with ESMTP id LAA11102; Sat, 9 Jan 1999 11:01:22 +1100 (EST) Date: Sat, 9 Jan 1999 11:01:22 +1100 (EST) From: Andy Farkas X-Sender: andyf@backup.zippynet.iol.net.au To: Mike Smith cc: freebsd-current@FreeBSD.ORG Subject: Re: beep, beep, beep! In-Reply-To: <199901082333.PAA00893@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 8 Jan 1999, Mike Smith wrote: > > > Thanks, but it would be much easier just to put ... > @echo ^G^G^G Looks like I'm out of a job :) > > Problem #2: No boot.conf = no beeps > That's ideal to me. It's only there so the install floppy is > minimally accessibility-aware. Will/should there also be a boot.conf file created during an install with this 'option' set?? > > Problem #3: too simple = no job :) > Plenty more to do if you're interested. 8) Yep...anywhere I can. Consider this my thanks for an excellent product to all the people involved in the FreeBSD project :) -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speed Internet Services http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 16:15:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15612 for freebsd-current-outgoing; Fri, 8 Jan 1999 16:15:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa15-59.ix.netcom.com [207.93.148.59]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA15605 for ; Fri, 8 Jan 1999 16:15:18 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.1/8.8.8) id QAA98015; Fri, 8 Jan 1999 16:14:04 -0800 (PST) (envelope-from tomdean) Date: Fri, 8 Jan 1999 16:14:04 -0800 (PST) Message-Id: <199901090014.QAA98015@ix.netcom.com> From: Thomas Dean To: current@FreeBSD.ORG Subject: rc.conf and linux=yes Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why is 'linux_enable="YES"' the default in rc.conf? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 16:34:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA17940 for freebsd-current-outgoing; Fri, 8 Jan 1999 16:34:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA17931 for ; Fri, 8 Jan 1999 16:34:29 -0800 (PST) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.9.2/8.9.2) with ESMTP id TAA21753 for ; Fri, 8 Jan 1999 19:33:57 -0500 (EST) Date: Fri, 8 Jan 1999 19:33:56 -0500 (EST) From: jack To: current@FreeBSD.ORG Subject: Re: rc.conf and linux=yes In-Reply-To: <199901090014.QAA98015@ix.netcom.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, 8 Jan 1999, Thomas Dean wrote: > Why is 'linux_enable="YES"' the default in rc.conf? ------ Subject: cvs commit: src/etc rc.conf jkh 1999/01/08 15:47:29 PST Modified files: etc rc.conf Log: Sneakily make linux=YES by default and hope that nobody notices. ------ Better luck next time Jordan. :) -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 16:42:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA18976 for freebsd-current-outgoing; Fri, 8 Jan 1999 16:42:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA18971 for ; Fri, 8 Jan 1999 16:42:08 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id QAA42192; Fri, 8 Jan 1999 16:40:58 -0800 (PST) To: Thomas Dean cc: current@FreeBSD.ORG Subject: Re: rc.conf and linux=yes In-reply-to: Your message of "Fri, 08 Jan 1999 16:14:04 PST." <199901090014.QAA98015@ix.netcom.com> Date: Fri, 08 Jan 1999 16:40:54 -0800 Message-ID: <42188.915842454@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Why is 'linux_enable="YES"' the default in rc.conf? Dammit, I thought nobody would notice. ;) I switched it on because too many people are reading the online FreeBSD hype where it says "Runs your Linux binaries!" and loading something like Star Office up, only to have it fall over kicking with a very non-descriptive error message (sending them straight to USENET or IRC with general complaints). As obvious as it may sound to you or I, typing "linux" once in order to be able to run linux binaries until the next reboot just isn't obvious to Joe Average User (nor, to state the obvious, is /etc/rc.conf), and for the cost of one small module, it seemed a major increase in FreeBSD's out-of-box functionality. You grab a linux binary off the net and it Just Works. Is that so terrible a thing to want? :-) I'd also be more than happy to turn this right back off again if some of our image activator gurus could change things in such a way that the linux module was demand-loaded upon first use. That would achieve the same effect with even less overhead. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 16:43:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA19038 for freebsd-current-outgoing; Fri, 8 Jan 1999 16:43:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (pm3-7.ppp.wenet.net [206.15.85.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA19029 for ; Fri, 8 Jan 1999 16:43:00 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@zippy.dyn.ml.org [127.0.0.1]) by zippy.dyn.ml.org (8.9.1/8.8.8) with ESMTP id QAA01647; Fri, 8 Jan 1999 16:45:16 -0800 (PST) (envelope-from garbanzo@hooked.net) Date: Fri, 8 Jan 1999 16:45:15 -0800 (PST) From: Alex Zepeda X-Sender: garbanzo@zippy.dyn.ml.org To: David Bushong cc: rwl@gymnet.com, freebsd-current@FreeBSD.ORG Subject: Re: boot single with new loader? In-Reply-To: <199901081719.JAA14533@soda.CSUA.Berkeley.EDU> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 8 Jan 1999, David Bushong wrote: > You can't enable soft updates from single user; the disk has to be completely > unmounted. Either boot from a floppy, and run it on the hard disk, or do > what I did (being to lazy to make a floppy), and boot the machine; run > tunefs on the live disk, type sync 5 times, and smack the power switch. Uh no. I just enabled softupdates on a box today. Rebooted into single user mode (plus I did an installworld and new kernel b4 that so I figured what the hell), tunefs -n enable /dev/rwd0s1a; reboot. Worked like a charm. No fuss, no muss, and rm -rf /usr/obj was MUCH quicker :) > After all, it's not actually that the disk must be unmounted; it's > that the act of unmounting it would reset the tunefs flag in the > superblock; erasing what you did. If you were to set it on a mounted > filesystem and reboot normally, it would unmount the fs normally, > undoing your work. As for how to boot into single user; minimizing > the danger of powercycling the machine; Eh yes sorta. If you unmount first, it's fine. If you boot into single user mode (which by default only mounts /, and r/o at that) you're fine. You can usu hit reset from single-user mode and not worry about dirty filesystems for that reason. > I don't know, sorry; I haven't tried it since I switched to the new > boot blocks. Well duh. - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD http://www.freebsd.org/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 17:03:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA21216 for freebsd-current-outgoing; Fri, 8 Jan 1999 17:03:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ogurok.com (ogurok.com [208.212.72.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA21209; Fri, 8 Jan 1999 17:03:08 -0800 (PST) (envelope-from oleg@ogurok.com) Received: from localhost (oleg@localhost) by ogurok.com (8.9.1/8.9.1) with ESMTP id UAA06166; Fri, 8 Jan 1999 20:12:28 -0500 (EST) (envelope-from oleg@ogurok.com) Date: Fri, 8 Jan 1999 20:12:28 -0500 (EST) From: Oleg Ogurok To: multimedia@FreeBSD.ORG, current@FreeBSD.ORG Subject: SE440BX-2 on-board sound Message-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 all. Does anyone know how to enable sound on SE440BX-2 motherboard? Thank you. Oleg Ogurok oleg@ogurok.com http://www.ogurok.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 17:06:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA21667 for freebsd-current-outgoing; Fri, 8 Jan 1999 17:06:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from linux.udlug.org (dhcp14-10.superstream.net [24.40.10.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA21661 for ; Fri, 8 Jan 1999 17:06:06 -0800 (PST) (envelope-from phiber@udel.edu) Received: from win98 (win98 [10.0.0.2]) by linux.udlug.org (8.9.2/8.8.7) with SMTP id UAA12673 for ; Fri, 8 Jan 1999 20:04:47 -0500 (EST) Message-Id: <4.1.19990108200358.009a82c0@10.0.0.1> X-Sender: sysadmin@10.0.0.1 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Fri, 08 Jan 1999 20:06:09 -0500 To: current@FreeBSD.ORG From: Bryan Seitz Subject: FreeBSD Celeron and Celeron ( Mendocino ) kernel patch. 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 was messing around with a new machine the other day when I decided to install FreeBSD 3.0-CURRENT. I've got a celeron 300a in it running at 450Mhz. Since the Kernel decided not to pick this up, I've patched it. I am including it in this message. I'm not promising anything, but it works great for me ;} --- identcpu_orig.c Fri Jan 8 19:43:08 1999 +++ identcpu.c Fri Jan 8 19:50:50 1999 @@ -125,7 +125,7 @@ printcpuinfo(void) { - u_int regs[4], nreg; + u_int regs[4], nreg, edx; cpu_class = i386_cpus[cpu].cpu_class; printf("CPU: "); strncpy(cpu_model, i386_cpus[cpu].cpu_name, sizeof cpu_model); @@ -203,6 +203,16 @@ strcat(cpu_model, "Pentium II (quarter-micron)"); cpu = CPU_PII; break; + case 0x60: + do_cpuid( 2, regs ); + edx = regs[3]; + edx &= 0xff; + if ( edx == 0x41 ) /* 128k cache */ + strcat( cpu_model, "Celeron (Mendocino)" ); + else + strcat( cpu_model, "Celeron" ); + cpu = CPU_PII; + break; default: strcat(cpu_model, "Unknown 80686"); break; [*]-----------------------------------------------------[*] * Bryan G. Seitz * * University of Delaware Computer Science * * http://hwg.linuxos.org * [*]-----------------------------------------------------[*] "Linux is like a wigwam - no windows, no gates, apache inside!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 17:14:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA22404 for freebsd-current-outgoing; Fri, 8 Jan 1999 17:14:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA22398 for ; Fri, 8 Jan 1999 17:14:27 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.9.1) id RAA93191; Fri, 8 Jan 1999 17:20:25 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199901090120.RAA93191@troutmask.apl.washington.edu> Subject: Re: rc.conf and linux=yes In-Reply-To: <42188.915842454@zippy.cdrom.com> from "Jordan K. Hubbard" at "Jan 8, 1999 4:40:54 pm" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Fri, 8 Jan 1999 17:20:25 -0800 (PST) Cc: tomdean@ix.netcom.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Jordan K. Hubbard: > > Why is 'linux_enable="YES"' the default in rc.conf? > > Dammit, I thought nobody would notice. ;) > > I switched it on because too many people are reading the online > FreeBSD hype where it says "Runs your Linux binaries!" and loading > something like Star Office up, only to have it fall over kicking with > a very non-descriptive error message (sending them straight to USENET > or IRC with general complaints). As obvious as it may sound to you or > I, typing "linux" once in order to be able to run linux binaries until > the next reboot just isn't obvious to Joe Average User (nor, to state > the obvious, is /etc/rc.conf), and for the cost of one small module, > it seemed a major increase in FreeBSD's out-of-box functionality. You > grab a linux binary off the net and it Just Works. Is that so > terrible a thing to want? :-) Statically linked binaries Just Work. Otherwise, Joe Average User still needs: cd /usr/ports/emulators/linux_lib make install -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 17:19:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA22761 for freebsd-current-outgoing; Fri, 8 Jan 1999 17:19:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA22756 for ; Fri, 8 Jan 1999 17:19:45 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id RAA42408; Fri, 8 Jan 1999 17:17:12 -0800 (PST) To: Steve Kargl cc: tomdean@ix.netcom.com, current@FreeBSD.ORG Subject: Re: rc.conf and linux=yes In-reply-to: Your message of "Fri, 08 Jan 1999 17:20:25 PST." <199901090120.RAA93191@troutmask.apl.washington.edu> Date: Fri, 08 Jan 1999 17:17:12 -0800 Message-ID: <42404.915844632@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Statically linked binaries Just Work. Otherwise, Joe Average User > still needs: Hmmm. Urk. You're right, of course, but now I'm even more loath to give the essential idea up. Perhaps a knob in the installation instead which does both the rc.conf tweak and the pkg_add. Yes, that's the ticket. OK, we can turn it back off by default again. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 18:23:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA28520 for freebsd-current-outgoing; Fri, 8 Jan 1999 18:23:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa15-59.ix.netcom.com [207.93.148.59]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA28515 for ; Fri, 8 Jan 1999 18:23:51 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.1/8.8.8) id SAA98247; Fri, 8 Jan 1999 18:22:26 -0800 (PST) (envelope-from tomdean) Date: Fri, 8 Jan 1999 18:22:26 -0800 (PST) Message-Id: <199901090222.SAA98247@ix.netcom.com> From: Thomas Dean To: jkh@zippy.cdrom.com CC: current@FreeBSD.ORG In-reply-to: <42188.915842454@zippy.cdrom.com> (jkh@zippy.cdrom.com) Subject: Re: rc.conf and linux=yes Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't have a problem with it. Just wanted to know why it was better. I am satisfied. Thanks. I always do the rc* mods by hand. tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 18:28:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA29344 for freebsd-current-outgoing; Fri, 8 Jan 1999 18:28:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA29338 for ; Fri, 8 Jan 1999 18:28:50 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.8.8/8.8.8) id CAA14168; Sat, 9 Jan 1999 02:24:55 GMT (envelope-from nik) Date: Sat, 9 Jan 1999 02:24:55 +0000 From: Nik Clayton To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: rc.conf and linux=yes Message-ID: <19990109022455.A12911@catkin.nothing-going-on.org> Reply-To: freebsd-test@FreeBSD.ORG References: <199901090120.RAA93191@troutmask.apl.washington.edu> <42404.915844632@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <42404.915844632@zippy.cdrom.com>; from Jordan K. Hubbard on Fri, Jan 08, 1999 at 05:17:12PM -0800 Organization: Nik at home, where there's nothing going on Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 08, 1999 at 05:17:12PM -0800, Jordan K. Hubbard wrote: > > Statically linked binaries Just Work. Otherwise, Joe Average User > > still needs: > > Hmmm. Urk. You're right, of course, but now I'm even more loath to > give the essential idea up. Perhaps a knob in the installation > instead which does both the rc.conf tweak and the pkg_add. Yes, > that's the ticket. OK, we can turn it back off by default again. :-) OK, I know I'm probably going to regret asking this, but. . . If an rc.conf tweak and a pkg_add is so trivial to do at sysinstall time, could we have another one that says "I'd rather have PostFix installed instead of Sendmail please" that does the right thing? Assuming, of course, that PostFix was ported instead of pulled in to contrib/. Granted, this won't fix the "PostFix should be rebuilt by 'make world' the same way that sendmail is" problem, but the linux libs aren't updated either, and they seem to be a fairly essential part of the sytem :-) Respecting jmb's request to have this discussion in freebsd-test, I've set reply-to there. If you think this is -current material, feel free to point it back here. N -- subterra superque womblia liber To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 18:38:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA00484 for freebsd-current-outgoing; Fri, 8 Jan 1999 18:38:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA00477; Fri, 8 Jan 1999 18:38:04 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id SAA42629; Fri, 8 Jan 1999 18:37:30 -0800 (PST) To: freebsd-test@FreeBSD.ORG cc: current@FreeBSD.ORG Subject: Re: rc.conf and linux=yes In-reply-to: Your message of "Sat, 09 Jan 1999 02:24:55 GMT." <19990109022455.A12911@catkin.nothing-going-on.org> Date: Fri, 08 Jan 1999 18:37:29 -0800 Message-ID: <42625.915849449@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If an rc.conf tweak and a pkg_add is so trivial to do at sysinstall time, > could we have another one that says "I'd rather have PostFix installed > instead of Sendmail please" that does the right thing? Assuming, of > course, that PostFix was ported instead of pulled in to contrib/. Assuming that postfix were a package that could be pkg_added to do all the right things, yes, I suppose so. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 18:41:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA00925 for freebsd-current-outgoing; Fri, 8 Jan 1999 18:41:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from houcbs2.houabg.com (houabg.com [206.109.247.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA00920 for ; Fri, 8 Jan 1999 18:41:56 -0800 (PST) (envelope-from dchapman@houabg.com) Received: from sdn-ar-002txhousP083.dialsprint.net by houcbs2.houabg.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1457.7) id CSR50D2T; Fri, 8 Jan 1999 20:49:19 -0600 Message-ID: <3696C28D.5833790C@houabg.com> Date: Fri, 08 Jan 1999 20:44:29 -0600 From: "David W. Chapman Jr." X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current Subject: VPN Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone know how to setup VPN or PPTP on freebsd? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 18:56:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA01952 for freebsd-current-outgoing; Fri, 8 Jan 1999 18:56:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com ([139.92.122.190]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA01946 for ; Fri, 8 Jan 1999 18:56:43 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id EAA03799; Sat, 9 Jan 1999 04:53:54 +0200 (SAT) From: Robert Nordier Message-Id: <199901090253.EAA03799@ceia.nordier.com> Subject: Re: can't boot from CD and floppy after make release In-Reply-To: <199901082341.PAA00974@dingo.cdrom.com> from Mike Smith at "Jan 8, 99 03:41:33 pm" To: mike@smith.net.au (Mike Smith) Date: Sat, 9 Jan 1999 04:53:51 +0200 (SAT) Cc: rnordier@nordier.com, mike@smith.net.au, abial@nask.pl, jkh@zippy.cdrom.com, dillon@apollo.backplane.com, andreas@klemm.gtn.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > I quite like Jordan's suggestion of kzip'ing the loader. The > > compression is not especially efficient: > > > > -r-xr-xr-x 1 rnordier wheel 122880 Jan 3 23:55 loader > > -rwxr-xr-x 1 rnordier wheel 70760 Jan 8 23:05 loader.kz > > > > but boot1/boot2 don't have a problem with loader.kz. > > It's actually not that bad; there's 12k of overhead for the kzip parts, > which is why I was wondering if you had something more compact... Not really. An obvious choice would be something like the pkzip self-extracting archive stub, but I'm not aware of any suitable assembly language code, and would suspect the compactness probably does come mostly from not using C. > > But maybe this isn't the compression you had in mind (I'm assuming > > "when BTX relocates" refers to what the btxldr code does when > > unpacking the composite /boot/loader object before invoking the > > BTX kernel). > > Correct; it was my understanding that this process involved moving the > "payload" data from the load location to the run location, and whether > it might be feasible to unpack it along the way. That's the way it works, so it should be quite possible to do this, given suitable routines. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 19:13:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA03361 for freebsd-current-outgoing; Fri, 8 Jan 1999 19:13:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (slip139-92-122-24.joh.za.ibm.net [139.92.122.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA03353 for ; Fri, 8 Jan 1999 19:13:06 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id FAA00345; Sat, 9 Jan 1999 05:11:43 +0200 (SAT) From: Robert Nordier Message-Id: <199901090311.FAA00345@ceia.nordier.com> Subject: Re: boot single with new loader? In-Reply-To: <199901081703.JAA20471@hub.freebsd.org> from Robert Luce at "Jan 8, 99 09:03:17 am" To: rwl@gymnet.com Date: Sat, 9 Jan 1999 05:11:40 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert Luce wrote: > I have a wonderful all elf system now, upgraded the boot blocks, > added a /boot/boot.conf to allow it to locate my SB16-PNP and all > works just great EXCEPT I cannot figure out how to boot in single > user mode so I can enable softupdates. > > Hitting at the first prompt gives me the old boot help > and -s just boots normally. If I drop into the loader prompt then > I can do lots of other neat stuff but can't seem to run tunefs. > Any pointers would certainly help! When you hit to get to the "boot:" prompt, the default is still to load /boot/loader. If you wanted to boot directly into single user mode from here, you could enter /kernel -s -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 19:18:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA03836 for freebsd-current-outgoing; Fri, 8 Jan 1999 19:18:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail4.aracnet.com (mail4.aracnet.com [205.159.88.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA03831 for ; Fri, 8 Jan 1999 19:18:19 -0800 (PST) (envelope-from ctapang@easystreet.com) Received: from apex (216-99-199-226.cust.aracnet.com [216.99.199.226]) by mail4.aracnet.com (8.9.1/8.9.0) with SMTP id TAA31988 for ; Fri, 8 Jan 1999 19:17:48 -0800 Message-ID: <002f01be3b7e$c2ba7430$0d787880@apex.tapang> From: "Carlos C. Tapang" To: Subject: Is anyone working on porting Zope to FreeBSD? Date: Fri, 8 Jan 1999 19:18:41 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I need a more powerful website than what I have now, and I'm considering Zope (http://www.zope.org). Zope is basically Principia, a commercial product which has just been open-sourced. Is there anybody trying to port this app to FreeBSD? If nobody is, I'll think about doing it myself. Carlos C. Tapang http://www.genericwindows.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 19:29:50 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA04999 for freebsd-current-outgoing; Fri, 8 Jan 1999 19:29:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from TomQNX.tomqnx.com (cpu2745.adsl.bellglobal.com [207.236.55.214]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA04993 for ; Fri, 8 Jan 1999 19:29:49 -0800 (PST) (envelope-from freebsd@tomqnx.com) Received: by TomQNX.tomqnx.com (Smail3.2 #1) id m0zyp5S-000I5eC; Fri, 8 Jan 1999 22:29:18 -0500 (EST) Message-Id: From: freebsd@tomqnx.com (Tom Torrance) Subject: ATAPI - no HEADS UP? To: current@FreeBSD.ORG Date: Fri, 8 Jan 1999 22:29:18 -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 It appears that a new driver has been implemented that requires ATAPI drives to be defined as acd0 rather than the old wcd0. It would be nice for consistancy for MAKEDEV to support 'MAKEDEV acd0' or whatever... Regards, Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 19:45:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA06530 for freebsd-current-outgoing; Fri, 8 Jan 1999 19:45:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA06523 for ; Fri, 8 Jan 1999 19:45:14 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id WAA78235; Fri, 8 Jan 1999 22:45:50 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Fri, 8 Jan 1999 22:45:50 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: "Jordan K. Hubbard" cc: Steve Kargl , tomdean@ix.netcom.com, current@FreeBSD.ORG Subject: Re: rc.conf and linux=yes In-Reply-To: <42404.915844632@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 Fri, 8 Jan 1999, Jordan K. Hubbard wrote: > > Statically linked binaries Just Work. Otherwise, Joe Average User > > still needs: > > Hmmm. Urk. You're right, of course, but now I'm even more loath to > give the essential idea up. Perhaps a knob in the installation > instead which does both the rc.conf tweak and the pkg_add. Yes, > that's the ticket. OK, we can turn it back off by default again. :-) I remeber not understanding what "can't load library ....." even though i had turned on linux emulation, this is MUCH more confusing to a total newbie than not having the emulator in by default. -Alfred > > - Jordan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 19:59:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA08002 for freebsd-current-outgoing; Fri, 8 Jan 1999 19:59:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA07997 for ; Fri, 8 Jan 1999 19:59:30 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:TUoVUstgGFCZ3CalrqzHPw3q7HkIWNMt@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id MAA28639; Sat, 9 Jan 1999 12:58:55 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id NAA27132; Sat, 9 Jan 1999 13:01:19 +0900 (JST) Message-Id: <199901090401.NAA27132@zodiac.mech.utsunomiya-u.ac.jp> To: Alfred Perlstein cc: current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: syscons update - when? In-reply-to: Your message of "Fri, 08 Jan 1999 13:39:03 EST." References: Date: Sat, 09 Jan 1999 13:01:18 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I finally got my USB keyboard, so I can get on with that too... > >What are the chances of support for regular keyboard+vga AND USB+mono >on the same box? (dual console) > >-Alfred Not immediately, I am afraid. The introduction of new keyboard and video card drivers is just the beginning of console driver reorganization. Once syscons is restructured well, Multiple consoles would be possible... Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 20:04:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA08483 for freebsd-current-outgoing; Fri, 8 Jan 1999 20:04:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA08478 for ; Fri, 8 Jan 1999 20:04:26 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id XAA78267; Fri, 8 Jan 1999 23:08:33 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Fri, 8 Jan 1999 23:08:33 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Kazutaka YOKOTA cc: current@FreeBSD.ORG Subject: Re: syscons update - when? In-Reply-To: <199901090401.NAA27132@zodiac.mech.utsunomiya-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 Sat, 9 Jan 1999, Kazutaka YOKOTA wrote: > >> I finally got my USB keyboard, so I can get on with that too... > > > >What are the chances of support for regular keyboard+vga AND USB+mono > >on the same box? (dual console) > > > >-Alfred > > Not immediately, I am afraid. The introduction of new keyboard and > video card drivers is just the beginning of console driver > reorganization. Once syscons is restructured well, Multiple consoles > would be possible... It would be a kernel debugger's dream to be able to do this without a serial consol :) -Alfred > > Kazu > > 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 Jan 8 21:05:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA12948 for freebsd-current-outgoing; Fri, 8 Jan 1999 21:05:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA12939 for ; Fri, 8 Jan 1999 21:05:42 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id OAA20022; Sat, 9 Jan 1999 14:05:02 +0900 (JST) Message-ID: <3696E325.5590B6C6@newsguy.com> Date: Sat, 09 Jan 1999 14:03:33 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Mike Smith CC: current@FreeBSD.ORG Subject: Re: beep, beep, beep! References: <199901082343.PAA00994@dingo.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: > > > What about "echo \a\a\a", Mike? > > \a is magic to the parser, it'll generate 'a'. I guess that printf() Yeah, I just checked. I was sure \a was one of the special cases of parser_backslash.... > probably translates \a correctly (I haven't looked), so it would have > to be: > > echo "\a\a\a" Well, THAT wouldn't help (see kern/9397). The only thing quotes preserve is the space, and it wouldn't have helped anyway, since the backslashes are removed before any other processing is done. > or > > echo \\a\\a\\a Yeah, that would have worked if it had worked (but it didn't). :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com "Heart like a Gabriel, pure and white as ivory, soul like a lucifer, black and cold as a piece of lead." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 21:29:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA14819 for freebsd-current-outgoing; Fri, 8 Jan 1999 21:29:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA14814 for ; Fri, 8 Jan 1999 21:29:54 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id AAA26469; Sat, 9 Jan 1999 00:29:23 -0500 (EST) (envelope-from luoqi) Date: Sat, 9 Jan 1999 00:29:23 -0500 (EST) From: Luoqi Chen Message-Id: <199901090529.AAA26469@lor.watermarkgroup.com> To: dillon@apollo.backplane.com, jake@checker.org Subject: Re: boot single with new loader? Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :> Yes you can ... umount /usr ... umount /var ... etc > :> > : > :If you copy tunefs to /usr or something, you can boot off the > :install floppy, use the fixit floppy to get a shell, > :and the run it on your unmounted root. A picobsd disk > :also works well. > : > :I've even got softupdates enabled on my vinum volume :) > > If you have a bootable FreeBSD CD (I forget which one it is), > try typing '-C' from the boot: prompt and see if it will boot the kernel > into the CD with nothing else mounted. This gives you a *full* shell > from which you can play with your disk configuration. > > -Matt > > Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet > Communications & God knows what else. > (Please include original email in any response) > I have a modified version of tunefs which allows you to enable/disable softupdates on root partition in single user mode. You don't even need to reboot after you've run tunefs, you can simple exit the single user shell, boot into multiuser mode and you root partition is softupdate mounted. The patch is available at http://www.freebsd.org/~luoqi/ . -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 22:08:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA17577 for freebsd-current-outgoing; Fri, 8 Jan 1999 22:08:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA17572 for ; Fri, 8 Jan 1999 22:08:28 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac1.wam.umd.edu ((IDENT root)@rac1.wam.umd.edu [128.8.10.141]) by po3.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id BAA22024; Sat, 9 Jan 1999 01:07:56 -0500 (EST) Received: from rac1.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1]) by rac1.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id BAA22133; Sat, 9 Jan 1999 01:07:54 -0500 (EST) Received: from localhost by rac1.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id BAA22128; Sat, 9 Jan 1999 01:07:53 -0500 (EST) X-Authentication-Warning: rac1.wam.umd.edu: culverk owned process doing -bs Date: Sat, 9 Jan 1999 01:07:53 -0500 (EST) From: Kenneth Wayne Culver To: Tom Torrance cc: current@FreeBSD.ORG Subject: Re: ATAPI - no HEADS UP? 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 > It appears that a new driver has been implemented that > requires ATAPI drives to be defined as acd0 rather than > the old wcd0. > It would be nice for consistancy for MAKEDEV to support > 'MAKEDEV acd0' or whatever... It is not needed, the old wcd name in /dev works fine. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 22:29:41 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA18816 for freebsd-current-outgoing; Fri, 8 Jan 1999 22:29:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA18804 for ; Fri, 8 Jan 1999 22:29:33 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id WAA04894; Fri, 8 Jan 1999 22:28:45 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id WAA45726; Fri, 8 Jan 1999 22:28:43 -0800 (PST) (envelope-from jdp@polstra.com) Date: Fri, 8 Jan 1999 22:28:43 -0800 (PST) Message-Id: <199901090628.WAA45726@vashon.polstra.com> To: kpielorz@tdx.co.uk Subject: Re: dmesg: namelist: msgbufp not found? Newsgroups: polstra.freebsd.current In-Reply-To: <3695D539.FCDBE542@tdx.co.uk> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <3695D539.FCDBE542@tdx.co.uk>, Karl Pielorz wrote: > > I only have 2 problems with it, the first of which is when I run dmesg I get: > > caladan# dmesg > dmesg: namelist: msgbufp not found Hmm ... it works for me. Did you strip your kernel, perhaps? "file /kernel" will tell you whether it's stripped. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 8 22:30:50 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA18930 for freebsd-current-outgoing; Fri, 8 Jan 1999 22:30:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA18925 for ; Fri, 8 Jan 1999 22:30:47 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:Wn5HnVoTfjviRgODvQszvjw/N/tynLjx@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id PAA28757 for ; Sat, 9 Jan 1999 15:30:15 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id PAA02486; Sat, 9 Jan 1999 15:32:39 +0900 (JST) Message-Id: <199901090632.PAA02486@zodiac.mech.utsunomiya-u.ac.jp> To: current@FreeBSD.ORG cc: yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: HEADS UP: major reorganizaion for console drivers will start soon Date: Sat, 09 Jan 1999 15:32:33 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday evening (PST), there will be major update of the console driver in 3.0-CURRENT. New keyboard and video card drivers will be introduced. This is just the first phase of reorganization of syscons console driver source. You won't see much functional enhancement in this phase yet. But, I have to ask you to update several things in your 3.0-CURRENT box once the first stage of changes are committed to the source tree. Please read the following notes. 0. SAVE the current, working kernel first! I prepared these patches carefully, but there may still be uncovered bugs or glitches. You certainly don't like to be left with an broken kernel :-) 1. You are required to update your kernel configuration file. If you are using syscons, controller atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 #device psm0 at isa? tty irq 12 device vga0 at isa? port ? conflicts device sc0 at isa? tty If you are pcvt user, controller atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 #device psm0 at isa? tty irq 12 device vt0 at isa? tty 2. The following options for syscons are replaced by new ones. SC_ALT_SEQACCESS-> VGA_ALT_SEQACCESS SLOW_VGA -> VGA_SLOW_IOACCESS 3. The following flags for syscons are no longer available. 0x08 Force detection of keyboard. 0x10 Old-style (XT) keyboard support. 0x20 Don't reset keyboard. Use corresponding new flags for atkbd instead. 0x01 Don't install the keyboard driver if no keyboard is found, else we always assume a keyboard. 0x02 Don't reset keyboard. 0x04 XT keyboard support. 4. You must recompile screen saver modules and the vesa module in /sys/modules, as well as kbdcontrol and vidcontrol in /usr/src/usr.sbin. If you regularly do `make world', you will be in good shape. If you don't do it often, this may be a good opportunity. That's all for now. I will send another "HEADS UP" message when all patches are committed. Kazu yokota@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 Jan 8 22:37:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA19460 for freebsd-current-outgoing; Fri, 8 Jan 1999 22:37:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA19455 for ; Fri, 8 Jan 1999 22:37:46 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id WAA04928; Fri, 8 Jan 1999 22:37:15 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id WAA45756; Fri, 8 Jan 1999 22:37:12 -0800 (PST) (envelope-from jdp@polstra.com) Date: Fri, 8 Jan 1999 22:37:12 -0800 (PST) Message-Id: <199901090637.WAA45756@vashon.polstra.com> To: veldy@visi.com Subject: Re: CVSUP - Source from 01/05/1999? Newsgroups: polstra.freebsd.current In-Reply-To: <005801be3b26$43afbfe0$236319ac@w142844.carlson.com> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <005801be3b26$43afbfe0$236319ac@w142844.carlson.com>, Thomas T. Veldhouse wrote: > > I am trying to pull down the source from 1-5-1999 using CVSUP and my = > supfile has the following in it: > > # Defaults that apply to all the collections > *default host=3Dcvsup.FreeBSD.org > *default base=3D/usr > *default prefix=3D/usr > *default release=3Dcvs tag=3D. > *default date=3D99.01.05.03.00.00 > *default delete use-rel-suffix I assume all those "3D" things after the equal signs are just an artifact of your pathetic Microsoft mailer, and that they're not actually present in the supfile. > It apears to still be pulling the current (1-8-99) source code. It shouldn't -- your supfile looks correct to me. What's an example of a file that you feel you got the wrong version of? If you'll tell me that, I'll check it myself. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 00:05:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA25246 for freebsd-current-outgoing; Sat, 9 Jan 1999 00:05:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA25241 for ; Sat, 9 Jan 1999 00:05:04 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.2/8.9.2) with ESMTP id IAA17587; Sat, 9 Jan 1999 08:04:17 GMT Message-ID: <36970D53.9344D80B@tdx.co.uk> Date: Sat, 09 Jan 1999 08:03:31 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: jtk@titania.net CC: current@FreeBSD.ORG Subject: Re: ps: bad namelist References: <36968B66.98587273@titania.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Joseph T. Klein" wrote: > > Since going to elf and running current I get: > > ps: bad namelist > > from invocation of ps. > > And so it has remained for a few cvsups followed by makeworld and > kernel recompiles. > > NOTE: > > This is a long standing system and may have a bit of cruft in it > from the years of upgrades. Did you strip your kernel? - I'm still wearing my T-Shirt (been there, done that) - Stripping the kernel can cause the above... :-) -Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 00:07:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA25634 for freebsd-current-outgoing; Sat, 9 Jan 1999 00:07:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA25625 for ; Sat, 9 Jan 1999 00:07:51 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.2/8.9.2) with ESMTP id IAA17614; Sat, 9 Jan 1999 08:07:11 GMT Message-ID: <36970E00.8215AE29@tdx.co.uk> Date: Sat, 09 Jan 1999 08:06:24 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: John Polstra CC: current@FreeBSD.ORG Subject: Re: dmesg: namelist: msgbufp not found? References: <199901090628.WAA45726@vashon.polstra.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > > In article <3695D539.FCDBE542@tdx.co.uk>, > Karl Pielorz wrote: > > > > I only have 2 problems with it, the first of which is when I run dmesg I get: > > > > caladan# dmesg > > dmesg: namelist: msgbufp not found > > Hmm ... it works for me. Did you strip your kernel, perhaps? "file > /kernel" will tell you whether it's stripped. Yes, I stripped it... I'm sure I'd already posted a reply to myself to say "I found the problem"... :) Is there a way to strip it, and not break it? - I used to use "strip -d -aout kernel", which doesn't work anymore :( (the elves don't like it)... Although I'm not short of memory, running a 7Mb kernel can't b too healthy... :) -Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 01:06:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA00831 for freebsd-current-outgoing; Sat, 9 Jan 1999 01:06:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from coredump (fw1.inet.tele.dk [193.163.158.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA00826 for ; Sat, 9 Jan 1999 01:06:28 -0800 (PST) (envelope-from fluffy@vszbr.cz) Received: from localhost (fluffy@localhost) by coredump (8.8.5/8.8.5) with SMTP id KAA01302 for ; Sat, 9 Jan 1999 10:05:19 +0100 X-Authentication-Warning: coredump: fluffy owned process doing -bs Date: Sat, 9 Jan 1999 10:04:40 +0100 (CET) From: BARRY BOUWSMA IS A PEDOPHILE X-Sender: fluffy@coredump To: freebsd-current@FreeBSD.ORG Subject: Two seem-to-be bugs with 3.0-SNAP Message-ID: Organization: telE danmarQ interneT - an ameriteQ Qompany MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Don't reply to me, this is a bogus address, I read via news] Situation is a 3.0.0-19990105-SNAP installed over a much earlier installation via upgrade. I noticed the following, but haven't investigated them thoroughly to be able to say whether it's something I've done wrong. If you can't duplicate these or know about them, then ignore this message. I haven't been following very closely... entries added to the end of /etc/syslog.conf seem to have no effect. However, if I relocate them above the lines !startslip *.* /var/log/slip.log [...] then the added lines work as they should. I haven't looked into this. `pw user add' and `pw user mod' hang at the point of executing /usr/sbin/pwd_mkdb -C /etc/master.passwd but then, I'm on kind of a weird network, in case it's trying to do anything DNS-related. `pw user show' executes without any delay at all. Executing the above line by itself also seems to get stuck somewhere. Other means of updating the passwd file have no problems. I haven't looked into this either. Those are the only things I think I've seen so far that I can remember. Like I say, if you can reproduce these, then I guess I'm not imagining too many things. thankz, barry bouwsma To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 01:59:50 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA06612 for freebsd-current-outgoing; Sat, 9 Jan 1999 01:59:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA06607 for ; Sat, 9 Jan 1999 01:59:47 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id KAA30138; Sat, 9 Jan 1999 10:00:04 GMT Date: Sat, 9 Jan 1999 10:00:04 +0000 (GMT) From: Doug Rabson To: Karl Pielorz cc: John Polstra , current@FreeBSD.ORG Subject: Re: dmesg: namelist: msgbufp not found? In-Reply-To: <36970E00.8215AE29@tdx.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 9 Jan 1999, Karl Pielorz wrote: > > > John Polstra wrote: > > > > In article <3695D539.FCDBE542@tdx.co.uk>, > > Karl Pielorz wrote: > > > > > > I only have 2 problems with it, the first of which is when I run dmesg I get: > > > > > > caladan# dmesg > > > dmesg: namelist: msgbufp not found > > > > Hmm ... it works for me. Did you strip your kernel, perhaps? "file > > /kernel" will tell you whether it's stripped. > > Yes, I stripped it... I'm sure I'd already posted a reply to myself to say "I > found the problem"... :) > > Is there a way to strip it, and not break it? - I used to use "strip -d -aout > kernel", which doesn't work anymore :( (the elves don't like it)... > > Although I'm not short of memory, running a 7Mb kernel can't b too healthy... > :) Try 'strip -g'. -- 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 Sat Jan 9 03:44:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA19565 for freebsd-current-outgoing; Sat, 9 Jan 1999 03:44:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from k6n1.znh.org (dialup2.gaffaneys.com [208.155.161.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA19559 for ; Sat, 9 Jan 1999 03:44:30 -0800 (PST) (envelope-from zach@gaffaneys.com) Received: (from zach@localhost) by k6n1.znh.org (8.9.1/8.9.1) id LAA65223; Sat, 9 Jan 1999 11:45:16 GMT (envelope-from zach) Message-ID: <19990109054516.A64005@znh.org> Date: Sat, 9 Jan 1999 05:45:16 -0600 From: Zach Heilig To: Karl Pielorz , John Polstra Cc: current@FreeBSD.ORG Subject: Re: dmesg: namelist: msgbufp not found? References: <199901090628.WAA45726@vashon.polstra.com> <36970E00.8215AE29@tdx.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <36970E00.8215AE29@tdx.co.uk>; from Karl Pielorz on Sat, Jan 09, 1999 at 08:06:24AM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 09, 1999 at 08:06:24AM +0000, Karl Pielorz wrote: > Is there a way to strip it, and not break it? - I used to use "strip -d -aout > kernel", which doesn't work anymore :( (the elves don't like it)... > Although I'm not short of memory, running a 7Mb kernel can't b too healthy... > :) $ strip --strip-debug kernel -- Zach Heilig (zach@gaffaneys.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 05:29:16 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA28736 for freebsd-current-outgoing; Sat, 9 Jan 1999 05:29:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA28728 for ; Sat, 9 Jan 1999 05:29:09 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (peter@localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Netplex) with ESMTP id VAA49489; Sat, 9 Jan 1999 21:28:10 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199901091328.VAA49489@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Zach Heilig cc: Karl Pielorz , John Polstra , current@FreeBSD.ORG Subject: Re: dmesg: namelist: msgbufp not found? In-reply-to: Your message of "Sat, 09 Jan 1999 05:45:16 CST." <19990109054516.A64005@znh.org> Date: Sat, 09 Jan 1999 21:28:09 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Zach Heilig wrote: > On Sat, Jan 09, 1999 at 08:06:24AM +0000, Karl Pielorz wrote: > > Is there a way to strip it, and not break it? - I used to use "strip -d -ao ut > > kernel", which doesn't work anymore :( (the elves don't like it)... > > > Although I'm not short of memory, running a 7Mb kernel can't b too healthy. .. > > :) > > $ strip --strip-debug kernel Just as a BTW; this will become unnecessary soon and plain strip will work. At the moment, kvm_mkdb reads the kernel namelist and stores it at bootup. This is no longer good enough as the namelist changes when things are loaded and unloaded, and the kernel keeps a hashed lookup symbol table itself already. It would make sense for kvm_nlist() to look this up directly and always get the correct and current values. > -- > Zach Heilig (zach@gaffaneys.com) Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 05:29:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA28756 for freebsd-current-outgoing; Sat, 9 Jan 1999 05:29:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bleep.ishiboo.com (bleep.ishiboo.com [199.79.133.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA28750 for ; Sat, 9 Jan 1999 05:29:25 -0800 (PST) (envelope-from nirva@ishiboo.com) Received: (qmail 22782 invoked by uid 1000); 9 Jan 1999 13:28:47 -0000 Message-ID: <19990109082847.15715@bleep.ishiboo.com> Date: Sat, 9 Jan 1999 08:28:47 -0500 From: Danny Dulai To: "David W. Chapman Jr." Cc: freebsd-current Subject: Re: VPN References: <3696C28D.5833790C@houabg.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <3696C28D.5833790C@houabg.com>; from David W. Chapman Jr. on Fri, Jan 08, 1999 at 08:44:29PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting David W. Chapman Jr. (dchapman@houabg.com): > Does anyone know how to setup VPN or PPTP on freebsd? I have a setup working with ppp over ssh. Scripts, netmap and ipfw info are available at http://www.ishiboo.com/~nirva/vpn/. I had most of an OpenBSD<-->FreeBSD w/ OpenBSD IPSec patches VPN working, but the port of the patches seems to have broken something, and i can't get it all working.. KAME didnt support tunneling last I looked, maybe it does now... http://www.kame.net. -- ___________________________________________________________________________ Danny Dulai Feet. Pumice. Lotion. http://www.ishiboo.com/~nirva/ nirva@ishiboo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 06:17:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA03539 for freebsd-current-outgoing; Sat, 9 Jan 1999 06:17:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA03534 for ; Sat, 9 Jan 1999 06:17:33 -0800 (PST) (envelope-from itojun@itojun.org) Received: from kiwi.itojun.org (itojun@localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.1+3.1W/3.7W) with ESMTP id XAA12073; Sat, 9 Jan 1999 23:16:17 +0900 (JST) To: Danny Dulai cc: freebsd-current In-reply-to: nirva's message of Sat, 09 Jan 1999 08:28:47 EST. <19990109082847.15715@bleep.ishiboo.com> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: VPN From: Jun-ichiro itojun Hagino Date: Sat, 09 Jan 1999 23:16:17 +0900 Message-ID: <12069.915891377@coconut.itojun.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Does anyone know how to setup VPN or PPTP on freebsd? >I have a setup working with ppp over ssh. Scripts, netmap and ipfw info >are available at http://www.ishiboo.com/~nirva/vpn/. >I had most of an OpenBSD<-->FreeBSD w/ OpenBSD IPSec patches VPN working, >but the port of the patches seems to have broken something, and i can't >get it all working.. KAME didnt support tunneling last I looked, maybe >it does now... http://www.kame.net. We have two variants of KAME patch kit ready for you for doing VPN, one is ongoing: for FreeBSD 2.2.8-RELEASE, IPsec and/or IPv6 (you can disable IPv6 if you want to) for FreeBSD 3.0-RELEASE, IPsec only for FreeBSD 3.0-RELEASE, IPsec and/or IPv6 (ongoing, soon be released) Take a look at ftp.kame.net and www.kame.net for details. We are able to do, of course, IPsec tunnels over IPv4. IPsec tunnels over IPv6 will be finalized after we are sure that our design for IPv4 case works right for every situations possible. (tunnels are ugly thing...) itojun, KAME project --- algorithms we support 4.3 Conformance to RFCs and IDs The IPsec code in the kernel conforms (or, tries to conform) to the following standards: "old IPsec" specification documented in rfc182[5-9].txt "new IPsec" specification documented in rfc240[1-6].txt, rfc241[01].txt, rfc2451.txt and draft-mcdonald-simple-ipsec-api-01.txt. (NOTE: IKE specifications, rfc241[7-9].txt are implemented in userland, as "racoon" IKE daemon) Currently supported algorithms are: old IPsec AH null crypto checksum (no document, just for debugging) keyed MD5 with 128bit crypto checksum (rfc1828.txt) keyed SHA1 with 128bit crypto checksum (no document) HMAC MD5 with 128bit crypto checksum (rfc2085.txt) HMAC SHA1 with 128bit crypto checksum (no document) old IPsec ESP null encryption (no document, similar to rfc2410.txt) DES-CBC mode (rfc1829.txt) new IPsec AH null crypto checksum (no document, just for debugging) keyed MD5 with 96bit crypto checksum (no document) keyed SHA1 with 96bit crypto checksum (no document) HMAC MD5 with 96bit crypto checksum (rfc2403.txt HMAC SHA1 with 96bit crypto checksum (rfc2404.txt) new IPsec ESP null encryption (rfc2410.txt) DES-CBC with derived IV (draft-ietf-ipsec-ciph-des-derived-01.txt, draft expired) DES-CBC with explicit IV (rfc2405.txt) 3DES-CBC with explicit IV (rfc2451.txt) BLOWFISH CBC (rfc2451.txt) CAST128 CBC (rfc2451.txt) RC5 CBC (rfc2451.txt) each of the above can be combined with: ESP authentication with HMAC-MD5(96bit) ESP authentication with HMAC-SHA1(96bit) The following algorithms are NOT supported: old IPsec AH HMAC MD5 with 128bit crypto checksum + 64bit replay prevention (rfc2085.txt) keyed SHA1 with 160bit crypto checksum + 32bit padding (rfc1852.txt) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 06:19:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA03636 for freebsd-current-outgoing; Sat, 9 Jan 1999 06:19:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA03630 for ; Sat, 9 Jan 1999 06:19:13 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id OAA19816; Sat, 9 Jan 1999 14:22:06 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Sat, 9 Jan 1999 14:22:06 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Mike Smith cc: Robert Nordier , jkh@zippy.cdrom.com, dillon@apollo.backplane.com, andreas@klemm.gtn.com, current@FreeBSD.ORG Subject: Re: can't boot from CD and floppy after make release In-Reply-To: <199901082341.PAA00974@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 8 Jan 1999, Mike Smith wrote: > > > > > > It'd definitely be useful for the PicoBSD people, and anyone else that > > > didn't need the loader's functionality. I'd also be interested in > > > knowing if you have any compression/decompression tools suitable for > > > use with BTX eg. to compress the application data/expand it when BTX > > > relocates. > > > > I quite like Jordan's suggestion of kzip'ing the loader. The > > compression is not especially efficient: > > > > -r-xr-xr-x 1 rnordier wheel 122880 Jan 3 23:55 loader > > -rwxr-xr-x 1 rnordier wheel 70760 Jan 8 23:05 loader.kz > > > > but boot1/boot2 don't have a problem with loader.kz. > > It's actually not that bad; there's 12k of overhead for the kzip parts, > which is why I was wondering if you had something more compact... > Kzip is certainly a feasible interim solution, but it relies on the > a.out tool chain which makes it a weak link. Not only that - when you kzip the bootloader, you end up having the same gunzip routines twice: one in the kzip stubs, and the second in the loader. The word "superfluous" comes to mind... Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 06:37:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA04605 for freebsd-current-outgoing; Sat, 9 Jan 1999 06:37:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA04600 for ; Sat, 9 Jan 1999 06:37:30 -0800 (PST) (envelope-from rock@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.2/1999010400) with ESMTP id PAA12351 for ; Sat, 9 Jan 1999 15:36:49 +0100 (CET) Received: from wurzelausix.cs.uni-sb.de (quadratix.cs.uni-sb.de [134.96.222.2]) by cs.uni-sb.de (8.9.2/1999010400) with ESMTP id PAA19605 for ; Sat, 9 Jan 1999 15:36:48 +0100 (CET) Received: (from rock@localhost) by wurzelausix.cs.uni-sb.de (8.9.1/wjp/19980821) id PAA27357 for current@FreeBSD.ORG; Sat, 9 Jan 1999 15:36:48 +0100 (CET) Date: Sat, 9 Jan 1999 15:36:48 +0100 (CET) From: "D. Rock" Message-Id: <199901091436.PAA27357@wurzelausix.cs.uni-sb.de> To: current@FreeBSD.ORG Subject: Re: boot single with new loader? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You can't enable soft updates from single user; the disk has to be completely > unmounted. Either boot from a floppy, and run it on the hard disk, or do > what I did (being to lazy to make a floppy), and boot the machine; run > tunefs on the live disk, type sync 5 times, and smack the power switch. Did I miss something. I always enabled soft updates on my root fs by booting into single user mode, tunefs -n enable /dev/r.... Press reset. Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 06:47:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA05589 for freebsd-current-outgoing; Sat, 9 Jan 1999 06:47:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from out2.ibm.net (out2.ibm.net [165.87.194.229]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA05582 for ; Sat, 9 Jan 1999 06:47:53 -0800 (PST) (envelope-from dwilde1@ibm.net) Received: from ibm.net (slip-32-100-60-106.nm.us.ibm.net [32.100.60.106]) by out2.ibm.net (8.8.5/8.6.9) with ESMTP id OAA118942 for ; Sat, 9 Jan 1999 14:47:21 GMT Message-ID: <36975C4F.AD73DED2@ibm.net> Date: Sat, 09 Jan 1999 06:40:31 -0700 From: Don Wilde Reply-To: dwilde1@ibm.net X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: expanded errata pages Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'd like to make a request that the errata.txt pages on the website be expanded to cover the entire distribution, not just the base code called 'FreeBSD'. Given that I'm still a naive user after years of use, I installed 3.0 on a machine to play with. Nothing special, and it worked as advertised until I installed X and lots of packages... Strange, that sure doesn't look like fvwm... It turns out (after searching through -current archives) that whoever assembled the ports tree for 3.0 built it with Kerberos installed, and that there's a silly little library that damn near every X program needs now that isn't normally installed. Yes, I built it, and yes, I'm okay now, but I think that's a gotcha that should be avoided in the future. I know you -core guys are working your ASCII's off just getting this out the door, and I REALLY APPRECIATE all that the FreeBSD Project (and WCCDROM) are doing. Please take this as just a gentle hint, not a screaming fit, because I have read all the previous warnings about being ready to accept such gotchas before running -CURRENT. TNX! Now back to your regularly-scheduled programming.... D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 07:00:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06748 for freebsd-current-outgoing; Sat, 9 Jan 1999 07:00:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www.giovannelli.it (www.giovannelli.it [194.184.65.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA06743 for ; Sat, 9 Jan 1999 07:00:10 -0800 (PST) (envelope-from gmarco@giovannelli.it) Received: from giovannelli.it (modem37.masternet.it [194.184.65.47]) by www.giovannelli.it (8.8.8/8.8.5) with ESMTP id PAA00411 for ; Sat, 9 Jan 1999 15:59:32 +0100 (MET) Message-ID: <369760D4.59D70D2C@giovannelli.it> Date: Sat, 09 Jan 1999 14:59:48 +0100 From: Gianmarco Giovannelli X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: make world fails Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After cvsupping this morning (CET) make world fails on : "bootstrap loader" cc -c vers.c cc -nostdlib -static -Ttext 0x1000 -o loader.sym /usr/obj/elf/usr/src/sys/boot/i386/loader/../btx/lib/crt0.o main.o conf.o bcache.o boot.o commands.o console.o devopen.o interp.o interp_backslash.o interp_parse.o load_aout.o load_elf.o ls.o misc.o module.o panic.o isapnp.o pnp.o interp_forth.o vers.o /usr/obj/elf/usr/src/sys/boot/i386/loader/../../ficl/libficl.a -lstand /usr/obj/elf/usr/src/sys/boot/i386/loader/../libi386/libi386.a -lstand cp loader.sym loader.bin strip loader.bin perl /usr/src/sys/boot/i386/loader/../../common/merge_help.pl /usr/src/sys/boot/i386/loader/../../common/help.common /usr/src/sys/boot/i386/loader/help.i386 > loader.help btxld -v -f aout -e 0x100000 -o loader -l /usr/obj/elf/usr/src/sys/boot/i386/loader/../btx/btxldr/btxldr -b /usr/obj/elf/usr/src/sys/boot/i386/loader/../btx/btx/btx loader.bin kernel: ver=0.87 size=6d0 load=9000 entry=9010 map=16M pgctl=1:18 client: fmt=elf size=1b024 text=178cf data=1760 bss=1968 entry=1000 output: fmt=aout size=1e000 text=1000 data=1c000 org=100000 entry=100000 kzip loader kzip: not found *** Error code 1 Thanks for attention.... -- Regards... Gianmarco "Unix expert since yesterday" http://www.giovannelli.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 07:51:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA11170 for freebsd-current-outgoing; Sat, 9 Jan 1999 07:51:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA11163 for ; Sat, 9 Jan 1999 07:51:17 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id KAA07206; Sat, 9 Jan 1999 10:50:42 -0500 (EST) (envelope-from wollman) Date: Sat, 9 Jan 1999 10:50:42 -0500 (EST) From: Garrett Wollman Message-Id: <199901091550.KAA07206@khavrinen.lcs.mit.edu> To: Bryan Seitz Cc: current@FreeBSD.ORG Subject: FreeBSD Celeron and Celeron ( Mendocino ) kernel patch. In-Reply-To: <4.1.19990108200358.009a82c0@10.0.0.1> References: <4.1.19990108200358.009a82c0@10.0.0.1> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Hi, I was messing around with a new machine the other day when I decided to > install > FreeBSD 3.0-CURRENT. I've got a celeron 300a in it running at 450Mhz. Since I don't believe it is useful to make any distinction between different flavors of Pentium II, since they all (for the time being) share the exact instruction-set architecture and feature set. Just because Intel's marketing department wants you to believe something, doesn't mean it's true. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 08:10:53 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA12453 for freebsd-current-outgoing; Sat, 9 Jan 1999 08:10:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA12448 for ; Sat, 9 Jan 1999 08:10:50 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac8.wam.umd.edu ((IDENT root)@rac8.wam.umd.edu [128.8.10.148]) by po4.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id LAA17158; Sat, 9 Jan 1999 11:11:22 -0500 (EST) Received: from rac8.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1]) by rac8.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id LAA02857; Sat, 9 Jan 1999 11:09:51 -0500 (EST) Received: from localhost by rac8.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id LAA02852; Sat, 9 Jan 1999 11:09:50 -0500 (EST) X-Authentication-Warning: rac8.wam.umd.edu: culverk owned process doing -bs Date: Sat, 9 Jan 1999 11:09:50 -0500 (EST) From: Kenneth Wayne Culver To: Gianmarco Giovannelli cc: current@FreeBSD.ORG Subject: Re: make world fails In-Reply-To: <369760D4.59D70D2C@giovannelli.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 9 Jan 1999, Gianmarco Giovannelli wrote: > After cvsupping this morning (CET) make world fails on : > > "bootstrap loader" > cc -c vers.c > cc -nostdlib -static -Ttext 0x1000 -o loader.sym > /usr/obj/elf/usr/src/sys/boot/i386/loader/../btx/lib/crt0.o main.o > conf.o bcache.o boot.o commands.o console.o devopen.o interp.o > interp_backslash.o interp_parse.o load_aout.o load_elf.o ls.o misc.o > module.o panic.o isapnp.o pnp.o interp_forth.o vers.o > /usr/obj/elf/usr/src/sys/boot/i386/loader/../../ficl/libficl.a -lstand > /usr/obj/elf/usr/src/sys/boot/i386/loader/../libi386/libi386.a -lstand > cp loader.sym loader.bin > strip loader.bin > perl /usr/src/sys/boot/i386/loader/../../common/merge_help.pl > /usr/src/sys/boot/i386/loader/../../common/help.common > /usr/src/sys/boot/i386/loader/help.i386 > loader.help > btxld -v -f aout -e 0x100000 -o loader -l > /usr/obj/elf/usr/src/sys/boot/i386/loader/../btx/btxldr/btxldr -b > /usr/obj/elf/usr/src/sys/boot/i386/loader/../btx/btx/btx loader.bin > kernel: ver=0.87 size=6d0 load=9000 entry=9010 map=16M pgctl=1:18 > client: fmt=elf size=1b024 text=178cf data=1760 bss=1968 entry=1000 > output: fmt=aout size=1e000 text=1000 data=1c000 org=100000 entry=100000 > kzip loader > kzip: not found > *** Error code 1 > > Thanks for attention.... > > -- > to fix this, go to /usr/src/sys/boot/i386/loader, and edit the Makefile. where it says kzip, change it to /usr/bin/kzip I had the same problem, and that is how I fixed it. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 08:13:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA12609 for freebsd-current-outgoing; Sat, 9 Jan 1999 08:13:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA12604 for ; Sat, 9 Jan 1999 08:12:58 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac8.wam.umd.edu ((IDENT root)@rac8.wam.umd.edu [128.8.10.148]) by po3.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id LAA29114; Sat, 9 Jan 1999 11:12:24 -0500 (EST) Received: from rac8.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1]) by rac8.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id LAA03104; Sat, 9 Jan 1999 11:12:21 -0500 (EST) Received: from localhost by rac8.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id LAA03099; Sat, 9 Jan 1999 11:12:20 -0500 (EST) X-Authentication-Warning: rac8.wam.umd.edu: culverk owned process doing -bs Date: Sat, 9 Jan 1999 11:12:20 -0500 (EST) From: Kenneth Wayne Culver To: Garrett Wollman cc: Bryan Seitz , current@FreeBSD.ORG Subject: Re: FreeBSD Celeron and Celeron ( Mendocino ) kernel patch. In-Reply-To: <199901091550.KAA07206@khavrinen.lcs.mit.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 Sat, 9 Jan 1999, Garrett Wollman wrote: > < said: > > > Hi, I was messing around with a new machine the other day when I decided to > > install > > FreeBSD 3.0-CURRENT. I've got a celeron 300a in it running at 450Mhz. Since > > I don't believe it is useful to make any distinction between different > flavors of Pentium II, since they all (for the time being) share the > exact instruction-set architecture and feature set. Just because > Intel's marketing department wants you to believe something, doesn't > mean it's true. > Well, they are the same in that respect, but the Pentium II has cache in the same package, and most Pentium II's aren't overclockable. The celeron is. Kenneth Culver Computer Science Major at the University of Maryland, College Park. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 08:22:39 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA13532 for freebsd-current-outgoing; Sat, 9 Jan 1999 08:22:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA13527 for ; Sat, 9 Jan 1999 08:22:38 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id LAA07272; Sat, 9 Jan 1999 11:22:06 -0500 (EST) (envelope-from wollman) Date: Sat, 9 Jan 1999 11:22:06 -0500 (EST) From: Garrett Wollman Message-Id: <199901091622.LAA07272@khavrinen.lcs.mit.edu> To: Kenneth Wayne Culver Cc: Garrett Wollman , Bryan Seitz , current@FreeBSD.ORG Subject: Re: FreeBSD Celeron and Celeron ( Mendocino ) kernel patch. In-Reply-To: References: <199901091550.KAA07206@khavrinen.lcs.mit.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Well, they are the same in that respect, but the Pentium II has cache in > the same package, and most Pentium II's aren't overclockable. The celeron > is. That's OK -- we don't support overclocking anyway. The Celeron does have a cache in the package, BTW. The cache in the Celeron is this tiny little thing that is actually capable of running at clock rates of 250 MHz or higher; the actual CPU is a perfectly ordinary Pentium-II core of the sort that would be labeled as ``450 MHz'' when coupled with a more expensive cache. (According to my friend who does VLSI design.) The Celeron chips are intentionally down-rated by Intel marketing to keep them from cannibalizing the high-end market. (Remember when upgrading to a faster line printer meant that a SE would change a single belt?) I think we should stick to identifying the core. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 08:35:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA14448 for freebsd-current-outgoing; Sat, 9 Jan 1999 08:35:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA14442 for ; Sat, 9 Jan 1999 08:35:55 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id RAA17098; Sat, 9 Jan 1999 17:33:23 +0100 (CET) To: Garrett Wollman cc: Kenneth Wayne Culver , Bryan Seitz , current@FreeBSD.ORG Subject: Re: FreeBSD Celeron and Celeron ( Mendocino ) kernel patch. In-reply-to: Your message of "Sat, 09 Jan 1999 11:22:06 EST." <199901091622.LAA07272@khavrinen.lcs.mit.edu> Date: Sat, 09 Jan 1999 17:33:23 +0100 Message-ID: <17096.915899603@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199901091622.LAA07272@khavrinen.lcs.mit.edu>, Garrett Wollman writes: >I think we should stick to identifying the core. I think we should follow the precedent from the vga PCI driver. -- 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 Sat Jan 9 08:59:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16802 for freebsd-current-outgoing; Sat, 9 Jan 1999 08:59:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA16656 for ; Sat, 9 Jan 1999 08:59:18 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac10.wam.umd.edu ((IDENT root)@rac10.wam.umd.edu [128.8.10.150]) by po4.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id MAA18528; Sat, 9 Jan 1999 12:00:15 -0500 (EST) Received: from rac10.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1]) by rac10.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id LAA09925; Sat, 9 Jan 1999 11:58:44 -0500 (EST) Received: from localhost by rac10.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id LAA09920; Sat, 9 Jan 1999 11:58:43 -0500 (EST) X-Authentication-Warning: rac10.wam.umd.edu: culverk owned process doing -bs Date: Sat, 9 Jan 1999 11:58:42 -0500 (EST) From: Kenneth Wayne Culver To: Garrett Wollman cc: Bryan Seitz , current@FreeBSD.ORG Subject: Re: FreeBSD Celeron and Celeron ( Mendocino ) kernel patch. In-Reply-To: <199901091622.LAA07272@khavrinen.lcs.mit.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 > < said: > > > Well, they are the same in that respect, but the Pentium II has cache in > > the same package, and most Pentium II's aren't overclockable. The celeron > > is. > > That's OK -- we don't support overclocking anyway. > > The Celeron does have a cache in the package, BTW. The cache in the > Celeron is this tiny little thing that is actually capable of running > at clock rates of 250 MHz or higher; the actual CPU is a perfectly > ordinary Pentium-II core of the sort that would be labeled as ``450 > MHz'' when coupled with a more expensive cache. (According to my > friend who does VLSI design.) The Celeron chips are intentionally > down-rated by Intel marketing to keep them from cannibalizing the > high-end market. (Remember when upgrading to a faster line printer > meant that a SE would change a single belt?) > > I think we should stick to identifying the core. I wasn't disagreeing with that, I was just saying what I said about the cache. Intel would have you believe that there is not any cache on the Celeron. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 09:02:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA17161 for freebsd-current-outgoing; Sat, 9 Jan 1999 09:02:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17150 for ; Sat, 9 Jan 1999 09:02:09 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac10.wam.umd.edu ((IDENT root)@rac10.wam.umd.edu [128.8.10.150]) by po4.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id MAA18568 for ; Sat, 9 Jan 1999 12:03:07 -0500 (EST) Received: from rac10.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1]) by rac10.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id MAA10138 for ; Sat, 9 Jan 1999 12:01:36 -0500 (EST) Received: from localhost by rac10.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id MAA10126 for ; Sat, 9 Jan 1999 12:01:35 -0500 (EST) X-Authentication-Warning: rac10.wam.umd.edu: culverk owned process doing -bs Date: Sat, 9 Jan 1999 12:01:35 -0500 (EST) From: Kenneth Wayne Culver To: freebsd-current@FreeBSD.ORG Subject: Build 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 I read about the -DNOAOUT option, but the Makefile doesn't tell me where to specify that. Do I just type: make -DNOAOUT world if not could someone let me know? Thanks. Kenneth Culver Computer Science Major at the University of Maryland, College Park. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 09:02:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA17216 for freebsd-current-outgoing; Sat, 9 Jan 1999 09:02:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA17199 for ; Sat, 9 Jan 1999 09:02:17 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 13816 invoked by uid 1001); 9 Jan 1999 17:01:44 +0000 (GMT) To: culverk@wam.umd.edu Cc: wollman@khavrinen.lcs.mit.edu, phiber@udel.edu, current@FreeBSD.ORG Subject: Re: FreeBSD Celeron and Celeron ( Mendocino ) kernel patch. In-Reply-To: Your message of "Sat, 9 Jan 1999 11:58:42 -0500 (EST)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 09 Jan 1999 18:01:43 +0100 Message-ID: <13814.915901303@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I wasn't disagreeing with that, I was just saying what I said about the > cache. Intel would have you believe that there is not any cache on the > Celeron. There are different Celeron models. The new models (300A, 333A etc.) have 128 kB L2 cache on the chip. The old (non-A) models *do not* have any L2 cache. AFAIK Intel has never made any secret about this. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 09:20:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18484 for freebsd-current-outgoing; Sat, 9 Jan 1999 09:20:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA18470 for ; Sat, 9 Jan 1999 09:20:02 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id EAA10820; Sun, 10 Jan 1999 04:19:17 +1100 Date: Sun, 10 Jan 1999 04:19:17 +1100 From: Bruce Evans Message-Id: <199901091719.EAA10820@godzilla.zeta.org.au> To: phk@critter.freebsd.dk, wollman@khavrinen.lcs.mit.edu Subject: Re: FreeBSD Celeron and Celeron ( Mendocino ) kernel patch. Cc: culverk@wam.umd.edu, current@FreeBSD.ORG, phiber@udel.edu Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>I think we should stick to identifying the core. > >I think we should follow the precedent from the vga PCI driver. I think we should follow the precedent from the sysctl error messages. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 09:22:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18931 for freebsd-current-outgoing; Sat, 9 Jan 1999 09:22:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA18922 for ; Sat, 9 Jan 1999 09:22:44 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac7.wam.umd.edu ((IDENT root)@rac7.wam.umd.edu [128.8.10.147]) by po4.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id MAA19196; Sat, 9 Jan 1999 12:23:37 -0500 (EST) Received: from rac7.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1]) by rac7.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id MAA09413; Sat, 9 Jan 1999 12:22:06 -0500 (EST) Received: from localhost by rac7.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id MAA09408; Sat, 9 Jan 1999 12:22:05 -0500 (EST) X-Authentication-Warning: rac7.wam.umd.edu: culverk owned process doing -bs Date: Sat, 9 Jan 1999 12:22:05 -0500 (EST) From: Kenneth Wayne Culver To: sthaug@nethelp.no cc: wollman@khavrinen.lcs.mit.edu, phiber@udel.edu, current@FreeBSD.ORG Subject: Re: FreeBSD Celeron and Celeron ( Mendocino ) kernel patch. In-Reply-To: <13814.915901303@verdi.nethelp.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 9 Jan 1999 sthaug@nethelp.no wrote: > > I wasn't disagreeing with that, I was just saying what I said about the > > cache. Intel would have you believe that there is not any cache on the > > Celeron. > > There are different Celeron models. The new models (300A, 333A etc.) have > 128 kB L2 cache on the chip. The old (non-A) models *do not* have any L2 > cache. Oh, sorry to bother about that then. I don't follow intel too closely, since I am eagerly waiting for the AMD K7 to arrive. Kenneth culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 09:45:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20515 for freebsd-current-outgoing; Sat, 9 Jan 1999 09:45:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kendra.ne.mediaone.net (kendra.ne.mediaone.net [24.128.94.182]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA20510 for ; Sat, 9 Jan 1999 09:45:23 -0800 (PST) (envelope-from software@kew.com) Received: from sonata.hh.kew.com (root@sonata-dmz.hh.kew.com [192.168.205.1]) by kendra.ne.mediaone.net (8.9.1/8.9.1) with ESMTP id MAA08410; Sat, 9 Jan 1999 12:44:52 -0500 (EST) Received: from kew.com (minerva.hh.kew.com [192.168.203.144]) by sonata.hh.kew.com (8.9.1/8.9.1) with ESMTP id MAA19117; Sat, 9 Jan 1999 12:44:51 -0500 (EST) Message-ID: <36979592.1FCFB1EC@kew.com> Date: Sat, 09 Jan 1999 12:44:50 -0500 From: Drew Derbyshire Organization: Kendra Electronic Wonderworks, Stoneham, MA 02180 (http://www.kew.com) X-Mailer: Mozilla 4.5 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Kenneth Wayne Culver CC: Tom Torrance , current@FreeBSD.ORG Subject: Re: ATAPI - no HEADS UP? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kenneth Wayne Culver wrote: > > It appears that a new driver has been implemented that > > requires ATAPI drives to be defined as acd0 rather than > > the old wcd0. > > It would be nice for consistancy for MAKEDEV to support > > 'MAKEDEV acd0' or whatever... > > It is not needed, the old wcd name in /dev works fine. But very desirable. If acd0 is the correct name, MAKEDEV should support it. -- Drew Derbyshire UUPC/extended e-mail: software@kew.com Telephone: 617-279-9812 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 10:17:59 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA23257 for freebsd-current-outgoing; Sat, 9 Jan 1999 10:17:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news2.du.gtn.com (news2.du.gtn.com [194.77.9.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA23248 for ; Sat, 9 Jan 1999 10:17:55 -0800 (PST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely.de [194.231.9.142]) by news2.du.gtn.com (8.8.6/8.8.6) with ESMTP id TAA21496 for ; Sat, 9 Jan 1999 19:17:18 +0100 (MET) Received: (from ticso@localhost) by cicely7.cicely.de (8.9.0/8.9.0) id TAA51346; Sat, 9 Jan 1999 19:17:19 +0100 (CET) Message-ID: <19990109191719.07005@cicely.de> Date: Sat, 9 Jan 1999 19:17:19 +0100 From: Bernd Walter To: freebsd-current@FreeBSD.ORG Subject: panicstr: ffs_valloc: dup alloc Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG System is current of about 6.12.1998 IdlePTD 2867200 initial pcb at 25603c panicstr: ffs_valloc: dup alloc panic messages: --- panic: ffs_valloc: dup alloc syncing disks... 29 26 15 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 giving up (da0:ahc0:0:2:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 (da0:ahc0:0:2:0): ILLEGAL REQUEST asc:20,0 (da0:ahc0:0:2:0): Invalid command operation code [...] (da24:ahc4:0:2:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 (da24:ahc4:0:2:0): ILLEGAL REQUEST asc:20,0 (da24:ahc4:0:2:0): Invalid command operation code dumping to dev 431, offset 633732 dump 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:285 285 dumppcb.pcb_cr3 = rcr3(); asf 0x0 #0 boot (howto=0x100) at ../../kern/kern_shutdown.c:285 #1 0xf014607d in panic (fmt=0xf01cbd46 "ffs_valloc: dup alloc") at ../../kern/kern_shutdown.c:446 #2 0xf01cbeac in ffs_valloc (pvp=0xfb96c300, mode=0x41ed, cred=0xf1d29200, vpp=0xfb85ad50) at ../../ufs/ffs/ffs_alloc.c:605 #3 0xf01deeca in ufs_mkdir (ap=0xfb85ae98) at ../../ufs/ufs/ufs_vnops.c:1298 #4 0xf01dff41 in ufs_vnoperate (ap=0xfb85ae98) at ../../ufs/ufs/ufs_vnops.c:2291 #5 0xf016e472 in mkdir (p=0xfb7e8700, uap=0xfb85af94) at vnode_if.h:611 #6 0xf0201baf in syscall (frame={tf_es = 0x27, tf_ds = 0x27, tf_edi = 0xffffffff, tf_esi = 0x19, tf_ebp = 0xefbfdb34, tf_isp = 0xfb85afe4, tf_ebx = 0x1, tf_edx = 0xffffffff, tf_ecx = 0x806d600, tf_eax = 0x88, tf_trapno = 0x7, tf_err = 0x2, tf_eip = 0x804a3f0, tf_cs = 0x1f, tf_eflags = 0x206, tf_esp = 0xefbfdaac, tf_ss = 0x27}) at ../../i386/i386/trap.c:1063 #7 0xf01f72fc in Xint0x80_syscall () #8 0x804854b in ?? () #9 0x80480c9 in ?? () It was the first time I got this panic. -- B.Walter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 10:36:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA25626 for freebsd-current-outgoing; Sat, 9 Jan 1999 10:36:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thing.dyn.ml.org (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA25570 for ; Sat, 9 Jan 1999 10:35:57 -0800 (PST) (envelope-from bsdx@spawnet.com) Received: from spawnet.com (bsdx [192.168.1.2]) by thing.dyn.ml.org (8.9.1/8.8.7) with ESMTP id NAA18761 for ; Sat, 9 Jan 1999 13:35:27 -0500 (EST) (envelope-from bsdx@spawnet.com) Message-ID: <3697A16C.3F6B7761@spawnet.com> Date: Sat, 09 Jan 1999 13:35:24 -0500 From: Adam McDougall X-Mailer: Mozilla 4.06 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: FreeBSD Celeron and Celeron ( Mendocino ) kernel patch. References: <4.1.19990108200358.009a82c0@10.0.0.1> <199901091550.KAA07206@khavrinen.lcs.mit.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garrett Wollman wrote: > > < said: > > > Hi, I was messing around with a new machine the other day when I decided to > > install > > FreeBSD 3.0-CURRENT. I've got a celeron 300a in it running at 450Mhz. Since > > I don't believe it is useful to make any distinction between different > flavors of Pentium II, since they all (for the time being) share the > exact instruction-set architecture and feature set. Just because > Intel's marketing department wants you to believe something, doesn't > mean it's true. > > -GAWollman I think it would be nice to at least have the kernel identify it as a pII, instead of 'Unknown 80686' which makes some people worry if its working right. Maybe then it could get more specific when booting with verbose(boot: -v), announcing celeron and if or if not it has cache. The reason it has its own case different from the other pII's is because (the models with it) have oncore fullspeed cache, whereas the normal pII's have off-core half-speed cache. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 10:53:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27532 for freebsd-current-outgoing; Sat, 9 Jan 1999 10:53:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from linux.udlug.org (dhcp14-10.superstream.net [24.40.10.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27525 for ; Sat, 9 Jan 1999 10:53:52 -0800 (PST) (envelope-from phiber@udel.edu) Received: from win98 (win98 [10.0.0.2]) by linux.udlug.org (8.9.2/8.8.7) with SMTP id NAA09164 for ; Sat, 9 Jan 1999 13:52:23 -0500 (EST) Message-Id: <4.1.19990109135236.009bfbf0@10.0.0.1> X-Sender: sysadmin@10.0.0.1 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sat, 09 Jan 1999 13:53:54 -0500 To: current@FreeBSD.ORG From: Bryan Seitz Subject: Celeron kernel Patch Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 01:35 PM 1/9/99 -0500, Adam McDougall wrote : >Garrett Wollman wrote: >> >> < said: >> >> > Hi, I was messing around with a new machine the other day when I decided to >> > install >> > FreeBSD 3.0-CURRENT. I've got a celeron 300a in it running at 450Mhz. >Since >> >> I don't believe it is useful to make any distinction between different >> flavors of Pentium II, since they all (for the time being) share the >> exact instruction-set architecture and feature set. Just because >> Intel's marketing department wants you to believe something, doesn't >> mean it's true. >> >> -GAWollman > >I think it would be nice to at least have the kernel identify it as a >pII, instead of 'Unknown 80686' which makes some people worry if its >working right. > >Maybe then it could get more specific when booting with verbose(boot: >-v), announcing celeron and if or if not it has cache. > >The reason it has its own case different from the other pII's is because >(the models with it) have oncore fullspeed cache, whereas the normal >pII's have off-core half-speed cache. > Finally a good post on this subject. That was my aim. Notice : CPU: Celeron (Mendocino) (451.03-MHz 686-class CPU) is still much better than CPU: Unknown (451.03-MHz 686-class CPU) If you have NO cache, ala, a 266 Celeron or Celeron 300 ( no A ), it would look like : CPU: Celeron (451.03-MHz 686-class CPU) I'd even like to put intel infront of the word celeron but hey. Either way, you don't have to like it. I wrote it for myself b/c I was sick of seeing unknown. The Celeron is different than a PII, so hence it is *not* really a complete PII. Sure you could make it say Pentium II, but I'd rather see that its a celeron, which is *WHY* intel gave it it's own ID. -B Bryan G. Seitz University of Delaware Computer Science http://linux.udlug.org "Linux is like a wigwam - no windows, no gates, apache inside!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 11:22:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA00915 for freebsd-current-outgoing; Sat, 9 Jan 1999 11:22:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA00909 for ; Sat, 9 Jan 1999 11:22:30 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac2.wam.umd.edu ((IDENT root)@rac2.wam.umd.edu [128.8.10.142]) by po4.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id OAA22599 for ; Sat, 9 Jan 1999 14:23:28 -0500 (EST) Received: from rac2.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1]) by rac2.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id OAA12804 for ; Sat, 9 Jan 1999 14:21:57 -0500 (EST) Received: from localhost by rac2.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id OAA12799 for ; Sat, 9 Jan 1999 14:21:56 -0500 (EST) X-Authentication-Warning: rac2.wam.umd.edu: culverk owned process doing -bs Date: Sat, 9 Jan 1999 14:21:56 -0500 (EST) From: Kenneth Wayne Culver To: freebsd-current@FreeBSD.ORG Subject: USER_LDT in Linux emulation Message-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 was wondering: has USER_LDT been incorporated into -current's Linux Emulation? Kenneth Culver Computer Science Major at the University of Maryland, College Park. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 11:25:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA01155 for freebsd-current-outgoing; Sat, 9 Jan 1999 11:25:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa15-59.ix.netcom.com [207.93.148.59]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA01149 for ; Sat, 9 Jan 1999 11:25:11 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.1/8.8.8) id LAA03536; Sat, 9 Jan 1999 11:23:41 -0800 (PST) (envelope-from tomdean) Date: Sat, 9 Jan 1999 11:23:41 -0800 (PST) Message-Id: <199901091923.LAA03536@ix.netcom.com> From: Thomas Dean To: culverk@wam.umd.edu CC: freebsd-current@FreeBSD.ORG In-reply-to: (message from Kenneth Wayne Culver on Sat, 9 Jan 1999 12:01:35 -0500 (EST)) Subject: Re: Build World Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, make -DNOAOUT world works. You could alternately put it in /etc/make.conf To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 11:39:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA03283 for freebsd-current-outgoing; Sat, 9 Jan 1999 11:39:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA03276 for ; Sat, 9 Jan 1999 11:39:48 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id OAA02504; Sat, 9 Jan 1999 14:39:19 -0500 (EST) Date: Sat, 9 Jan 1999 14:39:19 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Kenneth Wayne Culver cc: freebsd-current@FreeBSD.ORG Subject: Re: USER_LDT in Linux emulation 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, 9 Jan 1999, Kenneth Wayne Culver wrote: > I was wondering: has USER_LDT been incorporated into -current's Linux > Emulation? > You probably mean the modify_ldt (?) syscall for Linux. No, that is not there, and I'm thinking maybe I should probably get it working... but in the meantime I had added syscall 183 and 184 (I can send the module, which needs -DCOMPAT_LINUX_THREADS in the kernel already, since I accidentally clobbered my changes with cvsup before). I was working with this to get WINE working under Linux emu, so I could use WINE threads (clone() working, of course), but I'm having EXTREMELY strange sendmsg() problems (I'll include a bit of transcript afterwards, maybe someone can help). Anyway, if you really want that syscall, I suggest looking at i386_[gs]et_ldt() and WINE's LDT translation code (Linux uses a weird struct to set the ldt, if you can convert from that you're all set). The best way would probably be to make i386_[gs]et_ldt() global, and do something like int linux_modify_ldt(struct proc *p, struct args *uap) { #ifdef USER_LDT long real_ldt[2]; real_ldt = convert_struct_linux_ldt; switch (uap->type) { case SET_LDT: return i386_set_ldt(real_ldt); case GET_LDT: return i386_set_ldt(real_ldt); default: return EINVAL; } #else printf("Linux emu(%d): LDT modification needs USER_LDT\n", p->p_pid); return ENOSYS; #endif } You should be able to find any of the Linux LDT info in wine-xxx/memory/ldt.c. > > > Kenneth Culver > Computer Science Major at the University of Maryland, College Park. > Brian Feldman Science and Technology Student at Oxon Hill High School, Oxon Hill, Maryland. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 11:42:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA03520 for freebsd-current-outgoing; Sat, 9 Jan 1999 11:42:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA03514 for ; Sat, 9 Jan 1999 11:41:58 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id OAA02629; Sat, 9 Jan 1999 14:41:29 -0500 (EST) Date: Sat, 9 Jan 1999 14:41:29 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Kenneth Wayne Culver cc: freebsd-current@FreeBSD.ORG Subject: Re: USER_LDT in Linux emulation 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 Whoops, didn't include the sendmsg() weirdness I need a bit of help with. {"/home/green/wine-990103"}$ ./wine socket: 3 struct msghdr: msg_name = (nil) msg_namelen = 0 msg_iov = 0xefbfd6e8 msg_iovlen = 2 msg_control = 0xefbfd6b0 msg_controllen = 16 msg_flags = 0 msghdr.msg_iov[0].iov_base = 0xefbfd688 msghdr.msg_iov[0].iov_len = 12 msghdr.msg_iov[1].iov_base = 0xefbfd790 msghdr.msg_iov[1].iov_len = 4 sendmsg: Invalid argument Client protocol error:(nil): partial msg sent -1/16 Memory fault (core dumped) {"/home/green/wine-990103"}$ Relevant code: LIENT_SendRequest_v * * Send a request to the server. */ static void CLIENT_SendRequest_v( enum request req, int pass_fd, struct iovec *vec, int veclen ) { THDB *thdb = THREAD_Current(); #ifndef HAVE_MSGHDR_ACCRIGHTS struct cmsg_fd cmsg = { sizeof(cmsg), SOL_SOCKET, SCM_RIGHTS, pass_fd }; #endif struct msghdr msghdr = { NULL, 0, vec, veclen, NULL, 0, 0}; struct header head; int i, ret, len; assert( veclen > 0 ); vec[0].iov_base = &head; vec[0].iov_len = sizeof(head); for (i = len = 0; i < veclen; i++) len += vec[i].iov_len; assert( len <= MAX_MSG_LENGTH ); head.type = req; head.len = len; head.seq = thdb->seq++; if (pass_fd != -1) /* we have an fd to send */ { #ifdef HAVE_MSGHDR_ACCRIGHTS msghdr.msg_accrights = (void *)&pass_fd; msghdr.msg_accrightslen = sizeof(pass_fd); #else msghdr.msg_control = &cmsg; msghdr.msg_controllen = sizeof(cmsg); #endif } printf("socket: %d\n" "struct msghdr:\n" "msg_name = %p\n" "msg_namelen = %d\n" "msg_iov = %p\n" "msg_iovlen = %d\n" "msg_control = %p\n" "msg_controllen = %d\n" "msg_flags = %d\n", thdb->socket, msghdr.msg_name, msghdr.msg_namelen, msghdr.msg_iov, msghdr.msg_iovlen, msghdr.msg_control, msghdr.msg_controllen, msghdr.msg_flags); { register struct iovec *iov = msghdr.msg_iov; int c; for (c = 0; c < msghdr.msg_iovlen; c++) printf("msghdr.msg_iov[%d].iov_base = %p\n" "msghdr.msg_iov[%d].iov_len = %d\n", c, iov[c].iov_base, c, iov[c].iov_len); } if ((ret = sendmsg( thdb->socket, &msghdr, 0 )) < len) { if (ret == -1) perror( "sendmsg" ); CLIENT_ProtocolError( "partial msg sent %d/%d\n", ret, len ); } /* we passed the fd now we can close it */ if (pass_fd != -1) close( pass_fd ); } Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 12:13:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07850 for freebsd-current-outgoing; Sat, 9 Jan 1999 12:13:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles156.castles.com [208.214.165.156]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07840 for ; Sat, 9 Jan 1999 12:13:25 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA00770; Sat, 9 Jan 1999 12:09:00 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901092009.MAA00770@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrzej Bialecki cc: Mike Smith , Robert Nordier , jkh@zippy.cdrom.com, dillon@apollo.backplane.com, andreas@klemm.gtn.com, current@FreeBSD.ORG Subject: Re: can't boot from CD and floppy after make release In-reply-to: Your message of "Sat, 09 Jan 1999 14:22:06 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 09 Jan 1999 12:09:00 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > It's actually not that bad; there's 12k of overhead for the kzip parts, > > which is why I was wondering if you had something more compact... > > > Kzip is certainly a feasible interim solution, but it relies on the > > a.out tool chain which makes it a weak link. > > Not only that - when you kzip the bootloader, you end up having the same > gunzip routines twice: one in the kzip stubs, and the second in the > loader. The word "superfluous" comes to mind... Actually, the routines are somewhat different, and the kzip inflater could be trimmed a little, but the kzip stub isn't going to come under 10k in a hurry. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 12:16:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08816 for freebsd-current-outgoing; Sat, 9 Jan 1999 12:16:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles156.castles.com [208.214.165.156]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA08791 for ; Sat, 9 Jan 1999 12:16:13 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA00809; Sat, 9 Jan 1999 12:12:30 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901092012.MAA00809@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Gianmarco Giovannelli cc: current@FreeBSD.ORG Subject: Re: make world fails In-reply-to: Your message of "Sat, 09 Jan 1999 14:59:48 +0100." <369760D4.59D70D2C@giovannelli.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 09 Jan 1999 12:12:30 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > After cvsupping this morning (CET) make world fails on : ... > kzip loader > kzip: not found > *** Error code 1 Whoops, I forgot /usr/bin isn't a build tool, and s comes before u. I've patched it to use /usr/bin/kzip for now; we need a better solution in the longer term. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 14:17:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA22233 for freebsd-current-outgoing; Sat, 9 Jan 1999 14:17:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA22220 for ; Sat, 9 Jan 1999 14:17:03 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac4.wam.umd.edu ((IDENT root)@rac4.wam.umd.edu [128.8.10.144]) by po4.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id RAA28037 for ; Sat, 9 Jan 1999 17:17:56 -0500 (EST) Received: from rac4.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1]) by rac4.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id RAA26053 for ; Sat, 9 Jan 1999 17:16:25 -0500 (EST) Received: from localhost by rac4.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id RAA26048 for ; Sat, 9 Jan 1999 17:16:24 -0500 (EST) X-Authentication-Warning: rac4.wam.umd.edu: culverk owned process doing -bs Date: Sat, 9 Jan 1999 17:16:24 -0500 (EST) From: Kenneth Wayne Culver To: freebsd-current@FreeBSD.ORG Subject: ppbus stuff Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am using FreeBSD current (the kernel source is a few minutes old) and I am using a Parallel port zip drive. The zip-drive access is working fine, but I can't get the printer working. There is no disk in the drive when I am trying to print. Can someone tell me if this is common behavior? My dmesg output is below. Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #1: Sat Jan 9 16:57:47 EST 1999 culverk@localhost.x-press.net:/usr/src/sys/compile/MYKERNEL Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 199739217 Hz CPU: AMD-K6tm w/ multimedia extensions (199.74-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x562 Stepping=2 Features=0x8001bf real memory = 67108864 (65536K bytes) avail memory = 62828544 (61356K bytes) Preloaded elf kernel "kernel" at 0xf0254000. Probing for devices on PCI bus 0: chip0: rev 0xb2 on pci0.0.0 chip1: rev 0xb4 on pci0.2.0 de0: rev 0x22 int a irq 11 on pci0.3.0 de0: 21140A [10-100Mb/s] pass 2.2 de0: address 00:c0:f0:1f:21:02 vga0: rev 0x00 on pci0.4.0 Probing for PnP devices: CSN 1 Vendor ID: SUP2074 [0x7420b04e] Serial 0x00007916 Comp ID: @@@0000 [0x00000000] CSN 2 Vendor ID: CTL00f0 [0xf0008c0e] Serial 0xffffffff Comp ID: PNPb02f [0x2fb0d041] Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A psm0 at 0x60-0x64 irq 12 on motherboard psm0: model IntelliMouse, device ID 3 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 4120MB (8438850 sectors), 8930 cyls, 15 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): wd1: 2060MB (4219425 sectors), 4465 cyls, 15 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, accel, dma, iordy acd0: drive speed 30765 - 6187KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked npx0 on motherboard npx0: INT 16 interface ppc: parallel port found at 0x378 ppc0 at 0x378 irq 7 on isa ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode nlpt0: on ppbus 0 nlpt0: Interrupt-driven port ppi0: on ppbus 0 lppps0: on ppbus 0 vpo0: on ppbus 0 vpo0: EPP 1.9 mode Waiting 2 seconds for SCSI devices to settle da1 at vpo0 bus 0 target 6 lun 0 da1: Removable Direct Access SCSI-2 device da1: Attempt to query device size failed: NOT READY, Medium not present changing root device to wd1s1a Thanks again for your help. Kenneth Culver Computer Science Major at the University of Maryland, College Park. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 14:42:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24164 for freebsd-current-outgoing; Sat, 9 Jan 1999 14:42:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24156 for ; Sat, 9 Jan 1999 14:42:22 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.1/8.9.1) with ESMTP id RAA78913 for ; Sat, 9 Jan 1999 17:41:51 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <199901092241.RAA78913@whizzo.transsys.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG From: "Louis A. Mamakos" Subject: need a major device number.. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 09 Jan 1999 17:41:51 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I need a cdev major device number for a device driver I've written for a Datum bc635PCI time and frequency processor. It's part of some work that I'm doing to develop an infrastructure to precisely timestamp network traffic on a FreeBSD 3.0 system. The goal is to measure unidirectional network latency to sub-100 microsecond accuracy (hopefully closer to 40 or 50 microseconds) between pairs of systems with these boards and an external GPS receiver. This is part of a larger project that I've been working on at work (UUNET), and will be contributing to the FreeBSD project if they want it. As an aside, one of the diagnostic features of the driver is to measure interrupt service time latency in the FreeBSD kernel. I put this code in the driver as an attempt to characterize the "noise floor" of the overall system, as I'm timestamping inbound network traffic in response to an interrupt from the network adapter. The Datum bc635PCI board can be programmed to generate an interrupt at a preset time. You can then subsequently read the board's idea of the time to a 100ns resolution, needing only 3 PCI bus cycles to grab the time. The time is latched on one register reference, and then two 32 bit registers are read to fetch the latched time. The interrupt service routine in the driver notes the time, and maintains a histogram of service times. The driver does this one or twice a second, dependong how it's configured by the driver. Here's some data from a 300MHz P-II based system that been up almost 24 days: lower latency number upper latency bound samples bound ---------- -------- ---------- 6us <= 9 < 7us 7us <= 1478296 < 8us 8us <= 321601 < 9us 9us <= 58115 < 10us 10us <= 122543 < 11us 11us <= 52189 < 12us 12us <= 19390 < 13us 13us <= 6461 < 14us 14us <= 2266 < 15us 15us <= 1731 < 16us 16us <= 1398 < 17us 17us <= 727 < 18us 18us <= 368 < 19us 19us <= 279 < 20us 20us <= 1405 < 22us 22us <= 320 < 24us 24us <= 274 < 28us 28us <= 106 < 30us 30us <= 89 < 32us 32us <= 92 < 35us 35us <= 229 < 50us 50us <= 189 < 75us 75us <= 98 < 100us 100us <= 86 < 250us 250us <= 41 < 500us 500us <= 21 < 1000us 2000us <= 1 < 5000us louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 14:47:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24669 for freebsd-current-outgoing; Sat, 9 Jan 1999 14:47:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24664 for ; Sat, 9 Jan 1999 14:47:11 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id RAA18126 for ; Sat, 9 Jan 1999 17:46:39 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA10924; Sat, 9 Jan 1999 17:46:39 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id RAA54499 for freebsd-current@freebsd.org; Sat, 9 Jan 1999 17:46:39 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199901092246.RAA54499@bb01f39.unx.sas.com> Subject: make release failure: kld To: freebsd-current@FreeBSD.ORG Date: Sat, 9 Jan 1999 17:46:39 -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 Hi, Something related to kld... Could someone please check this out? If this is already fixed, then please ignore... I'm current as of 4pm EST.. Thanks, John install -c -o root -g wheel -m 644 kld/Makefile /snap/release/usr/share/examples/kld/Makefile install -c -o root -g wheel -m 644 kld/syscall/module/Makefile /snap/release/usr/share/examples/kld/syscall/module/Makefile install: /snap/release/usr/share/examples/kld/syscall/module/Makefile: No such file or directory *** Error code 71 Stop. *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 15:29:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27885 for freebsd-current-outgoing; Sat, 9 Jan 1999 15:29:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA27874; Sat, 9 Jan 1999 15:29:37 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id AAA28439; Sun, 10 Jan 1999 00:35:42 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Sun, 10 Jan 1999 00:35:42 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: freebsd-current@FreeBSD.ORG cc: Mike Smith Subject: sysctl's as an FS Message-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'm not sure if this idea has been already discussed... It occured to me that since we need some dynamic approach to the sysctl mechanism (which presently is static, constructed at compile time), especially when KLDs should be able to insert/delete whole subtrees in it, why not reimplement it in similar way to procfs? Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 17:06:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08827 for freebsd-current-outgoing; Sat, 9 Jan 1999 17:06:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oreo.adsu.bellsouth.com (oreo.adsu.bellsouth.com [205.152.173.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA08820 for ; Sat, 9 Jan 1999 17:06:27 -0800 (PST) (envelope-from ck@oreo.adsu.bellsouth.com) Received: (from ck@localhost) by oreo.adsu.bellsouth.com (8.9.1/8.9.1) id UAA78179; Sat, 9 Jan 1999 20:05:35 -0500 (EST) (envelope-from ck) Date: Sat, 9 Jan 1999 20:05:35 -0500 From: Christian Kuhtz To: "John W. DeBoskey" Cc: freebsd-current@FreeBSD.ORG Subject: Re: make release failure: kld Message-ID: <19990109200535.A78140@oreo.adsu.bellsouth.com> References: <199901092246.RAA54499@bb01f39.unx.sas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199901092246.RAA54499@bb01f39.unx.sas.com>; from John W. DeBoskey on Sat, Jan 09, 1999 at 05:46:39PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 09, 1999 at 05:46:39PM -0500, John W. DeBoskey wrote: > install -c -o root -g wheel -m 644 kld/Makefile /snap/release/usr/share/examples/kld/Makefile > install -c -o root -g wheel -m 644 kld/syscall/module/Makefile /snap/release/usr/share/examples/kld/syscall/module/Makefile > install: /snap/release/usr/share/examples/kld/syscall/module/Makefile: No such file or directory > *** Error code 71 > > Stop. > *** Error code 1 Neither /usr/share/examples/kld/syscall/module/, nor /usr/share/examples/kld/syscall/test/ are created if they don't exist prior to a make world.. Cheers, Chris -- "I can remember when a good politician had to be 75 percent ability and 25 percent actor, but I can well see the day when the reverse could be true." -- Harry Truman [Disclaimer: I speak for myself and my views are my own and not in any way to be construed as the views of BellSouth Corporation. ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 17:11:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA09536 for freebsd-current-outgoing; Sat, 9 Jan 1999 17:11:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from post.mail.demon.net (finch-post-10.mail.demon.net [194.217.242.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA09529 for ; Sat, 9 Jan 1999 17:11:41 -0800 (PST) (envelope-from dom@myrddin.demon.co.uk) Received: from [158.152.54.180] (helo=myrddin.demon.co.uk) by post.mail.demon.net with esmtp (Exim 2.10 #1) id 0zz9PJ-0002h2-00; Sun, 10 Jan 1999 01:11:09 +0000 Received: from localhost (myrddin.demon.co.uk) [127.0.0.1] by myrddin.demon.co.uk with esmtp (Exim 1.92 #1) id 0zz9P8-0000UY-00; Sun, 10 Jan 1999 01:10:58 +0000 To: Joe Abley Cc: Jaye Mathisen , current@FreeBSD.ORG Subject: Re: How's 3.0-current as an NFS client? References: <19990109000156.B17962@clear.co.nz> From: Dom Mitchell In-Reply-To: Joe Abley's message of "Sat, 9 Jan 1999 00:01:56 +1300" X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Date: Sun, 10 Jan 1999 01:10:58 +0000 Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joe Abley writes: > On Thu, Jan 07, 1999 at 08:22:54AM +0000, Dom Mitchell wrote: > > > > Personally, I'd still describe it as a tad flaky. It works for most > > things, but at present, there are at least 3 things I can do with an > > nfs mounted home directory that cause the box to hang. These include > > starting netscape or xcopilot and sending mail with MH (a bit bizzare > > that last one, I'll admit). These are mostly just minor annyoances > > for me at the moment which I can live with, but I'd beware of putting > > a heavy NFS load on it. > > > > This is with a current compiled each Monday morning. > > I run 3.0 about as current as you every day as an NFS client, and I have > seen no issues for months. The NFS server in my case is a SPARC Solaris > 2.5.1 box, and I am running NFSv2/UDP. > > What's your server? Solaris 2.6. NFSv2/UDP. Actually, for all that, this week's -current appears to be running netscape successfully again. I think the last set of changes to the nfs directory may have improved my stability qute a bit... -- When I said "we", officer, I was referring to myself, the four young ladies, and, of course, the goat. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 17:12:43 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA09890 for freebsd-current-outgoing; Sat, 9 Jan 1999 17:12:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (tibet-33.ppp.hooked.net [206.80.9.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA09885 for ; Sat, 9 Jan 1999 17:12:41 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@zippy.dyn.ml.org [127.0.0.1]) by zippy.dyn.ml.org (8.9.1/8.8.8) with ESMTP id RAA04249; Sat, 9 Jan 1999 17:15:15 -0800 (PST) (envelope-from garbanzo@hooked.net) Date: Sat, 9 Jan 1999 17:15:15 -0800 (PST) From: Alex Zepeda X-Sender: garbanzo@zippy.dyn.ml.org To: Bryan Seitz cc: current@FreeBSD.ORG Subject: Re: Celeron kernel Patch In-Reply-To: <4.1.19990109135236.009bfbf0@10.0.0.1> Message-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, 9 Jan 1999, Bryan Seitz wrote: > Either way, you don't have to like it. I wrote it for myself b/c I > was sick of seeing unknown. > The Celeron is different than a PII, so hence it is *not* really a > complete PII. Sure you could make it say Pentium II, but I'd rather > see that its a celeron, which is *WHY* intel gave it it's own ID. And if I'm not mistaken, it's marketed as the Pentium II Celeron processor. If anything giving the code-name might be more correct (Klamath, Mendicino, etc). And the cache (which is the only difference between a PII and a PII Celeron) info could be put under the features. The Xenon OTOH is a bit more different and deserves it's own ID string IMO.. - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD http://www.freebsd.org/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 17:38:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA11531 for freebsd-current-outgoing; Sat, 9 Jan 1999 17:38:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from scotty.masternet.it (scotty.masternet.it [194.184.65.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA11526 for ; Sat, 9 Jan 1999 17:38:24 -0800 (PST) (envelope-from gmarco@scotty.masternet.it) Received: from suzy (modem37.masternet.it [194.184.65.47]) by scotty.masternet.it (8.8.8/8.8.8) with SMTP id CAA06608; Sun, 10 Jan 1999 02:37:23 +0100 (CET) (envelope-from gmarco@scotty.masternet.it) Message-Id: <4.1.19990110024346.0092b930@194.184.65.4> X-Sender: gmarco@scotty.masternet.it X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sun, 10 Jan 1999 02:45:08 +0100 To: Kenneth Wayne Culver , freebsd-current@FreeBSD.ORG From: Gianmarco Giovannelli Subject: Re: Build World 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 At 12.01 09/01/99 -0500, Kenneth Wayne Culver wrote: >I read about the -DNOAOUT option, but the Makefile doesn't tell me where >to specify that. Do I just type: >make -DNOAOUT world > >if not could someone let me know? Thanks. It works in this way, or you can add simply in /etc/make.conf a line like NOAOUT= true (I think ...:-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 18:49:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA17651 for freebsd-current-outgoing; Sat, 9 Jan 1999 18:49:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles156.castles.com [208.214.165.156]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA17645; Sat, 9 Jan 1999 18:49:19 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA02550; Sat, 9 Jan 1999 18:45:27 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901100245.SAA02550@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrzej Bialecki cc: freebsd-current@FreeBSD.ORG, Mike Smith Subject: Re: sysctl's as an FS In-reply-to: Your message of "Sun, 10 Jan 1999 00:35:42 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 09 Jan 1999 18:45:27 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello, > > I'm not sure if this idea has been already discussed... It occured to me > that since we need some dynamic approach to the sysctl mechanism (which > presently is static, constructed at compile time), especially when KLDs > should be able to insert/delete whole subtrees in it, why not reimplement > it in similar way to procfs? Because procfs' design is not adequately dynamic, unfortunately. I looked at this back when the syctlfs discussion came up. I also started on a generic meta-filesystem framework as a learning exercise, but I doubt I will finish it anytime soon. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 19:50:53 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA23334 for freebsd-current-outgoing; Sat, 9 Jan 1999 19:50:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from amber.ghostwheel.com (amber.ghostwheel.com [207.201.56.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA23317 for ; Sat, 9 Jan 1999 19:50:50 -0800 (PST) (envelope-from merlin@ghostwheel.com) Received: from amber.ghostwheel.com (amber.ghostwheel.com [207.201.56.89]) by amber.ghostwheel.com (8.8.8/8.8.5) with SMTP id TAA18932 for ; Sat, 9 Jan 1999 19:50:33 -0800 (PST) Date: Sat, 9 Jan 1999 19:50:33 -0800 (PST) From: Christopher Knight To: freebsd-current@FreeBSD.ORG Subject: Is vinum an elf fatality? In-Reply-To: <199901100245.SAA02550@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, I've been using the Vinum lkm to stripe a set of 18G scsi drives. As of this week's update to an elf kernel and world, Vinum has suddenly died. The error is 'malformed input file (not relor archive)'. Any suggestions appreciated, since I'm pretty much down for the count right now. :( -ck ----------------------------------------------------------------------------- Everything in excess! To enjoy the flavor of life, take big bites. Moderation is for monks. -Lazarus Long ----------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 20:22:50 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA25368 for freebsd-current-outgoing; Sat, 9 Jan 1999 20:22:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from jumping-spider.aracnet.com (jumping-spider.aracnet.com [205.159.88.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA25363 for ; Sat, 9 Jan 1999 20:22:49 -0800 (PST) (envelope-from ctapang@easystreet.com) Received: from apex (216-99-199-226.cust.aracnet.com [216.99.199.226]) by jumping-spider.aracnet.com (8.9.1/8.9.0) with SMTP id UAA28781 for ; Sat, 9 Jan 1999 20:22:17 -0800 Message-ID: <00a201be3c50$ef3ec0b0$0d787880@apex.tapang> From: "Carlos C. Tapang" To: Subject: Re: Two seem-to-be bugs with 3.0-SNAP Date: Sat, 9 Jan 1999 20:23:11 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I experienced the same thing when using /stand/sysinstall to create a user. My system is all-ELF, current as of 01/03/1999. I upgraded from RELENG_3_0_0_RELEASE, not from 2.x.x. Carlos C. Tapang http://www.genericwindows.com > >`pw user add' and `pw user mod' hang at the point of executing >/usr/sbin/pwd_mkdb -C /etc/master.passwd >but then, I'm on kind of a weird network, in case it's trying to >do anything DNS-related. `pw user show' executes without any >delay at all. Executing the above line by itself also seems to >get stuck somewhere. Other means of updating the passwd file >have no problems. I haven't looked into this either. > >Those are the only things I think I've seen so far that I can >remember. Like I say, if you can reproduce these, then I guess >I'm not imagining too many things. > > >thankz, barry bouwsma > > >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 Jan 9 20:50:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA27786 for freebsd-current-outgoing; Sat, 9 Jan 1999 20:50:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles156.castles.com [208.214.165.156]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA27764 for ; Sat, 9 Jan 1999 20:50:19 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id UAA03176; Sat, 9 Jan 1999 20:46:23 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901100446.UAA03176@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Luoqi Chen cc: dillon@apollo.backplane.com, jake@checker.org, current@FreeBSD.ORG Subject: Re: boot single with new loader? In-reply-to: Your message of "Sat, 09 Jan 1999 00:29:23 EST." <199901090529.AAA26469@lor.watermarkgroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 09 Jan 1999 20:46:23 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have a modified version of tunefs which allows you to enable/disable > softupdates on root partition in single user mode. You don't even need > to reboot after you've run tunefs, you can simple exit the single user > shell, boot into multiuser mode and you root partition is softupdate > mounted. The patch is available at http://www.freebsd.org/~luoqi/ . Any reason you don't want to commit this? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 21:07:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA00266 for freebsd-current-outgoing; Sat, 9 Jan 1999 21:07:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA29840; Sat, 9 Jan 1999 21:05:52 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (root@keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id FAA27303; Sun, 10 Jan 1999 05:04:34 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.1/8.9.1) with ESMTP id FAA38121; Sun, 10 Jan 1999 05:05:45 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199901100505.FAA38121@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Somers cc: oZZ!!! , current@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: zlib-1.1.3 ??? In-reply-to: Your message of "Thu, 10 Dec 1998 09:21:54 GMT." <199812100921.JAA42419@keep.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 10 Jan 1999 05:05:38 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Hello! > > What about of new version of zlib??? > > why it not in -current source-tree ??? > > (now in my -current zlib-1.1.1) > > Peter (cc'd) said he'd do the update after 3.0-RELEASE :-) > > > Rgdz, Well, that was a month ago now.... I guess I'll do it :-] > -- > Brian > > Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 21:12:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA00730 for freebsd-current-outgoing; Sat, 9 Jan 1999 21:12:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA00719 for ; Sat, 9 Jan 1999 21:12:25 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac4.wam.umd.edu ((IDENT root)@rac4.wam.umd.edu [128.8.10.144]) by po4.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id AAA08808 for ; Sun, 10 Jan 1999 00:13:24 -0500 (EST) Received: from rac4.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1]) by rac4.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id AAA13310 for ; Sun, 10 Jan 1999 00:11:52 -0500 (EST) Received: from localhost by rac4.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id AAA13305 for ; Sun, 10 Jan 1999 00:11:51 -0500 (EST) X-Authentication-Warning: rac4.wam.umd.edu: culverk owned process doing -bs Date: Sun, 10 Jan 1999 00:11:51 -0500 (EST) From: Kenneth Wayne Culver To: freebsd-current@FreeBSD.ORG Subject: ide_pci Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I know someone has worked on the ide_pci.c file, but it still doesn't work on my system. I'm not sure what controller I have because it came on the Motherboard, and the documentation doesn't say. I think it is something from Acerlabs though. It detects the controller, but says there is no dma on the secondary channel (simplex), and then when it gets to the point where it finds the drives down in the ISA probing, it doesn't find the secondary IDE controller. I have an ATAPI CD-ROM drive there. I would appreciate some help, and I would be glad to test patches to this file. (ide_pci.c, or any that need changed.) Kenneth Culver Computer Science Major at the University of Maryland, College Park. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 21:13:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA01035 for freebsd-current-outgoing; Sat, 9 Jan 1999 21:13:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from assaris2.pdc.kth.se (assaris2.pdc.kth.se [130.237.221.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA01029 for ; Sat, 9 Jan 1999 21:13:08 -0800 (PST) (envelope-from assar@sics.se) Received: (from assar@localhost) by assaris2.pdc.kth.se (8.9.1/8.7.3) id GAA00355; Sun, 10 Jan 1999 06:14:09 +0100 (CET) To: current@FreeBSD.ORG Subject: kern/9413: patches for enabling profiling on ELF kernels Mime-Version: 1.0 (generated by tm-edit 7.68) Content-Type: text/plain; charset=US-ASCII From: Assar Westerlund Date: 10 Jan 1999 06:14:07 +0100 Message-ID: <5lu2xz7lr4.fsf@assaris2.pdc.kth.se> Lines: 4 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had to do the modifications in kern/9413 to get profiling of ELF kernels to work. Comments/questions/commits? /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 21:20:52 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA01594 for freebsd-current-outgoing; Sat, 9 Jan 1999 21:20:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles156.castles.com [208.214.165.156]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA01589 for ; Sat, 9 Jan 1999 21:20:50 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id VAA03360; Sat, 9 Jan 1999 21:17:22 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901100517.VAA03360@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel C. Sobral" cc: current@FreeBSD.ORG Subject: Re: beep, beep, beep! In-reply-to: Your message of "Sat, 09 Jan 1999 14:03:33 +0900." <3696E325.5590B6C6@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 09 Jan 1999 21:17:21 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > probably translates \a correctly (I haven't looked), so it would have > > to be: > > > > echo "\a\a\a" > > Well, THAT wouldn't help (see kern/9397). The only thing quotes > preserve is the space, and it wouldn't have helped anyway, since the > backslashes are removed before any other processing is done. Hmm. I'm presuming you tested that patch. It's generally considered good manners not to include reverse diffs in your PRs though. 8) Fixed and closed, and thanks. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 21:30:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA02251 for freebsd-current-outgoing; Sat, 9 Jan 1999 21:30:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from houcbs2.houabg.com (houabg.com [206.109.247.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA02246 for ; Sat, 9 Jan 1999 21:30:11 -0800 (PST) (envelope-from dchapman@houabg.com) Received: from sdn-ar-002txhousP083.dialsprint.net by houcbs2.houabg.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1457.7) id CSR50DLZ; Sat, 9 Jan 1999 23:37:36 -0600 Message-ID: <36983B98.345FCB57@houabg.com> Date: Sat, 09 Jan 1999 23:33:12 -0600 From: "David W. Chapman Jr." X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current Subject: KDE Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone been able to compile the latest source of kde from ftp.kde.org, I believe its version 1.1-something. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 21:43:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA03548 for freebsd-current-outgoing; Sat, 9 Jan 1999 21:43:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA03543 for ; Sat, 9 Jan 1999 21:43:45 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id QAA06093; Sun, 10 Jan 1999 16:13:11 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id QAA15059; Sun, 10 Jan 1999 16:13:10 +1030 (CST) Date: Sun, 10 Jan 1999 16:13:09 +1030 From: Greg Lehey To: Christopher Knight Cc: freebsd-current@FreeBSD.ORG Subject: Re: Is vinum an elf fatality? Message-ID: <19990110161309.I8886@freebie.lemis.com> References: <199901100245.SAA02550@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: ; from Christopher Knight on Sat, Jan 09, 1999 at 07:50:33PM -0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, 9 January 1999 at 19:50:33 -0800, Christopher Knight wrote: > 148 09-01-1999 Mike Smith To Andrzej Bial ( 24) Re: sysctl's as an FS > 149 09-01-1999 Christopher Knight To FreeBSD curr ( 21) --> Is vinum an elf fatality? This indicates that you have replied to Mike Smith's message about sysctl. This confuses a lot of people running threaded mailers. > I've been using the Vinum lkm to stripe a set of 18G scsi drives. As of > this week's update to an elf kernel and world, Vinum has suddenly died. > > The error is 'malformed input file (not relor archive)'. > > Any suggestions appreciated, since I'm pretty much down for the count > right now. :( I assume you're trying to load the LKM; that doesn't work any more AFAIK. Use the kld module instead: # kldload vinum If you have any trouble with that, please give more details. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 22:48:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA08726 for freebsd-current-outgoing; Sat, 9 Jan 1999 22:48:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA08717 for ; Sat, 9 Jan 1999 22:48:33 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id WAA49864 for ; Sat, 9 Jan 1999 22:47:51 -0800 (PST) To: current@FreeBSD.ORG Subject: State of the union, 1999. Date: Sat, 09 Jan 1999 22:47:50 -0800 Message-ID: <49859.915950870@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, it's another year behind us, folks, and probably high time for another state of the union report! Ahem... I'm never quite sure how to word these things since I'm always reminded of a U.S. president sitting in front of fireplace, trying to sound down-home and folksy for the corn growing states, or perhaps England's Queen on Christmas day, giving her usual somber-yet-hopeful address on how things went for Britannia during the previous year and what everyone should perhaps think about for the next. Neither one of those is really me, basically, so perhaps I'll just cut to the chase and focus on the most pertinent lessons (and objectives) to come out of the year 1998 for me. 1998 was, of course, the year that the Internet got bigger (no surprise), various "internetpraneurs" (gag) got richer and FreeBSD's user base, as measured by the ftp download stats grew at its usual 200-300% rate. More companies also entered the FreeBSD arena, either offering add-ons for or solutions incorporating FreeBSD, and our PR machine, as flimsy and low-key as it often is, managed to ratchet things up another notch. All in all, it was a very good year for FreeBSD and I don't think that even the most paranoid of us could claim otherwise - Microsoft took one in the shorts, we got bigger and just a bit better known, life was good. Well, mostly. Whipping off my rosy glasses for a second, I can also say that there were still a number of rocks in the road and unexpected bends that left us not always in the best of control there. While downloads have gone up, CD sales aren't quite following suit since the whole CD market in general is suffering from increased Internet availability and its erosion of some of the CD's fundamental advantages. We still did quite well, considering the market's gradual implosion, but it would be foolish to continue to rely on a single CD product to provide the kinds of subsidies that have been steadily oiling the project's gears (we more than doubled the size of the freebsd.org computing cluster, for example, and significantly enlarged our developer equipment grant program in 1998, all things which cost $$$). It's fairly obvious that Walnut Creek CDROM will need to increase the number of products it offers if it wishes to remain an effective player in the FreeBSD game and we must continue, as a project, to be flexible in exploring all types of relationships with those who may now have a vested interest in FreeBSD's success. Things are well past the point where we can do everything that needs to be done as a serious and "grown up" solution just on good will and volunteerism alone. With that in mind, sites like the FreeBSD Mall (www.freebsdmall.com) have been set up to try and market a wider variety of FreeBSD-related products and we've also begun exploring relationships with various companies who can derive measurable value from any PR campaign that enhances FreeBSD's reputation (translation: we want them to help pay for it :). As many people have somewhat bitterly pointed out by now, this business has become a 10% technology and 90% perception equation as far as the direction in which people stampede is concerned, and hate them for the mindless little sheep that they are, you still need to understand people's tendencies and behavioral patterns when it comes to dealing with anything they don't really understand. We've done a great job on the technology, we really have (and should be proud of that), but all too frequently we just throw up our hands over the perception issue and tell people to think whatever the hell they want to. Bad techies! Myopic techies! :-) What can we do to change this in 1999? Well, I've also heard our advocate corps calling for logistical support ("Backup! We need some *backup* here!!") and I've listened to them, part of my project for the new years being to get more digital daemon imagery made available (which I have already commissioned), more glossies with various handy comparison charts on them ("FreeBSD and NT", "FreeBSD and Solaris", "FreeBSD and Linux", etc) and more newsletters for passing out to people. We can also produce more marketing periphenalia like buttons, stickers, new T-shirts, etc. to give people a wider array of stuff to proudly point to in support of the "emerging FreeBSD phenomenon." If we can manage to raise more money for PR, we can also perhaps buy some of these items in bulk to use as give-aways in various promotional deals. Other than that, I'm always open to suggestions. We need to do more effective PR, that much is inarguable, it's only a question of picking our targets for maximum effect given a limited operating budget. The core team: 1998 also ended with a bit of a bang as far as FreeBSD's project management was concerned, frustration with a mostly recumbent core team goading a couple of bearded Danish Vikings into staging a midnight raid on -current, ruthlessly culling the weak and the lame from the source tree. Unfortunately, some of those weak or lame bits of code were still in use at the time and, with no prior public warning having been given, it did not exactly leave the various followers of -current with the feeling that the event was going to be the highlight of their Christmas season. Their complaints led, in turn, to something of a constitutional crisis within core, the rival factions each accusing one another of either impeding progress or using cowboy tactics to achieve that progress, and each faction had its legitimate points just as it had its wholly unreasonable ones. Coming out of this, various suggestions were bandied about concerning how we might put together a "better core team" to which such things simply did not happen (or, if they did, would not be our fault since we'd all be long gone :-) and many of these suggested cures were eventually deemed, quite rightly, to be worse than the disease. So what did we learn from the exercise then? First off, I think everyone is now pretty much in agreement that these sorts of drive-by shootings are just not an option for the future, no matter what the justification. Anyone who contemplates a major addition or removal of functionality from the source tree MUST communicate those intentions well in advance and give the readership of -current, -stable or -announce (the former two depending on the branch the changes affect and the latter on the extent of the changes) ample time to respond. If there is a conclusively negative response to a proposed change, it just doesn't happen until and unless the proposal somehow manages to win people over through sheer dint of persuasive argument in its favor. If it's more a mixed bag of reactions, or there is little reaction at all, the developer is free to proceed at his or her discretion but still never without advance notice. Second, in reaction to the various proposals put forward to either gut core or have core elected by popular vote, let me just say that we're not going to do that. There are probably several people currently in core who would gladly step aside and retire if they felt that adequate replacements had been found and the project was in good hands, but none of us like the scenario where anyone is overtly forced out of core. It's just not a reasonable way of going about it when so many less painful alternatives exist, and I, for one, would far rather simply grow core and let the inactive members fall off when they themselves have come to a decision that they have nothing left to contribute at a "core level", resignation from core having not stopped several folks from remaining as effective committers or making other valuable contributions. We're a free software project and nobody's paid to be in core, no matter how seriously we may be tempted to take the whole core thing sometimes, and we need to remember that all of this started as a bunch of folks who simply wanted to work together in creating something useful and interesting. The day we lose that kind of informal atmosphere of productivity over politics is the day that something pretty fundamental goes out at the center of core and also the day that I'll retire from it myself, handing my hat to a replacement and wishing everyone the very best of luck. I can also only sound a similar cautionary note about the idea of electing core from the user base, or with committers serving as a kind of "electoral college", as nice and democratic an idea as that might sound. The FreeBSD core team does not represent a democratically selected body and was, in fact, very carefully put together in a very non-democratic way. We picked core with the specific intention that it represent as diverse a set of hard-core FreeBSD evangelist/developers as we knew how to find and we've continued to add people using the same criteria. In bringing someone into core, we don't look at whether they've been winning popularity contests lately or won the Programming Olympiad 3 times in a row, we ask ourselves: "Does this person bring a unique talent or viewpoint to the group? Will the resulting whole be greater than the sum of its parts?" These are our two most overriding concerns and, in fact, are the only grounds on which we've ever felt it necessary to actually ask for someone's resignation from core. We can tolerate quite a bit from people but not when it impacts core's fundamental ability to work together or seeks to undermine the very diversity of opinion we've worked so hard to cultivate. It's good to be an effective group of decision makers as a core team, and we do have our moments (both ways), but sometimes it's even better to know simply when to stay out of the way and just make sure the train stays roughly on the tracks. We've prevented a lot more stupidity through having such a diverse and carefully selected core team than I think we've ever caused and I do not trust the democratic process to leave us with the same thing after a few elections. Core is also continuing to work on drafting some internal documents which cover, in much better detail, just what our rules as committers are, those superseding any "core member privileges", governing how large-scale code removal and addition operations should be carried out. We'll post something to committers just as soon as we finally flesh it out to our mutual satisfaction but, in a nutshell, it basically just insists that people need to be warned before such changes happen and that the owner of a given body of code should be given first say as to whether or not it's time to kill it in the name of obsolescence or redundancy. Finally, we are looking at the general issue of communication inside and outside core and the question of whether or not to bring in some new member(s) at this time. That discussion is ongoing and I'll do my best to keep everyone up to date on that as things progress. Release numbering: Other decisions on the horizon concern returning to our former practice of using "major" version numbers for branches and "minor" numbers for releases, the revision number field only being used to denote point-releases which were done for some reason significant enough to merit such a special release. This means that the next release will be 3.1, not 3.0.1, and the new branch will be 4.0-current instead of 3.1-current. Is this just a marketing ploy? No, it's not, though marketing has indeed been a frequent casualty of our current numbering scheme. We have frequently made fairly large changes between our "point releases", jumps like 2.2.5->2.2.6 and 2.2.6->2.2.7 being a lot bigger than most folks gave them credit for given that it was just one little revision number being changed. This one simple facet of human nature reduced the effectiveness of these releases and under-sold the work being done by our developers to substantially improve *every* release we do, regardless of which branch it's on. This is not a trend which seems to be reversing itself and so I feel quite safe in saying that 3.1 will be a "full release" over 3.0 in its own right and not merely the "3.0.1" which conveys such a different impression. It's also very important to note that since our branches seem to typically last from 12-18 months these days, no matter what we try in attempting to kill a branch earlier, a major version bump (4.0) is entirely merited for something which won't see full release status until sometime in the year 2000. This will make the marketing people happy since they won't have such an uphill battle on number perception and it will make the users happy since they'll get a clearer picture of what changed in, say, 3.1 to 3.2 vs 3.1 to 3.1.1 (which might be an important security update). It will also make this particular developer happy since I'll have the revision number space back again for doing point releases. It's a win and so we're going to do it. 3.0.1 is dead, long live 3.1! :) Technology: This last year also saw a successful transition to ELF from a.out format and a new kernel loadable module scheme which allows modules to be read in without a runtime dependency on /usr/bin/ld. We also got a new boot loader (with a forth interpreter!) to aggregate a "kernel" at boot time. These are both powerful new mechanisms and, coupled with some new stuff which will be coming in 1999, should give us a far more dynamic and extensible system than we've ever had before. Not to be overlooked is also our new SCSI CAM system, giving us more robust behavior with large drive arrays and supporting more of the high-end SCSI controllers, or the support for multiple processors on the x86. We made considerable progress all across the board with the release of 3.0, finally reaching a point with the DEC Alpha architecture port where people starting worrying more about the packages collection than they did about working kernels or a /usr/src which built. That represents considerable progress towards "genuine usefulness" and I hope that 1999 will see a fully desktop capable release of FreeBSD/axp (to say nothing of a server capable one), various difficulties with X server technology making the Alpha desktop a unique milestone in its own right, especially if it's on an ARC or AlphaBIOS machine. 1999 may also see the early release of a SPARC port, though it's still far too early to say anything more definite than that. Join the sparc@freebsd.org mailing list if you want to follow these efforts. IPv6 and IPSec were also hotly debated topics in 1998, FreeBSD's refusal to back any specific implementation being cited by many as an example of core's over-conservatism in action. Happily for everyone, our wait-and-see attitude proved to be the right one when the two major "competing" groups, KAME and INRIA, finally agreed to merge their implementations. We have, in turn, committed to adopting this merged implementation and have several people from the KAME/INRIA groups on the FreeBSD development team who will be importing and maintaining this code as it becomes available. There is also substantial work underway with the VM system and the filesystem code, much of which is either being tested quietly in small groups (Dillon/Dyson/Greenman) or is awaiting the 4.0 branch event, still scheduled for January 15th, 1999. In other areas, we have Kazu's very welcome total redesign of the console driver coming into -current along with USB support, courtesy of Nick Hibma and others. This is just to name a few of the projects underway and I don't mean to slight anyone by not mentioning theirs directly, these are just 3 ongoing projects right off the top of my head. We seem to be gaining a lot of technical momentum, and that's great, just so long as we can also keep our heads during the times where not everyone is in total agreement about which technical direction to take. Tech support: A point which should also be obvious to everyone yet still somehow requires frequent reinforcement is the fact that we need to maintain participation in this project as something which is also *enjoyable* for the developer/participants or they will just as quickly go away again and stop giving each and every one of us the benefit of their volunteer labor (on which a dollar value could not even be put). This is something which each and every one of our users needs to be aware of, at least somewhere in the back of their minds, for those times when they're tempted to start thinking of FreeBSD as just another shrink-wrap solution from Software, Inc. and start treating project members like personal employees. Those looking for actual FreeBSD employees should send mail to jobs@freebsd.org and indicate how much money they're willing to pay, otherwise don't do it. I don't mean to come across so harshly here that people don't even bother asking us for help, I'm simply saying that those users who avail themselves of the various FreeBSD volunteer tech support mechanisms out there (mail, news, irc, etc) should always understand that asking another perfect stranger for help is just not much different from asking a random person on the street for a dollar. If you want to get free handouts, you'd better at the very least learn to ask politely and when to take "no" for an answer! :-) I've seen a lot of abuse of the various tech support forum volunteers this last year and it frankly sucks. People just need to be more considerate and stop regarding free tech support as a god-given right rather than a very special privilege. If you want on-demand tech support, to to www.freebsdmall.com and order yourself a tech support contract. You get what you pay for! :) Looking forward: What do I see ahead for 1999? Well, assuming that we don't all vanish in some pre-millennial holocaust, I see more interesting new features, improved marketing, more commercial interest, more magazine articles and press attention, basically more of the same if we can just try to stay reasonably well focused on what we need to do and not get distracted into chasing weird desktop dreams or suddenly become overly minimalist or kitchen-sink biased in /usr/src, continuing to chart the middle course we're more famous for. The FreeBSD core team, one year older and hopefully a little wiser, needs to continue keeping a light but steady hand on the tiller, relying on our developers as usual to provide much of the actual motive force behind FreeBSD. Our users also need to become more involved and I'm hoping that 1999 will be the year when a lot more local user groups and other self-help type of organizations are formed. The Handbook and FAQ are documents which are getting better, hopefully another trend we'll see continue into 1999 as Nik Clayton, our fearless new Documentation Project leader, continues at the helm. We still have to remember, however, that for many users the handbook and FAQ docs are just not enough. Linux has succeeded largely because of a large grass-roots support and evangelism network which allows it to reach such people and communicate the message to them. If FreeBSD's own users want to see FreeBSD doing better against whomever they most perceive as its competition, and 1998 was certainly a year where I heard a lot of complaining about this, then they're going to simply have to get off their collective duffs and put in more of this kind of work. When was the last time a bunch of FreeBSD users got together to hand out FreeBSD literature at a Microsoft product launch, for example, or held an install-a-thon at a local computer show? The Linux folks do things like that all the time, apparently, whereas only a very few die-hard FreeBSD users currently do it now, so why not help these people out? Join the advocacy@freebsd.org mailing list and discuss your plans there so that others with more enthusiasm than ideas can also learn from and perhaps help you with yours. Write short articles for the new advocacy sites like www.daemonnews.org or www.freebsdrocks.com and help promote the success of BSD evangelical publications. Phrases like "this is your FreeBSD" and "it all depends on you" may seem shop-worn and trite, but they're also unfortunately still true when there's so few of us and so many of you. If FreeBSD is to *really* continue to succeed in 1999, it will only be with substantial user participation and that means you, users! Start a local user group, donate some of your older CD releases to the local library, try and convince a local small business or ISP to use FreeBSD, these are just a few of the many things that can be done if you're truly interested in putting some energy into FreeBSD and ideas for what to do will be the least of your worries if you're truly motivated. Executive Summary: 1999, rah rah rah, let's do it! :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 23:47:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14165 for freebsd-current-outgoing; Sat, 9 Jan 1999 23:47:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from st-lcremean.tidalwave.net (host-e186.tidalwave.net [208.213.203.186] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA14160 for ; Sat, 9 Jan 1999 23:47:24 -0800 (PST) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.9.1/8.8.8) id CAA50309; Sun, 10 Jan 1999 02:46:47 -0500 (EST) (envelope-from lee) Message-ID: <19990110024647.A50225@tidalwave.net> Date: Sun, 10 Jan 1999 02:46:47 -0500 From: Lee Cremeans To: Kenneth Wayne Culver , freebsd-current@FreeBSD.ORG Subject: Re: ide_pci Reply-To: lcremean@tidalwave.net References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Kenneth Wayne Culver on Sun, Jan 10, 1999 at 12:11:51AM -0500 X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 10, 1999 at 12:11:51AM -0500, Kenneth Wayne Culver wrote: > I know someone has worked on the ide_pci.c file, but it still doesn't work > on my system. I'm not sure what controller I have because it came on the > Motherboard, and the documentation doesn't say. I think it is something > from Acerlabs though. It detects the controller, but says there is no dma > on the secondary channel (simplex), and then when it gets to the point > where it finds the drives down in the ISA probing, it doesn't find the > secondary IDE controller. I have an ATAPI CD-ROM drive there. I would > appreciate some help, and I would be glad to test patches to this file. > (ide_pci.c, or any that need changed.) > I was one of the people working on stuff for this board; I got around the BMISTA_SIMPLEX bug by disabling the check for it, first with options DISABLE_PCI_IDE in my config file, then removing the check for it completely. As an added bonus, I was able to get Ultra DMA at least partially working -- reads work beautifully, pulling down 13+ MB/s from my Seagate Medalist Pro 9140, but writes were kinda recalcitrant, and I think that may have been because I overclocked the PCI bus on my board -- I need to test it at 33 MHz. I can't work on this seriously anymore because I've since returned the board to its rightful owner (who was letting me borrow it indefinitely), and now have a VIA-based Super7 board (Soyo SY-5EHM). I'll put the patches for the Acer chipset on my webpage. I NEED TESTERS FOR THE UDMA. They'll be available at http://st-lcremean.tidalwave.net/~lee/acer-udma.tar.gz -- +--------------------------------------------------------------------+ | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)| | lcremean@tidalwave.net| http://st-lcremean.tidalwave.net/~lee | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 23:53:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14842 for freebsd-current-outgoing; Sat, 9 Jan 1999 23:53:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www0d.netaddress.usa.net (www0d.netaddress.usa.net [204.68.24.33]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA14826 for ; Sat, 9 Jan 1999 23:53:07 -0800 (PST) (envelope-from slpalmer@netscape.net) Received: (qmail 12172 invoked by uid 60001); 10 Jan 1999 07:52:23 -0000 Message-ID: <19990110075223.12171.qmail@www0d.netaddress.usa.net> Received: from 204.68.24.33 by www0d via web-mailer(R2.6) on Sun Jan 10 07:52:23 GMT 1999 Date: 10 Jan 99 07:52:23 America/Fort_Wayne From: Stephen Palmer To: freebsd-current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG, son@teaser.fr, "José" "Mª" Alcaide Subject: Re: Request fo help with Zip Drive on vpo0 in -current CC: Stephen Palmer , gp@oitunix.oit.umass.edu, freebsd-current@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id XAA14829 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry if this is redundant, but I haven't seen any new posts on this since 1/1/99. I am still showing this problem (vpo0 detected, da0 and scbus not detected) with sources current as of 1/9/99 5PM CST. Any help would be appreciated. (I'm almost to the point of bowing down to whomever can solve this! I wish I could code as well as report :-( ) Stephen L. Palmer slpalmer@netscape.net son@teaser.fr wrote: > On Mon, Dec 28, 1998 at 11:48:15AM +0100, José Mª Alcaide wrote: > > > >Nicolas Souchu wrote: > >> > >> Sorry, I'm wrong, it's ok here with December, 22th. So I can't really > >> help you from there :( > >> > >> You may retry previous sys/ releases Dec, 1st, Nov, 15th to find out the bogus > >> submit. > >> > > > >Parallel ZIP doesn't work here, using sources CVSupped today (Dec 28th). > >Perhaps the cause isn't in the ppc/ppbus/vpo code; the problem > >I see is that da0 isn't initialized, so I think that scbus0 doesn't > >get attached to vpo0 for some reason. Some parts of the CAM code > >have changed in the last month... > > > >These are my kernel config lines related to the parallel bus: > > > >controller scbus0 # Lo necesita el ZIP paralelo. > >device da0 # Y esto también. > >controller ppbus0 # Bus paralelo > >controller vpo0 at ppbus? # ZIP paralelo > >device nlpt0 at ppbus? # Impresora > >controller ppc0 at isa? port ? tty irq 7 flags 0x04 > > > >I think that this config is OK. I have no SCSI adapter in this > >machine. These are the boot messages (boot -v): > > > >ppc: parallel port found at 0x378 > >ppc0: > >ppc0 at 0x378 irq 7 flags 0x4 on isa > >ppc0: Generic chipset (EPP-only) in EPP mode (EPP 1.9) > >nlpt0: on ppbus 0 > >nlpt0: Interrupt-driven port > >vpo0: on ppbus 0 > >vpo0: EPP 1.9 mode > > > >After that, there is no mention to any "da" device. > >This is very odd, indeed. > > Ooops, I've added some detection code October, 31th. It may break your > hardware. Detection of your ZIP is done in NIBBLE mode, then according to your > boot flags, EPP mode is required for transfer. > > First, try to set your bootflags to 0x3 to force PS2/NIBBLE mode and see > if it works. Then try 0x1. > > Secondly, set 0x44 to your bootflags to force your chipset generic and > avoid NS chips detection code execution. > > I completly forgot all this... please, give me some feedback. > > -- > nsouch@teaser.fr / nsouch@freebsd.org > FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org --- | Stephen L. Palmer | Sprint Paranet slpalmer@netscape.net \|/ slpalmer@sprintparanet.com "There are thousands of intelligent species in the Universe, and they all own cats." -Unknown ____________________________________________________________________ More than just email--Get your FREE Netscape WebMail account today at http://home.netscape.com/netcenter/mail To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 9 23:53:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14841 for freebsd-current-outgoing; Sat, 9 Jan 1999 23:53:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www0d.netaddress.usa.net (www0d.netaddress.usa.net [204.68.24.33]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA14828 for ; Sat, 9 Jan 1999 23:53:07 -0800 (PST) (envelope-from slpalmer@netscape.net) Received: (qmail 12172 invoked by uid 60001); 10 Jan 1999 07:52:23 -0000 Message-ID: <19990110075223.12171.qmail@www0d.netaddress.usa.net> Received: from 204.68.24.33 by www0d via web-mailer(R2.6) on Sun Jan 10 07:52:23 GMT 1999 Date: 10 Jan 99 07:52:23 America/Fort_Wayne From: Stephen Palmer To: freebsd-current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG, son@teaser.fr, "José" "Mª" Alcaide Subject: Re: Request fo help with Zip Drive on vpo0 in -current CC: Stephen Palmer , gp@oitunix.oit.umass.edu, freebsd-current@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id XAA14830 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry if this is redundant, but I haven't seen any new posts on this since 1/1/99. I am still showing this problem (vpo0 detected, da0 and scbus not detected) with sources current as of 1/9/99 5PM CST. Any help would be appreciated. (I'm almost to the point of bowing down to whomever can solve this! I wish I could code as well as report :-( ) Stephen L. Palmer slpalmer@netscape.net son@teaser.fr wrote: > On Mon, Dec 28, 1998 at 11:48:15AM +0100, José Mª Alcaide wrote: > > > >Nicolas Souchu wrote: > >> > >> Sorry, I'm wrong, it's ok here with December, 22th. So I can't really > >> help you from there :( > >> > >> You may retry previous sys/ releases Dec, 1st, Nov, 15th to find out the bogus > >> submit. > >> > > > >Parallel ZIP doesn't work here, using sources CVSupped today (Dec 28th). > >Perhaps the cause isn't in the ppc/ppbus/vpo code; the problem > >I see is that da0 isn't initialized, so I think that scbus0 doesn't > >get attached to vpo0 for some reason. Some parts of the CAM code > >have changed in the last month... > > > >These are my kernel config lines related to the parallel bus: > > > >controller scbus0 # Lo necesita el ZIP paralelo. > >device da0 # Y esto también. > >controller ppbus0 # Bus paralelo > >controller vpo0 at ppbus? # ZIP paralelo > >device nlpt0 at ppbus? # Impresora > >controller ppc0 at isa? port ? tty irq 7 flags 0x04 > > > >I think that this config is OK. I have no SCSI adapter in this > >machine. These are the boot messages (boot -v): > > > >ppc: parallel port found at 0x378 > >ppc0: > >ppc0 at 0x378 irq 7 flags 0x4 on isa > >ppc0: Generic chipset (EPP-only) in EPP mode (EPP 1.9) > >nlpt0: on ppbus 0 > >nlpt0: Interrupt-driven port > >vpo0: on ppbus 0 > >vpo0: EPP 1.9 mode > > > >After that, there is no mention to any "da" device. > >This is very odd, indeed. > > Ooops, I've added some detection code October, 31th. It may break your > hardware. Detection of your ZIP is done in NIBBLE mode, then according to your > boot flags, EPP mode is required for transfer. > > First, try to set your bootflags to 0x3 to force PS2/NIBBLE mode and see > if it works. Then try 0x1. > > Secondly, set 0x44 to your bootflags to force your chipset generic and > avoid NS chips detection code execution. > > I completly forgot all this... please, give me some feedback. > > -- > nsouch@teaser.fr / nsouch@freebsd.org > FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org --- | Stephen L. Palmer | Sprint Paranet slpalmer@netscape.net \|/ slpalmer@sprintparanet.com "There are thousands of intelligent species in the Universe, and they all own cats." -Unknown ____________________________________________________________________ More than just email--Get your FREE Netscape WebMail account today at http://home.netscape.com/netcenter/mail To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message