From owner-freebsd-hackers Sun Jan 22 02:12:39 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id CAA01758 for hackers-outgoing; Sun, 22 Jan 1995 02:12:39 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id CAA01752 for ; Sun, 22 Jan 1995 02:12:27 -0800 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id CAA22016; Sun, 22 Jan 1995 02:12:07 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.9/8.6.5) with SMTP id CAA00270; Sun, 22 Jan 1995 02:12:07 -0800 Message-Id: <199501221012.CAA00270@corbin.Root.COM> X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol To: Andras Olah cc: hackers@FreeBSD.org Subject: Re: Netinet internals (Was: Patching a running kernel) In-reply-to: Your message of "Wed, 18 Jan 95 14:54:22 +0100." <3909.790437262@utis156.cs.utwente.nl> From: David Greenman Reply-To: davidg@Root.COM Date: Sun, 22 Jan 1995 02:12:05 -0800 Sender: hackers-owner@FreeBSD.org Precedence: bulk >> These are obviously both bugs. I didn't notice the echo and the ack >> occuring seperately when I analyzed the packet stream after making the >> change...so this is a surprise to me. On the other hand, now that you mention >> it, it does appear that this is what the code is actually going to do. Hmmm. >> The second is an oversight and it should certainly account for any options that >> may reduce the length - provided that the sender takes this into account when >> deciding whether or not to send. The problem that was originally 'solved' by >> these changes was one where interactive usage over ether or other high speed >> network connection was 'choppy' because of the 200ms delays inserted into echo >> and other short packets (vi was especially bad). > >IMO, these changes (setting ACKNOW if segment is shorter than MSS) >aren't necessary because the echo packets aren't delayed for 200ms. >I've compiled out the code in question and hitting a single >character generates the following traffic: > >09:30:05.610948 localhost.1025 > localhost.telnet: P 1:2(1) ack 2 win 16384 [tos 0x10] >09:30:05.613837 localhost.telnet > localhost.1025: P 2:3(1) ack 2 win 16384 [tos 0x10] >09:30:05.770186 localhost.1025 > localhost.telnet: . ack 3 win 16384 [tos 0x10] > >The first packet carries the character, the second acks it and >carries the echo and the third acks the echo. Only the ack of the >echo is triggered by the delack timer which is normal, but that >doesn't affect the responsiveness of vi (or anything else). The >following fragment from tcp_output assures that the echo isn't >delayed: Only for the first character. If you type faster than 5 chars/sec the situation changes. This can easily happen if you start using keys that generate multiple bytes (like arrow keys). > > if ((idle || tp->t_flags & TF_NODELAY) && > len + off >= so->so_snd.sb_cc) > goto send; > >Therefore, I'd suggest that we change our tcp_input back to the >original 4.4 version with respect to delayed acks. The problem shows itself when using tcsh and some other shells that handle prompts (output) and input in special ways. The prompt is output in multiple short packets. The first packet is short (4 bytes in my case) and subsequant packets make up the rest of the prompt. The result is that, after the first short packet, the receiver wouldn't (normally) ack it and this results in the sender not sending the rest until fastimeout occurs - about 200ms later. Similar situations like this occur at other times, especially while editing. I personally find the choppiness over ethernet annoying. Choppiness aside, this also fixes another problem where some 4.3BSD based hosts would often send less than the expected mss during a normal bulk transfer on an idle network. The short packet would be randomly mixed in the data stream - probably because of bugs in the socket->tcp buffer transition. This happens often enough to cause *serious* performance penalties. In the worst case, I've seen transfer rates that should have been 800-900k/sec get reduced to a slow crawl of 20k/sec. If you're a slow typer, you may never notice these problems. :-) I really don't much like the Nagel algorithm. I think something that is more adaptive to different latency situations is needed. We know the average latency and should take advantage of this. On another related topic, I think the 'fast' timeout handling is bogus. The actual delay varies between 0-200ms. I suppose that this is done for 'performance', but having a single [200ms] timeout to transmit all queued DELACK packets seems wrong to me. I don't know how this affects performance on a typical LAN, but all the effects I've imagined aren't good (I'm imagining cases where a few dozen TCP connections are active - large bursts of short ACK packets become the norm). >> Indeed, rfc1122 does say "SHOULD"...which makes this behavior not required. >> The problem with acking this often is that on high speed, half-duplex networks >> like ethernet, the collision rate caused by acks this frequently can consume a >> large amount of the banwidth (measured 10-20%). > >That's an interesting point, I'll check it out. I'd appreciate if >you have traces or other descriptions of such behavior. When my workload lightens a bit, I may be able to due some experiments with the old code and provide some packet traces. I may also have some old email around detailing the problem that I could send you...I'll look around. The easy way to see the effects of this problem is via a simple netstat -i and look at the total collisions before and after a bulk transfer. ...and of course it also shows itself in the raw performance numbers. >The reason I think delayed acks for more than two segments may be a >problem is that it may adversely affect the congestion control >algorithms. Slow start increases cwnd by maxseg for each ack in the >exponential phase, thus less frequent acks result in slower >slow-start. There's something about it in a paper of Lawrence >Brakmo (ftp.cs.arizona.edu:xkernel/Papers/tcp_problems.ps). I'll >try to make some tests to see exactly what goes on. That's an interesting point. The future way of the world seems to be in the direction of full duplex communications [in LANs], so perhaps the problems with 802.3 ethernet shouldn't be optimized for. On the other hand, the requirements of LANs are usually quite different than long haul networks; perhaps there is a sort of compromise that can be acheived. I should say that I don't consider myself a TCP expert. I know enough to get into trouble, but not enough to fully understand the ramifications. Sorry for the delay in responding; I was at Usenix and having a lot of trouble replying to email remotely due to some recently introduced kernel bugs. -DG From owner-freebsd-hackers Sun Jan 22 02:41:54 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id CAA02031 for hackers-outgoing; Sun, 22 Jan 1995 02:41:54 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id CAA02025 for ; Sun, 22 Jan 1995 02:41:48 -0800 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id CAA22057; Sun, 22 Jan 1995 02:41:32 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.9/8.6.5) with SMTP id CAA00334; Sun, 22 Jan 1995 02:41:32 -0800 Message-Id: <199501221041.CAA00334@corbin.Root.COM> X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol To: Robert Michael Gorichanaz cc: hackers@FreeBSD.org Subject: Re: NE2100 questions In-reply-to: Your message of "Sat, 21 Jan 95 17:30:48 CST." <199501212330.RAA16045@alpha2.csd.uwm.edu> From: David Greenman Reply-To: davidg@Root.COM Date: Sun, 22 Jan 1995 02:41:31 -0800 Sender: hackers-owner@FreeBSD.org Precedence: bulk > >I'm not sure if my last post got mangled, so.... > > >I'm trying to get my FreeBSD box to recognize a Novel NE2100 ethernet card >(its the 16bit busmaster). I've tried the ed and ep drivers, with just about >every combination of irq/port/iomem I can think of, but cannot get these >cards to be seen by the operating system on boot-up. > >Are they even supported? I know the NE2000 is, but what about the 2100's? >Am I just doing something wrong? I believe that the NE2100 is supported in both the 'lnc' and 'is' drivers. -DG From owner-freebsd-hackers Sun Jan 22 03:21:54 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id DAA02380 for hackers-outgoing; Sun, 22 Jan 1995 03:21:54 -0800 Received: from duality.gnu.ai.mit.edu (!@#$%^&*!@#$%^&*!@#$%^&*!@#$%^&*!@#$%^&*!@#$%^&*!@#$%^&*!@#$%^&*!@#$%^&*!@#$@duality.gnu.ai.mit.edu [18.43.0.236]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id DAA02374 for ; Sun, 22 Jan 1995 03:21:47 -0800 Received: (from mycroft@localhost) by duality.gnu.ai.mit.edu (8.6.9/8.6.9) id GAA28543; Sun, 22 Jan 1995 06:21:25 -0500 Date: Sun, 22 Jan 1995 06:21:25 -0500 Message-Id: <199501221121.GAA28543@duality.gnu.ai.mit.edu> From: "Charles M. Hannum" To: davidg@Root.COM CC: olah@cs.utwente.nl, hackers@FreeBSD.org In-reply-to: <199501221012.CAA00270@corbin.Root.COM> (message from David Greenman on Sun, 22 Jan 1995 02:12:05 -0800) Subject: Re: Netinet internals (Was: Patching a running kernel) Sender: hackers-owner@FreeBSD.org Precedence: bulk Choppiness aside, this also fixes another problem where some 4.3BSD based hosts would often send less than the expected mss during a normal bulk transfer on an idle network. This can happen if you fill up the socket buffer before outputting a full window, since the receiver will wait until either a delayed ack timeout or a full window is received before acking. This usually happens with Berkeley TCP because for `performance reasons' the socket buffer is not aggressively compressed; nonetheless it is a more generic problem, and caused a factor of nearly 100 slowdown in one particular application I was looking at that opens a TCP connection to the local machine. I solved this (in NetBSD) by having the receiver always ack immediately if the incoming packet has the PUSH bit set. In the worst cases, there is either no change (if the PUSH bit is never set), or delayed ack is effectively disabled (if the PUSH bit is always set). In a slightly better implementation of TCP, the application would be able to request a push. In Berkeley TCP, the PUSH bit is set by the TCP stack automatically for the last piece of data in the buffer. Most implementations I've seen use the bit in this latter fashion. For compatibility reasons, all senders must set the PUSH bit about as often as Berkeley TCP (whether automatic or by request of the user), so the `worst case' of `no change' never happens. For the case of an honestly requested push, acking immediately is clearly the correct thing to do, since the sender would like to know as soon as possible that the data has actually been received. For the Berkeley TCP case, it turns out to solve the previous problem, and cause no additional network usage for bulk data transfers. I'm not aware of any problems created by this solution. (BTW, I also posted about this to comp.protocols.tcp-ip, though I only received one reply, on a somewhat different subject.) From owner-freebsd-hackers Sun Jan 22 04:09:45 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id EAA03395 for hackers-outgoing; Sun, 22 Jan 1995 04:09:45 -0800 Received: from expo.x.org (expo.x.org [198.112.45.11]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id EAA03385 for ; Sun, 22 Jan 1995 04:09:43 -0800 Received: from fedora.x.org by expo.x.org id AA24872; Sun, 22 Jan 95 06:35:07 -0500 Received: by fedora.x.org id AA18290; Sun, 22 Jan 1995 06:35:07 -0500 Message-Id: <9501221135.AA18290@fedora.x.org> To: hackers@freefall.cdrom.com Subject: new *BSD newsgroups Date: Sun, 22 Jan 1995 06:35:06 EST From: Kaleb Keithley Sender: hackers-owner@FreeBSD.org Precedence: bulk In case you're wondering what happened with the comp.unix.bsd reorg, here's a little status update. The RFD was posted on the 23rd of November. The "discussion period" ran a little longer than the typical 30 days because of the holidays. On January 4th I asked Ron Dippold of the Usenet Volunteer Votetakers (UVV) to conduct the vote. Then Ron's mail feed went down and I didn't hear from him again for two weeks. Things are coming together finally and the CFV has been submitted to the queue of things to be posted to news.announce.newgroups. Watch for it. For those of you who don't normally follow Usenet news I'll post again when I see it at my site. -- Kaleb KEITHLEY From owner-freebsd-hackers Sun Jan 22 06:18:30 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id GAA05593 for hackers-outgoing; Sun, 22 Jan 1995 06:18:30 -0800 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id GAA05587 for ; Sun, 22 Jan 1995 06:18:27 -0800 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id WAA00260; Sat, 21 Jan 1995 22:49:10 -0500 From: Peter Dufault Message-Id: <199501220349.WAA00260@hda.com> Subject: Re: 2.0R cpio flop problem To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Sat, 21 Jan 1995 22:49:09 -0500 (EST) Cc: FreeBSD-hackers@FreeBSD.org In-Reply-To: <199501212119.WAA00143@yedi.iaf.nl> from "Wilko Bulte" at Jan 21, 95 10:19:08 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 711 Sender: hackers-owner@FreeBSD.org Precedence: bulk Wilko Bulte writes: > Maybe I didn't pay attention or so, and missed something... > > Problem: hard errors while unpacking cpio flop on 2.0R install. All > stuff comes from the 2.0 CDrom. Tried various floppys, floppies are > perfectly readable on my main machine, but give trouble when installing > them on the testbox. There are floppy driver problems on 2.0R. A new driver fixes them. I don't know if new install floppies have been built with the new driver. Peter -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 -- Formerly hd@world.std.com. E-mail problems? Tell hdslip@iii.net From owner-freebsd-hackers Sun Jan 22 08:26:27 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id IAA07082 for hackers-outgoing; Sun, 22 Jan 1995 08:26:27 -0800 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id IAA07075 for ; Sun, 22 Jan 1995 08:26:20 -0800 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.8/jtpda-5.0) with SMTP id RAA24104 for ; Sun, 22 Jan 1995 17:27:14 +0100 Received: by blaise.ibp.fr (4.1/SMI-4.1) id AA04441; Sun, 22 Jan 95 17:27:13 +0100 Received: (from roberto@localhost) by keltia.frmug.fr.net (8.6.9/keltia-uucp-1.21) id RAA00782 for freebsd-hackers@FreeBSD.ORG; Sun, 22 Jan 1995 17:22:33 +0100 From: Ollivier Robert Message-Id: <199501221622.RAA00782@keltia.frmug.fr.net> Subject: CVS tree problem with tcpdump To: freebsd-hackers@FreeBSD.org (FreeBSD Hackers' list) Date: Sun, 22 Jan 1995 17:22:32 +0100 (MET) Reply-To: roberto@blaise.ibp.fr (Ollivier Robert) X-Operating-System: FreeBSD 2.1.0-Development ctm#295 X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1612 Sender: hackers-owner@FreeBSD.org Precedence: bulk I think something has not been done when tcpdump was imported : The log shows this 8 conflicts created by this import. Use the following command to help the merge: cvs checkout -jtcpdump:yesterday -jtcpdump src/usr.sbin/tcpdump/tcpdump and I don't see any "merge" log entry. Some thing interesting is that a few files should have a tcpdump3_0 tag for version 1.1.1.2 and the 1.1.1.2 revision is not the the ,v file... Take VERSION,v : ------------------------------------------------------------ head 1.1; branch 1.1.1; access; symbols tcpdump3_0:1.1.1.2 <<<< TAG for 1.1.1.2 tcpdump:1.1.1 RELEASE_2_0:1.1.1.1 BETA_2_0:1.1.1.1 ALPHA_2_0:1.1.1.1.0.4 MOVED_NEWCVS:1.1.1.1 FINAL_1_1_5:1.1.1.1 ALPHA_1_1_5:1.1.1.1 FINAL_1_1:1.1.1.1 GAMMA_1_1:1.1.1.1 BETA_1_1:1.1.1.1.0.2 BP_BETA_1_1:1.1.1.1 FINAL_1_0:1.1.1.1 EPSILON_1_0:1.1.1.1 GAMMA_1_0:1.1.1.1 BETA_1_0:1.1.1.1 ALPHA_1_0:1.1.1.1 V_0_1_2_4:1.1.1.1 V_0_1_2_4:1.1.1; locks; strict; comment @# @; 1.1 date 93.06.12.14.42.13; author rgrimes; state Exp; branches 1.1.1.1; next ; 1.1.1.1 date 93.06.12.14.42.14; author rgrimes; state Exp; branches; next ; desc @@ 1.1 log @Initial revision @ text ------------------------------------------------------------ and there is no 1.1.1.2 revision. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia 2.1.0-Development #9: Tue Jan 17 21:12:14 MET 1995 From owner-freebsd-hackers Sun Jan 22 09:05:55 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id JAA07881 for hackers-outgoing; Sun, 22 Jan 1995 09:05:55 -0800 Received: from sovcom.kiae.su (sovcom.kiae.su [144.206.136.1]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id JAA07875 for ; Sun, 22 Jan 1995 09:05:52 -0800 Received: by sovcom.kiae.su id AA11121 (5.65.kiae-2 ); Sun, 22 Jan 1995 19:57:50 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Sun, 22 Jan 95 19:57:49 +0300 Received: (from ache@localhost) by astral.msk.su (8.6.8/8.6.6) id UAA00222; Fri, 20 Jan 1995 20:54:27 +0300 To: hackers@FreeBSD.org, Luigi Rizzo Cc: Bruce Evans References: <199501201526.QAA07101@labinfo.iet.unipi.it> In-Reply-To: <199501201526.QAA07101@labinfo.iet.unipi.it>; from Luigi Rizzo at Fri, 20 Jan 1995 16:26:25 +0100 (MET) Message-Id: Organization: Olahm Ha-Yetzirah Date: Fri, 20 Jan 1995 20:54:27 +0300 X-Mailer: Mail/@ [v2.31 FreeBSD] From: "Andrew A. Chernov, Black Mage" X-Class: Fast Subject: Re: sio.c... Lines: 65 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 2596 Sender: hackers-owner@FreeBSD.org Precedence: bulk In message <199501201526.QAA07101@labinfo.iet.unipi.it> Luigi Rizzo writes: > timeout(wakeup, TSA_OCOMPLETE(tp), 60 * hz); > (*linesw[tp->t_line].l_close)(tp, flag); > untimeout(wakeup, TSA_OCOMPLETE(tp)); >while 1.1.5R has only the call to l_close. Would it be possible to add >the calls to timeout/untimeout on 1.1.5, or there are other changes >needed ? >[I know there are comments which say that the solution is far from >being optimal; however, it would at least save me rebooting the system >every time!] There is more optimal solution for this in -current now, you can specify ttywait() timeout in seconds by 'comcontrol drainwait 180 ...' Diffs are not 2.x unique and can be applied to 1.x too (don't ask me about sending them, you can found them into CVS tree). >--- second question--- >On the same 1.1.5 system here, I found out that a process here keeps >blocking with WCHAN="siotx" (this happens with mgetty, when a >particolar user drops the session, probably not in the most >appropriate way). "siotx" seems to be present only in sio.c, function >comparam(tp, t), in the following section of code, which is exactly the >same as in 2.0R (I have no current sources handy): > disable_intr(); >retry: > com->state &= ~CS_TTGO; > enable_intr(); > while ((inb(com->line_status_port) & (LSR_TSRE | LSR_TXRDY)) > != (LSR_TSRE | LSR_TXRDY)) { > error = ttysleep(tp, TSA_OCOMPLETE(tp), TTIPRI | PCATCH, > "siotx", hz / 100); > if (error != 0 && error != EAGAIN) { > if (!(tp->t_state & TS_TTSTOP)) { > disable_intr(); > com->state |= CS_TTGO; > enable_intr(); > } > splx(s); > return (error); > } > } >from which it appears that there is no timeout or other way out in case >the modem is not responding properly. Wouldn't it be better to add an >emergemcy exit after a proper timeout ? For Bruce: Hows about applly t_timeout here too? I mean change while() to for (i = tp->t_timeout; i >= 0; i -= hz/100;) And we need to think, where we need to go after timeout occurse... -- Andrew A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - FidoNet: 2:5020/230.3 : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-hackers Sun Jan 22 09:43:34 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id JAA08211 for hackers-outgoing; Sun, 22 Jan 1995 09:43:34 -0800 Received: from dataplex.net (SHARK.DATAPLEX.NET [199.183.109.241]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id JAA08205 for ; Sun, 22 Jan 1995 09:43:30 -0800 Received: from [199.183.109.242] by dataplex.net with SMTP (MailShare 1.0b8); Sun, 22 Jan 1995 11:43:15 -0600 X-Sender: wacky@mail.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 22 Jan 1995 11:43:16 -0600 To: freebsd-hackers@FreeBSD.org (FreeBSD Hackers' list) From: rkw@dataplex.net (Richard Wackerbarth) Subject: Which libraries? Sender: hackers-owner@FreeBSD.org Precedence: bulk In trying to fix some problems in wu-ftpd, I ran into the fnmatch incompatabilities. They are straight-forward to fix. But in looking into them, I found that there are 4 different versions of fnmatch.c in the -current tree. Is there some reason that we are not using the libc version in each case? And as for that, the version in libc is missing some of the options. Is there some reason that our libc is not the glibc? From owner-freebsd-hackers Sun Jan 22 12:54:28 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id MAA12134 for hackers-outgoing; Sun, 22 Jan 1995 12:54:28 -0800 Received: from campino.informatik.rwth-aachen.de (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id MAA12128 for ; Sun, 22 Jan 1995 12:54:24 -0800 Received: from gilberto.physik.rwth-aachen.de by campino.informatik.rwth-aachen.de (4.1/campino-6) id AA20711; Sun, 22 Jan 95 21:54:10 +0100 Received: by gilberto.physik.rwth-aachen.de (XAA21301); Sun, 22 Jan 1995 23:00:31 +0100 Date: Sun, 22 Jan 1995 23:00:31 +0100 From: "Christoph P. Kukulies" Message-Id: <199501222200.XAA21301@gilberto.physik.rwth-aachen.de> To: freebsd-hackers@freefall.cdrom.com Subject: 2.0-snap install wd0 on a PCI/I-486SP3G Sender: hackers-owner@FreeBSD.org Precedence: bulk Since I was having problems with the ncr53c810 driver - BTW I read in the port-i386 NetBSD list that they were seeing problems as well and it looks that the drivers are the same forgery - I installed on an IDE drive attached to the on board IDE controller. Many of the standalone programs dump core: pwd dumps core, umount and others. I don't know whether it's again memory or cache memory on that board. Anyway I'm clueless at the moment. Anyone else seeing these problems? --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de FreeBSD blues 2.1.0-Development FreeBSD 2.1.0-Development #1: Wed Jan 18 10:42:31 1995 kuku@blues:/usr/src/sys/compile/BLUES i386 From owner-freebsd-hackers Sun Jan 22 13:11:01 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id NAA12619 for hackers-outgoing; Sun, 22 Jan 1995 13:11:01 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id NAA12609 for ; Sun, 22 Jan 1995 13:10:51 -0800 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id NAA22623; Sun, 22 Jan 1995 13:10:33 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.9/8.6.5) with SMTP id NAA07491; Sun, 22 Jan 1995 13:10:33 -0800 Message-Id: <199501222110.NAA07491@corbin.Root.COM> X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol To: "Christoph P. Kukulies" cc: freebsd-hackers@freefall.cdrom.com Subject: Re: 2.0-snap install wd0 on a PCI/I-486SP3G In-reply-to: Your message of "Sun, 22 Jan 95 23:00:31 +0100." <199501222200.XAA21301@gilberto.physik.rwth-aachen.de> From: David Greenman Reply-To: davidg@Root.COM Date: Sun, 22 Jan 1995 13:10:27 -0800 Sender: hackers-owner@FreeBSD.org Precedence: bulk >Many of the standalone programs dump core: pwd dumps core, >umount and others. I don't know whether it's again memory or cache >memory on that board. The current 2.0-snap is *VERY* broken. The problems with -current will be fixed in the next couple of days, and a new 2.0-snap will then be made which should clear up the problems. -DG From owner-freebsd-hackers Sun Jan 22 16:39:30 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id QAA15829 for hackers-outgoing; Sun, 22 Jan 1995 16:39:30 -0800 Received: from uuneo.neosoft.com (uuneo.NeoSoft.COM [198.64.6.8]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id QAA15823 for ; Sun, 22 Jan 1995 16:39:28 -0800 Received: (from mailman@localhost) by uuneo.neosoft.com (8.6.9/8.6.9) id SAA27936 for ; Sun, 22 Jan 1995 18:39:12 -0600 Received: from concorde.neosoft.com(198.65.161.214) by uuneo.neosoft.com via smap (V1.3) id smaa27890; Sun Jan 22 18:38:45 1995 Received: (from dbaker@localhost) by Concorde.NeoSoft.COM (8.6.9/8.6.9) id RAA00211; Sun, 22 Jan 1995 17:27:02 -0600 Date: Sun, 22 Jan 1995 17:27:01 -0600 (CST) From: Daniel Baker To: hackers@FreeBSD.org Subject: Virus Scanner Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hackers-owner@FreeBSD.org Precedence: bulk Where can I get a virus scanner for FreeBSD Daniel Baker -- NeoSoft FTP/UseNet Administrator (713)531-8571 DBaker@NeoSoft.COM DBaker@Concorde-Mail.NeoSoft.COM From owner-freebsd-hackers Sun Jan 22 17:02:19 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id RAA16943 for hackers-outgoing; Sun, 22 Jan 1995 17:02:19 -0800 Received: from post.demon.co.uk (post.demon.co.uk [158.152.1.72]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id RAA16910 for ; Sun, 22 Jan 1995 17:01:06 -0800 Received: from bagpuss.demon.co.uk by post.demon.co.uk id aa21997; 23 Jan 95 1:00 GMT Received: (karl@localhost) by bagpuss.demon.co.uk (99.9/99.9) id BAA09216; Mon, 23 Jan 1995 01:01:41 GMT From: Karl Strickland Message-Id: <199501230101.BAA09216@bagpuss.demon.co.uk> Subject: Need jumper settings for WD8003E - anyone? To: freebsd-hackers@freefall.cdrom.com Date: Mon, 23 Jan 1995 01:01:40 +0000 (GMT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 349 Sender: hackers-owner@FreeBSD.org Precedence: bulk As the subject says - I've lost my copy :-( Thanks in advance! -- ------------------------------------------+----------------------------------- Mailed using ELM on FreeBSD | Karl Strickland PGP 2.3a Public Key Available. | Internet: karl@bagpuss.demon.co.uk | From owner-freebsd-hackers Sun Jan 22 18:26:53 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id SAA18231 for hackers-outgoing; Sun, 22 Jan 1995 18:26:53 -0800 Received: from goof.com (root@goof.com [198.82.204.15]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id SAA18224 for ; Sun, 22 Jan 1995 18:26:48 -0800 Received: (from mmead@localhost) by goof.com (8.6.9/8.6.9) id VAA08808 for hackers@freebsd.org; Sun, 22 Jan 1995 21:26:26 -0500 From: "matthew c. mead" Message-Id: <199501230226.VAA08808@goof.com> Subject: writing bootcode; need a method To: hackers@FreeBSD.org Date: Sun, 22 Jan 1995 21:26:25 -0500 (EST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 810 Sender: hackers-owner@FreeBSD.org Precedence: bulk Does anyone know how to write the FreeBSD bootcode despite the fact that disklabel doesn't like the way sysinstall sets up the drives? My setup is this: I have an IDE drive (for a couple doom games and such), so I still want FreeBSD to boot off sd0. I need to put the bootmanager on the wd0 drive, and then to run FreeBSD, point it to disk 2. Then I've got to manually type in hd(1,a)/kernel each time it boots. I know how to modify the bootcode and rebuild it, but disklabel won't write the bootcode, cause it doesn't like how sysinstall set things up... Any ideas? -matt -- Matthew C. Mead -- System/Network Administration, User Support, Software Devel. Virginia Tech Center for Transportation Research Work Related: mmead@ctr.vt.edu | All Other: mmead@goof.com WWW: http://www.goof.com:/~mmead From owner-freebsd-hackers Sun Jan 22 18:55:20 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id SAA18949 for hackers-outgoing; Sun, 22 Jan 1995 18:55:20 -0800 Received: from alpha2.csd.uwm.edu (wraith@alpha2.csd.uwm.edu [129.89.8.202]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id SAA18840; Sun, 22 Jan 1995 18:50:50 -0800 Received: (wraith@localhost) by alpha2.csd.uwm.edu (8.6.9/8.6.8) id UAA20330; Sun, 22 Jan 1995 20:50:34 -0600 From: Robert Michael Gorichanaz Message-Id: <199501230250.UAA20330@alpha2.csd.uwm.edu> Subject: Is this a bug?!? To: questions@FreeBSD.org Date: Sun, 22 Jan 1995 20:50:32 -0600 (CST) Cc: hackers@FreeBSD.org, hardware@FreeBSD.org X-Mailer: ELM [version 2.4 PL24alpha3] Content-Type: text Content-Length: 1530 Sender: hackers-owner@FreeBSD.org Precedence: bulk I seem to have stumbled upon a bug (?!?) in FreeBSD - or maybe its a hardware thing - dunno. I just finished upgrading one of my 'bsd boxes from a dx2-50 ISA to a dx2-66 VLB motherboard. Problems: I now seem to be unable to issue a Ctrl-Alt-Del (system just beeps at me each time I hit the combo). 'shutdown' results in a kernel panic: panic: b_to_q to a clist with no reserved cblocks 'reboot' 'fastboot' 'halt' etc. all lock the system just as it is about to reboot to system. I get the "Press any key to reboot" message, and then the keyboard locks and I hafta hit the reset switch. The board I used to use had the Symphony chipset, AMI bios and an Intel dx-50. This new one has a Bioteq chipset, AMI bios, and an AMD dx2-66. MoBo functions just fine under a DOS/Windows environment (ctrl-alt-del works). Cards: Soundblaster 16 Buslogic BT-545 16bit busmaster SCSI 'No-name' VLB IDE controller Trident 9400CXI VLB video 1MB This is the only panic I have experienced. While this isnt a HUGE problem, I really need to be able to reboot this machine remotely (have an autodial script to start a point-to-point link w/outside world). Has anyone had similar problems with VLB boards? Do I have a piece of sh*t MoBo? -W- -- / /| \ O For all you ORIGIN needs, | \`o.O' | Ack! Thptptptpt! -+- the Avatar is IN. | =(___)= | | \ U / wraith@alpha2.csd.uwm.edu Games, hardware, and comments. From owner-freebsd-hackers Sun Jan 22 20:25:01 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id UAA20906 for hackers-outgoing; Sun, 22 Jan 1995 20:25:01 -0800 Received: from simon.chi.il.us (simon.chi.il.us [199.245.227.17]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id UAA20897 for ; Sun, 22 Jan 1995 20:24:56 -0800 Received: by simon.chi.il.us (Smail3.1.28.1 #2) id m0rWGKV-000NAvC; Sun, 22 Jan 95 22:24 CST Message-Id: Date: Sun, 22 Jan 95 22:24 CST From: steve@simon.chi.il.us (Steven E. Piette) To: hackers@FreeBSD.org Subject: Re: SMC EtherEZ PnP Cc: davidg@Root.COM, jgreco@ns.sol.net, phk@ref.tfs.com Sender: hackers-owner@FreeBSD.org Precedence: bulk > To: steve@simon.chi.il.us (Steven E. Piette) > cc: jgreco@ns.sol.net, phk@ref.tfs.com > Subject: Re: SMC EtherEZ PnP > From: David Greenman > > >Back in October, there was some interest in the details of this new SMC > >adaptor. For $49 even if I couldn't use it with FreeBSD right off, it was > >a bargin. It could always replace the old 3C501 in the DOS machine :-) > >So, I got one. > > > >Here's the spec sheet that comes with: > > > >They also claim that "The EtherEZ adaptor, when in its optional Memory > >Mapped Adressing Mode, is compatable with SMC drivers developed for the > >EtherCard Elite16 Ultra adaptor, and drivers created by other developers." > > > >We'll see ..... > > It needs a patch to the driver before it will work. You might be able to > get it to work by setting 'iosiz 8192' in the kernel config file. > Unfortunately, 'iosiz' isn't settable in userconfig (-c on startup). That > needs to be fixed... > > -DG > I've received the SMC 83C795 Tech spec and done a quick hack which seems to work with both the SMC Ultra Elite (8216C) and the SMC EtherEZ (8316C) cards. The patch just reads the apparent size of buffer window from the asic and sets memsize to reflect that. I've tested with both here, so here's the diffs so others can try it out. *** if_ed.c.orig Thu Nov 17 08:42:27 1994 --- if_ed.c Sat Jan 21 13:19:21 1995 *************** *** 408,413 **** --- 408,437 ---- isa16bit = 0; memsize = 8192; } + + + if (sc->is790) { + outb(sc->asic_addr + ED_WD790_HWR, + inb(sc->asic_addr + ED_WD790_HWR) | ED_WD790_HWR_SWH); + + switch (inb(sc->asic_addr + ED_WD790_RAR) & ED_WD790_RAR_SZ64) { + case ED_WD790_RAR_SZ64: + memsize = 65536; + break; + case ED_WD790_RAR_SZ32: + memsize = 32768; + break; + case ED_WD790_RAR_SZ16: + memsize = 16384; + break; + case ED_WD790_RAR_SZ8: + memsize = 8192; + break; + } + outb(sc->asic_addr + ED_WD790_HWR, + inb(sc->asic_addr + ED_WD790_HWR) & ~ED_WD790_HWR_SWH); + } + #if ED_DEBUG printf("type = %x type_str=%s isa16bit=%d memsize=%d id_msize=%d\n", sc->type, sc->type_str, isa16bit, memsize, isa_dev->id_msize); *************** *** 546,556 **** sc->cr_proto = ED_CR_RD2; } else { outb(sc->asic_addr + ED_WD_MSR, ED_WD_MSR_MENB); ! outb(sc->asic_addr + 0x04, (inb(sc->asic_addr + 0x04) | 0x80)); ! outb(sc->asic_addr + 0x0b, ((kvtop(sc->mem_start) >> 13) & 0x0f) | ((kvtop(sc->mem_start) >> 11) & 0x40) | ! (inb(sc->asic_addr + 0x0b) & 0xb0)); ! outb(sc->asic_addr + 0x04, (inb(sc->asic_addr + 0x04) & ~0x80)); sc->cr_proto = 0; } --- 570,580 ---- sc->cr_proto = ED_CR_RD2; } else { outb(sc->asic_addr + ED_WD_MSR, ED_WD_MSR_MENB); ! outb(sc->asic_addr + ED_WD790_HWR, (inb(sc->asic_addr + ED_WD790_HWR) | ED_WD790_HWR_SWH)); ! outb(sc->asic_addr + ED_WD790_RAR, ((kvtop(sc->mem_start) >> 13) & 0x0f) | ((kvtop(sc->mem_start) >> 11) & 0x40) | ! (inb(sc->asic_addr + ED_WD790_RAR) & 0xb0)); ! outb(sc->asic_addr + ED_WD790_HWR, (inb(sc->asic_addr + ED_WD790_HWR) & ~ED_WD790_HWR_SWH)); sc->cr_proto = 0; } *** if_edreg.h.orig Thu Aug 4 12:42:35 1994 --- if_edreg.h Sat Jan 21 13:23:31 1995 *************** *** 705,710 **** --- 705,729 ---- #define ED_WD790_ICR_EIL 0x01 /* enable interrupts */ /* + * REV/IOPA Revision / I/O Pipe register for the 83C79X + */ + #define ED_WD790_REV 7 + + #define ED_WD790 0x20 + #define ED_WD795 0x40 + + /* + * 79X RAM Address Register (RAR) + * Enabled with SWH bit=1 in HWR register + */ + #define ED_WD790_RAR 0x0b + + #define ED_WD790_RAR_SZ8 0x00 /* 8k memory buffer */ + #define ED_WD790_RAR_SZ16 0x10 /* 16k memory buffer */ + #define ED_WD790_RAR_SZ32 0x20 /* 32k memory buffer */ + #define ED_WD790_RAR_SZ64 0x30 /* 64k memory buffer */ + + /* * General Control Register (GCR) * Enabled with SWH bit=1 in HWR register */ *************** *** 714,719 **** --- 733,739 ---- #define ED_WD790_GCR_IR1 0x08 /* bit 1 of encoded IRQ */ #define ED_WD790_GCR_ZWSEN 0x20 /* zero wait state enable */ #define ED_WD790_GCR_IR2 0x40 /* bit 2 of encoded IRQ */ + #define ED_WD790_GCR_LIT 0x01 /* Link Integrity Test Enable */ /* * The three bits of the encoded IRQ are decoded as follows: * Steve Piette Applied Computer Technology steve@simon.chi.il.US. 7N852 Phar Lap Drive (708) 513-6920 St. Charles, IL 60175-6868 ------------------------------------------------------------------------------- From owner-freebsd-hackers Sun Jan 22 22:02:13 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id WAA21566 for hackers-outgoing; Sun, 22 Jan 1995 22:02:13 -0800 Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.20.4]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id WAA21560 for ; Sun, 22 Jan 1995 22:02:11 -0800 Received: by brasil.moneng.mei.com (4.1/SMI-4.1) id AA13170; Sun, 22 Jan 95 23:59:45 CST From: Joe Greco Message-Id: <9501230559.AA13170@brasil.moneng.mei.com> Subject: No pages? revisited (2.0R) To: hackers@FreeBSD.org Date: Sun, 22 Jan 1995 23:59:44 -0600 (CST) Cc: ods-admin@ns.sol.net X-Mailer: ELM [version 2.4beta PL9] Content-Type: text Content-Length: 2377 Sender: hackers-owner@FreeBSD.org Precedence: bulk Odd 2.0R problems revisited...? I have been working with a large local BBS to get them Daemonized. I convinced them to provide FreeBSD shell accounts by offering to supply a router for their Internet connection (freeing up the machine they'd been using - a 4MB 386DX/40). I provided them with a Northgate 386DX/25 motherboard with 5MB last nite, and all seemed well. The hard disk, controller, serial card, display controller were all taken from the DX/40. The motherboard, memory, and WD8003E were taken from sol.net spare inventory and have worked in the past. It crashed early this morning with the dreaded "No pages" (it had been working just dandy on the 386DX/40). They rebooted. It crashed again tonite. The machine is not doing anything at the time of crash, at least that I am aware of - other than acting as internetwork router. There is a chance that it had started /etc/daily this morning, but reports were that it crashed prior to that. Nobody logged in. Just running pppd, named, and trivial other standard stuff. Notes: I did notice at one point that the machine seemed to be mildly funky - it got in a state last night where it was working, but systat would report "Alternate system clock has died, reverting to pigs" on some screens, and vmstat's output was rather funky. We let it go, since it seemed otherwise happy. Systat/etc works now, after a power cycle. Also: the kernel was generated from a 2.0R source tree with a single patch previously supplied to me by David Greenman(I think) that tweaked some magic number in vm/vm_pageout.c from 4 to 16 (vm_pageout_free_min = 16 + something) because I had had a similar problem on my news server (I am not sure if the extra memory I added or the patch fixed it on my news server, but I haven't seen it happen again). So this really makes No Friggin' Sense. As an interim fix, I am going to put 8MB more in the machine tomorrow morning. I suspect some sort of hardware problem - because it WAS working great on their DX/40 - so I may end up swapping in a new motherboard. I'd hate to do that, because this is a great "New Life for Old Hardware." Comments/advice/etc welcome. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 From owner-freebsd-hackers Sun Jan 22 22:37:54 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id WAA22211 for hackers-outgoing; Sun, 22 Jan 1995 22:37:54 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id WAA22205 for ; Sun, 22 Jan 1995 22:37:50 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id RAA20066; Mon, 23 Jan 1995 17:35:52 +1100 Date: Mon, 23 Jan 1995 17:35:52 +1100 From: Bruce Evans Message-Id: <199501230635.RAA20066@godzilla.zeta.org.au> To: freebsd-hackers@FreeBSD.org, rkw@dataplex.net Subject: Re: Which libraries? Sender: hackers-owner@FreeBSD.org Precedence: bulk >In trying to fix some problems in wu-ftpd, I ran into the fnmatch >incompatabilities. They are straight-forward to fix. But in looking into >them, I found that there are 4 different versions of fnmatch.c in the >-current tree. There are about 17 different versions of getopt.c :-(. >Is there some reason that we are not using the libc version in each case? It takes too long to decide if an imported utility depends on the possibly nonstandard library sources that are distributed with the utility. Gnu getopt certainly has features that aren't standard are used by most gnu utilites. >And as for that, the version in libc is missing some of the options. >Is there some reason that our libc is not the glibc? glibc is copylefted. Bruce From owner-freebsd-hackers Sun Jan 22 23:01:02 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id XAA22810 for hackers-outgoing; Sun, 22 Jan 1995 23:01:02 -0800 Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id WAA22577; Sun, 22 Jan 1995 22:55:35 -0800 Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.8/8.6.6) id BAA02642; Mon, 23 Jan 1995 01:53:07 -0500 From: Wankle Rotary Engine Message-Id: <199501230653.BAA02642@skynet.ctr.columbia.edu> Subject: Re: Is this a bug?!? To: wraith@csd.uwm.edu (Robert Michael Gorichanaz) Date: Mon, 23 Jan 1995 01:53:04 -0500 (EST) Cc: hackers@FreeBSD.org, questions@FreeBSD.org In-Reply-To: <199501230250.UAA20330@alpha2.csd.uwm.edu> from "Robert Michael Gorichanaz" at Jan 22, 95 08:50:32 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 7401 Sender: hackers-owner@FreeBSD.org Precedence: bulk They say this Robert Michael Gorichanaz person was kidding when he wrote: > > I seem to have stumbled upon a bug (?!?) in FreeBSD What version?!?!?! > - or maybe its a > hardware thing - dunno. > > I just finished upgrading one of my 'bsd boxes from a dx2-50 ISA to a dx2-66 > VLB motherboard. Problems: > > I now seem to be unable to issue a Ctrl-Alt-Del (system > just beeps at me each time I hit the combo). > > 'shutdown' results in a kernel panic: > > panic: b_to_q to a clist with no reserved cblocks Well there's a good chance that this particular panic isn't the result of a hardware problem, though it certainly is a bug. You need to supply *all* the messages generated between the time you typed 'shutdown' and the time when the panic message appeared. Write them down if you have to ("I don't remember the error messages exactly" won't cut it: detail is important). What I'm curious to know is exactly how far shutdown gets before the system pukes. Does it do it immediately? Does it shut down some processes first? Please be specific. For extra credit, provide a stack trace. :) I've been able to reliably reproduce this panic message on my system now that I've started looking into actually using /dev/console for something. Basically, I want to be able to put a getty on /dev/console (instead of /dev/ttyv0) so that I can boot either using the VGA display or a serial port as a console and have a getty pop up in the right place without having to modify /etc/ttys. (SunOS handles this correctly: /dev/console is always the console device no matter what physical I/O device you use.) This would be especially handy now that FreeBSD-current can be booted from a serial port without any special tinkering. The general consensus is that you aren't supposed to put a getty on /dev/console, but I disagree (and I certainly don't think it should result in a panic), so I've decided to hunt down and terminate this bug with extreme prejudice no matter how much of my real work I have to put aside to do it. :) The way I've been able to duplicate the problem is as follows: 1) Boot the system with a VGA console 2) Edit /etc/ttys and activate a getty on 'console' while turning off the getty on 'ttyv0.' 3) Log in on 'console' as root 4) Type the following: echo kaboom > /dev/ttyv0 Alternatively, if you boot with a serial port as your console, you can replace step 4 with: echo kaboom > /dev/ttyd0. Another way to do it is to fire up the X server. I've also seen the kernel panic in putc() because of the same problem (no reserved cblocks). Basically, if you write to the console device while /dev/console is also open, you get a panic. The immediate problem is that the tty struct that eventually makes it to ttywrite() doesn't have its clists set up correctly. cblocks are supposed to be reserved in ttyopen() (from what I can tell). After finally building a kernel with debugging symbols (6 Mbytes worth!) and 'options DODUMP,' I managed to analyze a crash dump and discovered that writing to /dev/ttyv0 actually causes the kernel to go from write(), to vn_write(), to ffsspec_write(), to spec_write(), to cn_write(), to scwrite(), to ttwrite() and then to b_to_q() and a panic. The strange thing is the call to cnwrite(): this should only happen if you actually write to /dev/console -- a write directly to /dev/ttyv0 should not end up there. Tracing back, I discovered that vn->v_un->vu_specinfo->si_rdev in spec_write() was 0x00000000 where it probably should have been 0x0c000000 (or something like that -- basically, 0x00000000 is major 0/minor 0 where it should have been major 12/minor 0 (for syscons) instead). My feeling is that there's a lookup function somewhere that's getting confused and returning the major/minor numbers for /dev/console when it should be returning the major/minor of the actual driver device. That, or it's failing entirely and just returning 0. The trouble is that there's a lot of code to cover: the problem could be in vn_write(), or it could be in vn_open() (you have to open the device before you can write to it, right?) or somewhere in between. Kernel printf()s themselves don't cause problems because there aren't any 'struct tty's involved. I'm not at all sure why normal writes to /dev/console work but writes to /dev/ttyv0 (or /dev/ttyd0 depending on the circumstances) with /dev/console open will bomb. Hmmm... now that I think of it, maybe /dev/ttyv0 isn't being opened at all... could it be /dev/console is actually being opened in place of /dev/ttyv0 by mistake? Maybe we're getting the major/minor number wrong right from the start and ttyopen()ing /dev/console for a second time instead of ttyopen()ing /dev/ttyv0, and then ttwrite()ing to ttyv0 when it hasn't really been properly open()ed yet. That would explain the bogus call to cnwrite and uninitialized clists. I'll have to look into this tomorrow. > 'reboot' 'fastboot' 'halt' etc. all lock the system just as > it is about to reboot to system. I get the "Press any key to reboot" > message, and then the keyboard locks and I hafta hit the reset > switch. This I don't know about. Whenever my system panics because of the 'no reserved cblocks' problem it always reboots cleanly. I have extremely generic hardware, however. (386DX/40 (no FPU) with 8 megs of RAM and only IDE disks) > The board I used to use had the Symphony chipset, AMI bios and an Intel > dx-50. This new one has a Bioteq chipset, AMI bios, and an AMD dx2-66. > > MoBo functions just fine under a DOS/Windows environment (ctrl-alt-del > works). Rrrrr... please don't say this. In reality, nothing functions just fine in a DOS/Windoze environment. If it did, you wouldn't be running FreeBSD. > Cards: Soundblaster 16 > Buslogic BT-545 16bit busmaster SCSI > 'No-name' VLB IDE controller > Trident 9400CXI VLB video 1MB > > This is the only panic I have experienced. While this isnt a HUGE problem, > I really need to be able to reboot this machine remotely (have an autodial > script to start a point-to-point link w/outside world). > > Has anyone had similar problems with VLB boards? Do I have a piece of sh*t > MoBo? There may be a hardware problem involved, but I'm not sure how closely related it is to this panic. From what I've read, FreeBSD uses something of a brute force approach to reset the CPU (it actually causes the CPU to triple fault, which shuts it down). But that doesn't happen until *after* the panic: I can underatand your hardware objecting to the brute force CPU reset, but that doesn't account for the panic since that happens before cpu_reset() is called. If you're feeling really adventurous you can generate a crash dump and try to trace through it to see exactly what the kernel does that leads up to the panic. This is a little tricky, but it's the best way to isolate the problem. -Bill -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~T~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Bill Paul (212) 854-6020 | System Manager Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The Møøse Illuminati: ignore it and be confused, or join it and be confusing! ~~~~~~~~ FreeBSD 2.1.0-Development #1: Fri Jan 20 14:28:17 EST 1995 ~~~~~~~~~ From owner-freebsd-hackers Mon Jan 23 01:04:50 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id BAA26869 for hackers-outgoing; Mon, 23 Jan 1995 01:04:50 -0800 Received: from cd1-fddi.lrz-muenchen.de (cd1-fddi.lrz-muenchen.de [129.187.13.3]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id BAA26771; Mon, 23 Jan 1995 01:03:17 -0800 Received: from loth.psychologie.wiso.tu-muenchen.de by cd1.lrz-muenchen.de; Mon, 23 Jan 95 08:53:19 +0100 Received: from LOTH/MERCURY by loth.psychologie.wiso.tu-muenchen.de (Mercury 1.11); Mon, 23 Jan 95 8:53:21 GMT+0200 Received: from MERCURY by LOTH (Mercury 1.11); Mon, 23 Jan 95 8:53:09 GMT+0200 From: "Guenter Marx" Organization: Chair of Psychology, TU Munich To: questions@FreeBSD.org Date: Mon, 23 Jan 1995 08:53:06 GMT+0100 Subject: BSD Installation 2.0 CC: hackers@FreeBSD.org Priority: normal X-mailer: Pegasus Mail/Windows (v1.11a) Message-ID: Sender: hackers-owner@FreeBSD.org Precedence: bulk Dear Sir, 2 days ago I bought the latest BSD Version 2.0 on a CD from DiskNet. I have the following installation problem. First it's an absolutely empty CONNER HD (540MB). I boot up the system with the boot floppy. I 'Fdisk' my HD with 266MB with Slice 1. Up to now everything's okay. On the screen I see a bootable BSD partition. Then I choose 'Disklabel'. I see a table on my screen with partitions a-h. Partition c is the FreeBsd partition and d is the entire disk. Then I choose ASSIGN and I'm asked which partition. I really don't know what I have to enter at this point. If I enter the letter c or d then it says INVALID PARTITION. If I enter a number it says INVALID PARTITION. If I enter the letter a,b or e-h it says INVALID PARTITION TYPE. At the moment I really don't know how to get BSD on my HD. Can Someone help me,please. Best regards, Guenter From owner-freebsd-hackers Mon Jan 23 02:46:32 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id CAA02315 for hackers-outgoing; Mon, 23 Jan 1995 02:46:32 -0800 Received: from eros.britain.eu.net (eros.Britain.EU.net [192.91.199.2]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id CAA02302 for ; Mon, 23 Jan 1995 02:46:17 -0800 Received: from sixnine.gid.co.uk by eros.britain.eu.net with UUCP id ; Mon, 23 Jan 1995 10:45:19 +0000 Received: by gid.co.uk (smail2.5) id AA29048; Mon, 23 Jan 95 07:53:29 GMT Message-Id: <3212.199501230801@seagoon.gid.co.uk> Received: from [192.9.200.25] by seagoon.gid.co.uk; Mon, 23 Jan 1995 08:01:00 GMT PP-warning: Illegal Via field on preceding line X-Sender: rb@seagoon.gid.co.uk Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 23 Jan 1995 08:00:22 +0000 To: hackers@FreeBSD.org From: rb@gid.co.uk (Bob Bishop) Subject: ep, 3C579 Sender: hackers-owner@FreeBSD.org Precedence: bulk Hi guys, On 2.0R, does the ep driver work with 3C579? If so, how should it be configured? I have the driver recognising the card at 0x8000 (ie slot 8) and the interface seems to come up, but it won't pass packets enough for ping to work (half-formed entries in the ARP cache). Had to configure the card on interrupt 9 and the driver on irq 10 otherwise got complaints about mismatch from the driver. This doesn't seem right, but I know nothing about EISA anyway. Please reply by mail. Thanks in advance. PS So far, I have 2.0 on 4 diverse machines and I like it a lot. Well done everyone. I'll have to take the plunge and upgrade my file server from 1.0.2... -- Bob Bishop (01734) 774017 international code +44 1734 rb@gid.co.uk fax (01734) 894254 between 0800 and 1800 UK From owner-freebsd-hackers Mon Jan 23 05:57:41 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id FAA00855 for hackers-outgoing; Mon, 23 Jan 1995 05:57:41 -0800 Received: from dkuug.dk (dkuug.dk [193.88.44.89]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id FAA00848 for ; Mon, 23 Jan 1995 05:57:34 -0800 Received: from kmd-ac.dk by dkuug.dk with UUCP id AA02350 (5.65c8/IDA-1.4.4j for freebsd.org!hackers); Mon, 23 Jan 1995 13:45:21 +0100 Message-Id: <199501231245.AA02350@dkuug.dk> Subject: Info on cirrus CLGD6225/35 ??? To: hackers@FreeBSD.org (FreeBSD hackers) Date: Mon, 23 Jan 1995 13:47:37 +0000 (GMT) From: "Soeren Schmidt" X-Mailer: ELM [version 2.4 PL22] Content-Type: text Content-Length: 367 X-Charset: ASCII X-Char-Esc: 29 Sender: hackers-owner@FreeBSD.org Precedence: bulk The subject says it all: Anybody having info/data on the CLGD6325/35, especially how it handles some of the nifty LCD features and how it is programmed... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org | sos@kmd-ac.dk) FreeBSD Core Team So much code to hack -- so little time .. From owner-freebsd-hackers Mon Jan 23 06:08:41 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id GAA02079 for hackers-outgoing; Mon, 23 Jan 1995 06:08:41 -0800 Received: from dataplex.net (SHARK.DATAPLEX.NET [199.183.109.241]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id GAA02073 for ; Mon, 23 Jan 1995 06:08:40 -0800 Received: from [199.183.109.242] by dataplex.net with SMTP (MailShare 1.0b8); Mon, 23 Jan 1995 06:32:12 -0600 X-Sender: wacky@mail.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 23 Jan 1995 06:32:13 -0600 To: Mark Diekhans From: rkw@dataplex.net (Richard Wackerbarth) Subject: Re: bin/173: rc trys to mount modload fs before ld is available. Cc: hackers@FreeBSD.org Sender: hackers-owner@FreeBSD.org Precedence: bulk >and that modload doesn't return very useful error messages. Perhaps we can address the problem from this direction. Useful messages and documentation do not take up valuable locked-in memory. From owner-freebsd-hackers Mon Jan 23 06:37:22 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id GAA02938 for hackers-outgoing; Mon, 23 Jan 1995 06:37:22 -0800 Received: from alpha.dsu.edu (ghelmer@alpha.dsu.edu [138.247.32.12]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id GAA02932 for ; Mon, 23 Jan 1995 06:37:21 -0800 Received: (from ghelmer@localhost) by alpha.dsu.edu (8.6.9/8.6.9) id IAA02505; Mon, 23 Jan 1995 08:37:17 -0600 Date: Mon, 23 Jan 1995 08:37:17 -0600 (CST) From: Guy Helmer To: Daniel Baker cc: hackers@FreeBSD.org Subject: Re: Virus Scanner In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hackers-owner@FreeBSD.org Precedence: bulk On Sun, 22 Jan 1995, Daniel Baker wrote: > Where can I get a virus scanner for FreeBSD AFAIK, there aren't any virus scanners for FreeBSD. A more general solution, which can detect any system changes, is tripwire 1.2, available via anonymous ftp from coast.cs.purdue.edu in the subdirectory /pub/COAST/tripwire. Be careful to follow the instructions for optimal security. > Daniel Baker -- NeoSoft FTP/UseNet Administrator (713)531-8571 > DBaker@NeoSoft.COM > DBaker@Concorde-Mail.NeoSoft.COM Guy Helmer, Dakota State University Computing Services - ghelmer@alpha.dsu.edu From owner-freebsd-hackers Mon Jan 23 07:44:39 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id HAA05158 for hackers-outgoing; Mon, 23 Jan 1995 07:44:39 -0800 Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id HAA05108 for ; Mon, 23 Jan 1995 07:42:53 -0800 Received: (from sjl@localhost) by minnow.render.com (8.6.9/8.6.9) id PAA09689; Mon, 23 Jan 1995 15:42:04 GMT Date: Mon, 23 Jan 1995 15:42:02 +0000 (GMT) From: Steve Lacey To: hackers@FreeBSD.org Subject: Problem booting 2.0 with new motherboard Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hackers-owner@FreeBSD.org Precedence: bulk I had FreeBSD running fine on a P90 non-intel motherboard - using slice 2. Now, the motherboard has been changed to a genuine intel motherboard and now I can't get FreeBSD to boot. The Boot manager that comes with FreeBSD just ignores the FreeBSD option and os-bs reports "No Operating System". The actual disk is the same, and disk geoms in the bios and as reported by the freebsd floppy match. Anyone any clues? This is getting frustrating... Cheers, Steve. ----------------------------------------------------------------------------- Steve Lacey, RenderMorphics Ltd. Email: sjl@render.com `Quis custodiet ipsos custodes?' Tel: +44 171 251 4411 Fax: +44 171 251 0939 From owner-freebsd-hackers Mon Jan 23 10:01:11 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id KAA00558 for hackers-outgoing; Mon, 23 Jan 1995 10:01:11 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id KAA00552 for ; Mon, 23 Jan 1995 10:01:09 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA08367; Mon, 23 Jan 95 09:37:29 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9501231637.AA08367@cs.weber.edu> Subject: Re: More serial console stuff... To: bde@zeta.org.au (Bruce Evans) Date: Mon, 23 Jan 95 9:37:28 MST Cc: rgrimes@gndrsh.aac.dev.com, freebsd-hackers@FreeBSD.org In-Reply-To: <199501220547.QAA31999@godzilla.zeta.org.au> from "Bruce Evans" at Jan 22, 95 04:47:34 pm X-Mailer: ELM [version 2.4dev PL52] Sender: hackers-owner@FreeBSD.org Precedence: bulk > I thought the example was a real one. It's easy for the sd driver to > make it work, e.g.: > > unit = drive & 0x7f; > if (unit > max_sd_unit) /* max_sd_unit = min_sd_unit > * + nr_sd_units - 1 */ > return ERROR; > if (unit < min_sd_unit) /* min_sd_unit = number of drives > * at the time we hooked */ > jumpto(saved_vector); /* restore regs and continue with > * the driver that owned INT 0x13 > * at the time we hooked */ > unit -= min_sd_unit; /* actual SCSI unit number */ > > Whether the bootstrap can determine all the mappings done by all the > hooked drivers is another question. Begging your and Rods pardon, but the issue is not where the current code works, it's where it doesn't. The installations that are falling flat are the ones that need fixed. Generally, this has fallen into two categories: the first is the case of multiple controllers, where it is still possible to misinterpret the drive ID passed from the boot blocks because the probe order does not match the chain order (if the BIOS on the second device even supports chaining, and yes, many apparently do). The second is where the geometry is guessed wrong and incorrect disklabel information is generated, either because it isn't passed correctly, or because of LCF used in the calculation (the latter is the EIDE problem). > >4) Your DOS drive numbering is invalid, unless the post-boot OS > > hacks the INT 13 vector with something more than simple BIOS > > code -- specifically, an INT 13 redirector that does DOS > > drive number translation before calling the previous-to-load > > POST initialized INT 13 vector, if the drive number is less > > than or equal to 0x80 OR'ed with the number of drives (option > > DOS is not involved, except for the special version of the bootstrap > that boots from DOS. Complicated redirections are just more likely > if DOS has been used to load special drivers. I should have said "BIOS" or "no protected mode OS" drive numbering instead of singling out DOS... unless you see some way to determine the BIOS chaining order that was used to generate the drive ID so that that ID may be interpreted unambiguously by the kernel's protected mode driver. For example, say I have no built in controller in the system and two SCSI controllers that support chaining. Each SCSI controller has two identical drives on it. The kernel is loaded via BIOS and is passed drive ID 0x82. On which controller does this drive reside? The actual residence of the drive is determined by BIOS chaining order. The apparent-to-the-kernel residence of the drive is dependent on the controller probe order. Now do you see what I mean? Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jan 23 10:08:26 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id KAA00854 for hackers-outgoing; Mon, 23 Jan 1995 10:08:26 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id KAA00847 for ; Mon, 23 Jan 1995 10:08:23 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA08805; Mon, 23 Jan 95 11:02:34 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9501231802.AA08805@cs.weber.edu> Subject: Re: Virus Scanner To: dbaker@concorde-mail.neosoft.com (Daniel Baker) Date: Mon, 23 Jan 95 11:02:34 MST Cc: hackers@FreeBSD.org In-Reply-To: from "Daniel Baker" at Jan 22, 95 05:27:01 pm X-Mailer: ELM [version 2.4dev PL52] Sender: hackers-owner@FreeBSD.org Precedence: bulk > > Where can I get a virus scanner for FreeBSD > Where can I get a virus for FreeBSD? Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jan 23 10:13:34 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id KAA01004 for hackers-outgoing; Mon, 23 Jan 1995 10:13:34 -0800 Received: from kalypso.iqm.unicamp.br (kalypso.iqm.unicamp.br [143.106.13.10]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id KAA00989 for ; Mon, 23 Jan 1995 10:13:23 -0800 Received: (from vazquez@localhost) by kalypso.iqm.unicamp.br (8.6.9/8.6.9) id GAA01450; Mon, 23 Jan 1995 06:18:51 -0200 From: Pedro A M Vazquez Message-Id: <199501230818.GAA01450@kalypso.iqm.unicamp.br> Subject: Re: Virus Scanner To: ghelmer@alpha.dsu.edu (Guy Helmer) Date: Mon, 23 Jan 1995 06:18:46 -0200 (EDT) Cc: hackers@FreeBSD.org In-Reply-To: from "Guy Helmer" at Jan 23, 95 08:37:17 am Organization: Instituto de Quimica Unicamp X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 115 Sender: hackers-owner@FreeBSD.org Precedence: bulk Hello Please, don't laugh, but I'm using pcemu to run scan or other scan virus program on the dos files. Pedro From owner-freebsd-hackers Mon Jan 23 10:36:30 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id KAA02696 for hackers-outgoing; Mon, 23 Jan 1995 10:36:30 -0800 Received: from time.cdrom.com (time.cdrom.com [192.216.223.46]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id KAA02685 for ; Mon, 23 Jan 1995 10:36:27 -0800 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.9/8.6.9) with SMTP id KAA14491; Mon, 23 Jan 1995 10:35:16 -0800 X-Authentication-Warning: time.cdrom.com: Host localhost didn't use HELO protocol To: Pedro A M Vazquez cc: ghelmer@alpha.dsu.edu (Guy Helmer), hackers@FreeBSD.org Subject: Re: Virus Scanner In-reply-to: Your message of "Mon, 23 Jan 95 06:18:46 -0200." <199501230818.GAA01450@kalypso.iqm.unicamp.br> Date: Mon, 23 Jan 1995 10:35:15 -0800 Message-ID: <14490.790886115@time.cdrom.com> From: "Jordan K. Hubbard" Sender: hackers-owner@FreeBSD.org Precedence: bulk > Please, don't laugh, but I'm using pcemu to run scan or other > scan virus program on the dos files. I won't laugh, but I may bulge out my eyes in sheer disbelief.. :-) Jordan From owner-freebsd-hackers Mon Jan 23 10:57:36 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id KAA05171 for hackers-outgoing; Mon, 23 Jan 1995 10:57:36 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id KAA05163 for ; Mon, 23 Jan 1995 10:57:31 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA08997; Mon, 23 Jan 95 11:51:42 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9501231851.AA08997@cs.weber.edu> Subject: Re: writing bootcode; need a method To: mmead@goof.com (matthew c. mead) Date: Mon, 23 Jan 95 11:51:41 MST Cc: hackers@FreeBSD.org In-Reply-To: <199501230226.VAA08808@goof.com> from "matthew c. mead" at Jan 22, 95 09:26:25 pm X-Mailer: ELM [version 2.4dev PL52] Sender: hackers-owner@FreeBSD.org Precedence: bulk > > Does anyone know how to write the FreeBSD bootcode despite the fact that > disklabel doesn't like the way sysinstall sets up the drives? My setup is > this: I have an IDE drive (for a couple doom games and such), so I still want > FreeBSD to boot off sd0. I need to put the bootmanager on the wd0 drive, and > then to run FreeBSD, point it to disk 2. Then I've got to manually type in > hd(1,a)/kernel each time it boots. I know how to modify the bootcode and > rebuild it, but disklabel won't write the bootcode, cause it doesn't like how > sysinstall set things up... Any ideas? Examining a disk: ,---.--------------------------.----------------------------. | A | B | C | `---'--------------------------'----------------------------' A) DOS MBR (Master Boot Record) containing BIOS boot code and a DOS partition table. B) Some non-BSD partition. C) The BSD paritition for our example. Examining a BSD partition: ,---.---.----------------.----------------. | 1 | 2 | 3 | 4 ... | `---'---'----------------'----------------' 1) BSD second stage boot. 2) BSD disklabel. 3) BSD slice 'a'. 4) BSD subsequent slices. Examining a BSD disklabel: ,-----------. | a | .-----------. | b | c | d | .---+---+---. | b | c | d | `-----------' a) Per BSD partition information BIOS apparent geometry (obsolete, but still used) BAD144 info (broken in FreeBSD 2.x) b) C/H/S value for a particular slice c) absolute sector offset for a particular slice d) absolute length in sectors There are three required slices, which BSD calls 'a', 'c', and 'd': o Slice 'a' is the root (/) partition from which the kernel is loaded. o Slice 'c' is the entire DOS partition containing BSD information. o Slice 'd' is the entire disk, including the MBR and everything else on the disk (other partitions, etc.). When you write the boot code, the disklabel is used to locate the start of the BSD partition and write the boot code there. Without a disklabel, this is impossible, since there is no way to know where the parition starts. This is the current approach. It's actually the wrong approach, since it should be possible for the running OS to decode the DOS partition table information -- the 'c' and 'd' slices are truly antiquated space wasters. It's even worse when you have to define a disklabel entry for a DOS partition, when all of the needed info is already stored elsehere. For right now, you are required to have a disklabel before proceeding. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jan 23 11:23:44 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id LAA07808 for hackers-outgoing; Mon, 23 Jan 1995 11:23:44 -0800 Received: from goof.com (root@goof.com [198.82.204.15]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id LAA07796 for ; Mon, 23 Jan 1995 11:23:41 -0800 Received: (from mmead@localhost) by goof.com (8.6.9/8.6.9) id OAA03201; Mon, 23 Jan 1995 14:23:29 -0500 From: "matthew c. mead" Message-Id: <199501231923.OAA03201@goof.com> Subject: Re: writing bootcode; need a method To: terry@cs.weber.edu (Terry Lambert) Date: Mon, 23 Jan 1995 14:23:28 -0500 (EST) Cc: hackers@FreeBSD.org In-Reply-To: <9501231851.AA08997@cs.weber.edu> from "Terry Lambert" at Jan 23, 95 11:51:41 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 971 Sender: hackers-owner@FreeBSD.org Precedence: bulk Terry Lambert wrote: > Examining a disk: [ good description of how partitions, slices, mbrs work omitted ] > For right now, you are required to have a disklabel before proceeding. This unfortunately isn't the problem. The problem lies in the fact that the sysinstall does not require BSD partitions to begin and end on cylinder boundaries, whereas the disklabel program does. Thus, the disklabel program, when told to write boot code, finds what it considers to be errors with the disklabel, because sysinstall has made partitions that don't begin/end on cylinder boundaries, and does not write out the new boot code, thus hd(1,a)/kernel can NOT be made the default, again, simply because disklabel never writes the boot code. -matt -- Matthew C. Mead -- System/Network Administration, User Support, Software Devel. Virginia Tech Center for Transportation Research Work Related: mmead@ctr.vt.edu | All Other: mmead@goof.com WWW: http://www.goof.com:/~mmead From owner-freebsd-hackers Mon Jan 23 12:48:21 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id MAA10962 for hackers-outgoing; Mon, 23 Jan 1995 12:48:21 -0800 Received: from dvals1.larc.nasa.gov (dvals1.larc.nasa.gov [128.155.4.96]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id MAA10952 for ; Mon, 23 Jan 1995 12:48:18 -0800 Received: by dvals1.larc.nasa.gov (8.6.9/server2.4) id PAA28676; Mon, 23 Jan 1995 15:48:04 -0500 Message-Id: <199501232048.PAA28676@dvals1.larc.nasa.gov> From: Branson Matheson Subject: Re: writing bootcode; need a method To: terry@cs.weber.edu (Terry Lambert) Date: Mon, 23 Jan 1995 15:48:03 -0500 (EST) Cc: mmead@goof.com, hackers@FreeBSD.org In-Reply-To: <9501231851.AA08997@cs.weber.edu> from "Terry Lambert" at Jan 23, 95 11:51:41 am X-Mailer: ELM [version 2.4 PL21] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1200 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > > > > Does anyone know how to write the FreeBSD bootcode despite the fact that > > disklabel doesn't like the way sysinstall sets up the drives? My setup is > > this: I have an IDE drive (for a couple doom games and such), so I still want > > FreeBSD to boot off sd0. I need to put the bootmanager on the wd0 drive, and > > then to run FreeBSD, point it to disk 2. Then I've got to manually type in > > hd(1,a)/kernel each time it boots. I know how to modify the bootcode and > > rebuild it, but disklabel won't write the bootcode, cause it doesn't like how > > sysinstall set things up... Any ideas? In anycase... why cannot the boot manager take care of this... it _was_ designed for it.... put the boot manager on your ide drive... and tell it to boot from hd(0,a)kernel. I have this setup at home and use it frequently for just this reason. -branson -- _______________________________________________________________________________ E. Branson Matheson III e.b.matheson@larc.nasa.gov Computer Sciences Corporation "If Pete and Re-Pete were sitting on (804)864-9700 -- Work a fence, And Pete fell off.... (804)881-8308 -- Beeper Who'd be left?" From owner-freebsd-hackers Mon Jan 23 13:21:55 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id NAA15207 for hackers-outgoing; Mon, 23 Jan 1995 13:21:55 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id NAA15200 for ; Mon, 23 Jan 1995 13:21:52 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA09719; Mon, 23 Jan 95 14:16:03 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9501232116.AA09719@cs.weber.edu> Subject: Re: writing bootcode; need a method To: mmead@goof.com (matthew c. mead) Date: Mon, 23 Jan 95 14:16:03 MST Cc: hackers@FreeBSD.org In-Reply-To: <199501231923.OAA03201@goof.com> from "matthew c. mead" at Jan 23, 95 02:23:28 pm X-Mailer: ELM [version 2.4dev PL52] Sender: hackers-owner@FreeBSD.org Precedence: bulk > > For right now, you are required to have a disklabel before proceeding. > > This unfortunately isn't the problem. The problem lies in the fact > that the sysinstall does not require BSD partitions to begin and end on > cylinder boundaries, whereas the disklabel program does. Thus, the disklabel > program, when told to write boot code, finds what it considers to be errors > with the disklabel, because sysinstall has made partitions that don't begin/end > on cylinder boundaries, and does not write out the new boot code, thus > hd(1,a)/kernel can NOT be made the default, again, simply because disklabel > never writes the boot code. Oh. Well. That's very different. 8-). I don't know about the ending BS, but the beginning BS is correct. The MBR may or may not be able to load a second stage boot that doesn't fit in a track, since it might be incapable of sector I/O to do the deed. Now, judging this on the basis of a BSD-apparent instead of a BIOS apparent starting location, that *is* a mistake. And that's what disklabel seems to be doing. It's a wonder anyone with a translated geomtery drive can install at all. -- BEGIN WORKAROUND -- What *should* work as a workaround is telling the machine the BIOS apparent geometry so it gets the same idea about cylinder start in BIOS and in BSD (sysinstall and disklabel). -- END WORKAROUND -- Meanwhile, anyone want to cut a new sysinstall AND disklabel program? Or just a disklabel hacked to not care and a warning in the install instructions about picking a cylinder boundry in sysinstall? You *can* write the boot block out there with dd or even cat by shoving it directly out the 0c device (or 1c for disk 1, etc.), but it won't help you, since you will still be screwed when the boot block goes looking for a valid disklabel. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jan 23 13:23:04 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id NAA15253 for hackers-outgoing; Mon, 23 Jan 1995 13:23:04 -0800 Received: from kronos (kronos.cam.paramax.com [128.170.2.8]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id NAA15243 for ; Mon, 23 Jan 1995 13:22:55 -0800 Received: by kronos (4.1/SMI-4.1) id AA15237; Mon, 23 Jan 95 13:27:51 PST Date: Mon, 23 Jan 95 13:27:51 PST From: tunch@cam.paramax.com (Tunc Hoscan) Message-Id: <9501232127.AA15237@kronos> To: dbaker@concorde-mail.neosoft.com, terry@cs.weber.edu Subject: Re: Virus Scanner Cc: hackers@FreeBSD.org Sender: hackers-owner@FreeBSD.org Precedence: bulk > > > > > Where can I get a virus scanner for FreeBSD > > > > Where can I get a virus for FreeBSD? > *That* can be arranged !.. ;-) Tunc N. Hoscan tunch@cam.paramax.com From owner-freebsd-hackers Mon Jan 23 13:57:03 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id NAA16799 for hackers-outgoing; Mon, 23 Jan 1995 13:57:03 -0800 Received: from tfs.com (mailhub.tfs.com [140.145.250.1]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id NAA16792 for ; Mon, 23 Jan 1995 13:57:00 -0800 Received: by tfs.com (smail3.1.28.1) Message-Id: From: julian@tfs.com (Julian Elischer) Subject: Re: Virus Scanner To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 23 Jan 1995 13:55:46 -0800 (PST) Cc: vazquez@iqm.unicamp.br, ghelmer@alpha.dsu.edu, hackers@FreeBSD.org In-Reply-To: <14490.790886115@time.cdrom.com> from "Jordan K. Hubbard" at Jan 23, 95 10:35:15 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 446 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > > Please, don't laugh, but I'm using pcemu to run scan or other > > scan virus program on the dos files. > > I won't laugh, but I may bulge out my eyes in sheer disbelief.. :-) > > Jordan Is what you are saying, that you have a version of pcemu, that runs under FreeBSD, and allows many DOS programs to be run directly? wheredyagettit? in your experience, what programs run? anything USEFULL? like WP or MS-WORD, etc? julian > From owner-freebsd-hackers Mon Jan 23 13:57:51 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id NAA16850 for hackers-outgoing; Mon, 23 Jan 1995 13:57:51 -0800 Received: from tfs.com (mailhub.tfs.com [140.145.250.1]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id NAA16844 for ; Mon, 23 Jan 1995 13:57:48 -0800 Received: by tfs.com (smail3.1.28.1) Message-Id: From: julian@tfs.com (Julian Elischer) Subject: Re: Virus Scanner To: terry@cs.weber.edu (Terry Lambert) Date: Mon, 23 Jan 1995 13:57:13 -0800 (PST) Cc: dbaker@concorde-mail.neosoft.com, hackers@FreeBSD.org In-Reply-To: <9501231802.AA08805@cs.weber.edu> from "Terry Lambert" at Jan 23, 95 11:02:34 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 321 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > > > > Where can I get a virus scanner for FreeBSD > > > > Where can I get a virus for FreeBSD? hmm I bet we would be susceptible to a bootblock virus.. ? > > > Terry Lambert > terry@cs.weber.edu > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > From owner-freebsd-hackers Mon Jan 23 13:58:08 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id NAA16879 for hackers-outgoing; Mon, 23 Jan 1995 13:58:08 -0800 Received: from goof.com (root@goof.com [198.82.204.15]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id NAA16869 for ; Mon, 23 Jan 1995 13:58:03 -0800 Received: (from mmead@localhost) by goof.com (8.6.9/8.6.9) id QAA04848; Mon, 23 Jan 1995 16:57:51 -0500 From: "matthew c. mead" Message-Id: <199501232157.QAA04848@goof.com> Subject: Re: writing bootcode; need a method To: branson@dvals1.larc.nasa.gov (Branson Matheson) Date: Mon, 23 Jan 1995 16:57:50 -0500 (EST) Cc: terry@cs.weber.edu, hackers@FreeBSD.org In-Reply-To: <199501232048.PAA28676@dvals1.larc.nasa.gov> from "Branson Matheson" at Jan 23, 95 03:48:03 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 775 Sender: hackers-owner@FreeBSD.org Precedence: bulk Branson Matheson wrote: > > > sysinstall set things up... Any ideas? > In anycase... why cannot the boot manager take care of this... it _was_ > designed for it.... put the boot manager on your ide drive... and tell it > to boot from hd(0,a)kernel. I have this setup at home and use it > frequently for just this reason. Because I want to boot hd(1,a)/kernel, NOT hd(0,a)/kernel ... hd(0,a)/kernel would be a my ide drive, which has no incarnation of FreeBSD on it whatsoever. hd(1,a)/kernel is my sd0 drive, which has 2.0 on it. -matt -- Matthew C. Mead -- System/Network Administration, User Support, Software Devel. Virginia Tech Center for Transportation Research Work Related: mmead@ctr.vt.edu | All Other: mmead@goof.com WWW: http://www.goof.com:/~mmead From owner-freebsd-hackers Mon Jan 23 14:27:27 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id OAA18461 for hackers-outgoing; Mon, 23 Jan 1995 14:27:27 -0800 Received: from cats.ucsc.edu (root@cats-po-1.UCSC.EDU [128.114.129.22]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id OAA18451 for ; Mon, 23 Jan 1995 14:27:26 -0800 Received: from scruz.ucsc.edu by cats.ucsc.edu with SMTP id OAA16441; Mon, 23 Jan 1995 14:27:21 -0800 Received: from osprey by scruz.ucsc.edu id aa06008; 23 Jan 95 15:17 PST Received: (from markd@localhost) by Grizzly.COM (8.6.9/8.6.9) id OAA06612; Mon, 23 Jan 1995 14:20:26 -0800 Date: Mon, 23 Jan 1995 14:20:26 -0800 From: Mark Diekhans Message-Id: <199501232220.OAA06612@Grizzly.COM> To: rkw@dataplex.net CC: hackers@FreeBSD.org In-reply-to: (message from Richard Wackerbarth on Mon, 23 Jan 1995 06:32:13 -0600) Subject: Re: bin/173: rc trys to mount modload fs before ld is available. Sender: hackers-owner@FreeBSD.org Precedence: bulk >>and that modload doesn't return very useful error messages. > >Perhaps we can address the problem from this direction. Useful messages and >documentation do not take up valuable locked-in memory. This, in case something goes wrong, and putting ld in /sbin, since modload needs ld, to prevent the problem from happening no matter how fstab gets built. Mark From owner-freebsd-hackers Mon Jan 23 15:17:05 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id PAA20488 for hackers-outgoing; Mon, 23 Jan 1995 15:17:05 -0800 Received: from nomad.osmre.gov (nomad.osmre.gov [192.243.129.244]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id PAA20482 for ; Mon, 23 Jan 1995 15:17:03 -0800 Received: (from gfoster@localhost) by nomad.osmre.gov (8.6.8/8.6.6) id SAA26113; Mon, 23 Jan 1995 18:15:36 -0500 Date: Mon, 23 Jan 1995 18:15:36 -0500 From: Glen Foster Message-Id: <199501232315.SAA26113@nomad.osmre.gov> To: julian@tfs.com CC: terry@cs.weber.edu, dbaker@concorde-mail.neosoft.com, hackers@FreeBSD.org In-reply-to: (julian@tfs.com) Subject: Re: Virus Scanner Sender: hackers-owner@FreeBSD.org Precedence: bulk > From: julian@tfs.com (Julian Elischer) > Date: Mon, 23 Jan 1995 13:57:13 -0800 (PST) > Cc: dbaker@concorde-mail.neosoft.com, hackers@FreeBSD.org > > > > Where can I get a virus for FreeBSD? > hmm I bet we would be susceptible to a bootblock virus.. ? Well, most common PC boot block viruses know only about booting DOS and, typically, reveal themselves by not honoring the boot select choice the user makes. When a client says "my computer won't boot Unix anymore!" I always have them scan for a boot block virus and, almost always, it has turned out they have one. I would classify a boot block virus as a hardware virus rather than an OS-specific one (although it will only propagate through DOS). Glen Foster From owner-freebsd-hackers Mon Jan 23 15:40:28 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id PAA21779 for hackers-outgoing; Mon, 23 Jan 1995 15:40:28 -0800 Received: from UUCP-GW.CC.UH.EDU (root@UUCP-GW.CC.UH.EDU [129.7.1.11]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id PAA21773 for ; Mon, 23 Jan 1995 15:40:22 -0800 Received: from Taronga.COM by UUCP-GW.CC.UH.EDU with UUCP id AA19577 (5.67a/IDA-1.5); Mon, 23 Jan 1995 17:30:46 -0600 Received: by bonkers.taronga.com (smail2.5p) id AA12431; 23 Jan 95 17:29:39 CST (Mon) Received: (from peter@localhost) by bonkers.taronga.com (8.6.8/8.6.6) id RAA12428; Mon, 23 Jan 1995 17:29:39 -0600 From: Peter da Silva Message-Id: <199501232329.RAA12428@bonkers.taronga.com> Subject: Re: writing bootcode; need a method To: terry@cs.weber.edu (Terry Lambert) Date: Mon, 23 Jan 1995 17:29:39 -0600 (CST) Cc: mmead@goof.com, hackers@FreeBSD.org In-Reply-To: <9501231851.AA08997@cs.weber.edu> from "Terry Lambert" at Jan 23, 95 11:51:41 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 894 Sender: hackers-owner@FreeBSD.org Precedence: bulk > Examining a BSD partition: > > ,---.---.----------------.----------------. > | 1 | 2 | 3 | 4 ... | > `---'---'----------------'----------------' > > 1) BSD second stage boot. > 2) BSD disklabel. > 3) BSD slice 'a'. > 4) BSD subsequent slices. Um, it's more like this: > ,------------------------.----------------. > | 3 | 4 ... | > |---.---. | | > | 1 | 2 | | | > `---'---'----------------'----------------' It's very important to understand that slice A contains the second stage boot and disklabel. I know you know that, Terry, but it's not intuitively obvious. In our OSF system administration class the instructor insisted that these were *outside* the slice and that there were special interfaces to get them. You need to watch out for the infamous "swap on a" problem. From owner-freebsd-hackers Mon Jan 23 15:58:29 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id PAA22168 for hackers-outgoing; Mon, 23 Jan 1995 15:58:29 -0800 Received: from tfs.com (mailhub.tfs.com [140.145.250.1]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id PAA22160 for ; Mon, 23 Jan 1995 15:58:27 -0800 Received: from mailhub by tfs.com (smail3.1.28.1) with UUCP id m0rWYdv-0003wCC; Mon, 23 Jan 95 15:57 PST Received: from kalypso.iqm.unicamp.br by tfs.com (smail3.1.28.1) with SMTP id m0rWX8m-0003wmC; Mon, 23 Jan 95 14:21 PST Received: (from vazquez@localhost) by kalypso.iqm.unicamp.br (8.6.9/8.6.9) id UAA00342 for julian@TFS.COM; Mon, 23 Jan 1995 20:18:35 -0200 From: Pedro A M Vazquez Message-Id: <199501232218.UAA00342@kalypso.iqm.unicamp.br> Subject: Re: Virus Scanner To: julian@tfs.com (Julian Elischer) Date: Mon, 23 Jan 1995 20:18:30 -0200 (EDT) In-Reply-To: from "Julian Elischer" at Jan 23, 95 01:55:46 pm Organization: Instituto de Quimica Unicamp X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1159 Sender: hackers-owner@FreeBSD.org Precedence: bulk Julian Elischer said: > > > > > > Please, don't laugh, but I'm using pcemu to run scan or other > > > scan virus program on the dos files. > > > > I won't laugh, but I may bulge out my eyes in sheer disbelief.. :-) > > > > Jordan > Is what you are saying, that you have a version of pcemu, > that runs under FreeBSD, and allows many DOS programs to be run directly? > Yes, under X only but you can have as many pcemu running as you want. > wheredyagettit? > ftp.cs.bris.ac.uk in pub/users/hedley or users/hedley > in your experience, what programs run? > anything USEFULL? like WP or MS-WORD, etc? Almost all that fit the 8086 model and does not use VGA graphics (this should be under development) It runs wp5.1 very well, quick basic, etc, the author as list of software he tested. It is not fast, it was writen to run under any unix I've tried (AIX, Solaris, SunOS, OS/F, FreeBSD1 and 2.0) and I think a good DOS/unix hacker can improve it much. I've modified it to run under 2.0 but the author has released the latest version with the modifications. I think this is a good package to be added to FBSD distribution > > julian > > > > > From owner-freebsd-hackers Mon Jan 23 16:25:26 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id QAA24052 for hackers-outgoing; Mon, 23 Jan 1995 16:25:26 -0800 Received: from time.cdrom.com (time.cdrom.com [192.216.223.46]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id QAA24044 for ; Mon, 23 Jan 1995 16:25:25 -0800 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.9/8.6.9) with SMTP id QAA28587; Mon, 23 Jan 1995 16:24:45 -0800 X-Authentication-Warning: time.cdrom.com: Host localhost didn't use HELO protocol To: julian@tfs.com (Julian Elischer) cc: vazquez@iqm.unicamp.br, ghelmer@alpha.dsu.edu, hackers@FreeBSD.org Subject: Re: Virus Scanner In-reply-to: Your message of "Mon, 23 Jan 95 13:55:46 PST." Date: Mon, 23 Jan 1995 16:24:45 -0800 Message-ID: <28579.790907085@time.cdrom.com> From: "Jordan K. Hubbard" Sender: hackers-owner@FreeBSD.org Precedence: bulk > Is what you are saying, that you have a version of pcemu, > that runs under FreeBSD, and allows many DOS programs to be run directly? Indeed! I've even run `epsilon' under it, and it works fine.. It's actually pretty impressive, and if you play a few tricks you can even have your `D' drive map to your actual DOS partition and your `E' drive map to your CD! > in your experience, what programs run? > anything USEFULL? like WP or MS-WORD, etc? If you have the DOS versions, yes. Jordan From owner-freebsd-hackers Mon Jan 23 16:46:36 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id QAA26010 for hackers-outgoing; Mon, 23 Jan 1995 16:46:36 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id QAA26004 for ; Mon, 23 Jan 1995 16:46:35 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA10359; Mon, 23 Jan 95 17:40:30 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9501240040.AA10359@cs.weber.edu> Subject: Re: Virus Scanner To: gfoster@osmre.gov (Glen Foster) Date: Mon, 23 Jan 95 17:40:29 MST Cc: julian@tfs.com, dbaker@concorde-mail.neosoft.com, hackers@FreeBSD.org In-Reply-To: <199501232315.SAA26113@nomad.osmre.gov> from "Glen Foster" at Jan 23, 95 06:15:36 pm X-Mailer: ELM [version 2.4dev PL52] Sender: hackers-owner@FreeBSD.org Precedence: bulk > I would classify a boot block virus as a hardware virus rather than an > OS-specific one (although it will only propagate through DOS). I can see the T shirt now "Running DOS is like not wearing a condom" Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jan 23 18:03:44 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id SAA00790 for hackers-outgoing; Mon, 23 Jan 1995 18:03:44 -0800 Received: from tfs.com (mailhub.tfs.com [140.145.250.1]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id SAA00781 for ; Mon, 23 Jan 1995 18:03:43 -0800 Received: by tfs.com (smail3.1.28.1) Message-Id: From: julian@tfs.com (Julian Elischer) Subject: Re: writing bootcode; need a method To: peter@bonkers.taronga.com (Peter da Silva) Date: Mon, 23 Jan 1995 18:02:52 -0800 (PST) Cc: terry@cs.weber.edu, mmead@goof.com, hackers@FreeBSD.org In-Reply-To: <199501232329.RAA12428@bonkers.taronga.com> from "Peter da Silva" at Jan 23, 95 05:29:39 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1171 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > > Examining a BSD partition: > > > Um, it's more like this: > > > ,------------------------.----------------. > > | 3 | 4 ... | > > |---.---. | | > > | 1 | 2 | | | > > `---'---'----------------'----------------' > > It's very important to understand that slice A contains the second stage > boot and disklabel. I know you know that, Terry, but it's not intuitively > obvious. In our OSF system administration class the instructor insisted > that these were *outside* the slice and that there were special interfaces > to get them. You need to watch out for the infamous "swap on a" problem. yes.... well if we are going to correct things, it's like this: > > ,------------------------.----------------. > > | 4 | 5 ... | > > |---.---.---. | | > > | 1 | 2 | 3 | | | > > `---'---'---'------------'----------------' > > 1) BSD second stage boot. (loads label and 3rd stage) > > 2) BSD disklabel. > > 3) BSD Third stage boot. (loads kernel) > > 4) BSD slice 'a'. > > 5) BSD subsequent slices. From owner-freebsd-hackers Mon Jan 23 20:10:00 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id UAA05891 for hackers-outgoing; Mon, 23 Jan 1995 20:10:00 -0800 Received: from relay1.UU.NET (relay1.UU.NET [192.48.96.5]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id UAA05877 for ; Mon, 23 Jan 1995 20:09:54 -0800 Received: from news.cs.utexas.edu by relay1.UU.NET with SMTP id QQyaaa26423; Mon, 23 Jan 1995 23:09:47 -0500 Received: from mail.cs.utexas.edu (root@mail.cs.utexas.edu [128.83.139.10]) by news.cs.utexas.edu (8.6.9/8.6.9) with ESMTP id WAA25992; Mon, 23 Jan 1995 22:09:04 -0600 Received: from uudell.us.dell.com (uudell.us.dell.com [143.166.224.6]) by mail.cs.utexas.edu (8.6.9/8.6.9) with SMTP id WAA23328; Mon, 23 Jan 1995 22:08:57 -0600 Received: from obiwan by uudell.us.dell.com (5.67/dns1.3) with UUCP id AA07011; Tue, 24 Jan 95 04:06:30 GMT Received: by obiwan.uucp (Smail3.1.29.1 #4) id m0rWbym-0002zyC; Mon, 23 Jan 95 21:31 CST Message-Id: From: obiwan!bob@uudell.us.dell.com (Bob Willcox) Subject: Re: ep, 3C579 To: rb@gid.co.uk (Bob Bishop) Date: Mon, 23 Jan 1995 21:31:39 -0600 (CST) Cc: hackers@FreeBSD.org In-Reply-To: <3212.199501230801@seagoon.gid.co.uk> from "Bob Bishop" at Jan 23, 95 08:00:22 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 968 Sender: hackers-owner@FreeBSD.org Precedence: bulk Bob Bishop wrote: > > > Hi guys, > > On 2.0R, does the ep driver work with 3C579? > > If so, how should it be configured? I have the driver recognising the card > at 0x8000 (ie slot 8) and the interface seems to come up, but it won't pass > packets enough for ping to work (half-formed entries in the ARP cache). > > Had to configure the card on interrupt 9 and the driver on irq 10 otherwise > got complaints about mismatch from the driver. This doesn't seem right, but > I know nothing about EISA anyway. What are you using for a config file specification for your card? I can't even get as far as you have. Though the epprobe routine finds the card I haven't a clue what interface specification to use. I have tried a variety of ep? values to no avail. -- Bob Willcox ...!{rutgers|ames}!cs.utexas.edu!uudell!obiwan!bob Austin, TX or try: @uudell.us.dell.com:obiwan!bob 512-258-4224 (home), 512-838-3914 (work) From owner-freebsd-hackers Mon Jan 23 20:14:57 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id UAA06401 for hackers-outgoing; Mon, 23 Jan 1995 20:14:57 -0800 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id UAA06383 for ; Mon, 23 Jan 1995 20:14:49 -0800 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.8/8.6.6) id EAA08904; Tue, 24 Jan 1995 04:14:10 GMT From: "Rodney W. Grimes" Message-Id: <199501240414.EAA08904@gndrsh.aac.dev.com> Subject: Re: writing bootcode; need a method To: peter@bonkers.taronga.com (Peter da Silva) Date: Tue, 24 Jan 1995 04:14:09 +0000 (GMT) Cc: terry@cs.weber.edu, mmead@goof.com, hackers@FreeBSD.org In-Reply-To: <199501232329.RAA12428@bonkers.taronga.com> from "Peter da Silva" at Jan 23, 95 05:29:39 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 2095 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > > Examining a BSD partition: > > > > ,---.---.----------------.----------------. > > | 1 | 2 | 3 | 4 ... | > > `---'---'----------------'----------------' > > > > 1) BSD second stage boot. > > 2) BSD disklabel. > > 3) BSD slice 'a'. > > 4) BSD subsequent slices. > > Um, it's more like this: > > > ,------------------------.----------------. > > | 3 | 4 ... | > > |---.---. | | > > | 1 | 2 | | | > > `---'---'----------------'----------------' > > It's very important to understand that slice A contains the second stage > boot and disklabel. I know you know that, Terry, but it's not intuitively > obvious. In our OSF system administration class the instructor insisted > that these were *outside* the slice and that there were special interfaces > to get them. You need to watch out for the infamous "swap on a" problem. Though this is true for BSD, your instructor was right about OSF/1, in OSF/1 the vtoc, bootblocks and label live outside of the a partition: # uname -a OSF1 pulltime 1.2.2 osc1.2.2 b? i386 # fdisk The data for partition 0 is: MT The data for partition 1 is: MT The data for partition 2 is: MT The data for partition 3 is: systid 99, start 1, size 1094687 (534 Meg), bootid 80 beg: cyl 0/ sector 2/ head 0; end: cyl 255/ sector 255/ head 15 # vtoc The static data for the vtoc is: cyls 1086/ heads 16/ sectors 63; alt ptr 15360 alt len 2048 6 UNIX partition entries. a: start 1008, end 33263, size 32256 ( 15 Meg), flag 200, tag 2 b: start 33264, end 97775, size 64512 ( 31 Meg), flag 201, tag 4 c: start 1, end 1094687, size 1094687 (534 Meg), flag 200, tag 5 d: start 97776, end 226799, size 129024 ( 63 Meg), flag 201, tag 4 e: start 226800, end 259055, size 32256 ( 15 Meg), flag 201, tag 4 f: start 259056, end 1094687, size 835632 (408 Meg), flag 201, tag 4 -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-hackers Mon Jan 23 20:59:28 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id UAA10705 for hackers-outgoing; Mon, 23 Jan 1995 20:59:28 -0800 Received: from one.mind.net (mind.net [198.68.24.65]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id UAA10699 for ; Mon, 23 Jan 1995 20:59:26 -0800 Received: from abraxas (abraxas.mind.net [198.68.24.70]) by one.mind.net (8.6.9/8.6.9) with SMTP id UAA13361 for ; Mon, 23 Jan 1995 20:55:25 -0800 Date: Mon, 23 Jan 1995 20:55:25 -0800 Message-Id: <199501240455.UAA13361@one.mind.net> X-Sender: laird@mind.net Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: hackers@FreeBSD.org From: laird@mind.net (Alan Laird) Subject: which release X-Mailer: Sender: hackers-owner@FreeBSD.org Precedence: bulk Hello, I have been running FreeBSD 2.0.5 for about three weeks now. I am having some problems compiling programs such as lynx2-3-7 using the freebsd target. I really like the package but I am looking to reduce the time I spend building things. Is there a version of FreeBSD that you would recomend as having the *best* package support? I said *best* because I understand the nature of this project and I am very excited to have a 4.4 variant on intel hardware. But, I have been told that I need to get these packages up with linux if I can't get them up with FreeBSD. I really would rather work on FreeBSD because I like the clean nature of it vs the dense nature of Linux. Thanks for your time and keep up the great work. Alan Laird --------------------------------------------------------- Alan Laird InfoStructure laird@mind.net 611 Siskiyou Blvd. voice:503-488-1962 fax:503-488-1962 Ashland OR 97520 --------------------------------------------------------- From owner-freebsd-hackers Mon Jan 23 21:13:18 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id VAA11256 for hackers-outgoing; Mon, 23 Jan 1995 21:13:18 -0800 Received: from violet.berkeley.edu (violet.Berkeley.EDU [128.32.155.22]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id VAA11250 for ; Mon, 23 Jan 1995 21:13:17 -0800 Received: by violet.berkeley.edu (8.6.8/1.33r) id VAA22750; Mon, 23 Jan 1995 21:13:14 -0800 Date: Mon, 23 Jan 1995 21:13:14 -0800 From: jkh@violet.berkeley.edu (Jordan K. Hubbard) Message-Id: <199501240513.VAA22750@violet.berkeley.edu> To: hackers@FreeBSD.org Subject: Let these people know how you feel! Sender: hackers-owner@FreeBSD.org Precedence: bulk Path: agate!howland.reston.ans.net!ix.netcom.com!netnews From: puzzle@ix.netcom.com (James Leslie) Newsgroups: comp.unix.bsd Subject: BSD/Novell Integration Date: 24 Jan 1995 03:29:17 GMT Organization: Netcom Lines: 28 Distribution: world Message-ID: <3g1s6d$779@ixnews2.ix.netcom.com> NNTP-Posting-Host: ix-sj14-27.ix.netcom.com BSD Folks: We're thinking about doing a port of our SoftNet Utilities software to the BSD (on Intel) environment and we need some honest, quality feedback. Basically, our SoftNet Utilities software allows a BSD UNIX system to ALSO function as a Novell 3.12 compatible server. It would be for anyone trying to integrate BSD platforms into existing Novell networks. Currently the software has been ported to 8 other UNIX enviroments and we're starting to get inquiries from BSD users too. We want to take this issue to the BSD community for input. Do you think that a port would be helpful? If so, why? (a Yes or No with a short explanation would be appreciated.) Please address your comments to: email: info@puzzle.com or Puzzle Systems Corporation Attn: Product Marketing 16360 Monterey Rd., Ste. 250 Morgan Hill, CA 95037 U.S.A. (408) 779-9909 (408) 779-5058 (FAX) From owner-freebsd-hackers Mon Jan 23 21:39:50 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id VAA12815 for hackers-outgoing; Mon, 23 Jan 1995 21:39:50 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id VAA12793; Mon, 23 Jan 1995 21:39:14 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id QAA10618; Tue, 24 Jan 1995 16:36:02 +1100 Date: Tue, 24 Jan 1995 16:36:02 +1100 From: Bruce Evans Message-Id: <199501240536.QAA10618@godzilla.zeta.org.au> To: wpaul@skynet.ctr.columbia.edu, wraith@csd.uwm.edu Subject: Re: Is this a bug?!? Cc: hackers@FreeBSD.org, questions@FreeBSD.org Sender: hackers-owner@FreeBSD.org Precedence: bulk >> I just finished upgrading one of my 'bsd boxes from a dx2-50 ISA to a dx2-66 >> VLB motherboard. Problems: >> >> I now seem to be unable to issue a Ctrl-Alt-Del (system >> just beeps at me each time I hit the combo). >> >> 'shutdown' results in a kernel panic: >> >> panic: b_to_q to a clist with no reserved cblocks This should be fixed in -current. There is another bug instead :-[. >I've been able to reliably reproduce this panic message on my system now >that I've started looking into actually using /dev/console for something. It is easier to reproduce on your serial console. syscons used to avoid the problem. >that writing to /dev/ttyv0 actually causes the kernel to go from >write(), to vn_write(), to ffsspec_write(), to spec_write(), to cn_write(), >to scwrite(), to ttwrite() and then to b_to_q() and a panic. The This layering seems excessive. One of the benchmarks in Larry Mcvoy's benchmark suite tests "syscall" overhead by writing a byte to stdout. FreeBSD is about 4 times slower than Linux for this benchmark, perhaps because of all the layers. The benchmark doesn't really test syscalls or i/o, but it's good for testing cdev overheads. >vn->v_un->vu_specinfo->si_rdev in spec_write() was 0x00000000 where >it probably should have been 0x0c000000 (or something like that -- >basically, 0x00000000 is major 0/minor 0 where it should have been >major 12/minor 0 (for syscons) instead). 0/0 is correct for the console. It gets translated to 12/0 in cons.c. The current version of syscons, and all versions of sio, cannot tell if they are working with the 0/0 device, and this causes problems when the 12/0 device is closed while the 0/0 device is open or vice versa. I fixed this, but now the process group info for the 12/0 device doesn't go away when the 12/0 device is closed, and TIOCSTTY fails in login_tty(). Bruce From owner-freebsd-hackers Mon Jan 23 22:03:15 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id WAA15096 for hackers-outgoing; Mon, 23 Jan 1995 22:03:15 -0800 Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id WAA15088 for ; Mon, 23 Jan 1995 22:03:12 -0800 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.9/8.6.9) id WAA17875; Mon, 23 Jan 1995 22:03:06 -0800 Date: Mon, 23 Jan 1995 22:03:06 -0800 Message-Id: <199501240603.WAA17875@silvia.HIP.Berkeley.EDU> To: hackers@FreeBSD.org Subject: cvs commit From: asami@cs.berkeley.edu (Satoshi Asami) Sender: hackers-owner@FreeBSD.org Precedence: bulk cvs commit said something like "ci warning: missing message for -m option" and started asking for messages using the ">>" prompt after I typed "!" in response to the "a)bort, c)ontinue, e)dit, !)reuse this message unchanged for remaining dirs" question during a multi-directory commit. Anyone know why? Satoshi From owner-freebsd-hackers Mon Jan 23 23:02:12 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id XAA18709 for hackers-outgoing; Mon, 23 Jan 1995 23:02:12 -0800 Received: from ns.gte.com (ns.gte.com [132.197.8.9]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id XAA18703 for ; Mon, 23 Jan 1995 23:02:10 -0800 Received: from bunny.gte.com by ns.gte.com (5.65c/IDA-1.4.4) id AA01809; Tue, 24 Jan 1995 02:00:09 -0500 Received: by bunny.gte.com (8.6.9/GTEL2.19) id CAA28324; Tue, 24 Jan 1995 02:01:32 -0500 Received: from localhost by genesis.nred.ma.us (8.3/genesis0.0) id XAA03010; Mon, 23 Jan 1995 23:45:53 -0800 Date: Mon, 23 Jan 1995 23:45:53 -0800 From: steve2@genesis.nred.ma.us (Steve Gerakines) Message-Id: <199501240745.XAA03010@genesis.nred.ma.us> To: freebsd-hackers@FreeBSD.org Subject: Floppy tape probe patch Sender: hackers-owner@FreeBSD.org Precedence: bulk Here's a set of patches against -current that should fix the probe issues that were brought up. The "output in input" messages should be gone and people without tape drives should not see any drive activity. Test it out and let me know how it goes. I am mostly interested in hearing from the people that said it caused problems for them. Two other things. Joerg is correct. The floppy tape is using unit 0 to address the drive in the GENERIC kernel. id_unit was always used to address the drive, while the id_physid number was used only to identify the tape drive config entry. Also, the ft driver brought out the output on input messages because it is polling for a seek or recalibrate completion by sending sense interrupt commands to the fdc. The fd driver doesn't see them because it doesn't poll, it just waits a long time and hopes that it finished. This is impractical for ft because the the probe would take too long. Although I'm glad the messages in the fd driver pointed out what was happening, as far as I can tell ft wasn't really doing anything wrong. Seems to me fd is reporting a bit too much for a non-debug mode. - Steve steve2@genesis.nred.ma.us ---- snip snip snip ---- *** fd.c.orig Mon Jan 23 22:20:24 1995 --- fd.c Mon Jan 23 22:22:44 1995 *************** *** 259,265 **** int ftioctl(dev_t, int, caddr_t, int, struct proc *); int ftdump(dev_t); int ftsize(dev_t); ! int ftattach(struct isa_device *, struct isa_device *); #endif /* autoconfig functions */ --- 259,265 ---- int ftioctl(dev_t, int, caddr_t, int, struct proc *); int ftdump(dev_t); int ftsize(dev_t); ! int ftattach(struct isa_device *, struct isa_device *, int); #endif /* autoconfig functions */ *************** *** 535,541 **** fdcu_t fdcu = dev->id_unit; fdc_p fdc = fdc_data + fdcu; fd_p fd; ! int fdsu, st0, st3, i; struct isa_device *fdup; int ic_type = 0; --- 535,541 ---- fdcu_t fdcu = dev->id_unit; fdc_p fdc = fdc_data + fdcu; fd_p fd; ! int fdsu, st0, st3, i, unithasfd; struct isa_device *fdup; int ic_type = 0; *************** *** 578,584 **** #if NFT > 0 /* If BIOS says no floppy, or > 2nd device */ /* Probe for and attach a floppy tape. */ ! if (ftattach(dev, fdup)) continue; if (fdsu < DRVS_PER_CTLR) fd->type = NO_TYPE; --- 578,590 ---- #if NFT > 0 /* If BIOS says no floppy, or > 2nd device */ /* Probe for and attach a floppy tape. */ ! /* Tell FT if there was already a disk */ ! /* with this unit number found. */ ! ! unithasfd = 0; ! if (fdu < NFD && fd->type != NO_TYPE) ! unithasfd = 1; ! if (ftattach(dev, fdup, unithasfd)) continue; if (fdsu < DRVS_PER_CTLR) fd->type = NO_TYPE; *** ft.c.orig Mon Jan 23 21:11:40 1995 --- ft.c Mon Jan 23 22:35:11 1995 *************** *** 19,24 **** --- 19,27 ---- * ft.c - QIC-40/80 floppy tape driver * $Id: ft.c,v 1.15 1994/12/04 03:10:09 jkh Exp $ * + * 01/19/95 ++sg + * Cleaned up recalibrate/seek code at attach time for FreeBSD 2.x. + * * 06/07/94 v0.9 ++sg * Tape stuck on segment problem should be gone. Re-wrote buffering * scheme. Added support for drives that do not automatically perform *************** *** 432,439 **** * Probe/attach floppy tapes. */ int ! ftattach(isadev, fdup) struct isa_device *isadev, *fdup; { fdcu_t fdcu = isadev->id_unit; /* fdc active unit */ fdc_p fdc = fdc_data + fdcu; /* pointer to controller structure */ --- 435,443 ---- * Probe/attach floppy tapes. */ int ! ftattach(isadev, fdup, unithasfd) struct isa_device *isadev, *fdup; + int unithasfd; { fdcu_t fdcu = isadev->id_unit; /* fdc active unit */ fdc_p fdc = fdc_data + fdcu; /* pointer to controller structure */ *************** *** 490,496 **** --- 494,505 ---- /* * FT_INSIGHT - insight style + * + * Since insight requires turning the drive motor on, we will not + * perform this probe if a floppy drive was already found with the + * the given unit and controller. */ + if (unithasfd) goto out; tape_start(ftu, 1); if (tape_status(ftu) >= 0) { ft->type = FT_INSIGHT; *************** *** 1469,1483 **** case FTCMD_RECAL: case FTCMD_SEEK: for (retries = 0; retries < 10000; retries++) { out_fdc(fdcu, NE7CMD_SENSEI); st0 = in_fdc(fdcu); pcn = in_fdc(fdcu); if (st0 & 0x20) { ft->sts_wait = FTSTS_INTERRUPT; ft->pcn = pcn; goto intrdone; } - DELAY(100); } break; } --- 1478,1493 ---- case FTCMD_RECAL: case FTCMD_SEEK: for (retries = 0; retries < 10000; retries++) { + DELAY(100); out_fdc(fdcu, NE7CMD_SENSEI); st0 = in_fdc(fdcu); + if ((st0 & 0xc0) == 0x80) continue; pcn = in_fdc(fdcu); if (st0 & 0x20) { ft->sts_wait = FTSTS_INTERRUPT; ft->pcn = pcn; goto intrdone; } } break; } *************** *** 1664,1669 **** --- 1674,1680 ---- ft_p ft = &ft_data[ftu]; fdc_p fdc = ft->fdc; int s, mbits; + static int mbmotor[] = { FDO_MOEN0, FDO_MOEN1, FDO_MOEN2, FDO_MOEN3 }; s = splbio(); DPRT(("tape_start start\n")); *************** *** 1673,1682 **** (void)ftintr_wait(ftu, FTCMD_RESET, hz/10); /* raise reset, enable DMA, motor on if needed */ ! if (motor) ! mbits = (!ftu) ? FDO_MOEN0 : FDO_MOEN1; ! else ! mbits = 0; outb(fdc->baseport+FDOUT, FDO_FRST | FDO_FDMAEN | mbits); (void)ftintr_wait(ftu, FTCMD_RESET, hz/10); --- 1684,1692 ---- (void)ftintr_wait(ftu, FTCMD_RESET, hz/10); /* raise reset, enable DMA, motor on if needed */ ! mbits = ftu & 3; ! if (motor && ftu < 4) ! mbits |= mbmotor[ftu]; outb(fdc->baseport+FDOUT, FDO_FRST | FDO_FDMAEN | mbits); (void)ftintr_wait(ftu, FTCMD_RESET, hz/10); ---- EOF EOF EOF ---- From owner-freebsd-hackers Mon Jan 23 23:37:24 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id XAA19119 for hackers-outgoing; Mon, 23 Jan 1995 23:37:24 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id XAA19113 for ; Mon, 23 Jan 1995 23:37:15 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id SAA12857; Tue, 24 Jan 1995 18:32:36 +1100 Date: Tue, 24 Jan 1995 18:32:36 +1100 From: Bruce Evans Message-Id: <199501240732.SAA12857@godzilla.zeta.org.au> To: julian@tfs.com, peter@bonkers.taronga.com Subject: Re: writing bootcode; need a method Cc: hackers@FreeBSD.org, mmead@goof.com, terry@cs.weber.edu Sender: hackers-owner@FreeBSD.org Precedence: bulk >well if we are going to correct things, it's like this: >> > ,------------------------.----------------. >> > | 4 | 5 ... | >> > |---.---.---. | | >> > | 1 | 2 | 3 | | | >> > `---'---'---'------------'----------------' >> > 1) BSD second stage boot. (loads label and 3rd stage) >> > 2) BSD disklabel. >> > 3) BSD Third stage boot. (loads kernel) >> > 4) BSD slice 'a'. >> > 5) BSD subsequent slices. I usually call 1) and 3) the first stage boot. We need a stage after that soon. I want it to be in /kernel0. There is also 6) BSD bad144 table at the end of what the disklabel and/or the drivers say is the end of the disk (the wrong place). On "i386" systems there are also the DOSpartitions, which can be laid out as something between a ternary and a quaternary tree and can have slightly complicated overlaps with each other and very complicated/ incoherent overlaps with the BSD partitions, especially on misconfigured systems. [Picture omitted due to lack of time, space and drawing capabilities.] Bruce From owner-freebsd-hackers Tue Jan 24 00:18:00 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id AAA20069 for hackers-outgoing; Tue, 24 Jan 1995 00:18:00 -0800 Received: from campino.informatik.rwth-aachen.de (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id AAA20063 for ; Tue, 24 Jan 1995 00:17:50 -0800 Received: from gilberto.physik.rwth-aachen.de by campino.informatik.rwth-aachen.de (4.1/campino-6) id AA06844; Tue, 24 Jan 95 09:17:33 +0100 Received: by gilberto.physik.rwth-aachen.de (KAA00162); Tue, 24 Jan 1995 10:24:06 +0100 Date: Tue, 24 Jan 1995 10:24:06 +0100 From: "Christoph P. Kukulies" Message-Id: <199501240924.KAA00162@gilberto.physik.rwth-aachen.de> To: freebsd-hackers@freefall.cdrom.com Subject: disklabel (1.1.5.1), partitions Sender: hackers-owner@FreeBSD.org Precedence: bulk I had disk problems on 'gil' recently (hopefully solved) - reformatted a Fuji M2694S using SCSICNTL. I was wondering about the following when disklabeling again: dmesg told me: 2117025 1819 cyl 15 heads 77 sec Using these figures in a disktab entry resulted in a warning saying that partitions c,d,e exceeded end of disk. (I made them p[cde]#2117025). So I reduced them to what 15 * 77 * 1819 calculates to, namely 2100945 and disklabel kept silent. Did I give away some sectors ? --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de FreeBSD blues 2.1.0-Development FreeBSD 2.1.0-Development #1: Wed Jan 18 10:42:31 1995 kuku@blues:/usr/src/sys/compile/BLUES i386 From owner-freebsd-hackers Tue Jan 24 01:04:04 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id BAA22208 for hackers-outgoing; Tue, 24 Jan 1995 01:04:04 -0800 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id BAA22198 for ; Tue, 24 Jan 1995 01:03:55 -0800 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.8/8.6.6) id JAA09359; Tue, 24 Jan 1995 09:03:27 GMT From: "Rodney W. Grimes" Message-Id: <199501240903.JAA09359@gndrsh.aac.dev.com> Subject: Re: which release To: laird@mind.net (Alan Laird) Date: Tue, 24 Jan 1995 09:03:27 +0000 (GMT) Cc: hackers@FreeBSD.org In-Reply-To: <199501240455.UAA13361@one.mind.net> from "Alan Laird" at Jan 23, 95 08:55:25 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1071 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > Hello, > > I have been running FreeBSD 2.0.5 for about three weeks now. I am having > some problems compiling programs such as lynx2-3-7 using the freebsd target. > I really like the package but I am looking to reduce the time I spend > building things. Is there a version of FreeBSD that you would recomend as > having the *best* package support? I said *best* because I understand the > nature of this project and I am very excited to have a 4.4 variant on intel > hardware. But, I have been told that I need to get these packages up with > linux if I can't get them up with FreeBSD. I really would rather work on > FreeBSD because I like the clean nature of it vs the dense nature of Linux. Did you try getting the port specifically done for FreeBSD, ie: freebsd.cdrom.com:/pub/FreeBSD/ports/net/lynx That port contains a 19kb patchfile that should probably just your porting work for you. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-hackers Tue Jan 24 01:25:55 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id BAA22947 for hackers-outgoing; Tue, 24 Jan 1995 01:25:55 -0800 Received: from linux4nn.iaf.nl (root@linux4nn.iaf.nl [193.67.144.34]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id BAA22934 for ; Tue, 24 Jan 1995 01:25:46 -0800 Received: from uni4nn.iaf.nl (root@uni4nn.iaf.nl [193.67.144.33]) by linux4nn.iaf.nl (8.6.9/8.6.9) with SMTP id KAA00332; Tue, 24 Jan 1995 10:28:34 +0100 Received: by uni4nn.iaf.nl with UUCP id AA25084 (5.67b/IDA-1.5); Tue, 24 Jan 1995 10:24:01 +0200 Received: by iafnl.iaf.nl with UUCP id AA00815 (5.65c/IDA-1.4.4); Mon, 23 Jan 1995 21:52:42 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.6.8/8.6.6) id UAA00595; Mon, 23 Jan 1995 20:44:45 +0100 From: Wilko Bulte Message-Id: <199501231944.UAA00595@yedi.iaf.nl> Subject: Re: Need jumper settings for WD8003E - anyone? To: karl@bagpuss.demon.co.uk (Karl Strickland) Date: Mon, 23 Jan 1995 20:44:44 +1596657 (MET) Cc: freebsd-hackers@freefall.cdrom.com In-Reply-To: <199501230101.BAA09216@bagpuss.demon.co.uk> from "Karl Strickland" at Jan 23, 95 01:01:40 am X-Mailer: ELM [version 2.4 PL22] Content-Type: text Content-Length: 1025 Sender: hackers-owner@FreeBSD.org Precedence: bulk W1 pin 1-2 zero wait when installed (default=out) W1 pin 3-4, 5-6, 9-10 IO adr 0x280 (default) 5-6, 9-10 IO adr 0x2a0 3-4, 9-10 2c0 9-10 2e0 3-4, 5-6, 7-8 300 5-6, 7-8 320 3-4, 7-8 340 W2 pin 1-2 IRQ7 3-4 IRQ6 5-6 IRQ5 7-8 IRQ4 9-10 IRQ3 11-12 IRQ2 (3 is default, only one jumper at a time) W3 all pins jumpered for BNC/Thinwire, all out for AUI W4 1-2 removed for thin ethernet IEEE802.3, in for Ethernet version one on AUI interface W5 1-2 installed for standard 185 m cable length, out for 300m extended length Hope this helps Wilko _ __________________________________________________________________________ | / o / / _ Wilko Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Private FreeBSD site - Arnhem - The Netherlands -------------------------------------------------------------------------------- From owner-freebsd-hackers Tue Jan 24 02:35:56 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id CAA27801 for hackers-outgoing; Tue, 24 Jan 1995 02:35:56 -0800 Received: from eros.britain.eu.net (eros.Britain.EU.net [192.91.199.2]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id CAA27790 for ; Tue, 24 Jan 1995 02:35:47 -0800 Received: from sixnine.gid.co.uk by eros.britain.eu.net with UUCP id ; Tue, 24 Jan 1995 10:34:21 +0000 Received: by gid.co.uk (smail2.5) id AA00585; Tue, 24 Jan 95 08:53:11 GMT Message-Id: <8017.199501240818@seagoon.gid.co.uk> Received: from [192.9.200.25] by seagoon.gid.co.uk; Tue, 24 Jan 1995 08:18:07 GMT PP-warning: Illegal Via field on preceding line X-Sender: rb@seagoon.gid.co.uk Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 24 Jan 1995 08:17:12 +0000 To: bob From: rb@gid.co.uk (Bob Bishop) Subject: Re: ep, 3C579 Cc: hackers@FreeBSD.org Sender: hackers-owner@FreeBSD.org Precedence: bulk >Bob Bishop wrote: >> >> >> Hi guys, >> >> On 2.0R, does the ep driver work with 3C579? >> >> If so, how should it be configured? I have the driver recognising the card >> at 0x8000 (ie slot 8) and the interface seems to come up, but it won't pass >> packets enough for ping to work (half-formed entries in the ARP cache). >> >> Had to configure the card on interrupt 9 and the driver on irq 10 otherwise >> got complaints about mismatch from the driver. This doesn't seem right, but >> I know nothing about EISA anyway. > >What are you using for a config file specification for your card? I can't >even get as far as you have. Though the epprobe routine finds the card >I haven't a clue what interface specification to use. I have tried >a variety of ep? values to no avail. > > >-- >Bob Willcox ...!{rutgers|ames}!cs.utexas.edu!uudell!obiwan!bob >Austin, TX or try: @uudell.us.dell.com:obiwan!bob >512-258-4224 (home), 512-838-3914 (work) I'm setting (via /kernel -c): port ep0 0x8000 You need to set port to 0xN000 where the card is in slot N. Driver handling of the the irq seems wrong at present. I'm working with Andres to test a fix for the driver. Watch this space... -- Bob Bishop (01734) 774017 international code +44 1734 rb@gid.co.uk fax (01734) 894254 between 0800 and 1800 UK From owner-freebsd-hackers Tue Jan 24 03:40:20 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id DAA28612 for hackers-outgoing; Tue, 24 Jan 1995 03:40:20 -0800 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id DAA28593 for ; Tue, 24 Jan 1995 03:39:32 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA28709; Tue, 24 Jan 1995 12:32:59 +0100 Received: by sax.sax.de (8.6.9/8.6.9-s1) with UUCP id MAA19630 for freebsd-hackers@FreeBSD.org; Tue, 24 Jan 1995 12:32:58 +0100 Received: by bonnie.tcd-dresden.de (8.6.8/8.6.6) id LAA21122; Tue, 24 Jan 1995 11:57:18 +0100 From: j@uriah.sax.de (J Wunsch) Message-Id: <199501241057.LAA21122@bonnie.tcd-dresden.de> Subject: Re: Floppy tape probe patch To: steve2@genesis.nred.ma.us (Steve Gerakines) Date: Tue, 24 Jan 1995 11:57:17 +0100 (MET) Cc: freebsd-hackers@FreeBSD.org In-Reply-To: <199501240745.XAA03010@genesis.nred.ma.us> from "Steve Gerakines" at Jan 23, 95 11:45:53 pm X-Phone: +49-351-8141 137 Reply-To: joerg_wunsch@uriah.sax.de X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1428 Sender: hackers-owner@FreeBSD.org Precedence: bulk As Steve Gerakines wrote: | | Here's a set of patches against -current that should fix the probe | issues that were brought up. The "output in input" messages should be | gone and people without tape drives should not see any drive activity. Good news! | Also, the ft driver brought out the output on input messages because | it is polling for a seek or recalibrate completion by sending sense | interrupt commands to the fdc. The fd driver doesn't see them because | it doesn't poll, it just waits a long time and hopes that it finished. | This is impractical for ft because the the probe would take too long. Hmmmm. Perhaps fd should also poll. On the other hand, polling the FDC is dangerous (the danger is only being eliminated by in_fdc() watching thoroughly for the ready-for-input bit), since many FDC's tend to lock up if someone requests ``unusual'' things (e.g. SENSEI where no interrupt happened) from them. | Although I'm glad the messages in the fd driver pointed out what was | happening, as far as I can tell ft wasn't really doing anything wrong. | Seems to me fd is reporting a bit too much for a non-debug mode. It should be made less noisy, and will be before 2.1 gets shipped. -- cheers, J"org work: --- no longer --- private: joerg_wunsch@uriah.sax.de Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Jan 24 04:03:46 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id EAA29142 for hackers-outgoing; Tue, 24 Jan 1995 04:03:46 -0800 Received: from campino.informatik.rwth-aachen.de (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id EAA29130 for ; Tue, 24 Jan 1995 04:03:43 -0800 Received: from gilberto.physik.rwth-aachen.de by campino.informatik.rwth-aachen.de (4.1/campino-6) id AA08915; Tue, 24 Jan 95 13:03:20 +0100 Received: by gilberto.physik.rwth-aachen.de (NAA00295); Tue, 24 Jan 1995 13:09:52 +0100 Date: Tue, 24 Jan 1995 13:09:52 +0100 From: "Christoph P. Kukulies" Message-Id: <199501241209.NAA00295@gilberto.physik.rwth-aachen.de> To: freebsd-hackers@freefall.cdrom.com Subject: old filesystems (1.1.0 ) not mountable? Sender: hackers-owner@FreeBSD.org Precedence: bulk I moved one machine to 2.0-current today, saved some user trees and important files to the second disk, installed 2.0 on the first disk and found that I cannot mount the old disk. Is it impossible or is there a work around? --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de FreeBSD blues 2.1.0-Development FreeBSD 2.1.0-Development #1: Wed Jan 18 10:42:31 1995 kuku@blues:/usr/src/sys/compile/BLUES i386 From owner-freebsd-hackers Tue Jan 24 05:19:42 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id FAA00970 for hackers-outgoing; Tue, 24 Jan 1995 05:19:42 -0800 Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id FAA00964 for ; Tue, 24 Jan 1995 05:19:40 -0800 Received: by dg-rtp.dg.com (5.4R2.01/dg-rtp-v02) id AA02850; Tue, 24 Jan 1995 08:18:59 -0500 Received: (rivers@localhost) by ponds.UUCP (8.6.9/8.6.5) id GAA11152; Tue, 24 Jan 1995 06:03:15 -0500 Date: Tue, 24 Jan 1995 06:03:15 -0500 From: Thomas David Rivers Message-Id: <199501241103.GAA11152@ponds.UUCP> To: freebsd-hackers@freefall.cdrom.com, jkh@time.cdrom.com Subject: 3c509 probs... Sender: hackers-owner@FreeBSD.org Precedence: bulk Jordan - I discovered this while trying to catch up on 1800+ pieces of mail (I've been busy with work lately.) Anyway, I find that with my 3c509 at work - if I boot DOS/Windows, then reboot into FreeBSD, FreeBSD does not recognize the 3c509. If I physically turn the machine off, FreeBSD does recognize the 3c509. Thus, I think there is possibly a probe problem here... - Dave Rivers - (p.s. this is with FreeBSD 2.0R, using the OS/2 boot manager to bounce between FreeBSD, OS/2, DOS/Windows.) > > Jordan, > We've been missing each other's telephone calls. This is in > regard to a problem that I'm having at work, with the current re- > lease of BSD from Walnut Creek. The probe only occasionally rec- > ognizes my 3C509-16-TP card. Even when it finds the board, it > never works properly. > > The port light on my hub never lights during the BSD boot. > When the probe has been successful finding the board, I've con- > figured the device with ifconfig and pinged another box on the > LAN. This causes the hub port light to blink. Afterwards, ping > fails, and the light stays off. > > I've used "/kernel -c" during boot to disable all devices > except my console, harddrive, and ethernet board. I had the same > results, except that the board was found consistently. > > I've swapped boards, cables, and ports. Used different base > addresses and interrupts. My LAN consists of two other boxes > running Linux with 3C509-16-TP cards. One is a router using two > 509 cards. The two Linux machines perform perfectly. > > The board is set to use base address 0x300, and interrupt > 10. > > The ethernet connection is vital to a project that I am > working on. I need to build a box that will analyze MPEG data > being transported across tcp LANS. I plan to build my software > on top of Tcpdump and BSD to do this. > > I would appreciate any help. Thank you. > > - Bill > -- > _________________________________ > Bill Smith > bill%saco@telesciences.com > twwells!telesci!saco!bill > > From owner-freebsd-hackers Tue Jan 24 05:38:43 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id FAA01374 for hackers-outgoing; Tue, 24 Jan 1995 05:38:43 -0800 Received: from dataplex.net (SHARK.DATAPLEX.NET [199.183.109.241]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id FAA01366 for ; Tue, 24 Jan 1995 05:38:38 -0800 Received: from [199.183.109.242] by dataplex.net with SMTP (MailShare 1.0b8); Tue, 24 Jan 1995 07:13:22 -0600 X-Sender: wacky@mail.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 24 Jan 1995 07:13:23 -0600 To: hackers@FreeBSD.org From: rkw@dataplex.net (Richard Wackerbarth) Subject: Make world Sender: hackers-owner@FreeBSD.org Precedence: bulk Personally, I feel that the "make" process is far from adequate. IMHO, I should be able to doo all of the following: 1) Compile a new system and make floppies, etc. for it on a running system WITHOUT altering the running enviornment of the host doing the work. 2) Alter some files in the tree and do a single "make all" at the top of the tree to recompile everything affected. 3) Not have "make all" ever do rebuilds if it follows another "make all" 4) (Eventually) Be able to cross compile for another type of system. 5) Be able to build similar kernels without having duplicate object modules. (Like "make links", but smarter -- IOW, folding of common options) Items 1 & 4 help "upgrade" from one release to the next. Items 2 & 3 reduce the "cost" of installing updates. Item 5 saves "time and space" There is still one problem for which I have no solution. This is caused by delays between updates and compiles. Assume that I have a correct source tree on day zero. On day two, I compile it and have a correct binary tree. All is well, so far. However, on day three, I learn that someone made a correction on day one. If I replace the source with one dated "3", make works just fine. However, my update procedure does not realize that I have the correct file. If instead, I replace the source with the one properly dated "1", make thinks that the binary (dated "2") is correct when, in fact, it is not. Is there any interest in modifying the system build procedure toward any of the goals mentioned? If so, I am willing to help. Does anyone have a good solution to the synchronization problem? From owner-freebsd-hackers Tue Jan 24 08:09:17 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id IAA00226 for hackers-outgoing; Tue, 24 Jan 1995 08:09:17 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id IAA00220 for ; Tue, 24 Jan 1995 08:09:12 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id DAA05264; Wed, 25 Jan 1995 03:08:21 +1100 Date: Wed, 25 Jan 1995 03:08:21 +1100 From: Bruce Evans Message-Id: <199501241608.DAA05264@godzilla.zeta.org.au> To: freebsd-hackers@freefall.cdrom.com, kuku@gilberto.physik.rwth-aachen.de Subject: Re: disklabel (1.1.5.1), partitions Sender: hackers-owner@FreeBSD.org Precedence: bulk >2117025 1819 cyl 15 heads 77 sec >Using these figures in a disktab entry resulted in a warning saying that >partitions c,d,e exceeded end of disk. (I made them p[cde]#2117025). >So I reduced them to what 15 * 77 * 1819 calculates to, namely 2100945 >and disklabel kept silent. >Did I give away some sectors ? According to /etc/disktab, you could have used `su#2117025' in the drive entry in /etc/disktab to use the sectors at the end. There is apparently no way to see or set the correct number of sectors using disklabel -e or sysinstall. Bruce From owner-freebsd-hackers Tue Jan 24 08:11:13 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id IAA00335 for hackers-outgoing; Tue, 24 Jan 1995 08:11:13 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id IAA00324 for ; Tue, 24 Jan 1995 08:11:09 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id CAA04957; Wed, 25 Jan 1995 02:49:03 +1100 Date: Wed, 25 Jan 1995 02:49:03 +1100 From: Bruce Evans Message-Id: <199501241549.CAA04957@godzilla.zeta.org.au> To: bde@zeta.org.au, peter@bonkers.taronga.com Subject: Re: writing bootcode; need a method Cc: hackers@FreeBSD.org, julian@tfs.com, mmead@goof.com, terry@cs.weber.edu Sender: hackers-owner@FreeBSD.org Precedence: bulk >As for /kernel0, what's wrong with following tradition and calling it /boot? What tradition? I remember pribootfd (?) and and out 20 specialized partitions on my first Xenix system, but I'm not familiar with boot traditions. FreeBSD already has /usr/mdec/boot. Bruce From owner-freebsd-hackers Tue Jan 24 08:35:41 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id IAA01018 for hackers-outgoing; Tue, 24 Jan 1995 08:35:41 -0800 Received: from UUCP-GW.CC.UH.EDU (root@UUCP-GW.CC.UH.EDU [129.7.1.11]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id IAA01002 for ; Tue, 24 Jan 1995 08:35:34 -0800 Received: from Taronga.COM by UUCP-GW.CC.UH.EDU with UUCP id AA27855 (5.67a/IDA-1.5); Tue, 24 Jan 1995 08:47:53 -0600 Received: by bonkers.taronga.com (smail2.5p) id AA13868; 24 Jan 95 08:37:51 CST (Tue) Received: from localhost (localhost [127.0.0.1]) by bonkers.taronga.com (8.6.8/8.6.6) with SMTP id IAA13865; Tue, 24 Jan 1995 08:37:50 -0600 Message-Id: <199501241437.IAA13865@bonkers.taronga.com> X-Authentication-Warning: bonkers.taronga.com: Host localhost didn't use HELO protocol To: Bruce Evans Cc: julian@tfs.com, hackers@FreeBSD.org, mmead@goof.com, terry@cs.weber.edu Subject: Re: writing bootcode; need a method In-Reply-To: Your message of "Tue, 24 Jan 95 18:32:36 +1100." <199501240732.SAA12857@godzilla.zeta.org.au> X-Mailer: exmh version 1.4.1 7/21/94 Date: Tue, 24 Jan 1995 08:37:46 -0600 From: Peter da Silva Sender: hackers-owner@FreeBSD.org Precedence: bulk > 6) BSD bad144 table at the end of what the disklabel and/or the drivers > say is the end of the disk (the wrong place). Only if you have bad144 working (which means small WD disks: my Maxtor 4380s never did work with it) . As for /kernel0, what's wrong with following tradition and calling it /boot? From owner-freebsd-hackers Tue Jan 24 08:37:47 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id IAA01089 for hackers-outgoing; Tue, 24 Jan 1995 08:37:47 -0800 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id IAA01081 for ; Tue, 24 Jan 1995 08:37:39 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA09219; Tue, 24 Jan 1995 17:02:21 +0100 Received: by sax.sax.de (8.6.9/8.6.9-s1) with UUCP id RAA20645 for freebsd-hackers@freebsd.org; Tue, 24 Jan 1995 17:02:21 +0100 Received: by bonnie.tcd-dresden.de (8.6.8/8.6.6) id QAA09408; Tue, 24 Jan 1995 16:46:50 +0100 From: j@uriah.sax.de (J Wunsch) Message-Id: <199501241546.QAA09408@bonnie.tcd-dresden.de> Subject: Re: Virus Scanner To: vazquez@iqm.unicamp.br (Pedro A M Vazquez) Date: Tue, 24 Jan 1995 16:46:50 +0100 (MET) Cc: freebsd-hackers@FreeBSD.org (FreeBSD hackers) In-Reply-To: <199501232218.UAA00342@kalypso.iqm.unicamp.br> from "Pedro A M Vazquez" at Jan 23, 95 08:18:30 pm X-Phone: +49-351-8141 137 Reply-To: joerg_wunsch@uriah.sax.de X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1280 Sender: hackers-owner@FreeBSD.org Precedence: bulk As Pedro A M Vazquez wrote: | | I've modified it to run under 2.0 but the author has released the | latest version with the modifications. | I think this is a good package to be added to FBSD distribution Basically agreed. A few problems i've been noticing so far: . The emulator shouldn't say goodbye if it enters an unknown instruction -- a real 8086 also continued to work in this case. The point is that some programs tend to execute known-to-be-286 instr's to see which CPU they run on. . A few 8086 instr's are missing (for no good reason, e.g. DAS). . The keymap handling (deducing the scan code from what XLookupString() reports) is bogus. The bogosity becomes already apparent when looking at the workarounds he hooked into the source for the UK keyboard, but considering things like a german or more weird keyboard, another customization method is needed. I've created something that allows a keystring -> scancode mapping out of the .pcemurc file. For all the above, i will yet have to contact the original author though. -- cheers, J"org work: --- no longer --- private: joerg_wunsch@uriah.sax.de Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Jan 24 08:39:48 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id IAA01126 for hackers-outgoing; Tue, 24 Jan 1995 08:39:48 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id IAA01120 for ; Tue, 24 Jan 1995 08:39:47 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA12193; Tue, 24 Jan 95 09:33:32 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9501241633.AA12193@cs.weber.edu> Subject: Re: writing bootcode; need a method To: bde@zeta.org.au (Bruce Evans) Date: Tue, 24 Jan 95 9:33:31 MST Cc: julian@tfs.com, peter@bonkers.taronga.com, hackers@FreeBSD.org, mmead@goof.com In-Reply-To: <199501240732.SAA12857@godzilla.zeta.org.au> from "Bruce Evans" at Jan 24, 95 06:32:36 pm X-Mailer: ELM [version 2.4dev PL52] Sender: hackers-owner@FreeBSD.org Precedence: bulk > I usually call 1) and 3) the first stage boot. We need a stage after > that soon. I want it to be in /kernel0. I used to agree with this. The implication is that the boot manager smarts are in the third stage boot. Now I am almost convinced of the SVR4 /stand approach, especially now that someone has modloading the /usr VFS! > 6) BSD bad144 table at the end of what the disklabel and/or the drivers > say is the end of the disk (the wrong place). I want to reiterate: wrong place. This table really wants to be either prior to or following slice 'a'. For a system with local swap, following slice 'a' makes more sense, since you can enlarge the table by stealing swap, on the theory that it's better to be able to load the kernel than it is to be able to make user processes inactive. For a system without local swap, or swap on other devices, it's irrelevent, since the table will end up being fixed size in either of the locations, with no chance to expand without a full backup/newfs/restore. > On "i386" systems there are also the DOSpartitions, which can be laid > out as something between a ternary and a quaternary tree and can have > slightly complicated overlaps with each other and very complicated/ > incoherent overlaps with the BSD partitions, especially on > misconfigured systems. [Picture omitted due to lack of time, space > and drawing capabilities.] It's tempting to use these, since Linux does, but this really messes up other architectures, since they are unlikely to start their disks with a DOS boot + partition table. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jan 24 08:42:35 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id IAA01183 for hackers-outgoing; Tue, 24 Jan 1995 08:42:35 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id IAA01176 for ; Tue, 24 Jan 1995 08:42:34 -0800 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id IAA20499; Tue, 24 Jan 1995 08:42:22 -0800 From: Poul-Henning Kamp Message-Id: <199501241642.IAA20499@ref.tfs.com> Subject: Re: Make world To: rkw@dataplex.net (Richard Wackerbarth) Date: Tue, 24 Jan 1995 08:42:22 -0800 (PST) Cc: hackers@FreeBSD.org In-Reply-To: from "Richard Wackerbarth" at Jan 24, 95 07:13:23 am Content-Type: text Content-Length: 352 Sender: hackers-owner@FreeBSD.org Precedence: bulk > Is there any interest in modifying the system build procedure toward any of > the goals mentioned? If so, I am willing to help. yes. > Does anyone have a good solution to the synchronization problem? no. -- Poul-Henning Kamp TRW Financial Systems, Inc. FreeBSD has, until now, not one single time had an undetected error. :-) From owner-freebsd-hackers Tue Jan 24 08:45:09 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id IAA01284 for hackers-outgoing; Tue, 24 Jan 1995 08:45:09 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id IAA01278 for ; Tue, 24 Jan 1995 08:45:08 -0800 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id IAA20509; Tue, 24 Jan 1995 08:44:54 -0800 From: Poul-Henning Kamp Message-Id: <199501241644.IAA20509@ref.tfs.com> Subject: Re: disklabel (1.1.5.1), partitions To: bde@zeta.org.au (Bruce Evans) Date: Tue, 24 Jan 1995 08:44:53 -0800 (PST) Cc: freebsd-hackers@freefall.cdrom.com, kuku@gilberto.physik.rwth-aachen.de In-Reply-To: <199501241608.DAA05264@godzilla.zeta.org.au> from "Bruce Evans" at Jan 25, 95 03:08:21 am Content-Type: text Content-Length: 327 Sender: hackers-owner@FreeBSD.org Precedence: bulk > >2117025 1819 cyl 15 heads 77 sec > Does anybody have anything remotely close to a good reason for not nuking the above printf in sd.c and always report a 32/64/X geometry ?? -- Poul-Henning Kamp TRW Financial Systems, Inc. FreeBSD has, until now, not one single time had an undetected error. :-) From owner-freebsd-hackers Tue Jan 24 08:50:50 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id IAA01543 for hackers-outgoing; Tue, 24 Jan 1995 08:50:50 -0800 Received: from eagle.eng.warwick.ac.uk (eagle.eng.warwick.ac.uk [137.205.144.1]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id IAA01530 for ; Tue, 24 Jan 1995 08:50:35 -0800 From: wkk@eng.warwick.ac.uk Received: from eng.warwick.ac.uk by eagle.eng.warwick.ac.uk with SMTP id QAA03543; Tue, 24 Jan 1995 16:00:22 GMT Date: Tue, 24 Jan 95 16:00:23 GMT Message-Id: <11463.9501241600@eng.warwick.ac.uk> To: hackers@FreeBSD.org Subject: Assembler error Sender: hackers-owner@FreeBSD.org Precedence: bulk Hello, I am trying to compile mach4 server on FreeBSD. Theoretically it should compile but I get the following error in file that has some assembler code. I am not an assembler expert but looking at the error it look likes the assembler is getting confused with the text and data segment (I think). Can anyone help? Thanks very much. khondkar. ************************************************************************ error ************************************************************************ gcc -c -MD -DHAVE_VPRINTF=1 -DHAVE_STRERROR=1 -Di386 -DMACH -DCMU -I- -I. -I../../mach4-i386/boot -I../../mach4-i386/include -I../../mach4/include -nostdinc -DASSEMBLER -MD ../../mach4-i386/boot/bmod_head.S assertion "seg == SEG_DATA || seg == SEG_TEXT" failed: file "/usr/src/gnu/usr.bin/as/subsegs.c", line 174 gcc: Internal compiler error: program as got fatal signal 6 gmake[1]: *** [bmod_head.o] Error 1 gmake[1]: Leaving directory `/usr/src/local/mach4-obj/boot' gmake: *** [install_subdirs] Error 1 ************************************************************************ assembler file while it gets bombed out ************************************************************************ #include .globl _mach_bmod_text,_mach_bmod_data,_mach_bmod_bss .text .align 4 _mach_bmod_text: .data .align 4 _mach_bmod_data: .long BMOD_MAGIC .long _mach_bmod_init .long _mach_bmod_text .long _mach_bmod_etext .long _mach_bmod_data .long _mach_bmod_edata .long _mach_bmod_bss .long _mach_bmod_ebss .bss .align 4 _mach_bmod_bss: From owner-freebsd-hackers Tue Jan 24 09:01:16 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id JAA01863 for hackers-outgoing; Tue, 24 Jan 1995 09:01:16 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id JAA01857 for ; Tue, 24 Jan 1995 09:01:14 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA12124; Tue, 24 Jan 95 09:22:58 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9501241622.AA12124@cs.weber.edu> Subject: Re: cvs commit To: asami@cs.berkeley.edu (Satoshi Asami) Date: Tue, 24 Jan 95 9:22:57 MST Cc: hackers@FreeBSD.org In-Reply-To: <199501240603.WAA17875@silvia.HIP.Berkeley.EDU> from "Satoshi Asami" at Jan 23, 95 10:03:06 pm X-Mailer: ELM [version 2.4dev PL52] Sender: hackers-owner@FreeBSD.org Precedence: bulk > > cvs commit said something like "ci warning: missing message for -m > option" and started asking for messages using the ">>" prompt after > I typed "!" in response to the "a)bort, c)ontinue, e)dit, !)reuse this > message unchanged for remaining dirs" question during a > multi-directory commit. Anyone know why? I have always seen this on multidirectory commits. What happens is the message is created in the first subdirectory, since each directory is the current directory for the commit phase. Typically, if the changes you made are all described by your first comment, use the '!' to reuse the comment on all files. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jan 24 09:02:07 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id JAA01882 for hackers-outgoing; Tue, 24 Jan 1995 09:02:07 -0800 Received: from time.cdrom.com (time.cdrom.com [192.216.223.46]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id JAA01874 for ; Tue, 24 Jan 1995 09:02:06 -0800 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.9/8.6.9) with SMTP id JAA14660; Tue, 24 Jan 1995 09:02:04 -0800 To: rkw@dataplex.net (Richard Wackerbarth) cc: hackers@FreeBSD.org Subject: Re: Make world In-reply-to: Your message of "Tue, 24 Jan 95 07:13:23 CST." Date: Tue, 24 Jan 1995 09:02:04 -0800 Message-ID: <14659.790966924@time.cdrom.com> From: "Jordan K. Hubbard" Sender: hackers-owner@FreeBSD.org Precedence: bulk > Personally, I feel that the "make" process is far from adequate. > IMHO, I should be able to doo all of the following: The entire world target (along with most of the other targets in /usr/src/Makefile) is something that's just mutated along the way since 1.0 days. It's not clean, it rebuilds a number of things gratuitiously (I think at one point we were rebuilding libc 3 times!! :-) and with each passing month it just gets more and more hacked as people add more special cases in. You want to embark on a program of Makefile reform, be my guest! If you can actually bring some sanity to the entire build process then I will personally hire the girl to kiss you! :-) [send me a private note if you've some other preference.. :-)] Jordan From owner-freebsd-hackers Tue Jan 24 09:02:58 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id JAA01904 for hackers-outgoing; Tue, 24 Jan 1995 09:02:58 -0800 Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id JAA01898 for ; Tue, 24 Jan 1995 09:02:56 -0800 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.9/8.6.9) id JAA24550; Tue, 24 Jan 1995 09:02:44 -0800 Date: Tue, 24 Jan 1995 09:02:44 -0800 Message-Id: <199501241702.JAA24550@silvia.HIP.Berkeley.EDU> To: terry@cs.weber.edu CC: hackers@FreeBSD.org In-reply-to: <9501241622.AA12124@cs.weber.edu> (terry@cs.weber.edu) Subject: Re: cvs commit From: asami@cs.berkeley.edu (Satoshi Asami) Sender: hackers-owner@FreeBSD.org Precedence: bulk * > cvs commit said something like "ci warning: missing message for -m * > option" and started asking for messages using the ">>" prompt after * > I typed "!" in response to the "a)bort, c)ontinue, e)dit, !)reuse this * > message unchanged for remaining dirs" question during a * > multi-directory commit. Anyone know why? * * I have always seen this on multidirectory commits. What happens is the * message is created in the first subdirectory, since each directory is * the current directory for the commit phase. * * Typically, if the changes you made are all described by your first comment, * use the '!' to reuse the comment on all files. I know.... Sorry if it wasn't clear, the problem is that it DIDN'T re-use the message after my "!", printed out the message ("ci warning") given above and then resorted to ">>" prompts (the one you get on vanilla ci operation...I think) for the remaining files. Anybody else having problems with multi-directory commits? Satoshi From owner-freebsd-hackers Tue Jan 24 09:28:21 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id JAA02652 for hackers-outgoing; Tue, 24 Jan 1995 09:28:21 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id JAA02644 for ; Tue, 24 Jan 1995 09:28:18 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA12428; Tue, 24 Jan 95 10:20:50 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9501241720.AA12428@cs.weber.edu> Subject: Re: disklabel (1.1.5.1), partitions To: phk@ref.tfs.com (Poul-Henning Kamp) Date: Tue, 24 Jan 95 10:20:50 MST Cc: bde@zeta.org.au, freebsd-hackers@freefall.cdrom.com, kuku@gilberto.physik.rwth-aachen.de In-Reply-To: <199501241644.IAA20509@ref.tfs.com> from "Poul-Henning Kamp" at Jan 24, 95 08:44:53 am X-Mailer: ELM [version 2.4dev PL52] Sender: hackers-owner@FreeBSD.org Precedence: bulk > > > >2117025 1819 cyl 15 heads 77 sec > > > Does anybody have anything remotely close to a good reason for not nuking > the above printf in sd.c and always report a 32/64/X geometry ?? Not all SCSI devices are thus translated? Hold on! How about because the kernel should know the real BIOS apparent geometry for instead of making things up like that? No, no, wait! I have a better one... because you could just add descriptive text to inform the user of the physical vs. the translated geometry? I've got it! I've got it! Because some of us don't install DOS boot blocks or partitioning at all, even though the implication is that we are supposed to? }B-). Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jan 24 09:50:58 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id JAA03556 for hackers-outgoing; Tue, 24 Jan 1995 09:50:58 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id JAA03549 for ; Tue, 24 Jan 1995 09:50:55 -0800 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id JAA21155; Tue, 24 Jan 1995 09:50:43 -0800 From: Poul-Henning Kamp Message-Id: <199501241750.JAA21155@ref.tfs.com> Subject: Re: disklabel (1.1.5.1), partitions To: terry@cs.weber.edu (Terry Lambert) Date: Tue, 24 Jan 1995 09:50:37 -0800 (PST) Cc: bde@zeta.org.au, freebsd-hackers@freefall.cdrom.com, kuku@gilberto.physik.rwth-aachen.de In-Reply-To: <9501241720.AA12428@cs.weber.edu> from "Terry Lambert" at Jan 24, 95 10:20:50 am Content-Type: text Content-Length: 1166 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > > >2117025 1819 cyl 15 heads 77 sec > > > > > Does anybody have anything remotely close to a good reason for not nuking > > the above printf in sd.c and always report a 32/64/X geometry ?? > > Not all SCSI devices are thus translated? mostly they are, unless the "> 1GB" option is set. > Hold on! How about because the kernel should know the real BIOS apparent > geometry for instead of making things up like that? true, except we cannot trust this one anymore :-( Some IDE and SCSI drivers get their "geometry" in CONFIG.SYS these days. > No, no, wait! I have a better one... because you could just add > descriptive text to inform the user of the physical vs. the translated > geometry? no. > I've got it! I've got it! Because some of us don't install DOS boot > blocks or partitioning at all, even though the implication is that we > are supposed to? Has nothing to do with it. If you pass some of the weird geometries to newfs it will become very confused... 32/64 works sensibly most of the time. -- Poul-Henning Kamp TRW Financial Systems, Inc. FreeBSD has, until now, not one single time had an undetected error. :-) From owner-freebsd-hackers Tue Jan 24 10:10:25 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id KAA04041 for hackers-outgoing; Tue, 24 Jan 1995 10:10:25 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id KAA04034 for ; Tue, 24 Jan 1995 10:10:23 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA12647; Tue, 24 Jan 95 11:04:15 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9501241804.AA12647@cs.weber.edu> Subject: Re: disklabel (1.1.5.1), partitions To: phk@ref.tfs.com (Poul-Henning Kamp) Date: Tue, 24 Jan 95 11:04:15 MST Cc: bde@zeta.org.au, freebsd-hackers@freefall.cdrom.com, kuku@gilberto.physik.rwth-aachen.de In-Reply-To: <199501241750.JAA21155@ref.tfs.com> from "Poul-Henning Kamp" at Jan 24, 95 09:50:37 am X-Mailer: ELM [version 2.4dev PL52] Sender: hackers-owner@FreeBSD.org Precedence: bulk > > Not all SCSI devices are thus translated? > mostly they are, unless the "> 1GB" option is set. Sorry, this isn't really a valid reason for lying about the geometry unless you can guarantee Adaptec ROMs for the house... my WD7000-FAAST controller (the works with 386BSD PL2 but not after -- I'll have to do something about that eventually) doesn't have this capability. I point at it not as a piece of obscure hardware (though it is that) but as an example of something that doesn't work that way that I can back up with ROM dumps. If you'll accept a more general statement, I'll say that the translation you suggest is primarily an Adaptec thing, and primarily for newer controllers from them, at that. > > Hold on! How about because the kernel should know the real BIOS apparent > > geometry for instead of making things up like that? > true, except we cannot trust this one anymore :-( Some IDE and SCSI > drivers get their "geometry" in CONFIG.SYS these days. Actually, most EIDE controllers get them from a modified system boot block installed by the OEM for the machine. Blowing the system boot block in that case really screws you up. I have a copy of the article describing this somewhere... > > No, no, wait! I have a better one... because you could just add > > descriptive text to inform the user of the physical vs. the translated > > geometry? > no. I don't understand... what's wrong with: Geometry CCCC/HH/SS (Physical CCCC/HH/SS) Instead of the unmarked numbers that it puts out now? > Has nothing to do with it. If you pass some of the weird geometries to > newfs it will become very confused... 32/64 works sensibly most of the > time. This is a bug in newfs, like the one where it doesn't create a lost+found, not a reason to bogify other parts of the system to hack around it. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jan 24 10:23:14 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id KAA04291 for hackers-outgoing; Tue, 24 Jan 1995 10:23:14 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id KAA04285 for ; Tue, 24 Jan 1995 10:23:13 -0800 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id KAA21387; Tue, 24 Jan 1995 10:23:01 -0800 From: Poul-Henning Kamp Message-Id: <199501241823.KAA21387@ref.tfs.com> Subject: Re: disklabel (1.1.5.1), partitions To: terry@cs.weber.edu (Terry Lambert) Date: Tue, 24 Jan 1995 10:22:58 -0800 (PST) Cc: bde@zeta.org.au, freebsd-hackers@freefall.cdrom.com, kuku@gilberto.physik.rwth-aachen.de In-Reply-To: <9501241804.AA12647@cs.weber.edu> from "Terry Lambert" at Jan 24, 95 11:04:15 am Content-Type: text Content-Length: 1942 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > > Not all SCSI devices are thus translated? > > mostly they are, unless the "> 1GB" option is set. > > Sorry, this isn't really a valid reason for lying about the geometry Hey terry, you lost the reason: A scsi-disk >HAS< no geometry we should care about. > > > Hold on! How about because the kernel should know the real BIOS apparent > > > geometry for instead of making things up like that? > > true, except we cannot trust this one anymore :-( Some IDE and SCSI > > drivers get their "geometry" in CONFIG.SYS these days. > > Actually, most EIDE controllers get them from a modified system boot block > installed by the OEM for the machine. Blowing the system boot block in > that case really screws you up. No, 540Mb and above seems to get it from various "disk-managers" loaded in the config.sys with an increasingly annoying frequency. > I don't understand... what's wrong with: > > Geometry CCCC/HH/SS (Physical CCCC/HH/SS) The Physical isn't true, It's two years since I saw anything which added (multiplied actually) up to the number of sectors available. The numbers are fiction, make belive, has no use, value or connection with our use of the drive. > > Has nothing to do with it. If you pass some of the weird geometries to > > newfs it will become very confused... 32/64 works sensibly most of the > > time. > > This is a bug in newfs, like the one where it doesn't create a lost+found, > not a reason to bogify other parts of the system to hack around it. Not true. Newfs and UFS was optimized to know about disk-geometry. Since most (95%) drives these days are zoned (variable sectors/track), this isn't of any particular use. The existense of caches on the drives doesn't improve it either. All the geometry is really used for is to size the "cylinder"-groups. -- Poul-Henning Kamp TRW Financial Systems, Inc. FreeBSD has, until now, not one single time had an undetected error. :-) From owner-freebsd-hackers Tue Jan 24 11:08:19 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id LAA07318 for hackers-outgoing; Tue, 24 Jan 1995 11:08:19 -0800 Received: from tfs.com (mailhub.tfs.com [140.145.250.1]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id LAA07312 for ; Tue, 24 Jan 1995 11:08:18 -0800 Received: by tfs.com (smail3.1.28.1) Message-Id: From: julian@tfs.com (Julian Elischer) Subject: Re: disklabel (1.1.5.1), partitions To: kuku@gilberto.physik.rwth-aachen.de (Christoph P. Kukulies) Date: Tue, 24 Jan 1995 11:07:44 -0800 (PST) Cc: freebsd-hackers@freefall.cdrom.com In-Reply-To: <199501240924.KAA00162@gilberto.physik.rwth-aachen.de> from "Christoph P. Kukulies" at Jan 24, 95 10:24:06 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1065 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > > I had disk problems on 'gil' recently (hopefully solved) - reformatted > a Fuji M2694S using SCSICNTL. > > I was wondering about the following when disklabeling again: > > dmesg told me: > > 2117025 1819 cyl 15 heads 77 sec > > Using these figures in a disktab entry resulted in a warning saying that > partitions c,d,e exceeded end of disk. (I made them p[cde]#2117025). > > So I reduced them to what 15 * 77 * 1819 calculates to, namely 2100945 > and disklabel kept silent. > > Did I give away some sectors ? > Unfortunatly yes... the question is "What do we do with disks with variable geometries.. especially when the disklabel code assumes it is a fixed geometry. we calculate an 'average' number of setors per track.. but it has to be an integer, and that truncation leads to a bunch of unused sectors.. julian > > > > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de > FreeBSD blues 2.1.0-Development FreeBSD 2.1.0-Development #1: > Wed Jan 18 10:42:31 1995 kuku@blues:/usr/src/sys/compile/BLUES i386 > From owner-freebsd-hackers Tue Jan 24 11:32:03 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id LAA08299 for hackers-outgoing; Tue, 24 Jan 1995 11:32:03 -0800 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id LAA08293 for ; Tue, 24 Jan 1995 11:31:56 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA26275; Tue, 24 Jan 1995 20:33:03 +0100 Received: by sax.sax.de (8.6.9/8.6.9-s1) with UUCP id UAA22073 for freebsd-hackers@freebsd.org; Tue, 24 Jan 1995 20:33:03 +0100 Received: by bonnie.tcd-dresden.de (8.6.8/8.6.6) id UAA10663; Tue, 24 Jan 1995 20:04:14 +0100 From: j@uriah.sax.de (J Wunsch) Message-Id: <199501241904.UAA10663@bonnie.tcd-dresden.de> Subject: Re: disklabel (1.1.5.1), partitions To: freebsd-hackers@FreeBSD.org (FreeBSD hackers) Date: Tue, 24 Jan 1995 20:04:14 +0100 (MET) In-Reply-To: <199501241750.JAA21155@ref.tfs.com> from "Poul-Henning Kamp" at Jan 24, 95 09:50:37 am X-Phone: +49-351-8141 137 Reply-To: joerg_wunsch@uriah.sax.de X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1263 Sender: hackers-owner@FreeBSD.org Precedence: bulk As Poul-Henning Kamp wrote: | | > > > >2117025 1819 cyl 15 heads 77 sec | > > > | > > Does anybody have anything remotely close to a good reason for not nuking | > > the above printf in sd.c and always report a 32/64/X geometry ?? Since it's the geometry the manufacter prefers to report back. It's the perhaps most realistic guess that roughly maps 1:1 to the physical geometry. (For what i've seen so far, the reported number of heads is often exact, and the number of cylinders too.) | > Not all SCSI devices are thus translated? | mostly they are, unless the "> 1GB" option is set. Which "> 1GB" option? Cannot remember one... | true, except we cannot trust this one anymore :-( Some IDE and SCSI | drivers get their "geometry" in CONFIG.SYS these days. find / -name CONFIG.SYS didn't report me any occurence of it. Which file do you refer to? >:-) Seriously, unless i really have a machine co-existing with messydos, i *never* used the 32/64 hack so far. (And this case hit for one out of five or six machines for me.) -- cheers, J"org work: --- no longer --- private: joerg_wunsch@uriah.sax.de Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Jan 24 11:38:46 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id LAA08412 for hackers-outgoing; Tue, 24 Jan 1995 11:38:46 -0800 Received: from terra.npi.msu.su (root@terra.npi.msu.su [158.250.20.3]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id LAA08406 for ; Tue, 24 Jan 1995 11:38:37 -0800 Received: from sunny.bog.msu.su (sunny.bog.msu.su [158.250.20.1]) by terra.npi.msu.su (8.6.9/8.6.6) with ESMTP id WAA19963; Tue, 24 Jan 1995 22:36:54 +0300 Received: (dima@localhost) by sunny.bog.msu.su (8.6.9/8.6.5) id WAA17250; Tue, 24 Jan 1995 22:37:32 +0300 Date: Tue, 24 Jan 1995 22:37:31 +0300 (????) From: Dmitry Khrustalev X-Sender: dima@sunny To: Poul-Henning Kamp cc: Terry Lambert , freebsd-hackers@freefall.cdrom.com Subject: Re: disklabel (1.1.5.1), partitions In-Reply-To: <199501241823.KAA21387@ref.tfs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hackers-owner@FreeBSD.org Precedence: bulk On Tue, 24 Jan 1995, Poul-Henning Kamp wrote: > > > > Not all SCSI devices are thus translated? > > > mostly they are, unless the "> 1GB" option is set. > > > > Sorry, this isn't really a valid reason for lying about the geometry > Hey terry, you lost the reason: A scsi-disk >HAS< no geometry we should > care about. It seems you are wrong: you can query scsi-2 disk for it's geometry. For details, see ftp://ftp.cdf.toronto.edu/pub/scsiinfo/scsiinfo-3.3.shar.gz dima. > > > > > Hold on! How about because the kernel should know the real BIOS apparent > > > > geometry for instead of making things up like that? > > > true, except we cannot trust this one anymore :-( Some IDE and SCSI > > > drivers get their "geometry" in CONFIG.SYS these days. > > > > Actually, most EIDE controllers get them from a modified system boot block > > installed by the OEM for the machine. Blowing the system boot block in > > that case really screws you up. > No, 540Mb and above seems to get it from various "disk-managers" loaded > in the config.sys with an increasingly annoying frequency. > > > I don't understand... what's wrong with: > > > > Geometry CCCC/HH/SS (Physical CCCC/HH/SS) > The Physical isn't true, It's two years since I saw anything which added > (multiplied actually) up to the number of sectors available. > The numbers are fiction, make belive, has no use, value or connection > with our use of the drive. > > > > Has nothing to do with it. If you pass some of the weird geometries to > > > newfs it will become very confused... 32/64 works sensibly most of the > > > time. > > > > This is a bug in newfs, like the one where it doesn't create a lost+found, > > not a reason to bogify other parts of the system to hack around it. > Not true. Newfs and UFS was optimized to know about disk-geometry. Since > most (95%) drives these days are zoned (variable sectors/track), this isn't > of any particular use. The existense of caches on the drives doesn't improve > it either. > All the geometry is really used for is to size the "cylinder"-groups. > > -- > Poul-Henning Kamp > TRW Financial Systems, Inc. > FreeBSD has, until now, not one single time had an undetected error. :-) > From owner-freebsd-hackers Tue Jan 24 12:09:35 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id MAA09062 for hackers-outgoing; Tue, 24 Jan 1995 12:09:35 -0800 Received: from nosferatu.cas.usf.edu (nosferatu.cas.usf.edu [131.247.31.155]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id MAA09056 for ; Tue, 24 Jan 1995 12:09:33 -0800 Received: (mephisto@localhost) by nosferatu.cas.usf.edu (8.6.8/8.3) id PAA27895; Tue, 24 Jan 1995 15:18:01 -0500 Date: Tue, 24 Jan 1995 15:18:00 -0500 (EST) From: NatureBoy To: wkk@eng.warwick.ac.uk cc: hackers@FreeBSD.org Subject: Re: Assembler error In-Reply-To: <11463.9501241600@eng.warwick.ac.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hackers-owner@FreeBSD.org Precedence: bulk You need a recent version of gas, and a patched one at that. I suggest finding gas-2.3 and using the patch that is buried somewhere in the mach4-users-archive located (I think) at ftp://jaquar.cs.utah.edu/flexmach. Joseph Orthoefer From owner-freebsd-hackers Tue Jan 24 12:19:58 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id MAA09929 for hackers-outgoing; Tue, 24 Jan 1995 12:19:58 -0800 Received: from isl.cf.ac.uk (isl-gate.elsy.cf.ac.uk [131.251.22.1]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id MAA09921 for ; Tue, 24 Jan 1995 12:19:45 -0800 Received: (from paul@localhost) by isl.cf.ac.uk (8.6.9/8.6.9) id UAA01237; Tue, 24 Jan 1995 20:18:21 GMT From: Paul Richards Message-Id: <199501242018.UAA01237@isl.cf.ac.uk> Subject: Re: disklabel (1.1.5.1), partitions To: phk@ref.tfs.com (Poul-Henning Kamp) Date: Tue, 24 Jan 1995 20:18:20 +0000 (GMT) Cc: bde@zeta.org.au, freebsd-hackers@freefall.cdrom.com, kuku@gilberto.physik.rwth-aachen.de In-Reply-To: <199501241644.IAA20509@ref.tfs.com> from "Poul-Henning Kamp" at Jan 24, 95 08:44:53 am X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 683 Sender: hackers-owner@FreeBSD.org Precedence: bulk In reply to Poul-Henning Kamp who said > > > >2117025 1819 cyl 15 heads 77 sec > > > Does anybody have anything remotely close to a good reason for not nuking > the above printf in sd.c and always report a 32/64/X geometry ?? > I dislike the idea. If you think the reported disk geometry is causing support hassles then just don't report it, don't pretend the disk reported something else instead even if that's what we use:-) -- Paul Richards, FreeBSD core team member. Phone: +44 1222 874000 x6646 (work), +44 1222 457651 (home) Dept. Mechanical Engineering, University of Wales, College Cardiff. Internet: paul@FreeBSD.org, JANET(UK): RICHARDSDP@CARDIFF.AC.UK From owner-freebsd-hackers Tue Jan 24 12:32:03 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id MAA10494 for hackers-outgoing; Tue, 24 Jan 1995 12:32:03 -0800 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id MAA10485 for ; Tue, 24 Jan 1995 12:31:52 -0800 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id PAA09576; Tue, 24 Jan 1995 15:31:25 -0500 From: Peter Dufault Message-Id: <199501242031.PAA09576@hda.com> Subject: Re: disklabel (1.1.5.1), partitions To: phk@ref.tfs.com (Poul-Henning Kamp) Date: Tue, 24 Jan 1995 15:31:25 -0500 (EST) Cc: bde@zeta.org.au, freebsd-hackers@freefall.cdrom.com, kuku@gilberto.physik.rwth-aachen.de In-Reply-To: <199501241644.IAA20509@ref.tfs.com> from "Poul-Henning Kamp" at Jan 24, 95 08:44:53 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 457 Sender: hackers-owner@FreeBSD.org Precedence: bulk Poul-Henning Kamp writes: > > Does anybody have anything remotely close to a good reason for not nuking > the above printf in sd.c and always report a 32/64/X geometry ?? How about just the number of sectors? Peter -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 -- Formerly hd@world.std.com. E-mail problems? Tell hdslip@iii.net From owner-freebsd-hackers Tue Jan 24 12:34:48 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id MAA10629 for hackers-outgoing; Tue, 24 Jan 1995 12:34:48 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id MAA10613 for ; Tue, 24 Jan 1995 12:34:45 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA13725; Tue, 24 Jan 95 13:28:41 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9501242028.AA13725@cs.weber.edu> Subject: Re: disklabel (1.1.5.1), partitions To: phk@ref.tfs.com (Poul-Henning Kamp) Date: Tue, 24 Jan 95 13:28:41 MST Cc: bde@zeta.org.au, freebsd-hackers@freefall.cdrom.com, kuku@gilberto.physik.rwth-aachen.de In-Reply-To: <199501241823.KAA21387@ref.tfs.com> from "Poul-Henning Kamp" at Jan 24, 95 10:22:58 am X-Mailer: ELM [version 2.4dev PL52] Sender: hackers-owner@FreeBSD.org Precedence: bulk > > > > Hold on! How about because the kernel should know the real BIOS apparent > > > > geometry for instead of making things up like that? > > > true, except we cannot trust this one anymore :-( Some IDE and SCSI > > > drivers get their "geometry" in CONFIG.SYS these days. > > > > Actually, most EIDE controllers get them from a modified system boot block > > installed by the OEM for the machine. Blowing the system boot block in > > that case really screws you up. > No, 540Mb and above seems to get it from various "disk-managers" loaded > in the config.sys with an increasingly annoying frequency. I lost this article. 8-(. I think it was in comp.os.386bsd.developer. Specifically, it referenced the Gateway boot code installing an INT 13 redirector. I can't remember who wrote it ("Vince" sounds familiar, though). > > I don't understand... what's wrong with: > > > > Geometry CCCC/HH/SS (Physical CCCC/HH/SS) > The Physical isn't true, It's two years since I saw anything which added > (multiplied actually) up to the number of sectors available. > The numbers are fiction, make belive, has no use, value or connection > with our use of the drive. I typically *use* the the physical geometry, particularly if there are more than 1024 cylinders. Specifically, C cylinders C' translated cylinders H heads H' translated heads S sectors S' translates sectors Why? Because I will never be provided with a translated number of cylinders that exceed 1024. Because of this, if the translation is not sufficient for BIOS to be able to use the whole disk, I'd rather not give that space away under BSD as well, thank you. Using an AHA1742 in advanced translation mode with a Maxtor Panther drive yields an additional .7G of disk this way. Just as an example. I can give the actual calculation steps, if I need to. They are in the archives of this list, already, however. > > > Has nothing to do with it. If you pass some of the weird geometries to > > > newfs it will become very confused... 32/64 works sensibly most of the > > > time. > > > > This is a bug in newfs, like the one where it doesn't create a lost+found, > > not a reason to bogify other parts of the system to hack around it. > Not true. I don't understand. Are you saying that it's OK for newfs to become confused, it's OK to not create lost+found, or both? >Newfs and UFS was optimized to know about disk-geometry. Since > most (95%) drives these days are zoned (variable sectors/track), this isn't > of any particular use. The existense of caches on the drives doesn't improve > it either. > All the geometry is really used for is to size the "cylinder"-groups. It's not of any particular use, unless the translated geometry limits the addressable space on the disk to less than the actual space on the disk. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jan 24 12:40:05 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id MAA10782 for hackers-outgoing; Tue, 24 Jan 1995 12:40:05 -0800 Received: from estienne.cs.berkeley.edu (estienne.CS.Berkeley.EDU [128.32.42.147]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id MAA10770 for ; Tue, 24 Jan 1995 12:39:58 -0800 Received: (from gibbs@localhost) by estienne.cs.berkeley.edu (8.6.9/8.6.9) id MAA23769; Tue, 24 Jan 1995 12:39:42 -0800 From: "Justin T. Gibbs" Message-Id: <199501242039.MAA23769@estienne.cs.berkeley.edu> Subject: Re: disklabel (1.1.5.1), partitions To: phk@ref.tfs.com (Poul-Henning Kamp) Date: Tue, 24 Jan 1995 12:39:41 -0800 (PST) Cc: bde@zeta.org.au, freebsd-hackers@freefall.cdrom.com, kuku@gilberto.physik.rwth-aachen.de In-Reply-To: <199501241644.IAA20509@ref.tfs.com> from "Poul-Henning Kamp" at Jan 24, 95 08:44:53 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 896 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > > >2117025 1819 cyl 15 heads 77 sec > > > Does anybody have anything remotely close to a good reason for not nuking > the above printf in sd.c and always report a 32/64/X geometry ?? People using extended translation? People wanting to know what the geometry reported by the disk really is (You can get a better idea of what the max possible bandwidth of the drive is this way). If we can always determine the translated geometry correctly, then I would suggest printing that at the time the SCSI bus is attached. > > -- > Poul-Henning Kamp > TRW Financial Systems, Inc. > FreeBSD has, until now, not one single time had an undetected error. :-) > -- Justin T. Gibbs ============================================== TCS Instructional Group - Programmer/Analyst 1 Cory | Po | Danube | Volga | Parker | Torus ============================================== From owner-freebsd-hackers Tue Jan 24 13:10:56 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id NAA11682 for hackers-outgoing; Tue, 24 Jan 1995 13:10:56 -0800 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id NAA11662 for ; Tue, 24 Jan 1995 13:10:41 -0800 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.8/8.6.6) id VAA10844; Tue, 24 Jan 1995 21:09:36 GMT From: "Rodney W. Grimes" Message-Id: <199501242109.VAA10844@gndrsh.aac.dev.com> Subject: Re: disklabel (1.1.5.1), partitions To: phk@ref.tfs.com (Poul-Henning Kamp) Date: Tue, 24 Jan 1995 21:09:36 +0000 (GMT) Cc: terry@cs.weber.edu, bde@zeta.org.au, freebsd-hackers@freefall.cdrom.com, kuku@gilberto.physik.rwth-aachen.de In-Reply-To: <199501241823.KAA21387@ref.tfs.com> from "Poul-Henning Kamp" at Jan 24, 95 10:22:58 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 2726 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > > > > Not all SCSI devices are thus translated? > > > mostly they are, unless the "> 1GB" option is set. > > > > Sorry, this isn't really a valid reason for lying about the geometry > Hey terry, you lost the reason: A scsi-disk >HAS< no geometry we should > care about. The keywords there are ``should care about''. SCSI disk only report 3 items, total number of sectors, physical number of heads and physical number of cylinders. The sectors/track is what we ``fake''. > > > > Hold on! How about because the kernel should know the real BIOS apparent > > > > geometry for instead of making things up like that? > > > true, except we cannot trust this one anymore :-( Some IDE and SCSI > > > drivers get their "geometry" in CONFIG.SYS these days. > > > > Actually, most EIDE controllers get them from a modified system boot block > > installed by the OEM for the machine. Blowing the system boot block in > > that case really screws you up. > No, 540Mb and above seems to get it from various "disk-managers" loaded > in the config.sys with an increasingly annoying frequency. There are many ways this problem is solved: 1) NEW BIOS'es that are LBA aware can handle drives into the GBytes 2) Special boot code that munges with the drive paramter table 3) Disk managers hidden on track 0 4) Device drivers loaded by config.sys > > I don't understand... what's wrong with: > > > > Geometry CCCC/HH/SS (Physical CCCC/HH/SS) > The Physical isn't true, It's two years since I saw anything which added > (multiplied actually) up to the number of sectors available. > The numbers are fiction, make belive, has no use, value or connection > with our use of the drive. I think it is time to change the sd probe message to ONLY output the total sectors, since that is the relevant number. And/Or clearly label the geometry as fictitious. > > > Has nothing to do with it. If you pass some of the weird geometries to > > > newfs it will become very confused... 32/64 works sensibly most of the > > > time. > > > > This is a bug in newfs, like the one where it doesn't create a lost+found, > > not a reason to bogify other parts of the system to hack around it. > Not true. Newfs and UFS was optimized to know about disk-geometry. Since > most (95%) drives these days are zoned (variable sectors/track), this isn't > of any particular use. The existense of caches on the drives doesn't improve > it either. > All the geometry is really used for is to size the "cylinder"-groups. Probably time to rewrite newfs and parts of ufs to deal with reality :-). -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-hackers Tue Jan 24 13:35:14 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id NAA12433 for hackers-outgoing; Tue, 24 Jan 1995 13:35:14 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id NAA12425 for ; Tue, 24 Jan 1995 13:35:11 -0800 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id NAA22149; Tue, 24 Jan 1995 13:34:49 -0800 From: Poul-Henning Kamp Message-Id: <199501242134.NAA22149@ref.tfs.com> Subject: Re: disklabel (1.1.5.1), partitions To: dima@sunny.bog.msu.su (Dmitry Khrustalev) Date: Tue, 24 Jan 1995 13:34:44 -0800 (PST) Cc: terry@cs.weber.edu, freebsd-hackers@freefall.cdrom.com In-Reply-To: from "Dmitry Khrustalev" at Jan 24, 95 10:37:31 pm Content-Type: text Content-Length: 830 Sender: hackers-owner@FreeBSD.org Precedence: bulk > On Tue, 24 Jan 1995, Poul-Henning Kamp wrote: > > > > > > Not all SCSI devices are thus translated? > > > > mostly they are, unless the "> 1GB" option is set. > > > > > > Sorry, this isn't really a valid reason for lying about the geometry > > Hey terry, you lost the reason: A scsi-disk >HAS< no geometry we should > > care about. > > It seems you are wrong: you can query scsi-2 disk for it's geometry. > For details, see ftp://ftp.cdf.toronto.edu/pub/scsiinfo/scsiinfo-3.3.shar.gz The operative word is "that we should care about". You extract that geometry and explain it to UFS, I have no problems with it. Until such code appears, we have all kinds of problems with it. -- Poul-Henning Kamp TRW Financial Systems, Inc. FreeBSD has, until now, not one single time had an undetected error. :-) From owner-freebsd-hackers Tue Jan 24 13:38:35 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id NAA12489 for hackers-outgoing; Tue, 24 Jan 1995 13:38:35 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id NAA12483 for ; Tue, 24 Jan 1995 13:38:32 -0800 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id NAA22208; Tue, 24 Jan 1995 13:38:16 -0800 From: Poul-Henning Kamp Message-Id: <199501242138.NAA22208@ref.tfs.com> Subject: Re: disklabel (1.1.5.1), partitions To: terry@cs.weber.edu (Terry Lambert) Date: Tue, 24 Jan 1995 13:38:13 -0800 (PST) Cc: bde@zeta.org.au, freebsd-hackers@freefall.cdrom.com, kuku@gilberto.physik.rwth-aachen.de In-Reply-To: <9501242028.AA13725@cs.weber.edu> from "Terry Lambert" at Jan 24, 95 01:28:41 pm Content-Type: text Content-Length: 1085 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > > This is a bug in newfs, like the one where it doesn't create a lost+found, > > > not a reason to bogify other parts of the system to hack around it. > > Not true. > > I don't understand. Are you saying that it's OK for newfs to become confused, > it's OK to not create lost+found, or both? "this is not a bug in newfs" > >Newfs and UFS was optimized to know about disk-geometry. Since > > most (95%) drives these days are zoned (variable sectors/track), this isn't > > of any particular use. The existense of caches on the drives doesn't improve > > it either. > > All the geometry is really used for is to size the "cylinder"-groups. > > It's not of any particular use, unless the translated geometry limits the > addressable space on the disk to less than the actual space on the disk. The problem is that you will get newfs into some strange corners if you report for instance 255 heads, as most of the ">1GB" stuff does... -- Poul-Henning Kamp TRW Financial Systems, Inc. FreeBSD has, until now, not one single time had an undetected error. :-) From owner-freebsd-hackers Tue Jan 24 13:39:29 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id NAA12511 for hackers-outgoing; Tue, 24 Jan 1995 13:39:29 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id NAA12505 for ; Tue, 24 Jan 1995 13:39:27 -0800 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id NAA22166; Tue, 24 Jan 1995 13:35:51 -0800 From: Poul-Henning Kamp Message-Id: <199501242135.NAA22166@ref.tfs.com> Subject: Re: disklabel (1.1.5.1), partitions To: paul@isl.cf.ac.uk (Paul Richards) Date: Tue, 24 Jan 1995 13:35:47 -0800 (PST) Cc: bde@zeta.org.au, freebsd-hackers@freefall.cdrom.com, kuku@gilberto.physik.rwth-aachen.de In-Reply-To: <199501242018.UAA01237@isl.cf.ac.uk> from "Paul Richards" at Jan 24, 95 08:18:20 pm Content-Type: text Content-Length: 643 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > > > > >2117025 1819 cyl 15 heads 77 sec > > > > > Does anybody have anything remotely close to a good reason for not nuking > > the above printf in sd.c and always report a 32/64/X geometry ?? > > > > I dislike the idea. If you think the reported disk geometry is causing > support hassles then just don't report it, don't pretend the disk > reported something else instead even if that's what we use:-) Exactly, I didn't intend to print it, only to stick it in the default disklabel. -- Poul-Henning Kamp TRW Financial Systems, Inc. FreeBSD has, until now, not one single time had an undetected error. :-) From owner-freebsd-hackers Tue Jan 24 13:41:04 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id NAA12553 for hackers-outgoing; Tue, 24 Jan 1995 13:41:04 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id NAA12546 for ; Tue, 24 Jan 1995 13:41:01 -0800 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id NAA22227; Tue, 24 Jan 1995 13:40:47 -0800 From: Poul-Henning Kamp Message-Id: <199501242140.NAA22227@ref.tfs.com> Subject: Re: disklabel (1.1.5.1), partitions To: gibbs@estienne.CS.Berkeley.EDU (Justin T. Gibbs) Date: Tue, 24 Jan 1995 13:40:44 -0800 (PST) Cc: bde@zeta.org.au, freebsd-hackers@freefall.cdrom.com, kuku@gilberto.physik.rwth-aachen.de In-Reply-To: <199501242039.MAA23769@estienne.cs.berkeley.edu> from "Justin T. Gibbs" at Jan 24, 95 12:39:41 pm Content-Type: text Content-Length: 647 Sender: hackers-owner@FreeBSD.org Precedence: bulk > If we can always determine the translated geometry correctly, then I would > suggest printing that at the time the SCSI bus is attached. By all means, except nobody have come up with any code yet. The bios-values are already in the kernel, we just need some way to match them to the drives we find. Best suggestion so far: Make a checksum of 4 sectors (#100, #200, #300 & #400 for instance) when asking the bios (in the bootblocks :-( ) and match that to what we find during disk-probe/attach. -- Poul-Henning Kamp TRW Financial Systems, Inc. FreeBSD has, until now, not one single time had an undetected error. :-) From owner-freebsd-hackers Tue Jan 24 13:51:04 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id NAA12923 for hackers-outgoing; Tue, 24 Jan 1995 13:51:04 -0800 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id NAA12916 for ; Tue, 24 Jan 1995 13:50:52 -0800 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.8/8.6.6) id VAA10908; Tue, 24 Jan 1995 21:21:59 GMT From: "Rodney W. Grimes" Message-Id: <199501242121.VAA10908@gndrsh.aac.dev.com> Subject: Re: disklabel (1.1.5.1), partitions To: paul@isl.cf.ac.uk (Paul Richards) Date: Tue, 24 Jan 1995 21:21:58 +0000 (GMT) Cc: freebsd-hackers@freefall.cdrom.com In-Reply-To: <199501242018.UAA01237@isl.cf.ac.uk> from "Paul Richards" at Jan 24, 95 08:18:20 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 891 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > In reply to Poul-Henning Kamp who said > > > > > >2117025 1819 cyl 15 heads 77 sec > > > > > Does anybody have anything remotely close to a good reason for not nuking > > the above printf in sd.c and always report a 32/64/X geometry ?? > > > > I dislike the idea. If you think the reported disk geometry is causing > support hassles then just don't report it, don't pretend the disk > reported something else instead even if that's what we use:-) How about changing it like this: OLD: sd0: 1169MB (2395980 total sec), 2448 cyl, 14 head, 69 sec, bytes/sec 512 NEW: sd0: 1169MB (2395980 total sec), 2448 cyl, 14 head, VAR sec, bytes/sec 512 One very small change, the other numbers are exact as reported by the SCSI spec. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-hackers Tue Jan 24 14:04:53 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id OAA13432 for hackers-outgoing; Tue, 24 Jan 1995 14:04:53 -0800 Received: from amcell2.caisr.cwru.edu (amcell2.CAISR.CWRU.Edu [129.22.24.2]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id OAA13424 for ; Tue, 24 Jan 1995 14:04:45 -0800 Received: (from ljo@localhost) by amcell2.caisr.cwru.edu (8.6.8/8.6.6) id RAA08717; Tue, 24 Jan 1995 17:03:24 -0500 Date: Tue, 24 Jan 1995 17:03:24 -0500 From: L Jonas Olsson Message-Id: <199501242203.RAA08717@amcell2.caisr.cwru.edu> To: phk@ref.tfs.com CC: terry@cs.weber.edu, bde@zeta.org.au, freebsd-hackers@freefall.cdrom.com, kuku@gilberto.physik.rwth-aachen.de In-reply-to: <199501242138.NAA22208@ref.tfs.com> (message from Poul-Henning Kamp on Tue, 24 Jan 1995 13:38:13 -0800 (PST)) Subject: Re: disklabel (1.1.5.1), partitions Reply-to: ljo@po.cwru.edu Sender: hackers-owner@FreeBSD.org Precedence: bulk From: Poul-Henning Kamp Date: Tue, 24 Jan 1995 13:38:13 -0800 (PST) Cc: bde@zeta.org.au, freebsd-hackers@freefall.cdrom.com, kuku@gilberto.physik.rwth-aachen.de Content-Type: text Content-Length: 1085 Sender: hackers-owner@FreeBSD.org Precedence: bulk <...> The problem is that you will get newfs into some strange corners if you report for instance 255 heads, as most of the ">1GB" stuff does... It is possible to use this geometry. I have one here (aic6360 controller on ZEOS MB): dumpfs /dev/sd0a gives: magic 11954 format dynamic time Mon Jan 11 22:26:27 1988 nbfree 637 ndir 58 nifree 7206 nffree 2 ncg 1 ncyl 2 size 4016 blocks 3761 bsize 8192 shift 13 mask 0xffffe000 fsize 4096 shift 12 mask 0xfffff000 frag 2 shift 1 fsbtodb 3 cpg 16 bpg 16065 fpg 32130 ipg 7872 minfree 10% optim time maxcontig 1 maxbpg 2048 rotdelay 4ms headswitch 0us trackseek 0us rps 60 ntrak 255 nsect 63 npsect 63 spc 16065 trackskew 0 interleave 1 nindir 2048 inopb 64 nspf 8 sblkno 4 cblkno 6 iblkno 8 dblkno 254 sbsize 4096 cgsize 8192 cgoffset 8 cgmask 0xffffff00 csaddr 254 cssize 4096 shift 9 mask 0xfffffe00 cgrotor 0 fmod 0 ronly 0 Note that fragment size (fsize) has to be 4096 to get past newfs. This machine is also not very stable, so perhaps the 255 head geometry should be avoided. This is with FreeBSD 1.1. Jonas From owner-freebsd-hackers Tue Jan 24 15:00:52 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id PAA14203 for hackers-outgoing; Tue, 24 Jan 1995 15:00:52 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id PAA14197 for ; Tue, 24 Jan 1995 15:00:50 -0800 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id OAA22888; Tue, 24 Jan 1995 14:59:52 -0800 From: Poul-Henning Kamp Message-Id: <199501242259.OAA22888@ref.tfs.com> Subject: Re: disklabel (1.1.5.1), partitions To: ljo@po.cwru.edu Date: Tue, 24 Jan 1995 14:59:51 -0800 (PST) Cc: terry@cs.weber.edu, bde@zeta.org.au, freebsd-hackers@freefall.cdrom.com, kuku@gilberto.physik.rwth-aachen.de In-Reply-To: <199501242203.RAA08717@amcell2.caisr.cwru.edu> from "L Jonas Olsson" at Jan 24, 95 05:03:24 pm Content-Type: text Content-Length: 424 Sender: hackers-owner@FreeBSD.org Precedence: bulk > The problem is that you will get newfs into some strange corners if you > report for instance 255 heads, as most of the ">1GB" stuff does... > > It is possible to use this geometry. I have one here (aic6360 > controller on ZEOS MB): Yes, possible, but not desireable. -- Poul-Henning Kamp TRW Financial Systems, Inc. FreeBSD has, until now, not one single time had an undetected error. :-) From owner-freebsd-hackers Tue Jan 24 15:10:13 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id PAA14354 for hackers-outgoing; Tue, 24 Jan 1995 15:10:13 -0800 Received: from devnull.mpd.tandem.com (devnull.mpd.tandem.com [131.124.4.29]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id PAA14348 for ; Tue, 24 Jan 1995 15:10:05 -0800 Received: from olympus by devnull.mpd.tandem.com (8.6.8/8.6.6) id QAA21033; Tue, 24 Jan 1995 16:21:30 -0600 Received: by olympus (4.1/TSS2.1) id AA13016; Tue, 24 Jan 95 16:20:07 CST From: faulkner@mpd.tandem.com (Boyd Faulkner) Message-Id: <9501242220.AA13016@olympus> Subject: Re: Assembler error To: wkk@eng.warwick.ac.uk Date: Tue, 24 Jan 1995 16:20:06 -0600 (CST) Cc: hackers@FreeBSD.org In-Reply-To: <11463.9501241600@eng.warwick.ac.uk> from "wkk@eng.warwick.ac.uk" at Jan 24, 95 04:00:23 pm X-Mailer: ELM [version 2.4 PL17] Content-Type: text Content-Length: 2038 Sender: hackers-owner@FreeBSD.org Precedence: bulk Are you using the ancient FreeBSD assembler or the recommended binutils-2.5.2 compiled to cross assemble for mach. That cleared this up for me. Boyd > > Hello, > I am trying to compile mach4 server on FreeBSD. Theoretically it should > compile but I get the following error in file that has some assembler code. I > am not an assembler expert but looking at the error it look likes the assembler > is getting confused with the text and data segment (I think). Can anyone help? > > Thanks very much. > > khondkar. > > ************************************************************************ > error > ************************************************************************ > gcc -c -MD -DHAVE_VPRINTF=1 -DHAVE_STRERROR=1 -Di386 -DMACH -DCMU -I- -I. -I../../mach4-i386/boot -I../../mach4-i386/include -I../../mach4/include -nostdinc -DASSEMBLER -MD ../../mach4-i386/boot/bmod_head.S > assertion "seg == SEG_DATA || seg == SEG_TEXT" failed: file "/usr/src/gnu/usr.bin/as/subsegs.c", line 174 > gcc: Internal compiler error: program as got fatal signal 6 > gmake[1]: *** [bmod_head.o] Error 1 > gmake[1]: Leaving directory `/usr/src/local/mach4-obj/boot' > gmake: *** [install_subdirs] Error 1 > > ************************************************************************ > assembler file while it gets bombed out > ************************************************************************ > > #include > > .globl _mach_bmod_text,_mach_bmod_data,_mach_bmod_bss > > .text > .align 4 > _mach_bmod_text: > > .data > .align 4 > _mach_bmod_data: > .long BMOD_MAGIC > .long _mach_bmod_init > .long _mach_bmod_text > .long _mach_bmod_etext > .long _mach_bmod_data > .long _mach_bmod_edata > .long _mach_bmod_bss > .long _mach_bmod_ebss > > .bss > .align 4 > _mach_bmod_bss: > > -- _______________________________________________________________________ Boyd Faulkner faulkner@isd.tandem.com _______________________________________________________________________ From owner-freebsd-hackers Tue Jan 24 16:56:57 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id QAA16479 for hackers-outgoing; Tue, 24 Jan 1995 16:56:57 -0800 Received: from cabri.obs-besancon.fr (cabri.obs-besancon.fr [193.52.184.3]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id QAA16469 for ; Tue, 24 Jan 1995 16:56:06 -0800 Received: by cabri.obs-besancon.fr (5.57/Ultrix3.0-C) id AA21321; Wed, 25 Jan 95 01:52:46 +0100 Date: Wed, 25 Jan 95 01:52:46 +0100 From: jmz@cabri.obs-besancon.fr (Jean-Marc Zucconi) Message-Id: <9501250052.AA21321@cabri.obs-besancon.fr> To: hackers@FreeBSD.org Subject: Joystick driver available Sender: hackers-owner@FreeBSD.org Precedence: bulk Hi fellow gamers! I have uploaded a joystick driver at ftp.cdrom.com: /pub/FreeBSD/incoming/joystick.tar.gz Jean-Marc. -- ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~ Jean-Marc Zucconi | jmz@cabri.obs-besancon.fr Observatoire de Besancon | F 25010 Besancon cedex | PGP Key: finger jmz@cabri.obs-besancon.fr ========================================================================= From owner-freebsd-hackers Tue Jan 24 17:31:16 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id RAA19952 for hackers-outgoing; Tue, 24 Jan 1995 17:31:16 -0800 Received: from ns.gte.com (ns.gte.com [132.197.8.9]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id RAA19941 for ; Tue, 24 Jan 1995 17:31:10 -0800 Received: from bunny.gte.com by ns.gte.com (5.65c/IDA-1.4.4) id AA29039; Tue, 24 Jan 1995 20:29:07 -0500 Received: by bunny.gte.com (8.6.9/GTEL2.19) id UAA07953; Tue, 24 Jan 1995 20:30:31 -0500 Received: from localhost by genesis.nred.ma.us (8.3/genesis0.0) id UAA12517; Tue, 24 Jan 1995 20:19:31 -0800 Date: Tue, 24 Jan 1995 20:19:31 -0800 From: steve2@genesis.nred.ma.us (Steve Gerakines) Message-Id: <199501250419.UAA12517@genesis.nred.ma.us> To: freebsd-hackers@FreeBSD.org Subject: Re: Floppy tape probe patch Sender: hackers-owner@FreeBSD.org Precedence: bulk > Hmmmm. Perhaps fd should also poll. On the other hand, polling the > FDC is dangerous (the danger is only being eliminated by in_fdc() > watching thoroughly for the ready-for-input bit), since many FDC's > tend to lock up if someone requests ``unusual'' things (e.g. SENSEI > where no interrupt happened) from them. Unfortunately looking at dio didn't help. Apparently once a command has been issued, dio doesn't change until a sense interrupt is issued and you pull off st0 and the cylinder number. This is why ft was blasting sense interrupt commands until it finally succeeded instead of just testing msr. The timeouts seem to work fine for fd so I wouldn't bother messing with it. Guaranteed we would end up breaking something that wasn't broken in the first place. :-) - Steve steve2@genesis.nred.ma.us From owner-freebsd-hackers Tue Jan 24 17:44:38 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id RAA21544 for hackers-outgoing; Tue, 24 Jan 1995 17:44:38 -0800 Received: from time.cdrom.com (time.cdrom.com [192.216.223.46]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id RAA21538 for ; Tue, 24 Jan 1995 17:44:37 -0800 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.9/8.6.9) with SMTP id RAA14684; Tue, 24 Jan 1995 17:44:27 -0800 To: jmz@cabri.obs-besancon.fr (Jean-Marc Zucconi) cc: hackers@FreeBSD.org Subject: Re: Joystick driver available In-reply-to: Your message of "Wed, 25 Jan 95 01:52:46 +0100." <9501250052.AA21321@cabri.obs-besancon.fr> Date: Tue, 24 Jan 1995 17:44:27 -0800 Message-ID: <14683.790998267@time.cdrom.com> From: "Jordan K. Hubbard" Sender: hackers-owner@FreeBSD.org Precedence: bulk Awesome! This was actually on my wish list from some time back, then I just sort of gave up on it.. Would you care to commit this? If you're hesitant about assigning the major/minor number (just take the next free one, pretty easy really) then I'd be willing to do it for you. Either way I'd like to have this as an option! Good work, Jean-Marc! Jordan > Hi fellow gamers! > > I have uploaded a joystick driver at ftp.cdrom.com: > /pub/FreeBSD/incoming/joystick.tar.gz > > Jean-Marc. > > -- > ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~ > Jean-Marc Zucconi | jmz@cabri.obs-besancon.fr > Observatoire de Besancon | > F 25010 Besancon cedex | PGP Key: finger jmz@cabri.obs-besancon.fr > ========================================================================= From owner-freebsd-hackers Tue Jan 24 17:44:24 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id RAA21508 for hackers-outgoing; Tue, 24 Jan 1995 17:44:24 -0800 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id RAA21490 for ; Tue, 24 Jan 1995 17:44:20 -0800 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.8/8.6.6) id BAA11440; Wed, 25 Jan 1995 01:43:31 GMT From: "Rodney W. Grimes" Message-Id: <199501250143.BAA11440@gndrsh.aac.dev.com> Subject: Re: disklabel (1.1.5.1), partitions To: julian@tfs.com (Julian Elischer) Date: Wed, 25 Jan 1995 01:43:31 +0000 (GMT) Cc: kuku@gilberto.physik.rwth-aachen.de, freebsd-hackers@freefall.cdrom.com In-Reply-To: from "Julian Elischer" at Jan 24, 95 11:07:44 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1830 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > > > > > > I had disk problems on 'gil' recently (hopefully solved) - reformatted > > a Fuji M2694S using SCSICNTL. > > > > I was wondering about the following when disklabeling again: > > > > dmesg told me: > > > > 2117025 1819 cyl 15 heads 77 sec > > > > Using these figures in a disktab entry resulted in a warning saying that > > partitions c,d,e exceeded end of disk. (I made them p[cde]#2117025). > > > > So I reduced them to what 15 * 77 * 1819 calculates to, namely 2100945 > > and disklabel kept silent. > > > > Did I give away some sectors ? > > > Unfortunatly yes... Infact you gave away 2117025 - ( 15 * 77 * 1819) = 16080 sectors, if you had used a translation of (64 heads * 32 sectors * 1033 cyl) you would have only given away 1441 sectors. > the question is "What do we do with disks with variable geometries.. > especially when the disklabel code assumes it is a fixed geometry. > > we calculate an 'average' number of setors per track.. > but it has to be an integer, and that truncation leads to a bunch of > unused sectors.. And this rounded integer is one of the worse things to use when creating a disklabel for the fact that you may give away up to (cyl * head) - 1 sectors instead of the max of translated head * sec when using translated or fictitios geometries. I highly recomened to anyone using the probe reported geometry to think twice and convert to a 32 sector 64 head geometry. > julian > > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de > > FreeBSD blues 2.1.0-Development FreeBSD 2.1.0-Development #1: > > Wed Jan 18 10:42:31 1995 kuku@blues:/usr/src/sys/compile/BLUES i386 > > > > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-hackers Tue Jan 24 21:22:33 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id VAA01367 for hackers-outgoing; Tue, 24 Jan 1995 21:22:33 -0800 Received: from goof.com (root@goof.com [198.82.204.15]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id VAA01353 for ; Tue, 24 Jan 1995 21:22:28 -0800 Received: (from mmead@localhost) by goof.com (8.6.9/8.6.9) id AAA00482 for hackers@freebsd.org; Wed, 25 Jan 1995 00:22:24 -0500 From: "matthew c. mead" Message-Id: <199501250522.AAA00482@goof.com> Subject: Motherboards To: hackers@FreeBSD.org Date: Wed, 25 Jan 1995 00:22:23 -0500 (EST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1279 Sender: hackers-owner@FreeBSD.org Precedence: bulk With all the recent discussion about the faulty, unreliable motherboard I was recently unfortunate to purchase, I've been wondering what a really good motherboard to use with FreeBSD is. I'll be returning this "gem" of a motherboard as soon as I get one in that works really well. My options are as follows: a straight VLB motherboard that has 8 SIMM slots, and can handle 4 4M SIMMs and 4 1M SIMMs; a PCI motherboard that's got some VLB slots, that can handle 30 pin SIMMs and 72 pin SIMMs, preferably lots of both; or a PCI motherboard that has no VLB slots, but has an onboard scsi that will work well with FreeBSD and can handle some 30 pin SIMMs. As far as what I want the board to be like goes, I'd just like one that has a fast cache, can support of to 1M of cache, but comes with either 256K or 512K, has a BIOS that will work well with FreeBSD, and is pretty reliable and so forth, so as not to act flakey under FreeBSD (where my machine spends 99.9% of its time). Anyone have any suggestions? Thanks, I appreciate it greatly! -matt -- Matthew C. Mead -- System/Network Administration, User Support, Software Devel. Virginia Tech Center for Transportation Research Work Related: mmead@ctr.vt.edu | All Other: mmead@goof.com WWW: http://www.goof.com:/~mmead From owner-freebsd-hackers Tue Jan 24 21:34:26 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id VAA02377 for hackers-outgoing; Tue, 24 Jan 1995 21:34:26 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id VAA02363 for ; Tue, 24 Jan 1995 21:34:09 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id QAA17692; Wed, 25 Jan 1995 16:32:12 +1100 Date: Wed, 25 Jan 1995 16:32:12 +1100 From: Bruce Evans Message-Id: <199501250532.QAA17692@godzilla.zeta.org.au> To: hackers@FreeBSD.org, wkk@eng.warwick.ac.uk Subject: Re: Assembler error Sender: hackers-owner@FreeBSD.org Precedence: bulk > I am trying to compile mach4 server on FreeBSD. Theoretically it should >compile but I get the following error in file that has some assembler code. I >am not an assembler expert but looking at the error it look likes the assembler >is getting confused with the text and data segment (I think). Can anyone help? > .bss > .align 4 >_mach_bmod_bss: The .bss directive isn't really supported by gas. I seem to remember that it used to be ignored. Now it is fatal. You could try removing it, but there are likely to be problems with code that was supposed to be in the bss section. Space in the bss section must be reserved using the directives .comm and .lcomm, not using .space or .long etc. Putting a label at the start of the bss section is difficult. Normally the label `_edata' is (ab)used. Bruce From owner-freebsd-hackers Tue Jan 24 22:09:47 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id WAA02816 for hackers-outgoing; Tue, 24 Jan 1995 22:09:47 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id WAA02810 for ; Tue, 24 Jan 1995 22:09:36 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id RAA18320; Wed, 25 Jan 1995 17:07:52 +1100 Date: Wed, 25 Jan 1995 17:07:52 +1100 From: Bruce Evans Message-Id: <199501250607.RAA18320@godzilla.zeta.org.au> To: bde@zeta.org.au, terry@cs.weber.edu Subject: Re: More serial console stuff... Cc: freebsd-hackers@FreeBSD.org, rgrimes@gndrsh.aac.dev.com Sender: hackers-owner@FreeBSD.org Precedence: bulk >For example, say I have no built in controller in the system and two SCSI >controllers that support chaining. >Each SCSI controller has two identical drives on it. >The kernel is loaded via BIOS and is passed drive ID 0x82. >On which controller does this drive reside? >The actual residence of the drive is determined by BIOS chaining order. >The apparent-to-the-kernel residence of the drive is dependent on the >controller probe order. >Now do you see what I mean? It's what I thought I said :-). There is no standard way to decide how the drives are mapped. We're not going to be able to decide without asking the user. Bruce From owner-freebsd-hackers Tue Jan 24 23:11:09 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id XAA03746 for hackers-outgoing; Tue, 24 Jan 1995 23:11:09 -0800 Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id XAA03735 for ; Tue, 24 Jan 1995 23:11:02 -0800 Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.8/8.6.6) id CAA02379; Wed, 25 Jan 1995 02:07:04 -0500 From: Wankle Rotary Engine Message-Id: <199501250707.CAA02379@skynet.ctr.columbia.edu> Subject: Re: Is this a bug?!? To: bde@zeta.org.au (Bruce Evans) Date: Wed, 25 Jan 1995 02:07:01 -0500 (EST) Cc: freebsd-hackers@FreeBSD.org In-Reply-To: <199501240536.QAA10618@godzilla.zeta.org.au> from "Bruce Evans" at Jan 24, 95 04:36:02 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 4687 Sender: hackers-owner@FreeBSD.org Precedence: bulk They say this Bruce Evans person was kidding when he wrote: > > >that writing to /dev/ttyv0 actually causes the kernel to go from > >write(), to vn_write(), to ffsspec_write(), to spec_write(), to cn_write(), > >to scwrite(), to ttwrite() and then to b_to_q() and a panic. The > > This layering seems excessive. A man after my own heart! This isn't the end of the line either. Normally (without panics) ttwrite() would eventually get to putc(), which would then find its way back to syscons and scput(). It looks to me though that there's no way to improve on this without changing a huge number of related things. > 0/0 is correct for the console. It gets translated to 12/0 in cons.c. > The current version of syscons, and all versions of sio, cannot tell > if they are working with the 0/0 device, and this causes problems when > the 12/0 device is closed while the 0/0 device is open or vice versa. > I fixed this, but now the process group info for the 12/0 device doesn't > go away when the 12/0 device is closed, and TIOCSTTY fails in login_tty(). > > Bruce "My lord, I have a cunning plan." Hurm. Okay, I think I have a fix for this (conceptually at least: I only just now managed to wrap my brain around this whole process in a satisfactory manner, and now I'm too tired to code). I think the answer is to stop trying to share one tty struct between what are fast becoming two seperate devices and instead give /dev/console a tty struct of its very own. (I wonder if we should start thinking of giving it a devconf entry too... maybe later -- one disgusting hack at a time. :) There's a small amount of nastiness in what I have in mind, but it's far better than throwing in a ton of special case handling code to keep /dev/console and its associated physical device from tripping over each other. First off, I like the idea of wedging cn{open, close}() in between spec_{open, close}() and sc{open,close}(). But I think that having cnopen() 'lie' to the underlying device driver is a Bad Thing: it always passes 12/0 to scopen() as a device value, which means that there's no way for syscons to know if it's dealing with /dev/ttyv0 or /dev/console. Yes, I know this would mean tying different device drivers together in a disgusting way, but cons.c can't handle this by itself. What I propose is this: - Have cons.c declare a tty struct for itself (thus eating up a small chunk of memory. oh well). - Pass the real device value to the underlying driver. (0/0, 12/0 or 28/0, depending on the circumstances) - Let scopen() (and sioopen()) test the value of 'dev' that's passed to it: if it's given a device with a major value of 0, then it knows that it's being asked to handle the console, and it can point 'tp' at the console's tty struct instead of one of its own array of tty structs. If major(dev) isn't 0, then go about business as usual. - Implement similar hackery for scclose() (and sioclose()). I think this would prevent the process group info straight (you'd no longer have to worry about the two different open and close calls clobbering each other since you'd have two independent sets of data -- I don't see an immediate problem with this, but then again I'm also half asleep). If done right, it should also allow for the correct t_dev value to show up in the process table, which would solve the problem of 'w' not working right when using /dev/console as a real live login device. This in turn would allow me to implement my Master Plan (tm), which is to actually have people *use* /dev/console as a login device. (Call me crazy, but "Last login on console" just looks cooler than "Last login on ttyv0.") Finally, this would keep all the changes isloated to the i386-specific code, which is a pretty good idea since this is largely an i386-specific bug. :) I can see only one problem with all this: it would break PCVT, though hopefully not so badly that the PCVT author would be seized with an irresistable urge to hunt me down and force me to watch Highlander II until my eyes bleed. Tomorrow I'll take a whack at this to see if it'll actually work. "So what do you think sirs?" -Bill -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~T~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Bill Paul (212) 854-6020 | System Manager Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The Møøse Illuminati: ignore it and be confused, or join it and be confusing! ~~~~~~~~ FreeBSD 2.1.0-Development #1: Fri Jan 20 14:28:17 EST 1995 ~~~~~~~~~ From owner-freebsd-hackers Wed Jan 25 00:06:00 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id AAA04533 for hackers-outgoing; Wed, 25 Jan 1995 00:06:00 -0800 Received: from cleese.apana.org.au (root@cleese.apana.org.au [192.203.213.4]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id AAA04526 for ; Wed, 25 Jan 1995 00:05:46 -0800 Received: by cleese.apana.org.au id AA07124 (5.67a/IDA-1.5 for hackers@freebsd.org); Wed, 25 Jan 1995 18:36:11 +1030 Date: Wed, 25 Jan 1995 18:36:11 +1030 From: Mark Newton Message-Id: <199501250806.AA07124@cleese.apana.org.au> To: hackers@FreeBSD.org Subject: Kernel changes between 2.0-RELEASE and snapshot Sender: hackers-owner@FreeBSD.org Precedence: bulk Hi, Guys. Time permitting, could someone please forward me a list of kernel changes and/or bug fixes between 2.0-RELEASE and the latest snapshot? I'm having stability problems on my public access UNIX, and it'd be nice if changes in the latest release have fixed 'em. Many thanks, - mark From owner-freebsd-hackers Wed Jan 25 00:35:37 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id AAA04895 for hackers-outgoing; Wed, 25 Jan 1995 00:35:37 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id AAA04889 for ; Wed, 25 Jan 1995 00:35:30 -0800 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id AAA28518; Wed, 25 Jan 1995 00:35:23 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.9/8.6.5) with SMTP id AAA06007; Wed, 25 Jan 1995 00:35:23 -0800 Message-Id: <199501250835.AAA06007@corbin.Root.COM> X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol To: Mark Newton cc: hackers@FreeBSD.org Subject: Re: Kernel changes between 2.0-RELEASE and snapshot In-reply-to: Your message of "Wed, 25 Jan 95 18:36:11 +1030." <199501250806.AA07124@cleese.apana.org.au> From: David Greenman Reply-To: davidg@Root.COM Date: Wed, 25 Jan 1995 00:35:22 -0800 Sender: hackers-owner@FreeBSD.org Precedence: bulk >Time permitting, could someone please forward me a list of kernel changes >and/or bug fixes between 2.0-RELEASE and the latest snapshot? I'm having >stability problems on my public access UNIX, and it'd be nice if changes >in the latest release have fixed 'em. Hmmm...well, we don't have such a list. If you are interested in hearing about the changes as they happen, you should subscribe to the CVS commit mailing list - this way you will get the log messages via email when they happen. Other than a general 'new features' summary that is provided with each new release, the CVS commit log is the only description of the changes being made to the FreeBSD source tree. I'm not aware of any bugs that cause 'hangs' in 2.0 that prevent you from entering the kernel debugger...not to say that one doesn't exist...but I haven't seen or heard of any (other than with your report). Are you sure that you are attempting to enter the debugger correctly? And you are sure that you have DDB in your kernel config file? Just making sure... On the positive note, there have been a large number of bug fixes since 2.0-release. The latest snapshot has serious problems, however, and while the next one should be the best one yet, I'm not sure that it would be wise to switch to it (considering the kind of load that your machine is experiancing) until the code has been shaken out a bit more. ...On the other hand, testing on a machine with a high load such as yours is good way to ensure that the bugs that do exist are fixed before the 2.1 release. Whether or not you wish to be involved in this is a different matter, however. :-) -DG From owner-freebsd-hackers Wed Jan 25 00:59:06 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id AAA05376 for hackers-outgoing; Wed, 25 Jan 1995 00:59:06 -0800 Received: from campino.informatik.rwth-aachen.de (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id AAA05368 for ; Wed, 25 Jan 1995 00:59:01 -0800 Received: from gilberto.physik.rwth-aachen.de by campino.informatik.rwth-aachen.de (4.1/campino-6) id AA24870; Wed, 25 Jan 95 09:58:55 +0100 Received: by gilberto.physik.rwth-aachen.de (KAA13741); Wed, 25 Jan 1995 10:05:24 +0100 Message-Id: <199501250905.KAA13741@gilberto.physik.rwth-aachen.de> Subject: Re: Joystick driver available To: jmz@cabri.obs-besancon.fr (Jean-Marc Zucconi) Date: Wed, 25 Jan 1995 10:05:23 +0100 (MET) Cc: freebsd-hackers@freefall.cdrom.com (user alias) Reply-To: kuku@gilberto.physik.rwth-aachen.de In-Reply-To: <9501250052.AA21321@cabri.obs-besancon.fr> from "Jean-Marc Zucconi" at Jan 25, 95 01:52:46 am From: Christoph Kukulies Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 845 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > Hi fellow gamers! > > I have uploaded a joystick driver at ftp.cdrom.com: > /pub/FreeBSD/incoming/joystick.tar.gz Thinking of possible applications (other than games) of a joy stick: Input device for X11. Does anyone know how to make X see it? > > Jean-Marc. > > -- > ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~ > Jean-Marc Zucconi | jmz@cabri.obs-besancon.fr > Observatoire de Besancon | > F 25010 Besancon cedex | PGP Key: finger jmz@cabri.obs-besancon.fr > ========================================================================= > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de FreeBSD blues 2.1.0-Development FreeBSD 2.1.0-Development #1: Wed Jan 18 10:42:31 1995 kuku@blues:/usr/src/sys/compile/BLUES i386 From owner-freebsd-hackers Wed Jan 25 02:08:42 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id CAA07444 for hackers-outgoing; Wed, 25 Jan 1995 02:08:42 -0800 Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.20.4]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id CAA07437 for ; Wed, 25 Jan 1995 02:08:36 -0800 Received: by brasil.moneng.mei.com (4.1/SMI-4.1) id AA15631; Wed, 25 Jan 95 04:04:38 CST From: Joe Greco Message-Id: <9501251004.AA15631@brasil.moneng.mei.com> Subject: Re: Joystick driver available To: kuku@gilberto.physik.rwth-aachen.de Date: Wed, 25 Jan 1995 04:04:37 -0600 (CST) Cc: jmz@cabri.obs-besancon.fr, freebsd-hackers@freefall.cdrom.com In-Reply-To: <199501250905.KAA13741@gilberto.physik.rwth-aachen.de> from "Christoph Kukulies" at Jan 25, 95 10:05:23 am X-Mailer: ELM [version 2.4beta PL9] Content-Type: text Content-Length: 881 Sender: hackers-owner@FreeBSD.org Precedence: bulk > Thinking of possible applications (other than games) of a joy stick: > > Input device for X11. > > Does anyone know how to make X see it? It depends on how it is implemented (and how easily XF86 would be adapted)... speaking as somebody who has done multiheaded touchscreen implementations for Sun workstaions, I would guess that it would be somewhat trivial, but would probably require XF86 mods... A neat thing to do might be to make it "look" like a serial mouse (ioctl or something?).... that would allow it to be used with XF86 without any further modifications. Cool way to do it, at least for certain applications. ... Joe ------------------------------------------------------------------------------- Joe Greco - The Data Capture Fellow (and UNIX/Network Hacker) 414/362-3617 Marquette Electronics, Inc. - Milwaukee, WI jgreco@brasil.moneng.mei.com From owner-freebsd-hackers Wed Jan 25 03:03:29 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id DAA08072 for hackers-outgoing; Wed, 25 Jan 1995 03:03:29 -0800 Received: from campino.informatik.rwth-aachen.de (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id DAA08057 for ; Wed, 25 Jan 1995 03:03:26 -0800 Received: from gilberto.physik.rwth-aachen.de by campino.informatik.rwth-aachen.de (4.1/campino-6) id AA26549; Wed, 25 Jan 95 12:00:36 +0100 Received: by gilberto.physik.rwth-aachen.de (MAA13952); Wed, 25 Jan 1995 12:07:06 +0100 Message-Id: <199501251107.MAA13952@gilberto.physik.rwth-aachen.de> Subject: Re: Joystick driver available To: jgreco@brasil.moneng.mei.com (Joe Greco) Date: Wed, 25 Jan 1995 12:07:05 +0100 (MET) Cc: freebsd-hackers@freefall.cdrom.com (user alias) In-Reply-To: <9501251004.AA15631@brasil.moneng.mei.com> from "Joe Greco" at Jan 25, 95 04:04:37 am From: Christoph Kukulies Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1208 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > > Thinking of possible applications (other than games) of a joy stick: > > > > Input device for X11. > > > > Does anyone know how to make X see it? > > It depends on how it is implemented (and how easily XF86 would be > adapted)... speaking as somebody who has done multiheaded touchscreen How would the Xaccel server (Xinside, Inc.) cope with that? (Jeremy?) > implementations for Sun workstaions, I would guess that it would be somewhat > trivial, but would probably require XF86 mods... > > A neat thing to do might be to make it "look" like a serial mouse (ioctl or > something?).... that would allow it to be used with XF86 without any > further modifications. Cool way to do it, at least for certain > applications. > > ... Joe > > ------------------------------------------------------------------------------- > Joe Greco - The Data Capture Fellow (and UNIX/Network Hacker) 414/362-3617 > Marquette Electronics, Inc. - Milwaukee, WI jgreco@brasil.moneng.mei.com > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de FreeBSD blues 2.1.0-Development FreeBSD 2.1.0-Development #1: Wed Jan 18 10:42:31 1995 kuku@blues:/usr/src/sys/compile/BLUES i386 From owner-freebsd-hackers Wed Jan 25 03:03:29 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id DAA08069 for hackers-outgoing; Wed, 25 Jan 1995 03:03:29 -0800 Received: from campino.informatik.rwth-aachen.de (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id DAA08051 for ; Wed, 25 Jan 1995 03:03:25 -0800 Received: from gilberto.physik.rwth-aachen.de by campino.informatik.rwth-aachen.de (4.1/campino-6) id AA26461; Wed, 25 Jan 95 11:50:11 +0100 Received: by gilberto.physik.rwth-aachen.de (LAA13917); Wed, 25 Jan 1995 11:56:41 +0100 Date: Wed, 25 Jan 1995 11:56:41 +0100 From: "Christoph P. Kukulies" Message-Id: <199501251056.LAA13917@gilberto.physik.rwth-aachen.de> To: freebsd-hackers@freefall.cdrom.com Subject: nfs: can't access Sender: hackers-owner@FreeBSD.org Precedence: bulk I wanted to make my life a bit easier in bringing ports to the various 2.0 machines in our network by doing the following: NFS server blues: /etc/exports: /home/ports-2.0 maproot=root mozart otherhost NFS client mozart: (snap-19950120) mozart#> mount blues:/home/ports-2.0 /home/ports-2.0 nfs: can't access /home/ports-2.0: Address already in use mozart#> removing the maproot from /etc/exports allows the mount to finish correctly. But executing make install (after removing work/.install_done) from e.g. /home/ports-2.0/mail/elm always wants to load the distribution from the site rather than seeing that the distribution is already in /home/ports-2.0/distfiles. What's wrong here? --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de FreeBSD blues 2.1.0-Development FreeBSD 2.1.0-Development #1: Wed Jan 18 10:42:31 1995 kuku@blues:/usr/src/sys/compile/BLUES i386 From owner-freebsd-hackers Wed Jan 25 08:50:34 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id IAA00250 for hackers-outgoing; Wed, 25 Jan 1995 08:50:34 -0800 Received: from seagull.rtd.com (root@Seagull.rtd.com [198.102.68.2]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id IAA00244 for ; Wed, 25 Jan 1995 08:50:30 -0800 Received: (from dgy@localhost) by seagull.rtd.com (8.6.9/8.6.9.1) id IAA26765; Wed, 25 Jan 1995 08:11:01 -0700 From: Don Yuniskis Message-Id: <199501251511.IAA26765@seagull.rtd.com> Subject: Re: Motherboards To: mmead@goof.com (matthew c. mead) Date: Wed, 25 Jan 1995 08:11:01 -0700 (MST) Cc: freebsd-hackers@freefall.cdrom.com (FreeBSD hackers) In-Reply-To: <199501250522.AAA00482@goof.com> from "matthew c. mead" at Jan 25, 95 00:22:23 am X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1318 Sender: hackers-owner@FreeBSD.org Precedence: bulk > With all the recent discussion about the faulty, unreliable motherboard I > was recently unfortunate to purchase, I've been wondering what a really good > motherboard to use with FreeBSD is. I'll be returning this "gem" of a > motherboard as soon as I get one in that works really well. My options are as > follows: a straight VLB motherboard that has 8 SIMM slots, and can handle 4 4M > SIMMs and 4 1M SIMMs; a PCI motherboard that's got some VLB slots, that can > handle 30 pin SIMMs and 72 pin SIMMs, preferably lots of both; or a PCI > motherboard that has no VLB slots, but has an onboard scsi that will work well > with FreeBSD and can handle some 30 pin SIMMs. As far as what I want the board > to be like goes, I'd just like one that has a fast cache, can support of to 1M Seems like you could better spend your money on extra DRAM instead of a huge ^^ cache... I doubt the gains when you exceed 128K of cache justify the expense relative to the gains some extra (regular) memory can bring.... (my $0.02) > of cache, but comes with either 256K or 512K, has a BIOS that will work well > with FreeBSD, and is pretty reliable and so forth, so as not to act flakey > under FreeBSD (where my machine spends 99.9% of its time). Anyone have any > suggestions? Thanks, I appreciate it greatly! G'Luck... From owner-freebsd-hackers Wed Jan 25 08:59:49 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id IAA00716 for hackers-outgoing; Wed, 25 Jan 1995 08:59:49 -0800 Received: from campino.informatik.rwth-aachen.de (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id IAA00701 for ; Wed, 25 Jan 1995 08:59:46 -0800 Received: from gilberto.physik.rwth-aachen.de by campino.informatik.rwth-aachen.de (4.1/campino-6) id AA29043; Wed, 25 Jan 95 15:56:50 +0100 Received: by gilberto.physik.rwth-aachen.de (QAA14268); Wed, 25 Jan 1995 16:03:20 +0100 Date: Wed, 25 Jan 1995 16:03:20 +0100 From: "Christoph P. Kukulies" Message-Id: <199501251503.QAA14268@gilberto.physik.rwth-aachen.de> To: freebsd-hackers@freefall.cdrom.com Subject: elm under 2.x-current Sender: hackers-owner@FreeBSD.org Precedence: bulk Anyone using the elm-2.4 from ports? I installed it on a snap-950120 system and elm seems to have problems with /var/mail. I wanted to peek into freefall or thud to look at the permissions of /usr/local/bin/elm and /var/mail but the Internet links were so terribly slow today that I gave up. When there is a file /var/mail/user elm waits in a lock loop waiting for access to the file and gives up after 7 tries. I don't know whether this is due to the file locking method I chose during elm configuration (flock) and this may have been wrong or what the issue is here. I'll give it another try without file locking (or another method) now. --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de FreeBSD blues 2.1.0-Development FreeBSD 2.1.0-Development #1: Wed Jan 18 10:42:31 1995 kuku@blues:/usr/src/sys/compile/BLUES i386 From owner-freebsd-hackers Wed Jan 25 09:01:34 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id JAA00974 for hackers-outgoing; Wed, 25 Jan 1995 09:01:34 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id JAA00961 for ; Wed, 25 Jan 1995 09:01:32 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA18604; Wed, 25 Jan 95 09:28:41 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9501251628.AA18604@cs.weber.edu> Subject: Re: Is this a bug?!? To: wpaul@skynet.ctr.columbia.edu (Wankle Rotary Engine) Date: Wed, 25 Jan 95 9:28:40 MST Cc: bde@zeta.org.au, freebsd-hackers@FreeBSD.org In-Reply-To: <199501250707.CAA02379@skynet.ctr.columbia.edu> from "Wankle Rotary Engine" at Jan 25, 95 02:07:01 am X-Mailer: ELM [version 2.4dev PL52] Sender: hackers-owner@FreeBSD.org Precedence: bulk > "My lord, I have a cunning plan." > > Hurm. Okay, I think I have a fix for this (conceptually at least: I > only just now managed to wrap my brain around this whole process in a > satisfactory manner, and now I'm too tired to code). I think the answer > is to stop trying to share one tty struct between what are fast becoming > two seperate devices and instead give /dev/console a tty struct of its > very own. (I wonder if we should start thinking of giving it a devconf > entry too... maybe later -- one disgusting hack at a time. :) There's a > small amount of nastiness in what I have in mind, but it's far better > than throwing in a ton of special case handling code to keep /dev/console > and its associated physical device from tripping over each other. [ ... ] > "So what do you think sirs?" "Baldric, you wouldn't know a cunning plan if it danced on the table singing 'cunning plans are here again'". 8-) 8-). Actually, this is probably close to the right way to do it; you really want to seperate the cannonical processing module from the driver implementation. Sort of like 'ldterm' for streams devices. This doesn't necessarily end with a different tty struct for each of the drivers (this would be rather painful), but it does allow a single device to (potentially) be output to by multiple modules (like whatever it normally gets plus the console). In reality, you probably want the console device to be considered as an opener of the device: ,------------. ,------------. | console | | tty | `------------' `------------' ,------------. ,------------. | cannonical | | cannonical | `------------' `------------' \ / \ / \ / \ / \/ ,-------------. | real device | `-------------' With each "real device" having the same interface for consumption by the cannonical processing modules. A cannonical processing module, in this case, becomes simply another line discipline (like SLIP or PPP or DDCMP) and is divorced from the actual device processing. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Jan 25 09:01:36 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id JAA00981 for hackers-outgoing; Wed, 25 Jan 1995 09:01:36 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id JAA00972 for ; Wed, 25 Jan 1995 09:01:34 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA18405; Wed, 25 Jan 95 09:07:11 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9501251607.AA18405@cs.weber.edu> Subject: Re: More serial console stuff... To: phk@ref.tfs.com (Poul-Henning Kamp) Date: Wed, 25 Jan 95 9:07:11 MST Cc: bde@zeta.org.au, freebsd-hackers@FreeBSD.org, rgrimes@gndrsh.aac.dev.com In-Reply-To: <199501251543.HAA25244@ref.tfs.com> from "Poul-Henning Kamp" at Jan 25, 95 07:43:14 am X-Mailer: ELM [version 2.4dev PL52] Sender: hackers-owner@FreeBSD.org Precedence: bulk > > There is no standard way to decide how the drives are mapped. We're > > not going to be able to decide without asking the user. > > Only the bruteforce mode: > > In bootblock: > make table of > drive-id > geometry > checksum of sector #200 > checksum of sector #400 > checksum of sector #600 > > In kernel > find entry in table where checksums match... I'd actually (and have done so) suggest determining both the translated and untranslated geometry in the boot blocks (see pfdisk.exe sources to see how this is done -- it *is* done). Then you can traverse the drives on each controller looking for matching non-translated geometries. The drive order on a particular controller ought to be invariant in moving to protected mode. A CRC (or checksum - bletch) would probably be necessary if identical devices were used on multiple controllers, or if drive chaining had occurred on the 0x80/0x81 boottable device boundry such that two bootable devices were not on the same controller. Yes, I'm ignoring the (possible) case of 0x82 ... as a boot device, since the boot blocks themselves would have to examine a potential 128 devices (0x80 - 0xff) if we were attempting to be comprehensive. Perhaps asking the number of devices via INT 13 would make this not a problem. This puts us in the territory of needing to load a much larger boot block that is still BIOS based. As an interim measure, we probably want to only consider the BSD partitions of drives, since the BSD boot blocks do not apply to anything else anyway. Ensuring a unique volume ID is not guranteed by a checksum of anything less than the 'a' slice of a BSD disk, since the DOS MBR and partition code, as well as IBMIO.SYS, and the BSD boot code should all be the same, especially in the case of identical devices. One potential soloution here is to add a random volume ID number and a time stamp to the disklabel and use these fields by themselves. I note "interim" here, since it is likely that BSD will want to support installing to non-UFS root volumes, and non-BSD managed geometries of file systems. One example would be a Linux-style umsdos install, where the BSD is non-destructively installed in a DOS directory heirarchy; this is conceptually very easy to accomplish, and destroys most of the road signs we have discussed using so far. Maybe the ultimate soloution is simply extending the search list on boot to include all drives as well as the 3 or 4 kernel names it likes to try? This would mean that it may need to try several times to do the boot, but that it would eventually succeed. Perhaps a simple timing change, such that the boot process only pauses for user override for the first kernel name attempt, instead of pausing on each attempt, would make this more palletable. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Jan 25 09:01:40 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id JAA00998 for hackers-outgoing; Wed, 25 Jan 1995 09:01:40 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id JAA00992 for ; Wed, 25 Jan 1995 09:01:38 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA18261; Wed, 25 Jan 95 08:37:55 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9501251537.AA18261@cs.weber.edu> Subject: sendmail 8.6.9 - "Name server failure" problem (fwd) To: hackers@FreeBSD.org Date: Wed, 25 Jan 95 8:37:55 MST X-Mailer: ELM [version 2.4dev PL52] Sender: hackers-owner@FreeBSD.org Precedence: bulk The following is from a friend of mine; he's already informed Eric and Paul, but I thought you might not want to wait for the next release of sendmail (or the previous release of BIND) to get your mail working. This is also a potentially generic problem for anyone moving from the old to the new resolver code for *any* application. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. ======================================================================== Forwarded message: > From mday@artisoft.com Tue Jan 24 20:49:51 1995 > Date: Tue, 24 Jan 1995 20:54:56 -0700 > From: Matt Day > Message-Id: <199501250354.UAA04640@sting.artisoft.com> > To: sendmail@CS.Berkeley.EDU > Subject: sendmail 8.6.9 - "Name server failure" problem > Cc: bind-workers@vix.com, volkerdi@mhd1.moorhead.msus.edu > > Hi, > > After upgrading my Linux system to sendmail 8.6.9 and BIND 4.9.3-BETA9 > (including the libc resolver routines), sendmail started leaving > incoming mail messages sitting in the mail queue with a "Name server > failure" error. My name server seemed to work for other applications > just fine, so this problem intrigued me. I tracked down the problem to > the hostnamebyanyaddr() routine in src/daemon.c. This routine saves the > value of _res.retry to a temporary variable and sets _res.retry to 3, > makes some resolver calls, and then restores _res.retry to its previous > value. But, the BIND 4.9.3 resolver routines no longer statically > initialize the global _res structure like older versions of the resolver > routines, leaving it to be initialized to 0 by default and later > initialized to proper values when res_init() is called. (See res_init() > in the BIND 4.9.3 code for more details.) > > So, since no resolver calls have been made at the time > hostnamebyanyaddr() gets first called, _res.retry is 0 (res_init() > hasn't been called yet), so sendmail saves _res.retry, sets it to 3, > calls a resolver routine which calls res_init(), and then restores > _res.retry to 0. Later, when sendmail makes another resolver call, > res_init() isn't called again (res_init() was called already when the > previous resolver call was made) so _res.retry gets left set to 0, which > causes the resolver routines to return the ECONNREFUSED error (because > no attempts are made to contact a name server), which sendmail > interprets as "Name server failure". > > So, the problem is hostnamebyanyaddr() assumes that _res is already > initialized to proper values, but this is no longer true as of BIND > 4.9.3. Here is a patch for sendmail 8.6.9 which changes > hostnamebyanyaddr() to make sure res_init() has been called before using > _res.retry. > > *** src/daemon.c- Mon Apr 18 06:48:41 1994 > --- src/daemon.c Tue Jan 24 19:38:06 1995 > *************** > *** 1406,1411 **** > --- 1406,1414 ---- > int saveretry; > > #if NAMED_BIND > + /* need to make sure _res.retry is initialized before using it */ > + if ((_res.options & RES_INIT) == 0) > + res_init(); > /* shorten name server timeout to avoid higher level timeouts */ > saveretry = _res.retry; > _res.retry = 3; > > Thanks, > > Matt Day > ======================================================================== From owner-freebsd-hackers Wed Jan 25 09:04:55 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id JAA01186 for hackers-outgoing; Wed, 25 Jan 1995 09:04:55 -0800 Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.20.4]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id JAA01177 for ; Wed, 25 Jan 1995 09:04:52 -0800 Received: by brasil.moneng.mei.com (4.1/SMI-4.1) id AA00571; Wed, 25 Jan 95 06:24:13 CST From: Joe Greco Message-Id: <9501251224.AA00571@brasil.moneng.mei.com> Subject: Re: Joystick driver available To: dawes@physics.su.oz.au (David Dawes) Date: Wed, 25 Jan 1995 06:24:13 -0600 (CST) Cc: kuku@gilberto.physik.rwth-aachen.de, jmz@cabri.obs-besancon.fr, freebsd-hackers@freefall.cdrom.com In-Reply-To: <199501251210.AA19077@physics.su.OZ.AU> from "David Dawes" at Jan 25, 95 11:10:47 pm X-Mailer: ELM [version 2.4beta PL9] Content-Type: text Content-Length: 1243 Sender: hackers-owner@FreeBSD.org Precedence: bulk > >A neat thing to do might be to make it "look" like a serial mouse (ioctl or > >something?).... that would allow it to be used with XF86 without any > >further modifications. Cool way to do it, at least for certain > >applications. > > We have someone working on implementing the XInput extension for XFree86. > That might be the best way to make X see it. > > David As someone who's barked up that tree before, it's not particularly great... part of the problem with the current X implementation is that there is only one conceptual cursor, and it gets a little bizarre when you would like to have multiple devices controlling it. XInput does not allow this _simultaneously_, although it does allow you to name your pointer device on the fly. (I am thinking in particular of a touchscreen and mouse combination, where one wants to have both active simultaneously, and not have to do special processing at the application level for one or the other. One of my past pet projects...). ... Joe ------------------------------------------------------------------------------- Joe Greco - The Data Capture Fellow (and UNIX/Network Hacker) 414/362-3617 Marquette Electronics, Inc. - Milwaukee, WI jgreco@brasil.moneng.mei.com From owner-freebsd-hackers Wed Jan 25 09:15:21 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id JAA01963 for hackers-outgoing; Wed, 25 Jan 1995 09:15:21 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id JAA01957 for ; Wed, 25 Jan 1995 09:15:19 -0800 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id HAA25244; Wed, 25 Jan 1995 07:43:15 -0800 From: Poul-Henning Kamp Message-Id: <199501251543.HAA25244@ref.tfs.com> Subject: Re: More serial console stuff... To: bde@zeta.org.au (Bruce Evans) Date: Wed, 25 Jan 1995 07:43:14 -0800 (PST) Cc: bde@zeta.org.au, terry@cs.weber.edu, freebsd-hackers@FreeBSD.org, rgrimes@gndrsh.aac.dev.com In-Reply-To: <199501250607.RAA18320@godzilla.zeta.org.au> from "Bruce Evans" at Jan 25, 95 05:07:52 pm Content-Type: text Content-Length: 497 Sender: hackers-owner@FreeBSD.org Precedence: bulk > There is no standard way to decide how the drives are mapped. We're > not going to be able to decide without asking the user. Only the bruteforce mode: In bootblock: make table of drive-id geometry checksum of sector #200 checksum of sector #400 checksum of sector #600 In kernel find entry in table where checksums match... -- Poul-Henning Kamp TRW Financial Systems, Inc. FreeBSD has, until now, not one single time had an undetected error. :-) From owner-freebsd-hackers Wed Jan 25 09:35:02 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id JAA02624 for hackers-outgoing; Wed, 25 Jan 1995 09:35:02 -0800 Received: from physics.su.OZ.AU (root@physics.su.OZ.AU [129.78.129.1]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id JAA02613 for ; Wed, 25 Jan 1995 09:35:00 -0800 Received: by physics.su.OZ.AU id AA19077 (5.67b/IDA-1.4.4 for freebsd-hackers@freefall.cdrom.com); Wed, 25 Jan 1995 23:10:48 +1100 From: David Dawes Message-Id: <199501251210.AA19077@physics.su.OZ.AU> Subject: Re: Joystick driver available To: jgreco@brasil.moneng.mei.com (Joe Greco) Date: Wed, 25 Jan 1995 23:10:47 +1100 (EST) Cc: kuku@gilberto.physik.rwth-aachen.de, jmz@cabri.obs-besancon.fr, freebsd-hackers@freefall.cdrom.com In-Reply-To: <9501251004.AA15631@brasil.moneng.mei.com> from "Joe Greco" at Jan 25, 95 04:04:37 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 773 Sender: hackers-owner@FreeBSD.org Precedence: bulk >> Thinking of possible applications (other than games) of a joy stick: >> >> Input device for X11. >> >> Does anyone know how to make X see it? > >It depends on how it is implemented (and how easily XF86 would be >adapted)... speaking as somebody who has done multiheaded touchscreen >implementations for Sun workstaions, I would guess that it would be somewhat >trivial, but would probably require XF86 mods... > >A neat thing to do might be to make it "look" like a serial mouse (ioctl or >something?).... that would allow it to be used with XF86 without any >further modifications. Cool way to do it, at least for certain >applications. We have someone working on implementing the XInput extension for XFree86. That might be the best way to make X see it. David From owner-freebsd-hackers Wed Jan 25 09:55:01 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id JAA03096 for hackers-outgoing; Wed, 25 Jan 1995 09:55:01 -0800 Received: from clem.systemsix.com (clem.systemsix.com [198.99.86.131]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id JAA03083 for ; Wed, 25 Jan 1995 09:54:55 -0800 Received: from clem.systemsix.com (localhost [127.0.0.1]) by clem.systemsix.com (8.6.5/8.6.5) with ESMTP id KAA01128 for ; Wed, 25 Jan 1995 10:56:05 -0700 Message-Id: <199501251756.KAA01128@clem.systemsix.com> To: hackers@FreeBSD.org Subject: Re: Kernel changes between 2.0-RELEASE and snapshot In-reply-to: Your message of "Wed, 25 Jan 1995 00:35:22 PST." <199501250835.AAA06007@corbin.Root.COM> Date: Wed, 25 Jan 1995 10:56:05 -0700 From: Steve Passe Sender: hackers-owner@FreeBSD.org Precedence: bulk Hello, > >Time permitting, could someone please forward me a list of kernel changes > >and/or bug fixes between 2.0-RELEASE and the latest snapshot? I'm having > >stability problems on my public access UNIX, and it'd be nice if changes > >in the latest release have fixed 'em. Related question, I found a bug in 2.0-950112-SNAP m4. What database can I search for previously reported bugs to ensure you good people have not already received a bug report on a particular subject? Don't want to waste your time, but don't want it slipping thru the cracks. Steve Passe smp@clem.systemsix.com From owner-freebsd-hackers Wed Jan 25 10:22:34 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id KAA03511 for hackers-outgoing; Wed, 25 Jan 1995 10:22:34 -0800 Received: from campino.informatik.rwth-aachen.de (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id KAA03504 for ; Wed, 25 Jan 1995 10:22:18 -0800 Received: from gilberto.physik.rwth-aachen.de by campino.informatik.rwth-aachen.de (4.1/campino-6) id AA27291; Wed, 25 Jan 95 13:03:21 +0100 Received: by gilberto.physik.rwth-aachen.de (NAA14061); Wed, 25 Jan 1995 13:09:51 +0100 Message-Id: <199501251209.NAA14061@gilberto.physik.rwth-aachen.de> Subject: Re: nfs: can't access To: vvm@cv.jinr.dubna.su (Valery Mitsyn) Date: Wed, 25 Jan 1995 13:09:51 +0100 (MET) Cc: freebsd-hackers@freefall.cdrom.com (user alias) In-Reply-To: <199501251255.OAA23942@cv.jinr.dubna.su> from "Valery Mitsyn" at Jan 25, 95 02:55:40 pm From: Christoph Kukulies Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 734 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > removing the maproot from /etc/exports allows the mount to finish correctly. > > But executing make install (after removing work/.install_done) > > from e.g. /home/ports-2.0/mail/elm always wants to load the distribution > > from the site rather than seeing that the distribution is already in > > /home/ports-2.0/distfiles. > > mount blue:/home/ports-2.0 /usr/ports > > or > > ln -s /home/ports-2.0 /usr/ports Hhhmm. Kinda something's hardwired and not very flexible. > -- > Best regards, > Valery V. Mitsyn > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de FreeBSD blues 2.1.0-Development FreeBSD 2.1.0-Development #1: Wed Jan 18 10:42:31 1995 kuku@blues:/usr/src/sys/compile/BLUES i386 From owner-freebsd-hackers Wed Jan 25 10:25:55 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id KAA03608 for hackers-outgoing; Wed, 25 Jan 1995 10:25:55 -0800 Received: from clem.systemsix.com (clem.systemsix.com [198.99.86.131]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id KAA03602 for ; Wed, 25 Jan 1995 10:25:50 -0800 Received: from clem.systemsix.com (localhost [127.0.0.1]) by clem.systemsix.com (8.6.5/8.6.5) with ESMTP id LAA01230 for ; Wed, 25 Jan 1995 11:27:01 -0700 Message-Id: <199501251827.LAA01230@clem.systemsix.com> To: freebsd-hackers@freefall.cdrom.com Subject: Re: Joystick driver available Date: Wed, 25 Jan 1995 11:27:00 -0700 From: Steve Passe Sender: hackers-owner@FreeBSD.org Precedence: bulk Hello, > adapted)... speaking as somebody who has done multiheaded touchscreen > implementations for Sun workstaions, I would guess that it would be somewhat (semi-)unrelated question. I have been thinking multiheaded display for freeBSD/XFree86 for awhile now. I know there is a server available using 1 vga, 1 mono card, but I would like to have a box with 3 accelerated cards in a true multiheaded setup. 1: take several PCI vga cards, clip a couple address traces and wire in an inverter. Might need to mess with several groups to re-address board in both io and mem spaces. 2: modify X server to probe for cards in new ranges. 3: ??? Some questions: 1: would it be necessary to hack the kernel paging code to provide a 'safe' area to put them into? anyone care to venture possible addresses for memory and io? would kernel mods be avoidable by putting these boards above 128/256(?)MB, and what about the io addresses? 2: what limitations are there as to caching circuits, ie. non-cachable memory holes, snooping, etc? 3: anyone have suggestions for specific boards that would be suitable for this? I favor PCI for the full 32 bit address range they have. This is a half-baked plan at best, anyone interested in cooking? Steve Passe smp@clem.systemsix.com From owner-freebsd-hackers Wed Jan 25 11:19:20 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id LAA23036 for hackers-outgoing; Wed, 25 Jan 1995 11:19:20 -0800 Received: from anvil.appsmiths.com (appsmiths.sccsi.com [198.65.134.98]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id LAA23031 for ; Wed, 25 Jan 1995 11:19:18 -0800 Received: (from hoppy@localhost) by anvil.appsmiths.com (8.6.8/8.6.6) id NAA09891 for hackers@FreeBSD.org; Wed, 25 Jan 1995 13:18:55 -0600 From: "Clay D. Hopperdietzel" Message-Id: <199501251918.NAA09891@anvil.appsmiths.com> Subject: duh, never mind gcc2.6.2 To: hackers@FreeBSD.org Date: Wed, 25 Jan 1995 13:18:55 -0600 (CST) X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 166 Sender: hackers-owner@FreeBSD.org Precedence: bulk Yes clay is in stooopid mode. I see that 2.6.2 is already happily in 2.0 I guess when I set out on this quest, I looked at the 1.1.5 machine for the gcc version. From owner-freebsd-hackers Wed Jan 25 11:19:38 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id LAA23043 for hackers-outgoing; Wed, 25 Jan 1995 11:19:38 -0800 Received: from anvil.appsmiths.com (appsmiths.sccsi.com [198.65.134.98]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id LAA23038 for ; Wed, 25 Jan 1995 11:19:36 -0800 Received: (from hoppy@localhost) by anvil.appsmiths.com (8.6.8/8.6.6) id NAA09864 for hackers@FreeBSD.org; Wed, 25 Jan 1995 13:12:25 -0600 From: "Clay D. Hopperdietzel" Message-Id: <199501251912.NAA09864@anvil.appsmiths.com> Subject: gcc 2.6.2 woes To: hackers@FreeBSD.org Date: Wed, 25 Jan 1995 13:12:24 -0600 (CST) X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 354 Sender: hackers-owner@FreeBSD.org Precedence: bulk I have had occasion to try to put gcc 2.6.2 on my 2.0 box. There seem to be some glitches along the way (and I'm not done yet either). I was wondering if anyone out there had been through this and could save me some time. Alternatively, If I have to hammer this out myself, perhaps someone can give me some guidence on how to "capture" this work. From owner-freebsd-hackers Wed Jan 25 11:23:00 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id LAA23121 for hackers-outgoing; Wed, 25 Jan 1995 11:23:00 -0800 Received: from goof.com (root@goof.com [198.82.204.15]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id LAA23115 for ; Wed, 25 Jan 1995 11:22:58 -0800 Received: (from mmead@localhost) by goof.com (8.6.9/8.6.9) id OAA01968; Wed, 25 Jan 1995 14:13:57 -0500 From: "matthew c. mead" Message-Id: <199501251913.OAA01968@goof.com> Subject: Re: Motherboards To: fbsd@clem.systemsix.com (Steve Passe) Date: Wed, 25 Jan 1995 14:13:57 -0500 (EST) Cc: hackers@FreeBSD.org In-Reply-To: <199501251834.LAA01262@clem.systemsix.com> from "Steve Passe" at Jan 25, 95 11:34:22 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 799 Sender: hackers-owner@FreeBSD.org Precedence: bulk Steve Passe wrote: > VLB: if a 486, OK, if a 586, no. VLB doesn't have a great future. PCI > cards are as cheap and becoming more available. > VLB/PCI: NO NO NO!!! makes for a slow machine. Really? > PCI: if a 586, yes. IMHO PCI is the future. What about with a 486? If I could get an upgrade for my SCSI controller, I'd do this.... > I use the intel plato premiere/II and am quite happy with it. The > prevailing wisdom within FreeBSD appears to favor the ASUS boards, > at least as far as pentium systems go... Hmm. I'll look into ASUS boards... -matt -- Matthew C. Mead -- System/Network Administration, User Support, Software Devel. Virginia Tech Center for Transportation Research Work Related: mmead@ctr.vt.edu | All Other: mmead@goof.com WWW: http://www.goof.com:/~mmead From owner-freebsd-hackers Wed Jan 25 11:28:32 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id LAA23311 for hackers-outgoing; Wed, 25 Jan 1995 11:28:32 -0800 Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id LAA23304 for ; Wed, 25 Jan 1995 11:28:20 -0800 Received: (from dfr@localhost) by minnow.render.com (8.6.9/8.6.9) id SAA23198; Wed, 25 Jan 1995 18:50:07 GMT Date: Wed, 25 Jan 1995 18:50:05 +0000 (GMT) From: Doug Rabson To: hackers@FreeBSD.org Subject: Strange errors with AHA1542B Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hackers-owner@FreeBSD.org Precedence: bulk I just started noticing errors like this appearing on my console: blkno=3831389276 bcount=1949779968 flags=0x100010 Debugger("") called. aha0: aha_scsi_cmd, more than 17 DMA segs sd1: oops not queue Is this a known problem? Is it serious? -- Doug Rabson, RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 71 251 4411 FAX: +44 71 251 0939 From owner-freebsd-hackers Wed Jan 25 11:35:04 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id LAA00173 for hackers-outgoing; Wed, 25 Jan 1995 11:35:04 -0800 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id LAA00162 for ; Wed, 25 Jan 1995 11:34:38 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA04342; Wed, 25 Jan 1995 20:33:09 +0100 Received: by sax.sax.de (8.6.9/8.6.9-s1) with UUCP id UAA29735 for freebsd-hackers@freefall.cdrom.com; Wed, 25 Jan 1995 20:33:09 +0100 Received: by bonnie.tcd-dresden.de (8.6.8/8.6.6) id SAA21352; Wed, 25 Jan 1995 18:45:20 +0100 From: j@uriah.sax.de (J Wunsch) Message-Id: <199501251745.SAA21352@bonnie.tcd-dresden.de> Subject: Re: Joystick driver available To: jgreco@brasil.moneng.mei.com (Joe Greco) Date: Wed, 25 Jan 1995 18:45:20 +0100 (MET) Cc: kuku@gilberto.physik.rwth-aachen.de, jmz@cabri.obs-besancon.fr, freebsd-hackers@freefall.cdrom.com In-Reply-To: <9501251004.AA15631@brasil.moneng.mei.com> from "Joe Greco" at Jan 25, 95 04:04:37 am X-Phone: +49-351-8141 137 Reply-To: joerg_wunsch@uriah.sax.de X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1022 Sender: hackers-owner@FreeBSD.org Precedence: bulk As Joe Greco wrote: | | > Input device for X11. | > | > Does anyone know how to make X see it? | | It depends on how it is implemented (and how easily XF86 would be | adapted)... speaking as somebody who has done multiheaded touchscreen | implementations for Sun workstaions, I would guess that it would be somewhat | trivial, but would probably require XF86 mods... The better way is to let XFree86 where it is (if you don't really have any mouse declare /dev/null being your ``mouse''), and use the XInputExtension for this type of device. This would allow for a concurrent work of the mouse and secondary input devices (joystick, digiboard). There's been a rumour on the XFree86 beta list that someone is actually implementing the XInputExtension these days... (he needs it for a digitizer). -- cheers, J"org work: --- no longer --- private: joerg_wunsch@uriah.sax.de Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Wed Jan 25 12:31:31 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id MAA01325 for hackers-outgoing; Wed, 25 Jan 1995 12:31:31 -0800 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id MAA01318 for ; Wed, 25 Jan 1995 12:31:27 -0800 Received: from masi.ibp.fr (root@masi.ibp.fr [132.227.60.23]) by ibp.ibp.fr (8.6.8/jtpda-5.0) with ESMTP id UAA10039 ; Wed, 25 Jan 1995 20:14:52 +0100 Received: from hebe.ibp.fr (card@hebe.ibp.fr [132.227.64.34]) by masi.ibp.fr (8.6.9/jtpda-5.0) with ESMTP id UAA25660 ; Wed, 25 Jan 1995 20:13:41 +0100 From: Remy.Card@masi.ibp.fr (Remy CARD) Received: by hebe.ibp.fr (8.6.9/jtpda-5.0) id UAA15501 ; Wed, 25 Jan 1995 20:10:57 +0100 Message-Id: <199501251910.UAA15501@hebe.ibp.fr> Subject: Re: Assembler error To: wkk@eng.warwick.ac.uk Date: Wed, 25 Jan 1995 20:10:57 +0100 (MET) Cc: hackers@FreeBSD.org In-Reply-To: <11463.9501241600@eng.warwick.ac.uk> from "wkk@eng.warwick.ac.uk" at Jan 24, 95 04:00:23 pm X-Mailer: ELM [version 2.4 PL21] Content-Type: text Content-Length: 1711 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > Hello, Hello, > I am trying to compile mach4 server on FreeBSD. Theoretically it should > compile but I get the following error in file that has some assembler code. I > am not an assembler expert but looking at the error it look likes the assembler > is getting confused with the text and data segment (I think). Can anyone help? Well, I have successfully built Mach 4 on FreeBSD after patching the assembler a bit. I include the patch in this mail. I don't think that it can break anything (I am running a system recompiled from the current sources and it works as usual). Note that the very same patch is needed for NetBSD 1.0. Can someone please consider commiting this patch? > > Thanks very much. > > khondkar. Remy *** gnu/usr.bin/as/subsegs.c.orig Fri Jan 13 12:36:42 1995 --- gnu/usr.bin/as/subsegs.c Thu Jan 5 19:56:40 1995 *************** *** 140,145 **** --- 140,148 ---- if (seg == SEG_DATA) { seg_fix_rootP = &data_fix_root; seg_fix_tailP = &data_fix_tail; + } else if (seg == SEG_BSS) { + seg_fix_rootP = &bss_fix_root; + seg_fix_tailP = &bss_fix_tail; } else { know (seg == SEG_TEXT); seg_fix_rootP = &text_fix_root; *************** *** 171,177 **** { long tmp; /* JF for obstack alignment hacking */ #ifndef MANY_SEGMENTS ! know(seg == SEG_DATA || seg == SEG_TEXT); #endif if (seg != now_seg || subseg != now_subseg) { /* we just changed sub-segments */ --- 174,180 ---- { long tmp; /* JF for obstack alignment hacking */ #ifndef MANY_SEGMENTS ! know(seg == SEG_DATA || seg == SEG_TEXT || seg == SEG_BSS); #endif if (seg != now_seg || subseg != now_subseg) { /* we just changed sub-segments */ From owner-freebsd-hackers Wed Jan 25 12:40:35 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id MAA01786 for hackers-outgoing; Wed, 25 Jan 1995 12:40:35 -0800 Received: from clem.systemsix.com (clem.systemsix.com [198.99.86.131]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id MAA01777 for ; Wed, 25 Jan 1995 12:40:30 -0800 Received: from clem.systemsix.com (localhost [127.0.0.1]) by clem.systemsix.com (8.6.5/8.6.5) with ESMTP id NAA01604; Wed, 25 Jan 1995 13:27:45 -0700 Message-Id: <199501252027.NAA01604@clem.systemsix.com> To: ljo@po.cwru.edu cc: freebsd-hackers@freefall.cdrom.com Subject: Re: Joystick driver available In-reply-to: Your message of "Wed, 25 Jan 1995 14:42:41 EST." <199501251942.OAA10556@amcell2.caisr.cwru.edu> Date: Wed, 25 Jan 1995 13:27:44 -0700 From: Steve Passe Sender: hackers-owner@FreeBSD.org Precedence: bulk > Just buy multi-head capable X server from X Inside. (800) XINSIDE. > Costs $99.50 and shoul support multiple PCI cards. > I have it,but none of my PCI cards work together... It is still > a bit unclear exactly what cards do work. Talked to them, they evidently have such a beast. Limited card support now, but they claim an update will soon fix that. No need to do any hardware/OS hacking, they disable vga section of cards (via software) and use as PCI devices. Would be a great solution EXCEPT for a bonehead like me who insists on having source. So discussion now is limited to techniques for accessing PCI video cards. From owner-freebsd-hackers Wed Jan 25 12:48:11 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id MAA01997 for hackers-outgoing; Wed, 25 Jan 1995 12:48:11 -0800 Received: from crab.xinside.com (crab.xinside.com [199.120.247.2]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id MAA01990 for ; Wed, 25 Jan 1995 12:48:07 -0800 Received: (jdc@localhost) by crab.xinside.com (8.6.8/8.6.5) id NAA06866; Wed, 25 Jan 1995 13:41:44 -0700 From: Jeremy Chatfield Message-Id: <199501252041.NAA06866@crab.xinside.com> Subject: Re: Joystick driver available To: kuku@gilberto.physik.rwth-aachen.de Date: Wed, 25 Jan 1995 13:41:43 +0000 (MST) Cc: jgreco@brasil.moneng.mei.com, freebsd-hackers@freefall.cdrom.com In-Reply-To: <199501251107.MAA13952@gilberto.physik.rwth-aachen.de> from "Christoph Kukulies" at Jan 25, 95 12:07:05 pm Organization: X Inside Inc, P O Box 10774, Golden, CO 80401-0610, USA. Phone: +1(303)470-5302 Reply-To: jdc@crab.xinside.com X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 3648 Sender: hackers-owner@FreeBSD.org Precedence: bulk Christoph Kukulies writes: > > > > > > Thinking of possible applications (other than games) of a joy stick: > > > > > > Input device for X11. > > > > > > Does anyone know how to make X see it? > > > > It depends on how it is implemented (and how easily XF86 would be > > adapted)... speaking as somebody who has done multiheaded touchscreen > > How would the Xaccel server (Xinside, Inc.) cope with that? (Jeremy?) Funny you should ask - I've just been checking. We don't want to handle this like Mice, graphics tablets and touchscreens. We were thinking of introducing some configuration methods that would restrict particular devices to particular screens (e.g. Mouse can't move from Screen 0, Digitiser only works on Screen 1, Touchscreens on Screen 0 and 2). To handle all these different input types, we're already planning on implementing the X Input extension (this is *NOT* XIE - that's the X Imaging Extension). What *we'd* like, is a common OS approach to handling Joy Sticks, device based, with a uniform data stream. That way, we can have a section in our config file: [JOYSTICK] Device = "/dev/joystick"; And no more need be said (unless limiting the joystick to a single screen of a multihead display). The different attributes and protocol streams of a joy stick would make this is a useful *additional* input device, rather than a replacement. This difference becomes more significant when we consider 3D pointing devices, which some might think of as fancy joysticks :-) We were thinking of introducing the X Input extension during the lifetime of 2.x (probably not in 2.0, since we're already loading that with more changes than can be coherently tested :-) ). We will be having minor upgrades during the lifetime of 1.2, since we already have new chipsets and warnings of new chipsets and boards that won;t work with what we ship as 1.2. We could *probably* introduce the X Input extension during this phase, if we significant interest. Given the high level of interest generated by our relatively low-key postings about X Video, we're already shifting Video into a higher priority slot than 3D. Shifting the X Input priority is just another example of us shifting priorities to meet demands. Oh, BTW (probably not the best place to flag this, but I'll note it anyway): Accelerated-X 1.2 Beta/3 will not support FreeBSD 1.1 This is because of a motherboard malfunction... If we don't see much in the way of complaints, we might just release our 1.2 for FreeBSD 2.x and drop the 1.1 support. > > A neat thing to do might be to make it "look" like a serial mouse (ioctl or > > something?).... that would allow it to be used with XF86 without any > > further modifications. Cool way to do it, at least for certain > > applications. Ouch. This is short term useful, but won't permit a full environment with multiple input devices... > > ------------------------------------------------------------------------------- > > Joe Greco - The Data Capture Fellow (and UNIX/Network Hacker) 414/362-3617 > > Marquette Electronics, Inc. - Milwaukee, WI jgreco@brasil.moneng.mei.com > > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de > FreeBSD blues 2.1.0-Development FreeBSD 2.1.0-Development #1: > Wed Jan 18 10:42:31 1995 kuku@blues:/usr/src/sys/compile/BLUES i386 -- Jeremy Chatfield, +1(303)470-5302, FAX:+1(303)470-5513, email:jdc@xinside.com X Inside Inc, P O Box 10774, Golden, CO 80401-0610, USA. Commercial X Server - for more information please try these services http://www.xinside.com info@xinside.com ftp.xinside.com From owner-freebsd-hackers Wed Jan 25 13:15:20 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id NAA02720 for hackers-outgoing; Wed, 25 Jan 1995 13:15:20 -0800 Received: from eagle.ais.net (eagle.ais.net [199.0.154.2]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id NAA02714; Wed, 25 Jan 1995 13:15:14 -0800 Received: by eagle.ais.net (Smail3.1.28.1 #9) id m0rXF1N-000BpuC; Wed, 25 Jan 95 15:12 CST Message-Id: Subject: email over slip To: freebsd-questions@FreeBSD.org Date: Wed, 25 Jan 1995 15:12:57 -0600 (CST) From: "Daniel Leeds" Cc: freebsd-hackers@FreeBSD.org X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 329 Sender: hackers-owner@FreeBSD.org Precedence: bulk Hi, I am running a 1.1.5.1 system over slip. I was wondering first, if anyone had a 1.1.x inary of PINE???? alos, how would I go about using elm/pine on my box to read mail sent to my shell acccount at ais.net?? is there a way to do this? I have heard of something called POP...any pointers/info would be helpful -- From owner-freebsd-hackers Wed Jan 25 14:57:04 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id OAA05969 for hackers-outgoing; Wed, 25 Jan 1995 14:57:04 -0800 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id OAA05961 for ; Wed, 25 Jan 1995 14:56:54 -0800 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.8/jtpda-5.0) with SMTP id XAA11507 for ; Wed, 25 Jan 1995 23:58:06 +0100 Received: by blaise.ibp.fr (4.1/SMI-4.1) id AA08129; Wed, 25 Jan 95 23:58:03 +0100 Received: (from roberto@localhost) by keltia.frmug.fr.net (8.6.9/keltia-uucp-1.21) id XAA13097 for freebsd-hackers@FreeBSD.ORG; Wed, 25 Jan 1995 23:45:48 +0100 From: Ollivier Robert Message-Id: <199501252245.XAA13097@keltia.frmug.fr.net> Subject: tcpdump again :-) To: freebsd-hackers@FreeBSD.org (FreeBSD Hackers' list) Date: Wed, 25 Jan 1995 23:45:46 +0100 (MET) Reply-To: roberto@blaise.ibp.fr (Ollivier Robert) X-Operating-System: FreeBSD 2.1.0-Development ctm#302 X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 492 Sender: hackers-owner@FreeBSD.org Precedence: bulk Jordan fixed the "nothing known about..." in tcpdump after 3.0's import but it doesn't build anymore : 290 [23:44] root@keltia:usr.sbin/tcpdump# tcpdump/obj/tcpdump -V Version 2.2.1 Usage: tcpdump [-deflnOpqtvx] [-c count] [-i interface] [-r filename] [-w filename] [expr] It seems that the 3.0 import has been screwed. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia 2.1.0-Development #15: Wed Jan 25 00:31:42 MET 1995 From owner-freebsd-hackers Wed Jan 25 15:16:17 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id PAA06351 for hackers-outgoing; Wed, 25 Jan 1995 15:16:17 -0800 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id PAA06345 for ; Wed, 25 Jan 1995 15:16:14 -0800 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.8/jtpda-5.0) with SMTP id AAA11718 for ; Thu, 26 Jan 1995 00:17:25 +0100 Received: by blaise.ibp.fr (4.1/SMI-4.1) id AA08190; Thu, 26 Jan 95 00:17:22 +0100 From: roberto@blaise.ibp.fr (Ollivier ROBERT) Message-Id: <9501252317.AA08190@blaise.ibp.fr> Subject: named To: hackers@FreeBSD.org (Hackers' list FreeBSD) Date: Thu, 26 Jan 1995 00:17:22 +0100 (MET) X-Operating-System: FreeBSD 2.1.0-Development ctm#292 X-Mailer: ELM [version 2.4 PL23beta2] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 537 Sender: hackers-owner@FreeBSD.org Precedence: bulk I remember someone (Paul ?) imported 4.9.3b9 at some time in our tree. 4.9.3b17 is the latest beta and is flagged by Paul (Vixie this time :-) as one of the last betas (if not the last one). Could we not upgrade ? PS: for my previous sig11 with sendmail and cron, a recompilation of all the libraries (I suspect an old libkvm or such) it seems to be back as always. Thanks for listening :-) -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@FreeBSD.ORG FreeBSD keltia 2.1.0-Development #9: Tue Jan 17 21:12:14 MET 1995 From owner-freebsd-hackers Wed Jan 25 16:15:13 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id QAA07516 for hackers-outgoing; Wed, 25 Jan 1995 16:15:13 -0800 Received: from tfs.com (mailhub.tfs.com [140.145.250.1]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id QAA07510 for ; Wed, 25 Jan 1995 16:15:11 -0800 Received: by tfs.com (smail3.1.28.1) Message-Id: From: julian@tfs.com (Julian Elischer) Subject: Re: Strange errors with AHA1542B To: dfr@render.com (Doug Rabson) Date: Wed, 25 Jan 1995 16:14:38 -0800 (PST) Cc: hackers@FreeBSD.org In-Reply-To: from "Doug Rabson" at Jan 25, 95 06:50:05 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 636 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > I just started noticing errors like this appearing on my console: > > blkno=3831389276 bcount=1949779968 flags=0x100010 these figures are rubish something has scribbled over something else.... > Debugger("") called. > aha0: aha_scsi_cmd, more than 17 DMA segs yep, 1949779968 bytes is more than 17 x 4k pages.... > sd1: oops not queue > > Is this a known problem? Is it serious? no and yes... (suspect H/W (cache?)) does it happen after a reboot? with a new kernel? julian > > -- > Doug Rabson, RenderMorphics Ltd. Mail: dfr@render.com > Phone: +44 71 251 4411 > FAX: +44 71 251 0939 > > From owner-freebsd-hackers Wed Jan 25 19:26:37 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id TAA12452 for hackers-outgoing; Wed, 25 Jan 1995 19:26:37 -0800 Received: from goof.com (root@goof.com [198.82.204.15]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id TAA12443 for ; Wed, 25 Jan 1995 19:26:31 -0800 Received: (from mmead@localhost) by goof.com (8.6.9/8.6.9) id WAA03630 for hackers@freebsd.org; Wed, 25 Jan 1995 22:26:20 -0500 From: "matthew c. mead" Message-Id: <199501260326.WAA03630@goof.com> Subject: Motherboards Revisitied (GIGA-BYTE) To: hackers@wcarchive.cdrom.com Date: Wed, 25 Jan 1995 16:01:57 -0500 (EST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 590 Sender: hackers-owner@FreeBSD.org Precedence: bulk Well, the best sounding motherboard that I have come across (if I stick with the VLB motherboard option) is a GIGA-BYTE. Does anyone know of any problems with their motherboards, or are they supposed to be pretty good? From what I've heard they seem to be pretty stable. It's got an AWARD BIOS (never heard of it...)... any experiences? Thanks... -matt -- Matthew C. Mead -- System/Network Administration, User Support, Software Devel. Virginia Tech Center for Transportation Research Work Related: mmead@ctr.vt.edu | All Other: mmead@goof.com WWW: http://www.goof.com:/~mmead From owner-freebsd-hackers Wed Jan 25 19:39:17 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id TAA12703 for hackers-outgoing; Wed, 25 Jan 1995 19:39:17 -0800 Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id TAA12696 for ; Wed, 25 Jan 1995 19:39:11 -0800 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.9/8.6.9) id TAA02959; Wed, 25 Jan 1995 19:35:32 -0800 Date: Wed, 25 Jan 1995 19:35:32 -0800 Message-Id: <199501260335.TAA02959@silvia.HIP.Berkeley.EDU> To: terry@cs.weber.edu CC: hackers@FreeBSD.org In-reply-to: <9501251537.AA18261@cs.weber.edu> (terry@cs.weber.edu) Subject: Re: sendmail 8.6.9 - "Name server failure" problem (fwd) From: asami@cs.berkeley.edu (Satoshi Asami) Sender: hackers-owner@FreeBSD.org Precedence: bulk Just to confirm you that this patch fixed the exact same problem (incoming mails sitting in the queue until explicitly cleared) I reported a while ago in this list. I'm running 2.0R. Satoshi --- * > *** src/daemon.c- Mon Apr 18 06:48:41 1994 * > --- src/daemon.c Tue Jan 24 19:38:06 1995 * > *************** * > *** 1406,1411 **** * > --- 1406,1414 ---- * > int saveretry; * > * > #if NAMED_BIND * > + /* need to make sure _res.retry is initialized before using it */ * > + if ((_res.options & RES_INIT) == 0) * > + res_init(); * > /* shorten name server timeout to avoid higher level timeouts */ * > saveretry = _res.retry; * > _res.retry = 3; From owner-freebsd-hackers Wed Jan 25 20:24:28 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id UAA13684 for hackers-outgoing; Wed, 25 Jan 1995 20:24:28 -0800 Received: from pyromania.apana.org.au (pyromania.apana.org.au [202.12.87.123]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id UAA13678 for ; Wed, 25 Jan 1995 20:24:12 -0800 Received: (from john@localhost) by pyromania.apana.org.au (8.6.9/8.6.9) id PAA00192 for hackers@freebsd.org; Thu, 26 Jan 1995 15:22:36 +1100 From: John Herks Message-Id: <199501260422.PAA00192@pyromania.apana.org.au> Subject: SyQuest works with FreeBSD 2.0R ! To: hackers@FreeBSD.org Date: Thu, 26 Jan 1995 15:22:36 +1100 (EST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1573 Sender: hackers-owner@FreeBSD.org Precedence: bulk I have just installed a SyQuest 3.5" 270 MB removable SCSI drive in my FreeBSD 2.0R system. So far everything seems to work just fine! Here is my dmesg output -: pci0: scanning device 0..15, mechanism=2. chip0 on pci0:0 ncr0 int a (config) irq 9 on pci0:1 reg20: virtual=0xf507c000 physical=0xc0000000 ncr0: restart (scsi reset). ncr0 scanning for targets 0..6 (1.12) ncr0 waiting for scsi devices to settle ncr0 targ 0 lun 0: type 0(direct) fixed SCSI2 ncr0 targ 0 lun 0: sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. sd0: 1029MB (2109376 total sec), 2874 cyl, 8 head, 91 sec, bytes/sec 512 ncr0 targ 1 lun 0: type 0(direct) removable SCSI2 ncr0 targ 1 lun 0: sd1(ncr0:1:0): 200ns (5 Mb/sec) offset 8. sd1: 256MB (524288 total sec), 3140 cyl, 2 head, 83 sec, bytes/sec 512 chip1 on pci0:2 pci uses physical addresses from 0xc0000000 to 0xc0001000 -- \|/ (@ @) ----------------------------oOO--(_)--OOo----------------------------------- ``` ''' John Herks Communications Engineer Pyromania Unix Melbourne john@pyromania.apana.org.au Phone:+613-220-4757 ---------------------------------------------------------------------------- From owner-freebsd-hackers Wed Jan 25 21:14:01 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id VAA14472 for hackers-outgoing; Wed, 25 Jan 1995 21:14:01 -0800 Received: from crab.xinside.com (crab.xinside.com [199.120.247.2]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id VAA14465 for ; Wed, 25 Jan 1995 21:13:56 -0800 Received: (jdc@localhost) by crab.xinside.com (8.6.8/8.6.5) id WAA08454; Wed, 25 Jan 1995 22:10:06 -0700 From: Jeremy Chatfield Message-Id: <199501260510.WAA08454@crab.xinside.com> Subject: Re: Joystick driver available To: fbsd@clem.systemsix.com (Steve Passe) Date: Wed, 25 Jan 1995 22:10:06 +0000 (MST) Cc: ljo@po.cwru.edu, freebsd-hackers@freefall.cdrom.com In-Reply-To: <199501252027.NAA01604@clem.systemsix.com> from "Steve Passe" at Jan 25, 95 01:27:44 pm Organization: X Inside Inc, P O Box 10774, Golden, CO 80401-0610, USA. Phone: +1(303)470-5302 Reply-To: jdc@crab.xinside.com X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 4257 Sender: hackers-owner@FreeBSD.org Precedence: bulk Steve Passe writes: > > > Just buy multi-head capable X server from X Inside. (800) XINSIDE. > > Costs $99.50 and shoul support multiple PCI cards. > > I have it,but none of my PCI cards work together... It is still > > a bit unclear exactly what cards do work. > > Talked to them, they evidently have such a beast. Limited > card support now, but they claim an update will soon fix that. > No need to do any hardware/OS hacking, they disable vga section > of cards (via software) and use as PCI devices. Would be a great > solution EXCEPT for a bonehead like me who insists on having source. > So discussion now is limited to techniques for accessing PCI video > cards. There are limits on what can be combined. These are inherent in the design of varioous boards and chipsets. The boards that work together best, are the boards designed to work together... Notably arbitrary numbers of the Matrox Impression and Matrox Ultima, or two I-128's. There are some specific limitations to the use of PCI bus graphics boards. You can't mix PCI bus and other bus types' graphics boards. For example, a VGA ISA card cannot be made towork with an I-128. Chipset limitations: Weitek P9000 We don't know of any boards, or any way, to have a Weitek P9000, PCI board coexist with any board. The VGA mode cannot be disabled. Board limitations: ATI Mach64 S3 964 STB PowerGraph Pro Tseng ET4000/W32p The ATI Mach64 (Graphics Pro Turbo, WinTurbo, Gateway Mach64) must be in the lowest available PCI slot number. This is the PCI logical slot number, which can be confusing. For example, an Intel Plato motherboard has Slot 0 as the middle of the three slots. This is not a restriction imposed by the X Server, but by the ATI board. S3 964 boards can be used, but so far as we can see, only one at a time. STB Powergraph Pro (Cirrus 5434) seems unhappy paired with anything else. This may be a 543x limit. Tseng ET4000/W32p boards are difficult. Some boards (Diamond Stealth 32) insist that they are the boot VGA board, even when they are in slot3 and two other boards should have priority. These will fail... Others (Jonas Olsson has the Matrox Comet) will probably work, but are kind of tricky to have working reliably (some of the graphics board vendors tell us that it is flat impossible, but that's seems to be not completely true). What works: #9 Imagine 128 (I-128) #9 GXE64 pro (S3 964) Matrox Impression Plus (MGA ATHENA) ATI Graphics Pro Turbo (ATI Mach64) #9 GXE64 (S3 864) Tseng VGA/32 (ET4000/W32p) Diamond Stealth 32 (ET4k/W32p, if in first slot) etc... For example (working from the lowest numbered slot, dual head Accelerated-X 1.2 Beta/3): ATI Pro Turbo, #9 GXE64pro OK ATI Pro Turbo, STB Nitro (though the reset is not quite right) Pro Turbo, Impression Plus OK Pro Turbo, I-128 OK Pro Turbo, GXE64 OK Impression Plus, Imp Plus OK Tseng VGA/32, Impression Plus OK Diamond Stealth 32, Impression Plus OK etc... What should work and currently fails: ATI Pro Turbo, Diamond Stealth 64 VRAM Pro Turbo, Diamond Stealth 64 VRAM FAIL (ST64 display bad) Pro Turbo, STB Nitro FAIL (5434 not right) Pro Turbo, 64310 FAIL (machine lockup) Pro Turbo, STB PowerGraph Pro FAIL (machine lockup) ST32, GXE64 FAIL (machine lockup) ST32, I-128 OK - horz too fast for monitor (acer34t, explicitly configured) ST32, GXE64p FAIL (machine lockup) ST32, STB PgPro FAIL (machine lockup) etc... As you can see, we've still got some boards that are troublesome in combination. Testing this is a combinatorial explosion. These lists are a fraction of the full two-board tested list, and that is only around the same size as the three board list (we take all two-board working pairs and add a third board). A full list should be available when we get to the release, or shortly thereafter. Running just basic 1024x768x8bpp tests for the full set of boards, takes days... Cheers, JeremyC. -- Jeremy Chatfield, +1(303)470-5302, FAX:+1(303)470-5513, email:jdc@xinside.com X Inside Inc, P O Box 10774, Golden, CO 80401-0610, USA. Commercial X Server - for more information please try these services http://www.xinside.com info@xinside.com ftp.xinside.com From owner-freebsd-hackers Wed Jan 25 21:28:53 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id VAA16202 for hackers-outgoing; Wed, 25 Jan 1995 21:28:53 -0800 Received: from simon.chi.il.us (simon.chi.il.us [199.245.227.17]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id VAA16196 for ; Wed, 25 Jan 1995 21:28:50 -0800 Received: by simon.chi.il.us (Smail3.1.29.1 #3) id m0rXMlf-000NAvC; Wed, 25 Jan 95 23:29 CST Message-Id: Date: Wed, 25 Jan 95 23:29 CST From: steve@simon.chi.il.us (Steven E. Piette) To: freebsd-hackers@freefall.cdrom.com Subject: Re: 3c509 Warm Boot probs... Cc: davidg@Root.COM, jkh@time.cdrom.com, ponds!rivers@dg-rtp.dg.com Sender: hackers-owner@FreeBSD.org Precedence: bulk Here's the fix to get the 3C509's to reset after warm boots. It's relative to the 2.0R source base. Steve *** if_ep.c.orig Tue Jan 24 22:57:15 1995 --- if_ep.c Wed Jan 25 23:19:40 1995 *************** *** 372,386 **** int nisa = 0, neisa = 0; if (ep_current_tag == (EP_LAST_TAG + 1)) { ! /* Come here just one time */ /* Look for the EISA boards, leave them activated */ ! for(j = 1; j < 16; j++) { io_base = (j * EP_EISA_START) | EP_EISA_W0; if (inw(io_base + EP_W0_MFG_ID) != MFG_ID) continue; ! /* we must found 0x1f if the board is EISA configurated */ if ((inw(io_base + EP_W0_ADDRESS_CFG) & 0x1f) != 0x1f) continue; --- 372,386 ---- int nisa = 0, neisa = 0; if (ep_current_tag == (EP_LAST_TAG + 1)) { ! /* Come here just one time for all boards */ /* Look for the EISA boards, leave them activated */ ! for (j = 1; j < 16; j++) { io_base = (j * EP_EISA_START) | EP_EISA_W0; if (inw(io_base + EP_W0_MFG_ID) != MFG_ID) continue; ! /* we must find 0x1f if the board is EISA configurated */ if ((inw(io_base + EP_W0_ADDRESS_CFG) & 0x1f) != 0x1f) continue; *************** *** 398,405 **** ep_current_tag--; /* Look for the ISA boards. Init and leave them actived */ ! outb(id_port, 0xc0); /* Global reset */ DELAY(1000); for (i = 0; i < EP_MAX_BOARDS; i++) { outb(id_port, 0); outb(id_port, 0); --- 398,409 ---- ep_current_tag--; /* Look for the ISA boards. Init and leave them actived */ ! outb(id_port, 0); ! outb(id_port, 0); ! send_ID_sequence(id_port); ! outb(id_port, 0xc0); /* ID Global reset */ DELAY(1000); + for (i = 0; i < EP_MAX_BOARDS; i++) { outb(id_port, 0); outb(id_port, 0); ----- Begin Included Message ----- >From steve Tue Jan 24 22:54:28 1995 To: jkh@time.cdrom.com, ponds!rivers@dg-rtp.dg.com Subject: Re: 3c509 probs... Content-Length: 2884 There's most definitally a reboot problem. It existed in 1.1.5.1 and it's still in Andres's code. I did fix it in the the old driver but I haven't got to fixing it in the 2.0R release. I brought home a second 509 to check out how well the multi-card support works as well. I thought I look at the 509B problem that was reported but 3COM hasn't posted any addendum to the tech ref yet and I don't have one. I can tell you that the reboot problem used to be due to not soft resetting the card correctly in epprobe. I got it right by trial adn error the last time. Steve > From: Thomas David Rivers > To: freebsd-hackers@freefall.cdrom.com, jkh@time.cdrom.com > Subject: 3c509 probs... > > Jordan - > > I discovered this while trying to catch up on 1800+ pieces of mail > (I've been busy with work lately.) > > Anyway, I find that with my 3c509 at work - if I boot DOS/Windows, > then reboot into FreeBSD, FreeBSD does not recognize the 3c509. If I > physically turn the machine off, FreeBSD does recognize the 3c509. > > Thus, I think there is possibly a probe problem here... > > - Dave Rivers - > > (p.s. this is with FreeBSD 2.0R, using the OS/2 boot manager to bounce > between FreeBSD, OS/2, DOS/Windows.) > ----- End Included Message ----- From owner-freebsd-hackers Wed Jan 25 21:47:24 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id VAA16330 for hackers-outgoing; Wed, 25 Jan 1995 21:47:24 -0800 Received: from crab.xinside.com (crab.xinside.com [199.120.247.2]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id VAA16324 for ; Wed, 25 Jan 1995 21:47:20 -0800 Received: (jdc@localhost) by crab.xinside.com (8.6.8/8.6.5) id WAA08677; Wed, 25 Jan 1995 22:43:44 -0700 From: Jeremy Chatfield Message-Id: <199501260543.WAA08677@crab.xinside.com> Subject: MultiHeaded X Servers on PCI To: fbsd@clem.systemsix.com (Steve Passe) Date: Wed, 25 Jan 1995 22:43:43 +0000 (MST) Cc: freebsd-hackers@freefall.cdrom.com In-Reply-To: <199501251827.LAA01230@clem.systemsix.com> from "Steve Passe" at Jan 25, 95 11:27:00 am Organization: X Inside Inc, P O Box 10774, Golden, CO 80401-0610, USA. Phone: +1(303)470-5302 Reply-To: jdc@crab.xinside.com X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 3253 Sender: hackers-owner@FreeBSD.org Precedence: bulk Ah, now I know where the question came from... this arrived long after the question that followed this. "Eddies in the time-space continuum" "Is he?" Steve Passe writes: > > (semi-)unrelated question. I have been thinking multiheaded display > for freeBSD/XFree86 for awhile now. I know there is a server available > using 1 vga, 1 mono card, but I would like to have a box with > 3 accelerated cards in a true multiheaded setup. > > 1: take several PCI vga cards, clip a couple address traces and wire > in an inverter. Might need to mess with several groups > to re-address board in both io and mem spaces. No need. The PCI BIOS and the BIOS on each of the graphics boards is supposed to handle this. Of course, not everyone has this right, yet. Most board vendors are still getting to grips with *one* PCI board in a machine :-) > 2: modify X server to probe for cards in new ranges. You need a PCI BIOS probe routine. The hardest part for us has been all the slightly different ways to read the PCI BIOS specs, resulting in some machines where we've had problems reading the data we need. > 3: ??? This must be the stage where you work out which chipsets can't possibly be made to work because of fundamental design problems, which will often work, and which will work consistently, unless paired with one of the design problem chips/boards... We're deep in this phase at the moment. > Some questions: > > 1: would it be necessary to hack the kernel paging code to provide > a 'safe' area to put them into? anyone care to venture > possible addresses for memory and io? would kernel mods > be avoidable by putting these boards above 128/256(?)MB, > and what about the io addresses? Not needed. > 2: what limitations are there as to caching circuits, ie. non-cachable > memory holes, snooping, etc? For most UNIX systems, users have become used to disabling VGA BIOS caches and shadowing. We need the VGA BIOS caches and shadowing turned on, for PCI systems, as there is a 32-bit PCI BIOS spec. We dip into that for a few bits and pieces during the initialisation, and then keep well away from it :-) > 3: anyone have suggestions for specific boards that would be > suitable for this? I favor PCI for the full 32 bit > address range they have. Absolutely the best boards for multihead displays are: Matrox Impression Plus, Ultima Plus ColorGraphics boards (already have 2 or 4 graphics chipsets and RAMDACs on each board) The #9 Imagine-128 is designed to permit two per system, which does not rule out their use with Matrox or ColorGraphics boards. > This is a half-baked plan at best, anyone interested in cooking? > > Steve Passe > smp@clem.systemsix.com Oh, we've been half-baked for months, already ;-) Umm, isn't System Six the US vendor of the Russian based Usix microkernel SVR4 clone, based in Golden, just up the road from me? Is Usix now FreeBSD compatible? Cheers, JeremyC. -- Jeremy Chatfield, +1(303)470-5302, FAX:+1(303)470-5513, email:jdc@xinside.com X Inside Inc, P O Box 10774, Golden, CO 80401-0610, USA. Commercial X Server - for more information please try these services http://www.xinside.com info@xinside.com ftp.xinside.com From owner-freebsd-hackers Wed Jan 25 23:12:21 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id XAA17868 for hackers-outgoing; Wed, 25 Jan 1995 23:12:21 -0800 Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id XAA17862 for ; Wed, 25 Jan 1995 23:12:09 -0800 Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.6.9/8.6.6) id JAA04848 for hackers@FreeBSD.ORG; Thu, 26 Jan 1995 09:13:20 +0200 From: John Hay Message-Id: <199501260713.JAA04848@zibbi.mikom.csir.co.za> Subject: Directory entries get corrupted? To: hackers@FreeBSD.org Date: Thu, 26 Jan 1995 09:13:19 +0200 (SAT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1944 Sender: hackers-owner@FreeBSD.org Precedence: bulk Hi, I have two machines here with their hardware almost identical: 486DX2-66, Adaptec 1542B SCSI card and Conner CFP1060S 1G disks. One is running 2.0R and the other is running current. When there is lots of disk activity like cvs checkout of the source tree or tar extract from a tape, a fsck will report that some directories are corrupted. The kernel however is quite happy with that directory it seems. If I remove that directory or move the data in the directory somewhere else and then remove the directory, fsck is quite happy with it. Have anybody seen something like this? Is it the software or should I suspect the hardware? The fsck message is: zibbi:/ns/work/FreeBSD # fsck -n /dev/rsd1e ** /dev/rsd1e (NO WRITE) ** Last Mounted on /ns/work/FreeBSD ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames DIRECTORY CORRUPTED I=23409 OWNER=root MODE=40775 SIZE=512 MTIME=Jan 20 11:58 1995 DIR=? SALVAGE? no MISSING '.' I=23409 OWNER=root MODE=40775 SIZE=512 MTIME=Jan 20 11:58 1995 DIR=? FIX? no MISSING '..' I=23409 OWNER=root MODE=40775 SIZE=512 MTIME=Jan 20 11:58 1995 DIR=/src/share/doc/smm/04.quotas FIX? no ** Phase 3 - Check Connectivity UNREF DIR I=15694 OWNER=root MODE=40775 SIZE=512 MTIME=Jan 20 11:58 1995 RECONNECT? no ** Phase 4 - Check Reference Counts LINK COUNT DIR I=15694 OWNER=root MODE=40775 SIZE=512 MTIME=Jan 20 11:58 1995 COUNT 2 SHOULD BE 1 ADJUST? no UNREF FILE I=23410 OWNER=root MODE=100664 SIZE=173 MTIME=Jan 11 02:15 1995 RECONNECT? no CLEAR? no UNREF FILE I=23411 OWNER=root MODE=100664 SIZE=11980 MTIME=May 30 21:08 1994 RECONNECT? no CLEAR? no LINK COUNT DIR I=104016 OWNER=root MODE=40775 SIZE=512 MTIME=Jan 26 08:35 1995 COUNT 17 SHOULD BE 16 ADJUST? no ** Phase 5 - Check Cyl groups CLEAN FLAG IS WRONG IN SUPERBLOCK FIX? no 34513 files, 313363 used, 123292 free (12652 frags, 13830 blocks, 2.9% fragmentation) John Hay -- jhay@mikom.csir.co.za From owner-freebsd-hackers Thu Jan 26 02:13:57 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id CAA20895 for hackers-outgoing; Thu, 26 Jan 1995 02:13:57 -0800 Received: from isl.cf.ac.uk (isl-gate.elsy.cf.ac.uk [131.251.22.1]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id CAA20880 for ; Thu, 26 Jan 1995 02:13:41 -0800 Received: (from paul@localhost) by isl.cf.ac.uk (8.6.9/8.6.9) id KAA08862; Thu, 26 Jan 1995 10:12:44 GMT From: Paul Richards Message-Id: <199501261012.KAA08862@isl.cf.ac.uk> Subject: Re: Is this a bug?!? To: terry@cs.weber.edu (Terry Lambert) Date: Thu, 26 Jan 1995 10:12:43 +0000 (GMT) Cc: wpaul@skynet.ctr.columbia.edu, bde@zeta.org.au, freebsd-hackers@FreeBSD.org In-Reply-To: <9501251628.AA18604@cs.weber.edu> from "Terry Lambert" at Jan 25, 95 09:28:40 am X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 511 Sender: hackers-owner@FreeBSD.org Precedence: bulk In reply to Terry Lambert who said > > > "My lord, I have a cunning plan." > > "Baldric, you wouldn't know a cunning plan if it danced on the table > singing 'cunning plans are here again'". > > 8-) 8-). > I take it Black Adder has made it to the US then? -- Paul Richards, FreeBSD core team member. Phone: +44 1222 874000 x6646 (work), +44 1222 457651 (home) Dept. Mechanical Engineering, University of Wales, College Cardiff. Internet: paul@FreeBSD.org, JANET(UK): RICHARDSDP@CARDIFF.AC.UK From owner-freebsd-hackers Thu Jan 26 02:59:29 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id CAA21833 for hackers-outgoing; Thu, 26 Jan 1995 02:59:29 -0800 Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id CAA21823 for ; Thu, 26 Jan 1995 02:59:17 -0800 Received: (from dfr@localhost) by minnow.render.com (8.6.9/8.6.9) id KAA25761; Thu, 26 Jan 1995 10:38:25 GMT Date: Thu, 26 Jan 1995 10:38:18 +0000 (GMT) From: Doug Rabson To: Julian Elischer cc: hackers@FreeBSD.org Subject: Re: Strange errors with AHA1542B In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hackers-owner@FreeBSD.org Precedence: bulk On Wed, 25 Jan 1995, Julian Elischer wrote: > > > > I just started noticing errors like this appearing on my console: > > > > blkno=3831389276 bcount=1949779968 flags=0x100010 > these figures are rubish > something has scribbled over something else.... > > Debugger("") called. > > aha0: aha_scsi_cmd, more than 17 DMA segs > yep, 1949779968 bytes is more than 17 x 4k pages.... > > > > sd1: oops not queue > > > > > Is this a known problem? Is it serious? > no and yes... > > (suspect H/W (cache?)) > does it happen after a reboot? > with a new kernel? This is with a FreeBSD-2.0-RELEASE kernel on a 486DX33 motherboard which has been happily running FreeBSD since it was called 386BSD-0.2.4. It happens very infrequently and does not *appear* to cause any problems. -- Doug Rabson, RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 71 251 4411 FAX: +44 71 251 0939 From owner-freebsd-hackers Thu Jan 26 10:36:42 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id KAA00155 for hackers-outgoing; Thu, 26 Jan 1995 10:36:42 -0800 Received: from inet-gw-1.pa.dec.com (inet-gw-1.pa.dec.com [16.1.0.22]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id KAA00147 for ; Thu, 26 Jan 1995 10:36:34 -0800 Received: from rks32.pcs.dec.com by inet-gw-1.pa.dec.com (5.65/10Aug94) id AA14157; Thu, 26 Jan 95 03:28:04 -0800 Received: by rks32.pcs.dec.com (Smail3.1.27.1 #16) id m0rXSMO-0005M7C; Thu, 26 Jan 95 12:27 MEZ Message-Id: To: mmead%goof.com@inet-gw-1.pa.dec.com Cc: hackers%freebsd.org@inet-gw-1.pa.dec.com In-Reply-To: Message from "matthew c. mead" of Wed, 25 Jan 95 16:01:57 EST. Reply-To: gj@FreeBSD.org Subject: Re: Motherboards Revisitied (GIGA-BYTE) Date: Thu, 26 Jan 95 11:27:32 GMT From: "gj%pcs.dec.com@inet-gw-1.pa.dec.com" Sender: hackers-owner@FreeBSD.org Precedence: bulk > Well, the best sounding motherboard that I have come across (if I stick > with the VLB motherboard option) is a GIGA-BYTE. Does anyone know of any > problems with their motherboards, or are they supposed to be pretty good? From > what I've heard they seem to be pretty stable. It's got an AWARD BIOS (never > heard of it...)... any experiences? Thanks... > > -matt I have a (really old) GIGA-BYTE MB which has served me faithfully with no problems. It's so old that the VL Bus slots were made to GIGA-BYTE's own spec. The only problem it's ever given me was when I tried to use an AMD DX2 in it. It couldn't find the FPU :( Using Bruce's memory speed program I get ~42 MB/sec to the L2-cache and ~26MB/sec to main memory, which are pretty good results. There's a magazine here in Germany called c't which regularly tests all MBs. GIGA-BYTE boards are almost always part of the group. Let me know which model you're interested in and I can check whether it was tested and tell you what c't thought of it. >From memory I can say that not all GIGA-BYTE boards were found to be good. But some of them were very good. It really depends a lot on which model you look at. Gary J. From owner-freebsd-hackers Thu Jan 26 10:38:17 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id KAA00261 for hackers-outgoing; Thu, 26 Jan 1995 10:38:17 -0800 Received: from prosun.first.gmd.de (prosun.first.gmd.de [192.35.150.136]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id KAA00184 for ; Thu, 26 Jan 1995 10:37:27 -0800 Received: from g386bsd.first.gmd.de by prosun.first.gmd.de (4.1/SMI-4.1) id AA07356; Thu, 26 Jan 95 17:16:31 +0100 Received: by g386bsd.first.gmd.de (RAA12826); Thu, 26 Jan 1995 17:17:49 +0059 From: Andreas Schulz Message-Id: <199501261618.RAA12826@g386bsd.first.gmd.de> Subject: Re: Directory entries get corrupted? To: jhay@mikom.csir.co.za (John Hay) Date: Thu, 26 Jan 1995 17:17:49 +0059 (MET) Cc: hackers@FreeBSD.org In-Reply-To: <199501260713.JAA04848@zibbi.mikom.csir.co.za> from "John Hay" at Jan 26, 95 09:13:19 am X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1447 Sender: hackers-owner@FreeBSD.org Precedence: bulk > I have two machines here with their hardware almost identical: 486DX2-66, > Adaptec 1542B SCSI card and Conner CFP1060S 1G disks. One is running 2.0R > and the other is running current. > When there is lots of disk activity like cvs checkout of the source tree > or tar extract from a tape, a fsck will report that some directories are > corrupted. The kernel however is quite happy with that directory it seems. > If I remove that directory or move the data in the directory somewhere else > and then remove the directory, fsck is quite happy with it. I have seen exactly the same failures with a 1542 and a Conner CFP1060S disk and it seems a firmware problem with the Conner disks. If you have a chance to get a firmware upgrade from Conner, try that. I have used after that a Fujitsu M2694 and now a Seagate Hawk disk on the same hardware without any problems. I have now seen three reports like that with Conner 1.0Gb udn 1.3Gb disks and four people have reported no problems. One mentioned there was a firmware upgrade for the 1.0Gb and only early disks showed this problem. Under DOS there is no problem with that disk. I have also used this disk with no problems for a short time in a SUN and now it landed in a MAC with no problems. ATS ( ats@first.gmd.de or ats@cs.tu-berlin.de ) Andreas Schulz GMD-FIRST 12489 Berlin-Adlershof Rudower Chaussee 5 Gebaeude 13.7 Tel: +49-30-6392-1856/+49-177-2134745 Germany/Europe From owner-freebsd-hackers Thu Jan 26 10:49:36 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id KAA00829 for hackers-outgoing; Thu, 26 Jan 1995 10:49:36 -0800 Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id KAA00819 for ; Thu, 26 Jan 1995 10:49:22 -0800 Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.6.9/8.6.6) id PAA06693; Thu, 26 Jan 1995 15:47:12 +0200 From: John Hay Message-Id: <199501261347.PAA06693@zibbi.mikom.csir.co.za> Subject: Re: Directory entries get corrupted? To: peter@bonkers.taronga.com (Peter da Silva) Date: Thu, 26 Jan 1995 15:47:12 +0200 (SAT) Cc: hackers@FreeBSD.org In-Reply-To: <199501261237.GAA07421@bonkers.taronga.com> from "Peter da Silva" at Jan 26, 95 06:37:29 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 588 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > Anything fsck tells you about an active file system should be taken with > a pinch of salt, a spoonful of sugar, and extreme suspicion. After all, it's > setpping through the disk looking for pointers to the wrong places while the > O/S is moving those pointers out from under it. It's no surprise that some > times the pointy end of a pointer is pointing to a block that's actually > holding something that pointer shouldn't be pointing to by the time it gets > around to it. > I get the same errors if I unmount that disk before doing the fsck. John Hay -- jhay@mikom.csir.co.za From owner-freebsd-hackers Thu Jan 26 10:49:52 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id KAA00852 for hackers-outgoing; Thu, 26 Jan 1995 10:49:52 -0800 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id KAA00831 for ; Thu, 26 Jan 1995 10:49:43 -0800 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id JAA04537; Thu, 26 Jan 1995 09:06:57 -0500 From: Peter Dufault Message-Id: <199501261406.JAA04537@hda.com> Subject: Re: kern/189: sd renames disks To: hsu@fx7.cs.hut.fi Date: Thu, 26 Jan 1995 09:06:56 -0500 (EST) Cc: freebsd-hackers@freefall.cdrom.com In-Reply-To: <199501260150.RAA10377@freefall.cdrom.com> from "Heikki Suonsivu" at Jan 25, 95 05:50:01 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 3628 Sender: hackers-owner@FreeBSD.org Precedence: bulk Heikki Suonsivu writes: > > > >Number: 189 > >Category: kern > >Synopsis: sd renames disks > >Confidential: no > >Severity: serious (...) > > sd thinks it is smarter than you on id's you want your disks have. Install > three disks, sd1a is /tmp and sd2a is users. Guess what happens if sd1 > breaks down, controller misses it by the phase of the moon, or you forget > to power it up if it is in an external box. > > I wouldn't be happy about editing fstab every time disk configuration changes, > but that is a minor problem compared to potential dangers this brings us. > > (I already complained, but maybe it is a good idea to gnats it so that it > won't be forgotten) > > >How-To-Repeat: > Some of this is present in sys/scsi/su.c, but there are a few things that have to be decided before it is complete. For example, ID 3 is a fujitsu drive: > hda.com# ls -lt /dev/rsd2d > crw-r----- 1 root operator 13, 19 Sep 26 00:01 /dev/rsd2d > hda.com# > hda.com# scsi -f /dev/rsd2d -c "12 0 0 0 64 0" -i 64 "s8 z8 z16" > FUJITSU M2654S-512 and I can access it through a fixed device with the SCSI ID embedded in the minor number (no, the man page isn't checked in on how the minor number format): > hda.com# mknod /dev/scsi/id3 c 18 458755 > hda.com# scsi -f /dev/scsi/id3 -c "12 0 0 0 64 0" -i 64 "s8 z8 z16" FUJITSU M2654S-512 > hda.com# mknod /dev/scsi/sd/rsd3 c 18 458758 > hda.com# mknod /dev/scsi/sd/sd3 b 18 458758 > hda.com# fsck -n /dev/scsi/sd/rsd3 > ** /dev/scsi/sd/rsd3 (NO WRITE) > ** Last Mounted on /mnt2 > ** Phase 1 - Check Blocks and Sizes > ^Chda.com# However, this does it through the minor numbers and not config. If you look in scsi/su.c (an unfortunate name that should be changed to fx.c for "fixed devices" before 2.1) you'll see that you can go from (BUS,ID,LUN) to underlying device, so if config is modified to build up a mapping table then you are almost done. However, we have to consider the problem of booting an old kernel and having the same problem Heikki mentions, namely, the new sd0 is scsi id3 or something and we mount on top of it and trash the disk. The same problem exists with the multiple host adapters: Currently they are "counting" host adapters also, and adding a host adapter with a disk will potentially trash your system. Some thoughts: 1. Keep the current "auto counting" devices exactly as they are. 2. Add "config'd" devices as a new facility, almost as Garrett proposed once before except they need new names: controller scbus0 at aha0 controller scbus1 at ncr0 disk ssd0 at scbus0 target 0 unit 0 disk ssd1 at scbus1 target 0 unit 0 tape sst0 at scbus0 target 5 device sch0 at scbus1 target 4 disk scd0 at scbus1 target 5 These have to be new devconf entries to avoid the "reboot old kernel and trash your system" problem, and can have new device entry points such as /dev/scsi/sd and so on. This will mean there will be three ways to get at a single scsi device: 1. Current "auto counting" devices; 2. Current "fixed" devices with target embedded in the minor number 3. Completely new conf'd devices. Any thoughts? P.S.: I use the fixed devices to access my tape drives. I don't mount my disks on them (mostly because I then can't boot old kernels) and thus don't consider that facility adequately tested. Peter -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 -- Formerly hd@world.std.com. E-mail problems? Tell hdslip@iii.net From owner-freebsd-hackers Thu Jan 26 11:00:00 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id LAA01300 for hackers-outgoing; Thu, 26 Jan 1995 11:00:00 -0800 Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id KAA01251 for ; Thu, 26 Jan 1995 10:58:43 -0800 Received: (from dfr@localhost) by minnow.render.com (8.6.9/8.6.9) id QAA00710; Thu, 26 Jan 1995 16:22:37 GMT Date: Thu, 26 Jan 1995 16:22:33 +0000 (GMT) From: Doug Rabson To: hackers@FreeBSD.org Subject: telldir Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hackers-owner@FreeBSD.org Precedence: bulk Telldir seems to be a cause of memory leaks in FreeBSD-2.0. It allocates memory on each call to telldir and the memory is not freed unless seekdir is called for the telldir cookie which was returned. For programs which call telldir many more times than seekdir, this can become a problem. I have noticed that the samba lanmanager server loses a hugh amount of memory in this way. Does anyone have any objections to me changing the code so that closedir reclaims memory for any outstanding telldir cookies? The manpage states that they are not useful after the directory is closed anyway. -- Doug Rabson, RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 71 251 4411 FAX: +44 71 251 0939 From owner-freebsd-hackers Thu Jan 26 11:02:20 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id LAA01390 for hackers-outgoing; Thu, 26 Jan 1995 11:02:20 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id LAA01384 for ; Thu, 26 Jan 1995 11:02:15 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA24506; Thu, 26 Jan 95 09:31:55 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9501261631.AA24506@cs.weber.edu> Subject: Re: SyQuest works with FreeBSD 2.0R ! To: john@pyromania.apana.org.au (John Herks) Date: Thu, 26 Jan 95 9:31:55 MST Cc: hackers@FreeBSD.org In-Reply-To: <199501260422.PAA00192@pyromania.apana.org.au> from "John Herks" at Jan 26, 95 03:22:36 pm X-Mailer: ELM [version 2.4dev PL52] Sender: hackers-owner@FreeBSD.org Precedence: bulk > > I have just installed a SyQuest 3.5" 270 MB removable SCSI drive in my > FreeBSD 2.0R system. > > So far everything seems to work just fine! I was speaking to Darren Davis (the author of IOmega's Bernoulli drivers for various types of UNIX, and now in UnixWare developer support at Novell) about removable media about a year ago. You need to be careful if you have more than one drive that you only use a single disk in a single drive for a system boot instance, since the OS (incorrectly) uses the device as part of the ident, and can get confused if you switch drives. Otherwise, you should have no problems. Note that Bernoulli's themselves have formatting issues -- they don't use a vendor private for their detach format. If anyone else is considering Bernoulli vs. Syquest, this should be part of their decision. Also dual Bernoulli's and dual Syquest use LUNs on a single target to get two devices. Some of the SCSI drivers are "uncomfortable" with LUNs. I would suggest seperate drives at this time. I suspect throwing in AIX style volume management would muddy the waters considerably, but no one has done that (yet). Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Thu Jan 26 11:05:33 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id LAA01518 for hackers-outgoing; Thu, 26 Jan 1995 11:05:33 -0800 Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.20.4]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id LAA01512 for ; Thu, 26 Jan 1995 11:05:31 -0800 Received: by brasil.moneng.mei.com (4.1/SMI-4.1) id AA01346; Thu, 26 Jan 95 08:12:23 CST From: Joe Greco Message-Id: <9501261412.AA01346@brasil.moneng.mei.com> Subject: Re-clocking a 16550 for 230,400: To: hackers@FreeBSD.org Date: Thu, 26 Jan 1995 08:12:22 -0600 (CST) X-Mailer: ELM [version 2.4beta PL9] Content-Type: text Content-Length: 1666 Sender: hackers-owner@FreeBSD.org Precedence: bulk (taken from a Usenet article I just posted. Reposted here because it seems appropriate): I've looked over all the data sheets. I've looked through a bunch of Usenet FAQ's. I've looked at the sources for my OS's serial device drivers. Problem: I need a 230,400 bps serial port. Somebody's suggested solution: Buy a Hayes high speed serial card, and select the "4x clock" option. My objection: Very expensive solution, particularly since my OS does not yet have driver support for the Hayes card, and it would be used in 16550-compat mode. I'm running FreeBSD 2.0R. I've looked at the NS data sheets for the 16550 which suggest that a 4MHz or 8MHz clock is fine, and that the maximum speed supported by the part is 256Kbps. Now, it would seem to me that it would be a trivial hobbyist level upgrade to toss a 3.6864MHz crystal on an ordinary, everyday PC serial card to effectively double the clock rate. I have not (yet) tried this, but I was suprised that it was not covered in a FAQ, if it is as simple an upgrade as it seems (I don't see why not). I am using the Startech 16552 part for most of my serial ports, by the way, in case it makes a difference. Has anybody tried this? Succeeded? Failed? Half & Half? :-) Since I don't think that this is of particular interest to the average hacker, followups have been redirected to poster. I will happily summarize any answers (and my own results) if there is any interest in this. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 From owner-freebsd-hackers Thu Jan 26 11:08:44 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id LAA01636 for hackers-outgoing; Thu, 26 Jan 1995 11:08:44 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id LAA01628 for ; Thu, 26 Jan 1995 11:08:40 -0800 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id LAA00957; Thu, 26 Jan 1995 11:08:25 -0800 From: Poul-Henning Kamp Message-Id: <199501261908.LAA00957@ref.tfs.com> Subject: Re: telldir To: dfr@render.com (Doug Rabson) Date: Thu, 26 Jan 1995 11:08:23 -0800 (PST) Cc: hackers@FreeBSD.org In-Reply-To: from "Doug Rabson" at Jan 26, 95 04:22:33 pm Content-Type: text Content-Length: 388 Sender: hackers-owner@FreeBSD.org Precedence: bulk > Does anyone have any objections to me changing the code so that closedir > reclaims memory for any outstanding telldir cookies? The manpage states > that they are not useful after the directory is closed anyway. By all means, please do! -- Poul-Henning Kamp TRW Financial Systems, Inc. FreeBSD has, until now, not one single time had an undetected error. :-) From owner-freebsd-hackers Thu Jan 26 11:56:15 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id LAA02805 for hackers-outgoing; Thu, 26 Jan 1995 11:56:15 -0800 Received: from liner.polytech.kiev.ua ([194.44.128.15]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id LAA02753 for ; Thu, 26 Jan 1995 11:50:26 -0800 Received: (from root@localhost) by liner.polytech.kiev.ua (8.6.9/8.6.9) id VAA00349 for hackers@FreeBSD.org; Thu, 26 Jan 1995 21:39:27 +0200 Date: Thu, 26 Jan 1995 21:39:27 +0200 From: Charlie Root Message-Id: <199501261939.VAA00349@liner.polytech.kiev.ua> To: hackers@FreeBSD.org Subject: Digiboard PC/16e driver needed!!! Sender: hackers-owner@FreeBSD.org Precedence: bulk Hi!! Is any way use Digiboard PC/16e in FreeBSD-2.0? If you know anything relevant please mail me! Thanx for cooperation. Vladimir. From owner-freebsd-hackers Thu Jan 26 12:23:29 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id MAA03331 for hackers-outgoing; Thu, 26 Jan 1995 12:23:29 -0800 Received: from inet-gw-1.pa.dec.com (inet-gw-1.pa.dec.com [16.1.0.22]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id MAA03325 for ; Thu, 26 Jan 1995 12:23:27 -0800 Received: from goof.com by inet-gw-1.pa.dec.com (5.65/10Aug94) id AA24130; Thu, 26 Jan 95 12:14:46 -0800 Received: (from mmead@localhost) by goof.com (8.6.9/8.6.9) id PAA05245; Thu, 26 Jan 1995 15:14:18 -0500 From: "matthew c. mead" Message-Id: <199501262014.PAA05245@goof.com> Subject: Re: Motherboards Revisitied (GIGA-BYTE) To: gj@FreeBSD.org Date: Thu, 26 Jan 1995 15:14:18 -0500 (EST) Cc: mmead%goof.com@inet-gw-1.pa.dec.com, hackers%freebsd.org@inet-gw-1.pa.dec.com In-Reply-To: from "gj%pcs.dec.com@inet-gw-1.pa.dec.com" at Jan 26, 95 11:27:32 am X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1660 Sender: hackers-owner@FreeBSD.org Precedence: bulk gj%pcs.dec.com@inet-gw-1.pa.dec.com wrote: > > Well, the best sounding motherboard that I have come across (if I stick > > with the VLB motherboard option) is a GIGA-BYTE. Does anyone know of any > > problems with their motherboards, or are they supposed to be pretty good? From > > what I've heard they seem to be pretty stable. It's got an AWARD BIOS (never > > heard of it...)... any experiences? Thanks... > > > > -matt > I have a (really old) GIGA-BYTE MB which has served me faithfully with > no problems. It's so old that the VL Bus slots were made to GIGA-BYTE's > own spec. The only problem it's ever given me was when I tried to use > an AMD DX2 in it. It couldn't find the FPU :( Using Bruce's memory > speed program I get ~42 MB/sec to the L2-cache and ~26MB/sec to main > memory, which are pretty good results. Sounds pretty good... > There's a magazine here in Germany called c't which regularly tests all > MBs. GIGA-BYTE boards are almost always part of the group. Let me know > which model you're interested in and I can check whether it was tested > and tell you what c't thought of it. The people who sell it said it's their VF motherboard. It's a 486 VLB/ISA motherboard. > >From memory I can say that not all GIGA-BYTE boards were found to be good. > But some of them were very good. It really depends a lot on which model > you look at. Hmm. Let me know if you need more information... -matt -- Matthew C. Mead -- System/Network Administration, User Support, Software Devel. Virginia Tech Center for Transportation Research Work Related: mmead@ctr.vt.edu | All Other: mmead@goof.com WWW: http://www.goof.com:/~mmead From owner-freebsd-hackers Thu Jan 26 12:42:00 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id MAA03544 for hackers-outgoing; Thu, 26 Jan 1995 12:42:00 -0800 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id MAA03538 for ; Thu, 26 Jan 1995 12:41:49 -0800 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.8/jtpda-5.0) with SMTP id VAA24228 for ; Thu, 26 Jan 1995 21:40:38 +0100 Received: by blaise.ibp.fr (4.1/SMI-4.1) id AA13203; Thu, 26 Jan 95 21:40:35 +0100 From: roberto@blaise.ibp.fr (Ollivier ROBERT) Message-Id: <9501262040.AA13203@blaise.ibp.fr> Subject: sig 11 and sig 10 To: roberto@blaise.ibp.fr (Ollivier ROBERT) Date: Thu, 26 Jan 1995 21:40:34 +0100 (MET) Cc: hackers@FreeBSD.org In-Reply-To: <9501252317.AA08190@blaise.ibp.fr> from "Ollivier ROBERT" at Jan 26, 95 00:17:22 am X-Operating-System: FreeBSD 2.1.0-Development ctm#292 X-Mailer: ELM [version 2.4 PL23beta2] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1491 Sender: hackers-owner@FreeBSD.org Precedence: bulk > PS: for my previous sig11 with sendmail and cron, a recompilation of all > the libraries (I suspect an old libkvm or such) it seems to be back > as always. Thanks for listening :-) cron is back normally. sendmail keeps dumping core every 31m (the -q31m parameter...). Jan 26 16:26:49 keltia /kernel: pid 29809: sendmail: uid 0: exited on signal 11 Jan 26 16:57:49 keltia /kernel: pid 29810: sendmail: uid 0: exited on signal 11 Jan 26 17:28:49 keltia /kernel: pid 29868: sendmail: uid 0: exited on signal 11 Jan 26 17:59:49 keltia /kernel: pid 29869: sendmail: uid 0: exited on signal 11 Jan 26 18:30:49 keltia /kernel: pid 29873: sendmail: uid 0: exited on signal 11 Jan 26 19:00:56 keltia login: login on tty00 as uuitesec Jan 26 19:01:49 keltia /kernel: pid 29884: sendmail: uid 0: exited on signal 11 Jan 26 19:32:49 keltia /kernel: pid 29888: sendmail: uid 0: exited on signal 11 Jan 26 20:03:49 keltia /kernel: pid 29902: sendmail: uid 0: exited on signal 11 I just got two core from inetd when invoking rlogin to my computer : Jan 26 20:56:09 keltia /kernel: pid 29958: inetd: uid 0: exited on signal 10 Jan 26 20:56:09 keltia /kernel: uid 0 on /: file system full Jan 26 20:56:04 keltia /kernel: pid 29957: inetd: uid 0: exited on signal 10 Jan 26 20:56:05 keltia /kernel: uid 0 on /: file system full Something is bad somewhere. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@FreeBSD.ORG FreeBSD keltia 2.1.0-Development #9: Tue Jan 17 21:12:14 MET 1995 From owner-freebsd-hackers Thu Jan 26 12:53:24 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id MAA03740 for hackers-outgoing; Thu, 26 Jan 1995 12:53:24 -0800 Received: from UUCP-GW.CC.UH.EDU (root@UUCP-GW.CC.UH.EDU [129.7.1.11]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id MAA03733 for ; Thu, 26 Jan 1995 12:53:09 -0800 Received: from Taronga.COM by UUCP-GW.CC.UH.EDU with UUCP id AA26348 (5.67a/IDA-1.5); Thu, 26 Jan 1995 06:38:48 -0600 Received: by bonkers.taronga.com (smail2.5p) id AA07424; 26 Jan 95 06:37:33 CST (Thu) Received: from localhost (localhost [127.0.0.1]) by bonkers.taronga.com (8.6.8/8.6.6) with SMTP id GAA07421; Thu, 26 Jan 1995 06:37:32 -0600 Message-Id: <199501261237.GAA07421@bonkers.taronga.com> X-Authentication-Warning: bonkers.taronga.com: Host localhost didn't use HELO protocol To: John Hay Cc: hackers@FreeBSD.org Subject: Re: Directory entries get corrupted? In-Reply-To: Your message of "Sat, 26 Jan 95 09:13:19 +0200." <199501260713.JAA04848@zibbi.mikom.csir.co.za> X-Mailer: exmh version 1.4.1 7/21/94 Date: Thu, 26 Jan 1995 06:37:29 -0600 From: Peter da Silva Sender: hackers-owner@FreeBSD.org Precedence: bulk Anything fsck tells you about an active file system should be taken with a pinch of salt, a spoonful of sugar, and extreme suspicion. After all, it's setpping through the disk looking for pointers to the wrong places while the O/S is moving those pointers out from under it. It's no surprise that some times the pointy end of a pointer is pointing to a block that's actually holding something that pointer shouldn't be pointing to by the time it gets around to it. From owner-freebsd-hackers Thu Jan 26 14:31:15 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id OAA05913 for hackers-outgoing; Thu, 26 Jan 1995 14:31:15 -0800 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id OAA05903 for ; Thu, 26 Jan 1995 14:31:08 -0800 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.8/jtpda-5.0) with SMTP id XAA24988 for ; Thu, 26 Jan 1995 23:32:19 +0100 Received: by blaise.ibp.fr (4.1/SMI-4.1) id AA13690; Thu, 26 Jan 95 23:32:15 +0100 From: roberto@blaise.ibp.fr (Ollivier ROBERT) Message-Id: <9501262232.AA13690@blaise.ibp.fr> Subject: Re: sig 11 and sig 10 To: roberto@blaise.ibp.fr (Ollivier ROBERT) Date: Thu, 26 Jan 1995 23:32:15 +0100 (MET) Cc: hackers@FreeBSD.org In-Reply-To: <9501262040.AA13203@blaise.ibp.fr> from "Ollivier ROBERT" at Jan 26, 95 09:40:34 pm X-Operating-System: FreeBSD 2.1.0-Development ctm#292 X-Mailer: ELM [version 2.4 PL23beta2] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 338 Sender: hackers-owner@FreeBSD.org Precedence: bulk > sendmail keeps dumping core every 31m (the -q31m parameter...). CTM#307 and/or patch from Doug (Thanks) seem to have fixed the problem. No sendmail's core or inetd core for almost an hour. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@FreeBSD.ORG FreeBSD keltia 2.1.0-Development #18: Thu Jan 26 22:22:16 MET 1995 From owner-freebsd-hackers Thu Jan 26 15:38:27 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id PAA00314 for hackers-outgoing; Thu, 26 Jan 1995 15:38:27 -0800 Received: from expo.x.org (expo.x.org [198.112.45.11]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id PAA00308 for ; Thu, 26 Jan 1995 15:38:22 -0800 Received: from fedora.x.org by expo.x.org id AA01717; Thu, 26 Jan 95 18:37:48 -0500 Received: by fedora.x.org id AA15538; Thu, 26 Jan 1995 18:37:47 -0500 Message-Id: <9501262337.AA15538@fedora.x.org> To: hackers@freefall.cdrom.com Subject: comp.unix.bsd reorg Date: Thu, 26 Jan 1995 18:37:47 EST From: Kaleb Keithley Sender: hackers-owner@FreeBSD.org Precedence: bulk You asked for it, you got it. The Call For Votes has finally appeared in news.announce.newgroups. Spread the word. -- Kaleb KEITHLEY From owner-freebsd-hackers Thu Jan 26 21:30:40 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id VAA07367 for hackers-outgoing; Thu, 26 Jan 1995 21:30:40 -0800 Received: from seagull.rtd.com (root@Seagull.rtd.com [198.102.68.2]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id VAA07361 for ; Thu, 26 Jan 1995 21:30:38 -0800 Received: (from dgy@localhost) by seagull.rtd.com (8.6.9/8.6.9.1) id WAA06166; Thu, 26 Jan 1995 22:30:30 -0700 From: Don Yuniskis Message-Id: <199501270530.WAA06166@seagull.rtd.com> Subject: Re: Is this a bug?!? To: paul@isl.cf.ac.uk (Paul Richards) Date: Thu, 26 Jan 1995 22:30:21 -0700 (MST) Cc: freebsd-hackers@freefall.cdrom.com (FreeBSD hackers) In-Reply-To: <199501261012.KAA08862@isl.cf.ac.uk> from "Paul Richards" at Jan 26, 95 10:12:43 am X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 278 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > "Baldric, you wouldn't know a cunning plan if it danced on the table > > singing 'cunning plans are here again'". > > I take it Black Adder has made it to the US then? Quite some time ago... actually, depending on what part of the country you're in, it comes and goes... From owner-freebsd-hackers Fri Jan 27 00:00:45 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id AAA10095 for hackers-outgoing; Fri, 27 Jan 1995 00:00:45 -0800 Received: from emma.sea.uct.ac.za (emma.sea.uct.ac.za [137.158.131.151]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id AAA10089 for ; Fri, 27 Jan 1995 00:00:25 -0800 Received: (from shaun@localhost) by emma.sea.uct.ac.za (8.6.8/8.6.6) id JAA06836 for hackers@freefall.cdrom.com; Fri, 27 Jan 1995 09:59:22 +0200 From: Shaun Courtney Message-Id: <199501270759.JAA06836@emma.sea.uct.ac.za> Subject: wu-ftpd-2.4 under FreeBSD 1.1.5.1 To: hackers@freefall.cdrom.com Date: Fri, 27 Jan 1995 09:59:12 +0200 (GMT+0200) X-Mailer: ELM [version 2.4 PL23beta2] Content-Type: text Content-Length: 528 Sender: hackers-owner@FreeBSD.org Precedence: bulk Hi all The problem with wu-ftpd under FreeBSD 1.1.5.1 is that works fine for anonymous ftp, but it doesn't read the shadow passwd files for normal users, much to the annoyance. Difining HAVE_SHADOW doesn't work because ftpd.c can't find shadow.h! Does someone have patch for this program, please email it to me or put it up for ftp if possible. (I know FreeBSD 2 is out, but I'm waiting for 2.1 :) Thanks Shaun Courtney -- Oceanography Department University of Cape Town, South Africa url: http://emma.sea.uct.ac.za From owner-freebsd-hackers Fri Jan 27 01:43:00 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id BAA11515 for hackers-outgoing; Fri, 27 Jan 1995 01:43:00 -0800 Received: from campino.informatik.rwth-aachen.de (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id BAA11509 for ; Fri, 27 Jan 1995 01:42:46 -0800 Received: from gilberto.physik.rwth-aachen.de by campino.informatik.rwth-aachen.de (4.1/campino-6) id AA27840; Thu, 26 Jan 95 12:54:38 +0100 Received: by gilberto.physik.rwth-aachen.de (NAA16351); Thu, 26 Jan 1995 13:01:06 +0100 Date: Thu, 26 Jan 1995 13:01:06 +0100 From: "Christoph P. Kukulies" Message-Id: <199501261201.NAA16351@gilberto.physik.rwth-aachen.de> To: freebsd-hackers@freefall.cdrom.com Subject: nfs problems with -current Sender: hackers-owner@FreeBSD.org Precedence: bulk >From man exports I see that mapping root=0 is now maproot=root. Trying so always results in an error on the client side: mozart# mount blues:/home/ports-2.0 /usr/ports nfs: cant access /home/ports-2.0: Address already in use mozart# This is between two quite recently built -current machines: Server: FreeBSD blues 2.1.0-Development FreeBSD 2.1.0-Development #0: Wed Jan 18 21:05:52 1995 root@blues:/usr/src/sys/compile/BLUES i386 Client: FreeBSD mozart 2.1.0-Development FreeBSD 2.1.0-Development #0: Wed Jan 25 15:09:11 1995 kuku@blues:/usr/src/sys/compile/MOZART20 i386 --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de FreeBSD blues 2.1.0-Development FreeBSD 2.1.0-Development #1: Wed Jan 18 10:42:31 1995 kuku@blues:/usr/src/sys/compile/BLUES i386 From owner-freebsd-hackers Fri Jan 27 04:17:14 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id EAA14942 for hackers-outgoing; Fri, 27 Jan 1995 04:17:14 -0800 Received: from galactica.galactica.it (galactica.galactica.it [192.106.152.1]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id EAA14933 for ; Fri, 27 Jan 1995 04:16:55 -0800 Received: from galactic.UUCP (root@localhost) by galactica.galactica.it (8.6.9/8.6.9) with UUCP id MAA08558 for hackers@FreeBSD.org; Fri, 27 Jan 1995 12:28:21 +0100 To: hackers@FreeBSD.org Subject: '.' in user name From: davide.tome'@galactica.it (DAVIDE TOME') Message-ID: <8A262CE.00010088AA.uuout@galactica.it> Date: Fri, 27 Jan 95 11:58:00 +0100 Organization: GALACTICA PROFESSIONAL COMMUNICATION - ++39-2-29.00.61.50 Reply-To: davide.tome'@galactica.it (DAVIDE TOME') X-Mailreader: PCBoard Version 15.21 X-Mailer: PCBoard/UUOUT Version 1.10 Sender: hackers-owner@FreeBSD.org Precedence: bulk Hi, I need to have users names with '.' character .... like pippo.pluto How can I do it ??? Ciao Davide Dott. Davide Tome' ------------------------------------------------- Internet .....: davide.tome'@galactica.it Fido..........: 2:331/358 davide tome' Galactica BBS.: +39-2-29006058 (24H 24 lines r.a) Voce..........: +39-2-29006150 Fax...........: +39-2-29006153 ------------------------------------------------- From owner-freebsd-hackers Fri Jan 27 04:19:49 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id EAA14982 for hackers-outgoing; Fri, 27 Jan 1995 04:19:49 -0800 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id EAA14976 for ; Fri, 27 Jan 1995 04:19:46 -0800 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id GAA07921; Fri, 27 Jan 1995 06:50:47 -0500 From: Peter Dufault Message-Id: <199501271150.GAA07921@hda.com> Subject: Re: SyQuest works with FreeBSD 2.0R ! To: terry@cs.weber.edu (Terry Lambert) Date: Fri, 27 Jan 1995 06:50:47 -0500 (EST) Cc: john@pyromania.apana.org.au, hackers@FreeBSD.org In-Reply-To: <9501261631.AA24506@cs.weber.edu> from "Terry Lambert" at Jan 26, 95 09:31:55 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2028 Sender: hackers-owner@FreeBSD.org Precedence: bulk Terry Lambert writes: > > > > > I have just installed a SyQuest 3.5" 270 MB removable SCSI drive in my > > FreeBSD 2.0R system. > > > > So far everything seems to work just fine! > > I was speaking to Darren Davis (the author of IOmega's Bernoulli drivers > for various types of UNIX, and now in UnixWare developer support at Novell) > about removable media about a year ago. > > You need to be careful if you have more than one drive that you only use > a single disk in a single drive for a system boot instance, since the > OS (incorrectly) uses the device as part of the ident, and can get > confused if you switch drives. I don't follow this. Is this a FreeBSD problem? > > Otherwise, you should have no problems. Actually, I think he will have a problem - UNIT ATTENTION is generated when the removable drive is changed. 2.0R doesn't retry at all on this, and 2.0-current will retry but not for removable drives because of the chance of someone swapping a mounted drive. I think we have to track the "first access after open" and retry even for removable drives in that case. I'd like a description of what happens when you unmount a file system, change the media, and try to mount a filesystem on a removable drive, including dmesg output. > Note that Bernoulli's themselves have formatting issues -- they don't use > a vendor private for their detach format. If anyone else is considering > Bernoulli vs. Syquest, this should be part of their decision. > > Also dual Bernoulli's and dual Syquest use LUNs on a single target to > get two devices. Some of the SCSI drivers are "uncomfortable" with LUNs. > I would suggest seperate drives at this time. Which drivers are uncomforable with LUNS? They shouldn't be too hard to fix. We need some pioneers... Peter -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 -- Formerly hd@world.std.com. E-mail problems? Tell hdslip@iii.net From owner-freebsd-hackers Fri Jan 27 06:11:45 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id GAA17080 for hackers-outgoing; Fri, 27 Jan 1995 06:11:45 -0800 Received: from UUCP-GW.CC.UH.EDU (root@UUCP-GW.CC.UH.EDU [129.7.1.11]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id GAA17071 for ; Fri, 27 Jan 1995 06:11:41 -0800 Received: from Taronga.COM by UUCP-GW.CC.UH.EDU with UUCP id AA12216 (5.67a/IDA-1.5); Fri, 27 Jan 1995 07:59:05 -0600 Received: by bonkers.taronga.com (smail2.5p) id AA09308; 27 Jan 95 07:58:16 CST (Fri) Received: from localhost (localhost [127.0.0.1]) by bonkers.taronga.com (8.6.8/8.6.6) with SMTP id HAA09305; Fri, 27 Jan 1995 07:58:15 -0600 Message-Id: <199501271358.HAA09305@bonkers.taronga.com> X-Authentication-Warning: bonkers.taronga.com: Host localhost didn't use HELO protocol To: Peter Dufault Cc: terry@cs.weber.edu (Terry Lambert), john@pyromania.apana.org.au, hackers@FreeBSD.org Subject: Re: SyQuest works with FreeBSD 2.0R ! In-Reply-To: Your message of "Fri, 27 Jan 95 06:50:47 EST." <199501271150.GAA07921@hda.com> X-Mailer: exmh version 1.4.1 7/21/94 Date: Fri, 27 Jan 1995 07:58:08 -0600 From: Peter da Silva Sender: hackers-owner@FreeBSD.org Precedence: bulk The real solution to removable media is to put some sort of ident in the disklabel (including time and system ID) and track that. If you have a mounted filesystem and get a UNIT ATTENTION then you can see whether it's been swapped or not. (yes, you can still defeat this with a dd to the raw device) What would be really cool would be to create a new pseudo-device entry when you mount the device, and treat each volume as a separate device. Then you could simply stall attempts to access a filesystem mounted on a device that's been removed. Perhaps even have a hook to alert the user when they do that to insert the appropriate volume... (ok, that's blue-sky... an ID in the disklabel is just good hygeine) From owner-freebsd-hackers Fri Jan 27 06:48:38 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id GAA18036 for hackers-outgoing; Fri, 27 Jan 1995 06:48:38 -0800 Received: from anvil.appsmiths.com (appsmiths.sccsi.com [198.65.134.98]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id GAA18031 for ; Fri, 27 Jan 1995 06:48:36 -0800 Received: (from hoppy@localhost) by anvil.appsmiths.com (8.6.8/8.6.6) id IAA17392 for hackers@FreeBSD.org; Fri, 27 Jan 1995 08:48:11 -0600 From: "Clay D. Hopperdietzel" Message-Id: <199501271448.IAA17392@anvil.appsmiths.com> Subject: >1024 cyl IDE drive To: hackers@FreeBSD.org Date: Fri, 27 Jan 1995 08:48:09 -0600 (CST) X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 703 Sender: hackers-owner@FreeBSD.org Precedence: bulk What a pile. This thing seems to have some special *boot* code on it to scramble BIOS' brain. >1600 cylinders. Some looney software to write the boot-block, partition it (oh, you want 2 partitions, okay here's 2 400MB partitions!). Has anybody ever made one of these goofy things work with FreeBSD, or should I just give it a fling? Thought it might be interesting to play with. I decided to give it a try, since the el-sleezo (dirt-cheep) PC sellers are pushing these hard. If it won't work, I can easily get my money back. The reason I took it was to see what kind of trouble they generate. It will only be a matter of time before these things are romping the planet and causing trouble. From owner-freebsd-hackers Fri Jan 27 06:55:53 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id GAA18274 for hackers-outgoing; Fri, 27 Jan 1995 06:55:53 -0800 Received: from dataplex.net (SHARK.DATAPLEX.NET [199.183.109.241]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id GAA18262 for ; Fri, 27 Jan 1995 06:55:50 -0800 Received: from [199.183.109.242] by dataplex.net with SMTP (MailShare 1.0b8); Fri, 27 Jan 1995 08:55:43 -0600 X-Sender: wacky@shark.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 27 Jan 1995 08:55:43 -0600 To: hackers@FreeBSD.org, freebsd-current@freefall.cdrom.com From: rkw@dataplex.net (Richard Wackerbarth) Subject: REMAKE WORLD Sender: hackers-owner@FreeBSD.org Precedence: bulk OK, guys! I'm on the "make" and I'm 'gonna take on the world. The warts on the makefile system have gotten out of control. It is time to throw out the old nag and get a fresh horse. I've "talked" to Jordan and we agree that this is a "good idea(tm)." Nothing is sacred. The plan: 1) Determine design goals 2) Design file structure to accomplish it. 3) Implement .mk files 4) Bring Makefiles into conformity. Although I have already given it some thought and think I have a good structure to accomplish it, we are just at step 1. Hopefully we can accomplish this for 2.1. If not, at least we can be well on the way. I'll start by throwing out a few ideas. Some of them may not fly, but that is OK. Right now, we need to decide WHAT rather than HOW. 1. The build procedure should run on any machine that meets certain minimal specs. (Like maybe 1.1.5.1) Doing a build will in NO way affect the host environment. 2. If everything is up to date, a make will do nothing except scan the tree. Nothing gets rebuilt unless it is out of date. 3. Build targets should exist for upgrading the running system, building a new root partition, and building tarball release files. Each of these would work off of the same object tree. 4. The make procedure is not allowed to "touch" it's input tree. The source tree can be read-only. The object tree can be read-only if up-to-date. 5. Multiple targets can co-exist at the same time. The entire process has a floating root. No path is hard coded. 6. Symbolic links are permitted. (This is a hard one because /../ does not necessarily get you back where you were :-( ) So much for starters. What other ideas do you want to throw in? 7. I know that we are not NetBSD but ... Multi-platform cross compiling is close enough to a fall-out that I think we should include the mechanism for it. 8. For those of us who build "sup -current" trees, the ability to post a "forget this program" lock which will allow a virtual delete of targets that do not properly build without altering the Makefiles. From owner-freebsd-hackers Fri Jan 27 07:34:53 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id HAA20578 for hackers-outgoing; Fri, 27 Jan 1995 07:34:53 -0800 Received: from relay-europe.ps.net (relay-europe.ps.net [160.110.96.10]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id HAA20571 for ; Fri, 27 Jan 1995 07:34:51 -0800 Received: by relay-europe.ps.net (AIX 3.2/UCB 5.64/4.03) id AA07593; Fri, 27 Jan 1995 15:39:39 GMT Date: Fri, 27 Jan 1995 15:39:38 +0000 (GMT) From: Aled Morris Subject: PCMCIA modem To: hackers@FreeBSD.org Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hackers-owner@FreeBSD.org Precedence: bulk What's the current status of support for PCMCIA modems? I have 2.0R, and I tried adding: device sio2 at isa? port "IO_COM3" tty irq 11 vector siointr to my config file, but the card wasn't recognised on startup. Under DOS I can see the card from kermit using 3E8 and IRQ 11 - does this work because Card Services are used in DOS? Anyway, is there a quick fix to make this work, or do I have to wait till the hot-swap-PCMCIA release of FreeBSD to use my modem? Aled -- aledm@relay-europe.ps.net | tel +44 973 207987 Perot Systems Europe Ltd. | fax +44 181 476 2419 From owner-freebsd-hackers Fri Jan 27 07:40:05 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id HAA20681 for hackers-outgoing; Fri, 27 Jan 1995 07:40:05 -0800 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id HAA20669 for ; Fri, 27 Jan 1995 07:39:58 -0800 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id KAA08510; Fri, 27 Jan 1995 10:39:52 -0500 From: Peter Dufault Message-Id: <199501271539.KAA08510@hda.com> Subject: Re: Help with SCSI development (fwd) To: freebsd-hackers@FreeBSD.org Date: Fri, 27 Jan 1995 10:39:51 -0500 (EST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 4936 Sender: hackers-owner@FreeBSD.org Precedence: bulk Peter Dufault writes: >From owner-freebsd-scsi@freefall.cdrom.com Fri Jan 27 13:31:15 1995 From: Peter Dufault Message-Id: <199501271137.GAA07903@hda.com> Subject: Re: Help with SCSI development To: vernick@cs.sunysb.edu (Michael Vernick) Date: Fri, 27 Jan 1995 06:37:07 -0500 (EST) Cc: freebsd-scsi@FreeBSD.org In-Reply-To: <199501270128.AA07506@cs.sunysb.edu> from "Michael Vernick" at Jan 26, 95 08:28:27 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 4132 Sender: freebsd-scsi-owner@FreeBSD.org Precedence: bulk I'm forwarding this to -hackers instead of just -scsi and including the full reference, since it is more than a scsi question. Michael Vernick writes: > > I'm planning to write software using Freebsd that will allow files to > be striped over multiple disks. At first, I plan on implmenting reads > only using a simple file system I plan to eventually write. Since I'm > new to the internals of Freebsd and Unix in general I was hoping that > I could get a little help. I've started going through the code and > have some questions. At first, I'd like to implement this in user > code using 1 process. This process will read the data from each disk. > Are there any direct calls to the scsi driver from user space? I saw > something about user calls in scsi_ioctl.c but couldn't figure out how > to access it. If there are user level calls, are they asynchronous? > What I'd like to do is issue a bunch of reads (1 for each disk) to the > controller all at once and then wait for the data to be returned. If I > can't make asynchronous calls in user space, I guess that I could have > multiple processes, one for each disk, where each process sends a > synchronous read to the driver, and once all of the processes finish, > accumulate the data. > > Eventually, I want to move this into the kernel. When it becomes a > kernel level process, at what level do I issue calls. At the > physio/bread level or lower? Also, I believe that physio and bread > call the scsi strategy function using a function pointer. Where does > this function pointer get set up? Lastly, is there any documentation > where I could get a better handle on how things work within the scsi > part of the IO subsystem? > > Thanks for any help. > > Michael Vernick > > Two overall comments: 1. This is independent of SCSI and more appropriates addressed as a pseudodevice that stripes multiple disk partitions and not just SCSI disk drives. I'm not sure how you configure these stripes to be persistent across reboots. Since it isn't likely that you'll ever boot off them they could get configured in rc after root is mounted and before the other partitions are mounted (the approach on the Alliant systems, which had a similar facility. I'm sure Convex and probably SGI have this also so you may want to look for some man pages). 2. Is your goal size or throughput? For size we still have a 2GB partition limit (maybe 4 but I'm not sure), and for throughput I'm not sure how well the PC architectures will distribute the I/O load across multiple host adapters (though I suppose with disconnect/reconnect and high burst rates to drives with caches it may work fairly well). 3. Sector sizes: In the general case you're likely to wind up with some pretty big sectors that may not work in all situations (I'm just guessing about this). Now, some of your questions: > I saw > something about user calls in scsi_ioctl.c but couldn't figure out how > to access it. Look at scsi(3) and scsi(8) in 2.0-current. This is not present in 2.0-R. > If there are user level calls, are they asynchronous? No. > Eventually, I want to move this into the kernel. When it becomes a > kernel level process, at what level do I issue calls. At the > physio/bread level or lower? Also, I believe that physio and bread > call the scsi strategy function using a function pointer. Where does > this function pointer get set up? Lastly, is there any documentation > where I could get a better handle on how things work within the scsi > part of the IO subsystem? I think the essence will be to have a stripe strategy routine that splits the single buf struct into multiple ones for the underlying drives, loops over the underlying drives calling the strategy routine, and then loops again and calls biodone on the multple devices. Keep in mind that the MTTF for N drives will be roughly N times shorter. Peter -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 -- Formerly hd@world.std.com. E-mail problems? Tell hdslip@iii.net -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 -- Formerly hd@world.std.com. E-mail problems? Tell hdslip@iii.net From owner-freebsd-hackers Fri Jan 27 08:34:51 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id IAA21710 for hackers-outgoing; Fri, 27 Jan 1995 08:34:51 -0800 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id IAA21704 for ; Fri, 27 Jan 1995 08:34:48 -0800 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.8/jtpda-5.0) with SMTP id RAA05408 ; Fri, 27 Jan 1995 17:34:51 +0100 Received: by blaise.ibp.fr (4.1/SMI-4.1) id AA16418; Fri, 27 Jan 95 17:34:48 +0100 From: roberto@blaise.ibp.fr (Ollivier ROBERT) Message-Id: <9501271634.AA16418@blaise.ibp.fr> Subject: Re: wu-ftpd-2.4 under FreeBSD 1.1.5.1 To: shaun@emma.sea.uct.ac.za (Shaun Courtney) Date: Fri, 27 Jan 1995 17:34:47 +0100 (MET) Cc: hackers@freefall.cdrom.com In-Reply-To: <199501270759.JAA06836@emma.sea.uct.ac.za> from "Shaun Courtney" at Jan 27, 95 09:59:12 am X-Operating-System: FreeBSD 2.1.0-Development ctm#307 X-Mailer: ELM [version 2.4 PL23beta2] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 450 Sender: hackers-owner@FreeBSD.org Precedence: bulk > Difining HAVE_SHADOW doesn't work because ftpd.c can't find shadow.h! > Does someone have patch for this program, please email it to me or > put it up for ftp if possible. Did you remember to add -lcrypt to the libraries ? HAVE_SHADOW is for the brain-damaged SVR4 shadowing scheme not for our own. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@FreeBSD.ORG FreeBSD keltia 2.1.0-Development #18: Thu Jan 26 22:22:16 MET 1995 From owner-freebsd-hackers Fri Jan 27 08:35:23 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id IAA21743 for hackers-outgoing; Fri, 27 Jan 1995 08:35:23 -0800 Received: from mailhost.tue.nl (mailhost.tue.nl [131.155.2.5]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id IAA21737 for ; Fri, 27 Jan 1995 08:35:22 -0800 Received: from terra.stack.urc.tue.nl (terra.stack.urc.tue.nl [131.155.140.128]) by mailhost.tue.nl (8.6.9/8.6.9) with SMTP id RAA22930; Fri, 27 Jan 1995 17:34:43 +0100 Received: from skynet.stack.urc.tue.nl by terra.stack.urc.tue.nl (4.1/1.53) id AA03097; Fri, 27 Jan 95 17:34:31 +0100 Received: (erik@localhost) by skynet.stack.urc.tue.nl (8.6.9/8.6.4) id RAA08316; Fri, 27 Jan 1995 17:34:04 +0100 From: erik@stack.urc.tue.nl (Erik Manders) Message-Id: <199501271634.RAA08316@skynet.stack.urc.tue.nl> Subject: a [t]csh oddity. To: hackers@FreeBSD.org Date: Fri, 27 Jan 1995 17:34:03 +0100 (MET) Cc: marcz@stack.urc.tue.nl, unix@stack.urc.tue.nl X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1205 Sender: hackers-owner@FreeBSD.org Precedence: bulk A friend of mine was porting tcsh to 2.0R and was irritated when, after typing './tcsh' he got '-/tcsh' as process name from ps. He chased down the bug (took all afternoon) and finally traced it to csh.c. He also tried 'csh' with identical results. This is apparently a historical 'feature' since FreeBSD csh, SunOS 4.1.1 csh, SVR2 csh and tcsh all suffer the same effect. SVR4 does not, as far as we know. The diff for removing the 'feature' from csh is enclosed. Our question is: is this a deliberate feature, a bug nobody ever bothered to chase down, or something else? This assignment takes place when setting signals for an interactive shell. *** csh.c.bak Fri Jan 27 17:01:16 1995 --- csh.c Fri Jan 27 17:02:36 1995 *************** *** 448,454 **** --- 448,456 ---- shpgrp = getpgrp(); opgrp = tpgrp = -1; if (setintr) { + #ifdef WHAT_IS_THIS **argv = '-'; + #endif if (!quitit) /* Wary! */ (void) signal(SIGQUIT, SIG_IGN); (void) signal(SIGINT, pintr); Erik Manders erik@stack.urc.tue.nl -- "Any sufficiently advanced technology is indistinguishable from magic." --Arthur C. Clarke Finger me at erik@blade.stack.urc.tue.nl for my PGP public key. From owner-freebsd-hackers Fri Jan 27 08:59:38 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id IAA22209 for hackers-outgoing; Fri, 27 Jan 1995 08:59:38 -0800 Received: from foxtrot.innovus.com (foxtrot.innovus.com [192.75.186.38]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id IAA22203 for ; Fri, 27 Jan 1995 08:59:34 -0800 Message-Id: <199501271659.IAA22203@freefall.cdrom.com> Received: by foxtrot.innovus.com (1.37.109.8/16.2) id AA05050; Fri, 27 Jan 1995 12:04:00 -0500 From: Martin Renters Subject: Re: SyQuest works with FreeBSD 2.0R ! To: peter@bonkers.taronga.com (Peter da Silva) Date: Fri, 27 Jan 95 12:03:59 EST Cc: dufault@hda.com, terry@cs.weber.edu, john@pyromania.apana.org.au, hackers@FreeBSD.org In-Reply-To: <199501271358.HAA09305@bonkers.taronga.com>; from "Peter da Silva" at Jan 27, 95 7:58 am Mailer: Elm [revision: 70.85] Sender: hackers-owner@FreeBSD.org Precedence: bulk > The real solution to removable media is to put some sort of ident in the > disklabel (including time and system ID) and track that. If you have a mounted > filesystem and get a UNIT ATTENTION then you can see whether it's been > swapped or not. > > (yes, you can still defeat this with a dd to the raw device) > > What would be really cool would be to create a new pseudo-device entry when > you mount the device, and treat each volume as a separate device. Then you > could simply stall attempts to access a filesystem mounted on a device that's > been removed. Perhaps even have a hook to alert the user when they do that > to insert the appropriate volume... This is what HP does for their optical juke boxes. Except in that case a robot decides you've looked at that disk long enough and puts another one in. As an aside, don't these drives have "PREVENT MEDIA EJECT" SCSI commands to lock the disks in? Martin From owner-freebsd-hackers Fri Jan 27 09:32:53 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id JAA23067 for hackers-outgoing; Fri, 27 Jan 1995 09:32:53 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id JAA23059 for ; Fri, 27 Jan 1995 09:32:51 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA29338; Fri, 27 Jan 95 10:26:53 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9501271726.AA29338@cs.weber.edu> Subject: Re: Help with SCSI development (fwd) To: dufault@hda.com (Peter Dufault) Date: Fri, 27 Jan 95 10:26:52 MST Cc: freebsd-hackers@FreeBSD.org, vernick@cs.sunysb.edu In-Reply-To: <199501271539.KAA08510@hda.com> from "Peter Dufault" at Jan 27, 95 10:39:51 am X-Mailer: ELM [version 2.4dev PL52] Sender: hackers-owner@FreeBSD.org Precedence: bulk > Michael Vernick writes: [ ... disk striping project ... ] [ ... async I/O ... ] > > Are there any direct calls to the scsi driver from user space? I saw > > something about user calls in scsi_ioctl.c but couldn't figure out how > > to access it. If there are user level calls, are they asynchronous? There are user space SCSI calls. Check current, per Peter's recommendation. The read calls in the kernel are synchronus. The write calls are either sync or async, depending on parameters. For the most part, the async nature of the calls is *not* exposed to the user space process. Generally, this is held in the kernel as a preemption point, and the sync writes are used simply to ensure writes of file system meta-data. Both types of sync operations cause the process to be suspended while they are serviced. Many user space threading mechanisms depend on async read and write operations to provide preemption points for user space tread scheduling algorithms. The specific calls dealing with async I/O are aioread, aiowrite, aiowait, and aiocancel. This is for the SunOS 4.x LWP system and for the SVR4 and SunOS 5.x N->M mapping of user to kernel threads, where N > M. In addition, there are primitives required for stack switching and register set saving, as well as pipeline synchronization. SunOS and SVR4 provide system calls to accomplish these tasks. These facilities are not generally implemented in *BSD at this time. You may want to look into the port of the pthreads library. This will allow you to get started on a user space implementation. Providing asynchronus reads within as single thread of control within the kernel is unlikely to be portable to other than SCSI devices, and will probably require a great deal of work on the SCSI devices themselves. If you indeed plan to move this into the kernel at a later date, you may wish to consider implementing or waiting for kernel threading. Otherwise you may see speed penalties for your striping. In effect, the NFS nfsd and biod processes, which make system calls and never return, as well as the swapper and update daemons, are in effect kernel threads, albiet threads with a proc structure attached to them for no good reason. A kernel threaded implementation would not *require* a divorce of this type, but is likely to suffer greatly increased complexity if this does not occur. Kernel thread spawning is perhaps the single easiest way of forcing sync operations to act s if they were async. In simplest parlance, a kernel thread is nothing more than the kernel stack, registers, and program counter of a process. Most of the work for supporting this is, or will be, talking place for medium and fine grained SMP support, which is directly analgous to kernel multithreading, or requires it (respectively; coarse grained SMP does not require that more than one processer be allowed to execute kernel code at a time, only that there is anonymity as to which processer is actually doing the kernel code execution). I would suggest a user space implementation at this time, with an eye to the coding techniques used to do as little to prevent moving into the kernel in the future as you can. > > What I'd like to do is issue a bunch of reads (1 for each disk) to the > > controller all at once and then wait for the data to be returned. If I > > can't make asynchronous calls in user space, I guess that I could have > > multiple processes, one for each disk, where each process sends a > > synchronous read to the driver, and once all of the processes finish, > > accumulate the data. For a user space implementation, the pthreads library is an ideal way to achieve this. > > Eventually, I want to move this into the kernel. When it becomes a > > kernel level process, at what level do I issue calls. At the > > physio/bread level or lower? This is a connundrum. The problem is presented because the "slice" abstraction and therefore the per-slice device abstraction is embedded in the SCSI driver itself. This is probably a mistake, if what you want to do approaches RAID I or the Zebra FS striping techniques (I would strongly advise *against* the Zebra approach for performance reasons). This bottlenecks async reads, especially, through the device/slice abstraction. Really, you want a cleanener logical seperation of layers, and to stick at least part of your code between the layers. If you do this, please ensure that your layering is clean, so that you can impose logical device management between your layer and the underlying driver code. AIX style logical volume management has long been a goal of at least several people on these lists, myself included. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Fri Jan 27 09:51:12 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id JAA23485 for hackers-outgoing; Fri, 27 Jan 1995 09:51:12 -0800 Received: from time.cdrom.com (time.cdrom.com [192.216.223.46]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id JAA23479 for ; Fri, 27 Jan 1995 09:51:11 -0800 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.9/8.6.9) with SMTP id JAA26953; Fri, 27 Jan 1995 09:50:51 -0800 To: "Clay D. Hopperdietzel" cc: hackers@FreeBSD.org Subject: Re: >1024 cyl IDE drive In-reply-to: Your message of "Fri, 27 Jan 95 08:48:09 CST." <199501271448.IAA17392@anvil.appsmiths.com> Date: Fri, 27 Jan 1995 09:50:51 -0800 Message-ID: <26952.791229051@time.cdrom.com> From: "Jordan K. Hubbard" Sender: hackers-owner@FreeBSD.org Precedence: bulk You're saying that these bootblock-remapping drives fall over kicking when you install the boot manager? Aieee! I can't say we weren't warned about this.. Or does this not have anything to do with the boot block? Jordan > > What a pile. This thing seems to have some special *boot* code on it > to scramble BIOS' brain. >1600 cylinders. Some looney software to > write the boot-block, partition it (oh, you want 2 partitions, okay > here's 2 400MB partitions!). > > Has anybody ever made one of these goofy things work with FreeBSD, or > should I just give it a fling? Thought it might be interesting to play > with. > > I decided to give it a try, since the el-sleezo (dirt-cheep) PC sellers > are pushing these hard. If it won't work, I can easily get my money > back. The reason I took it was to see what kind of trouble they generate. > It will only be a matter of time before these things are romping the > planet and causing trouble. From owner-freebsd-hackers Fri Jan 27 10:00:56 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id KAA23624 for hackers-outgoing; Fri, 27 Jan 1995 10:00:56 -0800 Received: (from jkh@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id KAA23617 for hackers; Fri, 27 Jan 1995 10:00:56 -0800 Date: Fri, 27 Jan 1995 10:00:56 -0800 From: "Jordan K. Hubbard" Message-Id: <199501271800.KAA23617@freefall.cdrom.com> To: hackers Subject: Am I dreaming? Sender: hackers-owner@FreeBSD.org Precedence: bulk Some may have noticed in the last snapshot that I'd created some seemingly bogus symlinks of the form: lrwxrwxr-x 1 root bin 54 Jan 27 00:39 packages -> ftp://ftp.freebsd.org/pub/FreeBSD/2.0-RELEASE/packages Which are indeed bogus from the file point of view, but are at least informational and show you just where you should go to get the real file. Since the snaps are in an anon ftp area, I can't just point my symlinks off to other NFS locations due to the chroot'd nature of it all. My question is, how hard would it be to make them MORE than informational? e.g. the system sees one of these URL specs as a filename and auto-fetches it for you. I guess this all gets back to the whole `user mode translation of file names' thing we were talking about awhile back. It's not the same as portals, which require a given mount point to be traversed, but rather affects all files who's names match some sort of selection criteria. The feature above would be one very nice application for this. Any comments? Am I, as the subject says, simply dreaming? Jordan From owner-freebsd-hackers Fri Jan 27 10:03:37 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id KAA23669 for hackers-outgoing; Fri, 27 Jan 1995 10:03:37 -0800 Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id KAA23647; Fri, 27 Jan 1995 10:02:51 -0800 Received: from localhost (localhost [127.0.0.1]) by grunt.grondar.za (8.6.9/8.6.9) with SMTP id UAA10232; Fri, 27 Jan 1995 20:00:58 +0200 Message-Id: <199501271800.UAA10232@grunt.grondar.za> X-Authentication-Warning: grunt.grondar.za: Host localhost didn't use HELO protocol To: rkw@dataplex.net (Richard Wackerbarth) cc: hackers@FreeBSD.org, freebsd-current@freefall.cdrom.com, mark@grunt.grondar.za Subject: Re: REMAKE WORLD Date: Fri, 27 Jan 1995 20:00:58 +0200 From: Mark Murray Sender: hackers-owner@FreeBSD.org Precedence: bulk > OK, guys! I'm on the "make" and I'm 'gonna take on the world. As long as you realise this takes 7 days, I think you have a good thing... > The warts on the makefile system have gotten out of control. It is time to > throw out the old nag and get a fresh horse. > > I've "talked" to Jordan and we agree that this is a "good idea(tm)." > > Nothing is sacred. :-) In the beginning... > The plan: > 1) Determine design goals : : > So much for starters. What other ideas do you want to throw in? In the ports tree, (I know this is a little detail, but let's sow the seed now) lets make some kind of cookie that shows whether a port is installed. (Sort-of-like-a /var/installed/less-) that other port builds can use. > 7. I know that we are not NetBSD but ... Multi-platform cross compiling is > close enough to a fall-out that I think we should include the mechanism for > it. Of course. Lets work towards "grand unification"! > 8. For those of us who build "sup -current" trees, the ability to post a > "forget this program" lock which will allow a virtual delete of targets > that do not properly build without altering the Makefiles. Something like an "anti-build-cookie"? M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 From owner-freebsd-hackers Fri Jan 27 10:14:22 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id KAA23872 for hackers-outgoing; Fri, 27 Jan 1995 10:14:22 -0800 Received: from seagull.rtd.com (root@Seagull.rtd.com [198.102.68.2]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id KAA23863 for ; Fri, 27 Jan 1995 10:14:16 -0800 Received: (from dgy@localhost) by seagull.rtd.com (8.6.9/8.6.9.1) id LAA21622 for freebsd-hackers@freefall.cdrom.com; Fri, 27 Jan 1995 11:14:07 -0700 From: Don Yuniskis Message-Id: <199501271814.LAA21622@seagull.rtd.com> Subject: shell trick? To: freebsd-hackers@freefall.cdrom.com (FreeBSD hackers) Date: Fri, 27 Jan 1995 11:14:06 -0700 (MST) X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 286 Sender: hackers-owner@FreeBSD.org Precedence: bulk Greetings! I'm sure this isn't the *best* place to post this, but, since it pertains to some FreeBSD hacking I'm doing... How can I, in a shell script, read lines from a file, expand any environment variables referenced therein and write results to another file? Thx, --don From owner-freebsd-hackers Fri Jan 27 10:22:23 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id KAA23986 for hackers-outgoing; Fri, 27 Jan 1995 10:22:23 -0800 Received: from lupine.nsi.nasa.gov (lupine.nsi.nasa.gov [198.116.2.100]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id KAA23980 for ; Fri, 27 Jan 1995 10:22:19 -0800 Received: (from mnewell@localhost) by lupine.nsi.nasa.gov (8.6.9/8.6.9) id NAA08093; Fri, 27 Jan 1995 13:21:06 -0500 Date: Fri, 27 Jan 1995 13:21:02 -0500 (EST) From: "Michael C. Newell" To: Erik Manders cc: hackers@FreeBSD.org, marcz@stack.urc.tue.nl, unix@stack.urc.tue.nl Subject: Re: a [t]csh oddity. In-Reply-To: <199501271634.RAA08316@skynet.stack.urc.tue.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hackers-owner@FreeBSD.org Precedence: bulk On Fri, 27 Jan 1995, Erik Manders wrote: > Our question is: is this a deliberate feature, a bug nobody ever > bothered to chase down, or something else? This assignment takes > place when setting signals for an interactive shell. I believe this is intentional; at least the Sun man pages for csh call out its special interpretation: Initialization and Termination When first started, the C shell normally performs commands from the .cshrc file in your home directory, provided that it is readable and you either own it or your real group ID matches its group ID. If the shell is invoked with a name that starts with `-', as when started by login(1), the shell runs as a login shell. In this case, after executing com- mands from the .cshrc file, the shell executes commands from the .login file in your home directory; the same permission checks as those for .cshrc are applied to this file. Typi- cally, the .login file contains commands to specify the ter- minal type and environment. Changing the "./" to "-/" does seem odd, though... Mike +--------------------------------------+------------------------------------+ |Mike Newell | The opinions expressed herein are | |NASA Science Internet Network Systems | my own, and do not necessarily | |Sterling Software, Inc. | reflect those of the NSI program, | |MNewell@nsipo.nasa.gov | Sterling Software, NASA, or anyone | |+1-202-434-8954 | else. | +--------------------------------------+------------------------------------+ From owner-freebsd-hackers Fri Jan 27 10:33:14 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id KAA24125 for hackers-outgoing; Fri, 27 Jan 1995 10:33:14 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id KAA24115; Fri, 27 Jan 1995 10:33:06 -0800 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id KAA03723; Fri, 27 Jan 1995 10:31:13 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.9/8.6.5) with SMTP id KAA00443; Fri, 27 Jan 1995 10:31:13 -0800 Message-Id: <199501271831.KAA00443@corbin.Root.COM> X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol To: "Jordan K. Hubbard" cc: hackers@freefall.cdrom.com Subject: Re: Am I dreaming? In-reply-to: Your message of "Fri, 27 Jan 95 10:00:56 PST." <199501271800.KAA23617@freefall.cdrom.com> From: David Greenman Reply-To: davidg@Root.COM Date: Fri, 27 Jan 1995 10:31:13 -0800 Sender: hackers-owner@FreeBSD.org Precedence: bulk >Any comments? Am I, as the subject says, simply dreaming? You're dreaming a nightmare. -DG From owner-freebsd-hackers Fri Jan 27 11:27:30 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id LAA25289 for hackers-outgoing; Fri, 27 Jan 1995 11:27:30 -0800 Received: from tfs.com (mailhub.tfs.com [140.145.250.1]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id LAA25283 for ; Fri, 27 Jan 1995 11:27:29 -0800 Received: by tfs.com (smail3.1.28.1) Message-Id: From: julian@tfs.com (Julian Elischer) Subject: Re: SyQuest works with FreeBSD 2.0R ! To: peter@bonkers.taronga.com (Peter da Silva) Date: Fri, 27 Jan 1995 11:26:34 -0800 (PST) Cc: dufault@hda.com, terry@cs.weber.edu, john@pyromania.apana.org.au, hackers@FreeBSD.org In-Reply-To: <199501271358.HAA09305@bonkers.taronga.com> from "Peter da Silva" at Jan 27, 95 07:58:08 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1018 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > The real solution to removable media is to put some sort of ident in the > disklabel (including time and system ID) and track that. If you have a mounted > filesystem and get a UNIT ATTENTION then you can see whether it's been > swapped or not. > At the moment, a unit-attention invalidates all accesses, until all have been closed. (the device becomes 'locked'. when the reference count has gone down to 0, the lock is released.. > (yes, you can still defeat this with a dd to the raw device) not at the moment..... > > What would be really cool would be to create a new pseudo-device entry when > you mount the device, and treat each volume as a separate device. Then you > could simply stall attempts to access a filesystem mounted on a device that's > been removed. Perhaps even have a hook to alert the user when they do that > to insert the appropriate volume... and send messages to the operator to mount volume "xxx"? hmm sounds a bit like a certain large blue coloured machine I remember once.. > From owner-freebsd-hackers Fri Jan 27 11:33:08 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id LAA25471 for hackers-outgoing; Fri, 27 Jan 1995 11:33:08 -0800 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id LAA25461 for ; Fri, 27 Jan 1995 11:33:01 -0800 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.8/jtpda-5.0) with SMTP id UAA07246 ; Fri, 27 Jan 1995 20:34:15 +0100 Received: by blaise.ibp.fr (4.1/SMI-4.1) id AA17198; Fri, 27 Jan 95 20:34:11 +0100 From: roberto@blaise.ibp.fr (Ollivier ROBERT) Message-Id: <9501271934.AA17198@blaise.ibp.fr> Subject: Re: shell trick? To: dgy@seagull.rtd.com (Don Yuniskis) Date: Fri, 27 Jan 1995 20:34:11 +0100 (MET) Cc: freebsd-hackers@freefall.cdrom.com In-Reply-To: <199501271814.LAA21622@seagull.rtd.com> from "Don Yuniskis" at Jan 27, 95 11:14:06 am X-Operating-System: FreeBSD 2.1.0-Development ctm#307 X-Mailer: ELM [version 2.4 PL23beta2] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1100 Sender: hackers-owner@FreeBSD.org Precedence: bulk > How can I, in a shell script, read lines from a file, expand any > environment variables referenced therein and write results to another > file? This not a real answer but you should really do this kind of things in perl... Its build-in eval function is great for this. You can create variables on the fly with new names, and so on. For example I read my new account configuration file and create variables named $conf_ with that : sub read_config_file { open (CONFIG, "$config") || die "Can't open $config.\n"; LOOP: while () { next if (/^#/o); # ignore comments next if (/^$/o); # ignore blank lines next if (/^[ \t]*$/o); # ignore lines with blanks and/or tabs chop; m#^([a-z0-9_]*)\s*=\s*(.+)$#; eval "\$conf_$1 = \"$2\";"; } } if the configuration file has : def_shell = /bin/tcsh then $conf_def_shell will have "/bin/tcsh" as value. Neat. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@FreeBSD.ORG FreeBSD keltia 2.1.0-Development #18: Thu Jan 26 22:22:16 MET 1995 From owner-freebsd-hackers Fri Jan 27 11:37:18 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id LAA25562 for hackers-outgoing; Fri, 27 Jan 1995 11:37:18 -0800 Received: (from dima@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id LAA25553; Fri, 27 Jan 1995 11:37:17 -0800 Message-Id: <199501271937.LAA25553@freefall.cdrom.com> Subject: Re: '.' in user name To: davide.tome'@galactica.it Date: Fri, 27 Jan 1995 11:37:17 -0800 (PST) Cc: hackers@FreeBSD.org In-Reply-To: <8A262CE.00010088AA.uuout@galactica.it> from "DAVIDE TOME'" at Jan 27, 95 11:58:00 am From: dima@FreeBSD.org (Dima Ruban) X-Class: Fast Organization: HackerDome X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 719 Sender: hackers-owner@FreeBSD.org Precedence: bulk DAVIDE TOME' writes: > > Hi, > > > I need to have users names with '.' character .... like You can't. On kerberos machine I can login as dima.root (If I have loginname dima) for example. (or something like that) > > > pippo.pluto > > > How can I do it ??? > > > Ciao > > Davide > > Dott. Davide Tome' > ------------------------------------------------- > Internet .....: davide.tome'@galactica.it > Fido..........: 2:331/358 davide tome' > Galactica BBS.: +39-2-29006058 (24H 24 lines r.a) > Voce..........: +39-2-29006150 > Fax...........: +39-2-29006153 > ------------------------------------------------- > -- dima From owner-freebsd-hackers Fri Jan 27 11:54:49 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id LAA25939 for hackers-outgoing; Fri, 27 Jan 1995 11:54:49 -0800 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id LAA25933 for ; Fri, 27 Jan 1995 11:54:47 -0800 Received: by halloran-eldar.lcs.mit.edu; id AA12060; Fri, 27 Jan 1995 14:54:38 -0500 Date: Fri, 27 Jan 1995 14:54:38 -0500 From: Garrett Wollman Message-Id: <9501271954.AA12060@halloran-eldar.lcs.mit.edu> To: Peter Dufault Cc: freebsd-hackers@FreeBSD.org Subject: Re: Help with SCSI development (fwd) In-Reply-To: <199501271539.KAA08510@hda.com> References: <199501271539.KAA08510@hda.com> Sender: hackers-owner@FreeBSD.org Precedence: bulk < said: >> I'm planning to write software using Freebsd that will allow files to >> be striped over multiple disks. There is already software in 4.4-Lite which is designed specifically for this purpose, although it is named badly and probably would take a bit of porting work to get it up to speed. See /sys/dev/cd.c in a convenient 4.4-Lite tree. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-hackers Fri Jan 27 11:59:31 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id LAA26020 for hackers-outgoing; Fri, 27 Jan 1995 11:59:31 -0800 Received: from gateway.cybernet.com (gateway.cybernet.com [192.245.33.1]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id LAA26009 for ; Fri, 27 Jan 1995 11:59:13 -0800 Received: from [192.245.33.12] by gateway.cybernet.com (8.6.8/1.0A) id PAA12868; Fri, 27 Jan 1995 15:22:19 -0500 X-Sender: mtaylor@gateway.cybernet.com Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 27 Jan 1995 15:08:14 -0500 To: kuku@gilberto.physik.rwth-aachen.de From: mtaylor@gateway.cybernet.com (Mark J. Taylor) Subject: Re: Joystick driver available Cc: hackers@FreeBSD.org Sender: hackers-owner@FreeBSD.org Precedence: bulk >> >> Hi fellow gamers! >> >> I have uploaded a joystick driver at ftp.cdrom.com: >> /pub/FreeBSD/incoming/joystick.tar.gz > >Thinking of possible applications (other than games) of a joy stick: > >Input device for X11. > >Does anyone know how to make X see it? > > We (Cybernet Systems) actually implemented a driver, the MultiMouse, which looks like a MouseSystems mouse to FreeBSD/XFree86, but it is actually talking over a socket to our mouse driver, which takes multiple input channels and converts them to 2-byte deltas and left-middle-right buttons of a MouseSystems mouse. Originally, we wrote it to support a touchscreen simultaneously with a mouse under XFree86 (the system we wrote it for does not usually have a real mouse), and since then it has grown to support a socket-based protocol which we call the Motion Platform Communications (MPC) protocol, as well as Microsoft Mice (in addition to the MouseSystems Mouse support). The Microsoft Mouse addition took all of 2 hours to add to the server. I suspect that adding a joystick to it would be just as easy. I would need to add 1) a parser for the joystick entry in the configuration file, 2) a setup routine, 3) a routine which passes the deltas and buttons back. I won't post another message to this group regarding this product, unless prompted to. Sorry about this "commercial" message. If anyone has any comments, questions, etc., email me. I will respond privately. If there are concerns about source code availability, please email me and we'll talk... -Mark Taylor Cybernet Systems mtaylor@cybernet.com From owner-freebsd-hackers Fri Jan 27 12:02:52 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id MAA26098 for hackers-outgoing; Fri, 27 Jan 1995 12:02:52 -0800 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id MAA26091 for ; Fri, 27 Jan 1995 12:02:45 -0800 Received: by halloran-eldar.lcs.mit.edu; id AA12096; Fri, 27 Jan 1995 15:01:25 -0500 Date: Fri, 27 Jan 1995 15:01:25 -0500 From: Garrett Wollman Message-Id: <9501272001.AA12096@halloran-eldar.lcs.mit.edu> To: terry@cs.weber.edu (Terry Lambert) Cc: freebsd-hackers@FreeBSD.org Subject: Re: Help with SCSI development (fwd) In-Reply-To: <9501271726.AA29338@cs.weber.edu> References: <199501271539.KAA08510@hda.com> <9501271726.AA29338@cs.weber.edu> Sender: hackers-owner@FreeBSD.org Precedence: bulk < In effect, the NFS nfsd and biod processes, which make system calls and > never return, as well as the swapper and update daemons, are in effect > kernel threads, albiet threads with a proc structure attached to them > for no good reason. UTSL. `nfssvc' does return for `nfsd' to perform authentication. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-hackers Fri Jan 27 12:12:17 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id MAA26272 for hackers-outgoing; Fri, 27 Jan 1995 12:12:17 -0800 Received: from tfs.com (mailhub.tfs.com [140.145.250.1]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id MAA26218; Fri, 27 Jan 1995 12:09:51 -0800 Received: by tfs.com (smail3.1.28.1) Message-Id: From: julian@tfs.com (Julian Elischer) Subject: SCSI device configuring.. (was scsi renames devices) To: dufault@hda.com (Peter Dufault) Date: Fri, 27 Jan 1995 12:08:58 -0800 (PST) Cc: hsu@fx7.cs.hut.fi, freebsd-hackers@freefall.cdrom.com, freebsd-scsi@freefall.cdrom.com In-Reply-To: <199501261406.JAA04537@hda.com> from "Peter Dufault" at Jan 26, 95 09:06:56 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 7086 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > Heikki Suonsivu writes: > > > > > > >Number: 189 > > >Category: kern > > >Synopsis: sd renames disks > > >Confidential: no > > >Severity: serious > (...) > > > > sd thinks it is smarter than you on id's you want your disks have. Install > > three disks, sd1a is /tmp and sd2a is users. Guess what happens if sd1 > > breaks down, controller misses it by the phase of the moon, or you forget > > to power it up if it is in an external box. > > > > I wouldn't be happy about editing fstab every time disk configuration changes, > > but that is a minor problem compared to potential dangers this brings us. > > > > (I already complained, but maybe it is a good idea to gnats it so that it > > won't be forgotten) > > > > >How-To-Repeat: > > > This came about because there was no way to specify a target and LUN in the config.. if you looked in the original SCSI stuff, there was support for nailing down a particular device to a particular address. however it required editing a file.. (scsiconf.c .. look for the word "predefined") The following comment from the file describes it: /* * The structure of pre-configured devices that might be turned * off and therefore may not show up */ It was a hack then and it still is.. there are several ways around the problem.. 1/ The NetBSD approach.. NetBSD have changed their config code almost entirely, to use the same system as (I believe) BSDI.. wherever it came from, it allows the scsi-IDs to be defined into the kernel.. it first assigns all the fixed units that you have defined and then moves onto the variable scheme for any extra devices. 2/ the /DEVFS approach.. the kernel creates the devices purely as it finds them and assignes names that are descriptive of WHERE it found them. Needs devfs, and I've just scrapped my 3rd try at it.. 3/ the /dev/scsi approach (aka the 'Peter (dufault) Principle' :) looks promising but unfortunatly, doesn't allow vnode locking between (say) /dev/rsd0d and /dev/scsi/dev3-lun0-part4 (for want of a better name). because they are different vnodes.. > Some of this is present in sys/scsi/su.c, but there are a few things > that have to be decided before it is complete. > > For example, ID 3 is a fujitsu drive: > > > hda.com# ls -lt /dev/rsd2d > > crw-r----- 1 root operator 13, 19 Sep 26 00:01 /dev/rsd2d > > hda.com# > > hda.com# scsi -f /dev/rsd2d -c "12 0 0 0 64 0" -i 64 "s8 z8 z16" > > FUJITSU M2654S-512 (neat!) > > and I can access it through a fixed device with the SCSI ID > embedded in the minor number (no, the man page isn't > checked in on how the minor number format): > > > hda.com# mknod /dev/scsi/id3 c 18 458755 > > hda.com# scsi -f /dev/scsi/id3 -c "12 0 0 0 64 0" -i 64 "s8 z8 z16" > FUJITSU M2654S-512 > yeah I read your code... sneaky.... > > hda.com# mknod /dev/scsi/sd/rsd3 c 18 458758 > > hda.com# mknod /dev/scsi/sd/sd3 b 18 458758 major 18 for both blk and char? > > hda.com# fsck -n /dev/scsi/sd/rsd3 > > ** /dev/scsi/sd/rsd3 (NO WRITE) > > ** Last Mounted on /mnt2 > > ** Phase 1 - Check Blocks and Sizes > > ^Chda.com# > > However, this does it through the minor numbers and not config. > > If you look in scsi/su.c (an unfortunate name that should be changed to > fx.c for "fixed devices" before 2.1) well, things change.. I'm not sure about fx.. (hmm we need a better name.. dscsi? (direct scsi) or ds? or ....? > you'll see that you can go from > (BUS,ID,LUN) to > underlying device, so if config is modified to build up a mapping > table then you are almost done. > > However, we have to consider the problem of booting an old kernel > and having the same problem Heikki mentions, namely, the new sd0 > is scsi id3 or something and we mount on top of it and trash the > disk. how many really old kernels do people run? particularly after a revision upgrade? > > The same problem exists with the multiple host adapters: Currently > they are "counting" host adapters also, and adding a host adapter > with a disk will potentially trash your system. > we could assign scsi-bus numbers to specific devices same as Net BSD assigns devices to TARG.. e.g. bus scbus0 at bt0 bus scbus1 at bt1 bus scbus2 at aha0 > Some thoughts: > > 1. Keep the current "auto counting" devices exactly as they are. auto counting is really good for many cases.. particularly when first setting up the system, and we don't know what's going to be where..... (or for quickly adding a new drive that we didn't know we were going to get,) etc. > 2. Add "config'd" devices as a new facility, almost > as Garrett proposed once before except they need new names: > > controller scbus0 at aha0 > controller scbus1 at ncr0 yes! but if we leave these out, it get's 'auto-added' (as in NetBSD) > disk ssd0 at scbus0 target 0 unit 0 > disk ssd1 at scbus1 target 0 unit 0 ah-ha! yes.. looks good, now how do we impliment it? > tape sst0 at scbus0 target 5 > device sch0 at scbus1 target 4 > disk scd0 at scbus1 target 5 and as netBSD have..... disk ssd0 at scbus ? target ? lun ? remember we may find more devices than those preconfigured.. Might I also add the following suggestion.. under OSF/1 on the PC. the boot code, has been modified to load 2 files, rather than just the kernel.. it loads a kernel, yes, but it also loads a configuration file. the configuration file is an ascii text file, that contains such things as MAXUSERs etc... I don't see why we couldn't do similar.. that way we could have file called /config with: > controller scbus0 at aha0 > controller scbus1 at ncr0 > disk ssd0 at scbus0 target 0 unit 0 > disk ssd1 at scbus1 target 0 unit 0 > tape sst0 at scbus0 target 5 > device sch0 at scbus1 target 4 > disk scd0 at scbus1 target 5 (or something similar) if the other file doesn't exist, the scsi code could just default to autocounting.. that way the kernel wouldn't need to know in advance about such things.... sort of the best of both worlds, and if we could make the kernel dump out it's config (lsdev?) in teh same format, then we could freeze a config by simply doing scsi -r (reprobe scsi bus for new devices) lsdev -c >/config > > These have to be new devconf entries to avoid the "reboot old kernel > and trash your system" problem, and can have new device entry points > such as /dev/scsi/sd and so on. not sure what you mean by this > > This will mean there will be three ways to get at a single scsi device: > > 1. Current "auto counting" devices; > 2. Current "fixed" devices with target embedded in the minor number > 3. Completely new conf'd devices. sure.. > > Any thoughts? yep, see above.. > > +----------------------------------+ ______ _ __ | __--_|\ Julian Elischer | \ U \/ / On assignment | / \ julian@tfs.com +------>x USA \ in a very strange | ( OZ ) 300 lakeside Dr. oakland CA. \___ ___ | country ! +- X_.---._/ USA+(510) 645-3137(wk) \_/ \\ v From owner-freebsd-hackers Fri Jan 27 12:13:04 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id MAA26299 for hackers-outgoing; Fri, 27 Jan 1995 12:13:04 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id MAA26293 for ; Fri, 27 Jan 1995 12:13:01 -0800 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id MAA07301; Fri, 27 Jan 1995 12:12:47 -0800 From: Poul-Henning Kamp Message-Id: <199501272012.MAA07301@ref.tfs.com> Subject: Re: Help with SCSI development (fwd) To: wollman@halloran-eldar.lcs.mit.edu (Garrett Wollman) Date: Fri, 27 Jan 1995 12:12:46 -0800 (PST) Cc: dufault@hda.com, freebsd-hackers@FreeBSD.org In-Reply-To: <9501271954.AA12060@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at Jan 27, 95 02:54:38 pm Content-Type: text Content-Length: 584 Sender: hackers-owner@FreeBSD.org Precedence: bulk > >> I'm planning to write software using Freebsd that will allow files to > >> be striped over multiple disks. > > There is already software in 4.4-Lite which is designed specifically > for this purpose, although it is named badly and probably would take a > bit of porting work to get it up to speed. See /sys/dev/cd.c in a > convenient 4.4-Lite tree. That stuff is a hack. I agree with Terry, this should be done "The Right Way". -- Poul-Henning Kamp TRW Financial Systems, Inc. FreeBSD has, until now, not one single time had an undetected error. :-) From owner-freebsd-hackers Fri Jan 27 12:26:02 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id MAA26445 for hackers-outgoing; Fri, 27 Jan 1995 12:26:02 -0800 Received: from arch.kiae.su (arch.kiae.su [144.206.136.10]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id MAA26439 for ; Fri, 27 Jan 1995 12:25:46 -0800 Received: from localhost by arch.kiae.su id XAA05279; (8.6.5/vak/1.8r) Fri, 27 Jan 1995 23:25:06 +0300 To: hackers@FreeBSD.org Message-ID: Organization: KIAE Archive Center Date: Fri, 27 Jan 1995 23:25:06 +0300 X-Mailer: Mail/@ [v2.16 SunOS] From: vak@cronyx.ru Subject: [patch 2.0R] wd.c: 32-bit mode added Lines: 169 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 5536 Sender: hackers-owner@FreeBSD.org Precedence: bulk Hi, Did anybode there ever try a VLBus IDE adapter? Theu are so cheap ($18), that I decided to buy a one. I tested it under MSDOS and FreeBSD on 486DX2/66, using the disk Caviar WDC AC2420H, and here are the results: IDE VLB IDE ISA ------------------------------------------------ DOS: Checkit 1205 847 DOS: Sysinfo 1556 1089 FreeBSD: Iozone 1675 1143 All numbers are measured in kilobytes per second. IDE ISA is a standard milti-i/o card. Under MSDOS for IDE VLB was used the special driver HTIDE, delivered with the board. Under FreeBSD was used the wd driver with 32-bit mode patch applied. Iozone parameters were: filesize = 8 megabytes, blocksize = 4096 bytes (there were 6 Meg of RAM on the test machine). It seems that VLB IDE is quite useful: 50% disk speed increase. This patch adds 32-bit i/o mode to wd driver. Regards, Serge --- wd20.c Fri Nov 18 14:27:41 1994 +++ wd.c Fri Jan 27 22:48:50 1995 @@ -218,6 +218,7 @@ #define DKFL_BADSECT 0x00020 /* has a bad144 badsector table */ #define DKFL_WRITEPROT 0x00040 /* manual unit write protect */ #define DKFL_LABELLING 0x00080 /* readdisklabel() in progress */ +#define DKFL_32BIT 0x00100 /* use 32-bit i/o mode */ struct wdparams dk_params; /* ESDI/IDE drive/controller parameters */ int dk_dkunit; /* number of statistics purposes */ struct disklabel dk_dd; /* device configuration data */ @@ -397,14 +398,17 @@ char buf[sizeof(du->dk_params.wdp_model) + 1]; bcopy(du->dk_params.wdp_model, buf, sizeof(buf)-1); buf[sizeof(buf)-1] = '\0'; - printf("wdc%d: unit %d (wd%d): <%s>\n", + printf("wdc%d: unit %d (wd%d): <%s>", dvp->id_unit, unit, lunit, buf); + if (du->dk_flags & DKFL_32BIT) + printf(", 32-bit data path"); + printf("\n"); if (du->dk_params.wdp_heads == 0 && du->dk_dd.d_secperunit > 100) - printf("wd%d: size unknown, using BIOS values\n", + printf("wd%d: size unknown, using BIOS values: ", lunit); else if (du->dk_params.wdp_heads == 0) - printf("wd%d: size unknown\n", lunit); + printf("wd%d: size unknown: ", lunit); else printf("wd%d: %luMB (%lu total sec), ", lunit, @@ -759,9 +763,14 @@ } /* then send it! */ - outsw(du->dk_port + wd_data, - (void *)((int)bp->b_un.b_addr + du->dk_skip * DEV_BSIZE), - DEV_BSIZE / sizeof(short)); + if (du->dk_flags & DKFL_32BIT) + outsl(du->dk_port + wd_data, + (void *)((int)bp->b_un.b_addr + du->dk_skip * DEV_BSIZE), + DEV_BSIZE / sizeof(long)); + else + outsw(du->dk_port + wd_data, + (void *)((int)bp->b_un.b_addr + du->dk_skip * DEV_BSIZE), + DEV_BSIZE / sizeof(short)); du->dk_bc -= DEV_BSIZE; } @@ -844,10 +853,6 @@ */ if (((bp->b_flags & (B_READ | B_ERROR)) == B_READ) && wdtab[unit].b_active) { - int chk, dummy; - - chk = min(DEV_BSIZE / sizeof(short), du->dk_bc / sizeof(short)); - /* ready to receive data? */ if ((du->dk_status & (WDCS_READY | WDCS_SEEKCMPLT | WDCS_DRQ)) != (WDCS_READY | WDCS_SEEKCMPLT | WDCS_DRQ)) @@ -858,14 +863,15 @@ } /* suck in data */ - insw(du->dk_port + wd_data, - (void *)((int)bp->b_un.b_addr + du->dk_skip * DEV_BSIZE), - chk); - du->dk_bc -= chk * sizeof(short); - - /* XXX for obsolete fractional sector reads. */ - while (chk++ < DEV_BSIZE / sizeof(short)) - insw(du->dk_port + wd_data, &dummy, 1); + if (du->dk_flags & DKFL_32BIT) + insl(du->dk_port + wd_data, + bp->b_un.b_addr + du->dk_skip * DEV_BSIZE, + DEV_BSIZE / sizeof(long)); + else + insw(du->dk_port + wd_data, + bp->b_un.b_addr + du->dk_skip * DEV_BSIZE, + DEV_BSIZE / sizeof(short)); + du->dk_bc -= DEV_BSIZE; } wdxfer[du->dk_lunit]++; @@ -1247,9 +1253,9 @@ wdgetctlr(struct disk *du) { int i; - char tb[DEV_BSIZE]; + char tb[DEV_BSIZE], tb2[DEV_BSIZE]; struct wdparams *wp; - +again: if (wdcommand(du, 0, 0, 0, 0, WDCC_READP) != 0 || wdwait(du, WDCS_READY | WDCS_SEEKCMPLT | WDCS_DRQ, TIMEOUT) != 0) { /* XXX need to check error status after final transfer. */ @@ -1328,7 +1334,25 @@ /* obtain parameters */ wp = &du->dk_params; - insw(du->dk_port + wd_data, tb, sizeof(tb) / sizeof(short)); + if (du->dk_flags & DKFL_32BIT) + insl(du->dk_port + wd_data, tb, sizeof(tb) / sizeof(long)); + else + insw(du->dk_port + wd_data, tb, sizeof(tb) / sizeof(short)); + + /* try 32-bit data path (VLB IDE controller) */ + if (! (du->dk_flags & DKFL_32BIT)) { + bcopy(tb, tb2, sizeof(struct wdparams)); + du->dk_flags |= DKFL_32BIT; + goto again; + } + + /* check that we really have 32-bit controller */ + if (bcmp (tb, tb2, sizeof(struct wdparams)) != 0) { + /* test failed, use 16-bit i/o mode */ + bcopy(tb2, tb, sizeof(struct wdparams)); + du->dk_flags &= ~DKFL_32BIT; + } + bcopy(tb, wp, sizeof(struct wdparams)); /* shuffle string byte order */ @@ -1745,9 +1769,14 @@ "wddump: timeout waiting for DRQ"); return (EIO); } - outsw(du->dk_port + wd_data, - CADDR1 + ((int)addr & (NBPG - 1)), - DEV_BSIZE / sizeof(short)); + if (du->dk_flags & DKFL_32BIT) + outsl(du->dk_port + wd_data, + CADDR1 + ((int)addr & (NBPG - 1)), + DEV_BSIZE / sizeof(long)); + else + outsw(du->dk_port + wd_data, + CADDR1 + ((int)addr & (NBPG - 1)), + DEV_BSIZE / sizeof(short)); addr += DEV_BSIZE; if ((unsigned)addr % (1024 * 1024) == 0) printf("%ld ", num / (1024 * 1024 / DEV_BSIZE)); From owner-freebsd-hackers Fri Jan 27 12:28:11 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id MAA26496 for hackers-outgoing; Fri, 27 Jan 1995 12:28:11 -0800 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id MAA26490; Fri, 27 Jan 1995 12:28:08 -0800 Received: by halloran-eldar.lcs.mit.edu; id AA12182; Fri, 27 Jan 1995 15:28:01 -0500 Date: Fri, 27 Jan 1995 15:28:01 -0500 From: Garrett Wollman Message-Id: <9501272028.AA12182@halloran-eldar.lcs.mit.edu> To: "Jordan K. Hubbard" Cc: hackers@freefall.cdrom.com Subject: Am I dreaming? In-Reply-To: <199501271800.KAA23617@freefall.cdrom.com> References: <199501271800.KAA23617@freefall.cdrom.com> Sender: hackers-owner@FreeBSD.org Precedence: bulk < said: > I guess this all gets back to the whole `user mode translation of file names' > thing we were talking about awhile back. It's not the same as portals, > which require a given mount point to be traversed, but rather affects all > files who's names match some sort of selection criteria. The feature above > would be one very nice application for this. Gross! That's even more evil than variant symbolic links! -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-hackers Fri Jan 27 12:43:40 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id MAA27152 for hackers-outgoing; Fri, 27 Jan 1995 12:43:40 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id MAA27146; Fri, 27 Jan 1995 12:43:36 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA00201; Fri, 27 Jan 95 13:36:13 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9501272036.AA00201@cs.weber.edu> Subject: Re: >1024 cyl IDE drive To: jkh@FreeBSD.org (Jordan K. Hubbard) Date: Fri, 27 Jan 95 13:36:12 MST Cc: hoppy@appsmiths.com, hackers@FreeBSD.org In-Reply-To: <26952.791229051@time.cdrom.com> from "Jordan K. Hubbard" at Jan 27, 95 09:50:51 am X-Mailer: ELM [version 2.4dev PL52] Sender: hackers-owner@FreeBSD.org Precedence: bulk > > You're saying that these bootblock-remapping drives fall over kicking > when you install the boot manager? Aieee! I can't say we weren't warned > about this.. Or does this not have anything to do with the boot block? I have the email addr of someone at OnTrack who actually wrote their boot code that they install -- and it does this. More information as talks progress. I told you so. Being right about it doesn't make it suck less. 8-(. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Fri Jan 27 12:52:38 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id MAA27230 for hackers-outgoing; Fri, 27 Jan 1995 12:52:38 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id MAA27224 for ; Fri, 27 Jan 1995 12:52:37 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA00266; Fri, 27 Jan 95 13:46:18 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9501272046.AA00266@cs.weber.edu> Subject: Re: SyQuest works with FreeBSD 2.0R ! To: dufault@hda.com (Peter Dufault) Date: Fri, 27 Jan 95 13:46:18 MST Cc: john@pyromania.apana.org.au, hackers@FreeBSD.org In-Reply-To: <199501271150.GAA07921@hda.com> from "Peter Dufault" at Jan 27, 95 06:50:47 am X-Mailer: ELM [version 2.4dev PL52] Sender: hackers-owner@FreeBSD.org Precedence: bulk > > You need to be careful if you have more than one drive that you only use > > a single disk in a single drive for a system boot instance, since the > > OS (incorrectly) uses the device as part of the ident, and can get > > confused if you switch drives. > > I don't follow this. Is this a FreeBSD problem? It depends. 2.0R was specifically referenced. Current may not have that problem. [ ... ] > Actually, I think he will have a problem - UNIT ATTENTION is > generated when the removable drive is changed. 2.0R doesn't retry > at all on this, and 2.0-current will retry > but not for removable drives because of the chance of someone swapping a > mounted drive. This should never happen; the device should be locked during reference so that you can't remove the media. Most removable SCSI devices support this, as long as they are not manual eject. I think we are screwed on floppies unless we get media change notification. > > Also dual Bernoulli's and dual Syquest use LUNs on a single target to > > get two devices. Some of the SCSI drivers are "uncomfortable" with LUNs. > > I would suggest seperate drives at this time. > > Which drivers are uncomforable with LUNS? They shouldn't be too hard to > fix. We need some pioneers... I think that the sound-baster drivers fall into the "uncomfortable" category. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Fri Jan 27 12:56:22 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id MAA27286 for hackers-outgoing; Fri, 27 Jan 1995 12:56:22 -0800 Received: from time.cdrom.com (time.cdrom.com [192.216.223.46]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id MAA27280 for ; Fri, 27 Jan 1995 12:56:21 -0800 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.9/8.6.9) with SMTP id MAA03197; Fri, 27 Jan 1995 12:56:07 -0800 To: Garrett Wollman cc: hackers@freefall.cdrom.com Subject: Re: Am I dreaming? In-reply-to: Your message of "Fri, 27 Jan 95 15:28:01 EST." <9501272028.AA12182@halloran-eldar.lcs.mit.edu> Date: Fri, 27 Jan 1995 12:56:06 -0800 Message-ID: <3196.791240166@time.cdrom.com> From: "Jordan K. Hubbard" Sender: hackers-owner@FreeBSD.org Precedence: bulk >> I guess this all gets back to the whole `user mode translation of file names' >> thing we were talking about awhile back. It's not the same as portals, >> which require a given mount point to be traversed, but rather affects all >> files who's names match some sort of selection criteria. The feature above >> would be one very nice application for this. > > Gross! That's even more evil than variant symbolic links! Heh, you bet! :-) Actually, the more I think about it the more I realize that it probably can't be made to work. Sure, you could put in a hook so that a process could register itself with namei() [if the hook was NULL, namei() would simply always skip over it] and get called via some mechanism that would allow it to pre-massage the name and pass it back (perhaps totally transformed) to namei() for further processing. For most names, the process would simply pass it back unchanged, but for the hairy ftp://.. stuff it would fetch the file and pass namei() back the name of something in /tmp. The problem is, what does namei() do while the process is talking to some server halfway around the world? We certainly can't block in the kernel waiting or all the other users on the system would vomit up their entrails, and a `wake me up when you're done, please' mechanism would be a lot more work to implement. Perhaps we should forget that I even suggested it.. :-) However, I do feel compelled to note that the inability to do this kind of thing easily only underscores the abominable evil that is the whole UNIX filesystem paradigm (as if ioctl() wasn't enough to already convince us of this! :-). Jordan From owner-freebsd-hackers Fri Jan 27 12:58:37 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id MAA27304 for hackers-outgoing; Fri, 27 Jan 1995 12:58:37 -0800 Received: from time.cdrom.com (time.cdrom.com [192.216.223.46]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id MAA27298; Fri, 27 Jan 1995 12:58:34 -0800 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.9/8.6.9) with SMTP id MAA03566; Fri, 27 Jan 1995 12:58:26 -0800 To: terry@cs.weber.edu (Terry Lambert) cc: jkh@FreeBSD.org (Jordan K. Hubbard), hoppy@appsmiths.com, hackers@FreeBSD.org Subject: Re: >1024 cyl IDE drive In-reply-to: Your message of "Fri, 27 Jan 95 13:36:12 MST." <9501272036.AA00201@cs.weber.edu> Date: Fri, 27 Jan 1995 12:58:26 -0800 Message-ID: <3564.791240306@time.cdrom.com> From: "Jordan K. Hubbard" Sender: hackers-owner@FreeBSD.org Precedence: bulk > > You're saying that these bootblock-remapping drives fall over kicking > > when you install the boot manager? Aieee! I can't say we weren't warned > > about this.. Or does this not have anything to do with the boot block? > > I have the email addr of someone at OnTrack who actually wrote their boot > code that they install -- and it does this. > > More information as talks progress. > > I told you so. Being right about it doesn't make it suck less. 8-(. Actually, you weren't even the first to tell me so. A guy on USENET was the first to post this REALLY LONG article about it! :-) [What was his name, anyway? He had a number of good comments about the installation that I read, filed and never quite got back to following up on - one of the dangers of sending me really long emails! :-)] Jordan From owner-freebsd-hackers Fri Jan 27 13:02:02 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id NAA27395 for hackers-outgoing; Fri, 27 Jan 1995 13:02:02 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id NAA27389; Fri, 27 Jan 1995 13:01:58 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA00229; Fri, 27 Jan 95 13:39:25 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9501272039.AA00229@cs.weber.edu> Subject: Re: Am I dreaming? To: jkh@freefall.cdrom.com (Jordan K. Hubbard) Date: Fri, 27 Jan 95 13:39:24 MST Cc: hackers@freefall.cdrom.com In-Reply-To: <199501271800.KAA23617@freefall.cdrom.com> from "Jordan K. Hubbard" at Jan 27, 95 10:00:56 am X-Mailer: ELM [version 2.4dev PL52] Sender: hackers-owner@FreeBSD.org Precedence: bulk > Some may have noticed in the last snapshot that I'd created some seemingly > bogus symlinks of the form: > > lrwxrwxr-x 1 root bin 54 Jan 27 00:39 packages -> ftp://ftp.freebsd.org/pub/FreeBSD/2.0-RELEASE/packages > > Which are indeed bogus from the file point of view, but are at least > informational and show you just where you should go to get the real file. > Since the snaps are in an anon ftp area, I can't just point my symlinks > off to other NFS locations due to the chroot'd nature of it all. > > My question is, how hard would it be to make them MORE than informational? > e.g. the system sees one of these URL specs as a filename and auto-fetches > it for you. > > I guess this all gets back to the whole `user mode translation of file names' > thing we were talking about awhile back. It's not the same as portals, > which require a given mount point to be traversed, but rather affects all > files who's names match some sort of selection criteria. The feature above > would be one very nice application for this. > > Any comments? Am I, as the subject says, simply dreaming? You *could* do it with portals. Specifically, you'd probably have to take advantage of POSIX and use something like //ftp:... as the link target, then wire it from there. This does not seem to be very worthwhile a pursuit. Especially as your company sells CDROMS to the netless masses, where it would be totally irrelevant anyway. 8-). Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Fri Jan 27 13:03:21 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id NAA27445 for hackers-outgoing; Fri, 27 Jan 1995 13:03:21 -0800 Received: from kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id NAA27434; Fri, 27 Jan 1995 13:03:13 -0800 Received: from mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by kitten.mcs.com (8.6.9/8.6.9) with SMTP id PAA09448; Fri, 27 Jan 1995 15:02:59 -0600 Received: by mailbox.mcs.com (/\==/\ Smail3.1.28.1 #28.5) id ; Fri, 27 Jan 95 15:04 CST Received: by mercury.mcs.com (/\==/\ Smail3.1.28.1 #28.5) id ; Fri, 27 Jan 95 15:02 CST Message-Id: From: fredriks@mcs.com (Lars Fredriksen) Subject: Re: Am I dreaming? To: jkh@freefall.cdrom.com (Jordan K. Hubbard) Date: Fri, 27 Jan 1995 15:02:57 -0600 (CST) Cc: hackers@freefall.cdrom.com In-Reply-To: <199501271800.KAA23617@freefall.cdrom.com> from "Jordan K. Hubbard" at Jan 27, 95 10:00:56 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1626 Sender: hackers-owner@FreeBSD.org Precedence: bulk Jordan K. Hubbard writes: > > Some may have noticed in the last snapshot that I'd created some seemingly > bogus symlinks of the form: > > lrwxrwxr-x 1 root bin 54 Jan 27 00:39 packages -> ftp://ftp.freebsd.org/pub/FreeBSD/2.0-RELEASE/packages > > Which are indeed bogus from the file point of view, but are at least > informational and show you just where you should go to get the real file. > Since the snaps are in an anon ftp area, I can't just point my symlinks > off to other NFS locations due to the chroot'd nature of it all. > > My question is, how hard would it be to make them MORE than informational? > e.g. the system sees one of these URL specs as a filename and auto-fetches > it for you. > > I guess this all gets back to the whole `user mode translation of file names' > thing we were talking about awhile back. It's not the same as portals, > which require a given mount point to be traversed, but rather affects all > files who's names match some sort of selection criteria. The feature above > would be one very nice application for this. > > Any comments? Am I, as the subject says, simply dreaming? > > Jordan > It might be a dream, but a cool one at that. If you could live with a symlink that looks like: flexfax --> /ftp::/sgi.com/..., then you could mount an ftp, http etc filesystem on /ftp, /http etc that would do the trick. Now someone needs to write a ftp/http filesystem. Lars -- ------------------------------------------------------------------- Lars Fredriksen fredriks@mcs.com (home) lars@fredriks.pr.mcs.net (home-home) fredriks@asiago.cs.wisc.edu From owner-freebsd-hackers Fri Jan 27 13:05:44 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id NAA27524 for hackers-outgoing; Fri, 27 Jan 1995 13:05:44 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id NAA27516 for ; Fri, 27 Jan 1995 13:05:27 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA00342; Fri, 27 Jan 95 13:58:42 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9501272058.AA00342@cs.weber.edu> Subject: Re: Help with SCSI development (fwd) To: wollman@halloran-eldar.lcs.mit.edu (Garrett Wollman) Date: Fri, 27 Jan 95 13:58:41 MST Cc: freebsd-hackers@FreeBSD.org In-Reply-To: <9501272001.AA12096@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at Jan 27, 95 03:01:25 pm X-Mailer: ELM [version 2.4dev PL52] Sender: hackers-owner@FreeBSD.org Precedence: bulk > > < > > In effect, the NFS nfsd and biod processes, which make system calls and > > never return, as well as the swapper and update daemons, are in effect > > kernel threads, albiet threads with a proc structure attached to them > > for no good reason. > > UTSL. `nfssvc' does return for `nfsd' to perform authentication. Logically, isn't this more of a kernel callback to a user space routine that was preregistered ("authenticate") than a real return? In response, the daemon immediately recalls, returning the thread of control to kernel space. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Fri Jan 27 13:06:26 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id NAA27540 for hackers-outgoing; Fri, 27 Jan 1995 13:06:26 -0800 Received: from inetgwy.asctmd.com (inetgwy.asctmd.com [198.59.170.33]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id NAA27526 for ; Fri, 27 Jan 1995 13:05:54 -0800 From: supervisor@alb.asctmd.com Received: from alb.asctmd.com (alb.asctmd.com [198.59.170.34]) by inetgwy.asctmd.com (8.6.8/8.6.6) with SMTP id OAA27616 for ; Fri, 27 Jan 1995 14:09:31 -0700 Received: from ALBUQUERQUE-Message_Server by alb.asctmd.com with WordPerfect_Office; Fri, 27 Jan 1995 14:06:26 -0700 Message-Id: X-Mailer: WordPerfect Office 4.0 Date: Fri, 27 Jan 1995 14:02:35 -0700 To: hackers@FreeBSD.org Subject: Very ALPHA netipx Code Available Sender: hackers-owner@FreeBSD.org Precedence: bulk I have uploaded my very ALPHA netipx stuff to the incomming directory on freefall.freebsd.org. The file is "netipx.tar.gz". Attached below is the README file which is included in the kit. If you wish to test this code and contribute patches, I will happily accept these and attempt to reintegrate them into my kit. I do not currently have the time spend on major support or enhancements. Late Breaking Note: You should ifconfig your ethernet interface with an IPX address right away following boot. A kernel built with these mods will crash without an IPX address after receiving a few IPX "broadcast" packets. /sbin/ifconfig ed1 ipx 0xaabbccdd # configure IPX network aabbccdd ---------- The purpose of this kit is to add rudimentary support for the IPX protocol (EtherNet_II frame type 0x8137) to the 4.4BSD Lite source tree. Please realize that it is currently very ALPHA and your mileage is expected to vary. I do not currently have the time to support this package the way I would like to; but, I am making it available in the hopes that someone else might. Mike Mitchell --- Projects for the Daring --- 1. Perform alot more testing. I do not know if the spx code works. However, it does compile without complaints. 2. Create and enhance more applications: IPXrouted keep ipx routing information up to date, implement correctly libc/net/gethostbyht.c libc/net/getnetbyht.c enhance routines with proto family field to support AF_IPX ipxping similar to ip ping but for a remote ipx host samba fix samba to work on AF_IPX to support Windows for Workgroups using the NetBIOS transport over SPX 3. The big pie in the sky would be to have a complete suite of working NetWare client utilities. Wouldn't you like to see a 'NFS like' file system attached to a NetWare server? Or maybe, emulation of a NetWare server so that clients may connect? --- Installation Notes --- 1. Install the FreeBSD 2.0 source tree. All patches have been made relative to a FreeBSD 2.0 Release source tree. The source tree available to me comes on the InfoMagic BSDisc. 2. Untar the netipx kit from the root directory. All of the pathnames are relative to the root directory. This will install new files in the source tree. If you wish to extract this kit in another directory, be sure to install all of the new files manually. 3. Apply the patches. It is not recommended that you apply these patches on a production environment. patch -p0 < PATCHES 4. Include the following lines in your kernel configuration file after application of the netipx kit. options IPX #IPX Networking Support options IPXIP #IPX over IP Networking Support 5. Rebuild your kernel and reboot. cd /usr/src/sys/i386/conf config GENERIC # GENERIC = your config file cd /usr/src/sys/compile/GENERIC # GENERIC = your config file make depend; make cp /kernel /kernel.old cp kernel /kernel shutdown -r now 6. Rebuild and install: libc, ifconfig, netstat cd /usr/src/lib/libc; make; make install cd /usr/src/sbin/ifconfig; make; make install cd /usr/src/usr.bin/netstat; make; make install cd /usr/src/usr.sbin/IPXrouted; make; make install 7. Test, Test, Test --- New Files --- The following list of files are not present in the FreeBSD 2.0 Release source tree: /usr/include/netipx/ipx.h /usr/include/netipx/ipx_error.h /usr/include/netipx/ipx_if.h /usr/include/netipx/ipx_pcb.h /usr/include/netipx/ipx_var.h /usr/include/netipx/spx.h /usr/include/netipx/spx_debug.h /usr/include/netipx/spx_timer.h /usr/include/netipx/spx_var.h /usr/src/lib/libc/net/ipx.3 /usr/src/lib/libc/net/ipx_addr.c /usr/src/lib/libc/net/ipx_ntoa.c /usr/src/sys/netipx/MAKE.PATCHES /usr/src/sys/netipx/MANIFEST /usr/src/sys/netipx/MANIFEST.DIFFS /usr/src/sys/netipx/PATCHES /usr/src/sys/netipx/README /usr/src/sys/netipx/ipx.c /usr/src/sys/netipx/ipx.h /usr/src/sys/netipx/ipx_cksum.c /usr/src/sys/netipx/ipx_error.c /usr/src/sys/netipx/ipx_error.h /usr/src/sys/netipx/ipx_if.h /usr/src/sys/netipx/ipx_input.c /usr/src/sys/netipx/ipx_ip.c /usr/src/sys/netipx/ipx_outputfl.c /usr/src/sys/netipx/ipx_pcb.c /usr/src/sys/netipx/ipx_pcb.h /usr/src/sys/netipx/ipx_proto.c /usr/src/sys/netipx/ipx_usrreq.c /usr/src/sys/netipx/ipx_var.h /usr/src/sys/netipx/spx.h /usr/src/sys/netipx/spx_debug.c /usr/src/sys/netipx/spx_debug.h /usr/src/sys/netipx/spx_timer.h /usr/src/sys/netipx/spx_usrreq.c /usr/src/sys/netipx/spx_var.h /usr/src/usr.bin/netstat/ipx.c /usr/src/usr.sbin/IPXrouted/IPXrouted.8 /usr/src/usr.sbin/IPXrouted/Makefile /usr/src/usr.sbin/IPXrouted/af.c /usr/src/usr.sbin/IPXrouted/af.h /usr/src/usr.sbin/IPXrouted/defs.h /usr/src/usr.sbin/IPXrouted/if.c /usr/src/usr.sbin/IPXrouted/input.c /usr/src/usr.sbin/IPXrouted/interface.h /usr/src/usr.sbin/IPXrouted/main.c /usr/src/usr.sbin/IPXrouted/output.c /usr/src/usr.sbin/IPXrouted/protocol.h /usr/src/usr.sbin/IPXrouted/startup.c /usr/src/usr.sbin/IPXrouted/table.h /usr/src/usr.sbin/IPXrouted/tables.c /usr/src/usr.sbin/IPXrouted/timer.c /usr/src/usr.sbin/IPXrouted/tools/query.c /usr/src/usr.sbin/IPXrouted/trace.c /usr/src/usr.sbin/IPXrouted/trace.h --- PATCHED FILES --- The following list of files are present in the FreeBSD 2.0 Release source tree and require modification: /usr/include/net/netisr.h /usr/include/net/route.h /usr/include/netiso/iso_errno.h /usr/src/sys/conf/files /usr/src/sys/i386/i386/machdep.c /usr/src/sys/i386/isa/if_ed.c /usr/src/sys/i386/isa/if_el.c /usr/src/sys/i386/isa/if_ep.c /usr/src/sys/i386/isa/if_ie.c /usr/src/sys/i386/isa/if_is.c /usr/src/sys/i386/isa/if_le.c /usr/src/sys/i386/isa/if_ze.c /usr/src/sys/i386/pci/if_de.c /usr/src/sys/kern/uipc_domain.c /usr/src/sys/net/if_ethersubr.c /usr/src/sys/net/if_loop.c /usr/src/sys/net/if_ppp.c /usr/src/sys/net/netisr.h /usr/src/sys/net/route.c /usr/src/sys/net/route.h /usr/src/sys/net/rtsock.c /usr/src/sys/netccitt/if_x25subr.c /usr/src/sys/netinet/in_proto.c /usr/src/sys/netiso/iso_errno.h /usr/src/usr.bin/netstat/Makefile /usr/src/usr.bin/netstat/if.c /usr/src/usr.bin/netstat/main.c /usr/src/usr.bin/netstat/netstat.h /usr/src/usr.bin/netstat/route.c /usr/src/sbin/ifconfig/ifconfig.c /usr/src/lib/libc/net/Makefile.inc From owner-freebsd-hackers Fri Jan 27 13:09:47 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id NAA27593 for hackers-outgoing; Fri, 27 Jan 1995 13:09:47 -0800 Received: from salyko.cube.net (salyko.cube.net [193.141.73.1]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id NAA27586 for ; Fri, 27 Jan 1995 13:09:11 -0800 Received: from nasim.nasim.cube.net by salyko.cube.net with smtp (Smail3.1.29.1 #1) id m0rXxtu-0002AaC; Fri, 27 Jan 95 22:08 MET Received: by nasim.nasim.cube.net (Smail3.1.29.0 #1) id m0rXxtd-000OMoC; Fri, 27 Jan 95 22:07 MET To: freebsd-hackers@freefall.cdrom.com Path: not-for-mail From: knarf@nasim.nasim.cube.net (Frank Bartels) Newsgroups: muc.lists.freebsd.hackers Subject: 1.1.5: ft Date: 27 Jan 1995 22:07:52 +0100 Organization: The Sunsite for ATARI-Friends Lines: 42 Message-ID: <3gbnb8$q9v@nasim.nasim.cube.net> X-Newsreader: TIN [version 1.2 PL2] Sender: hackers-owner@FreeBSD.org Precedence: bulk Hi! Environment: 386/40, ISA, Floppy Streamer, FreeBSD 1.1.5. sogand:/root# dmesg | grep ft fdc0: [0: fd0: 1.44MB 3.5in] [2: ft0: Colorado tape] I tried to make a Backup (which usually worked fine): tar cvlf - / /usr | ft "Backup vom 27.01.94" After a while the streamer stopped working and ft is still hanging: sogand:/root# ps -lp 10819 UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND 0 10819 1 5 -6 0 264 0 bavail DW p1- 0:04.30 ft Backup vo sogand:/root# fstat | grep ft root ft 10819 wd / 5 drwxr-xr-x 512 root ft 10819 0* unix stream f0af2694 root ft 10819 1 - - none - root ft 10819 2 - - none - root ft 10819 3 / 3212 crw-r----- rft0a I tried any signal (1, 15, 9) but the process does not disappear. I cannot use the floppy now, too: sogand:/root# cat /dev/rfd0.1440 cat: /dev/rfd0.1440: Device busy But: sogand:/root# fstat | grep fd [nothing] What can I do? I don't want to reboot. Bye, Knarf -- Frank Bartels | UUCP/ZModem: + 49 89 5469593 | MiNT is knarf@nasim.cube.net | Login: nuucp Index: /pub/ls-lR.nasim.gz | Now TOS! From owner-freebsd-hackers Fri Jan 27 13:18:56 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id NAA27794 for hackers-outgoing; Fri, 27 Jan 1995 13:18:56 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id NAA27784; Fri, 27 Jan 1995 13:18:36 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA00447; Fri, 27 Jan 95 14:12:35 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9501272112.AA00447@cs.weber.edu> Subject: Re: >1024 cyl IDE drive To: jkh@FreeBSD.org (Jordan K. Hubbard) Date: Fri, 27 Jan 95 14:12:35 MST Cc: jkh@FreeBSD.org, hoppy@appsmiths.com, hackers@FreeBSD.org In-Reply-To: <3564.791240306@time.cdrom.com> from "Jordan K. Hubbard" at Jan 27, 95 12:58:26 pm X-Mailer: ELM [version 2.4dev PL52] Sender: hackers-owner@FreeBSD.org Precedence: bulk [ ... translation in boot manager ... ] > Actually, you weren't even the first to tell me so. A guy on USENET > was the first to post this REALLY LONG article about it! :-) > > [What was his name, anyway? He had a number of good comments about the > installation that I read, filed and never quite got back to following up > on - one of the dangers of sending me really long emails! :-)] UGH! This is driving me nuts! The one frigging article I thought I saved but didn't! Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Fri Jan 27 13:21:51 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id NAA27948 for hackers-outgoing; Fri, 27 Jan 1995 13:21:51 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id NAA27942 for ; Fri, 27 Jan 1995 13:21:46 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA00468; Fri, 27 Jan 95 14:15:42 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9501272115.AA00468@cs.weber.edu> Subject: Re: Am I dreaming? To: jkh@FreeBSD.org (Jordan K. Hubbard) Date: Fri, 27 Jan 95 14:15:41 MST Cc: wollman@halloran-eldar.lcs.mit.edu, hackers@freefall.cdrom.com In-Reply-To: <3196.791240166@time.cdrom.com> from "Jordan K. Hubbard" at Jan 27, 95 12:56:06 pm X-Mailer: ELM [version 2.4dev PL52] Sender: hackers-owner@FreeBSD.org Precedence: bulk > However, I do feel compelled to note that the inability to do this kind > of thing easily only underscores the abominable evil that is the whole > UNIX filesystem paradigm (as if ioctl() wasn't enough to already convince > us of this! :-). File system ioctl()'s are beauty incarnate. It's the open/close/read/write/opendir/readdir/closedir/especially-telldir crap that ought to go. Well, OK, keep open and close to get handles you can ioctl() to, but that's it! Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Fri Jan 27 13:32:47 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id NAA28130 for hackers-outgoing; Fri, 27 Jan 1995 13:32:47 -0800 Received: from time.cdrom.com (time.cdrom.com [192.216.223.46]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id NAA28122 for ; Fri, 27 Jan 1995 13:32:40 -0800 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.9/8.6.9) with SMTP id NAA21806; Fri, 27 Jan 1995 13:32:08 -0800 To: terry@cs.weber.edu (Terry Lambert) cc: wollman@halloran-eldar.lcs.mit.edu, hackers@freefall.cdrom.com Subject: Re: Am I dreaming? In-reply-to: Your message of "Fri, 27 Jan 95 14:15:41 MST." <9501272115.AA00468@cs.weber.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 27 Jan 1995 13:32:08 -0800 Message-ID: <21803.791242328@time.cdrom.com> From: "Jordan K. Hubbard" Sender: hackers-owner@FreeBSD.org Precedence: bulk > File system ioctl()'s are beauty incarnate. I didn't know opium was available in Utah again! I thought the last crackdown had the supply pretty much dried up! :-) And yes, the *dir calls vie closely with ioctl() for sheer evil, though I think ioctl() wins. A filesystem paradigm where to extend it you have to add magic little integers in sys/ioctl.h. I must stop. I am feeling seasick already. Jordan From owner-freebsd-hackers Fri Jan 27 13:53:47 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id NAA28577 for hackers-outgoing; Fri, 27 Jan 1995 13:53:47 -0800 Received: from post.demon.co.uk (post.demon.co.uk [158.152.1.72]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id NAA28555 for ; Fri, 27 Jan 1995 13:53:35 -0800 Received: from palmer.demon.co.uk by post.demon.co.uk id aa04812; 27 Jan 95 21:51 GMT Received: (from gary@localhost) by palmer.demon.co.uk (8.6.9/8.6.9) id QAA00178; Fri, 27 Jan 1995 16:54:10 GMT From: Gary Palmer Message-Id: <199501271654.QAA00178@palmer.demon.co.uk> Subject: Re: REMAKE WORLD To: Richard Wackerbarth Date: Fri, 27 Jan 1995 16:54:09 +0000 (WET) Cc: hackers@FreeBSD.org, freebsd-current@freefall.cdrom.com In-Reply-To: from "Richard Wackerbarth" at Jan 27, 95 08:55:43 am X-OS: FreeBSD 2.1.0-Development X-Mailer: ELM [version 2.4 PL22] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 678 Sender: hackers-owner@FreeBSD.org Precedence: bulk > 7. I know that we are not NetBSD but ... Multi-platform cross compiling is > close enough to a fall-out that I think we should include the mechanism for > it. If you hadn't suggested multi-platform support, I personally would come to your house and persuade you the hard way that it's a good idea! I (and others) have spent too much time on porting FreeBSD for someone to come along and screw up the makefiles so that it'll only work on the PC!! Gary -- FreeBSD/ARM (ArchBSD) Core Member - BSD for the Acorn RISC platforms E-Mail: Gary@Palmer.Demon.co.uk, gpalmer@FreeBSD.org WWW Pages: http://WWW.FreeBSD.org/~gpalmer/ First the Daemon was Free - now the Daemon is ARMed. From owner-freebsd-hackers Fri Jan 27 14:50:13 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id OAA00199 for hackers-outgoing; Fri, 27 Jan 1995 14:50:13 -0800 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id OAA00191 for ; Fri, 27 Jan 1995 14:50:08 -0800 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id RAA09638; Fri, 27 Jan 1995 17:49:51 -0500 From: Peter Dufault Message-Id: <199501272249.RAA09638@hda.com> Subject: Re: Help with SCSI development (fwd) To: phk@ref.tfs.com (Poul-Henning Kamp) Date: Fri, 27 Jan 1995 17:49:50 -0500 (EST) Cc: wollman@halloran-eldar.lcs.mit.edu, freebsd-hackers@FreeBSD.org In-Reply-To: <199501272012.MAA07301@ref.tfs.com> from "Poul-Henning Kamp" at Jan 27, 95 12:12:46 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1020 Sender: hackers-owner@FreeBSD.org Precedence: bulk Poul-Henning Kamp writes: > > > >> I'm planning to write software using Freebsd that will allow files to > > >> be striped over multiple disks. > > > > There is already software in 4.4-Lite which is designed specifically > > for this purpose, although it is named badly and probably would take a > > bit of porting work to get it up to speed. See /sys/dev/cd.c in a > > convenient 4.4-Lite tree. > > That stuff is a hack. > > I agree with Terry, this should be done "The Right Way". > Can I ask what may be a stupid question? When you call a strategy function you either chain it into the start queue or start the I/O and then return. Then you call biodone to block. What is the flaw in thinking that you can call a set of strategies and then a set of biodones? Peter -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 -- Formerly hd@world.std.com. E-mail problems? Tell hdslip@iii.net From owner-freebsd-hackers Fri Jan 27 15:28:18 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id PAA00823 for hackers-outgoing; Fri, 27 Jan 1995 15:28:18 -0800 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id PAA00781; Fri, 27 Jan 1995 15:27:21 -0800 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id SAA09764; Fri, 27 Jan 1995 18:27:06 -0500 From: Peter Dufault Message-Id: <199501272327.SAA09764@hda.com> Subject: Re: SCSI device configuring.. (was scsi renames devices) To: julian@tfs.com (Julian Elischer) Date: Fri, 27 Jan 1995 18:27:05 -0500 (EST) Cc: hsu@fx7.cs.hut.fi, freebsd-hackers@freefall.cdrom.com, freebsd-scsi@freefall.cdrom.com In-Reply-To: from "Julian Elischer" at Jan 27, 95 12:08:58 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1093 Sender: hackers-owner@FreeBSD.org Precedence: bulk Julian Elischer writes: (Interesting stuff that I'll comment on later, but this I have to comment on right away...) > > However, we have to consider the problem of booting an old kernel e > and having the same problem Heikki mentions, namely, the new sd0 > > is scsi id3 or something and we mount on top of it and trash the > > disk. > how many really old kernels do people run? particularly after > a revision upgrade? I don't think we can make changes that will damage a file system if someone boots an older kernel of the same major rev. (I can see the 2.1 post now: "I had a copy of 2.0R on floppy, so I booted that and...") Although I also suppose that there are sanity checks that prevent a UFS file system from being mounted as swap, right? Am I right that most scenarios where a file system is trashed are bugs that we can address? Peter -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 -- Formerly hd@world.std.com. E-mail problems? Tell hdslip@iii.net From owner-freebsd-hackers Fri Jan 27 15:40:18 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id PAA01278 for hackers-outgoing; Fri, 27 Jan 1995 15:40:18 -0800 Received: from UUCP-GW.CC.UH.EDU (root@UUCP-GW.CC.UH.EDU [129.7.1.11]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id PAA01258; Fri, 27 Jan 1995 15:40:10 -0800 Received: from Taronga.COM by UUCP-GW.CC.UH.EDU with UUCP id AA17758 (5.67a/IDA-1.5); Fri, 27 Jan 1995 17:11:14 -0600 Received: by bonkers.taronga.com (smail2.5p) id AA22036; 27 Jan 95 17:09:44 CST (Fri) Received: (from peter@localhost) by bonkers.taronga.com (8.6.8/8.6.6) id RAA22033; Fri, 27 Jan 1995 17:09:43 -0600 From: Peter da Silva Message-Id: <199501272309.RAA22033@bonkers.taronga.com> Subject: Re: Am I dreaming? To: jkh@freefall.cdrom.com (Jordan K. Hubbard) Date: Fri, 27 Jan 1995 17:09:43 -0600 (CST) Cc: hackers@freefall.cdrom.com In-Reply-To: <199501271800.KAA23617@freefall.cdrom.com> from "Jordan K. Hubbard" at Jan 27, 95 10:00:56 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 952 Sender: hackers-owner@FreeBSD.org Precedence: bulk > My question is, how hard would it be to make them MORE than informational? > e.g. the system sees one of these URL specs as a filename and auto-fetches > it for you. Yow. Now *that* would be way cool. What would you do, have a mechanism to register a program to be passed the URL if you open a symlink that matches URL format? (ooh, then you could do ln -s http://localhost/cgi-bin/executable?symlink+target file though it'd be more fun to do ln -s sh:/usr/local/bin/... file ) > I guess this all gets back to the whole `user mode translation of file names' > thing we were talking about awhile back. It's not the same as portals, > which require a given mount point to be traversed, but rather affects all > files who's names match some sort of selection criteria. The feature above > would be one very nice application for this. I'd make it only in symlinks, and make the symlink match something more than just a URL... (@proto://...?). From owner-freebsd-hackers Fri Jan 27 16:17:55 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id QAA02078 for hackers-outgoing; Fri, 27 Jan 1995 16:17:55 -0800 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id QAA02068 for ; Fri, 27 Jan 1995 16:17:53 -0800 Received: by halloran-eldar.lcs.mit.edu; id AA12682; Fri, 27 Jan 1995 19:17:42 -0500 Date: Fri, 27 Jan 1995 19:17:42 -0500 From: Garrett Wollman Message-Id: <9501280017.AA12682@halloran-eldar.lcs.mit.edu> To: terry@cs.weber.edu (Terry Lambert) Cc: hackers@FreeBSD.org Subject: Re: SyQuest works with FreeBSD 2.0R ! In-Reply-To: <9501272046.AA00266@cs.weber.edu> References: <199501271150.GAA07921@hda.com> <9501272046.AA00266@cs.weber.edu> Sender: hackers-owner@FreeBSD.org Precedence: bulk < I think that the sound-baster drivers fall into the "uncomfortable" > category. Stupid question: Why would the host adapter know anything at all about LUNs? -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-hackers Fri Jan 27 16:42:56 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id QAA02307 for hackers-outgoing; Fri, 27 Jan 1995 16:42:56 -0800 Received: from tfs.com (mailhub.tfs.com [140.145.250.1]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id QAA02301 for ; Fri, 27 Jan 1995 16:42:53 -0800 Received: by tfs.com (smail3.1.28.1) Message-Id: From: julian@tfs.com (Julian Elischer) Subject: Re: Joystick driver available To: mtaylor@gateway.cybernet.com (Mark J. Taylor) Date: Fri, 27 Jan 1995 16:42:16 -0800 (PST) Cc: kuku@gilberto.physik.rwth-aachen.de, hackers@FreeBSD.org In-Reply-To: from "Mark J. Taylor" at Jan 27, 95 03:08:14 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 720 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > We (Cybernet Systems) actually implemented a driver, the MultiMouse, which > looks like a MouseSystems mouse to FreeBSD/XFree86, but it is actually > talking over a socket to our mouse driver, which takes multiple input > channels and converts them to 2-byte deltas and left-middle-right buttons > of a MouseSystems mouse. [...] > > I won't post another message to this group regarding this product, unless > prompted to. Sorry about this "commercial" message. > > If anyone has any comments, questions, etc., email me. I will respond > privately. If there are concerns about source code availability, please > email me and we'll talk... if we implimrnt such a neat idea ourselves.. do we get sued? :) > From owner-freebsd-hackers Fri Jan 27 17:02:11 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id RAA02490 for hackers-outgoing; Fri, 27 Jan 1995 17:02:11 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id RAA02484 for ; Fri, 27 Jan 1995 17:02:10 -0800 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id RAA22845; Fri, 27 Jan 1995 17:01:49 -0800 From: Poul-Henning Kamp Message-Id: <199501280101.RAA22845@ref.tfs.com> Subject: Re: Help with SCSI development (fwd) To: dufault@hda.com (Peter Dufault) Date: Fri, 27 Jan 1995 17:01:49 -0800 (PST) Cc: wollman@halloran-eldar.lcs.mit.edu, freebsd-hackers@FreeBSD.org In-Reply-To: <199501272249.RAA09638@hda.com> from "Peter Dufault" at Jan 27, 95 05:49:50 pm Content-Type: text Content-Length: 638 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > I agree with Terry, this should be done "The Right Way". > > > > Can I ask what may be a stupid question? When you call a strategy > function you either chain it into the start queue or start the I/O > and then return. Then you call biodone to block. What is the > flaw in thinking that you can call a set of strategies and then a > set of biodones? What I meant was, striped disks are only one subset of "virtual disks", mirrors, raid# and so on come to mind too. Make it general. -- Poul-Henning Kamp TRW Financial Systems, Inc. FreeBSD has, until now, not one single time had an undetected error. :-) From owner-freebsd-hackers Fri Jan 27 17:23:30 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id RAA02816 for hackers-outgoing; Fri, 27 Jan 1995 17:23:30 -0800 Received: from netcom2.netcom.com (root@netcom2.netcom.com [192.100.81.108]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id RAA02810; Fri, 27 Jan 1995 17:23:27 -0800 Received: from localhost by netcom2.netcom.com (8.6.9/Netcom) id RAA13132; Fri, 27 Jan 1995 17:16:32 -0800 Message-Id: <199501280116.RAA13132@netcom2.netcom.com> To: "Jordan K. Hubbard" cc: hackers@freefall.cdrom.com Subject: Re: Am I dreaming? In-reply-to: Your message of "Fri, 27 Jan 95 10:00:56 PST." <199501271800.KAA23617@freefall.cdrom.com> Date: Fri, 27 Jan 95 17:16:31 -0800 From: Bakul Shah Sender: hackers-owner@FreeBSD.org Precedence: bulk Wouldn't `Alex' do what you want? Here is a brief blurb from an old net message by Jurgen Botz about alex: ...by far the most elegant solution is to eliminate the FTP client entirely and make the global FTP space part of your file system. Then you can write ordinary shell scripts to automate "FTP" operations. There is a program called "Alex" (from "Alexandria", as in: The Library of...) that implements this solution as an NFS <-> FTP protocol "gateway", complete with some sophisticated caching. You can get, build, and install it on a Unix machine that supports NFS Then there is `prospero' by B. Clifford Neuman which does something similar + uses archie. I have not heard much lately about either system and I do not know how well they work in practice. Try archie to find out more recent info! From owner-freebsd-hackers Fri Jan 27 17:57:08 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id RAA03404 for hackers-outgoing; Fri, 27 Jan 1995 17:57:08 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id RAA03398 for ; Fri, 27 Jan 1995 17:57:07 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA01872; Fri, 27 Jan 95 18:51:14 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9501280151.AA01872@cs.weber.edu> Subject: Re: SyQuest works with FreeBSD 2.0R ! To: wollman@halloran-eldar.lcs.mit.edu (Garrett Wollman) Date: Fri, 27 Jan 95 18:51:13 MST Cc: hackers@FreeBSD.org In-Reply-To: <9501280017.AA12682@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at Jan 27, 95 07:17:42 pm X-Mailer: ELM [version 2.4dev PL52] Sender: hackers-owner@FreeBSD.org Precedence: bulk > > < > > I think that the sound-baster drivers fall into the "uncomfortable" > > category. > > Stupid question: > > Why would the host adapter know anything at all about LUNs? terry: File table overflow It shouldn't. But dual Bernoulli's seem to puke it. I thought it was the LUNs, since single Bernoulli's are OK. I could be wrong. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Fri Jan 27 18:59:58 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id SAA04235 for hackers-outgoing; Fri, 27 Jan 1995 18:59:58 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id SAA04228; Fri, 27 Jan 1995 18:59:40 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id NAA18071; Sat, 28 Jan 1995 13:56:35 +1100 Date: Sat, 28 Jan 1995 13:56:35 +1100 From: Bruce Evans Message-Id: <199501280256.NAA18071@godzilla.zeta.org.au> To: jkh@FreeBSD.org, terry@cs.weber.edu Subject: Re: >1024 cyl IDE drive Cc: hackers@FreeBSD.org, hoppy@appsmiths.com Sender: hackers-owner@FreeBSD.org Precedence: bulk >> I told you so. Being right about it doesn't make it suck less. 8-(. >Actually, you weren't even the first to tell me so. A guy on USENET >was the first to post this REALLY LONG article about it! :-) Someone told us long before that in the enclosed mail to freebsd-bugs. I thought it was well known to boot block hackers. Bruce >From owner-freebsd-bugs@freefall.cdrom.com Fri Nov 25 10:35:15 1994 Received: (from root@localhost) by freefall.cdrom.com (8.6.8/8.6.6) id PAA14743 for bugs-outgoing; Thu, 24 Nov 1994 15:31:31 -0800 Received: from albert.gnu.ai.mit.edu (root@albert.gnu.ai.mit.edu [128.52.46.31]) by freefall.cdrom.com (8.6.8/8.6.6) with ESMTP id PAA14737 for ; Thu, 24 Nov 1994 15:31:29 -0800 From: room42@gnu.ai.mit.edu Received: from spiff.gnu.ai.mit.edu by albert.gnu.ai.mit.edu (8.6.9/4.0) with SMTP id ; Thu, 24 Nov 1994 18:31:28 -0500 Received: by spiff.gnu.ai.mit.edu (5.65/4.0) id ; Thu, 24 Nov 94 18:30:37 -0500 Message-Id: <9411242330.AA08604@spiff.gnu.ai.mit.edu> Subject: URGENT - Install 2.0 trashes DOS partitions? To: bugs@freebsd.org Date: Thu, 24 Nov 1994 18:30:35 -0500 (EST) X-Mailer: ELM [version 2.4 PL5] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 7140 Sender: bugs-owner@freebsd.org Precedence: bulk Status: RO This URGENT bug report describes a possible disk partitioning problem that might potentially trash large numbers of users hard disks. Please ensure it is examined BEFORE CD-ROMs are mastered. It may well be a false alarm but I think somebody who knows more about this than I do better take a look. The problem is that disk geometry remapping is not only performed by the IDE controller or BIOS but also on many machines by special boot programs in the MBR sector which might appear to be the same as a BIOS remapping to FreeBSD utilities, but unlike a BIOS remapping would disappear when the MBR is re-written unless special precautions, not mentioned in the INSTALL file, are taken. Although there are many such machines around, they are unlikely to have been used in FreeBSD testing as explained below. According to the INSTALL file. vvvvvvvvvvvvvvvvvv At this point we're happy with the slices on the first drive, so we type `w' to write the new information out. It also prompts to make *sure* we really want to do this, so we backspace over the default of `N' and type `y'. And this point, we also can decide whether or not we want a "boot manager" installed. A boot manager is a little utility that prompts you for the operating system you want to boot every time you reset or power on your PC, and can be a very handy way of sharing your computer between FreeBSD and some other OS, like Linux or DOS. We decide that we want to have this feature, so we `b' to write the special MBR (B)ootcode out to the disk. This does not harm any of the other operating systems on the disk, as it's written to a special area. Now we exit this screen by typing `q', for (Q)uit. ^^^^^^^^^^^^^^^^^^ I believe this MAY "harm any of the other operating systems on the disk" under circumstances that could be quite common but have escaped FreeBSD release testing. That could result in the sort of reputation that was achieved by early forms of disk compression! There is no reference here to MBRs that perform geometry remapping. That is either a minor and fairly harmless flaw in the documentation or a MAJOR disaster that could result in significant numbers of hard disks being trashed. FreeBSD is now easy enough to install that many people will be able to do so who do NOT have the sense (or the tape drive) to do a full backup first and who have no idea what an FDISK partition or MBR is or does. I have not studied the code, or even installed the software yet, let alone experienced any problem, so this may be a completely false alarm, however the potential implications are serious enough to be worth the risk of wasting your time (and mine) on checking this out - especially as CD-ROMs that will reach a much wider audience are presumably being mastered right now. Many clone PCs are now being sold with disk drives that have more than 1024 cylinders but no geometry remapping support in the IDE controller or BIOS. A disk utility is used by the clone supplier, (before delivering the machine to the user, so most users would be unaware of its significance), which installs its own boot code in the MBR. (It signs on before the "Starting MSDOS" message and there is no driver in CONFIG.SYS or AUTOEXEC.BAT). Presumably this does geometry remapping in the same way that a BIOS would. This is a common approach for clones with over 500MB drives, which would be popular for many potential FreeBSD users (but have only recently become common). There is a clear warning in the accompanying documentation that this will not work with Unix partitions and that a "startup" floppy which can restore the MBR should be made in case the DOS partitions appear to have disappeared one day. (But only obsessive-compulsive paranoids read such documentation :-). If FreeBSD writes out a "standard" boot sector then presumably this code would be lost, unlike the "normal" BIOS remapping which you have presumably provided for. At best that would merely require restoration from a backup of the original MBR, as provided for in OS-BS. If that backup has been ENFORCED by the install procedures then this may be only a minor documentation flaw in not explaining (likewise if some other solution has been provided or if for some reason there is no problem - the documentation should simply be improved when convenient for the benefit of paranoids who read their disk controller manuals and/or who insist on having their installation floppies write protected and only made an unprotected copy of the wrong one :-) At worst however it might be that a user finds DOS booting up with a partition that can read enough of the first few sectors (before the different geometries matter) to pick up an apparently valid FAT table, and proceeds to totally scramble their disk while making copies of new CONFIG.SYS and AUTOEXEC.BAT files to figure out why things no longer seem to be working. An intermediate possibility is that that any problem always results in an unbootable hard disk rather than a scrambled one, but keeping a backup MBR is left to the user's discretion, as in OS-BS, which isn't really viable with the improved installation procedures (and mass market CD-ROM distribution) allowing people who don't know what they are doing to try it out. (Cf the precautions NOW taken by MSDOS disk compression with NO user discretion about them - AFTER numerous disasters.) I am concerned that a problem could easily have slipped by because: a) Most (or perhaps all) FreeBSD testers that have DOS would never think of trying to install FreeBSD on a machine which ONLY has a single DOS partition for the whole disk - which is the most likely scenario for a user with one of these geometry remapping MBRs. (Not needed and therefore not installed by the utility unless the DOS partition uses over 1024 "real" cylinders AND there is no BIOS remapping - i.e. usually a "whole disk"). Also I suspect that FIPS might successfully reduce the size of the partition to leave room for a second one since it could see and use the remapped geometry correctly as long as the special MBR is in place, just as though it was in the IDE controller or BIOS. b) The FreeBSD 1.1 installation only referred to BIOS remapping (and did not provide an automated solution or mention that simply using fdisk -i to correct the BIOS geometry AFTER making the disklabels and re-booting from floppy eliminates any need for hand-crafting to deal with BIOS remapping). There was no reference to MBR remapping, so you might well be unaware of it. Anyway I'm sorry if this wastes your time (which incidentally is GREATLY appreciated - THANKS for FreeBSD!). But I simply CAN'T check it out myself immediately and I thought it would be irresponsible to delay reporting the possible problem until I can be sure I am not just exposing my (considerable) ignorance. So I am just doing what I can TODAY to draw your attention to the POSSIBILITY. Seeya, Albert PS. If these are mailing lists sorry, but I haven't even subscribed (before panicking :-). Please CC any response direct. -- Albert.Langer@gnu.ai.mit.edu Disclaimer: "I am not a Marxist" - Karl Marx From owner-freebsd-hackers Fri Jan 27 20:30:35 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id UAA06164 for hackers-outgoing; Fri, 27 Jan 1995 20:30:35 -0800 Received: (from jkh@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id UAA06157 for hackers@freebsd.org; Fri, 27 Jan 1995 20:30:34 -0800 Date: Fri, 27 Jan 1995 20:30:34 -0800 From: "Jordan K. Hubbard" Message-Id: <199501280430.UAA06157@freefall.cdrom.com> To: hackers@FreeBSD.org Subject: pcd0?? Sender: hackers-owner@FreeBSD.org Precedence: bulk >From files.i386: i386/isa/pcd.c optional pcd device-driver Would someone kindly explain what this is doing here? The referenced file doesn't even exist! I would like to remove it and will do so in 24 hours if nobody pipes up. It's also referenced in LINT, and this is simply deceptive of support we currently do NOT offer! This entry is relevant to the change: revision 1.67 date: 1994/12/26 01:06:41; author: ats; state: Exp; lines: +2 -1 Correct the devices.i386 for the major numbers. 8 was already used now by the lkm driver, so put scd and pcd to the numbers they have now in i386/conf.c. Add the pcd.c file for the panasonic driver in files.i386. But I've mailed Andreas Schulz 3 times about this and never received an answer, so I can only presume that his mail is either broken or he's dead. The scd driver never existed either, at least not until about 5 minutes ago! I have absolutely no idea what Andreas had in mind, and he's not talking, so.... Jordan From owner-freebsd-hackers Fri Jan 27 20:32:50 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id UAA06194 for hackers-outgoing; Fri, 27 Jan 1995 20:32:50 -0800 Received: from kaiwan.kaiwan.com (4@kaiwan.kaiwan.com [198.178.203.2]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id UAA06186 for ; Fri, 27 Jan 1995 20:32:43 -0800 Received: from exit.com (uucp@localhost) by kaiwan.kaiwan.com (8.6.9/8.6.5) with UUCP id UAA17226 for hackers@freefall.cdrom.com; Fri, 27 Jan 1995 20:32:30 -0800 *** KAIWAN Internet Access *** Received: (from frank@localhost) by exit.com (8.6.8/8.6.6) id UAA08851 for hackers@freefall.cdrom.com; Fri, 27 Jan 1995 20:32:15 -0800 From: Frank Mayhar Message-Id: <199501280432.UAA08851@exit.com> Subject: Re: Am I dreaming? To: jkh@FreeBSD.org (Jordan K. Hubbard) Date: Fri, 27 Jan 1995 20:31:10 -0800 (PST) In-Reply-To: <3196.791240166@time.cdrom.com> from "Jordan K. Hubbard" at Jan 27, 95 12:56:06 pm X-Mailer: ELM [version 2.4 PL23beta2] Content-Type: text Content-Length: 1282 Sender: hackers-owner@FreeBSD.org Precedence: bulk > However, I do feel compelled to note that the inability to do this kind > of thing easily only underscores the abominable evil that is the whole > UNIX filesystem paradigm (as if ioctl() wasn't enough to already convince > us of this! :-). You want the DMIG spec, the Data Management Interfaces Group's specification for filesystem hooks to be used by user processes. I mean, if you're going to do it, you may as well do it in a standard fashion. I have a copy of the 2.0 draft spec that I can place on wcarchive, if there's interest (it's 352k of gzipped postscript), and you can also find it via ftp on ftp://acsc.com/pub/dmig/v2.0. No, I'm not volunteering, I just don't have time, but I thought I would mention it. If you guys do go this way, I would suggest implementing the parts that would be immediately useful (i.e. synchronous namespace events), and saving the rest for another time. There are bits that would be more easily implemented, (although the scaffolding would have to be there early on). I seem to remember that an earlier draft also had optional and mandatory bits, as well, although that may well have changed by now. I may do part of this on my own time, if and when I have time for it. If I do, I'll contribute it. -- Frank Mayhar frank@exit.com From owner-freebsd-hackers Fri Jan 27 20:56:28 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id UAA06513 for hackers-outgoing; Fri, 27 Jan 1995 20:56:28 -0800 Received: from vmbb.cts.com (vmbb.cts.com [192.188.72.18]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id UAA06507 for ; Fri, 27 Jan 1995 20:56:26 -0800 Received: from io.cts.com by vmbb.cts.com with smtp (Smail3.1.28.1 #9) id m0rY5CV-0000HaC; Fri, 27 Jan 95 20:55 PST Received: (from root@localhost) by io.cts.com (8.6.9/8.6.9) id UAA07123; Fri, 27 Jan 1995 20:48:00 -0800 From: Morgan Davis Message-Id: <199501280448.UAA07123@io.cts.com> Subject: Re: shell trick? To: roberto@blaise.ibp.fr (Ollivier ROBERT) Date: Fri, 27 Jan 1995 20:47:58 -0800 (PST) Cc: dgy@seagull.rtd.com, freebsd-hackers@freefall.cdrom.com In-Reply-To: <9501271934.AA17198@blaise.ibp.fr> from "Ollivier ROBERT" at Jan 27, 95 08:34:11 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 752 Sender: hackers-owner@FreeBSD.org Precedence: bulk Ollivier ROBERT writes: > > > How can I, in a shell script, read lines from a file, expand any > > environment variables referenced therein and write results to another > > file? > > This not a real answer but you should really do this kind of things > in perl... Its build-in eval function is great for this. You could also do this with (ba)sh's eval statement. Something like this: read line < fromfile eval var=$line This is only good for grabbing input from the first line of text in a file. You could use sed to extract other lines in a similar manner. The variable var would hold the evaluated results from whatever was read into the line variable. Use echo to write the expanded stuff into other files (using > and >> as needed). From owner-freebsd-hackers Fri Jan 27 23:07:47 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id XAA09718 for hackers-outgoing; Fri, 27 Jan 1995 23:07:47 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id XAA09699; Fri, 27 Jan 1995 23:07:20 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id SAA22269; Sat, 28 Jan 1995 18:01:41 +1100 Date: Sat, 28 Jan 1995 18:01:41 +1100 From: Bruce Evans Message-Id: <199501280701.SAA22269@godzilla.zeta.org.au> To: dufault@hda.com, julian@tfs.com Subject: Re: SCSI device configuring.. (was scsi renames devices) Cc: freebsd-hackers@freefall.cdrom.com, freebsd-scsi@freefall.cdrom.com, hsu@fx7.cs.hut.fi Sender: hackers-owner@FreeBSD.org Precedence: bulk >there are several ways around the problem.. >1/ The NetBSD approach.. NetBSD have changed their config code almost entirely, >to use the same system as (I believe) BSDI.. wherever it came from, it allows Does config.new do this? >2/ the /DEVFS approach.. the kernel creates the devices purely as it finds them >and assignes names that are descriptive of WHERE it found them. >Needs devfs, and I've just scrapped my 3rd try at it.. devfs will change the problems for config and booting. Config will have have to output names instead of numbers. This should be slightly easier - it can just copy the names given in the input file. However, conventions such as the b partition being for swap may still have to be handled to support old config files. >3/ the /dev/scsi approach (aka the 'Peter (dufault) Principle' :) >looks promising but unfortunatly, doesn't allow vnode locking between >(say) /dev/rsd0d and /dev/scsi/dev3-lun0-part4 (for want of a better name). >because they are different vnodes.. The driver probably has to handle this anyway. Aliased devices should be easier to handle than overlapping devices (partitions) provided the driver knows about the aliases. However, I think supporting the old names is too hard. Bruce From owner-freebsd-hackers Fri Jan 27 23:33:36 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id XAA10205 for hackers-outgoing; Fri, 27 Jan 1995 23:33:36 -0800 Received: from rover.village.org (rover.village.org [198.137.146.49]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id XAA10199 for ; Fri, 27 Jan 1995 23:33:32 -0800 Received: (from imp@localhost) by rover.village.org (8.6.9/8.6.6) id RAA00149 for hackers@freebsd.org; Fri, 27 Jan 1995 17:36:56 -0700 Date: Fri, 27 Jan 1995 17:36:56 -0700 From: Warner Losh Message-Id: <199501280036.RAA00149@rover.village.org> To: hackers@FreeBSD.org Subject: New 2.0 system... Much improved install Sender: hackers-owner@FreeBSD.org Precedence: bulk Greetings I finally bit the bullet and upgraded to 2.0. I must admit that I was quite nervous at this prospect, given the amount of negative things I had seen. However, I was pleasantly surprised by the ease of the install procedure. I was able to get up and running with a minimum of hassle. The install procedure looks very nice, especially the disk partition and label stuff. I did notice a couple of things have likely been corrected since the 2.0 cdrom, but I thought I'd pass them along just in case they are not known. 1) My ethernet card isn't at the standard place. Since my old kernel saw it, I didn't even think to look into chaning its IO, etc. However, the install did prompt me for a hostname an so forth, but it seemed to throw this info away. It would have been nice if I could say "oh, dang, my ed0 interface is really and truly there, please pretend it is and write the config file." 2) It would be nice to be able to install packages from the install progam at the same time I'm installing the rest of the system. It would also be nice to be able to get the kernel source w/o having to get the entire system source. I don't have the disk space for the source now that I've moved Linux and NT onto my 1G disk. It would also be nice to be able to pick and choose my X server, rather than having them all installed (but maybe I did something wrong). It would also be nice to have the setup program convert the old Xconfig files that I had to new ones, but since I had done a newfs, that doesn't seem to practical. All in all this is *MUCH* improved over the 1.0R days, or even the 1.1.5R install. Looks a lot nicer. Oh, there was one last thing, I had to keep booting off of my floppy during the install since FreeBSD wasn't the "master" OS (first one on the disk), otherwise I came up in NT. It would be nice if there was a warning for this, as it took me a little bit of fiddling to get that right. No biggie, but would make the install nicer. Warner From owner-freebsd-hackers Fri Jan 27 23:57:46 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id XAA11111 for hackers-outgoing; Fri, 27 Jan 1995 23:57:46 -0800 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id XAA11105 for ; Fri, 27 Jan 1995 23:57:44 -0800 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id CAA03905; Sat, 28 Jan 1995 02:57:28 -0500 From: Peter Dufault Message-Id: <199501280757.CAA03905@hda.com> Subject: Re: SyQuest works with FreeBSD 2.0R ! To: wollman@halloran-eldar.lcs.mit.edu (Garrett Wollman) Date: Sat, 28 Jan 1995 02:57:28 -0500 (EST) Cc: terry@cs.weber.edu, hackers@FreeBSD.org In-Reply-To: <9501280017.AA12682@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at Jan 27, 95 07:17:42 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 689 Sender: hackers-owner@FreeBSD.org Precedence: bulk Garrett Wollman writes: > > Stupid question: > > Why would the host adapter know anything at all about LUNs? The "aic6360" code has to build up the SCSI phases brute force, including the IDENTIFY phase that has the target LUN in it. A quick look through it shows that it seems to do the right thing. Another possibility is that the Bernoulli is so old and crufty that it looks for the LUN in the CDB, but the driver appears to put it there too. -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 -- Formerly hd@world.std.com. E-mail problems? Tell hdslip@iii.net From owner-freebsd-hackers Sat Jan 28 00:41:09 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id AAA11568 for hackers-outgoing; Sat, 28 Jan 1995 00:41:09 -0800 Received: from vmbb.cts.com (vmbb.cts.com [192.188.72.18]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id AAA11561 for ; Sat, 28 Jan 1995 00:41:06 -0800 Received: from io.cts.com by vmbb.cts.com with smtp (Smail3.1.28.1 #9) id m0rY8iE-0000Y6C; Sat, 28 Jan 95 00:40 PST Received: (from root@localhost) by io.cts.com (8.6.9/8.6.9) id AAA07588; Sat, 28 Jan 1995 00:33:06 -0800 From: Morgan Davis Message-Id: <199501280833.AAA07588@io.cts.com> Subject: Re: pcd0?? To: jkh@freefall.cdrom.com (Jordan K. Hubbard) Date: Sat, 28 Jan 1995 00:33:05 -0800 (PST) Cc: hackers@FreeBSD.org In-Reply-To: <199501280430.UAA06157@freefall.cdrom.com> from "Jordan K. Hubbard" at Jan 27, 95 08:30:34 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 825 Sender: hackers-owner@FreeBSD.org Precedence: bulk Jordan K. Hubbard writes: > > >From files.i386: > > i386/isa/pcd.c optional pcd device-driver > > Would someone kindly explain what this is doing here? The referenced > file doesn't even exist! > > I would like to remove it and will do so in 24 hours if nobody pipes up. > It's also referenced in LINT, and this is simply deceptive of support > we currently do NOT offer! Might this be why I'm getting this error on linking the kernel from today's -current? loading kernel ioconf.o: Undefined symbol `_pasdriver' referenced from data segment *** Error code 1 Stop. I last supped on 1/12 and everything was cool. I was able to sup -current and 'make world' fine today. But trying to make my kernel (which hasn't changed in configuration since 1/12) gives the above error. Suggestions? From owner-freebsd-hackers Sat Jan 28 00:48:41 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id AAA11632 for hackers-outgoing; Sat, 28 Jan 1995 00:48:41 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id AAA11625; Sat, 28 Jan 1995 00:48:39 -0800 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id AAA24431; Sat, 28 Jan 1995 00:48:23 -0800 From: Poul-Henning Kamp Message-Id: <199501280848.AAA24431@ref.tfs.com> Subject: Re: pcd0?? To: root@io.cts.com (Morgan Davis) Date: Sat, 28 Jan 1995 00:48:23 -0800 (PST) Cc: jkh@freefall.cdrom.com, hackers@FreeBSD.org In-Reply-To: <199501280833.AAA07588@io.cts.com> from "Morgan Davis" at Jan 28, 95 00:33:05 am Content-Type: text Content-Length: 475 Sender: hackers-owner@FreeBSD.org Precedence: bulk > Might this be why I'm getting this error on linking the kernel from > today's -current? > > loading kernel > ioconf.o: Undefined symbol `_pasdriver' referenced from data segment > *** Error code 1 The pas driver died yesterday (RIP), so you need to "config" again. Remember to read the commit-mail if you are on -current... -- Poul-Henning Kamp TRW Financial Systems, Inc. FreeBSD has, until now, not one single time had an undetected error. :-) From owner-freebsd-hackers Sat Jan 28 01:04:56 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id BAA11873 for hackers-outgoing; Sat, 28 Jan 1995 01:04:56 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id BAA11867; Sat, 28 Jan 1995 01:04:42 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id TAA24423; Sat, 28 Jan 1995 19:59:54 +1100 Date: Sat, 28 Jan 1995 19:59:54 +1100 From: Bruce Evans Message-Id: <199501280859.TAA24423@godzilla.zeta.org.au> To: freebsd-current@freefall.cdrom.com, hackers@FreeBSD.org, rkw@dataplex.net Subject: Re: REMAKE WORLD Sender: hackers-owner@FreeBSD.org Precedence: bulk >1. The build procedure should run on any machine that meets certain minimal >specs. (Like maybe 1.1.5.1) Doing a build will in NO way affect the host >environment. Too hard for 1.1.5.1. Require 2.1. >2. If everything is up to date, a make will do nothing except scan the >tree. Nothing gets rebuilt unless it is out of date. I have parts of this for 2.0. For `make; make install; make; make install', the second make does nothing and the second install changes very few timestamps although it is reinstalls almost everything. This requires mainly not clobbering timestamps when installing unchanged files. Making the world is harder, and most of the dependencies on libc.a are bogus. Links are normally done to ${SHLIBDIR}/libc.so.2.0. These should be done to /usr/obj/lib/libc/libc.so.2.0, and the linkage is not supposed to depend on the library file, only on the library version. What is "nothing"? I'd like it to be nothing more than reading Makefiles and stat()ing files to get timestamps. No building temporary files. >4. The make procedure is not allowed to "touch" it's input tree. The source >tree can be read-only. The object tree can be read-only if up-to-date. >5. Multiple targets can co-exist at the same time. The entire process has a >floating root. No path is hard coded. This makes it hard to check out a single module outside of the source tree and build it. >6. Symbolic links are permitted. (This is a hard one because /../ does not >necessarily get you back where you were :-( ) This is a bit inconsistent with (4). I think requiring obj links in the source tree would be best. Bruce From owner-freebsd-hackers Sat Jan 28 01:32:10 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id BAA12497 for hackers-outgoing; Sat, 28 Jan 1995 01:32:10 -0800 Received: from crab.xinside.com (crab.xinside.com [199.120.247.2]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id BAA12491; Sat, 28 Jan 1995 01:32:02 -0800 Received: (jdc@localhost) by crab.xinside.com (8.6.8/8.6.5) id CAA16417; Sat, 28 Jan 1995 02:29:29 -0700 From: Jeremy Chatfield Message-Id: <199501280929.CAA16417@crab.xinside.com> Subject: Re: Am I dreaming? To: jkh@FreeBSD.org (Jordan K. Hubbard) Date: Sat, 28 Jan 1995 02:29:29 +0000 (MST) Cc: wollman@halloran-eldar.lcs.mit.edu, hackers@freefall.cdrom.com In-Reply-To: <3196.791240166@time.cdrom.com> from "Jordan K. Hubbard" at Jan 27, 95 12:56:06 pm Organization: X Inside Inc, P O Box 10774, Golden, CO 80401-0610, USA. Phone: +1(303)470-5302 Reply-To: jdc@crab.xinside.com X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 3805 Sender: hackers-owner@FreeBSD.org Precedence: bulk Jordan K. Hubbard writes: > >> I guess this all gets back to the whole `user mode translation of file names' > >> thing we were talking about awhile back. It's not the same as portals, > >> which require a given mount point to be traversed, but rather affects all > >> files who's names match some sort of selection criteria. The feature above > >> would be one very nice application for this. > > Actually, the more I think about it the more I realize that it > probably can't be made to work. Sure, you could put in a hook so that > a process could register itself with namei() [if the hook was NULL, > namei() would simply always skip over it] and get called via some > mechanism that would allow it to pre-massage the name and pass it back > (perhaps totally transformed) to namei() for further processing. For > most names, the process would simply pass it back unchanged, but for > the hairy ftp://.. stuff it would fetch the file and pass namei() back > the name of something in /tmp. The problem is, what does namei() do > while the process is talking to some server halfway around the world? > We certainly can't block in the kernel waiting or all the other users > on the system would vomit up their entrails, and a `wake me up when > you're done, please' mechanism would be a lot more work to implement. The automount daemon circumvents the same problem appearing for NFS. Life goes on while the automounter tracks down and mounts the required resource... It's been a while since I ran a network large enough to justify automounting, but I don't remember any system delays while the node was found and mounted. Would it be useful to consider what & how the automounter achieves its' effects? Note that I'm not advocating copying the automount daemon behavior directly; my previous experience was with a well known SVR4.2 implementation and I had to rescue many users from strange system behaviours when the daemon died, or when the user managed to delete the directory structure that propped up the daemon :-) Another way to tackle the problem would be to have another file system type, mounted on /ftp by convention, with the FQDN used as the next component. By making this as a file system in its' own right, you should be able to sidestep some of the nasty issues involved in handling the special file within existing file systems. The symlink in the original example would simply point to /ftp/freefall.cdrom.com/... rather than using the URL semantic. By pushing this handling towards user space, you can also allow the per-user .netrc govern the behaviour, make a move to a more network security oriented approach (.profile --> ftp://....? I think not!) and make centralised administration easier. Some consideration would have to be given to how to handle FTP login and init macros for daemons rather than real users, which would probably revolve around identifying the correct home directory for each system id, rather than having half share /root and others in places like /tmp. This mechanism would let you skip a namei(), unless an FQPN (Fully Qualified Path Name) is given. For example, 'ls /ftp' yields nothing (unless there is a current open connection?), but 'ls /ftp/wuarchive.wustl.edu/pub' results in a listing. The effect that you are trying to achieve is approximately the same as AFS, isn't it? Rather than define a whole new semantic, why not port AFS (he said, confident that *he*, at least, would not have time to contribute effort). Cheers, JeremyC. -- Jeremy Chatfield, +1(303)470-5302, FAX:+1(303)470-5513, email:jdc@xinside.com X Inside Inc, P O Box 10774, Golden, CO 80401-0610, USA. Commercial X Server - for more information please try these services http://www.xinside.com info@xinside.com ftp.xinside.com From owner-freebsd-hackers Sat Jan 28 02:18:01 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id CAA13390 for hackers-outgoing; Sat, 28 Jan 1995 02:18:01 -0800 Received: from isl.cf.ac.uk (isl-gate.elsy.cf.ac.uk [131.251.22.1]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id CAA13384; Sat, 28 Jan 1995 02:17:50 -0800 Received: (from paul@localhost) by isl.cf.ac.uk (8.6.9/8.6.9) id KAA27697; Sat, 28 Jan 1995 10:18:19 GMT From: Paul Richards Message-Id: <199501281018.KAA27697@isl.cf.ac.uk> Subject: Re: Am I dreaming? To: bakul@netcom.com (Bakul Shah) Date: Sat, 28 Jan 1995 10:18:19 +0000 (GMT) Cc: jkh@freefall.cdrom.com, hackers@freefall.cdrom.com In-Reply-To: <199501280116.RAA13132@netcom2.netcom.com> from "Bakul Shah" at Jan 27, 95 05:16:31 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 509 Sender: hackers-owner@FreeBSD.org Precedence: bulk In reply to Bakul Shah who said > > Wouldn't `Alex' do what you want? Here is a brief blurb > from an old net message by Jurgen Botz about alex: > That's the one. I've been puzzling since this thread started where I'd seen something like this, it was Alex. -- Paul Richards, FreeBSD core team member. Phone: +44 1222 874000 x6646 (work), +44 1222 457651 (home) Dept. Mechanical Engineering, University of Wales, College Cardiff. Internet: paul@FreeBSD.org, JANET(UK): RICHARDSDP@CARDIFF.AC.UK From owner-freebsd-hackers Sat Jan 28 03:13:12 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id DAA13856 for hackers-outgoing; Sat, 28 Jan 1995 03:13:12 -0800 Received: from UUCP-GW.CC.UH.EDU (root@UUCP-GW.CC.UH.EDU [129.7.1.11]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id DAA13850; Sat, 28 Jan 1995 03:13:05 -0800 Received: from Taronga.COM by UUCP-GW.CC.UH.EDU with UUCP id AA24164 (5.67a/IDA-1.5); Sat, 28 Jan 1995 05:04:08 -0600 Received: by bonkers.taronga.com (smail2.5p) id AA10258; 28 Jan 95 05:03:08 CST (Sat) Received: (from peter@localhost) by bonkers.taronga.com (8.6.8/8.6.6) id FAA10255; Sat, 28 Jan 1995 05:03:07 -0600 From: Peter da Silva Message-Id: <199501281103.FAA10255@bonkers.taronga.com> Subject: Re: Am I dreaming? To: wollman@halloran-eldar.lcs.mit.edu (Garrett Wollman) Date: Sat, 28 Jan 1995 05:03:07 -0600 (CST) Cc: jkh@freefall.cdrom.com, hackers@freefall.cdrom.com In-Reply-To: <9501272028.AA12182@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at Jan 27, 95 03:28:01 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 100 Sender: hackers-owner@FreeBSD.org Precedence: bulk > Gross! That's even more evil than variant symbolic links! I thought it *was* a variant symlink. From owner-freebsd-hackers Sat Jan 28 03:13:27 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id DAA13864 for hackers-outgoing; Sat, 28 Jan 1995 03:13:27 -0800 Received: from time.cdrom.com (time.cdrom.com [192.216.223.46]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id DAA13858; Sat, 28 Jan 1995 03:13:24 -0800 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.9/8.6.9) with SMTP id DAA22313; Sat, 28 Jan 1995 03:12:02 -0800 To: Morgan Davis cc: jkh@freefall.cdrom.com (Jordan K. Hubbard), hackers@FreeBSD.org Subject: Re: pcd0?? In-reply-to: Your message of "Sat, 28 Jan 95 00:33:05 PST." <199501280833.AAA07588@io.cts.com> Date: Sat, 28 Jan 1995 03:12:01 -0800 Message-ID: <22312.791291521@time.cdrom.com> From: "Jordan K. Hubbard" Sender: hackers-owner@FreeBSD.org Precedence: bulk No, actually that's probably a result of Poul-Henning's commit earlier. Jordan > Jordan K. Hubbard writes: > > > > >From files.i386: > > > > i386/isa/pcd.c optional pcd device-driver > > > > Would someone kindly explain what this is doing here? The referenced > > file doesn't even exist! > > > > I would like to remove it and will do so in 24 hours if nobody pipes up. > > It's also referenced in LINT, and this is simply deceptive of support > > we currently do NOT offer! > > Might this be why I'm getting this error on linking the kernel from > today's -current? > > loading kernel > ioconf.o: Undefined symbol `_pasdriver' referenced from data segment > *** Error code 1 > > Stop. > > > I last supped on 1/12 and everything was cool. I was able to sup > -current and 'make world' fine today. But trying to make my kernel > (which hasn't changed in configuration since 1/12) gives the above > error. > > Suggestions? From owner-freebsd-hackers Sat Jan 28 04:11:01 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id EAA14624 for hackers-outgoing; Sat, 28 Jan 1995 04:11:01 -0800 Received: from UUCP-GW.CC.UH.EDU (root@UUCP-GW.CC.UH.EDU [129.7.1.11]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id EAA14616 for ; Sat, 28 Jan 1995 04:10:56 -0800 Received: from Taronga.COM by UUCP-GW.CC.UH.EDU with UUCP id AA24413 (5.67a/IDA-1.5); Sat, 28 Jan 1995 05:39:53 -0600 Received: by bonkers.taronga.com (smail2.5p) id AA10366; 28 Jan 95 05:15:17 CST (Sat) Received: (from peter@localhost) by bonkers.taronga.com (8.6.8/8.6.6) id FAA10363; Sat, 28 Jan 1995 05:15:17 -0600 From: Peter da Silva Message-Id: <199501281115.FAA10363@bonkers.taronga.com> Subject: Re: Am I dreaming? To: jkh@FreeBSD.org (Jordan K. Hubbard) Date: Sat, 28 Jan 1995 05:15:17 -0600 (CST) Cc: wollman@halloran-eldar.lcs.mit.edu, hackers@freefall.cdrom.com In-Reply-To: <3196.791240166@time.cdrom.com> from "Jordan K. Hubbard" at Jan 27, 95 12:56:06 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 592 Sender: hackers-owner@FreeBSD.org Precedence: bulk > However, I do feel compelled to note that the inability to do this kind > of thing easily only underscores the abominable evil that is the whole > UNIX filesystem paradigm (as if ioctl() wasn't enough to already convince > us of this! :-). Huh? There's already an FTP file system out there. People have been using it. What's the name of it? Alex? Something like that? Just make your symlinks point to that... The UNIX file system paradigm isn't evil. IOCTL is just a hack to cover up for not properly implementing it. They finally did replace ioctl with file system operations in Plan 9. From owner-freebsd-hackers Sat Jan 28 04:16:21 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id EAA17257 for hackers-outgoing; Sat, 28 Jan 1995 04:16:21 -0800 Received: from dataplex.net (SHARK.DATAPLEX.NET [199.183.109.241]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id EAA17251 for ; Sat, 28 Jan 1995 04:16:19 -0800 Received: from [199.183.109.242] by dataplex.net with SMTP (MailShare 1.0b8); Sat, 28 Jan 1995 06:11:08 -0600 X-Sender: wacky@shark.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 28 Jan 1995 06:11:07 -0600 To: Bruce Evans From: rkw@dataplex.net (Richard Wackerbarth) Subject: Re: REMAKE WORLD Cc: hackers@FreeBSD.org Sender: hackers-owner@FreeBSD.org Precedence: bulk >>1. The build procedure should run on any machine that meets certain minimal >>specs. (Like maybe 1.1.5.1) Doing a build will in NO way affect the host >>environment. > >Too hard for 1.1.5.1. Require 2.1. Come now, 2.1 doesn't even exist. I can certainly set up a procedure that runs on a 2.0 system, and off hand, I don't see anything about 1.1 that precludes it. After all, what do we need? The ability to execute gcc, make, etc. There is nothing to say that these are the native versions. Remember, one of the goals is that we don't affect the running system. As a result, every reference MUST be to our own tree of {tools, sources, includes, libraries, objects, binaries, and installation} files. As long as we can compile the tools on a system, we can do it. I will make one concession. I will require the OS to support certain Unix commands and features. At this point, I don't know just what the minimal set is. I know MSDOS won't hack it because of file name problems, but I am not sure just how far back in Unix we need to go in order to run our tools. >>2. If everything is up to date, a make will do nothing except scan the >>tree. Nothing gets rebuilt unless it is out of date. > >I have parts of this for 2.0. For `make; make install; make; make >install', the second make does nothing and the second install changes >very few timestamps although it is reinstalls almost everything. Gim'me! Gim'me! Assuming that you are willing to colaborate, my task may not be quite as hard. >This requires mainly not clobbering timestamps when installing unchanged >files. Making the world is harder, and most of the dependencies on >libc.a are bogus. Libc.a should not change if "make" does it's job properly. After all, what is magic about building a library? The output file depends on the objects just like any other part of the chain. If the library is up to date, make does nothing. >Links are normally done to ${SHLIBDIR}/libc.so.2.0. >These should be done to /usr/obj/lib/libc/libc.so.2.0, and the linkage >is not supposed to depend on the library file, only on the library >version. So we add shared library "cookies" that get changed only with the version number. >What is "nothing"? I'd like it to be nothing more than reading Makefiles >and stat()ing files to get timestamps. No building temporary files. I'd like that, too. >>5. Multiple targets can co-exist at the same time. The entire process has a >>floating root. No path is hard coded. > >This makes it hard to check out a single module outside of the source >tree and build it. It may be hard, but I don't really think impossible. Basically, you float EVERYTHING off of {SRCDIR}, {DESTDIR} type elements. >>4. The make procedure is not allowed to "touch" it's input tree. The source >>tree can be read-only. The object tree can be read-only if up-to-date. >>6. Symbolic links are permitted. (This is a hard one because /../ does not >>necessarily get you back where you were :-( ) > >This is a bit inconsistent with (4). I think requiring obj links in the >source tree would be best. What is inconsistent? Obj links are not consistent with (5). ---- Richard Wackerbarth rkw@dataplex.net From owner-freebsd-hackers Sat Jan 28 04:45:22 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id EAA17590 for hackers-outgoing; Sat, 28 Jan 1995 04:45:22 -0800 Received: from mailhost.tue.nl (mailhost.tue.nl [131.155.2.5]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id EAA17584; Sat, 28 Jan 1995 04:45:20 -0800 Received: from asterix.urc.tue.nl (asterix.urc.tue.nl [131.155.5.10]) by mailhost.tue.nl (8.6.9/8.6.9) with SMTP id NAA04893; Sat, 28 Jan 1995 13:44:40 +0100 Received: (from wmbfmk@localhost) by asterix.urc.tue.nl (8.6.9/8.6.9) id MAA22443; Sat, 28 Jan 1995 12:44:39 GMT From: Marc van Kempen Message-Id: <199501281244.MAA22443@asterix.urc.tue.nl> Subject: Re: pcd0?? To: jkh@FreeBSD.org (Jordan K. Hubbard) Date: Sat, 28 Jan 1995 13:44:38 +0100 (MET) Cc: hackers@FreeBSD.org In-Reply-To: <22312.791291521@time.cdrom.com> from "Jordan K. Hubbard" at Jan 28, 95 03:12:01 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 595 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > Jordan K. Hubbard writes: > > > > > > >From files.i386: > > > > > > i386/isa/pcd.c optional pcd device-driver > > > > > > Would someone kindly explain what this is doing here? The referenced > > > file doesn't even exist! > > > > > > I would like to remove it and will do so in 24 hours if nobody pipes up. > > > It's also referenced in LINT, and this is simply deceptive of support > > > we currently do NOT offer! > > > I saw ATS was working on this on his machine 'bsd386.first.gmd.de', but the files haven't been touched since late December. Marc. From owner-freebsd-hackers Sat Jan 28 05:00:01 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id FAA17723 for hackers-outgoing; Sat, 28 Jan 1995 05:00:01 -0800 Received: from galactica.galactica.it (galactica.galactica.it [192.106.152.1]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id EAA17711 for ; Sat, 28 Jan 1995 04:59:55 -0800 Received: from galactic.UUCP (root@localhost) by galactica.galactica.it (8.6.9/8.6.9) with UUCP id NAA24774 for hackers@FreeBSD.org; Sat, 28 Jan 1995 13:45:52 +0100 To: hackers@FreeBSD.org Subject: /stand directory From: davide.tome'@galactica.it (DAVIDE TOME') Message-ID: <8A272AF.0001008C79.uuout@galactica.it> Date: Sat, 28 Jan 95 11:27:00 +0100 Organization: GALACTICA PROFESSIONAL COMMUNICATION - ++39-2-29.00.61.50 Reply-To: davide.tome'@galactica.it (DAVIDE TOME') X-Mailreader: PCBoard Version 15.21 X-Mailer: PCBoard/UUOUT Version 1.10 Sender: hackers-owner@FreeBSD.org Precedence: bulk Hi, What is the meaning of the /stand directory ??? After installation can it be romoved ???? (there are a lot of 1Mb size files inside it) Ciao Davide Dott. Davide Tome' ------------------------------------------------- Internet .....: davide.tome'@galactica.it Fido..........: 2:331/358 davide tome' Galactica BBS.: +39-2-29006058 (24H 24 lines r.a) Voce..........: +39-2-29006150 Fax...........: +39-2-29006153 ------------------------------------------------- From owner-freebsd-hackers Sat Jan 28 09:52:32 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id JAA03290 for hackers-outgoing; Sat, 28 Jan 1995 09:52:32 -0800 Received: from seagull.rtd.com (root@Seagull.rtd.com [198.102.68.2]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id JAA03284 for ; Sat, 28 Jan 1995 09:52:29 -0800 Received: (from dgy@localhost) by seagull.rtd.com (8.6.9/8.6.9.1) id KAA22968 for freebsd-hackers@freefall.cdrom.com; Sat, 28 Jan 1995 10:52:13 -0700 From: Don Yuniskis Message-Id: <199501281752.KAA22968@seagull.rtd.com> Subject: RCS mod? To: freebsd-hackers@freefall.cdrom.com (FreeBSD hackers) Date: Sat, 28 Jan 1995 10:52:12 -0700 (MST) X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 241 Sender: hackers-owner@FreeBSD.org Precedence: bulk Greetings! In light of the use of the ".pl" suffix for perl scripts, should someone commit a change to RCS to redefine the comment character appropriately? Or, is ".pl" not quite as universally recognized in this regard... Thx, --don From owner-freebsd-hackers Sat Jan 28 09:54:57 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id JAA03423 for hackers-outgoing; Sat, 28 Jan 1995 09:54:57 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id JAA03417 for ; Sat, 28 Jan 1995 09:54:56 -0800 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id JAA26050; Sat, 28 Jan 1995 09:54:31 -0800 From: Poul-Henning Kamp Message-Id: <199501281754.JAA26050@ref.tfs.com> Subject: Re: /stand directory To: davide.tome'@galactica.it Date: Sat, 28 Jan 1995 09:54:31 -0800 (PST) Cc: hackers@FreeBSD.org In-Reply-To: <8A272AF.0001008C79.uuout@galactica.it> from "DAVIDE TOME'" at Jan 28, 95 11:27:00 am Content-Type: text Content-Length: 487 Sender: hackers-owner@FreeBSD.org Precedence: bulk > Hi, > > What is the meaning of the /stand directory ??? Some tools which can or cannot be handy to have around in case of major trouble. > After installation can it be romoved ???? (there are a lot of 1Mb size > files inside it) Yes you can remove it. It doesn't take that much space though, it's only few files with many links to them. -- Poul-Henning Kamp TRW Financial Systems, Inc. FreeBSD has, until now, not one single time had an undetected error. :-) From owner-freebsd-hackers Sat Jan 28 10:20:22 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id KAA05512 for hackers-outgoing; Sat, 28 Jan 1995 10:20:22 -0800 Received: from squid.umd.edu (squid.umd.edu [129.2.40.6]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id KAA05494; Sat, 28 Jan 1995 10:20:17 -0800 Received: by squid.umd.edu (5.65/Ultrix3.0-C) id AA01957; Sat, 28 Jan 1995 13:27:24 -0500 From: fcawth@squid.umd.edu (Fred Cawthorne) Message-Id: <9501281827.AA01957@squid.umd.edu> Subject: Re: >1024 cyl IDE drive To: jkh@FreeBSD.org (Jordan K. Hubbard) Date: Sat, 28 Jan 95 13:27:24 EST Cc: hoppy@appsmiths.com, hackers@FreeBSD.org In-Reply-To: <26952.791229051@time.cdrom.com>; from "Jordan K. Hubbard" at Jan 27, 95 9:50 am X-Mailer: ELM [version 2.3 PL11] Sender: hackers-owner@FreeBSD.org Precedence: bulk > > You're saying that these bootblock-remapping drives fall over kicking > when you install the boot manager? Aieee! I can't say we weren't warned > about this.. Or does this not have anything to do with the boot block? > > Jordan > Ummm... Why can't you just rewrite the MBR with fdisk or something?? I just installed a 1 gig Western Digital drive, and indeed Ontrack Disk manager does write some stuff into the MBR... The bios has the real parameters in it, so I would guess if this boot code wasn't there, you could just use the real ones with the usual >1024 cyl. precautions. I didn't check if the translator thingie was installed on the drive right out of the package, but I would guess it wasn't. If you install a small dos partition, and then try to install FreeBSD, then I would imagine it would choke when the MBR is overwritten by the boot selector... ): There should be a section in the install notes about these drives.. Fred. From owner-freebsd-hackers Sat Jan 28 10:28:39 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id KAA06214 for hackers-outgoing; Sat, 28 Jan 1995 10:28:39 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id KAA06208 for ; Sat, 28 Jan 1995 10:28:37 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA07320; Sat, 28 Jan 95 11:22:06 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9501281822.AA07320@cs.weber.edu> Subject: Re: SyQuest works with FreeBSD 2.0R ! To: julian@tfs.com (Julian Elischer) Date: Sat, 28 Jan 95 11:22:05 MST Cc: peter@bonkers.taronga.com, dufault@hda.com, john@pyromania.apana.org.au, hackers@FreeBSD.org In-Reply-To: from "Julian Elischer" at Jan 27, 95 11:26:34 am X-Mailer: ELM [version 2.4dev PL52] Sender: hackers-owner@FreeBSD.org Precedence: bulk > > The real solution to removable media is to put some sort of ident in the > > disklabel (including time and system ID) and track that. If you have a > > mounted filesystem and get a UNIT ATTENTION then you can see whether > > it's been swapped or not. > > At the moment, a unit-attention invalidates all accesses, until > all have been closed. (the device becomes 'locked'. > when the reference count has gone down to 0, the lock is released.. With respect, by the time you get a unit attention, it's too late to flush your in core buffers that haven't been written yet, unless you can throw the bits at the disk as it's walking down the hallway. Asking for the disk *back* seems reasonable to me. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sat Jan 28 10:30:44 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id KAA06465 for hackers-outgoing; Sat, 28 Jan 1995 10:30:44 -0800 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id KAA06435 for ; Sat, 28 Jan 1995 10:30:17 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA08892; Sat, 28 Jan 1995 19:31:31 +0100 Received: by sax.sax.de (8.6.9/8.6.9-s1) with UUCP id TAA23283 for freebsd-hackers@freebsd.org; Sat, 28 Jan 1995 19:31:30 +0100 Received: by bonnie.tcd-dresden.de (8.6.8/8.6.6) id TAA09150; Sat, 28 Jan 1995 19:11:07 +0100 From: j@uriah.sax.de (J Wunsch) Message-Id: <199501281811.TAA09150@bonnie.tcd-dresden.de> Subject: Re: SyQuest works with FreeBSD 2.0R ! To: freebsd-hackers@FreeBSD.org (FreeBSD hackers) Date: Sat, 28 Jan 1995 19:11:06 +0100 (MET) In-Reply-To: <199501271150.GAA07921@hda.com> from "Peter Dufault" at Jan 27, 95 06:50:47 am X-Phone: +49-351-8141 137 Reply-To: joerg_wunsch@uriah.sax.de X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 786 Sender: hackers-owner@FreeBSD.org Precedence: bulk As Peter Dufault wrote: | | I'd like a description of what happens when you unmount a file system, | change the media, and try to mount a filesystem on a removable drive, | including dmesg output. Sorry, no dmesg handy. :) The first attempt fails accompanied by the syslog message for the UNIT ATTN. The second mount attempt will succeed though. Btw., there's another annoying thing besides the UA: a message indicating ``disk does not have an MBR'' is logged, even if i'm using /dev/rsd*d -- where it does not make any sense to insist on having an MBR at all. -- cheers, J"org work: --- no longer --- private: joerg_wunsch@uriah.sax.de Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sat Jan 28 10:41:59 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id KAA07309 for hackers-outgoing; Sat, 28 Jan 1995 10:41:59 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id KAA07303; Sat, 28 Jan 1995 10:41:57 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA07357; Sat, 28 Jan 95 11:31:02 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9501281831.AA07357@cs.weber.edu> Subject: Re: >1024 cyl IDE drive To: bde@zeta.org.au (Bruce Evans) Date: Sat, 28 Jan 95 11:31:00 MST Cc: jkh@FreeBSD.org, hackers@FreeBSD.org, hoppy@appsmiths.com In-Reply-To: <199501280256.NAA18071@godzilla.zeta.org.au> from "Bruce Evans" at Jan 28, 95 01:56:35 pm X-Mailer: ELM [version 2.4dev PL52] Sender: hackers-owner@FreeBSD.org Precedence: bulk > Someone told us long before that in the enclosed mail to freebsd-bugs. > I thought it was well known to boot block hackers. [ ... ] > Bruce [ ... ] > This URGENT bug report describes a possible disk partitioning problem > that might potentially trash large numbers of users hard disks. Please > ensure it is examined BEFORE CD-ROMs are mastered. It may well be a > false alarm but I think somebody who knows more about this than I > do better take a look. > > The problem is that disk geometry remapping is not only performed > by the IDE controller or BIOS but also on many machines by special > boot programs in the MBR sector which might appear to be the same > as a BIOS remapping to FreeBSD utilities, but unlike a BIOS > remapping would disappear when the MBR is re-written unless special > precautions, not mentioned in the INSTALL file, are taken. THIS IS THE ARTICLE I HAVE BEEN REFERRING TO BUT UNABLE TO FIND! THANK YOU! Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sat Jan 28 10:42:52 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id KAA07384 for hackers-outgoing; Sat, 28 Jan 1995 10:42:52 -0800 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id KAA07373 for ; Sat, 28 Jan 1995 10:42:50 -0800 Received: by halloran-eldar.lcs.mit.edu; id AA13640; Sat, 28 Jan 1995 13:42:35 -0500 Date: Sat, 28 Jan 1995 13:42:35 -0500 From: Garrett Wollman Message-Id: <9501281842.AA13640@halloran-eldar.lcs.mit.edu> To: Poul-Henning Kamp Cc: freebsd-hackers@FreeBSD.org Subject: Re: Help with SCSI development (fwd) In-Reply-To: <199501280101.RAA22845@ref.tfs.com> References: <199501272249.RAA09638@hda.com> <199501280101.RAA22845@ref.tfs.com> Sender: hackers-owner@FreeBSD.org Precedence: bulk < said: > What I meant was, striped disks are only one subset of "virtual disks", > mirrors, raid# and so on come to mind too. > Make it general. ...and it will probably never happen. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-hackers Sat Jan 28 11:13:07 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id LAA09618 for hackers-outgoing; Sat, 28 Jan 1995 11:13:07 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id LAA09608; Sat, 28 Jan 1995 11:13:05 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA07476; Sat, 28 Jan 95 12:06:56 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9501281906.AA07476@cs.weber.edu> Subject: Re: >1024 cyl IDE drive To: fcawth@squid.umd.edu (Fred Cawthorne) Date: Sat, 28 Jan 95 12:06:55 MST Cc: jkh@FreeBSD.org, hoppy@appsmiths.com, hackers@FreeBSD.org In-Reply-To: <9501281827.AA01957@squid.umd.edu> from "Fred Cawthorne" at Jan 28, 95 01:27:24 pm X-Mailer: ELM [version 2.4dev PL52] Sender: hackers-owner@FreeBSD.org Precedence: bulk > > You're saying that these bootblock-remapping drives fall over kicking > > when you install the boot manager? Aieee! I can't say we weren't warned > > about this.. Or does this not have anything to do with the boot block? > > > > Jordan > > > Ummm... Why can't you just rewrite the MBR with fdisk or something?? > I just installed a 1 gig Western Digital drive, and indeed Ontrack Disk > manager does write some stuff into the MBR... The bios has the real > parameters in it, so I would guess if this boot code wasn't there, you > could just use the real ones with the usual >1024 cyl. precautions. > I didn't check if the translator thingie was installed on the drive > right out of the package, but I would guess it wasn't. > If you install a small dos partition, and then try to install FreeBSD, > then I would imagine it would choke when the MBR is overwritten by the > boot selector... ): > There should be a section in the install notes about these drives.. What do you do about the factory installed Windows and other software on the disk already, that depends on the geometry staying put? Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sat Jan 28 13:51:33 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id NAA18290 for hackers-outgoing; Sat, 28 Jan 1995 13:51:33 -0800 Received: from squid.umd.edu (squid.umd.edu [129.2.40.6]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id NAA18284; Sat, 28 Jan 1995 13:51:29 -0800 Received: by squid.umd.edu (5.65/Ultrix3.0-C) id AA02296; Sat, 28 Jan 1995 16:58:33 -0500 From: fcawth@squid.umd.edu (Fred Cawthorne) Message-Id: <9501282158.AA02296@squid.umd.edu> Subject: Re: >1024 cyl IDE drive To: terry@cs.weber.edu (Terry Lambert) Date: Sat, 28 Jan 95 16:58:33 EST Cc: jkh@FreeBSD.org, hoppy@appsmiths.com, hackers@FreeBSD.org In-Reply-To: <9501281906.AA07476@cs.weber.edu>; from "Terry Lambert" at Jan 28, 95 12:06 pm X-Mailer: ELM [version 2.3 PL11] Sender: hackers-owner@FreeBSD.org Precedence: bulk > > Ummm... Why can't you just rewrite the MBR with fdisk or something?? > > > What do you do about the factory installed Windows and other software > on the disk already, that depends on the geometry staying put? > > I guess then we're out of luck... I just noticed a message from someone else about the # of heads getting translated to > 16... I think this is what I ran into as well. A re-install of the dos stuff must be done in this case, I guess. (Or just leave it out completely (: ) Perhaps someone could make the wd driver use translations with >16 heads?? Is it possible to figure out how the bios/MBR extender is translating the disk?? Am I remembering incorrectly, or do some DRIVES actually do this >16 head thing too? About using pre-existing software... Do people usually use some utility to shrink the partition with the pre-installed software, then install FreeBSD?? Also, about the MBR based translation schemes... This will break when people boot a dos floppy and try to use the hard drive, right??? (I'll have to try it on that machine I just put the 1gig drive on...) Fred. From owner-freebsd-hackers Sat Jan 28 14:04:37 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id OAA18896 for hackers-outgoing; Sat, 28 Jan 1995 14:04:37 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id OAA18890; Sat, 28 Jan 1995 14:04:36 -0800 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id OAA26907; Sat, 28 Jan 1995 14:04:22 -0800 From: Poul-Henning Kamp Message-Id: <199501282204.OAA26907@ref.tfs.com> Subject: Re: >1024 cyl IDE drive To: fcawth@squid.umd.edu (Fred Cawthorne) Date: Sat, 28 Jan 1995 14:04:17 -0800 (PST) Cc: terry@cs.weber.edu, jkh@FreeBSD.org, hoppy@appsmiths.com, hackers@FreeBSD.org In-Reply-To: <9501282158.AA02296@squid.umd.edu> from "Fred Cawthorne" at Jan 28, 95 04:58:33 pm Content-Type: text Content-Length: 923 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > > Ummm... Why can't you just rewrite the MBR with fdisk or something?? > > > > > > What do you do about the factory installed Windows and other software > > on the disk already, that depends on the geometry staying put? > > > > > I guess then we're out of luck... I just noticed a message from Listen guys, you are way out on a tangent. There is >one< place where we need to care about the geometry we use: The boot-block. We can use any geometry we like in the kernel, as long as we have our partition boundaries the same places. This config will work just fine, the trick is to >uncouple< our devicedrivers from the bios/mbr view of things. I don't have the code to do this right now, but I belive I know what it takes to do it... And yes I'll try before 2.1. -- Poul-Henning Kamp TRW Financial Systems, Inc. FreeBSD has, until now, not one single time had an undetected error. :-) From owner-freebsd-hackers Sat Jan 28 14:07:36 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id OAA19056 for hackers-outgoing; Sat, 28 Jan 1995 14:07:36 -0800 Received: from anvil.appsmiths.com (appsmiths.sccsi.com [198.65.134.98]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id OAA19043 for ; Sat, 28 Jan 1995 14:07:31 -0800 Received: (from hoppy@localhost) by anvil.appsmiths.com (8.6.8/8.6.6) id QAA05213 for hackers@freeBSD.org; Sat, 28 Jan 1995 16:06:58 -0600 From: "Clay D. Hopperdietzel" Message-Id: <199501282206.QAA05213@anvil.appsmiths.com> Subject: Re: >1024 cyl IDE drive To: hackers@FreeBSD.org Date: Sat, 28 Jan 1995 16:06:58 -0600 (CST) In-Reply-To: <9501281827.AA01957@squid.umd.edu> from "Fred Cawthorne" at Jan 28, 95 01:27:05 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 4854 Sender: hackers-owner@FreeBSD.org Precedence: bulk :: Ummm... Why can't you just rewrite the MBR with fdisk or something?? :: I just installed a 1 gig Western Digital drive, and indeed Ontrack Disk :: manager does write some stuff into the MBR... The bios has the real :: parameters in it, so I would guess if this boot code wasn't there, you :: could just use the real ones with the usual >1024 cyl. precautions. :: I didn't check if the translator thingie was installed on the drive :: right out of the package, but I would guess it wasn't. :: If you install a small dos partition, and then try to install FreeBSD, :: then I would imagine it would choke when the MBR is overwritten by the :: boot selector... ): :: There should be a section in the install notes about these drives.. :: :: Fred. :: :: Since I had things apart already, I decided to have a little sick phun messing with this thing and see what would happen if I played dumb installer (not much of a stretch for me, actually ;>). Maybe some of this can be useful for the install notes/documentation project somehow. The software that I have is called EZ-Drive, by Microhouse Intl. I guess the On-ramp stuff might be another species. I installed EZD, selected 2 partitions (telling it the size was not an option). It blew goop out on the drive, copied some system files, etc. Reboot. The EZD banner now comes up. Boots from HD. Run FDISK. I have a 410M primary dos, and a ~410M extended dos with one drive defined. I don't like this. I use fdisk to delete the extended dos partition, give myself a 120 MB primary dos partition (I presume as the D.I. that I now have 600MB for FreeBSD). I fill it up and play with it, and all seems well. Just to be a jerk, I do a fdisk /MBR to see if I can scare EZD away. When I reboot its still there. (perhaps its not the MBR its messing with)? Onto FreeBSD install. I try using the (EZD floppy boot-o-matic) to boot the FreeBSD installation floppy (the ctrl-key hold trick). The FreeBSD floppy will not boot (just spins forever). Ok, I'll boot without EZD. That works. Install comes up. I get to the fdisk part of Install. When I look, I see that it thinks that there is a bootable partition 0, of unknown type, from (0,0,1) to (749,7,17). Also partition 2, (413,0,1) to (824,31,63), also unknown. Huh? Either this is some remanents of the *origional* 50/50 split that the EZD installer did, or FreeBSD fdisk can't cope without the mapper, or this turkey moved where the fdisk stuff lives. The geometry reported was wrong too. In fact, I went through this a couple of times, and I saw 2 different reports, total blocks constant, adjust #heads, #cyls inversely w.r.t each other. Ok, while I'm here I'll write the manager and the MBR from FreeBSD fdisk. Splat! I reboot. C drive now unbootable -- big surprise. Use DOS fdisk again. Shows 50/50 split. Okay, that one's toast. ------ Now I'll forget about the mapper. I boot from floppy, and go to fdisk the drive (without EZD). Fdisk seems to think its a 504MB drive, which is close to the proportion of (1024/1652)=(X/820). Fdisk has enough brains to not try to let the partition extend beyond c=1023. I make a small dos partion as above, and go for the FreeBSD install once again. No problems. Everything seems fine. ------ The other way I setup this drive was as wd1 in FreeBSD, and used the whole thing that way. Obviously no boot shennanigans here. ------- As far as the installation notes are concerned, what I guess I learned from this excercise is: 1 You will *not* run EZD and FreeBSD together, unless you do some very sick and creative things to boot FreeBSD using something other than the boot manager which comes with the install. The FreeBSD boot manager and the mapper would need to sit in the same chair on the C: Drive. 2 Because of 1, you will not get a DOS partition > 1024 cylinders to exist on your system on either IDE drive. 3 If you have EZD, you should remove it before running FreeBSD. When you remove it, you are going to roast any partitions which are already there. 4 There is a caveat surrounding where the large disk is .vs. where the mapper goes. I could imagine a configuration where the C drive was < 1024 cyls, and the D drive was > 1024 cyls. The mapper will still land on the C drive, just to map the D drive. Assuming exception from #2 above based in this is an error. 4 If you are trying to maximize DOS disk space on IDE disk(s), you would do so by laying out your/both IDE drive(s) such that the DOS partitions begin on Cylinder 0, and end on Cylinder 1023. DOS FDISK will prevent you from exceeding cylinder 1023 (at least my version did). 5 FreeBSD doesn't give a good hoot about any of this brain-damage. It'll use the disk just fine, no matter how you configure its partition. ---- an' that's all I got ta say 'bout dat. From owner-freebsd-hackers Sat Jan 28 14:40:41 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id OAA21056 for hackers-outgoing; Sat, 28 Jan 1995 14:40:41 -0800 Received: from UUCP-GW.CC.UH.EDU (root@UUCP-GW.CC.UH.EDU [129.7.1.11]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id OAA21050 for ; Sat, 28 Jan 1995 14:40:31 -0800 Received: from Taronga.COM by UUCP-GW.CC.UH.EDU with UUCP id AA28969 (5.67a/IDA-1.5 for freebsd.org!hackers); Sat, 28 Jan 1995 16:31:55 -0600 Received: by bonkers.taronga.com (smail2.5p) id AA27799; 28 Jan 95 16:17:55 CST (Sat) Received: from localhost (localhost [127.0.0.1]) by bonkers.taronga.com (8.6.8/8.6.6) with SMTP id QAA27795 for ; Sat, 28 Jan 1995 16:17:54 -0600 Message-Id: <199501282217.QAA27795@bonkers.taronga.com> X-Authentication-Warning: bonkers.taronga.com: Host localhost didn't use HELO protocol To: hackers@FreeBSD.org Subject: Alex X-Mailer: exmh version 1.4.1 7/21/94 Date: Sat, 28 Jan 1995 16:17:46 -0600 From: Peter da Silva Sender: hackers-owner@FreeBSD.org Precedence: bulk All the discussion about FTP file systems has gotten me to get off my duff and try and install Alex on my box. It's not going well. It looks like it's actually trying to get the files (I get a lot of modem activity) but then it turns around and gives me a stale NFS file handle. Looking at the log files it looks like it's timing out on the open and punting, then when I try to access the same file again it sees part of the information there and blows out. Has anyone got this working under FreeBSD? It's got some ifdefs for NetBSD. From owner-freebsd-hackers Sat Jan 28 18:09:05 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id SAA00378 for hackers-outgoing; Sat, 28 Jan 1995 18:09:05 -0800 Received: from prosun.first.gmd.de (prosun.first.gmd.de [192.35.150.136]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id SAA00372 for ; Sat, 28 Jan 1995 18:09:02 -0800 Received: from g386bsd.first.gmd.de by prosun.first.gmd.de (4.1/SMI-4.1) id AA06967; Sun, 29 Jan 95 03:08:48 +0100 Received: by g386bsd.first.gmd.de (DAA01561); Sun, 29 Jan 1995 03:10:02 +0100 From: Andreas Schulz Message-Id: <199501290210.DAA01561@g386bsd.first.gmd.de> Subject: Re: pcd0?? To: jkh@freefall.cdrom.com (Jordan K. Hubbard) Date: Sun, 29 Jan 1995 03:10:02 +0059 (MET) Cc: hackers@FreeBSD.org In-Reply-To: <199501280430.UAA06157@freefall.cdrom.com> from "Jordan K. Hubbard" at Jan 27, 95 08:30:34 pm X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1046 Sender: hackers-owner@FreeBSD.org Precedence: bulk > i386/isa/pcd.c optional pcd device-driver > > Would someone kindly explain what this is doing here? The referenced > file doesn't even exist! > > But I've mailed Andreas Schulz 3 times about this and never received > an answer, so I can only presume that his mail is either broken or he's > dead. The scd driver never existed either, at least not until about > 5 minutes ago! I have absolutely no idea what Andreas had in mind, > and he's not talking, so.... Sorry, i have not seen the mails from you, or only one other some hours ago in an attempt to get my mailbox smaller :-(. Something around ~1000 mails. Remove it, i have in the moment so many bugs seen in FreeBSD that waits for fixing, that i won't commit or write a new driver. And i only found time to work for FreeBSD on the weekend in the moment. ATS ( ats@first.gmd.de or ats@cs.tu-berlin.de ) Andreas Schulz GMD-FIRST 12489 Berlin-Adlershof Rudower Chaussee 5 Gebaeude 13.7 Tel: +49-30-6392-1856/+49-177-2134745 Germany/Europe