From owner-freebsd-current Sun Apr 12 05:01:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA29020 for freebsd-current-outgoing; Sun, 12 Apr 1998 05:01:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailer.tydfam.machida.tokyo.jp (ns.tydfam.machida.tokyo.jp [210.161.209.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA29015 for ; Sun, 12 Apr 1998 05:01:34 -0700 (PDT) (envelope-from ken@tydfam.machida.tokyo.jp) Received: from localhost (ns1.tydfam.machida.tokyo.jp [210.161.209.138]) by mailer.tydfam.machida.tokyo.jp (8.8.8/3.6W) with ESMTP id UAA19120 for ; Sun, 12 Apr 1998 20:35:19 +0900 (JST) To: freebsd-current@FreeBSD.ORG Subject: Q) XFree86-3.3.2 compile w/ -current X-Mailer: Mew version 1.93b1 on XEmacs 20.3 (Vatican City) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19980412203519D.ken@ns1.tydfam.machida.tokyo.jp> Date: Sun, 12 Apr 1998 20:35:19 +0900 From: Takeshi Yamada X-Dispatcher: imput version 971024 Lines: 158 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I have the following error, and I canot compile XFree86-3.3.2 with my FreeBSD-current using ports/x11/XFree86. (980411 cvsup'd) Is it my binary mis-installation, or any patch needed, or something goes wrong with myself or -current? Thank you for supports in advance. ============= make log goes ========================= >> Checksum OK for xc/X332src-1.tgz. >> Checksum OK for xc/X332src-2.tgz. ===> Extracting for XFree86-3.3.2 ===> Patching for XFree86-3.3.2 ===> Applying FreeBSD patches for XFree86-3.3.2 ===> Configuring for XFree86-3.3.2 : : : Do you want to build the VGA16 server? [YES] : : : ("YES" to all) : : : End of configuration questions. No more user input required ===> Applying KerberosIV patches ===> Building for XFree86-3.3.2 Building Release 6.3 of the X Window System. : : : : : : Building on FreeBSD 3.0-CURRENT i386 (3.0.0). make -f xmakefile Makefiles making Makefiles in include... making Makefiles in include/bitmaps... make: don't know how to make Makefiles. Stop making Makefiles in include/extensions... making Makefiles in include/fonts... make: don't know how to make Makefiles. Stop making Makefiles in config... making Makefiles in config/cf... making Makefiles in config/imake... making Makefiles in config/makedepend... make: don't know how to make Makefiles. Stop making Makefiles in config/util... make: don't know how to make Makefiles. Stop making Makefiles in lib... making Makefiles in lib/xtrans... making Makefiles in lib/Xau... "Makefile", line 777: Need an operator make: fatal errors encountered -- cannot continue making Makefiles in lib/Xdmcp... making Makefiles in lib/X11... "Makefile", line 1222: Need an operator make: fatal errors encountered -- cannot continue making Makefiles in lib/oldX... making Makefiles in lib/ICE... make: don't know how to make Makefiles. Stop making Makefiles in lib/SM... making Makefiles in lib/Xext... make: don't know how to make Makefiles. Stop making Makefiles in lib/Xt... making Makefiles in lib/Xss... make: don't know how to make Makefiles. Stop making Makefiles in lib/Xxf86misc... make: don't know how to make Makefiles. Stop making Makefiles in lib/Xxf86vm... "Makefile", line 752: Need an operator make: fatal errors encountered -- cannot continue making Makefiles in lib/Xxf86dga... "Makefile", line 752: Need an operator make: fatal errors encountered -- cannot continue making Makefiles in lib/Xmu... making Makefiles in lib/Xaw... making Makefiles in lib/XIE... make: don't know how to make Makefiles. Stop making Makefiles in lib/Xi... make: don't know how to make Makefiles. Stop making Makefiles in lib/Xtst... making Makefiles in lib/FS... make: don't know how to make Makefiles. Stop making Makefiles in lib/PEX5... make: don't know how to make Makefiles. Stop making Makefiles in lib/xkbfile... make: don't know how to make Makefiles. Stop making Makefiles in lib/xkbui... making Makefiles in lib/lbxutil... making Makefiles in lib/lbxutil/lbx_zlib... making Makefiles in lib/lbxutil/delta... making Makefiles in lib/lbxutil/image... make: don't know how to make Makefiles. Stop making Makefiles in lib/Xdpms... make: don't know how to make Makefiles. Stop making Makefiles in lib/Xp... making Makefiles in lib/font... making Makefiles in lib/font/bitmap... making Makefiles in lib/font/fontfile... make: don't know how to make Makefiles. Stop making Makefiles in lib/font/fc... make: don't know how to make Makefiles. Stop making Makefiles in lib/font/Speedo... making Makefiles in lib/font/Type1... make: don't know how to make Makefiles. Stop making Makefiles in lib/font/util... make: don't know how to make Makefiles. Stop making Makefiles in nls... making Makefiles in nls/XLC_LOCALE... make: don't know how to make Makefiles. Stop making Makefiles in nls/Compose... making Makefiles in programs... "Makefile", line 825: Need an operator make: fatal errors encountered -- cannot continue making Makefiles in fonts... making Makefiles in fonts/bdf... making Makefiles in fonts/bdf/misc... make: don't know how to make Makefiles. Stop making Makefiles in fonts/bdf/75dpi... making Makefiles in fonts/bdf/100dpi... making Makefiles in fonts/bdf/cyrillic... make: don't know how to make Makefiles. Stop making Makefiles in fonts/scaled... making Makefiles in fonts/scaled/Speedo... make: don't know how to make Makefiles. Stop making Makefiles in fonts/scaled/Type1... making Makefiles in fonts/PEX... make: don't know how to make Makefiles. Stop making Makefiles in doc... "Makefile", line 805: Need an operator make: fatal errors encountered -- cannot continue make -f xmakefile clean BOOTSTRAPSUBDIRS= : : : cleaning in lib/Xau... "Makefile", line 777: Need an operator make: fatal errors encountered -- cannot continue *** Error code 1 ================= lib/Xau/Makefile line - 777 says ======== 000: # Makefile generated by imake - do not edit! 001: # $TOG: imake.c /main/97 1997/06/20 20:23:51 kaleb $ 002: 003: # ---------------------------------------------------------------------- 004: # Makefile generated from "Imake.tmpl" and 005: # $TOG: Imake.tmpl /main/245 1997/05/20 10:05:47 kaleb $ : : : : : : : : 769: man_keywords:: 770: 771: # ---------------------------------------------------------------------- 772: # empty rules for directories that do not have SUBDIRS - do not edit 773: 774: install:: 775: @echo "install in $(CURRENT_DIR) done" 776: 777: ins To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 12 05:55:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA03861 for freebsd-current-outgoing; Sun, 12 Apr 1998 05:55:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hwcn.org (ac199@james.hwcn.org [199.212.94.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA03856 for ; Sun, 12 Apr 1998 05:55:12 -0700 (PDT) (envelope-from hoek@hwcn.org) Received: from localhost (ac199@localhost) by hwcn.org (8.8.8/8.8.8) with SMTP id IAA07564; Sun, 12 Apr 1998 08:50:48 -0400 (EDT) Date: Sun, 12 Apr 1998 08:50:48 -0400 (EDT) From: Tim Vanderhoek To: Kevin Day cc: current@FreeBSD.ORG Subject: Re: f00f + SMP = ick In-Reply-To: <199804120627.BAA00788@home.dragondata.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, 12 Apr 1998, Kevin Day wrote: > I can pretty much confirm that SMP -current kernels are are still vulnerable > to the f00f attack... This is analyzed in kern/5244, too. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 12 07:52:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA13325 for freebsd-current-outgoing; Sun, 12 Apr 1998 07:52:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA13316 for ; Sun, 12 Apr 1998 07:52:10 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id QAA16721 for ; Sun, 12 Apr 1998 16:51:16 +0200 (CEST) To: current@FreeBSD.ORG Subject: in case you're interested in NTP performance From: Poul-Henning Kamp Date: Sun, 12 Apr 1998 16:51:15 +0200 Message-ID: <16719.892392675@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG http://phk.freebsd.dk/rover.html -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 12 09:37:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24506 for freebsd-current-outgoing; Sun, 12 Apr 1998 09:37:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from burka.carrier.kiev.ua (root@burka.carrier.kiev.ua [193.193.193.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA24494 for ; Sun, 12 Apr 1998 09:36:47 -0700 (PDT) (envelope-from archer@grape.carrier.kiev.ua) Received: from unicorn.carrier.kiev.ua (unicorn.carrier.kiev.ua [193.193.193.113]) by burka.carrier.kiev.ua (8.8.8/8.Who.Cares) with ESMTP id TAA06511 for ; Sun, 12 Apr 1998 19:36:40 +0300 (EEST) Received: from kozlik.carrier.kiev.ua (kozlik.carrier.kiev.ua [193.193.193.111]) by unicorn.carrier.kiev.ua (8.8.8/8.8.7) with ESMTP id TAA08198 for ; Sun, 12 Apr 1998 19:36:38 +0300 (EEST) Received: (from uucp@localhost) by kozlik.carrier.kiev.ua (8.8.8/8.8.8/8.Who.Cares) with UUCP id TAA25422 for current@freebsd.org; Sun, 12 Apr 1998 19:30:50 +0300 (EEST) Received: (from archer@localhost) by grape.carrier.kiev.ua (8.8.8/8.8.8) id TAA00277; Sun, 12 Apr 1998 19:25:50 +0300 (EEST) (envelope-from archer) Message-ID: <19980412192549.51481@carrier.kiev.ua> Date: Sun, 12 Apr 1998 19:25:49 +0300 From: Alexander Litvin To: current@FreeBSD.ORG Subject: handle_workitem_remove: bad file delta Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, everybody! I'm not attempting to annoy somebody, but willing to see some progress in softupdates stuff. So I send the following backtrace of panic with current kernel (sources cvsupped Sun Apr 12 13:47:38 GMT 1998), during 'make -j8 buildworld', /usr/obj mounted with softupdates enabled. IdlePTD 217000 initial pcb at 1c8ce0 panicstr: handle_workitem_remove: bad file delta panic messages: --- panic: handle_workitem_remove: bad file delta syncing disks... 26 26 22 13 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 giving up dumping to dev 20001, offset 196608 dump 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:296 296 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=256) at ../../kern/kern_shutdown.c:296 #1 0xf01147a7 in panic ( fmt=0xf0174229 "handle_workitem_remove: bad file delta") at ../../kern/kern_shutdown.c:436 #2 0xf01742fd in handle_workitem_remove (dirrem=0xf0888080) at ../../ufs/ffs/ffs_softdep.c:2498 #3 0xf01717a9 in softdep_process_worklist (matchmnt=0x0) at ../../ufs/ffs/ffs_softdep.c:533 #4 0xf013332e in sched_sync () at ../../kern/vfs_subr.c:955 #5 0xf01083be in kproc_start (udata=0xf01bee14) at ../../kern/init_main.c:245 #6 0xf0195ad9 in fork_trampoline () Cannot access memory at address 0x1fff000. (kgdb) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 12 10:44:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02871 for freebsd-current-outgoing; Sun, 12 Apr 1998 10:44:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02832; Sun, 12 Apr 1998 10:44:39 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id TAA17213; Sun, 12 Apr 1998 19:43:45 +0200 (CEST) Date: Sun, 12 Apr 1998 19:43:44 +0200 Message-ID: <17211.892403024.1@critter.freebsd.dk> From: Poul-Henning Kamp Subject: IMPORTANT: PRs in suspended state MIME-Version: 1.0 Content-Type: multipart/digest; boundary="----- =_aaaaaaaaaa" Content-Description: Blind Carbon Copy Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To: undisclosed-recipients:; ------- =_aaaaaaaaaa Content-Type: message/rfc822 Content-Description: Original Message Subject: IMPORTANT: PRs in suspended state From: Poul-Henning Kamp Date: Sun, 12 Apr 1998 19:43:44 +0200 Message-ID: <17211.892403024@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Bcc: Blind Distribution List: ; In an attempt to get to the 3.0-RELEASE ready frame of mind, I am doing a end-to-other review of our Gnats database right now. The PRs which contain substance, but with little or no hope to get done will be moved to "suspended" state. There are a few PRs already in that state, which I have not visited yet, but when I'm done, "suspended" will have the meaning of: "Yeah, good idea, where is the patch ?" So these things will basically be up for grabs by anybody who feels like it. It is not a 100% guarantee that the code will be adopted if you write it, but chances are certainly very good. So if you are one of those people who don't know where to start: http://www.freebsd.org/cgi/query-pr-summary.cgi?state=s may provide you with some good ideas. Poul-Henning PS: It would help and speed my review, if you would check all the PRs you have opened, and close the ones which doesn't apply any more. If you are not a committer, just submit a followup saying "can be closed because: ..." -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." ------- =_aaaaaaaaaa-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 12 15:11:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA08565 for freebsd-current-outgoing; Sun, 12 Apr 1998 15:11:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wcc.wcc.net (wcc.wcc.net [208.6.232.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA08559 for ; Sun, 12 Apr 1998 15:11:29 -0700 (PDT) (envelope-from piquan@wcc.wcc.net) Received: from detlev.UUCP (tnt43.wcc.net [208.10.139.43]) by wcc.wcc.net (8.8.8/8.8.8) with ESMTP id RAA03060; Sun, 12 Apr 1998 17:07:08 -0500 (CDT) Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id RAA01455; Sun, 12 Apr 1998 17:10:21 -0500 (CDT) (envelope-from joelh) Date: Sun, 12 Apr 1998 17:10:21 -0500 (CDT) Message-Id: <199804122210.RAA01455@detlev.UUCP> To: tomdean@ix.netcom.com CC: current@FreeBSD.ORG In-reply-to: <199804110756.AAA04637@ix.netcom.com> (message from Thomas Dean on Sat, 11 Apr 1998 00:56:46 -0700 (PDT)) Subject: Re: Emacs E-Mail Slow From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199804110756.AAA04637@ix.netcom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have been using Emacs 19.34.1 for E-Mail and general editing. After > processing about a hundred messages and being on line for an hour, or > so, things get very slow. Getting mail from /var/mqueue/* takes much > longer than at startup. It takes 20 to 30 seconds to sort a hundred > headers. Editing in another frame appears normal. Do you have this same problem if you run 'emacs -no-init-file -nw'? I used RMAIL frequently under 19.34 (I now use a modified Emacs 20), and did not experience your problems. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 12 16:57:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA22916 for freebsd-current-outgoing; Sun, 12 Apr 1998 16:57:35 -0700 (PDT) (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 QAA22910 for ; Sun, 12 Apr 1998 16:57:32 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA15993; Sun, 12 Apr 1998 16:54:45 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd015990; Sun Apr 12 23:54:38 1998 Date: Sun, 12 Apr 1998 16:49:30 -0700 (PDT) From: Julian Elischer To: Alexander Litvin cc: current@FreeBSD.ORG Subject: Re: handle_workitem_remove: bad file delta In-Reply-To: <19980412192549.51481@carrier.kiev.ua> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for the backtrace.. softupdates work is presently stalled.. it is in a 'mostly works but not fully debugged' state at the moment. I hope to get back to it next week. I migh tadd that your backtrace is slightly differnt to the problems I am seeing, however it is obvious that there si a code-path that makes changes to metadata without telling the softupdates code about it. I will be looking for this next week. (kirk is away for 2 weeks and john is busy but I''m hoping that we can some progress with this before too long. julian On Sun, 12 Apr 1998, Alexander Litvin wrote: > Hi, everybody! > > I'm not attempting to annoy somebody, but willing to see > some progress in softupdates stuff. So I send the following > backtrace of panic with current kernel (sources cvsupped > Sun Apr 12 13:47:38 GMT 1998), during 'make -j8 buildworld', > /usr/obj mounted with softupdates enabled. > > IdlePTD 217000 > initial pcb at 1c8ce0 > panicstr: handle_workitem_remove: bad file delta > panic messages: > --- > panic: handle_workitem_remove: bad file delta > > syncing disks... 26 26 22 13 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 giving up > > dumping to dev 20001, offset 196608 > dump 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:296 > 296 dumppcb.pcb_cr3 = rcr3(); > (kgdb) bt > #0 boot (howto=256) at ../../kern/kern_shutdown.c:296 > #1 0xf01147a7 in panic ( > fmt=0xf0174229 "handle_workitem_remove: bad file delta") > at ../../kern/kern_shutdown.c:436 > #2 0xf01742fd in handle_workitem_remove (dirrem=0xf0888080) > at ../../ufs/ffs/ffs_softdep.c:2498 > #3 0xf01717a9 in softdep_process_worklist (matchmnt=0x0) > at ../../ufs/ffs/ffs_softdep.c:533 > #4 0xf013332e in sched_sync () at ../../kern/vfs_subr.c:955 > #5 0xf01083be in kproc_start (udata=0xf01bee14) at ../../kern/init_main.c:245 > #6 0xf0195ad9 in fork_trampoline () > Cannot access memory at address 0x1fff000. > (kgdb) > > > 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 Apr 12 17:24:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25905 for freebsd-current-outgoing; Sun, 12 Apr 1998 17:24:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA25899 for ; Sun, 12 Apr 1998 17:24:45 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id TAA02369; Sun, 12 Apr 1998 19:24:23 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199804130024.TAA02369@dyson.iquest.net> Subject: Re: handle_workitem_remove: bad file delta In-Reply-To: from Julian Elischer at "Apr 12, 98 04:49:30 pm" To: julian@whistle.com (Julian Elischer) Date: Sun, 12 Apr 1998 19:24:23 -0500 (EST) Cc: archer@lucky.net, 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 > Thanks for the backtrace.. > > softupdates work is presently stalled.. > it is in a 'mostly works but not fully debugged' state at the moment. > I hope to get back to it next week. > > I migh tadd that your backtrace is slightly differnt to the problems I am > seeing, however it is obvious that there si a code-path that makes changes > to metadata without telling the softupdates code about it. > > I will be looking for this next week. > (kirk is away for 2 weeks and john is busy but I''m hoping that we can > some progress with this before too long. > I'll be in the bay area next week, but I suggest that is it would be a good thing to get in touch with me as needed. (I am *super* busy when in the bay area, but the softupdates has languished too long, partially my fault.) John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 12 18:49:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA04985 for freebsd-current-outgoing; Sun, 12 Apr 1998 18:49:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wolfenet.com (root@frapp.wolfe.net [207.178.61.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA04980 for ; Sun, 12 Apr 1998 18:49:38 -0700 (PDT) (envelope-from moore@WOLFENET.com) Received: from gonzo.wolfenet.com (moore@gonzo.wolfenet.com [204.157.98.2]) by wolfenet.com (8.8.8/8.8.8) with ESMTP id SAA29379 for ; Sun, 12 Apr 1998 18:49:35 -0700 (PDT) Received: (from moore@localhost) by gonzo.wolfenet.com (8.8.3/8.7) id SAA23031; Sun, 12 Apr 1998 18:49:35 -0700 (PDT) Date: Sun, 12 Apr 1998 18:49:35 -0700 (PDT) Message-Id: <199804130149.SAA23031@gonzo.wolfenet.com> From: Timothy Moore To: current@FreeBSD.ORG Subject: CURRENT system gaining a lot of time? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running -current from Tuesday evening. My kernel seems to be gaining a lot of time, like 20 minutes per day. Is this a known problem? Here's my dmesg: Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #0: Tue Apr 7 22:45:15 PDT 1998 moore@herschel.pfgroup.com:/usr/src/sys/compile/HERSCHEL Timecounter "i8254" frequency 1193182 Hz cost 3025 ns Timecounter "TSC" frequency 89302867 Hz cost 376 ns CPU: Pentium (89.30-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x524 Stepping=4 Features=0x1bf real memory = 67108864 (65536K bytes) avail memory = 62738432 (61268K bytes) Probing for devices on PCI bus 0: chip0: rev 0x11 on pci0.0.0 chip1: rev 0x84 on pci0.2.0 ide_pci0: rev 0x02 int a irq 14 on pci0.3.0 de0: rev 0x23 int a irq 11 on pci0.13.0 de0: 21040 [10Mb/s] pass 2.3 de0: address 00:80:48:e8:1c:68 bt0: rev 0x00 int c irq 15 on pci0.14.0 bt0: Bt946C/ 0-(32bit) bus bt0: reading board settings, busmastering, int=15 bt0: version 4.25J, fast sync, parity, 32 mbxs, 32 ccbs bt0: targ 0 sync rate=10.00MB/s(100ns), offset=15 bt0: targ 5 sync rate= 5.00MB/s(200ns), offset=15 bt0: Using Strict Round robin scheme bt0: waiting for scsi devices to settle scbus0 at bt0 bus 0 sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access 2047MB (4194058 512 byte sectors) sd1 at scbus0 target 4 lun 0 sd1: type 0 fixed SCSI 2 sd1: Direct-Access 4095MB (8388315 512 byte sectors) st0 at scbus0 target 5 lun 0 st0: type 1 removable SCSI 2 st0: Sequential-Access density code 0x13, drive empty vga0: rev 0x00 int a irq 10 on pci0.15.0 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed1 not found at 0x300 sio0 at 0x3f8-0x3ff irq 4 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 lpt1 not found 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 not found at 0x1f0 wdc1 not found at 0x170 bt: unit number (1) too high bt1 not found at 0x330 npx0 on motherboard npx0: INT 16 interface Intel Pentium F00F detected, installing workaround changing root device to sd1s4a sd1: raw partition size != slice size sd1: start 0, end 8388314, size 8388315 sd1c: start 0, end 8386559, size 8386560 sd1: raw partition size != slice size sd1: start 0, end 8388314, size 8388315 sd1c: start 0, end 8386559, size 8386560 de0: autosense failed: cable problem? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 12 18:50:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05478 for freebsd-current-outgoing; Sun, 12 Apr 1998 18:50:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cabri.obs-besancon.fr (cabri.obs-besancon.fr [193.52.184.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA05428 for ; Sun, 12 Apr 1998 18:50:41 -0700 (PDT) (envelope-from jmz@cabri.obs-besancon.fr) Received: by cabri.obs-besancon.fr (5.57/Ultrix3.0-C) id AA22044; Mon, 13 Apr 98 03:53:23 +0200 Date: Mon, 13 Apr 98 03:53:23 +0200 Message-Id: <9804130153.AA22044@cabri.obs-besancon.fr> From: Jean-Marc Zucconi To: freebsd-current@FreeBSD.ORG Subject: nightmare: dump/restore broken X-Mailer: Emacs Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wanted to reorganize 2 disks: so I did a dump of the filesystems, relabeled/newfs'd the disks and restored the filesystems. This worked for the system disk (/, /usr, ....), but the situation is dramatic with my /home fs (the most important one, of course). After restore, I discovered that thousands (yes thousands :-() of files are empty and that a lot of other are truncated. It is also possible that some other files have grown. In short I losed 500Mbytes. I tried an old tape (2 months old): same result. I don't understand why the system files are ok, and this particular fs is broken. /dev/sd0a on / (NFS exported, local, writes: sync 153 async 1338)) /dev/sd0f on /usr (NFS exported, local, writes: sync 29 async 579)) /dev/sd0e on /var (local, writes: sync 179 async 479)) /dev/sd1e on /home (local, writes: sync 59 async 230)) I am runing a kernel from march, 30. Any help will be greatly appreciated... Jean-Marc _____________________________________________________________________________ Jean-Marc Zucconi Observatoire de Besancon F 25010 Besancon cedex PGP Key: finger jmz@cabri.obs-besancon.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 12 19:39:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA14680 for freebsd-current-outgoing; Sun, 12 Apr 1998 19:39:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cabri.obs-besancon.fr (cabri.obs-besancon.fr [193.52.184.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA14675 for ; Sun, 12 Apr 1998 19:39:07 -0700 (PDT) (envelope-from jmz@cabri.obs-besancon.fr) Received: by cabri.obs-besancon.fr (5.57/Ultrix3.0-C) id AA22247; Mon, 13 Apr 98 04:41:53 +0200 Date: Mon, 13 Apr 98 04:41:53 +0200 Message-Id: <9804130241.AA22247@cabri.obs-besancon.fr> From: Jean-Marc Zucconi To: jmz@cabri.obs-besancon.fr Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <9804130153.AA22044@cabri.obs-besancon.fr> (message from Jean-Marc Zucconi on Mon, 13 Apr 98 03:53:23 +0200) Subject: Re: nightmare: dump/restore broken X-Mailer: Emacs Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG One more point: I am able to restore a dump done on october. This seems to indicate that the kernel/restore combination is ok, and that the problem is with dump. Jean-Marc _____________________________________________________________________________ Jean-Marc Zucconi Observatoire de Besancon F 25010 Besancon cedex PGP Key: finger jmz@cabri.obs-besancon.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 13 03:00:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA19293 for freebsd-current-outgoing; Mon, 13 Apr 1998 03:00:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from solaric.UkrCard.COM (ukrcard-gu.gu.net [194.93.170.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA19251 for ; Mon, 13 Apr 1998 03:00:48 -0700 (PDT) (envelope-from alex@UkrCard.COM) Received: from localhost (alex@localhost) by solaric.UkrCard.COM (8.8.8/8.8.8) with SMTP id MAA15591; Mon, 13 Apr 1998 13:00:00 +0300 (EEST) (envelope-from alex@solaric.UkrCard.COM) Date: Mon, 13 Apr 1998 12:59:43 +0300 (EEST) From: Alexander Tatmaniants To: Gianmarco Giovannelli cc: current@FreeBSD.ORG Subject: Re: make world troubles with share/doc/smm/07.lpd In-Reply-To: <35307774.286EE4AC@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 Sun, 12 Apr 1998, Gianmarco Giovannelli wrote: > After cvsupping this morning (980412) I tried the daily make world but : > > 1) Soon an error in the make clean complaining about the missing 07.lpd > dir in obj tree ... created this dir make world proceeded but it stoped > here : > > 2) > ===> share/doc/smm/06.nfs > install -c -o bin -g bin -m 444 paper.ascii.gz > /usr/share/doc/smm/06.nfs > ===> share/doc/smm/07.lpd > install -c -o bin -g bin -m 444 bsd.README bsd.dep.mk bsd.doc.mk > bsd.info.mk bsd.kern.mk bsd.kmod.mk bsd.lib.mk bsd.libnames.mk > bsd.man.mk bsd.obj.mk bsd.own.mk bsd.port.mk bsd.port.subdir.mk > bsd.prog.mk bsd.sgml.mk bsd.subdir.mk sys.mk /mk ^^^ I think you have not this directory, it would be /usr/share/mk. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 13 06:04:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA19185 for freebsd-current-outgoing; Mon, 13 Apr 1998 06:04:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from r.scl.ameslab.gov (r.scl.ameslab.gov [147.155.137.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19180 for ; Mon, 13 Apr 1998 13:04:03 GMT (envelope-from ghelmer@scl.ameslab.gov) Received: from demios.scl.ameslab.gov (demios.ether.scl.ameslab.gov [147.155.137.54]) by r.scl.ameslab.gov (8.8.5/8.8.3) with SMTP id IAA17886 for ; Mon, 13 Apr 1998 08:03:58 -0500 (CDT) Date: Mon, 13 Apr 1998 08:03:57 -0500 (CDT) From: Guy Helmer To: current@FreeBSD.ORG Subject: Is current OK now?, was: A reminder of toxic -current In-Reply-To: <19980319134448.33500@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ----- Forwarded message from "John S. Dyson" ----- > > To: dyson@freebsd.org > > Date: Wed, 18 Mar 1998 22:07:57 -0500 (EST) > > Cc: dannyman@sasquatch.dannyland.org, dyson@freebsd.org, current@freebsd.org > > Reply-To: dyson@freebsd.org > > X-Mailer: ELM [version 2.4ME+ PL32 (25)] > > X-Loop: FreeBSD.ORG > > > John S. Dyson said: > >> > >> If -current works for you, I am still concerned. I would be misleading you > >> and others if I stated otherwise!!! I really do care about people getting > >> messed up filesystems!!! > >> > > Following up on my own posting: Maybe I am not being strong enough in > > my suggestion: Please do not use the -current kernel unless you know > > that the consequences will be that you will likely loose filesystem(s). Apologies if I missed the announcement, but is has the current kernel stabilized to its normal "probably works" state? Thanks, Guy Helmer Guy Helmer, Graduate Student, Iowa State University Dept. of Computer Science Research Assistant, Ames Laboratory --- ghelmer@scl.ameslab.gov http://www.cs.iastate.edu/~ghelmer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 13 08:19:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA10972 for freebsd-current-outgoing; Mon, 13 Apr 1998 08:19:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from asteroid.svib.ru (root@asteroid.svib.ru [195.151.166.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA10951 for ; Mon, 13 Apr 1998 15:18:47 GMT (envelope-from tarkhil@asteroid.svib.ru) Received: from minas-tirith.pol.ru (shuttle.svib.ru [195.151.166.144]) by asteroid.svib.ru (8.8.8/8.8.8) with ESMTP id TAA15149; Mon, 13 Apr 1998 19:18:41 +0400 (MSD) (envelope-from tarkhil@asteroid.svib.ru) Received: from minas-tirith.pol.ru (minas-tirith.pol.ru [127.0.0.1]) by minas-tirith.pol.ru (8.8.8/8.8.7) with ESMTP id TAA14985; Mon, 13 Apr 1998 19:19:12 +0400 (MSD) (envelope-from tarkhil@minas-tirith.pol.ru) Message-Id: <199804131519.TAA14985@minas-tirith.pol.ru> X-Mailer: exmh version 2.0.1 12/23/97 To: Guy Helmer cc: current@FreeBSD.ORG Subject: Re: Is current OK now?, was: A reminder of toxic -current In-reply-to: Your message "Mon, 13 Apr 1998 08:03:57 CDT." Reply-To: tarkhil@asteroid.svib.ru Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 13 Apr 1998 19:19:12 +0400 From: Alex Povolotsky Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Guy Helmer wr ites: >Apologies if I missed the announcement, but is has the current kernel >stabilized to its normal "probably works" state? Looks like "yes"... Alex. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 13 10:46:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15078 for freebsd-current-outgoing; Mon, 13 Apr 1998 10:46:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA15058 for ; Mon, 13 Apr 1998 17:45:59 GMT (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id LAA06802 for ; Mon, 13 Apr 1998 11:45:59 -0600 (MDT) Message-Id: <199804131745.LAA06802@pluto.plutotech.com> X-Mailer: exmh version 2.0.1 12/23/97 To: scsi@FreeBSD.ORG Subject: CAM 980413 snapshot available Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 13 Apr 1998 01:04:40 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Full information about CAM can be obtained from: ftp://ftp.FreeBSD.org/pub/FreeBSD/cam/README or ftp://ftp.kdm.org/pub/FreeBSD/cam/README Changes for the 980413 Snapshot: - New BusLogic/Mylex MultiMaster driver. - Tape driver now properly reports and allows the configuration of compression and density settings. mt not only reports if compression is available, but the type of compression that is being used. - Tape driver properly returns short or 0 length reads at EOF and EOM. - Dump understands ENOSPC and works in multi-volume mode with the CAM tape driver. -- Justin T. Gibbs Kenneth D. Merry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 13 10:55:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA16979 for freebsd-current-outgoing; Mon, 13 Apr 1998 10:55:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rvc1.informatik.ba-stuttgart.de (rvc1.informatik.ba-stuttgart.de [141.31.112.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA16973 for ; Mon, 13 Apr 1998 17:55:28 GMT (envelope-from helbig@Informatik.BA-Stuttgart.DE) Received: (from helbig@localhost) by rvc1.informatik.ba-stuttgart.de (8.8.8/8.8.5) id TAA01655; Mon, 13 Apr 1998 19:54:20 +0200 (MET DST) From: Wolfgang Helbig Message-Id: <199804131754.TAA01655@rvc1.informatik.ba-stuttgart.de> Subject: Re: Misspelling in lib/libutil/login_cap.3 [w/ patch] In-Reply-To: <199804110418.OAA08739@cimlogic.com.au> from John Birrell at "Apr 11, 98 02:18:23 pm" To: jb@cimlogic.com.au (John Birrell) Date: Mon, 13 Apr 1998 19:54:19 +0200 (MET DST) Cc: jfieber@indiana.edu, jb@cimlogic.com.au, chadf@bookcase.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (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 > John Fieber wrote: > > On Sat, 11 Apr 1998, John Birrell wrote: > > > > > Chad M. Fraleigh wrote: > > > > > > > > "authorisation" should be "authorization". > > > > > > In my _*English*_ dictionary, either is acceptable. > > > > Citation please? > > The Concise Oxford Dictionary 5th edition. Printed in Great Britain. > > > Not found in the Oxford English Dictionary (2nd ed), nor any of > > Check if the 's' and 'z' versions are under the _same_ entry. > They are in mine. > > > the American dictionaries I have on hand (American Heritage, > > Webster). > > > > It may be acceptable somewhere, but I dare say that the "z" > > version is much more widely accepted. > > Sorry, at school I was taught English, not American. So was I: - In my English-German dictionary only ``-ize'' and never ``-ise'' appears. - There is no language called ``American'', only ``American spelling''. The language is English. - In the dictionary there is a section about American versus British spelling. They don't even mentrion ``-ize'' or ``-ise''. So to me it appears that ``-ise'' is an Australian speciality, neither common in Great Britain nor in the US. Wolfgang, an amazed German. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 13 13:10:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06757 for freebsd-current-outgoing; Mon, 13 Apr 1998 13:10:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fang.cs.sunyit.edu (root@fang.cs.sunyit.edu [192.52.220.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA06752 for ; Mon, 13 Apr 1998 20:10:28 GMT (envelope-from perlsta@cs.sunyit.edu) Received: from win95.local.sunyit.edu (A-T34.rh.sunyit.edu [150.156.210.241]) by fang.cs.sunyit.edu (8.8.5/8.7.3) with SMTP id PAA01966 for ; Mon, 13 Apr 1998 15:12:01 GMT Message-ID: <000301bd6717$9608a6a0$0600a8c0@win95.local.sunyit.edu> From: "Alfred Perlstein" To: Subject: compiling newest wine seems to cause crash. Date: Mon, 13 Apr 1998 16:06:02 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG can someone on a recent -current box try compiling the latest version of wine? the url to wine is: ftp://sunsite.unc.edu/pub/Linux/ALPHA/wine/development/Wine-980413.tar.gz try this after exctraction: ./configure && gmake depend && gmake -j4 (running as a normal user) it's crashed my machine twice so far. i thought it was a freak thing cause i was playing with my cdrom at the moment... anyhow i'm off to cvsup and compile a debuggin kernel. thank you, Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 13 13:24:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09093 for freebsd-current-outgoing; Mon, 13 Apr 1998 13:24:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fang.cs.sunyit.edu (root@fang.cs.sunyit.edu [192.52.220.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA09083 for ; Mon, 13 Apr 1998 20:24:01 GMT (envelope-from perlsta@cs.sunyit.edu) Received: from win95.local.sunyit.edu (A-T34.rh.sunyit.edu [150.156.210.241]) by fang.cs.sunyit.edu (8.8.5/8.7.3) with SMTP id PAA02131 for ; Mon, 13 Apr 1998 15:25:40 GMT Message-ID: <007001bd6719$7e62f620$0600a8c0@win95.local.sunyit.edu> From: "Alfred Perlstein" To: Subject: Re: compiling newest wine seems to cause crash. Date: Mon, 13 Apr 1998 16:19:42 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >can someone on a recent -current box try compiling the latest version of >wine? > >the url to wine is: > anyhow, i don't seem to get any disk damage (which is odd on a -j# compile), but then again, the disks aren't marked clean on reboot, so it's prolly just a coincidence and i also don't have async or anything odd right now, just normal mount. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 13 14:56:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA27144 for freebsd-current-outgoing; Mon, 13 Apr 1998 14:56:33 -0700 (PDT) (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 VAA27125 for ; Mon, 13 Apr 1998 21:56:10 GMT (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id XAA05009 for freebsd-current@FreeBSD.ORG; Mon, 13 Apr 1998 23:55:53 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.9.0.Beta4/keltia-2.14/nospam) id XAA08425; Mon, 13 Apr 1998 23:48:30 +0200 (CEST) (envelope-from roberto) Message-ID: <19980413234828.A428@keltia.freenix.fr> Date: Mon, 13 Apr 1998 23:48:28 +0200 From: Ollivier Robert To: "FreeBSD Current Users' list" Subject: More on softupdates Mail-Followup-To: FreeBSD Current Users' list Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91i X-Operating-System: FreeBSD 3.0-CURRENT ctm#4209 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG During "make world", I got the following panic twice. I use softupdates for /usr/src & /usr/obj. The block # (bno) was different each time. /work (the FS as below) is only used for /tmp. CURRENT sources as of cvs-cur #4209 (1998/04/13 07:14:37). dev=0x30403 bno=754974743 bsize=8192 size=8192 fs=/work panic: ffs_blkfree: bad size Trace: _ffs_blkfree _indir_trunc _handle_workitem_freeblocks _softdep_process_worklist(0) _sched_sync _kproc_start _fork_trampoline -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #0: Mon Mar 30 22:21:31 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 13 15:48:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA11724 for freebsd-current-outgoing; Mon, 13 Apr 1998 15:48:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA11688 for ; Mon, 13 Apr 1998 22:47:56 GMT (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 17852 invoked by uid 1001); 13 Apr 1998 22:47:50 +0000 (GMT) To: freebsd-current@FreeBSD.ORG Subject: Fixes for tcpdump with LPIP encapsulation X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Tue, 14 Apr 1998 00:47:50 +0200 Message-ID: <17850.892507670@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Having recently bought a laptop, I've been using the parallel port and the LPIP encapsulation quite a bit. I found that tcpdump was completely broken for LPIP encapsulation, like this: tcpdump: WARNING: compensating for unaligned libpcap packets 00:21:22.606701 truncated-ip - 2777 bytes missing!3.1.192.168 > 3.2.8.0: (frag 0:2859@63496+) [tos 0x54] 00:21:22.608240 [|ip] This is one ping and its reply, and *should* look like: 00:23:27.306352 192.168.3.1 > 192.168.3.2: icmp: echo request 00:23:27.308098 192.168.3.2 > 192.168.3.1: icmp: echo reply There are several problems with the current BPF code in the LPIP (lpt) driver: - The DLT_NULL link layer type is just plain wrong for LPIP, because LPIP has a two byte (0x0800) "type" header in front of the packet, while tcpdump expects DLT_NULL to mean a four byte type header. - The code to send a packet calls bpf_mtap after the bytes have been sent, but at that point the length fields in the mbufs have been counted down to -1. - The code to send a packet makes an extra mbuf with the two byte type header to satisfy BPF - but tcpdump expects this in network byte order. I fixed the problem with the link layer type by defining a *new* link layer type (DLT_LPIP). This seems to me to be the cleanest solution (alternatives: remove the two byte header and use DLT_RAW, or expand it to four bytes, and use DLT_NULL). Unfortunately it's also the solution which touches the most files (changes needed for libpcap and tcpdump). Thus I'd like to have some comments from the good people on -current on whether this is the correct way of solving the problem, before I feed the changes back to the tcpdump/libpcap maintainers. Below are patches for these problems, affecting the following files: sys/i386/isa/lpt.c sys/net/bpf.c sys/net/bpf.h usr.sbin/tcpdump/tcpdump/Makefile contrib/libpcap/gencode.c contrib/libpcap/bpf/net/bpf.h contrib/tcpdump/tcpdump.c contrib/tcpdump/print-lpip.c contrib/tcpdump/interface.h plus the changed sys/net/bpf.h should also go into /usr/include/net. I've added some missing link types from the current LBL version of tcpdump/libpcap, and put the new link type at the first free entry. contrib/tcpdump/print-lpip.c is a new file, modeled after print-raw.c I've kept the same copyright notice even if this may not be strictly correct. Feel free to tack on the copyright that's most suitable if these changes are accepted. The same patches can be used almost unchanged for 2.2.6. print-lpip.c needs to have #include changed to #include Steinar Haug, Nethelp consulting, sthaug@nethelp.no ---------------------------------------------------------------------- *** sys/i386/isa/lpt.c.orig Tue Dec 2 22:06:24 1997 --- sys/i386/isa/lpt.c Mon Apr 13 14:12:32 1998 *************** *** 878,884 **** printf("lp%d: TCP/IP capable interface\n", unit); #if NBPFILTER > 0 ! bpfattach(ifp, DLT_NULL, LPIPHDRLEN); #endif } /* --- 878,884 ---- printf("lp%d: TCP/IP capable interface\n", unit); #if NBPFILTER > 0 ! bpfattach(ifp, DLT_LPIP, LPIPHDRLEN); #endif } /* *************** *** 1314,1321 **** mm = m; do { cp = mtod(mm,u_char *); ! while (mm->m_len--) if (lpoutbyte(*cp++, LPMAXSPIN2, lpt_data_port, lpt_stat_port)) goto end; } while ((mm = mm->m_next)); --- 1314,1322 ---- mm = m; do { + int l = mm->m_len; cp = mtod(mm,u_char *); ! while (l--) if (lpoutbyte(*cp++, LPMAXSPIN2, lpt_data_port, lpt_stat_port)) goto end; } while ((mm = mm->m_next)); *************** *** 1342,1348 **** * try to free it or keep a pointer to it). */ struct mbuf m0; ! u_short hdr = 0x800; m0.m_next = m; m0.m_len = 2; --- 1343,1349 ---- * try to free it or keep a pointer to it). */ struct mbuf m0; ! u_short hdr = htons(0x800); m0.m_next = m; m0.m_len = 2; *** sys/net/bpf.c.orig Tue Nov 18 17:29:53 1997 --- sys/net/bpf.c Mon Apr 13 14:12:32 1998 *************** *** 190,195 **** --- 190,196 ---- break; case DLT_NULL: + case DLT_LPIP: sockp->sa_family = AF_UNSPEC; hlen = 0; break; *** sys/net/bpf.h.orig Sat Feb 22 10:40:55 1997 --- sys/net/bpf.h Mon Apr 13 14:12:32 1998 *************** *** 146,151 **** --- 146,155 ---- #define DLT_PPP 9 /* Point-to-point Protocol */ #define DLT_FDDI 10 /* FDDI */ #define DLT_ATM_RFC1483 11 /* LLC/SNAP encapsulated atm */ + #define DLT_RAW 12 /* raw IP */ + #define DLT_SLIP_BSDOS 13 /* BSD/OS Serial Line IP */ + #define DLT_PPP_BSDOS 14 /* BSD/OS Point-to-point Protocol */ + #define DLT_LPIP 15 /* BSD parallel port "encapsulation" */ /* * The instruction encodings. *** usr.sbin/tcpdump/tcpdump/Makefile.orig Tue May 27 04:21:28 1997 --- usr.sbin/tcpdump/tcpdump/Makefile Mon Apr 13 15:38:56 1998 *************** *** 11,17 **** print-decnet.c print-domain.c print-dvmrp.c print-egp.c \ print-ether.c print-fddi.c print-gre.c print-icmp.c \ print-igrp.c print-ip.c print-ipx.c print-isoclns.c print-krb.c \ ! print-llc.c print-nfs.c print-ntp.c print-null.c print-ospf.c \ print-pim.c print-ppp.c print-rip.c print-sl.c print-snmp.c \ print-sunrpc.c print-tcp.c print-tftp.c print-udp.c print-wb.c \ addrtoname.c bpf_dump.c machdep.c parsenfsfh.c util.c --- 11,17 ---- print-decnet.c print-domain.c print-dvmrp.c print-egp.c \ print-ether.c print-fddi.c print-gre.c print-icmp.c \ print-igrp.c print-ip.c print-ipx.c print-isoclns.c print-krb.c \ ! print-llc.c print-lpip.c print-nfs.c print-ntp.c print-null.c print-ospf.c \ print-pim.c print-ppp.c print-rip.c print-sl.c print-snmp.c \ print-sunrpc.c print-tcp.c print-tftp.c print-udp.c print-wb.c \ addrtoname.c bpf_dump.c machdep.c parsenfsfh.c util.c *** contrib/libpcap/gencode.c.orig Tue May 27 02:05:20 1997 --- contrib/libpcap/gencode.c Mon Apr 13 15:34:59 1998 *************** *** 519,524 **** --- 519,529 ---- off_linktype = -1; off_nl = 0; return; + + case DLT_LPIP: + off_linktype = -1; + off_nl = 2; + return; } bpf_error("unknown data link type 0x%x", linktype); /* NOTREACHED */ *** contrib/libpcap/bpf/net/bpf.h.orig Tue May 27 02:01:11 1997 --- contrib/libpcap/bpf/net/bpf.h Mon Apr 13 23:59:22 1998 *************** *** 170,175 **** --- 170,178 ---- #define DLT_FDDI 10 /* FDDI */ #define DLT_ATM_RFC1483 11 /* LLC/SNAP encapsulated atm */ #define DLT_RAW 12 /* raw IP */ + #define DLT_SLIP_BSDOS 13 /* BSD/OS Serial Line IP */ + #define DLT_PPP_BSDOS 14 /* BSD/OS Point-to-point Protocol */ + #define DLT_LPIP 15 /* BSD parallel port "encapsulation" */ /* * The instruction encondings. *** contrib/tcpdump/tcpdump.c.orig Tue May 27 04:11:29 1997 --- contrib/tcpdump/tcpdump.c Mon Apr 13 15:33:42 1998 *************** *** 98,103 **** --- 98,104 ---- { fddi_if_print, DLT_FDDI }, { null_if_print, DLT_NULL }, { atm_if_print, DLT_ATM_RFC1483 }, + { lpip_if_print, DLT_LPIP }, { NULL, 0 }, }; *** contrib/tcpdump/print-lpip.c.orig Mon Apr 13 15:33:42 1998 --- contrib/tcpdump/print-lpip.c Tue Apr 14 00:01:40 1998 *************** *** 0 **** --- 1,90 ---- + /* + * Copyright (c) 1996 + * The Regents of the University of California. All rights reserved. + * + * Redistribution and use in source and binary forms, with or without + * modification, are permitted provided that: (1) source code distributions + * retain the above copyright notice and this paragraph in its entirety, (2) + * distributions including binary code include the above copyright notice and + * this paragraph in its entirety in the documentation or other materials + * provided with the distribution, and (3) all advertising materials mentioning + * features or use of this software display the following acknowledgement: + * ``This product includes software developed by the University of California, + * Lawrence Berkeley Laboratory and its contributors.'' Neither the name of + * the University nor the names of its contributors may be used to endorse + * or promote products derived from this software without specific prior + * written permission. + * THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED + * WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF + * MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. + */ + + #include + #include + #include + #include + #include + + #if __STDC__ + struct mbuf; + struct rtentry; + #endif + #include + + #include + #include + #include + #include + #include + #include + #include + #include + #include + + #include + #include + #include + + #include "addrtoname.h" + #include "interface.h" + + #ifndef AF_NS + #define AF_NS 6 /* XEROX NS protocols */ + #endif + + /* + * The DLT_LPIP packet has a two byte header containing 0x0800, followed + * by a raw IP packet. + */ + #define LPIP_HDRLEN 2 + + void + lpip_if_print(u_char *user, const struct pcap_pkthdr *h, const u_char *p) + { + u_int length = h->len; + u_int caplen = h->caplen; + const struct ip *ip; + + ts_print(&h->ts); + + /* + * Some printers want to get back at the link level addresses, + * and/or check that they're not walking off the end of the packet. + * Rather than pass them all the way down, we set these globals. + */ + packetp = p; + snapend = p + caplen; + + length -= LPIP_HDRLEN; + + ip = (struct ip *)(p + LPIP_HDRLEN); + + if (eflag) + printf("ip: "); + + ip_print((const u_char *)ip, length); + + if (xflag) + default_print(p, caplen); + putchar('\n'); + } *** contrib/tcpdump/interface.h.orig Tue May 27 04:11:11 1997 --- contrib/tcpdump/interface.h Mon Apr 13 15:33:42 1998 *************** *** 185,190 **** --- 185,191 ---- extern void isoclns_print(const u_char *, u_int, u_int, const u_char *, const u_char *); extern void krb_print(const u_char *, u_int); + extern void lpip_if_print(u_char *, const struct pcap_pkthdr *, const u_char *); extern void nfsreply_print(const u_char *, u_int, const u_char *); extern void nfsreq_print(const u_char *, u_int, const u_char *); extern void ns_print(const u_char *, u_int); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 13 15:57:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA15110 for freebsd-current-outgoing; Mon, 13 Apr 1998 15:57:58 -0700 (PDT) (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 WAA15075 for ; Mon, 13 Apr 1998 22:57:56 GMT (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id PAA26356; Mon, 13 Apr 1998 15:52:59 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd026346; Mon Apr 13 22:52:52 1998 Message-ID: <3532960A.59E2B600@whistle.com> Date: Mon, 13 Apr 1998 15:47:38 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: Ollivier Robert CC: "FreeBSD Current Users' list" Subject: Re: More on softupdates References: <19980413234828.A428@keltia.freenix.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG working on it... Ollivier Robert wrote: > > During "make world", I got the following panic twice. I use softupdates for > /usr/src & /usr/obj. The block # (bno) was different each time. /work (the > FS as below) is only used for /tmp. > > CURRENT sources as of cvs-cur #4209 (1998/04/13 07:14:37). > > dev=0x30403 bno=754974743 bsize=8192 size=8192 fs=/work > panic: ffs_blkfree: bad size > > Trace: > _ffs_blkfree > _indir_trunc > _handle_workitem_freeblocks > _softdep_process_worklist(0) > _sched_sync > _kproc_start > _fork_trampoline > -- > Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr > FreeBSD keltia.freenix.fr 3.0-CURRENT #0: Mon Mar 30 22:21:31 CEST 1998 > > 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 Apr 13 19:03:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA18869 for freebsd-current-outgoing; Mon, 13 Apr 1998 19:03:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.rwth-aachen.de (mail.RWTH-Aachen.DE [137.226.144.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA18856 for ; Tue, 14 Apr 1998 02:03:01 GMT (envelope-from heinig@hdz-ima.rwth-aachen.de) Received: from HDZ-IMA.RWTH-Aachen.de (majestix.hdz-ima.RWTH-Aachen.DE) by mail.rwth-aachen.de (PMDF V5.1-10 #23726) with ESMTP id <01IVUAVNAPLE0004DE@mail.rwth-aachen.de> for current@freebsd.org; Tue, 14 Apr 1998 01:17:36 +0200 Received: from MAJESTIX/MAIL by HDZ-IMA.RWTH-Aachen.de (Mercury 1.20); Tue, 14 Apr 1998 00:17:47 +0000 Received: from MAIL by MAJESTIX (Mercury 1.20); Tue, 14 Apr 1998 00:17:37 +0000 Received: from hdz-ima.rwth-aachen.de by HDZ-IMA.RWTH-Aachen.de (Mercury 1.20) with ESMTP; Tue, 14 Apr 1998 00:17:29 +0000 Date: Tue, 14 Apr 1998 01:17:09 +0200 From: Gerald Heinig Subject: Spelling etc. To: current@FreeBSD.ORG Message-id: <35329CF4.65DE8E18@hdz-ima.rwth-aachen.de> MIME-version: 1.0 X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.5-RELEASE i386) Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi guys, I always thought spelling was a non-issue for hackers. It seems I was wrong. It also seems to me to be an absolutely trivial problem of whether or not we authorise or authorize, since the meaning is quite clear. What an enormous number of people canīt seem to grasp is the difference between: The dog wagged its tail (*NOT* itīs tail!!!) and Itīs cold today (ie. It is cold today) Or stuff like: ....the variables are passed to the function and there values are changed. Does this mean: ...the variables are passed to the function and there, inside the function, *their* values are changed... or does it mean ...the variables are passed to the function, and inside the function some other, unconnected variables are changed... Iīve come across quite a few examples like those above and sometimes it really does change the meaning of the sentence. The only way to work out what the author meant is to write a test program to check. Apart from numerous occasions where misleading documentation has caused hours of pointless experimentation, making really *basic* spelling mistakes gives a product a very tacky feel. The idea is: if they canīt even get simple spelling right, whatīs their code going to look like? Keep up the good work Gerald To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 13 19:08:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA20259 for freebsd-current-outgoing; Mon, 13 Apr 1998 19:08:00 -0700 (PDT) (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 CAA20252 for ; Tue, 14 Apr 1998 02:07:59 GMT (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.HIP.Berkeley.EDU (ala-ca34-37.ix.netcom.com [207.93.143.165]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id TAA27161; Mon, 13 Apr 1998 19:07:57 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.8/8.6.9) id TAA01350; Mon, 13 Apr 1998 19:07:50 -0700 (PDT) Date: Mon, 13 Apr 1998 19:07:50 -0700 (PDT) Message-Id: <199804140207.TAA01350@silvia.HIP.Berkeley.EDU> To: heinig@hdz-ima.rwth-aachen.de CC: current@FreeBSD.ORG In-reply-to: <35329CF4.65DE8E18@hdz-ima.rwth-aachen.de> (message from Gerald Heinig on Tue, 14 Apr 1998 01:17:09 +0200) Subject: Re: Spelling etc. From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You loose. Satoshi :> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 13 19:26:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA24880 for freebsd-current-outgoing; Mon, 13 Apr 1998 19:26:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from goliath.camtech.com.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA24872 for ; Tue, 14 Apr 1998 02:26:41 GMT (envelope-from thyerm@camtech.net.au) Received: from camtech.net.au (dialup-ad-1-08.camtech.net.au [203.28.0.40]) by goliath.camtech.com.au (8.8.5/8.8.2) with ESMTP id LAA00084; Tue, 14 Apr 1998 11:53:45 +0930 (CST) Message-ID: <3532C93D.153F59B3@camtech.net.au> Date: Tue, 14 Apr 1998 11:56:05 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.05 [en] (X11; U; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: tarkhil@asteroid.svib.ru CC: Guy Helmer , current@FreeBSD.ORG Subject: Re: Is current OK now?, was: A reminder of toxic -current References: <199804131519.TAA14985@minas-tirith.pol.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maybe not so OK yet. I just got the following sig 11 from trying to compile Wine-980104 on a very recent version of CURRENT (CTM 3325). Also, dont use softupdates. (this is not a reflection on the stability of CURRENT). cc -c -O -pipe -Wall -D__WINE__ -I../include -I../include -I. -I. -I/usr/X11R6/ include -o registry.o ./registry.c ./registry.c: In function `SHELL_StartupRegistry': ./registry.c:293: warning: unused variable `cpubuf' ./registry.c:292: warning: unused variable `F' ./registry.c: In function `_w95_loadreg': ./registry.c:1160: warning: `key' might be used uninitialized in this function cc -c -O -pipe -Wall -D__WINE__ -I../include -I../include -I. -I. -I/usr/X11R6/ include -o shell.o ./shell.c ./shell.c: In function `InternalExtractIcon': ./shell.c:1154: warning: cast to pointer from integer of different size cc -c -O -pipe -Wall -D__WINE__ -I../include -I../include -I. -I. -I/usr/X11R6/ include -o shellord.o ./shellord.c cc: Internal compiler error: program cc1 got fatal signal 11 *** Error code 1 Alex Povolotsky wrote: > > Guy Helmer wr > ites: > >Apologies if I missed the announcement, but is has the current kernel > >stabilized to its normal "probably works" state? > > Looks like "yes"... > > Alex. > > 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 Mon Apr 13 19:29:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA25686 for freebsd-current-outgoing; Mon, 13 Apr 1998 19:29:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shadow.worldbank.org (shadow.worldbank.org [138.220.104.78]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA25665; Tue, 14 Apr 1998 02:29:38 GMT (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.8.8/8.8.8) with SMTP id WAA20996; Mon, 13 Apr 1998 22:29:07 -0400 (EDT) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Mon, 13 Apr 1998 22:29:07 -0400 (EDT) From: "Alok K. Dhir" To: asami@FreeBSD.ORG cc: heinig@hdz-ima.rwth-aachen.de, current@FreeBSD.ORG Subject: Re: Spelling etc. In-Reply-To: <4738EA2F469E8411852565E6000BF6F8.000B3809852565E6@worldbank.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 That's "lose". ;-) On Mon, 13 Apr 1998 asami@FreeBSD.ORG wrote: > You loose. > > Satoshi :> > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -------------------------------------------------------------------- \||/_ Alok K. Dhir Phone: +1.202.473.2446 oo \ S13-069, ISGMC Email: adhir@worldbank.org L_ The World Bank Group Washington, DC \/ ------------------------------------------------------------------------| "Unix _is_ user friendly - it just chooses friends selectively..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 13 19:47:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA28577 for freebsd-current-outgoing; Mon, 13 Apr 1998 19:47:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oldnews.quick.net (donegan@oldnews.quick.net [207.212.170.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA28571; Tue, 14 Apr 1998 02:47:35 GMT (envelope-from donegan@oldnews.quick.net) Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id TAA00538; Mon, 13 Apr 1998 19:47:32 -0700 (PDT) Date: Mon, 13 Apr 1998 19:47:32 -0700 (PDT) From: "Steven P. Donegan" To: "Alok K. Dhir" cc: asami@FreeBSD.ORG, heinig@hdz-ima.rwth-aachen.de, current@FreeBSD.ORG Subject: Re: Spelling etc. 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, 13 Apr 1998, Alok K. Dhir wrote: > > That's "lose". ;-) > > On Mon, 13 Apr 1998 asami@FreeBSD.ORG wrote: > > > You loose. > > > > Satoshi :> > > Please, can we stop discussing spelling? My emailbox runneth over with non-technical items :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 13 19:47:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA28646 for freebsd-current-outgoing; Mon, 13 Apr 1998 19:47:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.visint.co.uk (wakko.visint.co.uk [194.207.134.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA28633 for ; Tue, 14 Apr 1998 02:47:42 GMT (envelope-from steve@visint.co.uk) Received: from dylan (dylan.visint.co.uk [194.207.134.180]) by mail.visint.co.uk (8.8.8/8.8.5) with SMTP id DAA02183; Tue, 14 Apr 1998 03:45:41 +0100 (BST) Date: Tue, 14 Apr 1998 03:46:32 +0100 (BST) From: Stephen Roome X-Sender: steve@dylan To: Mike Smith cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: ps segfaults since I overclocked. and worries. In-Reply-To: <199804101947.MAA00847@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, 10 Apr 1998, Mike Smith wrote: > > There is some mention of this in /sys/pci/ide_pci.c, I > > This is a timing issue related to conformance with the various IDE > standards. Do you or anyone else know where I can get a copy of the IDE standards, I should probably have already read them before I even asked. > > am 100% certain that the hardware I have is performing fine at these > > speeds, > You have an observed aberration, yet you are "100% certain"? Who are > you kidding? I see your point. Someone replied earlier with the incredibly sensible suggestion that I should recompile my ps binary. Worked a treat! So, the hardware was fine after all, I'd just not got the software in proper order. Wasn't kidding anyone, I just hadn't made myself clear. > > Does the following mean that some new PC's are not going to work properly? > > And that FreeBSD just won't support them ? > > No. It means that you are expected to run the parts involved (the > VIA571 and Intel PIIXn) at their rated speeds. If you correctly > configure your system, this is what will happen. It was probably worth mentioning a long time ago that this isn't an Intel chipset based board: ide_pci0: rev 0x06 on pci0.7.1 Hypothetically : If I purchase a 6x86 that is supposed to run at 188Mhz, and hence a bus speed of 75Mhz (and run it on this board - an FIC PA2007) does this mean that the frequency the IDE devices are clocked at is greater than 30 or 33Mhz ? If so, then would a correctly configured system still work as you say? As this isn't what the comment in the code implies to me. If not, then I think I realise whats going on, but don't see how one would overclock the IDE devices (the code implies that it's possible). If I've got something wrong then please could someone explain it to me. I just wanted to know how/why it works or doesn't. P.S. I'm talking about a hypothetical system here, which isnt overclocked. Thanks, Steve Steve Roome - Vision Interactive Ltd. Tel:+44(0)117 9730597 Home:+44(0)976 241342 WWW: http://dylan.visint.co.uk/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 14 02:41:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA04253 for freebsd-current-outgoing; Tue, 14 Apr 1998 02:41:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peedub.muc.de (newpc.muc.ditec.de [194.120.126.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA04244 for ; Tue, 14 Apr 1998 09:41:11 GMT (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.8.8/8.6.9) with ESMTP id LAA11264 for ; Tue, 14 Apr 1998 11:41:36 +0200 (CEST) Message-Id: <199804140941.LAA11264@peedub.muc.de> X-Mailer: exmh version 2.0.1 12/23/97 To: freebsd-current@FreeBSD.ORG Subject: Re: ps segfaults since I overclocked. and worries. Reply-To: Gary Jennejohn In-reply-to: Your message of "Tue, 14 Apr 1998 03:46:32 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 14 Apr 1998 11:41:36 +0200 From: Gary Jennejohn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stephen Roome writes: >It was probably worth mentioning a long time ago that this isn't an Intel >chipset based board: > >ide_pci0: rev 0x06 on >pci0.7.1 > >Hypothetically : > >If I purchase a 6x86 that is supposed to run at 188Mhz, and hence a bus >speed of 75Mhz (and run it on this board - an FIC PA2007) does this mean >that the frequency the IDE devices are clocked at is greater than 30 or >33Mhz ? > >If so, then would a correctly configured system still work as you say? As >this isn't what the comment in the code implies to me. > IIRC, from a recent article in c't magazine, some motherboards, even though using a chipset which supposedly supports asynchronous bus clocks, do not set the chipset up correctly (a BIOS problem, usually). And some chipsets which claim to provide such support, do not really do so. Unfortunately, I don't have the magazine here. They tested a whole slew of motherboards, and this was a problem in many cases. Can't remember whether VIA/FIC was one of the bad guys. Of course, it seems like a "correctly configured" system should work. The big question is, whether the manufacturer does the setup correctly. --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.dec.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 14 07:14:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA19073 for freebsd-current-outgoing; Tue, 14 Apr 1998 07:14:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from set.spradley.tmi.net (set.spradley.tmi.net [207.170.107.99]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA19067 for ; Tue, 14 Apr 1998 14:14:38 GMT (envelope-from tsprad@set.spradley.tmi.net) Received: from localhost (set.spradley.tmi.net) [127.0.0.1] by set.spradley.tmi.net with esmtp (Exim 1.82 #2) id 0yP6Tf-0003SQ-00; Tue, 14 Apr 1998 09:14:23 -0500 X-Mailer: exmh version 2.0zeta 7/24/97 To: Stephen Roome Cc: current@FreeBSD.ORG Subject: Re: ps segfaults since I overclocked. and worries. In-reply-to: Your message of "Tue, 14 Apr 1998 03:46:32 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 14 Apr 1998 09:14:23 -0500 From: Ted Spradley Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I see your point. Someone replied earlier with the incredibly sensible > suggestion that I should recompile my ps binary. Worked a treat! So, the > hardware was fine after all, I'd just not got the software in proper > order. Wasn't kidding anyone, I just hadn't made myself clear. I hope I wasn't the only one who suggested that. If everything else works, then the problem is probably with the thing that doesn't work, the ps command. Seems to me like an obvious place to look. I was really surprised by the intense negative reaction to overclocking. The manufacturer tests the parts an then decides how to mark the parts based on the results of those tests and other marketing considerations, like the demand for slower parts and the embarrassment of not having faster ratings than the competition. The Do-It-Yourselfer tests the whole system and then decides how fast to run it based on the results of those tests and other considerations, like the cost of shortening the life of some parts and the inconvenience of a potential intermittent failure. What's the big deal? Last I heard, even wcarchive.cdrom.com is overclocked. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 14 07:35:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA22542 for freebsd-current-outgoing; Tue, 14 Apr 1998 07:35:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA22536 for ; Tue, 14 Apr 1998 14:35:43 GMT (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id HAA08207; Tue, 14 Apr 1998 07:34:15 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Ted Spradley cc: Stephen Roome , current@FreeBSD.ORG Subject: Re: ps segfaults since I overclocked. and worries. In-reply-to: Your message of "Tue, 14 Apr 1998 09:14:23 CDT." Date: Tue, 14 Apr 1998 07:34:15 -0700 Message-ID: <8203.892564455@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I was really surprised by the intense negative reaction to overclocking. > The manufacturer tests the parts an then decides how to mark the parts > based on the results of those tests and other marketing considerations, > like the demand for slower parts and the embarrassment of not having > faster ratings than the competition. The Do-It-Yourselfer tests the > whole system and then decides how fast to run it based on the results of > those tests and other considerations, like the cost of shortening the > life of some parts and the inconvenience of a potential intermittent > failure. What's the big deal? The big deal is that it makes it impossible to provide meaningful tech support for hardware problems when people do this, and ask us for tech support they do to the tune of hundreds of man hours a week. In order to make the tech support system even begin to work, it was absolutely necessary that certain ground rules be laid down and one of those rules is *no overclocking during debugging*. It's a very simple rule and one which is non-negotiable. It seemed (perhaps erroneously) that Stephen was wanting help with a hardware issue before properly obeying the ground rules and so, of course, people reacted negatively. We're really quite serious about those ground rules and absolutely will not help anyone until they're in full compliance with them. If that wasn't known before, let it be known now! :-) Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 14 07:41:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA23830 for freebsd-current-outgoing; Tue, 14 Apr 1998 07:41:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shadow.worldbank.org (shadow.worldbank.org [138.220.104.78]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23814 for ; Tue, 14 Apr 1998 14:41:52 GMT (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.8.8/8.8.8) with SMTP id KAA28272; Tue, 14 Apr 1998 10:38:15 -0400 (EDT) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Tue, 14 Apr 1998 10:38:15 -0400 (EDT) From: "Alok K. Dhir" To: tsprad@set.spradley.tmi.net cc: steve@visint.co.uk, current@FreeBSD.ORG Subject: Re: ps segfaults since I overclocked. and worries. 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, 14 Apr 1998 tsprad@set.spradley.tmi.net wrote: > I was really surprised by the intense negative reaction to overclocking. > The manufacturer tests the parts an then decides how to mark the parts > based on the results of those tests and other marketing considerations, > like the demand for slower parts and the embarrassment of not having > faster ratings than the competition. The Do-It-Yourselfer tests the > whole system and then decides how fast to run it based on the results of > those tests and other considerations, like the cost of shortening the > life of some parts and the inconvenience of a potential intermittent > failure. What's the big deal? Its not a big deal - until there are problems and you tell "tech support" you're overclocked. Then there's a big deal, because the immediate assumption is to blame the overclocking, and you'll never get past that, even if you un-overclock. If the problem still exists, you're typically told that the overclocking must have caused permanent damage. The moral of the story is "never admit to overclocking when asking for support". :-) Seriously, though, you give up the right to certain things when you overclock. When you run your machine out of spec, you can't be surprised when things start getting screwy, and there's just no easy way to tell what it is that's broken. If you are an overclocker, you need to be prepared to support yourself. -------------------------------------------------------------------- \||/_ Alok K. Dhir Phone: +1.202.473.2446 oo \ S13-069, ISGMC Email: adhir@worldbank.org L_ The World Bank Group Washington, DC \/ ------------------------------------------------------------------------| "Unix _is_ user friendly - it just chooses friends selectively..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 14 13:19:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04975 for freebsd-current-outgoing; Tue, 14 Apr 1998 13:19:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA04969 for ; Tue, 14 Apr 1998 20:19:21 GMT (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id WAA01121; Tue, 14 Apr 1998 22:18:04 +0200 (CEST) To: sthaug@nethelp.no cc: freebsd-current@FreeBSD.ORG Subject: Re: Fixes for tcpdump with LPIP encapsulation In-reply-to: Your message of "Tue, 14 Apr 1998 00:47:50 +0200." <17850.892507670@verdi.nethelp.no> Date: Tue, 14 Apr 1998 22:18:04 +0200 Message-ID: <1119.892585084@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I fixed the problem with the link layer type by defining a *new* link >layer type (DLT_LPIP). This seems to me to be the cleanest solution >(alternatives: remove the two byte header and use DLT_RAW, or expand it >to four bytes, and use DLT_NULL). Unfortunately it's also the solution >which touches the most files (changes needed for libpcap and tcpdump). >Thus I'd like to have some comments from the good people on -current on >whether this is the correct way of solving the problem, before I feed >the changes back to the tcpdump/libpcap maintainers. I think using DLT_NULL or DLT_RAW is preferable. Changing tcpdump and libpcap for the sake of LPIP really seems like overdoing it to me... Thanks for the attention to this neglegted child of mine... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 14 13:36:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08315 for freebsd-current-outgoing; Tue, 14 Apr 1998 13:36:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA08303 for ; Tue, 14 Apr 1998 20:36:08 GMT (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 27333 invoked by uid 1001); 14 Apr 1998 20:36:02 +0000 (GMT) To: phk@critter.freebsd.dk Cc: freebsd-current@FreeBSD.ORG Subject: Re: Fixes for tcpdump with LPIP encapsulation In-Reply-To: Your message of "Tue, 14 Apr 1998 22:18:04 +0200" References: <1119.892585084@critter.freebsd.dk> X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Tue, 14 Apr 1998 22:36:02 +0200 Message-ID: <27331.892586162@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Thus I'd like to have some comments from the good people on -current on > >whether this is the correct way of solving the problem, before I feed > >the changes back to the tcpdump/libpcap maintainers. > > I think using DLT_NULL or DLT_RAW is preferable. Changing tcpdump and > libpcap for the sake of LPIP really seems like overdoing it to me... That was my initial reaction too, but then I saw that BSDI had had their PPP and SLIP implementations given special types: #define DLT_SLIP_BSDOS 13 /* BSD/OS Serial Line IP */ #define DLT_PPP_BSDOS 14 /* BSD/OS Point-to-point Protocol */ So I thought - if it makes sense for BSDI, it might make sense for FreeBSD too. I'll look into using DLT_NULL or DLT_RAW. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 14 15:16:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00244 for freebsd-current-outgoing; Tue, 14 Apr 1998 15:16:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from m7.sprynet.com (m7.sprynet.com [165.121.2.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA00231 for ; Tue, 14 Apr 1998 22:16:38 GMT (envelope-from connecte@sprynet.com) Received: from sprynet.com (sbu1536.sbu.edu [149.76.206.0]) by m7.sprynet.com (8.8.5/8.8.5) with ESMTP id PAA27064 for ; Tue, 14 Apr 1998 15:16:32 -0700 (PDT) Message-ID: <3533DEC3.95AF82A7@sprynet.com> Date: Tue, 14 Apr 1998 18:10:11 -0400 From: Matthew & Lori Taylor Reply-To: connecte@sprynet.com Organization: Maledil Productions X-Mailer: Mozilla 4.04 [en] (Win95; U) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: IP address assignment 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 a NOVICE user of UNIX so, bear w/ me here. How/where do I configure the IP address for the NIC? I didn't see anything in the kernel setup, which is understandable, but is there a startup script that I can edit so the IP address that I need is static on the card? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 14 15:16:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00245 for freebsd-current-outgoing; Tue, 14 Apr 1998 15:16:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from m7.sprynet.com (m7.sprynet.com [165.121.2.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA00234 for ; Tue, 14 Apr 1998 22:16:39 GMT (envelope-from connecte@sprynet.com) Received: from sprynet.com (sbu1536.sbu.edu [149.76.206.0]) by m7.sprynet.com (8.8.5/8.8.5) with ESMTP id PAA27103 for ; Tue, 14 Apr 1998 15:16:37 -0700 (PDT) Message-ID: <3533DF1D.FCE1CA95@sprynet.com> Date: Tue, 14 Apr 1998 18:11:41 -0400 From: Matthew & Lori Taylor Reply-To: connecte@sprynet.com Organization: Maledil Productions X-Mailer: Mozilla 4.04 [en] (Win95; U) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Changing the prompt_name Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How would I change the prompt_name in the OS? Currently it's still . I am a NOVICE UNIX user, so if this question seems dumb, well.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 14 15:28:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02890 for freebsd-current-outgoing; Tue, 14 Apr 1998 15:28:48 -0700 (PDT) (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 WAA02884 for ; Tue, 14 Apr 1998 22:28:47 GMT (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id PAA01124; Tue, 14 Apr 1998 15:22:38 -0700 (PDT) Message-Id: <199804142222.PAA01124@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Stephen Roome cc: Mike Smith , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: ps segfaults since I overclocked. and worries. In-reply-to: Your message of "Tue, 14 Apr 1998 03:46:32 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 14 Apr 1998 15:22:37 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, 10 Apr 1998, Mike Smith wrote: > > > There is some mention of this in /sys/pci/ide_pci.c, I > > > > This is a timing issue related to conformance with the various IDE > > standards. > > Do you or anyone else know where I can get a copy of the IDE standards, > I should probably have already read them before I even asked. ftp://fission.dt.wdc.com/standards You will also want the PIIX datasheeds from Intel, as well as those for other PCI IDE controllers from VIA, SiS, etc. if you want the full complement. Some of these are easy to find, some can take quite a lot of work. > > > am 100% certain that the hardware I have is performing fine at these > > > speeds, > > You have an observed aberration, yet you are "100% certain"? Who are > > you kidding? > > I see your point. Someone replied earlier with the incredibly sensible > suggestion that I should recompile my ps binary. Worked a treat! So, the > hardware was fine after all, I'd just not got the software in proper > order. Wasn't kidding anyone, I just hadn't made myself clear. This really suggests that you changed more than "just" the clock speed - recompiling ps is normally only a requirement when you've updated your kernel - it's certainly not sensitive to CPU speed! Rule #1 when experimenting: Change _only_one_thing_ at a time. > > > Does the following mean that some new PC's are not going to work properly? > > > And that FreeBSD just won't support them ? > > > > No. It means that you are expected to run the parts involved (the > > VIA571 and Intel PIIXn) at their rated speeds. If you correctly > > configure your system, this is what will happen. > > It was probably worth mentioning a long time ago that this isn't an Intel > chipset based board: > > ide_pci0: rev 0x06 on > pci0.7.1 Hmm, somewhat pertinent. Your mention of the motherboard model is more useful though. > Hypothetically : > > If I purchase a 6x86 that is supposed to run at 188Mhz, and hence a bus > speed of 75Mhz (and run it on this board - an FIC PA2007) does this mean > that the frequency the IDE devices are clocked at is greater than 30 or > 33Mhz ? This depends on the board implementation, and the devices in question. As a general rule, if the board claims that the higher bus speeds are supported, then the design will cater for operating the IDE interfaces at the correct speed. It would be a valid question to ask whether the IDE controller requires different programming in order to operate the IDE bus at the correct speed - you would need chipset documentation to verify this (by examining the driver source). > If so, then would a correctly configured system still work as you say? As > this isn't what the comment in the code implies to me. A correctly configured system will have a 33MHz clock available to the IDE controller so that it can generate the 8.3MHz Ultra-DMA clock, or provide extra configurability such that the IDE controller can compensate. Note that requiring the IDE driver to know the bus speed is extremely bogus, but not out of the question. > If not, then I think I realise whats going on, but don't see how one would > overclock the IDE devices (the code implies that it's possible). If the IDE controller chip expects to be only ever fed with a 30/33MHz clock (eg. Intel PIIX), and the motherboard has a fixed ratio between the CPU:memory clock and PCI clock (most Intel-based boards), then if you pull the CPU:memory clock above rated spec (eg. 66MHz) you bring the clock to the IDE controller over spec too. An example: consider an Intel-based board using a PIIX controller and the 440LX AGPset. Boards of this ilk generally run with a 66MHz master clock. The clock is internally multiplied in the CPU to obtain the core clock, and divided by 2 to obtain the PCI clock, which is also fed to the PIIX. The PIIX divides by 4 again to produce the UDMA clock. If you raise this to 75MHz, the PCI clock rises to 37.5MHz, and the UDMA clock rises to 9.375MHz. This increase is more than enough for cable noise, marginal timing, etc. to become an issue. A "more correct" board design would ensure that the PCI clock stayed at 33MHz - this is not (AFAIK) feasible with the Intel chipsets (bus rate conversion is expensive, and Intel design for speed which is why they are going straight for 100MHz). > If I've got something wrong then please could someone explain it to me. I > just wanted to know how/why it works or doesn't. I hope the above is at least marginally helpful - part of the problem here is just that despite all the marketting hype to the contrary, modern PC systems are quite complex and vary enormously at the detail level, and this detail is often difficult to ascertain without access to data that often just isn't available. -- \\ 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 Apr 14 15:34:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04159 for freebsd-current-outgoing; Tue, 14 Apr 1998 15:34:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.mishkei.org.il (host3-64.mishkei.org.il [62.0.64.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA04081 for ; Tue, 14 Apr 1998 22:34:07 GMT (envelope-from lickyou@ein-hashofet.co.il) Received: from box.from.hell (host40-68.mishkei.org.il [62.0.68.40]) by mail.mishkei.org.il (8.8.5/8.8.5) with SMTP id BAA17340; Wed, 15 Apr 1998 01:31:58 +0300 Date: Wed, 15 Apr 1998 01:32:41 +0000 (GMT) From: Gilad Rom X-Sender: lickyou@box.from.hell To: Matthew & Lori Taylor cc: freebsd-current@FreeBSD.ORG Subject: Re: Changing the prompt_name In-Reply-To: <3533DF1D.FCE1CA95@sprynet.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, 14 Apr 1998, Matthew & Lori Taylor wrote: > How would I change the prompt_name in the OS? Currently it's still > . I am a NOVICE UNIX user, so if this question seems dumb, > well.... > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Have you tried looking at the handbook on www.freebsd.org? Im sure there are plenty of newbie and novice questions answered in there. Try the irc channel on EFnet (#FreeBSD) for more questions. Oh, and to configure the IP addresses, take a look at /etc/rc.conf . cya Gilad. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 14 15:49:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07787 for freebsd-current-outgoing; Tue, 14 Apr 1998 15:49:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebsd.scds.com (jseger.shore.net [204.167.102.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA07782 for ; Tue, 14 Apr 1998 22:49:44 GMT (envelope-from jseger@freebsd.scds.com) Received: (from jseger@localhost) by freebsd.scds.com (8.8.8/8.8.5) id SAA06059; Tue, 14 Apr 1998 18:56:18 -0400 (EDT) Date: Tue, 14 Apr 1998 18:56:18 -0400 (EDT) Message-Id: <199804142256.SAA06059@freebsd.scds.com> From: "Justin M. Seger" To: connecte@sprynet.com CC: freebsd-current@FreeBSD.ORG In-reply-to: <3533DEC3.95AF82A7@sprynet.com> (message from Matthew & Lori Taylor on Tue, 14 Apr 1998 18:10:11 -0400) Subject: Re: IP address assignment References: <3533DEC3.95AF82A7@sprynet.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How/where do I configure the IP address for the NIC? I didn't see anything in the kernel setup, which is understandable, but is there a startup script that I can edit so the IP address that I need is static on the card? Hi. This kind of question should be sent to questions@freebsd.org, please send all further questions that don't relate to FreeBSD-current (FreeBSD 3.X) to that address. Look in the file /etc/rc.conf, the ifconfig lines do that for you. TTYL, -Justin Seger- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 14 16:19:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA13265 for freebsd-current-outgoing; Tue, 14 Apr 1998 16:19:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sendero-fddi.simon-shapiro.org (sendero-fddi.Simon-Shapiro.ORG [206.190.148.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA13226 for ; Tue, 14 Apr 1998 23:18:57 GMT (envelope-from shimon@sendero-fddi.simon-shapiro.org) Received: (qmail 17971 invoked by uid 1000); 14 Apr 1998 23:28:18 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-040798 [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: <9804130153.AA22044@cabri.obs-besancon.fr> Date: Tue, 14 Apr 1998 16:28:18 -0700 (PDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Jean-Marc Zucconi Subject: RE: nightmare: dump/restore broken Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 13-Apr-98 Jean-Marc Zucconi wrote: ... > I tried an old tape (2 months old): same result. ^^^^ Keyword. It is not dump/restore. It is the tape. Shall I guess DAT on SCSI? Since a while back, they only work with 512 byte blocks. Dump/re store do not know how to handle larger blocks... > I don't understand why the system files are ok, and this particular fs > is broken. > /dev/sd0a on / (NFS exported, local, writes: sync 153 async 1338)) > /dev/sd0f on /usr (NFS exported, local, writes: sync 29 async 579)) > /dev/sd0e on /var (local, writes: sync 179 async 479)) > /dev/sd1e on /home (local, writes: sync 59 async 230)) Probably has something to do with blovking factors. I can solidly lock up or crash the system with tape operations. Try cpio to two separate tape drives... total confusion with regards to biodone callbacks. ---------- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG Voice: 503.799.2313 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 14 17:43:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01062 for freebsd-current-outgoing; Tue, 14 Apr 1998 17:43:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cabri.obs-besancon.fr (cabri.obs-besancon.fr [193.52.184.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA01055 for ; Wed, 15 Apr 1998 00:43:54 GMT (envelope-from jmz@cabri.obs-besancon.fr) Received: by cabri.obs-besancon.fr (5.57/Ultrix3.0-C) id AA03967; Wed, 15 Apr 98 02:46:26 +0200 Date: Wed, 15 Apr 98 02:46:26 +0200 Message-Id: <9804150046.AA03967@cabri.obs-besancon.fr> From: Jean-Marc Zucconi To: shimon@simon-shapiro.org Cc: freebsd-current@FreeBSD.ORG In-Reply-To: (message from Simon Shapiro on Tue, 14 Apr 1998 16:28:18 -0700 (PDT)) Subject: Re: RE: nightmare: dump/restore broken X-Mailer: Emacs Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> Simon Shapiro writes: > On 13-Apr-98 Jean-Marc Zucconi wrote: > ... >> I tried an old tape (2 months old): same result. > ^^^^ > Keyword. It is not dump/restore. It is the tape. Shall I guess DAT on > SCSI? Since a while back, they only work with 512 byte blocks. Dump/re > store do not know how to handle larger blocks... I don't think so. If this were the case, it would fail immediately whereas I see may files which are correctly restored. On the other hand the last dump was not done on my DAT, but on a file on another partition. And this one is broken too. There were no problems with my /usr partition, maybe because it is smaller. I will try to restore again and check where it begins to extract bad data. Jean-Marc _____________________________________________________________________________ Jean-Marc Zucconi Observatoire de Besancon F 25010 Besancon cedex PGP Key: finger jmz@cabri.obs-besancon.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 14 18:49:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA13136 for freebsd-current-outgoing; Tue, 14 Apr 1998 18:49:35 -0700 (PDT) (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 BAA13119 for ; Wed, 15 Apr 1998 01:49:32 GMT (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id SAA01812 for ; Tue, 14 Apr 1998 18:46:48 -0700 (PDT) Message-Id: <199804150146.SAA01812@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: current@FreeBSD.ORG Subject: HEADS UP: CAM cutover in two weeks. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 14 Apr 1998 18:46:47 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG One of the major feature goals for 3.0 is the transition to the new CAM-inspired SCSI subsystem. This transition requires a hard cutover date. The proposed cutover date is the 28th of April. On or about this point in time, the following steps will be taken: - A CVS tag will be applied to mark the last checkout date prior to the cutover. - The CAM code will be committed to the -current branch. - GENERIC and LINT will be translated to suit. - MAKEDEV will be updated. - Non-CAM SCSI code and drivers will be *disabled*. There will be an announcement at least 24 hours preceeding the cutover. It is important to note that the cutover to CAM will result in a number of SCSI adapters and devices becoming *unsupported*. A number of these are significant items, and developers are encouraged to take the time to update drivers which they may have an interest in. FreeBSD Test Labs will endeavour to provide loan equipment to developers undertaking such updates. The following SCSI adapters will become unsupported: Driver Adapter Owner ------ ------- ----- aha Adaptec 1542 ? (*)(+) aic Adaptec aic6x60 ? (*)(+) amd NCR 53c974 ? (*) dpt DPT RAID controllers Simon Shapiro (*) nca NCR 53c400 ? sea Seagate ST01/ST02 ? uha Ultrastor 34F ? (*)(+) vpo Iomega ppa3 (eg. Zip) Nicolas Souchu (*)(+) wds Western Digital WD7000 ? The following SCSI peripherals will become unsupported: Driver Adapter ------ ------- od Optical-disk device (*)(+) uk Unknown SCSI device worm Write-once SCSI device Drivers marked (*) are considered to be currently supported, and desirable for 3.0. FreeBSD Test Labs has development hardware available for loan to developers for drivers marked (+). In some cases, documentation may also be available. If there are any significant issues (other than FUD) relating to the proposed cutover, now is the time to raise them. Followups should be directed as follows: - Technical matters relating to updating a driver for CAM: freebsd-scsi@freebsd.org - All other issues: freebsd-current@freebsd.org -- \\ 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 Apr 14 19:26:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA22789 for freebsd-current-outgoing; Tue, 14 Apr 1998 19:26:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gneiss.eps.nagoya-u.ac.jp (gneiss.eps.nagoya-u.ac.jp [133.6.124.148]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA22731 for ; Wed, 15 Apr 1998 02:26:51 GMT (envelope-from kato@migmatite.eps.nagoya-u.ac.jp) Received: from localhost (localhost [127.0.0.1]) by gneiss.eps.nagoya-u.ac.jp (8.8.8/3.6Wbeta7) with ESMTP id LAA01264; Wed, 15 Apr 1998 11:25:24 +0900 (JST) To: mike@smith.net.au Cc: current@FreeBSD.ORG Subject: Re: HEADS UP: CAM cutover in two weeks. From: KATO Takenori In-Reply-To: Your message of "Tue, 14 Apr 1998 18:46:47 -0700" <199804150146.SAA01812@dingo.cdrom.com> References: <199804150146.SAA01812@dingo.cdrom.com> X-Mailer: Mew version 1.92.4 on Emacs 19.28 / Mule 2.3 (SUETSUMUHANA) X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19980415112523I.kato@gneiss.eps.nagoya-u.ac.jp> Date: Wed, 15 Apr 1998 11:25:23 +0900 X-Dispatcher: imput version 971024 Lines: 13 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > - Non-CAM SCSI code and drivers will be *disabled*. Where can I obtain the documentation for how to CAMify existing code? I need to keep bs driver (sys/i386/isa/bs) work to develop PC-98 code. -----------------------------------------------+--------------------------+ Kato Takenori | FreeBSD | Dept. Earth Planet. Sci, Nagoya Univ. | The powere to serve! | Nagoya, 464-8602, Japan | http://www.FreeBSD.org/ | ++++ FreeBSD(98) 2.2.6: coming soon! +==========================+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 14 22:25:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA23494 for freebsd-current-outgoing; Tue, 14 Apr 1998 22:25:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from granch.nsk.su (root@ns.granch.nsk.su [194.135.201.254]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA23451 for ; Wed, 15 Apr 1998 05:25:04 GMT (envelope-from shelton@sentry.granch.nsk.su) Received: from sentry.granch.nsk.su (1001@sentry.granch.nsk.su [194.135.201.135]) by granch.nsk.su (8.7.3/8.7.3) with SMTP id MAA27982; Wed, 15 Apr 1998 12:23:40 +0700 (NSD) Date: Wed, 15 Apr 1998 12:26:06 +0700 (NSS) From: "Rashid N. Achilov" To: Matthew & Lori Taylor cc: freebsd-current@FreeBSD.ORG Subject: Re: Changing the prompt_name In-Reply-To: <3533DF1D.FCE1CA95@sprynet.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, 14 Apr 1998, Matthew & Lori Taylor wrote: > How would I change the prompt_name in the OS? Currently it's still > . I am a NOVICE UNIX user, so if this question seems dumb, Try next: (in your .cshrc if you use csh or somewhere if you use another shell) if ($?prompt) then # An interactive shell -- set some stuff up set mch = `hostname -s` set prompt = "${mch:q}:[$USER] \!>" endif Best Regards, Rashid N. Achilov E-Mail: shelton@sentry.granch.nsk.su Granch Ltd. lead engineer FidoNet: 2:5000/92.1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 14 23:00:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA00202 for freebsd-current-outgoing; Tue, 14 Apr 1998 23:00:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uop.cs.uop.edu (uop.cs.uop.edu [138.9.200.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA00118 for ; Wed, 15 Apr 1998 05:59:58 GMT (envelope-from bford@uop.cs.uop.edu) Received: from heather (user187.pop2.cwia.com [209.142.32.187]) by uop.cs.uop.edu (8.8.8/8.8.8) with SMTP id WAA20428 for ; Tue, 14 Apr 1998 22:59:54 -0700 (PDT) Message-ID: <007701bd6833$b84396e0$0100000a@heather.my.domain> From: "Bret Ford" To: Subject: Wanted: Adaptec 1542c under CAM Date: Tue, 14 Apr 1998 22:59:48 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've got nearly zero programming ability---all I can do is complain :-) ---Is there likely to be 1542c support when CAM is merged, or have I been marooned? Aging hardware is becoming a lonely island these days. Bret Ford To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 14 23:01:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA00340 for freebsd-current-outgoing; Tue, 14 Apr 1998 23:01:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from solaris.matti.ee (root@solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA00331 for ; Wed, 15 Apr 1998 06:01:18 GMT (envelope-from vallo@matti.ee) Received: from localhost (vallo@localhost [127.0.0.1]) by solaris.matti.ee (8.8.8/8.8.8.s) with SMTP id JAA23639 for ; Wed, 15 Apr 1998 09:01:03 +0300 (EET DST) Date: Wed, 15 Apr 1998 09:01:02 +0300 (EET DST) From: Vallo Kallaste X-Sender: vallo@solaris To: freebsd-current@FreeBSD.ORG Subject: calcru: negative time, what is 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 Hello ! In the last two months or so I'm using current heavily and I keep getting messages like below: calcru: negative time of -39217543 usec for pid 1519 (smbd) This last is caused by heavy samba usage ( my colleague was using samba to copy full Slackware 3.4 mirror which resides on my machine ). From time to time these messages arrive on my console, not very often, but this irritates me enough to write to this list. There are no other things which accompany with this one, maybe even this message is needed for some purpose, I don't know. Thanks 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 Apr 14 23:08:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA02123 for freebsd-current-outgoing; Tue, 14 Apr 1998 23:08:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles111.castles.com [208.214.165.111]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA02118 for ; Wed, 15 Apr 1998 06:08:13 GMT (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id XAA00610; Tue, 14 Apr 1998 23:04:57 -0700 (PDT) Message-Id: <199804150604.XAA00610@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Bret Ford" cc: freebsd-current@FreeBSD.ORG Subject: Re: Wanted: Adaptec 1542c under CAM In-reply-to: Your message of "Tue, 14 Apr 1998 22:59:48 PDT." <007701bd6833$b84396e0$0100000a@heather.my.domain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 14 Apr 1998 23:04:57 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've got nearly zero programming ability---all I can do is > complain :-) ---Is there likely to be 1542c support when CAM is > merged, or have I been marooned? Aging hardware is becoming a lonely island > these days. It would be fair enough to say that the sheer weight of castaways on your particular island would be such that nobody could ignore it. If there is no CAM support for the 1542 at the merge date, you can expect it to follow as one of the highest-priority items therafter. -- \\ 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 Apr 14 23:23:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA06068 for freebsd-current-outgoing; Tue, 14 Apr 1998 23:23:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA06055 for ; Wed, 15 Apr 1998 06:23:32 GMT (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id IAA02758; Wed, 15 Apr 1998 08:22:31 +0200 (CEST) To: Vallo Kallaste cc: freebsd-current@FreeBSD.ORG Subject: Re: calcru: negative time, what is it ? In-reply-to: Your message of "Wed, 15 Apr 1998 09:01:02 +0300." Date: Wed, 15 Apr 1998 08:22:30 +0200 Message-ID: <2756.892621350@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Vallo Kallaste w rites: >Hello ! > >In the last two months or so I'm using current heavily and I keep getting >messages like below: > >calcru: negative time of -39217543 usec for pid 1519 (smbd) How current is this code ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 14 23:30:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA07817 for freebsd-current-outgoing; Tue, 14 Apr 1998 23:30:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail3.aracnet.com (root@mail3.aracnet.com [205.159.88.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA07749 for ; Wed, 15 Apr 1998 06:29:51 GMT (envelope-from beattie@aracnet.com) Received: from shell2.aracnet.com (beattie@shell2.aracnet.com [205.159.88.20]) by mail3.aracnet.com (8.8.8/8.8.5) with ESMTP id XAA03238; Tue, 14 Apr 1998 23:29:45 -0700 Received: from localhost by shell2.aracnet.com (8.8.7) id XAA19419; Tue, 14 Apr 1998 23:29:45 -0700 Date: Tue, 14 Apr 1998 23:29:45 -0700 (PDT) From: Brian Beattie To: Mike Smith cc: Bret Ford , freebsd-current@FreeBSD.ORG Subject: Re: Wanted: Adaptec 1542c under CAM In-Reply-To: <199804150604.XAA00610@antipodes.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, 14 Apr 1998, Mike Smith wrote: > > I've got nearly zero programming ability---all I can do is > > complain :-) ---Is there likely to be 1542c support when CAM is > > merged, or have I been marooned? Aging hardware is becoming a lonely island > > these days. > > It would be fair enough to say that the sheer weight of castaways on > your particular island would be such that nobody could ignore it. > > If there is no CAM support for the 1542 at the merge date, you can > expect it to follow as one of the highest-priority items therafter. > I have been working on support for the 1542, but the lack of documentation has slowed me up so I am currently trying to document the CAM kernel functions. Being currently unemployed I hope to have a good first cut done by the end of the week. Then I'll see what I can do about the driver it'self. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 14 23:34:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA09644 for freebsd-current-outgoing; Tue, 14 Apr 1998 23:34:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA09570 for ; Wed, 15 Apr 1998 06:34:19 GMT (envelope-from michael_class@hp.com) Received: from hpbbse.bbn.hp.com (root@hpbbse.bbn.hp.com [15.136.26.26]) by palrel1.hp.com (8.8.6/8.8.5tis) with ESMTP id XAA02836; Tue, 14 Apr 1998 23:34:10 -0700 (PDT) Received: from hp.com (michaelc@tmbbwmc.bbn.hp.com [15.136.25.181]) by hpbbse.bbn.hp.com with ESMTP (8.7.6/8.7.3) id HAA25281; Wed, 15 Apr 1998 07:34:08 +0100 (MEZ) Message-ID: <353454DE.F6020EDC@hp.com> Date: Wed, 15 Apr 1998 08:34:06 +0200 From: Michael Class Organization: Hewlett-Packard GmbH X-Mailer: Mozilla 4.05 [en] (X11; I; HP-UX B.10.20 9000/777) MIME-Version: 1.0 To: Mike Smith CC: current@FreeBSD.ORG Subject: Re: HEADS UP: CAM cutover in two weeks. References: <199804150146.SAA01812@dingo.cdrom.com> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms2CC06A894E473627A32C1D72" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a cryptographically signed message in MIME format. --------------ms2CC06A894E473627A32C1D72 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hello, thank you for your effort. And yes I think it is preferable to add the new SCSI-Layer to CURRENT-Code. Just on question: What will be our preferred way to burn CD's? Up to now I am pretty happy with my HP4020i and the wrom-driver (thank you Joerg for making it even possible to use the drive as a CD-ROM reader) Now I see that the worm driver is not currently supported. Is it only due to the lack of an owner, or do we need that thing any more? Why? A little bit confused Micha Mike Smith wrote: > The following SCSI peripherals will become unsupported: > > Driver Adapter > ------ ------- > od Optical-disk device (*)(+) > uk Unknown SCSI device > worm Write-once SCSI device > > Drivers marked (*) are considered to be currently supported, and > desirable for 3.0. -- ___________________________________________________________________________ Michael Class E-Mail: michael_class@hp.com E-Business Solutions Center Phone: +49 7031 14-3707 EBSO-SERC Fax: +49 7031 14-4196 ___________________________________________________________________________ Hewlett-Packard GmbH, PO Box 1430, 71004 Boeblingen Sitz der Gesellschaft: Böblingen, Amtsgericht Böblingen HRB 4081 Geschäftsführer: Jörg Menno Harms (Vorsitzender), Klaus-Dieter Laidig, Rudi Speier, Fritz Schuller, Hans-Günter Hohmann ___________________________________________________________________________ --------------ms2CC06A894E473627A32C1D72 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIGuQYJKoZIhvcNAQcCoIIGqjCCBqYCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC BSgwggLTMIICPKADAgECAgIDBDANBgkqhkiG9w0BAQQFADBvMQswCQYDVQQGEwJVUzETMBEG A1UECBMKQ2FsaWZvcm5pYTEgMB4GA1UEChMXSGV3bGV0dC1QYWNrYXJkIENvbXBhbnkxKTAn BgNVBAMTIEhld2xldHQtUGFja2FyZCBJbnRlcm5hbCBDbGFzcyAyMB4XDTk3MTEyODA4MTYy NloXDTk4MTEyODA4MTYyNlowZzELMAkGA1UEBhMCREUxHTAbBgNVBAoTFEhld2xldHQtUGFj a2FyZCBHbWJIMTkwFAYDVQQDEw1NaWNoYWVsIENsYXNzMCEGCSqGSIb3DQEJARYUbWljaGFl bF9jbGFzc0BocC5jb20wXDANBgkqhkiG9w0BAQEFAANLADBIAkEAv8/L5XYx1uxPkAzHszC1 JY7xptyAHKxTWpZUXkxNmf0zFp+7dv6PiR1gUFrYbsucBT+5zL/qNIZx1ZpAG8pk+wIDAQAB o4HJMIHGMBEGCWCGSAGG+EIBAQQEAwIHgDCBkQYJYIZIAYb4QgENBIGDFoGAVGhpcyBjZXJ0 aWZpY2F0ZSB3YXMgaXNzdWVkIGJ5IHRoZSBIZXdsZXR0LVBhY2thcmQgQ29tcGFueQpJbnRl cm5hbCBDbGFzcyAyIENlcnRpZmljYXRpb24gQXV0aG9yaXR5LgpJdCBpcyBmb3IgSFAgYnVz aW5lc3Mgb25seS4wHQYKKwYBBAELBAFjAQQPFg1taWNoYWVsX2NsYXNzMA0GCSqGSIb3DQEB BAUAA4GBALBCl3GFlLyWa+VHofzJh4W7u2VvzltE+JZu5lkpUPmc/EIyEFXn2pHY6Rnjjzvl i+BYYEOGjh0HIv7Guyw61Bw6gJ4n9IEGgVlK6CnJB/9wdG+Kw2zyFti7gELLk4/aoa3r/5b8 UTpmFCcm6kcP3ZOA8oisB5GBk+y81Vf2FmzoMIICTTCCAbYCAQEwDQYJKoZIhvcNAQEEBQAw bzELMAkGA1UEBhMCVVMxEzARBgNVBAgTCkNhbGlmb3JuaWExIDAeBgNVBAoTF0hld2xldHQt UGFja2FyZCBDb21wYW55MSkwJwYDVQQDEyBIZXdsZXR0LVBhY2thcmQgSW50ZXJuYWwgQ2xh c3MgMjAeFw05NjExMDgxOTM0MDJaFw05OTExMDgxOTM0MDJaMG8xCzAJBgNVBAYTAlVTMRMw EQYDVQQIEwpDYWxpZm9ybmlhMSAwHgYDVQQKExdIZXdsZXR0LVBhY2thcmQgQ29tcGFueTEp MCcGA1UEAxMgSGV3bGV0dC1QYWNrYXJkIEludGVybmFsIENsYXNzIDIwgZ8wDQYJKoZIhvcN AQEBBQADgY0AMIGJAoGBALqbWcNtPJ2asOcT/h5TdYRLAirp5MbqYyku8CVR38jLPdV4LitJ dwmxYQ5HLBAFg3TtQ9B9sGTMviK5vmY2/qoL+PN+FnFUNOxBepuSYU3nKA8rg16hEBmPhzvP oNTs+GWKRsAtkHpsTST4hs0OoG1YfJu68lpHg9Nl1wfcSLarAgMBAAEwDQYJKoZIhvcNAQEE BQADgYEAPEb7WKlEujMuEE16PKojLEgE++8GVpyovHcta/7N+fg2iGbeGx3XSdjdR3s7CqWb AU1ipmTUuYiu30zc/EiTNW3HcWGWy9FbmdP1mPw6si6KDXup9/3smmGWo8NA89trW5SE6HSs b/wtsJpR6qNC9zJ3VBKr5q0Gbgs60HSJrZ8xggFZMIIBVQIBATB1MG8xCzAJBgNVBAYTAlVT MRMwEQYDVQQIEwpDYWxpZm9ybmlhMSAwHgYDVQQKExdIZXdsZXR0LVBhY2thcmQgQ29tcGFu eTEpMCcGA1UEAxMgSGV3bGV0dC1QYWNrYXJkIEludGVybmFsIENsYXNzIDICAgMEMAkGBSsO AwIaBQCgfTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw05ODA0 MTUwNjM0MDZaMB4GCSqGSIb3DQEJDzERMA8wDQYIKoZIhvcNAwICASgwIwYJKoZIhvcNAQkE MRYEFGzkvAamSVgsa/qWkOX2HJFOF/RkMA0GCSqGSIb3DQEBAQUABEAywkYzLwBhHADwTxfU 7XnPKmjlF82X+G2FdFy9xtKgxDwisUwU/LF+zYlfYddS3reMOxIb7ciPd+TV8kQlI6aC --------------ms2CC06A894E473627A32C1D72-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 14 23:38:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA11192 for freebsd-current-outgoing; Tue, 14 Apr 1998 23:38:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dt050n33.san.rr.com (@dt050n33.san.rr.com [204.210.31.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA11059 for ; Wed, 15 Apr 1998 06:38:00 GMT (envelope-from Studded@san.rr.com) Received: from san.rr.com (Studded@localhost [127.0.0.1]) by dt050n33.san.rr.com (8.8.8/8.8.8) with ESMTP id XAA29127; Tue, 14 Apr 1998 23:37:53 -0700 (PDT) (envelope-from Studded@san.rr.com) Message-ID: <353455C1.507A135E@san.rr.com> Date: Tue, 14 Apr 1998 23:37:53 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.6-STABLE i386) MIME-Version: 1.0 To: Vallo Kallaste CC: freebsd-current@FreeBSD.ORG Subject: Re: calcru: negative time, what is it ? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Vallo Kallaste wrote: > > Hello ! > > In the last two months or so I'm using current heavily and I keep getting > messages like below: > > calcru: negative time of -39217543 usec for pid 1519 (smbd) What type of processor do you have? If it's a '586, check /var/run/dmesg.boot and see if it was identified at the proper speed. If not, go to http://www.freebsd.org/search.html and search the archives for "studded and calcru" for info on how to solve this. Good luck, Doug -- *** Chief Operations Officer, DALnet IRC network *** *** Proud operator, designer and maintainer of the world's largest *** Internet Relay Chat server. 5,328 clients and still growing. *** Try spider.dal.net on ports 6662-4 (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 Tue Apr 14 23:40:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA12351 for freebsd-current-outgoing; Tue, 14 Apr 1998 23:40:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from solaris.matti.ee (root@solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA12221 for ; Wed, 15 Apr 1998 06:40:11 GMT (envelope-from vallo@matti.ee) Received: from localhost (vallo@localhost [127.0.0.1]) by solaris.matti.ee (8.8.8/8.8.8.s) with SMTP id JAA25306 for ; Wed, 15 Apr 1998 09:39:58 +0300 (EET DST) Date: Wed, 15 Apr 1998 09:39:57 +0300 (EET DST) From: Vallo Kallaste X-Sender: vallo@solaris To: freebsd-current@FreeBSD.ORG Subject: Re: calcru: negative time, what is it ? In-Reply-To: <2756.892621350@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 Wed, 15 Apr 1998, Poul-Henning Kamp wrote: > >calcru: negative time of -39217543 usec for pid 1519 (smbd) > > How current is this code ? *** CVsupped two days ago, time about 14:00:00 EEST. Kernel compiled right after make world. 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 Apr 14 23:58:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA19374 for freebsd-current-outgoing; Tue, 14 Apr 1998 23:58:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA19330 for ; Wed, 15 Apr 1998 06:58:38 GMT (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id AAA13210; Wed, 15 Apr 1998 00:57:56 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199804150657.AAA13210@panzer.plutotech.com> Subject: Re: HEADS UP: CAM cutover in two weeks. In-Reply-To: <353454DE.F6020EDC@hp.com> from Michael Class at "Apr 15, 98 08:34:06 am" To: michael_class@hp.com (Michael Class) Date: Wed, 15 Apr 1998 00:57:55 -0600 (MDT) Cc: mike@smith.net.au, 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 Michael Class wrote... > thank you for your effort. And yes I think it is preferable to add the > new SCSI-Layer to CURRENT-Code. > > Just on question: What will be our preferred way to burn CD's? Up to now > I am pretty happy with my HP4020i and the wrom-driver (thank you Joerg > for making it even possible to use the drive as a CD-ROM reader) Now I > see that the worm driver is not currently supported. Is it only due to > the lack of an owner, or do we need that thing any more? Why? It isn't supported due to (my) lack of time. I have a WORM drive, though (Plextor 4/12 Max), and I'm planning to write a WORM driver for CAM. It's likely that we can get cdrecord running with the CAM passthrough driver fairly quickly, though. This would give you the ability to burn CD's from userland. As for mounting WORM drives as CDROM drives, I can probably come up with the necessary code in the current CAM CDROM driver to make that happen. (basically, I'd need to make quirk entries for worm drives that don't respond to CD commands...if there are any such devices) 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 Wed Apr 15 00:03:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA21034 for freebsd-current-outgoing; Wed, 15 Apr 1998 00:03:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA20963 for ; Wed, 15 Apr 1998 07:02:53 GMT (envelope-from grog@lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id QAA00940; Wed, 15 Apr 1998 16:32:42 +0930 (CST) (envelope-from grog) Message-ID: <19980415163242.H350@freebie.lemis.com> Date: Wed, 15 Apr 1998 16:32:42 +0930 From: Greg Lehey To: Mike Smith , current@FreeBSD.ORG Subject: Re: HEADS UP: CAM cutover in two weeks. References: <199804150146.SAA01812@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199804150146.SAA01812@dingo.cdrom.com>; from Mike Smith on Tue, Apr 14, 1998 at 06:46:47PM -0700 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 14 April 1998 at 18:46:47 -0700, Mike Smith wrote: > > One of the major feature goals for 3.0 is the transition to the new > CAM-inspired SCSI subsystem. This transition requires a hard cutover > date. > > The proposed cutover date is the 28th of April. On or about this point > in time, the following steps will be taken: > > - A CVS tag will be applied to mark the last checkout date prior to > the cutover. > - The CAM code will be committed to the -current branch. > - GENERIC and LINT will be translated to suit. > - MAKEDEV will be updated. > - Non-CAM SCSI code and drivers will be *disabled*. Am I correct in taking this last item to mean that the old code will still be present? So if I build a -CURRENT kernel for my test machine (with aha1542[ab]s), using the old config file, it should still work in the old way? > If there are any significant issues (other than FUD) relating to the > proposed cutover, now is the time to raise them. When do we raise the FUD issues? Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 00:08:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA22491 for freebsd-current-outgoing; Wed, 15 Apr 1998 00:08:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA22400 for ; Wed, 15 Apr 1998 07:07:40 GMT (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id JAA02862; Wed, 15 Apr 1998 09:06:33 +0200 (CEST) To: Vallo Kallaste cc: freebsd-current@FreeBSD.ORG Subject: Re: calcru: negative time, what is it ? In-reply-to: Your message of "Wed, 15 Apr 1998 09:39:57 +0300." Date: Wed, 15 Apr 1998 09:06:33 +0200 Message-ID: <2860.892623993@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Vallo Kallaste w rites: > > >On Wed, 15 Apr 1998, Poul-Henning Kamp wrote: > >> >calcru: negative time of -39217543 usec for pid 1519 (smbd) >> >> How current is this code ? > >*** > >CVsupped two days ago, time about 14:00:00 EEST. Kernel compiled right >after make world. Hmm... SMP machine ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 00:10:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA23316 for freebsd-current-outgoing; Wed, 15 Apr 1998 00:10:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from solaris.matti.ee (root@solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA23182 for ; Wed, 15 Apr 1998 07:09:52 GMT (envelope-from vallo@matti.ee) Received: from localhost (vallo@localhost [127.0.0.1]) by solaris.matti.ee (8.8.8/8.8.8.s) with SMTP id KAA26760 for ; Wed, 15 Apr 1998 10:09:40 +0300 (EET DST) Date: Wed, 15 Apr 1998 10:09:39 +0300 (EET DST) From: Vallo Kallaste X-Sender: vallo@solaris To: freebsd-current@FreeBSD.ORG Subject: Re: calcru: negative time, what is it ? In-Reply-To: <353455C1.507A135E@san.rr.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, 14 Apr 1998, Studded wrote: > What type of processor do you have? If it's a '586, check > /var/run/dmesg.boot and see if it was identified at the proper speed. If > not, go to http://www.freebsd.org/search.html and search the archives > for "studded and calcru" for info on how to solve this. *** Processor type is ordinary Intel Pentium 166, not MMX. My machine is overclocked to 188 Mhz about a year or so. Basically its 2,5x75 Mhz and worked _very_ well under FreeBSD, Linux, NT, W'95. If overclocking caused this message, then I mean problem is solved. After a year of successful overclocking there are no need for going with ordinary 166 Mhz speed. BTW, I'm using 2.2-STABLE before switching to -current and my machine runs exactly same configuration without these messages. (except having 32MB memory ) This message is binded with -current, not my machine hardware configuration as I can say. Thanks Vallo Kallaste vallo@matti.ee dmesg.boot: Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #0: Tue Apr 14 12:00:18 EEST 1998 root@myhakas.matti.ee:/opt/src/sys/compile/BSDcurrent Timecounter "i8254" frequency 1193230 Hz cost 2524 ns Timecounter "TSC" frequency 187245150 Hz cost 173 ns CPU: Pentium (187.25-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 134217728 (131072K bytes) avail memory = 127942656 (124944K bytes) Probing for devices on PCI bus 0: chip0: rev 0x01 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 ide_pci0: rev 0x01 on pci0.7.1 chip2: rev 0x01 int d irq 9 on pci0.7.2 and so on... there are no SCSI devices at all. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 01:01:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA29793 for freebsd-current-outgoing; Wed, 15 Apr 1998 01:01:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA29788 for ; Wed, 15 Apr 1998 08:01:25 GMT (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id KAA02958; Wed, 15 Apr 1998 10:00:24 +0200 (CEST) To: Vallo Kallaste cc: freebsd-current@FreeBSD.ORG Subject: Re: calcru: negative time, what is it ? In-reply-to: Your message of "Wed, 15 Apr 1998 10:09:39 +0300." Date: Wed, 15 Apr 1998 10:00:24 +0200 Message-ID: <2956.892627224@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Vallo Kallaste w rites: >Processor type is ordinary Intel Pentium 166, not MMX. My machine is >overclocked to 188 Mhz about a year or so. Basically its 2,5x75 Mhz and >worked _very_ well under FreeBSD, Linux, NT, W'95. If overclocking caused >this message, then I mean problem is solved. After a year of successful >overclocking there are no need for going with ordinary 166 Mhz speed. And APM is disabled ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 01:12:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA01232 for freebsd-current-outgoing; Wed, 15 Apr 1998 01:12:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from solaris.matti.ee (root@solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA01227 for ; Wed, 15 Apr 1998 08:12:22 GMT (envelope-from vallo@matti.ee) Received: from localhost (vallo@localhost [127.0.0.1]) by solaris.matti.ee (8.8.8/8.8.8.s) with SMTP id LAA00246 for ; Wed, 15 Apr 1998 11:12:09 +0300 (EET DST) Date: Wed, 15 Apr 1998 11:12:07 +0300 (EET DST) From: Vallo Kallaste X-Sender: vallo@solaris To: freebsd-current@FreeBSD.ORG Subject: Re: calcru: negative time, what is it ? In-Reply-To: <2956.892627224@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 Wed, 15 Apr 1998, Poul-Henning Kamp wrote: > And APM is disabled ? *** Yes. My kernel config file: machine "i386" #cpu "I386_CPU" #cpu "I486_CPU" cpu "I586_CPU" #cpu "I686_CPU" ident BSDcurrent maxusers 12 options "CPU_FASTER_5X86_FPU" options CLK_CALIBRATION_LOOP options "CLK_USE_I8254_CALIBRATION" options CLK_USE_TSC_CALIBRATION options PANIC_REBOOT_WAIT_TIME=30 options SYSVSHM options SYSVSEM options SYSVMSG options "SHMMAXPGS=1024" #16MB shareable memory (GIMP) options "MD5" options PERFMON options COMPAT_LINUX #options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem #options KERNFS 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!] #options NFS_ROOT #NFS usable as root device options PROCFS #Process filesystem #options DEVFS #devices filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] #options SCSI_DELAY=15 #Be pessimistic about Joe SCSI device options BOUNCE_BUFFERS #include support for DMA bounce buffers #options "MAXMEM=(96*1024)" #options UCONSOLE #Allow users to grab the console #options FAILSAFE #Be conservative #options SOFTUPDATES #options "EXT2FS" #options USERCONFIG #boot -c editor #options VISUAL_USERCONFIG #visual boot -c editor config kernel root on wd0 controller isa0 #controller eisa0 controller pci0 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 #tape ft0 at fdc0 drive 2 #options "CMD640" # work around CMD640 chip deficiency controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0x80088008 vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 flags 0x80088008 vector wdintr disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 controller wdc2 at isa? port "IO_WD3" bio irq 10 flags 0x80088008 vector wdintr disk wd4 at wdc2 drive 0 disk wd5 at wdc2 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) controller pnp0 # Mingi sektsioon SCSI emulatsiooni tarvis, ZIP 100 controller scbus0 # Single bus device device sd0 at scbus? # SCSI disks # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr options MAXCONS=16 # number of virtual consoles options SC_HISTORY_SIZE=600 # number of history buffer lines device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" 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 lpt1 at isa? port? tty #device mse0 at isa? port 0x23c tty irq 5 vector mseintr 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 #device fxp0 #device tx0 #device vx0 #device ed0 at isa? port 0x280 net irq 10 iomem 0xd8000 vector edintr #device ie0 at isa? port 0x300 net irq 10 iomem 0xd0000 vector ieintr #device ep0 at isa? port 0x300 net irq 10 vector epintr #device ex0 at isa? port? net irq? vector exintr #device fe0 at isa? port 0x300 net irq ? vector feintr #device le0 at isa? port 0x300 net irq 5 iomem 0xd0000 vector le_intr #device lnc0 at isa? port 0x280 net irq 10 drq 0 vector lncintr #device ze0 at isa? port 0x300 net irq 10 iomem 0xd8000 vector zeintr #device zp0 at isa? port 0x300 net irq 10 iomem 0xd8000 vector zpintr pseudo-device loop pseudo-device ether pseudo-device sl 1 pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's pseudo-device vn #Vnode driver (turns a file into a device) pseudo-device snp 3 #Snoop device - to look at pty/vty/etc.. pseudo-device bpfilter 4 #Berkeley packet filter # Parallel-port bus toetus controller ppc0 at isa? port ? irq 7 vector ppcintr controller ppbus0 controller vpo0 at ppbus? #device ppi0 at ppbus? # 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 device pcm0 at isa ? port? tty irq? drq? vector pcmintr 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 Wed Apr 15 01:51:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA07293 for freebsd-current-outgoing; Wed, 15 Apr 1998 01:51:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.visint.co.uk (wakko.visint.co.uk [194.207.134.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA07286 for ; Wed, 15 Apr 1998 08:51:39 GMT (envelope-from steve@visint.co.uk) Received: from dylan (dylan.visint.co.uk [194.207.134.180]) by mail.visint.co.uk (8.8.8/8.8.5) with SMTP id JAA10591; Wed, 15 Apr 1998 09:51:26 +0100 (BST) Date: Wed, 15 Apr 1998 09:52:32 +0100 (BST) From: Stephen Roome X-Sender: steve@dylan Reply-To: Stephen Roome To: "Jordan K. Hubbard" cc: Ted Spradley , current@FreeBSD.ORG Subject: Re: ps segfaults since I overclocked. and worries. In-Reply-To: <8203.892564455@time.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, 14 Apr 1998, Jordan K. Hubbard wrote: > ... it was absolutely necessary that certain ground rules be laid down > and one of those rules is *no overclocking during debugging*. It's a > very simple rule and one which is non-negotiable. Should it be added to either the list charter or the handbook page on the lists then ? [ Perhaps just after the bit about no personal attacks in section 25.1.3, (handbook317.html on www.freebsd.org) because people can get quite vehement about it! =) ] Agreed, It's a really important rule, seemingly an unspoken (even if obvious) one though. Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 03:58:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA25648 for freebsd-current-outgoing; Wed, 15 Apr 1998 03:58:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA25599 for ; Wed, 15 Apr 1998 10:58:11 GMT (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id MAA03641; Wed, 15 Apr 1998 12:57:40 +0200 (MEST) (envelope-from sos) Message-Id: <199804151057.MAA03641@sos.freebsd.dk> Subject: Re: HEADS UP: CAM cutover in two weeks. In-Reply-To: <199804150657.AAA13210@panzer.plutotech.com> from "Kenneth D. Merry" at "Apr 15, 98 00:57:55 am" To: ken@plutotech.com (Kenneth D. Merry) Date: Wed, 15 Apr 1998 12:57:40 +0200 (MEST) Cc: michael_class@hp.com, mike@smith.net.au, current@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (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 In reply to Kenneth D. Merry who wrote: > > > > Just on question: What will be our preferred way to burn CD's? Up to now > > I am pretty happy with my HP4020i and the wrom-driver (thank you Joerg > > for making it even possible to use the drive as a CD-ROM reader) Now I > > see that the worm driver is not currently supported. Is it only due to > > the lack of an owner, or do we need that thing any more? Why? > > It isn't supported due to (my) lack of time. I have a WORM drive, > though (Plextor 4/12 Max), and I'm planning to write a WORM driver for CAM. > > It's likely that we can get cdrecord running with the CAM > passthrough driver fairly quickly, though. This would give you the > ability to burn CD's from userland. As for mounting WORM drives as CDROM > drives, I can probably come up with the necessary code in the current CAM > CDROM driver to make that happen. (basically, I'd need to make quirk > entries for worm drives that don't respond to CD commands...if there are > any such devices) Lets stick to the passthrough driver and use cdrecord or semilar. I'm currently working on getting an ATAPI CDRW drive working, and have more or less given up on using the worm-type interface, it just doesn't fit for modern (MMC compliant) drives. And yes I plan to get ATAPI support in under the SCSI system whatever it might be. I think it might be a bit premature, we will alienate many (if not most) of the -current hackers by removing 80% of our SCSI drivers :( -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 04:55:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA06991 for freebsd-current-outgoing; Wed, 15 Apr 1998 04:55:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from aldan.ziplink.net (mi@kot.ne.mediaone.net [24.128.29.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA06981 for ; Wed, 15 Apr 1998 11:55:24 GMT (envelope-from mi@rtfm.ziplink.net) Received: from rtfm.ziplink.net (rtfm [199.232.255.52]) by aldan.ziplink.net (8.8.8/8.8.7) with ESMTP id LAA01256 for ; Wed, 15 Apr 1998 11:55:22 GMT (envelope-from mi@rtfm.ziplink.net) Received: (from mi@localhost) by rtfm.ziplink.net (8.8.8/8.8.5) id HAA03370 for freebsd-current@freebsd.org; Wed, 15 Apr 1998 07:55:21 -0400 (EDT) From: Mikhail Teterin Message-Id: <199804151155.HAA03370@rtfm.ziplink.net> Subject: A CAM of worms In-Reply-To: <199804150604.XAA00610@antipodes.cdrom.com> from "Mike Smith" at "Apr 14, 98 11:04:57 pm" To: freebsd-current@FreeBSD.ORG Date: Wed, 15 Apr 1998 07:55:21 -0400 (EDT) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA14361 for freebsd-current-outgoing; Wed, 15 Apr 1998 05:28:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from koto.partitur.se (koto.partitur.se [193.219.246.209]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14336 for ; Wed, 15 Apr 1998 12:28:22 GMT (envelope-from kudo@partitur.se) Received: from koto.partitur.se (koto.partitur.se [193.219.246.209]) by koto.partitur.se (8.8.7/8.8.7) with SMTP id OAA04643 for ; Wed, 15 Apr 1998 14:29:57 +0200 (CEST) (envelope-from kudo@partitur.se) Date: Wed, 15 Apr 1998 14:29:57 +0200 (CEST) From: Patrik Kudo To: FreeBSD Current Subject: Intel DK440LX Installation Message-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'm about to install FreeBSD on my Intel DK440LX based computer (only one CPU, one SCSI HD and one SCSI CDROM-drive). I figured out that I need to use freebsd-current to be able to run with this configuration, but I can't find any documentation on how to do this. Is there any good place to start looking for info (like where to find a bootdisk with the correct drivers, do I need to include SMP support when only running one CPU, etc)? Or even, if someone out there with experience installing freebsd on my kind of system have the time (yeah, I know I'm beeing optimistic =) to help me out more directly, I'd be eternaly greatful. Thanks in advance, Patrik Kudo kudo@partitur.se To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 05:39:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA15826 for freebsd-current-outgoing; Wed, 15 Apr 1998 05:39:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oskar.nanoteq.co.za (oskar.nanoteq.co.za [196.37.91.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15793 for ; Wed, 15 Apr 1998 12:39:27 GMT (envelope-from rbezuide@oskar.nanoteq.co.za) Received: (from rbezuide@localhost) by oskar.nanoteq.co.za (8.8.8/8.8.5) id OAA13867; Wed, 15 Apr 1998 14:37:57 +0200 (SAT) From: Reinier Bezuidenhout Message-Id: <199804151237.OAA13867@oskar.nanoteq.co.za> Subject: Re: A CAM of worms In-Reply-To: <199804151155.HAA03370@rtfm.ziplink.net> from Mikhail Teterin at "Apr 15, 98 07:55:21 am" To: mi@aldan.algebra.com (Mikhail Teterin) Date: Wed, 15 Apr 1998 14:36:42 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ... > Mike Smith once stated: > > =If there is no CAM support for the 1542 at the merge date, you can > =expect it to follow as one of the highest-priority items therafter. > > What about worms? No CD-writing under 3.0? Yes .. is this true .. no CD-writing .. I don't know much about CAM ... so if it is included somewhere .. sorry then :) but FreeBSD is one of/the most stable system to burn a CD on ... it would be a great loss. Reinier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 06:22:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA22117 for freebsd-current-outgoing; Wed, 15 Apr 1998 06:22:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22111 for ; Wed, 15 Apr 1998 13:22:27 GMT (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.7/8.8.7) id PAA01599 for freebsd-current@freefall.cdrom.com; Wed, 15 Apr 1998 15:25:47 +0200 (MEST) (envelope-from kuku) Date: Wed, 15 Apr 1998 15:25:47 +0200 (MEST) From: Christoph Kukulies Message-Id: <199804151325.PAA01599@gilberto.physik.RWTH-Aachen.DE> To: freebsd-current@freefall.FreeBSD.org Subject: current after a while - obsolete options Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Today I rebuilt a -current system (Apr 15) and make world worked flawlessly. Only a few kernel options seem to be obsolete and I'm asking whether they've been replaced by something else or have been dropped by the one or other reason: options "GUSMAX" pseudo-device log pseudo-device pcaudio -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 06:29:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23865 for freebsd-current-outgoing; Wed, 15 Apr 1998 06:29:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mexcom.net (ver2-117.uninet.net.mx [200.38.135.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA23533 for ; Wed, 15 Apr 1998 13:27:49 GMT (envelope-from eculp@ver1.telmex.net.mx) Received: from sunix (telmex@sunix.mexcom.net [206.103.64.3]) by ns.mexcom.net (8.8.8/8.8.7) with SMTP id IAA22649; Wed, 15 Apr 1998 08:24:35 -0500 (CDT) Message-ID: <3534B701.5F09D019@ver1.telmex.net.mx> Date: Wed, 15 Apr 1998 08:32:49 -0500 From: Edwin Culp Organization: Mexico Communicates, S.C. X-Mailer: Mozilla 3.01Gold (X11; I; Linux 2.0.14 i586) MIME-Version: 1.0 To: Patrik Kudo CC: FreeBSD Current Subject: Re: Intel DK440LX Installation References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Patrik Kudo wrote: > > Hi > > I'm about to install FreeBSD on my Intel DK440LX based computer (only one > CPU, one SCSI HD and one SCSI CDROM-drive). I figured out that I need to > use freebsd-current to be able to run with this configuration, but I can't > find any documentation on how to do this. Is there any good place to start > looking for info (like where to find a bootdisk with the correct drivers, > do I need to include SMP support when only running one CPU, etc)? Or even, > if someone out there with experience installing freebsd on my kind of > system have the time (yeah, I know I'm beeing optimistic =) to help me out > more directly, I'd be eternaly greatful. > > Thanks in advance, > Patrik Kudo > kudo@partitur.se > How about http://www.freebsd.org and read the documentation. I think you'll find it reasonably complete. You can even pick up your boot floppy there:-) provecho ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 06:34:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA25456 for freebsd-current-outgoing; Wed, 15 Apr 1998 06:34:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA25382 for ; Wed, 15 Apr 1998 13:34:42 GMT (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id PAA02140; Wed, 15 Apr 1998 15:36:35 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Wed, 15 Apr 1998 15:36:35 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Patrik Kudo cc: FreeBSD Current Subject: Re: Intel DK440LX Installation 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, 15 Apr 1998, Patrik Kudo wrote: > Hi > > I'm about to install FreeBSD on my Intel DK440LX based computer (only one > CPU, one SCSI HD and one SCSI CDROM-drive). I figured out that I need to > use freebsd-current to be able to run with this configuration, but I can't > find any documentation on how to do this. Is there any good place to start > looking for info (like where to find a bootdisk with the correct drivers, I just downloaded the new CAM snapshot to my Dakota-based machine. If you can wait two-three days, I'll prepare a new set of boot/fixit floppies. The old ones (based on Jan' snapshot) are available in: ftp://ftp.freebsd.org/pub/FreeBSD/incoming/cam-boot.tgz Please read the README before you start installation! > do I need to include SMP support when only running one CPU, etc)? Or even, No. > if someone out there with experience installing freebsd on my kind of > system have the time (yeah, I know I'm beeing optimistic =) to help me out I can help you, if you're ready to read some README's/ man pages/ config files... :-) Andrzej Bialecki ---------------------+--------------------------------------------------------- abial@warman.org.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. ---------------------+--------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 07:00:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA01325 for freebsd-current-outgoing; Wed, 15 Apr 1998 07:00:13 -0700 (PDT) (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 OAA01319 for ; Wed, 15 Apr 1998 14:00:09 GMT (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id KAA17718; Wed, 15 Apr 1998 10:01:59 -0400 (EDT) Date: Wed, 15 Apr 1998 10:01:59 -0400 (EDT) From: Daniel Eischen Message-Id: <199804151401.KAA17718@pcnet1.pcnet.com> To: freebsd-current@FreeBSD.ORG, mi@aldan.algebra.com, rbezuide@oskar.nanoteq.co.za Subject: Re: A CAM of worms Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > What about worms? No CD-writing under 3.0? > > Yes .. is this true .. no CD-writing .. I don't know much about > CAM ... so if it is included somewhere .. sorry then :) but > FreeBSD is one of/the most stable system to burn a CD on ... > it would be a great loss. It should be simple to change the user-land CD burning applications like cdrecord. As already mentioned, CAM already provides a SCSI pass-thru mechanism. Look at the CAMified xmcd for an example. The only thing that will initially be missing will be the worm control driver/commands. IMHO, it is important to bring CAM in now and get it ready for 3.0. Dan Eischen deischen@iworks.InterWorks.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 07:20:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06869 for freebsd-current-outgoing; Wed, 15 Apr 1998 07:20:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA06834 for ; Wed, 15 Apr 1998 14:20:03 GMT (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id HAA16310; Wed, 15 Apr 1998 07:20:11 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Edwin Culp cc: Patrik Kudo , FreeBSD Current Subject: Re: Intel DK440LX Installation In-reply-to: Your message of "Wed, 15 Apr 1998 08:32:49 CDT." <3534B701.5F09D019@ver1.telmex.net.mx> Date: Wed, 15 Apr 1998 07:20:11 -0700 Message-ID: <16307.892650011@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > How about http://www.freebsd.org and read the documentation. I think Won't help him - this motherboard has a specialized SCSI controller that is not yet supported in -current. That's part of what the CAM debate is all about. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 07:29:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA09093 for freebsd-current-outgoing; Wed, 15 Apr 1998 07:29:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from koto.partitur.se (koto.partitur.se [193.219.246.209]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09086 for ; Wed, 15 Apr 1998 14:29:54 GMT (envelope-from kudo@partitur.se) Received: from koto.partitur.se (koto.partitur.se [193.219.246.209]) by koto.partitur.se (8.8.7/8.8.7) with SMTP id QAA04825; Wed, 15 Apr 1998 16:31:10 +0200 (CEST) (envelope-from kudo@partitur.se) Date: Wed, 15 Apr 1998 16:31:10 +0200 (CEST) From: Patrik Kudo To: "Jordan K. Hubbard" cc: Edwin Culp , FreeBSD Current Subject: Re: Intel DK440LX Installation In-Reply-To: <16307.892650011@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 15 Apr 1998, Jordan K. Hubbard wrote: > > How about http://www.freebsd.org and read the documentation. I think > > Won't help him - this motherboard has a specialized SCSI controller > that is not yet supported in -current. That's part of what the CAM > debate is all about. I'm trying out with the cam-boot disks now. Thanks for your help, folks regards, Patrik Kudo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 08:43:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA22724 for freebsd-current-outgoing; Wed, 15 Apr 1998 08:43:06 -0700 (PDT) (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 PAA22704 for ; Wed, 15 Apr 1998 15:43:02 GMT (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id IAA00424; Wed, 15 Apr 1998 08:39:37 -0700 (PDT) Message-Id: <199804151539.IAA00424@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Mikhail Teterin cc: freebsd-current@FreeBSD.ORG Subject: Re: A CAM of worms In-reply-to: Your message of "Wed, 15 Apr 1998 07:55:21 EDT." <199804151155.HAA03370@rtfm.ziplink.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 15 Apr 1998 08:39:36 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith once stated: > > =If there is no CAM support for the 1542 at the merge date, you can > =expect it to follow as one of the highest-priority items therafter. > > What about worms? No CD-writing under 3.0? Is there anything that you need that cdrecord doesn't do? -- \\ 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 Apr 15 08:59:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25772 for freebsd-current-outgoing; Wed, 15 Apr 1998 08:59:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA25766 for ; Wed, 15 Apr 1998 15:59:54 GMT (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id RAA04181; Wed, 15 Apr 1998 17:58:47 +0200 (CEST) To: Vallo Kallaste cc: freebsd-current@FreeBSD.ORG Subject: Re: calcru: negative time, what is it ? In-reply-to: Your message of "Wed, 15 Apr 1998 11:12:07 +0300." Date: Wed, 15 Apr 1998 17:58:47 +0200 Message-ID: <4179.892655927@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Vallo Kallaste writes: > > >On Wed, 15 Apr 1998, Poul-Henning Kamp wrote: > >> And APM is disabled ? > >*** > >Yes. Sorry, I meant "disabled in the bios ?" -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 11:06:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA00872 for freebsd-current-outgoing; Wed, 15 Apr 1998 11:06:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.westbend.net (ns1.westbend.net [207.217.224.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA00852 for ; Wed, 15 Apr 1998 18:05:54 GMT (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [207.217.224.195]) by mail.westbend.net (8.8.8/8.8.8) with SMTP id NAA14557; Wed, 15 Apr 1998 13:05:51 -0500 (CDT) (envelope-from hetzels@westbend.net) Message-ID: <05cb01bd6899$6e0135e0$c3e0d9cf@admin.westbend.net> From: "Scot W. Hetzel" To: "Michael Class" Cc: Subject: Digitally Signed Messages (Re: HEADS UP: CAM cutover in two weeks.) Date: Wed, 15 Apr 1998 13:08:01 -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.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Could you please not send Digitally Signed Messages to the list. For those of us that have mail programs that support it, it is kind of annoying to have to go through 2 displays to just to read the message. Thanks, Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 11:25:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA04362 for freebsd-current-outgoing; Wed, 15 Apr 1998 11:25:27 -0700 (PDT) (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 SAA04315 for ; Wed, 15 Apr 1998 18:25:17 GMT (envelope-from ab@paert.tse-online.de) Received: (qmail 882 invoked by uid 1000); 15 Apr 1998 18:27:41 -0000 Message-ID: <19980415202740.43100@paert.tse-online.de> Date: Wed, 15 Apr 1998 20:27:40 +0200 From: Andreas Braukmann To: freebsd-current@FreeBSD.ORG Subject: 'fatal trap 12' on boot (smp and up) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 Organization: TSE TeleService GmbH Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I was running (quit happily) -current from late November '97 with an smp-enabled kernel. I updated my sources to 98/04/06 and waited a few days for 'alarm' and 'heads up'-messages on -current. Yesterday I made the world, installed the world and made my kernel based on my old kernel-configuration (just deleted the outdated 'log' pseudo-device). The new kernel traps on boot immediatly (after it's loaded). This happens to both - the smp-enabled and the normal uni-proc. kernel. (same config, just without smp). The hardware: * Gigabyte 686DX Dual PPro 200 * Award BIOS * 128 MB Ram The trap: (from the uni-proc. kernel, cited from hand-written notes) Fatal trap 12: page fault while in vm86 mode fault virtual address: 0x26e0 fault code: user read, page not present ip = 0x24a:0x240 sp = 0x0:0xff8 fp = 0x0:0x0 cs = base 0xf0000008, limit 0xd14c8, type 0xf DPL 0, pres 1, def 32 0, gran 0 proc eflags = trace trap, int enabled, resume, vm86, IOPL=0 cur proc = idle int mask = net tty bio cam I even made a 'config -g' up-kernel, but a 'trace'-command in the kernel-debugger didn't spit out anything that seemed very useful to me (I'm a non-kernel hacker ...), just something about 'xxxx DYNAMIC xxxx'. The trap appears at exactly the same addresse for the smp and the up-case. Any hints? Thanks, 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 Wed Apr 15 12:12:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13959 for freebsd-current-outgoing; Wed, 15 Apr 1998 12:12:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sumatra.americantv.com (sumatra.americantv.com [207.170.17.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA13950 for ; Wed, 15 Apr 1998 19:12:30 GMT (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id OAA24163; Wed, 15 Apr 1998 14:12:27 -0500 (CDT) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id OAA22949; Wed, 15 Apr 1998 14:11:55 -0500 Message-ID: <19980415141155.44599@right.PCS> Date: Wed, 15 Apr 1998 14:11:55 -0500 From: Jonathan Lemon To: Andreas Braukmann Cc: freebsd-current@FreeBSD.ORG Subject: Re: 'fatal trap 12' on boot (smp and up) References: <19980415202740.43100@paert.tse-online.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: <19980415202740.43100@paert.tse-online.de>; from Andreas Braukmann on Apr 04, 1998 at 08:27:40PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Apr 04, 1998 at 08:27:40PM +0200, Andreas Braukmann wrote: > The hardware: > * Gigabyte 686DX Dual PPro 200 > * Award BIOS > * 128 MB Ram > > The trap: (from the uni-proc. kernel, cited from hand-written notes) > Fatal trap 12: page fault while in vm86 mode > fault virtual address: 0x26e0 > fault code: user read, page not present > ip = 0x24a:0x240 > sp = 0x0:0xff8 > fp = 0x0:0x0 > cs = base 0xf0000008, limit 0xd14c8, type 0xf > DPL 0, pres 1, def 32 0, gran 0 > proc eflags = trace trap, int enabled, resume, vm86, IOPL=0 > cur proc = idle > int mask = net tty bio cam This is the VM86 memory sizing code on bootup; it is trying to coax the BIOS to tell it how much memory is in the machine. The BIOS routines are supposed to be at 0xA0000, for some reason, your machine is trying to execute code at 0x26e0. This fails, since I haven't mapped that particular page page into the address space. Do you have `BIOS shadowing' set in your BIOS? Try turning if off, if so. For a quick workaround, you can just take out "options VM86" from the kernel, but I'd really like to try to get this fixed. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 12:17:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14784 for freebsd-current-outgoing; Wed, 15 Apr 1998 12:17:49 -0700 (PDT) (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 TAA14778 for ; Wed, 15 Apr 1998 19:17:47 GMT (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id MAA03489; Wed, 15 Apr 1998 12:07:14 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd003463; Wed Apr 15 19:07:08 1998 Message-ID: <35350420.167EB0E7@whistle.com> Date: Wed, 15 Apr 1998 12:01:52 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: Mike Smith CC: Mikhail Teterin , freebsd-current@FreeBSD.ORG Subject: Re: A CAM of worms References: <199804151539.IAA00424@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: > > > Mike Smith once stated: > > > > =If there is no CAM support for the 1542 at the merge date, you can > > =expect it to follow as one of the highest-priority items therafter. > > > > What about worms? No CD-writing under 3.0? > > Is there anything that you need that cdrecord doesn't do? > > -- > \\ 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 The fact that CAM and the old SCSI can't coexist in the tree is purely a design decision by Justin. I managed to almost get it working in about 6 hours using mostly automatic tools (patch -D etc.) in October last year. personally I think he should spend the 2 or 3 days it would take to be able to do this. or at least make his own branch for a while.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 12:52:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA23244 for freebsd-current-outgoing; Wed, 15 Apr 1998 12:52:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ziplink.net (relay-0.ziplink.net [206.15.168.49]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA23189 for ; Wed, 15 Apr 1998 19:52:03 GMT (envelope-from mi@xxx.video-collage.com) Received: from xxx.video-collage.com (xxx.video-collage.com [199.232.254.68]) by ziplink.net (8.8.7/8.8.7) with ESMTP id PAA02069 for ; Wed, 15 Apr 1998 15:51:56 -0400 (EDT) Received: (from mi@localhost) by cobalt (950413.SGI.8.6.12/950213.SGI.AUTOCF) id NAA01529 for freebsd-current@freebsd.org; Wed, 15 Apr 1998 13:52:32 -0400 From: mi@video-collage.com (Mikhail Teterin) Message-Id: <199804151752.NAA01529@cobalt> Subject: Re: A CAM of worms In-Reply-To: <199804151539.IAA00424@dingo.cdrom.com> from Mike Smith at "Apr 15, 98 08:39:36 am" To: freebsd-current@FreeBSD.ORG Date: Wed, 15 Apr 1998 13:52:32 -0400 (EDT) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" =If there is no CAM support for the 1542 at the merge date, you can => =expect it to follow as one of the highest-priority items therafter. => => What about worms? No CD-writing under 3.0? = =Is there anything that you need that cdrecord doesn't do? Don't I need worm-driver to _read_ the cd in the worm-device? -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 13:06:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26765 for freebsd-current-outgoing; Wed, 15 Apr 1998 13:06:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sasami.jurai.net (winter@sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA26654; Wed, 15 Apr 1998 20:06:28 GMT (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id QAA01507; Wed, 15 Apr 1998 16:06:25 -0400 (EDT) Date: Wed, 15 Apr 1998 16:06:25 -0400 (EDT) From: "Matthew N. Dodd" To: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: temporary FreeBSD token-ring list. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG freebsd-tokenring@jurai.net is up and running as a temporary mailing list for the ongoing discussion of the efforts to add Token Ring and 802.2 LLC support to FreeBSD As there are a number of non-token ring issues that we will have to solve before working on any token-ring specific issues, I invite everyone who has an interest in making the network subsystem a bit less ethernet centric in the places that it is, and those who have interest in supporting Novell 802.3 IPX and NetBEUI. The 802.2 LLC is common to all of these. Thanks! /* Matthew N. Dodd | A memory retaining a love you had for life winter@jurai.net | As cruel as it seems nothing ever seems to http://www.jurai.net/~winter | go right - FLA M 3.1:53 */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 13:17:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA29729 for freebsd-current-outgoing; Wed, 15 Apr 1998 13:17:09 -0700 (PDT) (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 UAA29322 for ; Wed, 15 Apr 1998 20:15:49 GMT (envelope-from ab@paert.tse-online.de) Received: (qmail 401 invoked by uid 1000); 15 Apr 1998 20:18:29 -0000 Message-ID: <19980415221829.03759@paert.tse-online.de> Date: Wed, 15 Apr 1998 22:18:29 +0200 From: Andreas Braukmann To: freebsd-current@FreeBSD.ORG Subject: Re: 'fatal trap 12' on boot (smp and up) References: <19980415202740.43100@paert.tse-online.de> <19980415141155.44599@right.PCS> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <19980415141155.44599@right.PCS>; from Jonathan Lemon on Wed, Apr 15, 1998 at 02:11:55PM -0500 Organization: TSE TeleService GmbH Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, On Wed, Apr 15, 1998 at 02:11:55PM -0500, Jonathan Lemon wrote: > On Apr 04, 1998 at 08:27:40PM +0200, Andreas Braukmann wrote: > > The hardware: > > * Gigabyte 686DX Dual PPro 200 > > * Award BIOS > > * 128 MB Ram > > > > The trap: (from the uni-proc. kernel, cited from hand-written notes) > > Fatal trap 12: page fault while in vm86 mode > > fault virtual address: 0x26e0 > > fault code: user read, page not present > > ip = 0x24a:0x240 > > sp = 0x0:0xff8 > > fp = 0x0:0x0 > > cs = base 0xf0000008, limit 0xd14c8, type 0xf > > DPL 0, pres 1, def 32 0, gran 0 > > proc eflags = trace trap, int enabled, resume, vm86, IOPL=0 > > cur proc = idle > > int mask = net tty bio cam > > This is the VM86 memory sizing code on bootup; it is trying to coax the > BIOS to tell it how much memory is in the machine. The BIOS routines > are supposed to be at 0xA0000, for some reason, your machine is trying > to execute code at 0x26e0. This fails, since I haven't mapped that > particular page page into the address space. hmmm, anybody out here with the same mainboard? Which BIOS-revision does it have? > Do you have `BIOS shadowing' set in your BIOS? Try turning if off, if so. no. > For a quick workaround, you can just take out "options VM86" from > the kernel, but I'd really like to try to get this fixed. It works. My smp-kernel is up and running without 'vm86'. Tomorrow I will do some more tests. Thanks for the help. Regards, 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 Wed Apr 15 13:48:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09405 for freebsd-current-outgoing; Wed, 15 Apr 1998 13:48:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09350; Wed, 15 Apr 1998 13:48:39 -0700 (PDT) (envelope-from jmb) From: "Jonathan M. Bresler" Message-Id: <199804152048.NAA09350@hub.freebsd.org> Subject: Re: temporary FreeBSD token-ring list. In-Reply-To: from "Matthew N. Dodd" at "Apr 15, 98 04:06:25 pm" To: winter@jurai.net (Matthew N. Dodd) Date: Wed, 15 Apr 1998 13:48:38 -0700 (PDT) Cc: hackers@FreeBSD.ORG, 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 FreeBSD-tokenring and FreeBSD-advocacy are ready for use. tokenring@freebsd.org is a short cut to FreeBSD-tokenring@freebsd.org advocacy@freebsd.org is a short cut to FreeBSD-advocacy@freebsd.org enjoy! jmb Matthew N. Dodd wrote: > > freebsd-tokenring@jurai.net is up and running as a temporary mailing list > for the ongoing discussion of the efforts to add Token Ring and 802.2 LLC > support to FreeBSD > > As there are a number of non-token ring issues that we will have to solve > before working on any token-ring specific issues, I invite everyone who > has an interest in making the network subsystem a bit less ethernet > centric in the places that it is, and those who have interest in > supporting Novell 802.3 IPX and NetBEUI. The 802.2 LLC is common to all > of these. > > Thanks! > > /* > Matthew N. Dodd | A memory retaining a love you had for life > winter@jurai.net | As cruel as it seems nothing ever seems to > http://www.jurai.net/~winter | go right - FLA M 3.1:53 > */ > > > 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 Apr 15 13:49:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09613 for freebsd-current-outgoing; Wed, 15 Apr 1998 13:49:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sasami.jurai.net (winter@sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA09595; Wed, 15 Apr 1998 20:49:53 GMT (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id QAA02295; Wed, 15 Apr 1998 16:49:53 -0400 (EDT) Date: Wed, 15 Apr 1998 16:49:53 -0400 (EDT) From: "Matthew N. Dodd" To: "Jonathan M. Bresler" cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: temporary FreeBSD token-ring list. In-Reply-To: <199804152048.NAA09350@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 Wed, 15 Apr 1998, Jonathan M. Bresler wrote: > FreeBSD-tokenring and > FreeBSD-advocacy > > are ready for use. > > tokenring@freebsd.org is a short cut to FreeBSD-tokenring@freebsd.org > advocacy@freebsd.org is a short cut to FreeBSD-advocacy@freebsd.org > whew! freebsd-tokenring@jurai.net was -really- temporary. :) Thanks! > Matthew N. Dodd wrote: > > > > freebsd-tokenring@jurai.net is up and running as a temporary mailing list > > for the ongoing discussion of the efforts to add Token Ring and 802.2 LLC > > support to FreeBSD > > > > As there are a number of non-token ring issues that we will have to solve > > before working on any token-ring specific issues, I invite everyone who > > has an interest in making the network subsystem a bit less ethernet > > centric in the places that it is, and those who have interest in > > supporting Novell 802.3 IPX and NetBEUI. The 802.2 LLC is common to all > > of these. > > > > Thanks! > > > > /* > > Matthew N. Dodd | A memory retaining a love you had for life > > winter@jurai.net | As cruel as it seems nothing ever seems to > > http://www.jurai.net/~winter | go right - FLA M 3.1:53 > > */ > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > /* Matthew N. Dodd | A memory retaining a love you had for life winter@jurai.net | As cruel as it seems nothing ever seems to http://www.jurai.net/~winter | go right - FLA M 3.1:53 */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 13:51:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10139 for freebsd-current-outgoing; Wed, 15 Apr 1998 13:51:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10044; Wed, 15 Apr 1998 13:51:46 -0700 (PDT) (envelope-from jmb) From: "Jonathan M. Bresler" Message-Id: <199804152051.NAA10044@hub.freebsd.org> Subject: Re: temporary FreeBSD token-ring list. In-Reply-To: from "Matthew N. Dodd" at "Apr 15, 98 04:49:53 pm" To: winter@jurai.net (Matthew N. Dodd) Date: Wed, 15 Apr 1998 13:51:44 -0700 (PDT) Cc: jmb@FreeBSD.ORG, hackers@FreeBSD.ORG, 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 Matthew N. Dodd wrote: > > whew! freebsd-tokenring@jurai.net was -really- temporary. :) would have announce earlier but i had to deal with a "cannot fork" problem here, before announcing the two new lists. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 14:48:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23378 for freebsd-current-outgoing; Wed, 15 Apr 1998 14:48:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from top.worldcontrol.com (surf52.cruzers.com [205.215.232.52]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA23332 for ; Wed, 15 Apr 1998 21:48:29 GMT (envelope-from brian@litzinger.com) From: brian@litzinger.com Received: (qmail 14679 invoked by uid 100); 15 Apr 1998 21:49:24 -0000 Message-ID: <19980415144921.A14661@top.worldcontrol.com> Date: Wed, 15 Apr 1998 14:49:21 -0700 To: freebsd-current@FreeBSD.ORG Cc: freebsd-questions@FreeBSD.ORG Subject: attr_get() does not exist Mail-Followup-To: freebsd-current@freebsd.org, freebsd-questions@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The version of ncurses supplied with FreeBSD does not include the function attr_get(). At least as far as I can find. ncurses 4.1 and SLang's curses emulator both include it. The authors of mutt, my favorite mailer, may soon include the use of this function in mutt. (mutt 0.91, the latest release does not use it) I currently substitute ((stdscr)->_attrs) in place of attr_get(). Apparently, just about every other OS has the function. Have I missed something? If it really is missing mutt would probably have to add a facility to config to check for attr_get and if it didn't exist #define NO_ATTR_GET in config.h and modify the code appropriately. I suspect they aren't going to want to do this. Another solution is to simply build mutt with the SLang package. -- Brian Litzinger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 16:23:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14857 for freebsd-current-outgoing; Wed, 15 Apr 1998 16:23:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lsd.relcom.eu.net (lsd.relcom.eu.net [193.125.27.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA14753; Wed, 15 Apr 1998 23:23:22 GMT (envelope-from ache@lsd.relcom.eu.net) Received: (from ache@localhost) by lsd.relcom.eu.net (8.8.8/8.8.8) id DAA04845; Thu, 16 Apr 1998 03:23:10 +0400 (MSD) (envelope-from ache) Message-ID: <19980416032309.15926@nagual.pp.ru> Date: Thu, 16 Apr 1998 03:23:09 +0400 From: =?koi8-r?B?4c7E0sXKIP7F0s7P1w==?= To: freebsd-current@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Cc: peter@FreeBSD.ORG Subject: Re: attr_get() does not exist Mail-Followup-To: freebsd-current@freebsd.org, freebsd-questions@freebsd.org, peter@freebsd.org References: <19980415144921.A14661@top.worldcontrol.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980415144921.A14661@top.worldcontrol.com>; from brian@litzinger.com on Wed, Apr 15, 1998 at 02:49:21PM -0700 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 15, 1998 at 02:49:21PM -0700, brian@litzinger.com wrote: > The version of ncurses supplied with FreeBSD does not include > the function attr_get(). At least as far as I can find. I just add attr_get(). Really ncurses 4.1 should be imported as contrib material instead, but this task is not mine, as I remember Peter takes it, ask him about delays reason. -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ 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 Wed Apr 15 17:14:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01165 for freebsd-current-outgoing; Wed, 15 Apr 1998 17:14:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sasami.jurai.net (root@sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA01111; Wed, 15 Apr 1998 17:13:58 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id TAA04710; Wed, 15 Apr 1998 19:45:57 -0400 (EDT) Date: Wed, 15 Apr 1998 19:45:57 -0400 (EDT) From: "Matthew N. Dodd" To: freebsd-tokenring@FreeBSD.ORG, current@FreeBSD.ORG Subject: TODO: sys/netccitt/llc* Message-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, we've got nearly all the 802.2 LLC bits (in a decayed form) in sys/netccitt/llc*. If we could pull these out of the attic I'll see about merging the fixes from NetBSD. Any takers? /* Matthew N. Dodd | A memory retaining a love you had for life winter@jurai.net | As cruel as it seems nothing ever seems to http://www.jurai.net/~winter | go right - FLA M 3.1:53 */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 17:28:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA07150 for freebsd-current-outgoing; Wed, 15 Apr 1998 17:28:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from top.worldcontrol.com (surf52.cruzers.com [205.215.232.52]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA07034 for ; Wed, 15 Apr 1998 17:28:07 -0700 (PDT) (envelope-from brian@litzinger.com) From: brian@litzinger.com Received: (qmail 14969 invoked by uid 100); 16 Apr 1998 00:29:03 -0000 Message-ID: <19980415172858.A14927@top.worldcontrol.com> Date: Wed, 15 Apr 1998 17:28:58 -0700 To: "Scot W. Hetzel" , Michael Class Cc: current@FreeBSD.ORG Subject: Re: Digitally Signed Messages (Re: HEADS UP: CAM cutover in two weeks.) References: <05cb01bd6899$6e0135e0$c3e0d9cf@admin.westbend.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91i In-Reply-To: <05cb01bd6899$6e0135e0$c3e0d9cf@admin.westbend.net>; from Scot W. Hetzel on Wed, Apr 15, 1998 at 01:08:01PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On %M 0, "Scot W. Hetzel" wrote: > Could you please not send Digitally Signed Messages to the list. For those > of us that have mail programs that support it, it is kind of annoying to > have to go through 2 displays to just to read the message. I have a mail program that supports Digitally Signed Messages and I don't have to go through 2 displays just to read the message. -- Brian Litzinger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 17:32:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08713 for freebsd-current-outgoing; Wed, 15 Apr 1998 17:32:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA08623 for ; Wed, 15 Apr 1998 17:31:50 -0700 (PDT) (envelope-from grog@lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id KAA04378; Thu, 16 Apr 1998 10:01:39 +0930 (CST) (envelope-from grog) Message-ID: <19980416100139.T1090@freebie.lemis.com> Date: Thu, 16 Apr 1998 10:01:39 +0930 From: Greg Lehey To: Julian Elischer Cc: freebsd-current@FreeBSD.ORG Subject: Re: A CAM of worms References: <199804151539.IAA00424@dingo.cdrom.com> <35350420.167EB0E7@whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <35350420.167EB0E7@whistle.com>; from Julian Elischer on Wed, Apr 15, 1998 at 12:01:52PM -0700 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 15 April 1998 at 12:01:52 -0700, Julian Elischer wrote: > Mike Smith wrote: >> >>> Mike Smith once stated: >>> >>> =If there is no CAM support for the 1542 at the merge date, you can >>> =expect it to follow as one of the highest-priority items therafter. >>> >>> What about worms? No CD-writing under 3.0? >> >> Is there anything that you need that cdrecord doesn't do? > > The fact that CAM and the old SCSI can't coexist in the tree > is purely a design decision by Justin. > I managed to almost get it working in about 6 hours using mostly > automatic tools (patch -D etc.) > in October last year. > > personally I think he should spend the 2 or 3 days it would take > to be able to do this. > > or at least make his own branch for a while.. I agree. Although I use CAM, and it works for me, and it seems a whole lot better than the old driver, it's not finished yet. I currently have both the old and new drivers in my source tree. If it's too much trouble to keep the old version after the new one has taken up its final place, maybe it should be left where it is at the moment (/sys/cam) until CAM can do everything the old driver could do. This would have the advantage for Justin that it's almost no work. Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 18:18:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA21343 for freebsd-current-outgoing; Wed, 15 Apr 1998 18:18:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.westbend.net (ns1.westbend.net [207.217.224.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA21319 for ; Wed, 15 Apr 1998 18:18:30 -0700 (PDT) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [207.217.224.195]) by mail.westbend.net (8.8.8/8.8.8) with SMTP id UAA15647 for ; Wed, 15 Apr 1998 20:18:21 -0500 (CDT) (envelope-from hetzels@westbend.net) Message-ID: <000a01bd68d5$de1542e0$c3e0d9cf@admin.westbend.net> From: "Scot W. Hetzel" To: Subject: Re: Digitally Signed Messages (Re: HEADS UP: CAM cutover in two weeks.) Date: Wed, 15 Apr 1998 20:20:39 -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.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----Original Message----- From: brian@litzinger.com >On %M 0, "Scot W. Hetzel" wrote: >> Could you please not send Digitally Signed Messages to the list. For those >> of us that have mail programs that support it, it is kind of annoying to >> have to go through 2 displays to just to read the message. > >I have a mail program that supports Digitally Signed Messages and I don't >have to go through 2 displays just to read the message. > In reality it isn't 2 displays, the first screen is a notification of what a Digitally Signed Message is, and provides an option to never see that screen again. The second screen displays a security warning, which has performed various checks on the digital ID, and there is no way to disable it for all signed messages, only for the currently signed message. Then you can either add'em to the list, or open the message. The reason I posted in the first place is that I believe Digitally Signed Messages and HTML postings to the list provide absolutely no additional info for the topic currently being discussed. Which should be banned. Digitally Signing appropriate messages I have no problem with. (i.e. PATCHES). Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 20:35:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA15676 for freebsd-current-outgoing; Wed, 15 Apr 1998 20:35:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.atipa.com (altrox.atipa.com [208.128.22.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA15669 for ; Wed, 15 Apr 1998 20:35:47 -0700 (PDT) (envelope-from freebsd@atipa.com) Received: (qmail 28531 invoked by uid 1017); 16 Apr 1998 02:33:15 -0000 Date: Wed, 15 Apr 1998 20:33:15 -0600 (MDT) From: Atipa To: freebsd-current@FreeBSD.ORG Subject: Status of native threads on CURRENT / Support for mySQL Message-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 everyone, Can anyone help me out on the status of threads in -CURRENT? I am a bit confused as to when to use the following: 1) pthreads 2) libc_r (reentrant-safe/thread-safe libc?) 3) MIT threads and other 3rd part threads I need to make a fast, reliable database server (mySQL). I am currently using 2.2.6-STABLE w/ MIT threads, but MIT threads do not support unix sockets and are not native to the OS. But then again, I am a bit worried about the current stability of threading on -CURRENT. I have seen several complaints about missing functionality and possible bugs. Is there a noticable performance difference between mySQL on 2.2.6 and on -CURRENT? If so,... Does anyone have any experience / recommnedations for mySQL on -CURRENT? Would these recommendations be altered by using an SMP kernel? TIA, Kevin PS - Did the freebsd-databases mailing-list ever evolve? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 20:50:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA19021 for freebsd-current-outgoing; Wed, 15 Apr 1998 20:50:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from proxy.metro.tas.com.au ([147.109.165.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA19004 for ; Wed, 15 Apr 1998 20:50:42 -0700 (PDT) (envelope-from kerry.morse@metro.tas.com.au) Received: from mttmail.metro.tas.com.au (MTTMail.metro.tas.com.au [147.109.164.249]) by proxy.metro.tas.com.au (8.8.8/8.8.5) with ESMTP id NAA02570 for ; Thu, 16 Apr 1998 13:50:14 +1000 (EST) Received: by MTTMail.metro.tas.gov.au with Internet Mail Service (5.0.1458.49) id ; Thu, 16 Apr 1998 13:50:14 +1000 Message-ID: <02B01380C828D1119ED70020AF641C53068556@MTTMail.metro.tas.gov.au> From: Kerry Morse To: "'freebsd-current@FreeBSD.ORG'" Subject: Help - please... Adaptec 1542 and Exabyte tape problem... Date: Thu, 16 Apr 1998 13:50:13 +1000 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Apr 16 13:35:05 proxy /kernel: aha0: DMA beyond end Of ISA: 0x357cd10 Apr 16 13:35:05 proxy /kernel: st0: bad request, must be between 0 and 0 Apr 16 13:36:57 proxy /kernel: st0: MEDIUM ERROR info:0x1 This happens when I try a "dump -0 /" any suggestions?? The Kernel is using the 3.0-980414-snap off of current.freebsd.org with a vanilla setup. except for a slightly tweaked kernel.. the adaptec controller is also controlling the 3 SCSI disks that the operating system is running successfully off of.. Apr 16 11:20:09 proxy /kernel: st0 at scbus0 target 6 lun 0 Apr 16 11:20:09 proxy /kernel: st0: type 1 removable SCSI 1 Apr 16 11:20:09 proxy /kernel: st0: Sequential-Access density code 0x0, 1024-byte blocks, write-enabled Apr 16 11:20:09 proxy /kernel: ie0 not probed due to I/O address conflict with ed0 at 0x300 Part of the kernel config file: options MATH_EMULATE #Support for x87 emulation 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!] options NFS_ROOT #NFS usable as root device options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15 #Be pessimistic about Joe SCSI device options BOUNCE_BUFFERS #include support for DMA bounce buffers options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor -- Kerry Morse Email:Kerry.Morse@metro.tas.com.au IT Services Phone: (03) 62334224 Metro Tasmania Pty Ltd Fax : (03) 62728770 If you could kick the person who causes you the most problems,you couldn't sit down for a month. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 21:10:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA24630 for freebsd-current-outgoing; Wed, 15 Apr 1998 21:10:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA24605 for ; Wed, 15 Apr 1998 21:10:07 -0700 (PDT) (envelope-from grog@lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id NAA05072; Thu, 16 Apr 1998 13:39:39 +0930 (CST) (envelope-from grog) Message-ID: <19980416133939.F1090@freebie.lemis.com> Date: Thu, 16 Apr 1998 13:39:39 +0930 From: Greg Lehey To: "Scot W. Hetzel" , Michael Class Cc: current@FreeBSD.ORG Subject: Re: Digitally Signed Messages (Re: HEADS UP: CAM cutover in two weeks.) References: <05cb01bd6899$6e0135e0$c3e0d9cf@admin.westbend.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <05cb01bd6899$6e0135e0$c3e0d9cf@admin.westbend.net>; from Scot W. Hetzel on Wed, Apr 15, 1998 at 01:08:01PM -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 Wed, 15 April 1998 at 13:08:01 -0500, Scot W. Hetzel wrote: > Could you please not send Digitally Signed Messages to the list. For those > of us that have mail programs that support it, it is kind of annoying to > have to go through 2 displays to just to read the message. Can somebody give me more information on digital signatures? What software supports it? Where can I find the standards definition? Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 21:22:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA26836 for freebsd-current-outgoing; Wed, 15 Apr 1998 21:22:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from localhost.my.domain (ppp6523.on.bellglobal.com [206.172.208.115]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA26780; Wed, 15 Apr 1998 21:22:00 -0700 (PDT) (envelope-from ac199@hwcn.org) Received: from localhost (tim@localhost) by localhost.my.domain (8.8.8/8.8.8) with ESMTP id AAA00979; Thu, 16 Apr 1998 00:20:24 -0400 (EDT) (envelope-from ac199@hwcn.org) X-Authentication-Warning: localhost.my.domain: tim owned process doing -bs Date: Thu, 16 Apr 1998 00:20:23 -0400 (EDT) From: Tim Vanderhoek X-Sender: tim@localhost Reply-To: ac199@hwcn.org To: =?koi8-r?B?4c7E0sXKIP7F0s7P1w==?= cc: freebsd-current@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: attr_get() does not exist In-Reply-To: <19980416032309.15926@nagual.pp.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [-questions X-post removed] On Thu, 16 Apr 1998, [koi8-r] áÎÄŌÅĘ þÅŌÎÏŨ wrote: > On Wed, Apr 15, 1998 at 02:49:21PM -0700, brian@litzinger.com wrote: > > The version of ncurses supplied with FreeBSD does not include > > the function attr_get(). At least as far as I can find. > > I just add attr_get(). > > Really ncurses 4.1 should be imported as contrib material instead, but > this task is not mine, as I remember Peter takes it, ask him about delays > reason. I believe ncurses 4.2 has been released. I've got a couple of emails sitting in my Inbox from T. E. Dickey regarding ncurses. We're advised that ncurses newer than 1.8.6 (specifically 4.2) to use mytinfo may be some work. Incidentally, he also states that he is quite willing to help (possibly even `do the work for') anyone who wants to add FreeBSD mouse support to ncurses. Code already exists to support mice on X, Linux, and QNX. Adding mouse support for us is certainly possible, but I'm not sure how straightforward it would be. Last time I checked, our documentation was also wanting. Also, be warned. Dickey would appear to use DejaNews to kiboze, so you're being watched. :-) -- tIM...HOEk OPTIMIZATION: the process of using many one-letter variables names hoping that the resultant code will run faster. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 21:22:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA26911 for freebsd-current-outgoing; Wed, 15 Apr 1998 21:22:34 -0700 (PDT) (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 VAA26852 for ; Wed, 15 Apr 1998 21:22:22 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id NAA21035; Thu, 16 Apr 1998 13:51:49 +0930 (CST) Message-Id: <199804160421.NAA21035@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Greg Lehey cc: "Scot W. Hetzel" , Michael Class , current@FreeBSD.ORG Subject: Re: Digitally Signed Messages (Re: HEADS UP: CAM cutover in two weeks.) In-reply-to: Your message of "Thu, 16 Apr 1998 13:39:39 +0930." <19980416133939.F1090@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 16 Apr 1998 13:51:48 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Can somebody give me more information on digital signatures? What > software supports it? Where can I find the standards definition? AFAIK exmh supports using PGP to verify mail messages and the like.. I haven't set it up to do so, but all the options are there :) --------------------------------------------------------------------- |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 Wed Apr 15 22:44:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA12916 for freebsd-current-outgoing; Wed, 15 Apr 1998 22:44:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles142.castles.com [208.214.165.142]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA12908 for ; Wed, 15 Apr 1998 22:44:30 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id WAA01901 for ; Wed, 15 Apr 1998 22:42:11 -0700 (PDT) Message-Id: <199804160542.WAA01901@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: current@FreeBSD.ORG Subject: CAM cutover - important corrections Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 15 Apr 1998 22:42:09 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Due to a significant misunderstanding on my part, please disregard the deadline proposed in my initial post on this topic. The issues surrounding the transition to the CAM SCSI subsystem require considerably more discussion yet, and most importantly more input from both the CAM developers and the user community at large. My apologies for any confusion and/or anxiety that my extremely precipitate posting may have caused. If you have an interest in this issue, please stay tuned, as further items are likely to be raised and discussed in the near future. If at all feasible, you should endeavour to examine and experiment with the CAM test patches located at ftp://ftp.freebsd.org/pub/FreeBSD/cam Regards, -- \\ 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 Apr 15 22:51:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA15246 for freebsd-current-outgoing; Wed, 15 Apr 1998 22:51:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA15223 for ; Wed, 15 Apr 1998 22:51:49 -0700 (PDT) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id FAA09059; Thu, 16 Apr 1998 05:50:45 GMT Date: Thu, 16 Apr 1998 14:50:44 +0900 (JST) From: Michael Hancock To: Atipa cc: freebsd-current@FreeBSD.ORG Subject: Re: Status of native threads on CURRENT / Support for mySQL 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 If you're looking for stability in a production environment stay away from current for a little while as there is a lot of new activity including vm/vfs/cam/softupdates/elf/posix/microtime/alpha/sparc that's going to take a little while to settle even with careful planning and testing. I think thread work is suspended until some dependent underlying vm projects are completed. Regards, Mike On Wed, 15 Apr 1998, Atipa wrote: > Hi everyone, > > Can anyone help me out on the status of threads in -CURRENT? I am a bit > confused as to when to use the following: > > 1) pthreads > 2) libc_r (reentrant-safe/thread-safe libc?) > 3) MIT threads and other 3rd part threads > > I need to make a fast, reliable database server (mySQL). I am currently > using 2.2.6-STABLE w/ MIT threads, but MIT threads do not support unix > sockets and are not native to the OS. But then again, I am a bit worried > about the current stability of threading on -CURRENT. I have seen several > complaints about missing functionality and possible bugs. > > Is there a noticable performance difference between mySQL on 2.2.6 and on > -CURRENT? If so,... > > Does anyone have any experience / recommnedations for mySQL on -CURRENT? > Would these recommendations be altered by using an SMP kernel? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 22:57:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA16674 for freebsd-current-outgoing; Wed, 15 Apr 1998 22:57:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA16652 for ; Wed, 15 Apr 1998 22:57:19 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0yPheR-0002X8-00; Wed, 15 Apr 1998 22:55:59 -0700 Date: Wed, 15 Apr 1998 22:55:55 -0700 (PDT) From: Tom To: Kerry Morse cc: "'freebsd-current@FreeBSD.ORG'" Subject: Re: Help - please... Adaptec 1542 and Exabyte tape problem... In-Reply-To: <02B01380C828D1119ED70020AF641C53068556@MTTMail.metro.tas.gov.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 16 Apr 1998, Kerry Morse wrote: > Apr 16 13:35:05 proxy /kernel: aha0: DMA beyond end Of ISA: 0x357cd10 Bounce buffers are required to DMA above the 16MB for ISA devices. However, bounce buffers do not work for the aha driver (it is unclear whether the driver or the bounce buffers are broken). This is any old problem. See the archives. It seems that any developer who has more than 16MB of RAM has also decided to upgrade to non-ISA controllers. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 23:07:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA19992 for freebsd-current-outgoing; Wed, 15 Apr 1998 23:07:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlogic.com.au [203.36.2.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA19950 for ; Wed, 15 Apr 1998 23:07:01 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.5/8.8.7) id QAA02962; Thu, 16 Apr 1998 16:05:45 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199804160605.QAA02962@cimlogic.com.au> Subject: Re: Status of native threads on CURRENT / Support for mySQL In-Reply-To: from Michael Hancock at "Apr 16, 98 02:50:44 pm" To: michaelh@cet.co.jp (Michael Hancock) Date: Thu, 16 Apr 1998 16:05:44 +1000 (EST) Cc: freebsd@atipa.com, 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 Michael Hancock wrote: > If you're looking for stability in a production environment stay away from > current for a little while as there is a lot of new activity including > vm/vfs/cam/softupdates/elf/posix/microtime/alpha/sparc that's going to > take a little while to settle even with careful planning and testing. > > I think thread work is suspended until some dependent underlying vm > projects are completed. The _kernel_ thread work is limping along. It hasn't quite come to a halt. 8-) The code in libc_r passes all my local tests that include some rather big applications with performance comparisons of the same code running under OSF/1, including some X based. There have been changes recently to allow for kernel threading as an alternative, but these are insignificant. The elf, posix (realtime), alpha and sparc things won't destabilise the system, IMO. It looks like the microtime changes have been pretty much digested too. As always, -current in a production environment is a risk, but the system looks stable at present. YMMV. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 23:11:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA21209 for freebsd-current-outgoing; Wed, 15 Apr 1998 23:11:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA21111 for ; Wed, 15 Apr 1998 23:10:53 -0700 (PDT) (envelope-from andrew@zeta.org.au) Received: from gurney.reilly.home (d26.syd2.zeta.org.au [203.26.11.26]) by godzilla.zeta.org.au (8.8.7/8.8.7) with ESMTP id QAA29572; Thu, 16 Apr 1998 16:05:17 +1000 Received: (from andrew@localhost) by gurney.reilly.home (8.8.8/8.8.5) id KAA02399; Thu, 16 Apr 1998 10:05:21 +1000 (EST) From: Andrew Reilly Message-Id: <199804160005.KAA02399@gurney.reilly.home> Date: Thu, 16 Apr 1998 10:05:20 +1000 (EST) Subject: Re: Digitally Signed Messages (Re: HEADS UP: CAM cutover in two wee ks.) To: hetzels@westbend.net cc: michael_class@hp.com, current@FreeBSD.ORG In-Reply-To: <05cb01bd6899$6e0135e0$c3e0d9cf@admin.westbend.net> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 15 Apr, Scot W. Hetzel wrote: > Could you please not send Digitally Signed Messages to the list. For those > of us that have mail programs that support it, it is kind of annoying to > have to go through 2 displays to just to read the message. It wasn't digitally signed when it got to me, and I do have an MUA that knows about such things (tkrat). It did have a bit of Bcc: duplicate header bumpf. That wasn't in a MIME section though, so it should have just come through as part of the message. It did for me. Methinks your mailer is broken: >X-Mailer: Microsoft Outlook Express 4.72.2106.4 >X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 -- Andrew "The steady state of disks is full." -- Ken Thompson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 23:21:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA23937 for freebsd-current-outgoing; Wed, 15 Apr 1998 23:21:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA23930 for ; Wed, 15 Apr 1998 23:21:14 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id AAA28394; Thu, 16 Apr 1998 00:17:30 -0600 (MDT) Date: Thu, 16 Apr 1998 00:17:30 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199804160617.AAA28394@narnia.plutotech.com> To: Tom cc: current@FreeBSD.ORG Subject: Re: Help - please... Adaptec 1542 and Exabyte tape problem... Newsgroups: pluto.freebsd.current In-Reply-To: User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you wrote: > > On Thu, 16 Apr 1998, Kerry Morse wrote: > >> Apr 16 13:35:05 proxy /kernel: aha0: DMA beyond end Of ISA: 0x357cd10 > > Bounce buffers are required to DMA above the 16MB for ISA devices. > However, bounce buffers do not work for the aha driver (it is unclear > whether the driver or the bounce buffers are broken). It's not the driver, and it's not the bounce buffers. It's the fact that several portions of the SCSI layer allocate objects that are the targets of DMA on the kernel stack and that a clude in scsi_scsi_cmd() to detect this and properly bounce the data does not work. > This is any old problem. See the archives. It seems that any developer > who has more than 16MB of RAM has also decided to upgrade to non-ISA > controllers. Bah. I implemented the Bus DMA version of bounce buffers just so ISA AdvanSys and Adaptec cards could be properly supported. The 1542 driver simply hasn't been completed yet for CAM. > Tom -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 23:25:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA25322 for freebsd-current-outgoing; Wed, 15 Apr 1998 23:25:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA25279; Wed, 15 Apr 1998 23:25:39 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id XAA05141; Wed, 15 Apr 1998 23:25:26 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp03.primenet.com, id smtpd005123; Wed Apr 15 23:25:19 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id XAA13265; Wed, 15 Apr 1998 23:25:16 -0700 (MST) From: Terry Lambert Message-Id: <199804160625.XAA13265@usr01.primenet.com> Subject: Re: temporary FreeBSD token-ring list. To: winter@jurai.net (Matthew N. Dodd) Date: Thu, 16 Apr 1998 06:25:16 +0000 (GMT) Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: from "Matthew N. Dodd" at Apr 15, 98 04:06:25 pm 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 > freebsd-tokenring@jurai.net is up and running as a temporary mailing list > for the ongoing discussion of the efforts to add Token Ring and 802.2 LLC > support to FreeBSD > > As there are a number of non-token ring issues that we will have to solve > before working on any token-ring specific issues, I invite everyone who > has an interest in making the network subsystem a bit less ethernet > centric in the places that it is, and those who have interest in > supporting Novell 802.3 IPX and NetBEUI. The 802.2 LLC is common to all > of these. As a point of interest, MITRE announced a working NetBEUI for FreeBSD a number of moths ago on the SAMBA list. To do this, they must have implemented the 802.3 LLC. Someone should follow up with MITRE. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 23:32:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA27379 for freebsd-current-outgoing; Wed, 15 Apr 1998 23:32:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA27361 for ; Wed, 15 Apr 1998 23:32:17 -0700 (PDT) (envelope-from michael_class@hp.com) Received: from hpbbse.bbn.hp.com (root@hpbbse.bbn.hp.com [15.136.26.26]) by palrel1.hp.com (8.8.6/8.8.5tis) with ESMTP id XAA23193; Wed, 15 Apr 1998 23:32:14 -0700 (PDT) Received: from hp.com (michaelc@tmbbwmc.bbn.hp.com [15.136.25.181]) by hpbbse.bbn.hp.com with ESMTP (8.7.6/8.7.3) id HAA12805; Thu, 16 Apr 1998 07:32:13 +0100 (MEZ) Message-ID: <3535A5EB.E6B6E281@hp.com> Date: Thu, 16 Apr 1998 08:32:11 +0200 From: Michael Class Organization: Hewlett-Packard GmbH X-Mailer: Mozilla 4.05 [en] (X11; I; HP-UX B.10.20 9000/777) MIME-Version: 1.0 To: Greg Lehey CC: "Scot W. Hetzel" , current@FreeBSD.ORG Subject: Re: Digitally Signed Messages (Re: HEADS UP: CAM cutover in two weeks.) References: <05cb01bd6899$6e0135e0$c3e0d9cf@admin.westbend.net> <19980416133939.F1090@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 Wed, 15 April 1998 at 13:08:01 -0500, Scot W. Hetzel wrote: > > Could you please not send Digitally Signed Messages to the list. For those > > of us that have mail programs that support it, it is kind of annoying to > > have to go through 2 displays to just to read the message. > > Can somebody give me more information on digital signatures? What > software supports it? Where can I find the standards definition? > > Greg > -- Hello, I think I caused the discussion :-( Iam sorry, I just have the digitial signing (with X.509 Certificates, done by Netscape Communicator-Mailer) switched on as default, and forgot to switch it of for the message to this list. I apologize! The reason why I have switched it on by default is that I want to get people in discussions about digital signing, so that more and more people will understand how that works in the future. Btw: A digital signed message is just a MIME-Message with an attachment that has the Hash digital encrypted. Do you think that it is evil to use MIME-Messages on a mailinglist these days? Micha -- ___________________________________________________________________________ Michael Class E-Mail: michael_class@hp.com E-Business Solutions Center Phone: +49 7031 14-3707 EBSO-SERC Fax: +49 7031 14-4196 ___________________________________________________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 23:50:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA01090 for freebsd-current-outgoing; Wed, 15 Apr 1998 23:50:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA00979 for ; Wed, 15 Apr 1998 23:49:53 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id XAA15151; Wed, 15 Apr 1998 23:49:49 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp01.primenet.com, id smtpd015133; Wed Apr 15 23:49:43 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id XAA14604; Wed, 15 Apr 1998 23:49:37 -0700 (MST) From: Terry Lambert Message-Id: <199804160649.XAA14604@usr01.primenet.com> Subject: Re: Digitally Signed Messages (Re: HEADS UP: CAM cutover in two weeks.) To: grog@lemis.com (Greg Lehey) Date: Thu, 16 Apr 1998 06:49:37 +0000 (GMT) Cc: hetzels@westbend.net, michael_class@hp.com, current@FreeBSD.ORG In-Reply-To: <19980416133939.F1090@freebie.lemis.com> from "Greg Lehey" at Apr 16, 98 01:39:39 pm 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 > Can somebody give me more information on digital signatures? What > software supports it? Where can I find the standards definition? You are looking for the X.509 standard. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 15 23:58:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA03576 for freebsd-current-outgoing; Wed, 15 Apr 1998 23:58:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA03569 for ; Wed, 15 Apr 1998 23:58:11 -0700 (PDT) (envelope-from grog@lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id QAA05846; Thu, 16 Apr 1998 16:27:53 +0930 (CST) (envelope-from grog) Message-ID: <19980416162753.I1090@freebie.lemis.com> Date: Thu, 16 Apr 1998 16:27:53 +0930 From: Greg Lehey To: Andrew Reilly , hetzels@westbend.net Cc: michael_class@hp.com, current@FreeBSD.ORG Subject: Re: Digitally Signed Messages (Re: HEADS UP: CAM cutover in two wee ks.) References: <05cb01bd6899$6e0135e0$c3e0d9cf@admin.westbend.net> <199804160005.KAA02399@gurney.reilly.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199804160005.KAA02399@gurney.reilly.home>; from Andrew Reilly on Thu, Apr 16, 1998 at 10:05:20AM +1000 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 Thu, 16 April 1998 at 10:05:20 +1000, Andrew Reilly wrote: > On 15 Apr, Scot W. Hetzel wrote: >> X-Mailer: Microsoft Outlook Express 4.72.2106.4 >> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Just because it's Outlook? Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 03:01:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA27623 for freebsd-current-outgoing; Thu, 16 Apr 1998 03:01:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA27618; Thu, 16 Apr 1998 03:01:39 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id MAA22842; Thu, 16 Apr 1998 12:01:00 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Thu, 16 Apr 1998 12:00:59 +0200 (MET DST) Mime-Version: 1.0 To: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: syscons.c and graphical screensavers Organization: Gutteklubben Terrasse / KRST / PUMS / YASMW X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-Stop-Spam: http://www.cauce.org From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 16 Apr 1998 12:00:58 +0200 Message-ID: Lines: 9 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I changed current's src/sys/i386/isa/syscons.c to put the "should we stop the screensaver" check before the "should we just return" check. This will make graphical screensavers possible - but BE WARNED that to the best of my knowledge syscons.c still does not handle console switches properly when a graphical screensaver is active, especially not switches to whichever console X is using. I'll see to that RSN. -- fprintf(stderr, "I have a closed mind. It helps keeping the rain out.\n"); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 03:18:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA00486 for freebsd-current-outgoing; Thu, 16 Apr 1998 03:18:07 -0700 (PDT) (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 DAA00480 for ; Thu, 16 Apr 1998 03:18:03 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id SAA14071; Thu, 16 Apr 1998 18:15:22 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199804161015.SAA14071@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: "Justin T. Gibbs" cc: Tom , current@FreeBSD.ORG Subject: Re: Help - please... Adaptec 1542 and Exabyte tape problem... In-reply-to: Your message of "Thu, 16 Apr 1998 00:17:30 CST." <199804160617.AAA28394@narnia.plutotech.com> Date: Thu, 16 Apr 1998 18:15:21 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Justin T. Gibbs" wrote: > In article you wrote: > > > > On Thu, 16 Apr 1998, Kerry Morse wrote: > > > >> Apr 16 13:35:05 proxy /kernel: aha0: DMA beyond end Of ISA: 0x357cd10 > > > > Bounce buffers are required to DMA above the 16MB for ISA devices. > > However, bounce buffers do not work for the aha driver (it is unclear > > whether the driver or the bounce buffers are broken). > > It's not the driver, and it's not the bounce buffers. It's the fact > that several portions of the SCSI layer allocate objects that are > the targets of DMA on the kernel stack and that a clude in scsi_scsi_cmd() > to detect this and properly bounce the data does not work. I fixed this on one of my machines about an hour ago. There are several problems. 1: The kernel stack used to be < KERNBASE, it no longer is. The scsi_scsi_cmd() hack to catch these wasn't updated when the kstack moved. 2: I'm not 100% sure of all calling sequences for scsi_scsi_cmd(), but it looks like it tries to bcopy() things to and from userspace instead of using copyin/copyout.. This could be deadly under the wrong circumstances to say the least. I'm re-testing my patches, I managed to end up with 12 busy (locked) buffers when I did a reboot test. > > This is any old problem. See the archives. It seems that any developer > > who has more than 16MB of RAM has also decided to upgrade to non-ISA > > controllers. > > Bah. I implemented the Bus DMA version of bounce buffers just so ISA > AdvanSys and Adaptec cards could be properly supported. The 1542 driver > simply hasn't been completed yet for CAM. I propose to patch the scsi bounce buffer support One Last Time(TM) prior to CAM going in. > > Tom > > -- > Justin Cheers, -Peter -- Peter Wemm Netplex Consulting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 03:21:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA00977 for freebsd-current-outgoing; Thu, 16 Apr 1998 03:21:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from iworks.InterWorks.org (deischen@iworks.interworks.org [128.255.18.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA00971 for ; Thu, 16 Apr 1998 03:21:54 -0700 (PDT) (envelope-from deischen@iworks.InterWorks.org) Received: (from deischen@localhost) by iworks.InterWorks.org (8.8.7/) id FAA28103; Thu, 16 Apr 1998 05:30:49 -0500 (CDT) Message-Id: <199804161030.FAA28103@iworks.InterWorks.org> Date: Thu, 16 Apr 1998 05:30:49 -0500 (CDT) From: "Daniel M. Eischen" To: freebsd-current@FreeBSD.ORG, jb@cimlogic.com.au Subject: Re: Status of native threads on CURRENT / Support for mySQL Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The code in libc_r passes all my local tests that include some rather > big applications with performance comparisons of the same code running > under OSF/1, including some X based. There have been changes > recently to allow for kernel threading as an alternative, but these > are insignificant. Care to elaborate on this? Can we now create kernel threads with PTHREAD_SCOPE_SYSTEM and get kernel threads? Dan Eischen deischen@iworks.InterWorks.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 03:31:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA02787 for freebsd-current-outgoing; Thu, 16 Apr 1998 03:31:32 -0700 (PDT) (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 SMTP id DAA02780 for ; Thu, 16 Apr 1998 03:31:29 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: by outmail.utsunomiya-u.ac.jp id AA13857; Thu, 16 Apr 1998 19:30:59 +0900 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 TAA03820; Thu, 16 Apr 1998 19:39:37 +0900 (JST) Message-Id: <199804161039.TAA03820@zodiac.mech.utsunomiya-u.ac.jp> To: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Cc: current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: syscons.c and graphical screensavers In-Reply-To: Your message of "16 Apr 1998 12:00:58 +0200." References: Date: Thu, 16 Apr 1998 19:39:36 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I changed current's src/sys/i386/isa/syscons.c to put the "should we >stop the screensaver" check before the "should we just return" check. >This will make graphical screensavers possible - but BE WARNED that to >the best of my knowledge syscons.c still does not handle console >switches properly when a graphical screensaver is active, especially >not switches to whichever console X is using. I'll see to that RSN. I will also dig out the patch which msmith and I developed to make syscons to have graphical screensaver AND splash screen back in February. I will let you know. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 03:32:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA03033 for freebsd-current-outgoing; Thu, 16 Apr 1998 03:32:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlogic.com.au [203.36.2.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA03024 for ; Thu, 16 Apr 1998 03:32:21 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.5/8.8.7) id UAA04209; Thu, 16 Apr 1998 20:31:22 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199804161031.UAA04209@cimlogic.com.au> Subject: Re: Status of native threads on CURRENT / Support for mySQL In-Reply-To: <199804161030.FAA28103@iworks.InterWorks.org> from "Daniel M. Eischen" at "Apr 16, 98 05:30:49 am" To: deischen@iworks.InterWorks.org (Daniel M. Eischen) Date: Thu, 16 Apr 1998 20:31:22 +1000 (EST) Cc: freebsd-current@FreeBSD.ORG, jb@cimlogic.com.au 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 Daniel M. Eischen wrote: > Care to elaborate on this? Can we now create kernel threads with > PTHREAD_SCOPE_SYSTEM and get kernel threads? Not yet. The rfork syscall allows a kernel thread to be created, but more work is required to implement the pthread_* functions. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 03:57:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA06774 for freebsd-current-outgoing; Thu, 16 Apr 1998 03:57:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from techunix.technion.ac.il (mellon@techunix.technion.ac.il [132.68.1.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA06768 for ; Thu, 16 Apr 1998 03:57:22 -0700 (PDT) (envelope-from mellon@techunix.technion.ac.il) Received: (from mellon@localhost) by techunix.technion.ac.il (8.8.7/8.8.5) id NAA11314; Thu, 16 Apr 1998 13:57:16 +0300 (IDT) Message-ID: <19980416135716.36703@techunix.technion.ac.il> Date: Thu, 16 Apr 1998 13:57:16 +0300 From: Anatoly Vorobey To: current@FreeBSD.ORG Subject: Re: Spelling etc. References: <35329CF4.65DE8E18@hdz-ima.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.88 In-Reply-To: <35329CF4.65DE8E18@hdz-ima.rwth-aachen.de>; from Gerald Heinig on Tue, Apr 14, 1998 at 01:17:09AM +0200 X-Disclaimer: I was young, I needed the money! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You, Gerald Heinig, were spotted writing this on Tue, Apr 14, 1998 at 01:17:09AM +0200: > Hi guys, > > The dog wagged its tail (*NOT* itīs tail!!!) > > and > > Itīs cold today (ie. It is cold today) Well, a few weeks ago I sent a send-pr with a diff attached that eliminated _all_ its/it's mistakes in the kernel source (there were about 70 of them). Nothing resulted; I still hope someone would deal with it. -- Anatoly Vorobey, mellon@pobox.com http://pobox.com/~mellon/ "Angels can fly because they take themselves lightly" - G.K.Chesterton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 04:16:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA11739 for freebsd-current-outgoing; Thu, 16 Apr 1998 04:16:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from proxy.metro.tas.com.au ([147.109.165.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA11553 for ; Thu, 16 Apr 1998 04:15:57 -0700 (PDT) (envelope-from kerry.morse@metro.tas.com.au) Received: from mttmail.metro.tas.com.au (MTTMail.metro.tas.com.au [147.109.164.249]) by proxy.metro.tas.com.au (8.8.8/8.8.5) with ESMTP id VAA03075 for ; Thu, 16 Apr 1998 21:15:49 +1000 (EST) Received: by MTTMail.metro.tas.gov.au with Internet Mail Service (5.0.1458.49) id ; Thu, 16 Apr 1998 21:15:38 +1000 Message-ID: <02B01380C828D1119ED70020AF641C53068558@MTTMail.metro.tas.gov.au> From: Kerry Morse To: "'Peter Wemm'" , "Justin T. Gibbs" Cc: Tom , current@FreeBSD.ORG Subject: RE: Help - please... Adaptec 1542 and Exabyte tape problem... Date: Thu, 16 Apr 1998 21:15:37 +1000 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Thanks for the help... > So basically it's not going to work for at least a while or a few fixes so swapping the controller out over with a PCI controller while no ones looking is my best solution at present... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 06:38:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA04590 for freebsd-current-outgoing; Thu, 16 Apr 1998 06:38:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from limbo.rtfm.net (nathan@rtfm.net [204.141.125.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA04353 for ; Thu, 16 Apr 1998 06:37:31 -0700 (PDT) (envelope-from nathan@limbo.rtfm.net) Received: (from nathan@localhost) by limbo.rtfm.net (8.8.8/8.8.8) id JAA21706; Thu, 16 Apr 1998 09:35:15 -0400 (EDT) Message-ID: <19980416093514.34787@rtfm.net> Date: Thu, 16 Apr 1998 09:35:14 -0400 From: Nathan Dorfman To: Michael Class , Greg Lehey Cc: "Scot W. Hetzel" , current@FreeBSD.ORG Subject: Re: Digitally Signed Messages (Re: HEADS UP: CAM cutover in two weeks.) References: <05cb01bd6899$6e0135e0$c3e0d9cf@admin.westbend.net> <19980416133939.F1090@freebie.lemis.com> <3535A5EB.E6B6E281@hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <3535A5EB.E6B6E281@hp.com>; from Michael Class on Thu, Apr 16, 1998 at 08:32:11AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 16, 1998 at 08:32:11AM +0200, Michael Class wrote: > Greg Lehey wrote: > > > > On Wed, 15 April 1998 at 13:08:01 -0500, Scot W. Hetzel wrote: > > > Could you please not send Digitally Signed Messages to the list. For those > > > of us that have mail programs that support it, it is kind of annoying to > > > have to go through 2 displays to just to read the message. > > > > Can somebody give me more information on digital signatures? What > > software supports it? Where can I find the standards definition? > > > > Greg > > -- > > Hello, > > I think I caused the discussion :-( Iam sorry, I just have the digitial > signing (with X.509 Certificates, done by Netscape Communicator-Mailer) > switched on as default, and forgot to switch it of for the message to > this list. I apologize! > > The reason why I have switched it on by default is that I want to get > people in discussions about digital signing, so that more and more > people will understand how that works in the future. > > Btw: A digital signed message is just a MIME-Message with an attachment > that has the Hash digital encrypted. Do you think that it is evil to use > MIME-Messages on a mailinglist these days? Does this mean that PGP is truly dead? > Micha > > -- > ___________________________________________________________________________ > Michael Class E-Mail: michael_class@hp.com > E-Business Solutions Center Phone: +49 7031 14-3707 > EBSO-SERC Fax: +49 7031 14-4196 > ___________________________________________________________________________ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- ________________ _______________________________ / Nathan Dorfman V PGP: finger nathan@rtfm.net / / nathan@rtfm.net | http://www.rtfm.net / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 07:55:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA19146 for freebsd-current-outgoing; Thu, 16 Apr 1998 07:55:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.westbend.net (ns1.westbend.net [207.217.224.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA19137 for ; Thu, 16 Apr 1998 07:55:04 -0700 (PDT) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [207.217.224.195]) by mail.westbend.net (8.8.8/8.8.8) with SMTP id JAA17232; Thu, 16 Apr 1998 09:54:56 -0500 (CDT) (envelope-from hetzels@westbend.net) Message-ID: <006801bd6947$ea64a1e0$c3e0d9cf@admin.westbend.net> From: "Scot W. Hetzel" To: "Andrew Reilly" Cc: , Subject: Re: Digitally Signed Messages (Re: HEADS UP: CAM cutover in two weeks.) Date: Thu, 16 Apr 1998 09:57:01 -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.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----Original Message----- From: Andrew Reilly >Methinks your mailer is broken: > >>X-Mailer: Microsoft Outlook Express 4.72.2106.4 >>X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 > My Mailer isn't broken, I just wasn't expecting it from this list. And the extra steps I had to take to read the message. The real question is does Digitally Signed Messages, and HTML belong on a Mailing list? Absolutely NOT. By the way the original sender used Netscape to send it: Organization: Hewlett-Packard GmbH X-Mailer: Mozilla 4.05 [en] (X11; I; HP-UX B.10.20 9000/777) MIME-Version: 1.0 Scot P.S. Thanks, for you time to discuss this, we now return you to your regularly scheduled current mailing list. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 09:45:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14018 for freebsd-current-outgoing; Thu, 16 Apr 1998 09:45:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from jumping-spider.aracnet.com (root@jumping-spider.aracnet.com [205.159.88.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA13970 for ; Thu, 16 Apr 1998 16:45:37 GMT (envelope-from beattie@aracnet.com) Received: from shell2.aracnet.com (shell2.aracnet.com [205.159.88.20]) by jumping-spider.aracnet.com (8.8.5/8.8.5) with ESMTP id JAA03143; Thu, 16 Apr 1998 09:45:20 -0700 Received: from localhost by shell2.aracnet.com (8.8.7) id JAA04647; Thu, 16 Apr 1998 09:45:20 -0700 Date: Thu, 16 Apr 1998 09:45:20 -0700 (PDT) From: Brian Beattie To: Tom cc: Kerry Morse , "'freebsd-current@FreeBSD.ORG'" Subject: Re: Help - please... Adaptec 1542 and Exabyte tape problem... 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, 15 Apr 1998, Tom wrote: > > On Thu, 16 Apr 1998, Kerry Morse wrote: > > > Apr 16 13:35:05 proxy /kernel: aha0: DMA beyond end Of ISA: 0x357cd10 > > Bounce buffers are required to DMA above the 16MB for ISA devices. > However, bounce buffers do not work for the aha driver (it is unclear > whether the driver or the bounce buffers are broken). > > This is any old problem. See the archives. It seems that any developer > who has more than 16MB of RAM has also decided to upgrade to non-ISA > controllers. > I am planning to implement the aha1542 controller under the new CAM interface. I have more than 16MB and plan to ensure bounce buffers work. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 11:06:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29229 for freebsd-current-outgoing; Thu, 16 Apr 1998 11:06:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from unix.tfs.net (as1-p20.tfs.net [139.146.210.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA29197 for ; Thu, 16 Apr 1998 18:06:42 GMT (envelope-from jbryant@unix.tfs.net) Received: (from jbryant@localhost) by unix.tfs.net (8.8.8/8.8.5) id NAA10019; Wed, 20 May 1998 13:06:19 -0500 (CDT) From: Jim Bryant Message-Id: <199805201806.NAA10019@unix.tfs.net> Subject: Re: Help - please... Adaptec 1542 and Exabyte tape problem... In-Reply-To: from Brian Beattie at "Apr 16, 98 09:45:20 am" To: beattie@aracnet.com (Brian Beattie) Date: Wed, 20 May 1998 13:06:18 -0500 (CDT) Cc: freebsd-current@FreeBSD.ORG Reply-to: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 3.0-CURRENT #5: Sun Mar 8 12:29:10 CST 1998 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 In reply: > On Wed, 15 Apr 1998, Tom wrote: > > > > > On Thu, 16 Apr 1998, Kerry Morse wrote: > > > > > Apr 16 13:35:05 proxy /kernel: aha0: DMA beyond end Of ISA: 0x357cd10 > > > > Bounce buffers are required to DMA above the 16MB for ISA devices. > > However, bounce buffers do not work for the aha driver (it is unclear > > whether the driver or the bounce buffers are broken). > > > > This is any old problem. See the archives. It seems that any developer > > who has more than 16MB of RAM has also decided to upgrade to non-ISA > > controllers. > > > > I am planning to implement the aha1542 controller under the new CAM > interface. I have more than 16MB and plan to ensure bounce buffers work. crap.. i just sold my 1542cf for this very reason... i was wanting it to handle low-bandwidth stuff like the CD-ROM, M-O drive, and DDS-2 tape drive, but I kept getting the above messages... now i've got a heck of a lot of stuff hanging off my 2940UW... i of course have 'OPTION BOUNCE_BUFFERS' in my config... jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 11:41:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05290 for freebsd-current-outgoing; Thu, 16 Apr 1998 11:41:28 -0700 (PDT) (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 SAA05284 for ; Thu, 16 Apr 1998 18:41:23 GMT (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.8.8/8.8.8) with ESMTP id TAA02215 for ; Thu, 16 Apr 1998 19:41:19 +0100 (BST) (envelope-from kpielorz@tdx.co.uk) Message-ID: <353650CB.5FAD74C6@tdx.co.uk> Date: Thu, 16 Apr 1998 19:41:15 +0100 From: Karl Pielorz Organization: TDX X-Mailer: Mozilla 4.04 [en] (WinNT; I) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Should I run -CURRENT? SNAP? 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 been watching this list for a while now... My FreeBSD box is currently a dual P-Pro 200 with 192Mb of RAM and running 2.2.6-R. I use it mainly for mail, apache (and Apache-SSL), heavily for Samba - and also for some pretty scary shell scripts (basic data manipulation building web pages etc.) I would like to use the second processor - but I'm a bit worried about all my data... I do regular backups - but the machine houses some 18Gb of data spread accross an aging collection of IDE and SCSI drives - which are used via a 100Mbit link fxp card and Samba. I've seen a lot of problems with SoftUpdates going around recently - some of my drives are CCD based, so I would be avoiding stuff like that... What I'm trying to get at - is it a good idea? - The box isn't _mission_ critical, I don't mind it crashing, panicing etc. - but I'd rather not have the filesystems hosed... With this in mind can anyone offer any advice? - i.e. some good SNAP's to try etc? - I've read all the impending doom FAQ's on the FreeBSD site - and I have a working knowledge of 'c' and making worlds etc... :-) If I find a SNAP that works well is it likely to stay 'working well' (I know, how longs a piece of string?) - or am I better off staying 'really' current? I have run -CURRENT before, but only on an old 486 which whilst it could run it - would take days and days to do any makeworlds... :-( Oh for SMP-Stable... Regards, Karl Pielorz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 11:46:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06418 for freebsd-current-outgoing; Thu, 16 Apr 1998 11:46:34 -0700 (PDT) (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 SAA06380 for ; Thu, 16 Apr 1998 18:46:22 GMT (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id LAA00669; Thu, 16 Apr 1998 11:42:57 -0700 (PDT) Message-Id: <199804161842.LAA00669@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Karl Pielorz cc: current@FreeBSD.ORG Subject: Re: Should I run -CURRENT? SNAP? In-reply-to: Your message of "Thu, 16 Apr 1998 19:41:15 BST." <353650CB.5FAD74C6@tdx.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 16 Apr 1998 11:42:56 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > What I'm trying to get at - is it a good idea? - The box isn't _mission_ > critical, I don't mind it crashing, panicing etc. - but I'd rather not have > the filesystems hosed... -current right now seems to be quite stable. > If I find a SNAP that works well is it likely to stay 'working well' (I > know, how longs a piece of string?) - or am I better off staying 'really' > current? I tend to leapfrog; when I have a stable system I'll live with it until either I need/want to play with a new feature, or it just feels "really old" (usually 2-3 months). > Oh for SMP-Stable... Testing and input from people like you is what it will take to achieve just exactly 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 Apr 16 11:51:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07701 for freebsd-current-outgoing; Thu, 16 Apr 1998 11:51:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA07678 for ; Thu, 16 Apr 1998 18:51:33 GMT (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id UAA29581 for ; Thu, 16 Apr 1998 20:54:33 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Thu, 16 Apr 1998 20:54:32 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: freebsd-current@FreeBSD.ORG Subject: Booting issues Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I have a suggestion: could we change the messages "Can't find kernel.conf" etc. to something less scary for the new user? Something like "Using default config (no /kernel.conf)". And another issue: some time ago there was very animated discussion about "/boot.banner". Is this idea being implemented by someone, or it just died off? And yet another (CAM related): does present bootblock allow to use the "da" instead of "sd"? Andrzej Bialecki ---------------------+--------------------------------------------------------- abial@warman.org.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. ---------------------+--------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 11:54:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08616 for freebsd-current-outgoing; Thu, 16 Apr 1998 11:54:43 -0700 (PDT) (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 SAA08611 for ; Thu, 16 Apr 1998 18:54:40 GMT (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id TAA07192; Thu, 16 Apr 1998 19:15:02 +0200 From: Luigi Rizzo Message-Id: <199804161715.TAA07192@labinfo.iet.unipi.it> Subject: Diskless configuration... To: current@FreeBSD.ORG Date: Thu, 16 Apr 1998 19:15:01 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [not sure this is relevant to -current, but since the noise on -hackers is so high...] At http://www.iet.unipi.it/~luigi/diskless.html , I have put up a short description of the strategy I used to support two labs of diskless FreeBSD workstation booting from the same server using a shared readonly root and /usr partition. The description also includes most if not all of the files I have used to configure my machines. I'd like to receive suggestions and comments on the architecture i have devised, to see if there is some better approach. thanks luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 12:38:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA20851 for freebsd-current-outgoing; Thu, 16 Apr 1998 12:38:31 -0700 (PDT) (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 TAA20826 for ; Thu, 16 Apr 1998 19:38:14 GMT (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.8.8/8.8.8) with ESMTP id UAA02441; Thu, 16 Apr 1998 20:37:59 +0100 (BST) (envelope-from kpielorz@tdx.co.uk) Message-ID: <35365E14.BD1F9D21@tdx.co.uk> Date: Thu, 16 Apr 1998 20:37:56 +0100 From: Karl Pielorz Organization: TDX X-Mailer: Mozilla 4.04 [en] (WinNT; I) MIME-Version: 1.0 To: Mike Smith CC: current@FreeBSD.ORG Subject: Re: Should I run -CURRENT? SNAP? References: <199804161842.LAA00669@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: > -current right now seems to be quite stable. Yes, I haven't seen too many complaints recently... (Did I say complaints? - I mean't 'bug information'... :-) > > If I find a SNAP that works well is it likely to stay 'working well' (I > > know, how longs a piece of string?) - or am I better off staying 'really' > > current? > > I tend to leapfrog; when I have a stable system I'll live with it until > either I need/want to play with a new feature, or it just feels "really > old" (usually 2-3 months). Sounds like a good strategy... I like the 'play' word in there... > > Oh for SMP-Stable... > > Testing and input from people like you is what it will take to achieve > just exactly that. I guess so... I've just freed up a wedge of space on another 1Gb drive - and I'm about to install it... Thanks for your advice (to both my postings! - memory mapped IO?) Regards, Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 14:13:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA04613 for freebsd-current-outgoing; Thu, 16 Apr 1998 14:13:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hwcn.org (ac199@james.hwcn.org [199.212.94.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA04568 for ; Thu, 16 Apr 1998 21:12:57 GMT (envelope-from hoek@hwcn.org) Received: from localhost (ac199@localhost) by hwcn.org (8.8.8/8.8.8) with SMTP id RAA19905; Thu, 16 Apr 1998 17:08:33 -0400 (EDT) Date: Thu, 16 Apr 1998 17:08:33 -0400 (EDT) From: Tim Vanderhoek To: Anatoly Vorobey cc: current@FreeBSD.ORG Subject: Re: Spelling etc. In-Reply-To: <19980416135716.36703@techunix.technion.ac.il> Message-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, 16 Apr 1998, Anatoly Vorobey wrote: > Well, a few weeks ago I sent a send-pr with a diff attached > that eliminated _all_ its/it's mistakes in the kernel source > (there were about 70 of them). Nothing resulted; I still hope > someone would deal with it. That's because a patch that broad to the kernel source has more potential (political) trouble attached, and is less urgent (than patches to regular docs). It'll be dealt with in time, I expect. In general, if you're submitting patches to eliminite these types of mistakes, they will be dealt with the fastest for 1) web pages, 2) handbook 3) manpages, 4) FAQ, 5) source-code comments. Nos. 1-4 are all about equal and fairly fast. Patches for No 5 are quite welcome, too; they just have a history of taking longer to get fixed. -- Outnumbered? Maybe. Outspoken? Never! tIM...HOEk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 14:28:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10084 for freebsd-current-outgoing; Thu, 16 Apr 1998 14:28:03 -0700 (PDT) (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 VAA09996 for ; Thu, 16 Apr 1998 21:27:54 GMT (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id OAA01210; Thu, 16 Apr 1998 14:24:26 -0700 (PDT) Message-Id: <199804162124.OAA01210@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Andrzej Bialecki cc: freebsd-current@FreeBSD.ORG Subject: Re: Booting issues In-reply-to: Your message of "Thu, 16 Apr 1998 20:54:32 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 16 Apr 1998 14:24:26 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have a suggestion: could we change the messages "Can't find > kernel.conf" etc. to something less scary for the new user? Something like > "Using default config (no /kernel.conf)". General consensus is that the messages are spurious. The defenders of these messages are, however, firmly entrenched. Creating an empty /kernel.conf file is a trivial workaround. > And another issue: some time ago there was very animated discussion about > "/boot.banner". Is this idea being implemented by someone, or it just > died off? There is no space in the current booblocks, and their future is limited. > And yet another (CAM related): does present bootblock allow to use the > "da" instead of "sd"? No, although if you were to submit such a trivial patch to the CAM developers I'm sure they'd accept it. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 14:57:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19416 for freebsd-current-outgoing; Thu, 16 Apr 1998 14:57:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail3.aracnet.com (root@mail3.aracnet.com [205.159.88.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA19375 for ; Thu, 16 Apr 1998 21:57:41 GMT (envelope-from beattie@aracnet.com) Received: from shell2.aracnet.com (beattie@shell2.aracnet.com [205.159.88.20]) by mail3.aracnet.com (8.8.8/8.8.5) with ESMTP id OAA31055; Thu, 16 Apr 1998 14:57:39 -0700 Received: from localhost by shell2.aracnet.com (8.8.7) id OAA14525; Thu, 16 Apr 1998 14:57:38 -0700 Date: Thu, 16 Apr 1998 14:57:38 -0700 (PDT) From: Brian Beattie To: Jim Bryant cc: freebsd-current@FreeBSD.ORG Subject: Re: Help - please... Adaptec 1542 and Exabyte tape problem... In-Reply-To: <199805201806.NAA10019@unix.tfs.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, 20 May 1998, Jim Bryant wrote: > In reply: > > On Wed, 15 Apr 1998, Tom wrote: > > > > > > > > On Thu, 16 Apr 1998, Kerry Morse wrote: > > > > > > > Apr 16 13:35:05 proxy /kernel: aha0: DMA beyond end Of ISA: 0x357cd10 > > > > > > Bounce buffers are required to DMA above the 16MB for ISA devices. > > > However, bounce buffers do not work for the aha driver (it is unclear > > > whether the driver or the bounce buffers are broken). > > > > > crap.. i just sold my 1542cf for this very reason... i was wanting > it to handle low-bandwidth stuff like the CD-ROM, M-O drive, and DDS-2 > tape drive, but I kept getting the above messages... now i've got a > heck of a lot of stuff hanging off my 2940UW... i of course have > 'OPTION BOUNCE_BUFFERS' in my config... > I may be mistaken but I believe that the 2940UW is a PCI card. That being the case it does not require bounce buffers. The 2940UW is already supported by the CAM code. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 15:29:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27868 for freebsd-current-outgoing; Thu, 16 Apr 1998 15:29:32 -0700 (PDT) (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 WAA27823 for ; Thu, 16 Apr 1998 22:29:21 GMT (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id PAA01446; Thu, 16 Apr 1998 15:25:51 -0700 (PDT) Message-Id: <199804162225.PAA01446@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Luigi Rizzo cc: current@FreeBSD.ORG Subject: Re: Diskless configuration... In-reply-to: Your message of "Thu, 16 Apr 1998 19:15:01 +0200." <199804161715.TAA07192@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 16 Apr 1998 15:25:50 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > [not sure this is relevant to -current, but since the noise on -hackers > is so high...] > > At http://www.iet.unipi.it/~luigi/diskless.html , I have put up a > short description of the strategy I used to support two labs of > diskless FreeBSD workstation booting from the same server using a > shared readonly root and /usr partition. > > The description also includes most if not all of the files I have used > to configure my machines. > > I'd like to receive suggestions and comments on the architecture > i have devised, to see if there is some better approach. Hmm. See also: http://www.freebsd.org/~msmith/FTL/appnotes/1000.R-BOOTP_TFTP http://www.freebsd.org/~msmith/FTL/appnotes/1010.P-DISKLESS I haven't completed the RARP/BOOTPARAM appnote yet; being less relevant to FreeBSD systems it's a lower priority. -- \\ 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 Apr 16 16:06:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA06257 for freebsd-current-outgoing; Thu, 16 Apr 1998 16:06:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from jraynard.demon.co.uk (jraynard.demon.co.uk [158.152.42.77]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA06146 for ; Thu, 16 Apr 1998 23:05:23 GMT (envelope-from fcurrent@jraynard.demon.co.uk) Received: (from fcurrent@localhost) by jraynard.demon.co.uk (8.8.8/8.8.8) id WAA02722; Thu, 16 Apr 1998 22:12:57 +0100 (BST) (envelope-from fcurrent) Message-ID: <19980416221256.50848@jraynard.demon.co.uk> Date: Thu, 16 Apr 1998 22:12:56 +0100 From: James Raynard To: Anatoly Vorobey Cc: current@FreeBSD.ORG Subject: Re: Spelling etc. Reply-To: chat@FreeBSD.ORG References: <35329CF4.65DE8E18@hdz-ima.rwth-aachen.de> <19980416135716.36703@techunix.technion.ac.il> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <19980416135716.36703@techunix.technion.ac.il>; from Anatoly Vorobey on Thu, Apr 16, 1998 at 01:57:16PM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Followups to -chat] On Thu, Apr 16, 1998 at 01:57:16PM +0300, Anatoly Vorobey wrote: > You, Gerald Heinig, were spotted writing this on Tue, Apr 14, 1998 at 01:17:09AM +0200: > > > > Its cold today (ie. It is cold today) Yep, we don't usually get snow in mid-April here... > Well, a few weeks ago I sent a send-pr with a diff attached > that eliminated _all_ its/it's mistakes in the kernel source > (there were about 70 of them). Nothing resulted; I still hope > someone would deal with it. It's in my pile of things to look at, but there are a lot of things ahead of it... James To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 17:08:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA22359 for freebsd-current-outgoing; Thu, 16 Apr 1998 17:08:04 -0700 (PDT) (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 AAA22277 for ; Fri, 17 Apr 1998 00:08:00 GMT (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA19165; Thu, 16 Apr 1998 16:57:46 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd019159; Thu Apr 16 23:57:42 1998 Message-ID: <353699BD.ABD322C@whistle.com> Date: Thu, 16 Apr 1998 16:52:29 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: current@FreeBSD.ORG, Kenjiro Cho Subject: Networking strategy for -current Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG One of the things that has been apparent is that FreeBSD is being used more and more as a firewall and router for people with special networking requirements. The networking code however is getting old, and needs work in various places. many people are also using it for experimentation. One usage that people have often asked for is the ability to allocate bandwidth, and to re-visit the queuing strategies we use. Sony labs have recently announced their ALTQ package in a new release. I would like to find out from the people involved in networking, what the general consensus would be to our integrating this into -current. (under #ifdefs of course) I would envision that this would be done in a few steps. 1/ the framework for selecting alternate queueing schemes for intefaces could be integrated as a separate unit. It allows a queueing module to supply methods which would be used for queueing. A slightly more generic method than that used by Sony would allow queueing methods to be LKMs if needed. I'm pretty sure that this can be done as a compile parameter (as sony have done) that would leave the system still stable and effectively unaltered in the 'compiled out' case. 2/ The CBQ method Sony supply has it's own packet classifier that is basically a duplicate of the IPFW or ipfilter classifiers. It might be worth us looking to see if the IPFW (or ipfilter) code can be used to do this. I would do this by expanding the mbuf pkthdr field to contain a pointer to some meta-data such as 'traffic class'. This could be set by each protocol in any way that makes sense to it. (e.g. by a new IPFW command) (instead of a special pass). 3/ the methods that Sony supply are basically independent modules and could be added as independent modules. THey are only turned on on a -per interface- basis when requested so POLA is preserved. The ability of FreeBSD to handle various data streams in a prioritised and stable manner would be of great value to a lot of users.. (imagine if your FTP server didn't make your telnet sessions grind to a stop). This is just a first thought on this topic. I'm looking for feedback. At least I'd like to see the altq FRAMEWORK added even if the specific methods and more esoteric methods and control programs may not be immediatly added. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 17:18:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA24408 for freebsd-current-outgoing; Thu, 16 Apr 1998 17:18:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from phoenix.volant.org (phoenix.volant.org [205.179.79.193]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA24361 for ; Fri, 17 Apr 1998 00:18:29 GMT (envelope-from patl@phoenix.volant.org) From: patl@phoenix.volant.org Received: from asimov.phoenix.volant.org [205.179.79.65] by phoenix.volant.org with smtp (Exim 1.62 #1) id 0yPyrL-0002oK-00; Thu, 16 Apr 1998 17:18:27 -0700 Received: from localhost by asimov.phoenix.volant.org (SMI-8.6/SMI-SVR4) id RAA10067; Thu, 16 Apr 1998 17:16:33 -0700 Date: Thu, 16 Apr 1998 17:16:33 -0700 (PDT) Reply-To: patl@phoenix.volant.org Subject: Re: Digitally Signed Messages To: "Scot W. Hetzel" cc: current@FreeBSD.ORG In-Reply-To: <006801bd6947$ea64a1e0$c3e0d9cf@admin.westbend.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 > -----Original Message----- > From: Andrew Reilly > > >Methinks your mailer is broken: > > > >>X-Mailer: Microsoft Outlook Express 4.72.2106.4 > >>X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 > > > > My Mailer isn't broken, I just wasn't expecting it from this list. And the > extra steps I had to take to read the message. If it requires annoying extra steps, it IS broken. Complain to the vendor and/or switch mailers. > The real question is does Digitally Signed Messages, and HTML belong on a > Mailing list? Absolutely NOT. Half right. HTML doesn't add any useful information, and obscures the body of the message when view in non-HTML-aware MUAs. But Digital Signatures DO add useful information, namely a verification that the message is not a forgery and has not been tampered with. (Within whatever trust level you assign to that particular key.) This is just as useful in a mailing list as it is in a private discussion. Possibly more so, since the exposure to potential forgers is greater. -Pat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 17:22:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25239 for freebsd-current-outgoing; Thu, 16 Apr 1998 17:22:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlogic.com.au [203.36.2.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA25223 for ; Fri, 17 Apr 1998 00:22:15 GMT (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.5/8.8.7) id KAA00609; Fri, 17 Apr 1998 10:21:09 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199804170021.KAA00609@cimlogic.com.au> Subject: Re: Networking strategy for -current In-Reply-To: <353699BD.ABD322C@whistle.com> from Julian Elischer at "Apr 16, 98 04:52:29 pm" To: julian@whistle.com (Julian Elischer) Date: Fri, 17 Apr 1998 10:21:08 +1000 (EST) Cc: current@FreeBSD.ORG, kjc@csl.sony.co.jp 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 Julian Elischer wrote: > The ability of FreeBSD to handle various data streams in a > prioritised and stable manner would be of great value to a > lot of users.. (imagine if your FTP server didn't make your > telnet sessions grind to a stop). That would be neat. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 17:58:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA02602 for freebsd-current-outgoing; Thu, 16 Apr 1998 17:58:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA02531 for ; Fri, 17 Apr 1998 00:58:07 GMT (envelope-from grog@lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id KAA18774; Fri, 17 Apr 1998 10:27:38 +0930 (CST) (envelope-from grog) Message-ID: <19980417102737.G1090@freebie.lemis.com> Date: Fri, 17 Apr 1998 10:27:37 +0930 From: Greg Lehey To: Nathan Dorfman , Michael Class Cc: "Scot W. Hetzel" , current@FreeBSD.ORG Subject: Re: Digitally Signed Messages (Re: HEADS UP: CAM cutover in two weeks.) References: <05cb01bd6899$6e0135e0$c3e0d9cf@admin.westbend.net> <19980416133939.F1090@freebie.lemis.com> <3535A5EB.E6B6E281@hp.com> <19980416093514.34787@rtfm.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19980416093514.34787@rtfm.net>; from Nathan Dorfman on Thu, Apr 16, 1998 at 09:35:14AM -0400 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 Thu, 16 April 1998 at 9:35:14 -0400, Nathan Dorfman wrote: > On Thu, Apr 16, 1998 at 08:32:11AM +0200, Michael Class wrote: >> I think I caused the discussion :-( Iam sorry, I just have the digitial >> signing (with X.509 Certificates, done by Netscape Communicator-Mailer) >> switched on as default, and forgot to switch it of for the message to >> this list. I apologize! >> >> The reason why I have switched it on by default is that I want to get >> people in discussions about digital signing, so that more and more >> people will understand how that works in the future. >> >> Btw: A digital signed message is just a MIME-Message with an attachment >> that has the Hash digital encrypted. Do you think that it is evil to use >> MIME-Messages on a mailinglist these days? > > Does this mean that PGP is truly dead? Not at all. It does rather raise the question as to whether it should be used to sign mail messages, though. Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 18:10:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05666 for freebsd-current-outgoing; Thu, 16 Apr 1998 18:10:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.westbend.net (ns1.westbend.net [207.217.224.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA05661 for ; Fri, 17 Apr 1998 01:10:19 GMT (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [207.217.224.195]) by mail.westbend.net (8.8.8/8.8.8) with SMTP id UAA18762 for ; Thu, 16 Apr 1998 20:10:18 -0500 (CDT) (envelope-from hetzels@westbend.net) Message-ID: <00d401bd699d$e82d3260$c3e0d9cf@admin.westbend.net> From: "Scot W. Hetzel" To: Subject: Re: Digitally Signed Messages Date: Thu, 16 Apr 1998 20:12:35 -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.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----Original Message----- From: patl@phoenix.volant.org >If it requires annoying extra steps, it IS broken. Complain >to the vendor and/or switch mailers. > Ok, maybe it is broken if I have to do the extra step. >> The real question is does Digitally Signed Messages, and HTML belong on a >> Mailing list? Absolutely NOT. > >Half right. HTML doesn't add any useful information, and obscures >the body of the message when view in non-HTML-aware MUAs. But >Digital Signatures DO add useful information, namely a verification >that the message is not a forgery and has not been tampered with. >(Within whatever trust level you assign to that particular key.) >This is just as useful in a mailing list as it is in a private >discussion. Possibly more so, since the exposure to potential >forgers is greater. > Ok, maybe they do have there place on the list, but only when sending a patch to the list, not when posting/replying to complain/suggest improvements to current. For Example: 1. Poster complains current is broken and no suggested fix (Doesn't require a Digital Signature) 2. Poster advises/replies current is broken and suggests a fix (Include a Digital Signature, that way we know who to congratulate/blame when it does/doesn't work.) ;-) Now if people would think, (Does my message really require a Digital Signature?), before posting. Any ways, thanks for your time. This will be my last post on the subject. Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 18:27:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08884 for freebsd-current-outgoing; Thu, 16 Apr 1998 18:27:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from usr06.primenet.com (tlambert@usr06.primenet.com [206.165.6.206]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA08850 for ; Fri, 17 Apr 1998 01:27:33 GMT (envelope-from tlambert@usr06.primenet.com) Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id SAA00859; Thu, 16 Apr 1998 18:27:12 -0700 (MST) From: Terry Lambert Message-Id: <199804170127.SAA00859@usr06.primenet.com> Subject: Re: Digitally Signed Messages To: patl@phoenix.volant.org Date: Fri, 17 Apr 1998 01:27:11 +0000 (GMT) Cc: hetzels@westbend.net, current@FreeBSD.ORG In-Reply-To: from "patl@phoenix.volant.org" at Apr 16, 98 05:16:33 pm 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 > Half right. HTML doesn't add any useful information, and obscures > the body of the message when view in non-HTML-aware MUAs. But > Digital Signatures DO add useful information, namely a verification > that the message is not a forgery and has not been tampered with. > (Within whatever trust level you assign to that particular key.) > This is just as useful in a mailing list as it is in a private > discussion. Possibly more so, since the exposure to potential > forgers is greater. Digital signatures require an out-of-band courier or a Diffie-Helman key exchange or a central ceritificate authority that verifies the identity of the sender by chking their physical ID before signing the certificate. The problem with the certificates generally used in mailing lists is that they are not sufficiently verifiable that they can be used as identification, which is how their senders are pretending they can be used. Basically, they are subject to man-in-the-middle attacks. This means that they are generally worthless clutter. The VeriSign "personal certificates" are not usable because the certificate authority, Verisign, will not vouch for the identity of the user. An interesting side point: The X.509 ceritificate that you sent is invalid for signing email. It has a number of fields that are not compliant with X.509, and the "mail" bit is zero. And no, I refuse to become a certificate authority. 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 18:36:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10663 for freebsd-current-outgoing; Thu, 16 Apr 1998 18:36:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from aldan.ziplink.net (mi@kot.ne.mediaone.net [24.128.29.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA10566 for ; Fri, 17 Apr 1998 01:35:58 GMT (envelope-from mi@rtfm.ziplink.net) Received: from rtfm.ziplink.net (rtfm [199.232.255.52]) by aldan.ziplink.net (8.8.8/8.8.7) with ESMTP id BAA05527 for ; Fri, 17 Apr 1998 01:35:49 GMT (envelope-from mi@rtfm.ziplink.net) Received: (from mi@localhost) by rtfm.ziplink.net (8.8.8/8.8.5) id VAA11058 for current@freebsd.org; Thu, 16 Apr 1998 21:35:48 -0400 (EDT) From: Mikhail Teterin Message-Id: <199804170135.VAA11058@rtfm.ziplink.net> Subject: Re: Networking strategy for -current In-Reply-To: <353699BD.ABD322C@whistle.com> from "Julian Elischer" at "Apr 16, 98 04:52:29 pm" To: current@FreeBSD.ORG Date: Thu, 16 Apr 1998 21:35:48 -0400 (EDT) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10965 for freebsd-current-outgoing; Thu, 16 Apr 1998 18:37:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from goliath.camtech.com.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA10960 for ; Fri, 17 Apr 1998 01:37:39 GMT (envelope-from thyerm@camtech.net.au) Received: from camtech.net.au (dialup-ad-6-07.camtech.net.au [203.28.0.199]) by goliath.camtech.com.au (8.8.5/8.8.2) with ESMTP id LAA08322; Fri, 17 Apr 1998 11:04:43 +0930 (CST) Message-ID: <3536B24B.AF3DBB0D@camtech.net.au> Date: Fri, 17 Apr 1998 11:07:15 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.05 [en] (X11; U; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Andreas Braukmann CC: freebsd-current@FreeBSD.ORG Subject: Re: 'fatal trap 12' on boot (smp and up) References: <19980415202740.43100@paert.tse-online.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I also get the same crash if *and only if* I boot FreeBSD using FBSDBOOT.EXE from DOS (I have multiple OS's on my disk). The answer for me was to re-install my normal bootblock 'BootEasy' which had been lost when I recently re-installed Windows 95. I found that I could successfully boot my kernel built from CTM src-cur 3287 sources (~Mar 22 which *does* include options VM86). Also I could boot a new kernel I made without options VM86. By the way my recent-CURRENT kernel I was trying this with is built from CTM src-cur 3325 sources. (~Apr 14) There's something wierd going on. My kernel config file is included below: # $Id: MATTE,v 5.7 1998/04/10 18:02:30 CDT matt Exp $ # based on $Id: LINT,v 1.424 1998/04/09 22:28:57 sos Exp $ # machine "i386" ident "MATTE.3325" maxusers 20 options INCLUDE_CONFIG_FILE # Include this file in kernel config kernel root on wd0 cpu "I586_CPU" options "CPU_DISABLE_5X86_LSSER" # should not be used if you use memory mapped I/O device(s). options "CPU_FASTER_5X86_FPU" # COMPATIBILITY OPTIONS options "COMPAT_43" # Compatible with BSD 4.3 [KEEP THIS!] options USER_LDT # Let processes manipulate their local descriptor table (needed for WINE) options SYSVSHM # Enable SYSV style shared memory options SYSVSEM # Enable SYSV style semaphores options SYSVMSG # Enable SYSV style message queues options "MD5" # Include a MD5 routine in the kernel options "VM86" # Allow processes to switch to vm86 mode (needed for doscmd) # DEBUGGING OPTIONS options DDB # Enable the kernel debugger options UCONSOLE # Allow users to grab the console options USERCONFIG # boot -c editor options VISUAL_USERCONFIG # visual boot -c editor # NETWORKING OPTIONS options INET # Internet communications protocols pseudo-device ether # Generic Ethernet pseudo-device loop # Network loopback device pseudo-device tun 1 # Tunnel driver(user process ppp) # FILESYSTEM OPTIONS # The ones I have commented out will autoload when required options SOFTUPDATES # You bet! options FFS # Berkeley Fast Filesystem options NFS # Network Filesystem options "CD9660" # ISO 9660 Filesystem options MFS # Memory Filesystem options MSDOSFS # MSDOS Filesystem options PROCFS # Process Filesystem options NSWAPDEV=4 # Allow this many swap-devices controller pci0 controller ncr0 # My card set for termination and using IRQ 11 # SCSI DEVICE CONFIGURATION controller scbus0 at ncr0 # Base SCSI code disk sd0 at scbus0 target 0 disk sd1 at scbus0 target 1 disk sd2 at scbus0 target 2 disk sd3 at scbus0 target 3 disk sd4 at scbus0 target 4 disk sd5 at scbus0 target 5 disk sd6 at scbus0 target 6 # MISCELLANEOUS DEVICES AND OPTIONS pseudo-device pty 32 # Pseudo ttys - can go as high as 256 pseudo-device gzip # Exec gzipped a.out's pseudo-device vn # Vnode driver (turns a file into a device) pseudo-device ccd 4 # Concatenated disk driver # HARDWARE DEVICE CONFIGURATION controller isa0 options "AUTO_EOI_1" # Save 0.7-1.25 usec for each interrupt controller pnp0 # Enable PnP support in the kernel options XSERVER # Include code for XFree86 device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr options MAXCONS=12 # number of virtual consoles options SC_HISTORY_SIZE=200 # number of history buffer lines device npx0 at isa? port "IO_NPX" iosiz 0x0 flags 0x0 irq 13 vector npxintr options "CMD640" # Enable work around for CMD640 h/w bug controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0xb0ffb0ff vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 flags 0xb0ffb0ff 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 driver 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 tape ft0 at fdc0 drive 2 device lpt0 at isa? port? tty irq 7 vector lptintr device sio0 at isa? port "IO_COM1" tty flags 0x10 irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device ed0 at isa? port 0x300 net irq 9 iomem 0xd8000 vector edintr controller snd0 device sb0 at isa? port 0x220 irq 5 drq 1 vector sbintr device sbxvi0 at isa? drq 5 device sbmidi0 at isa? port 0x330 device joy0 at isa? port "IO_GAME" Andreas Braukmann wrote: > > Hello, > > I was running (quit happily) -current from late November '97 with > an smp-enabled kernel. > I updated my sources to 98/04/06 and waited a few days for > 'alarm' and 'heads up'-messages on -current. > Yesterday I made the world, installed the world and made my kernel > based on my old kernel-configuration (just deleted the outdated 'log' > pseudo-device). > > The new kernel traps on boot immediatly (after it's loaded). > This happens to both - the smp-enabled and the normal uni-proc. kernel. > (same config, just without smp). > > The hardware: > * Gigabyte 686DX Dual PPro 200 > * Award BIOS > * 128 MB Ram > > The trap: (from the uni-proc. kernel, cited from hand-written notes) > Fatal trap 12: page fault while in vm86 mode > fault virtual address: 0x26e0 > fault code: user read, page not present > ip = 0x24a:0x240 > sp = 0x0:0xff8 > fp = 0x0:0x0 > cs = base 0xf0000008, limit 0xd14c8, type 0xf > DPL 0, pres 1, def 32 0, gran 0 > proc eflags = trace trap, int enabled, resume, vm86, IOPL=0 > cur proc = idle > int mask = net tty bio cam > > I even made a 'config -g' up-kernel, but a 'trace'-command > in the kernel-debugger didn't spit out anything that seemed very > useful to me (I'm a non-kernel hacker ...), just something about > 'xxxx DYNAMIC xxxx'. > > The trap appears at exactly the same addresse for the smp and the up-case. > > Any hints? > > Thanks, > 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 -- /=====================================================================\ |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 Thu Apr 16 18:40:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11851 for freebsd-current-outgoing; Thu, 16 Apr 1998 18:40:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from goliath.camtech.com.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA11844 for ; Fri, 17 Apr 1998 01:40:22 GMT (envelope-from thyerm@camtech.net.au) Received: from camtech.net.au (dialup-ad-6-07.camtech.net.au [203.28.0.199]) by goliath.camtech.com.au (8.8.5/8.8.2) with ESMTP id LAA08645; Fri, 17 Apr 1998 11:07:21 +0930 (CST) Message-ID: <3536B2E9.6E686EC0@camtech.net.au> Date: Fri, 17 Apr 1998 11:09:53 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.05 [en] (X11; U; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Jonathan Lemon CC: Andreas Braukmann , freebsd-current@FreeBSD.ORG Subject: Re: 'fatal trap 12' on boot (smp and up) References: <19980415202740.43100@paert.tse-online.de> <19980415141155.44599@right.PCS> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Any reason why it should work from BootEasy but not from FBSDBOOT ?? Andreas, how were you booting ? Jonathan Lemon wrote: > > On Apr 04, 1998 at 08:27:40PM +0200, Andreas Braukmann wrote: > > The hardware: > > * Gigabyte 686DX Dual PPro 200 > > * Award BIOS > > * 128 MB Ram > > > > The trap: (from the uni-proc. kernel, cited from hand-written notes) > > Fatal trap 12: page fault while in vm86 mode > > fault virtual address: 0x26e0 > > fault code: user read, page not present > > ip = 0x24a:0x240 > > sp = 0x0:0xff8 > > fp = 0x0:0x0 > > cs = base 0xf0000008, limit 0xd14c8, type 0xf > > DPL 0, pres 1, def 32 0, gran 0 > > proc eflags = trace trap, int enabled, resume, vm86, IOPL=0 > > cur proc = idle > > int mask = net tty bio cam > > This is the VM86 memory sizing code on bootup; it is trying to coax the > BIOS to tell it how much memory is in the machine. The BIOS routines > are supposed to be at 0xA0000, for some reason, your machine is trying > to execute code at 0x26e0. This fails, since I haven't mapped that > particular page page into the address space. > > Do you have `BIOS shadowing' set in your BIOS? Try turning if off, if so. > > For a quick workaround, you can just take out "options VM86" from > the kernel, but I'd really like to try to get this fixed. > -- > Jonathan > > 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 Thu Apr 16 18:43:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA12915 for freebsd-current-outgoing; Thu, 16 Apr 1998 18:43:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from engulf.com (brandon@engulf.com [207.96.124.102]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA12866 for ; Fri, 17 Apr 1998 01:42:58 GMT (envelope-from brandon@engulf.com) Received: from localhost (brandon@localhost) by engulf.com (8.8.8/8.8.7) with SMTP id VAA04507 for ; Thu, 16 Apr 1998 21:39:33 -0400 (EDT) Date: Thu, 16 Apr 1998 21:39:33 -0400 (EDT) From: Brandon Lockhart To: current@FreeBSD.ORG Subject: Problems w/ Linux EMU In-Reply-To: <199804170135.VAA11058@rtfm.ziplink.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 I am running FreeBSD 3.0-Current last updated on Sunday. For some strange reason, my Linux EMU is having problems. (It doesn't recognize the ELF binary type). Any clue why this is happening? ,----------------------. | Brandon Lockhart | `----------,-----------'------------. | brandon@engulf.com | `------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 19:05:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA16864 for freebsd-current-outgoing; Thu, 16 Apr 1998 19:05:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA16856 for ; Fri, 17 Apr 1998 02:05:42 GMT (envelope-from andrew@zeta.org.au) Received: from gurney.reilly.home (d24.syd2.zeta.org.au [203.26.11.24]) by godzilla.zeta.org.au (8.8.7/8.8.7) with ESMTP id MAA11906; Fri, 17 Apr 1998 12:01:55 +1000 Received: (from andrew@localhost) by gurney.reilly.home (8.8.8/8.8.5) id JAA06765; Fri, 17 Apr 1998 09:10:56 +1000 (EST) From: Andrew Reilly Message-Id: <199804162310.JAA06765@gurney.reilly.home> Date: Fri, 17 Apr 1998 09:10:56 +1000 (EST) Subject: Re: Digitally Signed Messages (Re: HEADS UP: CAM cutover in two wee ks.) To: hetzels@westbend.net cc: reilly@zeta.org.au, michael_class@hp.com, current@FreeBSD.ORG In-Reply-To: <006801bd6947$ea64a1e0$c3e0d9cf@admin.westbend.net> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 16 Apr, Scot W. Hetzel wrote: > > My Mailer isn't broken, I just wasn't expecting it from this list. And the > extra steps I had to take to read the message. And I was just saying that most of the mailers that I've encountered do not require extra steps to read the message, and so I concluded that one that does must be broken by design. > The real question is does Digitally Signed Messages, and HTML belong on a > Mailing list? Absolutely NOT. HTML is a bit irksome (at the moment---I can see it becoming more and more acceptable with time), but I fail to see how message signing is a nuissance to anyone. Ultimately, I expect all e-mail to be digitally signed by default. -- Andrew "The steady state of disks is full." -- Ken Thompson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 19:06:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA17082 for freebsd-current-outgoing; Thu, 16 Apr 1998 19:06:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA17074 for ; Fri, 17 Apr 1998 02:06:06 GMT (envelope-from andrew@zeta.org.au) Received: from gurney.reilly.home (d24.syd2.zeta.org.au [203.26.11.24]) by godzilla.zeta.org.au (8.8.7/8.8.7) with ESMTP id MAA11907; Fri, 17 Apr 1998 12:01:57 +1000 Received: (from andrew@localhost) by gurney.reilly.home (8.8.8/8.8.5) id JAA06772; Fri, 17 Apr 1998 09:15:32 +1000 (EST) From: Andrew Reilly Message-Id: <199804162315.JAA06772@gurney.reilly.home> Date: Fri, 17 Apr 1998 09:15:31 +1000 (EST) Subject: Re: Digitally Signed Messages (Re: HEADS UP: CAM cutover in two wee ks.) To: grog@lemis.com cc: reilly@zeta.org.au, hetzels@westbend.net, michael_class@hp.com, current@FreeBSD.ORG In-Reply-To: <19980416162753.I1090@freebie.lemis.com> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 16 Apr, Greg Lehey wrote: > On Thu, 16 April 1998 at 10:05:20 +1000, Andrew Reilly wrote: >> On 15 Apr, Scot W. Hetzel wrote: >>> X-Mailer: Microsoft Outlook Express 4.72.2106.4 >>> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 > > Just because it's Outlook? No. I've never used Outlook, but I've been biassed against Microsoft's e-mail products by the obnoxious things all of the previous versions have done to me over the years. My original comment was intended to suggest that a mailer that did not handle digital signatures in a way that is convenient for the recipient must be broken by design. Note that convenient handling can legitimately include ignoring it altogether, or tagging it as an unrecognised MIME attachment. -- Andrew "The steady state of disks is full." -- Ken Thompson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 19:18:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA19473 for freebsd-current-outgoing; Thu, 16 Apr 1998 19:18:12 -0700 (PDT) (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 CAA19340 for ; Fri, 17 Apr 1998 02:17:47 GMT (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id KAA24737; Fri, 17 Apr 1998 10:14:53 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199804170214.KAA24737@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Kerry Morse cc: "Justin T. Gibbs" , Tom , current@FreeBSD.ORG Subject: Re: Help - please... Adaptec 1542 and Exabyte tape problem... In-reply-to: Your message of "Thu, 16 Apr 1998 21:15:37 +1000." <02B01380C828D1119ED70020AF641C53068558@MTTMail.metro.tas.gov.au> Date: Fri, 17 Apr 1998 10:14:52 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kerry Morse wrote: > > Thanks for the help... > > > So basically it's not going to work for at least a while or a few fixes > so swapping the controller out over with a PCI controller while no ones > looking is my best solution at present... I've just found a whole mess of bounce buffer bitrot in the existing scsi code and applied some bandaids. I can't test some of the more obscure drivers, but an aha1542B + sd0/sd1/st0/cd0 now seems to work fine. Before, talking to the tape would fail 50% of the time at startup. Ironically, I think I to blame for a good chunk of the original breakage. The scsi base code (scsi_scsi_cmd() specifically) had some patchwork to detect data transfers to/from the per-process kernel stack and how to manually bounce them. When I moved the kernel stack out of user space last year some time, the glue code that checked for requests on the kstack no longer worked as it used assumptions about the VM space layout that were no longer true. However, there was bitrot in other drivers too, notably worm, ch and st. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 19:28:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA21323 for freebsd-current-outgoing; Thu, 16 Apr 1998 19:28:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from home.dragondata.com (toasty@home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA21313 for ; Fri, 17 Apr 1998 02:28:10 GMT (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id VAA20582; Thu, 16 Apr 1998 21:26:15 -0500 (CDT) From: Kevin Day Message-Id: <199804170226.VAA20582@home.dragondata.com> Subject: Re: Networking strategy for -current In-Reply-To: <199804170021.KAA00609@cimlogic.com.au> from John Birrell at "Apr 17, 98 10:21:08 am" To: jb@cimlogic.com.au (John Birrell) Date: Thu, 16 Apr 1998 21:26:14 -0500 (CDT) Cc: julian@whistle.com, current@FreeBSD.ORG, kjc@csl.sony.co.jp 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: > > The ability of FreeBSD to handle various data streams in a > > prioritised and stable manner would be of great value to a > > lot of users.. (imagine if your FTP server didn't make your > > telnet sessions grind to a stop). > > That would be neat. > Imagine if one lame shell user couldn't spew 3mb/sec out my pipe, killing my router, and my uplink's router? :) And imagine if I could do this without messing with conversation limits on my router? :) Where do I send the check? Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 20:37:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA04270 for freebsd-current-outgoing; Thu, 16 Apr 1998 20:37:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shadow.worldbank.org (shadow.worldbank.org [138.220.104.78]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA04258 for ; Fri, 17 Apr 1998 03:37:44 GMT (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.8.8/8.8.8) with SMTP id XAA09139; Thu, 16 Apr 1998 23:36:31 -0400 (EDT) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Thu, 16 Apr 1998 23:36:30 -0400 (EDT) From: "Alok K. Dhir" To: brandon@engulf.com cc: current@FreeBSD.ORG Subject: Re: Problems w/ Linux EMU 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 probably need to remake the LKMs and reboot... On Thu, 16 Apr 1998 brandon@engulf.com wrote: > > > I am running FreeBSD 3.0-Current last updated on Sunday. For some strange > reason, my Linux EMU is having problems. (It doesn't recognize the ELF > binary type). Any clue why this is happening? > > > ,----------------------. > | Brandon Lockhart | > `----------,-----------'------------. > | brandon@engulf.com | > `------------------------' > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -------------------------------------------------------------------- \||/_ Alok K. Dhir Phone: +1.202.473.2446 oo \ S13-061, ISGMC Email: adhir@worldbank.org L_ The World Bank Group Washington, DC \/ ------------------------------------------------------------------------| "Unix _is_ user friendly - it just chooses friends selectively..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 20:43:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA05319 for freebsd-current-outgoing; Thu, 16 Apr 1998 20:43:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wcc.wcc.net (wcc.wcc.net [208.6.232.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA05293; Fri, 17 Apr 1998 03:43:15 GMT (envelope-from piquan@wcc.wcc.net) Received: from detlev.UUCP (tnt248.wcc.net [208.10.139.248]) by wcc.wcc.net (8.8.8/8.8.8) with ESMTP id WAA06101; Thu, 16 Apr 1998 22:38:28 -0500 (CDT) Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id WAA00898; Wed, 15 Apr 1998 22:42:32 -0500 (CDT) (envelope-from joelh) Date: Wed, 15 Apr 1998 22:42:32 -0500 (CDT) Message-Id: <199804160342.WAA00898@detlev.UUCP> To: sos@FreeBSD.ORG CC: ken@plutotech.com, michael_class@hp.com, mike@smith.net.au, current@FreeBSD.ORG In-reply-to: <199804151057.MAA03641@sos.freebsd.dk> (message from Søren Schmidt on Wed, 15 Apr 1998 12:57:40 +0200 (MEST)) Subject: Re: HEADS UP: CAM cutover in two weeks. From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199804151057.MAA03641@sos.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Lets stick to the passthrough driver and use cdrecord or semilar. I'm > currently working on getting an ATAPI CDRW drive working, and have > more or less given up on using the worm-type interface, it just > doesn't fit for modern (MMC compliant) drives. > And yes I plan to get ATAPI support in under the SCSI system whatever > it might be. I haven't tracked down the problem yet, but my Philips CDR2600 works only under wormcontrol/dd, not under cdrecord... locks up either the drive or the SCSI bus, depending on the number of crickets in the apartment. I don't have time or knowledge to port our worm driver, but would like to know if somebody else is doing it. Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 20:54:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA08932 for freebsd-current-outgoing; Thu, 16 Apr 1998 20:54:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wcc.wcc.net (wcc.wcc.net [208.6.232.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA08761 for ; Fri, 17 Apr 1998 03:53:49 GMT (envelope-from piquan@wcc.wcc.net) Received: from detlev.UUCP (tnt248.wcc.net [208.10.139.248]) by wcc.wcc.net (8.8.8/8.8.8) with ESMTP id WAA07057; Thu, 16 Apr 1998 22:49:01 -0500 (CDT) Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id WAA01213; Wed, 15 Apr 1998 22:53:09 -0500 (CDT) (envelope-from joelh) Date: Wed, 15 Apr 1998 22:53:09 -0500 (CDT) Message-Id: <199804160353.WAA01213@detlev.UUCP> To: dag-erli@ifi.uio.no CC: current@FreeBSD.ORG In-reply-to: (dag-erli@ifi.uio.no) Subject: Re: syscons.c and graphical screensavers From: Joel Ray Holveck Reply-to: joelh@gnu.org References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [following up to -current] > I changed current's src/sys/i386/isa/syscons.c to put the "should we > stop the screensaver" check before the "should we just return" check. > This will make graphical screensavers possible - but BE WARNED that to > the best of my knowledge syscons.c still does not handle console > switches properly when a graphical screensaver is active, especially > not switches to whichever console X is using. I'll see to that RSN. The screensaver needs to properly handle shutdown before the switch, but that's not hard. If you're writing a graphical screensaver, talk to me and I'll get you my template. -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 21:37:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15240 for freebsd-current-outgoing; Thu, 16 Apr 1998 21:37:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sumatra.americantv.com (sumatra.americantv.com [207.170.17.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA15234 for ; Fri, 17 Apr 1998 04:37:49 GMT (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id XAA28508; Thu, 16 Apr 1998 23:37:33 -0500 (CDT) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id XAA01056; Thu, 16 Apr 1998 23:37:02 -0500 Message-ID: <19980416233701.05315@right.PCS> Date: Thu, 16 Apr 1998 23:37:01 -0500 From: Jonathan Lemon To: Matthew Thyer Cc: Andreas Braukmann , freebsd-current@FreeBSD.ORG Subject: Re: 'fatal trap 12' on boot (smp and up) References: <19980415202740.43100@paert.tse-online.de> <3536B24B.AF3DBB0D@camtech.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: <3536B24B.AF3DBB0D@camtech.net.au>; from Matthew Thyer on Apr 04, 1998 at 11:07:15AM +0930 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Apr 04, 1998 at 11:07:15AM +0930, Matthew Thyer wrote: > I also get the same crash if *and only if* I boot FreeBSD using > FBSDBOOT.EXE from DOS (I have multiple OS's on my disk). Okay, that makes sense. The startup code tries making some INTn calls to size memory. If DOS happens to hook the interrupt vector, then the INTn call will try to jump to what it thinks is a DOS routine in low memory, which fails. Hmm. I'm not sure what the best solution for this is. > The answer for me was to re-install my normal bootblock 'BootEasy' > which had been lost when I recently re-installed Windows 95. That works, since it doesn't patch the real-mode interrupt vectors. > I found that I could successfully boot my kernel built from CTM > src-cur 3287 sources (~Mar 22 which *does* include options VM86). I put the new changes in on Mar 23rd... -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 22:00:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA18094 for freebsd-current-outgoing; Thu, 16 Apr 1998 22:00:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA18058; Fri, 17 Apr 1998 05:00:04 GMT (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id EAA17376; Fri, 17 Apr 1998 04:59:15 GMT Date: Fri, 17 Apr 1998 13:59:14 +0900 (JST) From: Michael Hancock To: freebsd-current@FreeBSD.ORG cc: freebsd-fs@FreeBSD.ORG Subject: Updated vfs 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 I've separated the layering fixes and the VFS_VRELE framework into separate projects. Here is an updated patch for making *both* refcounting and locking of vnodes reflexive using the current framework. http://www.freebsd.org/~mch/vop1a.diff For a testing tool see http://www.freebsd.org/~mch Some things I should note in this patch are listed below: 1) In the original code, ext2_rmdir and msdosfs_rmdir release the lock across the truncate call but ufs_rmdir doesn't. The ufs_rmdir implementation make it clean for me because I just delete the vput(), but in ext2_rmdir and msdosfs_rmdir I must reacquire the lock so the generic layer can do the vput() (phew!). I'm not sure if we should be holding a lock across truncate and I have yet to review the logs yet to see why. Perhaps someone can shed some light on this. 2) In the union filesystem, there are a also a few case where I have to reacquire the lock. However, it appears that there is an invariant that says if the upper vnode is held by me I can "diddle with the union vnode locking state at will", see UN_KLOCK and UN_ULOCK. I take advantage of this and reacquire the lock by just twiddling a bit instead of calling vn_lock(). Otherwise, this patch consists of mostly deleting vrele and vput calls in underlying filesystems and moving them to the generic layer. Regards, Mike Hancock To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 22:24:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA22186 for freebsd-current-outgoing; Thu, 16 Apr 1998 22:24:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA22156; Fri, 17 Apr 1998 05:24:28 GMT (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id FAA17520; Fri, 17 Apr 1998 05:23:40 GMT Date: Fri, 17 Apr 1998 14:23:40 +0900 (JST) From: Michael Hancock To: freebsd-current@FreeBSD.ORG cc: freebsd-fs@FreeBSD.ORG Subject: Re: Updated vfs patches 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, 17 Apr 1998, Michael Hancock wrote: > http://www.freebsd.org/~mch/vop1a.diff > > 1) In the original code, ext2_rmdir and msdosfs_rmdir release the lock > across the truncate call but ufs_rmdir doesn't. The ufs_rmdir > implementation make it clean for me because I just delete the vput(), but > in ext2_rmdir and msdosfs_rmdir I must reacquire the lock so the generic > layer can do the vput() (phew!). I'm not sure if we should be holding a > lock across truncate and I have yet to review the logs yet to see why. > Perhaps someone can shed some light on this. I found it (POST_SOFTUPDATES)! Do we not block when calling truncate with softupdates on? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 23:11:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA05410 for freebsd-current-outgoing; Thu, 16 Apr 1998 23:11:28 -0700 (PDT) (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 GAA05356; Fri, 17 Apr 1998 06:11:22 GMT (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id WAA28231; Thu, 16 Apr 1998 22:59:08 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd028229; Fri Apr 17 05:59:07 1998 Message-ID: <3536EE71.41C67EA6@whistle.com> Date: Thu, 16 Apr 1998 22:53:53 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: Michael Hancock CC: freebsd-current@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: Updated vfs patches References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Michael Hancock wrote: > > On Fri, 17 Apr 1998, Michael Hancock wrote: > > > http://www.freebsd.org/~mch/vop1a.diff > > > > 1) In the original code, ext2_rmdir and msdosfs_rmdir release the lock > > across the truncate call but ufs_rmdir doesn't. The ufs_rmdir > > implementation make it clean for me because I just delete the vput(), but > > in ext2_rmdir and msdosfs_rmdir I must reacquire the lock so the generic > > layer can do the vput() (phew!). I'm not sure if we should be holding a > > lock across truncate and I have yet to review the logs yet to see why. > > Perhaps someone can shed some light on this. > > I found it (POST_SOFTUPDATES)! Do we not block when calling truncate with > softupdates on? > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message now THAT is a good question...... I basically took the code from kirk's changes and he seemed (from my memory.. I don't have the changes here) to have made that change, so I did too. I'd have to ask kirk WHY he did that and he's out of town for 1 more week. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 23:22:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA07632 for freebsd-current-outgoing; Thu, 16 Apr 1998 23:22:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA07624 for ; Fri, 17 Apr 1998 06:22:27 GMT (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id IAA21912; Fri, 17 Apr 1998 08:22:25 +0200 (CEST) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id IAA09615; Fri, 17 Apr 1998 08:10:53 +0200 (MET DST) Date: Fri, 17 Apr 1998 08:10:53 +0200 (MET DST) Message-Id: <199804170610.IAA09615@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 0.9.8 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <199804151325.PAA01599@gilberto.physik.RWTH-Aachen.DE> In-Reply-To: <199804151325.PAA01599@gilberto.physik.RWTH-Aachen.DE> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: current after a while - obsolete options X-Original-Newsgroups: local.freebsd.current To: freebsd-current@FreeBSD.ORG Cc: Christoph Kukulies Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christoph Kukulies wrote: > Only a few kernel options seem to be obsolete and I'm asking > whether they've been replaced by something else or have been dropped > by the one or other reason: > > options "GUSMAX" (dunno) > pseudo-device log This one apparently went stale long ago without anybody noticing. This got only apparent when i modified config(8) to warn about superfluous pseudo-device statements (which it didn't use to do for some ten years). If you look into /sys/conf/files, you'll see that kern/subr_log.c is marked `standard' (and has been this way AFAcvsCT, i.e. at least back to 4.4BSD-Lite). > pseudo-device pcaudio See /sys/i386/conf/files: this one is named `pca' now. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 23:22:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA07712 for freebsd-current-outgoing; Thu, 16 Apr 1998 23:22:51 -0700 (PDT) (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 GAA07707 for ; Fri, 17 Apr 1998 06:22:46 GMT (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id IAA00244 for current@FreeBSD.ORG; Fri, 17 Apr 1998 08:22:42 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.9.0.Beta4/keltia-2.14/nospam) id IAA00156; Fri, 17 Apr 1998 08:16:48 +0200 (CEST) (envelope-from roberto) Message-ID: <19980417081647.A120@keltia.freenix.fr> Date: Fri, 17 Apr 1998 08:16:47 +0200 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: Problems w/ Linux EMU Mail-Followup-To: current@FreeBSD.ORG References: <199804170135.VAA11058@rtfm.ziplink.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91i In-Reply-To: ; from Brandon Lockhart on Thu, Apr 16, 1998 at 09:39:33PM -0400 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4213 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Brandon Lockhart: > I am running FreeBSD 3.0-Current last updated on Sunday. For some strange > reason, my Linux EMU is having problems. (It doesn't recognize the ELF > binary type). Any clue why this is happening? 1. check you have the LKM up to date with the kernel, 2. check that the linux LKM is loaded (with modstat(8)) and load it with linux(8), 3. if using static ELF binaries, don't forget to "brand" them with brandelf(8), -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #3: Tue Apr 14 21:41:01 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 23:33:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA09651 for freebsd-current-outgoing; Thu, 16 Apr 1998 23:33:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA09640 for ; Fri, 17 Apr 1998 06:33:40 GMT (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id IAA03123; Fri, 17 Apr 1998 08:33:35 +0200 (MEST) (envelope-from sos) Message-Id: <199804170633.IAA03123@sos.freebsd.dk> Subject: Re: Networking strategy for -current In-Reply-To: <353699BD.ABD322C@whistle.com> from Julian Elischer at "Apr 16, 98 04:52:29 pm" To: julian@whistle.com (Julian Elischer) Date: Fri, 17 Apr 1998 08:33:34 +0200 (MEST) Cc: current@FreeBSD.ORG, kjc@csl.sony.co.jp From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (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 In reply to Julian Elischer who wrote: > One of the things that has been apparent is that FreeBSD is being > used more and more as a firewall and router for people with > special networking requirements. The networking code however > is getting old, and needs work in various places. many people are > also using it for experimentation. Julian, to put it very simple, you need to get DEVFS and possibly softupdates finished before you get to commit any new halfbaked solutions to -current. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 23:35:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA10151 for freebsd-current-outgoing; Thu, 16 Apr 1998 23:35:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA10110; Fri, 17 Apr 1998 06:35:27 GMT (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id GAA17997; Fri, 17 Apr 1998 06:34:15 GMT Date: Fri, 17 Apr 1998 15:34:15 +0900 (JST) From: Michael Hancock To: Julian Elischer cc: freebsd-current@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: Updated vfs patches In-Reply-To: <3536EE71.41C67EA6@whistle.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, 16 Apr 1998, Julian Elischer wrote: > > I found it (POST_SOFTUPDATES)! Do we not block when calling truncate with > > softupdates on? > > now THAT is a good question...... > I basically took the code from kirk's changes and he seemed > (from my memory.. I don't have the changes here) to have made > that change, so I did too. I'd have to ask kirk WHY he did that > and he's out of town for 1 more week. The changes look intentional because it was like this before... vput(dvp) dvp = NULL truncate out: if (dvp) vput(dvp) return Now it looks like this ... truncate out: vput(dvp) return You had to make a couple of changes to do this. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 23:38:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA10940 for freebsd-current-outgoing; Thu, 16 Apr 1998 23:38:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles247.castles.com [208.214.165.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA10888; Fri, 17 Apr 1998 06:38:04 GMT (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id XAA00806; Thu, 16 Apr 1998 23:35:39 -0700 (PDT) Message-Id: <199804170635.XAA00806@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: sos@FreeBSD.ORG cc: julian@whistle.com (Julian Elischer), current@FreeBSD.ORG, kjc@csl.sony.co.jp Subject: Re: Networking strategy for -current In-reply-to: Your message of "Fri, 17 Apr 1998 08:33:34 +0200." <199804170633.IAA03123@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Thu, 16 Apr 1998 23:35:38 -0700 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id GAA10915 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In reply to Julian Elischer who wrote: > > One of the things that has been apparent is that FreeBSD is being > > used more and more as a firewall and router for people with > > special networking requirements. The networking code however > > is getting old, and needs work in various places. many people are > > also using it for experimentation. > > Julian, to put it very simple, you need to get DEVFS and possibly > softupdates finished before you get to commit any new halfbaked > solutions to -current. Do we want the DEVFS/SLICE code in before or after CAM? If we want before, then that can come prettymuch Right Now. I may have some time for this, if there's general agreement that that's what it will take. (Yes, Ken, I'll finish what I started there first 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 Thu Apr 16 23:47:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14459 for freebsd-current-outgoing; Thu, 16 Apr 1998 23:47:18 -0700 (PDT) (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 GAA14412; Fri, 17 Apr 1998 06:47:13 GMT (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id XAA29061; Thu, 16 Apr 1998 23:44:42 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd029059; Fri Apr 17 06:44:36 1998 Message-ID: <3536F91A.446B9B3D@whistle.com> Date: Thu, 16 Apr 1998 23:39:22 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: sos@FreeBSD.ORG CC: current@FreeBSD.ORG, kjc@csl.sony.co.jp Subject: Re: Networking strategy for -current References: <199804170633.IAA03123@sos.freebsd.dk> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG S?ren Schmidt wrote: > > In reply to Julian Elischer who wrote: > > One of the things that has been apparent is that FreeBSD is being > > used more and more as a firewall and router for people with > > special networking requirements. The networking code however > > is getting old, and needs work in various places. many people are > > also using it for experimentation. > > Julian, to put it very simple, you need to get DEVFS and possibly > softupdates finished before you get to commit any new halfbaked > solutions to -current. > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team > Even more code to hack -- will it ever end > .. Well gee thanks for the reminder.. here's what I recently said to poul on the topic: > >Oh I am.. but softupdates is on hold till kirk gets back >and doing bandwidth management is my present assigned task. > >I could do it in any way I want but I'd rather do it in a way that >benefits freeBSD generally and the easiest way of doing that is >to use the altq stuff that was released rather than doing proprietary >stuff. > >DEVFS is my personal hat. >bandwidth is my whistle hat while softupdates is on hold. I hope to get together with Mike smith in the next week to try knock out some of the devfs nits. As far as I'm concerned it's working. (I use it in production every day.) But thre are a few cosmetic things that need to be done. Have you tried it? I haven't seen a crash out of it since december. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 16 23:49:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA15783 for freebsd-current-outgoing; Thu, 16 Apr 1998 23:49:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA15657; Fri, 17 Apr 1998 06:49:35 GMT (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with ESMTP id GAA18086; Fri, 17 Apr 1998 06:48:44 GMT Date: Fri, 17 Apr 1998 15:48:44 +0900 (JST) From: Michael Hancock To: Søren Schmidt cc: Julian Elischer , current@FreeBSD.ORG, kjc@csl.sony.co.jp Subject: Re: Networking strategy for -current In-Reply-To: <199804170633.IAA03123@sos.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 17 Apr 1998, Søren Schmidt wrote: > Julian, to put it very simple, you need to get DEVFS and possibly > softupdates finished before you get to commit any new halfbaked > solutions to -current. Julian, have a look at my vfs patches. You will be able to get rid of VNSLEAZE in devfs. Soren, we should probably have some networking people look at it closely. ALTQ looks like it has had sometime to soak so be a little more careful before you call it halfbaked, unless you've reviewed it. Regards, Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 00:05:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA20545 for freebsd-current-outgoing; Fri, 17 Apr 1998 00:05:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA20517; Fri, 17 Apr 1998 07:05:13 GMT (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id JAA03190; Fri, 17 Apr 1998 09:04:57 +0200 (MEST) (envelope-from sos) Message-Id: <199804170704.JAA03190@sos.freebsd.dk> Subject: Re: Networking strategy for -current In-Reply-To: from Michael Hancock at "Apr 17, 98 03:48:44 pm" To: michaelh@cet.co.jp (Michael Hancock) Date: Fri, 17 Apr 1998 09:04:56 +0200 (MEST) Cc: sos@FreeBSD.ORG, julian@whistle.com, current@FreeBSD.ORG, kjc@csl.sony.co.jp From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (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 In reply to Michael Hancock who wrote: > On Fri, 17 Apr 1998, Søren Schmidt wrote: > > > Julian, to put it very simple, you need to get DEVFS and possibly > > softupdates finished before you get to commit any new halfbaked > > solutions to -current. > > Julian, have a look at my vfs patches. You will be able to get rid of > VNSLEAZE in devfs. I've not touched DEVFS sinc january, but back then it was far from finished, and my impression is that not much has happend since then. > Soren, we should probably have some networking people look at it closely. > ALTQ looks like it has had sometime to soak so be a little more careful > before you call it halfbaked, unless you've reviewed it. Oh, dont get me wrong here, I'm not after the ALTQ people, I'm after Julian, he has a deal with us that I will hold him to. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 00:32:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA26668 for freebsd-current-outgoing; Fri, 17 Apr 1998 00:32:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA26660; Fri, 17 Apr 1998 07:32:41 GMT (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with ESMTP id HAA18356; Fri, 17 Apr 1998 07:31:46 GMT Date: Fri, 17 Apr 1998 16:31:46 +0900 (JST) From: Michael Hancock To: Søren Schmidt cc: julian@whistle.com, current@FreeBSD.ORG, kjc@csl.sony.co.jp Subject: Re: Networking strategy for -current In-Reply-To: <199804170704.JAA03190@sos.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 17 Apr 1998, Søren Schmidt wrote: > In reply to Michael Hancock who wrote: > > On Fri, 17 Apr 1998, Søren Schmidt wrote: > > > > > Julian, to put it very simple, you need to get DEVFS and possibly > > > softupdates finished before you get to commit any new halfbaked > > > solutions to -current. > > > > Julian, have a look at my vfs patches. You will be able to get rid of > > VNSLEAZE in devfs. > > I've not touched DEVFS sinc january, but back then it was far from > finished, and my impression is that not much has happend since > then. I found a refcounting problem since then and I guess work was done on making it compatible with the slice code. I think we need to do things like verify that all the necessary devices show up. > > Soren, we should probably have some networking people look at it closely. > > ALTQ looks like it has had sometime to soak so be a little more careful > > before you call it halfbaked, unless you've reviewed it. > > Oh, dont get me wrong here, I'm not after the ALTQ people, I'm after > Julian, he has a deal with us that I will hold him to. Ok I misunderstood, I agree we do want to see things get completed. I think we need more warm bodies. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 00:43:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA28597 for freebsd-current-outgoing; Fri, 17 Apr 1998 00:43:41 -0700 (PDT) (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 HAA28573 for ; Fri, 17 Apr 1998 07:43:20 GMT (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id IAA08337; Fri, 17 Apr 1998 08:03:15 +0200 From: Luigi Rizzo Message-Id: <199804170603.IAA08337@labinfo.iet.unipi.it> Subject: Re: Networking strategy for -current To: julian@whistle.com (Julian Elischer) Date: Fri, 17 Apr 1998 08:03:15 +0200 (MET DST) Cc: current@FreeBSD.ORG, kjc@csl.sony.co.jp In-Reply-To: <353699BD.ABD322C@whistle.com> from "Julian Elischer" at Apr 16, 98 04:52:10 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > One usage that people have often asked for is the ability to allocate > bandwidth, and to re-visit the queuing strategies we use. right... I have been thinking for a long time to move my dummynet stuff down a level (now it's between TCP and IP) and hook it to the IPFW code so that one can use the same filtering as IPFW and use bw limitation. Haven't had the time to look at ALTQ, obviously if it can do hard BW limiting (and not only WFQ) that would be great (the only advantage of dummynet at this point would be the ability to add programmable delays to simulate long pipes...). > Sony labs have recently announced their ALTQ package in a new release. > I would like to find out from the people involved in networking, what > the general consensus would be to our integrating this into -current. > (under #ifdefs of course) I'd like the idea a lot. > 2/ The CBQ method Sony supply has it's own packet classifier > that is basically a duplicate of the IPFW or ipfilter > classifiers. It might be worth us looking to see if the IPFW > (or ipfilter) code can be used to do this. I would do this by this question can be turned to the author of ALTQ... My understanding is that if he wants a portable package, then the classifier must be within ALTQ -- in case some other OS does not have the classifier. In a sense this would be ok since we could remove our own IPFW classifier and use the ALTQ instead (the issues are efficiency -- i have no idea on this -- and backward compatibility -- but this can be solved at the user level perhaps, in the ipfw control program). > expanding the mbuf pkthdr field to contain a pointer to some meta-data > such as 'traffic class'. This could be set by each protocol a flow ID you mean ? > in any way that makes sense to it. (e.g. by a new IPFW command) > (instead of a special pass). cheers luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 00:51:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA00342 for freebsd-current-outgoing; Fri, 17 Apr 1998 00:51:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA00336 for ; Fri, 17 Apr 1998 07:51:01 GMT (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id JAA02462 for ; Fri, 17 Apr 1998 09:49:59 +0200 (CEST) To: current@FreeBSD.ORG Subject: DEVFS problem... From: Poul-Henning Kamp Date: Fri, 17 Apr 1998 09:49:58 +0200 Message-ID: <2460.892799398@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 3.0-current machine compile kernel with DEVFS boot -sv mount -t devfs /dev /dev ^D Kernel prints: bad-rev_link and userland prints: /dev/wd0s1a on /: Specified device does not match mounted device. /etc/fstab contains: /dev/wd0s1a / ufs rw 1 1 -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 01:15:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA03696 for freebsd-current-outgoing; Fri, 17 Apr 1998 01:15:19 -0700 (PDT) (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 IAA03683 for ; Fri, 17 Apr 1998 08:15:06 GMT (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id IAA08485; Fri, 17 Apr 1998 08:34:06 +0200 From: Luigi Rizzo Message-Id: <199804170634.IAA08485@labinfo.iet.unipi.it> Subject: Re: Diskless configuration... To: mike@smith.net.au (Mike Smith) Date: Fri, 17 Apr 1998 08:34:06 +0200 (MET DST) Cc: current@FreeBSD.ORG In-Reply-To: <199804162225.PAA01446@dingo.cdrom.com> from "Mike Smith" at Apr 16, 98 03:25:31 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hmm. See also: > > http://www.freebsd.org/~msmith/FTL/appnotes/1000.R-BOOTP_TFTP on this one, note that the nfs SWAP PATH is optional, at least 2.2.5 and above do work without NFS swap. My experience is that swap on NFS is ok if the server is nearby, but when i used it on a host 3 hops away, the machine is very sensitive to lost packets and often the machine hangs. > http://www.freebsd.org/~msmith/FTL/appnotes/1010.P-DISKLESS and in this one, if i am not mistaken, the shared root filesystem is not dealt in much detail. The main goal of my document was to give detailed info on exactly this step. Feel free to integrate in your pages above anything you like from my page. cheers luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 01:19:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA04304 for freebsd-current-outgoing; Fri, 17 Apr 1998 01:19:20 -0700 (PDT) (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 IAA04287 for ; Fri, 17 Apr 1998 08:19:17 GMT (envelope-from kpielorz@caladan.tdx.co.uk) Received: from localhost (kpielorz@localhost) by caladan.tdx.co.uk (8.8.8/8.8.8) with SMTP id JAA04707 for ; Fri, 17 Apr 1998 09:19:15 +0100 (BST) (envelope-from kpielorz@caladan.tdx.co.uk) Date: Fri, 17 Apr 1998 09:19:15 +0100 (BST) From: Karl Pielorz To: current@FreeBSD.ORG Subject: Problems with 3.0-980311-SNAP & Samba 1.9.18p4 Message-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've just installed 3.0-980311-SNAP on my system... It's the first time I've been running a 3.0 system as my 'main' (but not mission critical) machine... Everything went very smoothly - except Samba now refuses to work... If I boot the system back off it's old 2.2.6 drive it works fine (with either samba 1.9.18p3 or p4) - but with the new system under the 3.0 SNAP I get: Apr 17 08:57:26 caladan /kernel: pid 4664 (smbd), uid 2000: exited on signal 8 The samba logs don't show anything 'going wrong' even with debug level 9 set... :-( I've also made sure that the 3.0 system is a 'pure' system (i.e. theres no old 2.2.6 binaries / libs kicking around) - in fact it's guarenteed 100% pure as it's on a new disk, and the old one is disconnected! And my other machine (an NT box) gives "An unexpected network error has occured" (10 out of 10 for the nice cryptic NT error ;-) I'm kinda new to actually doing anything with 3.0-CURRENT my original plan was to run a SNAP for a few months - and then upgrade as and when... I'm looking at setting up cvsup etc. to at least keep the source on the system current... Is it a good idea for me just to grab -the latest- source and do a makeworld - is this the only likely thing that's going to stand a chance of fixing samba? Is there any documentation anywhere I can look at with a view of going through the nice .core files it produced and trying to find out what went wrong? Regards, Karl Pielorz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 01:35:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA07144 for freebsd-current-outgoing; Fri, 17 Apr 1998 01:35:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA07136 for ; Fri, 17 Apr 1998 08:35:37 GMT (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id KAA02674 for ; Fri, 17 Apr 1998 10:34:35 +0200 (CEST) To: current@FreeBSD.ORG Subject: DEVFS, DEVFS_ROOT doesn't help: From: Poul-Henning Kamp Date: Fri, 17 Apr 1998 10:34:34 +0200 Message-ID: <2672.892802074@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Same machine, added DEVFS_ROOT to kernel, now I get ffs_mountroot: can't find rootvperror2: panic: cannot mount root(2) -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 01:42:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA08909 for freebsd-current-outgoing; Fri, 17 Apr 1998 01:42:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA08896; Fri, 17 Apr 1998 08:42:09 GMT (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id KAA03375; Fri, 17 Apr 1998 10:42:04 +0200 (MEST) (envelope-from sos) Message-Id: <199804170842.KAA03375@sos.freebsd.dk> Subject: Re: DEVFS, DEVFS_ROOT doesn't help: In-Reply-To: <2672.892802074@critter.freebsd.dk> from Poul-Henning Kamp at "Apr 17, 98 10:34:34 am" To: phk@FreeBSD.ORG (Poul-Henning Kamp) Date: Fri, 17 Apr 1998 10:42:03 +0200 (MEST) Cc: current@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (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 In reply to Poul-Henning Kamp who wrote: > > Same machine, added DEVFS_ROOT to kernel, now I get > > ffs_mountroot: can't find rootvperror2: panic: cannot mount root(2) Who was it that said he was running production on this ???? -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 03:07:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA20917 for freebsd-current-outgoing; Fri, 17 Apr 1998 03:07:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA20912 for ; Fri, 17 Apr 1998 10:07:14 GMT (envelope-from dag-erli@ifi.uio.no) Received: from gladsheim.ifi.uio.no (2602@gladsheim.ifi.uio.no [129.240.64.132]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id MAA01225; Fri, 17 Apr 1998 12:07:12 +0200 (MET DST) Received: (from dag-erli@localhost) by gladsheim.ifi.uio.no ; Fri, 17 Apr 1998 12:07:11 +0200 (MET DST) Mime-Version: 1.0 To: joelh@gnu.org Cc: current@FreeBSD.ORG Subject: Re: syscons.c and graphical screensavers References: <199804160353.WAA01213@detlev.UUCP> Organization: Gutteklubben Terrasse / KRST / PUMS / YASMW X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-Stop-Spam: http://www.cauce.org From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 17 Apr 1998 12:07:11 +0200 In-Reply-To: Joel Ray Holveck's message of "Wed, 15 Apr 1998 22:53:09 -0500 (CDT)" Message-ID: Lines: 19 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joel Ray Holveck writes: > [following up to -current] > > I changed current's src/sys/i386/isa/syscons.c to put the "should we > > stop the screensaver" check before the "should we just return" check. > The screensaver needs to properly handle shutdown before the switch, > but that's not hard. If you're writing a graphical screensaver, talk > to me and I'll get you my template. OK, I added a call to stop_scrn_saver() right before the switching code in switch_scr(). Perhaps it's *too* conservative, but I figured it can't hurt. As to your template, I remember you mentioning it way back; I'd love to see it. I have written two graphical screensavers (the logo saver you've already seen, and a starfield with eight levels of parallax scrolling) which would certainly benefit from your code :) -- fprintf(stderr, "I have a closed mind. It helps keeping the rain out.\n"); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 04:59:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA09088 for freebsd-current-outgoing; Fri, 17 Apr 1998 04:59:34 -0700 (PDT) (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 LAA09080 for ; Fri, 17 Apr 1998 11:59:32 GMT (envelope-from ab@paert.tse-online.de) Received: (qmail 3131 invoked by uid 1000); 17 Apr 1998 11:03:05 -0000 Message-ID: <19980417130304.L25244@paert.tse-online.de> Date: Fri, 17 Apr 1998 13:03:04 +0200 From: Andreas Braukmann To: freebsd-current@FreeBSD.ORG Cc: Jonathan Lemon , Matthew Thyer Subject: Re: 'fatal trap 12' on boot (smp and up) Mail-Followup-To: freebsd-current@FreeBSD.ORG, Jonathan Lemon , Matthew Thyer References: <19980415202740.43100@paert.tse-online.de> <3536B24B.AF3DBB0D@camtech.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91i In-Reply-To: <3536B24B.AF3DBB0D@camtech.net.au>; from Matthew Thyer on Fri, Apr 17, 1998 at 11:07:15AM +0930 Organization: TSE TeleService GmbH Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, On Fri, Apr 17, 1998 at 11:07:15AM +0930, Matthew Thyer wrote: > I also get the same crash if *and only if* I boot FreeBSD using > FBSDBOOT.EXE from DOS (I have multiple OS's on my disk). hmm. We might have found the culprit. I'm using fbsdboot, too. Sorry for the incomplete information. I just didn't realized the possibility of the boot-method influencing a loaded kernel. > The answer for me was to re-install my normal bootblock 'BootEasy' > which had been lost when I recently re-installed Windows 95. I'm using fbsdboot for a slightly different reason. I'm multibooting the machine with FreeBSD SMP and UP, NT WS, NT Server and DOS/Win. (BSD's bootslice occupies sd1, NTs and Win95 are booting of sd0; the data-partitions are spreaded around 3 disks [bootdisks included]) Using booteasy I had difficulties with NT's harddisk-manager. This thing obviously insists on marking the bootsector with a so called signature, before taking any actions on the harddisks; thereby it used to overwrite the booteasy-code? Maybe I should try to boot the bsd-system directly from the NT-Bootmanager. I've tried that once, but without much success. Regards, 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 Fri Apr 17 05:44:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA13801 for freebsd-current-outgoing; Fri, 17 Apr 1998 05:44:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from widefw.csl.sony.co.jp (widefw.csl.sony.co.jp [133.138.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA13796 for ; Fri, 17 Apr 1998 12:44:20 GMT (envelope-from kjc@csl.sony.co.jp) Received: from hotaka.csl.sony.co.jp (root@hotaka.csl.sony.co.jp [43.27.98.57]) by widefw.csl.sony.co.jp (8.8.8/3.6W) with ESMTP id VAA08359; Fri, 17 Apr 1998 21:44:15 +0900 (JST) Received: from localhost (kjc@[127.0.0.1]) by hotaka.csl.sony.co.jp (8.8.8/3.6W/hotaka/98021914) with ESMTP id VAA14149; Fri, 17 Apr 1998 21:44:14 +0900 (JST) Message-Id: <199804171244.VAA14149@hotaka.csl.sony.co.jp> To: Julian Elischer cc: current@FreeBSD.ORG Subject: Re: Networking strategy for -current In-reply-to: Your message of "Thu, 16 Apr 1998 16:52:29 MST." <353699BD.ABD322C@whistle.com> Date: Fri, 17 Apr 1998 21:44:14 +0900 From: Kenjiro Cho Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian, Thank you for your interest in ALTQ. (for those who don't know about it, ALTQ is a queueing framework to control network traffic. The related information is available at http://www.csl.sony.co.jp/person/kjc/software.html) >> I would envision that this would be done in a few steps. >> 1/ the framework for selecting alternate queueing schemes for >> intefaces could be integrated as a separate unit. It allows a >> queueing module to supply methods which would be used for queueing. >> A slightly more generic method than that used by Sony would allow >> queueing methods to be LKMs if needed. I'm pretty sure that this can >> be done as a compile parameter (as sony have done) that would leave >> the system still stable and effectively unaltered in the 'compiled out' >> case. I'm planning to move to -current once things become more stable on -current. I believe there will be no technical problem to merge the ALTQ framework into -current, and I'm willing to do it if there are enough people interested. (I already have a commit privilege as a maintainer of the ATM driver.) >> 2/ The CBQ method Sony supply has it's own packet classifier >> that is basically a duplicate of the IPFW or ipfilter >> classifiers. It might be worth us looking to see if the IPFW >> (or ipfilter) code can be used to do this. I would do this by >> expanding the mbuf pkthdr field to contain a pointer to some meta-data >> such as 'traffic class'. This could be set by each protocol >> in any way that makes sense to it. (e.g. by a new IPFW command) >> (instead of a special pass). I think just merging the two is not enough. We need a more efficient and flexible classifier. But it isn't easy since there are a wide range of requirements and, at the same time, the classifier must be efficient. Although it is redundant to have two different implementations, it is easier for me or others to experiment with it. >> 3/ the methods that Sony supply are basically independent modules >> and could be added as independent modules. THey are only turned on on a >> -per interface- basis when requested so POLA is preserved. Yes. >> At least I'd like to see the altq FRAMEWORK added even if >> the specific methods and more esoteric methods and control >> programs may not be immediatly added. Thanks for your support. Also, I should mention that Linux recently added CBQ support. (but I haven't had time to look into their implementation.) I'm now working on the follwoing issues: 1. better support for slow links (suggested by Luigi) A better queueing alone is not enough for dial-up users. Parameter tuning (e.g., packet size, device buffer size) and additional mechanisms are required. 2. IPv6 support Make use of IPv6 features (e.g, flowlabel) Also, I feel that when we incorporate IPv6 is a good opportunity to incorporate various other networking research outputs (e.g., RED, ECN, diff-serv) into the existing platforms. 3. copyright issues Some of the CBQ related files have Sun's restrictive copyright. Sally Floyd (CBQ inventor) and I have been talking with Sun, and, at least, a guy at Sun is cooperative. Anyway, I will present my work at USENIX (Friday morning, Refereed paper). So, I will have a chance to talk with FreeBSD people in New Orleans. --Kenjiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 06:12:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA17462 for freebsd-current-outgoing; Fri, 17 Apr 1998 06:12:28 -0700 (PDT) (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 NAA17433 for ; Fri, 17 Apr 1998 13:12:25 GMT (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.8.8/8.8.8) with ESMTP id OAA01716 for ; Fri, 17 Apr 1998 14:12:23 +0100 (BST) (envelope-from kpielorz@tdx.co.uk) Message-ID: <3537551C.5F2C9731@tdx.co.uk> Date: Fri, 17 Apr 1998 14:11:56 +0100 From: Karl Pielorz Organization: TDX X-Mailer: Mozilla 4.04 [en] (WinNT; I) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: Problems with 3.0-980311-SNAP & Samba 1.9.18p4 - FIXED References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Karl Pielorz wrote: > > Hi, > > I've just installed 3.0-980311-SNAP on my system... It's the first time > [snip] > under the 3.0 SNAP I get: > > Apr 17 08:57:26 caladan /kernel: pid 4664 (smbd), uid 2000: exited on > signal 8 This is now fixed... CVSupp'ing to the latest as of 17/04/98 @ 13.50 & recompiling Samba did it... It also scared the living daylights out of me (watching it grab all the new code since the snapshot I installed), then having to make the world, then the kernel - and finally the device nodes & rebooting... As I said - all very scary, but a real credit to the people who design and code this stuff - it all went very smoothly! Regards, Karl Pielorz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 06:32:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA20915 for freebsd-current-outgoing; Fri, 17 Apr 1998 06:32:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles324.castles.com [208.214.167.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20770; Fri, 17 Apr 1998 13:31:45 GMT (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id GAA00385; Fri, 17 Apr 1998 06:29:23 -0700 (PDT) Message-Id: <199804171329.GAA00385@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: sos@FreeBSD.ORG cc: phk@FreeBSD.ORG (Poul-Henning Kamp), current@FreeBSD.ORG Subject: Re: DEVFS, DEVFS_ROOT doesn't help: In-reply-to: Your message of "Fri, 17 Apr 1998 10:42:03 +0200." <199804170842.KAA03375@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Fri, 17 Apr 1998 06:29:23 -0700 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id NAA20779 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In reply to Poul-Henning Kamp who wrote: > > > > Same machine, added DEVFS_ROOT to kernel, now I get > > > > ffs_mountroot: can't find rootvperror2: panic: cannot mount root(2) > > Who was it that said he was running production on this ???? I think you'll find that these are mostly related to the changes I recently made regarding root mounts. Note that if the DEVFS/SLICE code had been in the -current tree when I made these changes, it would have been updated as a matter 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 Fri Apr 17 06:50:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23838 for freebsd-current-outgoing; Fri, 17 Apr 1998 06:50:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from irbs.irbs.com (irbs.irbs.com [209.36.62.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA23831 for ; Fri, 17 Apr 1998 13:50:21 GMT (envelope-from jc@irbs.com) Received: (from jc@localhost) by irbs.irbs.com (8.8.5/8.8.5) id JAA13436; Fri, 17 Apr 1998 09:50:16 -0400 (EDT) Message-ID: <19980417095016.61655@irbs.com> Date: Fri, 17 Apr 1998 09:50:16 -0400 From: John Capo To: current@FreeBSD.ORG Subject: Re: Networking strategy for -current References: <353699BD.ABD322C@whistle.com> <199804170135.VAA11058@rtfm.ziplink.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199804170135.VAA11058@rtfm.ziplink.net>; from Mikhail Teterin on Thu, Apr 16, 1998 at 09:35:48PM -0400 X-Organization: IRBS Engineering, (954) 463-3771 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I modified ppp to round robin across the flows and it does improve interactive peformance on a modem link while multiple flows are active. My intention was to make it true fair queuing but I got side tracked with other projects. An MTU somewhat less than 1500 helps too. http://www.irbs.com/FreeBSD/ip.c This is a fairly old ip.c but it should drop into modern ppp without too much trouble.. John Capo Quoting Mikhail Teterin (mi@aldan.algebra.com): > > Yes! Absolute yes. This would be excellent! I could be downloading > some stuff over my modem while still working through ssh. Someone > could make sure the diskless workstations get their / and /usr > faster then then they talk to a Web proxy, etc. If the network is > indeed a computer, you must be able to prioritize it just like you > can prioritize processes. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 07:07:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA26512 for freebsd-current-outgoing; Fri, 17 Apr 1998 07:07:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from itesec.hsc.fr (root@itesec.hsc.fr [192.70.106.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA26505 for ; Fri, 17 Apr 1998 14:07:02 GMT (envelope-from pb@hsc.fr) Received: from mars.hsc.fr (pb@mars.hsc.fr [192.70.106.44]) by itesec.hsc.fr (8.8.8/8.8.5/itesec-1.12-nospam) with ESMTP id QAA17726; Fri, 17 Apr 1998 16:06:33 +0200 (MET DST) Received: (from pb@localhost) by mars.hsc.fr (8.8.5/8.8.5/pb-19970301) id QAA08623; Fri, 17 Apr 1998 16:06:32 +0200 (MET DST) Message-ID: <19980417160631.BO42933@mars.hsc.fr> Date: Fri, 17 Apr 1998 16:06:31 +0200 From: pb@fasterix.frmug.org (Pierre Beyssac) To: kjc@csl.sony.co.jp (Kenjiro Cho) Cc: julian@whistle.com (Julian Elischer), current@FreeBSD.ORG Subject: Re: Networking strategy for -current References: <353699BD.ABD322C@whistle.com> <199804171244.VAA14149@hotaka.csl.sony.co.jp> X-Mailer: Mutt 0.59.1e Mime-Version: 1.0 In-Reply-To: <199804171244.VAA14149@hotaka.csl.sony.co.jp>; from Kenjiro Cho on Apr 17, 1998 21:44:14 +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Kenjiro Cho: > I'm planning to move to -current once things become more stable on > -current. I believe there will be no technical problem to merge the > ALTQ framework into -current, and I'm willing to do it if there are > enough people interested. The IPv6 INRIA code includes ALTQ as an option. Since I've ported this code to -current, most of the porting work for ALTQ to -current is done except for one or two small compile nits (a problem with a change in queuing macros). I haven't had time to test ALTQ yet, and it's not the latest version. If anyone using -current is interested in having a look at it, my patches are available here, but keep in mind that they include IPv6 patches too : ftp://frmug.org/ipv6/ > 2. IPv6 support > Make use of IPv6 features (e.g, flowlabel) > Also, I feel that when we incorporate IPv6 is a good opportunity > to incorporate various other networking research outputs (e.g., > RED, ECN, diff-serv) into the existing platforms. Some of this (at least RED and ECN) is in the INRIA IPv6 too. About the same status as ALTQ regarding my port to -current (barely compile, untested). If there are any testers out there, they're more than welcome ! -- Pierre Beyssac pb@fasterix.frmug.org pb@fasterix.freenix.org {Free,Net,Open}BSD, Linux : il y a moins bien, mais c'est plus cher Free domains: http://www.eu.org/ or mail dns-manager@EU.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 07:07:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA26643 for freebsd-current-outgoing; Fri, 17 Apr 1998 07:07:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from opus.cts.cwu.edu (skynyrd@opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA26622 for ; Fri, 17 Apr 1998 14:07:27 GMT (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.8.8/8.8.8) with SMTP id HAA15467; Fri, 17 Apr 1998 07:07:13 -0700 (PDT) (envelope-from skynyrd@opus.cts.cwu.edu) Date: Fri, 17 Apr 1998 07:07:12 -0700 (PDT) From: Chris Timmons To: Karl Pielorz cc: current@FreeBSD.ORG Subject: Re: Problems with 3.0-980311-SNAP & Samba 1.9.18p4 - FIXED In-Reply-To: <3537551C.5F2C9731@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 You might try the www mailing list search page available at www.freebsd.org; search for samba in the current mailing list. The problem involved the compiler and operations involving unsigned integral types. -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 07:30:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA00628 for freebsd-current-outgoing; Fri, 17 Apr 1998 07:30:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from unix.tfs.net (as1-p147.tfs.net [139.146.210.147]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00621 for ; Fri, 17 Apr 1998 14:30:50 GMT (envelope-from jbryant@unix.tfs.net) Received: (from jbryant@localhost) by unix.tfs.net (8.8.8/8.8.5) id JAA11496; Thu, 21 May 1998 09:30:40 -0500 (CDT) From: Jim Bryant Message-Id: <199805211430.JAA11496@unix.tfs.net> Subject: Re: Help - please... Adaptec 1542 and Exabyte tape problem... In-Reply-To: from Brian Beattie at "Apr 16, 98 02:57:38 pm" To: beattie@aracnet.com (Brian Beattie) Date: Thu, 21 May 1998 09:30:39 -0500 (CDT) Cc: freebsd-current@FreeBSD.ORG Reply-to: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 3.0-CURRENT #5: Sun Mar 8 12:29:10 CST 1998 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 In reply: > On Wed, 20 May 1998, Jim Bryant wrote: > > > In reply: > > > On Wed, 15 Apr 1998, Tom wrote: > > > > > > > > > > > On Thu, 16 Apr 1998, Kerry Morse wrote: > > > > > > > > > Apr 16 13:35:05 proxy /kernel: aha0: DMA beyond end Of ISA: 0x357cd10 > > > > > > > > Bounce buffers are required to DMA above the 16MB for ISA devices. > > > > However, bounce buffers do not work for the aha driver (it is unclear > > > > whether the driver or the bounce buffers are broken). > > > > > > > > crap.. i just sold my 1542cf for this very reason... i was wanting > > it to handle low-bandwidth stuff like the CD-ROM, M-O drive, and DDS-2 > > tape drive, but I kept getting the above messages... now i've got a > > heck of a lot of stuff hanging off my 2940UW... i of course have > > 'OPTION BOUNCE_BUFFERS' in my config... > > > > I may be mistaken but I believe that the 2940UW is a PCI card. That being > the case it does not require bounce buffers. The 2940UW is already > supported by the CAM code. actually, i had it (bounce buffers) in for the 1452cf, thinking things would work like they used to... jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 07:44:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA02537 for freebsd-current-outgoing; Fri, 17 Apr 1998 07:44:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thing.dyn.ml.org (root@pm336-17.dialip.mich.net [35.9.11.83]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA02522 for ; Fri, 17 Apr 1998 14:44:19 GMT (envelope-from mcdougall@ameritech.net) Received: from ameritech.net (bsdx [192.168.1.2]) by thing.dyn.ml.org (8.8.8/8.8.7) with ESMTP id KAA00873 for ; Fri, 17 Apr 1998 10:44:12 -0400 (EDT) (envelope-from mcdougall@ameritech.net) Message-ID: <35376ABB.ADF827AF@ameritech.net> Date: Fri, 17 Apr 1998 10:44:12 -0400 From: Adam McDougall Reply-To: mcdougall@ameritech.net X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Unable to crashdump Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I would like to enable crash dumps for -current so I can better understand why it crashes sometimes (totally a mystery in X since the display simply freezes). I have enabled then in rc.conf, but when a panic happens, my dpt 2144 is no longer able to write to the disk it seems, something about the panic tells it to shut down. When a dump is supposed to occur, my screen scrolls wildly with this message: dpt0 ERROR: Command "Write (10) [6.1.18]" recieved for b0t0u0 but controller is shut down; Aborting I cannot tell if the numbers change since they fly by so fast. Any insight into making it not shutdown before dumps would be appreciated. I did ask freebsd-scsi first, but did not recieve concern towards the problem. Thanks in advance. System info: Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #10: Fri Apr 17 10:22:35 EDT 1998 user1@bsdx.dyn.ml.org:/asynch/src/sys/compile/BSDXKRNL Timecounter "i8254" frequency 1193182 Hz cost 4789 ns Timecounter "TSC" frequency 233223055 Hz cost 163 ns CPU: Pentium (233.22-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping=3 Features=0x8001bf real memory = 67108864 (65536K bytes) avail memory = 62910464 (61436K bytes) DPT: RAID Manager driver, Version 1.0.5 Probing for devices on PCI bus 0: DPT: PCI SCSI HBA Driver, version 1.4.2 chip0: rev 0x00 on pci0.0.0 chip1: rev 0x01 on pci0.1.0 ide_pci0: rev 0xc0 int a irq 14 on pci0.1.1 vga0: rev 0x02 int a irq 11 on pci0.11.0 ed1: rev 0x00 int a irq 9 on pci0.13.0 ed1: address 00:4f:49:03:cb:b9, type NE2000 (16 bit) dpt0: rev 0x02 int a irq 12 on pci0.15.0 dpt0: DPT type 3, model PM2144UW firmware 07LY, Protocol 0 on port 6110 with Disabled cache. LED = 0000 0000 dpt0: Enabled Options: Collect Metrics dpt0: Shutdown handler registered dpt0: waiting for scsi devices to settle scbus0 at dpt0 bus 0 sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access 8682MB (17781008 512 byte sectors) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x340 sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface asc0 at 0x2ab-0x2af irq 10 drq 3 on isa asc0: [GI1904/Trust Ami-Scan Grey/Color] fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold wdc0 not found at 0x1f0 wdc1 not found at 0x170 npx0 flags 0x1 on motherboard npx0: INT 16 interface sb0 at 0x220 irq 5 drq 1 on isa snd0: sbxvi0 at 0x0 drq 5 on isa snd0: sbmidi0 at 0x330 on isa snd0: opl0 at 0x388 on isa snd0: Intel Pentium F00F detected, installing workaround WARNING: / was not properly dismounted. my conf file: # 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.77.2.8 1997/04/18 14:06:20 nate Exp $ machine "i386" #cpu "I386_CPU" #cpu "I486_CPU" cpu "I586_CPU" #cpu "I686_CPU" ident BSDXKRNL maxusers 80 #options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking #options IPX options FFS #Berkeley Fast Filesystem #options SOFTUPDATES #options MFS options DDB options DDB_UNATTENDED #options NFS #Network Filesystem #options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=5 #Be pessimistic about Joe SCSI device #options BOUNCE_BUFFERS #include support for DMA bounce buffers options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor #options USERCONFIG_BOOT #options VISUAL_USERCONFIG #visual boot -c editor options SYSVSHM options SYSVSEM options SYSVMSG #options "SHMMAXPGS=1024" # 4 megs shared mem config kernel root on sd0 controller isa0 #controller eisa0 controller pci0 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 #tape ft0 at fdc0 drive 2 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 #controller matcd0 at isa? port? bio #controller matcd1 at isa? port? bio #controller matcd2 at isa? port? bio #controller matcd3 at isa? port? bio #controller scbus0 #base SCSI code #device sd0 #SCSI disks #controller ppbus0 #controller vpo0 at ppbus? #device nlpt0 at ppbus? #device ppi0 at ppbus? #controller ppc0 at isa? disable port ? irq 7 vector ppcintr #controller ppbus0 #controller vpo0 at ppbus0 # Iomega ZIP support #device nlpt0 at ppbus0 # printer support #device ppi0 at ppbus0 # ppbus interface #controller ppc0 at isa? port? irq 7 vector ppcintr #device plip0 at ppbus0 # PLIP support # controller ppa0 at isa? port 0x278 bio flags 0x0 #First drive # controller ppa1 at isa? port 0x378 bio flags 0x0 #Second drive #device lpt0 at isa? disable port? tty #Polling lpt driver # A single entry for any of these controllers (ncr, ahb, ahc, amd) is # sufficient for any number of installed devices. #controller ncr0 #controller amd0 #controller ahb0 #controller ahc0 #controller bt0 at isa? port "IO_BT0" bio irq ? vector bt_isa_intr #controller uha0 at isa? port "IO_UHA0" bio irq ? drq 5 vector uhaintr #controller aha0 at isa? port "IO_AHA0" bio irq ? drq 5 vector ahaintr #controller aic0 at isa? port 0x340 bio irq 10 vector aicintr #controller nca0 at isa? port 0x1f88 bio irq 10 vector ncaintr #controller nca1 at isa? port 0x350 bio irq 5 vector ncaintr #controller sea0 at isa? bio irq 5 iomem 0xc8000 iosiz 0x2000 vector seaintr controller scbus0 device sd0 device od0 #See LINT for possible `od' options. #device st0 device cd0 #Only need one of these, the code dynamically grows #device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr #device mcd0 at isa? port 0x300 bio irq 10 vector mcdintr #device scd0 at isa? port 0x230 bio # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? port "IO_KBD" tty irq 1 vector pcrint #options PCVT_FREEBSD=210 # pcvt running on FreeBSD >= 2.0.5 #options XSERVER # include code for XFree86 #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 # Mandatory, don't remove device npx0 at isa? port "IO_NPX" flags 0x1 irq 13 vector npxintr # # Laptop support (see LINT for more options) # #device apm0 at isa? disable # Advanced Power Management # PCCARD (PCMCIA) support #controller crd0 #device pcic0 at crd? #device pcic1 at crd? device sio0 at isa? port "IO_COM1" 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 lpt1 at isa? port? tty #device mse0 at isa? port 0x23c tty irq 5 vector mseintr #device psm0 at isa? disable 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 #device fxp0 #device vx0 device ed0 at isa? port 0x340 net irq 9 iomem 0xd8000 vector edintr #device ed1 at isa? port 0x300 net irq 5 iomem 0xd8000 vector edintr #device ie0 at isa? port 0x300 net irq 10 iomem 0xd0000 vector ieintr #device ie1 at isa? port 0x360 net irq 7 iomem 0xd0000 vector ieintr #device ep0 at isa? port 0x300 net irq 10 vector epintr #device ex0 at isa? port 0x300 net irq 10 iomem 0xd0000 vector exintr #device fe0 at isa? port 0x300 net irq ? vector feintr #device le0 at isa? port 0x300 net irq 5 iomem 0xd0000 vector le_intr #device lnc0 at isa? port 0x280 net irq 10 drq 0 vector lncintr #device ze0 at isa? port 0x300 net irq 5 iomem 0xd8000 vector zeintr #device zp0 at isa? port 0x300 net irq 10 iomem 0xd8000 vector zpintr pseudo-device loop pseudo-device ether #pseudo-device log #pseudo-device sl 1 # ijppp uses tun instead of ppp device #pseudo-device ppp 1 pseudo-device vn 4 #pseudo-device tun 1 pseudo-device pty 128 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 pseudo-device snp 4 pseudo-device speaker pseudo-device bpfilter 4 options USER_LDT # options IPFIREWALL #firewall device asc0 at isa? port 0x2ab tty drq3 irq10 vector ascintr # sound controller snd0 device sb0 at isa? port 0x220 irq 5 drq 1 vector sbintr device sbxvi0 at isa? port 0x0 drq 5 device sbmidi0 at isa? port 0x330 device opl0 at isa? port 0x388 #device awe0 at isa? port 0x620 #controller pnp0 # The 'dpt' driver provides support for DPT controllers (http://www.dpt.com/). # See sys/dev/dpt for debugging and other subtle options. # /usr/sbin/dpt_* tools. # DPT_DEBUG_xxxx These are controllable from sys/dev/dpt/dpt.h controller dpt0 options "ENABLE_VFS_IOOPT" # DPT options #options DPT_VERIFY_HINTR #options DPT_RESTRICTED_FREELIST options DPT_MEASURE_PERFORMANCE #options DPT_FREELIST_IS_STACK #options DPT_HANDLE_TIMEOUTS #options DPT_TIMEOUT_FACTOR=4 #options DPT_INTR_DELAY=200 # Some motherboards need that #options DPT_LOST_IRQ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 09:30:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23825 for freebsd-current-outgoing; Fri, 17 Apr 1998 09:30:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA23816 for ; Fri, 17 Apr 1998 16:30:43 GMT (envelope-from luoqi@watermarkgroup.com) Received: by watermarkgroup.com (4.1/SMI-4.1) id AA13338; Fri, 17 Apr 98 12:28:50 EDT Date: Fri, 17 Apr 98 12:28:50 EDT From: luoqi@watermarkgroup.com (Luoqi Chen) Message-Id: <9804171628.AA13338@watermarkgroup.com> To: braukmann@tse-online.de, freebsd-current@FreeBSD.ORG Subject: Re: 'fatal trap 12' on boot (smp and up) Cc: jlemon@americantv.com, thyerm@camtech.net.au Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm using fbsdboot for a slightly different reason. > I'm multibooting the machine with FreeBSD SMP and UP, NT WS, NT Server and DOS/Win. > (BSD's bootslice occupies sd1, NTs and Win95 are booting of sd0; the data-partitions > are spreaded around 3 disks [bootdisks included]) > Using booteasy I had difficulties with NT's harddisk-manager. This thing > obviously insists on marking the bootsector with a so called signature, before > taking any actions on the harddisks; thereby it used to overwrite the booteasy-code? > > Maybe I should try to boot the bsd-system directly from the NT-Bootmanager. > I've tried that once, but without much success. > I wrote a boot sector for the NT boot loader to do exactly that two days ago. What it does is relocate itself, load the boot sector from the second disk (actually the next bios disk) and pass the control over. You might be able to use booteasy instead, but I haven't tried. Save the attached file, uudecode, copy to NT's root directory and add a line to NT's boot.ini like, C:\BOOTSECT.NXT="Next Disk" I can post the source if anyone is interested. begin 644 bootsect.nxt M,<".V&:[``8``&:.P_QFB<=FO@!\``!FN0`!``#S9J5FZB@`````!O["CL!F MN`$"``!FNP!\``!FN0$```!F@>+_````S1-F<@AFZ@!\`````&:^@P```&;H M`P```&;K'F909E-FNP$```#\K#P`9G0'M`[-$&;K\V9;9EAFP_1FZ_Q296%D M(&5R Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA05774 for freebsd-current-outgoing; Fri, 17 Apr 1998 10:27:51 -0700 (PDT) (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 RAA05769 for ; Fri, 17 Apr 1998 17:27:48 GMT (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA12486; Fri, 17 Apr 1998 10:22:30 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd012482; Fri Apr 17 17:22:24 1998 Message-ID: <35378E95.3F54BC7E@whistle.com> Date: Fri, 17 Apr 1998 10:17:09 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: Pierre Beyssac CC: Kenjiro Cho , current@FreeBSD.ORG Subject: Re: Networking strategy for -current References: <353699BD.ABD322C@whistle.com> <199804171244.VAA14149@hotaka.csl.sony.co.jp> <19980417160631.BO42933@mars.hsc.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pierre Beyssac wrote: > > According to Kenjiro Cho: > > I'm planning to move to -current once things become more stable on > > -current. I believe there will be no technical problem to merge the > > ALTQ framework into -current, and I'm willing to do it if there are > > enough people interested. I have ported the ALTQ stuff to -current.. (the kernel part anyhow..) I'll put the patches up for ftp later today.. > > The IPv6 INRIA code includes ALTQ as an option. Since I've ported > this code to -current, most of the porting work for ALTQ to -current is > done except for one or two small compile nits (a problem with a change > in queuing macros). I haven't had time to test ALTQ yet, and it's not the > latest version. If anyone using -current is interested in having a look > at it, my patches are available here, but keep in mind that they include > IPv6 patches too : > > ftp://frmug.org/ipv6/ > > > 2. IPv6 support > > Make use of IPv6 features (e.g, flowlabel) > > Also, I feel that when we incorporate IPv6 is a good opportunity > > to incorporate various other networking research outputs (e.g., > > RED, ECN, diff-serv) into the existing platforms. > > Some of this (at least RED and ECN) is in the INRIA IPv6 too. About > the same status as ALTQ regarding my port to -current (barely compile, > untested). If there are any testers out there, they're more than > welcome ! > -- > Pierre Beyssac pb@fasterix.frmug.org pb@fasterix.freenix.org > {Free,Net,Open}BSD, Linux : il y a moins bien, mais c'est plus cher > Free domains: http://www.eu.org/ or mail dns-manager@EU.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 10:37:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA06910 for freebsd-current-outgoing; Fri, 17 Apr 1998 10:37:22 -0700 (PDT) (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 RAA06902; Fri, 17 Apr 1998 17:37:16 GMT (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA12882; Fri, 17 Apr 1998 10:36:24 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd012869; Fri Apr 17 17:36:20 1998 Message-ID: <353791D6.FF6D5DF@whistle.com> Date: Fri, 17 Apr 1998 10:31:02 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: Poul-Henning Kamp CC: current@FreeBSD.ORG Subject: Re: DEVFS problem... References: <2460.892799398@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: > > 3.0-current machine > > compile kernel with DEVFS > boot -sv > mount -t devfs /dev /dev > ^D > > Kernel prints: > bad-rev_link > > and userland prints: > /dev/wd0s1a on /: Specified device does not match mounted device. > > /etc/fstab contains: > > /dev/wd0s1a / ufs rw 1 1 > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message devfs on it's own will no longer work.. the rest of the puzzle is in the SLICE code that needs to be downloaded from: http://www.freebsd.org/~julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 10:37:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA07041 for freebsd-current-outgoing; Fri, 17 Apr 1998 10:37:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA06992 for ; Fri, 17 Apr 1998 17:37:46 GMT (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id RAA08755 for ; Fri, 17 Apr 1998 17:37:42 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id TAA08873; Fri, 17 Apr 1998 19:37:38 +0200 (MET DST) Message-ID: <19980417193737.36274@follo.net> Date: Fri, 17 Apr 1998 19:37:37 +0200 From: Eivind Eklund To: current@FreeBSD.ORG Subject: Bug in sh? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --- Tear Here (start) --- #!/bin/sh eval `SHELL=sh && export SHELL && tset -s -Q \?$TERM < /dev/tty` echo $TERM --- Tear Here (end) --- and --- Tear Here (start) --- #!/bin/sh . < Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10052 for freebsd-current-outgoing; Fri, 17 Apr 1998 10:47:24 -0700 (PDT) (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 RAA10046; Fri, 17 Apr 1998 17:47:23 GMT (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA13131; Fri, 17 Apr 1998 10:43:05 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd013128; Fri Apr 17 17:43:05 1998 Message-ID: <3537936E.31DFF4F5@whistle.com> Date: Fri, 17 Apr 1998 10:37:50 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: sos@FreeBSD.ORG CC: current@FreeBSD.ORG Subject: Re: DEVFS, DEVFS_ROOT doesn't help: References: <199804170842.KAA03375@sos.freebsd.dk> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG S?ren Schmidt wrote: > > In reply to Poul-Henning Kamp who wrote: > > > > Same machine, added DEVFS_ROOT to kernel, now I get > > > > ffs_mountroot: can't find rootvperror2: panic: cannot mount root(2) > > Who was it that said he was running production on this ???? THAT is not what I an running. That is the result of bitrot due to the fact that I can't check int he correct code because some people won't let me. > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team > Even more code to hack -- will it ever end > .. > > 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 Apr 17 10:47:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10142 for freebsd-current-outgoing; Fri, 17 Apr 1998 10:47:57 -0700 (PDT) (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 RAA10123; Fri, 17 Apr 1998 17:47:44 GMT (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA13087; Fri, 17 Apr 1998 10:41:25 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd013080; Fri Apr 17 17:41:16 1998 Message-ID: <35379301.ABD322C@whistle.com> Date: Fri, 17 Apr 1998 10:36:01 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: Mike Smith CC: sos@FreeBSD.ORG, Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: DEVFS, DEVFS_ROOT doesn't help: References: <199804171329.GAA00385@antipodes.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: > > > In reply to Poul-Henning Kamp who wrote: > > > > > > Same machine, added DEVFS_ROOT to kernel, now I get > > > > > > ffs_mountroot: can't find rootvperror2: panic: cannot mount root(2) DEVFS_ROOT does not exist in the SLICE/DEVFS code so obviously you are not running the SLICE/DEVFS code. > > > > Who was it that said he was running production on this ???? Me but not what is checked in that has severe bitrot.. Since you won't let me check in the final product, obviously you need to get the patches to make it work from: http://www.freebsd.org/~julian it worked fine as of last week, > > I think you'll find that these are mostly related to the changes I > recently made regarding root mounts. no it's just that DEVFS_ROOT id deprecated and you need to have the SLICE code and devfs fixes instead. > > Note that if the DEVFS/SLICE code had been in the -current tree when I > made these changes, it would have been updated as a matter 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 12:16:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA05740 for freebsd-current-outgoing; Fri, 17 Apr 1998 12:16:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA05733 for ; Fri, 17 Apr 1998 19:16:20 GMT (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id VAA04412; Fri, 17 Apr 1998 21:16:11 +0200 (MEST) (envelope-from sos) Message-Id: <199804171916.VAA04412@sos.freebsd.dk> Subject: Re: DEVFS, DEVFS_ROOT doesn't help: In-Reply-To: <3537936E.31DFF4F5@whistle.com> from Julian Elischer at "Apr 17, 98 10:37:50 am" To: julian@whistle.com (Julian Elischer) Date: Fri, 17 Apr 1998 21:16:11 +0200 (MEST) Cc: current@FreeBSD.ORG (FreeBSD current) From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (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 In reply to Julian Elischer who wrote: > S?ren Schmidt wrote: > > > > In reply to Poul-Henning Kamp who wrote: > > > > > > Same machine, added DEVFS_ROOT to kernel, now I get > > > > > > ffs_mountroot: can't find rootvperror2: panic: cannot mount root(2) > > > > Who was it that said he was running production on this ???? > > THAT is not what I an running. What I tried once was YOUR patches, not whats in current, and I'm pretty sure thats what Poul-Henning did too. > That is the result of bitrot due to > the fact that I can't check int he correct code because some > people won't let me. The bitrot might also be in your patches :), they are from feb 24 and lots of stuff has happend in this area since then. Talking about bitrot, the DEVFS in current is YOUR code, but you failed to keep it alive, show us that it will be better this time, and belive me it will go in, infact thats a promise... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 12:38:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA10985 for freebsd-current-outgoing; Fri, 17 Apr 1998 12:38:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA10904; Fri, 17 Apr 1998 19:37:58 GMT (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id VAA04642; Fri, 17 Apr 1998 21:36:53 +0200 (CEST) To: sos@FreeBSD.ORG cc: julian@whistle.com (Julian Elischer), current@FreeBSD.ORG (FreeBSD current) Subject: Re: DEVFS, DEVFS_ROOT doesn't help: In-reply-to: Your message of "Fri, 17 Apr 1998 21:16:11 +0200." <199804171916.VAA04412@sos.freebsd.dk> Date: Fri, 17 Apr 1998 21:36:53 +0200 Message-ID: <4640.892841813@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199804171916.VAA04412@sos.freebsd.dk>, Søren Schmidt writes: >In reply to Julian Elischer who wrote: >> S?ren Schmidt wrote: >> > >> > In reply to Poul-Henning Kamp who wrote: >> > > >> > > Same machine, added DEVFS_ROOT to kernel, now I get >> > > >> > > ffs_mountroot: can't find rootvperror2: panic: cannot mount root(2) >> > >> > Who was it that said he was running production on this ???? >> >> THAT is not what I an running. > >What I tried once was YOUR patches, not whats in current, and I'm >pretty sure thats what Poul-Henning did too. I wasn't aware that the SLICE stuff were needed at this time, but I'm trying it now, and it still doesn't look good. >The bitrot might also be in your patches :), they are from feb 24 >and lots of stuff has happend in this area since then. Indeed. >Talking about bitrot, the DEVFS in current is YOUR code, but you >failed to keep it alive, show us that it will be better this >time, and belive me it will go in, infact thats a promise... you forgot the "(with an omnious voice) Or..." bit Soren... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 13:12:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18043 for freebsd-current-outgoing; Fri, 17 Apr 1998 13:12:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA18037 for ; Fri, 17 Apr 1998 20:12:45 GMT (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0yQHUk-0003E4-00; Fri, 17 Apr 1998 13:12:22 -0700 Date: Fri, 17 Apr 1998 13:12:19 -0700 (PDT) From: Tom To: Kenjiro Cho cc: Julian Elischer , current@FreeBSD.ORG Subject: Re: Networking strategy for -current In-Reply-To: <199804171244.VAA14149@hotaka.csl.sony.co.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 Fri, 17 Apr 1998, Kenjiro Cho wrote: > Julian, > > Thank you for your interest in ALTQ. > (for those who don't know about it, ALTQ is a queueing framework to > control network traffic. The related information is available at > http://www.csl.sony.co.jp/person/kjc/software.html) Actually, can you get a properly assigned major number? The conflict with the dpt driver is a bit of problem (yes the dpt driver does exist). I belive Jordon should be able to allocate a major number for ALTQ. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 13:16:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18570 for freebsd-current-outgoing; Fri, 17 Apr 1998 13:16:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA18522; Fri, 17 Apr 1998 20:16:14 GMT (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id WAA04819; Fri, 17 Apr 1998 22:15:09 +0200 (CEST) cc: sos@FreeBSD.ORG, julian@whistle.com (Julian Elischer), current@FreeBSD.ORG (FreeBSD current) Subject: Re: DEVFS, DEVFS_ROOT doesn't help: In-reply-to: Your message of "Fri, 17 Apr 1998 21:36:53 +0200." <4640.892841813@critter.freebsd.dk> Date: Fri, 17 Apr 1998 22:15:09 +0200 Message-ID: <4817.892844109@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <4640.892841813@critter.freebsd.dk>, Poul-Henning Kamp writes: >In message <199804171916.VAA04412@sos.freebsd.dk>, Søren Schmidt writes: >>In reply to Julian Elischer who wrote: >>> S?ren Schmidt wrote: >>> > >>> > In reply to Poul-Henning Kamp who wrote: >>> > > >>> > > Same machine, added DEVFS_ROOT to kernel, now I get >>> > > >>> > > ffs_mountroot: can't find rootvperror2: panic: cannot mount root(2) >>> > >>> > Who was it that said he was running production on this ???? >>> >>> THAT is not what I an running. >> >>What I tried once was YOUR patches, not whats in current, and I'm >>pretty sure thats what Poul-Henning did too. > >I wasn't aware that the SLICE stuff were needed at this time, >but I'm trying it now, and it still doesn't look good. Well, I think I have it running on a one IDE disk machine here now, It's doing a make world overnight... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 13:39:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22263 for freebsd-current-outgoing; Fri, 17 Apr 1998 13:39:49 -0700 (PDT) (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 UAA22256 for ; Fri, 17 Apr 1998 20:39:47 GMT (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA18573; Fri, 17 Apr 1998 13:36:20 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd018568; Fri Apr 17 20:36:10 1998 Message-ID: <3537BBFF.4487EB71@whistle.com> Date: Fri, 17 Apr 1998 13:30:55 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: Tom CC: Kenjiro Cho , current@FreeBSD.ORG Subject: Re: Networking strategy for -current References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tom wrote: > > On Fri, 17 Apr 1998, Kenjiro Cho wrote: > > > Julian, > > > > Thank you for your interest in ALTQ. > > (for those who don't know about it, ALTQ is a queueing framework to > > control network traffic. The related information is available at > > http://www.csl.sony.co.jp/person/kjc/software.html) > > Actually, can you get a properly assigned major number? The conflict > with the dpt driver is a bit of problem (yes the dpt driver does exist). > I belive Jordon should be able to allocate a major number for ALTQ. > > Tom Actually I just did that.. altq has undisputed use of 96 in 2.2 and 3.0 as long as it needs it. hopefully that will save Kenjiro Cho from continually chasing it.. (I already use 20 here for local devices) julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 14:12:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28510 for freebsd-current-outgoing; Fri, 17 Apr 1998 14:12:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA28504 for ; Fri, 17 Apr 1998 21:12:40 GMT (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id XAA29081 for ; Fri, 17 Apr 1998 23:12:35 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Fri, 17 Apr 1998 23:12:34 +0200 (MET DST) Mime-Version: 1.0 To: current@FreeBSD.ORG Subject: kern/6184 Organization: Gutteklubben Terrasse / KRST / PUMS / YASMW X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-Stop-Spam: http://www.cauce.org From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 17 Apr 1998 23:12:34 +0200 Message-ID: Lines: 65 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a patch which I hope fixes kern/6184 (lseek allows seeks to negative offsets), but I don't want to commit it without having someone look at it first: Index: src/sys/kern/vfs_syscalls.c =================================================================== RCS file: /home/ncvs/src/sys/kern/vfs_syscalls.c,v retrieving revision 1.97 diff -u -r1.97 vfs_syscalls.c --- vfs_syscalls.c 1998/04/08 18:31:57 1.97 +++ vfs_syscalls.c 1998/04/17 21:03:13 @@ -1324,6 +1324,7 @@ register struct filedesc *fdp = p->p_fd; register struct file *fp; struct vattr vattr; + off_t ofs; int error; if ((u_int)SCARG(uap, fd) >= fdp->fd_nfiles || @@ -1333,21 +1334,22 @@ return (ESPIPE); switch (SCARG(uap, whence)) { case L_INCR: - fp->f_offset += SCARG(uap, offset); + ofs = fp->f_offset + SCARG(uap, offset); break; case L_XTND: error=VOP_GETATTR((struct vnode *)fp->f_data, &vattr, cred, p); if (error) return (error); - fp->f_offset = SCARG(uap, offset) + vattr.va_size; + ofs = SCARG(uap, offset) + vattr.va_size; break; case L_SET: - fp->f_offset = SCARG(uap, offset); + ofs = SCARG(uap, offset); break; default: return (EINVAL); } - *(off_t *)(p->p_retval) = fp->f_offset; + if (ofs < 0) return (EINVAL); + *(off_t *)(p->p_retval) = fp->f_offset = ofs; return (0); } Index: src/lib/libc/sys/lseek.2 =================================================================== RCS file: /home/ncvs/src/lib/libc/sys/lseek.2,v retrieving revision 1.6 diff -u -r1.6 lseek.2 --- lseek.2 1997/02/22 15:04:01 1.6 +++ lseek.2 1998/04/17 21:05:23 @@ -120,7 +120,7 @@ is associated with a pipe, socket, or FIFO. .It Bq Er EINVAL .Fa Whence -is not a proper value. +is not a proper value, or the resulting offset is negative. .El .Sh SEE ALSO .Xr dup 2 , -- Nobody else has a .sig like this one. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 15:48:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24550 for freebsd-current-outgoing; Fri, 17 Apr 1998 15:48:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA24543; Fri, 17 Apr 1998 22:48:46 GMT (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id PAA14061; Fri, 17 Apr 1998 15:48:33 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Julian Elischer cc: sos@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: DEVFS, DEVFS_ROOT doesn't help: In-reply-to: Your message of "Fri, 17 Apr 1998 10:37:50 PDT." <3537936E.31DFF4F5@whistle.com> Date: Fri, 17 Apr 1998 15:48:33 -0700 Message-ID: <14058.892853313@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > THAT is not what I an running. That is the result of bitrot due to > the fact that I can't check int he correct code because some > people won't let me. What? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 15:50:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24749 for freebsd-current-outgoing; Fri, 17 Apr 1998 15:50:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fang.cs.sunyit.edu (perlsta@fang.cs.sunyit.edu [192.52.220.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA24717 for ; Fri, 17 Apr 1998 22:50:04 GMT (envelope-from perlsta@fang.cs.sunyit.edu) Received: from localhost (perlsta@localhost) by fang.cs.sunyit.edu (8.8.5/8.7.3) with SMTP id RAA10375; Fri, 17 Apr 1998 17:51:04 GMT Date: Fri, 17 Apr 1998 17:51:04 +0000 (GMT) From: Alfred Perlstein To: "Alok K. Dhir" cc: brandon@engulf.com, current@FreeBSD.ORG Subject: Re: Problems w/ Linux EMU In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG no, "man brandelf" but the linux emu is quite borked in -current it seems. a LOT of stuff stopped working right about a month ago. -Alfred > You probably need to remake the LKMs and reboot... > > > I am running FreeBSD 3.0-Current last updated on Sunday. For some strange > > reason, my Linux EMU is having problems. (It doesn't recognize the ELF > > binary type). Any clue why this is happening? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 15:55:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA26116 for freebsd-current-outgoing; Fri, 17 Apr 1998 15:55:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from proxy.metro.tas.com.au ([147.109.165.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA26085 for ; Fri, 17 Apr 1998 22:55:16 GMT (envelope-from kerry.morse@metro.tas.com.au) Received: from mttmail.metro.tas.com.au (MTTMail.metro.tas.com.au [147.109.164.249]) by proxy.metro.tas.com.au (8.8.8/8.8.5) with ESMTP id IAA08691 for ; Sat, 18 Apr 1998 08:54:29 +1000 (EST) Received: by MTTMail.metro.tas.gov.au with Internet Mail Service (5.0.1458.49) id ; Sat, 18 Apr 1998 08:54:30 +1000 Message-ID: <02B01380C828D1119ED70020AF641C53068561@MTTMail.metro.tas.gov.au> From: Kerry Morse To: "'freebsd-current@FreeBSD.ORG'" Subject: RE: Help - please... Adaptec 1542 and Exabyte tape problem... Date: Sat, 18 Apr 1998 08:54:30 +1000 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > So basically it's not going to work for at least a while or a few > fixes > > so swapping the controller out over with a PCI controller while no > ones > > looking is my best solution at present... > > I've just found a whole mess of bounce buffer bitrot in the existing > scsi > code and applied some bandaids. I can't test some of the more obscure > > drivers, but an aha1542B + sd0/sd1/st0/cd0 now seems to work fine. > Before, talking to the tape would fail 50% of the time at startup. > > Ironically, I think I to blame for a good chunk of the original > breakage. > The scsi base code (scsi_scsi_cmd() specifically) had some patchwork > to > detect data transfers to/from the per-process kernel stack and how to > manually bounce them. When I moved the kernel stack out of user space > > last year some time, the glue code that checked for requests on the > kstack > no longer worked as it used assumptions about the VM space layout that > were no longer true. However, there was bitrot in other drivers too, > notably worm, ch and st. > > OK, is there a 'patch' I can apply or do I need to pull a whole new > image of > FreeBSD??, currently running the 980414 SNAP.... > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 16:02:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA28123 for freebsd-current-outgoing; Fri, 17 Apr 1998 16:02:08 -0700 (PDT) (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 XAA28031 for ; Fri, 17 Apr 1998 23:01:58 GMT (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id PAA01087; Fri, 17 Apr 1998 15:57:38 -0700 (PDT) Message-Id: <199804172257.PAA01087@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Alfred Perlstein cc: "Alok K. Dhir" , brandon@engulf.com, current@FreeBSD.ORG Subject: Re: Problems w/ Linux EMU In-reply-to: Your message of "Fri, 17 Apr 1998 17:51:04 -0000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 17 Apr 1998 15:57:36 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > no, "man brandelf" > but the linux emu is quite borked in -current it seems. > > a LOT of stuff stopped working right about a month ago. Really? Where have your problem reports been then? -- \\ 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 Apr 17 16:09:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01151 for freebsd-current-outgoing; Fri, 17 Apr 1998 16:09:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cerebus.nectar.com (cerebus.nectar.com [204.27.67.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA01091 for ; Fri, 17 Apr 1998 23:09:49 GMT (envelope-from nectar@cerebus.nectar.com) Received: from cerebus.nectar.com (localhost.communique.net [127.0.0.1]) by cerebus.nectar.com (8.8.8/8.8.8) with ESMTP id SAA28873; Fri, 17 Apr 1998 18:09:05 -0500 (CDT) Message-Id: <199804172309.SAA28873@cerebus.nectar.com> X-Mailer: exmh version 2.0.2 2/24/98 From: Jacques Vidrine To: Alfred Perlstein cc: "Alok K. Dhir" , brandon@engulf.com, current@FreeBSD.ORG Subject: Re: Problems w/ Linux EMU In-reply-to: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 17 Apr 1998 18:09:05 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Huh, Linux emulation has been working fine for me since I began to use it about a week ago ... I'm currently running -current sources from 4/14/1998 morning. The StarOffice applications are what I'm running. Just a datapoint. Jacques Vidrine On 17 April 1998 at 17:51, Alfred Perlstein wrote: > no, "man brandelf" > but the linux emu is quite borked in -current it seems. > > a LOT of stuff stopped working right about a month ago. > > -Alfred > > > You probably need to remake the LKMs and reboot... > > > > > I am running FreeBSD 3.0-Current last updated on Sunday. For some strang e > > > reason, my Linux EMU is having problems. (It doesn't recognize the ELF > > > binary type). Any clue why this is happening? > > > 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 Apr 17 16:30:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA07615 for freebsd-current-outgoing; Fri, 17 Apr 1998 16:30:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from engulf.com (engulf.com [207.96.124.102]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA07509 for ; Fri, 17 Apr 1998 23:30:20 GMT (envelope-from brandon@engulf.com) Received: from localhost (brandon@localhost) by engulf.com (8.8.8/8.8.7) with SMTP id TAA16667 for ; Fri, 17 Apr 1998 19:27:31 -0400 (EDT) Date: Fri, 17 Apr 1998 19:27:31 -0400 (EDT) From: Brandon Lockhart To: current@FreeBSD.ORG Subject: Linux EMU errors. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG engulf[21]:/usr/src# linux /lkm/linux_mod.o: Undefined symbol `_getmicrotime' referenced from text segment /lkm/linux_mod.o: Undefined symbol `_getmicrotime' referenced from text segment /lkm/linux_mod.o: Undefined symbol `_microruntime' referenced from text segment /lkm/linux_mod.o: Undefined symbol `_sched_setparam' referenced from data segment /lkm/linux_mod.o: Undefined symbol `_sched_getparam' referenced from data segment /lkm/linux_mod.o: Undefined symbol `_sched_setscheduler' referenced from data segment /lkm/linux_mod.o: Undefined symbol `_sched_getscheduler' referenced from data segment /lkm/linux_mod.o: Undefined symbol `_sched_yield' referenced from data segment /lkm/linux_mod.o: Undefined symbol `_sched_get_priority_max' referenced from data segment /lkm/linux_mod.o: Undefined symbol `_sched_get_priority_min' referenced from data segment /lkm/linux_mod.o: Undefined symbol `_sched_rr_get_interval' referenced from data segment modload: /usr/bin/ld: return code 1 engulf[22]:/usr/src# modstat Type Id Off Loadaddr Size Info Rev Module Name MISC 0 0 f49fa000 0008 f49fb000 1 green_saver_mod engulf[23]:/usr/src# uname -a FreeBSD engulf.com 3.0-CURRENT FreeBSD 3.0-CURRENT #3: Tue Mar 24 22:41:46 EST 1998 root@engulf.com:/usr/src/sys/compile/ENGULF i386 This system was CVSup'ed on April 17, 1998. (Today) ,----------------------. | Brandon Lockhart | `----------,-----------'------------. | brandon@engulf.com | `------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 16:42:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA11482 for freebsd-current-outgoing; Fri, 17 Apr 1998 16:42:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from engulf.com (engulf.com [207.96.124.102]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA11433 for ; Fri, 17 Apr 1998 23:41:55 GMT (envelope-from brandon@engulf.com) Received: from localhost (brandon@localhost) by engulf.com (8.8.8/8.8.7) with SMTP id TAA00311 for ; Fri, 17 Apr 1998 19:38:05 -0400 (EDT) Date: Fri, 17 Apr 1998 19:38:05 -0400 (EDT) From: Brandon Lockhart To: current@FreeBSD.ORG Subject: 3.0-current PS error. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG engulf[1]:~# ps ps: proc size mismatch (17928 total, 688 chunks) ,----------------------. | Brandon Lockhart | `----------,-----------'------------. | brandon@engulf.com | `------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 16:49:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA13189 for freebsd-current-outgoing; Fri, 17 Apr 1998 16:49:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA13166 for ; Fri, 17 Apr 1998 23:49:37 GMT (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id XAA19299; Fri, 17 Apr 1998 23:49:24 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id BAA09956; Sat, 18 Apr 1998 01:49:23 +0200 (MET DST) Message-ID: <19980418014923.21848@follo.net> Date: Sat, 18 Apr 1998 01:49:23 +0200 From: Eivind Eklund To: Brandon Lockhart , current@FreeBSD.ORG Subject: Re: 3.0-current PS error. References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Brandon Lockhart on Fri, Apr 17, 1998 at 07:38:05PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 17, 1998 at 07:38:05PM -0400, Brandon Lockhart wrote: > engulf[1]:~# ps > ps: proc size mismatch (17928 total, 688 chunks) Pilot error. Build the world and the kernel, not one or the other (unless you know what you're doing.) In this case, it is a change of proc size (gee, wasn't that news) - you have to re-compile at least libkvm and all group kmem programs with the new includes. The easiest way is by making the world. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 17:07:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17771 for freebsd-current-outgoing; Fri, 17 Apr 1998 17:07:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fang.cs.sunyit.edu (perlsta@fang.cs.sunyit.edu [192.52.220.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA17676 for ; Sat, 18 Apr 1998 00:07:13 GMT (envelope-from perlsta@fang.cs.sunyit.edu) Received: from localhost (perlsta@localhost) by fang.cs.sunyit.edu (8.8.5/8.7.3) with SMTP id TAA11277; Fri, 17 Apr 1998 19:07:54 GMT Date: Fri, 17 Apr 1998 19:07:54 +0000 (GMT) From: Alfred Perlstein To: Mike Smith cc: current@FreeBSD.ORG Subject: Re: Problems w/ Linux EMU In-Reply-To: <199804172257.PAA01087@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 > > no, "man brandelf" > > but the linux emu is quite borked in -current it seems. > > > > a LOT of stuff stopped working right about a month ago. > > Really? Where have your problem reports been then? mostly that i get "leaking" shared memory, this has been a problem as of a month ago or so. after staroffice 4 has been running for a few seconds it locks up and i do a ipcs and see all my shared segments are used up. this also happens with x11amp after every song it plays, it looses a segment every time a new song is loaded. (x11amp has stopped working even this well, it now doesn't even play music it seems) i might just be messing myself up, because i dumped an extra shared lib into my linux dirs recently, i'm going to clean shop, then reinstall the linux libs. but a few other users get this problem, and some don't. also linux programs attempting to use raw sockets don't seem to work anymore. all this "breakage" (for me) seems to have occured about a month or so ago. thank you, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 17:10:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA18831 for freebsd-current-outgoing; Fri, 17 Apr 1998 17:10:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA18783 for ; Sat, 18 Apr 1998 00:10:51 GMT (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id RAA14856; Fri, 17 Apr 1998 17:10:11 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Brandon Lockhart cc: current@FreeBSD.ORG Subject: Re: 3.0-current PS error. In-reply-to: Your message of "Fri, 17 Apr 1998 19:38:05 EDT." Date: Fri, 17 Apr 1998 17:10:10 -0700 Message-ID: <14852.892858210@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I sure hope to hell you thought to upgrade both the kernel and the binaries (via make world) at the same time or both of your messages to -current are most bogus indeed. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 17:22:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA21122 for freebsd-current-outgoing; Fri, 17 Apr 1998 17:22:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shell3.ba.best.com (root@shell3.ba.best.com [206.184.139.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA21054 for ; Sat, 18 Apr 1998 00:21:59 GMT (envelope-from schrade@schrade.com) Received: from localhost (schrade@localhost [127.0.0.1]) by shell3.ba.best.com (8.8.8/8.8.BEST) with SMTP id RAA29263; Fri, 17 Apr 1998 17:20:52 -0700 (PDT) Date: Fri, 17 Apr 1998 17:20:52 -0700 (PDT) From: Ken Krebs To: Brandon Lockhart cc: current@FreeBSD.ORG Subject: Re: Linux EMU errors. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 17 Apr 1998, Brandon Lockhart wrote: >engulf[21]:/usr/src# linux >/lkm/linux_mod.o: Undefined symbol `_getmicrotime' referenced from text segment >/lkm/linux_mod.o: Undefined symbol `_getmicrotime' referenced from text segment [...linux error spew deleted..] >This system was CVSup'ed on April 17, 1998. (Today) Did you make world & also build a new kernel? Also, if you want to get Quake 2 working, you'll need the diffs Stephen Hocking sent to the list. They're available for ftp from my ftp site, too. ftp://ftp.schrade.com/pub/unix/patches/linuxdiffs.tar.gz You'll need to do something like this inside the /sys/i386/linux dir: patch -f <../linux.h.diff patch -f <../linux_dummy.c.diff patch -f <../linux_ioctl.c.diff patch -f <../linux_misc.c.diff patch -f <../syscalls.master.diff make linux_sysent.c *********** NewOrderDepecheModeUltravoxViolentFemmesKillingJoke ************* * Ken * NineInchNailsFront242TangerineDreamTheBreedersTekno * * * Krebs * SkinnyPuppyLaTourBauhausBookOfLoveModernEnglishB52s * * *********** FishBoneBigCountryJoyDivisonSiouxsie&TheBansheesXTC ************* IRC: Schrade E-Mail: schrade@schrade.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 17:57:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25761 for freebsd-current-outgoing; Fri, 17 Apr 1998 17:57:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA25676 for ; Sat, 18 Apr 1998 00:57:31 GMT (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.7) with ESMTP id BAA21776; Sat, 18 Apr 1998 01:41:09 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199804180041.BAA21776@awfulhak.org> X-Mailer: exmh version 2.0.1 12/23/97 To: Eivind Eklund cc: current@FreeBSD.ORG Subject: Re: Bug in sh? In-reply-to: Your message of "Fri, 17 Apr 1998 19:37:37 +0200." <19980417193737.36274@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 18 Apr 1998 01:41:08 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [.....] > #!/bin/sh > . < `SHELL=sh && export SHELL && tset -s -Q \?$TERM < /dev/tty` > EOF [.....] > The second version doesn't work - it exits immediately, and seems to > run tset _after_ the shell has quit. This isn't a bug as you describe it. IMHO, the bug is that the shell doesn't complain that you've failed to pass ``.'' a file name. If the above syntax was ok, then command | . would also be ok (although the same as ``command | sh'' unless you're running a *real* ksh) :-/ Anyway, it just looks weird. > Eivind. -- 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 Apr 17 18:08:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA28402 for freebsd-current-outgoing; Fri, 17 Apr 1998 18:08:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA28267 for ; Sat, 18 Apr 1998 01:07:39 GMT (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id BAA21154; Sat, 18 Apr 1998 01:07:27 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id DAA00426; Sat, 18 Apr 1998 03:07:27 +0200 (MET DST) Message-ID: <19980418030726.52891@follo.net> Date: Sat, 18 Apr 1998 03:07:26 +0200 From: Eivind Eklund To: Brian Somers Cc: current@FreeBSD.ORG Subject: Re: Bug in sh? References: <19980417193737.36274@follo.net> <199804180041.BAA21776@awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199804180041.BAA21776@awfulhak.org>; from Brian Somers on Sat, Apr 18, 1998 at 01:41:08AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Apr 18, 1998 at 01:41:08AM +0100, Brian Somers wrote: > [.....] > > #!/bin/sh > > . < > `SHELL=sh && export SHELL && tset -s -Q \?$TERM < /dev/tty` > > EOF > [.....] > > The second version doesn't work - it exits immediately, and seems to > > run tset _after_ the shell has quit. > > This isn't a bug as you describe it. IMHO, the bug is that the shell > doesn't complain that you've failed to pass ``.'' a file name. My fault. I always forget that < Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA29299 for freebsd-current-outgoing; Fri, 17 Apr 1998 18:12:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from coleridge.kublai.com (coleridge.kublai.com [207.96.1.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA29205; Sat, 18 Apr 1998 01:11:16 GMT (envelope-from shmit@natasya.kublai.com) Received: from natasya.kublai.com (natasya.kublai.com [207.172.25.236]) by coleridge.kublai.com (8.8.8/8.8.8) with ESMTP id VAA18683; Fri, 17 Apr 1998 21:10:57 -0400 (EDT) (envelope-from shmit@natasya.kublai.com) Received: (from shmit@localhost) by natasya.kublai.com (8.8.8/8.8.8) id VAA12858; Fri, 17 Apr 1998 21:10:56 -0400 (EDT) Message-ID: <19980417211055.27018@kublai.com> Date: Fri, 17 Apr 1998 21:10:55 -0400 From: Brian Cully To: Julian Elischer , sos@FreeBSD.ORG Cc: current@FreeBSD.ORG, kjc@csl.sony.co.jp Subject: Re: Networking strategy for -current Reply-To: shmit@kublai.com References: <199804170633.IAA03123@sos.freebsd.dk> <3536F91A.446B9B3D@whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <3536F91A.446B9B3D@whistle.com>; from Julian Elischer on Thu, Apr 16, 1998 at 11:39:22PM -0700 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 Thu, Apr 16, 1998 at 11:39:22PM -0700, Julian Elischer wrote: > I hope to get together with Mike smith in the next week to try > knock out some of the devfs nits. > > As far as I'm concerned it's working. (I use it in production > every day.) > But thre are a few cosmetic things that need to be done. > > Have you tried it? I haven't seen a crash out of it since december. If I boot with options DEVFS_ROOT my kernel panics with `unable to mount root'. I've been holding off on sending anything until I can spend some time debugging the issue. It may very well be something I'm doing wrong, but there are NO docs on this particular subject (not even in LINT, although I'm inclined to say that there oughta be something in section 4 or 9 of the man pages). -- Brian Cully ``And when one of our comrades was taken prisoner, blindfolded, hung upside-down, shot, and burned, we thought to ourselves, `These are the best experiences of our lives''' -Pathology (Joe Frank, Somewhere Out There) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 18:30:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA02745 for freebsd-current-outgoing; Fri, 17 Apr 1998 18:30:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA02734 for ; Sat, 18 Apr 1998 01:29:55 GMT (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.7) with ESMTP id CAA24475; Sat, 18 Apr 1998 02:29:47 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199804180129.CAA24475@awfulhak.org> X-Mailer: exmh version 2.0.1 12/23/97 To: Eivind Eklund cc: Brian Somers , current@FreeBSD.ORG Subject: Re: Bug in sh? In-reply-to: Your message of "Sat, 18 Apr 1998 03:07:26 +0200." <19980418030726.52891@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 18 Apr 1998 02:29:47 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, Apr 18, 1998 at 01:41:08AM +0100, Brian Somers wrote: > > [.....] > > > #!/bin/sh > > > . < > > `SHELL=sh && export SHELL && tset -s -Q \?$TERM < /dev/tty` > > > EOF > > [.....] > > > The second version doesn't work - it exits immediately, and seems to > > > run tset _after_ the shell has quit. > > > > This isn't a bug as you describe it. IMHO, the bug is that the shell > > doesn't complain that you've failed to pass ``.'' a file name. > > My fault. I always forget that < (as it ought to, and used to in my old world), but instead is just one more > way of putting things at stdin. > > . still shouldn't just continue, and run the command in a second fork > . _after_ the initial shell script has quit. That _has_ to be a bug? Agreed. > Eivind. -- 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 Apr 17 18:32:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA03062 for freebsd-current-outgoing; Fri, 17 Apr 1998 18:32:58 -0700 (PDT) (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 BAA03045 for ; Sat, 18 Apr 1998 01:32:51 GMT (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.8.8/8.8.8) with ESMTP id CAA01426 for ; Sat, 18 Apr 1998 02:32:49 +0100 (BST) (envelope-from kpielorz@tdx.co.uk) Message-ID: <353802A2.CB67FCE7@tdx.co.uk> Date: Sat, 18 Apr 1998 02:32:18 +0100 From: Karl Pielorz Organization: TDX X-Mailer: Mozilla 4.04 [en] (WinNT; I) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Quick Question re: Dmesg & Current Version Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the dmesg for my system I get: FreeBSD 3.0-CURRENT #5: Fri Apr 17 20:25:58 BST 1998 What does the '#5' refer to? - I presume the Date & Time is the build time - I'm just starting to get to grips with CVSup - is there anywhere it stores the date & time that the source was last updated? - Rather than the last build time? Regards, Karl Pielorz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 19:05:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA07634 for freebsd-current-outgoing; Fri, 17 Apr 1998 19:05:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA07618 for ; Sat, 18 Apr 1998 02:05:30 GMT (envelope-from grog@lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id LAA06143; Sat, 18 Apr 1998 11:35:04 +0930 (CST) (envelope-from grog) Message-ID: <19980418113504.U1090@freebie.lemis.com> Date: Sat, 18 Apr 1998 11:35:04 +0930 From: Greg Lehey To: Karl Pielorz , current@FreeBSD.ORG Subject: Re: Quick Question re: Dmesg & Current Version References: <353802A2.CB67FCE7@tdx.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <353802A2.CB67FCE7@tdx.co.uk>; from Karl Pielorz on Sat, Apr 18, 1998 at 02:32:18AM +0100 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 18 April 1998 at 2:32:18 +0100, Karl Pielorz wrote: > In the dmesg for my system I get: > > FreeBSD 3.0-CURRENT #5: Fri Apr 17 20:25:58 BST 1998 > > What does the '#5' refer to? It's the version number. Each time you build a kernel, the number is incremented. Look at the file /sys/compile/YOURKERNEL/version. > I'm just starting to get to grips with CVSup - is there anywhere it stores > the date & time that the source was last updated? - Rather than the last > build time? Somewhere, probably. When I used ctm, I modified /sys/conf/newvers.sh to include the ctm update number in the header, but I haven't found anything useful in the CVS database. Let me know if you do. Greg -- See complete headers for address 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 Fri Apr 17 19:17:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA09326 for freebsd-current-outgoing; Fri, 17 Apr 1998 19:17:41 -0700 (PDT) (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 CAA09308; Sat, 18 Apr 1998 02:17:38 GMT (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id TAA28869; Fri, 17 Apr 1998 19:15:21 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd028864; Sat Apr 18 02:15:11 1998 Message-ID: <35380B75.15FB7483@whistle.com> Date: Fri, 17 Apr 1998 19:09:57 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: shmit@kublai.com CC: sos@FreeBSD.ORG, current@FreeBSD.ORG, kjc@csl.sony.co.jp Subject: Re: Networking strategy for -current References: <199804170633.IAA03123@sos.freebsd.dk> <3536F91A.446B9B3D@whistle.com> <19980417211055.27018@kublai.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Cully wrote: > > On Thu, Apr 16, 1998 at 11:39:22PM -0700, Julian Elischer wrote: > > I hope to get together with Mike smith in the next week to try > > knock out some of the devfs nits. > > > > As far as I'm concerned it's working. (I use it in production > > every day.) > > But thre are a few cosmetic things that need to be done. > > > > Have you tried it? I haven't seen a crash out of it since december. > > If I boot with options DEVFS_ROOT my kernel panics with `unable to > mount root'. I've been holding off on sending anything until I > can spend some time debugging the issue. > > It may very well be something I'm doing wrong, but there are NO > docs on this particular subject (not even in LINT, although I'm > inclined to say that there oughta be something in section 4 or 9 > of the man pages). > > -- > Brian Cully > ``And when one of our comrades was taken prisoner, blindfolded, hung > upside-down, shot, and burned, we thought to ourselves, `These are the > best experiences of our lives''' -Pathology (Joe Frank, Somewhere Out There) how many times do I have to repeat.. I'M not talking about what's int the tree, but rather what is at: http://www.freebsd.org/~julian DEVFS_ROOT is deprecated.. don't use it.. use DEVFS and SLICE instead. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 21:15:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA22929 for freebsd-current-outgoing; Fri, 17 Apr 1998 21:15:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sasami.jurai.net (root@sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA22883 for ; Sat, 18 Apr 1998 04:14:01 GMT (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id AAA16022 for ; Sat, 18 Apr 1998 00:02:57 -0400 (EDT) Date: Sat, 18 Apr 1998 00:02:57 -0400 (EDT) From: "Matthew N. Dodd" To: current@FreeBSD.ORG Subject: DPT EISA shim problems. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I appear to have had a rather serious flaw in my understanding of how to properly probe/attach EISA devices. I'm completly amazed that my code manages to do anything useful in the first place. Currently -most- cards with the EISA ID of DPTA410/0x1214A410 should work. I've only got a PM2022 which works. All other DPT EISA controllers probably don't work. :) I'll be working on rewriting the DPT EISA shim this weekend to do the right thing in probe/attach. At this point I suspect that I'm the only one running any of these cards so this message probably doesn't affect anyone. :) /* Matthew N. Dodd | A memory retaining a love you had for life winter@jurai.net | As cruel as it seems nothing ever seems to http://www.jurai.net/~winter | go right - FLA M 3.1:53 */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 17 23:52:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA13846 for freebsd-current-outgoing; Fri, 17 Apr 1998 23:52:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from widefw.csl.sony.co.jp (widefw.csl.sony.co.jp [133.138.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA13840 for ; Sat, 18 Apr 1998 06:52:29 GMT (envelope-from kjc@csl.sony.co.jp) Received: from hotaka.csl.sony.co.jp (root@hotaka.csl.sony.co.jp [43.27.98.57]) by widefw.csl.sony.co.jp (8.8.8/3.6W) with ESMTP id PAA12534; Sat, 18 Apr 1998 15:52:16 +0900 (JST) Received: from localhost (kjc@[127.0.0.1]) by hotaka.csl.sony.co.jp (8.8.8/3.6W/hotaka/98021914) with ESMTP id PAA23151; Sat, 18 Apr 1998 15:52:15 +0900 (JST) Message-Id: <199804180652.PAA23151@hotaka.csl.sony.co.jp> To: Julian Elischer cc: current@FreeBSD.ORG Subject: Re: Networking strategy for -current In-reply-to: Your message of "Fri, 17 Apr 1998 13:30:55 MST." <3537BBFF.4487EB71@whistle.com> Date: Sat, 18 Apr 1998 15:52:15 +0900 From: Kenjiro Cho Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks Julian, The official major device number for ALTQ makes my life a bit easier! --Kenjiro Tom wrote: > Actually, can you get a properly assigned major number? The conflict > with the dpt driver is a bit of problem (yes the dpt driver does exist). > I belive Jordon should be able to allocate a major number for ALTQ. Jilian wrote: >> Actually I just did that.. >> altq has undisputed use of 96 in 2.2 and 3.0 as long as it needs it. >> hopefully that will save Kenjiro Cho from continually chasing >> it.. (I already use 20 here for local devices) >> julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 18 00:17:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA16311 for freebsd-current-outgoing; Sat, 18 Apr 1998 00:17:20 -0700 (PDT) (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 HAA16306 for ; Sat, 18 Apr 1998 07:17:16 GMT (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id AAA03855; Sat, 18 Apr 1998 00:12:54 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd003852; Sat Apr 18 07:12:53 1998 Date: Sat, 18 Apr 1998 00:07:38 -0700 (PDT) From: Julian Elischer To: Kenjiro Cho cc: current@FreeBSD.ORG Subject: Re: Networking strategy for -current In-Reply-To: <199804180652.PAA23151@hotaka.csl.sony.co.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 do you want my 3.0 patches? seems to work like a treat, except the fxp driver never called altq_dequeue() because it first checked for the existance of packets on the old queue. (which of course was NULL) so packets were queued but never dequeued. this is in fxp_start(); julian On Sat, 18 Apr 1998, Kenjiro Cho wrote: > > Thanks Julian, > > The official major device number for ALTQ makes my life a bit easier! > > --Kenjiro > > Tom wrote: > > Actually, can you get a properly assigned major number? The conflict > > with the dpt driver is a bit of problem (yes the dpt driver does exist). > > I belive Jordon should be able to allocate a major number for ALTQ. > > Jilian wrote: > >> Actually I just did that.. > >> altq has undisputed use of 96 in 2.2 and 3.0 as long as it needs it. > >> hopefully that will save Kenjiro Cho from continually chasing > >> it.. (I already use 20 here for local devices) > > >> julian > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 18 00:57:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA20265 for freebsd-current-outgoing; Sat, 18 Apr 1998 00:57:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA20260 for ; Sat, 18 Apr 1998 07:57:31 GMT (envelope-from rkw@dataplex.net) Received: from [208.2.87.6] (user6.dataplex.net [208.2.87.6]) by shrimp.dataplex.net (8.8.8/8.8.5) with ESMTP id CAA12143; Sat, 18 Apr 1998 02:56:50 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <19980418113504.U1090@freebie.lemis.com> References: <353802A2.CB67FCE7@tdx.co.uk>; from Karl Pielorz on Sat, Apr 18, 1998 at 02:32:18AM +0100 <353802A2.CB67FCE7@tdx.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 18 Apr 1998 02:47:58 -0500 To: Greg Lehey From: Richard Wackerbarth Subject: Re: Quick Question re: Dmesg & Current Version Cc: Karl Pielorz , current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 9:05 PM -0500 4/17/98, Greg Lehey wrote: >On Sat, 18 April 1998 at 2:32:18 +0100, Karl Pielorz wrote: >> In the dmesg for my system I get: >> >> FreeBSD 3.0-CURRENT #5: Fri Apr 17 20:25:58 BST 1998 [...] >> I'm just starting to get to grips with CVSup - is there anywhere it stores >> the date & time that the source was last updated? - Rather than the last >> build time? > >Somewhere, probably. When I used ctm, I modified /sys/conf/newvers.sh >to include the ctm update number in the header, but I haven't found >anything useful in the CVS database. Let me know if you do. Nope. AFAIK, there is nothing there. What is needed is something generated at the MASTER source and propogated through all the distribution chains. I wrote such a change last year, but it was promptly rejected on what I can only conclude were political grounds. (The supposed "technical grounds" were bogus arguments.) Perhaps someone with some clout will reconsider :-( Richard Wackerbarth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 18 04:32:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA18358 for freebsd-current-outgoing; Sat, 18 Apr 1998 04:32:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA18353 for ; Sat, 18 Apr 1998 11:32:10 GMT (envelope-from dag-erli@ifi.uio.no) Received: from bilskirnir.ifi.uio.no (2602@bilskirnir.ifi.uio.no [129.240.64.135]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id NAA18153; Sat, 18 Apr 1998 13:32:06 +0200 (MET DST) Received: (from dag-erli@localhost) by bilskirnir.ifi.uio.no ; Sat, 18 Apr 1998 13:32:05 +0200 (MET DST) Mime-Version: 1.0 To: Tim Vanderhoek Cc: Anatoly Vorobey , current@FreeBSD.ORG Subject: Re: Spelling etc. References: Organization: Gutteklubben Terrasse / KRST / PUMS / YASMW X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-Stop-Spam: http://www.cauce.org From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 18 Apr 1998 13:32:04 +0200 In-Reply-To: Tim Vanderhoek's message of "Thu, 16 Apr 1998 17:08:33 -0400 (EDT)" Message-ID: Lines: 16 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tim Vanderhoek writes: > On Thu, 16 Apr 1998, Anatoly Vorobey wrote: > > Well, a few weeks ago I sent a send-pr with a diff attached > > that eliminated _all_ its/it's mistakes in the kernel source > > (there were about 70 of them). Nothing resulted; I still hope > > someone would deal with it. > That's because a patch that broad to the kernel source has more > potential (political) trouble attached, and is less urgent (than *Groan* See DES. See patch. See DES commit patch. See DES's mailbox explode. DES should have listened to Uncle Tim :) -- Nobody else has a .sig like this one. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 18 04:38:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA19332 for freebsd-current-outgoing; Sat, 18 Apr 1998 04:38:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19327 for ; Sat, 18 Apr 1998 11:38:30 GMT (envelope-from dag-erli@ifi.uio.no) Received: from bilskirnir.ifi.uio.no (2602@bilskirnir.ifi.uio.no [129.240.64.135]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id NAA18523; Sat, 18 Apr 1998 13:38:24 +0200 (MET DST) Received: (from dag-erli@localhost) by bilskirnir.ifi.uio.no ; Sat, 18 Apr 1998 13:38:23 +0200 (MET DST) Mime-Version: 1.0 To: Greg Lehey Cc: Karl Pielorz , current@FreeBSD.ORG Subject: Re: Quick Question re: Dmesg & Current Version References: <353802A2.CB67FCE7@tdx.co.uk> <19980418113504.U1090@freebie.lemis.com> Organization: Gutteklubben Terrasse / KRST / PUMS / YASMW X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-Stop-Spam: http://www.cauce.org From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 18 Apr 1998 13:38:22 +0200 In-Reply-To: Greg Lehey's message of "Sat, 18 Apr 1998 11:35:04 +0930" Message-ID: Lines: 18 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey writes: > On Sat, 18 April 1998 at 2:32:18 +0100, Karl Pielorz wrote: > > In the dmesg for my system I get: > > > > FreeBSD 3.0-CURRENT #5: Fri Apr 17 20:25:58 BST 1998 > > > > What does the '#5' refer to? > > It's the version number. Each time you build a kernel, the number is > incremented. Look at the file /sys/compile/YOURKERNEL/version. It is also reset to zero every time you run config, because /sys/compile/YOURKERNEL/version is deleted. I'm not sure if that's a bug or a feature... Maybe we could put (the|a) version number in /etc/YOURKERNEL.version so it is kept across config runs. -- Nobody else has a .sig like this one. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 18 05:10:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA24439 for freebsd-current-outgoing; Sat, 18 Apr 1998 05:10:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA24427 for ; Sat, 18 Apr 1998 12:10:03 GMT (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id MAA04617; Sat, 18 Apr 1998 12:09:55 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id OAA04822; Sat, 18 Apr 1998 14:09:54 +0200 (MET DST) Message-ID: <19980418140954.28168@follo.net> Date: Sat, 18 Apr 1998 14:09:54 +0200 From: Eivind Eklund To: Richard Wackerbarth , Greg Lehey Cc: Karl Pielorz , current@FreeBSD.ORG Subject: Re: Quick Question re: Dmesg & Current Version References: <353802A2.CB67FCE7@tdx.co.uk>; <353802A2.CB67FCE7@tdx.co.uk> <19980418113504.U1090@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Richard Wackerbarth on Sat, Apr 18, 1998 at 02:47:58AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Apr 18, 1998 at 02:47:58AM -0500, Richard Wackerbarth wrote: > At 9:05 PM -0500 4/17/98, Greg Lehey wrote: > >On Sat, 18 April 1998 at 2:32:18 +0100, Karl Pielorz wrote: > >> I'm just starting to get to grips with CVSup - is there anywhere it stores > >> the date & time that the source was last updated? - Rather than the last > >> build time? > > > >Somewhere, probably. When I used ctm, I modified /sys/conf/newvers.sh > >to include the ctm update number in the header, but I haven't found > >anything useful in the CVS database. Let me know if you do. > > Nope. AFAIK, there is nothing there. What is needed is something generated > at the MASTER source and propogated through all the distribution chains. > > I wrote such a change last year, but it was promptly rejected on what I > can only conclude were political grounds. (The supposed "technical grounds" > were bogus arguments.) Perhaps someone with some clout will reconsider :-( (Richard, please don't take this personally) I was in favour of reaching Richard's goal (and I think all of us where), but saw Nate's arguments as fully convincing. Loosing information if you loose a race is not acceptable for a production system as large as FreeBSD. I'd be glad if you looked into providing a solution for the problems with your change, and will try to get the change in if you do so. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 18 05:46:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA29861 for freebsd-current-outgoing; Sat, 18 Apr 1998 05:46:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from aldan.ziplink.net (mi@kot.ne.mediaone.net [24.128.29.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA29833 for ; Sat, 18 Apr 1998 12:46:08 GMT (envelope-from mi@rtfm.ziplink.net) Received: from rtfm.ziplink.net (rtfm [199.232.255.52]) by aldan.ziplink.net (8.8.8/8.8.7) with ESMTP id MAA00311 for ; Sat, 18 Apr 1998 12:46:04 GMT (envelope-from mi@rtfm.ziplink.net) Received: (from mi@localhost) by rtfm.ziplink.net (8.8.8/8.8.5) id IAA22497 for current@freebsd.org; Sat, 18 Apr 1998 08:46:00 -0400 (EDT) From: Mikhail Teterin Message-Id: <199804181246.IAA22497@rtfm.ziplink.net> Subject: Re: DPT EISA shim problems. In-Reply-To: from "Matthew N. Dodd" at "Apr 18, 98 00:02:57 am" To: current@FreeBSD.ORG Date: Sat, 18 Apr 1998 08:46:00 -0400 (EDT) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA00534 for freebsd-current-outgoing; Sat, 18 Apr 1998 06:28:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA00385 for ; Sat, 18 Apr 1998 13:28:22 GMT (envelope-from rkw@dataplex.net) Received: from [208.2.87.6] (user6.dataplex.net [208.2.87.6]) by shrimp.dataplex.net (8.8.8/8.8.5) with ESMTP id IAA18825; Sat, 18 Apr 1998 08:28:00 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <19980418140954.28168@follo.net> References: ; from Richard Wackerbarth on Sat, Apr 18, 1998 at 02:47:58AM -0500 <353802A2.CB67FCE7@tdx.co.uk>; <353802A2.CB67FCE7@tdx.co.uk> <19980418113504.U1090@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 18 Apr 1998 08:27:58 -0500 To: Eivind Eklund From: Richard Wackerbarth Subject: Re: Quick Question re: Dmesg & Current Version Cc: Greg Lehey , Karl Pielorz , current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 7:09 AM -0500 4/18/98, Eivind Eklund wrote: >On Sat, Apr 18, 1998 at 02:47:58AM -0500, Richard Wackerbarth wrote: >> At 9:05 PM -0500 4/17/98, Greg Lehey wrote: >> >On Sat, 18 April 1998 at 2:32:18 +0100, Karl Pielorz wrote: >> >> I'm just starting to get to grips with CVSup - is there anywhere it >>stores >> >> the date & time that the source was last updated? - Rather than the last >> >> build time? >> > >> >Somewhere, probably. When I used ctm, I modified /sys/conf/newvers.sh >> >to include the ctm update number in the header, but I haven't found >> >anything useful in the CVS database. Let me know if you do. >> >> Nope. AFAIK, there is nothing there. What is needed is something generated >> at the MASTER source and propogated through all the distribution chains. >> >> I wrote such a change last year, but it was promptly rejected on what I >> can only conclude were political grounds. (The supposed "technical grounds" >> were bogus arguments.) Perhaps someone with some clout will reconsider :-( > >(Richard, please don't take this personally) I was in favour of >reaching Richard's goal (and I think all of us where), but saw Nate's >arguments as fully convincing. Loosing information if you loose a >race is not acceptable for a production system as large as FreeBSD. > >I'd be glad if you looked into providing a solution for the problems >with your change, and will try to get the change in if you do so. AFAIK, Nate's objections were that I did not automate the recognition of new branches and that the mechanism that I was using to manually add a new branch was "overly dangerous" in that it could cause problems if someone made a mistake. As far as the "race" condition that you mention is concerned, that is solved by doing the steps in the proper order. While, early on, I conceeded that the process would be better if I simplified the insertion, I don't think that REQUIRING that is essential for a "first cut". I happen to disagree with Nate about the desirability of automatically recognizing new branches. IMHO, that configuration should be a manual step. I have been unable to get Nate to give me any explicit set of steps that breaks things in the manner that he claims. I do not consider it "broken" if someone creates a new branch and the file exists for a short time and then disappears. CVS will complain when that individual does his next update. However, the complaint is that the file no longer exists. This is a proper complaint. The problem should be fixed either by deleting the file or installing the branch in the list of branches that are being tracked. One reason that I am reluctant to automate the creation of new branches is that I am uncertain that our overall design is correct. We may need to have a different mechanism which tracks, in its output, stamps for multiple branches. For example, we may need to track "soft updates" separately from the main kernel by having more than one file appear when you select that sub-branch. Using the manufacture of automobiles as an analogy, I have hand-built a "concept car". I think that we should "road test" the design before we create the tooling for an assembly line. If someone is willing to address the present situation and get things out of the stalemate by either demonstrating, as opposed to simply alledging, a critical problem OR by getting the code accepted, I would certainly be willing to work with them. Richard Wackerbarth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 18 06:43:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA10570 for freebsd-current-outgoing; Sat, 18 Apr 1998 06:43:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shadow.worldbank.org (shadow.worldbank.org [138.220.104.78]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA10565 for ; Sat, 18 Apr 1998 13:43:27 GMT (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.8.8/8.8.8) with SMTP id JAA08109; Sat, 18 Apr 1998 09:41:45 -0400 (EDT) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Sat, 18 Apr 1998 09:41:45 -0400 (EDT) From: "Alok K. Dhir" To: perlsta@fang.cs.sunyit.edu cc: Alok_K._Dhir/Person/World_Bank@notes.worldbank.org, brandon@engulf.com, current@FreeBSD.ORG Subject: Re: Problems w/ Linux EMU 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 have yet to need to brandelf anything. I am quite aware of its existence and the purpose thereof... Incidentally, I haven't had any trouble with Linux emu... On Fri, 17 Apr 1998 perlsta@fang.cs.sunyit.edu wrote: > > > no, "man brandelf" > but the linux emu is quite borked in -current it seems. > > a LOT of stuff stopped working right about a month ago. > > -Alfred > > > You probably need to remake the LKMs and reboot... > > > > > I am running FreeBSD 3.0-Current last updated on Sunday. For some > strange > > > reason, my Linux EMU is having problems. (It doesn't recognize the ELF > > > binary type). Any clue why this is happening? > > -------------------------------------------------------------------- \||/_ Alok K. Dhir Phone: +1.202.473.2446 oo \ S13-061, ISGMC Email: adhir@worldbank.org L_ The World Bank Group Washington, DC \/ ------------------------------------------------------------------------| "Unix _is_ user friendly - it just chooses friends selectively..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 18 06:49:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA11816 for freebsd-current-outgoing; Sat, 18 Apr 1998 06:49:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bmccane.maxbaud.net ([208.155.166.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA11806 for ; Sat, 18 Apr 1998 13:49:30 GMT (envelope-from root@bmccane.maxbaud.net) Received: (from root@localhost) by bmccane.maxbaud.net (8.8.8/8.8.7) id IAA00634; Sat, 18 Apr 1998 08:49:01 -0500 (CDT) (envelope-from root) Date: Sat, 18 Apr 1998 08:48:59 -0500 (CDT) From: Wm Brian McCane To: current@FreeBSD.ORG Subject: cvsup messages Message-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 am getting the following errors on various files in -current when I cvsup them: Checksum mismatch -- will transfer entire file I tried wiping out the file. CVSUP pulled down the file, and on the next run (the following night) started giving the error again. any suggestions? brian +-----------------------------------+------------------------------------------+ He rides a cycle of mighty days, and \ Wm Brian and Lori McCane represents the last great schizm among\ McCane Consulting the gods. Evil though he obviously is, \ root@bmccane.cavtech.com he is a mighty figure, this father of \ http://bmccane.cavtech.com/ my spirit, and I respect him as the sons \ http://bmccane.cavtech.com/~pictures/ of old did the fathers of their bodies. \ http://bmccane.cavtech.com/~bmccane/ Roger Zelazny - "Lord of Light" \ +-------------------------------------------+----------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 18 07:53:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA20538 for freebsd-current-outgoing; Sat, 18 Apr 1998 07:53:02 -0700 (PDT) (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 OAA20529 for ; Sat, 18 Apr 1998 14:52:57 GMT (envelope-from pb@fasterix.frmug.org) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id QAA03168; Sat, 18 Apr 1998 16:52:29 +0200 (CEST) (envelope-from pb@fasterix.frmug.org) Received: (from pb@localhost) by fasterix.frmug.org (8.8.8/8.8.5/pb-19970302) id QAA08470; Sat, 18 Apr 1998 16:50:39 +0200 (CEST) Message-ID: <19980418165039.MO06387@@> Date: Sat, 18 Apr 1998 16:50:39 +0200 From: pb@fasterix.freenix.org (Pierre Beyssac) To: perlsta@fang.cs.sunyit.edu (Alfred Perlstein) Cc: mike@smith.net.au (Mike Smith), current@FreeBSD.ORG Subject: Re: Problems w/ Linux EMU References: <199804172257.PAA01087@dingo.cdrom.com> X-Mailer: Mutt 0.59.1e Mime-Version: 1.0 In-Reply-To: ; from Alfred Perlstein on Apr 17, 1998 19:07:54 +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein writes: > mostly that i get "leaking" shared memory, this has been a problem as of a > month ago or so. > > after staroffice 4 has been running for a few seconds it locks up and i do > a ipcs and see all my shared segments are used up. This is not a kernel leak. Shared memory shown by ipcs is freed by the application, not the kernel, because there is no other way to do. If the application fails to clean up (because it dumps core, for example), use "ipcrm" to clean up after. > also linux programs attempting to use raw sockets don't seem to work > anymore. all this "breakage" (for me) seems to have occured about a month > or so ago. Being more specific wouldn't hurt. I don't have any problems with a Linux traceroute and ping, with a Linux emulator compiled on April 1st. -- Pierre Beyssac pb@fasterix.frmug.org pb@fasterix.freenix.org {Free,Net,Open}BSD, Linux : il y a moins bien, mais c'est plus cher Free domains: http://www.eu.org/ or mail dns-manager@EU.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 18 10:15:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA21293 for freebsd-current-outgoing; Sat, 18 Apr 1998 10:15:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hawk.pearson.udel.edu. (hawk.pearson.udel.edu [128.175.64.150]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA21282; Sat, 18 Apr 1998 17:14:52 GMT (envelope-from alexandr@hawk.pearson.udel.edu) Received: from hawk.pearson.udel.edu by hawk.pearson.udel.edu. (SMI-8.6/SMI-SVR4) id NAA28122; Sat, 18 Apr 1998 13:18:30 -0400 Date: Sat, 18 Apr 1998 13:18:30 -0400 From: alexandr@hawk.pearson.udel.edu (Jerry Alexandratos) Message-Id: <199804181718.NAA28122@hawk.pearson.udel.edu.> To: current@FreeBSD.ORG Cc: webmaster@FreeBSD.ORG Subject: RE: Networking strategy for -current Organization: Broken Toys Unlimited Reply-To: alexandr@hawk.pearson.udel.edu Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In Reply to Your Message of Fri, 17 Apr 1998 19: 09:57 PDT MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <28115.892919909.1@hawk.pearson.udel.edu> Date: Sat, 18 Apr 1998 13:18:30 -0400 From: Jerry Alexandratos [stuff deleted] : how many times do I have to repeat.. : : I'M not talking about what's int the tree, but rather what is at: : http://www.freebsd.org/~julian Okay silly question (something I'm always full of). Where are all of these pages documented? I couldn't find any links off the web page to individual pages. Is there a place to look for stuff like this that isn't in the source tree but on someone's personal page? --Jerry 8) Jerry Alexandratos % - % "Nothing inhabits my (8 8) alexandr@louie.udel.edu % - % thoughts, and oblivion (8 8) alexandr@hawk.pearson.udel.edu % - % drives my desires." (8 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 18 10:35:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24854 for freebsd-current-outgoing; Sat, 18 Apr 1998 10:35:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (garbanzo@seoul-222.ppp.hooked.net [206.169.228.222]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA24847 for ; Sat, 18 Apr 1998 17:35:14 GMT (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.8/8.8.7) with ESMTP id KAA01158; Sat, 18 Apr 1998 10:35:00 -0700 (PDT) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Sat, 18 Apr 1998 10:35:00 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= cc: Greg Lehey , Karl Pielorz , current@FreeBSD.ORG Subject: Re: Quick Question re: Dmesg & Current Version In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18 Apr 1998, Dag-Erling Coidan [iso-8859-1] Smørgrav wrote: > Greg Lehey writes: > > On Sat, 18 April 1998 at 2:32:18 +0100, Karl Pielorz wrote: > > > In the dmesg for my system I get: > > > > > > FreeBSD 3.0-CURRENT #5: Fri Apr 17 20:25:58 BST 1998 > > > > > > What does the '#5' refer to? > > > > It's the version number. Each time you build a kernel, the number is > > incremented. Look at the file /sys/compile/YOURKERNEL/version. > > It is also reset to zero every time you run config, because > /sys/compile/YOURKERNEL/version is deleted. I'm not sure if that's a > bug or a feature... Maybe we could put (the|a) version number in > /etc/YOURKERNEL.version so it is kept across config runs. Well, it doesn't now on -current. On -stable man config. - alex "Contrary to popular belief, penguins are not the salvation of modern technology. Neither do they throw parties for the urban proletariat." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 18 10:37:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA25147 for freebsd-current-outgoing; Sat, 18 Apr 1998 10:37:35 -0700 (PDT) (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 RAA25133; Sat, 18 Apr 1998 17:37:23 GMT (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA13015; Sat, 18 Apr 1998 10:35:06 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd013013; Sat Apr 18 17:35:04 1998 Date: Sat, 18 Apr 1998 10:29:49 -0700 (PDT) From: Julian Elischer To: Jerry Alexandratos cc: current@FreeBSD.ORG, webmaster@FreeBSD.ORG Subject: RE: Networking strategy for -current In-Reply-To: <199804181718.NAA28122@hawk.pearson.udel.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 good question, Jordan, is there somewhere we can "advertise" our wares? julian On Sat, 18 Apr 1998, Jerry Alexandratos wrote: > In Reply to Your Message of Fri, 17 Apr 1998 19: 09:57 PDT > MIME-Version: 1.0 > Content-Type: text/plain; charset="us-ascii" > Content-ID: <28115.892919909.1@hawk.pearson.udel.edu> > Date: Sat, 18 Apr 1998 13:18:30 -0400 > From: Jerry Alexandratos > > [stuff deleted] > > : how many times do I have to repeat.. > : > : I'M not talking about what's int the tree, but rather what is at: > : http://www.freebsd.org/~julian > > Okay silly question (something I'm always full of). Where are all of > these pages documented? I couldn't find any links off the web page to > individual pages. Is there a place to look for stuff like this that > isn't in the source tree but on someone's personal page? > > --Jerry > > 8) Jerry Alexandratos % - % "Nothing inhabits my (8 > 8) alexandr@louie.udel.edu % - % thoughts, and oblivion (8 > 8) alexandr@hawk.pearson.udel.edu % - % drives my desires." (8 > > 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 Apr 18 11:03:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA28719 for freebsd-current-outgoing; Sat, 18 Apr 1998 11:03:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA28713; Sat, 18 Apr 1998 18:03:20 GMT (envelope-from jfieber@indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.8/8.8.7) with SMTP id NAA16650; Sat, 18 Apr 1998 13:03:10 -0500 (EST) Date: Sat, 18 Apr 1998 13:03:09 -0500 (EST) From: John Fieber To: Julian Elischer cc: Jerry Alexandratos , current@FreeBSD.ORG, webmaster@FreeBSD.ORG Subject: RE: Networking strategy for -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 18 Apr 1998, Julian Elischer wrote: > good question, Jordan, is there somewhere we can "advertise" our > wares? It needs to be promoted to a more visible position, but look up "FreeBSD Development projects" on the "Support" page. Feel free to add your own links there. -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 18 11:35:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07187 for freebsd-current-outgoing; Sat, 18 Apr 1998 11:35:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA07174 for ; Sat, 18 Apr 1998 18:35:30 GMT (envelope-from dag-erli@ifi.uio.no) Received: from skejdbrimir.ifi.uio.no (skejdbrimir.ifi.uio.no [129.240.65.2]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with SMTP id UAA11942; Sat, 18 Apr 1998 20:35:02 +0200 (MET DST) Received: from localhost (dag-erli@localhost) by skejdbrimir.ifi.uio.no ; Sat, 18 Apr 1998 18:34:58 GMT Mime-Version: 1.0 To: Alex Cc: "Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= =?iso-8859-1?Q?=2C?= Greg Lehey" , Karl Pielorz , current@FreeBSD.ORG Subject: Re: Quick Question re: Dmesg & Current Version References: Organization: Gutteklubben Terrasse / KRST / PUMS / YASMW X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-Stop-Spam: http://www.cauce.org From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 18 Apr 1998 20:34:44 +0200 In-Reply-To: Alex's message of "Sat, 18 Apr 1998 10:35:00 -0700 (PDT)" Message-ID: Lines: 16 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id SAA07176 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alex writes: > On 18 Apr 1998, Dag-Erling Coidan [iso-8859-1] Smørgrav wrote: > > Greg Lehey writes: > > > It's the version number. Each time you build a kernel, the number is > > > incremented. Look at the file /sys/compile/YOURKERNEL/version. > > It is also reset to zero every time you run config, because > Well, it doesn't now on -current. On -stable man config. Sorry, my brain's mode selector is still on "stable". *click* OK, I'm on "current" now :) -- Nobody else has a .sig like this one. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 18 12:23:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14846 for freebsd-current-outgoing; Sat, 18 Apr 1998 12:23:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA14839 for ; Sat, 18 Apr 1998 19:23:14 GMT (envelope-from dag-erli@ifi.uio.no) Received: from skejdbrimir.ifi.uio.no (skejdbrimir.ifi.uio.no [129.240.65.2]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with SMTP id VAA14347 for ; Sat, 18 Apr 1998 21:23:12 +0200 (MET DST) Received: from localhost (dag-erli@localhost) by skejdbrimir.ifi.uio.no ; Sat, 18 Apr 1998 19:23:12 GMT Mime-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: kern/6184 References: Organization: Gutteklubben Terrasse / KRST / PUMS / YASMW X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-Stop-Spam: http://www.cauce.org From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 18 Apr 1998 21:23:07 +0200 In-Reply-To: dag-erli@ifi.uio.no's message of "17 Apr 1998 23:12:34 +0200" Message-ID: Lines: 10 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id TAA14842 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG dag-erli@ifi.uio.no (Dag-Erling Coidan Smørgrav ) writes: > I have a patch which I hope fixes kern/6184 (lseek allows seeks to > negative offsets), but I don't want to commit it without having > someone look at it first: > [patch deleted] There was apparently no response, so I'm committing to -current. -- Nobody else has a .sig like this one. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 18 13:32:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23675 for freebsd-current-outgoing; Sat, 18 Apr 1998 13:32:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA23667 for ; Sat, 18 Apr 1998 20:32:45 GMT (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id WAA11738 for ; Sat, 18 Apr 1998 22:35:47 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Sat, 18 Apr 1998 22:35:46 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: freebsd-current@FreeBSD.ORG Subject: There was PicoBSD - let there be a Mini... Message-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 seem to have some crazy ideas from time to time... Here's one of them. I propose to add another type of installation combined with a special distribution set. The idea behind it is to let people who are completely new to FreeBSD just try the system without really installing it (which bears all the hassle of repartitioning etc.), and to have positive enough impression to install i then in normal way. I admit that this idea occured to me when I tried the JavaPC preview. :-) Here's what the setup would be like: * the whole installation (available in sysinstall :-) would place FreeBSD on an existing DOS partition. Installation program would create the file with filesystem on it (which will then be mounted on a vn(4) device). This will require (well, it depends) ca. 16-24MB of free space on a DOS partition. * then the special distribution set would be transferred to the vn-mounted file. This distribution would contain (among others): basic system utilities, pretty minimal XWindow with SVGA server and a nice window manager (qvwm?) with file manager (FreeBSD Explorer?); and of course Netscape/Mozilla browser with Java. * the most important requirement of this set would be that each element work as expected with almost no setup on user's part (except network/dialup setup, which can be done with user-friendly script). * the whole thing would be started from DOS (using fbsdboot.exe). This will probably require special C:\kernel with small MFS, containing init(8), mount, vnconfig etc.. which after booting would first mount the DOS partition, and then vnconfig the previously created file with OS on it, and mount it on /. Well, that's basically the whole idea. How do you like it? I'm willing to try it anyway, and even to write some of the glue code needed to incorporate it into sysinstall. Andrzej Bialecki --------------------+--------------------------------------------------------- abial@nask.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. --------------------+--------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 18 13:47:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26815 for freebsd-current-outgoing; Sat, 18 Apr 1998 13:47:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA26806 for ; Sat, 18 Apr 1998 20:47:41 GMT (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.8.8/8.8.8) with ESMTP id NAA10070; Sat, 18 Apr 1998 13:47:28 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199804182047.NAA10070@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrzej Bialecki cc: freebsd-current@FreeBSD.ORG Subject: Re: There was PicoBSD - let there be a Mini... In-reply-to: Your message of "Sat, 18 Apr 1998 22:35:46 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 18 Apr 1998 13:47:28 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Great Idea!! Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 18 14:17:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA01464 for freebsd-current-outgoing; Sat, 18 Apr 1998 14:17:12 -0700 (PDT) (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 VAA01459 for ; Sat, 18 Apr 1998 21:17:09 GMT (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id VAA10925; Sat, 18 Apr 1998 21:36:56 +0200 From: Luigi Rizzo Message-Id: <199804181936.VAA10925@labinfo.iet.unipi.it> Subject: Re: There was PicoBSD - let there be a Mini... To: abial@nask.pl (Andrzej Bialecki) Date: Sat, 18 Apr 1998 21:36:55 +0200 (MET DST) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: from "Andrzej Bialecki" at Apr 18, 98 10:35:27 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi! > > I seem to have some crazy ideas from time to time... Here's one of them. > > I propose to add another type of installation combined with a special > distribution set. The idea behind it is to let people who are completely > new to FreeBSD just try the system without really installing it (which i was thinking about the same thing, since recently tried something similar with diskless, and MFS filesystem backed on a DOS partition is reasonably fast now, and long name support (I used Luqi Chen patches with 2.2.5 and 2.2.6) is also working. > Here's what the setup would be like: > > * the whole installation (available in sysinstall :-) would place FreeBSD > on an existing DOS partition. Installation program would create the file > with filesystem on it (which will then be mounted on a vn(4) device). This > will require (well, it depends) ca. 16-24MB of free space on a DOS > partition. you'd need this much space just for the swapfile. I was thinking of a slightly different approach, where you mount all the binaries from a CD (with the 16X CDs available nowadays, speed is not as terrible as it was with 2X drives), and the DOS file is very small, containing only (a portion of) the root partition with kernel, /sbi, /etc, /var... . Home directories can go into the DOS partition, so they can be shared with DOS. cheers luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 18 14:25:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA02264 for freebsd-current-outgoing; Sat, 18 Apr 1998 14:25:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA02258 for ; Sat, 18 Apr 1998 21:25:37 GMT (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id XAA24958; Sat, 18 Apr 1998 23:27:54 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Sat, 18 Apr 1998 23:27:54 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Luigi Rizzo cc: freebsd-current@FreeBSD.ORG Subject: Re: There was PicoBSD - let there be a Mini... In-Reply-To: <199804181936.VAA10925@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 Sat, 18 Apr 1998, Luigi Rizzo wrote: > > * the whole installation (available in sysinstall :-) would place FreeBSD > > on an existing DOS partition. Installation program would create the file > > with filesystem on it (which will then be mounted on a vn(4) device). This > > will require (well, it depends) ca. 16-24MB of free space on a DOS > > partition. > > you'd need this much space just for the swapfile. As I said: it depends. E.g. PicoBSD doesn't use swap at all... So perhaps, in case of X's, 8MB would be for swap and 16MB for the binaries. > > I was thinking of a slightly different approach, where you mount all > the binaries from a CD (with the 16X CDs available nowadays, speed is > not as terrible as it was with 2X drives), and the DOS file is very > small, containing only (a portion of) the root partition with kernel, > /sbi, /etc, /var... . Home directories can go into the DOS partition, > so they can be shared with DOS. Yes, this way you could have even quite normal FreeBSD installation... but you need to keep the right CD in drive all the time. Andrzej Bialecki --------------------+--------------------------------------------------------- abial@nask.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. --------------------+--------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 18 14:44:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA05792 for freebsd-current-outgoing; Sat, 18 Apr 1998 14:44:27 -0700 (PDT) (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 VAA05767 for ; Sat, 18 Apr 1998 21:44:19 GMT (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id XAA21061 for current@FreeBSD.ORG; Sat, 18 Apr 1998 23:44:00 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.9.0.Beta4/keltia-2.14/nospam) id LAA07268; Sat, 18 Apr 1998 11:15:27 +0200 (CEST) (envelope-from roberto) Message-ID: <19980418111526.A7246@keltia.freenix.fr> Date: Sat, 18 Apr 1998 11:15:26 +0200 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Star Office 4 (Was: Re: Problems w/ Linux EMU) Mail-Followup-To: current@FreeBSD.ORG References: <199804172257.PAA01087@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91i In-Reply-To: ; from Alfred Perlstein on Fri, Apr 17, 1998 at 07:07:54PM +0000 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4213 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Alfred Perlstein: > after staroffice 4 has been running for a few seconds it locks up and i do > a ipcs and see all my shared segments are used up. I have a script that start StarOffice4 and then clean up the shared memory segments afterward (it is either a bug in SO4 or a bug in our shared mem emulation). I've been seeing SO4 lockups regularely too. Sometimes, you start doing something then everything is blocked because it has gone in a tight loop, taking huge amount of CPU. Only kill is effective. I don't know if it is a bug in SO4 or in the emulator. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #3: Tue Apr 14 21:41:01 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 18 14:45:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA06103 for freebsd-current-outgoing; Sat, 18 Apr 1998 14:45:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mhub3.tc.umn.edu (0@mhub3.tc.umn.edu [128.101.131.53]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA06092 for ; Sat, 18 Apr 1998 21:45:25 GMT (envelope-from adkin003@tc.umn.edu) Received: from gold.tc.umn.edu by mhub3.tc.umn.edu; Sat, 18 Apr 98 16:45:23 -0500 Received: from pub-29-b-210.dialup.umn.edu by gold.tc.umn.edu; Sat, 18 Apr 98 16:45:22 -0500 Date: Sat, 18 Apr 1998 16:45:17 -0500 (CDT) From: dave adkins X-Sender: adkin003@samthedog Reply-To: dave adkins To: freebsd-current@FreeBSD.ORG Subject: systat and \n in intr names Message-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 recently noticed that systat displays '\n' at the begining of the interrupt name entries. It doesn't look a vmstat.c problem. I wrote a small test prog to dump the entries in a current (041898) kernel's _intrnames[] and found the following. \nclk0 irq2 5c 6e 63 6c 6b 30 20 69 72 71 32 20 \nrtc0 irq8 5c 6e 72 74 63 30 20 69 72 71 38 20 \npci irqnn 5c 6e 70 63 69 20 69 72 71 6e 6e \npci irqnn 5c 6e 70 63 69 20 69 72 71 6e 6e \npci irqnn 5c 6e 70 63 69 20 69 72 71 6e 6e \npci irqnn 5c 6e 70 63 69 20 69 72 71 6e 6e \nipi irqnn 5c 6e 69 70 69 20 69 72 71 6e 6e \nipi irqnn 5c 6e 69 70 69 20 69 72 71 6e 6e \nipi irqnn 5c 6e 69 70 69 20 69 72 71 6e 6e \nipi irqnn 5c 6e 69 70 69 20 69 72 71 6e 6e \nfdc0 irq6 5c 6e 66 64 63 30 20 69 72 71 36 20 \nwdc0 irq14 5c 6e 77 64 63 30 20 69 72 71 31 34 \nwdc1 irq15 5c 6e 77 64 63 31 20 69 72 71 31 35 \nppc0 irq7 5c 6e 70 70 63 30 20 69 72 71 37 20 \nsc0 irq1 5c 6e 73 63 30 20 69 72 71 31 20 \nsio0 irq4 5c 6e 73 69 6f 30 20 69 72 71 34 20 \nsio1 irq3 5c 6e 73 69 6f 31 20 69 72 71 33 20 \nlpt0 irqnn 5c 6e 6c 70 74 30 20 69 72 71 6e 6e \nnpx0 irqnn 5c 6e 6e 70 78 30 20 69 72 71 6e 6e \nstray irq0 5c 6e 73 74 72 61 79 20 69 72 71 30 stray irq1 73 74 72 61 79 20 69 72 71 31 These are some of the entries between _intrnames and _eintrnames. Most include the chars '\', 'n' before each entry. This is something that has crept in in the last month or so, I don't remember exactly when. Is there a reason for the leading '\','n' chars for each name, and should systat -vm display them? dave adkins To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 18 14:45:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA06332 for freebsd-current-outgoing; Sat, 18 Apr 1998 14:45:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA06326 for ; Sat, 18 Apr 1998 21:45:50 GMT (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.8.8/8.8.8) with ESMTP id OAA10693; Sat, 18 Apr 1998 14:45:29 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199804182145.OAA10693@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrzej Bialecki cc: Luigi Rizzo , freebsd-current@FreeBSD.ORG Subject: Re: There was PicoBSD - let there be a Mini... In-reply-to: Your message of "Sat, 18 Apr 1998 23:27:54 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 18 Apr 1998 14:45:29 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yes, this way you could have even quite normal FreeBSD installation... but > you need to keep the right CD in drive all the time. > A nice reminder for people to install FreeBSD on its rightful disk partition 8) Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 18 14:49:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA07348 for freebsd-current-outgoing; Sat, 18 Apr 1998 14:49:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dt050n33.san.rr.com (@dt050n33.san.rr.com [204.210.31.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA07323 for ; Sat, 18 Apr 1998 21:49:10 GMT (envelope-from Studded@san.rr.com) Received: from san.rr.com (Studded@localhost [127.0.0.1]) by dt050n33.san.rr.com (8.8.8/8.8.8) with ESMTP id OAA11186; Sat, 18 Apr 1998 14:48:23 -0700 (PDT) (envelope-from Studded@san.rr.com) Message-ID: <35391FA6.79CA8363@san.rr.com> Date: Sat, 18 Apr 1998 14:48:22 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.6-STABLE-0418 i386) MIME-Version: 1.0 To: Greg Lehey CC: Karl Pielorz , current@FreeBSD.ORG Subject: Re: Quick Question re: Dmesg & Current Version References: <353802A2.CB67FCE7@tdx.co.uk> <19980418113504.U1090@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: > Somewhere, probably. When I used ctm, I modified /sys/conf/newvers.sh > to include the ctm update number in the header, but I haven't found > anything useful in the CVS database. Let me know if you do. I have a little script that I run before a make world, one of the things it does is insert the date in newvers.sh. # Add today's date so I know when this was built sed s/SNAPDATE=\"\"/SNAPDATE=\"`date +%m%d`\"/ /usr/src/sys/conf/newvers.sh \ > /usr/src/sys/conf/newvers.sh.sed cp /usr/src/sys/conf/newvers.sh.sed /usr/src/sys/conf/newvers.sh && rm /usr/src/sys/conf/newvers.sh.sed echo '' grep 'SNAPDATE=' /usr/src/sys/conf/newvers.sh If you'd like to see the rest of the script, fetch http://home.san.rr.com/freebsd/mwprep Hope this is useful, Doug -- *** Chief Operations Officer, DALnet IRC network *** *** Proud designer and maintainer of the world's largest Internet *** Relay Chat server with 5,328 simultaneous connections. *** Try spider.dal.net on ports 6662-4 (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 Sat Apr 18 14:50:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA07834 for freebsd-current-outgoing; Sat, 18 Apr 1998 14:50:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA07824 for ; Sat, 18 Apr 1998 21:50:39 GMT (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.8.8/8.8.8) with ESMTP id OAA10755; Sat, 18 Apr 1998 14:50:03 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199804182150.OAA10755@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Ollivier Robert cc: current@FreeBSD.ORG Subject: Re: Star Office 4 (Was: Re: Problems w/ Linux EMU) In-reply-to: Your message of "Sat, 18 Apr 1998 11:15:26 +0200." <19980418111526.A7246@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 18 Apr 1998 14:50:03 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sometimes for debugging purposes, I just install linux on a disk. It is just that sometimes I don't get good cooperation from the linux side or is hard to get accurate information from "them" . Or , just post to a list in the hope that someone has a linux partition and request comments. Cheers, Amancio > According to Alfred Perlstein: > > after staroffice 4 has been running for a few seconds it locks up and i do > > a ipcs and see all my shared segments are used up. > > I have a script that start StarOffice4 and then clean up the shared memory > segments afterward (it is either a bug in SO4 or a bug in our shared mem > emulation). > > I've been seeing SO4 lockups regularely too. Sometimes, you start doing > something then everything is blocked because it has gone in a tight loop, > taking huge amount of CPU. Only kill is effective. > > I don't know if it is a bug in SO4 or in the emulator. > > -- > Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr > FreeBSD keltia.freenix.fr 3.0-CURRENT #3: Tue Apr 14 21:41:01 CEST 1998 > > 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 Apr 18 14:54:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA08745 for freebsd-current-outgoing; Sat, 18 Apr 1998 14:54:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA08694 for ; Sat, 18 Apr 1998 21:53:57 GMT (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id QAA25065; Sat, 18 Apr 1998 16:53:36 -0500 (EST) (envelope-from toor) Message-Id: <199804182153.QAA25065@dyson.iquest.net> Subject: Re: There was PicoBSD - let there be a Mini... In-Reply-To: from Andrzej Bialecki at "Apr 18, 98 11:27:54 pm" To: abial@nask.pl (Andrzej Bialecki) Date: Sat, 18 Apr 1998 16:53:36 -0500 (EST) Cc: luigi@labinfo.iet.unipi.it, freebsd-current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@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 Andrzej Bialecki said: > On Sat, 18 Apr 1998, Luigi Rizzo wrote: > > > > * the whole installation (available in sysinstall :-) would place FreeBSD > > > on an existing DOS partition. Installation program would create the file > > > with filesystem on it (which will then be mounted on a vn(4) device). This > > > will require (well, it depends) ca. 16-24MB of free space on a DOS > > > partition. > > > > you'd need this much space just for the swapfile. > > As I said: it depends. E.g. PicoBSD doesn't use swap at all... So perhaps, > in case of X's, 8MB would be for swap and 16MB for the binaries. > As you probably know, FreeBSD-current has two interesting sysctl variables for swap control, for exactly the case of embedded applications: sysctl vm.defer_swapspace_pageouts Makes it improbable to use swap space, unless the system really needs it. sysctl vm.disable_swapspace_pageouts Makes the system avoid using swap totally. In the above cases, the paging algorithms are changed to be friendly for the application. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 18 14:56:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09605 for freebsd-current-outgoing; Sat, 18 Apr 1998 14:56:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alexis.videotron.ca (ppp035.101.mmtl.videotron.net [207.253.101.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA09597 for ; Sat, 18 Apr 1998 21:56:44 GMT (envelope-from sepotvin@videotron.ca) Received: from videotron.ca (localhost.videotron.ca [127.0.0.1]) by alexis.videotron.ca (8.8.8/8.8.8) with ESMTP id RAA15628 for ; Sat, 18 Apr 1998 17:52:09 -0400 (EDT) (envelope-from sepotvin@videotron.ca) Message-ID: <35392082.ACA5F7C9@videotron.ca> Date: Sat, 18 Apr 1998 17:52:04 -0400 From: "Stephane E. Potvin" Organization: IBM Canada Ltd. X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: FreeBSD-current@FreeBSD.ORG Subject: zp driver not probing the MAC address properly Content-Type: multipart/mixed; boundary="------------BE801210807BD09BBB661745" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------BE801210807BD09BBB661745 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Can someone please check and commit the following little patch. It stopped my laptop from dying miserably when enabling the driver. Thx /SEP --------------BE801210807BD09BBB661745 Content-Type: text/plain; charset=us-ascii; name="if_zp.c.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="if_zp.c.diff" *** if_zp.c Sat Apr 18 17:37:29 1998 --- if_zp.c.orig Sat Mar 28 08:24:28 1998 *************** *** 542,548 **** short tmp_addr[3]; int j; for (j = 0; j < 3; j++) { ! tmp_addr[j] = htons(read_eeprom_data(BASE, j)); } bcopy(tmp_addr, sc->arpcom.ac_enaddr, 6); } --- 542,548 ---- short tmp_addr[3]; int j; for (j = 0; j < 3; j++) { ! tmp_addr[i] = htons(read_eeprom_data(BASE, j)); } bcopy(tmp_addr, sc->arpcom.ac_enaddr, 6); } --------------BE801210807BD09BBB661745-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 18 15:37:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16836 for freebsd-current-outgoing; Sat, 18 Apr 1998 15:37:31 -0700 (PDT) (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 WAA16826 for ; Sat, 18 Apr 1998 22:37:28 GMT (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id PAA17781; Sat, 18 Apr 1998 15:36:43 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd017777; Sat Apr 18 22:36:40 1998 Date: Sat, 18 Apr 1998 15:31:23 -0700 (PDT) From: Julian Elischer To: Andrzej Bialecki cc: freebsd-current@FreeBSD.ORG Subject: Re: There was PicoBSD - let there be a Mini... 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's funny, but that's EXACTLY what I was think about yesterday.. basically you are right on target.. The current PicoBSD could be booted off a DOS partition as it is, except for it's expectation to find a copy of /etc on a floppy. julian On Sat, 18 Apr 1998, Andrzej Bialecki wrote: > Hi! > > I seem to have some crazy ideas from time to time... Here's one of them. > > I propose to add another type of installation combined with a special > distribution set. The idea behind it is to let people who are completely > new to FreeBSD just try the system without really installing it (which > bears all the hassle of repartitioning etc.), and to have positive enough > impression to install i then in normal way. I admit that this idea occured > to me when I tried the JavaPC preview. :-) > > Here's what the setup would be like: > > * the whole installation (available in sysinstall :-) would place FreeBSD > on an existing DOS partition. Installation program would create the file > with filesystem on it (which will then be mounted on a vn(4) device). This > will require (well, it depends) ca. 16-24MB of free space on a DOS > partition. > > * then the special distribution set would be transferred to the vn-mounted > file. This distribution would contain (among others): basic system > utilities, pretty minimal XWindow with SVGA server and a nice window > manager (qvwm?) with file manager (FreeBSD Explorer?); and of course > Netscape/Mozilla browser with Java. > > * the most important requirement of this set would be that each element > work as expected with almost no setup on user's part (except > network/dialup setup, which can be done with user-friendly script). > > * the whole thing would be started from DOS (using fbsdboot.exe). This > will probably require special C:\kernel with small MFS, containing > init(8), mount, vnconfig etc.. which after booting would first mount the > DOS partition, and then vnconfig the previously created file with OS on > it, and mount it on /. > > Well, that's basically the whole idea. How do you like it? > > I'm willing to try it anyway, and even to write some of the glue code > needed to incorporate it into sysinstall. > > Andrzej Bialecki > > --------------------+--------------------------------------------------------- > abial@nask.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } > Research & Academic | "Be open-minded, but don't let your brains to fall out." > Network in Poland | All of the above (and more) is just my personal opinion. > --------------------+--------------------------------------------------------- > > > 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 Apr 18 15:47:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA18260 for freebsd-current-outgoing; Sat, 18 Apr 1998 15:47:19 -0700 (PDT) (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 WAA18252; Sat, 18 Apr 1998 22:47:12 GMT (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id PAA17849; Sat, 18 Apr 1998 15:39:53 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd017847; Sat Apr 18 22:39:43 1998 Date: Sat, 18 Apr 1998 15:34:28 -0700 (PDT) From: Julian Elischer To: John Fieber cc: Jerry Alexandratos , current@FreeBSD.ORG, webmaster@FreeBSD.ORG Subject: RE: Networking strategy for -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can you give a hint how people can get-to /modify this? (especially thise without freefall logins (though I have one)) julian On Sat, 18 Apr 1998, John Fieber wrote: > On Sat, 18 Apr 1998, Julian Elischer wrote: > > > good question, Jordan, is there somewhere we can "advertise" our > > wares? > > It needs to be promoted to a more visible position, but look up > "FreeBSD Development projects" on the "Support" page. > > Feel free to add your own links there. > > -john > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 18 15:59:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19907 for freebsd-current-outgoing; Sat, 18 Apr 1998 15:59:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA19902 for ; Sat, 18 Apr 1998 22:59:53 GMT (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id PAA24390; Sat, 18 Apr 1998 15:59:41 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Andrzej Bialecki cc: freebsd-current@FreeBSD.ORG Subject: Re: There was PicoBSD - let there be a Mini... In-reply-to: Your message of "Sat, 18 Apr 1998 22:35:46 +0200." Date: Sat, 18 Apr 1998 15:59:40 -0700 Message-ID: <24386.892940380@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I seem to have some crazy ideas from time to time... Here's one of them. Heh. Not so crazy. This was first proposed about 3 years ago for the same general purpose - how to create quick and easy FreeBSD demo systems (you could even have the complete "preinstalled image" available as a much larger file if the user just wanted to grab a "typical" FreeBSD system and try it). I think it was jealously concerning Linux's "UMSDOS" filesystem and its frequent use for exactly this purpose that first led people to think of it. :) It should theoretically be possible, nobody's simply bothered to work out the details. It would, for another thing, be very slow (as Linux's UMSDOS is) and I think that's sort of dampened people's enthusiasm for the idea in the past, but if you're keen to try it I still think there'd be legitimate interest in 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 Apr 18 16:05:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA21451 for freebsd-current-outgoing; Sat, 18 Apr 1998 16:05:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA21411; Sat, 18 Apr 1998 23:05:36 GMT (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id QAA24463; Sat, 18 Apr 1998 16:05:23 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Julian Elischer cc: John Fieber , Jerry Alexandratos , current@FreeBSD.ORG, webmaster@FreeBSD.ORG Subject: Re: Networking strategy for -current In-reply-to: Your message of "Sat, 18 Apr 1998 15:34:28 PDT." Date: Sat, 18 Apr 1998 16:05:22 -0700 Message-ID: <24460.892940722@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Can you give a hint how people can get-to /modify this? > (especially thise without freefall logins (though I have one)) You need to be a committer to change this and all committers have freefall logins anyway. :) Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 18 16:09:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA22292 for freebsd-current-outgoing; Sat, 18 Apr 1998 16:09:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA22268 for ; Sat, 18 Apr 1998 23:09:10 GMT (envelope-from jfieber@indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.8/8.8.7) with SMTP id SAA17214; Sat, 18 Apr 1998 18:09:05 -0500 (EST) Date: Sat, 18 Apr 1998 18:09:05 -0500 (EST) From: John Fieber To: Julian Elischer cc: Jerry Alexandratos , current@FreeBSD.ORG Subject: RE: Networking strategy for -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 18 Apr 1998, Julian Elischer wrote: > Can you give a hint how people can get-to /modify this? > (especially thise without freefall logins (though I have one)) www.freebsd.org/cgi/cvsweb.cgi/www/data/support.sgml, edit, send diffs to www@freebsd.org. Alternatively, get that part of the cvs repository via cvsup, edit and send diffs to ww@freebsd.org. -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 18 17:00:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01734 for freebsd-current-outgoing; Sat, 18 Apr 1998 17:00:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from aldan.ziplink.net (mi@kot.ne.mediaone.net [24.128.29.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA01724 for ; Sun, 19 Apr 1998 00:00:03 GMT (envelope-from mi@rtfm.ziplink.net) Received: from rtfm.ziplink.net (rtfm [199.232.255.52]) by aldan.ziplink.net (8.8.8/8.8.7) with ESMTP id XAA01741 for ; Sat, 18 Apr 1998 23:59:59 GMT (envelope-from mi@rtfm.ziplink.net) Received: (from mi@localhost) by rtfm.ziplink.net (8.8.8/8.8.5) id TAA18624 for current@freebsd.org; Sat, 18 Apr 1998 19:59:57 -0400 (EDT) From: Mikhail Teterin Message-Id: <199804182359.TAA18624@rtfm.ziplink.net> Subject: Re: Star Office 4 (Was: Re: Problems w/ Linux EMU) In-Reply-To: <19980418111526.A7246@keltia.freenix.fr> from "Ollivier Robert" at "Apr 18, 98 11:15:26 am" To: current@FreeBSD.ORG Date: Sat, 18 Apr 1998 19:59:57 -0400 (EDT) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" after staroffice 4 has been running for a few seconds it locks up and i do => a ipcs and see all my shared segments are used up. = =I have a script that start StarOffice4 and then clean up the shared memory =segments afterward (it is either a bug in SO4 or a bug in our shared mem =emulation). Same here. =I've been seeing SO4 lockups regularely too. Sometimes, you start doing =something then everything is blocked because it has gone in a tight loop, =taking huge amount of CPU. Only kill is effective. Did not happen to me yet. I'm not a heavy user though... -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 18 17:16:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA05910 for freebsd-current-outgoing; Sat, 18 Apr 1998 17:16:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from aldan.ziplink.net (mi@kot.ne.mediaone.net [24.128.29.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA05901 for ; Sun, 19 Apr 1998 00:16:40 GMT (envelope-from mi@rtfm.ziplink.net) Received: from rtfm.ziplink.net (rtfm [199.232.255.52]) by aldan.ziplink.net (8.8.8/8.8.7) with ESMTP id AAA01778 for ; Sun, 19 Apr 1998 00:16:38 GMT (envelope-from mi@rtfm.ziplink.net) Received: (from mi@localhost) by rtfm.ziplink.net (8.8.8/8.8.5) id UAA18692 for current@freebsd.org; Sat, 18 Apr 1998 20:16:37 -0400 (EDT) From: Mikhail Teterin Message-Id: <199804190016.UAA18692@rtfm.ziplink.net> Subject: Re: There was PicoBSD - let there be a Mini... In-Reply-To: from "Andrzej Bialecki" at "Apr 18, 98 10:35:46 pm" To: current@FreeBSD.ORG Date: Sat, 18 Apr 1998 20:16:37 -0400 (EDT) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" dosfs instead of kernel -> ufs -> vn -> dosfs and eaither to explore from other the FreeBSD. Another note -- do not forget the Windoze swap file(s). pagefile.sys for NT/95 and (what's its name) on 3.1 . I use the as additional swap now on my dual boot machine -- works fine. =* the most important requirement of this set would be that each element =work as expected with almost no setup on user's part (except =network/dialup setup, which can be done with user-friendly script). Yep, this must be true for the real FreeBSD users too! =* the whole thing would be started from DOS (using fbsdboot.exe). This =will probably require special C:\kernel with small MFS, containing =init(8), mount, vnconfig etc.. which after booting would first mount the =DOS partition, and then vnconfig the previously created file with OS on =it, and mount it on /. -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 18 17:17:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06145 for freebsd-current-outgoing; Sat, 18 Apr 1998 17:17:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles324.castles.com [208.214.167.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA06101 for ; Sun, 19 Apr 1998 00:17:00 GMT (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id RAA06029; Sat, 18 Apr 1998 17:13:32 -0700 (PDT) Message-Id: <199804190013.RAA06029@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Amancio Hasty cc: Ollivier Robert , current@FreeBSD.ORG Subject: Re: Star Office 4 (Was: Re: Problems w/ Linux EMU) In-reply-to: Your message of "Sat, 18 Apr 1998 14:50:03 PDT." <199804182150.OAA10755@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 18 Apr 1998 17:13:31 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Sometimes for debugging purposes, I just install linux on a disk. > It is just that sometimes I don't get good cooperation from > the linux side or is hard to get accurate information from "them" . > > Or , just post to a list in the hope that someone has a linux > partition and request comments. I attempted to install RedHat 5.0 yesterday for just this purpose. However, if the Adaptec 2940U I was using was in the system, it would explode as soon as it tried to talk to it. Then I switched to an NCR875-based controller, and the driver enlessly timed out. And it didn't support the Qlogic card I have either. So, time to look for another controller. Maybe Monday. -- \\ 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 Apr 18 17:29:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08389 for freebsd-current-outgoing; Sat, 18 Apr 1998 17:29:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles324.castles.com [208.214.167.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA08372 for ; Sun, 19 Apr 1998 00:29:44 GMT (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id RAA06092; Sat, 18 Apr 1998 17:27:00 -0700 (PDT) Message-Id: <199804190027.RAA06092@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Andrzej Bialecki cc: freebsd-current@FreeBSD.ORG Subject: Re: There was PicoBSD - let there be a Mini... In-reply-to: Your message of "Sat, 18 Apr 1998 22:35:46 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 18 Apr 1998 17:26:59 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Here's what the setup would be like: > > * the whole installation (available in sysinstall :-) would place FreeBSD > on an existing DOS partition. Installation program would create the file > with filesystem on it (which will then be mounted on a vn(4) device). This > will require (well, it depends) ca. 16-24MB of free space on a DOS > partition. Sounds reasonable. Why limit yourself though? Given the disk sizes common today, why not allow the user to select the size they want? > * then the special distribution set would be transferred to the vn-mounted > file. This distribution would contain (among others): basic system > utilities, pretty minimal XWindow with SVGA server and a nice window > manager (qvwm?) with file manager (FreeBSD Explorer?); and of course > Netscape/Mozilla browser with Java. If you're going to offer a canned distribution set, it would be much simpler to just install it once locally, then zip up the bootstrap, kernel and image file (perhaps with a custom once-off /etc/rc that asks the config questions) and offer *that* for download. ... > Well, that's basically the whole idea. How do you like it? Do it! Very neat. -- \\ 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 Apr 18 17:30:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08765 for freebsd-current-outgoing; Sat, 18 Apr 1998 17:30:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA08723 for ; Sun, 19 Apr 1998 00:30:32 GMT (envelope-from rkw@dataplex.net) Received: from [208.2.87.6] (user6.dataplex.net [208.2.87.6]) by shrimp.dataplex.net (8.8.8/8.8.5) with ESMTP id TAA28563; Sat, 18 Apr 1998 19:30:12 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <35391FA6.79CA8363@san.rr.com> References: <353802A2.CB67FCE7@tdx.co.uk> <19980418113504.U1090@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 18 Apr 1998 19:30:08 -0500 To: Studded From: Richard Wackerbarth Subject: Re: Quick Question re: Dmesg & Current Version Cc: Greg Lehey , Karl Pielorz , current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 4:48 PM -0500 4/18/98, Studded wrote: >Greg Lehey wrote: > >> Somewhere, probably. When I used ctm, I modified /sys/conf/newvers.sh >> to include the ctm update number in the header, but I haven't found >> anything useful in the CVS database. Let me know if you do. > > I have a little script that I run before a make world, one of the >things it does is insert the date in newvers.sh. > ># Add today's date so I know when this was built >sed s/SNAPDATE=\"\"/SNAPDATE=\"`date +%m%d`\"/ >/usr/src/sys/conf/newvers.sh \ > > /usr/src/sys/conf/newvers.sh.sed >cp /usr/src/sys/conf/newvers.sh.sed /usr/src/sys/conf/newvers.sh && > rm /usr/src/sys/conf/newvers.sh.sed > >echo '' >grep 'SNAPDATE=' /usr/src/sys/conf/newvers.sh > > If you'd like to see the rest of the script, >fetch http://home.san.rr.com/freebsd/mwprep > >Hope this is useful, I go a little further. By storing the date in a file at the time that you update (via cvsup), the date reflects when you got the sources rather than when you did the build. The version string (which is IMHO much too verbose) already has the time of the build built into it. Here are my changes. The first change in newvers.sh is the operative one. The rest are because I am happier with the more terse format. If this is incorporated in the main tree, there will need to be a slight "fix" to take care of the real "SNAP" and "RELEASE" versions. The operative part of the output in vers.c is shown below. Note that the date in the osrelease string is earlier than the build date in the version string. For the CTM users, we could get similar info from the .ctm_status file. char ostype[] = "FreeBSD"; char osrelease[] = "3.0-19980416"; int osreldate = 300001; char sccs[4] = { '@', '(', '#', ')' }; char version[] = "DATAPLEX #4: 04/18/98\n"; shrimp: {66} cat ~library/bin/do-CVSUP #!/bin/sh /usr/local/sbin/cvsup supfile.cvsup TODAY=`date +%C%y%m%d` cat >/usr/src/.timestamp < SNAPDATE="`sed "s/#define FreeBSD_Source_Timestamp //" RELEASE="${REVISION}-${SNAPDATE}" 85c85 < v=`cat version` u=${USER-root} d=`pwd` h=`hostname` t=`date` --- > v=`cat version` u=${USER-root} d=`pwd` h=`hostname` t=`date +%D` 93c93 < \"${VERSION} #${v}: ${t}\\n ${u}@${h}:${d}\\n\";" >>vers.c --- > \"$1 #${v}: ${t}\\n\";" >>vers.c Richard Wackerbarth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 18 17:41:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA10731 for freebsd-current-outgoing; Sat, 18 Apr 1998 17:41:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (root@lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA10726 for ; Sun, 19 Apr 1998 00:41:39 GMT (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.8.7/8.8.7) with SMTP id UAA08890 for ; Sat, 18 Apr 1998 20:41:38 -0400 (EDT) Received: by mozart (5.65c/SAS/Domains/5-6-90) id AA21150; Sat, 18 Apr 1998 20:41:37 -0400 From: "John W. DeBoskey" Message-Id: <199804190041.AA21150@mozart> Subject: lnc1 & loss of carrier To: freebsd-current@FreeBSD.ORG Date: Sat, 18 Apr 1998 20:41:37 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have an HP Vectra XU 5/133C. It has lnc1 built into the motherboard which works fine for normal day to day activity. However, if I try to ftp a large file, I get the following (using a generic kernel): Apr 17 22:35:26 elisa /kernel: lnc1: Loss of carrier during transmit -- Net error? Apr 17 22:35:55 elisa last message repeated 31 times Apr 17 22:37:55 elisa last message repeated 104 times Apr 17 22:47:53 elisa last message repeated 440 times Apr 17 22:57:55 elisa last message repeated 453 times Apr 17 23:07:55 elisa last message repeated 431 times Apr 17 23:17:55 elisa last message repeated 440 times Apr 17 23:27:56 elisa last message repeated 460 times Apr 17 23:37:56 elisa last message repeated 449 times Apr 17 23:45:03 elisa last message repeated 330 times With the above errors, the transfer rate is: 94030KB 4178 seconds (22.50 KB/Sec) (Not real good :-( >From inconfig -a lnc1: flags=843 mtu 1500 inet 172.21.10.5 netmask 0xffffff00 broadcast 172.21.10.255 ether 08:00:09:c3:71:3e >From uname -a FreeBSD elisa.jwd.sas.com 3.0-971215-SNAP FreeBSD 3.0-971215-SNAP #0: Mon Dec 15 10:22:08 GMT 1997 root@make.ican.net:/usr/src/sys/compile/GENERIC i386 And from dmesg: lnc1: rev 0x02 int b irq 9 on pci0.3.0 lnc1: PCnet-32 VL-Bus address 08:00:09:c3:71:3e Does anyone have any ideas on what might be causing this? I've swapped out ethernet cabling between the Fbsd box and my other unix box and isdn router, but to no effect. Thanks, John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 18 17:54:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA13591 for freebsd-current-outgoing; Sat, 18 Apr 1998 17:54:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chaotic.ultra.net.au (totally.damaged.org [198.142.63.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA13545 for ; Sun, 19 Apr 1998 00:54:13 GMT (envelope-from simon@chaotic.ultra.net.au) Received: (from simon@localhost) by chaotic.ultra.net.au (8.8.8/8.8.8) id KAA00320 for freebsd-current@freebsd.org; Sun, 19 Apr 1998 10:52:02 +1000 (EST) Message-ID: X-Mailer: XFMail 1.3-beta-041398 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Date: Sun, 19 Apr 1998 10:52:01 +1000 (EST) Organization: Chaotic Software From: Simon Coggins To: freebsd-current@FreeBSD.ORG Subject: Problems with X windows, and Shared memory Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I'm running -current last updated FreeBSD chaotic 3.0-CURRENT FreeBSD 3.0-CURRENT #0: Thu Apr 16 19:33:14 EST 1998 I'm seeing the following problems, X windows locks up, and I have to ctrl alt backspace to get out of it, and if I run x windows again the whole machine locks up and I have to reboot. If I edit a file after I ctrl alt backspace then reload xwindows that file i edited is trashed. This problem also arises if I just close down X windows then reload it it'll lock solid and I have power cycle. On a separate note, I saw someone talking about a shared memory problem. I've been experiencing the same problems with Quake, you run quake and it won't free the shared memory I have to do it manually. Regards Simon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 18 18:00:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA14741 for freebsd-current-outgoing; Sat, 18 Apr 1998 18:00:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mhub3.tc.umn.edu (0@mhub3.tc.umn.edu [128.101.131.53]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA14720 for ; Sun, 19 Apr 1998 01:00:16 GMT (envelope-from adkin003@tc.umn.edu) Received: from gold.tc.umn.edu by mhub3.tc.umn.edu; Sat, 18 Apr 98 20:00:09 -0500 Received: from pub-12-b-22.dialup.umn.edu by gold.tc.umn.edu; Sat, 18 Apr 98 20:00:08 -0500 Date: Sat, 18 Apr 1998 20:00:04 -0500 (CDT) From: dave adkins X-Sender: adkin003@samthedog To: freebsd-current@FreeBSD.ORG Subject: systat and newlines in names Message-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, well, a little more investigation showed that the entries in vector.h that config generated were not being handled correctly by egcs. I wonder if its also a problem with gcc 2.8.x. I should have thought of that before posting, sorry. dave adkins To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 18 18:48:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20858 for freebsd-current-outgoing; Sat, 18 Apr 1998 18:48:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.atipa.com (altrox.atipa.com [208.128.22.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA20820 for ; Sun, 19 Apr 1998 01:48:01 GMT (envelope-from freebsd@atipa.com) Received: (qmail 21999 invoked by uid 1017); 19 Apr 1998 00:45:18 -0000 Date: Sat, 18 Apr 1998 18:45:18 -0600 (MDT) From: Atipa To: Andrzej Bialecki cc: freebsd-current@FreeBSD.ORG Subject: Re: There was PicoBSD - let there be a Mini... 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 was working on a Tcl/Tk frontend to Userland PPP. If that would be helpful for this project, let me know and I will continue work. I put it on the back burner a couple months ago... Looking at RedHat Linux as an example of GUI admin tools for UNIX converts, they use lots of Tk. I think that would be a good addition to a FreeBSD "usable preview" as such. This is also like a different project that I was thinking about. My idea was very similar, except the whole distribution came on a bootable CD-ROM w/ live filesystem. You could mount /etc on MFS, and fire up a X11 w/ a basic SVGA server, and use X11 for setup. Kevin On Sat, 18 Apr 1998, Andrzej Bialecki wrote: > Hi! > > I seem to have some crazy ideas from time to time... Here's one of them. > > I propose to add another type of installation combined with a special > distribution set. The idea behind it is to let people who are completely > new to FreeBSD just try the system without really installing it (which > bears all the hassle of repartitioning etc.), and to have positive enough > impression to install i then in normal way. I admit that this idea occured > to me when I tried the JavaPC preview. :-) > > Here's what the setup would be like: > > * the whole installation (available in sysinstall :-) would place FreeBSD > on an existing DOS partition. Installation program would create the file > with filesystem on it (which will then be mounted on a vn(4) device). This > will require (well, it depends) ca. 16-24MB of free space on a DOS > partition. > > * then the special distribution set would be transferred to the vn-mounted > file. This distribution would contain (among others): basic system > utilities, pretty minimal XWindow with SVGA server and a nice window > manager (qvwm?) with file manager (FreeBSD Explorer?); and of course > Netscape/Mozilla browser with Java. > > * the most important requirement of this set would be that each element > work as expected with almost no setup on user's part (except > network/dialup setup, which can be done with user-friendly script). > > * the whole thing would be started from DOS (using fbsdboot.exe). This > will probably require special C:\kernel with small MFS, containing > init(8), mount, vnconfig etc.. which after booting would first mount the > DOS partition, and then vnconfig the previously created file with OS on > it, and mount it on /. > > Well, that's basically the whole idea. How do you like it? > > I'm willing to try it anyway, and even to write some of the glue code > needed to incorporate it into sysinstall. > > Andrzej Bialecki > > --------------------+--------------------------------------------------------- > abial@nask.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } > Research & Academic | "Be open-minded, but don't let your brains to fall out." > Network in Poland | All of the above (and more) is just my personal opinion. > --------------------+--------------------------------------------------------- > > > 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 Apr 18 21:37:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA09289 for freebsd-current-outgoing; Sat, 18 Apr 1998 21:37:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sasami.jurai.net (winter@sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA09282 for ; Sun, 19 Apr 1998 04:37:49 GMT (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id AAA04202; Sun, 19 Apr 1998 00:36:45 -0400 (EDT) Date: Sun, 19 Apr 1998 00:36:44 -0400 (EDT) From: "Matthew N. Dodd" To: Atipa cc: Andrzej Bialecki , freebsd-current@FreeBSD.ORG Subject: Re: There was PicoBSD - let there be a Mini... 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, 18 Apr 1998, Atipa wrote: > Looking at RedHat Linux as an example of GUI admin tools for UNIX > converts, they use lots of Tk. I think that would be a good addition to a > FreeBSD "usable preview" as such. I think you'll be more impressed with the Perl bindings for Gtk. The Gnome people have a gnome app that frontends their PPP. It appears to be linux centric but wouldn't be a bad thing to look at. /* Matthew N. Dodd | A memory retaining a love you had for life winter@jurai.net | As cruel as it seems nothing ever seems to http://www.jurai.net/~winter | go right - FLA M 3.1:53 */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 18 23:58:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA27405 for freebsd-current-outgoing; Sat, 18 Apr 1998 23:58:50 -0700 (PDT) (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 GAA27379 for ; Sun, 19 Apr 1998 06:58:39 GMT (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id HAA11593; Sun, 19 Apr 1998 07:19:26 +0200 From: Luigi Rizzo Message-Id: <199804190519.HAA11593@labinfo.iet.unipi.it> Subject: Can I have the root partition on other than UFS ? (was miniBSD...) To: luigi@labinfo.iet.unipi.it (Luigi Rizzo) Date: Sun, 19 Apr 1998 07:19:26 +0200 (MET DST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG About the discussion on minbsd, I am curious: can we mount the root partition from MSDOSFS or CD9660 ? I know we can have it from UFS or NFS, but not sure about other filesystem types (unless one plays tricks with root in mfs as it is done on the boot floppy...). cheers luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message