From owner-freebsd-bugs Sun Mar 26 00:15:28 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA03673 for bugs-outgoing; Sun, 26 Mar 1995 00:15:28 -0800 Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id AAA03667; Sun, 26 Mar 1995 00:15:17 -0800 Received: from localhost (localhost [127.0.0.1]) by grunt.grondar.za (8.6.11/8.6.9) with SMTP id KAA03681; Sun, 26 Mar 1995 10:15:02 +0200 Message-Id: <199503260815.KAA03681@grunt.grondar.za> X-Authentication-Warning: grunt.grondar.za: Host localhost didn't use HELO protocol To: current@FreeBSD.org cc: freebsd-bugs@freefall.cdrom.com Subject: Re: conf/273: syslogd no longer gets loaded at boot time Date: Sun, 26 Mar 1995 10:14:59 +0200 From: Mark Murray Sender: bugs-owner@FreeBSD.org Precedence: bulk > > >Number: 273 > >Category: conf > >Synopsis: syslogd no longer gets loaded at boot time > >Description: > > At boot time syslogd craps out with "cant bind to requested address" > > >How-To-Repeat: > > Reboot :-) > > >Fix: > > run syslogd as root. A whole bunch of queued messages (hardware id stuff from > the boot) gets dumped to the screen. Better Fix: move the loading of syslogd to _after_ . /etc/netstart This is how it was done before the great rc reorganise. M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 From owner-freebsd-bugs Sun Mar 26 08:24:09 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA19681 for bugs-outgoing; Sun, 26 Mar 1995 08:24:09 -0800 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 IAA19667; Sun, 26 Mar 1995 08:23:43 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id CAA27027; Mon, 27 Mar 1995 02:20:44 +1000 Date: Mon, 27 Mar 1995 02:20:44 +1000 From: Bruce Evans Message-Id: <199503261620.CAA27027@godzilla.zeta.org.au> To: current@FreeBSD.org, mark@grondar.za Subject: Re: conf/273: syslogd no longer gets loaded at boot time Cc: freebsd-bugs@freefall.cdrom.com Sender: bugs-owner@FreeBSD.org Precedence: bulk >> >Description: >> >> At boot time syslogd craps out with "cant bind to requested address" >> >> >How-To-Repeat: >> >> Reboot :-) >> >> >Fix: >> >> run syslogd as root. A whole bunch of queued messages (hardware id stuff from >> the boot) gets dumped to the screen. >Better Fix: move the loading of syslogd to _after_ . /etc/netstart This is not quite right either: 1) messages logged by the processes started in /etc/netstart may be lost. 2) syslogd complains about /var/run/utmp being removed and a few "wall" messages may be lost. >This is how it was done before the great rc reorganise. Then it was quite right. Parts of the apparently chaotic order of starting up processes were to avoid problems such as the above. Bruce From owner-freebsd-bugs Sun Mar 26 10:22:05 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA21077 for bugs-outgoing; Sun, 26 Mar 1995 10:22:05 -0800 Received: (from wpaul@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA21062; Sun, 26 Mar 1995 10:22:04 -0800 Date: Sun, 26 Mar 1995 10:22:04 -0800 From: Bill Paul Message-Id: <199503261822.KAA21062@freefall.cdrom.com> To: mark@grondar.za, wpaul, freebsd-bugs Subject: Changed information for PR conf/273 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: syslogd no longer gets loaded at boot time State-Changed-From-To: open-closed State-Changed-By: wpaul State-Changed-When: Sun Mar 26 10:19:31 PST 1995 State-Changed-Why: Fixed: syslogd startup has been moved into /etc/netstart. It's brought up right after the network interfaces, hostname and domainname have been configured but right before the other daemons are started. From owner-freebsd-bugs Sun Mar 26 10:51:20 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA21731 for bugs-outgoing; Sun, 26 Mar 1995 10:51:20 -0800 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 KAA21725; Sun, 26 Mar 1995 10:51:19 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA06789; Sun, 26 Mar 95 11:45:03 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9503261845.AA06789@cs.weber.edu> Subject: Re: List of open PRs To: joerg@freefall.cdrom.com (Joerg Wunsch) Date: Sun, 26 Mar 95 11:45:02 MST Cc: freebsd-bugs@freefall.cdrom.com In-Reply-To: <199503251325.OAA22072@freefall.cdrom.com> from "Joerg Wunsch" at Mar 25, 95 02:25:12 pm X-Mailer: ELM [version 2.4dev PL52] Sender: bugs-owner@FreeBSD.org Precedence: bulk > > This is the list of open problem reports > May I suggest that this should also include an "as of" date, since not all mail propagation is instantaneous? And a note about posting frequency... And a BEGIN/END encapsulation of the list so we can know it wasn't truncated by a mailer somewhere? Regards, 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 Sun Mar 26 13:52:00 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA28834 for bugs-outgoing; Sun, 26 Mar 1995 13:52:00 -0800 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 NAA28792 for ; Sun, 26 Mar 1995 13:51:50 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA27947; Sun, 26 Mar 1995 23:51:31 +0200 Received: by sax.sax.de (8.6.9/8.6.9-s1) with UUCP id XAA21104 for freebsd-bugs@freefall.cdrom.com; Sun, 26 Mar 1995 23:51:30 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id WAA12615 for freebsd-bugs@freefall.cdrom.com; Sun, 26 Mar 1995 22:31:56 +0200 From: J Wunsch Message-Id: <199503262031.WAA12615@uriah.heep.sax.de> Subject: Re: List of open PRs To: freebsd-bugs@freefall.cdrom.com Date: Sun, 26 Mar 1995 22:31:55 +0200 (MET DST) In-Reply-To: <9503261845.AA06789@cs.weber.edu> from "Terry Lambert" at Mar 26, 95 11:45: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: 1004 Sender: bugs-owner@FreeBSD.org Precedence: bulk As Terry Lambert wrote: > > > > > This is the list of open problem reports > > > > May I suggest that this should also include an "as of" date, since > not all mail propagation is instantaneous? What about the Date: header? I thought that's sufficient? > And a note about posting frequency... weekly. > And a BEGIN/END encapsulation of the list so we can know it wasn't > truncated by a mailer somewhere? Ok, easy. Jordan, can you include this? *** list-pr.orig Sun Mar 26 22:25:49 1995 --- list-pr Sun Mar 26 22:29:11 1995 *************** *** 13,18 **** --- 13,20 ---- print MAIL "This is the list of open problem reports\n\n"; + print MAIL "BEGIN\n\n"; + while() { chop; if(/^>Number:/) { *************** *** 34,39 **** --- 36,43 ---- . "\n"; } } + + print MAIL "BEGIN\n"; close(Q); close(MAIL); -- 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 Sun Mar 26 14:23:01 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA03408 for bugs-outgoing; Sun, 26 Mar 1995 14:23:01 -0800 Received: from post.demon.co.uk (post.demon.co.uk [158.152.1.72]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id OAA03400 for ; Sun, 26 Mar 1995 14:22:59 -0800 Received: from palmer.demon.co.uk by post.demon.co.uk id aa04062; 26 Mar 95 23:07 GMT-60:00 Received: from localhost (gary@localhost [127.0.0.1]) by palmer.demon.co.uk (8.6.9/8.6.9) with SMTP id XAA03060 ; Sun, 26 Mar 1995 23:06:54 +0100 X-Authentication-Warning: palmer.demon.co.uk: Host localhost didn't use HELO protocol To: Joerg Wunsch cc: freebsd-bugs@freefall.cdrom.com Subject: Re: List of open PRs In-reply-to: Your message of "Sun, 26 Mar 1995 22:31:55 +0200." <199503262031.WAA12615@uriah.heep.sax.de> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3056.796255612.1@palmer.demon.co.uk> Date: Sun, 26 Mar 1995 23:06:53 +0100 Message-ID: <3057.796255613@palmer.demon.co.uk> From: Gary Palmer Sender: bugs-owner@FreeBSD.org Precedence: bulk In message <199503262031.WAA12615@uriah.heep.sax.de>, J Wunsch writes: >Jordan, can you include this? > >*** list-pr.orig Sun Mar 26 22:25:49 1995 >--- list-pr Sun Mar 26 22:29:11 1995 >*************** >*** 13,18 **** >--- 13,20 ---- > > print MAIL "This is the list of open problem reports\n\n"; > >+ print MAIL "BEGIN\n\n"; >+ > while() { > chop; > if(/^>Number:/) { >*************** >*** 34,39 **** >--- 36,43 ---- > . "\n"; > } > } >+ >+ print MAIL "BEGIN\n"; ^^^^^END???? :-) Gary From owner-freebsd-bugs Sun Mar 26 15:42:47 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA18371 for bugs-outgoing; Sun, 26 Mar 1995 15:42:47 -0800 Received: from gate2.internet-eireann.ie (gate2.internet-eireann.ie [194.9.1.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA18325 for ; Sun, 26 Mar 1995 15:42:34 -0800 From: acs@gate1.internet-eireann.ie Received: from acs.internet-eireann.ie (acs.internet-eireann.ie [194.9.32.177]) by gate2.internet-eireann.ie (8.6.8/8.6.9) with SMTP id AAA11094 for ; Mon, 27 Mar 1995 00:45:17 +0100 Date: Mon, 27 Mar 1995 00:45:17 +0100 Message-Id: <199503262345.AAA11094@gate2.internet-eireann.ie> X-Sender: acs@mail.internet-eireann.ie (Unverified) X-Mailer: Windows Eudora Version 1.4.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: bugs@FreeBSD.org Subject: v2.0 install Sender: bugs-owner@FreeBSD.org Precedence: bulk Hi, I was looking for a mailbox to send install problems to, but i couldn't find one in the documentation, so please redirect me. I'll include some text on my problem anyhow. I've got an ESDI hard disk. The 1st partiton is 220 mb for DOS, and the rest, 101 mb, is for FreeBSD. I've booted off the boot_144.flp image and have done my fdisk work. I then used disklabel to set-up partition 'a' as 76 mb for '/' and 'b' as 25 mb for 'swap'. So I've made everything as simple as possible. When I come out of disklabel and choose proceed, it comes up with a windows titled progress, saying 'newfs /dev/rwd0a' then the errors start happening; the 1st error says 'wd0 interrupt timeout status 59 error 0'. After a few more errors it comes up with a window titled fatal and says 'exec (/stand/newfs) failed, code 9216'. I've tried various alterations with my disklabel set-up etc., but to no avail. Can you help plz... Austin Cagney From owner-freebsd-bugs Sun Mar 26 20:55:04 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA03683 for bugs-outgoing; Sun, 26 Mar 1995 20:55:04 -0800 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 UAA03674 for ; Sun, 26 Mar 1995 20:54:52 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id OAA07747; Mon, 27 Mar 1995 14:51:38 +1000 Date: Mon, 27 Mar 1995 14:51:38 +1000 From: Bruce Evans Message-Id: <199503270451.OAA07747@godzilla.zeta.org.au> To: acs@gate1.internet-eireann.ie, bugs@FreeBSD.org Subject: Re: v2.0 install Sender: bugs-owner@FreeBSD.org Precedence: bulk >I've got an ESDI hard disk. The 1st partiton is 220 mb for DOS, and the >rest, 101 mb, is for FreeBSD. I've booted off the boot_144.flp image and >have done my fdisk work. I then used disklabel to set-up partition 'a' as 76 >mb for '/' and 'b' as 25 mb for 'swap'. So I've made everything as simple as >possible. When I come out of disklabel and choose proceed, it comes up with >a windows titled progress, saying 'newfs /dev/rwd0a' then the errors start >happening; the 1st error says 'wd0 interrupt timeout status 59 error 0'. >After a few more errors it comes up with a window titled fatal and says >'exec (/stand/newfs) failed, code 9216'. The disk apparently has unmarked bad sector. If the disk has any bad sectors, then FreeBSD-2.0 doesn't support it. FreeBSD-2.1 should support it. Bruce From owner-freebsd-bugs Sun Mar 26 22:58:47 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA06154 for bugs-outgoing; Sun, 26 Mar 1995 22:58:47 -0800 Received: from relay.philips.nl (relay.philips.nl [130.144.65.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA06148; Sun, 26 Mar 1995 22:58:44 -0800 Received: from muxgw1.ms.philips.nl ([130.144.90.6]) by relay.philips.nl (8.6.9/8.6.9-950103) with SMTP id IAA14619; Mon, 27 Mar 1995 08:57:16 +0200 Received: by muxgw1.ms.philips.nl (5.57/Ultrix2.4-C) id AA06326; Mon, 27 Mar 95 08:40:11 +0300 Received: by mmra1.ms.philips.nl (4.1/SMI-4.1) id AA06797; Mon, 27 Mar 95 08:55:04 +0200 From: gvrooij@mmra1.ms.philips.nl (Guido van Rooij) Message-Id: <9503270655.AA06797@mmra1.ms.philips.nl> Subject: Re: List of open PRs To: joerg@freefall.cdrom.com (Joerg Wunsch) Date: Mon, 27 Mar 1995 08:55:03 +0200 (MET DST) Cc: freebsd-bugs@freefall.cdrom.com In-Reply-To: <199503251325.OAA22072@freefall.cdrom.com> from "Joerg Wunsch" at Mar 25, 95 02:25:12 pm X-Mailer: ELM [version 2.4 PL21] Content-Type: text Content-Length: 345 Sender: bugs-owner@FreeBSD.org Precedence: bulk > [1994/12/14] bin/55 suspend wedges vipw This has been fixed by Andrew by applying a usenet fix I believe. > [1994/12/21] misc/75 Netboot ignores gateway I believe this was fixed too. Not sure though. > [1995/02/16] kern/219 Performance on local net drops too much when SNDBUF Wasnt this 'solved by discussion'? -Guido From owner-freebsd-bugs Mon Mar 27 03:02:59 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA04671 for bugs-outgoing; Mon, 27 Mar 1995 03:02:59 -0800 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 CAA04580 for ; Mon, 27 Mar 1995 02:59:38 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA12319; Mon, 27 Mar 1995 12:58:49 +0200 Received: by sax.sax.de (8.6.9/8.6.9-s1) with UUCP id MAA25304 for freebsd-bugs@freefall.cdrom.com; Mon, 27 Mar 1995 12:58:49 +0200 Received: by bonnie.tcd-dresden.de (8.6.8/8.6.6) id MAA29633; Mon, 27 Mar 1995 12:46:45 +0200 From: j@narcisa.sax.de (J Wunsch) Message-Id: <199503271046.MAA29633@bonnie.tcd-dresden.de> Subject: Re: List of open PRs To: freebsd-bugs@freefall.cdrom.com Date: Mon, 27 Mar 1995 12:46:44 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de In-Reply-To: <3057.796255613@palmer.demon.co.uk> from "Gary Palmer" at Mar 26, 95 11:06:53 pm X-Phone: +49-351-2012 669 Reply-To: joerg_wunsch@uriah.heep.sax.de X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 347 Sender: bugs-owner@FreeBSD.org Precedence: bulk As Gary Palmer wrote: | | >+ | >+ print MAIL "BEGIN\n"; | ^^^^^END???? :-) Oooooops! Pass me that hat... too much cut'n'paste. -- cheers, J"org private: 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 Mon Mar 27 13:00:09 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA07290 for bugs-outgoing; Mon, 27 Mar 1995 13:00:09 -0800 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA07279; Mon, 27 Mar 1995 13:00:05 -0800 Date: Mon, 27 Mar 1995 13:00:05 -0800 Message-Id: <199503272100.NAA07279@freefall.cdrom.com> From: root@hclb.demon.co.uk Reply-To: root@hclb.demon.co.uk To: freebsd-bugs Subject: bin/274: touch -t with century doesn't work In-Reply-To: Your message of Mon, 27 Mar 95 21:46 BST Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 274 >Category: bin >Synopsis: touch -t with century doesn't work >Confidential: yes >Severity: non-critical >Priority: low >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Mar 27 13:00:02 1995 >Originator: Dave Evans >Organization: >Release: FreeBSD 2.1.0-Development i386 >Environment: >Description: The command: touch -t 199504011200 testfile gives the error message: touch: out of range or illegal time specification: [[CC]YY]MMDDhhmm[.SS] >How-To-Repeat: >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Mon Mar 27 13:06:22 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA07462 for bugs-outgoing; Mon, 27 Mar 1995 13:06:22 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA07455; Mon, 27 Mar 1995 13:06:14 -0800 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id NAA02063; Mon, 27 Mar 1995 13:06:08 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id NAA00368; Mon, 27 Mar 1995 13:06:08 -0800 Message-Id: <199503272106.NAA00368@corbin.Root.COM> X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol To: FreeBSD-gnats@freefall.cdrom.com, freebsd-bugs@freefall.cdrom.com cc: root@freefall.cdrom.com Subject: Re: bin/274: touch -t with century doesn't work In-reply-to: Your message of "Mon, 27 Mar 95 13:00:04 PST." <199503272100.NAA07275@freefall.cdrom.com> From: David Greenman Reply-To: davidg@Root.COM Date: Mon, 27 Mar 1995 13:06:07 -0800 Sender: bugs-owner@FreeBSD.org Precedence: bulk >Thank you very much for your problem report. >It has the internal identification `bin/274'. >The individual assigned to look at your >bug is: freebsd-bugs (FreeBSD bugs mailing list). > >>Category: bin >>Responsible: freebsd-bugs (FreeBSD bugs mailing list) >>Synopsis: touch -t with century doesn't work >>Arrival-Date: Mon Mar 27 13:00:02 1995 Umm, why is 'root' being CC'd? -DG From owner-freebsd-bugs Mon Mar 27 13:08:46 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA07558 for bugs-outgoing; Mon, 27 Mar 1995 13:08:46 -0800 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id NAA07550; Mon, 27 Mar 1995 13:08:43 -0800 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: davidg@Root.COM cc: FreeBSD-gnats@freefall.cdrom.com, freebsd-bugs@freefall.cdrom.com, root@freefall.cdrom.com Subject: Re: bin/274: touch -t with century doesn't work In-reply-to: Your message of "Mon, 27 Mar 95 13:06:07 PST." <199503272106.NAA00368@corbin.Root.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 27 Mar 1995 13:08:42 -0800 Message-ID: <7548.796338522@freefall.cdrom.com> From: Gary Palmer (FreeBSD/ARM Team) Sender: bugs-owner@FreeBSD.org Precedence: bulk In message <199503272106.NAA00368@corbin.Root.COM>, David Greenman writes: > Umm, why is 'root' being CC'd? It wasn't a CC: - it was sent To: root ... I think someone has a screwed up sendmail.cf file (if that is possible). Gary From owner-freebsd-bugs Mon Mar 27 13:10:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA07622 for bugs-outgoing; Mon, 27 Mar 1995 13:10:02 -0800 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 NAA07589; Mon, 27 Mar 1995 13:09:51 -0800 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.8/8.6.6) id NAA15279; Mon, 27 Mar 1995 13:09:26 -0800 From: "Rodney W. Grimes" Message-Id: <199503272109.NAA15279@gndrsh.aac.dev.com> Subject: Re: bin/274: touch -t with century doesn't work To: davidg@Root.COM Date: Mon, 27 Mar 1995 13:09:25 -0800 (PST) Cc: FreeBSD-gnats@freefall.cdrom.com, freebsd-bugs@freefall.cdrom.com, root@freefall.cdrom.com In-Reply-To: <199503272106.NAA00368@corbin.Root.COM> from "David Greenman" at Mar 27, 95 01:06:07 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1036 Sender: bugs-owner@FreeBSD.org Precedence: bulk > > >Thank you very much for your problem report. > >It has the internal identification `bin/274'. > >The individual assigned to look at your > >bug is: freebsd-bugs (FreeBSD bugs mailing list). > > > >>Category: bin > >>Responsible: freebsd-bugs (FreeBSD bugs mailing list) > >>Synopsis: touch -t with century doesn't work > >>Arrival-Date: Mon Mar 27 13:00:02 1995 > > Umm, why is 'root' being CC'd? Probably because someone installed a new sendmail.cf file and did not get it quite right: # class L: names that should be delivered locally, even if we have a relay # class E: names that should be exposed as from this host, even if we masquerade CLroot CEroot I'v changed it to: # class L: names that should be delivered locally, even if we have a relay # class E: names that should be exposed as from this host, even if we masquerade #CLroot CEroot -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-bugs Mon Mar 27 21:05:22 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA24676 for bugs-outgoing; Mon, 27 Mar 1995 21:05:22 -0800 Received: from relay2.UU.NET (relay2.UU.NET [192.48.96.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id VAA24666; Mon, 27 Mar 1995 21:05:18 -0800 Received: from ast.com by relay2.UU.NET with SMTP id QQyiyu04490; Tue, 28 Mar 1995 00:05:13 -0500 Received: from trsvax.fw.ast.com (fw.ast.com) by ast.com with SMTP id AA27696 (5.67b/IDA-1.5 for uunet!freebsd.org!freebsd-current); Mon, 27 Mar 1995 21:09:12 -0800 Received: by trsvax.fw.ast.com (/\=-/\ Smail3.1.18.1 #18.1) id ; Mon, 27 Mar 95 23:04 CST Received: by nemesis.lonestar.org (Smail3.1.27.1 #18) id m0rtTLY-0004vrC; Mon, 27 Mar 95 22:57 CST Message-Id: Date: Mon, 27 Mar 95 22:57 CST To: freebsd-bugs@FreeBSD.org, freebsd-current@FreeBSD.org From: uhclem@nemesis.lonestar.org (Frank Durda IV) Sent: Mon Mar 27 1995, 22:57:40 CST Subject: No declaration for bounds_check_with_label Cc: uhclem@nemesis.lonestar.org Sender: bugs-owner@FreeBSD.org Precedence: bulk Could we locate a nice include file and include: extern int bounds_check_with_label(struct buf *bp, struct disklabel *lp, int wlabel); Several different drivers have to references this and it has no declaration. The function is in machdep.c. Perhaps in devconf.h? Frank Durda IV |"When Windows runs low on memory, or uhclem%nemesis@trsvax.ast.com (Internet)| it gets very unstable." ...letni!rwsys!nemesis!uhclem | - Unnamed Microsoft Windows ...decvax!trsvax.fw.ast.com!nemesis!uhclem | designer, 1992 Really! From owner-freebsd-bugs Mon Mar 27 21:12:04 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA24930 for bugs-outgoing; Mon, 27 Mar 1995 21:12:04 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id VAA24923; Mon, 27 Mar 1995 21:11:55 -0800 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id VAA03007; Mon, 27 Mar 1995 21:11:50 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id VAA00602; Mon, 27 Mar 1995 21:11:50 -0800 Message-Id: <199503280511.VAA00602@corbin.Root.COM> X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol To: uhclem@nemesis.lonestar.org (Frank Durda IV) cc: freebsd-bugs@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: No declaration for bounds_check_with_label In-reply-to: Your message of "Mon, 27 Mar 95 22:57:00 CST." From: David Greenman Reply-To: davidg@Root.COM Date: Mon, 27 Mar 1995 21:11:49 -0800 Sender: bugs-owner@FreeBSD.org Precedence: bulk >Could we locate a nice include file and include: > >extern int bounds_check_with_label(struct buf *bp, struct disklabel *lp, > int wlabel); > >Several different drivers have to references this and it has no >declaration. The function is in machdep.c. It's declaration is in sys/disklabel.h. -DG From owner-freebsd-bugs Mon Mar 27 23:19:48 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA29754 for bugs-outgoing; Mon, 27 Mar 1995 23:19:48 -0800 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 XAA29726; Mon, 27 Mar 1995 23:19:14 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id RAA13866; Tue, 28 Mar 1995 17:14:53 +1000 Date: Tue, 28 Mar 1995 17:14:53 +1000 From: Bruce Evans Message-Id: <199503280714.RAA13866@godzilla.zeta.org.au> To: freebsd-bugs@FreeBSD.org, freebsd-current@FreeBSD.org, uhclem@nemesis.lonestar.org Subject: Re: No declaration for bounds_check_with_label Sender: bugs-owner@FreeBSD.org Precedence: bulk >Could we locate a nice include file and include: >extern int bounds_check_with_label(struct buf *bp, struct disklabel *lp, > int wlabel); >Several different drivers have to references this and it has no >declaration. The function is in machdep.c. It is declared in (since revision 1.11 1995/03/16), but will go away. Please update your driver(s) to use disk slices (dscheck()) so that bounds_check_with_label() can go away ASAP. See recent changes to sd.c. for examples. Unsliced unlabeled read-only disks are simpler to handle. dsopen() will eventually have a `struct diskgeom' arg (the struct will be something like `struct disk_parms' in sd.c) so that a dummy label doesn't have to be created in 1001 different cdrom drivers. The disk slice module also handles all for the DIOC* ioctls so that drivers don't have to and correctly tracks open partitions. Most scsi and cd drivers incorrectly track open partitions. Some of them incorrectly declare their close function so they don't even know about the `fmt' arg which is required for distinguishing closes of the cdev from closes of the bdev. Bruce From owner-freebsd-bugs Tue Mar 28 10:50:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA23824 for bugs-outgoing; Tue, 28 Mar 1995 10:50:02 -0800 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA23817; Tue, 28 Mar 1995 10:50:01 -0800 Date: Tue, 28 Mar 1995 10:50:01 -0800 Message-Id: <199503281850.KAA23817@freefall.cdrom.com> From: Michael Gerhards Reply-To: Michael Gerhards To: freebsd-bugs Subject: kern/275: FreeBSD 2.0R and QIC-02 streamer In-Reply-To: Your message of Tue, 28 Mar 1995 18:02:58 +0200 <199503281602.SAA12494@nina.jester.gun.de> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 275 >Category: kern >Synopsis: qic-02 streamer won't work >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: Tue Mar 28 10:50:00 1995 >Originator: Michael Gerhards >Organization: private >Release: FreeBSD 2.0-RELEASE i386 >Environment: 486DX40, 8 MB, Adaptec 1542B, three SCSI-disks, CDROM Archive SC499 with SC402 controller ( qic-02 ) >Description: I get 'unrecoverable errors' when using tar with /dev/rwt0. The kernel is configured correctly; the streamer is found during startup. >How-To-Repeat: every command which uses the streamer. 'mt' won't use the streamer ( unknown tape ) tar gives me 'unrecoverable' errors or 'input/ourput-errors'. The drive is detected and tar sees if it is write-protected. tar tvf /dev/rwt0 >Fix: I would be happy, if you could make the streamer work :-) >Audit-Trail: >Unformatted: From owner-freebsd-bugs Tue Mar 28 14:44:12 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA00170 for bugs-outgoing; Tue, 28 Mar 1995 14:44:12 -0800 Received: from mail.bw.lgca.ohio.gov (mail.bw.lgca.ohio.gov [156.63.242.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA00163 for ; Tue, 28 Mar 1995 14:44:10 -0800 Received: from localhost (ram@localhost) by mail.bw.lgca.ohio.gov (8.3/8.3) id RAA26144; Tue, 28 Mar 1995 17:59:57 -0500 From: Ronald Matuszak Message-Id: <199503282259.RAA26144@mail.bw.lgca.ohio.gov> Subject: HELP--please :-( To: bugs@FreeBSD.org Date: Tue, 28 Mar 1995 17:59:56 -0500 (EST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1325 Sender: bugs-owner@FreeBSD.org Precedence: bulk I am currently running FreeBSD 1.0.2 on a old 486 (junk) clone and have impressed my school board enough to have them buy the FreeBSD 2.0 CD and a pentium 90 (geniune intel motherboard) 32 megs RAM, Buslogic-946C Fast SCSI PCI card, Seagate 1 gig drive, wangtec DAT drive, and NEC SSCI CD rom. The boot floopy did not even bring me to the install screen. I downloaded the new boot file from ftp.cdrom.com (dated March 24) Now the boot disk makes it to the install screen but does not list any drives on the screen where you decide partition sizes. Durring the boot process one of the last lines read this: pci0:3: vendor=0x104b, device=ox104, class=storage [not supported} map(10): io(d000) does this mean that the controller card is the problem. Durring the boot process it saw and identified the scsi hard drive and dat drive and cd rom. We have no IDE drives on this system. I saw the 946c scsi card on your list of supported controlers. I believe the firmware on the card is 4.25j Please advise.... The old (1.0.2 system) was a breeze. I REALLY REALLY LIKE YOUR SOFTWARE!! I AM NOT BITCHING...... JUST TRYING TO JUSTIFY OUR RECENT 5K PURCHASE OF NEW HARDWARE. THANKS IN ADVANCE :-) Ron Matuszak Network systems admin Beachwood City schools (216) 292-2350 ram@mail.bw.lgca.ohio.gov CUL8TER From owner-freebsd-bugs Tue Mar 28 14:51:28 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA00283 for bugs-outgoing; Tue, 28 Mar 1995 14:51:28 -0800 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id OAA00273; Tue, 28 Mar 1995 14:51:27 -0800 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: Ronald Matuszak cc: bugs@FreeBSD.org Subject: Re: HELP--please :-( In-reply-to: Your message of "Tue, 28 Mar 95 17:59:56 EST." <199503282259.RAA26144@mail.bw.lgca.ohio.gov> Date: Tue, 28 Mar 1995 14:51:26 -0800 Message-ID: <272.796431086@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: bugs-owner@FreeBSD.org Precedence: bulk > I am currently running FreeBSD 1.0.2 on a old 486 (junk) clone and > have impressed my school board enough to have them buy the FreeBSD 2.0 > CD and a pentium 90 (geniune intel motherboard) 32 megs RAM, > Buslogic-946C Fast SCSI PCI card, Seagate 1 gig drive, wangtec DAT drive, and Nice! > The boot floopy did not even bring me to the install screen. > I downloaded the new boot file from ftp.cdrom.com (dated March 24) !!! Can you tell us a little more about what happened? I know of a number of people using such configurations with little or no trouble (myself included!). Unless the Bt946 is misconfigured, it should have been recognised by the 2.0 boot disk, to say nothing of the later one. > does this mean that the controller card is the problem. Durring the boot pro >cess it saw and identified the scsi hard drive and dat drive and cd rom. Please send us your boot message output, particularly as it relates to the bt0 device. I strongly suspect a simple misconfiguration problem that, once rectified, will allow your machine to come up with flying colors. Jordan From owner-freebsd-bugs Tue Mar 28 15:00:30 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA00389 for bugs-outgoing; Tue, 28 Mar 1995 15:00:30 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA00383 for ; Tue, 28 Mar 1995 15:00:28 -0800 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id PAA05189; Tue, 28 Mar 1995 15:00:18 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id PAA00566; Tue, 28 Mar 1995 15:00:17 -0800 Message-Id: <199503282300.PAA00566@corbin.Root.COM> X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol To: Ronald Matuszak cc: bugs@FreeBSD.org Subject: Re: HELP--please :-( In-reply-to: Your message of "Tue, 28 Mar 95 17:59:56 EST." <199503282259.RAA26144@mail.bw.lgca.ohio.gov> From: David Greenman Reply-To: davidg@Root.COM Date: Tue, 28 Mar 1995 15:00:16 -0800 Sender: bugs-owner@FreeBSD.org Precedence: bulk >I am currently running FreeBSD 1.0.2 on a old 486 (junk) clone and >have impressed my school board enough to have them buy the FreeBSD 2.0 >CD and a pentium 90 (geniune intel motherboard) 32 megs RAM, >Buslogic-946C Fast SCSI PCI card, Seagate 1 gig drive, wangtec DAT drive, and >NEC SSCI CD rom. > >The boot floopy did not even bring me to the install screen. >I downloaded the new boot file from ftp.cdrom.com (dated March 24) > >Now the boot disk makes it to the install screen but does not list any >drives on the screen where you decide partition sizes. >Durring the boot process one of the last lines read this: > >pci0:3: vendor=0x104b, device=ox104, class=storage [not supported} >map(10): io(d000) My guess would be that the 946c isn't set to 0x330 (or is that 0x334...I don't recall). I know the card I have is set to 0x334 and that I had to change the kernel to match (I recall not being able to set it to 0x330 for some reason). Anyway, I think your problem is with the I/O address of the card and the kernel not matching. If you know how the card is set, you can use the '-c' option at boot time to enter 'userconfig' to change it in the kernel ('help' should give a hint at what to do). -DG From owner-freebsd-bugs Tue Mar 28 18:20:01 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA02667 for bugs-outgoing; Tue, 28 Mar 1995 18:20:01 -0800 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA02660; Tue, 28 Mar 1995 18:20:01 -0800 Date: Tue, 28 Mar 1995 18:20:01 -0800 Message-Id: <199503290220.SAA02660@freefall.cdrom.com> From: Paul Traina Reply-To: Paul Traina To: freebsd-bugs Subject: misc/276: rc.maint clears /var/run directory after syslogd has started In-Reply-To: Your message of Tue, 28 Mar 1995 18:16:14 -0800 <199503290216.SAA00440@precipice.shockwave.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 276 >Category: misc >Synopsis: rc.maint hoses over syslogd by clearing /var/run >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 Mar 28 18:20:00 1995 >Originator: Paul Traina >Organization: >Release: FreeBSD 2.1.0-Development i386 >Environment: FreeBSD current rc files as of last night (3/27/95) >Description: /etc/rc executes netstart via syslogd /etc/rc.maint then blows away the utmp file as it clears things up. >How-To-Repeat: Boot system, watch syslogd complain >Fix: Move the cleanup of /var/run ahead of starting syslogd. I'd suggest simply executing rc.maint before executing netstart, but I have not tested this in an NFS configuration. You may need to mount /var first (sigh). >Audit-Trail: >Unformatted: From owner-freebsd-bugs Tue Mar 28 18:30:01 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA02836 for bugs-outgoing; Tue, 28 Mar 1995 18:30:01 -0800 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA02829; Tue, 28 Mar 1995 18:30:00 -0800 Date: Tue, 28 Mar 1995 18:30:00 -0800 Message-Id: <199503290230.SAA02829@freefall.cdrom.com> From: Paul Traina Reply-To: Paul Traina To: freebsd-bugs Subject: kern/277: netstat -r reports entries with negative expire times In-Reply-To: Your message of Tue, 28 Mar 1995 18:20:59 -0800 <199503290220.SAA00574@precipice.shockwave.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 277 >Category: kern >Synopsis: netstat -r reports entries with negative expire times >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: Tue Mar 28 18:30:00 1995 >Originator: Paul Traina >Organization: >Release: FreeBSD 2.1.0-Development i386 >Environment: FreeBSD 2.1.0-current as of 3/27/95 >Description: Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 171.69.108.38 UGSc 7 1 ed0 127.0.0.1 127.0.0.1 UH 0 70 lo0 171.69.108.32 link#1 UC 0 0 ed0 -1279 171.69.108.33 0:0:c0:93:88:53 UHLW 2 246 lo0 171.69.108.38 0:0:c:2:f4:74 UHLW 8 4 ed0 1145 224 link#1 UCS 0 0 ed0 -1279 >How-To-Repeat: % netstat -rn >Fix: In the routing table, clonable master entries should probably never have an expire time set or displayed. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Tue Mar 28 18:40:03 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA03049 for bugs-outgoing; Tue, 28 Mar 1995 18:40:03 -0800 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA03041; Tue, 28 Mar 1995 18:40:01 -0800 Date: Tue, 28 Mar 1995 18:40:01 -0800 Message-Id: <199503290240.SAA03041@freefall.cdrom.com> From: Paul Traina Reply-To: Paul Traina To: freebsd-bugs Subject: misc/278: text formatting of syscons startup is nonstandard In-Reply-To: Your message of Tue, 28 Mar 1995 18:36:45 -0800 <199503290236.SAA00413@precipice.shockwave.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 278 >Category: misc >Synopsis: the echos in /etc/rc to start syscons have a couple of mistakes >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: Tue Mar 28 18:40:01 1995 >Originator: Paul Traina >Organization: >Release: FreeBSD 2.1.0-Development i386 >Environment: FreeBSD 2.1.0-current as of 3/27/95 >Description: If you enable some of the syscons options, in my case, all I did was load a new keyboard map to change the backspace key to generate delete (death to backspace...grrr), the echos are kinda all over the place. It looks like a couple of -n's got overlooked. >How-To-Repeat: Define a keyboard map and reboot. >Fix: *** rc Sun Mar 26 13:03:04 1995 --- rc Tue Mar 28 18:28:08 1995 *************** *** 127,133 **** [ "X${kbdadjust}" != X"NO" -o "X${vidadjust}" != X"NO" -o \ "X${saver}" != X"NO" ] && echo "starting syscons:" ! [ "X${kbdadjust}" != X"NO" ] && echo "kbdcontrol: " # keymap if [ "X${keymap}" != X"NO" ]; then --- 127,133 ---- [ "X${kbdadjust}" != X"NO" -o "X${vidadjust}" != X"NO" -o \ "X${saver}" != X"NO" ] && echo "starting syscons:" ! [ "X${kbdadjust}" != X"NO" ] && echo -n "kbdcontrol: " # keymap if [ "X${keymap}" != X"NO" ]; then *************** *** 142,148 **** fi [ "X${kbdadjust}" != X"NO" ] && echo ! [ "X${vidadjust}" != X"NO" ] && echo "vidcontrol: " # screen mapping if [ "X${scrnmap}" != X"NO" ]; then --- 142,148 ---- fi [ "X${kbdadjust}" != X"NO" ] && echo ! [ "X${vidadjust}" != X"NO" ] && echo -n "vidcontrol: " # screen mapping if [ "X${scrnmap}" != X"NO" ]; then >Audit-Trail: >Unformatted: From owner-freebsd-bugs Tue Mar 28 18:50:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA03332 for bugs-outgoing; Tue, 28 Mar 1995 18:50:02 -0800 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA03325; Tue, 28 Mar 1995 18:50:01 -0800 Date: Tue, 28 Mar 1995 18:50:01 -0800 Message-Id: <199503290250.SAA03325@freefall.cdrom.com> From: Paul Traina Reply-To: Paul Traina To: freebsd-bugs Subject: misc/279: remove non-bsdish echo in rc.maint In-Reply-To: Your message of Tue, 28 Mar 1995 18:39:53 -0800 <199503290239.SAA00521@precipice.shockwave.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 279 >Category: misc >Synopsis: lose the '** Begin system maintenance tasks **' message >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: Tue Mar 28 18:50:01 1995 >Originator: Paul Traina >Organization: >Release: FreeBSD 2.1.0-Development i386 >Environment: FreeBSD 2.1.0 as of last night >Description: echo '** Begin system maintainance tasks **' is gratuitous. Given all of the crap currently being echoed to the screen at startup, why do we need yet another line that can scroll useful information off the top of the screen. I'm sure it was useful when you were debugging the rc* stuff, but now it's just annoying. >How-To-Repeat: Boot system >Fix: *** rc.maint Thu Mar 23 19:03:34 1995 --- /etc/rc.maint Tue Mar 28 18:16:34 1995 *************** *** 4,11 **** # Various maintainance tasks to be done as the system is coming up - echo '** Begin system maintainance tasks **' - # /var/crash should be a directory or a symbolic link # to the crash directory if core dumps are to be saved. if [ "X${savecore}" = X"YES" -a -d /var/crash ]; then --- 4,9 ---- >Audit-Trail: >Unformatted: From owner-freebsd-bugs Tue Mar 28 19:00:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA03459 for bugs-outgoing; Tue, 28 Mar 1995 19:00:02 -0800 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA03452; Tue, 28 Mar 1995 19:00:02 -0800 Date: Tue, 28 Mar 1995 19:00:02 -0800 Message-Id: <199503290300.TAA03452@freefall.cdrom.com> From: Paul Traina Reply-To: Paul Traina To: freebsd-bugs Subject: kern/280: new slice manager totally confused about old slice disks In-Reply-To: Your message of Tue, 28 Mar 1995 18:52:58 -0800 <199503290252.SAA00683@precipice.shockwave.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 280 >Category: kern >Synopsis: the new slice code is bitching about my old slices >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 Mar 28 19:00:00 1995 >Originator: Paul Traina >Organization: >Release: FreeBSD 2.1.0-Development i386 >Environment: FreeBSD 2.1.0 as of yesterday. A pair of SCSI drives: sd0 has both DOS and FreeBSD partitions on it sd1 has DOS partitions on it >Description: 1) It looks like the implicit label stuff for unlabeled disks is non-functional? I cannot ask disklable to read the pseudo-label off of sd1 root@precipice$ disklabel sd1 disklabel: ioctl DIOCGDINFO: Invalid argument 2) All of this slice stuff is really verbose and I think gratuitous. Note: I am using older boot blocks that don't support -v, so it may be that the system assumes old boot blocks generate -v, if so, I think that is backwards and yet another bug, but WTF. If the slice manager was working well, I would use disklable to write new boot blocks and test it, but since I can't access my MSDOS partition on sd0 via FreeBSD anymore, I'm concerned that disklabel is going to lose that information if I write out new boot blocks (I gotta go read the source code again, it's been a while since I looked at what disklabel -B does and doesn't do.) 2) When the system is booting, it whines loudly about partitions not being inside slices... this may indeed be an error condition, but that's the way FreeBSD 2.0 did things, so you're going to have a hell of a support problem with these new slice changes. FreeBSD 2.1.0-Development #0: Tue Mar 28 12:17:28 PST 1995 pst@precipice.Shockwave.COM:/usr/src/sys/compile/PRECIPICE CPU: Pentium (Pentium-class CPU) 60 MHz Origin = "GenuineIntel" Id = 0x515 This is a Pentium 510\\60 or 567\\66 Stepping=5 Features=0x1bf FPU VME PSE MCE CX8 real memory = 16384000 (4000 pages) avail memory = 15093760 (3685 pages) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x280-0x29f irq 9 maddr 0xd8000 msize 8192 on isa ed0: address 00:00:c0:93:88:53, type WD8013EPC (8 bit) bpf: ed0 attached sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16450 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 765 fd0: 1.44MB 3.5in bt0: Bt445S/ 0-PCI/EISA/VLB(32bit) bus bt0: reading board settings, dma=5, int=11 bt0: version 3.37, fast sync, no parity, 32 mbxs, 32 ccbs bt0: targ 0 sync rate=10.00MB/s(100ns), offset=15 bt0: targ 1 sync rate= 4.54MB/s(220ns), offset=15 bt0: targ 4 async bt0: targ 6 async bt0: Enabling Round robin scheme bt0 at 0x330 irq 11 drq 5 on isa (bt0:0:0): "QUANTUM PD1800S 3161" is a type 0 fixed SCSI 2 sd0(bt0:0:0): Direct-Access 1717MB (3517856 512 byte sectors) (bt0:1:0): "MAXTOR P0-12S JB22" is a type 0 fixed SCSI 1 sd1(bt0:1:0): Direct-Access 997MB (2042265 512 byte sectors) (bt0:4:0): "NEC CD-ROM DRIVE:210 1.0" is a type 5 removable SCSI 1 cd0(bt0:4:0): CD-ROM cd0(bt0:4:0): NOT READY csi:20,b,0,0 asc:b,0 cd0: could not get size drive empty (bt0:6:0): "WANGTEK 5150ES SCSI FA14 08" is a type 1 removable SCSI 1 st0(bt0:6:0): Sequential-Access drive offline npx0 on motherboard npx0: INT 16 interface gus0 at 0x220 irq 12 drq 1 on isa gus0: sd0s1: start 32, end = 511999, size 511968: OK sd0s4: start 512000, end = 3514367, size 3002368: OK sd0: rejecting partition in BSD label: it isn't entirely within the slice sd0: start 512000, end 3514367, size 3002368 sd0d: start 0, end 3514367, size 3514368 sd0: rejecting partition in BSD label: it isn't entirely within the slice sd0h: start 32, end 511999, size 511968 sd1s1: start 32, end = 819199, size 819168: OK sd1s2: start 819200, end = 2041855, size 1222656: OK sd1s5: start 819232, end = 2041855, size 1222624: OK sd0s1: start 32, end = 511999, size 511968: OK sd0s4: start 512000, end = 3514367, size 3002368: OK sd0: rejecting partition in BSD label: it isn't entirely within the slice sd0: start 512000, end 3514367, size 3002368 sd0d: start 0, end 3514367, size 3514368 sd0: rejecting partition in BSD label: it isn't entirely within the slice sd0h: start 32, end 511999, size 511968 bpf: lo0 attached bpf: tun0 attached sd0s1: start 32, end = 511999, size 511968: OK sd0s4: start 512000, end = 3514367, size 3002368: OK sd0: rejecting partition in BSD label: it isn't entirely within the slice sd0: start 512000, end 3514367, size 3002368 sd0d: start 0, end 3514367, size 3514368 sd0: rejecting partition in BSD label: it isn't entirely within the slice sd0h: start 32, end 511999, size 511968 sd1s1: start 32, end = 819199, size 819168: OK sd1s2: start 819200, end = 2041855, size 1222656: OK sd1s5: start 819232, end = 2041855, size 1222624: OK 3) Oh where oh where has my MSDOS partition gone? Oh where oh where can it beeeeee? pst@precipice$ cat /etc/fstab /dev/sd0a / ufs rw 1 1 /dev/sd0e /usr ufs rw 1 2 /dev/sd0b none swap sw /dev/sd0h /dos msdos rw proc /proc procfs rw root@precipice$ mount /dos msdos: mount: Invalid argument pst@precipice$ disklabel sd0 # /dev/rsd0c: type: SCSI disk: quantum_pd1800s label: flags: bytes/sector: 512 sectors/track: 32 tracks/cylinder: 128 sectors/cylinder: 4096 cylinders: 733 sectors/unit: 3002368 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 36864 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 8) b: 131072 36864 swap # (Cyl. 9 - 40) c: 3002368 0 unused 0 0 # (Cyl. 0 - 732) e: 2834432 167936 4.2BSD 1024 8192 16 # (Cyl. 41 - 732) >How-To-Repeat: Boot system on a machine that has both DOS and FreeBSD partitions that was built from FreeBSD 2.0's install procedure with the new kernel. >Fix: Hell if I know. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Tue Mar 28 19:23:27 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA04112 for bugs-outgoing; Tue, 28 Mar 1995 19:23:27 -0800 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id TAA04105; Tue, 28 Mar 1995 19:23:25 -0800 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: Paul Traina cc: freebsd-bugs@freefall.cdrom.com Subject: Re: kern/280: new slice manager totally confused about old slice disks In-reply-to: Your message of "Tue, 28 Mar 95 19:00:02 PST." <199503290300.TAA03452@freefall.cdrom.com> Date: Tue, 28 Mar 1995 19:23:25 -0800 Message-ID: <4104.796447405@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: bugs-owner@FreeBSD.org Precedence: bulk > 1) It looks like the implicit label stuff for unlabeled disks is > non-functional? I cannot ask disklable to read the pseudo-label off > of sd1 Maybe if you specify /dev/sd0d explicitly? Works for me! > 2) All of this slice stuff is really verbose and I think gratuitous. > Note: I am using older boot blocks that don't support -v, so it Agreed! > 2) When the system is booting, it whines loudly about partitions not being > inside slices... this may indeed be an error condition, but that's the > way FreeBSD 2.0 did things, so you're going to have a hell of a support > problem with these new slice changes. Agreed again. We're going to need to deal with this somehow, or users are going to SCREECH. Bruce is safe over there in OZ, but I know that folks like Poul and I are going to get hundreds of mails in our boxes! :-( > 3) Oh where oh where has my MSDOS partition gone? Oh where oh where > can it beeeeee? Try copying the new MAKEDEV over and doing a ./MAKEDEV sd0, then try: mount -t msdos /dev/sd0s1 /dos Assuming, of course, that slice 1 is the DOS partition. This is actually a very GOOD part of the change and I'm happy that we have it. It will make auto-detecting and mounting the DOS partition from the install much easier (I can just look to see what partition is a DOS partition and then mount the corresponding slice). Jordan From owner-freebsd-bugs Tue Mar 28 19:31:08 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA04474 for bugs-outgoing; Tue, 28 Mar 1995 19:31:08 -0800 Received: (from jkh@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA04459; Tue, 28 Mar 1995 19:31:06 -0800 Date: Tue, 28 Mar 1995 19:31:06 -0800 From: "Jordan K. Hubbard" Message-Id: <199503290331.TAA04459@freefall.cdrom.com> To: pst@Shockwave.COM, jkh, freebsd-bugs Subject: Changed information for PR misc/279 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: lose the '** Begin system maintenance tasks **' message State-Changed-From-To: open-closed State-Changed-By: jkh State-Changed-When: Tue Mar 28 19:30:47 PST 1995 State-Changed-Why: Addressed the problem. From owner-freebsd-bugs Tue Mar 28 19:35:35 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA04921 for bugs-outgoing; Tue, 28 Mar 1995 19:35:35 -0800 Received: (from jkh@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA04904; Tue, 28 Mar 1995 19:35:33 -0800 Date: Tue, 28 Mar 1995 19:35:33 -0800 From: "Jordan K. Hubbard" Message-Id: <199503290335.TAA04904@freefall.cdrom.com> To: pst@Shockwave.COM, jkh, freebsd-bugs Subject: Changed information for PR misc/278 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: the echos in /etc/rc to start syscons have a couple of mistakes State-Changed-From-To: open-closed State-Changed-By: jkh State-Changed-When: Tue Mar 28 19:35:18 PST 1995 State-Changed-Why: Problem addressed. From owner-freebsd-bugs Tue Mar 28 19:36:36 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA04979 for bugs-outgoing; Tue, 28 Mar 1995 19:36:36 -0800 Received: from host.yab.com (host.yab.com [204.94.255.4]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA04973 for ; Tue, 28 Mar 1995 19:36:34 -0800 From: bamfordd@host.yab.com Received: (from bamfordd@localhost) by host.yab.com (8.6.9/8.6.9) id UAA09921 for bugs@freebsd.org; Tue, 28 Mar 1995 20:35:04 -0700 Date: Tue, 28 Mar 1995 20:35:04 -0700 Message-Id: <199503290335.UAA09921@host.yab.com> To: bugs@FreeBSD.org Subject: Building a new kernel on a 486 Sender: bugs-owner@FreeBSD.org Precedence: bulk Hi, it's me again. I've got the machine to run, and I've loaded the bindist and the srcdist. However, every time I boot, I have to give the -c option so I can switch off pas0, which gives a panic if probed. So I would like to build a new kernel; at least leaving out the pas0 probe. So I bought the BOOK. Yes, O'Reilly's SMM. I've read the chapter a few times, only once is the 486 mentioned. I read that there should be a /sys, and if there isn't, then the source should be linked to /sys. So I linked /sys to /usr/src (if I remember); that didn't work, although it said that it was creating a new kernel, I never found it. Then I started from scratch again, repartitioning and install. I copied /usr/src/sys/i386/conf/GENERIC to /usr/src/sys/i386/conf/derek, took out the pas0 entry, and tried it again - config derek, cd ../../compile/derek, make depend, make kernel. Again there were lots of links missing, and it didn't compile. Now, I'd hate to think what a novice would do with the software. There are no hints anywhere as to what to do, how to do it, etc. I've been SA on a Unisys 5000/90 for the last 7 years, and life was a lot easier. Can anyone help, or send me a README or something? Please derek j bamford .\ From owner-freebsd-bugs Tue Mar 28 19:43:25 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA05447 for bugs-outgoing; Tue, 28 Mar 1995 19:43:25 -0800 Received: (from jkh@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA05427; Tue, 28 Mar 1995 19:43:21 -0800 Date: Tue, 28 Mar 1995 19:43:21 -0800 From: "Jordan K. Hubbard" Message-Id: <199503290343.TAA05427@freefall.cdrom.com> To: pst@Shockwave.COM, jkh, freebsd-bugs Subject: Changed information for PR misc/276 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: rc.maint hoses over syslogd by clearing /var/run State-Changed-From-To: open-closed State-Changed-By: jkh State-Changed-When: Tue Mar 28 19:42:35 PST 1995 State-Changed-Why: suggestion to move rc.maint ahead of netstart adopted. From owner-freebsd-bugs Tue Mar 28 20:09:21 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA10104 for bugs-outgoing; Tue, 28 Mar 1995 20:09:21 -0800 Received: from dtr.com (dtr.rain.com [204.119.8.19]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id UAA09995 for ; Tue, 28 Mar 1995 20:09:13 -0800 From: bmk@dtr.com Received: (from bmk@localhost) by dtr.com (8.6.11/8.6.9) id UAA12714; Tue, 28 Mar 1995 20:03:35 -0800 Message-Id: <199503290403.UAA12714@dtr.com> Subject: Re: kern/280: new slice manager totally confused about old slice disks To: pst@Shockwave.COM Date: Tue, 28 Mar 1995 20:03:35 -0800 (PST) Cc: bugs@FreeBSD.org In-Reply-To: <199503290300.TAA03452@freefall.cdrom.com> from "Paul Traina" at Mar 28, 95 07:00:02 pm Reply-To: bmk@dtr.com X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 191 Sender: bugs-owner@FreeBSD.org Precedence: bulk > >Synopsis: the new slice code is bitching about my old slices > FreeBSD 2.1.0 as of yesterday. I saw this with yesterday's FreeBSD-current kernel as well. SNAP-0322 works fine. From owner-freebsd-bugs Tue Mar 28 21:21:54 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA21566 for bugs-outgoing; Tue, 28 Mar 1995 21:21:54 -0800 Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id VAA21558; Tue, 28 Mar 1995 21:21:53 -0800 Received: from localhost (localhost [127.0.0.1]) by precipice.shockwave.com (8.6.11/8.6.9) with SMTP id VAA01004; Tue, 28 Mar 1995 21:21:15 -0800 Message-Id: <199503290521.VAA01004@precipice.shockwave.com> To: "Jordan K. Hubbard" cc: freebsd-bugs@freefall.cdrom.com Subject: Re: kern/280: new slice manager totally confused about old slice disks In-reply-to: Your message of "Tue, 28 Mar 1995 19:23:25 PST." <4104.796447405@freefall.cdrom.com> Date: Tue, 28 Mar 1995 21:21:15 -0800 From: Paul Traina Sender: bugs-owner@FreeBSD.org Precedence: bulk From: "Jordan K. Hubbard" Subject: Re: kern/280: new slice manager totally confused about old slice dis >>ks > 1) It looks like the implicit label stuff for unlabeled disks is > non-functional? I cannot ask disklable to read the pseudo-label off > of sd1 Maybe if you specify /dev/sd0d explicitly? Works for me! root@precipice$ disklabel /dev/sd1d disklabel: /dev/sd1d: Invalid argument root@precipice$ disklabel sd1 disklabel: ioctl DIOCGDINFO: Invalid argument However, I was very wrong about the disk never having a label. It used to be my old root drive, and I think a FreeBSD 1.1 label might still exist having not been overwritten, even though the entire disk is now a DOS drive... this leads me to wonder... sd1s1: start 32, end = 819199, size 819168: OK sd1s2: start 819200, end = 2041855, size 1222656: OK sd1s5: start 819232, end = 2041855, size 1222624: OK > 2) All of this slice stuff is really verbose and I think gratuitous. > Note: I am using older boot blocks that don't support -v, so it Agreed! > 2) When the system is booting, it whines loudly about partitions not being > inside slices... this may indeed be an error condition, but that's the > way FreeBSD 2.0 did things, so you're going to have a hell of a support > problem with these new slice changes. Agreed again. We're going to need to deal with this somehow, or users are going to SCREECH. Bruce is safe over there in OZ, but I know that folks like Poul and I are going to get hundreds of mails in our boxes! :-( > 3) Oh where oh where has my MSDOS partition gone? Oh where oh where > can it beeeeee? Try copying the new MAKEDEV over and doing a ./MAKEDEV sd0, then try: mount -t msdos /dev/sd0s1 /dos Assuming, of course, that slice 1 is the DOS partition. This is actually a very GOOD part of the change and I'm happy that we have it. It will make auto-detecting and mounting the DOS partition from the install much easier (I can just look to see what partition is a DOS partition and then mount the corresponding slice). I'm a little fuzzy on something, what is a slice vs a partition? Is a slice one of the one of four (recursive) classic DOS partitions or is a slice a UNIX disklabel partition? From owner-freebsd-bugs Tue Mar 28 21:25:48 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA21697 for bugs-outgoing; Tue, 28 Mar 1995 21:25:48 -0800 Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id VAA21691; Tue, 28 Mar 1995 21:25:46 -0800 Received: from localhost (localhost [127.0.0.1]) by precipice.shockwave.com (8.6.11/8.6.9) with SMTP id VAA01190; Tue, 28 Mar 1995 21:25:09 -0800 Message-Id: <199503290525.VAA01190@precipice.shockwave.com> To: "Jordan K. Hubbard" cc: freebsd-bugs@freefall.cdrom.com Subject: Re: kern/280: new slice manager totally confused about old slice disks In-reply-to: Your message of "Tue, 28 Mar 1995 19:23:25 PST." <4104.796447405@freefall.cdrom.com> Date: Tue, 28 Mar 1995 21:25:09 -0800 From: Paul Traina Sender: bugs-owner@FreeBSD.org Precedence: bulk > 3) Oh where oh where has my MSDOS partition gone? Oh where oh where > can it beeeeee? Try copying the new MAKEDEV over and doing a ./MAKEDEV sd0, then try: mount -t msdos /dev/sd0s1 /dos Assuming, of course, that slice 1 is the DOS partition. This is actually a very GOOD part of the change and I'm happy that we have it. It will make auto-detecting and mounting the DOS partition from the install much easier (I can just look to see what partition is a DOS partition and then mount the corresponding slice). Aha, ok, this worked for me, I now understand a lot more about the slice scheme (took only 30 seconds wall clock time and 1 second CPU time). I would suggest documenting the living hell out of this. The gratuitous kernel printfs when accessing the label are a bit much, do they only happen when booting in verbose mode? sd0s1: start 32, end = 511999, size 511968: OK sd0s4: start 512000, end = 3514367, size 3002368: OK sd0: rejecting partition in BSD label: it isn't entirely within the slice sd0: start 512000, end 3514367, size 3002368 sd0d: start 0, end 3514367, size 3514368 sd0: rejecting partition in BSD label: it isn't entirely within the slice sd0h: start 32, end 511999, size 511968 sd1s1: start 32, end = 819199, size 819168: OK sd1s2: start 819200, end = 2041855, size 1222656: OK sd1s5: start 819232, end = 2041855, size 1222624: OK sd0s1: start 32, end = 511999, size 511968: OK sd0s4: start 512000, end = 3514367, size 3002368: OK sd0: rejecting partition in BSD label: it isn't entirely within the slice sd0: start 512000, end 3514367, size 3002368 sd0d: start 0, end 3514367, size 3514368 sd0: rejecting partition in BSD label: it isn't entirely within the slice sd0h: start 32, end 511999, size 511968 bpf: lo0 attached bpf: tun0 attached sd0s1: start 32, end = 511999, size 511968: OK sd0s4: start 512000, end = 3514367, size 3002368: OK sd0: rejecting partition in BSD label: it isn't entirely within the slice sd0: start 512000, end 3514367, size 3002368 sd0d: start 0, end 3514367, size 3514368 sd0: rejecting partition in BSD label: it isn't entirely within the slice sd0h: start 32, end 511999, size 511968 sd1s1: start 32, end = 819199, size 819168: OK sd1s2: start 819200, end = 2041855, size 1222656: OK sd1s5: start 819232, end = 2041855, size 1222624: OK sd1s1: start 32, end = 819199, size 819168: OK sd1s2: start 819200, end = 2041855, size 1222656: OK sd1s5: start 819232, end = 2041855, size 1222624: OK sd1s1: start 32, end = 819199, size 819168: OK sd1s2: start 819200, end = 2041855, size 1222656: OK sd1s5: start 819232, end = 2041855, size 1222624: OK sd1s1: start 32, end = 819199, size 819168: OK sd1s2: start 819200, end = 2041855, size 1222656: OK sd1s5: start 819232, end = 2041855, size 1222624: OK sd1s1: start 32, end = 819199, size 819168: OK sd1s2: start 819200, end = 2041855, size 1222656: OK sd1s5: start 819232, end = 2041855, size 1222624: OK I'm going to try writing out the new boot blocks, now that I understand what things should be doing a little better. This is not going to be fun to support, but I have to admit that it's far nicer than the old organization. Kudos to all. From owner-freebsd-bugs Tue Mar 28 21:33:50 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA21957 for bugs-outgoing; Tue, 28 Mar 1995 21:33:50 -0800 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 VAA21927; Tue, 28 Mar 1995 21:33:38 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id PAA18058; Wed, 29 Mar 1995 15:30:15 +1000 Date: Wed, 29 Mar 1995 15:30:15 +1000 From: Bruce Evans Message-Id: <199503290530.PAA18058@godzilla.zeta.org.au> To: freebsd-bugs@freefall.cdrom.com, jkh@freefall.cdrom.com, pst@Shockwave.COM Subject: Re: Changed information for PR misc/278 Sender: bugs-owner@FreeBSD.org Precedence: bulk >Synopsis: the echos in /etc/rc to start syscons have a couple of mistakes >State-Changed-From-To: open-closed >State-Changed-By: jkh >State-Changed-When: Tue Mar 28 19:35:18 PST 1995 >State-Changed-Why: >Problem addressed. Hrrmph. We're further from ever from allowing /usr to be nfs-mounted. /etc/netstart is bloated and broken. It used to be possible to run it independently of /etc/rc. This was useful for starting network interfaces from the single user shell. Now it wants to start lots of network daemons from unmounted partitions. Bruce From owner-freebsd-bugs Tue Mar 28 21:40:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA22061 for bugs-outgoing; Tue, 28 Mar 1995 21:40:02 -0800 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA22051; Tue, 28 Mar 1995 21:40:01 -0800 Date: Tue, 28 Mar 1995 21:40:01 -0800 Message-Id: <199503290540.VAA22051@freefall.cdrom.com> From: Paul Traina Reply-To: Paul Traina To: freebsd-bugs Subject: kern/281: messages printed when checking CD ROM device too verbose In-Reply-To: Your message of Tue, 28 Mar 1995 21:35:22 -0800 <199503290535.VAA00349@precipice.shockwave.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 281 >Category: kern >Synopsis: Messages printed when checking CD ROM device too verbose >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: Tue Mar 28 21:40:00 1995 >Originator: Paul Traina >Organization: >Release: FreeBSD 2.1.0-Development i386 >Environment: FreeBSD 2.1.0-current as of last night >Description: (bt0:4:0): "NEC CD-ROM DRIVE:210 1.0" is a type 5 removable SCSI 1 cd0(bt0:4:0): CD-ROM cd0(bt0:4:0): NOT READY csi:20,b,0,0 asc:b,0 cd0: could not get size drive empty I loaded up the new boot blocks and am NOT booting with -v, so verbose is turned off. This is way too much information, and the "drive empty" line doesn't refer to the device. In my opinion, the output in this case should have simply been: (bt0:4:0): "NEC CD-ROM DRIVE:210 1.0" is a type 5 removable SCSI 1 cd0: drive empty >How-To-Repeat: Boot a kernel on a system with a CDROM drive with nothing in it. >Fix: Lose the following lines: cd0(bt0:4:0): CD-ROM cd0(bt0:4:0): NOT READY csi:20,b,0,0 asc:b,0 cd0: could not get size Add the device name to the line: drive empty >Audit-Trail: >Unformatted: From owner-freebsd-bugs Tue Mar 28 21:40:03 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA22072 for bugs-outgoing; Tue, 28 Mar 1995 21:40:03 -0800 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA22065; Tue, 28 Mar 1995 21:40:02 -0800 Date: Tue, 28 Mar 1995 21:40:02 -0800 Message-Id: <199503290540.VAA22065@freefall.cdrom.com> From: Paul Traina Reply-To: Paul Traina To: freebsd-bugs Subject: kern/282: buslogic adapter information WAY too verbose In-Reply-To: Your message of Tue, 28 Mar 1995 21:39:10 -0800 <199503290539.VAA00457@precipice.shockwave.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 282 >Category: kern >Synopsis: buslogic adapter information WAY too verbose >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: Tue Mar 28 21:40:01 1995 >Originator: Paul Traina >Organization: >Release: FreeBSD 2.1.0-Development i386 >Environment: FreeBSD 2.1.0-current as of last night on a system with a buslogic BT445S controller. >Description: There's a lot of crud printed at boot time that is only interesting if we're booting with the -v (verbose) flag set. Lose it. bt0: Bt445S/ 0-PCI/EISA/VLB(32bit) bus bt0: reading board settings, dma=5, int=11 bt0: version 3.37, fast sync, no parity, 32 mbxs, 32 ccbs bt0: targ 0 sync rate=10.00MB/s(100ns), offset=15 bt0: targ 1 sync rate= 4.54MB/s(220ns), offset=15 bt0: targ 4 async bt0: targ 6 async bt0: Enabling Round robin scheme bt0 at 0x330 irq 11 drq 5 on isa Of all of this stuff, the only interesting lines that should be printed if -v is not set are: bt0: Bt445S/ 0-PCI/EISA/VLB(32bit) bus bt0 at 0x330 irq 11 drq 5 on isa >How-To-Repeat: Boot a current kernel on a box with a buslogic controller and watch the fun. >Fix: Conditionalize things so only useful information is printed without -v. By the way, the reason I am on this less is better kick is because I'm trying to stop the useful information from being scrolled off the screen if something really is wrong. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Tue Mar 28 22:27:16 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA06941 for bugs-outgoing; Tue, 28 Mar 1995 22:27:16 -0800 Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA06915; Tue, 28 Mar 1995 22:27:12 -0800 Received: from localhost (localhost [127.0.0.1]) by precipice.shockwave.com (8.6.11/8.6.9) with SMTP id WAA00864; Tue, 28 Mar 1995 22:26:34 -0800 Message-Id: <199503290626.WAA00864@precipice.shockwave.com> To: jkh@FreeBSD.org cc: freebsd-bugs@FreeBSD.org Subject: misc/276: rc.maint vs syslogd Date: Tue, 28 Mar 1995 22:26:34 -0800 From: Paul Traina Sender: bugs-owner@FreeBSD.org Precedence: bulk I'm a little confused on how this all got messed up. Here's what I think should be done to get us back behaving in classic fashion: (a) /etc/netstart just starts things needed to start networking (i.e. it -just- does the interface configurations, no NFS, no xntpd, no sendmail, no inetd) (b) start up the networking daemons necessary for mounting remote disks (portmapper, nfsiod, do the mount) (c) start up the time tracking stuff (ntpdate/xntpd/timed/adjtime) (d) invoke syslogd right after the directory clearing stuff in /etc/rc.maint (except it's back in rc...see below) (e) lose /etc/rc.maint ... I don't see what advantage we gained by splitting this stuff out in the first place... put that stuff back in to /etc/rc so we have more flexibility with placement... (f) start up the other daemons that we need and inetd If you don't hate this, I'll actually go to the trouble of generating the new /etc files and test them out. I would -like- to make it so that FreeBSD really can boot properly with a remote /usr or boot diskless. It's really bad that we've lost this ability. From owner-freebsd-bugs Tue Mar 28 22:39:13 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA09869 for bugs-outgoing; Tue, 28 Mar 1995 22:39:13 -0800 Received: from thud.cdrom.com (thud.cdrom.com [192.216.222.13]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA09863 for ; Tue, 28 Mar 1995 22:39:12 -0800 Received: (from timb@localhost) by thud.cdrom.com (8.6.11/8.6.9) id WAA01185 for bugs@freebsd.org; Tue, 28 Mar 1995 22:39:04 -0800 Date: Tue, 28 Mar 1995 22:39:04 -0800 From: Tim Bach Message-Id: <199503290639.WAA01185@thud.cdrom.com> To: bugs@FreeBSD.org Sender: bugs-owner@FreeBSD.org Precedence: bulk Subject:System lock's up completly with no reason in LATEST SNAP I am not sure what is causing this but every so often when i am doing a few things the system will totally free and i can't get control on any of the virtual consoles.. I am running slip on a 486dx66 with 8 meg's of memory using the latest snap.. I was running a finger in the background and somebody was running lynx then tin which after it soon after it core dump or around the same time the system totally hung.. It did this once before when i was just doing misc things to.. I think it also had this problem is the kernel from about a week ago to current. Anyone got any clues on this?.. I believe this problem also happend when i was running ppp but i am not certain. From owner-freebsd-bugs Tue Mar 28 23:04:15 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA10695 for bugs-outgoing; Tue, 28 Mar 1995 23:04:15 -0800 Received: from relay.philips.nl (relay.philips.nl [130.144.65.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA10683; Tue, 28 Mar 1995 23:04:13 -0800 Received: from muxgw1.ms.philips.nl ([130.144.90.6]) by relay.philips.nl (8.6.9/8.6.9-950103) with SMTP id JAA27319; Wed, 29 Mar 1995 09:02:24 +0200 Received: by muxgw1.ms.philips.nl (5.57/Ultrix2.4-C) id AA00503; Wed, 29 Mar 95 08:45:50 +0300 Received: by mmra1.ms.philips.nl (4.1/SMI-4.1) id AA23134; Wed, 29 Mar 95 09:00:39 +0200 From: gvrooij@mmra1.ms.philips.nl (Guido van Rooij) Message-Id: <9503290700.AA23134@mmra1.ms.philips.nl> Subject: Re: kern/280: new slice manager totally confused about old slice disks To: pst@shockwave.com (Paul Traina) Date: Wed, 29 Mar 1995 09:00:39 +0200 (MET DST) Cc: jkh@freefall.cdrom.com, freebsd-bugs@freefall.cdrom.com In-Reply-To: <199503290525.VAA01190@precipice.shockwave.com> from "Paul Traina" at Mar 28, 95 09:25:09 pm X-Mailer: ELM [version 2.4 PL21] Content-Type: text Content-Length: 1458 Sender: bugs-owner@FreeBSD.org Precedence: bulk > > Aha, ok, this worked for me, I now understand a lot more about the slice > scheme (took only 30 seconds wall clock time and 1 second CPU time). > I still dont get it completely. At first I thought the slices referred to `fdisk partition' and partitions to `BSD partitions'. But now I'm not sure anymore, as I saw slice 5 as well. Or do we support extended slices now? Further: I *know* 2.0R made releases where disklable would complain about partition c and d extending past the end of the drive (due to the total #sec > #secpertrack * #heads * #cyl. I guess the option to use the rest of the drive for a partition took all sectors left, while not checking the consistency of all drive params). How is that handled by this new scheme? > I would suggest documenting the living hell out of this. > Yep. > The gratuitous kernel printfs when accessing the label are a bit much, > do they only happen when booting in verbose mode? > > sd0s1: start 32, end = 511999, size 511968: OK > sd0s4: start 512000, end = 3514367, size 3002368: OK > sd0: rejecting partition in BSD label: it isn't entirely within the slice What exactly does this message mean? And, more important, what are its consequences on operation? > This is not going to be fun to support, but I have to admit that it's > far nicer than the old organization. Kudos to all. > It looks nice at first sight, but I haven't got the feeling that I completely understand it (yet). -Guido From owner-freebsd-bugs Tue Mar 28 23:14:28 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA10880 for bugs-outgoing; Tue, 28 Mar 1995 23:14:28 -0800 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 XAA10860; Tue, 28 Mar 1995 23:14:06 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id RAA20923; Wed, 29 Mar 1995 17:12:22 +1000 Date: Wed, 29 Mar 1995 17:12:22 +1000 From: Bruce Evans Message-Id: <199503290712.RAA20923@godzilla.zeta.org.au> To: jkh@freefall.cdrom.com, root@Shockwave.COM Subject: Re: kern/280: new slice manager totally confused about old slice disks Cc: freebsd-bugs@freefall.cdrom.com Sender: bugs-owner@FreeBSD.org Precedence: bulk > Subject: Re: kern/280: new slice manager totally confused about old slice dis >>>ks > > 1) It looks like the implicit label stuff for unlabeled disks is > > non-functional? I cannot ask disklable to read the pseudo-label off > > of sd1 Did you install a current MAKEDEV and run it? > Maybe if you specify /dev/sd0d explicitly? Works for me! It shouldn't work. The d partition is no longer special. >root@precipice$ disklabel /dev/sd1d >disklabel: /dev/sd1d: Invalid argument Correct. Perhaps the errno's could be improved. I seem to have broken ENXIO being returned for opens of nonexistent partitions (EINVAL is now returned) while fixing(?) sd's return of ENXIO for existent empty partitions (wd always allowed opening such partitions). Both drives always returned the confusing errno EINVAL for nonexistent labels. >root@precipice$ disklabel sd1 >disklabel: ioctl DIOCGDINFO: Invalid argument disklabel(8) translates sd1 to /dev/sd1c. Apparently you have no label on sd1c. `disklabel sd1' used to return a dummy in-core label if there is no label on the disk, but this didn't seem reasonable so I broke it. There is no-longer a dummy in-core label for each slice, and you wouldn't want one for non-BSD slices. There is only a dummy in-core label for the whole disk. The whole disk is the device /dev/sd1, which is a completely different device from sd1 and /dev/sd1c. >sd1s1: start 32, end = 819199, size 819168: OK >sd1s2: start 819200, end = 2041855, size 1222656: OK >sd1s5: start 819232, end = 2041855, size 1222624: OK > > 2) All of this slice stuff is really verbose and I think gratuitous. > > Note: I am using older boot blocks that don't support -v, so it More is apparently required for debugging old broken installations :-(. > > 2) When the system is booting, it whines loudly about partitions not being > > inside slices... this may indeed be an error condition, but that's the > > way FreeBSD 2.0 did things, so you're going to have a hell of a support > > problem with these new slice changes. > > Agreed again. We're going to need to deal with this somehow, or users > are going to SCREECH. Bruce is safe over there in OZ, but I know that > folks like Poul and I are going to get hundreds of mails in our boxes! :-( Disagreed. Aren't you going to tell everyone to reinstall like you did with all previous releases? The new sysinstall won't make any invalid slices or partitions ;-). > > 3) Oh where oh where has my MSDOS partition gone? Oh where oh where > > can it beeeeee? Apparently the verbose boot info should include freebsd-current mail explaining all this :-|. > Try copying the new MAKEDEV over and doing a ./MAKEDEV sd0, then try: > > mount -t msdos /dev/sd0s1 /dos > > Assuming, of course, that slice 1 is the DOS partition. This is Not a good assumption. There may be up to 26 DOS partitions starting as late as slice s4 (primary partition #4, extended partition #3 containing 25 more). Very few setups will have this, but the install program has to be careful not to break it (if not support it), and people answering bug reports should know about it. > actually a very GOOD part of the change and I'm happy that we have it. > It will make auto-detecting and mounting the DOS partition from the > install much easier (I can just look to see what partition is a DOS > partition and then mount the corresponding slice). I need to add an ioctl to return the slice struct. It still isn't easy, because there are several different DOS partition types and no requirement that the partition type have anything to do with the file system type. >I'm a little fuzzy on something, what is a slice vs a partition? >Is a slice one of the one of four (recursive) classic DOS partitions >or is a slice a UNIX disklabel partition? DOS calls its subdivisions of a disk `partitions' and so does FreeBSD. The slice code nests FreeBSD partitions (if any) inside DOS partitions (if any). It is very confusing to call both `partitions' so we usually call the DOS ones `slices'. Bruce From owner-freebsd-bugs Tue Mar 28 23:23:37 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA10983 for bugs-outgoing; Tue, 28 Mar 1995 23:23:37 -0800 Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA10977; Tue, 28 Mar 1995 23:23:33 -0800 Received: (from nate@localhost) by trout.sri.MT.net (8.6.9/8.6.9) id AAA13507; Wed, 29 Mar 1995 00:26:50 -0700 Date: Wed, 29 Mar 1995 00:26:50 -0700 Message-Id: <199503290726.AAA13507@trout.sri.MT.net> To: Bruce Evans Cc: jkh@freefall.cdrom.com, root@Shockwave.COM, freebsd-bugs@freefall.cdrom.com Subject: Re: kern/280: new slice manager totally confused about old slice disks In-Reply-To: <199503290712.RAA20923@godzilla.zeta.org.au> References: <199503290712.RAA20923@godzilla.zeta.org.au> Reply-To: nate@sneezy.sri.com (Nate Williams) From: nate@sneezy.sri.com (Nate Williams) Sender: bugs-owner@FreeBSD.org Precedence: bulk > > Agreed again. We're going to need to deal with this somehow, or users > > are going to SCREECH. Bruce is safe over there in OZ, but I know that > > folks like Poul and I are going to get hundreds of mails in our boxes! :-( > > Disagreed. Aren't you going to tell everyone to reinstall like you did with > all previous releases? The new sysinstall won't make any invalid slices > or partitions ;-). The upgrade from 1.0 -> 1.1 didn't require a re-install. ;) (And neither did the upgrade from 386BSD -> FreeBSD. I wrote the upgrade script for that) Nate From owner-freebsd-bugs Tue Mar 28 23:38:18 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA11132 for bugs-outgoing; Tue, 28 Mar 1995 23:38:18 -0800 Received: from relay.philips.nl (relay.philips.nl [130.144.65.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA11126; Tue, 28 Mar 1995 23:38:15 -0800 Received: from muxgw1.ms.philips.nl ([130.144.90.6]) by relay.philips.nl (8.6.9/8.6.9-950103) with SMTP id JAA29199; Wed, 29 Mar 1995 09:36:30 +0200 Received: by muxgw1.ms.philips.nl (5.57/Ultrix2.4-C) id AA00757; Wed, 29 Mar 95 09:20:06 +0300 Received: by mmra1.ms.philips.nl (4.1/SMI-4.1) id AA25038; Wed, 29 Mar 95 09:34:56 +0200 From: gvrooij@mmra1.ms.philips.nl (Guido van Rooij) Message-Id: <9503290734.AA25038@mmra1.ms.philips.nl> Subject: Re: kern/280: new slice manager totally confused about old slice disks To: bde@zeta.org.au (Bruce Evans) Date: Wed, 29 Mar 1995 09:34:55 +0200 (MET DST) Cc: jkh@freefall.cdrom.com, root@shockwave.com, freebsd-bugs@freefall.cdrom.com In-Reply-To: <199503290712.RAA20923@godzilla.zeta.org.au> from "Bruce Evans" at Mar 29, 95 05:12:22 pm X-Mailer: ELM [version 2.4 PL21] Content-Type: text Content-Length: 934 Sender: bugs-owner@FreeBSD.org Precedence: bulk > > Agreed again. We're going to need to deal with this somehow, or users > > are going to SCREECH. Bruce is safe over there in OZ, but I know that > > folks like Poul and I are going to get hundreds of mails in our boxes! :-( > > Disagreed. Aren't you going to tell everyone to reinstall like you did with > all previous releases? The new sysinstall won't make any invalid slices > or partitions ;-). > Please tell me that this is *not* going to happen. It is rediculous to ask to completely reinstall everything each time a new release comes out. Ppl have more on their mind than disklabel their disks again to support yet another view on the disks (even if its a big improvement) I would be very upset if I'd have to backup 7 gigs again just to upgrade and wait for 2 whole days for restore to finish (if I'm lucky enough that dump does break again like it does all the time nowadays, see freebsd-questions). -Guido From owner-freebsd-bugs Tue Mar 28 23:47:51 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA11277 for bugs-outgoing; Tue, 28 Mar 1995 23:47:51 -0800 Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA11271; Tue, 28 Mar 1995 23:47:50 -0800 Received: from localhost (localhost [127.0.0.1]) by precipice.shockwave.com (8.6.11/8.6.9) with SMTP id XAA00441; Tue, 28 Mar 1995 23:46:57 -0800 Message-Id: <199503290746.XAA00441@precipice.shockwave.com> To: gvrooij@mmra1.ms.philips.nl (Guido van Rooij) cc: jkh@freefall.cdrom.com, freebsd-bugs@freefall.cdrom.com Subject: Re: kern/280: new slice manager totally confused about old slice disks In-reply-to: Your message of "Wed, 29 Mar 1995 09:00:39 +0200." <9503290700.AA23134@mmra1.ms.philips.nl> Date: Tue, 28 Mar 1995 23:46:57 -0800 From: Paul Traina Sender: bugs-owner@FreeBSD.org Precedence: bulk From: gvrooij@mmra1.ms.philips.nl (Guido van Rooij) Subject: Re: kern/280: new slice manager totally confused about old slice dis >>ks > > Aha, ok, this worked for me, I now understand a lot more about the slice > scheme (took only 30 seconds wall clock time and 1 second CPU time). > I still dont get it completely. At first I thought the slices referred to `fdisk partition' and partitions to `BSD partitions'. But now I'm not sure anymore, as I saw slice 5 as well. Or do we support extended slices now? Yes, and they seem to even work. :-) Further: I *know* 2.0R made releases where disklable would complain about partition c and d extending past the end of the drive (due to the total #sec > #secpertrack * #heads * #cyl. I guess the option to use the rest of the drive for a partition took all sectors left, while not checking the consistency of all drive params). How is that handled by this new scheme? Dunno... Bruce? > I would suggest documenting the living hell out of this. > Yep. > The gratuitous kernel printfs when accessing the label are a bit much, > do they only happen when booting in verbose mode? > > sd0s1: start 32, end = 511999, size 511968: OK > sd0s4: start 512000, end = 3514367, size 3002368: OK > sd0: rejecting partition in BSD label: it isn't entirely within the slice What exactly does this message mean? And, more important, what are its consequences on operation? Yes, the message is quite ambiguious and the printf's are debugging and need to go. > This is not going to be fun to support, but I have to admit that it's > far nicer than the old organization. Kudos to all. > It looks nice at first sight, but I haven't got the feeling that I completely understand it (yet). -Guido From owner-freebsd-bugs Tue Mar 28 23:52:11 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA11367 for bugs-outgoing; Tue, 28 Mar 1995 23:52:11 -0800 Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA11361; Tue, 28 Mar 1995 23:52:09 -0800 Received: from localhost (localhost [127.0.0.1]) by precipice.shockwave.com (8.6.11/8.6.9) with SMTP id XAA00464; Tue, 28 Mar 1995 23:50:44 -0800 Message-Id: <199503290750.XAA00464@precipice.shockwave.com> To: Bruce Evans cc: jkh@freefall.cdrom.com, root@shockwave.com, freebsd-bugs@freefall.cdrom.com Subject: Re: kern/280: new slice manager totally confused about old slice disks In-reply-to: Your message of "Wed, 29 Mar 1995 17:12:22 +1000." <199503290712.RAA20923@godzilla.zeta.org.au> Date: Tue, 28 Mar 1995 23:50:44 -0800 From: Paul Traina Sender: bugs-owner@FreeBSD.org Precedence: bulk From: Bruce Evans Subject: Re: kern/280: new slice manager totally confused about old slice dis >>ks > Subject: Re: kern/280: new slice manager totally confused about old slice >>dis >>>ks > > 1) It looks like the implicit label stuff for unlabeled disks is > > non-functional? I cannot ask disklable to read the pseudo-label off > > of sd1 Did you install a current MAKEDEV and run it? Yes, I just didn't understand what I did at the time... all is working fine now, very very nice job overall. > Maybe if you specify /dev/sd0d explicitly? Works for me! It shouldn't work. The d partition is no longer special. Yep. >root@precipice$ disklabel /dev/sd1d >disklabel: /dev/sd1d: Invalid argument Correct. Perhaps the errno's could be improved. I seem to have broken ENXIO being returned for opens of nonexistent partitions (EINVAL is now returned) while fixing(?) sd's return of ENXIO for existent empty partitions (wd always allowed opening such partitions). Both drives always returned the confusing errno EINVAL for nonexistent labels. >root@precipice$ disklabel sd1 >disklabel: ioctl DIOCGDINFO: Invalid argument disklabel(8) translates sd1 to /dev/sd1c. Apparently you have no label on sd1c. `disklabel sd1' used to return a dummy in-core label if there is no label on the disk, but this didn't seem reasonable so I broke it. There is no-longer a dummy in-core label for each slice, and you wouldn't want one for non-BSD slices. There is only a dummy in-core label for the whole disk. The whole disk is the device /dev/sd1, which is a completely different device from sd1 and /dev/sd1c. Yep, makes perfect sense. >sd1s1: start 32, end = 819199, size 819168: OK >sd1s2: start 819200, end = 2041855, size 1222656: OK >sd1s5: start 819232, end = 2041855, size 1222624: OK > > 2) All of this slice stuff is really verbose and I think gratuitous. > > Note: I am using older boot blocks that don't support -v, so it More is apparently required for debugging old broken installations :-(. Actually, I just think judicious use of bootverbose would help here. As far as documentation, all I can say is document the shit out of this in the 2.1 release notes in the area "READ AT LEAST THIS BEFORE YOU START" :-) From owner-freebsd-bugs Wed Mar 29 00:25:05 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA11589 for bugs-outgoing; Wed, 29 Mar 1995 00:25:05 -0800 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id AAA11583 for ; Wed, 29 Mar 1995 00:25:03 -0800 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id DAA02000; Wed, 29 Mar 1995 03:25:05 -0500 From: Peter Dufault Message-Id: <199503290825.DAA02000@hda.com> Subject: Re: kern/281: messages printed when checking CD ROM device too verbose To: pst@Shockwave.COM Date: Wed, 29 Mar 1995 03:25:04 -0500 (EST) Cc: freebsd-bugs@freefall.cdrom.com In-Reply-To: <199503290540.VAA22051@freefall.cdrom.com> from "Paul Traina" at Mar 28, 95 09:40:01 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1137 Sender: bugs-owner@FreeBSD.org Precedence: bulk I know this isn't quite what you'll want, but how about: > (bt0:4:0): "NEC CD-ROM DRIVE:210 1.0" is a type 5 removable SCSI 1 > cd0(bt0:4:0): CD-ROM > cd0(bt0:4:0): NOT READY csi:20,b,0,0 asc:b,0 > could not get size with: > (bt0:4:0): "NEC CD-ROM DRIVE:210 1.0" is a type 5 removable SCSI 1 > cd0(bt0:4:0): CD-ROM drive empty for devices we fully understand. The reason we still have a dangling line is that the driver is in the process of printing out the "CD-ROM [disk size]" line when the interrupt routine reports the undefined (in the SCSI-2 spec) error asc:b ascq:0. When this is something we understand then we can catch it and not log the message. In checking the code I see a buglet. The "drive empty" message is a bit presumptious - all we really know is we can't get the size. That's why I propose to change the message from "drive empty" to "could not get size". Some of checking in the ASC should let us be more explicit, but not in your case. -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-bugs Wed Mar 29 00:43:00 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA11878 for bugs-outgoing; Wed, 29 Mar 1995 00:43:00 -0800 Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id AAA11872 for ; Wed, 29 Mar 1995 00:42:58 -0800 Received: from localhost (localhost [127.0.0.1]) by precipice.shockwave.com (8.6.11/8.6.9) with SMTP id AAA00307; Wed, 29 Mar 1995 00:41:36 -0800 Message-Id: <199503290841.AAA00307@precipice.shockwave.com> To: Peter Dufault cc: freebsd-bugs@freefall.cdrom.com Subject: Re: kern/281: messages printed when checking CD ROM device too verbose In-reply-to: Your message of "Wed, 29 Mar 1995 03:25:04 EST." <199503290825.DAA02000@hda.com> Date: Wed, 29 Mar 1995 00:41:36 -0800 From: Paul Traina Sender: bugs-owner@FreeBSD.org Precedence: bulk Works for me. From: Peter Dufault Subject: Re: kern/281: messages printed when checking CD ROM device too verbo >>se I know this isn't quite what you'll want, but how about: > (bt0:4:0): "NEC CD-ROM DRIVE:210 1.0" is a type 5 removable SCSI 1 > cd0(bt0:4:0): CD-ROM > cd0(bt0:4:0): NOT READY csi:20,b,0,0 asc:b,0 > could not get size with: > (bt0:4:0): "NEC CD-ROM DRIVE:210 1.0" is a type 5 removable SCSI 1 > cd0(bt0:4:0): CD-ROM drive empty for devices we fully understand. The reason we still have a dangling line is that the driver is in the process of printing out the "CD-ROM [disk size]" line when the interrupt routine reports the undefined (in the SCSI-2 spec) error asc:b ascq:0. When this is something we understand then we can catch it and not log the message. In checking the code I see a buglet. The "drive empty" message is a bit presumptious - all we really know is we can't get the size. That's why I propose to change the message from "drive empty" to "could not get size". Some of checking in the ASC should let us be more explicit, but not in your case. -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-bugs Wed Mar 29 00:49:25 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA11950 for bugs-outgoing; Wed, 29 Mar 1995 00:49:25 -0800 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 AAA11944; Wed, 29 Mar 1995 00:49:00 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id SAA23221; Wed, 29 Mar 1995 18:43:47 +1000 Date: Wed, 29 Mar 1995 18:43:47 +1000 From: Bruce Evans Message-Id: <199503290843.SAA23221@godzilla.zeta.org.au> To: gvrooij@mmra1.ms.philips.nl, pst@shockwave.com Subject: Re: kern/280: new slice manager totally confused about old slice disks Cc: freebsd-bugs@freefall.cdrom.com, jkh@freefall.cdrom.com Sender: bugs-owner@FreeBSD.org Precedence: bulk >I still dont get it completely. At first I thought the slices referred >to `fdisk partition' and partitions to `BSD partitions'. This is correct. >But now I'm not sure anymore, as I saw slice 5 as well. Or do we support >extended slices now? Drivers now support extended slices although fdisk doesn't. >Further: I *know* 2.0R made releases where disklable would complain about >partition c and d extending past the end of the drive (due to the total >#sec > #secpertrack * #heads * #cyl. I guess the option to use the rest I think sysinstall creates a valid disk label with size #secpertrack * #heads * #cyl in both the d_secperunit and the 'd' partition size fields. The problem occurs when the sd driver blows away the 'd' partition size field (replacing it with the total #sec) without touching the d_secperunit field. The wd driver is more careful and verbose. It replaces the 'd' partition size field by the d_secperunit field and warns if there is a change. The size reported by the drive gets blown away by the d_secperunit field earlier (this is "fixed" in the sliced version of wd). >of the drive for a partition took all sectors left, while not checking >the consistency of all drive params). >How is that handled by this new scheme? The label is adjusted so that all partitions are within the slice and warnings are printed about all adjustments. >> The gratuitous kernel printfs when accessing the label are a bit much, >> do they only happen when booting in verbose mode? >> >> sd0s1: start 32, end = 511999, size 511968: OK >> sd0s4: start 512000, end = 3514367, size 3002368: OK >> sd0: rejecting partition in BSD label: it isn't entirely within the slice >What exactly does this message mean? And, more important, what are its >consequences on operation? The OK messages are mainly to help debug the errror messages. (If any. This is for a device driver - it isn't reasonable to look ahead 10 slices to decide if the OK messages should be printed. The bootverbose flag doesn't apply because the messages are for open(), not for probe()/ attach(). You might need these messages after screwing up the DOS partitioning.) The other message (1 line of 3) occurs because FreeBSD partitions are now required to be within the FreeBSD slice that the label is on. This helps stop FreeBSD from writing to foreign slices when labels are misconfigured. Rejected partitions become empty so you can't damage them. Bruce From owner-freebsd-bugs Wed Mar 29 01:14:10 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA12589 for bugs-outgoing; Wed, 29 Mar 1995 01:14:10 -0800 Received: from relay.philips.nl (relay.philips.nl [130.144.65.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id BAA12581; Wed, 29 Mar 1995 01:14:02 -0800 Received: from muxgw1.ms.philips.nl ([130.144.90.6]) by relay.philips.nl (8.6.9/8.6.9-950103) with SMTP id LAA04262; Wed, 29 Mar 1995 11:11:26 +0200 Received: by muxgw1.ms.philips.nl (5.57/Ultrix2.4-C) id AA01894; Wed, 29 Mar 95 10:54:58 +0300 Received: by mmra1.ms.philips.nl (4.1/SMI-4.1) id AA27856; Wed, 29 Mar 95 11:09:47 +0200 From: gvrooij@mmra1.ms.philips.nl (Guido van Rooij) Message-Id: <9503290909.AA27856@mmra1.ms.philips.nl> Subject: Re: kern/280: new slice manager totally confused about old slice disks To: bde@zeta.org.au (Bruce Evans) Date: Wed, 29 Mar 1995 11:09:46 +0200 (MET DST) Cc: pst@shockwave.com, freebsd-bugs@freefall.cdrom.com, jkh@freefall.cdrom.com In-Reply-To: <199503290843.SAA23221@godzilla.zeta.org.au> from "Bruce Evans" at Mar 29, 95 06:43:47 pm X-Mailer: ELM [version 2.4 PL21] Content-Type: text Content-Length: 2658 Sender: bugs-owner@FreeBSD.org Precedence: bulk > > This is correct. > That's a big improvement. Thanks! > > I think sysinstall creates a valid disk label with size > #secpertrack * #heads * #cyl in both the d_secperunit and the 'd' partition > size fields. The problem occurs when the sd driver blows away the 'd' > partition size field (replacing it with the total #sec) without touching > the d_secperunit field. The wd driver is more careful and verbose. It Might well explain what we see indeed. But the same holds for the c partition. > replaces the 'd' partition size field by the d_secperunit field and warns > if there is a change. The size reported by the drive gets blown away by > the d_secperunit field earlier (this is "fixed" in the sliced version of > wd). > > >of the drive for a partition took all sectors left, while not checking > >the consistency of all drive params). > >How is that handled by this new scheme? > > The label is adjusted so that all partitions are within the slice and > warnings are printed about all adjustments. > > >> The gratuitous kernel printfs when accessing the label are a bit much, > >> do they only happen when booting in verbose mode? > >> > >> sd0s1: start 32, end = 511999, size 511968: OK > >> sd0s4: start 512000, end = 3514367, size 3002368: OK > >> sd0: rejecting partition in BSD label: it isn't entirely within the slice > > >What exactly does this message mean? And, more important, what are its > >consequences on operation? > > The OK messages are mainly to help debug the errror messages. (If any. > This is for a device driver - it isn't reasonable to look ahead 10 > slices to decide if the OK messages should be printed. The bootverbose > flag doesn't apply because the messages are for open(), not for probe()/ > attach(). You might need these messages after screwing up the DOS > partitioning.) > Sounds fair enough. > The other message (1 line of 3) occurs because FreeBSD partitions are > now required to be within the FreeBSD slice that the label is on. This > helps stop FreeBSD from writing to foreign slices when labels are > misconfigured. Rejected partitions become empty so you can't damage > them. > But what abt the following scheme: I've got a disk, labeled by 2.0R whit only one slice, namely for freebsd with the defect I mentioned earlier (i.e. that the sd driver replaces the c and d partition sizes with larger values than possible according to the other drive params.). I dont have sources handy and might well mix up the order of evaluation but if the slice code rejects the c and d partitions because of their sizes, it will also at least reject the (physically) last partition... -Guido From owner-freebsd-bugs Wed Mar 29 01:20:05 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA12822 for bugs-outgoing; Wed, 29 Mar 1995 01:20:05 -0800 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 BAA12766; Wed, 29 Mar 1995 01:19:37 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id TAA24895; Wed, 29 Mar 1995 19:14:28 +1000 Date: Wed, 29 Mar 1995 19:14:28 +1000 From: Bruce Evans Message-Id: <199503290914.TAA24895@godzilla.zeta.org.au> To: gvrooij@mmra1.ms.philips.nl, pst@shockwave.com Subject: Re: kern/280: new slice manager totally confused about old slice disks Cc: freebsd-bugs@freefall.cdrom.com, jkh@freefall.cdrom.com Sender: bugs-owner@FreeBSD.org Precedence: bulk > > The gratuitous kernel printfs when accessing the label are a bit much, > > do they only happen when booting in verbose mode? > > > > sd0s1: start 32, end = 511999, size 511968: OK > > sd0s4: start 512000, end = 3514367, size 3002368: OK These printfs happen whenever a device on a sliced drive is opened and there are no other devices on the drive open (all slice tables and labels for the drive are forgotten - this is unfortunately currently the only mechanism for picking up changes to the on-disk slice tables (the "DOS" partition tables for i386ish systems)). > > sd0: rejecting partition in BSD label: it isn't entirely within the slice These printfs happen whenever a device on a BSD-labeled slice is opened and the label for the slice is not already in core and there is an error. Labels are kept in core across closes of all devices on the slice, except they are forgotten after all devices on the drive are closed, as above. > What exactly does this message mean? And, more important, what are its > consequences on operation? >Yes, the message is quite ambiguious and the printf's are debugging and >need to go. The error messages should have more punctuation: > > sd0: rejecting partition in BSD label: it isn't entirely within the slice: ^ [2 more lines not quoted]. > > This is not going to be fun to support, but I have to admit that it's > > far nicer than the old organization. Kudos to all. It would be worse if we supported nested^N partitions within other OS's partitions! There should only be one layer of partitioning. Bruce From owner-freebsd-bugs Wed Mar 29 01:25:29 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA12925 for bugs-outgoing; Wed, 29 Mar 1995 01:25:29 -0800 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id BAA12917; Wed, 29 Mar 1995 01:25:26 -0800 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: Bruce Evans cc: freebsd-bugs@freefall.cdrom.com, pst@shockwave.com Subject: Re: Changed information for PR misc/278 In-reply-to: Your message of "Wed, 29 Mar 95 15:30:15 +1000." <199503290530.PAA18058@godzilla.zeta.org.au> Date: Wed, 29 Mar 1995 01:25:26 -0800 Message-ID: <12916.796469126@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: bugs-owner@FreeBSD.org Precedence: bulk > /etc/netstart is bloated and broken. It used to be possible to run > it independently of /etc/rc. This was useful for starting network > interfaces from the single user shell. Now it wants to start lots > of network daemons from unmounted partitions. Well, it also seems to be something of a sacred cow around here and I got flamed when I tried to significantly alter it. I've really no immediate idea as to how to restructure the thing, and there's a lot to be said for adding a `NETWORKED=[yes|no]' that possibly even turns most of this stuff OFF for situations where the machine *isn't even on a network and never will be*. Has anyone stopped to consider this case? We've always just barreled along and never even really given the user the opportunity to easily deselect what might be an entirely gratuitous set of daemons.. Sigh.. I think it must be said: Most of /etc is a mess, it always has been a mess and all I've ever seen other operating systems do with it is make it a more *convoluted* mess (SVR4 - gag me!). What's the cool, killer paradigm shift we're missing here? :-) Jordan From owner-freebsd-bugs Wed Mar 29 01:35:18 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA15153 for bugs-outgoing; Wed, 29 Mar 1995 01:35:18 -0800 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 BAA14924; Wed, 29 Mar 1995 01:34:59 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id TAA25301; Wed, 29 Mar 1995 19:33:09 +1000 Date: Wed, 29 Mar 1995 19:33:09 +1000 From: Bruce Evans Message-Id: <199503290933.TAA25301@godzilla.zeta.org.au> To: bde@zeta.org.au, gvrooij@mmra1.ms.philips.nl Subject: Re: kern/280: new slice manager totally confused about old slice disks Cc: freebsd-bugs@freefall.cdrom.com, jkh@freefall.cdrom.com, pst@shockwave.com Sender: bugs-owner@FreeBSD.org Precedence: bulk >> I think sysinstall creates a valid disk label with size >> #secpertrack * #heads * #cyl in both the d_secperunit and the 'd' partition >> size fields. The problem occurs when the sd driver blows away the 'd' >> partition size field (replacing it with the total #sec) without touching >> the d_secperunit field. The wd driver is more careful and verbose. It >Might well explain what we see indeed. But the same holds for the c partition. Maybe sysinstall set the size of the c partition correctly to extend to the end of the disk, and d_secperunit to match. Old versions of `disklabel -e' rounded down d_secperunit to a cylinder boundary so running `disklabel -e' could cause the problem. >But what abt the following scheme: >I've got a disk, labeled by 2.0R whit only one slice, namely for freebsd >with the defect I mentioned earlier (i.e. that the sd driver replaces >the c and d partition sizes with larger values than possible according >to the other drive params.). >I dont have sources handy and might well mix up the order of evaluation >but if the slice code rejects the c and d partitions because of their >sizes, it will also at least reject the (physically) last partition... The c partition size is rounded down while the d partition is rejected. These partitions are not used for normal operation (except maybe sector #2 of partition c to read the label) so normal operation is not normally affected. Similar rounding down of the a partition (e.g.) would cause problems if the file system extends into the lost sectors. Most such problems are avoided by specially handling the 50000-sector "whole disk for FreeBSD" partition table. Bruce From owner-freebsd-bugs Wed Mar 29 01:53:19 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA29085 for bugs-outgoing; Wed, 29 Mar 1995 01:53:19 -0800 Received: from isl.cf.ac.uk (isl-gate.elsy.cf.ac.uk [131.251.22.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id BAA28739; Wed, 29 Mar 1995 01:52:54 -0800 Received: (from paul@localhost) by isl.cf.ac.uk (8.6.9/8.6.9) id KAA18163; Wed, 29 Mar 1995 10:52:58 +0100 From: Paul Richards Message-Id: <199503290952.KAA18163@isl.cf.ac.uk> Subject: Re: Changed information for PR misc/278 To: jkh@freefall.cdrom.com (Jordan K. Hubbard) Date: Wed, 29 Mar 1995 10:52:58 +0100 (BST) Cc: pst@Shockwave.COM, jkh@freefall.cdrom.com, freebsd-bugs@freefall.cdrom.com In-Reply-To: <199503290335.TAA04904@freefall.cdrom.com> from "Jordan K. Hubbard" at Mar 28, 95 07:35:33 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 587 Sender: bugs-owner@FreeBSD.org Precedence: bulk In reply to Jordan K. Hubbard who said > > Synopsis: the echos in /etc/rc to start syscons have a couple of mistakes > > State-Changed-From-To: open-closed > State-Changed-By: jkh > State-Changed-When: Tue Mar 28 19:35:18 PST 1995 > State-Changed-Why: > Problem addressed. > Cmon Jordan, lead by example and include proper log messages. -- Paul Richards, FreeBSD core team member. Internet: paul@FreeBSD.org, URL: http://isl.cf.ac.uk/~paul/ Phone: +44 1222 874000 x6646 (work), +44 1222 457651 (home) Dept. Mechanical Engineering, University of Wales, College Cardiff. From owner-freebsd-bugs Wed Mar 29 02:03:33 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA29804 for bugs-outgoing; Wed, 29 Mar 1995 02:03:33 -0800 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 CAA29796; Wed, 29 Mar 1995 02:03:29 -0800 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.8/8.6.6) id CAA01968; Wed, 29 Mar 1995 02:03:17 -0800 From: "Rodney W. Grimes" Message-Id: <199503291003.CAA01968@gndrsh.aac.dev.com> Subject: Re: Changed information for PR misc/278 To: jkh@freefall.cdrom.com (Jordan K. Hubbard) Date: Wed, 29 Mar 1995 02:03:15 -0800 (PST) Cc: bde@zeta.org.au, freebsd-bugs@freefall.cdrom.com, pst@shockwave.com In-Reply-To: <12916.796469126@freefall.cdrom.com> from "Jordan K. Hubbard" at Mar 29, 95 01:25:26 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 2791 Sender: bugs-owner@FreeBSD.org Precedence: bulk > > > /etc/netstart is bloated and broken. It used to be possible to run > > it independently of /etc/rc. This was useful for starting network > > interfaces from the single user shell. Now it wants to start lots > > of network daemons from unmounted partitions. > > Well, it also seems to be something of a sacred cow around here and I > got flamed when I tried to significantly alter it. I've really no > immediate idea as to how to restructure the thing, and there's a lot > to be said for adding a `NETWORKED=[yes|no]' that possibly even turns > most of this stuff OFF for situations where the machine *isn't even on > a network and never will be*. Has anyone stopped to consider this > case? We've always just barreled along and never even really given > the user the opportunity to easily deselect what might be an entirely > gratuitous set of daemons.. > > Sigh.. I think it must be said: Most of /etc is a mess, it always has > been a mess and all I've ever seen other operating systems do with it > is make it a more *convoluted* mess (SVR4 - gag me!). What's the > cool, killer paradigm shift we're missing here? :-) As distributed up until the recent attempt at cleaning this up /etc/rc and /etc/netstart did just about the right thing for a machine with no actual network attachment. A lot of the daemons started are not just for internet connected machines, BSD itself wants atleast the loopback device running so things like syslogd can work. We do need to add the knobs to turn any of these off if so desired, and set the default states to something reasonable. I think we need to intergrate what I just read as a patch submission from Paul Tarina (I am going to do it as soon as I finish my mail reading and test it locally if some one has not already beaten me to it) as it cleans up all the bugs recently introduced, and adds at least one I spotted. Then a few more knobs need added to /etc/sysconfig so we can do things like enable the ``route add $hostname localhost'' in /etc/netstart without editing netstart itself, etc. I have written for Domain/OS a set of /etc/rc scripts that work well for that environment and they work similiarly to what we have now with the /etc/sysconfig being replaced by a node specific file that lives in /etc/daemons (a variant symbolic link). The environment on Domain/OS is about 10x more complicated than what FreeBSD has as it is a tri universe (Aegis, SYS5 and BSD4.3) OS, but the model works, and works very well. Having /etc/netstart usable from single user mode to pull you up on the network but not start up any servers is functionality we need to keep!! -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-bugs Wed Mar 29 02:09:10 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA29961 for bugs-outgoing; Wed, 29 Mar 1995 02:09:10 -0800 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id CAA29953; Wed, 29 Mar 1995 02:09:08 -0800 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: Paul Richards cc: pst@shockwave.com, freebsd-bugs@freefall.cdrom.com Subject: Re: Changed information for PR misc/278 In-reply-to: Your message of "Wed, 29 Mar 95 10:52:58 +0100." <199503290952.KAA18163@isl.cf.ac.uk> Date: Wed, 29 Mar 1995 02:09:08 -0800 Message-ID: <29952.796471748@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: bugs-owner@FreeBSD.org Precedence: bulk > > Synopsis: the echos in /etc/rc to start syscons have a couple of mistakes > > > > State-Changed-From-To: open-closed > > State-Changed-By: jkh > > State-Changed-When: Tue Mar 28 19:35:18 PST 1995 > > State-Changed-Why: > > Problem addressed. > > > > Cmon Jordan, lead by example and include proper log messages. I included a pointer to the PR it closed - there's LOTS of detail information in there! But, sigh, I'll duplicate it in its entirety from now on.. Jordan From owner-freebsd-bugs Wed Mar 29 02:10:46 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA00109 for bugs-outgoing; Wed, 29 Mar 1995 02:10:46 -0800 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id CAA29998; Wed, 29 Mar 1995 02:10:44 -0800 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: "Rodney W. Grimes" cc: bde@zeta.org.au, freebsd-bugs@freefall.cdrom.com, pst@shockwave.com Subject: Re: Changed information for PR misc/278 In-reply-to: Your message of "Wed, 29 Mar 95 02:03:15 PST." <199503291003.CAA01968@gndrsh.aac.dev.com> Date: Wed, 29 Mar 1995 02:10:43 -0800 Message-ID: <29997.796471843@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: bugs-owner@FreeBSD.org Precedence: bulk > I think we need to intergrate what I just read as a patch submission > from Paul Tarina (I am going to do it as soon as I finish my mail > reading and test it locally if some one has not already beaten me > to it) as it cleans up all the bugs recently introduced, and adds > at least one I spotted. That's fine with me. I was going to do that if nobody beat ME to it since I figure if we can't have neat, we might as well have functional and Paul's brings us back to that again. Jordan From owner-freebsd-bugs Wed Mar 29 02:18:16 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA00552 for bugs-outgoing; Wed, 29 Mar 1995 02:18:16 -0800 Received: from isl.cf.ac.uk (isl-gate.elsy.cf.ac.uk [131.251.22.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id CAA00524; Wed, 29 Mar 1995 02:18:12 -0800 Received: (from paul@localhost) by isl.cf.ac.uk (8.6.9/8.6.9) id LAA18400; Wed, 29 Mar 1995 11:18:23 +0100 From: Paul Richards Message-Id: <199503291018.LAA18400@isl.cf.ac.uk> Subject: Re: Changed information for PR misc/278 To: jkh@freefall.cdrom.com (Jordan K. Hubbard) Date: Wed, 29 Mar 1995 11:18:23 +0100 (BST) Cc: pst@shockwave.com, freebsd-bugs@freefall.cdrom.com In-Reply-To: <29952.796471748@freefall.cdrom.com> from "Jordan K. Hubbard" at Mar 29, 95 02:09:08 am X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1060 Sender: bugs-owner@FreeBSD.org Precedence: bulk In reply to Jordan K. Hubbard who said > > > > Synopsis: the echos in /etc/rc to start syscons have a couple of mistakes > > > > > > State-Changed-From-To: open-closed > > > State-Changed-By: jkh > > > State-Changed-When: Tue Mar 28 19:35:18 PST 1995 > > > State-Changed-Why: > > > Problem addressed. > > > > > > > Cmon Jordan, lead by example and include proper log messages. > > I included a pointer to the PR it closed - there's LOTS of detail Ehh? Are you feeling alright. Of course you supplied a pointer to the PR it closed, you're closing it! edit-pr did that automatically. There's no info *at all* about what you did to fix the problem. > information in there! But, sigh, I'll duplicate it in its entirety > from now on.. I'd prefer a reference to the cvs log rather than a duplicate of the fix. -- Paul Richards, FreeBSD core team member. Internet: paul@FreeBSD.org, URL: http://isl.cf.ac.uk/~paul/ Phone: +44 1222 874000 x6646 (work), +44 1222 457651 (home) Dept. Mechanical Engineering, University of Wales, College Cardiff. From owner-freebsd-bugs Wed Mar 29 02:20:14 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA01120 for bugs-outgoing; Wed, 29 Mar 1995 02:20:14 -0800 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 CAA01087; Wed, 29 Mar 1995 02:20:07 -0800 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.8/8.6.6) id CAA02077; Wed, 29 Mar 1995 02:19:56 -0800 From: "Rodney W. Grimes" Message-Id: <199503291019.CAA02077@gndrsh.aac.dev.com> Subject: Re: Changed information for PR misc/278 To: jkh@freefall.cdrom.com (Jordan K. Hubbard) Date: Wed, 29 Mar 1995 02:19:56 -0800 (PST) Cc: paul@isl.cf.ac.uk, pst@shockwave.com, freebsd-bugs@freefall.cdrom.com In-Reply-To: <29952.796471748@freefall.cdrom.com> from "Jordan K. Hubbard" at Mar 29, 95 02:09:08 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 869 Sender: bugs-owner@FreeBSD.org Precedence: bulk > > > > Synopsis: the echos in /etc/rc to start syscons have a couple of mistakes > > > > > > State-Changed-From-To: open-closed > > > State-Changed-By: jkh > > > State-Changed-When: Tue Mar 28 19:35:18 PST 1995 > > > State-Changed-Why: > > > Problem addressed. > > > > > > > Cmon Jordan, lead by example and include proper log messages. > > I included a pointer to the PR it closed - there's LOTS of detail > information in there! But, sigh, I'll duplicate it in its entirety > from now on.. Please, don't do that, all's you needed to do was say: Problem corrected by version 1.58 of /etc/rc. You managed to refer to the PR# in the commit, we just now need to start refering to the $Id$ in the edit-pr. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-bugs Wed Mar 29 02:26:32 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA03087 for bugs-outgoing; Wed, 29 Mar 1995 02:26:32 -0800 Received: from isl.cf.ac.uk (isl-gate.elsy.cf.ac.uk [131.251.22.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id CAA03049; Wed, 29 Mar 1995 02:26:23 -0800 Received: (from paul@localhost) by isl.cf.ac.uk (8.6.9/8.6.9) id LAA18458; Wed, 29 Mar 1995 11:25:59 +0100 From: Paul Richards Message-Id: <199503291025.LAA18458@isl.cf.ac.uk> Subject: Re: kern/280: new slice manager totally confused about old slice disks To: bde@zeta.org.au (Bruce Evans) Date: Wed, 29 Mar 1995 11:25:58 +0100 (BST) Cc: bde@zeta.org.au, gvrooij@mmra1.ms.philips.nl, freebsd-bugs@freefall.cdrom.com, jkh@freefall.cdrom.com, pst@shockwave.com In-Reply-To: <199503290933.TAA25301@godzilla.zeta.org.au> from "Bruce Evans" at Mar 29, 95 07:33:09 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1195 Sender: bugs-owner@FreeBSD.org Precedence: bulk In reply to Bruce Evans who said > > >> I think sysinstall creates a valid disk label with size > >> #secpertrack * #heads * #cyl in both the d_secperunit and the 'd' partition > >> size fields. The problem occurs when the sd driver blows away the 'd' > >> partition size field (replacing it with the total #sec) without touching > >> the d_secperunit field. The wd driver is more careful and verbose. It > > >Might well explain what we see indeed. But the same holds for the c partition. > > Maybe sysinstall set the size of the c partition correctly to extend to > the end of the disk, and d_secperunit to match. Old versions of > `disklabel -e' rounded down d_secperunit to a cylinder boundary so running > `disklabel -e' could cause the problem. I doubt sysinstall is doing anything right anymore. It certainly won't be setting the c partition to cover the whole disk. It's still setting d to cover the whole disk and c to the BSD slice. -- Paul Richards, FreeBSD core team member. Internet: paul@FreeBSD.org, URL: http://isl.cf.ac.uk/~paul/ Phone: +44 1222 874000 x6646 (work), +44 1222 457651 (home) Dept. Mechanical Engineering, University of Wales, College Cardiff. From owner-freebsd-bugs Wed Mar 29 02:43:41 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA09427 for bugs-outgoing; Wed, 29 Mar 1995 02:43:41 -0800 Received: from isl.cf.ac.uk (isl-gate.elsy.cf.ac.uk [131.251.22.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id CAA09366; Wed, 29 Mar 1995 02:43:33 -0800 Received: (from paul@localhost) by isl.cf.ac.uk (8.6.9/8.6.9) id LAA19868; Wed, 29 Mar 1995 11:43:32 +0100 From: Paul Richards Message-Id: <199503291043.LAA19868@isl.cf.ac.uk> Subject: Re: kern/280: new slice manager totally confused about old slice disks To: bde@zeta.org.au (Bruce Evans) Date: Wed, 29 Mar 1995 11:43:32 +0100 (BST) Cc: jkh@freefall.cdrom.com, root@Shockwave.COM, freebsd-bugs@freefall.cdrom.com In-Reply-To: <199503290712.RAA20923@godzilla.zeta.org.au> from "Bruce Evans" at Mar 29, 95 05:12:22 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1151 Sender: bugs-owner@FreeBSD.org Precedence: bulk In reply to Bruce Evans who said > > Disagreed. Aren't you going to tell everyone to reinstall like you did with > all previous releases? The new sysinstall won't make any invalid slices > or partitions ;-). We might have to *strenously* suggest that sysinstall be allowed to rewrite the MBR and disklabel. I'll think about this and I'm sure Poul will shout at me if I get it wrong :-) There's no reason why we can't read all the existing info off the disk and re-write correctly as part of the installation. We will obviously get a confirm from the user but if they override this we'll just tell them they're on their own and that it's not our fault if everything breaks. This should fix up the problem of previous MBR/disklabel formats we've been using without forcing a total re-install of the whole system. We'll have to get it absolutely spot on though or we'll toast their existing partitions. -- Paul Richards, FreeBSD core team member. Internet: paul@FreeBSD.org, URL: http://isl.cf.ac.uk/~paul/ Phone: +44 1222 874000 x6646 (work), +44 1222 457651 (home) Dept. Mechanical Engineering, University of Wales, College Cardiff. From owner-freebsd-bugs Wed Mar 29 05:00:03 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA17277 for bugs-outgoing; Wed, 29 Mar 1995 05:00:03 -0800 Received: from relay.philips.nl (relay.philips.nl [130.144.65.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA17258; Wed, 29 Mar 1995 04:59:59 -0800 Received: from muxgw1.ms.philips.nl ([130.144.90.6]) by relay.philips.nl (8.6.9/8.6.9-950103) with SMTP id OAA15283; Wed, 29 Mar 1995 14:58:05 +0200 Received: by muxgw1.ms.philips.nl (5.57/Ultrix2.4-C) id AA02765; Wed, 29 Mar 95 12:29:10 +0300 Received: by mmra1.ms.philips.nl (4.1/SMI-4.1) id AA29820; Wed, 29 Mar 95 12:43:58 +0200 From: gvrooij@mmra1.ms.philips.nl (Guido van Rooij) Message-Id: <9503291043.AA29820@mmra1.ms.philips.nl> Subject: Re: kern/280: new slice manager totally confused about old slice disks To: bde@zeta.org.au (Bruce Evans) Date: Wed, 29 Mar 1995 12:43:57 +0200 (MET DST) Cc: bde@zeta.org.au, freebsd-bugs@freefall.cdrom.com, jkh@freefall.cdrom.com, pst@shockwave.com In-Reply-To: <199503290933.TAA25301@godzilla.zeta.org.au> from "Bruce Evans" at Mar 29, 95 07:33:09 pm X-Mailer: ELM [version 2.4 PL21] Content-Type: text Content-Length: 667 Sender: bugs-owner@FreeBSD.org Precedence: bulk > > The c partition size is rounded down while the d partition is rejected. > These partitions are not used for normal operation (except maybe sector > #2 of partition c to read the label) so normal operation is not normally > affected. Similar rounding down of the a partition (e.g.) would cause That's a big relief. Pitty though that we'll get the warnings (pitty because we didnt screw up anything; we just followed 2.0R's sysinstall). > problems if the file system extends into the lost sectors. Most such > problems are avoided by specially handling the 50000-sector "whole > disk for FreeBSD" partition table. Eh? What's tyhe magic behind 50000? -Guido From owner-freebsd-bugs Wed Mar 29 05:53:16 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA18217 for bugs-outgoing; Wed, 29 Mar 1995 05:53:16 -0800 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 FAA18202; Wed, 29 Mar 1995 05:53:02 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id XAA01384; Wed, 29 Mar 1995 23:46:20 +1000 Date: Wed, 29 Mar 1995 23:46:20 +1000 From: Bruce Evans Message-Id: <199503291346.XAA01384@godzilla.zeta.org.au> To: bde@zeta.org.au, gvrooij@mmra1.ms.philips.nl Subject: Re: kern/280: new slice manager totally confused about old slice disks Cc: freebsd-bugs@freefall.cdrom.com, jkh@freefall.cdrom.com, pst@shockwave.com Sender: bugs-owner@FreeBSD.org Precedence: bulk >> problems if the file system extends into the lost sectors. Most such >> problems are avoided by specially handling the 50000-sector "whole >> disk for FreeBSD" partition table. >Eh? What's tyhe magic behind 50000? Either Julian or a Mach developer though of a number and put it in the boot block. This number is still with us 2.5 years later. Bruce From owner-freebsd-bugs Wed Mar 29 07:41:36 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA27621 for bugs-outgoing; Wed, 29 Mar 1995 07:41:36 -0800 Received: from mpp.com (dialup-2-151.gw.umn.edu [134.84.101.151]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id HAA27578 for ; Wed, 29 Mar 1995 07:41:30 -0800 Received: (from mpp@localhost) by mpp.com (8.6.11/8.6.9) id EAA00389; Wed, 29 Mar 1995 04:57:13 -0600 From: Mike Pritchard Message-Id: <199503291057.EAA00389@mpp.com> Subject: Re: kern/280: new slice manager totally confused about old slice disks To: bde@zeta.org.au (Bruce Evans) Date: Wed, 29 Mar 1995 04:57:12 -0600 (CST) Cc: freebsd-bugs@freefall.cdrom.com In-Reply-To: <199503290712.RAA20923@godzilla.zeta.org.au> from "Bruce Evans" at Mar 29, 95 05:12:22 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: 1696 Sender: bugs-owner@FreeBSD.org Precedence: bulk > > Subject: Re: kern/280: new slice manager totally confused about old slice dis > > Try copying the new MAKEDEV over and doing a ./MAKEDEV sd0, then try: > > > > mount -t msdos /dev/sd0s1 /dos > > > > Assuming, of course, that slice 1 is the DOS partition. This is > > Not a good assumption. There may be up to 26 DOS partitions starting > as late as slice s4 (primary partition #4, extended partition #3 > containing 25 more). Very few setups will have this, but the install > program has to be careful not to break it (if not support it), and > people answering bug reports should know about it. > OK, after finally seeing some mail mentioning that I needed to run the new MAKEDEV to create the /dev/sd#s# devices I was finally able to mount my MS-DOS paritition I have on my sd0 drive again . I still can't mount the two partitions I have on my sd1 disk. My sd1 disk is fdisked as follows: 500MB for DOS within this paritition are two extended/logical DOS partitions, which are my DOS D/E drives. 500MB for FreeBSD Before all of the slicing code I was able to create entries in my disk label with the correct start/end locations so I could mount the D/E DOS drives under FreeBSD. After running the new MAKEDEV and attempting to mount every /dev/{sd1*,sd1s*} device, I was unable to mount either paritition. An fdisk on /dev/sd1s1 shows an entry that would be the D/E logical DOS partitions. fdisk sd1s2 shows my FreeBSD paritition, which is what I would expect. So my question is, with the new slice code, how do I mount these two parititions again. -- Mike Pritchard pritc003@maroon.tc.umn.edu "Go that way. Really fast. If something gets in your way, turn" From owner-freebsd-bugs Wed Mar 29 07:50:03 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA04278 for bugs-outgoing; Wed, 29 Mar 1995 07:50:03 -0800 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA04266; Wed, 29 Mar 1995 07:50:03 -0800 Date: Wed, 29 Mar 1995 07:50:03 -0800 Message-Id: <199503291550.HAA04266@freefall.cdrom.com> From: pritc003@maroon.tc.umn.edu Reply-To: pritc003@maroon.tc.umn.edu To: freebsd-bugs Subject: kern/283: When using wall CMOS clock, MS-DOS file timestamps are off In-Reply-To: Your message of Wed, 29 Mar 1995 09:34:56 -0600 <199503291534.JAA00331@mpp.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 283 >Category: kern >Synopsis: When using wall CMOS clock, MS-DOS file timestamps are off >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 Mar 29 07:50:01 1995 >Originator: Mike Pritchard >Organization: Mike Pritchard >Release: FreeBSD 2.1.0-Development i386 >Environment: Using a wall CMOS clock. >Description: If you are using a wall CMOS clock as opposed to a UTC CMOS clock, the file timestamps on MS-DOS mounted file system are off by the amount of your timezone adjustment. >How-To-Repeat: Mount a MS-DOS file system while using a wall CMOS clock and do an "ls -l" on some file. Then boot MS-DOS and compare the timestamps. >Fix: The supplied patch fixes the problem, as well as optimizes the dos2unixtime() routine a to eliminate some needless loops in the code. The unix2dostime() routine could probably also be optimized a bit, but it probably only gets called 1/100th as much as the other routine so I didn't bother. This patch applies to the following revision of msdosfs_conv.c: /* $Id: msdosfs_conv.c,v 1.3 1994/12/12 12:35:42 bde Exp $ */ *** orig/msdosfs_conv.c Wed Mar 29 07:14:46 1995 --- ./msdosfs_conv.c Wed Mar 29 09:04:26 1995 *************** *** 24,29 **** --- 24,30 ---- #include #include /* defines tz */ #include /* defines tz */ + #include /* * MSDOSFS include files. *************** *** 31,49 **** #include /* ! * Days in each month in a regular year. */ u_short regyear[] = { ! 31, 28, 31, 30, 31, 30, ! 31, 31, 30, 31, 30, 31 }; /* ! * Days in each month in a leap year. */ u_short leapyear[] = { ! 31, 29, 31, 30, 31, 30, ! 31, 31, 30, 31, 30, 31 }; /* --- 32,50 ---- #include /* ! * Total number of days that have passed for each month in a regular year. */ u_short regyear[] = { ! 31, 59, 90, 120, 151, 181, ! 212, 243, 273, 304, 334, 365 }; /* ! * Total number of days that have passed for each month in a leap year. */ u_short leapyear[] = { ! 31, 60, 91, 121, 152, 182, ! 213, 244, 274, 305, 335, 366 }; /* *************** *** 76,82 **** * If the time from the last conversion is the same as now, then * skip the computations and use the saved result. */ ! t = tsp->ts_sec - (tz.tz_minuteswest * 60) /* +- daylight savings time correction */ ; if (lasttime != t) { lasttime = t; --- 77,83 ---- * If the time from the last conversion is the same as now, then * skip the computations and use the saved result. */ ! t = tsp->ts_sec - (tz.tz_minuteswest * 60) - adjkerntz; /* +- daylight savings time correction */ ; if (lasttime != t) { lasttime = t; *************** *** 99,109 **** days -= inc; } months = year & 0x03 ? regyear : leapyear; ! for (month = 0; month < 12; month++) { ! if (days < months[month]) ! break; ! days -= months[month]; ! } lastddate = ((days + 1) << DD_DAY_SHIFT) + ((month + 1) << DD_MONTH_SHIFT); /* --- 100,109 ---- days -= inc; } months = year & 0x03 ? regyear : leapyear; ! for (month = 0; days > months[month]; month++) ! ; ! if (month > 0) ! days -= months[month - 1]; lastddate = ((days + 1) << DD_DAY_SHIFT) + ((month + 1) << DD_MONTH_SHIFT); /* *************** *** 157,185 **** lastdosdate = dd; days = 0; year = (dd & DD_YEAR_MASK) >> DD_YEAR_SHIFT; ! for (y = 0; y < year; y++) { ! days += y & 0x03 ? 365 : 366; ! } months = year & 0x03 ? regyear : leapyear; - /* - * Prevent going from 0 to 0xffffffff in the following - * loop. - */ month = (dd & DD_MONTH_MASK) >> DD_MONTH_SHIFT; ! if (month == 0) { printf( "dos2unixtime(): month value out of range (%ld)\n", month); month = 1; } ! for (m = 0; m < month - 1; m++) { ! days += months[m]; ! } days += ((dd & DD_DAY_MASK) >> DD_DAY_SHIFT) - 1; lastseconds = (days * 24 * 60 * 60) + SECONDSTO1980; } tsp->ts_sec = seconds + lastseconds + (tz.tz_minuteswest * 60) ! /* -+ daylight savings time correction */ ; tsp->ts_nsec = 0; } --- 157,181 ---- lastdosdate = dd; days = 0; year = (dd & DD_YEAR_MASK) >> DD_YEAR_SHIFT; ! days = year * 365; ! days += year / 4 + 1; /* add in leap days */ ! if ((year & 0x03) == 0) ! days--; /* if year is a leap year */ months = year & 0x03 ? regyear : leapyear; month = (dd & DD_MONTH_MASK) >> DD_MONTH_SHIFT; ! if (month < 1 || month > 12) { printf( "dos2unixtime(): month value out of range (%ld)\n", month); month = 1; } ! if (month > 1) ! days += months[month - 2]; days += ((dd & DD_DAY_MASK) >> DD_DAY_SHIFT) - 1; lastseconds = (days * 24 * 60 * 60) + SECONDSTO1980; } tsp->ts_sec = seconds + lastseconds + (tz.tz_minuteswest * 60) ! + adjkerntz /* -+ daylight savings time correction */ ; tsp->ts_nsec = 0; } >Audit-Trail: >Unformatted: From owner-freebsd-bugs Wed Mar 29 08:38:19 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA19801 for bugs-outgoing; Wed, 29 Mar 1995 08:38:19 -0800 Received: from nic1.barrnet.net (NIC1.BARRNET.NET [131.119.245.5]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA19795; Wed, 29 Mar 1995 08:38:17 -0800 Received: from ipsilon.com by nic1.barrnet.net (8.6.10/BARRNET-RELAY.1) id IAA19187; Wed, 29 Mar 1995 08:38:04 -0800 Received: from [204.160.240.227] (green.ipsilon.COM) by ipsilon.com (4.1/SMI-4.1MDV1.0) id AA08398; Wed, 29 Mar 95 08:36:42 PST Date: Wed, 29 Mar 95 08:36:41 PST X-Sender: minshall@servo.ipsilon.com Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: pace@prep.ai.mit.edu, hassey@dg-rtp.dg.com, paul@freefall.cdrom.com, bugs@FreeBSD.org, roland@albert.gnu.ai.mit.edu From: minshall@ipsilon.com (Greg Minshall) Subject: GDB and Intelx86 and 16-bit code disassembly Sender: bugs-owner@FreeBSD.org Precedence: bulk Hi. I've been beating my head on some bug with boot blocks on the disk on my FreeBSD 2.0 system (it boots from NCR adapters, but hangs when i install BusLogic adapters -- any ideas?). As part of this, i've been using GDB to disassemble the 16-bit code that is found in these boot blocks. As the doc says, it doesn't actually work on 16-bit code. So, i hacked on it a bit. Below are changes that seemed to do as much 16-bit as *I* needed, but i didn't do an exhaustive search. I.e., i think these changes make things *much* better than current code, but i'm sure there are other things that will need to be changed to fully support 16-bit code. (If i had spent the time to understand GDB's command structures, i would have added commands like "set x86-16-bit-code" and "set x86-32-bit-code"...) Hope this is understandable. If anyone would like a different form of "diff" output, let me know. Greg Minshall ---- =================================================================== RCS file: RCS/i386-dis.c,v retrieving revision 1.1 diff -c -r1.1 i386-dis.c *** 1.1 1995/03/25 23:08:18 --- i386-dis.c 1995/03/26 03:11:27 *************** *** 702,707 **** --- 702,710 ---- static char *names_seg[] = { "%es","%cs","%ss","%ds","%fs","%gs","%?","%?", }; + static char *names_ea16bit[] = { + "%bx,%si","%bx,%di","%bp,%si","%bp,%di","%si","%di","%bp","%bx" + }; struct dis386 grps[][8] = { /* GRP1b */ *************** *** 949,954 **** --- 952,961 ---- } } + /* Initialization values - suitable for tweaking (0 --> 16 bit mode) */ + static int Dflag = 1; + static int Aflag = 1; + static int dflag; static int aflag; *************** *** 1025,1032 **** } /* these would be initialized to 0 if disassembling for 8086 or 286 */ ! dflag = 1; ! aflag = 1; if (prefixes & PREFIX_DATA) dflag ^= 1; --- 1032,1039 ---- } /* these would be initialized to 0 if disassembling for 8086 or 286 */ ! dflag = Dflag; ! aflag = Aflag; if (prefixes & PREFIX_DATA) dflag ^= 1; *************** *** 1034,1040 **** if (prefixes & PREFIX_ADR) { aflag ^= 1; ! oappend ("addr16 "); } if (*codep == 0x0f) --- 1041,1051 ---- if (prefixes & PREFIX_ADR) { aflag ^= 1; ! if (Aflag) { ! oappend ("addr16 "); ! } else { ! oappend("addr32 "); ! } } if (*codep == 0x0f) *************** *** 1532,1538 **** } append_prefix (); ! if (rm == 4) { havesib = 1; havebase = 1; --- 1543,1549 ---- } append_prefix (); ! if (dflag && (rm == 4)) /* In 32-bit mode, rm 4 ==> SIB byte */ { havesib = 1; havebase = 1; *************** *** 1546,1581 **** switch (mod) { case 0: ! switch (rm) ! { ! case 4: ! /* implies havesib and havebase */ ! if (base == 5) { ! havebase = 0; ! disp = get32 (); ! } ! break; ! case 5: ! disp = get32 (); ! break; ! default: ! havebase = 1; ! base = rm; ! break; ! } break; case 1: FETCH_DATA (the_info, codep + 1); disp = *(char *)codep++; ! if (rm != 4) { havebase = 1; base = rm; } break; case 2: ! disp = get32 (); ! if (rm != 4) { havebase = 1; base = rm; --- 1557,1590 ---- switch (mod) { case 0: ! if ((rm == 4) && dflag && (base == 5)) { ! /* implies havesib and havebase */ ! havebase = 0; /* mod 0 and SIB base 5 ==> disp32, no base */ ! disp = get32 (); ! } else if ((rm == 5) && dflag) { ! disp = get32 (); /* disp32 */ ! } else if ((rm == 6) && !dflag) { ! disp = get16 (); /* disp16 */ ! } else { ! havebase = 1; ! base = rm; ! } break; case 1: FETCH_DATA (the_info, codep + 1); disp = *(char *)codep++; ! if ((dflag == 0) || (rm != 4)) { havebase = 1; base = rm; } break; case 2: ! if (dflag) ! disp = get32 (); ! else ! disp = get16 (); ! if ((dflag == 0) || (rm != 4)) { havebase = 1; base = rm; *************** *** 1583,1589 **** break; } ! if (mod != 0 || rm == 5 || (havesib && base == 5)) { sprintf (scratchbuf, "0x%x", disp); oappend (scratchbuf); --- 1592,1601 ---- break; } ! if (mod != 0 || ! (dflag && (rm == 5)) || /* 32-bit mode ==> mod 0, rm 5 */ ! (!dflag && (rm == 6)) || /* 32-bit mode ==> mod 0, rm 6 */ ! (havesib && base == 5)) { sprintf (scratchbuf, "0x%x", disp); oappend (scratchbuf); *************** *** 1592,1599 **** if (havebase || havesib) { oappend ("("); ! if (havebase) ! oappend (names32[base]); if (havesib) { if (index != 4) --- 1604,1615 ---- if (havebase || havesib) { oappend ("("); ! if (havebase) { ! if (dflag) ! oappend (names32[base]); ! else ! oappend (names_ea16bit[base]); ! } if (havesib) { if (index != 4) *************** *** 1823,1829 **** switch (size) { case lptr: ! if (aflag) { offset = get32 (); seg = get16 (); --- 1839,1845 ---- switch (size) { case lptr: ! if (dflag) /* depending on operand size (not address) */ { offset = get32 (); seg = get16 (); From owner-freebsd-bugs Wed Mar 29 08:57:10 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA21871 for bugs-outgoing; Wed, 29 Mar 1995 08:57:10 -0800 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 IAA21865; Wed, 29 Mar 1995 08:57:06 -0800 Received: by halloran-eldar.lcs.mit.edu; id AA14584; Wed, 29 Mar 1995 11:56:56 -0500 Date: Wed, 29 Mar 1995 11:56:56 -0500 From: Garrett Wollman Message-Id: <9503291656.AA14584@halloran-eldar.lcs.mit.edu> To: "Jordan K. Hubbard" Cc: freebsd-bugs@freefall.cdrom.com Subject: Re: Changed information for PR misc/278 In-Reply-To: <12916.796469126@freefall.cdrom.com> References: <199503290530.PAA18058@godzilla.zeta.org.au> <12916.796469126@freefall.cdrom.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk < said: > Sigh.. I think it must be said: Most of /etc is a mess, it always has > been a mess and all I've ever seen other operating systems do with it > is make it a more *convoluted* mess (SVR4 - gag me!). What's the > cool, killer paradigm shift we're missing here? :-) Well, I like what Paul has done with the RC files. As for configuration, I have had a dream occasionally that we could have a completely integrated, text-file-based, configuration database system with a different sort of naming concept. The idea was as follows: 1) Configuration specifications are hierarchical, named along the same lines as sysctl(8) MIB variables: net.inetd.conf, disk.quotas.enabled, config.lkm.autoload, passwd.userclass.grimblepritz.expiretime, etc. 2) Configuration information is stored in files with multiple sections, or in directories, or both. So, disk.quotas.enabled might be stored in a file called ${CONFIG_ROOT}/config, or /disk, or /disk/config, or /disk/quotas, or /disk/quotas/config. 3) Database schema information is integrated with the configuration information, so that for every section (like disk.quotas), there is also a schema.disk.quotas section, with entries like `entries' and `entry.description' and `entry.type'. 4) A search path for configuration information, so that site-wide defaults with local overrides can be established easily. (Default /etc/config:/usr/share/config.) 5) A central libconfig to make this all work, and user applications to edit it in a reasonable way. No, I don't plan on implementing it. But it would be nice. -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 Wed Mar 29 09:01:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA21958 for bugs-outgoing; Wed, 29 Mar 1995 09:01:02 -0800 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 JAA21952; Wed, 29 Mar 1995 09:00:58 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA19490; Wed, 29 Mar 95 09:54:33 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9503291654.AA19490@cs.weber.edu> Subject: Re: Changed information for PR misc/278 To: jkh@freefall.cdrom.com (Jordan K. Hubbard) Date: Wed, 29 Mar 95 9:54:32 MST Cc: bde@zeta.org.au, freebsd-bugs@freefall.cdrom.com, pst@shockwave.com In-Reply-To: <12916.796469126@freefall.cdrom.com> from "Jordan K. Hubbard" at Mar 29, 95 01:25:26 am X-Mailer: ELM [version 2.4dev PL52] Sender: bugs-owner@FreeBSD.org Precedence: bulk > Well, it also seems to be something of a sacred cow around here and I > got flamed when I tried to significantly alter it. I've really no > immediate idea as to how to restructure the thing, and there's a lot > to be said for adding a `NETWORKED=[yes|no]' that possibly even turns > most of this stuff OFF for situations where the machine *isn't even on > a network and never will be*. Has anyone stopped to consider this > case? We've always just barreled along and never even really given > the user the opportunity to easily deselect what might be an entirely > gratuitous set of daemons.. > > Sigh.. I think it must be said: Most of /etc is a mess, it always has > been a mess and all I've ever seen other operating systems do with it > is make it a more *convoluted* mess (SVR4 - gag me!). What's the > cool, killer paradigm shift we're missing here? :-) Well, let me take a stab at attracting flames here.... 8-). % cd /etc % pseudogrep netstart rc ... # Uncomment the following line if you are on a network. This replaces # the old /etc/netstart. This really should be conditional on the # contents of a configuration file that gets sourced by rc. # /etc/rc.net start # start networking ... % pseudocat rc.net ... # Save argument ACTION=$1 # The following environment variable refers to the file that is set # up by the configuration management tools during install and which # can be modified by rerunning them (TBD). # NETCONF=/var/etc/netconfig # # The $NETCONFIG file is a file that sets environment variables and # does nothing else. These environment variable can have 'YES' or 'NO' # for various network options. We import them to tell rc.net how to # behave. # . $NETCONF # # Because the tools exist (TBD) to allow us to reconfigure the network # on the host while the machine is up (if we use a local terminal), or # to reconfigure the machine and have the changes take effect next # reboot (for a non-local administrator, we have to be able to start, # stop, and restart the commands in this file at will. So we provide # a "start" and a "stop" entry point. # # -- HANDLE START ------------------------------------------------ if test "$1" = "start" then echo "NETWORK: starting up" ... echo "NETWORK: startup complete" exit 0 fi # -- HANDLE STOP ------------------------------------------------- if test "$1" = "stop" then echo "NETWORK: shutting down" ... echo "NETWORK: shutdown complete" exit 0 fi # -- DEFAULT ACTION ---------------------------------------------- echo "usage: /etc/rc.net [start|stop]" exit 1 The basic idea is to cannonize the name ("netstart" is a stupid name in that it doesn't fit with where and how this thing is to be run), provide a mechanism for abstracting the procedure from the system configuration so the scripts can be shared between multiple hosts via network mount, and provide the capability of modifying the configuration using system management tools (which admittedly don't exist yet). The tools management procedure would be: 1) copy the current configuration to a work location 2) edit the work copy 3) decide to make it the active copy 4) shut down the net 5) move the work copy to the current configuration 6) start the net 7) the system runs with the new configuration The offline (remote management) procedure would be: 1) copy the current configuration to a work location 2) edit the work copy 3) decide to make it the active copy 4) move the work copy to a "shutdown install" directory 5) shut the system down 6) last act of shutdown is to move "shutdown install" directory contents to the current configuration locations 7) system reboots using new configuration Of course, you could launch a daemon to do the tools management procedure steps 4, 5, and 6 in a non-network dependent way. This would be more difficult, but more elegant. Because this is data driven, it also lends itself to remote management via snmp agent. 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 Mar 29 09:53:32 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA23160 for bugs-outgoing; Wed, 29 Mar 1995 09:53:32 -0800 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 JAA23136 for ; Wed, 29 Mar 1995 09:52:44 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA26540; Wed, 29 Mar 1995 19:24:46 +0200 Received: by sax.sax.de (8.6.9/8.6.9-s1) with UUCP id TAA08350 for freebsd-bugs@FreeBSD.org; Wed, 29 Mar 1995 19:24:45 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id TAA27644 for freebsd-bugs@FreeBSD.org; Wed, 29 Mar 1995 19:20:24 +0200 From: J Wunsch Message-Id: <199503291720.TAA27644@uriah.heep.sax.de> Subject: Re: kern/280: new slice manager totally confused about old slice disks To: freebsd-bugs@FreeBSD.org (FreeBSD bugs list) Date: Wed, 29 Mar 1995 19:20:23 +0200 (MET DST) In-Reply-To: <199503290843.SAA23221@godzilla.zeta.org.au> from "Bruce Evans" at Mar 29, 95 06:43:47 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 641 Sender: bugs-owner@FreeBSD.org Precedence: bulk As Bruce Evans wrote: > > I think sysinstall creates a valid disk label with size > #secpertrack * #heads * #cyl in both the d_secperunit and the 'd' partition > size fields. It did, but at least until before the last slice changes have been commited, disklabel complained about d_secperunit being less than the actual unit size. I had to correct this value manually to even get a new bootstrap installed. (There's an open bug report for it. Sysinstall should enter the right values, IMHO.) -- 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 Wed Mar 29 10:40:06 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA24795 for bugs-outgoing; Wed, 29 Mar 1995 10:40:06 -0800 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA24785; Wed, 29 Mar 1995 10:40:04 -0800 Date: Wed, 29 Mar 1995 10:40:04 -0800 Message-Id: <199503291840.KAA24785@freefall.cdrom.com> From: Lucas James Reply-To: Lucas James To: freebsd-bugs Subject: kern/284: Network seems to be funny In-Reply-To: Your message of Wed, 29 Mar 1995 22:03:22 +0930 <199503291233.WAA01015@ldjpc.apana.org.au> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 284 >Category: kern >Synopsis: Network gives permission denied >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 Mar 29 10:40:02 1995 >Originator: Lucas James >Organization: -- >Release: FreeBSD 2.1.0-Development i386 >Environment: >Description: after a reboot: Telnet to the local machine gives permission denied (even as root) kerberos doesn't work. innd doesn't work et.al. (a telnet to the nntp port also give permission denied.) >How-To-Repeat: jj@ldjpc> telnet ldjpc Trying 192.203.213.254... telnet: Unable to connect to remote host: Permission denied jj@ldjpc> telnet ldjpc nntp Trying 192.203.213.254... telnet: Unable to connect to remote host: Permission denied jj@ldjpc> su su: kerberos: unable to su: Retry count exceeded (send_to_kdc) Password: root@ldjpc# telnet ldjpc nntp Trying 192.203.213.254... telnet: Unable to connect to remote host: Permission denied root@ldjpc# >Fix: ???/ >Audit-Trail: >Unformatted: From owner-freebsd-bugs Wed Mar 29 10:48:47 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA25594 for bugs-outgoing; Wed, 29 Mar 1995 10:48:47 -0800 Received: (from ache@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA25578; Wed, 29 Mar 1995 10:48:45 -0800 Date: Wed, 29 Mar 1995 10:48:45 -0800 From: "Andrey A. Chernov" Message-Id: <199503291848.KAA25578@freefall.cdrom.com> To: pritc003@maroon.tc.umn.edu, ache, freebsd-bugs Subject: Changed information for PR kern/283 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: When using wall CMOS clock, MS-DOS file timestamps are off State-Changed-From-To: open-closed State-Changed-By: ache State-Changed-When: Wed Mar 29 10:48:15 PST 1995 State-Changed-Why: Fix applied. From owner-freebsd-bugs Wed Mar 29 12:39:06 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA28449 for bugs-outgoing; Wed, 29 Mar 1995 12:39:06 -0800 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 MAA28443 for ; Wed, 29 Mar 1995 12:38:57 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id GAA12906; Thu, 30 Mar 1995 06:38:03 +1000 Date: Thu, 30 Mar 1995 06:38:03 +1000 From: Bruce Evans Message-Id: <199503292038.GAA12906@godzilla.zeta.org.au> To: bde@zeta.org.au, pritc003@maroon.tc.umn.edu Subject: Re: kern/280: new slice manager totally confused about old slice disks Cc: freebsd-bugs@freefall.cdrom.com Sender: bugs-owner@FreeBSD.org Precedence: bulk >500MB for DOS > within this paritition are two extended/logical DOS partitions, > which are my DOS D/E drives. >500MB for FreeBSD >Before all of the slicing code I was able to create entries in my disk >label with the correct start/end locations so I could mount the D/E >DOS drives under FreeBSD. >After running the new MAKEDEV and attempting to mount every /dev/{sd1*,sd1s*} >device, I was unable to mount either paritition. An fdisk on /dev/sd1s1 >shows an entry that would be the D/E logical DOS partitions. fdisk sd1s2 >shows my FreeBSD paritition, which is what I would expect. >So my question is, with the new slice code, how do I mount these >two parititions again. Read the boot messages to see what the slice numbers of the extended/ logical partitions might be. Run MAKEDEV to create these slices if necessary. `sh MAKEDEV all' only creates some devices for slices s1-s4. Extended/logical partitions are on slices s5-s30. Bruce From owner-freebsd-bugs Wed Mar 29 14:28:58 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA03628 for bugs-outgoing; Wed, 29 Mar 1995 14:28:58 -0800 Received: from munich.gcomm.com (munich.gcomm.com [199.227.15.15]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA03622 for ; Wed, 29 Mar 1995 14:28:57 -0800 Received: (from mahesh@localhost) by munich.gcomm.com (8.6.8.1/8.6.6) id RAA01123 for bugs@freebsd.org; Wed, 29 Mar 1995 17:30:30 -0500 From: Mahesh Neelakanta Message-Id: <199503292230.RAA01123@munich.gcomm.com> Subject: March 22nd, 1995 snapshot of FreeBSD To: bugs@FreeBSD.org Date: Wed, 29 Mar 1995 17:30:30 -0500 (EST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 968 Sender: bugs-owner@FreeBSD.org Precedence: bulk Here are some things I found: 1) After installing, there was no /var/tmp 2) After installing, there was no /var/spool or /var/spool/mqueue 3) I had to add -I/usr/include and -I/usr/include/sys to get the kernel to compile. Also, If I enable the vt100 (pcvt?) console code, the kernel fails to compile. I can get the log for this if you want. 4) The intel-etherexpress dos config program does not allow the express to be at io base 0x280 but this is what the default kernel is compiled for. If you folks can change this to 0x300 or 0x310, that would be good. 5) TCP/IP transmission was slow on a 3com etherlink 3 (~12kbytes/sec) but works well on the etherexpress 6) The installation program allows ESC to shell out but this is not written anywhere on the screen (i.e. there should be a F1=HELP, ESC=SHELL) Overall, it's very sturdy. The installation went very well and I love the colorful installation program. Good job guys! mahesh@gcomm.com From owner-freebsd-bugs Wed Mar 29 16:24:55 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA08132 for bugs-outgoing; Wed, 29 Mar 1995 16:24:55 -0800 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 QAA08126 for ; Wed, 29 Mar 1995 16:24:52 -0800 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.8/8.6.6) id QAA03981; Wed, 29 Mar 1995 16:24:28 -0800 From: "Rodney W. Grimes" Message-Id: <199503300024.QAA03981@gndrsh.aac.dev.com> Subject: Re: March 22nd, 1995 snapshot of FreeBSD To: mahesh@munich.gcomm.com (Mahesh Neelakanta) Date: Wed, 29 Mar 1995 16:24:28 -0800 (PST) Cc: bugs@FreeBSD.org In-Reply-To: <199503292230.RAA01123@munich.gcomm.com> from "Mahesh Neelakanta" at Mar 29, 95 05:30:30 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1826 Sender: bugs-owner@FreeBSD.org Precedence: bulk > > Here are some things I found: > > 1) After installing, there was no /var/tmp > 2) After installing, there was no /var/spool or /var/spool/mqueue > 3) I had to add -I/usr/include and -I/usr/include/sys to get the kernel > to compile. Also, If I enable the vt100 (pcvt?) console code, the > kernel fails to compile. I can get the log for this if you want. As to the first one, you need to have /usr/src/include as well as /usr/src/sys to compile a kernel. This issue is currently being discussed. What you did is a reasonable work around until a final solution is found. > 4) The intel-etherexpress dos config program does not allow the express to > be at io base 0x280 but this is what the default kernel is compiled for. > If you folks can change this to 0x300 or 0x310, that would be good. Ooopss... that way my fault, it has been corrected. Thanks for the report! > 5) TCP/IP transmission was slow on a 3com etherlink 3 (~12kbytes/sec) > but works well on the etherexpress I don't know anything about the 3com problem, but am glad to here the EtherExpress driver is up and running and working ``well'' for you. If you notice any console messages from it could you cut and paste them and send me a copy (or just send it to the bugs list). There are some debug messages still in it and I need to know if people are hitting them. > > 6) The installation program allows ESC to shell out but this is not > written anywhere on the screen (i.e. there should be a F1=HELP, ESC=SHELL) > > Overall, it's very sturdy. The installation went very well and I love the > colorful installation program. Good job guys! > > mahesh@gcomm.com > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-bugs Thu Mar 30 06:00:03 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA27511 for bugs-outgoing; Thu, 30 Mar 1995 06:00:03 -0800 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA27504; Thu, 30 Mar 1995 06:00:02 -0800 Date: Thu, 30 Mar 1995 06:00:02 -0800 Message-Id: <199503301400.GAA27504@freefall.cdrom.com> From: Alan Judge Reply-To: Alan Judge To: freebsd-bugs Subject: gnu/285: ld.so problem with -lg++ in 2.0-950322-SNAP In-Reply-To: Your message of Thu, 30 Mar 1995 14:55:14 +0100 <199503301355.OAA07281@hogthrob.dsg.cs.tcd.ie> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 285 >Category: gnu >Synopsis: ld.so problem with -lg++ >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Mar 30 06:00:01 1995 >Originator: Alan Judge >Organization: Trinity College Dublin >Release: FreeBSD 2.1.0-Development i386 (2.0-950322-SNAP) >Environment: >Description: It doesn't appear possible to dynamically link any program with -lg++. This is new in 950322. Everything works fine in 950210. >How-To-Repeat: Given a small C++ program like: extern "C" { extern int getpid(); extern int printf(...); } main() { int i = getpid(); printf("%d\n", i); } $ gcc test.cc $ ldd a.out a.out: -lc.2 => /usr/lib/libc.so.2.0 (0x801a000) $ a.out 7087 $ gcc test.cc -lg++ $ ldd a.out a.out: -lg++.2 => /usr/lib/libg++.so.2.0 (0x801a000) -lc.2 => /usr/lib/libc.so.2.0 (0x807d000) -lcurses.2 => /usr/lib/libcurses.so.2.0 (0x80e1000) -ltermcap.2 => /usr/lib/libtermcap.so.2.0 (0x80ed000) $ a.out ld.so failed The program works fine with -static. In fact, any C or C++ program would appear to provoke the problem. Given: main() {} You get the same problem: $ gcc test.c $ a.out $ gcc test.c -lg++ $ a.out ld.so failed Copying libg++.so and libcompat.so from a 950210 machine doesn't help, so I guess it must be some new problem in the linker/runtime loader. >Fix: Unknown. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Thu Mar 30 15:29:36 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA02008 for bugs-outgoing; Thu, 30 Mar 1995 15:29:36 -0800 Received: (from jkh@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA01992; Thu, 30 Mar 1995 15:29:34 -0800 Date: Thu, 30 Mar 1995 15:29:34 -0800 From: "Jordan K. Hubbard" Message-Id: <199503302329.PAA01992@freefall.cdrom.com> To: dave@prlng.co.uk, jkh, freebsd-bugs Subject: Changed information for PR gnu/240 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: gdb does not correctly find the stack in a core dump State-Changed-From-To: open-closed State-Changed-By: jkh State-Changed-When: Thu Mar 30 15:29:18 PST 1995 State-Changed-Why: Gary Jennejohn reports that the bug has been fixed in -current. From owner-freebsd-bugs Thu Mar 30 17:20:03 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA07830 for bugs-outgoing; Thu, 30 Mar 1995 17:20:03 -0800 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA07820; Thu, 30 Mar 1995 17:20:02 -0800 Date: Thu, 30 Mar 1995 17:20:02 -0800 Message-Id: <199503310120.RAA07820@freefall.cdrom.com> From: Craig Huckabee Reply-To: Craig Huckabee To: freebsd-bugs Subject: conf/286: PR on Kernel building in 2.0-950322-SNAP In-Reply-To: Your message of Thu, 30 Mar 95 20:16:09 -0500 <9503310116.AA00554@slartibartfast.nosc.mil> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 286 >Category: conf >Synopsis: 'make depend' on GENERIC kernel stops >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Mar 30 17:20:01 1995 >Originator: Craig Huckabee >Organization: NISE East Charleston, SC >Release: FreeBSD 2.1.0-Development i386 >Environment: >Description: When trying to build a new kernel on a new machine, one that has just completed the automated install and has been rebooted, the 'make' or 'make depend' of a new configuration fails. What follows is the error message : Script started on Thu Mar 30 19:54:56 1995 mispwoso# make depend cc -c -O -W -Wreturn-type -Wcomment -Wredundant-decls -nostdinc -I. -I../.. -I../../sys -I../../../include -DGENERICA -DI486_CPU -DXSERVER -DUCONSOLE -DBOUNCE_BUFFERS -DSCSI_DELAY=15 -DCOMPAT_43 -DPROCFS -DCD9660 -DMSDOSFS -DNFS -DFFS -DINET -DKERNEL -Di386 -DLOAD_ADDRESS=0xF0100000 -DTIMEZONE=0 -DDST=0 -DMAXUSERS=10 -UKERNEL ../../i386/i386/genassym.c In file included from ../../i386/i386/genassym.c:40: ../../../include/stdio.h:43: sys/types.h: No such file or directory ../../../include/stdio.h:46: sys/cdefs.h: No such file or directory ../../i386/i386/genassym.c:41: sys/param.h: No such file or directory ../../i386/i386/genassym.c:42: sys/buf.h: No such file or directory ../../i386/i386/genassym.c:43: sys/proc.h: No such file or directory ../../i386/i386/genassym.c:50: sys/mount.h: No such file or directory ../../i386/i386/genassym.c:52: sys/mbuf.h: No such file or directory ../../i386/i386/genassym.c:53: sys/msgbuf.h: No such file or directory In file included from ./machine/cpu.h:46, from ../../i386/i386/genassym.c:54: ./machine/frame.h:43: sys/signal.h: No such file or directory ../../i386/i386/genassym.c:59: sys/syscall.h: No such file or directory In file included from ../../i386/i386/genassym.c:60: ../../vm/vm.h:60: sys/vmmeter.h: No such file or directory ../../vm/vm.h:61: sys/queue.h: No such file or directory In file included from ../../vm/vm.h:62, from ../../i386/i386/genassym.c:60: ./machine/cpufunc.h:43: sys/cdefs.h: No such file or directory ./machine/cpufunc.h:44: sys/types.h: No such file or directory ../../i386/i386/genassym.c:61: sys/user.h: No such file or directory In file included from ../../i386/i386/genassym.c:62: ../../net/if.h:65: sys/socket.h: No such file or directory ../../net/if.h:68: sys/time.h: No such file or directory In file included from ../../net/if.h:343, from ../../i386/i386/genassym.c:62: ../../net/if_arp.h:40: sys/socket.h: No such file or directory *** Error code 1 Stop. I have installed everything from the install program, using FTP, at least 4 times now, but each time it fails with the above problem. >How-To-Repeat: do a 'make depend' on any configuration file. >Fix: Alter Makefile.i386 somehow? >Audit-Trail: >Unformatted: From owner-freebsd-bugs Thu Mar 30 19:19:27 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA10923 for bugs-outgoing; Thu, 30 Mar 1995 19:19:27 -0800 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id TAA10915; Thu, 30 Mar 1995 19:19:24 -0800 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: Garrett Wollman cc: freebsd-bugs@freefall.cdrom.com Subject: Re: Changed information for PR misc/278 In-reply-to: Your message of "Wed, 29 Mar 95 11:56:56 EST." <9503291656.AA14584@halloran-eldar.lcs.mit.edu> Date: Thu, 30 Mar 1995 19:19:23 -0800 Message-ID: <10914.796619963@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: bugs-owner@FreeBSD.org Precedence: bulk > 1) Configuration specifications are hierarchical, named along the same > lines as sysctl(8) MIB variables: net.inetd.conf, disk.quotas.enabled, > config.lkm.autoload, passwd.userclass.grimblepritz.expiretime, etc. We can't do something like this! It makes too much sense! :-) > 2) Configuration information is stored in files with multiple > sections, or in directories, or both. So, disk.quotas.enabled might I'd prefer sections in one directory - /lots/of/directory/levels/make/me/crazy. > 3) Database schema information is integrated with the configuration > information, so that for every section (like disk.quotas), there is > also a schema.disk.quotas section, with entries like `entries' and > `entry.description' and `entry.type'. Hmmm. Or you could go with a "property" model where each foo.bar.baz atom had a list of properties. Syntax might be something like: config.lkm.autoload[value] = yes config.lkm.autoload[description_long] = "This option determines whether or not Loadable Kernel Modules (LKMs) are loaded on-demand as needed, without user intervention" config.lkm.autoload[description_short] = "Enable auto-loading of LKMs" config.lkm.autoload[default] = yes And so forth. Then I just query some known atoms for known property values and I get all the information I need. If you want to add field checking, you can even define "mask" and "checkfunc" properties for an arbitrary field. Extend the whole thing as you go along and RIGOROUSLY DOCUMENT the name of every special atom and reasonably generic property name. There you go. > 4) A search path for configuration information, so that site-wide > defaults with local overrides can be established easily. (Default > /etc/config:/usr/share/config.) Most surely. You could even make it: /etc/config:/usr/share/config:$HOME/.sys-config So that even those few user-specific parameters (MANPATH, ldconfig info, etc) can be set with the same scheme. > 5) A central libconfig to make this all work, and user applications to > edit it in a reasonable way. Yep. > No, I don't plan on implementing it. But it would be nice. Damn. And I was liking it, too, until we got to this caveat.. :-) Seriously, this would be a really interesting project - a chance to rip BSD's hoary configuration management screaming out by the roots and replace it with something MUCH nicer. Surely there is some insane person out there? Maybe even two? Come on out, you two! We won't bite! [much] :-) Jordan From owner-freebsd-bugs Thu Mar 30 19:30:08 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA11140 for bugs-outgoing; Thu, 30 Mar 1995 19:30:08 -0800 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA11132; Thu, 30 Mar 1995 19:30:04 -0800 Date: Thu, 30 Mar 1995 19:30:04 -0800 Message-Id: <199503310330.TAA11132@freefall.cdrom.com> From: J Wunsch Reply-To: J Wunsch To: freebsd-bugs Subject: kern/287: Iconsistent header files In-Reply-To: Your message of Fri, 31 Mar 1995 05:03:27 +0200 <199503310303.FAA05509@uriah.heep.sax.de> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 287 >Category: kern >Synopsis: Several header files are not consistent >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Mar 30 19:30:02 1995 >Originator: Joerg Wunsch >Organization: >Release: FreeBSD 2.1.0-Development i386 >Environment: 950322 SNAP >Description: The following inconsistencies have been reported by Mahesh Neelakanta When making a kernel with pcvt enabled, he got those errors/warnings: In file included from ../../i386/isa/pcvt/pcvt_hdr.h:78, from ../../i386/isa/pcvt/pcvt_drv.c:81: ../../../include/malloc.h:2: warning: #warning "this file includes which is obsoleted, use instead" In file included from ../../../include/malloc.h:5, from ../../i386/isa/pcvt/pcvt_hdr.h:78, from ../../i386/isa/pcvt/pcvt_drv.c:81: ../../../include/stdlib.h:170: conflicting types for `random' ../../../include/sys/libkern.h:56: previous declaration of `random' ../../../include/stdlib.h:170: warning: redundant redeclaration of `random' in same scope ../../../include/sys/libkern.h:56: warning: previous declaration of `random' In file included from ../../i386/isa/pcvt/pcvt_hdr.h:79, from ../../i386/isa/pcvt/pcvt_drv.c:81: ../../../include/time.h:101: `time' redeclared as different kind of symbol ../../../include/sys/kernel.h:59: previous declaration of `time' *** Error code 1 Sometimes even the wrong headers are being picked (malloc.h). Sometimes we simply need to be consistent. >How-To-Repeat: >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Thu Mar 30 20:43:36 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA12737 for bugs-outgoing; Thu, 30 Mar 1995 20:43:36 -0800 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 UAA12731 for ; Thu, 30 Mar 1995 20:43:36 -0800 Received: (hlew@localhost) by vegemite.Stanford.EDU (8.6.10/8.6.4) id UAA15708; Thu, 30 Mar 1995 20:43:32 -0800 Date: Thu, 30 Mar 1995 20:43:30 -0800 (PST) From: Howard Lew To: Brian Litzinger cc: bugs@FreeBSD.org Subject: passwd broken in new snap??? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@FreeBSD.org Precedence: bulk On Thu, 30 Mar 1995, Brian Litzinger wrote: > > > : I upgraded to 950322 SNAP from 950210 SNAP, and ever since I can't use > > > : "passwd". (I didn't do a "full re-install", I just unpacked the bin/* > > make passwd setuid to root. > chown root passwd > chmod 4555 passwd (I think) > Yep, I tried it and that doesn't fix it. Here's a log of what I did: paradise: {5} chown root passwd paradise: {6} passwd passwd: /etc/master.passwd: Permission denied paradise: {7} chmod 4555 passwd paradise: {8} passwd passwd: /etc/master.passwd: Permission denied paradise: {9} ls -al *passwd* -rw------- 1 root wheel 1182 Mar 26 20:01 master.passwd -r-sr-xr-x 1 root wheel 933 Mar 26 20:01 passwd paradise: {10} Okay, no can do, so changed it back to the way it was: paradise: {17} ls -al *passwd* -rw------- 1 root wheel 1182 Mar 26 20:01 master.passwd -rw-r--r-- 1 root wheel 933 Mar 26 20:01 passwd paradise: {18} passwd passwd: /etc/master.passwd: Permission denied paradise: {19} Any ideas? I think passwd is broken in the new snap release. I'll try the passwd command from the older snap and see if that fixes the problem. From owner-freebsd-bugs Thu Mar 30 21:37:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA13440 for bugs-outgoing; Thu, 30 Mar 1995 21:37:02 -0800 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 VAA13421 for ; Thu, 30 Mar 1995 21:36:59 -0800 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.8/8.6.6) id VAA07667; Thu, 30 Mar 1995 21:36:40 -0800 From: "Rodney W. Grimes" Message-Id: <199503310536.VAA07667@gndrsh.aac.dev.com> Subject: Re: passwd broken in new snap??? To: hlew@genome.Stanford.EDU (Howard Lew) Date: Thu, 30 Mar 1995 21:36:40 -0800 (PST) Cc: brian@mediacity.com, bugs@FreeBSD.org In-Reply-To: from "Howard Lew" at Mar 30, 95 08:43:30 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1758 Sender: bugs-owner@FreeBSD.org Precedence: bulk > > > > On Thu, 30 Mar 1995, Brian Litzinger wrote: > > > > > : I upgraded to 950322 SNAP from 950210 SNAP, and ever since I can't use > > > > : "passwd". (I didn't do a "full re-install", I just unpacked the bin/* > > > > make passwd setuid to root. > > chown root passwd > > chmod 4555 passwd (I think) > > > > Yep, I tried it and that doesn't fix it. Here's a log of what I did: > > paradise: {5} chown root passwd > paradise: {6} passwd > passwd: /etc/master.passwd: Permission denied > paradise: {7} chmod 4555 passwd > paradise: {8} passwd > passwd: /etc/master.passwd: Permission denied > paradise: {9} ls -al *passwd* > -rw------- 1 root wheel 1182 Mar 26 20:01 master.passwd > -r-sr-xr-x 1 root wheel 933 Mar 26 20:01 passwd > paradise: {10} > > Okay, no can do, so changed it back to the way it was: > paradise: {17} ls -al *passwd* > -rw------- 1 root wheel 1182 Mar 26 20:01 master.passwd > -rw-r--r-- 1 root wheel 933 Mar 26 20:01 passwd > paradise: {18} passwd > passwd: /etc/master.passwd: Permission denied > paradise: {19} Your changing permissions on the wrong ``passwd'', the person above was refering to the command in /usr/bin, not the data file in /etc: chown root:bin /usr/bin/passwd chmod 4555 /usr/bin/passwd chown root:wheel /etc/passwd chmod 644 /etc/passwd chown root:wheel /etc/master.passwd chmod 600 /etc/master.passwd > > Any ideas? I think passwd is broken in the new snap release. I'll try > the passwd command from the older snap and see if that fixes the problem. > File permissions where seriously damaged in this release :-(. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-bugs Thu Mar 30 22:39:57 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA14390 for bugs-outgoing; Thu, 30 Mar 1995 22:39:57 -0800 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 WAA14384 for ; Thu, 30 Mar 1995 22:39:56 -0800 Received: (hlew@localhost) by vegemite.Stanford.EDU (8.6.10/8.6.4) id WAA15871; Thu, 30 Mar 1995 22:39:29 -0800 Date: Thu, 30 Mar 1995 22:39:27 -0800 (PST) From: Howard Lew To: "Rodney W. Grimes" cc: fbsd@clem.systemsix.com, bugs@FreeBSD.org Subject: Re: passwd broken in new snap??? NOT! In-Reply-To: <199503310536.VAA07667@gndrsh.aac.dev.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@FreeBSD.org Precedence: bulk Thanks guys! It works! passwd is fine. I must be broken. How dumb of me. Ouch! :-) > > File permissions where seriously damaged in this release :-(. Yep. It says: paradise: {46} ls -al passwd -r-sr-xr-x 1 bin bin 20480 Mar 24 00:48 passwd But of course that's how it is to live on the bleeding edge of technology. :-) From owner-freebsd-bugs Thu Mar 30 22:56:31 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA14744 for bugs-outgoing; Thu, 30 Mar 1995 22:56:31 -0800 Received: from pluto.ops.NeoSoft.com (root@pluto.ops.NeoSoft.COM [198.64.212.23]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA14738 for ; Thu, 30 Mar 1995 22:56:30 -0800 Received: from metal.ops.neosoft.com (root@glenn-slip42.nmt.edu [129.138.5.142]) by pluto.ops.NeoSoft.com (8.6.10/8.6.10) with ESMTP id AAA17355; Fri, 31 Mar 1995 00:56:22 -0600 Received: (from smace@localhost) by metal.ops.neosoft.com (8.6.11/8.6.10) id XAA04105; Thu, 30 Mar 1995 23:56:19 -0700 From: Scott Mace Message-Id: <199503310656.XAA04105@metal.ops.neosoft.com> Subject: Re: passwd broken in new snap??? To: hlew@genome.Stanford.EDU (Howard Lew) Date: Thu, 30 Mar 1995 23:56:19 -0700 (MST) Cc: brian@mediacity.com, bugs@FreeBSD.org In-Reply-To: from "Howard Lew" at Mar 30, 95 08:43:30 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1311 Sender: bugs-owner@FreeBSD.org Precedence: bulk > > > > On Thu, 30 Mar 1995, Brian Litzinger wrote: > > > > > : I upgraded to 950322 SNAP from 950210 SNAP, and ever since I can't use > > > > : "passwd". (I didn't do a "full re-install", I just unpacked the bin/* > > > > make passwd setuid to root. > > chown root passwd > > chmod 4555 passwd (I think) > > that would be /usr/bin/passwd not /etc/passwd which is a file not a executable. > > Yep, I tried it and that doesn't fix it. Here's a log of what I did: > > paradise: {5} chown root passwd > paradise: {6} passwd > passwd: /etc/master.passwd: Permission denied > paradise: {7} chmod 4555 passwd > paradise: {8} passwd > passwd: /etc/master.passwd: Permission denied > paradise: {9} ls -al *passwd* > -rw------- 1 root wheel 1182 Mar 26 20:01 master.passwd > -r-sr-xr-x 1 root wheel 933 Mar 26 20:01 passwd > paradise: {10} > > Okay, no can do, so changed it back to the way it was: > paradise: {17} ls -al *passwd* > -rw------- 1 root wheel 1182 Mar 26 20:01 master.passwd > -rw-r--r-- 1 root wheel 933 Mar 26 20:01 passwd > paradise: {18} passwd > passwd: /etc/master.passwd: Permission denied > paradise: {19} > > Any ideas? I think passwd is broken in the new snap release. I'll try > the passwd command from the older snap and see if that fixes the problem. > > From owner-freebsd-bugs Fri Mar 31 00:17:37 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA29643 for bugs-outgoing; Fri, 31 Mar 1995 00:17:37 -0800 Received: from seldon.apanix.apana.org.au (seldon.apanix.apana.org.au [192.203.213.8]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id AAA29606 for ; Fri, 31 Mar 1995 00:17:28 -0800 Received: from ldjpc.apana.org.au (ldjpc.apana.org.au [192.203.213.254]) by seldon.apanix.apana.org.au (8.6.10/8.6.9) with ESMTP id RAA25464 for ; Fri, 31 Mar 1995 17:47:39 +0930 Received: (from jj@localhost) by ldjpc.apana.org.au (8.6.9/8.6.9) id HAA01972; Fri, 31 Mar 1995 07:53:35 +0930 Date: Fri, 31 Mar 1995 07:53:34 +0930 (CST) From: Lucas James To: freebsd-bugs@freefall.cdrom.com Subject: Re: kern/284: Network seems to be funny In-Reply-To: <199503291840.KAA24785@freefall.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@FreeBSD.org Precedence: bulk On Wed, 29 Mar 1995, Lucas James wrote: > >Number: 284 > >Category: kern > >Synopsis: Network gives permission denied > >How-To-Repeat: > > jj@ldjpc> telnet ldjpc > Trying 192.203.213.254... > telnet: Unable to connect to remote host: Permission denied > jj@ldjpc> telnet ldjpc nntp > Trying 192.203.213.254... > telnet: Unable to connect to remote host: Permission denied > jj@ldjpc> su > su: kerberos: unable to su: Retry count exceeded (send_to_kdc) > Password: > root@ldjpc# telnet ldjpc nntp > Trying 192.203.213.254... > telnet: Unable to connect to remote host: Permission denied > root@ldjpc# > > > >Fix: Let the machine "warm up" (?!) for 1/2 hour or so and everything works OK. (?) -- Lucas James jj@ldjpc.apana.org.au From owner-freebsd-bugs Fri Mar 31 01:53:54 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA10828 for bugs-outgoing; Fri, 31 Mar 1995 01:53:54 -0800 Received: from ptnsct.nis.za (ptnsct.nis.za [196.6.121.4]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id BAA10819 for ; Fri, 31 Mar 1995 01:53:44 -0800 Date: Fri, 31 Mar 1995 11:51:18 +0200 (O) From: ROBIN@ptnsct.nis.za (Robin Hunt) Message-Id: <950331115118.28d44@ptnsct.nis.za> Subject: NPX problem on 486? To: bugs@FreeBSD.org X-Vmsmail-To: SMTP%"bugs@freebsd.org" Sender: bugs-owner@FreeBSD.org Precedence: bulk Hi, I have a 486DX2/80 with 16Meg of RAM, running the 950211 (+-) SNAP of FreeBSD. It boots and runs fine on this kernel (except when I install 32 Meg of RAM, in which case it randomly panics). I have attempted to updgrade to the latest release (950322) (+-) in the hope that the 16/32 Meg problem would be resolved, but when I recompile the kernel and reboot, it gets as fas as: npx0 on motherboard npx0 INT 16 interface then it panics with the following error: Fatal trap 18: integer divide fault while in kernel mode Instruction Pointer: 0x8:0xf016e9f8 (see end for kernel listing of this addr) Code Segment = base = 0x0 limit = 0xfffff type = 0x16 DPL 0 pres 1 def 32 gran 1 Processor eflags: int enabled, resume IOPL = 0 Current process = 0 panic: integer divide fault please press reset ... which is all rather worrying, since the same motherboard DOES boot with the same config with the older kernel. Here is the kernel name list from around that address: f016cda0 F machdep.o f016ce64 T _cpu_startup f016d400 t _identifycpu f016d798 T _sendsig f016d944 T _sigreturn f016da54 T _diediedie f016db64 T _boot f016ddcc T _dumpsys f016def0 t _initcpu f016def8 T _setregs f016df74 T _cpu_sysctl f016e008 T _setidt f016e064 T _sdtossd f016e194 T _init386 f016e6b4 T _ptrace_set_pc f016e6d8 T _ptrace_single_step f016e6fc T _ptrace_getregs f016e728 T _ptrace_setregs f016e754 T _ptrace_write_u f016e818 T _fill_regs f016e888 T _set_regs f016e934 T _Debugger f016e948 T _bounds_check_with_label <--- Somewhere around here... f016ea20 T _disk_externalize f016ea50 F math_emulate.o I would appreciate any help, send to robin@ptnsct.nis.za From owner-freebsd-bugs Fri Mar 31 03:10:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA14044 for bugs-outgoing; Fri, 31 Mar 1995 03:10:02 -0800 Received: from easynet.com (easyr.easynet.net [198.67.38.6]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id DAA14032 for ; Fri, 31 Mar 1995 03:10:00 -0800 Received: by easynet.com (Smail3.1.28.1 #7) id m0rueR4-000rccC; Fri, 31 Mar 95 03:00 WET Message-Id: From: brian@MediaCity.Com (Brian Litzinger) Subject: Re: passwd broken in new snap??? To: hlew@genome.Stanford.EDU (Howard Lew) Date: Fri, 31 Mar 1995 03:00:14 -0800 (PST) Cc: brian@MediaCity.Com, bugs@FreeBSD.org In-Reply-To: from "Howard Lew" at Mar 30, 95 08:43:30 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 557 Sender: bugs-owner@FreeBSD.org Precedence: bulk > > > > On Thu, 30 Mar 1995, Brian Litzinger wrote: > > > > > : I upgraded to 950322 SNAP from 950210 SNAP, and ever since I can't use > > > > : "passwd". (I didn't do a "full re-install", I just unpacked the bin/* > > > > make passwd setuid to root. > > chown root passwd > > chmod 4555 passwd (I think) > > > > Yep, I tried it and that doesn't fix it. Here's a log of what I did: Sorry I should have been more clear: make /usr/bin/passwd setuid to root. chown root /usr/bin/passwd chmod 4555 /usr/bin/passwd Brian Litzinger brian@easynet.com From owner-freebsd-bugs Fri Mar 31 03:13:54 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA14179 for bugs-outgoing; Fri, 31 Mar 1995 03:13:54 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id DAA14168 for ; Fri, 31 Mar 1995 03:13:50 -0800 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id DAA16330; Fri, 31 Mar 1995 03:13:35 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id DAA00224; Fri, 31 Mar 1995 03:13:35 -0800 Message-Id: <199503311113.DAA00224@corbin.Root.COM> X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol To: ROBIN@ptnsct.nis.za (Robin Hunt) cc: bugs@FreeBSD.org Subject: Re: NPX problem on 486? In-reply-to: Your message of "Fri, 31 Mar 95 11:51:18 +0200." <950331115118.28d44@ptnsct.nis.za> From: David Greenman Reply-To: davidg@Root.COM Date: Fri, 31 Mar 1995 03:13:30 -0800 Sender: bugs-owner@FreeBSD.org Precedence: bulk >npx0 on motherboard >npx0 INT 16 interface > >then it panics with the following error: > >Fatal trap 18: integer divide fault while in kernel mode >Instruction Pointer: 0x8:0xf016e9f8 (see end for kernel listing of this addr) ... >f016e948 T _bounds_check_with_label <--- Somewhere around here... >f016ea20 T _disk_externalize The bounds_check_with_label routine is on its way out and should be gone in the next snapshot (in 1-2 weeks). Something isn't quite right with your disk label/drive parameters as sensed by the kernel...and is dividing by zero at: bp->b_cylin = bp->b_pblkno / lp->d_secpercyl; ...in the routine. -DG From owner-freebsd-bugs Fri Mar 31 08:27:09 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA25590 for bugs-outgoing; Fri, 31 Mar 1995 08:27:09 -0800 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 IAA25584 for ; Fri, 31 Mar 1995 08:27:08 -0800 Received: by halloran-eldar.lcs.mit.edu; id AA18373; Fri, 31 Mar 1995 11:22:40 -0500 Date: Fri, 31 Mar 1995 11:22:40 -0500 From: Garrett Wollman Message-Id: <9503311622.AA18373@halloran-eldar.lcs.mit.edu> To: J Wunsch Cc: freebsd-bugs@freefall.cdrom.com Subject: kern/287: Iconsistent header files In-Reply-To: <199503310330.TAA11132@freefall.cdrom.com> References: <199503310303.FAA05509@uriah.heep.sax.de> <199503310330.TAA11132@freefall.cdrom.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk < said: > In file included from ../../i386/isa/pcvt/pcvt_hdr.h:78, > from ../../i386/isa/pcvt/pcvt_drv.c:81: > ../../../include/malloc.h:2: warning: #warning "this file includes which is obsoleted, use instead" Should be , not > ../../../include/stdlib.h:170: conflicting types for `random' > ../../../include/sys/libkern.h:56: previous declaration of `random' > ../../../include/stdlib.h:170: warning: redundant redeclaration of `random' in same scope > ../../../include/sys/libkern.h:56: warning: previous declaration of `random' This is fallout from the above. The kernel random() and libc random() are very different beasts. > In file included from ../../i386/isa/pcvt/pcvt_hdr.h:79, > from ../../i386/isa/pcvt/pcvt_drv.c:81: > ../../../include/time.h:101: `time' redeclared as different kind of symbol > ../../../include/sys/kernel.h:59: previous declaration of `time' > *** Error code 1 Should be , not . -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 Mar 31 13:04:16 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA04590 for bugs-outgoing; Fri, 31 Mar 1995 13:04:16 -0800 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 MAA04512 for ; Fri, 31 Mar 1995 12:58:33 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA22936; Fri, 31 Mar 1995 22:54:03 +0200 Received: by sax.sax.de (8.6.9/8.6.9-s1) with UUCP id WAA22781; Fri, 31 Mar 1995 22:54:02 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id WAA08873; Fri, 31 Mar 1995 22:03:57 +0200 From: J Wunsch Message-Id: <199503312003.WAA08873@uriah.heep.sax.de> Subject: Re: kern/287: Iconsistent header files To: wollman@halloran-eldar.lcs.mit.edu (Garrett Wollman) Date: Fri, 31 Mar 1995 22:03:56 +0200 (MET DST) Cc: freebsd-bugs@freefall.cdrom.com In-Reply-To: <9503311622.AA18373@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at Mar 31, 95 11:22:40 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: 253 Sender: bugs-owner@FreeBSD.org Precedence: bulk As Garrett Wollman wrote: > > Should be , not Ok, thank'ya for pointing this out! -- 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 Mar 31 13:43:46 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA07092 for bugs-outgoing; Fri, 31 Mar 1995 13:43:46 -0800 Received: (from wollman@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA07074; Fri, 31 Mar 1995 13:43:44 -0800 Date: Fri, 31 Mar 1995 13:43:44 -0800 From: "Garrett A. Wollman" Message-Id: <199503312143.NAA07074@freefall.cdrom.com> To: jkh, wollman, freebsd-bugs Subject: Changed information for PR docs/262 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: There is no man page for the map-mbone command State-Changed-From-To: open-closed State-Changed-By: wollman State-Changed-When: Fri Mar 31 13:43:18 PST 1995 State-Changed-Why: Man page added. From owner-freebsd-bugs Fri Mar 31 18:12:31 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA15310 for bugs-outgoing; Fri, 31 Mar 1995 18:12:31 -0800 Received: from disperse.demon.co.uk (disperse.demon.co.uk [158.152.1.77]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id SAA15304 for ; Fri, 31 Mar 1995 18:12:29 -0800 Received: from palmer.demon.co.uk by disperse.demon.co.uk id aa09527; 1 Apr 95 3:12 GMT-60:00 Received: from localhost (gary@localhost [127.0.0.1]) by palmer.demon.co.uk (8.6.9/8.6.9) with SMTP id DAA00200 for ; Sat, 1 Apr 1995 03:11:22 +0100 X-Authentication-Warning: palmer.demon.co.uk: Host localhost didn't use HELO protocol To: FreeBSD-Bugs Subject: tun driver MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <196.796702281.1@palmer.demon.co.uk> Date: Sat, 01 Apr 1995 03:11:21 +0100 Message-ID: <197.796702281@palmer.demon.co.uk> From: Gary Palmer Sender: bugs-owner@FreeBSD.org Precedence: bulk I've now changed to using the tun driver from kermit&slattach, and boy, what an improvement! especially the -auto feature :-) HOWEVER (yes, it had to come :-( ), it seems to reboot the machine (note: no panic message) if it tries to add a route to the tables which already existed. It's caught me about 3 times tonight already. Anyone else seen this? This is with a kernel from ~2 days ago. Gary From owner-freebsd-bugs Fri Mar 31 19:10:07 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA26136 for bugs-outgoing; Fri, 31 Mar 1995 19:10:07 -0800 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA26128; Fri, 31 Mar 1995 19:10:03 -0800 Date: Fri, 31 Mar 1995 19:10:03 -0800 Message-Id: <199504010310.TAA26128@freefall.cdrom.com> From: System Administration Reply-To: System Administration To: freebsd-bugs Subject: kern/288: panic in kern_malloc.c free: multiple frees In-Reply-To: Your message of Fri, 31 Mar 1995 22:02:03 -0500 <199504010302.WAA00663@crlabs.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 288 >Category: kern >Synopsis: panic: free: multiple frees >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Mar 31 19:10:02 1995 >Originator: System Administration >Organization: CR Labs >Release: FreeBSD 2.1.0-Development i386 >Environment: FreeBSD 2.0-SNAP-950322 80486DX-50 16M RAM WD8003E AHA1542B 16550 SIO running at 115.2K bps Sportster 28.8 Modem >Description: Upon heavy network activity using FreeBSD SNAP 950322 as a Ethernet <--> PPP router, the kernel panics with: panic: free: multiple frees >How-To-Repeat: Using PC-Anywhere for Windows running on Ethernet-connected machines at the local and remote sites, transfer a large file such as Mosaic 2.0 Beta 3 (1.5M) through the FreeBSD machine which is acting as an IP router. Within a few 100Kbytes, the kernel will panic. >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Sat Apr 1 00:03:36 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA13571 for bugs-outgoing; Sat, 1 Apr 1995 00:03:36 -0800 Received: from indigo.csci.csusb.edu (hishibas@indigo.csci.csusb.edu [139.182.38.28]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id AAA13563 for ; Sat, 1 Apr 1995 00:03:35 -0800 Received: by indigo.csci.csusb.edu (931110.SGI/930416.SGI) for bugs@FreeBSD.org id AA25113; Sat, 1 Apr 95 00:01:19 -0800 From: hishibas@indigo.csci.csusb.edu (Hiroki Ishibashi) Message-Id: <9504010801.AA25113@indigo.csci.csusb.edu> Subject: Compaq's BIOS Problem ?? To: bugs@FreeBSD.org Date: Sat, 1 Apr 1995 00:01:19 -0800 (PST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 454 Sender: bugs-owner@FreeBSD.org Precedence: bulk I tried to install FreeBSD 2.0, but boot disk hangs on my Compaq Prolinea 4/33. I was able to install it on AST Bravo. This could be BIOS Problem?? ================================================================================ = Hiroki Ishibashi hishibas@silicon.csci.csusb.edu = = ** California State University, San Bernardino ** = ================================================================================ From owner-freebsd-bugs Sat Apr 1 01:01:21 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA29073 for bugs-outgoing; Sat, 1 Apr 1995 01:01:21 -0800 Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id BAA29064 for ; Sat, 1 Apr 1995 01:01:13 -0800 Received: from localhost (localhost [127.0.0.1]) by grunt.grondar.za (8.6.11/8.6.9) with SMTP id LAA15671 for ; Sat, 1 Apr 1995 11:00:54 +0200 Message-Id: <199504010900.LAA15671@grunt.grondar.za> X-Authentication-Warning: grunt.grondar.za: Host localhost didn't use HELO protocol To: bugs@FreeBSD.org Subject: TIP still broken... Date: Sat, 01 Apr 1995 11:00:54 +0200 From: Mark Murray Sender: bugs-owner@FreeBSD.org Precedence: bulk Hi tip(1) is till not compiling on my system (as of ctm470): > ===> libacu > ===> tip > cc -O2 -g -o tip acu.o acutab.o cmds.o cmdtab.o cu.o hunt.o log.o partab.o remote.o tip.o tipout.o uucplock.o value.o vars.o ../libacu/libacu.a > cc: ../libacu/libacu.a: No such file or directory > *** Error code 1 vvv The library is actually in ../libacu/obj/libacu.a. I'm not too sure of the best fix for this, whether to install the library, or to just modify the path to it. Also, are there any good reasons why this is being compiled with -g? M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 From owner-freebsd-bugs Sat Apr 1 02:02:41 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA01964 for bugs-outgoing; Sat, 1 Apr 1995 02:02:41 -0800 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 CAA01958 for ; Sat, 1 Apr 1995 02:02:40 -0800 Received: (hlew@localhost) by vegemite.Stanford.EDU (8.6.10/8.6.4) id CAA22400; Sat, 1 Apr 1995 02:02:32 -0800 Date: Sat, 1 Apr 1995 02:02:30 -0800 (PST) From: Howard Lew To: bugs@FreeBSD.org Subject: more info on the IDE hard disk timeout (SNAP) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@FreeBSD.org Precedence: bulk Here's what the xconsole says when the hard drive times out: wd1: interrupt timeout: wd1: status 50 error 0 wd1: interrupt timeout: wd1: status 50 error 1 The hard drive is a Maxtor 7120AT (130 MB). I do not think it can do multi-block transfers, but the bootup message says it can: [... deleted] fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: (NEC 765) [0: fd0: 1.44MB 3.5in] [1: fd1: 1.2MB 5.25in] wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): , 32-bit, multi-block-16 wd0: 518MB (1061424 sectors), 1053 C 16 H 63 S/T 512 B/S wdc0: unit 1 (wd1): , 32-bit, multi-block-16 wd1: 124MB (254592 sectors), 936 C 16 H 17 S/T 512 B/S wdc1 not found at 0x170 From owner-freebsd-bugs Sat Apr 1 02:36:26 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA02368 for bugs-outgoing; Sat, 1 Apr 1995 02:36:26 -0800 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id CAA02358; Sat, 1 Apr 1995 02:36:23 -0800 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: Mark Murray cc: bugs@FreeBSD.org Subject: Re: TIP still broken... In-reply-to: Your message of "Sat, 01 Apr 95 11:00:54 +0200." <199504010900.LAA15671@grunt.grondar.za> Date: Sat, 01 Apr 1995 02:36:23 -0800 Message-ID: <2357.796732583@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: bugs-owner@FreeBSD.org Precedence: bulk > Hi > > tip(1) is till not compiling on my system (as of ctm470): Sorry, fixed! Jordan From owner-freebsd-bugs Sat Apr 1 04:00:15 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA07133 for bugs-outgoing; Sat, 1 Apr 1995 04:00:15 -0800 Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA07100 for ; Sat, 1 Apr 1995 04:00:13 -0800 Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id NAA06008 for bugs@freebsd.org; Sat, 1 Apr 1995 13:50:35 +0200 From: Luigi Rizzo Message-Id: <199504011150.NAA06008@labinfo.iet.unipi.it> Subject: A note on snap950322 install -- lnc0 support To: bugs@FreeBSD.org Date: Sat, 1 Apr 1995 13:50:35 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1164 Sender: bugs-owner@FreeBSD.org Precedence: bulk I tried to install snap950322 on a system with an Ether-32VL ethernet card. This card uses the lnc driver. Two points about the install kernel and procedures: - the kernel on the disk look for the card at io 0x280, int 5; the card, by default, is at io 0x300, int 3, and, at least mine CANNOT be configured at 0x280 (the reason is probably that it seems to use a lot of IO ports). I used kernel -c to change this, but it would be nicer if the default choices in the kernel were pointing to a realistic address. - the install scripts seems to lack an entry for lnc cards. I'd suggest two things: 1) obviously, add the entry in the install scripts, 2) add a "blank" entry where the user can specify its own adapter name, to overcome the problem in case a new adapter is not supported. Thanks Luigi ==================================================================== Luigi Rizzo Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it Universita' di Pisa tel: +39-50-568533 via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 ==================================================================== From owner-freebsd-bugs Sat Apr 1 04:30:05 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA09307 for bugs-outgoing; Sat, 1 Apr 1995 04:30:05 -0800 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA09300 for freebsd-bugs; Sat, 1 Apr 1995 04:30:04 -0800 Date: Sat, 1 Apr 1995 04:30:04 -0800 From: GNU GNATS Message-Id: <199504011230.EAA09300@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/09/22] i386/4 You can mount a filesystem multiple times "on top" o [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/15] gnu/19 cvs commit core dumps on multiple files [1994/11/18] kern/21 kernel panic. [1994/11/18] conf/22 Cannot use links to share kernel objects [1994/11/23] kern/25 mounting a photocd panics the kernel [1994/11/23] kern/27 Loopback mounts confuse unmount-on-reboot code [1994/11/26] docs/29 man page descriptions of /etc/ftpwelcome and /etc/ft [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 Bug in /etc/rc [1994/12/13] misc/49 Bug in /etc/rc [1994/12/14] kern/51 Panic accessing NFS mounted file system [1994/12/14] gnu/54 No manual entry for uucpd [1994/12/18] misc/66 if you run bininst when you're on the net via slip, [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/18] bin/71 Incomplete package of tcl7.3.tgz [1994/12/18] bin/72 emu-1.3 has empty app-defaults file [1994/12/18] bin/73 no man page in xearth package [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 serious [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/125 no references to makewhatis in manual pages [1995/01/14] docs/127 locate man page does not have any clues to how the d [1995/01/14] misc/128 default owners of system directories is a security h [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] misc/134 ispell (in ports) thinks the dictionary is in /usr/d [1995/01/14] bin/135 not enough ptys; virtual console names conflict with [1995/01/14] docs/137 domainname man page references getdomainname(2) whic [1995/01/14] kern/140 cdplay will not work with NEC210 [1995/01/14] kern/143 Processes using NFS (eg to link an X server) will so [1995/01/14] kern/144 Processes using NFS (eg to link an X server) will so [1995/01/15] bin/146 version of compress is kinda old and slow [1995/01/16] kern/147 auvoxware and xdm occasionally die with a signal 10 [1995/01/16] kern/148 auvoxware dumps core sometimes after playing file [1995/01/19] bin/151 One of the pkg_add set /tmp mod to 755 [1995/01/19] kern/152 Kernel config doesn't handle "irq 2" as irq 9 [1995/01/20] bin/153 mount -u improvement for diskless systems [1995/01/21] kern/157 Quota system does not work [1995/01/21] docs/159 uucp manual files have wrong file locations. [1995/01/21] docs/161 Not MAKEDEV(8) manual page. [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] bin/167 makewhatis ignores symbolic links. [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/179 Getty hangs on ttyv0 [1995/01/23] kern/180 Fiddling with process stack and using scanf with inv [1995/01/24] bin/182 Strange error from umount [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] conf/187 Files referenced in Makefiles do not exist [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] bin/201 PPP does not find config-files [1995/02/01] misc/202 System hang or reboot without clues, tcp ppp named r [1995/02/02] bin/204 Installing failes [1995/02/05] kern/207 Using a local version of clntudp_create under gdb ca [1995/02/06] gnu/210 tar support for rsh doesn't work [1995/02/08] kern/211 mv returns "Invalid argument" unreasonably [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/13] bin/242 [1995/03/14] kern/243 missing routines for new sound drivers [1995/03/17] kern/247 Berkeley Packet Filter fix [1995/03/17] kern/248 scbus attach/probe information is inconsistent [1995/03/17] misc/249 $hostname variable in /etc/netstart not always set [1995/03/17] conf/250 /etc/netstart executes undesired hostname.xxx files [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] misc/254 fsck -p misbehaves for SIGQUIT [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] gnu/285 ld.so problem with -lg++ [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 From owner-freebsd-bugs Sat Apr 1 05:31:31 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA11069 for bugs-outgoing; Sat, 1 Apr 1995 05:31:31 -0800 Received: (from ache@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA11048; Sat, 1 Apr 1995 05:31:27 -0800 Date: Sat, 1 Apr 1995 05:31:27 -0800 From: "Andrey A. Chernov" Message-Id: <199504011331.FAA11048@freefall.cdrom.com> To: muir@idiom.com, ache, freebsd-bugs Subject: Changed information for PR docs/125 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: no references to makewhatis in manual pages State-Changed-From-To: open-closed State-Changed-By: ache State-Changed-When: Sat Apr 1 05:30:46 PST 1995 State-Changed-Why: Fixed. From owner-freebsd-bugs Sat Apr 1 05:37:13 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA11348 for bugs-outgoing; Sat, 1 Apr 1995 05:37:13 -0800 Received: (from ache@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA11333; Sat, 1 Apr 1995 05:37:11 -0800 Date: Sat, 1 Apr 1995 05:37:11 -0800 From: "Andrey A. Chernov" Message-Id: <199504011337.FAA11333@freefall.cdrom.com> To: mrami@mramirez.sy.yale.edu, ache, freebsd-bugs Subject: Changed information for PR bin/242 Sender: bugs-owner@FreeBSD.org Precedence: bulk Old Synopsis: New Synopsis: curses header files do not have correct linkages for C++ State-Changed-From-To: open-closed State-Changed-By: ache State-Changed-When: Sat Apr 1 05:34:14 PST 1995 State-Changed-Why: There is separate C++ interface for curses From owner-freebsd-bugs Sat Apr 1 05:43:51 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA11562 for bugs-outgoing; Sat, 1 Apr 1995 05:43:51 -0800 Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA11556; Sat, 1 Apr 1995 05:43:39 -0800 Received: from localhost (localhost [127.0.0.1]) by grunt.grondar.za (8.6.11/8.6.9) with SMTP id PAA05212; Sat, 1 Apr 1995 15:40:56 +0200 Message-Id: <199504011340.PAA05212@grunt.grondar.za> X-Authentication-Warning: grunt.grondar.za: Host localhost didn't use HELO protocol To: GNU GNATS cc: freebsd-bugs@freefall.cdrom.com Subject: Re: List of open Problem Reports Date: Sat, 01 Apr 1995 15:40:56 +0200 From: Mark Murray Sender: bugs-owner@FreeBSD.org Precedence: bulk > [1994/12/18] bin/73 no man page in xearth package This can be laid to rest. There is a man page now. > [1995/01/22] kern/175 Syscons does not recover X graphics mode I know this issue got quite seriously discussed, in recent days, BUT I really think it ought to go. Bruce (?) eventually agreed that it worked for him. > [1995/01/23] kern/179 Getty hangs on ttyv0 Is this still open because of hangs on COMCONSOLEs? Mark -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 From owner-freebsd-bugs Sat Apr 1 06:33:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA12594 for bugs-outgoing; Sat, 1 Apr 1995 06:33:02 -0800 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 GAA12588; Sat, 1 Apr 1995 06:32:35 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id AAA12517; Sun, 2 Apr 1995 00:27:29 +1000 Date: Sun, 2 Apr 1995 00:27:29 +1000 From: Bruce Evans Message-Id: <199504011427.AAA12517@godzilla.zeta.org.au> To: gnats@freefall.cdrom.com, mark@grondar.za Subject: Re: List of open Problem Reports Cc: freebsd-bugs@freefall.cdrom.com Sender: bugs-owner@FreeBSD.org Precedence: bulk >> [1995/01/22] kern/175 Syscons does not recover X graphics mode >I know this issue got quite seriously discussed, in recent days, BUT >I really think it ought to go. Bruce (?) eventually agreed that it worked >for him. No. You just got tired of discussing how it worked like I mistakenly(?) expected it to work for old versions (with NCONS=4 and gettys on all consoles, Alt-Fn went back to X started on console n under 1.1.5 and Xfree-old). Now, with syscons (NCONS=default) or pcvt and gettys on 4 consoles, Alt-Fn goes back to the text console n (it shows normal X error output), and Alt-F5 clears the until the system is rebooted. This is clearly an X problem (XFree86-3.1-W32 ET4000/W32i). Bruce From owner-freebsd-bugs Sat Apr 1 06:55:34 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA12908 for bugs-outgoing; Sat, 1 Apr 1995 06:55:34 -0800 Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id GAA12902; Sat, 1 Apr 1995 06:55:21 -0800 Received: from localhost (localhost [127.0.0.1]) by grunt.grondar.za (8.6.11/8.6.9) with SMTP id QAA05677; Sat, 1 Apr 1995 16:54:15 +0200 Message-Id: <199504011454.QAA05677@grunt.grondar.za> X-Authentication-Warning: grunt.grondar.za: Host localhost didn't use HELO protocol To: Bruce Evans cc: gnats@freefall.cdrom.com, freebsd-bugs@freefall.cdrom.com Subject: Re: List of open Problem Reports Date: Sat, 01 Apr 1995 16:54:15 +0200 From: Mark Murray Sender: bugs-owner@FreeBSD.org Precedence: bulk >> [1995/01/22] kern/175 Syscons does not recover X graphics mode > > >I know this issue got quite seriously discussed, in recent days, BUT > >I really think it ought to go. Bruce (?) eventually agreed that it worked > >for him. > > No. You just got tired of discussing how it worked like I mistakenly(?) > expected it to work for old versions (with NCONS=4 and gettys on all > consoles, Alt-Fn went back to X started on console n under 1.1.5 and > Xfree-old). Sorry. I thought we had reached a (sort-of) conclusion. I get TONS of email, mostly work related, and I hate for threads to drag on. > Now, with syscons (NCONS=default) or pcvt and gettys on 4 consoles, > Alt-Fn goes back to the text console n (it shows normal X error output), > and Alt-F5 clears the until the system is rebooted. This is clearly > an X problem (XFree86-3.1-W32 ET4000/W32i). Of course. I had forgotten about the W32 aspect. It was someone else who had a similar problem to yours, and who had (also?) not used the Alt-F(n+1) approach. With _him_, it came right. I must have confused the issues along the way. This has been a bad month... M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 From owner-freebsd-bugs Sat Apr 1 09:22:13 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA18576 for bugs-outgoing; Sat, 1 Apr 1995 09:22:13 -0800 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 JAA18568; Sat, 1 Apr 1995 09:21:55 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA23285; Sat, 1 Apr 1995 19:20:51 +0200 Received: by sax.sax.de (8.6.9/8.6.9-s1) with UUCP id TAA01510; Sat, 1 Apr 1995 19:20:48 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id TAA00466; Sat, 1 Apr 1995 19:01:56 +0200 From: J Wunsch Message-Id: <199504011701.TAA00466@uriah.heep.sax.de> Subject: Re: List of open Problem Reports To: mark@grondar.za (Mark Murray) Date: Sat, 1 Apr 1995 19:01:55 +0200 (MET DST) Cc: gnats@freefall.cdrom.com, freebsd-bugs@freefall.cdrom.com In-Reply-To: <199504011340.PAA05212@grunt.grondar.za> from "Mark Murray" at Apr 1, 95 03:40:56 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 468 Sender: bugs-owner@FreeBSD.org Precedence: bulk As Mark Murray wrote: > > > [1995/01/23] kern/179 Getty hangs on ttyv0 > > Is this still open because of hangs on COMCONSOLEs? Yes. Comconsoles and pcvt are still malfunctioning; syscons only added a private hackaround. It's i386/i386/cons.c that is broken, Bruce agrees with me (and hopes i'll go and fix it :-). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Sat Apr 1 09:27:03 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA18626 for bugs-outgoing; Sat, 1 Apr 1995 09:27:03 -0800 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 JAA18616 for ; Sat, 1 Apr 1995 09:26:56 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA23441; Sat, 1 Apr 1995 19:26:39 +0200 Received: by sax.sax.de (8.6.9/8.6.9-s1) with UUCP id TAA01592 for freebsd-bugs@FreeBSD.org; Sat, 1 Apr 1995 19:26:38 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id TAA00643 for freebsd-bugs@FreeBSD.org; Sat, 1 Apr 1995 19:20:48 +0200 From: J Wunsch Message-Id: <199504011720.TAA00643@uriah.heep.sax.de> Subject: Re: List of open Problem Reports To: freebsd-bugs@FreeBSD.org (FreeBSD bugs list) Date: Sat, 1 Apr 1995 19:20:48 +0200 (MET DST) In-Reply-To: <199504011427.AAA12517@godzilla.zeta.org.au> from "Bruce Evans" at Apr 2, 95 00:27:29 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: 741 Sender: bugs-owner@FreeBSD.org Precedence: bulk As Bruce Evans wrote: > > >> [1995/01/22] kern/175 Syscons does not recover X graphics mode > ... > Now, with syscons (NCONS=default) or pcvt and gettys on 4 consoles, > Alt-Fn goes back to the text console n (it shows normal X error output), > and Alt-F5 clears the until the system is rebooted. This is clearly > an X problem (XFree86-3.1-W32 ET4000/W32i). pcvt defaults to 8 screens. Start 8 getty's, and X should be operating on the VT where it has been started. As for the XFree86 problem, *our* bug report should be closed and you should hand the problem of to the XFree86 folks. -- 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 Sat Apr 1 09:46:27 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA22071 for bugs-outgoing; Sat, 1 Apr 1995 09:46:27 -0800 Received: from irbs.com ([199.182.75.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA22062 for ; Sat, 1 Apr 1995 09:46:24 -0800 Received: (from jc@localhost) by irbs.com (8.6.11/8.6.6) id MAA10720; Sat, 1 Apr 1995 12:45:52 -0500 From: John Capo Message-Id: <199504011745.MAA10720@irbs.com> Subject: Re: tun driver To: gary@palmer.demon.co.uk (Gary Palmer) Date: Sat, 1 Apr 1995 12:45:51 -0500 (EST) Cc: freebsd-bugs@FreeBSD.org In-Reply-To: <197.796702281@palmer.demon.co.uk> from "Gary Palmer" at Apr 1, 95 03:11:21 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1374 Sender: bugs-owner@FreeBSD.org Precedence: bulk Gary Palmer writes: > > I've now changed to using the tun driver from kermit&slattach, and boy, > what an improvement! especially the -auto feature :-) I have been using iijppp for about a month now and have found and fixed a number of bugs related to the auto mode. They have not made it back into the distribution yet. > > HOWEVER (yes, it had to come :-( ), it seems to reboot the machine (note: > no panic message) if it tries to add a route to the tables which already > existed. It's caught me about 3 times tonight already. > > Anyone else seen this? This is with a kernel from ~2 days ago. > This problem is not specific to the tun driver. I get spontaneous reboots with routed, gated, pppd, and route at times. There is something evil in the route cloning. Interfaces coming and going or deleting an active default route causes a reboot. Disable route cloning and I believe your problem will go away. My current method is to disable this statement in in_rmx.c:in_addroute() /* * For IP, all unicast non-host routes are automatically cloning. if(!(rt->rt_flags & (RTF_HOST | RTF_CLONING))) { struct sockaddr_in *sin = (struct sockaddr_in *)rt_key(rt); if(!IN_MULTICAST(ntohl(sin->sin_addr.s_addr))) { rt->rt_flags |= RTF_PRCLONING; } } */ I would be very interested to know if this works for you. John Capo From owner-freebsd-bugs Sat Apr 1 12:00:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA27378 for bugs-outgoing; Sat, 1 Apr 1995 12:00:02 -0800 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA27368; Sat, 1 Apr 1995 12:00:01 -0800 Date: Sat, 1 Apr 1995 12:00:01 -0800 Message-Id: <199504012000.MAA27368@freefall.cdrom.com> From: J Wunsch Reply-To: J Wunsch To: freebsd-bugs Subject: gnu/289: info(1) cannot handle arrow keys In-Reply-To: Your message of Sat, 1 Apr 1995 21:46:00 +0200 <199504011946.VAA21269@uriah.heep.sax.de> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 289 >Category: gnu >Synopsis: info(1) cannot handle arrow keys on a VT100 >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 Apr 1 12:00:01 1995 >Originator: J Wunsch >Organization: >Release: FreeBSD 2.1.0-Development i386 >Environment: >Description: info(1) beeps when being faced with the arrow keys as sent by a VT100- compatible terminal. This is not acceptable for a user-friendly front- end to a substantial part of the system documentation (especially considering the fact that emacs(1) *does* know how to handle it right out of the box). Users cannot be expected to now something about C-N and C-P just in order to move the cursor around. >How-To-Repeat: Start info(1) from something that emulates a VT100 (pcvt(4), kermit(1)), and hit an arrow key. >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Sat Apr 1 12:00:03 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA27389 for bugs-outgoing; Sat, 1 Apr 1995 12:00:03 -0800 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA27382; Sat, 1 Apr 1995 12:00:03 -0800 Date: Sat, 1 Apr 1995 12:00:03 -0800 Message-Id: <199504012000.MAA27382@freefall.cdrom.com> From: J Wunsch Reply-To: J Wunsch To: freebsd-bugs Subject: kern/290: latest sio change broke slattach(8) In-Reply-To: Your message of Sat, 1 Apr 1995 21:53:26 +0200 <199504011953.VAA00384@uriah.heep.sax.de> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 290 >Category: kern >Synopsis: latest sio change broke slattach(8) >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 Apr 1 12:00:02 1995 >Originator: J Wunsch >Organization: >Release: FreeBSD 2.1.0-Development i386 >Environment: -current as of ctm #511 (95/04/01, 09:35:47 UTC) >Description: The latest sio changes obviously broke the SLIP line discipline. Slattach(8) complains: Apr 1 21:48:55 uriah slattach[150]: cannot get carrier state: Inappropriate ioctl for device Apr 1 21:48:55 uriah slattach[150]: Waiting for carrier on /dev/cuaa1 (sl-1) >How-To-Repeat: start slattach(8) on a recent kernel >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Sat Apr 1 12:52:27 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA29274 for bugs-outgoing; Sat, 1 Apr 1995 12:52:27 -0800 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 MAA29265 for ; Sat, 1 Apr 1995 12:52:23 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id GAA20113; Sun, 2 Apr 1995 06:50:12 +1000 Date: Sun, 2 Apr 1995 06:50:12 +1000 From: Bruce Evans Message-Id: <199504012050.GAA20113@godzilla.zeta.org.au> To: freebsd-bugs@freefall.cdrom.com, j@uriah.heep.sax.de Subject: Re: kern/290: latest sio change broke slattach(8) Sender: bugs-owner@FreeBSD.org Precedence: bulk >The latest sio changes obviously broke the SLIP line discipline. >Slattach(8) complains: >Apr 1 21:48:55 uriah slattach[150]: cannot get carrier state: Inappropriate ioctl for device >Apr 1 21:48:55 uriah slattach[150]: Waiting for carrier on /dev/cuaa1 (sl-1) I'll fix this in a few minutes. sltioctl() now returns ENOTTY for ioctls that it doesn't know about. It's supposed to return -1 like it used to so that such ioctls can be handled by higher layer(s). BTW, slioctl() (a different function) returns EINVAL for ioctls that it doesn't know about. Shouldn't it return ENOTTY? Bruce From owner-freebsd-bugs Sat Apr 1 13:40:35 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA01553 for bugs-outgoing; Sat, 1 Apr 1995 13:40:35 -0800 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 NAA01544; Sat, 1 Apr 1995 13:40:33 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA11148; Sat, 1 Apr 95 14:33:40 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9504012133.AA11148@cs.weber.edu> Subject: Re: List of open Problem Reports To: gnats@freefall.cdrom.com (GNU GNATS) Date: Sat, 1 Apr 95 14:33:39 MST Cc: freebsd-bugs@freefall.cdrom.com In-Reply-To: <199504011230.EAA09300@freefall.cdrom.com> from "GNU GNATS" at Apr 1, 95 04:30:04 am X-Mailer: ELM [version 2.4dev PL52] Sender: bugs-owner@FreeBSD.org Precedence: bulk > > This is the list of currently open problem reports [ ... ] > [1995/03/30] kern/287 Several header files are not consistent > [1995/03/31] kern/288 panic: free: multiple frees > Is this the intended last report on this list? Unfortunately, the list end indicator patch that was recently posted has apparently not been applied, and it is impossible to tell if it's the genuine list end or if the list has been truncated. 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 Apr 1 15:20:01 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA09304 for bugs-outgoing; Sat, 1 Apr 1995 15:20:01 -0800 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA09297; Sat, 1 Apr 1995 15:20:01 -0800 Date: Sat, 1 Apr 1995 15:20:01 -0800 Message-Id: <199504012320.PAA09297@freefall.cdrom.com> From: gibbs@estienne.cs.berkeley.edu Reply-To: gibbs@estienne.cs.berkeley.edu To: freebsd-bugs Subject: kern/291: PCI devices still probe/attach after being disabled via usercfg In-Reply-To: Your message of Sat, 1 Apr 1995 15:16:14 -0800 <199504012316.PAA25490@narnia.hip.berkeley.edu> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 291 >Category: kern >Synopsis: PCI devices still probe/attach after being disabled via usercfg >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 Apr 1 15:20:00 1995 >Originator: gibbs >Organization: >Release: FreeBSD 2.1.0-Development i386 >Environment: >Description: PCI devices don't follow the same rules as all other types of devices in the way they are probed. PCI devices will steal unit numbers from non PCI devices as well as probe devices that was disabled. This is probably because most drivers only look to see if the unit number they are passed is < NFOO and userconfig does not update NFOO. Even updating NFOO would not be enough since (as in the case of the ahc driver) other units may be on other types of buses and a PCI device will just take the place of an EISA or VL device. Both of these behaviors will make userconfig less powerful and more confusing to users. >How-To-Repeat: Configure a kernel with both eisa and PCI ahc devices. Attempt to disable the PCI device. For stealing, configure one EISA and one PCI ahc device. Put two aic7870 based controllers in the machine. >Fix: Haven't looked yet. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Sat Apr 1 15:30:04 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA09495 for bugs-outgoing; Sat, 1 Apr 1995 15:30:04 -0800 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA09488; Sat, 1 Apr 1995 15:30:03 -0800 Date: Sat, 1 Apr 1995 15:30:03 -0800 Message-Id: <199504012330.PAA09488@freefall.cdrom.com> From: gibbs@estienne.cs.berkeley.edu Reply-To: gibbs@estienne.cs.berkeley.edu To: freebsd-bugs Subject: misc/292: rfc1323 and rfc1644 support can confuse terminal servers w/SLIP In-Reply-To: Your message of Sat, 1 Apr 1995 15:22:43 -0800 <199504012322.PAA27919@narnia.hip.berkeley.edu> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 292 >Category: misc >Synopsis: rfc1323 and rfc1644 support can confuse terminal servers w/SLIP >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Apr 1 15:30:01 1995 >Originator: gibbs >Organization: >Release: FreeBSD 2.1.0-Development i386 >Environment: SLIP connection to an annex (and possibly other) terminal server. VJ header compression might be a factor. >Description: rfc1323 and rfc1644 negotiation can make TCP communication to other FreeBSD machines on the other side of a SLIP link impossible. This is not a FreeBSD bug, but a bug in many terminal servers. During install, I would highly recommend that these two commands be run before any type of network installation: sysctl -w net.inet.tcp.rfc1323=0 sysctl -w net.inet.tcp.rfc1644=0 It would not look good to not be able to ftp the distribution from one of our own machines. There should also be a big warning about this in the install notes and possibly even during installation. >How-To-Repeat: If you want to see it in action, just let me know, and I'll turn rfc1323 and rfc1644 negotiation back on for narnia.hip.berkeley.edu. >Fix: Make the install program disable these features during network installations. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Sat Apr 1 16:01:36 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA10290 for bugs-outgoing; Sat, 1 Apr 1995 16:01:36 -0800 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id QAA10283; Sat, 1 Apr 1995 16:01:35 -0800 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: gibbs@estienne.cs.berkeley.edu cc: freebsd-bugs@freefall.cdrom.com Subject: Re: misc/292: rfc1323 and rfc1644 support can confuse terminal servers w/SLIP In-reply-to: Your message of "Sat, 01 Apr 95 15:30:03 PST." <199504012330.PAA09488@freefall.cdrom.com> Date: Sat, 01 Apr 1995 16:01:35 -0800 Message-ID: <10282.796780895@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: bugs-owner@FreeBSD.org Precedence: bulk > rfc1323 and rfc1644 negotiation can make TCP communication to other > FreeBSD machines on the other side of a SLIP link impossible. This > is not a FreeBSD bug, but a bug in many terminal servers. > > During install, I would highly recommend that these two commands be > run before any type of network installation: > > sysctl -w net.inet.tcp.rfc1323=0 > sysctl -w net.inet.tcp.rfc1644=0 Maybe these need to be switched on and off inside netstart using sysconfig variables? Suggestions? Jordan From owner-freebsd-bugs Sat Apr 1 16:30:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA11361 for bugs-outgoing; Sat, 1 Apr 1995 16:30:02 -0800 Received: (from ache@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA11335; Sat, 1 Apr 1995 16:30:00 -0800 Date: Sat, 1 Apr 1995 16:30:00 -0800 From: "Andrey A. Chernov" Message-Id: <199504020030.QAA11335@freefall.cdrom.com> To: joerg_wunsch@uriah.heep.sax.de, ache, freebsd-bugs Subject: Changed information for PR kern/290 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: latest sio change broke slattach(8) State-Changed-From-To: open-closed State-Changed-By: ache State-Changed-When: Sat Apr 1 16:29:33 PST 1995 State-Changed-Why: Fixed. From owner-freebsd-bugs Sat Apr 1 19:30:04 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA21080 for bugs-outgoing; Sat, 1 Apr 1995 19:30:04 -0800 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA21073; Sat, 1 Apr 1995 19:30:02 -0800 Date: Sat, 1 Apr 1995 19:30:02 -0800 Message-Id: <199504020330.TAA21073@freefall.cdrom.com> From: Shipley Reply-To: Shipley To: freebsd-bugs Subject: kern/293: wd0: interrupt timeout In-Reply-To: Your message of Sat, 1 Apr 1995 19:15:59 -0800 <199504020315.TAA00378@whimpy.dis.org> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 293 >Category: kern >Synopsis: wd0: interrupt timeout >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Apr 1 19:30:01 1995 >Originator: & >Organization: >Release: FreeBSD 2.1.0-Development i386 >Environment: Apr 1 19:03:29 whimpy /kernel: CPU: i386DX (386-class CPU) Apr 1 19:03:29 whimpy /kernel: real memory = 7995392 (1952 pages) Apr 1 19:03:29 whimpy /kernel: avail memory = 6803456 (1661 pages) [...] Apr 1 19:03:32 whimpy /kernel: wdc0 at 0x1f0-0x1f7 irq 14 on isa Apr 1 19:03:32 whimpy /kernel: wdc0: unit 0 (wd0): Apr 1 19:03:32 whimpy /kernel: wd0: 202MB (415264 total sec), 683 cyl, 16 head, 38 sec, bytes/sec 512 Apr 1 19:03:32 whimpy /kernel: wdc1 not found at 0x170 Apr 1 19:03:32 whimpy /kernel: wt0 not found at 0x300 >Description: When I upgraded from 2.0-950210-SNAP to 2.0-950322-SNAP I started getting kernel panics during boot (thus went back to 2.0-950210-SNAP). now when I use -current I get the following: wd0: interrupt timeout: wd0: status 58 error 0 wd0: interrupt timeout: wd0: status 59 error 4 wd0: interrupt timeout: wd0: status d0 error 4 wb0b: wdstart: timeout waiting to give command writing fsbn 840 or 840-863 ( wd0bn 49992; cn 82 tn 3 sn 22) wd0: wdunwedge failed:o and the system seem to hang, I have to power cycle the system to reboot, if I just hit the reset switch it will not boot. >How-To-Repeat: >Fix: >Audit-Trail: >Unformatted: