From owner-freebsd-current Sun Apr 16 00:15:57 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA20976 for current-outgoing; Sun, 16 Apr 1995 00:15:57 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id AAA20962 for ; Sun, 16 Apr 1995 00:15:45 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA24169; Sun, 16 Apr 1995 09:15:33 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA10898; Sun, 16 Apr 1995 09:15:32 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id JAA15392; Sun, 16 Apr 1995 09:10:51 +0200 From: J Wunsch Message-Id: <199504160710.JAA15392@uriah.heep.sax.de> Subject: Re: [0412-SNAP] missing libcompat.so.2.0 To: jdli@CCCA.NCTU.edu.tw (醉生夢死 無言以對) Date: Sun, 16 Apr 1995 09:10:51 +0200 (MET DST) Cc: freebsd-current@FreeBSD.org In-Reply-To: <199504152013.EAA13942@CCCA.NCTU.edu.tw> from "醉生夢死 無言以對" at Apr 16, 95 04:13:48 am Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 601 Sender: current-owner@FreeBSD.org Precedence: bulk As 醉生夢死 無言以對 wrote: > > I just installed 0412-SNAP, and found my old programs out of work > due to missing /usr/lib/libcompat.so.2.0. > > Is it been removed (like libgcc.so.261.0) ?! I guess nobody thought about this. It's been removed, but unlike with libgcc.so, the linker would start to link against this one as soon as you put it back into /usr/lib again. Perhaps you can put it at some other place and make it only known via ldconfig. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Apr 16 00:56:28 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA21985 for current-outgoing; Sun, 16 Apr 1995 00:56:28 -0700 Received: from easynet.com ([198.67.38.6]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id AAA21979 for ; Sun, 16 Apr 1995 00:56:27 -0700 Received: by easynet.com (Smail3.1.28.1 #7) id m0s0P5a-000rdAC; Sun, 16 Apr 95 00:49 WET DST Message-Id: From: brian@mediacity.com (Brian Litzinger) Subject: Re: Memory init pattern To: henrich@crh.cl.msu.edu (Charles Henrich) Date: Sun, 16 Apr 1995 00:49:50 -0700 (PDT) Cc: freebsd-current@FreeBSD.org In-Reply-To: <199504160314.UAA16947@freefall.cdrom.com> from "Charles Henrich" at Apr 15, 95 11:14:21 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1166 Sender: current-owner@FreeBSD.org Precedence: bulk > > >Already in use doesn't mean "perfect and can't be better" way to do > >things. Since this did cause even Microsoft PR problems, it seems > >silly to not avoid the same mistake if it costs nothing. > > >Hey, I'm not suggesting filling memory with zeros or all "U"s (ala WATFIV), > >just pick something that doesn't mean anything in any language or culture. > >Save the FreeBSD PR people some headaches later. (I agree - we do have > >enough controversy now just with the daemon logo unfortunately.) > > *bitch moan flame on* > > Aggh, goddamn cant Political Correct stay the hell out of something? As a > precedent AIX uses 0xdeadbeef as its fill pattern, its useful, and its pretty > funny, the daemon logo is really spiffy. Who really gives a rats ass if > someone who has no life takes exception to it? Tough shit, they get what they > pay for no? > > *flame off* I agree with the original posters sentiment. If FreeBSD wants to be taken seriously in the business community, which I sincerely hope it does and would like to help in making it so, it has to "play the game", by the rules the game is played by. Brian Litzinger brian@easynet.com From owner-freebsd-current Sun Apr 16 05:32:32 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA28714 for current-outgoing; Sun, 16 Apr 1995 05:32:32 -0700 Received: from specgw.spec.co.jp (specgw.spec.co.jp [202.32.13.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA28708 for ; Sun, 16 Apr 1995 05:32:28 -0700 Received: from localhost (uucp@localhost) by specgw.spec.co.jp (8.6.5/3.3Wb-SPEC) with UUCP id VAA22103; Sun, 16 Apr 1995 21:27:00 +0901 Received: by tama.spec.co.jp (8.6.11/6.4J.5) id RAA00474; Sun, 16 Apr 1995 17:18:14 +0900 From: Atsushi Murai Message-Id: <199504160818.RAA00474@tama.spec.co.jp> Subject: Re: man ppp To: gary@palmer.demon.co.uk (Gary Palmer) Date: Sun, 16 Apr 1995 17:18:13 +0900 (JST) Cc: FreeBSD-Current@FreeBSD.org In-Reply-To: <3739.796600041@palmer.demon.co.uk> from "Gary Palmer" at Mar 30, 95 10:47:21 pm Reply-To: amurai@spec.co.jp X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 514 Sender: current-owner@FreeBSD.org Precedence: bulk > Someone want to delve into this man page and tidy it up? The english > is kinda convoluted in places and (for me anyhow) difficult to follow! > In places I wouldn't even dare to try to re-write it as I dunno what's > meant! Could you help me for re-writing ppp man page with NATIVE/Excellent English ? We don't want to leave it ! > Gary Atsushi. -- Atsushi Murai Internet: amurai@spec.co.jp System Planning and Engineering Co,.Ltd. Voice : +81-33833-5341 From owner-freebsd-current Sun Apr 16 05:44:34 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA28905 for current-outgoing; Sun, 16 Apr 1995 05:44:34 -0700 Received: from gw.itfs.nsk.su (gw.itfs.nsk.su [193.124.36.33]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA28882 for ; Sun, 16 Apr 1995 05:43:56 -0700 Received: (nnd@localhost) by gw.itfs.nsk.su (8.6.12/8.6.12) id TAA00756 for current@freebsd.org; Sun, 16 Apr 1995 19:43:16 +0700 Date: Sun, 16 Apr 1995 19:43:16 +0700 From: "Nickolay N. Dudorov" Message-Id: <199504161243.TAA00756@gw.itfs.nsk.su> To: current@FreeBSD.org Subject: Ipfw/Ipacct questions Sender: current-owner@FreeBSD.org Precedence: bulk Ipfirewall/Ipaccounting code in current only partially enabled/disabled by IPFIREWALL/IPACCT kernel config options. Why does this code contains run time tests (f.e. if(ip_acct_cnt_ptr == NULL) ) when I config kernel without IPFIREWALL/IPACCT ? Is it possible to #ifdef all such tests by IPFIREWALL/IPACCT ? N.Dudorov From owner-freebsd-current Sun Apr 16 05:51:12 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA29021 for current-outgoing; Sun, 16 Apr 1995 05:51:12 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA29015 for ; Sun, 16 Apr 1995 05:51:09 -0700 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id FAA21614; Sun, 16 Apr 1995 05:51:00 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id FAA00127; Sun, 16 Apr 1995 05:51:00 -0700 Message-Id: <199504161251.FAA00127@corbin.Root.COM> To: "Nickolay N. Dudorov" cc: current@FreeBSD.org Subject: Re: Ipfw/Ipacct questions In-reply-to: Your message of "Sun, 16 Apr 95 19:43:16 +0700." <199504161243.TAA00756@gw.itfs.nsk.su> From: David Greenman Reply-To: davidg@Root.COM Date: Sun, 16 Apr 1995 05:50:59 -0700 Sender: current-owner@FreeBSD.org Precedence: bulk > Ipfirewall/Ipaccounting code in current >only partially enabled/disabled by IPFIREWALL/IPACCT kernel >config options. Why does this code contains run time tests >(f.e. if(ip_acct_cnt_ptr == NULL) ) when I config kernel >without IPFIREWALL/IPACCT ? Is it possible to #ifdef all Because ipfw is also an LKM. -DG From owner-freebsd-current Sun Apr 16 06:01:49 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA29417 for current-outgoing; Sun, 16 Apr 1995 06:01:49 -0700 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id GAA29410 for ; Sun, 16 Apr 1995 06:01:47 -0700 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id PAA09226 ; Sun, 16 Apr 1995 15:01:44 +0200 Received: from (roberto@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) id PAA00269 ; Sun, 16 Apr 1995 15:01:43 +0200 From: roberto@blaise.ibp.fr (Ollivier Robert) Message-Id: <199504161301.PAA00269@blaise.ibp.fr> Subject: Re: Interesting (and odd) effect in -current To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Sun, 16 Apr 1995 15:01:43 +0200 (MET DST) Cc: jkh@freefall.cdrom.com, current@FreeBSD.org In-Reply-To: <199504152313.QAA05625@gndrsh.aac.dev.com> from "Rodney W. Grimes" at Apr 15, 95 04:13:00 pm X-Operating-System: FreeBSD 2.1.0-Development ctm#480 X-Mailer: ELM [version 2.4 PL23beta2] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 259 Sender: current-owner@FreeBSD.org Precedence: bulk > biddable ciliella diabolic fellable official ^^^^^^^^ We have a demon logo so we should take this one :-) -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@FreeBSD.ORG FreeBSD keltia 2.1.0-Development #7: Thu Mar 23 00:28:31 MET 1995 From owner-freebsd-current Sun Apr 16 06:15:34 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA29898 for current-outgoing; Sun, 16 Apr 1995 06:15:34 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id GAA29889 for ; Sun, 16 Apr 1995 06:15:31 -0700 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id GAA21798; Sun, 16 Apr 1995 06:15:27 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id GAA00213; Sun, 16 Apr 1995 06:15:27 -0700 Message-Id: <199504161315.GAA00213@corbin.Root.COM> To: roberto@blaise.ibp.fr (Ollivier Robert) cc: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes), jkh@freefall.cdrom.com, current@FreeBSD.org Subject: Re: Interesting (and odd) effect in -current In-reply-to: Your message of "Sun, 16 Apr 95 15:01:43 +0200." <199504161301.PAA00269@blaise.ibp.fr> From: David Greenman Reply-To: davidg@Root.COM Date: Sun, 16 Apr 1995 06:15:27 -0700 Sender: current-owner@FreeBSD.org Precedence: bulk >> biddable ciliella diabolic fellable official > ^^^^^^^^ >We have a demon logo so we should take this one :-) I didn't know the real meaning of "diabolic" until just before I was about to decide to use it. I thought "Hmmm, maybe I should look it up in the dictionary next to me and see what its true meaning is". I was surprised to find out that it meant "Of, concerning, or characteristic of the devil; satanic." ...then I was amazed at how I could have gone this far in life using that word without knowing what it really meant. Anyway, the code has been changed to use 0xdeadc0de. I hope everyone's happy. -DG From owner-freebsd-current Sun Apr 16 07:18:54 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA01389 for current-outgoing; Sun, 16 Apr 1995 07:18:54 -0700 Received: from gw.itfs.nsk.su (gw.itfs.nsk.su [193.124.36.33]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id HAA01346 for ; Sun, 16 Apr 1995 07:17:40 -0700 Received: (nnd@localhost) by gw.itfs.nsk.su (8.6.12/8.6.12) id VAA01173 for current@freebsd.org; Sun, 16 Apr 1995 21:16:25 +0700 Date: Sun, 16 Apr 1995 21:16:25 +0700 From: "Nickolay N. Dudorov" Message-Id: <199504161416.VAA01173@gw.itfs.nsk.su> To: current@FreeBSD.org Subject: Re: Ipfw/Ipacct questions Sender: current-owner@FreeBSD.org Precedence: bulk >> Ipfirewall/Ipaccounting code in current >>only partially enabled/disabled by IPFIREWALL/IPACCT kernel >>config options. Why does this code contains run time tests >>(f.e. if(ip_acct_cnt_ptr == NULL) ) when I config kernel >>without IPFIREWALL/IPACCT ? Is it possible to #ifdef all > > Because ipfw is also an LKM. > >-DG The next question - is it possible/feasible to build a kernel which'll not allow modload 'ipfw' LKM ? It seems to me that such a situation was here some time ago with IBCS2 support - i.e. I have to define option IBCS2 (?) for later use of IBCS2-support LKMs. N.Dudorov From owner-freebsd-current Sun Apr 16 08:42:41 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA05445 for current-outgoing; Sun, 16 Apr 1995 08:42:41 -0700 Received: from obiwan.pmr.com (obiwan.pmr.com [199.98.84.130]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id IAA05438 for ; Sun, 16 Apr 1995 08:42:38 -0700 Received: by obiwan.pmr.com (Smail3.1.29.1 #4) id m0s0WRn-00030eC; Sun, 16 Apr 95 10:41 CDT Message-Id: From: bob@obiwan.pmr.com (Bob Willcox) Subject: Re: 0412-SNAP is FUBAR To: phk@ref.tfs.com (Poul-Henning Kamp) Date: Sun, 16 Apr 1995 10:41:14 -0500 (CDT) Cc: jkh@freefall.cdrom.com, kargl@crosby.apl.washington.edu, bde@zeta.org.au, freebsd-current@FreeBSD.org In-Reply-To: <199504152124.OAA22122@ref.tfs.com> from "Poul-Henning Kamp" at Apr 15, 95 02:24:35 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 2148 Sender: current-owner@FreeBSD.org Precedence: bulk Poul-Henning Kamp wrote: > > > > When is the scsi version of the slice code scheduled for prime time use? > > > > The minute you see the commit messages go into sysinstall saying > > "make this utility understand slices" :-) > > > > More like, "you can grab the sd.c and wd.c from current and recompile > your kernel". > > Sysinstall is only a tool for loading FreeBSD onto the disk, the kernel > is all fine and ready to use slices. > > Problem is, until we fix sysinstall, we cannot use the "new" sd.c and wd.c > on the distribution :-( What version of the aic7xxx device driver is on the 412 snap? I have found that I can't use my AHA-2740A SCSI adapter on this snap, though -current is working ok. If I attempt to install with this adapter I get a panic. I went ahead and installed with my BusLogic BT-747S adapter without problems but when I switch to the Adaptec I also get a similar (I didn't take notes of the install panic, sorry) panic: Fatal trap 12: page fault while in kernel mode fault virtual address = 0xf06539fa fault code = supervisor write, page not present instruction pointer = 0x8:0xf019cb1d code segment = base 0x0, limit 0xfffff, type 0x1b DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = net tty panic: page fault syncing disks... Fatal trap 12: page fault while in kernel mode fault virtual address = 0x1b fault code = 0x8:0xf01215eb code segment = base -x0, limit 0xfffff, type 0x1b DBL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = net tty bio panic: page fault This occurs following the ed1: .... multi-line stuff on the console. Note that fsck's have been done by this time so the adapter and drive (its a Micropolis 2217) seem to be working fine. One last thing. With both the Adaptec and BusLogic adapters in the machine (this is how I run it under -current) the floppy disk boot sequence hangs right after the warning about there being no swap space. -- Bob Willcox bob@obiwan.pmr.com (or obiwan%bob@uunet.uu.net) Austin, TX From owner-freebsd-current Sun Apr 16 11:26:25 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA07954 for current-outgoing; Sun, 16 Apr 1995 11:26:25 -0700 Received: from news.rim.or.jp (news.rim.or.jp [202.255.181.3]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA07948 for ; Sun, 16 Apr 1995 11:26:23 -0700 Received: (from uucp@localhost) by news.rim.or.jp (8.6.10+2.4W/3.3W-rim1.0) with UUCP id DAA25404 for freebsd-current@FreeBSD.org; Mon, 17 Apr 1995 03:26:21 +0900 Received: from us.and.or.jp (localhost [127.0.0.1]) by us.and.or.jp (8.6.11/3.3W8) with ESMTP id DAA12647 for ; Mon, 17 Apr 1995 03:07:06 +0900 Message-Id: <199504161807.DAA12647@us.and.or.jp> Reply-To: sa2c@st.rim.or.jp To: freebsd-current@FreeBSD.org Subject: Re: [0412-SNAP] missing libcompat.so.2.0 In-reply-to: <199504160710.JAA15392@uriah.heep.sax.de> J Wunsch's message of Sun, 16 Apr 1995 09:10:51 +0200 (MET DST) Date: Mon, 17 Apr 1995 03:07:05 +0900 From: NIIMI Satoshi Sender: current-owner@FreeBSD.org Precedence: bulk > Perhaps you can put it at some other place and make it only known > via ldconfig. How about to make a /usr/compat/lib directory in standard distribution and change ldconfig stuff in /etc/rc to following? if [ -x /sbin/ldconfig ]; then _LDC=/usr/lib if [ -d /usr/X11R6/lib ]; then _LDC="${_LDC} /usr/X11R6/lib" ; fi if [ -d /usr/X386/lib ]; then _LDC="${_LDC} /usr/X386/lib" ; fi if [ -d /usr/local/lib ]; then _LDC="${_LDC} /usr/local/lib" ; fi if [ -d /usr/gnu/lib ]; then _LDC="${_LDC} /usr/gnu/lib" ; fi if [ -d /usr/compat/lib ]; then _LDC="${_LDC} /usr/compat/lib" ; fi echo 'setting ldconfig path:' ${_LDC} ldconfig ${_LDC} fi And It is nice if compat2.0 stuff are stored in tar.gz file with following manner. usr/compat/lib/libgcc.so.261.0 usr/compat/lib/libcompat.so.2.0 etc... Of course, there should be a notice to users like "If you want to install a shared libraries which is used in prior releases, you must place it in /usr/compat/lib directory". Sorry for my English, and hope readers can understand this mail. -- NIIMI Satoshi From owner-freebsd-current Sun Apr 16 23:27:18 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA08477 for current-outgoing; Sun, 16 Apr 1995 23:27:18 -0700 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id XAA08470 ; Sun, 16 Apr 1995 23:27:16 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: uhclem@nemesis.lonestar.org (Frank Durda IV) cc: freebsd-current@FreeBSD.org, davidg@Root.COM Subject: Re: Memory init pattern In-reply-to: Your message of "Sat, 15 Apr 95 19:48:00 CDT." Date: Sun, 16 Apr 1995 23:27:15 -0700 Message-ID: <8469.798100035@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk > Fine. I still Strongly recommend picking something that doesn't mean > anything or is otherwise harmless in meaning, such as 0xbad1bad2. > Still easy to spot or search for - and no one can complain. I'm sorry, I'm just having a hard time believing at all that we're arguing about hexadecimal patterns to fill memory with. Perhaps this is a flashback, or I simply ate some ergot-tainted bread this morning and am now in the full-throes of an LSD induced hallucination. I think it's safe to say that a race of creatures which worries overmuch about potentially hidden meanings in arbitrary patters of numbers is a race of creatures who's time is up, geologically speaking, and should have the good grace to wipe themselves off the face of the map so that the NEXT dominant species (mutant cockroaches, most likely) can have its well-deserved turn. Jordan From owner-freebsd-current Mon Apr 17 01:39:46 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA12018 for current-outgoing; Mon, 17 Apr 1995 01:39:46 -0700 Received: from bunyip.cc.uq.oz.au (bunyip.cc.uq.oz.au [130.102.2.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id BAA12003 for ; Mon, 17 Apr 1995 01:39:35 -0700 Received: from cc.uq.oz.au by bunyip.cc.uq.oz.au id <02910-0@bunyip.cc.uq.oz.au>; Mon, 17 Apr 1995 18:35:53 +1000 Received: from netfl15a.devetir.qld.gov.au by pandora.devetir.qld.gov.au (8.6.10/DEVETIR-E0.3a) with ESMTP id PAA19994; Mon, 17 Apr 1995 15:17:48 +1000 Received: from localhost by netfl15a.devetir.qld.gov.au (8.6.8.1/DEVETIR-0.1) id FAA08801; Mon, 17 Apr 1995 05:15:55 GMT Message-Id: <199504170515.FAA08801@netfl15a.devetir.qld.gov.au> X-Mailer: exmh version 1.6beta 3/23/95 To: "Justin T. Gibbs" cc: current@FreeBSD.org Subject: Re: Fixed seagate.c (incl. recent devconf changes) In-reply-to: Your message of "Fri, 14 Apr 1995 19:08:51 MST." <199504150208.TAA00515@estienne.cs.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 17 Apr 1995 15:15:54 +1000 From: Stephen Hocking Sender: current-owner@FreeBSD.org Precedence: bulk > >Recently I reported a bug (i386/337) about the -current seagate controller > >code not working with my hardware. I also enclosed a fix, but I'm not sure if > >after the recent set of SCSI changes that it has made it in or is event being > >considered yet. Anyway, incorporating the recent changes, here's the working > >version. It's slow, but it works, unlike the later version. > > > > Your changes are based on a very old version of the driver. This makes > it difficult for us to see what you changed and what was changed in other > revisions of the driver. Can you make your changes relative to version 1.7 > (today's current) and resubmit them as context diffs (diff -c)? > > Thank you very much for your submission, and I hope we can integrate your > changes once we get them in a format where we can better understand what > they are. :) > > -- > Justin T. Gibbs > ============================================== > TCS Instructional Group - Programmer/Analyst 1 > Cory | Po | Danube | Volga | Parker | Torus > ============================================== OK, here it is, against the seagate.c found on the 2.0 CDROM.... *** /tmp/seagate.c.2.0 Mon Apr 17 15:13:16 1995 --- seagate.c Thu Apr 13 13:25:07 1995 *************** *** 104,111 **** * the use of blind transfers coded in assembler. SEA_ASSEMBLER is no good * without SEA_BLINDTRANSFER defined. */ ! #define SEA_BLINDTRANSFER 1 /* do blind transfers */ ! #define SEA_ASSEMBLER 1 /* Use assembly code for fast transfers */ /* * defining SEANOMSGS causes messages not to be used (thereby disabling --- 104,111 ---- * the use of blind transfers coded in assembler. SEA_ASSEMBLER is no good * without SEA_BLINDTRANSFER defined. */ ! #undef SEA_BLINDTRANSFER 1 /* do blind transfers */ ! #undef SEA_ASSEMBLER 1 /* Use assembly code for fast transfers */ /* * defining SEANOMSGS causes messages not to be used (thereby disabling *************** *** 390,395 **** --- 390,404 ---- } #endif + static char sea_description [80]; /* XXX BOGUS!!! */ + static struct kern_devconf sea_kdc[NSEA] = {{ + 0, 0, 0, "sea", 0, { MDDT_ISA, 0, "bio" }, + isa_generic_externalize, 0, 0, ISA_EXTERNALLEN, &kdc_isa0, 0, + DC_UNCONFIGURED, sea_description, + DC_CLS_MISC /* host adapters aren't special */ + } }; + + /***********************************************************************\ * Check if the device can be found at the port given and if so, detect * * the type of board. Set it up ready for further work. Takes the * *************** *** 514,519 **** --- 523,530 ---- sea->st0x_dr = (void *) (((unsigned char *) sea->basemaddr) + ((sea->ctrl_type == SEAGATE) ? 0x1c00 : 0x1e00)); + strcpy(sea_description, (sea->ctrl_type == SEAGATE) ? "Seagate ST01/ST02": + "Future Domain TMC-885/TMC-950"); /* Test controller RAM (works the same way on future domain cards?) */ *(sea->basemaddr + SEAGATERAMOFFSET) = 0xa5; *(sea->basemaddr + SEAGATERAMOFFSET + 1) = 0x5a; *************** *** 537,560 **** return(1); } - static struct kern_devconf kdc_sea[NSEA] = { { - 0, 0, 0, /* filled in by dev_attach */ - "sea", 0, { MDDT_ISA, 0, "bio" }, - isa_generic_externalize, 0, 0, ISA_EXTERNALLEN, - &kdc_isa0, /* parent */ - 0, /* parentdata */ - DC_BUSY, /* host adaptors are always busy */ - "Seagate ST01/02 SCSI controller" - } }; - static inline void sea_registerdev(struct isa_device *id) { if(id->id_unit) ! kdc_sea[id->id_unit] = kdc_sea[0]; ! kdc_sea[id->id_unit].kdc_unit = id->id_unit; ! kdc_sea[id->id_unit].kdc_isa = id; ! dev_attach(&kdc_sea[id->id_unit]); } /***********************************************\ --- 548,561 ---- return(1); } static inline void sea_registerdev(struct isa_device *id) { if(id->id_unit) ! sea_kdc[id->id_unit] = sea_kdc[0]; ! sea_kdc[id->id_unit].kdc_unit = id->id_unit; ! sea_kdc[id->id_unit].kdc_isa = id; ! dev_attach(&sea_kdc[id->id_unit]); } /***********************************************\ *************** *** 571,576 **** --- 572,578 ---- printf("sea_attach called\n"); #endif + sea_kdc[unit].kdc_state = DC_BUSY; /* host adapters are always busy */ /* fill in the prototype scsi_link */ sea->sc_link.adapter_unit = unit; sea->sc_link.adapter_targ = sea->our_id; I do not speak for the Worker's Compensation Board of Queensland - They don't pay me enough for that! From owner-freebsd-current Mon Apr 17 01:39:37 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA12008 for current-outgoing; Mon, 17 Apr 1995 01:39:37 -0700 Received: from bunyip.cc.uq.oz.au (bunyip.cc.uq.oz.au [130.102.2.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id BAA11986 for ; Mon, 17 Apr 1995 01:36:08 -0700 Received: from cc.uq.oz.au by bunyip.cc.uq.oz.au id <02904-0@bunyip.cc.uq.oz.au>; Mon, 17 Apr 1995 18:35:49 +1000 Received: from orion.devetir.qld.gov.au by pandora.devetir.qld.gov.au (8.6.10/DEVETIR-E0.3a) with ESMTP id SAA20901 for ; Mon, 17 Apr 1995 18:34:04 +1000 Received: from localhost by orion.devetir.qld.gov.au (8.6.10/DEVETIR-0.2a) id SAA27341; Mon, 17 Apr 1995 18:31:35 +1000 Message-Id: <199504170831.SAA27341@orion.devetir.qld.gov.au> To: current@FreeBSD.org cc: syssgm@devetir.qld.gov.au Subject: fcntl F_SETLK backward compatibility kludge Date: Mon, 17 Apr 1995 18:31:35 +1000 From: Stephen McKay Sender: current-owner@FreeBSD.org Precedence: bulk Between 1.1.5 and 2.0, the format of one of the parameters to the fcntl() system call changed, but neither the system call number nor the command codes passed to it were updated to reflect this. This causes some 1.1.5 binaries to fail when run on 2.0 systems. This is a proposal which should almost totally heal this minor wart. Old struct flock from Freebsd 1.1.5 and earlier: type whence start length pid junk (because of padding) +-----+-----+-----------+-----------+-----+ - - + | 16 | 16 | 32 | 32 | 16 | | +-----+-----+-----------+-----------+-----+ - - + New struct flock from Freebsd 2.0 and later: start length pid type whence +-----------------------+-----------------------+-----------+-----+-----+ | 64 | 64 | 32 | 16 | 16 | +-----------------------+-----------------------+-----------+-----+-----+ I propose that fcntl() command codes 7, 8, 9 be reserved for the backward compatible locking calls, and new values 10, 11, 12 be allocated for use in FreeBSD 2.1 as F_GETLK, F_SETLK and F_SETLKW. Code bracketed by #ifdef COMPAT_43 should be added to fcntl() in kern_descrip.c to handle the old case in the following way: Using the fact that "type" must be 1, 2 or 3, and "whence" must be 0, 1 or 2, an educated guess can be made as to which of the two forms is being used by the currently executing binary. The two possible cases of confusion are when an old style struct flock is followed in memory by data that just happens to contain 1, 2 or 3 and 0, 1 or 2 in the right place, or when a new style struct flock specifies a start offset with a low 32 bits of 0x00000001, 0x00000002, 0x00000003, 0x00010001, 0x00010002, 0x00010003, 0x00020001, 0x00020002, or 0x00020003. In these cases, the old style should be assumed, possibly logging a kernel warning message. The assumption here is that the 2.0 binary is newer and thus more easily recompiled to use the unambiguous 2.1 fcntl() call. I have scanned the 2.0 source code for uses of fcntl() locking and have found four cases. "amd", "vi", and "sendmail" use fcntl() locking to simulate flock() locking if that is unavailable. "at" uses fcntl() locking, but only with full file locking (whence = 0, start = 0, end = 0) which is correctly detected by the above scheme. It seems likely that most uses of fcntl() locking are to simulate flock(), and will be correctly handled. If added complication is desired :-) a number of other checks can be done. It seems very unlikely that any program in this transitional situation is going to be using files >= 2^32 bytes, and so the high 32 bits of a new style "start" and "length" must be 0 or -1. Thus an old style flock with a "start" field not 0 or -1 will not be mistaken for a new style flock. Similarly, the "pid" field and padding of an old style struct flock can contain garbage, and be an unmistakable marker since it overlaps the high half of a new style "length" field. There are also some constraints on what values "start" and "length" can have for various values of "whence". If guessing for each call is not your idea of determinism, there are a few spare bits in u_pcb.pcb_flags in the user struct. A value could be determined on the first call, and stored here to remove future guesswork. So, how far should we go to support a few old binaries using a system call that the man page bags so heavily? My second favourite proposal after this one, is to convert the old calls to simply log a kernel error message, and return a failure code to the program. Old binaries will then be detected and hopefully upgraded. I am available to implement and test either of these solutions as I currently have both 1.1.5 and 2.0 at home. Stephen. From owner-freebsd-current Mon Apr 17 07:28:37 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA00692 for current-outgoing; Mon, 17 Apr 1995 07:28:37 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id HAA00603 for ; Mon, 17 Apr 1995 07:26:28 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA06908; Mon, 17 Apr 1995 16:25:15 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id QAA20806; Mon, 17 Apr 1995 16:25:13 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id OAA06482; Mon, 17 Apr 1995 14:43:00 +0200 From: J Wunsch Message-Id: <199504171243.OAA06482@uriah.heep.sax.de> Subject: Re: fcntl F_SETLK backward compatibility kludge To: syssgm@devetir.qld.gov.au (Stephen McKay) Date: Mon, 17 Apr 1995 14:42:58 +0200 (MET DST) Cc: current@FreeBSD.org, syssgm@devetir.qld.gov.au In-Reply-To: <199504170831.SAA27341@orion.devetir.qld.gov.au> from "Stephen McKay" at Apr 17, 95 06:31:35 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 744 Sender: current-owner@FreeBSD.org Precedence: bulk As Stephen McKay wrote: > > I have scanned the 2.0 source code for uses of fcntl() locking and have found > four cases. "amd", "vi", and "sendmail" use fcntl() locking to simulate > flock() locking if that is unavailable. "at" uses fcntl() locking, but only > with full file locking (whence = 0, start = 0, end = 0) which is correctly > detected by the above scheme. It seems likely that most uses of fcntl() > locking are to simulate flock(), and will be correctly handled. Elm was also using this (config-dependant, but it suggested to use fcntl, flock and lock files alltogether by default). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Apr 17 07:43:18 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA01734 for current-outgoing; Mon, 17 Apr 1995 07:43:18 -0700 Received: from irbs.com (irbs.com [199.182.75.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id HAA01718 for ; Mon, 17 Apr 1995 07:43:04 -0700 Received: (from jc@localhost) by irbs.com (8.6.11/8.6.6) id KAA26207 for freebsd-current@freefall.cdrom.com; Mon, 17 Apr 1995 10:42:54 -0400 From: John Capo Message-Id: <199504171442.KAA26207@irbs.com> Subject: Re: Missing telent login prompt To: freebsd-current@freefall.cdrom.com (freebsd-current) Date: Mon, 17 Apr 1995 10:42:52 -0400 (EDT) In-Reply-To: <9504150736.AA01776@cs.weber.edu> from "Terry Lambert" at Apr 15, 95 01:36:20 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 5378 Sender: current-owner@FreeBSD.org Precedence: bulk Terry Lambert writes: > > > > > > > No, the prompt fell on the floor. login is running and waiting > > > for a user name. Terry says its a option negotiation problem. > > > > Hmmmm, haven't seen that problem here then. My problem is simply > > a delayed login prompt or password (i.e., happens whether I use telnet > > or rlogin to contact the FreeBSD box). > > Terry introduced this problem in a prerelease version of a commercial > telnet client, which is why he thinks it's option negotiation. 8-(. > > The missing login prompt depends on the erase character. Script started on Mon Apr 17 10:02:41 1995 irbs 1% stty erase '^H' irbs 2% telnet freefall.cdrom.com Trying 192.216.222.4... Connected to freefall.cdrom.com. Escape character is '^]'. FreeBSD (freefall.cdrom.com) (ttyp6) ^] telnet> ^DConnection closed. irbs 3% stty erase '^?' irbs 4% telnet freefall.cdrom.com Trying 192.216.222.4... Connected to freefall.cdrom.com. Escape character is '^]'. FreeBSD (freefall.cdrom.com) (ttyp6) login: ^] telnet> ^DConnection closed. irbs 5% ^Dexit I _NEVER_ get a prompt from freefall if my erase character is ^H and I _ALWAYS_ get a prompt if my erase character is ^?. I have not been able to determine what is eating the login prompt. The slave side of the pty, login then a shell, is started in the middle of option negotiation. Starting the slave pty after option negotation works. Code compiled for Convex does this. Another problem was that when the slave pty is started the erase character for the slave is CERASE from sys/ttydefaults.h. This is set after telnet has negotiated an erase character. Telnetd notices that the erase character has changed and it notifies the other side of that fact. Your erase character has now been changed to CERASE rather than what your tty is set for. After login the erase character is set back to what the tty is set for. You only loose proper erase during login. I have an ISP friend that needed reliable telnet prompts from a 2.X machine for his naive users. This patch works if anyone else is interested. John Capo *** telnetd.c.orig Fri Aug 12 19:00:02 1994 --- telnetd.c Wed Apr 12 11:46:21 1995 *************** *** 740,749 **** char host_name[MAXHOSTNAMELEN]; char remote_host_name[MAXHOSTNAMELEN]; ! #ifndef convex ! extern void telnet P((int, int)); ! #else extern void telnet P((int, int, char *)); #endif /* --- 740,749 ---- char host_name[MAXHOSTNAMELEN]; char remote_host_name[MAXHOSTNAMELEN]; ! #if defined(convex) || defined(__FreeBSD__) extern void telnet P((int, int, char *)); + #else + extern void telnet P((int, int)); #endif /* *************** *** 837,843 **** /* * Start up the login process on the slave side of the terminal */ ! #ifndef convex startslave(host, level, user_name); #if defined(_SC_CRAY_SECURE_SYS) --- 837,843 ---- /* * Start up the login process on the slave side of the terminal */ ! #if !defined(convex) && !defined(__FreeBSD__) startslave(host, level, user_name); #if defined(_SC_CRAY_SECURE_SYS) *************** *** 849,855 **** --- 849,859 ---- } #endif /* _SC_CRAY_SECURE_SYS */ + #if __FreeBSD__ + telnet(net, pty, host); /* begin server processing */ + #else telnet(net, pty); /* begin server processing */ + #endif #else telnet(net, pty, host); #endif *************** *** 876,888 **** * hand data to telnet receiver finite state machine. */ void ! #ifndef convex ! telnet(f, p) ! #else telnet(f, p, host) #endif int f, p; ! #ifdef convex char *host; #endif { --- 880,892 ---- * hand data to telnet receiver finite state machine. */ void ! #if defined(convex) || defined(__FreeBSD__) telnet(f, p, host) + #else + telnet(f, p) #endif int f, p; ! #if defined(convex) || defined(__FreeBSD__) char *host; #endif { *************** *** 1120,1126 **** {sprintf(nfrontp, "td: Entering processing loop\r\n"); nfrontp += strlen(nfrontp);}); ! #ifdef convex startslave(host); #endif --- 1124,1130 ---- {sprintf(nfrontp, "td: Entering processing loop\r\n"); nfrontp += strlen(nfrontp);}); ! #if defined(convex) || defined(__FreeBSD__) startslave(host); #endif *** sys_term.c.orig Thu Feb 9 10:17:32 1995 --- sys_term.c Thu Apr 13 13:10:34 1995 *************** *** 1025,1030 **** --- 1025,1031 ---- getptyslave() { register int t = -1; + char erase; #if !defined(CRAY) || !defined(NEWINIT) # ifdef LINEMODE *************** *** 1046,1052 **** # ifdef LINEMODE waslm = tty_linemode(); # endif ! /* * Make sure that we don't have a controlling tty, and --- 1047,1053 ---- # ifdef LINEMODE waslm = tty_linemode(); # endif ! erase = termbuf.c_cc[VERASE]; /* * Make sure that we don't have a controlling tty, and *************** *** 1090,1095 **** --- 1091,1097 ---- * set up the tty modes as we like them to be. */ init_termbuf(); + # ifdef TIOCGWINSZ if (def_row || def_col) { bzero((char *)&ws, sizeof(ws)); *************** *** 1133,1138 **** --- 1135,1143 ---- tty_rspeed((def_rspeed > 0) ? def_rspeed : 9600); tty_tspeed((def_tspeed > 0) ? def_tspeed : 9600); # ifdef LINEMODE + if (erase) + termbuf.c_cc[VERASE] = erase; + if (waslm) tty_setlinemode(1); # endif /* LINEMODE */ From owner-freebsd-current Mon Apr 17 10:32:44 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA09363 for current-outgoing; Mon, 17 Apr 1995 10:32:44 -0700 Received: from aries.ibms.sinica.edu.tw ([140.109.40.248]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA09351 for ; Mon, 17 Apr 1995 10:32:40 -0700 Received: (from taob@localhost) by aries.ibms.sinica.edu.tw (8.6.11/8.6.9) id BAA04114; Tue, 18 Apr 1995 01:32:57 +0800 Date: Tue, 18 Apr 1995 01:32:56 +0800 (CST) From: Brian Tao To: FREEBSD-CURRENT-L Subject: Behaviour of rm/rmdir Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk This is something that has been bothering me for years... dunno why I suddenly decide to bring it up now. ;-) Why do "rm -r[f]" and "rmdir" complain about removing an empty directory if you append a slash to the name? I mean, this looks pretty ridiculous to me: % du testdir 2371 testdir % rm -rf testdir/ rm: testdir/: Is a directory <--- tell me something I don't know... % rmdir testdir/ rmdir: testdir/: Is a directory <--- argh!!! It isn't a big deal to leave off the trailing slash, but filename completion in tcsh and bash both append it. Is this just a 4.4BSD thing? I checked around on our IRIX, SunOS, Solaris and AIX machines and none exhibit this behaviour. BSD/OS 2.0 rm/rmdir behave this way too. Bug or feature? -- Brian ("Though this be madness, yet there is method in't") Tao taob@gate.sinica.edu.tw <-- work ........ play --> taob@io.org From owner-freebsd-current Mon Apr 17 15:18:15 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA26507 for current-outgoing; Mon, 17 Apr 1995 15:18:15 -0700 Received: from devnull (devnull.mpd.tandem.com [131.124.4.29]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA26497 for ; Mon, 17 Apr 1995 15:18:11 -0700 Received: from olympus by devnull (8.6.8/8.6.6) id RAA08903; Mon, 17 Apr 1995 17:17:59 -0500 Received: by olympus (4.1/TSS2.1) id AA22907; Mon, 17 Apr 95 17:16:22 CDT From: faulkner@mpd.tandem.com (Boyd Faulkner) Message-Id: <9504172216.AA22907@olympus> Subject: stdlib.h:80: parse error before `__dead2' To: current@FreeBSD.org Date: Mon, 17 Apr 1995 17:16:21 -0500 (CDT) X-Mailer: ELM [version 2.4 PL17] Content-Type: text Content-Length: 1528 Sender: current-owner@FreeBSD.org Precedence: bulk I have been seeing these lately. What does it mean? I am compiling ImageMagick. tk fails the same way. Even after a sup and a build world. In file included from magick.h:9, from widget.c:50: /usr/include/stdlib.h:80: parse error before `__dead2' /usr/include/stdlib.h:80: warning: data definition has no type or storage class /usr/include/stdlib.h:82: parse error before `__pure2' /usr/include/stdlib.h:82: warning: data definition has no type or storage class /usr/include/stdlib.h:91: parse error before `__pure2' /usr/include/stdlib.h:91: warning: data definition has no type or storage class /usr/include/stdlib.h:93: parse error before `__dead2' /usr/include/stdlib.h:93: warning: data definition has no type or storage class /usr/include/stdlib.h:97: parse error before `__pure2' /usr/include/stdlib.h:97: warning: data definition has no type or storage class /usr/include/stdlib.h:99: parse error before `__pure2' /usr/include/stdlib.h:99: warning: data definition has no type or storage class In file included from magick.h:10, from widget.c:50: /usr/include/unistd.h:53: parse error before `__dead2' /usr/include/unistd.h:53: warning: data definition has no type or storage class In file included from magick.h:20, from widget.c:50: Boyd -- _______________________________________________________________________ Boyd Faulkner faulkner@isd.tandem.com _______________________________________________________________________ From owner-freebsd-current Mon Apr 17 19:33:53 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA10738 for current-outgoing; Mon, 17 Apr 1995 19:33:53 -0700 Received: from atari.cybernetics.net (atari.cybernetics.net [198.80.51.226]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA10724 for ; Mon, 17 Apr 1995 19:33:37 -0700 Received: from localhost (localhost [127.0.0.1]) by atari.cybernetics.net (8.6.11/8.6.9) with SMTP id WAA00472 for ; Mon, 17 Apr 1995 22:33:21 -0400 Message-Id: <199504180233.WAA00472@atari.cybernetics.net> X-Authentication-Warning: atari.cybernetics.net: Host localhost didn't use HELO protocol To: freebsd-current@FreeBSD.org Subject: msdos mounts won't mount under current 950416 Date: Mon, 17 Apr 1995 22:33:20 -0400 From: "Adam W. Hawks" Sender: current-owner@FreeBSD.org Precedence: bulk I just built a new kernel using deltas up to src-cur.0519 and now I can't mount the dos partitions that have worked up till delta 486 or so. What has changed or what do I need to change to get my dos partition back? Adam W. Hawks awhawks@server0.cybernetics.net From owner-freebsd-current Mon Apr 17 19:41:14 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA11157 for current-outgoing; Mon, 17 Apr 1995 19:41:14 -0700 Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id TAA11147 for ; Mon, 17 Apr 1995 19:41:11 -0700 Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <14457(1)>; Mon, 17 Apr 1995 19:40:35 PDT Received: by crevenia.parc.xerox.com id <49864>; Mon, 17 Apr 1995 19:40:31 -0700 From: Bill Fenner To: freebsd-current@FreeBSD.org Subject: fsck trashes / if no /lost+found? Message-Id: <95Apr17.194031pdt.49864@crevenia.parc.xerox.com> Date: Mon, 17 Apr 1995 19:40:28 PDT Sender: current-owner@FreeBSD.org Precedence: bulk I am running SNAP-950322. I crashed hard, and on the way up, fsck tried to reconnect a file when fsck'ing /usr. Apparently, for some reason there was no /usr/lost+found, and fsck printed an error something like "no room in /" when it said it was trying to create it. The fsck failed, and when I fsck'd manually it said there was no /, and it ended up reconnecting all the directories in /lost+found (after creating /lost+found). I managed to reconnect most everything where it belongs, but having to recreate /usr from /usr/lost+found is not something you want to do every day. I don't know enough about the ffs code myself to fix this, but if someone feels like looking into fsck's behavior in this case it might be a good idea. (Of course, it's entirely possible that going down hard actually did trash /usr's /, but I'm not convinced.) Bill From owner-freebsd-current Mon Apr 17 19:42:16 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA11204 for current-outgoing; Mon, 17 Apr 1995 19:42:16 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA11198 for ; Mon, 17 Apr 1995 19:42:14 -0700 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id TAA00934; Mon, 17 Apr 1995 19:40:58 -0700 From: Poul-Henning Kamp Message-Id: <199504180240.TAA00934@ref.tfs.com> Subject: Re: msdos mounts won't mount under current 950416 To: root@atari.cybernetics.net (Adam W. Hawks) Date: Mon, 17 Apr 1995 19:40:56 -0700 (PDT) Cc: freebsd-current@FreeBSD.org In-Reply-To: <199504180233.WAA00472@atari.cybernetics.net> from "Adam W. Hawks" at Apr 17, 95 10:33:20 pm Content-Type: text Content-Length: 600 Sender: current-owner@FreeBSD.org Precedence: bulk > I just built a new kernel using deltas up to src-cur.0519 and now I can't mount > the dos partitions that have worked up till delta 486 or so. What has changed > or what do I need to change to get my dos partition back? Slices, your dos partition is now called /dev/wd0s[1234] or something appropiate along those lines. Do a fdisk "/dev/rwd0" and add one to the slice number [0-3] to get the /dev/wd0s[1-4] number -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant' From owner-freebsd-current Mon Apr 17 20:24:54 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA12443 for current-outgoing; Mon, 17 Apr 1995 20:24:54 -0700 Received: from cardhu.cs.hut.fi (hsu@cardhu.cs.hut.fi [130.233.192.95]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id UAA12437 for ; Mon, 17 Apr 1995 20:24:50 -0700 Received: by cardhu.cs.hut.fi id AA16519 (5.65c8/HUTCS-C 1.3 for freebsd-current@FreeBSD.org); Tue, 18 Apr 1995 06:23:25 +0300 Date: Tue, 18 Apr 1995 06:23:25 +0300 From: Heikki Suonsivu Message-Id: <199504180323.AA16519@cardhu.cs.hut.fi> To: Joe Greco Cc: joerg_wunsch@uriah.heep.sax.de, gpalmer@freefall.cdrom.com, hsu@cs.hut.fi, freebsd-current@FreeBSD.org Subject: Re: mmap bugs gone yet? In-Reply-To: <9504142236.AA02076@brasil.moneng.mei.com> References: <199504141030.MAA18746@uriah.heep.sax.de> <9504142236.AA02076@brasil.moneng.mei.com> Organization: Helsinki University of Technology, Otaniemi, Finland Sender: current-owner@FreeBSD.org Precedence: bulk Joe Greco writes: > > With the merged VM/buffer cache, i doubt it will buy too much to mmap > > the files at all. > > This was not true on my Sun 3/60. I never investigated to find out why, > however. It would seem to be writing the history file every 10 articles if you use ACT_READ option. I don't know if it writes all of it or just the modified parts. You can tune innd to write less often, but it doesn't seem to help much. We are in big trouble soon if the NNTP protocol isn't quickly revised, and we probably need a fully rewritten news system in less than a year... -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@cs.hut.fi home +358-0-8031121 work -4513377 fax -4555276 riippu SN From owner-freebsd-current Mon Apr 17 21:25:35 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA13608 for current-outgoing; Mon, 17 Apr 1995 21:25:35 -0700 Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.20.4]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id VAA13602 for ; Mon, 17 Apr 1995 21:25:33 -0700 Received: by brasil.moneng.mei.com (4.1/SMI-4.1) id AA05862; Mon, 17 Apr 95 23:23:47 CDT From: Joe Greco Message-Id: <9504180423.AA05862@brasil.moneng.mei.com> Subject: Re: mmap bugs gone yet? To: hsu@cs.hut.fi (Heikki Suonsivu) Date: Mon, 17 Apr 1995 23:23:47 -0500 (CDT) Cc: joerg_wunsch@uriah.heep.sax.de, gpalmer@freefall.cdrom.com, hsu@cs.hut.fi, freebsd-current@FreeBSD.org In-Reply-To: <199504180323.AA16519@cardhu.cs.hut.fi> from "Heikki Suonsivu" at Apr 18, 95 06:23:25 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2288 Sender: current-owner@FreeBSD.org Precedence: bulk > Joe Greco writes: > > > With the merged VM/buffer cache, i doubt it will buy too much to mmap > > > the files at all. > > > > This was not true on my Sun 3/60. I never investigated to find out why, > > however. > > It would seem to be writing the history file every 10 articles if you use > ACT_READ option. I don't know if it writes all of it or just the modified > parts. You can tune innd to write less often, but it doesn't seem to help > much. We are in big trouble soon if the NNTP protocol isn't quickly Does ACT_READ actually affect the history file mechanism? My memory suggests that the history code is always handled with a write, and the only thing that you can affect is the dbzincore()... I could go look at the code, I suppose.... not fun at 1200 baud, though, so I won't. > revised, and we probably need a fully rewritten news system in less than a > year... And here I thought that's what INN was. :-) What NNTP failing in particular are we discussing, anyways? NNTP throughput rates due to turnaround times? Bandwidth requirements to send complete uncompressed text chunks? I am not yet aware of any inherent limits to the technology. Sure, those of us running major backbone sites are using things such as parallel nntplink processes to help circumvent problems inherent when you're trying to push gigabytes of news daily, but I don't see this as a deficiency in the protocol per se. What I _would_ like to see is a new generation of threaded news tools - perhaps (most ideally) rolling the functionality of nntplink into INN, and providing a mechanism that allows INN to open several concurrent NNTP connections to a peer, multiplexed such that it appears to INN as a single feed. Of course, this doesn't buy as much under FreeBSD as it would under Solaris. That's not saying anything bad about FreeBSD, by the way, but I do believe that there is something inherently threadable about news. Providing NNTP extensions to do NNTP command stacking and/or simple batch/compression on the fly (for slow links) would be the next step. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 From owner-freebsd-current Mon Apr 17 22:58:45 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA15953 for current-outgoing; Mon, 17 Apr 1995 22:58:45 -0700 Received: from mail.barrnet.net (mail.BARRNET.NET [131.119.246.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA15947 for ; Mon, 17 Apr 1995 22:58:43 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by mail.barrnet.net (8.6.10/MAIL-RELAY-LEN) with ESMTP id RAA19385 for ; Sun, 16 Apr 1995 17:59:59 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id KAA21944 for current@freebsd.org; Mon, 17 Apr 1995 10:44:51 +1000 Date: Mon, 17 Apr 1995 10:44:51 +1000 From: Bruce Evans Message-Id: <199504170044.KAA21944@godzilla.zeta.org.au> To: current@FreeBSD.org Subject: compiler warnings for building GENERIC kernel Sender: current-owner@FreeBSD.org Precedence: bulk I'd like all warnings from all system makes to be fixed for 2.1. `make depend' in sys/compile/GENERIC current produces the following error output: >mv: .depend: set owner/group: Operation not permitted This is because `mkdep' creates a temporary file in /tmp, and /tmp has group bin so the temporary has group bin, and I'm not in group bin so I can't move the temporary to my GENERIC directory without losing the group. I don't know of a good fix. Inheriting the group from the parent directory seems to be completely wrong for temporary files. `make' in sys/compile/GENERIC currently produces the following error output: >../../i386/isa/if_le.c:805: warning: large integer implicitly truncated to unsigned type >... >../../i386/isa/if_le.c:808: warning: large integer implicitly truncated to unsigned type I will fix this in a few minutes. Bruce From owner-freebsd-current Tue Apr 18 01:08:40 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA21813 for current-outgoing; Tue, 18 Apr 1995 01:08:40 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id BAA21793 for ; Tue, 18 Apr 1995 01:08:26 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id RAA09975; Tue, 18 Apr 1995 17:59:12 +1000 Date: Tue, 18 Apr 1995 17:59:12 +1000 From: Bruce Evans Message-Id: <199504180759.RAA09975@godzilla.zeta.org.au> To: current@FreeBSD.org, faulkner@mpd.tandem.com Subject: Re: stdlib.h:80: parse error before `__dead2' Sender: current-owner@FreeBSD.org Precedence: bulk >I have been seeing these lately. What does it mean? I am compiling >ImageMagick. tk fails the same way. Even after a sup and a build world. >In file included from magick.h:9, > from widget.c:50: >/usr/include/stdlib.h:80: parse error before `__dead2' >/usr/include/stdlib.h:80: warning: data definition has no type or storage class __dead2 is defined in so it can't appear in a compiler error message if the includes are set up correctly. Bruce From owner-freebsd-current Tue Apr 18 01:27:29 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA23844 for current-outgoing; Tue, 18 Apr 1995 01:27:29 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id BAA23757 for ; Tue, 18 Apr 1995 01:26:51 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id SAA11255; Tue, 18 Apr 1995 18:22:22 +1000 Date: Tue, 18 Apr 1995 18:22:22 +1000 From: Bruce Evans Message-Id: <199504180822.SAA11255@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.org, taob@gate.sinica.edu.tw Subject: Re: Behaviour of rm/rmdir Sender: current-owner@FreeBSD.org Precedence: bulk > This is something that has been bothering me for years... dunno >why I suddenly decide to bring it up now. ;-) Why do "rm -r[f]" and >"rmdir" complain about removing an empty directory if you append a >slash to the name? I mean, this looks pretty ridiculous to me: >% du testdir >2371 testdir >% rm -rf testdir/ >rm: testdir/: Is a directory <--- tell me something I don't know... >% rmdir testdir/ >rmdir: testdir/: Is a directory <--- argh!!! > It isn't a big deal to leave off the trailing slash, but filename >completion in tcsh and bash both append it. Is this just a 4.4BSD >thing? I checked around on our IRIX, SunOS, Solaris and AIX machines >and none exhibit this behaviour. BSD/OS 2.0 rm/rmdir behave this way >too. Bug or feature? It is apprently a BSD thing. It was in FreeBSD-1.1.5. I fixed it there, and have updated the changes to FreeBSD-2.1-Development except for one detail that causes an infinite loop for "testdir/" when testdir is a symlink (perhaps to a directory). POSIX requires trailing slashes to work right and the other OS's are probably more POSIXish than FreeBSD. Some versions of `rm' and `rmdir' mask the bug by gratuitously stripping trailing slashes. Bruce From owner-freebsd-current Tue Apr 18 03:04:27 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA28666 for current-outgoing; Tue, 18 Apr 1995 03:04:27 -0700 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id DAA28654 for ; Tue, 18 Apr 1995 03:04:12 -0700 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id MAA18819 ; Tue, 18 Apr 1995 12:04:08 +0200 Received: from (roberto@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) id MAA11893 ; Tue, 18 Apr 1995 12:04:07 +0200 From: roberto@blaise.ibp.fr (Ollivier Robert) Message-Id: <199504181004.MAA11893@blaise.ibp.fr> Subject: Re: mmap bugs gone yet? To: hsu@cs.hut.fi (Heikki Suonsivu) Date: Tue, 18 Apr 1995 12:04:06 +0200 (MET DST) Cc: jgreco@brasil.moneng.mei.com, joerg_wunsch@uriah.heep.sax.de, gpalmer@freefall.cdrom.com, hsu@cs.hut.fi, freebsd-current@FreeBSD.org In-Reply-To: <199504180323.AA16519@cardhu.cs.hut.fi> from "Heikki Suonsivu" at Apr 18, 95 06:23:25 am X-Operating-System: FreeBSD 2.0.950416-SNAP ctm#562 X-Mailer: ELM [version 2.4 PL23beta2] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 659 Sender: current-owner@FreeBSD.org Precedence: bulk > It would seem to be writing the history file every 10 articles if you use > ACT_READ option. I don't know if it writes all of it or just the modified > parts. You can tune innd to write less often, but it doesn't seem to help > much. We are in big trouble soon if the NNTP protocol isn't quickly > revised, and we probably need a fully rewritten news system in less than a > year... Inn seems to work fine now that mmap bugs are fixed. I've recompiled it with ACT_READ at MMAP and I've not crashed since. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@FreeBSD.ORG FreeBSD keltia 2.0.950416-SNAP #17: Sun Apr 16 17:12:07 MET DST 1995 From owner-freebsd-current Tue Apr 18 03:26:18 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA29206 for current-outgoing; Tue, 18 Apr 1995 03:26:18 -0700 Received: from silver.sms.fi (silver.sms.fi [193.64.137.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id DAA29191 for ; Tue, 18 Apr 1995 03:26:12 -0700 Received: (from pete@localhost) by silver.sms.fi (8.6.11/8.6.9) id NAA15219; Tue, 18 Apr 1995 13:24:30 +0300 Date: Tue, 18 Apr 1995 13:24:30 +0300 Message-Id: <199504181024.NAA15219@silver.sms.fi> From: Petri Helenius To: Joe Greco Cc: freebsd-current@FreeBSD.org Subject: Re: mmap bugs gone yet? In-Reply-To: <9504180423.AA05862@brasil.moneng.mei.com> References: <199504180323.AA16519@cardhu.cs.hut.fi> <9504180423.AA05862@brasil.moneng.mei.com> Sender: current-owner@FreeBSD.org Precedence: bulk Joe Greco writes: > > And here I thought that's what INN was. :-) > Me too. And from my experience working at ISP suggests the same. But INN's shortcomings are becoming more visible each day. And INN is the most popular news-software today. > What NNTP failing in particular are we discussing, anyways? NNTP throughput > rates due to turnaround times? Bandwidth requirements to send complete > uncompressed text chunks? I am not yet aware of any inherent limits to the > technology. Sure, those of us running major backbone sites are using things > such as parallel nntplink processes to help circumvent problems inherent > when you're trying to push gigabytes of news daily, but I don't see this as > a deficiency in the protocol per se. > Neither do I. The news community definetly does _not_ need another protocol to replace NNTP. It would create a administrative nightmare. > What I _would_ like to see is a new generation of threaded news tools - > perhaps (most ideally) rolling the functionality of nntplink into INN, and > providing a mechanism that allows INN to open several concurrent NNTP > connections to a peer, multiplexed such that it appears to INN as a single > feed. > I've thought about that but since an ISP does not pay my salary any longer I've not done anything about it (and most likely will not get involved to actual implementations) but I think I might be of help on my experience of running. (though there is plenty of us who have been knee-deep in the usenet-stuff, unfortunately ;) > Of course, this doesn't buy as much under FreeBSD as it would under Solaris. > That's not saying anything bad about FreeBSD, by the way, but I do believe > that there is something inherently threadable about news. > I can agree you fully. > Providing NNTP extensions to do NNTP command stacking and/or simple > batch/compression on the fly (for slow links) would be the next step. Usually you most definetly don't have the CPU cycles to spare for a compressed feed, so I would leave compression to the lower layers of networking. Most of the routers do low-speed link compression nowadays and it's becoming more popular when people upgrade their boxes to more recent software. Also they usually manage to even lessen the latency with the compression. (when it's done by the routers, not external boxes) Pete From owner-freebsd-current Tue Apr 18 03:41:39 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA29581 for current-outgoing; Tue, 18 Apr 1995 03:41:39 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id DAA29575 for ; Tue, 18 Apr 1995 03:41:37 -0700 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id DAA26058; Tue, 18 Apr 1995 03:41:34 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id DAA00176; Tue, 18 Apr 1995 03:41:34 -0700 Message-Id: <199504181041.DAA00176@corbin.Root.COM> To: roberto@blaise.ibp.fr (Ollivier Robert) cc: freebsd-current@FreeBSD.org Subject: Re: mmap bugs gone yet? In-reply-to: Your message of "Tue, 18 Apr 95 12:04:06 +0200." <199504181004.MAA11893@blaise.ibp.fr> From: David Greenman Reply-To: davidg@Root.COM Date: Tue, 18 Apr 1995 03:41:32 -0700 Sender: current-owner@FreeBSD.org Precedence: bulk >> It would seem to be writing the history file every 10 articles if you use >> ACT_READ option. I don't know if it writes all of it or just the modified >> parts. You can tune innd to write less often, but it doesn't seem to help >> much. We are in big trouble soon if the NNTP protocol isn't quickly >> revised, and we probably need a fully rewritten news system in less than a >> year... > >Inn seems to work fine now that mmap bugs are fixed. I've recompiled it >with ACT_READ at MMAP and I've not crashed since. Good to hear; thanks for the report. -DG From owner-freebsd-current Tue Apr 18 05:36:09 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA02236 for current-outgoing; Tue, 18 Apr 1995 05:36:09 -0700 Received: from sovcom.kiae.su (sovcom.kiae.su [144.206.136.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id FAA02215 for ; Tue, 18 Apr 1995 05:34:47 -0700 Received: by sovcom.kiae.su id AA24077 (5.65.kiae-2 ); Tue, 18 Apr 1995 16:24:45 +0400 Received: by sovcom.KIAE.su (UUMAIL/2.0); Tue, 18 Apr 95 16:24:44 +0300 Received: (from ache@localhost) by astral.msk.su (8.6.8/8.6.6) id PAA01744; Tue, 18 Apr 1995 15:32:10 +0400 To: Heikki Suonsivu , Ollivier Robert Cc: freebsd-current@FreeBSD.org, gpalmer@freefall.cdrom.com, jgreco@brasil.moneng.mei.com, joerg_wunsch@uriah.heep.sax.de References: <199504181004.MAA11893@blaise.ibp.fr> In-Reply-To: <199504181004.MAA11893@blaise.ibp.fr>; from Ollivier Robert at Tue, 18 Apr 1995 12:04:06 +0200 (MET DST) Message-Id: Organization: Olahm Ha-Yetzirah Date: Tue, 18 Apr 1995 15:32:09 +0400 X-Mailer: Mail/@ [v2.32 FreeBSD] From: "Andrey A. Chernov, Black Mage" X-Class: Fast Subject: Re: mmap bugs gone yet? Lines: 20 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 922 Sender: current-owner@FreeBSD.org Precedence: bulk In message <199504181004.MAA11893@blaise.ibp.fr> Ollivier Robert writes: >> It would seem to be writing the history file every 10 articles if you use >> ACT_READ option. I don't know if it writes all of it or just the modified >> parts. You can tune innd to write less often, but it doesn't seem to help >> much. We are in big trouble soon if the NNTP protocol isn't quickly >> revised, and we probably need a fully rewritten news system in less than a >> year... >Inn seems to work fine now that mmap bugs are fixed. I've recompiled it >with ACT_READ at MMAP and I've not crashed since. Can you upgrade INN port too? -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - FidoNet: 2:5020/230.3 : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-current Tue Apr 18 05:56:00 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA02780 for current-outgoing; Tue, 18 Apr 1995 05:56:00 -0700 Received: (from jkh@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA02773 for current; Tue, 18 Apr 1995 05:55:59 -0700 Date: Tue, 18 Apr 1995 05:55:59 -0700 From: "Jordan K. Hubbard" Message-Id: <199504181255.FAA02773@freefall.cdrom.com> To: current Subject: Using current ports.. Sender: current-owner@FreeBSD.org Precedence: bulk If you're going to start using any of the ports in ftp://freebsd.org/pub/FreeBSD/packages, let me just first warn you: Update your pkg_install tools. If you're running pre 0412-SNAP level pkg_install binaries, you won't get the dependency handling in pkg_add and your life will generally suck.. :-) Jordan From owner-freebsd-current Tue Apr 18 06:41:33 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA06696 for current-outgoing; Tue, 18 Apr 1995 06:41:33 -0700 Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id GAA06638 for ; Tue, 18 Apr 1995 06:41:25 -0700 Received: (from dfr@localhost) by minnow.render.com (8.6.9/8.6.9) id OAA06323; Tue, 18 Apr 1995 14:19:39 +0100 Date: Tue, 18 Apr 1995 14:19:38 +0100 (BST) From: Doug Rabson To: current@FreeBSD.org Subject: DAT tape problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk I just attempted to read back a dump from a DAT tape to test our backup strategy and disturbingly, the file which read back from the tape was corrupted. The directory was intact but when the dump was extracted, there was a checksum error on one file and when comparing the extracted tree with the original, at least one file had been corrupted. My DAT drive probes as a 'WangDAT Model 3400DX' and it is set to use compression. Does anyone have an idea what is happening? -- Doug Rabson, RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 251 4411 FAX: +44 171 251 0939 From owner-freebsd-current Tue Apr 18 08:22:22 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA09568 for current-outgoing; Tue, 18 Apr 1995 08:22:22 -0700 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA09562 for ; Tue, 18 Apr 1995 08:22:06 -0700 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id RAA22975 ; Tue, 18 Apr 1995 17:15:09 +0200 Received: from (roberto@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) id RAA13711 ; Tue, 18 Apr 1995 17:15:08 +0200 From: roberto@blaise.ibp.fr (Ollivier Robert) Message-Id: <199504181515.RAA13711@blaise.ibp.fr> Subject: Re: mmap bugs gone yet? To: ache@astral.msk.su (Andrey A. Chernov, Black Mage) Date: Tue, 18 Apr 1995 17:15:08 +0200 (MET DST) Cc: hsu@cs.hut.fi, freebsd-current@FreeBSD.org, gpalmer@freefall.cdrom.com, jgreco@brasil.moneng.mei.com, joerg_wunsch@uriah.heep.sax.de In-Reply-To: from "Andrey A. Chernov, Black Mage" at Apr 18, 95 03:32:09 pm X-Operating-System: FreeBSD 2.0.950416-SNAP ctm#562 X-Mailer: ELM [version 2.4 PL23beta2] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 261 Sender: current-owner@FreeBSD.org Precedence: bulk > Can you upgrade INN port too? Done with a big warning in the commit message for pre-4/15/95 -current systems. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@FreeBSD.ORG FreeBSD keltia 2.0.950416-SNAP #17: Sun Apr 16 17:12:07 MET DST 1995 From owner-freebsd-current Tue Apr 18 08:25:48 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA09657 for current-outgoing; Tue, 18 Apr 1995 08:25:48 -0700 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA09651 for ; Tue, 18 Apr 1995 08:25:46 -0700 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id LAA00977; Tue, 18 Apr 1995 11:24:53 -0400 From: Peter Dufault Message-Id: <199504181524.LAA00977@hda.com> Subject: Re: DAT tape problems To: dfr@render.com (Doug Rabson) Date: Tue, 18 Apr 1995 11:24:53 -0400 (EDT) Cc: current@FreeBSD.org In-Reply-To: from "Doug Rabson" at Apr 18, 95 02:19:38 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1011 Sender: current-owner@FreeBSD.org Precedence: bulk Doug Rabson writes: > > I just attempted to read back a dump from a DAT tape to test our backup > strategy and disturbingly, the file which read back from the tape was > corrupted. The directory was intact but when the dump was extracted, > there was a checksum error on one file and when comparing the extracted > tree with the original, at least one file had been corrupted. > > My DAT drive probes as a 'WangDAT Model 3400DX' and it is set to use > compression. Does anyone have an idea what is happening? There seems to be a big problem with DAT support. We should put a WARNING someplace, maybe even at boot up in the driver, until it is fixed. This is about the third DAT bug report in a few weeks. I just did a full dump/restore of two big partitions with an Exabyte 8200 on -current, so it isn't a general tape problem. -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-current Tue Apr 18 08:27:43 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA09724 for current-outgoing; Tue, 18 Apr 1995 08:27:43 -0700 Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.20.4]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id IAA09718 for ; Tue, 18 Apr 1995 08:27:42 -0700 Received: by brasil.moneng.mei.com (4.1/SMI-4.1) id AA06665; Tue, 18 Apr 95 10:25:46 CDT From: Joe Greco Message-Id: <9504181525.AA06665@brasil.moneng.mei.com> Subject: Re: mmap bugs gone yet? To: davidg@Root.COM Date: Tue, 18 Apr 1995 10:25:45 -0500 (CDT) Cc: roberto@blaise.ibp.fr, freebsd-current@FreeBSD.org In-Reply-To: <199504181041.DAA00176@corbin.Root.COM> from "David Greenman" at Apr 18, 95 03:41:32 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1145 Sender: current-owner@FreeBSD.org Precedence: bulk > >> It would seem to be writing the history file every 10 articles if you use > >> ACT_READ option. I don't know if it writes all of it or just the modified > >> parts. You can tune innd to write less often, but it doesn't seem to help > >> much. We are in big trouble soon if the NNTP protocol isn't quickly > >> revised, and we probably need a fully rewritten news system in less than a > >> year... > > > >Inn seems to work fine now that mmap bugs are fixed. I've recompiled it > >with ACT_READ at MMAP and I've not crashed since. > > Good to hear; thanks for the report. I'd been running it this way almost continuously since December and hadn't noticed any problems. The system had a tendency to crash on an at-least-weekly basis early on, but as time has passed, it has become more and more stable (beats the heck outta me!). I don't remember a crash within the last month. Ah, wonderful operating system! :-) :-) ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 From owner-freebsd-current Tue Apr 18 08:33:31 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA09828 for current-outgoing; Tue, 18 Apr 1995 08:33:31 -0700 Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.20.4]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id IAA09822 for ; Tue, 18 Apr 1995 08:33:29 -0700 Received: by brasil.moneng.mei.com (4.1/SMI-4.1) id AA06693; Tue, 18 Apr 95 10:32:15 CDT From: Joe Greco Message-Id: <9504181532.AA06693@brasil.moneng.mei.com> Subject: Re: mmap bugs gone yet? To: pete@silver.sms.fi (Petri Helenius) Date: Tue, 18 Apr 1995 10:32:14 -0500 (CDT) Cc: freebsd-current@FreeBSD.org In-Reply-To: <199504181024.NAA15219@silver.sms.fi> from "Petri Helenius" at Apr 18, 95 01:24:30 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1889 Sender: current-owner@FreeBSD.org Precedence: bulk > Joe Greco writes: > > And here I thought that's what INN was. :-) > > Me too. And from my experience working at ISP suggests the same. But INN's > shortcomings are becoming more visible each day. And INN is the most popular > news-software today. Hi Pete, What precisely ARE these shortcomings that you see? I'm sorta curious. :-) INN is a 1000% improvement over C-news for complex environments, and while I would definitely consider INN to be a work in progress, the fundamental design philosophy seems to work. > ...... > > Of course, this doesn't buy as much under FreeBSD as it would under Solaris. > > That's not saying anything bad about FreeBSD, by the way, but I do believe > > that there is something inherently threadable about news. > > I can agree you fully. (now we just have to devise the tools... sigh!) > > Providing NNTP extensions to do NNTP command stacking and/or simple > > batch/compression on the fly (for slow links) would be the next step. > > Usually you most definetly don't have the CPU cycles to spare for a compressed > feed, so I would leave compression to the lower layers of networking. Most > of the routers do low-speed link compression nowadays and it's becoming > more popular when people upgrade their boxes to more recent software. Also > they usually manage to even lessen the latency with the compression. > (when it's done by the routers, not external boxes) I guess that depends on the system, and the number of feeds, etc... It is my (current) general policy to try to scale news servers such that there are plenty of free cycles - and since many feeds are UUCP, they're already being compressed by the CPU. :-) ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 From owner-freebsd-current Tue Apr 18 09:07:49 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA10319 for current-outgoing; Tue, 18 Apr 1995 09:07:49 -0700 Received: from ns1.win.net (ns1.win.net [204.215.209.3]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA10313 for ; Tue, 18 Apr 1995 09:07:46 -0700 Received: (from bugs@localhost) by ns1.win.net (8.6.11/8.6.9) id MAA15803 for current@freebsd.org; Tue, 18 Apr 1995 12:09:49 -0400 From: Mark Hittinger Message-Id: <199504181609.MAA15803@ns1.win.net> Subject: re: DAT tape problems To: current@FreeBSD.org Date: Tue, 18 Apr 1995 12:09:48 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 949 Sender: current-owner@FreeBSD.org Precedence: bulk > From: Doug Rabson > > I just attempted to read back a dump from a DAT tape to test our backup > strategy and disturbingly, the file which read back from the tape was > corrupted. The directory was intact but when the dump was extracted, > there was a checksum error on one file and when comparing the extracted > tree with the original, at least one file had been corrupted. > My DAT drive probes as a 'WangDAT Model 3400DX' and it is set to use > compression. Does anyone have an idea what is happening? I am using one here with success and have not seen this problem. I have been using it since the first snap (not on 2.0R). I am running 3/22 snap now, not -current. I have noticed a problem with the last file on the tape. Could this be what you are seeing? I have placed a dummy file as the last file to be backed up to get around this issue. My controller is a BT946C. Regards, Mark Hittinger bugs@win.net From owner-freebsd-current Tue Apr 18 10:10:55 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA12100 for current-outgoing; Tue, 18 Apr 1995 10:10:55 -0700 Received: from FileServ1.MI.Uni-Koeln.DE (FileServ1.MI.Uni-Koeln.DE [134.95.212.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id KAA12091 for ; Tue, 18 Apr 1995 10:10:51 -0700 Received: by FileServ1.MI.Uni-Koeln.DE id AA17946 (5.67b/IDA-1.5 for current@freebsd.org); Tue, 18 Apr 1995 19:10:29 +0200 Message-Id: <199504181710.AA17946@FileServ1.MI.Uni-Koeln.DE> From: se@MI.Uni-Koeln.DE (Stefan Esser) Date: Tue, 18 Apr 1995 19:10:29 +0200 In-Reply-To: Doug Rabson "DAT tape problems" (Apr 18, 14:19) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Doug Rabson Subject: Re: DAT tape problems Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk On Apr 18, 14:19, Doug Rabson wrote: } Subject: DAT tape problems } I just attempted to read back a dump from a DAT tape to test our backup } strategy and disturbingly, the file which read back from the tape was } corrupted. The directory was intact but when the dump was extracted, } there was a checksum error on one file and when comparing the extracted } tree with the original, at least one file had been corrupted. } } My DAT drive probes as a 'WangDAT Model 3400DX' and it is set to use } compression. Does anyone have an idea what is happening? DAT drives are supposed to work ! I'm using a HP 1533 DDS-2 drive with good success. What controller are you using ? There is special code in the NCR driver, that deals with certain DAT drives, which don't accept SCSI messages within an GETCC command. In case you are using this controller, your particular drive ID might need to be entered in some table in the driver. Most other controllers ought to deal with this in the controller firmware. Regards, STefan -- Stefan Esser Internet: Zentrum fuer Paralleles Rechnen Tel: +49 221 4706019 Universitaet zu Koeln FAX: +49 221 4705160 Weyertal 80 50931 Koeln From owner-freebsd-current Tue Apr 18 11:11:09 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA13403 for current-outgoing; Tue, 18 Apr 1995 11:11:09 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id LAA13383 for ; Tue, 18 Apr 1995 11:10:12 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA23485; Tue, 18 Apr 1995 20:09:33 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA01771; Tue, 18 Apr 1995 20:09:30 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id UAA04362; Tue, 18 Apr 1995 20:06:19 +0200 From: J Wunsch Message-Id: <199504181806.UAA04362@uriah.heep.sax.de> Subject: Re: fsck trashes / if no /lost+found? To: fenner@parc.xerox.com (Bill Fenner) Date: Tue, 18 Apr 1995 20:06:19 +0200 (MET DST) Cc: freebsd-current@FreeBSD.org In-Reply-To: <95Apr17.194031pdt.49864@crevenia.parc.xerox.com> from "Bill Fenner" at Apr 17, 95 07:40:28 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 705 Sender: current-owner@FreeBSD.org Precedence: bulk As Bill Fenner wrote: > > I am running SNAP-950322. I crashed hard, and on the way up, fsck tried to > reconnect a file when fsck'ing /usr. Apparently, for some reason there was > no /usr/lost+found, and fsck printed an error something like "no room in /" > when it said it was trying to create it. The fsck failed, and when I fsck'd > manually it said there was no /, and it ended up reconnecting all the > directories in /lost+found (after creating /lost+found). Terry tells about this every second day. :-) Time to add the appropriate part to newfs(8)? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Tue Apr 18 11:11:48 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA13444 for current-outgoing; Tue, 18 Apr 1995 11:11:48 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id LAA13391 for ; Tue, 18 Apr 1995 11:10:31 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA23488; Tue, 18 Apr 1995 20:09:34 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA01774 for freebsd-current@FreeBSD.org; Tue, 18 Apr 1995 20:09:33 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id UAA04376 for freebsd-current@FreeBSD.org; Tue, 18 Apr 1995 20:07:54 +0200 From: J Wunsch Message-Id: <199504181807.UAA04376@uriah.heep.sax.de> Subject: Re: Behaviour of rm/rmdir To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Tue, 18 Apr 1995 20:07:53 +0200 (MET DST) Reply-To: freebsd-current@FreeBSD.org (FreeBSD-current users) In-Reply-To: from "Brian Tao" at Apr 18, 95 01:32:56 am Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 550 Sender: current-owner@FreeBSD.org Precedence: bulk As Brian Tao wrote: > > % rm -rf testdir/ > rm: testdir/: Is a directory <--- tell me something I don't know... > % rmdir testdir/ > rmdir: testdir/: Is a directory <--- argh!!! This has been discussed to death before ``your time'', Brian. Unfortunately, there didn't seem to be a good way to solve all the related problems inside `namei', so the consensus happened to be ``leave it as it is now''. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Tue Apr 18 11:25:13 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA14034 for current-outgoing; Tue, 18 Apr 1995 11:25:13 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA14023 for ; Tue, 18 Apr 1995 11:25:10 -0700 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id LAA26856; Tue, 18 Apr 1995 11:24:56 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id LAA01700; Tue, 18 Apr 1995 11:24:56 -0700 Message-Id: <199504181824.LAA01700@corbin.Root.COM> To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: fenner@parc.xerox.com (Bill Fenner), freebsd-current@FreeBSD.org Subject: Re: fsck trashes / if no /lost+found? In-reply-to: Your message of "Tue, 18 Apr 95 20:06:19 +0200." <199504181806.UAA04362@uriah.heep.sax.de> From: David Greenman Reply-To: davidg@Root.COM Date: Tue, 18 Apr 1995 11:24:44 -0700 Sender: current-owner@FreeBSD.org Precedence: bulk >As Bill Fenner wrote: >> >> I am running SNAP-950322. I crashed hard, and on the way up, fsck tried to >> reconnect a file when fsck'ing /usr. Apparently, for some reason there was >> no /usr/lost+found, and fsck printed an error something like "no room in /" >> when it said it was trying to create it. The fsck failed, and when I fsck'd >> manually it said there was no /, and it ended up reconnecting all the >> directories in /lost+found (after creating /lost+found). > >Terry tells about this every second day. :-) > >Time to add the appropriate part to newfs(8)? I asked Kirk about this and he said "no". I might still have the email around somewhere. -DG From owner-freebsd-current Tue Apr 18 11:56:34 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA14717 for current-outgoing; Tue, 18 Apr 1995 11:56:34 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id LAA14711 for ; Tue, 18 Apr 1995 11:56:32 -0700 Received: by halloran-eldar.lcs.mit.edu; id AA00720; Tue, 18 Apr 1995 14:56:16 -0400 Date: Tue, 18 Apr 1995 14:56:16 -0400 From: Garrett Wollman Message-Id: <9504181856.AA00720@halloran-eldar.lcs.mit.edu> To: Stephen Hocking Cc: "Justin T. Gibbs" , current@FreeBSD.org Subject: Re: Fixed seagate.c (incl. recent devconf changes) In-Reply-To: <199504170515.FAA08801@netfl15a.devetir.qld.gov.au> References: <199504150208.TAA00515@estienne.cs.berkeley.edu> <199504170515.FAA08801@netfl15a.devetir.qld.gov.au> Sender: current-owner@FreeBSD.org Precedence: bulk < quoted Justin Gibbs as saying: >> Your changes are based on a very old version of the driver. This makes >> it difficult for us to see what you changed and what was changed in other >> revisions of the driver. Can you make your changes relative to version 1.7 >> (today's current) and resubmit them as context diffs (diff -c)? Actually, this is fairly trivial to handle: cvs co modulename cd path/to/source cvs update -rBASE-REVISION-OF-NEW-FILE file.names # now splat new file cvs update -A file.names # now deal with the conflicts, if any -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Tue Apr 18 12:09:04 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA14975 for current-outgoing; Tue, 18 Apr 1995 12:09:04 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA14961 for ; Tue, 18 Apr 1995 12:08:53 -0700 Received: by halloran-eldar.lcs.mit.edu; id AA00747; Tue, 18 Apr 1995 15:08:34 -0400 Date: Tue, 18 Apr 1995 15:08:34 -0400 From: Garrett Wollman Message-Id: <9504181908.AA00747@halloran-eldar.lcs.mit.edu> To: "Rodney W. Grimes" Cc: current@FreeBSD.org Subject: Memory fill patterns In-Reply-To: <199504152313.QAA05625@gndrsh.aac.dev.com> References: <636.797979286@freefall.cdrom.com> <199504152313.QAA05625@gndrsh.aac.dev.com> Sender: current-owner@FreeBSD.org Precedence: bulk < said: > We have lots of choices, a grep of /usr/share/dict/words turns > up 64 words that are 8 characters long using the letters [a-filo]. You > use 1 for i and l and 0 for o: [list deleted] Unfortunately, Rod missed the point, or rather, he saw one of them and missed the rest. Here is the rationale for the choice of 0xdeadbeef (or 0xdeadbee1): 1) When printed in decimal, it's obnoxiously large and negative. 2) When printed in hex, It's recognizable. 3) When printed as a float, it's either invalid or at least obnoxiously large. 4) When used as an address, it's unlikely to be mapped. 5) When used as an address, it will cause an unaligned-access trap. This is from memory after someone posted in alt.folklore.computers three or four years ago about the origin of 0xdeadbee1. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Tue Apr 18 12:10:10 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA15010 for current-outgoing; Tue, 18 Apr 1995 12:10:10 -0700 Received: from estienne.cs.berkeley.edu (estienne.CS.Berkeley.EDU [128.32.42.147]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA15004 for ; Tue, 18 Apr 1995 12:10:09 -0700 Received: from localhost (localhost [127.0.0.1]) by estienne.cs.berkeley.edu (8.6.11/8.6.9) with SMTP id MAA18532; Tue, 18 Apr 1995 12:09:52 -0700 Message-Id: <199504181909.MAA18532@estienne.cs.berkeley.edu> X-Authentication-Warning: estienne.cs.berkeley.edu: Host localhost didn't use HELO protocol To: Garrett Wollman cc: Stephen Hocking , current@FreeBSD.org Subject: Re: Fixed seagate.c (incl. recent devconf changes) In-reply-to: Your message of "Tue, 18 Apr 1995 14:56:16 EDT." <9504181856.AA00720@halloran-eldar.lcs.mit.edu> Date: Tue, 18 Apr 1995 12:09:52 -0700 From: "Justin T. Gibbs" Sender: current-owner@FreeBSD.org Precedence: bulk >< quoted Justin Gibbs as saying: > >>> Your changes are based on a very old version of the driver. This makes >>> it difficult for us to see what you changed and what was changed in other >>> revisions of the driver. Can you make your changes relative to version 1.7 >>> (today's current) and resubmit them as context diffs (diff -c)? > >Actually, this is fairly trivial to handle: > >cvs co modulename >cd path/to/source >cvs update -rBASE-REVISION-OF-NEW-FILE file.names ># now splat new file >cvs update -A file.names ># now deal with the conflicts, if any Yes, but I don't have one of these controllers, so it would be best for him to look at current first, resolve the conflicts himself, test them on the hardware, and resubmit them. > >-GAWollman > >-- >Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... >wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. >Opinions not those of| It is a bond more powerful than absence. We like peopl >e >MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant -- Justin T. Gibbs ============================================== TCS Instructional Group - Programmer/Analyst 1 Cory | Po | Danube | Volga | Parker | Torus ============================================== From owner-freebsd-current Tue Apr 18 12:30:39 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA15362 for current-outgoing; Tue, 18 Apr 1995 12:30:39 -0700 Received: from mail.barrnet.net (mail.BARRNET.NET [131.119.246.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA15356 for ; Tue, 18 Apr 1995 12:30:37 -0700 Received: from silver.sms.fi (silver.sms.fi [193.64.137.1]) by mail.barrnet.net (8.6.10/MAIL-RELAY-LEN) with ESMTP id MAA09201 for ; Tue, 18 Apr 1995 12:27:58 -0700 Received: (from pete@localhost) by silver.sms.fi (8.6.11/8.6.9) id WAA00592; Tue, 18 Apr 1995 22:27:59 +0300 Date: Tue, 18 Apr 1995 22:27:59 +0300 Message-Id: <199504181927.WAA00592@silver.sms.fi> From: Petri Helenius To: Joe Greco Cc: freebsd-current@FreeBSD.org Subject: Re: mmap bugs gone yet? In-Reply-To: <9504181532.AA06693@brasil.moneng.mei.com> References: <199504181024.NAA15219@silver.sms.fi> <9504181532.AA06693@brasil.moneng.mei.com> Sender: current-owner@FreeBSD.org Precedence: bulk Joe Greco writes: > > Hi Pete, > > What precisely ARE these shortcomings that you see? I'm sorta curious. :-) > INN is a 1000% improvement over C-news for complex environments, and while I > would definitely consider INN to be a work in progress, the fundamental > design philosophy seems to work. > I can agree that INN is _huge_ improvement over C-news but it still does not solve the problem that most likely an article comes in, gets stored to the disk and then when we're running a hub it's read from the disk about 20 times if the fanout is 50 feeds. (the rest comes from the buffer) If INN would be able to integrate nntplink functionality and be multithreading, this could be (in normal circumstances) be reduced to around 5 times. Inn also goes to non-responsive mode when it processes a newgroup or a rmgroup and does not accept new connections during the processing of those. This is a quite hard issue to resolve but annoys quite a lot on a busy server. > (now we just have to devise the tools... sigh!) > ;-) > I guess that depends on the system, and the number of feeds, etc... It is > my (current) general policy to try to scale news servers such that there are > plenty of free cycles - and since many feeds are UUCP, they're already > being compressed by the CPU. :-) > That's not true around here. Very few of the feeds are UUCP and most likely the UUCP feeds are quite to very small. The article load is so huge that you don't want to spend the money on transmitting them over dialups. (because around here you pay for local calls) Pete From owner-freebsd-current Tue Apr 18 12:40:56 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA15573 for current-outgoing; Tue, 18 Apr 1995 12:40:56 -0700 Received: from estienne.cs.berkeley.edu (estienne.CS.Berkeley.EDU [128.32.42.147]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA15567 for ; Tue, 18 Apr 1995 12:40:55 -0700 Received: from localhost (localhost [127.0.0.1]) by estienne.cs.berkeley.edu (8.6.11/8.6.9) with SMTP id MAA18635; Tue, 18 Apr 1995 12:39:08 -0700 Message-Id: <199504181939.MAA18635@estienne.cs.berkeley.edu> X-Authentication-Warning: estienne.cs.berkeley.edu: Host localhost didn't use HELO protocol To: se@MI.Uni-Koeln.DE (Stefan Esser) cc: Doug Rabson , current@FreeBSD.org Subject: Re: DAT tape problems In-reply-to: Your message of "Tue, 18 Apr 1995 19:10:29 +0200." <199504181710.AA17946@FileServ1.MI.Uni-Koeln.DE> Date: Tue, 18 Apr 1995 12:39:08 -0700 From: "Justin T. Gibbs" Sender: current-owner@FreeBSD.org Precedence: bulk >On Apr 18, 14:19, Doug Rabson wrote: >} Subject: DAT tape problems >} I just attempted to read back a dump from a DAT tape to test our backup >} strategy and disturbingly, the file which read back from the tape was >} corrupted. The directory was intact but when the dump was extracted, >} there was a checksum error on one file and when comparing the extracted >} tree with the original, at least one file had been corrupted. >} >} My DAT drive probes as a 'WangDAT Model 3400DX' and it is set to use >} compression. Does anyone have an idea what is happening? > >DAT drives are supposed to work ! > >I'm using a HP 1533 DDS-2 drive with good success. > >What controller are you using ? > >There is special code in the NCR driver, that deals >with certain DAT drives, which don't accept SCSI >messages within an GETCC command. In case you are >using this controller, your particular drive ID >might need to be entered in some table in the driver. > >Most other controllers ought to deal with this in >the controller firmware. > >Regards, STefan >-- > Stefan Esser Internet: > Zentrum fuer Paralleles Rechnen Tel: +49 221 4706019 > Universitaet zu Koeln FAX: +49 221 4705160 > Weyertal 80 > 50931 Koeln Can we better publicize these "known rogue" devices. I hadn't heard of this problem, so if it needs controller firmware mods, I'd like to know about it. Do these problems have to be handled at the controller level? or can they be handled more generically? -- Justin T. Gibbs ============================================== TCS Instructional Group - Programmer/Analyst 1 Cory | Po | Danube | Volga | Parker | Torus ============================================== From owner-freebsd-current Tue Apr 18 13:15:39 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA16821 for current-outgoing; Tue, 18 Apr 1995 13:15:39 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id NAA16812 for ; Tue, 18 Apr 1995 13:15:32 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA14739; Tue, 18 Apr 95 13:58:48 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9504181958.AA14739@cs.weber.edu> Subject: Re: fsck trashes / if no /lost+found? To: davidg@Root.COM Date: Tue, 18 Apr 95 13:58:48 MDT Cc: joerg_wunsch@uriah.heep.sax.de, fenner@parc.xerox.com, freebsd-current@FreeBSD.org In-Reply-To: <199504181824.LAA01700@corbin.Root.COM> from "David Greenman" at Apr 18, 95 11:24:44 am X-Mailer: ELM [version 2.4dev PL52] Sender: current-owner@FreeBSD.org Precedence: bulk [ ... lost+found not created by default ... ] > >Time to add the appropriate part to newfs(8)? > > I asked Kirk about this and he said "no". I might still have the email > around somewhere. I still think his arguments are only valid for the log structured FS. There is also the problem of archivers ignoring inode 3 the same way they ignore inode 1 (which used to be the free list). At the *very* least, inode 3 ought to be preallocated or unallocable. I'm sure you probably have my reply lurking around as well in case I brought it up at some future date. 8-). Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Tue Apr 18 14:44:49 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA19989 for current-outgoing; Tue, 18 Apr 1995 14:44:49 -0700 Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.20.4]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id OAA19983 for ; Tue, 18 Apr 1995 14:44:46 -0700 Received: by brasil.moneng.mei.com (4.1/SMI-4.1) id AA07382; Tue, 18 Apr 95 16:43:38 CDT From: Joe Greco Message-Id: <9504182143.AA07382@brasil.moneng.mei.com> Subject: Re: mmap bugs gone yet? To: pete@silver.sms.fi (Petri Helenius) Date: Tue, 18 Apr 1995 16:43:37 -0500 (CDT) Cc: freebsd-current@FreeBSD.org In-Reply-To: <199504181927.WAA00592@silver.sms.fi> from "Petri Helenius" at Apr 18, 95 10:27:59 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 4202 Sender: current-owner@FreeBSD.org Precedence: bulk Hi Pete, > I can agree that INN is _huge_ improvement over C-news but it still does not > solve the problem that most likely an article comes in, gets stored to the > disk and then when we're running a hub it's read from the disk about 20 > times if the fanout is 50 feeds. (the rest comes from the buffer) If INN would > be able to integrate nntplink functionality and be multithreading, this > could be (in normal circumstances) be reduced to around 5 times. I would take this to mean that you're in a very memory-starved environment? Are you running realtime nntplinks, or batchfile nntplinks? I only deal with realtime links, so the following discussion mostly applies there: I do not think that this would be helped by the integration of nntplink into INN, multithreaded or otherwise. Basically, if a feed is falling behind, it will tend to continue to fall even further behind, to a point where it is no longer reasonable to maintain a cache of articles to be sent in memory. At this point, INN must log to disk the list of articles to be sent. So there are a few scenarios that I can envision, depending on the implementation: INN could remember the entire article in memory, and provide it to the nntplink threads. I do not think that this would be efficient. Consider somebody posting several hundred largish (700K) articles in a row. Consider what the memory requirements would be for any sort of "queued in-RAM" implementation. Consider the consequences of a feed that was even just a few articles behind. Now multiply it times ten feeds. :-( !!!! INN could remember the list of articles in memory, and provide that to the nntplink threads. The nntplink processes would mmap the articles in (or read them in) and send them. This basically relies on their existence within the cache, in order to be efficient. At some point, for a feed that is falling behind, INN would have to flush the list of articles to a batchfile (but by that point, it has probably been long enough that it is no longer likely that the article is in cache anyways). INN could do what it does now, which is essentially identical to the scenario immediately above (from a VM/efficiency viewpoint), although there's a lot more process context switching. The first scenario COULD be done if you assumed everyone has at least 128MB of RAM and not too many feeds. The second and third scenarios work poorly with smaller amounts of memory and work better with much larger amounts of memory. In general, if a feed is not keeping up, you are virtually guaranteed to be forced to reread the article from disk at some point. The only optimization I can think of would be to devise some method that would try to "synchronize" these rereads in some way. I don't see an easy way to do _that_. More memory allows you more caching. Less memory screws you. The ideal news server would have a gigabyte of RAM and be able to cache about a day's worth of news in RAM. :-) I do not see any real way to shift the paradigm to alter this scenario - certainly not if we accept the fact that more than 5 feeds will be severely lagging. > Inn also goes to non-responsive mode when it processes a newgroup or a rmgroup > and does not accept new connections during the processing of those. This is a > quite hard issue to resolve but annoys quite a lot on a busy server. > > > (now we just have to devise the tools... sigh!) > > > ;-) > > > I guess that depends on the system, and the number of feeds, etc... It is > > my (current) general policy to try to scale news servers such that there are > > plenty of free cycles - and since many feeds are UUCP, they're already > > being compressed by the CPU. :-) > > That's not true around here. Very few of the feeds are UUCP and most likely > the UUCP feeds are quite to very small. The article load is so huge that you > don't want to spend the money on transmitting them over dialups. (because > around here you pay for local calls) Ah, well. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 From owner-freebsd-current Tue Apr 18 14:50:41 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA20124 for current-outgoing; Tue, 18 Apr 1995 14:50:41 -0700 Received: from vector.eikon.e-technik.tu-muenchen.de (vector.eikon.e-technik.tu-muenchen.de [129.187.142.36]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA20028 for ; Tue, 18 Apr 1995 14:46:05 -0700 Received: from localhost (localhost [127.0.0.1]) by vector.eikon.e-technik.tu-muenchen.de (8.6.11/8.6.9) with SMTP id WAA00860; Tue, 18 Apr 1995 22:53:18 +0200 Message-Id: <199504182053.WAA00860@vector.eikon.e-technik.tu-muenchen.de> X-Authentication-Warning: vector.eikon.e-technik.tu-muenchen.de: Host localhost didn't use HELO protocol To: davidg@Root.COM cc: uhclem@nemesis.lonestar.org (Frank Durda IV), freebsd-current@FreeBSD.org Subject: Re: Memory init pattern In-reply-to: Your message of "Sat, 15 Apr 1995 19:33:33 +0200." <199504151733.KAA00867@corbin.Root.COM> Date: Tue, 18 Apr 1995 22:53:18 +0200 From: Julian Howard Stacey Sender: current-owner@FreeBSD.org Precedence: bulk Re. > Oops, I meant "TI"...but now that I think about it, I don't know how long > TI has been is business. ...but my point still stands about there being > systems far before '78 that used start-up memory tests, however. Texas Instruments ? rumoured to have invented the venerable 7400 series in 1974 ! Some very big companies like British Telecom, (my ex employer _way_ back) would be very upset not to able to continue running start up self tests without paying royalties, they've probably been doing start up self test since before I was born (some long time ago ;-) BT & other large `mostly-computer-consumer' firms have plenty of lawyers, but are probably not so cosily tucked into the big companies incestuous patent sharing (& screw the little guy) arragements, thus if TI push too hard, they just might disturb some powerful opposition. I don't think we need tremble too much from TI's antisocial behaviour :-) Julian S From owner-freebsd-current Tue Apr 18 14:51:34 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA20158 for current-outgoing; Tue, 18 Apr 1995 14:51:34 -0700 Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id OAA20150 for ; Tue, 18 Apr 1995 14:51:32 -0700 Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <14616(6)>; Tue, 18 Apr 1995 14:50:52 PDT Received: by crevenia.parc.xerox.com id <49864>; Tue, 18 Apr 1995 14:50:41 -0700 From: Bill Fenner To: freebsd-current@FreeBSD.org Subject: kgdb dumps core when kernel-file doesn't exist Message-Id: <95Apr18.145041pdt.49864@crevenia.parc.xerox.com> Date: Tue, 18 Apr 1995 14:50:32 PDT Sender: current-owner@FreeBSD.org Precedence: bulk I'm really used to typing "adb -k /vmunix /dev/mem", so under FreeBSD I have been doing "gdb -k /vmunix /dev/mem" by mistake. (Maybe I should link /vmunix to /kernel =) Anyway, gdb dumps core when I do this (after printing a nice error message). Bill From owner-freebsd-current Tue Apr 18 14:56:26 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA20283 for current-outgoing; Tue, 18 Apr 1995 14:56:26 -0700 Received: from vector.eikon.e-technik.tu-muenchen.de (vector.eikon.e-technik.tu-muenchen.de [129.187.142.36]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA20181 for ; Tue, 18 Apr 1995 14:52:27 -0700 Received: from localhost (localhost [127.0.0.1]) by vector.eikon.e-technik.tu-muenchen.de (8.6.11/8.6.9) with SMTP id VAA00731; Tue, 18 Apr 1995 21:57:07 +0200 Message-Id: <199504181957.VAA00731@vector.eikon.e-technik.tu-muenchen.de> X-Authentication-Warning: vector.eikon.e-technik.tu-muenchen.de: Host localhost didn't use HELO protocol To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-current@FreeBSD.org (FreeBSD-current users) Subject: Re: Info on VM/VFS changes since 4.4Lite In-reply-to: Your message of "Sat, 15 Apr 1995 08:34:10 +0200." <199504150634.IAA01755@uriah.heep.sax.de> Date: Tue, 18 Apr 1995 21:57:06 +0200 From: Julian Howard Stacey Sender: current-owner@FreeBSD.org Precedence: bulk > > I thought that it would be nice to talk about the improvements to the > > FreeBSD VFS/VM since the 4.4-Lite code was given to us. > Nice explanation, i gonna translate it into german and post it into > de.comp.os.unix, if you don't mind. I think this is interesting > enough to hide it in a mailing list. If you go to that effort, perhaps you might send a copy to 1 or 2 German magazines, some even have email addresses I think, ... I'll fax it to them if you dont have a fax, (yes folks, hylafax works on my FreeBSD :-) :-) I suspect a fax will draw more attention than an envelope. Joerg, if you want to take me up on this, also translate the cover sentence I should prepend (my written German is rotten ;-) , & append a note for the magazines in German, with your phone number for queries, then email me the lot. Julian S Munich (=Muenchen) Germany. From owner-freebsd-current Tue Apr 18 15:00:54 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA20375 for current-outgoing; Tue, 18 Apr 1995 15:00:54 -0700 Received: from vector.eikon.e-technik.tu-muenchen.de (vector.eikon.e-technik.tu-muenchen.de [129.187.142.36]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA20314 ; Tue, 18 Apr 1995 14:58:39 -0700 Received: from localhost (localhost [127.0.0.1]) by vector.eikon.e-technik.tu-muenchen.de (8.6.11/8.6.9) with SMTP id CAA19622; Tue, 18 Apr 1995 02:06:00 +0200 Message-Id: <199504180006.CAA19622@vector.eikon.e-technik.tu-muenchen.de> X-Authentication-Warning: vector.eikon.e-technik.tu-muenchen.de: Host localhost didn't use HELO protocol To: "Jordan K. Hubbard" cc: "Mike O'Brien" , freebsd-current@freefall.cdrom.com Subject: Re: ASUS www mirror In-reply-to: Your message of "Wed, 12 Apr 1995 11:52:59 +0200." <6665.797680379@freefall.cdrom.com> Date: Tue, 18 Apr 1995 02:05:59 +0200 From: Julian Howard Stacey Sender: current-owner@FreeBSD.org Precedence: bulk > PacBell .... business ISDN" ...unmetered 24-hour connections $69/month, Huh ! Green with envy ! I bet Deutsche Telekom cant come near that (not that I've asked, I just assume, I'd be delighted to be contradicted ! Julian S. Munich From owner-freebsd-current Tue Apr 18 16:09:58 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA26875 for current-outgoing; Tue, 18 Apr 1995 16:09:58 -0700 Received: from tcsi.tcs.com (tcsi.tcs.com [137.134.41.11]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA26869 for ; Tue, 18 Apr 1995 16:09:53 -0700 Received: from phact.tcs.com (phact.tcs.com [137.134.41.99]) by tcsi.tcs.com (8.6.10/8.6.10) with ESMTP id QAA00394; Tue, 18 Apr 1995 16:09:20 -0700 Received: from cozumel.tcs.com (cozumel.tcs.com [137.134.104.12]) by phact.tcs.com (8.6.10/8.6.10) with ESMTP id QAA16957; Tue, 18 Apr 1995 16:09:19 -0700 From: Douglas Ambrisko Received: (ambrisko@localhost) by cozumel.tcs.com (8.6.10/8.6.10) id QAA04563; Tue, 18 Apr 1995 16:09:18 -0700 Message-Id: <199504182309.QAA04563@cozumel.tcs.com> Subject: Re: DAT tape problems To: bugs@ns1.win.net (Mark Hittinger) Date: Tue, 18 Apr 1995 16:09:17 -0700 (PDT) Cc: current@FreeBSD.org In-Reply-To: <199504181609.MAA15803@ns1.win.net> from "Mark Hittinger" at Apr 18, 95 12:09:48 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2188 Sender: current-owner@FreeBSD.org Precedence: bulk Mark Hittinger writes: | | > From: Doug Rabson | > | > I just attempted to read back a dump from a DAT tape to test our backup | > strategy and disturbingly, the file which read back from the tape was | > corrupted. The directory was intact but when the dump was extracted, | > there was a checksum error on one file and when comparing the extracted | > tree with the original, at least one file had been corrupted. | > My DAT drive probes as a 'WangDAT Model 3400DX' and it is set to use | > compression. Does anyone have an idea what is happening? | | I am using one here with success and have not seen this problem. I have | been using it since the first snap (not on 2.0R). | | I am running 3/22 snap now, not -current. | | I have noticed a problem with the last file on the tape. Could this be | what you are seeing? I have placed a dummy file as the last file to be | backed up to get around this issue. This dummy file fix is usually and indicator that you are using the tape device wrong. Most tape drivers (if not all?) are fixed block. Therefore when you write to the tape, the archive must be a multiple of this fixed block. "tar" does this almost right, if you use compression (ie tar -z) then it just pipes the output from tar -> gzip -> tape device. To fix this do something like tar cfvz - | dd obs=10240 of= conv=sync I beleive tar should be fixed such that it forks itself so that you get tar->gzip->tar tape handler and then we could do multi-volume backups with tar! But this isn't an issue with me, since I usually do the dd trick to backup to a remote tape device which uses a couple of dd tricks anyways. Also, QIC tapes are usually 512 and I've notice some DAT tapes >512 so maybe some program have 512 hard-wired? Note 10240 is a multiple of 1024 & 512 which cover most blocking methods. Also reading and writing on block boundries makes the tape drive/driver happier. So try the dd thing and then you can isolate the problem a little more and maybe you can use this as a work-around. BTW this stuff happens on a 1542, NCR chip and most other computer systems I've used. Doug A. From owner-freebsd-current Tue Apr 18 16:16:31 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA27005 for current-outgoing; Tue, 18 Apr 1995 16:16:31 -0700 Received: from devnull (devnull.mpd.tandem.com [131.124.4.29]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA26990 for ; Tue, 18 Apr 1995 16:16:24 -0700 Received: from olympus by devnull (8.6.8/8.6.6) id SAA15463; Tue, 18 Apr 1995 18:16:11 -0500 Received: by olympus (4.1/TSS2.1) id AA25676; Tue, 18 Apr 95 18:14:33 CDT From: faulkner@mpd.tandem.com (Boyd Faulkner) Message-Id: <9504182314.AA25676@olympus> Subject: Re: stdlib.h:80: parse error before `__dead2' To: bde@zeta.org.au (Bruce Evans) Date: Tue, 18 Apr 1995 18:14:32 -0500 (CDT) Cc: current@FreeBSD.org, faulkner@devnull.mpd.tandem.com In-Reply-To: <199504180759.RAA09975@godzilla.zeta.org.au> from "Bruce Evans" at Apr 18, 95 05:59:12 pm X-Mailer: ELM [version 2.4 PL17] Content-Type: text Content-Length: 1001 Sender: current-owner@FreeBSD.org Precedence: bulk > > >I have been seeing these lately. What does it mean? I am compiling > >ImageMagick. tk fails the same way. Even after a sup and a build world. > > >In file included from magick.h:9, > > from widget.c:50: > >/usr/include/stdlib.h:80: parse error before `__dead2' > >/usr/include/stdlib.h:80: warning: data definition has no type or storage class > > __dead2 is defined in so it can't appear in a compiler error > message if the includes are set up correctly. > > Bruce > Indeed, this is true. Lites strikes again. The sys include files for Lites and/or Mach4 reside in /usr/local/include/sys. /usr/local/include is forceably included before /usr/include. Move it and viola, joy is intensified. Thanks for the confirmation. Boyd -- _______________________________________________________________________ Boyd Faulkner faulkner@isd.tandem.com _______________________________________________________________________ From owner-freebsd-current Tue Apr 18 16:52:36 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA27784 for current-outgoing; Tue, 18 Apr 1995 16:52:36 -0700 Received: from bunyip.cc.uq.oz.au (bunyip.cc.uq.oz.au [130.102.2.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id QAA27778 for ; Tue, 18 Apr 1995 16:52:34 -0700 Received: from s1.elec.uq.oz.au by bunyip.cc.uq.oz.au with SMTP (PP); Wed, 19 Apr 1995 09:52:18 +1000 Received: by s1.elec.uq.oz.au (4.0/SMI-4.0) id AA11761; Wed, 19 Apr 95 09:52:00 EST From: clary@elec.uq.oz.au (Clary Harridge) Message-Id: <9504182352.AA11761@s1.elec.uq.oz.au> Subject: Why was the NFS mount option wsize removed? To: freebsd-current@FreeBSD.org Date: Wed, 19 Apr 95 9:51:59 EST X-Mailer: ELM [version 2.3 PL1] Sender: current-owner@FreeBSD.org Precedence: bulk Can someone please tell me whether the old mount option for write buffer size /dev/sd0e /usr ufs rw,wsize=1024 1 2 can be achieved in some other manner? Default NFS buffer sizes are too large when using WD 8003 ethernet cards to support DISKLESS clients. mount_nfs has a "-w" switch but how what option in /etc/fstab or /etc/exports will invoke it? -- regards Dept. of Electrical Engineering, Clary Harridge University of Queensland, QLD, Australia, 4072 Phone: +61-7-365-3636 Fax: +61-7-365-4999 INTERNET: clary@elec.uq.oz.au From owner-freebsd-current Tue Apr 18 17:29:13 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA28520 for current-outgoing; Tue, 18 Apr 1995 17:29:13 -0700 Received: from kaiwan.kaiwan.com (4@kaiwan.kaiwan.com [198.178.203.2]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA28514 for ; Tue, 18 Apr 1995 17:29:10 -0700 Received: from exit.com (uucp@localhost) by kaiwan.kaiwan.com (8.6.9/8.6.5) with UUCP id RAA18630; Tue, 18 Apr 1995 17:28:35 -0700 *** KAIWAN Internet Access *** Received: (from frank@localhost) by exit.com (8.6.8/8.6.6) id QAA11703; Tue, 18 Apr 1995 16:35:06 -0700 From: Frank Mayhar Message-Id: <199504182335.QAA11703@exit.com> Subject: Re: Memory fill patterns To: wollman@halloran-eldar.lcs.mit.edu (Garrett Wollman) Date: Tue, 18 Apr 1995 16:35:05 -0700 (PDT) Cc: rgrimes@gndrsh.aac.dev.com, current@FreeBSD.org In-Reply-To: <9504181908.AA00747@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at Apr 18, 95 03:08:34 pm X-Mailer: ELM [version 2.4 PL23beta2] Content-Type: text Content-Length: 550 Sender: current-owner@FreeBSD.org Precedence: bulk > Unfortunately, Rod missed the point, or rather, he saw one of them and > missed the rest. Here is the rationale for the choice of 0xdeadbeef > (or 0xdeadbee1): > > 4) When used as an address, it's unlikely to be mapped. Well, 4) is actually not true, at least for the version of 80x86-based SVR4.2 I hack at work. 0xdeadbeef, or anything in the range 0xd0000000 - 0xdfffffff is very, very often a valid kernel address. I don't know how this maps to FreeBSD (not very well, I suspect), but it's a consideration. -- Frank Mayhar frank@exit.com From owner-freebsd-current Tue Apr 18 17:32:28 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA28571 for current-outgoing; Tue, 18 Apr 1995 17:32:28 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA28562 for ; Tue, 18 Apr 1995 17:32:24 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id RAA00537 for current@freebsd.org; Tue, 18 Apr 1995 17:29:50 -0700 From: "Rodney W. Grimes" Message-Id: <199504190029.RAA00537@gndrsh.aac.dev.com> Subject: Fix for motherboards that don't reboot. To: current@FreeBSD.org Date: Tue, 18 Apr 1995 17:29:49 -0700 (PDT) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1876 Sender: current-owner@FreeBSD.org Precedence: bulk I spent some time talking with a BIOS engineer today about the problem of FreeBSD not rebooting on some motherboards and have come up with the following patch that fixes the problem on the board I have here. Could others who are having this problem please apply this patch and let me know if it fixes your problem too? I am also interested in other boards that don't have this problem if you can see if it ever does the ``Keyboard reset did not work'' thing. If we can't produce that message on any board we have probably fixed this problem once and for all. The BIOS engineer I was working with claims that this should work for all BIOS's include MCA machines. Index: vm_machdep.c =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/vm_machdep.c,v retrieving revision 1.35 diff -c -r1.35 vm_machdep.c *** 1.35 1995/03/19 14:28:41 --- vm_machdep.c 1995/04/18 22:44:31 *************** *** 50,61 **** --- 50,64 ---- #include #include + #include #include #include #include #include + #include + #ifdef BOUNCE_BUFFERS vm_map_t io_map; volatile int kvasfreecnt; *************** *** 803,808 **** --- 806,817 ---- */ void cpu_reset() { + + /* Attempt to do a CPU reset via the keyboard controller */ + outb(IO_KBD + 4, 0xFE); + DELAY(500000); /* wait 0.5 sec to see if that did it */ + printf("Keyboard reset did not work, attempting CPU shutdown\n"); + DELAY(1000000); /* wait 1 sec for printf to complete */ /* force a shutdown by unmapping entire address space ! */ bzero((caddr_t) PTD, NBPG); -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Tue Apr 18 18:10:18 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA29120 for current-outgoing; Tue, 18 Apr 1995 18:10:18 -0700 Received: from ns1.win.net (ns1.win.net [204.215.209.3]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id SAA29114 for ; Tue, 18 Apr 1995 18:10:15 -0700 Received: (from bugs@localhost) by ns1.win.net (8.6.11/8.6.9) id VAA23435 for current@freebsd.org; Tue, 18 Apr 1995 21:12:30 -0400 From: Mark Hittinger Message-Id: <199504190112.VAA23435@ns1.win.net> Subject: Re: DAT tape problems (fwd) To: current@FreeBSD.org Date: Tue, 18 Apr 1995 21:12:30 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 577 Sender: current-owner@FreeBSD.org Precedence: bulk > From: Douglas Ambrisko > > This dummy file fix is usually and indicator that you are using the > tape device wrong. Most tape drivers (if not all?) are fixed block. I agree with this generally but in my case it is due to a problem with the rewind/eject logic of the scsi driver. The scsi transactions for the last write/close/rewind/eject seem to be unstable for my configuration. I have worked around it but I have not had the time to actually locate the problem and correct it. Its waaaaay down on the list. Regards, Mark Hittinger bugs@win.net From owner-freebsd-current Tue Apr 18 18:17:33 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA29269 for current-outgoing; Tue, 18 Apr 1995 18:17:33 -0700 Received: from sbstark.cs.sunysb.edu (sbstark.cs.sunysb.edu [130.245.1.47]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id SAA29259 for ; Tue, 18 Apr 1995 18:17:31 -0700 Received: (from root@localhost) by sbstark.cs.sunysb.edu (8.6.12/8.6.9) with UUCP id VAA00481 for current@freebsd.org; Tue, 18 Apr 1995 21:17:22 -0400 Received: (from gene@localhost) by starkhome.cs.sunysb.edu (8.6.11/8.6.9) id UAA00208; Tue, 18 Apr 1995 20:47:08 -0400 Date: Tue, 18 Apr 1995 20:47:08 -0400 From: Gene Stark Message-Id: <199504190047.UAA00208@starkhome.cs.sunysb.edu> To: current@FreeBSD.org Subject: Resets under -current (April 16) Sender: current-owner@FreeBSD.org Precedence: bulk Tonight I got two resets (no panic or core dump) running an April 16 kernel. They occurred in close time proximity to killing a pppd. I suspect they have to do with the removal of default routes. - Gene Stark From owner-freebsd-current Tue Apr 18 18:21:10 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA29447 for current-outgoing; Tue, 18 Apr 1995 18:21:10 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id SAA29439 for ; Tue, 18 Apr 1995 18:20:59 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id LAA15783; Wed, 19 Apr 1995 11:15:30 +1000 Date: Wed, 19 Apr 1995 11:15:30 +1000 From: Bruce Evans Message-Id: <199504190115.LAA15783@godzilla.zeta.org.au> To: current@FreeBSD.org, rgrimes@gndrsh.aac.dev.com Subject: Re: Fix for motherboards that don't reboot. Sender: current-owner@FreeBSD.org Precedence: bulk >I spent some time talking with a BIOS engineer today about the problem >of FreeBSD not rebooting on some motherboards and have come up with >the following patch that fixes the problem on the board I have here. > void > cpu_reset() { >+ >+ /* Attempt to do a CPU reset via the keyboard controller */ >+ outb(IO_KBD + 4, 0xFE); This is what I implemented for Minix about (sigh) 6 years ago. I found that outputting 0xFC works better. AFAIR 0xFE strobes the CPU reset line and 0xFC additionally strobes GateA20. Both methods worked in protected mode on the machines that I had access to, but in real mode, (with A20 forced to 0) several machines hung, apparently due to a bad fetch of the first instruction after reset. The first instruction was usually invalid and jumped to the BIOS invalid instruction handler, which was braindamaged and looped. Trapping it with a debugger and jumping to the correct reset vector worked. I suspect the reset worked better in protected mode only because the invalid instruction handler was invalid and the system eventually got reset better after a triple fault. Bruce From owner-freebsd-current Tue Apr 18 19:05:20 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA00807 for current-outgoing; Tue, 18 Apr 1995 19:05:20 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA00796 for ; Tue, 18 Apr 1995 19:05:09 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id TAA00702; Tue, 18 Apr 1995 19:00:35 -0700 From: "Rodney W. Grimes" Message-Id: <199504190200.TAA00702@gndrsh.aac.dev.com> Subject: Re: Fix for motherboards that don't reboot. To: bde@zeta.org.au (Bruce Evans) Date: Tue, 18 Apr 1995 19:00:35 -0700 (PDT) Cc: current@FreeBSD.org In-Reply-To: <199504190115.LAA15783@godzilla.zeta.org.au> from "Bruce Evans" at Apr 19, 95 11:15:30 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1493 Sender: current-owner@FreeBSD.org Precedence: bulk > > >I spent some time talking with a BIOS engineer today about the problem > >of FreeBSD not rebooting on some motherboards and have come up with > >the following patch that fixes the problem on the board I have here. > > > void > > cpu_reset() { > >+ > >+ /* Attempt to do a CPU reset via the keyboard controller */ > >+ outb(IO_KBD + 4, 0xFE); > > This is what I implemented for Minix about (sigh) 6 years ago. I found > that outputting 0xFC works better. AFAIR 0xFE strobes the CPU reset > line and 0xFC additionally strobes GateA20. Both methods worked in > protected mode on the machines that I had access to, but in real mode, > (with A20 forced to 0) several machines hung, apparently due to a bad > fetch of the first instruction after reset. The first instruction was > usually invalid and jumped to the BIOS invalid instruction handler, > which was braindamaged and looped. Trapping it with a debugger and > jumping to the correct reset vector worked. I suspect the reset worked > better in protected mode only because the invalid instruction handler > was invalid and the system eventually got reset better after a triple > fault. > Thanks for the input, I will talk to this person again at a meeting I have on Thursday evening. I will bring the issue of GateA20 up with him and see what he says about it. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Tue Apr 18 19:20:27 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA01525 for current-outgoing; Tue, 18 Apr 1995 19:20:27 -0700 Received: from relay2.UU.NET (relay2.UU.NET [192.48.96.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA01515 for ; Tue, 18 Apr 1995 19:20:20 -0700 Received: from ast.com by relay2.UU.NET with SMTP id QQymbp20031; Tue, 18 Apr 1995 22:20:08 -0400 Received: from trsvax.fw.ast.com (fw.ast.com) by ast.com with SMTP id AA21317 (5.67b/IDA-1.5 for uunet!FreeBSD.org!freebsd-current); Tue, 18 Apr 1995 19:24:14 -0700 Received: by trsvax.fw.ast.com (/\=-/\ Smail3.1.18.1 #18.1) id ; Tue, 18 Apr 95 21:18 CDT Received: by nemesis.lonestar.org (Smail3.1.27.1 #18) id m0s1OcG-0004vtC; Tue, 18 Apr 95 20:31 CDT Message-Id: Date: Tue, 18 Apr 95 20:31 CDT To: freebsd-current@FreeBSD.org From: uhclem@nemesis.lonestar.org (Frank Durda IV) Sent: Tue Apr 18 1995, 20:31:39 CDT Subject: No lost+found - offer a substitute? Cc: uhclem@nemesis.lonestar.org Sender: current-owner@FreeBSD.org Precedence: bulk [0][ ... lost+found not created by default ... ] [1]Time to add the appropriate part to newfs(8)? [2]I asked Kirk about this and he said "no". I might still have the [2] email around somewhere. [3]I still think his arguments are only valid for the log structured FS. Ok, how about changing fsck to offer to use /tmp (or some other directory) in place of lost+found if it can't create lost+found? There is a precedence for fsck asking for something other than Y/N input. I remember older systems asking for the name of a device for writing a scratch file. I've had to rename tmp into lost+found with a filesystem zapper more than once to avoid losing something important after a bad crash when lost+found was one of the things that was wiped. Since then, every site I touch gets lost+found and a lost-found directories (just in case). Frank Durda IV |"The Knights who say "LETNi" or uhclem%nemesis@fw.ast.com (Fastest Route)| demand... A SEGMENT REGISTER!!!" ...letni!rwsys!nemesis!uhclem |"A what?" ...decvax!fw.ast.com!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983 From owner-freebsd-current Tue Apr 18 19:29:06 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA01858 for current-outgoing; Tue, 18 Apr 1995 19:29:06 -0700 Received: from halon.sybase.com (halon.sybase.com [192.138.151.33]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id TAA01850 for ; Tue, 18 Apr 1995 19:28:55 -0700 Received: from sybase.com (sybgate.sybase.com) by halon.sybase.com (5.0/SMI-SVR4/SybFW4.0) id AA01856; Tue, 18 Apr 1995 19:33:41 -0700 Received: from red_oak.sybgate.sybase.com by sybase.com (4.1/SMI-4.1/SybH3.4) id AA18425; Tue, 18 Apr 95 19:28:07 PDT Received: by red_oak.sybgate.sybase.com (4.1/SMI-4.1/SybEC3.2) id AA09313; Tue, 18 Apr 95 22:28:05 EDT From: jeffa@sybase.com (Jeff Anuszczyk) Message-Id: <9504190228.AA09313@red_oak.sybgate.sybase.com> Subject: Questions/problems installing 950412 SNAP To: freebsd-current@FreeBSD.org Date: Tue, 18 Apr 95 22:28:05 EDT Cc: jeffa@sybase.com (Jeff Anuszczyk) X-Mailer: ELM [version 2.3 PL0] content-length: 3014 Sender: current-owner@FreeBSD.org Precedence: bulk Hi All, I finally finished downloading the latest SNAP and started to install it. First I made the install disks using dd. Then I booted the floppies and did a "normal" install. About the only things to note are: two SCSI disks (entire disk is used), the primary disk uses all partitions (a,e,f, g,h) for filesystems plus b for swap. I then had a devil of a time booting from the main system disk (recently running 2.0R). I needed to rewrite the boot block a bunch of times before it finally "took". When it failed the system was just booting (the primary booter is loading /kernel). The first 3 of the spining bars printed and then nothing. In any case, I got around this and the system started to boot. At this point the system is probed and promptly crashes with a fatal trap 12. I rebooted and select -c to look at what it was probing. This is were things started to get weird. It turns out that there are four entries marked enabled but has device names of zero/one as follows: Device Port irq drq iomem iosize unit flags enabled fdc0 0x3f0 6 2 0x0 0 0 0x0 Yes . . . aha0 0x330 -1 5 0x0 0 0 0x0 Yes aic0 0x340 11 -1 0x0 0 0 0x0 Yes 0 0x1f88 10 -1 0x0 0 0 0x0 Yes 1 0x350 5 -1 0x0 0 1 0x0 Yes sea0 0x0 5 -1 0xc8000 8192 0 0x0 Yes . . . ze0 0x300 10 -1 0xd8000 0 0 0x0 Yes zp0 0x300 10 -1 0xd8000 0 0 0x0 Yes 0 0xffffffff -1 -1 0x0 0 0 0x0 Yes 0 0xf0 13 -1 0x0 0 0 0x0 Yes I've edited some of the less than important stuff. The problem started immediately after the probe of aic0. The system got the fatal trap 12 and halted. I did a "disable 0" & "disable 1" and the system would now continue to just after the probe of zp0 when it then traped out again. The problem is I can't disable these additional "0" devices since the assumption of the code is a device name is unique. Any suggestions? In case anyone is curious, here is the trap. I suspect you won't need it... but better safe than sorry. This is with all devices enabled: st0(aha0:6:0): Sequential-Access density code 0x8c, drive empty aic0 not found at 0x340 Fatal Trap 12: page fault while in kernel mode fault virtual address = 0x431f4a30 fault code = supervisor read, page not present instruction pointer = 0x8:0xf01c69a4 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 () interrupt mask = net tty bio panic: page fault The system is an AMD DX2/80, 16MB, VLB/ISA Adaptec 1542B, 1GB SCSI-2 (DEC), Archive Python Tape SMC Elite16T This configuration worked fine under 1.1.5.1 & 2.0R. Thanks for any help anyone can offer! - Jeff From owner-freebsd-current Tue Apr 18 19:32:28 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA01993 for current-outgoing; Tue, 18 Apr 1995 19:32:28 -0700 Received: from uustar.starnet.net (root@uustar.starnet.net [128.252.135.2]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id TAA01985 for ; Tue, 18 Apr 1995 19:32:24 -0700 Received: from mumps.pfcs.com by uustar.starnet.net with UUCP id AA10148 (5.67b/IDA-1.5); Tue, 18 Apr 1995 21:17:51 -0500 Received: from localhost by mumps.pfcs.com with SMTP id AA22251 (5.67b/IDA-1.5); Tue, 18 Apr 1995 22:10:25 -0400 To: Peter Dufault Cc: dfr@render.com (Doug Rabson), current@FreeBSD.org Subject: Re: DAT tape problems In-Reply-To: Peter Dufault's (dufault@hda.com) message dated Tue, 18 Apr 1995 11:24:53. <199504181524.LAA00977@hda.com> Date: Tue, 18 Apr 1995 22:10:24 -0300 Message-Id: <22249.798257424@mumps.pfcs.com> From: Harlan Stenn Sender: current-owner@FreeBSD.org Precedence: bulk I've been quiet, but I can read DAT tapes written from an AIX box, and I can write tapes with FreeBSD-SNAP950322 (or whatever) and with -current as of 30 April, but I can't read tapes written by either FreeBSD machine from either machine. I don't know if the written tapes contain valid data; I just know that "dump" didn't complain when writing them. I think I get I/O error when reading them, and it might even hose the machine (I forget - I haven't done it in a while and I don't want to risk an unplanned reboot right now). H From owner-freebsd-current Tue Apr 18 19:43:06 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA02277 for current-outgoing; Tue, 18 Apr 1995 19:43:06 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA02266 for ; Tue, 18 Apr 1995 19:43:04 -0700 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id TAA06341; Tue, 18 Apr 1995 19:39:08 -0700 From: Poul-Henning Kamp Message-Id: <199504190239.TAA06341@ref.tfs.com> Subject: Re: DAT tape problems To: Harlan.Stenn@pfcs.com (Harlan Stenn) Date: Tue, 18 Apr 1995 19:39:06 -0700 (PDT) Cc: dufault@hda.com, dfr@render.com, current@FreeBSD.org In-Reply-To: <22249.798257424@mumps.pfcs.com> from "Harlan Stenn" at Apr 18, 95 10:10:24 pm Content-Type: text Content-Length: 727 Sender: current-owner@FreeBSD.org Precedence: bulk > I've been quiet, but I can read DAT tapes written from an AIX box, and I > can write tapes with FreeBSD-SNAP950322 (or whatever) and with -current > as of 30 April, but I can't read tapes written by either FreeBSD machine > from either machine. I don't know if the written tapes contain valid > data; I just know that "dump" didn't complain when writing them. Remember to set the tape's blocksize in SMIT to something appropiate for the tape you wrote on FreeBSD. Either '0' (meaning variable) or the exact blocksize you wrote the tape at. -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant' From owner-freebsd-current Tue Apr 18 19:58:03 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA02794 for current-outgoing; Tue, 18 Apr 1995 19:58:03 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA02762 for ; Tue, 18 Apr 1995 19:57:58 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id TAA00885; Tue, 18 Apr 1995 19:55:02 -0700 From: "Rodney W. Grimes" Message-Id: <199504190255.TAA00885@gndrsh.aac.dev.com> Subject: Re: DAT tape problems To: Harlan.Stenn@pfcs.com (Harlan Stenn) Date: Tue, 18 Apr 1995 19:55:01 -0700 (PDT) Cc: dufault@hda.com, dfr@render.com, current@FreeBSD.org In-Reply-To: <22249.798257424@mumps.pfcs.com> from "Harlan Stenn" at Apr 18, 95 10:10:24 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 742 Sender: current-owner@FreeBSD.org Precedence: bulk > > I've been quiet, but I can read DAT tapes written from an AIX box, and I > can write tapes with FreeBSD-SNAP950322 (or whatever) and with -current > as of 30 April, but I can't read tapes written by either FreeBSD machine > from either machine. I don't know if the written tapes contain valid > data; I just know that "dump" didn't complain when writing them. > > I think I get I/O error when reading them, and it might even hose the > machine (I forget - I haven't done it in a while and I don't want to > risk an unplanned reboot right now). try ``restore ibf 10 /dev/rst0''. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Tue Apr 18 20:02:02 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA02921 for current-outgoing; Tue, 18 Apr 1995 20:02:02 -0700 Received: from uustar.starnet.net (root@uustar.starnet.net [128.252.135.2]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id UAA02915 for ; Tue, 18 Apr 1995 20:02:00 -0700 Received: from mumps.pfcs.com by uustar.starnet.net with UUCP id AA12826 (5.67b/IDA-1.5); Tue, 18 Apr 1995 21:47:31 -0500 Received: from localhost by mumps.pfcs.com with SMTP id AA22483 (5.67b/IDA-1.5); Tue, 18 Apr 1995 22:36:54 -0400 To: "Justin T. Gibbs" Cc: se@mi.uni-koeln.de (Stefan Esser), Doug Rabson , current@FreeBSD.org Subject: Re: DAT tape problems In-Reply-To: "Justin T. Gibbs"'s (gibbs@estienne.CS.Berkeley.EDU) message dated Tue, 18 Apr 1995 12:39:08. <199504181939.MAA18635@estienne.cs.berkeley.edu> Date: Tue, 18 Apr 1995 22:36:53 -0300 Message-Id: <22481.798259013@mumps.pfcs.com> From: Harlan Stenn Sender: current-owner@FreeBSD.org Precedence: bulk OK, here's a slightly better report form me. The 950322-SNAP machine is running a bt946C, and the -current (as of 30 March) machine is running an Adaptec 1742 (or 1740 - I forget. It's an EISA machine.) The DAT drive is the Connor 4236 (?) DDS II, which identifies itself at startup as: ahb0 targ 5 lun 0: on one machine, and: bt0: Bt946C/ 0-PCI/EISA/VLB(32bit) bus bt0: reading board settings, busmastering, int=11 bt0: version 4.25J, async only, parity, 32 mbxs, 32 ccbs bt0: targ 0 async bt0: targ 5 async bt0: targ 6 async bt0: Enabling Round robin scheme bt0 at 0x330 irq 11 on isa bt0 waiting for scsi devices to settle (bt0:0:0): "SEAGATE ST32550N 0011" is a type 0 fixed SCSI 2 sd0(bt0:0:0): Direct-Access 2047MB (4194058 512 byte sectors) (bt0:5:0): "ARCHIVE Python 28388-XXX 4.98" is a type 1 removable SCSI 2 st0(bt0:5:0): Sequential-Access density code 0x13, drive empty (bt0:6:0): "TOSHIBA CD-ROM XM-3501TA 3384" is a type 5 removable SCSI 2 cd0(bt0:6:0): CD-ROM cd0(bt0:6:0): NOT READY asc:3a,0Medium not present on the other (just being more complete on this machine). H From owner-freebsd-current Tue Apr 18 22:08:29 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA06221 for current-outgoing; Tue, 18 Apr 1995 22:08:29 -0700 Received: from silver.sms.fi (silver.sms.fi [193.64.137.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA06213 for ; Tue, 18 Apr 1995 22:08:26 -0700 Received: (from pete@localhost) by silver.sms.fi (8.6.11/8.6.9) id IAA05591; Wed, 19 Apr 1995 08:07:00 +0300 Date: Wed, 19 Apr 1995 08:07:00 +0300 Message-Id: <199504190507.IAA05591@silver.sms.fi> From: Petri Helenius To: Joe Greco Cc: freebsd-current@FreeBSD.org Subject: Re: mmap bugs gone yet? In-Reply-To: <9504182143.AA07382@brasil.moneng.mei.com> References: <199504181927.WAA00592@silver.sms.fi> <9504182143.AA07382@brasil.moneng.mei.com> Sender: current-owner@FreeBSD.org Precedence: bulk Joe Greco writes: > Hi Pete, > > I would take this to mean that you're in a very memory-starved environment? > Are you running realtime nntplinks, or batchfile nntplinks? I only deal > with realtime links, so the following discussion mostly applies there: > With 50 outgoing feeds you're most likely to starve a lot of memory. (because you also have readers running around) > I do not think that this would be helped by the integration of nntplink into > INN, multithreaded or otherwise. Basically, if a feed is falling behind, it > will tend to continue to fall even further behind, to a point where it is no > longer reasonable to maintain a cache of articles to be sent in memory. At > this point, INN must log to disk the list of articles to be sent. So there > are a few scenarios that I can envision, depending on the implementation: > Yes, but I can see the behaviour that even if most of the feeds are up to date within 60 or 120 seconds (equals to about same amount of articles) the system tends to read the articles from disk. > INN could remember the entire article in memory, and provide it to the > nntplink threads. I do not think that this would be efficient. Consider > somebody posting several hundred largish (700K) articles in a row. Consider > what the memory requirements would be for any sort of "queued in-RAM" > implementation. Consider the consequences of a feed that was even just a > few articles behind. Now multiply it times ten feeds. :-( !!!! > Over a half of the articles are under 2k, most of the articles are less than 4k. This mechanism could read articles say, larger than 16 or 32k from disk and send them there and keep articles less than that in memory. I've also thought that the article buffer could be shared with the feeds, not separate for each feed (which would a waste memory-wise as you state). If a feed is behind enough not to keep up with the "current" state it should be handled as it is now. > In general, if a feed is not keeping up, you are virtually guaranteed to be > forced to reread the article from disk at some point. The only optimization > I can think of would be to devise some method that would try to > "synchronize" these rereads in some way. I don't see an easy way to do > _that_. More memory allows you more caching. Less memory screws you. The > ideal news server would have a gigabyte of RAM and be able to cache about a > day's worth of news in RAM. :-) > > I do not see any real way to shift the paradigm to alter this scenario - > certainly not if we accept the fact that more than 5 feeds will be severely > lagging. > I think getting this amount from 20 to 5 reads would help a lot in many cases but disk is getting enough cheap to have multiple fast 2G's for your news spool. If only more OS's would support that kind of configuration efficiently. (have the disks mounted as single partition spanning all or many of the disks) Pete From owner-freebsd-current Wed Apr 19 00:22:51 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA09257 for current-outgoing; Wed, 19 Apr 1995 00:22:51 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id AAA09180 for ; Wed, 19 Apr 1995 00:22:13 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA07016; Wed, 19 Apr 1995 09:22:04 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA05711 for freebsd-current@FreeBSD.org; Wed, 19 Apr 1995 09:22:02 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id IAA07774 for freebsd-current@FreeBSD.org; Wed, 19 Apr 1995 08:54:25 +0200 From: J Wunsch Message-Id: <199504190654.IAA07774@uriah.heep.sax.de> Subject: Re: kgdb dumps core when kernel-file doesn't exist To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Wed, 19 Apr 1995 08:54:24 +0200 (MET DST) Reply-To: freebsd-current@FreeBSD.org (FreeBSD-current users) In-Reply-To: <95Apr18.145041pdt.49864@crevenia.parc.xerox.com> from "Bill Fenner" at Apr 18, 95 02:50:32 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 541 Sender: current-owner@FreeBSD.org Precedence: bulk As Bill Fenner wrote: > > I'm really used to typing "adb -k /vmunix /dev/mem", so under FreeBSD I have > been doing "gdb -k /vmunix /dev/mem" by mistake. (Maybe I should link > /vmunix to /kernel =) :-) This reminds me the guy in Usenet who asked what he'd have to do to rename everything back to /vmunix. > Anyway, gdb dumps core when I do this (after printing > a nice error message). :( -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Wed Apr 19 00:30:14 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA09645 for current-outgoing; Wed, 19 Apr 1995 00:30:14 -0700 Received: from nlsys.demon.co.uk (nlsys.demon.co.uk [158.152.125.33]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id AAA09639 for ; Wed, 19 Apr 1995 00:30:11 -0700 Received: (from dfr@localhost) by nlsys.demon.co.uk (8.6.10/8.6.9) id IAA01119; Wed, 19 Apr 1995 08:21:09 +0100 Date: Wed, 19 Apr 1995 08:21:09 +0100 (BST) From: Doug Rabson To: Mark Hittinger cc: current@FreeBSD.org Subject: re: DAT tape problems In-Reply-To: <199504181609.MAA15803@ns1.win.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk On Tue, 18 Apr 1995, Mark Hittinger wrote: > > From: Doug Rabson > > > > I just attempted to read back a dump from a DAT tape to test our backup > > strategy and disturbingly, the file which read back from the tape was > > corrupted. The directory was intact but when the dump was extracted, > > there was a checksum error on one file and when comparing the extracted > > tree with the original, at least one file had been corrupted. > > My DAT drive probes as a 'WangDAT Model 3400DX' and it is set to use > > compression. Does anyone have an idea what is happening? > > I am using one here with success and have not seen this problem. I have > been using it since the first snap (not on 2.0R). > > I am running 3/22 snap now, not -current. > > I have noticed a problem with the last file on the tape. Could this be > what you are seeing? I have placed a dummy file as the last file to be > backed up to get around this issue. This was actually the second to last of about 6 files on the tape. > > My controller is a BT946C. 1542B -- Doug Rabson Mail: dfr@nlsys.demon.co.uk Phone: +44 181 951 1891 From owner-freebsd-current Wed Apr 19 02:41:34 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA13768 for current-outgoing; Wed, 19 Apr 1995 02:41:34 -0700 Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id CAA13760 for ; Wed, 19 Apr 1995 02:41:31 -0700 Received: (from dfr@localhost) by minnow.render.com (8.6.9/8.6.9) id KAA13096; Wed, 19 Apr 1995 10:13:09 +0100 Date: Wed, 19 Apr 1995 10:13:08 +0100 (BST) From: Doug Rabson To: Stefan Esser cc: current@FreeBSD.org Subject: Re: DAT tape problems In-Reply-To: <199504181710.AA17946@FileServ1.MI.Uni-Koeln.DE> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk On Tue, 18 Apr 1995, Stefan Esser wrote: > On Apr 18, 14:19, Doug Rabson wrote: > } Subject: DAT tape problems > } I just attempted to read back a dump from a DAT tape to test our backup > } strategy and disturbingly, the file which read back from the tape was > } corrupted. The directory was intact but when the dump was extracted, > } there was a checksum error on one file and when comparing the extracted > } tree with the original, at least one file had been corrupted. > } > } My DAT drive probes as a 'WangDAT Model 3400DX' and it is set to use > } compression. Does anyone have an idea what is happening? > > DAT drives are supposed to work ! > > I'm using a HP 1533 DDS-2 drive with good success. > > What controller are you using ? Its an old Adaptec 1542B. I am sure that I have successfully restored stuff from this drive before though. Maybe it is something to do with the file being restored not being the first on the tape? -- Doug Rabson, RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 251 4411 FAX: +44 171 251 0939 From owner-freebsd-current Wed Apr 19 02:50:38 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA14058 for current-outgoing; Wed, 19 Apr 1995 02:50:38 -0700 Received: from inet-gw-1.pa.dec.com (inet-gw-1.pa.dec.com [16.1.0.22]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id CAA14050 for ; Wed, 19 Apr 1995 02:50:36 -0700 Received: from rks32.pcs.dec.com by inet-gw-1.pa.dec.com (5.65/24Feb95) id AA05982; Wed, 19 Apr 95 02:49:09 -0700 Received: by rks32.pcs.dec.com (Smail3.1.27.1 #16) id m0s1WKg-0005OqC; Wed, 19 Apr 95 11:46 MSZ Message-Id: To: Bill Fenner Cc: current%freebsd.org@inet-gw-1.pa.dec.com In-Reply-To: Message from Bill Fenner of Tue, 18 Apr 95 14:50:32 PDT. Reply-To: gj@FreeBSD.org Subject: Re: kgdb dumps core when kernel-file doesn't exist Date: Wed, 19 Apr 95 09:46:02 GMT From: "gj%pcs.dec.com@inet-gw-1.pa.dec.com" Sender: current-owner@FreeBSD.org Precedence: bulk > Anyway, gdb dumps core when I do this (after printing a nice error message). ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ What more can you ask for ? :-) Anyway, I'll look into this if nobody beats me to it. Gary J. From owner-freebsd-current Wed Apr 19 03:14:53 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA14626 for current-outgoing; Wed, 19 Apr 1995 03:14:53 -0700 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id DAA14616 for ; Wed, 19 Apr 1995 03:14:33 -0700 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id MAA00764 ; Wed, 19 Apr 1995 12:14:25 +0200 Received: from (roberto@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) id LAA18894 ; Wed, 19 Apr 1995 11:22:13 +0200 From: roberto@blaise.ibp.fr (Ollivier Robert) Message-Id: <199504190922.LAA18894@blaise.ibp.fr> Subject: Re: Info on VM/VFS changes since 4.4Lite To: jhs@regent.e-technik.tu-muenchen.de (Julian Howard Stacey) Date: Wed, 19 Apr 1995 11:22:12 +0200 (MET DST) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@FreeBSD.org In-Reply-To: <199504181957.VAA00731@vector.eikon.e-technik.tu-muenchen.de> from "Julian Howard Stacey" at Apr 18, 95 09:57:06 pm X-Operating-System: FreeBSD 2.0.950416-SNAP ctm#562 X-Mailer: ELM [version 2.4 PL23beta2] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 509 Sender: current-owner@FreeBSD.org Precedence: bulk > > Nice explanation, i gonna translate it into german and post it into > > de.comp.os.unix, if you don't mind. I think this is interesting > > enough to hide it in a mailing list. I've posted it in the french newsgroup fr.comp.os.bsd too. That's too bad that I've written an article with two friends of mine about FreeBSD a few days before this came out... -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@FreeBSD.ORG FreeBSD keltia 2.0.950416-SNAP #17: Sun Apr 16 17:12:07 MET DST 1995 From owner-freebsd-current Wed Apr 19 04:58:25 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA17280 for current-outgoing; Wed, 19 Apr 1995 04:58:25 -0700 Received: from cardhu.cs.hut.fi (hsu@cardhu.cs.hut.fi [130.233.192.95]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id EAA17273 for ; Wed, 19 Apr 1995 04:58:15 -0700 Received: by cardhu.cs.hut.fi id AA20596 (5.65c8/HUTCS-C 1.3 for freebsd-current@FreeBSD.org); Wed, 19 Apr 1995 14:56:08 +0300 Date: Wed, 19 Apr 1995 14:56:08 +0300 From: Heikki Suonsivu Message-Id: <199504191156.AA20596@cardhu.cs.hut.fi> To: Joe Greco Cc: hsu@cs.hut.fi (Heikki Suonsivu), joerg_wunsch@uriah.heep.sax.de, gpalmer@freefall.cdrom.com, freebsd-current@FreeBSD.org Subject: Re: mmap bugs gone yet? In-Reply-To: <9504180423.AA05862@brasil.moneng.mei.com> References: <199504180323.AA16519@cardhu.cs.hut.fi> <9504180423.AA05862@brasil.moneng.mei.com> Organization: Helsinki University of Technology, Otaniemi, Finland Sender: current-owner@FreeBSD.org Precedence: bulk Joe Greco writes: > > It would seem to be writing the history file every 10 articles if you use > > ACT_READ option. I don't know if it writes all of it or just the modified > Does ACT_READ actually affect the history file mechanism? My memory No, sorry, I was intending to say active file. > What NNTP failing in particular are we discussing, anyways? NNTP throughput > rates due to turnaround times? Bandwidth requirements to send complete > uncompressed text chunks? I am not yet aware of any inherent limits to the > technology. All of these. inn is completely single-threaded system and NNTP is completely synchronous protocol (IHAVE-REPLY-Article-REPLY-...). As it is running on top of TCP, it takes at least 4 turnarounds for each article, and innd is not receiving anything else when it is doing a history check, for example. Bandwidth isn't really a problem for anyone else but people who wish to transfer full newsfeed on modems. > Sure, those of us running major backbone sites are using things > such as parallel nntplink processes to help circumvent problems inherent > when you're trying to push gigabytes of news daily, but I don't see this as > a deficiency in the protocol per se. It doesn't help, as innd is single-threaded, it won't serve multiple requests concurrently. We tried double feeding, and as one might guess, it degraded the performance. Mmapping the active file would help for a couple of months, but probably not longer than that. I'll try it (as the mmap bugs seem to be fixed now?) > What I _would_ like to see is a new generation of threaded news tools - > perhaps (most ideally) rolling the functionality of nntplink into INN, and > providing a mechanism that allows INN to open several concurrent NNTP > connections to a peer, multiplexed such that it appears to INN as a single > feed. Would seem a complicated solution to me, when one connection with an efficient protocol and multithreaded news server would solve the problem? multithreading innd probably is the biggest job, just making NNTP do windowing would be simple. -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@cs.hut.fi home +358-0-8031121 work -4513377 fax -4555276 riippu SN From owner-freebsd-current Wed Apr 19 06:27:37 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA19084 for current-outgoing; Wed, 19 Apr 1995 06:27:37 -0700 Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.20.4]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id GAA19070 for ; Wed, 19 Apr 1995 06:27:12 -0700 Received: by brasil.moneng.mei.com (4.1/SMI-4.1) id AA08515; Wed, 19 Apr 95 08:11:17 CDT From: Joe Greco Message-Id: <9504191311.AA08515@brasil.moneng.mei.com> Subject: Re: mmap bugs gone yet? To: hsu@cs.hut.fi (Heikki Suonsivu) Date: Wed, 19 Apr 1995 08:11:17 -0500 (CDT) Cc: hsu@cs.hut.fi, joerg_wunsch@uriah.heep.sax.de, gpalmer@freefall.cdrom.com, freebsd-current@FreeBSD.org In-Reply-To: <199504191156.AA20596@cardhu.cs.hut.fi> from "Heikki Suonsivu" at Apr 19, 95 02:56:08 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 3504 Sender: current-owner@FreeBSD.org Precedence: bulk > Joe Greco writes: > > What NNTP failing in particular are we discussing, anyways? NNTP throughput > > rates due to turnaround times? Bandwidth requirements to send complete > > uncompressed text chunks? I am not yet aware of any inherent limits to the > > technology. > > All of these. inn is completely single-threaded system and NNTP is > completely synchronous protocol (IHAVE-REPLY-Article-REPLY-...). As it is > running on top of TCP, it takes at least 4 turnarounds for each article, > and innd is not receiving anything else when it is doing a history check, > for example. Yes, perhaps this aspect could be threaded, but you are not helping the transaction turnaround time any (i.e. if it takes .2 seconds to complete one whole IHAVE-REPLY-Art-REPLY cycle, you haven't increased that). > Bandwidth isn't really a problem for anyone else but people who wish to > transfer full newsfeed on modems. You haven't tried running a full feed over 56K lately? It does not work unless you are running parallel nntplinks. And there, it just *barely* works (i.e. sucks up 94% of the bandwidth currently, 100% by summer). > > Sure, those of us running major backbone sites are using things > > such as parallel nntplink processes to help circumvent problems inherent > > when you're trying to push gigabytes of news daily, but I don't see this as > > a deficiency in the protocol per se. > > It doesn't help, as innd is single-threaded, it won't serve multiple > requests concurrently. We tried double feeding, and as one might guess, it > degraded the performance. Mmapping the active file would help for a couple > of months, but probably not longer than that. I'll try it (as the mmap > bugs seem to be fixed now?) I don't think mmap'ing the active file will have much of anything to do with that problem. You're not dealing with the active file. What you would *like* to do is to have your history in memory. :-) What sort of target machine are we discussing, anyways? I run one system with a 90%++ rejection rate and I do not notice anything that I would consider "performance degradation" associated with it. > > What I _would_ like to see is a new generation of threaded news tools - > > perhaps (most ideally) rolling the functionality of nntplink into INN, and > > providing a mechanism that allows INN to open several concurrent NNTP > > connections to a peer, multiplexed such that it appears to INN as a single > > feed. > > Would seem a complicated solution to me, when one connection with an > efficient protocol and multithreaded news server would solve the problem? > multithreading innd probably is the biggest job, just making NNTP do > windowing would be simple. If you want to push Son-of-RFC-whatever, go for it. I do not think that the changes you are proposing to innd are feasible. INN enforces coherency within the news system by virtue of its singlethreadedness. You can multithread it, perhaps, by maintaining the singlethreadedness on a per-resource basis (i.e. thread for history access, thread for active file access) but I do not know how much it'll buy you. And I simply hate to reinvent the whole news system, when I can simply write a single utility that would deal quite effectively with the one problem that I do see. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 From owner-freebsd-current Wed Apr 19 08:59:53 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA22744 for current-outgoing; Wed, 19 Apr 1995 08:59:53 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id IAA22737 for ; Wed, 19 Apr 1995 08:59:51 -0700 Received: by halloran-eldar.lcs.mit.edu; id AA02212; Wed, 19 Apr 1995 11:59:40 -0400 Date: Wed, 19 Apr 1995 11:59:40 -0400 From: Garrett Wollman Message-Id: <9504191559.AA02212@halloran-eldar.lcs.mit.edu> To: clary@elec.uq.oz.au (Clary Harridge) Cc: freebsd-current@FreeBSD.org Subject: Why was the NFS mount option wsize removed? In-Reply-To: <9504182352.AA11761@s1.elec.uq.oz.au> References: <9504182352.AA11761@s1.elec.uq.oz.au> Sender: current-owner@FreeBSD.org Precedence: bulk < mount_nfs has a "-w" switch but how what option in /etc/fstab or /etc/exports > will invoke it? -w. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Wed Apr 19 09:38:06 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA23349 for current-outgoing; Wed, 19 Apr 1995 09:38:06 -0700 Received: from cithe312.cithep.caltech.edu (cithe312.cithep.caltech.edu [131.215.124.112]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id JAA23343 ; Wed, 19 Apr 1995 09:38:04 -0700 Received: by cithe312.cithep.caltech.edu (AIX 3.2/UCB 5.64/4.03) id AA19889; Wed, 19 Apr 1995 09:37:31 -0700 From: shih@cithe312.cithep.caltech.edu (Ching Shih) Message-Id: <9504191637.AA19889@cithe312.cithep.caltech.edu> Subject: some comments on the 2.0 and 3.1.1 To: bugs@FreeBSD.org, current@FreeBSD.org Date: Wed, 19 Apr 1995 09:37:30 -0700 (PDT) X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1093 Sender: current-owner@FreeBSD.org Precedence: bulk Hi there, First of all, many thanks for making FreeBSD and Xfree86 working on PC. I have some comments on those, just for your information: I run FreeBSD 2.0 (and its snapshot) and XFree86 3.1.x on my PC. (DX4-100/isa/pci, 3c509, Adaptec 2940, Quantum 1080s, ATI Mach 64, NEC XE17, Combinet CB-160 for ISDN) I tried some some combinations of the 2.0 and the 3.1.x. Some work, others don't: 2.0 + 3.1: working, except no X for ATI Mach64, and not working for 2940+1080s 2.0-950322-SNAP + 3.1: working, except no X for ATI Mach64 but working for 2940+1080s 2.0-950322-SNAP + 3.1.1: cannot make it work for ATI Mach64, even XF_SVGA doesn't work for my ATI Mach64 2.0-950412-SNAP: failed on the installation; stop at "root device changed to sd0a..." Thus so far, only the combination of 2.0-950322 + 3.1 work for me. I cannot fully use the ATI Mach64 card, but use it as a SVGA card. Just try to give you all some feedback. You all just have done a very good job! As a user, I very appreciate it! Ching Shih shih@cithe312.cithep.caltech.edu From owner-freebsd-current Wed Apr 19 11:34:32 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA25666 for current-outgoing; Wed, 19 Apr 1995 11:34:32 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id LAA25640 for ; Wed, 19 Apr 1995 11:33:11 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA29563; Wed, 19 Apr 1995 20:31:29 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA09435; Wed, 19 Apr 1995 20:31:28 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id UAA09477; Wed, 19 Apr 1995 20:16:00 +0200 From: J Wunsch Message-Id: <199504191816.UAA09477@uriah.heep.sax.de> Subject: Re: Why was the NFS mount option wsize removed? To: clary@elec.uq.oz.au (Clary Harridge) Date: Wed, 19 Apr 1995 20:16:00 +0200 (MET DST) Cc: freebsd-current@FreeBSD.org Reply-To: freebsd-current@FreeBSD.org In-Reply-To: <9504182352.AA11761@s1.elec.uq.oz.au> from "Clary Harridge" at Apr 19, 95 09:51:59 am Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 617 Sender: current-owner@FreeBSD.org Precedence: bulk As Clary Harridge wrote: > > Can someone please tell me whether the old mount option for write buffer size > > /dev/sd0e /usr ufs rw,wsize=1024 1 2 > > can be achieved in some other manner? It seems to be not fully intentional. The option handling for the mount command seems to try a simple check if the option ends up in a `=', but the code is broken, so the check would always reject such options. If nobody else jumps in, i'd see if i can repair it. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Wed Apr 19 11:55:31 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA26184 for current-outgoing; Wed, 19 Apr 1995 11:55:31 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id LAA26178 for ; Wed, 19 Apr 1995 11:55:28 -0700 Received: by halloran-eldar.lcs.mit.edu; id AA02575; Wed, 19 Apr 1995 14:52:55 -0400 Date: Wed, 19 Apr 1995 14:52:55 -0400 From: Garrett Wollman Message-Id: <9504191852.AA02575@halloran-eldar.lcs.mit.edu> To: freebsd-current@FreeBSD.org, joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: clary@elec.uq.oz.au (Clary Harridge) Subject: Re: Why was the NFS mount option wsize removed? In-Reply-To: <199504191816.UAA09477@uriah.heep.sax.de> References: <9504182352.AA11761@s1.elec.uq.oz.au> <199504191816.UAA09477@uriah.heep.sax.de> Sender: current-owner@FreeBSD.org Precedence: bulk < said: > It seems to be not fully intentional. It is intentional. The format for options was changed for the worse by 4.4, and we have spent a bit of effort recovering from that mistake. The correct way to specify the old `wsize=' option is with `-w='. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Wed Apr 19 12:22:21 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA26628 for current-outgoing; Wed, 19 Apr 1995 12:22:21 -0700 Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.97.216]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA26622 ; Wed, 19 Apr 1995 12:22:19 -0700 Received: (from kargl@localhost) by troutmask.apl.washington.edu (8.6.11/8.6.9) id MAA02152; Wed, 19 Apr 1995 12:20:19 -0700 From: Steven G Kargl Message-Id: <199504191920.MAA02152@troutmask.apl.washington.edu> Subject: Re: some comments on the 2.0 and 3.1.1 To: shih@cithe312.cithep.caltech.edu (Ching Shih) Date: Wed, 19 Apr 1995 12:20:18 -0700 (PDT) Cc: bugs@FreeBSD.org, current@FreeBSD.org In-Reply-To: <9504191637.AA19889@cithe312.cithep.caltech.edu> from "Ching Shih" at Apr 19, 95 09:37:30 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 884 Sender: current-owner@FreeBSD.org Precedence: bulk According to Ching Shih: > > I run FreeBSD 2.0 (and its snapshot) and XFree86 3.1.x > on my PC. (DX4-100/isa/pci, 3c509, Adaptec 2940, Quantum 1080s, > ATI Mach 64, NEC XE17, Combinet CB-160 for ISDN) > > I tried some some combinations of the 2.0 and the 3.1.x. > Some work, others don't: > > 2.0-950412-SNAP: failed on the installation; > stop at "root device changed to sd0a..." > There seems to be a problem with devices conflicting with the ep0 driver for the 3c509 in 0412-SNAP. I had the same problem until I disabled all devices that could conflict with the ep0 driver. This might help you get up and running, then compile a custom kernel. -- Steven G. Kargl | Phone: 206-685-4677 | Applied Physics Lab | Fax: 206-543-6785 | Univ. of Washington |---------------------| 1013 NE 40th St | FreeBSD 2.1-current | Seattle, WA 98105 |---------------------| From owner-freebsd-current Wed Apr 19 12:48:48 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA27014 for current-outgoing; Wed, 19 Apr 1995 12:48:48 -0700 Received: from inet-gw-1.pa.dec.com (inet-gw-1.pa.dec.com [16.1.0.22]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA27008 for ; Wed, 19 Apr 1995 12:48:39 -0700 Received: from rks32.pcs.dec.com by inet-gw-1.pa.dec.com (5.65/24Feb95) id AA08002; Wed, 19 Apr 95 12:43:16 -0700 Received: by rks32.pcs.dec.com (Smail3.1.27.1 #16) id m0s1fbi-0005OqC; Wed, 19 Apr 95 21:40 MSZ Message-Id: Date: Wed, 19 Apr 95 21:40 MSZ From: garyj@rks32.pcs.dec.com (Gary Jennejohn) To: current%freebsd.org@inet-gw-1.pa.dec.com Subject: patch to gdb Sender: current-owner@FreeBSD.org Precedence: bulk Reply-to: gj@freebsd.org [ had to add the Reply-to by hand, damned mailx ! ] The appended patch fixes the "when I do gdb -k /none_existent_file /dev/mem, gdb core dumps" bug which was recently reported. Can some kind soul apply it ? Maybe it's time for me to get commit privileges, Jordan ? Gary J. ------------------------------- SNIP ------------------------------ *** kcorelow.c~ Wed Apr 19 19:52:52 1995 --- kcorelow.c Wed Apr 19 20:42:48 1995 *************** *** 170,177 **** old_chain = make_cleanup (free, filename); core_kd = kvm_open (exec_bfd->filename, filename, NULL, ! write_files? O_RDWR: O_RDONLY, 0); if (core_kd < 0) perror_with_name (filename); --- 170,187 ---- old_chain = make_cleanup (free, filename); + /* + * gdb doesn't really do anything if the exec-file couldn't + * be opened (in that case exec_bfd is NULL). Usually that's + * no big deal, but kvm_open needs the exec-file's name, + * which results in dereferencing a NULL pointer, a real NO-NO ! + * So, check here if the open of the exec-file succeeded. + */ + if (exec_bfd == NULL) /* the open failed */ + error ("kgdb could not open the exec-file, please check the name you used !"); + core_kd = kvm_open (exec_bfd->filename, filename, NULL, ! write_files? O_RDWR: O_RDONLY, "kgdb: "); if (core_kd < 0) perror_with_name (filename); From owner-freebsd-current Wed Apr 19 14:15:52 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA29467 for current-outgoing; Wed, 19 Apr 1995 14:15:52 -0700 Received: from anvil.wtc.com (anvil.wtc.com [199.38.41.21]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA29461 for ; Wed, 19 Apr 1995 14:15:49 -0700 Received: (from tjon@localhost) by anvil.wtc.com (8.6.11/8.6.9) id QAA18111 for current@freebsd.org; Wed, 19 Apr 1995 16:16:34 -0500 Date: Wed, 19 Apr 1995 16:16:34 -0500 From: Chris Tjon Message-Id: <199504192116.QAA18111@anvil.wtc.com> To: current@FreeBSD.org Subject: upgrade from 2.0-950322-SNAP to 2.0-950412-SNAP Sender: current-owner@FreeBSD.org Precedence: bulk Can I simply extract the src distribution from the 4/12 snap and compile it on a 3/22 system or will this cause problems? Thanks in advance Chris tjon@anvil.wtc.com From owner-freebsd-current Wed Apr 19 14:26:02 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA29788 for current-outgoing; Wed, 19 Apr 1995 14:26:02 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id OAA29781 for ; Wed, 19 Apr 1995 14:25:50 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA03738; Wed, 19 Apr 1995 23:25:19 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA10892 for freebsd-current@FreeBSD.org; Wed, 19 Apr 1995 23:25:17 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id XAA10660 for freebsd-current@FreeBSD.org; Wed, 19 Apr 1995 23:22:07 +0200 From: J Wunsch Message-Id: <199504192122.XAA10660@uriah.heep.sax.de> Subject: Re: Why was the NFS mount option wsize removed? To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Wed, 19 Apr 1995 23:22:06 +0200 (MET DST) Reply-To: freebsd-current@FreeBSD.org (FreeBSD-current users) In-Reply-To: <9504191852.AA02575@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at Apr 19, 95 02:52:55 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 578 Sender: current-owner@FreeBSD.org Precedence: bulk As Garrett Wollman wrote: > > > It seems to be not fully intentional. > > It is intentional. The format for options was changed for the worse > by 4.4, and we have spent a bit of effort recovering from that > mistake. The correct way to specify the old `wsize=' option is with > `-w='. Anyway, changing options in an incompatible way (not only to the predecessors, but also to the `rest of the world') is not a good idea. IMNSO. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Wed Apr 19 14:27:40 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA29872 for current-outgoing; Wed, 19 Apr 1995 14:27:40 -0700 Received: from plains.nodak.edu (tinguely@plains.NoDak.edu [134.129.111.64]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA29865 ; Wed, 19 Apr 1995 14:27:39 -0700 Received: (from tinguely@localhost) by plains.nodak.edu (8.6.11/8.6.10) id QAA10520; Wed, 19 Apr 1995 16:27:26 -0500 Date: Wed, 19 Apr 1995 16:27:26 -0500 From: Mark Tinguely Message-Id: <199504192127.QAA10520@plains.nodak.edu> To: bugs@FreeBSD.org, current@FreeBSD.org, shih@cithe312.cithep.caltech.edu Subject: Re: some comments on the 2.0 and 3.1.1 Content-Length: 322 Sender: current-owner@FreeBSD.org Precedence: bulk > Thus so far, only the combination of 2.0-950322 + 3.1 work for me. > I cannot fully use the ATI Mach64 card, but use it as a SVGA card. for me, the XFree86 3.1 gave poor ATI Mach64 quality at 1024x768 (flickers really bad). When using the 2.0 SNAPs here, I still am using a hand patched XFree86 2.x Release. --mark. From owner-freebsd-current Wed Apr 19 15:29:21 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA01384 for current-outgoing; Wed, 19 Apr 1995 15:29:21 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id PAA01369 for ; Wed, 19 Apr 1995 15:29:06 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA05164; Thu, 20 Apr 1995 00:28:01 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA11433; Thu, 20 Apr 1995 00:27:44 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id AAA12054; Thu, 20 Apr 1995 00:25:21 +0200 From: J Wunsch Message-Id: <199504192225.AAA12054@uriah.heep.sax.de> Subject: Re: upgrade from 2.0-950322-SNAP to 2.0-950412-SNAP To: tjon@anvil.wtc.com (Chris Tjon) Date: Thu, 20 Apr 1995 00:25:18 +0200 (MET DST) Cc: current@FreeBSD.org In-Reply-To: <199504192116.QAA18111@anvil.wtc.com> from "Chris Tjon" at Apr 19, 95 04:16:34 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 531 Sender: current-owner@FreeBSD.org Precedence: bulk As Chris Tjon wrote: > > Can I simply extract the src distribution from the 4/12 snap and compile it > on a 3/22 system or will this cause problems? Should be possible. Anticipate problems with the removal of libgcc.so.261.0. I guess (!) if you're going to do a ``make world'', it should do it. (But it will take time; it used to build things like the C compiler two or three times.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Wed Apr 19 16:03:37 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA02275 for current-outgoing; Wed, 19 Apr 1995 16:03:37 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id QAA02266 for ; Wed, 19 Apr 1995 16:03:21 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA05667; Thu, 20 Apr 1995 01:01:26 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id BAA11755; Thu, 20 Apr 1995 01:01:25 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id BAA00453; Thu, 20 Apr 1995 01:00:23 +0200 From: J Wunsch Message-Id: <199504192300.BAA00453@uriah.heep.sax.de> Subject: Re: patch to gdb To: garyj@rks32.pcs.dec.com (Gary Jennejohn) Date: Thu, 20 Apr 1995 01:00:23 +0200 (MET DST) Cc: freebsd-current@FreeBSD.org (FreeBSD-current users) In-Reply-To: from "Gary Jennejohn" at Apr 19, 95 09:40:00 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 555 Sender: current-owner@FreeBSD.org Precedence: bulk As Gary Jennejohn wrote: > > Reply-to: gj@freebsd.org > > [ had to add the Reply-to by hand, damned mailx ! ] And it didn't even work:-) (There has been a blank line.) > The appended patch fixes the "when I do gdb -k /none_existent_file /dev/mem, > gdb core dumps" bug which was recently reported. > > Can some kind soul apply it ? Commited. (Btw., it was garbled, i had to use ``patch -l''.) Thank'ya! -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Wed Apr 19 16:09:08 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA02373 for current-outgoing; Wed, 19 Apr 1995 16:09:08 -0700 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA02365 for ; Wed, 19 Apr 1995 16:09:01 -0700 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id BAA08226 for ; Thu, 20 Apr 1995 01:08:58 +0200 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id BAA29977 for freebsd-current@FreeBSD.ORG; Thu, 20 Apr 1995 01:08:58 +0200 Received: (from roberto@localhost) by keltia.frmug.fr.net (8.6.11/keltia-uucp-1.21) id BAA01744 for freebsd-current@FreeBSD.ORG; Thu, 20 Apr 1995 01:05:21 +0200 From: Ollivier Robert Message-Id: <199504192305.BAA01744@keltia.frmug.fr.net> Subject: Pb with pcvt's utils To: freebsd-current@FreeBSD.org (FreeBSD Current Users' list) Date: Thu, 20 Apr 1995 01:05:20 +0200 (MET DST) Reply-To: roberto@keltia.freenix.fr (Ollivier Robert) X-Operating-System: FreeBSD 2.0.950416-SNAP ctm#565 X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1062 Sender: current-owner@FreeBSD.org Precedence: bulk -current from 19950417080002 ctm#565 /usr/src/usr.sbin/pcvt : ===> pcvt/vgaio yacc -d /src/src/usr.sbin/pcvt/vgaio/vgaio.y yacc: 2 shift/reduce conflicts. cc -O -m486 -pipe -I /src/src/usr.sbin/pcvt/vgaio/obj -I /src/src/usr.sbin/pcvt/vgaio -g -c y.tab.c -o vgaio.o /usr/include/machine/cpufunc.h: In function `getreg': /usr/include/machine/cpufunc.h:203: impossible register constraint in `asm' /usr/include/machine/cpufunc.h:203: impossible register constraint in `asm' /usr/include/machine/cpufunc.h:203: impossible register constraint in `asm' /usr/include/machine/cpufunc.h: In function `setreg': /usr/include/machine/cpufunc.h:203: impossible register constraint in `asm' /usr/include/machine/cpufunc.h:203: impossible register constraint in `asm' /usr/include/machine/cpufunc.h:203: impossible register constraint in `asm' *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia 2.0.950416-SNAP #18: Sun Apr 16 18:24:55 MET DST 1995 From owner-freebsd-current Wed Apr 19 17:23:01 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA03496 for current-outgoing; Wed, 19 Apr 1995 17:23:01 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA03481 ; Wed, 19 Apr 1995 17:22:52 -0700 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id RAA00643; Wed, 19 Apr 1995 17:22:50 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id RAA02211; Wed, 19 Apr 1995 17:22:49 -0700 Message-Id: <199504200022.RAA02211@corbin.Root.COM> To: hackers@FreeBSD.org, current@FreeBSD.org Subject: wcarchive down From: David Greenman Reply-To: davidg@Root.COM Date: Wed, 19 Apr 1995 17:22:49 -0700 Sender: current-owner@FreeBSD.org Precedence: bulk Wcarchive ate it's system disk after an attempt to add 3 new drives was made. I'm flying down to the Bay area tonight to help fix it, but this will likely require a re-install (and as such, will mean upgrading to -current - a scarey thought). While in the Bay area, I'll likely not be able to read email, so when messages to me go unanswered, this is the reason. I expect wcarchive to be down at least a couple of days, and may not be back up until early next week. Another announcement will be made at that time. Thanks for your patience. -DG From owner-freebsd-current Wed Apr 19 19:38:03 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA10852 for current-outgoing; Wed, 19 Apr 1995 19:38:03 -0700 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id TAA10802 ; Wed, 19 Apr 1995 19:36:19 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: shih@cithe312.cithep.caltech.edu (Ching Shih) cc: bugs@FreeBSD.org, current@FreeBSD.org Subject: Re: some comments on the 2.0 and 3.1.1 In-reply-to: Your message of "Wed, 19 Apr 95 09:37:30 PDT." <9504191637.AA19889@cithe312.cithep.caltech.edu> Date: Wed, 19 Apr 1995 19:36:17 -0700 Message-ID: <10801.798345377@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk > First of all, many thanks for making FreeBSD and Xfree86 working on PC. > > I have some comments on those, just for your information: Thank you, such information is always appreciated! We don't have all possible hardware to test on ourselves and rely on user feedback to let us know how we're doing! I will make a note that there's still some problems with the ATI Mach 64, or that a possible configuration problem exists. The failure to boot with the 2940 under 0412-SNAP is also disturbing and I'm sure Justin will follow up to it. Thanks again! Jordan > > I run FreeBSD 2.0 (and its snapshot) and XFree86 3.1.x > on my PC. (DX4-100/isa/pci, 3c509, Adaptec 2940, Quantum 1080s, > ATI Mach 64, NEC XE17, Combinet CB-160 for ISDN) > > I tried some some combinations of the 2.0 and the 3.1.x. > Some work, others don't: > > 2.0 + 3.1: working, except no X for ATI Mach64, > and not working for 2940+1080s > > 2.0-950322-SNAP + 3.1: working, except no X for ATI Mach64 > but working for 2940+1080s > > 2.0-950322-SNAP + 3.1.1: cannot make it work for ATI Mach64, > even XF_SVGA doesn't work for my ATI Mach64 > > 2.0-950412-SNAP: failed on the installation; > stop at "root device changed to sd0a..." > > Thus so far, only the combination of 2.0-950322 + 3.1 work for me. > I cannot fully use the ATI Mach64 card, but use it as a SVGA card. > > Just try to give you all some feedback. You all just have done > a very good job! As a user, I very appreciate it! > > Ching Shih > shih@cithe312.cithep.caltech.edu From owner-freebsd-current Wed Apr 19 20:56:09 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA13585 for current-outgoing; Wed, 19 Apr 1995 20:56:09 -0700 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id UAA13578 ; Wed, 19 Apr 1995 20:56:07 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: garyj%rks32.pcs.dec.com@inet-gw-1.pa.dec.com (Gary Jennejohn) cc: current@freefall.cdrom.com Subject: Re: patch to gdb In-reply-to: Your message of "Wed, 19 Apr 95 21:40:00 +0600." Date: Wed, 19 Apr 1995 20:56:07 -0700 Message-ID: <13577.798350167@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk > Can some kind soul apply it ? I'll field it. > Maybe it's time for me to get commit privileges, Jordan ? If you're comfortable with CVS, I'm certainly OK with that. I'm already well familiar with the quality of your work (and have been trying to get you more actively involved for as long as I can remember :-). If you're not comfortable with CVS then I suggest that you first practice on a small test repository there before turning yourself loose on the main FreeBSD repository! :-) Jordan From owner-freebsd-current Wed Apr 19 20:59:16 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA13662 for current-outgoing; Wed, 19 Apr 1995 20:59:16 -0700 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id UAA13621 ; Wed, 19 Apr 1995 20:58:51 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: davidg@Root.COM cc: hackers@FreeBSD.org, current@FreeBSD.org Subject: Re: wcarchive down In-reply-to: Your message of "Wed, 19 Apr 95 17:22:49 PDT." <199504200022.RAA02211@corbin.Root.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 19 Apr 1995 20:58:51 -0700 Message-ID: <13620.798350331@freefall.cdrom.com> From: Gary Palmer (FreeBSD/ARM Team) Sender: current-owner@FreeBSD.org Precedence: bulk In message <199504200022.RAA02211@corbin.Root.COM>, David Greenman writes: > I expect wcarchive to be down at least a couple of days, and may not be >back up until early next week. Another announcement will be made at that time. FYI wcarchive is Walnut Creek CDROM's ``ftp'' server (aka ftp.cdrom.com). Also, it'll be down for at least 24-48 hours, and then come back up in a limited fashion across our T1 for testing, and them early next week moved back to the end of the T3 at the Barrnet PoP in Stanford. How stable it'll be remains to be seen :-( Gary From owner-freebsd-current Wed Apr 19 22:20:06 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA18351 for current-outgoing; Wed, 19 Apr 1995 22:20:06 -0700 Received: from shell1.best.com (root@shell1.best.com [204.156.128.10]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA18345 for ; Wed, 19 Apr 1995 22:20:04 -0700 Received: from geli.clusternet (rcarter.vip.best.com [204.156.137.2]) by shell1.best.com (8.6.12/8.6.5) with ESMTP id WAA00425; Wed, 19 Apr 1995 22:19:40 -0700 Received: (from rcarter@localhost) by geli.clusternet (8.6.11/8.6.9) id WAA03907; Wed, 19 Apr 1995 22:18:59 -0700 Date: Wed, 19 Apr 1995 22:18:59 -0700 From: "Russell L. Carter" Message-Id: <199504200518.WAA03907@geli.clusternet> To: davidg@Root.COM, gpalmer@freefall.cdrom.com Subject: Re: wcarchive down Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk |In message <199504200022.RAA02211@corbin.Root.COM>, David Greenman writes: |> I expect wcarchive to be down at least a couple of days, and may not be |>back up until early next week. Another announcement will be made at that time. | |FYI wcarchive is Walnut Creek CDROM's ``ftp'' server (aka ftp.cdrom.com). |Also, it'll be down for at least 24-48 hours, and then come back up in |a limited fashion across our T1 for testing, and them early next week moved |back to the end of the T3 at the Barrnet PoP in Stanford. | |How stable it'll be remains to be seen :-( This is a helluva commitment to FreeBSD, might be messy to begin with but will likely root out many of those hard to find bugs right quick, with long term benefits for the community. Free software is really going through a paradigm shift these days. Russell | |Gary | | From owner-freebsd-current Wed Apr 19 22:50:46 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA18951 for current-outgoing; Wed, 19 Apr 1995 22:50:46 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA18941 for ; Wed, 19 Apr 1995 22:50:30 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id PAA03506; Thu, 20 Apr 1995 15:48:12 +1000 Date: Thu, 20 Apr 1995 15:48:12 +1000 From: Bruce Evans Message-Id: <199504200548.PAA03506@godzilla.zeta.org.au> To: Ollivier.Robert@keltia.frmug.fr.net, freebsd-current@FreeBSD.org Subject: Re: Pb with pcvt's utils Sender: current-owner@FreeBSD.org Precedence: bulk >-current from 19950417080002 ctm#565 >/usr/src/usr.sbin/pcvt : >===> pcvt/vgaio >yacc -d /src/src/usr.sbin/pcvt/vgaio/vgaio.y >yacc: 2 shift/reduce conflicts. >cc -O -m486 -pipe -I /src/src/usr.sbin/pcvt/vgaio/obj -I /src/src/usr.sbin/pcvt/vgaio -g -c y.tab.c -o vgaio.o ^^ >/usr/include/machine/cpufunc.h: In function `getreg': >/usr/include/machine/cpufunc.h:203: impossible register constraint in `asm' This seems to be a compiler bug. The compile works with the default CFLAGS of -O2. The asms in cpufunc.h work in the kernel with -O. They never work with -O0. Why does `make' delete the C source file created by yacc? `make depend' cannot work right without this source file. Bruce From owner-freebsd-current Wed Apr 19 23:08:09 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA19459 for current-outgoing; Wed, 19 Apr 1995 23:08:09 -0700 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id XAA19452 ; Wed, 19 Apr 1995 23:08:07 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: "Russell L. Carter" cc: davidg@Root.COM, current@FreeBSD.org Subject: Re: wcarchive down In-reply-to: Your message of "Wed, 19 Apr 95 22:18:59 PDT." <199504200518.WAA03907@geli.clusternet> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 19 Apr 1995 23:08:07 -0700 Message-ID: <19451.798358087@freefall.cdrom.com> From: Gary Palmer (FreeBSD/ARM Team) Sender: current-owner@FreeBSD.org Precedence: bulk In message <199504200518.WAA03907@geli.clusternet>, "Russell L. Carter" writes: >This is a helluva commitment to FreeBSD, might be messy to begin with but >will likely root out many of those hard to find bugs right quick, with long >term benefits for the community. And in the meantime, every time wcarchive goes down, Walnut Creek's name get's slightly muddier. We were origionally waiting for 2.1 to come out, and be properly tested, etc, etc, before even thinking of touching wcarchive, but it spamming it's /dev/*sd* entries well enough so that we can't even re-mount the root filesystem read-write kinda forced our hands. Yes, it'll force a lot of obscure bugs into the open, but debugging wcarchive isn't easy as we don't normally have any console access... Gary From owner-freebsd-current Wed Apr 19 23:56:15 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA20527 for current-outgoing; Wed, 19 Apr 1995 23:56:15 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id XAA20433 for ; Wed, 19 Apr 1995 23:53:12 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA13624; Thu, 20 Apr 1995 08:53:04 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA14415 for freebsd-current@FreeBSD.org; Thu, 20 Apr 1995 08:53:03 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id IAA02048 for freebsd-current@FreeBSD.org; Thu, 20 Apr 1995 08:40:36 +0200 From: J Wunsch Message-Id: <199504200640.IAA02048@uriah.heep.sax.de> Subject: Re: Pb with pcvt's utils To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Thu, 20 Apr 1995 08:40:36 +0200 (MET DST) Reply-To: freebsd-current@FreeBSD.org (FreeBSD-current users) In-Reply-To: <199504192305.BAA01744@keltia.frmug.fr.net> from "Ollivier Robert" at Apr 20, 95 01:05:20 am Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1452 Sender: current-owner@FreeBSD.org Precedence: bulk As Ollivier Robert wrote: > > -current from 19950417080002 ctm#565 > > /usr/src/usr.sbin/pcvt : > > ===> pcvt/vgaio > yacc -d /src/src/usr.sbin/pcvt/vgaio/vgaio.y > yacc: 2 shift/reduce conflicts. > cc -O -m486 -pipe -I /src/src/usr.sbin/pcvt/vgaio/obj -I /src/src/usr.sbin/pcvt/vgaio -g -c y.tab.c -o vgaio.o > /usr/include/machine/cpufunc.h: In function `getreg': > /usr/include/machine/cpufunc.h:203: impossible register constraint in `asm' > /usr/include/machine/cpufunc.h:203: impossible register constraint in `asm' > /usr/include/machine/cpufunc.h:203: impossible register constraint in `asm' ... ????? bin@uriah 114% make clean rm -f a.out [Ee]rrs mklog vgaio vgaio.o lex.o y.tab.h y.output bin@uriah 115% make yacc -d vgaio.y yacc: 2 shift/reduce conflicts. cc -O2 -m486 -pipe -I /home/bin/pcvt/vgaio/obj -I /home/bin/pcvt/vgaio -g -c y.tab.c -o vgaio.o rm -f y.tab.c lex -I lex.l cc -O2 -m486 -pipe -I /home/bin/pcvt/vgaio/obj -I /home/bin/pcvt/vgaio -g -c lex.yy.c -o lex.o rm -f lex.yy.c cc -O2 -m486 -pipe -I /home/bin/pcvt/vgaio/obj -I /home/bin/pcvt/vgaio -g -o vgaio vgaio.o lex.o -lm -ly -ll bin@uriah 116% ident /usr/include/machine/cpufunc.h /usr/include/machine/cpufunc.h: $Id: cpufunc.h,v 1.34 1995/03/03 22:14:42 davidg Exp $ So i dunno how i can help here. %-] -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Thu Apr 20 01:48:56 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA22747 for current-outgoing; Thu, 20 Apr 1995 01:48:56 -0700 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id BAA22740 for ; Thu, 20 Apr 1995 01:48:53 -0700 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id KAA11101 ; Thu, 20 Apr 1995 10:48:43 +0200 Received: from (roberto@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) id KAA02837 ; Thu, 20 Apr 1995 10:48:42 +0200 From: roberto@blaise.ibp.fr (Ollivier Robert) Message-Id: <199504200848.KAA02837@blaise.ibp.fr> Subject: Re: Pb with pcvt's utils To: bde@zeta.org.au (Bruce Evans) Date: Thu, 20 Apr 1995 10:48:42 +0200 (MET DST) Cc: Ollivier.Robert@keltia.frmug.fr.net, freebsd-current@FreeBSD.org In-Reply-To: <199504200548.PAA03506@godzilla.zeta.org.au> from "Bruce Evans" at Apr 20, 95 03:48:12 pm X-Operating-System: FreeBSD 2.0.950416-SNAP ctm#562 X-Mailer: ELM [version 2.4 PL23beta2] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 526 Sender: current-owner@FreeBSD.org Precedence: bulk > >/usr/include/machine/cpufunc.h: In function `getreg': > >/usr/include/machine/cpufunc.h:203: impossible register constraint in `asm' > > This seems to be a compiler bug. The compile works with the default CFLAGS > of -O2. The asms in cpufunc.h work in the kernel with -O. They never work > with -O0. Its weird as I'm sure this is not the first time I build the tools... -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@FreeBSD.ORG FreeBSD keltia 2.0.950416-SNAP #17: Sun Apr 16 17:12:07 MET DST 1995 From owner-freebsd-current Thu Apr 20 04:12:30 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA26039 for current-outgoing; Thu, 20 Apr 1995 04:12:30 -0700 Received: from utrhcs.cs.utwente.nl (utrhcs.cs.utwente.nl [130.89.10.247]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id EAA26033 for ; Thu, 20 Apr 1995 04:12:27 -0700 Received: from utis156.cs.utwente.nl by utrhcs.cs.utwente.nl (5.0/csrelayMX-SVR4_1.0/RB) id AA05528; Thu, 20 Apr 1995 13:12:17 --100 Received: by utis156.cs.utwente.nl (4.1/RBCS-1.0.1) id AA12725; Thu, 20 Apr 95 13:12:09 +0200 To: current@FreeBSD.org Subject: Programs using kmem always dump core Date: Thu, 20 Apr 1995 13:12:08 +0200 Message-Id: <12724.798376328@utis156.cs.utwente.nl> From: Andras Olah content-length: 884 Sender: current-owner@FreeBSD.org Precedence: bulk Programs that use kvm (e.g. ifconfig, savecore, kvm_mkdb at bootup, but also netstat or ps) dump core on my current machine. I've supped the sources at Wed Apr 19 05:01:02 1995 (reported by sup -t) and did a 'make world -DCLOBBER', so I expect everything on the system to be up to date. Checking some of the core dumps shows that the problem is always in an strcmp call. Does anybody have a clue on what's going wrong. (I can supply more details if needed.) Andras (gdb) run -aux Starting program: /usr/src/bin/ps/obj/ps -aux USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND Program received signal SIGSEGV, Segmentation fault. 0xe106 in strcmp () (gdb) bt #0 0xe106 in strcmp () #1 0x6d40 in __fdnlist () #2 0x52d3 in kvm_nlist () #3 0x1cfb in donlist () #4 0x2885 in getpcpu () #5 0x3674 in pscomp () #6 0x9182 in qsort () #7 0x3373 in main () From owner-freebsd-current Thu Apr 20 08:19:26 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA00188 for current-outgoing; Thu, 20 Apr 1995 08:19:26 -0700 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA00182 for ; Thu, 20 Apr 1995 08:19:24 -0700 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id LAA10306; Thu, 20 Apr 1995 11:18:17 -0400 From: Peter Dufault Message-Id: <199504201518.LAA10306@hda.com> Subject: Re: wcarchive down To: rcarter@geli.com (Russell L. Carter) Date: Thu, 20 Apr 1995 11:18:16 -0400 (EDT) Cc: davidg@Root.COM, gpalmer@freefall.cdrom.com, current@FreeBSD.org In-Reply-To: <199504200518.WAA03907@geli.clusternet> from "Russell L. Carter" at Apr 19, 95 10:18:59 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 555 Sender: current-owner@FreeBSD.org Precedence: bulk Russell L. Carter writes: > > |In message <199504200022.RAA02211@corbin.Root.COM>, David Greenman writes: > |> I expect wcarchive to be down at least a couple of days, and may not be > |>back up until early next week. Another announcement will be made at that time. Could someone say how it spammed its disks, and why the upgrade to -current instead of sticking at 1.1.5.1? Peter -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-current Thu Apr 20 08:35:15 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA00471 for current-outgoing; Thu, 20 Apr 1995 08:35:15 -0700 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA00465 for ; Thu, 20 Apr 1995 08:35:13 -0700 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id RAA17281 for ; Thu, 20 Apr 1995 17:35:10 +0200 Received: from (roberto@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) id RAA04755 for freebsd-current@FreeBSD.org; Thu, 20 Apr 1995 17:35:10 +0200 From: roberto@blaise.ibp.fr (Ollivier Robert) Message-Id: <199504201535.RAA04755@blaise.ibp.fr> Subject: Re: Pb with pcvt's utils To: freebsd-current@FreeBSD.org Date: Thu, 20 Apr 1995 17:35:09 +0200 (MET DST) In-Reply-To: <199504200640.IAA02048@uriah.heep.sax.de> from "J Wunsch" at Apr 20, 95 08:40:36 am X-Operating-System: FreeBSD 2.0.950416-SNAP ctm#562 X-Mailer: ELM [version 2.4 PL23beta2] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 304 Sender: current-owner@FreeBSD.org Precedence: bulk > cc -O2 -m486 -pipe -I /home/bin/pcvt/vgaio/obj -I /home/bin/pcvt/vgaio -g ^^^^^^^^^^^ You use -O2 where I use -O. That's the only difference I see... -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@FreeBSD.ORG FreeBSD keltia 2.0.950416-SNAP #17: Sun Apr 16 17:12:07 MET DST 1995 From owner-freebsd-current Thu Apr 20 08:35:50 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA00484 for current-outgoing; Thu, 20 Apr 1995 08:35:50 -0700 Received: from utrhcs.cs.utwente.nl (utrhcs.cs.utwente.nl [130.89.10.247]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id IAA00478 for ; Thu, 20 Apr 1995 08:35:48 -0700 Received: from utis156.cs.utwente.nl by utrhcs.cs.utwente.nl (5.0/csrelayMX-SVR4_1.0/RB) id AA13272; Thu, 20 Apr 1995 17:35:45 --100 Received: by utis156.cs.utwente.nl (4.1/RBCS-1.0.1) id AA14716; Thu, 20 Apr 95 17:35:38 +0200 To: current@FreeBSD.org Subject: Re: Programs using kmem always dump core In-Reply-To: Your message of Thu, 20 Apr 1995 13:12:08 +0200 Date: Thu, 20 Apr 1995 17:35:37 +0200 Message-Id: <14715.798392137@utis156.cs.utwente.nl> From: Andras Olah content-length: 542 Sender: current-owner@FreeBSD.org Precedence: bulk On Thu, 20 Apr 1995 13:12:08 +0200, Andras Olah wrote: > Programs that use kvm (e.g. ifconfig, savecore, kvm_mkdb at bootup, > but also netstat or ps) dump core on my current machine. I've I've found the (partial) solution in an earlier posting of Bruce. A week ago he wrote about an mmap() bug which causes stripped kernels to have an invalid symbol table. Until now I've used kernels which were 'config -g' -ed and then I 'strip -x' -ed them before installation. I compiled a kernel without -g and there're no more core dumps. Andras From owner-freebsd-current Thu Apr 20 08:58:59 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA01242 for current-outgoing; Thu, 20 Apr 1995 08:58:59 -0700 Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.97.216]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA01236 ; Thu, 20 Apr 1995 08:58:58 -0700 Received: (from kargl@localhost) by troutmask.apl.washington.edu (8.6.11/8.6.9) id IAA04465; Thu, 20 Apr 1995 08:57:12 -0700 From: Steven G Kargl Message-Id: <199504201557.IAA04465@troutmask.apl.washington.edu> Subject: Re: some comments on the 2.0 and 3.1.1 To: jkh@freefall.cdrom.com (Jordan K. Hubbard) Date: Thu, 20 Apr 1995 08:57:11 -0700 (PDT) Cc: shih@cithe312.cithep.caltech.edu, bugs@FreeBSD.org, current@FreeBSD.org In-Reply-To: <10801.798345377@freefall.cdrom.com> from "Jordan K. Hubbard" at Apr 19, 95 07:36:17 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1316 Sender: current-owner@FreeBSD.org Precedence: bulk According to Jordan K. Hubbard: > > > First of all, many thanks for making FreeBSD and Xfree86 working on PC. > > > > I have some comments on those, just for your information: > > Thank you, such information is always appreciated! We don't have all > possible hardware to test on ourselves and rely on user feedback to > let us know how we're doing! I will make a note that there's still > some problems with the ATI Mach 64, or that a possible configuration > problem exists. The failure to boot with the 2940 under 0412-SNAP is > also disturbing and I'm sure Justin will follow up to it. > > > > > 2.0-950412-SNAP: failed on the installation; > > stop at "root device changed to sd0a..." > > > Jordan, I think his problem is related to probing problems with the ep0 driver (3c509). This is the behaviour I saw last Friday when I upgraded my -current machine to 0412-SNAP:( He might be able to boot if he disables all devices that can conflict with the 3c509 (boot: -c and disable everything at address 0x300). If you recall I reported that wt0 and mcd0 found the 3c509. -- Steven G. Kargl | Phone: 206-685-4677 | Applied Physics Lab | Fax: 206-543-6785 | Univ. of Washington |---------------------| 1013 NE 40th St | FreeBSD 2.1-current | Seattle, WA 98105 |---------------------| From owner-freebsd-current Thu Apr 20 09:38:04 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA01994 for current-outgoing; Thu, 20 Apr 1995 09:38:04 -0700 Received: from tcsi.tcs.com (tcsi.tcs.com [137.134.41.11]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA01988 for ; Thu, 20 Apr 1995 09:38:04 -0700 Received: from phact.tcs.com (phact.tcs.com [137.134.41.99]) by tcsi.tcs.com (8.6.10/8.6.10) with ESMTP id JAA23958; Thu, 20 Apr 1995 09:36:23 -0700 Received: from cozumel.tcs.com (cozumel.tcs.com [137.134.104.12]) by phact.tcs.com (8.6.10/8.6.10) with ESMTP id JAA06158; Thu, 20 Apr 1995 09:36:21 -0700 From: Douglas Ambrisko Received: (ambrisko@localhost) by cozumel.tcs.com (8.6.10/8.6.10) id JAA05934; Thu, 20 Apr 1995 09:36:20 -0700 Message-Id: <199504201636.JAA05934@cozumel.tcs.com> Subject: Re: wcarchive down To: gpalmer@freefall.cdrom.com (Gary Palmer) Date: Thu, 20 Apr 1995 09:36:20 -0700 (PDT) Cc: rcarter@geli.com, davidg@Root.COM, current@FreeBSD.org In-Reply-To: <19451.798358087@freefall.cdrom.com> from "Gary Palmer" at Apr 19, 95 11:08:07 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1534 Sender: current-owner@FreeBSD.org Precedence: bulk Gary Palmer writes: | | In message <199504200518.WAA03907@geli.clusternet>, "Russell L. Carter" writes: | >This is a helluva commitment to FreeBSD, might be messy to begin with but | >will likely root out many of those hard to find bugs right quick, with long | >term benefits for the community. | | And in the meantime, every time wcarchive goes down, Walnut Creek's name | get's slightly muddier. We were origionally waiting for 2.1 to come out, and | be properly tested, etc, etc, before even thinking of touching wcarchive, | but it spamming it's /dev/*sd* entries well enough so that we can't even | re-mount the root filesystem read-write kinda forced our hands. | | Yes, it'll force a lot of obscure bugs into the open, but debugging wcarchive | isn't easy as we don't normally have any console access... ----------------------------------------- Gee, sounds like time to use the new serial console mode. I've been using it on my server and it works great. I have it setup so I can tip into it to grab the console etc, as such it now lives in my closet without a monitor or keyboard. Another thing you can use DTR from you tip host to trigger a hard reset to it incase you need to reset it remotely. To do this it just requires a diode and maybe a couple of resistors. It works great. This also makes for a great debugging environment (build your kernel on your fast work-station, boot the kernel from the network and test it through the serial console) Now you can work from anywhere. Doug A. From owner-freebsd-current Thu Apr 20 10:14:16 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA02542 for current-outgoing; Thu, 20 Apr 1995 10:14:16 -0700 Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.20.4]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id KAA02536 ; Thu, 20 Apr 1995 10:14:13 -0700 Received: by brasil.moneng.mei.com (4.1/SMI-4.1) id AA10822; Thu, 20 Apr 95 11:13:06 CDT From: Joe Greco Message-Id: <9504201613.AA10822@brasil.moneng.mei.com> Subject: Re: wcarchive down To: gpalmer@freefall.cdrom.com (Gary Palmer) Date: Thu, 20 Apr 1995 11:13:05 -0500 (CDT) Cc: current@FreeBSD.org, jkh@FreeBSD.org In-Reply-To: <19451.798358087@freefall.cdrom.com> from "Gary Palmer" at Apr 19, 95 11:08:07 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2535 Sender: current-owner@FreeBSD.org Precedence: bulk > In message <199504200518.WAA03907@geli.clusternet>, "Russell L. Carter" writes: > >This is a helluva commitment to FreeBSD, might be messy to begin with but > >will likely root out many of those hard to find bugs right quick, with long > >term benefits for the community. > > And in the meantime, every time wcarchive goes down, Walnut Creek's name > get's slightly muddier. We were origionally waiting for 2.1 to come out, and > be properly tested, etc, etc, before even thinking of touching wcarchive, > but it spamming it's /dev/*sd* entries well enough so that we can't even > re-mount the root filesystem read-write kinda forced our hands. > > Yes, it'll force a lot of obscure bugs into the open, but debugging wcarchive > isn't easy as we don't normally have any console access... Then maybe it's time to ARRANGE for console access. As I recall, somebody recently arranged for serial consoles under -current. This works; I tried it. I spent money on hardware which ultimately will centralize console control for my own little flock of FreeBSD systems. As I also recall, I offered a 386sx/16 at one point in the past to "the Cause". This machine can be outfitted with a little extra circuitry to provide a hardware reset output. I will donate a 2-port 16550 card for this box, and one for wcarchive, if need be, and a cable. You then wire the serial ports together, and the 386sx/16 has console control over wcarchive. The 386sx/16 can reset wcarchive. From this perspective, you can do ANYTHING to wcarchive that does not require physical hardware muckymuck. The 386sx/16 in question has already been verified to fit within the minimalistic space available down at Barrnet. IF there is still interest, *I* am still willing to provide this machine. AND a cheap network card. MAYBE even memory and a hard drive (i.e. whole ball of wax). IF it will make wcarchive maintenance easier! This is almost a drop-in solution! But SOMEBODY has gotta say "O.k., it's time to take advantage of this fool who's willing to give up a machine for free". :-) wcarchive has been *extremely* useful to all of us. I consider it an "essential" resource. Do we have any takers? (Dammit, I have very little time to do software hacking and the like. But I'd like to "contribute" to the FreeBSD effort in some manner!) ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 From owner-freebsd-current Thu Apr 20 10:14:40 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA02560 for current-outgoing; Thu, 20 Apr 1995 10:14:40 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA02552 for ; Thu, 20 Apr 1995 10:14:29 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id DAA23471 for current@freebsd.org; Fri, 21 Apr 1995 03:11:43 +1000 Date: Fri, 21 Apr 1995 03:11:43 +1000 From: Bruce Evans Message-Id: <199504201711.DAA23471@godzilla.zeta.org.au> To: current@FreeBSD.org Subject: bootstrap now too large Sender: current-owner@FreeBSD.org Precedence: bulk Adding 'C' to the usage message and the CDROM case to the switch expanded my boot blocks by 128 bytes. They previously had 16 bytes to spare and are now 112 bytes too large. Apparently gcc generates fat time-optimized code for the switch. Bruce From owner-freebsd-current Thu Apr 20 10:52:48 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA03500 for current-outgoing; Thu, 20 Apr 1995 10:52:48 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA03494 for ; Thu, 20 Apr 1995 10:52:46 -0700 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id KAA14845; Thu, 20 Apr 1995 10:52:21 -0700 From: Poul-Henning Kamp Message-Id: <199504201752.KAA14845@ref.tfs.com> Subject: Re: bootstrap now too large To: bde@zeta.org.au (Bruce Evans) Date: Thu, 20 Apr 1995 10:52:21 -0700 (PDT) Cc: current@FreeBSD.org In-Reply-To: <199504201711.DAA23471@godzilla.zeta.org.au> from "Bruce Evans" at Apr 21, 95 03:11:43 am Content-Type: text Content-Length: 476 Sender: current-owner@FreeBSD.org Precedence: bulk > Adding 'C' to the usage message and the CDROM case to the switch expanded > my boot blocks by 128 bytes. They previously had 16 bytes to spare and > are now 112 bytes too large. > > Apparently gcc generates fat time-optimized code for the switch. SHit! Any body with time on their hands ? -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant' From owner-freebsd-current Thu Apr 20 11:28:27 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA04998 for current-outgoing; Thu, 20 Apr 1995 11:28:27 -0700 Received: from gw.itfs.nsk.su (gw.itfs.nsk.su [193.124.36.33]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA04967 for ; Thu, 20 Apr 1995 11:27:33 -0700 Received: (nnd@localhost) by gw.itfs.nsk.su (8.6.12/8.6.12) id BAA23062 for current@freebsd.org; Fri, 21 Apr 1995 01:26:16 +0700 Date: Fri, 21 Apr 1995 01:26:16 +0700 From: "Nickolay N. Dudorov" Message-Id: <199504201826.BAA23062@gw.itfs.nsk.su> To: current@FreeBSD.org Subject: About 1.1.5.1 quality Sender: current-owner@FreeBSD.org Precedence: bulk Here is just my experience with 1.1.5.1 and 2.1-development: one of my computers (386DX40, 8MB, 340 MB IDE) used to run 1.1.5.1 with named (primary for 4 zones and secondary for another 6), gated (2 ethernets and 1 slip, RIP ), SMTP relay for about 300 UUCP-connected customers (modems and uucp connections established by another comp). All this time I have to reboot it (unless it hungs or reboots without me) every 5 days due to constantn grows of used swap space. Now I use another computer (486SX33, 8MB, 540 MB PCI SCSI) with the same functions and with 2.1-development at April 9 CTM-500 level. Today "w" shows 10+ days up and swap space is used by 25% (from 35MB total). This number would be bigger if I not restart named several times, but I could not find any "unreturned" swap space. I know that this is only ONE example and 1.1.5.1 is realy VERY stable system (my 1.1.5.1 USENET and news-mail server usualy shows more than month up and I reboot it only to change the UPS) but if you dont use some KNOWN experimental or broken parts -current may bite 1.1.5.1 in some applications. N.Dudorov From owner-freebsd-current Thu Apr 20 12:20:57 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA06900 for current-outgoing; Thu, 20 Apr 1995 12:20:57 -0700 Received: from devnull.mpd.tandem.com (devnull.mpd.tandem.com [131.124.4.29]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA06894 for ; Thu, 20 Apr 1995 12:20:56 -0700 Received: from muzak by devnull.mpd.tandem.com (8.6.8/8.6.6) id OAA21584; Thu, 20 Apr 1995 14:20:35 -0500 Received: by muzak (4.1/TSS2.1) id AA08100; Thu, 20 Apr 95 14:16:36 CDT From: chain@mpd.tandem.com (Chain Lee) Message-Id: <9504201916.AA08100@muzak> Subject: Re: 950412-SNAP To: current@FreeBSD.org Date: Thu, 20 Apr 1995 14:16:35 -0500 (CDT) Cc: chain%muzak.mpd.tandem.com@mpd.tandem.com (Chain Lee) X-Mailer: ELM [version 2.4 PL17] Content-Type: text Content-Length: 1823 Sender: current-owner@FreeBSD.org Precedence: bulk > Hello, > > First let me thank you (in case I forget :-) for the great work > you've accomplished! > > I have a few comments/questions regarding diskless and kernel debug > support in this snapshot. > > When running a diskless station using nfs shared /usr, /usr needs > to be mounted very earlier on in /etc/rc and /etc/netstart. In the > current scripts, "mount -a -t nfs" is started after system daemons > which require /usr to be mounted, and therefore the system fails > to start. The mount command may need to be moved into middle of > /etc/netstart where network has been set up but before starting > any network daemons. > > 2) My 'diskless' station has only a DOS partition and no FreeBSD > partition in a wd0 (ST506). It panics during diskless boot. I traced > down the panic to wdopen which was getting an integer division fault. > The trace is as follows: > configure() > swapconf() > wdsize() > wdopen() > ---idiv fault > Is this a known problem? I got around the problem by bypassing wdopen() > but wasn't able to trace further down because no symbols were loaded > into the kernel, and ddb trace shows no names. I modified netboot to > load symbol table over the net but it seems to have no effect. What > other things do I need to do to get the symbol table loaded into ddb? 3) One more thing: mountd seems to allow only one directory to be exported for a mounted file system if no -alldirs options is given. The subsequent entries will get "permission denied" error when being mounted. Is this a desired behavior or a bug (or I was doing something wrong?) > > Thank you again! > > -chain -chain -- Chain Lee Tandem Computers, Inc. Voice: (512) 432-8969 14231 Tandem Boulevard Email: chain@isd.tandem.com Austin, TX 78728-6699 Office: 2359 From owner-freebsd-current Thu Apr 20 12:23:55 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA06928 for current-outgoing; Thu, 20 Apr 1995 12:23:55 -0700 Received: from devnull.mpd.tandem.com (devnull.mpd.tandem.com [131.124.4.29]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA06922 for ; Thu, 20 Apr 1995 12:23:54 -0700 Received: from muzak by devnull.mpd.tandem.com (8.6.8/8.6.6) id OAA21299; Thu, 20 Apr 1995 14:10:44 -0500 Received: by muzak (4.1/TSS2.1) id AA08080; Thu, 20 Apr 95 14:06:37 CDT From: chain@mpd.tandem.com (Chain Lee) Message-Id: <9504201906.AA08080@muzak> Subject: 950412-SNAP To: current@FreeBSD.org Date: Thu, 20 Apr 1995 14:06:34 -0500 (CDT) Cc: chain%muzak.mpd.tandem.com@mpd.tandem.com (Chain Lee) X-Mailer: ELM [version 2.4 PL17] Content-Type: text Content-Length: 1460 Sender: current-owner@FreeBSD.org Precedence: bulk Hello, First let me thank you (in case I forget :-) for the great work you've accomplished! I have a few comments/questions regarding diskless and kernel debug support in this snapshot. When running a diskless station using nfs shared /usr, /usr needs to be mounted very earlier on in /etc/rc and /etc/netstart. In the current scripts, "mount -a -t nfs" is started after system daemons which require /usr to be mounted, and therefore the system fails to start. The mount command may need to be moved into middle of /etc/netstart where network has been set up but before starting any network daemons. 2) My 'diskless' station has only a DOS partition and no FreeBSD partition in a wd0 (ST506). It panics during diskless boot. I traced down the panic to wdopen which was getting an integer division fault. The trace is as follows: configure() swapconf() wdsize() wdopen() ---idiv fault Is this a known problem? I got around the problem by bypassing wdopen() but wasn't able to trace further down because no symbols were loaded into the kernel, and ddb trace shows no names. I modified netboot to load symbol table over the net but it seems to have no effect. What other things do I need to do to get the symbol table loaded into ddb? Thank you again! -chain -- Chain Lee Tandem Computers, Inc. Voice: (512) 432-8969 14231 Tandem Boulevard Email: chain@isd.tandem.com Austin, TX 78728-6699 Office: 2359 From owner-freebsd-current Thu Apr 20 12:35:16 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA07204 for current-outgoing; Thu, 20 Apr 1995 12:35:16 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA07198 for ; Thu, 20 Apr 1995 12:35:11 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id MAA06554; Thu, 20 Apr 1995 12:32:28 -0700 From: "Rodney W. Grimes" Message-Id: <199504201932.MAA06554@gndrsh.aac.dev.com> Subject: Re: 950412-SNAP To: chain@mpd.tandem.com (Chain Lee) Date: Thu, 20 Apr 1995 12:32:27 -0700 (PDT) Cc: current@FreeBSD.org, chain%muzak.mpd.tandem.com@mpd.tandem.com In-Reply-To: <9504201906.AA08080@muzak> from "Chain Lee" at Apr 20, 95 02:06:34 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1030 Sender: current-owner@FreeBSD.org Precedence: bulk > > Hello, > > First let me thank you (in case I forget :-) for the great work > you've accomplished! > > I have a few comments/questions regarding diskless and kernel debug > support in this snapshot. > > When running a diskless station using nfs shared /usr, /usr needs > to be mounted very earlier on in /etc/rc and /etc/netstart. In the > current scripts, "mount -a -t nfs" is started after system daemons > which require /usr to be mounted, and therefore the system fails > to start. The mount command may need to be moved into middle of > /etc/netstart where network has been set up but before starting > any network daemons. Could you please pick up /usr/src/etc/{rc, netstart, sysconfig} and /usr/src/etc/etc.i386/rc.i386 from -current and try them out. I need some more feedback on these versions. I believe your above problems have been addressed in them. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Thu Apr 20 12:43:23 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA07377 for current-outgoing; Thu, 20 Apr 1995 12:43:23 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA07371 for ; Thu, 20 Apr 1995 12:43:19 -0700 Received: by halloran-eldar.lcs.mit.edu; id AA05876; Thu, 20 Apr 1995 15:42:59 -0400 Date: Thu, 20 Apr 1995 15:42:59 -0400 From: Garrett Wollman Message-Id: <9504201942.AA05876@halloran-eldar.lcs.mit.edu> To: chain@mpd.tandem.com (Chain Lee) Cc: current@FreeBSD.org Subject: Re: 950412-SNAP In-Reply-To: <9504201916.AA08100@muzak> References: <9504201916.AA08100@muzak> Sender: current-owner@FreeBSD.org Precedence: bulk < 3) One more thing: mountd seems to allow only one directory to be exported > for a mounted file system if no -alldirs options is given. The > subsequent entries will get "permission denied" error when being mounted. > Is this a desired behavior or a bug (or I was doing something wrong?) Guelph NFS access control operates at the mount points, so this is intentional. If you allowed users to mount any old directory without providing some way to tell the kernel about it, then users would mysteriously find that their mount requests would succeed but then filesystem operations would not, which is clearly even more undesirable. It would be impractical to apply an access-control list at every single vnode, although it might be worth trying anyway to quantify the memory hit. So, in other words, it's a feature to enhance security (although not by much). -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Thu Apr 20 14:41:05 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA11013 for current-outgoing; Thu, 20 Apr 1995 14:41:05 -0700 Received: from FileServ1.MI.Uni-Koeln.DE (FileServ1.MI.Uni-Koeln.DE [134.95.212.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id OAA11007 for ; Thu, 20 Apr 1995 14:40:54 -0700 Received: by FileServ1.MI.Uni-Koeln.DE id AA19852 (5.67b/IDA-1.5 for current@FreeBSD.org); Thu, 20 Apr 1995 23:32:22 +0200 Message-Id: <199504202132.AA19852@FileServ1.MI.Uni-Koeln.DE> From: se@MI.Uni-Koeln.DE (Stefan Esser) Date: Thu, 20 Apr 1995 23:32:21 +0200 In-Reply-To: "Rodney W. Grimes" "Re: 950412-SNAP" (Apr 20, 12:32) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: "Rodney W. Grimes" Subject: Re: 950412-SNAP Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk On Apr 20, 12:32, "Rodney W. Grimes" wrote: } Subject: Re: 950412-SNAP } Could you please pick up /usr/src/etc/{rc, netstart, sysconfig} and } /usr/src/etc/etc.i386/rc.i386 from -current and try them out. I need } some more feedback on these versions. I believe your above problems } have been addressed in them. My system needed one modification to /etc/rc. I'm using the "amd" auto mounter with NIS maps and found that at the time "amd" gets started the NIS binding doesn't succeed in time. I've added an ypwhich >/dev/null 2>&1 immediately after the "ypbind" command, and notice a few seconds of delay at that point. This seems to be the only way to get amd working with NIS maps ... Regards, STefan -- Stefan Esser Internet: Zentrum fuer Paralleles Rechnen Tel: +49 221 4706019 Universitaet zu Koeln FAX: +49 221 4705160 Weyertal 80 50931 Koeln From owner-freebsd-current Thu Apr 20 14:44:59 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA11089 for current-outgoing; Thu, 20 Apr 1995 14:44:59 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id OAA11079 for ; Thu, 20 Apr 1995 14:44:48 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA08772; Thu, 20 Apr 1995 23:42:42 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA19100; Thu, 20 Apr 1995 23:42:41 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id XAA05168; Thu, 20 Apr 1995 23:37:57 +0200 From: J Wunsch Message-Id: <199504202137.XAA05168@uriah.heep.sax.de> Subject: Re: bootstrap now too large To: phk@ref.tfs.com (Poul-Henning Kamp) Date: Thu, 20 Apr 1995 23:37:57 +0200 (MET DST) Cc: bde@zeta.org.au, current@FreeBSD.org In-Reply-To: <199504201752.KAA14845@ref.tfs.com> from "Poul-Henning Kamp" at Apr 20, 95 10:52:21 am Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 759 Sender: current-owner@FreeBSD.org Precedence: bulk As Poul-Henning Kamp wrote: > > > Adding 'C' to the usage message and the CDROM case to the switch expanded > > my boot blocks by 128 bytes. They previously had 16 bytes to spare and > > are now 112 bytes too large. > > > > Apparently gcc generates fat time-optimized code for the switch. > > SHit! > > Any body with time on their hands ? I'm still hacking on them. I've just got a final success report from someone with a Gateway 2000 programmable key, where any and all of our keyboard-probing bootblocks hung before. I'm about to integrate my changes back, and naturally i'll have to re-fit them then... -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Thu Apr 20 14:58:01 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA11555 for current-outgoing; Thu, 20 Apr 1995 14:58:01 -0700 Received: from bunyip.cc.uq.oz.au (bunyip.cc.uq.oz.au [130.102.2.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id OAA11547 for ; Thu, 20 Apr 1995 14:57:59 -0700 Received: from cc.uq.oz.au by bunyip.cc.uq.oz.au id <07299-0@bunyip.cc.uq.oz.au>; Fri, 21 Apr 1995 07:57:12 +1000 Received: from netfl15a.devetir.qld.gov.au by pandora.devetir.qld.gov.au (8.6.10/DEVETIR-E0.3a) with ESMTP id TAA20907 for ; Thu, 20 Apr 1995 19:51:25 +1000 Received: from localhost by netfl15a.devetir.qld.gov.au (8.6.8.1/DEVETIR-0.1) id JAA14550 for ; Thu, 20 Apr 1995 09:49:44 GMT Message-Id: <199504200949.JAA14550@netfl15a.devetir.qld.gov.au> X-Mailer: exmh version 1.6beta 3/23/95 To: current@FreeBSD.org Subject: Slicing breaks new IDE disk Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 20 Apr 1995 19:49:43 +1000 From: Stephen Hocking Sender: current-owner@FreeBSD.org Precedence: bulk Was working fine before I moved to a kernel with the recent slicing changes for IDE drives on it. - a Connor CFA850A drive, allegedly 1652 cyl, 16 heads and 63 sectors/track. I've already backup up the data on this drive and am happy to do anything to it, can anyone give me an explicit set of steps to take to ready it for use as my second drive again? Stephen I do not speak for the Worker's Compensation Board of Queensland - They don't pay me enough for that! From owner-freebsd-current Thu Apr 20 15:30:10 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA12256 for current-outgoing; Thu, 20 Apr 1995 15:30:10 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA12250 for ; Thu, 20 Apr 1995 15:30:09 -0700 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id PAA15883; Thu, 20 Apr 1995 15:10:46 -0700 From: Poul-Henning Kamp Message-Id: <199504202210.PAA15883@ref.tfs.com> Subject: Re: bootstrap now too large To: joerg_wunsch@uriah.heep.sax.de Date: Thu, 20 Apr 1995 15:10:46 -0700 (PDT) Cc: bde@zeta.org.au, current@FreeBSD.org In-Reply-To: <199504202137.XAA05168@uriah.heep.sax.de> from "J Wunsch" at Apr 20, 95 11:37:57 pm Content-Type: text Content-Length: 668 Sender: current-owner@FreeBSD.org Precedence: bulk > As Poul-Henning Kamp wrote: > > > > > Adding 'C' to the usage message and the CDROM case to the switch expanded > > > my boot blocks by 128 bytes. They previously had 16 bytes to spare and > > > are now 112 bytes too large. > > > > > > Apparently gcc generates fat time-optimized code for the switch. > > > > SHit! > > > > Any body with time on their hands ? > > I'm still hacking on them. I've just got a final success report from OK, I got them back down to size. Have fun! -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant' From owner-freebsd-current Thu Apr 20 16:07:36 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA13273 for current-outgoing; Thu, 20 Apr 1995 16:07:36 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA13267 for ; Thu, 20 Apr 1995 16:07:31 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id QAA07244; Thu, 20 Apr 1995 16:04:27 -0700 From: "Rodney W. Grimes" Message-Id: <199504202304.QAA07244@gndrsh.aac.dev.com> Subject: Re: 950412-SNAP To: se@MI.Uni-Koeln.DE (Stefan Esser) Date: Thu, 20 Apr 1995 16:04:27 -0700 (PDT) Cc: current@FreeBSD.org In-Reply-To: <199504202132.AA19852@FileServ1.MI.Uni-Koeln.DE> from "Stefan Esser" at Apr 20, 95 11:32:21 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1771 Sender: current-owner@FreeBSD.org Precedence: bulk > > On Apr 20, 12:32, "Rodney W. Grimes" wrote: > } Subject: Re: 950412-SNAP > } Could you please pick up /usr/src/etc/{rc, netstart, sysconfig} and > } /usr/src/etc/etc.i386/rc.i386 from -current and try them out. I need > } some more feedback on these versions. I believe your above problems > } have been addressed in them. > > My system needed one modification to /etc/rc. > > I'm using the "amd" auto mounter with NIS maps > and found that at the time "amd" gets started > the NIS binding doesn't succeed in time. > > I've added an > > ypwhich >/dev/null 2>&1 > > immediately after the "ypbind" command, and > notice a few seconds of delay at that point. > > This seems to be the only way to get amd > working with NIS maps ... Are you saying the following diff fixed your problem: And could others running NIS please test this so I can commit it with a reviewed by: line. I don't run NIS here :-(. Index: rc =================================================================== RCS file: /home/ncvs/src/etc/rc,v retrieving revision 1.63 diff -c -r1.63 rc *** 1.63 1995/04/11 18:36:10 --- rc 1995/04/20 23:02:56 *************** *** 179,184 **** --- 179,185 ---- # Start ypbind if we're an NIS client if [ "X${nis_clientflags}" != X"NO" ]; then echo -n ' ypbind'; ypbind ${nis_clientflags} + ypwhich >/dev/null 2>&1 fi # $rwhod is imported from /etc/sysconfig; > > Regards, STefan > > -- > Stefan Esser Internet: > Zentrum fuer Paralleles Rechnen Tel: +49 221 4706019 > Universitaet zu Koeln FAX: +49 221 4705160 > Weyertal 80 > 50931 Koeln > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Thu Apr 20 16:19:26 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA13550 for current-outgoing; Thu, 20 Apr 1995 16:19:26 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id QAA13543 for ; Thu, 20 Apr 1995 16:19:10 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA10783; Fri, 21 Apr 1995 01:17:49 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id BAA19998 for freebsd-current@FreeBSD.org; Fri, 21 Apr 1995 01:17:48 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id BAA06269 for freebsd-current@FreeBSD.org; Fri, 21 Apr 1995 01:17:14 +0200 From: J Wunsch Message-Id: <199504202317.BAA06269@uriah.heep.sax.de> Subject: biosboot To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Fri, 21 Apr 1995 01:17:13 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 362 Sender: current-owner@FreeBSD.org Precedence: bulk Sorry if i've just stepped on someone's toes with my commit to biosboot. I noticed i had to do a cvs update before, but with > 60 % packet loss, i was unable to examine the diffs yet another time before commiting. :( -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Thu Apr 20 17:10:26 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA14733 for current-outgoing; Thu, 20 Apr 1995 17:10:26 -0700 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id RAA14720 ; Thu, 20 Apr 1995 17:10:21 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: Peter Dufault cc: rcarter@geli.com (Russell L. Carter), davidg@Root.COM, current@FreeBSD.org Subject: Re: wcarchive down In-reply-to: Your message of "Thu, 20 Apr 95 11:18:16 EDT." <199504201518.LAA10306@hda.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 20 Apr 1995 17:10:20 -0700 Message-ID: <14719.798423020@freefall.cdrom.com> From: Gary Palmer (FreeBSD/ARM Team) Sender: current-owner@FreeBSD.org Precedence: bulk In message <199504201518.LAA10306@hda.com>, Peter Dufault writes: >Could someone say how it spammed its disks, and why the upgrade to >-current instead of sticking at 1.1.5.1? We tried to put 3 new Quantum Grand Prix drives onto a Adaptec 174x SCSI card. Pity that the Adaptec cards have a problem talking to the drives or something and the SCSI bus just kept locking up. This somehow forced the system to spam the entries for /dev/*sd0*. This meant that we couldn't even remount the drive read-write to correct the /dev entries. Also, the upgrade to -current has been scheduled for a LONG time 'cos we NEED (urgently) large filesystem (>>2Gb) support. Gary From owner-freebsd-current Thu Apr 20 17:12:24 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA14783 for current-outgoing; Thu, 20 Apr 1995 17:12:24 -0700 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id RAA14776 ; Thu, 20 Apr 1995 17:12:22 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: Douglas Ambrisko cc: rcarter@geli.com, davidg@Root.COM, current@FreeBSD.org Subject: Re: wcarchive down In-reply-to: Your message of "Thu, 20 Apr 95 09:36:20 PDT." <199504201636.JAA05934@cozumel.tcs.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 20 Apr 1995 17:12:21 -0700 Message-ID: <14775.798423141@freefall.cdrom.com> From: Gary Palmer (FreeBSD/ARM Team) Sender: current-owner@FreeBSD.org Precedence: bulk In message <199504201636.JAA05934@cozumel.tcs.com>, Douglas Ambrisko writes: >Gary Palmer writes: >Gee, sounds like time to use the new serial console mode. I've been using it >on my server and it works great. OK, fine, you willing to pay BARRNET the extra money to have a second machine on the ethernet and the extra rack space & so on? You have to remember that we don't have the bandwidth on site to site it locally, it's at BARRNET's Stanford PoP. Gary From owner-freebsd-current Thu Apr 20 17:13:45 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA14848 for current-outgoing; Thu, 20 Apr 1995 17:13:45 -0700 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id RAA14841 ; Thu, 20 Apr 1995 17:13:43 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: Joe Greco cc: current@FreeBSD.org, jkh@FreeBSD.org Subject: Re: wcarchive down In-reply-to: Your message of "Thu, 20 Apr 95 11:13:05 CDT." <9504201613.AA10822@brasil.moneng.mei.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 20 Apr 1995 17:13:43 -0700 Message-ID: <14839.798423223@freefall.cdrom.com> From: Gary Palmer (FreeBSD/ARM Team) Sender: current-owner@FreeBSD.org Precedence: bulk In message <9504201613.AA10822@brasil.moneng.mei.com>, Joe Greco writes: >Then maybe it's time to ARRANGE for console access. [...] >The 386sx/16 in question has already been verified to fit within the >minimalistic space available down at Barrnet. We would still have to persuade BARRNET to let us have another IP address and a second ethernet tap. This may not be easy. Even if we aren't gonna be using much (if any) bandwidth... Gary From owner-freebsd-current Thu Apr 20 17:23:26 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA15174 for current-outgoing; Thu, 20 Apr 1995 17:23:26 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id RAA15168 for ; Thu, 20 Apr 1995 17:23:16 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA10696; Fri, 21 Apr 1995 01:11:36 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id BAA19950; Fri, 21 Apr 1995 01:11:13 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id BAA06086; Fri, 21 Apr 1995 01:01:18 +0200 From: J Wunsch Message-Id: <199504202301.BAA06086@uriah.heep.sax.de> Subject: Re: bootstrap now too large To: phk@ref.tfs.com (Poul-Henning Kamp) Date: Fri, 21 Apr 1995 01:01:17 +0200 (MET DST) Cc: joerg_wunsch@uriah.heep.sax.de, bde@zeta.org.au, current@FreeBSD.org In-Reply-To: <199504202210.PAA15883@ref.tfs.com> from "Poul-Henning Kamp" at Apr 20, 95 03:10:46 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 368 Sender: current-owner@FreeBSD.org Precedence: bulk As Poul-Henning Kamp wrote: > > > I'm still hacking on them. I've just got a final success report from > > OK, I got them back down to size. Have fun! Just about to commit my changes. Lines are waaay too slow however. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Thu Apr 20 17:25:59 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA15988 for current-outgoing; Thu, 20 Apr 1995 17:25:59 -0700 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id RAA15953 ; Thu, 20 Apr 1995 17:25:56 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: Peter Dufault cc: rcarter@geli.com (Russell L. Carter), davidg@Root.COM, gpalmer@freefall.cdrom.com, current@FreeBSD.org Subject: Re: wcarchive down In-reply-to: Your message of "Thu, 20 Apr 95 11:18:16 EDT." <199504201518.LAA10306@hda.com> Date: Thu, 20 Apr 1995 17:25:55 -0700 Message-ID: <15943.798423955@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk > Could someone say how it spammed its disks, and why the upgrade to > -current instead of sticking at 1.1.5.1? 1. Dicky 1742 controller, it looks like. The thing was ancient and needed to be upgraded. 2. We don't even have any reasonable 1.1.5.1 distributions around here. We took the legal injunction seriously, and I doubt that I'd even be able to scare up a 1.x repair disk if I tried. Nor would I ftp a distribution from somewhere else. Those kinds of hassles we don't need. It's not worth it. Running 1.x on wcarchive all this time was a major thorn in our side and a perennial risk for Walnut Creek, legally bound as they were to not use 1.x. I'm glad it's behind us. Jordan From owner-freebsd-current Thu Apr 20 17:30:41 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA16813 for current-outgoing; Thu, 20 Apr 1995 17:30:41 -0700 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id RAA16805 ; Thu, 20 Apr 1995 17:30:39 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: Douglas Ambrisko cc: gpalmer@freefall.cdrom.com (Gary Palmer), rcarter@geli.com, davidg@Root.COM, current@FreeBSD.org Subject: Re: wcarchive down In-reply-to: Your message of "Thu, 20 Apr 95 09:36:20 PDT." <199504201636.JAA05934@cozumel.tcs.com> Date: Thu, 20 Apr 1995 17:30:38 -0700 Message-ID: <16804.798424238@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk > Gee, sounds like time to use the new serial console mode. I've been using it > on my server and it works great. I have it setup so I can tip into it to > grab the console etc, as such it now lives in my closet without a monitor or We've been over this before. We don't have the luxury of being able to install another machine in that machine room, nor are any of the neighboring machines "friendly" enough to us to provide access. We're in a hostile machine room where space costs multiple thousands of dollars per square foot per year! We need to implement the least obtrusive solutions available.. :-) Jordan From owner-freebsd-current Thu Apr 20 18:48:14 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA19460 for current-outgoing; Thu, 20 Apr 1995 18:48:14 -0700 Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.20.4]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id SAA19453 for ; Thu, 20 Apr 1995 18:48:12 -0700 Received: by brasil.moneng.mei.com (4.1/SMI-4.1) id AA11703; Thu, 20 Apr 95 20:45:58 CDT From: Joe Greco Message-Id: <9504210145.AA11703@brasil.moneng.mei.com> Subject: Re: wcarchive down To: jkh@freefall.cdrom.com (Jordan K. Hubbard) Date: Thu, 20 Apr 1995 20:45:57 -0500 (CDT) Cc: ambrisko@tcs.com, gpalmer@freefall.cdrom.com, rcarter@geli.com, davidg@Root.COM, current@FreeBSD.org In-Reply-To: <16804.798424238@freefall.cdrom.com> from "Jordan K. Hubbard" at Apr 20, 95 05:30:38 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1236 Sender: current-owner@FreeBSD.org Precedence: bulk > We've been over this before. > > We don't have the luxury of being able to install another machine in > that machine room, nor are any of the neighboring machines "friendly" > enough to us to provide access. We're in a hostile machine room where > space costs multiple thousands of dollars per square foot per year! > We need to implement the least obtrusive solutions available.. :-) Last I heard, back in October, we had sorta agreed that there might be space for a slimline PC...? I have a box that is about 16"x16"x4", case, power supply, the works. 3 slots, built in VGA, etc. At the time, this was "just about an exact fit". I have a 386sx/16 motherboard, too. Much smaller footprint. If somebody can come up with a riser card and a very compact power supply, I could probably hit something like 16"x8"x2" (haven't measured it). If space is *really* short, maybe a microcontroller with Ethernet. I am willing to work on this with someone. _IF_ there's any interest. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Software Engineer, UNIX/Network Hacker, Etc. 414/362-3617 Marquette Electronics, Inc. - R&D - Milwaukee, WI jgreco@mei.com From owner-freebsd-current Thu Apr 20 18:55:53 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA19616 for current-outgoing; Thu, 20 Apr 1995 18:55:53 -0700 Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.20.4]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id SAA19609 ; Thu, 20 Apr 1995 18:55:51 -0700 Received: by brasil.moneng.mei.com (4.1/SMI-4.1) id AA11730; Thu, 20 Apr 95 20:54:48 CDT From: Joe Greco Message-Id: <9504210154.AA11730@brasil.moneng.mei.com> Subject: Re: wcarchive down To: gpalmer@freefall.cdrom.com (Gary Palmer) Date: Thu, 20 Apr 1995 20:54:47 -0500 (CDT) Cc: current@FreeBSD.org, jkh@FreeBSD.org In-Reply-To: <14839.798423223@freefall.cdrom.com> from "Gary Palmer" at Apr 20, 95 05:13:43 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1283 Sender: current-owner@FreeBSD.org Precedence: bulk > We would still have to persuade BARRNET to let us have another IP address > and a second ethernet tap. This may not be easy. Even if we aren't > gonna be using much (if any) bandwidth... I guess I am not in the mood to fight to _give_ away a machine to what I consider a worthy cause. I was hoping that people would be a little more enthusiastic and try to come up with ways to implement SOMETHING... It's quite simple, really. If you want to be able to get at the console without being in the machine room, you need a communications medium. You can use phone lines. You can use Ethernet. You can use ham radio. You can use telegraph. You can use smoke signals. Somebody with knowledge of the situation has to evaluate what technologies might be used. If somebody has to grovel with BARRNET for an IP, so be it. If a phone line can be brought in (this _is_ a PoP, right?), maybe that's cheaper/easier. Whatever the hell works. Now, if, along the way, I can provide any technology or equipment that I already possess or can cheaply acquire, I will do so... ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 From owner-freebsd-current Thu Apr 20 19:31:45 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA20576 for current-outgoing; Thu, 20 Apr 1995 19:31:45 -0700 Received: from gilmore.nas.nasa.gov (gilmore.nas.nasa.gov [129.99.33.168]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA20562 for ; Thu, 20 Apr 1995 19:31:39 -0700 Received: from localhost (localhost [127.0.0.1]) by gilmore.nas.nasa.gov (8.6.10/8.3) with ESMTP id TAA08764; Thu, 20 Apr 1995 19:32:31 -0700 Message-Id: <199504210232.TAA08764@gilmore.nas.nasa.gov> Reply-To: Dave Tweten To: brian@mediacity.com (Brian Litzinger) cc: henrich@crh.cl.msu.edu (Charles Henrich), freebsd-current@FreeBSD.org Subject: Re: Memory init pattern Date: Thu, 20 Apr 1995 19:32:29 -0700 From: Dave Tweten Sender: current-owner@FreeBSD.org Precedence: bulk Brian Litzinger writes: >> >Hey, I'm not suggesting filling memory with zeros or all "U"s (ala WATFIV), >> >just pick something that doesn't mean anything in any language or culture. >> >Save the FreeBSD PR people some headaches later. (I agree - we do have >> >enough controversy now just with the daemon logo unfortunately.) >I agree with the original posters sentiment. >If FreeBSD wants to be taken seriously in the business community, >which I sincerely hope it does and would like to help in making it so, >it has to "play the game", by the rules the game is played by. Just as a data point on the "business community," when I worked for Control Data, about 15 years ago, their Cyber 200 series computers would display a 32-bit hex number on the system console when they crashed. The two most frequent were DEADBEEF and DEADCACA. They were all in the DEAD0000 to DEADFFFF range and were known as "dead codes." Course, CDC may not be the best precedent to follow for commercial success. From owner-freebsd-current Thu Apr 20 20:17:39 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA22874 for current-outgoing; Thu, 20 Apr 1995 20:17:39 -0700 Received: from ns1.win.net (ns1.win.net [204.215.209.3]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id UAA22859 for ; Thu, 20 Apr 1995 20:17:37 -0700 Received: (from bugs@localhost) by ns1.win.net (8.6.11/8.6.9) id XAA01212 for current@freebsd.org; Thu, 20 Apr 1995 23:19:10 -0400 From: Mark Hittinger Message-Id: <199504210319.XAA01212@ns1.win.net> Subject: Re: wcarchive down (fwd) To: current@FreeBSD.org Date: Thu, 20 Apr 1995 23:19:09 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 429 Sender: current-owner@FreeBSD.org Precedence: bulk There was an interesting little device on a stack of routers that I saw in town. It was a telephone power switch. The routers were plugged into this black box that was plugged into the ac. There was a phone line plugged into this black box. You could dial the black box, punch in a code, and it would power cycle the router stack. I sort of wish I had that for my main box now :-) Regards, Mark Hittinger bugs@win.net From owner-freebsd-current Thu Apr 20 20:19:35 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA22921 for current-outgoing; Thu, 20 Apr 1995 20:19:35 -0700 Received: from ns1.win.net (ns1.win.net [204.215.209.3]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id UAA22915 for ; Thu, 20 Apr 1995 20:19:32 -0700 Received: (from bugs@localhost) by ns1.win.net (8.6.11/8.6.9) id XAA01936 for current@freebsd.org; Thu, 20 Apr 1995 23:21:05 -0400 From: Mark Hittinger Message-Id: <199504210321.XAA01936@ns1.win.net> Subject: sd1a: oop not found biodone: buffer already done To: current@FreeBSD.org Date: Thu, 20 Apr 1995 23:21:05 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 294 Sender: current-owner@FreeBSD.org Precedence: bulk I am seeing more of: sd1a: oop not found biodone: buffer already done typically the system is locked up or a process (generally INN) is locked up. I am running the 3/22 snap right now. The processes are unkillable. Wchan on ps shows them in getblk. Regards, Mark Hittinger bugs@win.net From owner-freebsd-current Thu Apr 20 20:47:28 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA23632 for current-outgoing; Thu, 20 Apr 1995 20:47:28 -0700 Received: from westhill.cdrom.com (westhill.cdrom.com [192.216.223.57]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id UAA23615 for ; Thu, 20 Apr 1995 20:47:25 -0700 Received: from localhost (localhost [127.0.0.1]) by westhill.cdrom.com (8.6.11/8.6.11) with SMTP id UAA06712; Thu, 20 Apr 1995 20:33:10 -0700 X-Authentication-Warning: westhill.cdrom.com: Host localhost didn't use HELO protocol To: Mark Hittinger cc: current@FreeBSD.org Subject: Re: wcarchive down (fwd) In-reply-to: Your message of "Thu, 20 Apr 1995 23:19:09 EDT." <199504210319.XAA01212@ns1.win.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 20 Apr 1995 20:33:10 -0700 Message-ID: <6711.798435190@westhill.cdrom.com> From: Gary Palmer Sender: current-owner@FreeBSD.org Precedence: bulk In message <199504210319.XAA01212@ns1.win.net>, Mark Hittinger writes: >There was an interesting little device on a stack of routers that I saw >in town. >It was a telephone power switch. The routers were plugged into this >black box that was plugged into the ac. There was a phone line plugged >into this black box. >You could dial the black box, punch in a code, and it would power cycle >the router stack. We are seriously thinking about this ourselves, but with a AC powered cell phone rather than a conventional land-line phone. For one reason. It may be a PoP, but running another phone line in there would be expensive, and cell phones & access rates are dirt cheap now. Gary From owner-freebsd-current Thu Apr 20 22:02:16 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA26438 for current-outgoing; Thu, 20 Apr 1995 22:02:16 -0700 Received: from bunyip.cc.uq.oz.au (bunyip.cc.uq.oz.au [130.102.2.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id WAA26430 for ; Thu, 20 Apr 1995 22:02:15 -0700 Received: from cc.uq.oz.au by bunyip.cc.uq.oz.au id <00997-0@bunyip.cc.uq.oz.au>; Fri, 21 Apr 1995 15:01:38 +1000 Received: from netfl15a.devetir.qld.gov.au by pandora.devetir.qld.gov.au (8.6.10/DEVETIR-E0.3a) with ESMTP id PAA26592; Fri, 21 Apr 1995 15:05:27 +1000 Received: from localhost by netfl15a.devetir.qld.gov.au (8.6.8.1/DEVETIR-0.1) id FAA21553; Fri, 21 Apr 1995 05:03:50 GMT Message-Id: <199504210503.FAA21553@netfl15a.devetir.qld.gov.au> X-Mailer: exmh version 1.6beta 3/23/95 To: Poul-Henning Kamp cc: current@FreeBSD.org Subject: Re: Slicing breaks new IDE disk In-reply-to: Your message of "Thu, 20 Apr 1995 15:04:45 MST." <199504202204.PAA15840@ref.tfs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Apr 1995 15:03:49 +1000 From: Stephen Hocking Sender: current-owner@FreeBSD.org Precedence: bulk Aaagh, fixed it by rebooting from a recent install flop, and repartiting the disk from it. Works fine now, rrestore is busily humming away event as we speak. > > Was working fine before I moved to a kernel with the recent slicing changes > > for IDE drives on it. - a Connor CFA850A drive, allegedly 1652 cyl, 16 heads > > and 63 sectors/track. I've already backup up the data on this drive and am > > happy to do anything to it, can anyone give me an explicit set of steps to > > take to ready it for use as my second drive again? > > Be more specific, what happens ? > > -- > Poul-Henning Kamp -- TRW Financial Systems, Inc. > 'All relevant people are pertinent' && 'All rude people are impertinent' > => 'no rude people are relevant' I do not speak for the Worker's Compensation Board of Queensland - They don't pay me enough for that! From owner-freebsd-current Thu Apr 20 23:24:18 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA29694 for current-outgoing; Thu, 20 Apr 1995 23:24:18 -0700 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id XAA29687 ; Thu, 20 Apr 1995 23:24:16 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: Joe Greco cc: gpalmer@freefall.cdrom.com (Gary Palmer), current@FreeBSD.org, jkh@FreeBSD.org Subject: Re: wcarchive down In-reply-to: Your message of "Thu, 20 Apr 95 11:13:05 CDT." <9504201613.AA10822@brasil.moneng.mei.com> Date: Thu, 20 Apr 1995 23:24:16 -0700 Message-ID: <29684.798445456@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk > As I also recall, I offered a 386sx/16 at one point in the past to "the > Cause". This machine can be outfitted with a little extra circuitry to > provide a hardware reset output. I will donate a 2-port 16550 card for this > box, and one for wcarchive, if need be, and a cable. You then wire the > serial ports together, and the 386sx/16 has console control over wcarchive. > The 386sx/16 can reset wcarchive. From this perspective, you can do > ANYTHING to wcarchive that does not require physical hardware muckymuck. Yes, you did offer that and I'm still grateful for the offer. I haven't taken you up on that offer yet due to the twin reasons of severe time pressure (we haven't been thinking much about it lately, though it's always somewhere in the back of my mind) and basically my disenchantment with the whole idea of adding an entire extra machine to do this. Where this arrangement with wcarchive and BARRNET is concerned, the simpler the solution the better! I don't want another machine to manage and worry about if I can help it, and the solution we've come up with is rather more simplistic. What I'm going to do is get a cheap cellular phone and a basic rate service with a local provider (I've verified good reception at that location with my own cell phone) and hook it to a ready-built DTMF decoder of the type various HAM enthusiasts use to control remote repeaters (in fact, I count on buying it at the local HAM shack), and we're going to reset that baby by calling it up and punching numbers at it. It's cheap, it's simple, it can be literally bolted to the side of the existing system (we'll work out something creative - there's even room inside some of the disk cases; we could run a wire out to the CPU module.. :-) Jordan From owner-freebsd-current Thu Apr 20 23:56:44 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA01202 for current-outgoing; Thu, 20 Apr 1995 23:56:44 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA01196 for ; Thu, 20 Apr 1995 23:56:41 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id XAA07853; Thu, 20 Apr 1995 23:53:20 -0700 From: "Rodney W. Grimes" Message-Id: <199504210653.XAA07853@gndrsh.aac.dev.com> Subject: Re: wcarchive down To: gpalmer@freefall.cdrom.com (Gary Palmer) Date: Thu, 20 Apr 1995 23:53:19 -0700 (PDT) Cc: ambrisko@tcs.com, rcarter@geli.com, davidg@Root.COM, current@FreeBSD.org In-Reply-To: <14775.798423141@freefall.cdrom.com> from "Gary Palmer" at Apr 20, 95 05:12:21 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1056 Sender: current-owner@FreeBSD.org Precedence: bulk > > In message <199504201636.JAA05934@cozumel.tcs.com>, Douglas Ambrisko writes: > >Gary Palmer writes: > >Gee, sounds like time to use the new serial console mode. I've been using it > >on my server and it works great. > > OK, fine, you willing to pay BARRNET the extra money to have a second machine > on the ethernet and the extra rack space & so on? There should be no addition service provider fee from Barrnet, WC bought a 10MB/sec pipe, they should be able to put as many machines as they want on that pipe. There will be an additional 1' or so of rack space needed, which should be a $100/month add on. IMHO, what it buys WC is well worth the $100 month. > You have to remember that we don't have the bandwidth on site to site > it locally, it's at BARRNET's Stanford PoP. And your not asking for another 10MB/sec pipe, you just want 2 machines on the pipe you are already paying for. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Fri Apr 21 01:17:17 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA03082 for current-outgoing; Fri, 21 Apr 1995 01:17:17 -0700 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id BAA03067 ; Fri, 21 Apr 1995 01:17:16 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: Joe Greco cc: gpalmer@freefall.cdrom.com (Gary Palmer), current@FreeBSD.org, jkh@FreeBSD.org Subject: Re: wcarchive down In-reply-to: Your message of "Thu, 20 Apr 95 20:54:47 CDT." <9504210154.AA11730@brasil.moneng.mei.com> Date: Fri, 21 Apr 1995 01:17:15 -0700 Message-ID: <3066.798452235@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk > I guess I am not in the mood to fight to _give_ away a machine to what I > consider a worthy cause. I was hoping that people would be a little more > enthusiastic and try to come up with ways to implement SOMETHING... Sorry, please don't misunderstand - as I've already stated in an earlier message, we ARE going to implement something! It's just not something that involves a machine! We, and certainly *I*, am certainly grateful for your offer - trust me! I don't mean to be unenthusiastic, I'm just really really busy! Please don't hesitate to volunteer your hardware in the future! :-) Jordan From owner-freebsd-current Fri Apr 21 07:52:26 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA08925 for current-outgoing; Fri, 21 Apr 1995 07:52:26 -0700 Received: from utrhcs.cs.utwente.nl (utrhcs.cs.utwente.nl [130.89.10.247]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id HAA08917 for ; Fri, 21 Apr 1995 07:52:16 -0700 Received: from utis156.cs.utwente.nl by utrhcs.cs.utwente.nl (5.0/csrelayMX-SVR4_1.0/RB) id AA17407; Fri, 21 Apr 1995 16:52:10 --100 Received: by utis156.cs.utwente.nl (4.1/RBCS-1.0.1) id AA25512; Fri, 21 Apr 95 16:52:03 +0200 To: current@FreeBSD.org Subject: Fatal trap 12: page fault while in kernel mode Date: Fri, 21 Apr 1995 16:52:01 +0200 Message-Id: <25511.798475921@utis156.cs.utwente.nl> From: Andras Olah content-length: 2215 Sender: current-owner@FreeBSD.org Precedence: bulk I keep on getting these using a current kernel for about a week or two. The system usually panics when I use Netscape (and/or perhaps tcpdump?) on it. I'm not at all sure that it's really netscape, just a guess. A few days ago I made a make world on the machine without any troubles. Here's the panic message from the log and a stack trace. The machine is a 486/66MHz, 8MB mem, 340MB IDE system. The system was supped at Wed Apr 19 05:01:02 1995 and I recompiled everything. Does anybody have a clue? Andras Apr 21 16:03:54 utip007 /kernel: Apr 21 16:03:54 utip007 /kernel: Apr 21 16:03:54 utip007 /kernel: Fatal trap 12: page fault while in kernel mode Apr 21 16:03:55 utip007 /kernel: fault virtual address = 0xf037d0fa Apr 21 16:03:55 utip007 /kernel: fault code = supervisor write, page not present Apr 21 16:03:55 utip007 /kernel: instruction pointer = 0x8:0xf016992d Apr 21 16:03:55 utip007 /kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Apr 21 16:03:55 utip007 /kernel: = DPL 0, pres 1, def32 1, gran 1 Apr 21 16:03:55 utip007 /kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Apr 21 16:03:55 utip007 /kernel: current process = 256 (netscape) Apr 21 16:03:55 utip007 /kernel: interrupt mask = net Apr 21 16:03:55 utip007 /kernel: panic: from debugger Apr 21 16:03:55 utip007 /kernel: (kgdb) bt #0 0xf0165ff8 in boot () #1 0xf0113175 in panic () #2 0xf010123d in db_panic () #3 0xf0101126 in db_command (-266851596, -266852012, -267382206) #4 0xf01012a5 in db_command_loop () #5 0xf0103c28 in db_trap () #6 0xf016328a in kdb_trap (12, 0, -272630724, -266949882) #7 0xf016ad97 in trap_fatal () #8 0xf016a914 in trap_pfault () #9 0xf016a5a3 in trap () #10 0xf0163b31 in exception:calltrap (-266750324, -267546876, -264790014, 65535) #11 0xf01721c4 in if_ed:ed_get_packet () #12 0xf0171d5a in edintr () #13 0xf0164a1d in exception:Xresume9 () #14 0xf013eeae in ip_output (-263761152, 0, -263767636, 0, 0) #15 0xf0143626 in tcp_output () #16 0xf014445e in tcp_usrreq () #17 0xf011cc92 in sosend () #18 0xf0115435 in soo_write () #19 0xf01144ff in write () #20 0xf016b005 in syscall () (kgdb) From owner-freebsd-current Fri Apr 21 08:56:17 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA10041 for current-outgoing; Fri, 21 Apr 1995 08:56:17 -0700 Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.20.4]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id IAA10035 for ; Fri, 21 Apr 1995 08:56:15 -0700 Received: by brasil.moneng.mei.com (4.1/SMI-4.1) id AA12625; Fri, 21 Apr 95 10:55:03 CDT From: Joe Greco Message-Id: <9504211555.AA12625@brasil.moneng.mei.com> Subject: Re: wcarchive down (fwd) To: gpalmer@cdrom.com (Gary Palmer) Date: Fri, 21 Apr 1995 10:55:02 -0500 (CDT) Cc: bugs@ns1.win.net, current@FreeBSD.org In-Reply-To: <6711.798435190@westhill.cdrom.com> from "Gary Palmer" at Apr 20, 95 08:33:10 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 540 Sender: current-owner@FreeBSD.org Precedence: bulk > We are seriously thinking about this ourselves, but with a AC powered > cell phone rather than a conventional land-line phone. For one reason. > It may be a PoP, but running another phone line in there would be expensive, > and cell phones & access rates are dirt cheap now. So hang a modem off it too. :-) "Could be cool." ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 From owner-freebsd-current Fri Apr 21 09:23:29 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA10486 for current-outgoing; Fri, 21 Apr 1995 09:23:29 -0700 Received: from vector.eikon.e-technik.tu-muenchen.de (vector.eikon.e-technik.tu-muenchen.de [129.187.142.36]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA10395 for ; Fri, 21 Apr 1995 09:16:56 -0700 Received: (from jhs@localhost) by vector.eikon.e-technik.tu-muenchen.de (8.6.11/8.6.9) id LAA18527 for current@freebsd.org; Fri, 21 Apr 1995 11:34:18 +0200 Date: Fri, 21 Apr 1995 11:34:18 +0200 From: Julian Howard Stacey Message-Id: <199504210934.LAA18527@vector.eikon.e-technik.tu-muenchen.de> To: current@FreeBSD.org Subject: Suggest src/Makefile all: copy /usr/src/.ctm_status to /usr/obj/usr/src Sender: current-owner@FreeBSD.org Precedence: bulk I suggest we consider src/Makefile all: copying /usr/src/.ctm_status to /usr/obj/usr/src/ this would help ctm users when filing bug reports. I for instance run a single nfs mounted src, with multiple obj/ trees, the src/ was rebuilt a few days back, but the system for which I want to provide background environment info for a `ports' bug report runs from an obj at earlier patch level (& I cant remember which) I realise we don't all use ctm, I'd think we could do the same for a .mirror, & whatever for sup, & even some extract log stamp for few who do a local cvs extract, as their means of gen'ing src/ Julian S From owner-freebsd-current Fri Apr 21 09:47:58 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA10967 for current-outgoing; Fri, 21 Apr 1995 09:47:58 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id JAA10960 for ; Fri, 21 Apr 1995 09:47:55 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA03580; Fri, 21 Apr 95 10:41:21 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9504211641.AA03580@cs.weber.edu> Subject: Re: Memory init pattern To: tweten@nas.nasa.gov Date: Fri, 21 Apr 95 10:41:20 MDT Cc: brian@mediacity.com, henrich@crh.cl.msu.edu, freebsd-current@FreeBSD.org In-Reply-To: <199504210232.TAA08764@gilmore.nas.nasa.gov> from "Dave Tweten" at Apr 20, 95 07:32:29 pm X-Mailer: ELM [version 2.4dev PL52] Sender: current-owner@FreeBSD.org Precedence: bulk > > Course, CDC may not be the best precedent to follow for commercial success. > I don't think we have to worry about IBM dumping to force us out of the hardware business. 8-). Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Fri Apr 21 10:22:18 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA11706 for current-outgoing; Fri, 21 Apr 1995 10:22:18 -0700 Received: from pp2.smc.south.telia.se (pp2.smc.south.telia.se [131.116.12.194]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA11698 for ; Fri, 21 Apr 1995 10:21:59 -0700 Received: (from paul@localhost) by pp2.smc.south.telia.se (8.6.8/8.6.6) id TAA05679; Fri, 21 Apr 1995 19:28:54 +0200 Date: Fri, 21 Apr 1995 19:28:52 +0200 (MET DST) From: Paul Pries Subject: SNAP-950412: One good, one bad... To: mailing-list FreeBSD-current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk Well, now we've done it again! That is managed to install FreeBSD. :-) The first machine, a noname P-66 went smooth as ever, the only minor screwup was ncftp, but it was an easy thing to circumvent. The install program was just beautiful! Now to the bad one. I tried to install on a AST Bravo (P-90) with both IDE and SCSI. No go on either drivetype! SCSI controller is a Bt-946C, which is detected properly. Everything seems fine with the install until it is time to reboot from the harddisk when it fails miserably with some error that 'cant be reported'. Sorry I can't be more specific about the error, but if more info is needed I can pop down to work and try booting it... DOS boots fine off the damned thing, just BSD fails. I tried using a bt545 also, but that one didn't like the 3c509. Sigh. The error with the IDE is the usual 'don't like 32 heads'. This is well documented, I suppose. At least I've heard about it and know what to do about it... I really would like to get this box going, as my future net-access depends on it... :-) Thanks in advance for any hints, Paul. -- Paul Pries email: Phone: Telia AB paul@smc.south.telia.se +46 40 445108 (home) Region Syd paul@pp2.smc.south.telia.se +46 40 272671 (work) 205 21 Malmo +46 10 201 8925 (mobile) SWEDEN +46 40 974865 (fax) Any opinions that might have been expressed in the above message are mine. If you like them, you can have them too. From owner-freebsd-current Fri Apr 21 12:47:02 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA17116 for current-outgoing; Fri, 21 Apr 1995 12:47:02 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA17110 for ; Fri, 21 Apr 1995 12:46:56 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id MAA09159; Fri, 21 Apr 1995 12:37:57 -0700 From: "Rodney W. Grimes" Message-Id: <199504211937.MAA09159@gndrsh.aac.dev.com> Subject: Re: Fix for motherboards that don't reboot. To: bde@zeta.org.au (Bruce Evans) Date: Fri, 21 Apr 1995 12:37:56 -0700 (PDT) Cc: current@FreeBSD.org In-Reply-To: <199504190115.LAA15783@godzilla.zeta.org.au> from "Bruce Evans" at Apr 19, 95 11:15:30 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2172 Sender: current-owner@FreeBSD.org Precedence: bulk > > >I spent some time talking with a BIOS engineer today about the problem > >of FreeBSD not rebooting on some motherboards and have come up with > >the following patch that fixes the problem on the board I have here. > > > void > > cpu_reset() { > >+ > >+ /* Attempt to do a CPU reset via the keyboard controller */ > >+ outb(IO_KBD + 4, 0xFE); > > This is what I implemented for Minix about (sigh) 6 years ago. I found > that outputting 0xFC works better. AFAIR 0xFE strobes the CPU reset > line and 0xFC additionally strobes GateA20. Both methods worked in > protected mode on the machines that I had access to, but in real mode, > (with A20 forced to 0) several machines hung, apparently due to a bad > fetch of the first instruction after reset. The first instruction was > usually invalid and jumped to the BIOS invalid instruction handler, > which was brain damaged and looped. Trapping it with a debugger and > jumping to the correct reset vector worked. I suspect the reset worked > better in protected mode only because the invalid instruction handler > was invalid and the system eventually got reset better after a triple > fault. I have gotten back one test report on my patch, it did not work for the person and he got the: Keyboard reset did not work, attempting CPU shutdown message I put in there. I had him change the 0xFE to 0xFC and it caused a processor exception (gating A20 off without the reset occurring sent the machine to god knows where) and did not output the above message. This is clearly either a defective MB or a bad design. But given the 2 values it looks as if 0xFE is safer since it allows us to at least attempt the CPU shutdown if the reset failed. The person I got the information from about doing this says that in fact 0xFE is the better value to use (this person writes BIOS'es for a living) and is suppose to dig out the official reason for me today. Once I here from him I will be committing my patch with additional comments with the 0xFE value. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Fri Apr 21 15:44:47 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA23358 for current-outgoing; Fri, 21 Apr 1995 15:44:47 -0700 Received: from vector.eikon.e-technik.tu-muenchen.de (vector.eikon.e-technik.tu-muenchen.de [129.187.142.36]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA23299 for ; Fri, 21 Apr 1995 15:42:49 -0700 Received: (from jhs@localhost) by vector.eikon.e-technik.tu-muenchen.de (8.6.11/8.6.9) id SAA25436 for current@freebsd.org; Fri, 21 Apr 1995 18:31:13 +0200 Date: Fri, 21 Apr 1995 18:31:13 +0200 From: Julian Howard Stacey Message-Id: <199504211631.SAA25436@vector.eikon.e-technik.tu-muenchen.de> To: current@FreeBSD.org Subject: dumb Q. on sendmail Sender: current-owner@FreeBSD.org Precedence: bulk Quick dumb question ;-) I log in about every day via slip, & sendmail flushes my outgoing mail spool, (the line gets cut by the IP provider after 20 mins (shortage of lines), I don't pay, so I don't complain :-) Anyway .. my outgoing mail stacks up, sendmail build slow end to end temporary virtual circuits across the planet to deliver, this is _slow_, Ideally I'd upload to a fast local internet host, & let it sweat it out after Id hung up, lately I tried: mail foobar%freebsd.org@my-citys-ip-provider-host-name not much luck with that (can't remember why offhand) In the past I used a for loop on the remote-slip host, & invoked sendmail i-i -t there ... thats cludgy, & doesnt interface easily to mail readers etc, Is there some other obvious way I'm missing ? The only other way I can see is repetitive redial after hang up (or pay for hours of commercial IP gateway connect time) & wait while sendmail slowly does it's stuff, & the modem light barely blink PS I've got Ok8 in my sendmail.cf which says "Set connection cache size." Perhaps what I need to do is to up the no. of simultaneous sendmail slave processes to about 20 (anything else on my machine can wait ;-) PPS I've also set: # load average at which we just queue messages Ox20 # load average at which we refuse connections OX20 Julian S From owner-freebsd-current Fri Apr 21 15:57:01 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA23660 for current-outgoing; Fri, 21 Apr 1995 15:57:01 -0700 Received: from vector.eikon.e-technik.tu-muenchen.de (vector.eikon.e-technik.tu-muenchen.de [129.187.142.36]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA23440 for ; Fri, 21 Apr 1995 15:47:08 -0700 Received: from localhost (localhost [127.0.0.1]) by vector.eikon.e-technik.tu-muenchen.de (8.6.11/8.6.9) with SMTP id CAA08309; Fri, 21 Apr 1995 02:09:20 +0200 Message-Id: <199504210009.CAA08309@vector.eikon.e-technik.tu-muenchen.de> X-Authentication-Warning: vector.eikon.e-technik.tu-muenchen.de: Host localhost didn't use HELO protocol To: velte@cdrom.com, current@freefall.cdrom.com Subject: A Scenario for FreeBSD Commercial Support In-reply-to: Your message of "Wed, 19 Apr 1995 14:43:58 +0200." <18149.798295438@freefall.cdrom.com> Date: Fri, 21 Apr 1995 02:09:19 +0200 From: Julian Howard Stacey Sender: current-owner@FreeBSD.org Precedence: bulk To Jack Velte (WC Inc) & Folk On FreeBSD Current list. Jordan wrote: >Subject: Re: Minutes of the Thursday, April 13th core team meeting in Berkeley. >Support Mgr[10]: vacant (possibly PAY someone) You'd have to pay someone, I can't see anyone properly doing a full time high-availability support job for free, unless he's a millionaire who loves stress, hard work, & agravation :-) Someone with a real job or study load would not have sufficient time. FreeBSD Support could be a 24 hour/day job: - We have users spread round the planet, - Thanks to some people's interaction through Internet, & many people's copious coffee drinking, I suspect in most timezones of the world, we have users working probably 18 hours out of every 24 hours (assuming the 2am-8am period to be slack), (& not 5 but 7 days/week) Given sufficient cash, I'd suggest at least Three support people ! meta-physically living about 8 timezones apart (eg: USA, Europe & Australia/Japan)> (though 2 might be on same continent (USA ?) if (a) one worked the `graveyard shift' (b) preferably we had a few local incoming auto-divert phone numbers on each continental land mass, to establish pseudo `local' presence. Any paid support FreeBSD offered would have to make sense to whoever sponsored us to provide it. At present this means it would have to make commercial sense to Walnut Creek (currently our sole sponsor I believe). Jack Velte of WC Inc must be used to crystal ball gazing on prospective CD-ROM sales quantities versus marketing & support effort. One question for him is: If FreeBSD provided Walnut with `ready to press' CD-ROM trees every 13 weeks, could WC Inc sell sufficent CD-ROMs to pay staffing costs of (aprox) :- a few assorted support folk (mostly full time), a Release Engineeer (5 weeks in every 13 ?), a Jordan-like-jack-of-all-trades (full time), kernel-gurus-&-whoever-else-ive-missed ;-) We could boost CD-ROM sales & CD-subscriptions like this: "Yes Sir/Madam, of course the Support Desks run the latest CD release. What is the Serial number stamped on the `Free Support' sticker on your Jewel Case ?" "Sorry Sir/Madam, Walnut do not contract us to provide _free_ support for old CD-ROMS, the new one has been out longer than the 4 week changeover period, & we don't run the old software. I advise you to phone Walnut & order either the current CD (with 13 week support), or an ongoing subscription (with ongoing support), then phone me back if you have a problem with the currently valid release." "Yes Sir, you're of course free to email `hackers' & ask for help, (if you want to, if your email works), some of those guys run from CD's much older than yours, & some from much newer sources than the CD you still need to buy, just remember those guys aren't paid to help you, so be grateful if someone offers free advice for problems based on your out-of-date CD. "May I give you Walnut's Tel. Order Number ? .... Good Luck Sir" WC Inc would benefit most from offering Primary worldwide support, to solve the `Ring Ring .. Hallo ? ... Help , It won't boot !' scenario's, thus assisting sales of further CD's to friends & colleagues of folk who had initial booting problems. Later fine tuning support/consultancy is not in WC's interest to pay to support, & would cost a fortune, either the user should make a direct contract with local support personnel, or he should work on it himself, enlisting the support of our existing mail lists. I'd define Primary Support as: help in getting it to boot, & to send mail to enroll on hackers, Further `free' support (ie paid for by WC Inc) would be of less benefit to WC. Are the folks in FreeBSD agreeable to a regular 13 week release schedule, if the `grunt work' is offloaded onto paid help ? (We'd need 13 week releases to fund proper support) Would FreeBSD worry about geting over dependent on WC Inc ? I'd be interested in doing Paid support in Europe - But Not For Free !. If I were to do FreeBSD support, I'd order at least a 3rd phone line, (& perhaps a leased IP line) (fortunately I had the extra cable laid through the concrete building recently) :- 1 New line for the FreeBSD hackers who never sleep, & are likely to phone at the most inconvenient times (they have so far ;-). 1 line for fax + getty modem (serviced of course, not by a `Development' box, but by a seperate box running the latest Quarterly Release CD-ROM. 1 line for existing friends & local customers (& spare modem) (for the people one wants to hear from, even After doing a day's support work) --- Julian Stacey Tel. +49 89 268616. Fax Modem: 2608126 Vector Systems Ltd: an Internet, Unix & C systems consultancy. From owner-freebsd-current Fri Apr 21 16:14:52 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA24275 for current-outgoing; Fri, 21 Apr 1995 16:14:52 -0700 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id QAA24266 ; Fri, 21 Apr 1995 16:14:50 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: Julian Howard Stacey cc: velte@cdrom.com, current@freefall.cdrom.com Subject: Re: A Scenario for FreeBSD Commercial Support In-reply-to: Your message of "Fri, 21 Apr 95 02:09:19 +0200." <199504210009.CAA08309@vector.eikon.e-technik.tu-muenchen.de> Date: Fri, 21 Apr 1995 16:14:49 -0700 Message-ID: <24265.798506089@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk > Are the folks in FreeBSD agreeable to a regular 13 week release schedule, > if the `grunt work' is offloaded onto paid help ? (We'd need 13 week releases > to fund proper support) > Would FreeBSD worry about geting over dependent on WC Inc ? I don't much like this idea. It would essentially require the users to upgrade whether they liked it or not every 4 months if they wished to remain on the tech support rolls. What happens to the corporate shop who runs 2.3 for 7 months and likes it just fine, then they one day have a problem they can't solve with their own techs and they call us. "Sorry, you're out of date. You need to upgrade your entire shop and fix what isn't broken before we'll help you with your problem." The rule doesn't mean anything if you don't generally enforce it, and in this case you're depriving a good customer of one silly question just because their release of 2.3 worked _too well_ up to now! If someone is going to pay for tech support, I'd rather it be the FreeBSD Project, Inc. Then it could be done on a much more standard "U want it, U pay for it." kind of support contract basis. It's like insurance - most people don't mind paying for first level support if it only costs a few hundred bucks a year whether they use it actively or not. They know it's always there. I'm not sure WC itself is in the market for selling tech support, even though it's been talked about. "We make CDROMS" is what Jack tells me on a regular basis whenever some tangental business model is mentioned. Jordan From owner-freebsd-current Fri Apr 21 16:21:51 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA24690 for current-outgoing; Fri, 21 Apr 1995 16:21:51 -0700 Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.20.4]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id QAA24684 for ; Fri, 21 Apr 1995 16:21:49 -0700 Received: by brasil.moneng.mei.com (4.1/SMI-4.1) id AA13507; Fri, 21 Apr 95 18:20:54 CDT From: Joe Greco Message-Id: <9504212320.AA13507@brasil.moneng.mei.com> Subject: Re: dumb Q. on sendmail To: jhs@regent.e-technik.tu-muenchen.de (Julian Howard Stacey) Date: Fri, 21 Apr 1995 18:20:53 -0500 (CDT) Cc: current@FreeBSD.org In-Reply-To: <199504211631.SAA25436@vector.eikon.e-technik.tu-muenchen.de> from "Julian Howard Stacey" at Apr 21, 95 06:31:13 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1914 Sender: current-owner@FreeBSD.org Precedence: bulk > Quick dumb question ;-) > > I log in about every day via slip, & sendmail flushes my outgoing mail spool, > (the line gets cut by the IP provider after 20 mins (shortage of lines), > I don't pay, so I don't complain :-) > Anyway .. my outgoing mail stacks up, sendmail build slow end to end > temporary virtual circuits across the planet to deliver, this is _slow_, > > Ideally I'd upload to a fast local internet host, & let it sweat it out > after Id hung up, lately I tried: > mail foobar%freebsd.org@my-citys-ip-provider-host-name > not much luck with that (can't remember why offhand) > > In the past I used a for loop on the remote-slip host, & > invoked sendmail i-i -t there ... thats cludgy, & doesnt interface easily to > mail readers etc, > > Is there some other obvious way I'm missing ? > > The only other way I can see is repetitive redial after hang up > (or pay for hours of commercial IP gateway connect time) > & wait while sendmail slowly does it's stuff, & the modem light barely blink > > PS I've got > Ok8 > in my sendmail.cf which says "Set connection cache size." > Perhaps what I need to do is to up the no. of simultaneous sendmail slave > processes to about 20 (anything else on my machine can wait ;-) > PPS I've also set: > # load average at which we just queue messages > Ox20 > # load average at which we refuse connections > OX20 > > Julian S Actually, what you *might* want to do is to pass off all your mail to your ISP, and have their machines deal with it. All you really need to do is look at Sendmail's examples for "smarthost" delivery, where the local Sendmail mostly disregards DNS/etc. This is the fix that will probably serve you best. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 From owner-freebsd-current Fri Apr 21 16:38:37 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA24900 for current-outgoing; Fri, 21 Apr 1995 16:38:37 -0700 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA24890 for ; Fri, 21 Apr 1995 16:38:34 -0700 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id BAA03994 ; Sat, 22 Apr 1995 01:38:19 +0200 Received: from (roberto@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) id BAA14419 ; Sat, 22 Apr 1995 01:38:19 +0200 From: roberto@blaise.ibp.fr (Ollivier Robert) Message-Id: <199504212338.BAA14419@blaise.ibp.fr> Subject: Re: dumb Q. on sendmail To: jgreco@brasil.moneng.mei.com (Joe Greco) Date: Sat, 22 Apr 1995 01:38:18 +0200 (MET DST) Cc: jhs@regent.e-technik.tu-muenchen.de, current@FreeBSD.org In-Reply-To: <9504212320.AA13507@brasil.moneng.mei.com> from "Joe Greco" at Apr 21, 95 06:20:53 pm X-Operating-System: FreeBSD 2.0.950416-SNAP ctm#562 X-Mailer: ELM [version 2.4 PL23beta2] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 751 Sender: current-owner@FreeBSD.org Precedence: bulk > Actually, what you *might* want to do is to pass off all your mail to your > ISP, and have their machines deal with it. All you really need to do is > look at Sendmail's examples for "smarthost" delivery, where the local > Sendmail mostly disregards DNS/etc. This is the fix that will probably > serve you best. I think it is the best solution... define(`SMART_HOST', esmtp:[mailhost.provider.net])dnl is the parameter to use in your .mc file. Replace esmtp by smtp if the sendmail on the other side is not a 8.6.x. The [] make sendmail ignore MX records for the smart host (you don't need them). -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@FreeBSD.ORG FreeBSD keltia 2.0.950416-SNAP #17: Sun Apr 16 17:12:07 MET DST 1995 From owner-freebsd-current Fri Apr 21 19:51:58 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA29993 for current-outgoing; Fri, 21 Apr 1995 19:51:58 -0700 Received: from main.statsci.com (main.statsci.com [198.145.125.110]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id TAA29987 for ; Fri, 21 Apr 1995 19:51:51 -0700 Received: by main.statsci.com (Smail3.1.28.1 #9) id m0s2VIK-000r3rC; Fri, 21 Apr 95 19:51 PDT Message-Id: To: Julian Howard Stacey cc: current@FreeBSD.org Subject: Re: dumb Q. on sendmail In-reply-to: Your message of "Fri, 21 Apr 1995 18:31:13 +0200." <199504211631.SAA25436@vector.eikon.e-technik.tu-muenchen.de> Reply-to: scott@statsci.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 21 Apr 1995 19:50:03 -0700 From: Scott Blachowicz Sender: current-owner@FreeBSD.org Precedence: bulk > mail foobar%freebsd.org@my-citys-ip-provider-host-name > not much luck with that (can't remember why offhand) Hmmm...I would think that would work. Sounds like you could set a "smart host" to your IP provider, then just bump everything there. In 'smail' it'd be easy. It's probably easy in sendmail, too...I've used the appended sendmail.cf file (on other UNIX systems - I'm not up on FreeBSD yet) for client workstations that ALWAYS bump mail to a central mail hub. You'd need to change it so you recognize local deliveries and keep them. Or look around for mentions of "smart hosts" or whatever. Hope this helps a little. Scott Blachowicz Ph: 206/283-8802x240 StatSci, a div of MathSoft, Inc. 1700 Westlake Ave N #500 scott@statsci.com Seattle, WA USA 98109 Scott.Blachowicz@seaslug.org ---------- cut here ---------- ########################################################################### ### The simplified configuration for clients only ### ### Just sends ABSOLUT everything to the server. ### ########################################################################### # Current version DVBUMP-IT # This node's official domain name #Dj$w.uni-paderborn.de Dj$w.statsci.com ########################################################################### ### The next few lines should be carefully checked. ### ########################################################################### # Mail server. ALL mail forwarded here by TCP mailer. [n.n.n.n] is OK. #DSYourMailServerFully.Qualified.Name DSmailhost # SMTP login message De$j $v/$V Sendmail is ready at $b # queue directory OQ/usr/spool/mqueue ########################################################################## # Header Formats HReceived: $?sfrom $s $.by $j$?r with $r$. id $i ($v/$V$?m for $m$.); $b H?P?Return-Path: <$g> H?D?Date: $a H?F?From: $q H?x?Full-Name: $x H?M?Message-ID: <$t.$i@$j> ########################################################################## ## Mailer Specifications ################################################# ########################################################################## # Do nothing rule for Mailer S=/R= S10 Mlocal, P=/bin/mail, F=DFMlrmns, R=10, S=10, A=mail -d $u Mprog, P=/bin/sh, F=DFMhlsu, R=10, S=10, A=sh -c $u MTCP, P=[IPC], F=CDFMXnmu, E=\r\n, R=10, S=10, A=IPC $h # Rule Set #0: Mailer Resolving Ruleset # Just forward everything to our server. S0 R$+ $#TCP $@$S $:$1 Route most mail to server. # Rule Set #1: Nothing. S1 # Rule Set #2: Nothing. S2 # Rule Set #3: Nothing. S3 # Rule Set #4: Nothing. S4 From owner-freebsd-current Fri Apr 21 20:02:34 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA00394 for current-outgoing; Fri, 21 Apr 1995 20:02:34 -0700 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id UAA00384 ; Fri, 21 Apr 1995 20:02:29 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: Julian Howard Stacey cc: current@FreeBSD.org Subject: Re: dumb Q. on sendmail In-reply-to: Your message of "Fri, 21 Apr 95 18:31:13 +0200." <199504211631.SAA25436@vector.eikon.e-technik.tu-muenchen.de> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 21 Apr 1995 20:02:28 -0700 Message-ID: <383.798519748@freefall.cdrom.com> From: Gary Palmer (FreeBSD/ARM Team) Sender: current-owner@FreeBSD.org Precedence: bulk In message <199504211631.SAA25436@vector.eikon.e-technik.tu-muenchen.de>, Julia n Howard Stacey writes: >Ideally I'd upload to a fast local internet host, & let it sweat it out >after Id hung up, lately I tried: > mail foobar%freebsd.org@my-citys-ip-provider-host-name >not much luck with that (can't remember why offhand) Set the line : # "Smart" relay host (may be null) DSmy-citys-ip-provider-host-name That should pass *ALL* outgoing e-mail onto that machine for delivery. Gary From owner-freebsd-current Fri Apr 21 20:11:09 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA00728 for current-outgoing; Fri, 21 Apr 1995 20:11:09 -0700 Received: from psycfrnd.interaccess.com (psycfrnd.interaccess.com [198.80.0.26]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id UAA00719 for ; Fri, 21 Apr 1995 20:11:06 -0700 Received: (joeg@localhost) by psycfrnd.interaccess.com (8.6.12/8.6.10) id WAA09867; Fri, 21 Apr 1995 22:08:40 -0500 From: Joe Grosch Message-Id: <199504220308.WAA09867@psycfrnd.interaccess.com> Subject: Re: A Scenario for FreeBSD Commercial Support To: jkh@freefall.cdrom.com (Jordan K. Hubbard) Date: Fri, 21 Apr 1995 22:08:39 -0500 (CDT) Cc: current@FreeBSD.org Reply-To: joeg@truenorth.org In-Reply-To: <24265.798506089@freefall.cdrom.com> from "Jordan K. Hubbard" at Apr 21, 95 04:14:49 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 2363 Sender: current-owner@FreeBSD.org Precedence: bulk > >> Are the folks in FreeBSD agreeable to a regular 13 week release schedule, >> if the `grunt work' is offloaded onto paid help ? (We'd need 13 week releases >> to fund proper support) >> Would FreeBSD worry about geting over dependent on WC Inc ? > >I don't much like this idea. It would essentially require the users >to upgrade whether they liked it or not every 4 months if they wished >to remain on the tech support rolls. What happens to the corporate >shop who runs 2.3 for 7 months and likes it just fine, then they one >day have a problem they can't solve with their own techs and they call >us. "Sorry, you're out of date. You need to upgrade your entire shop >and fix what isn't broken before we'll help you with your problem." > Agree. One of the first rules I learned in this trade is never to upgrade the OS durning a project unless the upgrade fixes a number of very bad bugs, i.e. the kernel panics several times a day. Forcing clients to upgrade when it's convenient for us or because we have a new release is not going to endear us to them. >The rule doesn't mean anything if you don't generally enforce it, and >in this case you're depriving a good customer of one silly question >just because their release of 2.3 worked _too well_ up to now! > >If someone is going to pay for tech support, I'd rather it be the >FreeBSD Project, Inc. Then it could be done on a much more standard >"U want it, U pay for it." kind of support contract basis. It's like >insurance - most people don't mind paying for first level support if >it only costs a few hundred bucks a year whether they use it actively >or not. They know it's always there. > At the risk of sounding like a heretic, might I recommend we try what the FSF does, provide a list of consultants and/or companys that will support FreeBSD for a fee. This list would not be an endorsement by FreeBSD Inc, or FooBar Inc, or what ever we are calling our organazation. These would just be people know to us. >I'm not sure WC itself is in the market for selling tech support, even >though it's been talked about. "We make CDROMS" is what Jack tells me >on a regular basis whenever some tangental business model is >mentioned. > Josef -- Josef Grosch | joeg@truenorth.org | "Laugh while you can, monkey boy." finger for my | - Buckaroo Banzai - public PGP key | From owner-freebsd-current Sat Apr 22 06:40:50 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA22935 for current-outgoing; Sat, 22 Apr 1995 06:40:50 -0700 Received: from aries.ibms.sinica.edu.tw ([140.109.40.248]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id GAA22929 for ; Sat, 22 Apr 1995 06:40:43 -0700 Received: (from taob@localhost) by aries.ibms.sinica.edu.tw (8.6.11/8.6.9) id VAA15459; Sat, 22 Apr 1995 21:41:06 +0800 Date: Sat, 22 Apr 1995 21:41:05 +0800 (CST) From: Brian Tao To: FREEBSD-CURRENT-L Subject: Fixing /dev entries (was Re: wcarchive down ) In-Reply-To: <14719.798423020@freefall.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk On Thu, 20 Apr 1995, Gary Palmer wrote: > > We tried to put 3 new Quantum Grand Prix drives onto a Adaptec 174x SCSI > card. Pity that the Adaptec cards have a problem talking to the drives > or something and the SCSI bus just kept locking up. This somehow forced > the system to spam the entries for /dev/*sd0*. This meant that we > couldn't even remount the drive read-write to correct the /dev entries. If someone had physical access, would the solution be as simple as mounting the drive with the root filesystem on another FreeBSD machine, re-doing the /dev entries and then replacing the drive? I'm thinking ahead in case it ever happens to any of the machines here. -- Brian ("Though this be madness, yet there is method in't") Tao taob@gate.sinica.edu.tw <-- work ........ play --> taob@io.org From owner-freebsd-current Sat Apr 22 07:58:07 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA24569 for current-outgoing; Sat, 22 Apr 1995 07:58:07 -0700 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id HAA24561 ; Sat, 22 Apr 1995 07:58:05 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: Brian Tao cc: FREEBSD-CURRENT-L Subject: Re: Fixing /dev entries (was Re: wcarchive down ) In-reply-to: Your message of "Sat, 22 Apr 95 21:41:05 +0800." MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 22 Apr 1995 07:58:05 -0700 Message-ID: <24560.798562685@freefall.cdrom.com> From: Gary Palmer (FreeBSD/ARM Team) Sender: current-owner@FreeBSD.org Precedence: bulk In message , Brian Tao writes: > If someone had physical access, would the solution be as simple as >mounting the drive with the root filesystem on another FreeBSD >machine, re-doing the /dev entries and then replacing the drive? I'm >thinking ahead in case it ever happens to any of the machines here. If the /dev/*sd* entries were the only things affected, then yes. But when we ran fsck on the drive a lot of the files normally considered non-optional for a root filesystem bit the dust. It's either a complete re-install or a upgrade to 2.x I'm not sure if anyone has fgured out what exactly happened yet, I'm not at all sure and I was there watching this happen :-( Gary From owner-freebsd-current Sat Apr 22 08:35:56 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA25394 for current-outgoing; Sat, 22 Apr 1995 08:35:56 -0700 Received: from aries.ibms.sinica.edu.tw ([140.109.40.248]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA25365 ; Sat, 22 Apr 1995 08:35:36 -0700 Received: (from taob@localhost) by aries.ibms.sinica.edu.tw (8.6.11/8.6.9) id XAA16965; Sat, 22 Apr 1995 23:34:43 +0800 Date: Sat, 22 Apr 1995 23:34:42 +0800 (CST) From: Brian Tao To: Ching Shih cc: bugs@FreeBSD.org, current@FreeBSD.org Subject: Re: some comments on the 2.0 and 3.1.1 In-Reply-To: <9504191637.AA19889@cithe312.cithep.caltech.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk On Wed, 19 Apr 1995, Ching Shih wrote: > > 2.0 + 3.1: working, except no X for ATI Mach64, > and not working for 2940+1080s The AHA-2940 wasn't supported until recently, and you really should run XFree86 3.1.1 and the patchlevel 2 Mach64 server. > 2.0-950322-SNAP + 3.1.1: cannot make it work for ATI Mach64, > even XF_SVGA doesn't work for my ATI Mach64 Works just dandy with 950322 and still works great under 950412. This is a Mach64 Graphics Pro Turbo (not the Winturbo or Graphics Expression or some OEM model). -- Brian ("Though this be madness, yet there is method in't") Tao taob@gate.sinica.edu.tw <-- work ........ play --> taob@io.org From owner-freebsd-current Sat Apr 22 14:11:17 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA02310 for current-outgoing; Sat, 22 Apr 1995 14:11:17 -0700 Received: from devnull.mpd.tandem.com (devnull.mpd.tandem.com [131.124.4.29]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA02304 for ; Sat, 22 Apr 1995 14:11:16 -0700 Received: from olympus by devnull.mpd.tandem.com (8.6.8/8.6.6) id QAA04794; Sat, 22 Apr 1995 16:11:00 -0500 Received: by olympus (4.1/TSS2.1) id AA03643; Sat, 22 Apr 95 16:09:20 CDT From: faulkner@mpd.tandem.com (Boyd Faulkner) Message-Id: <9504222109.AA03643@olympus> Subject: Re: cvs commit: /host/freefall/a/ncvs/ports/ To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Sat, 22 Apr 1995 16:09:20 -0500 (CDT) Cc: current@FreeBSD.org In-Reply-To: <199504221733.KAA01908@gndrsh.aac.dev.com> from "Rodney W. Grimes" at Apr 22, 95 10:33:37 am X-Mailer: ELM [version 2.4 PL17] Content-Type: text Content-Length: 1090 Sender: current-owner@FreeBSD.org Precedence: bulk Rod, My 486 PCI Asus Box boots FreeBSD current great... but the latest snap boot floppy and the fixit disk do not. Everthing is cool until the PCI is found. Apr 22 15:05:09 catburg /kernel: Probing for devices on the pci0 bus: Apr 22 15:05:10 catburg /kernel: configuration mode 2 allows 16 devices. Apr 22 15:05:10 catburg /kernel: chip0 rev 4 on pci0:0 Apr 22 15:05:10 catburg /kernel: ncr0 rev 2 int a irq 9 on pci 0:1 Apr 22 15:05:10 catburg /kernel: reg20: virtual=0xf2fe9000 physical=0xfbf ef000 size=0x100 Up to here life is good, but the following never happens from floppy. Apr 22 15:05:10 catburg /kernel: ncr0: restart (scsi reset). Apr 22 15:05:10 catburg /kernel: ncr0 scanning for targets 0..6 (V2 pl21 95/03/21) I have waited over a minute. Seen this before? Boyd -- _______________________________________________________________________ Boyd Faulkner faulkner@isd.tandem.com _______________________________________________________________________ From owner-freebsd-current Sat Apr 22 14:27:11 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA03699 for current-outgoing; Sat, 22 Apr 1995 14:27:11 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA03693 for ; Sat, 22 Apr 1995 14:27:08 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id OAA02464; Sat, 22 Apr 1995 14:24:25 -0700 From: "Rodney W. Grimes" Message-Id: <199504222124.OAA02464@gndrsh.aac.dev.com> Subject: Re: cvs commit: /host/freefall/a/ncvs/ports/ To: faulkner@mpd.tandem.com (Boyd Faulkner) Date: Sat, 22 Apr 1995 14:24:24 -0700 (PDT) Cc: current@FreeBSD.org In-Reply-To: <9504222109.AA03643@olympus> from "Boyd Faulkner" at Apr 22, 95 04:09:20 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1500 Sender: current-owner@FreeBSD.org Precedence: bulk > > Rod, > My 486 PCI Asus Box boots FreeBSD current great... but the latest snap > boot floppy and the fixit disk do not. Everthing is cool until the PCI > is found. > > Apr 22 15:05:09 catburg /kernel: Probing for devices on the pci0 bus: > Apr 22 15:05:10 catburg /kernel: configuration mode 2 allows 16 devices. > Apr 22 15:05:10 catburg /kernel: chip0 > rev 4 on pci0:0 > Apr 22 15:05:10 catburg /kernel: ncr0 rev 2 int a irq 9 on > pci 0:1 > Apr 22 15:05:10 catburg /kernel: reg20: virtual=0xf2fe9000 > physical=0xfbf ef000 size=0x100 > > Up to here life is good, but the following never happens from floppy. > > Apr 22 15:05:10 catburg /kernel: ncr0: restart (scsi reset). > Apr 22 15:05:10 catburg /kernel: ncr0 scanning for targets 0..6 > (V2 pl21 95/03/21) > > I have waited over a minute. > > Seen this before? No I have not, but then I don't run the SNAP shots as it is easier for me to build my own releases here and do disk to disk installs using ``make DESTDIR=/newroot'' install. I will down load the latest snap boot floppies and take a look at what they do on my 5 PCI test systems. I currently don't have a ASUS PCI/I-486SP3G on site, but could pull one in on monday easily. (And probably going to have to anyway for other reasons). -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Sat Apr 22 15:32:23 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA05498 for current-outgoing; Sat, 22 Apr 1995 15:32:23 -0700 Received: from FileServ1.MI.Uni-Koeln.DE (FileServ1.MI.Uni-Koeln.DE [134.95.212.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id PAA05492 for ; Sat, 22 Apr 1995 15:32:19 -0700 Received: by FileServ1.MI.Uni-Koeln.DE id AA28723 (5.67b/IDA-1.5 for current@freebsd.org); Sun, 23 Apr 1995 00:31:55 +0200 Message-Id: <199504222231.AA28723@FileServ1.MI.Uni-Koeln.DE> From: se@MI.Uni-Koeln.DE (Stefan Esser) Date: Sun, 23 Apr 1995 00:31:55 +0200 In-Reply-To: faulkner@mpd.tandem.com (Boyd Faulkner) "Re: cvs commit: /host/freefall/a/ncvs/ports/" (Apr 22, 16:09) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: faulkner@mpd.tandem.com (Boyd Faulkner) Subject: Re: cvs commit: /host/freefall/a/ncvs/ports/ Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk On Apr 22, 16:09, Boyd Faulkner wrote: } Subject: Re: cvs commit: /host/freefall/a/ncvs/ports/ } Rod, } My 486 PCI Asus Box boots FreeBSD current great... but the latest snap } boot floppy and the fixit disk do not. Everthing is cool until the PCI } is found. } } Apr 22 15:05:09 catburg /kernel: Probing for devices on the pci0 bus: } Apr 22 15:05:10 catburg /kernel: configuration mode 2 allows 16 devices. } Apr 22 15:05:10 catburg /kernel: chip0 } rev 4 on pci0:0 } Apr 22 15:05:10 catburg /kernel: ncr0 rev 2 int a irq 9 on } pci 0:1 } Apr 22 15:05:10 catburg /kernel: reg20: virtual=0xf2fe9000 } physical=0xfbf ef000 size=0x100 } } Up to here life is good, but the following never happens from floppy. } } Apr 22 15:05:10 catburg /kernel: ncr0: restart (scsi reset). } Apr 22 15:05:10 catburg /kernel: ncr0 scanning for targets 0..6 } (V2 pl21 95/03/21) No, sorry, haven't ... I just booted the SNAP floppies on my SP3G, and everything seems fine. Regards, STefan -- Stefan Esser Internet: Zentrum fuer Paralleles Rechnen Tel: +49 221 4706019 Universitaet zu Koeln FAX: +49 221 4705160 Weyertal 80 50931 Koeln From owner-freebsd-current Sat Apr 22 20:31:09 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA12390 for current-outgoing; Sat, 22 Apr 1995 20:31:09 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id UAA12384 for ; Sat, 22 Apr 1995 20:31:08 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA10199; Sat, 22 Apr 95 21:24:30 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9504230324.AA10199@cs.weber.edu> Subject: Re: Fixing /dev entries (was Re: wcarchive down ) To: gpalmer@freefall.cdrom.com (Gary Palmer) Date: Sat, 22 Apr 95 21:24:30 MDT Cc: taob@gate.sinica.edu.tw, freebsd-current@FreeBSD.org In-Reply-To: <24560.798562685@freefall.cdrom.com> from "Gary Palmer" at Apr 22, 95 07:58:05 am X-Mailer: ELM [version 2.4dev PL52] Sender: current-owner@FreeBSD.org Precedence: bulk > > If someone had physical access, would the solution be as simple as > >mounting the drive with the root filesystem on another FreeBSD > >machine, re-doing the /dev entries and then replacing the drive? I'm > >thinking ahead in case it ever happens to any of the machines here. > > If the /dev/*sd* entries were the only things affected, then yes. But when > we ran fsck on the drive a lot of the files normally considered non-optional > for a root filesystem bit the dust. It's either a complete re-install or > a upgrade to 2.x > > I'm not sure if anyone has fgured out what exactly happened yet, I'm > not at all sure and I was there watching this happen :-( There is still a nice hole for all you truck-drivers. The bdwrite for ffs_update() probably ought to be a bwrite if the inode being updated is a directory. I think it's possible that "current directories" for apps can ge corrupted by virtue of the inode being dirty for the access times. An explicit reading of POSIX allows you to treat a directory as if it were not a file, and only (synchronously!) update times on getdents (VOP_READDIR). I fixed this problem on UnixWare about a year ago, and was hard pressed to cause unreferenced files while flipping the power off during stress testing (before the fix, this would inevitably end up with crap in the lost+found directory). Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Sat Apr 22 23:54:05 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA14736 for current-outgoing; Sat, 22 Apr 1995 23:54:05 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA14730 for ; Sat, 22 Apr 1995 23:54:02 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id XAA03319; Sat, 22 Apr 1995 23:51:19 -0700 From: "Rodney W. Grimes" Message-Id: <199504230651.XAA03319@gndrsh.aac.dev.com> Subject: Re: Problem booting SNAP floppy on PCI/I-486SP3G To: faulkner@mpd.tandem.com (Boyd Faulkner) Date: Sat, 22 Apr 1995 23:51:19 -0700 (PDT) Cc: current@FreeBSD.org In-Reply-To: <9504222109.AA03643@olympus> from "Boyd Faulkner" at Apr 22, 95 04:09:20 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1383 Sender: current-owner@FreeBSD.org Precedence: bulk > > Rod, > My 486 PCI Asus Box boots FreeBSD current great... but the latest snap > boot floppy and the fixit disk do not. Everthing is cool until the PCI > is found. > > Apr 22 15:05:09 catburg /kernel: Probing for devices on the pci0 bus: > Apr 22 15:05:10 catburg /kernel: configuration mode 2 allows 16 devices. > Apr 22 15:05:10 catburg /kernel: chip0 > rev 4 on pci0:0 > Apr 22 15:05:10 catburg /kernel: ncr0 rev 2 int a irq 9 on > pci 0:1 > Apr 22 15:05:10 catburg /kernel: reg20: virtual=0xf2fe9000 > physical=0xfbf ef000 size=0x100 > > Up to here life is good, but the following never happens from floppy. > > Apr 22 15:05:10 catburg /kernel: ncr0: restart (scsi reset). > Apr 22 15:05:10 catburg /kernel: ncr0 scanning for targets 0..6 > (V2 pl21 95/03/21) > > I have waited over a minute. > > Seen this before? I tried all my boards here, and every one of them works. I will bring in a PCI/I-486SP3G this week and see if I can track this down. You mention that this works with a -current kernel, what happens if you put that kernel on floppy? Or if you copy the floppy kernel to hard disk as /kernel.flp and try to boot it? -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD