From owner-freebsd-bugs Sun Jun 11 02:51:52 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA07962 for bugs-outgoing; Sun, 11 Jun 1995 02:51:52 -0700 Received: from cycle.Stanford.EDU (hlew@cycle.Stanford.EDU [36.159.0.10]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id CAA07956 for ; Sun, 11 Jun 1995 02:51:50 -0700 Received: by cycle.Stanford.EDU; id AA03124; Sun, 11 Jun 1995 02:51:49 -0700 Date: Sun, 11 Jun 1995 02:51:49 -0700 (PDT) From: Howard Lew To: bugs@FreeBSD.org Subject: 2.05 Release Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@FreeBSD.org Precedence: bulk I just ftped the 2.05 release and tried the install, and the installation process went well. But when I rebooted, the system would not boot up. Here's the system I tested it on: 386DX-40, 387 Cyrix MPU, 8MB RAM, 850MB (wd0) with Ontrack DM, and 540MB (wd1). The 850MB has DOS with dynamic drive overlay from Ontrack DM. I was planning on installing 2.05R on the 540MB Conner (entire disk). So after reset, it tries to boot up. I see the usual Ontrack DM overlay stuff, and then it says to press space for floppy boot. It never asks for F1-Disk 1 or F5-Disk 2. (Hmmm... This is strange because the SNAP releases didn't seem to have this boot selection problem. That boot manager seemed to always work fine). If I insert my 2.05 boot.flp disk, and enter hd(1,a)/kernel, it starts booting from wd1. And everything looks good until it finishes probing npx (no immediate problem after the probe). Then it tries probing the PCI stuff. (Yes it really probes for PCI stuff on my 386), and after it finishes the probe, it says: panic: cannot mount root syncing disks... done Automatic reboot in 15 seconds - press a key on the console to abort ----------------------------------------------------------- I redid the installation several times, and here are some additional observations: * If disabled the cache on my 386 motherboard and also disabled the 387, the system no longer probes for the PCI stuff... But then panics with the same message after the NPX probe. * The system panics regardless of whether or not I disable the NPX probe. * I tried disabling practically all the devices except the floppy drive, hard drives, lpt0, and sio1 with no effect -- still panics. * If I go through the installation program and finish the installation, I can use ALT-F4 to see everything on my wd1 drive. There appears to be no problems mounting partions from wd1, but it just can't do it from the hard disk kernel. * The boot.flp kernel does not seem to panic (but then again it is mounting root from mfs). * If I use Ontrack DM 6.03a and set the DOS partition active (I don't know why it became inactive), the system prompts for F1-Disk 1 and F5-Disk 2. But at that prompt, if I choose F1, I get DOS. And if I choose F5, I also get DOS (so they are still booting from wd0 which is my DOS drive). * In the installation... If I choose wd1 and do the partition, and then do the disklabel to mount the partitions, I never see the R flag as mentioned in the help info for Partitions. The CA>= flags do appear, but I never see the R flag appear. Could this be the cause of the problems? * The time zone setting doesn't seem to work (maybe old news sorry). Well, sorry this is kind of out of order. Any help is greatly appreciated. I really would like to get this 2.05R system humming... Thanks in advance for any help. --------------- Some good stuff I noticed fixed: * Help info is there * Many install bugs gone * PPP over a 115200 serial cable link never hangs anymore * no errors in bin extractions -= Howard =- From owner-freebsd-bugs Sun Jun 11 12:39:48 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA17049 for bugs-outgoing; Sun, 11 Jun 1995 12:39:48 -0700 Received: from clark.net (rwatson@clark.net [168.143.0.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA17042 for ; Sun, 11 Jun 1995 12:39:47 -0700 Received: (rwatson@localhost) by clark.net (8.6.12/8.6.5) id PAA21682; Sun, 11 Jun 1995 15:39:44 -0400 Date: Sun, 11 Jun 1995 15:39:44 -0400 (EDT) From: Robert Watson To: bugs@FreeBSD.org Subject: (fwd) 2.0.5R -- boot failure on inst floppy (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@FreeBSD.org Precedence: bulk I posted this to comp.unix.bsd.freebsd.misc, but am now mailing it to you also. Robert Watson rwatson@sidwell.edu http://www.sidwell.edu/~rwatson/ The goal of science is to build better mousetraps. The goal of nature is to build better mice. ---------- Forwarded message ---------- Date: Sun, 11 Jun 1995 15:33:29 -0400 From: Robert Watson To: rwatson@clark.net Newgroups: comp.unix.bsd.freebsd.misc Subject: (fwd) 2.0.5R -- boot failure on inst floppy Newsgroups: comp.unix.bsd.freebsd.misc Path: nih-csl!rwatson From: rwatson@nih.gov (Robert Watson) Subject: 2.0.5R -- boot failure on inst floppy Message-ID: <1995Jun11.193433.22255@alw.nih.gov> Sender: postman@alw.nih.gov (AMDS Postmaster) Nntp-Posting-Host: kronos.nchgr.nih.gov Organization: National Institutes of Health X-Newsreader: TIN [version 1.2 PL2] Date: Sun, 11 Jun 1995 19:34:33 GMT I just ftp'd the installation floppy (boot.flp) and created the disk on a 3.5" disk drive (a:). I used essentially the same method as for 2.0, which worked fine. Unfortunately, when I begin the boot process, I get this far: Booting fd(0,a)/kernel @ 0x300000 text=0x100000 data=0x0 bss=0xa00 symbols=[+0x600+0x4+0x258+0x4+0x1d9] total=0x401439 entry point=0x300000 And then the system freezes with the floppy disk light on. Keyboard toggles (caps lock) don't change the lights. I'm working with a 386sx20 with 4 megs of ram, IDE (generic) controller w/2 HD's, 3 serial ports (2x16550 and one 8250, IRQ's 3, 4, 5) SMC Ultra Elite (irq 2) SBPro (irq 10). I'm getting the 2.0 floppy again just to make sure it's not my system failing to boot, but I've been running DOS/Windows fine for years on this system.. -- Robert Watson rwatson@sidwell.edu http://www.sidwell.edu/~rwatson/ The goal of science is to build better mousetraps. The goal of nature is to build better mice. -- Robert Watson rwatson@sidwell.edu http://www.sidwell.edu/~rwatson/ The goal of science is to build better mousetraps. The goal of nature is to build better mice. From owner-freebsd-bugs Sun Jun 11 19:40:03 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA16000 for bugs-outgoing; Sun, 11 Jun 1995 19:40:03 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA15991 ; Sun, 11 Jun 1995 19:40:02 -0700 Date: Sun, 11 Jun 1995 19:40:02 -0700 Message-Id: <199506120240.TAA15991@freefall.cdrom.com> From: Charles Henrich Reply-To: Charles Henrich To: freebsd-bugs Subject: bin/505: LINEMODE causes problems with some telnetd clients + fix. In-Reply-To: Your message of Sun, 11 Jun 1995 22:34:14 -0400 <199506120234.WAA05116@crh.cl.msu.edu> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 505 >Category: bin >Synopsis: LINEMODE causes problems with some telnetd clients + fix. >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Jun 11 19:40:01 1995 >Originator: Charles Henrich >Organization: Michigan State U. >Release: FreeBSD 2.0-BUILT-19950603 i386 >Environment: FreeBSD 2.0.5-R >Description: The final negotiation of DO_BINARY in the LINEMODE portion of the telnetd code causes some clients that do not support linemode to mis-interpret the return key (i.e. double returns). >How-To-Repeat: Use FTP Software PCTCP or NCSA Telnet and telnet to a freebsd box. >Fix: *** termstat.c.orig Mon Dec 21 08:09:29 1987 --- termstat.c Mon Dec 21 08:18:20 1987 *************** *** 144,168 **** #endif /* defined(CRAY2) && defined(UNICOS5) */ /* - * Check for state of BINARY options. - */ - if (tty_isbinaryin()) { - if (his_want_state_is_wont(TELOPT_BINARY)) - send_do(TELOPT_BINARY, 1); - } else { - if (his_want_state_is_will(TELOPT_BINARY)) - send_dont(TELOPT_BINARY, 1); - } - - if (tty_isbinaryout()) { - if (my_want_state_is_wont(TELOPT_BINARY)) - send_will(TELOPT_BINARY, 1); - } else { - if (my_want_state_is_will(TELOPT_BINARY)) - send_wont(TELOPT_BINARY, 1); - } - - /* * Check for changes to flow control if client supports it. */ flowstat(); --- 144,149 ---- *************** *** 181,186 **** --- 162,195 ---- tty_setlinemode(uselinemode); } + if(uselinemode) { + + /* + * Check for state of BINARY options. + * + * We only need to do the binary dance if we are actually going + * to use linemode. As this confuses some telnet clients that dont + * support linemode, and doesnt gain us anything, we dont do it + * unless we're doing linemode. -Crh (henrich@msu.edu) + */ + + if (tty_isbinaryin()) { + if (his_want_state_is_wont(TELOPT_BINARY)) + send_do(TELOPT_BINARY, 1); + } else { + if (his_want_state_is_will(TELOPT_BINARY)) + send_dont(TELOPT_BINARY, 1); + } + + if (tty_isbinaryout()) { + if (my_want_state_is_wont(TELOPT_BINARY)) + send_will(TELOPT_BINARY, 1); + } else { + if (my_want_state_is_will(TELOPT_BINARY)) + send_wont(TELOPT_BINARY, 1); + } + + } /* * Do echo mode handling as soon as we know what the >Audit-Trail: >Unformatted: To: FreeBSD-gnats-submit@freebsd.org Subject: LINEMODE causes problems with some telnetd clients + fix. From: henrich@crh.cl.msu.edu Reply-To: henrich@crh.cl.msu.edu X-send-pr-version: 3.2 From owner-freebsd-bugs Mon Jun 12 02:09:16 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA16170 for bugs-outgoing; Mon, 12 Jun 1995 02:09:16 -0700 Received: from ra.ibr.cs.tu-bs.de (ra.ibr.cs.tu-bs.de [134.169.246.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id CAA16145 ; Mon, 12 Jun 1995 02:06:34 -0700 Received: from jupiter [134.169.34.4] by ra.ibr.cs.tu-bs.de (8.6.10/tubsibr) with ESMTP id LAA10079; Mon, 12 Jun 1995 11:05:42 +0200 Received: from petri@localhost by jupiter.ibr.cs.tu-bs.de (8.6.11/tubsibr) id LAA14341; Mon, 12 Jun 1995 11:05:36 +0200 Date: Mon, 12 Jun 1995 11:05:36 +0200 Message-Id: <199506120905.LAA14341@jupiter.ibr.cs.tu-bs.de> To: FreeBSD-gnats-submit@FreeBSD.org, bugs@FreeBSD.org Subject: make chokes on empty rules + fix From: petri@ibr.cs.tu-bs.de (Stefan Petri) Reply-To: petri@ibr.cs.tu-bs.de X-send-pr-version: 3.2 Sender: bugs-owner@FreeBSD.org Precedence: bulk >Submitter-Id: net >Originator: Stefan Petri >Organization: TU Braunschweig, Inst. f. Betriebssysteme u. Rechnerverbund >Confidential: no >Synopsis: make chokes on empty rules + fix >Severity: non-critical >Priority: medium >Category: bin >Release: FreeBSD 2.0.950412-SNAP i386 >Class: change-request >Environment: Any FreeBSD >Description: make aborts with fatal error if a Makefile rule line contains a tab followed by an emtpy shell command line. This is very annoying, because the Makefiles in almost every piece of software on the net contain such lines, notably Makefiles that are generated by the gnu configure utility. The correctness of such lines might be arguable, but since every other version of make simply ignores such lines, I propose the following fix, which will print out a warning about such a line, but will continue to make the target. [send-pr did not like ``Severity: seriuosly annoying'' ;-] >How-To-Repeat: Creat a Makefile with only a tabulator in a rule line, then invoke make. >Fix: *** /usr/src/usr.bin/make/parse.c-950412-SNAP Mon Jan 23 22:01:46 1995 --- parse.c Mon Jun 12 10:44:13 1995 *************** *** 715,721 **** * Ending a dependency line without an operator is a Bozo * no-no */ ! Parse_Error (PARSE_FATAL, "Need an operator"); return; } *cp = '\0'; --- 715,721 ---- * Ending a dependency line without an operator is a Bozo * no-no */ ! Parse_Error (PARSE_WARNING, "Need an operator"); return; } *cp = '\0'; From owner-freebsd-bugs Mon Jun 12 06:30:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA19605 for bugs-outgoing; Mon, 12 Jun 1995 06:30:02 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA19598 ; Mon, 12 Jun 1995 06:30:01 -0700 Date: Mon, 12 Jun 1995 06:30:01 -0700 Message-Id: <199506121330.GAA19598@freefall.cdrom.com> From: seki@sysrap.cs.fujitsu.co.jp Reply-To: seki@sysrap.cs.fujitsu.co.jp To: freebsd-bugs Subject: bin/506: /usr/src/release/libdisk/dkcksum.c missing In-Reply-To: Your message of Mon, 12 Jun 1995 22:06:19 GMT <199506122206.WAA02173@miroku.sysrap.cs.fujitsu.co.jp> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 506 >Category: bin >Synopsis: "Release" id generated by send-pr looks incorrect. >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Jun 12 06:30:01 1995 >Originator: Masahiro Sekiguchi >Organization: Fujitsu >Release: FreeBSD 2.0.5-RELEASE i386 >Environment: FreeBSD 2.0.5 RELEASE >Description: I invoked send-pr command to report a bug. I found that the "Release:" line generated by send-pr command incorrectly stated the system version as follows: >Release: FreeBSD 2.0-BUILT-19950603 i386 It should be >Release: FreeBSD 2.0.5-RELEASE i386 >How-To-Repeat: Invoke send-pr. >Fix: Not sure. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Mon Jun 12 06:34:08 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA19664 for bugs-outgoing; Mon, 12 Jun 1995 06:34:08 -0700 Received: from clark.net (rwatson@clark.net [168.143.0.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id GAA19658 for ; Mon, 12 Jun 1995 06:34:06 -0700 Received: (rwatson@localhost) by clark.net (8.6.12/8.6.5) id JAA07229 for bugs@freebsd.org; Mon, 12 Jun 1995 09:34:01 -0400 Date: Mon, 12 Jun 1995 09:34:01 -0400 From: Robert Watson Message-Id: <199506121334.JAA07229@clark.net> Subject: Installation on a 4 meg system -- still having problems after new boot.flp Content-Type: text Content-Length: 805 Apparently-To: bugs@FreeBSD.org Sender: bugs-owner@FreeBSD.org Precedence: bulk I just ftp'd the updated boot.flp and am still having difficulty -- the debug screen tells me that I keep running out of swap space and it is killing various processed (such as whenever I try to install, it aborts on the labeling/newfsing with error 137). I can't get it installed if it kills the installation process ;). Any help would be most appreciated. Also, just as a technical question -- the slice manager is showing a >1024 cylinder space on my drive -- can I safetly use that for either the root partition or the swap partition? Or should I use that for some less essential (and less boot-orriented) partition.. The best partition to use it for (for me) would be swap, if possible. Thanks for a great product (once I get it installed on this system ;). Robert Watson rwatson@sidwell.edu From owner-freebsd-bugs Mon Jun 12 07:32:29 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA20952 for bugs-outgoing; Mon, 12 Jun 1995 07:32:29 -0700 Received: from gateway.us.sidwell.edu (gateway.us.sidwell.edu [198.3.254.33]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id HAA20946 for ; Mon, 12 Jun 1995 07:32:25 -0700 Received: (from rwatson@localhost) by gateway.us.sidwell.edu (8.6.10/8.6.10) id KAA28134; Mon, 12 Jun 1995 10:31:32 -0400 Date: Mon, 12 Jun 1995 10:31:31 -0400 (EDT) From: Robert Watson X-Sender: rwatson@gateway.us.sidwell.edu To: bugs@FreeBSD.org Subject: Re: 2.0.5-RELEASE update (fwd) Message-ID: Organization: The Sidwell Friends School MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@FreeBSD.org Precedence: bulk Robert Watson rwatson@sidwell.edu http://www.sidwell.edu/~rwatson/ The goal of science is to build better mousetraps. The goal of nature is to build better mice. ---------- Forwarded message ---------- Date: Mon, 12 Jun 1995 09:45:53 -0400 (EDT) From: Robert Watson To: Gary Palmer Subject: Re: 2.0.5-RELEASE update Essentially -- I boot up, go to the menu program, and allocate the partitions and labels. Then I try to begin the rest of the installation, telling it what distirbutions to load. I choose medi, etc, and then commit. It tries to create the partitions (including swap, I guess) and things begin to die at this point, and I end up back at the menu with essentially nothing done (the parititions get made, slices get made, but no installation or newfs'ing occurs.) Since this is pre hd-swap, I don't see that I can allocate more swap ;). The HD parition I assign for swapping in the label section is 17 megs, which should be more than enough. It just isn't swapping at that point in the process. I'll try the dynamic ppp stuff once I get to the point where it will load -- I was just curious as it seemed to require config entries in the ppp config section. Thanks again. On Mon, 12 Jun 1995, Gary Palmer wrote: > In message , > Robert Watson writes: > >I'm still having difficulties udner the new boot disk under 4 megs -- I > >run out of swap space regularly during the installation procedure, and > >the processes for the installation get killed. Looks like just a little > >more space is needed even now.. I sent a more indepth description to > >bugs@freebsd.org a minute or so ago. It may just be a problem at my end, > >but the 2.0R disk worked fine on my system. > > Allocate more swap space and see if that helps. On a 4Mb machine, I > would generally recommend 16Mb's, as your machine is extremely limited > for main memory. I've passed this on to our local guru in this area. > I would certainly say if it boots, and you are getting processes > killed after boot due to lack of swap space, increase your swap space > allocation. Of course, if this is before you have a chance to allocate > and use swap, that is another problem :-( > > >Also, is there any support for dynamic IP allocation under PPP at this > >point, and if not, has SLIP support been removed in the installation (I > >have static SLIP available, and dynamic PPP ;). > > If you feed the system the correct information, I believe it will do > dynamic address resolution, although it may only be for the servers > end. I can't remember off hand. I know that ijppp can use dynamic > addressing, and that is the protocol module we are using. > > SLIP is supported, but only for hard wired links, i.e. you can't dial > out and connect via a modem. > > Sorry I can't be of more help, but the last week has kind of drained me :-( > > Gary > > Robert Watson rwatson@sidwell.edu http://www.sidwell.edu/~rwatson/ The goal of science is to build better mousetraps. The goal of nature is to build better mice. From owner-freebsd-bugs Mon Jun 12 07:52:12 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA21251 for bugs-outgoing; Mon, 12 Jun 1995 07:52:12 -0700 Received: from gw2.att.com (gw1.att.com [192.20.239.133]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id HAA21245 for ; Mon, 12 Jun 1995 07:52:11 -0700 Received: from ihats1.ih.att.com by ig1.att.att.com id AA03015; Mon, 12 Jun 95 10:45:44 EDT Received: by ihats1.ih.att.com (4.1/EMS-1.1.1 SunOS) id AA24433; Mon, 12 Jun 95 09:45:42 CDT From: imdave@ihats103.ih.att.com Received: from ihats103.ih.att.com by ihats1.ih.att.com (4.1/EMS-1.1.1 SunOS) id AA24429; Mon, 12 Jun 95 09:45:40 CDT Received: by ihats103.ih.att.com (4.1/EMS-1.1.1 SunOS) id AA02273; Mon, 12 Jun 95 09:45:15 CDT Date: Mon, 12 Jun 95 09:45:15 CDT Message-Id: <9506121445.AA02273@ihats103.ih.att.com> To: freebsd.org!freebsd-bugs@ig1.att.att.com Subject: iostat/scsi cdrom bug report Sender: bugs-owner@FreeBSD.org Precedence: bulk Running the april snap, I tried iostat. It showed the statistics for the WD? and SD? disks, but when I mounted a cdrom and did some cat's, no activity showed up. I took a quick look at the source for the SCSI cdrom driver, and it appears that the value of 'unit' being non-zero is used to control the statistics counting. However, since I only have one cdrom, the unit number is zero. I think the code uses a value of -1 to indicate "not present", so the check for updating the statistics needs to be changed. Dave Bodenstab AT&T ...att!ihats1!imdave From owner-freebsd-bugs Mon Jun 12 07:53:07 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA21259 for bugs-outgoing; Mon, 12 Jun 1995 07:53:07 -0700 Received: from gw2.att.com (gw1.att.com [192.20.239.133]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id HAA21253 for ; Mon, 12 Jun 1995 07:53:03 -0700 Received: from ihats1.ih.att.com by ig1.att.att.com id AA04037; Mon, 12 Jun 95 10:47:17 EDT Received: by ihats1.ih.att.com (4.1/EMS-1.1.1 SunOS) id AA24471; Mon, 12 Jun 95 09:47:15 CDT From: imdave@ihats103.ih.att.com Received: from ihats103.ih.att.com by ihats1.ih.att.com (4.1/EMS-1.1.1 SunOS) id AA24467; Mon, 12 Jun 95 09:47:14 CDT Received: by ihats103.ih.att.com (4.1/EMS-1.1.1 SunOS) id AA02278; Mon, 12 Jun 95 09:46:50 CDT Date: Mon, 12 Jun 95 09:46:50 CDT Message-Id: <9506121446.AA02278@ihats103.ih.att.com> To: freebsd.org!freebsd-bugs@ig1.att.att.com Subject: system header file problem bug report Sender: bugs-owner@FreeBSD.org Precedence: bulk Running april snap.... porting xfractint.... ran into undefined symbols sqrtl() etc. because the header files detected long double.... So, I grabbed the GNU C lib thinking it might support the math functions with long double (it turns out it doesn't, but I didn't know this yet.) When I ran the configure script, it worked OK until it referenced sys/sockio.h. This header contains some ioctl's which use some structures that are not declared anywhere in the kernel source tree -- I even grep'ed in the 2.0.1alpha kernel source tree. The ioctl's are: SIOCGETRTINFO, SIOCCGETSGCNT, SIOCCGETVIFCNT and SIOCSETRTINFO It seems to me that these should not be in the header files if FreeBSD does not support them, or at a minimum, the structures that these reference should be declared somewhere. Dave Bodenstab AT&T ...att!ihats1!imdave From owner-freebsd-bugs Mon Jun 12 08:08:10 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA21732 for bugs-outgoing; Mon, 12 Jun 1995 08:08:10 -0700 Received: from ra.ibr.cs.tu-bs.de (ra.ibr.cs.tu-bs.de [134.169.246.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA21718 for ; Mon, 12 Jun 1995 08:08:00 -0700 Received: from achill [134.169.34.18] by ra.ibr.cs.tu-bs.de (8.6.10/tubsibr) with ESMTP id RAA17464 for ; Mon, 12 Jun 1995 17:07:30 +0200 Received: from petri@localhost by achill.ibr.cs.tu-bs.de (8.6.10/tubsibr) id RAA09330; Mon, 12 Jun 1995 17:07:29 +0200 Date: Mon, 12 Jun 1995 17:07:29 +0200 From: Stefan Petri Message-Id: <199506121507.RAA09330@achill.ibr.cs.tu-bs.de> To: bugs@FreeBSD.org Subject: Re: make vs. empty lines Reply-to: petri@ibr.cs.tu-bs.de Sender: bugs-owner@FreeBSD.org Precedence: bulk Hi! well, the patch that I submitted earlier today does of course not really fix the problem in all cases (embarassed blush). However, the problem still remains, that it is seriously annoying when make aborts on empty lines. Who ever put that feature in, please do us all a favor and revert it. Stefan From owner-freebsd-bugs Mon Jun 12 10:00:09 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA25949 for bugs-outgoing; Mon, 12 Jun 1995 10:00:09 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA25929 for ; Mon, 12 Jun 1995 10:00:06 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id JAA02348; Mon, 12 Jun 1995 09:59:50 -0700 From: "Rodney W. Grimes" Message-Id: <199506121659.JAA02348@gndrsh.aac.dev.com> Subject: Re: make vs. empty lines To: petri@ibr.cs.tu-bs.de Date: Mon, 12 Jun 1995 09:59:50 -0700 (PDT) Cc: bugs@FreeBSD.org In-Reply-To: <199506121507.RAA09330@achill.ibr.cs.tu-bs.de> from "Stefan Petri" at Jun 12, 95 05:07:29 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: 828 Sender: bugs-owner@FreeBSD.org Precedence: bulk > > Hi! > > well, the patch that I submitted earlier today does of course not > really fix the problem in all cases (embarassed blush). However, the > problem still remains, that it is seriously annoying when make aborts > on empty lines. Who ever put that feature in, please do us all a favor > and revert it. Work is being done on this right now, I have one submission that has gone for review and been rejected by my second set of eyes, your submission that by your own admission is wrong. There is someone working on this that will get it right. And no, we can't just revert it as there are lots of other fixes in the same commit that are needed and are correct. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-bugs Mon Jun 12 10:25:55 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA02401 for bugs-outgoing; Mon, 12 Jun 1995 10:25:55 -0700 Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id KAA02390 for ; Mon, 12 Jun 1995 10:25:53 -0700 Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <15536(4)>; Mon, 12 Jun 1995 10:25:04 PDT Received: from localhost by crevenia.parc.xerox.com with SMTP id <49859>; Mon, 12 Jun 1995 10:24:57 -0700 X-Mailer: exmh version 1.6 4/21/95 To: imdave@ihats103.ih.att.com cc: bugs@FreeBSD.org Subject: Re: system header file problem bug report In-reply-to: Your message of "Mon, 12 Jun 95 07:46:50 PDT." <9506121446.AA02278@ihats103.ih.att.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 12 Jun 1995 10:24:43 PDT From: Bill Fenner Message-Id: <95Jun12.102457pdt.49859@crevenia.parc.xerox.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk In message <9506121446.AA02278@ihats103.ih.att.com> you write: >sys/sockio.h >contains some ioctl's which use some structures that are not declared anywhere >in the kernel source tree -- I even grep'ed in the 2.0.1alpha kernel source >tree. The ioctl's are: > > SIOCGETRTINFO, SIOCCGETSGCNT, SIOCCGETVIFCNT and SIOCSETRTINFO I assume that the doubled C's are typos. I think that SIOC{GET,SET}RTINFO were imported into FreeBSD because of a bug in the 3.3 multicast distribution -- one of the diff's included some DARTNet kernel changes by accident. The structures for SIOCGETSGCNT and SIOCGETVIFCNT are in /sys/netinet/ip_mroute.h . Bill From owner-freebsd-bugs Mon Jun 12 23:59:12 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA01109 for bugs-outgoing; Mon, 12 Jun 1995 23:59:12 -0700 Received: from cycle.Stanford.EDU (hlew@cycle.Stanford.EDU [36.159.0.10]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id XAA01103 ; Mon, 12 Jun 1995 23:59:11 -0700 Received: by cycle.Stanford.EDU; id AA19882; Mon, 12 Jun 1995 23:59:10 -0700 Date: Mon, 12 Jun 1995 23:59:10 -0700 (PDT) From: Howard Lew To: bugs@FreeBSD.org, hackers@FreeBSD.org Subject: 2.05R panics on boot Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@FreeBSD.org Precedence: bulk I just tried the new (second 2.05R) boot.flp, and it still panics with the same message on bootup after the PCI probe is completed. panic: cannot mount root syncing disks... done Automatic reboot in 15 seconds - press a key on the console to abort I didn't get any replies on the first post, so here it is again. Any help would be greatly appreciated. ---------- Forwarded message ---------- Date: Sun, 11 Jun 1995 02:51:49 -0700 (PDT) From: Howard Lew To: bugs@freebsd.org Subject: 2.05 Release I just ftped the 2.05 release and tried the install, and the installation process went well. But when I rebooted, the system would not boot up. Here's the system I tested it on: 386DX-40, 387 Cyrix MPU, 8MB RAM, 850MB (wd0) with Ontrack DM, and 540MB (wd1). The 850MB has DOS with dynamic drive overlay from Ontrack DM. I was planning on installing 2.05R on the 540MB Conner (entire disk). So after reset, it tries to boot up. I see the usual Ontrack DM overlay stuff, and then it says to press space for floppy boot. It never asks for F1-Disk 1 or F5-Disk 2. (Hmmm... This is strange because the SNAP releases didn't seem to have this boot selection problem. That boot manager seemed to always work fine). If I insert my 2.05 boot.flp disk, and enter hd(1,a)/kernel, it starts booting from wd1. And everything looks good until it finishes probing npx (no immediate problem after the probe). Then it tries probing the PCI stuff. (Yes it really probes for PCI stuff on my 386), and after it finishes the probe, it says: panic: cannot mount root syncing disks... done Automatic reboot in 15 seconds - press a key on the console to abort ----------------------------------------------------------- I redid the installation several times, and here are some additional observations: * If disabled the cache on my 386 motherboard and also disabled the 387, the system no longer probes for the PCI stuff... But then panics with the same message after the NPX probe. * The system panics regardless of whether or not I disable the NPX probe. * I tried disabling practically all the devices except the floppy drive, hard drives, lpt0, and sio1 with no effect -- still panics. * If I go through the installation program and finish the installation, I can use ALT-F4 to see everything on my wd1 drive. There appears to be no problems mounting partions from wd1, but it just can't do it from the hard disk kernel. * The boot.flp kernel does not seem to panic (but then again it is mounting root from mfs). * If I use Ontrack DM 6.03a and set the DOS partition active (I don't know why it became inactive), the system prompts for F1-Disk 1 and F5-Disk 2. But at that prompt, if I choose F1, I get DOS. And if I choose F5, I also get DOS (so they are still booting from wd0 which is my DOS drive). * In the installation... If I choose wd1 and do the partition, and then do the disklabel to mount the partitions, I never see the R flag as mentioned in the help info for Partitions. The CA>= flags do appear, but I never see the R flag appear. Could this be the cause of the problems? * The time zone setting doesn't seem to work (maybe old news sorry). Well, sorry this is kind of out of order. Any help is greatly appreciated. I really would like to get this 2.05R system humming... Thanks in advance for any help. --------------- Some good stuff I noticed fixed: * Help info is there * Many install bugs gone * PPP over a 115200 serial cable link never hangs anymore * no errors in bin extractions From owner-freebsd-bugs Tue Jun 13 00:10:24 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA02401 for bugs-outgoing; Tue, 13 Jun 1995 00:10:24 -0700 Received: from fitipc31.tu-graz.ac.at (root@fitipc31.tu-graz.ac.at [129.27.146.51]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id AAA02369 for ; Tue, 13 Jun 1995 00:10:02 -0700 Received: (from ruplit@localhost) by fitipc31.tu-graz.ac.at (8.6.9/8.6.9) id JAA20118; Tue, 13 Jun 1995 09:09:16 +0200 Date: Tue, 13 Jun 1995 09:09:15 +0200 (MET DST) From: Michael Ruplitsch To: Joerg Wunsch cc: freebsd-bugs@FreeBSD.org Subject: Re: dump having problems with remote tape drive In-Reply-To: <199506091735.TAA04032@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@FreeBSD.org Precedence: bulk On Fri, 9 Jun 1995, J Wunsch wrote: > As Michael Ruplitsch wrote: > > > > Hi, > Moin, Servus, > [...] > > Today I wanted to use `dump' to backup my hard drive onto a remote scsi tape > > drive. dump terminated with the message: > > Cannot open output "/dev/rmt/ctapen". > > > I found out that dump tries to open the remote tape for reading and > > writing (by sending "Otape-device\n2\n" to rmt where 2 means O_RDWR) > > instead of opening it for writing only (`1' instead of `2'). Is this a bug > > or is it a feature of dump? > > A feature. Why do you think _this_ might be the problem? > > [dump output deleted] > > Is there any reason why a tape driver should not allow an O_RDWR > access where it does allow O_WRONLY? Hmm, I don't think so. But on the other hand: what does dump need the read permission for? > Anyway, i found another bogon while i've been looking at this: dump > doesn't use an absolute path (/etc/rmt) as it ought to be; instead it > thinks it should rely on "rmt" only. As far as I know rmt does not live in /etc anymore. It's a link to /usr/sbin/rmt which is kept for reasons of backward compatibility. Slan, Michael From owner-freebsd-bugs Tue Jun 13 00:13:16 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA02593 for bugs-outgoing; Tue, 13 Jun 1995 00:13:16 -0700 Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id AAA02574 ; Tue, 13 Jun 1995 00:13:09 -0700 Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.9/8.6.9) id QAA24206; Tue, 13 Jun 1995 16:40:39 +0930 From: Michael Smith Message-Id: <199506130710.QAA24206@genesis.atrad.adelaide.edu.au> Subject: Re: 2.05R panics on boot To: hlew@cycle.Stanford.EDU (Howard Lew) Date: Tue, 13 Jun 1995 16:40:39 +0930 (CST) Cc: bugs@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: from "Howard Lew" at Jun 12, 95 11:59:10 pm Content-Type: text Content-Length: 1908 Sender: bugs-owner@FreeBSD.org Precedence: bulk Howard Lew stands accused of saying: > > I just tried the new (second 2.05R) boot.flp, and it still panics with > the same message on bootup after the PCI probe is completed. > So after reset, it tries to boot up. I see the usual Ontrack DM overlay > stuff, and then it says to press space for floppy boot. It never asks > for F1-Disk 1 or F5-Disk 2. (Hmmm... This is strange because the SNAP > releases didn't seem to have this boot selection problem. That boot > manager seemed to always work fine). Um. This sort of implies that your BIOS is set to boot from harddisk first, and then floppy. This is extremely ungood, if it is the case. > * If I use Ontrack DM 6.03a and set the DOS partition active (I don't > know why it became inactive), the system prompts for F1-Disk 1 and > F5-Disk 2. But at that prompt, if I choose F1, I get DOS. And if I > choose F5, I also get DOS (so they are still booting from wd0 which is my > DOS drive). This smells _awfully_ like you have DM coming in too early and trying to be "smart". > * In the installation... If I choose wd1 and do the partition, and then > do the disklabel to mount the partitions, I never see the R flag as > mentioned in the help info for Partitions. The CA>= flags do appear, but > I never see the R flag appear. Could this be the cause of the problems? I've never seen the 'R' flag either 8) Dike out the 850 and reconfigure the second disk as the first & try booting from it. This will rule out DM as a possible cause of trauma. -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] My car has "demand start" - Terry Lambert [[ From owner-freebsd-bugs Tue Jun 13 00:32:53 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA05172 for bugs-outgoing; Tue, 13 Jun 1995 00:32:53 -0700 Received: from muse.microunity.com (muse1.microunity.com [192.216.206.2]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id AAA05158 for ; Tue, 13 Jun 1995 00:32:50 -0700 Received: from gaea.microunity.com by muse.microunity.com (4.1/ericm1.1) id AA15776; Tue, 13 Jun 95 00:32:13 PDT Received: from muse.microunity.com by gaea.microunity.com (4.1/muse1.3) id AA03430; Tue, 13 Jun 95 00:32:12 PDT Received: from bilbo.microunity.com by muse.microunity.com (4.1/ericm1.1) id AA15773; Tue, 13 Jun 95 00:32:07 PDT Received: by bilbo.microunity.com (8.6.10/muse-sgi.2) for bugs@FreeBSD.org id AAA21266; Tue, 13 Jun 1995 00:32:05 -0700 Date: Tue, 13 Jun 1995 00:32:05 -0700 From: gmo@microunity.com (Guillermo A. Loyola) Message-Id: <199506130732.AAA21266@bilbo.microunity.com> To: bugs@FreeBSD.org Subject: Tape install & documentation Sender: bugs-owner@FreeBSD.org Precedence: bulk Hi BSDers, It would seem that there is a problem with tape installs or at least a documentation bug. The INSTALL document says to create a tape for installation by issuing a tar command like: "tar cvf /dev/... ". I did that on our freshly installed 2.0.5R, writing to an HP DAT tape. That command creates a tape blocked at 10k. When the sysinstall program tries to read the tape, it is using cpio -B which according to the man page means a blocksize of 5k. In fact when trying to use the tape to install, I get a message like "st0: 10k too big" (Sorry I didn't write down the exact wording) immediately. On a different subject, my previous attempt to install 2.0.5R on the machine I made the tape for was over an ISDN line with ethernet bridges (meaninig that as far as the machine is concerned it is just an ethernet that happens to only have 128kbits of bandwidth). I tried the install first using NFS with no special options and that just hung. Reading about the problems with NFS's big blocks I tried a second time setting the "slow ethernet" option and this time it didn't hang, but it was very slow (much less that 128kbits). Since my policy is "always blame NFS" I tried a third time using FTP and to my suprise, that was also about as slow. Now, this is a setup that I've been using with both Windows and FreeBSD 2.0R, and with either of them I do get transfer rates using FTP which are very close to the maximum (FTP reports 11 or 12 kbytes), but the 2.0.5R installation was just going like molases. Once I get 2.0.5 installed, I'll report on what kind of network performace I get out of the ISDN line, but in the mean time if you know of any reason why the install would go so slow, I'd like to know. For reference the machine in question is a Gateway2000 90Mhz Pentium with the Neptune PCI chipset. It has an ATI Mach64 video card and a Buslogic Bt946c SCSI controller with a Seagate 2G drive, Plexor 4X CD-ROM and the HP DAT tape. The machine has 32Meg of memory and uses a 3Com 3c509 ISA ethernet board. It also has a SoundScape board which is ignored by bsd. Btw, is anybody working on drivers for the soundscape? Do you know if Ensoniq is willing to disclose the necessary technical info? Gmo. From owner-freebsd-bugs Tue Jun 13 01:02:47 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA10816 for bugs-outgoing; Tue, 13 Jun 1995 01:02:47 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id BAA10774 for ; Tue, 13 Jun 1995 01:02:36 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id BAA09770; Tue, 13 Jun 1995 01:02:07 -0700 From: "Rodney W. Grimes" Message-Id: <199506130802.BAA09770@gndrsh.aac.dev.com> Subject: Re: 2.05R panics on boot To: hlew@cycle.Stanford.EDU (Howard Lew) Date: Tue, 13 Jun 1995 01:02:07 -0700 (PDT) Cc: bugs@FreeBSD.org In-Reply-To: from "Howard Lew" at Jun 12, 95 11:59:10 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: 4354 Sender: bugs-owner@FreeBSD.org Precedence: bulk [Please, one list ONLY! Redirected to -bugs] > I just tried the new (second 2.05R) boot.flp, and it still panics with > the same message on bootup after the PCI probe is completed. > > panic: cannot mount root > syncing disks... done > Automatic reboot in 15 seconds - press a key on the console to abort > > I didn't get any replies on the first post, so here it is > again. Any help would be greatly appreciated. Stopping say hd(1,a)/kernel as you do not have both an IDE and a SCSI disk. You are trying to boot from the second IDE disk which is wd(1,a)/kernel. The problem you are having is ``hd'' is magic, it says use the n'th BIOS disk to load, but pass the kernel sd(n - 1) as the root device. Thus it is looking for sd0 on your system for the root file system, and you don't have one... > > ---------- Forwarded message ---------- > Date: Sun, 11 Jun 1995 02:51:49 -0700 (PDT) > From: Howard Lew > To: bugs@freebsd.org > Subject: 2.05 Release > > I just ftped the 2.05 release and tried the install, and the installation > process went well. But when I rebooted, the system would not boot up. > > Here's the system I tested it on: > 386DX-40, 387 Cyrix MPU, 8MB RAM, 850MB (wd0) with Ontrack DM, and > 540MB (wd1). > > The 850MB has DOS with dynamic drive overlay from Ontrack DM. I was > planning on installing 2.05R on the 540MB Conner (entire disk). > > So after reset, it tries to boot up. I see the usual Ontrack DM overlay > stuff, and then it says to press space for floppy boot. It never asks > for F1-Disk 1 or F5-Disk 2. (Hmmm... This is strange because the SNAP > releases didn't seem to have this boot selection problem. That boot > manager seemed to always work fine). > > If I insert my 2.05 boot.flp disk, and enter hd(1,a)/kernel, it starts > booting from wd1. And everything looks good until it finishes probing > npx (no immediate problem after the probe). Then it tries probing the PCI > stuff. (Yes it really probes for PCI stuff on my 386), and after it > finishes the probe, it says: > > panic: cannot mount root > syncing disks... done > Automatic reboot in 15 seconds - press a key on the console to abort > ----------------------------------------------------------- > I redid the installation several times, and here are some additional > observations: > > * If disabled the cache on my 386 motherboard and also disabled the 387, > the system no longer probes for the PCI stuff... But then panics with the > same message after the NPX probe. > > * The system panics regardless of whether or not I disable the NPX probe. > > * I tried disabling practically all the devices except the floppy drive, > hard drives, lpt0, and sio1 with no effect -- still panics. > > * If I go through the installation program and finish the installation, I > can use ALT-F4 to see everything on my wd1 drive. There appears to be no > problems mounting partions from wd1, but it just can't do it from the > hard disk kernel. > > * The boot.flp kernel does not seem to panic (but then again it is > mounting root from mfs). > > * If I use Ontrack DM 6.03a and set the DOS partition active (I don't > know why it became inactive), the system prompts for F1-Disk 1 and > F5-Disk 2. But at that prompt, if I choose F1, I get DOS. And if I > choose F5, I also get DOS (so they are still booting from wd0 which is my > DOS drive). > > * In the installation... If I choose wd1 and do the partition, and then > do the disklabel to mount the partitions, I never see the R flag as > mentioned in the help info for Partitions. The CA>= flags do appear, but > I never see the R flag appear. Could this be the cause of the problems? > > * The time zone setting doesn't seem to work (maybe old news sorry). > > Well, sorry this is kind of out of order. Any help is greatly > appreciated. I really would like to get this 2.05R system humming... > Thanks in advance for any help. > > --------------- > Some good stuff I noticed fixed: > * Help info is there > * Many install bugs gone > * PPP over a 115200 serial cable link never hangs anymore > * no errors in bin extractions > > > > > > > > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-bugs Tue Jun 13 10:25:17 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA21838 for bugs-outgoing; Tue, 13 Jun 1995 10:25:17 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id KAA21804 for ; Tue, 13 Jun 1995 10:25:11 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA20562; Tue, 13 Jun 1995 19:25:06 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id TAA25201; Tue, 13 Jun 1995 19:25:06 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id SAA07714; Tue, 13 Jun 1995 18:21:41 +0200 From: J Wunsch Message-Id: <199506131621.SAA07714@uriah.heep.sax.de> Subject: Re: dump having problems with remote tape drive To: ruplit@fitipc31.tu-graz.ac.at (Michael Ruplitsch) Date: Tue, 13 Jun 1995 18:21:40 +0200 (MET DST) Cc: freebsd-bugs@FreeBSD.org (FreeBSD bugs list) In-Reply-To: from "Michael Ruplitsch" at Jun 13, 95 09:09:15 am Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1372 Sender: bugs-owner@FreeBSD.org Precedence: bulk As Michael Ruplitsch wrote: > > > Is there any reason why a tape driver should not allow an O_RDWR > > access where it does allow O_WRONLY? > Hmm, I don't think so. But on the other hand: what does dump need the > read permission for? Ok, so it's not a fatal bug, but perhaps worth to be fixed anyway. > > Anyway, i found another bogon while i've been looking at this: dump > > doesn't use an absolute path (/etc/rmt) as it ought to be; instead it > > thinks it should rely on "rmt" only. > As far as I know rmt does not live in /etc anymore. It's a link to > /usr/sbin/rmt which is kept for reasons of backward compatibility. *Our* rmt program does not live in /etc, yes. Anyway, since it's a remote protocol, we cannot rely on any particular location for any particular system. The only convention for the location is /etc (as it used to be all the time), hence every system usually keeps the symlink there. The salomonic decision of the 4.4BSD designers to let rdump just ask for "rmt" instead of any particular path is IMVHO a bad bug. It's now relying on some user's login path setting. (Btw., GNU tar, also using the rmt protocol, made it obvious that we actually need the symlink, that's why it is there now.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Tue Jun 13 10:30:07 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA22876 for bugs-outgoing; Tue, 13 Jun 1995 10:30:07 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA22866 ; Tue, 13 Jun 1995 10:30:04 -0700 Date: Tue, 13 Jun 1995 10:30:04 -0700 Message-Id: <199506131730.KAA22866@freefall.cdrom.com> From: wpaul@skynet.ctr.columbia.edu Reply-To: wpaul@skynet.ctr.columbia.edu To: freebsd-bugs Subject: kern/507: Trying to load if_sl_mod or if_ppp_mod *twice* crashes system In-Reply-To: Your message of Tue, 13 Jun 1995 13:20:04 -0400 <199506131720.NAA00962@skynet.ctr.columbia.edu> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 507 >Category: kern >Synopsis: Trying to load if_sl_mod or if_ppp_mod *twice* crashes system >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jun 13 10:30:02 1995 >Originator: Bill Paul >Organization: Center for Telecommunications Research, Columbia University >Release: FreeBSD 2.0.5-RELEASE i386 >Environment: FreeBSD 2.0.5-RELEASE 386sx/16Mhz CPU with 80387 FPU 4 MB RAM (yes, it works :) NEC 765 floppy controller with 2 floppies 2 IDE controllers (wdc0, wdc1) 2 Seagate ST351A/X drives (wd0 and wd2) 1 Maxtor 7345 AT drive (wd1) 3 serial ports (sio0, sio1, sio2) 2 parallel ports original 8-bit mono SoundBlaster card SMC SMC8416C/SMC8416BT plug & play ethernet adapter (ed0) STB PowerGraph ET4000-based SVGA display adapter (1MB RAM) (sc0) external USRobotics Sportster 14.4 moded (with FAX) on /dev/cuaa1 System kernel is compiled with support for all hardware devices, but SLIP, PPP, NFS and procfs support is loaded dynamically at boot time using loadable kernel modules. I have rebuilt the SLIP and PPP modules to support the Berkeley Packet Filter since I have BPF configured into my kernel, however this does not influence the manifestation of the bug: both my rebuilt modules and the stock modules distributed with the 2.0.5R bindist exhibit the same broken behavior. >Description: The 'pseudo-lkms,' such as if_sl, if_ppp (and probably if_tun too though I haven't tested that one yet) appear to get just a little too far into their initialization before checking for the existance of duplicate modules. In my configuration, if_sl_mod.o is loaded by netstart when the system boots. This first instance of the SLIP driver works perfectly by itself (I'm writing this bug report on my home machine from work over the SLIP link now). However, attempting to load the if_sl_mod.o module for a second time causes the system to lock up or panic (the exact outcome depends on the phase of the moon, the direction of the wind and other irreproducible phenomena). You're supposed to get an error and the module should simply fail to load. Instead, you get an error, and then the system self-destructs. There's supposed to be some checking done to prevent the loading of two instances of the same module, but the checks don't seem to work correctly for LM_MISC pseudo_lkms. When the second instance of the module is loaded, you do indeed get an error telling you that there's a duplicate module present, but the checking is done too late; by the time modload gets hit with EEXIST, the module has already been initialized and has irrevocably wired itself into the system. Once the error has been detected, an attempt is them made to unreserve the memory occupied by the duplicate module, which causes the system to either hang or crash a short while later. >How-To-Repeat: # modload -e if_sl_mod -o /tmp/if_sl /lkm/if_sl_mod.o # modload -e if_sl_mod -o /tmp/if_sl /lkm/if_sl_mod.o [modload will complain 'file exists' then the system will die] >Fix: I think this is a case of misplaced sanity checking. Digging through the tangle of macros used to implement the PSEUDO_LKMs has led me to the conclusion that the 'init' function (in this case slattach()) is being called before lkmdispatch(), with the difficulty being that lkmdispatch() (which is in the kernel) is the function that does the duplicate module checking. (Hijinks ensue, and all that.) With the other LKMs (the VFS ones, for instance), the module initialization is left up to specific kernel functions that are called by lkmdispatch(), so in those cases the sanity checks work correctly. But if_sl, if_ppp, etc. are LM_MISC type modules which are largely left to their own devices (no pun intended). One way I can think of to fix this would be to make the LKM_E_LOAD case of the DISPATCH() macro (/usr/include/sys/lkm.h) do more sanity checking before marching off and invoking the module's initialization function. If it's possible to call lkmexists() from there, this would be ideal. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Tue Jun 13 10:57:44 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA27946 for bugs-outgoing; Tue, 13 Jun 1995 10:57:44 -0700 Received: from vegemite.Stanford.EDU (2842@vegemite.Stanford.EDU [36.159.0.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA27936 for ; Tue, 13 Jun 1995 10:57:43 -0700 Received: (hlew@localhost) by vegemite.Stanford.EDU (8.6.10/8.6.4) id KAA08430; Tue, 13 Jun 1995 10:57:33 -0700 Date: Tue, 13 Jun 1995 10:57:32 -0700 (PDT) From: Howard Lew To: "Rodney W. Grimes" cc: bugs@FreeBSD.org Subject: Re: 2.05R panics on boot In-Reply-To: <199506130802.BAA09770@gndrsh.aac.dev.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@FreeBSD.org Precedence: bulk On Tue, 13 Jun 1995, Rodney W. Grimes wrote: > [Please, one list ONLY! Redirected to -bugs] > > > I just tried the new (second 2.05R) boot.flp, and it still panics with > > the same message on bootup after the PCI probe is completed. > > > > panic: cannot mount root > > syncing disks... done > > Automatic reboot in 15 seconds - press a key on the console to abort > > > Stopping say hd(1,a)/kernel as you do not have both an IDE and a SCSI > disk. You are trying to boot from the second IDE disk which is > wd(1,a)/kernel. The problem you are having is ``hd'' is magic, it > says use the n'th BIOS disk to load, but pass the kernel sd(n - 1) > as the root device. Thus it is looking for sd0 on your system for > the root file system, and you don't have one... > Thanks for the help. Using wd(1,a)/kernel did solve the panic problem (gee, how much I wish this was in a faq...) Now only if the system would boot up with the boot manager. What ever happened to the boot manager that was used on the SNAPs? That one seemed to work be able to boot up even on this 850 WDC drive with Ontrack DM installed. Booteasy wasn't able to do it. They were different right? or has something changed? From owner-freebsd-bugs Tue Jun 13 11:13:44 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA00978 for bugs-outgoing; Tue, 13 Jun 1995 11:13:44 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id LAA00957 ; Tue, 13 Jun 1995 11:13:40 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA03697; Tue, 13 Jun 95 12:06:31 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9506131806.AA03697@cs.weber.edu> Subject: Re: 2.05R panics on boot To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Tue, 13 Jun 95 12:06:31 MDT Cc: hlew@cycle.Stanford.EDU, bugs@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: <199506130710.QAA24206@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Jun 13, 95 04:40:39 pm X-Mailer: ELM [version 2.4dev PL52] Sender: bugs-owner@FreeBSD.org Precedence: bulk > > * If I use Ontrack DM 6.03a and set the DOS partition active (I don't > > know why it became inactive), the system prompts for F1-Disk 1 and > > F5-Disk 2. But at that prompt, if I choose F1, I get DOS. And if I > > choose F5, I also get DOS (so they are still booting from wd0 which is my > > DOS drive). > > This smells _awfully_ like you have DM coming in too early and trying to > be "smart". Well, it's allowed to do that. It *is* smart. 8^). What it sounds more like is the boot manager being written on top of DM instead of being smart (like *it* should) and getting written to the secondary MBR that DM causes to exist following 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-bugs Tue Jun 13 12:37:37 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA04354 for bugs-outgoing; Tue, 13 Jun 1995 12:37:37 -0700 Received: from ibeam.intel.com (ibeam.jf.intel.com [134.134.208.3]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA04348 for ; Tue, 13 Jun 1995 12:37:36 -0700 Received: from aahz.jf.intel.com by ibeam.intel.com with smtp (Smail3.1.28.1 #6) id m0sLbkw-000RTVC; Tue, 13 Jun 95 12:36 PDT Received: by aahz.jf.intel.com (Smail3.1.28.1 #13) id m0sLblo-000RhyC; Tue, 13 Jun 95 12:36 PDT Message-Id: From: batie@ibeam.jf.intel.com (Alan Batie) Subject: EE16 driver: No buffers To: freebsd-bugs@FreeBSD.org Date: Tue, 13 Jun 1995 12:36:47 -40962758 (PDT) X-Mailer: ELM [version 2.4 PL17] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 586 Sender: bugs-owner@FreeBSD.org Precedence: bulk FreeBSD 2.0.5 Release Intel EtherExpress 16 Things work just fine under light load, but when I toss a little bit of stress at it (in particular, a few constant streams of http requests), the network interface stops functioning. When I try pinging someplace from the console, I get "ping: sendto: No buffer space available". netstat -m shows all of 88 MBUFS in use. -- Alan Batie ------ batie@aahz.jf.intel.com \ / X.400: same day delivery +1 503-264-8844 (voice) \ / ...in a nanosecond world. +1 503-264-6388 (fax) \/ From owner-freebsd-bugs Tue Jun 13 12:39:47 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA04430 for bugs-outgoing; Tue, 13 Jun 1995 12:39:47 -0700 Received: from ibeam.intel.com (ibeam.jf.intel.com [134.134.208.3]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA04423 for ; Tue, 13 Jun 1995 12:39:46 -0700 Received: from aahz.jf.intel.com by ibeam.intel.com with smtp (Smail3.1.28.1 #6) id m0sLbn2-000RTLC; Tue, 13 Jun 95 12:38 PDT Received: by aahz.jf.intel.com (Smail3.1.28.1 #13) id m0sLbnu-000RhyC; Tue, 13 Jun 95 12:38 PDT Message-Id: From: batie@ibeam.jf.intel.com (Alan Batie) Subject: ed0 lockup To: freebsd-bugs@FreeBSD.org Date: Tue, 13 Jun 1995 12:38:57 -40962758 (PDT) X-Mailer: ELM [version 2.4 PL17] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 364 Sender: bugs-owner@FreeBSD.org Precedence: bulk FreeBSD 2.0.5 Release Compex ReadyLINK ENET16-COMBO/P (REV A1) When I ifconfig the ed0 interface, I get a shell prompt and the system locks up. -- Alan Batie ------ batie@aahz.jf.intel.com \ / X.400: same day delivery +1 503-264-8844 (voice) \ / ...in a nanosecond world. +1 503-264-6388 (fax) \/ From owner-freebsd-bugs Tue Jun 13 14:13:12 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA14586 for bugs-outgoing; Tue, 13 Jun 1995 14:13:12 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id OAA14574 for ; Tue, 13 Jun 1995 14:13:10 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA17287; Tue, 13 Jun 95 15:05:04 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9506132105.AA17287@cs.weber.edu> Subject: Re: 2.05R panics on boot To: hlew@genome.Stanford.EDU (Howard Lew) Date: Tue, 13 Jun 95 15:05:03 MDT Cc: rgrimes@gndrsh.aac.dev.com, bugs@FreeBSD.org In-Reply-To: from "Howard Lew" at Jun 13, 95 10:57:32 am X-Mailer: ELM [version 2.4dev PL52] Sender: bugs-owner@FreeBSD.org Precedence: bulk > Now only if the system would boot up with the boot manager. What ever > happened to the boot manager that was used on the SNAPs? That one > seemed to work be able to boot up even on this 850 WDC drive with Ontrack > DM installed. Booteasy wasn't able to do it. They were different > right? or has something changed? Boot DOS from the hard drive to get the DM stuff installed and subtracting 64 from the sector number on all references. Install a boot manager under DOS. Everything should work. The boot manager installation appears to not take DM into account. 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-bugs Tue Jun 13 14:30:04 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA16763 for bugs-outgoing; Tue, 13 Jun 1995 14:30:04 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA16756 ; Tue, 13 Jun 1995 14:30:02 -0700 Date: Tue, 13 Jun 1995 14:30:02 -0700 Message-Id: <199506132130.OAA16756@freefall.cdrom.com> From: Bill Fenner Reply-To: Bill Fenner To: freebsd-bugs Subject: bin/508: getnetgrent() prints un-helpful error message (with NULL pointer, even) In-Reply-To: Your message of Tue, 13 Jun 1995 14:31:46 PDT <199506132131.OAA08396@baobab.parc.xerox.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 508 >Category: bin >Synopsis: getnetgrent() prints un-helpful error message (with NULL pointer, even) >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jun 13 14:30:01 1995 >Originator: Bill Fenner >Organization: Xerox PARC >Release: FreeBSD 2.0-BUILT-19950527 i386 >Environment: FreeBSD 2.0.5-ALPHA >Description: /etc/netgroup has a single "+" /etc/hosts.equiv has "+@sun-access" The NIS netgroup sun-access is a very deeply recursive list. Example: % ypmatch sun-access netgroup sun-accessN sun-accessD % ypmatch sun-accessN netgroup sun-access01N sun-access02N sun-access03N % ypmatch sun-access03N netgroup parc-pcsN parc-guestsN parc-termportsN % ypmatch parc-pcsN netgroup pcs01N pcs02N pcs03N pcs04N pcs05N pcs06N % ypmatch pcs02N netgroup parc-pcs10N parc-pcs11N parc-pcs12N parc-pcs13N parc-pcs14N parc-pcs15N parc-pcs16N parc-pcs17N parc-pcs18N % ypmatch parc-pcs15N netgroup (esca,-,PARC) (tech-1,-,PARC) (doc-control,-,PARC) (the-stooges,-,PARC) (munira,-,PARC) (sonoma,-,PARC) (tfs-pc,-,PARC) (oemd-pc,-PARC) (fourier,-,PARC) Attempting to rlogin gives: crevenia% rlogin baobab ad netgroup parc-pcs15N at ..(null) I assume that this is the error printed by lib/libc/gen/getnetgrent.c: parse_netgrp(). Now, indeed, oemd-pc's entry is bad, but the error message doesn't exactly make that very obvious... Also, someone ate the first character of the error message. >How-To-Repeat: Create a netgroup with an entry like (foo,-BAR) and try to use getnetgrent() on it. >Fix: Probably just need a more intelligent error message. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Tue Jun 13 14:40:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA18515 for bugs-outgoing; Tue, 13 Jun 1995 14:40:02 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA18508 ; Tue, 13 Jun 1995 14:40:01 -0700 Date: Tue, 13 Jun 1995 14:40:01 -0700 Message-Id: <199506132140.OAA18508@freefall.cdrom.com> From: Bill Fenner Reply-To: Bill Fenner To: freebsd-bugs Subject: bin/509: netgroup cycle detection is broken In-Reply-To: Your message of Tue, 13 Jun 1995 14:40:20 PDT <199506132140.OAA08511@baobab.parc.xerox.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 509 >Category: bin >Synopsis: netgroup cycle detection is too "greedy" >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jun 13 14:40:00 1995 >Originator: Bill Fenner >Organization: Xerox PARC >Release: FreeBSD 2.0-BUILT-19950527 i386 >Environment: FreeBSD 2.0.5-ALPHA running NIS in existing, largely Sun environment >Description: getnetgrent() claims that there is a loop in the netgroup parc-decsD. The problem is actually that the netgroup sun-access02D contains parc-decsD twice: % ypmatch sun-access02D netgroup parc-abekasD parc-irisD parc-vaxsD parc-decsD parc-ibmsD parc-ncdsD parc-decsD parc-annexD Since it has visited the node before, it decides that there is a cycle in parc-decsD. >How-To-Repeat: Create a netgroups file similar to: foo bar bar bar (baz,-,MYDOMAIN) getnetgrent() will complain that there is a cycle in bar. >Fix: Not clear. It's clearly less than ideal to list the same subgroup twice in the same netgroup entry, but it's also clear that the problem is not that there is a cycle. Might be fixing the error message, might be fixing the checks. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Tue Jun 13 15:30:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA21305 for bugs-outgoing; Tue, 13 Jun 1995 15:30:02 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA21296 ; Tue, 13 Jun 1995 15:30:01 -0700 Date: Tue, 13 Jun 1995 15:30:01 -0700 Message-Id: <199506132230.PAA21296@freefall.cdrom.com> From: Bill Fenner Reply-To: Bill Fenner To: freebsd-bugs Subject: bin/510: netgroup host matching doesn't appear to work In-Reply-To: Your message of Tue, 13 Jun 1995 15:24:55 PDT <199506132224.PAA08651@baobab.parc.xerox.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 510 >Category: bin >Synopsis: netgroup host matching doesn't appear to work >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jun 13 15:30:01 1995 >Originator: Bill Fenner >Organization: Xerox PARC >Release: FreeBSD 2.0-BUILT-19950527 i386 >Environment: FreeBSD 2.0.5-ALPHA Existing sun NIS environment >Description: /etc/hosts.equiv has "+@sun-access" in it When trying to log in from the machine "crevenia", I still get asked for a password. "crevenia" is in the sun-access netgroup as both "crevenia" and "crevenia.parc.xerox.com". baobab# domainname PARC baobab# ypwhich eich.parc.xerox.com baobab# alias yk 'ypmatch -k \!* netgroup' baobab# yk sun-access sun-access sun-accessN sun-accessD baobab# yk sun-accessN sun-accessN sun-access01N sun-access02N sun-access03N baobab# yk sun-access01N sun-access01N parc-sunsN parc-ardenN parc-macsN parc-mipsN parc-doradosN parc-daybreaksN parc-symbolicsN parc-nextN baobab# yk parc-sunsN parc-sunsN suns01N suns02N suns03N suns04N suns05N suns06N suns07N suns08N suns09N suns10N suns11N baobab# yk suns02N suns02N parc-suns10N parc-suns11N parc-suns12N parc-suns13N parc-suns14N parc-suns15N parc-suns16N parc-suns17N parc-suns18N baobab# yk parc-suns18N parc-suns18N (crevenia,-,PARC) (antarea,-,PARC) (arcturia,-,PARC) (thyron,-,PARC) /* The D tree follows the N tree exactly, no point in repeating it */ baobab# yk parc-suns18D parc-suns18D (crevenia.parc.xerox.com,-,PARC) (antarea.parc.xerox.com,-,PARC) (arcturia.parc.xerox.com,-,PARC) (thyron.parc.xerox.com,-,PARC) >How-To-Repeat: Try to rlogin to a machine with a netgroup in /etc/hosts.equiv and a + in /etc/netgroup >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Tue Jun 13 22:16:49 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA08169 for bugs-outgoing; Tue, 13 Jun 1995 22:16:49 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA08161 for ; Tue, 13 Jun 1995 22:16:46 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id WAA00211; Tue, 13 Jun 1995 22:15:23 -0700 From: "Rodney W. Grimes" Message-Id: <199506140515.WAA00211@gndrsh.aac.dev.com> Subject: Re: EE16 driver: No buffers To: batie@ibeam.jf.intel.com (Alan Batie) Date: Tue, 13 Jun 1995 22:15:22 -0700 (PDT) Cc: freebsd-bugs@FreeBSD.org In-Reply-To: from "Alan Batie" at Jun 13, 95 12:36:47 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: 1513 Sender: bugs-owner@FreeBSD.org Precedence: bulk > > FreeBSD 2.0.5 Release > Intel EtherExpress 16 > > Things work just fine under light load, but when I toss a little bit of > stress at it (in particular, a few constant streams of http requests), > the network interface stops functioning. When I try pinging someplace > from the console, I get "ping: sendto: No buffer space available". > netstat -m shows all of 88 MBUFS in use. Is this on agora?? If so I can pop over and look at it. I have had several sites report what looks to be a lost interrupt problem. Have you had an ix0: device timeout messages? Also if you ping it from another box does it magically come back to life?? Also you might try this to speed up the recovery from lost transmitter interrupts: Index: if_ix.c =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/if_ix.c,v retrieving revision 1.7 diff -c -r1.7 if_ix.c *** 1.7 1995/05/30 08:02:15 --- if_ix.c 1995/06/14 05:14:51 *************** *** 1464,1470 **** * set the watchdog timer so that if the board fails to interrupt * we will go clean up */ ! ifp->if_timer = 2; ixstart_exit: DEBUGBEGIN(DEBUGSTART) --- 1464,1470 ---- * set the watchdog timer so that if the board fails to interrupt * we will go clean up */ ! ifp->if_timer = 1; ixstart_exit: DEBUGBEGIN(DEBUGSTART) -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-bugs Tue Jun 13 22:35:41 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA09794 for bugs-outgoing; Tue, 13 Jun 1995 22:35:41 -0700 Received: from pelican.com (pelican.com [134.24.4.62]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id WAA09773 for ; Tue, 13 Jun 1995 22:35:30 -0700 Received: by pelican.com (Smail3.1.28.1 #5) id m0sLl6j-000K0pC; Tue, 13 Jun 95 22:35 WET DST Message-Id: From: pete@pelican.com (Pete Carah) Subject: msdos floppy problem To: bugs@freebsd.org Date: Tue, 13 Jun 1995 22:35:17 -0700 (PDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 796 Sender: bugs-owner@freebsd.org Precedence: bulk System: Current from about 2-3 weeks ago; I don't think anything has changed in msdosfs... With a miscellaneous dos floppy (1.44mb 3.5") that I needed to get data from, "mount -t msdos /dev/fd0.1440 /a" then "ls -l /a" gave a half-screen of garbage followed by a decent directory (there were only 2 files in the disks root; one a .exe and the other a directory, which contained 2 regular files). At least this garbage didn't scramble cons25 :-) mdir/mcopy saw it just fine with no bogus entries. (the reason I used mount in the first place was that I didn't yet have mtools; I ended up downloading it in midstream, in disgust.) Don't know what the problem is unless the directory read isn't getting truncated at the first 0 leading byte (or is that still a valid dos optimization?) -- Pete From owner-freebsd-bugs Wed Jun 14 12:10:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA23955 for bugs-outgoing; Wed, 14 Jun 1995 12:10:02 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA23947 ; Wed, 14 Jun 1995 12:10:01 -0700 Date: Wed, 14 Jun 1995 12:10:01 -0700 Message-Id: <199506141910.MAA23947@freefall.cdrom.com> From: Alan Bawden Reply-To: Alan Bawden To: freebsd-bugs Subject: docs/511: bpf(4) is gone In-Reply-To: Your message of Wed, 14 Jun 1995 15:06:44 -0400 <199506141906.PAA00512@beandorf.epilogue.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 511 >Category: docs >Synopsis: bpf(4) is gone >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Wed Jun 14 12:10:00 1995 >Originator: Alan Bawden >Organization: >Release: FreeBSD 2.0-RELEASE i386 >Environment: ??? >Description: The manual page for /dev/bpf seems to missing from 2.0. It was present in 1.1.5.1. >How-To-Repeat: 'man bpf' >Fix: Bring it back. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Wed Jun 14 12:22:23 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA25408 for bugs-outgoing; Wed, 14 Jun 1995 12:22:23 -0700 Received: from vegemite.Stanford.EDU (2842@vegemite.Stanford.EDU [36.159.0.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA25400 for ; Wed, 14 Jun 1995 12:22:21 -0700 Received: (hlew@localhost) by vegemite.Stanford.EDU (8.6.10/8.6.4) id MAA11184; Wed, 14 Jun 1995 12:22:18 -0700 Date: Wed, 14 Jun 1995 12:22:17 -0700 (PDT) From: Howard Lew To: Terry Lambert cc: bugs@FreeBSD.org Subject: Re: 2.05R panics on boot In-Reply-To: <9506132105.AA17287@cs.weber.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@FreeBSD.org Precedence: bulk On Tue, 13 Jun 1995, Terry Lambert wrote: > > Now only if the system would boot up with the boot manager. What ever > > happened to the boot manager that was used on the SNAPs? That one > > seemed to work be able to boot up even on this 850 WDC drive with Ontrack > > DM installed. Booteasy wasn't able to do it. They were different > > right? or has something changed? > > Boot DOS from the hard drive to get the DM stuff installed and subtracting > 64 from the sector number on all references. Do I subtract 64 from the sector number while in the FreeBSD install program under disk partitioning or are you referring to a DOS utility to do this? > > Install a boot manager under DOS. > > Everything should work. > > The boot manager installation appears to not take DM into account. Do I still use booteasy? For some reason, the Dynamic drive overlay from Ontrack DM always comes up first. Then after the prompt about booting from floppies, it starts booteasy. But booteasy gives 2 options: F1-for disk 1 or F5-For disk 2 (no F4-For Freebsd like in the SNAPs). Thanks for the help. /--------------------------------------\ / Howard Lew \ < Email: hlew@genome.stanford.edu > \ http://www.shoppersnet.com / \--------------------------------------/ From owner-freebsd-bugs Wed Jun 14 13:57:06 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA29506 for bugs-outgoing; Wed, 14 Jun 1995 13:57:06 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id NAA29500 for ; Wed, 14 Jun 1995 13:57:04 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA19501; Wed, 14 Jun 95 14:50:15 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9506142050.AA19501@cs.weber.edu> Subject: Re: 2.05R panics on boot To: hlew@genome.Stanford.EDU (Howard Lew) Date: Wed, 14 Jun 95 14:50:14 MDT Cc: bugs@FreeBSD.org, terry@cs.weber.edu (Terry Lambert) In-Reply-To: from "Howard Lew" at Jun 14, 95 12:22:17 pm X-Mailer: ELM [version 2.4dev PL52] Sender: bugs-owner@FreeBSD.org Precedence: bulk > > > Now only if the system would boot up with the boot manager. What ever > > > happened to the boot manager that was used on the SNAPs? That one > > > seemed to work be able to boot up even on this 850 WDC drive with Ontrack > > > DM installed. Booteasy wasn't able to do it. They were different > > > right? or has something changed? > > > > Boot DOS from the hard drive to get the DM stuff installed and subtracting > > 64 from the sector number on all references. [ SIZES IN THE FOLLOWING ARE NOT RELATIVE... ] Without DM: ,---------.---------------.---------------.---------------- | DOS MBR | PARTITION ... | PARTITION ... | ... `---------'---------------'---------------'---------------- ^ | A With DM: ,--------.---------.---------------.---------------.------- | DM MBR | DOS MBR | PARTITION ... | PARTITION ... | ... `--------'---------'---------------'---------------'------- ^ | A' The DOS MBR: ,------.---------------------.-------------------. | JUMP | DOS PARTITION TABLE | DOS MBR BOOT CODE | `------'---------------------'-------------------' The DM MBR: .------.-------------------------.---------------. | JUMP | FAKE DOS PARTIOTN TABLE | DM MAGIC CODE | `------'-------------------------'---------------' The PBR (partition boot record; second stage boot): ,-----------.------------------------------- | IBMIO.SYS | ... REST OF THE PARTITION ... `-----------'------------------------------- > Do I subtract 64 from the sector number while in the FreeBSD install > program under disk partitioning or are you referring to a DOS utility to > do this? OK, DM has a boot record it writes on the drives that's 63 or so sectors long (depends on the version, etc.). When this things load, instead of like a normal DOS MBR, going to the partition table embedded in itself, finding the one marked active in the partition table flags field, and loading the PBR and that booting the OS on that partition, it cheats. It loads itself in, loads up some crap as an INT 13 redirector, and does geometry translation on you. One of the the things it does is lie about where the disk starts: it pretends the disk starts after itself. THEN it loads the DOS MBR and runs it. Since it's lying about not being there, any request that somes in for a sector 'x' will have the request changed to be 'x' + 63 (or 64 or whatever) and any disk references will get the relative address instead of the real address. Now what is "OS-BS", "BootEasy", "LILO", the"OS/2 Boot Manager", etc. going to do? Well, they're supposed to replace the DOS MBR. So if you boot off the hard drive to install them, then the BIOS sees A' as "sector 0". And if you install them under DOS on a DM disk, then they will overwrite the DOS MBR. Now what happens if you boot off a floppy (oh, say a DOS floppy) and do the install? Unless the know about DM, they overwrite the DM MBR instead, because since you booted off the floppy, it didn't patch the INT 13 vecotr to hide itself. Now you are screwed. OK, now say you boot off a BSD floppy. You are still screwed, because even if it had loaded the DM MBR and patched INT 13, except for actually loading, the BSD code doesn't use the BIOS at all. Not that you could load the DM MBR anyway, if you boot off a floppy. Now BSD's new slice code knows about the DM MBR. But the installation of the MBR code does not. And the installation doesn't use BIOS, so like a raw floppy boot, it overwrites the DM MBR. The fix is to make the "OS-BS" or other boot track installation in BSD know about the DM MBR by recognizing it (it has ID crap so you can do this). OR YOU CAN INSTALL THE BOOT MANAGER AFTER BOOTING DOS OF THE HARD DRIVE. 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-bugs Wed Jun 14 15:40:01 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA02865 for bugs-outgoing; Wed, 14 Jun 1995 15:40:01 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA02858 ; Wed, 14 Jun 1995 15:40:01 -0700 Date: Wed, 14 Jun 1995 15:40:01 -0700 Message-Id: <199506142240.PAA02858@freefall.cdrom.com> From: Alan Bawden Reply-To: Alan Bawden To: freebsd-bugs Subject: kern/512: writing to bpf(loopback) causes kernel panic In-Reply-To: Your message of Wed, 14 Jun 1995 18:30:34 -0400 <199506142230.SAA00401@beandorf.epilogue.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 512 >Category: kern >Synopsis: writing to bpf(loopback) causes kernel panic >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Jun 14 15:40:00 1995 >Originator: Alan Bawden >Organization: >Release: FreeBSD 2.0-RELEASE i386 >Environment: ??? >Description: Attaching the bpf device to the loopback interface, and then attempting to write data always causes a kernel panic. It seems to have nothing to do with the validity of the data being written, although the example below is careful to write a valid ICMP packet. >How-To-Repeat: Compile and run the following program: /* Bug: writing to bpf(loopback) causes kernel panic * **DANGER** this -will- crash your machine! */ #include #include #include #include #include #include #include #include #include /* Here is ping I captured off the loopback interface. * Sending it out again shouldn't be a problem! */ char ping[] = { 0x02, 0x00, 0x00, 0x00, /* fix first word endianness later */ 0x45, 0x00, 0x00, 0x54, 0xC7, 0xB5, 0x00, 0x00, 0xFF, 0x01, 0xF5, 0xF0, /* Protocol = ICMP */ 0x7F, 0x00, 0x00, 0x01, /* 127.0.0.1 */ 0x7F, 0x00, 0x00, 0x01, /* 127.0.0.1 */ 0x08, 0x00, 0x09, 0x66, /* Type = ECHO */ 0xBE, 0x03, 0x04, 0x00, 0x73, 0x51, 0xDF, 0x2F, 0xEC, 0x11, 0x03, 0x00, 0x08, 0x09, 0x0A, 0x0B, 0x0C, 0x0D, 0x0E, 0x0F, 0x10, 0x11, 0x12, 0x13, 0x14, 0x15, 0x16, 0x17, 0x18, 0x19, 0x1A, 0x1B, 0x1C, 0x1D, 0x1E, 0x1F, 0x20, 0x21, 0x22, 0x23, 0x24, 0x25, 0x26, 0x27, 0x28, 0x29, 0x2A, 0x2B, 0x2C, 0x2D, 0x2E, 0x2F, 0x30, 0x31, 0x32, 0x33, 0x34, 0x35, 0x36, 0x37 }; void die(char *msg) { fprintf(stderr, "error %d: %s\n", errno, msg); abort(); } int main(int argc, char **argv) { int bpf; struct ifreq ifr; bpf = open("/dev/bpf0", O_RDWR, 0666); if (bpf < 0) die("open bpf0"); strncpy(ifr.ifr_name, "lo0", sizeof(ifr.ifr_name)); if (ioctl(bpf, BIOCSETIF, &ifr)) die("set interface"); * (u_long *) ping = PF_INET; if (write(bpf, &ping, sizeof(ping)) != sizeof(ping)) die("write"); exit(0); } >Fix: ??? >Audit-Trail: >Unformatted: From owner-freebsd-bugs Wed Jun 14 17:20:03 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA08150 for bugs-outgoing; Wed, 14 Jun 1995 17:20:03 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA08137 ; Wed, 14 Jun 1995 17:20:01 -0700 Date: Wed, 14 Jun 1995 17:20:01 -0700 Message-Id: <199506150020.RAA08137@freefall.cdrom.com> From: Bill Fenner Reply-To: Bill Fenner To: freebsd-bugs Subject: bin/513: Suspending and resuming vi gives TIOCGWINSIZ error In-Reply-To: Your message of Wed, 14 Jun 1995 17:11:33 PDT <199506150011.RAA00360@baobab.parc.xerox.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 513 >Category: bin >Synopsis: Suspending and resuming vi gives TIOCGWINSIZ error >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Jun 14 17:20:00 1995 >Originator: Bill Fenner >Organization: Xerox PARC >Release: FreeBSD 2.0-BUILT-19950527 i386 >Environment: FreeBSD 2.0.5-ALPHA >Description: After suspending and resuming a vi session when telnet'd in, I get: Error: TIOCGWINSZ: No such file or directory. It doesn't appear to happen when using rlogin. >How-To-Repeat: telnet freebsd-machine log in vi file ^Z fg >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Wed Jun 14 17:20:05 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA08190 for bugs-outgoing; Wed, 14 Jun 1995 17:20:05 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA08157 ; Wed, 14 Jun 1995 17:20:04 -0700 Date: Wed, 14 Jun 1995 17:20:04 -0700 Message-Id: <199506150020.RAA08157@freefall.cdrom.com> From: root@totum.muc.de Reply-To: root@totum.muc.de To: freebsd-bugs Subject: bin/514: mt & chflags must be static and/or in /bin In-Reply-To: Your message of Thu, 15 Jun 1995 02:30:08 +0200 <199506150030.CAA01331@totum.muc.de> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 514 >Category: bin >Synopsis: Crash recovery impossible without static mt/chflags. >Confidential: yes >Severity: serious >Priority: high >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: support >Submitter-Id: current-users >Arrival-Date: Wed Jun 14 17:20:02 1995 >Originator: Michael Reifenberger >Organization: Bye! ---- Michael Reifenberger >Release: FreeBSD 2.0-BUILT-19950611 i386 >Environment: Current system. >Description: o I have 2 partitions ( /, /usr) o I made backups of / and /usr onto one tape. First / then /usr. o A make install under /usr/src/lib corrupted my libc.so.2.1 o After reboot all shared bins exited with Sig11's. o I couldn'd delete libc.so.2.1 'cause of the immunitable flag. o Clearing the flag was impossible 'cause of shared chflags. The mt is independent of the chflags problem. o I could not wind tho the 2'nd backup on the Tape (the /usr backup) 'cause of the shared mt. >How-To-Repeat: See above. >Fix: Make mt and chflags at least static. mt should go into /sbin cause it is too essential for recovery. chflags should also go into /sbin 'cause progs under / have the immuntable flags set too and could therefore not be replaced if they where corrupt. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Wed Jun 14 17:38:26 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA11218 for bugs-outgoing; Wed, 14 Jun 1995 17:38:26 -0700 Received: from clark.net (rwatson@clark.net [168.143.0.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA11209 for ; Wed, 14 Jun 1995 17:38:24 -0700 Received: (rwatson@localhost) by clark.net (8.6.12/8.6.5) id UAA07231; Wed, 14 Jun 1995 20:38:17 -0400 Date: Wed, 14 Jun 1995 20:38:17 -0400 (EDT) From: Robert Watson To: bugs@freebsd.org Subject: originally a newsgroup post, but news server here isn't working Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@freebsd.org Precedence: bulk Subject: FreeBSD 2.0.5R: need disklabel help Newsgroups: comp.unix.bsd.freebsd.misc Organization: The Star-Lit BBS, Bethesda, Maryland, USA Summary: Keywords: X-Newsreader: TIN [version 1.2 PL2] My installation of 2.0.5 provied messy from the beginning -- where 2.0R installed the first time it took an epic 10attempts (and 3 trashed partition tables) to get 2.0.5R to even install the binary installation on my system. Admittadly it's a 386sx20 w/4megs of ram, but that's supposedly the min platform line or such. The problem is essentially this: 1) sysinstall has problems with memory -- first it started killing its own processed (hadn't set up swap yet, hadn't given me a chance, but was still complaining). sysinstall killed off rather vital applications, such as the newfs of the root partition, etc. Eventually this worked, but for no discernable reason. It should have worked the 3rd time running, but apparently something cleared out of memory (?). 2) Having the ppp installation line go down trashes the installation program, locking up the ppp dialer and not letting you reload a further installation. Or at the least, ppp quits, but you can't load another copy. My ppp line went down three times during the installation process (ten isntallations is a lot of time connected) since the default packet timeout was 1:30 and sometimes processing a file took longer. I also had a problem with ppp freezing or not talking to the modem. when the line went down, I typically lost my partition table and couldn't boot anything (either of my dos partitions on two drives, for example.) Thank god for Norton, which rebuilt the partitions. This isn't to say that I don't love FreeBSD ;). We run our main router on 2.0R beautifully (although its a slightly higher end machine) -- my system is a bottom end system we do installations on to see if software is reall as stable as it claims. Right now I have the binary installation on the disk, and the X installation, etc. I set up a ping process on the shell on ttyv4 during the installation to stop the ppp line from dropping, and set the timeout to an hour (assuming that would be enough.) When I got back, it had installed fine, but the system froze shortly afterwards when I tried to abort part of sysinstall. (pressing ctrl-c results in a reboot of sysinstall is locked, because answering no gets you stuck again waiting between dialogs, and yes reboots.) Sysinstall never installed my boot blocks, so I have to stick in a floppy, and at the floppies boot prompt, type in wd(1,a)/kernel. So I'm ppp'd right now, and happy, except that I can't boot the system without a floppy in the drive. I also found that no /dev/tty0? files were created for my comm ports, which left the Xconfig program confused, as it suggested /dev/tty00 as a possible mouse device, but there wasn't one (after linking random tty files to /dev/mouse, I eventually found /dev/ttyid0 for the mouse on com1.) Now I'm doing complaining, it's time for praise ;). The performance on my 386sx20 is dramatically better under 2.0.5R than 2.0R w/4 megs of ram. It swaps, but not as insanely as before ;). If the boot problem can be fixed easily (I just don't know the unix side commands to install a boot label/manager from freebsd) then I'll go ahead with my router installation (routes several ethernets -- pricingwise beats normal routers into the ground, since we don't do too much heavy stuff on our ethernets.) I assume a lot of the problems with sysinstall were RAM related -- I don't know what the processes were that died (all it reported on the debug screen was the process ids, not the names) -- they probably didn't do something they were meant to as a result, meaning some installation portions never occured. Boot assistance would be great -- I have a 230 meg FreeBSD slice on wd1 (a maxtor 540 drive) and a 130 meg dos slice on wd0 (130 meg maxtor drive) and a 270 meg and 40 meg slice on wd1 again. (eg., freebsd should boot off of wd(1,a)/kernel -- which it did one installation, only the sysinstall program never installed all of the binary installation that time ;). Thanks.. -- Robert Watson rwatson@sidwell.edu http://www.sidwell.edu/~rwatson/ The goal of science is to build better mousetraps. The goal of nature is to build better mice. Robert Watson rwatson@sidwell.edu http://www.sidwell.edu/~rwatson/ The goal of science is to build better mousetraps. The goal of nature is to build better mice. From owner-freebsd-bugs Wed Jun 14 18:06:25 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA13017 for bugs-outgoing; Wed, 14 Jun 1995 18:06:25 -0700 Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id SAA13011 for ; Wed, 14 Jun 1995 18:06:24 -0700 Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <14607(3)>; Wed, 14 Jun 1995 18:05:41 PDT Received: from localhost by crevenia.parc.xerox.com with SMTP id <49859>; Wed, 14 Jun 1995 18:05:29 -0700 X-Mailer: exmh version 1.6 4/21/95 To: Alan Bawden cc: freebsd-bugs@freefall.cdrom.com Subject: Re: kern/512: writing to bpf(loopback) causes kernel panic In-reply-to: Your message of "Wed, 14 Jun 95 15:40:01 PDT." <199506142240.PAA02858@freefall.cdrom.com> Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="===_0_Wed_Jun_14_17:46:23_PDT_1995" Date: Wed, 14 Jun 1995 18:05:27 PDT From: Bill Fenner Message-Id: <95Jun14.180529pdt.49859@crevenia.parc.xerox.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk This is a multipart MIME message. --===_0_Wed_Jun_14_17:46:23_PDT_1995 Content-Type: text/plain; charset=us-ascii In message <199506142240.PAA02858@freefall.cdrom.com> you write: > Attaching the bpf device to the loopback interface, and then > attempting to write data always causes a kernel panic. It seems > to have nothing to do with the validity of the data being written, > although the example below is careful to write a valid ICMP packet. Note that the BPF man page says ...Currently, only writes to Ethernets and SLIP links are supported. The panic is "looutput no HDR", and indeed, bpfwrite() doesn't build an mbuf chain starting with an M_PKTHDR. In addition, looutput() needs special handling for the AF_UNSPEC case. (I'd be willing to bet that SLIP, PPP, TUN, and perhaps others also need special handling...) Try these patches. (bpf should arguably know about the existance of the address family at the beginning of the written packet, but that doesn't change the user interface, just the bpf->if_loop interface. I'm trying to figure out why in the world the interface is allowed to specify the header size to bpf on attach() but during write() the size is hardcoded. sigh.) Bill % tcpdump -x -v -i lo0 & % tcpdump: listening on lo0 ./crash % 00:44:46.565013 localhost > localhost: icmp: echo request (ttl 255, id 51125) 4500 0054 c7b5 0000 ff01 f5f0 7f00 0001 7f00 0001 0800 0966 be03 0400 7351 df2f ec11 0300 0809 0a0b 0c0d 0e0f 1011 1213 1415 1617 1819 1a1b 1c1d 1e1f 2021 2223 00:44:46.565684 localhost > localhost: icmp: echo reply (ttl 255, id 770) 4500 0054 0302 0000 ff01 baa4 7f00 0001 7f00 0001 0000 1166 be03 0400 7351 df2f ec11 0300 0809 0a0b 0c0d 0e0f 1011 1213 1415 1617 1819 1a1b 1c1d 1e1f 2021 2223 --===_0_Wed_Jun_14_17:46:23_PDT_1995 Content-Type: text/plain; charset=us-ascii Content-Description: bpf.c.diff *** net/bpf.c.orig Thu Jun 15 00:11:41 1995 --- net/bpf.c Thu Jun 15 00:12:14 1995 *************** *** 192,201 **** if ((unsigned)len > MCLBYTES) return (EIO); ! MGET(m, M_WAIT, MT_DATA); if (m == 0) return (ENOBUFS); ! if (len > MLEN) { #if BSD >= 199103 MCLGET(m, M_WAIT); if ((m->m_flags & M_EXT) == 0) { --- 192,201 ---- if ((unsigned)len > MCLBYTES) return (EIO); ! MGETHDR(m, M_WAIT, MT_DATA); if (m == 0) return (ENOBUFS); ! if (len > MHLEN) { #if BSD >= 199103 MCLGET(m, M_WAIT); if ((m->m_flags & M_EXT) == 0) { *************** *** 207,213 **** goto bad; } } ! m->m_len = len; *mp = m; /* * Make room for link header. --- 207,214 ---- goto bad; } } ! m->m_pkthdr.len = m->m_len = len; ! m->m_pkthdr.rcvif = NULL; *mp = m; /* * Make room for link header. --===_0_Wed_Jun_14_17:46:23_PDT_1995 Content-Type: text/plain; charset=us-ascii Content-Description: if_loop.c.diff *** net/if_loop.c.orig Wed Jun 14 23:44:44 1995 --- net/if_loop.c Thu Jun 15 00:39:54 1995 *************** *** 124,129 **** --- 124,137 ---- panic("looutput no HDR"); ifp->if_lastchange = time; #if NBPFILTER > 0 + /* BPF write needs to be handled specially */ + if (dst->sa_family == AF_UNSPEC) { + dst->sa_family = *(mtod(m, int *)); + m->m_len -= 4; + m->m_pkthdr.len -= 4; + m->m_data += 4; + } + if (ifp->if_bpf) { /* * We need to prepend the address family as --===_0_Wed_Jun_14_17:46:23_PDT_1995-- From owner-freebsd-bugs Wed Jun 14 18:32:45 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA14280 for bugs-outgoing; Wed, 14 Jun 1995 18:32:45 -0700 Received: from whisker.internet-eireann.ie (whisker.internet-eireann.ie [194.9.34.204]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id SAA14271 for ; Wed, 14 Jun 1995 18:32:38 -0700 Received: from localhost (localhost [127.0.0.1]) by whisker.internet-eireann.ie (8.6.11/8.6.9) with SMTP id CAA01397; Thu, 15 Jun 1995 02:32:49 +0100 X-Authentication-Warning: whisker.internet-eireann.ie: Host localhost didn't use HELO protocol To: Robert Watson cc: bugs@freebsd.org Subject: Re: originally a newsgroup post, but news server here isn't working In-reply-to: Your message of "Wed, 14 Jun 1995 20:38:17 EDT." Date: Thu, 15 Jun 1995 02:32:48 +0100 Message-ID: <1394.803179968@whisker.internet-eireann.ie> From: "Jordan K. Hubbard" Sender: bugs-owner@freebsd.org Precedence: bulk > on my system. Admittadly it's a 386sx20 w/4megs of ram, but that's > supposedly the min platform line or such. Egads. I suppose I should be happy that there are people like you around to keep us honest, though frankly you're all also a big pain in the butt! :-) :-) Anyway, all joking aside, on to the reported problems. > 1) sysinstall has problems with memory -- first it started killing its > own processed (hadn't set up swap yet, hadn't given me a chance, but was This *is* with the latest 2.0.5R "UPDATES" boot floppy? As Gary announced on the mailing list, we initially made a mistake with 4MB machines and overflowed our maximum allowable kernel size. Gary pared things back down again at the last moment and stuck a boot boot floppy in place. If it's still dying WITH that floppy, then we definitely want to know about it as it means that the problem hasn't been fixed! > 2) Having the ppp installation line go down trashes the installation > program, locking up the ppp dialer and not letting you reload a further Sorry, I expect a reliable line for now and will continue to do so for the forseeable future - coding defensively for this isn't actually all that easy, and there are bigger problems I'd prefer to focus on solving anyway. Heck, 2.0R didn't even *support* a ppp installation, so I figured one that works on a reliable line was still a fair step up from none at all! :) > to an hour (assuming that would be enough.) When I got back, it had > installed fine, but the system froze shortly afterwards when I tried to > abort part of sysinstall. (pressing ctrl-c results in a reboot of Sorry, you can't really abort it effectively right now - I don't hold and process signals at checkpoints, though I may perhaps add this at some other point. > Xconfig program confused, as it suggested /dev/tty00 as a possible mouse > device, but there wasn't one (after linking random tty files to > /dev/mouse, I eventually found /dev/ttyid0 for the mouse on com1.) This is because they've been renamed for 2.0.5 (which really should be documented in a "Changes" doc someplace - argh!). /dev/cuaa0 is the ticket. > Boot assistance would be great -- I have a 230 meg FreeBSD slice on wd1 > (a maxtor 540 drive) and a 130 meg dos slice on wd0 (130 meg maxtor > drive) and a 270 meg and 40 meg slice on wd1 again. (eg., freebsd should > boot off of wd(1,a)/kernel -- which it did one installation, only the > sysinstall program never installed all of the binary installation that > time ;). Try a reinstall with the latest, if you haven't already done so, and select the boot manager option. Try to also be sure of each step in advance; sysinstall isn't very fault-tolerant right now and it works fairly well in most instances if you say just the right things to it. :-) Jordan From owner-freebsd-bugs Wed Jun 14 19:40:03 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA16455 for bugs-outgoing; Wed, 14 Jun 1995 19:40:03 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA16447 ; Wed, 14 Jun 1995 19:40:02 -0700 Date: Wed, 14 Jun 1995 19:40:02 -0700 Message-Id: <199506150240.TAA16447@freefall.cdrom.com> From: "Jordan K. Hubbard" Reply-To: "Jordan K. Hubbard" To: freebsd-bugs Subject: gnu/515: Info command has no tutorial In-Reply-To: Your message of Thu, 15 Jun 1995 03:33:38 +0100 <199506150233.DAA01703@whisker.internet-eireann.ie> Sender: bugs-owner@freebsd.org Precedence: bulk >Number: 515 >Category: gnu >Synopsis: Info command has no tutorial >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Jun 14 19:40:01 1995 >Originator: Jordan K. Hubbard >Organization: FreeBSD Project >Release: FreeBSD 2.0-BUILT-19950603 i386 >Environment: info command on newly installed 2.0.5R system >Description: Use the `h' command in the info program; you will get: Cannot find the node "(Info)Help-Small-Screen". >How-To-Repeat: >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Wed Jun 14 20:11:46 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA17417 for bugs-outgoing; Wed, 14 Jun 1995 20:11:46 -0700 Received: from clark.net (rwatson@clark.net [168.143.0.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id UAA17411 ; Wed, 14 Jun 1995 20:11:43 -0700 Received: (rwatson@localhost) by clark.net (8.6.12/8.6.5) id XAA17966; Wed, 14 Jun 1995 23:11:40 -0400 Date: Wed, 14 Jun 1995 23:11:40 -0400 (EDT) From: Robert Watson To: "Jordan K. Hubbard" cc: bugs@freebsd.org Subject: Re: originally a newsgroup post, but news server here isn't working In-Reply-To: <1394.803179968@whisker.internet-eireann.ie> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@freebsd.org Precedence: bulk Sorry to quote your entire email, but I'm currently running under XFree86 on the same 386sx20 w/4megs of ram, a 14.4 ppp line ftping the kernel source dist. As you might imagine, the keystrokes are a little bit slow to appear (though that's actually mostly the ppp line being overrun by ftp packets ;). Other than the 5 minute startup time on X, and removing the window manager and other useless memory hogs (;) it doesn't run too badly. When I moved the window managing to a remote system (olwm on a sparcstation ten) it really sped up (and that over a ppp line ;). Anyhow, enough of the pushing-the-reasonable-limits-of-any-sane--system.. This is the version on the UPDATES floppy that I used. The initial version didn't even boot, unlike this version which boots and does some of its intended actions. At this point I'm a little hesitant to reinstall again from scratch, because over this ppp line its about 6 hours a throw, and I've lost my dos partition several times so far. Speaking of which, there may be a bug in your dos partition handling -- once I rebooted and booted dos, I discovered a looped directory pointer -- I have d: mounted to /dos under freebsd, and had a /bin directory in it. When I next looked under dos, there was a bi directory entry in bi pointing back to bin again. under dos you can cd for a while (getting bin\bin\... until you run out of path space) -- under FreeBSD it won't allow the installation to continue. This wasn't there prior to freebsd, so it might be the dos handling routines (or it might be the memory lack or any number of things.) I fixed it up quickly with norton disk editor and then ran ndd and it picked up the rest. At this point, from my point of view, the best possible thing would be quick instructions as to how to make the boot manager load onto wd0 so I could boot freebsd off of wd1/a. Right now it just goes straight to dos booting off of c: (wd0) but if I stick in the boot floppy, boot to the boot manager, and tell it wd(1/a) it boots to freebsd fine. So I just lost the boot manager/boot block somewhere along the way. The man pages aren't exactly clear as to how to just arbitrarily stick in a boot manager (unlike dos's sys/fdisk/mbr, etc). If you want, I can try and pursuade the boot disk to reproduce the trash-the-partition table bug, but I'm not sure I want to ;). I believe it just happens when I tell the partition editor in sysinstall to view wd0 (which won't contain any unix stuff but a boot manager), set the dos partition as bootable (btw, my primary on wd0 (dos primary) doesn't show up as dos -- it shows up as unused under the partition manager.) Anyhow, I'm just sitting here babbling away watching keys show up occasinoally. If you could send me a list of specific things to watch for debugging wise, or such, I'd gladly write them down and mail them to you as things progress. I'll even trash my dos partitions a few more times.. Just let me know ;). Sorry for any hassle this is causing you.. Robert Watson rwatson@sidwell.edu http://www.sidwell.edu/~rwatson/ The goal of science is to build better mousetraps. The goal of nature is to build better mice. On Thu, 15 Jun 1995, Jordan K. Hubbard wrote: > > on my system. Admittadly it's a 386sx20 w/4megs of ram, but that's > > supposedly the min platform line or such. > > Egads. I suppose I should be happy that there are people like you > around to keep us honest, though frankly you're all also a big pain in > the butt! :-) :-) > > Anyway, all joking aside, on to the reported problems. > > > 1) sysinstall has problems with memory -- first it started killing its > > own processed (hadn't set up swap yet, hadn't given me a chance, but was > > This *is* with the latest 2.0.5R "UPDATES" boot floppy? As Gary > announced on the mailing list, we initially > made a mistake with 4MB machines and overflowed our maximum allowable > kernel size. Gary pared things back down again at the last moment and > stuck a boot boot floppy in place. If it's still dying WITH that > floppy, then we definitely want to know about it as it means that the > problem hasn't been fixed! > > > 2) Having the ppp installation line go down trashes the installation > > program, locking up the ppp dialer and not letting you reload a further > > Sorry, I expect a reliable line for now and will continue to do so for > the forseeable future - coding defensively for this isn't actually all > that easy, and there are bigger problems I'd prefer to focus on > solving anyway. Heck, 2.0R didn't even *support* a ppp installation, > so I figured one that works on a reliable line was still a fair step > up from none at all! :) > > > to an hour (assuming that would be enough.) When I got back, it had > > installed fine, but the system froze shortly afterwards when I tried to > > abort part of sysinstall. (pressing ctrl-c results in a reboot of > > Sorry, you can't really abort it effectively right now - I don't hold > and process signals at checkpoints, though I may perhaps add this at > some other point. > > > Xconfig program confused, as it suggested /dev/tty00 as a possible mouse > > device, but there wasn't one (after linking random tty files to > > /dev/mouse, I eventually found /dev/ttyid0 for the mouse on com1.) > > This is because they've been renamed for 2.0.5 (which really should be > documented in a "Changes" doc someplace - argh!). /dev/cuaa0 is the > ticket. > > > Boot assistance would be great -- I have a 230 meg FreeBSD slice on wd1 > > (a maxtor 540 drive) and a 130 meg dos slice on wd0 (130 meg maxtor > > drive) and a 270 meg and 40 meg slice on wd1 again. (eg., freebsd should > > boot off of wd(1,a)/kernel -- which it did one installation, only the > > sysinstall program never installed all of the binary installation that > > time ;). > > Try a reinstall with the latest, if you haven't already done so, and > select the boot manager option. Try to also be sure of each step in > advance; sysinstall isn't very fault-tolerant right now and it works > fairly well in most instances if you say just the right things to > it. :-) > > Jordan > From owner-freebsd-bugs Wed Jun 14 20:13:25 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA17523 for bugs-outgoing; Wed, 14 Jun 1995 20:13:25 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id UAA17517 for ; Wed, 14 Jun 1995 20:13:20 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id NAA27850; Thu, 15 Jun 1995 13:09:11 +1000 Date: Thu, 15 Jun 1995 13:09:11 +1000 From: Bruce Evans Message-Id: <199506150309.NAA27850@godzilla.zeta.org.au> To: hlew@genome.Stanford.EDU, terry@cs.weber.edu Subject: Re: 2.05R panics on boot Cc: bugs@FreeBSD.org Sender: bugs-owner@FreeBSD.org Precedence: bulk >The DOS MBR: >,------.---------------------.-------------------. >| JUMP | DOS PARTITION TABLE | DOS MBR BOOT CODE | >`------'---------------------'-------------------' >The DM MBR: >.------.-------------------------.---------------. >| JUMP | FAKE DOS PARTIOTN TABLE | DM MAGIC CODE | >`------'-------------------------'---------------' There is code between the JUMP and the PARTITION TABLE too. >The PBR (partition boot record; second stage boot): >> Do I subtract 64 from the sector number while in the FreeBSD install >> program under disk partitioning or are you referring to a DOS utility to >> do this? A driver should subtract it. >OK, DM has a boot record it writes on the drives that's 63 or so sectors >long (depends on the version, etc.). FreeBSD assumes the fixed value 63 (for DM partition type 84). >Now what is "OS-BS", "BootEasy", "LILO", the"OS/2 Boot Manager", etc. going >to do? >... >OK, now say you boot off a BSD floppy. >You are still screwed, because even if it had loaded the DM MBR and patched >INT 13, except for actually loading, the BSD code doesn't use the BIOS >at all. Not that you could load the DM MBR anyway, if you boot off a >floppy. >Now BSD's new slice code knows about the DM MBR. But the installation >of the MBR code does not. Yes it does (modulo bugs). Only one case can't possibly work: loading the bootstrap off a floppy and then attempting to boot from a hard disk (e.g., by typing sd(1,a)/kernel). The boot code doesn't know about DM, so it won't work if DM needs to be loaded. Bruce From owner-freebsd-bugs Wed Jun 14 21:24:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA19966 for bugs-outgoing; Wed, 14 Jun 1995 21:24:02 -0700 Received: from westhill.cdrom.com (westhill.cdrom.com [192.216.223.147]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id VAA19959 ; Wed, 14 Jun 1995 21:24:01 -0700 Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by westhill.cdrom.com (8.6.11/8.6.11) with SMTP id VAA03509 ; Wed, 14 Jun 1995 21:24:00 -0700 X-Authentication-Warning: westhill.cdrom.com: Host localhost.cdrom.com didn't use HELO protocol To: "Jordan K. Hubbard" cc: Robert Watson , bugs@freebsd.org Subject: Re: originally a newsgroup post, but news server here isn't working In-reply-to: Your message of "Thu, 15 Jun 1995 02:32:48 BST." <1394.803179968@whisker.internet-eireann.ie> Date: Wed, 14 Jun 1995 21:23:59 -0700 Message-ID: <3507.803190239@westhill.cdrom.com> From: Gary Palmer Sender: bugs-owner@freebsd.org Precedence: bulk In message <1394.803179968@whisker.internet-eireann.ie>, "Jordan K. Hubbard" wr ites: >This *is* with the latest 2.0.5R "UPDATES" boot floppy? As Gary >announced on the mailing list, we initially >made a mistake with 4MB machines and overflowed our maximum allowable >kernel size. Gary pared things back down again at the last moment and >stuck a boot boot floppy in place. If it's still dying WITH that >floppy, then we definitely want to know about it as it means that the >problem hasn't been fixed! Just to let people know, the new boot floppy DOES work - I've just installed 2.0.5-RELEASE (from an updated floppy) on a 4Mb 486DX2 66 with an Adaptec 1540C card WITHOUT PROBLEM. However, it does have a 4Gb hard drive (it's one of our CDROM burner boxes, so it needs lots of disk space to hold CDROM images), so I gave it 32Mb swap space. If I can find a machine which I can spam a lot without affecting peoples work here, I'll see what the minumum swap you can have on a 4Mb machine is without sysinstall falling over. N.B. As I know the install system BACKWARDS, I didn't reference (i.e. look at) any docs. This may be a crucial point as the way the docs are loaded is, err, interesting. Gary From owner-freebsd-bugs Wed Jun 14 23:34:28 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA27100 for bugs-outgoing; Wed, 14 Jun 1995 23:34:28 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA27092 ; Wed, 14 Jun 1995 23:34:16 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id QAA01865; Thu, 15 Jun 1995 16:30:58 +1000 Date: Thu, 15 Jun 1995 16:30:58 +1000 From: Bruce Evans Message-Id: <199506150630.QAA01865@godzilla.zeta.org.au> To: jkh@FreeBSD.org, rwatson@clark.net Subject: Re: originally a newsgroup post, but news server here isn't working Cc: bugs@FreeBSD.org Sender: bugs-owner@FreeBSD.org Precedence: bulk >At this point I'm a little hesitant to reinstall again from scratch, >because over this ppp line its about 6 hours a throw, and I've lost my >dos partition several times so far. Speaking of which, there may be a >bug in your dos partition handling -- once I rebooted and booted dos, I >discovered a looped directory pointer -- I have d: mounted to /dos under >freebsd, and had a /bin directory in it. When I next looked under dos, >there was a bi directory entry in bi pointing back to bin again. under Renaming of directories is quite broken for msdosfs. The following would create a looped directory: cd /dos mv bin bi # where bin is a dir and bi doesn't exist This destroys the "." entry in bin by overwriting it with "bi". >At this point, from my point of view, the best possible thing would be >quick instructions as to how to make the boot manager load onto wd0 so I >could boot freebsd off of wd1/a. Right now it just goes straight to dos >booting off of c: (wd0) but if I stick in the boot floppy, boot to the >boot manager, and tell it wd(1/a) it boots to freebsd fine. So I just Er, the program that you tell wd(1,a) too isn't a boot manager. It's just the FreeBSD boot loader. Once it is loaded, it can boot from any partition on the first FreeBSD slice on any drive (except DiskManaged hard drives when the DM software hasn't been loaded by a previous stage in the bootstrap, e.g., after booting from a FreeBSD floppy). You need a disk manager on the MBR or on its own partition to load the FreeBSD boot loader if the FreeBSD slice isn't active. Bruce From owner-freebsd-bugs Thu Jun 15 01:00:18 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA28928 for bugs-outgoing; Thu, 15 Jun 1995 01:00:18 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA28918 ; Thu, 15 Jun 1995 01:00:17 -0700 Date: Thu, 15 Jun 1995 01:00:17 -0700 Message-Id: <199506150800.BAA28918@freefall.cdrom.com> From: tim@sarc.city.ac.uk Reply-To: tim@sarc.city.ac.uk To: freebsd-bugs Subject: kern/516: Crynwr compatibility mode for PLIP driver. In-Reply-To: Your message of Thu, 15 Jun 1995 08:52:53 +0100 <199506150752.IAA10916@cripplecock.sarc.city.ac.uk> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 516 >Category: kern >Synopsis: Crynwr compatibility mode for PLIP driver. >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: support >Submitter-Id: current-users >Arrival-Date: Thu Jun 15 01:00:01 1995 >Originator: Tim Wilkinson >Organization: Systems Architecture Research Centre, City Uni. UK >Release: FreeBSD 2.0.5-RELEASE i386 >Environment: >Description: The PLIP driver (IP over the printer port) does not conform to the "standard" used by Crynwr (and Linux I think). >How-To-Repeat: >Fix: In the spirit of the comments in lpt.c, I've added a Crynwr compatibility mode to enable PLIP to talk to DOS programs which use the Crynwr PLIP driver. The mode is enabled using the link0 option to ifconfig otherwise the driver remains compaitible with the old verion. Find the patch enclosed. *** lpt.orig Wed Jun 14 08:44:11 1995 --- lpt.c Wed Jun 14 15:38:41 1995 *************** *** 62,69 **** * This driver sends two bytes (0x08, 0x00) in front of each packet, * to allow us to distinguish another format later. * * TODO: - * Make Linux/Crynwr compatible mode, use IF_LLC0 to enable. * Make HDLC/PPP mode, use IF_LLC1 to enable. * * Connect the two computers using a Laplink parallel cable to use this --- 62,71 ---- * This driver sends two bytes (0x08, 0x00) in front of each packet, * to allow us to distinguish another format later. * + * Now added an Linux/Crynwr compatibility mode which is enabled using + * IF_LINK0 - Tim Wilkinson. + * * TODO: * Make HDLC/PPP mode, use IF_LLC1 to enable. * * Connect the two computers using a Laplink parallel cable to use this *************** *** 102,107 **** --- 104,111 ---- #include "lpt.h" #if NLPT > 0 + #define CRYNWR_COMPAT /* Include Crynwr compatible PLIP driver */ + #include #include #include *************** *** 132,137 **** --- 136,144 ---- #include #include #include + #ifdef CRYNWR_COMPAT + #include + #endif #endif /* INET */ #define LPINITRDY 4 /* wait up to 4 seconds for a ready */ *************** *** 156,164 **** #define LPMAXERRS 100 #endif #define LPIPHDRLEN 2 /* We send 0x08, 0x00 in front of packet */ - #define LPIPTBLSIZE 256 /* Size of octet translation table */ #define LPIP_SHAKE 0x40 /* This bit toggles between nibble reception */ #endif /* INET */ --- 163,183 ---- #define LPMAXERRS 100 #endif + #ifdef CRYNWR_COMPAT + + #define CLPIPHDRLEN 14 /* We send dummy ethernet addresses (two) + packet type in front of packet */ + #define CLPIP_SHAKE 0x80 /* This bit toggles between nibble reception */ + #define MLPIPHDRLEN CLPIPHDRLEN + + #endif /* CRYNWR_COMPAT */ + #define LPIPHDRLEN 2 /* We send 0x08, 0x00 in front of packet */ #define LPIP_SHAKE 0x40 /* This bit toggles between nibble reception */ + #if !defined(MLPIPHDRLEN) || LPIPHDRLEN > MLPIPHDRLEN + #define MLPIPHDRLEN LPIPHDRLEN + #endif + + #define LPIPTBLSIZE 256 /* Size of octet translation table */ #endif /* INET */ *************** *** 245,250 **** --- 264,276 ---- #define trecvh (txmith+(2*LPIPTBLSIZE)) #define trecvl (txmith+(3*LPIPTBLSIZE)) + #ifdef CRYNWR_COMPAT + static u_char *ctxmith; + #define ctxmitl (ctxmith+(1*LPIPTBLSIZE)) + #define ctrecvh (ctxmith+(2*LPIPTBLSIZE)) + #define ctrecvl (ctxmith+(3*LPIPTBLSIZE)) + #endif /* CRYNWR_COMPAT */ + /* Functions for the lp# interface */ static void lpattach(struct lpt_softc *,int); static int lpinittables(); *************** *** 851,856 **** --- 877,899 ---- if (!txmith) return 1; + #ifdef CRYNWR_COMPAT + + if (!ctxmith) + ctxmith = malloc(4*LPIPTBLSIZE, M_DEVBUF, M_NOWAIT); + + if (!ctxmith) + return 1; + + for (i=0; i < LPIPTBLSIZE; i++) { + ctxmith[i] = (i & 0xF0) >> 4; + ctxmitl[i] = 0x10 | (i & 0x0F); + ctrecvh[i] = (i & 0x78) << 1; + ctrecvl[i] = (i & 0x78) >> 3; + } + + #endif /* CRYNWR_COMPAT */ + for (i=0; i < LPIPTBLSIZE; i++) { txmith[i] = ((i & 0x80) >> 3) | ((i & 0x70) >> 4) | 0x08; txmitl[i] = ((i & 0x08) << 1) | (i & 0x07); *************** *** 892,898 **** if (((ifp->if_flags & IFF_UP)) && (!(ifp->if_flags & IFF_RUNNING))) { if (lpinittables()) return ENOBUFS; ! sc->sc_ifbuf = malloc(sc->sc_if.if_mtu + LPIPHDRLEN, M_DEVBUF, M_WAITOK); if (!sc->sc_ifbuf) return ENOBUFS; --- 935,941 ---- if (((ifp->if_flags & IFF_UP)) && (!(ifp->if_flags & IFF_RUNNING))) { if (lpinittables()) return ENOBUFS; ! sc->sc_ifbuf = malloc(sc->sc_if.if_mtu + MLPIPHDRLEN, M_DEVBUF, M_WAITOK); if (!sc->sc_ifbuf) return ENOBUFS; *************** *** 904,910 **** case SIOCSIFMTU: ptr = sc->sc_ifbuf; ! sc->sc_ifbuf = malloc(ifr->ifr_metric+LPIPHDRLEN, M_DEVBUF, M_NOWAIT); if (!sc->sc_ifbuf) { sc->sc_ifbuf = ptr; return ENOBUFS; --- 947,953 ---- case SIOCSIFMTU: ptr = sc->sc_ifbuf; ! sc->sc_ifbuf = malloc(ifr->ifr_metric+MLPIPHDRLEN, M_DEVBUF, M_NOWAIT); if (!sc->sc_ifbuf) { sc->sc_ifbuf = ptr; return ENOBUFS; *************** *** 925,930 **** --- 968,1015 ---- return 0; } + #ifdef CRYNWR_COMPAT + + static inline int + clpoutbyte (u_char byte, int spin, int data_port, int status_port) + { + outb(data_port, ctxmitl[byte]); + while (inb(status_port) & CLPIP_SHAKE) + if (--spin == 0) { + return 1; + } + outb(data_port, ctxmith[byte]); + while (!(inb(status_port) & CLPIP_SHAKE)) + if (--spin == 0) { + return 1; + } + return 0; + } + + static inline int + clpinbyte (int spin, int data_port, int status_port) + { + int c, cl; + + while((inb(status_port) & CLPIP_SHAKE)) + if(!--spin) { + return -1; + } + cl = inb(status_port); + outb(data_port, 0x10); + + while(!(inb(status_port) & CLPIP_SHAKE)) + if(!--spin) { + return -1; + } + c = inb(status_port); + outb(data_port, 0x00); + + return (ctrecvl[cl] | ctrecvh[c]); + } + + #endif /* CRYNWR_COMPAT */ + static void lpintr (int unit) { *************** *** 939,944 **** --- 1024,1084 ---- s = splhigh(); + #ifdef CRYNWR_COMPAT + + if (sc->sc_if.if_flags & IFF_LINK0) { + + /* Ack. the request */ + outb(lpt_data_port, 0x01); + + /* Get the packet length */ + j = clpinbyte(LPMAXSPIN2, lpt_data_port, lpt_stat_port); + if (j == -1) + goto err; + len = j; + j = clpinbyte(LPMAXSPIN2, lpt_data_port, lpt_stat_port); + if (j == -1) + goto err; + len = len + (j << 8); + + bp = sc->sc_ifbuf; + + while (len--) { + j = clpinbyte(LPMAXSPIN2, lpt_data_port, lpt_stat_port); + if (j == -1) { + goto err; + } + *bp++ = j; + } + /* Get and ignore checksum */ + j = clpinbyte(LPMAXSPIN2, lpt_data_port, lpt_stat_port); + if (j == -1) { + goto err; + } + + len = bp - sc->sc_ifbuf; + if (len <= CLPIPHDRLEN) + goto err; + + sc->sc_iferrs = 0; + + if (IF_QFULL(&ipintrq)) { + lprintf("DROP"); + IF_DROP(&ipintrq); + goto done; + } + len -= CLPIPHDRLEN; + sc->sc_if.if_ipackets++; + sc->sc_if.if_ibytes += len; + top = m_devget(sc->sc_ifbuf + CLPIPHDRLEN, len, 0, &sc->sc_if, 0); + if (top) { + IF_ENQUEUE(&ipintrq, top); + schednetisr(NETISR_IP); + } + goto done; + } + #endif /* CRYNWR_COMPAT */ + while ((inb(lpt_stat_port) & LPIP_SHAKE)) { len = sc->sc_if.if_mtu + LPIPHDRLEN; bp = sc->sc_ifbuf; *************** *** 1014,1029 **** static inline int lpoutbyte (u_char byte, int spin, int data_port, int status_port) { ! outb(data_port, txmith[byte]); ! while (!(inb(status_port) & LPIP_SHAKE)) ! if (--spin == 0) ! return 1; ! outb(data_port, txmitl[byte]); ! while (inb(status_port) & LPIP_SHAKE) ! if (--spin == 0) ! return 1; ! ! return 0; } static int --- 1154,1168 ---- static inline int lpoutbyte (u_char byte, int spin, int data_port, int status_port) { ! outb(data_port, txmith[byte]); ! while (!(inb(status_port) & LPIP_SHAKE)) ! if (--spin == 0) ! return 1; ! outb(data_port, txmitl[byte]); ! while (inb(status_port) & LPIP_SHAKE) ! if (--spin == 0) ! return 1; ! return 0; } static int *************** *** 1037,1042 **** --- 1176,1187 ---- int s, err; struct mbuf *mm; u_char *cp = "\0\0"; + #ifdef CRYNWR_COMPAT + u_char chksum = 0; + int count = 0; + int i; + int spin; + #endif /* CRYNWR_COMPAT */ /* We need a sensible value if we abort */ cp++; *************** *** 1049,1075 **** /* Suspend (on laptops) or receive-errors might have taken us offline */ outb(lpt_ctrl_port, LPC_ENA); if (inb(lpt_stat_port) & LPIP_SHAKE) { ! lprintf("&"); ! lptintr(ifp->if_unit); } if (lpoutbyte(0x08, LPMAXSPIN1, lpt_data_port, lpt_stat_port)) ! goto end; if (lpoutbyte(0x00, LPMAXSPIN2, lpt_data_port, lpt_stat_port)) ! goto end; mm = m; do { ! cp = mtod(mm,u_char *); ! while (mm->m_len--) if (lpoutbyte(*cp++, LPMAXSPIN2, lpt_data_port, lpt_stat_port)) ! goto end; } while ((mm = mm->m_next)); err = 0; /* no errors were encountered */ ! end: --cp; outb(lpt_data_port, txmitl[*cp] ^ 0x17); --- 1194,1302 ---- /* Suspend (on laptops) or receive-errors might have taken us offline */ outb(lpt_ctrl_port, LPC_ENA); + #ifdef CRYNWR_COMPAT + + if (ifp->if_flags & IFF_LINK0) { + + if (!(inb(lpt_stat_port) & CLPIP_SHAKE)) { + lprintf("&"); + lptintr(ifp->if_unit); + } + + /* Alert other end to pending packet */ + spin = LPMAXSPIN1; + outb(lpt_data_port, 0x08); + while ((inb(lpt_stat_port) & 0x08) == 0) + if (--spin == 0) { + goto nend; + } + + /* Calculate length of packet, then send that */ + + count += 14; /* Ethernet header len */ + + mm = m; + for (mm = m; mm; mm = mm->m_next) { + count += mm->m_len; + } + if (clpoutbyte(count & 0xFF, LPMAXSPIN1, lpt_data_port, lpt_stat_port)) + goto nend; + if (clpoutbyte((count >> 8) & 0xFF, LPMAXSPIN1, lpt_data_port, lpt_stat_port)) + goto nend; + + /* Send dummy ethernet header */ + for (i = 0; i < 12; i++) { + if (clpoutbyte(i, LPMAXSPIN1, lpt_data_port, lpt_stat_port)) + goto nend; + chksum += i; + } + + if (clpoutbyte(0x08, LPMAXSPIN1, lpt_data_port, lpt_stat_port)) + goto nend; + if (clpoutbyte(0x00, LPMAXSPIN1, lpt_data_port, lpt_stat_port)) + goto nend; + chksum += 0x08 + 0x00; /* Add into checksum */ + + mm = m; + do { + cp = mtod(mm, u_char *); + while (mm->m_len--) { + chksum += *cp; + if (clpoutbyte(*cp++, LPMAXSPIN2, lpt_data_port, lpt_stat_port)) + goto nend; + } + } while ((mm = mm->m_next)); + + /* Send checksum */ + if (clpoutbyte(chksum, LPMAXSPIN2, lpt_data_port, lpt_stat_port)) + goto nend; + + /* Go quiescent */ + outb(lpt_data_port, 0); + + err = 0; /* No errors */ + + nend: + if (err) { /* if we didn't timeout... */ + ifp->if_oerrors++; + lprintf("X"); + } else { + ifp->if_opackets++; + ifp->if_obytes += m->m_pkthdr.len; + } + + m_freem(m); + + if (!(inb(lpt_stat_port) & CLPIP_SHAKE)) { + lprintf("^"); + lptintr(ifp->if_unit); + } + (void) splx(s); + return 0; + } + #endif /* CRYNWR_COMPAT */ + if (inb(lpt_stat_port) & LPIP_SHAKE) { ! lprintf("&"); ! lptintr(ifp->if_unit); } if (lpoutbyte(0x08, LPMAXSPIN1, lpt_data_port, lpt_stat_port)) ! goto end; if (lpoutbyte(0x00, LPMAXSPIN2, lpt_data_port, lpt_stat_port)) ! goto end; mm = m; do { ! cp = mtod(mm,u_char *); ! while (mm->m_len--) if (lpoutbyte(*cp++, LPMAXSPIN2, lpt_data_port, lpt_stat_port)) ! goto end; } while ((mm = mm->m_next)); err = 0; /* no errors were encountered */ ! end: --cp; outb(lpt_data_port, txmitl[*cp] ^ 0x17); >Audit-Trail: >Unformatted: From owner-freebsd-bugs Thu Jun 15 01:10:27 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA29499 for bugs-outgoing; Thu, 15 Jun 1995 01:10:27 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA29481 ; Thu, 15 Jun 1995 01:10:17 -0700 Date: Thu, 15 Jun 1995 01:10:17 -0700 Message-Id: <199506150810.BAA29481@freefall.cdrom.com> From: tim@sarc.city.ac.uk Reply-To: tim@sarc.city.ac.uk To: freebsd-bugs Subject: bin/517: Bad group change with 'install' In-Reply-To: Your message of Thu, 15 Jun 1995 09:03:13 +0100 <199506150803.JAA11210@cripplecock.sarc.city.ac.uk> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 517 >Category: bin >Synopsis: Bad group change with 'install' >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jun 15 01:10:01 1995 >Originator: Tim Wilkinson >Organization: Systems Architecture Research Centre, City Uni. UK. >Release: FreeBSD 2.0.5-RELEASE i386 >Environment: >Description: When using 'install' to install software, the '-g' option does not change the group correctly if the owner is also being set and the /etc/group file is being checked because of "+groupname" entries in the /etc/passwd file. Essentially, the information returned by 'getgrnam' is being overwritten by the subsequent call to 'getpwnam' (which inturn calls 'getgrnam'). >How-To-Repeat: Add an entry at then end of the password file such as "+operator:*:0:0:::" then use "install -o root -g kmem" to install a program. The installed program will not get the correct group set. >Fix: The patch below just avoids the problem by changing the order ot the calls to getgrnam and getpwnam so the group information isn't overwritten. This is not so much a fix as a hastily applied bit of sticky tape. *** xinstall.c.orig Thu Jun 15 08:19:11 1995 --- xinstall.c Thu Jun 15 08:19:15 1995 *************** *** 123,132 **** usage(); /* get group and owner id's */ - if (group && !(gp = getgrnam(group))) - err("unknown group %s", group); if (owner && !(pp = getpwnam(owner))) err("unknown user %s", owner); no_target = stat(to_name = argv[argc - 1], &to_sb); if (!no_target && (to_sb.st_mode & S_IFMT) == S_IFDIR) { --- 123,132 ---- usage(); /* get group and owner id's */ if (owner && !(pp = getpwnam(owner))) err("unknown user %s", owner); + if (group && !(gp = getgrnam(group))) + err("unknown group %s", group); no_target = stat(to_name = argv[argc - 1], &to_sb); if (!no_target && (to_sb.st_mode & S_IFMT) == S_IFDIR) { >Audit-Trail: >Unformatted: From owner-freebsd-bugs Thu Jun 15 02:10:27 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA01164 for bugs-outgoing; Thu, 15 Jun 1995 02:10:27 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA01156 ; Thu, 15 Jun 1995 02:10:17 -0700 Date: Thu, 15 Jun 1995 02:10:17 -0700 Message-Id: <199506150910.CAA01156@freefall.cdrom.com> From: knarf@nasim.cube.net Reply-To: knarf@nasim.cube.net To: freebsd-bugs Subject: bin/518: passwd asks YP-Server for unknown user In-Reply-To: Your message of Thu, 15 Jun 1995 00:15:12 +0200 <199506142215.AAA07374@ivanhoe.nasim.cube.net> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 518 >Category: bin >Synopsis: passwd asks YP-Server for unknown user >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jun 15 02:10:01 1995 >Originator: Frank Bartels >Organization: Frank Bartels | UUCP/ZModem/Fax: + 49 89 5469593 | MiNT is knarf@nasim.cube.net | Login: nuucp Index: /pub/ls-lR.nasim.gz | Now TOS! >Release: FreeBSD 2.0-BUILT-19950527 i386 >Environment: 2.0.5-ALPHA, also 2.0.5-RELEASE, no YP configured. >Description: When I try to change the passwd for an nonexistant user, I get: ivanhoe:/root# passwd foobar yppasswd: can't find the master ypserver: Request arguments bad With 2.0-RELEASE I get the correct message: sogand:/root# passwd foobar passwd: unknown user foobar >How-To-Repeat: passwd foobar >Fix: Setup an YP server? ;) >Audit-Trail: >Unformatted: From owner-freebsd-bugs Thu Jun 15 04:41:41 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA04006 for bugs-outgoing; Thu, 15 Jun 1995 04:41:41 -0700 Received: from clark.net (rwatson@clark.net [168.143.0.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA04000 ; Thu, 15 Jun 1995 04:41:40 -0700 Received: (rwatson@localhost) by clark.net (8.6.12/8.6.5) id HAA18949; Thu, 15 Jun 1995 07:41:35 -0400 Date: Thu, 15 Jun 1995 07:41:35 -0400 (EDT) From: Robert Watson To: Gary Palmer cc: "Jordan K. Hubbard" , bugs@freebsd.org Subject: Re: originally a newsgroup post, but news server here isn't working In-Reply-To: <3507.803190239@westhill.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@freebsd.org Precedence: bulk I loaded with 16 megs of swap on wd1s2b -- the first time I tried to install, it didn't make it to mounting the swap before conking out.. It might be the docs -- sometimes when I tried pressing f1 for help it would show the docs -- sometimes some of the docs (eg., it would break off some way into them), and sometimes it would tell me that the help file (for the slices, for example) wasn't included on this boot floppy (although later I viewed them fine?). After I had some initial labels written, it started mounting the swap fine (after a boot or two.) Once the swap was mounted on a fresh boot, three processes were killed every time through by vm_pager for lack of swap before swap was loaded, but later stuff (like newfs) survived. Essentially, if I looked at the debug screen while dialing out with term under ppp, I'd see that three processes had been killed. BTW, the in kernel config stuff (-c) is great.. just configured my ethernet card with no hassles ;). I'll recompile and trim the kernel anyway though, given my distinct lack of ram. FreeBSD under 4 megs (text) is pretty snappy though.. I was pleasently surprised. X was a little slow (not surprisingly) -- but I found that it worked fine as long as I tried not to load too many processes locally. If I went to a window manager off-system, killed all but one xterm, and only used that for transport to other systems and to play with authentification, It went reasonably well (although the window manager performance over a PPP line was sluggish ;). Amazing what you can do on a 386 ;). Robert Watson rwatson@sidwell.edu http://www.sidwell.edu/~rwatson/ The goal of science is to build better mousetraps. The goal of nature is to build better mice. On Wed, 14 Jun 1995, Gary Palmer wrote: > In message <1394.803179968@whisker.internet-eireann.ie>, "Jordan K. Hubbard" wr > ites: > >This *is* with the latest 2.0.5R "UPDATES" boot floppy? As Gary > >announced on the mailing list, we initially > >made a mistake with 4MB machines and overflowed our maximum allowable > >kernel size. Gary pared things back down again at the last moment and > >stuck a boot boot floppy in place. If it's still dying WITH that > >floppy, then we definitely want to know about it as it means that the > >problem hasn't been fixed! > > Just to let people know, the new boot floppy DOES work - I've just > installed 2.0.5-RELEASE (from an updated floppy) on a 4Mb 486DX2 66 > with an Adaptec 1540C card WITHOUT PROBLEM. However, it does have a > 4Gb hard drive (it's one of our CDROM burner boxes, so it needs lots > of disk space to hold CDROM images), so I gave it 32Mb swap space. If > I can find a machine which I can spam a lot without affecting peoples > work here, I'll see what the minumum swap you can have on a 4Mb > machine is without sysinstall falling over. > > N.B. As I know the install system BACKWARDS, I didn't reference > (i.e. look at) any docs. This may be a crucial point as the way the > docs are loaded is, err, interesting. > > Gary > > From owner-freebsd-bugs Thu Jun 15 04:47:51 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA04280 for bugs-outgoing; Thu, 15 Jun 1995 04:47:51 -0700 Received: from clark.net (rwatson@clark.net [168.143.0.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA04270 ; Thu, 15 Jun 1995 04:47:49 -0700 Received: (rwatson@localhost) by clark.net (8.6.12/8.6.5) id HAA19947; Thu, 15 Jun 1995 07:46:53 -0400 Date: Thu, 15 Jun 1995 07:46:53 -0400 (EDT) From: Robert Watson To: Bruce Evans cc: jkh@FreeBSD.org, bugs@FreeBSD.org Subject: Re: originally a newsgroup post, but news server here isn't working In-Reply-To: <199506150630.QAA01865@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@FreeBSD.org Precedence: bulk On Thu, 15 Jun 1995, Bruce Evans wrote: > >At this point I'm a little hesitant to reinstall again from scratch, > >because over this ppp line its about 6 hours a throw, and I've lost my > >dos partition several times so far. Speaking of which, there may be a > >bug in your dos partition handling -- once I rebooted and booted dos, I > >discovered a looped directory pointer -- I have d: mounted to /dos under > >freebsd, and had a /bin directory in it. When I next looked under dos, > >there was a bi directory entry in bi pointing back to bin again. under > > Renaming of directories is quite broken for msdosfs. The following > would create a looped directory: > > cd /dos > mv bin bi # where bin is a dir and bi doesn't exist > > This destroys the "." entry in bin by overwriting it with "bi". Sounds right ;). Nothing norton couldn't fix (or some creative isk editing..). > >At this point, from my point of view, the best possible thing would be > >quick instructions as to how to make the boot manager load onto wd0 so I > >could boot freebsd off of wd1/a. Right now it just goes straight to dos > >booting off of c: (wd0) but if I stick in the boot floppy, boot to the > >boot manager, and tell it wd(1/a) it boots to freebsd fine. So I just > > Er, the program that you tell wd(1,a) too isn't a boot manager. It's just > the FreeBSD boot loader. Once it is loaded, it can boot from any partition > on the first FreeBSD slice on any drive (except DiskManaged hard drives > when the DM software hasn't been loaded by a previous stage in the > bootstrap, e.g., after booting from a FreeBSD floppy). You need a disk > manager on the MBR or on its own partition to load the FreeBSD boot loader > if the FreeBSD slice isn't active. Ok. So here's what I have -- a) no boot manager installed -- for soe reason that didn't happen during sysinstall. b) a bootable freebsd partition, wd(a,1) if anything knew to look there. c) a FreeBSD boot loader on floppy that can be told to point to wd(a,1) So here's my question ;). Is there any post-installation way to get FreeBSD to put in the boot manager, or is that only available from the installation program, which has a nasty tendancy towards overwriting ones root partition entries if run with any decisions made (eg., to install the boot manager, you have to install root.flp, as far as I can see, and that zaps my /etc tree (also on wd(a,1)). I also have a dos partition filling wd0 that I'd like to mount ( > 32 megs dos primary) but freebsd's partition manager says it is unuse, and has a tenency to zap it to actually being unused. Do I need to disklabel the disk? How should I go about mounting it? From owner-freebsd-bugs Thu Jun 15 05:34:43 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA06540 for bugs-outgoing; Thu, 15 Jun 1995 05:34:43 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA06528 ; Thu, 15 Jun 1995 05:34:34 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id WAA14042; Thu, 15 Jun 1995 22:28:31 +1000 Date: Thu, 15 Jun 1995 22:28:31 +1000 From: Bruce Evans Message-Id: <199506151228.WAA14042@godzilla.zeta.org.au> To: bde@zeta.org.au, rwatson@clark.net Subject: Re: originally a newsgroup post, but news server here isn't working Cc: bugs@FreeBSD.org, jkh@FreeBSD.org Sender: bugs-owner@FreeBSD.org Precedence: bulk >So here's my question ;). Is there any post-installation way to get >FreeBSD to put in the boot manager, or is that only available from the >installation program, which has a nasty tendancy towards overwriting ones There should be sources and a standalone installation program (probably DOS-based) for boot manager(s) somewhere in the distribution. On the 2.0R cdrom they are in tools/dos-tools (bteasy and os-bs). >I also have a dos partition filling wd0 that I'd like to mount ( > 32 >megs dos primary) but freebsd's partition manager says it is unuse, and >has a tenency to zap it to actually being unused. Do I need to disklabel >the disk? How should I go about mounting it? mount -t msdos /dev/wd0s1 /where-you-want-it Then put it in /etc/fstab if it works. You shouldn't need to touch wd0 using sysinstall; however if sysinstall is confused by the existing partition table then maybe the kernel will be too. Bruce From owner-freebsd-bugs Thu Jun 15 07:10:37 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA17744 for bugs-outgoing; Thu, 15 Jun 1995 07:10:37 -0700 Received: from lambda.demon.co.uk (lambda.demon.co.uk [158.152.17.124]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id HAA17716 ; Thu, 15 Jun 1995 07:10:28 -0700 Received: (from paul@localhost) by lambda.demon.co.uk (8.6.11/8.6.9) id PAA00290; Thu, 15 Jun 1995 15:08:46 +0100 From: Paul Richards Message-Id: <199506151408.PAA00290@lambda.demon.co.uk> Subject: Re: originally a newsgroup post, but news server here isn't working To: rwatson@clark.net (Robert Watson) Date: Thu, 15 Jun 1995 15:08:10 +0100 (BST) Cc: bde@zeta.org.au, jkh@freebsd.org, bugs@freebsd.org In-Reply-To: from "Robert Watson" at Jun 15, 95 07:46:53 am Reply-to: paul@freebsd.org X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=UK-ASCII Content-Transfer-Encoding: 8bit Content-Length: 1726 Sender: bugs-owner@freebsd.org Precedence: bulk In reply to Robert Watson who said > > > > a) no boot manager installed -- for soe reason that didn't happen during > sysinstall. > > b) a bootable freebsd partition, wd(a,1) if anything knew to look there. > > c) a FreeBSD boot loader on floppy that can be told to point to wd(a,1) > > So here's my question ;). Is there any post-installation way to get > FreeBSD to put in the boot manager, or is that only available from the > installation program, which has a nasty tendancy towards overwriting ones > root partition entries if run with any decisions made (eg., to install > the boot manager, you have to install root.flp, as far as I can see, and > that zaps my /etc tree (also on wd(a,1)). Yes, if you play around a bit. 1) Run sysinstall :-) 2) Go to the mbr (fdisk) partition editor, DON'T change any partition sizes. Just mark your primary FreeBSD partition as bootable. 3) Go to the disklabel editor, don't change anything other than re-assigning the mount points. That should mean that all the partitions are marked read-only. 4) Proceed with the installation, it will ask about installing a boot manager -- choose one. 5) It will then fsck your disks, you should be able to abort the installation at this point (hit ctrl-C) before it does anything else and all that will have happened is that the partition will have been marked bootable and a boot manager will have been installed. This isn't a guarantee but I had similar problems and something along these lines worked for me. -- Paul Richards, Bluebird Computer Systems. FreeBSD core team member. Internet: paul@FreeBSD.org, http://www.freebsd.org/~paul Phone: 0370 462071 (Mobile), +44 1222 457651 (home) From owner-freebsd-bugs Thu Jun 15 12:00:03 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA05971 for bugs-outgoing; Thu, 15 Jun 1995 12:00:03 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA05963 ; Thu, 15 Jun 1995 12:00:02 -0700 Date: Thu, 15 Jun 1995 12:00:02 -0700 Message-Id: <199506151900.MAA05963@freefall.cdrom.com> From: "matthew c. mead" Reply-To: "matthew c. mead" To: freebsd-bugs Subject: bin/519: quotacheck: cannot allocate memory In-Reply-To: Your message of Thu, 15 Jun 1995 14:53:41 -0400 <199506151853.OAA03296@Glock.COM> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 519 >Category: bin >Synopsis: execution of quotacheck from /etc/rc fails >Confidential: yes >Severity: serious >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jun 15 12:00:01 1995 >Originator: matthew c. mead >Organization: Glock 'Em Matthew C. Mead | Network Administration: Virginia Tech Center for | Transportation Research -> mmead@ctr.vt.edu mmead@Glock.COM | Network Administration and Software Development http://www.Glock.COM/~mmead/ | Consulting: BizNet Technologies -> mmead@bnt.com >Release: FreeBSD 2.0-BUILT-19950603 i386 >Environment: Standard environment when booting up. Here is /etc/sysconfig for more information on that environment: ----- /etc/sysconfig ----- #!/bin/sh # # This is sysconfig - a file full of useful variables that you can set # to change the default startup behavior of your system. # # sysconfig,v 1.14 1995/05/17 04:46:57 rgrimes Exp ######################### Start Of Syscons Section ####################### # Choose keyboard map from /usr/share/syscons/keymaps/* or NO if default. keymap=NO # Set keyboard rate to: slow, normal, fast or NO if default. keyrate="fast" # Change function keys default values (or no change if NO) # Syntax: " [ ]..." keychange=NO # Desired cursor type {normal|blink|destructive}, NO if no change cursor=NO # Choose screen map from /usr/share/syscons/scrnmaps/* (or NO for none) scrnmap=NO # Choose font 8x16 from /usr/share/syscons/fonts/* (or NO for default) font8x16=NO # Choose font 8x14 from /usr/share/syscons/fonts/* (or NO for default) font8x14=NO # Choose font 8x8 from /usr/share/syscons/fonts/* (or NO for default) font8x8=NO # Set blank time (in seconds) or "off" to turn it off (or NO for default) blanktime="300" # Set to screen saver desired: blank, green, snake, star (or NO for none) saver="blank" # General russian setup for example: # (koi8-r keyboard with cp866 screen font mapped to koi8-r) # # keymap=ru.koi8-r # keyrate=fast # keychange="61 " # cursor=destructive # scrnmap=koi8-r2cp866 # font8x16=cp866b-8x16 # font8x14=cp866-8x14 # font8x8=cp866-8x8 # blanktime=600 # saver=snake ######################### End Of Syscons Section ####################### ######################### Start Of Netconfig Section ####################### # Set to the name of your host - this is pretty important! hostname="Glock.COM" # Set to the NIS domainname of your host, or NO if none defaultdomainname=NO # # Some broken implementations can't handle the RFC 1323 and RFC 1644 # TCP options. If TCP connections randomly hang, try disabling this, # and bug the vendor of the losing equipment. # tcp_extensions=YES # # Set to the list of network devices on this host. You must have an # ifconfig_${network_interface} line for each interface listed here. # for example: # # network_interfaces="ed0 sl0 lo0" # ifconfig_ed0="inet 10.0.0.1 netmask 0xffffff00" # ifconfig_sl0="inet 10.0.1.0 netmask 0xffffff00" # network_interfaces="ed0 lo0" ifconfig_ed0="inet 198.82.228.165 netmask 255.255.255.0" ifconfig_lo0="inet localhost" # # Set to the list of route add lines for this host. You must have a # route_${static_routes} line for each static route listed here. # static_routes="multicast loopback" route_multicast="224.0.0.0 -netmask 0xf0000000 -interface ${hostname}" route_loopback="${hostname} localhost" # Set to the host you'd like set as your default router, or NO for none. defaultrouter="198.82.228.1" # These are the flags you'd like to start the routing daemon with routedflags="-q" # timed flags, or NO if you don't want to start the time daemon timedflags=NO # xntpd flags, or NO if you don't want to start the xntpd daemon xntpdflags="NO" # this is inoperative unless xntpd is enabled; NO to disable tickadjflags="-Aq" # Set to the site you'd like to syncronize your clock from (gatekeeper.dec.com, # for example) or NO for no such site. ntpdate="ntp-1.vt.edu" # Set to YES if you want to run rwhod rwhod="YES" # Default sendmail flags. -bd is pretty mandatory, -qm sets the queue scan # time in minutes. If set to NO, don't start sendmail at all. sendmail_flags="-bd -q15m" # Set to appropriate flags if you want to use AMD amdflags="NO" # Set to YES if this machine will be an NFS client nfs_client=NO # Set to YES if this machine will be an NFS server nfs_server=NO # Set to appropriate flags if you want to start NIS for a client nis_clientflags="NO" # Set to appropriate flags if you want to start NIS for a server nis_serverflags="NO" # Set to appropriate flags for yppasswdd, if you wish to run it. # Typical flags might be "-m /var/yp/master.passwd -s -f" yppasswddflags="NO" # Set to appropriate flags for named, if you have a full-time # connection to the Internet. # For most hosts, flags should be "-b /etc/namedb/named.boot" namedflags="-b /etc/namedb/named.boot" # Set to YES if you want to run the X-10 power controller daemon xtend=NO # Set to YES if you want kernel crashdumps to be saved for debugging savecore=NO # Set to YES if you want to run Kerberos authentication kerberos_server=NO # Set to YES if you want to run gated gated=NO # Set to YES if you wish to check quotas. NOTE: For now this probably # doesn't work and should be left disabled. check_quotas=NO # Set to YES to turn on accounting. NOTE: For now this probably # doesn't work and should be left disabled. accounting=YES # This stuff needed for proper daemons tuning, comsat f.e. # See profile and csh.login also. # Uncomment next line if you want to setup your 8-bit locale at program # startup automatically # ENABLE_STARTUP_LOCALE=; export ENABLE_STARTUP_LOCALE # Uncomment next line to activate russian locale # LANG=ru_SU.KOI8-R; export LANG # Uncomment next line to activate italian locale # LANG=it_IT.ISO8859-1; export LANG # For full list of locales, check /usr/share/locale/* ######################### End Of Netconfig Section ####################### ######################### Start Of Misc Section ####################### # Set to YES if you want ibcs2 (SCO) emulation loaded at startup ibcs2=NO ----- /etc/sysconfig ----- >Description: options QUOTA has been compiled into the kernel. The /etc/fstab file follows: ----- /etc/fstab ----- /dev/sd0a / ufs rw 1 1 /dev/sd1s1f /tmp ufs rw,userquota=/var/quotas/tmp.user,groupquota=/var/quotas/tmp.group 1 1 /dev/sd0s2e /usr ufs rw,userquota=/var/quotas/usr.user,groupquota=/var/quotas/usr.group 1 1 /dev/sd1s1g /usr/local ufs rw 1 1 /dev/sd1s1e /var ufs rw,userquota=/var/quotas/var.user,groupquota=/var/quotas/var.group 1 1 /dev/sd1s1b none swap sw 0 0 /dev/sd0s2b none swap sw 0 0 proc /proc procfs rw 0 0 /dev/cd0a /cdrom cd9660 ro 0 0 ----- /etc/fstab ----- All of the files specified in /var/quotas exist. >How-To-Repeat: Just reboot with my sysconfig and the quota setup shown above. >Fix: Unknown. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Thu Jun 15 12:00:05 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA05993 for bugs-outgoing; Thu, 15 Jun 1995 12:00:05 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA05982 ; Thu, 15 Jun 1995 12:00:04 -0700 Date: Thu, 15 Jun 1995 12:00:04 -0700 Message-Id: <199506151900.MAA05982@freefall.cdrom.com> From: "matthew c. mead" Reply-To: "matthew c. mead" To: freebsd-bugs Subject: docs/520: documentation on Other ftp site URL for FreeBSD 2.0.5 installation In-Reply-To: Your message of Thu, 15 Jun 1995 14:58:28 -0400 <199506151858.OAA03420@Glock.COM> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 520 >Category: docs >Synopsis: instructions are not clear as to what the url should point to >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Thu Jun 15 12:00:02 1995 >Originator: matthew c. mead >Organization: Glock 'Em! Matthew C. Mead | Network Administration: Virginia Tech Center for | Transportation Research -> mmead@ctr.vt.edu mmead@Glock.COM | Network Administration and Software Development http://www.Glock.COM/~mmead/ | Consulting: BizNet Technologies -> mmead@bnt.com >Release: FreeBSD 2.0-BUILT-19950603 i386 >Environment: Installation environment, with media type set to ftp. >Description: On the screen where you must type in an ftp:// style url that points to a FreeBSD distribution other than one of the ones listed, it isn't clear where this url should point. I.E. Should it point to the equivalent of /pub/FreeBSD/ or should it point to the equivalent of /pub/FreeBSD/2.0.5-RELEASE/ ?? Using the equivalent of /pub/FreeBSD causes a "timeout" error. >How-To-Repeat: Specify the toplevel FreeBSD distribution directory instead of toplevel/2.0.5-RELEASE >Fix: Documentation for the Other ftp site feature should be included on the screen where it is typed in, so that it is clear where the url should point. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Thu Jun 15 15:41:24 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA11684 for bugs-outgoing; Thu, 15 Jun 1995 15:41:24 -0700 Received: from beandorf.epilogue.com (beandorf.epilogue.com [128.224.1.153]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA11674 for ; Thu, 15 Jun 1995 15:41:22 -0700 Received: (from alan@localhost) by beandorf.epilogue.com (8.6.9/8.6.9) id SAA02037; Thu, 15 Jun 1995 18:41:15 -0400 Date: Thu, 15 Jun 1995 18:41:15 -0400 Message-Id: <15Jun1995.180039.Alan@Epilogue.Com> From: Alan Bawden To: fenner@parc.xerox.com CC: freebsd-bugs@freefall.cdrom.com In-reply-to: Bill Fenner's message of Wed, 14 Jun 1995 18:05:27 PDT <95Jun14.180529pdt.49859@crevenia.parc.xerox.com> Subject: kern/512: writing to bpf(loopback) causes kernel panic Sender: bugs-owner@FreeBSD.org Precedence: bulk Date: Wed, 14 Jun 1995 18:05:27 PDT From: Bill Fenner Note that the BPF man page says ...Currently, only writes to Ethernets and SLIP links are supported. (Ignoring the fact that the bpf man page is missing from freebsd-2.0...) Yeah I read that -- but if I believed everything the man pages told me I wouldn't ever get anything done! Looking at the kernel sources made it clear that somebody -thought- that writing to the loopback interface was supposed to work. Try these patches. Next time I'm in a position to re-boot that machine with a new kernel I'll give it a try. Thanks for the prompt response! From owner-freebsd-bugs Thu Jun 15 20:10:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA01029 for bugs-outgoing; Thu, 15 Jun 1995 20:10:02 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA01018 ; Thu, 15 Jun 1995 20:10:01 -0700 Date: Thu, 15 Jun 1995 20:10:01 -0700 Message-Id: <199506160310.UAA01018@freefall.cdrom.com> From: Tom Samplonius Reply-To: Tom Samplonius To: freebsd-bugs Subject: docs/521: catgets() man page error In-Reply-To: Your message of Thu, 15 Jun 1995 11:46:38 -0700 <199506151846.LAA03248@misery.sdf.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 521 >Category: docs >Synopsis: catgets() man page error >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Thu Jun 15 20:10:00 1995 >Originator: Tom Samplonius >Organization: SDF Systems >Release: 2.0.5R >Environment: 2.0.5R >Description: Man page for catgets(3) says: STANDARDS The catgets() function conforms to . but fails to mention exactly what it conforms to. >How-To-Repeat: man catgets >Fix: What standard does it conform to? If you know, please add it, because I'd like to know! >Audit-Trail: >Unformatted: From owner-freebsd-bugs Thu Jun 15 20:36:37 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA09130 for bugs-outgoing; Thu, 15 Jun 1995 20:36:37 -0700 Received: (from wpaul@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA09111 ; Thu, 15 Jun 1995 20:36:35 -0700 Date: Thu, 15 Jun 1995 20:36:35 -0700 From: Bill Paul Message-Id: <199506160336.UAA09111@freefall.cdrom.com> To: knarf@nasim.cube.net, wpaul, freebsd-bugs Subject: Changed information for PR bin/518 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: passwd asks YP-Server for unknown user State-Changed-From-To: open-closed State-Changed-By: wpaul State-Changed-When: Thu Jun 15 20:33:48 PDT 1995 State-Changed-Why: Fixed in revision 1.4 of /usr/src/usr.bin/passwd.c. We now check to see if NIS is actually enabled (by looking for +::::::::: or similar in the password database) and don't transform into yppasswd if it isn't. From owner-freebsd-bugs Thu Jun 15 20:40:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA09964 for bugs-outgoing; Thu, 15 Jun 1995 20:40:02 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA09949 ; Thu, 15 Jun 1995 20:40:01 -0700 Date: Thu, 15 Jun 1995 20:40:01 -0700 Message-Id: <199506160340.UAA09949@freefall.cdrom.com> From: Dmitry Khrustalev Reply-To: Dmitry Khrustalev To: freebsd-bugs Subject: kern/522: In-Reply-To: Your message of Fri, 16 Jun 1995 03:38:34 GMT <199506160338.DAA19369@satty.npi.msu.su> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 522 >Category: kern >Synopsis: >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jun 15 20:40:00 1995 >Originator: Dmitry Khrustalev >Organization: Moscow State University >Release: FreeBSD 2.1.0-Development i386 >Environment: >Description: If interface goes down while bpf is listening on it in promiscuous mode, closing bpf will panic system in bpf.c line 278. panic: bpf: ifpromisc failed >How-To-Repeat: Start tcpdump on ppp interface while pppd is running. Terminate pppd. Terminating tcpdump will result in panic. >Fix: This fix changes current bpf behavior, however current behavior has problems: for example if transmitting a packet results in interface going up, how do we capture this packet? *** bpf.c.orig Fri Jun 16 06:12:07 1995 --- bpf.c Fri Jun 16 06:12:35 1995 *************** *** 1261,1272 **** int pswitch; { struct ifreq ifr; - /* - * If the device is not configured up, we cannot put it in - * promiscuous mode. - */ - if ((ifp->if_flags & IFF_UP) == 0) - return (ENETDOWN); if (pswitch) { if (ifp->if_pcount++ != 0) --- 1261,1266 ---- >Audit-Trail: >Unformatted: From owner-freebsd-bugs Thu Jun 15 22:23:42 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA25417 for bugs-outgoing; Thu, 15 Jun 1995 22:23:42 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA25403 for ; Thu, 15 Jun 1995 22:23:37 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id PAA08032; Fri, 16 Jun 1995 15:22:00 +1000 Date: Fri, 16 Jun 1995 15:22:00 +1000 From: Bruce Evans Message-Id: <199506160522.PAA08032@godzilla.zeta.org.au> To: freebsd-bugs@freefall.cdrom.com, tom@sdf.com Subject: Re: docs/521: catgets() man page error Sender: bugs-owner@FreeBSD.org Precedence: bulk > Man page for catgets(3) says: >STANDARDS > The catgets() function conforms to . >but fails to mention exactly what it conforms to. >>How-To-Repeat: > man catgets >>Fix: > > What standard does it conform to? If you know, please add it, because I'd like to know! -xpg3 according to catgets.3. We're missing several man page and doc macros. Bruce From owner-freebsd-bugs Fri Jun 16 04:28:05 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA07989 for bugs-outgoing; Fri, 16 Jun 1995 04:28:05 -0700 Received: from mail.id.net (kilroy.id.net [152.160.9.10]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA07972 ; Fri, 16 Jun 1995 04:28:01 -0700 Received: from hades.id.net (hades.id.net [152.160.9.12]) by mail.id.net (8.6.8/8.6.6) with ESMTP id HAA09308; Fri, 16 Jun 1995 07:28:04 -0400 From: Robert Shady Received: (rls@localhost) by hades.id.net (8.6.11/8.6.6) id HAA00565; Fri, 16 Jun 1995 07:28:05 -0400 Message-Id: <199506161128.HAA00565@hades.id.net> Subject: Problems with 2.0.5-RELEASE To: hackers@freebsd.org, bugs@freebsd.org Date: Fri, 16 Jun 1995 07:28:05 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 5753 Sender: bugs-owner@freebsd.org Precedence: bulk We have a network of 7 FreeBSD machines here. KILROY is currently our main file server. All of the machines, except for one (Hades), are running FreeBSD 1.1.5.1 w/patches. We would like to upgrade all of our machines to FreeBSD 2.0.5, but we have to make sure it's stable first, and it doesn't seem to be quite there yet. Not quite sure how to track this one down, but I've got three major problems with the 2.0.5-RELEASE so far. 1) I keep getting "nfs send error 65 for server kilroy:/home" errors. At first this doesn't seem to be a problem, but after a few of these errors the entire FreeBSD box "locks up". I'm not sure if these two are related, but thought I would mention it. By "lock up", I mean the console & telnet ports lock, but it looks as though the system is still running (Ie: screen saver is still going). 2) I have a MUD (LP-Mud Game Driver) that is ran on the 2.0.5 machine. It dies rather often under 2.0.5-RELEASE with SIGFAULT or IOT Trap errors. This same game, on the same machine, running 1.1.5.1 w/patches would run for 15-20 days before upgrading to 2.0.5, now it runs anywhere from a couple minutes to 4 hours. 3) The 2.0.5 machine keeps rebooting about once every 24 hours or so. I haven't checked the logs before to find out why, but this time I did and found: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x2a fault code = supervisor read, page not present instruction pointer = 0x8:0xf0108c8d code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 599 (ndriver2.0) interrupt mask = net tty bio panic: page fault syncing disks... 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 giving up Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... Machine configuration is: ========================= Pentium 100Mhz PCI Motherboard Onboard NCR SCSI Controller 32MB of RAM IDE Controller Card 540MB IDE Hard Drive SMC Elite Ultra Ethernet Card Plain-Jane VGA Card (Yes, I am not currently using ANY PCI ports ;) Here is my DMESG, followed by my CONFIG file ============================================ FreeBSD 2.0.5-RELEASE #0: Wed Jun 14 15:30:41 EDT 1995 root@hades.id.net:/usr/src/sys/compile/HADES CPU: 100-MHz Pentium 815\\100 (Pentium-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping=5 Features=0x1bf real memory = 33161216 (8096 pages) avail memory = 30875648 (7538 pages) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <4 virtual consoles, flags=0x0> ed0 at 0x300-0x31f irq 5 maddr 0xd0000 msize 8192 on isa ed0: address 00:00:c0:a3:6a:b0, type SMC8416C/SMC8416BT (16 bit) pca0 on motherboard pca0: PC speaker audio driver fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 765 fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 514MB (1054368 sectors), 1046 cyls, 16 heads, 63 S/T, 512 B/S npx0 on motherboard npx0: INT 16 interface Probing for devices on the pci0 bus: configuration mode 1 allows 32 devices. pci0:0: vendor=0x1039, device=0x406, class=bridge [not supported] pci0:1: vendor=0x1039, device=0x8, class=bridge [not supported] WARNING: / was not properly dismounted. nfs send error 65 for server kilroy:/home nfs send error 65 for server kilroy:/home nfs send error 65 for server kilroy:/home nfs send error 65 for server kilroy:/home nfs send error 65 for server kilroy:/home nfs send error 65 for server kilroy:/home Fatal trap 12: page fault while in kernel mode fault virtual address = 0x2a fault code = supervisor read, page not present instruction pointer = 0x8:0xf0108c8d code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 599 (ndriver2.0) interrupt mask = net tty bio panic: page fault syncing disks... 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 giving up Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... Here is the configuration file ============================== # # HADES -- # Presently the second dialup machine at Innovative Data Services (id.net) # machine "i386" cpu "I386_CPU" cpu "I486_CPU" cpu "I586_CPU" ident HADES maxusers 256 options "COMPAT_43" # Compatible with BSD 4.3 options "OPEN_MAX=256" # Maximum # of open files per process options "MAXCONS=4" # Maximum Virtual Consoles options "CHILD_MAX=256" options "NMBCLUSTERS=1024" options "MAXDSIZ=256UL*1024*1024" options INET # Internet communications protocols options FFS # Berkeley Fast File System options NFS # Network File System options PROCFS # Process File System options MSDOSFS # MSDOS File System options MROUTING # Multicast Routing options BOUNCE_BUFFERS # Bounce Buffer Support options DUMMY_NOPS # Remove extra delays options SYSVSHM options SYSVSEM options SYSVMSG options COMPAT_LINUX config kernel root on wd0 controller isa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 device pca0 at isa? port IO_TIMER1 tty device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device ed0 at isa? port 0x300 net irq 5 iomem 0xd0000 vector edintr pseudo-device vn pseudo-device log pseudo-device pty 64 pseudo-device snp 4 pseudo-device gzip pseudo-device loop pseudo-device ether pseudo-device speaker From owner-freebsd-bugs Fri Jun 16 04:47:01 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA08585 for bugs-outgoing; Fri, 16 Jun 1995 04:47:01 -0700 Received: from clark.net (rwatson@clark.net [168.143.0.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA08579 ; Fri, 16 Jun 1995 04:46:58 -0700 Received: (rwatson@localhost) by clark.net (8.6.12/8.6.5) id HAA11615; Fri, 16 Jun 1995 07:46:55 -0400 Date: Fri, 16 Jun 1995 07:46:54 -0400 (EDT) From: Robert Watson To: paul@freebsd.org cc: bde@zeta.org.au, jkh@freebsd.org, bugs@freebsd.org Subject: Re: originally a newsgroup post, but news server here isn't working In-Reply-To: <199506151408.PAA00290@lambda.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@freebsd.org Precedence: bulk I tried this and apparently it didn't work -- I aborted during the fsck after it had said it was writing the boot manager, bt when I rebooted it booted straight to dos again. I ftp'd osbs (135) and booteasy -- found that os-bs (as found in dos-tools) won't support boot off of a second HD. Boot easy worked fine though. So it's now bootable, but that was after many attempts and several lost partitions (and not handled completely by sysinstall in order to get it to work.) I guess the amin problem as I see it (from the perspective of the person watching the installation) is that killing off processes beacue of a lack of swap before there is swap can have bad side effects -- like incomplete tasks. So I guess that may be the cause of all this. I'm doing an installation on an 8 meg machine on Monday, I'll watch for any related problems and let yo know. Thanks again.. Robert Watson rwatson@sidwell.edu http://www.sidwell.edu/~rwatson/ The goal of science is to build better mousetraps. The goal of nature is to build better mice. On Thu, 15 Jun 1995, Paul Richards wrote: > > a) no boot manager installed -- for soe reason that didn't happen during > > sysinstall. > > > > b) a bootable freebsd partition, wd(a,1) if anything knew to look there. > > > > c) a FreeBSD boot loader on floppy that can be told to point to wd(a,1) > > > > So here's my question ;). Is there any post-installation way to get > > FreeBSD to put in the boot manager, or is that only available from the > > installation program, which has a nasty tendancy towards overwriting ones > > root partition entries if run with any decisions made (eg., to install > > the boot manager, you have to install root.flp, as far as I can see, and > > that zaps my /etc tree (also on wd(a,1)). > > Yes, if you play around a bit. > > 1) Run sysinstall :-) > > 2) Go to the mbr (fdisk) partition editor, DON'T change any partition > sizes. Just mark your primary FreeBSD partition as bootable. > > 3) Go to the disklabel editor, don't change anything other than > re-assigning the mount points. That should mean that all the > partitions are marked read-only. > > 4) Proceed with the installation, it will ask about installing a boot > manager -- choose one. > > 5) It will then fsck your disks, you should be able to abort the > installation at this point (hit ctrl-C) before it does anything > else and all that will have happened is that the partition will > have been marked bootable and a boot manager will have been > installed. > > This isn't a guarantee but I had similar problems and something along these > lines worked for me. > From owner-freebsd-bugs Fri Jun 16 05:11:42 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA09607 for bugs-outgoing; Fri, 16 Jun 1995 05:11:42 -0700 Received: from ki1.chemie.fu-berlin.de (ki1.Chemie.FU-Berlin.DE [160.45.24.21]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id FAA09581 for ; Fri, 16 Jun 1995 05:11:16 -0700 Received: by ki1.chemie.fu-berlin.de (Smail3.1.28.1) from sirius.physik.fu-berlin.de (130.133.3.140) with smtp id ; Fri, 16 Jun 95 14:10 MEST Received: by sirius.physik.fu-berlin.de; id AA13815; Fri, 16 Jun 1995 14:09:54 +0200 From: Thomas Graichen Message-Id: <9506161209.AA13815@sirius.physik.fu-berlin.de> Subject: problems with termcap-entries To: freebsd-bugs@freebsd.org Date: Fri, 16 Jun 1995 14:09:54 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1226 Sender: bugs-owner@freebsd.org Precedence: bulk hello we had her some problems with xterm - some people were able to run xterms - other ones not - they got the message: unable to find usable termcap entry (this comes from main.c of xterm) we had to look a long time before we've found the problem - the homedir of the person has to be -*******x (*may be everything) this is only needed for FreeBSD (not for Dec OSF/1 or Linux) - after changing this the problem went away - should this be so (i don't think so) - and why this is so ? - do you have any ideas ? here some more description of our setup: FreeBSD-950412-SNAP - homedir's mounted via nfs (via amd) - passwd etc. via nis/yp - if you leke to know more please mail to me hope this helps - t _______________________________________________________||_____________________ __|| Perfection is reached, not when there is no __|| thomas graichen longer anything to add, but when there __|| freie universitaet berlin is no longer anything to take away __|| fachbereich physik __|| - Antoine de Saint-Exupery - __|| ___________________________||____email: graichen@omega.physik.fu-berlin.de____ From owner-freebsd-bugs Fri Jun 16 07:00:03 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA15377 for bugs-outgoing; Fri, 16 Jun 1995 07:00:03 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA15364 ; Fri, 16 Jun 1995 07:00:02 -0700 Date: Fri, 16 Jun 1995 07:00:02 -0700 Message-Id: <199506161400.HAA15364@freefall.cdrom.com> From: cstruble@vt.edu Reply-To: cstruble@vt.edu To: freebsd-bugs Subject: bin/523: disklabel -B too anal In-Reply-To: Your message of Fri, 16 Jun 1995 09:54:57 -0400 <199506161354.JAA07513@singularity.bevc.blacksburg.va.us> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 523 >Category: bin >Synopsis: disklabel -B anal about writing boot blocks >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jun 16 07:00:01 1995 >Originator: Craig Struble >Organization: Craig Struble - Grad Student, Consultant, | Student ACM Co-President, Virginia Tech | The space reserved for more Email - cstruble@vt.edu | obfuscation. URL - http://acm.vt.edu/~cstruble/ | >Release: FreeBSD 2.0-BUILT-19950603 i386 >Environment: FreeBSD 2.0.5 installed on SCSI drive. The system has 2 SCSI drives and 1 IDE drive. >Description: disklabel -B won't install boot blocks if it finds trouble in the disk label. Not a bad thing, except that the label installed on the drive has a superblock size of 0. The disk label was installed with sysinstall. >How-To-Repeat: Install FreeBSD onto a SCSI drive on a system with an IDE drive. Try updating your bootblocks with disklabel -B >Fix: One way of getting around the problem is to comment out the check of the disk label when only writing boot blocks. However, this probably isn't the safest thing to do. It looks like either sysinstall needs to correct the disk label it writes, or disklabel -B shouldn't be so anal about how it checks the disk label. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Fri Jun 16 07:50:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA18634 for bugs-outgoing; Fri, 16 Jun 1995 07:50:02 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA18627 ; Fri, 16 Jun 1995 07:50:01 -0700 Date: Fri, 16 Jun 1995 07:50:01 -0700 Message-Id: <199506161450.HAA18627@freefall.cdrom.com> From: slr@mitre.org Reply-To: slr@mitre.org To: freebsd-bugs Subject: bin/524: a fix for mrouted In-Reply-To: Your message of Fri, 16 Jun 1995 10:49:40 -0400 <199506161449.KAA14783@lusty.acet.org> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 524 >Category: bin >Synopsis: mrouted won't accept prunes from another fbsd mrouter >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jun 16 07:50:00 1995 >Originator: Soochon Radee >Organization: MITRE >Release: FreeBSD 2.0-BUILT-19950616 >Environment: Any system with the the recent multicast 3.5 port. >Description: Mrouted reads the prune timer from prune packets wrongly and will flood the tunnel or link with multicast packets even after prunes are issued. >How-To-Repeat: Set up mrouted on any FreeBSD box so that it is upstream of another mrouter that supports pruning. Fire up mrouted on both. >Fix: *** usr.sbin/mrouted/prune.c.old Tue Jun 13 16:52:49 1995 --- usr.sbin/mrouted/prune.c Fri Jun 16 10:03:12 1995 *************** *** 1212,1217 **** --- 1212,1218 ---- ((char *)&prun_grp)[i] = *p++; for (i = 0; i< 4; i++) ((char *)&prun_tmr)[i] = *p++; + prun_tmr = ntohl(prun_tmr); log(LOG_DEBUG, 0, "%s on vif %d prunes (%s %s)/%d", inet_fmt(src, s1), vifi, >Audit-Trail: >Unformatted: From owner-freebsd-bugs Fri Jun 16 09:39:59 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA25151 for bugs-outgoing; Fri, 16 Jun 1995 09:39:59 -0700 Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id JAA25145 for ; Fri, 16 Jun 1995 09:39:58 -0700 Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <14713(4)>; Fri, 16 Jun 1995 09:39:09 PDT Received: from localhost by crevenia.parc.xerox.com with SMTP id <49859>; Fri, 16 Jun 1995 09:38:58 -0700 X-Mailer: exmh version 1.6 4/21/95 To: slr@mitre.org cc: freebsd-bugs@freefall.cdrom.com Subject: Re: bin/524: a fix for mrouted In-reply-to: Your message of "Fri, 16 Jun 95 07:50:01 PDT." <199506161450.HAA18627@freefall.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 16 Jun 1995 09:38:46 PDT From: Bill Fenner Message-Id: <95Jun16.093858pdt.49859@crevenia.parc.xerox.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk In message <199506161450.HAA18627@freefall.cdrom.com> you write: >*** usr.sbin/mrouted/prune.c.old Tue Jun 13 16:52:49 1995 >--- usr.sbin/mrouted/prune.c Fri Jun 16 10:03:12 1995 >*************** >*** 1212,1217 **** >--- 1212,1218 ---- > ((char *)&prun_grp)[i] = *p++; > for (i = 0; i< 4; i++) > ((char *)&prun_tmr)[i] = *p++; >+ prun_tmr = ntohl(prun_tmr); > > log(LOG_DEBUG, 0, "%s on vif %d prunes (%s %s)/%d", > inet_fmt(src, s1), vifi, Thanks, I caught this already. However, since this isn't the version of mrouted that's in the tree, bug reports should probably just go to me for now. (Someone might as well close this PR; the mrouted in the tree doesn't have this bug.) Bill From owner-freebsd-bugs Fri Jun 16 09:58:12 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA26219 for bugs-outgoing; Fri, 16 Jun 1995 09:58:12 -0700 Received: (from wollman@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA26205 ; Fri, 16 Jun 1995 09:58:11 -0700 Date: Fri, 16 Jun 1995 09:58:11 -0700 From: "Garrett A. Wollman" Message-Id: <199506161658.JAA26205@freefall.cdrom.com> To: slr@mitre.org, wollman, freebsd-bugs Subject: Changed information for PR bin/524 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: mrouted won't accept prunes from another fbsd mrouter State-Changed-From-To: open-closed State-Changed-By: wollman State-Changed-When: Fri Jun 16 09:57:28 PDT 1995 State-Changed-Why: Suggested fix applied. From owner-freebsd-bugs Fri Jun 16 10:00:38 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA26468 for bugs-outgoing; Fri, 16 Jun 1995 10:00:38 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id KAA26462 for ; Fri, 16 Jun 1995 10:00:37 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.3.6) id AA05419; Fri, 16 Jun 1995 13:00:11 -0400 Date: Fri, 16 Jun 1995 13:00:11 -0400 From: Garrett Wollman Message-Id: <9506161700.AA05419@halloran-eldar.lcs.mit.edu> To: Bill Fenner Cc: freebsd-bugs@freefall.cdrom.com Subject: Re: bin/524: a fix for mrouted In-Reply-To: <95Jun16.093858pdt.49859@crevenia.parc.xerox.com> References: <199506161450.HAA18627@freefall.cdrom.com> <95Jun16.093858pdt.49859@crevenia.parc.xerox.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk < said: >> ((char *)&prun_tmr)[i] = *p++; >> + prun_tmr = ntohl(prun_tmr); >> >> log(LOG_DEBUG, 0, "%s on vif %d prunes (%s %s)/%d", >> inet_fmt(src, s1), vifi, > Thanks, I caught this already. However, since this isn't the version of > mrouted that's in the tree, bug reports should probably just go to me for now. Um, Bill, yes it is. Go look. -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-bugs Fri Jun 16 12:26:00 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA13726 for bugs-outgoing; Fri, 16 Jun 1995 12:26:00 -0700 Received: from mailhost.primenet.com (root@mailhost.primenet.com [198.68.32.50]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA13720 for ; Fri, 16 Jun 1995 12:25:58 -0700 Received: from ip214.sna.primenet.com (ip214.sna.primenet.com [204.212.53.214]) by mailhost.primenet.com (8.6.11/wjp-h2.0) with SMTP id MAA26927 for ; Fri, 16 Jun 1995 12:25:54 -0700 Date: Fri, 16 Jun 1995 12:25:54 -0700 Message-Id: <199506161925.MAA26927@mailhost.primenet.com> X-Sender: sjs1@mailhost.primenet.com X-Mailer: Windows Eudora Version 1.4.4 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: freebsd-bugs@FreeBSD.ORG From: sjs1@primenet.com (Scott Story) Subject: NCR53c400 Magoptic Problem Sender: bugs-owner@FreeBSD.ORG Precedence: bulk >Scott Story writes: >> >> Any help or a refferal would be apprieciated. >> I am trying to install freeBSD 2.0 on to a SCSI 1 Sony MagOptic drive. >> (486,33 8 mg. one SCSI device) >> These are the messages I am getting. >> Durring kernel boot: >> nca1: NCR-53C400 >> nca1: wating for SCSI devices to settle >> nca1: "Sony SMO-C501-00 2.22" is a type 0 removeable SCSI 1 >> sd0 (nca1) Direct Access >> sd0 (nca1) Illegal Request ASC:24,0 invalid field in CDB >> sdo could not mode sense (4), Using Fictitious Geometry, 281 (576999, 512 >> byte sectors) > >Does this happen even if you have the formatted media installed? YES with 512 Media There is 512 or 1024 byte sector media for the SMO501. > >> During sysinstall >> >> Select install >> >> nca1/0/0/sd0/timed out >> Fatal Trap 12: page fault in kernel mode >> Fault Address=0x8 >> Fault Code=supervisor read, page np >> install pointer=0x8:0xf0172c1b >> code sequence= base 0x0, limit 0xfffff, type ox1b=DPL 0,pres 1, def 32, gran 1 >> Processor eflags=interupt enabled, resume,10 PL=0 >> Current Process= 1 (sysinstall) >> int. mask= bio >> panic=page fault > >Oops. Do you have a stack back trace? NO stack back trace. How? I want to die quietly in my sleep like my grandfather, not SCREAMING! like his passengers <:) http://www.primenet.com/~sjs1/index sjs1@primenet.com From owner-freebsd-bugs Fri Jun 16 13:07:14 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA15645 for bugs-outgoing; Fri, 16 Jun 1995 13:07:14 -0700 Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id NAA15638 for ; Fri, 16 Jun 1995 13:07:12 -0700 Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <14535(5)>; Fri, 16 Jun 1995 13:06:25 PDT Received: from localhost by crevenia.parc.xerox.com with SMTP id <49859>; Fri, 16 Jun 1995 13:06:14 -0700 X-Mailer: exmh version 1.6 4/21/95 To: Garrett Wollman cc: freebsd-bugs@freefall.cdrom.com Subject: Re: bin/524: a fix for mrouted In-reply-to: Your message of "Fri, 16 Jun 95 10:00:11 PDT." <9506161700.AA05419@halloran-eldar.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 16 Jun 1995 13:06:07 PDT From: Bill Fenner Message-Id: <95Jun16.130614pdt.49859@crevenia.parc.xerox.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk In message <9506161700.AA05419@halloran-eldar.lcs.mit.edu> you write: >Um, Bill, yes it is. Go look. Sorry, I haven't been keeping up with the commit messages. Pass me the pointy hat, please. Bill From owner-freebsd-bugs Fri Jun 16 13:29:22 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA16955 for bugs-outgoing; Fri, 16 Jun 1995 13:29:22 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id NAA16936 for ; Fri, 16 Jun 1995 13:29:10 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA08822; Fri, 16 Jun 1995 22:29:05 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA28310; Fri, 16 Jun 1995 22:29:05 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id WAA04354; Fri, 16 Jun 1995 22:09:31 +0200 From: J Wunsch Message-Id: <199506162009.WAA04354@uriah.heep.sax.de> Subject: Re: bin/523: disklabel -B too anal To: cstruble@vt.edu Date: Fri, 16 Jun 1995 22:09:31 +0200 (MET DST) Cc: freebsd-bugs@freefall.cdrom.com In-Reply-To: <199506161400.HAA15364@freefall.cdrom.com> from "cstruble@vt.edu" at Jun 16, 95 07:00:02 am Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 626 Sender: bugs-owner@FreeBSD.org Precedence: bulk As cstruble@vt.edu wrote: > > > disklabel -B won't install boot blocks if it finds trouble in the > disk label. This is a duplicate for PR # i386/251. My first idea has also been to blame disklabel, but thinking over it, the disklabel is located midst in the boot blocks, so it's really a Good Thing (tm) that disklabel(8) insists on correct data. sysinstall needs to be fixed instead. I'm going to close this PR, since it's not particularly useful to have a duplicate one. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Fri Jun 16 22:04:54 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA07612 for bugs-outgoing; Fri, 16 Jun 1995 22:04:54 -0700 Received: (from wpaul@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA07595 ; Fri, 16 Jun 1995 22:04:53 -0700 Date: Fri, 16 Jun 1995 22:04:53 -0700 From: Bill Paul Message-Id: <199506170504.WAA07595@freefall.cdrom.com> To: wpaul@skynet.ctr.columbia.edu, wpaul, freebsd-bugs Subject: Changed information for PR kern/507 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: Trying to load if_sl_mod or if_ppp_mod *twice* crashes system State-Changed-From-To: open-closed State-Changed-By: wpaul State-Changed-When: Fri Jun 16 22:03:04 PDT 1995 State-Changed-Why: Fixed in revision 1.6 of /usr/src/sys/sys/lkm.h. The DISPATCH() macro now does an lkmexists() check to catch duplicate instances of modules _before_ the module is initialized. From owner-freebsd-bugs Fri Jun 16 22:51:38 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA08460 for bugs-outgoing; Fri, 16 Jun 1995 22:51:38 -0700 Received: (from davidg@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA08446 ; Fri, 16 Jun 1995 22:51:37 -0700 Date: Fri, 16 Jun 1995 22:51:37 -0700 From: David Greenman Message-Id: <199506170551.WAA08446@freefall.cdrom.com> To: henrich@crh.cl.msu.edu, davidg, freebsd-bugs Subject: Changed information for PR bin/505 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: LINEMODE causes problems with some telnetd clients + fix. State-Changed-From-To: open-closed State-Changed-By: davidg State-Changed-When: Fri Jun 16 22:50:54 PDT 1995 State-Changed-Why: Suggested patch was applied. From owner-freebsd-bugs Fri Jun 16 22:57:26 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA08777 for bugs-outgoing; Fri, 16 Jun 1995 22:57:26 -0700 Received: (from davidg@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA08761 ; Fri, 16 Jun 1995 22:57:25 -0700 Date: Fri, 16 Jun 1995 22:57:25 -0700 From: David Greenman Message-Id: <199506170557.WAA08761@freefall.cdrom.com> To: henrich@fubar.cl.msu.edu, davidg, freebsd-bugs Subject: Changed information for PR bin/396 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: telnetd problems. State-Changed-From-To: open-closed State-Changed-By: davidg State-Changed-When: Fri Jun 16 22:55:50 PDT 1995 State-Changed-Why: This PR was duplicated in PR#505 where a bug fix was provided and applied. From owner-freebsd-bugs Fri Jun 16 22:59:50 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA08971 for bugs-outgoing; Fri, 16 Jun 1995 22:59:50 -0700 Received: (from davidg@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA08954 ; Fri, 16 Jun 1995 22:59:50 -0700 Date: Fri, 16 Jun 1995 22:59:50 -0700 From: David Greenman Message-Id: <199506170559.WAA08954@freefall.cdrom.com> To: gibbs@estienne.cs.berkeley.edu, davidg, freebsd-bugs Subject: Changed information for PR misc/292 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: rfc1323 and rfc1644 support can confuse terminal servers w/SLIP State-Changed-From-To: open-closed State-Changed-By: davidg State-Changed-When: Fri Jun 16 22:58:46 PDT 1995 State-Changed-Why: As mentioned in the PR, this isn't a bug in FreeBSD and the decision on this is that TCP options negotiation should remain enabled. From owner-freebsd-bugs Fri Jun 16 23:47:35 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA10207 for bugs-outgoing; Fri, 16 Jun 1995 23:47:35 -0700 Received: from vegemite.Stanford.EDU (2842@vegemite.Stanford.EDU [36.159.0.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA10201 for ; Fri, 16 Jun 1995 23:47:33 -0700 Received: (hlew@localhost) by vegemite.Stanford.EDU (8.6.10/8.6.4) id XAA17121; Fri, 16 Jun 1995 23:47:30 -0700 Date: Fri, 16 Jun 1995 23:47:29 -0700 (PDT) From: Howard Lew To: Terry Lambert cc: bugs@FreeBSD.org Subject: Re: 2.05R panics on boot In-Reply-To: <9506142050.AA19501@cs.weber.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@FreeBSD.org Precedence: bulk > > > > Now only if the system would boot up with the boot manager. What ever > > > > happened to the boot manager that was used on the SNAPs? That one > > > > seemed to work be able to boot up even on this 850 WDC drive with Ontrack > > > > DM installed. Booteasy wasn't able to do it. They were different > > > > right? or has something changed? > > > > > Now BSD's new slice code knows about the DM MBR. But the installation > of the MBR code does not. And the installation doesn't use BIOS, so > like a raw floppy boot, it overwrites the DM MBR. > > The fix is to make the "OS-BS" or other boot track installation in BSD > know about the DM MBR by recognizing it (it has ID crap so you can do > this). OR YOU CAN INSTALL THE BOOT MANAGER AFTER BOOTING DOS OF THE > HARD DRIVE. Okay... I've given up on Booteasy, and I have tried installing a boot manager (OSBS2.0b8) a number of ways. If I install the boot manager after booting up DOS from hard drive C, the boot manager comes up after the Ontrack DM, but when I choose the FreeBSD partition (wd1), OS-BS just hangs the system. But if I choose the MSDOS partition, it doesn't crash. If I install OS-BS after booting from a DOS floppy, OS-BS shows the OS menu before it gets to the Ontrack DM. If I choose FreeBSD, it comes up fine (perfecto!) But if I choose MSDOS, the system says: Missing Operating System. :-( I have also toggled around the writing of the active partion flag on bootup with no luck either. As for setting the ID in OS-BS... Do I change the value (I think it was 50 something) to a DOS value? And should I do this after booting from a DOS floppy? Thanks for your continuing assistance. From owner-freebsd-bugs Fri Jun 16 23:59:45 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA10391 for bugs-outgoing; Fri, 16 Jun 1995 23:59:45 -0700 Received: from vegemite.Stanford.EDU (2842@vegemite.Stanford.EDU [36.159.0.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA10385 for ; Fri, 16 Jun 1995 23:59:44 -0700 Received: (hlew@localhost) by vegemite.Stanford.EDU (8.6.10/8.6.4) id XAA17129; Fri, 16 Jun 1995 23:53:28 -0700 Date: Fri, 16 Jun 1995 23:53:28 -0700 (PDT) From: Howard Lew To: Bruce Evans cc: bugs@FreeBSD.org Subject: Re: 2.05R panics on boot In-Reply-To: <199506150309.NAA27850@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@FreeBSD.org Precedence: bulk On Thu, 15 Jun 1995, Bruce Evans wrote: > Only one case can't possibly work: loading the bootstrap off a floppy > and then attempting to boot from a hard disk (e.g., by typing > sd(1,a)/kernel). The boot code doesn't know about DM, so it won't > work if DM needs to be loaded. > Right now the only way I can boot up FreeBSD system on the Ontrack DM system is by using boot.flp and entering wd(1,a)/kernel. This is very annoying. I have not tried and I doubt if I can access the msdos stuff from FreeBSD for now. Is there a way to easily make a boot disk that loads the Ontrack DM and then boots up FreeBSD from wd1 or from DOS? From owner-freebsd-bugs Sat Jun 17 02:28:38 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA15624 for bugs-outgoing; Sat, 17 Jun 1995 02:28:38 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id CAA15617 for ; Sat, 17 Jun 1995 02:28:33 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id RAA18958; Sat, 17 Jun 1995 17:57:56 +1000 Date: Sat, 17 Jun 1995 17:57:56 +1000 From: Bruce Evans Message-Id: <199506170757.RAA18958@godzilla.zeta.org.au> To: bde@zeta.org.au, hlew@genome.Stanford.EDU Subject: Re: 2.05R panics on boot Cc: bugs@FreeBSD.org Sender: bugs-owner@FreeBSD.org Precedence: bulk >> Only one case can't possibly work: loading the bootstrap off a floppy >> and then attempting to boot from a hard disk (e.g., by typing >> sd(1,a)/kernel). The boot code doesn't know about DM, so it won't >> work if DM needs to be loaded. >> >Right now the only way I can boot up FreeBSD system on the Ontrack DM >system is by using boot.flp and entering wd(1,a)/kernel. This is very >annoying. I have not tried and I doubt if I can access the msdos stuff >from FreeBSD for now. This seems to be the case that I said can't work. Apparently wd1 doesn't have Ontrack on it, but Ontrack on the boot disk adjusts for all disks. Bruce From owner-freebsd-bugs Sat Jun 17 02:34:06 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA15789 for bugs-outgoing; Sat, 17 Jun 1995 02:34:06 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id CAA15782 for ; Sat, 17 Jun 1995 02:34:01 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id RAA18958; Sat, 17 Jun 1995 17:57:56 +1000 Date: Sat, 17 Jun 1995 17:57:56 +1000 From: Bruce Evans Message-Id: <199506170757.RAA18958@godzilla.zeta.org.au> To: bde@zeta.org.au, hlew@genome.Stanford.EDU Subject: Re: 2.05R panics on boot Cc: bugs@FreeBSD.org Sender: bugs-owner@FreeBSD.org Precedence: bulk >> Only one case can't possibly work: loading the bootstrap off a floppy >> and then attempting to boot from a hard disk (e.g., by typing >> sd(1,a)/kernel). The boot code doesn't know about DM, so it won't >> work if DM needs to be loaded. >> >Right now the only way I can boot up FreeBSD system on the Ontrack DM >system is by using boot.flp and entering wd(1,a)/kernel. This is very >annoying. I have not tried and I doubt if I can access the msdos stuff >from FreeBSD for now. This seems to be the case that I said can't work. Apparently wd1 doesn't have Ontrack on it, but Ontrack on the boot disk adjusts for all disks. Bruce From owner-freebsd-bugs Sat Jun 17 04:30:10 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA21470 for bugs-outgoing; Sat, 17 Jun 1995 04:30:10 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA21463 for freebsd-bugs; Sat, 17 Jun 1995 04:30:09 -0700 Date: Sat, 17 Jun 1995 04:30:09 -0700 From: GNU GNATS Message-Id: <199506171130.EAA21463@freefall.cdrom.com> To: freebsd-bugs Subject: List of open Problem Reports Sender: bugs-owner@FreeBSD.org Precedence: bulk This is the list of currently open problem reports [1994/09/14] kern/1 Toshiba MK156FB scsi drive does not work with 2.0 ke [1994/10/07] kern/6 System hangs while using slip or ppp connection [1994/11/13] i386/14 No MBR put on prestine IDE disk drive [1994/11/14] bin/17 "mount -t foo /dev/wd1h /mnt" gives incorrect error [1994/11/18] kern/21 kernel panic. [1994/11/18] conf/22 Cannot use links to share kernel objects [1994/11/23] kern/27 Loopback mounts confuse unmount-on-reboot code [1994/11/30] kern/34 nullfs and union mounts can result in wild pointer r [1994/12/03] kern/39 Recent config changes hosed ft config [1994/12/04] kern/40 Floppy tape probe hosed (FIX) [1994/12/06] kern/42 PC-NFS on -current can't access disks [1994/12/07] docs/43 manpage for keysu is missing. reference from keyinit [1994/12/07] kern/44 ep driver won't work with anything but bnc [1994/12/08] kern/46 ed driver don't know the link0 flag (IFF_LINK0) [1994/12/13] misc/48 /etc/rc does not recover recovery files [1994/12/14] kern/51 Panic accessing NFS mounted file system [1994/12/18] misc/67 It took 20 tries to get free-bsd installed [1994/12/18] misc/68 bininst leaves system kinda hung [1994/12/21] misc/75 Netboot ignores gateway [1994/12/20] conf/76 fdisk can't be trusted. [1994/12/21] i386/79 Reboots sometimes don't complete. [1994/12/23] misc/83 System crash after abrupt end of slip session [1995/01/03] kern/95 Configuring a SLIP device with source = destination [1995/01/09] kern/102 PANIC after running Merged Buffer Cache kernel for a [1995/01/10] bin/104 pax -rwl may corrupt filesystem [1995/01/11] i386/105 Distributed libm (msun) has non-standard error handl [1995/01/13] gnu/107 kernel build produces internal compiler error [1995/01/14] bin/109 at command doesn't parse dates time and doesn't prom [1995/01/14] misc/112 ^C cause panic during install [1995/01/14] bin/113 /bin/csh and /usr/local/bin/tcsh choke on my nasty c [1995/01/14] bin/115 systat iostat display doesn't scale high enough [1995/01/14] bin/116 disk transfer rates reported by systat :iostat are t [1995/01/14] misc/118 use of 386bsd partition tag makes multi-os boot hard [1995/01/14] misc/119 you cannot tune your newfs parameters at intall time [1995/01/14] misc/120 first Initial security report is bogus becuase of ls [1995/01/14] bin/124 traceroute doesn't support -g flag. [1995/01/14] docs/127 locate man page does not have any clues to how the d [1995/01/14] bin/129 fsck cannot take a mount point as an argument [1995/01/14] docs/131 there is no man page for uucpd [1995/01/14] docs/132 gettytab documentation is split between /etc/gettyta [1995/01/14] bin/133 mail program doesn't have editheaders option [1995/01/14] bin/135 not enough ptys; virtual console names conflict with [1995/01/15] bin/146 version of compress is kinda old and slow [1995/01/19] bin/151 One of the pkg_add set /tmp mod to 755 [1995/01/20] bin/153 mount -u improvement for diskless systems [1995/01/21] kern/157 Quota system does not work [1995/01/21] bin/163 telneting sometimes doesn't yield a "login:" prompt [1995/01/21] docs/164 no ptrace(2) manual page. [1995/01/21] docs/165 No documentation on kernel boot flags. [1995/01/21] misc/166 /usr/include/machine/asmacros.h includes uninstalled [1995/01/21] kern/169 Errors from mkdir & mv when directories paths end wi [1995/01/21] bin/170 ar does not print an error message with readonly lib [1995/01/21] docs/171 No documentation on .forward files. [1995/01/21] bin/172 cp -f does not work [1995/01/21] bin/173 rc trys to mount modload fs before ld is available. [1995/01/21] bin/174 Poor error message from stty [1995/01/22] kern/175 Syscons does not recover X graphics mode [1995/01/22] kern/176 EIDRM not defined in errno.h [1995/01/22] docs/177 man pages missing for SYSV IPC funtions [1995/01/23] kern/180 Fiddling with process stack and using scanf with inv [1995/01/24] gnu/183 can't resolve "operator <<" overload [1995/01/24] bin/184 send-pr says "Aborting ..." and happily removes the [1995/01/25] kern/185 kernel stability problems - can't sustain uptimes > [1995/01/25] bin/188 disklabel uses c partition by default, kernel says d [1995/01/30] gnu/196 size of bss in *.o's reported wrong by size [1995/01/30] bin/198 1.1.5.1 pine binary loops; top shows fancy values [1995/02/01] bin/199 quiz(6) reading database bug, pattern matching bug [1995/02/01] misc/202 System hang or reboot without clues, tcp ppp named r [1995/02/14] kern/214 Using wt driver crashes system [1995/02/14] kern/216 /kernel: panic: ffs_alloccg: map corrupted [1995/02/14] docs/218 dbm references from hash(3) [1995/02/16] kern/219 Performance on local net drops too much when SNDBUF [1995/02/16] misc/220 Cancel still doesn't work during install [1995/02/16] misc/221 lots of error messages during unpacking via ftp inst [1995/02/16] i386/222 boot prompt doesn't always work [1995/02/16] misc/223 default domain shouldn't be hostname [1995/02/18] kern/224 ppp net serial [1995/02/18] kern/225 Panic: invalid wire count when GDB kills stopped inf [1995/03/02] misc/229 acos() core dump [1995/03/03] bin/230 C++ contructors not being called [1995/03/05] gnu/231 send-pr initializes Organization with ~/.signature [1995/03/05] docs/232 The mandoc .St macro doesn't work or misses IEEE754 [1995/03/10] misc/236 2.0-950210-SNAP/src/extract.sh references "release" [1995/03/11] kern/238 failed assertion in ncr.c --> no more scsi disk acce [1995/03/13] bin/241 strange behavior of /bin/sh [1995/03/17] kern/247 Berkeley Packet Filter fix [1995/03/17] kern/248 scbus attach/probe information is inconsistent [1995/03/18] i386/251 disklabel(8) refuses to install new bootstrap [1995/03/18] kern/253 Tagged queuing with an Adaptec 2842 controller doesn [1995/03/19] gnu/256 nasty gdb bug back in 031595 system [1995/03/20] docs/263 There is absolutely no documentation for the dialog [1995/03/21] docs/265 mtrace command lacks man pages [1995/03/21] kern/266 ifconfig panics kernel built without option NFS [1995/03/27] bin/274 touch -t with century doesn't work [1995/03/28] kern/275 qic-02 streamer won't work [1995/03/28] kern/277 netstat -r reports entries with negative expire time [1995/03/28] kern/280 the new slice code is bitching about my old slices [1995/03/28] kern/281 Messages printed when checking CD ROM device too ver [1995/03/28] kern/282 buslogic adapter information WAY too verbose [1995/03/29] kern/284 Network gives permission denied [1995/03/30] conf/286 'make depend' on GENERIC kernel stops [1995/03/30] kern/287 Several header files are not consistent [1995/03/31] kern/288 panic: free: multiple frees [1995/04/01] gnu/289 info(1) cannot handle arrow keys on a VT100 [1995/04/01] kern/291 PCI devices still probe/attach after being disabled [1995/04/01] kern/293 wd0: interrupt timeout [1995/04/02] kern/294 Bootstrap has problems with -g compiled kernels [1995/04/04] i386/297 matcd does not play audio CDs from cdplay [1995/04/04] kern/299 SCSI probes stop at ID 7 even for WIDE busses [1995/04/05] bin/300 __fdnlist fails on kernels created by cc -g and stri [1995/04/06] conf/301 Log rotation wastes _much_ to much space [1995/04/06] kern/302 Changing st tapes after extract crashes system [1995/04/08] pending/307 request for a customer id [1995/04/08] bin/308 Do-it-yourself FTP needs to prompt for what to downl [1995/04/08] bin/309 Do-it-yourself FTP deletes /usr/tmp dir rather than [1995/04/08] bin/310 ^C or ^Z in do-it-yourself FTP installation crashes [1995/04/08] bin/311 Do-it-yourself FTP deletes /usr/tmp dir rather than [1995/04/09] bin/314 CTRL-Z during installation crashes install FDIV008 [1995/04/09] bin/315 Kernel and boot block don't agree on kernel name FD [1995/04/09] bin/316 SNAP950322 less stable on IDE than earlier releases [1995/04/09] docs/317 Install README doesn't list matcd as install choice [1995/04/09] bin/318 matcd driver not on boot or fixit floppy FDIV012 [1995/04/09] bin/319 Install doesn't strip sys name in prompt for domain [1995/04/09] bin/320 TCP/IP settings entered b4 install are not kept FDIV [1995/04/09] bin/321 TCP/IP settings given during install are not kept FD [1995/04/09] bin/322 No way to restart a failed FTP download FDIV016 [1995/04/09] bin/323 Creating lost+found causes fsck to stop fsck -y FDIV [1995/04/09] bin/324 /usr/include/sys -> /usr/sys/sys -> /usr/sys/sys FD [1995/04/09] bin/326 Weekly cron generates some usage and error messages [1995/04/09] bin/327 Clock management punishes you if CMOS != GMT FDIV020 [1995/04/09] bin/328 Checking for -c kernel changes randomly hangs FDIV02 [1995/04/09] bin/329 FTP transfers above 99K shown in scientific notation [1995/04/11] kern/332 Incorrect routes can cause system to reset [1995/04/11] kern/336 make world fails on NCR-SCSI machine [1995/04/11] i386/337 seagate controller code hangs on boot. [1995/04/14] docs/341 vnconfig(8) disagrees with its man page [1995/04/14] bin/342 lpd can allow users access to all of root's groups [1995/04/14] kern/343 tcpdump with filter fails on tun and lo devices [1995/04/14] misc/344 Signal 11 when running a user program [1995/04/15] kern/345 panic "biodone: page busy < 0" [1995/04/15] pending/346 request for a customer id [1995/04/17] kern/349 Panic with bad dir [1995/04/20] kern/353 xcdplayer crashes machine (with NCR810 SCSI) [1995/04/20] kern/354 Can't configure two IP aliases with the same network [1995/04/20] misc/355 policy on /usr/local permission in base release [1995/04/20] bin/357 pkg_delete aborts when subcommand fails [1995/04/24] bin/359 BS/DEL is still not quite right. [1995/04/26] kern/365 if_fddisubr.c doesn't compile (it never has...?!?) [1995/04/26] kern/366 queue changes broke ISO tpip code [1995/04/26] kern/367 kernel hangs after ep0 attach message appears [1995/04/26] i386/369 AHA-154X-A problems [1995/04/29] kern/371 panic: msdosfs_unlock: denode not locked [1995/04/30] pending/372 request for a customer id [1995/05/01] gnu/373 In response to admittedly bogus code, gcc emits an o [1995/05/01] kern/374 panic: bad dir [1995/05/01] bin/375 NIS does not seem to work with Kerberos [1995/05/02] kern/376 tcpdump seems to cause spontaneous reboots [1995/05/02] kern/377 Can't config any but first bus of a host adapter [1995/05/03] kern/378 (apparently) bounce buffer code gets used on 32bit b [1995/05/05] kern/383 dd to from /dev/mem panics the machine. [1995/05/06] kern/384 ep0 conflicts with some other drivers [1995/05/06] kern/385 ep0 finds card on irq 10 when it's actually on 11 [1995/05/07] kern/387 scsistrategy doesn't use bounce buffers [1995/05/08] bin/389 Simultaneous creation/deletion of dirs corrupts file [1995/05/11] i386/394 IP multicast not supported by ep driver [1995/05/12] bin/398 VI doesnt do the correct thing [1995/05/13] bin/401 Add REMOTE_* variables [1995/05/13] bin/402 w -n shows non-numeric addresses [1995/05/13] misc/403 FreeBSD 1-compiled tcsh, bash and zsh binaries dump [1995/05/14] pending/404 request for a customer id [1995/05/14] kern/405 The gpio driver does not work with the AT-GPIB, only [1995/05/14] pending/406 Sendmail 8.6.11 was not imported correctly. [1995/05/14] bin/410 bad144(8) should probably scan the bad block remap s [1995/05/14] kern/411 bad144 allow you to add blocks in the remap area [1995/05/14] kern/416 page fault in syscons.c:scopen() [1995/05/14] bin/419 pkg_delete refuses to delete an incompletely added p [1995/05/15] misc/423 Sound devices are too insecure [1995/05/15] kern/424 3COM 3C509 driver doesn't support multicast [1995/05/16] kern/425 arp entries not getting removed when interface chang [1995/05/16] kern/427 eg doesn't work with more than one card [1995/05/16] kern/428 configure is not foolproof [1995/05/19] kern/430 SCSI Tape dont work [1995/05/19] pending/431 Processes sometime's hang and wont die when they hav [1995/05/21] bin/432 mixer should print out the current mixer settings by [1995/05/22] pending/433 request for a customer id [1995/05/22] kern/434 umapfs panics when mounting ufs over itself [1995/05/23] kern/435 mb_map full, network starts jumping off and on, fina [1995/05/23] misc/437 addition for /usr/src/usr.bin/file/Magdir/zyxel [1995/05/23] i386/440 want vidcontrol option to apply settings to all sysc [1995/05/24] bin/441 more does not call vi with +linenum when EDITOR=vi [1995/05/24] gnu/442 when invoked from "make' cc not including name lists [1995/05/25] kern/443 65 sendmails crashes system [1995/05/26] i386/444 GUS sound driver does not seem to work. [1995/05/26] kern/446 unable to diskless-boot a PC when the server mounts [1995/05/26] docs/447 typos in vnconfig.8 [1995/05/26] kern/448 ktrace not enabled in default kernel [1995/05/27] gnu/450 tar --exclude -c doesn't work [1995/05/28] gnu/451 cvsinit/cvs doesn't work as expected with perl [1995/05/28] kern/452 vnode swapping panics [1995/05/28] misc/453 The release/Makefile does not make all des/eBones ta [1995/05/28] bin/454 compile ports/x11/iv and ld got sig11 [1995/05/28] misc/455 library wont compile [1995/05/29] bin/457 We may have an obscure csh bug [1995/05/30] pending/458 px doc does not find include figure [1995/05/30] kern/459 Systems freezes w/ 2842 [1995/05/30] pending/460 request for a customer id [1995/05/30] bin/461 Bogus lseek warning when dump large filesystems [1995/05/30] kern/462 struct utsname.version corrupted after calling uname [1995/05/31] bin/464 dialog_gauge goes one char too far for 100% value [1995/05/31] kern/466 Unexpected disk errors during installation/newfs [1995/06/01] ports/467 utils/kp wrong distfile place after make fetch [1995/06/01] misc/469 ctm leaves temp files after errors [1995/06/01] kern/471 System can not access SCSI DAT tape. [1995/06/01] kern/472 'mount /foo /foo' causes panic: ufs_lock [1995/06/01] gnu/474 typos in /usr/src/gnu/usr.bin/yppush/yppush.c [1995/06/02] bin/476 kvm_openfiles called w/ too small error buffer [1995/06/02] bin/477 telnet autologin ain't working [1995/06/03] docs/480 We don't have an rhosts.5 man page [1995/06/03] pending/481 request for a customer id [1995/06/03] pending/482 request for a customer id [1995/06/04] bin/483 at doesn't seem to accept the time formats it's supp [1995/06/04] bin/486 ls includes utmp.h but doesn't use it [1995/06/05] misc/487 [1995/06/05] kern/488 System can not access SCSI DAT tape. [1995/06/05] bin/489 timed & timedc bugs [1995/06/05] kern/492 sysinstall shows "success" after "no space" failure. [1995/06/07] kern/496 kzip'ed kernel & modload problem [1995/06/07] kern/497 system calls to the kernel for BSDI uname() compatib [1995/06/07] bin/499 pkg_manage percent done is broken/dependancies arent [1995/06/07] bin/500 pkg_manage fails to continue without return sometime [1995/06/08] kern/501 CTRL-ALT-DEL at config> prompt causes trap 12 [FDIV [1995/06/09] bin/502 xdr_double is missing [1995/06/10] kern/503 removing floppy during write causes reboot [1995/06/10] ports/504 NN port defines invalid TMP_DIRECTORY in global.c [1995/06/12] bin/506 "Release" id generated by send-pr looks incorrect. [1995/06/13] bin/508 getnetgrent() prints un-helpful error message (with [1995/06/13] bin/509 netgroup cycle detection is too "greedy" [1995/06/13] bin/510 netgroup host matching doesn't appear to work [1995/06/14] docs/511 bpf(4) is gone [1995/06/14] kern/512 writing to bpf(loopback) causes kernel panic [1995/06/14] bin/513 Suspending and resuming vi gives TIOCGWINSIZ error [1995/06/14] bin/514 Crash recovery impossible without static mt/chflags. [1995/06/14] gnu/515 Info command has no tutorial [1995/06/15] kern/516 Crynwr compatibility mode for PLIP driver. [1995/06/15] bin/517 Bad group change with 'install' [1995/06/15] bin/519 execution of quotacheck from /etc/rc fails [1995/06/15] docs/520 instructions are not clear as to what the url should [1995/06/15] docs/521 catgets() man page error [1995/06/15] kern/522 [1995/06/16] pending/525 The file-command does not recognice adpcm4 /* EOF -- this list has not been truncated */ From owner-freebsd-bugs Sat Jun 17 04:49:33 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA21809 for bugs-outgoing; Sat, 17 Jun 1995 04:49:33 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA21802 ; Sat, 17 Jun 1995 04:49:19 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id VAA25496; Sat, 17 Jun 1995 21:47:20 +1000 Date: Sat, 17 Jun 1995 21:47:20 +1000 From: Bruce Evans Message-Id: <199506171147.VAA25496@godzilla.zeta.org.au> To: davidg@freefall.cdrom.com, freebsd-bugs@freefall.cdrom.com, gibbs@estienne.cs.berkeley.edu Subject: Re: Changed information for PR misc/292 Sender: bugs-owner@FreeBSD.org Precedence: bulk >Synopsis: rfc1323 and rfc1644 support can confuse terminal servers w/SLIP >State-Changed-From-To: open-closed >State-Changed-By: davidg >State-Changed-When: Fri Jun 16 22:58:46 PDT 1995 >State-Changed-Why: >As mentioned in the PR, this isn't a bug in FreeBSD and the decision on >this is that TCP options negotiation should remain enabled. It does seem rather wasteful for slip. The overhead is about 4% for the default mtu. At 115200 bps, as measured by ttcp -r for 80 packets of size 8K: protocol mtu throughput -------------- ---- ----------- cslip 552 9.98 K/sec cslip/no rfc 552 10.39 cslip 1500 10.76 cslip/no rfc 1500 10.92 For catting and `rz -q'ing /kernel, and for larger `ttcp -r's. -------- overheads (%) ------- 86DX2/66-16550 486DX/33-16450 --------------- -------------- protocol mtu throughput r w r w -------------- ---- ----------- ---- ---- ---- ---- cat - 11.25 6.7 2.9 20.3 15.6 cslip 1500 10.76 6.7 3.6 21.5 16.7 pppd 1500 10.74 9.1 4.3 26.2 18.2 ppp (no pred1) 1500 10.80 11.3 6.6 28.6 21.7 zmodem - 10.73 11.4 5.8 27.6 19.2 The overheads were measured by counting to 1 or 2 billion in the background (this takes about 150 seconds on an idle machine) and measuring the relative slowdown. Bruce From owner-freebsd-bugs Sat Jun 17 05:10:01 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA22136 for bugs-outgoing; Sat, 17 Jun 1995 05:10:01 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA22129 ; Sat, 17 Jun 1995 05:10:01 -0700 Date: Sat, 17 Jun 1995 05:10:01 -0700 Message-Id: <199506171210.FAA22129@freefall.cdrom.com> From: Gene Stark Reply-To: Gene Stark To: freebsd-bugs Subject: ports/526: rmail-spool-directory misconfigured in editors/xemacs In-Reply-To: Your message of Sat, 17 Jun 1995 08:06:58 -0400 <199506171206.IAA08249@starkhome.cs.sunysb.edu> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 526 >Category: ports >Synopsis: rmail-spool-directory misconfigured in editors/xemacs >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Jun 17 05:10:00 1995 >Originator: Gene Stark >Organization: >Release: FreeBSD 2.0-BUILT-19950529 i386 >Environment: >Description: When xemacs-19.11 is built (under ports/editors/xemacs), xemacs gets configured with the variable "rmail-spool-directory" set to "/usr/spool/mail/" which does not match the proper directory under FreeBSD. This makes it hard for xemacs to find new mail, and keeps it from determining whether to use "movemail" to get it. >How-To-Repeat: >Fix: Apply the following patch to "paths.el" before compiling: *** paths.el Fri Jan 28 12:01:26 1994 --- /usr/local/lib/xemacs-19.11/lisp/paths.el Sat Jun 17 07:53:12 1995 *************** *** 107,113 **** ((memq system-type '(dgux-unix hpux usg-unix-v unisoft-unix rtu irix silicon-graphics-unix)) "/usr/mail/") ! ((memq system-type '(netbsd)) "/var/mail/") (t "/usr/spool/mail/"))) --- 107,113 ---- ((memq system-type '(dgux-unix hpux usg-unix-v unisoft-unix rtu irix silicon-graphics-unix)) "/usr/mail/") ! ((memq system-type '(netbsd freebsd)) "/var/mail/") (t "/usr/spool/mail/"))) >Audit-Trail: >Unformatted: From owner-freebsd-bugs Sat Jun 17 07:40:03 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA25229 for bugs-outgoing; Sat, 17 Jun 1995 07:40:03 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA25221 ; Sat, 17 Jun 1995 07:40:02 -0700 Date: Sat, 17 Jun 1995 07:40:02 -0700 Message-Id: <199506171440.HAA25221@freefall.cdrom.com> From: koeck@pluto.mpi-hd.mpg.de Reply-To: koeck@pluto.mpi-hd.mpg.de To: freebsd-bugs Subject: kern/527: dump causes assertion in ncr.c In-Reply-To: Your message of Sat, 17 Jun 1995 16:32:37 +0200 <199506171432.QAA03118@fbsd> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 527 >Category: kern >Synopsis: dump causes assertion in ncr.c >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Jun 17 07:40:02 1995 >Originator: Frank Koeck >Organization: Max-Planck-Institut fuer Kernphysik, Heidelberg, Germany >Release: FreeBSD 2.0-BUILT-19950603 i386 >Environment: Pentium 90 System with 32 MB Ram, ELSA Winner 1000, NCR 53c810 SCSI Adapter, Elite Ethernet Card with Digital DC21040 Chip HP C1533A DAT Drive, IBM DPES-31080 Disk FreeBSD 2.0.5-R >Description: The dump command will cause kernel assertion messages of the ncr scsi driver to be printed out. Appended is the printout of two examples showing the kernel message produced by ncr.c. It is possible to restore a previously written dump without a problem. 1. Example: dump to /dev/rst0 (DAT) : ===================================== bash# dump 0fds /dev/nrst0 10000 10000 / DUMP: Date of this level 0 dump: Sat Jun 17 15:22:14 1995 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/rsd0a (/) to /dev/nrst0 DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 13396 tape blocks on 0.01 tape(s). DUMP: dumping (Pass III) [directories] Jun 17 15:22:22 fbsd /kernel: assertion "cp == np->header.cp" failed: file "../. ./pci/ncr.c", line 5395 Jun 17 15:22:22 fbsd /kernel: assertion "cp == np->header.cp" failed: file "../. ./pci/ncr.c", line 5395 Jun 17 15:22:22 fbsd /kernel: assertion "cp" failed: file "../../pci/ncr.c", lin e 5396 Jun 17 15:22:22 fbsd /kernel: assertion "cp" failed: file "../../pci/ncr.c", lin e 5396 DUMP: dumping (Pass IV) [regular files] DUMP: DUMP: 13407 tape blocks on 1 volumes(s) DUMP: Closing /dev/nrst0 DUMP: DUMP IS DONE 2. Example: dump to /dev/null: ============================== bash# dump 0fds /dev/null 10000 10000 / DUMP: Date of this level 0 dump: Sat Jun 17 15:24:16 1995 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/rsd0a (/) to /dev/null DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 13396 tape blocks on 0.01 tape(s). DUMP: dumping (Pass III) [directories] Jun 17 15:24:24 fbsd /kernel: assertion "cp == np->header.cp" failed: file "../. ./pci/ncr.c", line 5395 Jun 17 15:24:24 fbsd /kernel: assertion "cp == np->header.cp" failed: file "../. ./pci/ncr.c", line 5395 Jun 17 15:24:24 fbsd /kernel: assertion "cp" failed: file "../../pci/ncr.c", lin e 5396 Jun 17 15:24:24 fbsd /kernel: assertion "cp" failed: file "../../pci/ncr.c", lin e 5396 DUMP: dumping (Pass IV) [regular files] DUMP: DUMP: 13407 tape blocks on 1 volumes(s) DUMP: Closing /dev/null DUMP: DUMP IS DONE >How-To-Repeat: see above >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Sat Jun 17 09:19:56 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA28885 for bugs-outgoing; Sat, 17 Jun 1995 09:19:56 -0700 Received: from virginia.edu (uvaarpa.Virginia.EDU [128.143.2.7]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id JAA28879 for ; Sat, 17 Jun 1995 09:19:53 -0700 Received: from server.cs.virginia.edu by uvaarpa.virginia.edu id aa05862; 17 Jun 95 12:19 EDT Received: from larc.cs.Virginia.edu (larc-fo.cs.Virginia.EDU) by uvacs.cs.virginia.edu (4.1/5.1.UVA) id AA11713; Sat, 17 Jun 95 12:19:48 EDT Posted-Date: Sat, 17 Jun 1995 12:19:45 -0400 (EDT) Received: by larc.cs.Virginia.edu (4.1/SMI-2.0) id AA12197; Sat, 17 Jun 95 12:19:46 EDT Date: Sat, 17 Jun 1995 12:19:45 -0400 (EDT) From: "Adrian T. Filipi-Martin" Reply-To: adrian@virginia.edu To: bugs@freebsd.org Subject: /usr/src/bin Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@freebsd.org Precedence: bulk Hi folks, Unless I am hallucinating, 2.0.5-RELEASE does not install the sources for /bin. I checked the release/sysinstall/dist.{h,c} files, and find no mention of sbin.* in the source distributions section. The oversight seems to have carried over to menu.c as well. It appears that by adding a single line to menu.c, dist.h and dist.c for the sbin distribution fixes the problem. Appended is a small diff of what I changed. Note that I also made a couple of minor changes to install.c, such that sysinstall could safely be run at a later time to add distributions without destroying your devices or extracting the root.flp. These latter changes are not thoroughly thought through, so work still needs to be done to make sysinstall safe. BTW, the release sources also have object files packed in there. They survive a 'make cleandist', so this is probably the root of the problem. cheers, Adrian adrian@virginia.edu ---->>>>| Support your local programmer, http://www.cs.virginia.edu/~atf3r/ --->>>| STOP Software Patent Abuses NOW! Member: The League for -->>| info at ftp.uu.net:/doc/lpf, print Programming Freedom ->| "join.ps.Z" for an application -------------------------------------------------------------- diff -cr release/sysinstall/dist.c release.new/sysinstall/dist.c *** release/sysinstall/dist.c Sat Jun 10 05:35:49 1995 --- release.new/sysinstall/dist.c Sat Jun 17 10:50:13 1995 *************** *** 104,109 **** --- 104,110 ---- { "slibexec", "/usr/src", &SrcDists, DIST_SRC_LIBEXEC, NULL }, { "slkm", "/usr/src", &SrcDists, DIST_SRC_LKM, NULL }, { "srelease", "/usr/src", &SrcDists, DIST_SRC_RELEASE, NULL }, + { "sbin", "/usr/src", &SrcDists, DIST_SRC_BIN, NULL }, { "ssbin", "/usr/src", &SrcDists, DIST_SRC_SBIN, NULL }, { "sshare", "/usr/src", &SrcDists, DIST_SRC_SHARE, NULL }, { "ssys", "/usr/src", &SrcDists, DIST_SRC_SYS, NULL }, diff -cr release/sysinstall/dist.h release.new/sysinstall/dist.h *** release/sysinstall/dist.h Sat Jun 10 04:59:20 1995 --- release.new/sysinstall/dist.h Sat Jun 17 10:48:59 1995 *************** *** 46,51 **** --- 46,52 ---- #define DIST_SRC_SYS 0x0800 #define DIST_SRC_UBIN 0x1000 #define DIST_SRC_USBIN 0x2000 + #define DIST_SRC_BIN 0x4000 #define DIST_SRC_ALL 0xFFFF /* Subtypes for XFree86 distribution */ diff -cr release/sysinstall/install.c release.new/sysinstall/install.c *** release/sysinstall/install.c Sat Jun 10 03:58:37 1995 --- release.new/sysinstall/install.c Sat Jun 17 11:39:17 1995 *************** *** 271,277 **** return 0; configFstab(); } ! if (!SystemWasInstalled && !root_extract()) { msgConfirm("Failed to load the ROOT distribution. Please correct\nthis problem and try again."); return 0; } --- 271,277 ---- return 0; configFstab(); } ! if (RunningAsInit && !SystemWasInstalled && !root_extract()) { msgConfirm("Failed to load the ROOT distribution. Please correct\nthis problem and try again."); return 0; } *************** *** 290,296 **** } /* Resurrect /dev after bin distribution screws it up */ ! if (!SystemWasInstalled) { msgNotify("Remaking all devices.. Please wait!"); if (vsystem("cd /dev; sh MAKEDEV all")) msgConfirm("MAKEDEV returned non-zero status"); --- 290,296 ---- } /* Resurrect /dev after bin distribution screws it up */ ! if (RunningAsInit && !SystemWasInstalled) { msgNotify("Remaking all devices.. Please wait!"); if (vsystem("cd /dev; sh MAKEDEV all")) msgConfirm("MAKEDEV returned non-zero status"); diff -cr release/sysinstall/menus.c release.new/sysinstall/menus.c *** release/sysinstall/menus.c Sat Jun 10 04:59:24 1995 --- release.new/sysinstall/menus.c Sat Jun 17 11:19:55 1995 *************** *** 457,462 **** --- 457,464 ---- DMENU_SET_FLAG, &SrcDists, DIST_SRC_LKM, 0, dmenuFlagCheck }, { "release", "/usr/src/release (release-generation tools) [533K]", DMENU_SET_FLAG, &SrcDists, DIST_SRC_RELEASE, 0, dmenuFlagCheck }, + { "bin", "/usr/src/bin (system binaries) [???MB]", + DMENU_SET_FLAG, &SrcDists, DIST_SRC_BIN, 0, dmenuFlagCheck }, { "sbin", "/usr/src/sbin (system binaries) [1.3MB]", DMENU_SET_FLAG, &SrcDists, DIST_SRC_SBIN, 0, dmenuFlagCheck }, { "share", "/usr/src/share (documents and shared files) [10MB]", From owner-freebsd-bugs Sat Jun 17 12:04:31 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA02354 for bugs-outgoing; Sat, 17 Jun 1995 12:04:31 -0700 Received: from hkpu01.polyu.edu.hk (hkpu01.polyu.edu.hk [158.132.14.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA02344 for ; Sat, 17 Jun 1995 12:04:18 -0700 Received: by hkpu01.polyu.edu.hk (4.1/SMI-4.1) id AA10543; Sun, 18 Jun 95 03:03:07 HKT Date: Sun, 18 Jun 95 03:03:07 HKT From: en152062@hkpu01.polyu.edu.hk (Hi Little ... ) Message-Id: <9506171903.AA10543@hkpu01.polyu.edu.hk> To: bugs@FreeBSD.org Sender: bugs-owner@FreeBSD.org Precedence: bulk Dear Sir, I have tried to install the FreeBSD 2.0-RELEASE package. But I found problems in my machine. I have two ethernet network cards. The BSD kernel can only detect only one network. And the hardware information of the detected card was wrong. I have two cards, Port Add IRQ Type 1. 300 15 NE2000 2. 320 12 NE2000 But the kernel detected as 300, IRQ 5 and the other cards was disapeared. Would you please tell me how to solve this problem? Am I need to recompile the kernel? If yes, how to recompile it? (similar to linux?) Concerning the BSD CD-rom, would you please tell me what includes in the disc. (eg. kernel, source, gcc...) Where can I buy it and how much for it (Hong Kong)? Alan Ng From owner-freebsd-bugs Sat Jun 17 13:25:28 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA03718 for bugs-outgoing; Sat, 17 Jun 1995 13:25:28 -0700 Received: from vegemite.Stanford.EDU (2842@vegemite.Stanford.EDU [36.159.0.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA03710 for ; Sat, 17 Jun 1995 13:25:27 -0700 Received: (hlew@localhost) by vegemite.Stanford.EDU (8.6.10/8.6.4) id NAA17592; Sat, 17 Jun 1995 13:19:09 -0700 Date: Sat, 17 Jun 1995 13:19:08 -0700 (PDT) From: Howard Lew To: Bruce Evans cc: bde@zeta.org.au, bugs@FreeBSD.org Subject: Re: 2.05R panics on boot In-Reply-To: <199506170757.RAA18958@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@FreeBSD.org Precedence: bulk On Sat, 17 Jun 1995, Bruce Evans wrote: > >> Only one case can't possibly work: loading the bootstrap off a floppy > >> and then attempting to boot from a hard disk (e.g., by typing > >> sd(1,a)/kernel). The boot code doesn't know about DM, so it won't > >> work if DM needs to be loaded. > >> > > >Right now the only way I can boot up FreeBSD system on the Ontrack DM > >system is by using boot.flp and entering wd(1,a)/kernel. This is very > >annoying. I have not tried and I doubt if I can access the msdos stuff > >from FreeBSD for now. > > This seems to be the case that I said can't work. Apparently wd1 doesn't > have Ontrack on it, but Ontrack on the boot disk adjusts for all disks. Yep, that's correct. It's too bad that DOS can't handle more than 504 MB for a large EIDE drive. Because if it could I wouldn't need to install the Ontrack DM overlay, and then FreeBSD would work like a charm. So can DOS access more than 504 MB per partition on SCSI drives? Oh well.... I guess the only alternative is to swap the hard drive cables and redo the master/slave jumpers... :-( Thanks for your help. From owner-freebsd-bugs Sat Jun 17 13:26:59 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA03808 for bugs-outgoing; Sat, 17 Jun 1995 13:26:59 -0700 Received: from wall.olivetti.nl (wall.olivetti.nl [193.67.10.65]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA03789 for ; Sat, 17 Jun 1995 13:26:52 -0700 Received: (from nobody@localhost) by wall.olivetti.nl (8.6.9/8.6.9) id WAA13191 for ; Sat, 17 Jun 1995 22:26:46 +0200 Received: from oli1.olivetti.nl(192.87.20.30) by wall.olivetti.nl via smap (V1.3) id sma013189; Sat Jun 17 22:26:41 1995 Received: by oli1.olivetti.nl (Smail3.1.28.1 #6) id m0sN4S0-000QezC; Sat, 17 Jun 95 22:26 MET DST Received: by olivaw.olivetti.nl (Smail3.1.28.1 #5) id m0sN4QP-000SF9C; Sat, 17 Jun 95 22:25 MET DST Message-Id: Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 3.3 v118.2) Received: by NeXT.Mailer (1.118.2) Date: Sat, 17 Jun 95 22:25:00 +0200 To: bugs@FreeBSD.org Subject: Disk errors installing 2.0.5-REL Reply-To: paulzn@olivetti.nl From: paulzn@olivetti.nl (Paul van der Zwan) Sender: bugs-owner@FreeBSD.org Precedence: bulk I've been unable to install 2.0.5-REL on a machine that ran the latest SNAP without a problem and runs DOS without any disk-related problems I keep getting an error code of 10 on some writes when making the root fs. The disk is a Micropolis 1558 ESDI ( 1224 cyl 15 hds 35 sect.) connected to a WD1007 controller which remaps it to 814 cyl 15 hds 51 sect which is also the geometry DOS uses. When I run FreeBSD fdisk from the boot floppy ( I have tried the original and the one from UPDATES), it keep showing the geometry as 840 cyls which is wrong, even if I manually enter 814 cyls. When I enable badblock detection it detect a bad block every 35 blocks which looks very suspicious to me. Even after a low level format it keeps finding bad blocks every 35 blocks. Any suggestions ??? TIA Paul From owner-freebsd-bugs Sat Jun 17 15:41:26 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA08536 for bugs-outgoing; Sat, 17 Jun 1995 15:41:26 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id PAA08526 for ; Sat, 17 Jun 1995 15:41:25 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA16034; Sat, 17 Jun 95 16:34:34 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9506172234.AA16034@cs.weber.edu> Subject: Re: 2.05R panics on boot To: hlew@genome.Stanford.EDU (Howard Lew) Date: Sat, 17 Jun 95 16:34:33 MDT Cc: bugs@FreeBSD.org In-Reply-To: from "Howard Lew" at Jun 16, 95 11:47:29 pm X-Mailer: ELM [version 2.4dev PL52] Sender: bugs-owner@FreeBSD.org Precedence: bulk > If I install the boot manager after booting up DOS from hard drive C, the > boot manager comes up after the Ontrack DM, but when I choose the FreeBSD > partition (wd1), OS-BS just hangs the system. But if I choose the MSDOS > partition, it doesn't crash. This is the correct installation. > If I install OS-BS after booting from a DOS floppy, OS-BS shows the > OS menu before it gets to the Ontrack DM. If I choose FreeBSD, it > comes up fine (perfecto!) But if I choose MSDOS, the system says: > Missing Operating System. :-( This is messed; you have overwritten part of the DM. > I have also toggled around the writing of the active partion flag on > bootup with no luck either. This is not relevent to the problem, so you don't need to play with it. > As for setting the ID in OS-BS... Do I change the value (I think it was > 50 something) to a DOS value? And should I do this after booting from > a DOS floppy? OK. You can *probably* do the following: 1) Do the correct installion of DM. 2) Install OS-BS after booting from the hard drive. Now installing FreeBSD should cause the FreeBSD to see the DM and write its partition entry into the offset partition. If it doesn't work, you need to hit up Bruce (or whoever currently owns that code). 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-bugs Sat Jun 17 15:53:51 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA10534 for bugs-outgoing; Sat, 17 Jun 1995 15:53:51 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id PAA10526 for ; Sat, 17 Jun 1995 15:53:49 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA16053; Sat, 17 Jun 95 16:44:00 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9506172244.AA16053@cs.weber.edu> Subject: Re: 2.05R panics on boot To: hlew@genome.Stanford.EDU (Howard Lew) Date: Sat, 17 Jun 95 16:43:59 MDT Cc: bde@zeta.org.au, bugs@FreeBSD.org In-Reply-To: from "Howard Lew" at Jun 16, 95 11:53:28 pm X-Mailer: ELM [version 2.4dev PL52] Sender: bugs-owner@FreeBSD.org Precedence: bulk > Right now the only way I can boot up FreeBSD system on the Ontrack DM > system is by using boot.flp and entering wd(1,a)/kernel. This is very > annoying. I have not tried and I doubt if I can access the msdos stuff > from FreeBSD for now. OK, this is dangerous. What you have done is installed the BSD partition, I think overlapping the end of the DOS partition (assuming you put it at the offset the BIOS said when booting DOS off the C drive and running pfdisk). What you need to do is move it higher. Apparently your DM version is different so it isn't recognized. If you fill up the DOS partition, you will overwrite the BSD boot sector and label, etc. Probably you made the BSD parition entry in the DM pseudo-partition table. When you boot off the floppy, is it directly from the floppy or from the DM boot menu? This would tell for sure. You should boot DOS off floppy and run pfdisk. Then you should boot DOS off of C: and run pfdisk. That information will tell us if we can hack with pfdisk or if you probably shouldn't install at all. > Is there a way to easily make a boot disk that loads the Ontrack DM and > then boots up FreeBSD from wd1 or from DOS? Yes, once you have the partition and disklabel information set up correctly, there's DOSBOOT.COM. 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-bugs Sat Jun 17 16:30:19 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA17332 for bugs-outgoing; Sat, 17 Jun 1995 16:30:19 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id QAA17320 for ; Sat, 17 Jun 1995 16:30:17 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA16151; Sat, 17 Jun 95 17:20:27 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9506172320.AA16151@cs.weber.edu> Subject: Re: 2.05R panics on boot To: bde@zeta.org.au (Bruce Evans) Date: Sat, 17 Jun 95 17:20:27 MDT Cc: bde@zeta.org.au, hlew@genome.Stanford.EDU, bugs@FreeBSD.org In-Reply-To: <199506170757.RAA18958@godzilla.zeta.org.au> from "Bruce Evans" at Jun 17, 95 05:57:56 pm X-Mailer: ELM [version 2.4dev PL52] Sender: bugs-owner@FreeBSD.org Precedence: bulk > >Right now the only way I can boot up FreeBSD system on the Ontrack DM > >system is by using boot.flp and entering wd(1,a)/kernel. This is very > >annoying. I have not tried and I doubt if I can access the msdos stuff > >from FreeBSD for now. > > This seems to be the case that I said can't work. Apparently wd1 doesn't > have Ontrack on it, but Ontrack on the boot disk adjusts for all disks. YES. Makes perfect sense, actually. Once you are booting BSD, the disk BSD is on is hat it thinks the boot disk is. It can't know the INT 13 chaining used by the BIOS. You could manually fix this up. I hesistate to describe the process (so I won't) since it's rather complex and requires a deep understanding of the boot process. In broad strokes, it would involve modifying the second disks partition table, installing, modifying the installed disk label and partition table, and going from there. If you *only* have BSD on the second drive, and are willing to blow it away, you can get the same effect by making the BSD drive the primary drive, installing OnTrack (assuming you have it), then installing BSD onto what is now the first drive. When you put ehe drive back to the second drive and put the original drive back on, it should work. This is complicated, but not as complicated as the geometry mathematics required for just "fixing it up". Hacking partitions and disklabels is a real pain, comparatively. The final alternative is to continue using a boot floppy to get BSD. The DOSBOOT.COM might be more easily hacked to work -- but it depends on if negative offsets are allowed. 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-bugs Sat Jun 17 17:22:33 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA25127 for bugs-outgoing; Sat, 17 Jun 1995 17:22:33 -0700 Received: from whisker.internet-eireann.ie (whisker.internet-eireann.ie [194.9.34.204]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA25105 for ; Sat, 17 Jun 1995 17:22:28 -0700 Received: from localhost (localhost [127.0.0.1]) by whisker.internet-eireann.ie (8.6.11/8.6.9) with SMTP id BAA04230; Sun, 18 Jun 1995 01:20:48 +0100 X-Authentication-Warning: whisker.internet-eireann.ie: Host localhost didn't use HELO protocol To: adrian@virginia.edu cc: bugs@freebsd.org Subject: Re: /usr/src/bin In-reply-to: Your message of "Sat, 17 Jun 1995 12:19:45 EDT." Date: Sun, 18 Jun 1995 01:20:47 +0100 Message-ID: <4227.803434847@whisker.internet-eireann.ie> From: "Jordan K. Hubbard" Sender: bugs-owner@freebsd.org Precedence: bulk > Unless I am hallucinating, 2.0.5-RELEASE does not install the > sources for /bin. I checked the release/sysinstall/dist.{h,c} files, and > find no mention of sbin.* in the source distributions section. The > oversight seems to have carried over to menu.c as well. Sigh.. You're right! I found this out myself just recently. Your patches look good and will be incorporated - thanks! Jordan From owner-freebsd-bugs Sat Jun 17 19:30:05 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA10132 for bugs-outgoing; Sat, 17 Jun 1995 19:30:05 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA10117 ; Sat, 17 Jun 1995 19:30:04 -0700 Date: Sat, 17 Jun 1995 19:30:04 -0700 Message-Id: <199506180230.TAA10117@freefall.cdrom.com> From: Heikki Suonsivu Reply-To: Heikki Suonsivu To: freebsd-bugs Subject: kern/528: interrupt-level buffer overflows In-Reply-To: Your message of Sun, 18 Jun 1995 05:27:39 +0300 <199506180227.FAA01387@katiska.clinet.fi> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 528 >Category: kern >Synopsis: slow 386 reports excessive interrupt-level buffer overlows >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Jun 17 19:30:02 1995 >Originator: Heikki Suonsivu >Organization: Helsinki University of Technology, Finland >Release: FreeBSD 2.0-BUILT-19950507 i386 >Environment: 386-16, IDE disk, 10M. A ppp router, 38400 leased line. 16550 serial port. wd8013. It is dedicated solely for the purpose of routing this one single connection. >Description: Kernel spits out lot of these Jun 18 05:14:47 pommi /kernel: sio1: 119 more interrupt-level buffer over flows (total 3642) Jun 18 05:14:47 pommi /kernel: sio1: 119 more interrupt-level buffer overflows ( total 3642) It also very easily reboots when lots of PPP load exits. Low tcp performance hints that it is loosing lots of data. >How-To-Repeat: Use FreeBSD as a router for a PPP connection on a slow machine. >Fix: I think this feature has already been discussed; grepping 'interrupt-level' from FAQ's didn't help. If this is a feature which can be worked around, this might be a doc-bug? However, I find it curous how a 386-16 could be too slow to respond for a 38400 bps link? >Audit-Trail: >Unformatted: From owner-freebsd-bugs Sat Jun 17 22:20:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA26849 for bugs-outgoing; Sat, 17 Jun 1995 22:20:02 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA26842 ; Sat, 17 Jun 1995 22:20:01 -0700 Date: Sat, 17 Jun 1995 22:20:01 -0700 Message-Id: <199506180520.WAA26842@freefall.cdrom.com> From: Scott Hazen Mueller Reply-To: Scott Hazen Mueller To: freebsd-bugs Subject: conf/529: Please put mountd's '-n' flag into /etc/sysconfig In-Reply-To: Your message of Sat, 17 Jun 1995 22:13:17 -0700 <199506180513.WAA04449@zorch.sf-bay.org> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 529 >Category: conf >Synopsis: Please put mountd's '-n' flag into /etc/sysconfig >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: change-request >Submitter-Id: current-users >Arrival-Date: Sat Jun 17 22:20:01 1995 >Originator: Scott Hazen Mueller >Organization: At Home; Salida, CA >Release: FreeBSD 2.0-BUILT-19950603 i386 >Environment: >Description: The mountd command can have a parameter that is system-specific (-n), but the parameter is not customizable through /etc/sysconfig, and my custom change got lost in the 2.0R -> 2.0.5R upgrade. I'd like to not lose it again in the next upgrade. >How-To-Repeat: >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Sat Jun 17 22:35:55 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA28259 for bugs-outgoing; Sat, 17 Jun 1995 22:35:55 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA28251 for ; Sat, 17 Jun 1995 22:35:53 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id WAA00568; Sat, 17 Jun 1995 22:35:54 -0700 From: "Rodney W. Grimes" Message-Id: <199506180535.WAA00568@gndrsh.aac.dev.com> Subject: Re: conf/529: Please put mountd's '-n' flag into /etc/sysconfig To: scott@zorch.sf-bay.org Date: Sat, 17 Jun 1995 22:35:54 -0700 (PDT) Cc: freebsd-bugs@freefall.cdrom.com In-Reply-To: <199506180520.WAA26842@freefall.cdrom.com> from "Scott Hazen Mueller" at Jun 17, 95 10:20:01 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: 1185 Sender: bugs-owner@FreeBSD.org Precedence: bulk > > > >Number: 529 > >Category: conf > >Synopsis: Please put mountd's '-n' flag into /etc/sysconfig > >Confidential: no > >Severity: non-critical > >Priority: low > >Responsible: freebsd-bugs (FreeBSD bugs mailing list) > >State: open > >Class: change-request > >Submitter-Id: current-users > >Arrival-Date: Sat Jun 17 22:20:01 1995 > >Originator: Scott Hazen Mueller > >Organization: > At Home; Salida, CA > >Release: FreeBSD 2.0-BUILT-19950603 i386 > >Environment: > >Description: > > The mountd command can have a parameter that is system-specific (-n), > but the parameter is not customizable through /etc/sysconfig, and my > custom change got lost in the 2.0R -> 2.0.5R upgrade. I'd like to not > lose it again in the next upgrade. > > >How-To-Repeat: > >Fix: > >Audit-Trail: > >Unformatted: Thank you for pointing this out. I have saved this bug report on my hit list for the next round of changes to /etc/{rc, netstart, sysconfig}. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-bugs Sat Jun 17 22:44:51 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA29195 for bugs-outgoing; Sat, 17 Jun 1995 22:44:51 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA29143 for ; Sat, 17 Jun 1995 22:44:33 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id PAA15480; Sun, 18 Jun 1995 15:38:55 +1000 Date: Sun, 18 Jun 1995 15:38:55 +1000 From: Bruce Evans Message-Id: <199506180538.PAA15480@godzilla.zeta.org.au> To: bde@zeta.org.au, terry@cs.weber.edu Subject: Re: 2.05R panics on boot Cc: bugs@FreeBSD.org, hlew@genome.Stanford.EDU Sender: bugs-owner@FreeBSD.org Precedence: bulk >> This seems to be the case that I said can't work. Apparently wd1 doesn't >> have Ontrack on it, but Ontrack on the boot disk adjusts for all disks. >YES. >Makes perfect sense, actually. Once you are booting BSD, the disk BSD is >on is hat it thinks the boot disk is. It can't know the INT 13 chaining >used by the BIOS. It's not clear to me whether this is an installation error. Why is Ontrack managling disks that it isn't on? Can the problem be fixed by installing Ontrack on all disks, or configuring it to only manage the disk(s) that it is installed on? >You could manually fix this up. >I hesistate to describe the process (so I won't) since it's rather complex >and requires a deep understanding of the boot process. In broad strokes, >it would involve modifying the second disks partition table, installing, >modifying the installed disk label and partition table, and going from there. This won't work. If there is only one partition table, then the FreeBSD boot loader and FreeBSD proper will see the same one, and FreeBSD proper needs to see a table modified as above. >If you *only* have BSD on the second drive, and are willing to blow it >away, you can get the same effect by making the BSD drive the primary >drive, installing OnTrack (assuming you have it), then installing BSD onto >what is now the first drive. >When you put ehe drive back to the second drive and put the original drive >back on, it should work. Only if Ontrack doesn't doubly manage the second drive after you put it back. I think we're finding complications where none exist. It's hard to debug without seeing the output of boot -v and sysinstall. Bruce From owner-freebsd-bugs Sat Jun 17 22:50:55 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA29958 for bugs-outgoing; Sat, 17 Jun 1995 22:50:55 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA29938 for ; Sat, 17 Jun 1995 22:50:47 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id PAA15709; Sun, 18 Jun 1995 15:47:18 +1000 Date: Sun, 18 Jun 1995 15:47:18 +1000 From: Bruce Evans Message-Id: <199506180547.PAA15709@godzilla.zeta.org.au> To: bde@zeta.org.au, hlew@genome.Stanford.EDU Subject: Re: 2.05R panics on boot Cc: bugs@FreeBSD.org Sender: bugs-owner@FreeBSD.org Precedence: bulk >> This seems to be the case that I said can't work. Apparently wd1 doesn't >> have Ontrack on it, but Ontrack on the boot disk adjusts for all disks. >Yep, that's correct. Isn't there a way to stop it adjusting for all disks? >It's too bad that DOS can't handle more than 504 MB for a large EIDE >drive. Because if it could I wouldn't need to install the Ontrack DM >overlay, and then FreeBSD would work like a charm. DOS has no problems handling >= 504 MB. This is a BIOS problem. >So can DOS access more than 504MB per partition on SCSI drives? Yes, up to 8GB, provided the BIOS supports it (I haven't figured out how to make my U34F or BT445C support more than 1024MB - they always use the 64H 32S geometry). Modern EIDE BIOSes also support up to 8GB. Disk managers are only required for old BIOSes. >Oh well.... I guess the only alternative is to swap the hard drive cables >and redo the master/slave jumpers... :-( How would that help? You would still need Ontrack somewhere to use more than 504MB for DOS on the big drive. Putting Ontrack somewhere apparently affects everywhere. Bruce