From owner-freebsd-current Sun Jul 21 00:51:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA19102 for current-outgoing; Sun, 21 Jul 1996 00:51:27 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA19095 for ; Sun, 21 Jul 1996 00:51:23 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA15223; Sun, 21 Jul 1996 09:51:08 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA07454; Sun, 21 Jul 1996 09:51:08 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id JAA05208; Sun, 21 Jul 1996 09:44:57 +0200 (MET DST) From: J Wunsch Message-Id: <199607210744.JAA05208@uriah.heep.sax.de> Subject: Re: cu(1) stopped working? To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 21 Jul 1996 09:44:56 +0200 (MET DST) Cc: nordquis@visi.com (Brent J. Nordquist) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <01BB768F.78EB2D60@undquirt.visi.com> from "Brent J. Nordquist" at "Jul 20, 96 11:01:56 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Brent J. Nordquist wrote: > Suddenly in the latest sup of -current (Jul. 18) cu reports "Device > not configured" and that it's locked, but there are no lock files (I > can't believe it's really in use). Snooping around in /etc, I found > that /etc/uucp was changed by the make world. Has cu always been > part of Taylor UUCP (as noted in the man page), or have we suddenly > switched cu's? Or, has something else changed very recently having > to do with cu? cu has been the Taylor version for very long now, and it always (erroneously) installs the template files in /etc/uucp from a `make world'. They all end up in .sample however, und thus should not conflict with the actual configuration files. The entire UUCP suite never broke for me by this (neither cu nor uucico), and i'm relying exclusively on UUCP for all my mail and news. > And yes, I have been meaning to switch to tip anyway... looks like > now is the time. Just wanted everyone to have my one data point on > this. Do you have any reason to switch to tip? I find the Taylor config files much more intelligible than all the /etc/remote etc. stuff. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Jul 21 00:54:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA19344 for current-outgoing; Sun, 21 Jul 1996 00:54:39 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA19331; Sun, 21 Jul 1996 00:54:34 -0700 (PDT) Received: from critter.tfs.com (localhost.dk.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id JAA00753; Sun, 21 Jul 1996 09:54:24 +0200 (MET DST) To: davidg@root.com cc: "Michael L. VanLoon -- HeadCandy.com" , John Dyson , hsu@clinet.fi (Heikki Suonsivu), freebsd-current@freebsd.org Subject: Re: vm work helps In-reply-to: Your message of "Sat, 20 Jul 1996 19:24:47 PDT." <199607210224.TAA16881@root.com> Date: Sun, 21 Jul 1996 09:54:23 +0200 Message-ID: <751.837935663@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Just a wild guess: The vop_bmap() code in it is probably broken. We rely >heavily on this and if it's broken, the filesystem will be corrupted. NetBSD >won't suffer from this because they have much more limited use of the vop_bmap >function. Further guessing, I'd guess that the problem is that CCD doesn't >limit the forward/behind contiguousness to be within the underlying device's >cluster, or something of this nature. Sort of my conclusion too, but I'd be damned if I can find out where the problem is. Havn't spent more than one hour though. It is actually an interesting thing to think about. I guess our clustering code should communicate four block#'s downward: First block that could be any use First block that is strictly needed Last block that is strictly needed Last block that would be any use. And then ccd could select chop between these boundaries to match entire stripes. I doubt we'd gain much though :-) -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Sun Jul 21 01:52:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA21600 for current-outgoing; Sun, 21 Jul 1996 01:52:05 -0700 (PDT) Received: from hermes.algonet.se (mail.algonet.se [193.12.207.206]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA21584 for ; Sun, 21 Jul 1996 01:51:59 -0700 (PDT) Received: from (johang@sophocles.algonet.se [193.12.207.10]) by hermes.algonet.se (8.7.4/hdw.1.0) with SMTP id KAA03520 for ; Sun, 21 Jul 1996 10:52:22 +0200 (MET DST) Message-Id: <199607210852.KAA03520@hermes.algonet.se> Comments: Authenticated sender is From: "Johan Granlund" To: freebsd-current@freebsd.org Date: Sun, 21 Jul 1996 11:47:56 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Still problems with if_ep ? Priority: normal X-mailer: Pegasus Mail for Windows (v2.33) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Some time ago we got a problem with the ep driver. since then a couple of changes has been made. As of yesterday i still get "no buffer space available" and have to do a ifconfig ep0 down/up to get it running again :-) Intel endevour motherboard Adaptec 2940 uw 3c509 (Isa not PnP) /Johan ___________________________________________________________ Internet: Johang@Algonet.se I don't even speak for myself From owner-freebsd-current Sun Jul 21 02:09:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA22133 for current-outgoing; Sun, 21 Jul 1996 02:09:12 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA22121 for ; Sun, 21 Jul 1996 02:09:09 -0700 (PDT) Received: (from richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) id CAA19785; Sun, 21 Jul 1996 02:09:25 -0700 Date: Sun, 21 Jul 1996 02:09:23 -0700 (PDT) From: Veggy Vinny To: Joerg Wunsch cc: FreeBSD-current users Subject: Re: /usr/bin/passwd and finger output In-Reply-To: <199607200720.JAA03329@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 20 Jul 1996, J Wunsch wrote: > As Veggy Vinny wrote: > > > You're right about this one except I logged in as user vince then > > su to root so then I su -l dennis and then did the passwd, this used to > > work in -current as of 1.5 weeks ago but is there anyway around this? > > It should never have worked this way. If you verify the CVS file, > you'll notice that it used getlogin() all the time to obtain the > identity of the login user. > > As i wrote, i think this is in error, and it should use getuid. This > has other ill side-effects however, for cases where you've got more > than one user with the same UID. > > The optimal way would be perhaps to use getlogin(), but fall back to > getuid() in case the login user has a different UID than the current > user. Hmmm, okay... Just don't know why it worked then... Vince From owner-freebsd-current Sun Jul 21 02:23:32 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA24076 for current-outgoing; Sun, 21 Jul 1996 02:23:32 -0700 (PDT) Received: from wgrobez1.remote.louisville.edu (root@wgrobez1.remote.louisville.edu [136.165.243.183]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA24046 for ; Sun, 21 Jul 1996 02:23:26 -0700 (PDT) Received: from localhost (wangel@localhost) by wgrobez1.remote.louisville.edu (8.7.5/8.6.12) with SMTP id FAA02171 for ; Sun, 21 Jul 1996 05:23:28 -0400 (EDT) Date: Sun, 21 Jul 1996 05:23:27 -0400 (EDT) From: spazboy-whq To: freebsd-current@freebsd.org Subject: Linux Emu. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has anyone succesfully gotten Quake to run in FreeBSD-Current with the linux emu ? Thanks From owner-freebsd-current Sun Jul 21 03:04:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA26216 for current-outgoing; Sun, 21 Jul 1996 03:04:47 -0700 (PDT) Received: from dworshak.cs.uidaho.edu (dworshak.cs.uidaho.edu [129.101.100.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA26211 for ; Sun, 21 Jul 1996 03:04:45 -0700 (PDT) Received: from waldrog.cs.uidaho.edu (waldrog.cs.uidaho.edu [129.101.100.23]) by dworshak.cs.uidaho.edu (8.7.5/1.1) with ESMTP id DAA19297; Sun, 21 Jul 1996 03:04:43 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by waldrog.cs.uidaho.edu (8.7.5/1.0) with SMTP id DAA15547; Sun, 21 Jul 1996 03:04:43 -0700 (PDT) X-Authentication-Warning: waldrog.cs.uidaho.edu: Host localhost [127.0.0.1] didn't use HELO protocol To: spazboy-whq cc: freebsd-current@freebsd.org Subject: Re: Linux Emu. In-reply-to: Your message of "Sun, 21 Jul 1996 05:23:27 PDT." Date: Sun, 21 Jul 1996 03:04:42 PDT Message-ID: <15545.837943482@waldrog.cs.uidaho.edu> From: faried nawaz Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk spazboy-whq wrote... Has anyone succesfully gotten Quake to run in FreeBSD-Current with the linux emu ? I ran linux_qtest1 fine a few days ago on -current (as of July 3rd). From owner-freebsd-current Sun Jul 21 03:21:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA26781 for current-outgoing; Sun, 21 Jul 1996 03:21:06 -0700 (PDT) Received: from wgrobez1.remote.louisville.edu (root@wgrobez1.remote.louisville.edu [136.165.243.183]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA26776 for ; Sun, 21 Jul 1996 03:21:02 -0700 (PDT) Received: from localhost (wangel@localhost) by wgrobez1.remote.louisville.edu (8.7.5/8.6.12) with SMTP id GAA02370 for ; Sun, 21 Jul 1996 06:21:06 -0400 (EDT) Date: Sun, 21 Jul 1996 06:21:05 -0400 (EDT) From: Gary Roberts To: freebsd-current@freebsd.org Subject: Re: Linux Emu. In-Reply-To: <15545.837943482@waldrog.cs.uidaho.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 21 Jul 1996, faried nawaz wrote: > spazboy-whq wrote... > > Has anyone succesfully gotten Quake to run in FreeBSD-Current with the > linux emu ? > > I ran linux_qtest1 fine a few days ago on -current (as of July 3rd). > > Well, I'll try that I suppose .... I was looking forward to getting Quake .91 or 1.01 to work. It starts to load but then core dumps ... I was wondering if I need to do some kernel tweeking or what not ? ... Also, if it helps, Doom doesn't work either -- it loads, then bombs out with a broken pipe and when trying to reload, it yells about shared mem or something. Thanks From owner-freebsd-current Sun Jul 21 05:40:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA29743 for current-outgoing; Sun, 21 Jul 1996 05:40:33 -0700 (PDT) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA29738 for ; Sun, 21 Jul 1996 05:40:31 -0700 (PDT) Received: from localhost.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.7.5/8.7.3) with SMTP id IAA21730; Sun, 21 Jul 1996 08:40:14 -0400 (EDT) Message-Id: <199607211240.IAA21730@whizzo.transsys.com> X-Authentication-Warning: whizzo.transsys.com: Host localhost.transsys.com [127.0.0.1] didn't use HELO protocol To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-current@freebsd.org From: "Louis A. Mamakos" Subject: Re: cu(1) stopped working? References: <199607210744.JAA05208@uriah.heep.sax.de> In-reply-to: Your message of "Sun, 21 Jul 1996 09:44:56 +0200." <199607210744.JAA05208@uriah.heep.sax.de> Date: Sun, 21 Jul 1996 08:40:14 -0400 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > And yes, I have been meaning to switch to tip anyway... looks like > > now is the time. Just wanted everyone to have my one data point on > > this. > > Do you have any reason to switch to tip? I find the Taylor config > files much more intelligible than all the /etc/remote etc. stuff. It's pretty suprising, since we all "know" that tip and cu have both used /etc/remote for years. In fact, the tip(1) man page even covers cu, which furthers confusion for the unsuspecting UNIX user. louie From owner-freebsd-current Sun Jul 21 06:01:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA00422 for current-outgoing; Sun, 21 Jul 1996 06:01:59 -0700 (PDT) Received: from spooky.eis.net.au (root@spooky.eis.net.au [203.12.171.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA00414 for ; Sun, 21 Jul 1996 06:01:52 -0700 (PDT) Received: (from ernie@localhost) by spooky.eis.net.au (8.7.5/8.6.12) id WAA23057 for freebsd-current@freebsd.org; Sun, 21 Jul 1996 22:59:53 +1000 (EST) From: Ernie Elu Message-Id: <199607211259.WAA23057@spooky.eis.net.au> Subject: Adding drives with sysinstall To: freebsd-current@freebsd.org Date: Sun, 21 Jul 1996 22:59:52 +1000 (EST) X-Mailer: ELM [version 2.4ME+ PL15 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am trying to use sysinstall to add a second hard disk as per the freebsd-faq, as I find using disklabel manually confusing. I select Expres mode, create the partition with fdisk, write it out then quit. That bit is fine, then sysinstall pops me into disklabel where I create just one new partition the size of the drive (sd1s1) with a mount point of /usr/ports. When I select w to write to disk then hit return to say yes, sysinstall puts up a dialog " Copying initail device files.." Segmentation fault (core dumped) According to the FAQ you are meant to be able to press q to exit after doing the write to disk, this is not the case. The sysinstall is compiled from a fresh sup of -current today. - Ernie. From owner-freebsd-current Sun Jul 21 06:18:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA00925 for current-outgoing; Sun, 21 Jul 1996 06:18:16 -0700 (PDT) Received: from dworshak.cs.uidaho.edu (dworshak.cs.uidaho.edu [129.101.100.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA00920 for ; Sun, 21 Jul 1996 06:18:14 -0700 (PDT) Received: from waldrog.cs.uidaho.edu (waldrog.cs.uidaho.edu [129.101.100.23]) by dworshak.cs.uidaho.edu (8.7.5/1.1) with ESMTP id GAA19444; Sun, 21 Jul 1996 06:18:12 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by waldrog.cs.uidaho.edu (8.7.5/1.0) with SMTP id GAA15607; Sun, 21 Jul 1996 06:18:12 -0700 (PDT) X-Authentication-Warning: waldrog.cs.uidaho.edu: Host localhost [127.0.0.1] didn't use HELO protocol To: Gary Roberts cc: freebsd-current@freebsd.org Subject: Re: Linux Emu. In-reply-to: Your message of "Sun, 21 Jul 1996 06:21:05 PDT." Date: Sun, 21 Jul 1996 06:18:11 PDT Message-ID: <15605.837955091@waldrog.cs.uidaho.edu> From: faried nawaz Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Gary Roberts wrote... Well, I'll try that I suppose .... I was looking forward to getting Quake .91 or 1.01 to work. It starts to load but then core dumps ... I was wondering if I need to do some kernel tweeking or what not ? ... Also, if it helps, Doom doesn't work either -- it loads, then bombs out with a broken pipe and when trying to reload, it yells about shared mem or something. Where can one find quake 1.x for Linux? I couldn't find it...would very much like to be able to play that! I had trouble with doom as well; some complaint about shlibs (can't recall the exact error & have deleted it off my system). From owner-freebsd-current Sun Jul 21 08:18:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA08712 for current-outgoing; Sun, 21 Jul 1996 08:18:08 -0700 (PDT) Received: from relay-5.mail.demon.net (relay-5.mail.demon.net [158.152.1.48]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA08700 for ; Sun, 21 Jul 1996 08:18:02 -0700 (PDT) Received: from post.demon.co.uk by relay-5.mail.demon.net id am26675; 21 Jul 96 16:12 +0100 Received: from jraynard.demon.co.uk ([158.152.42.77]) by relay-3.mail.demon.net id aa28232; 21 Jul 96 15:24 +0100 Received: (from fcurrent@localhost) by jraynard.demon.co.uk (8.7.5/8.6.12) id MAA00718; Sun, 21 Jul 1996 12:30:11 GMT From: James Raynard Message-Id: <199607211230.MAA00718@jraynard.demon.co.uk> Subject: Re: missed SIGALRM To: Adam David Date: Sun, 21 Jul 1996 12:30:11 +0000 () Cc: freebsd-current@freebsd.org In-Reply-To: <199607202348.XAA06918@veda.is> from "Adam David" at Jul 20, 96 11:48:22 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I have noticed that a SIGALRM can sometimes be missed altogether under certain > conditions, perhaps as a side-effect of heavy machine load. I am looking into > this problem, and any other datapoints/suggestions are welcome. The following > program (in its more complete version) stops doing its stuff once in a while > (typically once a day or more often) and needs to be restarted as a result. > The likelihood of this occuring seems related to periods of heavy system load. Your code is vulnerable to race conditions - when the machine is heavily loaded, there may be gaps of more than one second between the times when the program is scheduled to run. Hence a SIGALRM may occur when you are in the middle of one of these function calls, leaving data (in this case tick) in an inconsistent state. Here's my suggestion (based on one of the examples in "Advanced Programming in the Unix Environment" by W. Richard Stevens). The tick variable is a sig_atomic_t type, rather than a plain int, to guarantee that writes to it will not be interrupted. The sigprocmask() function is used to block SIGALRM signals until we're ready to handle them; sigsuspend() temporarily sets the signal mask to the one before we called sigprocmask() and waits for a signal and waits for a signal to occur. When one does, the mask is reset to the one set by sigprocmask(), so that we can call get_tick() and set_tick() without having to worry about another SIGALRM occuring during the function calls. Finally, we call sigprocmask() to reset the original signal mask (not really necessary here, but a good habit to get into). #include #include #include volatile sig_atomic_t tick; void handler(int signo) { tick = 1; } void set_tick(void) { tick = 0; alarm(1); } int get_tick(void) { return tick; } int main(void) { sigset_t newmask, oldmask; if (signal(SIGALRM, handler) == SIG_ERR) perror("signal"); sigemptyset(&newmask); sigaddset(&newmask, SIGALRM); if (sigprocmask(SIG_BLOCK, &newmask, &oldmask) < 0) perror("sigprocmask"); set_tick(); for (;;) { while (get_tick() == 0) sigsuspend(&oldmask); /* do stuff */ set_tick(); } if (sigprocmask(SIG_SETMASK, &oldmask, NULL) < 0) perror("sigprocmask"); return 0; } From owner-freebsd-current Sun Jul 21 08:21:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA09171 for current-outgoing; Sun, 21 Jul 1996 08:21:41 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA09164 for ; Sun, 21 Jul 1996 08:21:35 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id RAA25881; Sun, 21 Jul 1996 17:21:05 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id RAA11176; Sun, 21 Jul 1996 17:21:05 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id PAA06413; Sun, 21 Jul 1996 15:00:36 +0200 (MET DST) From: J Wunsch Message-Id: <199607211300.PAA06413@uriah.heep.sax.de> Subject: Re: cu(1) stopped working? To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 21 Jul 1996 15:00:36 +0200 (MET DST) Cc: louie@TransSys.COM (Louis A. Mamakos) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199607211240.IAA21730@whizzo.transsys.com> from "Louis A. Mamakos" at "Jul 21, 96 08:40:14 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Louis A. Mamakos wrote: > It's pretty suprising, since we all "know" that tip and cu have both > used /etc/remote for years. Yes, lacking something better. ;-) We decided that the Taylor version is much more powerful (even more than the HDB UUCP version), and stopped aliasing tip(1) to cu before FreeBSD 2.0.5. > In fact, the tip(1) man page even covers > cu, which furthers confusion for the unsuspecting UNIX user. This should be removed. However, ``man cu'' yields the correct man page. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Jul 21 10:13:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA16645 for current-outgoing; Sun, 21 Jul 1996 10:13:56 -0700 (PDT) Received: from precipice.shockwave.com (ppp-5-79.rdcy01.pacbell.net [206.170.5.79]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA16627; Sun, 21 Jul 1996 10:13:51 -0700 (PDT) Received: from shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.7.5/8.7.3) with ESMTP id KAA00268; Sun, 21 Jul 1996 10:13:10 -0700 (PDT) Message-Id: <199607211713.KAA00268@precipice.shockwave.com> To: current@freebsd.org, hackers@freebsd.org cc: wollman@freebsd.org Subject: tcp w/SACK Date: Sun, 21 Jul 1996 10:13:09 -0700 From: Paul Traina Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has anyone else already signed up for tcp w/SACK porting into FreeBSD? It looks like the NetBSD code should be available soon. As soon as it settles down, I was thinking of merging it in. From owner-freebsd-current Sun Jul 21 10:14:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA16725 for current-outgoing; Sun, 21 Jul 1996 10:14:33 -0700 (PDT) Received: from precipice.shockwave.com (ppp-5-79.rdcy01.pacbell.net [206.170.5.79]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA16720; Sun, 21 Jul 1996 10:14:31 -0700 (PDT) Received: from shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.7.5/8.7.3) with ESMTP id KAA00277; Sun, 21 Jul 1996 10:13:53 -0700 (PDT) Message-Id: <199607211713.KAA00277@precipice.shockwave.com> To: hackers@freebsd.org, current@freebsd.org Subject: anyone working on upgrading the msdosfs to NetBSD levels? Date: Sun, 21 Jul 1996 10:13:53 -0700 From: Paul Traina Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk From owner-freebsd-current Sun Jul 21 10:50:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA18068 for current-outgoing; Sun, 21 Jul 1996 10:50:29 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA18063 for ; Sun, 21 Jul 1996 10:50:27 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id KAA15780; Sun, 21 Jul 1996 10:49:50 -0700 (PDT) To: Ernie Elu cc: freebsd-current@FreeBSD.org Subject: Re: Adding drives with sysinstall In-reply-to: Your message of "Sun, 21 Jul 1996 22:59:52 +1000." <199607211259.WAA23057@spooky.eis.net.au> Date: Sun, 21 Jul 1996 10:49:50 -0700 Message-ID: <15778.837971390@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hmmmm. I'll put together a test box and try this out. Jordan > I am trying to use sysinstall to add a second hard disk as per the > freebsd-faq, as I find using disklabel manually confusing. > > I select Expres mode, create the partition with fdisk, write it out then > quit. That bit is fine, then sysinstall pops me into disklabel where I create > just one new partition the size of the drive (sd1s1) with a mount point of > /usr/ports. > > When I select w to write to disk then hit return to say yes, sysinstall puts > up a dialog " Copying initail device files.." Segmentation fault (core dumped ) > > According to the FAQ you are meant to be able to press q to exit > after doing the write to disk, this is not the case. > > The sysinstall is compiled from a fresh sup of -current today. > > - Ernie. From owner-freebsd-current Sun Jul 21 11:14:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA18826 for current-outgoing; Sun, 21 Jul 1996 11:14:43 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA18821; Sun, 21 Jul 1996 11:14:41 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id LAA15909; Sun, 21 Jul 1996 11:14:10 -0700 (PDT) To: Paul Traina cc: hackers@freebsd.org, current@freebsd.org Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? In-reply-to: Your message of "Sun, 21 Jul 1996 10:13:53 PDT." <199607211713.KAA00277@precipice.shockwave.com> Date: Sun, 21 Jul 1996 11:14:10 -0700 Message-ID: <15906.837972850@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I think Robert Nordier is working on a complete re-write, actually. How's that going, Robert? Jordan From owner-freebsd-current Sun Jul 21 11:25:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA19280 for current-outgoing; Sun, 21 Jul 1996 11:25:02 -0700 (PDT) Received: from apocalypse.superlink.net (root@apocalypse.superlink.net [205.246.27.150]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA19267 for ; Sun, 21 Jul 1996 11:24:58 -0700 (PDT) Received: (from marxx@localhost) by apocalypse.superlink.net (8.7.5/8.7.3) id VAA19567; Mon, 22 Jul 1996 21:34:30 -0400 (EDT) Date: Mon, 22 Jul 1996 21:34:29 -0400 (EDT) From: "Charles C. Figueiredo" To: current@freebsd.org Subject: Make world Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, my make worlds are failing with: cd /usr/src && make cleandir ===> include usage: rm [-f | -i] [-dPRr] file ... *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. I thought maybe it was a typo in the makefile, but I didn't find any. Any idea what's wrong? Charles ------------------------------------------------------------------------------ Charles C. Figueiredo CCF13 marxx@doomsday.org ------------------------------------------------------------------------------ From owner-freebsd-current Sun Jul 21 13:06:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA22958 for current-outgoing; Sun, 21 Jul 1996 13:06:41 -0700 (PDT) Received: from relay-5.mail.demon.net (relay-5.mail.demon.net [158.152.1.48]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA22949 for ; Sun, 21 Jul 1996 13:06:38 -0700 (PDT) Received: from post.demon.co.uk by relay-5.mail.demon.net id bd04469; 21 Jul 96 20:40 +0100 Received: from jraynard.demon.co.uk ([158.152.42.77]) by relay-3.mail.demon.net id aa20197; 21 Jul 96 20:37 +0100 Received: (from fcurrent@localhost) by jraynard.demon.co.uk (8.7.5/8.6.12) id OAA01402; Sun, 21 Jul 1996 14:44:23 GMT From: James Raynard Message-Id: <199607211444.OAA01402@jraynard.demon.co.uk> Subject: Re: Adding drives with sysinstall To: Ernie Elu Date: Sun, 21 Jul 1996 14:44:22 +0000 () Cc: freebsd-current@freebsd.org In-Reply-To: <199607211259.WAA23057@spooky.eis.net.au> from "Ernie Elu" at Jul 21, 96 10:59:52 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I am trying to use sysinstall to add a second hard disk as per the > freebsd-faq, as I find using disklabel manually confusing. > > I select Expres mode, create the partition with fdisk, write it out then > quit. That bit is fine, then sysinstall pops me into disklabel where I create > just one new partition the size of the drive (sd1s1) with a mount point of > /usr/ports. > > When I select w to write to disk then hit return to say yes, sysinstall puts > up a dialog " Copying initail device files.." Segmentation fault (core dumped) > > According to the FAQ you are meant to be able to press q to exit > after doing the write to disk, this is not the case. Hmm. I wrote that FAQ entry based on some experimenting I did with -current's sysinstall of about a month ago (or perhaps even 2.1.0's sysinstall, I forget now). Anyway, the sysinstall that's now in -current (and presumably in 2.1.5) has a command-line option that allows you to add a new disk and bale out gracefully. Unfortunately I don't have any space to 'make release' here (nor do I have a second disk any more), but I think the relevant possibilities are:- sysinstall diskPartitionEditor sysinstall diskPartitionWrite sysinstall diskLabelEditor sysinstall diskLabelCommit (or sysinstall -fake ... for testing purposes) Can someone with the appropriate hardware, time and bravery try this out for me and I'll update the FAQ entry? Thanks! From owner-freebsd-current Sun Jul 21 13:37:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA26151 for current-outgoing; Sun, 21 Jul 1996 13:37:41 -0700 (PDT) Received: from gargoyle.bazzle.com ([206.103.246.190]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA26095 for ; Sun, 21 Jul 1996 13:37:17 -0700 (PDT) Received: from localhost (ejc@localhost) by gargoyle.bazzle.com (8.7.5/8.6.12) with SMTP id QAA03476; Sun, 21 Jul 1996 16:35:13 -0400 (EDT) Date: Sun, 21 Jul 1996 16:35:13 -0400 (EDT) From: "Eric J. Chet" To: "Charles C. Figueiredo" cc: current@freebsd.org Subject: Re: Make world In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > my make worlds are failing with: > cd /usr/src && make cleandir > ===> include > usage: rm [-f | -i] [-dPRr] file ... > *** Error code 1 Hello I just completed a make world of -current today(july 21) without any problems. Check your src tree. Eric J. Chet - ejc@bazzle.com - Powered by FreeBSD | Live Free or Die Lucent Technologies, Bell Labs Innovations | UNIX Columbus, OH 43213 RM 1D246s ejc@nasvr1.cb.lucent.com | Bell Labs > Charles C. Figueiredo CCF13 marxx@doomsday.org > ------------------------------------------------------------------------------ > From owner-freebsd-current Sun Jul 21 14:30:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA28829 for current-outgoing; Sun, 21 Jul 1996 14:30:41 -0700 (PDT) Received: from vector.jhs.no_domain (slip139-92-42-153.ut.nl.ibm.net [139.92.42.153]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA28786; Sun, 21 Jul 1996 14:29:59 -0700 (PDT) Received: from vector.jhs.no_domain (localhost [127.0.0.1]) by vector.jhs.no_domain (8.7.5/8.6.9) with ESMTP id TAA07244; Sun, 21 Jul 1996 19:37:47 +0200 (MET DST) Message-Id: <199607211737.TAA07244@vector.jhs.no_domain> To: "Michael L. VanLoon -- HeadCandy.com" cc: current@freebsd.org Subject: Re: Opinions? NT VS UNIX, NT SUCKS SOMETIMES From: "Julian H. Stacey" Reply-To: "Julian H. Stacey" Organization: Vector Systems Ltd. Address: Holz Strasse 27d, 80469 Munich, Germany Phone: +49.89.268616 Fax: +49.89.2608126 (later) Web: http://www.freebsd.org/~jhs/ Mailer: EXMH 1.6.7, PGP available In-reply-to: Your message of "Fri, 19 Jul 1996 22:10:02 PDT." <199607200510.WAC20472@MindBender.HeadCandy.com> Date: Sun, 21 Jul 1996 19:37:46 +0200 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Aaaargh ! Current@ != Hackers@ !!!! Using current@freebsd.org for the thread Subject: Re. Opinions? NT VS UNIX, NT SUCKS SOMETIMES is an Abuse of the current@ list. The thread has no specific `current src/' matters to justify it being in current@ rather than hackers@ Not all current@ readers are readers of hackers@ (self included, to avoid the traffic noise ). _Please_ do this: echo info freebsd_current | mail majordomo@freebsd.org echo info freebsd_hackers | mail majordomo@freebsd.org echo info freebsd_chat | mail majordomo@freebsd.org & in future initiate & cc posts to the _correct_ list. Posting off-topic thread(s) to current & asking people to manually adjust their cc: to chat@ does not work, & causes noise. _Dont_ post to current, unless it complies with stated purpose for current@ Just because one uses current/ does Not mean all one's FreeBSD related posts should be dumped on to current@ ..... use hackers@ Please. Thanks. Julian -- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ From owner-freebsd-current Sun Jul 21 16:24:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA02624 for current-outgoing; Sun, 21 Jul 1996 16:24:38 -0700 (PDT) Received: from prozac.neuron.net (prozac.neuron.net [165.254.1.213]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA02618 for ; Sun, 21 Jul 1996 16:24:33 -0700 (PDT) Received: (from amir@localhost) by prozac.neuron.net (8.7.5/8.6.12) id TAA00588 for freebsd-current@freebsd.org; Sun, 21 Jul 1996 19:35:06 -0400 (EDT) From: "Amir Y. Rosenblatt" Message-Id: <199607212335.TAA00588@prozac.neuron.net> Subject: SCSI errors and repeated panics To: freebsd-current@freebsd.org Date: Sun, 21 Jul 1996 19:35:06 -0400 (EDT) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk A short while ago I started getting massive numbers of SCSI erros (to be shown below) followed by kernel panics. It's happenbed 3 times in the last hour. Only once did it drop me to ddb (output included below). First off my hardware and software configuration is as follows: Intel P120 on an ASUS motherboard 64 meg RAM Adaptec 2940UW hooked up to the following: - On the 68-pin cable, a pair of ST32550W 2.1 gig 'cudas (sd0 and sd1, with SCSI ID's 0 and 1 in that order). - On the 50-pin cable, an an HP C1533A DAT drive and an NEC MultiSpin 4V CD-ROM drive (SCSI IDs 3 and 2 in that order). The chain is terminated on one end by the second 'cudah and on the other with the CD-ROM drive. A 3Com 3c509-TP An ATI Mach64 video card. It's running 2.2-061296-SNAP system binaries with a kernel compiled from -current as of June 10th. The following is from /var/log/messages -- these messages were all repeated several dozen times with each crash -- this is just to give a sampling. ---------------[Begin Included Text]------------------- Jul 21 18:17:56 prozac /kernel: sd0(ahc0:0:0): timed out in dataout phase, SCSIS IGI == 0x0 Jul 21 18:17:56 prozac /kernel: sd0(ahc0:0:0): timed out in dataout phase, SCSIS IGI == 0x0 Jul 21 18:17:57 prozac /kernel: ahc0: Issued Channel A Bus Reset #2. 2 SCBs aborted Jul 21 18:17:57 prozac /kernel: ahc0: Issued Channel A Bus Reset #2. 2 SCBs aborted Jul 21 18:17:57 prozac /kernel: :2 Jul 21 18:17:57 prozac /kernel: :2 Jul 21 18:17:57 prozac /kernel: sd0(ahc0:0:0): NOT READY asc:4,1 Jul 21 18:17:57 prozac /kernel: sd0(ahc0:0:0): Logical unit is in process of becoming ready field replaceable unit: 2 Jul 21 18:17:57 prozac /kernel: sd0(ahc0:0:0): Logical unit is in process of becoming ready field replaceable unit: 2 Jul 21 18:17:57 prozac /kernel: , retries:1 Jul 21 18:17:57 prozac /kernel: , retries:1 Jul 21 18:17:58 prozac /kernel: sd0(ahc0:0:0): NOT READY asc:4,1 Jul 21 18:17:58 prozac /kernel: sd0(ahc0:0:0): NOT READY asc:4,1 Jul 21 18:17:58 prozac /kernel: sd0(ahc0:0:0): Logical unit is in process of becoming ready field replaceable unit: 2 Jul 21 18:17:58 prozac /kernel: sd0(ahc0:0:0): Logical unit is in process of becoming ready field replaceable unit: 2 Jul 21 18:17:58 prozac /kernel: , FAILURE Jul 21 18:17:58 prozac /kernel: , FAILURE Jul 21 18:17:58 prozac /kernel: sd0(ahc0:0:0): NOT READY asc:4,1 Jul 21 18:17:58 prozac /kernel: sd0(ahc0:0:0): NOT READY asc:4,1 Jul 21 18:17:58 prozac /kernel: sd0(ahc0:0:0): Logical unit is in process of becoming ready field replaceable unit: 2 [etc...] Jul 21 18:18:00 prozac /kernel: , retries:1 Jul 21 18:18:00 prozac /kernel: , retries:1 Jul 21 18:18:16 prozac /kernel: sd1(ahc0:1:0): UNIT ATTENTION asc:29,0 Jul 21 18:18:16 prozac /kernel: sd1(ahc0:1:0): UNIT ATTENTION asc:29,0 Jul 21 18:18:16 prozac /kernel: sd1(ahc0:1:0): Power on, reset, or bus device reset occurred field replaceable unit: 1 Jul 21 18:18:16 prozac /kernel: sd1(ahc0:1:0): Power on, reset, or bus device reset occurred field replaceable unit: 1 Jul 21 18:18:16 prozac /kernel: , retries:4 Jul 21 18:18:16 prozac /kernel: , retries:4 Jul 21 18:24:35 prozac /kernel: mode = 0100600, inum = 23192, fs = /var Jul 21 18:24:35 prozac /kernel: mode = 0100600, inum = 23192, fs = /var Jul 21 18:24:36 prozac /kernel: panic: ffs_valloc: dup alloc Jul 21 18:24:36 prozac /kernel: panic: ffs_valloc: dup alloc Jul 21 18:24:36 prozac /kernel: Jul 21 18:24:36 prozac /kernel: Jul 21 18:24:36 prozac /kernel: syncing disks... 11 11 6 FreeBSD 2.2-CURRENT #0: Mon Jul 15 22:23:14 EDT 1996 Jul 21 18:24:36 prozac /kernel: syncing disks... 11 11 6 FreeBSD 2.2-CURRENT #0: Mon Jul 15 22:23:14 EDT 1996 [then during bootup] Jul 21 18:24:39 prozac /kernel: cd0(ahc0:2:0): CD-ROM Jul 21 18:24:39 prozac /kernel: cd0(ahc0:2:0): CD-ROM Jul 21 18:24:39 prozac /kernel: cd0(ahc0:2:0): NOT READY asc:4,0 Jul 21 18:24:39 prozac /kernel: cd0(ahc0:2:0): NOT READY asc:4,0 Jul 21 18:24:39 prozac /kernel: cd0(ahc0:2:0): Logical unit not ready, cause not reportable Jul 21 18:24:39 prozac /kernel: cd0(ahc0:2:0): Logical unit not ready, cause not reportable Jul 21 18:24:39 prozac /kernel: can't get the size Jul 21 18:24:39 prozac /kernel: can't get the size ----------------[End Included Text]-------------------- The third time it hosed itself it dropped into the debugger. Here's what it aaid: spec_getpages: I/O read error vm_fault: pager input (probably hardware) error, PID 243 failure Fatatl trap 12: page fault while in kernel mode fault virtual address = 0x80accd0 fault code = supervisor read, page not present instruction pointer = 0x8:0xf0108877 stack pointer = 0x10:0xefbffde0 frame pointer = 0x10:0xefbffe0c 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 = 243 (tcsh) interrupt mask = kernel: type 12 trap, code=0 Stopped at exec_aout_imgact + 0x17: movl 0(%esi), %edx Incidentally, I had a vm panic last week that I posted about to the list as well. Don't know if there's a connection. As it moved toward the 4th panic (I was watching the SCSI error messages pop up on screen, I waited till the disk activity paused, then shut it down, removed the cover and cranked up the air conditioner in the room all the way. Let it sit for 15 minutes, closed it back up and brought it back online. It's been bahaving fine so far since then. I got these errors once before, last week, when I installed the CD-ROM drive and forgot to adjust the termination appropriately on the SCSI chain. Fixing the termination setup, however put an end to those problems. I suppose it might just be an issue of internal cooling -- it's a full-height tower case with a fan in the lower froint sucking air in and one in the upper rear pushing it out. There's no airflow directly over the disks, but I did seperate each of them from everything else (including each other) by an ampty half-height bay worth of space. Any suggestions would be greatly appreciated. Thank you. -Amir From owner-freebsd-current Sun Jul 21 17:05:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA04518 for current-outgoing; Sun, 21 Jul 1996 17:05:44 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA04513; Sun, 21 Jul 1996 17:05:42 -0700 (PDT) Message-Id: <199607220005.RAA04513@freefall.freebsd.org> To: "Amir Y. Rosenblatt" cc: freebsd-current@freebsd.org Subject: Re: SCSI errors and repeated panics In-reply-to: Your message of "Sun, 21 Jul 1996 19:35:06 EDT." <199607212335.TAA00588@prozac.neuron.net> Date: Sun, 21 Jul 1996 17:05:42 -0700 From: "Justin T. Gibbs" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >A short while ago I started getting massive numbers of SCSI erros (to be >shown below) followed by kernel panics. It's happenbed 3 times in the >last hour. Only once did it drop me to ddb (output included below). Upgrade your kernel. This bug was fixed on June 8th in revision 1.41 of sys/dev/aic7xxx/aic7xxx.seq. I think you must have just missed this change with the last SUP you did of current. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Sun Jul 21 18:47:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA07898 for current-outgoing; Sun, 21 Jul 1996 18:47:59 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA07893 for ; Sun, 21 Jul 1996 18:47:55 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id SAA12945; Sun, 21 Jul 1996 18:47:38 -0700 From: "Rodney W. Grimes" Message-Id: <199607220147.SAA12945@GndRsh.aac.dev.com> Subject: Re: SCSI errors and repeated panics To: amir@neuron.net (Amir Y. Rosenblatt) Date: Sun, 21 Jul 1996 18:47:38 -0700 (PDT) Cc: freebsd-current@freebsd.org In-Reply-To: <199607212335.TAA00588@prozac.neuron.net> from "Amir Y. Rosenblatt" at "Jul 21, 96 07:35:06 pm" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > A short while ago I started getting massive numbers of SCSI erros (to be > shown below) followed by kernel panics. It's happenbed 3 times in the > last hour. Only once did it drop me to ddb (output included below). > > First off my hardware and software configuration is as follows: > Intel P120 on an ASUS motherboard > 64 meg RAM > Adaptec 2940UW hooked up to the following: > - On the 68-pin cable, a pair of ST32550W 2.1 gig 'cudas (sd0 and > sd1, with SCSI ID's 0 and 1 in that order). > - On the 50-pin cable, an an HP C1533A DAT drive and an NEC > MultiSpin 4V CD-ROM drive (SCSI IDs 3 and 2 in that order). > The chain is terminated on one end by the second 'cudah and on > the other with the CD-ROM drive. I see justin replied about a kernel bug, but thought I might mention that you did not complete the scsi bus termination description: The upper 8 bits are terminated on the 2940UW, if not you have a miss termination on the data<7-15> signals of the scsi bus, please check your SCSI-Select BIOS settings. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Sun Jul 21 21:31:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA14085 for current-outgoing; Sun, 21 Jul 1996 21:31:39 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.eu.org [193.56.58.253]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA14080 for ; Sun, 21 Jul 1996 21:31:36 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.eu.org [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id GAA03784; Mon, 22 Jul 1996 06:31:29 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id GAA17386; Mon, 22 Jul 1996 06:31:13 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.Alpha.5/keltia-uucp-2.8) id CAA01211; Mon, 22 Jul 1996 02:43:00 +0200 (MET DST) Message-Id: <199607220043.CAA01211@keltia.freenix.fr> Date: Mon, 22 Jul 1996 02:43:00 +0200 From: roberto@keltia.freenix.fr (Ollivier Robert) To: marxx@doomsday.org (Charles C. Figueiredo) Cc: current@freebsd.org Subject: Re: Make world In-Reply-To: ; from Charles C. Figueiredo on Jul 22, 1996 21:34:29 -0400 References: X-Mailer: Mutt 0.37 Mime-Version: 1.0 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to Charles C. Figueiredo: > I thought maybe it was a typo in the makefile, but I didn't find any. > Any idea what's wrong? I think it is the make bootstrapping problem... cd /usr/src/usr.bin/make make depend all install cd /usr/src make world -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #16: Sun Jul 21 13:26:53 MET DST 1996 From owner-freebsd-current Sun Jul 21 22:34:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA16191 for current-outgoing; Sun, 21 Jul 1996 22:34:51 -0700 (PDT) Received: from precipice.shockwave.com (ppp-5-51.rdcy01.pacbell.net [206.170.5.51]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA16176; Sun, 21 Jul 1996 22:34:48 -0700 (PDT) Received: from shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.7.5/8.7.3) with ESMTP id WAA03617; Sun, 21 Jul 1996 22:34:04 -0700 (PDT) Message-Id: <199607220534.WAA03617@precipice.shockwave.com> To: "Jordan K. Hubbard" cc: hackers@freebsd.org, current@freebsd.org Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? In-reply-to: Your message of "Sun, 21 Jul 1996 11:14:10 PDT." <15906.837972850@time.cdrom.com> Date: Sun, 21 Jul 1996 22:34:02 -0700 From: Paul Traina Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Do we -need- a complete rewrite? It looks like the current NetBSD version is actually in pretty damn good shape. Unfortunately, detangling changes is not going to be bloody easy (). Paul From: "Jordan K. Hubbard" Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? I think Robert Nordier is working on a complete re-write, actually. How's that going, Robert? Jordan From owner-freebsd-current Sun Jul 21 22:49:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA17439 for current-outgoing; Sun, 21 Jul 1996 22:49:57 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA17432; Sun, 21 Jul 1996 22:49:55 -0700 (PDT) Received: (from richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) id WAA05746; Sun, 21 Jul 1996 22:50:27 -0700 Date: Sun, 21 Jul 1996 22:50:25 -0700 (PDT) From: Veggy Vinny To: current@freebsd.org, questions@freebsd.org Subject: bootstrap Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi everyone, How do I regenerate the bootstrap for the FreeBSD partition? Thanks. P.S. I'm using -current.. Vince From owner-freebsd-current Sun Jul 21 23:28:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA19604 for current-outgoing; Sun, 21 Jul 1996 23:28:46 -0700 (PDT) Received: from meno.uchicago.edu (meno.uchicago.edu [128.135.21.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA19599 for ; Sun, 21 Jul 1996 23:28:44 -0700 (PDT) Received: from meno.uchicago.edu (localhost [127.0.0.1]) by meno.uchicago.edu (8.7.5/8.7.3) with ESMTP id BAA13190; Mon, 22 Jul 1996 01:30:44 -0500 (CDT) Message-Id: <199607220630.BAA13190@meno.uchicago.edu> To: "Charles C. Figueiredo" cc: current@freebsd.org, spfarrel@midway.uchicago.edu Subject: Re: Make world In-reply-to: Your message of "Mon, 22 Jul 1996 21:34:29 EDT." MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <13186.838017040.1@meno.uchicago.edu> Date: Mon, 22 Jul 1996 01:30:40 -0500 From: steve farrell Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk i thought i was going to tear my hair out over this same problem... and then one day it dissappeared. it think it was with my last sup, where i noticed the makefiles (/usr/src/share/mk/*) seemed to have been redone. (the problem, incidentally, is that it had stuff like (this is out of memory): @if test -d ${SOMEVARIABLE}; then \ rm -rf ${SOMEVARIABLE} which seems fine, but if you look at the behavoir or test, it seems rather unexpected... bash$ if test -d; then echo hi; fi hi i would have thought that the directory would return false, but it returns true... =(. so this is what happens in the makefile: bash$: rm -rf usage: rm [-f | -i] [-dPRr] file ... anyway, taking a glance at then new bsd.mk.obj, make cleanobj (the routine that was causing this problem) has been cleaned up to: rm -f -r ${.CURDIR}/${__objdir} anyway, this all seemed rather odd to me b/c i couldn't believe that -current was that broken... i knew there had to be a way around it ( i tried changing my /bin/sh, which i usually keep as a static bash, for example) but never found one besides most heinous hacking of the makefile. oh well.. it's fixed now =). --steve farrell > > > Hi, > > my make worlds are failing with: >cd /usr/src && make cleandir >===> include >usage: rm [-f | -i] [-dPRr] file ... >*** Error code 1 > >Stop. >*** Error code 1 > >Stop. >*** Error code 1 > >Stop. > > I thought maybe it was a typo in the makefile, but I didn't find any. >Any idea what's wrong? > >Charles > > >------------------------------------------------------------------------------ >Charles C. Figueiredo CCF13 marxx@doomsday.org >------------------------------------------------------------------------------ > From owner-freebsd-current Sun Jul 21 23:51:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA20330 for current-outgoing; Sun, 21 Jul 1996 23:51:04 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA20324; Sun, 21 Jul 1996 23:51:00 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id IAA19690; Mon, 22 Jul 1996 08:50:57 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA22909; Mon, 22 Jul 1996 08:50:56 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id IAA04045; Mon, 22 Jul 1996 08:24:22 +0200 (MET DST) From: J Wunsch Message-Id: <199607220624.IAA04045@uriah.heep.sax.de> Subject: Re: bootstrap To: richardc@CSUA.Berkeley.EDU (Veggy Vinny) Date: Mon, 22 Jul 1996 08:24:21 +0200 (MET DST) Cc: current@FreeBSD.ORG, questions@FreeBSD.ORG Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Veggy Vinny at "Jul 21, 96 10:50:25 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Veggy Vinny wrote: > How do I regenerate the bootstrap for the FreeBSD partition? Thanks. > P.S. I'm using -current.. disklabel -B sd0 (But you certainly meant ``FreeBSD slice'', right? :) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Jul 21 23:58:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA20788 for current-outgoing; Sun, 21 Jul 1996 23:58:35 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA20783; Sun, 21 Jul 1996 23:58:33 -0700 (PDT) Received: (from richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) id XAA08666; Sun, 21 Jul 1996 23:58:36 -0700 Date: Sun, 21 Jul 1996 23:58:35 -0700 (PDT) From: Veggy Vinny To: Joerg Wunsch cc: current@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: bootstrap In-Reply-To: <199607220624.IAA04045@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Jul 1996, J Wunsch wrote: > As Veggy Vinny wrote: > > > How do I regenerate the bootstrap for the FreeBSD partition? Thanks. > > P.S. I'm using -current.. > > disklabel -B sd0 > > (But you certainly meant ``FreeBSD slice'', right? :) Yeah, probably... :) Does the bootstrap work on an EIDE LBA FreeBSD slice in -current? Vince From owner-freebsd-current Mon Jul 22 00:21:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA22720 for current-outgoing; Mon, 22 Jul 1996 00:21:38 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA22706; Mon, 22 Jul 1996 00:21:33 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id AAA02406; Mon, 22 Jul 1996 00:21:27 -0700 (PDT) To: Paul Traina cc: hackers@freebsd.org, current@freebsd.org Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? In-reply-to: Your message of "Sun, 21 Jul 1996 22:34:02 PDT." <199607220534.WAA03617@precipice.shockwave.com> Date: Mon, 22 Jul 1996 00:21:27 -0700 Message-ID: <2404.838020087@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Do we -need- a complete rewrite? It looks like the current NetBSD version Well, the last person to look at it concluded that it was a steaming heap of bits, so I'm just going by his opinion. In the final analysis, be it NetBSD's code or a complete rewrite, it's still down to whomever's willing to do the work anyway.. Jordan From owner-freebsd-current Mon Jul 22 00:35:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA24184 for current-outgoing; Mon, 22 Jul 1996 00:35:21 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA24178 for ; Mon, 22 Jul 1996 00:35:17 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id RAA09746; Mon, 22 Jul 1996 17:30:45 +1000 Date: Mon, 22 Jul 1996 17:30:45 +1000 From: Bruce Evans Message-Id: <199607220730.RAA09746@godzilla.zeta.org.au> To: marxx@doomsday.org, spfarrel@midway.uchicago.edu Subject: Re: Make world Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >(the problem, incidentally, is that it had stuff like (this is out of >memory): > > @if test -d ${SOMEVARIABLE}; then \ > rm -rf ${SOMEVARIABLE} > >which seems fine, but if you look at the behavoir or test, it seems >rather unexpected... > > bash$ if test -d; then echo hi; fi > hi > >i would have thought that the directory would return false, but >it returns true... =(. so this is what happens in the makefile: FreeBSD still has the bug that the empty pathname means the current directory. Thus `test -d ""' exits with status 0. `test -d' with no args is completely different. For some reason it isn't a syntax error, and it exits with status 0 here although I have fixed the empty pathname bug. Bruce From owner-freebsd-current Mon Jul 22 00:35:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA24234 for current-outgoing; Mon, 22 Jul 1996 00:35:38 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA24205; Mon, 22 Jul 1996 00:35:34 -0700 (PDT) Received: from localhost (scrappy@localhost) by ki.net (8.7.5/8.7.5) with SMTP id DAA00374; Mon, 22 Jul 1996 03:35:31 -0400 (EDT) Date: Mon, 22 Jul 1996 03:35:31 -0400 (EDT) From: "Marc G. Fournier" Reply-To: "Marc G. Fournier" To: current@freebsd.org, stable@freebsd.org Subject: ncr53c810 driver in stable/current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi... for the second time today, my -stable machine has crashed, and hung while trying to reboot. the machine is using an ncr53c810 SCSI controller (the ASUS PC-200(sp?)) is the only SCSI controller in the box.... Now, I can live with the crashes, for now, but the fact that it is hanging on reboots is becoming a royal pain... The last time I reported this, someone made mention that the cause was the NCR driver not switching modes or something like that, so that it can't dump core...? If anyone remembers this thread, or knows what the hell I'm talking about...has this been fixed in -current? I've disabled savecore/dumpdev in /etc/sysconfig now, in the hopes that since it isn't setup to dump core, it won't try too...is this a correct assumption? thanks... Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Mon Jul 22 00:52:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA24820 for current-outgoing; Mon, 22 Jul 1996 00:52:34 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA24814; Mon, 22 Jul 1996 00:52:32 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id AAA10622; Mon, 22 Jul 1996 00:51:21 -0700 (PDT) Message-Id: <199607220751.AAA10622@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Paul Traina cc: "Jordan K. Hubbard" , hackers@freebsd.org, current@freebsd.org Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? In-reply-to: Your message of "Sun, 21 Jul 1996 22:34:02 PDT." <199607220534.WAA03617@precipice.shockwave.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 22 Jul 1996 00:51:21 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Do we -need- a complete rewrite? It looks like the current NetBSD version >is actually in pretty damn good shape. We obviously have very different opinions about what "damn good shape" means. While the NetBSD version on the whole has likely been better maintained and has fewer bugs, it also appears to lack some important fixes that we have in our version. In any case, the msdosfs code in both FreeBSD and NetBSD reminds me of a festering sore, and in my opinion, should be rewritten. It's going to take far more than just a few patches to make it 'better'. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Mon Jul 22 01:04:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA25280 for current-outgoing; Mon, 22 Jul 1996 01:04:01 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA25264; Mon, 22 Jul 1996 01:03:53 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id BAA10665; Mon, 22 Jul 1996 01:03:56 -0700 (PDT) Message-Id: <199607220803.BAA10665@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: "Marc G. Fournier" cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: ncr53c810 driver in stable/current In-reply-to: Your message of "Mon, 22 Jul 1996 03:35:31 EDT." From: David Greenman Reply-To: dg@root.com Date: Mon, 22 Jul 1996 01:03:56 -0700 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > for the second time today, my -stable machine has crashed, >and hung while trying to reboot. the machine is using an ncr53c810 >SCSI controller (the ASUS PC-200(sp?)) is the only SCSI controller >in the box.... > > Now, I can live with the crashes, for now, but the fact that >it is hanging on reboots is becoming a royal pain... > > The last time I reported this, someone made mention that >the cause was the NCR driver not switching modes or something like >that, so that it can't dump core...? > > If anyone remembers this thread, or knows what the hell I'm >talking about...has this been fixed in -current? We've seen this problem on freefall (which uses the NCR controller). It likes to hang when we try to reboot it. I don't recall any fixes for this, and I don't know what causes it. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Mon Jul 22 01:39:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA26948 for current-outgoing; Mon, 22 Jul 1996 01:39:55 -0700 (PDT) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA26941 for ; Mon, 22 Jul 1996 01:39:50 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.7.5/8.6.9) with SMTP id JAA20454 for ; Mon, 22 Jul 1996 09:47:44 +0100 (BST) Date: Mon, 22 Jul 1996 09:47:43 +0100 (BST) From: Developer To: freebsd-current@freebsd.org Subject: Termcap problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I`m having a little problem with the termcap. If the xwindow width is particular sizes (Not sure which ones, but always larger than 80 char) then commands (like ls) think the window width is different (wider) than it actually is, and so the formatting really messes up. Any ideas would be great. Regards, Trefor S. From owner-freebsd-current Mon Jul 22 02:25:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA28765 for current-outgoing; Mon, 22 Jul 1996 02:25:50 -0700 (PDT) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA28758 for ; Mon, 22 Jul 1996 02:25:42 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.7.5/8.6.9) with SMTP id KAA20911 for ; Mon, 22 Jul 1996 10:33:38 +0100 (BST) Date: Mon, 22 Jul 1996 10:33:37 +0100 (BST) From: Developer To: freebsd-current@freebsd.org Subject: Linux Java compiler on FreeBSD Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ive been trying to get the linux java compiler running under FreeBSD 2.2 current and I`m having a slight problem with the libraries. I had to download libXpm from the linux site but still I get an error when I run it:- ./java: can't resolve symbol '__libc_malloc' Has anyone any ideas how I can fix this one? Thanks in advance. Regards, Trefor S. From owner-freebsd-current Mon Jul 22 04:51:22 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA03975 for current-outgoing; Mon, 22 Jul 1996 04:51:22 -0700 (PDT) Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA03970 for ; Mon, 22 Jul 1996 04:51:19 -0700 (PDT) Received: from localhost (dfr@localhost) by minnow.render.com (8.6.12/8.6.9) with SMTP id MAA13252; Mon, 22 Jul 1996 12:52:51 +0100 Date: Mon, 22 Jul 1996 12:52:49 +0100 (BST) From: Doug Rabson To: Developer cc: freebsd-current@freebsd.org Subject: Re: Linux Java compiler on FreeBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Jul 1996, Developer wrote: > > Ive been trying to get the linux java compiler running under FreeBSD 2.2 > current and I`m having a slight problem with the libraries. I had to > download libXpm from the linux site but still I get an error when I run > it:- > > ./java: can't resolve symbol '__libc_malloc' > > Has anyone any ideas how I can fix this one? You need to download some more up-to-date linux libraries. I trawled around on src.doc.ic.ac.uk until I found an unpacked linux dist and picked up the lib directory from that. -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 251 4411 FAX: +44 171 251 0939 From owner-freebsd-current Mon Jul 22 05:23:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA04883 for current-outgoing; Mon, 22 Jul 1996 05:23:45 -0700 (PDT) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA04877 for ; Mon, 22 Jul 1996 05:23:39 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.7.5/8.6.9) with SMTP id NAA23991 for ; Mon, 22 Jul 1996 13:31:39 +0100 (BST) Date: Mon, 22 Jul 1996 13:31:39 +0100 (BST) From: Developer To: freebsd-current@freebsd.org Subject: Re: turing off swap interleaving Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Jul 1996, John-Mark Gurney wrote: > I am wondering if there is a way to disable interleaving... or best > yet... tell it not to use one partition of swap until another is used > up... the reason I ask is because I reciently came very close to running > out of swap so I created a 16meg file, vnconfiged it... and swapped it > on... then I relized that the interleaving will actually kill performance > when it swap... while it would be better to tell it to use the original > swap until that is full... any body thought of this before? thanks for > the help... TTYL... k Sounds like a good idea - I`d like to find out if this is possible also. What is the quickest way of creating a 100MB file BTW? Also I managed to delete the swap file after swapping on it! I think it didn`t free up the space on the file system however. Is this safe or not? Regards, Trefor S. From owner-freebsd-current Mon Jul 22 05:33:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA05252 for current-outgoing; Mon, 22 Jul 1996 05:33:11 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA05247 for ; Mon, 22 Jul 1996 05:33:09 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id FAA14015; Mon, 22 Jul 1996 05:33:01 -0700 (PDT) Message-Id: <199607221233.FAA14015@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Developer cc: freebsd-current@freebsd.org Subject: Re: turing off swap interleaving In-reply-to: Your message of "Mon, 22 Jul 1996 13:31:39 BST." From: David Greenman Reply-To: dg@root.com Date: Mon, 22 Jul 1996 05:33:00 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >On Mon, 22 Jul 1996, John-Mark Gurney wrote: > >> I am wondering if there is a way to disable interleaving... or best >> yet... tell it not to use one partition of swap until another is used >> up... the reason I ask is because I reciently came very close to running >> out of swap so I created a 16meg file, vnconfiged it... and swapped it >> on... then I relized that the interleaving will actually kill performance >> when it swap... while it would be better to tell it to use the original >> swap until that is full... any body thought of this before? thanks for >> the help... TTYL... >k >Sounds like a good idea - I`d like to find out if this is possible also. It's not currently possible. >What is the quickest way of creating a 100MB file BTW? dd if=/dev/zero of=your.file bs=10k count=1000 ...probably not strictly the "quickest" way, but certainly one of the easiest ways. >Also I managed to delete the swap file after swapping on it! I think it >didn`t free up the space on the file system however. Is this safe or not? It's safe. The file is marked for delete and should go away when the system is rebooted (at which time the filesystems are forcibly dismounted, closing the file and causing it to be deleted). -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Mon Jul 22 05:58:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA05832 for current-outgoing; Mon, 22 Jul 1996 05:58:45 -0700 (PDT) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA05827 for ; Mon, 22 Jul 1996 05:58:42 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.7.5/8.6.9) with SMTP id OAA24492; Mon, 22 Jul 1996 14:06:42 +0100 (BST) Date: Mon, 22 Jul 1996 14:06:41 +0100 (BST) From: Developer To: Doug Rabson cc: freebsd-current@FreeBSD.ORG Subject: Re: Linux Java compiler on FreeBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Jul 1996, Doug Rabson wrote: > On Mon, 22 Jul 1996, Developer wrote: > > > > > Ive been trying to get the linux java compiler running under FreeBSD 2.2 > > current and I`m having a slight problem with the libraries. I had to > > download libXpm from the linux site but still I get an error when I run > > it:- > > > > ./java: can't resolve symbol '__libc_malloc' > > > > Has anyone any ideas how I can fix this one? > > You need to download some more up-to-date linux libraries. I trawled > around on src.doc.ic.ac.uk until I found an unpacked linux dist and picked > up the lib directory from that. I tried to download the libs from slackware-3.0 but that was the same version that I have (libc 5.0.9) and didn`t make any difference, is there a new one that this? Regards, Trefor S. From owner-freebsd-current Mon Jul 22 06:33:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA06861 for current-outgoing; Mon, 22 Jul 1996 06:33:20 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA06853 for ; Mon, 22 Jul 1996 06:33:18 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id GAA14093; Mon, 22 Jul 1996 06:33:18 -0700 (PDT) Message-Id: <199607221333.GAA14093@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Developer cc: freebsd-current@freebsd.org Subject: Re: turing off swap interleaving From: David Greenman Reply-To: dg@root.com Date: Mon, 22 Jul 1996 06:33:17 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>What is the quickest way of creating a 100MB file BTW? > > dd if=/dev/zero of=your.file bs=10k count=1000 Woops, that should be count=10000. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Mon Jul 22 08:39:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA12644 for current-outgoing; Mon, 22 Jul 1996 08:39:37 -0700 (PDT) Received: from phaedrus.uchicago.edu (phaedrus.uchicago.edu [128.135.21.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA12639 for ; Mon, 22 Jul 1996 08:39:34 -0700 (PDT) Received: from phaedrus.uchicago.edu (localhost [127.0.0.1]) by phaedrus.uchicago.edu (8.7.5/8.7.3) with ESMTP id KAA04372; Mon, 22 Jul 1996 10:40:14 GMT Message-Id: <199607221040.KAA04372@phaedrus.uchicago.edu> To: Developer cc: freebsd-current@freebsd.org Subject: Re: Linux Java compiler on FreeBSD In-reply-to: Your message of "Mon, 22 Jul 1996 10:33:37 +0100." MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4368.838032012.1@phaedrus.uchicago.edu> Date: Mon, 22 Jul 1996 10:40:13 +0000 From: steve farrell Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >Ive been trying to get the linux java compiler running under FreeBSD 2.2 >current and I`m having a slight problem with the libraries. I had to >download libXpm from the linux site but still I get an error when I run >it:- > >./java: can't resolve symbol '__libc_malloc' > >Has anyone any ideas how I can fix this one? > well, i remember this problem from my linux day: java requires libc.so.5.2.x (well, at least newer than the 5.0.9 version, which is common on the distributions, and, surprise surprise, in the linux-libs port). unfortunately, upgrading to 5.3.12 (the newest i could find), results in java -> coredump; javac exits normally, but does nothing... didn't try the others. (sidenote: can you do anything with a coredump from the linux emulator? maybe you need gdb compiled for linux?) i'm guessing this might have something to do with freebsd not being capable of handling the pthreads which are compiled into the jdk? the netscape_javac, with 3.0b5a, gives the error that it can't initialize threads. i guess still only 3.0b2 works for that port? --wasn't that interesting to me because it only gives an alternative to javac, not java... anyway, i would love to see a jdk port to freebsd. i know one was done by a guy in korea using green threads in february, i think, though i haven't been able to get my hands on it, and i understand it needed more work (?). i wrote to him asking if he worked on it some more, and i think he misunderstood me and was offended, so i kind of backed off =). i know there was a bit of discussion about this last time i brought this up about a month ago -- but i'll probably bring it up again =). anyone working on this? i'd love to do what i can to help... (by the way, i read ahead a bit -- you can get all kinds of linux libs -- maybe worth trying some other versions? -- from: ftp://tsx-11.mit.edu/pub/linux/packages/GCC/) From owner-freebsd-current Mon Jul 22 08:59:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA13369 for current-outgoing; Mon, 22 Jul 1996 08:59:16 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@mindbender.headcandy.com [199.238.225.168]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA13364 for ; Mon, 22 Jul 1996 08:59:12 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.7.3) with SMTP id IAA03361; Mon, 22 Jul 1996 08:57:44 -0700 (PDT) Message-Id: <199607221557.IAA03361@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Developer cc: freebsd-current@freebsd.org Subject: Re: turing off swap interleaving In-reply-to: Your message of Mon, 22 Jul 96 13:31:39 +0100. Date: Mon, 22 Jul 1996 08:57:38 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Also I managed to delete the swap file after swapping on it! I think it >didn`t free up the space on the file system however. Is this safe or not? Uh, have you ever used Unix before? ;-) As long as the kernel has a file descriptor open on the file, it still exists. You merely removed the last named reference to it on the disk. Once the kernel closes the last reference to the file, it will see that there are no remaining links to it, and remove it completely. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@HeadCandy.com --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... Roll your own Internet access -- Seattle People's Internet cooperative. If you're in the Seattle area, ask me how. ----------------------------------------------------------------------------- From owner-freebsd-current Mon Jul 22 09:05:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA13837 for current-outgoing; Mon, 22 Jul 1996 09:05:06 -0700 (PDT) Received: from srv1-bsb.gns.com.br ([200.239.56.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA13820 for ; Mon, 22 Jul 1996 09:04:59 -0700 (PDT) Received: (from mail@localhost) by srv1-bsb.gns.com.br (8.7.5/8.7.5) id NAA29308; Mon, 22 Jul 1996 13:04:05 -0300 (EST) Received: from dl0117-bsb.gns.com.br(200.239.56.117) by srv1-bsb.gns.com.br via smap (V1.3) id sma029266; Mon Jul 22 13:03:49 1996 Received: by DANIEL.gns.net.br (IBM OS/2 SENDMAIL VERSION 1.3.14/2.12um) id AA0064; Sun, 21 Jul 96 16:37:56 +0300 Message-Id: <9607211337.AA0064@DANIEL.gns.net.br> Date: Sun, 21 Jul 96 16:37:55 +0300 From: "Daniel C. Sobral" Subject: ncurses To: current@freefall.freebsd.org Reply-To: e8917523@linf.unb.br X-Disclaimer: Klaatu Barada Nikto! X-Mailer: ELM [version 2.3 PL11] for OS/2 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk ncurses has, for sometime now, been using curses.h as is header file. Some softwares are already using this (e.g., lynx). Is the current tree using the latest ncurses version (and thus have the correct curses.h header)? -- Daniel C. Sobral (8-DCS) dcs@gns.com.br e8917523@linf.unb.br From owner-freebsd-current Mon Jul 22 09:09:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA14044 for current-outgoing; Mon, 22 Jul 1996 09:09:51 -0700 (PDT) Received: from phaedrus.uchicago.edu (phaedrus.uchicago.edu [128.135.21.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA14037 for ; Mon, 22 Jul 1996 09:09:49 -0700 (PDT) Received: from phaedrus.uchicago.edu (localhost [127.0.0.1]) by phaedrus.uchicago.edu (8.7.5/8.7.3) with ESMTP id LAA06106; Mon, 22 Jul 1996 11:10:29 GMT Message-Id: <199607221110.LAA06106@phaedrus.uchicago.edu> To: Developer cc: freebsd-current@freebsd.org, spfarrel@phaedrus.uchicago.edu Subject: Re: Linux Java compiler on FreeBSD In-reply-to: Your message of "Mon, 22 Jul 1996 10:33:37 +0100." MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <6102.838033827.1@phaedrus.uchicago.edu> Date: Mon, 22 Jul 1996 11:10:28 +0000 From: steve farrell Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >./java: can't resolve symbol '__libc_malloc' > of course, i'm a moron: ftp://freefall.FreeBSD.org/pub/FreeBSD/LOCAL_PORTS/jdk10.tar.gz looks like a good place to start. i'm just setting it up now. evidentally there is no appletviewer, but that is one thing i can live without (it's called netscape). (unfortunately, the few tests i gave the jdk port, it didn't fare very well... a lot of exceptions on code that works in solaris...) From owner-freebsd-current Mon Jul 22 09:10:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA14120 for current-outgoing; Mon, 22 Jul 1996 09:10:34 -0700 (PDT) Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA14114 for ; Mon, 22 Jul 1996 09:10:31 -0700 (PDT) Received: from localhost (dfr@localhost) by minnow.render.com (8.6.12/8.6.9) with SMTP id RAA13627; Mon, 22 Jul 1996 17:11:38 +0100 Date: Mon, 22 Jul 1996 17:11:37 +0100 (BST) From: Doug Rabson To: Developer cc: freebsd-current@FreeBSD.ORG Subject: Re: Linux Java compiler on FreeBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Jul 1996, Developer wrote: > > > On Mon, 22 Jul 1996, Doug Rabson wrote: > > > On Mon, 22 Jul 1996, Developer wrote: > > > > > > > > Ive been trying to get the linux java compiler running under FreeBSD 2.2 > > > current and I`m having a slight problem with the libraries. I had to > > > download libXpm from the linux site but still I get an error when I run > > > it:- > > > > > > ./java: can't resolve symbol '__libc_malloc' > > > > > > Has anyone any ideas how I can fix this one? > > > > You need to download some more up-to-date linux libraries. I trawled > > around on src.doc.ic.ac.uk until I found an unpacked linux dist and picked > > up the lib directory from that. > > I tried to download the libs from slackware-3.0 but that was the same > version that I have (libc 5.0.9) and didn`t make any difference, is there > a new one that this? I think I picked up the ones from redhat. I had to get an up-to-date version of ld.so as well. -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 251 4411 FAX: +44 171 251 0939 From owner-freebsd-current Mon Jul 22 11:09:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA20838 for current-outgoing; Mon, 22 Jul 1996 11:09:00 -0700 (PDT) Received: from eac.iafrica.com (h196-7-192-155.iafrica.com [196.7.192.155]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA20833; Mon, 22 Jul 1996 11:08:54 -0700 (PDT) Received: (from rnordier@localhost) by eac.iafrica.com (8.6.12/8.6.12) id UAA00225; Mon, 22 Jul 1996 20:08:13 +0200 From: Robert Nordier Message-Id: <199607221808.UAA00225@eac.iafrica.com> Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 22 Jul 1996 20:08:11 +0200 (SAT) Cc: pst@shockwave.com, hackers@freebsd.org, current@freebsd.org In-Reply-To: <15906.837972850@time.cdrom.com> from "Jordan K. Hubbard" at Jul 21, 96 11:14:10 am X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard wrote: > > I think Robert Nordier is working on a complete re-write, actually. > How's that going, Robert? > > Jordan > The FAT fs primitives are done and tested and I'm currently working on VFAT support. Microsoft is shortly to be introducing a FAT32 filesystem to Windows 95 which will increase maximum filesystem size from 2 (or 4, for NT) gigabytes to 2 terabytes. The new filesystem makes use of 32-bit (as opposed to 12-bit and 16-bit) FAT entries and will require a fundamentally different handling of boot record, FATs, and root directory, so I'm busy on provision for this also. The changes required for FAT32 support would probably be rather difficult to graft onto the msdosfs at this stage: possibly another factor supporting the decision to re-implement DOS/Win filesystem support on FreeBSD. FAT32 is supposedly due for public release in the fall. I'm currently working towards a similar release date for the new filesystem. -- Robert Nordier From owner-freebsd-current Mon Jul 22 11:52:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA24656 for current-outgoing; Mon, 22 Jul 1996 11:52:31 -0700 (PDT) Received: from fang.cs.sunyit.edu (fang.cs.sunyit.edu [192.52.220.66]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA24649; Mon, 22 Jul 1996 11:52:26 -0700 (PDT) Received: (from chuck@localhost) by fang.cs.sunyit.edu (8.6.9/8.6.9) id OAA01064; Mon, 22 Jul 1996 14:52:04 -0400 Date: Mon, 22 Jul 1996 14:52:04 -0400 From: Charles Green Message-Id: <199607221852.OAA01064@fang.cs.sunyit.edu> In-Reply-To: Robert Nordier "Re: anyone working on upgrading the msdosfs to NetBSD levels?" (Jul 22, 20:08) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Robert Nordier Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? Cc: hackers@freebsd.org, current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Robert Nordier stands accused of saying: } Date: Jul 22, 20:08 } Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? } Jordan K. Hubbard wrote: } > } > I think Robert Nordier is working on a complete re-write, actually. } > How's that going, Robert? } > } > Jordan } > } } The FAT fs primitives are done and tested and I'm currently working } on VFAT support. } } Microsoft is shortly to be introducing a FAT32 filesystem to Windows } 95 which will increase maximum filesystem size from 2 (or 4, for } NT) gigabytes to 2 terabytes. The new filesystem makes use of } 32-bit (as opposed to 12-bit and 16-bit) FAT entries and will } require a fundamentally different handling of boot record, FATs, } and root directory, so I'm busy on provision for this also. } } The changes required for FAT32 support would probably be rather } difficult to graft onto the msdosfs at this stage: possibly another } factor supporting the decision to re-implement DOS/Win filesystem } support on FreeBSD. } } FAT32 is supposedly due for public release in the fall. I'm } currently working towards a similar release date for the new } filesystem. } } -- } Robert Nordier }-- End of excerpt from Robert Nordier How soon will we see the integration of at least the FAT fs support into -current? -- Charles Green, PRC Inc. Research & Development Rome Laboratory, NY From owner-freebsd-current Mon Jul 22 12:00:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA25712 for current-outgoing; Mon, 22 Jul 1996 12:00:17 -0700 (PDT) Received: from eac.iafrica.com (h196-7-192-190.iafrica.com [196.7.192.190]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA25623; Mon, 22 Jul 1996 11:59:30 -0700 (PDT) Received: (from rnordier@localhost) by eac.iafrica.com (8.6.12/8.6.12) id UAA00383; Mon, 22 Jul 1996 20:58:04 +0200 From: Robert Nordier Message-Id: <199607221858.UAA00383@eac.iafrica.com> Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? To: pst@shockwave.com (Paul Traina) Date: Mon, 22 Jul 1996 20:58:02 +0200 (SAT) Cc: jkh@time.cdrom.com, hackers@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <199607220534.WAA03617@precipice.shockwave.com> from "Paul Traina" at Jul 21, 96 10:34:02 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Paul Traina wrote: > > Do we -need- a complete rewrite? It looks like the current NetBSD version > is actually in pretty damn good shape. Unfortunately, detangling changes > is not going to be bloody easy ( source code changes>). > > Paul I ran some fairly extensive tests on the FreeBSD msdosfs several months ago. At that stage, it seemed to me to have fundamental problems that did not appear to be addressed (or easily addressable), even taking into account NetBSD diffs. Unfortunately - as you mention - the NetBSD code contains many changes that are more stylistic than functional. Over the last few weeks, I've been working on a few msdosfs patches myself. However, the most serious FreeBSD msdosfs problem (where it causes corruption to other partitions) apparently needs a 64-cluster FIPS-ed FAT filesystem with an EIDE controller translating to 64 heads, 63 sectors to be readily reproducible. (At least, I haven't reproduced it on any other 64-cluster filesystems.) Personally, I'd be glad if someone did succumb to the urge to bring NetBSD changes across to the msdosfs. That way, I could forget msdosfs patches, and concentrate on getting the new vfatfs finished. The vfatfs would then also have to be demonstrably better than an improved msdosfs to be worth adopting: a good incentive, and probably a good thing for FreeBSD generally. -- Robert Nordier From owner-freebsd-current Mon Jul 22 12:52:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA01391 for current-outgoing; Mon, 22 Jul 1996 12:52:34 -0700 (PDT) Received: from eac.iafrica.com (slipper101149.iafrica.com [196.7.101.149]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA01368; Mon, 22 Jul 1996 12:52:15 -0700 (PDT) Received: (from rnordier@localhost) by eac.iafrica.com (8.6.12/8.6.12) id VAA00711; Mon, 22 Jul 1996 21:50:11 +0200 From: Robert Nordier Message-Id: <199607221950.VAA00711@eac.iafrica.com> Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? To: green@fang.cs.sunyit.edu (Charles Green) Date: Mon, 22 Jul 1996 21:50:10 +0200 (SAT) Cc: hackers@freebsd.org, current@freebsd.org In-Reply-To: <199607221852.OAA01064@fang.cs.sunyit.edu> from "Charles Green" at Jul 22, 96 02:52:04 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Charles Green wrote: > > Robert Nordier stands accused of saying: > } Date: Jul 22, 20:08 > } Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? > } Jordan K. Hubbard wrote: > } > > } > I think Robert Nordier is working on a complete re-write, actually. > } > How's that going, Robert? > } > > } > Jordan > } > > } > } The FAT fs primitives are done and tested and I'm currently working > } on VFAT support. > } > } Microsoft is shortly to be introducing a FAT32 filesystem to Windows > } 95 which will increase maximum filesystem size from 2 (or 4, for > } NT) gigabytes to 2 terabytes. The new filesystem makes use of > } 32-bit (as opposed to 12-bit and 16-bit) FAT entries and will > } require a fundamentally different handling of boot record, FATs, > } and root directory, so I'm busy on provision for this also. > } > } The changes required for FAT32 support would probably be rather > } difficult to graft onto the msdosfs at this stage: possibly another > } factor supporting the decision to re-implement DOS/Win filesystem > } support on FreeBSD. > } > } FAT32 is supposedly due for public release in the fall. I'm > } currently working towards a similar release date for the new > } filesystem. > } > } -- > } Robert Nordier > }-- End of excerpt from Robert Nordier > > > > How soon will we see the integration of at least the FAT fs support > into -current? I wasn't actually planning to release FAT fs-only support separately, since FAT32 support, in particular, requires a fundamentally different, mostly more flexible, approach at a number of levels; and I'd rather have it there at the start. I don't think there's very much deep interest, among most FreeBSD hackers, in the unsavory technical details of DOS/Win filesystems. So it seems to make most sense to release the vfatfs as functionally complete as possible, rather than as work in progress. Anyway, that's how I've been looking at it. -- Robert Nordier From owner-freebsd-current Mon Jul 22 13:11:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA03069 for current-outgoing; Mon, 22 Jul 1996 13:11:14 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA03064; Mon, 22 Jul 1996 13:11:10 -0700 (PDT) Received: (from richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) id NAA20832; Mon, 22 Jul 1996 13:11:04 -0700 Date: Mon, 22 Jul 1996 13:11:02 -0700 (PDT) From: Veggy Vinny To: Joerg Wunsch cc: current@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: bootstrap In-Reply-To: <199607220624.IAA04045@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Jul 1996, J Wunsch wrote: > As Veggy Vinny wrote: > > > How do I regenerate the bootstrap for the FreeBSD partition? Thanks. > > P.S. I'm using -current.. > > disklabel -B sd0 > > (But you certainly meant ``FreeBSD slice'', right? :) Just tried it as disklabel -B wd0 but no luck... I'm using a Western Digital WDAC31600 Caviar EIDE HD in LBA mode under -current and in the Booteasy menu, when I hit F2 for FreeBSD, it just redisplays the Booteasy menu again in a loop..... Is there a way I can fix this? Here is my fdisk wd0 output: root@bigbang [1:06pm][/usr/home/vince] >> fdisk wd0 ******* Working on device /dev/rwd0 ******* parameters extracted from in-core disklabel are: cylinders=3148 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=3148 heads=16 sectors/track=63 (1008 blks/cyl) Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 0 is: sysid 6,(Primary 'big' DOS (> 32MB)) start 63, size 1031121 (503 Meg), flag 0 beg: cyl 0/ sector 1/ head 1; end: cyl 785/ sector 63/ head 15 The data for partition 1 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 1031184, size 2142000 (1045 Meg), flag 0 beg: cyl 785/ sector 1/ head 0; end: cyl 785/ sector 63/ head 15 The data for partition 2 is: The data for partition 3 is: Vince From owner-freebsd-current Mon Jul 22 13:21:22 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA03824 for current-outgoing; Mon, 22 Jul 1996 13:21:22 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA03805 for ; Mon, 22 Jul 1996 13:21:13 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id WAA18134 for ; Mon, 22 Jul 1996 22:21:09 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA04566 for freebsd-current@FreeBSD.org; Mon, 22 Jul 1996 22:21:09 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id VAA05192 for freebsd-current@FreeBSD.org; Mon, 22 Jul 1996 21:57:58 +0200 (MET DST) From: J Wunsch Message-Id: <199607221957.VAA05192@uriah.heep.sax.de> Subject: Re: bootstrap To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 22 Jul 1996 21:57:57 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Veggy Vinny at "Jul 21, 96 11:58:35 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Veggy Vinny wrote: > Yeah, probably... :) Does the bootstrap work on an EIDE LBA > FreeBSD slice in -current? You cannot have an ``LBA FreeBSD slice'', only a BIOS using LBA translation. I know that our new notebook is setup to use LBA mode in the BIOS and that it boots FreeBSD ok. However, my experience with IDE is rather limited, so i haven't thought about the limitations and constraints. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Jul 22 13:22:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA03929 for current-outgoing; Mon, 22 Jul 1996 13:22:02 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA03910 for ; Mon, 22 Jul 1996 13:21:56 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id WAA18123; Mon, 22 Jul 1996 22:20:56 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA04549; Mon, 22 Jul 1996 22:20:55 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id WAA05286; Mon, 22 Jul 1996 22:15:08 +0200 (MET DST) From: J Wunsch Message-Id: <199607222015.WAA05286@uriah.heep.sax.de> Subject: Re: Termcap problems To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 22 Jul 1996 22:15:08 +0200 (MET DST) Cc: dev@fgate.flevel.co.uk (Developer) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Developer at "Jul 22, 96 09:47:43 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Developer wrote: > I`m having a little problem with the termcap. If the xwindow width is > particular sizes (Not sure which ones, but always larger than 80 char) > then commands (like ls) think the window width is different (wider) than > it actually is, and so the formatting really messes up. What makes you think they thought of a different size? Programs like ls usually get the window geometry out of the struct winsize. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Jul 22 13:40:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA05934 for current-outgoing; Mon, 22 Jul 1996 13:40:18 -0700 (PDT) Received: from prozac.neuron.net (prozac.neuron.net [165.254.1.213]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA05911 for ; Mon, 22 Jul 1996 13:40:06 -0700 (PDT) Received: (from amir@localhost) by prozac.neuron.net (8.7.5/8.6.12) id QAA00424; Mon, 22 Jul 1996 16:49:50 -0400 (EDT) From: "Amir Y. Rosenblatt" Message-Id: <199607222049.QAA00424@prozac.neuron.net> Subject: Re: SCSI errors and repeated panics To: rgrimes@GndRsh.aac.dev.com (Rodney W. Grimes) Date: Mon, 22 Jul 1996 16:49:49 -0400 (EDT) Cc: amir@neuron.net, freebsd-current@freebsd.org In-Reply-To: <199607220147.SAA12945@GndRsh.aac.dev.com> from "Rodney W. Grimes" at Jul 21, 96 06:47:38 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I see justin replied about a kernel bug, but thought I might mention that > you did not complete the scsi bus termination description: OK -- I re-supped last night and recompiled my kernel. > The upper 8 bits are terminated on the 2940UW, if not you have > a miss termination on the data<7-15> signals of the scsi bus, > please check your SCSI-Select BIOS settings. I'm not entirely sure what you mean. I've had devices on boith the 8 and 16 bit internal connectors on the card since the first day I brought the machine online back in February. The only change I've made to the setup is that originally, the 4 gig HP C1533 DAT was at the end of the 8-bit chain and now it's in the middle, with the NEC CD-ROM drive at the end (the termination on both set appropriately as far as I could tell from the manuals). From the outset I'd adjusted the 2940UW's built-in termination to match this configuration as specified in the manual. Furthur advice or clarification would be greatly appreciated, as it started giving me the same errors again a short while ago (I called the guy who was sitting at the console and had him bring prozac [the machine] down for 15 minutes rather than letting it panic and crash). Thanks in advance, -Amir From owner-freebsd-current Mon Jul 22 13:54:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA07223 for current-outgoing; Mon, 22 Jul 1996 13:54:40 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA07217 for ; Mon, 22 Jul 1996 13:54:36 -0700 (PDT) Received: (from richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) id NAA25469; Mon, 22 Jul 1996 13:54:59 -0700 Date: Mon, 22 Jul 1996 13:54:58 -0700 (PDT) From: Veggy Vinny To: Joerg Wunsch cc: FreeBSD-current users Subject: Re: bootstrap In-Reply-To: <199607221957.VAA05192@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Jul 1996, J Wunsch wrote: > As Veggy Vinny wrote: > > > Yeah, probably... :) Does the bootstrap work on an EIDE LBA > > FreeBSD slice in -current? > > You cannot have an ``LBA FreeBSD slice'', only a BIOS using LBA > translation. > > I know that our new notebook is setup to use LBA mode in the BIOS and > that it boots FreeBSD ok. However, my experience with IDE is rather > limited, so i haven't thought about the limitations and constraints. What I mean was that this was a new drive and I was trying to back up my old drive to the new drive and everything seems working except the new drive won't boot FreeBSD.... I put the drive in the Bios with LBA translation and then installed FreeBSD after the 540 meg DOS partition but where is the problem exactly? Vince From owner-freebsd-current Mon Jul 22 14:02:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA08277 for current-outgoing; Mon, 22 Jul 1996 14:02:36 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA08265 for ; Mon, 22 Jul 1996 14:02:30 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id OAA19362; Mon, 22 Jul 1996 14:02:20 -0700 From: "Rodney W. Grimes" Message-Id: <199607222102.OAA19362@GndRsh.aac.dev.com> Subject: Re: SCSI errors and repeated panics To: amir@neuron.net (Amir Y. Rosenblatt) Date: Mon, 22 Jul 1996 14:02:19 -0700 (PDT) Cc: amir@neuron.net, freebsd-current@freebsd.org In-Reply-To: <199607222049.QAA00424@prozac.neuron.net> from "Amir Y. Rosenblatt" at "Jul 22, 96 04:49:49 pm" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I see justin replied about a kernel bug, but thought I might mention that > > you did not complete the scsi bus termination description: > > OK -- I re-supped last night and recompiled my kernel. > > > The upper 8 bits are terminated on the 2940UW, if not you have > > a miss termination on the data<7-15> signals of the scsi bus, > > please check your SCSI-Select BIOS settings. > > I'm not entirely sure what you mean. I mean that if you go into the SCSI-Select BIOS (Hit ^A during system Power On Self Test (POST) when the Adaptec bios mentions it) and check the settings of the on board scsi termination. You will find 3 or 4 options: a) Automatic (I recommend against this setting, the detection logic may fail under certain conditions.) b) High/Low Enabled (ie, all 16 bits of the scsi bus are terminated. c) High Enabled (ie, the upper 8 bits of the scsi bus are terminated) d) Disabled. In your configuration it _must_ be set to c) above... see the diagrams in the Adaptec manual.... > I've had devices on boith the 8 and > 16 bit internal connectors on the card since the first day I brought the > machine online back in February. The only change I've made to the setup > is that originally, the 4 gig HP C1533 DAT was at the end of the 8-bit > chain and now it's in the middle, with the NEC CD-ROM drive at the end > (the termination on both set appropriately as far as I could tell from > the manuals). Humm... I suspect that the HP C1533 DAT drive has active terminators, ie the resistor value will be 110 ohms, and the NEC CD-ROM is using passive termination, ie the resitor value will be 220/330 ohm. I highly recommend (and the SCSI-II spec just recommends) that you use active termination with Fast SCSI-II. > From the outset I'd adjusted the 2940UW's built-in > termination to match this configuration as specified in the manual. > Furthur advice or clarification would be greatly appreciated, as it > started giving me the same errors again a short while ago (I called the > guy who was sitting at the console and had him bring prozac [the machine] > down for 15 minutes rather than letting it panic and crash). Thanks in > advance, > > -Amir -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Mon Jul 22 14:03:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA08433 for current-outgoing; Mon, 22 Jul 1996 14:03:47 -0700 (PDT) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA08403; Mon, 22 Jul 1996 14:03:41 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-5.slip.Uni-Koeln.DE) by Sisyphos with SMTP id AA19903 (5.67b/IDA-1.5); Mon, 22 Jul 1996 23:03:16 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.7.5/8.6.9) id XAA04254; Mon, 22 Jul 1996 23:03:08 +0200 (MET DST) Date: Mon, 22 Jul 1996 23:03:08 +0200 (MET DST) Message-Id: <199607222103.XAA04254@x14.mi.uni-koeln.de> From: Stefan Esser To: dg@root.com Cc: "Marc G. Fournier" , current@freebsd.org, stable@freebsd.org Subject: Re: ncr53c810 driver in stable/current In-Reply-To: <199607220803.BAA10665@root.com> References: <199607220803.BAA10665@root.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk David Greenman writes: > > for the second time today, my -stable machine has crashed, > >and hung while trying to reboot. the machine is using an ncr53c810 > >SCSI controller (the ASUS PC-200(sp?)) is the only SCSI controller > >in the box.... > > > > Now, I can live with the crashes, for now, but the fact that > >it is hanging on reboots is becoming a royal pain... > > > > The last time I reported this, someone made mention that > >the cause was the NCR driver not switching modes or something like > >that, so that it can't dump core...? > > > > If anyone remembers this thread, or knows what the hell I'm > >talking about...has this been fixed in -current? > > We've seen this problem on freefall (which uses the NCR controller). It > likes to hang when we try to reboot it. I don't recall any fixes for this, > and I don't know what causes it. Hmm, I have not heard about this problem on other systems ... Could both of you please send details on the configuration: 1) CPU class (eg. P5/133) 2) controller chip (810 or 825) 3) disk drives connected 4) type of hang (does the SDMS BIOS probe complete ?) Since 1-3) is reported in the boot messages, I'd like to receive a verbose boot log. Regarding the kernel dump: It used to work at a time, and I'm not sure what makes it fail. There was some way to obtain a kernel core with DDB at no risk of data corruption on the disk (which I couldn't take !), but I don't remember any details. I'll build a kernel with the debugger and will try to test the dump feature over the next few days. (Please allow 10 days for me to get it fixed ...) Regards, STefan From owner-freebsd-current Mon Jul 22 14:11:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA09159 for current-outgoing; Mon, 22 Jul 1996 14:11:18 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA09113; Mon, 22 Jul 1996 14:11:12 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id OAA01034; Mon, 22 Jul 1996 14:10:42 -0700 (PDT) Message-Id: <199607222110.OAA01034@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Stefan Esser cc: "Marc G. Fournier" , current@freebsd.org, stable@freebsd.org Subject: Re: ncr53c810 driver in stable/current In-reply-to: Your message of "Mon, 22 Jul 1996 23:03:08 +0200." <199607222103.XAA04254@x14.mi.uni-koeln.de> From: David Greenman Reply-To: dg@root.com Date: Mon, 22 Jul 1996 14:10:42 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > We've seen this problem on freefall (which uses the NCR controller). It > > likes to hang when we try to reboot it. I don't recall any fixes for this, > > and I don't know what causes it. > >Hmm, I have not heard about this problem on other systems ... > >Could both of you please send details on the configuration: > >1) CPU class (eg. P5/133) P5/100 >2) controller chip (810 or 825) 810 >3) disk drives connected I don't have an exact answer to this at the moment, but I think freefall has three Quantum PD-1800, one Quantum Grand Prix (might be a Seagate Baracuda), and a Toshiba 3501 CDROM drive. >4) type of hang (does the SDMS BIOS probe complete ?) The hang is at shutdown, not startup. Jordan might be able to tell you if there are any console messages prior to the hang. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Mon Jul 22 14:35:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA12131 for current-outgoing; Mon, 22 Jul 1996 14:35:13 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA12106; Mon, 22 Jul 1996 14:35:06 -0700 (PDT) Received: (from richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) id OAA29810; Mon, 22 Jul 1996 14:33:42 -0700 Date: Mon, 22 Jul 1996 14:33:40 -0700 (PDT) From: Veggy Vinny To: Stefan Esser cc: dg@root.com, "Marc G. Fournier" , current@freebsd.org, stable@freebsd.org Subject: Re: ncr53c810 driver in stable/current In-Reply-To: <199607222103.XAA04254@x14.mi.uni-koeln.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Jul 1996, Stefan Esser wrote: > David Greenman writes: > > > for the second time today, my -stable machine has crashed, > > >and hung while trying to reboot. the machine is using an ncr53c810 > > >SCSI controller (the ASUS PC-200(sp?)) is the only SCSI controller > > >in the box.... > > > > > > Now, I can live with the crashes, for now, but the fact that > > >it is hanging on reboots is becoming a royal pain... > > > > > > The last time I reported this, someone made mention that > > >the cause was the NCR driver not switching modes or something like > > >that, so that it can't dump core...? > > > > > > If anyone remembers this thread, or knows what the hell I'm > > >talking about...has this been fixed in -current? > > > > We've seen this problem on freefall (which uses the NCR controller). It > > likes to hang when we try to reboot it. I don't recall any fixes for this, > > and I don't know what causes it. > > Hmm, I have not heard about this problem on other systems ... > > Could both of you please send details on the configuration: > > 1) CPU class (eg. P5/133) > > 2) controller chip (810 or 825) > > 3) disk drives connected > > 4) type of hang (does the SDMS BIOS probe complete ?) > > Since 1-3) is reported in the boot messages, I'd like > to receive a verbose boot log. > > Regarding the kernel dump: It used to work at a time, > and I'm not sure what makes it fail. > > There was some way to obtain a kernel core with DDB at > no risk of data corruption on the disk (which I couldn't > take !), but I don't remember any details. I'll build a > kernel with the debugger and will try to test the dump > feature over the next few days. (Please allow 10 days > for me to get it fixed ...) Maybe it could be the SCSI Tags problem I had before? Vince From owner-freebsd-current Mon Jul 22 14:42:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA12901 for current-outgoing; Mon, 22 Jul 1996 14:42:27 -0700 (PDT) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA12880; Mon, 22 Jul 1996 14:42:16 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-5.slip.Uni-Koeln.DE) by Sisyphos with SMTP id AA20278 (5.67b/IDA-1.5); Mon, 22 Jul 1996 23:41:47 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.7.5/8.6.9) id XAA04311; Mon, 22 Jul 1996 23:41:45 +0200 (MET DST) Date: Mon, 22 Jul 1996 23:41:45 +0200 (MET DST) Message-Id: <199607222141.XAA04311@x14.mi.uni-koeln.de> From: Stefan Esser To: jkh@freebsd.org Cc: "Marc G. Fournier" , current@freebsd.org, stable@freebsd.org, dg@root.com Subject: Re: ncr53c810 driver in stable/current In-Reply-To: <199607222110.OAA01034@root.com> References: <199607222103.XAA04254@x14.mi.uni-koeln.de> <199607222110.OAA01034@root.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk David Greenman writes: > > > We've seen this problem on freefall (which uses the NCR controller). It > > > likes to hang when we try to reboot it. I don't recall any fixes for this, > > > and I don't know what causes it. > > > >Hmm, I have not heard about this problem on other systems ... > > > >Could both of you please send details on the configuration: > > > >1) CPU class (eg. P5/133) > > P5/100 Hmm, I had been thinking of a problem with a very fast CPU. > >2) controller chip (810 or 825) > > 810 Ok. > >3) disk drives connected > > I don't have an exact answer to this at the moment, but I think freefall > has three Quantum PD-1800, one Quantum Grand Prix (might be a Seagate > Baracuda), and a Toshiba 3501 CDROM drive. Also nothing special. > >4) type of hang (does the SDMS BIOS probe complete ?) > > The hang is at shutdown, not startup. Jordan might be able to tell you if > there are any console messages prior to the hang. Ok. I guess Jordan is reading this anyway: Please provide me with details: 1) does the system complete the final sync ? 2) does it clear the screen in preparation of a warm boot ? 3) does it require a power-off or can it be made to boot by some other means (Ctl-Alt-Del) ? 4) does it always hang ? 5) do you know that the hang is not caused by some unrelated problem (BROKEN_KEYBOARD_RESET comes to mind :) ? Regards, STefan From owner-freebsd-current Mon Jul 22 14:43:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA13033 for current-outgoing; Mon, 22 Jul 1996 14:43:37 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA13003 for ; Mon, 22 Jul 1996 14:43:27 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id XAA19905 for ; Mon, 22 Jul 1996 23:43:21 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA05933 for freebsd-current@FreeBSD.org; Mon, 22 Jul 1996 23:43:21 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id WAA06528 for freebsd-current@FreeBSD.org; Mon, 22 Jul 1996 22:50:38 +0200 (MET DST) From: J Wunsch Message-Id: <199607222050.WAA06528@uriah.heep.sax.de> Subject: Re: bootstrap To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 22 Jul 1996 22:50:38 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Veggy Vinny at "Jul 22, 96 01:11:02 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Veggy Vinny wrote: > Just tried it as disklabel -B wd0 but no luck... I'm using a > Western Digital WDAC31600 Caviar EIDE HD in LBA mode under -current and > in the Booteasy menu, when I hit F2 for FreeBSD, it just redisplays the > Booteasy menu again in a loop..... Is there a way I can fix this? By using a Real Disk. No, sorry, i don't have a clue about the implications of using LBA mode. I decided to not bother with this half-designed approach, and to ignore IDE for the rest of my life except for some situations like notebooks. You certainly either have to get a really good picture about who uses which figures (BIOS, BSD, other systems on the same disk), or you have to teach the wdc driver about LBA addressing. Pick your more favorite choice. :-] (Btw., this wasn't a question of the BSD bootstrap from the beginning, that's why disklabel -B didn't change the behaviour.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Jul 22 15:04:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA15027 for current-outgoing; Mon, 22 Jul 1996 15:04:52 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA14996; Mon, 22 Jul 1996 15:04:35 -0700 (PDT) Received: from localhost (scrappy@localhost) by ki.net (8.7.5/8.7.5) with SMTP id SAA14584; Mon, 22 Jul 1996 18:04:17 -0400 (EDT) Date: Mon, 22 Jul 1996 18:04:16 -0400 (EDT) From: "Marc G. Fournier" To: Stefan Esser cc: jkh@freebsd.org, current@freebsd.org, stable@freebsd.org, dg@root.com Subject: Re: ncr53c810 driver in stable/current In-Reply-To: <199607222141.XAA04311@x14.mi.uni-koeln.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Jul 1996, Stefan Esser wrote: > David Greenman writes: > > > > We've seen this problem on freefall (which uses the NCR controller). It > > > > likes to hang when we try to reboot it. I don't recall any fixes for this, > > > > and I don't know what causes it. > > > > > >Hmm, I have not heard about this problem on other systems ... > > > > > >Could both of you please send details on the configuration: > > > > > >1) CPU class (eg. P5/133) > > > > P5/100 > > Hmm, I had been thinking of a problem with a very fast CPU. > 486DX4-100 here > > >2) controller chip (810 or 825) > > > > 810 > > Ok. > Same > > >3) disk drives connected > > > > I don't have an exact answer to this at the moment, but I think freefall > > has three Quantum PD-1800, one Quantum Grand Prix (might be a Seagate > > Baracuda), and a Toshiba 3501 CDROM drive. > > Also nothing special. > (ncr0:0:0): "QUANTUM FIREBALL1280S 630C" type 0 fixe (ncr0:1:0): "QUANTUM LPS340S 020B" type 0 fixed SCSI (ncr0:2:0): "QUANTUM LP240S GM240S01X 4.6" type 0 fi (ncr0:3:0): "CONNER CFP1060S 1.05GB 243F" type 0 fix > > >4) type of hang (does the SDMS BIOS probe complete ?) > > > > The hang is at shutdown, not startup. Jordan might be able to tell you if > > there are any console messages prior to the hang. > Same, on shutdown, not startup... > Ok. I guess Jordan is reading this anyway: > > Please provide me with details: > > 1) does the system complete the final sync ? No, this is where it hangs... > 2) does it clear the screen in preparation of a warm boot ? No, see 1 > 3) does it require a power-off or can it be made to boot > by some other means (Ctl-Alt-Del) ? requires a power-off, but am not 100% certain, since I've gotten into the habit of doing a cold boot (99.9% certain the habit is because ctl-alt-del didn't work) > 4) does it always hang ? Everytime it crashes, yes...doing reboot from the console has never hung it... > 5) do you know that the hang is not caused by some unrelated > problem (BROKEN_KEYBOARD_RESET comes to mind :) ? > No, how would I find out? Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Mon Jul 22 15:30:32 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA16866 for current-outgoing; Mon, 22 Jul 1996 15:30:32 -0700 (PDT) Received: from troll.uunet.ca (troll.uunet.ca [142.77.1.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA16847; Mon, 22 Jul 1996 15:30:27 -0700 (PDT) Received: from localhost by troll.uunet.ca with SMTP id <21007-20218>; Mon, 22 Jul 1996 18:30:17 -0400 Date: Mon, 22 Jul 1996 18:30:10 -0400 From: Cat Okita To: "Marc G. Fournier" cc: Stefan Esser , jkh@freebsd.org, current@freebsd.org, stable@freebsd.org, dg@Root.COM Subject: Re: ncr53c810 driver in stable/current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Jul 1996, Marc G. Fournier wrote: > Same, on shutdown, not startup... I have a vague recollection of a panic on not being able to write to assigned vnode (or something along those lines - it *was* 3:30am) > requires a power-off, but am not 100% certain, since I've gotten > into the habit of doing a cold boot (99.9% certain the habit is because > ctl-alt-del didn't work) Definately requires a power off - the keyboard doesn't respond to any key or combination that I've tried. > > 4) does it always hang ? > Everytime it crashes, yes...doing reboot from the console > has never hung it... *Only* when it crashes - a planned reboot, be it remote or local always seems to work. Cat From owner-freebsd-current Mon Jul 22 17:42:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA24936 for current-outgoing; Mon, 22 Jul 1996 17:42:11 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA24925 for ; Mon, 22 Jul 1996 17:42:09 -0700 (PDT) Received: (from richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) id RAA18372; Mon, 22 Jul 1996 17:42:22 -0700 Date: Mon, 22 Jul 1996 17:42:20 -0700 (PDT) From: Veggy Vinny To: Joerg Wunsch cc: FreeBSD-current users Subject: Re: bootstrap In-Reply-To: <199607222050.WAA06528@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Jul 1996, J Wunsch wrote: > As Veggy Vinny wrote: > > > Just tried it as disklabel -B wd0 but no luck... I'm using a > > Western Digital WDAC31600 Caviar EIDE HD in LBA mode under -current and > > in the Booteasy menu, when I hit F2 for FreeBSD, it just redisplays the > > Booteasy menu again in a loop..... Is there a way I can fix this? > > By using a Real Disk. Yeah, I know but the problem is my Seagate 4 GIG Barrcuda is still back at Seagate and I still haven't seen it for the last 3-4 months so I have to use this for now.. > No, sorry, i don't have a clue about the implications of using LBA > mode. I decided to not bother with this half-designed approach, and > to ignore IDE for the rest of my life except for some situations like > notebooks. Hmmm, who is the one who actually does the EIDE support in -current because I remember that before FreeBSD wouldn't let a disk using LBA to even install when it was 2.0.5R so my original Conner CFA1275A 1.275 Gig Drive was installed as Normal for the BIOS mode and it worked fine. But with this drive (Western Digital WDAC31600 1.6 GIG EIDE), I remember reading on -current mailing list that it supported LBA so I just installed the DOS partition using 540 megs and had the drive setted up as LBA Bios Mode. I then just transfered the entire Conner drive contents to the WD. > You certainly either have to get a really good picture about who uses > which figures (BIOS, BSD, other systems on the same disk), or you have > to teach the wdc driver about LBA addressing. Pick your more favorite > choice. :-] Actually, here is the interesting part, I tried putting the drive back in NORMAL mode and the DOS partition boots fine but the Booteasy menu still does the same thing so I boot from the second drive and tell it to boot wd(0,a)/kernel and it says something about the cylinder count greater than 1023 and didn't boot but would putting the drive back in NORMAL and then bootstrap actually solve this problem? > (Btw., this wasn't a question of the BSD bootstrap from the beginning, > that's why disklabel -B didn't change the behaviour.) Hmmm, I thought I messed up the bootstrap somehow since the booteasy menu came up as someone I know with the same drive has it in LBA mode and the drive boots FreeBSD without any problems. Vince From owner-freebsd-current Mon Jul 22 20:03:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA08388 for current-outgoing; Mon, 22 Jul 1996 20:03:35 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA08370 for ; Mon, 22 Jul 1996 20:03:27 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id UAA02759 for ; Mon, 22 Jul 1996 20:03:09 -0700 (PDT) To: current@freebsd.org Subject: 2.2 SNAP soon? Date: Mon, 22 Jul 1996 20:03:09 -0700 Message-ID: <2757.838090989@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Now that 2.1.5 is off my plate, I can focus my attentions on 2.2 again and am wondering if we're about due for another SNAP. If we're going to switch compilers anytime soon, I'd also like that to happen before the SNAP since this is going to be another CD version (the last was on May 1st, 1996) - shall we shoot for August 1st, thereabouts? Anybody got any burning issues they'd like to deal with before I do this? Jordan From owner-freebsd-current Mon Jul 22 20:12:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA08922 for current-outgoing; Mon, 22 Jul 1996 20:12:23 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA08912; Mon, 22 Jul 1996 20:12:20 -0700 (PDT) Message-Id: <199607230312.UAA08912@freefall.freebsd.org> To: "Jordan K. Hubbard" cc: current@freebsd.org Subject: Re: 2.2 SNAP soon? In-reply-to: Your message of "Mon, 22 Jul 1996 20:03:09 PDT." <2757.838090989@time.cdrom.com> Date: Mon, 22 Jul 1996 20:12:20 -0700 From: "Justin T. Gibbs" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Now that 2.1.5 is off my plate, I can focus my attentions on 2.2 again >and am wondering if we're about due for another SNAP. If we're going >to switch compilers anytime soon, I'd also like that to happen before >the SNAP since this is going to be another CD version (the last was on >May 1st, 1996) - shall we shoot for August 1st, thereabouts? Anybody >got any burning issues they'd like to deal with before I do this? > > Jordan I have a whole slew of SCSI changes in the pipe that, although they should fix quite a few problems, do have the potential of breaking a very important sub-system. They should be in soon (I want to get them reviewed first), but I don't want them to come in just a day or two before you do a snapshot. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Mon Jul 22 20:32:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA09930 for current-outgoing; Mon, 22 Jul 1996 20:32:48 -0700 (PDT) Received: from wgrobez1.remote.louisville.edu (root@wgrobez1.remote.louisville.edu [136.165.243.183]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA09925 for ; Mon, 22 Jul 1996 20:32:36 -0700 (PDT) Received: from localhost (wangel@localhost) by wgrobez1.remote.louisville.edu (8.7.5/8.6.12) with SMTP id XAA00297 for ; Mon, 22 Jul 1996 23:32:12 -0400 (EDT) Date: Mon, 22 Jul 1996 23:32:10 -0400 (EDT) From: Gary Roberts To: current@freebsd.org Subject: Re: 2.2 SNAP soon? In-Reply-To: <2757.838090989@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Jul 1996, Jordan K. Hubbard wrote: > Now that 2.1.5 is off my plate, I can focus my attentions on 2.2 again > and am wondering if we're about due for another SNAP. If we're going > to switch compilers anytime soon, I'd also like that to happen before > the SNAP since this is going to be another CD version (the last was on > May 1st, 1996) - shall we shoot for August 1st, thereabouts? Anybody > got any burning issues they'd like to deal with before I do this? > > Jordan > > I see no problems what so ever with an August 1st release. One question tho, I noticed talk about vfat or fat32, maybe we should perhaps include that in the next SNAP ? Just my 2 cents. Gary From owner-freebsd-current Mon Jul 22 21:26:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA12675 for current-outgoing; Mon, 22 Jul 1996 21:26:53 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA12665 for ; Mon, 22 Jul 1996 21:26:46 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id VAA02963; Mon, 22 Jul 1996 21:26:16 -0700 (PDT) To: Gary Roberts cc: current@freebsd.org Subject: Re: 2.2 SNAP soon? In-reply-to: Your message of "Mon, 22 Jul 1996 23:32:10 EDT." Date: Mon, 22 Jul 1996 21:26:16 -0700 Message-ID: <2961.838095976@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I see no problems what so ever with an August 1st release. One question > tho, I noticed talk about vfat or fat32, maybe we should perhaps include > that in the next SNAP ? Were you reading the same talk I was? ;-) Robert seems to have indicated that this was months away in his last message. Jordan From owner-freebsd-current Tue Jul 23 02:04:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA29819 for current-outgoing; Tue, 23 Jul 1996 02:04:33 -0700 (PDT) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA29814 for ; Tue, 23 Jul 1996 02:04:28 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.7.5/8.6.9) with SMTP id KAA07511; Tue, 23 Jul 1996 10:03:26 +0100 (BST) Date: Tue, 23 Jul 1996 10:03:25 +0100 (BST) From: Developer To: Joerg Wunsch cc: FreeBSD-current users Subject: Re: Termcap problems In-Reply-To: <199607222015.WAA05286@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Jul 1996, J Wunsch wrote: > As Developer wrote: > > > I`m having a little problem with the termcap. If the xwindow width is > > particular sizes (Not sure which ones, but always larger than 80 char) > > then commands (like ls) think the window width is different (wider) than > > it actually is, and so the formatting really messes up. > > What makes you think they thought of a different size? > > Programs like ls usually get the window geometry out of the struct > winsize. Usually what happens when the problem occurs is ls prints more characters per line than it should - e.g. all the lines wrap a little onto the next line!! Regards. Trefor S. From owner-freebsd-current Tue Jul 23 02:31:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA01556 for current-outgoing; Tue, 23 Jul 1996 02:31:57 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA01512; Tue, 23 Jul 1996 02:31:41 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id SAA24449; Tue, 23 Jul 1996 18:08:47 +1000 Date: Tue, 23 Jul 1996 18:08:47 +1000 From: Bruce Evans Message-Id: <199607230808.SAA24449@godzilla.zeta.org.au> To: pst@shockwave.com, rnordier@iafrica.com Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? Cc: current@FreeBSD.org, hackers@FreeBSD.org, jkh@time.cdrom.com Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >myself. However, the most serious FreeBSD msdosfs problem (where >it causes corruption to other partitions) apparently needs a >64-cluster FIPS-ed FAT filesystem with an EIDE controller translating >to 64 heads, 63 sectors to be readily reproducible. (At least, I >haven't reproduced it on any other 64-cluster filesystems.) I think you're saying that it is a hardware problem :-). Bruce From owner-freebsd-current Tue Jul 23 02:33:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA01706 for current-outgoing; Tue, 23 Jul 1996 02:33:13 -0700 (PDT) Received: (from julian@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA01679; Tue, 23 Jul 1996 02:33:10 -0700 (PDT) Date: Tue, 23 Jul 1996 02:33:10 -0700 (PDT) From: Julian Elischer Message-Id: <199607230933.CAA01679@freefall.freebsd.org> To: current, hackers Subject: anyone have a clue on this bug? Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk It's bitten us several times on recent -current machines.. due to some problem, a system dies.. (bad h/w or whatever..) on reboot it is discovered that some the files that were open at the time of the reboot have been deleted by fsck (i.e. they had 0 references or something) it's particulary annoying when it deletes the console or some other useful device.. I've mainly seen it with devices, but I think I have also seen directories mutating into devices and files doing other odd things.. this is all with a 3 week old -current.. I will be upgrading the systems in the next day or so.. so if it's known but fixed.. I'll get it then.. julian From owner-freebsd-current Tue Jul 23 02:55:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA03433 for current-outgoing; Tue, 23 Jul 1996 02:55:58 -0700 (PDT) Received: from perki0.connect.com.au (perki0.connect.com.au [192.189.54.85]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA03414 for ; Tue, 23 Jul 1996 02:55:25 -0700 (PDT) Received: (from Unemeton@localhost) by perki0.connect.com.au id TAA13598 (8.7.5/IDA-1.6); Tue, 23 Jul 1996 19:47:49 +1000 (EST) X-Authentication-Warning: perki0.connect.com.au: Unemeton set sender to giles@nemeton.com.au using -f >Received: from localhost (giles@localhost [127.0.0.1]) by nemeton.com.au (8.6.12/8.6.9) with SMTP id TAA08246; Tue, 23 Jul 1996 19:26:17 +1000 Message-Id: <199607230926.TAA08246@nemeton.com.au> To: "Rodney W. Grimes" cc: amir@neuron.net (Amir Y. Rosenblatt), freebsd-current@freebsd.org Subject: Re: SCSI errors and repeated panics In-reply-to: <199607222102.OAA19362@GndRsh.aac.dev.com> Date: Tue, 23 Jul 1996 19:23:32 +1000 From: Giles Lean Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Jul 1996 14:02:19 -0700 (PDT) "Rodney W. Grimes" wrote: > Humm... I suspect that the HP C1533 DAT drive has active terminators The C1533 drives I've seen don't have termination. They can however provide termination power to the SCSI bus and the documentation talks about this, so it is pretty easy to get confused. I certainly was. :-( Giles From owner-freebsd-current Tue Jul 23 04:20:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA08191 for current-outgoing; Tue, 23 Jul 1996 04:20:03 -0700 (PDT) Received: from wgrobez1.remote.louisville.edu (root@wgrobez1.remote.louisville.edu [136.165.243.183]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA08126 for ; Tue, 23 Jul 1996 04:19:58 -0700 (PDT) Received: from localhost (wangel@localhost) by wgrobez1.remote.louisville.edu (8.7.5/8.6.12) with SMTP id HAA02042 for ; Tue, 23 Jul 1996 07:20:00 -0400 (EDT) Date: Tue, 23 Jul 1996 07:19:59 -0400 (EDT) From: Gary Roberts To: freebsd-current@freebsd.org Subject: Re: 2.2 SNAP soon? In-Reply-To: <2961.838095976@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Jul 1996, Jordan K. Hubbard wrote: > > I see no problems what so ever with an August 1st release. One question > > tho, I noticed talk about vfat or fat32, maybe we should perhaps include > > that in the next SNAP ? > > Were you reading the same talk I was? ;-) Robert seems to have indicated > that this was months away in his last message. > > Jordan > Then I read it wrong, I thought he said he was getting close =) From owner-freebsd-current Tue Jul 23 05:11:22 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA09849 for current-outgoing; Tue, 23 Jul 1996 05:11:22 -0700 (PDT) Received: from eac.iafrica.com (h196-7-192-139.iafrica.com [196.7.192.139]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA09813; Tue, 23 Jul 1996 05:11:04 -0700 (PDT) Received: (from rnordier@localhost) by eac.iafrica.com (8.6.12/8.6.12) id NAA00292; Tue, 23 Jul 1996 13:45:26 +0200 From: Robert Nordier Message-Id: <199607231145.NAA00292@eac.iafrica.com> Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? To: bde@zeta.org.au (Bruce Evans) Date: Tue, 23 Jul 1996 13:45:25 +0200 (SAT) Cc: current@freebsd.org, hackers@freebsd.org In-Reply-To: <199607230808.SAA24449@godzilla.zeta.org.au> from "Bruce Evans" at Jul 23, 96 06:08:47 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Bruce Evans wrote: > > >myself. However, the most serious FreeBSD msdosfs problem (where > >it causes corruption to other partitions) apparently needs a > >64-cluster FIPS-ed FAT filesystem with an EIDE controller translating > >to 64 heads, 63 sectors to be readily reproducible. (At least, I > >haven't reproduced it on any other 64-cluster filesystems.) > > I think you're saying that it is a hardware problem :-). > > Bruce > Over a few months, I've been collecting drive and DOS fs parameters when users have reported corruption to *BSD partitions after accessing (mounting/reading: not necessarily writing to) their DOS filesystems using msdosfs. The details I have (from 4 users) are summarized below. Incomplete details from 2 further users also indicate /dev/wd? and 400M+ partition sizes (but I'm not sure about the 64/63 geometry). I don't currently have easy access to an IDE setup supporting more than 16 heads. Through fairly devious means, I have tried formatting various DOS filesystems _as if_ they were originally created on such as setup (and then FIPS-ed), but this doesn't reproduce the problem. DRIVE DOS START DOS END cyl head sect || cyl head sect cyl head sect size ------------------------------------------------------------------- wd0 | 525 | 64 | 63 || 0 | 1 | 1 | 126 | 63 | 63 | 512001 wd0 | 2099 | 64 | 63 || 0 | 1 | 1 | 189 | 63 | 63 | 766017 same drive || 250 | 0 | 1 | 523 | 63 | 63 | 1104768 wd0 | 788 | 64 | 63 || 0 | 1 | 1 | 787 | 63 | 63 | 3177153 wd0 | 621 | 64 | 63 || 0 | 1 | 1 | 619 | 63 | 63 | 2499777 -- Robert Nordier From owner-freebsd-current Tue Jul 23 05:18:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA10001 for current-outgoing; Tue, 23 Jul 1996 05:18:26 -0700 (PDT) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA09955; Tue, 23 Jul 1996 05:15:50 -0700 (PDT) Received: from schubert.Promo.DE by mail.crl.com with SMTP id AA19940 (5.65c/IDA-1.5); Tue, 23 Jul 1996 05:15:04 -0700 Received: from quick.promo.de (quick.Promo.DE [194.45.188.67]) by schubert.promo.de (8.6.12/8.6.12) with SMTP id KAA20515; Tue, 23 Jul 1996 10:31:41 +0200 Message-Id: Date: 23 Jul 1996 10:32:08 +0200 From: "Stefan Bethke" Subject: Re: ncr53c810 driver in sta To: jkh@FreeBSD.org, "Stefan Esser" Cc: current@FreeBSD.org, dg@root.com, "Marc G. Fournier" , stable@FreeBSD.org X-Mailer: Mail*Link SMTP-QM 3.0.2 Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; Name="Message Body" Content-Transfer-Encoding: quoted-printable Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk We have a similiar problem here: Asus SP3G-II (Neptune II chipset), 810, = Quantum Fireball, but I'm not sure it is related to the 810 in any way. It hangs sometimes on reboots, after clearing the screen. However, when = it does, it corrupts the BIOS nvram, so I have to re-enter all BIOS = settings :-( Currently, I always halt the machine and do a reset; this never caused = the problem to occur. > Ok. I guess Jordan is reading this anyway: > Please provide me with details: > 1) does the system complete the final sync ? > 2) does it clear the screen in preparation of a warm boot ? > 3) does it require a power-off or can it be made to boot > by some other means (Ctl-Alt-Del) ? > 4) does it always hang ? > 5) do you know that the hang is not caused by some unrelated > problem (BROKEN_KEYBOARD_RESET comes to mind :) ? Can you give me a pointer where to find an explanation of the broken = reset? Stefan -- Promo Datentechnik | Tel. +49-40-431360-0 + Systemberatung GmbH | Fax. +49-40-431360-60 Waterloohain 6-8 | e-mail: stefan@Promo.DE D-22769 Hamburg | http://www.Promo.DE/ From owner-freebsd-current Tue Jul 23 06:42:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA13929 for current-outgoing; Tue, 23 Jul 1996 06:42:59 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA13924 for ; Tue, 23 Jul 1996 06:42:47 -0700 (PDT) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id PAA02116 for ; Tue, 23 Jul 1996 15:38:35 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id PAA29995 for freebsd-current@freefall.cdrom.com; Tue, 23 Jul 1996 15:52:10 +0200 Date: Tue, 23 Jul 1996 15:52:10 +0200 From: "Christoph P. Kukulies" Message-Id: <199607231352.PAA29995@gilberto.physik.rwth-aachen.de> To: freebsd-current@freefall.FreeBSD.org Subject: contrib (Makefile missing?) Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I wonder how the /usr/src/Makefile should function upon cleandir in /usr/src/contrib. At least this is hat I'm getting here: rm -f .depend tags ===> contrib make: don't know how to make cleandir. Stop *** Error code 2 Stop. *** Error code 1 Stop. --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Tue Jul 23 07:50:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA17745 for current-outgoing; Tue, 23 Jul 1996 07:50:55 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA17709 for ; Tue, 23 Jul 1996 07:50:44 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id AAA10854; Wed, 24 Jul 1996 00:40:07 +1000 Date: Wed, 24 Jul 1996 00:40:07 +1000 From: Bruce Evans Message-Id: <199607231440.AAA10854@godzilla.zeta.org.au> To: freebsd-current@freefall.freebsd.org, kuku@gilberto.physik.rwth-aachen.de Subject: Re: contrib (Makefile missing?) Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I wonder how the /usr/src/Makefile should function upon cleandir in >/usr/src/contrib. At least this is hat I'm getting here: It shouldn't descend into /usr/src/contrib, and hasn't since this problem was fixed on 27 June. Bruce From owner-freebsd-current Tue Jul 23 08:18:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA19722 for current-outgoing; Tue, 23 Jul 1996 08:18:42 -0700 (PDT) Received: from critter.tfs.com (ip82.image.dk [194.19.141.82]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA19686; Tue, 23 Jul 1996 08:18:27 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id RAA03902; Tue, 23 Jul 1996 17:17:35 +0200 (MET DST) To: Robert Nordier cc: bde@zeta.org.au (Bruce Evans), current@FreeBSD.org, hackers@FreeBSD.org Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? In-reply-to: Your message of "Sat, 23 Jul 1996 13:45:25 +0200." <199607231145.NAA00292@eac.iafrica.com> Date: Tue, 23 Jul 1996 17:17:35 +0200 Message-ID: <3900.838135055@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > DRIVE DOS START DOS END > cyl head sect || cyl head sect cyl head sect size >------------------------------------------------------------------- >wd0 | 525 | 64 | 63 || 0 | 1 | 1 | 126 | 63 | 63 | 512001 >wd0 | 2099 | 64 | 63 || 0 | 1 | 1 | 189 | 63 | 63 | 766017 > same drive || 250 | 0 | 1 | 523 | 63 | 63 | 1104768 >wd0 | 788 | 64 | 63 || 0 | 1 | 1 | 787 | 63 | 63 | 3177153 >wd0 | 621 | 64 | 63 || 0 | 1 | 1 | 619 | 63 | 63 | 2499777 This could be because the drives in question have a version of then "OnTrack" diskmanager that we don't recognize". -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Tue Jul 23 08:40:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA21141 for current-outgoing; Tue, 23 Jul 1996 08:40:34 -0700 (PDT) Received: from mispwoso.nosc.mil (mispwoso.nosc.mil [198.253.27.55]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA21104; Tue, 23 Jul 1996 08:40:24 -0700 (PDT) Received: (from huck@localhost) by mispwoso.nosc.mil (8.7.5/8.7.3) id LAA19629; Tue, 23 Jul 1996 11:39:45 -0400 (EDT) From: Craig Huckabee Message-Id: <199607231539.LAA19629@mispwoso.nosc.mil> Subject: Re: ncr53c810 driver in sta To: stefan@promo.de (Stefan Bethke), jkh@freebsd.org, se@zpr.uni-koeln.de, dg@root.com, scrappy@ki.net Date: Tue, 23 Jul 1996 11:39:45 -0400 (EDT) Cc: current@freebsd.org, stable@freebsd.org In-Reply-To: from Stefan Bethke at "Jul 23, 96 10:32:08 am" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > We have a similiar problem here: Asus SP3G-II (Neptune II chipset), 810, Quantum Fireball, but I'm not sure it is related to the 810 in any way. > > It hangs sometimes on reboots, after clearing the screen. However, when it does, it corrupts the BIOS nvram, so I have to re-enter all BIOS settings :-( > Same problem here: I issue a 'reboot' (or a 'shutdown -r') command. Disk synchs up. Screen goes black. Machine is dead. When I do a cold boot the BIOS nvram is hosed. Machine: ASUS PCI/E-P54NP4 ASUS SC-200 NCR SCSI controller (1) MAXTOR MXT-540SL hard drive (2) HITACHI DK517C-37 hard drives My answers to the questions : > > 1) does the system complete the final sync ? Yes. > > 2) does it clear the screen in preparation of a warm boot ? Yes, screen goes black. > > 3) does it require a power-off or can it be made to boot > > by some other means (Ctl-Alt-Del) ? A cold boot or a reset works. > > 4) does it always hang ? Yes. > > 5) do you know that the hang is not caused by some unrelated > > problem (BROKEN_KEYBOARD_RESET comes to mind :) ? Nope. Thanks, Craig > Currently, I always halt the machine and do a reset; this never caused the problem to occur. > > > Ok. I guess Jordan is reading this anyway: > > > Please provide me with details: > > > 1) does the system complete the final sync ? > > 2) does it clear the screen in preparation of a warm boot ? > > 3) does it require a power-off or can it be made to boot > > by some other means (Ctl-Alt-Del) ? > > 4) does it always hang ? > > 5) do you know that the hang is not caused by some unrelated > > problem (BROKEN_KEYBOARD_RESET comes to mind :) ? > > Can you give me a pointer where to find an explanation of the broken reset? > > Stefan > -- > Promo Datentechnik | Tel. +49-40-431360-0 > + Systemberatung GmbH | Fax. +49-40-431360-60 > Waterloohain 6-8 | e-mail: stefan@Promo.DE > D-22769 Hamburg | http://www.Promo.DE/ > From owner-freebsd-current Tue Jul 23 09:42:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA25315 for current-outgoing; Tue, 23 Jul 1996 09:42:34 -0700 (PDT) Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA25308 for ; Tue, 23 Jul 1996 09:42:30 -0700 (PDT) Received: from localhost (dfr@localhost) by minnow.render.com (8.6.12/8.6.9) with SMTP id OAA16735 for ; Tue, 23 Jul 1996 14:13:46 +0100 Date: Tue, 23 Jul 1996 14:13:45 +0100 (BST) From: Doug Rabson To: current@freebsd.org Subject: Using clustered writes for NFSv3 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In NFSv3, when a buffer is written to a server, normally the server doesn't write the data to stable storage immediately. Instead, it informs the client that the data is written but 'unstable'. The client can later commit the data to stable storage in a seperate call. In FreeBSD's (and anyone else who is using Rick Macklem's code) implementation of NFSv3, this is implemented by turning the buffer into a delayed write buffer, marked with B_DELWRI|B_NEEDCOMMIT. When the buffer is later recycled by the buffer cache or explicitly synced with VOP_FSYNC, the nfs client code notices the B_NEEDCOMMIT flag and performs the appropriate commit call. If a lot of unstable writes are made with NFSv3, this commit operation tends to be done via vfs_bio_awrite when the buffer is recycled. This leads to a large number of more-or-less sequential commit operations which could be combined into one request. In particular for an IRIX 5.3 server, this causes very poor performance copying large files over NFSv3. By a stroke of luck, the existing code for clustered writes in vfs_bio.c and vfs_cluster.c can be made to work for NFSv3 as well. I needed to tweak cluster_wbuild a little to copy over the B_NEEDCOMMIT flag and to set the b_dirtyoff and b_dirtyend fields of the cluster appropriately. Is there any chance I can get this change into -current? The only possible problem with the patch that I can see is the part which copies over the write credentials (required for NFS) to the new buffer. It seems to improve the write performance against an SGI fileserver by a factor of two (with some other NFS patches not included here). Index: vfs_cluster.c =================================================================== RCS file: /home/ncvs/src/sys/kern/vfs_cluster.c,v retrieving revision 1.36 diff -c -r1.36 vfs_cluster.c *** vfs_cluster.c 1996/06/03 04:40:35 1.36 --- vfs_cluster.c 1996/07/23 11:34:27 *************** *** 616,626 **** bp->b_bcount = 0; bp->b_bufsize = 0; bp->b_npages = 0; bp->b_blkno = tbp->b_blkno; bp->b_lblkno = tbp->b_lblkno; (vm_offset_t) bp->b_data |= ((vm_offset_t) tbp->b_data) & PAGE_MASK; ! bp->b_flags |= B_CALL | B_BUSY | B_CLUSTER | (tbp->b_flags & B_VMIO); bp->b_iodone = cluster_callback; pbgetvp(vp, bp); --- 616,630 ---- bp->b_bcount = 0; bp->b_bufsize = 0; bp->b_npages = 0; + if (tbp->b_wcred != NOCRED) { + bp->b_wcred = tbp->b_wcred; + crhold(bp->b_wcred); + } bp->b_blkno = tbp->b_blkno; bp->b_lblkno = tbp->b_lblkno; (vm_offset_t) bp->b_data |= ((vm_offset_t) tbp->b_data) & PAGE_MASK; ! bp->b_flags |= B_CALL | B_BUSY | B_CLUSTER | (tbp->b_flags & (B_VMIO|B_NEEDCOMMIT)); bp->b_iodone = cluster_callback; pbgetvp(vp, bp); *************** *** 632,638 **** break; } ! if ((tbp->b_flags & (B_VMIO|B_CLUSTEROK|B_INVAL|B_BUSY|B_DELWRI)) != (B_DELWRI|B_CLUSTEROK|(bp->b_flags & B_VMIO))) { splx(s); break; } --- 636,647 ---- break; } ! if ((tbp->b_flags & (B_VMIO|B_CLUSTEROK|B_INVAL|B_BUSY|B_DELWRI|B_NEEDCOMMIT)) != (B_DELWRI|B_CLUSTEROK|(bp->b_flags & (B_VMIO|B_NEEDCOMMIT)))) { ! splx(s); ! break; ! } ! ! if (tbp->b_wcred != bp->b_wcred) { splx(s); break; } *************** *** 676,681 **** --- 685,692 ---- pmap_qenter(trunc_page((vm_offset_t) bp->b_data), (vm_page_t *) bp->b_pages, bp->b_npages); totalwritten += bp->b_bufsize; + bp->b_dirtyoff = 0; + bp->b_dirtyend = bp->b_bufsize; bawrite(bp); len -= i; -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 251 4411 FAX: +44 171 251 0939 From owner-freebsd-current Tue Jul 23 10:57:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA29743 for current-outgoing; Tue, 23 Jul 1996 10:57:27 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA29718 for ; Tue, 23 Jul 1996 10:57:18 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id TAA26437; Tue, 23 Jul 1996 19:51:37 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id TAA22323; Tue, 23 Jul 1996 19:51:36 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id TAA10778; Tue, 23 Jul 1996 19:48:32 +0200 (MET DST) From: J Wunsch Message-Id: <199607231748.TAA10778@uriah.heep.sax.de> Subject: Re: Termcap problems To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Tue, 23 Jul 1996 19:48:32 +0200 (MET DST) Cc: dev@fgate.flevel.co.uk (Developer) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Developer at "Jul 23, 96 10:03:25 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Developer wrote: > > What makes you think they thought of a different size? > > > > Programs like ls usually get the window geometry out of the struct > > winsize. > > Usually what happens when the problem occurs is ls prints more characters > per line than it should - e.g. all the lines wrap a little onto the next > line!! What says ``stty -a'' about the window size? For me, everything works well. I've just maximized an xterm, and ls /usr/local/bin (where there are quite many files), and it looks reasonable. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Tue Jul 23 11:32:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA02845 for current-outgoing; Tue, 23 Jul 1996 11:32:31 -0700 (PDT) Received: from relay.hp.com (relay.hp.com [15.255.152.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA02837 for ; Tue, 23 Jul 1996 11:32:30 -0700 (PDT) Received: from srmail.sr.hp.com by relay.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA045546739; Tue, 23 Jul 1996 11:32:19 -0700 Received: from hpnmhjw.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA087476737; Tue, 23 Jul 1996 11:32:18 -0700 Received: from mina.sr.hp.com by hpnmhjw.sr.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA232866737; Tue, 23 Jul 1996 11:32:17 -0700 Message-Id: <199607231832.AA232866737@hpnmhjw.sr.hp.com> To: "Jordan K. Hubbard" Cc: current@freefall.freebsd.org Subject: Re: 2.2 SNAP soon? In-Reply-To: Your message of "Mon, 22 Jul 1996 20:03:09 PDT." Date: Tue, 23 Jul 1996 11:32:16 -0700 From: Darryl Okahata Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Now that 2.1.5 is off my plate, I can focus my attentions on 2.2 again > and am wondering if we're about due for another SNAP. If we're going > to switch compilers anytime soon, I'd also like that to happen before > the SNAP since this is going to be another CD version (the last was on > May 1st, 1996) - shall we shoot for August 1st, thereabouts? Anybody > got any burning issues they'd like to deal with before I do this? I assume that 2.7.2 (or whatever) is "adequately stable/bug-free"? I'd hate to see lots of mysterious kernel and user-land bugs pop-up .... -- Darryl Okahata Internet: darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. From owner-freebsd-current Tue Jul 23 11:58:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA04410 for current-outgoing; Tue, 23 Jul 1996 11:58:19 -0700 (PDT) Received: from prozac.neuron.net (prozac.neuron.net [165.254.1.213]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA04402 for ; Tue, 23 Jul 1996 11:58:16 -0700 (PDT) Received: (from amir@localhost) by prozac.neuron.net (8.7.5/8.6.12) id PAA01110; Tue, 23 Jul 1996 15:08:20 -0400 (EDT) From: "Amir Y. Rosenblatt" Message-Id: <199607231908.PAA01110@prozac.neuron.net> Subject: Re: SCSI errors and repeated panics To: rgrimes@GndRsh.aac.dev.com (Rodney W. Grimes) Date: Tue, 23 Jul 1996 15:08:20 -0400 (EDT) Cc: amir@neuron.net, freebsd-current@freebsd.org In-Reply-To: <199607222102.OAA19362@GndRsh.aac.dev.com> from "Rodney W. Grimes" at Jul 22, 96 02:02:19 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > In your configuration it _must_ be set to c) above... see the diagrams > in the Adaptec manual.... My termination setup is as dictated by the manual. > Humm... I suspect that the HP C1533 DAT drive has active terminators, > ie the resistor value will be 110 ohms, and the NEC CD-ROM is using > passive termination, ie the resitor value will be 220/330 ohm. I highly > recommend (and the SCSI-II spec just recommends) that you use active > termination with Fast SCSI-II. OK -- this morning I switched the DAT drive and the CD-ROM's places in the chain so the DAT drive was at the end and adjusted the termination settings on both accordingly. Then my logs show the following: ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@Jul 23 09:24:28 prozac /kernel: sd0(ahc0:0:0): timed out in dataout phase, SCSISIGI == 0x0 Jul 23 09:24:29 prozac /kernel: ahc0: Issued Channel A Bus Reset #2. 2 SCBs aborted Jul 23 09:24:29 prozac /kernel: ahc0: Issued Channel A Bus Reset #2. 2 SCBs aborted Jul 23 09:24:29 prozac /kernel: es:3 Jul 23 09:24:29 prozac /kernel: es:3 Jul 23 09:24:29 prozac /kernel: sd0(ahc0:0:0): NOT READY asc:4,1 Jul 23 09:24:29 prozac /kernel: sd0(ahc0:0:0): NOT READY asc:4,1 Jul 23 09:24:29 prozac /kernel: sd0(ahc0:0:0): Logical unit is in process of be coming ready field replaceable unit: 2 Jul 23 09:24:29 prozac /kernel: sd0(ahc0:0:0): Logical unit is in process of be coming ready field replaceable unit: 2 etc... for about 5 minutes -- then nothing in the logfile until 4 hours later: Jul 23 09:24:48 prozac /kernel: , retries:4 Jul 23 09:24:48 prozac /kernel: , retries:4 Jul 23 13:53:18 prozac /kernel: mode = 0100600, inum = 23201, fs = /var Jul 23 13:53:18 prozac /kernel: mode = 0100600, inum = 23201, fs = /var Jul 23 13:53:18 prozac /kernel: panic: ffs_valloc: dup alloc Jul 23 13:53:18 prozac /kernel: panic: ffs_valloc: dup alloc Jul 23 13:53:19 prozac /kernel: Jul 23 13:53:19 prozac /kernel: Jul 23 13:53:19 prozac /kernel: syncing disks... 10 9 5 FreeBSD 2.2-CURRENT #0: Sun Jul 21 22:24:59 EDT 1996 And a reboot which lect it sitting until I could run home to fsck all the partitions. I have since disconnected the cd-rom drive altogether. Any further suggestions? It's getting muy frustrating -- any and all ideas are welcome. -Amir From owner-freebsd-current Tue Jul 23 12:13:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA05236 for current-outgoing; Tue, 23 Jul 1996 12:13:21 -0700 (PDT) Received: from american.com (biscayne.american.com [204.253.96.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA05223 for ; Tue, 23 Jul 1996 12:12:59 -0700 (PDT) Received: from muir-woods.american.com (muir-woods.american.com [204.253.96.201]) by american.com (8.6.12/8.6.12) with ESMTP id PAA24912 for ; Tue, 23 Jul 1996 15:12:18 -0400 Received: (from brad@localhost) by muir-woods.american.com (8.6.12/8.6.12) id PAA10790; Tue, 23 Jul 1996 15:12:13 -0400 Date: Tue, 23 Jul 1996 15:12:13 -0400 Message-Id: <199607231912.PAA10790@muir-woods.american.com> From: Brad Parker To: current@freefall.freebsd.org Subject: gcc 2.7.2 + binutils 2.7 on stable? Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I've been trying to build gcc-2.7.2 and binutils 2.7 on a "stable" system (i.e. sup'd from the stable release). I give up. I can't get bfd and ld to do the right thing. Near as I can tell on a 2.1 system "netbsd" style .o's are generated and QMAGIC executables are linked. I can't build an "ld" with binutils 2.7 that does this. judging from the recent current email someone else has done this ;-) can you send me a note on how you did it? (I'm guessing that there is a file missing from ld/emulparams for freebsd... -brad From owner-freebsd-current Tue Jul 23 14:34:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA15464 for current-outgoing; Tue, 23 Jul 1996 14:34:15 -0700 (PDT) Received: from DeepCore.dk (aalb27.pip.dknet.dk [194.192.0.187]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA15306; Tue, 23 Jul 1996 14:33:30 -0700 (PDT) Received: (from sos@localhost) by DeepCore.dk (8.7.5/8.7.3) id XAA00352; Tue, 23 Jul 1996 23:30:50 +0200 (MET DST) Message-Id: <199607232130.XAA00352@DeepCore.dk> Subject: Re: anyone have a clue on this bug? To: julian@freefall.freebsd.org (Julian Elischer) Date: Tue, 23 Jul 1996 23:30:50 +0200 (MET DST) Cc: current@freefall.freebsd.org, hackers@freefall.freebsd.org In-Reply-To: <199607230933.CAA01679@freefall.freebsd.org> from Julian Elischer at "Jul 23, 96 02:33:10 am" From: sos@FreeBSD.org Reply-to: sos@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL15 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In reply to Julian Elischer who wrote: > > It's bitten us several times on recent -current machines.. > > due to some problem, a system dies.. > (bad h/w or whatever..) > on reboot it is discovered that some the files that were open at > the time of the reboot have been deleted by fsck > (i.e. they had 0 references or something) > > it's particulary annoying when it deletes the console or some other > useful device.. I've mainly seen it with devices, > but I think I have also seen directories mutating into devices > and files doing other odd things.. Seems like bad hw, I havn't seen anything like this, except when I tried out DEVFS long ago.... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-current Tue Jul 23 15:09:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA18622 for current-outgoing; Tue, 23 Jul 1996 15:09:03 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA18615; Tue, 23 Jul 1996 15:09:01 -0700 (PDT) Message-Id: <199607232209.PAA18615@freefall.freebsd.org> To: sos@FreeBSD.org cc: julian@freefall.freebsd.org (Julian Elischer), current@freefall.freebsd.org, hackers@freefall.freebsd.org Subject: Re: anyone have a clue on this bug? In-reply-to: Your message of "Tue, 23 Jul 1996 23:30:50 +0200." <199607232130.XAA00352@DeepCore.dk> Date: Tue, 23 Jul 1996 15:09:01 -0700 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >In reply to Julian Elischer who wrote: >> >> It's bitten us several times on recent -current machines.. >> >> due to some problem, a system dies.. >> (bad h/w or whatever..) >> on reboot it is discovered that some the files that were open at >> the time of the reboot have been deleted by fsck >> (i.e. they had 0 references or something) >> >> it's particulary annoying when it deletes the console or some other >> useful device.. I've mainly seen it with devices, >> but I think I have also seen directories mutating into devices >> and files doing other odd things.. > >Seems like bad hw, I havn't seen anything like this, except when I >tried out DEVFS long ago.... I've seen fsck eat things I didn't think it should have before. I never looked into fsck itself though, I just fixed the bugs in my driver that would cause hangs. 8-( >-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- >Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team > Even more code to hack -- will it ever end >.. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Tue Jul 23 15:25:32 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA19819 for current-outgoing; Tue, 23 Jul 1996 15:25:32 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA19800; Tue, 23 Jul 1996 15:25:26 -0700 (PDT) Received: from rah.star-gate.com (localhost.cdrom.com [127.0.0.1]) by rah.star-gate.com (8.7.5/8.7.3) with ESMTP id PAA07706; Tue, 23 Jul 1996 15:25:11 -0700 (PDT) Message-Id: <199607232225.PAA07706@rah.star-gate.com> X-Mailer: exmh version 1.6.5 12/11/95 To: "Justin T. Gibbs" cc: sos@FreeBSD.ORG, julian@freefall.freebsd.org (Julian Elischer), current@freefall.freebsd.org, hackers@freefall.freebsd.org Subject: Re: anyone have a clue on this bug? In-reply-to: Your message of "Tue, 23 Jul 1996 15:09:01 PDT." <199607232209.PAA18615@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Jul 1996 15:25:10 -0700 From: Amancio Hasty Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >From The Desk Of "Justin T. Gibbs" : > I've seen fsck eat things I didn't think it should have before. I never > looked into fsck itself though, I just fixed the bugs in my driver that > would cause hangs. 8-( And you have done and darn good job . Currently, running FreeBSD-current with my adaptec 2940UW, a Seagate 4.1gb Wide scsi and few a other scsi devices 8) Tnks! Amancio From owner-freebsd-current Tue Jul 23 16:51:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA24860 for current-outgoing; Tue, 23 Jul 1996 16:51:15 -0700 (PDT) Received: from wgrobez1.remote.louisville.edu (root@wgrobez1.remote.louisville.edu [136.165.243.183]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA24850 for ; Tue, 23 Jul 1996 16:51:08 -0700 (PDT) Received: from localhost (wangel@localhost) by wgrobez1.remote.louisville.edu (8.7.5/8.6.12) with SMTP id TAA04448 for ; Tue, 23 Jul 1996 19:51:25 -0400 (EDT) Date: Tue, 23 Jul 1996 19:51:24 -0400 (EDT) From: Gary Roberts To: freebsd-current@freebsd.org Subject: SharedMem. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hey all. I keep getting errors complaining about not finding any 'shared' memory. I get the error the most on linux apps when I run them ... I've included all the SYSV declarations in the kernel config file, any idea what's going on ? Thanks Gary From owner-freebsd-current Tue Jul 23 17:54:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA28650 for current-outgoing; Tue, 23 Jul 1996 17:54:09 -0700 (PDT) Received: from mixer.visi.com (nordquis@mixer.visi.com [204.73.178.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA28645 for ; Tue, 23 Jul 1996 17:54:04 -0700 (PDT) Received: (from nordquis@localhost) by mixer.visi.com (8.7.4/8.7.5) id TAA06681; Tue, 23 Jul 1996 19:53:45 -0500 (CDT) From: "Brent J. Nordquist" Posted-Date: Tue, 23 Jul 1996 19:53:45 -0500 (CDT) Message-Id: <199607240053.TAA06681@mixer.visi.com> Subject: Re: cu(1) stopped working? To: joerg_wunsch@uriah.heep.sax.de Date: Tue, 23 Jul 1996 19:53:45 -0500 (CDT) Cc: freebsd-current@freebsd.org In-Reply-To: <199607210744.JAA05208@uriah.heep.sax.de> from "J Wunsch" at Jul 21, 96 09:44:56 am Reply-to: nordquis@visi.com (Brent J. Nordquist) X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk | > And yes, I have been meaning to switch to tip anyway... looks like | > now is the time. Just wanted everyone to have my one data point on | > this. | | Do you have any reason to switch to tip? I find the Taylor config | files much more intelligible than all the /etc/remote etc. stuff. No, other than the fact the the man page seems to be encouraging me to do so. ;-) I've used cu since the old days... Thanks for the response explaining /etc/uucp from make world... I'll do a little more poking around and see what I turn up. -- Brent J. Nordquist nordquis@winternet.com +1 612 827-2747 From owner-freebsd-current Tue Jul 23 18:21:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA00141 for current-outgoing; Tue, 23 Jul 1996 18:21:46 -0700 (PDT) Received: from prozac.neuron.net (prozac.neuron.net [165.254.1.213]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA00132 for ; Tue, 23 Jul 1996 18:21:43 -0700 (PDT) Received: (from amir@localhost) by prozac.neuron.net (8.7.5/8.6.12) id VAA00646 for freebsd-current@freebsd.org; Tue, 23 Jul 1996 21:32:09 -0400 (EDT) From: "Amir Y. Rosenblatt" Message-Id: <199607240132.VAA00646@prozac.neuron.net> Subject: more on SCSI problems To: freebsd-current@freebsd.org Date: Tue, 23 Jul 1996 21:32:08 -0400 (EDT) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Well, despite the CD-ROM drive now being disconnected, as I sat here I heard a couple clicking sounds from the hard drives and beforew I could tail the messages file the machine rebooted. A later look at the messages file showed it didn't even panic -- it just *click* rebooted. I tried bringing it back up; fscked the disks, but as soon as it started syslog I got dropped into the debugger: spec_getpages: I/O read error vm_fault: pager input (probably hardware) error, PID 80 failure Fatal trap 12: page fault while in kernel mode fault virtual address = 0xf602c000 fault code = supervisor read, page not present instruction pointer = 0x8:0xf0108877 stack pointer = 0x10:0xefbffde0 frame pointer = 0x10:0xefbffe0c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume IOPL=0 current process = 80 (sh) interrupt mask = kernel: type 12 trap, code=0 stopped at _exec_aout_imgact+0x17: movl 0(%esi), %edx I rebooted and this time brought up the Adaptec BIOS setup program. Double-checked the settings and then turned off Wide-Negotiation for the tape drive. It's never caused a proibelm before to have it turned on but maybe the newer aic7xxx driver is more sensitive to that stuff. Couldn;t hurt. Any other suggestions? -Amir From owner-freebsd-current Tue Jul 23 19:30:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA04257 for current-outgoing; Tue, 23 Jul 1996 19:30:34 -0700 (PDT) Received: from prozac.neuron.net (prozac.neuron.net [165.254.1.213]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA04247 for ; Tue, 23 Jul 1996 19:30:31 -0700 (PDT) Received: (from amir@localhost) by prozac.neuron.net (8.7.5/8.6.12) id WAA00294 for freebsd-current@freebsd.org; Tue, 23 Jul 1996 22:41:05 -0400 (EDT) From: "Amir Y. Rosenblatt" Message-Id: <199607240241.WAA00294@prozac.neuron.net> Subject: A new twist on the reboot problems To: freebsd-current@freebsd.org Date: Tue, 23 Jul 1996 22:41:05 -0400 (EDT) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Well, for the second time tonight, prozac rebooted A look at syslog around the time of the first reboot shows no errors, no panic, no nuthin. Just *click*. There had been a slew of the usual scsi errors about an hour and a half before the reboot, but when the reboot itself hit there was nothing. No errors, no panics. I disabled WIDE NEGOTIATION on the 2940UW and brought prozac back online. This time there were no scsi errors (hopefully that means that problem is solved). /var/log/messages had the following though: ------ Jul 23 22:30:30 prozac /kernel: dev = 0x20405, block = 300, fs = /var/mail Jul 23 22:30:31 prozac /kernel: panic: blkfree: freeing free block Jul 23 22:30:31 prozac /kernel: Jul 23 22:30:31 prozac /kernel: syncing disks... 15 15 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 FreeBSD 2.2-CURRENT #0: Sun Jul 21 22:24:59 EDT 1996 ------ Any suggestions? -Amir From owner-freebsd-current Tue Jul 23 21:16:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA11153 for current-outgoing; Tue, 23 Jul 1996 21:16:08 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA11102 for ; Tue, 23 Jul 1996 21:15:58 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with SMTP id WAA08760; Tue, 23 Jul 1996 22:11:52 -0600 (MDT) Message-Id: <199607240411.WAA08760@rover.village.org> To: Darryl Okahata Subject: Re: 2.2 SNAP soon? Cc: "Jordan K. Hubbard" , current@freefall.freebsd.org In-reply-to: Your message of Tue, 23 Jul 1996 11:32:16 PDT Date: Tue, 23 Jul 1996 22:11:51 -0600 From: Warner Losh Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk : I assume that 2.7.2 (or whatever) is "adequately stable/bug-free"? : I'd hate to see lots of mysterious kernel and user-land bugs pop-up .... I'd recommend that we use 2.7.3 (or the set of patches that is ready to go for that) if we do a snap on a non 2.6 compiler. There are a lot of bugs fixed in that that people tripped over on intel. Warner From owner-freebsd-current Tue Jul 23 21:29:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA12642 for current-outgoing; Tue, 23 Jul 1996 21:29:25 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA12637 for ; Tue, 23 Jul 1996 21:29:23 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.5/8.7.3) with ESMTP id VAA00920; Tue, 23 Jul 1996 21:29:19 -0700 (PDT) Message-Id: <199607240429.VAA00920@austin.polstra.com> To: brad@american.com Cc: freebsd-current@freebsd.org Subject: Re: gcc 2.7.2 + binutils 2.7 on stable? In-reply-to: <199607231912.PAA10790@muir-woods.american.com> Date: Tue, 23 Jul 1996 21:29:19 -0700 From: John Polstra Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I've been trying to build gcc-2.7.2 and binutils 2.7 on a "stable" > system (i.e. sup'd from the stable release). I give up. I can't > get bfd and ld to do the right thing. Give it up, unless you have a lot of time, a lot of patience, and some experience writing language tools. The linker in GNU binutils doesn't come close to supporting FreeBSD. For starters, there's absolutely no support for our shared libraries. You can use gcc-2.7.2 with the native FreeBSD assembler and linker, provided that you modify gcc slightly so that it doesn't try to use weak symbols. (Our assembler doesn't support weak symbols.) To do that, find the #define of "ASM_WEAKEN_LABEL" in "config/i386/freebsd.h", and delete it. There have been some reports of problems with C++ after doing that, but the reports were rather vague, and I am not sure what, if anything, was actually the problem. As another option: Reportedly, it's not that hard to get just the assembler from binutils working for FreeBSD. Our linker seems to support weak symbols, so if you can get the binutils assembler working, then you should be able to use it with the stock gcc-2.7.2 and the native linker. Finally, you may wish to wait a couple of weeks. Peter Wemm is poised to bring the latest version of gcc into our source tree. He has been holding off, because rumor has it that gcc-2.7.3 is just around the corner. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-current Tue Jul 23 22:20:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA15991 for current-outgoing; Tue, 23 Jul 1996 22:20:27 -0700 (PDT) Received: from gw.itfs.nsk.su (gw.itfs.nsk.su [193.124.36.33]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA15981 for ; Tue, 23 Jul 1996 22:20:19 -0700 (PDT) Received: from itfs.UUCP (uucp@localhost) by gw.itfs.nsk.su (8.6.12/8.6.12) with UUCP id MAA16989 for current@freebsd.org; Wed, 24 Jul 1996 12:20:11 +0700 Received: by itfs.nsk.su; Wed, 24 Jul 96 12:13:23 +0700 (NST) Received: (from daemon@localhost) by news.itfs.nsk.su (8.6.12/8.6.12) id MAA08199; Wed, 24 Jul 1996 12:02:19 +0700 From: nnd@itfs.nsk.su (Nickolay N. Dudorov) To: current@freebsd.org Subject: Current , and POSIX (?) Message-ID: Date: Wed, 24 Jul 1996 05:02:15 GMT Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk There are two (mainly identical) #include s in current to deal with directory entries: and Both of them require #include for compilation. I was told (in qmail-beta mailing list) that by POSIX it is not necessary to include to use . Could someone POSIXly-impaired (:-) confirm that ? BTW, in NetBSD-current(?) contains #include just before #include (I see it in file with /* $NetBSD: dirent.h,v 1.10 1995/12/05 03:09:19 jtc Exp $ */ and * @dirent.h 8.2 (Berkeley) 7/28/94 and in FreeBSD-current there is * @dirent.h 8.1 (Berkeley) 6/8/93 ) N.Dudorov From owner-freebsd-current Wed Jul 24 00:05:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA22155 for current-outgoing; Wed, 24 Jul 1996 00:05:11 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@mindbender.headcandy.com [199.238.225.168]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA22148 for ; Wed, 24 Jul 1996 00:05:07 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.7.3) with SMTP id AAA11312; Wed, 24 Jul 1996 00:04:51 -0700 (PDT) Message-Id: <199607240704.AAA11312@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: "Amir Y. Rosenblatt" cc: freebsd-current@freebsd.org Subject: Re: A new twist on the reboot problems In-reply-to: Your message of Tue, 23 Jul 96 22:41:05 -0400. <199607240241.WAA00294@prozac.neuron.net> Date: Wed, 24 Jul 1996 00:04:49 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Well, for the second time tonight, prozac rebooted A look at syslog >around the time of the first reboot shows no errors, no panic, no nuthin. >Just *click*. There had been a slew of the usual scsi errors about an >hour and a half before the reboot, but when the reboot itself hit there >was nothing. No errors, no panics. Incidentally, if you want to be *sure* you capture all panic output, you might consider putting a comconsole into your kernel and hooking a serial terminal with scrollback and/or logging (old PC running kermit works fine) up to be the console. Then, no matter what gets written, or not written, before the machine freaks out, and before fsck "cleans" everything, you have it all logged on a separate machine. >I disabled WIDE NEGOTIATION on the 2940UW and brought prozac back online. >This time there were no scsi errors (hopefully that means that problem is >solved). /var/log/messages had the following though: >------ >Jul 23 22:30:30 prozac /kernel: dev = 0x20405, block = 300, fs = /var/mail >Jul 23 22:30:31 prozac /kernel: panic: blkfree: freeing free block >Jul 23 22:30:31 prozac /kernel: >Jul 23 22:30:31 prozac /kernel: syncing disks... 15 15 2 1 1 1 1 1 1 1 1 >1 1 1 1 1 1 1 1 FreeBSD 2.2-CURRENT #0: Sun Jul 21 22:24:59 EDT 1996 >------ Out of curiosity, do you have "options DIAGNOSTIC" in your kernel? If so, remove it, rebuild, reinstall. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@HeadCandy.com --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... Roll your own Internet access -- Seattle People's Internet cooperative. If you're in the Seattle area, ask me how. ----------------------------------------------------------------------------- From owner-freebsd-current Wed Jul 24 01:11:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA28395 for current-outgoing; Wed, 24 Jul 1996 01:11:39 -0700 (PDT) Received: from zed.ludd.luth.se (root@zed.ludd.luth.se [130.240.16.33]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA28355 for ; Wed, 24 Jul 1996 01:11:28 -0700 (PDT) Received: from zen.ludd.luth.se (zen.ludd.luth.se [130.240.16.34]) by zed.ludd.luth.se (8.7.5/8.7.2) with ESMTP id KAA05214; Wed, 24 Jul 1996 10:10:59 +0200 From: Joakim Henriksson Received: (murduth@localhost) by zen.ludd.luth.se (8.6.11/8.6.11) id KAA01568; Wed, 24 Jul 1996 10:10:58 +0200 Message-Id: <199607240810.KAA01568@zen.ludd.luth.se> Subject: Re: gcc 2.7.2 + binutils 2.7 on stable? To: jdp@polstra.com (John Polstra) Date: Wed, 24 Jul 1996 10:10:57 +0200 (EET DST) Cc: freebsd-current@freebsd.org In-Reply-To: <199607240429.VAA00920@austin.polstra.com> from "John Polstra" at Jul 23, 96 09:29:19 pm Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > As another option: Reportedly, it's not that hard to get just the > assembler from binutils working for FreeBSD. Our linker seems to > support weak symbols, so if you can get the binutils assembler working, > then you should be able to use it with the stock gcc-2.7.2 and the > native linker. Yeah, the assembler isn't to hard to compile. But g++ still generates code that the native ld can't handle :( But gcc seems to behave. regards/ Joakim From owner-freebsd-current Wed Jul 24 01:28:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA01422 for current-outgoing; Wed, 24 Jul 1996 01:28:46 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA01387 for ; Wed, 24 Jul 1996 01:28:38 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id SAA16182; Wed, 24 Jul 1996 18:11:17 +1000 Date: Wed, 24 Jul 1996 18:11:17 +1000 From: Bruce Evans Message-Id: <199607240811.SAA16182@godzilla.zeta.org.au> To: current@freebsd.org, nnd@itfs.nsk.su Subject: Re: Current , and POSIX (?) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I was told (in qmail-beta mailing list) that by POSIX >it is not necessary to include to use >. >Could someone POSIXly-impaired (:-) confirm that ? No, POSIX.1 section 4.1.2.1 requires to be included before , even though the interfaces defined in don't depend explictly on any of the types declared in (most POSIX interfaces do depend on these types so the requirement for is obvious). The old BSD happened not to depend on any of the types in . This changed in BSD4.4Lite2. >BTW, in NetBSD-current(?) contains >#include just before #include I think NetBSD attempts to conform to X/OPEN and X/OPEN does require it. FreeBSD's doesn't conform to POSIX anyway. Even if _POSIX_SOURCE is defined, it #defines many application identifiers: DTTOIF, DT_BLK, many other DT_'s, IFTODT. Only application identifiers beginning with d_ or ending with _t are reserved for (they shall not be declared or defined for the application). FreeBSD's also fails to confrom to POSIX. Even if _POSIX_SOURCE is defined, it #defines many application identifiers: BIG_ENDIAN, BYTE_ORDER, HTONL, HTONS, LITTLE_ENDIAN NTOHL, NTOHS, PDP_ENDIAN, htonl, htons, ntohl, ntohs. and it declares one system identifier that doesn't belong here: lseek. Bruce From owner-freebsd-current Wed Jul 24 03:38:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA11360 for current-outgoing; Wed, 24 Jul 1996 03:38:53 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA11351 for ; Wed, 24 Jul 1996 03:38:49 -0700 (PDT) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id MAA16219 for ; Wed, 24 Jul 1996 12:34:17 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id MAA03005 for freebsd-current@freefall.cdrom.com; Wed, 24 Jul 1996 12:47:51 +0200 Date: Wed, 24 Jul 1996 12:47:51 +0200 From: "Christoph P. Kukulies" Message-Id: <199607241047.MAA03005@gilberto.physik.rwth-aachen.de> To: freebsd-current@freefall.FreeBSD.org Subject: ___runetype ? ctype problem Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I was off for two weeks and I'm trying to keep up with -current and get through make world. What stops me now is that compilation of ctype.h fails with some runetype related error. Am I missing some recent fix regarding this or what? --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Wed Jul 24 04:05:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA12634 for current-outgoing; Wed, 24 Jul 1996 04:05:51 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA12629 for ; Wed, 24 Jul 1996 04:05:49 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id EAA03234 for ; Wed, 24 Jul 1996 04:05:46 -0700 Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id MAA16587 for ; Wed, 24 Jul 1996 12:57:20 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id NAA03054 for freebsd-current@freefall.cdrom.com; Wed, 24 Jul 1996 13:10:50 +0200 Date: Wed, 24 Jul 1996 13:10:50 +0200 From: "Christoph P. Kukulies" Message-Id: <199607241110.NAA03054@gilberto.physik.rwth-aachen.de> To: freebsd-current@freefall.FreeBSD.org Subject: Re: A couple of problems!! Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I'm back from a two weeks vacation and wading through the 4500 mail messages I found some people pointing out problems with sup.de.freebsd.org (my responsibility). I'm hoping getting things fixed soon. sups often didn't finish since some US supservers were out of order or connections were slow. Also the volume (gcc changes ?) was tremendous. sup often never finished so that supscan wasn't run. --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Wed Jul 24 05:01:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA15600 for current-outgoing; Wed, 24 Jul 1996 05:01:48 -0700 (PDT) Received: from freebsd.gaffaneys.com (dialup10.gaffaneys.com [134.129.252.29]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA15593 for ; Wed, 24 Jul 1996 05:01:45 -0700 (PDT) Received: (from zach@localhost) by freebsd.gaffaneys.com (8.7.5/8.7.3) id HAA05351; Wed, 24 Jul 1996 07:02:57 -0500 (CDT) To: "Michael L. VanLoon -- HeadCandy.com" Cc: "Amir Y. Rosenblatt" , freebsd-current@freebsd.org Subject: Re: A new twist on the reboot problems References: <199607240704.AAA11312@MindBender.HeadCandy.com> From: Zach Heilig Date: 24 Jul 1996 07:02:56 -0500 In-Reply-To: "Michael L. VanLoon -- HeadCandy.com"'s message of Wed, 24 Jul 1996 00:04:49 -0700 Message-ID: <87afwpc0zz.fsf@freebsd.gaffaneys.com> Lines: 21 X-Mailer: Gnus v5.2.32/Emacs 19.31 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk "Michael L. VanLoon -- HeadCandy.com" writes: > Incidentally, if you want to be *sure* you capture all panic output, > you might consider putting a comconsole into your kernel and hooking a > serial terminal with scrollback and/or logging (old PC running kermit > works fine) up to be the console. Then, no matter what gets written, > or not written, before the machine freaks out, and before fsck > "cleans" everything, you have it all logged on a separate machine. Speaking of re-routing the console, I noticed this option is called COMconsole (caps for emphasis). Is there anyway to re-route the console to a parallel port? I don't get many console messages (I'm the only one who uses it), so routing them to a printer wouldn't be a bad idea. (Though I'd have to come up with a second parallel port, I don't want to use my laser for console messages... but that's an entirely different problem) -- Zach Heilig (zach@blizzard.gaffaneys.com) | ALL unsolicited commercial email Support bacteria -- it's the | is unwelcome. I avoid dealing only culture some people have! | with companies that email ads. From owner-freebsd-current Wed Jul 24 05:28:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA16530 for current-outgoing; Wed, 24 Jul 1996 05:28:51 -0700 (PDT) Received: from prozac.neuron.net (prozac.neuron.net [165.254.1.213]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA16525 for ; Wed, 24 Jul 1996 05:28:48 -0700 (PDT) Received: (from amir@localhost) by prozac.neuron.net (8.7.5/8.6.12) id IAA00291; Wed, 24 Jul 1996 08:39:04 -0400 (EDT) From: "Amir Y. Rosenblatt" Message-Id: <199607241239.IAA00291@prozac.neuron.net> Subject: Re: A new twist on the reboot problems To: michaelv@HeadCandy.com (Michael L. VanLoon -- HeadCandy.com) Date: Wed, 24 Jul 1996 08:39:04 -0400 (EDT) Cc: amir@neuron.net, freebsd-current@freebsd.org, amir@garpac.com In-Reply-To: <199607240704.AAA11312@MindBender.HeadCandy.com> from "Michael L. VanLoon -- HeadCandy.com" at Jul 24, 96 00:04:49 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Incidentally, if you want to be *sure* you capture all panic output, > you might consider putting a comconsole into your kernel and hooking a > serial terminal with scrollback and/or logging (old PC running kermit > works fine) up to be the console. Then, no matter what gets written, > or not written, before the machine freaks out, and before fsck > "cleans" everything, you have it all logged on a separate machine. Good idea. I'll hav to see if I can drag another machine to within serial-cable range. > Out of curiosity, do you have "options DIAGNOSTIC" in your kernel? If > so, remove it, rebuild, reinstall. Nope -- it's gone. Last night the thing started making those clicking noises again and constantly rebooting. I took it down for a bit, brought it up and it had trouble even getting sd0 to start up. The clicking sounded like it could have been a breaker or something -- every time I heard it, the disk would cut out for a few seconds and then start back up again. All my errors have been on sd0 which leads me to believe that either my power supply or that disk is hosed. I have a spare 'cuda on hand which I'll be installing shortly to see if that's the problem. -Amir From owner-freebsd-current Wed Jul 24 09:42:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA28830 for current-outgoing; Wed, 24 Jul 1996 09:42:02 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@mindbender.headcandy.com [199.238.225.168]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA28814 for ; Wed, 24 Jul 1996 09:41:52 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.7.3) with SMTP id JAA00407; Wed, 24 Jul 1996 09:41:31 -0700 (PDT) Message-Id: <199607241641.JAA00407@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: "Amir Y. Rosenblatt" cc: freebsd-current@freebsd.org, amir@garpac.com Subject: Re: A new twist on the reboot problems In-reply-to: Your message of Wed, 24 Jul 96 08:39:04 -0400. <199607241239.IAA00291@prozac.neuron.net> Date: Wed, 24 Jul 1996 09:41:26 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Nope -- it's gone. Last night the thing started making those clicking >noises again and constantly rebooting. I took it down for a bit, brought >it up and it had trouble even getting sd0 to start up. The clicking >sounded like it could have been a breaker or something -- every time I >heard it, the disk would cut out for a few seconds and then start back up >again. All my errors have been on sd0 which leads me to believe that >either my power supply or that disk is hosed. I have a spare 'cuda on >hand which I'll be installing shortly to see if that's the problem. I would definitely say that it's either a dying power supply, or a dying hard drive (having trouble spinning up). Either way, I'm pretty positive you're seeing bad hardware somewhere if you're getting this many crashes. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@HeadCandy.com --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... Roll your own Internet access -- Seattle People's Internet cooperative. If you're in the Seattle area, ask me how. ----------------------------------------------------------------------------- From owner-freebsd-current Wed Jul 24 10:00:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA00597 for current-outgoing; Wed, 24 Jul 1996 10:00:07 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA00592 for ; Wed, 24 Jul 1996 10:00:06 -0700 (PDT) Received: from sun ([165.254.119.3]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id KAA03549 for ; Wed, 24 Jul 1996 10:00:04 -0700 Received: (from amir@localhost) by sun (8.6.13/8.6.12) id MAA01886; Wed, 24 Jul 1996 12:58:07 -0400 Date: Wed, 24 Jul 1996 12:58:06 -0400 (EDT) From: Amir Rosenblatt To: "Michael L. VanLoon -- HeadCandy.com" cc: "Amir Y. Rosenblatt" , freebsd-current@freebsd.org Subject: Re: A new twist on the reboot problems In-Reply-To: <199607241641.JAA00407@MindBender.HeadCandy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 24 Jul 1996, Michael L. VanLoon -- HeadCandy.com wrote: > I would definitely say that it's either a dying power supply, or a > dying hard drive (having trouble spinning up). Yeah, I'm about 95% sure it's the hard drive. I shuffled things around this morning a bit to give that drive more breathing room (glad I got a full tower case :) It's been behaving since then -- if it doesn't crash in the next 12 hours or so, then I'm going to run under the assumption that it was a heat problem. Otherwise I'll swap it out for a fresh drive. I'll be calling Seagate this afternoon anyway to see what they can tell me about this sorta stuff. > Either way, I'm pretty positive you're seeing bad hardware somewhere > if you're getting this many crashes. Yeah, it's looking that way. Thanks for your time, -Amir From owner-freebsd-current Wed Jul 24 10:33:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA02669 for current-outgoing; Wed, 24 Jul 1996 10:33:41 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA02663 for ; Wed, 24 Jul 1996 10:33:39 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id MAA14379; Wed, 24 Jul 1996 12:31:19 -0500 From: Joe Greco Message-Id: <199607241731.MAA14379@brasil.moneng.mei.com> Subject: Re: A new twist on the reboot problems To: amir@garpac.com (Amir Rosenblatt) Date: Wed, 24 Jul 1996 12:31:19 -0500 (CDT) Cc: michaelv@HeadCandy.com, amir@neuron.net, freebsd-current@freebsd.org In-Reply-To: from "Amir Rosenblatt" at Jul 24, 96 12:58:06 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I would definitely say that it's either a dying power supply, or a > > dying hard drive (having trouble spinning up). > > Yeah, I'm about 95% sure it's the hard drive. I shuffled things around > this morning a bit to give that drive more breathing room (glad I got a > full tower case :) It's been behaving since then -- if it doesn't crash > in the next 12 hours or so, then I'm going to run under the assumption > that it was a heat problem. Otherwise I'll swap it out for a fresh > drive. I'll be calling Seagate this afternoon anyway to see what they > can tell me about this sorta stuff. > > > Either way, I'm pretty positive you're seeing bad hardware somewhere > > if you're getting this many crashes. > > Yeah, it's looking that way. Thanks for your time, The spin-up spin-down thing is sometimes the sign of a bad power connector. I used to have some drive power-Y's on news.sol.net that would affect the drives. You could wiggle them and a drive would spin down... On the other hand, Barracuda's sometimes just die - particularly if they have been heat-abused. While the 'cudas are still my favored drive, I've seen two failures too many in the last two weeks. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/546-7968 From owner-freebsd-current Wed Jul 24 11:57:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA06590 for current-outgoing; Wed, 24 Jul 1996 11:57:51 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA06584 for ; Wed, 24 Jul 1996 11:57:49 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with SMTP id MAA19986 for ; Wed, 24 Jul 1996 12:57:47 -0600 (MDT) Message-Id: <199607241857.MAA19986@rover.village.org> To: current@freebsd.org Subject: Kernel hang Date: Wed, 24 Jul 1996 12:57:46 -0600 From: Warner Losh Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just tried to boot my machine with a Jul 18th -current kernel. I have two scsi disks (sd0 and sd1). It fscks sd0 fine, but fails to fsck sd1. It will set there for up to 30 minutes (I waited that long one, 5 minutes longer than normal the other times (total 10)). This is true over multiple attempts to boot the kerenl. A Jul 12 -current kernel doesn't exibit this behavior. The only delta between the two kernels (modulo source changes between those dates) is that I upped max users from 10 to 20 so that my X builds won't fail with can't for in imake. My system is a 486DX2-66 with 32M of memory, a VLB bus with an UltraStor 34F and a SMC8216C that has been running FreeBSD in this configuration since about FreeBSD 1.1R (and 1.0GAMMA w/o the SMC card or 16M of memory). I know this is scant information. How do I force FreeBSD to dump a core file that I can use gdb to send a reasonable traceback for further analysis. I'll be trying again in a day or three with the then current kernel. Thanks for your help Warner From owner-freebsd-current Wed Jul 24 12:54:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA11279 for current-outgoing; Wed, 24 Jul 1996 12:54:39 -0700 (PDT) Received: from ref.tfs.com ([206.245.251.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA11259; Wed, 24 Jul 1996 12:54:32 -0700 (PDT) Received: (from julian@localhost) by ref.tfs.com (8.7.5/8.7.3) id MAA06454; Wed, 24 Jul 1996 12:50:45 -0700 (PDT) Message-Id: <199607241950.MAA06454@ref.tfs.com> Subject: Re: bootstrap To: richardc@CSUA.Berkeley.EDU (Veggy Vinny) Date: Wed, 24 Jul 1996 12:50:44 -0700 (PDT) From: "JULIAN Elischer" Cc: joerg_wunsch@uriah.heep.sax.de, current@FreeBSD.ORG, questions@FreeBSD.ORG In-Reply-To: from "Veggy Vinny" at Jul 22, 96 01:11:02 pm X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Just tried it as disklabel -B wd0 but no luck... I'm using a > Western Digital WDAC31600 Caviar EIDE HD in LBA mode under -current and > in the Booteasy menu, when I hit F2 for FreeBSD, it just redisplays the > Booteasy menu again in a loop..... Is there a way I can fix this? > > Here is my fdisk wd0 output: > > root@bigbang [1:06pm][/usr/home/vince] >> fdisk wd0 > ******* Working on device /dev/rwd0 ******* > parameters extracted from in-core disklabel are: > cylinders=3148 heads=16 sectors/track=63 (1008 blks/cyl) > > Figures below won't work with BIOS for partitions not in cyl 1 > parameters to be used for BIOS calculations are: > cylinders=3148 heads=16 sectors/track=63 (1008 blks/cyl) > > Warning: BIOS sector numbering starts with sector 1 > Information from DOS bootblock is: > The data for partition 0 is: > sysid 6,(Primary 'big' DOS (> 32MB)) > start 63, size 1031121 (503 Meg), flag 0 > beg: cyl 0/ sector 1/ head 1; > end: cyl 785/ sector 63/ head 15 > The data for partition 1 is: ok, so let's do some arrithmetic.... with 63 x 16 geometry, block 1031184 is cyl 1024 sector 1 (first sector...) head 0 > sysid 165,(FreeBSD/NetBSD/386BSD) > start 1031184, size 2142000 (1045 Meg), flag 0 > beg: cyl 785/ sector 1/ head 0; > end: cyl 785/ sector 63/ head 15 You are instructin the bios to look at cyl 785, sector 1 head 0 this misses by some 239 cylinders.. This assumes your bios can USE 1024 cyls.. most can't > The data for partition 2 is: > > The data for partition 3 is: > > > Vince > > From owner-freebsd-current Wed Jul 24 13:43:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA14412 for current-outgoing; Wed, 24 Jul 1996 13:43:17 -0700 (PDT) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA14406 for ; Wed, 24 Jul 1996 13:43:10 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.7.5/8.6.9) with SMTP id NAA24940; Wed, 24 Jul 1996 13:35:10 +0100 (BST) Date: Wed, 24 Jul 1996 13:35:09 +0100 (BST) From: Developer To: Joerg Wunsch cc: FreeBSD-current users Subject: Re: Termcap problems In-Reply-To: <199607231748.TAA10778@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 23 Jul 1996, J Wunsch wrote: > As Developer wrote: > > > > What makes you think they thought of a different size? > > > > > > Programs like ls usually get the window geometry out of the struct > > > winsize. > > > > Usually what happens when the problem occurs is ls prints more characters > > per line than it should - e.g. all the lines wrap a little onto the next > > line!! > > What says ``stty -a'' about the window size? > > For me, everything works well. I've just maximized an xterm, and > ls /usr/local/bin (where there are quite many files), and it looks > reasonable. Okay, for any window larger the 80 chars width it does it, but only in certain directories like / on one machine.. here is the output .CARD bin/ fd0/ lib@ proc/ sys@ .LOCK compat@ fnews/ lkm/ root/ tmp/ .cshrc dcf/ ftmp/ lost+found/ sbin/ usr/ .newuser dev/ httpd@ man@ schoolwww@ var/ .profile etc/ kernel* mnt/ stand@ www@ amitcp/ fastboot kernel.old* news@ store/ #stty -a speed 9600 baud; 24 rows; 110 columns; lflags: icanon isig iexten echo echoe -echok echoke -echonl echoctl -echoprt -altwerase -noflsh -tostop -flusho pendin -nokerninfo -extproc iflags: istrip icrnl -inlcr -igncr ixon -ixoff ixany imaxbel ignbrk brkint -inpck -ignpar -parmrk oflags: opost onlcr -oxtabs cflags: cread cs8 -parenb -parodd hupcl -clocal -cstopb -crtscts -dsrflow -dtrflow -mdmbuf cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = ; eol2 = ; erase = ^?; intr = ^C; kill = ^U; lnext = ^V; min = 1; quit = ^\; reprint = ^R; start = ^Q; status = ; stop = ^S; susp = ^Z; time = 0; werase = ^W; Any ideas? Thanks in advance. Trefor S. From owner-freebsd-current Wed Jul 24 13:48:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA14714 for current-outgoing; Wed, 24 Jul 1996 13:48:37 -0700 (PDT) Received: from mail.ruhrgebiet.individual.net (in-ruhr.ruhr.de [193.100.176.38]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA14708 for ; Wed, 24 Jul 1996 13:48:32 -0700 (PDT) Received: by mail.ruhrgebiet.individual.net (8.7.1/8.6.12) with UUCP id VAA19509 for freebsd.org!freebsd-current; Wed, 24 Jul 1996 21:52:11 +0200 (MET DST) Received: by robkaos.ruhr.de (/\oo/\ Smail3.1.29.1 #29.1) id ; Wed, 24 Jul 96 21:49 MET DST Message-Id: From: robsch@robkaos.ruhr.de (Robert Schien) Subject: Directory structure of 2.1.5-CD-ROM To: freebsd-current@freebsd.org Date: Wed, 24 Jul 1996 21:49:13 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I want to burn my own FreeBSD 2.1.5 CD-ROM. I am subscribing the FreeBSD CD from Walnut Creek, but it will still take some weeks to get it. So, how is the CD structured? Same as in 2.1.0? TIA Robert From owner-freebsd-current Wed Jul 24 16:12:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA23415 for current-outgoing; Wed, 24 Jul 1996 16:12:58 -0700 (PDT) Received: from american.com (biscayne.american.com [204.253.96.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA23410 for ; Wed, 24 Jul 1996 16:12:54 -0700 (PDT) Received: from muir-woods.american.com (muir-woods.american.com [204.253.96.201]) by american.com (8.6.12/8.6.12) with ESMTP id TAA03493; Wed, 24 Jul 1996 19:11:52 -0400 Received: from localhost (localhost [127.0.0.1]) by muir-woods.american.com (8.6.12/8.6.12) with SMTP id TAA07943; Wed, 24 Jul 1996 19:11:51 -0400 Message-Id: <199607242311.TAA07943@muir-woods.american.com> X-Authentication-Warning: muir-woods.american.com: Host localhost didn't use HELO protocol X-Mailer: exmh version 1.6.7 5/3/96 To: John Polstra cc: brad@american.com, freebsd-current@freebsd.org Subject: Re: gcc 2.7.2 + binutils 2.7 on stable? In-reply-to: Your message of "Tue, 23 Jul 1996 21:29:19 PDT." <199607240429.VAA00920@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 24 Jul 1996 19:11:50 -0400 From: Brad Parker Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk jdp@polstra.com said: > > I've been trying to build gcc-2.7.2 and binutils 2.7 on a "stable" > > system (i.e. sup'd from the stable release). I give up. I can't get > > bfd and ld to do the right thing. ... [part about "ASM_WEAKEN_LABEL" deleted - thanks! I'll try that] > As another option: Reportedly, it's not that hard to get just the > assembler from binutils working for FreeBSD. Our linker seems to > support weak symbols, so if you can get the binutils assembler > working, then you should be able to use it with the stock gcc-2.7.2 > and the native linker. I got the binutils-2.7 gas to work, but the a.out's which came from gcc-2.7.2 + binutils-2.7-gas + native-2.1-ld would crash in odd ways... (I beleive it would segv in libfd) If I recompiled using the native gas the crash would go away... I'll try the first idea - thanks again. -brad From owner-freebsd-current Wed Jul 24 19:15:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA04119 for current-outgoing; Wed, 24 Jul 1996 19:15:13 -0700 (PDT) Received: from zombie.ncsc.mil (zombie.ncsc.mil [144.51.15.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id TAA04095 for ; Wed, 24 Jul 1996 19:15:04 -0700 (PDT) Received: (from sjr@localhost) by zombie.ncsc.mil (8.6.11/8.6.11) id WAA09616 for current@freebsd.org; Wed, 24 Jul 1996 22:15:02 -0400 Date: Wed, 24 Jul 1996 22:15:02 -0400 From: "Stephen J. Roznowski" Message-Id: <199607250215.WAA09616@zombie.ncsc.mil> To: current@freebsd.org Subject: Memory fault during make world Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I got the following error during a "make world" with freshly supped sources: ===> gnu/usr.bin/perl/x2p install -c -o bin -g bin -m 555 /usr/src/gnu/usr.bin/perl/x2p/s2p /usr/bin install -c -o bin -g bin -m 555 /usr/src/gnu/usr.bin/perl/x2p/h2ph /usr/bin install -c -s -o bin -g bin -m 555 a2p /usr/bin install -c -o bin -g bin -m 444 a2p.1.gz s2p.1.gz h2ph.1.gz /usr/share/man/man1 (DESTDIR=; cd /usr/include; h2ph * sys/*) Memory fault - core dumped *** Error code 139 Stop. In searching the mailing list archives, I see that someone reported this same problem on 27 Feb 1996, but I didn't see any answer posted to this problem. Can anyone help me out? Thanks, Stephen Roznowski (sjr@zombie.ncsc.mil) From owner-freebsd-current Wed Jul 24 23:46:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA21608 for current-outgoing; Wed, 24 Jul 1996 23:46:50 -0700 (PDT) Received: from dworshak.cs.uidaho.edu (dworshak.cs.uidaho.edu [129.101.100.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA21600 for ; Wed, 24 Jul 1996 23:46:48 -0700 (PDT) Received: from waldrog.cs.uidaho.edu (waldrog.cs.uidaho.edu [129.101.100.23]) by dworshak.cs.uidaho.edu (8.7.5/1.1) with ESMTP id XAA14068 for ; Wed, 24 Jul 1996 23:46:47 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by waldrog.cs.uidaho.edu (8.7.5/1.0) with SMTP id XAA20270 for ; Wed, 24 Jul 1996 23:46:46 -0700 (PDT) X-Authentication-Warning: waldrog.cs.uidaho.edu: Host localhost [127.0.0.1] didn't use HELO protocol To: current@freebsd.org Subject: bt946 problems. MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <20266.838277205.1@waldrog.cs.uidaho.edu> Date: Wed, 24 Jul 1996 23:46:46 PDT Message-ID: <20268.838277206@waldrog.cs.uidaho.edu> From: faried nawaz Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk hi, i've got a p133, triton 2, one sd0, one cd0, and one bt946c. i can't seemingly use the bt0 driver with -current (2.1's kernel works ok). on bootup i find the bt0 card (and assoc. devices) just fine; at the end of the boot process, it says bt: unit number (1) too high bt1 not found at 0x334 npx0 on motherboard npx0: INT 16 interface and then hangs. (note: my bt0 is on 0x334, not 0x330. if i could just _find_ the dos utils to reconfig...) kernel.GENERIC's dmesg output is: ; dmesg |grep bt0 bt0: Bt946C/ 0-PCI/EISA/VLB(32bit) bus bt0: reading board settings, dma=5, int=10 bt0: version 4.25J, fast sync, parity, 32 mbxs, 32 ccbs bt0: targ 0 sync rate=10.00MB/s(100ns), offset=15 bt0: targ 1 sync rate= 5.00MB/s(200ns), offset=15 bt0: Using Strict Round robin scheme bt0 at 0x334 irq 10 drq 5 on isa bt0 waiting for scsi devices to settle (bt0:0:0): "HP C3325A 4299" type 0 fixed SCSI 2 sd0(bt0:0:0): Direct-Access 2069MB (4238836 512 byte sectors) (bt0:1:0): "SONY CD-ROM CDU-76S 1.1c" type 5 removable SCSI 2 cd0(bt0:1:0): CD-ROM cd0(bt0:1:0): NOT READY asc:3a,0 Medium not present ; my kernel config is: # # lisp-reader # machine "i386" cpu "I586_CPU" ident lispreader maxusers 32 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 options "SCSI_DELAY=15" #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options SYSVSHM options SYSVSEM options SYSVMSG options KTRACE options MROUTING options SCSI_REPORT_GEOMETRY options DUMMY_NOPS options PROBE_VERBOSE options "I586_FAST_BCOPY" options SHOW_BUSYBUFS config kernel root on sd0 controller isa0 controller pci0 controller scbus0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr controller bt0 at isa? port 0x334 bio irq ? vector bt_isa_intr #controller ahc0 controller snd0 #device de0 disk fd0 at fdc0 drive 0 device sd0 device cd0 #Only need one of these, the code dynamically grows device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device ed0 at isa? port 0x280 net irq 7 iomem 0xda000 vector edintr device sb0 at isa? port 0x220 irq 7 conflicts drq 1 vector sbintr device sbxvi0 at isa? drq 5 device sbmidi0 at isa? port 0x330 pseudo-device loop pseudo-device ether pseudo-device log pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's pseudo-device vn 2 pseudo-device speaker i can leave the machine as-is for the next month or two (i will be out of town), but i would very much like suggestions i could test out before i leave tomorrow (~ 9am PST). thanks, faried. From owner-freebsd-current Thu Jul 25 06:41:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA29194 for current-outgoing; Thu, 25 Jul 1996 06:41:05 -0700 (PDT) Received: from nervosa.netcom.com (nervosa.vendetta.com [192.187.167.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA29177; Thu, 25 Jul 1996 06:41:00 -0700 (PDT) Received: (from coredump@localhost) by nervosa.netcom.com (8.7.5/8.7.3) id GAA12575; Thu, 25 Jul 1996 06:41:17 -0700 (PDT) Date: Thu, 25 Jul 1996 06:41:17 -0700 (PDT) From: goamatic To: winter@jurai.net cc: freebsd-current@freebsd.org, freebsd-security@freebsd.org Subject: well.. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Here is beta 1 of the changes I have done to Crack 4.1 in order to make it work with master.passwd (md5) style passwords. Patch from crack/ -- begin --- diff -c Sources/Makefile /var/tmp/Sources/Makefile *** Sources/Makefile Thu Jun 25 07:54:38 1992 --- /var/tmp/Sources/Makefile Thu Jul 25 05:02:14 1996 *************** *** 2,8 **** # Revised Makefile for Crack v4.1 - AEM, Feb 14 1992 ### ! LIBS= CFLAGS= -O PWC= crack-pwc FCRYPT= crack-fcrypt.o --- 2,8 ---- # Revised Makefile for Crack v4.1 - AEM, Feb 14 1992 ### ! LIBS= -lcrypt CFLAGS= -O PWC= crack-pwc FCRYPT= crack-fcrypt.o diff -c Sources/conf.h /var/tmp/Sources/conf.h *** Sources/conf.h Thu Jun 25 07:54:41 1992 --- /var/tmp/Sources/conf.h Thu Jul 25 04:23:15 1996 *************** *** 58,64 **** */ #define COMPRESSION ! #define ZCAT "/usr/ucb/zcat" /* as in "zcat Dicts/bigdict.Z" */ #define PCAT "/usr/bin/pcat" /* --- 58,64 ---- */ #define COMPRESSION ! #define ZCAT "/usr/bin/zcat" /* as in "zcat Dicts/bigdict.Z" */ #define PCAT "/usr/bin/pcat" /* *************** *** 66,69 **** * doesn't work properly */ ! #define FCRYPT --- 66,69 ---- * doesn't work properly */ ! #undef FCRYPT diff -c Sources/crack-pwc.c /var/tmp/Sources/crack-pwc.c *** Sources/crack-pwc.c Thu Jun 25 07:55:44 1992 --- /var/tmp/Sources/crack-pwc.c Thu Jul 25 06:21:44 1996 *************** *** 125,131 **** p = PWSkip (p); retval -> passwd.pw_gid = atoi (p); ! p = PWSkip (p); retval -> passwd.pw_gecos = p; p = PWSkip (p); --- 125,140 ---- p = PWSkip (p); retval -> passwd.pw_gid = atoi (p); ! p = PWSkip (p); ! retval -> passwd.pw_class = p; ! ! p = PWSkip (p); ! retval -> passwd.pw_change = atoi (p); ! ! p = PWSkip (p); ! retval -> passwd.pw_expire = atoi (p); ! ! p = PWSkip (p); retval -> passwd.pw_gecos = p; p = PWSkip (p); *************** *** 143,149 **** { int i; char *ptr; ! char salt[2]; char buffer[STRINGSIZE]; long int numlines; long int numentries; --- 152,158 ---- { int i; char *ptr; ! char salt[34]; char buffer[STRINGSIZE]; long int numlines; long int numentries; *************** *** 153,159 **** numlines = 0L; numentries = 0L; current_line = NULL; ! salt[0] = salt[1] = '*'; while (fgets (buffer, STRINGSIZE, stdin)) { --- 162,169 ---- numlines = 0L; numentries = 0L; current_line = NULL; ! salt[0] = '*'; ! salt[1] = '$'; while (fgets (buffer, STRINGSIZE, stdin)) { *************** *** 191,202 **** new_element -> filename); continue; } ! if (i > 13) { Log ("User %s (in %s) has a long pw_passwd field - truncating.\n", new_element -> passwd.pw_name, new_element -> filename); ! ptr[13] = '\0'; } numentries++; --- 201,212 ---- new_element -> filename); continue; } ! if (i > 34) { Log ("User %s (in %s) has a long pw_passwd field - truncating.\n", new_element -> passwd.pw_name, new_element -> filename); ! ptr[34] = '\0'; } numentries++; *************** *** 204,222 **** { new_element -> across = current_line; current_line = new_element; ! } else { if (current_line) { ! current_line -> next = userroot; } userroot = current_line; current_line = new_element; numlines++; ! salt[0] = ptr[0]; ! salt[1] = ptr[1]; ! } } if (current_line) /* last one tends to hang about */ { --- 214,233 ---- { new_element -> across = current_line; current_line = new_element; ! } else { if (current_line) { ! current_line -> next = userroot; } userroot = current_line; current_line = new_element; numlines++; ! strcpy(salt, ptr); ! /* salt[0] = ptr[0]; */ ! /* salt[1] = ptr[1]; */ } + } if (current_line) /* last one tends to hang about */ { *************** *** 1091,1104 **** /* Quick, verify that we are sane ! */ - if (strcmp (crypt ("fredfred", "fredfred"), "frxWbx4IRuBBA")) - { - Log ("Version of crypt() being used internally is not compatible with standard.\n"); - Log ("This could be due to byte ordering problems - see the comments in Sources/conf.h\n"); - Log ("If there is another reason for this, edit the source to remove this assertion.\n"); - Log ("Terminating...\n"); - exit (0); - } #ifndef AMIGA signal (SIGTERM, CatchTERM); #endif --- 1102,1107 ---- diff -c Scripts/do_join /var/tmp/Scripts/do_join *** Scripts/do_join Thu Jun 25 07:54:20 1992 --- /var/tmp/Scripts/do_join Thu Jul 25 05:05:32 1996 *************** *** 48,54 **** awk -F: ' BEGIN { FS = ":"; ! numf = 8; # number of fields in a pwent, + 1 warn="'"$warn"'"; date = "'"`date`"'"; date = substr(date, 5, 15); --- 48,54 ---- awk -F: ' BEGIN { FS = ":"; ! numf = 11; # number of fields in a pwent, + 1 warn="'"$warn"'"; date = "'"`date`"'"; date = substr(date, 5, 15); -- cut -------- == Chris Layne ======================================== Nervosa Computing == == coredump@nervosa.vendetta.com == http://nervosa.vendetta.com/~coredump == From owner-freebsd-current Thu Jul 25 07:14:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA01029 for current-outgoing; Thu, 25 Jul 1996 07:14:27 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA01018 for ; Thu, 25 Jul 1996 07:14:22 -0700 (PDT) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id QAA04270 for ; Thu, 25 Jul 1996 16:10:05 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id QAA09520 for freebsd-current@freefall.cdrom.com; Thu, 25 Jul 1996 16:23:38 +0200 Date: Thu, 25 Jul 1996 16:23:38 +0200 From: "Christoph P. Kukulies" Message-Id: <199607251423.QAA09520@gilberto.physik.rwth-aachen.de> To: freebsd-current@freefall.FreeBSD.org Subject: getting thru make world (atapi lkm fails) Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Due to a lot of problems I had with sup recently I'm only gradually keeping up with getting a world compiled again. Last problem got solved: I had an old /usr/src/include/ctype.h which never got superceeded by sup (my server was holding the correct one - strange). Anyway, now make depend in lkm/atapi fails the following way: ===> lkm/atapi rm -f .depend files=""; if [ "$files" != "" ]; then mkdep -a -I. -DATAPI -DATAPI_MODULE -DKERNEL -I/usr/src/lkm/atapi/../../sys $files; fi files="/usr/src/lkm/atapi/../../sys/i386/isa/atapi.c"; if [ "$files" != "" ]; then mkdep -a -I. -DATAPI -DATAPI_MODULE -DKERNEL -I/usr/src/lkm/atapi/../../sys $files; fi In file included from /usr/src/lkm/atapi/../../sys/sys/conf.h:226, from /usr/src/lkm/atapi/../../sys/i386/isa/atapi.c:934: /usr/include/machine/conf.h:6: ioconf.h: No such file or directory mkdep: compile failed. *** Error code 1 Stop. Isn't ioconf.h generated at kernel config time? Any clues what might be wrong with my setup? src tree still outdated? --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Thu Jul 25 08:28:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA05489 for current-outgoing; Thu, 25 Jul 1996 08:28:33 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA05481; Thu, 25 Jul 1996 08:28:26 -0700 (PDT) Message-Id: <199607251528.IAA05481@freefall.freebsd.org> To: faried nawaz cc: current@freebsd.org Subject: Re: bt946 problems. In-reply-to: Your message of "Wed, 24 Jul 1996 23:46:46 PDT." <20268.838277206@waldrog.cs.uidaho.edu> Date: Thu, 25 Jul 1996 08:28:26 -0700 From: "Justin T. Gibbs" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >bt: unit number (1) too high >bt1 not found at 0x334 >npx0 on motherboard >npx0: INT 16 interface The ISA bt probe is screwing you up. Take the ISA bt stuff out of your kernel config file. Use controller bt0 instead of controller bt0 at isa?... >thanks, > >faried. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Thu Jul 25 10:34:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA14197 for current-outgoing; Thu, 25 Jul 1996 10:34:12 -0700 (PDT) Received: from midway (midway.evtech.com [204.96.163.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA14186 for ; Thu, 25 Jul 1996 10:34:10 -0700 (PDT) Received: from tahiti.evtech.com (tahiti.evtech.com [192.35.179.19]) by midway (8.7.3/8.6.9) with ESMTP id LAA01612; Thu, 25 Jul 1996 11:30:08 -0500 (CDT) Received: from borneo.evtech.com (borneo.evtech.com [192.35.179.29]) by tahiti.evtech.com (8.6.12/8.6.12) with ESMTP id LAA26018; Thu, 25 Jul 1996 11:30:08 -0500 Message-Id: <199607251630.LAA26018@tahiti.evtech.com> To: current-users@NetBSD.ORG cc: freebsd-current@FreeBSD.ORG Subject: Wanted: C/perl/sh/x86asm (etc) programming tools Date: Thu, 25 Jul 1996 11:30:06 -0500 From: Travis Hassloch x231 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk While I don't make it a habit of posting to multiple lists, I wanted to be as ecumenical as possible so as to get the most responses. I've searched UGU and a couple other archives, but I'm still looking for: programming tools for... C - including ``code exploration'' tools for trying to track code flow through the kernel and other large beasts... so far: ctags, cflow (is out for Linux, prob FreeBSD too), [x]lint sh - m4 works beautifully; snagged a bunch of macros from autoconf and dressed them up to be what _could_ be a mostly-shell-independent programming language (I use that term with strong reservations). I use it here at work to generate portable but highly redundant shell scripts that don't rely on fancy features like, oh, the case statement or shell functions... ;) or that they work right. It'd work okay for doing simple scripts that just set envars and envars that point to other envars by name, and could do nested command subst on sh's that don't support it with temp vars... PERL - no real programming tools here, but there's a byacc that emits C or PERL (sort of a overstatement, since you have to write the actions and headers for the rules in one or the other) that lets you throw together parsers quickly (hope your lexer is simple) A ``perlflow'' utility, if possible, would be nice misc - it'd be nice to maintain keyword and/or function names across large hierarchies of code; I would probably generate database for C mostly, but it'd be nice to have a framework to parse the info out of any language. Maybe some search engine like pursuit might work but there has to be something better for code WEB, noweb, nuweb(?) look interesting, haven't used 'em Something to show variable lifetimes (first use, last use) would be nice in several languages, but most notably assembler -- Travis Hassloch, Illuminatus Double-Prime | P=NP if (P=0 or N=1) ``Software code is the language that makes computer programs run'' [sic] From owner-freebsd-current Thu Jul 25 12:09:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA22371 for current-outgoing; Thu, 25 Jul 1996 12:09:20 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA22366 for ; Thu, 25 Jul 1996 12:09:18 -0700 (PDT) Received: from desiree.teleport.com (desiree.teleport.com [192.108.254.21]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id MAA02400 for ; Thu, 25 Jul 1996 12:09:15 -0700 Received: from linda.teleport.com (mrl@linda.teleport.com [192.108.254.12]) by desiree.teleport.com (8.7.5/8.7.3) with ESMTP id MAA28974; Thu, 25 Jul 1996 12:07:55 -0700 (PDT) From: Mostyn/Annabella Received: (from mrl@localhost) by linda.teleport.com (8.7.5/8.7.3) id MAA23128; Thu, 25 Jul 1996 12:07:54 -0700 (PDT) Message-Id: <199607251907.MAA23128@linda.teleport.com> Subject: Current, elfkit, linux ELF static bin To: current@FreeBSD.ORG Date: Thu, 25 Jul 1996 12:07:54 -0700 (PDT) Cc: mrl@teleport.com X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Howdy, Running current with elfkit set up to provide /usr/libexec/ld-elf.so.1 seems to run hand rolled ELF bins fine. However, importing an ELF linux static bin and running (after installing the linux lkm) bombs. The binary is the "Bulldozer" WYSIWYG HTML editor from http://cscsun1.larc.nasa.gov/~rboykin/Dozer/ Running it gets ./dozer Memory fault (core dumped) and produces a "garbled" directory which looks like drw-r----- 2 root wheel 512 Jul 23 15:45 ¼Ö¿ï/ Any ideas? Mostyn From owner-freebsd-current Thu Jul 25 12:52:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA26568 for current-outgoing; Thu, 25 Jul 1996 12:52:58 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA26549 for ; Thu, 25 Jul 1996 12:52:54 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id VAA19839 for ; Thu, 25 Jul 1996 21:52:28 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA23881 for freebsd-current@FreeBSD.org; Thu, 25 Jul 1996 21:52:27 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id TAA22036 for freebsd-current@FreeBSD.org; Thu, 25 Jul 1996 19:27:27 +0200 (MET DST) From: J Wunsch Message-Id: <199607251727.TAA22036@uriah.heep.sax.de> Subject: Re: cvs commit: src/sys/dev/ccd ccd.c src/sys/dev/vn vn.c src/sys/sys conf.h src/sys/i386/isa fd.c mcd.c scd.c wcd.c wd.c wt.c s To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Thu, 25 Jul 1996 19:27:26 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <3577.838236253@time.cdrom.com> from "Jordan K. Hubbard" at "Jul 24, 96 12:24:13 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk (Moved to -current.) As Jordan K. Hubbard wrote: > Also, the persistence people don't mind if devfs is *optional*, then > it can throw your /dev files away every 5 minutes just for fun if it > likes - they don't have to use it. What sense does it make using /dev entries to unconfigured drivers (that's about all persistance would give you, isn't it :)? Of course, this assumes a debugged and functional devfs, so the /dev tree always reflects the current state. This is certainly some way to go from now, so don't call for something like persistance just because you don't like its current bugs. ;-) I think the union file system might be a good one, so you can stuff like /dev/tape, /dev/root :) and other pseudo-device names into it. Alternatively, symlinks inside devfs might do it, but they require some more effort to save the current state. Wasn't Julian promising that he's got symlinks almost working? ;) We need them badly for /dev/log. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Thu Jul 25 12:54:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA26818 for current-outgoing; Thu, 25 Jul 1996 12:54:46 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA26796 for ; Thu, 25 Jul 1996 12:54:39 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id VAA19868; Thu, 25 Jul 1996 21:53:00 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA23894; Thu, 25 Jul 1996 21:52:59 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id VAA22683; Thu, 25 Jul 1996 21:07:09 +0200 (MET DST) From: J Wunsch Message-Id: <199607251907.VAA22683@uriah.heep.sax.de> Subject: Re: Termcap problems To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Thu, 25 Jul 1996 21:07:09 +0200 (MET DST) Cc: dev@fgate.flevel.co.uk (Developer) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Developer at "Jul 24, 96 01:35:09 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Developer wrote: > Okay, for any window larger the 80 chars width it does it, but only in > certain directories like / on one machine.. here is the output > > .CARD bin/ fd0/ lib@ proc/ > sys@ > .LOCK compat@ fnews/ lkm/ root/ > tmp/ > .cshrc dcf/ ftmp/ lost+found/ sbin/ > usr/ > .newuser dev/ httpd@ man@ schoolwww@ > var/ > .profile etc/ kernel* mnt/ stand@ > www@ > amitcp/ fastboot kernel.old* news@ store/ > > #stty -a > > speed 9600 baud; 24 rows; 110 columns; Perhaps a miscalculation that only hits in some special case. I bet if you turn off the -F, it will look normally. You could have a look into the column number calculation, and file a PR once you've got a fix. :-)) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Thu Jul 25 13:15:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA28242 for current-outgoing; Thu, 25 Jul 1996 13:15:38 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA28229; Thu, 25 Jul 1996 13:15:33 -0700 (PDT) Message-Id: <199607252015.NAA28229@freefall.freebsd.org> To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-current@FreeBSD.ORG (FreeBSD-current users) Subject: Re: cvs commit: src/sys/dev/ccd ccd.c src/sys/dev/vn vn.c src/sys/sys conf.h src/sys/i386/isa fd.c mcd.c scd.c wcd.c wd.c wt.c s In-reply-to: Your message of "Thu, 25 Jul 1996 19:27:26 +0200." <199607251727.TAA22036@uriah.heep.sax.de> Date: Thu, 25 Jul 1996 13:15:32 -0700 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >(Moved to -current.) > >As Jordan K. Hubbard wrote: > >> Also, the persistence people don't mind if devfs is *optional*, then >> it can throw your /dev files away every 5 minutes just for fun if it >> likes - they don't have to use it. > >What sense does it make using /dev entries to unconfigured drivers >(that's about all persistance would give you, isn't it :)? Persistence would allow you to change the permissions on a device and have them stick. If a device was not availible, it wouldn't show up in /dev, but if it came back (say after replacing faulty hardware) any permission changes you made in the past would show up as soon as the device did. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Thu Jul 25 13:57:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA00991 for current-outgoing; Thu, 25 Jul 1996 13:57:27 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA00981 for ; Thu, 25 Jul 1996 13:57:17 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id OAA07544; Thu, 25 Jul 1996 14:45:55 -0600 (MDT) Date: Thu, 25 Jul 1996 14:45:55 -0600 (MDT) Message-Id: <199607252045.OAA07544@rocky.mt.sri.com> From: Nate Williams To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: freebsd-current@freebsd.org (FreeBSD-current users) Subject: Re: cvs commit: src/sys/dev/ccd ccd.c src/sys/dev/vn vn.c src/sys/sys conf.h src/sys/i386/isa fd.c mcd.c scd.c wcd.c wd.c wt.c s In-Reply-To: <199607251727.TAA22036@uriah.heep.sax.de> References: <3577.838236253@time.cdrom.com> <199607251727.TAA22036@uriah.heep.sax.de> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > it can throw your /dev files away every 5 minutes just for fun if it > > likes - they don't have to use it. > > What sense does it make using /dev entries to unconfigured drivers > (that's about all persistance would give you, isn't it :)? Permissions is the thing I'm most worried about. On my box, /dev/apm is open to the world, and I don't want to have to go edit a file *every* time I want to change the default permissions of a device. On my sun box, I have to write a script to change the default permissions on certain devices where the default permisissions aren't appropriate for my local use. Requiring every user to be a 'sh/perl/C/TCL/' programmer is not acceptable. If the 'persistance' happeens to be in a easy-to-use program like mset which edits the internal tables, it's fine by me. Just as long as I don't have to do it all by hand to change the default permissions. Nate From owner-freebsd-current Thu Jul 25 14:43:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA03336 for current-outgoing; Thu, 25 Jul 1996 14:43:26 -0700 (PDT) Received: from desiree.teleport.com (desiree.teleport.com [192.108.254.21]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA03323 for ; Thu, 25 Jul 1996 14:42:56 -0700 (PDT) Received: from linda.teleport.com (mrl@linda.teleport.com [192.108.254.12]) by desiree.teleport.com (8.7.5/8.7.3) with ESMTP id OAA17783; Thu, 25 Jul 1996 14:42:41 -0700 (PDT) From: Mostyn/Annabella Received: (from mrl@localhost) by linda.teleport.com (8.7.5/8.7.3) id OAA06919; Thu, 25 Jul 1996 14:42:38 -0700 (PDT) Message-Id: <199607252142.OAA06919@linda.teleport.com> Subject: Re: Current, elfkit, linux ELF static bin To: chuckr@Glue.umd.edu (Chuck Robey) Date: Thu, 25 Jul 1996 14:42:38 -0700 (PDT) Cc: current@freebsd.org In-Reply-To: from "Chuck Robey" at Jul 25, 96 04:54:44 pm X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > On Thu, 25 Jul 1996, Mostyn/Annabella wrote: > > > Howdy, > > > > Running current with elfkit set up to provide /usr/libexec/ld-elf.so.1 > > seems to run hand rolled ELF bins fine. > > However, importing an ELF linux static bin and running (after installing > > the linux lkm) bombs. > > The binary is the "Bulldozer" WYSIWYG HTML editor from > > http://cscsun1.larc.nasa.gov/~rboykin/Dozer/ > > > > Running it gets > > > > ./dozer > > Memory fault (core dumped) > > > > and produces a "garbled" directory which looks like > > > > drw-r----- 2 root wheel 512 Jul 23 15:45 > > > The ld-elf.so.1 is only for linux executeables that are dynamically > linked. When you do a 'file Bulldozer' (assuming that's the name of your > executeable) what does FreeBSD tell you (what type of file is it really?) Thanks, I was aware of the dynamic loader - I was imprecise - statically linked ELF bins made locally work too. I was only pointing out that it seems the kernel image activator for ELF seemed to be working OK. The "dozer" file, by the way, owns up to being -> file dozer dozer: ELF 32-bit LSB executable, Intel 80386, version 1 Mostyn From owner-freebsd-current Thu Jul 25 16:10:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA08838 for current-outgoing; Thu, 25 Jul 1996 16:10:24 -0700 (PDT) Received: from central.picker.com (central.picker.com [144.54.31.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA08829 for ; Thu, 25 Jul 1996 16:10:22 -0700 (PDT) Received: from ct.picker.com by central.picker.com with smtp (Smail3.1.28.1 #3) id m0ujZGQ-0004rrC; Thu, 25 Jul 96 18:52 EDT Received: from elmer.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1) id AA02836; Thu, 25 Jul 96 18:51:15 EDT Received: by elmer.picker.com (SMI-8.6/SMI-SVR4) id SAA15868; Thu, 25 Jul 1996 18:46:31 -0400 From: rhh@ct.picker.com (Randall Hopper) Message-Id: <199607252246.SAA15868@elmer.picker.com> Subject: Re: Linux Emu. To: wangel@wgrobez1.remote.louisville.edu (Gary Roberts) Date: Thu, 25 Jul 1996 18:46:31 -0400 (EDT) Cc: current@freebsd.org In-Reply-To: from "Gary Roberts" at Jul 21, 96 06:21:05 am Reply-To: rhh@ct.picker.com Organization: Picker International, CT Division X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Gary Roberts: >Well, I'll try that I suppose .... I was looking forward to getting Quake >.91 or 1.01 to work. It starts to load but then core dumps ... I was I'd be interested in where to get this. >wondering if I need to do some kernel tweeking or what not ? ... Also, if >it helps, Doom doesn't work either -- it loads, then bombs out with a >broken pipe and when trying to reload, it yells about shared mem or >something. Yes, when it dumps it leaves shared memory allocated. I hit the broken pipe problem too but did something to get around it. If it helps, here's my /opt/bin/doom script: #!/bin/sh # # Launch doom, and clean up shared memory when it's done (RHH - 6/1/96) # DOOMDIR=/opt/pkg/doom-1.8 musserver_pid=99999 DOOMWADDIR=$DOOMDIR PATH=$DOOMDIR:/usr/bin:$PATH export DOOMWADDIR PATH cd $DOOMDIR /opt/pkg/doom-1.8/musserver.fbsd -f -u 0 & musserver_pid=$! joystick4doom /dev/joy0 Control Space -strafe & #trap "kill -9 $musserver_pid; ipcrm -m `ipcs | grep ^m | cut -f2 -d" "` > /dev/null 2>&1; trap 0; exit" 0 1 2 3 4 5 6 7 8 10 12 13 14 15 trap "ipcrm -m `ipcs | grep ^m | cut -f2 -d" "` > /dev/null 2>&1; trap 0; exit" 0 1 2 3 4 5 6 7 8 10 12 13 14 15 xdoom-mus joystick4doom -k Should give you doom with sound effects and a joystick. With Amancio's musserver port, I get the intro music, but the musserver core dumps after that, while the rest of the game and sound effects go on. I'm running a Sound Blaster 32 (16) with stock 2.2-960612-SNAP sound drivers, so you might get better music results with other combinations. By the way, the URL with the joystick and music server: ftp://rah.star-gate.com/pub Randall Hopper rhh@ct.picker.com From owner-freebsd-current Thu Jul 25 20:03:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA21938 for current-outgoing; Thu, 25 Jul 1996 20:03:21 -0700 (PDT) Received: from felix.antiquity.arts.su.edu.au (felix.antiquity.arts.su.edu.AU [129.78.16.135]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA21860 for ; Thu, 25 Jul 1996 20:01:57 -0700 (PDT) Received: (from patc@localhost) by felix.antiquity.arts.su.edu.au (8.7.4/8.7.3) id NAA09970; Fri, 26 Jul 1996 13:00:50 +1000 From: Pat Caldon Message-Id: <199607260300.NAA09970@felix.antiquity.arts.su.edu.au> Subject: Re: Linux Java compiler on FreeBSD To: dfr@render.com (Doug Rabson) Date: Fri, 26 Jul 1996 13:00:50 +1000 (EST) Cc: freebsd-current@freebsd.org In-Reply-To: from "Doug Rabson" at Jul 22, 96 05:11:37 pm Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > I tried to download the libs from slackware-3.0 but that was the same > > version that I have (libc 5.0.9) and didn`t make any difference, is there > > a new one that this? > > I think I picked up the ones from redhat. I had to get an up-to-date > version of ld.so as well. You need version 5.2 or above I believe; 5.3.12 worked fine for me. pat. From owner-freebsd-current Thu Jul 25 21:34:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA26253 for current-outgoing; Thu, 25 Jul 1996 21:34:52 -0700 (PDT) Received: from caliban.dihelix.com (caliban.dihelix.com [199.4.33.251]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA26248; Thu, 25 Jul 1996 21:34:49 -0700 (PDT) Received: (from langfod@localhost) by caliban.dihelix.com (8.7.5/8.6.12) id SAA00979; Thu, 25 Jul 1996 18:34:43 -1000 (HST) Message-Id: <199607260434.SAA00979@caliban.dihelix.com> Subject: Re: SCO and Wordperfect 7 problems (socksys) To: jfieber@indiana.edu (John Fieber) Date: Thu, 25 Jul 1996 18:34:43 -1000 (HST) Cc: hackers@freebsd.org, current@freebsd.org In-Reply-To: from John Fieber at "Jul 25, 96 08:21:34 am" From: "David Langford" X-blank-line: This space intentionaly left blank. X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk John Fieber >On Wed, 24 Jul 1996, David Langford wrote: > >> I am trying to install Wordperfect 7 for SCO and I am getting the folowing >> errors: >> >> libsocket: socket: /dev/socksys: No such device or address >> Error: Can't open display: 127.0.0.1:0.0 > >Try setting the display to your (fully qualified) hostname. With >WP6.0, I couldn't even get started with :0.0 or unix:0.0 or >localhost:0.0, I had to use fallout.campusview.indiana.edu:0.0. >== jfieber@indiana.edu =========================================== > No DISPLAY I get: /dev/X0R: No such file or directory Error: Can't open display: :0.0 DISPLAY = caliban (what hostname and /etc/hosts think machine is): /dev/X0R: No such file or directory Error: Can't open display: caliban:0.0 DISPLAY = fqdn0.0 libsocket: socket: /dev/socksys: No such device or address libsocket: socket: /dev/socksys: No such device or address libsocket: socket: /dev/socksys: No such device or address Error: Can't open display: caliban.dihelix.com:0.0 DISPLAY = 127.0.0.1:0.0 libsocket: socket: /dev/socksys: No such device or address Error: Can't open display: 127.0.0.1:0.0 I dont have any other SCO programs to try (any one know of some???) and I dont have the WP6.0 demo- guess I can download it... weeee. Is anyone using SCO X stuff (like Wordperfect) on current?? -David Langford From owner-freebsd-current Thu Jul 25 21:53:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA26945 for current-outgoing; Thu, 25 Jul 1996 21:53:52 -0700 (PDT) Received: from localhost.my.domain (root@lennon-c12.aa.net [204.157.220.176]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA26940 for ; Thu, 25 Jul 1996 21:53:49 -0700 (PDT) Received: from localhost (smpatel@localhost [127.0.0.1]) by localhost.my.domain (8.7.5/8.6.12) with SMTP id VAA00927; Thu, 25 Jul 1996 21:53:29 -0700 (PDT) Date: Thu, 25 Jul 1996 21:53:27 -0700 (PDT) From: Sujal Patel X-Sender: smpatel@localhost To: Mostyn/Annabella cc: Chuck Robey , current@FreeBSD.ORG Subject: Re: Current, elfkit, linux ELF static bin In-Reply-To: <199607252142.OAA06919@linda.teleport.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 25 Jul 1996, Mostyn/Annabella wrote: > > > Running current with elfkit set up to provide /usr/libexec/ld-elf.so.1 > > > seems to run hand rolled ELF bins fine. > > > However, importing an ELF linux static bin and running (after installing > > > the linux lkm) bombs. > > > The binary is the "Bulldozer" WYSIWYG HTML editor from > > > http://cscsun1.larc.nasa.gov/~rboykin/Dozer/ With a dynamic binary, the image activater can uses some of the ELF header to determine which system the ELF binary was meant to run on. Unfortuantely, with the static binary, you can't tell whether the binary is meant for FreeBSD or for Linux. FreeBSD needs to implement a way of differentiating Linux & FreeBSD ELF binaries. Problem report 1102, describes one possible solution, but it is completely brain dead (it should work though). I believe NetBSD recently implemented a 'hack' to get this working for them. > > > ./dozer > > > Memory fault (core dumped) > > > > > > and produces a "garbled" directory which looks like > > > > > > drw-r----- 2 root wheel 512 Jul 23 15:45 Message-Id: <199607260648.XAA12470@relay.nuxi.com> Subject: Re: Crack 4.1 patches for FBSD To: coredump@nervosa.vendetta.com (goamatic) Date: Thu, 25 Jul 1996 23:48:00 -0700 (PDT) Cc: winter@jurai.net, freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG In-Reply-To: from goamatic at "Jul 25, 96 06:41:17 am" X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Here is beta 1 of the changes I have done to Crack 4.1 in order to > make it work with master.passwd (md5) style passwords. Patch from crack/ I wouldn't bother. I spoke with Alec Moffet today at the USENIX security conference. Crack 5.0 is due out in 6 (or so) weeks. He said it was a complete rewrite, and he has substantually changed the handing of different password file formats. -- David (obrien@cs.ucdavis.edu) From owner-freebsd-current Thu Jul 25 23:52:32 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA02752 for current-outgoing; Thu, 25 Jul 1996 23:52:32 -0700 (PDT) Received: from nervosa.netcom.com (nervosa.vendetta.com [192.187.167.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA02745; Thu, 25 Jul 1996 23:52:30 -0700 (PDT) Received: (from coredump@localhost) by nervosa.netcom.com (8.7.5/8.7.3) id XAA14706; Thu, 25 Jul 1996 23:53:01 -0700 (PDT) Date: Thu, 25 Jul 1996 23:53:00 -0700 (PDT) From: goamatic To: "David E. O'Brien" cc: winter@jurai.net, freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: Crack 4.1 patches for FBSD In-Reply-To: <199607260648.XAA12470@relay.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 25 Jul 1996, David E. O'Brien wrote: > > Here is beta 1 of the changes I have done to Crack 4.1 in order to > > make it work with master.passwd (md5) style passwords. Patch from crack/ > > I wouldn't bother. I spoke with Alec Moffet today at the USENIX security > conference. Crack 5.0 is due out in 6 (or so) weeks. He said it was a > complete rewrite, and he has substantually changed the handing of > different password file formats. > > -- David (obrien@cs.ucdavis.edu) > Yeah, well it's not like Crack is some hard programming feat in itself. Until than, the patch is available. == Chris Layne ======================================== Nervosa Computing == == coredump@nervosa.vendetta.com == http://nervosa.vendetta.com/~coredump == From owner-freebsd-current Fri Jul 26 00:29:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA04886 for current-outgoing; Fri, 26 Jul 1996 00:29:47 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA04859; Fri, 26 Jul 1996 00:29:39 -0700 (PDT) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id JAA14186; Fri, 26 Jul 1996 09:25:28 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id JAA13228; Fri, 26 Jul 1996 09:38:55 +0200 From: "Christoph P. Kukulies" Message-Id: <199607260738.JAA13228@gilberto.physik.rwth-aachen.de> Subject: Re: SCO and Wordperfect 7 problems (socksys) To: langfod@dihelix.com (David Langford) Date: Fri, 26 Jul 1996 09:38:54 +0200 (MET DST) Cc: jfieber@indiana.edu, hackers@freebsd.org, current@freebsd.org In-Reply-To: <199607260434.SAA00979@caliban.dihelix.com> from David Langford at "Jul 25, 96 06:34:43 pm" Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4ME+ PL16 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > John Fieber > >On Wed, 24 Jul 1996, David Langford wrote: > > > >> I am trying to install Wordperfect 7 for SCO and I am getting the folowing > >> errors: > >> > >> libsocket: socket: /dev/socksys: No such device or address > >> Error: Can't open display: 127.0.0.1:0.0 > > > >Try setting the display to your (fully qualified) hostname. With > >WP6.0, I couldn't even get started with :0.0 or unix:0.0 or > >localhost:0.0, I had to use fallout.campusview.indiana.edu:0.0. > >== jfieber@indiana.edu =========================================== > > > > No DISPLAY I get: > > /dev/X0R: No such file or directory > Error: Can't open display: :0.0 > > DISPLAY = caliban (what hostname and /etc/hosts think machine is): > > /dev/X0R: No such file or directory > Error: Can't open display: caliban:0.0 > > DISPLAY = fqdn0.0 > > libsocket: socket: /dev/socksys: No such device or address > libsocket: socket: /dev/socksys: No such device or address > libsocket: socket: /dev/socksys: No such device or address > Error: Can't open display: caliban.dihelix.com:0.0 > > DISPLAY = 127.0.0.1:0.0 > > libsocket: socket: /dev/socksys: No such device or address > Error: Can't open display: 127.0.0.1:0.0 > > I dont have any other SCO programs to try (any one know of some???) > and I dont have the WP6.0 demo- guess I can download it... weeee. > > Is anyone using SCO X stuff (like Wordperfect) on current?? > > -David Langford > Wasn't the clue just to do a touch /dev/socksys ? --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Fri Jul 26 00:43:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA05571 for current-outgoing; Fri, 26 Jul 1996 00:43:25 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA05566 for ; Fri, 26 Jul 1996 00:43:23 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id AAA01432; Fri, 26 Jul 1996 00:42:56 -0700 (PDT) To: "Justin T. Gibbs" cc: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch), freebsd-current@freebsd.org (FreeBSD-current users) Subject: Re: cvs commit: src/sys/dev/ccd ccd.c src/sys/dev/vn vn.c src/sys/sys conf.h src/sys/i386/isa fd.c mcd.c scd.c wcd.c wd.c wt.c s In-reply-to: Your message of "Thu, 25 Jul 1996 13:15:32 PDT." <199607252015.NAA28229@freefall.freebsd.org> Date: Fri, 26 Jul 1996 00:42:56 -0700 Message-ID: <1430.838366976@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Persistence would allow you to change the permissions on a device and > have them stick. If a device was not availible, it wouldn't show up > in /dev, but if it came back (say after replacing faulty hardware) > any permission changes you made in the past would show up as soon as > the device did. It would also allow you to make links, like: ln -s /dev/cuaa0 /dev/mouse Which get recreated automagically when devfs is next mounted. Yes, you could accomplish the same effect with a handful of commands in /etc/rc.local, but the point is to make it transparent and so obey the principle of least astonishment. Jordan From owner-freebsd-current Fri Jul 26 01:17:22 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA07429 for current-outgoing; Fri, 26 Jul 1996 01:17:22 -0700 (PDT) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA07403 for ; Fri, 26 Jul 1996 01:17:18 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.7.5/8.6.9) with SMTP id JAA13208; Fri, 26 Jul 1996 09:16:19 +0100 (BST) Date: Fri, 26 Jul 1996 09:16:17 +0100 (BST) From: Developer To: Joerg Wunsch cc: FreeBSD-current users Subject: Re: Termcap problems In-Reply-To: <199607251907.VAA22683@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 25 Jul 1996, J Wunsch wrote: > As Developer wrote: > > > Okay, for any window larger the 80 chars width it does it, but only in > > certain directories like / on one machine.. here is the output > > > > .CARD bin/ fd0/ lib@ proc/ > > sys@ > > .LOCK compat@ fnews/ lkm/ root/ > > tmp/ > > .cshrc dcf/ ftmp/ lost+found/ sbin/ > > usr/ > > .newuser dev/ httpd@ man@ schoolwww@ > > var/ > > .profile etc/ kernel* mnt/ stand@ > > www@ > > amitcp/ fastboot kernel.old* news@ store/ > > > > #stty -a > > > > speed 9600 baud; 24 rows; 110 columns; > > Perhaps a miscalculation that only hits in some special case. I bet > if you turn off the -F, it will look normally. > > You could have a look into the column number calculation, and file a > PR once you've got a fix. :-)) I see - you think the bug might be in ls? The strange thing is if I put on an old termcap from FreeBSD2.0 release I don`t get this problem. Thanks. Trefor S. From owner-freebsd-current Fri Jul 26 01:28:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA08954 for current-outgoing; Fri, 26 Jul 1996 01:28:24 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA08910; Fri, 26 Jul 1996 01:28:14 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id KAA02330; Fri, 26 Jul 1996 10:28:25 +0200 (MET DST) To: "David E. O'Brien" cc: coredump@nervosa.vendetta.com (goamatic), winter@jurai.net, freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: Crack 4.1 patches for FBSD In-reply-to: Your message of "Thu, 25 Jul 1996 23:48:00 PDT." <199607260648.XAA12470@relay.nuxi.com> Date: Fri, 26 Jul 1996 10:28:24 +0200 Message-ID: <2328.838369704@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199607260648.XAA12470@relay.nuxi.com>, "David E. O'Brien" writes: >> Here is beta 1 of the changes I have done to Crack 4.1 in order to >> make it work with master.passwd (md5) style passwords. Patch from crack/ > >I wouldn't bother. I spoke with Alec Moffet today at the USENIX security >conference. Crack 5.0 is due out in 6 (or so) weeks. He said it was a >complete rewrite, and he has substantually changed the handing of >different password file formats. Any news on any attacks on our MD5 based passwords ? -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Fri Jul 26 01:53:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA12344 for current-outgoing; Fri, 26 Jul 1996 01:53:26 -0700 (PDT) Received: from caliban.dihelix.com (caliban.dihelix.com [199.4.33.251]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA12324; Fri, 26 Jul 1996 01:53:21 -0700 (PDT) Received: (from langfod@localhost) by caliban.dihelix.com (8.7.5/8.6.12) id WAA00291; Thu, 25 Jul 1996 22:52:36 -1000 (HST) Message-Id: <199607260852.WAA00291@caliban.dihelix.com> Subject: Re: SCO and Wordperfect 7 problems (socksys) To: kuku@gilberto.physik.rwth-aachen.de Date: Thu, 25 Jul 1996 22:52:36 -1000 (HST) Cc: langfod@dihelix.com, jfieber@indiana.edu, hackers@freebsd.org, current@freebsd.org In-Reply-To: <199607260738.JAA13228@gilberto.physik.rwth-aachen.de> from "Christoph P. Kukulies" at "Jul 26, 96 09:38:54 am" From: "David Langford" X-blank-line: This space intentionaly left blank. X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> DISPLAY = 127.0.0.1:0.0 >> libsocket: socket: /dev/socksys: No such device or address >> Error: Can't open display: 127.0.0.1:0.0 >> >> I dont have any other SCO programs to try (any one know of some???) >> and I dont have the WP6.0 demo- guess I can download it... weeee. >> Is anyone using SCO X stuff (like Wordperfect) on current?? >> -David Langford > >Wasn't the clue just to do a touch /dev/socksys ? >--Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de Well I found this problemn out. MAKEDEV seems to create socksys as a device: MAKEDEV:socksys) MAKEDEV: rm -f socksys nfsd spx MAKEDEV: mknod socksys c 41 0 >-----^ MAKEDEV: mknod spx c 41 1 MAKEDEV: ln -s socksys nfsd MAKEDEV: chown root.wheel socksys nfsd spx MAKEDEV: chmod 666 socksys nfsd spx MAKEDEV: ;; removing socksys and linking it to /dev/null was the right trick. I assumed that MAKEDEV would do the right thing. ot that part out of the way. Now on to the next problem: % SCO/_I/wpinstg agre -bg grey Segmentation fault (core dumped) Last part of ktrace I have right now is: ... 276 wpinstg NAMI "shared/m_agre" 276 wpinstg RET open 4 276 wpinstg CALL ioctl(0x4,0x5401 ,0xefbfd6ba) 276 wpinstg RET ioctl -1 errno 25 Inappropriate ioctl for device 276 wpinstg CALL sendmsg(0x4,0xefbfd6a8) 276 wpinstg RET sendmsg 0 276 wpinstg CALL read(0x4,0x767de8,0x400) 276 wpinstg GIO fd 4 read 609 bytes "PREV_BUTTON= COMMENT=WordPerfect 7 for UNIX Systems blah blah blah Comment=DONE " 276 wpinstg RET read 609/0x261 276 wpinstg CALL read(0x4,0x767de8,0x400) 276 wpinstg GIO fd 4 read 0 bytes "" 276 wpinstg RET read 0 276 wpinstg CALL close(0x4) 276 wpinstg RET close 0 276 wpinstg PSIG SIGSEGV SIG_DFL 276 wpinstg NAMI "wpinstg.core" Not too helpful... trudging along. -David Langford langfod@dihelix.com From owner-freebsd-current Fri Jul 26 03:44:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA21080 for current-outgoing; Fri, 26 Jul 1996 03:44:38 -0700 (PDT) Received: from zit1.zit.th-darmstadt.de (root@zit1.zit.th-darmstadt.de [130.83.63.20]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA21057; Fri, 26 Jul 1996 03:44:25 -0700 (PDT) Received: from [130.83.63.13] (apfel.zit.th-darmstadt.de [130.83.63.13]) by zit1.zit.th-darmstadt.de (8.7.5/8.6.9) with ESMTP id MAA05550; Fri, 26 Jul 1996 12:43:54 +0200 (MET DST) X-Sender: petzi@mail.zit.th-darmstadt.de Message-Id: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 26 Jul 1996 12:43:28 +0200 To: "Stefan Bethke" From: Michael Beckmann Subject: Re: ncr53c810 driver in sta Cc: current@freebsd.org, stable@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 10:32 Uhr +0200 23.7.1996, Stefan Bethke wrote: >We have a similiar problem here: Asus SP3G-II (Neptune II chipset), I was under the impression that the SP3G had a Saturn II Chipset. >It hangs sometimes on reboots, after clearing the screen. However, when it >does, it corrupts the BIOS nvram, so I have to re-enter all BIOS settings >:-( That happened to me, too, when I was still using an SP3G mainboard. Later I upgraded it with a Gigabyte 586 ATE/P mainboard, and recently with a Gigabyte 586 HX mainboard; both equipped with an Asus SC-200 PCI controller (NCR 53c810 based); and with both Gigabyte board / Asus controller combinations I have never had a problem. Michael From owner-freebsd-current Fri Jul 26 05:40:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA24826 for current-outgoing; Fri, 26 Jul 1996 05:40:46 -0700 (PDT) Received: from spooky.eis.net.au (root@spooky.eis.net.au [203.12.171.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA24731 for ; Fri, 26 Jul 1996 05:37:20 -0700 (PDT) Received: (from ernie@localhost) by spooky.eis.net.au (8.7.5/8.6.12) id WAA06937 for freebsd-current@freebsd.org; Fri, 26 Jul 1996 22:36:25 +1000 (EST) From: Ernie Elu Message-Id: <199607261236.WAA06937@spooky.eis.net.au> Subject: Adding a second scsi drive To: freebsd-current@freebsd.org Date: Fri, 26 Jul 1996 22:36:24 +1000 (EST) X-Mailer: ELM [version 2.4ME+ PL15 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Can someone one email me a set of instructions on how to add a second scsi drive with -current without using sysinstall? Sysinstall still core dumps when I try and usr it to partition and and disklabel the second drive. - Ernie. From owner-freebsd-current Fri Jul 26 08:24:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA01857 for current-outgoing; Fri, 26 Jul 1996 08:24:24 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA01825; Fri, 26 Jul 1996 08:24:00 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id JAA11010; Fri, 26 Jul 1996 09:19:51 -0600 (MDT) Date: Fri, 26 Jul 1996 09:19:51 -0600 (MDT) Message-Id: <199607261519.JAA11010@rocky.mt.sri.com> From: Nate Williams To: "David Langford" Cc: jfieber@indiana.edu (John Fieber), hackers@freebsd.org, current@freebsd.org Subject: Re: SCO and Wordperfect 7 problems (socksys) In-Reply-To: <199607260434.SAA00979@caliban.dihelix.com> References: <199607260434.SAA00979@caliban.dihelix.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Is anyone using SCO X stuff (like Wordperfect) on current?? Yep. However, all of my /dev stuff is in /compat/ibcs2. I'm on a business trip right now so I can't show you what's it's supposed to look like, but it works. Also, are you running -current, or a 2.2-SNAP? Nate From owner-freebsd-current Fri Jul 26 10:27:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA10629 for current-outgoing; Fri, 26 Jul 1996 10:27:53 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA10619 for ; Fri, 26 Jul 1996 10:27:35 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with SMTP id LAA28387; Fri, 26 Jul 1996 11:27:20 -0600 (MDT) Message-Id: <199607261727.LAA28387@rover.village.org> To: "Jordan K. Hubbard" Subject: Re: cvs commit: src/sys/dev/ccd ccd.c src/sys/dev/vn vn.c src/sys/sys conf.h src/sys/i386/isa fd.c mcd.c scd.c wcd.c wd.c wt.c s Cc: freebsd-current@FreeBSD.ORG (FreeBSD-current users) In-reply-to: Your message of Fri, 26 Jul 1996 00:42:56 PDT Date: Fri, 26 Jul 1996 11:27:19 -0600 From: Warner Losh Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk : It would also allow you to make links, like: : : ln -s /dev/cuaa0 /dev/mouse : : Which get recreated automagically when devfs is next mounted. Yes, : you could accomplish the same effect with a handful of commands in : /etc/rc.local, but the point is to make it transparent and so obey the : principle of least astonishment. Hmmm, sounds like what is needed is a file system that maintains a file, lets call it /etc/devperms to invent a name. When you mount this file system, it reads that file. When you hack this file system, it hacks that file for you. When you unmount, nothing would happen to that file. All of this is dependent, of course, on the existance of real devices on the system. I don't know how hard something like that would be to do, but I think that's what people are asking for.... Warner From owner-freebsd-current Fri Jul 26 11:24:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA13735 for current-outgoing; Fri, 26 Jul 1996 11:24:43 -0700 (PDT) Received: from dworshak.cs.uidaho.edu (dworshak.cs.uidaho.edu [129.101.100.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA13721 for ; Fri, 26 Jul 1996 11:24:39 -0700 (PDT) Received: from waldrog.cs.uidaho.edu (waldrog.cs.uidaho.edu [129.101.100.23]) by dworshak.cs.uidaho.edu (8.7.5/1.1) with ESMTP id LAA23453; Fri, 26 Jul 1996 11:24:33 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by waldrog.cs.uidaho.edu (8.7.5/1.0) with SMTP id LAA21250; Fri, 26 Jul 1996 11:24:33 -0700 (PDT) X-Authentication-Warning: waldrog.cs.uidaho.edu: Host localhost [127.0.0.1] didn't use HELO protocol To: "Justin T. Gibbs" cc: current@freebsd.org Subject: Re: bt946 problems. In-reply-to: Your message of "Thu, 25 Jul 1996 08:28:26 PDT." <199607251528.IAA05481@freefall.freebsd.org> Date: Fri, 26 Jul 1996 11:24:32 PDT Message-ID: <21247.838405472@waldrog.cs.uidaho.edu> From: faried nawaz Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk "Justin T. Gibbs" wrote... The ISA bt probe is screwing you up. Take the ISA bt stuff out of your kernel config file. Use controller bt0 instead of controller bt0 at isa?... Ah! Okay, trying... Now it doesn't display the "bt: unit number.." lines, but it still hangs after the npx lines. I tested this with -current, as of July 24th. From owner-freebsd-current Fri Jul 26 11:32:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA14427 for current-outgoing; Fri, 26 Jul 1996 11:32:11 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA14415 for ; Fri, 26 Jul 1996 11:32:09 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id NAA17041; Fri, 26 Jul 1996 13:30:34 -0500 From: Joe Greco Message-Id: <199607261830.NAA17041@brasil.moneng.mei.com> Subject: Re: cvs commit: src/sys/dev/ccd ccd.c src/sys/dev/vn vn.c src/sys/sys conf.h src/sys/i386/isa fd.c mcd.c scd.c wcd.c wd.c wt.c s To: imp@village.org (Warner Losh) Date: Fri, 26 Jul 1996 13:30:33 -0500 (CDT) Cc: jkh@time.cdrom.com, freebsd-current@freebsd.org In-Reply-To: <199607261727.LAA28387@rover.village.org> from "Warner Losh" at Jul 26, 96 11:27:19 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > : It would also allow you to make links, like: > : > : ln -s /dev/cuaa0 /dev/mouse > : > : Which get recreated automagically when devfs is next mounted. Yes, > : you could accomplish the same effect with a handful of commands in > : /etc/rc.local, but the point is to make it transparent and so obey the > : principle of least astonishment. > > Hmmm, sounds like what is needed is a file system that maintains a > file, lets call it /etc/devperms to invent a name. When you mount > this file system, it reads that file. When you hack this file system, > it hacks that file for you. When you unmount, nothing would happen to > that file. All of this is dependent, of course, on the existance of > real devices on the system. I don't have anything useful to suggest other than to note that Sun took the easy way out of this problem by implementing a "devfs-on-ufs", i.e. they use UFS and have a procedure for "automatically" creating new instances of devices. Their method does preserve permissions, etc., but it does so at the awful price of a half-baked implementation that I really can't stand. ... JG From owner-freebsd-current Fri Jul 26 11:44:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA15645 for current-outgoing; Fri, 26 Jul 1996 11:44:57 -0700 (PDT) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA15637 for ; Fri, 26 Jul 1996 11:44:54 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA05293; Fri, 26 Jul 1996 14:43:37 -0400 Date: Fri, 26 Jul 1996 14:43:37 -0400 From: Garrett Wollman Message-Id: <9607261843.AA05293@halloran-eldar.lcs.mit.edu> To: Joe Greco Cc: imp@village.org (Warner Losh), jkh@time.cdrom.com, freebsd-current@freebsd.org Subject: Re: cvs commit: src/sys/dev/ccd ccd.c src/sys/dev/vn vn.c src/sys/sys conf.h src/sys/i386/isa fd.c mcd.c scd.c wcd.c wd.c wt.c s In-Reply-To: <199607261830.NAA17041@brasil.moneng.mei.com> References: <199607261727.LAA28387@rover.village.org> <199607261830.NAA17041@brasil.moneng.mei.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk < said: > I don't have anything useful to suggest other than to note that Sun took the > easy way out of this problem by implementing a "devfs-on-ufs", i.e. they use > UFS and have a procedure for "automatically" creating new instances of > devices. Well, perhaps this is an indication of the correct way to implement persistence. Filesystems keep device nodes as they currently exist, but they don't actually do anything---they are just place-holders that return ENXIO or some such if you try to do anything to them. However, if a devfs layer is stacked on top of a directory containing such a node, then the devfs hides any device nodes that are not available in the running system, and ``adopts'' the permissions of the underlying nodes for its own local devices. That way, upgrading an old system to devfs would Just Work. Attempts to change the permissions of a node would cause a new node to be created in the underlying filesystem, and the permissions changed on that, as well. This fixes the persistence problem, leverages our stackable filesystem infrastructure in a useful way, and makes devices work again over NFS. (This wouldn't support renaming of devices, but I don't know if that's at all useful if we have symbolic links instead.) Julian, does this sound reasonable to you? -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, ANA, or NSA| - Susan Aglukark and Chad Irschick From owner-freebsd-current Fri Jul 26 12:04:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA16759 for current-outgoing; Fri, 26 Jul 1996 12:04:28 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA16754 for ; Fri, 26 Jul 1996 12:04:26 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id OAA18686; Fri, 26 Jul 1996 14:03:53 -0500 From: Joe Greco Message-Id: <199607261903.OAA18686@brasil.moneng.mei.com> Subject: Re: cvs commit: src/sys/dev/ccd ccd.c src/sys/dev/vn vn.c src/sys/sys conf.h src/sys/i386/isa fd.c mcd.c scd.c wcd.c wd.c wt.c s To: wollman@lcs.mit.edu (Garrett Wollman) Date: Fri, 26 Jul 1996 14:03:53 -0500 (CDT) Cc: current@freebsd.org, imp@village.org, jkh@time.cdrom.com In-Reply-To: <9607261843.AA05293@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at Jul 26, 96 02:43:37 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > < said: > > > I don't have anything useful to suggest other than to note that Sun took the > > easy way out of this problem by implementing a "devfs-on-ufs", i.e. they use > > UFS and have a procedure for "automatically" creating new instances of > > devices. > > Well, perhaps this is an indication of the correct way to implement > persistence. Uh, no. I should have mentioned, also, that it's done as symlinks into a botched and bizarre /devices hierarchy that causes no end of grief when you switch slots, etc... I was just bi***ing about how NOT to do it. :-) > Filesystems keep device nodes as they currently exist, > but they don't actually do anything---they are just place-holders that > return ENXIO or some such if you try to do anything to them. > However, if a devfs layer is stacked on top of a directory containing > such a node, then the devfs hides any device nodes that are not > available in the running system, and ``adopts'' the permissions of the > underlying nodes for its own local devices. That way, upgrading an > old system to devfs would Just Work. Attempts to change the > permissions of a node would cause a new node to be created in the > underlying filesystem, and the permissions changed on that, as well. > This fixes the persistence problem, leverages our stackable filesystem > infrastructure in a useful way, and makes devices work again over > NFS. (This wouldn't support renaming of devices, but I don't know if > that's at all useful if we have symbolic links instead.) > > Julian, does this sound reasonable to you? So, what you're saying is, sort of a strange union mount where the "devfs" overlays /dev. /dev contains the permissions, symlinks for aliases, owners, etc. "devfs" obscures nonexistent devices.. and also creates devices that do not exist in the underlying layer that do exist.. Wow, I don't see a problem.. that does actually sound workable. Unfortunately I don't have the time or knowledge to code something of this complexity :-( ... JG From owner-freebsd-current Fri Jul 26 12:14:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA17163 for current-outgoing; Fri, 26 Jul 1996 12:14:36 -0700 (PDT) Received: from neworder.cc.uky.edu (neworder.cc.uky.edu [128.163.18.198]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA17154 for ; Fri, 26 Jul 1996 12:14:33 -0700 (PDT) Received: (from soward@localhost) by neworder.cc.uky.edu (8.7/Soward0.1) id PAA02955 for current@freebsd.org; Fri, 26 Jul 1996 15:14:40 -0400 (EDT) Message-Id: <199607261914.PAA02955@neworder.cc.uky.edu> MIME-Version: 1.0 (NeXT Mail 4.0 v141) Content-Type: text/plain Received: by NeXT.Mailer (1.141) From: John Soward Date: Fri, 26 Jul 96 15:14:39 -0400 To: current@freebsd.org Subject: Re: SCO and Wordperfect 7 problems (socksys) Reply-To: soward@service1.uky.edu References: <199607260434.SAA00979@caliban.dihelix.com> <199607261519.JAA11010@rocky.mt.sri.com> Organization: University of Kentucky Technical Services X-URL: "http://neworder.cc.uky.edu/" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm not using WP, but another SCO application...here's what I have...this wasn't very well documented...if you read the code for the ibcs2 stuff ;) % ls -ltr /compat/ibcs2/dev total 0 crw-rw-rw- 1 root wheel 41, 0 3/96 11:32:5 spx -rw-rw-r-- 1 root wheel 0 3/96 11:33:2 null lrwxrwxr-x 1 root wheel 9 3/96 11:33:2 socksys -> /dev/null lrwxrwxr-x 1 root wheel 7 3/96 11:33:2 nfsd -> socksys lrwxrwxr-x 1 root wheel 9 3/96 11:33:2 XOR -> /dev/null --- John Soward JpS Systems Programmer 'The Midnight sun will burn you up.' University of Kentucky (NeXT and MIME mail OK) -R. Smith From owner-freebsd-current Fri Jul 26 12:37:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA18467 for current-outgoing; Fri, 26 Jul 1996 12:37:26 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA18462; Fri, 26 Jul 1996 12:37:21 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id VAA03121; Fri, 26 Jul 1996 21:37:22 +0200 (MET DST) To: Joe Greco cc: wollman@lcs.mit.edu (Garrett Wollman), current@FreeBSD.ORG, imp@village.org, jkh@time.cdrom.com Subject: Re: cvs commit: src/sys/dev/ccd ccd.c src/sys/dev/vn vn.c src/sys/sys conf.h src/sys/i386/isa fd.c mcd.c scd.c wcd.c wd.c wt.c s In-reply-to: Your message of "Fri, 26 Jul 1996 14:03:53 CDT." <199607261903.OAA18686@brasil.moneng.mei.com> Date: Fri, 26 Jul 1996 21:37:22 +0200 Message-ID: <3119.838409842@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As much as I pride myself with never agreeing with Garrett, I'm having a hard time finding a reason not to in this particular case. :-) There are a couple of fine points still not resolved. There is >still< no way to generally specify a policy: "Make all disks foo.bar mode 0640" and such. The major/minor of the underlying nodes are of course of no significance, but wouldn't it be nice to get rid of all that blasted code entirely ? Why would we even care about the type of node apart from "Directory" or "Not Directory" ? Ie, we could mount devfs on a FS that doesn't support c/b devs at all (msdos, hfs ...) -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Fri Jul 26 12:49:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA19441 for current-outgoing; Fri, 26 Jul 1996 12:49:39 -0700 (PDT) Received: from hermes.algonet.se (mail.algonet.se [193.12.207.206]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA19436 for ; Fri, 26 Jul 1996 12:49:35 -0700 (PDT) Received: from (johang@bengt.algonet.se [193.12.207.211]) by hermes.algonet.se (8.7.4/hdw.1.0) with SMTP id VAA10211 for ; Fri, 26 Jul 1996 21:49:32 +0200 (MET DST) Message-Id: <199607261949.VAA10211@hermes.algonet.se> Comments: Authenticated sender is From: "Johan Granlund" To: freebsd-current@FreeBSD.org Date: Fri, 26 Jul 1996 22:44:02 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: A new twist on the reboot problems Priority: normal X-mailer: Pegasus Mail for Windows (v2.33) Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > Incidentally, if you want to be *sure* you capture all panic > > output, you might consider putting a comconsole into your kernel > > and hooking a serial terminal with scrollback and/or logging (old > > PC running kermit works fine) up to be the console. Then, no > > matter what gets written, or not written, before the machine > > freaks out, and before fsck "cleans" everything, you have it all > > logged on a separate machine. Once upon a time there was a beast called teletype. I miss them. /Johan ___________________________________________________________ Internet: Johang@Algonet.se I don't even speak for myself From owner-freebsd-current Fri Jul 26 13:03:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA20348 for current-outgoing; Fri, 26 Jul 1996 13:03:54 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA20340 for ; Fri, 26 Jul 1996 13:03:46 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id PAA18767; Fri, 26 Jul 1996 15:03:08 -0500 From: Joe Greco Message-Id: <199607262003.PAA18767@brasil.moneng.mei.com> Subject: Re: cvs commit: src/sys/dev/ccd ccd.c src/sys/dev/vn vn.c src/sys/sys conf.h src/sys/i386/isa fd.c mcd.c scd.c wcd.c wd.c wt.c s To: phk@critter.tfs.com (Poul-Henning Kamp) Date: Fri, 26 Jul 1996 15:03:08 -0500 (CDT) Cc: wollman@lcs.mit.edu, current@FreeBSD.ORG, imp@village.org, jkh@time.cdrom.com In-Reply-To: <3119.838409842@critter.tfs.com> from "Poul-Henning Kamp" at Jul 26, 96 09:37:22 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > As much as I pride myself with never agreeing with Garrett, I'm having a > hard time finding a reason not to in this particular case. :-) > > There are a couple of fine points still not resolved. > There is >still< no way to generally specify a policy: > "Make all disks foo.bar mode 0640" > and such. This is a good point. There are some of us who use things like amanda for backups, and currently I rely on blind chance and the amanda report to remind me when I have bad permissions on a disk. My personal opinion, however, is that you can make this sort of a thing into a real problem and go to great lengths to "solve" it at ridiculous cost in complexity. Let's say, for example, that you were to create a "sd.defaults" file that specifies the default permissions for any newly created sd device. Well that's fine for the general case, but now somebody wants a special case for sd5, which holds a raw-partition database. It starts to get icky. The cure is worse than the disease, IMVHO. Unless somebody has a functionally better cure... I probably am not qualified to be a part of this architectural discussion anyways so I'll butt out now :-) I'm just speaking as someone who has gotten very tired of ./MAKEDEV sd13 sd13s1 sd13s1e sd14 sd14s1 sd14s1e > The major/minor of the underlying nodes are of course of no significance, > but wouldn't it be nice to get rid of all that blasted code entirely ? > > Why would we even care about the type of node apart from "Directory" or > "Not Directory" ? Ie, we could mount devfs on a FS that doesn't support > c/b devs at all (msdos, hfs ...) I wouldn't care :-) I think that would be a superb feature. ... JG From owner-freebsd-current Fri Jul 26 13:10:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA20635 for current-outgoing; Fri, 26 Jul 1996 13:10:17 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA20625 for ; Fri, 26 Jul 1996 13:10:12 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id NAA20263; Fri, 26 Jul 1996 13:09:54 -0700 (PDT) To: Poul-Henning Kamp cc: wollman@lcs.mit.edu (Garrett Wollman), current@FreeBSD.ORG, imp@village.org Subject: Re: cvs commit: src/sys/dev/ccd ccd.c src/sys/dev/vn vn.c src/sys/sys conf.h src/sys/i386/isa fd.c mcd.c scd.c wcd.c wd.c wt.c s In-reply-to: Your message of "Fri, 26 Jul 1996 21:37:22 +0200." <3119.838409842@critter.tfs.com> Date: Fri, 26 Jul 1996 13:09:54 -0700 Message-ID: <20261.838411794@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > There are a couple of fine points still not resolved. > There is >still< no way to generally specify a policy: > "Make all disks foo.bar mode 0640" You wouldn't be losing anything though - we don't have this now! :-) You could still make the foo.bar devices underneath and chmod them 640, which is not as elegant, no, but still gives the "traditional" UNIX user a solution which makes sense. I wouldn't leave this as a sticking point since the proposal solves so many of the problems people have been complaining about so far, it should just be done. > Why would we even care about the type of node apart from "Directory" or > "Not Directory" ? Ie, we could mount devfs on a FS that doesn't support > c/b devs at all (msdos, hfs ...) I suppose that's true too! If you found a regular file named fd0a with perms 700 then you'd just borrow the perms and ignore the type? Jordan From owner-freebsd-current Fri Jul 26 13:11:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA20764 for current-outgoing; Fri, 26 Jul 1996 13:11:39 -0700 (PDT) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA20708; Fri, 26 Jul 1996 13:11:20 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-42.slip.Uni-Koeln.DE) by Sisyphos with SMTP id AA02113 (5.67b/IDA-1.5); Fri, 26 Jul 1996 22:10:13 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.7.5/8.6.9) id WAA00324; Fri, 26 Jul 1996 22:09:39 +0200 (MET DST) Date: Fri, 26 Jul 1996 22:09:39 +0200 (MET DST) Message-Id: <199607262009.WAA00324@x14.mi.uni-koeln.de> From: Stefan Esser To: Cat Okita Cc: "Marc G. Fournier" , Stefan Esser , jkh@freebsd.org, current@freebsd.org, stable@freebsd.org, dg@root.com Subject: Obtaining a kernel core with NCR In-Reply-To: References: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Cat Okita writes: > > > 4) does it always hang ? > > Everytime it crashes, yes...doing reboot from the console > > has never hung it... > > *Only* when it crashes - a planned reboot, be it remote or local always seems > to work. Well, I just thought it might be a good idea to let you know, whether your system suffers form the same hang in the kernel dump code as mine. If you can afford the time to test this, I'd really appreciate receiving your results! The test requires a kernel compile a few more minutes of time for a the actual test. It does not cause a corrupt or dirty file system to be left over. (The FS is mounted R/O in single user mode anyway). 1) build a kernel with options "SCSI_DEBUG_FLAGS=DEBUG_SCATTER" options DDB 2) boot this kernel into single user mode 3) enter the command "dumpon /dev/sd0b" if you did not already define the dump device on the "config kernel" line in the config file 4) enter DDB by pressing CTL+ALT+ESC or CTL+Print depending on your keyboard (this is for syscons, don't know about PCVT) 5) enter the command "panic" at the debugger prompt. You will see a lot of trace output flow by, and it will stop with the well-known SCSI hang. My guess is, that the physical address of the last memory page touched is in the BIOS region. Please let me know what actual addresses (virtual and physical) there are at the start of the last scatter/gather block reported. Regards, STefan From owner-freebsd-current Fri Jul 26 13:19:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA21360 for current-outgoing; Fri, 26 Jul 1996 13:19:11 -0700 (PDT) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA21323; Fri, 26 Jul 1996 13:18:55 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-42.slip.Uni-Koeln.DE) by Sisyphos with SMTP id AA02248 (5.67b/IDA-1.5); Fri, 26 Jul 1996 22:18:45 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.7.5/8.6.9) id VAA00305; Fri, 26 Jul 1996 21:45:55 +0200 (MET DST) Date: Fri, 26 Jul 1996 21:45:55 +0200 (MET DST) Message-Id: <199607261945.VAA00305@x14.mi.uni-koeln.de> From: Stefan Esser To: Michael Beckmann Cc: current@freebsd.org, stable@freebsd.org Subject: Re: ncr53c810 driver in sta In-Reply-To: References: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Michael Beckmann writes: > At 10:32 Uhr +0200 23.7.1996, Stefan Bethke wrote: > > >We have a similiar problem here: Asus SP3G-II (Neptune II chipset), > > I was under the impression that the SP3G had a Saturn II Chipset. Mine does :) > >It hangs sometimes on reboots, after clearing the screen. However, when it > >does, it corrupts the BIOS nvram, so I have to re-enter all BIOS settings > >:-( > > That happened to me, too, when I was still using an SP3G mainboard. The ASUS SP3G seems to need a "options BROKEN_KEYBOARD_RESET" line in the kernel config file. Mine does ... > Later I upgraded it with a Gigabyte 586 ATE/P mainboard, and recently with > a Gigabyte 586 HX mainboard; both equipped with an Asus SC-200 PCI > controller (NCR 53c810 based); and with both Gigabyte board / Asus > controller combinations I have never had a problem. That's not at all related to the SCSI controller. Regards, STefan From owner-freebsd-current Fri Jul 26 13:19:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA21535 for current-outgoing; Fri, 26 Jul 1996 13:19:48 -0700 (PDT) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA21443; Fri, 26 Jul 1996 13:19:32 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-42.slip.Uni-Koeln.DE) by Sisyphos with SMTP id AA02251 (5.67b/IDA-1.5); Fri, 26 Jul 1996 22:18:48 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.7.5/8.6.9) id VAA00315; Fri, 26 Jul 1996 21:57:50 +0200 (MET DST) Date: Fri, 26 Jul 1996 21:57:50 +0200 (MET DST) Message-Id: <199607261957.VAA00315@x14.mi.uni-koeln.de> From: Stefan Esser To: Cat Okita Cc: "Marc G. Fournier" , Stefan Esser , jkh@freebsd.org, current@freebsd.org, stable@freebsd.org, dg@root.com Subject: Re: ncr53c810 driver in stable/current In-Reply-To: References: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Cat Okita writes: > On Mon, 22 Jul 1996, Marc G. Fournier wrote: > > Same, on shutdown, not startup... > > I have a vague recollection of a panic on not being able to write to assigned > vnode (or something along those lines - it *was* 3:30am) > > > requires a power-off, but am not 100% certain, since I've gotten > > into the habit of doing a cold boot (99.9% certain the habit is because > > ctl-alt-del didn't work) > > Definately requires a power off - the keyboard doesn't respond to any key > or combination that I've tried. > > > > 4) does it always hang ? > > Everytime it crashes, yes...doing reboot from the console > > has never hung it... > > *Only* when it crashes - a planned reboot, be it remote or local always seems > to work. Ok. Today I found some time to have my system crash for the sake of science :-) Well, the hang occurs and it really can't be interrupted from the keyboard. But the code did work at some time, and it in fact still does. Mostly ... The dump writes out the first few MB within less than a second, and then the SCSI LED stays on and the system hangs, always after accessing the same virtual address. It took me some time to think about checking which physical address that corresponds to that page, and to my surprise I found that the BIOS region at e8000 is the last thing touched by the NCR chip. I have no idea why the page at 0e8000 is mapped into the kernel, and I do not think that I got some device at that address. But it still causes the hang :( I will add a debugging printf to the VM code, to identify the subroutine that registers a mapping for that physical address. Just wanted to let those interested in obtaining core dumps with the NCR know, that I'm working on this. I'd really appreciate if somebody could tell me why writing the page at 0e8000 to disk is a bad idea :) Regards, STefan From owner-freebsd-current Fri Jul 26 13:20:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA21695 for current-outgoing; Fri, 26 Jul 1996 13:20:17 -0700 (PDT) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA21573; Fri, 26 Jul 1996 13:19:55 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-42.slip.Uni-Koeln.DE) by Sisyphos with SMTP id AA02254 (5.67b/IDA-1.5); Fri, 26 Jul 1996 22:18:52 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.7.5/8.6.9) id VAA00299; Fri, 26 Jul 1996 21:43:44 +0200 (MET DST) Date: Fri, 26 Jul 1996 21:43:44 +0200 (MET DST) Message-Id: <199607261943.VAA00299@x14.mi.uni-koeln.de> From: Stefan Esser To: "Stefan Bethke" Cc: jkh@freebsd.org, "Stefan Esser" , current@freebsd.org, dg@root.com, "Marc G. Fournier" , stable@freebsd.org Subject: Re: ncr53c810 driver in sta In-Reply-To: References: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Stefan Bethke writes: > We have a similiar problem here: Asus SP3G-II (Neptune II chipset), 810, = > Quantum Fireball, but I'm not sure it is related to the 810 in any way. Well, the SP3G has originally been delivered with a Saturn II (rev. 4) chip set. Guess that is what you got ... (???) > It hangs sometimes on reboots, after clearing the screen. However, when = > it does, it corrupts the BIOS nvram, so I have to re-enter all BIOS = > settings :-( This is most likely a problem with your NVRAM (ie. a hardware problem). > > 5) do you know that the hang is not caused by some unrelated > > problem (BROKEN_KEYBOARD_RESET comes to mind :) ? > > Can you give me a pointer where to find an explanation of the broken = > reset? This has been discussed a few months ago. You may try to seach for the key word in an archive of the mailing lists. I had to add the "options BROKEN_KEYBOARD_RESET" line to the kernel config file of my ASUS SP3g ... Regards, STefan From owner-freebsd-current Fri Jul 26 13:29:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA22680 for current-outgoing; Fri, 26 Jul 1996 13:29:35 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA22669 for ; Fri, 26 Jul 1996 13:29:31 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id PAA18823; Fri, 26 Jul 1996 15:28:06 -0500 From: Joe Greco Message-Id: <199607262028.PAA18823@brasil.moneng.mei.com> Subject: Re: A new twist on the reboot problems To: johang@algonet.se (Johan Granlund) Date: Fri, 26 Jul 1996 15:28:05 -0500 (CDT) Cc: freebsd-current@freebsd.org In-Reply-To: <199607261949.VAA10211@hermes.algonet.se> from "Johan Granlund" at Jul 26, 96 10:44:02 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > matter what gets written, or not written, before the machine > > > freaks out, and before fsck "cleans" everything, you have it all > > > logged on a separate machine. > > Once upon a time there was a beast called teletype. > > I miss them. Teletypes suck. They are old, slow, clunky, noisy, and eat great quantities of paper. They cannot be accessed from remote, you cannot bring up their output in an X11 window and use cut-n-paste. A small FreeBSD based console manager box would have none of these flaws :-) (However you could not take a baseball bat to the FreeBSD box without fear of hardware failure). It would be particularly efficient at dealing with a larger number of other boxes, 1 < n < 10. For anyone who is interested, I should have a prototype set up shortly. What I plan to do: Set up small FreeBSD box. With a large disk. And a modem. And its own Kerberos domain, and encrypted telnet. This will allow me to log in remotely or locally, in a secure fashion. Stick in a multiport serial card. Connected to the COM1: serial ports of other FreeBSD machines, running comconsole. Set up a user, "consmgr". Install "screen" and "kermit". Set up /etc/rc such that "screen" is kicked off on ttyv4 as user "consmgr". I explicitly do not wish to do this out of /etc/ttys. This is just to initialize the system after a reboot. Set up "consmgr" user's account such that "screen -d; screen -r" is executed upon login. This means essentially that consmgr will have a virtual session active for as long as the box is up, and as long as the admin is careful not to kill a session.. Set up kermit scripts that open a unique log file and connect to a specific port (i.e. a remote FreeBSD box's console). In consmgr's .screenrc, automatically kick off each kermit script in a different window. Now we are flying. I can log in from anywhere in the world, via Inet or modem, or on console, securely, and access half a dozen other boxes' consoles, review their console output, etc. With a little work, the box hosting consmgr could be outfitted with reset-button outputs for the other boxes, or power controls, etc. That would not be out-of-the-box technology (although you COULD use xtend if you were desperate for a quick solution).. UNIX: the flexibility to leverage off of an apparently unrelated set of powerful tools to do something cool. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/546-7968 From owner-freebsd-current Fri Jul 26 13:41:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA23493 for current-outgoing; Fri, 26 Jul 1996 13:41:10 -0700 (PDT) Received: from gemini.scl.ameslab.gov (gemini.scl.ameslab.gov [147.155.138.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA23487 for ; Fri, 26 Jul 1996 13:41:06 -0700 (PDT) Received: (from ccsanady@localhost) by gemini.scl.ameslab.gov (950413.SGI.8.6.12/8.6.12) id UAA19146; Fri, 26 Jul 1996 20:40:24 GMT From: Chris Csanady Message-Id: <199607262040.UAA19146@gemini.scl.ameslab.gov> Subject: ep driver somewhat broken... To: freebsd-current@FreeBSD.ORG Date: Fri, 26 Jul 1996 15:40:24 -0500 (CDT) Cc: ccsanady@scl.ameslab.gov X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I just compiled current from 2.1.5 yesterday, and now the ep driver is broken. Essentially, the driver will not stay in UTP mode. Or at least i think this is the problem.. It may be completely unrelated. What happens though, is every couple minutes (or less) my networking hanges. Doing a 'ifconfig ep0 -link0 -link1' fixes the problem. If anyone has any idea what the problem is, or fixes it, Id really appreciate it. :) Also, please leave my address in the cc, as I will probably not be receiving anything off the lists soon... Thanks, Chris Csanady From owner-freebsd-current Fri Jul 26 14:25:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA28098 for current-outgoing; Fri, 26 Jul 1996 14:25:00 -0700 (PDT) Received: from paris.CS.Berkeley.EDU (paris.CS.Berkeley.EDU [128.32.34.47]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA28074 for ; Fri, 26 Jul 1996 14:24:57 -0700 (PDT) Received: from paris.CS.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by paris.CS.Berkeley.EDU (8.6.11/8.6.9) with ESMTP id OAA27498; Fri, 26 Jul 1996 14:24:27 -0700 From: Josh MacDonald Message-Id: <199607262124.OAA27498@paris.CS.Berkeley.EDU> To: faried nawaz cc: freebsd-current@freebsd.org Subject: Re: Linux Emu. In-reply-to: Your message of "Sun, 21 Jul 1996 03:04:42 PDT." <15545.837943482@waldrog.cs.uidaho.edu> Date: Fri, 26 Jul 1996 14:24:26 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > spazboy-whq wrote... > > Has anyone succesfully gotten Quake to run in FreeBSD-Current with the > linux emu ? > > I ran linux_qtest1 fine a few days ago on -current (as of July 3rd). > I have run versions of quake up to v0.91 on FreeBSD deceit.xcf.berkeley.edu 2.2-960612-SNAP FreeBSD 2.2-960612-SNAP #0: Mon, 17 Jun 1996 15:51:19 -0700 jmacd@deceit.xcf.berkeley.edu:/home3/2.2/src/sys/compile/DECEIT i386 The only thing I miss is sound. DOOM no longer runs, when last I tried. -josh From owner-freebsd-current Fri Jul 26 14:32:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA29653 for current-outgoing; Fri, 26 Jul 1996 14:32:38 -0700 (PDT) Received: from sasami.jurai.net (root@sasami.jurai.net [206.151.208.162]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA29642 for ; Fri, 26 Jul 1996 14:32:33 -0700 (PDT) Received: from localhost (winter@localhost) by sasami.jurai.net (8.7.5/8.7.3) with SMTP id QAA26812; Fri, 26 Jul 1996 16:31:26 -0500 (CDT) Date: Fri, 26 Jul 1996 16:31:25 -0500 (CDT) From: "Matthew N. Dodd" X-Sender: winter@sasami To: Joe Greco cc: freebsd-current@FreeBSD.ORG Subject: Re: A new twist on the reboot problems In-Reply-To: <199607262028.PAA18823@brasil.moneng.mei.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 26 Jul 1996, Joe Greco wrote: > Set up small FreeBSD box. With a large disk. And a modem. And its own > Kerberos domain, and encrypted telnet. This will allow me to log in > remotely or locally, in a secure fashion. ssh > Stick in a multiport serial card. Connected to the COM1: serial ports of > other FreeBSD machines, running comconsole. any random multiport card works. > Set up a user, "consmgr". Install "screen" and "kermit". Humm... I've been using 'root' :) but thats not such a big deal. [bit about screen deleted] > Now we are flying. I can log in from anywhere in the world, via Inet or > modem, or on console, securely, and access half a dozen other boxes' > consoles, review their console output, etc. I've got mine hooked to all of my terminal servers, my router, and my PBX. Kinda nifty. I'm probably going to try to setup serial consoles on the rest of the unix boxes... I've got tons of free serial ports on the box... Have a good one. | Matthew N.. Dodd | winter@jurai.net | http://www.jurai.net/~winter | | Technical Manager | mdodd@intersurf.net | http://www.intersurf.net | | InterSurf Online | "Welcome to the net Sir, would you like a handbasket?"| From owner-freebsd-current Fri Jul 26 14:33:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA29754 for current-outgoing; Fri, 26 Jul 1996 14:33:34 -0700 (PDT) Received: from central.picker.com (central.picker.com [144.54.31.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA29730 for ; Fri, 26 Jul 1996 14:33:25 -0700 (PDT) Received: from ct.picker.com by central.picker.com with smtp (Smail3.1.28.1 #3) id m0ujuKw-0004wvC; Fri, 26 Jul 96 17:22 EDT Received: from elmer.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1) id AA06802; Fri, 26 Jul 96 17:21:17 EDT Received: by elmer.picker.com (SMI-8.6/SMI-SVR4) id RAA19749; Fri, 26 Jul 1996 17:16:32 -0400 From: rhh@ct.picker.com (Randall Hopper) Message-Id: <199607262116.RAA19749@elmer.picker.com> Subject: Re: Linux Java compiler on FreeBSD To: current@freebsd.org Date: Fri, 26 Jul 1996 17:16:32 -0400 (EDT) Reply-To: rhh@ct.picker.com Organization: Picker International, CT Division X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Pat Caldon: >> > I tried to download the libs from slackware-3.0 but that was the same >> > version that I have (libc 5.0.9) and didn`t make any difference, is there >> > a new one that this? ... >> > ./java: can't resolve symbol '__libc_malloc' >> >> I think I picked up the ones from redhat. I had to get an up-to-date >> version of ld.so as well. > >You need version 5.2 or above I believe; 5.3.12 worked fine for me. I was getting the same undefined symbol. Folowing this thread, I picked up libc.so.5.2.18 from Redhat, and it turned that message into a bus error. Guess I'll seek out 5.3.12 and give that a whirl. I'd sure like to get that Linux appletviewer running (in the absense of a native FreeBSD version.) By the way, is there any way to do some reasonable diagnosis from core dumps from Linux ELF binaries (assuming they've got debug info, etc)? As new as ELF support is, I think I know the answer, but just in case my guess is wrong... Thanks, Randall Hopper rhh@ct.picker.com From owner-freebsd-current Fri Jul 26 14:49:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA01047 for current-outgoing; Fri, 26 Jul 1996 14:49:07 -0700 (PDT) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA01032 for ; Fri, 26 Jul 1996 14:49:04 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id OAA02428; Fri, 26 Jul 1996 14:47:43 -0700 (PDT) Received: from shrimp.whistle.com(207.76.205.74) by whistle.com via smap (V1.3) id sma002426; Fri Jul 26 14:47:31 1996 Received: (from julian@localhost) by shrimp.whistle.com (8.6.12/8.6.12) id OAA20960; Fri, 26 Jul 1996 14:47:30 -0700 From: Julian Elischer Message-Id: <199607262147.OAA20960@shrimp.whistle.com> Subject: Re: cvs commit: src/sys/dev/ccd ccd.c src/sys/dev/vn vn.c src/sys/sys conf.h src/sys/i386/isa fd.c mcd.c scd.c wcd.c wd.c wt.c s To: jgreco@brasil.moneng.mei.com (Joe Greco) Date: Fri, 26 Jul 1996 14:47:30 -0700 (PDT) Cc: phk@critter.tfs.com, wollman@lcs.mit.edu, current@FreeBSD.ORG, imp@village.org, jkh@time.cdrom.com In-Reply-To: <199607262003.PAA18767@brasil.moneng.mei.com> from "Joe Greco" at Jul 26, 96 03:03:08 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > As much as I pride myself with never agreeing with Garrett, I'm having a > > hard time finding a reason not to in this particular case. :-) > > > > There are a couple of fine points still not resolved. > > There is >still< no way to generally specify a policy: > > "Make all disks foo.bar mode 0640" > > and such. > > This is a good point. There are some of us who use things like amanda for > backups, and currently I rely on blind chance and the amanda report to > remind me when I have bad permissions on a disk. > > My personal opinion, however, is that you can make this sort of a thing > into a real problem and go to great lengths to "solve" it at ridiculous > cost in complexity. > > Let's say, for example, that you were to create a "sd.defaults" file that > specifies the default permissions for any newly created sd device. Well > that's fine for the general case, but now somebody wants a special case > for sd5, which holds a raw-partition database. It starts to get icky. The > cure is worse than the disease, IMVHO. Unless somebody has a functionally > better cure... > > I probably am not qualified to be a part of this architectural discussion > anyways so I'll butt out now :-) I'm just speaking as someone who has > gotten very tired of no, every comment is welcome! what I've started doing: mount -t devfs devfs /mnt cd .mnt find . -print |cpio -pdmuv /dev cd / umount /mnt :) > > ./MAKEDEV sd13 sd13s1 sd13s1e sd14 sd14s1 sd14s1e > > > The major/minor of the underlying nodes are of course of no significance, > > but wouldn't it be nice to get rid of all that blasted code entirely ? > > > > Why would we even care about the type of node apart from "Directory" or > > "Not Directory" ? Ie, we could mount devfs on a FS that doesn't support > > c/b devs at all (msdos, hfs ...) > > I wouldn't care :-) I think that would be a superb feature. > > ... JG > From owner-freebsd-current Fri Jul 26 15:14:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA07296 for current-outgoing; Fri, 26 Jul 1996 15:14:50 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA07264; Fri, 26 Jul 1996 15:14:41 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id XAA03317; Fri, 26 Jul 1996 23:01:20 +0200 (MET DST) To: Joe Greco cc: johang@algonet.se (Johan Granlund), freebsd-current@FreeBSD.ORG Subject: Re: A new twist on the reboot problems In-reply-to: Your message of "Fri, 26 Jul 1996 15:28:05 CDT." <199607262028.PAA18823@brasil.moneng.mei.com> Date: Fri, 26 Jul 1996 23:01:20 +0200 Message-ID: <3315.838414880@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >A small FreeBSD based console manager box would have none of these flaws :-) There is already a neat little program called "console" that will do this. Can't remember where it comes from, some US Uni. Use it for a bunch of Sun's works better than the suns :-) You can run it remotely, log to files, you name it. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Fri Jul 26 15:23:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA08232 for current-outgoing; Fri, 26 Jul 1996 15:23:55 -0700 (PDT) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA08191; Fri, 26 Jul 1996 15:23:43 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-13.slip.Uni-Koeln.DE) by Sisyphos with SMTP id AA03773 (5.67b/IDA-1.5); Sat, 27 Jul 1996 00:23:29 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.7.5/8.6.9) id AAA00256; Sat, 27 Jul 1996 00:23:26 +0200 (MET DST) Date: Sat, 27 Jul 1996 00:23:26 +0200 (MET DST) Message-Id: <199607262223.AAA00256@x14.mi.uni-koeln.de> From: Stefan Esser To: dg@root.com Subject: Re: ncr53c810 driver in stable/current Cc: current@freebsd.org, stable@freebsd.org, "Marc G. Fournier" In-Reply-To: <199607220803.BAA10665@root.com> References: <199607220803.BAA10665@root.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk David Greenman writes: > > The last time I reported this, someone made mention that > >the cause was the NCR driver not switching modes or something like > >that, so that it can't dump core...? > > > > If anyone remembers this thread, or knows what the hell I'm > >talking about...has this been fixed in -current? > > We've seen this problem on freefall (which uses the NCR controller). It > likes to hang when we try to reboot it. I don't recall any fixes for this, > and I don't know what causes it. Hmmm, it hangs when you try to reboot it ? This is more probably related to some problem with the motherboard than the SCSI controller. (Ie. the (in)famous BROKEN_KEYBOARD_RESET.) But I now know how to make the NCR write a kernel dump in case of a crash: Just leave alone the "hole" between 0xe8000 and 0xfffff ... It seems that the NCR gets some error accessing this addresses. I did not have time to completely analyse the resulting chip status, but it appears that the failed memory access (which is reported to a PCI bus-master on a PCI bus line !) causes the hang. Isn't it dangerous to touch that region from the dump code, anyway ? There might be memory mapped registers that make some device change state when read ... I will try to make the driver ignore the access error in the dump, but it might be a good idea to not include the BIOS region in the dump (???) Regards, STefan From owner-freebsd-current Fri Jul 26 15:31:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA10276 for current-outgoing; Fri, 26 Jul 1996 15:31:27 -0700 (PDT) Received: from gateway.tcsi.com (tcsi.com [137.134.47.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA10256 for ; Fri, 26 Jul 1996 15:31:21 -0700 (PDT) Received: from draco.tcs.com (draco.tcs.com [137.134.40.2]) by gateway.tcsi.com (8.7.4/8.7.3) with ESMTP id PAA29426; Fri, 26 Jul 1996 15:24:55 -0700 (PDT) Received: from cozumel.tcs.com (cozumel.tcs.com [137.134.104.12]) by draco.tcs.com (8.7.5/8.7.3) with ESMTP id PAA14504; Fri, 26 Jul 1996 15:25:24 -0700 (PDT) From: Douglas Ambrisko Received: (ambrisko@localhost) by cozumel.tcs.com (8.6.10/8.6.10) id PAA19772; Fri, 26 Jul 1996 15:25:09 -0700 Message-Id: <199607262225.PAA19772@cozumel.tcs.com> Subject: Re: A new twist on the reboot problems To: jgreco@brasil.moneng.mei.com (Joe Greco) Date: Fri, 26 Jul 1996 15:25:07 -0700 (PDT) Cc: johang@algonet.se, freebsd-current@FreeBSD.ORG In-Reply-To: <199607262028.PAA18823@brasil.moneng.mei.com> from "Joe Greco" at Jul 26, 96 03:28:05 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Joe Greco writes: | | With a little work, the box hosting consmgr could be outfitted with | reset-button outputs for the other boxes, or power controls, etc. | That would not be out-of-the-box technology (although you COULD use xtend | if you were desperate for a quick solution).. At a prior company we wired DTR on com1 to the PC reset. The circuit consisted of a diode and resister. We even hacked a header so it could be pluging in-line of the serial port and reset line so the reset and serial port were still usable. (the only side effect is that we had it connected to a DEC Alpha which toggled DTR when OSF booted ... this actually turned out to be a nice feature for the project). | UNIX: the flexibility to leverage off of an apparently unrelated set of | powerful tools to do something cool. Yep. Doug A. From owner-freebsd-current Fri Jul 26 16:42:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA14540 for current-outgoing; Fri, 26 Jul 1996 16:42:04 -0700 (PDT) Received: from chain.iafrica.com (root@chain.iafrica.com [196.31.1.66]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA14529 for ; Fri, 26 Jul 1996 16:41:56 -0700 (PDT) Received: from localhost (khetan@localhost [127.0.0.1]) by chain.iafrica.com (8.7.5/8.6.12) with SMTP id BAA06043; Sat, 27 Jul 1996 01:40:29 +0200 (SAT) Date: Sat, 27 Jul 1996 01:40:29 +0200 (SAT) From: Khetan Gajjar To: David Langford cc: current@FreeBSD.ORG Subject: Re: SCO and Wordperfect 7 problems (socksys) In-Reply-To: <199607260434.SAA00979@caliban.dihelix.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 25 Jul 1996, David Langford wrote: >I dont have any other SCO programs to try (any one know of some???) >and I dont have the WP6.0 demo- guess I can download it... weeee. xwp -e runs it in demo mode. --- Khetan Gajjar [ http://www.iafrica.com/~khetan ] UUNet Internet Africa [ 0800-030-002 & help@iafrica.com ] From owner-freebsd-current Fri Jul 26 17:33:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA18797 for current-outgoing; Fri, 26 Jul 1996 17:33:53 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA18786 for ; Fri, 26 Jul 1996 17:33:50 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id RAA23533; Fri, 26 Jul 1996 17:32:27 -0700 (PDT) Message-Id: <199607270032.RAA23533@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Poul-Henning Kamp cc: Joe Greco , wollman@lcs.mit.edu (Garrett Wollman), current@FreeBSD.ORG, imp@village.org, jkh@time.cdrom.com Subject: Re: cvs commit: src/sys/dev/ccd ccd.c src/sys/dev/vn vn.c src/sys/sys conf.h src/sys/i386/isa fd.c mcd.c scd.c wcd.c wd.c wt.c s In-reply-to: Your message of "Fri, 26 Jul 1996 21:37:22 +0200." <3119.838409842@critter.tfs.com> From: David Greenman Reply-To: dg@root.com Date: Fri, 26 Jul 1996 17:32:27 -0700 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >As much as I pride myself with never agreeing with Garrett, I'm having a >hard time finding a reason not to in this particular case. :-) > >There are a couple of fine points still not resolved. >There is >still< no way to generally specify a policy: > "Make all disks foo.bar mode 0640" >and such. > >The major/minor of the underlying nodes are of course of no significance, >but wouldn't it be nice to get rid of all that blasted code entirely ? > >Why would we even care about the type of node apart from "Directory" or >"Not Directory" ? Ie, we could mount devfs on a FS that doesn't support >c/b devs at all (msdos, hfs ...) I tend to agree with Poul's opinion...I'd really like to get rid of c/b devices entirely (in as far as they are types within the filesystem). Only devfs should know about them. Perhaps the underlying file in Garrett's suggestion can be of any type - even a regular file of 0 bytes. The new instances that he talks about being created automatically would be 0 length regular files. If we go for a model like this, I would want it to be controlled with a (devfs) mount option so that persistence can be turned on and off. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Fri Jul 26 20:26:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA04985 for current-outgoing; Fri, 26 Jul 1996 20:26:20 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA04979 for ; Fri, 26 Jul 1996 20:26:13 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id WAA02574 for current@freebsd.org; Fri, 26 Jul 1996 22:26:03 -0500 (EST) From: "John S. Dyson" Message-Id: <199607270326.WAA02574@dyson.iquest.net> Subject: libkvm/ps, etc. rebuild warning!!! To: current@freebsd.org Date: Fri, 26 Jul 1996 22:26:03 -0500 (EST) Reply-To: dyson@freebsd.org X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Next time that you sup, you'll find that you need to rebuild libkvm and ps. The size of some of the kernel data structures has changed again... Sorry, John From owner-freebsd-current Sat Jul 27 03:53:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA28994 for current-outgoing; Sat, 27 Jul 1996 03:53:04 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA28964; Sat, 27 Jul 1996 03:52:54 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id UAA08492; Sat, 27 Jul 1996 20:49:41 +1000 Date: Sat, 27 Jul 1996 20:49:41 +1000 From: Bruce Evans Message-Id: <199607271049.UAA08492@godzilla.zeta.org.au> To: cat@uunet.ca, se@ZPR.Uni-Koeln.DE Subject: Re: ncr53c810 driver in stable/current Cc: current@FreeBSD.org, dg@Root.COM, jkh@FreeBSD.org, scrappy@ki.net, stable@FreeBSD.org Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >The dump writes out the first few MB within less than a >second, and then the SCSI LED stays on and the system >hangs, always after accessing the same virtual address. >It took me some time to think about checking which physical >address that corresponds to that page, and to my surprise I >found that the BIOS region at e8000 is the last thing touched >by the NCR chip. I have no idea why the page at 0e8000 is >mapped into the kernel, and I do not think that I got some >device at that address. But it still causes the hang :( 0xe8000 is in the first MB so it's surprising that the first few MB got written. sddump() and wddump() write all pages from page #0 to page #MaxMem-1, so they always write the entire BIOS area. Perhaps they should write only RAM. phys_avail[] almost says where RAM is. Unfortunately, it is truncated at the start to skip the BIOS page and at the end to skip the message buffer. Bruce From owner-freebsd-current Sat Jul 27 04:45:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA03195 for current-outgoing; Sat, 27 Jul 1996 04:45:12 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA03181 for ; Sat, 27 Jul 1996 04:45:09 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id NAA21574; Sat, 27 Jul 1996 13:45:02 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id NAA27419; Sat, 27 Jul 1996 13:45:01 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id LAA29044; Sat, 27 Jul 1996 11:21:37 +0200 (MET DST) From: J Wunsch Message-Id: <199607270921.LAA29044@uriah.heep.sax.de> Subject: Re: bt946 problems. To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sat, 27 Jul 1996 11:21:37 +0200 (MET DST) Cc: nawaz921@cs.uidaho.edu (faried nawaz) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <21247.838405472@waldrog.cs.uidaho.edu> from faried nawaz at "Jul 26, 96 11:24:32 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As faried nawaz wrote: > Now it doesn't display the "bt: unit number.." lines, but it still > hangs after the npx lines. Btw., if you boot with `-v', you can seem some more messages after the npx line (status information about where it tries to find the root file system etc.). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sat Jul 27 04:45:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA03238 for current-outgoing; Sat, 27 Jul 1996 04:45:19 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA03197 for ; Sat, 27 Jul 1996 04:45:12 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id NAA21520; Sat, 27 Jul 1996 13:44:43 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id NAA27411; Sat, 27 Jul 1996 13:44:43 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id MAA29822; Sat, 27 Jul 1996 12:42:09 +0200 (MET DST) From: J Wunsch Message-Id: <199607271042.MAA29822@uriah.heep.sax.de> Subject: Re: Termcap problems To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sat, 27 Jul 1996 12:42:09 +0200 (MET DST) Cc: dev@fgate.flevel.co.uk (Developer) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Developer at "Jul 26, 96 09:16:17 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Developer wrote: > > Perhaps a miscalculation that only hits in some special case. I bet > > if you turn off the -F, it will look normally. > > > > You could have a look into the column number calculation, and file a > > PR once you've got a fix. :-)) > > I see - you think the bug might be in ls? The strange thing is if I put on > an old termcap from FreeBSD2.0 release I don`t get this problem. It doesn't even remotely touch TERMCAP, it's not linked against -ltermcap either. The variable `termwidth' is set in ls.c, basically the tty's window size gets precedence if output is a tty, otherwise if COLUMNS is set this one is used, otherwise it falls back to assuming 80 columns. The logic with considering COLUMNS even for non-tty's wasn't always there, it is so you can say something like: env COLUMNS=132 ls -CF | lpr -Psome-wide-printer The actual output formatting happens inside print.c. Simply run it through a debugger and have a close look at the few variables that affect formatting. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sat Jul 27 04:45:22 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA03255 for current-outgoing; Sat, 27 Jul 1996 04:45:22 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA03232 for ; Sat, 27 Jul 1996 04:45:19 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id NAA21609 for ; Sat, 27 Jul 1996 13:45:16 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id NAA27429 for freebsd-current@FreeBSD.org; Sat, 27 Jul 1996 13:45:16 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id LAA29233 for freebsd-current@FreeBSD.org; Sat, 27 Jul 1996 11:41:31 +0200 (MET DST) From: J Wunsch Message-Id: <199607270941.LAA29233@uriah.heep.sax.de> Subject: Re: cvs commit: src/sys/dev/ccd ccd.c src/sys/dev/vn vn.c src/sys/sys conf.h src/sys/i386/isa fd.c mcd.c scd.c wcd.c wd.c wt.c s To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sat, 27 Jul 1996 11:41:31 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <1430.838366976@time.cdrom.com> from "Jordan K. Hubbard" at "Jul 26, 96 00:42:56 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Jordan K. Hubbard wrote: > It would also allow you to make links, like: > > ln -s /dev/cuaa0 /dev/mouse > > Which get recreated automagically when devfs is next mounted. Yes, That's what i wrote as being ``logical device names''. However, there's still the problem that your /dev/mouse might point to nowhereland if your sio0 failed probing at this kernel boot. It would normally be better to not have /dev/mouse in this case either. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sat Jul 27 04:45:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA03331 for current-outgoing; Sat, 27 Jul 1996 04:45:34 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA03299 for ; Sat, 27 Jul 1996 04:45:29 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id NAA21605 for ; Sat, 27 Jul 1996 13:45:15 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id NAA27428 for freebsd-current@FreeBSD.org; Sat, 27 Jul 1996 13:45:14 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id LAA29208 for freebsd-current@FreeBSD.org; Sat, 27 Jul 1996 11:38:55 +0200 (MET DST) From: J Wunsch Message-Id: <199607270938.LAA29208@uriah.heep.sax.de> Subject: Re: cvs commit: src/sys/dev/ccd ccd.c src/sys/dev/vn vn.c src/sys/sys conf.h src/sys/i386/isa fd.c mcd.c scd.c wcd.c wd.c wt.c s To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sat, 27 Jul 1996 11:38:55 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199607252015.NAA28229@freefall.freebsd.org> from "Justin T. Gibbs" at "Jul 25, 96 01:15:32 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Justin T. Gibbs wrote: > >What sense does it make using /dev entries to unconfigured drivers > >(that's about all persistance would give you, isn't it :)? > > Persistence would allow you to change the permissions on a device and > have them stick. If a device was not availible, it wouldn't show up > in /dev, but if it came back (say after replacing faulty hardware) > any permission changes you made in the past would show up as soon as > the device did. That sounds reasonable. The mere question is whether you want an `automatic' persistance, or rather prefer sort of a knob you can turn in order to say ``record permissions right now''. The latter is rather easy to accomplish by recording them in say /etc/rc.devices, and run this script before going multi-user. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sat Jul 27 04:46:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA03478 for current-outgoing; Sat, 27 Jul 1996 04:46:43 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA03468 for ; Sat, 27 Jul 1996 04:46:39 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id NAA21532; Sat, 27 Jul 1996 13:44:48 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id NAA27413; Sat, 27 Jul 1996 13:44:47 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id NAA00538; Sat, 27 Jul 1996 13:29:43 +0200 (MET DST) From: J Wunsch Message-Id: <199607271129.NAA00538@uriah.heep.sax.de> Subject: Re: Adding a second scsi drive To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sat, 27 Jul 1996 13:29:43 +0200 (MET DST) Cc: ernie@spooky.eis.net.au (Ernie Elu) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199607261236.WAA06937@spooky.eis.net.au> from Ernie Elu at "Jul 26, 96 10:36:24 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Ernie Elu wrote: > Can someone one email me a set of instructions on how to add a second scsi > drive with -current without using sysinstall? I mailed my procedure a dozen times: disklabel -Brw sd1 auto disklabel -e sd1 # edit partitions for filesys in `get file system partitions of sd1` do newfs -d0 /dev/rsd1${filesys} done vi /etc/fstab This creates ``dangerously dedicated'' drives (thus no `fdisk' required), as long as this is fine with you, the above is perhaps the easiest way. > Sysinstall still core dumps when I try and usr it to partition and and > disklabel the second drive. Analyze it, and tell Jordan about the actual problem. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sat Jul 27 04:54:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA03734 for current-outgoing; Sat, 27 Jul 1996 04:54:40 -0700 (PDT) Received: from dworshak.cs.uidaho.edu (dworshak.cs.uidaho.edu [129.101.100.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA03728 for ; Sat, 27 Jul 1996 04:54:38 -0700 (PDT) Received: from waldrog.cs.uidaho.edu (waldrog.cs.uidaho.edu [129.101.100.23]) by dworshak.cs.uidaho.edu (8.7.5/1.1) with ESMTP id EAA26726; Sat, 27 Jul 1996 04:53:33 -0700 (PDT) From: faried nawaz Received: (nawaz921@localhost) by waldrog.cs.uidaho.edu (8.7.5/1.0) id EAA21729; Sat, 27 Jul 1996 04:53:32 -0700 (PDT) Date: Sat, 27 Jul 1996 04:53:32 -0700 (PDT) Message-Id: <199607271153.EAA21729@waldrog.cs.uidaho.edu> To: joerg_wunsch@uriah.heep.sax.de Subject: Re: bt946 problems. Cc: current@freebsd.org, nawaz921@cs.uidaho.edu Mime-Version: 1.0 Content-Type: text/plain; charset=X-roman8 Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk J"org writes... > Btw., if you boot with `-v', you can seem some more messages after the > npx line (status information about where it tries to find the root > file system etc.). I apparently never reach that point when I use the Buslogic; I do see that when I use other controllers (aha2940w, etc) and on all other -current machines I have access to. faried. From owner-freebsd-current Sat Jul 27 05:38:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA05518 for current-outgoing; Sat, 27 Jul 1996 05:38:53 -0700 (PDT) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA05497; Sat, 27 Jul 1996 05:38:47 -0700 (PDT) Received: by Sisyphos id AA14447 (5.67b/IDA-1.5); Sat, 27 Jul 1996 14:36:45 +0200 Message-Id: <199607271236.AA14447@Sisyphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Sat, 27 Jul 1996 14:36:44 +0200 In-Reply-To: Bruce Evans "Re: ncr53c810 driver in stable/current" (Jul 27, 20:49) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: Bruce Evans Subject: Re: ncr53c810 driver in stable/current Cc: current@freebsd.org, stable@freebsd.org, scrappy@ki.net Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Jul 27, 20:49, Bruce Evans wrote: } Subject: Re: ncr53c810 driver in stable/current } >The dump writes out the first few MB within less than a } >second, and then the SCSI LED stays on and the system } >hangs, always after accessing the same virtual address. } } >It took me some time to think about checking which physical } >address that corresponds to that page, and to my surprise I } >found that the BIOS region at e8000 is the last thing touched } >by the NCR chip. I have no idea why the page at 0e8000 is } >mapped into the kernel, and I do not think that I got some } >device at that address. But it still causes the hang :( } } 0xe8000 is in the first MB so it's surprising that the first } few MB got written. Yes, sure, you are of course right! I wrote the message whiledoing the tests, and in fact had estimated that 2MB had been written at the time of the hand, when it in fact was a little less than 1MB ... } sddump() and wddump() write all pages from page #0 to page } #MaxMem-1, so they always write the entire BIOS area. Perhaps } they should write only RAM. phys_avail[] almost says where } RAM is. Unfortunately, it is truncated at the start to skip } the BIOS page and at the end to skip the message buffer. I'm not sure about the right way to deal with that region. There might be interesting data in some devices buffer (e.g. of an ISA ethernet card) that should go into the dump. PCI is different from ISA in that each transfer has to be acknowledged. But the ISA memory hole is subtractively decoded: If no PCI chip signals a "DEVSEL" (some device is selected) state within a few PCI bus clocks, then the PCI to ISA bridge will forward the request to the ISA bus. The NCR won't actually know whether the address was decoded on ISA, so I'm again not sure why the system hangs when the NCR tries to read from that address. I will add a few more micro-tests to find out what actually causes the hang. As a work around to those people in need to have kernel dumps written to disk on a NCR system: Is it worth the effort to detect the special situation and have the driver ignore the memory hole in the dump ? If all you want is to have the system come up automatically after crash, then you might as well just turn off the kernel dump feature (using the dumpon command or by not having a "sump on sd0" in the kernel config file ...) Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se From owner-freebsd-current Sat Jul 27 06:01:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA06419 for current-outgoing; Sat, 27 Jul 1996 06:01:29 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA06364; Sat, 27 Jul 1996 06:01:07 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id WAA11898; Sat, 27 Jul 1996 22:58:24 +1000 Date: Sat, 27 Jul 1996 22:58:24 +1000 From: Bruce Evans Message-Id: <199607271258.WAA11898@godzilla.zeta.org.au> To: bde@zeta.org.au, se@zpr.uni-koeln.de Subject: Re: ncr53c810 driver in stable/current Cc: current@FreeBSD.org, scrappy@ki.net, stable@FreeBSD.org Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >As a work around to those people in need to have >kernel dumps written to disk on a NCR system: Is >it worth the effort to detect the special situation >and have the driver ignore the memory hole in the >dump ? It would have to fill the hole(s) with nulls or something for compatibility (savecore and gdb don't understand holes). To handle this machine-independently, xddump() should probably write a memory map and not dump the holes; then savecore should fill the holes with null blocks. Otherwise /dev/mem would take more than 2^64 bytes of memory to map on 64-bit systems with physical memory at high addresses. Bruce From owner-freebsd-current Sat Jul 27 08:31:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA13991 for current-outgoing; Sat, 27 Jul 1996 08:31:19 -0700 (PDT) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA13969 for ; Sat, 27 Jul 1996 08:31:13 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.7.5/8.6.9) with SMTP id QAA17989 for ; Sat, 27 Jul 1996 16:32:28 +0100 (BST) Date: Sat, 27 Jul 1996 16:32:27 +0100 (BST) From: Developer To: freebsd-current@freebsd.org Subject: Problem with Sup Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I keep getting this error in my sup log - from sup.freebsd.org:- SUP Updating file distfiles/xdvi/xdvi-20.tar.Z SUP Updating file distfiles/xdvi/xdvi-pl17+markpage+toc+printdvi.patch.gz SUP Updating file distfiles/xdvi/xdvi.tar.Z SUP Updating file distfiles/xdvik-18f.tar.gz SUP Updating file distfiles/xearth-1.0.tar.gz SUP: SCM GOAWAY We died trying to "gzip -c < distfiles/xemacs-19.14.tar.gz > /var/tmp/tmp.0.015956 " SUP: Premature EOF on network input SUP: Error receiving file from file server SUP: Upgrade of ports-distfiles-current aborted at Jul 27 01:18:18 1996 SUP: Aborted Any ideas what might be wrong? Regards, Trefor S. From owner-freebsd-current Sat Jul 27 11:25:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA23856 for current-outgoing; Sat, 27 Jul 1996 11:25:20 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA23851 for ; Sat, 27 Jul 1996 11:25:19 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id LAA25827; Sat, 27 Jul 1996 11:23:48 -0700 (PDT) To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-current@FreeBSD.ORG (FreeBSD-current users), ernie@spooky.eis.net.au (Ernie Elu) Subject: Re: Adding a second scsi drive In-reply-to: Your message of "Sat, 27 Jul 1996 13:29:43 +0200." <199607271129.NAA00538@uriah.heep.sax.de> Date: Sat, 27 Jul 1996 11:23:48 -0700 Message-ID: <25825.838491828@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Sysinstall still core dumps when I try and usr it to partition and and > > disklabel the second drive. > > Analyze it, and tell Jordan about the actual problem. I'll also get to this sooner or later, it's just down on my TODO list (trying to get the Doc CD finished right now). Jordan From owner-freebsd-current Sat Jul 27 14:51:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA06155 for current-outgoing; Sat, 27 Jul 1996 14:51:24 -0700 (PDT) Received: from sed.cs.fsu.edu (sed.cs.fsu.edu [128.186.121.157]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA06148 for ; Sat, 27 Jul 1996 14:51:19 -0700 (PDT) Received: by sed.cs.fsu.edu (8.6.9/56) id RAA17879; Sat, 27 Jul 1996 17:51:17 -0400 From: Gang-Ryung Uh Message-Id: <199607272151.RAA17879@sed.cs.fsu.edu> Subject: make world To: freebsd-current@FreeBSD.org Date: Sat, 27 Jul 1996 17:51:16 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi, I have supped Jul27 1996 current src, and try to "make world" I got following fatal error. Would you tell me what I am missing? Thanks in advance. ================= -------------------------------------------------------------- Cleaning up the source tree, and rebuilding the obj tree -------------------------------------------------------------- cd /usr/src && make cleandir ===> include usage: rm [-f | -i] [-dPRr] file ... *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 ============================== Gang-Ryung Uh (uh@cs.fsu.edu) From owner-freebsd-current Sat Jul 27 16:02:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA10818 for current-outgoing; Sat, 27 Jul 1996 16:02:36 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA10795; Sat, 27 Jul 1996 16:02:32 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id QAA23177; Sat, 27 Jul 1996 16:02:25 -0700 (PDT) To: dyson@freebsd.org cc: current@freebsd.org Subject: New wierdness since latest VM kernel. Date: Sat, 27 Jul 1996 16:02:24 -0700 Message-ID: <23173.838508544@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk A make world now falls over randomly, though always with a shell script spontaneously deciding that it's not happy with life, like so: chroot-> make sgmlfmt -f html /usr/src/share/doc/handbook/handbook.sgml /usr/bin/sgmlfmt: 30: Syntax error: "{" unexpected (expecting "then") *** Error code 2 Stop. chroot-> make sgmlfmt -f html /usr/src/share/doc/handbook/handbook.sgml generating handbook.html... The second time it succeeds, for no discernable reason, and may fail again later. Any ideas? Jordan From owner-freebsd-current Sat Jul 27 18:57:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA18244 for current-outgoing; Sat, 27 Jul 1996 18:57:29 -0700 (PDT) Received: from Fieber-John.campusview.indiana.edu (Fieber-John.campusview.indiana.edu [149.159.1.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA18239; Sat, 27 Jul 1996 18:57:27 -0700 (PDT) Received: from localhost (jfieber@localhost) by Fieber-John.campusview.indiana.edu (8.7.5/8.7.3) with SMTP id UAA02097; Sat, 27 Jul 1996 20:57:22 -0500 (EST) X-Authentication-Warning: Fieber-John.campusview.indiana.edu: jfieber owned process doing -bs Date: Sat, 27 Jul 1996 20:57:22 -0500 (EST) From: John Fieber X-Sender: jfieber@Fieber-John.campusview.indiana.edu To: "Jordan K. Hubbard" cc: dyson@FreeBSD.org, current@FreeBSD.org Subject: Re: New wierdness since latest VM kernel. In-Reply-To: <23173.838508544@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 27 Jul 1996, Jordan K. Hubbard wrote: > A make world now falls over randomly, though always with a shell script > spontaneously deciding that it's not happy with life, like so: > > chroot-> make > sgmlfmt -f html /usr/src/share/doc/handbook/handbook.sgml > /usr/bin/sgmlfmt: 30: Syntax error: "{" unexpected (expecting "then") > *** Error code 2 Actully, that would be perl, if it makes any difference. -john == jfieber@indiana.edu =========================================== == http://fallout.campusview.indiana.edu/~jfieber ================ From owner-freebsd-current Sat Jul 27 23:51:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA02434 for current-outgoing; Sat, 27 Jul 1996 23:51:37 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA02412 for ; Sat, 27 Jul 1996 23:51:34 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id IAA11463; Sun, 28 Jul 1996 08:51:28 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA11968; Sun, 28 Jul 1996 08:51:28 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id IAA06999; Sun, 28 Jul 1996 08:47:00 +0200 (MET DST) From: J Wunsch Message-Id: <199607280647.IAA06999@uriah.heep.sax.de> Subject: Re: make world To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 28 Jul 1996 08:47:00 +0200 (MET DST) Cc: uh@sed.cs.fsu.edu (Gang-Ryung Uh) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199607272151.RAA17879@sed.cs.fsu.edu> from Gang-Ryung Uh at "Jul 27, 96 05:51:16 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Gang-Ryung Uh wrote: > I have supped Jul27 1996 current src, and try to "make world" > I got following fatal error. Would you tell me what I am missing? > cd /usr/src && make cleandir > ===> include > usage: rm [-f | -i] [-dPRr] file ... > *** Error code 1 Search for this error in the mailing list archive, this has already been discussed here. I mostly forgot the reason, except that it was an attempt to `remove nothing'. I think if you are running ``make -i cleandir'', you should be able to bootstrap. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)