From owner-freebsd-current Sun Jan 17 00:03:38 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA16752 for freebsd-current-outgoing; Sun, 17 Jan 1999 00:03:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from scotty.masternet.it (scotty.masternet.it [194.184.65.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA16736; Sun, 17 Jan 1999 00:03:34 -0800 (PST) (envelope-from gmarco@scotty.masternet.it) Received: from suzy (modem32.masternet.it [194.184.65.42]) by scotty.masternet.it (8.8.8/8.8.8) with SMTP id JAA15555; Sun, 17 Jan 1999 09:03:02 +0100 (CET) (envelope-from gmarco@scotty.masternet.it) Message-Id: <4.1.19990117085758.009d2ee0@194.184.65.4> X-Sender: gmarco@scotty.masternet.it X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sun, 17 Jan 1999 09:06:46 +0100 To: Andrew Kenneth Milton , merlin@ghostwheel.com (Christopher Knight) From: Gianmarco Giovannelli Subject: Re: Problem booting from aic7890/91 Ultra2 SCSI Cc: current@FreeBSD.ORG, scsi@FreeBSD.ORG In-Reply-To: <199901170256.MAA01382@zeus.theinternet.com.au> References: <4.1.19990116180852.00a9aea0@pop.ghostwheel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12.56 17/01/99 +1000, Andrew Kenneth Milton wrote: >+----[ Christopher Knight ]--------------------------------------------- >| At 12:49 AM 1/17/99 +0100, Gianmarco Giovannelli wrote: >| > >| >Ok, first the conclusion... >| > >| >I am not able to boot anymore from a 3.0-current system while I can boot >| >quite nicely from the 3.0-RELEASE generic kernel. >| > >| >The system hangs on checking the scsi chain and remains stopped here. The >| >last thing I can see on the screen is the : >| >Waiting 3 seconds for SCSI devices to settle >| > >| >And nothing else happens anymore. So I have to hard reset the box. >| >| >| I have been seeing this for the two weeks or so. A shutdown -r will always >| hang. A complete powerdown has been the only way I can reboot my box of >late. > >I recently (last night) added USB support to my kernel (just to see :-) >and it hung at the same place. Removing the USB entries fixed it. > >This was also at the same time as the syscons/atkbd changeover for me as well >so I wasn't expecting it really to be the USB driver (since I have no >USB devices). > >If you have USB support compiled in try removing it. > I have no USB support compiled, as you can see in my kernel configuration I sent with my last message. Perhaps it's a timing problem or an intrusive check. boh ? Who knows what is changed in the (scsi|cam|adaptec) in the last mounth or so ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 00:12:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA17776 for freebsd-current-outgoing; Sun, 17 Jan 1999 00:12:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA17771 for ; Sun, 17 Jan 1999 00:12:27 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id SAA20515; Sun, 17 Jan 1999 18:42:21 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id SAA15753; Sun, 17 Jan 1999 18:42:19 +1030 (CST) Date: Sun, 17 Jan 1999 18:42:19 +1030 From: Greg Lehey To: Mark Murray Cc: "Jordan K. Hubbard" , Carroll Kong , Edwin Culp , "freebsd-current@FreeBSD.ORG" Subject: Re: Today's Make World Message-ID: <19990117184218.F55525@freebie.lemis.com> References: <4822.916525330@zippy.cdrom.com> <199901170747.JAA16312@greenpeace.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199901170747.JAA16312@greenpeace.grondar.za>; from Mark Murray on Sun, Jan 17, 1999 at 09:47:40AM +0200 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 17 January 1999 at 9:47:40 +0200, Mark Murray wrote: > "Jordan K. Hubbard" wrote: >> We're all seeing this error, not to worry. Happily, it's clearly >> Mark's baby since he both imported the new texinfo *and* does the >> perl5 stuff. :-) > > ... and he is not getting the errors! It obviously knows you :-) > I have done N make worlds in the last 48 hours; clean as a whistle. > (I do blow away /usr/obj/* each time, and I'm pretty anal about > cleaning garbage out of the source tree before building; garbage > includes editor backup files, .#* files from CVS, .o .so files from > builds without obj/ and so forth. I want the tree to be _really_ > clean before I try). It looks as if it's missing a header file. Maybe it's finding it elsewhere on your system. I had the problem too, and the backout trick worked for me too. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 00:44:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA19680 for freebsd-current-outgoing; Sun, 17 Jan 1999 00:44:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA19675 for ; Sun, 17 Jan 1999 00:44:53 -0800 (PST) (envelope-from randy@psg.com) Received: from localhost (3899 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Sun, 17 Jan 1999 00:44:50 -0800 (PST) (Smail-3.2.0.101 1997-Dec-17 #1 built 1998-Oct-13) Message-Id: Date: Sun, 17 Jan 1999 00:44:50 -0800 (PST) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-current@FreeBSD.ORG Subject: no sound with fxtv Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG in fxtv, i am still trying to sort out how to get sound from the video card through the sound card. current of 98.12.31 o hauppauge wintv plugged into cable o awe-64 o matrox millennium ii agp i think the problem is really on the video card, or the bt drivers. o the awe-64 works fine with vat in multicast, as does the hauppauge with a camera in vic. o i have the line-out of the hauppauge plugged into the line-in of the awe-64 o in fxtv, when i switch channels or change audio input select, i hear a click through the speakers clues solicited. randy FreeBSD 3.0-CURRENT #0: Sat Jan 9 11:05:57 PST 1999 root@rip.psg.com:/usr/src/sys/compile/RIP Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 300682774 Hz CPU: Pentium II (quarter-micron) (300.68-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping=1 Features=0x183fbff> real memory = 134217728 (131072K bytes) config> quit avail memory = 128040960 (125040K bytes) Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x02 on pci0.1.0 chip2: rev 0x02 on pci0.4.0 chip3: rev 0x02 on pci0.4.3 ahc0: rev 0x00 int a irq 15 on pci0.6.0 ahc0: aic 7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs fxp0: rev 0x05 int a irq 15 on pci0.9.0 fxp0: Ethernet address 00:a0:c9:df:c8:4e bktr0: rev 0x02 int a irq 10 on pci0.10.0 bti2c0: iicbb0: on bti2c0 iicbus0: on iicbb0 master-only Probing for devices on iicbus0: <80> <81> smbus0: on bti2c0 smb0: on smbus0 Hauppauge WinCast/TV, Philips FR1236 NTSC FM tuner. Probing for devices on PCI bus 1: vga0: rev 0x00 int a irq 11 on pci1.0.0 Probing for PnP devices: CSN 1 Vendor ID: CTL00c3 [0xc3008c0e] Serial 0x1fd0a682 Comp ID: PNPb02f [0x2fb0d041] pcm1 (SB16pnp sn 0x1fd0a682) at 0x220-0x22f irq 5 drq 1 flags 0x15 on isa Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff i rq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0 pcm0 not probed due to drq conflict with pcm1 at 1 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wl0 at 0x300-0x30f irq 7 on isa wl0: address 08:00:6a:2b:dd:a7, NWID 0xaaaa npx0 on motherboard npx0: INT 16 interface ccd0-5: Concatenated disk drivers Waiting 15 seconds for SCSI devices to settle changing root device to da0s1a da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 80.0MB/s transfers (40.0MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 80.0MB/s transfers (40.0MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) cd0 at ah c0 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.0MB/s transfers (20.0MHz, offset 16) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 01:23:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA22012 for freebsd-current-outgoing; Sun, 17 Jan 1999 01:23:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail4.svr.pol.co.uk (mail4.svr.pol.co.uk [195.92.193.211]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA22007 for ; Sun, 17 Jan 1999 01:23:47 -0800 (PST) (envelope-from A.M.Zanker@open.ac.uk) Received: from modem-85.magnesium.dialup.pol.co.uk ([62.136.5.213] helo=jemima) by mail4.svr.pol.co.uk with smtp (Exim 2.10 #1) id 101oQb-0008Jd-00; Sun, 17 Jan 1999 09:23:29 +0000 Message-Id: <4.1.19990116231755.009f8c40@aire.open.ac.uk> Message-Id: <4.1.19990116231755.009f8c40@aire.open.ac.uk> X-Sender: mikez@aire.open.ac.uk X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sat, 16 Jan 1999 23:21:42 +0000 To: jack From: Mike Zanker Subject: Re: trivial rc/rc.local observation Cc: current@FreeBSD.ORG In-Reply-To: References: <4.1.19990116192533.009e8820@aire.open.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 21:11 16/01/99 , jack wrote: >rc.local was removed from the tree on Dec. 12th. If you're still >using it you're on your own, edit it as you wish. :) Oops - I'd better delete it then. I've always updated /etc from src/etc but never compared for removals. Thanks, Mike -- Mike Zanker, Academic Computing Service, The Open University, UK Tel: +44 1908 652726, Fax: +44 1908 652193 Views expressed are personal and do not necessarily reflect University opinion. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 01:38:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA23195 for freebsd-current-outgoing; Sun, 17 Jan 1999 01:38:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA23185 for ; Sun, 17 Jan 1999 01:38:07 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id LAA09842; Sun, 17 Jan 1999 11:37:59 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.2/8.9.2) with ESMTP id LAA16540; Sun, 17 Jan 1999 11:37:56 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199901170937.LAA16540@greenpeace.grondar.za> To: "Jordan K. Hubbard" cc: "freebsd-current@FreeBSD.ORG" Subject: Re: Today's Make World In-Reply-To: Your message of " Sat, 16 Jan 1999 23:49:03 PST." <641.916559343@zippy.cdrom.com> References: <641.916559343@zippy.cdrom.com> Date: Sun, 17 Jan 1999 11:37:55 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > Every -current release I try and build falls over with this one. > Tried making a release lately? :) Aaaah! _Releases_ are broken? For how long? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 01:56:02 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA24675 for freebsd-current-outgoing; Sun, 17 Jan 1999 01:56:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA24648 for ; Sun, 17 Jan 1999 01:55:54 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id LAA09870; Sun, 17 Jan 1999 11:55:48 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.2/8.9.2) with ESMTP id LAA16641; Sun, 17 Jan 1999 11:55:47 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199901170955.LAA16641@greenpeace.grondar.za> To: "Jordan K. Hubbard" cc: "freebsd-current@FreeBSD.ORG" Subject: Re: Today's Make World In-Reply-To: Your message of " Sat, 16 Jan 1999 23:49:03 PST." <641.916559343@zippy.cdrom.com> References: <641.916559343@zippy.cdrom.com> Date: Sun, 17 Jan 1999 11:55:46 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > Every -current release I try and build falls over with this one. > Tried making a release lately? :) OK - I got it! I backed out a commit and things are rosy. Have I mentioned before that I hate the Perl5 build? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 01:56:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA24706 for freebsd-current-outgoing; Sun, 17 Jan 1999 01:56:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA24693 for ; Sun, 17 Jan 1999 01:56:05 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id BAA01149; Sun, 17 Jan 1999 01:56:05 -0800 (PST) To: Mark Murray cc: "freebsd-current@FreeBSD.ORG" Subject: Re: Today's Make World In-reply-to: Your message of "Sun, 17 Jan 1999 11:37:55 +0200." <199901170937.LAA16540@greenpeace.grondar.za> Date: Sun, 17 Jan 1999 01:56:04 -0800 Message-ID: <1145.916566964@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Aaaah! _Releases_ are broken? For how long? Since the 12th, but don't worry - it was only your problem for the last couple of days. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 02:00:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA25334 for freebsd-current-outgoing; Sun, 17 Jan 1999 02:00:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA25327 for ; Sun, 17 Jan 1999 02:00:27 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id MAA09899; Sun, 17 Jan 1999 12:00:16 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.2/8.9.2) with ESMTP id MAA16710; Sun, 17 Jan 1999 12:00:16 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199901171000.MAA16710@greenpeace.grondar.za> To: "Jordan K. Hubbard" cc: "freebsd-current@FreeBSD.ORG" Subject: Re: Today's Make World In-Reply-To: Your message of " Sun, 17 Jan 1999 01:56:04 PST." <1145.916566964@zippy.cdrom.com> References: <1145.916566964@zippy.cdrom.com> Date: Sun, 17 Jan 1999 12:00:15 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > > Aaaah! _Releases_ are broken? For how long? > > Since the 12th, but don't worry - it was only your problem for the > last couple of days. :) OK - but losing stdio.h?? :-) That confuses the crap out of me. Anyone been screwing with build tools? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 02:13:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA26137 for freebsd-current-outgoing; Sun, 17 Jan 1999 02:13:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id CAA26128 for ; Sun, 17 Jan 1999 02:13:43 -0800 (PST) (envelope-from fenner@parc.xerox.com) Received: from mango.parc.xerox.com ([13.1.102.232]) by alpha.xerox.com with SMTP id <52793(5)>; Sun, 17 Jan 1999 02:13:39 PST Received: from mango.parc.xerox.com (localhost.parc.xerox.com [127.0.0.1]) by mango.parc.xerox.com (8.8.8/8.8.8) with ESMTP id CAA11289; Sun, 17 Jan 1999 02:13:35 -0800 (PST) (envelope-from fenner@mango.parc.xerox.com) Message-Id: <199901171013.CAA11289@mango.parc.xerox.com> To: Mark Murray cc: "freebsd-current@FreeBSD.ORG" Subject: Re: Today's Make World In-reply-to: Your message of "Sun, 17 Jan 1999 02:00:15 PST." <199901171000.MAA16710@greenpeace.grondar.za> Date: Sun, 17 Jan 1999 02:13:35 PST From: Bill Fenner Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199901171000.MAA16710@greenpeace.grondar.za> Mark Murray wrote: >OK - but losing stdio.h?? :-) That confuses the crap out of me. Anyone >been screwing with build tools? Uh, the failing command in my log file included "-nostdinc"; that does a good job of hiding friends like stdio.h... Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 02:37:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA28169 for freebsd-current-outgoing; Sun, 17 Jan 1999 02:37:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA28161 for ; Sun, 17 Jan 1999 02:37:05 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id MAA09960; Sun, 17 Jan 1999 12:36:59 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.2/8.9.2) with ESMTP id MAA16835; Sun, 17 Jan 1999 12:36:57 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199901171036.MAA16835@greenpeace.grondar.za> To: Bill Fenner cc: "freebsd-current@FreeBSD.ORG" Subject: Re: Today's Make World In-Reply-To: Your message of " Sun, 17 Jan 1999 02:13:35 PST." <199901171013.CAA11289@mango.parc.xerox.com> References: <199901171013.CAA11289@mango.parc.xerox.com> Date: Sun, 17 Jan 1999 12:36:56 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Fenner wrote: > In message <199901171000.MAA16710@greenpeace.grondar.za> Mark Murray wrote: > >OK - but losing stdio.h?? :-) That confuses the crap out of me. Anyone > >been screwing with build tools? > > Uh, the failing command in my log file included "-nostdinc"; that > does a good job of hiding friends like stdio.h... Right, but there was a -I/usr/obj/...tmp.../someplace/include in there to get the build environment's headers. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 02:49:41 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA28902 for freebsd-current-outgoing; Sun, 17 Jan 1999 02:49:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA28890; Sun, 17 Jan 1999 02:49:37 -0800 (PST) (envelope-from se@dialup124.zpr.uni-koeln.de) Received: from dialup124.zpr.Uni-Koeln.DE (dialup124.zpr.Uni-Koeln.DE [134.95.219.124]) by Sisyphos.MI.Uni-Koeln.DE (8.8.7/8.8.7) with ESMTP id LAA10546; Sun, 17 Jan 1999 11:49:30 +0100 (MET) Received: (from se@localhost) by dialup124.zpr.Uni-Koeln.DE (8.9.1/8.6.9) id XAA00459; Sat, 16 Jan 1999 23:54:37 +0100 (CET) Date: Sat, 16 Jan 1999 23:54:36 +0100 From: Stefan Esser To: freebsd-current@FreeBSD.ORG Cc: Stefan Esser Subject: Re: boot single with new loader? Message-ID: <19990116235436.B382@dialup124.mi.uni-koeln.de> Reply-To: se@FreeBSD.ORG Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <009c01be3b2c$92e60320$236319ac@w142844.carlson.com> <19990111231143.A83935@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <19990111231143.A83935@keltia.freenix.fr>; from Ollivier Robert on Mon, Jan 11, 1999 at 11:11:43PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-01-11 23:11 +0100, Ollivier Robert wrote: > According to Thomas T. Veldhouse: > > the root slice as sync. I figured it was safer, and it wasn't that > > important to me to have that particular slice on softupdates anyway. > > Beware of something that can be deadly for a "make installworld". When > using SU, space freed by "rm" takes a bit more time to be taken into account > and you can fill "/" or "/usr" up because the space recovered by "install" > is not yet freed. > > It happened to me a few times for "/usr" and one time for "/". Having > "/bin/sh" with a 0-byte size is not good for booting :-) Yes, that forced me to turn off soft-updates for the / file system. I was lucky not to have tried rebooting the system, since then there would not have been a chance to invoke a shell (and lots of other binaries that had not made it to /bin and /sbin) from within /usr/obj ! I found that I need 3 times the size of the binaries in / during the "make install" phase, if softupdates is enabled! With more than 11MB in /bin and /sbin, I need some 20MB of free space in /, or the file system will fill up and files will be missing ! I warned about this, a few months ago, after it first hit me. Can't we work around this, for example by waking up the update daemon when the disk is nearly full ? This may call degradation of performance, but will help avoid spurious disk full situations on file systems that appear to have lots (possibly tens) of MB of free space, when you look at them a minute later ... Having a process sleep for some fraction of a second (or possibly more) in a disk full situation, when in fact many blocks have been freed and are awaiting a soft-updates commit to disk, may also be better than to have the processes fail! Regards, STefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 02:58:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA00320 for freebsd-current-outgoing; Sun, 17 Jan 1999 02:58:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Wit401305.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA00312 for ; Sun, 17 Jan 1999 02:58:10 -0800 (PST) (envelope-from daeron@Wit401305.student.utwente.nl) Received: from localhost (daeron@localhost) by Wit401305.student.utwente.nl (8.9.2/8.9.2) with ESMTP id LAA12660 for ; Sun, 17 Jan 1999 11:58:05 +0100 (CET) (envelope-from daeron@Wit401305.student.utwente.nl) Date: Sun, 17 Jan 1999 11:58:05 +0100 (CET) From: Pascal Hofstee To: freebsd-current@FreeBSD.ORG Subject: acd-driver Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am trying for a while now to get the acd-driver working but I just can't find the way ... can anybody explain to me how to config the kernel to support an ATAPI CD-ROM .. (I have the CD-ROM hooked up to the primary slave controller) -------------------- Pascal Hofstee - daeron@shadowmere.student.utwente.nl -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS d- s+: a-- C++ UB++++ P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP-- t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 06:16:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA19482 for freebsd-current-outgoing; Sun, 17 Jan 1999 06:16:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from PacHell.TelcoSucks.org (PacHell.TelcoSucks.org [207.90.181.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA19476 for ; Sun, 17 Jan 1999 06:16:33 -0800 (PST) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.1/8.9.1) id GAA13004 for current@FreeBSD.org; Sun, 17 Jan 1999 06:16:42 -0800 (PST) (envelope-from ulf) Message-ID: <19990117061641.D28911@TelcoSucks.org> Date: Sun, 17 Jan 1999 06:16:42 -0800 From: Ulf Zimmermann To: current@FreeBSD.ORG Subject: possible problem with new boot loader ? Reply-To: ulf@Alameda.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.0-19980930-BETA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Not sure if I am just to stupid or if this is a bug. My system has 2 IDE drives and then several SCSI drives. FreeBSD is on the first scsi drive, so da0. Root is da0s1a. Bios sees the drive as the 3. When the new boot loader comes up with no /boot.config, it prints 2:da(2,a)/boot/loader, which isn't right, as it should be 2:da(0,a). If I now press a key and enter 2:da(0,a), it complains it can't find /boot/loader. Entering 2:da(0,a)/kernel works fine and that is what i have now in my boot.conf. Could this be a bug or not? -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 06:27:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA20669 for freebsd-current-outgoing; Sun, 17 Jan 1999 06:27:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA20664 for ; Sun, 17 Jan 1999 06:27:28 -0800 (PST) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt1-71.HiWAAY.net [208.147.147.71]) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id IAA18258 for ; Sun, 17 Jan 1999 08:27:23 -0600 (CST) Received: from nospam.hiwaay.net (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.1/8.9.1) with ESMTP id IAA01013 for ; Sun, 17 Jan 1999 08:27:22 -0600 (CST) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <199901171427.IAA01013@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG From: David Kelly Subject: Re: boot single with new loader? In-reply-to: Message from Stefan Esser of "Sat, 16 Jan 1999 23:54:36 +0100." <19990116235436.B382@dialup124.mi.uni-koeln.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 17 Jan 1999 08:27:22 -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stefan Esser writes: > On 1999-01-11 23:11 +0100, Ollivier Robert wrote: > > > > Beware of something that can be deadly for a "make installworld". When > > using SU, space freed by "rm" takes a bit more time to be taken into account > > and you can fill "/" or "/usr" up because the space recovered by "install" > > is not yet freed. > > > > It happened to me a few times for "/usr" and one time for "/". Having > > "/bin/sh" with a 0-byte size is not good for booting :-) > > Yes, that forced me to turn off soft-updates for the / file system. > I was lucky not to have tried rebooting the system, since then there > would not have been a chance to invoke a shell (and lots of other > binaries that had not made it to /bin and /sbin) from within /usr/obj ! Maybe something like this was happening to me yesterday. I too have softupdates on root and everything. Rebooted more times yesterday than ever messing with a soundcard and updating kernel. 4 or 5 times /etc/nologin did not get unlinked before the system halted. Forced me to login as root to remove the troublemaker manually. The problem always happened when I issued shutdown as myself (not root) but as a member of group operator. But has now cured itself possibly due to replacing /etc/ login.{conf,access} and /etc/rc* with current versions. This is what / etc/nologin contained altho "shutdown -r now" was the command used: NO LOGINS: System going down at 18:00 -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 06:31:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA21161 for freebsd-current-outgoing; Sun, 17 Jan 1999 06:31:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bs1-highway1.skyman (ns.modem.ru [212.57.132.253]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA21154 for ; Sun, 17 Jan 1999 06:31:05 -0800 (PST) (envelope-from igorsh@garural.chel.su) Received: from garural.chel.su (garant-ural.ru [195.54.6.129]) by bs1-highway1.skyman (8.6.12/8.6.12) with ESMTP id TAA13126 for ; Sun, 17 Jan 1999 19:30:21 +0500 Received: from igorsh.garural.chel.su (igorsh.garant-ural.ru [195.54.6.135]) by garural.chel.su (8.9.1/8.9.1) with SMTP id TAA00302 for ; Sun, 17 Jan 1999 19:30:44 +0500 (ES) (envelope-from igorsh@garural.chel.su) Message-ID: <003301be4226$21772740$870636c3@igorsh.garural.chel.su> From: "Igor Shulgin" To: "FreeBSD-current" Subject: Running old program on 3.0-RELEASE Date: Sun, 17 Jan 1999 19:31:53 +0500 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently installed 3.0-RELEASE on existing 2.1.0-RELEASE. After that one program does not run any more. That program is being invoked by Apache daemon (now I use Apache 1.2.6 from 3.0-RELEASE/packages) and is needed for access to some special part of our WWW-server. After attempt of invocation this program accordingly to user's action next message appears in /var/log/httpd-error.log : "ld.so failed: Can't find shared library "libg++.so.3.0"" User is seeing message "500 Internal Server Error" on his screen. I have no influence on author of program mentioned above to prompt him to recompile his program on 3.0-RELEASE. As I know this program successful works on pack of 2.1.x and 2.2.x systems. I run "ldconfig -r" and not found "libg++.so.3.0" in list. File /usr/lib/libg++.so.3.0 exist but have old date "Nov 16 1995" because this file remained from old version. There is new file /usr/lib/compat/libg++.so.3.0 with date "Oct 16 1997". There is line ldconfig_paths="/usr/lib/compat /usr/X11R6/lib /usr/local/lib" in file /etc/rc.conf and I see messages at rebooting about successful running ldconfig on these directories. Output of "ldconfig -r" has 1st and 2nd line: "/var/run/ld-elf.so.hints searching directories: /usr/lib:/usr/lib/compat:/usr/local/lib " But there are not files from /usr/lib/compat in list. Is something incorrectly installed in my system? Should I remove all files from /usr/lib with date "16 Nov 1995" and earlier? Must I remove directory /usr/lib before any installation newer version above older? Thanks in advance. --- With good wishes, Igor Shulgin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 06:51:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA22632 for freebsd-current-outgoing; Sun, 17 Jan 1999 06:51:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA22627 for ; Sun, 17 Jan 1999 06:51:28 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id JAA17066; Sun, 17 Jan 1999 09:51:13 -0500 (EST) Date: Sun, 17 Jan 1999 09:51:12 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Igor Shulgin cc: FreeBSD-current Subject: Re: Running old program on 3.0-RELEASE In-Reply-To: <003301be4226$21772740$870636c3@igorsh.garural.chel.su> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 17 Jan 1999, Igor Shulgin wrote: > I recently installed 3.0-RELEASE on existing 2.1.0-RELEASE. > After that one program does not run any more. > That program is being invoked by Apache daemon (now I use Apache 1.2.6 from > 3.0-RELEASE/packages) and is needed for access to some special part of our > WWW-server. After attempt of invocation this program accordingly to user's > action next message appears in /var/log/httpd-error.log : > "ld.so failed: Can't find shared library "libg++.so.3.0"" > User is seeing message "500 Internal Server Error" on his screen. > I have no influence on author of program mentioned above to prompt him to > recompile his program on 3.0-RELEASE. As I know this program successful works > on pack of 2.1.x and 2.2.x systems. > > I run "ldconfig -r" and not found "libg++.so.3.0" in list. > File /usr/lib/libg++.so.3.0 exist but have old date "Nov 16 1995" because > this file remained from old version. There is new file > /usr/lib/compat/libg++.so.3.0 with date "Oct 16 1997". There is line > ldconfig_paths="/usr/lib/compat /usr/X11R6/lib /usr/local/lib" > in file /etc/rc.conf and I see messages at rebooting about successful running > ldconfig on these directories. > Output of "ldconfig -r" has 1st and 2nd line: > "/var/run/ld-elf.so.hints > searching directories: /usr/lib:/usr/lib/compat:/usr/local/lib " > But there are not files from /usr/lib/compat in list. > > Is something incorrectly installed in my system? > Should I remove all files from /usr/lib with date "16 Nov 1995" and earlier? > Must I remove directory /usr/lib before any installation newer version above > older? > > Thanks in advance. All old /usr/lib files need to be moved to /usr/lib/compat or /usr/lib/aout. /usr/lib/compat is the better place because it contains OLD, not current, libs. Hint: do NOT save the archives "libfoo.a", they're for building new static executables, and you don't want to replace your much more current ars. Did you even try installing "compat21 compat22 compat1x" etc? > > --- With good wishes, > Igor Shulgin > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 08:20:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00997 for freebsd-current-outgoing; Sun, 17 Jan 1999 08:20:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bs1-highway1.skyman (ns.modem.ru [212.57.132.253]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA00959 for ; Sun, 17 Jan 1999 08:20:01 -0800 (PST) (envelope-from igorsh@garural.chel.su) Received: from garural.chel.su (garant-ural.ru [195.54.6.129]) by bs1-highway1.skyman (8.6.12/8.6.12) with ESMTP id VAA13215; Sun, 17 Jan 1999 21:19:16 +0500 Received: from igorsh.garural.chel.su (igorsh.garant-ural.ru [195.54.6.135]) by garural.chel.su (8.9.1/8.9.1) with SMTP id VAA00491; Sun, 17 Jan 1999 21:19:40 +0500 (ES) (envelope-from igorsh@garural.chel.su) Message-ID: <008301be4235$5988f3c0$870636c3@igorsh.garural.chel.su> From: "Igor Shulgin" To: "Brian Feldman" Cc: "FreeBSD-current" Subject: Re: Running old program on 3.0-RELEASE Date: Sun, 17 Jan 1999 21:20:49 +0500 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Feldman wrote: >All old /usr/lib files need to be moved to /usr/lib/compat or /usr/lib/aout. >/usr/lib/compat is the better place because it contains OLD, not current, libs. What about files which already exist in /usr/lib/compat directory with same name but new date? Move them to /usr/lib/aout (may be to /usr/lib/compat/aout ?) or simly remove them? libg++.so.3.0 is such case. >Hint: do NOT save the archives "libfoo.a", they're for building new static >executables, and you don't want to replace your much more current ars. Did you >even try installing "compat21 compat22 compat1x" etc? Of course. During installation I not checked "compat" but after installation I run install.sh from compat1x compat21 compat22 directories of 3.0-RELEASE distribution (in this order). Have order the meaning? >> --- With good wishes, >> Igor Shulgin >> > Brian Feldman _ __ ___ ___ ___ > green@unixhelp.org _ __ ___ | _ ) __| \ > http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | > FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 08:29:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA01708 for freebsd-current-outgoing; Sun, 17 Jan 1999 08:29:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oreo.adsu.bellsouth.com (oreo.adsu.bellsouth.com [205.152.173.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA01701 for ; Sun, 17 Jan 1999 08:29:30 -0800 (PST) (envelope-from ck@oreo.adsu.bellsouth.com) Received: (from ck@localhost) by oreo.adsu.bellsouth.com (8.9.1/8.9.1) id LAA19862 for freebsd-current@freebsd.org; Sun, 17 Jan 1999 11:29:26 -0500 (EST) (envelope-from ck) Date: Sun, 17 Jan 1999 11:29:25 -0500 From: Christian Kuhtz To: freebsd-current@FreeBSD.ORG Subject: ufs async Message-ID: <19990117112925.A19618@oreo.adsu.bellsouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey gang: Somebody mentioned the other day that UFS async isn't entirely async, and that directories are (always) sync. Is that true? Can somebody elaborate on why that is? Cheers, Chris -- "We are not bound by any concept, we are just bound to make any concept work better than others." -- Dr. Ferry Porsche [Disclaimer: I speak for myself and my views are my own and not in any way to be construed as the views of BellSouth Corporation. ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 08:31:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA02073 for freebsd-current-outgoing; Sun, 17 Jan 1999 08:31:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-25-dbn.dial-up.net [196.34.155.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA02063 for ; Sun, 17 Jan 1999 08:31:20 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id SAA26217; Sun, 17 Jan 1999 18:29:33 +0200 (SAT) From: Robert Nordier Message-Id: <199901171629.SAA26217@ceia.nordier.com> Subject: Re: possible problem with new boot loader ? In-Reply-To: <19990117061641.D28911@TelcoSucks.org> from Ulf Zimmermann at "Jan 17, 99 06:16:42 am" To: ulf@Alameda.net Date: Sun, 17 Jan 1999 18:29:30 +0200 (SAT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ulf Zimmermann wrote: > Not sure if I am just to stupid or if this is a bug. My system has > 2 IDE drives and then several SCSI drives. FreeBSD is on the first > scsi drive, so da0. Root is da0s1a. Bios sees the drive as the 3. > > When the new boot loader comes up with no /boot.config, it prints > 2:da(2,a)/boot/loader, which isn't right, as it should be 2:da(0,a). > If I now press a key and enter 2:da(0,a), it complains it can't find > /boot/loader. Entering 2:da(0,a)/kernel works fine and that is > what i have now in my boot.conf. > > Could this be a bug or not? There are two issues here: o The bootblocks get the SCSI unit number wrong in cases where IDE drives are also attached. This is to be expected. There is just insufficient space available to the bootblocks for "smarter" logic. The old bootblocks have a build setting BOOT_HD_BIAS to work around this problem. The new bootblocks rely on /boot.config. You can have 2:da(0,a) in /boot.config (ie. without a kernel name) to override just the unit number. o The /boot/loader program just isn't being found. Are you sure this actually exists? What shows up if you enter 2:da(0,a)/boot/? (to get a directory listing of /boot) at the "boot:" prompt? Incidentally, do these bootblocks contain the BTX patch I sent you, or did you find some other way around that problem? -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 08:38:42 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA02748 for freebsd-current-outgoing; Sun, 17 Jan 1999 08:38:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA02742 for ; Sun, 17 Jan 1999 08:38:39 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id LAA22367; Sun, 17 Jan 1999 11:38:29 -0500 (EST) Date: Sun, 17 Jan 1999 11:38:29 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Igor Shulgin cc: FreeBSD-current Subject: Re: Running old program on 3.0-RELEASE In-Reply-To: <008301be4235$5988f3c0$870636c3@igorsh.garural.chel.su> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 17 Jan 1999, Igor Shulgin wrote: > Brian Feldman wrote: > >All old /usr/lib files need to be moved to /usr/lib/compat or /usr/lib/aout. > >/usr/lib/compat is the better place because it contains OLD, not current, > libs. > > What about files which already exist in /usr/lib/compat directory with same > name but new date? Move them to /usr/lib/aout (may be to /usr/lib/compat/aout > ?) or simly remove them? libg++.so.3.0 is such case. > > >Hint: do NOT save the archives "libfoo.a", they're for building new static > >executables, and you don't want to replace your much more current ars. Did > you > >even try installing "compat21 compat22 compat1x" etc? > > > Of course. During installation I not checked "compat" but after installation > I run install.sh from compat1x compat21 compat22 directories of 3.0-RELEASE > distribution (in this order). Have order the meaning? Okay, try this: /bin/sh cd /usr/lib for i in *; do if file $i | grep FreeBSD/i386 >/dev/null; then rm $i; fi done After doing that, look in /etc/rc.conf and check if you have an ldconfig_paths_aout. If you don't, set it to something on the order of "/usr/X11R6/lib/aout /usr/local/lib/aout /usr/lib/aout /usr/lib/compat/aout /usr/lib/compat". Then try typing ldconfig -aout /usr/X11R6/lib/aout /usr/local/lib/aout \ /usr/lib/aout /usr/lib/compat/aout /usr /lib/compat You may want to also clean out /usr/local/lib, /usr/X11R6/lib, etc. to make certain no a.out is there. I'd do something like cd /usr/local/lib; mkdir aout for i in *; do if file $i | grep FreeBSD/i386 >/dev/null; then mv $i aout; fi \ done Cheers, > > >> --- With good wishes, > >> Igor Shulgin > >> > > Brian Feldman _ __ ___ ___ ___ > > green@unixhelp.org _ __ ___ | _ ) __| \ > > http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | > > FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ > > > > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 08:40:52 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA03159 for freebsd-current-outgoing; Sun, 17 Jan 1999 08:40:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA03154 for ; Sun, 17 Jan 1999 08:40:50 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id JAA09341; Sun, 17 Jan 1999 09:32:28 -0700 (MST) Date: Sun, 17 Jan 1999 09:32:28 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199901171632.JAA09341@narnia.plutotech.com> To: Gianmarco Giovannelli cc: current@FreeBSD.ORG Subject: Re: Problem booting from aic7890/91 Ultra2 SCSI X-Newsgroups: pluto.freebsd.current In-Reply-To: <4.1.19990117003737.009d4a80@194.184.65.4> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <4.1.19990117003737.009d4a80@194.184.65.4> you wrote: > > Ok, first the conclusion... > > I am not able to boot anymore from a 3.0-current system while I can boot > quite nicely from the 3.0-RELEASE generic kernel. What revision of aic7xxx.c do you have? I introduced a bug in rev 1.15 that was fixed a day or so later. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 08:46:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA03432 for freebsd-current-outgoing; Sun, 17 Jan 1999 08:46:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA03427 for ; Sun, 17 Jan 1999 08:46:27 -0800 (PST) (envelope-from fbsd@Ilsa.StevesCafe.com) Received: from Ilsa.StevesCafe.com (localhost.StevesCafe.com [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.8/8.8.5) with ESMTP id JAA14204; Sun, 17 Jan 1999 09:52:22 -0700 (MST) Message-Id: <199901171652.JAA14204@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0.2 2/24/98 From: Steve Passe To: "Jordan K. Hubbard" cc: current@FreeBSD.ORG Subject: Re: Annoying messages on startup.. In-reply-to: Your message of "Sat, 16 Jan 1999 23:16:57 PST." <199901170716.XAA00345@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 17 Jan 1999 09:52:21 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > jkh@zippy-> dmesg|grep Freeing > Freeing (NOT implemented) redirected ISA irq 11. > Freeing (NOT implemented) redirected ISA irq 10. > Freeing (NOT implemented) redirected ISA irq 10. > Freeing (NOT implemented) redirected ISA irq 10. > Freeing (NOT implemented) redirected ISA irq 9. > Freeing (NOT implemented) redirected ISA irq 10. > > Can these just go away? They certainly don't tell *me* anything > useful and if it's a feature which should be implemented then > we ought to implement it. If it's just a harmless warning, then > we ought to just remove it. :-) I'm the person who put those there, and yes, they are meant to be annoying. I was hoping that someone who already knew the insides of motherboard chips would pick it up and fix it, but I guess not... Essentially they refer to the fact that an APIC pin is directly connected to a PCI INT, (theoretically) freeing up the ISA path for another INT source on the ISA bus. I believed at the time that this could be done by reprogramming the PCI/ISA redirection circuit in the MB chipset, but never got around to proving it. At the very least they could be moved to "if ( bootverbose ) ..." Someone might also remove the: interrupt mask = cam <- SMP: XXX ^^^^^^^^^^^ from: trap.c: printf(" <- SMP: XXX"); I have no memory as to whether the associated comment is valid! -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 09:13:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA05062 for freebsd-current-outgoing; Sun, 17 Jan 1999 09:13:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA05057 for ; Sun, 17 Jan 1999 09:13:03 -0800 (PST) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.9.2/8.9.2) with ESMTP id MAA60854; Sun, 17 Jan 1999 12:10:34 -0500 (EST) Date: Sun, 17 Jan 1999 12:10:34 -0500 (EST) From: jack To: "Jordan K. Hubbard" cc: current@FreeBSD.ORG Subject: Re: Annoying messages on startup.. In-Reply-To: <199901170716.XAA00345@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 16 Jan 1999, Jordan K. Hubbard wrote: > jkh@zippy-> dmesg|grep Freeing > Freeing (NOT implemented) redirected ISA irq 11. > Freeing (NOT implemented) redirected ISA irq 10. Nowhere near as annoying as "tagged openings now xx". Perhaps `|| 1' could be changed to `|| crs->openings < some critical number' in cam_xpt.c. As it is now a boy and a wolf come to mind. Also, I suspect having acd in the kernel and wcd in MAKEDEV may lead to confusion for some people. -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 09:19:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA05893 for freebsd-current-outgoing; Sun, 17 Jan 1999 09:19:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from scotty.masternet.it (scotty.masternet.it [194.184.65.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA05887 for ; Sun, 17 Jan 1999 09:19:19 -0800 (PST) (envelope-from gmarco@scotty.masternet.it) Received: from suzy (modem32.masternet.it [194.184.65.42]) by scotty.masternet.it (8.8.8/8.8.8) with SMTP id SAA20554; Sun, 17 Jan 1999 18:18:59 +0100 (CET) (envelope-from gmarco@scotty.masternet.it) Message-Id: <4.1.19990117182213.0093b980@194.184.65.4> X-Sender: gmarco@scotty.masternet.it X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sun, 17 Jan 1999 18:27:06 +0100 To: "Justin T. Gibbs" From: Gianmarco Giovannelli Subject: Re: Problem booting from aic7890/91 Ultra2 SCSI Cc: current@FreeBSD.ORG In-Reply-To: <199901171632.JAA09341@narnia.plutotech.com> References: <4.1.19990117003737.009d4a80@194.184.65.4> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 09.32 17/01/99 -0700, you wrote: >In article <4.1.19990117003737.009d4a80@194.184.65.4> you wrote: >> >> Ok, first the conclusion... >> >> I am not able to boot anymore from a 3.0-current system while I can boot >> quite nicely from the 3.0-RELEASE generic kernel. > >What revision of aic7xxx.c do you have? I introduced a bug in rev 1.15 >that was fixed a day or so later. $Id: aic7xxx.c,v 1.16 1999/01/15 23:24:23 gibbs Exp $ Please tell me if I can do anything to boot again :-) Best Regards, Gianmarco Giovannelli (http://www.giovannelli.it/~gmarco) "Unix expert since yesterday" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 09:21:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06285 for freebsd-current-outgoing; Sun, 17 Jan 1999 09:21:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from octopus.originative.co.uk (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06278 for ; Sun, 17 Jan 1999 09:21:42 -0800 (PST) (envelope-from paul@originative.co.uk) From: paul@originative.co.uk Received: by OCTOPUS with Internet Mail Service (5.5.1960.3) id ; Sun, 17 Jan 1999 17:20:08 -0000 Message-ID: To: wollman@khavrinen.lcs.mit.edu, culverk@wam.umd.edu Cc: phiber@udel.edu, current@FreeBSD.ORG Subject: RE: FreeBSD Celeron and Celeron ( Mendocino ) kernel patch. Date: Sun, 17 Jan 1999 17:20:07 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Garrett Wollman [mailto:wollman@khavrinen.lcs.mit.edu] > Sent: Saturday, January 09, 1999 4:22 PM > To: Kenneth Wayne Culver > Cc: Garrett Wollman; Bryan Seitz; current@FreeBSD.ORG > Subject: Re: FreeBSD Celeron and Celeron ( Mendocino ) kernel patch. > > > < Culver said: > > > Well, they are the same in that respect, but the Pentium II > has cache in > > the same package, and most Pentium II's aren't > overclockable. The celeron > > is. > > That's OK -- we don't support overclocking anyway. > > The Celeron does have a cache in the package, BTW. The cache in the > Celeron is this tiny little thing that is actually capable of running > at clock rates of 250 MHz or higher; the actual CPU is a perfectly > ordinary Pentium-II core of the sort that would be labeled as ``450 > MHz'' when coupled with a more expensive cache. (According to my > friend who does VLSI design.) The Celeron chips are intentionally > down-rated by Intel marketing to keep them from cannibalizing the > high-end market. (Remember when upgrading to a faster line printer > meant that a SE would change a single belt?) > > I think we should stick to identifying the core. I disagree. From an user perspective I think it will be confusing to general users to report PII when they think they've got a Celeron. From a support perspective it might be useful to know what CPU is actually installed rather than just the class of CPU. On a related note, I'd be interested in benchmarks for the Celerons, how does the on-chip cache compare to the off-chip cache. Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 09:50:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08553 for freebsd-current-outgoing; Sun, 17 Jan 1999 09:50:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA08472 for ; Sun, 17 Jan 1999 09:49:56 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id SAA08436 for freebsd-current@FreeBSD.ORG; Sun, 17 Jan 1999 18:49:51 +0100 (CET) (envelope-from olli) Date: Sun, 17 Jan 1999 18:49:51 +0100 (CET) From: Oliver Fromme Message-Id: <199901171749.SAA08436@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: New syscons + XFree 3.3.3.1 = problem? Newsgroups: list.freebsd-current Organization: Administration Heim 3 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm using -current as of 1998-01-14 with the new syscons (with separated keyboard driver) and XFree86 3.3.3.1 (XF86_SVGA on a Matrox G200). The keyboard and mouse are plain PS/2 models, they work fine under syscons (i.e. not using XFree). The kernel contains the following entries: controller atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 device psm0 at isa? tty irq 12 device vga0 at isa? port ? conflicts pseudo-device splash device sc0 at isa? tty options MAXCONS=10 options SC_HISTORY_SIZE=500 XFree used to allocate the next free virtual terminal when started (in this case the 11th), but that doesn't happen any- more. Instead, it uses the current one (i.e. if I'm on ttyv3 and start X, it uses ttyv3). Is this intentional, or is it a bug? While the above isn't really a serious problem, the following is: When X has run for some time, the keyboard suddenly starts being unresponsive and unusable. This can happen after a few minutes or after a few hours. There are no error messages, no syslog entries. It looks like the keypresses don't get to XFree anymore, but to the vty beneath. Restarting X helps, until it happens again. Quite annoying. Does anyone else experience the same problems? Am I doing something wrong? What can I do to help tracking down the problem? Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 09:53:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08838 for freebsd-current-outgoing; Sun, 17 Jan 1999 09:53:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bs1-highway1.skyman (ns.modem.ru [212.57.132.253]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA08826 for ; Sun, 17 Jan 1999 09:53:39 -0800 (PST) (envelope-from igorsh@garural.chel.su) Received: from garural.chel.su (garant-ural.ru [195.54.6.129]) by bs1-highway1.skyman (8.6.12/8.6.12) with ESMTP id WAA13298; Sun, 17 Jan 1999 22:52:54 +0500 Received: from igorsh.garural.chel.su (igorsh.garant-ural.ru [195.54.6.135]) by garural.chel.su (8.9.1/8.9.1) with SMTP id WAA00235; Sun, 17 Jan 1999 22:53:18 +0500 (ES) (envelope-from igorsh@garural.chel.su) Message-ID: <00ee01be4242$6e9cd800$870636c3@igorsh.garural.chel.su> From: "Igor Shulgin" To: "Brian Feldman" Cc: "FreeBSD-current" Subject: Re: Running old program on 3.0-RELEASE Date: Sun, 17 Jan 1999 22:54:29 +0500 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Feldman wrote: >Okay, try this: > >/bin/sh >cd /usr/lib >for i in *; do if file $i | grep FreeBSD/i386 >/dev/null; then rm $i; fi done > >After doing that, look in /etc/rc.conf and check if you have an >ldconfig_paths_aout. If you don't, set it to something on the order of >"/usr/X11R6/lib/aout /usr/local/lib/aout /usr/lib/aout /usr/lib/compat/aout /usr/lib/compat". >Then try typing ldconfig -aout /usr/X11R6/lib/aout /usr/local/lib/aout \ >/usr/lib/aout /usr/lib/compat/aout /usr /lib/compat Thank you very much for your help! After doing this I see strange (for me) thing: files in /usr/lib/compat is not showed in "ldconfig -r -elf" nor "ldconfig -r -aout". After this I move directory /usr/lib/compat from ldconfig_paths to ldconfig_paths_aout in file rc.conf . And now all works! Is it mistake in file rc.conf (I did not modify it before) or my system is incorrectly configuring? --- With good wishes, Igor Shulgin >> > Brian Feldman _ __ ___ ___ ___ >> > green@unixhelp.org _ __ ___ | _ ) __| \ >> > http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | >> > FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ >> >> >> >> > > Brian Feldman _ __ ___ ___ ___ > green@unixhelp.org _ __ ___ | _ ) __| \ > http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | > FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 10:04:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA09853 for freebsd-current-outgoing; Sun, 17 Jan 1999 10:04:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA09846 for ; Sun, 17 Jan 1999 10:04:16 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id NAA53090; Sun, 17 Jan 1999 13:09:41 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Sun, 17 Jan 1999 13:09:41 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Christian Kuhtz cc: freebsd-current@FreeBSD.ORG Subject: Re: ufs async In-Reply-To: <19990117112925.A19618@oreo.adsu.bellsouth.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 17 Jan 1999, Christian Kuhtz wrote: > > Hey gang: > > Somebody mentioned the other day that UFS async isn't entirely async, and > that directories are (always) sync. Is that true? not afaik. > Can somebody elaborate on why that is? normal UFS mounts are async in respect to data, however meta-data/directory-ops are done sync so that your filesystem doesn't resemble the aftermath of "squril VS 18-wheeler" in the case of a power outage/crash you CAN mount UFS totally async, but then if you incorrectly shutdown your box prepare to recreate the filesystem (*) in 3.0 you have the option of 'softupdates' if you qualify for the license, look in the /usr/src/contrib/sys/softupdates/README for an explanation. softupdates allow for safe async because writes to the meta-data are ordered in a failsafe manner. -Alfred (*) i used to mount async for builds and compiling at times a while back, i never had massive destruction, but you never know, i suspect renaming your /usr and hitting the reset button would be considered fatal if timed properly > > Cheers, > Chris > > -- > "We are not bound by any concept, we are just bound to make any concept work > better than others." -- Dr. Ferry Porsche > > [Disclaimer: I speak for myself and my views are my own and not in any way to > be construed as the views of BellSouth Corporation. ] > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 10:14:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10922 for freebsd-current-outgoing; Sun, 17 Jan 1999 10:14:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA10905 for ; Sun, 17 Jan 1999 10:14:27 -0800 (PST) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt4-170.HiWAAY.net [208.166.127.170]) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id MAA30906; Sun, 17 Jan 1999 12:14:23 -0600 (CST) Received: from nospam.hiwaay.net (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.1/8.9.1) with ESMTP id JAA01243; Sun, 17 Jan 1999 09:11:08 -0600 (CST) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <199901171511.JAA01243@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: Ollivier Robert cc: freebsd-current@FreeBSD.ORG From: David Kelly Subject: nologin file (was: Re: Symbios 875 activity LED?) In-reply-to: Message from Ollivier Robert of "Sun, 17 Jan 1999 12:37:26 +0100." <19990117123726.A73895@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 17 Jan 1999 09:11:07 -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Probably belongs in -current rather than -scsi. Ollivier Robert writes: > According to David Kelly: > > member of group "operator") that /etc/nologin was not being deleted. > > It has been moved recently to /var/run/nologin: Noticed that in shutdown.8 (keep trying to type "sendmail" here). I see /etc/login.conf has the default user set to honor :nologin=/var/run/nologin:\ Apparently updating my login.conf cured my nologin lockout problems due to the above line as: nospam: [1009] ls -l /etc/nologin -rw-r--r-- 1 root wheel 41 Jan 16 21:27 /etc/nologin nospam: [1010] ls -lu `which shutdown` -r-sr-x--- 1 root operator 149920 Jan 16 20:32 /sbin/shutdown* nospam: [1011] Now that's interesting. /etc/nologin is newer than shutdown was last used. Think that's because I've started using control-alt-delete of recent. What does control-alt-delete launch that would create the above nologin file as I need to update that too? But am still concerned whatever it is is not unlinking it before system halt. > -=-=- > asami 1999/01/11 01:07:42 PST > > Modified files: > etc login.conf rc > include paths.h > sbin/shutdown shutdown.8 > usr.bin/login login.1 > Log: > Move nologin from /etc to /var/run. This means one less file that has > to be written to /etc. > > The only essential change is in paths.h, so any third-party software > written correctly will pick it up in the next rebuild. > -=-=- Arrgh. Now I see it. My /usr/include/paths.h is from November 8. This accounts for shutdown. So what else creates /etc/nologin? Short of a new "make world" I need to update paths.h and build a new shutdown. But what else? And is there a way to extract the above commit message out of cvs? Do I need to cvsup something special other than src-all? Only recently subscribed to cvs-all (and -current) and wonder if that's the only place to get it? -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 10:27:41 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA12236 for freebsd-current-outgoing; Sun, 17 Jan 1999 10:27:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA12231 for ; Sun, 17 Jan 1999 10:27:39 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id NAA28276; Sun, 17 Jan 1999 13:27:30 -0500 (EST) Date: Sun, 17 Jan 1999 13:27:30 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Igor Shulgin cc: FreeBSD-current Subject: Re: Running old program on 3.0-RELEASE In-Reply-To: <00ee01be4242$6e9cd800$870636c3@igorsh.garural.chel.su> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 17 Jan 1999, Igor Shulgin wrote: > Brian Feldman wrote: > > > >Okay, try this: > > > >/bin/sh > >cd /usr/lib > >for i in *; do if file $i | grep FreeBSD/i386 >/dev/null; then rm $i; fi > done > > > >After doing that, look in /etc/rc.conf and check if you have an > >ldconfig_paths_aout. If you don't, set it to something on the order of > >"/usr/X11R6/lib/aout /usr/local/lib/aout /usr/lib/aout /usr/lib/compat/aout > /usr/lib/compat". > >Then try typing ldconfig -aout /usr/X11R6/lib/aout /usr/local/lib/aout \ > >/usr/lib/aout /usr/lib/compat/aout /usr /lib/compat > > > Thank you very much for your help! > After doing this I see strange (for me) thing: files in /usr/lib/compat is > not showed in "ldconfig -r -elf" nor "ldconfig -r -aout". After this I move > directory /usr/lib/compat from ldconfig_paths to ldconfig_paths_aout in file > rc.conf . And now all works! > Is it mistake in file rc.conf (I did not modify it before) or my system is > incorrectly configuring? I use /usr/lib/compat in both of those, because older compat stuff is in there, as is newer. /usr/lib/compat/aout is just aout, but /usr/lib/compat seems to be a mix of ELF and a.out, now. Glad I could help! > > --- With good wishes, > Igor Shulgin > > >> > Brian Feldman _ __ ___ ___ ___ > >> > green@unixhelp.org _ __ ___ | _ ) __| \ > >> > http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | > >> > FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ > >> > >> > >> > >> > > > > Brian Feldman _ __ ___ ___ ___ > > green@unixhelp.org _ __ ___ | _ ) __| \ > > http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | > > FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ > > > > > > > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 10:34:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA12989 for freebsd-current-outgoing; Sun, 17 Jan 1999 10:34:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA12984 for ; Sun, 17 Jan 1999 10:34:24 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 14458 invoked by uid 1001); 17 Jan 1999 18:34:18 +0000 (GMT) To: jack@germanium.xtalwind.net Cc: current@FreeBSD.ORG Subject: Re: Annoying messages on startup.. In-Reply-To: Your message of "Sun, 17 Jan 1999 12:10:34 -0500 (EST)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sun, 17 Jan 1999 19:34:18 +0100 Message-ID: <14456.916598058@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > jkh@zippy-> dmesg|grep Freeing > > Freeing (NOT implemented) redirected ISA irq 11. > > Freeing (NOT implemented) redirected ISA irq 10. > > Nowhere near as annoying as "tagged openings now xx". Agreed. They are confusing to those who don't know what it means. As for me, I just ignore them - ie. they don't do *me* any good either. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 10:55:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14897 for freebsd-current-outgoing; Sun, 17 Jan 1999 10:55:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from osiris.kuniv.edu.kw ([139.141.220.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14845 for ; Sun, 17 Jan 1999 10:54:45 -0800 (PST) (envelope-from root@isis.dynip.com) Received: from localhost (localhost [127.0.0.1]) by osiris.kuniv.edu.kw (8.9.2/8.9.1) with SMTP id VAA61046 for ; Sun, 17 Jan 1999 21:50:51 +0300 (AST) (envelope-from root@isis.dynip.com) Date: Sun, 17 Jan 1999 21:48:22 +0300 (AST) From: Joss Roots X-Sender: root@access1_6.kuniv.edu.kw To: freebsd-current@FreeBSD.ORG Subject: make world & release breakage Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, I've been experiencing breakage of make world very late during the install phase of man pages and rebuilding whatis database.(manually trying to make install in the /src/share/man) completes succefully. make release also breaks at the make readmes phase in /ports directory, the interesting thing is that manually making readmes in the ports directory (of /src) completes successflly. is it a problem with the Makefiles or what, how can I fix. Thanks - MAY THE FORCE BE WITH YOU. ~o .^. ---------------------------- ___ o~ .00 ) Static Email : osiris2002@yahoo.com /| o~ /)( Bouncing Email : root@isis.dynip.com / | | \ Web Site : http://isis.dynip.com:80 (Frames) ___/ | / \ Anon FTP Site : ftp://isis.dynip.com:21 (anonymous) | /''___/ / | Gopher Site : gopher://isis.dynip.com:70 | /'''/___/ | Network News : isis.dynip.com (Read, Post, Xfer) __|/'''/ Mailing Lists : majordomo@isis.dynip.com (public) pgp key : finger root@isis.dynip.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 11:04:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA15741 for freebsd-current-outgoing; Sun, 17 Jan 1999 11:04:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from scotty.masternet.it (scotty.masternet.it [194.184.65.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA15729 for ; Sun, 17 Jan 1999 11:04:35 -0800 (PST) (envelope-from gmarco@scotty.masternet.it) Received: from suzy (modem19.masternet.it [194.184.65.29]) by scotty.masternet.it (8.8.8/8.8.8) with SMTP id UAA21797; Sun, 17 Jan 1999 20:03:40 +0100 (CET) (envelope-from gmarco@scotty.masternet.it) Message-Id: <4.1.19990117201046.009e2ad0@194.184.65.4> X-Sender: gmarco@scotty.masternet.it X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sun, 17 Jan 1999 20:11:47 +0100 To: Christopher Knight From: Gianmarco Giovannelli Subject: Re: Problem booting from aic7890/91 Ultra2 SCSI Cc: current@FreeBSD.ORG In-Reply-To: <4.1.19990116180852.00a9aea0@pop.ghostwheel.com> References: <4.1.19990117003737.009d4a80@194.184.65.4> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 18.10 16/01/99 -0800, you wrote: >At 12:49 AM 1/17/99 +0100, Gianmarco Giovannelli wrote: >> >>Ok, first the conclusion... >> >>I am not able to boot anymore from a 3.0-current system while I can boot >>quite nicely from the 3.0-RELEASE generic kernel. >> >>The system hangs on checking the scsi chain and remains stopped here. The >>last thing I can see on the screen is the : >>Waiting 3 seconds for SCSI devices to settle >> >>And nothing else happens anymore. So I have to hard reset the box. > > >I have been seeing this for the two weeks or so. A shutdown -r will always >hang. A complete powerdown has been the only way I can reboot my box of late. Please try to remove apm0 , if you have ... here it seems to solve the problem (after 15 reboot no problem...) Best Regards, Gianmarco Giovannelli (http://www.giovannelli.it/~gmarco) "Unix expert since yesterday" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 11:25:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA17534 for freebsd-current-outgoing; Sun, 17 Jan 1999 11:25:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA17528 for ; Sun, 17 Jan 1999 11:25:20 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.2/8.9.2/Netplex) with ESMTP id DAA06456 for ; Mon, 18 Jan 1999 03:25:14 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199901171925.DAA06456@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: HEADS UP: i386 a.out LKM support now an option.. Date: Mon, 18 Jan 1999 03:25:14 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As of a few minutes ago, I committed some changes that: 1: make the LKM code use the common VFS and syscall registration routines 2: make an 'options LKM' option. 3: build an 'lkm' loadable kld module This means that if you are still using an a.out kernel and are loading LKM's specifically, you either need to add 'options LKM' to your config, or do a 'kldload lkm' to load the /dev/lkm support routines. I have not added 'options LKM' to GENERIC.. Please bear in mind that new installations are 100% ELF, including the kernel and the LKM support has zero use there. FreeBSD no longer supplies LKM's, but it is still possible to build your own from source... However, the thought has occurred on many occasions that it might be an idea to make a stand on this and remove the LKM build support. It will clean up a few interfaces. If this doesn't happen for 3.1, it's definately on my agenda for after the branch. Converting the common LKM's to kld modules is pretty easy, and even the ones with custom load/unload code are not too hard. I'd be interested to get a feeling for whether this should be done for 3.1 or later. (Remember, OSS have a KLD version now for 3.0). Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 11:33:42 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA18130 for freebsd-current-outgoing; Sun, 17 Jan 1999 11:33:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rebma.ghostwheel.com (rebma.ghostwheel.com [207.201.56.159]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA18125 for ; Sun, 17 Jan 1999 11:33:39 -0800 (PST) (envelope-from merlin@ghostwheel.com) Received: from avalon (avalon.ghostwheel.com [207.201.56.88]) by rebma.ghostwheel.com (8.9.1/8.8.8) with SMTP id LAA26714; Sun, 17 Jan 1999 11:33:34 -0800 (PST) (envelope-from merlin@ghostwheel.com) Message-Id: <4.1.19990117112437.009c78f0@pop.ghostwheel.com> X-Sender: merlin@rebma.ghostwheel.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sun, 17 Jan 1999 11:25:28 -0800 To: Gianmarco Giovannelli From: Christopher Knight Subject: Re: Problem booting from aic7890/91 Ultra2 SCSI Cc: current@FreeBSD.ORG In-Reply-To: <4.1.19990117201046.009e2ad0@194.184.65.4> References: <4.1.19990116180852.00a9aea0@pop.ghostwheel.com> <4.1.19990117003737.009d4a80@194.184.65.4> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 08:11 PM 1/17/99 +0100, Gianmarco Giovannelli wrote: >Please try to remove apm0 , if you have ... here it seems to solve the >problem (after 15 reboot no problem...) I didn't have it compiled in. :( # # Laptop support (see LINT for more options) # #device apm0 at isa? disable flags 0x31 # Advanced Power Management Bust be something else, at least in my case. -ck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 11:51:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20029 for freebsd-current-outgoing; Sun, 17 Jan 1999 11:51:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chmls11.mediaone.net (chmls11.mediaone.net [24.128.1.112]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20023 for ; Sun, 17 Jan 1999 11:51:22 -0800 (PST) (envelope-from veldy@visi.com) Received: from rover (h-178-251.mn.mediaone.net [209.32.178.251]) by chmls11.mediaone.net (8.8.7/8.8.7) with SMTP id OAA16771 for ; Sun, 17 Jan 1999 14:51:16 -0500 (EST) From: "Thomas T. Veldhouse" To: "FreeBSD-Current" Subject: /boot/loader and booting off of second IDE Date: Sun, 17 Jan 1999 13:52:15 -0600 Message-ID: <000001be4252$e2562340$0264a8c0@rover.mn.mediaone.net> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01BE4220.97C35460" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0001_01BE4220.97C35460 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit OK. I have tried to figure out how to boot off of my second IDE drive and I am close, but I still haven't got it. I need to boot wd2s1a. Here is what I have done. Booting off of a floppy with the old boot blocks: 1:wd(2,a)/boot/loader I get to the prompt and type: set currdev=disk2s1a set rootdev=disk2s1a when I type show, I see loaddev=disk2s1a:, but there does not seem to be any documentation on this. Anybody know if this is significant? Anyway, I then do: boot -rootdev And the kernel proceeds to boot and it actually mounts the correct root (wd2s1a). It shows the all the drives are clean and then it fails, stating that it can't mount wd2s1a because the device is incompatible (or something like that - I am running from memory, as I have blown my system with fdisk (DOS) and am rebuilding) and then drops to a single user shell with / mounted read-only. It seems to me that it is having a problem going from root as a read-only filesystem to a read-write filesystem. I have tried many combinations without success. If it mounts root, it always fails during the remount (fstab). If I don't pass rootdev as an argument to the kernel, it tries to mount wd1s1 and then it panics, obviously because there is no [UFS] filesystem there. Any ideas what else to try? Tom Veldhouse veldy@visi.com ------=_NextPart_000_0001_01BE4220.97C35460 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
OK.  I have tried to figure out how to boot off of my = second IDE=20 drive and I am close, but I still haven't got it.  I need to boot=20 wd2s1a.  Here is what I have done.
 
Booting off of a floppy with the old boot = blocks:
 
    1:wd(2,a)/boot/loader
 
    I get to the prompt and = type:
 
    set currdev=3Ddisk2s1a
    set rootdev=3Ddisk2s1a
 
    when I type show, I see loaddev=3Ddisk2s1a:, = but there=20 does not seem to be any documentation on this.  Anybody know if = this is=20 significant?  Anyway,  I then do:
 
    boot -rootdev
 
And=20 the kernel proceeds to boot and it actually mounts the correct root=20 (wd2s1a).  It shows the all the drives are clean and then it fails, = stating=20 that it can't mount wd2s1a because the device is incompatible (or = something like=20 that - I am running from memory, as I have blown my system with fdisk = (DOS) and=20 am rebuilding) and then drops to a single user shell with / mounted=20 read-only.  It seems to me that it is having a problem going from = root as a=20 read-only filesystem to a read-write filesystem.  I have tried many = combinations without success.  If it mounts root, it always fails = during=20 the remount (fstab).  If I don't pass rootdev as an argument to the = kernel,=20 it tries to mount wd1s1 and then it panics, obviously because there is = no [UFS]=20 filesystem there.
 
Any=20 ideas what else to try?
 
Tom=20 Veldhouse
veldy@visi.com
------=_NextPart_000_0001_01BE4220.97C35460-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 12:01:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA21373 for freebsd-current-outgoing; Sun, 17 Jan 1999 12:01:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA21365 for ; Sun, 17 Jan 1999 12:01:04 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.2/8.9.2/Netplex) with ESMTP id EAA06611; Mon, 18 Jan 1999 04:00:36 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199901172000.EAA06611@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: sthaug@nethelp.no cc: jack@germanium.xtalwind.net, current@FreeBSD.ORG Subject: Re: Annoying messages on startup.. In-reply-to: Your message of "Sun, 17 Jan 1999 19:34:18 +0100." <14456.916598058@verdi.nethelp.no> Date: Mon, 18 Jan 1999 04:00:35 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sthaug@nethelp.no wrote: > > > jkh@zippy-> dmesg|grep Freeing > > > Freeing (NOT implemented) redirected ISA irq 11. > > > Freeing (NOT implemented) redirected ISA irq 10. > > > > Nowhere near as annoying as "tagged openings now xx". > > Agreed. They are confusing to those who don't know what it means. As for > me, I just ignore them - ie. they don't do *me* any good either. And they are actually wrong in the general case. What happens is that the system boots up in a kinda compatability mode where the PCI interrupts are routed to the ISA interrupt sources. However, once the APIC is started, this routing stops instantly - we don't have to implement anything, the IRQ is now free by the hardware. It is now is quite useable by some other ISA device, perhaps via PnP or by selecting an interrupt via the IO registers. I'm pretty sure the message was left out of Steve's caution. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 12:52:53 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA28304 for freebsd-current-outgoing; Sun, 17 Jan 1999 12:52:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA28299 for ; Sun, 17 Jan 1999 12:52:50 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.2/8.9.2) with ESMTP id UAA36906 for ; Sun, 17 Jan 1999 20:52:45 GMT Message-ID: <36A24D5E.F1875A83@tdx.co.uk> Date: Sun, 17 Jan 1999 20:51:42 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Problems with new IDE's & -current Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have a system that's meant as a 'backup disk spool' - it has a 2Gb SCSI drive to boot from, and then 2 x 16Gb IDE drives (IBM-DTTA-351680's). The system works fine so long as I stick to using the SCSI drives... If I use the IDE's (e.g. backup another machine to them, tar / untar 'usr/src' to them) I start getting problems, e.g. Jan 14 13:01:42 magpie /kernel: wd0: interrupt timeout: Jan 14 13:01:42 magpie /kernel: wd0: status 58 error 0 Jan 15 17:56:52 magpie /kernel: lnc0: Missed packet -- no receive buffer Jan 15 17:57:43 magpie /kernel: lnc0: Missed packet -- no receive buffer The machine also has an NE-2100 embedded network card. We have 4 other identical machines to this, all SCSI based - all work without any problems... Is there anything that can be done? - at a guess I'd say the IDE's/wcd0 are timing out on interrupts, which is then stuffing the network (as the systems been waiting around too long for wcd0's IRQ's?)... The machine is a dual P90 (running SMP) - I get the problems even with a single CPU kernel... It's running Neptune chipset (quite old) - and only has 1 IDE channel. Any pointers? - The drives do appear to work OK, i.e. no corruption, but the _whole_ machine appears to 'stall' when the above occurs = not good... :-( I've tried 3.0-Release and 3.0-Current as of 7th Jan, '99 - Both exhibit identical symptoms... -Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 13:02:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA29554 for freebsd-current-outgoing; Sun, 17 Jan 1999 13:02:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA29545 for ; Sun, 17 Jan 1999 13:02:40 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.2/8.9.2) with ESMTP id VAA36978; Sun, 17 Jan 1999 21:02:08 GMT Message-ID: <36A24F91.478B5387@tdx.co.uk> Date: Sun, 17 Jan 1999 21:01:05 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: jack CC: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Heavy on the Verbosity (was) Re: Annoying messages on startup.. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG jack wrote: > Nowhere near as annoying as "tagged openings now xx". > > Perhaps `|| 1' could be changed to `|| crs->openings < some > critical number' in cam_xpt.c. As it is now a boy and a wolf > come to mind. Coming from someone who's spent the best part of last week trying to diagnose various hardware & software problems on NT & Win'95 machines (to almost no avail), I'd appreciate as much verbosity being left _in_ the kernel & FreeBSD as possible... I'm fed up with seeing "Unknown error", or "Unknown errors occured" or "Service Failed" and the like on competitor / other products... Make them only 'if verbose' if you need to - just don't lose them alltogether!... :) -Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 13:04:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA29745 for freebsd-current-outgoing; Sun, 17 Jan 1999 13:04:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA29738 for ; Sun, 17 Jan 1999 13:04:44 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id NAA32887; Sun, 17 Jan 1999 13:04:48 -0800 (PST) To: "Igor Shulgin" cc: "FreeBSD-current" Subject: Re: Running old program on 3.0-RELEASE In-reply-to: Your message of "Sun, 17 Jan 1999 19:31:53 +0500." <003301be4226$21772740$870636c3@igorsh.garural.chel.su> Date: Sun, 17 Jan 1999 13:04:47 -0800 Message-ID: <32884.916607087@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I recently installed 3.0-RELEASE on existing 2.1.0-RELEASE. > After that one program does not run any more. You probably did not update the contents of /etc, as one must by hand. This would not create the a.out search paths properly and leads to this exact error. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 13:12:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00828 for freebsd-current-outgoing; Sun, 17 Jan 1999 13:12:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA00820 for ; Sun, 17 Jan 1999 13:12:52 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id WAA16964; Sun, 17 Jan 1999 22:10:42 +0100 (CET) To: Karl Pielorz cc: jack , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: Heavy on the Verbosity (was) Re: Annoying messages on startup.. In-reply-to: Your message of "Sun, 17 Jan 1999 21:01:05 GMT." <36A24F91.478B5387@tdx.co.uk> Date: Sun, 17 Jan 1999 22:10:42 +0100 Message-ID: <16962.916607442@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <36A24F91.478B5387@tdx.co.uk>, Karl Pielorz writes: >jack wrote: > >> Nowhere near as annoying as "tagged openings now xx". >> >> Perhaps `|| 1' could be changed to `|| crs->openings < some >> critical number' in cam_xpt.c. As it is now a boy and a wolf >> come to mind. > >Coming from someone who's spent the best part of last week trying to diagnose >various hardware & software problems on NT & Win'95 machines (to almost no >avail), I'd appreciate as much verbosity being left _in_ the kernel & FreeBSD >as possible... I'm fed up with seeing "Unknown error", or "Unknown errors >occured" or "Service Failed" and the like on competitor / other products... >Make them only 'if verbose' if you need to - just don't lose them >alltogether!... :) ... and add a magic key combination to turn on the verbose flag. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 13:14:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00914 for freebsd-current-outgoing; Sun, 17 Jan 1999 13:14:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from st-lcremean.tidalwave.net (host-e186.tidalwave.net [208.213.203.186] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA00908 for ; Sun, 17 Jan 1999 13:14:33 -0800 (PST) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.9.1/8.8.8) id QAA65508; Sun, 17 Jan 1999 16:14:19 -0500 (EST) (envelope-from lee) Message-ID: <19990117161419.A65396@tidalwave.net> Date: Sun, 17 Jan 1999 16:14:19 -0500 From: Lee Cremeans To: Karl Pielorz , current@FreeBSD.ORG Subject: Re: Problems with new IDE's & -current Reply-To: lcremean@tidalwave.net References: <36A24D5E.F1875A83@tdx.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <36A24D5E.F1875A83@tdx.co.uk>; from Karl Pielorz on Sun, Jan 17, 1999 at 08:51:42PM +0000 X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 17, 1999 at 08:51:42PM +0000, Karl Pielorz wrote: > Hi, > > I have a system that's meant as a 'backup disk spool' - it has a 2Gb SCSI > drive to boot from, and then 2 x 16Gb IDE drives (IBM-DTTA-351680's). > > The system works fine so long as I stick to using the SCSI drives... If I use > the IDE's (e.g. backup another machine to them, tar / untar 'usr/src' to them) > I start getting problems, > > e.g. > > Jan 14 13:01:42 magpie /kernel: wd0: interrupt timeout: > Jan 14 13:01:42 magpie /kernel: wd0: status 58 error 0 > Jan 15 17:56:52 magpie /kernel: lnc0: Missed packet -- no receive buffer > Jan 15 17:57:43 magpie /kernel: lnc0: Missed packet -- no receive buffer > [snip] > The machine is a dual P90 (running SMP) - I get the problems even with a > single CPU kernel... It's running Neptune chipset (quite old) - and only > has 1 IDE channel. I would say that this has something to do with the DMA support, but since Neptune's IDE controller isn't DMA capable and PCI, that doesn't follow. Chances are that there's a not-quite-bad spot on your drive -- does it always seem to happen in the same place on the disk? I have no love lost for Neptune boards; we have two of them at work, and it's like trying to work with a 486 board with an OverDrive chip on it. I'm also wary of Intel boards in general, since they tend to think they're smarter than you. -- +--------------------------------------------------------------------+ | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)| | lcremean@tidalwave.net| http://st-lcremean.tidalwave.net/~lee | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 13:14:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00931 for freebsd-current-outgoing; Sun, 17 Jan 1999 13:14:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA00924; Sun, 17 Jan 1999 13:14:40 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id NAA32926; Sun, 17 Jan 1999 13:14:48 -0800 (PST) To: jack cc: current@FreeBSD.ORG, gibbs@FreeBSD.ORG Subject: Re: Annoying messages on startup.. In-reply-to: Your message of "Sun, 17 Jan 1999 12:10:34 EST." Date: Sun, 17 Jan 1999 13:14:47 -0800 Message-ID: <32922.916607687@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Nowhere near as annoying as "tagged openings now xx". I don't like this error much either (especially since it generates tech support questions on USENET and other places from users going "Aieee! What does this mean?!") but I was overruled on the issue by arguments that it was still providing useful information about drives that didn't really handle multiple tags as well as their spec sheets claimed. The problem with this argument is that it's sort of like the syslogd spew argument. It used to be that syslogd would just hammer your console (or log files) with repetetive messages, should some utility be generating them, without attempting to collapse them to a more meaningful (readable) summary. People screamed loudly about this and subsequent generations of syslogd just print the original message and then a little one-liner some time later which says "And I just got 47 more messages just like that." That's a great optimization and I would suggest that the tag reduction messages be similarly collapsed. Each and every time I boot my system and then launch X (through xdm), for example, I get a spew like this on my console: (da0:ahc0:0:0:0): tagged openings now 64 (da0:ahc0:0:0:0): tagged openings now 63 (da0:ahc0:0:0:0): tagged openings now 62 (da0:ahc0:0:0:0): tagged openings now 61 (da0:ahc0:0:0:0): tagged openings now 60 (da0:ahc0:0:0:0): tagged openings now 59 (da0:ahc0:0:0:0): tagged openings now 58 (da0:ahc0:0:0:0): tagged openings now 57 (da0:ahc0:0:0:0): tagged openings now 56 (da0:ahc0:0:0:0): tagged openings now 55 (da0:ahc0:0:0:0): tagged openings now 54 (da0:ahc0:0:0:0): tagged openings now 53 (da0:ahc0:0:0:0): tagged openings now 52 (da0:ahc0:0:0:0): tagged openings now 51 (da0:ahc0:0:0:0): tagged openings now 50 (da0:ahc0:0:0:0): tagged openings now 49 It all comes in one burst and isn't helping me any by giving me 16 messages where one would do just as nicely. > Also, I suspect having acd in the kernel and wcd in MAKEDEV may > lead to confusion for some people. I was under the impression that Soren was going to rename acd to wcd before the branch. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 13:23:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01702 for freebsd-current-outgoing; Sun, 17 Jan 1999 13:23:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA01694 for ; Sun, 17 Jan 1999 13:23:14 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id IAA03253; Mon, 18 Jan 1999 08:24:35 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199901172124.IAA03253@cimlogic.com.au> Subject: Re: HEADS UP: i386 a.out LKM support now an option.. In-Reply-To: <199901171925.DAA06456@spinner.netplex.com.au> from Peter Wemm at "Jan 18, 1999 3:25:14 am" To: peter@netplex.com.au (Peter Wemm) Date: Mon, 18 Jan 1999 08:24:34 +1100 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: > However, the thought has occurred on many occasions that it might be an > idea to make a stand on this and remove the LKM build support. It will > clean up a few interfaces. If this doesn't happen for 3.1, it's definately > on my agenda for after the branch. Converting the common LKM's to kld > modules is pretty easy, and even the ones with custom load/unload code are > not too hard. I'd be interested to get a feeling for whether this should > be done for 3.1 or later. (Remember, OSS have a KLD version now for 3.0). I'm a fan of the new KLD system, so removing LKM build support is IMHO the right thing to do. I've been working on an embedded system which boots from a 2Mb flash chip without a filesystem. Before KLDs came along, I couldn't use LKMs for I/O devices because of the overhead of having to ship GNU tools too. Now all custom code lives in KLDs which get loaded by the application which replaces init and a simple 20 line kernel config file suits all target hardware versions. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 13:30:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA02437 for freebsd-current-outgoing; Sun, 17 Jan 1999 13:30:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA02430 for ; Sun, 17 Jan 1999 13:30:28 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.2/8.9.2) with ESMTP id VAA37160; Sun, 17 Jan 1999 21:30:22 GMT Message-ID: <36A2562F.52251545@tdx.co.uk> Date: Sun, 17 Jan 1999 21:29:19 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: lcremean@tidalwave.net CC: current@FreeBSD.ORG Subject: Re: Problems with new IDE's & -current References: <36A24D5E.F1875A83@tdx.co.uk> <19990117161419.A65396@tidalwave.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Lee Cremeans wrote: > > The machine is a dual P90 (running SMP) - I get the problems even with a > > single CPU kernel... It's running Neptune chipset (quite old) - and only > > has 1 IDE channel. > > I would say that this has something to do with the DMA support, but since > Neptune's IDE controller isn't DMA capable and PCI, that doesn't follow. > Chances are that there's a not-quite-bad spot on your drive -- does it > always seem to happen in the same place on the disk? Nope, it's more 'load' oriented than 'spot' oriented (i.e. the harder you push them - the more of the above you get)... Both drives are brand new out the box (for what it's worth), so I doub't they're 'bad'... DMA is disabled in the kernel config as well, and the dmesg shows no hints of either multi-block or DMA transfers... Thinking that way I've tried another cable since (brand new out the bag - again 'for what it's worth') - and that has the same symptoms... So does running only 1 drive on the bus... :-( > > I have no love lost for Neptune boards; we have two of them at work, > and it's like trying to work with a 486 board with an OverDrive chip on it. > I'm also wary of Intel boards in general, since they tend to think they're > smarter than you. > True, my second Pentium board was Neptune based (Plato-90?), and it had it's fare share of problems - but to be honest we've had no problems with these ones - their all in AST Premmia GX's - which are the backbone of our business systems at the moment... They work fine, except for this one (which is the only one using IDE). -Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 13:35:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA02952 for freebsd-current-outgoing; Sun, 17 Jan 1999 13:35:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from st-lcremean.tidalwave.net (host-e186.tidalwave.net [208.213.203.186] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA02947 for ; Sun, 17 Jan 1999 13:35:53 -0800 (PST) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.9.1/8.8.8) id QAA65613; Sun, 17 Jan 1999 16:35:44 -0500 (EST) (envelope-from lee) Message-ID: <19990117163544.A65560@tidalwave.net> Date: Sun, 17 Jan 1999 16:35:44 -0500 From: Lee Cremeans To: Karl Pielorz Cc: current@FreeBSD.ORG Subject: Re: Problems with new IDE's & -current Reply-To: lcremean@tidalwave.net References: <36A24D5E.F1875A83@tdx.co.uk> <19990117161419.A65396@tidalwave.net> <36A2562F.52251545@tdx.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <36A2562F.52251545@tdx.co.uk>; from Karl Pielorz on Sun, Jan 17, 1999 at 09:29:19PM +0000 X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 17, 1999 at 09:29:19PM +0000, Karl Pielorz wrote: > > > Lee Cremeans wrote: > > > > The machine is a dual P90 (running SMP) - I get the problems even with a > > > single CPU kernel... It's running Neptune chipset (quite old) - and only > > > has 1 IDE channel. > > > > I would say that this has something to do with the DMA support, but since > > Neptune's IDE controller isn't DMA capable and PCI, that doesn't follow. > > Chances are that there's a not-quite-bad spot on your drive -- does it > > always seem to happen in the same place on the disk? > > Nope, it's more 'load' oriented than 'spot' oriented (i.e. the harder you push > them - the more of the above you get)... Both drives are brand new out the box > (for what it's worth), so I doub't they're 'bad'... DMA is disabled in the > kernel config as well, and the dmesg shows no hints of either multi-block or > DMA transfers... > > Thinking that way I've tried another cable since (brand new out the bag - > again 'for what it's worth') - and that has the same symptoms... So does > running only 1 drive on the bus... :-( I dunno then; it sounds like the IDE port is broken and starts dropping interrupts. This is a bit over my head -- any interrupt-service-routine gurus want to jump in here? I don't want to condemn the motherboard just yet. -- +--------------------------------------------------------------------+ | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)| | lcremean@tidalwave.net| http://st-lcremean.tidalwave.net/~lee | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 13:36:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA03035 for freebsd-current-outgoing; Sun, 17 Jan 1999 13:36:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from PacHell.TelcoSucks.org (PacHell.TelcoSucks.org [207.90.181.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA03030 for ; Sun, 17 Jan 1999 13:36:16 -0800 (PST) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.1/8.9.1) id NAA22000; Sun, 17 Jan 1999 13:35:34 -0800 (PST) (envelope-from ulf) Message-ID: <19990117133534.F28911@TelcoSucks.org> Date: Sun, 17 Jan 1999 13:35:34 -0800 From: Ulf Zimmermann To: Robert Nordier , ulf@Alameda.net Cc: current@FreeBSD.ORG Subject: Re: possible problem with new boot loader ? Reply-To: ulf@Alameda.net References: <19990117061641.D28911@TelcoSucks.org> <199901171629.SAA26217@ceia.nordier.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199901171629.SAA26217@ceia.nordier.com>; from Robert Nordier on Sun, Jan 17, 1999 at 06:29:30PM +0200 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.0-19980930-BETA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 17, 1999 at 06:29:30PM +0200, Robert Nordier wrote: > Ulf Zimmermann wrote: > > > Not sure if I am just to stupid or if this is a bug. My system has > > 2 IDE drives and then several SCSI drives. FreeBSD is on the first > > scsi drive, so da0. Root is da0s1a. Bios sees the drive as the 3. > > > > When the new boot loader comes up with no /boot.config, it prints > > 2:da(2,a)/boot/loader, which isn't right, as it should be 2:da(0,a). > > If I now press a key and enter 2:da(0,a), it complains it can't find > > /boot/loader. Entering 2:da(0,a)/kernel works fine and that is > > what i have now in my boot.conf. > > > > Could this be a bug or not? > > There are two issues here: > > o The bootblocks get the SCSI unit number wrong in cases where > IDE drives are also attached. > > This is to be expected. There is just insufficient space > available to the bootblocks for "smarter" logic. > > The old bootblocks have a build setting BOOT_HD_BIAS to work > around this problem. The new bootblocks rely on /boot.config. > You can have > > 2:da(0,a) If I do that, it does find the loader, but the kernel panics, because it thinks root should be on da2s1a. > > in /boot.config (ie. without a kernel name) to override just > the unit number. > > o The /boot/loader program just isn't being found. > > Are you sure this actually exists? What shows up if you > enter > > 2:da(0,a)/boot/? > > (to get a directory listing of /boot) at the "boot:" prompt? > > Incidentally, do these bootblocks contain the BTX patch I sent you, > or did you find some other way around that problem? This are the boot loaders from last night, just after make world got through. > > -- > Robert Nordier -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 13:39:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA03285 for freebsd-current-outgoing; Sun, 17 Jan 1999 13:39:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peacock.tci.com (coral.tci.com [198.178.8.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA03280 for ; Sun, 17 Jan 1999 13:39:17 -0800 (PST) (envelope-from chris@tci.com) Received: from oreo.tci.com (co-chris-pc01.tci.com [172.18.27.65]) by peacock.tci.com (8.9.0/8.9.0) with ESMTP id OAA16029; Sun, 17 Jan 1999 14:39:12 -0700 (MST) Received: from tci.com (localhost [127.0.0.1]) by oreo.tci.com (8.9.1b+Sun/8.9.1) with ESMTP id OAA01428; Sun, 17 Jan 1999 14:38:48 -0700 (MST) Message-ID: <36A25867.5EF5E5CE@tci.com> Date: Sun, 17 Jan 1999 14:38:47 -0700 From: Chris Tubutis Organization: Tele-Communications, Inc. X-Mailer: Mozilla 4.5 [en] (X11; U; SunOS 5.7 sun4m) X-Accept-Language: en MIME-Version: 1.0 To: Karl Pielorz CC: jack , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: Heavy on the Verbosity (was) Re: Annoying messages on startup.. References: <36A24F91.478B5387@tdx.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Karl Pielorz wrote: > > Coming from someone who's spent the best part of last week trying to diagnose > various hardware & software problems on NT & Win'95 machines (to almost no > avail), I'd appreciate as much verbosity being left _in_ the kernel & FreeBSD > as possible... I'm fed up with seeing "Unknown error", or "Unknown errors > occured" or "Service Failed" and the like on competitor / other products... > Make them only 'if verbose' if you need to - just don't lose them > alltogether!... :) This is a very good point, something that I strongly agree with. As hard as I try not to, I find myself having to deal with products from Redmond while at work. Yeah, stuff like "Error connecting to database" tells me absolutely nothing and is frustrating as all Hell. Maybe a way to toggle the verbosity to suit individual preferences would be a good way to go? ct To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 13:39:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA03315 for freebsd-current-outgoing; Sun, 17 Jan 1999 13:39:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles174.castles.com [208.214.165.174]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA03309 for ; Sun, 17 Jan 1999 13:39:38 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA08876; Sun, 17 Jan 1999 13:36:12 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901172136.NAA08876@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: ulf@Alameda.net cc: current@FreeBSD.ORG Subject: Re: possible problem with new boot loader ? In-reply-to: Your message of "Sun, 17 Jan 1999 13:35:34 PST." <19990117133534.F28911@TelcoSucks.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 17 Jan 1999 13:36:12 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > There are two issues here: > > > > o The bootblocks get the SCSI unit number wrong in cases where > > IDE drives are also attached. > > > > This is to be expected. There is just insufficient space > > available to the bootblocks for "smarter" logic. > > > > The old bootblocks have a build setting BOOT_HD_BIAS to work > > around this problem. The new bootblocks rely on /boot.config. > > You can have > > > > 2:da(0,a) > > If I do that, it does find the loader, but the kernel panics, because > it thinks root should be on da2s1a. You need 'set num_ide_disks=2' The variable's somewhat misnamed, and I'm still groping for an algorithm that'll get it more or less right without screwing the pooch should we ever improve the root mount detection in the kernel. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 13:48:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04066 for freebsd-current-outgoing; Sun, 17 Jan 1999 13:48:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from PacHell.TelcoSucks.org (PacHell.TelcoSucks.org [207.90.181.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA04061 for ; Sun, 17 Jan 1999 13:48:22 -0800 (PST) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.1/8.9.1) id NAA24593; Sun, 17 Jan 1999 13:47:45 -0800 (PST) (envelope-from ulf) Message-ID: <19990117134745.G28911@TelcoSucks.org> Date: Sun, 17 Jan 1999 13:47:45 -0800 From: Ulf Zimmermann To: Robert Nordier , ulf@Alameda.net Cc: current@FreeBSD.ORG Subject: Re: possible problem with new boot loader ? Reply-To: ulf@Alameda.net References: <19990117061641.D28911@TelcoSucks.org> <199901171629.SAA26217@ceia.nordier.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199901171629.SAA26217@ceia.nordier.com>; from Robert Nordier on Sun, Jan 17, 1999 at 06:29:30PM +0200 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.0-19980930-BETA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 17, 1999 at 06:29:30PM +0200, Robert Nordier wrote: > Ulf Zimmermann wrote: > > > Not sure if I am just to stupid or if this is a bug. My system has > > 2 IDE drives and then several SCSI drives. FreeBSD is on the first > > scsi drive, so da0. Root is da0s1a. Bios sees the drive as the 3. > > > > When the new boot loader comes up with no /boot.config, it prints > > 2:da(2,a)/boot/loader, which isn't right, as it should be 2:da(0,a). > > If I now press a key and enter 2:da(0,a), it complains it can't find > > /boot/loader. Entering 2:da(0,a)/kernel works fine and that is > > what i have now in my boot.conf. > > > > Could this be a bug or not? > > There are two issues here: > > o The bootblocks get the SCSI unit number wrong in cases where > IDE drives are also attached. > > This is to be expected. There is just insufficient space > available to the bootblocks for "smarter" logic. > > The old bootblocks have a build setting BOOT_HD_BIAS to work > around this problem. The new bootblocks rely on /boot.config. > You can have > > 2:da(0,a) > > in /boot.config (ie. without a kernel name) to override just > the unit number. > > o The /boot/loader program just isn't being found. > > Are you sure this actually exists? What shows up if you > enter > > 2:da(0,a)/boot/? > > (to get a directory listing of /boot) at the "boot:" prompt? > > Incidentally, do these bootblocks contain the BTX patch I sent you, > or did you find some other way around that problem? More info. With "2:da(0,a)" in /boot.config, a boot looks like this: /boot.config: 2:da(0,a) / BTX loader 0.01 BTX version is 0.87 Console: internal video/keyboard BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS drive D: is disk2 BIOS drive E: is disk3 BIOS drive F: is disk4 FreeBSD/i386 bootstrap loader, Revision 0.2 636/65532kB (root@Playtoy.Melmac.org, Sun Jan 17 03:54:54 PST 1999) Hit [Enter] to boot immediatly, or any other key for command prompt. Booting [kernel]... can't load 'kernel' Type '?' for a list of commands, 'help' for more detailed help. disk1s1a:> Interrupting earlier: /boot.config: 2:da(0,a) >> FreeBSD/i386 BOOT Default: 2:da(0,a)/boot/loader boot: 2:da(0,a)/boot/? . .. boot0 boot1 boot2 loader loader.old loader.help > > -- > Robert Nordier -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 13:49:59 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04204 for freebsd-current-outgoing; Sun, 17 Jan 1999 13:49:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from PacHell.TelcoSucks.org (PacHell.TelcoSucks.org [207.90.181.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA04199 for ; Sun, 17 Jan 1999 13:49:58 -0800 (PST) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.1/8.9.1) id NAA25169; Sun, 17 Jan 1999 13:49:51 -0800 (PST) (envelope-from ulf) Message-ID: <19990117134951.H28911@TelcoSucks.org> Date: Sun, 17 Jan 1999 13:49:51 -0800 From: Ulf Zimmermann To: Mike Smith , ulf@Alameda.net Cc: current@FreeBSD.ORG Subject: Re: possible problem with new boot loader ? Reply-To: ulf@Alameda.net References: <19990117133534.F28911@TelcoSucks.org> <199901172136.NAA08876@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199901172136.NAA08876@dingo.cdrom.com>; from Mike Smith on Sun, Jan 17, 1999 at 01:36:12PM -0800 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.0-19980930-BETA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 17, 1999 at 01:36:12PM -0800, Mike Smith wrote: > > > There are two issues here: > > > > > > o The bootblocks get the SCSI unit number wrong in cases where > > > IDE drives are also attached. > > > > > > This is to be expected. There is just insufficient space > > > available to the bootblocks for "smarter" logic. > > > > > > The old bootblocks have a build setting BOOT_HD_BIAS to work > > > around this problem. The new bootblocks rely on /boot.config. > > > You can have > > > > > > 2:da(0,a) > > > > If I do that, it does find the loader, but the kernel panics, because > > it thinks root should be on da2s1a. > > You need 'set num_ide_disks=2' > > The variable's somewhat misnamed, and I'm still groping for an > algorithm that'll get it more or less right without screwing the pooch > should we ever improve the root mount detection in the kernel. Set that where? At the disk1s1a:> prompt ? Still can't find kernel. > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 13:58:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05091 for freebsd-current-outgoing; Sun, 17 Jan 1999 13:58:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05086 for ; Sun, 17 Jan 1999 13:58:08 -0800 (PST) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.9.2/8.9.2) with ESMTP id QAA62667; Sun, 17 Jan 1999 16:57:59 -0500 (EST) Date: Sun, 17 Jan 1999 16:57:59 -0500 (EST) From: jack To: "Jordan K. Hubbard" cc: current@FreeBSD.ORG Subject: Re: Annoying messages on startup.. In-Reply-To: <32922.916607687@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 17 Jan 1999, Jordan K. Hubbard wrote: > > Nowhere near as annoying as "tagged openings now xx". > > I don't like this error much either (especially since it generates > tech support questions on USENET and other places from users going > "Aieee! What does this mean?!") but I was overruled on the issue by > arguments that it was still providing useful information about drives > that didn't really handle multiple tags as well as their spec sheets > claimed. I never saw less than 62 with Seagates and IBMs on three different boxes. Now I just change if (bootverbose || 1) { to if (bootverbose || crs->openings < 50) { everytime cam_xpt.c gets updated and I don't see it at all. If I do I know Something Bad is happening. Since bootverbose will turn it on for those folks who need it what's the point in spamming everyone's consoles? Just 'cause it's flu season is no reason for _everyone_ to constantly use a rectal thermometer. -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 14:00:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA05824 for freebsd-current-outgoing; Sun, 17 Jan 1999 14:00:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles174.castles.com [208.214.165.174]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA05813 for ; Sun, 17 Jan 1999 14:00:41 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA09016; Sun, 17 Jan 1999 13:57:21 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901172157.NAA09016@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: ulf@Alameda.net cc: current@FreeBSD.ORG Subject: Re: possible problem with new boot loader ? In-reply-to: Your message of "Sun, 17 Jan 1999 13:49:51 PST." <19990117134951.H28911@TelcoSucks.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 17 Jan 1999 13:57:20 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, Jan 17, 1999 at 01:36:12PM -0800, Mike Smith wrote: > > > > There are two issues here: > > > > > > > > o The bootblocks get the SCSI unit number wrong in cases where > > > > IDE drives are also attached. > > > > > > > > This is to be expected. There is just insufficient space > > > > available to the bootblocks for "smarter" logic. > > > > > > > > The old bootblocks have a build setting BOOT_HD_BIAS to work > > > > around this problem. The new bootblocks rely on /boot.config. > > > > You can have > > > > > > > > 2:da(0,a) > > > > > > If I do that, it does find the loader, but the kernel panics, because > > > it thinks root should be on da2s1a. > > > > You need 'set num_ide_disks=2' > > > > The variable's somewhat misnamed, and I'm still groping for an > > algorithm that'll get it more or less right without screwing the pooch > > should we ever improve the root mount detection in the kernel. > > Set that where? At the disk1s1a:> prompt ? Still can't find kernel. num_ide_disks will help the kernel work out where the root filesystem is. If you can't find the kernel, try 'ls' to start with, and then send the output 'lsdev' I'm also curious why you get a 'disk1s1a' prompt, when it should be disk3 (presuming you have a floppy disk). Have you installed new bootblocks on your boot disk? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 14:05:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA06943 for freebsd-current-outgoing; Sun, 17 Jan 1999 14:05:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from schuimpje.snt.utwente.nl (schuimpje.snt.utwente.nl [130.89.238.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA06919; Sun, 17 Jan 1999 14:05:21 -0800 (PST) (envelope-from gelderen@mediaport.org) Received: from wit395301.student.utwente.nl ([130.89.235.121]:4100 "HELO deskfix" ident: "NO-IDENT-SERVICE[2]") by schuimpje.snt.utwente.nl with SMTP id <7966-10514>; Sun, 17 Jan 1999 23:05:09 +0100 Message-ID: <000e01be4265$588824c0$1400000a@deskfix.local> From: "Jeroen C. van Gelderen" To: "jack" , "Jordan K. Hubbard" Cc: , Subject: Re: Annoying messages on startup.. Date: Sun, 17 Jan 1999 23:04:25 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Jordan K. Hubbard >I don't like this error much either (especially since it generates >tech support questions on USENET and other places from users going >"Aieee! What does this mean?!") me too Question is what to do about the messages. I can think of a few options: 1. move them to verbose mode. There are more drivers that spew this kind of message in verbose mode. 2. handle them trough the quirk mechanism. I was told that this would cause kernel-bloat but that might be remedied by using a more compact format (now 17 bytes per entry) for the quirk table and/or allowing the quirk table to be paged out (if possible?) 3. issue them only when the driver expects it to be a quirk. There are a lot of drives that will cause the openings to run down to a certain number and stay there. Don't issue a warning when the number stays above ??. 4. adjust the number of tagged openings on boot. Simply issue a lot of tagged openings and adjust the number appropriately. This would look very nice: da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 5.0MB/s transfers (5.0MHz, offset 15), Tagged Queueing Enabled (31 concurrent transactions) da0: 4096MB (8388608 512 byte sectors: 255H 63S/T 522C) or, if you want to do something about the formatting of the boot msgs: da0 at ahc0 bus 0 target 0 lun 0 Fixed Direct Access SCSI-2 device 5.0MB/s transfers (5.0MHz, offset 15), Tagged Queueing Enabled (31 concurrent transactions) 4096MB (8388608 512 byte sectors: 255H 63S/T 522C) A combination of these ideas might do. Basically you want to get rid of the warnings when there's nothing wrong with the hardware. DISCLAIMER: I don't know much about CAM so please don't shoot me if this is nonsense... Cheers, Jeroen -- Jeroen C. van Gelderen -- gelderen@mediaport.org -- &[8-D}~<= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 14:12:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA07837 for freebsd-current-outgoing; Sun, 17 Jan 1999 14:12:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA07832 for ; Sun, 17 Jan 1999 14:12:25 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id OAA33231; Sun, 17 Jan 1999 14:12:04 -0800 (PST) To: Karl Pielorz cc: jack , current@FreeBSD.ORG Subject: Re: Heavy on the Verbosity (was) Re: Annoying messages on startup.. In-reply-to: Your message of "Sun, 17 Jan 1999 21:01:05 GMT." <36A24F91.478B5387@tdx.co.uk> Date: Sun, 17 Jan 1999 14:12:04 -0800 Message-ID: <33227.916611124@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Coming from someone who's spent the best part of last week trying to diagnose > various hardware & software problems on NT & Win'95 machines (to almost no > avail), I'd appreciate as much verbosity being left _in_ the kernel & FreeBSD You can always have verbosity as a selective option. We're talking about what to do for the great majority of users who aren't in your shoes at all and don't want to be. You can always boot with -v to have the messages in question, I'm not talking about removing them so much as not making them the _default_. Don't worry, I don't want this to become NT either. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 14:13:02 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA07907 for freebsd-current-outgoing; Sun, 17 Jan 1999 14:13:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA07900 for ; Sun, 17 Jan 1999 14:12:57 -0800 (PST) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.9.2/8.9.2) with ESMTP id RAA62758; Sun, 17 Jan 1999 17:12:37 -0500 (EST) Date: Sun, 17 Jan 1999 17:12:37 -0500 (EST) From: jack To: Chris Tubutis cc: Karl Pielorz , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: Heavy on the Verbosity (was) Re: Annoying messages on startup.. In-Reply-To: <36A25867.5EF5E5CE@tci.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 17 Jan 1999, Chris Tubutis wrote: > > Coming from someone who's spent the best part of last week trying to diagnose > > various hardware & software problems on NT & Win'95 machines (to almost no > > avail), I'd appreciate as much verbosity being left _in_ the kernel & FreeBSD > > as possible... I'm fed up with seeing "Unknown error", or "Unknown errors > > occured" or "Service Failed" and the like on competitor / other products... > > Make them only 'if verbose' if you need to - just don't lose them > > alltogether!... :) > > This is a very good point, something that I strongly agree with. As hard > as I try not to, I find myself having to deal with products from Redmond > while at work. Yeah, stuff like "Error connecting to database" tells me > absolutely nothing and is frustrating as all Hell. I think most of us have been there as some point and I totally agree. It's just that in this case we're getting more than we want at those times when we don't need it. > Maybe a way to toggle the verbosity to suit individual > preferences would be a good way to go? It is keyed to bootverbose, but `or'ed with 1. Perhaps a sysctl(8) knob, kern.verbosity, is worth thinking about. -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 14:18:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA08616 for freebsd-current-outgoing; Sun, 17 Jan 1999 14:18:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA08611 for ; Sun, 17 Jan 1999 14:18:16 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id OAA33244; Sun, 17 Jan 1999 14:12:26 -0800 (PST) To: Poul-Henning Kamp cc: Karl Pielorz , jack , current@FreeBSD.ORG Subject: Re: Heavy on the Verbosity (was) Re: Annoying messages on startup.. In-reply-to: Your message of "Sun, 17 Jan 1999 22:10:42 +0100." <16962.916607442@critter.freebsd.dk> Date: Sun, 17 Jan 1999 14:12:26 -0800 Message-ID: <33241.916611146@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ... and add a magic key combination to turn on the verbose flag. gdb -kW :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 14:22:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09437 for freebsd-current-outgoing; Sun, 17 Jan 1999 14:22:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09426 for ; Sun, 17 Jan 1999 14:22:22 -0800 (PST) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (lxpxbf.lx.ehu.es [158.227.99.131]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id XAA25502; Sun, 17 Jan 1999 23:21:49 +0100 (MET) Message-ID: <36A2627C.5B6E189E@we.lc.ehu.es> Date: Sun, 17 Jan 1999 23:21:48 +0100 From: "José Mª Alcaide" Organization: Universidad del País Vasco - Dept. Electricidad y Electrónica X-Mailer: Mozilla 4.07 [en] (X11; U; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: "Daniel C. Sobral" CC: current@FreeBSD.ORG Subject: Re: Suspend on Current References: <36A0C882.1C7F2AAD@newsguy.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel C. Sobral wrote: > > Is it just me, or is there anyone else experiencing system freezes > on current after a zzz? > "Me too"® What I see is that, sometimes, after a "zzz" the system goes to sleep (at least, the monitor turns off), but there is no way to wake it up again. The only reason for I have APM enabled is that I like "shutdown -p" (my computer is not a laptop). -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | http://www.we.lc.ehu.es/~jose Dpto. de Electricidad y Electrónica | Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139 ----------------------------------------------------------------------- "Go ahead... make my day." - H. Callahan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 14:24:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09596 for freebsd-current-outgoing; Sun, 17 Jan 1999 14:24:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from PacHell.TelcoSucks.org (PacHell.TelcoSucks.org [207.90.181.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09546 for ; Sun, 17 Jan 1999 14:24:00 -0800 (PST) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.1/8.9.1) id OAA03216; Sun, 17 Jan 1999 14:23:59 -0800 (PST) (envelope-from ulf) Message-ID: <19990117142359.J28911@TelcoSucks.org> Date: Sun, 17 Jan 1999 14:23:59 -0800 From: Ulf Zimmermann To: Mike Smith , ulf@Alameda.net Cc: current@FreeBSD.ORG Subject: Re: possible problem with new boot loader ? Reply-To: ulf@Alameda.net References: <19990117134951.H28911@TelcoSucks.org> <199901172157.NAA09016@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199901172157.NAA09016@dingo.cdrom.com>; from Mike Smith on Sun, Jan 17, 1999 at 01:57:20PM -0800 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.0-19980930-BETA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 17, 1999 at 01:57:20PM -0800, Mike Smith wrote: > > On Sun, Jan 17, 1999 at 01:36:12PM -0800, Mike Smith wrote: > > > > > There are two issues here: > > > > > > > > > > o The bootblocks get the SCSI unit number wrong in cases where > > > > > IDE drives are also attached. > > > > > > > > > > This is to be expected. There is just insufficient space > > > > > available to the bootblocks for "smarter" logic. > > > > > > > > > > The old bootblocks have a build setting BOOT_HD_BIAS to work > > > > > around this problem. The new bootblocks rely on /boot.config. > > > > > You can have > > > > > > > > > > 2:da(0,a) > > > > > > > > If I do that, it does find the loader, but the kernel panics, because > > > > it thinks root should be on da2s1a. > > > > > > You need 'set num_ide_disks=2' > > > > > > The variable's somewhat misnamed, and I'm still groping for an > > > algorithm that'll get it more or less right without screwing the pooch > > > should we ever improve the root mount detection in the kernel. > > > > Set that where? At the disk1s1a:> prompt ? Still can't find kernel. > > num_ide_disks will help the kernel work out where the root filesystem > is. If you can't find the kernel, try 'ls' to start with, and then > send the output 'lsdev' > > I'm also curious why you get a 'disk1s1a' prompt, when it should be > disk3 (presuming you have a floppy disk). Have you installed new > bootblocks on your boot disk? I have installed the new bootblocks with disklabel -B -b /boot/boot1 -s /boot/boot2 /dev/da0s1. I use System Commander, that might have an influence too. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 14:27:43 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10148 for freebsd-current-outgoing; Sun, 17 Jan 1999 14:27:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10132; Sun, 17 Jan 1999 14:27:32 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id XAA06713; Sun, 17 Jan 1999 23:24:45 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199901172224.XAA06713@freebsd.dk> Subject: Re: Annoying messages on startup.. In-Reply-To: <32922.916607687@zippy.cdrom.com> from "Jordan K. Hubbard" at "Jan 17, 1999 1:14:47 pm" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Sun, 17 Jan 1999 23:24:45 +0100 (CET) Cc: jack@germanium.xtalwind.net, current@FreeBSD.ORG, gibbs@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Jordan K. Hubbard wrote: > > > Also, I suspect having acd in the kernel and wcd in MAKEDEV may > > lead to confusion for some people. > > I was under the impression that Soren was going to rename acd to wcd > before the branch. Oops, forgot about that one... In fact I was going to add BOTH instead, then those that cannot fathom the change can stay behind ;) I'll see if I can get around to it tomorrow.... -sos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 14:33:34 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11261 for freebsd-current-outgoing; Sun, 17 Jan 1999 14:33:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shell7.ba.best.com (shell7.ba.best.com [206.184.139.138]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11256 for ; Sun, 17 Jan 1999 14:33:33 -0800 (PST) (envelope-from spadger@shell7.ba.best.com) Received: (from spadger@localhost) by shell7.ba.best.com (8.9.2/8.9.2/best.sh) id OAA14740; Sun, 17 Jan 1999 14:32:12 -0800 (PST) From: Andrew Sparrow Message-Id: <199901172232.OAA14740@shell7.ba.best.com> Subject: RE: FreeBSD Celeron and Celeron ( Mendocino ) kernel patch. To: paul@originative.co.uk Date: Sun, 17 Jan 1999 14:32:11 -0800 (PST) Cc: wollman@khavrinen.lcs.mit.edu, culverk@wam.umd.edu, phiber@udel.edu, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I disagree. From an user perspective I think it will be confusing to > general users to report PII when they think they've got a Celeron. From > a support perspective it might be useful to know what CPU is actually > installed rather than just the class of CPU. FWIW, that would be my preference too. It's a warm fuzzy to know that the hardware was correctly identified, even if there's no specific optimisations for it. :) > On a related note, I'd be interested in benchmarks for the Celerons, how > does the on-chip cache compare to the off-chip cache. Very well, it seems. http://www.tomshardware.com has a bunch of benchmarks for the Celerons, both overclocked (overbussed) and regular speed(s), comparisons to AMD K6's and PIIs, as well as much interesting information on motherboards, chipsets and CPUs - including why the Slot 1 form factor is already doomed.. Cheers, AS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 14:51:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13721 for freebsd-current-outgoing; Sun, 17 Jan 1999 14:51:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-38-dbn.dial-up.net [196.34.155.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13713 for ; Sun, 17 Jan 1999 14:51:19 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id AAA28595; Mon, 18 Jan 1999 00:50:03 +0200 (SAT) From: Robert Nordier Message-Id: <199901172250.AAA28595@ceia.nordier.com> Subject: Re: possible problem with new boot loader ? In-Reply-To: <19990117133534.F28911@TelcoSucks.org> from Ulf Zimmermann at "Jan 17, 99 01:35:34 pm" To: ulf@Alameda.net Date: Mon, 18 Jan 1999 00:49:59 +0200 (SAT) Cc: rnordier@nordier.com, ulf@Alameda.net, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ulf Zimmermann wrote: > On Sun, Jan 17, 1999 at 06:29:30PM +0200, Robert Nordier wrote: > > Ulf Zimmermann wrote: > > Incidentally, do these bootblocks contain the BTX patch I sent you, > > or did you find some other way around that problem? > > This are the boot loaders from last night, just after make world > got through. On 12 Jan, you reported getting a BTX register dump on booting and I subsequently sent you a patch to src/sys/boot/i386/btx/btx/btx.s which seemed likely to resolve this problem (which has evidently now disappeared). Sorry to harp on this, but I'm trying to find out what caused the problem to disappear. Any clues? -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 14:52:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14215 for freebsd-current-outgoing; Sun, 17 Jan 1999 14:52:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14205 for ; Sun, 17 Jan 1999 14:52:39 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id JAA30159; Mon, 18 Jan 1999 09:22:33 +1030 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA18965; Mon, 18 Jan 1999 09:22:32 +1030 Date: Mon, 18 Jan 1999 09:22:31 +1030 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: Igor Shulgin Cc: Brian Feldman , FreeBSD-current Subject: Re: Running old program on 3.0-RELEASE In-Reply-To: <00ee01be4242$6e9cd800$870636c3@igorsh.garural.chel.su> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 17 Jan 1999, Igor Shulgin wrote: > Is it mistake in file rc.conf (I did not modify it before) or my system is > incorrectly configuring? If you're updating your system to 3.0 from 2.1, you will have MANY MANY outdated files in /etc. The system is not likely to work properly unless you update these - the problems with old a.out libraries is one of them. Check out /usr/ports/sysutils/mergemaster for a very handy way to manage this merge process (which should be run each time you update the system through 'make world' or a binary update). However, there may be so many changes from your 2.1 /etc that it's more practical to just `mv /etc /etc.old` and install the 3.x /etc over the top, then go through and restore passwd files and re-add any local configuration options. Kris ----- (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 14:55:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14596 for freebsd-current-outgoing; Sun, 17 Jan 1999 14:55:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles174.castles.com [208.214.165.174]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14591 for ; Sun, 17 Jan 1999 14:55:45 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA09325; Sun, 17 Jan 1999 14:52:15 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901172252.OAA09325@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: ulf@Alameda.net cc: Mike Smith , current@FreeBSD.ORG Subject: Re: possible problem with new boot loader ? In-reply-to: Your message of "Sun, 17 Jan 1999 14:23:59 PST." <19990117142359.J28911@TelcoSucks.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 17 Jan 1999 14:52:14 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > You need 'set num_ide_disks=2' > > > > > > > > The variable's somewhat misnamed, and I'm still groping for an > > > > algorithm that'll get it more or less right without screwing the pooch > > > > should we ever improve the root mount detection in the kernel. > > > > > > Set that where? At the disk1s1a:> prompt ? Still can't find kernel. > > > > num_ide_disks will help the kernel work out where the root filesystem > > is. If you can't find the kernel, try 'ls' to start with, and then > > send the output 'lsdev' > > > > I'm also curious why you get a 'disk1s1a' prompt, when it should be > > disk3 (presuming you have a floppy disk). Have you installed new > > bootblocks on your boot disk? > > I have installed the new bootblocks with disklabel -B -b /boot/boot1 -s /boot/boot2 /dev/da0s1. I use System Commander, that might have an influence > too. Which device is the bootstrap (not the bootloader) defaulting to? If it's 'wd(0,a)', then yes, it does seem that System Commander is at fault, since it should be passing in the BIOS unit number. If it's 'wd(2,a)', then it's doing the Right Thing. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 15:02:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA15462 for freebsd-current-outgoing; Sun, 17 Jan 1999 15:02:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA15443 for ; Sun, 17 Jan 1999 15:02:02 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.2/8.9.2) with ESMTP id XAA37691; Sun, 17 Jan 1999 23:01:41 GMT Message-ID: <36A26B96.3807E934@tdx.co.uk> Date: Sun, 17 Jan 1999 23:00:38 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: "Jordan K. Hubbard" CC: jack , current@FreeBSD.ORG Subject: Re: Heavy on the Verbosity (was) Re: Annoying messages on startup.. References: <33227.916611124@zippy.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > You can always have verbosity as a selective option. We're talking > about what to do for the great majority of users who aren't in your > shoes at all and don't want to be. True, although the messages (OK, admitadly not the ones we're talking about at the moment) are also usefull to others trying to diagnose the problem e.g. "My hard drive doesn't work - help" vs. "My hard drive doesn't work, what does 'timed out during SCB mean?' ;-) > You can always boot with -v to > have the messages in question, I'm not talking about removing them so > much as not making them the _default_. Don't worry, I don't want this > to become NT either. :) That would suite me, and by the look of it - the majority of people... I'm pretty confident we'll never see the day of the likes of "inetd[]: An unknown error occured while loading the pop3 service. The return data is the result code, 0x0f 0x02 0xff 0xfe". -Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 15:07:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16108 for freebsd-current-outgoing; Sun, 17 Jan 1999 15:07:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-49-dbn.dial-up.net [196.34.155.49]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA16098 for ; Sun, 17 Jan 1999 15:07:19 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id BAA29070; Mon, 18 Jan 1999 01:06:10 +0200 (SAT) From: Robert Nordier Message-Id: <199901172306.BAA29070@ceia.nordier.com> Subject: Re: possible problem with new boot loader ? In-Reply-To: <19990117134745.G28911@TelcoSucks.org> from Ulf Zimmermann at "Jan 17, 99 01:47:45 pm" To: ulf@Alameda.net Date: Mon, 18 Jan 1999 01:06:07 +0200 (SAT) Cc: rnordier@nordier.com, ulf@Alameda.net, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ulf Zimmermann wrote: > On Sun, Jan 17, 1999 at 06:29:30PM +0200, Robert Nordier wrote: > > Ulf Zimmermann wrote: > > The old bootblocks have a build setting BOOT_HD_BIAS to work > > around this problem. The new bootblocks rely on /boot.config. > > You can have > > > > 2:da(0,a) > > > > in /boot.config (ie. without a kernel name) to override just > > the unit number. > More info. With "2:da(0,a)" in /boot.config, a boot looks like this: > > /boot.config: 2:da(0,a) > / > BTX loader 0.01 BTX version is 0.87 > Console: internal video/keyboard > BIOS drive A: is disk0 > BIOS drive C: is disk1 > BIOS drive D: is disk2 > BIOS drive E: is disk3 > BIOS drive F: is disk4 Thanks. With the /boot.config setting, the bootblocks are evidently passing control to /boot/loader correctly; and it should also be possible to boot directly from boot2, if that's ever necessary. The issue of how to get /boot/loader to DTRT is something you'll have to take further with Mike (but I see that's going on already). -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 15:35:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20262 for freebsd-current-outgoing; Sun, 17 Jan 1999 15:35:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA20243 for ; Sun, 17 Jan 1999 15:35:04 -0800 (PST) (envelope-from fenner@parc.xerox.com) Received: from mango.parc.xerox.com ([13.1.102.232]) by alpha.xerox.com with SMTP id <52134(2)>; Sun, 17 Jan 1999 15:35:00 PST Received: from mango.parc.xerox.com (localhost.parc.xerox.com [127.0.0.1]) by mango.parc.xerox.com (8.8.8/8.8.8) with ESMTP id PAA21914; Sun, 17 Jan 1999 15:34:54 -0800 (PST) (envelope-from fenner@mango.parc.xerox.com) Message-Id: <199901172334.PAA21914@mango.parc.xerox.com> To: Mark Murray cc: "freebsd-current@FreeBSD.ORG" Subject: Re: Today's Make World In-reply-to: Your message of "Sun, 17 Jan 1999 02:36:56 PST." <199901171036.MAA16835@greenpeace.grondar.za> Date: Sun, 17 Jan 1999 15:34:53 PST From: Bill Fenner Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The one that failed: cc -c -nostdinc -O -pipe -DVERSION=\"1.03\" -DXS_VERSION=\"1.03\" -DPIC - fpic -I/usr/obj/usr/src/gnu/usr.bin/perl/perl -DPERL_CORE -DLIBC="" DynaLoader.c The one that succeeded: cc -c -DVERSION=\"1.03\" -DXS_VERSION=\"1.03\" -DPIC -fpic -I/usr/obj/us r/src/gnu/usr.bin/perl/perl -DPERL_CORE -DLIBC="" DynaLoader.c which is why I suggested that the -nostdinc caused the problem that people were seeing. Now, maybe the -nostdinc belongs there along with another -I to get the build environment instead of the host environment, but... Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 15:43:38 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA21554 for freebsd-current-outgoing; Sun, 17 Jan 1999 15:43:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from scotty.masternet.it (scotty.masternet.it [194.184.65.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA21483 for ; Sun, 17 Jan 1999 15:43:19 -0800 (PST) (envelope-from gmarco@scotty.masternet.it) Received: from suzy (modem38.masternet.it [194.184.65.48]) by scotty.masternet.it (8.8.8/8.8.8) with SMTP id AAA26108; Mon, 18 Jan 1999 00:42:38 +0100 (CET) (envelope-from gmarco@scotty.masternet.it) Message-Id: <4.1.19990118004756.0092d380@194.184.65.4> X-Sender: gmarco@scotty.masternet.it X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 18 Jan 1999 00:50:46 +0100 To: Christopher Knight From: Gianmarco Giovannelli Subject: Re: Problem booting from aic7890/91 Ultra2 SCSI Cc: current@FreeBSD.ORG In-Reply-To: <4.1.19990117112437.009c78f0@pop.ghostwheel.com> References: <4.1.19990117201046.009e2ad0@194.184.65.4> <4.1.19990116180852.00a9aea0@pop.ghostwheel.com> <4.1.19990117003737.009d4a80@194.184.65.4> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I didn't have it compiled in. :( > ># ># Laptop support (see LINT for more options) ># >#device apm0 at isa? disable flags 0x31 # Advanced Power >Management > > >Bust be something else, at least in my case. :-( Boh, I really don't understand... for me apm0, for another person was usb... I think we have to chek better what can break the booting process... scsi delay ? I have 10 ... and you ? Best Regards, Gianmarco Giovannelli (http://www.giovannelli.it/~gmarco) "Unix expert since yesterday" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 15:56:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA23697 for freebsd-current-outgoing; Sun, 17 Jan 1999 15:56:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA23689 for ; Sun, 17 Jan 1999 15:56:52 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id KAA05189; Mon, 18 Jan 1999 10:56:44 +1100 Date: Mon, 18 Jan 1999 10:56:44 +1100 From: Bruce Evans Message-Id: <199901172356.KAA05189@godzilla.zeta.org.au> To: kpielorz@tdx.co.uk, lcremean@tidalwave.net Subject: Re: Problems with new IDE's & -current Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> > The machine is a dual P90 (running SMP) - I get the problems even with a >> > single CPU kernel... It's running Neptune chipset (quite old) - and only >> > has 1 IDE channel. >> >> I would say that this has something to do with the DMA support, but since >> Neptune's IDE controller isn't DMA capable and PCI, that doesn't follow. >> Chances are that there's a not-quite-bad spot on your drive -- does it >> always seem to happen in the same place on the disk? > >Nope, it's more 'load' oriented than 'spot' oriented (i.e. the harder you push >them - the more of the above you get)... Both drives are brand new out the box >(for what it's worth), so I doub't they're 'bad'... DMA is disabled in the >kernel config as well, and the dmesg shows no hints of either multi-block or >DMA transfers... New models of IBM IDE drives are fast enough to consume a significant fraction (perhaps > 100%) of PIO mode 4 bandwidth (16.6 MB/s). Don't use them without DMA. Don't use them without UltraDMA (33.3 MB/s) if you want full performance. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 15:58:42 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24215 for freebsd-current-outgoing; Sun, 17 Jan 1999 15:58:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from babar.INS.CWRU.Edu (babar.INS.CWRU.Edu [129.22.8.213]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA24204 for ; Sun, 17 Jan 1999 15:58:40 -0800 (PST) (envelope-from csteva@crs.STUDENT.CWRU.Edu) Received: from crs (crs.STUDENT.CWRU.Edu [129.22.241.108]) by babar.INS.CWRU.Edu with SMTP (8.8.8+cwru/CWRU-3.4) id SAA06848; Sun, 17 Jan 1999 18:58:36 -0500 (EST) (from csteva@crs.cwru.edu for ) Message-ID: <006501be4275$44ec5b60$6cf11681@cwru.edu> From: "Chris Steva" To: Subject: ATM LANE support Date: Sun, 17 Jan 1999 18:58:24 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.0810.800 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was pleasantly surprised to find that FreeBSD 3.0 supported my FORE PCA-200e ATM card, but I wasn't able to get it up and running becuase there is no support for ethernet LANE (LAN emulation). Instead I found HARP, which appears to be some kind of substitue to LANE for running IP over ATM. Will there be support for LANE in the future? I havn't been able to find any information about what's is going on in FreeBSD ATM land. The Linux ATM world doesn't seem to be any further along, but I saw that they do have LANE support in their alpha release of ATM drivers. Chris -A very satisfied FreeBSD user and trapped on an ATM LANE network w/Win98. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 16:17:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA28943 for freebsd-current-outgoing; Sun, 17 Jan 1999 16:17:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from megaweapon.zigg.com (megaweapon.zigg.com [206.114.60.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA28910 for ; Sun, 17 Jan 1999 16:17:06 -0800 (PST) (envelope-from matt@zigg.com) Received: from localhost (matt@localhost) by megaweapon.zigg.com (8.9.2/8.9.2) with ESMTP id TAA00346; Sun, 17 Jan 1999 19:11:35 -0500 (EST) (envelope-from matt@zigg.com) Date: Sun, 17 Jan 1999 19:11:34 -0500 (EST) From: Matt Behrens To: FreeBSD-Current cc: System Account Subject: 0112-SNAP system hangs w/ incessant disk activity - softupdates related? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been running 3.0.0-19990112-SNAP for about half the weekend now and have run into the same problem twice while having several compile windows open. Both happened after I turned on softupdates on both my partitions (I have a / partition + swap on my first IDE drive, and a /usr partition on my second.) The system becomes totally unresponsive (console driver still seems to be running but the processes all seem to have hung) at some random point. The second time, I noticed my second hard drive was going totally crazy -- sounded like a `find /' or something. :) In both cases, I couldn't Ctrl-Alt-Del, so I rebooted. The first time, I didn't know what to expect -- but the standard fsck-if-not-clean "took care" of my problem on reboot. I didn't get to see many of the messages, but I did catch quite a few (and on the tail) clearing of unref files, many owned by me. They seemed to (and indeed did) correspond to some files that I was unpacking. Attributing it to just running into a random bug, I re-unpacked the files and went on. Several kernel recompiles later (I've noticed it takes a *lot* less time to recompile a kernel after a compile directory already exists, even though I'm running config each time... I take it 3.0's config doesn't clear the compile directory beforehand?), it happened again -- just a little while ago. I rebooted into single user and fsck -p'd both partitions, which proceeded to display quite a large number of incorrect block counts (most along the line of `12 should be 0' or something very similar), followed by the expected glob of unref files, and then it pronounced the filesystems clean. Just to make sure, I turned off softupdates for now, and am running all mounts sync again. (Especially since tomorrow I won't be around to flip the power if I need to.) Any ideas on what I should do? Should I, perhaps, make sure kernel compile directories are cleared all the time and the like? Or maybe I should just stick to sync, seeing as how I've got only 32M of real RAM? I was reading through the softupdates README and thought maybe it might have to do with hitting that `wall' and suddenly having to dump a very large amount of stuff to disk. In any case, it doesn't seem to be wiping stuff out that I haven't written to in that session, so I suppose I'm lucky. :) - Matt Behrens Network Administrator, zigg.com Engineer, Nameless IRC Network To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 16:31:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01065 for freebsd-current-outgoing; Sun, 17 Jan 1999 16:31:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oreo.adsu.bellsouth.com (oreo.adsu.bellsouth.com [205.152.173.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA01034 for ; Sun, 17 Jan 1999 16:31:10 -0800 (PST) (envelope-from ck@oreo.adsu.bellsouth.com) Received: (from ck@localhost) by oreo.adsu.bellsouth.com (8.9.1/8.9.1) id TAA97752 for freebsd-current@freebsd.org; Sun, 17 Jan 1999 19:31:05 -0500 (EST) (envelope-from ck) Date: Sun, 17 Jan 1999 19:31:05 -0500 From: Christian Kuhtz To: freebsd-current@FreeBSD.ORG Subject: how to snapshoot :) Message-ID: <19990117193105.G97318@oreo.adsu.bellsouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey gang: Can somebody throw me a pointer or lifeline so that I can build my own snapshots? This would greatly simply my task of keeping machines up to date over here where it is impractical to ride current all the time. I'd like to get to the point where I can have one server create a snapshot -current build whenever I feel like it and point everyone interested to it. This is particularly important because of all the behind-the-scenes coding going on. Any and all help would be greatly appreciated. Thanks, Chris -- "We are not bound by any concept, we are just bound to make any concept work better than others." -- Dr. Ferry Porsche [Disclaimer: I speak for myself and my views are my own and not in any way to be construed as the views of BellSouth Corporation. ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 16:39:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02636 for freebsd-current-outgoing; Sun, 17 Jan 1999 16:39:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA02625 for ; Sun, 17 Jan 1999 16:39:12 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id LAA24257; Mon, 18 Jan 1999 11:09:07 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id LAA55528; Mon, 18 Jan 1999 11:09:05 +1030 (CST) Date: Mon, 18 Jan 1999 11:09:05 +1030 From: Greg Lehey To: Christian Kuhtz Cc: freebsd-current@FreeBSD.ORG Subject: Re: how to snapshoot :) Message-ID: <19990118110905.Z55525@freebie.lemis.com> References: <19990117193105.G97318@oreo.adsu.bellsouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990117193105.G97318@oreo.adsu.bellsouth.com>; from Christian Kuhtz on Sun, Jan 17, 1999 at 07:31:05PM -0500 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 17 January 1999 at 19:31:05 -0500, Christian Kuhtz wrote: > > Hey gang: > > Can somebody throw me a pointer or lifeline so that I can build my own > snapshots? This would greatly simply my task of keeping machines up to date > over here where it is impractical to ride current all the time. Just check out the sources. Read http://www.lemis.com/staying-current or "The Complete FreeBSD" for more details. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 16:55:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA05345 for freebsd-current-outgoing; Sun, 17 Jan 1999 16:55:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mfo01.iij.ad.jp (mfo01.iij.ad.jp [202.232.2.118]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA05340 for ; Sun, 17 Jan 1999 16:55:55 -0800 (PST) (envelope-from tsuranu@po.iijnet.or.jp) Received: from sh0.po.iijnet.or.jp (sh0.po.iijnet.or.jp [202.232.2.1]) by mfo01.iij.ad.jp (8.8.8/MFO1.1) with ESMTP id JAA18075 for ; Mon, 18 Jan 1999 09:55:51 +0900 (JST) Received: from solo5100.po.iijnet.or.jp (x05-200.osaka.highway.ne.jp [210.159.124.200]) by sh0.po.iijnet.or.jp (8.8.8+ACL/PO1.1) with SMTP id JAA05780 for ; Mon, 18 Jan 1999 09:55:50 +0900 (JST) Message-Id: <199901180055.AA00297@solo5100.po.iijnet.or.jp> From: Yokoyama Tsuranu Date: Mon, 18 Jan 1999 09:55:34 +0900 To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 X-Mailer: AL-Mail32 Version 1.10 beta7 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG auth 294fcd6a unsubscribe freebsd-current tsuranu@po.iijnet.or.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 17:07:39 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA07413 for freebsd-current-outgoing; Sun, 17 Jan 1999 17:07:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA07408 for ; Sun, 17 Jan 1999 17:07:36 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from localhost (kpielorz@localhost) by caladan.tdx.co.uk (8.9.2/8.9.2) with ESMTP id BAA38295; Mon, 18 Jan 1999 01:07:16 GMT Date: Mon, 18 Jan 1999 01:07:16 +0000 (GMT) From: Karl Pielorz To: Bruce Evans cc: lcremean@tidalwave.net, current@FreeBSD.ORG Subject: Re: Problems with new IDE's & -current In-Reply-To: <199901172356.KAA05189@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 18 Jan 1999, Bruce Evans wrote: > New models of IBM IDE drives are fast enough to consume a significant > fraction (perhaps > 100%) of PIO mode 4 bandwidth (16.6 MB/s). Don't > use them without DMA. Don't use them without UltraDMA (33.3 MB/s) if > you want full performance. I presume the last "don't" should have been a 'do', i.e. _do_ use them with UltraDMA if you want full performance...? Also, the controller their running off isn't _Any_ DMA capable, at a guess it's going to be PIO4 tops, in which case (and as EIDA/UltraDMA are mean't to be 'backwards' compatible) - does this point to a bug/problem with the wdc driver? (i.e. drive too fast = wdc interrupt timeouts?) -Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 17:26:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA09995 for freebsd-current-outgoing; Sun, 17 Jan 1999 17:26:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA09984 for ; Sun, 17 Jan 1999 17:26:27 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:i4LK8OUX60C9ep0N0lTyMwKYXtj+wBde@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id KAA25636; Mon, 18 Jan 1999 10:26:04 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id KAA19816; Mon, 18 Jan 1999 10:28:35 +0900 (JST) Message-Id: <199901180128.KAA19816@zodiac.mech.utsunomiya-u.ac.jp> To: Kelvin Farmer cc: freebsd-current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: [Fwd: splash screen & xdm] In-reply-to: Your message of "Fri, 15 Jan 1999 23:25:25 EST." <36A014B5.5A7F15E5@trentu.ca> References: <36A00BE2.B7DB46AC@trentu.ca> <36A014B5.5A7F15E5@trentu.ca> Date: Mon, 18 Jan 1999 10:28:34 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >It seems that if the splash screen image is not cleared (ie: press any >> >key) before xdm starts up then once logged in the user is unable to >> >switch to a vitual terminal (ie: ctrl-alt-f1 etc), and it just beeps >> >when those keys are pressed. >> >Solution? Putting the command kldunload splash_bmp before the line that >> >loads xdm seems to work. Is this a bug or just the way things are? >> >> Definitely a bug. >> >> Which version of the X server are you using? > >3.3.3.1 Please apply the following patch to /sys/dev/syscons/syscons.c and see if it works for you. (It works for me, at least.) Kazu Index: syscons.c =================================================================== RCS file: /src/CVS/src/sys/dev/syscons/syscons.c,v retrieving revision 1.291 diff -u -r1.291 syscons.c --- syscons.c 1999/01/13 01:14:26 1.291 +++ syscons.c 1999/01/18 01:19:33 @@ -1450,11 +1479,15 @@ return EINVAL; case VT_ACTIVATE: /* switch to screen *data */ + scsplash_stick(FALSE); + sc_clean_up(cur_console); return switch_scr(scp, *(int *)data - 1); case VT_WAITACTIVE: /* wait for switch to occur */ if (*(int *)data > MAXCONS || *(int *)data < 0) return EINVAL; + scsplash_stick(FALSE); + sc_clean_up(cur_console); if (minor(dev) == *(int *)data - 1) return 0; if (*(int *)data == 0) { To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 17:28:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA10200 for freebsd-current-outgoing; Sun, 17 Jan 1999 17:28:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA10193 for ; Sun, 17 Jan 1999 17:28:09 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (doconnor@lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA27934; Mon, 18 Jan 1999 11:57:32 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199901170937.LAA16540@greenpeace.grondar.za> Date: Mon, 18 Jan 1999 12:00:52 +1030 (CST) From: "Daniel O'Connor" To: Mark Murray Subject: Re: Today's Make World Cc: "freebsd-current@FreeBSD.ORG" Cc: "freebsd-current@FreeBSD.ORG" , "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Jan-99 Mark Murray wrote: > > Every -current release I try and build falls over with this one. > > Tried making a release lately? :) > Aaaah! _Releases_ are broken? For how long? Hmm.. I did make release on the 12th (or so :) and it generates broken boot disks/cdroms :( (ie it doesn't put /boot/loader on) The fixit CD seems OK tho, but we don't boot off it :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 17:46:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA12812 for freebsd-current-outgoing; Sun, 17 Jan 1999 17:46:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA12777 for ; Sun, 17 Jan 1999 17:46:05 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id MAA16732; Mon, 18 Jan 1999 12:45:57 +1100 Date: Mon, 18 Jan 1999 12:45:57 +1100 From: Bruce Evans Message-Id: <199901180145.MAA16732@godzilla.zeta.org.au> To: bde@zeta.org.au, kpielorz@tdx.co.uk Subject: Re: Problems with new IDE's & -current Cc: current@FreeBSD.ORG, lcremean@tidalwave.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> New models of IBM IDE drives are fast enough to consume a significant >> fraction (perhaps > 100%) of PIO mode 4 bandwidth (16.6 MB/s). Don't >> use them without DMA. Don't use them without UltraDMA (33.3 MB/s) if >> you want full performance. > >I presume the last "don't" should have been a 'do', i.e. _do_ use them >with UltraDMA if you want full performance...? Don't use without == do use with. >Also, the controller their running off isn't _Any_ DMA capable, at a guess >it's going to be PIO4 tops, in which case (and as EIDA/UltraDMA are mean't >to be 'backwards' compatible) - does this point to a bug/problem with the >wdc driver? (i.e. drive too fast = wdc interrupt timeouts?) This is a general problem with i/o capabilties exceeding system capabilities. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 18:08:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA15846 for freebsd-current-outgoing; Sun, 17 Jan 1999 18:08:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA15839 for ; Sun, 17 Jan 1999 18:08:15 -0800 (PST) (envelope-from arg@arg1.demon.co.uk) Received: from localhost (arg@localhost) by arg1.demon.co.uk (8.8.8/8.8.8) with SMTP id CAA11387; Mon, 18 Jan 1999 02:06:32 GMT (envelope-from arg@arg1.demon.co.uk) Date: Mon, 18 Jan 1999 02:06:27 +0000 (GMT) From: Andrew Gordon X-Sender: arg@server.arg.sj.co.uk To: Christopher Knight cc: Gianmarco Giovannelli , current@FreeBSD.ORG Subject: Re: Problem booting from aic7890/91 Ultra2 SCSI In-Reply-To: <4.1.19990117112437.009c78f0@pop.ghostwheel.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 17 Jan 1999, Christopher Knight wrote: > At 08:11 PM 1/17/99 +0100, Gianmarco Giovannelli wrote: > > >Please try to remove apm0 , if you have ... here it seems to solve the > >problem (after 15 reboot no problem...) > > I didn't have it compiled in. :( > > # > # Laptop support (see LINT for more options) > # > #device apm0 at isa? disable flags 0x31 # Advanced Power > Management There seems to be some interaction with APM even without apm0 compiled in. I have a motherboard (AMI bios, about 1 year old) which works fine if APM is disabled in the BIOS setup, but with it enabled: - 2.2.x kernels seem to work fine. - 3.0R boot floppy boots and installs OK - 3.0R GENERIC kernel doesn't work - current kernels built in the past week or so don't work. All the above is exactly the same whether using "old" or "new" bootblocks. The combinations that "don't work" crash at a very early stage - you get the line printed by the loader showing the size of the kernel code/data/etc, then absolutely nothing more - no kernel startup, device probing or whatever. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 19:15:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27724 for freebsd-current-outgoing; Sun, 17 Jan 1999 19:15:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA27682 for ; Sun, 17 Jan 1999 19:15:36 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id EAA00600 for freebsd-current@FreeBSD.ORG; Mon, 18 Jan 1999 04:15:22 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 698D21574; Mon, 18 Jan 1999 02:15:22 +0100 (CET) Date: Mon, 18 Jan 1999 02:15:22 +0100 From: Ollivier Robert To: "FreeBSD Current Users' list" Subject: vinum is always started at boot-time... Message-ID: <19990118021522.A443@keltia.freenix.fr> Mail-Followup-To: FreeBSD Current Users' list Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4994 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ...regardless of the "vinum_slices" setting. It is not a nice thing considering the size of the vinum kld (a6000 bytes). "if [ -n $vinum_slices ]" doesn't seem to work. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #67: Tue Dec 29 20:24:02 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 19:21:52 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA28596 for freebsd-current-outgoing; Sun, 17 Jan 1999 19:21:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA28589 for ; Sun, 17 Jan 1999 19:21:49 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 1025G4-0000C7-00; Sun, 17 Jan 1999 20:21:44 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id UAA43305; Sun, 17 Jan 1999 20:21:14 -0700 (MST) Message-Id: <199901180321.UAA43305@harmony.village.org> To: Chuck Robey Subject: Re: CTM <> CVSUP differences Cc: Boris Staeblow , current@FreeBSD.ORG In-reply-to: Your message of "Fri, 15 Jan 1999 20:46:23 EST." References: Date: Sun, 17 Jan 1999 20:21:13 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Chuck Robey writes: : In terms of convenience, cvsup is supreme, but in terms of stability, : Poul's baby here is the champ, so you have to really consider other : places of corruption first. I've had problems when I get > 30 parts at one time on the fast list... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 19:22:53 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA28837 for freebsd-current-outgoing; Sun, 17 Jan 1999 19:22:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fw.bby.com.au (ns.bby.com.au [192.83.119.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA28830 for ; Sun, 17 Jan 1999 19:22:49 -0800 (PST) (envelope-from gnb@itga.com.au) Received: (from daemon@localhost) by fw.bby.com.au (8.8.8/8.6.9) id OAA28921; Mon, 18 Jan 1999 14:21:48 +1100 (EST) Received: from melba.bby.com.au(192.43.186.1) via SMTP by fw.bby.com.au, id smtpd028919; Mon Jan 18 03:21:46 1999 Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by melba.bby.com.au (8.8.2/8.8.2) with ESMTP id OAA16569; Mon, 18 Jan 1999 14:21:46 +1100 (EST) Received: from lightning (lightning [192.168.71.20]) by lightning.itga.com.au (8.9.1a/8.9.1) with ESMTP id OAA06491; Mon, 18 Jan 1999 14:21:43 +1100 (EST) Message-Id: <199901180321.OAA06491@lightning.itga.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: Ollivier Robert Cc: "FreeBSD Current Users' list" Subject: Re: vinum is always started at boot-time... In-reply-to: Your message of Mon, 18 Jan 1999 02:15:22 +0100. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 Jan 1999 14:21:43 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG noticed this when it tried to create lotsa devices in a read-only /dev at boot time. Patch: hellcat## diff -u rc.orig rc --- rc.orig Mon Jan 18 14:20:49 1999 +++ rc Mon Jan 18 14:20:59 1999 @@ -27,7 +27,7 @@ ccdconfig -C fi -if [ -n $vinum_slices ]; then +if [ -n "$vinum_slices" ]; then if [ -r /modules/vinum.ko ]; then # jkh paranoia kldload vinum vinum read $vinum_slices To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 19:25:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA29273 for freebsd-current-outgoing; Sun, 17 Jan 1999 19:25:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA29266 for ; Sun, 17 Jan 1999 19:25:22 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id NAA25121 for ; Mon, 18 Jan 1999 13:55:16 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id NAA28411 for freebsd-current@FreeBSD.ORG; Mon, 18 Jan 1999 13:55:15 +1030 (CST) Date: Mon, 18 Jan 1999 13:55:14 +1030 From: Greg Lehey To: "FreeBSD Current Users' list" Subject: Re: vinum is always started at boot-time... Message-ID: <19990118135514.Y55525@freebie.lemis.com> References: <19990118021522.A443@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990118021522.A443@keltia.freenix.fr>; from Ollivier Robert on Mon, Jan 18, 1999 at 02:15:22AM +0100 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 18 January 1999 at 2:15:22 +0100, Ollivier Robert wrote: > ...regardless of the "vinum_slices" setting. It is not a nice thing > considering the size of the vinum kld (a6000 bytes). > > "if [ -n $vinum_slices ]" doesn't seem to work. Ugh. It wants to be if [ -n "$vinum_slices" ] Fixed. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 19:39:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA01234 for freebsd-current-outgoing; Sun, 17 Jan 1999 19:39:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA01215 for ; Sun, 17 Jan 1999 19:39:27 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:iFNtvgqX3v0dNoFdyK2/Qvpdbwp1l2Wt@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id MAA26417; Mon, 18 Jan 1999 12:39:07 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id MAA23586; Mon, 18 Jan 1999 12:41:39 +0900 (JST) Message-Id: <199901180341.MAA23586@zodiac.mech.utsunomiya-u.ac.jp> To: Oliver Fromme cc: freebsd-current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: New syscons + XFree 3.3.3.1 = problem? In-reply-to: Your message of "Sun, 17 Jan 1999 18:49:51 +0100." <199901171749.SAA08436@dorifer.heim3.tu-clausthal.de> References: <199901171749.SAA08436@dorifer.heim3.tu-clausthal.de> Date: Mon, 18 Jan 1999 12:41:38 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I'm using -current as of 1998-01-14 with the new syscons (with >separated keyboard driver) and XFree86 3.3.3.1 (XF86_SVGA on a >Matrox G200). The keyboard and mouse are plain PS/2 models, >they work fine under syscons (i.e. not using XFree). [...] >XFree used to allocate the next free virtual terminal when >started (in this case the 11th), Yes, and it still should be. >but that doesn't happen any- >more. Instead, it uses the current one (i.e. if I'm on ttyv3 >and start X, it uses ttyv3). Is this intentional, or is it a >bug? Hmm, no, this shouldn't be happening. How do you start X, by hand, or via a local shell script (i.e. rc.local or something), or via /etc/ttys? >While the above isn't really a serious problem, the following >is: When X has run for some time, the keyboard suddenly starts >being unresponsive and unusable. This can happen after a few >minutes or after a few hours. There are no error messages, no >syslog entries. It looks like the keypresses don't get to >XFree anymore, but to the vty beneath. Restarting X helps, >until it happens again. Quite annoying. It sounds like the X server and getty is fighting for keyboard input... How many vtys do you have (check MAXCONS in the kernel config)? How many of which will run getty (check /etc/ttys)? Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 19:53:41 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA03709 for freebsd-current-outgoing; Sun, 17 Jan 1999 19:53:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtpott1.nortel.ca (smtpott1.nortel.ca [192.58.194.78]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA03684 for ; Sun, 17 Jan 1999 19:53:31 -0800 (PST) (envelope-from atrens@nortelnetworks.com) Received: from zcars01t by smtpott1; Sun, 17 Jan 1999 22:52:57 -0500 Received: from wmerh01z.ca.nortel.com by zcars01t; Sun, 17 Jan 1999 22:52:22 -0500 Received: from hcarp00g.ca.nortel.com (atrens@hcarp00g.ca.nortel.com@wmerh01z) by wmerh01z.ca.nortel.com with ESMTP (8.7.1/8.7.1) id WAA21901; Sun, 17 Jan 1999 22:52:22 -0500 (EST) Date: Sun, 17 Jan 1999 23:01:38 -0500 (EST) From: "Andrew Atrens" Reply-To: "Andrew Atrens" To: Karl Pielorz cc: current@FreeBSD.ORG Subject: Re: Problems with new IDE's & -current In-Reply-To: <36A24D5E.F1875A83@tdx.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 17 Jan 1999, Karl Pielorz wrote: Karl, Let's see your (dmesg) probe messages ... :) they may shed some light on what's happening. I don't claim to be an expert on wd.c but from what I can tell it seems that controller and drive capabilities are probed separately, its conceivable you've hit upon an untested code path. ide_pci.c has been changing a lot lately (probably four times in the last seven days) - after capturing your dmesg output, try a fresh kernel and look for differences in probed controller/drive capabilities... Andrew. +----------------------------------------------------+ = Andrew Atrens - Nortel Networks (atrens@nortel.ca) = = P.O. Box 3511, Station C Ottawa, Canada = = = = All opinions expressed are mine, not Nortel's. = +----------------------------------------------------+ -- > Date: Sun, 17 Jan 1999 20:51:42 +0000 > From: Karl Pielorz > To: current@FreeBSD.ORG > Subject: Problems with new IDE's & -current > > Hi, > > I have a system that's meant as a 'backup disk spool' - it has a 2Gb SCSI > drive to boot from, and then 2 x 16Gb IDE drives (IBM-DTTA-351680's). > > The system works fine so long as I stick to using the SCSI drives... If I use > the IDE's (e.g. backup another machine to them, tar / untar 'usr/src' to them) > I start getting problems, > > e.g. > > Jan 14 13:01:42 magpie /kernel: wd0: interrupt timeout: > Jan 14 13:01:42 magpie /kernel: wd0: status 58 error 0 > Jan 15 17:56:52 magpie /kernel: lnc0: Missed packet -- no receive buffer > Jan 15 17:57:43 magpie /kernel: lnc0: Missed packet -- no receive buffer > > The machine also has an NE-2100 embedded network card. We have 4 other > identical machines to this, all SCSI based - all work without any problems... > > Is there anything that can be done? - at a guess I'd say the IDE's/wcd0 are > timing out on interrupts, which is then stuffing the network (as the systems > been waiting around too long for wcd0's IRQ's?)... > > The machine is a dual P90 (running SMP) - I get the problems even with a > single CPU kernel... It's running Neptune chipset (quite old) - and only has 1 > IDE channel. > > Any pointers? - The drives do appear to work OK, i.e. no corruption, but the > _whole_ machine appears to 'stall' when the above occurs = not good... :-( > > I've tried 3.0-Release and 3.0-Current as of 7th Jan, '99 - Both exhibit > identical symptoms... > > -Kp > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 19:57:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA04498 for freebsd-current-outgoing; Sun, 17 Jan 1999 19:57:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA04493 for ; Sun, 17 Jan 1999 19:57:56 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id TAA28775; Sun, 17 Jan 1999 19:57:51 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id TAA22127; Sun, 17 Jan 1999 19:57:50 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sun, 17 Jan 1999 19:57:50 -0800 (PST) Message-Id: <199901180357.TAA22127@vashon.polstra.com> To: herbelot@cybercable.fr Subject: Re: correction for find(1)'s man page Newsgroups: polstra.freebsd.current In-Reply-To: <36A0FC11.8B22D0F5@cybercable.fr> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <36A0FC11.8B22D0F5@cybercable.fr>, Thierry Herbelot wrote: > Hello > > I was reading the man page for find(1), looking for the precise option > to follow symbolic links. > > This option is -follow, of course, but it is not described in the man > page Huh? The correct options are the first three options described in the man page: -H The -H option causes the file information and file type (see stat(2)) returned for each symbolic link specified on the command line to be those of the file referenced by the link, not the link itself. If the referenced file does not exist, the file informa- tion and type will be for the link itself. File information of all symbolic links not on the command line is that of the link itself. -L The -L option causes the file information and file type (see stat(2)) returned for each symbolic link to be those of the file referenced by the link, not the link itself. If the referenced file does not exist, the file information and type will be for the link itself. -P The -P option causes the file information and file type (see stat(2)) returned for each symbolic link to be those of the link itself. This is the default. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 20:04:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA05571 for freebsd-current-outgoing; Sun, 17 Jan 1999 20:04:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from iip-lab.ics.es.osaka-u.ac.jp (iip-lab.ics.es.osaka-u.ac.jp [133.1.12.191]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA05561 for ; Sun, 17 Jan 1999 20:04:05 -0800 (PST) (envelope-from matusita@ics.es.osaka-u.ac.jp) Received: from localhost (martini.ics.es.osaka-u.ac.jp [133.1.12.88]) by iip-lab.ics.es.osaka-u.ac.jp (8.8.8/3.6W/ICS-2.2.2v7-44BSD) with ESMTP id NAA03731 for ; Mon, 18 Jan 1999 13:03:09 +0900 (JST) In-Reply-To: <19990118135514.Y55525@freebie.lemis.com> References: <19990118021522.A443@keltia.freenix.fr> <19990118021522.A443@keltia.freenix.fr> <19990118135514.Y55525@freebie.lemis.com> X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V User-Agent: Mew/1.94b2 XEmacs/21.2 (Artemis) X-SKK-Version: 10.47.6.2 X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) X-Fingerprint: 0C AC 93 FC E3 9D 9E 5B 3D B8 AC 5C 4A 79 D8 A6 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 981124(IM104) Lines: 25 From: Makoto MATSUSHITA (=?ISO-2022-JP?B?GyRCJF4kRCQ3JD8kXiQzJEgbKEI=?=) To: current@FreeBSD.ORG Subject: Re: vinum is always started at boot-time... Date: Mon, 18 Jan 1999 13:03:53 +0900 Message-Id: <19990118130353I.matusita@ics.es.osaka-u.ac.jp> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry donno who set "$vinum_slide" variable, however, grog> Ugh. It wants to be grog> if [ -n "$vinum_slices" ] why not do as the CCD do? Anybody have the answer? if [ -f /etc/vinum.conf ]; vinum create /etc/vinum.conf >/dev/null 2>&1 fi Smart and simple enough? And, why we should always do kldload the vinum module? Built-in the vinum module into kernel (say "pseudo-device vinum" in kernel config file) is prohibited? Sorry I do not know how to decide that vinum (or whatever feature) is already built-in or should be kldload after the kernel starts, but now we have /boot/loader; pre-loading the modules is quite easy (see the usage of splash module), and maybe it's not /etc/rc's business. -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 20:12:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA07206 for freebsd-current-outgoing; Sun, 17 Jan 1999 20:12:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.atl.bellsouth.net (mail.atl.bellsouth.net [205.152.0.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA07201 for ; Sun, 17 Jan 1999 20:12:38 -0800 (PST) (envelope-from wghicks@bellsouth.net) Received: from wghicks.bellsouth.net (host-209-214-65-160.atl.bellsouth.net [209.214.65.160]) by mail.atl.bellsouth.net (8.8.8-spamdog/8.8.5) with ESMTP id XAA01309; Sun, 17 Jan 1999 23:12:20 -0500 (EST) Received: from wghicks (localhost [127.0.0.1]) by wghicks.bellsouth.net (8.9.2/8.9.2) with ESMTP id XAA49378; Sun, 17 Jan 1999 23:28:37 -0500 (EST) (envelope-from wghicks@wghicks.bellsouth.net) Message-Id: <199901180428.XAA49378@bellsouth.net> To: Christian Kuhtz Cc: freebsd-current@FreeBSD.ORG Subject: Re: how to snapshoot :) In-reply-to: Your message of "Sun, 17 Jan 1999 19:31:05 EST." <19990117193105.G97318@oreo.adsu.bellsouth.com> Date: Sun, 17 Jan 1999 23:28:37 -0500 From: W Gerald Hicks Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Chris, You've got ports/net/cvsup-mirror installed and functional right? That is the best way I know to keep up a local repository, which is also a prerequisite for spinning a release. The other necessity is to have gobs of disk space. It's recommended to have no less than 1GB free disk space on the drive to build the image. I like to leave a healthy margin above that too. You'll be happier with a fast system and lots of ram, but that isn't a strict requirement if you're patient enough ;-) First thing to do is get through a make {build,install}world and leave the objects generated in /usr/obj I'd recommend *not* building the docs and ports from within your first 'make release' attempts (more on ports later). It's a bit tricky sometimes if you have transient internet access to get the distfiles thing right. Here's the script I use: #!/bin/sh cd /usr/src/release mkdir /usr/local/FreeBSD-GEN || exit 1 CVSROOT=/home/ncvs export nice nohup make NOPORTS=yes NODOCS=yes RELEASENAME=3.0-CURRENT \ CHROOTDIR=/usr/local/FreeBSD-GEN release 2>&1 > /var/tmp/release.log & tail -f /var/tmp/release.log # end of script To me, the really interesting part about the release generation process is how it's done inside of a chrooted environment. Once you've generated your target images, this environment is left behind as an artifact in /usr/local/FreeBSD-GEN (for my example). If you're interested in prebuilding packages for later installations this is most convenient. You'll need to either copy relevant distfiles into /usr/local/FreeBSD-GEN/usr/ports/distfiles or be sure to establish internet connectivity before doing something like this: # cd /usr/local/FreeBSD-GEN/ # pwd /usr/local/FreeBSD-GEN # chroot . /bin/sh # pwd / # cd /usr/ports/devel/gmake && make package # exit # pwd /usr/local/FreeBSD-GEN A working null filesystem layer would be useful here for distfiles, but I'm not smart enough to fix it. :-( I try to leave everything intact in the target directory between builds, just in case I need to go hack together a special boot floppy or something. It's been a great help for us on several occasions. This environment is also where I generate custom PicoBSD images for a few special things were doing here. Hope all this is reasonably correct and helps :-) Feel free to drop me a line if you get stuck or need any clarification. Cheers, Jerry Hicks wghicks@bellsouth.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 20:16:53 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA07964 for freebsd-current-outgoing; Sun, 17 Jan 1999 20:16:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA07953 for ; Sun, 17 Jan 1999 20:16:46 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id OAA25483; Mon, 18 Jan 1999 14:46:40 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id OAA59631; Mon, 18 Jan 1999 14:46:37 +1030 (CST) Date: Mon, 18 Jan 1999 14:46:36 +1030 From: Greg Lehey To: Makoto MATSUSHITA Cc: current@FreeBSD.ORG Subject: Re: vinum is always started at boot-time... Message-ID: <19990118144636.B55525@freebie.lemis.com> References: <19990118021522.A443@keltia.freenix.fr> <19990118021522.A443@keltia.freenix.fr> <19990118135514.Y55525@freebie.lemis.com> <19990118130353I.matusita@ics.es.osaka-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990118130353I.matusita@ics.es.osaka-u.ac.jp>; from Makoto MATSUSHITA on Mon, Jan 18, 1999 at 01:03:53PM +0900 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 18 January 1999 at 13:03:53 +0900, Makoto MATSUSHITA wrote: > > Sorry donno who set "$vinum_slide" variable, however, > > grog> Ugh. It wants to be > grog> if [ -n "$vinum_slices" ] > > why not do as the CCD do? Anybody have the answer? > > if [ -f /etc/vinum.conf ]; > vinum create /etc/vinum.conf >/dev/null 2>&1 > fi > > Smart and simple enough? Because it doesn't work like that. The config is stored in the disk labels, not in a static (and not necessarily correct) config file. The config file is only for the first-time create. > And, why we should always do kldload the vinum module? Because I believe that's the correct way to do it. > Built-in the vinum module into kernel (say "pseudo-device vinum" in > kernel config file) is prohibited? Currently, yes. Peter put in hooks to statically configure Vinum, but THEY ARE NOT TESTED. Not at all. Please don't use them, or if you do, tell me only about the fixes you make. > Sorry I do not know how to decide that vinum (or whatever feature) > is already built-in or should be kldload after the kernel starts, > but now we have /boot/loader; pre-loading the modules is quite easy > (see the usage of splash module), and maybe it's not /etc/rc's > business. That's a valid point. When the bootstrap stops moving long enough for me to catch it, I'll look at that. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 20:30:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA10104 for freebsd-current-outgoing; Sun, 17 Jan 1999 20:30:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pobox.com (planetx-1-97.mdm.mkt.execpc.com [169.207.119.97]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA10098 for ; Sun, 17 Jan 1999 20:30:11 -0800 (PST) (envelope-from hamilton@pobox.com) Message-Id: <199901180430.UAA10098@hub.freebsd.org> Received: (qmail 6191 invoked from network); 17 Jan 1999 22:29:30 -0600 Received: from localhost (HELO pobox.com) (127.0.0.1) by localhost with SMTP; 17 Jan 1999 22:29:30 -0600 To: John Polstra cc: herbelot@cybercable.fr, current@FreeBSD.ORG Subject: Re: correction for find(1)'s man page In-reply-to: Your message of "Sun, 17 Jan 1999 19:57:50 PST." <199901180357.TAA22127@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 17 Jan 1999 22:29:30 -0600 From: Jon Hamilton Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199901180357.TAA22127@vashon.polstra.com>, John Polstra wrote: } In article <36A0FC11.8B22D0F5@cybercable.fr>, } Thierry Herbelot wrote: } > Hello } > } > I was reading the man page for find(1), looking for the precise option } > to follow symbolic links. } > } > This option is -follow, of course, but it is not described in the man } > page } } Huh? The correct options are the first three options described in } the man page: } -H The -H option causes the file information and file type (see } stat(2)) returned for each symbolic link specified on the command } line to be those of the file referenced by the link, not the link } itself. If the referenced file does not exist, the file informa- } tion and type will be for the link itself. File information of } all symbolic links not on the command line is that of the link } itself. What this doesn't explicitly say is that it causes find(1) to actually follow the symlink and recursively descend the target tree (if the link points to a directory); I assume that's the behavior the original poster wanted. Near the bottom of the find(1) manpage (on my -stable system), is this: Historically, the -d, -h and -x options were implemented using the pri- maries ``-depth'', ``-follow'', and ``-xdev''. These primaries always ``-h'' there should read ``-H''; -h is an unknown option to find(1). -- Jon Hamilton hamilton@pobox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 20:52:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA13508 for freebsd-current-outgoing; Sun, 17 Jan 1999 20:52:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from iip-lab.ics.es.osaka-u.ac.jp (iip-lab.ics.es.osaka-u.ac.jp [133.1.12.191]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA13503 for ; Sun, 17 Jan 1999 20:52:03 -0800 (PST) (envelope-from matusita@ics.es.osaka-u.ac.jp) Received: from localhost (martini.ics.es.osaka-u.ac.jp [133.1.12.88]) by iip-lab.ics.es.osaka-u.ac.jp (8.8.8/3.6W/ICS-2.2.2v7-44BSD) with ESMTP id NAA03923 for ; Mon, 18 Jan 1999 13:51:13 +0900 (JST) In-Reply-To: <19990118144636.B55525@freebie.lemis.com> References: <19990118021522.A443@keltia.freenix.fr> <19990118021522.A443@keltia.freenix.fr> <19990118135514.Y55525@freebie.lemis.com> <19990118130353I.matusita@ics.es.osaka-u.ac.jp> <19990118144636.B55525@freebie.lemis.com> X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V User-Agent: Mew/1.94b2 XEmacs/21.2 (Artemis) X-SKK-Version: 10.47.6.2 X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) X-Fingerprint: 0C AC 93 FC E3 9D 9E 5B 3D B8 AC 5C 4A 79 D8 A6 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 981124(IM104) Lines: 18 From: Makoto MATSUSHITA (=?ISO-2022-JP?B?GyRCJF4kRCQ3JD8kXiQzJEgbKEI=?=) To: current@FreeBSD.ORG Subject: Re: vinum is always started at boot-time... Date: Mon, 18 Jan 1999 13:51:57 +0900 Message-Id: <19990118135157W.matusita@ics.es.osaka-u.ac.jp> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG grog> Because it doesn't work like that. The config is stored in the grog> disk labels, not in a static (and not necessarily correct) grog> config file. The config file is only for the first-time create. O.K. I understand (not 'vinum create' but 'vinum read'). Would you please ('cause I don't know :-) how to set the "vinum_slice" variable? We don't include /etc/rc.conf in such an early stage of /etc/rc... grog> Currently, yes. Peter put in hooks to statically configure grog> Vinum, but THEY ARE NOT TESTED. Not at all. Please don't use grog> them, or if you do, tell me only about the fixes you make. Hmm, I've used vinum without module (built-in the kernel). It works for a week... Anyway, I'll stop it and switch to kldloading... thank you. -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 21:08:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15620 for freebsd-current-outgoing; Sun, 17 Jan 1999 21:08:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA15587 for ; Sun, 17 Jan 1999 21:08:14 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id PAA25811; Mon, 18 Jan 1999 15:38:08 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.2/8.9.0) id PAA91525; Mon, 18 Jan 1999 15:38:06 +1030 (CST) Date: Mon, 18 Jan 1999 15:38:05 +1030 From: Greg Lehey To: Makoto MATSUSHITA Cc: current@FreeBSD.ORG Subject: Re: vinum is always started at boot-time... Message-ID: <19990118153804.D55525@freebie.lemis.com> References: <19990118021522.A443@keltia.freenix.fr> <19990118021522.A443@keltia.freenix.fr> <19990118135514.Y55525@freebie.lemis.com> <19990118130353I.matusita@ics.es.osaka-u.ac.jp> <19990118144636.B55525@freebie.lemis.com> <19990118135157W.matusita@ics.es.osaka-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990118135157W.matusita@ics.es.osaka-u.ac.jp>; from Makoto MATSUSHITA on Mon, Jan 18, 1999 at 01:51:57PM +0900 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 18 January 1999 at 13:51:57 +0900, Makoto MATSUSHITA wrote: > > grog> Because it doesn't work like that. The config is stored in the > grog> disk labels, not in a static (and not necessarily correct) > grog> config file. The config file is only for the first-time create. > > O.K. I understand (not 'vinum create' but 'vinum read'). Would you > please ('cause I don't know :-) how to set the "vinum_slice" variable? > We don't include /etc/rc.conf in such an early stage of /etc/rc... Oops. This was a thoroughly successful commit, wasn't it? At least it didn't break `make world'. I'll think out another way and test more thoroughly. How does this look? if [ -f /etc/vinumslices ]; then read /etc/vinumslices if [ -r /modules/vinum.ko ]; then # jkh paranoia kldload vinum vinum read $vinum_slices else echo "Can't find /modules/vinum.ko" fi fi > grog> Currently, yes. Peter put in hooks to statically configure > grog> Vinum, but THEY ARE NOT TESTED. Not at all. Please don't use > grog> them, or if you do, tell me only about the fixes you make. > > Hmm, I've used vinum without module (built-in the kernel). It works > for a week... Anyway, I'll stop it and switch to kldloading... thank you. OK, I take that back. You can also tell me about your successes :-) There's still one way you can shoot yourself in the foot with statically configured Vinum: unless you specify VINUMDEBUG, you can find yourself out of sync with Vinum(8): they pass structures via ioctl, and some of the structures include debugging information. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 21:52:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA21872 for freebsd-current-outgoing; Sun, 17 Jan 1999 21:52:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from opus.cts.cwu.edu (opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA21859; Sun, 17 Jan 1999 21:52:02 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.9.1/8.9.1) with SMTP id VAA11700; Sun, 17 Jan 1999 21:51:58 -0800 (PST) Date: Sun, 17 Jan 1999 21:51:58 -0800 (PST) From: Chris Timmons To: freebsd-current@FreeBSD.ORG cc: John Polstra , luoqi@FreeBSD.ORG Subject: NFS: likely problem is vfs_bio.c rev 1.188 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra did some leg work and found a few candidate commits which he suggested backing out one by one to see if they affected the current situation with NFS. On the server I downgraded vfs_bio.c to rev 1.187 & rebooted; no luck. I then installed the same kernel (with the downgraded vfs_bio.c) to the client. Bingo. With both NFS client & server machine running rev 1.187, the problem so far as building XFree86-contrib from an NFS mounted /usr/ports disappears. As Chuck Robey noted, it seems like the client's writes are not completely being committed to the server, which results in partially baked files which are truncated. Unfortunately -r1.188 -r1.187 doesn't apply cleanly, so there's some work to be done by Eivind to adapt his subsequent commits if we were to say, back out 1.188 prior to the branch. -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 21:55:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA22116 for freebsd-current-outgoing; Sun, 17 Jan 1999 21:55:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picalon.gun.de (picalon.gun.de [194.77.0.18] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA22110 for ; Sun, 17 Jan 1999 21:54:56 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.8.6/8.8.6) with ESMTP id GAA15804 for ; Mon, 18 Jan 1999 06:54:49 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.2/8.9.2) id GAA22681 for current@FreeBSD.ORG; Mon, 18 Jan 1999 06:38:28 +0100 (CET) (envelope-from andreas) Date: Mon, 18 Jan 1999 06:38:27 +0100 From: Andreas Klemm To: current@FreeBSD.ORG Subject: make release fails to build floppies.... (no space left) Message-ID: <19990118063827.A15841@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG mv /R/stage/kernels/BOOTMFS /R/stage/image.boot/kernel Getting symbols from /R/stage/image.boot/kernel for mfsroot Writing MFS image into kernel for boot floppy /R/stage/image.boot/kernel: 54.7% -- replaced with /R/stage/image.boot/kern el.gz disklabel: ioctl DIOCWLABEL: Operation not supported by device Warning: Block size restricts cylinders per group to 4. Warning: 2880 sector(s) in last cylinder unallocated /dev/rvn0c: 2880 sectors in 1 cylinders of 1 tracks, 5760 sectors 1.4MB in 1 cyl groups (4 c/g, 11.25MB/g, 32 i/g) super-block backups (for fsck -b #) at: 32, cpio: write error: No space left on device *** Error code 1 Stop. *** Error code 1 (ignored) *** Error code 1 Stop. *** Error code 1 -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 22:19:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA24516 for freebsd-current-outgoing; Sun, 17 Jan 1999 22:19:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kir.ics.es.osaka-u.ac.jp (kir.ics.es.osaka-u.ac.jp [133.1.12.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA24509 for ; Sun, 17 Jan 1999 22:19:44 -0800 (PST) (envelope-from matusita@jp.FreeBSD.ORG) Received: from localhost (localhost [127.0.0.1]) by kir.ics.es.osaka-u.ac.jp (8.8.8/3.6W/ICS-2.2.2v7-44BSD) with ESMTP id PAA03312 for ; Mon, 18 Jan 1999 15:19:35 +0900 (JST) In-Reply-To: <19990118153804.D55525@freebie.lemis.com> References: <19990118153804.D55525@freebie.lemis.com> X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V User-Agent: Mew/1.94b2 XEmacs/21.2 (Artemis) X-SKK-Version: 10.47.6.2 X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) X-Fingerprint: 0C AC 93 FC E3 9D 9E 5B 3D B8 AC 5C 4A 79 D8 A6 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 981124(IM104) Lines: 28 From: Makoto MATSUSHITA To: current@FreeBSD.ORG Subject: Re: vinum is always started at boot-time... Date: Mon, 18 Jan 1999 15:19:34 +0900 Message-Id: <19990118151934P.matusita@jp.FreeBSD.ORG> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG grog> I'll think out another way and test more thoroughly. How does this grog> look? gnb@itga.com.au already pointed out that "vinum read" command in such an early stage of /etc/rc causes much much warnings about /dev/ is read-only filesystem. And, a typo around reading from /etc/vinumslices (I don't want to type every time :-). Anyway, I do try with this: if [ -f /etc/vinumslices ]; then read vinum_slices < /etc/vinumslices if [ -r /modules/vinum.ko ]; then # jkh paranoia kldload vinum vinum read $vinum_slices >/dev/null 2>&1 else echo "Can't find /modules/vinum.ko" fi fi It works fine, however, sorry I have only ONE volume so how it goes if two or more volumes are defined (note that 'vinum read' takes only one argument). If more 'vinum read' commands should be done, the commands should be within for-loop. -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 22:21:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA24897 for freebsd-current-outgoing; Sun, 17 Jan 1999 22:21:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from h24-64-221-247.gv.wave.shaw.ca (h24-64-221-247.gv.wave.shaw.ca [24.64.221.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA24886 for ; Sun, 17 Jan 1999 22:21:17 -0800 (PST) (envelope-from jake@h24-64-221-247.gv.wave.shaw.ca) Received: from h24-64-221-247.gv.wave.shaw.ca (localhost [127.0.0.1]) by h24-64-221-247.gv.wave.shaw.ca (8.9.2/8.9.2) with ESMTP id WAA01907; Sun, 17 Jan 1999 22:17:21 -0800 (PST) (envelope-from jake@h24-64-221-247.gv.wave.shaw.ca) Message-Id: <199901180617.WAA01907@h24-64-221-247.gv.wave.shaw.ca> X-Mailer: exmh version 2.0.2 2/24/98 To: Greg Lehey Cc: current@FreeBSD.ORG Subject: Re: vinum is always started at boot-time... In-reply-to: Your message of "Mon, 18 Jan 1999 15:38:05 +1030." <19990118153804.D55525@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 17 Jan 1999 22:17:21 -0800 From: Jake Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Oops. This was a thoroughly successful commit, wasn't it? At least > it didn't break `make world'. :) > > I'll think out another way and test more thoroughly. How does this > look? > > if [ -f /etc/vinumslices ]; then > read /etc/vinumslices > if [ -r /modules/vinum.ko ]; then # jkh paranoia > kldload vinum > vinum read $vinum_slices > else > echo "Can't find /modules/vinum.ko" > fi > fi > Why not just suck in rc.conf before starting vinum? I've modified my /etc/rc to do this, and it works fine. I submitted a PR with a patch. also, I tried 'pseudo-device vinum' and it does work, but I think I ran into trouble somewhere. Oh yeah, it worked once, but each subsequent reboot seemed to replicate my subdisks, until I had about 16, only two of which were real. Finally I found my config file, recreated and switched back to the kld. FWIW I think its good to load the module from /etc/rc rather than loader.rc, keeps all the vinum stuff in one place. Maybe we could even have the module loaded on demand; ie if you try to run vinum before the module is loaded, load it automatically. Cheers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 22:28:16 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA25429 for freebsd-current-outgoing; Sun, 17 Jan 1999 22:28:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bouvreuil.cybercable.fr (bouvreuil.cybercable.fr [212.198.3.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA25423 for ; Sun, 17 Jan 1999 22:28:13 -0800 (PST) (envelope-from herbelot@cybercable.fr) Received: (qmail 17179 invoked from network); 18 Jan 1999 06:28:07 -0000 Received: from d003.paris-21.cybercable.fr (HELO cybercable.fr) (212.198.21.3) by bouvreuil.cybercable.fr with SMTP; 18 Jan 1999 06:28:07 -0000 Message-ID: <36A2D468.1AB416C4@cybercable.fr> Date: Mon, 18 Jan 1999 07:27:52 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Jon Hamilton CC: John Polstra , current@FreeBSD.ORG Subject: Re: correction for find(1)'s man page References: <199901180430.UAA10098@hub.freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jon Hamilton wrote: > > In message <199901180357.TAA22127@vashon.polstra.com>, John Polstra wrote: > } In article <36A0FC11.8B22D0F5@cybercable.fr>, > } Thierry Herbelot wrote: > } > Hello > } > > } > I was reading the man page for find(1), looking for the precise option > } > to follow symbolic links. > } > > } > This option is -follow, of course, but it is not described in the man > } > page > } > } Huh? The correct options are the first three options described in > } the man page: > > } -H The -H option causes the file information and file type (see > } stat(2)) returned for each symbolic link specified on the command > } line to be those of the file referenced by the link, not the link > } itself. If the referenced file does not exist, the file informa- > } tion and type will be for the link itself. File information of > } all symbolic links not on the command line is that of the link > } itself. > > What this doesn't explicitly say is that it causes find(1) to actually > follow the symlink and recursively descend the target tree (if the link > points to a directory); I assume that's the behavior the original poster > wanted. Exactly, but this is not clear in he man page (furthermore, -follow is still a valid option and is not documented). TfH > > Near the bottom of the find(1) manpage (on my -stable system), is this: > > Historically, the -d, -h and -x options were implemented using the pri- > maries ``-depth'', ``-follow'', and ``-xdev''. These primaries always > > ``-h'' there should read ``-H''; -h is an unknown option to find(1). > > -- > Jon Hamilton > hamilton@pobox.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 22:38:59 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA26740 for freebsd-current-outgoing; Sun, 17 Jan 1999 22:38:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.atl.bellsouth.net (mail.atl.bellsouth.net [205.152.0.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA26735 for ; Sun, 17 Jan 1999 22:38:58 -0800 (PST) (envelope-from wghicks@bellsouth.net) Received: from wghicks.bellsouth.net (host-209-214-65-160.atl.bellsouth.net [209.214.65.160]) by mail.atl.bellsouth.net (8.8.8-spamdog/8.8.5) with ESMTP id BAA21055; Mon, 18 Jan 1999 01:38:51 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by wghicks.bellsouth.net (8.9.2/8.9.2) with ESMTP id BAA59195; Mon, 18 Jan 1999 01:55:07 -0500 (EST) (envelope-from wghicks@wghicks.bellsouth.net) To: andreas@klemm.gtn.com Cc: current@FreeBSD.ORG Subject: Re: make release fails to build floppies.... (no space left) In-Reply-To: Your message of "Mon, 18 Jan 1999 06:38:27 +0100" <19990118063827.A15841@titan.klemm.gtn.com> References: <19990118063827.A15841@titan.klemm.gtn.com> X-Mailer: Mew version 1.93 on XEmacs 20.4 (Emerald) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990118015507Q.wghicks@wghicks.bellsouth.net> Date: Mon, 18 Jan 1999 01:55:07 -0500 From: W Gerald Hicks X-Dispatcher: imput version 980905(IM100) Lines: 49 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Andreas Klemm Subject: make release fails to build floppies.... (no space left) Date: Mon, 18 Jan 1999 06:38:27 +0100 > mv /R/stage/kernels/BOOTMFS /R/stage/image.boot/kernel > Getting symbols from /R/stage/image.boot/kernel for mfsroot > Writing MFS image into kernel for boot floppy > /R/stage/image.boot/kernel: 54.7% -- replaced with /R/stage/image.boot/kern > el.gz > disklabel: ioctl DIOCWLABEL: Operation not supported by device > Warning: Block size restricts cylinders per group to 4. > Warning: 2880 sector(s) in last cylinder unallocated > /dev/rvn0c: 2880 sectors in 1 cylinders of 1 tracks, 5760 sectors > 1.4MB in 1 cyl groups (4 c/g, 11.25MB/g, 32 i/g) > super-block backups (for fsck -b #) at: > 32, > cpio: write error: No space left on device > *** Error code 1 > > Stop. > *** Error code 1 (ignored) > *** Error code 1 > > Stop. > *** Error code 1 > > When did you last CVSup? Jordan made that mistake last week but I'm sure he backed it out. Are you using version src/release/Makefile version 1.459? Good Luck, Jerry Hicks wghicks@bellsouth.net > -- > Andreas Klemm http://www.FreeBSD.ORG/~andreas > What gives you 90% more speed, for example, in kernel compilation ? > http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html > "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 22:52:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA28226 for freebsd-current-outgoing; Sun, 17 Jan 1999 22:52:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from iip-lab.ics.es.osaka-u.ac.jp (iip-lab.ics.es.osaka-u.ac.jp [133.1.12.191]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA28219 for ; Sun, 17 Jan 1999 22:52:19 -0800 (PST) (envelope-from matusita@ics.es.osaka-u.ac.jp) Received: from localhost (martini.ics.es.osaka-u.ac.jp [133.1.12.88]) by iip-lab.ics.es.osaka-u.ac.jp (8.8.8/3.6W/ICS-2.2.2v7-44BSD) with ESMTP id PAA04618 for ; Mon, 18 Jan 1999 15:51:26 +0900 (JST) In-Reply-To: <19990118151934P.matusita@jp.FreeBSD.ORG> References: <19990118153804.D55525@freebie.lemis.com> <19990118153804.D55525@freebie.lemis.com> <19990118151934P.matusita@jp.FreeBSD.ORG> X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V User-Agent: Mew/1.94b2 XEmacs/21.2 (Artemis) X-SKK-Version: 10.47.6.2 X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) X-Fingerprint: 0C AC 93 FC E3 9D 9E 5B 3D B8 AC 5C 4A 79 D8 A6 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 981124(IM104) Lines: 13 From: Makoto MATSUSHITA (=?ISO-2022-JP?B?GyRCJF4kRCQ3JD8kXiQzJEgbKEI=?=) To: current@FreeBSD.ORG Subject: Re: vinum is always started at boot-time... Date: Mon, 18 Jan 1999 15:15:09 +0900 Message-Id: <19990118151509G.matusita@ics.es.osaka-u.ac.jp> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG matusita> It works fine, however, sorry I have only ONE volume so how matusita> it goes if two or more volumes are defined (note that 'vinum matusita> read' takes only one argument). And, this code causes *duplicate* vinum information, if we do shutdown to single-user mode and then try to come back to the multi-user world (this causes to rerun /etc/rc, rerun 'vinum read' command, and dup them). Somebody may say that's bad... -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 22:59:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA28849 for freebsd-current-outgoing; Sun, 17 Jan 1999 22:59:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA28843 for ; Sun, 17 Jan 1999 22:58:58 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id RAA26018; Mon, 18 Jan 1999 17:28:53 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.2/8.9.0) id RAA00500; Mon, 18 Jan 1999 17:28:51 +1030 (CST) Date: Mon, 18 Jan 1999 17:28:51 +1030 From: Greg Lehey To: Makoto MATSUSHITA Cc: current@FreeBSD.ORG Subject: Re: vinum is always started at boot-time... Message-ID: <19990118172851.A474@freebie.lemis.com> References: <19990118153804.D55525@freebie.lemis.com> <19990118153804.D55525@freebie.lemis.com> <19990118151934P.matusita@jp.FreeBSD.ORG> <19990118151509G.matusita@ics.es.osaka-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990118151509G.matusita@ics.es.osaka-u.ac.jp>; from Makoto MATSUSHITA on Mon, Jan 18, 1999 at 03:15:09PM +0900 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 18 January 1999 at 15:15:09 +0900, Makoto MATSUSHITA wrote: > > matusita> It works fine, however, sorry I have only ONE volume so how > matusita> it goes if two or more volumes are defined (note that 'vinum > matusita> read' takes only one argument). > > And, this code causes *duplicate* vinum information, if we do shutdown > to single-user mode and then try to come back to the multi-user world > (this causes to rerun /etc/rc, rerun 'vinum read' command, and dup them). There is a bug in the current version of Vinum which would allow this, but it's been fixed in the new megacommit I'm preparing. For example: Jan 18 15:36:36 panic /kernel: vinum: reading configuration from /dev/sd4h Jan 18 15:36:37 panic /kernel: vinum: updating configuration from /dev/sd3h Jan 18 15:36:38 panic /kernel: vinum: updating configuration from /dev/sd2h Jan 18 15:36:39 panic /kernel: vinum: updating configuration from /dev/sd1h Jan 18 15:38:35 panic /kernel: vinum: already read config from drive1 Jan 18 15:38:35 panic /kernel: vinum: already read config from drive2 Jan 18 15:38:35 panic /kernel: vinum: already read config from drive3 Jan 18 15:38:35 panic /kernel: vinum: already read config from drive4 Don't worry about the panic; that's the name of the system :-) You'll also notice that the order of reading is not the order in which the names are specified; Vinum starts with the newest config and works back. > Somebody may say that's bad... If you've tripped over the bug, `bad' is an understatement. It can completely tear your config apart. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 23:01:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA29154 for freebsd-current-outgoing; Sun, 17 Jan 1999 23:01:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA29139 for ; Sun, 17 Jan 1999 23:00:55 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id RAA26038; Mon, 18 Jan 1999 17:30:49 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.2/8.9.0) id RAA00524; Mon, 18 Jan 1999 17:30:48 +1030 (CST) Date: Mon, 18 Jan 1999 17:30:48 +1030 From: Greg Lehey To: Jake Cc: current@FreeBSD.ORG Subject: Re: vinum is always started at boot-time... Message-ID: <19990118173048.B474@freebie.lemis.com> References: <19990118153804.D55525@freebie.lemis.com> <199901180617.WAA01907@h24-64-221-247.gv.wave.shaw.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199901180617.WAA01907@h24-64-221-247.gv.wave.shaw.ca>; from Jake on Sun, Jan 17, 1999 at 10:17:21PM -0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 17 January 1999 at 22:17:21 -0800, Jake wrote: >> Oops. This was a thoroughly successful commit, wasn't it? At least >> it didn't break `make world'. > > :) > >> >> I'll think out another way and test more thoroughly. How does this >> look? >> >> if [ -f /etc/vinumslices ]; then >> read /etc/vinumslices >> if [ -r /modules/vinum.ko ]; then # jkh paranoia >> kldload vinum >> vinum read $vinum_slices >> else >> echo "Can't find /modules/vinum.ko" >> fi >> fi >> > > Why not just suck in rc.conf before starting vinum? Good idea. Does anybody have a reason for reading in rc.conf so late? > I've modified my /etc/rc to do this, and it works fine. > I submitted a PR with a patch. I'll look at it. > also, I tried 'pseudo-device vinum' and it does work, > but I think I ran into trouble somewhere. > Oh yeah, it worked once, but each subsequent > reboot seemed to replicate my subdisks, > until I had about 16, only two of which were real. > Finally I found my config file, recreated and switched > back to the kld. I don't think this is the fault of the pseudo-device. This is more likely to be the bug I mentioned in my mail to Matsushita-san. > FWIW I think its good to load the module from /etc/rc > rather than loader.rc, keeps all the vinum stuff in one > place. Maybe we could even have the module loaded > on demand; ie if you try to run vinum before the module > is loaded, load it automatically. Once I have this update out of my hair, I'll think about this. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 23:06:41 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA29735 for freebsd-current-outgoing; Sun, 17 Jan 1999 23:06:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA29728 for ; Sun, 17 Jan 1999 23:06:38 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id RAA26056 for ; Mon, 18 Jan 1999 17:36:32 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.2/8.9.0) id RAA00637 for FreeBSD-current@FreeBSD.ORG; Mon, 18 Jan 1999 17:36:31 +1030 (CST) Date: Mon, 18 Jan 1999 17:36:31 +1030 From: Greg Lehey To: FreeBSD current users Subject: dmesg: kernel message buffer has different magic number Message-ID: <19990118173631.D474@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just upgraded to an all-ELF system. The results are less than marvellous. For some reason, one of my IDE disks no longer runs in DMA mode (I'll put in a PR about that in a minute), and I've just had a panic. The trouble is, I can't analyse it. It happened while I was in X, so I didn't see anything of use, and when I try to look at it with gdb, I get: IdlePTD 2949120 initial pcb at 263858 panic messages: --- dmesg: kernel message buffer has different magic number --- #0 0xf014ed7b in boot () (kgdb) Does this mean I've corrupted something good? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 23:10:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA00379 for freebsd-current-outgoing; Sun, 17 Jan 1999 23:10:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA00372 for ; Sun, 17 Jan 1999 23:10:07 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id RAA26080; Mon, 18 Jan 1999 17:40:01 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.2/8.9.0) id RAA00657; Mon, 18 Jan 1999 17:40:00 +1030 (CST) Date: Mon, 18 Jan 1999 17:40:00 +1030 From: Greg Lehey To: Makoto MATSUSHITA Cc: current@FreeBSD.ORG Subject: Re: vinum is always started at boot-time... Message-ID: <19990118174000.E474@freebie.lemis.com> References: <19990118153804.D55525@freebie.lemis.com> <19990118151934P.matusita@jp.FreeBSD.ORG> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990118151934P.matusita@jp.FreeBSD.ORG>; from Makoto MATSUSHITA on Mon, Jan 18, 1999 at 03:19:34PM +0900 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 18 January 1999 at 15:19:34 +0900, Makoto MATSUSHITA wrote: > > grog> I'll think out another way and test more thoroughly. How does this > grog> look? > > gnb@itga.com.au already pointed out that "vinum read" command in such > an early stage of /etc/rc causes much much warnings about /dev/ is > read-only filesystem. We can get rid of the warnings. And they'll go away by themselves when we have devfs. > And, a typo around reading from /etc/vinumslices > (I don't want to type every time :-). > > Anyway, I do try with this: > > if [ -f /etc/vinumslices ]; then > read vinum_slices < /etc/vinumslices > if [ -r /modules/vinum.ko ]; then # jkh paranoia > kldload vinum > vinum read $vinum_slices >/dev/null 2>&1 > else > echo "Can't find /modules/vinum.ko" > fi > fi > > It works fine, however, sorry I have only ONE volume so how it goes if > two or more volumes are defined (note that 'vinum read' takes only one > argument). The syntax for `vinum read' is changing. It now *must* specify all drives (not volumes). You can lie and specify others, too, if you want: it will silently ignore any drives which don't contain Vinum data. We need to do it like this in order to read in the config in the correct order after a crash. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 23:39:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA03925 for freebsd-current-outgoing; Sun, 17 Jan 1999 23:39:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA03914 for ; Sun, 17 Jan 1999 23:39:02 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id XAA35098; Sun, 17 Jan 1999 23:39:02 -0800 (PST) To: Christian Kuhtz cc: freebsd-current@FreeBSD.ORG Subject: Re: how to snapshoot :) In-reply-to: Your message of "Sun, 17 Jan 1999 19:31:05 EST." <19990117193105.G97318@oreo.adsu.bellsouth.com> Date: Sun, 17 Jan 1999 23:39:01 -0800 Message-ID: <35095.916645141@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Can somebody throw me a pointer or lifeline so that I can build my own > snapshots? This would greatly simply my task of keeping machines up to date Read /usr/src/release/Makefile and understand it thoroughly. That's all you have to do. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 17 23:46:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA05177 for freebsd-current-outgoing; Sun, 17 Jan 1999 23:46:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA05172 for ; Sun, 17 Jan 1999 23:46:29 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id XAA35189; Sun, 17 Jan 1999 23:46:30 -0800 (PST) To: Ollivier Robert cc: "FreeBSD Current Users' list" Subject: Re: vinum is always started at boot-time... In-reply-to: Your message of "Mon, 18 Jan 1999 02:15:22 +0100." <19990118021522.A443@keltia.freenix.fr> Date: Sun, 17 Jan 1999 23:46:29 -0800 Message-ID: <35186.916645589@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg left out the quotes from my example. :) > ...regardless of the "vinum_slices" setting. It is not a nice thing > considering the size of the vinum kld (a6000 bytes). > > "if [ -n $vinum_slices ]" doesn't seem to work. > -- > Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.f r > FreeBSD keltia.freenix.fr 3.0-CURRENT #67: Tue Dec 29 20:24:02 CET 1998 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 00:02:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA06131 for freebsd-current-outgoing; Mon, 18 Jan 1999 00:02:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA06126; Mon, 18 Jan 1999 00:02:24 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id AAA58279; Mon, 18 Jan 1999 00:00:54 -0800 (PST) (envelope-from dillon) Date: Mon, 18 Jan 1999 00:00:54 -0800 (PST) From: Matthew Dillon Message-Id: <199901180800.AAA58279@apollo.backplane.com> To: Chris Timmons Cc: freebsd-current@FreeBSD.ORG, John Polstra , luoqi@FreeBSD.ORG Subject: Re: NFS: likely problem is vfs_bio.c rev 1.188 References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On the server I downgraded vfs_bio.c to rev 1.187 & rebooted; no luck. I :then installed the same kernel (with the downgraded vfs_bio.c) to the :client. Bingo. With both NFS client & server machine running rev 1.187, :the problem so far as building XFree86-contrib from an NFS mounted :/usr/ports disappears. : :As Chuck Robey noted, it seems like the client's writes are not completely :being committed to the server, which results in partially baked files :which are truncated. : :Unfortunately -r1.188 -r1.187 doesn't apply cleanly, so there's some work :to be done by Eivind to adapt his subsequent commits if we were to say, :back out 1.188 prior to the branch. : :-Chris Hmm. r1.88 are Luoqi's fixes to the handling of misaligned buffers. It is quite possible that there is a bug in there or with assumptions made in the NFS code in regards to how buffers are handled, but most of those changes are theoretically critical to the proper operation of the VFS code on other platforms (aka alpha, with its larger page size), and pretty important to the msdos code too under certain circumstances. And it was reviewed pretty well, too. I'd rather we not lose the work. I think it is important that we find the bug and fix it without having to back-out that entire patch! I was hoping to avoid updating my codebase until after the split, but I'll go ahead and try to sync it up tonight and see if I can reproduce the NFS problem. If I can do that, I should be able to locate the bug and fix it. So, nobody backout 1.188 yet, please. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 00:14:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA07658 for freebsd-current-outgoing; Mon, 18 Jan 1999 00:14:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cassiopeia.hkstar.com (cassiopeia.hkstar.com [202.82.3.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA07640 for ; Mon, 18 Jan 1999 00:14:21 -0800 (PST) (envelope-from c5666305@b1.hkstar.com) Received: from b1.hkstar.com (b1.hkstar.com [202.82.0.87]) by cassiopeia.hkstar.com (8.9.1/8.9.1) with ESMTP id QAA26645 for ; Mon, 18 Jan 1999 16:14:15 +0800 (HKT) Received: (from c5666305@localhost) by b1.hkstar.com (8.8.8/8.8.8) id QAA16685 for freebsd-current@freebsd.org; Mon, 18 Jan 1999 16:14:18 +0800 (HKT) From: Chan Yiu Wah Message-Id: <199901180814.QAA16685@b1.hkstar.com> Subject: make world error upto src-cur.3710 To: freebsd-current@FreeBSD.ORG Date: Mon, 18 Jan 1999 16:14:18 +0800 (HKT) X-Mailer: ELM [version 2.5 PL0b1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I tried to make world (src-cur.3710) todya and found the following error. Can anyone tell me how to solve it. thanks. Clarence ======= Error ======= In file included from /usr/obj/usr/src/gnu/usr.bin/perl/perl/perl.h:2081, from DynaLoader.xs:107: /usr/obj/usr/src/gnu/usr.bin/perl/perl/thrdvar.h:73: parse error before `PL_ofslen' /usr/obj/usr/src/gnu/usr.bin/perl/perl/thrdvar.h:73: warning: data definition has no type or storage class In file included from DynaLoader.xs:130: dlutils.c:10: `NULL' undeclared here (not in a function) dlutils.c: In function `dl_generic_private_init': dlutils.c:35: `NULL' undeclared (first use this function) dlutils.c:35: (Each undeclared identifier is reported only once dlutils.c:35: for each function it appears in.) dlutils.c: In function `SaveError': dlutils.c:50: `va_list' undeclared (first use this function) dlutils.c:50: parse error before `args' dlutils.c:56: `args' undeclared (first use this function) DynaLoader.c: In function `XS_DynaLoader_dl_load_file': DynaLoader.c:155: dereferencing pointer to incomplete type DynaLoader.c:155: dereferencing pointer to incomplete type DynaLoader.c:165: dereferencing pointer to incomplete type DynaLoader.xs:163: warning: assignment makes pointer from integer without a cast DynaLoader.xs:166: `NULL' undeclared (first use this function) DynaLoader.c: In function `XS_DynaLoader_dl_find_symbol': DynaLoader.c:197: dereferencing pointer to incomplete type DynaLoader.c:198: dereferencing pointer to incomplete type DynaLoader.c:198: dereferencing pointer to incomplete type DynaLoader.xs:183: warning: assignment makes pointer from integer without a cast DynaLoader.xs:187: `NULL' undeclared (first use this function) DynaLoader.c: In function `XS_DynaLoader_dl_install_xsub': DynaLoader.c:240: dereferencing pointer to incomplete type DynaLoader.c:240: dereferencing pointer to incomplete type DynaLoader.c:241: dereferencing pointer to incomplete type DynaLoader.c:247: dereferencing pointer to incomplete type DynaLoader.c:247: dereferencing pointer to incomplete type DynaLoader.c: In function `boot_DynaLoader': DynaLoader.c:282: `NULL' undeclared (first use this function) DynaLoader.c:282: dereferencing pointer to incomplete type DynaLoader.c:282: dereferencing pointer to incomplete type DynaLoader.c:282: dereferencing pointer to incomplete type DynaLoader.c:282: dereferencing pointer to incomplete type *** Error code 1 Stop. ======= Error ======= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 00:22:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA08661 for freebsd-current-outgoing; Mon, 18 Jan 1999 00:22:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cassiopeia.hkstar.com (cassiopeia.hkstar.com [202.82.3.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA08655 for ; Mon, 18 Jan 1999 00:22:47 -0800 (PST) (envelope-from c5666305@b1.hkstar.com) Received: from b1.hkstar.com (b1.hkstar.com [202.82.0.87]) by cassiopeia.hkstar.com (8.9.1/8.9.1) with ESMTP id QAA27459 for ; Mon, 18 Jan 1999 16:22:42 +0800 (HKT) Received: (from c5666305@localhost) by b1.hkstar.com (8.8.8/8.8.8) id QAA17026 for freebsd-current@freebsd.org; Mon, 18 Jan 1999 16:22:46 +0800 (HKT) From: Chan Yiu Wah Message-Id: <199901180822.QAA17026@b1.hkstar.com> Subject: how to update the system from the master machine To: freebsd-current@FreeBSD.ORG Date: Mon, 18 Jan 1999 16:22:45 +0800 (HKT) X-Mailer: ELM [version 2.5 PL0b1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I have two system. One is P233 (master) and the other is a dual P90. How can I update the dual P90 system from the P233 (master) system. Is there anyone can share your experience with me. Thanks. clarence To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 00:36:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA10388 for freebsd-current-outgoing; Mon, 18 Jan 1999 00:36:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from scotty.masternet.it (scotty.masternet.it [194.184.65.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA10380 for ; Mon, 18 Jan 1999 00:36:39 -0800 (PST) (envelope-from gmarco@scotty.masternet.it) Received: from suzy (modem38.masternet.it [194.184.65.48]) by scotty.masternet.it (8.8.8/8.8.8) with SMTP id JAA29808; Mon, 18 Jan 1999 09:36:05 +0100 (CET) (envelope-from gmarco@scotty.masternet.it) Message-Id: <4.1.19990118093203.009e7c60@194.184.65.4> X-Sender: gmarco@scotty.masternet.it X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 18 Jan 1999 09:44:14 +0100 To: Chan Yiu Wah From: Gianmarco Giovannelli Subject: Re: how to update the system from the master machine Cc: current@FreeBSD.ORG In-Reply-To: <199901180822.QAA17026@b1.hkstar.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 16.22 18/01/99 +0800, you wrote: >Hello, > >I have two system. One is P233 (master) and the other is a dual P90. >How can I update the dual P90 system from the P233 (master) system. >Is there anyone can share your experience with me. Thanks. > >clarence I usually have a box ("server") which make the make world process, the others ("clients") only install what the server did :-) Let's say in advance that I do it _only_ if server and clients run the same version of FreeBSD. If yes : (server) cd /sys/i386/conf (server) cp GENERIC CLIENT_NAME (server) edit CLIENT_NAME to suit your needs (server) config -r CLIENT_NAME (if 3.0) else config CLIENT_NAME (server) cd ../../compile/CLIENT_NAME (server) make all When it is finished : (client) mount /usr/src and /usr/obj of the server in /usr/src and /usr/obj (client) cd /sys/compile/CLIENT_NAME (client) make install (client) cd /usr/src (client) make installworld (or make reinstall if both are release prior 3.0) (client) compare /etc/* with /usr/src/etc/* to see if it is changed something in the scripts (client) restart Please check that both systems have the same /etc/make.conf or at least compatible each other. Also it could not work if the clients are too much older from the server. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 00:39:59 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA10815 for freebsd-current-outgoing; Mon, 18 Jan 1999 00:39:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from andrsn.stanford.edu (andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA10810 for ; Mon, 18 Jan 1999 00:39:58 -0800 (PST) (envelope-from andrsn@andrsn.stanford.edu) Received: from localhost (andrsn@localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.9.1/8.9.1) with SMTP id AAA21820 for ; Mon, 18 Jan 1999 00:38:12 -0800 (PST) Date: Mon, 18 Jan 1999 00:38:11 -0800 (PST) From: Annelise Anderson To: freebsd-current@FreeBSD.ORG Subject: Build Errors in -current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With sources as of about 10 p.m. PST, I got an error in /usr/src/usr.bin/netstat/mbuf.c:71, which was easy to fix. But I still got an error much later with texinfo, so apparently this is only partly fixed. Annelise To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 00:46:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA11702 for freebsd-current-outgoing; Mon, 18 Jan 1999 00:46:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from scotty.masternet.it (scotty.masternet.it [194.184.65.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA11696 for ; Mon, 18 Jan 1999 00:46:42 -0800 (PST) (envelope-from gmarco@scotty.masternet.it) Received: from suzy (modem38.masternet.it [194.184.65.48]) by scotty.masternet.it (8.8.8/8.8.8) with SMTP id JAA29923; Mon, 18 Jan 1999 09:46:10 +0100 (CET) (envelope-from gmarco@scotty.masternet.it) Message-Id: <4.1.19990118095228.009e7310@194.184.65.4> X-Sender: gmarco@scotty.masternet.it X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 18 Jan 1999 09:54:18 +0100 To: Chan Yiu Wah From: Gianmarco Giovannelli Subject: Re: how to update the system from the master machine Cc: current@FreeBSD.ORG In-Reply-To: <4.1.19990118093203.009e7c60@194.184.65.4> References: <199901180822.QAA17026@b1.hkstar.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 09.44 18/01/99 +0100, Gianmarco Giovannelli wrote: >At 16.22 18/01/99 +0800, you wrote: >I usually have a box ("server") which make the make world process, the >others ("clients") only install what the server did :-) > >Let's say in advance that I do it _only_ if server and clients run the same >version of FreeBSD. >If yes : Ehm, obviusly you need a built /usr/obj tree so you need also to do : (server) cd /usr/src (server) make world >(server) cd /sys/i386/conf >(server) cp GENERIC CLIENT_NAME >(server) edit CLIENT_NAME to suit your needs >(server) config -r CLIENT_NAME (if 3.0) else config CLIENT_NAME >(server) cd ../../compile/CLIENT_NAME >(server) make all > >When it is finished : > >(client) mount /usr/src and /usr/obj of the server in /usr/src and /usr/obj >(client) cd /sys/compile/CLIENT_NAME >(client) make install >(client) cd /usr/src >(client) make installworld (or make reinstall if both are release prior 3.0) >(client) compare /etc/* with /usr/src/etc/* to see if it is changed >something in the scripts >(client) restart To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 01:13:34 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA14165 for freebsd-current-outgoing; Mon, 18 Jan 1999 01:13:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA14160 for ; Mon, 18 Jan 1999 01:13:32 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.2/8.9.2) with ESMTP id JAA55045; Mon, 18 Jan 1999 09:13:19 GMT Message-ID: <36A2FAEF.AD700F6@tdx.co.uk> Date: Mon, 18 Jan 1999 09:12:15 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Andrew Atrens CC: current@FreeBSD.ORG Subject: Re: Problems with new IDE's & -current References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew Atrens wrote: > > On Sun, 17 Jan 1999, Karl Pielorz wrote: > > Karl, > > Let's see your (dmesg) probe messages ... :) they may shed some light on > what's happening. I don't claim to be an expert on wd.c but from what I > can tell it seems that controller and drive capabilities are probed > separately, its conceivable you've hit upon an untested code path. > > ide_pci.c has been changing a lot lately (probably four times in the last > seven days) - after capturing your dmesg output, try a fresh kernel and > look for differences in probed controller/drive capabilities... > > Andrew. OK, I didn't want to post the dmesg as it's quite long, and I couldn't see anything relevant in it - but here goes... :) The machines running fairly recent -current from ~7th Jan... I've been trying to update recently but run into the same problems everyone else has... I'm hoping to get another build done today/tomorrow... re: Probed controller/drive capabilities - from the look of it (and assuming the Neptune is as old as it is) - it seems to be finding no g'o faster stripes', multiblock, DMA or anything (which is what I'd expect) - so I don't think it's getting the 'wrong mode' for the drives... -Kp --- Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-RELEASE #1: Thu Jan 14 12:49:14 GMT 1999 root@magpie.dmpriest.com:/usr/src/sys/compile/SMP-MAGPIE Timecounter "i8254" frequency 1193182 Hz cost 4354 ns CPU: Pentium/P54C (586-class CPU) Origin = "GenuineIntel" Id = 0x521 Stepping=1 Features=0x7bf real memory = 16777216 (16384K bytes) avail memory = 14397440 (14060K bytes) Programming 16 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00030010, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00030010, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x000f0011, at 0xfec00000 eisa0: Probing for devices on the EISA bus Probing for devices on PCI bus 0: chip0: rev 0x11 on pci0.0.0 ncr0: rev 0x01 int a irq 15 on pci0.1.0 chip1: rev 0x04 on pci0.2.0 vga0: rev 0x00 int a irq 10 on pci0.4.0 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x278-0x27f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 16124MB (33022080 sectors), 32760 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): wd1: 16124MB (33022080 sectors), 32760 cyls, 16 heads, 63 S/T, 512 B/S lnc0 at 0x340-0x357 irq 9 drq 7 on isa lnc0: PCnet-ISA address 00:40:1c:60:36:ab npx0 on motherboard npx0: INT 16 interface Intel Pentium F00F detected, installing workaround APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 ccd0-1: Concatenated disk drivers SMP: AP CPU #1 Launched! changing root device to da0s1a da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: 10.0MB/s transfers (10.0MHz, offset 8), Tagged Queueing Enabled da0: 2049MB (4197405 512 byte sectors: 255H 63S/T 261C) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 01:49:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA18073 for freebsd-current-outgoing; Mon, 18 Jan 1999 01:49:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA18049 for ; Mon, 18 Jan 1999 01:49:01 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.10 #1) id 102BIi-0000em-00 for current@freebsd.org; Mon, 18 Jan 1999 11:48:52 +0200 From: Sheldon Hearn To: current@FreeBSD.ORG Subject: netstat prints shifted if_obytes values? Date: Mon, 18 Jan 1999 11:48:52 +0200 Message-ID: <2527.916652932@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, Is the following behaviour from netstat expected under CURRENT? input (xl0) output packets errs bytes packets errs bytes colls 2 0 390 0 0 0 0 4 0 264 0 0 90 0 3 0 1469 1 0 0 0 18 0 1581 0 0 0 0 21 0 15621 0 0 90 0 6 0 312 1 0 0 0 4 0 760 0 0 90 0 9 0 785 1 0 0 0 36 0 8085 0 0 0 0 7 0 1084 0 0 0 0 21 0 13615 0 0 0 0 7 0 616 0 0 0 0 4 0 249 0 0 0 0 1 0 440 0 0 0 0 5 0 312 0 0 0 0 5 0 528 0 0 0 0 18 0 13971 1 0 82 0 4 0 678 0 0 0 0 7 0 390 0 0 0 0 3 0 364 0 0 0 0 7 0 400 0 0 0 0 Specifically, I'm interested in the fact that it _looks_ like if_obytes is sometimes being printed for each ``loop''. At the time, the only expected network traffic was generated by NFSv3. I have no idea whether this might be significant. Thanks, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 01:54:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA18645 for freebsd-current-outgoing; Mon, 18 Jan 1999 01:54:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from localhost (gserver.com [209.180.80.210]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA18639 for ; Mon, 18 Jan 1999 01:54:04 -0800 (PST) (envelope-from surfchina@gserver.com) Received: (surfchina@localhost) by gserver.com (8.8.8) id CAA26660; Mon, 18 Jan 1999 02:58:49 -0700 (MST) Date: Mon, 18 Jan 1999 02:58:49 -0700 (MST) From: surfchina@gserver.com (Surf China) Message-Id: <199901180958.CAA26660@gserver.com> To: current@FreeBSD.ORG Subject: SurfChina.com - Search Engine for China Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear friend, Do you ever wonder where to find information about China? Well, wonder no more. Come check out SurfChina.com (http://www.surfchina.com), the BEST SEARCH ENGINE for China. SurfChina.com's database consists of thousands of China, Chinese related web sites, all sites are carefully categorized into over 300 categories, which makes search very easy. New sites and categories are added everyday. You can find Chinese companies, Chinese culture sites, travel agencies, employment opportunities, Chinese newspapers, and much, much more. Take a look for yourself, and tell a friend about SurfChina.com, so everyone can take advantage of this wonderful resource. SurfChina.com also provides China statistical information service. We work directly with the State Statistical Bureau of China to provide the latest, the most accurate, and most authritative China statistical data for our clients. To find out more about this service, please visit http://www.surfchina.com/stats/ Sincerely yours, SurfChina.com team To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 02:05:39 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA20327 for freebsd-current-outgoing; Mon, 18 Jan 1999 02:05:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rossel.saarnet.de (rossel.saarnet.de [145.253.240.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA20299 for ; Mon, 18 Jan 1999 02:05:20 -0800 (PST) (envelope-from doehrm@aubi.de) Received: from igate.aubi.de (root@igate.aubi.de [145.253.242.249]) by rossel.saarnet.de (8.8.8/8.8.8) with ESMTP id LAA10319; Mon, 18 Jan 1999 11:08:03 +0100 (MET) Received: from cisco.aubi.de (cisco.aubi.de [170.56.121.252]) by igate.aubi.de (8.9.1a/8.9.1) with ESMTP id MAA17098; Mon, 18 Jan 1999 12:01:36 +0100 Received: from exchange.aubi.de (EXCHANGE.aubi.de [170.56.121.91]) by cisco.aubi.de (8.9.1/8.9.1) with ESMTP id LAA08910; Mon, 18 Jan 1999 11:12:31 +0100 (CET) Received: by EXCHANGE.aubi.de with Internet Mail Service (5.5.2232.9) id ; Mon, 18 Jan 1999 10:57:18 +0100 Message-ID: From: =?iso-8859-1?Q?Markus_D=F6hr?= To: "'surfchina@gserver.com'" Cc: current@FreeBSD.ORG Subject: RE: SurfChina.com - Search Engine for China Date: Mon, 18 Jan 1999 10:56:18 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id CAA20306 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [snip] > Dear friend, > > Do you ever wonder where to find information about China? > Well, wonder no > more. Come check out SurfChina.com [snap] just wondering if anyone else receives this post about 10 times...? -- Markus Doehr IT Admin AUBI Baubeschläge GmbH Tel.: +49 6503 917 152 Fax : +49 6503 917 119 e-Mail: doehrm@aubi.de MD1139-RIPE ************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 04:42:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA06518 for freebsd-current-outgoing; Mon, 18 Jan 1999 04:42:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from octopus.originative.co.uk (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA06506 for ; Mon, 18 Jan 1999 04:42:01 -0800 (PST) (envelope-from paul@originative.co.uk) From: paul@originative.co.uk Received: by OCTOPUS with Internet Mail Service (5.5.1960.3) id ; Mon, 18 Jan 1999 12:40:29 -0000 Message-ID: To: current@FreeBSD.ORG Subject: The removal of MT_RTABLE Date: Mon, 18 Jan 1999 12:40:26 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The removal of MT_RTABLE by fenner in rev 1.32 of /sys/sys/mbuf.h has broken the build of the tree in netstat. It may have broken other net apps that I haven't hit yet. There's also a new coding style that I've not come across before being used in this file, it's based on commenting out lines by clobbering the first two chars, e.g. /*efine MT_RTABLE 5*/ /* routing tables */ It looks like it was invented by Garret and fenner followed his good example :-) Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 05:38:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA10828 for freebsd-current-outgoing; Mon, 18 Jan 1999 05:38:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA10781; Mon, 18 Jan 1999 05:38:10 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id FAA72182; Mon, 18 Jan 1999 05:36:36 -0800 (PST) (envelope-from dillon) Date: Mon, 18 Jan 1999 05:36:36 -0800 (PST) From: Matthew Dillon Message-Id: <199901181336.FAA72182@apollo.backplane.com> To: Chris Timmons Cc: freebsd-current@FreeBSD.ORG, John Polstra , luoqi@FreeBSD.ORG Subject: NFS problem found - pleaes try this patch. References: <199901180800.AAA58279@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ::On the server I downgraded vfs_bio.c to rev 1.187 & rebooted; no luck. I ::then installed the same kernel (with the downgraded vfs_bio.c) to the ::client. Bingo. With both NFS client & server machine running rev 1.187, ::... ::-Chris : : Hmm. r1.88 are Luoqi's fixes to the handling of misaligned buffers. It is : quite possible that there is a bug in there or with assumptions made in : the NFS code in regards to how buffers are handled, but most of those :... : -Matt Ok, I believe I have found the bug. Please test the patch included below. I was able to make /usr/ports/x11/XFree86-contrib after applying this patch ( and it was screwing up prior to that ). The problem is in getblk() - code was added to validate the buffer and to clear B_CACHE if the bp was not entirely valid. The problem is that NFS uses B_CACHE to flag a dirty buffer that needs to be written out! Additionally, a write() to an NFS based file may write data that is not on a DEV_BSIZE'd boundry which causes a subsequent read() to improperly clear B_CACHE. There are almost certainly more problems like this -- using B_CACHE to mark a buffer dirty is just plain dumb, it's no wonder NFS is so screwed up! -Matt Matthew Dillon Index: kern/vfs_bio.c =================================================================== RCS file: /home/ncvs/src/sys/kern/vfs_bio.c,v retrieving revision 1.192 diff -u -r1.192 vfs_bio.c --- vfs_bio.c 1999/01/12 11:59:34 1.192 +++ vfs_bio.c 1999/01/18 13:25:27 @@ -1364,6 +1364,7 @@ break; } } + boffset = (i << PAGE_SHIFT) - (bp->b_offset & PAGE_MASK); if (boffset < bp->b_dirtyoff) { bp->b_dirtyoff = max(boffset, 0); @@ -1457,7 +1458,14 @@ } KASSERT(bp->b_offset != NOOFFSET, ("getblk: no buffer offset")); +#if 0 /* + * XXX REMOVED XXX - this is bogus. It will cause the + * B_CACHE flag to be cleared for a partially constituted + * dirty buffer (NFS) that happens to have a write that is + * not on a DEV_BSIZE boundry!!!!!! XXX REMOVED XXXX + */ + /* * Check that the constituted buffer really deserves for the * B_CACHE bit to be set. B_VMIO type buffers might not * contain fully valid pages. Normal (old-style) buffers @@ -1478,6 +1486,7 @@ poffset = 0; } } +#endif if (bp->b_usecount < BUF_MAXUSE) ++bp->b_usecount; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 05:59:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA12947 for freebsd-current-outgoing; Mon, 18 Jan 1999 05:59:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from agnes.stthom.edu ([209.184.165.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA12942 for ; Mon, 18 Jan 1999 05:59:43 -0800 (PST) (envelope-from root@wt.net) Received: from wilber.home.net (216-119-132-178.ipset12.WT.NET [216.119.132.178]) by agnes.stthom.edu (8.7.6/8.7.3) with SMTP id HAA19992 for ; Mon, 18 Jan 1999 07:22:53 -0600 Date: Mon, 18 Jan 1999 20:00:35 +0000 (GMT) From: Charlie ROOT X-Sender: root@wilber.home.net To: current@FreeBSD.ORG Subject: Broken make world Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I got the following when trying a new make world (1-17-99): cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/netstat/if.c cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/netstat/inet.c cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/netstat/main.c cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/netstat/mbuf.c /usr/src/usr.bin/netstat/mbuf.c:71: `MT_RTABLE' undeclared here (not in a function) /usr/src/usr.bin/netstat/mbuf.c:71: initializer element for `mbtypes[4].mt_type' is not constant *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 06:17:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA16461 for freebsd-current-outgoing; Mon, 18 Jan 1999 06:17:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from opus.cts.cwu.edu (opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA16452; Mon, 18 Jan 1999 06:17:45 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.9.1/8.9.1) with SMTP id GAA00217; Mon, 18 Jan 1999 06:17:32 -0800 (PST) Date: Mon, 18 Jan 1999 06:17:32 -0800 (PST) From: Chris Timmons To: Matthew Dillon cc: freebsd-current@FreeBSD.ORG, John Polstra , luoqi@FreeBSD.ORG Subject: Re: NFS problem found - pleaes try this patch. In-Reply-To: <199901181336.FAA72182@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Good work! I have to run at the moment but it looks like you nailed this one. Your explanation coincides perfectly with the symptoms. Thanks! -Chris On Mon, 18 Jan 1999, Matthew Dillon wrote: > Ok, I believe I have found the bug. Please test the patch included below. > I was able to make /usr/ports/x11/XFree86-contrib after applying this > patch ( and it was screwing up prior to that ). > > The problem is in getblk() - code was added to validate the buffer and > to clear B_CACHE if the bp was not entirely valid. The problem is > that NFS uses B_CACHE to flag a dirty buffer that needs to be written out! > Additionally, a write() to an NFS based file may write data that is not > on a DEV_BSIZE'd boundry which causes a subsequent read() to improperly > clear B_CACHE. > > There are almost certainly more problems like this -- using B_CACHE to > mark a buffer dirty is just plain dumb, it's no wonder NFS is so screwed > up! > > -Matt > > Matthew Dillon > > > Index: kern/vfs_bio.c > =================================================================== > RCS file: /home/ncvs/src/sys/kern/vfs_bio.c,v > retrieving revision 1.192 > diff -u -r1.192 vfs_bio.c > --- vfs_bio.c 1999/01/12 11:59:34 1.192 > +++ vfs_bio.c 1999/01/18 13:25:27 > @@ -1364,6 +1364,7 @@ > break; > } > } > + > boffset = (i << PAGE_SHIFT) - (bp->b_offset & PAGE_MASK); > if (boffset < bp->b_dirtyoff) { > bp->b_dirtyoff = max(boffset, 0); > @@ -1457,7 +1458,14 @@ > } > KASSERT(bp->b_offset != NOOFFSET, > ("getblk: no buffer offset")); > +#if 0 > /* > + * XXX REMOVED XXX - this is bogus. It will cause the > + * B_CACHE flag to be cleared for a partially constituted > + * dirty buffer (NFS) that happens to have a write that is > + * not on a DEV_BSIZE boundry!!!!!! XXX REMOVED XXXX > + */ > + /* > * Check that the constituted buffer really deserves for the > * B_CACHE bit to be set. B_VMIO type buffers might not > * contain fully valid pages. Normal (old-style) buffers > @@ -1478,6 +1486,7 @@ > poffset = 0; > } > } > +#endif > > if (bp->b_usecount < BUF_MAXUSE) > ++bp->b_usecount; > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 07:12:02 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA21535 for freebsd-current-outgoing; Mon, 18 Jan 1999 07:12:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA21505; Mon, 18 Jan 1999 07:11:58 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id KAA15315; Mon, 18 Jan 1999 10:05:50 -0500 (EST) (envelope-from luoqi) Date: Mon, 18 Jan 1999 10:05:50 -0500 (EST) From: Luoqi Chen Message-Id: <199901181505.KAA15315@lor.watermarkgroup.com> To: dillon@apollo.backplane.com, skynyrd@opus.cts.cwu.edu Subject: Re: NFS problem found - pleaes try this patch. Cc: freebsd-current@FreeBSD.ORG, jdp@polstra.com, luoqi@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The check is correct and should be there, the B_CACHE bit was cleared because I made a mistake when setting the valid bit in the vm page. Index: vfs_bio.c =================================================================== RCS file: /home/ncvs/src/sys/kern/vfs_bio.c,v retrieving revision 1.192 diff -u -r1.192 vfs_bio.c --- vfs_bio.c 1999/01/12 11:59:34 1.192 +++ vfs_bio.c 1999/01/18 14:45:33 @@ -2171,7 +2171,7 @@ (vm_offset_t) (soff & PAGE_MASK), (vm_offset_t) (eoff - soff)); sv = (bp->b_offset + bp->b_validoff + DEV_BSIZE - 1) & ~(DEV_BSIZE - 1); - ev = (bp->b_offset + bp->b_validend) & ~(DEV_BSIZE - 1); + ev = (bp->b_offset + bp->b_validend + DEV_BSIZE - 1) & ~(DEV_BSIZE - 1); soff = qmax(sv, soff); eoff = qmin(ev, eoff); } Note the calculation of ev, the original code was a round-up and I changed it to round-down in my -r1.188 commit (I thought it was a bug in the original code, but it was actually me who didn't understand the nfs code well enough). -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 07:17:57 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA22192 for freebsd-current-outgoing; Mon, 18 Jan 1999 07:17:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA22186 for ; Mon, 18 Jan 1999 07:17:55 -0800 (PST) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.1/8.8.8) id PAA74396 for freebsd-current@FreeBSD.ORG; Mon, 18 Jan 1999 15:17:50 GMT (envelope-from joe) Date: Mon, 18 Jan 1999 15:17:49 +0000 From: Josef Karthauser To: freebsd-current@FreeBSD.ORG Subject: New boot blocks + serial hardware handshaking? Message-ID: <19990118151749.A68260@florence.pavilion.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Organisation: Pavilion Internet plc, 24 The Old Steine, Brighton, BN1 1EL, England Phone: +44-1273-607072 Fax: +44-1273-607073 Mobile: +44-403-596893 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We're having trouble using the new boot loader code and '-h' in boot.config. It appears that unless the terminal is connected to the serial port a machine doesn't reboot properly. My guess is that the new boot serial code is defaulting to hardware handshaking on the serial terminal line, whereas the original boot code didn't. A quick glance at the code didn't confirm this, but does anyone know the answer to this off the top of their heads? Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 08:38:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA02266 for freebsd-current-outgoing; Mon, 18 Jan 1999 08:38:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from arthur.INS.CWRU.Edu (arthur.INS.CWRU.Edu [129.22.8.215]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA02261 for ; Mon, 18 Jan 1999 08:38:38 -0800 (PST) (envelope-from csteva@crs.STUDENT.CWRU.Edu) Received: from crs (crs.STUDENT.CWRU.Edu [129.22.241.108]) by arthur.INS.CWRU.Edu with SMTP (8.8.8+cwru/CWRU-3.4) id LAA07840; Mon, 18 Jan 1999 11:38:32 -0500 (EST) (from csteva@crs.cwru.edu) Message-ID: <003201be4300$f321eb60$6cf11681@cwru.edu> From: "Chris Steva" To: "Christian Kuhtz" , Subject: Re: ATM LANE support Date: Mon, 18 Jan 1999 11:38:16 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.0810.800 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Unfortunately in practice at the desktop level there are a mix of hosts that run on ATM or ethernet. As is the case here where we use LANE to integrate both in to a single network. Chris >ATM LANE is evil. Why do you want it? > >On Sun, Jan 17, 1999 at 06:58:24PM -0500, Chris Steva wrote: >> I was pleasantly surprised to find that FreeBSD 3.0 supported my FORE >> PCA-200e ATM card, but I wasn't able to get it up and running becuase there >> is no support for ethernet LANE (LAN emulation). Instead I found HARP, >> which appears to be some kind of substitue to LANE for running IP over ATM. >> Will there be support for LANE in the future? >> >> I havn't been able to find any information about what's is going on in >> FreeBSD ATM land. The Linux ATM world doesn't seem to be any further along, >> but I saw that they do have LANE support in their alpha release of ATM >> drivers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 09:39:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09814 for freebsd-current-outgoing; Mon, 18 Jan 1999 09:39:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-49-dbn.dial-up.net [196.34.155.49]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA09808 for ; Mon, 18 Jan 1999 09:39:48 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id TAA04407; Mon, 18 Jan 1999 19:39:09 +0200 (SAT) From: Robert Nordier Message-Id: <199901181739.TAA04407@ceia.nordier.com> Subject: Re: New boot blocks + serial hardware handshaking? In-Reply-To: <19990118151749.A68260@florence.pavilion.net> from Josef Karthauser at "Jan 18, 99 03:17:49 pm" To: joe@pavilion.net (Josef Karthauser) Date: Mon, 18 Jan 1999 19:39:06 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Josef Karthauser wrote: > We're having trouble using the new boot loader code and '-h' in > boot.config. It appears that unless the terminal is connected to > the serial port a machine doesn't reboot properly. My guess is > that the new boot serial code is defaulting to hardware handshaking > on the serial terminal line, whereas the original boot code didn't. > > A quick glance at the code didn't confirm this, but does anyone > know the answer to this off the top of their heads? As the one who did the actual coding, I can confirm that the approach adopted in both the new bootblocks and the boot loader is virtually identical to that used in the older (biosboot) bootblocks. In all cases, the simplest approach giving the smallest code sizes was used, so there's very little difference between the three sets of routines. The above applies to 3.0-current. In 3.0-release, the boot loader was still using BIOS routines (with hardware handshaking), but this was changed around late November 1998. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 10:22:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15088 for freebsd-current-outgoing; Mon, 18 Jan 1999 10:22:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA15082; Mon, 18 Jan 1999 10:22:25 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id KAA75229; Mon, 18 Jan 1999 10:22:19 -0800 (PST) (envelope-from dillon) Date: Mon, 18 Jan 1999 10:22:19 -0800 (PST) From: Matthew Dillon Message-Id: <199901181822.KAA75229@apollo.backplane.com> To: Luoqi Chen Cc: skynyrd@opus.cts.cwu.edu, freebsd-current@FreeBSD.ORG, jdp@polstra.com, luoqi@FreeBSD.ORG Subject: Re: NFS problem found - pleaes try this patch. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ahhhh. Yes, I see. I will unapply my patch and apply this one and test it. I'm not sure what the use of having m->valid and m->clean bits are at all if we have to munge them like this. Perhaps we should change these vm_page_t to a byte range in -4.0. I think we also need to redefine the way dirty bp's are handled, though, and at least panic if it tries to clear B_CACHE on something that B_CACHE should not be cleared on. -Matt Matthew Dillon :The check is correct and should be there, the B_CACHE bit was cleared because :I made a mistake when setting the valid bit in the vm page. : :Index: vfs_bio.c :=================================================================== :RCS file: /home/ncvs/src/sys/kern/vfs_bio.c,v :retrieving revision 1.192 :diff -u -r1.192 vfs_bio.c :--- vfs_bio.c 1999/01/12 11:59:34 1.192 :+++ vfs_bio.c 1999/01/18 14:45:33 :@@ -2171,7 +2171,7 @@ : (vm_offset_t) (soff & PAGE_MASK), : (vm_offset_t) (eoff - soff)); : sv = (bp->b_offset + bp->b_validoff + DEV_BSIZE - 1) & ~(DEV_BSIZE - 1); :- ev = (bp->b_offset + bp->b_validend) & ~(DEV_BSIZE - 1); :+ ev = (bp->b_offset + bp->b_validend + DEV_BSIZE - 1) & ~(DEV_BSIZE - 1); : soff = qmax(sv, soff); : eoff = qmin(ev, eoff); : } : :Note the calculation of ev, the original code was a round-up and I changed it :to round-down in my -r1.188 commit (I thought it was a bug in the original :code, but it was actually me who didn't understand the nfs code well enough). : :-lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 11:06:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA21288 for freebsd-current-outgoing; Mon, 18 Jan 1999 11:06:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA21277 for ; Mon, 18 Jan 1999 11:06:41 -0800 (PST) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.9.1/8.8.7) with ESMTP id OAA51434 for ; Mon, 18 Jan 1999 14:06:26 -0500 (EST) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: current@FreeBSD.ORG From: "Gary Palmer" Subject: build failure on dec axp Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 Jan 1999 14:06:26 -0500 Message-ID: <51430.916686386@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/netstat/uni x.c /usr/src/usr.bin/netstat/mbuf.c:71: `MT_RTABLE' undeclared here (not in a functi on) /usr/src/usr.bin/netstat/mbuf.c:71: initializer element for `mbtypes[4].mt_type' is not constant Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 11:28:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA24462 for freebsd-current-outgoing; Mon, 18 Jan 1999 11:28:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oreo.adsu.bellsouth.com (oreo.adsu.bellsouth.com [205.152.173.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA24430 for ; Mon, 18 Jan 1999 11:28:24 -0800 (PST) (envelope-from ck@oreo.adsu.bellsouth.com) Received: (from ck@localhost) by oreo.adsu.bellsouth.com (8.9.1/8.9.1) id OAA02317 for freebsd-current@freebsd.org; Mon, 18 Jan 1999 14:28:16 -0500 (EST) (envelope-from ck) Date: Mon, 18 Jan 1999 14:28:16 -0500 From: Christian Kuhtz To: freebsd-current@FreeBSD.ORG Subject: make release & vn Message-ID: <19990118142816.G405@oreo.adsu.bellsouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey gang: Should I worry about these messages on the console when doing a make release? vn0: raw partition size != slice size vn0: start 0, end 2879, size 2880 vn0: start 0, end 5759, size 5760 vn0: truncating raw partition vn0: rejecting partition in BSD label: it isn't entirely within the slice vn0: start 0, end 2879, size 2880 vn0: start 0, end 5759, size 5760 Eventually (later in the build) the make release fails because /mnt is full. I'm running a CVSup mirror locally, which sync'ed every hour with cvsup.freebsd.org. The make release failed just a few minutes ago, and was started a couple of hours ago. Cheers, Chris -- "We are not bound by any concept, we are just bound to make any concept work better than others." -- Dr. Ferry Porsche [Disclaimer: I speak for myself and my views are my own and not in any way to be construed as the views of BellSouth Corporation. ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 11:36:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25855 for freebsd-current-outgoing; Mon, 18 Jan 1999 11:36:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.6.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25839 for ; Mon, 18 Jan 1999 11:36:11 -0800 (PST) (envelope-from plm@smtp1.xs4all.nl) Received: from localhost. (dc2-isdn293.dial.xs4all.nl [194.109.149.37]) by smtp1.xs4all.nl (8.8.8/8.8.8) with ESMTP id UAA15406 for ; Mon, 18 Jan 1999 20:35:57 +0100 (CET) Received: (from plm@localhost) by localhost. (8.9.1/8.9.1) id UAA10145; Mon, 18 Jan 1999 20:35:56 +0100 (MET) (envelope-from plm) To: freebsd-current@FreeBSD.ORG Subject: aic (adaptec 152x) still not supported in -current? From: Peter Mutsaers Date: 18 Jan 1999 20:35:55 +0100 Message-ID: <8767a4e5lw.fsf@muon.xs4all.nl> Lines: 16 X-Mailer: Gnus v5.6.45/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, When CAM was integrated someone reported that the aic driver was not ready yet for CAM, but that "Brian Beattie is working on it". At the moment, looking in LINT, it looks like aic still isn't supported. Is that true? Does anyone know whether it will be? Thanks, -- Peter Mutsaers | Abcoude (Utrecht), | Trust me, I know plm@xs4all.nl | the Netherlands | what I'm doing. ---------------+---------------------+----------------- Running FreeBSD-3.0 UNIX. See http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 11:47:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27741 for freebsd-current-outgoing; Mon, 18 Jan 1999 11:47:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27733 for ; Mon, 18 Jan 1999 11:47:17 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA26268 for ; Mon, 18 Jan 1999 11:38:48 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdF26263; Mon Jan 18 19:38:42 1999 Date: Mon, 18 Jan 1999 11:38:39 -0800 (PST) From: Julian Elischer To: current@FreeBSD.ORG Subject: kernel malloc and M_CANWAIT Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here at whistle we are trying to remember about a conversation regarding malloc that occured recently. Maybe others can help. There was some talk about the fact that malloc(..M_CANWAIT) can now return with a failure. Is that true? who has their finger on that particular button? julian (p.s. still searching the archives but not having much success) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 11:58:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29805 for freebsd-current-outgoing; Mon, 18 Jan 1999 11:58:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA29746 for ; Mon, 18 Jan 1999 11:58:05 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA26768 for ; Mon, 18 Jan 1999 11:52:06 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpda26749; Mon Jan 18 19:51:53 1999 Date: Mon, 18 Jan 1999 11:51:43 -0800 (PST) From: Julian Elischer To: current@FreeBSD.ORG Subject: oops on last mail..(malloc) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of course I meant M_WAITOK not M_CANWAIT julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 12:16:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA03351 for freebsd-current-outgoing; Mon, 18 Jan 1999 12:16:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shell3.ba.best.com (shell3.ba.best.com [206.184.139.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA03344 for ; Mon, 18 Jan 1999 12:16:30 -0800 (PST) (envelope-from schrade@schrade.com) Received: from localhost (schrade@localhost [127.0.0.1]) by shell3.ba.best.com (8.9.2/8.9.2/best.sh) with ESMTP id MAA15071 for ; Mon, 18 Jan 1999 12:16:11 -0800 (PST) Date: Mon, 18 Jan 1999 12:16:11 -0800 (PST) From: Ken Krebs To: current@FreeBSD.ORG Subject: RELNOTES.TXT Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In /usr/src/release/texts/RELNOTES.TXT it lists the following for supported adaptec controllers: Adaptec 1535 ISA SCSI controllers Adaptec 154x series ISA SCSI controllers Adaptec 174x series EISA SCSI controller in standard and enhanced mode. Adaptec 274X/284X/2920/2940/2950/3940/3950 (Narrow/Wide/Twin) series ^^^^ EISA/VLB/PCI SCSI controllers. Adaptec AIC7850, AIC7880, AIC789x, on-board SCSI controllers. As far as I know, I don't think the 2920 is supported since it's not a standard adaptec card (it was bought from another company) If I'm wrong, I'd be really pleased since we've been trying to get one of these cards to be supported in FreeBSD 3.0-current. But if I'm right, it should be removed because it's sure to piss people off :) The last known source for the old patches to get this card working are at the following URL: http://www.sbox.tu-graz.ac.at/home/r/rmike/freebsd/welcome.html They, of course, don't work with CAM. IRC: Schrade E-Mail: schrade@schrade.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 12:24:02 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA04376 for freebsd-current-outgoing; Mon, 18 Jan 1999 12:24:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles250.castles.com [208.214.165.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA04371 for ; Mon, 18 Jan 1999 12:24:01 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA18399; Mon, 18 Jan 1999 12:20:35 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901182020.MAA18399@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Julian Elischer cc: current@FreeBSD.ORG Subject: Re: kernel malloc and M_CANWAIT In-reply-to: Your message of "Mon, 18 Jan 1999 11:38:39 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 Jan 1999 12:20:34 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Here at whistle we are trying to remember about a conversation > regarding malloc that occured recently. Maybe others can help. > > There was some talk about the fact that malloc(..M_CANWAIT) > can now return with a failure. Is that true? Yes; it's necessary to do this to allow some chance of avoiding deadlock. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 12:29:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA05412 for freebsd-current-outgoing; Mon, 18 Jan 1999 12:29:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA05391 for ; Mon, 18 Jan 1999 12:29:44 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id PAA19180; Mon, 18 Jan 1999 15:29:11 -0500 (EST) Date: Mon, 18 Jan 1999 15:29:11 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Mike Smith cc: Julian Elischer , current@FreeBSD.ORG Subject: Re: kernel malloc and M_CANWAIT In-Reply-To: <199901182020.MAA18399@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 18 Jan 1999, Mike Smith wrote: > > > > Here at whistle we are trying to remember about a conversation > > regarding malloc that occured recently. Maybe others can help. > > > > There was some talk about the fact that malloc(..M_CANWAIT) > > can now return with a failure. Is that true? > > Yes; it's necessary to do this to allow some chance of avoiding > deadlock. Ouch! Is everything in src-sys already checking the return value of an M_WAITOK? > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 12:33:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA05856 for freebsd-current-outgoing; Mon, 18 Jan 1999 12:33:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles250.castles.com [208.214.165.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA05847 for ; Mon, 18 Jan 1999 12:33:40 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA18468; Mon, 18 Jan 1999 12:29:32 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901182029.MAA18468@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Feldman cc: Mike Smith , Julian Elischer , current@FreeBSD.ORG Subject: Re: kernel malloc and M_CANWAIT In-reply-to: Your message of "Mon, 18 Jan 1999 15:29:11 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 Jan 1999 12:29:31 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, 18 Jan 1999, Mike Smith wrote: > > > > > > > Here at whistle we are trying to remember about a conversation > > > regarding malloc that occured recently. Maybe others can help. > > > > > > There was some talk about the fact that malloc(..M_CANWAIT) > > > can now return with a failure. Is that true? > > > > Yes; it's necessary to do this to allow some chance of avoiding > > deadlock. > > Ouch! Is everything in src-sys already checking the return value of an M_WAITOK? Probably not, no. I had some patches from Andrzej who was trying to do it just for the mbuf allocator case; there's definitely a call for someone to take the time to clean things up. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 12:40:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA06703 for freebsd-current-outgoing; Mon, 18 Jan 1999 12:40:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA06698 for ; Mon, 18 Jan 1999 12:40:27 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id PAA19890; Mon, 18 Jan 1999 15:40:18 -0500 (EST) Date: Mon, 18 Jan 1999 15:40:18 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Mike Smith cc: Julian Elischer , current@FreeBSD.ORG Subject: Re: kernel malloc and M_CANWAIT In-Reply-To: <199901182029.MAA18468@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 18 Jan 1999, Mike Smith wrote: > > On Mon, 18 Jan 1999, Mike Smith wrote: > > > > > > > > > > Here at whistle we are trying to remember about a conversation > > > > regarding malloc that occured recently. Maybe others can help. > > > > > > > > There was some talk about the fact that malloc(..M_CANWAIT) > > > > can now return with a failure. Is that true? > > > > > > Yes; it's necessary to do this to allow some chance of avoiding > > > deadlock. > > > > Ouch! Is everything in src-sys already checking the return value of an M_WAITOK? > > Probably not, no. I had some patches from Andrzej who was trying to do > it just for the mbuf allocator case; there's definitely a call for > someone to take the time to clean things up. Well, it'll be hard to determine (for me, not knowing any of the kernel well) whether it's proper for: a. return EAGAIN b. return ENOMEN c. try again, then return EAGAIN/ENOMEM? But I'm going to start fixing what I can. It would have been nice for a HEADS UP! or somesuch. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 12:41:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA06768 for freebsd-current-outgoing; Mon, 18 Jan 1999 12:41:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA06758 for ; Mon, 18 Jan 1999 12:41:05 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id MAA78403; Mon, 18 Jan 1999 12:40:59 -0800 (PST) (envelope-from dillon) Date: Mon, 18 Jan 1999 12:40:59 -0800 (PST) From: Matthew Dillon Message-Id: <199901182040.MAA78403@apollo.backplane.com> To: Brian Feldman Cc: Mike Smith , Julian Elischer , current@FreeBSD.ORG Subject: Re: kernel malloc and M_CANWAIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> > There was some talk about the fact that malloc(..M_CANWAIT) :> > can now return with a failure. Is that true? :> :> Yes; it's necessary to do this to allow some chance of avoiding :> deadlock. : :Ouch! Is everything in src-sys already checking the return value of an M_WAITOK? : : Brian Feldman _ __ ___ ___ ___ It looks like malloc() can return NULL if the kmem_malloc() fails. kmem_malloc() can only fail in the M_WAITOK case if the KVM map is full. If the system is simply low on memory, kmem_malloc() will block. So malloc() will generally not return NULL even in low memory situations unless the KVM map fills up, which isn't supposed to happen but can in certain severe circumstances. Callers should therefore check for NULL. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 12:59:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09941 for freebsd-current-outgoing; Mon, 18 Jan 1999 12:59:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA09936 for ; Mon, 18 Jan 1999 12:59:11 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id MAA29573; Mon, 18 Jan 1999 12:49:52 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdm29556; Mon Jan 18 20:49:41 1999 Date: Mon, 18 Jan 1999 12:49:31 -0800 (PST) From: Julian Elischer To: Mike Smith cc: current@FreeBSD.ORG Subject: Re: kernel malloc and M_CANWAIT In-Reply-To: <199901182020.MAA18399@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 18 Jan 1999, Mike Smith wrote: > > > > Here at whistle we are trying to remember about a conversation > > regarding malloc that occured recently. Maybe others can help. > > > > There was some talk about the fact that malloc(..M_CANWAIT) oops M_WAITOK.. > > can now return with a failure. Is that true? > > Yes; it's necessary to do this to allow some chance of avoiding > deadlock. I can't find this in the archives.. can you remember a keyword that would pull it up? I've looked in.. The archives freebsd-current and freebsd-hackers contain the following items relevant to `malloc AND M_WAITOK AND 1998' (and similar) It seems to me that there must be a lot of places where the return value of MALLOC is not tested when M_WAITOK is set. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 12:59:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09988 for freebsd-current-outgoing; Mon, 18 Jan 1999 12:59:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA09981 for ; Mon, 18 Jan 1999 12:59:27 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id MAA00156; Mon, 18 Jan 1999 12:57:33 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdcWe132; Mon Jan 18 20:57:22 1999 Date: Mon, 18 Jan 1999 12:57:02 -0800 (PST) From: Julian Elischer To: Matthew Dillon cc: Brian Feldman , Mike Smith , current@FreeBSD.ORG Subject: Re: kernel malloc and M_CANWAIT In-Reply-To: <199901182040.MAA78403@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 18 Jan 1999, Matthew Dillon wrote: > :> > There was some talk about the fact that malloc(..M_CANWAIT) > :> > can now return with a failure. Is that true? > :> > :> Yes; it's necessary to do this to allow some chance of avoiding > :> deadlock. > : > :Ouch! Is everything in src-sys already checking the return value of an M_WAITOK? > : > : Brian Feldman _ __ ___ ___ ___ > > It looks like malloc() can return NULL if the kmem_malloc() fails. > > kmem_malloc() can only fail in the M_WAITOK case if the KVM map is full. > If the system is simply low on memory, kmem_malloc() will block. > > So malloc() will generally not return NULL even in low memory situations > unless the KVM map fills up, which isn't supposed to happen but can in > certain severe circumstances. Callers should therefore check for NULL. why not just put it in a loop and block on lbolt? (or call panic) the trouble is that this is a major change in semantics and will affect code flow all over the place. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 13:04:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA11194 for freebsd-current-outgoing; Mon, 18 Jan 1999 13:04:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles250.castles.com [208.214.165.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA11187 for ; Mon, 18 Jan 1999 13:04:53 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA18690; Mon, 18 Jan 1999 13:01:19 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901182101.NAA18690@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Julian Elischer cc: current@FreeBSD.ORG Subject: Re: kernel malloc and M_CANWAIT In-reply-to: Your message of "Mon, 18 Jan 1999 12:49:31 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 Jan 1999 13:01:19 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > There was some talk about the fact that malloc(..M_CANWAIT) > oops M_WAITOK.. > > > > can now return with a failure. Is that true? > > > > Yes; it's necessary to do this to allow some chance of avoiding > > deadlock. > > I can't find this in the archives.. can you remember > a keyword that would pull it up? No; Matt's on the spot with his comment though, and it's trivial to understand why it needs to be able to fail to avoid deadlock. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 13:09:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA11866 for freebsd-current-outgoing; Mon, 18 Jan 1999 13:09:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles250.castles.com [208.214.165.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA11861 for ; Mon, 18 Jan 1999 13:09:14 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA18722; Mon, 18 Jan 1999 13:05:25 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901182105.NAA18722@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Julian Elischer cc: Matthew Dillon , Brian Feldman , Mike Smith , current@FreeBSD.ORG Subject: Re: kernel malloc and M_CANWAIT In-reply-to: Your message of "Mon, 18 Jan 1999 12:57:02 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 Jan 1999 13:05:24 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > So malloc() will generally not return NULL even in low memory situations > > unless the KVM map fills up, which isn't supposed to happen but can in > > certain severe circumstances. Callers should therefore check for NULL. > > why not just put it in a loop and block on lbolt? > (or call panic) Because you shouldn't panic unless there's no alternative. Panicking on resource starvation is just totally lame. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 13:35:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA15298 for freebsd-current-outgoing; Mon, 18 Jan 1999 13:35:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA15285 for ; Mon, 18 Jan 1999 13:35:01 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id QAA23082; Mon, 18 Jan 1999 16:34:49 -0500 (EST) Date: Mon, 18 Jan 1999 16:34:49 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Mike Smith cc: Julian Elischer , Matthew Dillon , current@FreeBSD.ORG Subject: Re: kernel malloc and M_CANWAIT In-Reply-To: <199901182105.NAA18722@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 18 Jan 1999, Mike Smith wrote: > > > So malloc() will generally not return NULL even in low memory situations > > > unless the KVM map fills up, which isn't supposed to happen but can in > > > certain severe circumstances. Callers should therefore check for NULL. > > > > why not just put it in a loop and block on lbolt? > > (or call panic) > > Because you shouldn't panic unless there's no alternative. Panicking > on resource starvation is just totally lame. And what's wrong with spinning inside malloc until the resources are free? There are places that architecturally require M_WAITOK to not return NULL. Look at the void () functions that call malloc/MALLOC. Also, commit the attached patch; it was OKed by Bruce to disallow this, but he seems to forget to commit it. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ --- src/sys/kern/vfs_syscalls.c.orig Fri Dec 25 22:27:21 1998 +++ src/sys/kern/vfs_syscalls.c Fri Dec 25 22:28:12 1998 @@ -2909,6 +2909,10 @@ if (error = namei(&nd)) return (error); vp = nd.ni_vp; + if (vp->v_type == VFIFO) { + error = EINVAL; + goto out; + } if (error = VOP_GETATTR(vp, &vattr, p->p_ucred, p)) goto out; if (p->p_ucred->cr_uid != vattr.va_uid && To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 13:41:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16198 for freebsd-current-outgoing; Mon, 18 Jan 1999 13:41:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16193 for ; Mon, 18 Jan 1999 13:41:29 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id IAA14501; Tue, 19 Jan 1999 08:41:21 +1100 Date: Tue, 19 Jan 1999 08:41:21 +1100 From: Bruce Evans Message-Id: <199901182141.IAA14501@godzilla.zeta.org.au> To: current@FreeBSD.ORG, julian@whistle.com Subject: Re: kernel malloc and M_CANWAIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >There was some talk about the fact that malloc(..M_CANWAIT) >can now return with a failure. You mean M_WAITOK. >Is that true? Of course not. It is fundamental that malloc(..., M_WAITOK) either succeeds or panics. Most callers depend on this and don't check for success. The others are bogus. You may be thinking of the documented but unimplemented new flag M_ASLEEP. It's hard to see what this does (since it is unimplemented), but the docs say to only use it with M_NOWAIT. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 13:47:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16995 for freebsd-current-outgoing; Mon, 18 Jan 1999 13:47:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16984 for ; Mon, 18 Jan 1999 13:47:42 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id QAA23771; Mon, 18 Jan 1999 16:47:27 -0500 (EST) Date: Mon, 18 Jan 1999 16:47:27 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Mike Smith cc: Julian Elischer , Matthew Dillon , current@FreeBSD.ORG Subject: Re2: kernel malloc and M_CANWAIT In-Reply-To: <199901182105.NAA18722@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 18 Jan 1999, Mike Smith wrote: > > > So malloc() will generally not return NULL even in low memory situations > > > unless the KVM map fills up, which isn't supposed to happen but can in > > > certain severe circumstances. Callers should therefore check for NULL. > > > > why not just put it in a loop and block on lbolt? > > (or call panic) > > Because you shouldn't panic unless there's no alternative. Panicking > on resource starvation is just totally lame. Ahem: uipc_mbuf.c: unmodified, readonly: line 268 of 945 [28%] panic("Out of mbuf clusters"); uipc_mbuf.c: unmodified, readonly: line 296 of 945 [31%] panic("Out of mbuf clusters"); And if the max number of mbuf clusters is{, to become} a sysctl, shouldn't these just be informative printf()s or something? > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 13:47:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17002 for freebsd-current-outgoing; Mon, 18 Jan 1999 13:47:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16986 for ; Mon, 18 Jan 1999 13:47:43 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA02078 for ; Mon, 18 Jan 1999 13:39:18 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdGc2063; Mon Jan 18 21:39:08 1999 Date: Mon, 18 Jan 1999 13:38:51 -0800 (PST) From: Julian Elischer To: current@FreeBSD.ORG Subject: Sync card users. need testers.. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Whistle is preparing to submit it's synchronous protocols suppoort framework, but to make it usable we'd like to be able to release it with support for the sr and ar sync cards (and maybe even the third (cx) if I can get to it). However as we have NONE of those cards I'll need people to help test the driver mods. We can presently run sync cards in, raw hdlc, cisco-hdlc, raw framerelay, rfc1490 over framerelay, and, with userland help, ppp over all the above. Anyone who is running a recent -current and who would be able to help with any of the 3 sync cards mantionned above is invited to contact me for information on how we can test these. The new code is non invasive, (i.e it doesn't edit other kernel files) except for the additions to the 3 sync driver files. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 13:51:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17602 for freebsd-current-outgoing; Mon, 18 Jan 1999 13:51:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hda.hda.com (hda-bicnet.bicnet.net [209.244.238.132] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17588 for ; Mon, 18 Jan 1999 13:51:18 -0800 (PST) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id QAA09337; Mon, 18 Jan 1999 16:44:45 -0500 (EST) From: Peter Dufault Message-Id: <199901182144.QAA09337@hda.hda.com> Subject: Re: kernel malloc and M_CANWAIT In-Reply-To: <199901182105.NAA18722@dingo.cdrom.com> from Mike Smith at "Jan 18, 99 01:05:24 pm" To: mike@smith.net.au (Mike Smith) Date: Mon, 18 Jan 1999 16:44:45 -0500 (EST) Cc: julian@whistle.com, dillon@apollo.backplane.com, green@unixhelp.org, mike@smith.net.au, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > why not just put it in a loop and block on lbolt? > > (or call panic) > > Because you shouldn't panic unless there's no alternative. Panicking > on resource starvation is just totally lame. We haven't used up the kernel name space yet. This sort of fundamental change should be enabled by a new flag and then added when handled. Changing things to return NULL pointers in the kernel where they never were before is equally lame. Without the appropriate work you're just pushing the panic off to a hard to find location. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 13:58:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18551 for freebsd-current-outgoing; Mon, 18 Jan 1999 13:58:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA18536 for ; Mon, 18 Jan 1999 13:58:07 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA02930; Mon, 18 Jan 1999 13:55:31 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdcZ2924; Mon Jan 18 21:55:22 1999 Date: Mon, 18 Jan 1999 13:55:17 -0800 (PST) From: Julian Elischer To: Bruce Evans cc: current@FreeBSD.ORG Subject: Re: kernel malloc and M_CANWAIT In-Reply-To: <199901182141.IAA14501@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 19 Jan 1999, Bruce Evans wrote: > >There was some talk about the fact that malloc(..M_CANWAIT) > >can now return with a failure. > > You mean M_WAITOK. yes.. a braino.. (I corrected in later mail) > > >Is that true? > > Of course not. It is fundamental that malloc(..., M_WAITOK) either > succeeds or panics. Most callers depend on this and don't check for > success. The others are bogus. actually it turns out to be true.. see other email from matt. > > You may be thinking of the documented but unimplemented new flag > M_ASLEEP. It's hard to see what this does (since it is > unimplemented), but the docs say to only use it with M_NOWAIT. Unrelated > > Bruce > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 14:11:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA21026 for freebsd-current-outgoing; Mon, 18 Jan 1999 14:11:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA21017 for ; Mon, 18 Jan 1999 14:11:48 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id JAA17726; Tue, 19 Jan 1999 09:11:38 +1100 Date: Tue, 19 Jan 1999 09:11:38 +1100 From: Bruce Evans Message-Id: <199901182211.JAA17726@godzilla.zeta.org.au> To: dillon@apollo.backplane.com, green@unixhelp.org Subject: Re: kernel malloc and M_CANWAIT Cc: current@FreeBSD.ORG, julian@whistle.com, mike@smith.net.au Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It looks like malloc() can return NULL if the kmem_malloc() fails. Not for the M_WAITOK case. > kmem_malloc() can only fail in the M_WAITOK case if the KVM map is full. kmem_malloc() panics in this case (except for map == mb_map; the mbuf allocator has special handling for this problem). > If the system is simply low on memory, kmem_malloc() will block. > > So malloc() will generally not return NULL even in low memory situations > unless the KVM map fills up, which isn't supposed to happen but can in > certain severe circumstances. Callers should therefore check for NULL. Callers that check for NULL are bogus. Callers that can actually handle low memory conditions should use M_NOWAIT. There should probably be a flag that says to wait for everything except the map to unfill, and this flag should have been used instead of the `map == mb_map' hack, but no callers actually handle filling of their map (the mbuf allocator doesn't -- it tends to panic a little later because m_retry[hdr]() is not prepared to pass failures back to callers in the can-wait case). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 14:16:16 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA21762 for freebsd-current-outgoing; Mon, 18 Jan 1999 14:16:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA21757 for ; Mon, 18 Jan 1999 14:16:12 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id JAA18275; Tue, 19 Jan 1999 09:16:06 +1100 Date: Tue, 19 Jan 1999 09:16:06 +1100 From: Bruce Evans Message-Id: <199901182216.JAA18275@godzilla.zeta.org.au> To: bde@zeta.org.au, julian@whistle.com Subject: Re: kernel malloc and M_CANWAIT Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Of course not. It is fundamental that malloc(..., M_WAITOK) either >> succeeds or panics. Most callers depend on this and don't check for >> success. The others are bogus. > >actually it turns out to be true.. Actually not. >see other email from matt. See my corrections to that mail. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 14:21:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA22484 for freebsd-current-outgoing; Mon, 18 Jan 1999 14:21:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles250.castles.com [208.214.165.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA22471 for ; Mon, 18 Jan 1999 14:20:58 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA19112; Mon, 18 Jan 1999 14:17:04 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901182217.OAA19112@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Feldman cc: Mike Smith , Julian Elischer , Matthew Dillon , current@FreeBSD.ORG Subject: Re: kernel malloc and M_CANWAIT In-reply-to: Your message of "Mon, 18 Jan 1999 16:34:49 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 Jan 1999 14:17:03 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, 18 Jan 1999, Mike Smith wrote: > > > > > So malloc() will generally not return NULL even in low memory situations > > > > unless the KVM map fills up, which isn't supposed to happen but can in > > > > certain severe circumstances. Callers should therefore check for NULL. > > > > > > why not just put it in a loop and block on lbolt? > > > (or call panic) > > > > Because you shouldn't panic unless there's no alternative. Panicking > > on resource starvation is just totally lame. > > And what's wrong with spinning inside malloc until the resources are free? If you have to ask this, you have a lot of reading to do before you're going to be able to understand any of the deadlock issues. Just as a hint for this one though - if you're spinning inside malloc() waiting for the resources to be freed, who is going to free them? > There are places that architecturally require M_WAITOK to not return NULL. > Look at the void () functions that call malloc/MALLOC. These are (obviously) bogus code. So they need to be fixed... > Also, commit the > attached patch; it was OKed by Bruce to disallow this, but he seems to forget > to commit it. I'm not going to second-guess Bruce on this one. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 14:21:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA22536 for freebsd-current-outgoing; Mon, 18 Jan 1999 14:21:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA22520 for ; Mon, 18 Jan 1999 14:21:07 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id JAA18722; Tue, 19 Jan 1999 09:21:00 +1100 Date: Tue, 19 Jan 1999 09:21:00 +1100 From: Bruce Evans Message-Id: <199901182221.JAA18722@godzilla.zeta.org.au> To: green@unixhelp.org, mike@smith.net.au Subject: Re: kernel malloc and M_CANWAIT Cc: current@FreeBSD.ORG, dillon@apollo.backplane.com, julian@whistle.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Look at the void () functions that call malloc/MALLOC. Also, commit the >attached patch; it was OKed by Bruce to disallow this, but he seems to forget >to commit it. It is queued behind 10-100 other patches. >--- src/sys/kern/vfs_syscalls.c.orig Fri Dec 25 22:27:21 1998 >+++ src/sys/kern/vfs_syscalls.c Fri Dec 25 22:28:12 1998 >@@ -2909,6 +2909,10 @@ > if (error = namei(&nd)) > return (error); > vp = nd.ni_vp; >+ if (vp->v_type == VFIFO) { >+ error = EINVAL; >+ goto out; >+ } > if (error = VOP_GETATTR(vp, &vattr, p->p_ucred, p)) > goto out; > if (p->p_ucred->cr_uid != vattr.va_uid && Actually, the patch from Lite1 is queued. It also backs out support for revoke of everything except cdevs and bdevs. I don't have time to check what happens for regular files, pipes and sockets... Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 14:22:16 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA22775 for freebsd-current-outgoing; Mon, 18 Jan 1999 14:22:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles250.castles.com [208.214.165.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA22626 for ; Mon, 18 Jan 1999 14:22:00 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA19128; Mon, 18 Jan 1999 14:18:18 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901182218.OAA19128@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Feldman cc: Mike Smith , Julian Elischer , Matthew Dillon , current@FreeBSD.ORG Subject: Re: Re2: kernel malloc and M_CANWAIT In-reply-to: Your message of "Mon, 18 Jan 1999 16:47:27 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 Jan 1999 14:18:17 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Because you shouldn't panic unless there's no alternative. Panicking > > on resource starvation is just totally lame. > > Ahem: > uipc_mbuf.c: unmodified, readonly: line 268 of 945 [28%] > panic("Out of mbuf clusters"); > uipc_mbuf.c: unmodified, readonly: line 296 of 945 [31%] > panic("Out of mbuf clusters"); > And if the max number of mbuf clusters is{, to become} a sysctl, shouldn't > these just be informative printf()s or something? See my earlier comment about work in progress on just exactly this. Pay attention. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 14:37:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25135 for freebsd-current-outgoing; Mon, 18 Jan 1999 14:37:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles250.castles.com [208.214.165.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25129 for ; Mon, 18 Jan 1999 14:36:56 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA19242; Mon, 18 Jan 1999 14:33:19 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901182233.OAA19242@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bruce Evans cc: current@FreeBSD.ORG Subject: Re: kernel malloc and M_CANWAIT In-reply-to: Your message of "Tue, 19 Jan 1999 09:11:38 +1100." <199901182211.JAA17726@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 Jan 1999 14:33:18 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > If the system is simply low on memory, kmem_malloc() will block. > > > > So malloc() will generally not return NULL even in low memory situations > > unless the KVM map fills up, which isn't supposed to happen but can in > > certain severe circumstances. Callers should therefore check for NULL. > > Callers that check for NULL are bogus. If it can truly never return NULL, that's true. But it would also be true to say that callers that can't deal with a veto return and that can't guarantee deadlock avoidance are also bogus. I got the impression that my understanding of M_WAITOK's behaviour came from a discussion with you about it, but it looks like I was mistaken. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 17:01:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA13539 for freebsd-current-outgoing; Mon, 18 Jan 1999 17:01:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA13529 for ; Mon, 18 Jan 1999 17:01:23 -0800 (PST) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.1/8.9.1) id RAA25215 for freebsd-current@freebsd.org; Mon, 18 Jan 1999 17:00:54 -0800 (PST) (envelope-from dhw) Date: Mon, 18 Jan 1999 17:00:54 -0800 (PST) From: David Wolfskill Message-Id: <199901190100.RAA25215@pau-amma.whistle.com> To: freebsd-current@FreeBSD.ORG Subject: 19990112-SNAP: no /usr/libexec/ld.so Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Making use of a hint from Mike Smith (re: "two-floppy boot"), I tried upgrading a box here that had been running an older level of -CURRENT to the 19990112-SNAP. Died while copying data (I think it was ports) with a SIGSEGV; no recent corefiles were on the system, and I didn't think it was worthwhile to try to reproduce the failure. Since my basic task was to get the machine running that SNAP, and since there wasn't much critical on the system, I elected to just re-install. That worked, and I booted (in single-user mode) to edit /etc/rc.conf (to add in the name of the NIS domain, as well as a couple of other tweaks). I then created a new kernel config file, and config CLEAR cd ../../compile/CLEAR make depend && make && make install && reboot which worked OK, but toward the tail end of the boot process, 6 occurrences of Couldn't open /usr/libexec/ld.so. were issued. Sure enough, ls -l /usr/libexec/ld* yields: -r-xr-xr-x 1 root wheel 62872 Jan 13 03:37 /usr/libexec/ld-elf.so.1 On a colleague's 3.0 system, the same command yields: -r-xr-xr-x 1 root wheel 62900 Jan 8 19:31 /usr/libexec/ld-elf.so.1 -r-xr-xr-x 1 root wheel 77824 Nov 11 08:16 /usr/libexec/ld.so It appears that /usr/libexec/ld.so is found, OK... but this colleague re-builds thinsg fairly often, and that file seems to have merely been left there, rather than having been built any time in the recent past. Further, I tried an exhaustive "find" looking for ld.so on the new system; no such file found anywhere. As for why the start-up was looking for the file, I suspect that it's an issue with the contents of /usr/local/etc/rc.d -- which (in the environment that I inherited here) is mounted from an NFS export from a (now) FreeBSD-2.2.6-R system. (Actually, all of /usr/local is thus mounted.) And sure enough, if I try to telnet to the system, I get: pau-amma[37]% telnet clear Trying 207.76.205.132... Connected to clear.whistle.com. Escape character is '^]'. FreeBSD/i386 (clear.whistle.com) (ttyp0) login: dhw Password: Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 3.0.0-19990112-SNAP (CLEAR) #0: Mon Jan 18 16:09:57 PST 1999 Welcome to FreeBSD! If the doc distribution has been loaded on this machine, the FreeBSD Handbook will be in file:/usr/share/doc/handbook and the FAQ in file:/usr/share/doc/FAQ Type /stand/sysinstall to re-enter the installation and configuration utility. No ld.so Connection closed by foreign host. pau-amma[38]% (A telnet as root goes OK (since I whacked /etc/ttys to permit this, though I realize it's dangerous), so it's likely that my attempted use of a.out-flavored stuff is a problem.) I suppose I could copy /usr/libexec/ld.so from a random machine, but that approach seems to be, at best, inelegant. Also, I don't look forward to doing the same to each machine on our (engineering) net. I welcome suggestions for making this work better (for some arguably reasonable definition of the term "better"). Thankas, david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 17:26:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17215 for freebsd-current-outgoing; Mon, 18 Jan 1999 17:26:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17206 for ; Mon, 18 Jan 1999 17:26:37 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id UAA06184; Mon, 18 Jan 1999 20:26:18 -0500 (EST) Date: Mon, 18 Jan 1999 20:26:18 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Bruce Evans cc: mike@smith.net.au, current@FreeBSD.ORG, dillon@apollo.backplane.com, julian@whistle.com Subject: Re: kernel malloc and M_CANWAIT In-Reply-To: <199901182221.JAA18722@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 19 Jan 1999, Bruce Evans wrote: > >Look at the void () functions that call malloc/MALLOC. Also, commit the > >attached patch; it was OKed by Bruce to disallow this, but he seems to forget > >to commit it. > > It is queued behind 10-100 other patches. > > >--- src/sys/kern/vfs_syscalls.c.orig Fri Dec 25 22:27:21 1998 > >+++ src/sys/kern/vfs_syscalls.c Fri Dec 25 22:28:12 1998 > >@@ -2909,6 +2909,10 @@ > > if (error = namei(&nd)) > > return (error); > > vp = nd.ni_vp; > >+ if (vp->v_type == VFIFO) { > >+ error = EINVAL; > >+ goto out; > >+ } > > if (error = VOP_GETATTR(vp, &vattr, p->p_ucred, p)) > > goto out; > > if (p->p_ucred->cr_uid != vattr.va_uid && > > Actually, the patch from Lite1 is queued. It also backs out support > for revoke of everything except cdevs and bdevs. I don't have time to > check what happens for regular files, pipes and sockets... Hmm... that may be a good idea, although for it seems to work on all of them, I haven't checked for any kind of leak in the others, nor would truly expect one. And pipes ARE fifo's aren't they? > > Bruce > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 17:28:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17466 for freebsd-current-outgoing; Mon, 18 Jan 1999 17:28:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17447 for ; Mon, 18 Jan 1999 17:28:33 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id UAA06297; Mon, 18 Jan 1999 20:28:21 -0500 (EST) Date: Mon, 18 Jan 1999 20:28:21 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Mike Smith cc: Bruce Evans , current@FreeBSD.ORG Subject: Re: kernel malloc and M_CANWAIT In-Reply-To: <199901182233.OAA19242@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 18 Jan 1999, Mike Smith wrote: > > > If the system is simply low on memory, kmem_malloc() will block. > > > > > > So malloc() will generally not return NULL even in low memory situations > > > unless the KVM map fills up, which isn't supposed to happen but can in > > > certain severe circumstances. Callers should therefore check for NULL. > > > > Callers that check for NULL are bogus. > > If it can truly never return NULL, that's true. But it would also be > true to say that callers that can't deal with a veto return and that > can't guarantee deadlock avoidance are also bogus. > > I got the impression that my understanding of M_WAITOK's behaviour > came from a discussion with you about it, but it looks like I was > mistaken. Everyone else's impression of malloc M_WAITOK's behavior has always been that it could never return NULL, at least without (say) trying to allocate all available kernel memory. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 18:04:50 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22313 for freebsd-current-outgoing; Mon, 18 Jan 1999 18:04:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from andrsn.stanford.edu (andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA22308 for ; Mon, 18 Jan 1999 18:04:49 -0800 (PST) (envelope-from andrsn@andrsn.stanford.edu) Received: from localhost (andrsn@localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.9.1/8.9.1) with SMTP id SAA25702; Mon, 18 Jan 1999 18:04:16 -0800 (PST) Date: Mon, 18 Jan 1999 18:04:15 -0800 (PST) From: Annelise Anderson To: Chan Yiu Wah cc: freebsd-current@FreeBSD.ORG Subject: Re: how to update the system from the master machine In-Reply-To: <199901180822.QAA17026@b1.hkstar.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 18 Jan 1999, Chan Yiu Wah wrote: > Hello, > > I have two system. One is P233 (master) and the other is a dual P90. > How can I update the dual P90 system from the P233 (master) system. > Is there anyone can share your experience with me. Thanks. > > clarence I have used dump and restore to "clone" a running system, but you want to be careful about what you don't want to be identical on the two systems, or, in my case, the two drives. I use rsync to keep it up to date, so the second disk is a backup for the first. This can be used from one host to another. Again, you might not want everything the same. But rsync is quite fast since it only transfers differences. Annelise To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 18:27:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA25025 for freebsd-current-outgoing; Mon, 18 Jan 1999 18:27:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from top.worldcontrol.com (snblitz.sc.scruznet.com [165.227.132.84]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA25020 for ; Mon, 18 Jan 1999 18:27:22 -0800 (PST) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 15583 invoked by uid 100); 19 Jan 1999 02:27:18 -0000 Date: Mon, 18 Jan 1999 18:27:18 -0800 To: freebsd-current@FreeBSD.ORG Subject: linuxthreads, gimp 1.1+, dies Message-ID: <19990118182717.A15566@top.worldcontrol.com> Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I running gimp -unstable (CVS 1/17/1998) and FreeBSD -current (1/17/1998) with CFLAGS= -O2 -m486 -pipe -DCOMPAT_LINUX_THREADS -DVM_STACK COPTFLAGS= -O -pipe -DCOMPAT_LINUX_THREADS -DVM_STACK and linuxthreads port from http://lt.tar.com. recompiled glib, gtk+ and gimp which works fine reasonably well without threads. with threads CFLAGS="-D_THREAD_SAFE -I/usr/local/include -L/usr/local/lib -O2 -m486 -pipe -lpthread" Everything compiles and it runs. However, various operations crash for example: starting tile preswapper /usr/local/bin/gimp fatal error: sigsegv caught /usr/local/bin/gimp (pid:15557): [E]xit, [H]alt, show [S]tack trace or [P]roceed: S #0 0x282a0326 in g_on_error_stack_trace ( #1 0x282a0254 in g_on_error_query (prg_name=0xefbfdb40 "/usr/local/bin/gimp") #2 0x808b867 in fatal_error () #3 0x80cef0a in on_signal () #4 #5 0x8100a33 in tile_idle_thread () #6 0x28155ea1 in pthread_start_thread (arg=0xeb7ffd08) #7 0x2815650d in _clone () at clone.S:1 #8 0x7202c in ?? () #9 0x1 in ?? () -- Brian Litzinger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 19:04:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA29749 for freebsd-current-outgoing; Mon, 18 Jan 1999 19:04:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA29740 for ; Mon, 18 Jan 1999 19:04:47 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id WAA12039; Mon, 18 Jan 1999 22:04:43 -0500 (EST) Date: Mon, 18 Jan 1999 22:04:43 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: brian@worldcontrol.com cc: freebsd-current@FreeBSD.ORG Subject: Re: linuxthreads, gimp 1.1+, dies In-Reply-To: <19990118182717.A15566@top.worldcontrol.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 18 Jan 1999 brian@worldcontrol.com wrote: > I running gimp -unstable (CVS 1/17/1998) and FreeBSD -current > (1/17/1998) with > > CFLAGS= -O2 -m486 -pipe -DCOMPAT_LINUX_THREADS -DVM_STACK > COPTFLAGS= -O -pipe -DCOMPAT_LINUX_THREADS -DVM_STACK > > and linuxthreads port from http://lt.tar.com. > > recompiled glib, gtk+ and gimp which works fine reasonably > well without threads. > > with threads > CFLAGS="-D_THREAD_SAFE -I/usr/local/include -L/usr/local/lib -O2 -m486 -pipe -lpthread" Where's -g? > > Everything compiles and it runs. However, various operations crash > for example: > > starting tile preswapper > /usr/local/bin/gimp fatal error: sigsegv caught > /usr/local/bin/gimp (pid:15557): [E]xit, [H]alt, show [S]tack trace or [P]roceed: > S > #0 0x282a0326 in g_on_error_stack_trace ( > #1 0x282a0254 in g_on_error_query (prg_name=0xefbfdb40 "/usr/local/bin/gimp") > #2 0x808b867 in fatal_error () > #3 0x80cef0a in on_signal () > #4 > #5 0x8100a33 in tile_idle_thread () > #6 0x28155ea1 in pthread_start_thread (arg=0xeb7ffd08) > #7 0x2815650d in _clone () at clone.S:1 > #8 0x7202c in ?? () > #9 0x1 in ?? () > Try compiling with debugging info, get a coredump, and debug with the binary that has the full debugging symbols. > > -- > Brian Litzinger > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 19:34:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA03251 for freebsd-current-outgoing; Mon, 18 Jan 1999 19:34:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA03239 for ; Mon, 18 Jan 1999 19:34:32 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id EAA04934 for current@FreeBSD.ORG; Tue, 19 Jan 1999 04:34:10 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id D3AC91574; Tue, 19 Jan 1999 03:20:44 +0100 (CET) Date: Tue, 19 Jan 1999 03:20:44 +0100 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: The removal of MT_RTABLE Message-ID: <19990119032044.A7159@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from paul@originative.co.uk on Mon, Jan 18, 1999 at 12:40:26PM -0000 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4994 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to paul@originative.co.uk: > The removal of MT_RTABLE by fenner in rev 1.32 of /sys/sys/mbuf.h has > broken the build of the tree in netstat. It may have broken other net > apps that I haven't hit yet. Already fixed. If you're not subscribed to cvs-all, please do... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #69: Mon Jan 18 02:02:12 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 19:35:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA03509 for freebsd-current-outgoing; Mon, 18 Jan 1999 19:35:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA03492 for ; Mon, 18 Jan 1999 19:35:03 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id EAA04938 for freebsd-current@FreeBSD.ORG; Tue, 19 Jan 1999 04:34:44 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 4D67F1574; Tue, 19 Jan 1999 03:21:38 +0100 (CET) Date: Tue, 19 Jan 1999 03:21:38 +0100 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: Build Errors in -current Message-ID: <19990119032138.B7159@keltia.freenix.fr> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Annelise Anderson on Mon, Jan 18, 1999 at 12:38:11AM -0800 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4994 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Annelise Anderson: > But I still got an error much later with texinfo, so apparently > this is only partly fixed. Weird. After fixing netstat, my "make buildworld" succeeded w/o any problem... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #69: Mon Jan 18 02:02:12 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 20:03:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA05909 for freebsd-current-outgoing; Mon, 18 Jan 1999 20:03:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA05904 for ; Mon, 18 Jan 1999 20:03:24 -0800 (PST) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id UAA07357 for ; Mon, 18 Jan 1999 20:54:55 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp02.primenet.com, id smtpd007263; Mon Jan 18 20:54:49 1999 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id UAA04699 for FreeBSD-Current@FreeBSD.ORG; Mon, 18 Jan 1999 20:54:39 -0700 (MST) From: Terry Lambert Message-Id: <199901190354.UAA04699@usr04.primenet.com> Subject: Re: FrontPage Extensions To: FreeBSD-Current@FreeBSD.ORG Date: Tue, 19 Jan 1999 03:54:33 +0000 (GMT) In-Reply-To: <00ea01be374a$b11fa020$1acb2e9c@westbend.net> from "Scot W. Hetzel" at Jan 3, 99 12:35:35 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For what it's worth, the FP security issues are very well documented by ReadyToRun Software's site (these are the folks who do the UNIX ports for Microsoft). They also keep both BSDI 2.1 and 3.0 binaries available, and they know about FreeBSD (it's mentioned in the FAQ as an unsupported platform; apparently someone was having problems with the MD5 password hashing. Someone who cares should send them mail on how to update their FAQ to be more correct, and to raise FreeBSD's visibility as a platform -- e.g. what versions to us4e for what, install instructions for FreeBSD, etc.). Here is the source code to mod_frontpage and fpexe: http://www.rtr.com/fpsupport/SERK/a_modfp.htm http://www.rtr.com/fpsupport/SERK/a_fpexe.htm Here's Microsoft's take on the security issues: http://www.rtr.com/fpsupport/SERK/security.htm Pretty much, using the source code provided, you could add FP extensions to any web server for which you had source. One caveat is that the FrontPage client (stupidly) will refuse to create "sub webs" unless the server type is "netscape" or "apache-fp", so I guess it's back to lying about what your server is if it isn't one of those; sorry, JAVA-teers... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 20:16:52 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA07553 for freebsd-current-outgoing; Mon, 18 Jan 1999 20:16:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA07541 for ; Mon, 18 Jan 1999 20:16:50 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id VAA05677; Mon, 18 Jan 1999 21:16:40 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199901190416.VAA05677@panzer.plutotech.com> Subject: Re: aic (adaptec 152x) still not supported in -current? In-Reply-To: <8767a4e5lw.fsf@muon.xs4all.nl> from Peter Mutsaers at "Jan 18, 99 08:35:55 pm" To: plm@xs4all.nl (Peter Mutsaers) Date: Mon, 18 Jan 1999 21:16:40 -0700 (MST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Mutsaers wrote... > Hello, > > When CAM was integrated someone reported that the aic driver was not > ready yet for CAM, but that "Brian Beattie is > working on it". Right. > At the moment, looking in LINT, it looks like aic still isn't > supported. Is that true? Does anyone know whether it will be? It's true that it isn't supported yet. We are planning on supporting it. Brian Beattie is the one working on it, you should probably ask him how it is coming along. I have no idea when support will appear. If you want SCSI support any time soon, I would suggest getting a supported card. An ISA Advansys card might be a good, cheap substitute for your 6360/6260 board. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 21:10:59 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15200 for freebsd-current-outgoing; Mon, 18 Jan 1999 21:10:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chandra.eatell.msr.prug.or.jp ([202.247.4.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA15195 for ; Mon, 18 Jan 1999 21:10:57 -0800 (PST) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id OAA06814 for ; Tue, 19 Jan 1999 14:09:45 +0900 (JST) Message-Id: <199901190509.OAA06814@chandra.eatell.msr.prug.or.jp> To: current@FreeBSD.ORG Subject: Re: RELNOTES.TXT In-reply-to: Your message of "Mon, 18 Jan 1999 12:16:11 PST." Date: Tue, 19 Jan 1999 14:09:44 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As far as I know, I don't think the 2920 is supported since it's not a > standard adaptec card (it was bought from another company) Old 2920, AHA-2920A is using Future Domain chip. Newer 2920, AHA-2920C? is using adaptec chip. But I don't test yet. And, 2910 is using adaptec chip, too. This card has not boot-ROM. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 21:45:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA19202 for freebsd-current-outgoing; Mon, 18 Jan 1999 21:45:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA19197 for ; Mon, 18 Jan 1999 21:45:09 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id WAA06318; Mon, 18 Jan 1999 22:44:58 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199901190544.WAA06318@panzer.plutotech.com> Subject: Re: RELNOTES.TXT In-Reply-To: from Ken Krebs at "Jan 18, 99 12:16:11 pm" To: schrade@schrade.com (Ken Krebs) Date: Mon, 18 Jan 1999 22:44:58 -0700 (MST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ken Krebs wrote... > > In /usr/src/release/texts/RELNOTES.TXT it lists the following for > supported adaptec controllers: > > Adaptec 1535 ISA SCSI controllers > Adaptec 154x series ISA SCSI controllers > Adaptec 174x series EISA SCSI controller in standard and enhanced mode. > Adaptec 274X/284X/2920/2940/2950/3940/3950 (Narrow/Wide/Twin) series > ^^^^ > EISA/VLB/PCI SCSI controllers. > Adaptec AIC7850, AIC7880, AIC789x, on-board SCSI controllers. > > > As far as I know, I don't think the 2920 is supported since it's not a > standard adaptec card (it was bought from another company) The 2920 is a rebadged Future Domain card, and you're right, it isn't supported. The 2920C, on the other hand, has an Adaptec 7855 on board and it is supported. The release notes should probably be qualified. > If I'm wrong, I'd be really pleased since we've been trying to get one of > these cards to be supported in FreeBSD 3.0-current. > > But if I'm right, it should be removed because it's sure to piss people > off :) It should be qualified. > The last known source for the old patches to get this card working are at > the following URL: > > http://www.sbox.tu-graz.ac.at/home/r/rmike/freebsd/welcome.html > > They, of course, don't work with CAM. Yep. -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 21:50:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA19793 for freebsd-current-outgoing; Mon, 18 Jan 1999 21:50:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA19787 for ; Mon, 18 Jan 1999 21:50:24 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.8.6/8.8.6) with ESMTP id GAA14222 for ; Tue, 19 Jan 1999 06:50:16 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.2/8.9.2) id GAA01519 for current@FreeBSD.ORG; Tue, 19 Jan 1999 06:48:56 +0100 (CET) (envelope-from andreas) Date: Tue, 19 Jan 1999 06:48:56 +0100 From: Andreas Klemm To: current@FreeBSD.ORG Subject: make release produces unbootable boot floppies, no boot loader, no /kernel Message-ID: <19990119064856.A991@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ! Bad news, make release still produces non bootable floppies. I cvsupped yesterday evening at 8pm and did a make world and make release .... Now I tried the boot.flp image from the ftp subdir in /R/.... First error message No /boot/loader Then the typical "boot banner" 2nd error message No /kernel When typing ? . .. kernel.gz When typing kernel.gz to load this kernel invalid format Well, there is _still_ something wron, believe me. Andreas /// -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 21:56:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA20381 for freebsd-current-outgoing; Mon, 18 Jan 1999 21:56:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles139.castles.com [208.214.165.139]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA20376 for ; Mon, 18 Jan 1999 21:56:06 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id VAA01750; Mon, 18 Jan 1999 21:52:26 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901190552.VAA01750@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andreas Klemm cc: current@FreeBSD.ORG Subject: Re: make release produces unbootable boot floppies, no boot loader, no /kernel In-reply-to: Your message of "Tue, 19 Jan 1999 06:48:56 +0100." <19990119064856.A991@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 Jan 1999 21:52:26 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi ! Bad news, make release still produces non bootable floppies. > I cvsupped yesterday evening at 8pm and did a make world and > make release .... > > Now I tried the boot.flp image from the ftp subdir in /R/.... > > First error message > No /boot/loader > Then the typical "boot banner" > 2nd error message > No /kernel > When typing ? > . .. kernel.gz > When typing kernel.gz to load this kernel > invalid format Of course, it's gzipped. > Well, there is _still_ something wron, believe me. The single-floppy install is broken. Use the two-floppy install as I've been encouraging people to do now since the 12th. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 22:00:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA21079 for freebsd-current-outgoing; Mon, 18 Jan 1999 22:00:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from send105.yahoomail.com (send105.yahoomail.com [205.180.60.128]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA21074 for ; Mon, 18 Jan 1999 22:00:03 -0800 (PST) (envelope-from ixkatl@yahoo.com) Message-ID: <19990119060002.27133.rocketmail@send105.yahoomail.com> Received: from [207.172.144.152] by send105.yahoomail.com; Mon, 18 Jan 1999 22:00:02 PST Date: Mon, 18 Jan 1999 22:00:02 -0800 (PST) From: Andrew Sherrod Subject: Re: Disk Geometry Patch. Could someone test this on -current. To: current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="0-1789366143-916725602=:16744" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --0-1789366143-916725602=:16744 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline As I now have upgraded at last, I tested the 3.0 version of the patch. It does appear to make the system recognize the proper disk geometry where the standard wd.c does not report the proper size. Attached is the diff and 2 dmesgs, before and after. (Sorry for the length of the dmesg, haven't compeltely configured the kernel yet.) Any thoughts on the patch? Andrew Sherrod ---Andrew Sherrod wrote: > > I have found several people using IDE disks on newer Award BIOSes have trouble getting the boot-time probes and installation routines to recognize the correct disk geometry. > > If anyone is running 3.0 (or 2.2.x) on a machine with Award BIOS using IDE drives with LBA turned off in the kernel configuration, and if you have trouble getting dmesg/boot probes to recognize the proper disk size, could you test the attached patch for me? > > I would also like to find testers with ANY BIOS that reports a disk size too small. I think my patch will correct most problems with IDE geometry showing as smaller than it actually is. (I don't make any claims about geometries being reported as too large, or SCSI disks...) > > Thanks to anyone who can help. > > Andrew Sherrod > > P.S. I know this is not a really big problem, but it always seemed a bit insulting that FreeBSD had to rely on DOS boot sectors to get the correct disk geometry. I would rather that we could identify the correct geometry without having to rely on another OS. > > And, face it, for newbies and those not terribly computer literate, getting the right geometry during installation is a very nice feature. It is rather disheartening for a new-comer to find out that their new operating system can't even identify the correct disk geometry. > > > > > _________________________________________________________ > DO YOU YAHOO!? > Get your free @yahoo.com address at http://mail.yahoo.com > > > ------------------------------------------------- > PR: i386/9431 > ------------------------------------------------- > > ------------------------------------------------- > Patch for 2.2.8 (May also workfor 2.2.6/2.2.7) > ------------------------------------------------- > > *** wd.c.2_2_8 Wed Jan 13 21:07:30 1999 > --- wd.c.original.2_2_8 Wed Jan 13 21:08:24 1999 > *************** > *** 113,122 **** > #define WDOPT_FORCEHD(x) (((x)&0x0f00)>>8) > #define WDOPT_MULTIMASK 0x00ff > > - /* This bit mask is used to determine if the drive supports LBA addressing. */ > - > - #define WDCAP_LBA 0x02 > - > /* > * This biotab field doubles as a field for the physical unit number on > * the controller. > --- 113,118 ---- > *************** > *** 1731,1745 **** > du->dk_dd.d_nsectors = wp->wdp_sectors; > du->dk_dd.d_secpercyl = du->dk_dd.d_ntracks * du->dk_dd.d_nsectors; > du->dk_dd.d_secperunit = du->dk_dd.d_secpercyl * du->dk_dd.d_ncylinders; > ! > ! /* Check for BIOS LBA flag. This should allow kernel to determine > ! actual disk geometry for diffiuclt BIOSes. > ! This will likely only be of use during initial installation, or > ! perhaps when configuring a new drive. Otherwise, the disk geometry > ! should already be known. -A. Sherrod 01/13/1999*/ > ! > ! if ( ( (wp->wdp_capability&WDCAP_LBA) || > ! (wp->wdp_cylinders == 16383 ) ) && > du->dk_dd.d_secperunit < wp->wdp_lbasize) { > du->dk_dd.d_secperunit = wp->wdp_lbasize; > du->dk_dd.d_ncylinders = > --- 1727,1733 ---- > du->dk_dd.d_nsectors = wp->wdp_sectors; > du->dk_dd.d_secpercyl = du->dk_dd.d_ntracks * du->dk_dd.d_nsectors; > du->dk_dd.d_secperunit = du->dk_dd.d_secpercyl * du->dk_dd.d_ncylinders; > ! if (wp->wdp_cylinders == 16383 && > du->dk_dd.d_secperunit < wp->wdp_lbasize) { > du->dk_dd.d_secperunit = wp->wdp_lbasize; > du->dk_dd.d_ncylinders = > > ------------------------------------------------- > Patch for 3.0 > ------------------------------------------------- > > *** wd.c.3_0 Wed Jan 13 12:07:46 1999 > --- wd.c.original.3_0 Wed Jan 13 11:17:54 1999 > *************** > *** 130,140 **** > */ > #define id_physid id_scsiid > > - /* This bitmask is used to determine if the BIOS flags showing LBA support > - are active or inactive */ > - > - #define WDCAP_LBA 0x02 > - > /* > * Drive states. Used to initialize drive. > */ > --- 130,135 ---- > *************** > *** 1954,1973 **** > du->dk_dd.d_ntracks * du->dk_dd.d_nsectors; > du->dk_dd.d_secperunit = > du->dk_dd.d_secpercyl * du->dk_dd.d_ncylinders; > ! > ! /* If BIOS specifies LBA mode is supported, but LBA flags > ! are not set, check if wdp_lbasize is larger than > ! CHS size. If so, use the lba_size. > ! This should fix problems with certain BIOSes (e.g. Award) > ! which do not report the correct size when using only > ! CHS calculations. > ! This will not force the use of LBA mode. It is only > ! used to determine disk geometry. > ! > ! -A. Sherrod 01/13/1999 */ > ! > ! if ( ( (wp->wdp_capabilities & WDCAP_LBA) || > ! (wp->wdp_cylinders == 16383) ) && > du->dk_dd.d_secperunit < wp->wdp_lbasize) { > du->dk_dd.d_secperunit = wp->wdp_lbasize; > du->dk_dd.d_ncylinders = > --- 1949,1955 ---- > du->dk_dd.d_ntracks * du->dk_dd.d_nsectors; > du->dk_dd.d_secperunit = > du->dk_dd.d_secpercyl * du->dk_dd.d_ncylinders; > ! if (wp->wdp_cylinders == 16383 && > du->dk_dd.d_secperunit < wp->wdp_lbasize) { > du->dk_dd.d_secperunit = wp->wdp_lbasize; > du->dk_dd.d_ncylinders = > > ------------------------------------------------- > dmesg from 2.2.8 system before patch > ------------------------------------------------- > > > Copyright (c) 1992-1998 FreeBSD Inc. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > > FreeBSD 2.2.8-RELEASE #6: Wed Jan 13 21:11:20 EST 1999 > root@HAL9000.yaldabaoth.com:/usr/src/sys/compile/HAL > CPU: AMD-K6(tm) 3D processor (350.80-MHz 586-class CPU) > Origin = "AuthenticAMD" Id = 0x580 Stepping=0 > Features=0x8001bf > real memory = 201326592 (196608K bytes) > avail memory = 194924544 (190356K bytes) > Probing for devices on PCI bus 0: > chip0 rev 4 on pci0:0:0 > chip1 rev 0 on pci0:1:0 > chip2 rev 65 on pci0:7:0 > pci0:7:1: VIA Technologies, device=0x0571, class=storage (ide) [no driver assigned] > chip3 rev 16 on pci0:7:3 > xl0 <3Com 3c905B Fast Etherlink XL 10/100BaseTX> rev 48 int a irq 11 on pci0:10:0 > xl0: Ethernet address: 00:10:5a:20:9b:68 > xl0: autoneg not complete, no carrier (forcing half-duplex, 10Mbps) > Probing for devices on PCI bus 1: > Probing for devices on the ISA bus: > sc0 at 0x60-0x6f irq 1 on motherboard > sc0: VGA color <16 virtual consoles, flags=0x0> > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0 at 0x3f8-0x3ff irq 4 on isa > sio0: type 8250 > sio1 at 0x2f8-0x2ff irq 3 on isa > sio1: type 16550A > lpt0 at 0x378-0x37f irq 7 on isa > lpt0: Interrupt-driven port > lp0: TCP/IP capable interface > psm0 at 0x60-0x64 irq 12 on motherboard > psm0: model Generic PS/2 mouse, device ID 0 > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > fdc0: FIFO enabled, 8 bytes threshold > fd0: 1.44MB 3.5in > wdc0 at 0x1f0-0x1f7 irq 14 on isa > wdc0: unit 0 (wd0): > wd0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S > wdc0: unit 1 (wd1): > wd1: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S > wdc1 at 0x170-0x177 irq 15 on isa > wdc1: unit 0 (wd2): > wd2: 1888MB (3866940 sectors), 4092 cyls, 15 heads, 63 S/T, 512 B/S > wdc1: unit 1 (atapi): , removable, intr, dma, iordis > wcd0: 5512KB/sec, 256KB cache, audio play, 255 volume levels, ejectable tray > wcd0: no disc inside, unlocked > mcd0 not found at 0x300 > npx0 flags 0x1 on motherboard > npx0: INT 16 interface > > ------------------------------------------------- > dmesg from 2.2.8 system after patch > ------------------------------------------------- > > > Copyright (c) 1992-1998 FreeBSD Inc. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > > FreeBSD 2.2.8-RELEASE #7: Wed Jan 13 21:26:09 EST 1999 > root@HAL9000.yaldabaoth.com:/usr/src/sys/compile/HAL > CPU: AMD-K6(tm) 3D processor (350.80-MHz 586-class CPU) > Origin = "AuthenticAMD" Id = 0x580 Stepping=0 > Features=0x8001bf > real memory = 201326592 (196608K bytes) > avail memory = 194924544 (190356K bytes) > Probing for devices on PCI bus 0: > chip0 rev 4 on pci0:0:0 > chip1 rev 0 on pci0:1:0 > chip2 rev 65 on pci0:7:0 > pci0:7:1: VIA Technologies, device=0x0571, class=storage (ide) [no driver assigned] > chip3 rev 16 on pci0:7:3 > xl0 <3Com 3c905B Fast Etherlink XL 10/100BaseTX> rev 48 int a irq 11 on pci0:10:0 > xl0: Ethernet address: 00:10:5a:20:9b:68 > xl0: autoneg not complete, no carrier (forcing half-duplex, 10Mbps) > Probing for devices on PCI bus 1: > Probing for devices on the ISA bus: > sc0 at 0x60-0x6f irq 1 on motherboard > sc0: VGA color <16 virtual consoles, flags=0x0> > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0 at 0x3f8-0x3ff irq 4 on isa > sio0: type 8250 > sio1 at 0x2f8-0x2ff irq 3 on isa > sio1: type 16550A > lpt0 at 0x378-0x37f irq 7 on isa > lpt0: Interrupt-driven port > lp0: TCP/IP capable interface > psm0 at 0x60-0x64 irq 12 on motherboard > psm0: model Generic PS/2 mouse, device ID 0 > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > fdc0: FIFO enabled, 8 bytes threshold > fd0: 1.44MB 3.5in > wdc0 at 0x1f0-0x1f7 irq 14 on isa > wdc0: unit 0 (wd0): > wd0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S > wdc0: unit 1 (wd1): > wd1: 3020MB (6185088 sectors), 6136 cyls, 16 heads, 63 S/T, 512 B/S > wdc1 at 0x170-0x177 irq 15 on isa > wdc1: unit 0 (wd2): > wd2: 4120MB (8439184 sectors), 8930 cyls, 15 heads, 63 S/T, 512 B/S > wdc1: unit 1 (atapi): , removable, intr, dma, iordis > wcd0: 5512KB/sec, 256KB cache, audio play, 255 volume levels, ejectable tray > wcd0: no disc inside, unlocked > mcd0 not found at 0x300 > npx0 flags 0x1 on motherboard > npx0: INT 16 interface > _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com --0-1789366143-916725602=:16744 Content-Type: text/plain; name="adiff1.txt" Content-Transfer-Encoding: base64 Content-Description: adiff1.txt Content-Disposition: attachment; filename="adiff1.txt" --0-1789366143-916725602=:16744 Content-Type: text/plain; name="admesg1.txt" Content-Description: admesg1.txt Content-Disposition: inline; filename="admesg1.txt" Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-RELEASE #11: Mon Jan 18 19:53:18 EST 1999 root@HAL9000.no_net.none:/usr/src/sys/compile/HAL_NEW Timecounter "i8254" frequency 1193182 Hz cost 3863 ns CPU: AMD-K6(tm) 3D processor (350.80-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x580 Stepping=0 Features=0x8001bf real memory = 201326592 (196608K bytes) avail memory = 192839680 (188320K bytes) Probing for devices on PCI bus 0: chip0: rev 0x04 on pci0.0.0 chip1: rev 0x00 on pci0.1.0 chip2: rev 0x41 on pci0.7.0 ide_pci0: rev 0x06 on pci0.7.1 chip3: rev 0x10 on pci0.7.3 xl0: <3Com 3c905B Fast Etherlink XL 10/100BaseTX> rev 0x30 int a irq 11 on pci0.10.0 xl0: Ethernet address: 00:10:5a:20:9b:68 xl0: autoneg not complete, no carrier (forcing half-duplex, 10Mbps) Probing for devices on PCI bus 1: Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x280 fe0 not found at 0x300 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 8250 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): wd1: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (wd2): wd2: 1888MB (3866940 sectors), 4092 cyls, 15 heads, 63 S/T, 512 B/S wdc1: unit 1 (atapi): , removable, intr, dma, iordis wcd0: 5512Kb/sec, 256Kb cache, audio play, 255 volume levels, ejectable tray wcd0: no disc inside, unlocked wt0 not found at 0x300 mcd0 not found at 0x300 matcdc0 not found at 0x230 scd0 not found at 0x230 ie0: unknown board_id: f000 ie0 not found at 0x300 ep0 not found at 0x300 ex0 not found le0 not found at 0x300 lnc0 not found at 0x280 ze0 not found at 0x300 zp0 not found at 0x300 cs0 not found at 0x300 adv0 not found at 0x330 bt0 not found at 0x134 aha0 not found at 0x134 npx0 on motherboard npx0: INT 16 interface changing root device to wd0s1a fd0c: hard error writing fsbn 1 of 1-3 (No status) fd0c: hard error writing fsbn 761 (No status) fd0c: hard error writing fsbn 10 of 10-12 (No status) fd0c: hard error writing fsbn 22 (No status) --0-1789366143-916725602=:16744 Content-Type: text/plain; name="admesg2.txt" Content-Description: admesg2.txt Content-Disposition: inline; filename="admesg2.txt" Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-RELEASE #10: Mon Jan 18 19:47:08 EST 1999 root@HAL9000.no_net.none:/usr/src/sys/compile/HAL_NEW Timecounter "i8254" frequency 1193182 Hz cost 3863 ns CPU: AMD-K6(tm) 3D processor (350.80-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x580 Stepping=0 Features=0x8001bf real memory = 201326592 (196608K bytes) avail memory = 192839680 (188320K bytes) Probing for devices on PCI bus 0: chip0: rev 0x04 on pci0.0.0 chip1: rev 0x00 on pci0.1.0 chip2: rev 0x41 on pci0.7.0 ide_pci0: rev 0x06 on pci0.7.1 chip3: rev 0x10 on pci0.7.3 xl0: <3Com 3c905B Fast Etherlink XL 10/100BaseTX> rev 0x30 int a irq 11 on pci0.10.0 xl0: Ethernet address: 00:10:5a:20:9b:68 xl0: autoneg not complete, no carrier (forcing half-duplex, 10Mbps) Probing for devices on PCI bus 1: Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x280 fe0 not found at 0x300 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 8250 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S Using A. Sherrod's patch of 01/18/1999. wdc0: unit 1 (wd1): wd1: 3020MB (6185088 sectors), 6136 cyls, 16 heads, 63 S/T, 512 B/S Using A. Sherrod's patch of 01/18/1999. wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (wd2): wd2: 4120MB (8439184 sectors), 8930 cyls, 15 heads, 63 S/T, 512 B/S Using A. Sherrod's patch of 01/18/1999. wdc1: unit 1 (atapi): , removable, intr, dma, iordis wcd0: 5512Kb/sec, 256Kb cache, audio play, 255 volume levels, ejectable tray wcd0: no disc inside, unlocked wt0 not found at 0x300 mcd0 not found at 0x300 matcdc0 not found at 0x230 scd0 not found at 0x230 ie0: unknown board_id: f000 ie0 not found at 0x300 ep0 not found at 0x300 ex0 not found le0 not found at 0x300 lnc0 not found at 0x280 ze0 not found at 0x300 zp0 not found at 0x300 cs0 not found at 0x300 adv0 not found at 0x330 bt0 not found at 0x134 aha0 not found at 0x134 npx0 on motherboard npx0: INT 16 interface changing root device to wd0s1a --0-1789366143-916725602=:16744-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 22:02:59 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA21227 for freebsd-current-outgoing; Mon, 18 Jan 1999 22:02:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from send102.yahoomail.com (send102.yahoomail.com [205.180.60.90]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA21219 for ; Mon, 18 Jan 1999 22:02:55 -0800 (PST) (envelope-from ixkatl@yahoo.com) Message-ID: <19990119060441.24783.rocketmail@send102.yahoomail.com> Received: from [207.172.144.152] by send102.yahoomail.com; Mon, 18 Jan 1999 22:04:41 PST Date: Mon, 18 Jan 1999 22:04:41 -0800 (PST) From: Andrew Sherrod Subject: Re: Disk Geometry Patch. Could someone test this on -current. To: current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="0-424238335-916725881=:22614" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --0-424238335-916725881=:22614 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Appears the diff didn't get attached. Here it is. Sorry! ---Andrew Sherrod wrote: > > > As I now have upgraded at last, I tested the 3.0 > version of the patch. It does appear to make the > system recognize the proper disk geometry where the > standard wd.c does not report the proper size. > Attached is the diff and 2 dmesgs, before and after. > > (Sorry for the length of the dmesg, haven't compeltely > configured the kernel yet.) > > Any thoughts on the patch? > > Andrew Sherrod > > > > ---Andrew Sherrod wrote: > > > > I have found several people using IDE disks on newer Award BIOSes have trouble getting the boot-time probes and installation routines to recognize the correct disk geometry. > > > > If anyone is running 3.0 (or 2.2.x) on a machine with Award BIOS using IDE drives with LBA turned off in the kernel configuration, and if you have trouble getting dmesg/boot probes to recognize the proper disk size, could you test the attached patch for me? > > > > I would also like to find testers with ANY BIOS that reports a disk size too small. I think my patch will correct most problems with IDE geometry showing as smaller than it actually is. (I don't make any claims about geometries being reported as too large, or SCSI disks...) > > > > Thanks to anyone who can help. > > > > Andrew Sherrod > > > > P.S. I know this is not a really big problem, but it always seemed a bit insulting that FreeBSD had to rely on DOS boot sectors to get the correct disk geometry. I would rather that we could identify the correct geometry without having to rely on another OS. > > > > And, face it, for newbies and those not terribly computer literate, getting the right geometry during installation is a very nice feature. It is rather disheartening for a new-comer to find out that their new operating system can't even identify the correct disk geometry. > > > > > > > > > > _________________________________________________________ > > DO YOU YAHOO!? > > Get your free @yahoo.com address at http://mail.yahoo.com > > > > > ------------------------------------------------- > > PR: i386/9431 > > ------------------------------------------------- > > > > ------------------------------------------------- > > Patch for 2.2.8 (May also workfor 2.2.6/2.2.7) > > ------------------------------------------------- > > > > *** wd.c.2_2_8 Wed Jan 13 21:07:30 1999 > > --- wd.c.original.2_2_8 Wed Jan 13 21:08:24 1999 > > *************** > > *** 113,122 **** > > #define WDOPT_FORCEHD(x) (((x)&0x0f00)>>8) > > #define WDOPT_MULTIMASK 0x00ff > > > > - /* This bit mask is used to determine if the drive supports LBA addressing. */ > > - > > - #define WDCAP_LBA 0x02 > > - > > /* > > * This biotab field doubles as a field for the physical unit number on > > * the controller. > > --- 113,118 ---- > > *************** > > *** 1731,1745 **** > > du->dk_dd.d_nsectors = wp->wdp_sectors; > > du->dk_dd.d_secpercyl = du->dk_dd.d_ntracks * du->dk_dd.d_nsectors; > > du->dk_dd.d_secperunit = du->dk_dd.d_secpercyl * du->dk_dd.d_ncylinders; > > ! > > ! /* Check for BIOS LBA flag. This should allow kernel to determine > > ! actual disk geometry for diffiuclt BIOSes. > > ! This will likely only be of use during initial installation, or > > ! perhaps when configuring a new drive. Otherwise, the disk geometry > > ! should already be known. -A. Sherrod 01/13/1999*/ > > ! > > ! if ( ( (wp->wdp_capability&WDCAP_LBA) || > > ! (wp->wdp_cylinders == 16383 ) ) && > > du->dk_dd.d_secperunit < wp->wdp_lbasize) { > > du->dk_dd.d_secperunit = wp->wdp_lbasize; > > du->dk_dd.d_ncylinders = > > --- 1727,1733 ---- > > du->dk_dd.d_nsectors = wp->wdp_sectors; > > du->dk_dd.d_secpercyl = du->dk_dd.d_ntracks * du->dk_dd.d_nsectors; > > du->dk_dd.d_secperunit = du->dk_dd.d_secpercyl * du->dk_dd.d_ncylinders; > > ! if (wp->wdp_cylinders == 16383 && > > du->dk_dd.d_secperunit < wp->wdp_lbasize) { > > du->dk_dd.d_secperunit = wp->wdp_lbasize; > > du->dk_dd.d_ncylinders = > > > > ------------------------------------------------- > > Patch for 3.0 > > ------------------------------------------------- > > > > *** wd.c.3_0 Wed Jan 13 12:07:46 1999 > > --- wd.c.original.3_0 Wed Jan 13 11:17:54 1999 > > *************** > > *** 130,140 **** > > */ > > #define id_physid id_scsiid > > > > - /* This bitmask is used to determine if the BIOS flags showing LBA support > > - are active or inactive */ > > - > > - #define WDCAP_LBA 0x02 > > - > > /* > > * Drive states. Used to initialize drive. > > */ > > --- 130,135 ---- > > *************** > > *** 1954,1973 **** > > du->dk_dd.d_ntracks * du->dk_dd.d_nsectors; > > du->dk_dd.d_secperunit = > > du->dk_dd.d_secpercyl * du->dk_dd.d_ncylinders; > > ! > > ! /* If BIOS specifies LBA mode is supported, but LBA flags > > ! are not set, check if wdp_lbasize is larger than > > ! CHS size. If so, use the lba_size. > > ! This should fix problems with certain BIOSes (e.g. Award) > > ! which do not report the correct size when using only > > ! CHS calculations. > > ! This will not force the use of LBA mode. It is only > > ! used to determine disk geometry. > > ! > > ! -A. Sherrod 01/13/1999 */ > > ! > > ! if ( ( (wp->wdp_capabilities & WDCAP_LBA) || > > ! (wp->wdp_cylinders == 16383) ) && > > du->dk_dd.d_secperunit < wp->wdp_lbasize) { > > du->dk_dd.d_secperunit = wp->wdp_lbasize; > > du->dk_dd.d_ncylinders = > > --- 1949,1955 ---- > > du->dk_dd.d_ntracks * du->dk_dd.d_nsectors; > > du->dk_dd.d_secperunit = > > du->dk_dd.d_secpercyl * du->dk_dd.d_ncylinders; > > ! if (wp->wdp_cylinders == 16383 && > > du->dk_dd.d_secperunit < wp->wdp_lbasize) { > > du->dk_dd.d_secperunit = wp->wdp_lbasize; > > du->dk_dd.d_ncylinders = > > > > ------------------------------------------------- > > dmesg from 2.2.8 system before patch > > ------------------------------------------------- > > > > > > Copyright (c) 1992-1998 FreeBSD Inc. > > Copyright (c) 1982, 1986, 1989, 1991, 1993 > > The Regents of the University of California. All rights reserved. > > > > FreeBSD 2.2.8-RELEASE #6: Wed Jan 13 21:11:20 EST 1999 > > root@HAL9000.yaldabaoth.com:/usr/src/sys/compile/HAL > > CPU: AMD-K6(tm) 3D processor (350.80-MHz 586-class CPU) > > Origin = "AuthenticAMD" Id = 0x580 Stepping=0 > > Features=0x8001bf > > real memory = 201326592 (196608K bytes) > > avail memory = 194924544 (190356K bytes) > > Probing for devices on PCI bus 0: > > chip0 rev 4 on pci0:0:0 > > chip1 rev 0 on pci0:1:0 > > chip2 rev 65 on pci0:7:0 > > pci0:7:1: VIA Technologies, device=0x0571, class=storage (ide) [no driver assigned] > > chip3 rev 16 on pci0:7:3 > > xl0 <3Com 3c905B Fast Etherlink XL 10/100BaseTX> rev 48 int a irq 11 on pci0:10:0 > > xl0: Ethernet address: 00:10:5a:20:9b:68 > > xl0: autoneg not complete, no carrier (forcing half-duplex, 10Mbps) > > Probing for devices on PCI bus 1: > > Probing for devices on the ISA bus: > > sc0 at 0x60-0x6f irq 1 on motherboard > > sc0: VGA color <16 virtual consoles, flags=0x0> > > sio0: configured irq 4 not in bitmap of probed irqs 0 > > sio0 at 0x3f8-0x3ff irq 4 on isa > > sio0: type 8250 > > sio1 at 0x2f8-0x2ff irq 3 on isa > > sio1: type 16550A > > lpt0 at 0x378-0x37f irq 7 on isa > > lpt0: Interrupt-driven port > > lp0: TCP/IP capable interface > > psm0 at 0x60-0x64 irq 12 on motherboard > > psm0: model Generic PS/2 mouse, device ID 0 > > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > > fdc0: FIFO enabled, 8 bytes threshold > > fd0: 1.44MB 3.5in > > wdc0 at 0x1f0-0x1f7 irq 14 on isa > > wdc0: unit 0 (wd0): > > wd0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S > > wdc0: unit 1 (wd1): > > wd1: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S > > wdc1 at 0x170-0x177 irq 15 on isa > > wdc1: unit 0 (wd2): > > wd2: 1888MB (3866940 sectors), 4092 cyls, 15 heads, 63 S/T, 512 B/S > > wdc1: unit 1 (atapi): , removable, intr, dma, iordis > > wcd0: 5512KB/sec, 256KB cache, audio play, 255 volume levels, ejectable tray > > wcd0: no disc inside, unlocked > > mcd0 not found at 0x300 > > npx0 flags 0x1 on motherboard > > npx0: INT 16 interface > > > > ------------------------------------------------- > > dmesg from 2.2.8 system after patch > > ------------------------------------------------- > > > > > > Copyright (c) 1992-1998 FreeBSD Inc. > > Copyright (c) 1982, 1986, 1989, 1991, 1993 > > The Regents of the University of California. All rights reserved. > > > > FreeBSD 2.2.8-RELEASE #7: Wed Jan 13 21:26:09 EST 1999 > > root@HAL9000.yaldabaoth.com:/usr/src/sys/compile/HAL > > CPU: AMD-K6(tm) 3D processor (350.80-MHz 586-class CPU) > > Origin = "AuthenticAMD" Id = 0x580 Stepping=0 > > Features=0x8001bf > > real memory = 201326592 (196608K bytes) > > avail memory = 194924544 (190356K bytes) > > Probing for devices on PCI bus 0: > > chip0 rev 4 on pci0:0:0 > > chip1 rev 0 on pci0:1:0 > > chip2 rev 65 on pci0:7:0 > > pci0:7:1: VIA Technologies, device=0x0571, class=storage (ide) [no driver assigned] > > chip3 rev 16 on pci0:7:3 > > xl0 <3Com 3c905B Fast Etherlink XL 10/100BaseTX> rev 48 int a irq 11 on pci0:10:0 > > xl0: Ethernet address: 00:10:5a:20:9b:68 > > xl0: autoneg not complete, no carrier (forcing half-duplex, 10Mbps) > > Probing for devices on PCI bus 1: > > Probing for devices on the ISA bus: > > sc0 at 0x60-0x6f irq 1 on motherboard > > sc0: VGA color <16 virtual consoles, flags=0x0> > > sio0: configured irq 4 not in bitmap of probed irqs 0 > > sio0 at 0x3f8-0x3ff irq 4 on isa > > sio0: type 8250 > > sio1 at 0x2f8-0x2ff irq 3 on isa > > sio1: type 16550A > > lpt0 at 0x378-0x37f irq 7 on isa > > lpt0: Interrupt-driven port > > lp0: TCP/IP capable interface > > psm0 at 0x60-0x64 irq 12 on motherboard > > psm0: model Generic PS/2 mouse, device ID 0 > > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > > fdc0: FIFO enabled, 8 bytes threshold > > fd0: 1.44MB 3.5in > > wdc0 at 0x1f0-0x1f7 irq 14 on isa > > wdc0: unit 0 (wd0): > > wd0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S > > wdc0: unit 1 (wd1): > > wd1: 3020MB (6185088 sectors), 6136 cyls, 16 heads, 63 S/T, 512 B/S > > wdc1 at 0x170-0x177 irq 15 on isa > > wdc1: unit 0 (wd2): > > wd2: 4120MB (8439184 sectors), 8930 cyls, 15 heads, 63 S/T, 512 B/S > > wdc1: unit 1 (atapi): , removable, intr, dma, iordis > > wcd0: 5512KB/sec, 256KB cache, audio play, 255 volume levels, ejectable tray > > wcd0: no disc inside, unlocked > > mcd0 not found at 0x300 > > npx0 flags 0x1 on motherboard > > npx0: INT 16 interface > > > > _________________________________________________________ > DO YOU YAHOO!? > Get your free @yahoo.com address at http://mail.yahoo.com > > > > > Copyright (c) 1992-1998 FreeBSD Inc. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 3.0-RELEASE #11: Mon Jan 18 19:53:18 EST 1999 > root@HAL9000.no_net.none:/usr/src/sys/compile/HAL_NEW > Timecounter "i8254" frequency 1193182 Hz cost 3863 ns > CPU: AMD-K6(tm) 3D processor (350.80-MHz 586-class CPU) > Origin = "AuthenticAMD" Id = 0x580 Stepping=0 > Features=0x8001bf > real memory = 201326592 (196608K bytes) > avail memory = 192839680 (188320K bytes) > Probing for devices on PCI bus 0: > chip0: rev 0x04 on pci0.0.0 > chip1: rev 0x00 on pci0.1.0 > chip2: rev 0x41 on pci0.7.0 > ide_pci0: rev 0x06 on pci0.7.1 > chip3: rev 0x10 on pci0.7.3 > xl0: <3Com 3c905B Fast Etherlink XL 10/100BaseTX> rev 0x30 int a irq 11 on pci0.10.0 > xl0: Ethernet address: 00:10:5a:20:9b:68 > xl0: autoneg not complete, no carrier (forcing half-duplex, 10Mbps) > Probing for devices on PCI bus 1: > Probing for devices on the ISA bus: > sc0 at 0x60-0x6f irq 1 on motherboard > sc0: VGA color <16 virtual consoles, flags=0x0> > ed0 not found at 0x280 > fe0 not found at 0x300 > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa > sio0: type 8250 > sio1 at 0x2f8-0x2ff irq 3 on isa > sio1: type 16550A > lpt0 at 0x378-0x37f irq 7 on isa > lpt0: Interrupt-driven port > lp0: TCP/IP capable interface > psm0 at 0x60-0x64 irq 12 on motherboard > psm0: model Generic PS/2 mouse, device ID 0 > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > fdc0: FIFO enabled, 8 bytes threshold > fd0: 1.44MB 3.5in > wdc0 at 0x1f0-0x1f7 irq 14 on isa > wdc0: unit 0 (wd0): > wd0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S > wdc0: unit 1 (wd1): > wd1: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S > wdc1 at 0x170-0x177 irq 15 on isa > wdc1: unit 0 (wd2): > wd2: 1888MB (3866940 sectors), 4092 cyls, 15 heads, 63 S/T, 512 B/S > wdc1: unit 1 (atapi): , removable, intr, dma, iordis > wcd0: 5512Kb/sec, 256Kb cache, audio play, 255 volume levels, ejectable tray > wcd0: no disc inside, unlocked > wt0 not found at 0x300 > mcd0 not found at 0x300 > matcdc0 not found at 0x230 > scd0 not found at 0x230 > ie0: unknown board_id: f000 > ie0 not found at 0x300 > ep0 not found at 0x300 > ex0 not found > le0 not found at 0x300 > lnc0 not found at 0x280 > ze0 not found at 0x300 > zp0 not found at 0x300 > cs0 not found at 0x300 > adv0 not found at 0x330 > bt0 not found at 0x134 > aha0 not found at 0x134 > npx0 on motherboard > npx0: INT 16 interface > changing root device to wd0s1a > fd0c: hard error writing fsbn 1 of 1-3 (No status) > fd0c: hard error writing fsbn 761 (No status) > fd0c: hard error writing fsbn 10 of 10-12 (No status) > fd0c: hard error writing fsbn 22 (No status) > > > Copyright (c) 1992-1998 FreeBSD Inc. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 3.0-RELEASE #10: Mon Jan 18 19:47:08 EST 1999 > root@HAL9000.no_net.none:/usr/src/sys/compile/HAL_NEW > Timecounter "i8254" frequency 1193182 Hz cost 3863 ns > CPU: AMD-K6(tm) 3D processor (350.80-MHz 586-class CPU) > Origin = "AuthenticAMD" Id = 0x580 Stepping=0 > Features=0x8001bf > real memory = 201326592 (196608K bytes) > avail memory = 192839680 (188320K bytes) > Probing for devices on PCI bus 0: > chip0: rev 0x04 on pci0.0.0 > chip1: rev 0x00 on pci0.1.0 > chip2: rev 0x41 on pci0.7.0 > ide_pci0: rev 0x06 on pci0.7.1 > chip3: rev 0x10 on pci0.7.3 > xl0: <3Com 3c905B Fast Etherlink XL 10/100BaseTX> rev 0x30 int a irq 11 on pci0.10.0 > xl0: Ethernet address: 00:10:5a:20:9b:68 > xl0: autoneg not complete, no carrier (forcing half-duplex, 10Mbps) > Probing for devices on PCI bus 1: > Probing for devices on the ISA bus: > sc0 at 0x60-0x6f irq 1 on motherboard > sc0: VGA color <16 virtual consoles, flags=0x0> > ed0 not found at 0x280 > fe0 not found at 0x300 > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa > sio0: type 8250 > sio1 at 0x2f8-0x2ff irq 3 on isa > sio1: type 16550A > lpt0 at 0x378-0x37f irq 7 on isa > lpt0: Interrupt-driven port > lp0: TCP/IP capable interface > psm0 at 0x60-0x64 irq 12 on motherboard > psm0: model Generic PS/2 mouse, device ID 0 > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > fdc0: FIFO enabled, 8 bytes threshold > fd0: 1.44MB 3.5in > wdc0 at 0x1f0-0x1f7 irq 14 on isa > wdc0: unit 0 (wd0): > wd0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S > Using A. Sherrod's patch of 01/18/1999. > wdc0: unit 1 (wd1): > wd1: 3020MB (6185088 sectors), 6136 cyls, 16 heads, 63 S/T, 512 B/S > Using A. Sherrod's patch of 01/18/1999. > wdc1 at 0x170-0x177 irq 15 on isa > wdc1: unit 0 (wd2): > wd2: 4120MB (8439184 sectors), 8930 cyls, 15 heads, 63 S/T, 512 B/S > Using A. Sherrod's patch of 01/18/1999. > wdc1: unit 1 (atapi): , removable, intr, dma, iordis > wcd0: 5512Kb/sec, 256Kb cache, audio play, 255 volume levels, ejectable tray > wcd0: no disc inside, unlocked > wt0 not found at 0x300 > mcd0 not found at 0x300 > matcdc0 not found at 0x230 > scd0 not found at 0x230 > ie0: unknown board_id: f000 > ie0 not found at 0x300 > ep0 not found at 0x300 > ex0 not found > le0 not found at 0x300 > lnc0 not found at 0x280 > ze0 not found at 0x300 > zp0 not found at 0x300 > cs0 not found at 0x300 > adv0 not found at 0x330 > bt0 not found at 0x134 > aha0 not found at 0x134 > npx0 on motherboard > npx0: INT 16 interface > changing root device to wd0s1a > _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com --0-424238335-916725881=:22614 Content-Type: text/plain; name="adiff.txt" Content-Description: adiff.txt Content-Disposition: inline; filename="adiff.txt" *** wd.c Mon Jan 18 19:39:22 1999 --- wd.c.original Mon Jan 18 18:24:14 1999 *************** *** 120,131 **** #define WDOPT_MULTIMASK 0x00ff /* - * This define is used to determine if the drive is LBA capable - */ - - #define WDCAP_LBA 0x02 - - /* * This biotab field doubles as a field for the physical unit number on * the controller. */ --- 120,125 ---- *************** *** 516,523 **** du->dk_dd.d_nsectors, du->dk_dd.d_secsize); - printf("Using A. Sherrod's patch of 01/18/1999.\n"); - if (bootverbose) { wp = &du->dk_params; printf( "wd%d: ATA INQUIRE valid = %04x, " --- 510,515 ---- *************** *** 1940,1960 **** du->dk_dd.d_ntracks * du->dk_dd.d_nsectors; du->dk_dd.d_secperunit = du->dk_dd.d_secpercyl * du->dk_dd.d_ncylinders; ! ! /* ! * tThe following change determines if the disk ! * is LBA capable. If it is, and the lba size is ! * larger than the CHS size, use the LBA size. ! * This should allow certain difficult BIOSES ! * (eg. Award) which do not report the correct ! * CHS size to still give an accurate measure ! * of disk size,w ithout forcing the user to ! * enable LBA mode. ! * A. Sherrod (01/18/1999) ! */ ! ! if ( ( (wp->wdp_capability & WDCAP_LBA) || ! (wp->wdp_cylinders == 16383) ) && du->dk_dd.d_secperunit < wp->wdp_lbasize) { du->dk_dd.d_secperunit = wp->wdp_lbasize; du->dk_dd.d_ncylinders = --- 1932,1938 ---- du->dk_dd.d_ntracks * du->dk_dd.d_nsectors; du->dk_dd.d_secperunit = du->dk_dd.d_secpercyl * du->dk_dd.d_ncylinders; ! if (wp->wdp_cylinders == 16383 && du->dk_dd.d_secperunit < wp->wdp_lbasize) { du->dk_dd.d_secperunit = wp->wdp_lbasize; du->dk_dd.d_ncylinders = --0-424238335-916725881=:22614-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 22:15:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA22233 for freebsd-current-outgoing; Mon, 18 Jan 1999 22:15:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chandra.eatell.msr.prug.or.jp ([202.247.4.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA22227 for ; Mon, 18 Jan 1999 22:15:43 -0800 (PST) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id PAA06890; Tue, 19 Jan 1999 15:13:10 +0900 (JST) Message-Id: <199901190613.PAA06890@chandra.eatell.msr.prug.or.jp> To: "Kenneth D. Merry" cc: plm@xs4all.nl (Peter Mutsaers), freebsd-current@FreeBSD.ORG Subject: Re: aic (adaptec 152x) still not supported in -current? In-reply-to: Your message of "Mon, 18 Jan 1999 21:16:40 MST." <199901190416.VAA05677@panzer.plutotech.com> Date: Tue, 19 Jan 1999 15:13:09 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If you want SCSI support any time soon, I would suggest getting a supported > card. An ISA Advansys card might be a good, cheap substitute for your > 6360/6260 board. Adaptec SlimSCSI is major PC-Card SCSI-IF, it is based on aic6360. Now, aic not supported yet, so Note-PC user can't use any PC-Card SCSI-IF. In PAO, another PC-Card SCSI-IF supported, but these are 2.2-stable only, not yet CAMed. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 22:26:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA23169 for freebsd-current-outgoing; Mon, 18 Jan 1999 22:26:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA23158 for ; Mon, 18 Jan 1999 22:26:13 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.8.6/8.8.6) with ESMTP id HAA14738; Tue, 19 Jan 1999 07:25:54 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.2/8.9.2) id HAA02779; Tue, 19 Jan 1999 07:25:40 +0100 (CET) (envelope-from andreas) Date: Tue, 19 Jan 1999 07:25:40 +0100 From: Andreas Klemm To: Mike Smith Cc: Andreas Klemm , current@FreeBSD.ORG Subject: Re: make release produces unbootable boot floppies, no boot loader, no /kernel Message-ID: <19990119072540.A2761@titan.klemm.gtn.com> References: <19990119064856.A991@titan.klemm.gtn.com> <199901190552.VAA01750@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199901190552.VAA01750@dingo.cdrom.com>; from Mike Smith on Mon, Jan 18, 1999 at 09:52:26PM -0800 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 18, 1999 at 09:52:26PM -0800, Mike Smith wrote: > > Hi ! Bad news, make release still produces non bootable floppies. > > I cvsupped yesterday evening at 8pm and did a make world and > > make release .... > > > > Now I tried the boot.flp image from the ftp subdir in /R/.... > > > > First error message > > No /boot/loader > > Then the typical "boot banner" > > 2nd error message > > No /kernel > > When typing ? > > . .. kernel.gz > > When typing kernel.gz to load this kernel > > invalid format > > Of course, it's gzipped. > > > Well, there is _still_ something wron, believe me. > > The single-floppy install is broken. Use the two-floppy install as > I've been encouraging people to do now since the 12th. This sounds like booting/installing from CD-ROM is currently impossible as well ??? Andreas /// -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 22:34:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA23933 for freebsd-current-outgoing; Mon, 18 Jan 1999 22:34:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles139.castles.com [208.214.165.139]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA23928 for ; Mon, 18 Jan 1999 22:34:54 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id WAA01992; Mon, 18 Jan 1999 22:31:22 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901190631.WAA01992@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andreas Klemm cc: current@FreeBSD.ORG Subject: Re: make release produces unbootable boot floppies, no boot loader, no /kernel In-reply-to: Your message of "Tue, 19 Jan 1999 07:25:40 +0100." <19990119072540.A2761@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 Jan 1999 22:31:21 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, Jan 18, 1999 at 09:52:26PM -0800, Mike Smith wrote: > > > Hi ! Bad news, make release still produces non bootable floppies. > > > I cvsupped yesterday evening at 8pm and did a make world and > > > make release .... > > > > > > Now I tried the boot.flp image from the ftp subdir in /R/.... > > > > > > First error message > > > No /boot/loader > > > Then the typical "boot banner" > > > 2nd error message > > > No /kernel > > > When typing ? > > > . .. kernel.gz > > > When typing kernel.gz to load this kernel > > > invalid format > > > > Of course, it's gzipped. > > > > > Well, there is _still_ something wron, believe me. > > > > The single-floppy install is broken. Use the two-floppy install as > > I've been encouraging people to do now since the 12th. > > This sounds like booting/installing from CD-ROM is currently > impossible as well ??? That's correct. We're looking at having to move to a harddisk emulation mode to get this back on track. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 18 23:30:22 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA28890 for freebsd-current-outgoing; Mon, 18 Jan 1999 23:30:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA28872 for ; Mon, 18 Jan 1999 23:30:18 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 102Vbz-00014j-00; Tue, 19 Jan 1999 00:30:07 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id AAA55424; Tue, 19 Jan 1999 00:29:50 -0700 (MST) Message-Id: <199901190729.AAA55424@harmony.village.org> To: NAKAGAWA Yoshihisa Subject: Re: aic (adaptec 152x) still not supported in -current? Cc: "Kenneth D. Merry" , plm@xs4all.nl (Peter Mutsaers), freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 19 Jan 1999 15:13:09 +0900." <199901190613.PAA06890@chandra.eatell.msr.prug.or.jp> References: <199901190613.PAA06890@chandra.eatell.msr.prug.or.jp> Date: Tue, 19 Jan 1999 00:29:50 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199901190613.PAA06890@chandra.eatell.msr.prug.or.jp> NAKAGAWA Yoshihisa writes: : Adaptec SlimSCSI is major PC-Card SCSI-IF, it is based on : aic6360. Now, aic not supported yet, so Note-PC user can't use any : PC-Card SCSI-IF. I'd love to see the aic supported, mostly for my notebook. However, no one seems to have a confluance of time, information and talent to write the driver, or even port the other one in all its gory. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 00:02:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA01855 for freebsd-current-outgoing; Tue, 19 Jan 1999 00:02:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA01849 for ; Tue, 19 Jan 1999 00:02:43 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id AAA39684; Tue, 19 Jan 1999 00:02:33 -0800 (PST) To: Andreas Klemm cc: Mike Smith , current@FreeBSD.ORG Subject: Re: make release produces unbootable boot floppies, no boot loader, no /kernel In-reply-to: Your message of "Tue, 19 Jan 1999 07:25:40 +0100." <19990119072540.A2761@titan.klemm.gtn.com> Date: Tue, 19 Jan 1999 00:02:33 -0800 Message-ID: <39679.916732953@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been taking the last few days off, but I intend to get to this this week and fix whatever's broken. Don't panic. :) > On Mon, Jan 18, 1999 at 09:52:26PM -0800, Mike Smith wrote: > > > Hi ! Bad news, make release still produces non bootable floppies. > > > I cvsupped yesterday evening at 8pm and did a make world and > > > make release .... > > > > > > Now I tried the boot.flp image from the ftp subdir in /R/.... > > > > > > First error message > > > No /boot/loader > > > Then the typical "boot banner" > > > 2nd error message > > > No /kernel > > > When typing ? > > > . .. kernel.gz > > > When typing kernel.gz to load this kernel > > > invalid format > > > > Of course, it's gzipped. > > > > > Well, there is _still_ something wron, believe me. > > > > The single-floppy install is broken. Use the two-floppy install as > > I've been encouraging people to do now since the 12th. > > This sounds like booting/installing from CD-ROM is currently > impossible as well ??? > > Andreas /// > > -- > Andreas Klemm http://www.FreeBSD.ORG/~andreas > What gives you 90% more speed, for example, in kernel compilation ? > http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html > "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 00:26:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA03775 for freebsd-current-outgoing; Tue, 19 Jan 1999 00:26:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cassiopeia.hkstar.com (cassiopeia.hkstar.com [202.82.3.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA03760 for ; Tue, 19 Jan 1999 00:25:59 -0800 (PST) (envelope-from c5666305@b1.hkstar.com) Received: from b1.hkstar.com (b1.hkstar.com [202.82.0.87]) by cassiopeia.hkstar.com (8.9.1/8.9.1) with ESMTP id QAA20173 for ; Tue, 19 Jan 1999 16:25:51 +0800 (HKT) Received: (from c5666305@localhost) by b1.hkstar.com (8.8.8/8.8.8) id QAA20618 for freebsd-current@freebsd.org; Tue, 19 Jan 1999 16:25:46 +0800 (HKT) From: Chan Yiu Wah Message-Id: <199901190825.QAA20618@b1.hkstar.com> Subject: How should I config the atkbdc device To: freebsd-current@FreeBSD.ORG Date: Tue, 19 Jan 1999 16:25:46 +0800 (HKT) X-Mailer: ELM [version 2.5 PL0b1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I just finished the compilation of the whole system with ctm source upto src-cur.3712 and found the keyboard freezed after system boot up. I would like to know the usage of atkbdc device which I think is the cause of the keyboard freeze. Any idea ? cheers Clarence To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 00:47:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA05358 for freebsd-current-outgoing; Tue, 19 Jan 1999 00:47:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA05353 for ; Tue, 19 Jan 1999 00:47:20 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id AAA21785 for ; Tue, 19 Jan 1999 00:43:36 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdY21783; Tue Jan 19 08:43:31 1999 Date: Tue, 19 Jan 1999 00:43:27 -0800 (PST) From: Julian Elischer To: current@FreeBSD.ORG Subject: KLD cannot load dependent modules Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If I load a module A then try load a module B that requires a function in A it fails because it cannot find the symbol.. is this a known problem? (A real bummer if so) julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 00:47:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA05606 for freebsd-current-outgoing; Tue, 19 Jan 1999 00:47:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chandra.eatell.msr.prug.or.jp ([202.247.4.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA05598 for ; Tue, 19 Jan 1999 00:47:53 -0800 (PST) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id RAA07103; Tue, 19 Jan 1999 17:44:57 +0900 (JST) Message-Id: <199901190844.RAA07103@chandra.eatell.msr.prug.or.jp> To: Warner Losh cc: "Kenneth D. Merry" , plm@xs4all.nl (Peter Mutsaers), freebsd-current@FreeBSD.ORG Subject: Re: aic (adaptec 152x) still not supported in -current? In-reply-to: Your message of "Tue, 19 Jan 1999 00:29:50 MST." <199901190729.AAA55424@harmony.village.org> Date: Tue, 19 Jan 1999 17:44:57 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'd love to see the aic supported, mostly for my notebook. However, > no one seems to have a confluance of time, information and talent to > write the driver, or even port the other one in all its gory. If CAMed aic driver is available, SlimSCSI support is very easy. First of all, we need CAMed aic driver. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 01:02:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA06797 for freebsd-current-outgoing; Tue, 19 Jan 1999 01:02:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail-spool.is.co.za (mail-spool.is.co.za [196.4.160.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA06782 for ; Tue, 19 Jan 1999 01:02:13 -0800 (PST) (envelope-from geoffr@is.co.za) Received: from admin.is.co.za (admin.is.co.za [196.23.0.9]) by mail-spool.is.co.za (8.8.6/IShub#3) with ESMTP id LAA04568 for ; Tue, 19 Jan 1999 11:01:44 +0200 Received: from isjhbex01.is.co.za (isjhbex01.is.co.za [196.26.1.16]) by admin.is.co.za (8.8.6/8.7.3/ISsubsidiary#1) with ESMTP id LAA16709 for ; Tue, 19 Jan 1999 11:02:04 +0200 (GMT) Received: by isjhbex01.is.co.za with Internet Mail Service (5.5.2232.9) id ; Tue, 19 Jan 1999 10:57:41 +0200 Message-ID: <3D5EC7D2992BD211A95600A0C9CE047F017E2163@isjhbex01.is.co.za> From: Geoff Rehmet To: "'current@freebsd.org'" Subject: Building a new system to current Date: Tue, 19 Jan 1999 10:57:39 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id BAA06792 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi,   I'm in the process of setting up a new FreeBSD-current box, starting with 3.0 Release, and moving to current. One question I have, is whether to go to the ELF kernel before I recompile the world with current source.     My plan is as follows: - Load 3.0-RELEASE (done) - archive and delete all a.out tools (done) - update to the new bootblocks (done) - move to ELF kernel - CVSup to current - rebuild the world - come up on current   I have tarred up all the a.out libraries and tools, to try and make sure that I don't install anything that depends on a.out.  Hopefully, I will not have to go back on that!   Apart from the comments in src/UPDATING, Peter Wemm's ELF day web page, and Robert Nordiers page on the new bootblocks, can anyone think of anything I should take into account?   regards, Geoff (hoping to be hacking again soon!) -- Geoff Rehmet, The Internet Solution - Infrastructure tel: +27-11-283-5462, fax: +27-11-283-5401 mobile: +27-83-292-5800 email: geoffr@is.co.za URL: http://www.is.co.za   To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 01:08:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA08715 for freebsd-current-outgoing; Tue, 19 Jan 1999 01:08:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles139.castles.com [208.214.165.139]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA08707 for ; Tue, 19 Jan 1999 01:08:08 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id BAA02765; Tue, 19 Jan 1999 01:03:59 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901190903.BAA02765@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Geoff Rehmet cc: "'current@freebsd.org'" Subject: Re: Building a new system to current In-reply-to: Your message of "Tue, 19 Jan 1999 10:57:39 +0200." <3D5EC7D2992BD211A95600A0C9CE047F017E2163@isjhbex01.is.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Tue, 19 Jan 1999 01:03:59 -0800 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id BAA08708 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, >   > I'm in the process of setting up a new FreeBSD-current > box, starting with 3.0 Release, and moving to current. > One question I have, is whether to go to the ELF kernel > before I recompile the world with current source. >   >   > My plan is as follows: > - Load 3.0-RELEASE (done) > - archive and delete all a.out tools (done) > - update to the new bootblocks (done) > - move to ELF kernel Installing the Jan 12th snapshopt gives you all of this already, and no a.out cruft anywhere in sight. > Apart from the comments in src/UPDATING, > Peter Wemm's ELF day web page, and Robert > Nordiers page on the new bootblocks, can anyone > think of anything I should take into account? Nothing immediately obvious - you've taken a slightly longer path but I think you'll end up in the right place. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 01:10:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA09802 for freebsd-current-outgoing; Tue, 19 Jan 1999 01:10:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from osiris.kuniv.edu.kw ([139.141.220.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA09520 for ; Tue, 19 Jan 1999 01:09:19 -0800 (PST) (envelope-from root@isis.dynip.com) Received: from localhost (localhost [127.0.0.1]) by osiris.kuniv.edu.kw (8.9.2/8.9.1) with ESMTP id MAA27950 for ; Tue, 19 Jan 1999 12:06:37 +0300 (AST) (envelope-from root@isis.dynip.com) Date: Tue, 19 Jan 1999 12:04:13 +0300 (AST) From: Joss Roots Reply-To: root@isis.dynip.com To: freebsd-current@FreeBSD.ORG Subject: C++ compliler unable to produce excutables Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, Some ports are complaining during early configuration phase using configure that c++ compiler is unable to produce excutables, and the options are -O -pipe is there anything I am missing here, as this is the first time I hear this complain, please help. thanks - MAY THE FORCE BE WITH YOU. ~o .^. ---------------------------- ___ o~ .00 ) Static Email : osiris2002@yahoo.com /| o~ /)( Bouncing Email : root@isis.dynip.com / | | \ Web Site : http://isis.dynip.com:80 (Frames) ___/ | / \ Anon FTP Site : ftp://isis.dynip.com:21 (anonymous) | /''___/ / | Gopher Site : gopher://isis.dynip.com:70 | /'''/___/ | Network News : isis.dynip.com (Read, Post, Xfer) __|/'''/ Mailing Lists : majordomo@isis.dynip.com (public) pgp key : finger root@isis.dynip.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 01:42:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA12866 for freebsd-current-outgoing; Tue, 19 Jan 1999 01:42:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA12859 for ; Tue, 19 Jan 1999 01:42:13 -0800 (PST) (envelope-from geoff@rucus.ru.ac.za) Received: (qmail 23913 invoked by uid 268); 19 Jan 1999 09:42:04 -0000 Message-ID: <19990119094204.23912.qmail@rucus.ru.ac.za> Subject: Re: Building a new system to current In-Reply-To: <199901190903.BAA02765@dingo.cdrom.com> from Mike Smith at "Jan 19, 99 01:03:59 am" To: current@FreeBSD.ORG Date: Tue, 19 Jan 1999 11:42:04 +0200 (SAT) Reply-To: geoffr@is.co.za From: geoffr@is.co.za X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes : > > Installing the Jan 12th snapshopt gives you all of this already, and no > a.out cruft anywhere in sight. After a bit of thought - I think I will take this advice. Blowing the achine I have installed away is quicker than trying to juggle some of the recent changes! geoff. -- Geoff Rehmet, The Internet Solution geoffr@is.co.za; geoff@rucus.ru.ac.za; csgr@freebsd.org tel: +27-83-292-5800 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 01:50:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA13666 for freebsd-current-outgoing; Tue, 19 Jan 1999 01:50:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from idefix.omnix.net (idefix.omnix.net [194.183.217.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA13630 for ; Tue, 19 Jan 1999 01:50:01 -0800 (PST) (envelope-from didier@idefix.omnix.net) Received: from localhost (localhost [127.0.0.1]) by idefix.omnix.net (8.9.1/8.8.5) with SMTP id KAA03415 for ; Tue, 19 Jan 1999 10:50:02 +0100 (CET) Date: Tue, 19 Jan 1999 10:50:02 +0100 (CET) From: Didier Derny X-Sender: didier@idefix To: freebsd-current@FreeBSD.ORG Subject: help (3.0.0-19990112 nightmare) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, I tried to upgrade my system (FreeBSD-3.0 december) with 3.0.0-19990112. I'm using 2 scsi drivers for FreeBSD SCSIID 1 for my work system SCSIID 2 for my test system I'm always installing a new version on my test drive (SCSIID 2) with the (SCSIID 1) drive disconnected. the I reconnect my work drive (standard boot) and I boot the new system with 1:da(1,a)/kernel (now 1:da(1,a)/boot/loader) 1- book ok 2- installation interrupted while probing devices (I've not been able to get any useful message [reboot too fast]) 3- boot by mistake on the root floppy disk then inserted the boot floppy disk (boot ok, upgrade apparently ok) 4- no label on the disk after the upgrade 5- I reinstalled everything startting from the root+boo+mfsroot everything worked fined. 6- I now unable to boot (refuse to mount / writable) apparently the disk with SCSIID-2 is not recognized as da1s1a even if it booted in read only from this disk. If you have any idea ? thanks for your help ---------------------------------------------------------------------------- Didier Derny | FreeBSD 3.0-CURRENT Site Email: didier@omnix.net | Microsoft Free Computer. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 02:24:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA16415 for freebsd-current-outgoing; Tue, 19 Jan 1999 02:24:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cs.tu-berlin.de (mail.cs.tu-berlin.de [130.149.17.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA16406 for ; Tue, 19 Jan 1999 02:24:03 -0800 (PST) (envelope-from wosch@cs.tu-berlin.de) Received: from caramba.cs.tu-berlin.de (wosch@caramba.cs.tu-berlin.de [130.149.17.12]) by mail.cs.tu-berlin.de (8.9.1/8.9.1) with ESMTP id LAA12618 for ; Tue, 19 Jan 1999 11:19:24 +0100 (MET) Received: (from wosch@localhost) by caramba.cs.tu-berlin.de (8.9.1/8.9.0) id LAA18953 for current@freebsd.org; Tue, 19 Jan 1999 11:19:15 +0100 (MET) Message-ID: <19990119111611.A16717@caramba.cs.tu-berlin.de> Date: Tue, 19 Jan 1999 11:16:11 +0100 From: Wolfram Schneider To: current@FreeBSD.ORG Subject: make aout-to-elf died in src/gnu/usr.bin/texinfo/doc Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I tried `make aout-to-elf' last sunday (17th Jan). Make died in src/gnu/usr.bin/texinfo/doc The Makefile started the elf binary `../makeinfo/makeinfo' But the elf linker was not yet ready ... -- Wolfram Schneider http://freebsd.org/~w/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 02:41:43 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA18194 for freebsd-current-outgoing; Tue, 19 Jan 1999 02:41:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA18188 for ; Tue, 19 Jan 1999 02:41:41 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id TAA23253; Tue, 19 Jan 1999 19:41:26 +0900 (JST) Message-ID: <36A45D06.D4935603@newsguy.com> Date: Tue, 19 Jan 1999 19:23:02 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: "Kenneth D. Merry" CC: Peter Mutsaers , freebsd-current@FreeBSD.ORG Subject: Re: aic (adaptec 152x) still not supported in -current? References: <199901190416.VAA05677@panzer.plutotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Kenneth D. Merry" wrote: > > > At the moment, looking in LINT, it looks like aic still isn't > > supported. Is that true? Does anyone know whether it will be? > > It's true that it isn't supported yet. We are planning on supporting it. > Brian Beattie is the one working on it, you should probably ask him how > it is coming along. I have no idea when support will appear. > > If you want SCSI support any time soon, I would suggest getting a supported > card. An ISA Advansys card might be a good, cheap substitute for your > 6360/6260 board. I was under the impression that SlimSCSI was 152x-compatible. PCMCIA SCSI support is very lacking in FreeBSD-current. (Soon to be -stable!) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com If you sell your soul to the Devil and all you get is an MCSE from it, you haven't gotten market rate. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 02:42:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA18285 for freebsd-current-outgoing; Tue, 19 Jan 1999 02:42:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA18275 for ; Tue, 19 Jan 1999 02:42:07 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id JAA46055; Tue, 19 Jan 1999 09:37:48 GMT Date: Tue, 19 Jan 1999 09:37:48 +0000 (GMT) From: Doug Rabson To: Julian Elischer cc: current@FreeBSD.ORG Subject: Re: KLD cannot load dependent modules In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 19 Jan 1999, Julian Elischer wrote: > > If I load a module A > then try load a module B that requires a function in A > it fails because it cannot find the symbol.. > is this a known problem? > > (A real bummer if so) The module B needs to have A as a dependancy. Use KMODDEPS to do this. Something like this should work in the Makefile: KMOD= modB SRCS= ... KMODDEPS= modA KLDMOD=t NOMAN=t .include The linker will only resolve symbols against the files in the dependancy list (and the kernel). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 02:45:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA18760 for freebsd-current-outgoing; Tue, 19 Jan 1999 02:45:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from top.worldcontrol.com (snblitz.sc.scruznet.com [165.227.132.84]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id CAA18754 for ; Tue, 19 Jan 1999 02:45:45 -0800 (PST) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 88406 invoked by uid 100); 19 Jan 1999 10:45:40 -0000 Date: Tue, 19 Jan 1999 02:45:39 -0800 To: Brian Feldman Cc: freebsd-current@FreeBSD.ORG Subject: Re: linuxthreads, gimp 1.1+, dies Message-ID: <19990119024539.A88383@top.worldcontrol.com> Mail-Followup-To: Brian Feldman , freebsd-current@FreeBSD.ORG References: <19990118182717.A15566@top.worldcontrol.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: ; from Brian Feldman on Mon, Jan 18, 1999 at 10:04:43PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Feldman suggested: > Try compiling with debugging info, get a coredump, and debug with the binary > that has the full debugging symbols. Gimp (CVS) compiled with CFLAGS="-g -D_THREAD_SAFE -I/usr/local/include -L/usr/local/lib -O2 -m486 -pipe -lpthread" Brian Litzinger wrote: >>Everything compiles and it runs. However, various operations crash... Every crash I've generated since adding -g as been in the app/tile_cache.c code. Seems to be some problem in the list management. I recompiled that particular file using the non-thread version and have not been able to cause a crash, so I'll look more closely at that file. Thanks for the help, -- Brian Litzinger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 02:46:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA18898 for freebsd-current-outgoing; Tue, 19 Jan 1999 02:46:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frolic.no-support.loc (ppp39-41.hrz.uni-bielefeld.de [129.70.39.41]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA18889; Tue, 19 Jan 1999 02:46:43 -0800 (PST) (envelope-from bfischer@Techfak.Uni-Bielefeld.DE) Received: (from bjoern@localhost) by frolic.no-support.loc (8.9.1/8.8.8/Debian/GNU) id LAA38890; Tue, 19 Jan 1999 11:38:51 +0100 (CET) From: Bjoern Fischer Date: Tue, 19 Jan 1999 11:38:50 +0100 To: Luoqi Chen Cc: dillon@apollo.backplane.com, skynyrd@opus.cts.cwu.edu, freebsd-current@FreeBSD.ORG, jdp@polstra.com, luoqi@FreeBSD.ORG Subject: Re: NFS problem found - pleaes try this patch. Message-ID: <19990119113849.A36643@frolic.no-support.loc> References: <199901181505.KAA15315@lor.watermarkgroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199901181505.KAA15315@lor.watermarkgroup.com>; from Luoqi Chen on Mon, Jan 18, 1999 at 10:05:50AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 18, 1999 at 10:05:50AM -0500, Luoqi Chen wrote: > The check is correct and should be there, the B_CACHE bit was cleared because > I made a mistake when setting the valid bit in the vm page. [...] > Note the calculation of ev, the original code was a round-up and I changed it > to round-down in my -r1.188 commit (I thought it was a bug in the original > code, but it was actually me who didn't understand the nfs code well enough). The patch seems to solve the problem as nfs behaves as it did prior to -r1.188. Thanks. But there's still something wrong: When shutting down the server it still sometimes panics in vinvalbuf() complaining 'bout dirty pages. On the client side vi dies of SEGV (edited file and /var/tmp/vi.recover on nfs fs) generating a wrong sized recover file. After that the server panics on shutdown. Without triggering the bug it shuts down gracefully. I'll try to receipe a situation for easily reproducing this. Bjoern -- -----BEGIN GEEK CODE BLOCK----- GCS d--(+) s++: a- C+++(-) UBL++++OSI++++$ P+++(-) L+++(-) !E W- N+ o>+ K- !w !O !M !V PS++ PE- PGP++ t+++ !5 X++ tv- b+++ D++ G e+ h-- y+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 03:00:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA20534 for freebsd-current-outgoing; Tue, 19 Jan 1999 03:00:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.6.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA20529 for ; Tue, 19 Jan 1999 03:00:15 -0800 (PST) (envelope-from berend@pobox.com) Received: from auke.nederware.nl (nederware.nl [194.109.55.62]) by smtp1.xs4all.nl (8.8.8/8.8.8) with ESMTP id MAA09568; Tue, 19 Jan 1999 12:00:07 +0100 (CET) Received: from bmach (bmach.nederware.nl [192.168.33.3]) by auke.nederware.nl (8.8.8/8.8.8) with SMTP id LAA01868; Tue, 19 Jan 1999 11:48:30 +0100 (CET) (envelope-from berend@pobox.com) From: "Berend de Boer" To: "'Mike Smith'" Cc: "'current@freebsd.org'" Subject: RE: Building a new system to current Date: Tue, 19 Jan 1999 11:48:33 +0100 Message-ID: <000401be4399$42e9fa00$0321a8c0@bmach.nederware.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-Reply-To: <199901190903.BAA02765@dingo.cdrom.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> - update to the new bootblocks (done) >> - move to ELF kernel > Installing the Jan 12th snapshopt gives you all of this already, and > no a.out cruft anywhere in sight. Warning: make world doesn't upgrade the bootblocks as I just detected. I tried disklabel -B before but it complained that the device was busy (of course). Time to read the fallback section )-: Groetjes, Berend. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 03:06:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA21499 for freebsd-current-outgoing; Tue, 19 Jan 1999 03:06:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA21451; Tue, 19 Jan 1999 03:06:03 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.10 #1) id 102Yuc-00005U-00; Tue, 19 Jan 1999 13:01:34 +0200 From: Sheldon Hearn To: Bjoern Fischer cc: Luoqi Chen , dillon@apollo.backplane.com, skynyrd@opus.cts.cwu.edu, freebsd-current@FreeBSD.ORG, jdp@polstra.com, luoqi@FreeBSD.ORG Subject: Re: NFS problem found - pleaes try this patch. In-reply-to: Your message of "Tue, 19 Jan 1999 11:38:50 +0100." <19990119113849.A36643@frolic.no-support.loc> Date: Tue, 19 Jan 1999 13:01:34 +0200 Message-ID: <339.916743694@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 19 Jan 1999 11:38:50 +0100, Bjoern Fischer wrote: > But there's still something wrong: When shutting down the server > it still sometimes panics in vinvalbuf() complaining 'bout dirty > pages. I'm not sure this has anything to do with NFS. I got this after last night's fresh world and kernel install. The vinvalbuf message occured after the ``syncing disks ...done'' message but before the ``Rebooting'' message and. However, I cannot reproduce the message since that reboot, with or without NFS activity. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 03:22:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA23066 for freebsd-current-outgoing; Tue, 19 Jan 1999 03:22:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA23055 for ; Tue, 19 Jan 1999 03:22:18 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.2/8.9.2/Netplex) with ESMTP id TAA14881; Tue, 19 Jan 1999 19:21:53 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199901191121.TAA14881@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Doug Rabson cc: Julian Elischer , current@FreeBSD.ORG Subject: Re: KLD cannot load dependent modules In-reply-to: Your message of "Tue, 19 Jan 1999 09:37:48 GMT." Date: Tue, 19 Jan 1999 19:21:53 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson wrote: > On Tue, 19 Jan 1999, Julian Elischer wrote: > > > > > If I load a module A > > then try load a module B that requires a function in A > > it fails because it cannot find the symbol.. > > is this a known problem? > > > > (A real bummer if so) > > The module B needs to have A as a dependancy. Use KMODDEPS to do this. > Something like this should work in the Makefile: > > KMOD= modB > SRCS= ... > KMODDEPS= modA > KLDMOD=t > NOMAN=t > .include > > The linker will only resolve symbols against the files in the dependancy > list (and the kernel). I've been thinking that this could be improved. Yes, following the dependency list first for resolving symbols is right, I think there should be a fallback global search. Specific example (which is probably going to change today, but it's a good example): - wd.c has got hooks for the ATAPI code. - The ATAPI code can be build either statically or as a module. - ATAPI clients (acd, wfd, wst etc) therefore depend either on the kernel or the atapi module. If the atapi module was statically configured, and the acd driver depended on the atapi file, it would eventually fail due to conflicts. - However, if the acd driver didn't depend on atapi (the file), then a kernel compiled without it would be unable to load acd.ko regardless of whether atapi.ko had been previously loaded, because acd.ko won't see the symbold in atapi.ko. Does this description of the problem make sense? I think the symbol resolution should do a global search once the dependency list is exhausted. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 03:33:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA24302 for freebsd-current-outgoing; Tue, 19 Jan 1999 03:33:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-59-dbn.dial-up.net [196.34.155.59]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA24296 for ; Tue, 19 Jan 1999 03:33:03 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id NAA14265; Tue, 19 Jan 1999 13:31:51 +0200 (SAT) From: Robert Nordier Message-Id: <199901191131.NAA14265@ceia.nordier.com> Subject: Re: Building a new system to current In-Reply-To: <000401be4399$42e9fa00$0321a8c0@bmach.nederware.nl> from Berend de Boer at "Jan 19, 99 11:48:33 am" To: berend@pobox.com (Berend de Boer) Date: Tue, 19 Jan 1999 13:31:47 +0200 (SAT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Berend de Boer wrote: > >> - update to the new bootblocks (done) > >> - move to ELF kernel > > > Installing the Jan 12th snapshopt gives you all of this already, and > > no a.out cruft anywhere in sight. > > Warning: make world doesn't upgrade the bootblocks as I just detected. I > tried disklabel -B before but it complained that the device was busy (of > course). A "Device busy" is most likely due to specifying the full path of a block device disklabel -B /dev/da0s2a The best approach is to specify just the drive disklabel -B da0 or the slice, if you have more than one FreeBSD slice per drive disklabel -B da0s3 -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 03:38:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA24670 for freebsd-current-outgoing; Tue, 19 Jan 1999 03:38:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA24665 for ; Tue, 19 Jan 1999 03:38:28 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:Al7ZX1zlnT9CU78wbi2kL9y+i8Z40AS2@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id UAA01198 for ; Tue, 19 Jan 1999 20:38:21 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id UAA23720; Tue, 19 Jan 1999 20:40:45 +0900 (JST) Message-Id: <199901191140.UAA23720@zodiac.mech.utsunomiya-u.ac.jp> To: current@FreeBSD.ORG cc: yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: HEADS UP: another syscons update Date: Tue, 19 Jan 1999 20:40:43 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have committed another syscons update. Because one new file has been added to the source tree, and one file has changed location, I have to ask you to run config() before you compile the kernel next time, and "make clean depend all" in your kernel compile directory. No need to update the kernel config file this time, though. Sorry for this inconvenience. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 03:46:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA25107 for freebsd-current-outgoing; Tue, 19 Jan 1999 03:46:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA24903 for ; Tue, 19 Jan 1999 03:42:45 -0800 (PST) (envelope-from semen@iclub.nsu.ru) Received: from localhost (semen@localhost) by iclub.nsu.ru (8.8.8/8.8.5) with SMTP id RAA14565 for ; Tue, 19 Jan 1999 17:42:15 +0600 (NS) Date: Tue, 19 Jan 1999 17:42:14 +0600 (NS) From: Ustimenko Semen To: freebsd-current@FreeBSD.ORG Subject: sys/kern/kern_linker.c patch Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Imagine: I'm trying to unload KLD module, it is busy: # kldunload -n ntfs kldunload: can't unload file: Device busy After this point i'll never get module unloaded becouse kldunload() in sys/kern/kern_linker.c has already decremeted lf->userrefs. I'll get only this messages: # kldunload -n ntfs Jan 18 17:10:13 ws21 /kernel: linkerunload: attempt to unload file which was not loaded by user kldunload: can't unload file: Device busy Here is patch. *** kern_linker.c.orig Mon Jan 18 17:22:39 1999 --- kern_linker.c Mon Jan 18 16:40:33 1999 *************** *** 653,660 **** error = EBUSY; goto out; } - lf->userrefs--; error = linker_file_unload(lf); } else error = ENOENT; --- 653,662 ---- error = EBUSY; goto out; } error = linker_file_unload(lf); + if(error) + goto out; + lf->userrefs--; } else error = ENOENT; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 03:46:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA25295 for freebsd-current-outgoing; Tue, 19 Jan 1999 03:46:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from schuimpje.snt.utwente.nl (schuimpje.snt.utwente.nl [130.89.238.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA25133 for ; Tue, 19 Jan 1999 03:46:35 -0800 (PST) (envelope-from gelderen@mediaport.org) Received: from wit395301.student.utwente.nl ([130.89.235.121]:7173 "HELO deskfix" ident: "NO-IDENT-SERVICE[2]") by schuimpje.snt.utwente.nl with SMTP id <8088-10513>; Tue, 19 Jan 1999 12:46:06 +0100 Message-ID: <011b01be43a1$323851e0$0d79eb0a@deskfix.local> From: "Jeroen C. van Gelderen" To: "Doug Rabson" Cc: Subject: KLD naming Date: Tue, 19 Jan 1999 12:45:22 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Might it be a good idea to choose a consistent naming scheme for the modules? I'd think so because it would help blind loading at the boot prompt. If you choose names it the following format: type_name saver_warp saver_daemon the modules of one type will sort together in a directory listing. This is a change that will make FreeBSD more user friendly I think. Cheers, Jeroen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 04:06:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA28333 for freebsd-current-outgoing; Tue, 19 Jan 1999 04:06:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shale.csir.co.za (shale.csir.co.za [146.64.46.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA28040 for ; Tue, 19 Jan 1999 04:06:28 -0800 (PST) (envelope-from reg@shale.csir.co.za) Received: (from reg@localhost) by shale.csir.co.za (8.9.2/8.9.2) id OAA54395; Tue, 19 Jan 1999 14:06:14 +0200 (SAT) (envelope-from reg) Date: Tue, 19 Jan 1999 14:06:13 +0200 From: Jeremy Lea To: freebsd-current@FreeBSD.ORG, brian@litzinger.org Subject: Re: linuxthreads, gimp 1.1+, dies Message-ID: <19990119140613.B826@shale.csir.co.za> References: <19990118182717.A15566@top.worldcontrol.com> <19990119024539.A88383@top.worldcontrol.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990119024539.A88383@top.worldcontrol.com>; from brian@worldcontrol.com on Tue, Jan 19, 1999 at 02:45:39AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Tue, Jan 19, 1999 at 02:45:39AM -0800, brian@worldcontrol.com wrote: > Gimp (CVS) compiled with > CFLAGS="-g -D_THREAD_SAFE -I/usr/local/include -L/usr/local/lib -O2 -m486 > -pipe -lpthread" Hmm, if you're using the libpthread from lt.tar.com, and you installed it according to the instructions, then that should read: > CFLAGS="-g -D_THREAD_SAFE -DLINUXTHREADS -I/usr/local/include > --L/usr/local/lib -O2 -m486 pipe -lpthread" So it picks up the correct header. But I doubt you would have got it compiled without that? Also, are you using glib11-devel/gtk11-devel ports linked against libpthread? By default the ports link against libc_r. Also, the linuxthreads stuff needs libc to be reentrant, from what I understand, and Richard hasn't released (or finished) those patches yet. Regards, -Jeremy PS Your mailer is setting a bogus followup's line... or mine is misreading it... -- | If I was not so weak, if I was not so cold, --+-- If I was not so scared of being broken, growing old, | I would be. I would be... frail. | - jars of clay / much afraid / frail To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 04:25:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA00500 for freebsd-current-outgoing; Tue, 19 Jan 1999 04:25:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA00473 for ; Tue, 19 Jan 1999 04:25:12 -0800 (PST) (envelope-from semen@iclub.nsu.ru) Received: from localhost (semen@localhost) by iclub.nsu.ru (8.8.8/8.8.5) with SMTP id SAA15696 for ; Tue, 19 Jan 1999 18:25:00 +0600 (NS) Date: Tue, 19 Jan 1999 18:24:59 +0600 (NS) From: Ustimenko Semen To: freebsd-current@FreeBSD.ORG Subject: Re: sys/kern/kern_linker.c patch In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry for self reply. Patch isn't good enougth:-) becouse linker_file_unload() deallocates lf structure's memory... so lf->userrefs-- may cause page fault or whatever else. (I wonder how that didn't happened) Look at this one: *** kern_linker.c.orig Mon Jan 18 17:22:39 1999 --- kern_linker.c Mon Jan 18 18:14:28 1999 *************** *** 655,660 **** --- 655,662 ---- } lf->userrefs--; error = linker_file_unload(lf); + if(error) + lf->userrefs++; } else error = ENOENT; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 04:44:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA02460 for freebsd-current-outgoing; Tue, 19 Jan 1999 04:44:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA02444 for ; Tue, 19 Jan 1999 04:44:27 -0800 (PST) (envelope-from rock@cs.uni-sb.de) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.2/1999010400) with ESMTP id NAA12012; Tue, 19 Jan 1999 13:43:45 +0100 (CET) Received: from cs.uni-sb.de (maxtnt-025.rz.uni-sb.de [134.96.70.152]) by cs.uni-sb.de (8.9.2/1999010400) with ESMTP id NAA19265; Tue, 19 Jan 1999 13:43:42 +0100 (CET) Message-ID: <36A47DFC.88EC82D0@cs.uni-sb.de> Date: Tue, 19 Jan 1999 13:43:40 +0100 From: "D. Rock" X-Mailer: Mozilla 4.5 [de] (WinNT; U) X-Accept-Language: de MIME-Version: 1.0 To: Luoqi Chen CC: dillon@apollo.backplane.com, skynyrd@opus.cts.cwu.edu, freebsd-current@FreeBSD.ORG, jdp@polstra.com Subject: Re: NFS problem found - pleaes try this patch. References: <199901181505.KAA15315@lor.watermarkgroup.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This patch seems to fix my NFS problems. I started a make release yesterday and it is still running (It's a slow machine). No problems so far. The chroot dir is NFSv2/UDP mounted. Thanks, Daniel Luoqi Chen schrieb: > > The check is correct and should be there, the B_CACHE bit was cleared because > I made a mistake when setting the valid bit in the vm page. > > Index: vfs_bio.c > =================================================================== > RCS file: /home/ncvs/src/sys/kern/vfs_bio.c,v > retrieving revision 1.192 > diff -u -r1.192 vfs_bio.c > --- vfs_bio.c 1999/01/12 11:59:34 1.192 > +++ vfs_bio.c 1999/01/18 14:45:33 > @@ -2171,7 +2171,7 @@ > (vm_offset_t) (soff & PAGE_MASK), > (vm_offset_t) (eoff - soff)); > sv = (bp->b_offset + bp->b_validoff + DEV_BSIZE - 1) & ~(DEV_BSIZE - 1); > - ev = (bp->b_offset + bp->b_validend) & ~(DEV_BSIZE - 1); > + ev = (bp->b_offset + bp->b_validend + DEV_BSIZE - 1) & ~(DEV_BSIZE - 1); > soff = qmax(sv, soff); > eoff = qmin(ev, eoff); > } > > Note the calculation of ev, the original code was a round-up and I changed it > to round-down in my -r1.188 commit (I thought it was a bug in the original > code, but it was actually me who didn't understand the nfs code well enough). > > -lq > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 05:13:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA04503 for freebsd-current-outgoing; Tue, 19 Jan 1999 05:13:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gilgamesch.bik-gmbh.de (gilgamesch.bik-gmbh.de [194.233.237.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA04498 for ; Tue, 19 Jan 1999 05:13:02 -0800 (PST) (envelope-from cracauer@gilgamesch.bik-gmbh.de) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.8.8/8.7.3) id OAA00895; Tue, 19 Jan 1999 14:12:43 +0100 (MET) Message-ID: <19990119141243.A753@cons.org> Date: Tue, 19 Jan 1999 14:12:43 +0100 From: Martin Cracauer To: root@isis.dynip.com, freebsd-current@FreeBSD.ORG Subject: Re: C++ compliler unable to produce excutables References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: ; from Joss Roots on Tue, Jan 19, 1999 at 12:04:13PM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In , Joss Roots wrote: > Hi there, > Some ports are complaining during early configuration > phase using configure that c++ compiler is unable to > produce excutables, and the options are -O -pipe > is there anything I am missing here, as this is the > first time I hear this complain, please help. > thanks Do you have egcs or gcc-2.8 or anything else installaed that installs /usr/local/bin/g++? Such extra compilers from ports tend to break. Make sure you use /usr/bin/g++. If it still fails, please post the log of error messages and the usual stuff `uname -a` and such. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 05:22:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA05111 for freebsd-current-outgoing; Tue, 19 Jan 1999 05:22:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA05106 for ; Tue, 19 Jan 1999 05:22:28 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id OAA17681 for freebsd-current@FreeBSD.ORG; Tue, 19 Jan 1999 14:22:22 +0100 (CET) (envelope-from olli) Date: Tue, 19 Jan 1999 14:22:22 +0100 (CET) From: Oliver Fromme Message-Id: <199901191322.OAA17681@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: New syscons + XFree 3.3.3.1 = problem? Newsgroups: list.freebsd-current Organization: Administration Heim 3 Reply-To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >but that doesn't happen any- > >more. Instead, it uses the current one (i.e. if I'm on ttyv3 > >and start X, it uses ttyv3). Is this intentional, or is it a > >bug? Oops... I'm very sorry for the confusion... it was all my fault. There were as many gettys configured in in /etc/ttys as MAXCONS in the kernel, so XFree wasn't able to allocate an unused vty, obviously. Disabling one getty solved the problem. Maybe this pitfall could be documented somewhere... But then again, maybe I'm the only one who's too dumb to get it right. :-] Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 05:41:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA07104 for freebsd-current-outgoing; Tue, 19 Jan 1999 05:41:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kendra.ne.mediaone.net (kendra.ne.mediaone.net [24.128.94.182]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA07086 for ; Tue, 19 Jan 1999 05:40:56 -0800 (PST) (envelope-from software@kew.com) Received: from sonata.hh.kew.com (root@sonata-dmz.hh.kew.com [192.168.205.1]) by kendra.ne.mediaone.net (8.9.1/8.9.1) with ESMTP id IAA04074 for ; Tue, 19 Jan 1999 08:40:50 -0500 (EST) Received: from kew.com (minerva.hh.kew.com [192.168.203.144]) by sonata.hh.kew.com (8.9.1/8.9.1) with ESMTP id IAA12810 for ; Tue, 19 Jan 1999 08:40:49 -0500 (EST) Message-ID: <36A48B60.26D131A0@kew.com> Date: Tue, 19 Jan 1999 08:40:48 -0500 From: Drew Derbyshire Organization: Kendra Electronic Wonderworks, Stoneham, MA 02180 (http://www.kew.com) X-Mailer: Mozilla 4.5 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: make release produces unbootable boot floppies, no boot loader, no /kernel References: <199901190631.WAA01992@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > This sounds like booting/installing from CD-ROM is currently > > impossible as well ??? > > That's correct. We're looking at having to move to a harddisk > emulation mode to get this back on track. Would a 2.88M virtual floppy for the CD-ROM boot image be a quick fix, or is it too much work? -- Drew Derbyshire UUPC/extended e-mail: software@kew.com Telephone: 617-279-9812 "I get by with a little help from my friends . . ." - Lennon/McCartney To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 06:37:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23376 for freebsd-current-outgoing; Tue, 19 Jan 1999 06:37:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gemma.TechFak.Uni-Bielefeld.DE (gemma.TechFak.Uni-Bielefeld.DE [129.70.136.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA23367 for ; Tue, 19 Jan 1999 06:37:47 -0800 (PST) (envelope-from bfischer@TechFak.Uni-Bielefeld.DE) Received: from voliere.TechFak.Uni-Bielefeld.DE (voliere.TechFak.Uni-Bielefeld.DE [129.70.136.2]) by gemma.TechFak.Uni-Bielefeld.DE (8.9.1/8.9.1/TechFak/pk+ro19980721) with SMTP id PAA19796; Tue, 19 Jan 1999 15:37:31 +0100 (MET) From: Bjoern Fischer Received: by voliere.TechFak.Uni-Bielefeld.DE (SMI-8.6/pk19971205) id PAA14329; Tue, 19 Jan 1999 15:37:30 +0100 Date: Tue, 19 Jan 1999 15:37:30 +0100 To: Sheldon Hearn Cc: Bjoern Fischer , freebsd-current@FreeBSD.ORG Subject: Re: NFS problem found - pleaes try this patch. Message-ID: <19990119153730.C13902@voliere.TechFak.Uni-Bielefeld.DE> References: <19990119113849.A36643@frolic.no-support.loc> <339.916743694@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <339.916743694@axl.noc.iafrica.com>; from Sheldon Hearn on Tue, Jan 19, 1999 at 01:01:34PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 19, 1999 at 01:01:34PM +0200, Sheldon Hearn wrote: [...] > > But there's still something wrong: When shutting down the server > > it still sometimes panics in vinvalbuf() complaining 'bout dirty > > pages. > > I'm not sure this has anything to do with NFS. I got this after last > night's fresh world and kernel install. The vinvalbuf message occured > after the ``syncing disks ...done'' message but before the ``Rebooting'' > message and. Then why is the panic on the server triggered by the vi SEGV? No vi SEGV -> server goes down normally; vi SEGV -> server panics on shutdown. > However, I cannot reproduce the message since that reboot, with or > without NFS activity. It is somewhat tricky. There's actually only one file I've got that causes vi to SEGV (and the server to panic on shutdown). I'll have to look into vi source to find out how the vi.recover file is created. Maybe some locking is involvled, too. Bjoern -- (sig_t*)NULL To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 06:46:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA24402 for freebsd-current-outgoing; Tue, 19 Jan 1999 06:46:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spoon.beta.com (mcgovern.ne.mediaone.net [24.128.106.170]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA24394 for ; Tue, 19 Jan 1999 06:46:05 -0800 (PST) (envelope-from mcgovern@spoon.beta.com) Received: from spoon.beta.com (localhost.beta.com [127.0.0.1]) by spoon.beta.com (8.8.8/8.8.8) with ESMTP id JAA02473; Tue, 19 Jan 1999 09:45:36 -0500 (EST) (envelope-from mcgovern@spoon.beta.com) Message-Id: <199901191445.JAA02473@spoon.beta.com> To: Mike Smith cc: Andreas Klemm , current@FreeBSD.ORG Subject: Re: make release produces unbootable boot floppies, no boot loader, no /kernel In-reply-to: Your message of "Mon, 18 Jan 1999 22:31:21 PST." <199901190631.WAA01992@dingo.cdrom.com> Date: Tue, 19 Jan 1999 09:45:36 -0500 From: "Brian J. McGovern" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wouldn't it be possible to use a 2.88MB boot image? Most of the documentation I've read states that this should be supportable on machines that understand 2.88MB floppies.... Or, have we outgrown that already? -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 06:56:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA26597 for freebsd-current-outgoing; Tue, 19 Jan 1999 06:56:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA26588 for ; Tue, 19 Jan 1999 06:56:46 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.2/8.9.1) id IAA05304 for freebsd-current@freebsd.org; Tue, 19 Jan 1999 08:56:39 -0600 (CST) (envelope-from dick) Date: Tue, 19 Jan 1999 08:56:39 -0600 From: "Richard Seaman, Jr." To: freebsd-current@FreeBSD.ORG Subject: Re: linuxthreads, gimp 1.1+, dies Message-ID: <19990119085639.E600@tar.com> References: <19990118182717.A15566@top.worldcontrol.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <19990118182717.A15566@top.worldcontrol.com>; from brian@worldcontrol.com on Mon, Jan 18, 1999 at 06:27:18PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 18, 1999 at 06:27:18PM -0800, brian@worldcontrol.com wrote: > I running gimp -unstable (CVS 1/17/1998) and FreeBSD -current > (1/17/1998) with > > CFLAGS= -O2 -m486 -pipe -DCOMPAT_LINUX_THREADS -DVM_STACK > COPTFLAGS= -O -pipe -DCOMPAT_LINUX_THREADS -DVM_STACK > > and linuxthreads port from http://lt.tar.com. > > recompiled glib, gtk+ and gimp which works fine reasonably > well without threads. > > with threads > CFLAGS="-D_THREAD_SAFE -I/usr/local/include -L/usr/local/lib -O2 -m486 -pipe -lpthread" > > Everything compiles and it runs. However, various operations crash > for example: Thanks for the report. I'll look into it, though it may be a day or two before I can get to it. One question, I assume you compiled glib and gtk+ with linuxthreads also? If so, can you send me the makefile (and any other) mods you made to do the compile? Thanks. -- Richard Seamman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 07:12:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA13831 for freebsd-current-outgoing; Tue, 19 Jan 1999 07:12:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vanessa.eliuk.org (pme189.sunshine.net [209.17.178.189]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA13824 for ; Tue, 19 Jan 1999 07:12:11 -0800 (PST) (envelope-from kevin_eliuk@sunshine.net) Received: from localhost (cagey@localhost) by vanessa.eliuk.org (8.9.2/8.9.2) with ESMTP id HAA02219; Tue, 19 Jan 1999 07:10:02 -0800 (PST) (envelope-from cagey@vanessa.eliuk.org) Date: Tue, 19 Jan 1999 07:09:31 -0800 (PST) From: "Kevin G. Eliuk" Reply-To: "Kevin G. Eliuk" To: Chan Yiu Wah cc: freebsd-current@FreeBSD.ORG Subject: Re: How should I config the atkbdc device In-Reply-To: <199901190825.QAA20618@b1.hkstar.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 19 Jan 1999, Chan Yiu Wah wrote: > Hello, > > I just finished the compilation of the whole system with ctm source upto > src-cur.3712 and found the keyboard freezed after system boot up. I would > like to know the usage of atkbdc device which I think is the cause of the > keyboard freeze. Any idea ? > Look at http://www.freebsd.org/~yokota/sc_update.txt, that should be all you need. -- Regards, Kevin G. Eliuk Discover Rock Solid, Discover FreeBSD | http://www.FreeBSD.Org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 07:14:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA14265 for freebsd-current-outgoing; Tue, 19 Jan 1999 07:14:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA14210 for ; Tue, 19 Jan 1999 07:14:11 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.2/8.9.1) id JAA05428; Tue, 19 Jan 1999 09:11:51 -0600 (CST) (envelope-from dick) Date: Tue, 19 Jan 1999 09:11:51 -0600 From: "Richard Seaman, Jr." To: Jeremy Lea Cc: freebsd-current@FreeBSD.ORG, brian@litzinger.org Subject: Re: linuxthreads, gimp 1.1+, dies Message-ID: <19990119091151.F600@tar.com> References: <19990118182717.A15566@top.worldcontrol.com> <19990119024539.A88383@top.worldcontrol.com> <19990119140613.B826@shale.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <19990119140613.B826@shale.csir.co.za>; from Jeremy Lea on Tue, Jan 19, 1999 at 02:06:13PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 19, 1999 at 02:06:13PM +0200, Jeremy Lea wrote: > On Tue, Jan 19, 1999 at 02:45:39AM -0800, brian@worldcontrol.com wrote: > > Gimp (CVS) compiled with > > CFLAGS="-g -D_THREAD_SAFE -I/usr/local/include -L/usr/local/lib -O2 -m486 > > -pipe -lpthread" > > Hmm, if you're using the libpthread from lt.tar.com, and you installed it > according to the instructions, then that should read: > > > CFLAGS="-g -D_THREAD_SAFE -DLINUXTHREADS -I/usr/local/include > > --L/usr/local/lib -O2 -m486 pipe -lpthread" > > So it picks up the correct header. But I doubt you would have got it > compiled without that? Actually, the new version, in FreeBSD "ports" form, doesn't require -DLINUXTHREADS anymore, but it does require -I/usr/local/include to pick up the right header, since it installs a pthread.h into /usr/local/include. This conflicts with the pthread.h in /usr/include. > Also, are you using glib11-devel/gtk11-devel ports > linked against libpthread? By default the ports link against libc_r. Right. > Also, the linuxthreads stuff needs libc to be reentrant, from what I > understand, and Richard hasn't released (or finished) those patches yet. libc is partly re-entrant, partly not. It depends on what calls you're making. As a rule of thumb, wherever the pthread spec calls for a "_r" function (eg. readdir_r), the underlying function is not thread safe, and either the "_r" function is missing or is not threadsafe itself (eg. localtime_r exists in libc -- recent versions -- but is not thread safe). strrok_r is an exception, I think. -- Richard Seamman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 08:35:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA06210 for freebsd-current-outgoing; Tue, 19 Jan 1999 08:35:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles238.castles.com [208.214.165.238]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA06202 for ; Tue, 19 Jan 1999 08:35:35 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id IAA05057; Tue, 19 Jan 1999 08:32:07 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901191632.IAA05057@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Brian J. McGovern" cc: current@FreeBSD.ORG Subject: Re: make release produces unbootable boot floppies, no boot loader, no /kernel In-reply-to: Your message of "Tue, 19 Jan 1999 09:45:36 EST." <199901191445.JAA02473@spoon.beta.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 19 Jan 1999 08:32:06 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Wouldn't it be possible to use a 2.88MB boot image? Most of the documentation > I've read states that this should be supportable on machines that understand > 2.88MB floppies.... Or, have we outgrown that already? How many systems have you seen with 2.88MB floppy drives? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 08:49:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA08182 for freebsd-current-outgoing; Tue, 19 Jan 1999 08:49:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA08177 for ; Tue, 19 Jan 1999 08:49:04 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (crossd@o2.cs.rpi.edu [128.113.96.156]) by cs.rpi.edu (8.9.1/8.9.1) with ESMTP id LAA16041; Tue, 19 Jan 1999 11:48:36 -0500 (EST) Message-Id: <199901191648.LAA16041@cs.rpi.edu> To: Mike Smith cc: "Brian J. McGovern" , current@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: make release produces unbootable boot floppies, no boot loader, no /kernel In-Reply-To: Message from Mike Smith of "Tue, 19 Jan 1999 08:32:06 PST." <199901191632.IAA05057@dingo.cdrom.com> Date: Tue, 19 Jan 1999 11:48:33 -0500 From: "David E. Cross" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think the 2.88MB suggestion was an alternative to going to a 'Hard Drive' type solution for bootable CDROMs (from a jkh post earlier). Since most bioses support 2.88MB floppies (regardless of if the hardware exists on the person's machine), wouldn't it be possible to have the 'boot.flp' for a bootable CDROM be one of these? (Personally, I think going to the Hard Disk method is the right-way; this could be a short term band-aid though.) -- David Cross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 08:59:50 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA08942 for freebsd-current-outgoing; Tue, 19 Jan 1999 08:59:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bs1-highway1.skyman (ns.modem.ru [212.57.132.253]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA08935 for ; Tue, 19 Jan 1999 08:59:46 -0800 (PST) (envelope-from igorsh@garural.chel.su) Received: from garural.chel.su ([195.54.6.129]) by bs1-highway1.skyman (8.6.12/8.6.12) with ESMTP id VAA18235; Tue, 19 Jan 1999 21:58:47 +0500 Received: from igorsh.garural.chel.su (igorsh.garant-ural.ru [195.54.6.135]) by garural.chel.su (8.9.1/8.9.1) with SMTP id VAA02928; Tue, 19 Jan 1999 21:59:26 +0500 (ES) (envelope-from igorsh@garural.chel.su) Message-ID: <007901be43cd$3d2145e0$870636c3@igorsh.garural.chel.su> From: "Igor Shulgin" To: "Jordan K. Hubbard" Cc: "FreeBSD-current" Subject: ïÔ×ÅÔ: Running old program on 3.0-RELEASE Date: Tue, 19 Jan 1999 22:00:37 +0500 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I recently installed 3.0-RELEASE on existing 2.1.0-RELEASE. >> After that one program does not run any more. > >You probably did not update the contents of /etc, as one must by hand. >This would not create the a.out search paths properly and leads to this >exact error. By the way, file /etc/rc.conf did not exist in 2.1.0-RELEASE and was completely (I think) maden during installation. Was it more practical for me to remove old /etc (/usr/lib , other dirs) before upgrade from 2.1 to 3.0? Should I do it in future? Does installation on existing system use (or consider) old configuration by whatever manner? I mean more close subsequence of versions than extreme case of 2.1->3.0 . There were 2 lines in my file /etc/rc.conf : ldconfig_paths="/usr/lib/compat /usr/X11R6/lib /usr/local/lib" ldconfig_paths_aout="/usr/lib/compat/aout /usr/X11R6/lib/aout /usr/local/lib/aout" After several advices in maillist freebsd-current I _move_ /usr/lib/compat to ldconfig_paths_aout . Not copy because there are no ELF-files in my /usr/lib/compat . Is it OK? Sorry for importunity. --- With good wishes, Igor Shulgin >- Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 09:18:01 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA12555 for freebsd-current-outgoing; Tue, 19 Jan 1999 09:18:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from jli.com (jli.com [199.2.111.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA12541 for ; Tue, 19 Jan 1999 09:17:59 -0800 (PST) (envelope-from trost@cloud.rain.com) Received: (qmail 16970 invoked by uid 4); 19 Jan 1999 17:17:54 -0000 Received: (qmail 47219 invoked from network); 18 Jan 1999 20:54:50 -0000 Received: from localhost.cloud.rain.com (HELO grey.cloud.rain.com) (127.0.0.1) by localhost.cloud.rain.com with SMTP; 18 Jan 1999 20:54:50 -0000 To: current@FreeBSD.ORG Subject: Re: mounting double-ended SCSI disks References: <199901161020.CAA47520@silvia.hip.berkeley.edu> In-reply-to: Your message of Sat, 16 Jan 1999 02:20:06 PST. <199901161020.CAA47520@silvia.hip.berkeley.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <47215.916692888.1@grey.cloud.rain.com> Date: Mon, 18 Jan 1999 12:54:49 -0800 Message-ID: <47216.916692889@grey.cloud.rain.com> From: Bill Trost Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Satoshi Asami writes: However, if I try to mount it from B read-only while A is mounting it read-write, it succeeds. This looks dangerous, as A writing data onto the disk could cause B's cache to go stale without B knowing it. Just about as dangerous al letting A mount it read-only, and then B mounting it read-write. Only in this case, nobody has a chance to know that something is amiss, and since you probably are letting this happen automatically at OS startup, the chances of a RO mount being followed by a RW one are about the same as the other way 'round. You're going to have the problem regardless of whether mount pays attention to the clean flag. If you are worried about a RO mount getting corrupted, don't modify the partition out from under it on another machine. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 09:58:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA16758 for freebsd-current-outgoing; Tue, 19 Jan 1999 09:58:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA16753 for ; Tue, 19 Jan 1999 09:58:19 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id OAA47275; Sat, 16 Jan 1999 14:58:19 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Sat, 16 Jan 1999 14:58:19 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Bruce Evans cc: fn@Radio-do.de, freebsd-current@FreeBSD.ORG Subject: Re: SOFTUPDATES In-Reply-To: <199901111356.AAA06651@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 12 Jan 1999, Bruce Evans wrote: > >Does softupdates give any gain over async? > >I have /usr/src and /usr/obj both mounted async, noatime, and it does > >seem to be rather nicely fast over default mountops. > > Async isn't fully async in FreeBSD (some directory operations are still > sync), so softupdates is much faster in some cases. Fully async async > seems to be a little faster than softupdates. That's very arbitrary, softupdates can collaps and queue operations and be much faster, it just depends on your operations. -Alfred > > Bruce > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 11:13:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25124 for freebsd-current-outgoing; Tue, 19 Jan 1999 11:13:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from roma.coe.ufrj.br (roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25112 for ; Tue, 19 Jan 1999 11:13:28 -0800 (PST) (envelope-from jonny@jonny.eng.br) Received: (from jonny@localhost) by roma.coe.ufrj.br (8.8.8/8.8.8) id RAA22486 for current@freebsd.org; Tue, 19 Jan 1999 17:13:21 -0200 (EDT) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199901191913.RAA22486@roma.coe.ufrj.br> Subject: compat22 ??? To: current@FreeBSD.ORG Date: Tue, 19 Jan 1999 17:13:21 -0200 (EDT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Installing the latest 3.0-SNAP, I just discovered that I cannot run the netscape binaries anymore. It stops claiming not to find /usr/libexec/ld.so, but obviously it would not find a.out libraries neither. :) Maybe we need a compat22 distribution before 3.1 release. Jonny -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro "This .sig is not meant to be politically correct." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 11:52:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29750 for freebsd-current-outgoing; Tue, 19 Jan 1999 11:52:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA29741 for ; Tue, 19 Jan 1999 11:52:25 -0800 (PST) (envelope-from netchild@wurzelausix.cs.uni-sb.de) Received: from Vodix.CS.Uni-SB.de (maxtnt-133.telip.uni-sb.de [134.96.71.4]) by uni-sb.de (8.9.2/1999010400) with ESMTP id UAA14476 for ; Tue, 19 Jan 1999 20:52:17 +0100 (CET) Received: from wurzelausix.cs.uni-sb.de (localhost [127.0.0.1]) by Vodix.CS.Uni-SB.de (8.9.2/8.9.2) with ESMTP id UAA01392 for ; Tue, 19 Jan 1999 20:51:29 +0100 (CET) (envelope-from netchild@wurzelausix.cs.uni-sb.de) Message-Id: <199901191951.UAA01392@Vodix.CS.Uni-SB.de> Date: Tue, 19 Jan 1999 20:51:27 +0100 (CET) From: Alexander Leidinger Subject: readdir & cd9660 & direntp->d_type == bug? To: current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, dirp = opendir("/cdrom"); direntp = readdir(dirp); results in direntp->d_type == DT_UNKNOWN for every kind of directoryentry, even if it is a directory or file. The man page didn't say it didn't work with CDs, so I assume it should work ( ;) ). current from "Sun Jan 17", Bye, Alexander. -- "Darth Vader sleeps with a Teddywookie." Fortune cookie http://netchild.home.pages.de/ A.Leidinger @ wurzelausix.cs.uni-sb.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 11:55:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29984 for freebsd-current-outgoing; Tue, 19 Jan 1999 11:55:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA29976 for ; Tue, 19 Jan 1999 11:55:03 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id TAA47619; Tue, 19 Jan 1999 19:55:09 GMT Date: Tue, 19 Jan 1999 19:55:09 +0000 (GMT) From: Doug Rabson To: Peter Wemm cc: Julian Elischer , current@FreeBSD.ORG Subject: Re: KLD cannot load dependent modules In-Reply-To: <199901191121.TAA14881@spinner.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 19 Jan 1999, Peter Wemm wrote: > Doug Rabson wrote: > > On Tue, 19 Jan 1999, Julian Elischer wrote: > > > > > > > > If I load a module A > > > then try load a module B that requires a function in A > > > it fails because it cannot find the symbol.. > > > is this a known problem? > > > > > > (A real bummer if so) > > > > The module B needs to have A as a dependancy. Use KMODDEPS to do this. > > Something like this should work in the Makefile: > > > > KMOD= modB > > SRCS= ... > > KMODDEPS= modA > > KLDMOD=t > > NOMAN=t > > .include > > > > The linker will only resolve symbols against the files in the dependancy > > list (and the kernel). > > I've been thinking that this could be improved. Yes, following the > dependency list first for resolving symbols is right, I think there should > be a fallback global search. > > Specific example (which is probably going to change today, but it's a good > example): > > - wd.c has got hooks for the ATAPI code. > - The ATAPI code can be build either statically or as a module. > - ATAPI clients (acd, wfd, wst etc) therefore depend either on the kernel or > the atapi module. If the atapi module was statically configured, and the > acd driver depended on the atapi file, it would eventually fail due to > conflicts. > - However, if the acd driver didn't depend on atapi (the file), then a > kernel compiled without it would be unable to load acd.ko regardless of > whether atapi.ko had been previously loaded, because acd.ko won't see the > symbold in atapi.ko. > > Does this description of the problem make sense? I think the symbol > resolution should do a global search once the dependency list is exhausted. This makes a lot of sense. I think this is what Mike is trying to address in his new module-based instead of file-based dependancy scheme. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 11:58:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA00461 for freebsd-current-outgoing; Tue, 19 Jan 1999 11:58:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA00441 for ; Tue, 19 Jan 1999 11:58:41 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id TAA47674; Tue, 19 Jan 1999 19:59:16 GMT Date: Tue, 19 Jan 1999 19:59:16 +0000 (GMT) From: Doug Rabson To: "Jeroen C. van Gelderen" cc: current@FreeBSD.ORG Subject: Re: KLD naming In-Reply-To: <011b01be43a1$323851e0$0d79eb0a@deskfix.local> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 19 Jan 1999, Jeroen C. van Gelderen wrote: > Hi, > > Might it be a good idea to choose a consistent naming scheme for the > modules? I'd think so because it would help blind loading at the boot > prompt. If you choose names it the following format: > > type_name > saver_warp > saver_daemon > > the modules of one type will sort together in a directory listing. This is a > change that will make FreeBSD more user friendly I think. When I first started writing KLD, I had a vague notion that there would be a simple directory structure under /modules, e.g.: /modules pci/ ncr.ko ... isa/ if_ed.ko ... ... Including the type in the filename instead might be a better idea though. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 12:11:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01910 for freebsd-current-outgoing; Tue, 19 Jan 1999 12:11:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA01905 for ; Tue, 19 Jan 1999 12:11:12 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA00417; Tue, 19 Jan 1999 12:07:19 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901192007.MAA00417@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Drew Derbyshire cc: current@FreeBSD.ORG Subject: Re: make release produces unbootable boot floppies, no boot loader, no /kernel In-reply-to: Your message of "Tue, 19 Jan 1999 08:40:48 EST." <36A48B60.26D131A0@kew.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 19 Jan 1999 12:07:18 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith wrote: > > > > This sounds like booting/installing from CD-ROM is currently > > > impossible as well ??? > > > > That's correct. We're looking at having to move to a harddisk > > emulation mode to get this back on track. > > Would a 2.88M virtual floppy for the CD-ROM boot image be a quick fix, or is > it too much work? The 10M image is so little extra work that its worth doing it properly. I just have to get this damn drive off to Robert... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 12:25:38 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA03250 for freebsd-current-outgoing; Tue, 19 Jan 1999 12:25:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-51-dbn.dial-up.net [196.34.155.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA03238 for ; Tue, 19 Jan 1999 12:25:32 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id WAA19131; Tue, 19 Jan 1999 22:24:04 +0200 (SAT) From: Robert Nordier Message-Id: <199901192024.WAA19131@ceia.nordier.com> Subject: Re: make release produces unbootable boot floppies, no boot loader, no /kernel In-Reply-To: <199901192007.MAA00417@dingo.cdrom.com> from Mike Smith at "Jan 19, 99 12:07:18 pm" To: mike@smith.net.au (Mike Smith) Date: Tue, 19 Jan 1999 22:24:01 +0200 (SAT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > Mike Smith wrote: > > > > > > This sounds like booting/installing from CD-ROM is currently > > > > impossible as well ??? > > > > > > That's correct. We're looking at having to move to a harddisk > > > emulation mode to get this back on track. > > > > Would a 2.88M virtual floppy for the CD-ROM boot image be a quick fix, or is > > it too much work? > > The 10M image is so little extra work that its worth doing it properly. > I just have to get this damn drive off to Robert... ... and then Robert has to find some damn time to look at it. :-) Anyway, drop me a line when it goes off. Around 4-5 weeks seems fairly promising at the moment. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 12:54:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA06048 for freebsd-current-outgoing; Tue, 19 Jan 1999 12:54:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spoon.beta.com (mcgovern.ne.mediaone.net [24.128.106.170]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA06043 for ; Tue, 19 Jan 1999 12:54:22 -0800 (PST) (envelope-from mcgovern@spoon.beta.com) Received: from spoon.beta.com (localhost.beta.com [127.0.0.1]) by spoon.beta.com (8.8.8/8.8.8) with ESMTP id PAA03377; Tue, 19 Jan 1999 15:54:29 -0500 (EST) (envelope-from mcgovern@spoon.beta.com) Message-Id: <199901192054.PAA03377@spoon.beta.com> To: Mike Smith cc: current@FreeBSD.ORG Subject: Re: make release produces unbootable boot floppies, no boot loader, no /kernel In-reply-to: Your message of "Tue, 19 Jan 1999 08:32:06 PST." <199901191632.IAA05057@dingo.cdrom.com> Date: Tue, 19 Jan 1999 15:54:29 -0500 From: "Brian J. McGovern" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually, about half a dozen. Lots More if you include LS-120 drives in the list... But, the main point I'm driving at is to still be able to build bootable CDs without too much playing... -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 14:13:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14766 for freebsd-current-outgoing; Tue, 19 Jan 1999 14:13:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14758 for ; Tue, 19 Jan 1999 14:13:32 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (root@keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id WAA14441 for ; Tue, 19 Jan 1999 22:13:23 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.2/8.9.1) with ESMTP id WAA16620; Tue, 19 Jan 1999 22:01:57 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199901192201.WAA16620@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Somers cc: current@FreeBSD.ORG Subject: Re: Incorrect EAGAIN & select() exceptions In-reply-to: Your message of "Sun, 10 Jan 1999 13:58:25 GMT." <199901101358.NAA00734@keep.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 19 Jan 1999 22:01:56 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just in case anyone's been losing sleep over this, it was pilot error! bde@ pointed out the problem, and cron confirmed it :-/ > Hi, > > Something weird is happening in -current. I installed world, a > kernel and bootblocks on Jan 6 - I can't say for sure that it wasn't > happening before this as I usually do all ppp testing via the > loopback interface on a single machine for convenience. > > Yesterday, I tried using ppp on the above -current via a tty and got > two weird results, both happen at random intervals, but are > reasonably easy to reproduce. > > 1. I select() on a tty descriptor for reading (and writing & > exceptions). Select comes back with the read descriptor set, > I do a read() and get -1 with errno EAGAIN. This must be > wrong ! > > 2. I select() on a tty descriptor for reading, writing and > exceptions and get the exception fd_set bit set. This has never > happened before, and it was only a few weeks ago that I even had > ppp not always abend when an exception is detected. > > Does anybody know what's going on (before I look into things further) ? > Help would be appreciated if anyone has any su{spicions,gestions}. > > Cheers. > -- > Brian > > Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 14:23:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16316 for freebsd-current-outgoing; Tue, 19 Jan 1999 14:23:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from infowest.com (ns1.infowest.com [204.17.177.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA16308 for ; Tue, 19 Jan 1999 14:23:23 -0800 (PST) (envelope-from agifford@infowest.com) Received: from infowest.com (Tambler.infowest.com [207.49.57.143]) by infowest.com (8.8.8/8.8.8) with ESMTP id PAA10690 for ; Tue, 19 Jan 1999 15:23:12 -0700 (MST) Message-ID: <36A505D0.94D1D89@infowest.com> Date: Tue, 19 Jan 1999 15:23:12 -0700 From: "Aaron D. Gifford" X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 2.2.8-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: make world dying Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm still trying to upgrade from 3.0-RELEASE to 3.0-CURRENT unsuccessfully. It used to die in perl, then that was fixed, but for the past 2 days, it has been dying in /usr/src/sys/boot/i386/libi386. Is this a known problem? Yes, I'm a CURRENT newbie, but hopefully only until the split to 3.1 when I can hopefully then play with 3.1-STABLE. Are questions such as the above better addressed to -questions or -current? Thanks. Hoping to catch a cvsup when the source tree will build, Aaron out. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 14:33:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17780 for freebsd-current-outgoing; Tue, 19 Jan 1999 14:33:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nhj.nlc.net.au (nhj.nlc.net.au [203.24.133.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA17773 for ; Tue, 19 Jan 1999 14:33:22 -0800 (PST) (envelope-from john.saunders@nlc.net.au) Received: (qmail 24188 invoked by uid 1000); 20 Jan 1999 09:33:14 +1100 From: "John Saunders" Date: Wed, 20 Jan 1999 09:33:14 +1100 (EST) To: freebsd-current@FreeBSD.ORG Subject: Booting -current with new loader Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have had no success in booting -current with the new loader. I can boot the kernel directly by entering 1:wd(2,a)/kernel at the boot prompt. However if I enter either 1:wd(1,a)/boot/loader (the default) or 1:wd(2,a)/boot/loader I get the loader started but the kernel won't boot. The the second case commands like source and ls don't work unless I set currdev=disk2s1a: and then it works. I have tried setting rootdev to lots of things but the kernel _always_ tried to mount wd1s1a as the root filesystem. It seems to ignore the rootdev flag. The kernel has been built with "config kernel root on wd2" but even this is ignored. The only solution I have is bypass the loader all-together, but I really wanted a splash screen :( Or possibly use config to make my second disk appear as wd1 instead of wd2 (not tried yet because I consider it an ugly hack). Cheers. -- +------------------------------------------------------------+ . | John Saunders - mailto:john@nlc.net.au (EMail) | ,--_|\ | - http://www.nlc.net.au/ (WWW) | / Oz \ | - 02-9489-4932 or 041-822-3814 (Phone) | \_,--\_/ | NHJ NORTHLINK COMMUNICATIONS - Supplying a professional, | v | and above all friendly, internet connection service. | +------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 14:36:22 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA18352 for freebsd-current-outgoing; Tue, 19 Jan 1999 14:36:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA18342 for ; Tue, 19 Jan 1999 14:36:18 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA01127; Tue, 19 Jan 1999 14:32:38 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901192232.OAA01127@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "John Saunders" cc: freebsd-current@FreeBSD.ORG Subject: Re: Booting -current with new loader In-reply-to: Your message of "Wed, 20 Jan 1999 09:33:14 +1100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 19 Jan 1999 14:32:38 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The only solution I have is bypass the loader all-together, but I really > wanted a splash screen :( Or possibly use config to make my second disk > appear as wd1 instead of wd2 (not tried yet because I consider it an ugly > hack). Try "set num_ide_disks=-1" in the loader. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 14:47:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19454 for freebsd-current-outgoing; Tue, 19 Jan 1999 14:47:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA19447 for ; Tue, 19 Jan 1999 14:47:26 -0800 (PST) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id PAA13496; Tue, 19 Jan 1999 15:47:14 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp01.primenet.com, id smtpd013430; Tue Jan 19 15:47:10 1999 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id PAA05080; Tue, 19 Jan 1999 15:47:05 -0700 (MST) From: Terry Lambert Message-Id: <199901192247.PAA05080@usr04.primenet.com> Subject: Re: ufs async To: ck@adsu.bellsouth.com (Christian Kuhtz) Date: Tue, 19 Jan 1999 22:47:04 +0000 (GMT) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <19990117112925.A19618@oreo.adsu.bellsouth.com> from "Christian Kuhtz" at Jan 17, 99 11:29:25 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hey gang: > > Somebody mentioned the other day that UFS async isn't entirely async, and > that directories are (always) sync. Is that true? No. The default is sync metadata and async user data, with the assumption that the user will have taken a CS 203 class and know about two stage commit for database/index integrity, if they care about their data. With the "sync" option, all data, both metadata and user data, is written synchronously. With the "async" option, all data, both metadata and user data, is written asynchronously. Put another way: default: A seat belt for you, but not the passenger sync: A seat belt for you and your passenger async: You are both strapped to the bumper There's also soft updates. The point of soft updates is to ensure ordering for maximal data ingrity (default ensures only metadata integrity by ordering metadata operations, sync assures only that writes occur in order, but that user data/metadata dependencies are not assured because of implied dependecies between file contents, and async implies no data integrity whatsoever). Basically, soft updates is just a more efficient way of ensuring operations occur in order (like the USL "DOW" -- Delayed Ordered Writes -- technology, which is under patent, only more efficient). So... soft updates: A seat belat and an air bag for both you and your passenger Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 14:56:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20519 for freebsd-current-outgoing; Tue, 19 Jan 1999 14:56:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA20513 for ; Tue, 19 Jan 1999 14:56:53 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40346>; Wed, 20 Jan 1999 09:55:56 +1100 Date: Wed, 20 Jan 1999 09:56:35 +1100 From: Peter Jeremy Subject: Re: ufs async To: freebsd-current@FreeBSD.ORG Message-Id: <99Jan20.095556est.40346@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: >Put another way: > > default: A seat belt for you, but not the passenger > sync: A seat belt for you and your passenger Terry forgot to mention that you also have to come to a dead stop every 10 feet and check that the wheel bolts are all tight :-). > async: You are both strapped to the bumper And the brakes don't work. > soft updates: A seat belt and an air bag for both you > and your passenger Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 15:25:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24215 for freebsd-current-outgoing; Tue, 19 Jan 1999 15:25:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA24208 for ; Tue, 19 Jan 1999 15:25:52 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id IAA18629; Wed, 20 Jan 1999 08:25:35 +0900 (JST) Message-ID: <36A512CF.370F4E1E@newsguy.com> Date: Wed, 20 Jan 1999 08:18:39 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: John Saunders CC: freebsd-current@FreeBSD.ORG Subject: Re: Booting -current with new loader References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Saunders wrote: > > I have had no success in booting -current with the new loader. I can boot > the kernel directly by entering 1:wd(2,a)/kernel at the boot prompt. > However if I enter either 1:wd(1,a)/boot/loader (the default) or > 1:wd(2,a)/boot/loader I get the loader started but the kernel won't boot. > The the second case commands like source and ls don't work unless I set > currdev=disk2s1a: and then it works. I have tried setting rootdev to lots > of things but the kernel _always_ tried to mount wd1s1a as the root > filesystem. It seems to ignore the rootdev flag. The kernel has been built > with "config kernel root on wd2" but even this is ignored. You failed to mention your disk configuration... -- Daniel C. Sobral (8-DCS) dcs@newsguy.com If you sell your soul to the Devil and all you get is an MCSE from it, you haven't gotten market rate. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 17:26:16 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA07403 for freebsd-current-outgoing; Tue, 19 Jan 1999 17:26:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from opus.cts.cwu.edu (opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA07398 for ; Tue, 19 Jan 1999 17:26:14 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.9.1/8.9.1) with SMTP id RAA19031; Tue, 19 Jan 1999 17:26:07 -0800 (PST) Date: Tue, 19 Jan 1999 17:26:07 -0800 (PST) From: Chris Timmons To: "Aaron D. Gifford" cc: current@FreeBSD.ORG Subject: Re: make world dying In-Reply-To: <36A505D0.94D1D89@infowest.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmmm, I zapped my /usr/obj clean around 1100PST 19/Jan/1999 and made world just fine. Try starting with an empty /usr/obj. You can pretty much glean from reading -current whether or not most people are building it or if it is broken. -questions is more for general freebsd issues. -Chris On Tue, 19 Jan 1999, Aaron D. Gifford wrote: > I'm still trying to upgrade from 3.0-RELEASE to 3.0-CURRENT > unsuccessfully. It used to die in perl, then that was fixed, but for > the past 2 days, it has been dying in /usr/src/sys/boot/i386/libi386. > Is this a known problem? Yes, I'm a CURRENT newbie, but hopefully only > until the split to 3.1 when I can hopefully then play with 3.1-STABLE. > > Are questions such as the above better addressed to -questions or > -current? > > Thanks. > > Hoping to catch a cvsup when the source tree will build, > Aaron out. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 17:37:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08332 for freebsd-current-outgoing; Tue, 19 Jan 1999 17:37:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA08324 for ; Tue, 19 Jan 1999 17:37:09 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id RAA75052; Tue, 19 Jan 1999 17:35:47 -0800 (PST) (envelope-from dillon) Date: Tue, 19 Jan 1999 17:35:47 -0800 (PST) From: Matthew Dillon Message-Id: <199901200135.RAA75052@apollo.backplane.com> To: Chris Timmons Cc: "Aaron D. Gifford" , current@FreeBSD.ORG Subject: Re: make world dying References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hmmm, I zapped my /usr/obj clean around 1100PST 19/Jan/1999 and made world :just fine. Try starting with an empty /usr/obj. : :You can pretty much glean from reading -current whether or not most people :are building it or if it is broken. -questions is more for general :freebsd issues. : :-Chris : :On Tue, 19 Jan 1999, Aaron D. Gifford wrote: : :> I'm still trying to upgrade from 3.0-RELEASE to 3.0-CURRENT :> unsuccessfully. It used to die in perl, then that was fixed, but for :... I updated my tree last night and was able to do a buildworld without mishap, but I already had a mostly -current install. However, I do not recall there being a specific problem with libi386. The only other thing I can think of is that I'm doing an ELF build, and I suppose it is possible that the A.OUT build is broken and the ELF build is not. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 17:39:01 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08545 for freebsd-current-outgoing; Tue, 19 Jan 1999 17:39:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chmls11.mediaone.net (chmls11.mediaone.net [24.128.1.112]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA08523 for ; Tue, 19 Jan 1999 17:38:36 -0800 (PST) (envelope-from veldy@visi.com) Received: from rover (h-178-1.mn.mediaone.net [209.32.178.1]) by chmls11.mediaone.net (8.8.7/8.8.7) with SMTP id UAA11197; Tue, 19 Jan 1999 20:35:43 -0500 (EST) From: "Thomas T. Veldhouse" To: "Mike Smith" , "John Saunders" Cc: Subject: RE: Booting -current with new loader Date: Tue, 19 Jan 1999 19:36:45 -0600 Message-ID: <000e01be4415$56c97d80$0264a8c0@rover.mn.mediaone.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <199901192232.OAA01127@dingo.cdrom.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FYI. That had no affect for me at all. I was able to pass the kernel the rootdev by: boot -rootdev kernel but then I had a problem when it came time to mount root as read/write. It mounted read-only successfully and then bailed because it couldn't remount as read/write. num_ide_disks=-1 seemed to have absolutely no affect at all. Tom Veldhouse veldy@visi.com > -----Original Message----- > From: owner-freebsd-current@FreeBSD.ORG > [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of Mike Smith > Sent: Tuesday, January 19, 1999 4:33 PM > To: John Saunders > Cc: freebsd-current@FreeBSD.ORG > Subject: Re: Booting -current with new loader > > > > The only solution I have is bypass the loader all-together, but I really > > wanted a splash screen :( Or possibly use config to make my second disk > > appear as wd1 instead of wd2 (not tried yet because I consider > it an ugly > > hack). > > Try "set num_ide_disks=-1" in the loader. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 18:01:52 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11141 for freebsd-current-outgoing; Tue, 19 Jan 1999 18:01:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-53-dbn.dial-up.net [196.34.155.53]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA11134 for ; Tue, 19 Jan 1999 18:01:47 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id EAA23343; Wed, 20 Jan 1999 04:01:03 +0200 (SAT) From: Robert Nordier Message-Id: <199901200201.EAA23343@ceia.nordier.com> Subject: Re: make world dying In-Reply-To: <36A505D0.94D1D89@infowest.com> from "Aaron D. Gifford" at "Jan 19, 99 03:23:12 pm" To: agifford@infowest.com (Aaron D. Gifford) Date: Wed, 20 Jan 1999 04:00:59 +0200 (SAT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Aaron D. Gifford wrote: > I'm still trying to upgrade from 3.0-RELEASE to 3.0-CURRENT > unsuccessfully. It used to die in perl, then that was fixed, but for > the past 2 days, it has been dying in /usr/src/sys/boot/i386/libi386. > Is this a known problem? Yes, I'm a CURRENT newbie, but hopefully only > until the split to 3.1 when I can hopefully then play with 3.1-STABLE. A good plan is to include the actual diagnostic, together with some context, if you run into a problem. For instance: | /usr/obj/elf/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr -o | boot2.ld -P 1 boot2.bin | kernel: ver=0.87 size=6d0 load=9000 entry=9010 map=16M pgctl=1:1 | client: fmt=bin size=143c text=0 data=0 bss=0 entry=0 | output: fmt=bin size=1d0c text=200 data=1b0c org=0 entry=0 | 244 bytes available | dd if=boot2.ld of=boot2 obs=7680 conv=osync 2>/dev/null | ===> sys/boot/i386/libi386 | make: don't know how to make machine/ansi.h. Stop | *** Error code 2 | | Stop. That way, if it's not a known problem, but some form of pilot error, you may get some useful help anyway. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 18:10:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA12244 for freebsd-current-outgoing; Tue, 19 Jan 1999 18:10:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA12239 for ; Tue, 19 Jan 1999 18:10:13 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id DAA19311 for freebsd-current@FreeBSD.ORG; Wed, 20 Jan 1999 03:10:07 +0100 (CET) (envelope-from olli) Date: Wed, 20 Jan 1999 03:10:07 +0100 (CET) From: Oliver Fromme Message-Id: <199901200210.DAA19311@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Directory structure on current.freebsd.org Newsgroups: list.freebsd-current Organization: Administration Heim 3 Reply-To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Please excuse me if this is the wrong place to ask this kind of things... I'm wondering whether it might be a good idea to rename the directories "current" and "releng22" on {current,releng22} .freebsd.org to "FreeBSD-current" and "FreeBSD-stable", as they are named on ftp.freebsd.org. That would be more consistent, and it would make life a bit easier for some of the mirror sites which mirror releases and snaps on the same server, like ftp7.de.freebsd.org. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 19:32:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA21360 for freebsd-current-outgoing; Tue, 19 Jan 1999 19:32:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA21352 for ; Tue, 19 Jan 1999 19:32:21 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id EAA19624 for freebsd-current@FreeBSD.ORG; Wed, 20 Jan 1999 04:32:12 +0100 (CET) (envelope-from olli) Date: Wed, 20 Jan 1999 04:32:12 +0100 (CET) From: Oliver Fromme Message-Id: <199901200332.EAA19624@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: Directory structure on current.freebsd.org Newsgroups: list.freebsd-current Organization: Administration Heim 3 Reply-To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry for replying to my own mail... In list.freebsd-current I wrote: > I'm wondering whether it might be a good idea to rename the > directories "current" and "releng22" on {current,releng22} > .freebsd.org to "FreeBSD-current" and "FreeBSD-stable", as > they are named on ftp.freebsd.org. I just noticed that the naming of the architecture directories isn't consistent either: In releases/snapshots they're called "axp" and "x86", while in ports they're called "alpha" and "i386". Personally I prefer the latter (because "Alpha" is more well- known and 'catchy' than "AXP", and "x86" could imply that we're running on 286, too, and it's more in line with "sparc64"), but at least the naming should be consistent. Just my 0.02 Euro... Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 21:08:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA01987 for freebsd-current-outgoing; Tue, 19 Jan 1999 21:08:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nhj.nlc.net.au (nhj.nlc.net.au [203.24.133.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA01982 for ; Tue, 19 Jan 1999 21:08:05 -0800 (PST) (envelope-from john.saunders@nlc.net.au) Received: (qmail 29646 invoked by uid 1000); 20 Jan 1999 16:07:57 +1100 From: "John Saunders" Date: Wed, 20 Jan 1999 16:07:57 +1100 (EST) To: "Daniel C. Sobral" cc: freebsd-current@FreeBSD.ORG Subject: Re: Booting -current with new loader In-Reply-To: <36A512CF.370F4E1E@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 20 Jan 1999, Daniel C. Sobral wrote: > John Saunders wrote: > > I have had no success in booting -current with the new loader. I can boot > > the kernel directly by entering 1:wd(2,a)/kernel at the boot prompt. > > However if I enter either 1:wd(1,a)/boot/loader (the default) or > > 1:wd(2,a)/boot/loader I get the loader started but the kernel won't boot. > > The the second case commands like source and ls don't work unless I set > > currdev=disk2s1a: and then it works. I have tried setting rootdev to lots > > of things but the kernel _always_ tried to mount wd1s1a as the root > > filesystem. It seems to ignore the rootdev flag. The kernel has been built > > with "config kernel root on wd2" but even this is ignored. > > You failed to mention your disk configuration... Opps, 2 drives, both as IDE master, one on primary and one on secondary. Also a CDROM as secondary slave. Also to make matters worse 2 SCSI drives. The complete mapping is... BIOS number FreeBSD name 0x80 wd0 0x81 wd2 0x82 da0 0x83 da1 For the moment I am not trying to do anything with the SCSI drives, although da1 has a FreeBSD slice. Both wd0 and da0 re FAT32 Winblows. New information... I have been able to get the kernel into single user mode, where mount / barfs about not being able to mount /dev/wd2s1a on / because the filesystem is different. However an ls shows it _did_ get the right one, it just thinks it's wrong. Also curiously the normal boot-time message "changing root device to wd2s1a" doesn't appear. I can get this far using 2 methods... Booting using 1:wd(1,a)/boot/loader Then at the loader type load kernel set currdev=disk3s1a: boot With this both currdev and loaddev are initially set to disk2s1a: Or boot using 1:wd(2,a)/boot/loader Then at the loader type set currdev=disk2s1a: load kernel set currdev=disk3s1a: boot With this both currdev and loaddev are initially set to disk3s1a: The loader is also unable to access files (ls, source, help, load, etc) until I set currdev to disk2s1a: It seems that I need currdev=disk2s1a: so that the loader can load files, and I need currdev=disk3s1a: so that the kernel will mount root. Two conflicting requirements. I'm off now to play now with rootdev and boot_askname. Cheers. -- +------------------------------------------------------------+ . | John Saunders - mailto:john@nlc.net.au (EMail) | ,--_|\ | - http://www.nlc.net.au/ (WWW) | / Oz \ | - 02-9489-4932 or 041-822-3814 (Phone) | \_,--\_/ | NHJ NORTHLINK COMMUNICATIONS - Supplying a professional, | v | and above all friendly, internet connection service. | +------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 22:13:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA09209 for freebsd-current-outgoing; Tue, 19 Jan 1999 22:13:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA09204 for ; Tue, 19 Jan 1999 22:13:16 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id WAA26664; Tue, 19 Jan 1999 22:13:06 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma026662; Tue, 19 Jan 99 22:12:44 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id WAA20699; Tue, 19 Jan 1999 22:12:43 -0800 (PST) From: Archie Cobbs Message-Id: <199901200612.WAA20699@bubba.whistle.com> Subject: Re: KLD naming In-Reply-To: from Doug Rabson at "Jan 19, 99 07:59:16 pm" To: dfr@nlsystems.com (Doug Rabson) Date: Tue, 19 Jan 1999 22:12:43 -0800 (PST) Cc: gelderen@mediaport.org, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson writes: > > Might it be a good idea to choose a consistent naming scheme for the > > modules? I'd think so because it would help blind loading at the boot > > prompt. If you choose names it the following format: > > > > type_name > > saver_warp > > saver_daemon > > > > the modules of one type will sort together in a directory listing. This is a > > change that will make FreeBSD more user friendly I think. > > When I first started writing KLD, I had a vague notion that there would be > a simple directory structure under /modules, e.g.: > > /modules > pci/ > ncr.ko > ... > isa/ > if_ed.ko > ... > ... I like this idea (subdirectories) better.. it will last longer :-) Witness the explosion of the ports tree. You should then be able to load a module "isa/if_ed.ko" etc and have it work (no leading slash). In fact, we can implement this (maybe it already works) before coming to a final decision on what the actual layout should be. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 22:21:53 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA10465 for freebsd-current-outgoing; Tue, 19 Jan 1999 22:21:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA10440 for ; Tue, 19 Jan 1999 22:21:46 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40349>; Wed, 20 Jan 1999 17:20:41 +1100 Date: Wed, 20 Jan 1999 17:21:17 +1100 From: Peter Jeremy Subject: Re: Directory structure on current.freebsd.org To: freebsd-current@FreeBSD.ORG Message-Id: <99Jan20.172041est.40349@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oliver Fromme wrote: >In releases/snapshots they're called "axp" and "x86", while in >ports they're called "alpha" and "i386". I agree that having two different names is confusing. DEC (or Compaq) literature seems to use both Alpha and AXP - I'm not sure that either is an especially better choice. > "x86" could imply that we're >running on 286, too, and it's more in line with "sparc64"), I personally find "i386" a pain because it is used to specify both an architecture (IA-32) and a particular implementation (80386) of that architecture. In some cases it may not be clear which is meant. It's worthwhile noting that Sun use "x86" to specify their Intel port. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 22:35:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA12018 for freebsd-current-outgoing; Tue, 19 Jan 1999 22:35:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA11977 for ; Tue, 19 Jan 1999 22:35:24 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.8.6/8.8.6) with ESMTP id HAA14919 for ; Wed, 20 Jan 1999 07:35:09 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.2/8.9.2) id HAA00749 for current@FreeBSD.ORG; Wed, 20 Jan 1999 07:34:46 +0100 (CET) (envelope-from andreas) Date: Wed, 20 Jan 1999 07:34:45 +0100 From: Andreas Klemm To: current@FreeBSD.ORG Subject: panic: vinvalbuf: dirty bufs (during reboot, several times) Message-ID: <19990120073445.A402@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ! Since one or two weeks my system panics shortly before completely going down. Services like squid and inn take a little longer than usual to finish, I hear much disk activity. This happens usually if the system ran a day or so. What can I do to help ? Compile Kernel with debug infos ? BTW, yes I run an ELF kernel. Can't say exactly, if it's behaving like this after completely migrating to ELF. innd: server SHUTDOWN received boot() called on cpu#1 syncing disks 8 7 1 done panic: vinvalbuf: dirty bufs mp_lock = 00000001, cpuid = 0 lapic.id = 01000000 Debugger ("panic") trace: Debugger panic vinvalbuf vclean vflush ffs_flushfiles ffs_unmount dounmount vfs_unmountall boot reboot syscall Xint0x80_syscall Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #1: Mon Jan 18 19:26:39 CET 1999 root@titan.klemm.gtn.com:/home/src/sys/compile/TITAN Timecounter "i8254" frequency 1193182 Hz CPU: Pentium Pro (686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping=9 Features=0xfbff real memory = 100663296 (98304K bytes) avail memory = 94658560 (92440K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xf02dd000. Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 vga0: rev 0x01 int a irq 19 on pci0.11.0 xl0: <3Com 3c900 Etherlink XL 10BaseT Combo> rev 0x00 int a irq 18 on pci0.12.0 xl0: Ethernet address: 00:60:97:aa:3a:db xl0: selecting BNC port, half duplex ahc0: rev 0x00 int a irq 17 on pci0.13.0 ahc0: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs ahc1: rev 0x03 int a irq 16 on pci0.14.0 ahc1: aic7870 Single Channel A, SCSI Id=7, 16/255 SCBs Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x280-0x29f irq 10 maddr 0xd8000 msize 16384 on isa ed0: address 00:00:c0:5a:98:2a, type WD8013EPC (16 bit) atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface pcm0 at 0x220 irq 5 drq 1 on isa WARNING: sb: misconfigured secondary DMA channel fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in isic0 at 0xd80 irq 9 flags 0x3 on isa isic0: Teles S0/16.3 isic0: ISAC 2085 Version A1/A2 or 2086/2186 Version 1.1 (IOM-2) (Addr=0x960) isic0: HSCX 82525 or 21525 Version 2.1 (AddrA=0x160, AddrB=0x560) vga0 at 0x3c0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 IP packet filtering initialized, divert enabled, rule-based forwarding enabled, logging limited to 100 packets/entry i4b: ISDN call control device attached i4bisppp: 4 ISDN SyncPPP device(s) attached i4bctl: ISDN system control port attached i4bipr: 4 IP over raw HDLC ISDN device(s) attached (VJ header compression) i4btel: 2 ISDN telephony interface device(s) attached i4brbch: 4 raw B channel access device(s) attached i4btrc: 4 ISDN trace device(s) attached ccd0-3: Concatenated disk drivers DUMMYNET initialized (980901) -- size dn_pkt 48 Waiting 8 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! sa0 at ahc0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 4.807MB/s transfers (4.807MHz, offset 8) da3 at ahc0 bus 0 target 1 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da3: 1006MB (2061108 512 byte sectors: 64H 32S/T 1006C) cd0 at ahc0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.0MB/s transfers (10.0MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present cd1 at ahc0 bus 0 target 6 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 10.0MB/s transfers (10.0MHz, offset 15) cd1: Attempt to query device size failed: NOT READY, Medium not present da1 at ahc1 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da1: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da2 at ahc1 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da2: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled da0: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) WARNING: / was not properly dismounted ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates xl0: selecting 10baseT transceiver, half duplex i4b-L2-i4b_T202_timeout: unit 0, N202 = 3 i4b: unit 0, assigned TEI = 64 = 0x40 xl0: promiscuous mode enabled (da0:ahc0:0:0:0): tagged openings now 32 (da1:ahc1:0:1:0): tagged openings now 32 # # TITAN # machine "i386" cpu "I686_CPU" ident TITAN maxusers 128 options INCLUDE_CONFIG_FILE # Include this file in kernel options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O options "I4B_SMP_WORKAROUND" # Options for the VM subsystem #options PQ_NOOPT # No coloring options PQ_LARGECACHE # color for 512k/16k cache #options PQ_HUGECACHE # color for 1024k/16k cache # Debugging options DDB options KTRACE #kernel tracing # Network options MROUTING # Multicast routing options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about # dropped packets options IPFIREWALL_FORWARD #enable xparent proxy support options "IPFIREWALL_VERBOSE_LIMIT=100" #limit verbosity options IPDIVERT #divert sockets options "ICMP_BANDLIM" options DUMMYNET options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Softupdates options MFS #Memory Filesystem options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options KERNFS #Kernel filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console options SYSVSHM options "MD5" options NSWAPDEV=3 options PCI_QUIET options COMPAT_LINUX options SHOW_BUSYBUFS options "P1003_1B" options "_KPOSIX_PRIORITY_SCHEDULING" options "_KPOSIX_VERSION=199309L" # Size of the kernel message buffer. Should be N * pagesize. options "MSGBUF_SIZE=40960" config kernel root on da0s2a controller isa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 disk fd0 at fdc0 drive 0 controller ahc0 controller scbus0 at ahc0 disk da0 at scbus0 target 0 unit 0 disk da3 at scbus0 target 1 unit 0 tape sa0 at scbus0 target 4 device cd0 at scbus0 target 5 device cd1 at scbus0 target 6 device pass0 # CAM passthrough driver # AHA 2940 controller ahc1 controller scbus1 at ahc1 disk da1 at scbus1 target 1 unit 0 disk da2 at scbus1 target 2 unit 0 options SCSI_DELAY=8000 #Be pessimistic about Joe SCSI device options AHC_ALLOW_MEMIO options SCSI_REPORT_GEOMETRY # atkbdc0 controlls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 device psm0 at isa? tty irq 12 device vga0 at isa? port ? conflicts # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? tty device npx0 at isa? port IO_NPX irq 13 device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 device sio1 at isa? port "IO_COM2" tty irq 3 device lpt0 at isa? port? tty irq 7 device xl0 device ed0 at isa? port 0x280 net irq 10 iomem 0xd8000 device pcm0 at isa? port ? tty irq 5 drq 1 flags 0x0 pseudo-device loop pseudo-device ether pseudo-device pty 16 pseudo-device gzip #Exec gzipped a.out's pseudo-device vn #Vnode driver (turns a file into a device) pseudo-device snp 3 #Snoop device - to look at pty/vty/etc.. pseudo-device bpfilter 4 #Berkeley packet filter pseudo-device sppp #Generic Synchronous PPP pseudo-device tun 1 pseudo-device ppp 1 pseudo-device ccd 4 #Concatenated disk driver options PPP_BSDCOMP #PPP BSD-compress support options PPP_DEFLATE #PPP zlib/deflate/gzip support options PPP_FILTER #enable bpf filtering (needs bpfilter) # i4b passive ISDN cards support (isic - I4b Siemens Isdn Chipset driver) # note that the ``options'' and ``device'' lines must BOTH be defined ! # # Non-PnP Cards: # -------------- # # Teles S0/8 or Niccy 1008 #options "TEL_S0_8" #device isic0 at isa? iomem 0xd0000 net irq 5 flags 1 # # Teles S0/16 or Creatix ISDN-S0 or Niccy 1016 #options "TEL_S0_16" #device isic0 at isa? port 0xd80 iomem 0xd0000 net irq 5 flags 2 # # Teles S0/16.3 options "TEL_S0_16_3" #device isic0 at isa? port 0xd80 net irq 5 flags 3 device isic0 at isa? port 0xd80 net irq 9 flags 3 # # AVM A1 or AVM Fritz!Card #options "AVM_A1" #device isic0 at isa? port 0x340 net irq 5 flags 4 # # USRobotics Sportster ISDN TA intern #options "USR_STI" #device isic0 at isa? port 0x268 net irq 5 flags 7 # # ITK ix1 Micro #options "ITKIX1" #device isic0 at isa? port 0x398 net irq 10 flags 18 # # PnP-Cards: # ---------- # # Teles S0/16.3 PnP #options "TEL_S0_16_3_P" #device isic0 at isa? port ? net irq ? # # Creatix ISDN-S0 P&P #options "CRTX_S0_P" #device isic0 at isa? port ? net irq ? # # Dr. Neuhaus Niccy Go@ #options "DRN_NGO" #device isic0 at isa? port ? net irq ? # # Sedlbauer Win Speed #options "SEDLBAUER" #device isic0 at isa? port ? net irq ? # # Dynalink IS64PH #options "DYNALINK" #device isic0 at isa? port ? net irq ? # # ELSA QuickStep 1000pro ISA #options "ELSA_QS1ISA" #device isic0 at isa? port ? net irq ? # # PCI-Cards: # ---------- # # ELSA QuickStep 1000pro PCI #options "ELSA_QS1PCI" #device isic0 # # PCMCIA-Cards: # ------------- # # AVM PCMCIA Fritz!Card #options "AVM_A1_PCMCIA" device isic0 at isa? port 0x340 net irq 5 flags 10 # # Active Cards: # ------------- # # Stollmann Tina-dd control device #device tina0 at isa? port 0x260 net irq 10 # # ISDN Protocol Stack # ------------------- # # Q.921 / layer 2 - i4b passive cards D channel handling pseudo-device "i4bq921" # # Q.931 / layer 3 - i4b passive cards D channel handling pseudo-device "i4bq931" # # layer 4 - i4b common passive and active card handling pseudo-device "i4b" # # ISDN devices # ------------ # # userland driver to do ISDN tracing (for passive cards only) pseudo-device "i4btrc" 4 # # userland driver to control the whole thing pseudo-device "i4bctl" # # userland driver for access to raw B channel pseudo-device "i4brbch" 4 # # userland driver for telephony pseudo-device "i4btel" 2 # # network driver for IP over raw HDLC ISDN pseudo-device "i4bipr" 4 # enable VJ header compression detection for ipr i/f options IPR_VJ # # network driver for sync PPP over ISDN pseudo-device "i4bisppp" 4 -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 22:52:57 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA13486 for freebsd-current-outgoing; Tue, 19 Jan 1999 22:52:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nhj.nlc.net.au (nhj.nlc.net.au [203.24.133.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA13478 for ; Tue, 19 Jan 1999 22:52:51 -0800 (PST) (envelope-from john.saunders@nlc.net.au) Received: (qmail 9756 invoked by uid 1000); 20 Jan 1999 17:52:42 +1100 Date: 20 Jan 1999 17:52:42 +1100 Message-ID: <19990120065242.9754.qmail@nhj.nlc.net.au> From: "John Saunders" To: freebsd-current@FreeBSD.ORG Subject: Re: Booting -current with new loader X-Newsgroups: nlc.lists.freebsd-current In-Reply-To: User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (Linux/2.0.36 (i686)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wrote: > I'm off now to play now with rootdev and boot_askname. Well, if I let the standard boot process occur, then I stop the loader and set rootdev=disk3s1a: I can get the kernel running in single user mode but mount refuses to remount / as rw. It's curious that the message about changing the root device doesn't occur, time for debug output in the kernel. BTW boot_askname doesn't :-) I read some comments in the kernel source to the effect "maybe we should prompt for a boot device here" so I didn't expect it to work. The next option is configuring my master drive on the secondary interface as wd1 instead of wd2. I'm not sure about anybody else here, but to my mind a "Winblows on C: drive and let's try out FreeBSD on the second disk" configuration should really be supported seamlessly. The option of putting the second drive as slave on the primary interface would work, however anybody that knows anything about IDE (read somebdy interested in trying FreeBSD) would put it on the second interface for speed reasons. Cheers. -- +------------------------------------------------------------+ . | John Saunders - mailto:john@nlc.net.au (EMail) | ,--_|\ | - http://www.nlc.net.au/ (WWW) | / Oz \ | - 02-9489-4932 or 041-822-3814 (Phone) | \_,--\_/ | NHJ NORTHLINK COMMUNICATIONS - Supplying a professional, | v | and above all friendly, internet connection service. | +------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 23:00:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14307 for freebsd-current-outgoing; Tue, 19 Jan 1999 23:00:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA14192 for ; Tue, 19 Jan 1999 23:00:07 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca7-31.ix.netcom.com [209.109.235.31]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id WAA17755; Tue, 19 Jan 1999 22:29:08 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.1/8.6.9) id WAA84031; Tue, 19 Jan 1999 22:29:04 -0800 (PST) Date: Tue, 19 Jan 1999 22:29:04 -0800 (PST) Message-Id: <199901200629.WAA84031@silvia.hip.berkeley.edu> To: peter.jeremy@auss2.alcatel.com.au CC: freebsd-current@FreeBSD.ORG In-reply-to: <99Jan20.172041est.40349@border.alcanet.com.au> (message from Peter Jeremy on Wed, 20 Jan 1999 17:21:17 +1100) Subject: Re: Directory structure on current.freebsd.org From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry I'm jumping into this in the middle. * Oliver Fromme wrote: * >In releases/snapshots they're called "axp" and "x86", while in * >ports they're called "alpha" and "i386". I'm not sure where this "axp/x86" thing is coming from, but we are using "alpha" and "i386" in ports (and /usr/src/sys) because that's what "uname -m" returns. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 19 23:02:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14485 for freebsd-current-outgoing; Tue, 19 Jan 1999 23:02:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA14480 for ; Tue, 19 Jan 1999 23:02:26 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id XAA76802; Tue, 19 Jan 1999 23:00:55 -0800 (PST) (envelope-from dillon) Date: Tue, 19 Jan 1999 23:00:55 -0800 (PST) From: Matthew Dillon Message-Id: <199901200700.XAA76802@apollo.backplane.com> To: Andreas Klemm Cc: current@FreeBSD.ORG Subject: Re: panic: vinvalbuf: dirty bufs (during reboot, several times) References: <19990120073445.A402@titan.klemm.gtn.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi ! : :Since one or two weeks my system panics shortly before completely :going down. Services like squid and inn take a little longer than :usual to finish, I hear much disk activity. : :This happens usually if the system ran a day or so. : :What can I do to help ? Compile Kernel with debug infos ? : :BTW, yes I run an ELF kernel. Can't say exactly, if it's behaving :like this after completely migrating to ELF. : :innd: server SHUTDOWN received :boot() called on cpu#1 :syncing disks 8 7 1 done :panic: vinvalbuf: dirty bufs :mp_lock = 00000001, cpuid = 0 lapic.id = 01000000 :Debugger ("panic") : :trace: :Debugger :panic :vinvalbuf :... Hmm. Interesting, it's dying trying to fsync an FFS vnode. Are you by any chance running NFS ( client *or* server ) on this box? Bjoern had a comment relating to the same sort of problem, which I include below: ::But there's still something wrong: When shutting down the server ::it still sometimes panics in vinvalbuf() complaining 'bout dirty ::pages. On the client side vi dies of SEGV (edited file and ::/var/tmp/vi.recover on nfs fs) generating a wrong sized recover ::file. After that the server panics on shutdown. Without triggering ::the bug it shuts down gracefully. :: ::I'll try to receipe a situation for easily reproducing this. :: :: Bjoern We have a couple of possibilities. First, if either of you are compiling up your own kernels, please remember that if you are using SOFTUPDATES, the SOFTUPDATES code does *NOT* reside in /usr/src/sys but instead resides in /usr/src/contrib/sys ... when you update your kernel, also make sure that /usr/src/contrib/sys is updated. With that out of the way, if the vinvalbuf() problem still occurs our best bet is if Bjoern can give us a repeatable vi SEGV / shutdown sequence that results in the panic. If I can reproduce it on one of my machines, I can probably figure out what is going on. If both of you are running NFS, it could possibly be the NFS server forgetting to unbusy a page somewhere. If you aren't running NFS, it could be an actual bug in FFS somewhere(!). -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 00:03:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA21601 for freebsd-current-outgoing; Wed, 20 Jan 1999 00:03:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from guardian.familyins.com (guardian.familyins.com [204.50.184.246]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA21594 for ; Wed, 20 Jan 1999 00:03:02 -0800 (PST) (envelope-from davidg@autodebit.com) Received: from adsdevelop2.autodebit.com by guardian.familyins.com via smtpd (for hub.FreeBSD.ORG [204.216.27.18]) with SMTP; 20 Jan 1999 08:02:56 UT Received: by adsdevelop2.autodebit.com with Internet Mail Service (5.0.1460.8) id ; Wed, 20 Jan 1999 00:06:39 -0800 Message-ID: <71D507C37988D11182ED0000F80462AC3A63CE@adsdevelop2.autodebit.com> From: David Green-Seed To: "'freebsd-current@freebsd.org'" Subject: dual boot problems Date: Wed, 20 Jan 1999 00:06:37 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1460.8) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's my problem: at 10:21pm PST (Jan 19th 1998) I cvsupped world, rebuilt, installed the new boot blocks, and did a first-time install of an ELF kernel. Unfortunately, I'm dual-booting with windows 95 using fbsdboot.exe - which I just discovered does not work with an ELF kernel. Has anyone encountered this problem (and what did you do to fix it) or does anyone have any suggestions (other than getting rid of windows 95)? I've checked around - and the only thing that I can come up with is that NTLDR (the windows NT loader) will boot an elf FreeBSD using the new boot blocks... but I don't have NT. Any help/suggestions would be much appreciated. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 01:26:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA01315 for freebsd-current-outgoing; Wed, 20 Jan 1999 01:26:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-1-dbn.dial-up.net [196.34.155.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA01250 for ; Wed, 20 Jan 1999 01:25:57 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id LAA00531; Wed, 20 Jan 1999 11:24:34 +0200 (SAT) From: Robert Nordier Message-Id: <199901200924.LAA00531@ceia.nordier.com> Subject: Re: dual boot problems In-Reply-To: <71D507C37988D11182ED0000F80462AC3A63CE@adsdevelop2.autodebit.com> from David Green-Seed at "Jan 20, 99 00:06:37 am" To: davidg@autodebit.com (David Green-Seed) Date: Wed, 20 Jan 1999 11:24:22 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Green-Seed wrote: > Here's my problem: > > at 10:21pm PST (Jan 19th 1998) I cvsupped world, rebuilt, installed the new > boot blocks, and did a first-time install of an ELF kernel. Unfortunately, > I'm > dual-booting with windows 95 using fbsdboot.exe - which I just discovered > does not work with an ELF kernel. > > Has anyone encountered this problem (and what did you do to fix it) or does > anyone have any suggestions (other than getting rid of windows 95)? I've > checked around - and the only thing that I can come up with is that NTLDR > (the windows NT loader) will boot an elf FreeBSD using the new boot > blocks... > but I don't have NT. > > Any help/suggestions would be much appreciated. The fbsdboot.exe program should probably be considered obsolete. It should (in theory) be possible to use it to load /boot/loader, which can then load the kernel, but there are various reasons this doesn't work too well. The standard approach would be to install the FreeBSD boot manager. This displays a menu like F1 DOS F2 FreeBSD every time the machine is rebooted. So, whether in FreeBSD or Windows, you'd reboot to switch OSes. To install this, there's a utility at http://www.freebsd.org/~rnordier/boot0inst-1.0.2.tar.gz though you can also use sysinstall. There are also various alternative boot managers, commercial and otherwise. System Commander from V-Communications seems fairly popular: though I wouldn't personally pay a $100 list price for this kind of thing. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 02:55:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA12861 for freebsd-current-outgoing; Wed, 20 Jan 1999 02:55:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from octopus.originative.co.uk (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA12781 for ; Wed, 20 Jan 1999 02:54:45 -0800 (PST) (envelope-from paul@originative.co.uk) From: paul@originative.co.uk Received: by OCTOPUS with Internet Mail Service (5.5.1960.3) id ; Wed, 20 Jan 1999 10:53:06 -0000 Message-ID: To: peter.jeremy@auss2.alcatel.com.au, freebsd-current@FreeBSD.ORG Subject: RE: Directory structure on current.freebsd.org Date: Wed, 20 Jan 1999 10:53:06 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Peter Jeremy [mailto:peter.jeremy@auss2.alcatel.com.au] > Sent: Wednesday, January 20, 1999 6:21 AM > To: freebsd-current@FreeBSD.ORG > Subject: Re: Directory structure on current.freebsd.org > > > Oliver Fromme wrote: > >In releases/snapshots they're called "axp" and "x86", while in > >ports they're called "alpha" and "i386". > > I agree that having two different names is confusing. > > DEC (or Compaq) literature seems to use both Alpha and AXP - I'm not > sure that either is an especially better choice. > > > "x86" could imply that we're > >running on 286, too, and it's more in line with "sparc64"), > > I personally find "i386" a pain because it is used to specify both an > architecture (IA-32) and a particular implementation (80386) of that > architecture. In some cases it may not be clear which is meant. I think the architecture names are more appropriate than any cpu related name. For the alpha, while we might all use alpha in everyday speech axp is more specific when it comes to releases since the alpha release of the alpha code can get a tad confusing, I think that's why it was changed in the first place. It'd be nice if i386 could become IA32 but it probably won't happen. Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 02:57:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA13245 for freebsd-current-outgoing; Wed, 20 Jan 1999 02:57:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA13240 for ; Wed, 20 Jan 1999 02:57:32 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (brian@keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id KAA10815; Wed, 20 Jan 1999 10:57:18 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.2/8.9.1) with ESMTP id IAA00908; Wed, 20 Jan 1999 08:50:01 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199901200850.IAA00908@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: alk@pobox.com cc: current@FreeBSD.ORG Subject: Re: PPP data-dependent bug In-reply-to: Your message of "Fri, 15 Jan 1999 12:03:10 CST." <13983.33200.312463.1364@avalon.east> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 20 Jan 1999 08:50:01 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > FYI, when I rcp (actually, rsync) a certain makefile (ppp -alias), I > get lots of these, and it never completes: > > Warning: CCP: deflink: Incorrect ResetAck (id 49, not 50) ignored > Warning: CCP: deflink: Incorrect ResetAck (id 49, not 50) ignored > Warning: CCP: deflink: Unexpected ResetAck (id 51) ignored > Warning: CCP: deflink: Unexpected ResetAck (id 55) ignored > Warning: CCP: deflink: Unexpected ResetAck (id 55) ignored Dare I say ``you're talking to a lousy CCP/FSM implementation'' ? (your response: It's also user-ppp). Unfortunately, there aren't any interesting logs that mention the ResetReq - just logs that mention the reason behind it :-( If you're using user-ppp on the other end, you could have a look at the CCP logs there and try to match up the FSM IDs (the bit in parenthesis after the {Send,Recv}ResetReq messages). You're proabably better off using hardware compression here - if the peer can't get a reset right. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 02:59:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA13563 for freebsd-current-outgoing; Wed, 20 Jan 1999 02:59:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from octopus.originative.co.uk (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA13550 for ; Wed, 20 Jan 1999 02:59:50 -0800 (PST) (envelope-from paul@originative.co.uk) From: paul@originative.co.uk Received: by OCTOPUS with Internet Mail Service (5.5.1960.3) id ; Wed, 20 Jan 1999 10:58:14 -0000 Message-ID: To: archie@whistle.com, dfr@nlsystems.com Cc: gelderen@mediaport.org, current@FreeBSD.ORG Subject: RE: KLD naming Date: Wed, 20 Jan 1999 10:58:13 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Archie Cobbs [mailto:archie@whistle.com] > Sent: Wednesday, January 20, 1999 6:13 AM > To: dfr@nlsystems.com > Cc: gelderen@mediaport.org; current@FreeBSD.ORG > Subject: Re: KLD naming > > > Doug Rabson writes: > > > Might it be a good idea to choose a consistent naming > scheme for the > > > modules? I'd think so because it would help blind loading > at the boot > > > prompt. If you choose names it the following format: > > > > > > type_name > > > saver_warp > > > saver_daemon > > > > > > the modules of one type will sort together in a directory > listing. This is a > > > change that will make FreeBSD more user friendly I think. > > > > When I first started writing KLD, I had a vague notion that > there would be > > a simple directory structure under /modules, e.g.: > > > > /modules > > pci/ > > ncr.ko > > ... > > isa/ > > if_ed.ko > > ... > > ... > > I like this idea (subdirectories) better.. it will last longer :-) > Witness the explosion of the ports tree. > > You should then be able to load a module "isa/if_ed.ko" etc > and have it work (no leading slash). I don't think subdirectories based on bus type is a good idea, it doesn't really fit the granularity we're probably heading towards. Some thinks don't really fit at all, filesystems, screen savers etc and even for drivers we're heading towards less bus specific devices so an ethernet driver, say, would be the same for any bus, only the startup code would be different and possibly(probably) in a different module. A functional structure is probably better /modules /devices /ethernet /storage /display /network /filesystems /screensavers etc. Not a specific proposal for actual directories but perhaps a better direction. I think we should start thinking more in terms of function, rather than bus, in a lot of what we do with devices as we abstract out the bus code more effectively. Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 03:08:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA14298 for freebsd-current-outgoing; Wed, 20 Jan 1999 03:08:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from schuimpje.snt.utwente.nl (schuimpje.snt.utwente.nl [130.89.238.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA14293 for ; Wed, 20 Jan 1999 03:08:31 -0800 (PST) (envelope-from gelderen@mediaport.org) Received: from wit395301.student.utwente.nl ([130.89.235.121]:4612 "HELO deskfix" ident: "NO-IDENT-SERVICE[2]") by schuimpje.snt.utwente.nl with SMTP id <8095-10515>; Wed, 20 Jan 1999 12:08:10 +0100 Message-ID: <003601be4465$104203a0$0d79eb0a@deskfix.local> From: "Jeroen C. van Gelderen" To: "Archie Cobbs" , "Doug Rabson" Cc: Subject: Re: KLD naming Date: Wed, 20 Jan 1999 12:07:26 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Archie Cobbs >Doug Rabson writes: >> > Might it be a good idea to choose a consistent naming scheme for the >> > modules? I'd think so because it would help blind loading at the boot >> > prompt. If you choose names it the following format: >> > >> > type_name >> > saver_warp >> > saver_daemon >> > >> > the modules of one type will sort together in a directory listing. This is a >> > change that will make FreeBSD more user friendly I think. >> >> When I first started writing KLD, I had a vague notion that there would be >> a simple directory structure under /modules, e.g.: >> >> /modules >> pci/ >> ncr.ko >> ... >> isa/ >> if_ed.ko >> ... >> ... > >I like this idea (subdirectories) better.. it will last longer :-) >Witness the explosion of the ports tree. I witnessed. But I don't think we will be heading that way. Even if you have 40 modules in each category, this ought to work (ls saver*). It will work because we prefix every driver with it's type so they sort together. This would have worked for the ports tree as well. Another advantage of the flat model is that it's way easier to browse. IMHO it's a real pain to have descend into subdirectories, only to find out that you want to look in another one. Cheers, Jeroen -- Jeroen C. van Gelderen -- gelderen@mediaport.org -- 0x46D8D3C8 -- &[8-D}~<= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 03:29:42 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA16255 for freebsd-current-outgoing; Wed, 20 Jan 1999 03:29:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA16250 for ; Wed, 20 Jan 1999 03:29:39 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.10 #1) id 102vp9-0008c9-00 for current@freebsd.org; Wed, 20 Jan 1999 13:29:27 +0200 From: Sheldon Hearn To: current@FreeBSD.ORG Subject: src/games turds after make buildworld Date: Wed, 20 Jan 1999 13:23:06 +0200 Message-ID: <33047.916831386@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, I'm finding turds in src/games/{advanture,hack,phantasia}/ and would like to prevent buildworld from producing them. Looks to me as though the turds are produced by a broken build-tools rule in their Makefiles. Anyone know wtf these games contribute to buildworld's bootstrapping? :-) Thanks, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 04:27:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA23069 for freebsd-current-outgoing; Wed, 20 Jan 1999 04:27:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gemma.TechFak.Uni-Bielefeld.DE (gemma.TechFak.Uni-Bielefeld.DE [129.70.136.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA23059 for ; Wed, 20 Jan 1999 04:27:16 -0800 (PST) (envelope-from bfischer@TechFak.Uni-Bielefeld.DE) Received: from voliere.TechFak.Uni-Bielefeld.DE (voliere.TechFak.Uni-Bielefeld.DE [129.70.136.2]) by gemma.TechFak.Uni-Bielefeld.DE (8.9.1/8.9.1/TechFak/pk+ro19980721) with SMTP id NAA06906; Wed, 20 Jan 1999 13:27:01 +0100 (MET) From: Bjoern Fischer Received: by voliere.TechFak.Uni-Bielefeld.DE (SMI-8.6/pk19971205) id NAA15746; Wed, 20 Jan 1999 13:27:00 +0100 Date: Wed, 20 Jan 1999 13:27:00 +0100 To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: panic: vinvalbuf: dirty bufs (during reboot, several times) Message-ID: <19990120132700.A15521@voliere.TechFak.Uni-Bielefeld.DE> References: <19990120073445.A402@titan.klemm.gtn.com> <199901200700.XAA76802@apollo.backplane.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=opJtzjQTFsWo+cga X-Mailer: Mutt 0.95.1i In-Reply-To: <199901200700.XAA76802@apollo.backplane.com>; from Matthew Dillon on Tue, Jan 19, 1999 at 11:00:55PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --opJtzjQTFsWo+cga Content-Type: text/plain; charset=us-ascii On Tue, Jan 19, 1999 at 11:00:55PM -0800, Matthew Dillon wrote: [...] > ::But there's still something wrong: When shutting down the server > ::it still sometimes panics in vinvalbuf() complaining 'bout dirty > ::pages. On the client side vi dies of SEGV (edited file and > ::/var/tmp/vi.recover on nfs fs) generating a wrong sized recover > ::file. After that the server panics on shutdown. Without triggering > ::the bug it shuts down gracefully. > :: > ::I'll try to receipe a situation for easily reproducing this. > :: > :: Bjoern > [...] > With that out of the way, if the vinvalbuf() problem still occurs > our best bet is if Bjoern can give us a repeatable vi SEGV / shutdown > sequence that results in the panic. > > If I can reproduce it on one of my machines, I can probably figure out > what is going on. If both of you are running NFS, it could possibly be > the NFS server forgetting to unbusy a page somewhere. If you aren't > running NFS, it could be an actual bug in FFS somewhere(!). ok, here are some instructions which -- I hope -- reproduce it (I haven't found a *nice* way; this is the ridiculous way): NFS server and client are completely 3.0-CURRENT (of CTM src-cur.3712.gz) with Luoqi's NFS fix. The server has all (physical) file systems mounted with softupdates except `/'. On the client simply edit `http://www.freebsd.org/~yokota/sc_update.txt' (hey, don't laugh. Other files won't do it. Not even files with the same size.) with FreeBSD vanilla vi (nvi). `sc_update.txt' is also attached to this mail if the file in it's original location had been changed recently. vi doesn't start normally, but skrews up and gets into an uninterruptible state. Trying to kill the beast makes it SEGV. (Of course everything is pretty normal when viing on the server.) The file system which contains the file and the one which contains /var/tmp/vi.recover are NFS ver2,udp,hard (although ver3,tcp/udp should work^H^H^H^Hfail, too). They don't need to be separate mounts. After the vi-SEGV try to shutdown the server with `shutdown -[rh] now'. You may shutdown the client first -- it makes no difference. Then you will get the panic. Good luck. Bjoern -- (sig_t*)NULL --opJtzjQTFsWo+cga Content-Type: text/plain Content-Disposition: attachment; filename="sc_update.txt" Last update: 12 January 1999. Kazutaka YOKOTA yokota@FreeBSD.ORG ----------------------------------------------------------------------- I) Syscons Update II) Splash Screen III) Splash Screen/Screen Saver FAQ ----------------------------------------------------------------------- I) Syscons Update Major update for the console driver started on 10 January. New keyboard and video card drivers have been introduced (This is just the begining. There will be more updates to follow in the next few months.) Because of these changes, you must update several things in your -current system. 1. You are required to update your kernel configuration file. If you are using syscons, controller atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 #device psm0 at isa? tty irq 12 device vga0 at isa? port ? conflicts device sc0 at isa? tty pseudo-device splash Note that `splash' is required if you intend to use screen savers or splash screen. !!IMPORTANT!! Due to sloppy programming of mine, the pseudo-device splash is ALWAYS needed for the syscons driver at the moment. The problem will be fixed soon .(12 Jan. 99) If you are pcvt user, controller atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 #device psm0 at isa? tty irq 12 device vt0 at isa? tty 2. The following options for syscons are replaced by new ones. SC_ALT_SEQACCESS-> VGA_ALT_SEQACCESS SLOW_VGA -> VGA_SLOW_IOACCESS 3. The following flags for syscons are no longer available. 0x08 Force detection of keyboard. 0x10 Old-style (XT) keyboard support. 0x20 Don't reset keyboard. Use corresponding new flags for atkbd instead. 0x01 Don't install the keyboard driver if no keyboard is found, else we always assume a keyboard. 0x02 Don't reset keyboard. 0x04 XT keyboard support. 4. You must recompile screen saver modules and the vesa module in /sys/modules, as well as kbdcontrol and vidcontrol in /usr/src/usr.sbin. If you regularly do `make world', you will be in good shape. If you don't do it often, this may be a good opportunity. II) Splash Screen A splash screen module has been added. See /sys/modules/splash. This version has rather limited capabilities: it can handle W*ndows 256 color BMP file only (other color depth probably won't work); the size of the image must be 320x200 or less. In order to see splash image when your kernel loads, do the following: Make sure the following line is added to your kernel configuration file and rebuild a new kernel. pseudo-device splash Copy your favorite W*ndows BMP file to somewhere the boot loader can see. When the boot loader starts, load kernel, splash image file and the splash image decoder module as follows. load kernel load -t splash_image_data _your_BMP_file_ load splash_bmp boot "-t splash_image_data" is extremely important as the the decoder will look for this tag for the bitmap data. Then you should see the image on your screen as soon as the kernel loads. If you specify -c or -v options to the boot command, the splash image won't appear. (But is loaded and can be used as a screen saver later; see below.) Note also that the splash screen won't be available if you use pcvt driver. You must be using syscons. The splash screen will go away if you hit any key (this may not work immediately if the kernel is still probing devices), or you load a screen saver. If you load the splash image decoder module but don't load a screen saver, you can continue using the splash module as a screen saver. Specify timeout value by running vidcontrol. vidcontrol -t timeout Then, the splash screen image will come back after the specified time. (You cannot use the regular screen saver as a splash screen, though.) There is a little-known feature of kbdcontrol which you might be interested in. You can define the `saver' key in the keymap. You press the `saver' key, then the current screen saver (or the splash screen if no screen saver is loaded) will immediately pops up. For example, if you want to assign the `saver' key to the Pause key, whose key number is 104, find the line for the4 key 104 and change it to 104 saver saver saver saver saver saver saver saver O Then reload the keymap. kbdcontrol -l mykeymap The `saver' key has no effect in the X session. III) Splash Screen/Screen Saver FAQ -------------------------------------- Q. Do I need the pseudo-device splash in order to use `blank' or `green' savers? A. Yes. The splash device is required for ANY screen savers and splash screen. -------------------------------------- Q. I loaded kernel, a bitmap file and the splash_bmp module as instructed, but got the following error. What gives? Preloaded elf module "splash_bmp.ko" at XXXXXX. module_register_init: module_register(splash_bmp, YYYYYY, 0) error 19 A. The current version of splash_bmp.ko is very limited. The color depth must be 8 bpp (256 color), and the size must be 320x200 or smaller. If your BMP file doesn't satisfy these conditions, splash_bmp.ko will return error 19 (ENODEV). These restriction may be relaxed in the future (no delivery date is promised, though). Another possible cause of error is that the video driver finds it unable to switch video modes on your video card and splash_bmp.ko is failing. Run the `dmesg' command and see if it shows something like "...video mode switching is only partially supported..." among boot messages. There is no fix for this at the moment. Sorry. -------------------------------------- Q. Can we have splash screen and screen savers on the Alpha architecture? A. Not at the moment. -------------------------------------- ---- End of File ---- --opJtzjQTFsWo+cga-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 04:39:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA24290 for freebsd-current-outgoing; Wed, 20 Jan 1999 04:39:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nhj.nlc.net.au (nhj.nlc.net.au [203.24.133.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA24279 for ; Wed, 20 Jan 1999 04:39:08 -0800 (PST) (envelope-from john.saunders@nlc.net.au) Received: (qmail 754 invoked by uid 1000); 20 Jan 1999 23:39:01 +1100 Date: 20 Jan 1999 23:39:01 +1100 Message-ID: <19990120123901.753.qmail@nhj.nlc.net.au> From: "John Saunders" To: freebsd-current@FreeBSD.ORG Subject: Re: Booting -current with new loader X-Newsgroups: nlc.lists.freebsd-current In-Reply-To: <19990120065242.9754.qmail@nhj.nlc.net.au> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (Linux/2.0.36 (i686)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The next option is configuring my master drive on the secondary interface > as wd1 instead of wd2. This works fine. I guess the real solution is to make the IDE disk scan the same as we do for SCSI, which also happens to be the same as the BIOS does. We possible need a config syntax like controler wdc0 ... controler wdc1 ... device wd? ay wdc? This will automatically assign numbers to drives as it finds them. Actually I tried this syntax which config accepted OK, however no drives got detected. Anyway for me at least a kernel config file tweak got me booting with spash screens. If you want my system to be a test bed for any mods, please let me know. Cheers. -- +------------------------------------------------------------+ . | John Saunders - mailto:john@nlc.net.au (EMail) | ,--_|\ | - http://www.nlc.net.au/ (WWW) | / Oz \ | - 02-9489-4932 or 041-822-3814 (Phone) | \_,--\_/ | NHJ NORTHLINK COMMUNICATIONS - Supplying a professional, | v | and above all friendly, internet connection service. | +------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 06:54:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA07714 for freebsd-current-outgoing; Wed, 20 Jan 1999 06:54:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hschpt06.hou.ucarb.com ([144.68.7.99]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA07685 for ; Wed, 20 Jan 1999 06:53:59 -0800 (PST) (envelope-from miker@hschpt06.hou.ucarb.com) Received: (from miker@localhost) by hschpt06.hou.ucarb.com (8.8.8/8.8.8) id IAA15473 for current@freebsd.org; Wed, 20 Jan 1999 08:53:34 -0600 (CST) (envelope-from mikenguyen@sprintmail.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 20 Jan 1999 08:53:34 -0600 (CST) From: Mike Nguyen To: current@FreeBSD.ORG Subject: /etc/nsswitch.conf Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I noticed that NetBSD is switching over to using /etc/nsswitch.conf (like Slowlaris, PH-UX, etc.). Would it be a good idea to do this for FreeBSD too (when I first started using FreeBSD, it took me a long time to figure out the analogous file for hostname lookups was /etc/host.conf) -- it seems consolidating all that config information would in one place would be a good thing. Mike. ------------------------------------------------------------------------------- Mike Nguyen - UNIX Sysadmin and Geek Pager (800) SKY-8888 pin# 1138368 or 1138368@skytel.com Abandon the search for Truth; settle for a good fantasy. ------------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 07:21:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA10400 for freebsd-current-outgoing; Wed, 20 Jan 1999 07:21:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA10394 for ; Wed, 20 Jan 1999 07:21:38 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id HAA13241; Wed, 20 Jan 1999 07:21:23 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id HAA05211; Wed, 20 Jan 1999 07:21:23 -0800 (PST) (envelope-from jdp@polstra.com) Date: Wed, 20 Jan 1999 07:21:23 -0800 (PST) Message-Id: <199901201521.HAA05211@vashon.polstra.com> To: yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: HEADS UP: another syscons update Newsgroups: polstra.freebsd.current In-Reply-To: <199901191140.UAA23720@zodiac.mech.utsunomiya-u.ac.jp> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199901191140.UAA23720@zodiac.mech.utsunomiya-u.ac.jp>, Kazutaka YOKOTA wrote: > I have committed another syscons update. > > Because one new file has been added to the source tree, and one file > has changed location, I have to ask you to run config() before you > compile the kernel next time, and "make clean depend all" in your > kernel compile directory. Is "make clean" really necessary? A "make depend" ought to be sufficient, I would think. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 07:41:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA12543 for freebsd-current-outgoing; Wed, 20 Jan 1999 07:41:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA12486 for ; Wed, 20 Jan 1999 07:40:55 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.10 #1) id 102zjA-000CNY-00; Wed, 20 Jan 1999 17:39:32 +0200 From: Sheldon Hearn To: John Polstra cc: yokota@zodiac.mech.utsunomiya-u.ac.jp, current@FreeBSD.ORG Subject: Re: HEADS UP: another syscons update In-reply-to: Your message of "Wed, 20 Jan 1999 07:21:23 PST." <199901201521.HAA05211@vashon.polstra.com> Date: Wed, 20 Jan 1999 17:39:32 +0200 Message-ID: <47587.916846772@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 20 Jan 1999 07:21:23 PST, John Polstra wrote: > Is "make clean" really necessary? A "make depend" ought to be > sufficient, I would think. I think that's an attempt to protect people who've upgraded from STABLE and haven't gotten used to ``config -r''? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 08:31:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18155 for freebsd-current-outgoing; Wed, 20 Jan 1999 08:31:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA18150 for ; Wed, 20 Jan 1999 08:31:02 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.2/8.9.2/Netplex) with ESMTP id AAA20789; Thu, 21 Jan 1999 00:29:54 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199901201629.AAA20789@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Sheldon Hearn cc: John Polstra , yokota@zodiac.mech.utsunomiya-u.ac.jp, current@FreeBSD.ORG Subject: Re: HEADS UP: another syscons update In-reply-to: Your message of "Wed, 20 Jan 1999 17:39:32 +0200." <47587.916846772@axl.noc.iafrica.com> Date: Thu, 21 Jan 1999 00:29:54 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > > > On Wed, 20 Jan 1999 07:21:23 PST, John Polstra wrote: > > > Is "make clean" really necessary? A "make depend" ought to be > > sufficient, I would think. > > I think that's an attempt to protect people who've upgraded from STABLE > and haven't gotten used to ``config -r''? config -r? I'd be highly suprised if this was needed at all for 99% of the time. The only time that I've been aware of it being needed was quite some time ago when there was an option that got removed - if people were using it, that option wouldn't get cleaned out from the .h files, and it caused a problem somewhere. I don't remember the specifics, it was a long time ago. The only other time I can think of where this might be needed is when the system clock gets screwed and the *.h files get future dates on them. In just about all other cases, a 'make clean' is sufficient to start the tree from scratch if there are any suspicions about old files. 'make depend' really does work, and is quite safe. Cleaning the tree should be a very rare requirement. > Ciao, > Sheldon. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 08:47:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA19535 for freebsd-current-outgoing; Wed, 20 Jan 1999 08:47:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA19529 for ; Wed, 20 Jan 1999 08:47:40 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.10 #1) id 1030lc-000J1q-00; Wed, 20 Jan 1999 18:46:08 +0200 From: Sheldon Hearn To: Peter Wemm cc: John Polstra , yokota@zodiac.mech.utsunomiya-u.ac.jp, current@FreeBSD.ORG Subject: Re: HEADS UP: another syscons update In-reply-to: Your message of "Thu, 21 Jan 1999 00:29:54 +0800." <199901201629.AAA20789@spinner.netplex.com.au> Date: Wed, 20 Jan 1999 18:46:08 +0200 Message-ID: <73149.916850768@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 21 Jan 1999 00:29:54 +0800, Peter Wemm wrote: > 'make depend' really does work, and is quite safe. Cleaning the tree > should be a very rare requirement. Perhaps the chap sitting next to me and I are just unlucky. Between the two of us, we've needed to use ``config -r'' three times since moving over to CURRENT about two weeks ago. What I pity we didn't save typescripts for the failures this corrected. :( Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 08:54:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA20410 for freebsd-current-outgoing; Wed, 20 Jan 1999 08:54:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA20402 for ; Wed, 20 Jan 1999 08:54:42 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.1/8.9.1) id RAA38738; Wed, 20 Jan 1999 17:53:51 +0100 (CET) (envelope-from des) To: Peter Wemm Cc: Sheldon Hearn , John Polstra , yokota@zodiac.mech.utsunomiya-u.ac.jp, current@FreeBSD.ORG Subject: Re: HEADS UP: another syscons update References: <199901201629.AAA20789@spinner.netplex.com.au> From: Dag-Erling Smorgrav Date: 20 Jan 1999 17:53:50 +0100 In-Reply-To: Peter Wemm's message of "Thu, 21 Jan 1999 00:29:54 +0800" Message-ID: Lines: 14 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm writes: > config -r? I'd be highly suprised if this was needed at all for 99% of the > time. The only time that I've been aware of it being needed was quite some > time ago when there was an option that got removed - if people were using > it, that option wouldn't get cleaned out from the .h files, and it caused > a problem somewhere. Old-style options weren't placed in .h files, but passed on the command line, so they broke the dependency system. Perhaps that is what you are referring to? DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 08:58:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA20791 for freebsd-current-outgoing; Wed, 20 Jan 1999 08:58:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA20784 for ; Wed, 20 Jan 1999 08:58:25 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.1/8.9.1) id RAA38766; Wed, 20 Jan 1999 17:58:03 +0100 (CET) (envelope-from des) To: Mike Nguyen Cc: current@FreeBSD.ORG Subject: Re: /etc/nsswitch.conf References: From: Dag-Erling Smorgrav Date: 20 Jan 1999 17:58:01 +0100 In-Reply-To: Mike Nguyen's message of "Wed, 20 Jan 1999 08:53:34 -0600 (CST)" Message-ID: Lines: 18 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Nguyen writes: > I noticed that NetBSD is switching over to using /etc/nsswitch.conf (like > Slowlaris, PH-UX, etc.). Would it be a good idea to do this for FreeBSD too > (when I first started using FreeBSD, it took me a long time to figure out the > analogous file for hostname lookups was /etc/host.conf) -- it seems > consolidating all that config information would in one place would be a good > thing. When I first started using Solaris, it took me a long time to figure out the analoguous file for hostname setup was /etc/nodename. It seems consolidating all that config information in one place, such as /etc/rc.conf, would be a good thing. YMMV. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 09:04:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21278 for freebsd-current-outgoing; Wed, 20 Jan 1999 09:04:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21270 for ; Wed, 20 Jan 1999 09:04:18 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.2/8.9.2/Netplex) with ESMTP id BAA20981; Thu, 21 Jan 1999 01:03:21 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199901201703.BAA20981@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Sheldon Hearn cc: John Polstra , yokota@zodiac.mech.utsunomiya-u.ac.jp, current@FreeBSD.ORG Subject: Re: HEADS UP: another syscons update In-reply-to: Your message of "Wed, 20 Jan 1999 18:46:08 +0200." <73149.916850768@axl.noc.iafrica.com> Date: Thu, 21 Jan 1999 01:03:21 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > > > On Thu, 21 Jan 1999 00:29:54 +0800, Peter Wemm wrote: > > > 'make depend' really does work, and is quite safe. Cleaning the tree > > should be a very rare requirement. > > Perhaps the chap sitting next to me and I are just unlucky. Between the > two of us, we've needed to use ``config -r'' three times since moving > over to CURRENT about two weeks ago. What I pity we didn't save > typescripts for the failures this corrected. :( It's worked a few times in a row for me; some samples: FreeBSD 3.0-CURRENT #384: Sat Jan 16 17:23:36 WST 1999 FreeBSD 3.0-CURRENT #111: Sat Jan 16 14:39:22 WST 1999 FreeBSD 3.0-CURRENT #265: Wed Jan 20 06:02:36 WST 1999 FreeBSD 3.0-CURRENT #61: Mon Jan 18 19:33:08 WST 1999 The first machine has been doing 'config -n' since 1996, with (when necessary) a make clean. It was doing early SMP development which tended to have some scarey consequences on filesystems at times. :-] Are you sure you're doing a 'make depend' after each config(8) run and after building for the first time after a cvsup run or cvs update? Yes, a 'make depend' is required whenever the sources change any of their include files. > Ciao, > Sheldon. Cheers, -Peter -- Peter Wemm Netplex Consulting "No coffee, No workee!" :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 09:07:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21814 for freebsd-current-outgoing; Wed, 20 Jan 1999 09:07:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA21719 for ; Wed, 20 Jan 1999 09:06:36 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA31710 (5.67b/IDA-1.5); Wed, 20 Jan 1999 17:24:53 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id QAA02100; Wed, 20 Jan 1999 16:47:46 +0100 (CET) From: Wilko Bulte Message-Id: <199901201547.QAA02100@yedi.iaf.nl> Subject: Re: Directory structure on current.freebsd.org In-Reply-To: from "paul@originative.co.uk" at "Jan 20, 99 10:53:06 am" To: paul@originative.co.uk Date: Wed, 20 Jan 1999 16:47:46 +0100 (CET) Cc: peter.jeremy@auss2.alcatel.com.au, freebsd-current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As paul@originative.co.uk wrote... > > -----Original Message----- > > From: Peter Jeremy [mailto:peter.jeremy@auss2.alcatel.com.au] > > Sent: Wednesday, January 20, 1999 6:21 AM > > To: freebsd-current@FreeBSD.ORG > > Subject: Re: Directory structure on current.freebsd.org > > > > > > Oliver Fromme wrote: > > >In releases/snapshots they're called "axp" and "x86", while in > > >ports they're called "alpha" and "i386". > > > > I agree that having two different names is confusing. > > > > DEC (or Compaq) literature seems to use both Alpha and AXP - I'm not > > sure that either is an especially better choice. Officially it is Alpha AXP. Alpha was too generic to be trademarked. > > I personally find "i386" a pain because it is used to specify both an > > architecture (IA-32) and a particular implementation (80386) of that > > architecture. In some cases it may not be clear which is meant. > > I think the architecture names are more appropriate than any cpu related > name. For the alpha, while we might all use alpha in everyday speech axp > is more specific when it comes to releases since the alpha release of Hear hear ;-) > the alpha code can get a tad confusing, I think that's why it was > changed in the first place. It'd be nice if i386 could become IA32 but > it probably won't happen. Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 09:11:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22210 for freebsd-current-outgoing; Wed, 20 Jan 1999 09:11:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22201 for ; Wed, 20 Jan 1999 09:11:04 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.10 #1) id 10318r-000MOP-00; Wed, 20 Jan 1999 19:10:09 +0200 From: Sheldon Hearn To: Peter Wemm cc: John Polstra , yokota@zodiac.mech.utsunomiya-u.ac.jp, current@FreeBSD.ORG Subject: Re: HEADS UP: another syscons update In-reply-to: Your message of "Thu, 21 Jan 1999 01:03:21 +0800." <199901201703.BAA20981@spinner.netplex.com.au> Date: Wed, 20 Jan 1999 19:10:09 +0200 Message-ID: <86080.916852209@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 21 Jan 1999 01:03:21 +0800, Peter Wemm wrote: > The first machine has been doing 'config -n' since 1996 Don't get me wrong, config _usually_ works for us without ``-r''. But we got bitten once or twice and have since opted for ``config -r'', since that's what fixed things for us when we had trouble. > Are you sure you're doing a 'make depend' after each config(8) run and > after building for the first time after a cvsup run or cvs update? Dead sure. That's a habit we got into with STABLE, even. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 09:58:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA26097 for freebsd-current-outgoing; Wed, 20 Jan 1999 09:58:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peacock.tci.com (coral.tci.com [198.178.8.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA26091 for ; Wed, 20 Jan 1999 09:58:21 -0800 (PST) (envelope-from chris@tci.com) Received: from guido.tci.com (guido.tci.com [165.137.145.151]) by peacock.tci.com (8.9.0/8.9.0) with ESMTP id KAA03623; Wed, 20 Jan 1999 10:58:13 -0700 (MST) Received: from tci.com (localhost [127.0.0.1]) by guido.tci.com (8.9.1b+Sun/8.9.1) with ESMTP id KAA04542; Wed, 20 Jan 1999 10:58:08 -0700 (MST) Message-ID: <36A6192F.7C253E7E@tci.com> Date: Wed, 20 Jan 1999 10:58:07 -0700 From: Chris Tubutis Organization: Tele-Communications, Inc. X-Mailer: Mozilla 4.5 [en] (X11; U; SunOS 5.7 sun4m) X-Accept-Language: en MIME-Version: 1.0 To: Dag-Erling Smorgrav CC: Mike Nguyen , current@FreeBSD.ORG Subject: Re: /etc/nsswitch.conf References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: > > Mike Nguyen writes: > > I noticed that NetBSD is switching over to using /etc/nsswitch.conf (like > > Slowlaris, PH-UX, etc.). Would it be a good idea to do this for FreeBSD too > > (when I first started using FreeBSD, it took me a long time to figure out the > > analogous file for hostname lookups was /etc/host.conf) -- it seems > > consolidating all that config information would in one place would be a good > > thing. > > When I first started using Solaris, it took me a long time to figure > out the analoguous file for hostname setup was /etc/nodename. It seems > consolidating all that config information in one place, such as > /etc/rc.conf, would be a good thing. I agree; I deal with Solaris, Linux and FreeBSD every day. This may sound pretty Redmondish, but imho the more that things are the same, the better. ct To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 10:26:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29082 for freebsd-current-outgoing; Wed, 20 Jan 1999 10:26:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from server.amis.net (server.amis.net [195.10.52.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA29070 for ; Wed, 20 Jan 1999 10:26:23 -0800 (PST) (envelope-from blaz@gold.amis.net) Received: (from uucp@localhost) by server.amis.net (8.8.8/8.8.8) with UUCP id TAA20322 for freebsd-current@freebsd.org; Wed, 20 Jan 1999 19:26:04 +0100 (CET) Received: (qmail 310 invoked by uid 1000); 20 Jan 1999 18:25:26 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 20 Jan 1999 18:25:26 -0000 Date: Wed, 20 Jan 1999 19:25:26 +0100 (CET) From: Blaz Zupan To: freebsd-current@FreeBSD.ORG Subject: Cosmetic issues with ISDN startup Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am experiencing two rather cosmetic issues with how the ISDN subsystem starts up. The first is, that when you enable isdnd, syslogd is not yet running. So isdnd outputs a whole lot of garbage (basically the whole configuration) to the console. This patch to /usr/src/usr.sbin/i4b/isdnd/log.c solves the mess: *** log.c.old Sun Dec 27 22:47:01 1998 --- log.c Wed Jan 20 18:57:08 1999 *************** *** 100,106 **** logfacility); else #endif ! (void)openlog("isdnd", LOG_PID|LOG_CONS|LOG_NDELAY, logfacility); } --- 100,106 ---- logfacility); else #endif ! (void)openlog("isdnd", LOG_PID|LOG_NDELAY, logfacility); } I really don't believe the messages are urgent enough to warrant LOG_CONS, considering that named doesn't openlog() with LOG_CONS either. The next issue is in /etc/rc.network. When you solve the above mess, you get this during startup: Doing initial network setup: hostname. isdnd ... [rest of messages] I belive the isdnd should be output on the previous line, this patches fixes it: *** rc.network.old Thu Jan 14 00:18:07 1999 --- rc.network Wed Jan 20 19:20:28 1999 *************** *** 23,39 **** domainname $nisdomainname echo -n ' domain' fi echo '.' # Initial ATM interface configuration if [ "X${atm_enable}" = X"YES" -a -f /etc/rc.atm ]; then . /etc/rc.atm atm_pass1 - fi - - # ISDN subsystem startup - if [ "X${isdn_enable}" = X"YES" -a -f /etc/rc.isdn ]; then - . /etc/rc.isdn fi # Special options for sppp(4) interfaces go here. These need --- 23,40 ---- domainname $nisdomainname echo -n ' domain' fi + + # ISDN subsystem startup + if [ "X${isdn_enable}" = X"YES" -a -f /etc/rc.isdn ]; then + . /etc/rc.isdn + fi + echo '.' # Initial ATM interface configuration if [ "X${atm_enable}" = X"YES" -a -f /etc/rc.atm ]; then . /etc/rc.atm atm_pass1 fi # Special options for sppp(4) interfaces go here. These need Best regards, Blaz Zupan, blaz@medinet.si, http://home.amis.net/blaz Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 10:34:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA00557 for freebsd-current-outgoing; Wed, 20 Jan 1999 10:34:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picalon.gun.de (picalon.gun.de [194.77.0.18] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA00551 for ; Wed, 20 Jan 1999 10:34:26 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.8.6/8.8.6) with ESMTP id TAA01894; Wed, 20 Jan 1999 19:34:10 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.2/8.9.2) id TAA01578; Wed, 20 Jan 1999 19:33:55 +0100 (CET) (envelope-from andreas) Date: Wed, 20 Jan 1999 19:33:54 +0100 From: Andreas Klemm To: Matthew Dillon Cc: Andreas Klemm , current@FreeBSD.ORG Subject: Re: panic: vinvalbuf: dirty bufs (during reboot, several times) Message-ID: <19990120193354.A1554@titan.klemm.gtn.com> References: <19990120073445.A402@titan.klemm.gtn.com> <199901200700.XAA76802@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199901200700.XAA76802@apollo.backplane.com>; from Matthew Dillon on Tue, Jan 19, 1999 at 11:00:55PM -0800 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 19, 1999 at 11:00:55PM -0800, Matthew Dillon wrote: > > Hmm. Interesting, it's dying trying to fsync an FFS vnode. Are you > by any chance running NFS ( client *or* server ) on this box? No, no NFS compiled in and am not using it. See my kernel config. > First, if either of you are compiling up your own kernels, please > remember that if you are using SOFTUPDATES, the SOFTUPDATES code > does *NOT* reside in /usr/src/sys but instead resides in > /usr/src/contrib/sys ... when you update your kernel, also make sure > that /usr/src/contrib/sys is updated. I know this, but checked it to be sure, yes I use the 'up to date' softupdate source from contrib/sys. * from: @(#)ffs_softdep.c 9.28 (McKusick) 8/8/98 * $Id: ffs_softdep.c,v 1.20 1999/01/07 16:14:10 bde Exp $ * @(#)softdep.h 9.5 (McKusick) 2/11/98 * $Id: softdep.h,v 1.4 1998/05/19 23:07:25 julian Exp $ > If I can reproduce it on one of my machines, I can probably figure out > what is going on. If both of you are running NFS, it could possibly be > the NFS server forgetting to unbusy a page somewhere. If you aren't > running NFS, it could be an actual bug in FFS somewhere(!). No NFS. -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 11:06:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05169 for freebsd-current-outgoing; Wed, 20 Jan 1999 11:06:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05136 for ; Wed, 20 Jan 1999 11:06:23 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.1/8.9.1) id VAA04468; Wed, 20 Jan 1999 21:05:50 +0200 (SAT) From: John Hay Message-Id: <199901201905.VAA04468@zibbi.mikom.csir.co.za> Subject: Re: HEADS UP: another syscons update In-Reply-To: <199901201629.AAA20789@spinner.netplex.com.au> from Peter Wemm at "Jan 21, 99 00:29:54 am" To: peter@netplex.com.au (Peter Wemm) Date: Wed, 20 Jan 1999 21:05:50 +0200 (SAT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > > Is "make clean" really necessary? A "make depend" ought to be > > > sufficient, I would think. > > > > I think that's an attempt to protect people who've upgraded from STABLE > > and haven't gotten used to ``config -r''? > > config -r? I'd be highly suprised if this was needed at all for 99% of the > time. The only time that I've been aware of it being needed was quite some > time ago when there was an option that got removed - if people were using > it, that option wouldn't get cleaned out from the .h files, and it caused > a problem somewhere. I don't remember the specifics, it was a long time > ago. The only other time I can think of where this might be needed is > when the system clock gets screwed and the *.h files get future dates on > them. In just about all other cases, a 'make clean' is sufficient to > start the tree from scratch if there are any suspicions about old files. The place where it really bytes is when options move from one *.h to another. Especially if you then change it. :-) I wish config would remove old options out of *.h files. John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 11:23:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06803 for freebsd-current-outgoing; Wed, 20 Jan 1999 11:23:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA06798 for ; Wed, 20 Jan 1999 11:23:57 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id LAA05838; Wed, 20 Jan 1999 11:23:41 -0800 (PST) (envelope-from dillon) Date: Wed, 20 Jan 1999 11:23:41 -0800 (PST) From: Matthew Dillon Message-Id: <199901201923.LAA05838@apollo.backplane.com> To: Bjoern Fischer Cc: current@FreeBSD.ORG Subject: Re: panic: vinvalbuf: dirty bufs (during reboot, several times) References: <19990120073445.A402@titan.klemm.gtn.com> <199901200700.XAA76802@apollo.backplane.com> <19990120132700.A15521@voliere.TechFak.Uni-Bielefeld.DE> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :ok, here are some instructions which -- I hope -- reproduce it :(I haven't found a *nice* way; this is the ridiculous way): : :NFS server and client are completely 3.0-CURRENT :(of CTM src-cur.3712.gz) with Luoqi's NFS fix. The server has all :(physical) file systems mounted with softupdates except `/'. : :On the client simply edit `http://www.freebsd.org/~yokota/sc_update.txt' :... :After the vi-SEGV try to shutdown the server with `shutdown -[rh] now'. :You may shutdown the client first -- it makes no difference. :Then you will get the panic. : :Good luck. : : Bjoern Good work! I can repeat the SEGV fault. The SEGV is being caused by a bug in NFS which I haven't tracked down yet, but basically what happens is that vi tries to create a recovery file and uses lseek() to skip around a little, then seek's back and reads something it just wrote. Over NFS, this blew up -- it didn't read what it wrote. cc x.c -o x cd somewhere ( into NFS partition on NFS client ) ./x | hexdump cd localfilesystem /path/x | hexdump I do not know if this related to the non-NFS panic. When I find the bug, we'll know better. This should be easy. -Matt #include #include #include #include char buf[4096]; int main(int ac, char **av) { int fd = open("test", O_RDWR|O_CREAT|O_TRUNC, 0666); int n; memset(buf, 1, 4096); write(fd, buf, 1024); lseek(fd, 0x800, 0); write(fd, buf, 1024); lseek(fd, 0xC00, 0); write(fd, buf, 1024); lseek(fd, 0x1000, 0); write(fd, buf, 1024); lseek(fd, 0x1400, 0); write(fd, buf, 1024); lseek(fd, 0x1800, 0); write(fd, buf, 1024); lseek(fd, 0x800, 0); read(fd, buf, 1024); write(1, buf, 1024); return(0); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 12:24:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13428 for freebsd-current-outgoing; Wed, 20 Jan 1999 12:24:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA13422 for ; Wed, 20 Jan 1999 12:24:06 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id MAA06937; Wed, 20 Jan 1999 12:23:59 -0800 (PST) (envelope-from dillon) Date: Wed, 20 Jan 1999 12:23:59 -0800 (PST) From: Matthew Dillon Message-Id: <199901202023.MAA06937@apollo.backplane.com> To: Bjoern Fischer , current@FreeBSD.ORG Subject: Re: panic: vinvalbuf: dirty bufs (during reboot, several times) References: <19990120073445.A402@titan.klemm.gtn.com> <199901200700.XAA76802@apollo.backplane.com> <19990120132700.A15521@voliere.TechFak.Uni-Bielefeld.DE> <199901201923.LAA05838@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Try this. In nfs_bioread(), nfs/nfs_bio.c: Before, it was: if (getpages && !(bp->b_flags & B_VMIO)) { #ifdef DIAGNOSTIC printf("nfs_bioread: non vmio buf found, discarding\n"); Try changin the if() to this: if ( (getpages && !(bp->b_flags & B_VMIO)) || (bp->b_flags & (B_CACHE|B_DELWRI)) == B_DELWRI ) { #ifdef DIAGNOSTIC printf("nfs_bioread: non vmio buf found, discarding\n"); #endif I believe what is going on is that bioread() is misinterpreting B_CACHE to mean that it can discard the entire buffer. If B_DELWRI is set, however, it must sync the buffer first. What is occuring is that when a program write()'s non-contiguously and then lseek's back and read()'s again, B_CACHE is getting cleared and the buffer is being re-read from NFS without first being flushed to NFS, causing the written data to be overwritten by the read. I have NOT tested this well. It seems to solve the vi SEG fault problem. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 12:27:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13725 for freebsd-current-outgoing; Wed, 20 Jan 1999 12:27:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles232.castles.com [208.214.165.232]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA13712 for ; Wed, 20 Jan 1999 12:27:40 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA01056; Wed, 20 Jan 1999 12:23:39 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901202023.MAA01056@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Archie Cobbs cc: dfr@nlsystems.com (Doug Rabson), gelderen@mediaport.org, current@FreeBSD.ORG Subject: Re: KLD naming In-reply-to: Your message of "Tue, 19 Jan 1999 22:12:43 PST." <199901200612.WAA20699@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 20 Jan 1999 12:23:38 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > When I first started writing KLD, I had a vague notion that there would be > > a simple directory structure under /modules, e.g.: > > > > /modules > > pci/ > > ncr.ko > > ... > > isa/ > > if_ed.ko > > ... > > ... > > I like this idea (subdirectories) better.. it will last longer :-) It's a really bad idea, because it requires you to classify things. It also makes it much harder to administer. In addition, classifications are bad (witness the need to reorganise the kernel source tree). > You should then be able to load a module "isa/if_ed.ko" etc > and have it work (no leading slash). And here is a good example. Why would you want to put if_ed in the "ISA" category when it can be attached to both the PCI and ISA busses? > In fact, we can implement this (maybe it already works) before > coming to a final decision on what the actual layout should be. A single directory holding module files. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 12:30:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14320 for freebsd-current-outgoing; Wed, 20 Jan 1999 12:30:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14312 for ; Wed, 20 Jan 1999 12:30:49 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id MAA06970; Wed, 20 Jan 1999 12:30:43 -0800 (PST) (envelope-from dillon) Date: Wed, 20 Jan 1999 12:30:43 -0800 (PST) From: Matthew Dillon Message-Id: <199901202030.MAA06970@apollo.backplane.com> To: Matthew Dillon Cc: Bjoern Fischer , current@FreeBSD.ORG Subject: Re: panic: vinvalbuf: dirty bufs (during reboot, several times) References: <19990120073445.A402@titan.klemm.gtn.com> <199901200700.XAA76802@apollo.backplane.com> <19990120132700.A15521@voliere.TechFak.Uni-Bielefeld.DE> <199901201923.LAA05838@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (This is mainly for Luoqi, John, or David, or anyone who understands struct buf's and NFS). I see some other weirdness in bread() relating to NFS as well. int bread(struct vnode * vp, daddr_t blkno, int size, struct ucred * cred, struct buf ** bpp) { struct buf *bp; bp = getblk(vp, blkno, size, 0, 0); *bpp = bp; /* if not found in cache, do some I/O */ if ((bp->b_flags & B_CACHE) == 0) { if (curproc != NULL) curproc->p_stats->p_ru.ru_inblock++; bp->b_flags |= B_READ; bp->b_flags &= ~(B_DONE | B_ERROR | B_INVAL); if (bp->b_rcred == NOCRED) { if (cred != NOCRED) crhold(cred); bp->b_rcred = cred; } vfs_busy_pages(bp, 0); VOP_STRATEGY(vp, bp); return (biowait(bp)); } return (0); } The question is: Do we have to check for B_DELWRI here and flush the bp before we issue the read op? -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 12:31:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14396 for freebsd-current-outgoing; Wed, 20 Jan 1999 12:31:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles232.castles.com [208.214.165.232]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14387 for ; Wed, 20 Jan 1999 12:31:33 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA01089; Wed, 20 Jan 1999 12:27:57 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901202027.MAA01089@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "John Saunders" cc: freebsd-current@FreeBSD.ORG Subject: Re: Booting -current with new loader In-reply-to: Your message of "20 Jan 1999 17:52:42 +1100." <19990120065242.9754.qmail@nhj.nlc.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 20 Jan 1999 12:27:57 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm not sure about anybody else here, but to my mind a "Winblows on C: > drive and let's try out FreeBSD on the second disk" configuration should > really be supported seamlessly. You're more than welcome to propose a technical solution that solves the problem. > The option of putting the second drive > as slave on the primary interface would work, however anybody that knows > anything about IDE (read somebdy interested in trying FreeBSD) would put > it on the second interface for speed reasons. Er, you want to stop and think about that for a second? If you have Windows on one disk and FreeBSD on the other, where is the opportiunity for drive conflicts (the source of performance loss)? You'd be much better off with both disks on the primary controller and your CDROM on the secondary controller if you cared about performance. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 12:47:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16351 for freebsd-current-outgoing; Wed, 20 Jan 1999 12:47:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA16345 for ; Wed, 20 Jan 1999 12:47:50 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id MAA06444; Wed, 20 Jan 1999 12:46:57 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma006440; Wed, 20 Jan 99 12:46:37 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id MAA23549; Wed, 20 Jan 1999 12:46:37 -0800 (PST) From: Archie Cobbs Message-Id: <199901202046.MAA23549@bubba.whistle.com> Subject: Re: KLD naming In-Reply-To: <199901202023.MAA01056@dingo.cdrom.com> from Mike Smith at "Jan 20, 99 12:23:38 pm" To: mike@smith.net.au (Mike Smith) Date: Wed, 20 Jan 1999 12:46:36 -0800 (PST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: > > > When I first started writing KLD, I had a vague notion that there would be > > > a simple directory structure under /modules, e.g.: > > > > > > /modules > > > pci/ > > > ncr.ko > > > ... > > > isa/ > > > if_ed.ko > > > ... > > > ... > > > > I like this idea (subdirectories) better.. it will last longer :-) > > It's a really bad idea, because it requires you to classify things. It > also makes it much harder to administer. In addition, classifications > are bad (witness the need to reorganise the kernel source tree). > > > You should then be able to load a module "isa/if_ed.ko" etc > > and have it work (no leading slash). > > And here is a good example. Why would you want to put if_ed in the > "ISA" category when it can be attached to both the PCI and ISA busses? I don't care how you classify it.. of course the "isa" category is wrong. I was just pointing out that having things in subdirectories is better than having a zillion files piled into a single directory. > are bad (witness the need to reorganise the kernel source tree). Maybe I'm just an optimist.. but if we have already solved (through various incarnations) how to classify the kernel source, then we can pretty much inherit this same classification scheme for the modules. After all, they are all *kernel* modules, right? > A single directory holding module files. Blech :-) -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 13:49:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23694 for freebsd-current-outgoing; Wed, 20 Jan 1999 13:49:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from friley-185-114.res.iastate.edu (friley-185-114.res.iastate.edu [129.186.185.114]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA23676 for ; Wed, 20 Jan 1999 13:49:30 -0800 (PST) (envelope-from ccsanady@friley-185-114.res.iastate.edu) Received: from friley-185-114.res.iastate.edu (localhost.res.iastate.edu [127.0.0.1]) by friley-185-114.res.iastate.edu (8.9.1/8.9.1) with ESMTP id PAA61128; Wed, 20 Jan 1999 15:48:37 -0600 (CST) (envelope-from ccsanady@friley-185-114.res.iastate.edu) Message-Id: <199901202148.PAA61128@friley-185-114.res.iastate.edu> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Nguyen cc: current@FreeBSD.ORG Subject: Re: /etc/nsswitch.conf In-reply-to: Your message of "Wed, 20 Jan 1999 08:53:34 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 20 Jan 1999 15:48:37 -0600 From: Chris Csanady Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I noticed that NetBSD is switching over to using /etc/nsswitch.conf (like >Slowlaris, PH-UX, etc.). Would it be a good idea to do this for FreeBSD too >(when I first started using FreeBSD, it took me a long time to figure out the >analogous file for hostname lookups was /etc/host.conf) -- it seems >consolidating all that config information would in one place would be a good >thing. I would really like to see this integrated into FreeBSD. Does anyone have any plans to do this? It would be really nice to be able to do lookups using hesiod or perhaps even LDAP. Btw, has anyone looked at nsd in Irix6.5? It is quite interesting.. Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 14:27:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA26627 for freebsd-current-outgoing; Wed, 20 Jan 1999 14:27:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ozz.etrust.ru (ozz.etrust.ru [195.2.84.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA26619 for ; Wed, 20 Jan 1999 14:27:27 -0800 (PST) (envelope-from osa@etrust.ru) Received: from localhost (localhost [127.0.0.1]) by ozz.etrust.ru (8.9.2/8.9.1) with ESMTP id BAA02040 for ; Thu, 21 Jan 1999 01:19:31 +0300 (MSK) (envelope-from osa@etrust.ru) Date: Thu, 21 Jan 1999 01:19:31 +0300 (MSK) From: oZZ!!! To: current@FreeBSD.ORG Subject: New tag for -STABLE? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=KOI8-R Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! What is new tag for -STABLE? RELENG_3_1 ? Rgdz, ïÓÏËÉÎ óÅÒÇÅÊ aka oZZ, osa@etrust.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 15:07:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00176 for freebsd-current-outgoing; Wed, 20 Jan 1999 15:07:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00166 for ; Wed, 20 Jan 1999 15:07:25 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id SAA29406 for ; Wed, 20 Jan 1999 18:07:22 -0500 (EST) Date: Wed, 20 Jan 1999 18:07:22 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: current@FreeBSD.ORG Subject: Truth to M_WAITOK? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Would someone PLEASE tell us all if malloc can really return NULL now with flags & M_WAITOK? I've gotten contradictory answers... Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 15:20:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA01622 for freebsd-current-outgoing; Wed, 20 Jan 1999 15:20:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles232.castles.com [208.214.165.232]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA01610 for ; Wed, 20 Jan 1999 15:20:33 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA03949; Wed, 20 Jan 1999 15:16:57 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901202316.PAA03949@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Feldman cc: current@FreeBSD.ORG Subject: Re: Truth to M_WAITOK? In-reply-to: Your message of "Wed, 20 Jan 1999 18:07:22 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 20 Jan 1999 15:16:56 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Would someone PLEASE tell us all if malloc can really return NULL now with > flags & M_WAITOK? I've gotten contradictory answers... I went back and looked at the code again. It looks like M_WAITOK will either return non-NULL or panic; it shouldn't be capable of returning NULL. Ideally, it shouldn't panic either (why is it only that M_WAITOK can panic, and M_NOWAIT can't?). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 15:39:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03798 for freebsd-current-outgoing; Wed, 20 Jan 1999 15:39:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles232.castles.com [208.214.165.232]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03792 for ; Wed, 20 Jan 1999 15:39:47 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA04090; Wed, 20 Jan 1999 15:36:15 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901202336.PAA04090@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Archie Cobbs cc: current@FreeBSD.ORG Subject: Re: KLD naming In-reply-to: Your message of "Wed, 20 Jan 1999 12:46:36 PST." <199901202046.MAA23549@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 20 Jan 1999 15:36:14 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [KLD module file locations] > I was just pointing out that having things in subdirectories > is better than having a zillion files piled into a single directory. I'm torn between agreeing that it's tidier and disagreeing on the grounds that it's much more of a pain to administer. "Where is that damnned module?" "Why am I loading a stale version of saver_foo?", etc. As a rule when I'm thinking about KLDs I look at the way that MacOS manages inits/extensions. That's a model that's survived over a decade of use by generally fairly clueless users, and hasn't completely irritated the smarter ones either. > > are bad (witness the need to reorganise the kernel source tree). > > Maybe I'm just an optimist.. but if we have already solved (through > various incarnations) how to classify the kernel source, then we can > pretty much inherit this same classification scheme for the modules. The fact that we're trying to reorganise the kernel sources right now tends to indicate to me that we haven't solved this at all. > > A single directory holding module files. > > Blech :-) Put aside the aesthetics for a moment, and try to raise some real, practical objections. I'm continually battling my own temptation to make the whole module thing more complex, but if you've got really good reasons that can justify the extra complexity everywhere I'm still open to suggestions. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 15:47:16 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04367 for freebsd-current-outgoing; Wed, 20 Jan 1999 15:47:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04362 for ; Wed, 20 Jan 1999 15:47:13 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id KAA13074; Thu, 21 Jan 1999 10:46:57 +1100 Date: Thu, 21 Jan 1999 10:46:57 +1100 From: Bruce Evans Message-Id: <199901202346.KAA13074@godzilla.zeta.org.au> To: green@unixhelp.org, mike@smith.net.au Subject: Re: Truth to M_WAITOK? Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >It looks like M_WAITOK will either return non-NULL or panic; it >shouldn't be capable of returning NULL. Ideally, it shouldn't panic >either (why is it only that M_WAITOK can panic, and M_NOWAIT can't?). Because failures for M_NOWAIT are normal (all pages may be in use, and the caller is not prepared for pages top be freed by swapping). Therefore, callers that set M_NOWAIT must be prepared for failure. OTOH, failures for M_WAITOK are abnormal, and at least for map == kmem_map (as it is for calls to kmem_malloc() from malloc()), the correct handling for failure is to panic since a full map is unlikely to become unfull and neither the caller or kmem_malloc() can know what to do to unfill it. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 15:50:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04795 for freebsd-current-outgoing; Wed, 20 Jan 1999 15:50:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles232.castles.com [208.214.165.232]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04789 for ; Wed, 20 Jan 1999 15:50:28 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA04181; Wed, 20 Jan 1999 15:46:39 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901202346.PAA04181@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bruce Evans cc: green@unixhelp.org, mike@smith.net.au, current@FreeBSD.ORG Subject: Re: Truth to M_WAITOK? In-reply-to: Your message of "Thu, 21 Jan 1999 10:46:57 +1100." <199901202346.KAA13074@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 20 Jan 1999 15:46:39 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >It looks like M_WAITOK will either return non-NULL or panic; it > >shouldn't be capable of returning NULL. Ideally, it shouldn't panic > >either (why is it only that M_WAITOK can panic, and M_NOWAIT can't?). > > Because failures for M_NOWAIT are normal (all pages may be in use, > and the caller is not prepared for pages top be freed by swapping). > Therefore, callers that set M_NOWAIT must be prepared for failure. OTOH, > failures for M_WAITOK are abnormal, and at least for map == kmem_map (as > it is for calls to kmem_malloc() from malloc()), the correct handling > for failure is to panic since a full map is unlikely to become unfull > and neither the caller or kmem_malloc() can know what to do to unfill it. Bear with the ignorance a moment; how is a full map any different to no more kmem space? In the "out of kmem" case, we call VM_WAIT and retry. Why not do this in the kmem_map full case as well? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 16:00:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA06124 for freebsd-current-outgoing; Wed, 20 Jan 1999 16:00:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA06119 for ; Wed, 20 Jan 1999 16:00:35 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id BAA19057; Thu, 21 Jan 1999 01:06:45 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Thu, 21 Jan 1999 01:06:45 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Archie Cobbs cc: Mike Smith , current@FreeBSD.ORG Subject: Re: KLD naming In-Reply-To: <199901202046.MAA23549@bubba.whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 20 Jan 1999, Archie Cobbs wrote: > > > I like this idea (subdirectories) better.. it will last longer :-) > > > > It's a really bad idea, because it requires you to classify things. It > > also makes it much harder to administer. In addition, classifications > > are bad (witness the need to reorganise the kernel source tree). > > > > > You should then be able to load a module "isa/if_ed.ko" etc > > > and have it work (no leading slash). > > > > And here is a good example. Why would you want to put if_ed in the > > "ISA" category when it can be attached to both the PCI and ISA busses? > > I don't care how you classify it.. of course the "isa" category is wrong. > > I was just pointing out that having things in subdirectories > is better than having a zillion files piled into a single directory. Not always. Consider a case when all modules are on a slow media (such as a floppy or zipfs) - then putting things in subdirs adds quite significant overhead to load/ls/search due to pathname lookups. Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 16:12:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA07434 for freebsd-current-outgoing; Wed, 20 Jan 1999 16:12:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA07419 for ; Wed, 20 Jan 1999 16:12:25 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id LAA15843; Thu, 21 Jan 1999 11:12:16 +1100 Date: Thu, 21 Jan 1999 11:12:16 +1100 From: Bruce Evans Message-Id: <199901210012.LAA15843@godzilla.zeta.org.au> To: bde@zeta.org.au, mike@smith.net.au Subject: Re: Truth to M_WAITOK? Cc: current@FreeBSD.ORG, green@unixhelp.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Bear with the ignorance a moment; how is a full map any different to no >more kmem space? I'd call them the same. The map is kmem_map for malloc(), and running out of space in that map is fatal. When the map fills up, it is usually not really full, it is just so fragmented that contiguous space can't be found for the larger than usual allocation in the current request. Freeing memory in the map won't necessarily reduce fragmentation. The map must be quite sparse to work at all. >In the "out of kmem" case, we call VM_WAIT and retry. Why not do this >in the kmem_map full case as well? I'd call that the the out of general memory (pages) case. This is non- fatal because normally lots of memory is allocated to applications and it is easy to free some by swapping. There are no fragmentation problems since pages can be mapped anywhere in virtual memory. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 16:25:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA08793 for freebsd-current-outgoing; Wed, 20 Jan 1999 16:25:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.kersur.net (mail.kersur.net [199.79.199.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA08768 for ; Wed, 20 Jan 1999 16:25:06 -0800 (PST) (envelope-from dswartz@druber.com) Received: from manticore (manticore.druber.com [207.180.95.108]) by mail.kersur.net (8.9.1/8.9.1) with SMTP id TAA05726; Wed, 20 Jan 1999 19:26:30 -0500 (EST) Message-Id: <3.0.5.32.19990120192420.0097b5f0@mail.kersur.net> X-Sender: druber@mail.kersur.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 20 Jan 1999 19:24:20 -0500 To: Mike Smith From: Dan Swartzendruber Subject: Re: Truth to M_WAITOK? Cc: Bruce Evans , green@unixhelp.org, mike@smith.net.au, current@FreeBSD.ORG In-Reply-To: <199901202346.PAA04181@dingo.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 03:46 PM 1/20/99 -0800, Mike Smith wrote: >> >It looks like M_WAITOK will either return non-NULL or panic; it >> >shouldn't be capable of returning NULL. Ideally, it shouldn't panic >> >either (why is it only that M_WAITOK can panic, and M_NOWAIT can't?). >> >> Because failures for M_NOWAIT are normal (all pages may be in use, >> and the caller is not prepared for pages top be freed by swapping). >> Therefore, callers that set M_NOWAIT must be prepared for failure. OTOH, >> failures for M_WAITOK are abnormal, and at least for map == kmem_map (as >> it is for calls to kmem_malloc() from malloc()), the correct handling >> for failure is to panic since a full map is unlikely to become unfull >> and neither the caller or kmem_malloc() can know what to do to unfill it. > >Bear with the ignorance a moment; how is a full map any different to no >more kmem space? > >In the "out of kmem" case, we call VM_WAIT and retry. Why not do this >in the kmem_map full case as well? I've stayed out of this until now, but here's my 2 cents. I never understood why so much Unix code can't be bothered to check error codes. If the semantics for a procedure are to return NULL if it can't get the buffer without waiting, fine. I don't understand why that implies that specifying that you are willing to wait means the routine can never fail. If it is true that an allocation routine will never normally fail when WAITOK is specified, that still doesn't mean that some implementation or other couldn't return NULL on some kind of pathological error. Maybe not in this subsystem, but I don't like the precedent that is set. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 16:58:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA13895 for freebsd-current-outgoing; Wed, 20 Jan 1999 16:58:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nhj.nlc.net.au (nhj.nlc.net.au [203.24.133.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA13890 for ; Wed, 20 Jan 1999 16:58:23 -0800 (PST) (envelope-from john.saunders@nlc.net.au) Received: (qmail 15705 invoked by uid 1000); 21 Jan 1999 11:58:13 +1100 From: "John Saunders" Date: Thu, 21 Jan 1999 11:58:13 +1100 (EST) To: Mike Smith cc: freebsd-current@FreeBSD.ORG Subject: Re: Booting -current with new loader In-Reply-To: <199901202027.MAA01089@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 20 Jan 1999, Mike Smith wrote: > > The option of putting the second drive > > as slave on the primary interface would work, however anybody that knows > > anything about IDE (read somebdy interested in trying FreeBSD) would put > > it on the second interface for speed reasons. > > Er, you want to stop and think about that for a second? If you have > Windows on one disk and FreeBSD on the other, where is the opportiunity > for drive conflicts (the source of performance loss)? In the context of one disk totally Windows and the other totally FreeBSD then yes you are correct. However I have a 1 Gig partition at the end of both disks that I have a CCD mirror on. Read performance won't suffer by moving the drive but write performance halves. Actually I have intended to modify CCD so that is distributes reads over all devices in the mirror, I noticed that it simply hammers the first drive. I'm not sure if core would be interested in such a patch since I think vinum is taking over. That's why I shy away from moving my hardware around. Also I would have to break out the screw driver, when all I need is some finger work. > > I'm not sure about anybody else here, but to my mind a "Winblows on C: > > drive and let's try out FreeBSD on the second disk" configuration should > > really be supported seamlessly. > > You're more than welcome to propose a technical solution that solves > the problem. OK, the technical solution that I propose is an alternative (optional because I want to retain the current semantics) config semantics. controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0xa0ffa0ff controller wdc1 at isa? port "IO_WD2" bio irq 15 flags 0xa0ffa0ff disk wd? at wdc? This would act identical to the way the SCSI system works by assigning names to disks as they get probed. It would also have the advantage of assigning disk names in the same order as the BIOS (and thereby the boot loader), hence there would be a 1 to 1 mapping between what the boot loader uses and what the FreeBSD kernel detects. I believe the current problem stems from the BIOS (and thereby the boot loader) and the FreeBSD kernel assigning names using a different algorithm and then getting out of step when the kernel skips a name. If anybody knows how to do this quickly then I am happy to help test it. Cheers. -- +------------------------------------------------------------+ . | John Saunders - mailto:john@nlc.net.au (EMail) | ,--_|\ | - http://www.nlc.net.au/ (WWW) | / Oz \ | - 02-9489-4932 or 041-822-3814 (Phone) | \_,--\_/ | NHJ NORTHLINK COMMUNICATIONS - Supplying a professional, | v | and above all friendly, internet connection service. | +------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 17:52:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA18997 for freebsd-current-outgoing; Wed, 20 Jan 1999 17:52:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA18990 for ; Wed, 20 Jan 1999 17:52:30 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40340>; Thu, 21 Jan 1999 12:51:34 +1100 Date: Thu, 21 Jan 1999 12:52:12 +1100 From: Peter Jeremy Subject: Experiences with aout-to-elf and new bootblocks To: current@FreeBSD.ORG Message-Id: <99Jan21.125134est.40340@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been experimenting with moving a 2.2.6-RELEASE system to 3.0 (-current for now, but probably moving towards -stable). Not wanting to totally trash my current system until I have the new one working, I've been building 3.0 on a second disk [mounted as /3.0 on my 2.x system]. I'm using CTM 'cvs-cur 4996' as a base. My experiences with 'DESTDIR=/3.0 make aout-to-elf' are: 1) The _real_ system libraries are moved, rather than the ones relative to /3.0. I then need to manually move them back and repeat the ldconfig to keep my 2.x system consistent. 2) The miniperl built during the perl5 build looks in /usr/libdata/perl for it's libraries, although they're installed in /3.0/usr/libdata/perl. A manual symbolic link fixed that. 3) During the kernel build (do_aout_kernel), config fails because it is using the 2.x config instead of the one it just built. I solved this with "chroot /3.0 'build kernel'" Other than the above, everything worked (although I wasn't game to try the do_install_kernel_reboot step and installed the new kernel manually). [I also needed to manually run 'make distribution' in .../src/etc to initially populate the new /etc - before manually transferring my system configuration]. I then had a look at the new bootblocks (following Peter's elfday tutorial: http://www.freebsd.org/~peter/elfday.html). I found that /boot/loader could load my 2.x kernel (although it happily handled [gzip'd] -current kernels in both a.out and ELF format). The stage2 loader boot: prompt happily loaded the 2.x kernel. When /boot/loader tries to load my 2.x kernel, the screen displays gibberish and the system locks up (hard reset needed). Any ideas on this one? Finally, whilst I can happily load a 3.x kernel from my 2nd HD, the kernel is confused about where it's loading from: It can't find root and panics. System details: PII-266 with IDE disks: primary master: wd0: dualboot (W95/FreeBSD 2.x) primary slave: ATAPI cdrom secondary master: wd2: FreeBSD 3.0 (not dangerously dedicated) secondary slave: not present Both the 2.x and -current kernels correctly recognize both disks during the probes. When I try to boot from wd2a, the kernel reports: changing root device to wd1s1a changing root device to wd1a error 6: panic cannot mount root(2) If I recall correctly, the problem here is that the BIOS is reporting the 2 HDs as 0 and 1, rather than 0 and 2. I can't recall what the work-around is (I'd prefer not to juggle the disks). Any suggestions? Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 17:52:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA19215 for freebsd-current-outgoing; Wed, 20 Jan 1999 17:52:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailbox1.ucsd.edu (mailbox1.ucsd.edu [132.239.1.53]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA19210 for ; Wed, 20 Jan 1999 17:52:48 -0800 (PST) (envelope-from rjdawes@physics.ucsd.edu) Received: from physics.ucsd.edu (physics.ucsd.edu [132.239.69.26]) by mailbox1.ucsd.edu (8.9.1a/8.9.1) with SMTP id RAA23793 for ; Wed, 20 Jan 1999 17:52:41 -0800 (PST) Received: from localhost by physics.ucsd.edu (SMI-8.6/SMI-SVR4) id RAA16549; Wed, 20 Jan 1999 17:51:00 -0800 Date: Wed, 20 Jan 1999 17:50:58 -0800 (PST) From: "Richard J. Dawes" X-Sender: rjdawes@physics Reply-To: Richard Dawes To: freebsd-current@FreeBSD.ORG Subject: boot.flp versions Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! The "boot.flp" in 3.0.0-19990112-SNAP/floppies is 2880K, which of course won't work. [I think this was acknowledged earlier by JKH, but has gone unfixed.] I'm wondering if an earlier boot.flp, say from the 1/6/99 SNAP, will work just the same? Thanks. --Rich To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 17:59:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA19692 for freebsd-current-outgoing; Wed, 20 Jan 1999 17:59:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA19674 for ; Wed, 20 Jan 1999 17:59:14 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (doconnor@lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id MAA19616; Thu, 21 Jan 1999 12:28:54 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 21 Jan 1999 12:33:53 +1030 (CST) From: "Daniel O'Connor" To: Richard Dawes Subject: RE: boot.flp versions Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 21-Jan-99 Richard J. Dawes wrote: > The "boot.flp" in 3.0.0-19990112-SNAP/floppies is 2880K, which of course > won't work. [I think this was acknowledged earlier by JKH, but has gone > unfixed.] I'm wondering if an earlier boot.flp, say from the 1/6/99 > SNAP, will work just the same? Thanks. The boot.flp is broken.. Try the 2 disk install (ie kern.flp and mfsroot.flp) They boot, but when I got some sucker^h^h^h^h friend to test it, he had no end of trouble installing. Things like sysinstall trying to run the holographic shell twice, mounting things twice and sig-11'ing.. I recommended a source install after that :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 18:00:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19846 for freebsd-current-outgoing; Wed, 20 Jan 1999 18:00:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA19834 for ; Wed, 20 Jan 1999 18:00:14 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id RAA10934; Wed, 20 Jan 1999 17:38:28 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma010925; Wed, 20 Jan 99 17:37:58 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id RAA27076; Wed, 20 Jan 1999 17:37:57 -0800 (PST) From: Archie Cobbs Message-Id: <199901210137.RAA27076@bubba.whistle.com> Subject: Re: KLD naming In-Reply-To: <199901202336.PAA04090@dingo.cdrom.com> from Mike Smith at "Jan 20, 99 03:36:14 pm" To: mike@smith.net.au (Mike Smith) Date: Wed, 20 Jan 1999 17:37:57 -0800 (PST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: > > > A single directory holding module files. > > > > Blech :-) > > Put aside the aesthetics for a moment, and try to raise some real, > practical objections. I'm continually battling my own temptation to > make the whole module thing more complex, but if you've got really good > reasons that can justify the extra complexity everywhere I'm still open > to suggestions. You've got a good point, I don't have any really good reasons, other than trying to be 'organized'. I guess if it looks like the number of files is getting out of hand, then at that time we can say "I told you so!" and then fix the problem. Solving problems on-demand rather than preemptively is more efficient I suppose.. :-) -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 18:00:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19911 for freebsd-current-outgoing; Wed, 20 Jan 1999 18:00:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA19899 for ; Wed, 20 Jan 1999 18:00:48 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id MAA14095; Thu, 21 Jan 1999 12:09:00 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.2/8.9.0) id MAA18644; Thu, 21 Jan 1999 12:09:00 +1030 (CST) Date: Thu, 21 Jan 1999 12:09:00 +1030 From: Greg Lehey To: Andreas Klemm Cc: Matthew Dillon , current@FreeBSD.ORG Subject: Re: panic: vinvalbuf: dirty bufs (during reboot, several times) Message-ID: <19990121120900.R15785@freebie.lemis.com> References: <19990120073445.A402@titan.klemm.gtn.com> <199901200700.XAA76802@apollo.backplane.com> <19990120193354.A1554@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990120193354.A1554@titan.klemm.gtn.com>; from Andreas Klemm on Wed, Jan 20, 1999 at 07:33:54PM +0100 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 20 January 1999 at 19:33:54 +0100, Andreas Klemm wrote: > On Tue, Jan 19, 1999 at 11:00:55PM -0800, Matthew Dillon wrote: >> >> Hmm. Interesting, it's dying trying to fsync an FFS vnode. Are you >> by any chance running NFS ( client *or* server ) on this box? > > No, no NFS compiled in and am not using it. See my kernel config. Where's your kernel config? Are you running vinum? I had some problems with this in earlier versions, but I'm pretty sure none are left. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 18:02:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20127 for freebsd-current-outgoing; Wed, 20 Jan 1999 18:02:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from megaweapon.zigg.com (megaweapon.zigg.com [206.114.60.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA20114 for ; Wed, 20 Jan 1999 18:02:51 -0800 (PST) (envelope-from matt@zigg.com) Received: from localhost (matt@localhost) by megaweapon.zigg.com (8.9.2/8.9.2) with ESMTP id UAA01231 for ; Wed, 20 Jan 1999 20:57:20 -0500 (EST) (envelope-from matt@zigg.com) Date: Wed, 20 Jan 1999 20:57:19 -0500 (EST) From: Matt Behrens To: freebsd-current@FreeBSD.ORG Subject: RE: boot.flp versions In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From 19990112? I had no such problems on three different systems. (System #3 had a lot of other unrelated problems, like a loose ethernet cable and mislabelled jumpers on drives, but none of them were 19990112-related.) :) On Thu, 21 Jan 1999, Daniel O'Connor wrote: : On 21-Jan-99 Richard J. Dawes wrote: : > The "boot.flp" in 3.0.0-19990112-SNAP/floppies is 2880K, which of course : > won't work. [I think this was acknowledged earlier by JKH, but has gone : > unfixed.] I'm wondering if an earlier boot.flp, say from the 1/6/99 : > SNAP, will work just the same? Thanks. : The boot.flp is broken.. : Try the 2 disk install (ie kern.flp and mfsroot.flp) : : They boot, but when I got some sucker^h^h^h^h friend to test it, he had no end of trouble : installing. Things like sysinstall trying to run the holographic shell twice, : mounting things twice and sig-11'ing.. : : I recommended a source install after that :) - Matt Behrens Network Administrator, zigg.com Engineer, Nameless IRC Network To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 18:04:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20277 for freebsd-current-outgoing; Wed, 20 Jan 1999 18:04:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles350.castles.com [208.214.167.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA20267 for ; Wed, 20 Jan 1999 18:04:04 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA05065; Wed, 20 Jan 1999 18:00:34 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901210200.SAA05065@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Richard Dawes cc: freebsd-current@FreeBSD.ORG Subject: Re: boot.flp versions In-reply-to: Your message of "Wed, 20 Jan 1999 17:50:58 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 20 Jan 1999 18:00:34 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello! > > The "boot.flp" in 3.0.0-19990112-SNAP/floppies is 2880K, which of course > won't work. [I think this was acknowledged earlier by JKH, but has gone > unfixed.] I'm wondering if an earlier boot.flp, say from the 1/6/99 > SNAP, will work just the same? Thanks. Use the two-floppy install (kern.flp, mfsroot.flp) instead. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 18:05:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20397 for freebsd-current-outgoing; Wed, 20 Jan 1999 18:05:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from krdl.org.sg (rodin.krdl.org.sg [137.132.252.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA20329 for ; Wed, 20 Jan 1999 18:04:48 -0800 (PST) (envelope-from joerg@mailbox.iss.nus.sg) Received: from mailhost.krdl.org.sg (mailbox.krdl.org.sg [137.132.247.30]) by krdl.org.sg (8.9.2/8.9.2) with ESMTP id JAA10632; Thu, 21 Jan 1999 09:44:00 +0800 (SGT) Received: from negara.nus.sg (negara [137.132.248.175]) by mailhost.krdl.org.sg (8.9.2/8.9.2) with ESMTP id JAA14896; Thu, 21 Jan 1999 09:38:04 +0800 (SGT) Received: (from joerg@localhost) by negara.nus.sg (8.9.1b+Sun/8.9.1) id CAA00485; Thu, 21 Jan 1999 02:39:14 +0800 (SGT) Message-ID: <19990121023914.B468@krdl.org.sg> Date: Thu, 21 Jan 1999 02:39:14 +0800 From: "Joerg B. Micheel" To: Dag-Erling Smorgrav , Mike Nguyen Cc: current@FreeBSD.ORG Subject: Re: /etc/nsswitch.conf References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: ; from Dag-Erling Smorgrav on Wed, Jan 20, 1999 at 05:58:01PM +0100 Organization: Kent Ridge Digital Labs, Singapore Project: SingAREN, the Singapore Advanced Research and Education Network Operating-System: ... drained by Solaris 7 Intel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 20, 1999 at 05:58:01PM +0100, Dag-Erling Smorgrav wrote: > Mike Nguyen writes: > > I noticed that NetBSD is switching over to using /etc/nsswitch.conf (like > > Slowlaris, PH-UX, etc.). Would it be a good idea to do this for FreeBSD too > > (when I first started using FreeBSD, it took me a long time to figure out the > > analogous file for hostname lookups was /etc/host.conf) -- it seems > > consolidating all that config information would in one place would be a good > > thing. > > When I first started using Solaris, it took me a long time to figure > out the analoguous file for hostname setup was /etc/nodename. It seems Thats because Solaris has separated hostname's from nodename. Originally, /etc/hostname.le0, the name/IP address for the primary Ethernet interface, would become the hosts name. What, if you have 3 or 4 interfaces ? The algorithm used in /etc/rc* with SunOS would pick the first interface available. Now if you happen to have a vendor that picks an network interface name "lower" than "le", your host suddenly may a different name. So it happend with FORE's SPANS interface (fa0). When reading Internet RFCs carefully, you figure that there is in fact the term of a nodename, so the decision that Sun made was not very far fetched. Which did not keep them from making the same mistake again. The default multicast interface again gets chosen the same odd way, instead of having a separate configuration mechanism. I chose to reconfigure machines and add something like /etc/hostname.mcast and make it a symlink to the appropriate interface. > consolidating all that config information in one place, such as > /etc/rc.conf, would be a good thing. Agreed, it really isn't such a good idea to clutter /etc/ with all those single line configuration files. Joerg -- Joerg B. Micheel Email: SingAREN Technology Center Phone: +65 8742582 Kent Ridge Digital Labs, Rm 3-65, C041 Fax: +65 7744990 21 Heng Mui Keng Terrace Pager: +65 96016020 Singapore 119613 Plan: Troubleshooting ATM Republic of Singapore Networks and Applications To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 18:08:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20892 for freebsd-current-outgoing; Wed, 20 Jan 1999 18:08:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA20886 for ; Wed, 20 Jan 1999 18:08:12 -0800 (PST) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.1/8.9.1) id SAA05470; Wed, 20 Jan 1999 18:07:38 -0800 (PST) (envelope-from dhw) Date: Wed, 20 Jan 1999 18:07:38 -0800 (PST) From: David Wolfskill Message-Id: <199901210207.SAA05470@pau-amma.whistle.com> To: freebsd-current@FreeBSD.ORG, rdawes@ucsd.edu Subject: Re: boot.flp versions In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Wed, 20 Jan 1999 17:50:58 -0800 (PST) >From: "Richard J. Dawes" >The "boot.flp" in 3.0.0-19990112-SNAP/floppies is 2880K, which of course >won't work. [I think this was acknowledged earlier by JKH, but has gone >unfixed.] I'm wondering if an earlier boot.flp, say from the 1/6/99 >SNAP, will work just the same? Thanks. Mike Smith alluded to the "two-floppy boot" procedure about a week ago; the README.TXT in the floppies directory mentions how to use the kern.flp & the mfsroot.flp images to get started. As to whether a boot.flp from an earlier SNAP will "work just the same," I don't know. Cheers, david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 18:14:16 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA21622 for freebsd-current-outgoing; Wed, 20 Jan 1999 18:14:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA21615 for ; Wed, 20 Jan 1999 18:14:15 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id SAA90524; Wed, 20 Jan 1999 18:14:05 -0800 (PST) To: David Wolfskill cc: freebsd-current@FreeBSD.ORG, rdawes@ucsd.edu Subject: Re: boot.flp versions In-reply-to: Your message of "Wed, 20 Jan 1999 18:07:38 PST." <199901210207.SAA05470@pau-amma.whistle.com> Date: Wed, 20 Jan 1999 18:14:04 -0800 Message-ID: <90520.916884844@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG All: Sorry the boot.flp has been broken for this long, but I've had other distractions lately. I will make it work once more, somehow or other, and just keep your eyes on current.freebsd.org over the next few days. When it returns to 1.44MB in size again, give it a try. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 18:20:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22375 for freebsd-current-outgoing; Wed, 20 Jan 1999 18:20:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from k6n1.znh.org ([207.109.235.45]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA22269 for ; Wed, 20 Jan 1999 18:19:46 -0800 (PST) (envelope-from zach@uffdaonline.net) Received: (from zach@localhost) by k6n1.znh.org (8.9.1/8.9.1) id BAA37970; Thu, 21 Jan 1999 01:45:56 GMT (envelope-from zach) Message-ID: <19990120194556.B37565@znh.org> Date: Wed, 20 Jan 1999 19:45:56 -0600 From: Zach Heilig To: Mike Smith , Archie Cobbs Cc: current@FreeBSD.ORG Subject: Re: KLD naming References: <199901202046.MAA23549@bubba.whistle.com> <199901202336.PAA04090@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199901202336.PAA04090@dingo.cdrom.com>; from Mike Smith on Wed, Jan 20, 1999 at 03:36:14PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 20, 1999 at 03:36:14PM -0800, Mike Smith wrote: > [KLD module file locations] > > I was just pointing out that having things in subdirectories > > is better than having a zillion files piled into a single directory. > I'm torn between agreeing that it's tidier and disagreeing on the > grounds that it's much more of a pain to administer. "Where is that > damnned module?" "Why am I loading a stale version of saver_foo?", etc. Perhaps something more along the lines of: /modules <- empty, except for directories /console <- console related modules blank_saver.ko, daemon_saver.ko, fade_saver.ko, green_saver.ko, logo_saver.ko, rain_saver.ko, snake_saver.ko, star_saver.ko, vesa.ko, warp_saver.ko /devices <- device drivers. joy.ko /emulation <- like linux, fpu, etc... fpu.ko, gnufpu.ko, ibcs2.ko, ibcs2_coff.ko, linux.ko /fs <- filesystem related modules atapi.ko, ccd.ko, cd9660.ko, coda.ko, fdesc.ko, kernfs.ko, mfs.ko, msdos.ko, nfs.ko, null.ko, portal.ko, procfs.ko, umap.ko, union.ko, vinum.ko /net <- network related modules. if_disc.ko, if_ppp.ko, if_sl.ko, if_tun.ko, ipfw.ko I think this takes care of everything currently in /modules. -- Zach Heilig / Zach Heilig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 18:33:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA23730 for freebsd-current-outgoing; Wed, 20 Jan 1999 18:33:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA23716 for ; Wed, 20 Jan 1999 18:33:51 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (doconnor@lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id NAA19936; Thu, 21 Jan 1999 13:03:19 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 21 Jan 1999 13:08:19 +1030 (CST) From: "Daniel O'Connor" To: Matt Behrens Subject: RE: boot.flp versions Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 21-Jan-99 Matt Behrens wrote: > From 19990112? I had no such problems on three different systems. Hmm.. OK.. Maybe pilot error :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 18:57:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA26767 for freebsd-current-outgoing; Wed, 20 Jan 1999 18:57:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA26760 for ; Wed, 20 Jan 1999 18:57:43 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id VAA07518; Wed, 20 Jan 1999 21:57:23 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA03996; Wed, 20 Jan 1999 21:57:23 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id VAA51099; Wed, 20 Jan 1999 21:57:21 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199901210257.VAA51099@bb01f39.unx.sas.com> Subject: Re: make release produces unbootable boot floppies, no boot loader, no /kernel In-Reply-To: From Drew Derbyshire at "Jan 19, 1999 8:40:48 am" To: freebsd-current@FreeBSD.ORG Date: Wed, 20 Jan 1999 21:57:21 -0500 (EST) Cc: software@kew.com (Drew Derbyshire) X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, FWIW, I've been modifying my local 'make release' to produce a 2.88M boot floppy, which I then use as the boot image when I burn a CD of the SNAP. Works like a champ. Thus, the isofs creation is a straight run of the code in examples/worm and cdrecord: sh /usr/share/examples/worm/makecdfs.sh \ -b "${SNAP}" /cdwork/disc1 /cdwork/cd1.image \ "${SNAP} (c) FreeBSD" && \ cd /cdwork && cdrecord dev=5,0 speed=4 -v cd1.image If I hop on my soapbox, I'd really like to see a single floppy network install which supports nfs(which I also re-enable on the normal boot.flp since it fits on the 2.88M image). oh well, John > Mike Smith wrote: > > > > This sounds like booting/installing from CD-ROM is currently > > > impossible as well ??? > > > > That's correct. We're looking at having to move to a harddisk > > emulation mode to get this back on track. > > Would a 2.88M virtual floppy for the CD-ROM boot image be a quick fix, or is > it too much work? > > > - -- > Drew Derbyshire UUPC/extended e-mail: software@kew.com > Telephone: 617-279-9812 > > "I get by with a little help from my friends . . ." - Lennon/McCartney > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > ------------------------------ > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 19:03:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27474 for freebsd-current-outgoing; Wed, 20 Jan 1999 19:03:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pc2-c804.uibk.ac.at (pc2-c804.uibk.ac.at [138.232.82.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA27459 for ; Wed, 20 Jan 1999 19:02:58 -0800 (PST) (envelope-from fatal@pc2-c804.uibk.ac.at) Received: (from fatal@localhost) by pc2-c804.uibk.ac.at (8.8.6/8.8.6) id FAA10116 for freebsd-current@freebsd.org; Thu, 21 Jan 1999 05:08:07 +0100 From: Marco van Hylckama Vlieg Message-Id: <199901210408.FAA10116@pc2-c804.uibk.ac.at> Subject: FreeBSD include paths To: freebsd-current@FreeBSD.ORG Date: Thu, 21 Jan 1999 05:08:07 +0100 (MET) Reply-To: "Marco van Hylckama Vlieg" X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, I got a nagging question... Very often when trying to compile packages I find myself editing makefiles and having to add really obvious include paths like /usr/local/include or /usr/X11R6/include in order to get the package installed. Now I wonder, why doesn't the system itself have these include paths "enabled" by default? Is there a way to fix these ever occuring annoyances when compiling programs? Thanks in advance, Marco -- QQWT!"^""9QQQ ------------------------------------------------ QP' _%7? WindowMaker, the choice of a GNUstep Generation. P WQQ, http://www.windowmaker.org/ ' mWQh Marco's WindowMaker icons: .__s_QWQQ http://marco.shada.com/wmaker/ . ]QQQQQQQ@ L )WQQQQQQ( Marco van Hylckama Vlieg !`_ajQQQQQ@( marco@windowmaker.org "?TUVY"` ------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 19:03:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27662 for freebsd-current-outgoing; Wed, 20 Jan 1999 19:03:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles232.castles.com [208.214.165.232]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA27650 for ; Wed, 20 Jan 1999 19:03:24 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA05393; Wed, 20 Jan 1999 18:59:42 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901210259.SAA05393@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "John W. DeBoskey" cc: freebsd-current@FreeBSD.ORG, software@kew.com (Drew Derbyshire) Subject: Re: make release produces unbootable boot floppies, no boot loader, no /kernel In-reply-to: Your message of "Wed, 20 Jan 1999 21:57:21 EST." <199901210257.VAA51099@bb01f39.unx.sas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 20 Jan 1999 18:59:41 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If I hop on my soapbox, I'd really like to see a single floppy > network install which supports nfs(which I also re-enable on the > normal boot.flp since it fits on the 2.88M image). The problem is that there are too many people standing on too many different soapboxes. Each and every one of you wants a different combination of stuff on the One True Boot Floppy. I'm sure you can see what's wrong with this picture. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 19:06:53 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27927 for freebsd-current-outgoing; Wed, 20 Jan 1999 19:06:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles232.castles.com [208.214.165.232]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA27915 for ; Wed, 20 Jan 1999 19:06:48 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id TAA05424; Wed, 20 Jan 1999 19:02:48 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901210302.TAA05424@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Marco van Hylckama Vlieg" cc: freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD include paths In-reply-to: Your message of "Thu, 21 Jan 1999 05:08:07 +0100." <199901210408.FAA10116@pc2-c804.uibk.ac.at> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 20 Jan 1999 19:02:45 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello all, > > I got a nagging question... > Very often when trying to compile packages I find myself editing > makefiles and having to add really obvious include paths like > /usr/local/include or /usr/X11R6/include in order to get the > package installed. > Now I wonder, why doesn't the system itself have these include paths > "enabled" by default? > Is there a way to fix these ever occuring annoyances when compiling > programs? You are probably building sources from Linux developers. The "correct" fix is to edit the Makefiles as you are doing, and point out to the package authors that it is not correct to assume that the system includes will be spammed with installed packages. > -- > QQWT!"^""9QQQ ------------------------------------------------ > QP' _%7? WindowMaker, the choice of a GNUstep Generation. Please trim your oversized and offensive signature file. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 19:12:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA28391 for freebsd-current-outgoing; Wed, 20 Jan 1999 19:12:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Vorlon.odc.net (Vorlon.odc.net [207.137.42.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA28383 for ; Wed, 20 Jan 1999 19:12:22 -0800 (PST) (envelope-from nwestfal@Vorlon.odc.net) Received: from localhost (nwestfal@localhost) by Vorlon.odc.net (8.8.7/8.8.7) with ESMTP id TAA29809; Wed, 20 Jan 1999 19:11:58 -0800 Date: Wed, 20 Jan 1999 19:11:58 -0800 (PST) From: Neal Westfall To: "Daniel O'Connor" cc: Richard Dawes , freebsd-current@FreeBSD.ORG Subject: RE: boot.flp versions In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I installed the 19990112 snap late last night with no problems using the 2 disk install. Worked great. Its now been upgraded to current. On Thu, 21 Jan 1999, Daniel O'Connor wrote: > The boot.flp is broken.. > Try the 2 disk install (ie kern.flp and mfsroot.flp) > > They boot, but when I got some sucker^h^h^h^h friend to test it, he had no end of trouble > installing. Things like sysinstall trying to run the holographic shell twice, > mounting things twice and sig-11'ing.. > > I recommended a source install after that :) > > --- > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- Neal Westfall mailto:nwestfal@odc.net http://www.odc.net/~nwestfal/ FreeBSD: The Power To Serve! http://www.freebsd.org/ $Id: dot.signature,v 1.2 1998/12/30 08:23:13 nwestfal Exp nwestfal $ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 19:16:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA28740 for freebsd-current-outgoing; Wed, 20 Jan 1999 19:16:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA28727 for ; Wed, 20 Jan 1999 19:16:24 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id TAA17509; Wed, 20 Jan 1999 19:16:07 -0800 (PST) (envelope-from obrien) Date: Wed, 20 Jan 1999 19:16:07 -0800 From: "David O'Brien" To: Richard Dawes Cc: freebsd-current@FreeBSD.ORG Subject: Re: boot.flp versions Message-ID: <19990120191607.A17471@relay.nuxi.com> Reply-To: obrien@NUXI.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Richard J. Dawes on Wed, Jan 20, 1999 at 05:50:58PM -0800 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm wondering if an earlier boot.flp, say from the 1/6/99 SNAP, will > work just the same? Thanks. Normally, a boot.flp of about the same time will work fine. You just need to go into the Options and change the release name string. The 1/6/99 boot.flp is broken. /boot/* can't be found. This means you can't do a fresh install (well, maybe in dangeriously dedicated mode -- I didn't try that) because the boot blocks can't be found by sysinstall. I was able to install the 1/6/99 SNAP by 1st installing a minimal 3.0-R and then doing an upgrade using the 1/6/99 boot.flp. This will leave you with an a.out kernel. You will need to install new boot blocks before you make your first 1/6/99 kernel. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 19:19:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA29002 for freebsd-current-outgoing; Wed, 20 Jan 1999 19:19:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA28985 for ; Wed, 20 Jan 1999 19:19:26 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id TAA17537 for current@FreeBSD.ORG; Wed, 20 Jan 1999 19:19:15 -0800 (PST) (envelope-from obrien) Date: Wed, 20 Jan 1999 19:19:15 -0800 From: "David O'Brien" To: current@FreeBSD.ORG Subject: Re: KLD naming Message-ID: <19990120191915.B17471@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <199901202046.MAA23549@bubba.whistle.com> <199901202336.PAA04090@dingo.cdrom.com> <19990120194556.B37565@znh.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <19990120194556.B37565@znh.org>; from Zach Heilig on Wed, Jan 20, 1999 at 07:45:56PM -0600 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Perhaps something more along the lines of: > > /modules <- empty, except for directories > /console <- console related modules > blank_saver.ko, daemon_saver.ko, fade_saver.ko, green_saver.ko, Gross. What is wrong with: saver_*.ko device_*.ko linux_*.ko fs_*.ko if_*.ko etc? This is what the original poster suggested, and nobody has really given a good response what is wrong with the "grouping" being expressed in the modules' name. Mike Smith and Andrzej Bialecki have given good reasons why *not* to go to a subdirectory structure. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 19:43:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA01234 for freebsd-current-outgoing; Wed, 20 Jan 1999 19:43:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA01137 for ; Wed, 20 Jan 1999 19:43:35 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id OAA14863 for ; Thu, 21 Jan 1999 14:13:18 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.2/8.9.0) id OAA19520 for FreeBSD-current@FreeBSD.ORG; Thu, 21 Jan 1999 14:13:17 +1030 (CST) Date: Thu, 21 Jan 1999 14:13:16 +1030 From: Greg Lehey To: FreeBSD current users Subject: HEADS UP: New version of Vinum Message-ID: <19990121141315.H15785@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just committed a new version of Vinum with a large number of changes. It works fine here, much better than the old version, but there's just a possibility that things may go wrong. If you have trouble, please let me know immediately. One way you can shoot yourself in the foot: the `read' command has changed. In the previous version, you specified the name of exactly one device containing a vinum partition. This is suboptimal, because it doesn't allow you to read multiple configurations, and it doesn't allow you to move drives around. In the new version, you *must* specify the names of *all* disks containing Vinum partitions. For example, if you have Vinum partitions /dev/da1h /dev/da2h /dev/da3h /dev/da4h /dev/da5h and /dev/da6h, you might previously have written: vinum read /dev/da3h Now you *must* write: vinum read /dev/da1 /dev/da2 /dev/da3 /dev/da4 /dev/da5 /dev/da6 If you do this wrong, you have the potential to wipe out your on-disk configuration. You can avoid this by disabling saving the configuration. Do this with the `setdaemon' command: # vinum vinum -> setdaemon 4 vinum -> read /dev/da1 /dev/da2 /dev/da3 /dev/da4 /dev/da5 /dev/da6 Yes, I know, specifying bits for the setdaemon command is tacky, and it'll go away. Bit 4 disables the configuration save. When your configuration is recognized correctly, you can re-enable it with `setdaemon 0'. For more information RTFM. The on-disk configuration has also changed. Previously, it contained the names of the drives as well as the other objects; now Vinum finds the drives by itself. You can check the versions by looking at the config copy at offset 9 blocks from the beginning of the partition: # dd if=/dev/da2h skip=9 count=1 volume obj state up volume src state up volume raid state up volume r state up volume S state up plex name obj.p0 state up org concat vol obj plex name obj.p1 state up org striped 128b vol obj plex name src.p0 state up org striped 128b vol src plex name src.p1 state up org concat vol src plex name raid.p0 state up org raid5 vol raid plex name r.p0 state up org raid5 vol r plex name S.p0 state up org raid5 vol S sd name obj.p0.s0 drive drive2 plex obj.p0 state up len 409600b driveoffset 265b plexof1+0 records in This version shows the new configuration: it starts with volume definitions. The old version starts with drive definitions. The new version will ignore any drive definitions it finds in the configuration. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 19:54:01 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02282 for freebsd-current-outgoing; Wed, 20 Jan 1999 19:54:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02259 for ; Wed, 20 Jan 1999 19:53:59 -0800 (PST) (envelope-from rainking@shell.futuresouth.com) Received: from localhost (rainking@localhost) by shell.futuresouth.com (8.9.1a/8.9.1) with SMTP id VAA03514 for ; Wed, 20 Jan 1999 21:53:51 -0600 (CST) Date: Wed, 20 Jan 1999 21:53:51 -0600 (CST) From: Owen Barnett To: freebsd-current@FreeBSD.ORG Subject: ELF kernel make problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently used "make world" to update make system to ELF. The make world finished successfully everything appears to function correctly except when I try to recompile my kernel. make depend works but once I get to 'make' it will compile for a while then stop when it gets to db_aout.o and say Not an ELF file, or File format not recognized. Any suggestions? Owen BTW - I used mergemaster to update my files. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 19:57:02 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02841 for freebsd-current-outgoing; Wed, 20 Jan 1999 19:57:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02829 for ; Wed, 20 Jan 1999 19:56:59 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac8.wam.umd.edu ((IDENT root)@rac8.wam.umd.edu [128.8.10.148]) by po4.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id WAA20225; Wed, 20 Jan 1999 22:56:57 -0500 (EST) Received: from rac8.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1]) by rac8.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id WAA00152; Wed, 20 Jan 1999 22:56:40 -0500 (EST) Received: from localhost by rac8.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id WAA00147; Wed, 20 Jan 1999 22:56:38 -0500 (EST) X-Authentication-Warning: rac8.wam.umd.edu: culverk owned process doing -bs Date: Wed, 20 Jan 1999 22:56:37 -0500 (EST) From: Kenneth Wayne Culver To: Owen Barnett cc: freebsd-current@FreeBSD.ORG Subject: Re: ELF kernel make problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I recently used "make world" to update make system to ELF. The make world > finished successfully everything appears to function correctly except when > I try to recompile my kernel. make depend works but once I get to 'make' > it will compile for a while then stop when it gets to db_aout.o and say > Not an ELF file, or File format not recognized. Any suggestions? > > Owen > > BTW - I used mergemaster to update my files. when you do the config on your kernel config file type: config -r replace with the name of your kernel config file. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 20:08:43 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA04022 for freebsd-current-outgoing; Wed, 20 Jan 1999 20:08:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oreo.adsu.bellsouth.com (oreo.adsu.bellsouth.com [205.152.173.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA04017 for ; Wed, 20 Jan 1999 20:08:41 -0800 (PST) (envelope-from ck@oreo.adsu.bellsouth.com) Received: (from ck@localhost) by oreo.adsu.bellsouth.com (8.9.1/8.9.1) id XAA26993; Wed, 20 Jan 1999 23:08:26 -0500 (EST) (envelope-from ck) Date: Wed, 20 Jan 1999 23:08:26 -0500 From: Christian Kuhtz To: paul@originative.co.uk Cc: archie@whistle.com, dfr@nlsystems.com, gelderen@mediaport.org, current@FreeBSD.ORG Subject: Re: KLD naming Message-ID: <19990120230826.X25047@oreo.adsu.bellsouth.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from paul@originative.co.uk on Wed, Jan 20, 1999 at 10:58:13AM -0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why not just follow the directory structure under /sys? Afterall, we are talking about kernel stuff here. On Wed, Jan 20, 1999 at 10:58:13AM -0000, paul@originative.co.uk wrote: [..] > I don't think subdirectories based on bus type is a good idea, it > doesn't really fit the granularity we're probably heading towards. Some > thinks don't really fit at all, filesystems, screen savers etc and even > for drivers we're heading towards less bus specific devices so an > ethernet driver, say, would be the same for any bus, only the startup > code would be different and possibly(probably) in a different module. > > A functional structure is probably better > > /modules > /devices > /ethernet > /storage > /display > /network > /filesystems > /screensavers > > > etc. > > Not a specific proposal for actual directories but perhaps a better > direction. I think we should start thinking more in terms of function, > rather than bus, in a lot of what we do with devices as we abstract out > the bus code more effectively. > > Paul. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- "Logic is a little bird, sitting in a tree; that smells *awful*." -- /usr/bin/fortune [Disclaimer: I speak for myself and my views are my own and not in any way to be construed as the views of BellSouth Corporation. ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 20:12:39 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA04586 for freebsd-current-outgoing; Wed, 20 Jan 1999 20:12:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wat-border.sentex.ca (sentex-uu.sentex.ca [209.167.167.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA04257 for ; Wed, 20 Jan 1999 20:09:58 -0800 (PST) (envelope-from mike@sentex.net) Received: from gravel (ospf-wat.sentex.net [209.167.248.81]) by wat-border.sentex.ca (8.8.8/8.8.8) with SMTP id XAA02164 for ; Wed, 20 Jan 1999 23:08:54 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <3.0.5.32.19990120231515.026b52b0@granite.sentex.ca> X-Sender: mdtancsa@granite.sentex.ca X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Wed, 20 Jan 1999 23:15:15 -0500 To: current@FreeBSD.ORG From: Mike Tancsa Subject: make: don't know how to make vinumdaemon.c. Stop Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Am I the only one seeing this ? Current as a few hrs ago... /usr/src/sys/modules/mfs/../../ufs/mfs/mfs_vfsops.c:68: warning: `mfs_rootsize' defined but not used /usr/src/sys/modules/vinum/../../dev/vinum/vinum.c:324: warning: initialization from incompatible pointer type /usr/src/sys/modules/vinum/../../dev/vinum/vinumio.c: In function `check_drive': /usr/src/sys/modules/vinum/../../dev/vinum/vinumio.c:513: warning: variable `cptr' might be clobbered by `longjmp' or `vfork' make: don't know how to make vinumdaemon.c. Stop ---Mike ********************************************************************** Mike Tancsa, Network Admin * mike@sentex.net Sentex Communications Corp, * http://www.sentex.net/mike Cambridge, Ontario * 01.519.651.3400 Canada * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 20:17:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA05045 for freebsd-current-outgoing; Wed, 20 Jan 1999 20:17:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oreo.adsu.bellsouth.com (oreo.adsu.bellsouth.com [205.152.173.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA05039 for ; Wed, 20 Jan 1999 20:17:56 -0800 (PST) (envelope-from ck@oreo.adsu.bellsouth.com) Received: (from ck@localhost) by oreo.adsu.bellsouth.com (8.9.1/8.9.1) id XAA27090; Wed, 20 Jan 1999 23:17:41 -0500 (EST) (envelope-from ck) Date: Wed, 20 Jan 1999 23:17:41 -0500 From: Christian Kuhtz To: "David O'Brien" Cc: current@FreeBSD.ORG Subject: Re: KLD naming Message-ID: <19990120231741.Z25047@oreo.adsu.bellsouth.com> References: <199901202046.MAA23549@bubba.whistle.com> <199901202336.PAA04090@dingo.cdrom.com> <19990120194556.B37565@znh.org> <19990120191915.B17471@relay.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <19990120191915.B17471@relay.nuxi.com>; from David O'Brien on Wed, Jan 20, 1999 at 07:19:15PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 20, 1999 at 07:19:15PM -0800, David O'Brien wrote: [..] > etc? This is what the original poster suggested, and nobody has really > given a good response what is wrong with the "grouping" being expressed > in the modules' name. Mike Smith and Andrzej Bialecki have given good > reasons why *not* to go to a subdirectory structure. What would you name a network stack? For example: net_mpls_tdp.ko net_mpls_ldp.ko net_mpls_core.ko or net_h323v2_yada.ko net_h323v2_yadayada.ko net_h323v2_barf.ko or codec_g711.ko codec_g7231a.ko codec_g729.ko Is that acceptable? Anyone have better ideas? Cheers, Chris -- "Logic is a little bird, sitting in a tree; that smells *awful*." -- /usr/bin/fortune [Disclaimer: I speak for myself and my views are my own and not in any way to be construed as the views of BellSouth Corporation. ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 20:21:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA05598 for freebsd-current-outgoing; Wed, 20 Jan 1999 20:21:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA05590 for ; Wed, 20 Jan 1999 20:21:43 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id OAA15165; Thu, 21 Jan 1999 14:51:26 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.2/8.9.0) id OAA19814; Thu, 21 Jan 1999 14:51:21 +1030 (CST) Date: Thu, 21 Jan 1999 14:51:21 +1030 From: Greg Lehey To: Mike Tancsa Cc: current@FreeBSD.ORG Subject: Re: make: don't know how to make vinumdaemon.c. Stop Message-ID: <19990121145121.N15785@freebie.lemis.com> References: <3.0.5.32.19990120231515.026b52b0@granite.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <3.0.5.32.19990120231515.026b52b0@granite.sentex.ca>; from Mike Tancsa on Wed, Jan 20, 1999 at 11:15:15PM -0500 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 20 January 1999 at 23:15:15 -0500, Mike Tancsa wrote: > > Am I the only one seeing this ? Yes, I think so. > Current as a few hrs ago... > > /usr/src/sys/modules/mfs/../../ufs/mfs/mfs_vfsops.c:68: warning: `mfs_rootsize' defined but not used > /usr/src/sys/modules/vinum/../../dev/vinum/vinum.c:324: warning: initialization from incompatible pointer type > /usr/src/sys/modules/vinum/../../dev/vinum/vinumio.c: In function `check_drive': > /usr/src/sys/modules/vinum/../../dev/vinum/vinumio.c:513: warning: variable `cptr' might be clobbered by `longjmp' or `vfork' Hmm. These messages look like an old version of vinumio.c. > make: don't know how to make vinumdaemon.c. Stop> I would guess that you cvsupped in the window between 16:25:48 PST, when I committed the new Makefile, and 16:31:31 PST, when I committed vinumdaemon.c. Try again once the tags have been updated (a couple of hours). Check sys/conf/newvers.sh: it should show 4.0. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 20:29:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA06539 for freebsd-current-outgoing; Wed, 20 Jan 1999 20:29:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wat-border.sentex.ca (sentex-uu.sentex.ca [209.167.167.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA06530 for ; Wed, 20 Jan 1999 20:29:17 -0800 (PST) (envelope-from mike@sentex.net) Received: from gravel (ospf-wat.sentex.net [209.167.248.81]) by wat-border.sentex.ca (8.8.8/8.8.8) with SMTP id XAA02180; Wed, 20 Jan 1999 23:28:31 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <3.0.5.32.19990120233452.04b59340@granite.sentex.ca> X-Sender: mdtancsa@granite.sentex.ca X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Wed, 20 Jan 1999 23:34:52 -0500 To: Greg Lehey From: Mike Tancsa Subject: Re: make: don't know how to make vinumdaemon.c. Stop Cc: current@FreeBSD.ORG In-Reply-To: <19990121145121.N15785@freebie.lemis.com> References: <3.0.5.32.19990120231515.026b52b0@granite.sentex.ca> <3.0.5.32.19990120231515.026b52b0@granite.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 02:51 PM 1/21/99 +1030, Greg Lehey wrote: >On Wednesday, 20 January 1999 at 23:15:15 -0500, Mike Tancsa wrote: >> >> Am I the only one seeing this ? > >Yes, I think so. >I would guess that you cvsupped in the window between 16:25:48 PST, >when I committed the new Makefile, and 16:31:31 PST, when I committed >vinumdaemon.c. Try again once the tags have been updated (a couple of >hours). Check sys/conf/newvers.sh: it should show 4.0. Sounds like this might be the problem... I will resup it again in a bit. # @(#)newvers.sh 8.1 (Berkeley) 4/20/94 # $Id: newvers.sh,v 1.41 1998/11/01 15:36:20 wosch Exp $ TYPE="FreeBSD" REVISION="3.0" BRANCH="CURRENT" RELEASE="${REVISION}-${BRANCH}" SNAPDATE="" ---Mike ********************************************************************** Mike Tancsa, Network Admin * mike@sentex.net Sentex Communications Corp, * http://www.sentex.net/mike Cambridge, Ontario * 01.519.651.3400 Canada * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 20:29:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA06598 for freebsd-current-outgoing; Wed, 20 Jan 1999 20:29:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA06590 for ; Wed, 20 Jan 1999 20:29:38 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id OAA15197; Thu, 21 Jan 1999 14:59:28 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.2/8.9.0) id OAA19896; Thu, 21 Jan 1999 14:59:28 +1030 (CST) Date: Thu, 21 Jan 1999 14:59:28 +1030 From: Greg Lehey To: Mike Tancsa Cc: current@FreeBSD.ORG Subject: Re: make: don't know how to make vinumdaemon.c. Stop Message-ID: <19990121145927.P15785@freebie.lemis.com> References: <3.0.5.32.19990120231515.026b52b0@granite.sentex.ca> <3.0.5.32.19990120231515.026b52b0@granite.sentex.ca> <19990121145121.N15785@freebie.lemis.com> <3.0.5.32.19990120233452.04b59340@granite.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <3.0.5.32.19990120233452.04b59340@granite.sentex.ca>; from Mike Tancsa on Wed, Jan 20, 1999 at 11:34:52PM -0500 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 20 January 1999 at 23:34:52 -0500, Mike Tancsa wrote: > At 02:51 PM 1/21/99 +1030, Greg Lehey wrote: >> On Wednesday, 20 January 1999 at 23:15:15 -0500, Mike Tancsa wrote: >>> >>> Am I the only one seeing this ? >> >> Yes, I think so. >> I would guess that you cvsupped in the window between 16:25:48 PST, >> when I committed the new Makefile, and 16:31:31 PST, when I committed >> vinumdaemon.c. Try again once the tags have been updated (a couple of >> hours). Check sys/conf/newvers.sh: it should show 4.0. > > Sounds like this might be the problem... I will resup it again in a bit. > # @(#)newvers.sh 8.1 (Berkeley) 4/20/94 > # $Id: newvers.sh,v 1.41 1998/11/01 15:36:20 wosch Exp $ > > TYPE="FreeBSD" > REVISION="3.0" > BRANCH="CURRENT" > RELEASE="${REVISION}-${BRANCH}" > SNAPDATE="" Yup, I'm waiting too. BTW, read the HEADS UP that I sent out a while back. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 20:36:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA07412 for freebsd-current-outgoing; Wed, 20 Jan 1999 20:36:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fledge.watson.org (FLEDGE.RES.CMU.EDU [128.2.93.229]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA07407 for ; Wed, 20 Jan 1999 20:36:53 -0800 (PST) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id XAA25447; Wed, 20 Jan 1999 23:35:07 -0500 (EST) Date: Wed, 20 Jan 1999 23:35:07 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Mike Smith cc: Archie Cobbs , current@FreeBSD.ORG Subject: Re: KLD naming In-Reply-To: <199901202336.PAA04090@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 20 Jan 1999, Mike Smith wrote: > > I was just pointing out that having things in subdirectories > > is better than having a zillion files piled into a single directory. > > I'm torn between agreeing that it's tidier and disagreeing on the > grounds that it's much more of a pain to administer. "Where is that > damnned module?" "Why am I loading a stale version of saver_foo?", etc. Putting the source code in different directories is not equivilent to putting the modules in different directories, needless to say. :-) As such, I think having a structured source tree is really nice, but the simplicity of modules in a single directory in the style of MacOS extensions as you discuss has appeal (and means that users don't have to try and reproduce a directory hierarchy for binary-only modules they get somewhere). On the other hand, this still requires moderation in namespace use for modules. Robert N Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ SafePort Network Services http://www.safeport.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 20:56:43 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA09288 for freebsd-current-outgoing; Wed, 20 Jan 1999 20:56:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA09279; Wed, 20 Jan 1999 20:56:40 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id UAA10191; Wed, 20 Jan 1999 20:56:32 -0800 (PST) (envelope-from dillon) Date: Wed, 20 Jan 1999 20:56:32 -0800 (PST) From: Matthew Dillon Message-Id: <199901210456.UAA10191@apollo.backplane.com> To: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Heads up! New swapper and VM changes being committed to -4.x tonight. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The new swapper and a bunch of VM stuff I've been sitting on is going to be committed into the new -current tree tonight. These changes also include the most recent NFS fix ( of two.. the one prior to this one has already been committed ). This fix and numerous other minor VM bug fixes that are applicable to the -3.x tree will be backported once some external testing has been done. Hopefully *before* the 3.1 freeze. New material not related to out-and-out bug fixes will probably not be backported to -3.x. Or, if it is, not for some time. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 21:43:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15380 for freebsd-current-outgoing; Wed, 20 Jan 1999 21:43:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.atl.bellsouth.net (mail.atl.bellsouth.net [205.152.0.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA15365 for ; Wed, 20 Jan 1999 21:43:17 -0800 (PST) (envelope-from wghicks@bellsouth.net) Received: from wghicks.bellsouth.net (root@host-209-214-76-34.atl.bellsouth.net [209.214.76.34]) by mail.atl.bellsouth.net (8.8.8-spamdog/8.8.5) with ESMTP id AAA14739; Thu, 21 Jan 1999 00:43:07 -0500 (EST) Received: from wghicks (wghicks@localhost [127.0.0.1]) by wghicks.bellsouth.net (8.9.2/8.9.2) with ESMTP id AAA31363; Thu, 21 Jan 1999 00:59:32 -0500 (EST) (envelope-from wghicks@wghicks.bellsouth.net) Message-Id: <199901210559.AAA31363@bellsouth.net> X-Mailer: exmh version 2.0.2 2/24/98 To: David Wolfskill cc: freebsd-current@FreeBSD.ORG, rdawes@ucsd.edu Subject: Re: boot.flp versions In-reply-to: Your message of "Wed, 20 Jan 1999 18:07:38 PST." <199901210207.SAA05470@pau-amma.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Jan 1999 00:59:32 -0500 From: W Gerald Hicks Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [snips] > As to whether a boot.flp from an earlier SNAP will "work just the same," > I don't know. > > Cheers, > david > -- > David Wolfskill UNIX System Administrator > dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 I used a 3.0-RELEASE boot.flp to load a 'minimal configuration' by changing the options screen to the Jan 12 SNAP. First thing after that, I loaded a cvsup-bin package, grabbed the sources from our local cvsup-mirror and built world. It's working fine now but I'll bet 'you shouldn't do this' (TM) :-) Cheers, Jerry Hicks wghicks@bellsouth.net -- Jerry Hicks wghicks@bellsouth.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 21:54:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA17166 for freebsd-current-outgoing; Wed, 20 Jan 1999 21:54:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA17161 for ; Wed, 20 Jan 1999 21:54:55 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id AAA01080; Thu, 21 Jan 1999 00:54:36 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA18355; Thu, 21 Jan 1999 00:54:36 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id AAA51853; Thu, 21 Jan 1999 00:54:36 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199901210554.AAA51853@bb01f39.unx.sas.com> Subject: Re: make release produces unbootable boot floppies, no boot loader, no /kernel In-Reply-To: <199901210259.SAA05393@dingo.cdrom.com> from Mike Smith at "Jan 20, 1999 6:59:41 pm" To: freebsd-current@FreeBSD.ORG Date: Thu, 21 Jan 1999 00:54:36 -0500 (EST) Cc: mike@smith.net.au (Mike Smith), software@kew.com X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, Hang on a second... I think you might be putting words in my mouth... I'm not saying that the nfs boot floppy is the One True Boot Floppy. I see no reason why we can't have a netboot.flp and a dskboot.flp created. If you really want to make things easier for the beginner, why not provide a DOS boot program. Then you wouldn't even have to worry about boot floppies. Tell new folks to copy the boot program to the DOS partition and run it from DOS. Case closed. No boot floppy required. I can imagine half a dozen ways to make this work. However, I don't really want the above. I'd simply like to see a netboot.flp become a standard part of the distribution. There are others on the list besides myself who have said they would like to see this. It's simple to do, just a few extra commands in the release.8 target. Unfortunately, I'm not a committer, and it really isn't a technical question... It's a political issue... FreeBSD seems to want 'The One True Floppy'... Oh well, Thanks for listening! John I said: > > If I hop on my soapbox, I'd really like to see a single floppy > > network install which supports nfs(which I also re-enable on the > > normal boot.flp since it fits on the 2.88M image). > and Mike replied: > The problem is that there are too many people standing on too many > different soapboxes. Each and every one of you wants a different > combination of stuff on the One True Boot Floppy. > > I'm sure you can see what's wrong with this picture. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 22:00:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA18071 for freebsd-current-outgoing; Wed, 20 Jan 1999 22:00:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles232.castles.com [208.214.165.232]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA18066 for ; Wed, 20 Jan 1999 22:00:32 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id VAA06281; Wed, 20 Jan 1999 21:56:53 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901210556.VAA06281@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Christian Kuhtz cc: "David O'Brien" , current@FreeBSD.ORG Subject: Re: KLD naming In-reply-to: Your message of "Wed, 20 Jan 1999 23:17:41 EST." <19990120231741.Z25047@oreo.adsu.bellsouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 20 Jan 1999 21:56:52 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, Jan 20, 1999 at 07:19:15PM -0800, David O'Brien wrote: > [..] > > etc? This is what the original poster suggested, and nobody has really > > given a good response what is wrong with the "grouping" being expressed > > in the modules' name. Mike Smith and Andrzej Bialecki have given good > > reasons why *not* to go to a subdirectory structure. > > What would you name a network stack? For example: > > net_mpls_tdp.ko > net_mpls_ldp.ko > net_mpls_core.ko > > or > net_h323v2_yada.ko > net_h323v2_yadayada.ko > net_h323v2_barf.ko > > or > codec_g711.ko > codec_g7231a.ko > codec_g729.ko > > Is that acceptable? Anyone have better ideas? I guess it depends on how fancy we want to get. Here are some examples that I've been rolling around; some are fanciful, some practical) dev_ generic device (eg. dev_sio) bus_ bus support (eg. bus_pci) netif_ network interface (eg. netif_ed) netproto_ network protocol (eg. netproto_arp) netdomain_ network domain (eg. netdomain_ip) vfs_ VFS layer (eg. vfs_nfs) kern_ kernel infrastructure (eg. kern_vfs) syscall_ loadable system calls (eg. syscall_sendfile) I don't think we want to make the mistake of being too specific about what pigeonhole something falls into. In many cases, we might want new categories when a new case arises, eg. for USB we might have: bus_usb.ko usb_hub.ko usb_mouse.ko usb_keyboard.ko usb_disk.ko usb_scanner.ko ... There's no ambiguity here, the names are simple and convey a direct set of relationships. Your examples (except the first) do a pretty good job of the same thing. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 22:04:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA18532 for freebsd-current-outgoing; Wed, 20 Jan 1999 22:04:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA18524 for ; Wed, 20 Jan 1999 22:04:20 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id WAA87470; Wed, 20 Jan 1999 22:03:45 -0800 (PST) To: Mike Smith cc: Christian Kuhtz , "David O'Brien" , current@FreeBSD.ORG Subject: Re: KLD naming In-reply-to: Your message of "Wed, 20 Jan 1999 21:56:52 PST." <199901210556.VAA06281@dingo.cdrom.com> Date: Wed, 20 Jan 1999 22:03:44 -0800 Message-ID: <87466.916898624@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I guess it depends on how fancy we want to get. Here are some examples > that I've been rolling around; some are fanciful, some practical) > > dev_ generic device (eg. dev_sio) > bus_ bus support (eg. bus_pci) > netif_ network interface (eg. netif_ed) > netproto_ network protocol (eg. netproto_arp) > netdomain_ network domain (eg. netdomain_ip) > vfs_ VFS layer (eg. vfs_nfs) > kern_ kernel infrastructure (eg. kern_vfs) > syscall_ loadable system calls (eg. syscall_sendfile) I like this. It's the best alternative to an arbitrarily deep (and much disputed) directory structure I've seen so far. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 22:17:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA20157 for freebsd-current-outgoing; Wed, 20 Jan 1999 22:17:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from access2_15.kuniv.edu.kw ([139.141.220.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA20076 for ; Wed, 20 Jan 1999 22:17:14 -0800 (PST) (envelope-from root@access2_15.kuniv.edu.kw) Received: (from root@localhost) by access2_15.kuniv.edu.kw (8.9.2/8.9.1) id JAA02672; Thu, 21 Jan 1999 09:13:59 +0300 (AST) (envelope-from root) Message-Id: <199901210613.JAA02672@access2_15.kuniv.edu.kw> Date: Thu, 21 Jan 1999 09:13:58 +0300 (AST) From: root@isis.dynip.com Reply-To: root@isis.dynip.com Subject: Re: C++ compliler unable to produce excutables To: cracauer@cons.org cc: freebsd-current@FreeBSD.ORG In-Reply-To: <19990119141243.A753@cons.org> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Do you have egcs or gcc-2.8 or anything else installaed that installs > /usr/local/bin/g++? > yes, that's the one I really recently installed I was suspecious about it, but now you confirmed it. > Such extra compilers from ports tend to break. Make sure you use > /usr/bin/g++. > Thanks -- - MAY THE FORCE BE WITH YOU. ~o .^. ---------------------------- ___ o~ .00 ) Static Email : osiris2002@yahoo.com /| o~ /)( Bouncing Email : root@isis.dynip.com / | | \ Web Site : http://isis.dynip.com:80 (Frames) ___/ | / \ Anon FTP Site : ftp://isis.dynip.com:21 (anonymous) | /''___/ / | Gopher Site : gopher://isis.dynip.com:70 | /'''/___/ | Network News : isis.dynip.com (Read, Post, Xfer) __|/'''/ Mailing Lists : majordomo@isis.dynip.com (public) pgp key : finger root@isis.dynip.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 22:22:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA20709 for freebsd-current-outgoing; Wed, 20 Jan 1999 22:22:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles232.castles.com [208.214.165.232]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA20701 for ; Wed, 20 Jan 1999 22:22:46 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id WAA06427; Wed, 20 Jan 1999 22:19:10 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901210619.WAA06427@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "John W. DeBoskey" cc: freebsd-current@FreeBSD.ORG, mike@smith.net.au (Mike Smith), software@kew.com Subject: Re: make release produces unbootable boot floppies, no boot loader, no /kernel In-reply-to: Your message of "Thu, 21 Jan 1999 00:54:36 EST." <199901210554.AAA51853@bb01f39.unx.sas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 20 Jan 1999 22:19:09 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hang on a second... I think you might be putting words in my > mouth... I'm not saying that the nfs boot floppy is the One True > Boot Floppy. I see no reason why we can't have a netboot.flp and > a dskboot.flp created. The slicing that's being contemplated at the moment is actually "install from CDROM" and "install from anywhere else". The CDROM support actually covers a reasonable amount of code (although there are some angsty issues about ATAPI ZIP/LS120 disks still). > If you really want to make things easier for the beginner, why > not provide a DOS boot program. Then you wouldn't even have to > worry about boot floppies. Tell new folks to copy the boot program > to the DOS partition and run it from DOS. Case closed. No boot > floppy required. I can imagine half a dozen ways to make this work. Please read everything that Robert Nordier has written about how it's not possible to boot once DOS has started. Or take it from me - we have canned support for that mode of operation and we're not going back. > Unfortunately, I'm not a committer, and it really isn't a > technical question... It's a political issue... FreeBSD seems to > want 'The One True Floppy'... Not really; and if you have diffs that let us split into a couple of cleanly separated floppies with no missing cases then we would enthusiastically leap onboard. But "net/no-net" isn't enough of a dividing line. We're pretty much resigned to the death of "one true floppy". 8( -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 22:47:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA23222 for freebsd-current-outgoing; Wed, 20 Jan 1999 22:47:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA23178 for ; Wed, 20 Jan 1999 22:47:02 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.8.6/8.8.6) with ESMTP id HAA14480; Thu, 21 Jan 1999 07:46:25 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.2/8.9.2) id HAA13957; Thu, 21 Jan 1999 07:19:40 +0100 (CET) (envelope-from andreas) Date: Thu, 21 Jan 1999 07:19:39 +0100 From: Andreas Klemm To: Greg Lehey Cc: Andreas Klemm , Matthew Dillon , current@FreeBSD.ORG Subject: Re: panic: vinvalbuf: dirty bufs (during reboot, several times) Message-ID: <19990121071939.A13938@titan.klemm.gtn.com> References: <19990120073445.A402@titan.klemm.gtn.com> <199901200700.XAA76802@apollo.backplane.com> <19990120193354.A1554@titan.klemm.gtn.com> <19990121120900.R15785@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990121120900.R15785@freebie.lemis.com>; from Greg Lehey on Thu, Jan 21, 1999 at 12:09:00PM +1030 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 21, 1999 at 12:09:00PM +1030, Greg Lehey wrote: > On Wednesday, 20 January 1999 at 19:33:54 +0100, Andreas Klemm wrote: > > On Tue, Jan 19, 1999 at 11:00:55PM -0800, Matthew Dillon wrote: > >> > >> Hmm. Interesting, it's dying trying to fsync an FFS vnode. Are you > >> by any chance running NFS ( client *or* server ) on this box? > > > > No, no NFS compiled in and am not using it. See my kernel config. > > Where's your kernel config? Are you running vinum? I had some > problems with this in earlier versions, but I'm pretty sure none are > left. Im my first mail (where I reported the problem) I sent kernel config file and dmesg output. And no, sorry, am using ccd, not vinum. -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 22:57:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA24679 for freebsd-current-outgoing; Wed, 20 Jan 1999 22:57:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA24655 for ; Wed, 20 Jan 1999 22:57:25 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id RAA15755; Thu, 21 Jan 1999 17:27:13 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.2/8.9.0) id RAA23811; Thu, 21 Jan 1999 17:27:08 +1030 (CST) Date: Thu, 21 Jan 1999 17:27:08 +1030 From: Greg Lehey To: Andreas Klemm Cc: Matthew Dillon , current@FreeBSD.ORG Subject: Re: panic: vinvalbuf: dirty bufs (during reboot, several times) Message-ID: <19990121172707.U15785@freebie.lemis.com> References: <19990120073445.A402@titan.klemm.gtn.com> <199901200700.XAA76802@apollo.backplane.com> <19990120193354.A1554@titan.klemm.gtn.com> <19990121120900.R15785@freebie.lemis.com> <19990121071939.A13938@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990121071939.A13938@titan.klemm.gtn.com>; from Andreas Klemm on Thu, Jan 21, 1999 at 07:19:39AM +0100 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 21 January 1999 at 7:19:39 +0100, Andreas Klemm wrote: > On Thu, Jan 21, 1999 at 12:09:00PM +1030, Greg Lehey wrote: >> On Wednesday, 20 January 1999 at 19:33:54 +0100, Andreas Klemm wrote: >>> On Tue, Jan 19, 1999 at 11:00:55PM -0800, Matthew Dillon wrote: >>>> >>>> Hmm. Interesting, it's dying trying to fsync an FFS vnode. Are you >>>> by any chance running NFS ( client *or* server ) on this box? >>> >>> No, no NFS compiled in and am not using it. See my kernel config. >> >> Where's your kernel config? Are you running vinum? I had some >> problems with this in earlier versions, but I'm pretty sure none are >> left. > > Im my first mail (where I reported the problem) I sent kernel config > file and dmesg output. You shouldn't expect everybody to have kept that message. Matt obviously hadn't either. That's what quotes are for. > And no, sorry, am using ccd, not vinum. No need to apologize :-) If you had been using vinum, I'd have to worry about a potential bug. But it's conceivable that something similar exists in ccd. Try umounting the ccd file systems before shutting down and see what happens. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 23:00:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA25192 for freebsd-current-outgoing; Wed, 20 Jan 1999 23:00:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA25184 for ; Wed, 20 Jan 1999 23:00:54 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id XAA10740; Wed, 20 Jan 1999 23:00:34 -0800 (PST) (envelope-from dillon) Date: Wed, 20 Jan 1999 23:00:34 -0800 (PST) From: Matthew Dillon Message-Id: <199901210700.XAA10740@apollo.backplane.com> To: Luoqi Chen Cc: current@FreeBSD.ORG Subject: Re: panic: vinvalbuf: dirty bufs (during reboot, several times) References: <199901210536.AAA08007@lor.watermarkgroup.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Sorry, Matt, the patch in my previous email was fatally flawed. Try this one :below. The two printf() messages don't necessarily come out in pairs and :it's not just NFS bufs' B_CACHE bits are cleared, so my comment about :vm_page_is_valid() check in my previous message was wrong and the check is :needed here. : :-lq Ok, I understand what you've done... you are effectively bypassing having to check for B_DELWRI in bread(), breadn(), and nfs_bioread() by forcing getblk() to handle the B_DELWRI condition. Cool. I'll replace my nfs_bioread() patch with this one and test it before committing all this stuff to the -4.x branch ( which I will also do sometime tonight ). I am also CCing this to current so Greg and Andreas are kept abrest of events. I think this will fix *both* of their reported panics. -Matt Matthew Dillon :Index: vfs_bio.c :=================================================================== :RCS file: /home/ncvs/src/sys/kern/vfs_bio.c,v :retrieving revision 1.193 :diff -u -r1.193 vfs_bio.c :--- vfs_bio.c 1999/01/19 08:00:51 1.193 :+++ vfs_bio.c 1999/01/21 05:26:10 :@@ -1437,6 +1437,11 @@ : : if (bp->b_bcount != size) { : if ((bp->b_flags & B_VMIO) && (size <= bp->b_kvasize)) { :+printf("getblk: extending buf %ld->%d\n", bp->b_bcount, size); :+ if (bp->b_flags & B_DELWRI) { :+ VOP_BWRITE(bp); :+ goto loop; :+ } : allocbuf(bp, size); : } else { : if (bp->b_flags & B_DELWRI) { :@@ -1471,6 +1476,8 @@ : resid = (checksize > (PAGE_SIZE - poffset)) ? : (PAGE_SIZE - poffset) : checksize; : if (!vm_page_is_valid(bp->b_pages[i], poffset, resid)) { :+printf("getblk: clear B_CACHE, bufsize %ld, page %d valid %02x dirty %02x\n", :+ bp->b_bufsize, i, bp->b_pages[i]->valid, bp->b_pages[i]->dirty); : bp->b_flags &= ~(B_CACHE | B_DONE); : break; : } : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 23:04:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA25517 for freebsd-current-outgoing; Wed, 20 Jan 1999 23:04:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA25503 for ; Wed, 20 Jan 1999 23:04:41 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id RAA15777; Thu, 21 Jan 1999 17:34:26 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.2/8.9.0) id RAA29524; Thu, 21 Jan 1999 17:34:25 +1030 (CST) Date: Thu, 21 Jan 1999 17:34:25 +1030 From: Greg Lehey To: Matthew Dillon Cc: Luoqi Chen , current@FreeBSD.ORG Subject: Re: panic: vinvalbuf: dirty bufs (during reboot, several times) Message-ID: <19990121173424.V15785@freebie.lemis.com> References: <199901210536.AAA08007@lor.watermarkgroup.com> <199901210700.XAA10740@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199901210700.XAA10740@apollo.backplane.com>; from Matthew Dillon on Wed, Jan 20, 1999 at 11:00:34PM -0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 20 January 1999 at 23:00:34 -0800, Matthew Dillon wrote: >> Sorry, Matt, the patch in my previous email was fatally flawed. Try this one >> below. The two printf() messages don't necessarily come out in pairs and >> it's not just NFS bufs' B_CACHE bits are cleared, so my comment about >> vm_page_is_valid() check in my previous message was wrong and the check is >> needed here. >> >> -lq > > Ok, I understand what you've done... you are effectively bypassing > having to check for B_DELWRI in bread(), breadn(), and nfs_bioread() > by forcing getblk() to handle the B_DELWRI condition. > > Cool. I'll replace my nfs_bioread() patch with this one and test it > before committing all this stuff to the -4.x branch ( which I will also > do sometime tonight ). > > I am also CCing this to current so Greg and Andreas are kept abrest > of events. I think this will fix *both* of their reported panics. Not mine :-) Mine was a bug in vinum which I had already fixed; I was just concerned about whether it had shown its nose again. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 23:05:59 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA25624 for freebsd-current-outgoing; Wed, 20 Jan 1999 23:05:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles232.castles.com [208.214.165.232]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA25613 for ; Wed, 20 Jan 1999 23:05:55 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id XAA06653; Wed, 20 Jan 1999 23:00:29 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901210700.XAA06653@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "John Saunders" cc: Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: Booting -current with new loader In-reply-to: Your message of "Thu, 21 Jan 1999 11:58:13 +1100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 20 Jan 1999 23:00:27 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I'm not sure about anybody else here, but to my mind a "Winblows on C: > > > drive and let's try out FreeBSD on the second disk" configuration should > > > really be supported seamlessly. > > > > You're more than welcome to propose a technical solution that solves > > the problem. > > OK, the technical solution that I propose is an alternative (optional > because I want to retain the current semantics) config semantics. > > controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0xa0ffa0ff > controller wdc1 at isa? port "IO_WD2" bio irq 15 flags 0xa0ffa0ff > disk wd? at wdc? > > This would act identical to the way the SCSI system works by assigning > names to disks as they get probed. It would also have the advantage of > assigning disk names in the same order as the BIOS (and thereby the boot > loader), hence there would be a 1 to 1 mapping between what the boot > loader uses and what the FreeBSD kernel detects. > > I believe the current problem stems from the BIOS (and thereby the boot > loader) and the FreeBSD kernel assigning names using a different algorithm > and then getting out of step when the kernel skips a name. You're spot on the money here. If you have any good ideas about guaranteeing the probe order (and there are some other issues here, like what about systems where the BIOS doesn't know about the IDE disks?) matches up, I'm all ears. Later versions of the EDD spec offer a technique for geting a device path for a given ID, but support for that seems to be *very* flaky. > If anybody knows how to do this quickly then I am happy to help test it. Right now I'm looking at stamping the disklabel which contains the designated root filesystem and passing the stamp into the kernel, which will then go look for it. There are still gremlins with this approach, but I can't think of anything better. 8( -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 23:12:53 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA26151 for freebsd-current-outgoing; Wed, 20 Jan 1999 23:12:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA26144 for ; Wed, 20 Jan 1999 23:12:47 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id XAA11040; Wed, 20 Jan 1999 23:12:22 -0800 (PST) (envelope-from dillon) Date: Wed, 20 Jan 1999 23:12:22 -0800 (PST) From: Matthew Dillon Message-Id: <199901210712.XAA11040@apollo.backplane.com> To: Greg Lehey Cc: Luoqi Chen , current@FreeBSD.ORG Subject: Re: panic: vinvalbuf: dirty bufs (during reboot, several times) References: <199901210536.AAA08007@lor.watermarkgroup.com> <199901210700.XAA10740@apollo.backplane.com> <19990121173424.V15785@freebie.lemis.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :>... :> having to check for B_DELWRI in bread(), breadn(), and nfs_bioread() :> by forcing getblk() to handle the B_DELWRI condition. :> :> Cool. I'll replace my nfs_bioread() patch with this one and test it :> before committing all this stuff to the -4.x branch ( which I will also :> do sometime tonight ). :> :> I am also CCing this to current so Greg and Andreas are kept abrest :> of events. I think this will fix *both* of their reported panics. : :Not mine :-) Mine was a bug in vinum which I had already fixed; I was :just concerned about whether it had shown its nose again. : :Greg Ah, excellent. If my tests of Luoqi's fix work, I'll commit it as part of my big VM commit to -4.x, and also commit this and a few other simple VM bug fixes to -3.x. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 23:32:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA27806 for freebsd-current-outgoing; Wed, 20 Jan 1999 23:32:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fw.bby.com.au (ns.bby.com.au [192.83.119.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA27798 for ; Wed, 20 Jan 1999 23:32:31 -0800 (PST) (envelope-from gnb@itga.com.au) Received: (from daemon@localhost) by fw.bby.com.au (8.8.8/8.6.9) id SAA04080 for ; Thu, 21 Jan 1999 18:32:18 +1100 (EST) Received: from lightning.itga.com.au(192.168.71.20) via SMTP by fw.bby.com.au, id smtpd004078; Thu Jan 21 07:32:15 1999 Received: from lightning (lightning [192.168.71.20]) by lightning.itga.com.au (8.9.1a/8.9.1) with ESMTP id SAA09979; Thu, 21 Jan 1999 18:32:15 +1100 (EST) Message-Id: <199901210732.SAA09979@lightning.itga.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: current@FreeBSD.ORG Subject: some guidance on forked cvsup please Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Jan 1999 18:32:15 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Now we've gone and got forked, can someone please give us examples of cvsup files for those that want to follow 4-current and those that want to follow 3-stable. Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 23:47:59 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA29118 for freebsd-current-outgoing; Wed, 20 Jan 1999 23:47:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA29113 for ; Wed, 20 Jan 1999 23:47:58 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id XAA12203; Wed, 20 Jan 1999 23:47:47 -0800 (PST) (envelope-from dillon) Date: Wed, 20 Jan 1999 23:47:47 -0800 (PST) From: Matthew Dillon Message-Id: <199901210747.XAA12203@apollo.backplane.com> To: Greg Lehey , Luoqi Chen , current@FreeBSD.ORG Subject: Re: panic: vinvalbuf: dirty bufs (during reboot, several times) References: <199901210536.AAA08007@lor.watermarkgroup.com> <199901210700.XAA10740@apollo.backplane.com> <19990121173424.V15785@freebie.lemis.com> <199901210712.XAA11040@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : : Ah, excellent. If my tests of Luoqi's fix work, I'll commit it as : part of my big VM commit to -4.x, and also commit this and a few : other simple VM bug fixes to -3.x. Oops, there is still something broken. I think getblk() needs to be reorganized completely, there are still cases where B_CACHE gets cleared and B_DELWRI can leak through without getting comitted. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 20 23:57:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA00193 for freebsd-current-outgoing; Wed, 20 Jan 1999 23:57:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA00188 for ; Wed, 20 Jan 1999 23:57:25 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id XAA12288; Wed, 20 Jan 1999 23:57:09 -0800 (PST) (envelope-from dillon) Date: Wed, 20 Jan 1999 23:57:09 -0800 (PST) From: Matthew Dillon Message-Id: <199901210757.XAA12288@apollo.backplane.com> To: Gregory Bond Cc: current@FreeBSD.ORG Subject: Re: some guidance on forked cvsup please References: <199901210732.SAA09979@lightning.itga.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Now we've gone and got forked, can someone please give us examples of cvsup :files for those that want to follow 4-current and those that want to follow :3-stable. : :Thanks! It's real simple. The -stable is the 3.x branch. This is the branch that Jordan just created tonight. So, for example, if you do a 'cvs log kern/vfs_bio.c' you will see this: ... head: 1.193 ... RELENG_3: 1.193.0.2 RELENG_3_BP: 1.193 What this means is that the HEAD of the CVS tree is 1.193, and RELENG_3 ( the new -stable ) has been forked off as 1.193.0.2. If your files are currently checked out and have the HEAD branch's revision, then anything you checkin will be checked in under -current ( the -4.x tree ). If your files are currently checked out and have RELENG_3's branch revision, then anything you check in will be checked in under -stable ( the -3.x tree ). If you haven't messed with your CVS tree and it was previously -current ( 3.x ), it is still -current, but is now 4.x. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 00:04:01 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA00787 for freebsd-current-outgoing; Thu, 21 Jan 1999 00:04:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA00775 for ; Thu, 21 Jan 1999 00:03:59 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id XAA06618; Wed, 20 Jan 1999 23:58:10 -0800 (PST) Received: from s204m82.isp.whistle.com(207.76.204.82) via SMTP by alpo.whistle.com, id smtpdsI6615; Thu Jan 21 07:58:00 1999 Date: Wed, 20 Jan 1999 23:57:56 -0800 (PST) From: Julian Elischer X-Sender: julian@s204m82.isp.whistle.com To: Mike Smith cc: Christian Kuhtz , "David O'Brien" , current@FreeBSD.ORG Subject: Re: KLD naming In-Reply-To: <199901210556.VAA06281@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG well you're about to get your first test.... we are releasing the netgrpah code in full production form tonigh (if the version we've put together for release passes all tests tonight) The whole thing installs as KLD modules (or linked in of course) our present names are all predicated with ng_ hence ng_socket ng_rfc1490, ng_frame_relay etc the base module is 'netgraph'. now what would you suggest? we can still cahnge it before we release and no-body knows any better but after is always harder to change than beefore.. julian On Wed, 20 Jan 1999, Mike Smith wrote: > > On Wed, Jan 20, 1999 at 07:19:15PM -0800, David O'Brien wrote: > > [..] > > > etc? This is what the original poster suggested, and nobody has really > > > given a good response what is wrong with the "grouping" being expressed > > > in the modules' name. Mike Smith and Andrzej Bialecki have given good > > > reasons why *not* to go to a subdirectory structure. > > > > What would you name a network stack? For example: > > > > net_mpls_tdp.ko > > net_mpls_ldp.ko > > net_mpls_core.ko > > > > or > > net_h323v2_yada.ko > > net_h323v2_yadayada.ko > > net_h323v2_barf.ko > > > > or > > codec_g711.ko > > codec_g7231a.ko > > codec_g729.ko > > > > Is that acceptable? Anyone have better ideas? > > I guess it depends on how fancy we want to get. Here are some examples > that I've been rolling around; some are fanciful, some practical) > > dev_ generic device (eg. dev_sio) > bus_ bus support (eg. bus_pci) > netif_ network interface (eg. netif_ed) > netproto_ network protocol (eg. netproto_arp) > netdomain_ network domain (eg. netdomain_ip) > vfs_ VFS layer (eg. vfs_nfs) > kern_ kernel infrastructure (eg. kern_vfs) > syscall_ loadable system calls (eg. syscall_sendfile) > > I don't think we want to make the mistake of being too specific about > what pigeonhole something falls into. In many cases, we might want new > categories when a new case arises, eg. for USB we might have: > > bus_usb.ko > usb_hub.ko > usb_mouse.ko > usb_keyboard.ko > usb_disk.ko > usb_scanner.ko > ... > > There's no ambiguity here, the names are simple and convey a direct > set of relationships. Your examples (except the first) do a pretty > good job of the same thing. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 00:08:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA01199 for freebsd-current-outgoing; Thu, 21 Jan 1999 00:08:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from camel.ethereal.net (camel.ethereal.net [206.79.74.102]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA01193 for ; Thu, 21 Jan 1999 00:08:26 -0800 (PST) (envelope-from mistwolf@camel.ethereal.net) Received: (from mistwolf@localhost) by camel.ethereal.net (8.9.1a/8.9.1) id AAA03789; Thu, 21 Jan 1999 00:07:21 -0800 (PST) Message-ID: <19990121000721.B3580@ethereal.net> Date: Thu, 21 Jan 1999 00:07:21 -0800 From: Jamie Norwood To: Matthew Dillon , Gregory Bond Cc: current@FreeBSD.ORG Subject: Re: some guidance on forked cvsup please References: <199901210732.SAA09979@lightning.itga.com.au> <199901210757.XAA12288@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199901210757.XAA12288@apollo.backplane.com>; from Matthew Dillon on Wed, Jan 20, 1999 at 11:57:09PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I currently run a 2.2.8 machine. Is there a guide somewhere on the exact process of bringing this up to the forthcoming 3.0 stable branch, such as the conversion from sdX to CAM, a.out to Elf, what softupdates are and who should use them, SMP, and the like? I am about to buy a new, dual proc mainboard to coincide with 3.0 going stable, and all of these are of interest to me, but I'm not sure the best way to migrate from the 'old' 2.2.x system to the 'new' 3.x system. Thanks! Jamie On Wed, Jan 20, 1999 at 11:57:09PM -0800, Matthew Dillon wrote: > > It's real simple. The -stable is the 3.x branch. This is the branch > that Jordan just created tonight. So, for example, if you do a > 'cvs log kern/vfs_bio.c' you will see this: > > ... > head: 1.193 > ... > RELENG_3: 1.193.0.2 > RELENG_3_BP: 1.193 > > What this means is that the HEAD of the CVS tree is 1.193, and > RELENG_3 ( the new -stable ) has been forked off as 1.193.0.2. > > If your files are currently checked out and have the HEAD branch's > revision, then anything you checkin will be checked in under > -current ( the -4.x tree ). > > If your files are currently checked out and have RELENG_3's branch > revision, then anything you check in will be checked in under > -stable ( the -3.x tree ). > > If you haven't messed with your CVS tree and it was previously > -current ( 3.x ), it is still -current, but is now 4.x. > > -Matt > Matthew Dillon > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 00:09:38 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA01481 for freebsd-current-outgoing; Thu, 21 Jan 1999 00:09:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles310.castles.com [208.214.167.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA01471 for ; Thu, 21 Jan 1999 00:09:35 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id AAA07073; Thu, 21 Jan 1999 00:05:57 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901210805.AAA07073@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Julian Elischer cc: Christian Kuhtz , "David O'Brien" , current@FreeBSD.ORG Subject: Re: KLD naming In-reply-to: Your message of "Wed, 20 Jan 1999 23:57:56 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Jan 1999 00:05:57 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > well you're about to get your first test.... > we are releasing the netgrpah code in full production form tonigh (if > the version we've put together for release passes all tests tonight) > The whole thing installs as KLD modules (or linked in of course) > > our present names are all predicated with ng_ > hence ng_socket ng_rfc1490, ng_frame_relay etc > the base module is 'netgraph'. > > now what would you suggest? > we can still cahnge it before we release and no-body knows any better but > after is always harder to change than beefore.. Hmm. Where does "netgraph" fit in? From your earlier commits, I presume it's a domain, so I would suggest: netdomain_netgraph.ko netgraph_rfc1490.ko netgraph_framerelay.ko ... ie. don't be afraid to be verbose. I'd certainly say "no" to a two-letter abbreviation. > julian > > > On Wed, 20 Jan 1999, Mike Smith wrote: > > > > On Wed, Jan 20, 1999 at 07:19:15PM -0800, David O'Brien wrote: > > > [..] > > > > etc? This is what the original poster suggested, and nobody has really > > > > given a good response what is wrong with the "grouping" being expressed > > > > in the modules' name. Mike Smith and Andrzej Bialecki have given good > > > > reasons why *not* to go to a subdirectory structure. > > > > > > What would you name a network stack? For example: > > > > > > net_mpls_tdp.ko > > > net_mpls_ldp.ko > > > net_mpls_core.ko > > > > > > or > > > net_h323v2_yada.ko > > > net_h323v2_yadayada.ko > > > net_h323v2_barf.ko > > > > > > or > > > codec_g711.ko > > > codec_g7231a.ko > > > codec_g729.ko > > > > > > Is that acceptable? Anyone have better ideas? > > > > I guess it depends on how fancy we want to get. Here are some examples > > that I've been rolling around; some are fanciful, some practical) > > > > dev_ generic device (eg. dev_sio) > > bus_ bus support (eg. bus_pci) > > netif_ network interface (eg. netif_ed) > > netproto_ network protocol (eg. netproto_arp) > > netdomain_ network domain (eg. netdomain_ip) > > vfs_ VFS layer (eg. vfs_nfs) > > kern_ kernel infrastructure (eg. kern_vfs) > > syscall_ loadable system calls (eg. syscall_sendfile) > > > > I don't think we want to make the mistake of being too specific about > > what pigeonhole something falls into. In many cases, we might want new > > categories when a new case arises, eg. for USB we might have: > > > > bus_usb.ko > > usb_hub.ko > > usb_mouse.ko > > usb_keyboard.ko > > usb_disk.ko > > usb_scanner.ko > > ... > > > > There's no ambiguity here, the names are simple and convey a direct > > set of relationships. Your examples (except the first) do a pretty > > good job of the same thing. > > > > -- > > \\ Sometimes you're ahead, \\ Mike Smith > > \\ sometimes you're behind. \\ mike@smith.net.au > > \\ The race is long, and in the \\ msmith@freebsd.org > > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 00:20:41 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA02435 for freebsd-current-outgoing; Thu, 21 Jan 1999 00:20:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from post.mail.demon.net (post-11.mail.demon.net [194.217.242.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA02429 for ; Thu, 21 Jan 1999 00:20:39 -0800 (PST) (envelope-from dom@myrddin.demon.co.uk) Received: from [158.152.54.180] (helo=myrddin.demon.co.uk) by post.mail.demon.net with esmtp (Exim 2.10 #2) id 103FLq-0001AB-00; Thu, 21 Jan 1999 08:20:31 +0000 Received: from localhost (myrddin.demon.co.uk) [127.0.0.1] by myrddin.demon.co.uk with esmtp (Exim 1.92 #1) id 103F4Y-0000NV-00; Thu, 21 Jan 1999 08:02:38 +0000 To: Mike Nguyen Cc: current@FreeBSD.ORG Subject: Re: /etc/nsswitch.conf References: From: Dom Mitchell In-Reply-To: Mike Nguyen's message of "Wed, 20 Jan 1999 08:53:34 -0600 (CST)" X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Date: Thu, 21 Jan 1999 08:02:38 +0000 Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Nguyen writes: > I noticed that NetBSD is switching over to using /etc/nsswitch.conf (like > Slowlaris, PH-UX, etc.). Would it be a good idea to do this for FreeBSD too > (when I first started using FreeBSD, it took me a long time to figure out the > analogous file for hostname lookups was /etc/host.conf) -- it seems > consolidating all that config information would in one place would be a good > thing. There was talk of integrating into libc something which we already have in our tree: irs.conf. It's part of the bind source. Nothing seems to have happened though. It's a fairly major change to lots of libc. -- When I said "we", officer, I was referring to myself, the four young ladies, and, of course, the goat. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 00:37:38 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA04169 for freebsd-current-outgoing; Thu, 21 Jan 1999 00:37:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rebma.ghostwheel.com (rebma.ghostwheel.com [207.201.56.159]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA04164 for ; Thu, 21 Jan 1999 00:37:35 -0800 (PST) (envelope-from fbsd-cur@ghostwheel.com) Received: from avalon (avalon.ghostwheel.com [207.201.56.88]) by rebma.ghostwheel.com (8.8.8/8.8.8) with SMTP id AAA07216; Thu, 21 Jan 1999 00:37:09 -0800 (PST) (envelope-from fbsd-cur@ghostwheel.com) Message-Id: <4.1.19990121002356.009b0a60@pop.ghostwheel.com> X-Sender: fbsd-cur@pop2.ghostwheel.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Thu, 21 Jan 1999 00:24:24 -0800 To: Greg Lehey From: Chris Knight Subject: Re: HEADS UP: New version of Vinum Cc: FreeBSD current users In-Reply-To: <19990121141315.H15785@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 02:13 PM 1/21/99 +1030, you wrote: >I've just committed a new version of Vinum with a large number of >changes. It works fine here, much better than the old version, but >there's just a possibility that things may go wrong. If you have >trouble, please let me know immediately. Greg, Was this just committed to -current, or is this also in -stable (now that it exists)? I'd like to move to -stable, but if the latest Vinum mods are going to take a while to move to -current I'll be staying here for the duration. :) -ck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 00:55:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA06182 for freebsd-current-outgoing; Thu, 21 Jan 1999 00:55:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA06177; Thu, 21 Jan 1999 00:55:46 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id AAA05930; Thu, 21 Jan 1999 00:55:38 -0800 (PST) (envelope-from dillon) Date: Thu, 21 Jan 1999 00:55:38 -0800 (PST) From: Matthew Dillon Message-Id: <199901210855.AAA05930@apollo.backplane.com> To: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Heads up! New swapper and VM changes have been committed to -4.x References: <199901210456.UAA10191@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's all in. The more feedback the better. You will have to recompile KVM-related support programs, especially pstat. I also suggest recompiling libkvm, ps, top, vmstat, systat, etc... The new swapper is not understood by top or systat yet but it is well understood by pstat -s ( aka swapinfo ), and pstat -ss will dump the radix tree. One thing I haven't been able to test, because I forgot: Interleaved swap ( more then one swap device ). I'll try to test that ASAP. I've tested everything else as well as I've been able, mainly by running 'make -j30 buildworld', make on various ports, eatmem, and other applications all at once on my test box. No comments on syntax, please, the commit is understood to be rough and the syntax and comments will be fixed up with more commits. I intend to make further forced commits to document special items, such as core bug fixes, and addlib other comments. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 01:31:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA10359 for freebsd-current-outgoing; Thu, 21 Jan 1999 01:31:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA10353 for ; Thu, 21 Jan 1999 01:31:14 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id UAA16438; Thu, 21 Jan 1999 20:01:01 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.2/8.9.0) id UAA00816; Thu, 21 Jan 1999 20:01:00 +1030 (CST) Date: Thu, 21 Jan 1999 20:00:59 +1030 From: Greg Lehey To: Matthew Dillon Cc: FreeBSD current users Subject: Re: Heads up! New swapper and VM changes have been committed to -4.x Message-ID: <19990121200059.B417@freebie.lemis.com> References: <199901210456.UAA10191@apollo.backplane.com> <199901210855.AAA05930@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199901210855.AAA05930@apollo.backplane.com>; from Matthew Dillon on Thu, Jan 21, 1999 at 12:55:38AM -0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 21 January 1999 at 0:55:38 -0800, Matthew Dillon wrote: > It's all in. The more feedback the better. > > You will have to recompile KVM-related support programs, especially > pstat. I also suggest recompiling libkvm, ps, top, vmstat, systat, > etc... > > The new swapper is not understood by top or systat yet but it is > well understood by pstat -s ( aka swapinfo ), and pstat -ss will > dump the radix tree. > > One thing I haven't been able to test, because I forgot: Interleaved > swap ( more then one swap device ). I'll try to test that ASAP. Please let us know when you've done it. I think I'll hold off until then. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 01:34:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA10924 for freebsd-current-outgoing; Thu, 21 Jan 1999 01:34:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA10824 for ; Thu, 21 Jan 1999 01:33:59 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id JAA55271; Thu, 21 Jan 1999 09:34:28 GMT Date: Thu, 21 Jan 1999 09:34:28 +0000 (GMT) From: Doug Rabson To: Mike Smith cc: Christian Kuhtz , "David O'Brien" , current@FreeBSD.ORG Subject: Re: KLD naming In-Reply-To: <199901210556.VAA06281@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 20 Jan 1999, Mike Smith wrote: > I guess it depends on how fancy we want to get. Here are some examples > that I've been rolling around; some are fanciful, some practical) > > dev_ generic device (eg. dev_sio) > bus_ bus support (eg. bus_pci) > netif_ network interface (eg. netif_ed) > netproto_ network protocol (eg. netproto_arp) > netdomain_ network domain (eg. netdomain_ip) > vfs_ VFS layer (eg. vfs_nfs) > kern_ kernel infrastructure (eg. kern_vfs) > syscall_ loadable system calls (eg. syscall_sendfile) > > I don't think we want to make the mistake of being too specific about > what pigeonhole something falls into. In many cases, we might want new > categories when a new case arises, eg. for USB we might have: > > bus_usb.ko > usb_hub.ko > usb_mouse.ko > usb_keyboard.ko > usb_disk.ko > usb_scanner.ko > ... > > There's no ambiguity here, the names are simple and convey a direct > set of relationships. Your examples (except the first) do a pretty > good job of the same thing. This is good. As far as I'm concerned, we should go with this. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 01:37:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA11231 for freebsd-current-outgoing; Thu, 21 Jan 1999 01:37:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA11226 for ; Thu, 21 Jan 1999 01:37:46 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id UAA16464; Thu, 21 Jan 1999 20:07:35 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.2/8.9.0) id UAA00869; Thu, 21 Jan 1999 20:07:35 +1030 (CST) Date: Thu, 21 Jan 1999 20:07:35 +1030 From: Greg Lehey To: Chris Knight Cc: FreeBSD current users Subject: Re: HEADS UP: New version of Vinum Message-ID: <19990121200734.C417@freebie.lemis.com> References: <19990121141315.H15785@freebie.lemis.com> <4.1.19990121002356.009b0a60@pop.ghostwheel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <4.1.19990121002356.009b0a60@pop.ghostwheel.com>; from Chris Knight on Thu, Jan 21, 1999 at 12:24:24AM -0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 21 January 1999 at 0:24:24 -0800, Chris Knight wrote: > At 02:13 PM 1/21/99 +1030, you wrote: >> I've just committed a new version of Vinum with a large number of >> changes. It works fine here, much better than the old version, but >> there's just a possibility that things may go wrong. If you have >> trouble, please let me know immediately. > > Greg, > > Was this just committed to -current, or is this also in -stable (now that > it exists)? It was committed to the tree minutes before the tagging, so currently both branches have the same content. > I'd like to move to -stable, but if the latest Vinum mods are going to > take a while to move to -current I'll be staying here for the duration. :) Well, it's more like the other way round: the changes go to -current first, and then move to -stable. You can expect a number of changes in both versions in the next few weeks. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 01:44:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA11972 for freebsd-current-outgoing; Thu, 21 Jan 1999 01:44:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA11929; Thu, 21 Jan 1999 01:43:54 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id KAA28172; Thu, 21 Jan 1999 10:47:55 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Thu, 21 Jan 1999 10:47:55 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Matthew Dillon cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Heads up! New swapper and VM changes being committed to -4.x tonight. In-Reply-To: <199901210456.UAA10191@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 20 Jan 1999, Matthew Dillon wrote: > The new swapper and a bunch of VM stuff I've been sitting > on is going to be committed into the new -current tree tonight. I'm more than willing to test it in low memory conditions.. :-) I have that special 386SX/4MB RAM machine in the corner to test things like picobsd memory requirements... Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 01:50:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA12944 for freebsd-current-outgoing; Thu, 21 Jan 1999 01:50:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA12938 for ; Thu, 21 Jan 1999 01:50:53 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id SAA02021; Thu, 21 Jan 1999 18:50:33 +0900 (JST) Message-ID: <36A6F1A9.9DE01A79@newsguy.com> Date: Thu, 21 Jan 1999 18:21:45 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Peter Jeremy CC: current@FreeBSD.ORG Subject: Re: Experiences with aout-to-elf and new bootblocks References: <99Jan21.125134est.40340@border.alcanet.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Jeremy wrote: > > tutorial: http://www.freebsd.org/~peter/elfday.html). I found that > /boot/loader could load my 2.x kernel (although it happily handled ^^^^^^^^^^ You mean "could not", right? > [gzip'd] -current kernels in both a.out and ELF format). The stage2 > loader boot: prompt happily loaded the 2.x kernel. When /boot/loader > tries to load my 2.x kernel, the screen displays gibberish and the > system locks up (hard reset needed). Any ideas on this one? Is it kzipped, your 2.x kernel? (Is there any detail about it that you think it is not relevant? :-) > Finally, whilst I can happily load a 3.x kernel from my 2nd HD, > the kernel is confused about where it's loading from: It can't > find root and panics. > > System details: PII-266 with IDE disks: > primary master: wd0: dualboot (W95/FreeBSD 2.x) > primary slave: ATAPI cdrom > secondary master: wd2: FreeBSD 3.0 (not dangerously dedicated) > secondary slave: not present > > Both the 2.x and -current kernels correctly recognize both disks > during the probes. When I try to boot from wd2a, the kernel > reports: > changing root device to wd1s1a > changing root device to wd1a > error 6: panic cannot mount root(2) > > If I recall correctly, the problem here is that the BIOS is reporting > the 2 HDs as 0 and 1, rather than 0 and 2. I can't recall what the > work-around is (I'd prefer not to juggle the disks). Any suggestions? Well, kind of. You "hard code" the name wd2 in your kernel configuration file. Loader assigns numbers sequentially. Either we teach loader to hard code names (which is probably an excellent idea), or you assign names to your hd following loader's logic. Ie, s/wd2/wd1/ in your kernel configuration file (and rebuild :). BTW, what *devfs* would call that second drive, anyone? I suspect this "hard coding" might not be... healthy... -- Daniel C. Sobral (8-DCS) dcs@newsguy.com If you sell your soul to the Devil and all you get is an MCSE from it, you haven't gotten market rate. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 01:55:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA13220 for freebsd-current-outgoing; Thu, 21 Jan 1999 01:55:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA13209 for ; Thu, 21 Jan 1999 01:55:03 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.10 #1) id 103Go8-000JGC-00; Thu, 21 Jan 1999 11:53:48 +0200 From: Sheldon Hearn To: "Daniel C. Sobral" cc: Peter Jeremy , current@FreeBSD.ORG Subject: Re: Experiences with aout-to-elf and new bootblocks In-reply-to: Your message of "Thu, 21 Jan 1999 18:21:45 +0900." <36A6F1A9.9DE01A79@newsguy.com> Date: Thu, 21 Jan 1999 11:53:48 +0200 Message-ID: <74039.916912428@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 21 Jan 1999 18:21:45 +0900, "Daniel C. Sobral" wrote: > Well, kind of. You "hard code" the name wd2 in your kernel > configuration file. Loader assigns numbers sequentially. FWIW, I've never seen FreeBSD boot off a drive on the secondary IDE controller using a boot manager on the primary. I haven't tried with CURRENT. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 02:22:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA15992 for freebsd-current-outgoing; Thu, 21 Jan 1999 02:22:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mescalero.asd1.rl.ac.uk (mescalero.asd1.rl.ac.uk [130.246.170.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA15979 for ; Thu, 21 Jan 1999 02:22:28 -0800 (PST) (envelope-from tmb@rcru.rl.ac.uk) Received: from rcru.rl.ac.uk (LOCALHOST [127.0.0.1]) by mescalero.asd1.rl.ac.uk (8.9.1/8.9.1) with ESMTP id KAA64271; Thu, 21 Jan 1999 10:21:12 GMT (envelope-from tmb@rcru.rl.ac.uk) Message-Id: <199901211021.KAA64271@mescalero.asd1.rl.ac.uk> To: Sheldon Hearn cc: "Daniel C. Sobral" , Peter Jeremy , current@FreeBSD.ORG, tmb@mescalero.asd1.rl.ac.uk Subject: Re: Experiences with aout-to-elf and new bootblocks In-reply-to: Your message of "Thu, 21 Jan 1999 11:53:48 +0200." <74039.916912428@axl.noc.iafrica.com> Date: Thu, 21 Jan 1999 10:21:12 +0000 From: Mark Blackman Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FWIW, I've done it under 2.2.7 by 1) installing booteasy on both wd0 *AND* wd2 2) altering the boot.config to 1:wd(2,a)kernel 3) compiling above kernel with config kernel root on wd2 Mark In message <74039.916912428@axl.noc.iafrica.com>, Sheldon Hearn writes: > > >On Thu, 21 Jan 1999 18:21:45 +0900, "Daniel C. Sobral" wrote: > >> Well, kind of. You "hard code" the name wd2 in your kernel >> configuration file. Loader assigns numbers sequentially. > >FWIW, I've never seen FreeBSD boot off a drive on the secondary IDE >controller using a boot manager on the primary. I haven't tried with >CURRENT. > >Ciao, >Sheldon. > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 03:14:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA20506 for freebsd-current-outgoing; Thu, 21 Jan 1999 03:14:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from octopus.originative.co.uk (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA20492 for ; Thu, 21 Jan 1999 03:14:07 -0800 (PST) (envelope-from paul@originative.co.uk) From: paul@originative.co.uk Received: by OCTOPUS with Internet Mail Service (5.5.1960.3) id ; Thu, 21 Jan 1999 11:12:31 -0000 Message-ID: To: julian@whistle.com, mike@smith.net.au Cc: ck@adsu.bellsouth.com, obrien@NUXI.com, current@FreeBSD.ORG Subject: RE: KLD naming Date: Thu, 21 Jan 1999 11:12:27 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Julian Elischer [mailto:julian@whistle.com] > Sent: Thursday, January 21, 1999 7:58 AM > To: Mike Smith > Cc: Christian Kuhtz; David O'Brien; current@FreeBSD.ORG > Subject: Re: KLD naming > > > well you're about to get your first test.... > we are releasing the netgrpah code in full production form tonigh (if > the version we've put together for release passes all tests tonight) > The whole thing installs as KLD modules (or linked in of course) > > our present names are all predicated with ng_ > hence ng_socket ng_rfc1490, ng_frame_relay etc > the base module is 'netgraph'. > > now what would you suggest? > we can still cahnge it before we release and no-body knows > any better but > after is always harder to change than beefore.. Why not have a third party identifier on the front, e.g. whistle_ng_rfc1490 You can determine your own naming scheme then and if we make this standard then it will ensure that third party supplied modules don't result in name space conflicts. It's perfectly feasible in the future that different companies might produce competing modules for subsystems, sound for example, so we might as well deal with this possibility now. Makes it easier to identify the source of the modules as well. Perhaps we should adopt a FreeBSD prefix on core modules so you can see from ls what's part of the OS and what's been added in from elsewhere. Although I'm in favour of this naming scheme over directories you can reach the point where the names are holding too much metainformation that really should be directory structure. There wouldn't be need for directories at all if you put the structure in the filename :-) Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 03:34:22 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA22957 for freebsd-current-outgoing; Thu, 21 Jan 1999 03:34:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from teknos.teknos.com (teknos.teknos.com [216.0.190.11] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA22952 for ; Thu, 21 Jan 1999 03:34:20 -0800 (PST) (envelope-from salaman@teknos.com) Received: by teknos.teknos.com with Internet Mail Service (5.5.2448.0) id ; Thu, 21 Jan 1999 07:41:21 -0400 Message-ID: <608F4F76C94DD211B93100805F29063A8D35@teknos.teknos.com> From: Victor Salaman To: "'freebsd-current@freebsd.org'" Subject: Make world dies on 3.0 STABLE Date: Thu, 21 Jan 1999 07:41:20 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just csvup'ed the sources...(I had the sources from January 12's snapshot). While trying to do a "make world", eventually I get this message. c++ -pg -I/usr/obj/usr/src/tmp/usr/include/g++ -nostdinc -O -pipe -I/usr/src/gnu /lib/libstdc++/../../../contrib/libg++/include -I/usr/obj/usr/src/tmp/usr/includ e/g++ -I. -I/usr/obj/usr/src/tmp/usr/include -I/usr/src/gnu/lib/libstdc++/../../ ../contrib/libg++/include -I/usr/src/gnu/lib/libstdc++/../../../contrib/libg++/l ibio -I/usr/src/gnu/lib/libstdc++/../../../contrib/libg++/libstdc++ -fno-implici t-templates -c /usr/src/gnu/lib/libstdc++/../../../contrib/libg++/libio/fstream. cc -o fstream.po /usr/obj/usr/src/tmp/usr/include/g++/streambuf.h: In method `void ios::clear(int = 0)': In file included from /usr/obj/usr/src/tmp/usr/include/g++/iostream.h:31, from /usr/obj/usr/src/tmp/usr/include/g++/fstream.h:30, from /usr/src/gnu/lib/libstdc++/../../../contrib/libg++/libio/f stream.cc:34: /usr/obj/usr/src/tmp/usr/include/g++/streambuf.h:202: `_strbuf' undeclared (firs t use this function) /usr/obj/usr/src/tmp/usr/include/g++/streambuf.h:202: (Each undeclared identifie r is reported only once /usr/obj/usr/src/tmp/usr/include/g++/streambuf.h:202: for each function it appea rs in.) /usr/obj/usr/src/tmp/usr/include/g++/streambuf.h: In method `class streambuf * i os::rdbuf() const': /usr/obj/usr/src/tmp/usr/include/g++/streambuf.h:220: `_strbuf' undeclared (firs t use this function) /usr/obj/usr/src/tmp/usr/include/g++/streambuf.h: In method `class streambuf * i os::rdbuf(class streambuf *)': /usr/obj/usr/src/tmp/usr/include/g++/streambuf.h:222: `_strbuf' undeclared (firs t use this function) /usr/obj/usr/src/tmp/usr/include/g++/streambuf.h: In method `void ios::init(stru ct streambuf *, class ostream * = 0)': /usr/obj/usr/src/tmp/usr/include/g++/streambuf.h:458: `_strbuf' undeclared (firs t use this function) /usr/obj/usr/src/tmp/usr/include/g++/iostream.h: In method `class ostream & ostr eam::put(char)': In file included from /usr/obj/usr/src/tmp/usr/include/g++/fstream.h:30, from /usr/src/gnu/lib/libstdc++/../../../contrib/libg++/libio/f stream.cc:34: /usr/obj/usr/src/tmp/usr/include/g++/iostream.h:56: `_strbuf' undeclared (first use this function) /usr/obj/usr/src/tmp/usr/include/g++/iostream.h: In method `struct streambuf * o stream::ostreambuf() const': /usr/obj/usr/src/tmp/usr/include/g++/iostream.h:104: `_strbuf' undeclared (first use this function) /usr/obj/usr/src/tmp/usr/include/g++/iostream.h: In method `int istream::get()': /usr/obj/usr/src/tmp/usr/include/g++/iostream.h:165: `_strbuf' undeclared (first use this function) /usr/obj/usr/src/tmp/usr/include/g++/iostream.h: In method `class istream & istr eam::putback(char)': /usr/obj/usr/src/tmp/usr/include/g++/iostream.h:177: `_strbuf' undeclared (first use this function) /usr/obj/usr/src/tmp/usr/include/g++/iostream.h: In method `class istream & istr eam::unget()': /usr/obj/usr/src/tmp/usr/include/g++/iostream.h:180: `_strbuf' undeclared (first use this function) /usr/obj/usr/src/tmp/usr/include/g++/iostream.h: In method `struct streambuf * i stream::istreambuf() const': /usr/obj/usr/src/tmp/usr/include/g++/iostream.h:187: `_strbuf' undeclared (first use this function) *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. and then dies! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 03:40:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA23526 for freebsd-current-outgoing; Thu, 21 Jan 1999 03:40:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA23430 for ; Thu, 21 Jan 1999 03:39:59 -0800 (PST) (envelope-from rock@cs.uni-sb.de) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.2/1999010400) with ESMTP id MAA26450 for ; Thu, 21 Jan 1999 12:39:38 +0100 (CET) Received: from cs.uni-sb.de (maxtnt-180.telip.uni-sb.de [134.96.71.51]) by cs.uni-sb.de (8.9.2/1999010400) with ESMTP id MAA18252 for ; Thu, 21 Jan 1999 12:39:37 +0100 (CET) Message-ID: <36A711FD.85F65545@cs.uni-sb.de> Date: Thu, 21 Jan 1999 12:39:41 +0100 From: "D. Rock" X-Mailer: Mozilla 4.5 [de] (WinNT; U) X-Accept-Language: de MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: NFS v3 issue Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With NFS v3 there seem still to be some open issues. Im running the latest (4.0)-current with the new vm/NFS changes. While I haven't found any problems with NFSv2 so far, v3 still seems to make trouble. I noticed the error some months ago, while my /usr/obj was NFS mounted, and a build failed while making termcap.db. Today, I gave it another try. I copied /usr/src/share/termcap into an NFS mounted directory and did a "make". I compared the output of termcap.db with the one build on the local drive. While the NFS mounted one was only 1077760 bytes in size, the correct size (from the local build) should be 1245184 bytes. I did the build several times, everytime I got the same values. I then remounted the direcory NFSv2. Now the build produced the right file (in size and content). The NFS Server is a Solaris 7 machine. Can anyone else confirm this error? Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 04:05:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA26552 for freebsd-current-outgoing; Thu, 21 Jan 1999 04:05:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA26362 for ; Thu, 21 Jan 1999 04:01:41 -0800 (PST) (envelope-from dawes@rf900.physics.usyd.edu.au) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.9.1a/8.9.1) id XAA11708 for current@freebsd.org; Thu, 21 Jan 1999 23:01:29 +1100 (EST) Message-ID: <19990121230129.D5377@rf900.physics.usyd.edu.au> Date: Thu, 21 Jan 1999 23:01:29 +1100 From: David Dawes To: current@FreeBSD.ORG Subject: Promise FastTrack PCI IDE controller Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been playing with a Promise FastTrack RAID (IDE) controller with 3.0-current as of yesterday. Although it is recognised in the PCI bus probe as a "Promise Ultra/33" (it has the same vendor/chip ID as the non-RAID card), the probes in i386/isa/wd.c fail. I added some debugging printfs to the code, and have found that wdreset() is failing. By changing the code to ignore that failure, it gets further, and correctly identifies the attached disks. I can even access the disks sufficiently to read the partition table with fdisk (but with timeouts). I've included some information from a verbose boot, and the debugging printfs I added. I don't have any programming docs for this hardware, and I don't know much about IDE controllers at this level. If anyone has any suggestions of where I might look for the problems, they'd be most welcome. FWIW, the IDE driver in Linux (2.0.35) handles the card OK. FreeBSD 3.0-CURRENT #11: Thu Jan 21 17:28:17 EST 1999 ... ide_pci1: rev 0x01 int a irq 11 on pci0.18.0 ide_pci1: adding drives to controller 2: 4 5 using shared irq11. 6 7 promise_status: port0: 0xeff0, port0_alt: 0xefe4, port1: 0xefa8, port1_alt: 0xefe0 promise_status: dma control blk address: 0xef80, int: 1, irq: 11 drivebits0-1: 4249f4 drivetiming0: pa: 0x4, pb: 0x9, mb: 0x2, mc: 0x2 drivetiming1: pa: 0x4, pb: 0x13, mb: 0x7, mc: 0xf drivebits2-3: 4249f4 drivetiming2: pa: 0x4, pb: 0x9, mb: 0x2, mc: 0x2 drivetiming3: pa: 0x4, pb: 0x13, mb: 0x7, mc: 0xf promise_status: port0: 0xeff0, port0_alt: 0xefe4, port1: 0xefa8, port1_alt: 0xefe0 promise_status: dma control blk address: 0xef80, int: 1, irq: 11 drivebits0-1: 4249f4 drivetiming0: pa: 0x4, pb: 0x9, mb: 0x2, mc: 0x2 drivetiming1: pa: 0x4, pb: 0x13, mb: 0x7, mc: 0xf drivebits2-3: 4249f4 drivetiming2: pa: 0x4, pb: 0x9, mb: 0x2, mc: 0x2 drivetiming3: pa: 0x4, pb: 0x13, mb: 0x7, mc: 0xf ide_pci: busmaster 0 status: 04 from port: 0000ef82 promise_status: port0: 0xeff0, port0_alt: 0xefe4, port1: 0xefa8, port1_alt: 0xefe0 promise_status: dma control blk address: 0xef80, int: 1, irq: 11 drivebits0-1: 4249f4 drivetiming0: pa: 0x4, pb: 0x9, mb: 0x2, mc: 0x2 drivetiming1: pa: 0x4, pb: 0x13, mb: 0x7, mc: 0xf drivebits2-3: 4249f4 drivetiming2: pa: 0x4, pb: 0x9, mb: 0x2, mc: 0x2 drivetiming3: pa: 0x4, pb: 0x13, mb: 0x7, mc: 0xf promise_status: port0: 0xeff0, port0_alt: 0xefe4, port1: 0xefa8, port1_alt: 0xefe0 promise_status: dma control blk address: 0xef80, int: 1, irq: 11 drivebits0-1: 4249f4 drivetiming0: pa: 0x4, pb: 0x9, mb: 0x2, mc: 0x2 drivetiming1: pa: 0x4, pb: 0x13, mb: 0x7, mc: 0xf drivebits2-3: 4249f4 drivetiming2: pa: 0x4, pb: 0x9, mb: 0x2, mc: 0x2 drivetiming3: pa: 0x4, pb: 0x13, mb: 0x7, mc: 0xf ide_pci: busmaster 1 status: 04 from port: 0000ef8a ... wdc2: wdd_candma is set for ide_pci1 wdc2: I/O to 0xeff0 does work wdc2: reset failed wdc2: wd_cyl for master is 63397 (0xf7a5) wdc2: wd_cyl for slave is 63397 (0xf7a5) wdc2: second reset failed wdc2: controller only command OK wdc2 at 0xeff0-0xeff7 flags 0xa0ffa0ff on isa ide_pci: generic_dmainit eff0:0: warning, IDE controller timing not set wd4: wdsetmode() setting transfer mode to 22 wd(2,0): wdgetctlr: gc 45a cyl 16383 trk 16 sec 63 type 3 sz 924 model IBM-DTTA-351680 wdc2: unit 0 (wd4): , DMA, 32-bit, multi-block-16 wd4: 16124MB (33022080 sectors), 32760 cyls, 16 heads, 63 S/T, 512 B/S wd4: ATA INQUIRE valid = 0007, dmamword = 0007, apio = 0003, udma = 0207 wdc3: wdd_candma is set for ide_pci1 wdc3: I/O to 0xefa8 does work wdc3: reset failed wdc3: wd_cyl for master is 63397 (0xf7a5) wdc3: wd_cyl for slave is 63397 (0xf7a5) wdc3: second reset failed wdc3: controller only command OK wdc3 at 0xefa8-0xefaf flags 0xa0ffa0ff on isa ide_pci: generic_dmainit efa8:0: warning, IDE controller timing not set wd6: wdsetmode() setting transfer mode to 22 wd(3,0): wdgetctlr: gc 45a cyl 16383 trk 16 sec 63 type 3 sz 924 model IBM-DTTA-351680 wdc3: unit 0 (wd6): , DMA, 32-bit, multi-block-16 wd6: 16124MB (33022080 sectors), 32760 cyls, 16 heads, 63 S/T, 512 B/S wd6: ATA INQUIRE valid = 0007, dmamword = 0007, apio = 0003, udma = 0207 at this point, run 'fdisk wd4' wd(2,0): wdsetctlr: C 32760 H 16 S 63 wd4: interrupt timeout (status 50 error 0) wd4: wdtimeout() DMA status 1 wd4: wdunwedge failed (status 50 error 0) wd4s1: type 0x6, start 63, end = 96389, size 96327 : OK wd(2,0): wdsetctlr: C 32760 H 16 S 63 wd4: interrupt timeout (status 50 error 0) wd4: wdtimeout() DMA status 1 wd4: wdunwedge failed (status 50 error 0) wd4: interrupt timeout (status 50 error 0) wd4: wdtimeout() DMA status 1 wd4: wdunwedge failed (status 50 error 0) at this point, run 'fdisk wd6' wd(3,0): wdsetctlr: C 32760 H 16 S 63 wd6: DMA failure, DMA status 0 wd6s1: type 0x6, start 63, end = 96389, size 96327 : OK wd(3,0): wdsetctlr: C 32760 H 16 S 63 wd6: DMA failure, DMA status 0 wd6: interrupt timeout (status 50 error 0) wd6: wdtimeout() DMA status 1 wd6: wdunwedge failed (status 58 error 0) David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 04:21:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA28074 for freebsd-current-outgoing; Thu, 21 Jan 1999 04:21:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA28064 for ; Thu, 21 Jan 1999 04:21:32 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id NAA16525; Thu, 21 Jan 1999 13:21:03 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199901211221.NAA16525@freebsd.dk> Subject: Re: Promise FastTrack PCI IDE controller In-Reply-To: <19990121230129.D5377@rf900.physics.usyd.edu.au> from David Dawes at "Jan 21, 1999 11: 1:29 pm" To: dawes@rf900.physics.usyd.edu.au (David Dawes) Date: Thu, 21 Jan 1999 13:21:03 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems David Dawes wrote: > I've been playing with a Promise FastTrack RAID (IDE) controller with > 3.0-current as of yesterday. Although it is recognised in the PCI bus > probe as a "Promise Ultra/33" (it has the same vendor/chip ID as the > non-RAID card), the probes in i386/isa/wd.c fail. I added some debugging > printfs to the code, and have found that wdreset() is failing. By > changing the code to ignore that failure, it gets further, and correctly > identifies the attached disks. I can even access the disks sufficiently > to read the partition table with fdisk (but with timeouts). Hmm, I run one of my systems with the Ultra/33, but with the following patch, without that it wont recognise a lone CDROM/TAPE, but requires a disk to be present. It also includes some other patches, including a fix for SMP system which Julian broke in rev1.183 of wd.c. I also run the card without its BIOS, as that tends to get in the way. I think the FastTrack is just an Ultra/33 with another BIOS chip on it. - Søren Index: wd.c =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/wd.c,v retrieving revision 1.186 diff -u -r1.186 wd.c --- wd.c 1999/01/17 05:46:24 1.186 +++ wd.c 1999/01/19 18:29:23 @@ -350,9 +350,11 @@ goto reset_ok; #endif DELAY(RECOVERYTIME); +/* Allow atapi only channels to work proberly SOS if (wdreset(du) != 0) { goto nodevice; } +*/ reset_ok: /* execute a controller only command */ @@ -1084,10 +1086,11 @@ du = wddrives[dkunit(bp->b_dev)]; /* finish off DMA */ - if (du->dk_flags & (DKFL_DMA|DKFL_USEDMA)) { + if ((du->dk_flags & (DKFL_DMA|DKFL_SINGLE)) == DKFL_DMA) { /* XXX SMP boxes sometimes generate an early intr. Why? */ - if ((wddma[du->dk_interface].wdd_dmastatus(du->dk_dmacookie) & WDDS_INTERRUPT) - != 0) + if ((wddma[du->dk_interface].wdd_dmastatus(du->dk_dmacookie) & + WDDS_INTERRUPT) == 0) + return; dmastat = wddma[du->dk_interface].wdd_dmadone(du->dk_dmacookie); } @@ -1568,6 +1571,7 @@ if (wdwait(du, 0, TIMEOUT) < 0) return (1); if( command == WDCC_FEATURES) { + outb(wdc + wd_sdh, WDSD_IBM | (du->dk_unit << 4) | head); outb(wdc + wd_features, count); if ( count == WDFEA_SETXFER ) outb(wdc + wd_seccnt, sector); @@ -2289,9 +2293,8 @@ { int err = 0; - if ((du->dk_flags & (DKFL_DMA|DKFL_USEDMA)) && du->dk_dmacookie) + if ((du->dk_flags & (DKFL_DMA|DKFL_SINGLE)) == DKFL_DMA) wddma[du->dk_interface].wdd_dmadone(du->dk_dmacookie); - (void)wdwait(du, 0, TIMEOUT); outb(du->dk_altport, WDCTL_IDS | WDCTL_RST); DELAY(10 * 1000); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 04:49:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA01409 for freebsd-current-outgoing; Thu, 21 Jan 1999 04:49:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA01401 for ; Thu, 21 Jan 1999 04:49:13 -0800 (PST) (envelope-from dawes@rf900.physics.usyd.edu.au) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.9.1a/8.9.1) id XAA11857; Thu, 21 Jan 1999 23:46:51 +1100 (EST) Message-ID: <19990121234651.F5377@rf900.physics.usyd.edu.au> Date: Thu, 21 Jan 1999 23:46:51 +1100 From: David Dawes To: =?iso-8859-1?Q?S=F8ren_Schmidt?= Cc: current@FreeBSD.ORG Subject: Re: Promise FastTrack PCI IDE controller References: <19990121230129.D5377@rf900.physics.usyd.edu.au> <199901211221.NAA16525@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.93.2i In-Reply-To: =?iso-8859-1?Q?=3C199901211221=2ENAA16525=40freebsd=2Edk=3E=3B_from_S=F8?= =?iso-8859-1?Q?ren_Schmidt_on_Thu=2C_Jan_21=2C_1999_at_01:21:03PM_+0100?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 21, 1999 at 01:21:03PM +0100, Søren Schmidt wrote: >It seems David Dawes wrote: >> I've been playing with a Promise FastTrack RAID (IDE) controller with >> 3.0-current as of yesterday. Although it is recognised in the PCI bus >> probe as a "Promise Ultra/33" (it has the same vendor/chip ID as the >> non-RAID card), the probes in i386/isa/wd.c fail. I added some debugging >> printfs to the code, and have found that wdreset() is failing. By >> changing the code to ignore that failure, it gets further, and correctly >> identifies the attached disks. I can even access the disks sufficiently >> to read the partition table with fdisk (but with timeouts). > >Hmm, I run one of my systems with the Ultra/33, but with the following >patch, without that it wont recognise a lone CDROM/TAPE, but requires >a disk to be present. It also includes some other patches, including >a fix for SMP system which Julian broke in rev1.183 of wd.c. That didn't improve things, but with the patch I got lots of messages like the following (for a disk attached to the onboard PIIX4): wd1: DMA failure, DMA status 0 (The box isn't SMP.) >I also run the card without its BIOS, as that tends to get in the way. >I think the FastTrack is just an Ultra/33 with another BIOS chip on it. I'll try pulling the BIOS tomorrow. We didn't get this card for it's RAID features anyway. Thanks. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 05:06:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA03148 for freebsd-current-outgoing; Thu, 21 Jan 1999 05:06:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA03129 for ; Thu, 21 Jan 1999 05:06:41 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id OAA16593; Thu, 21 Jan 1999 14:06:22 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199901211306.OAA16593@freebsd.dk> Subject: Re: Promise FastTrack PCI IDE controller In-Reply-To: <19990121234651.F5377@rf900.physics.usyd.edu.au> from David Dawes at "Jan 21, 1999 11:46:51 pm" To: dawes@rf900.physics.usyd.edu.au (David Dawes) Date: Thu, 21 Jan 1999 14:06:22 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems David Dawes wrote: > > That didn't improve things, but with the patch I got lots of messages > like the following (for a disk attached to the onboard PIIX4): > > wd1: DMA failure, DMA status 0 > > (The box isn't SMP.) Hmm, and it is an uptodate -current system ?? Just use this part then: Index: wd.c =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/wd.c,v retrieving revision 1.186 diff -u -r1.186 wd.c --- wd.c 1999/01/17 05:46:24 1.186 +++ wd.c 1999/01/19 18:29:23 @@ -350,9 +350,11 @@ goto reset_ok; #endif DELAY(RECOVERYTIME); +/* Allow atapi only channels to work proberly SOS if (wdreset(du) != 0) { goto nodevice; } +*/ reset_ok: /* execute a controller only command */ > >I also run the card without its BIOS, as that tends to get in the way. > >I think the FastTrack is just an Ultra/33 with another BIOS chip on it. > > I'll try pulling the BIOS tomorrow. We didn't get this card for it's > RAID features anyway. That helped me in a lot if situations, but performance wont be as good as we seem not to initialize the chip(s)... I have the specsheets somewhere if anybody is interested... - Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 05:30:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA04777 for freebsd-current-outgoing; Thu, 21 Jan 1999 05:30:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail2.leirianet.pt (vortex.leirianet.pt [195.23.92.20]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA04768 for ; Thu, 21 Jan 1999 05:30:08 -0800 (PST) (envelope-from mfer@leirianet.pt) Received: (qmail 22743 invoked from network); 21 Jan 1999 13:29:56 -0000 Received: from unknown (HELO OSIRIS) (195.61.93.61) by mail2.leirianet.pt with SMTP; 21 Jan 1999 13:29:56 -0000 From: mfer@leirianet.pt (M Ferreira) To: freebsd-current@FreeBSD.ORG Subject: Spontaneous system freezes Date: Thu, 21 Jan 1999 13:29:05 GMT Reply-To: mfer@leirianet.pt (M Ferreira) Message-ID: <36ad2732.12001256@mail2.leirianet.pt> X-Mailer: Forte Agent 1.5/32.451 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id FAA04773 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to get 3.0-RELEASE to run as stable as possible on a PII with aic7895 onboard scsi controller. my dmesg output is: Timecounter "i8254" frequency 1193182 Hz cost 3126 ns Timecounter "TSC" frequency 349069134 Hz cost 140 ns CPU: Pentium II (quarter-micron) (349.07-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping=2 Features=0x183fbff> real memory = 134217728 (131072K bytes) avail memory = 127844352 (124848K bytes) Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x02 on pci0.1.0 chip2: rev 0x02 on pci0.7.0 chip3: rev 0x01 int d irq 11 on pci0.7.2 chip4: rev 0x02 on pci0.7.3 vga0: rev 0x3a int a irq 255 on pci0.8.0 de0: rev 0x20 int a irq 10 on pci0.10.0 de0: 21140A [10-100Mb/s] pass 2.0 de0: address 00:48:54:00:07:b1 ahc0: rev 0x04 int a irq 5 on pci0.12.0 ahc0: aic7895 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: rev 0x04 int b irq 5 on pci0.12.1 ahc1: Using left over BIOS settings ahc1: aic7895 Wide Channel B, SCSI Id=7, 16/255 SCBs Probing for devices on PCI bus 1: Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in npx0 on motherboard npx0: INT 16 interface Waiting 15 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 5 lun 0 sa0: Removable Sequential Access SCSI2 device sa0: 3.300MB/s transfers da4 at ahc1 bus 0 target 2 lun 0 da4: Fixed Direct Access SCSI2 device da4: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da4: 4340MB (8888924 512 byte sectors: 64H 32S/T 4340C) da5 at ahc1 bus 0 target 3 lun 0 da5: Fixed Direct Access SCSI2 device da5: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da5: 4340MB (8888924 512 byte sectors: 64H 32S/T 4340C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI2 device da1: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) changing root device to da0s1a I'm having spontaneous freezes whenever I compile anything, be it a kernel build or a port install. Beeing more specific, it's a total system freeze. Nothing on the console (have DDB in the kernel), no response to pings, and total keyboard freeze. Can anyone shed any light on this? tia M Ferreira To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 06:26:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA09784 for freebsd-current-outgoing; Thu, 21 Jan 1999 06:26:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from friley-184-92.res.iastate.edu (friley-184-92.res.iastate.edu [129.186.184.92]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA09779 for ; Thu, 21 Jan 1999 06:26:04 -0800 (PST) (envelope-from mystify@friley-184-92.res.iastate.edu) Received: from friley-184-92.res.iastate.edu (localhost.res.iastate.edu [127.0.0.1]) by friley-184-92.res.iastate.edu (8.9.2/8.9.1) with ESMTP id IAA33202 for ; Thu, 21 Jan 1999 08:25:25 -0600 (CST) (envelope-from mystify@friley-184-92.res.iastate.edu) Message-Id: <199901211425.IAA33202@friley-184-92.res.iastate.edu> To: freebsd-current@FreeBSD.ORG Subject: Changes to pam_kerberosIV broke ftpd Date: Thu, 21 Jan 1999 08:25:24 -0600 From: Patrick Hartling Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It appears that revision 1.9 of lib/libpam/modules/pam_kerberosIV/klogin.c and revision 1.3 of lib/libpam/modules/pam_kerberosIV/pam_kerberosIV.c broke ftpd when compiling with MAKE_KERBEROS defined. The errors I get when compiling with 4.0-current sources (and presumably 3.0-stable though I haven't tried compiling that yet) cvsup'd last night at about 11:00 pm CST are: ===> libexec/ftpd [...] cc -O -pipe -DSETPROCTITLE -DSKEY -DLOGIN_CAP -DVIRTUAL_HOSTING -Wall -I/usr/src/libexec/ftpd/../../contrib-crypto/telnet -DKERBEROS -I/usr/obj/usr/src/tmp/usr/include -o ftpd ftpd.o ftpcmd.o logwtmp.o popen.o skey-stuff.o klogin.o -lskey -lmd -lcrypt -lutil -lkrb -ldes ftpd.o: In function `pass': ftpd.o(.text+0x11c9): undefined reference to `klogin' klogin.o: In function `_pam_klogin': klogin.o(.text+0x3e): undefined reference to `_pam_noticketsdontcomplain' klogin.o(.text+0xd2): undefined reference to `_pam_krbtkfile_env' klogin.o(.text+0x1a3): undefined reference to `_pam_notickets' This could be the case for other Kerberized programs, but this is as far as my 'make world' got. -Patrick Patrick L. Hartling | Research Assistant, ICEMT mystify@friley-184-92.res.iastate.edu | Carver Lab - 0095E Black Engineering http://www.public.iastate.edu/~oz/ | http://www.icemt.iastate.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 06:37:34 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA11093 for freebsd-current-outgoing; Thu, 21 Jan 1999 06:37:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oreo.adsu.bellsouth.com (oreo.adsu.bellsouth.com [205.152.173.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA11088 for ; Thu, 21 Jan 1999 06:37:30 -0800 (PST) (envelope-from ck@oreo.adsu.bellsouth.com) Received: (from ck@localhost) by oreo.adsu.bellsouth.com (8.9.1/8.9.1) id JAA31266; Thu, 21 Jan 1999 09:36:32 -0500 (EST) (envelope-from ck) Date: Thu, 21 Jan 1999 09:36:31 -0500 From: Christian Kuhtz To: Doug Rabson Cc: Mike Smith , Christian Kuhtz , "David O'Brien" , current@FreeBSD.ORG Subject: Re: KLD naming Message-ID: <19990121093631.A31170@oreo.adsu.bellsouth.com> References: <199901210556.VAA06281@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Doug Rabson on Thu, Jan 21, 1999 at 09:34:28AM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 21, 1999 at 09:34:28AM +0000, Doug Rabson wrote: > On Wed, 20 Jan 1999, Mike Smith wrote: > > > I guess it depends on how fancy we want to get. Here are some examples > > that I've been rolling around; some are fanciful, some practical) > > > > dev_ generic device (eg. dev_sio) > > bus_ bus support (eg. bus_pci) > > netif_ network interface (eg. netif_ed) > > netproto_ network protocol (eg. netproto_arp) > > netdomain_ network domain (eg. netdomain_ip) How is the difference between netproto & netdomain defined? I'm running into a case where I can easily turn the stack upside down (say, running frame-relay over IP over MPLS in an IP tunnel over PPP -- that's almost working actually). It sounds like netdomain is somehow higher up in the stack than netproto.. even though they're all protocols. Comments? Cheers, Chris -- "Logic is a little bird, sitting in a tree; that smells *awful*." -- /usr/bin/fortune [Disclaimer: I speak for myself and my views are my own and not in any way to be construed as the views of BellSouth Corporation. ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 07:14:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA14052 for freebsd-current-outgoing; Thu, 21 Jan 1999 07:14:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA14045 for ; Thu, 21 Jan 1999 07:14:57 -0800 (PST) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.1/8.9.1) id HAA07738 for freebsd-current@freebsd.org; Thu, 21 Jan 1999 07:14:20 -0800 (PST) (envelope-from dhw) Date: Thu, 21 Jan 1999 07:14:20 -0800 (PST) From: David Wolfskill Message-Id: <199901211514.HAA07738@pau-amma.whistle.com> To: freebsd-current@FreeBSD.ORG Subject: Re: make release produces unbootable boot floppies, no boot loader, no /kernel In-Reply-To: <199901210554.AAA51853@bb01f39.unx.sas.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From: "John W. DeBoskey" >Date: Thu, 21 Jan 1999 00:54:36 -0500 (EST) > If you really want to make things easier for the beginner, why >not provide a DOS boot program. Then you wouldn't even have to >worry about boot floppies. Tell new folks to copy the boot program >to the DOS partition and run it from DOS. Case closed. No boot >floppy required. I can imagine half a dozen ways to make this work. Although I'll cheerfully admit that I'm probably in the minority in this respect, such an approach would do me not one whit of good, since, given a desired objective, I have no idea how to make MS-DOS accomplish it. (I'm coming at FreeBSD with no background in PCs at all, about 12+ years working with UNIX, about 12 years as an IBM mainframe (MVS) systems programmer, and some years before that of various other types of systems. In my (somewhat limited) experience, when I've tried to use MS-DOS for anything, more than half the time either the application or the machine would hang or crash; thus, I'd be hard-pressed to advocate reliance upon that mechanism for anything of perceived importance.) Cheers, david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 07:26:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA15548 for freebsd-current-outgoing; Thu, 21 Jan 1999 07:26:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA15543 for ; Thu, 21 Jan 1999 07:26:46 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (crossd@o2.cs.rpi.edu [128.113.96.156]) by cs.rpi.edu (8.9.1/8.9.1) with ESMTP id KAA27834; Thu, 21 Jan 1999 10:24:55 -0500 (EST) Message-Id: <199901211524.KAA27834@cs.rpi.edu> To: Chris Csanady cc: Mike Nguyen , current@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: /etc/nsswitch.conf In-Reply-To: Message from Chris Csanady of "Wed, 20 Jan 1999 15:48:37 CST." <199901202148.PAA61128@friley-185-114.res.iastate.edu> Date: Thu, 21 Jan 1999 10:24:54 -0500 From: "David E. Cross" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, indeed, I have looked at nsd in Irix 6.5 and I like it. What Irix does well, Irix does very well (save a couple of PRs I have filed with SGI of course ;). -- David Cross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 07:54:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA19028 for freebsd-current-outgoing; Thu, 21 Jan 1999 07:54:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA19022 for ; Thu, 21 Jan 1999 07:54:49 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (crossd@o2.cs.rpi.edu [128.113.96.156]) by cs.rpi.edu (8.9.1/8.9.1) with ESMTP id KAA28454 for ; Thu, 21 Jan 1999 10:54:38 -0500 (EST) Message-Id: <199901211554.KAA28454@cs.rpi.edu> To: current@FreeBSD.ORG Subject: mountd Date: Thu, 21 Jan 1999 10:54:36 -0500 From: "David E. Cross" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I posted this awhile ago to -questions, but never received a reply. We have a number of FreeBSD NFS servers here. Occasionally we need to change the exports list on the servers and send mountd a SIGHUP. This leads to a condition that in many ways is much worse than a server reboot. What happens is for the duration of mountd reading the exports file it denies all NFS requests. This has a number of bad effects; 1) any user home and system directories become unavailable, with the error 'permission denied' 2) (and this is far worse), any process with a mapped .text segment off of the NFS server, should it branch to code not in the cache gets immediately killed. This include user processes that are running from home directories, and system processes (such as ssh). If we were to reboot the machine it would just hang those connections until the machine came back, without killing anyone. Is there a solution to this problem? I know that none of HP-UX, IRIX, or Solaris have this problem. -- David Cross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 08:03:01 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA19995 for freebsd-current-outgoing; Thu, 21 Jan 1999 08:03:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA19989 for ; Thu, 21 Jan 1999 08:02:59 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:NMWQQT47V7BZqSDx2lJQpbQhPJ1hKLE5@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id BAA10637 for ; Fri, 22 Jan 1999 01:02:48 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id BAA24511; Fri, 22 Jan 1999 01:05:23 +0900 (JST) Message-Id: <199901211605.BAA24511@zodiac.mech.utsunomiya-u.ac.jp> To: current@FreeBSD.ORG cc: yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: keymaps Date: Fri, 22 Jan 1999 01:05:22 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently looked at keymaps in /usr/share/syscons/keymaps and found many minor errors. In addition to that, there is so much inconsistency among existing keymaps. True that national keyboards have different layout of regular keys (alphanumeric keys and symbol keys). But, it is absurd that functions keys and special keys are handled in so many different ways. The syscons keymap can assign special functions to key strokes, such as `suspend', `next virtual screen'. However, some keymaps don't have these special functions assigned to any key strokes. The other keymaps may have them but assign them differently. There is no standard here. So, I would propose the following key assignment to be the standard from now on. I compiled this list based on existing keymaps and recent input from a contributer (thanks, J M Alcaide!) If this assignment is not desirable for some keymaps, such as Russian and Dvorak maps which are rather unique, they may be made exceptions. But, unless there is a good reason to make other exceptions, I will modify the other national keymaps to adapt these key assignments. Any comments? I am open to suggestions. Kazu * 101/102/104 Enhanced Keyboard support Key Code Key Stroke Function ----------------------------------------------------------------------------- 1 Ctrl-Alt-Esc Enter DDB (debug). 57 Ctrl-Alt-Space Suspend (susp). 70 ScrollLock Backscroll (slock). 84 Alt-SysRq(PrintScreen) - (nop) 92 PrintScreen Switch to the next vty (next). 104 Pause Start screen saver (saver). 104 Alt-Pause Suspend (susp). 105 Left Windows fkey62 106 Right Windows fkey63 107 Menu fkey64 108 Ctrl-Break(Pause) Enter DDB (debug). The separate SysRq key doesn't exist on the enhanced keyboard. It is combined with the PrintScreen key. The SysRq code is generated when the Alt and the PrintScreen keys are pressed together. The separate Break key doesn't exist on the enhanced keyboard. It is combined with the Pause key. The Break code is generated when the Ctrl and the Pause keys are pressed together. The above assignments for the keycodes 1, 57, 70, 84 and 92 are compatible with many, if not all, existing keymaps. The assignments for 104 and 108 are new. Many keymaps lacks entries for 105 through 107. * 84 Keyboard support Key Code Key Stroke Function ----------------------------------------------------------------------------- 1 Ctrl-Alt-Esc Enter DDB (debug). 57 Ctrl-Alt-Space Suspend (susp). 70 ScrollLock Backscroll (slock). 84 SysRq - (nop) 92 Shift-PrintScreen(*) Switch to the next vty (next). 104 Ctrl-Pause(NumLock) Start screen saver (saver). 104 Ctrl-Alt-Pause(NumLock) Suspend (susp). 108 Ctrl-Break(ScrollLock) Enter DDB (debug). The separate PrintScreen key doesn't exist on the 84 keyboard. It is combined with the numpad * key. The PrintScreen code is generated when the Shift and the numpad * keys are pressed together. The separate Pause key doesn't exist on the 84 keyboard. It is combined with the NumLock key. The Pause code is generated when the Ctrl and the NumlLock keys are pressed together. The separate Break key doesn't exist on the 84 keyboard. It is combined with the ScrollLock key. The Break code is generated when the Ctrl and the ScrollLock keys are pressed together. * Proposed keymap Combining the support for the 84 keyboard and the enhanced keyboard described above, we will get the following keymap entries. alt ctrl alt alt ctrl code base shift ctrl shift alt shift ctrl shift ----------------------------------------------------- 1 esc esc esc esc esc esc debug esc 57 ' ' ' ' null ' ' ' ' ' ' susp ' ' 70 slock slock slock slock slock slock slock slock 84 nop nop nop nop nop nop nop nop 92 next next nop nop nop nop nop nop 104 saver nop saver nop susp nop susp nop 105 nop nop nop nop nop nop nop nop 106 nop nop nop nop nop nop nop nop 107 nop nop nop nop nop nop nop nop 108 nop nop debug nop nop nop nop nop <> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 08:13:34 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA21106 for freebsd-current-outgoing; Thu, 21 Jan 1999 08:13:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shale.csir.co.za (shale.csir.co.za [146.64.46.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA21071 for ; Thu, 21 Jan 1999 08:13:29 -0800 (PST) (envelope-from reg@shale.csir.co.za) Received: (from reg@localhost) by shale.csir.co.za (8.9.2/8.9.2) id SAA30759; Thu, 21 Jan 1999 18:12:31 +0200 (SAT) (envelope-from reg) Date: Thu, 21 Jan 1999 18:12:29 +0200 From: Jeremy Lea To: "Richard Seaman, Jr." Cc: freebsd-current@FreeBSD.ORG Subject: Using LinuxThreads Message-ID: <19990121181228.A98581@shale.csir.co.za> References: <19990118182717.A15566@top.worldcontrol.com> <19990119024539.A88383@top.worldcontrol.com> <19990119140613.B826@shale.csir.co.za> <19990119091151.F600@tar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990119091151.F600@tar.com>; from Richard Seaman, Jr. on Tue, Jan 19, 1999 at 09:11:51AM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Tue, Jan 19, 1999 at 09:11:51AM -0600, Richard Seaman, Jr. wrote: > Actually, the new version, in FreeBSD "ports" form, doesn't require > -DLINUXTHREADS anymore, but it does require -I/usr/local/include to > pick up the right header, since it installs a pthread.h into > /usr/local/include. This conflicts with the pthread.h in /usr/include. This is nagging at me. Having two headers of the same name, but importantly different content is asking for touble. There needs to be a way to ensure that only one or the other is picked up. The best way I can think of is to only include the contents of the user thread pthread.h if _THREAD_SAFE is defined (to force people to use the right defines...) and the contents of kernel thread pthread.h if _REENTRANT (and not _THREAD_SAFE) is defined. This has the added bonus of meaning that most linux apps wont have to be patched. To many applications have configure scripts which might find /usr/local/lib/libpthread, but not /usr/local/include/pthread.h, or find /usr/lib/libc_r and find /usr/local/include/pthread.h. Can gcc be made to define _THREAD_SAFE automatically if -pthread is given? And _REENTRANT if -kthread is given? What are the plans for the import of the LinuxThreads stuff into the src tree? Or is it going to remain a port, and the source tree position be reserved for a future kernel threads implementation? My mind says it is to closely tied to the OS to be a port. And when are COMPAT_LINUX_THREADS and VM_STACK going away? Regards, -Jeremy -- | "In this world of temptation, I will stand for what is right. --+-- With a heart of salvation, I will hold up the light. | If I live or if I die, if I laugh or if I cry, | in this world of temptation, I will stand." -Pam Thum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 09:44:57 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02563 for freebsd-current-outgoing; Thu, 21 Jan 1999 09:44:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA02558 for ; Thu, 21 Jan 1999 09:44:52 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id JAA17852; Thu, 21 Jan 1999 09:39:28 -0800 (PST) Received: from s204m82.isp.whistle.com(207.76.204.82) via SMTP by alpo.whistle.com, id smtpdS17842; Thu Jan 21 17:39:20 1999 Date: Thu, 21 Jan 1999 09:39:14 -0800 (PST) From: Julian Elischer X-Sender: julian@s204m82.isp.whistle.com To: paul@originative.co.uk cc: mike@smith.net.au, ck@adsu.bellsouth.com, obrien@NUXI.com, current@FreeBSD.ORG Subject: RE: KLD naming In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 21 Jan 1999 paul@originative.co.uk wrote: > > Why not have a third party identifier on the front, e.g. > > whistle_ng_rfc1490 > > You can determine your own naming scheme then and if we make this > standard then it will ensure that third party supplied modules don't > result in name space conflicts. It's perfectly feasible in the future > that different companies might produce competing modules for subsystems, > sound for example, so we might as well deal with this possibility now. > Makes it easier to identify the source of the modules as well. Perhaps > we should adopt a FreeBSD prefix on core modules so you can see from ls > what's part of the OS and what's been added in from elsewhere. > > Although I'm in favour of this naming scheme over directories you can > reach the point where the names are holding too much metainformation > that really should be directory structure. There wouldn't be need for > directories at all if you put the structure in the filename :-) Well whistle is giving htis away so we don'tthink it should be whistle_xxx any more than the kernel should be UCB/... It occur to me that eventually every single device driver will be a KLD an also a lot of other things besides... there are going to be a LOT of files in /modules.... > > Paul. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 09:53:42 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA03746 for freebsd-current-outgoing; Thu, 21 Jan 1999 09:53:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA03498 for ; Thu, 21 Jan 1999 09:51:29 -0800 (PST) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (tiburon [158.227.6.111]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id SAA11296; Thu, 21 Jan 1999 18:48:57 +0100 (MET) Message-ID: <36A76889.93DE88B4@we.lc.ehu.es> Date: Thu, 21 Jan 1999 18:48:57 +0100 From: "José Mª Alcaide" Organization: Universidad del País Vasco - Dept. de Electricidad y Electrónica X-Mailer: Mozilla 4.07 [en] (X11; U; FreeBSD 2.2.8-RELEASE i386) MIME-Version: 1.0 To: Kazutaka YOKOTA CC: current@FreeBSD.ORG Subject: Re: keymaps References: <199901211605.BAA24511@zodiac.mech.utsunomiya-u.ac.jp> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kazutaka YOKOTA wrote: > > * 101/102/104 Enhanced Keyboard support > > Key Code Key Stroke Function > ----------------------------------------------------------------------------- > 1 Ctrl-Alt-Esc Enter DDB (debug). > 57 Ctrl-Alt-Space Suspend (susp). > 70 ScrollLock Backscroll (slock). > 84 Alt-SysRq(PrintScreen) - (nop) > 92 PrintScreen Switch to the next vty (next). > 104 Pause Start screen saver (saver). > 104 Alt-Pause Suspend (susp). > 105 Left Windows fkey62 > 106 Right Windows fkey63 > 107 Menu fkey64 > 108 Ctrl-Break(Pause) Enter DDB (debug). I am afraid of being myself the cause of a keymap revolution!! 8-) As I said in a previous message to freebsd-bugs, I think that mapping the saver to the "base" Pause key could annoy people accustomed to pressing this key to stop the screen output. I would map the [very useful] saver function to Shift-Pause (Shift-Ctrl-NumLock on the 84 KB ?) or, perhaps better, Break (Ctrl-Pause on the 104 KB, Ctrl-ScrollLock on the 84 KB). Another suggestion: I would move the debug function from Break to SysReq (Alt-PrtScr on the 104 KB); I think that associating SysReq to the debugger is intuitive. Then, the now free Break key could be used for the saver function (as suggested above) or, perhaps, the DOS-like "etx" (Ctrl-C) character (I'm supposing the usual stty intr ^C). > * 84 Keyboard support > > Key Code Key Stroke Function > ----------------------------------------------------------------------------- > 1 Ctrl-Alt-Esc Enter DDB (debug). > 57 Ctrl-Alt-Space Suspend (susp). > 70 ScrollLock Backscroll (slock). > 84 SysRq - (nop) > 92 Shift-PrintScreen(*) Switch to the next vty (next). > 104 Ctrl-Pause(NumLock) Start screen saver (saver). > 104 Ctrl-Alt-Pause(NumLock) Suspend (susp). > 108 Ctrl-Break(ScrollLock) Enter DDB (debug). > > The separate PrintScreen key doesn't exist on the 84 keyboard. It is > combined with the numpad * key. The PrintScreen code is generated > when the Shift and the numpad * keys are pressed together. > > The separate Pause key doesn't exist on the 84 keyboard. It is > combined with the NumLock key. The Pause code is generated when the > Ctrl and the NumlLock keys are pressed together. > > The separate Break key doesn't exist on the 84 keyboard. It is > combined with the ScrollLock key. The Break code is generated when > the Ctrl and the ScrollLock keys are pressed together. > > * Proposed keymap > > Combining the support for the 84 keyboard and the enhanced keyboard > described above, we will get the following keymap entries. > alt > ctrl alt alt ctrl > code base shift ctrl shift alt shift ctrl shift > ----------------------------------------------------- > 1 esc esc esc esc esc esc debug esc > 57 ' ' ' ' null ' ' ' ' ' ' susp ' ' > 70 slock slock slock slock slock slock slock slock > 84 nop nop nop nop nop nop nop nop > 92 next next nop nop nop nop nop nop > 104 saver nop saver nop susp nop susp nop > 105 nop nop nop nop nop nop nop nop > 106 nop nop nop nop nop nop nop nop > 107 nop nop nop nop nop nop nop nop > 108 nop nop debug nop nop nop nop nop > There is something I do not understand. Is it possible to generate the Ctrl-Key104 and Alt-Ctrl-Key104 combinations? These are not available on the 104 KB (Ctrl-Pause ==> Break) and, on the 84 KB, Ctrl-NumLock yields the "base" Pause (or Ctrl-Pause?)... Another question: the numpad '*' key (keycode 55) has this mapping in most keymaps: 055 '*' '*' nscr nscr '*' '*' nscr nscr You told me that the nscr function was needed for the 84 KBD, but now you are saying that, on that KB, the PrtScrn code (92) is generated by Shift-Numpad*. Now I cannot understand the utility of that mapping for the keycode 055... --JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | http://www.we.lc.ehu.es/~jose Dpto. de Electricidad y Electrónica | Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139 ----------------------------------------------------------------------- "Go ahead... make my day." - H. Callahan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 09:55:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA03999 for freebsd-current-outgoing; Thu, 21 Jan 1999 09:55:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA03971 for ; Thu, 21 Jan 1999 09:54:57 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id JAA18067; Thu, 21 Jan 1999 09:45:04 -0800 (PST) Received: from s204m82.isp.whistle.com(207.76.204.82) via SMTP by alpo.whistle.com, id smtpdb18043; Thu Jan 21 17:44:50 1999 Date: Thu, 21 Jan 1999 09:44:38 -0800 (PST) From: Julian Elischer X-Sender: julian@s204m82.isp.whistle.com To: Christian Kuhtz cc: Doug Rabson , Mike Smith , "David O'Brien" , current@FreeBSD.ORG Subject: Re: KLD naming In-Reply-To: <19990121093631.A31170@oreo.adsu.bellsouth.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 21 Jan 1999, Christian Kuhtz wrote: > On Thu, Jan 21, 1999 at 09:34:28AM +0000, Doug Rabson wrote: > > On Wed, 20 Jan 1999, Mike Smith wrote: > > > > > I guess it depends on how fancy we want to get. Here are some examples > > > that I've been rolling around; some are fanciful, some practical) > > > > > > dev_ generic device (eg. dev_sio) > > > bus_ bus support (eg. bus_pci) > > > netif_ network interface (eg. netif_ed) > > > netproto_ network protocol (eg. netproto_arp) > > > netdomain_ network domain (eg. netdomain_ip) > > How is the difference between netproto & netdomain defined? I'm running into > a case where I can easily turn the stack upside down (say, running frame-relay > over IP over MPLS in an IP tunnel over PPP -- that's almost working actually). > > It sounds like netdomain is somehow higher up in the stack than netproto.. > even though they're all protocols. > > Comments? > > Cheers, > Chris > > -- > "Logic is a little bird, sitting in a tree; that smells *awful*." > -- /usr/bin/fortune > > [Disclaimer: I speak for myself and my views are my own and not in any way to > be construed as the views of BellSouth Corporation. ] > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 10:00:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA04846 for freebsd-current-outgoing; Thu, 21 Jan 1999 10:00:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from octopus.originative.co.uk (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA04777 for ; Thu, 21 Jan 1999 10:00:44 -0800 (PST) (envelope-from paul@originative.co.uk) From: paul@originative.co.uk Received: by OCTOPUS with Internet Mail Service (5.5.1960.3) id ; Thu, 21 Jan 1999 17:59:08 -0000 Message-ID: To: julian@whistle.com, paul@originative.co.uk Cc: mike@smith.net.au, ck@adsu.bellsouth.com, obrien@NUXI.com, current@FreeBSD.ORG Subject: RE: KLD naming Date: Thu, 21 Jan 1999 17:59:05 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Julian Elischer [mailto:julian@whistle.com] > Sent: Thursday, January 21, 1999 5:39 PM > To: paul@originative.co.uk > Cc: mike@smith.net.au; ck@adsu.bellsouth.com; obrien@NUXI.com; > current@FreeBSD.ORG > Subject: RE: KLD naming > > Well whistle is giving htis away so we don'tthink it should > be whistle_xxx > any more than the kernel should be UCB/... > It occur to me that eventually every single device driver > will be a KLD > an also a lot of other things besides... > there are going to be a LOT of files in /modules.... Ok, in this case maybe it doesn't apply but in general we should determine what the guidelines for third party module developers should be to avoid namespace clashes. I though a FreeBSD prefix for modules shipped as part of FreeBSD would be useful to list all those modules that are *not* third party supplied when you've got a directory full of the things. Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 10:10:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA06386 for freebsd-current-outgoing; Thu, 21 Jan 1999 10:10:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from server.noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA06275 for ; Thu, 21 Jan 1999 10:10:05 -0800 (PST) (envelope-from geoffb@gti.noc.demon.net) Received: by server.noc.demon.net; id SAA26327; Thu, 21 Jan 1999 18:09:55 GMT Received: from gti.noc.demon.net(195.11.55.101) by inside.noc.demon.net via smap (3.2) id xma026322; Thu, 21 Jan 99 18:09:43 GMT Received: (from geoffb@localhost) by gti.noc.demon.net (8.8.8/8.8.8) id SAA24949 for freebsd-current@freebsd.org; Thu, 21 Jan 1999 18:09:41 GMT Message-ID: <19990121180941.G19395@gti.noc.demon.net> Date: Thu, 21 Jan 1999 18:09:41 +0000 From: Geoff Buckingham To: freebsd-current@FreeBSD.ORG Subject: KVA/KVM shortages Reply-To: Geoff Buckingham Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Organisation: Demon Internet Ltd Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On tuesday I crashed a machine after it ran out of kvm. (dual PII 400 with 768MB RAM) poking about in the code adding: options "VM_KMEM_SIZE=(24*1024*1024)" options "VM_KMEM_SIZE_MAX=(128*1024*1024)" seems like a good way foward. Is it? -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 10:16:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA07218 for freebsd-current-outgoing; Thu, 21 Jan 1999 10:16:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA07213 for ; Thu, 21 Jan 1999 10:16:26 -0800 (PST) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.9.1/8.8.7) with ESMTP id NAA07051 for ; Thu, 21 Jan 1999 13:16:18 -0500 (EST) (envelope-from gjp@gjp.erols.com) To: current@FreeBSD.ORG From: "Gary Palmer" Subject: More make release woes Date: Thu, 21 Jan 1999 13:16:17 -0500 Message-ID: <7047.916942577@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Looks like the Alpha AXP boot floppy has bitten the dust also: Making the regular boot floppy. Compressing doc files... disklabel: ioctl DIOCWLABEL: Operation not supported by device Warning: Block size restricts cylinders per group to 4. Warning: 2880 sector(s) in last cylinder unallocated /dev/rvn0c: 2880 sectors in 1 cylinders of 1 tracks, 5760 sectors 1.4MB in 1 cyl groups (4 c/g, 11.25MB/g, 192 i/g) super-block backups (for fsck -b #) at: 32, cpio: write error: No space left on device *** Error code 1 (ignored) *** Error code 1 Stop. *** Error code 1 Stop. Sigh. Oh well. I was hoping to get a SNAP out with all the changes Matt did. Guess not. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 10:30:50 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA09259 for freebsd-current-outgoing; Thu, 21 Jan 1999 10:30:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dns.MexComUSA.NET (cm4094.cableco-op.com [208.138.40.94]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA09254 for ; Thu, 21 Jan 1999 10:30:48 -0800 (PST) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (cm4094.cableco-op.com [208.138.40.94]) by dns.MexComUSA.NET (8.9.2/8.9.1) with ESMTP id KAA70507 for ; Thu, 21 Jan 1999 10:30:39 -0800 (PST) (envelope-from eculp@MexComUSA.net) Message-ID: <36A7724F.E283588A@MexComUSA.net> Date: Thu, 21 Jan 1999 10:30:39 -0800 From: Edwin Culp Organization: Mexico Communicates, S.C. X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: SCSI errors from IBM Netfinity 3500 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm getting a lot of these SCSI disk errors from Current as of Sunday with the onboard Adaptec Controler with an IBM netfinity 3500. Can someone tell me if I should worry and/or what they mean? Thanks, ed (da0:ahc0:0:0:0): parity error during Data-In phase. SEQADDR == 0x10e SCSIRATE == 0x88 (da0:ahc0:0:0:0): parity error during Data-In phase. SEQADDR == 0x4f SCSIRATE == 0x88 (da0:ahc0:0:0:0): parity error during Data-In phase. SEQADDR == 0x10f SCSIRATE == 0x88 (da0:ahc0:0:0:0): parity error during Data-In phase. SEQADDR == 0x10e SCSIRATE == 0x88 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 10:39:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10135 for freebsd-current-outgoing; Thu, 21 Jan 1999 10:39:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA10130 for ; Thu, 21 Jan 1999 10:39:52 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.2/8.9.1) id MAA33677; Thu, 21 Jan 1999 12:38:14 -0600 (CST) (envelope-from dick) Date: Thu, 21 Jan 1999 12:38:14 -0600 From: "Richard Seaman, Jr." To: Jeremy Lea Cc: freebsd-current@FreeBSD.ORG, Julian Elischer , Peter Wemm Subject: Re: Using LinuxThreads Message-ID: <19990121123814.B5495@tar.com> References: <19990118182717.A15566@top.worldcontrol.com> <19990119024539.A88383@top.worldcontrol.com> <19990119140613.B826@shale.csir.co.za> <19990119091151.F600@tar.com> <19990121181228.A98581@shale.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <19990121181228.A98581@shale.csir.co.za>; from Jeremy Lea on Thu, Jan 21, 1999 at 06:12:29PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 21, 1999 at 06:12:29PM +0200, Jeremy Lea wrote: > On Tue, Jan 19, 1999 at 09:11:51AM -0600, Richard Seaman, Jr. wrote: > > Actually, the new version, in FreeBSD "ports" form, doesn't require > > -DLINUXTHREADS anymore, but it does require -I/usr/local/include to > > pick up the right header, since it installs a pthread.h into > > /usr/local/include. This conflicts with the pthread.h in /usr/include. > > This is nagging at me. Having two headers of the same name, but importantly > different content is asking for touble. There needs to be a way to ensure > that only one or the other is picked up. The best way I can think of is to > only include the contents of the user thread pthread.h if _THREAD_SAFE is > defined (to force people to use the right defines...) and the contents of > kernel thread pthread.h if _REENTRANT (and not _THREAD_SAFE) is defined. > This has the added bonus of meaning that most linux apps wont have to be > patched. Actually, its more complicated than this. Currently, _THREAD_SAFE is a switch for turning on libc_r behaviour when compiling libc_r, but it is a switch for more general thread safe behaviour in the header files for libc and libc_r. In other words, threaded applications linking against either libc or libc_r should define _THREAD_SAFE. But, when compiling libc, _THREAD_SAFE should be turned off. Very confusing IMHO. Now, on the topic of conflicting pthread.h files, I agree this is a problem. One choice, which I originally implemented, is to fix pthread.h so it pulls in the right data based on a swtich (eg. if LINUXTHREADS is defined, pull in LT headers, else pull in user threads headers). I don't like using _THREAD_SAFE for this test, for the reason mentioned above. And I don't like using _REENTRANT because its so widely used and it could still confure people. The second choice, which is what the current version of the "port" does, is to put the conflicting headers in different directories, and require the application to define the order of the include files to get the right one in. There are proglems either way, and I don't really prefer one over the other. > To many applications have configure scripts which might find > /usr/local/lib/libpthread, but not /usr/local/include/pthread.h, or find > /usr/lib/libc_r and find /usr/local/include/pthread.h. Yes. This is a problem. But, taking glib as an example, and using glib-1.1.13 directly (not the "port", which is kind of messed up for linuxthreads), the following configure script does the right thing: $ CPPFLAGS="-D_THREAD_SAFE -I/usr/local/include" LDFLAGS="-L/usr/local/lib" ./configure --with-threads=posix This isn't that bad, and I think you need to customize your configure scripts (normally) if you're using threads, anyway. > What are the plans for the import of the LinuxThreads stuff into the src > tree? Or is it going to remain a port, and the source tree position be > reserved for a future kernel threads implementation? My mind says it is to > closely tied to the OS to be a port. It can be a port. I suspect there will be more support for its possible inclusion this way. The current version at lt.tar.com is in ports form. Granted, it depends to an unusual degree (for a port) on having the src tree around. > And when are COMPAT_LINUX_THREADS and VM_STACK going away? I have no idea. I was hoping that at least COMPAT_LINUX_THREADS would go away before the branch. I don't have commit authority, so it isn't up to me. -- Richard Seamman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 10:40:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10289 for freebsd-current-outgoing; Thu, 21 Jan 1999 10:40:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA10284 for ; Thu, 21 Jan 1999 10:40:43 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.1) with ESMTP id UAA06348; Thu, 21 Jan 1999 20:40:26 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.2/8.9.2) with ESMTP id UAA92062; Thu, 21 Jan 1999 20:40:25 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199901211840.UAA92062@greenpeace.grondar.za> To: Kazutaka YOKOTA cc: current@FreeBSD.ORG Subject: Re: keymaps In-Reply-To: Your message of " Fri, 22 Jan 1999 01:05:22 +0900." <199901211605.BAA24511@zodiac.mech.utsunomiya-u.ac.jp> References: <199901211605.BAA24511@zodiac.mech.utsunomiya-u.ac.jp> Date: Thu, 21 Jan 1999 20:40:24 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kazutaka YOKOTA wrote: : > 104 Pause Start screen saver (saver). : > The above assignments for the keycodes 1, 57, 70, 84 and 92 are > compatible with many, if not all, existing keymaps. So far so good! > The assignments for 104 and 108 are new. 104 (Pause?) does the "Backscroll" on my Libretto 70. I'd hate to lose that. M To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 10:50:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11667 for freebsd-current-outgoing; Thu, 21 Jan 1999 10:50:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from emu.sourcee.com (emu.sourcee.com [205.181.251.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA11651 for ; Thu, 21 Jan 1999 10:50:43 -0800 (PST) (envelope-from nrice@emu.sourcee.com) Received: (from nrice@localhost) by emu.sourcee.com (8.9.1/8.9.1) id NAA27534 for freebsd-current@FreeBSD.ORG; Thu, 21 Jan 1999 13:50:34 -0500 (EST) Date: Thu, 21 Jan 1999 13:50:33 -0500 From: "Norman C. Rice" To: freebsd-current@FreeBSD.ORG Subject: make world fails -- libcrypt's Makefile? Message-ID: <19990121134847.A27178@emu.sourcee.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Current cvsup'd today at 12:08 EST -- make world failed looking for /usr/src/secure/lib/libcrypt/crypt-md5.c. It appears that crypt-md5.c and crypt.3 were moved to /usr/src/lib/libcrypt/ on Thu Jan 21 13:50:09 1999 UTC by brandon, but /usr/src/secure/lib/libcrypt/Makefile still references crypt-md5.c and crypt.3 SRCS= crypt.c crypt-md5.c md5c.c MAN3= crypt.3 -- Regards, Norman C. Rice, Jr. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 10:56:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA12286 for freebsd-current-outgoing; Thu, 21 Jan 1999 10:56:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA12269; Thu, 21 Jan 1999 10:56:24 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 103PGp-0002yV-00; Thu, 21 Jan 1999 11:55:59 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id LAA79083; Thu, 21 Jan 1999 11:53:46 -0700 (MST) Message-Id: <199901211853.LAA79083@harmony.village.org> To: Andrzej Bialecki Subject: Re: Heads up! New swapper and VM changes being committed to -4.x tonight. Cc: Matthew Dillon , current@FreeBSD.ORG, hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 21 Jan 1999 10:47:55 +0100." References: Date: Thu, 21 Jan 1999 11:53:46 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Andrzej Bialecki writes: : I'm more than willing to test it in low memory conditions.. :-) I have : that special 386SX/4MB RAM machine in the corner to test things like : picobsd memory requirements... So how well does this work? I have a 4MB machine that I'd like to run FreeBSD on, including X on a low res screen... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 11:13:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA14226 for freebsd-current-outgoing; Thu, 21 Jan 1999 11:13:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA14206 for ; Thu, 21 Jan 1999 11:13:01 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 103PX9-0002zG-00; Thu, 21 Jan 1999 12:12:51 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id MAA79228 for ; Thu, 21 Jan 1999 12:10:39 -0700 (MST) Message-Id: <199901211910.MAA79228@harmony.village.org> To: current@FreeBSD.ORG Subject: Mail archive question Date: Thu, 21 Jan 1999 12:10:38 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Given a message id and a mailing list, is there some way construct a URL that will fetch that mail message. This will make doing the UPDATING file a little easier when long messages are sent to -current. I can say blah blah blah changed, see for details. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 11:17:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA14637 for freebsd-current-outgoing; Thu, 21 Jan 1999 11:17:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles236.castles.com [208.214.165.236]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA14632 for ; Thu, 21 Jan 1999 11:17:52 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id LAA10340; Thu, 21 Jan 1999 11:13:50 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901211913.LAA10340@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: paul@originative.co.uk cc: julian@whistle.com, mike@smith.net.au, ck@adsu.bellsouth.com, obrien@NUXI.com, current@FreeBSD.ORG Subject: Re: KLD naming In-reply-to: Your message of "Thu, 21 Jan 1999 17:59:05 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Jan 1999 11:13:49 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Well whistle is giving htis away so we don'tthink it should > > be whistle_xxx > > any more than the kernel should be UCB/... > > It occur to me that eventually every single device driver > > will be a KLD > > an also a lot of other things besides... > > there are going to be a LOT of files in /modules.... > > Ok, in this case maybe it doesn't apply but in general we should > determine what the guidelines for third party module developers should > be to avoid namespace clashes. I though a FreeBSD prefix for modules > shipped as part of FreeBSD would be useful to list all those modules > that are *not* third party supplied when you've got a directory full of > the things. I've thought about this, and I think it would be a very bad idea. We want to keep this *simple*. In the case of, eg. OSS, one might expect: dev_oss.ko oss_yamaha.ko oss_sb16.ko ... There's no need to add extra crap just to identify the vendor. It doesn't serve any really useful purpose - we will have metainformation elsewhere that can be used to link modules comprising a product together - there's no need to duplicate it in the filename. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 11:22:22 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA15355 for freebsd-current-outgoing; Thu, 21 Jan 1999 11:22:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picalon.gun.de (picalon.gun.de [194.77.0.18] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA15347 for ; Thu, 21 Jan 1999 11:22:18 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.8.6/8.8.6) with ESMTP id UAA01383 for ; Thu, 21 Jan 1999 20:22:02 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.2/8.9.2) id UAA50431 for current@FreeBSD.ORG; Thu, 21 Jan 1999 20:14:21 +0100 (CET) (envelope-from andreas) Date: Thu, 21 Jan 1999 20:14:21 +0100 From: Andreas Klemm To: current@FreeBSD.ORG Subject: klogin.o(.text+0x3e): undefined reference to `_pam_noticketsdontcomplain' Message-ID: <19990121201420.A50416@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just wanted to let you know ... cc -O -pipe -DSETPROCTITLE -DSKEY -DLOGIN_CAP -DVIRTUAL_HOSTING -Wall -I/home/src/libexec/ftpd/../../contrib-crypto/telnet -DKERBEROS -I/usr/obj/home/src/tmp/usr/include -o ftpd ftpd.o ftpcmd.o logwtmp.o popen.o skey-stuff.o klogin.o -lskey -lmd -lcrypt -lutil -lkrb -ldes ftpd.o: In function `pass': ftpd.o(.text+0x11c9): undefined reference to `klogin' klogin.o: In function `_pam_klogin': klogin.o(.text+0x3e): undefined reference to `_pam_noticketsdontcomplain' klogin.o(.text+0x96): undefined reference to `_pam_krbtkfile_env' klogin.o(.text+0x167): undefined reference to `_pam_notickets' *** Error code 1 1 error -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 11:41:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA17286 for freebsd-current-outgoing; Thu, 21 Jan 1999 11:41:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA17281 for ; Thu, 21 Jan 1999 11:41:04 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA21279; Thu, 21 Jan 1999 11:04:53 -0800 (PST) Received: from s204m82.isp.whistle.com(207.76.204.82) via SMTP by alpo.whistle.com, id smtpda21270; Thu Jan 21 19:04:46 1999 Date: Thu, 21 Jan 1999 11:04:38 -0800 (PST) From: Julian Elischer X-Sender: julian@s204m82.isp.whistle.com To: "Richard Seaman, Jr." cc: Jeremy Lea , freebsd-current@FreeBSD.ORG, Peter Wemm Subject: Re: Using LinuxThreads In-Reply-To: <19990121123814.B5495@tar.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 21 Jan 1999, Richard Seaman, Jr. wrote: > > And when are COMPAT_LINUX_THREADS and VM_STACK going away? > > I have no idea. I was hoping that at least COMPAT_LINUX_THREADS > would go away before the branch. I don't have commit authority, > so it isn't up to me. > hmm did you send me the patches? I can certainly do it now..(given a patch set to apply) I just realised however, that if we make them go away we break SMP right? hmm I guess we only break it for programs that woudltry use it which should be none if you run SMP :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 11:41:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA17488 for freebsd-current-outgoing; Thu, 21 Jan 1999 11:41:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cerebus.nectar.com (nectar-gw.nectar.com [204.0.249.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA17471 for ; Thu, 21 Jan 1999 11:41:15 -0800 (PST) (envelope-from nectar@nectar.com) Received: (from smap@localhost) by cerebus.nectar.com (8.9.1/8.9.1) id NAA03584 for ; Thu, 21 Jan 1999 13:41:03 -0600 (CST) (envelope-from nectar@nectar.com) Received: from spawn.nectar.com(10.0.0.101) by cerebus.nectar.com via smap (V2.1) id xma003582; Thu, 21 Jan 99 13:40:55 -0600 Received: from spawn.nectar.com (localhost [127.0.0.1]) by spawn.nectar.com (8.9.2/8.9.1) with ESMTP id NAA29673 for ; Thu, 21 Jan 1999 13:40:54 -0600 (CST) (envelope-from nectar@spawn.nectar.com) Message-Id: <199901211940.NAA29673@spawn.nectar.com> X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine Subject: cvsup failures Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii To: current@FreeBSD.ORG Date: Thu, 21 Jan 1999 13:40:54 -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been seeing this since yesterday morning when trying to cvsup: Rmdir ispell/word2x Delete ispell/yodl/Makefile,v Delete ispell/yodl/files/md5,v Rmdir ispell/yodl/files Delete ispell/yodl/patches/patch-aa,v Rmdir ispell/yodl/patches Delete ispell/yodl/pkg/COMMENT,v Delete ispell/yodl/pkg/DESCR,v Delete ispell/yodl/pkg/PLIST,v Rmdir ispell/yodl/pkg Rmdir ispell/yodl Rmdir ispell *** *** runtime error: *** ASSERT failed *** file "../src/FileStatus.m3", line 467 *** Abort trap (core dumped) Any known problems, or should I clear out my repository and start over? Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 11:45:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA17823 for freebsd-current-outgoing; Thu, 21 Jan 1999 11:45:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cantor.boolean.net (cantor.boolean.net [209.133.111.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA17818 for ; Thu, 21 Jan 1999 11:44:58 -0800 (PST) (envelope-from Kurt@OpenLDAP.Org) Received: from gypsy (localhost [127.0.0.1]) by cantor.boolean.net (8.9.1/8.9.1) with SMTP id TAA04310; Thu, 21 Jan 1999 19:50:37 GMT (envelope-from Kurt@OpenLDAP.Org) Message-Id: <3.0.5.32.19990121114214.00958c30@localhost> X-Sender: guru@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Thu, 21 Jan 1999 11:42:14 -0800 To: Jeremy Lea From: "Kurt D. Zeilenga" Subject: Re: Using LinuxThreads Cc: "Richard Seaman, Jr." , freebsd-current@FreeBSD.ORG In-Reply-To: <19990121181228.A98581@shale.csir.co.za> References: <19990119091151.F600@tar.com> <19990118182717.A15566@top.worldcontrol.com> <19990119024539.A88383@top.worldcontrol.com> <19990119140613.B826@shale.csir.co.za> <19990119091151.F600@tar.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 06:12 PM 1/21/99 +0200, Jeremy Lea wrote: >On Tue, Jan 19, 1999 at 09:11:51AM -0600, Richard Seaman, Jr. wrote: >> Actually, the new version, in FreeBSD "ports" form, doesn't require >> -DLINUXTHREADS anymore, but it does require -I/usr/local/include to >> pick up the right header, since it installs a pthread.h into >> /usr/local/include. This conflicts with the pthread.h in /usr/include. It doesn't conflict, it overrides the pthread.h in /usr/include iff the port is installed AND the application is compiled with -I/usr/local/include. Sounds a lot like how various other 'replacement' libraries are implemented. >This is nagging at me. Having two headers of the same name, but importantly >different content is asking for touble. There needs to be a way to ensure >that only one or the other is picked up. The best way I can think of is to >only include the contents of the user thread pthread.h if _THREAD_SAFE is >defined (to force people to use the right defines...) and the contents of >kernel thread pthread.h if _REENTRANT (and not _THREAD_SAFE) is defined. >This has the added bonus of meaning that most linux apps wont have to be >patched. Of course, this would only work if the contents of the two pthread.h files were merged. I'm not sure this is a good idea. If you did this, do NOT use -D_REENTRANT or -D_THREAD_SAFE as the conditional to determine the content. Use -DLINUXTHREADS or something. >To many applications have configure scripts which might find >/usr/local/lib/libpthread, but not /usr/local/include/pthread.h, or find >/usr/lib/libc_r and find /usr/local/include/pthread.h. Garbage in, garbage out. If the configure script in handed ill defined environment settings (CPPFLAGS, LDFLAGS) you get what you deserve! > Can gcc be made to define _THREAD_SAFE automatically if -pthread >is given? And _REENTRANT if -kthread is given? -pthread/-kthread, in my option, should be considerred linker options (basically just a short hand for -lc_r -nostdlib) BTW, why does FreeBSD use -D_THREAD_SAFE AND -D_REENTRANT (math.h) while most other PThread (final) implementations use -D_REENTRANT? Also, the cc(1) says to use -D_THREADSAFE not -D_THREAD_SAFE. Personallly, I think -DREENTRANT should be used for include all prototypes for reentrant functions not requiring thread support (like strtok_r) and -D_THREAD_SAFE routines only implemented in -lc_r. If possible, functions should be implemented in both -lc and -lc_r such that 3rd party libraries wouldn't have to create both a -lfoolib vs. -lfoolib_r versions (unless their _r versions requires threading). Kurt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 11:59:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19839 for freebsd-current-outgoing; Thu, 21 Jan 1999 11:59:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19832 for ; Thu, 21 Jan 1999 11:59:12 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.2/8.9.1) id NAA86426; Thu, 21 Jan 1999 13:57:20 -0600 (CST) (envelope-from dick) Date: Thu, 21 Jan 1999 13:57:20 -0600 From: "Richard Seaman, Jr." To: Julian Elischer Cc: Jeremy Lea , freebsd-current@FreeBSD.ORG, Peter Wemm Subject: Re: Using LinuxThreads Message-ID: <19990121135720.C5495@tar.com> References: <19990121123814.B5495@tar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Julian Elischer on Thu, Jan 21, 1999 at 11:04:38AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 21, 1999 at 11:04:38AM -0800, Julian Elischer wrote: > > > On Thu, 21 Jan 1999, Richard Seaman, Jr. wrote: > > > > And when are COMPAT_LINUX_THREADS and VM_STACK going away? > > > > I have no idea. I was hoping that at least COMPAT_LINUX_THREADS > > would go away before the branch. I don't have commit authority, > > so it isn't up to me. > > > > hmm did you send me the patches? No. You said you wanted Peter to do it. I offered to send patches upon request, but never got a request. :) > > I can certainly do it now..(given a patch set to apply) Ok. I'll send it. Do you want VM_STACK out too? > I just realised however, that if we make them go away we break > SMP right? No. I don't think the patches affect SMP one way or the other. If someone tries to run kernel threads of any kind (linuxthreads in emulation, linuxthread in FreeBSD native, any other kernel threads implementation that uses rfork with RFMEM) rfork will fail, with or without the patches (unless you apply Luoqi Chen's pmap patches). I see no reason the patches shouldn't work with SMP when rfork gets fixed, but I haven't tried it. > hmm I guess we only break it for programs that woudltry use it > which should be none if you run SMP :-) See above. -- Richard Seamman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 12:08:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA21213 for freebsd-current-outgoing; Thu, 21 Jan 1999 12:08:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA21207 for ; Thu, 21 Jan 1999 12:08:08 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id NAA84520; Thu, 21 Jan 1999 13:07:53 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199901212007.NAA84520@panzer.plutotech.com> Subject: Re: SCSI errors from IBM Netfinity 3500 In-Reply-To: <36A7724F.E283588A@MexComUSA.net> from Edwin Culp at "Jan 21, 99 10:30:39 am" To: eculp@MexComUSA.net (Edwin Culp) Date: Thu, 21 Jan 1999 13:07:53 -0700 (MST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Edwin Culp wrote... > I'm getting a lot of these SCSI disk errors from Current as of Sunday > with the onboard Adaptec Controler with an IBM netfinity 3500. Can > someone tell me if I should worry and/or what they mean? > > Thanks, > > ed > > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10e > SCSIRATE == 0x88 > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x4f > SCSIRATE == 0x88 > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10f > SCSIRATE == 0x88 > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10e > SCSIRATE == 0x88 You have a cabling or termination problem. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 12:11:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA21666 for freebsd-current-outgoing; Thu, 21 Jan 1999 12:11:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oreo.adsu.bellsouth.com (oreo.adsu.bellsouth.com [205.152.173.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA21661 for ; Thu, 21 Jan 1999 12:11:01 -0800 (PST) (envelope-from ck@oreo.adsu.bellsouth.com) Received: (from ck@localhost) by oreo.adsu.bellsouth.com (8.9.1/8.9.1) id PAA76705; Thu, 21 Jan 1999 15:10:44 -0500 (EST) (envelope-from ck) Date: Thu, 21 Jan 1999 15:10:44 -0500 From: Christian Kuhtz To: Mike Smith Cc: current@FreeBSD.ORG Subject: kld meta info (Re: KLD naming) Message-ID: <19990121151044.B5050@oreo.adsu.bellsouth.com> References: <199901211913.LAA10340@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199901211913.LAA10340@dingo.cdrom.com>; from Mike Smith on Thu, Jan 21, 1999 at 11:13:49AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there meta information in a .ko file? That way you could do a kldinfo to find out where to go for more info, etc. On Thu, Jan 21, 1999 at 11:13:49AM -0800, Mike Smith wrote: > I've thought about this, and I think it would be a very bad idea. > > We want to keep this *simple*. In the case of, eg. OSS, one might > expect: > > dev_oss.ko > oss_yamaha.ko > oss_sb16.ko > ... > > There's no need to add extra crap just to identify the vendor. It > doesn't serve any really useful purpose - we will have metainformation > elsewhere that can be used to link modules comprising a product > together - there's no need to duplicate it in the filename. -- "Logic is a little bird, sitting in a tree; that smells *awful*." -- /usr/bin/fortune [Disclaimer: I speak for myself and my views are my own and not in any way to be construed as the views of BellSouth Corporation. ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 12:12:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA22017 for freebsd-current-outgoing; Thu, 21 Jan 1999 12:12:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA22006 for ; Thu, 21 Jan 1999 12:12:42 -0800 (PST) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from mail.siemens.de (salomon.siemens.de [139.23.33.13]) by david.siemens.de (8.9.2/8.9.2) with ESMTP id VAA27343 for ; Thu, 21 Jan 1999 21:12:21 +0100 (MET) Received: from curry.mchp.siemens.de (daemon@curry.mchp.siemens.de [146.180.31.23]) by mail.siemens.de (8.9.2/8.9.2) with ESMTP id VAA03682 for ; Thu, 21 Jan 1999 21:12:24 +0100 (MET) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.8/8.8.8) id VAA24305 for ; Thu, 21 Jan 1999 21:12:24 +0100 (CET) Date: Thu, 21 Jan 1999 21:12:21 +0100 From: Andre Albsmeier To: "David E. Cross" Cc: current@FreeBSD.ORG Subject: Re: mountd Message-ID: <19990121211221.A11186@internal> References: <199901211554.KAA28454@cs.rpi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199901211554.KAA28454@cs.rpi.edu>; from David E. Cross on Thu, Jan 21, 1999 at 10:54:36AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 21-Jan-1999 at 10:54:36 -0500, David E. Cross wrote: > I posted this awhile ago to -questions, but never received a reply. > > We have a number of FreeBSD NFS servers here. Occasionally we need to > change the exports list on the servers and send mountd a SIGHUP. This > leads to a condition that in many ways is much worse than a server reboot. > > What happens is for the duration of mountd reading the exports file it denies > all NFS requests. This has a number of bad effects; 1) any user home and > system directories become unavailable, with the error 'permission denied' 2) > (and this is far worse), any process with a mapped .text segment off of the > NFS server, should it branch to code not in the cache gets immediately killed. > This include user processes that are running from home directories, and system > processes (such as ssh). If we were to reboot the machine it would just > hang those connections until the machine came back, without killing anyone. > > Is there a solution to this problem? I know that none of HP-UX, IRIX, or > Solaris have this problem. Please, please, if anyone knows a solution for this, drop me a note also... Thanks, -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 12:15:43 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA22514 for freebsd-current-outgoing; Thu, 21 Jan 1999 12:15:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles236.castles.com [208.214.165.236]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA22493 for ; Thu, 21 Jan 1999 12:15:35 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA10797; Thu, 21 Jan 1999 12:11:29 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901212011.MAA10797@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Christian Kuhtz cc: Mike Smith , current@FreeBSD.ORG Subject: Re: kld meta info (Re: KLD naming) In-reply-to: Your message of "Thu, 21 Jan 1999 15:10:44 EST." <19990121151044.B5050@oreo.adsu.bellsouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Jan 1999 12:11:28 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Is there meta information in a .ko file? That way you could do a kldinfo to > find out where to go for more info, etc. There's not time to standardise this, so I would say that 3.x .ko files won't have metainformation internally, no. Certainly 4.x .ko files will carry a lot more metainformation with them, and that may include this, yes. > On Thu, Jan 21, 1999 at 11:13:49AM -0800, Mike Smith wrote: > > I've thought about this, and I think it would be a very bad idea. > > > > We want to keep this *simple*. In the case of, eg. OSS, one might > > expect: > > > > dev_oss.ko > > oss_yamaha.ko > > oss_sb16.ko > > ... > > > > There's no need to add extra crap just to identify the vendor. It > > doesn't serve any really useful purpose - we will have metainformation > > elsewhere that can be used to link modules comprising a product > > together - there's no need to duplicate it in the filename. > > -- > "Logic is a little bird, sitting in a tree; that smells *awful*." > -- /usr/bin/fortune > > [Disclaimer: I speak for myself and my views are my own and not in any way to > be construed as the views of BellSouth Corporation. ] -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 12:24:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA24141 for freebsd-current-outgoing; Thu, 21 Jan 1999 12:24:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA24134 for ; Thu, 21 Jan 1999 12:24:49 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.9.1) id MAA23279 for freebsd-current@freebsd.org; Thu, 21 Jan 1999 12:26:04 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199901212026.MAA23279@troutmask.apl.washington.edu> Subject: src/secure breaks world To: freebsd-current@FreeBSD.ORG Date: Thu, 21 Jan 1999 12:26:04 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cd /usr/src/secure/lib/libcrypt; /usr/obj/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED cleandepend; /usr/obj/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED all; /usr/obj/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -B install cleandir obj rm -f .depend /usr/obj/usr/src/secure/lib/libcrypt/GPATH /usr/obj/usr/src/secure/lib/libcrypt/GRTAGS /usr/obj/usr/src/secure/lib/libcrypt/GSYMS /usr/obj/usr/src/secure/lib/libcrypt/GTAGS make: don't know how to make crypt-md5.c. Stop *** Error code 2 1 error Seem crypt-md5.c was moved into the attic, but the Makefile was updated. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 12:27:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA24517 for freebsd-current-outgoing; Thu, 21 Jan 1999 12:27:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA24511 for ; Thu, 21 Jan 1999 12:27:52 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id MAA24634; Thu, 21 Jan 1999 12:22:32 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdL24625; Thu Jan 21 20:22:27 1999 Date: Thu, 21 Jan 1999 12:22:17 -0800 (PST) From: Julian Elischer To: "Richard Seaman, Jr." cc: Jeremy Lea , freebsd-current@FreeBSD.ORG, Peter Wemm Subject: Re: Using LinuxThreads In-Reply-To: <19990121135720.C5495@tar.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 21 Jan 1999, Richard Seaman, Jr. wrote: > On Thu, Jan 21, 1999 at 11:04:38AM -0800, Julian Elischer wrote: > > > > > > On Thu, 21 Jan 1999, Richard Seaman, Jr. wrote: > > > > > > And when are COMPAT_LINUX_THREADS and VM_STACK going away? > > > > > > I have no idea. I was hoping that at least COMPAT_LINUX_THREADS > > > would go away before the branch. I don't have commit authority, > > > so it isn't up to me. > > > > > > > hmm did you send me the patches? > > No. You said you wanted Peter to do it. I offered to send > patches upon request, but never got a request. :) > > > > > I can certainly do it now..(given a patch set to apply) > > Ok. I'll send it. Do you want VM_STACK out too? yes > > > I just realised however, that if we make them go away we break > > SMP right? > > No. I don't think the patches affect SMP one way or the other. > If someone tries to run kernel threads of any kind (linuxthreads > in emulation, linuxthread in FreeBSD native, any other kernel > threads implementation that uses rfork with RFMEM) rfork will > fail, with or without the patches (unless you apply Luoqi Chen's > pmap patches). > > I see no reason the patches shouldn't work with SMP when rfork > gets fixed, but I haven't tried it. ok send them and I'll commit julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 12:28:50 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA24678 for freebsd-current-outgoing; Thu, 21 Jan 1999 12:28:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles236.castles.com [208.214.165.236]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA24668 for ; Thu, 21 Jan 1999 12:28:47 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA10887; Thu, 21 Jan 1999 12:25:01 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901212025.MAA10887@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: paul@originative.co.uk cc: current@FreeBSD.ORG Subject: Re: KLD naming In-reply-to: Your message of "Thu, 21 Jan 1999 20:21:05 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Jan 1999 12:25:00 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've taken this off list. I'm not sure we're quite addressing the same > issue. No, I think we were at angles for a bit here. But I do believe that this is something work copying to people on the list, as you do raise a very good point. I hope this was on -current. 8) > > I've thought about this, and I think it would be a very bad idea. > > > > We want to keep this *simple*. In the case of, eg. OSS, one might > > expect: > > > > dev_oss.ko > > oss_yamaha.ko > > oss_sb16.ko > > ... > > > > There's no need to add extra crap just to identify the vendor. It > > doesn't serve any really useful purpose - we will have > > metainformation elsewhere that can be used to link modules > > comprising a product together - there's no need to duplicate it > > in the filename. > > It's not a question, primarily, of being able to identify the vendor > from the filename, it's more the case of different vendors not both > choosing the *same* filename thereby making it very difficult to install > them both at the same time. I'm saying primarily since if we do have a > vendor prefix in the filename it would make it easy to see where a > module came from but that is not my main motivation for suggesting it. > > I'm proposing that the guidleline be that anyone wishing to publish > their own modules (i.e. not contribute them to the FreeBSD source base) > should effectively create their own namespace by prefixing the filename > with a vendor code. This would make clashes a lot less likely and if > necessary a registry of vendor codes would have to be made available. > > I can't see how you can avoid namespace clashes otherwise. Third party > developers aren't likely to communicate with each other to ensure > uniqueness so it's better that the naming convention provide a mechanism > for such parties to ensure that the filenames they choose don't clash > with other people's modules. Ah, understood. I'd be inclined to use a suffix, so that our prefix-based classification scheme still worked, eg. dev_ahc_Adaptec.ko kern_descrypt_RSA.ko etc. > It'd be very irritating to pop a floppy in the machine that you got from > some vendor, run install and then find that some important module had > been overwritten from the vendor disk, or that the install failed > because it couldn't copy over all the modules. Understood now, yes. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 12:37:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA25435 for freebsd-current-outgoing; Thu, 21 Jan 1999 12:37:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from burka.carrier.kiev.ua (burka.carrier.kiev.ua [193.193.193.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA25430 for ; Thu, 21 Jan 1999 12:37:26 -0800 (PST) (envelope-from archer@lucky.net) Received: (from archer@localhost) by burka.carrier.kiev.ua (8.Who.Cares/8.Who.Cares) id WAA07569 for current@freebsd.org; Thu, 21 Jan 1999 22:37:15 +0200 (EET) (envelope-from archer) Date: Thu, 21 Jan 1999 22:37:15 +0200 (EET) From: Alexander Litvin Message-Id: <199901212037.WAA07569@burka.carrier.kiev.ua> To: current@FreeBSD.ORG Subject: Re: PR filed on dying daemons bug X-Newsgroups: sita.freebsd.current In-Reply-To: <199812280019.QAA22862@hub.freebsd.org> User-Agent: tin/pre-1.4-980226 (UNIX) (FreeBSD/2.2.6-RELEASE (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199812280019.QAA22862@hub.freebsd.org> you wrote: > On 28 Dec, Dmitrij Tejblum wrote: >> I once suggested this patch: >> > [ patch snipped ] >> >> Dima >> > My, I forgot about that patch. It is working so far right now (I've > managed to bring the swap usage to levels which would trigger the bug > before, and nothing has happened yet) > Thank you very much for that patch, please consider this a premature > positive response :) > I haven't had any negative side-effects as a result of this patch, and > it might just be my imagination but it seemed to take much more work to > get the machine to swap than before. If I'm not mistaken, I was that person who gave the positive response to Dima's patch. Since applying it I was not able to reproduce "daemons dying". Though it seems that nobody responsible for FreeBSD VM paied attention to that. I think that it happened so that people who do not see the problem on their machines just do not beleive the problem really exist ;) :(. > -- > Jason Garman http://fs.sso.sytexinc.com/~jgarman/ > Student, University of Maryland garman@earthling.net > Words of Wisdom from the Simpsons: Whois: JAG145 > "'The President did it' is not an excuse" -- Bart Simpson's punishment --- "I didn't know it was impossible when I did it." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 12:41:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA25740 for freebsd-current-outgoing; Thu, 21 Jan 1999 12:41:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA25733 for ; Thu, 21 Jan 1999 12:41:15 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.2/8.9.1) id OAA06652; Thu, 21 Jan 1999 14:39:40 -0600 (CST) (envelope-from dick) Date: Thu, 21 Jan 1999 14:39:40 -0600 From: "Richard Seaman, Jr." To: "Kurt D. Zeilenga" Cc: Jeremy Lea , freebsd-current@FreeBSD.ORG Subject: Re: Using LinuxThreads Message-ID: <19990121143940.D5495@tar.com> References: <19990119091151.F600@tar.com> <19990118182717.A15566@top.worldcontrol.com> <19990119024539.A88383@top.worldcontrol.com> <19990119140613.B826@shale.csir.co.za> <19990119091151.F600@tar.com> <19990121181228.A98581@shale.csir.co.za> <3.0.5.32.19990121114214.00958c30@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <3.0.5.32.19990121114214.00958c30@localhost>; from Kurt D. Zeilenga on Thu, Jan 21, 1999 at 11:42:14AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 21, 1999 at 11:42:14AM -0800, Kurt D. Zeilenga wrote: > >This is nagging at me. Having two headers of the same name, but importantly > >different content is asking for touble. There needs to be a way to ensure > >that only one or the other is picked up. The best way I can think of is to > >only include the contents of the user thread pthread.h if _THREAD_SAFE is > >defined (to force people to use the right defines...) and the contents of > >kernel thread pthread.h if _REENTRANT (and not _THREAD_SAFE) is defined. > >This has the added bonus of meaning that most linux apps wont have to be > >patched. > > Of course, this would only work if the contents of the two pthread.h files > were merged. I'm not sure this is a good idea. I'm not advocating any changes. But, IMO the best way to do it, if you did, wouldn't be to merge the files, but rather to re-implemnt pthread.h like: #ifdef LINUXTHREADS #include <..pointer to lt pthread.h file..> #else #include <..pointer to user thread pthread.h file..> #endif > If you did this, do NOT use -D_REENTRANT or -D_THREAD_SAFE as the conditional > to determine the content. Use -DLINUXTHREADS or something. Right. > BTW, why does FreeBSD use -D_THREAD_SAFE AND -D_REENTRANT (math.h) > while most other PThread (final) implementations use -D_REENTRANT? Don't know. Using _REENTRANT would be preferable, IMO. > > Also, the cc(1) says to use -D_THREADSAFE not -D_THREAD_SAFE. Hmm. Not on my machine. :) > Personallly, I think -DREENTRANT should be used for include all prototypes > for reentrant functions not requiring thread support (like strtok_r) and > -D_THREAD_SAFE routines only implemented in -lc_r. I think _THREAD_SAFE should be used as a switch when compiling libc/libc_r to turn on libc_r specific options, which is how it is primarily used now. _REENTRANT should be used in all libc/libc_r and system headers to turn on generic thread safe options. > If possible, functions > should be implemented in both -lc and -lc_r such that 3rd party libraries > wouldn't have to create both a -lfoolib vs. -lfoolib_r versions (unless > their _r versions requires threading). For kernel threading you just use libc. Whether or not libc generates thread safe (re-entrant) calls depends on whether its also linked with a library that 1) sets __isthreaded to a non-zero value, 2) has a _spinlock() implementationm, and 3) implements the functions flockfile, funlockfile, etc. There are also a few macros in header files that require _THREAD_SAFE to be defined to be thread safe. libc_r could be modified so that is doesn't replace libc, but rather is an addon, comparable to the kernel threaded libc case. But, it would involve a bit of work. -- Richard Seamman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 13:08:39 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA28142 for freebsd-current-outgoing; Thu, 21 Jan 1999 13:08:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA28137 for ; Thu, 21 Jan 1999 13:08:37 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.1/8.9.1) id WAA43344; Thu, 21 Jan 1999 22:08:09 +0100 (CET) (envelope-from des) To: "Joerg B. Micheel" Cc: Dag-Erling Smorgrav , Mike Nguyen , current@FreeBSD.ORG Subject: Re: /etc/nsswitch.conf References: <19990121023914.B468@krdl.org.sg> From: Dag-Erling Smorgrav Date: 21 Jan 1999 22:08:08 +0100 In-Reply-To: "Joerg B. Micheel"'s message of "Thu, 21 Jan 1999 02:39:14 +0800" Message-ID: Lines: 17 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Joerg B. Micheel" writes: > > consolidating all that config information in one place, such as > > /etc/rc.conf, would be a good thing. > Agreed, it really isn't such a good idea to clutter /etc/ with all > those single line configuration files. Actually, they did it for a reason, and it's not really a *bad* reason. It makes automated administration a lot easier - e.g. writing scripts that modify the system config etc. Solaris (and SysV in general) is *very* geared towards automated adminning. That's not necessarily a bad thing, if it's done properly, but I don't agree with the way they chose to solve some of the problems that arise when you do that. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 13:10:16 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA28344 for freebsd-current-outgoing; Thu, 21 Jan 1999 13:10:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA28336 for ; Thu, 21 Jan 1999 13:10:13 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.2/8.9.2/Netplex) with ESMTP id FAA27978; Fri, 22 Jan 1999 05:08:11 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199901212108.FAA27978@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Julian Elischer cc: "Richard Seaman, Jr." , Jeremy Lea , freebsd-current@FreeBSD.ORG Subject: Re: Using LinuxThreads In-reply-to: Your message of "Thu, 21 Jan 1999 12:22:17 PST." Date: Fri, 22 Jan 1999 05:08:11 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer wrote: [..] > > > I just realised however, that if we make them go away we break > > > SMP right? > > > > No. I don't think the patches affect SMP one way or the other. > > If someone tries to run kernel threads of any kind (linuxthreads > > in emulation, linuxthread in FreeBSD native, any other kernel > > threads implementation that uses rfork with RFMEM) rfork will > > fail, with or without the patches (unless you apply Luoqi Chen's > > pmap patches). > > > > I see no reason the patches shouldn't work with SMP when rfork > > gets fixed, but I haven't tried it. > > ok send them and I'll commit > > julian Wait a day or two for the VM dust to settle otherwise there will be no telling which set of code is causing problems. The POSIX options probably need to go on with this or there isn't much point doing it since it's part of what the linux threads package calls. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 13:16:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA28869 for freebsd-current-outgoing; Thu, 21 Jan 1999 13:16:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp2.erols.com (smtp2.erols.com [207.172.3.235]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA28860 for ; Thu, 21 Jan 1999 13:16:04 -0800 (PST) (envelope-from marlowe@alfheim.net) Received: from soia.erols.com (soia.erols.com [209.122.180.118]) by smtp2.erols.com (8.8.8/8.8.5) with SMTP id QAA10753 for ; Thu, 21 Jan 1999 16:20:52 -0500 (EST) Date: Thu, 21 Jan 1999 16:16:16 -0500 (EST) From: Matthew Marlowe X-Sender: marlowe@soia.erols.com To: current@FreeBSD.ORG Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 13:57:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA03671 for freebsd-current-outgoing; Thu, 21 Jan 1999 13:57:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles236.castles.com [208.214.165.236]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA03664 for ; Thu, 21 Jan 1999 13:57:28 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA11404; Thu, 21 Jan 1999 13:53:45 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901212153.NAA11404@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Geoff Buckingham cc: freebsd-current@FreeBSD.ORG Subject: Re: KVA/KVM shortages In-reply-to: Your message of "Thu, 21 Jan 1999 18:09:41 GMT." <19990121180941.G19395@gti.noc.demon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Jan 1999 13:53:44 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On tuesday I crashed a machine after it ran out of kvm. (dual PII 400 with > 768MB RAM) poking about in the code adding: > > options "VM_KMEM_SIZE=(24*1024*1024)" > options "VM_KMEM_SIZE_MAX=(128*1024*1024)" > > seems like a good way foward. Is it? >From what I can see, you shouldn't need to set VM_KMEM_SIZE_MAX unless you're also setting VM_KMEM_SIZE_SCALE. I just committed a tweak that allows you to say: set kern.vm.kmem.size= at the loader prompt or in /boot/loader.rc to override the default VM_KMEM_SIZE value. If anyone has any more of these tunables that can easily be enhanced like this, please let me know. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 14:03:22 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA04279 for freebsd-current-outgoing; Thu, 21 Jan 1999 14:03:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cantor.boolean.net (cantor.boolean.net [209.133.111.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA04256 for ; Thu, 21 Jan 1999 14:03:18 -0800 (PST) (envelope-from Kurt@OpenLDAP.Org) Received: from OpenLDAP.Org (localhost [127.0.0.1]) by cantor.boolean.net (8.9.1/8.9.1) with ESMTP id WAA06591; Thu, 21 Jan 1999 22:09:19 GMT (envelope-from Kurt@OpenLDAP.Org) Message-ID: <36A7A395.29B3E8A7@OpenLDAP.Org> Date: Thu, 21 Jan 1999 14:00:53 -0800 From: "Kurt D. Zeilenga" Organization: OpenLDAP X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en-GB,en-US,en,de-DE,de MIME-Version: 1.0 To: "Richard Seaman, Jr." CC: freebsd-current@FreeBSD.ORG Subject: -D_REENTRANT (Was: Using LinuxThreads) References: <19990119091151.F600@tar.com> <19990118182717.A15566@top.worldcontrol.com> <19990119024539.A88383@top.worldcontrol.com> <19990119140613.B826@shale.csir.co.za> <19990119091151.F600@tar.com> <19990121181228.A98581@shale.csir.co.za> <3.0.5.32.19990121114214.00958c30@localhost> <19990121143940.D5495@tar.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Richard Seaman, Jr." wrote: > > BTW, why does FreeBSD use -D_THREAD_SAFE AND -D_REENTRANT (math.h) > > while most other PThread (final) implementations use -D_REENTRANT? > Don't know. Using _REENTRANT would be preferable, IMO. Now if only a committer would agree... (I'll send patches if needed). > > Also, the cc(1) says to use -D_THREADSAFE not -D_THREAD_SAFE. > Hmm. Not on my machine. :) http://www.freebsd.org/cgi/man.cgi?query=cc&apropos=0&sektion=0&manpath=FreeBSD+3.0-current&format=html > > Personallly, I think -DREENTRANT should be used for include all prototypes > > for reentrant functions not requiring thread support (like strtok_r) and > > -D_THREAD_SAFE routines only implemented in -lc_r. > > I think _THREAD_SAFE should be used as a switch when compiling libc/libc_r to > turn on libc_r specific options, which is how it is primarily used now. Then it shouldn't be used in the headers if at all possible! > _REENTRANT should be used in all libc/libc_r and system headers to turn on > generic thread safe options. -D_REENTRANT should turn on reentrant functions, some of which may or may not be thread safe, that do not require threading support to implement. Reentrant functions that require threading support to implement should only be behind a different define. I think the problem is that folks tend to think the reentrant functions are only for use in threaded applications. They are quite useful in non-threaded applications as well (especially strtok_r). > > If possible, functions > > should be implemented in both -lc and -lc_r such that 3rd party libraries > > wouldn't have to create both a -lfoolib vs. -lfoolib_r versions (unless > > their _r versions requires threading). > > For kernel threading you just use libc. Whether or not libc generates > thread safe (re-entrant) calls depends on whether its also linked with > a library that 1) sets __isthreaded to a non-zero value, 2) has a _spinlock() > implementationm, and 3) implements the functions flockfile, funlockfile, etc. > There are also a few macros in header files that require _THREAD_SAFE to > be defined to be thread safe. I was hoping to be able to produce one ldap library that could be safely linked with or without threads. However, if I must define _THREAD_SAFE to generate code to be linked with threads then I must produce two libraries (-lfoolib compiled with -U_THREAD_SAFE and -lfoolib_r with -D_THREAD_SAFE). This is quite painful. Many 3rd packages won't go through the pain. They will generate one library and assume all users will compile/link with compatible flags. Of course, most users don't know how their libraries were built nor pay much attention when configure dependent software. We run into this big time with OpenLDAP and third party packages such as DB2. It gets real complicated with try to link with multiple third party libs which may or may not be compiled with -D_THREAD_SAFE. errno was the biggest problem, but its conditional declaration of it has long since been removed. 3rd party library implementors need to be careful when using any function with a conditional declaration as you don't know which you'll get when an application is linked. We also only use reentrant functions where exist in -lc and avoid functions such as feof that may have conditional declarations. This allows us to build one -lldap that *can be* safely used by both threaded and non-threaded applications. > libc_r could be modified so that is doesn't replace libc, but rather is > an addon, comparable to the kernel threaded libc case. But, it would > involve a bit of work. > > -- > Richard Seamman, Jr. email: dick@tar.com > 5182 N. Maple Lane phone: 414-367-5450 > Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 14:06:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA04648 for freebsd-current-outgoing; Thu, 21 Jan 1999 14:06:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA04641 for ; Thu, 21 Jan 1999 14:06:19 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id OAA21381; Thu, 21 Jan 1999 14:06:10 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id OAA07883; Thu, 21 Jan 1999 14:06:09 -0800 (PST) (envelope-from jdp@polstra.com) Date: Thu, 21 Jan 1999 14:06:09 -0800 (PST) Message-Id: <199901212206.OAA07883@vashon.polstra.com> To: andreas@klemm.gtn.com Subject: Re: klogin.o(.text+0x3e): undefined reference to `_pam_noticketsdontcomplain' Newsgroups: polstra.freebsd.current In-Reply-To: <19990121201420.A50416@titan.klemm.gtn.com> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19990121201420.A50416@titan.klemm.gtn.com>, Andreas Klemm wrote: > cc -O -pipe -DSETPROCTITLE -DSKEY -DLOGIN_CAP -DVIRTUAL_HOSTING -Wall -I/home/src/libexec/ftpd/../../contrib-crypto/telnet -DKERBEROS -I/usr/obj/home/src/tmp/usr/include -o ftpd ftpd.o ftpcmd.o logwtmp.o popen.o skey-stuff.o klogin.o -lskey -lmd -lcrypt -lutil -lkrb -ldes > ftpd.o: In function `pass': > ftpd.o(.text+0x11c9): undefined reference to `klogin' > klogin.o: In function `_pam_klogin': > klogin.o(.text+0x3e): undefined reference to `_pam_noticketsdontcomplain' > klogin.o(.text+0x96): undefined reference to `_pam_krbtkfile_env' > klogin.o(.text+0x167): undefined reference to `_pam_notickets' Sorry folks! Pointy hat, please. I fixed it now, in both -current and RELENG_3. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 14:11:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA05208 for freebsd-current-outgoing; Thu, 21 Jan 1999 14:11:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from emu.sourcee.com (emu.sourcee.com [205.181.251.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA05200 for ; Thu, 21 Jan 1999 14:11:16 -0800 (PST) (envelope-from nrice@emu.sourcee.com) Received: (from nrice@localhost) by emu.sourcee.com (8.9.1/8.9.1) id RAA28147; Thu, 21 Jan 1999 17:10:27 -0500 (EST) Date: Thu, 21 Jan 1999 17:10:27 -0500 From: "Norman C. Rice" To: Steve Kargl Cc: freebsd-current@FreeBSD.ORG Subject: Re: src/secure breaks world Message-ID: <19990121171027.A27856@emu.sourcee.com> References: <199901212026.MAA23279@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199901212026.MAA23279@troutmask.apl.washington.edu>; from Steve Kargl on Thu, Jan 21, 1999 at 12:26:04PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 21, 1999 at 12:26:04PM -0800, Steve Kargl wrote: > cd /usr/src/secure/lib/libcrypt; /usr/obj/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED cleandepend; /usr/obj/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED all; /usr/obj/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -B install cleandir obj > rm -f .depend /usr/obj/usr/src/secure/lib/libcrypt/GPATH /usr/obj/usr/src/secure/lib/libcrypt/GRTAGS /usr/obj/usr/src/secure/lib/libcrypt/GSYMS /usr/obj/usr/src/secure/lib/libcrypt/GTAGS > make: don't know how to make crypt-md5.c. Stop > *** Error code 2 > 1 error > > Seem crypt-md5.c was moved into the attic, but the Makefile was updated. Do you mean "wasn't" updated? I am not sure that fixing the Makefile will resolve all the issues with the recent libcrypt changes. -- Regards, Norman C. Rice, Jr. > -- > Steve > > finger kargl@troutmask.apl.washington.edu > http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 14:16:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA05507 for freebsd-current-outgoing; Thu, 21 Jan 1999 14:16:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA05497 for ; Thu, 21 Jan 1999 14:15:57 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.9.1) id OAA07856; Thu, 21 Jan 1999 14:17:06 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199901212217.OAA07856@troutmask.apl.washington.edu> Subject: Re: src/secure breaks world In-Reply-To: <19990121171027.A27856@emu.sourcee.com> from "Norman C. Rice" at "Jan 21, 1999 5:10:27 pm" To: nrice@emu.sourcee.com (Norman C. Rice) Date: Thu, 21 Jan 1999 14:17:06 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Norman C. Rice wrote: > On Thu, Jan 21, 1999 at 12:26:04PM -0800, Steve Kargl wrote: > > make: don't know how to make crypt-md5.c. Stop > > *** Error code 2 > > 1 error > > > > Seem crypt-md5.c was moved into the attic, but the Makefile was updated. > > Do you mean "wasn't" updated? Yes, of course. I think faster than I type. > I am not sure that fixing the Makefile will resolve all the issues with the > recent libcrypt changes. I agree because there is now src/lib/libcrypt/crypt-md5.c, and its unclear whether one should delete crypt-md5.c from SRCS in the Makefile or change .PATH to pick up the new file. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 14:16:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA05582 for freebsd-current-outgoing; Thu, 21 Jan 1999 14:16:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from octopus.originative.co.uk (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA05566 for ; Thu, 21 Jan 1999 14:16:06 -0800 (PST) (envelope-from paul@originative.co.uk) From: paul@originative.co.uk Received: by OCTOPUS with Internet Mail Service (5.5.1960.3) id ; Thu, 21 Jan 1999 21:58:51 -0000 Message-ID: To: mike@smith.net.au Cc: current@FreeBSD.ORG Subject: RE: KLD naming Date: Thu, 21 Jan 1999 21:58:50 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Mike Smith [mailto:mike@smith.net.au] > Sent: Thursday, January 21, 1999 8:25 PM > To: paul@originative.co.uk > Cc: current@FreeBSD.ORG > Subject: Re: KLD naming > ... > Ah, understood. I'd be inclined to use a suffix, so that our > prefix-based classification scheme still worked, eg. > > dev_ahc_Adaptec.ko > kern_descrypt_RSA.ko > > etc. Hmm, wouldn't this impose our kernel structure onto modules? This might not be desirable for external developers, they may just want to provide a single module rather than split the product into submodules that fit our categories. Why not allow SafeCo_firewall.ko rather than netif_foo_SafeCo.ko netproto_bar_SafeCo.ko etc. Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 14:17:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA05651 for freebsd-current-outgoing; Thu, 21 Jan 1999 14:17:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from charon.khoral.com (charon.khoral.com [209.75.155.97]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA05646 for ; Thu, 21 Jan 1999 14:17:04 -0800 (PST) (envelope-from steve@khoral.com) Received: from zen.alb.khoral.com by charon.khoral.com via smtpd (for hub.FreeBSD.ORG [204.216.27.18]) with SMTP; 21 Jan 1999 22:16:55 UT Received: from khoral.com Thu, 21 Jan 1999 15:16:52 -0700 (MST) From: Steve Jorgensen Message-Id: <199901212216.PAA28961@zen.alb.khoral.com> Subject: Current compile problem To: current@FreeBSD.ORG Date: Thu, 21 Jan 1999 15:16:51 -0700 (MST) X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I cvsup'ed current today, and am having a problem with the build. I am running current as of a couple of weeks ago, and during the buildworld, I get an error in the /usr/src/secure/lib/libcrypt directory, because the Makefile is refering to crypt.c crypt-md5.c md5c.c and crypt.3, but only crypt.c seems to exist. I double checked all the example cvsup files I could find, to make sure something hasn't changed in the crypto stuff, but it all looks fine to me. Did some files get missed in a commit? I also tried removing the non-existent files from the Makefile, but that errors out later with undefined symbols. I'm cvsup'ing src-all, src-crypto, src-secure, and src-eBones. Steve -- ----------------------------------------------------------- Steven Jorgensen steve@khoral.com steve@haunt.com ------------------------------+---------------------------- Khoral Research Inc. | PHONE: (505) 837-6500 6200 Uptown Blvd, Suite 200 | FAX: (505) 881-3842 Albuquerque, NM 87110 | URL: http://www.khoral.com/ ----------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 14:24:01 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA06166 for freebsd-current-outgoing; Thu, 21 Jan 1999 14:24:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (root.com [208.221.12.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA06152 for ; Thu, 21 Jan 1999 14:23:57 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id OAA19995; Thu, 21 Jan 1999 14:19:26 -0800 (PST) Message-Id: <199901212219.OAA19995@implode.root.com> To: Mike Smith cc: Geoff Buckingham , freebsd-current@FreeBSD.ORG Subject: Re: KVA/KVM shortages In-reply-to: Your message of "Thu, 21 Jan 1999 13:53:44 PST." <199901212153.NAA11404@dingo.cdrom.com> From: David Greenman Reply-To: dg@root.com Date: Thu, 21 Jan 1999 14:19:26 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> On tuesday I crashed a machine after it ran out of kvm. (dual PII 400 with >> 768MB RAM) poking about in the code adding: >> >> options "VM_KMEM_SIZE=(24*1024*1024)" >> options "VM_KMEM_SIZE_MAX=(128*1024*1024)" >> >> seems like a good way foward. Is it? > >>From what I can see, you shouldn't need to set VM_KMEM_SIZE_MAX unless >you're also setting VM_KMEM_SIZE_SCALE. > >I just committed a tweak that allows you to say: > > set kern.vm.kmem.size= > >at the loader prompt or in /boot/loader.rc to override the default >VM_KMEM_SIZE value. > >If anyone has any more of these tunables that can easily be enhanced >like this, please let me know. Is there a way from the boot loader that one can find out what options are available to be tuned? -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 14:33:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA06957 for freebsd-current-outgoing; Thu, 21 Jan 1999 14:33:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles236.castles.com [208.214.165.236]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA06951 for ; Thu, 21 Jan 1999 14:33:38 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA11601; Thu, 21 Jan 1999 14:29:49 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901212229.OAA11601@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: dg@root.com cc: Mike Smith , Geoff Buckingham , freebsd-current@FreeBSD.ORG Subject: Re: KVA/KVM shortages In-reply-to: Your message of "Thu, 21 Jan 1999 14:19:26 PST." <199901212219.OAA19995@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Jan 1999 14:29:49 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > >If anyone has any more of these tunables that can easily be enhanced > >like this, please let me know. > > Is there a way from the boot loader that one can find out what options > are available to be tuned? At the moment, the values are picked up on-demand by the kernel as it's initialising its state from the preprocessor defines, so there's no metainformation that can be extracted from the kernel to determine the tunables that are available. This could be improved in a number of ways - it would be achievable, for example, to have a macro: is_set = GET_KERN_TUNABLE(name, "description", variable); which exported "name" and "description" via a linker set which could be extracted by the loader. In the meantime, "help set tunables" inside the loader contains a list of the ones I've updated so far (the source for this is in sys/boot/common/help.common) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 14:39:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA07873 for freebsd-current-outgoing; Thu, 21 Jan 1999 14:39:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA07868 for ; Thu, 21 Jan 1999 14:39:03 -0800 (PST) (envelope-from hibma@skylink.it) Received: from henny.jrc.it (va-139.skylink.it [194.177.113.139]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id XAA31733; Thu, 21 Jan 1999 23:37:00 +0100 Received: from localhost (localhost.plazza.it [127.0.0.1]) by henny.jrc.it (8.9.1/8.8.7) with SMTP id AAA00481; Sat, 16 Jan 1999 00:43:28 +0100 (CET) (envelope-from hibma@skylink.it) Date: Sat, 16 Jan 1999 00:43:28 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@henny.plazza.it Reply-To: hibma@skylink.it To: Mike Smith cc: FreeBSD current mailing list Subject: Re: splash screen & xdm In-Reply-To: <199901151654.IAA00940@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This, no response on Ctrl-Alt-F1, happens as well when you kill the X server (because it is somehow stuck) so that the login prompt of xdm appears again. So I bet it has something to do with and is either located in syscons or in X. Nick > > It seems that if the splash screen image is not cleared (ie: press any > > key) before xdm starts up then once logged in the user is unable to > > switch to a vitual terminal (ie: ctrl-alt-f1 etc), and it just beeps > > when those keys are pressed. > > Solution? Putting the command kldunload splash_bmp before the line that > > loads xdm seems to work. Is this a bug or just the way things are? > > It's arguably a bug - the splash should be cleared before the vty > switch that X makes. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > FreeBSD USB Driver Development -- e-mail: n_hibma@freebsd.org home page: http://www.etla.net/~n_hibma/usb/usb.pl mailing list: usb-bsd@egroups.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 14:41:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA08185 for freebsd-current-outgoing; Thu, 21 Jan 1999 14:41:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from schizo.cdsnet.net (schizo.cdsnet.net [204.118.244.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA08177 for ; Thu, 21 Jan 1999 14:41:22 -0800 (PST) (envelope-from mrcpu@internetcds.com) Received: from localhost (mrcpu@localhost) by schizo.cdsnet.net (8.8.8/8.7.3) with SMTP id OAA22593 for ; Thu, 21 Jan 1999 14:36:25 -0800 (PST) Date: Thu, 21 Jan 1999 14:36:24 -0800 (PST) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: current@FreeBSD.ORG Subject: CVS tags to use? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The readme in /usr/share/examples hasn't been updated in a while... WHat tag should I be using now to track 3.0-current/3.1? (Not the 4.x branch). Right now, I have tag=., and I can't get a compilable kernel to save my life, problems in syscons. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 14:43:52 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA08421 for freebsd-current-outgoing; Thu, 21 Jan 1999 14:43:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA08416 for ; Thu, 21 Jan 1999 14:43:51 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id OAA29795 for ; Thu, 21 Jan 1999 14:41:35 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdc29793; Thu Jan 21 22:41:35 1999 Date: Thu, 21 Jan 1999 14:41:31 -0800 (PST) From: Julian Elischer To: current@FreeBSD.ORG Subject: Re: make world broken in /lib Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "me too" -DNOSECURE seems to help but it hasn't completed yet. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 14:54:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09541 for freebsd-current-outgoing; Thu, 21 Jan 1999 14:54:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from PigStuy.nws.net (nyc-ny77-45.ix.netcom.com [209.109.228.237]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09528 for ; Thu, 21 Jan 1999 14:54:13 -0800 (PST) (envelope-from spork@ix.netcom.com) Received: from localhost (spork@localhost) by PigStuy.nws.net (8.9.2/8.8.7) with ESMTP id RAA00317; Thu, 21 Jan 1999 17:52:16 -0500 (EST) (envelope-from spork@ix.netcom.com) X-Authentication-Warning: PigStuy.nws.net: spork owned process doing -bs Date: Thu, 21 Jan 1999 17:52:15 -0500 (EST) From: Spike X-Sender: spork@PigStuy.nws.net Reply-To: sporkl@ix.netcom.com To: Jaye Mathisen cc: current@FreeBSD.ORG Subject: Re: CVS tags to use? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 21 Jan 1999, Jaye Mathisen wrote: > > > The readme in /usr/share/examples hasn't been updated in a while... > > WHat tag should I be using now to track 3.0-current/3.1? (Not the 4.x > branch). > > Right now, I have tag=., and I can't get a compilable kernel to save my > life, problems in syscons. I have tag=RELENG_3, which gave me: FreeBSD PigStuy.nws.net 3.0-STABLE FreeBSD 3.0-STABLE #13: Thu Jan 21 17:45:26 EST 1999 spork@PigStuy.nws.net:/usr/src/sys/compile/MYKERNEL2 i386 3.0-RELEASE is 3_0_0_RELEASE. I just got bit by syscons- do you have the new syscons configuration? I needed to change: device sc0 at isa? port "IO_KBD" conflicts tty irq 1 vector scintr to: controller atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 device psm0 at isa? tty irq 12 device vga0 at isa? port ? conflicts device sc0 at isa? tty Or else both my psm and syscons drivers would scream various functions they couldn't find. Hope this solves your problem. -Spike Gronim sporkl@ix.netcom.com The majority only rules those who let them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 15:05:38 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10440 for freebsd-current-outgoing; Thu, 21 Jan 1999 15:05:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from post.mail.demon.net (post-11.mail.demon.net [194.217.242.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA10434 for ; Thu, 21 Jan 1999 15:05:36 -0800 (PST) (envelope-from root@scratch.demon.co.uk) Received: from [212.228.22.156] (helo=scratch.demon.co.uk) by post.mail.demon.net with smtp (Exim 2.10 #2) id 103TAB-00065c-00 for freebsd-current@FREEBSD.ORG; Thu, 21 Jan 1999 23:05:27 +0000 Message-ID: Date: Thu, 21 Jan 1999 23:03:45 +0000 To: freebsd-current@FreeBSD.ORG From: Tim Subject: PNP and new bootloader with ELF kernel MIME-Version: 1.0 X-Mailer: Turnpike (32) Version 4.00 <2bL8TQCIEWg0B+1EtXWvseZtDP> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I am currently running 3.0-RELEASE -current last updated 15th Jan (I think) and after a make world things were great kernel builds in an instant, computer boots faster etc etc. However I am unable to use help in the new bootloader, it sais the file boot.help cant be found and as such I do not know how to set up my PnP cards. Before I used -c at boot followed by pnp 1 enable etc., but this does not work now. How do I set up the CSN now as I get CSN 1 disabled and CSN 2 disabled on boot. Also I would like to remove the previous boot screen and boot straight into the new bootloader, so can a dos partition be configured to boot from the new bootloader Sorry if this has already been answered anywhere but I cant find it ! Is there any extensive documentation on the new ELF system ? Thanks for any help -- Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 15:26:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13553 for freebsd-current-outgoing; Thu, 21 Jan 1999 15:26:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13536 for ; Thu, 21 Jan 1999 15:26:29 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id SAA14936; Thu, 21 Jan 1999 18:26:17 -0500 (EST) (envelope-from luoqi) Date: Thu, 21 Jan 1999 18:26:17 -0500 (EST) From: Luoqi Chen Message-Id: <199901212326.SAA14936@lor.watermarkgroup.com> To: nrice@emu.sourcee.com, sgk@troutmask.apl.washington.edu Subject: Re: src/secure breaks world Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, Jan 21, 1999 at 12:26:04PM -0800, Steve Kargl wrote: > > cd /usr/src/secure/lib/libcrypt; /usr/obj/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED cleandepend; /usr/obj/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED all; /usr/obj/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -B install cleandir obj > > rm -f .depend /usr/obj/usr/src/secure/lib/libcrypt/GPATH /usr/obj/usr/src/secure/lib/libcrypt/GRTAGS /usr/obj/usr/src/secure/lib/libcrypt/GSYMS /usr/obj/usr/src/secure/lib/libcrypt/GTAGS > > make: don't know how to make crypt-md5.c. Stop > > *** Error code 2 > > 1 error > > > > Seem crypt-md5.c was moved into the attic, but the Makefile was updated. > > Do you mean "wasn't" updated? > > I am not sure that fixing the Makefile will resolve all the issues with the > recent libcrypt changes. I just finished a make world, here're the changes I made, Makefile.inc1: delete secure/lib/libcrypt from bootstrap library list lib/Makefile: delete secure/lib/libcrypt from SUBDIR list secure/lib/libcrypt: rename crypt.c to crypt-des.c -lq > -- > Regards, > Norman C. Rice, Jr. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 15:56:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA17411 for freebsd-current-outgoing; Thu, 21 Jan 1999 15:56:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA17405 for ; Thu, 21 Jan 1999 15:56:43 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:fe59el7y0RNXTWrz+dIwdm2+69zmCYl3@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id IAA11541; Fri, 22 Jan 1999 08:56:09 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id IAA01400; Fri, 22 Jan 1999 08:58:44 +0900 (JST) Message-Id: <199901212358.IAA01400@zodiac.mech.utsunomiya-u.ac.jp> To: Mark Murray cc: current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: keymaps In-reply-to: Your message of "Thu, 21 Jan 1999 20:40:24 +0200." <199901211840.UAA92062@greenpeace.grondar.za> References: <199901211605.BAA24511@zodiac.mech.utsunomiya-u.ac.jp> <199901211840.UAA92062@greenpeace.grondar.za> Date: Fri, 22 Jan 1999 08:58:43 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> 104 Pause Start screen saver (saver). >: >> The above assignments for the keycodes 1, 57, 70, 84 and 92 are >> compatible with many, if not all, existing keymaps. > >So far so good! > >> The assignments for 104 and 108 are new. > >104 (Pause?) does the "Backscroll" on my Libretto 70. I'd hate to >lose that. ScrollLock does "back scroll" too. You want both? Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 16:00:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA17789 for freebsd-current-outgoing; Thu, 21 Jan 1999 16:00:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA17781 for ; Thu, 21 Jan 1999 16:00:10 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40367>; Fri, 22 Jan 1999 10:59:10 +1100 Date: Fri, 22 Jan 1999 10:59:46 +1100 From: Peter Jeremy Subject: Problem loading 2.x kernel with new bootblocks [Re: Experiences with aout-to-elf and new bootblocks] To: dcs@newsguy.com Cc: current@FreeBSD.ORG Message-Id: <99Jan22.105910est.40367@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Splitting the thread... "Daniel C. Sobral" wrote: >> /boot/loader could load my 2.x kernel (although it happily handled > ^^^^^^^^^^ >You mean "could not", right? That's correct. >Is it kzipped, your 2.x kernel? (Is there any detail about it that >you think it is not relevant? :-) Further point: a GENERIC 2.2.6-RELEASE kernel boots successfully, so it is something about my kernel. The config file and boot messages are below. FWIW, boot -d still hangs, so it's dying fairly early. The kernel is not gzip'd - it's installed using `make install'. System details: PII-266 with IDE disks: primary master: wd0: dualboot (W95/FreeBSD 2.x) primary slave: ATAPI cdrom secondary master: wd2: FreeBSD 3.0 (not dangerously dedicated) secondary slave: not present The kernel has been built with gcc-2.8.1 -O2. My 2.x config file: machine "i386" cpu "I686_CPU" ident gsm_xt maxusers 20 options FAILSAFE #Be conservative config kernel root on wd0 options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options USER_LDT # user-level control of i386 LDT options SYSVSHM options SHMMAX=16777216 options SYSVSEM options SYSVMSG options "MD5" options DDB options KTRACE #kernel tracing options PERFMON options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options INET #InterNETworking pseudo-device ether pseudo-device loop pseudo-device bpfilter 4 pseudo-device tun 1 options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options "CD9660" #ISO 9660 Filesystem options FDESC #File descriptor filesystem options KERNFS #Kernel filesystem options MFS #Memory filesystem options MSDOSFS #MSDOS Filesystem options PROCFS #Process filesystem pseudo-device pty 256 pseudo-device speaker pseudo-device log pseudo-device gzip # Exec gzipped a.out's pseudo-device vn controller isa0 options "AUTO_EOI_1" controller pci0 controller pnp0 device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr options MAXCONS=12 # number of virtual consoles device npx0 at isa? port "IO_NPX" flags 0x1 irq 13 vector npxintr controller wdc0 at isa? port "IO_WD1" flags 0x80ff80ff bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 disable drive 1 controller wdc1 at isa? disable port "IO_WD2" bio irq 15 vector wdintr disk wd2 at wdc1 disable drive 0 disk wd3 at wdc1 disable drive 1 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM device wcd0 #IDE CD-ROM controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 disk fd1 at fdc0 disable drive 1 device lpt0 at isa? port? tty irq 7 vector lptintr device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr device apm0 at isa? # Advanced Power Management device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device pcm0 at isa? port ? tty irq 5 drq 1 flags 0x13 vector pcmintr device pca0 at isa? port IO_TIMER1 tty device joy0 at isa? port "IO_GAME" device tx0 options "CLK_USE_I586_CALIBRATION" The boot messages: Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2.6-RELEASE #1: Tue Dec 1 07:58:15 EST 1998 root@gsmx07.alcatel.com.au:/usr/src/sys/compile/gsmx CPU: Pentium Pro (267.32-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x633 Stepping=3 Features=0x80f9ff real memory = 67108864 (65536K bytes) avail memory = 63406080 (61920K bytes) Probing for devices on PCI bus 0: chip0 rev 3 on pci0:0:0 chip1 rev 3 on pci0:1:0 chip2 rev 1 on pci0:7:0 chip3 rev 1 on pci0:7:1 chip4 rev 1 int d irq 11 on pci0:7:2 chip5 rev 1 on pci0:7:3 vga0 rev 0 int a irq 10 on pci0:9:0 tx0 rev 6 int a irq 9 on pci0:10:0 tx0: address 00:e0:29:24:34:1f, type SMC9432TX, phy QS6612, Auto-Neg 10Mbps Probing for devices on PCI bus 1: Probing for PnP devices: CSN 1 Vendor ID: CTL00f0 [0xf0008c0e] Serial 0xffffffff pcm1 (SB16pnp sn 0xffffffff) at 0x220 irq 5 drq 1 flags 0x13 id 14 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <12 virtual consoles, flags=0x0> lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A pcm0 not found at 0xffffffff pca0 on motherboard pca0: PC speaker audio driver wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff80ff on isa wdc0: unit 0 (wd0): , 32-bit, multi-block-16 wd0: 6187MB (12672450 sectors), 13410 cyls, 15 heads, 63 S/T, 512 B/S wdc0: unit 1 (atapi): , removable, accel, dma, iordis wcd0: 1723KB/sec, 256KB cache, audio play, 16 volume levels, ejectable tray wcd0: no disc inside, unlocked wcd0: mode 2 form 1(XA) 2, multisession, CD-DA read stream, comb. rw, rw corr., ISRC, UPC wdc1 at 0x170-0x177 irq 15 flags 0x80ff80ff on isa wdc1: unit 0 (wd2): , 32-bit, multi-block-16 wd2: 1222MB (2503872 sectors), 2484 cyls, 16 heads, 63 S/T, 512 B/S fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in npx0 flags 0x1 on motherboard npx0: INT 16 interface apm0 on isa apm: found APM BIOS version 1.1 joy0 at 0x201 on isa joy0: joystick Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 16:08:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20621 for freebsd-current-outgoing; Thu, 21 Jan 1999 16:08:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA20607 for ; Thu, 21 Jan 1999 16:08:39 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40377>; Fri, 22 Jan 1999 11:07:37 +1100 Date: Fri, 22 Jan 1999 11:08:12 +1100 From: Peter Jeremy Subject: Booting from 2nd IDE [Re: Experiences with aout-to-elf and new bootblocks] To: dcs@newsguy.com, tmb@rcru.rl.ac.uk Cc: current@FreeBSD.ORG Message-Id: <99Jan22.110737est.40377@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel C. Sobral" wrote: >Well, kind of. You "hard code" the name wd2 in your kernel >configuration file. [...] Ie, s/wd2/wd1/ > in your kernel configuration file (and rebuild :). It was wd0 (the generic). Making it wd2 didn't help. Mark Blackman wrote: >FWIW, I've done it under 2.2.7 by > >1) installing booteasy on both wd0 *AND* wd2 >2) altering the boot.config to > 1:wd(2,a)kernel This works for an a.out 3.0 kernel, but the old bootloader can't handle ELF kernels, so this isn't a usable solution. >3) compiling above kernel with > config kernel root on wd2 This made no difference. Since typing on a keyboard is easier than opening the box, I wrote the following kludge. It builds a bitmap of IDE devices as it probes them and then counts active IDE devices to work out the actual unit number. Index: i386/autoconf.c =================================================================== RCS file: /home/CVSROOT/./src/sys/i386/i386/autoconf.c,v retrieving revision 1.110 diff -u -r1.110 autoconf.c --- autoconf.c 1998/10/26 07:05:34 1.110 +++ autoconf.c 1999/01/21 23:18:18 @@ -433,6 +433,10 @@ #define FDMAJOR 2 #define FDUNITSHIFT 6 +/* KLUDGE for bios handling of multiple devices */ +#define WDMAJOR 0 +int wd_mask = 0; /* mask of WD devices found during probe */ + /* * Attempt to find the device from which we were booted. * If we can do so, and not instructed not to do so, @@ -467,6 +471,18 @@ slice = COMPATIBILITY_SLICE; part = RAW_PART; mindev = unit << FDUNITSHIFT; + } else if (majdev == WDMAJOR) { + /* + * XXX kludge to handle holes in numbering + */ + for (part = 0, mindev = unit; part < 32 && mindev >= 0; part++) + if (wd_mask & (1 << part)) + mindev--; + if (mindev == -1) + unit = part - 1; + + part = B_PARTITION(bootdev); + mindev = dkmakeminor(unit, slice, part); } else { part = B_PARTITION(bootdev); mindev = dkmakeminor(unit, slice, part); Index: isa/wd.c =================================================================== RCS file: /home/CVSROOT/./src/sys/i386/isa/wd.c,v retrieving revision 1.186 diff -u -r1.186 wd.c --- wd.c 1999/01/17 05:46:24 1.186 +++ wd.c 1999/01/21 23:18:18 @@ -223,6 +223,8 @@ static struct buf rwdbuf[NWD]; /* buffers for raw IO */ #endif +extern int wd_mask; /* This is a KLUDGE */ + static int wdprobe(struct isa_device *dvp); static int wdattach(struct isa_device *dvp); static void wdustart(struct disk *du); @@ -551,6 +553,8 @@ DEVSTAT_NO_ORDERED_TAGS, DEVSTAT_TYPE_DIRECT | DEVSTAT_TYPE_IF_IDE); + /* KLUDGE: mark drive as present */ + wd_mask |= 1 << lunit; } else { free(du, M_TEMP); wddrives[lunit] = NULL; ------------- This successfully allows me to boot from wd2. I agree that it doesn't address the general problem (in particular, it can't handle the case where the BIOS doesn't see a device that the kernel probe does see, and doesn't support SCSI). Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 16:27:39 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA24605 for freebsd-current-outgoing; Thu, 21 Jan 1999 16:27:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles236.castles.com [208.214.165.236]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA24576 for ; Thu, 21 Jan 1999 16:27:32 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA12213; Thu, 21 Jan 1999 16:23:30 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901220023.QAA12213@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Jeremy cc: dcs@newsguy.com, current@FreeBSD.ORG Subject: Re: Problem loading 2.x kernel with new bootblocks [Re: Experiences with aout-to-elf and new bootblocks] In-reply-to: Your message of "Fri, 22 Jan 1999 10:59:46 +1100." <99Jan22.105910est.40367@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Jan 1999 16:23:29 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The kernel has been built with gcc-2.8.1 -O2. Please rebuild with the system compiler and -O at most. We're hard-pressed enough as it is to support our own software without introducing complete unknowns into the equation. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 16:44:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA27153 for freebsd-current-outgoing; Thu, 21 Jan 1999 16:44:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA27145 for ; Thu, 21 Jan 1999 16:44:14 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.9.1) id QAA45843 for freebsd-current@freebsd.org; Thu, 21 Jan 1999 16:45:22 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199901220045.QAA45843@troutmask.apl.washington.edu> Subject: PLEASE: back out recent crypt breakage To: freebsd-current@FreeBSD.ORG Date: Thu, 21 Jan 1999 16:45:22 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The recent changes to src/secure/libcrypt have severely broken "make buildworld". Can some please back out the recent changes, and give to the committer named "brandon" a pointed hat? PS: This makes my attempt to test Matt's VM change rather difficult. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 16:44:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA27169 for freebsd-current-outgoing; Thu, 21 Jan 1999 16:44:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fw.bby.com.au (ns.bby.com.au [192.83.119.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA27146 for ; Thu, 21 Jan 1999 16:44:16 -0800 (PST) (envelope-from gnb@itga.com.au) Received: (from daemon@localhost) by fw.bby.com.au (8.8.8/8.6.9) id LAA12220; Fri, 22 Jan 1999 11:43:58 +1100 (EST) Received: from lightning.itga.com.au(192.168.71.20) via SMTP by fw.bby.com.au, id smtpd012218; Fri Jan 22 00:43:56 1999 Received: from lightning (lightning [192.168.71.20]) by lightning.itga.com.au (8.9.1a/8.9.1) with ESMTP id LAA22437; Fri, 22 Jan 1999 11:43:56 +1100 (EST) Message-Id: <199901220043.LAA22437@lightning.itga.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: Kazutaka YOKOTA Cc: current@FreeBSD.ORG Subject: Re: keymaps In-reply-to: Your message of Fri, 22 Jan 1999 01:05:22 +0900. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 22 Jan 1999 11:43:56 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG my vote: A version of the standard keymap with CapsLock and LeftCtl functions swapped so the control key is under my left finger like God intended! Greg, home of us.iso-lock-ctl.kbd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 16:59:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA28549 for freebsd-current-outgoing; Thu, 21 Jan 1999 16:59:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA28540 for ; Thu, 21 Jan 1999 16:59:17 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id TAA15433 for current@freebsd.org; Thu, 21 Jan 1999 19:59:07 -0500 (EST) (envelope-from luoqi) Date: Thu, 21 Jan 1999 19:59:07 -0500 (EST) From: Luoqi Chen Message-Id: <199901220059.TAA15433@lor.watermarkgroup.com> To: current@FreeBSD.ORG Subject: Trouble executing from NFS with latest 4.0-current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Execute anything from NFS would result in an "Input/output error", but if I do a hexdump of the executable first, the execution would be successful. If I reverse the order, i.e., execute first then hexdump, execution would fail and hexdump would hang at "pgtblk". No problem with FFS. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 17:08:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA29969 for freebsd-current-outgoing; Thu, 21 Jan 1999 17:08:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA29946 for ; Thu, 21 Jan 1999 17:08:42 -0800 (PST) (envelope-from dawes@rf900.physics.usyd.edu.au) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.9.1a/8.9.1) id MAA13650; Fri, 22 Jan 1999 12:06:34 +1100 (EST) Message-ID: <19990122120633.A13400@rf900.physics.usyd.edu.au> Date: Fri, 22 Jan 1999 12:06:33 +1100 From: David Dawes To: =?iso-8859-1?Q?S=F8ren_Schmidt?= Cc: current@FreeBSD.ORG Subject: Re: Promise FastTrack PCI IDE controller References: <19990121234651.F5377@rf900.physics.usyd.edu.au> <199901211306.OAA16593@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.93.2i In-Reply-To: =?iso-8859-1?Q?=3C199901211306=2EOAA16593=40freebsd=2Edk=3E=3B_from_S=F8?= =?iso-8859-1?Q?ren_Schmidt_on_Thu=2C_Jan_21=2C_1999_at_02:06:22PM_+0100?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 21, 1999 at 02:06:22PM +0100, Søren Schmidt wrote: >It seems David Dawes wrote: >> >> That didn't improve things, but with the patch I got lots of messages >> like the following (for a disk attached to the onboard PIIX4): >> >> wd1: DMA failure, DMA status 0 >> >> (The box isn't SMP.) > >Hmm, and it is an uptodate -current system ?? >Just use this part then: It might have been related to some of the other changes I had made. With a new clean wd.c and your patch I don't get the "wd1: DMA failure, DMA status 0" messages. The Promise card doesn't behave any differently though. >> >I also run the card without its BIOS, as that tends to get in the way. >> >I think the FastTrack is just an Ultra/33 with another BIOS chip on it. >> >> I'll try pulling the BIOS tomorrow. We didn't get this card for it's >> RAID features anyway. > >That helped me in a lot if situations, but performance wont be as good >as we seem not to initialize the chip(s)... When I remove the BIOS it works OK. The initialisation is different though. For the drives on the PIIX4 I get: wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 wd0: 16124MB (33022080 sectors), 32760 cyls, 16 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0007, dmamword = 0007, apio = 0003, udma = 0407 for the ones on the Promise card I get: wdc2 at 0xeff0-0xeff7 flags 0xa0ffa0ff on isa wdc2: unit 0 (wd4): , DMA, 32-bit, multi-block-16 wd4: 16124MB (33022080 sectors), 32760 cyls, 16 heads, 63 S/T, 512 B/S wd4: ATA INQUIRE valid = 0007, dmamword = 0407, apio = 0003, udma = 0007 I also get the following warning, but only for the secondary controller on the Promise card: ide_pci: generic_dmainit efa8:0: warning, IDE controller timing not set and in the PCI probe section: ide_pci: busmaster 0 status: 60 from port: 0000ef82 ide_pci: ide0:0 has been configured for DMA by BIOS ide_pci: ide0:1 has been configured for DMA by BIOS ... ide_pci: busmaster 1 status: 00 from port: 0000ef8a The performance isn't as good, as you say. For one of these disks on the PIIX4 I get about 12 MByte/s for a large (1GB) sequential read from the raw device. I only get about 4 MByte/s for one of the same disks on the Promise controller. I presume that's because it isn't initialised to the fastest DMA mode? The performance is adequate for our needs though, so removing the BIOS is a workable solution. Thanks. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 18:04:59 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08715 for freebsd-current-outgoing; Thu, 21 Jan 1999 18:04:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA08705 for ; Thu, 21 Jan 1999 18:04:56 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id SAA46934; Thu, 21 Jan 1999 18:04:45 -0800 (PST) (envelope-from dillon) Date: Thu, 21 Jan 1999 18:04:45 -0800 (PST) From: Matthew Dillon Message-Id: <199901220204.SAA46934@apollo.backplane.com> To: Luoqi Chen Cc: current@FreeBSD.ORG Subject: Re: Trouble executing from NFS with latest 4.0-current References: <199901220059.TAA15433@lor.watermarkgroup.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Execute anything from NFS would result in an "Input/output error", but if I do :a hexdump of the executable first, the execution would be successful. If I :reverse the order, i.e., execute first then hexdump, execution would fail and :hexdump would hang at "pgtblk". No problem with FFS. : :-lq Hmmm. It's working fine for me between two FreeBSD boxes. Do a cvs diff against your entire /usr/src/sys tree first to make sure you are up to date on all the patches. If it's still broken, we need to identify whether it is NFSV2, V3, and whether the problem is related to FreeBSD<->FreeBSD or FreeBSD w/ some other platform. Also any mount options, such as read and write buffer settings, etc... -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 19:39:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA13846 for freebsd-current-outgoing; Thu, 21 Jan 1999 19:39:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA13837; Thu, 21 Jan 1999 19:39:19 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id TAA37867; Thu, 21 Jan 1999 19:38:59 -0800 (PST) To: "Gary Palmer" cc: current@FreeBSD.ORG Subject: Re: More make release woes In-reply-to: Your message of "Thu, 21 Jan 1999 13:16:17 EST." <7047.916942577@gjp.erols.com> Date: Thu, 21 Jan 1999 19:38:58 -0800 Message-ID: <37863.916976338@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's time to do a functional split on boot.flp / kern+mfsroot.flp builds. Hmmm. What to axe.. Let me thwap on this a bit over the weekend. :) - Jordan > > Looks like the Alpha AXP boot floppy has bitten the dust also: > > Making the regular boot floppy. > Compressing doc files... > disklabel: ioctl DIOCWLABEL: Operation not supported by device > Warning: Block size restricts cylinders per group to 4. > Warning: 2880 sector(s) in last cylinder unallocated > /dev/rvn0c: 2880 sectors in 1 cylinders of 1 tracks, 5760 sectors > 1.4MB in 1 cyl groups (4 c/g, 11.25MB/g, 192 i/g) > super-block backups (for fsck -b #) at: > 32, > cpio: write error: No space left on device > *** Error code 1 (ignored) > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > > > Sigh. Oh well. I was hoping to get a SNAP out with all the changes > Matt did. Guess not. > > Gary > -- > Gary Palmer FreeBSD Core Team Member > FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 21:27:01 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA18369 for freebsd-current-outgoing; Thu, 21 Jan 1999 21:27:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oreo.adsu.bellsouth.com (oreo.adsu.bellsouth.com [205.152.173.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA18360 for ; Thu, 21 Jan 1999 21:26:56 -0800 (PST) (envelope-from ck@oreo.adsu.bellsouth.com) Received: (from ck@localhost) by oreo.adsu.bellsouth.com (8.9.1/8.9.1) id VAA79757 for freebsd-current@freebsd.org; Thu, 21 Jan 1999 21:23:52 -0500 (EST) (envelope-from ck) Date: Thu, 21 Jan 1999 21:23:52 -0500 From: Christian Kuhtz To: freebsd-current@FreeBSD.ORG Subject: top broken - VM sideeffect? Message-ID: <19990121212352.D79573@oreo.adsu.bellsouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Looks like top's broken. It no longer shows swap space status on 4.0-CURRENT. Side effect of the VM update? -- "Logic is a little bird, sitting in a tree; that smells *awful*." -- /usr/bin/fortune [Disclaimer: I speak for myself and my views are my own and not in any way to be construed as the views of BellSouth Corporation. ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 21:28:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA18750 for freebsd-current-outgoing; Thu, 21 Jan 1999 21:28:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dns.MexComUSA.NET (cm4094.cableco-op.com [208.138.40.94]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA18740 for ; Thu, 21 Jan 1999 21:28:12 -0800 (PST) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (cm4094.cableco-op.com [208.138.40.94]) by dns.MexComUSA.NET (8.9.2/8.9.1) with ESMTP id TAA74684 for ; Thu, 21 Jan 1999 19:18:11 -0800 (PST) (envelope-from eculp@MexComUSA.net) Message-ID: <36A7EDF3.F0A433EC@MexComUSA.net> Date: Thu, 21 Jan 1999 19:18:11 -0800 From: Edwin Culp Organization: Mexico Communicates, S.C. X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Make Release this afternoon. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What is the trick to get past this problem? Or can a release not be made as before? Thanks a lot, ed disklabel: ioctl DIOCWLABEL: Operation not supported by device Warning: Block size restricts cylinders per group to 4. Warning: 2880 sector(s) in last cylinder unallocated /dev/rvn0c: 2880 sectors in 1 cylinders of 1 tracks, 5760 sectors 1.4MB in 1 cyl groups (4 c/g, 11.25MB/g, 32 i/g) super-block backups (for fsck -b #) at: 32, /mnt: write failed, file system is full cpio: write error: No space left on device *** Error code 1 Stop. *** Error code 1 (ignored) *** Error code 1 Stop. *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 21:28:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA18759 for freebsd-current-outgoing; Thu, 21 Jan 1999 21:28:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA18738 for ; Thu, 21 Jan 1999 21:28:12 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40356>; Fri, 22 Jan 1999 14:44:56 +1100 Date: Fri, 22 Jan 1999 14:45:33 +1100 From: Peter Jeremy Subject: Re: Problem loading 2.x kernel with new bootblocks To: mike@smith.net.au Cc: current@FreeBSD.ORG Message-Id: <99Jan22.144456est.40356@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: >> The kernel has been built with gcc-2.8.1 -O2. > >Please rebuild with the system compiler and -O at most. It makes no difference. The kernel loads and runs happily from the old bootloader, but crashes with /boot/loader. (I disabled my gcc-2.8.1, changed make.conf to -O, re-ran config; make depend; make; make install). Something that `fell off' my previous posting (it was implied in the context of my original posting): Both disks have Booteasy installed. wd0 has the old bootblocks (from 2.2.6-RELEASE) and FreeBSD 2.x installed on slice 2. wd2 has the new bootblocks and 3.0-current built from CTM 'cvs-cur 4996' occupying all of slice 1 (which is all of the disk). The boot sequences are: disk0 booteasy offers: W95, FreeBSD, Disk1: - select FreeBSD and 2.x boots successfully - select `disk1' and the disk1 booteasy offers: BSD, disk0 Select BSD and the new /boot/loader comes up. If I let it continue, I wind up with the 3.0 (customised, ELF) kernel booting successfully. If I abort /boot/loader's autostart (giving me a prompt), then (as per Peter Wemm's elfday tutorial) issue the commands: set currdev=disk1s2a load /kernel boot -s the system displays garbage on the screen and doesn't respond to anything gentler than the reset button. If I load the GENERIC 2.2.6-RELEASE kernel, ("load /kernel.GENERIC" above) then it works. Any suggestions as to my next step? Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 21:28:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA18825 for freebsd-current-outgoing; Thu, 21 Jan 1999 21:28:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA18760 for ; Thu, 21 Jan 1999 21:28:15 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 103YQ8-0003K7-00; Thu, 21 Jan 1999 21:42:12 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id VAA83421; Thu, 21 Jan 1999 21:40:02 -0700 (MST) Message-Id: <199901220440.VAA83421@harmony.village.org> To: Gregory Bond Subject: Re: keymaps Cc: Kazutaka YOKOTA , current@FreeBSD.ORG In-reply-to: Your message of "Fri, 22 Jan 1999 11:43:56 +1100." <199901220043.LAA22437@lightning.itga.com.au> References: <199901220043.LAA22437@lightning.itga.com.au> Date: Thu, 21 Jan 1999 21:40:02 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199901220043.LAA22437@lightning.itga.com.au> Gregory Bond writes: : my vote: A version of the standard keymap with CapsLock and LeftCtl : functions swapped so the control key is under my left finger like : God intended! What's wrong with us.unix.kbd? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 21:30:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA19344 for freebsd-current-outgoing; Thu, 21 Jan 1999 21:30:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA19321 for ; Thu, 21 Jan 1999 21:30:48 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id VAA47615; Thu, 21 Jan 1999 21:30:37 -0800 (PST) (envelope-from dillon) Date: Thu, 21 Jan 1999 21:30:37 -0800 (PST) From: Matthew Dillon Message-Id: <199901220530.VAA47615@apollo.backplane.com> To: Christian Kuhtz Cc: freebsd-current@FreeBSD.ORG Subject: Re: top broken - VM sideeffect? References: <19990121212352.D79573@oreo.adsu.bellsouth.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :Looks like top's broken. It no longer shows swap space status on 4.0-CURRENT. :Side effect of the VM update? Yes. I've only made pstat -s ( aka swapinfo ) work so far. systat -swap is also broken. Both are on my TODO list. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 21:32:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA19707 for freebsd-current-outgoing; Thu, 21 Jan 1999 21:32:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA19652 for ; Thu, 21 Jan 1999 21:32:04 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id QAA21641; Fri, 22 Jan 1999 16:01:51 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.2/8.9.0) id QAA08230; Fri, 22 Jan 1999 16:01:27 +1030 (CST) Date: Fri, 22 Jan 1999 16:01:27 +1030 From: Greg Lehey To: Christian Kuhtz Cc: freebsd-current@FreeBSD.ORG Subject: Re: top broken - VM sideeffect? Message-ID: <19990122160127.A5697@freebie.lemis.com> References: <19990121212352.D79573@oreo.adsu.bellsouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990121212352.D79573@oreo.adsu.bellsouth.com>; from Christian Kuhtz on Thu, Jan 21, 1999 at 09:23:52PM -0500 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 21 January 1999 at 21:23:52 -0500, Christian Kuhtz wrote: > > Looks like top's broken. It no longer shows swap space status on 4.0-CURRENT. > Side effect of the VM update? Yup. Matt announced it. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 21:32:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA19718 for freebsd-current-outgoing; Thu, 21 Jan 1999 21:32:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA19702 for ; Thu, 21 Jan 1999 21:32:24 -0800 (PST) (envelope-from rock@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.2/1999010400) with ESMTP id DAA02872 for ; Fri, 22 Jan 1999 03:56:37 +0100 (CET) Received: from wurzelausix (wurzelausix.cs.uni-sb.de [134.96.247.1]) by cs.uni-sb.de (8.9.2/1999010400) with ESMTP id DAA28341 for ; Fri, 22 Jan 1999 03:56:36 +0100 (CET) Received: from vodix.aremorika (vodix [134.96.247.43]) by wurzelausix (8.9.1/wjp/19980821) with ESMTP id DAA16102 for ; Fri, 22 Jan 1999 03:56:35 +0100 (CET) From: "D. Rock" Received: by vodix.aremorika; Fri, 22 Jan 1999 03:56:35 +0100 (MET) Date: Fri, 22 Jan 1999 03:56:35 +0100 (MET) Message-Id: <199901220256.DAA04587@vodix.aremorika> To: current@FreeBSD.ORG Subject: libexpcrypt? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, after todays build I wasn't able to login: Instead of installing libdescrypt.* and linking libcrypt.* to libdescrypt.* I suddenly got libexpcrypt.* files, with no DES code in. It seems the international secure distribution isn't in sync any more. I am missing /usr/src/secure/lib/libcrypt/crypt-des.c I have also noticed the major number in the library bump. Is it safe for the transition period still link libcrypt.so.3 to libdescrypt.so.2? Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 21:41:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA21035 for freebsd-current-outgoing; Thu, 21 Jan 1999 21:41:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA21029 for ; Thu, 21 Jan 1999 21:41:26 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id UAA47389; Thu, 21 Jan 1999 20:39:21 -0800 (PST) (envelope-from dillon) Date: Thu, 21 Jan 1999 20:39:21 -0800 (PST) From: Matthew Dillon Message-Id: <199901220439.UAA47389@apollo.backplane.com> To: "D. Rock" Cc: current@FreeBSD.ORG Subject: Re: NFS v3 issue References: <36A711FD.85F65545@cs.uni-sb.de> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :With NFS v3 there seem still to be some open issues. :Im running the latest (4.0)-current with the new vm/NFS changes. :While I haven't found any problems with NFSv2 so far, v3 still seems to make :trouble. : :I noticed the error some months ago, while my /usr/obj was NFS mounted, and :a build failed while making termcap.db. Today, I gave it another try. :I copied /usr/src/share/termcap into an NFS mounted directory and did :a "make". I compared the output of termcap.db with the one build on the local :drive. :While the NFS mounted one was only 1077760 bytes in size, the correct :size (from the local build) should be 1245184 bytes. I did the build :several times, everytime I got the same values. I then remounted the :direcory NFSv2. Now the build produced the right file (in size and content). : :The NFS Server is a Solaris 7 machine. : :Can anyone else confirm this error? : :Daniel I can't help you here, but I want to make sure: The problems you are having are the same problems you were having a few months ago? ( I want to make sure I haven't introduced new problems in -4.x, and if I have to fix them ASAP! ). -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 21:41:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA21098 for freebsd-current-outgoing; Thu, 21 Jan 1999 21:41:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles327.castles.com [208.214.167.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA21056 for ; Thu, 21 Jan 1999 21:41:32 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id VAA13835; Thu, 21 Jan 1999 21:37:34 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901220537.VAA13835@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Robert V. Baron" cc: Mike Smith , Geoff Buckingham , freebsd-current@FreeBSD.ORG Subject: Re: KVA/KVM shortages In-reply-to: Your message of "21 Jan 1999 22:05:23 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Jan 1999 21:37:34 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith writes: > > > I just committed a tweak that allows you to say: > > > > set kern.vm.kmem.size= > > > > at the loader prompt or in /boot/loader.rc to override the default > > VM_KMEM_SIZE value. > > > > If anyone has any more of these tunables that can easily be enhanced > > like this, please let me know. > > > How about all the parameters that are assigned in param.c? Why not > make them all tweakable in the loader.rc, rather than having to patch > the kernel. Because they're not all used in fashions that either make tuning them really desirable, or easy. I looked at all of them and decided that most weren't actually really candidates for that sort of hackery. > Actually, thinking about this a little more ... > The loader knows where all symbols are in memory. Why not a general > mechanism to let you reassign the value of any "variable" used in > the kernel or in a module. I presume that the loader allocates bss > for the kernel and each module as it loads it. So I presume I can > assign a value to a variable that would ordinarily take on a 0 > value, too. Because most of them are initialised at runtime from preprocessor defines, so tweaking their initial values wouldn't save anything (you'd have to hack the code anyway to have it not override a non-zero initial value). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 21:42:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA21186 for freebsd-current-outgoing; Thu, 21 Jan 1999 21:42:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA21172 for ; Thu, 21 Jan 1999 21:41:58 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id VAA15941; Thu, 21 Jan 1999 21:53:13 -0500 (EST) (envelope-from luoqi) Date: Thu, 21 Jan 1999 21:53:13 -0500 (EST) From: Luoqi Chen Message-Id: <199901220253.VAA15941@lor.watermarkgroup.com> To: dillon@apollo.backplane.com, luoqi@watermarkgroup.com Subject: Re: Trouble executing from NFS with latest 4.0-current Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :Execute anything from NFS would result in an "Input/output error", but if I do > :a hexdump of the executable first, the execution would be successful. If I > :reverse the order, i.e., execute first then hexdump, execution would fail and > :hexdump would hang at "pgtblk". No problem with FFS. > : > :-lq > > Hmmm. It's working fine for me between two FreeBSD boxes. Do a > cvs diff against your entire /usr/src/sys tree first to make > sure you are up to date on all the patches. > > If it's still broken, we need to identify whether it is NFSV2, V3, > and whether the problem is related to FreeBSD<->FreeBSD or FreeBSD > w/ some other platform. Also any mount options, such as read and > write buffer settings, etc... > > -Matt > > Matthew Dillon > > Sorry, it was an outdated nfs.ko, please disregard the report. I had some trouble with making world because of the libcrypt stuff and I'm still struggling to get everything installed right. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 21:48:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA22160 for freebsd-current-outgoing; Thu, 21 Jan 1999 21:48:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Terry.Dorm10.NCTU.edu.tw (Terry.Dorm10.NCTU.edu.tw [140.113.122.99]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA22031 for ; Thu, 21 Jan 1999 21:47:33 -0800 (PST) (envelope-from ijliao@Terry.Dorm10.NCTU.edu.tw) Received: (from ijliao@localhost) by Terry.Dorm10.NCTU.edu.tw (8.9.2/8.9.2) id MAA02416; Fri, 22 Jan 1999 12:22:26 +0800 (CST) (envelope-from ijliao) Date: Fri, 22 Jan 1999 12:22:26 +0800 From: Ying-Chieh Liao To: Tim Cc: freebsd-current@FreeBSD.ORG Subject: Re: PNP and new bootloader with ELF kernel Message-ID: <19990122122226.A2328@terry.dragon2.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from "Tim" on Thu, Jan 21, 1999 at 23:03:45 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 21, 1999 at 23:03:45 +0000, Tim wrote: > How do I set up the CSN now as I get CSN 1 disabled and CSN 2 disabled > on boot. you can put this pnp information in /kernel.config and, in your /boot/boot.conf, put load /kernel load -t userconfig_script /kernel.config boot this works fine on my box > Also I would like to remove the previous boot screen and boot straight > into the new bootloader, so can a dos partition be configured to boot > from the new bootloader just execute the following command : disklabel -B -b /boot/boot1 -s /boot/boot2 is which you boot from ex : disklabel -B -b /boot/boot1 -s /boot/boot2 wd0s1 -- mailto:ijliao@dragon2.net?subject="send pgp key" to get my pgp public key key finger print : FA 38 7E 91 FA 22 FA F6 63 04 E3 B5 A1 9F 0C CD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 22:01:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA23945 for freebsd-current-outgoing; Thu, 21 Jan 1999 22:01:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from daphne.bogus (dialup34.black-hole.com [206.145.13.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA23934 for ; Thu, 21 Jan 1999 22:00:46 -0800 (PST) (envelope-from hank@black-hole.com) Received: from localhost (hank@localhost) by daphne.bogus (8.9.1/8.8.8) with SMTP id XAA59405 for ; Thu, 21 Jan 1999 23:42:20 -0600 (CST) (envelope-from hank@black-hole.com) X-Authentication-Warning: daphne.bogus: hank owned process doing -bs Date: Thu, 21 Jan 1999 23:42:20 -0600 (CST) From: Henry Miller X-Sender: hank@daphne.bogus cc: current@FreeBSD.ORG Subject: Re: CVS tags to use? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 21 Jan 1999, Jaye Mathisen wrote: > > The readme in /usr/share/examples hasn't been updated in a while... > > WHat tag should I be using now to track 3.0-current/3.1? (Not the 4.x > branch). > > Right now, I have tag=., and I can't get a compilable kernel to save my > life, problems in syscons. RELENG_3 Related to the above question though, is when should I drop my subscription to current, and move to stable (the mailing lists) I presume that for a while the current mailing list will be more relavent as people on it will at least remember similear problems, while the -stable list will have 2.2.x users who have never seen our porblems. Gradually this would change though, as the 4.x path moves beyond the 3.x track in significant ways. (Already a couple important changes are in the 4.x track) I guess the big questions is where do I look for 3.x Head-up messages. -- http://www.black-hole.com/users/henrymiller/ hank@black-hole.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 22:01:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA23963 for freebsd-current-outgoing; Thu, 21 Jan 1999 22:01:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from daphne.bogus (dialup34.black-hole.com [206.145.13.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA23944 for ; Thu, 21 Jan 1999 22:00:59 -0800 (PST) (envelope-from hank@black-hole.com) Received: from localhost (hank@localhost) by daphne.bogus (8.9.1/8.8.8) with SMTP id XAA59398; Thu, 21 Jan 1999 23:38:19 -0600 (CST) (envelope-from hank@black-hole.com) X-Authentication-Warning: daphne.bogus: hank owned process doing -bs Date: Thu, 21 Jan 1999 23:38:19 -0600 (CST) From: Henry Miller X-Sender: hank@daphne.bogus To: Gregory Bond cc: Kazutaka YOKOTA , current@FreeBSD.ORG Subject: Re: keymaps In-Reply-To: <199901220043.LAA22437@lightning.itga.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 22 Jan 1999, Gregory Bond wrote: > my vote: A version of the standard keymap with CapsLock and LeftCtl functions > swapped so the control key is under my left finger like God intended! My vote is both of the above. I've never found a use for CapsLock, but LeftCtl is important enough that I wouldn't mind it duplicated. Most people I know are like this. (Yes of course there needs to be a way to get at capslock for those who really need it) -- http://www.black-hole.com/users/henrymiller/ hank@black-hole.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 22:08:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA24625 for freebsd-current-outgoing; Thu, 21 Jan 1999 22:08:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA24613 for ; Thu, 21 Jan 1999 22:08:16 -0800 (PST) (envelope-from martti.kuparinen@lmf.ericsson.se) Received: from lmf.lmf.ericsson.se (umail.lmf.ericsson.se [131.160.11.2]) by penguin.wise.edt.ericsson.se (8.9.0/8.9.0/WIREfire-1.2) with ESMTP id HAA04408 for ; Fri, 22 Jan 1999 07:08:01 +0100 (MET) Received: from tosb0323 by lmf.lmf.ericsson.se (8.8.8+Sun/SMI-SVR4) id IAA20258; Fri, 22 Jan 1999 08:08:02 +0200 (EET) Message-Id: <3.0.6.32.19990122080605.02ee0d90@openmail.lmf.ericsson.se> X-Sender: lmfmara@openmail.lmf.ericsson.se X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Fri, 22 Jan 1999 08:06:05 +0200 To: current@FreeBSD.ORG From: Martti Kuparinen Subject: New keyboard setting for sysinstall Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have modified sysinstall to include support for the Finnish keyboards. (I know, we had a discussion less than 1 year ago about the Swedish and the Finnish keyboards :-) I hope this gets in 3.1-RELEASE as some Finnish users may be unaware of the fact that they might use the Swedish keyboard settings... Below is an uucoded diff file from /usr/src. /Martti begin 644 finnish.gz M'XL("'=RIS8"`V9I;FYI]NV$?[9_2M0-ZW\(<(`F"227-EN>A'D>OP#N\`,$7!Q"7 M@X,#EL5I'.;Q47Z= )Y-\%J;IT9-P'(^2-&Y.L^1\Y^7%G/T03ICK,+?5=[U^ MVV-.K]?[K-%HV&JO5O3[CH\5#Y8_HL PZK7JGPZ#(V,Z]F^/C6]:8LFP69Y=1 M>,7NW32/7[UX\/#%[9&ZUHQ8(Y6_>27Q]SE[]-U/3[YY ?GJ?#>)FDD_9('.[ M;?@U#"=)?@$_1QG`.:\;3N!G,@-X+1I/HC@-)\,D@DL_7S6=5H=-IMG;^# R1 M[MF\.9XF02-C>0(7\JL%.Y#D;^.ANI"_3?)<:VP^1LB;PS?3+!R+7_R"N`$Q MIC@4_%?C8P Q%,OD$AN7`+%3>G_-F9))IJ]/W>E:98MW5:MV^U]HL4L<+ZH[? M0ID*7KS04P]+?'@3L_CR^(+3 QR?3R6QOQ+_.^'V^7?`R229CN M[4;32>ZV4V>WSN33/%.7ZHRLC4N#_>P2N&\_.V 3\[\TT&7(0-WF6Q[.S$WS, M>]%%F+&#?);M<^L-_[?:E],HB^/)97BU-XQ'X3R=G>51)LJK=?K MMZW* \5MU_M76M8.7NKIZ&+MAN]]FX:])ROB`[M9WM!(;Q]?\2?"+0]&)'\/L M^"*.QG4&Q=-X]HA;^= 4D'*1QG3U]]?@Q'RFL=)]F_RZ[K>NM/8`IRHZ?!YVV M:$^5I\.8/0_/8\:OOU?+,MI$5Z(!<^/R 5A>E#]&@NM?#17-R&HB;;;>XWR)C:T+^]7*[[7#6M!?'6`3[ )X$F$+>V$4Q9/9 M/MSWXC)R**LHYOM;=@/6CR8GVMP+N.W5QM^GN=6FOH<%13WA'2H;'_`VS
?L,N73`.;C4A`L7-T?(5BXV^> M"[#9B`1B;(*.#VN:,B38;$0",7:*CL\`\H1I8+,1"<38*W1\ CH.7QAK8;$0B M%.NZ/0C4O>[&4+`<5I3L%4D7PCS.XG^:0L%_[HXG$`2B#'<4")-4!YN-2,2- M I!%L&DJ#(O%`L2'>]S?X!*87&MAL:DP\4&R.CJ=2VIX&-AN1@&*'Z/@`I3V= M:6"S$0DH=H2.)P !A--;`9B,24.PY.GX/,)#!%<%F(Q)0[`4Z_JFV'IIM-B*! M&/LS.OY06]>"S48D$&/'Z/@(X`T. F@2;C4@@QJ;H^!A@-&(:V&Q$(A3K^N*F M^!;?M%/Z=VU]-5V9@'X+9G&`L[BS<7]BW&$0B0.S&& *`$_0V+NBR0^99[`O% MIKA?+PU$`HJM86L'6^X*?%#LKTCR-YRI\X$&-AN-"2CV'3K^%4"^!TFP V8@$ M%!NAX[%HN.3VGI\M]F(!&)L'1V_WJR3VN\LBFU#C&TB2=]"\GL; M"2BV@21G`/.E#:]\:S!NE( E$*#;#J5`:B*2]F#1J[N0P;A)L-B(1BDWQ5;PT M$`DHEF%K3'_C7+XH(9_G5XL2D<"N0)P?;`%$ (A0[&L?7_%5=`'_K$,`W4`+X M6L#O7KS%(H$N^!@%_@&"D@/BN^%HAJ768&(NDH$NR" MBUWP\%GQM4#X!\P, 1-)5)-@%%[O@X;/B:X'P[S$S$$D@21SL@HM=\/!9\;5` MW'Z+F8%(>K!G`15+6-XAVFR*I"L(<_ 20L/SN:[,1B5(L#_OJ!*0PL*>21"F6 MAWUU`E(8B$0IEH=]=0)2&(A$*9:'?1FO9:"6H(*X"8A$ *9:'?7G(51R(1"F6 MAWUUR%48B$0IEH=]>]M6!3F$@$A5C>=A7YYB%09 $$ M*L;RL*_.,0L#D2C%\K"OSC$+`Y$HQ?*PKT[*"@.1>(OYI'88%AA,X<5-`I'X M:QHM#FH6!^ T/<-`==!9[*>-NR/AFL$JB%.M@<'4QN'JX"OE=;1%>!R*A&(O! MU<7@ZN$JY`?:(KP.1-+[``<. /:'8#,\/2@.1.-H.L2PHG?1<;3N'8RY3#24> M<4\H-L-]7&D@$G^Q9)0&(FDOEHS20"2=Q9)1&H BDNXCVI8%(@D6@+@U$HL78 MTB!)G)868TL#D6@QMC00B19C2P.1>#MP!1_;'2!#JRP1A;^V%RH. 1-+&?F!` M*@5$T4$*%$\I((HN4F`\+`6IN8UA/K8K/8J@1WE>"N$MP?(,'M0/J2 .;[A?R[9;,L)[BZFQN#@9N68Q>D& M&E0)[BK!726X]02WX^/\:)LFH,6VE.!V0"W; M[>,FN&VV*L%=);A))Q9;X02WS79W@GLE;V*R50GN*L%=);BK!'>5X/Z?)+B+ MPR>1X"X.58*[2G#_%@ENZ_^`K1+<58*[2G!7">XJP?W_E^#^+P#9%@P$1P`` ` end --- Martti Kuparinen http://www.hut.fi/~kuparine To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 22:11:50 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA24968 for freebsd-current-outgoing; Thu, 21 Jan 1999 22:11:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from psf.Pinyon.ORG (ppp1-236.presc.dialup.futureone.com [209.250.11.236]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA24959 for ; Thu, 21 Jan 1999 22:11:46 -0800 (PST) (envelope-from rcarter@psf.Pinyon.ORG) Received: from psf.Pinyon.ORG (localhost [127.0.0.1]) by psf.Pinyon.ORG (8.9.2/8.9.2) with ESMTP id TAA06788 for ; Thu, 21 Jan 1999 19:39:28 -0700 (MST) (envelope-from rcarter@psf.Pinyon.ORG) Message-Id: <199901220239.TAA06788@psf.Pinyon.ORG> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG Subject: Re: Using LinuxThreads Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Jan 1999 19:39:28 -0700 From: "Russell L. Carter" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG dick@tar.com said: %For kernel threading you just use libc. Whether or not libc generates % thread safe (re-entrant) calls depends on whether its also linked %with a library that 1) sets __isthreaded to a non-zero value, 2) has a %_spinlock() implementationm, and 3) implements the functions %flockfile, funlockfile, etc. There are also a few macros in header %files that require _THREAD_SAFE to be defined to be thread safe. %libc_r could be modified so that is doesn't replace libc, but rather %is an addon, comparable to the kernel threaded libc case. But, it %would involve a bit of work. I thought so at first, but then I had to look at wait4 today and now I'm not so sure. At least some of libc_r is very closely tied to the uthread scheduler: uthread_wait4.c: #include #include #ifdef _THREAD_SAFE #include #include "pthread_private.h" pid_t wait4(pid_t pid, int *istat, int options, struct rusage * rusage) { pid_t ret; /* Perform a non-blocking wait4 syscall: */ while ((ret = _thread_sys_wait4(pid, istat, options | WNOHANG, rusage)) == 0 && (options & WNOHANG) == 0) { /* Reset the interrupted operation flag: */ _thread_run->interrupted = 0; /* Schedule the next thread while this one waits: */ _thread_kern_sched_state(PS_WAIT_WAIT, __FILE__, __LINE__); /* Check if this call was interrupted by a signal: */ if (_thread_run->interrupted) { errno = EINTR; ret = -1; break; } } return (ret); } #endif Russell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 22:15:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA25483 for freebsd-current-outgoing; Thu, 21 Jan 1999 22:15:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA25438 for ; Thu, 21 Jan 1999 22:14:46 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.1) with ESMTP id IAA07697; Fri, 22 Jan 1999 08:14:33 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.2/8.9.2) with ESMTP id IAA94244; Fri, 22 Jan 1999 08:14:31 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199901220614.IAA94244@greenpeace.grondar.za> To: Kazutaka YOKOTA cc: current@FreeBSD.ORG Subject: Re: keymaps In-Reply-To: Your message of " Fri, 22 Jan 1999 08:58:43 +0900." <199901212358.IAA01400@zodiac.mech.utsunomiya-u.ac.jp> References: <199901211605.BAA24511@zodiac.mech.utsunomiya-u.ac.jp> <199901211840.UAA92062@greenpeace.grondar.za> <199901212358.IAA01400@zodiac.mech.utsunomiya-u.ac.jp> Date: Fri, 22 Jan 1999 08:14:30 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kazutaka YOKOTA wrote: > ScrollLock does "back scroll" too. You want both? My Libretto 70CT has no Scroll Lock, only a Pause. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 22:16:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA25662 for freebsd-current-outgoing; Thu, 21 Jan 1999 22:16:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA25655 for ; Thu, 21 Jan 1999 22:16:35 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id WAA13024; Thu, 21 Jan 1999 22:07:28 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdw13022; Fri Jan 22 06:07:23 1999 Date: Thu, 21 Jan 1999 22:07:21 -0800 (PST) From: Julian Elischer To: Christian Kuhtz cc: freebsd-current@FreeBSD.ORG Subject: Re: top broken - VM sideeffect? In-Reply-To: <19990121212352.D79573@oreo.adsu.bellsouth.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG yes matt said that it was broken... On Thu, 21 Jan 1999, Christian Kuhtz wrote: > > Looks like top's broken. It no longer shows swap space status on 4.0-CURRENT. > Side effect of the VM update? > > -- > "Logic is a little bird, sitting in a tree; that smells *awful*." > -- /usr/bin/fortune > > [Disclaimer: I speak for myself and my views are my own and not in any way to > be construed as the views of BellSouth Corporation. ] > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 23:04:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA01096 for freebsd-current-outgoing; Thu, 21 Jan 1999 23:04:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-49-dbn.dial-up.net [196.34.155.49]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA01086 for ; Thu, 21 Jan 1999 23:04:50 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id JAA15837; Fri, 22 Jan 1999 09:03:12 +0200 (SAT) From: Robert Nordier Message-Id: <199901220703.JAA15837@ceia.nordier.com> Subject: Re: Booting from 2nd IDE [Re: Experiences with aout-to-elf and new bootblocks] In-Reply-To: <99Jan22.110737est.40377@border.alcanet.com.au> from Peter Jeremy at "Jan 22, 99 11:08:12 am" To: peter.jeremy@auss2.alcatel.com.au (Peter Jeremy) Date: Fri, 22 Jan 1999 09:03:09 +0200 (SAT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Jeremy wrote: > Mark Blackman wrote: > >FWIW, I've done it under 2.2.7 by > > > >1) installing booteasy on both wd0 *AND* wd2 > >2) altering the boot.config to > > 1:wd(2,a)kernel > > This works for an a.out 3.0 kernel, but the old bootloader can't handle > ELF kernels, so this isn't a usable solution. The new boot blocks, installed by disklabel -B $DRIVE do handle (both a.out and) ELF kernels, despite looking very similar to the old a.out-only ones. The idea is to provide a fallback means of booting a kernel in either format. So using a /boot.config statement like the above (or hitting any key before seeing the /boot/loader prompt, to get the old "boot:" prompt instead), is a recommended workaround for any temporary /boot/loader problems. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 23:07:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA01285 for freebsd-current-outgoing; Thu, 21 Jan 1999 23:07:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp2.erols.com (smtp2.erols.com [207.172.3.235]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA01280 for ; Thu, 21 Jan 1999 23:07:28 -0800 (PST) (envelope-from shmit@natasya.noc.erols.net) Received: from natasya.noc.erols.net (natasya.noc.erols.net [207.172.25.236]) by smtp2.erols.com (8.8.8/8.8.5) with ESMTP id XAA03573; Thu, 21 Jan 1999 23:29:19 -0500 (EST) Received: (from shmit@localhost) by natasya.noc.erols.net (8.9.1/8.9.1) id XAA00279; Thu, 21 Jan 1999 23:24:01 -0500 (EST) Message-ID: <19990121232401.A267@kublai.com> Date: Thu, 21 Jan 1999 23:24:01 -0500 From: Brian Cully To: Gregory Bond , Kazutaka YOKOTA Cc: current@FreeBSD.ORG Subject: Re: keymaps Reply-To: shmit@kublai.com References: <199901220043.LAA22437@lightning.itga.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199901220043.LAA22437@lightning.itga.com.au>; from Gregory Bond on Fri, Jan 22, 1999 at 11:43:56AM +1100 X-Sender: If your mailer pays attention to this, it's broken. X-PGP-Info: finger shmit@kublai.com for my public key. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 22, 1999 at 11:43:56AM +1100, Gregory Bond wrote: > my vote: A version of the standard keymap with CapsLock and LeftCtl > functions swapped so the control key is under my left finger like God > intended! Take your existing keymap and swap 029 and 058 with these: 029 clock clock clock clock clock clock clock clock O 058 lctrl lctrl lctrl lctrl lctrl lctrl lctrl lctrl O I've tacked this into my Dvorak keymap and have been pretty happy ever since --- it actually makes the console usable. -- Brian Cully ``I'm not surprised,'' said I. ``You created God in your own image, and when you found out he was no good you abolished him. It's quite a common form of psychological suicide.'' -- Robertson Davies, Fifth Buisiness To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 23:08:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA01360 for freebsd-current-outgoing; Thu, 21 Jan 1999 23:08:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sicily.odyssey.cs.cmu.edu (SICILY.ODYSSEY.CS.CMU.EDU [128.2.185.138]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA01352 for ; Thu, 21 Jan 1999 23:08:07 -0800 (PST) (envelope-from rvb+@sicily.odyssey.cs.cmu.edu) To: Mike Smith Cc: Geoff Buckingham , freebsd-current@FreeBSD.ORG Subject: Re: KVA/KVM shortages References: <199901212153.NAA11404@dingo.cdrom.com> From: "Robert V. Baron" Date: 21 Jan 1999 22:05:23 -0500 In-Reply-To: Mike Smith's message of Thu, 21 Jan 1999 13:53:44 -0800 Message-ID: Lines: 23 X-Mailer: Gnus v5.4.46/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: > I just committed a tweak that allows you to say: > > set kern.vm.kmem.size= > > at the loader prompt or in /boot/loader.rc to override the default > VM_KMEM_SIZE value. > > If anyone has any more of these tunables that can easily be enhanced > like this, please let me know. > How about all the parameters that are assigned in param.c? Why not make them all tweakable in the loader.rc, rather than having to patch the kernel. Actually, thinking about this a little more ... The loader knows where all symbols are in memory. Why not a general mechanism to let you reassign the value of any "variable" used in the kernel or in a module. I presume that the loader allocates bss for the kernel and each module as it loads it. So I presume I can assign a value to a variable that would ordinarily take on a 0 value, too. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 23:14:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA01877 for freebsd-current-outgoing; Thu, 21 Jan 1999 23:14:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-49-dbn.dial-up.net [196.34.155.49]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA01867 for ; Thu, 21 Jan 1999 23:14:49 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id JAA15866; Fri, 22 Jan 1999 09:12:32 +0200 (SAT) From: Robert Nordier Message-Id: <199901220712.JAA15866@ceia.nordier.com> Subject: Re: Problem loading 2.x kernel with new bootblocks In-Reply-To: <99Jan22.144456est.40356@border.alcanet.com.au> from Peter Jeremy at "Jan 22, 99 02:45:33 pm" To: peter.jeremy@auss2.alcatel.com.au (Peter Jeremy) Date: Fri, 22 Jan 1999 09:12:30 +0200 (SAT) Cc: mike@smith.net.au, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Jeremy wrote: > Mike Smith wrote: > >> The kernel has been built with gcc-2.8.1 -O2. > > > >Please rebuild with the system compiler and -O at most. > > It makes no difference. The kernel loads and runs happily from the > old bootloader, but crashes with /boot/loader. (I disabled my > gcc-2.8.1, changed make.conf to -O, re-ran config; make depend; make; > make install). > > Something that `fell off' my previous posting (it was implied in the > context of my original posting): > > Both disks have Booteasy installed. wd0 has the old bootblocks > (from 2.2.6-RELEASE) and FreeBSD 2.x installed on slice 2. wd2 > has the new bootblocks and 3.0-current built from CTM 'cvs-cur 4996' > occupying all of slice 1 (which is all of the disk). > > The boot sequences are: > disk0 booteasy offers: W95, FreeBSD, Disk1: > - select FreeBSD and 2.x boots successfully > - select `disk1' and the disk1 booteasy offers: BSD, disk0 > > Select BSD and the new /boot/loader comes up. If I let it continue, I > wind up with the 3.0 (customised, ELF) kernel booting successfully. > > If I abort /boot/loader's autostart (giving me a prompt), then (as per > Peter Wemm's elfday tutorial) issue the commands: > set currdev=disk1s2a > load /kernel > boot -s > the system displays garbage on the screen and doesn't respond to anything > gentler than the reset button. > > If I load the GENERIC 2.2.6-RELEASE kernel, ("load /kernel.GENERIC" above) > then it works. > > Any suggestions as to my next step? Please e-mail me a copy of the kernel (or put it up for ftp, if you prefer), and I'll take a look. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 21 23:33:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA03467 for freebsd-current-outgoing; Thu, 21 Jan 1999 23:33:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA03461 for ; Thu, 21 Jan 1999 23:33:23 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id IAA18616; Fri, 22 Jan 1999 08:33:04 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199901220733.IAA18616@freebsd.dk> Subject: Re: Promise FastTrack PCI IDE controller In-Reply-To: <19990122120633.A13400@rf900.physics.usyd.edu.au> from David Dawes at "Jan 22, 1999 12: 6:33 pm" To: dawes@rf900.physics.usyd.edu.au (David Dawes) Date: Fri, 22 Jan 1999 08:33:04 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems David Dawes wrote: > > >> >I also run the card without its BIOS, as that tends to get in the way. > >> >I think the FastTrack is just an Ultra/33 with another BIOS chip on it. > >> > >> I'll try pulling the BIOS tomorrow. We didn't get this card for it's > >> RAID features anyway. > > > >That helped me in a lot if situations, but performance wont be as good > >as we seem not to initialize the chip(s)... > > When I remove the BIOS it works OK. The initialisation is different > though. Yep I know, the chipset on the Promise is not initialized to what the drives support then, its working in a slow (but always working though) mode. I did plan to change this, and even got the docs for the chips but it has sunken pretty low on the TODO list lately... > The performance isn't as good, as you say. For one of these disks on > the PIIX4 I get about 12 MByte/s for a large (1GB) sequential read from > the raw device. I only get about 4 MByte/s for one of the same disks > on the Promise controller. I presume that's because it isn't initialised > to the fastest DMA mode? > > The performance is adequate for our needs though, so removing the BIOS > is a workable solution. Or you could try to get ahold of a BIOS from an Ultra/33 controller, that does work in most situations... - Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 00:13:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA07201 for freebsd-current-outgoing; Fri, 22 Jan 1999 00:13:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA07195 for ; Fri, 22 Jan 1999 00:12:55 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:8BqyQBdf7hmcxfEHeiuloC/QMedS2YIB@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id RAA13752 for ; Fri, 22 Jan 1999 17:12:45 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id RAA15900; Fri, 22 Jan 1999 17:15:21 +0900 (JST) Message-Id: <199901220815.RAA15900@zodiac.mech.utsunomiya-u.ac.jp> To: current@FreeBSD.ORG cc: yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: keymaps In-reply-to: Your message of "Thu, 21 Jan 1999 23:38:19 CST." References: Date: Fri, 22 Jan 1999 17:15:20 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> my vote: A version of the standard keymap with CapsLock and LeftCtl functio >ns >> swapped so the control key is under my left finger like God intended! > >My vote is both of the above. I've never found a use for CapsLock, but >LeftCtl is important enough that I wouldn't mind it duplicated. Most >people I know are like this. > >(Yes of course there needs to be a way to get at capslock for those who >really need it) I understand many of you prefer the Ctrl key sitting next to the 'A' key, as my own keymap swaps the Caps key and the Left Ctrl key too :-) But, this is a matter of personal taste and preference which you can easily obtain by editing a keymap. Gentlemen, I don't intend to add yet another keymap to /usr/share/syscons/keymaps. I am merely trying to define a reasonable set of common, consistent key binding for existing keymaps. National keyboards have different layout of regular keys. But function keys and special keys are placed identically. They should work in the same way, or at least similar way in all keyboards, unless there is a good reason to do otherwise. (I am not talking about non-AT keyboards which are totally different from either AT 84 or 101/102/104 keyboards.) What I want to avoid is that one key does one thing on one national keyboard and the same key on another national keyboard does a different thing. This is absurd, and hazardous when writing document or giving advises ("you can cycle through vtys by hitting PrintScreen, um, well, on most keyboards, well, on your keyboard you may need to hit a different key, I don't know which...") In order to define a common set, I start from key assignments based on existing keymaps, which may not necessarily be your, or my, favorite. (Why on earth Ctrl-Alt-ESC yields "debug"? Because someone started it and documented in the handbook!) New functions and their assignments can be controversial and we shall hear various opinions about them. I expect that, and we should resolve this on technical merits. (The following is an example. In my previous post I removed the "backscroll" function from the Pause key because the ScrollLock key already has "backscroll". My reasoning was wrong. A user reported that his notebook PC doesn't have the ScrollLock key and we have to let the Pause key have "backscroll" too.) I don't intend to enforce preference or taste, or particular usage of, or a particular way of working with the keyboard. (I certainly won't force mine on you) So, keymaps I am trying to define may look too plain, too boring, too uninteresting, and less appealing to you. But, I am not depriving you of liberty to modify your keymap. Be creative and write a keymap of your own. You are free to do that. But, don't expect your modification should instantly be the standard in all keymaps. It won't necessarily happen... Well, it might happen, if it has sound reason other than "because I like it that way" :-) Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 00:42:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA10034 for freebsd-current-outgoing; Fri, 22 Jan 1999 00:42:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (c2-17-dbn.dial-up.net [196.34.155.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA10027 for ; Fri, 22 Jan 1999 00:42:21 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id KAA16785; Fri, 22 Jan 1999 10:41:15 +0200 (SAT) From: Robert Nordier Message-Id: <199901220841.KAA16785@ceia.nordier.com> Subject: Re: Booting from 2nd IDE [Re: Experiences with aout-to-elf and new bootblocks] In-Reply-To: <199901220703.JAA15837@ceia.nordier.com> from Robert Nordier at "Jan 22, 99 09:03:09 am" To: peter.jeremy@auss2.alcatel.com.au (Peter Jeremy) Date: Fri, 22 Jan 1999 10:41:12 +0200 (SAT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wrote: > Peter Jeremy wrote: > > > Mark Blackman wrote: > > >FWIW, I've done it under 2.2.7 by > > > > > >1) installing booteasy on both wd0 *AND* wd2 > > >2) altering the boot.config to > > > 1:wd(2,a)kernel > > > > This works for an a.out 3.0 kernel, but the old bootloader can't handle > > ELF kernels, so this isn't a usable solution. > > The new boot blocks, installed by > > disklabel -B $DRIVE > > do handle (both a.out and) ELF kernels, despite looking very similar > to the old a.out-only ones. The idea is to provide a fallback > means of booting a kernel in either format. > > So using a /boot.config statement like the above (or hitting any > key before seeing the /boot/loader prompt, to get the old "boot:" > prompt instead), is a recommended workaround for any temporary > /boot/loader problems. I should have added that, where more than one version of FreeBSD is installed on the same machine, updating the default boot disk to the latest boot blocks is also suggested. A /boot.config like 1:wd(2,a) would then pass control directly to a non-default copy of /boot/loader. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 01:18:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA13790 for freebsd-current-outgoing; Fri, 22 Jan 1999 01:18:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA13783 for ; Fri, 22 Jan 1999 01:18:19 -0800 (PST) (envelope-from rock@cs.uni-sb.de) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.2/1999010400) with ESMTP id KAA04570; Fri, 22 Jan 1999 10:18:04 +0100 (CET) Received: from cs.uni-sb.de (maxtnt-088.rz.uni-sb.de [134.96.70.215]) by cs.uni-sb.de (8.9.2/1999010400) with ESMTP id KAA01406; Fri, 22 Jan 1999 10:18:02 +0100 (CET) Message-ID: <36A84252.84EB3244@cs.uni-sb.de> Date: Fri, 22 Jan 1999 10:18:10 +0100 From: "D. Rock" X-Mailer: Mozilla 4.5 [de] (WinNT; U) X-Accept-Language: de MIME-Version: 1.0 To: Matthew Dillon CC: current@FreeBSD.ORG Subject: Re: NFS v3 issue References: <36A711FD.85F65545@cs.uni-sb.de> <199901220439.UAA47389@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon schrieb: > > :With NFS v3 there seem still to be some open issues. > :Im running the latest (4.0)-current with the new vm/NFS changes. > :While I haven't found any problems with NFSv2 so far, v3 still seems to make > :trouble. > : > :I noticed the error some months ago, while my /usr/obj was NFS mounted, and > :a build failed while making termcap.db. Today, I gave it another try. > :I copied /usr/src/share/termcap into an NFS mounted directory and did > :a "make". I compared the output of termcap.db with the one build on the local > :drive. > :While the NFS mounted one was only 1077760 bytes in size, the correct > :size (from the local build) should be 1245184 bytes. I did the build > :several times, everytime I got the same values. I then remounted the > :direcory NFSv2. Now the build produced the right file (in size and content). > : > :The NFS Server is a Solaris 7 machine. > : > :Can anyone else confirm this error? > : > :Daniel > > I can't help you here, but I want to make sure: The problems you are > having are the same problems you were having a few months ago? ( I > want to make sure I haven't introduced new problems in -4.x, and if I > have to fix them ASAP! ). I am not sure if they are the same, but it seems so: A make world with /usr/obj NFS mounted worked up to the point where the termcap was built. Now only the error is slightly different: A few months ago, cap_mkdb exited with SIG 11, now it succeeds but generates the wrong file. I think it's the same bug. The SEGV maybe have gone away because of some library reordering over the months. Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 01:32:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA15288 for freebsd-current-outgoing; Fri, 22 Jan 1999 01:32:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA15245 for ; Fri, 22 Jan 1999 01:32:28 -0800 (PST) (envelope-from netchild@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.2/1999010400) with ESMTP id JAA04239 for ; Fri, 22 Jan 1999 09:32:58 +0100 (CET) Received: from wurzelausix (wurzelausix.cs.uni-sb.de [134.96.247.1]) by cs.uni-sb.de (8.9.2/1999010400) with ESMTP id JAA00825 for ; Fri, 22 Jan 1999 09:32:58 +0100 (CET) Received: from wurzelausix.cs.uni-sb.de (IDENT:hN41YST/WC+fNaL7I/6KVk2ZdfgeBz9k@localhost [127.0.0.1]) by wurzelausix (8.9.1/wjp/19980821) with ESMTP id JAA22092 for ; Fri, 22 Jan 1999 09:32:54 +0100 (CET) Message-Id: <199901220832.JAA22092@wurzelausix> Date: Fri, 22 Jan 1999 09:32:52 +0100 (CET) From: Alexander Leidinger Subject: Splash screen and "boot -s" To: current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, booting into single user mode didn`t remove the splash screen at the "enter path to shell..." prompt. FreeBSD 4.0-CURRENT #0: Thu Jan 21 Bye, Alexander. -- http://netchild.home.pages.de A.Leidinger @ wurzelausix.cs.uni-sb.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 01:32:50 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA15305 for freebsd-current-outgoing; Fri, 22 Jan 1999 01:32:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA15287 for ; Fri, 22 Jan 1999 01:32:48 -0800 (PST) (envelope-from netchild@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.2/1999010400) with ESMTP id JAA04286 for ; Fri, 22 Jan 1999 09:43:14 +0100 (CET) Received: from wurzelausix (wurzelausix.cs.uni-sb.de [134.96.247.1]) by cs.uni-sb.de (8.9.2/1999010400) with ESMTP id JAA00935 for ; Fri, 22 Jan 1999 09:43:14 +0100 (CET) Received: from wurzelausix.cs.uni-sb.de (IDENT:C83DmvzmqOxGkjgZ6E68lmXmnCKJja5b@localhost [127.0.0.1]) by wurzelausix (8.9.1/wjp/19980821) with ESMTP id JAA22269 for ; Fri, 22 Jan 1999 09:43:11 +0100 (CET) Message-Id: <199901220843.JAA22269@wurzelausix> Date: Fri, 22 Jan 1999 09:43:08 +0100 (CET) From: Alexander Leidinger Subject: Re: readdir & cd9660 & direntp->d_type == bug (more) To: current@FreeBSD.ORG In-Reply-To: <199901191951.UAA01392@Vodix.CS.Uni-SB.de> MIME-Version: 1.0 Content-Type: MULTIPART/mixed; BOUNDARY="-559023410-851401618-916994593=:22089" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ---559023410-851401618-916994593=:22089 Content-Type: TEXT/plain; CHARSET=US-ASCII Hi, attached is the source of a test program. With the CD of my ISDN card it produces: {0} (15) netchild@ttyp1 > ./dirtest /cdrom /cdrom: . (type: unknown) .. (type: unknown) autorun.inf (type: unknown) cardware (type: unknown) doku (type: unknown) fritz.ico (type: unknown) fritz! (type: unknown) intro.hlp (type: unknown) online (type: unknown) tools (type: unknown) winport (type: unknown) {0} (16) netchild@ttyp1 > ls -l /cdrom total 173 -r-xr-xr-x 1 root wheel 54 22 Mai 1998 autorun.inf dr-xr-xr-x 1 root wheel 2048 27 Mai 1998 cardware dr-xr-xr-x 1 root wheel 2048 27 Mai 1998 doku dr-xr-xr-x 1 root wheel 2048 27 Mai 1998 fritz! -r-xr-xr-x 1 root wheel 766 15 Mai 1998 fritz.ico -r-xr-xr-x 1 root wheel 75833 22 Mai 1998 intro.hlp dr-xr-xr-x 1 root wheel 2048 27 Mai 1998 online dr-xr-xr-x 1 root wheel 2048 27 Mai 1998 tools dr-xr-xr-x 1 root wheel 2048 27 Mai 1998 winport Every other CD I tried shows similar results. With ufs or msdos it displays the correct type (dir, reg, ...). FreeBSD 4.0-CURRENT #0: Thu Jan 21 Bye, Alexander. -- http://netchild.home.pages.de A.Leidinger @ wurzelausix.cs.uni-sb.de ---559023410-851401618-916994593=:22089 Content-Type: APPLICATION/octet-stream Content-Description: dirtest.c #define _POSIX_SOURCE #include #include #include char *types[] = { "unknown", "fifo", "chr", "not defined", "dir", "not defined", "blk", "not defined", "reg", "not defined", "lnk", "not defined", "sock", "not defined", "wht" }; int main(int argc, char **argv) { DIR *dir_p; struct dirent *dent_p; if(argc != 2) printf("%s \n", argv[0]); dir_p = opendir(argv[1]); if(!dir_p) exit(1); printf("\n%s:\n", argv[1]); while((dent_p = readdir(dir_p))) { printf("%-40s (type: %s)\n", dent_p->d_name, types[dent_p->d_type]); } if(closedir(dir_p) == -1) perror("Shit happens"); return 0; } ---559023410-851401618-916994593=:22089-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 01:55:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA17798 for freebsd-current-outgoing; Fri, 22 Jan 1999 01:55:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pi.yip.org (yip.org [142.154.6.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA17784 for ; Fri, 22 Jan 1999 01:55:46 -0800 (PST) (envelope-from melange@yip.org) Received: from localhost (melange@localhost) by pi.yip.org (8.8.8/8.8.8) with SMTP id EAA00187; Fri, 22 Jan 1999 04:53:28 -0500 (EST) (envelope-from melange@yip.org) Date: Fri, 22 Jan 1999 04:53:27 -0500 (EST) From: Bob K To: =?iso-8859-1?Q?S=F8ren_Schmidt?= cc: David Dawes , current@FreeBSD.ORG Subject: Re: Promise FastTrack PCI IDE controller In-Reply-To: <199901220733.IAA18616@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id BAA17790 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 22 Jan 1999, Søren Schmidt wrote: [snip] > Yep I know, the chipset on the Promise is not initialized to what the > drives support then, its working in a slow (but always working though) > mode. I did plan to change this, and even got the docs for the chips > but it has sunken pretty low on the TODO list lately... [snip] Having one of these cards sitting in my desk after buying it mail-order and finding out afterwards that it wasn't supported, I for one would be exceedingly happy if support for the FastTrack was added. I'd be willing to test patches for people, but I'll have to bring the system up to date, which will probably take a day or two. melange@yip.org - For external use only. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 02:20:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA21211 for freebsd-current-outgoing; Fri, 22 Jan 1999 02:20:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from server.noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA21203 for ; Fri, 22 Jan 1999 02:20:52 -0800 (PST) (envelope-from geoffb@gti.noc.demon.net) Received: by server.noc.demon.net; id KAA15427; Fri, 22 Jan 1999 10:20:43 GMT Received: from gti.noc.demon.net(195.11.55.101) by inside.noc.demon.net via smap (3.2) id xmae15421; Fri, 22 Jan 99 10:20:42 GMT Received: (from geoffb@localhost) by gti.noc.demon.net (8.8.8/8.8.8) id KAA06441; Fri, 22 Jan 1999 10:20:41 GMT Message-ID: <19990122102040.H19395@gti.noc.demon.net> Date: Fri, 22 Jan 1999 10:20:40 +0000 From: Geoff Buckingham To: Mike Smith Cc: freebsd-current@FreeBSD.ORG Subject: Re: KVA/KVM shortages Reply-To: Geoff Buckingham References: <19990121180941.G19395@gti.noc.demon.net> <199901212153.NAA11404@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199901212153.NAA11404@dingo.cdrom.com>; from Mike Smith on Thu, Jan 21, 1999 at 01:53:44PM -0800 Organisation: Demon Internet Ltd Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Previously on Thu, Jan 21, 1999 at 01:53:44PM -0800, Mike Smith wrote: : > On tuesday I crashed a machine after it ran out of kvm. (dual PII 400 with : > 768MB RAM) poking about in the code adding: : > : > options "VM_KMEM_SIZE=(24*1024*1024)" : > options "VM_KMEM_SIZE_MAX=(128*1024*1024)" : > : > seems like a good way foward. Is it? : : >From what I can see, you shouldn't need to set VM_KMEM_SIZE_MAX unless : you're also setting VM_KMEM_SIZE_SCALE. : My understanding was VM_KMEM_SIZE_SCALE picks up a default of value of 3 from vmparam.h, which if I understand the following from kern-malloc.c vm_kmem_size = VM_KMEM_SIZE; mem_size = cnt.v_page_count * PAGE_SIZE; #if defined(VM_KMEM_SIZE_SCALE) if ((mem_size / VM_KMEM_SIZE_SCALE) > vm_kmem_size) vm_kmem_size = mem_size / VM_KMEM_SIZE_SCALE; #endif #if defined(VM_KMEM_SIZE_MAX) if (vm_kmem_size >= VM_KMEM_SIZE_MAX) vm_kmem_size = VM_KMEM_SIZE_MAX; #endif combined with the apparent defaults of VM_KMEM_SIZE 12M VM_KMEM_SIZE_SCALE 3 VM_KMEM_SIZE_MAX 80M means vm_kmem_size never gets bigger than 80M without VM_KMEM_SIZE_MAX being defined >80M (This is all from a mid december 3.x box) : I just committed a tweak that allows you to say: : : set kern.vm.kmem.size= : : at the loader prompt or in /boot/loader.rc to override the default : VM_KMEM_SIZE value. : Unless I am being too literal or miss-understanding the above do you not need to set VM_KMEM_SIZE_MAX or have thing moved on since december? -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 02:25:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA22014 for freebsd-current-outgoing; Fri, 22 Jan 1999 02:25:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA22003 for ; Fri, 22 Jan 1999 02:25:50 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.10 #1) id 103diw-00002z-00; Fri, 22 Jan 1999 12:21:58 +0200 From: Sheldon Hearn To: Ying-Chieh Liao cc: Tim , freebsd-current@FreeBSD.ORG Subject: Re: PNP and new bootloader with ELF kernel In-reply-to: Your message of "Fri, 22 Jan 1999 12:22:26 +0800." <19990122122226.A2328@terry.dragon2.net> Date: Fri, 22 Jan 1999 12:21:58 +0200 Message-ID: <183.917000518@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 22 Jan 1999 12:22:26 +0800, Ying-Chieh Liao wrote: > you can put this pnp information in /kernel.config > and, in your /boot/boot.conf, put > > load /kernel > load -t userconfig_script /kernel.config > boot Hi chaps, Try to encourage current users to use /boot/loader.rc instead. We don't want kernel.config anymore, from what I've read on this list. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 02:34:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA22990 for freebsd-current-outgoing; Fri, 22 Jan 1999 02:34:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ayukawa.aus.org (ayukawa.aus.org [199.166.246.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA22979 for ; Fri, 22 Jan 1999 02:34:23 -0800 (PST) (envelope-from lh@aus.org) Received: from bsd.aus.org (bsd.aus.org [199.166.246.189]) by ayukawa.aus.org (8.8.7/8.7.3) with ESMTP id FAA07191 for ; Fri, 22 Jan 1999 05:15:10 -0500 (EST) Message-Id: <199901221015.FAA07191@ayukawa.aus.org> X-Mailer: XFMail 1.3-beta-042198 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 22 Jan 1999 05:34:11 -0500 (EST) Reply-To: lh@aus.org From: Luke To: current@FreeBSD.ORG Subject: Re: make world broken in /lib Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > "me too" > > -DNOSECURE seems to help but it hasn't completed yet. > > julian me too, but figured the longer strings with the crypt -DNOSECURE makes must be better :). Anyone know of an easy or possible way to turn a DES crypted passwd file into the normal libcrypt kind? --- E-Mail: Luke Sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 02:43:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA23855 for freebsd-current-outgoing; Fri, 22 Jan 1999 02:43:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA23849 for ; Fri, 22 Jan 1999 02:43:24 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id CAA17721 for ; Fri, 22 Jan 1999 02:39:13 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdK17719; Fri Jan 22 10:39:05 1999 Date: Fri, 22 Jan 1999 02:39:03 -0800 (PST) From: Julian Elischer To: current@FreeBSD.ORG Subject: world broken Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG having spent almost an hour trying to decode the complexities of the crypt making process I admit defeat.. can SOMEBODY please fix the build in -current and sent branson a nice pointy hat.. I think he committed and went on vacation (I haven't seen any commits that say they fixed this but I'm waiting for cvsup to connect just in case I missed it...) julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 03:10:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA26247 for freebsd-current-outgoing; Fri, 22 Jan 1999 03:10:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA26242 for ; Fri, 22 Jan 1999 03:10:18 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id DAA52243; Fri, 22 Jan 1999 03:10:09 -0800 (PST) (envelope-from dillon) Date: Fri, 22 Jan 1999 03:10:09 -0800 (PST) From: Matthew Dillon Message-Id: <199901221110.DAA52243@apollo.backplane.com> To: current@FreeBSD.ORG Subject: kvm_getswapinfo() function added to libkvm. top, pstat, systat updated Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A new function, kvm_getswapinfo(), has been added to libkvm. pstat, systat, and top have been updated to use the new function. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 03:20:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA26991 for freebsd-current-outgoing; Fri, 22 Jan 1999 03:20:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rnocserv.urc.ac.ru (rnocserv.urc.ac.ru [193.233.85.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA26983 for ; Fri, 22 Jan 1999 03:20:44 -0800 (PST) (envelope-from joy@urc.ac.ru) Received: from urc.ac.ru (y.urc.ac.ru [193.233.85.37]) by rnocserv.urc.ac.ru (8.8.8/8.8.8) with ESMTP id QAA08559 for ; Fri, 22 Jan 1999 16:20:17 +0500 (ES) (envelope-from joy@urc.ac.ru) Message-ID: <36A85EF1.444A86B@urc.ac.ru> Date: Fri, 22 Jan 1999 16:20:17 +0500 From: Konstantin Chuguev Organization: Southern Regional Center of FREEnet X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: T/TCP in FreeBSD-3.x Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Has FreeBSD-3.x a correct implementation of T/TCP? There is some bug mentioned in Squid FAQ (http://squid.nlanr.net/Squid/FAQ/FAQ-14.html#ss14.2), about brokenness of T/TCP in FreeBSD-2.2.2. Why I'm asking about this, is because I recently read an advice in one of the FreeBSD mailing lists, about "Why my dial-up PPP connection from a FreeBSD box is so slow comparing with Windows NT (about ten times slower)?" And the advice was (without explanations): "Try to switch off the TCP_EXTENSIONS in /etc/rc.conf". So, is it safe to use T/TCP (at least for Squid) for RELENG_3? RELENG_2_2? And what about MBUF size (mentioned at the same page of the Squid FAQ)? Do I need to patch Squid as it shown at the page? Thanks. -- Konstantin V. Chuguev. System administrator of Southern http://www.urc.ac.ru/~joy/ Ural Regional Center of FREEnet, mailto:joy@urc.ac.ru Chelyabinsk, Russia. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 03:33:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA28086 for freebsd-current-outgoing; Fri, 22 Jan 1999 03:33:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA28081 for ; Fri, 22 Jan 1999 03:33:14 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id WAA17787; Fri, 22 Jan 1999 22:32:55 +1100 Date: Fri, 22 Jan 1999 22:32:55 +1100 From: Bruce Evans Message-Id: <199901221132.WAA17787@godzilla.zeta.org.au> To: current@FreeBSD.ORG, netchild@wurzelausix.CS.Uni-SB.DE Subject: Re: readdir & cd9660 & direntp->d_type == bug (more) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >attached is the source of a test program. > >With the CD of my ISDN card it produces: > >{0} >(15) netchild@ttyp1 > ./dirtest /cdrom > >/cdrom: >. (type: unknown) >.. (type: unknown) >autorun.inf (type: unknown) This is because the cd9660 file system doesn't implement d_type. >{0} >(16) netchild@ttyp1 > ls -l /cdrom >total 173 >-r-xr-xr-x 1 root wheel 54 22 Mai 1998 autorun.inf ls works because it stats the file. >#define _POSIX_SOURCE > >#include >#include >... > while((dent_p = readdir(dir_p))) > { > printf("%-40s (type: %s)\n", dent_p->d_name, types[dent_p->d_type]); > } This probably shouldn't compile, since d_type isn't in POSIX.1. POSIX.1 only guarantees d_name in struct dirent. Names beginning with d_ are reserved for use in , but FreeBSD normally attempts to give strict POSIX.1 if _POSIX_SOURCE is defined. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 03:49:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA29509 for freebsd-current-outgoing; Fri, 22 Jan 1999 03:49:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA29497 for ; Fri, 22 Jan 1999 03:49:10 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id LAA59902; Fri, 22 Jan 1999 11:49:31 GMT Date: Fri, 22 Jan 1999 11:49:31 +0000 (GMT) From: Doug Rabson To: "David E. Cross" cc: current@FreeBSD.ORG Subject: Re: mountd In-Reply-To: <199901211554.KAA28454@cs.rpi.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 21 Jan 1999, David E. Cross wrote: > I posted this awhile ago to -questions, but never received a reply. > > We have a number of FreeBSD NFS servers here. Occasionally we need to > change the exports list on the servers and send mountd a SIGHUP. This > leads to a condition that in many ways is much worse than a server reboot. > > What happens is for the duration of mountd reading the exports file it denies > all NFS requests. This has a number of bad effects; 1) any user home and > system directories become unavailable, with the error 'permission denied' 2) > (and this is far worse), any process with a mapped .text segment off of the > NFS server, should it branch to code not in the cache gets immediately killed. > This include user processes that are running from home directories, and system > processes (such as ssh). If we were to reboot the machine it would just > hang those connections until the machine came back, without killing anyone. > > Is there a solution to this problem? I know that none of HP-UX, IRIX, or > Solaris have this problem. Please submit a PR for this (if there isn't one already) so at least it can be tracked. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 03:59:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA00498 for freebsd-current-outgoing; Fri, 22 Jan 1999 03:59:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [195.123.29.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA00493; Fri, 22 Jan 1999 03:59:01 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega.pfts.com (async2-53.iptelecom.net.ua [195.123.29.118]) by ipt2.iptelecom.net.ua (8.8.8/8.8.8) with ESMTP id NAA15084; Fri, 22 Jan 1999 13:58:50 +0200 (EET) (envelope-from sobomax@altavista.net) Received: from altavista.net (big_brother [192.168.1.1]) by vega.pfts.com (8.9.1/8.9.1) with ESMTP id NAA11261; Fri, 22 Jan 1999 13:58:10 +0200 (EET) (envelope-from sobomax@altavista.net) Message-ID: <36A867ED.8ADAC14C@altavista.net> Date: Fri, 22 Jan 1999 13:58:37 +0200 From: Maxim Sobolev X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: World broken in RELENG_3 when making aout-to-elf bulid Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, I have recent sources (cvsup'ed today) and make aout-to-elf broken with: ===> usr.bin/login cc -pipe -O2 -DCOMPAT_LINUX_THREADS -DVM_STACK -m486 -Wall -DLOGIN_ACCESS -DLOGALL   -I/usr/obj/aout/usr/obj/src/tmp/usr/include -c /usr/obj/src/usr.bin/login/login.c /usr/obj/src/usr.bin/login/login.c: In function `main': /usr/obj/src/usr.bin/login/login.c:129: warning: argument `argv' might be clobbered by `longjmp' or `vfork' cc -pipe -O2 -DCOMPAT_LINUX_THREADS -DVM_STACK -m486 -Wall -DLOGIN_ACCESS -DLOGALL   -I/usr/obj/aout/usr/obj/src/tmp/usr/include -c /usr/obj/src/usr.bin/login/login_access.c cc -pipe -O2 -DCOMPAT_LINUX_THREADS -DVM_STACK -m486 -Wall -DLOGIN_ACCESS -DLOGALL   -I/usr/obj/aout/usr/obj/src/tmp/usr/include -c /usr/obj/src/usr.bin/login/login_fbtab.c cc -pipe -O2 -DCOMPAT_LINUX_THREADS -DVM_STACK -m486 -Wall -DLOGIN_ACCESS -DLOGALL   -I/usr/obj/aout/usr/obj/src/tmp/usr/include  -o login login.o login_access.o login_fbtab.o  -lutil -lcrypt login.o: Undefined symbol `_pam_start' referenced from text segment login.o: Undefined symbol `_pam_strerror' referenced from text segment login.o: Undefined symbol `_pam_set_item' referenced from text segment login.o: Undefined symbol `_pam_strerror' referenced from text segment login.o: Undefined symbol `_pam_set_item' referenced from text segment login.o: Undefined symbol `_pam_strerror' referenced from text segment login.o: Undefined symbol `_pam_authenticate' referenced from text segment login.o: Undefined symbol `_pam_get_item' referenced from text segment login.o: Undefined symbol `_pam_strerror' referenced from text segment login.o: Undefined symbol `_pam_strerror' referenced from text segment login.o: Undefined symbol `_pam_end' referenced from text segment login.o: Undefined symbol `_pam_strerror' referenced from text segment login.o: Undefined symbol `_misc_conv' referenced from data segment *** Error code 1 Stop. Any glue??? Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 04:04:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA03040 for freebsd-current-outgoing; Fri, 22 Jan 1999 04:04:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA03035 for ; Fri, 22 Jan 1999 04:04:22 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id LAA59922; Fri, 22 Jan 1999 11:55:43 GMT Date: Fri, 22 Jan 1999 11:55:43 +0000 (GMT) From: Doug Rabson To: Julian Elischer cc: "Richard Seaman, Jr." , Jeremy Lea , freebsd-current@FreeBSD.ORG, Peter Wemm Subject: Re: Using LinuxThreads In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 21 Jan 1999, Julian Elischer wrote: > > > On Thu, 21 Jan 1999, Richard Seaman, Jr. wrote: > > > > And when are COMPAT_LINUX_THREADS and VM_STACK going away? > > > > I have no idea. I was hoping that at least COMPAT_LINUX_THREADS > > would go away before the branch. I don't have commit authority, > > so it isn't up to me. > > > > hmm did you send me the patches? > > I can certainly do it now..(given a patch set to apply) > > I just realised however, that if we make them go away we break > SMP right? > hmm I guess we only break it for programs that woudltry use it > which should be none if you run SMP :-) It doesn't break SMP (I'm running an SMP kernel with COMPAT_LINUX_THREADS). All that happens is that linux_clone() returns an error. Surprisingly StarOffice still works fairly well. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 04:53:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA12768 for freebsd-current-outgoing; Fri, 22 Jan 1999 04:53:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA12763 for ; Fri, 22 Jan 1999 04:53:11 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id HAA29657 for ; Fri, 22 Jan 1999 07:53:01 -0500 (EST) Date: Fri, 22 Jan 1999 07:53:01 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: current@FreeBSD.ORG Subject: kldload of procfs panics Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm having a bit of trouble with 4.0-CURRENT as of last night. After fully updating my system, on reboot procfs (a KLD module) panics the system as follows: (more explanation after bt) #9 0xf01d9c1a in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = -142545460, tf_esi = -250596864, tf_ebp = -142545512, tf_isp = -142545640, tf_ebx = 0, tf_edx = 0, tf_ecx = 0, tf_eax = 10, tf_trapno = 12, tf_err = 0, tf_eip = -266759770, tf_cs = 8, tf_eflags = 66134, tf_esp = 880, tf_ss = -147665856}) at ../../i386/i386/trap.c:437 #10 0xf01991a6 in ffs_read (ap=0xf780edb0) at ../../ufs/ufs/ufs_readwrite.c:97 #11 0xf0161bbd in vn_rdwr (rw=UIO_READ, vp=0xf732cc40, base=0xf1104000 "", len=880, offset=0x0000000000004418, segflg=UIO_SYSSPACE, ioflg=8, ---Type to continue, or q to quit--- cred=0xf05a0280, aresid=0xf780ee90, p=0xf7333620) at vnode_if.h:331 #12 0xf012d11f in link_elf_load_file (filename=0xf10a8d90 "procfs.ko", result=0xf780ef2c) at ../../kern/link_elf.c:635 #13 0xf012cb76 in link_elf_load_module (filename=0xf10a8d90 "procfs.ko", result=0xf780ef2c) at ../../kern/link_elf.c:340 #14 0xf012afa3 in linker_load_file (filename=0xf1104c00 "procfs", result=0xf780ef4c) at ../../kern/kern_linker.c:263 #15 0xf012b782 in kldload (p=0xf7333620, uap=0xf780ef84) at ../../kern/kern_linker.c:655 #16 0xf01da56f in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = -272638612, tf_esi = -1, tf_ebp = -272638580, tf_isp = -142544940, tf_ebx = -272638324, tf_edx = 99, tf_ecx = 10, tf_eax = 304, tf_trapno = 12, tf_err = 2, tf_eip = 134517080, tf_cs = 31, tf_eflags = 662, tf_esp = -272638620, tf_ss = 39}) at ../../i386/i386/trap.c:1100 #17 0xf01ccf2c in Xint0x80_syscall () #18 0x8048245 in ?? () #19 0x80480e9 in ?? () (kgdb) frame 10 #10 0xf01991a6 in ffs_read (ap=0xf780edb0) at ../../ufs/ufs/ufs_readwrite.c:97 97 if ((u_int64_t)uio->uio_offset > fs->fs_maxfilesize) (kgdb) printf "%p\n", fs 0x0 Now fs is part of strucct inode in the vnode, but struct inode seems to be TOTALLY ZERO! After rebooting, a fsck fixes all filesystems and the system boots fine, but on any _clean_ boot, procfs panics. I have absolutely no idea what could be causing this, but that I know procfs is the first module loaded and if I use the boot loader to load kernel+procfs first, nothing panics (e.g. kernfs). Anyone have an idea? Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 04:55:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA13069 for freebsd-current-outgoing; Fri, 22 Jan 1999 04:55:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA13064 for ; Fri, 22 Jan 1999 04:55:11 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id XAA23422; Fri, 22 Jan 1999 23:54:59 +1100 Date: Fri, 22 Jan 1999 23:54:59 +1100 From: Bruce Evans Message-Id: <199901221254.XAA23422@godzilla.zeta.org.au> To: current@FreeBSD.ORG, dawes@rf900.physics.usyd.edu.au Subject: Re: Promise FastTrack PCI IDE controller Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I've been playing with a Promise FastTrack RAID (IDE) controller with >3.0-current as of yesterday. Although it is recognised in the PCI bus >probe as a "Promise Ultra/33" (it has the same vendor/chip ID as the >non-RAID card), the probes in i386/isa/wd.c fail. I added some debugging >printfs to the code, and have found that wdreset() is failing. By >changing the code to ignore that failure, it gets further, and correctly >identifies the attached disks. I can even access the disks sufficiently >to read the partition table with fdisk (but with timeouts). Errors in wdreset() for the Promise (at least for the Ultra/33) probably mean that du->dk_altport is not initialized properly. (Setting du->dk_altport is the only thing that is very special for the Promise, and wdreset() is the only function that uses du->dk_altport for anything except debugging.) The wrong setting of du->dk_altport may be caused by the section of code in pci/ide_pci.c described by "/* This code below is mighty bogus. ...". Bugs there may also break DMA capability. >... >promise_status: port0: 0xeff0, port0_alt: 0xefe4, port1: 0xefa8, port1_alt: 0xefe0 >... >wdc2: wdd_candma is set for ide_pci1 >wdc2: I/O to 0xeff0 does work >wdc2: reset failed If the main block of ports is really at 0xeff0, as it probably must be since something worked, the altport is probably at port 0xefe4 and initializing du->dk_altport to this manually should fix wdreset(). >ide_pci: generic_dmainit eff0:0: warning, IDE controller timing not set >wd4: wdsetmode() setting transfer mode to 22 I don't see how the Promise can work right if generic_dmainit() gets called. generic_dmainit() never sets UltraDMA mode. It only sets mode 22, which is twice as slow. There is no special support for seting the IDE controller timing for the Promise, so generic_dmainit() gets called unless the BIOS has already set the IDE controller timing. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 05:23:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA15357 for freebsd-current-outgoing; Fri, 22 Jan 1999 05:23:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.128.29.136]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA15351 for ; Fri, 22 Jan 1999 05:23:24 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: (from mi@localhost) by kot.ne.mediaone.net (8.9.1a/8.9.1) id IAA00282 for current@freebsd.org; Fri, 22 Jan 1999 08:22:57 -0500 (EST) From: Mikhail Teterin Message-Id: <199901221322.IAA00282@kot.ne.mediaone.net> Subject: zip drive and parallel port in NIBBLE mode hang the machine To: current@FreeBSD.ORG Date: Fri, 22 Jan 1999 08:22:56 -0500 (EST) Reply-To: mi@kot.ne.mediaone.net X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA18916 for freebsd-current-outgoing; Fri, 22 Jan 1999 05:53:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from megaweapon.zigg.com (megaweapon.zigg.com [206.114.60.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA18911 for ; Fri, 22 Jan 1999 05:53:28 -0800 (PST) (envelope-from matt@zigg.com) Received: from localhost (matt@localhost) by megaweapon.zigg.com (8.9.2/8.9.2) with ESMTP id IAA83728 for ; Fri, 22 Jan 1999 08:49:17 -0500 (EST) (envelope-from matt@zigg.com) Date: Fri, 22 Jan 1999 08:49:16 -0500 (EST) From: Matt Behrens To: FreeBSD-Current Subject: Re: 0112-SNAP system hangs w/ incessant disk activity - softupdates related? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-2122900727-917012956=:81847" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-2122900727-917012956=:81847 Content-Type: TEXT/PLAIN; charset=US-ASCII Attached is a DDB trace that I obtained the next morning after I posted the original message. FWIW, I've been running without softupdates now since rebooting after that crash Monday morning, and everything is running beautifully (albeit a bit more slowly) :) mounted default. I hope this can help. I hear there are a lot of these traces floating around that maybe can be pieced together. I've since switched to 3.0-STABLE (though make world isn't quite done yet), so I don't follow -current anymore -- but I figured -current would be the best place to put this so that it can be fixed in -CURRENT and backported. Thanks. On Sun, 17 Jan 1999, Matt Behrens wrote: : The system becomes totally unresponsive (console driver still seems : to be running but the processes all seem to have hung) at some : random point. The second time, I noticed my second hard drive was : going totally crazy -- sounded like a `find /' or something. :) : In both cases, I couldn't Ctrl-Alt-Del, so I rebooted. : : The first time, I didn't know what to expect -- but the standard : fsck-if-not-clean "took care" of my problem on reboot. I didn't : get to see many of the messages, but I did catch quite a few (and : on the tail) clearing of unref files, many owned by me. They seemed : to (and indeed did) correspond to some files that I was unpacking. : Attributing it to just running into a random bug, I re-unpacked : the files and went on. - Matt Behrens Network Administrator, zigg.com Engineer, Nameless IRC Network --0-2122900727-917012956=:81847 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="softupdates_ddb_trace.txt" Content-ID: Content-Description: DDB trace with softupdates on Content-Disposition: attachment; filename="softupdates_ddb_trace.txt" Content-Transfer-Encoding: BASE64 RGVidWdnZXIoZjAyMWY4NjUpIGF0IERlYnVnZ2VyKzB4MzcNCnNjX2FsbG9j X2hpc3RvcnlfYnVmZmVyKGYwMjUyNjdjLDIsMCxmMDI1MjY3Yyw3MDExZCkg YXQgc2NfYWxsb2NfaGlzdG9yeV9idWZmZXIrMHhjZDANCnNjZGV2dG90dHko ZjAyNTI2N2MsMCwwLDAsZjA2MTJjMDApIGF0IHNjZGV2dG90dHkrMHgzNWMN CmF0a2JkX2F0dGFjaF91bml0KGYwMjUyNjdjLDAsMCxmMzJiN2UyNCxmMDFl ZmZjZSkgYXQgYXRrYmRfYXR0YWNoX3VuaXQrMHg0ZTcNCmlzX3BoeXNpY2Fs X21lbW9yeSgwLGMwMDg0MDQwLGYwNjEwMDEwLGYwMTMwMDEwLDcwMTFkKSBh dCBpc19waHlzaWNhbF9tZW1vcnkrMHgyY2MNClhpbnRyMSgwLDAsZjAxYTcx ODgsYzAwMDAwMDAsMCkgYXQgWGludHIxKzB4NWUNCndkaW50cigwLGMwMDAw MDAwLGYwNjEwMDEwLDEwLGMwMDAwMDAwKSBhdCB3ZGludHIrMHg1YjgNClhp bnRyMTQoODAwMDAwMDAsZjMyYjAwMTAsZjAxZDAwMTAsZjMyYjdmODgsZjMy YTYyMDApIGF0IFhpbnRyMTQrMHg2MQ0KZG9yZXRpX3BvcGxfZXNfZmF1bHQo ZjMyYjdmODgpIGF0IGRvcmV0aV9wb3BsX2VzX2ZhdWx0KzB4NDkNCnZuX3N5 bmNlcl9hZGRfdG9fd29ya2xpc3QoZjMyYWJiZjcsZjAyMTkyYTUsZjAyMzA1 ODgsZjAxZjMwZnMsZjAxZWY1YzApIGF0IHZuX3N5bmNlcl9hZGRfdG9fd29y a2xpc3QrMHgxM2MNCmtwcm9jX3N0YXJ0KGYwMjMwNTg4KSBhdCBrcHJvY19z dGFydCsweDMyDQpmb3JrX3RyYW1wb2xpbmUoZTRlYzE1ODksYzc2NmYwMjUs MjVlNGVlMDUsODAwMDA4ZjAsMjVlNGYwMjUpIGF0IGZvcmtfdHJhbXBvbGlu ZSsweDMwDQo= --0-2122900727-917012956=:81847-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 05:56:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA19273 for freebsd-current-outgoing; Fri, 22 Jan 1999 05:56:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from server.noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA19266 for ; Fri, 22 Jan 1999 05:56:46 -0800 (PST) (envelope-from fanf@demon.net) Received: by server.noc.demon.net; id NAA14000; Fri, 22 Jan 1999 13:56:35 GMT Received: from fanf.noc.demon.net(195.11.55.83) by inside.noc.demon.net via smap (3.2) id xma013983; Fri, 22 Jan 99 13:56:24 GMT Received: from fanf by fanf.noc.demon.net with local (Exim 1.73 #2) id 103h4S-0004Jv-00; Fri, 22 Jan 1999 13:56:24 +0000 To: current@FreeBSD.ORG From: Tony Finch Subject: Re: -D_REENTRANT (Was: Using LinuxThreads) Newsgroups: chiark.mail.freebsd.current In-Reply-To: <36A7A395.29B3E8A7@OpenLDAP.Org> Organization: Deliberate Obfuscation To Amuse Tony References: <19990119091151.F600@tar.com> <19990118182717.A15566@top.worldcontrol.com> <19990119024539.A88383@top.worldcontrol.com> <19990119140613.B826@shale.csir.co.za> <19990119091151.F600@tar.com> <19990121181228.A98581@shale.csir.co.za> <3.0.5.32.19990121114214.00958c30@localhost> <19990121143940.D5495@tar.com> Message-Id: Date: Fri, 22 Jan 1999 13:56:24 +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Kurt D. Zeilenga" wrote: >"Richard Seaman, Jr." wrote: >> [lost attribution] >> > Also, the cc(1) says to use -D_THREADSAFE not -D_THREAD_SAFE. >> Hmm. Not on my machine. :) > >http://www.freebsd.org/cgi/man.cgi?query=cc&apropos=0&sektion=0&manpath=FreeBSD+3.0-current&format=html This was changed some time after 3.0.0. http://www.freebsd.org/cgi/cvsweb.cgi/src/contrib/gcc/gcc.1 Tony. -- f.a.n.finch dot@dotat.at fanf@demon.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 06:20:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA21909 for freebsd-current-outgoing; Fri, 22 Jan 1999 06:20:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA21898 for ; Fri, 22 Jan 1999 06:20:42 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id XAA01682; Fri, 22 Jan 1999 23:18:57 +0900 (JST) Message-ID: <36A88573.AAB48B54@newsguy.com> Date: Fri, 22 Jan 1999 23:04:35 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Sheldon Hearn CC: Ying-Chieh Liao , Tim , freebsd-current@FreeBSD.ORG Subject: Re: PNP and new bootloader with ELF kernel References: <183.917000518@axl.noc.iafrica.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > > On Fri, 22 Jan 1999 12:22:26 +0800, Ying-Chieh Liao wrote: > > > you can put this pnp information in /kernel.config > > and, in your /boot/boot.conf, put > > > > load /kernel > > load -t userconfig_script /kernel.config > > boot > > Hi chaps, > > Try to encourage current users to use /boot/loader.rc instead. We don't > want kernel.config anymore, from what I've read on this list. What should have changed up there is "boot.conf". The /kernel.config is, as a matter of fact, correct. The commands you place in it are, as you can see, "userconfig_script", not loader script. That's why you are placing them there, not in boot.rc. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com If you sell your soul to the Devil and all you get is an MCSE from it, you haven't gotten market rate. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 06:27:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA22282 for freebsd-current-outgoing; Fri, 22 Jan 1999 06:27:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA22263 for ; Fri, 22 Jan 1999 06:26:50 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.10 #1) id 103hWW-000074-00 for current@freebsd.org; Fri, 22 Jan 1999 16:25:24 +0200 From: Sheldon Hearn To: current@FreeBSD.ORG Subject: WARNING: Today's current breaks passwords Date: Fri, 22 Jan 1999 16:25:24 +0200 Message-ID: <437.917015124@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This may or may not affect you. Today's installworld broke passwords for me. By that, I mean that login, xdm, su and friends gave authentication failures on all passwords for all users that I tried. I suspect this has to do with a hashing algorithm that isn't backward compatible. I used Kerberos to get into the machine as root and change important passwords to exactly what they were before. This worked. The new encrypted passwords are happy. :) I don't want to cause hysteria, and I can't guarantee that my report is accurate. All the same, do yourself a favour on your next installworld: Make SURE you have an open root session somewhere. Do NOT hide it behind xlock, and do NOT use lock(1) to keep it safe. This will allow you to passwd(1) to create new encrypted passwords for your users. If you have shell accounts that need access to the box and you don't want to have to rehash all their passwords, hold off on installworld until someone calls me a liar, or a fix is committed. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 06:32:01 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA22624 for freebsd-current-outgoing; Fri, 22 Jan 1999 06:30:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA22576 for ; Fri, 22 Jan 1999 06:30:35 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.2/8.9.1) id IAA75697; Fri, 22 Jan 1999 08:30:21 -0600 (CST) (envelope-from dick) Date: Fri, 22 Jan 1999 08:30:21 -0600 From: "Richard Seaman, Jr." To: "Russell L. Carter" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Using LinuxThreads Message-ID: <19990122083021.E5495@tar.com> References: <199901220239.TAA06788@psf.Pinyon.ORG> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199901220239.TAA06788@psf.Pinyon.ORG>; from Russell L. Carter on Thu, Jan 21, 1999 at 07:39:28PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 21, 1999 at 07:39:28PM -0700, Russell L. Carter wrote: > dick@tar.com said: > %libc_r could be modified so that is doesn't replace libc, but rather > %is an addon, comparable to the kernel threaded libc case. But, it > %would involve a bit of work. > > I thought so at first, but then I had to look at wait4 today and > now I'm not so sure. At least some of libc_r is very closely > tied to the uthread scheduler: Sure it is. But, I don't see why that prevents the possibility of leaving libc in place and having libc_r just be an add on (not that I'm advocating this). Taking your example, in libc the syscall is implemented as _wait4, and wait4 is a weak alias to _wait4. If you replaced _thread_sys_wait4 below with _wait4 instead, and put the resulting code in a library separate from libc (eg. in a "new" libc_r) along with the uthread scheduling code and the rest of the uthread pthread code, you could leave libc alone. Then, when you linked with libc and libc_r together, the wait4 in libc_r would override the weak aliased wait4 in libc. If you didn't link with libc_r, you'd have your plain old wait4. The bigger problem is that the uthread code needs "two layer" aliasing in order to implement pthread cancellation. > pid_t > wait4(pid_t pid, int *istat, int options, struct rusage * rusage) > { > pid_t ret; > > /* Perform a non-blocking wait4 syscall: */ > while ((ret = _thread_sys_wait4(pid, istat, options | WNOHANG, > rusage)) == 0 && (options & WNOHANG) == 0) { > /* Reset the interrupted operation flag: */ > _thread_run->interrupted = 0; > > /* Schedule the next thread while this one waits: */ > _thread_kern_sched_state(PS_WAIT_WAIT, __FILE__, __LINE__); > > /* Check if this call was interrupted by a signal: */ > if (_thread_run->interrupted) { > errno = EINTR; > ret = -1; > break; > } > } > return (ret); > } > #endif -- Richard Seamman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 06:51:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA24419 for freebsd-current-outgoing; Fri, 22 Jan 1999 06:51:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [195.123.29.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA24399 for ; Fri, 22 Jan 1999 06:51:38 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega.pfts.com (async2-53.iptelecom.net.ua [195.123.29.118]) by ipt2.iptelecom.net.ua (8.8.8/8.8.8) with ESMTP id QAA27109; Fri, 22 Jan 1999 16:51:21 +0200 (EET) (envelope-from sobomax@altavista.net) Received: from altavista.net (big_brother [192.168.1.1]) by vega.pfts.com (8.9.1/8.9.1) with ESMTP id QAA29335; Fri, 22 Jan 1999 16:51:14 +0200 (EET) (envelope-from sobomax@altavista.net) Message-ID: <36A8907C.828FE9AF@altavista.net> Date: Fri, 22 Jan 1999 16:51:40 +0200 From: Maxim Sobolev X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: Sheldon Hearn CC: current@FreeBSD.ORG Subject: Re: WARNING: Today's current breaks passwords References: <437.917015124@axl.noc.iafrica.com> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maybe your have switched between hashing modes (DES->MD5 or MD5->DES)? Because hashing algorithms doesn't changing without a wide notification has been made. Please check handbook on this subj. Maxim Sheldon Hearn wrote: > This may or may not affect you. > > Today's installworld broke passwords for me. By that, I mean that login, > xdm, su and friends gave authentication failures on all passwords for > all users that I tried. I suspect this has to do with a hashing > algorithm that isn't backward compatible. > > I used Kerberos to get into the machine as root and change important > passwords to exactly what they were before. This worked. The new > encrypted passwords are happy. :) > > I don't want to cause hysteria, and I can't guarantee that my report is > accurate. All the same, do yourself a favour on your next installworld: > >         Make SURE you have an open root session somewhere. Do NOT hide >         it behind xlock, and do NOT use lock(1) to keep it safe. > >         This will allow you to passwd(1) to create new encrypted >         passwords for your users. > >         If you have shell accounts that need access to the box and you >         don't want to have to rehash all their passwords, hold off on >         installworld until someone calls me a liar, or a fix is >         committed. > > Ciao, > Sheldon. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 06:58:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA25170 for freebsd-current-outgoing; Fri, 22 Jan 1999 06:58:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA25162 for ; Fri, 22 Jan 1999 06:58:21 -0800 (PST) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.8.8/8.8.5) with SMTP id UAA09250; Fri, 22 Jan 1999 20:56:47 +0600 (NS) Date: Fri, 22 Jan 1999 20:56:46 +0600 (NS) From: Max Khon To: Sheldon Hearn cc: current@FreeBSD.ORG Subject: Re: WARNING: Today's current breaks passwords In-Reply-To: <437.917015124@axl.noc.iafrica.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! On Fri, 22 Jan 1999, Sheldon Hearn wrote: > This may or may not affect you. > > Today's installworld broke passwords for me. By that, I mean that login, > xdm, su and friends gave authentication failures on all passwords for > all users that I tried. I suspect this has to do with a hashing > algorithm that isn't backward compatible. is RELENG_3 affected too? /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 07:03:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA25876 for freebsd-current-outgoing; Fri, 22 Jan 1999 07:03:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA25849 for ; Fri, 22 Jan 1999 07:03:19 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.2/8.9.1) id JAA75832; Fri, 22 Jan 1999 09:01:34 -0600 (CST) (envelope-from dick) Date: Fri, 22 Jan 1999 09:01:34 -0600 From: "Richard Seaman, Jr." To: Jeremy Lea Cc: freebsd-current@FreeBSD.ORG Subject: Re: Using LinuxThreads Message-ID: <19990122090134.F5495@tar.com> References: <19990118182717.A15566@top.worldcontrol.com> <19990119024539.A88383@top.worldcontrol.com> <19990119140613.B826@shale.csir.co.za> <19990119091151.F600@tar.com> <19990121181228.A98581@shale.csir.co.za> <19990121123814.B5495@tar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <19990121123814.B5495@tar.com>; from Richard Seaman, Jr. on Thu, Jan 21, 1999 at 12:38:14PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 21, 1999 at 12:38:14PM -0600, Richard Seaman, Jr. wrote: > On Thu, Jan 21, 1999 at 06:12:29PM +0200, Jeremy Lea wrote: > > > On Tue, Jan 19, 1999 at 09:11:51AM -0600, Richard Seaman, Jr. wrote: > > > Actually, the new version, in FreeBSD "ports" form, doesn't require > > > -DLINUXTHREADS anymore, but it does require -I/usr/local/include to > > > pick up the right header, since it installs a pthread.h into > > > /usr/local/include. This conflicts with the pthread.h in /usr/include. > > > > This is nagging at me. Having two headers of the same name, but importantly > > different content is asking for touble. There needs to be a way to ensure > > that only one or the other is picked up. The best way I can think of is to > > only include the contents of the user thread pthread.h if _THREAD_SAFE is > > defined (to force people to use the right defines...) and the contents of > > kernel thread pthread.h if _REENTRANT (and not _THREAD_SAFE) is defined. > > This has the added bonus of meaning that most linux apps wont have to be > > patched. > Now, on the topic of conflicting pthread.h files, I agree this is a > problem. One choice, which I originally implemented, is to fix > pthread.h so it pulls in the right data based on a swtich (eg. > if LINUXTHREADS is defined, pull in LT headers, else pull in > user threads headers). I don't like using _THREAD_SAFE for this > test, for the reason mentioned above. And I don't like using > _REENTRANT because its so widely used and it could still confure > people. > > The second choice, which is what the current version of the "port" > does, is to put the conflicting headers in different directories, > and require the application to define the order of the include > files to get the right one in. > > There are proglems either way, and I don't really prefer one > over the other. Upon further investigation, I'm not sure I agree with myself on this point anymore. I've been trying to get gimp compiled to look into the reported problem Brian Litzinger had. I notice that glib, gtk+ (both needed for gimp) and gimp itself generate include search paths that include /usr/local/include, which means that the linuxthreads pthread.h will get picked up even if the user wants the uthread version in /usr/include. Maybe having just one pthread.h that pulls in the required headers based on a switch (eg. -DLINUXTHREADS) is the way to go? -- Richard Seamman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 07:18:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA27709 for freebsd-current-outgoing; Fri, 22 Jan 1999 07:18:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA27704 for ; Fri, 22 Jan 1999 07:18:25 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.10 #1) id 103iKe-0000DO-00; Fri, 22 Jan 1999 17:17:12 +0200 From: Sheldon Hearn To: Maxim Sobolev cc: current@FreeBSD.ORG Subject: Re: WARNING: Today's current breaks passwords In-reply-to: Your message of "Fri, 22 Jan 1999 16:51:40 +0200." <36A8907C.828FE9AF@altavista.net> Date: Fri, 22 Jan 1999 17:17:12 +0200 Message-ID: <829.917018232@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 22 Jan 1999 16:51:40 +0200, Maxim Sobolev wrote: > Maybe your have switched between hashing modes (DES->MD5 or MD5->DES)? Possibly that's what's happened, but it certainly isn't something I did deliberately. > Because hashing algorithms doesn't changing without a wide > notification has been made. Please check handbook on this subj. Really? You been watching your cvs commit mail? :) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 07:24:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA28302 for freebsd-current-outgoing; Fri, 22 Jan 1999 07:24:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.sitaranetworks.com (apollo.sitaranetworks.com [199.103.141.105]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA28235 for ; Fri, 22 Jan 1999 07:24:26 -0800 (PST) (envelope-from loverso@sitara.net) Received: from sitara.net (jamaica.sitaranetworks.com [199.103.141.147]) by apollo.sitaranetworks.com (8.9.1a/8.9.1) with ESMTP id KAA05863; Fri, 22 Jan 1999 10:09:32 -0500 (EST) Message-ID: <36A89597.98108990@sitara.net> Date: Fri, 22 Jan 1999 10:13:27 -0500 From: "John R. LoVerso" Reply-To: loverso@sitaranetworks.com Organization: Sitara Networks, http://surf.to/loverso/ X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Konstantin Chuguev CC: freebsd-current@FreeBSD.ORG Subject: Re: T/TCP in FreeBSD-3.x References: <36A85EF1.444A86B@urc.ac.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Why I'm asking about this, is because I recently read an advice in one > of the FreeBSD mailing lists, > about "Why my dial-up PPP connection from a FreeBSD box is so slow > comparing with Windows NT > (about ten times slower)?" > > And the advice was (without explanations): "Try to switch off the > TCP_EXTENSIONS in /etc/rc.conf". This isn't something that can be fixed in FreeBSD's TCP. Rather, it is a general bug in how TCP Header Compression is defined for PPP and SLIP. Basically, TCP Header Compression will not compress any TCP segment that contains a TCP option. This means the use of ANY TCP option, whether T/TCP or RTTM, will cause your PPP links to not compress those packets and, thus, make your link slower. Unfortunately, just fixing FreeBSD isn't the answer, because you need to fix EVERY implementation of PPP to accept and generate TCP segments with options. The new "IP Header Compression" Internet Draft specifies how this is to be done. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 07:51:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA01649 for freebsd-current-outgoing; Fri, 22 Jan 1999 07:51:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA01640 for ; Fri, 22 Jan 1999 07:51:04 -0800 (PST) (envelope-from jfieber@fallout.campusview.indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.9.1/8.9.1) with ESMTP id KAA78638; Fri, 22 Jan 1999 10:50:50 -0500 (EST) Date: Fri, 22 Jan 1999 10:50:49 -0500 (EST) From: John Fieber To: Kazutaka YOKOTA cc: current@FreeBSD.ORG Subject: Re: keymaps In-Reply-To: <199901220815.RAA15900@zodiac.mech.utsunomiya-u.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 22 Jan 1999, Kazutaka YOKOTA wrote: > Gentlemen, I don't intend to add yet another keymap to > /usr/share/syscons/keymaps. I am merely trying to define a reasonable > set of common, consistent key binding for existing keymaps. > > National keyboards have different layout of regular keys. But > function keys and special keys are placed identically. They should > work in the same way, or at least similar way in all keyboards, unless > there is a good reason to do otherwise. (I am not talking about > non-AT keyboards which are totally different from either AT 84 or > 101/102/104 keyboards.) What would be useful here is the ability to "compose" keymaps. There would be basically two sets: one that defines the layout of the main keyboard and one that defines the layout of the other keys. That way I could pick my dvorak layout, then add on a layout that, say, swaps control and caps lock but leaves the main layout alone. -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 08:01:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA02315 for freebsd-current-outgoing; Fri, 22 Jan 1999 08:01:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA02310 for ; Fri, 22 Jan 1999 08:01:18 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.8.6/8.8.6) with ESMTP id RAA22900 for ; Fri, 22 Jan 1999 17:01:07 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.2/8.9.2) id RAA19118 for current@FreeBSD.ORG; Fri, 22 Jan 1999 17:00:52 +0100 (CET) (envelope-from andreas) Date: Fri, 22 Jan 1999 17:00:52 +0100 From: Andreas Klemm To: current@FreeBSD.ORG Subject: make release, kernel.flp mfsroot.flp from Jan 21th doesn't work as well Message-ID: <19990122170052.A19090@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-STABLE SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ho ! Someone recommended me a week or so ago, to use the "2 floppy install". Did so now with a FreeBSD 3.0-SNAP from Jan 21 1999. No success: my notebook 'sits' beneath me and tells me the following after inserting the 2nd floppy: zf_read: fill error .... .... [cpu register contents deleted] .... System halted JFYI -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 08:15:38 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA03692 for freebsd-current-outgoing; Fri, 22 Jan 1999 08:15:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA03687 for ; Fri, 22 Jan 1999 08:15:33 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.8.6/8.8.6) with ESMTP id RAA23186 for ; Fri, 22 Jan 1999 17:15:21 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.2/8.9.2) id RAA19509; Fri, 22 Jan 1999 17:15:05 +0100 (CET) (envelope-from andreas) Date: Fri, 22 Jan 1999 17:15:05 +0100 From: Andreas Klemm To: Andreas Klemm Cc: current@FreeBSD.ORG Subject: Re: make release, kernel.flp mfsroot.flp from Jan 21th doesn't work as well Message-ID: <19990122171505.A19455@titan.klemm.gtn.com> References: <19990122170052.A19090@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990122170052.A19090@titan.klemm.gtn.com>; from Andreas Klemm on Fri, Jan 22, 1999 at 05:00:52PM +0100 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-STABLE SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 22, 1999 at 05:00:52PM +0100, Andreas Klemm wrote: > Hi ho ! > > Someone recommended me a week or so ago, to use the "2 floppy install". > Did so now with a FreeBSD 3.0-SNAP from Jan 21 1999. > No success: my notebook 'sits' beneath me and tells me the following > after inserting the 2nd floppy: > > zf_read: fill error > .... > .... [cpu register contents deleted] > .... > System halted Sorry ! This was because of an read error on the floppy ! Please give me the hat ;-) -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 08:30:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA05306 for freebsd-current-outgoing; Fri, 22 Jan 1999 08:30:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA05301 for ; Fri, 22 Jan 1999 08:30:29 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id LAA10394; Fri, 22 Jan 1999 11:28:49 -0500 (EST) Date: Fri, 22 Jan 1999 11:28:48 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Doug Rabson cc: Julian Elischer , "Richard Seaman, Jr." , Jeremy Lea , freebsd-current@FreeBSD.ORG, Peter Wemm Subject: Re: Using LinuxThreads In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 22 Jan 1999, Doug Rabson wrote: > On Thu, 21 Jan 1999, Julian Elischer wrote: > > > > > > > On Thu, 21 Jan 1999, Richard Seaman, Jr. wrote: > > > > > > And when are COMPAT_LINUX_THREADS and VM_STACK going away? > > > > > > I have no idea. I was hoping that at least COMPAT_LINUX_THREADS > > > would go away before the branch. I don't have commit authority, > > > so it isn't up to me. > > > > > > > hmm did you send me the patches? > > > > I can certainly do it now..(given a patch set to apply) > > > > I just realised however, that if we make them go away we break > > SMP right? > > hmm I guess we only break it for programs that woudltry use it > > which should be none if you run SMP :-) > > It doesn't break SMP (I'm running an SMP kernel with > COMPAT_LINUX_THREADS). All that happens is that linux_clone() returns > an error. Surprisingly StarOffice still works fairly well. StarOffice 5.0? Is this with Luoqi's shared process across SMP patches? > > -- > Doug Rabson Mail: dfr@nlsystems.com > Nonlinear Systems Ltd. Phone: +44 181 442 9037 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 09:07:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08875 for freebsd-current-outgoing; Fri, 22 Jan 1999 09:07:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bastuba.partitur.se (bastuba.partitur.se [193.219.246.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA08865 for ; Fri, 22 Jan 1999 09:07:06 -0800 (PST) (envelope-from girgen@partitur.se) Received: from partitur.se (solist.partitur.se [193.219.246.204]) by bastuba.partitur.se (8.8.8/8.8.8) with ESMTP id QAA23567 for ; Fri, 22 Jan 1999 16:11:48 +0100 (CET) (envelope-from girgen@partitur.se) Message-ID: <36A89532.97D035B5@partitur.se> Date: Fri, 22 Jan 1999 16:11:46 +0100 From: Palle Girgensohn Organization: Partitur X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.6 sun4u) X-Accept-Language: sv, en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: netd in free(): warning: junk pointer, too low to make sense. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I'm experiencing some strange errors with one of our workstations. I recently moved all of our workstations to 3.0 current as of 1998-12-18. Does any of this make any sense to anyone: trumpet:~>rlogin balalaika netd in free(): warning: junk pointer, too low to make sense. trumpet:~>telnet balalaika Trying 1.2.3.4... Connected to balalaika.partitur.se. Escape character is '^]'. inetd in free(): warning: junk pointer, too low to make sense. inetd in free(): warning: junk pointer, too high to make sense. inetd in free(): warning: junk pointer, too high to make sense. inetd in free(): warning: junk pointer, too high to make sense. inetd in free(): warning: junk pointer, too low to make sense. inetd in free(): warning: junk pointer, too high to make sense. inetd in free(): warning: junk pointer, too high to make sense. inetd in free(): warning: junk pointer, too high to make sense. inetd in free(): warning: junk pointer, too low to make sense. inetd in free(): warning: junk pointer, too high to make sense. inetd in free(): warning: junk pointer, too high to make sense. inetd in free(): warning: junk pointer, too high to make sense. inetd in free(): warning: junk pointer, too low to make sense. inetd in free(): warning: junk pointer, too high to make sense. inetd in free(): warning: junk pointer, too low to make sense. FreeBSD/i386 (balalaika.partitur.se) (ttyp2) login: username Ok... I get in... If I'm lucky. Sometimes not at all. Besides, it acts a little strange. For example, here's what newsyslog told me recently: newsyslog: preposterous process number: 77243 newsyslog: log not compressed because daemon not notified Restarting inetd fixes the problem with rlogin/telnet, but it is bound to come back within a day or so. My guess is that this started when we started using samba on the machine, for sharing some simple stuff to windows machines. The samba has probably not been recompiled since our elf transition (our server uses the same binaries, and serves them via nfs to the troubled machine), so there shouldn't be a problem. Anyway, I fetched the brand new 2.0 port of samba, but still have problems. I haven't modified the smb.conf, though. It seems at first that it is the inetd that has some kind of memory leak, but I really don't like that idea. Well... Any ideas appreciated. Get back if you need more input. uname -a: FreeBSD balalaika.partitur.se 3.0-CURRENT FreeBSD 3.0-CURRENT #1: Thu Jan 7 01:16:11 CET 1999 girgen@trumpet.partitur.se:/disk3/src/sys/compile/WORKSTATION i386 Oh, one more thing: There are five machines installed from the same build (built on the server, installed to all the boxes). The others work just fine. Regards, Palle To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 09:16:57 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09973 for freebsd-current-outgoing; Fri, 22 Jan 1999 09:16:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA09883 for ; Fri, 22 Jan 1999 09:16:44 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id MAA67012; Fri, 22 Jan 1999 12:22:28 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Fri, 22 Jan 1999 12:22:28 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Palle Girgensohn cc: freebsd-current@FreeBSD.ORG Subject: Re: netd in free(): warning: junk pointer, too low to make sense. In-Reply-To: <36A89532.97D035B5@partitur.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 22 Jan 1999, Palle Girgensohn wrote: > Hi! > > I'm experiencing some strange errors with one of our workstations. I > recently moved all of our workstations to 3.0 current as of 1998-12-18. > Does any of this make any sense to anyone: > > trumpet:~>rlogin balalaika > netd in free(): warning: junk pointer, too low to make sense. check the archives of -current, i think this was fixed after the date of your build. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 4.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 09:19:42 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10386 for freebsd-current-outgoing; Fri, 22 Jan 1999 09:19:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-54-dbn.dial-up.net [196.34.155.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA10374 for ; Fri, 22 Jan 1999 09:19:29 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id TAA00398; Fri, 22 Jan 1999 19:18:14 +0200 (SAT) From: Robert Nordier Message-Id: <199901221718.TAA00398@ceia.nordier.com> Subject: Re: make release, kernel.flp mfsroot.flp from Jan 21th doesn't work as well In-Reply-To: <19990122171505.A19455@titan.klemm.gtn.com> from Andreas Klemm at "Jan 22, 99 05:15:05 pm" To: andreas@klemm.gtn.com (Andreas Klemm) Date: Fri, 22 Jan 1999 19:18:11 +0200 (SAT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andreas Klemm wrote: > On Fri, Jan 22, 1999 at 05:00:52PM +0100, Andreas Klemm wrote: > > Hi ho ! > > > > Someone recommended me a week or so ago, to use the "2 floppy install". > > Did so now with a FreeBSD 3.0-SNAP from Jan 21 1999. > > No success: my notebook 'sits' beneath me and tells me the following > > after inserting the 2nd floppy: > > > > zf_read: fill error > > .... > > .... [cpu register contents deleted] > > .... > > System halted > > Sorry ! This was because of an read error on the floppy ! > > Please give me the hat ;-) No, you don't deserve it. :-) /boot/loader should *not* become so confused that it has to be killed by BTX, just because of an I/O error. Bad floppies are common and this is a reproducible bug that needs fixing. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 09:24:02 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10785 for freebsd-current-outgoing; Fri, 22 Jan 1999 09:24:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from h24-64-221-247.gv.wave.shaw.ca (h24-64-221-247.gv.wave.shaw.ca [24.64.221.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA10763 for ; Fri, 22 Jan 1999 09:23:59 -0800 (PST) (envelope-from jake@h24-64-221-247.gv.wave.shaw.ca) Received: from h24-64-221-247.gv.wave.shaw.ca (localhost [127.0.0.1]) by h24-64-221-247.gv.wave.shaw.ca (8.9.2/8.9.2) with ESMTP id JAA01151; Fri, 22 Jan 1999 09:23:48 -0800 (PST) (envelope-from jake@h24-64-221-247.gv.wave.shaw.ca) Message-Id: <199901221723.JAA01151@h24-64-221-247.gv.wave.shaw.ca> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG cc: grog@lemis.com Subject: vinum read no longer works Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 22 Jan 1999 09:23:48 -0800 From: Jake Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I can no longer bring up my vinum volume with the vinum read command: vinum read /dev/wd0s1e /dev/wd2s1f vinum read /dev/wd0s1e vinum read /dev/wd2s1f all come back with vinum: no drives I understand that all slices belonging to a volume must now be passed to read, but that doesn't make any difference. I've modified /etc/rc to do a vinum create /etc/vinum.conf instead and that works, but I thought read was the correct commmand. 4.0-current as of yesterday, previously running 3.0-current as of the 19th. /etc/vinum.conf: drive drive1 device /dev/wd0s1e drive drive2 device /dev/wd2s1f volume usrc plex org striped 512b sd length 1g drive drive1 sd length 1g drive drive2 h24-64-221-247# vinum list Configuration summary Drives: 2 (4 configured) Volumes: 1 (4 configured) Plexes: 1 (8 configured) Subdisks: 2 (16 configured) D drive1 State: up Device /dev/wd0s1e D drive2 State: up Device /dev/wd2s1f V usrc State: up Plexes: 1 Size: 2048 MB P usrc.p0 S State: up Subdisks: 2 Size: 2048 MB S usrc.p0.s0 State: up PO: 0 B Size: 1024 MB S usrc.p0.s1 State: up PO: 256 kB Size: 1024 MB relevant changes to /etc/rc: if [ -f /etc/vinum.conf ]; then if [ -r /modules/vinum.ko ]; then # jkh paranoia kldload vinum vinum create /etc/vinum.conf 2>&1 > /dev/null else echo "Can't find /modules/vinum.ko" fi fi also, I suggest that something like the following patch be applied to /etc/rc once the read command works again, it allows the "vinum on startup" knob to function. rc.conf must be read in before vinum is started, or $vinum_slices is not initialized. --- rc.orig Wed Jan 20 04:30:13 1999 +++ rc Fri Jan 22 09:10:18 1999 @@ -22,11 +22,23 @@ PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin export PATH +# If there is a global system configuration file, suck it in. +if [ -f /etc/rc.conf ]; then + . /etc/rc.conf +fi + +# If old file exists, whine until they fix it. +if [ -f /etc/sysconfig ]; then + echo "Warning: /etc/sysconfig has been replaced by /etc/rc.conf." + echo "You should switch to /etc/rc.conf ASAP to eliminate this warning." +fi + # Configure ccd devices. if [ -f /etc/ccd.conf ]; then ccdconfig -C fi +# Configure vinum volumes. if [ -n "$vinum_slices" ]; then if [ -r /modules/vinum.ko ]; then # jkh paranoia kldload vinum @@ -88,17 +100,6 @@ if [ $? != 0 ]; then echo "Filesystem mount failed, startup aborted" exit 1 -fi - -# If there is a global system configuration file, suck it in. -if [ -f /etc/rc.conf ]; then - . /etc/rc.conf -fi - -# If old file exists, whine until they fix it. -if [ -f /etc/sysconfig ]; then - echo "Warning: /etc/sysconfig has been replaced by /etc/rc.conf." - echo "You should switch to /etc/rc.conf ASAP to eliminate this warning." fi adjkerntz -i To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 09:42:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA12897 for freebsd-current-outgoing; Fri, 22 Jan 1999 09:42:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12881 for ; Fri, 22 Jan 1999 09:42:07 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.2/8.9.1) id LAA23750; Fri, 22 Jan 1999 11:41:53 -0600 (CST) (envelope-from dick) Date: Fri, 22 Jan 1999 11:41:53 -0600 From: "Richard Seaman, Jr." To: "Kurt D. Zeilenga" Cc: freebsd-current@FreeBSD.ORG Subject: Re: -D_REENTRANT (Was: Using LinuxThreads) Message-ID: <19990122114153.H92540@tar.com> References: <19990119091151.F600@tar.com> <19990118182717.A15566@top.worldcontrol.com> <19990119024539.A88383@top.worldcontrol.com> <19990119140613.B826@shale.csir.co.za> <19990119091151.F600@tar.com> <19990121181228.A98581@shale.csir.co.za> <3.0.5.32.19990121114214.00958c30@localhost> <19990121143940.D5495@tar.com> <36A7A395.29B3E8A7@OpenLDAP.Org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <36A7A395.29B3E8A7@OpenLDAP.Org>; from Kurt D. Zeilenga on Thu, Jan 21, 1999 at 02:00:53PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 21, 1999 at 02:00:53PM -0800, Kurt D. Zeilenga wrote: > > For kernel threading you just use libc. Whether or not libc generates > > thread safe (re-entrant) calls depends on whether its also linked with > > a library that 1) sets __isthreaded to a non-zero value, 2) has a _spinlock() > > implementationm, and 3) implements the functions flockfile, funlockfile, etc. > > There are also a few macros in header files that require _THREAD_SAFE to > > be defined to be thread safe. > > > I was hoping to be able to produce one ldap library that could be safely > linked with or without threads. However, if I must define _THREAD_SAFE > to generate code to be linked with threads then I must produce two libraries > (-lfoolib compiled with -U_THREAD_SAFE and -lfoolib_r with -D_THREAD_SAFE). _THREAD_SAFE is only used in stdio.h. Looking at what's there, it could be rewritten to eliminate _THREAD_SAFE entirely, at a (very slight) performance penalty. You'd have to check __isthreaded (could be done once, instead of twice, as in the code now) each time you call one of the functions defined within the _THREAD_SAFE switch. All _THREAD_SAFE does is let you avoid checking __isthreaded when you're not threaded. -- Richard Seamman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 09:51:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14378 for freebsd-current-outgoing; Fri, 22 Jan 1999 09:51:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cantor.boolean.net (cantor.boolean.net [209.133.111.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA14373 for ; Fri, 22 Jan 1999 09:51:53 -0800 (PST) (envelope-from Kurt@OpenLDAP.Org) Received: from OpenLDAP.Org (localhost [127.0.0.1]) by cantor.boolean.net (8.9.1/8.9.1) with ESMTP id RAA21169; Fri, 22 Jan 1999 17:58:06 GMT (envelope-from Kurt@OpenLDAP.Org) Message-ID: <36A8BA23.8AE3B430@OpenLDAP.Org> Date: Fri, 22 Jan 1999 09:49:23 -0800 From: "Kurt D. Zeilenga" Organization: OpenLDAP X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en-GB,en-US,en,de-DE,de MIME-Version: 1.0 To: "Richard Seaman, Jr." CC: freebsd-current@FreeBSD.ORG Subject: Re: -D_REENTRANT (Was: Using LinuxThreads) References: <19990119091151.F600@tar.com> <19990118182717.A15566@top.worldcontrol.com> <19990119024539.A88383@top.worldcontrol.com> <19990119140613.B826@shale.csir.co.za> <19990119091151.F600@tar.com> <19990121181228.A98581@shale.csir.co.za> <3.0.5.32.19990121114214.00958c30@localhost> <19990121143940.D5495@tar.com> <36A7A395.29B3E8A7@OpenLDAP.Org> <19990122114153.H92540@tar.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Richard Seaman, Jr." wrote: > > On Thu, Jan 21, 1999 at 02:00:53PM -0800, Kurt D. Zeilenga wrote: > > > > For kernel threading you just use libc. Whether or not libc generates > > > thread safe (re-entrant) calls depends on whether its also linked with > > > a library that 1) sets __isthreaded to a non-zero value, 2) has a _spinlock() > > > implementationm, and 3) implements the functions flockfile, funlockfile, etc. > > > There are also a few macros in header files that require _THREAD_SAFE to > > > be defined to be thread safe. > > > > > > I was hoping to be able to produce one ldap library that could be safely > > linked with or without threads. However, if I must define _THREAD_SAFE > > to generate code to be linked with threads then I must produce two libraries > > (-lfoolib compiled with -U_THREAD_SAFE and -lfoolib_r with -D_THREAD_SAFE). > > _THREAD_SAFE is only used in stdio.h. Looking at what's there, it could > be rewritten to eliminate _THREAD_SAFE entirely, at a (very slight) > performance penalty. You'd have to check __isthreaded (could be done > once, instead of twice, as in the code now) each time you call one > of the functions defined within the _THREAD_SAFE switch. All > _THREAD_SAFE does is let you avoid checking __isthreaded when you're > not threaded. So, if I want to produce a library which can be safely used by both threaded and non-threaded applications I should NOT define -D_THREAD_SAFE such that __isthreaded is always checked by the library. In effect, -D_THREAD_SAFE makes the generated code non-thread UNSAFE. - Kurt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 09:53:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14653 for freebsd-current-outgoing; Fri, 22 Jan 1999 09:53:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA14647 for ; Fri, 22 Jan 1999 09:53:46 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id MAA67060; Fri, 22 Jan 1999 12:59:42 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Fri, 22 Jan 1999 12:59:42 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Mikhail Teterin cc: current@FreeBSD.ORG Subject: Re: zip drive and parallel port in NIBBLE mode hang the machine In-Reply-To: <199901221322.IAA00282@kot.ne.mediaone.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 22 Jan 1999, Mikhail Teterin wrote: > Hello! > > My system is too old to have anything other then "Compatable" and > "Bi-directional" modes for the parallel port. Both of this are recognized > as NIBBLE-only by ppc0. > > When I try to cp a big file (Wordperfect distribution) onto a Zip > cartridge (with ufs with softupdates) the whole system becomes "jerky" > and soon hangs -- I can still go from one virtual console to another, > but can not do anything and need cold reboot. > > I used to be able to use the drive during Autumn (although I only > used msdos-formatted cartridges). Any ideas? Thanks! > try searching the lists, my suggestion is to compile like so: controller ppc0 at isa? disable port ? tty irq 7 change to: controller ppc0 at isa? disable port ? cam irq 7 -----------------------------------------^^^ you may also want to try 'bio' it's been explained on the lists and i'm unsure. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 4.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 09:56:43 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA15118 for freebsd-current-outgoing; Fri, 22 Jan 1999 09:56:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from quackerjack.cc.vt.edu (quackerjack.cc.vt.edu [198.82.160.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA15112 for ; Fri, 22 Jan 1999 09:56:42 -0800 (PST) (envelope-from jobaldwi@vt.edu) Received: from sable.cc.vt.edu (sable.cc.vt.edu [128.173.16.30]) by quackerjack.cc.vt.edu (8.8.8/8.8.8) with ESMTP id MAA19354 for ; Fri, 22 Jan 1999 12:56:30 -0500 (EST) Received: from john.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.63]) by sable.cc.vt.edu (8.8.8/8.8.8) with ESMTP id MAA05307 for ; Fri, 22 Jan 1999 12:56:30 -0500 (EST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 22 Jan 1999 12:57:56 -0500 (EST) From: John Baldwin To: freebsd-current@FreeBSD.ORG Subject: Can't get 3.0 stable to build... :( Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- I hope this is the right list... I'm having some problems building 3.0 stable on a 3.0-19990105-SNAP machine. I've tried blowing away /usr/src and checking it back out again to no avail. Buildworld always dies with this error: install -c -o root -g wheel -m 444 bsd.README bsd.dep.mk bsd.doc.mk bsd.docb.mk bsd.info.mk bsd.kern.mk bsd.kmod.mk bsd.lib.mk bsd.libnames.mk bsd.man.mk bsd.obj.mk bsd.own.mk bsd.port.mk bsd.port.post.mk bsd.port.pre.mk bsd.port.subdir.mk bsd.prog.mk bsd.sgml.mk bsd.subdir.mk sys.mk /usr/obj/usr/source/src/tmp/mk usage: install [-CcDps] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 install [-CcDps] [-f flags] [-g group] [-m mode] [-o owner] file1 ... fileN directory install -d [-g group] [-m mode] [-o owner] directory ... *** Error code 64 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Note that my source tree is stored in /usr/source/src and that /usr/src is symlinked to /usr/source/src. I start the build by doing, cd /usr/src; make buildworld. The problem seems to be that /usr/obj/usr/source/src/tmp/mk does not exist, although /usr/source/src/tmp/make does. Does anyone have any suggestions, etc? - --- John Baldwin -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNqi8ILaE8XzBCodNAQHiUAP/QL1+SrFOFGbLnNuPxbwZrpnY83MVR0Sc lonWq1Mtv6SDe2y812fbZ7bHzAOoRqldMCNYHrllFae+6Vb/gj1v049ktTpFA1ow 2QloeArpjPMGHCP7NwlXmiwV5S2tP3og2MhJJb2wsaXTZsQ28XGXR0aEzK3LcmwI X0Q3Oke+vss= =3XMU -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 10:14:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17090 for freebsd-current-outgoing; Fri, 22 Jan 1999 10:14:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17067; Fri, 22 Jan 1999 10:14:50 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id TAA20228; Fri, 22 Jan 1999 19:20:05 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Fri, 22 Jan 1999 19:20:05 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Warner Losh cc: Matthew Dillon , current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Heads up! New swapper and VM changes being committed to -4.x tonight. In-Reply-To: <199901211853.LAA79083@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 21 Jan 1999, Warner Losh wrote: > In message Andrzej Bialecki writes: > : I'm more than willing to test it in low memory conditions.. :-) I have > : that special 386SX/4MB RAM machine in the corner to test things like > : picobsd memory requirements... > > So how well does this work? I have a 4MB machine that I'd like to run > FreeBSD on, including X on a low res screen... Hmmm.. Did I mention that I just left for a week to another country? Probably not :) I'll do the testing when I'm back. Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 10:20:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17914 for freebsd-current-outgoing; Fri, 22 Jan 1999 10:20:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17885 for ; Fri, 22 Jan 1999 10:20:02 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.2/8.9.1) id MAA70818; Fri, 22 Jan 1999 12:19:49 -0600 (CST) (envelope-from dick) Date: Fri, 22 Jan 1999 12:19:49 -0600 From: "Richard Seaman, Jr." To: "Kurt D. Zeilenga" Cc: freebsd-current@FreeBSD.ORG Subject: Re: -D_REENTRANT (Was: Using LinuxThreads) Message-ID: <19990122121949.I92540@tar.com> References: <19990119024539.A88383@top.worldcontrol.com> <19990119140613.B826@shale.csir.co.za> <19990119091151.F600@tar.com> <19990121181228.A98581@shale.csir.co.za> <3.0.5.32.19990121114214.00958c30@localhost> <19990121143940.D5495@tar.com> <36A7A395.29B3E8A7@OpenLDAP.Org> <19990122114153.H92540@tar.com> <36A8BA23.8AE3B430@OpenLDAP.Org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <36A8BA23.8AE3B430@OpenLDAP.Org>; from Kurt D. Zeilenga on Fri, Jan 22, 1999 at 09:49:23AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 22, 1999 at 09:49:23AM -0800, Kurt D. Zeilenga wrote: > "Richard Seaman, Jr." wrote: > > _THREAD_SAFE is only used in stdio.h. Looking at what's there, it could > > be rewritten to eliminate _THREAD_SAFE entirely, at a (very slight) > > performance penalty. You'd have to check __isthreaded (could be done > > once, instead of twice, as in the code now) each time you call one > > of the functions defined within the _THREAD_SAFE switch. All > > _THREAD_SAFE does is let you avoid checking __isthreaded when you're > > not threaded. > > So, if I want to produce a library which can be safely used by both > threaded and non-threaded applications I should NOT define -D_THREAD_SAFE > such that __isthreaded is always checked by the library. I guess I was a little unclear. 1) I think you would have to rewrite a little bit of the header to use the __isthreaded test on a couple of more functions. 2) If you always define -D_THREAD_SAFE, __isthreaded will be checked whether you're threaded or not. If you're not threaded, __isthreaded should be false and you avoid the file locking code. If you're threaded, __isthreaded should be true and you get the file locking (if you're linked with a library that has actualy file locking code to override the libc file locking stub functions -- libc_r does this for you, you need something like a pthreads library linked in for libc). You could also just eliminate _THREAD_SAFE entirely by letting __isthreaded get checked on each relevant call. 3) If you're linking with FreeBSD user threads, you still have the problem that user threads needs libc_r and not libc, while everything else (no threads, or kernel threads) needs libc. The _THREAD_SAFE switch doesn't affect whether you link with libc or libc_r. As mentioned before, libc_r could be rewritten to look like a "normal" libpthread addon library, ie. it wouldn't duplicate libc, but it would require some work. 4) There are portions of libc that are only thread safe when they are compiled as part of libc_r (almost all of libc gets rolled into libc_r). This can be fixed. Indeed, I have patches that do this, but they need some testing. -- Richard Seamman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 10:30:53 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18826 for freebsd-current-outgoing; Fri, 22 Jan 1999 10:30:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18821 for ; Fri, 22 Jan 1999 10:30:51 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id KAA26668; Fri, 22 Jan 1999 10:30:37 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id KAA10166; Fri, 22 Jan 1999 10:30:37 -0800 (PST) (envelope-from jdp@polstra.com) Date: Fri, 22 Jan 1999 10:30:37 -0800 (PST) Message-Id: <199901221830.KAA10166@vashon.polstra.com> To: mystify@friley-184-92.res.iastate.edu Subject: Re: Changes to pam_kerberosIV broke ftpd Newsgroups: polstra.freebsd.current In-Reply-To: <199901211425.IAA33202@friley-184-92.res.iastate.edu> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199901211425.IAA33202@friley-184-92.res.iastate.edu>, Patrick Hartling wrote: > It appears that revision 1.9 of lib/libpam/modules/pam_kerberosIV/klogin.c > and revision 1.3 of lib/libpam/modules/pam_kerberosIV/pam_kerberosIV.c > broke ftpd when compiling with MAKE_KERBEROS defined. Right. It's fixed now (yesterday, actually). John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 10:47:01 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA21121 for freebsd-current-outgoing; Fri, 22 Jan 1999 10:47:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cantor.boolean.net (cantor.boolean.net [209.133.111.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA21115 for ; Fri, 22 Jan 1999 10:46:59 -0800 (PST) (envelope-from Kurt@OpenLDAP.Org) Received: from OpenLDAP.Org (localhost [127.0.0.1]) by cantor.boolean.net (8.9.1/8.9.1) with ESMTP id SAA21910; Fri, 22 Jan 1999 18:52:47 GMT (envelope-from Kurt@OpenLDAP.Org) Message-ID: <36A8C6F3.5D611CA9@OpenLDAP.Org> Date: Fri, 22 Jan 1999 10:44:03 -0800 From: "Kurt D. Zeilenga" Organization: OpenLDAP X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en-GB,en-US,en,de-DE,de MIME-Version: 1.0 To: "Richard Seaman, Jr." CC: freebsd-current@FreeBSD.ORG Subject: Re: -D_REENTRANT (Was: Using LinuxThreads) References: <19990119024539.A88383@top.worldcontrol.com> <19990119140613.B826@shale.csir.co.za> <19990119091151.F600@tar.com> <19990121181228.A98581@shale.csir.co.za> <3.0.5.32.19990121114214.00958c30@localhost> <19990121143940.D5495@tar.com> <36A7A395.29B3E8A7@OpenLDAP.Org> <19990122114153.H92540@tar.com> <36A8BA23.8AE3B430@OpenLDAP.Org> <19990122121949.I92540@tar.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Richard Seaman, Jr." wrote: > > On Fri, Jan 22, 1999 at 09:49:23AM -0800, Kurt D. Zeilenga wrote: > > "Richard Seaman, Jr." wrote: > > > _THREAD_SAFE is only used in stdio.h. Looking at what's there, it could > > > be rewritten to eliminate _THREAD_SAFE entirely, at a (very slight) > > > performance penalty. You'd have to check __isthreaded (could be done > > > once, instead of twice, as in the code now) each time you call one > > > of the functions defined within the _THREAD_SAFE switch. All > > > _THREAD_SAFE does is let you avoid checking __isthreaded when you're > > > not threaded. > > > > So, if I want to produce a library which can be safely used by both > > threaded and non-threaded applications I should NOT define -D_THREAD_SAFE > > such that __isthreaded is always checked by the library. > > I guess I was a little unclear. > > 1) I think you would have to rewrite a little bit of the header to > use the __isthreaded test on a couple of more functions. > > 2) If you always define -D_THREAD_SAFE, __isthreaded will be > checked whether you're threaded or not. I would think that most third party libraries (from Ports) do not compile with -D_THREAD_SAFE. As such, __isthreaded won't be checked and the library cannot be safely used in a threaded environment. > You could also just eliminate _THREAD_SAFE entirely by letting > __isthreaded get checked on each relevant call. I would much prefer this. Then third party libraries compiled without -D_THREAD_SAFE can be used in threaded environments (though they might require external synchronization). Kurt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 10:58:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA23382 for freebsd-current-outgoing; Fri, 22 Jan 1999 10:58:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA23323 for ; Fri, 22 Jan 1999 10:58:02 -0800 (PST) (envelope-from jfieber@fallout.campusview.indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.9.1/8.9.1) with ESMTP id NAA79234; Fri, 22 Jan 1999 13:57:43 -0500 (EST) Date: Fri, 22 Jan 1999 13:57:43 -0500 (EST) From: John Fieber To: Palle Girgensohn cc: freebsd-current@FreeBSD.ORG Subject: Re: netd in free(): warning: junk pointer, too low to make sense. In-Reply-To: <36A89532.97D035B5@partitur.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 22 Jan 1999, Palle Girgensohn wrote: > I'm experiencing some strange errors with one of our workstations. I > recently moved all of our workstations to 3.0 current as of 1998-12-18. > Does any of this make any sense to anyone: > > trumpet:~>rlogin balalaika > netd in free(): warning: junk pointer, too low to make sense. > trumpet:~>telnet balalaika > Trying 1.2.3.4... > Connected to balalaika.partitur.se. > Escape character is '^]'. > inetd in free(): warning: junk pointer, too low to make sense. There are two separate bugs that can cause this behavior, one in inetd and the other is the infamous "dying daemons" bug. Both have theoretically been fixed, recently. Sorry I don't have exact dates handy. -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 11:02:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA24293 for freebsd-current-outgoing; Fri, 22 Jan 1999 11:02:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA24288 for ; Fri, 22 Jan 1999 11:02:12 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id LAA26816; Fri, 22 Jan 1999 11:02:02 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id LAA10234; Fri, 22 Jan 1999 11:02:01 -0800 (PST) (envelope-from jdp@polstra.com) Date: Fri, 22 Jan 1999 11:02:01 -0800 (PST) Message-Id: <199901221902.LAA10234@vashon.polstra.com> To: sobomax@altavista.net Subject: Re: World broken in RELENG_3 when making aout-to-elf bulid Newsgroups: polstra.freebsd.current In-Reply-To: <36A867ED.8ADAC14C@altavista.net> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <36A867ED.8ADAC14C@altavista.net>, Maxim Sobolev wrote: > > -o login login.o login_access.o login_fbtab.o  -lutil -lcrypt > login.o: Undefined symbol `_pam_start' referenced from text segment ... I merged the fix into RELENG_3 this morning. Sorry about that! John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 11:07:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25300 for freebsd-current-outgoing; Fri, 22 Jan 1999 11:07:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from roma.coe.ufrj.br (roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25291 for ; Fri, 22 Jan 1999 11:07:21 -0800 (PST) (envelope-from jonny@jonny.eng.br) Received: (from jonny@localhost) by roma.coe.ufrj.br (8.8.8/8.8.8) id RAA19846; Fri, 22 Jan 1999 17:06:35 -0200 (EDT) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199901221906.RAA19846@roma.coe.ufrj.br> Subject: Re: boot.flp versions In-Reply-To: <90520.916884844@zippy.cdrom.com> from "Jordan K. Hubbard" at "Jan 20, 1999 6:14: 4 pm" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Fri, 22 Jan 1999 17:06:35 -0200 (EDT) Cc: dhw@whistle.com, freebsd-current@FreeBSD.ORG, rdawes@ucsd.edu X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG #define quoting(Jordan K. Hubbard) // All: Sorry the boot.flp has been broken for this long, but I've had // other distractions lately. I will make it work once more, somehow // or other, and just keep your eyes on current.freebsd.org over // the next few days. When it returns to 1.44MB in size again, give // it a try. :) Another problem I had with that snap here is that it does not install on a machine with 8M RAM. It started installing, but stopped in random places during file copy. It did work after I remade the kern.flp with only the devices I had (thus, using less memory). I noticed that swapping was disabled in the BOOTMFS kernel. Is this really necessary ? How hard is to add an option "use this swap partition during install", or even a "create and use a vn swap file in /usr/tmp during install" ? Or should I just assume 8M RAM machines are not any more supported ? Jonny PS: Wow !!! The new loader made dealing with boot.flp a very easy task. :) -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro "This .sig is not meant to be politically correct." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 11:11:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA26126 for freebsd-current-outgoing; Fri, 22 Jan 1999 11:11:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA26121 for ; Fri, 22 Jan 1999 11:11:24 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id LAA40757; Fri, 22 Jan 1999 11:10:29 -0800 (PST) To: Joao Carlos Mendes Luis cc: dhw@whistle.com, freebsd-current@FreeBSD.ORG, rdawes@ucsd.edu Subject: Re: boot.flp versions In-reply-to: Your message of "Fri, 22 Jan 1999 17:06:35 -0200." <199901221906.RAA19846@roma.coe.ufrj.br> Date: Fri, 22 Jan 1999 11:10:29 -0800 Message-ID: <40753.917032229@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, in retrospect, turning off swapping was a mistake. I should have thought about this a bit more before blindly accepting the suggestion from Andrzej. ;) Fixed. - Jordan > #define quoting(Jordan K. Hubbard) > // All: Sorry the boot.flp has been broken for this long, but I've had > // other distractions lately. I will make it work once more, somehow > // or other, and just keep your eyes on current.freebsd.org over > // the next few days. When it returns to 1.44MB in size again, give > // it a try. :) > > Another problem I had with that snap here is that it does not install > on a machine with 8M RAM. It started installing, but stopped in > random places during file copy. It did work after I remade the > kern.flp with only the devices I had (thus, using less memory). > > I noticed that swapping was disabled in the BOOTMFS kernel. Is this > really necessary ? How hard is to add an option "use this swap > partition during install", or even a "create and use a vn swap file in > /usr/tmp during install" ? > > Or should I just assume 8M RAM machines are not any more supported ? > > Jonny > > PS: Wow !!! The new loader made dealing with boot.flp a very easy > task. :) > > -- > Joao Carlos Mendes Luis M.Sc. Student > jonny@jonny.eng.br Universidade Federal do Rio de Janeiro > "This .sig is not meant to be politically correct." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 11:23:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27400 for freebsd-current-outgoing; Fri, 22 Jan 1999 11:23:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vip.consys.com (Comobabi.ConSys.COM [209.141.107.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27393 for ; Fri, 22 Jan 1999 11:23:01 -0800 (PST) (envelope-from rcarter@pinyon.org) Received: (from pinyon@localhost) by vip.consys.com (8.9.1/8.9.1) id MAA02272 for freebsd-current@freebsd.org; Fri, 22 Jan 1999 12:18:18 -0700 (MST) Date: Fri, 22 Jan 1999 12:18:18 -0700 (MST) From: "Russell L. Carter" Message-Id: <199901221918.MAA02272@vip.consys.com> To: freebsd-current@FreeBSD.ORG Subject: Re: Using LinuxThreads In-Reply-To: <19990122090134.F5495@tar.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG |Maybe having just one pthread.h that pulls in the required headers |based on a switch (eg. -DLINUXTHREADS) is the way to go? Doing this makes linuxthread support more or less "official", I would think. I am for it. Russell | |-- |Richard Seamman, Jr. email: dick@tar.com |5182 N. Maple Lane phone: 414-367-5450 |Chenequa WI 53058 fax: 414-367-5852 | |To Unsubscribe: send mail to majordomo@FreeBSD.org |with "unsubscribe freebsd-current" in the body of the message | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 11:30:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27707 for freebsd-current-outgoing; Fri, 22 Jan 1999 11:25:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from octopus.originative.co.uk (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27678 for ; Fri, 22 Jan 1999 11:25:02 -0800 (PST) (envelope-from paul@originative.co.uk) From: paul@originative.co.uk Received: by OCTOPUS with Internet Mail Service (5.5.1960.3) id ; Fri, 22 Jan 1999 19:23:25 -0000 Message-ID: To: axl@iafrica.com, sobomax@altavista.net Cc: current@FreeBSD.ORG Subject: RE: WARNING: Today's current breaks passwords Date: Fri, 22 Jan 1999 19:23:24 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Sheldon Hearn [mailto:axl@iafrica.com] > Sent: Friday, January 22, 1999 3:17 PM > To: Maxim Sobolev > Cc: current@FreeBSD.ORG > Subject: Re: WARNING: Today's current breaks passwords > > > > > On Fri, 22 Jan 1999 16:51:40 +0200, Maxim Sobolev wrote: > > > Maybe your have switched between hashing modes (DES->MD5 or > MD5->DES)? > > Possibly that's what's happened, but it certainly isn't > something I did > deliberately. It happened to me too. Did a cvsupdate after the tag and Matt's code was commited, did a make world, built a new kernel, rebooted and couldn't log in! After changing root's password it went from being DES to SHA1 so I suspect it's failing to honour the existing hash algorithm and trying to use SHA1 regardless. Brandon looks like he's been around here recently, like yesterday when it happened :-). Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 11:36:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29382 for freebsd-current-outgoing; Fri, 22 Jan 1999 11:36:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA29377 for ; Fri, 22 Jan 1999 11:36:57 -0800 (PST) (envelope-from fenner@parc.xerox.com) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <55546(2)>; Fri, 22 Jan 1999 11:36:37 PST Received: from localhost by crevenia.parc.xerox.com with SMTP id <177534>; Fri, 22 Jan 1999 11:36:24 -0800 To: Konstantin Chuguev cc: freebsd-current@FreeBSD.ORG Subject: Re: T/TCP in FreeBSD-3.x In-reply-to: Your message of "Fri, 22 Jan 99 03:20:17 PST." <36A85EF1.444A86B@urc.ac.ru> Date: Fri, 22 Jan 1999 11:36:20 PST From: Bill Fenner Message-Id: <99Jan22.113624pst.177534@crevenia.parc.xerox.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <36A85EF1.444A86B@urc.ac.ru> you write: >Why I'm asking about this, is because I recently read an advice in one >of the FreeBSD mailing lists, >about "Why my dial-up PPP connection from a FreeBSD box is so slow >comparing with Windows NT >(about ten times slower)?" > >And the advice was (without explanations): "Try to switch off the >TCP_EXTENSIONS in /etc/rc.conf". Some dialup terminal servers have problems with TCP options; turning off TCP_EXTENSIONS is the easiest way to handle these terminal servers. >So, is it safe to use T/TCP (at least for Squid) for RELENG_3? >RELENG_2_2? I asked for more info about the problems they were having with T/TCP and never got much of an answer; since they don't say what the problem they were having was it's hard to say whether or not it was resolved. >And what about MBUF size (mentioned at the same page of the Squid FAQ)? >Do I need to patch Squid as it shown at the page? Recent (as in the last day or so) RELENG_3's should not need this patch; the bug described has been fixed in another way. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 11:42:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA00180 for freebsd-current-outgoing; Fri, 22 Jan 1999 11:42:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA00124 for ; Fri, 22 Jan 1999 11:42:00 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id OAA39629; Fri, 22 Jan 1999 14:47:53 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Fri, 22 Jan 1999 14:47:53 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: "Russell L. Carter" cc: freebsd-current@FreeBSD.ORG, dick@tar.com Subject: Re: Using LinuxThreads In-Reply-To: <199901221918.MAA02272@vip.consys.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 22 Jan 1999, Russell L. Carter wrote: > |Maybe having just one pthread.h that pulls in the required headers > |based on a switch (eg. -DLINUXTHREADS) is the way to go? > > Doing this makes linuxthread support more or less "official", I would > think. > > I am for it. *confused look* somehow even though i've been trying to follow this thread i got lost. questions: 1) are 'linuxthreads' enabled by defualt now? 2) if not then 'make world -DLINUXTHREADS' ? 3) when it's decided can someone explain how to use this stuff nativly? thanks, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 11:54:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA01883 for freebsd-current-outgoing; Fri, 22 Jan 1999 11:54:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from octopus.originative.co.uk (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA01877 for ; Fri, 22 Jan 1999 11:54:26 -0800 (PST) (envelope-from paul@originative.co.uk) From: paul@originative.co.uk Received: by OCTOPUS with Internet Mail Service (5.5.1960.3) id ; Fri, 22 Jan 1999 19:52:45 -0000 Message-ID: To: jfieber@indiana.edu, yokota@zodiac.mech.utsunomiya-u.ac.jp Cc: current@FreeBSD.ORG Subject: RE: keymaps Date: Fri, 22 Jan 1999 19:52:44 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: John Fieber [mailto:jfieber@indiana.edu] > Sent: Friday, January 22, 1999 3:51 PM > To: Kazutaka YOKOTA > Cc: current@FreeBSD.ORG > Subject: Re: keymaps > > > On Fri, 22 Jan 1999, Kazutaka YOKOTA wrote: > > > Gentlemen, I don't intend to add yet another keymap to > > /usr/share/syscons/keymaps. I am merely trying to define a > reasonable > > set of common, consistent key binding for existing keymaps. > > > > National keyboards have different layout of regular keys. But > > function keys and special keys are placed identically. They should > > work in the same way, or at least similar way in all > keyboards, unless > > there is a good reason to do otherwise. (I am not talking about > > non-AT keyboards which are totally different from either AT 84 or > > 101/102/104 keyboards.) > > What would be useful here is the ability to "compose" keymaps. > There would be basically two sets: one that defines the layout of > the main keyboard and one that defines the layout of the other > keys. That way I could pick my dvorak layout, then add on a > layout that, say, swaps control and caps lock but leaves the main > layout alone. I was thinking something similar, a way to dynamically modify the map ala xmodmap would be useful so that users who have particular preferences can implement the changes in, say, .login That's exactly what I do with xmodmap and X. The standard maps can continue to reflect the actual layout of the keyboards then rather than having a number of variations according to popular user preference. Paul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 11:55:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA02031 for freebsd-current-outgoing; Fri, 22 Jan 1999 11:55:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA02024 for ; Fri, 22 Jan 1999 11:55:47 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.2/8.9.1) id NAA27494; Fri, 22 Jan 1999 13:55:21 -0600 (CST) (envelope-from dick) Date: Fri, 22 Jan 1999 13:55:21 -0600 From: "Richard Seaman, Jr." To: Alfred Perlstein Cc: freebsd-current@FreeBSD.ORG Subject: Re: Using LinuxThreads Message-ID: <19990122135521.J92540@tar.com> References: <199901221918.MAA02272@vip.consys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Alfred Perlstein on Fri, Jan 22, 1999 at 02:47:53PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 22, 1999 at 02:47:53PM -0500, Alfred Perlstein wrote: > *confused look* > > somehow even though i've been trying to follow this thread i got lost. > > questions: > 1) are 'linuxthreads' enabled by defualt now? The terminology is a little confusing. There's "linuxthreads" for those running linux apps in FreeBSD using the linux emulation modules. Then, there's a port of linuxthreads to FreeBSD which runs natively, ie. no linux emulation, and gives 1-1 kernel threading to apps that link to it. Both require some options to be turned on for kernel/world builds that are not on by default. (see http://lt.tar.com) Julian Elischer has agreed to commit the patches to remove the options and make the code change permanent, when I send him the patches. I'll send him the patches as soon as I can test them after a "make world", which I'll do as soon as the libcrypt build problems are fixed. > 2) if not then 'make world -DLINUXTHREADS' ? See above. > 3) when it's decided can someone explain how to use this stuff nativly? See http://lt.tar.com . I also have some patches for squid, glib and I'm working on gimp to compile using the FreeBSD port of linuxthreads. Others have had success in varying degress with NSPR (mozilla), ACE and others. -- Richard Seamman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 12:17:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA04598 for freebsd-current-outgoing; Fri, 22 Jan 1999 12:17:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA04593 for ; Fri, 22 Jan 1999 12:17:07 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id PAA20747; Fri, 22 Jan 1999 15:16:56 -0500 (EST) (envelope-from luoqi) Date: Fri, 22 Jan 1999 15:16:56 -0500 (EST) From: Luoqi Chen Message-Id: <199901222016.PAA20747@lor.watermarkgroup.com> To: current@FreeBSD.ORG, julian@whistle.com Subject: Re: world broken Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > having spent almost an hour trying to decode the complexities of the crypt > making process I admit defeat.. > can SOMEBODY please fix the build in -current and sent branson > a nice pointy hat.. > I think he committed and went on vacation > > (I haven't seen any commits that say they fixed this but I'm waiting > for cvsup to connect just in case I missed it...) > > julian > I spend half night yesterday to sort this mess out. If no one objects, I'll commit my fixes. (anyone volunteers to make the hat?) -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 12:28:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA06509 for freebsd-current-outgoing; Fri, 22 Jan 1999 12:28:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA06500 for ; Fri, 22 Jan 1999 12:28:12 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id PAA11494; Fri, 22 Jan 1999 15:34:06 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Fri, 22 Jan 1999 15:34:06 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: "Richard Seaman, Jr." cc: freebsd-current@FreeBSD.ORG Subject: Re: Using LinuxThreads In-Reply-To: <19990122135521.J92540@tar.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 22 Jan 1999, Richard Seaman, Jr. wrote: > > *confused look* > > > > somehow even though i've been trying to follow this thread i got lost. > > > > questions: > > 1) are 'linuxthreads' enabled by defualt now? > > The terminology is a little confusing. There's "linuxthreads" for those > running linux apps in FreeBSD using the linux emulation modules. Then, > there's a port of linuxthreads to FreeBSD which runs natively, ie. no > linux emulation, and gives 1-1 kernel threading to apps that link to > it. > > Both require some options to be turned on for kernel/world builds that > are not on by default. (see http://lt.tar.com) Julian Elischer has > agreed to commit the patches to remove the options and make the code > change permanent, when I send him the patches. I'll send him the patches > as soon as I can test them after a "make world", which I'll do as soon > as the libcrypt build problems are fixed. awesome, btw, it seems that make world is also broken on libkvm. > > 3) when it's decided can someone explain how to use this stuff nativly? > > See http://lt.tar.com . I also have some patches for squid, glib and I'm > working on gimp to compile using the FreeBSD port of linuxthreads. Others > have had success in varying degress with NSPR (mozilla), ACE and others. will do. > > -- > Richard Seamman, Jr. email: dick@tar.com > 5182 N. Maple Lane phone: 414-367-5450 > Chenequa WI 53058 fax: 414-367-5852 > Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 4.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 12:34:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07362 for freebsd-current-outgoing; Fri, 22 Jan 1999 12:34:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07352 for ; Fri, 22 Jan 1999 12:34:48 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.1) with ESMTP id WAA09118; Fri, 22 Jan 1999 22:34:23 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.2/8.9.2) with ESMTP id WAA97434; Fri, 22 Jan 1999 22:34:20 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199901222034.WAA97434@greenpeace.grondar.za> To: Luoqi Chen cc: current@FreeBSD.ORG, brandon@whistle.com Subject: Re: world broken In-Reply-To: Your message of " Fri, 22 Jan 1999 15:16:56 EST." <199901222016.PAA20747@lor.watermarkgroup.com> References: <199901222016.PAA20747@lor.watermarkgroup.com> Date: Fri, 22 Jan 1999 22:34:18 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luoqi Chen wrote: > I spend half night yesterday to sort this mess out. If no one objects, > I'll commit my fixes. (anyone volunteers to make the hat?) I know who gets the hat; please cool it on the fixes until the original committer has finished. I'm watching this one closely, and I need to track it on Internat as well. Not long now. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 12:36:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07784 for freebsd-current-outgoing; Fri, 22 Jan 1999 12:36:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from post.mail.demon.net (post-20.mail.demon.net [194.217.242.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07779 for ; Fri, 22 Jan 1999 12:36:30 -0800 (PST) (envelope-from root@scratch.demon.co.uk) Received: from [212.228.22.156] (helo=scratch.demon.co.uk) by post.mail.demon.net with smtp (Exim 2.10 #2) id 103nJM-0005N8-00; Fri, 22 Jan 1999 20:36:13 +0000 Message-ID: Date: Fri, 22 Jan 1999 20:34:52 +0000 To: Ying-Chieh Liao Cc: freebsd-current@FreeBSD.ORG From: Tim Subject: Re: PNP and new bootloader with ELF kernel References: <19990122122226.A2328@terry.dragon2.net> In-Reply-To: <19990122122226.A2328@terry.dragon2.net> MIME-Version: 1.0 X-Mailer: Turnpike (32) Version 4.00 <2bL8TQCIEWg0B+1EtXWvseZtDP> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990122122226.A2328@terry.dragon2.net>, Ying-Chieh Liao writes >On Thu, Jan 21, 1999 at 23:03:45 +0000, Tim wrote: >> How do I set up the CSN now as I get CSN 1 disabled and CSN 2 disabled >> on boot. > >you can put this pnp information in /kernel.config >and, in your /boot/boot.conf, put > >load /kernel >load -t userconfig_script /kernel.config >boot > >this works fine on my box > >> Also I would like to remove the previous boot screen and boot straight >> into the new bootloader, so can a dos partition be configured to boot >> from the new bootloader > >just execute the following command : > >disklabel -B -b /boot/boot1 -s /boot/boot2 > > is which you boot from >ex : > >disklabel -B -b /boot/boot1 -s /boot/boot2 wd0s1 > Thanks for the info but unfortunately this has not worked, maybe this is the syntax I have used in the /kernel.config file pnp 1 enable os irq0 11 port0 0x3e8 used to work before else what permissions do the files need to be also, where did you find this load -t stuff Thanks -- Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 13:27:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA15923 for freebsd-current-outgoing; Fri, 22 Jan 1999 13:27:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bryggen.bgnett.no (bryggen.bgnett.no [194.54.96.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA15917 for ; Fri, 22 Jan 1999 13:27:43 -0800 (PST) (envelope-from erik@habatech.no) Received: from HABAWKS (4pogc-gw.online.no [194.248.199.142]) by bryggen.bgnett.no (8.8.8/8.8.5/brage2.1) with SMTP id VAA23807; Fri, 22 Jan 1999 21:26:13 GMT Message-ID: <00c601be464d$bb537eb0$8101a8c0@HABAWKS> From: "Erik H. Bakke" To: "Joerg B. Micheel" , "Dag-Erling Smorgrav" , "Mike Nguyen" Cc: Subject: Re: /etc/nsswitch.conf Date: Fri, 22 Jan 1999 22:22:14 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.0707.2700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0707.2700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Wed, Jan 20, 1999 at 05:58:01PM +0100, Dag-Erling Smorgrav wrote: >> Mike Nguyen writes: >> consolidating all that config information in one place, such as >> /etc/rc.conf, would be a good thing. > >Agreed, it really isn't such a good idea to clutter /etc/ with all >those single line configuration files. > How about having one file in /etc containing all the different configuration options, and have this file processed by a program to generate all the different configuration files. This would give us the benefits of a centralized configuration file, without the need of rewriting the many programs that really want to have their configuration in specific files. On the other hand, this would require a reprocessing of the file for each modification to the configuration. Maybe we could run the command at the beginning of /etc/rc, and allow a user with root privileges to rerun the command at any time to rescan the configuration? It would require a minimum of effort to implement this, so I hope this is not too simple for us. Regards --- Erik H. Bakke Habatech AS erik@habatech.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 14:01:02 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20412 for freebsd-current-outgoing; Fri, 22 Jan 1999 14:01:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA20273 for ; Fri, 22 Jan 1999 14:00:55 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id IAA27742; Sat, 23 Jan 1999 08:17:54 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.2/8.9.0) id IAA19627; Sat, 23 Jan 1999 08:17:08 +1030 (CST) Date: Sat, 23 Jan 1999 08:17:08 +1030 From: Greg Lehey To: Jake Cc: current@FreeBSD.ORG Subject: vinum read no longer works Message-ID: <19990123081708.I5697@freebie.lemis.com> References: <199901221723.JAA01151@h24-64-221-247.gv.wave.shaw.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199901221723.JAA01151@h24-64-221-247.gv.wave.shaw.ca>; from Jake on Fri, Jan 22, 1999 at 09:23:48AM -0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 22 January 1999 at 9:23:48 -0800, Jake wrote: > I can no longer bring up my vinum volume with the vinum read > command: > > vinum read /dev/wd0s1e /dev/wd2s1f > vinum read /dev/wd0s1e > vinum read /dev/wd2s1f > > all come back with > vinum: no drives Correct. As I explained in detail in my HEADS UP message a couple of days ago, you must now specify drives, not partitions. The correct command might be vinum read /dev/wd0 /dev/wd2 To quote the message: >> One way you can shoot yourself in the foot: the `read' command has >> changed. In the previous version, you specified the name of exactly >> one device containing a vinum partition. This is suboptimal, because >> it doesn't allow you to read multiple configurations, and it doesn't >> allow you to move drives around. In the new version, you *must* >> specify the names of *all* disks containing Vinum partitions. For >> example, if you have Vinum partitions /dev/da1h /dev/da2h /dev/da3h >> /dev/da4h /dev/da5h and /dev/da6h, you might previously have written: >> >> vinum read /dev/da3h >> >> Now you *must* write: >> >> vinum read /dev/da1 /dev/da2 /dev/da3 /dev/da4 /dev/da5 /dev/da6 >> >> If you do this wrong, you have the potential to wipe out your on-disk >> configuration. You can avoid this by disabling saving the >> configuration. Do this with the `setdaemon' command: >> >> # vinum >> vinum -> setdaemon 4 >> vinum -> read /dev/da1 /dev/da2 /dev/da3 /dev/da4 /dev/da5 /dev/da6 > I understand that all slices belonging to a volume must now be > passed to read, but that doesn't make any difference. Yes it does. As a result of the incorrect read command, you have probably obliterated your configuration. > I've modified /etc/rc to do a vinum create /etc/vinum.conf instead > and that works, but I thought read was the correct commmand. `read' is the correct command. The arguments you supplied are wrong. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 14:02:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20644 for freebsd-current-outgoing; Fri, 22 Jan 1999 14:02:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA20625 for ; Fri, 22 Jan 1999 14:02:24 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA20085 (5.67b/IDA-1.5); Fri, 22 Jan 1999 22:44:08 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id VAA14861; Fri, 22 Jan 1999 21:52:07 +0100 (CET) From: Wilko Bulte Message-Id: <199901222052.VAA14861@yedi.iaf.nl> Subject: Re: boot.flp versions In-Reply-To: <199901221906.RAA19846@roma.coe.ufrj.br> from Joao Carlos Mendes Luis at "Jan 22, 99 05:06:35 pm" To: jonny@jonny.eng.br (Joao Carlos Mendes Luis) Date: Fri, 22 Jan 1999 21:52:07 +0100 (CET) Cc: jkh@zippy.cdrom.com, dhw@whistle.com, freebsd-current@FreeBSD.ORG, rdawes@ucsd.edu X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Joao Carlos Mendes Luis wrote... > #define quoting(Jordan K. Hubbard) > // All: Sorry the boot.flp has been broken for this long, but I've had > // other distractions lately. I will make it work once more, somehow > // or other, and just keep your eyes on current.freebsd.org over > // the next few days. When it returns to 1.44MB in size again, give > // it a try. :) > > Another problem I had with that snap here is that it does not install > on a machine with 8M RAM. It started installing, but stopped in > random places during file copy. It did work after I remade the > kern.flp with only the devices I had (thus, using less memory). > > I noticed that swapping was disabled in the BOOTMFS kernel. Is this > really necessary ? How hard is to add an option "use this swap > partition during install", or even a "create and use a vn swap file in > /usr/tmp during install" ? > > Or should I just assume 8M RAM machines are not any more supported ? What grew so drastically that the memory requirements grew from 5 Mbytes minimum memory to > 8Mb? (remember all those discussions when 4Mb became too small to run the install floppy?) Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 14:24:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23829 for freebsd-current-outgoing; Fri, 22 Jan 1999 14:24:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23822 for ; Fri, 22 Jan 1999 14:24:50 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.2/8.9.2/Netplex) with ESMTP id GAA36415; Sat, 23 Jan 1999 06:24:17 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199901222224.GAA36415@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Greg Lehey cc: Jake , current@FreeBSD.ORG Subject: Re: vinum read no longer works In-reply-to: Your message of "Sat, 23 Jan 1999 08:17:08 +1030." <19990123081708.I5697@freebie.lemis.com> Date: Sat, 23 Jan 1999 06:24:17 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > On Friday, 22 January 1999 at 9:23:48 -0800, Jake wrote: > > I can no longer bring up my vinum volume with the vinum read > > command: > > > > vinum read /dev/wd0s1e /dev/wd2s1f > > vinum read /dev/wd0s1e > > vinum read /dev/wd2s1f > > > > all come back with > > vinum: no drives > > Correct. As I explained in detail in my HEADS UP message a couple of > days ago, you must now specify drives, not partitions. The correct > command might be > > vinum read /dev/wd0 /dev/wd2 Does vinum scan the slices? What if there are two freebsd slices? From vinumhdr.h, it looks like it totally ignores slices. If somebody is working on a disk shared with something else (eg: DOS/windoze), then perhaps the examples should be: vinum read /dev/wd0s1 /dev/wd2s1 Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 14:36:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24759 for freebsd-current-outgoing; Fri, 22 Jan 1999 14:36:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24748 for ; Fri, 22 Jan 1999 14:36:15 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id JAA28141; Sat, 23 Jan 1999 09:06:01 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.2/8.9.0) id JAA20086; Sat, 23 Jan 1999 09:06:01 +1030 (CST) Date: Sat, 23 Jan 1999 09:06:01 +1030 From: Greg Lehey To: Peter Wemm Cc: Jake , current@FreeBSD.ORG Subject: Re: vinum read no longer works Message-ID: <19990123090601.E19921@freebie.lemis.com> References: <19990123081708.I5697@freebie.lemis.com> <199901222224.GAA36415@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199901222224.GAA36415@spinner.netplex.com.au>; from Peter Wemm on Sat, Jan 23, 1999 at 06:24:17AM +0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, 23 January 1999 at 6:24:17 +0800, Peter Wemm wrote: > Greg Lehey wrote: >> On Friday, 22 January 1999 at 9:23:48 -0800, Jake wrote: >>> I can no longer bring up my vinum volume with the vinum read >>> command: >>> >>> vinum read /dev/wd0s1e /dev/wd2s1f >>> vinum read /dev/wd0s1e >>> vinum read /dev/wd2s1f >>> >>> all come back with >>> vinum: no drives >> >> Correct. As I explained in detail in my HEADS UP message a couple of >> days ago, you must now specify drives, not partitions. The correct >> command might be >> >> vinum read /dev/wd0 /dev/wd2 > > Does vinum scan the slices? What if there are two freebsd slices? Currently it just scans the compatibility slice. I'll change that later. > From vinumhdr.h, it looks like it totally ignores slices. Well, that's not the place I'd look. > If somebody is working on a disk shared with something else (eg: > DOS/windoze), then perhaps the examples should be: vinum read > /dev/wd0s1 /dev/wd2s1 Interesting. Yes, I think this would work. The real problem here is that, as you know from private correspondence, I haven't found a good way to determine what partitions are on the system, so I go through with brute force and try to open each possible partition. This will change when I find a better way, but it shouldn't require incompatible changes to the command line syntax again. With any luck, I *will* be able to say `vinum start', and it will go out and find the partitions by itself. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 14:54:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA27020 for freebsd-current-outgoing; Fri, 22 Jan 1999 14:54:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from burka.rdy.com (burka.rdy.com [205.149.163.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27014 for ; Fri, 22 Jan 1999 14:54:18 -0800 (PST) (envelope-from dima@burka.rdy.com) Received: (from dima@localhost) by burka.rdy.com (8.9.2/RDY&DVV) id OAA95175 for current@freebsd.org; Fri, 22 Jan 1999 14:54:08 -0800 (PST) Message-Id: <199901222254.OAA95175@burka.rdy.com> Subject: make world breakage To: current@FreeBSD.ORG Date: Fri, 22 Jan 1999 14:54:08 -0800 (PST) X-Class: Fast Organization: HackerDome Reply-To: dima@best.net From: dima@best.net (Dima Ruban) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey guys! After all these commits for secure/lib/libcrypt it seems that make world doesn't work anymore. ===> csu/i386-elf ===> libcom_err ===> libcom_err/doc ===> ../secure/lib/libcrypt cc -nostdinc -O -pipe -I/usr/src/secure/lib/libcrypt/../../../lib/libmd -Wall -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/secure/lib/libcrypt/crypt.c -o crypt.o make: don't know how to make crypt-md5.c. Stop *** Error code 2 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. burka# -- dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 15:10:38 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29131 for freebsd-current-outgoing; Fri, 22 Jan 1999 15:10:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA29104 for ; Fri, 22 Jan 1999 15:10:34 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.2/8.9.2/Netplex) with ESMTP id HAA36697; Sat, 23 Jan 1999 07:10:09 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199901222310.HAA36697@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Greg Lehey cc: Jake , current@FreeBSD.ORG Subject: Re: vinum read no longer works In-reply-to: Your message of "Sat, 23 Jan 1999 09:06:01 +1030." <19990123090601.E19921@freebie.lemis.com> Date: Sat, 23 Jan 1999 07:10:08 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > On Saturday, 23 January 1999 at 6:24:17 +0800, Peter Wemm wrote: > > Greg Lehey wrote: > >> On Friday, 22 January 1999 at 9:23:48 -0800, Jake wrote: > >>> I can no longer bring up my vinum volume with the vinum read > >>> command: > >>> > >>> vinum read /dev/wd0s1e /dev/wd2s1f > >>> vinum read /dev/wd0s1e > >>> vinum read /dev/wd2s1f > >>> > >>> all come back with > >>> vinum: no drives > >> > >> Correct. As I explained in detail in my HEADS UP message a couple of > >> days ago, you must now specify drives, not partitions. The correct > >> command might be > >> > >> vinum read /dev/wd0 /dev/wd2 > > > > Does vinum scan the slices? What if there are two freebsd slices? > > Currently it just scans the compatibility slice. I'll change that > later. What is worrying me was that wd0 is the "whole disk", not a "compatability slice"... I'm not quite sure how this is dealt with, vinumio.c does a DIOCGPART into &drive->partinfo.. Is this how it's finding the compatability slice info? As I understand it by looking at the unit numbers in /dev, and the subr_diskslice code: wd0c = whole compat slice (slice 0 = compat slice) wd0 = whole disk (this is slice 1 == whole disk != compat slice) wd0s1 == wd0s1c == whole of first slice (this is slice 2 in the major number). Now perhaps the DIOCGPART on slice 1 is being translated into the info for slice 0 (compat slice) but I don't quite see where. > > If somebody is working on a disk shared with something else (eg: > > DOS/windoze), then perhaps the examples should be: vinum read > > /dev/wd0s1 /dev/wd2s1 > > Interesting. Yes, I think this would work. > > The real problem here is that, as you know from private > correspondence, I haven't found a good way to determine what > partitions are on the system, so I go through with brute force and try > to open each possible partition. This will change when I find a > better way, but it shouldn't require incompatible changes to the > command line syntax again. With any luck, I *will* be able to say > `vinum start', and it will go out and find the partitions by itself. Well, we used to have a way, it was the #ifdef SLICE code. It used to actively probe the devices and went out and found all the disks, slices, labels etc. It would have been an ideal thing for vinum to hook into as it could notify vinum "hey, I've just found something that looks like it belongs to vinum!". When vinum was told about all the components needed to make up a volume and attached that to the system, the SLICE code would have probed for disklabels etc inside. That would have taken us 99% of the way to booting from a drive array with a root partition. > Greg Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 15:17:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00359 for freebsd-current-outgoing; Fri, 22 Jan 1999 15:17:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00343 for ; Fri, 22 Jan 1999 15:17:26 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id JAA28319; Sat, 23 Jan 1999 09:47:14 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.2/8.9.0) id JAA20353; Sat, 23 Jan 1999 09:47:13 +1030 (CST) Date: Sat, 23 Jan 1999 09:47:13 +1030 From: Greg Lehey To: Peter Wemm Cc: Jake , current@FreeBSD.ORG Subject: Re: vinum read no longer works Message-ID: <19990123094713.I19921@freebie.lemis.com> References: <19990123090601.E19921@freebie.lemis.com> <199901222310.HAA36697@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199901222310.HAA36697@spinner.netplex.com.au>; from Peter Wemm on Sat, Jan 23, 1999 at 07:10:08AM +0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, 23 January 1999 at 7:10:08 +0800, Peter Wemm wrote: > Greg Lehey wrote: >> On Saturday, 23 January 1999 at 6:24:17 +0800, Peter Wemm wrote: >>> Greg Lehey wrote: >>>> On Friday, 22 January 1999 at 9:23:48 -0800, Jake wrote: >>>>> I can no longer bring up my vinum volume with the vinum read >>>>> command: >>>>> >>>>> vinum read /dev/wd0s1e /dev/wd2s1f >>>>> vinum read /dev/wd0s1e >>>>> vinum read /dev/wd2s1f >>>>> >>>>> all come back with >>>>> vinum: no drives >>>> >>>> Correct. As I explained in detail in my HEADS UP message a couple of >>>> days ago, you must now specify drives, not partitions. The correct >>>> command might be >>>> >>>> vinum read /dev/wd0 /dev/wd2 >>> >>> Does vinum scan the slices? What if there are two freebsd slices? >> >> Currently it just scans the compatibility slice. I'll change that >> later. > > What is worrying me was that wd0 is the "whole disk", not a "compatability > slice"... I'm not quite sure how this is dealt with, vinumio.c does a > DIOCGPART into &drive->partinfo.. Is this how it's finding the > compatability slice info? > > As I understand it by looking at the unit numbers in /dev, and the > subr_diskslice code: > > wd0c = whole compat slice (slice 0 = compat slice) > wd0 = whole disk (this is slice 1 == whole disk != compat slice) > wd0s1 == wd0s1c == whole of first slice (this is slice 2 in the major number). > > Now perhaps the DIOCGPART on slice 1 is being translated into the info for > slice 0 (compat slice) but I don't quite see where. It's much more of a kludge than that. Remember, this is interim code while I look for the right way to do it. I take the name of the disk and append the letters a to h to them (omitting c), and try to open them. >>> If somebody is working on a disk shared with something else (eg: >>> DOS/windoze), then perhaps the examples should be: vinum read >>> /dev/wd0s1 /dev/wd2s1 >> >> Interesting. Yes, I think this would work. >> >> The real problem here is that, as you know from private >> correspondence, I haven't found a good way to determine what >> partitions are on the system, so I go through with brute force and try >> to open each possible partition. This will change when I find a >> better way, but it shouldn't require incompatible changes to the >> command line syntax again. With any luck, I *will* be able to say >> `vinum start', and it will go out and find the partitions by itself. > > Well, we used to have a way, it was the #ifdef SLICE code. It used to > actively probe the devices and went out and found all the disks, slices, > labels etc. It would have been an ideal thing for vinum to hook into as > it could notify vinum "hey, I've just found something that looks like it > belongs to vinum!". When vinum was told about all the components needed > to make up a volume and attached that to the system, the SLICE code would > have probed for disklabels etc inside. You mean Julian's SLICE code, right? Yes, I knew about that, and I'm agreed. But as you say, it's currently not there. I need a solution that works in all configurations. > That would have taken us 99% of the way to booting from a drive > array with a root partition. Maybe. There are a number of issues here, most of them minor but irritating. I haven't looked at it properly yet. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 15:36:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02083 for freebsd-current-outgoing; Fri, 22 Jan 1999 15:36:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02076 for ; Fri, 22 Jan 1999 15:36:03 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id PAA08517; Fri, 22 Jan 1999 15:34:38 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdUV8511; Fri Jan 22 23:34:32 1999 Date: Fri, 22 Jan 1999 15:34:26 -0800 (PST) From: Julian Elischer To: Mark Murray cc: Luoqi Chen , current@FreeBSD.ORG, brandon@whistle.com Subject: Re: world broken In-Reply-To: <199901222034.WAA97434@greenpeace.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark, can you announce when the fixes are in place? thanks, julian On Fri, 22 Jan 1999, Mark Murray wrote: > Luoqi Chen wrote: > > I spend half night yesterday to sort this mess out. If no one objects, > > I'll commit my fixes. (anyone volunteers to make the hat?) > > I know who gets the hat; please cool it on the fixes until the original > committer has finished. > > I'm watching this one closely, and I need to track it on Internat > as well. Not long now. > > M > -- > Mark Murray > Join the anti-SPAM movement: http://www.cauce.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 15:41:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02545 for freebsd-current-outgoing; Fri, 22 Jan 1999 15:41:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from top.worldcontrol.com (ppp3-24.sj.netmagic.net [209.24.171.56]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA02529 for ; Fri, 22 Jan 1999 15:41:00 -0800 (PST) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 13117 invoked by uid 100); 22 Jan 1999 23:40:02 -0000 Date: Fri, 22 Jan 1999 15:40:02 -0800 To: Dima Ruban Cc: current@FreeBSD.ORG Subject: Re: make world breakage Message-ID: <19990122154002.A13108@top.worldcontrol.com> References: <199901222254.OAA95175@burka.rdy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199901222254.OAA95175@burka.rdy.com>; from Dima Ruban on Fri, Jan 22, 1999 at 02:54:08PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > make: don't know how to make crypt-md5.c. Stop Me three. I was looking forward to testing all the VM improvements, but have been stuck because of this. I've watched the cvs-all list and haven't seen a mention of this being fixed. -- Brian Litzinger On Fri, Jan 22, 1999 at 02:54:08PM -0800, Dima Ruban wrote: > After all these commits for secure/lib/libcrypt it seems that > make world doesn't work anymore. > > ===> csu/i386-elf > ===> libcom_err > ===> libcom_err/doc > ===> ../secure/lib/libcrypt > cc -nostdinc -O -pipe -I/usr/src/secure/lib/libcrypt/../../../lib/libmd -Wall > -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/secure/lib/libcrypt/crypt.c -o > crypt.o > make: don't know how to make crypt-md5.c. Stop > *** Error code 2 >... > Stop. > *** Error code 1 > > Stop. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 15:41:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02557 for freebsd-current-outgoing; Fri, 22 Jan 1999 15:41:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02539 for ; Fri, 22 Jan 1999 15:41:03 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id SAA06198; Fri, 22 Jan 1999 18:40:55 -0500 (EST) Date: Fri, 22 Jan 1999 18:40:55 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Matthew Dillon cc: current@FreeBSD.ORG Subject: Re: kvm_getswapinfo() function added to libkvm. top, pstat, systat updated In-Reply-To: <199901221110.DAA52243@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 22 Jan 1999, Matthew Dillon wrote: > A new function, kvm_getswapinfo(), has been added to libkvm. > > pstat, systat, and top have been updated to use the new function. > > -Matt > > Matthew Dillon > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Where's struct kvm_swap and typedef struct kvm_swap *kvm_swap_t supposed to now be? Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 15:47:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03606 for freebsd-current-outgoing; Fri, 22 Jan 1999 15:47:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03599 for ; Fri, 22 Jan 1999 15:47:37 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id SAA21980; Fri, 22 Jan 1999 18:47:24 -0500 (EST) (envelope-from luoqi) Date: Fri, 22 Jan 1999 18:47:24 -0500 (EST) From: Luoqi Chen Message-Id: <199901222347.SAA21980@lor.watermarkgroup.com> To: luoqi@watermarkgroup.com, mark@grondar.za Subject: Re: world broken Cc: brandon@whistle.com, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Luoqi Chen wrote: > > I spend half night yesterday to sort this mess out. If no one objects, > > I'll commit my fixes. (anyone volunteers to make the hat?) > > I know who gets the hat; please cool it on the fixes until the original > committer has finished. > > I'm watching this one closely, and I need to track it on Internat > as well. Not long now. > > M > -- > Mark Murray > Join the anti-SPAM movement: http://www.cauce.org > Ok, I'll let the original committer do it. For those who can't wait to try Matt's new VM system, the following diff will help you get by. After applied the patch, mv/cp/ln secure/lib/libcrypt/crypt.c to crypt-des.c in the same directory. (I hope this patch doesn't reveal any information that would harm national security :-) -lq Index: lib/Makefile =================================================================== RCS file: /home/ncvs/src/lib/Makefile,v retrieving revision 1.87 diff -u -r1.87 Makefile --- Makefile 1998/12/17 23:02:11 1.87 +++ Makefile 1999/01/21 20:22:54 @@ -39,9 +39,7 @@ # Build both libraries. They have different names, so no harm, # and this avoids having stale libscrypt.* -.if exists(${.CURDIR}/../secure) && !defined(NOSECURE) && !defined(NOCRYPT) -_libcrypt= ../secure/lib/libcrypt libcrypt -.else +.if !defined(NOCRYPT) _libcrypt= libcrypt .endif Index: secure/lib/libcrypt/crypt.c =================================================================== RCS file: /home/ncvs/src/secure/lib/libcrypt/crypt.c,v retrieving revision 1.9 diff -u -r1.9 crypt.c --- crypt.c 1997/02/22 14:40:30 1.9 +++ crypt.c 1999/01/22 23:38:24 @@ -59,9 +59,8 @@ #include #include #include +#include "crypt.h" -char *crypt_md5(const char *pw, const char *salt); - /* We can't always assume gcc */ #ifdef __GNUC__ #define INLINE inline @@ -578,20 +577,26 @@ return(retval); } -char * -crypt(char *key, char *setting) +char * +crypt_des(pw, pl, sp, sl, passwd, token) + const unsigned char *pw; + const unsigned int pl; + const unsigned char *sp; + const unsigned int sl; + char * passwd; + char * token; { - int i; - u_long count, salt, l, r0, r1, keybuf[2]; - u_char *p, *q; - static u_char output[21]; + int i; + u_long count, salt, l, r0, r1, keybuf[2]; + u_char *p, *q; + u_char *key = pw, *setting = sp; + u_char *output = (u_char *)passwd; - if (!strncmp(setting, "$1$", 3)) - return crypt_md5(key, setting); + if (!*setting) + setting = key; if (!des_initialised) des_init(); - /* * Copy the key, shifting each character up by one bit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 16:24:39 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10285 for freebsd-current-outgoing; Fri, 22 Jan 1999 16:24:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA10279 for ; Fri, 22 Jan 1999 16:24:33 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id BAA04004; Sat, 23 Jan 1999 01:29:59 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Sat, 23 Jan 1999 01:29:59 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: "Jordan K. Hubbard" cc: Joao Carlos Mendes Luis , dhw@whistle.com, freebsd-current@FreeBSD.ORG, rdawes@ucsd.edu Subject: Re: boot.flp versions In-Reply-To: <40753.917032229@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 22 Jan 1999, Jordan K. Hubbard wrote: > OK, in retrospect, turning off swapping was a mistake. I should have > thought about this a bit more before blindly accepting the suggestion > from Andrzej. ;) Fixed. Oh well.. It made sense for me, I just thought it might help to save some space. It was only a few bytes anyway, and we're short of a couple of kBs now, so it's irrelevant... Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 16:30:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA11097 for freebsd-current-outgoing; Fri, 22 Jan 1999 16:30:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA10943 for ; Fri, 22 Jan 1999 16:29:59 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id BAA05184; Sat, 23 Jan 1999 01:35:56 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Sat, 23 Jan 1999 01:35:56 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Matthew Dillon cc: current@FreeBSD.ORG Subject: Re: kvm_getswapinfo() function added to libkvm. top, pstat, systat updated In-Reply-To: <199901221110.DAA52243@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 22 Jan 1999, Matthew Dillon wrote: > A new function, kvm_getswapinfo(), has been added to libkvm. > > pstat, systat, and top have been updated to use the new function. Have you considered using sysctl(3) for this instead? If yes, could you explain why the libkvm seemed better to you? (I'm asking because with libkvm you need to use /dev/kmem _and_ you need to access symbol table - this doesn't work with stripped kernels). Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 16:44:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA12329 for freebsd-current-outgoing; Fri, 22 Jan 1999 16:44:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA12240; Fri, 22 Jan 1999 16:44:00 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA10580; Fri, 22 Jan 1999 16:38:05 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdy10576; Sat Jan 23 00:38:02 1999 Date: Fri, 22 Jan 1999 16:37:59 -0800 (PST) From: Julian Elischer To: Mark Murray cc: Luoqi Chen , current@FreeBSD.ORG, brandon@FreeBSD.ORG Subject: Re: world broken In-Reply-To: <199901222034.WAA97434@greenpeace.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG so what happenned.. he checked in more stuff this morning and DIDN'T fix the build breakage from yesterday.. doesn't he know about it? On Fri, 22 Jan 1999, Mark Murray wrote: > Luoqi Chen wrote: > > I spend half night yesterday to sort this mess out. If no one objects, > > I'll commit my fixes. (anyone volunteers to make the hat?) > > I know who gets the hat; please cool it on the fixes until the original > committer has finished. > > I'm watching this one closely, and I need to track it on Internat > as well. Not long now. > > M > -- > Mark Murray > Join the anti-SPAM movement: http://www.cauce.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 16:51:53 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA13068 for freebsd-current-outgoing; Fri, 22 Jan 1999 16:51:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA13063 for ; Fri, 22 Jan 1999 16:51:49 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id AAA65352; Sat, 23 Jan 1999 00:50:38 GMT Date: Sat, 23 Jan 1999 00:50:37 +0000 (GMT) From: Doug Rabson To: Brian Feldman cc: Julian Elischer , "Richard Seaman, Jr." , Jeremy Lea , freebsd-current@FreeBSD.ORG, Peter Wemm Subject: Re: Using LinuxThreads In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 22 Jan 1999, Brian Feldman wrote: > On Fri, 22 Jan 1999, Doug Rabson wrote: > > > On Thu, 21 Jan 1999, Julian Elischer wrote: > > > > > > > > > > > On Thu, 21 Jan 1999, Richard Seaman, Jr. wrote: > > > > > > > > And when are COMPAT_LINUX_THREADS and VM_STACK going away? > > > > > > > > I have no idea. I was hoping that at least COMPAT_LINUX_THREADS > > > > would go away before the branch. I don't have commit authority, > > > > so it isn't up to me. > > > > > > > > > > hmm did you send me the patches? > > > > > > I can certainly do it now..(given a patch set to apply) > > > > > > I just realised however, that if we make them go away we break > > > SMP right? > > > hmm I guess we only break it for programs that woudltry use it > > > which should be none if you run SMP :-) > > > > It doesn't break SMP (I'm running an SMP kernel with > > COMPAT_LINUX_THREADS). All that happens is that linux_clone() returns > > an error. Surprisingly StarOffice still works fairly well. > > StarOffice 5.0? Is this with Luoqi's shared process across SMP patches? I don't have Luoqi's patches. StarOffice seems to work even if there is no thread support. Wierd. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 17:57:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA20989 for freebsd-current-outgoing; Fri, 22 Jan 1999 17:57:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA20984 for ; Fri, 22 Jan 1999 17:57:07 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id UAA04602; Fri, 22 Jan 1999 20:56:40 -0500 (EST) (envelope-from wollman) Date: Fri, 22 Jan 1999 20:56:40 -0500 (EST) From: Garrett Wollman Message-Id: <199901230156.UAA04602@khavrinen.lcs.mit.edu> To: Brian Feldman Cc: Matthew Dillon , current@FreeBSD.ORG Subject: Re: kvm_getswapinfo() function added to libkvm. top, pstat, systat updated In-Reply-To: References: <199901221110.DAA52243@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Where's struct kvm_swap and typedef struct kvm_swap *kvm_swap_t supposed to > now be? Hopefully the latter isn't anywhere, since style(9) says very specifically that such typedefs are Not To Be Introduced. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 18:18:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA24200 for freebsd-current-outgoing; Fri, 22 Jan 1999 18:18:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA24106 for ; Fri, 22 Jan 1999 18:17:58 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id VAA16461; Fri, 22 Jan 1999 21:17:48 -0500 (EST) Date: Fri, 22 Jan 1999 21:17:48 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Garrett Wollman cc: Matthew Dillon , current@FreeBSD.ORG Subject: Re: kvm_getswapinfo() function added to libkvm. top, pstat, systat updated In-Reply-To: <199901230156.UAA04602@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 22 Jan 1999, Garrett Wollman wrote: > < said: > > > Where's struct kvm_swap and typedef struct kvm_swap *kvm_swap_t supposed to > > now be? > > Hopefully the latter isn't anywhere, since style(9) says very > specifically that such typedefs are Not To Be Introduced. This doesn't change the fact that there seems to be them... Of course, without these definitions libkvm no longer will compile. > > -GAWollman > > -- > Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same > wollman@lcs.mit.edu | O Siem / The fires of freedom > Opinions not those of| Dance in the burning flame > MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 18:34:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA26554 for freebsd-current-outgoing; Fri, 22 Jan 1999 18:34:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA26539 for ; Fri, 22 Jan 1999 18:34:26 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.2/8.9.2/Netplex) with ESMTP id KAA00481; Sat, 23 Jan 1999 10:34:04 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199901230234.KAA00481@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon cc: current@FreeBSD.ORG Subject: panic: found dirty cache page 0xf046f1c0 Date: Sat, 23 Jan 1999 10:34:04 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dual p5-90 w/ 48M ram, doing a major cvs update/merge (which mostly got lost): panic: found dirty cache page 0xf046f1c0 mp_lock = 01000001; cpuid = 1; lapic.id = 01000000 Debugger("panic") Stopped at Debugger+0x37: movl $0,in_Debugger db> trace Debugger(f01f1806) at Debugger+0x37 panic(f01fbb50,f046f1c0,0,80,f45cbb20) at panic+0xa4 vm_page_alloc(f45f6f68,80,3,0,80) at vm_page_alloc+0x114 vm_page_grab(f45f6f68,80,83,0,80) at vm_page_grab+0x8d _pmap_allocpte(f45cbb20,80,201df000,201df000,2a86000) at _pmap_allocpte+0x19 pmap_allocpte(f45cbb20,201df000,f02c4df4,201df000,f45cbac0) at pmap_allocpte+0x53 pmap_enter(f45cbb20,201df000,2a86000,5,0) at pmap_enter+0x3d vm_fault(f45cbac0,201df000,1,0,f4195180) at vm_fault+0x891 trap_pfault(f45f9fbc,1,201df236) at trap_pfault+0xf2 trap(27,27,ffffffff,5,efbfad38) at trap+0x1c2 calltrap() at calltrap+0x3c --- trap 0xc, eip = 0x201df236, esp = 0xefbfac4c, ebp = 0xefbfad38 --- db> c boot() called on cpu#1 syncing disks... 232 232 232 232 232 232 232 232 232 232 232 232 232 232 232 232 232 232 232 232 giving up 1: dev:ffffffff, flags:20020034, blkno:1057008, lblkno:0 [..] This was compiled two houts ago from absolute latest -current: FreeBSD spinner.netplex.com.au 4.0-CURRENT FreeBSD 4.0-CURRENT #385: Sat Jan 23 08:38:42 WST 1999 peter@spinner.netplex.com.au:/home/src/sys/compile/SPINNER i386 My other SMP machine (2xPPro200) seems to be running fine: FreeBSD beast.netplex.com.au 4.0-CURRENT FreeBSD 4.0-CURRENT #267: Thu Jan 21 21:39:45 WST 1999 peter@beast.netplex.com.au:/home/src/sys/compile/BEAST i386 Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 19:09:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA01526 for freebsd-current-outgoing; Fri, 22 Jan 1999 19:09:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pozo.pozo.com (pozo.pozo.com [207.201.8.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA01467 for ; Fri, 22 Jan 1999 19:09:49 -0800 (PST) (envelope-from mantar@netcom.com) Received: from dual (DUAL [192.168.0.2]) by pozo.pozo.com (8.9.2/8.9.2) with SMTP id TAA07480; Fri, 22 Jan 1999 19:09:07 -0800 (PST) (envelope-from mantar@netcom.com) Message-Id: <4.1.19990122190240.00a1f7c0@192.168.0.1> X-Sender: null@192.168.0.1 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Fri, 22 Jan 1999 19:09:06 -0800 To: Peter Wemm , Matthew Dillon From: Manfred Antar Subject: Re: panic: found dirty cache page 0xf046f1c0 Cc: current@FreeBSD.ORG In-Reply-To: <199901230234.KAA00481@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:34 AM 1/23/99 +0800, Peter Wemm wrote: >Dual p5-90 w/ 48M ram, doing a major cvs update/merge (which mostly got >lost): > >panic: found dirty cache page 0xf046f1c0 >mp_lock = 01000001; cpuid = 1; lapic.id = 01000000 >Debugger("panic") >Stopped at Debugger+0x37: movl $0,in_Debugger >db> trace >Debugger(f01f1806) at Debugger+0x37 >panic(f01fbb50,f046f1c0,0,80,f45cbb20) at panic+0xa4 >vm_page_alloc(f45f6f68,80,3,0,80) at vm_page_alloc+0x114 >vm_page_grab(f45f6f68,80,83,0,80) at vm_page_grab+0x8d >_pmap_allocpte(f45cbb20,80,201df000,201df000,2a86000) at _pmap_allocpte+0x19 >pmap_allocpte(f45cbb20,201df000,f02c4df4,201df000,f45cbac0) at >pmap_allocpte+0x53 >pmap_enter(f45cbb20,201df000,2a86000,5,0) at pmap_enter+0x3d >vm_fault(f45cbac0,201df000,1,0,f4195180) at vm_fault+0x891 >trap_pfault(f45f9fbc,1,201df236) at trap_pfault+0xf2 >trap(27,27,ffffffff,5,efbfad38) at trap+0x1c2 >calltrap() at calltrap+0x3c >--- trap 0xc, eip = 0x201df236, esp = 0xefbfac4c, ebp = 0xefbfad38 --- >db> c >boot() called on cpu#1 > >syncing disks... 232 232 232 232 232 232 232 232 232 232 232 232 232 232 232 >232 > 232 232 232 232 giving up >1: dev:ffffffff, flags:20020034, blkno:1057008, lblkno:0 >[..] > >This was compiled two houts ago from absolute latest -current: >FreeBSD spinner.netplex.com.au 4.0-CURRENT FreeBSD 4.0-CURRENT #385: >Sat Jan 23 08:38:42 WST 1999 >peter@spinner.netplex.com.au:/home/src/sys/compile/SPINNER i386 > >My other SMP machine (2xPPro200) seems to be running fine: >FreeBSD beast.netplex.com.au 4.0-CURRENT FreeBSD 4.0-CURRENT #267: >Thu Jan 21 21:39:45 WST 1999 >peter@beast.netplex.com.au:/home/src/sys/compile/BEAST i386 > >Cheers, >-Peter > I just got the same thing doing a make -j8 world Machine is a dual pentium pro Intel PR440FX This must be from the recent vm changes as I could make -j8 world continually a few days ago without problem. This is the second time it happened to me the first time I was running X so I couldn't see the debugger message . This time without X I got the : panic: found dirty cache page Manfred ===================== || mantar@netcom.com || || pozo@infinex.com || || Ph. (415) 681-6235 || ===================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 19:21:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA03083 for freebsd-current-outgoing; Fri, 22 Jan 1999 19:21:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA03074 for ; Fri, 22 Jan 1999 19:21:46 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id MAA15002; Sat, 23 Jan 1999 12:21:25 +0900 (JST) Message-ID: <36A93D71.328C06C1@newsguy.com> Date: Sat, 23 Jan 1999 12:09:37 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Tim , freebsd-current@FreeBSD.ORG Subject: Re: PNP and new bootloader with ELF kernel References: <19990122122226.A2328@terry.dragon2.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tim wrote: > > >and, in your /boot/loader.rc, put > > > >load /kernel > >load -t userconfig_script /kernel.config > > Thanks for the info but unfortunately this has not worked, maybe this is > the syntax I have used in the /kernel.config file > > pnp 1 enable os irq0 11 port0 0x3e8 > > used to work before > > else what permissions do the files need to be > > also, where did you find this load -t stuff load -t stuff is new stuff, currently undocumented, with the sole exception of "help" at loader's prompt (I assume you are using current from sometime this month, since the new loader was introduced in november/december). The load -t stuff is what will make /kernel.config get read. Your old contents for that file should be ok otherwise. Before modifying /boot/loader.rc, though, you might just *type* these commands at the loader's prompt (followed by "boot"), to test if they actually work. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com If you sell your soul to the Devil and all you get is an MCSE from it, you haven't gotten market rate. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 20:00:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA07433 for freebsd-current-outgoing; Fri, 22 Jan 1999 20:00:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA07421 for ; Fri, 22 Jan 1999 20:00:43 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.2/8.9.2/Netplex) with ESMTP id MAA00394; Sat, 23 Jan 1999 12:00:12 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199901230400.MAA00394@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon , current@FreeBSD.ORG Subject: Re: panic: found dirty cache page 0xf046f1c0 In-reply-to: Your message of "Sat, 23 Jan 1999 10:34:04 +0800." <199901230234.KAA00481@spinner.netplex.com.au> Date: Sat, 23 Jan 1999 12:00:10 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: > Dual p5-90 w/ 48M ram, doing a major cvs update/merge (which mostly got > lost): > > panic: found dirty cache page 0xf046f1c0 > mp_lock = 01000001; cpuid = 1; lapic.id = 01000000 > Debugger("panic") > Stopped at Debugger+0x37: movl $0,in_Debugger > db> trace This is possibly a false alarm.. Something wierd was happening. I cleaned out the kernel and reconfigured with NFS static (it was being loaded) and it seems to boot OK. At least, I'm not getting console corruption (random baud rate changes) and the SMP mutex being broken and both cpu's entering the kernel at once..... I think I'll blame it on the 15 hour electrical storm. :-] Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 20:32:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA11256 for freebsd-current-outgoing; Fri, 22 Jan 1999 20:32:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA11250 for ; Fri, 22 Jan 1999 20:32:26 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id UAA58243; Fri, 22 Jan 1999 20:30:28 -0800 (PST) (envelope-from dillon) Date: Fri, 22 Jan 1999 20:30:28 -0800 (PST) From: Matthew Dillon Message-Id: <199901230430.UAA58243@apollo.backplane.com> To: Peter Wemm Cc: current@FreeBSD.ORG Subject: Re: panic: found dirty cache page 0xf046f1c0 References: <199901230400.MAA00394@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Peter Wemm wrote: :> Dual p5-90 w/ 48M ram, doing a major cvs update/merge (which mostly got :> lost): :> :> panic: found dirty cache page 0xf046f1c0 :... : :This is possibly a false alarm.. Something wierd was happening. I cleaned :out the kernel and reconfigured with NFS static (it was being loaded) and :it seems to boot OK. At least, I'm not getting console corruption (random :baud rate changes) and the SMP mutex being broken and both cpu's entering :the kernel at once..... I think I'll blame it on the 15 hour electrical :storm. :-] : :Cheers, :-Peter An old nfs module would almost certainly not work with the new kernel without at least a recompile. I'd definitely recommend keeping the major modules compiled in rather then dynamically loaded, just on principle. In fact, in all my time at BEST and all my time playing with FreeBSD, I have *never* used any dynamic module except for the linux compatibility thingy, and even that was only a fluke. If you can compile it in, compile it in. But, keep a watch on it. I didn't have an SMP box to test the new VM stuff on so it's possible there's something going on there. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 20:44:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA12051 for freebsd-current-outgoing; Fri, 22 Jan 1999 20:44:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA12046 for ; Fri, 22 Jan 1999 20:44:29 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id UAA58355; Fri, 22 Jan 1999 20:44:17 -0800 (PST) (envelope-from dillon) Date: Fri, 22 Jan 1999 20:44:17 -0800 (PST) From: Matthew Dillon Message-Id: <199901230444.UAA58355@apollo.backplane.com> To: Andrzej Bialecki Cc: current@FreeBSD.ORG Subject: Re: kvm_getswapinfo() function added to libkvm. top, pstat, systat updated References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Fri, 22 Jan 1999, Matthew Dillon wrote: : :> A new function, kvm_getswapinfo(), has been added to libkvm. :> :> pstat, systat, and top have been updated to use the new function. : :Have you considered using sysctl(3) for this instead? If yes, could you :explain why the libkvm seemed better to you? That's easy. Look how much code kvm_getswapinfo() is and tell me that you want to waste that memory in the kernel. :(I'm asking because with libkvm you need to use /dev/kmem _and_ you need :to access symbol table - this doesn't work with stripped kernels). : :Andrzej Bialecki You can boot with a stripped kernel and then point the system's notion of the kernel binary to a non-stripped version. That doesn't handle permissions, but getting deep-down swap information is not something any standard utility ever needs to do. It isn't something like getting the load average, which utilities may legitimately need. For that reason, I see no problem leaving kvm_getswapinfo() in libkvm. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 20:47:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA12644 for freebsd-current-outgoing; Fri, 22 Jan 1999 20:47:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA12637 for ; Fri, 22 Jan 1999 20:47:49 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id UAA58388; Fri, 22 Jan 1999 20:47:33 -0800 (PST) (envelope-from dillon) Date: Fri, 22 Jan 1999 20:47:33 -0800 (PST) From: Matthew Dillon Message-Id: <199901230447.UAA58388@apollo.backplane.com> To: Manfred Antar Cc: Peter Wemm , current@FreeBSD.ORG Subject: Re: panic: found dirty cache page 0xf046f1c0 References: <4.1.19990122190240.00a1f7c0@192.168.0.1> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :At 10:34 AM 1/23/99 +0800, Peter Wemm wrote: :>Dual p5-90 w/ 48M ram, doing a major cvs update/merge (which mostly got :>lost): :> :>panic: found dirty cache page 0xf046f1c0 :>mp_lock = 01000001; cpuid = 1; lapic.id = 01000000 :... :I just got the same thing doing a make -j8 world :Machine is a dual pentium pro Intel PR440FX :This must be from the recent vm changes as I could make -j8 world :continually a :few days ago without problem. This is the second time it happened to me :the first time I was running X so I couldn't see the debugger message . :This time without X I got the : : :panic: found dirty cache page : :Manfred Any dynamically loaded modules? e.g. nfs? Did you update /usr/src/contrib/sys (i.e. softupdates ) along with /usr/src/sys ? Are you using vinum? -Matt :===================== :|| mantar@netcom.com || :|| pozo@infinex.com || :|| Ph. (415) 681-6235 || :===================== Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 21:05:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA14777 for freebsd-current-outgoing; Fri, 22 Jan 1999 21:05:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA14772 for ; Fri, 22 Jan 1999 21:05:47 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id AAA25899; Sat, 23 Jan 1999 00:05:20 -0500 (EST) Date: Sat, 23 Jan 1999 00:05:20 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Manfred Antar cc: Peter Wemm , Matthew Dillon , current@FreeBSD.ORG Subject: Re: panic: found dirty cache page 0xf046f1c0 In-Reply-To: <4.1.19990122190240.00a1f7c0@192.168.0.1> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 22 Jan 1999, Manfred Antar wrote: > At 10:34 AM 1/23/99 +0800, Peter Wemm wrote: > >Dual p5-90 w/ 48M ram, doing a major cvs update/merge (which mostly got > >lost): > > > >panic: found dirty cache page 0xf046f1c0 > >mp_lock = 01000001; cpuid = 1; lapic.id = 01000000 > >Debugger("panic") > >Stopped at Debugger+0x37: movl $0,in_Debugger > >db> trace > >Debugger(f01f1806) at Debugger+0x37 > >panic(f01fbb50,f046f1c0,0,80,f45cbb20) at panic+0xa4 > >vm_page_alloc(f45f6f68,80,3,0,80) at vm_page_alloc+0x114 > >vm_page_grab(f45f6f68,80,83,0,80) at vm_page_grab+0x8d > >_pmap_allocpte(f45cbb20,80,201df000,201df000,2a86000) at _pmap_allocpte+0x19 > >pmap_allocpte(f45cbb20,201df000,f02c4df4,201df000,f45cbac0) at > >pmap_allocpte+0x53 > >pmap_enter(f45cbb20,201df000,2a86000,5,0) at pmap_enter+0x3d > >vm_fault(f45cbac0,201df000,1,0,f4195180) at vm_fault+0x891 > >trap_pfault(f45f9fbc,1,201df236) at trap_pfault+0xf2 > >trap(27,27,ffffffff,5,efbfad38) at trap+0x1c2 > >calltrap() at calltrap+0x3c > >--- trap 0xc, eip = 0x201df236, esp = 0xefbfac4c, ebp = 0xefbfad38 --- > >db> c > >boot() called on cpu#1 > > > >syncing disks... 232 232 232 232 232 232 232 232 232 232 232 232 232 232 232 > >232 > > 232 232 232 232 giving up > >1: dev:ffffffff, flags:20020034, blkno:1057008, lblkno:0 > >[..] > > > >This was compiled two houts ago from absolute latest -current: > >FreeBSD spinner.netplex.com.au 4.0-CURRENT FreeBSD 4.0-CURRENT #385: > >Sat Jan 23 08:38:42 WST 1999 > >peter@spinner.netplex.com.au:/home/src/sys/compile/SPINNER i386 > > > >My other SMP machine (2xPPro200) seems to be running fine: > >FreeBSD beast.netplex.com.au 4.0-CURRENT FreeBSD 4.0-CURRENT #267: > >Thu Jan 21 21:39:45 WST 1999 > >peter@beast.netplex.com.au:/home/src/sys/compile/BEAST i386 > > > >Cheers, > >-Peter > > > I just got the same thing doing a make -j8 world > Machine is a dual pentium pro Intel PR440FX > This must be from the recent vm changes as I could make -j8 world > continually a > few days ago without problem. This is the second time it happened to me > the first time I was running X so I couldn't see the debugger message . > This time without X I got the : > > panic: found dirty cache page You should definitely be using DDB_UNATTENDED, by the way, if you're going to be running X and want DDB but not to have DDB try to pop up on a panic. I did get DDB_UNATTENDED behavior finally working as well as it should, so there's no reason not to use it. > > Manfred > ===================== > || mantar@netcom.com || > || pozo@infinex.com || > || Ph. (415) 681-6235 || > ===================== > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 21:53:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA18411 for freebsd-current-outgoing; Fri, 22 Jan 1999 21:53:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA18406 for ; Fri, 22 Jan 1999 21:53:27 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id VAA16685 for ; Fri, 22 Jan 1999 21:36:06 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdB16683; Sat Jan 23 05:36:05 1999 Message-ID: <36A95FC1.794BDF32@whistle.com> Date: Fri, 22 Jan 1999 21:36:01 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.8-RELEASE i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: -current now dead for over 24 hours. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG All because of a makefile snaffoo.. luoqi has a patch to fix it, but if anyone knows what the author was trying to achieve, can they please try fixing it? julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 22:12:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA20315 for freebsd-current-outgoing; Fri, 22 Jan 1999 22:12:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA20308 for ; Fri, 22 Jan 1999 22:12:05 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id WAA29555; Fri, 22 Jan 1999 22:11:54 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id WAA12057; Fri, 22 Jan 1999 22:11:53 -0800 (PST) (envelope-from jdp@polstra.com) Date: Fri, 22 Jan 1999 22:11:53 -0800 (PST) Message-Id: <199901230611.WAA12057@vashon.polstra.com> To: gnb@itga.com.au Subject: Re: some guidance on forked cvsup please Newsgroups: polstra.freebsd.current In-Reply-To: <199901210732.SAA09979@lightning.itga.com.au> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199901210732.SAA09979@lightning.itga.com.au>, Gregory Bond wrote: > Now we've gone and got forked, can someone please give us examples of cvsup > files for those that want to follow 4-current and those that want to follow > 3-stable. To track -current, the cvsupfile should contain "tag=." To track 3-stable, it should contain "tag=RELENG_3". For the rest of the cvsupfile, see the examples in "/usr/share/examples/cvsup". I haven't updated them with the new RELENG_3 tag yet, but I will do that soon. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 22:20:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA20897 for freebsd-current-outgoing; Fri, 22 Jan 1999 22:20:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA20892 for ; Fri, 22 Jan 1999 22:20:07 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.2/8.9.2/Netplex) with ESMTP id OAA06346; Sat, 23 Jan 1999 14:19:53 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199901230619.OAA06346@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon cc: current@FreeBSD.ORG Subject: Re: panic: found dirty cache page 0xf046f1c0 In-reply-to: Your message of "Fri, 22 Jan 1999 20:30:28 PST." <199901230430.UAA58243@apollo.backplane.com> Date: Sat, 23 Jan 1999 14:19:52 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > :Peter Wemm wrote: > :> Dual p5-90 w/ 48M ram, doing a major cvs update/merge (which mostly got > :> lost): > :> > :> panic: found dirty cache page 0xf046f1c0 > :... > : > :This is possibly a false alarm.. Something wierd was happening. I cleaned > :out the kernel and reconfigured with NFS static (it was being loaded) and > :it seems to boot OK. At least, I'm not getting console corruption (random > :baud rate changes) and the SMP mutex being broken and both cpu's entering > :the kernel at once..... I think I'll blame it on the 15 hour electrical > :storm. :-] > : > :Cheers, > :-Peter > > An old nfs module would almost certainly not work with the new > kernel without at least a recompile. I'd definitely recommend > keeping the major modules compiled in rather then dynamically > loaded, just on principle. In fact, in all my time at BEST and > all my time playing with FreeBSD, I have *never* used any > dynamic module except for the linux compatibility thingy, and > even that was only a fluke. If you can compile it in, compile > it in. It's definately happening still, sorry. :-( I recompiled a 100% static kernel and have had three more explosions, usually after starting exmh. (exmh takes 10 to 15MB of ram on this system due to my mailbox folder sizes). > But, keep a watch on it. I didn't have an SMP box to test > the new VM stuff on so it's possible there's something going > on there. However, a clue.. The SMP box that is doing fine is a P6, an NFS client and server (loading nfs.ko, it fsck's fast, so I use that box for making sure the modules work). The one that is crashing, is a P5, an NFS client and server (static kernel), and with a MFS /tmp. Both run softupdates (up to date src/contrib/sys). I suspect MFS is the key. There's the new VOP_FREEBLKS() stuff you added, and the corresponding calls to madvise to free the pages. Given madvise()'s murky history, I can't help but feel suspicious about it. I've unmounted /tmp and am about to thrash the machine. At the moment, it's sitting on: Swap: 120M Total, 376K Used, 120M Free Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 22:35:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA22374 for freebsd-current-outgoing; Fri, 22 Jan 1999 22:35:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.128.29.136]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA22365 for ; Fri, 22 Jan 1999 22:35:12 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: (from mi@localhost) by kot.ne.mediaone.net (8.9.1a/8.9.1) id BAA22200 for current@FreeBSD.ORG; Sat, 23 Jan 1999 01:34:40 -0500 (EST) From: Mikhail Teterin Message-Id: <199901230634.BAA22200@kot.ne.mediaone.net> Subject: softupdates bug shows on zip drive and parallel port in NIBBLE mode To: current@FreeBSD.ORG Date: Sat, 23 Jan 1999 01:34:40 -0500 (EST) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" When I try to cp a big file (Wordperfect distribution) onto a Zip > cartridge (with ufs with softupdates) the whole system becomes "jerky" > and soon hangs -- I can still go from one virtual console to another, > but can not do anything and need cold reboot. [...] try searching the lists, my suggestion is to compile like so: controller ppc0 at isa? disable port ? tty irq 7 change to: controller ppc0 at isa? disable port ? cam irq 7 -----------------------------------------^^^ you may also want to try 'bio' it's been explained on the lists and i'm unsure. ----- End of forwarded message from Alfred Perlstein ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 22:44:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA23369 for freebsd-current-outgoing; Fri, 22 Jan 1999 22:44:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA23328 for ; Fri, 22 Jan 1999 22:44:00 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.9.1) id WAA03481; Fri, 22 Jan 1999 22:44:59 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199901230644.WAA03481@troutmask.apl.washington.edu> Subject: Re: -current now dead for over 24 hours. In-Reply-To: <36A95FC1.794BDF32@whistle.com> from Julian Elischer at "Jan 22, 1999 9:36: 1 pm" To: julian@whistle.com (Julian Elischer) Date: Fri, 22 Jan 1999 22:44:59 -0800 (PST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer wrote: > All because of a makefile snaffoo.. > luoqi has a patch to fix it, but if anyone knows what > the author was trying to achieve, can they please try fixing it? > brandon and markm seem to have vanished. Please, commit luoqi's patch. You have commit privilege. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 22:59:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA24461 for freebsd-current-outgoing; Fri, 22 Jan 1999 22:59:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from monk.via.net (monk.via.net [209.81.9.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA24455 for ; Fri, 22 Jan 1999 22:59:25 -0800 (PST) (envelope-from joe@monk.via.net) Received: (from joe@localhost) by monk.via.net (8.8.8/8.8.8) id WAA13353 for freebsd-current@FreeBSD.ORG; Fri, 22 Jan 1999 22:59:15 -0800 (PST) (envelope-from joe) From: Joe McGuckin Message-Id: <199901230659.WAA13353@monk.via.net> Date: Fri, 22 Jan 1999 22:59:15 -0800 (PST) To: freebsd-current@FreeBSD.ORG Subject: SOFTUPDATES code in 3.0-RELEASE X-Mailer: Ishmail 1.3.1-970608-bsdi MIME-Version: 1.0 Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is this code included, or must it be patched in? Is softupdates enabled by default or do I have to use a special mount flag? Thanks, Joe Joe McGuckin ViaNet Communications 1235 Pear Ave, Suite 107 Mountain View, CA 90403 Phone: 650-969-2203 Cell: 415-710-4894 Fax: 650-969-2124 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 23:06:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA25180 for freebsd-current-outgoing; Fri, 22 Jan 1999 23:06:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smarter.than.nu (lal-99-91.Reshall.Berkeley.EDU [169.229.99.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA25175 for ; Fri, 22 Jan 1999 23:06:54 -0800 (PST) (envelope-from brian@CSUA.Berkeley.EDU) Received: from localhost (localhost [127.0.0.1]) by smarter.than.nu (8.9.1/8.9.1) with ESMTP id XAA78503; Fri, 22 Jan 1999 23:06:43 -0800 (PST) (envelope-from brian@CSUA.Berkeley.EDU) Date: Fri, 22 Jan 1999 23:06:43 -0800 (PST) From: "Brian W. Buchanan" X-Sender: brian@smarter.than.nu To: Joe McGuckin cc: freebsd-current@FreeBSD.ORG Subject: Re: SOFTUPDATES code in 3.0-RELEASE In-Reply-To: <199901230659.WAA13353@monk.via.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 22 Jan 1999, Joe McGuckin wrote: > Is this code included, or must it be patched in? Because of licensing issues, you have to enable it yourself. See the instructions in /sys/ufs/ffs/README.softupdates for how to do this. > Is softupdates enabled by default or do I have to use a special > mount flag? Neither. :) Once you have a softupdates kernel, you use "tunefs -n enable" on the unmounted filesystem to enable softupdates. (You only have to do this once.) -- Brian Buchanan brian@CSUA.Berkeley.EDU -------------------------------------------------------------------------- FreeBSD - The Power to Serve! http://www.freebsd.org daemon(n): 1. an attendant power or spirit : GENIUS 2. the cute little mascot of the FreeBSD operating system To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 23:17:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA25840 for freebsd-current-outgoing; Fri, 22 Jan 1999 23:17:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA25832 for ; Fri, 22 Jan 1999 23:17:24 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.1) with ESMTP id JAA13035; Sat, 23 Jan 1999 09:17:10 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.2/8.9.2) with ESMTP id JAA36219; Sat, 23 Jan 1999 09:17:09 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199901230717.JAA36219@greenpeace.grondar.za> To: Steve Kargl cc: julian@whistle.com (Julian Elischer), current@FreeBSD.ORG Subject: Re: -current now dead for over 24 hours. In-Reply-To: Your message of " Fri, 22 Jan 1999 22:44:59 PST." <199901230644.WAA03481@troutmask.apl.washington.edu> References: <199901230644.WAA03481@troutmask.apl.washington.edu> Date: Sat, 23 Jan 1999 09:17:07 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steve Kargl wrote: > Julian Elischer wrote: > > All because of a makefile snaffoo.. > > luoqi has a patch to fix it, but if anyone knows what > > the author was trying to achieve, can they please try fixing it? > > > > brandon and markm seem to have vanished. Please, commit > luoqi's patch. You have commit privilege. I have not! Fix coming! M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 22 23:49:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA28041 for freebsd-current-outgoing; Fri, 22 Jan 1999 23:49:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA28036 for ; Fri, 22 Jan 1999 23:49:20 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id XAA16308 for ; Fri, 22 Jan 1999 23:49:10 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma016306; Fri, 22 Jan 99 23:48:51 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id XAA14754 for current@FreeBSD.ORG; Fri, 22 Jan 1999 23:48:51 -0800 (PST) From: Archie Cobbs Message-Id: <199901230748.XAA14754@bubba.whistle.com> Subject: kvm question To: current@FreeBSD.ORG Date: Fri, 22 Jan 1999 23:48:50 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I ran into an interesting problem in the process of modifying "netstat" to understand the PF_NETGRAPH protocol family. "netstat" uses kvm_read(), etc. to read kernel symbols. However, this doesn't work when the symbols you're looking for are in an KLD module (eg, ng_socket.ko) -- the symbol will not be found. So I added some code/hackery to look for any loaded modules and if on named "ng_socket.ko" was found, try finding the symbol in there. My question is, should kvm_read() and friends be "enhanced" with this ability to find a symbol by searching through the loaded KLD modules? Seems a bit hackish, but then again so is the whole kvm() idea. I'd be willing to add this code if so.. it's not much. Unrelated question: SYSINIT() doesn't work from KLD modules. Is this problem being addressed? -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 00:08:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA29487 for freebsd-current-outgoing; Sat, 23 Jan 1999 00:08:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA29481 for ; Sat, 23 Jan 1999 00:08:21 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.1) with ESMTP id KAA13098; Sat, 23 Jan 1999 10:07:59 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.2/8.9.2) with ESMTP id KAA36520; Sat, 23 Jan 1999 10:07:58 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199901230807.KAA36520@greenpeace.grondar.za> To: Julian Elischer cc: Luoqi Chen , current@FreeBSD.ORG, brandon@whistle.com Subject: Re: world broken In-Reply-To: Your message of " Fri, 22 Jan 1999 15:34:26 PST." References: Date: Sat, 23 Jan 1999 10:07:57 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer wrote: > can you announce when the fixes are in place? I'll do better; I am about to back it all out. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 00:43:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA02413 for freebsd-current-outgoing; Sat, 23 Jan 1999 00:43:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA02406 for ; Sat, 23 Jan 1999 00:43:26 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id AAA19316; Sat, 23 Jan 1999 00:43:06 -0800 (PST) Received: from s204m82.isp.whistle.com(207.76.204.82) via SMTP by alpo.whistle.com, id smtpdb19307; Sat Jan 23 08:42:56 1999 Date: Sat, 23 Jan 1999 00:42:53 -0800 (PST) From: Julian Elischer X-Sender: julian@s204m82.isp.whistle.com To: Archie Cobbs cc: current@FreeBSD.ORG Subject: Re: kvm question In-Reply-To: <199901230748.XAA14754@bubba.whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 22 Jan 1999, Archie Cobbs wrote: > > Unrelated question: SYSINIT() doesn't work from KLD modules. > Is this problem being addressed? you mean sysctl > > -Archie > > ___________________________________________________________________________ > Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 00:47:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA02969 for freebsd-current-outgoing; Sat, 23 Jan 1999 00:47:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA02964 for ; Sat, 23 Jan 1999 00:47:29 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id AAA44590; Sat, 23 Jan 1999 00:47:03 -0800 (PST) (envelope-from dillon) Date: Sat, 23 Jan 1999 00:47:03 -0800 (PST) From: Matthew Dillon Message-Id: <199901230847.AAA44590@apollo.backplane.com> To: Peter Wemm Cc: current@FreeBSD.ORG Subject: Re: panic: found dirty cache page 0xf046f1c0 References: <199901230619.OAA06346@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :It's definately happening still, sorry. :-( I recompiled a 100% static :kernel and have had three more explosions, usually after starting exmh. :(exmh takes 10 to 15MB of ram on this system due to my mailbox folder :sizes). : :However, a clue.. The SMP box that is doing fine is a P6, an NFS client :and server (loading nfs.ko, it fsck's fast, so I use that box for making :sure the modules work). The one that is crashing, is a P5, an NFS client :and server (static kernel), and with a MFS /tmp. Both run softupdates (up :to date src/contrib/sys). : :I suspect MFS is the key. There's the new VOP_FREEBLKS() stuff you added, :and the corresponding calls to madvise to free the pages. : :Given madvise()'s murky history, I can't help but feel suspicious about it. : :I've unmounted /tmp and am about to thrash the machine. At the :moment, it's sitting on: Swap: 120M Total, 376K Used, 120M Free : :Cheers, :-Peter Hmmm. It's possible. A quick look at the exmh source indicates that it uses /tmp a lot. I've been doing make buildworld's with a 300MB MFS /usr/obj, but those are typically nothing more then simple file creates, reads, and writes. Presumably exmh is doing something more sophisticated. Try changing the panic in vm/vm_page.c to a printf() ( if (m->dirty) panic("found dirty cache page %p", m); if (m->dirty) printf( "found dirty cache page %p (%p,%d,%x) obtype %d obflags %x", m, m->object, (int)m->pindex, (int)m->flags, (int)m->object->type, (int)m->object->flags ); Lets see what we get. This should tell me what kind of object the page is attached to and the flags of the page and object. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 01:10:52 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA04489 for freebsd-current-outgoing; Sat, 23 Jan 1999 01:10:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA04484; Sat, 23 Jan 1999 01:10:51 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id BAA16737; Sat, 23 Jan 1999 01:10:42 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma016735; Sat, 23 Jan 99 01:10:32 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id BAA14995; Sat, 23 Jan 1999 01:10:32 -0800 (PST) From: Archie Cobbs Message-Id: <199901230910.BAA14995@bubba.whistle.com> Subject: Re: DEVFS, the time has come... In-Reply-To: <94808.915113237@critter.freebsd.dk> from Poul-Henning Kamp at "Dec 31, 98 03:07:17 pm" To: arch@FreeBSD.ORG Date: Sat, 23 Jan 1999 01:10:32 -0800 (PST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp writes: > ... to make up our mind about it. > > [ clear arguments for DEVFS and why persistence is complicated ] This email was a few weeks ago, and there was a lively debate, then Julian sent an email listing some issues/requirements, and then the thread kindof died and now we're back to where we were before, which is not any further on.. So I'd like to make another attempt to get agreement on the next step here, so that *something* can happen. We need to get more people using DEVFS, so we can gain some experience & feedback. I don't think DEVFS has any issues that are not surmountable. However, at some point you must take the next step. To do this, we need to come up with a 'next step' that doesn't necessarily make everybody happy, but does make enough people happy that they can use it and it becomes somewhat 'mainstream'... Here's my proposal, which is basically the same thing Poul was suggesting: - Have a non-persistent DEVFS in the kernel; when devices appear they have the default permissions - Have an /etc/rc.devices script to make any site-specific customizations at boot up - Have a mount flag that would disable the apperance of new devices - DEVFS remains a kernel option for now To try and answer some of the issues from Julian's email, in the interest of making decisions so we can proceed: > 3/ The filesystem needs to give a method to allow new devices to appear > as created. If the layout of a /chroot/dev filesystem has been > changed, then you need to work out WHERE in the filesystem to > create the new device. Devices should appear in the same place (relative to the root of the mount) every time. For now, this path can be hardwired in the device driver. > 4/ If a user changes the name of a device or makes a link to it, those > devices must still be removed when the device becomes invalid. > ... > 6/ If a process has a device open and it 'goes away', what should happen? No automatic removal of device nodes.. if the device goes away, then operations start returning ENXIO or whatever. After all, this is what a non-DEVFS system would do in the same situation (if it could). > 7/ Persistence is I think a WOFTAM. Some people want it. It could be > ignored in my opinion but you should at least have a scheme in > mind.. My suggestion is to pick up permissions and owners from > inodes of the same name read from the filesystem on which the devfs > was mounted. A synthetic / filesystem (An idea that I know Poul has > been kicking around for a while) wouldn't be able to do that, but > there are other ideas I guess. Devices appear with default permissions and ownership... always. "What about a new device that appears when I insert my PCCARD?" Well, you can always do what you do now, which is not have them appear, So at least things get no worse. "Well, actually now I have the device node with my special permissions set already created in /dev, so when the PCCARD is inserted, the device node already exists with those permissions..". Good question.. for now, we ignore this case (and potentially lose a few DEVFS customers). Solving this can be part of the next step. Ideas: (a) have a user daemon; (b) have DEVFS inherit permissions from a 'stub' node of the same name that already exists (if any) when the device appears (then /etc/rc.devices could do its thing for these dynamically appearing nodes as well). > 5/ If a device has its modification time changed, does that change > reflect through all instances of that device? (E.g. /dev/xxx and > /chroot/dev/xxx). What about permissions? What about ownerships? No.. separate nodes are separate files, they just refer to the same device. OK.. so there is some percentage X% of people for whom this proposal would be sufficient to use DEVFS on their systems. Personally, I find it hard to believe that X is not a large number, because for "normal" usage you'd get exactly what we have now, functionally speaking. It seems like this proposal would make DEVFS acceptable for a large percentage of folks.. but definitely not 100% -- and that's OK for a first step. Ultimately, we want to get to a fully DEVFS world. By taking a few steps at a time, and getting people to *use* it, we can eventually discover and address everybody's concerns. Comments?? The issue here is not whether this proposal is a sufficient *final* incarnation of DEVFS, but whether it's a sufficient next step.. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 01:12:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA04789 for freebsd-current-outgoing; Sat, 23 Jan 1999 01:12:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA04784 for ; Sat, 23 Jan 1999 01:12:26 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id BAA16750; Sat, 23 Jan 1999 01:12:12 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma016746; Sat, 23 Jan 99 01:12:11 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id BAA15056; Sat, 23 Jan 1999 01:12:11 -0800 (PST) From: Archie Cobbs Message-Id: <199901230912.BAA15056@bubba.whistle.com> Subject: Re: kvm question In-Reply-To: from Julian Elischer at "Jan 23, 99 00:42:53 am" To: julian@whistle.com (Julian Elischer) Date: Sat, 23 Jan 1999 01:12:11 -0800 (PST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer writes: > On Fri, 22 Jan 1999, Archie Cobbs wrote: > > Unrelated question: SYSINIT() doesn't work from KLD modules. > > Is this problem being addressed? > > you mean sysctl Oops, thanks.. SYSCTL() doesn't work from KLD modules but SYSINIT() does. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 01:25:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA05533 for freebsd-current-outgoing; Sat, 23 Jan 1999 01:25:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA05523 for ; Sat, 23 Jan 1999 01:25:26 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.2/8.9.2/Netplex) with ESMTP id RAA00489; Sat, 23 Jan 1999 17:25:03 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199901230925.RAA00489@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon cc: current@FreeBSD.ORG Subject: Re: panic: found dirty cache page 0xf046f1c0 In-reply-to: Your message of "Sat, 23 Jan 1999 00:47:03 PST." <199901230847.AAA44590@apollo.backplane.com> Date: Sat, 23 Jan 1999 17:25:03 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > :It's definately happening still, sorry. :-( I recompiled a 100% static > :kernel and have had three more explosions, usually after starting exmh. > :(exmh takes 10 to 15MB of ram on this system due to my mailbox folder > :sizes). > : > :However, a clue.. The SMP box that is doing fine is a P6, an NFS client > :and server (loading nfs.ko, it fsck's fast, so I use that box for making > :sure the modules work). The one that is crashing, is a P5, an NFS client > :and server (static kernel), and with a MFS /tmp. Both run softupdates (up > :to date src/contrib/sys). > : > :I suspect MFS is the key. There's the new VOP_FREEBLKS() stuff you added, > :and the corresponding calls to madvise to free the pages. > : > :Given madvise()'s murky history, I can't help but feel suspicious about it. > : > :I've unmounted /tmp and am about to thrash the machine. At the > :moment, it's sitting on: Swap: 120M Total, 376K Used, 120M Free > : > :Cheers, > :-Peter > > Hmmm. It's possible. A quick look at the exmh source indicates that > it uses /tmp a lot. I've been doing make buildworld's with a 300MB > MFS /usr/obj, but those are typically nothing more then simple file > creates, reads, and writes. Presumably exmh is doing something more > sophisticated. I've since disabled MFS, compiled out a couple of other things I'm not using very often and generally cleaned things up. I've had three more panics since turning off MFS, so that wasn't it. :-( Anyway, I've just recompiled without SMP. There were some very strange things happening on the serial console again that I really do not like the look of. Console output has been disappearing and getting duplicated. > Try changing the panic in vm/vm_page.c to a printf() ( I'll do that. FWIW, this has happened while the system has been nearly quiescent all the way through to being thrashed with parallel cvs updates etc running. Most times it waits till exmh is running. Last time (when recompiling without SMP) it crashed when it came to linking the kernel (and no exmh running). I'll see if it still crashes in uniprocessor mode, if so, I'll put some debugging in and see if I can find anything out. The kernel was last built on Jan 16, and that one works fine still, so I'm pretty sure it isn't hardware. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 01:31:57 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA06159 for freebsd-current-outgoing; Sat, 23 Jan 1999 01:31:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA06154 for ; Sat, 23 Jan 1999 01:31:53 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.2/8.9.2/Netplex) with ESMTP id RAA00520; Sat, 23 Jan 1999 17:31:33 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199901230931.RAA00520@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Archie Cobbs cc: julian@whistle.com (Julian Elischer), current@FreeBSD.ORG Subject: Re: kvm question In-reply-to: Your message of "Sat, 23 Jan 1999 01:12:11 PST." <199901230912.BAA15056@bubba.whistle.com> Date: Sat, 23 Jan 1999 17:31:33 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Archie Cobbs wrote: > Julian Elischer writes: > > On Fri, 22 Jan 1999, Archie Cobbs wrote: > > > Unrelated question: SYSINIT() doesn't work from KLD modules. > > > Is this problem being addressed? > > > > you mean sysctl > > Oops, thanks.. SYSCTL() doesn't work from KLD modules but SYSINIT() does. > > -Archie Yes, this is well known. :-( The only way it's going to work is by a major rebuild of the underlying linker set based initialization mechanism. linker sets cannot be updated at module load/unload time. The present mechanism has the nice advantage that the directory tree part of the name is kept in the symbol space and only the terminal node name is an ascii string in the kernel data space. I can't think of an easy way of rebuilding sysctl without loosing that feature. About the best I can think of is some sort of gensetdefs-like tool to scan the binaries of the modules to create a descriptor for any internal sysctl tables - at minimum it needs to know where in the heirarchy it needs to be attached. kern_linker.c can then look for it and attach it to the sysctl tree, once sysctl gets updated to allow dynamic extensions like that. Cheers, -Peter -- Peter Wemm Netplex Consulting "No coffee, No workee!" :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 01:38:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA06604 for freebsd-current-outgoing; Sat, 23 Jan 1999 01:38:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from top.worldcontrol.com (snblitz.sc.scruznet.com [165.227.132.84]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA06599 for ; Sat, 23 Jan 1999 01:37:58 -0800 (PST) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 801 invoked by uid 100); 23 Jan 1999 09:37:52 -0000 Date: Sat, 23 Jan 1999 01:37:52 -0800 To: freebsd-current@FreeBSD.ORG Subject: #error "This ain't NetBSD. You lose!" Message-ID: <19990123013752.A795@top.worldcontrol.com> Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A very interesting error during last nights buildworld. In think the fix is obvious. ===> usr.bin/xlint/xlint cc -O2 -m486 -pipe -DCOMPAT_LINUX_THREADS -DVM_STACK -I/ust/src/usr.bin/xlint/xlint/../lint1 -I/usr/obj/ust/src/tmp/usr/include -c /ust/src/usr.bin/xlint/xlint/xlint.c cc -O2 -m486 -pipe -DCOMPAT_LINUX_THREADS -DVM_STACK -I/ust/src/usr.bin/xlint/xlint/../lint1 -I/usr/obj/ust/src/tmp/usr/include -c /ust/src/usr.bin/xlint/xlint/../lint1/mem.c gzip -cn /ust/src/usr.bin/xlint/xlint/lint.1 > lint.1.gz /ust/src/usr.bin/xlint/xlint/xlint.c:333: #error "This ain't NetBSD. You lose!" *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error -- Brian Litzinger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 03:10:50 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA14215 for freebsd-current-outgoing; Sat, 23 Jan 1999 03:10:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from stade.demon.co.uk (stade.demon.co.uk [158.152.29.164]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA14206 for ; Sat, 23 Jan 1999 03:10:45 -0800 (PST) (envelope-from aw1@stade.co.uk) Received: (from aw1@localhost) by stade.demon.co.uk (8.9.2/8.9.1) id KAA23929; Sat, 23 Jan 1999 10:46:30 GMT (envelope-from aw1) Date: Sat, 23 Jan 1999 10:46:30 +0000 From: Adrian Wontroba To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: Heads up! New swapper and VM changes have been committed to -4.x Message-ID: <19990123104630.A74306@titus.stade.co.uk> Reply-To: aw1@stade.co.uk References: <199901210456.UAA10191@apollo.backplane.com> <199901210855.AAA05930@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199901210855.AAA05930@apollo.backplane.com>; from Matthew Dillon on Thu, Jan 21, 1999 at 12:55:38AM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: Yes, I need some of that. X-Phone: +(44) 121 681 6677 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 21, 1999 at 12:55:38AM -0800, Matthew Dillon wrote: > One thing I haven't been able to test, because I forgot: Interleaved > swap ( more then one swap device ). I'll try to test that ASAP. I've tried, with sources cvsupped at 0600 22/11/1999 UTC. On a 128MB machine, and a make -j32 buildworld going, all seems to be running well - and possibly more responsive than the last time I tried anything other than -j4 (which was a long time ago). swapinfo output looks a little odd: Device 1K-blocks Used Avail Capacity Type /dev/da0s2b 196608 19372 177108 10% Interleaved /dev/da3b 196704 19140 177436 10% Interleaved Total 393056 393056 0 100% The totals don't appear to add up. -- Adrian Wontroba To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 04:40:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA27018 for freebsd-current-outgoing; Sat, 23 Jan 1999 04:40:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA26904 for ; Sat, 23 Jan 1999 04:39:48 -0800 (PST) (envelope-from netchild@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.2/1999010400) with ESMTP id NAA13512; Sat, 23 Jan 1999 13:38:27 +0100 (CET) Received: from wurzelausix (wurzelausix.cs.uni-sb.de [134.96.247.1]) by cs.uni-sb.de (8.9.2/1999010400) with ESMTP id NAA15562; Sat, 23 Jan 1999 13:38:26 +0100 (CET) Received: from wurzelausix.cs.uni-sb.de (IDENT:0y3sVnkwndc0Sz3O5Ienw2AMZaIOr0uB@localhost [127.0.0.1]) by wurzelausix (8.9.1/wjp/19980821) with ESMTP id NAA29562; Sat, 23 Jan 1999 13:38:22 +0100 (CET) Message-Id: <199901231238.NAA29562@wurzelausix> Date: Sat, 23 Jan 1999 13:36:53 +0100 (CET) From: Alexander Leidinger Subject: Re: readdir & cd9660 & direntp->d_type == bug (more) To: bde@zeta.org.au cc: current@FreeBSD.ORG In-Reply-To: <199901221132.WAA17787@godzilla.zeta.org.au> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22 Jan, Bruce Evans wrote: >>/cdrom: >>. (type: unknown) >>.. (type: unknown) >>autorun.inf (type: unknown) > > This is because the cd9660 file system doesn't implement d_type. man dirent or man readdir didn`t note that it`s possible to have this behavior. >>#define _POSIX_SOURCE >> >>#include >>#include >>... >> while((dent_p = readdir(dir_p))) >> { >> printf("%-40s (type: %s)\n", dent_p->d_name, types[dent_p->d_type]); >> } > > This probably shouldn't compile, since d_type isn't in POSIX.1. POSIX.1 It compiles, output above. > only guarantees d_name in struct dirent. Names beginning with d_ are > reserved for use in , but FreeBSD normally attempts to give > strict POSIX.1 if _POSIX_SOURCE is defined. So it`s a bug, but in a different way I want. :( Without _POSIX_SOURCE it didn`t work either. Is it useless, because we can only say "it works _perhaps_" (and we have to stat the entry), or is it a bug? Bye, Alexander. -- http://netchild.home.pages.de A.Leidinger @ wurzelausix.cs.uni-sb.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 04:59:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA28974 for freebsd-current-outgoing; Sat, 23 Jan 1999 04:59:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA28969 for ; Sat, 23 Jan 1999 04:59:48 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.1) with ESMTP id OAA13461 for ; Sat, 23 Jan 1999 14:59:26 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.2/8.9.2) with ESMTP id OAA66718 for ; Sat, 23 Jan 1999 14:59:24 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199901231259.OAA66718@greenpeace.grondar.za> To: current@FreeBSD.ORG Subject: PLIP code giving funny logs... Date: Sat, 23 Jan 1999 14:59:22 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I het a lot of this in my PLIP connection: Jan 23 14:44:00 gratis /kernel: X Jan 23 14:44:00 gratis /kernel: X Jan 23 14:44:01 gratis /kernel: RR Jan 23 14:44:01 gratis /kernel: RR Jan 23 14:44:02 gratis /kernel: X^RRR&RX^R Jan 23 14:44:02 gratis /kernel: X^RRR&RX^R Seems that in src/sys/dev/ppbus/if_plip.c there is #ifndef DEBUG #define DEBUG #endif Is this really necessary? What do the letters actually mean? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 07:15:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA10451 for freebsd-current-outgoing; Sat, 23 Jan 1999 07:15:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA10446 for ; Sat, 23 Jan 1999 07:15:23 -0800 (PST) (envelope-from son@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id QAA01733; Sat, 23 Jan 1999 16:15:04 +0100 (MET) Received: (from son@localhost) by teaser.fr (8.9.1/8.9.1) id QAA91604; Sat, 23 Jan 1999 16:49:09 +0100 (CET) (envelope-from son) Message-ID: <19990123164908.45330@breizh.prism.uvsq.fr> Date: Sat, 23 Jan 1999 16:49:08 +0100 From: Nicolas Souchu To: Mikhail Teterin Cc: current@FreeBSD.ORG Subject: Re: softupdates bug shows on zip drive and parallel port in NIBBLE mode References: <199901230634.BAA22200@kot.ne.mediaone.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199901230634.BAA22200@kot.ne.mediaone.net>; from Mikhail Teterin on Sat, Jan 23, 1999 at 01:34:40AM -0500 X-Operating-System: FreeBSD breizh 3.0-CURRENT FreeBSD 3.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 23, 1999 at 01:34:40AM -0500, Mikhail Teterin wrote: > >I tried both cam and bio -- no difference. It is not that it's >slow -- I was prepared for that, it is that it totally hangs -- >forever. > >I narrowed it down to softupdates. If I disable the softupdates on >the cartridge's filesystem copying finishes successfully. Somehow >the `cp' process takes 150% of the CPU time (purely single CPU system), >but that's a different story, I guess. The drive is polling-capable only. So it makes no difference with the cam/bio configuration. And it explains your performance result. > >I hope, this sad experience of mine will help further improve >softupdates. Thanks. -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 07:15:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA10471 for freebsd-current-outgoing; Sat, 23 Jan 1999 07:15:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA10466 for ; Sat, 23 Jan 1999 07:15:27 -0800 (PST) (envelope-from son@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id QAA07891; Sat, 23 Jan 1999 16:15:09 +0100 (MET) Received: (from son@localhost) by teaser.fr (8.9.1/8.9.1) id QAA89015; Sat, 23 Jan 1999 16:43:36 +0100 (CET) (envelope-from son) Message-ID: <19990123164335.07944@breizh.prism.uvsq.fr> Date: Sat, 23 Jan 1999 16:43:35 +0100 From: Nicolas Souchu To: Mark Murray Cc: current@FreeBSD.ORG Subject: Re: PLIP code giving funny logs... References: <199901231259.OAA66718@greenpeace.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199901231259.OAA66718@greenpeace.grondar.za>; from Mark Murray on Sat, Jan 23, 1999 at 02:59:22PM +0200 X-Operating-System: FreeBSD breizh 3.0-CURRENT FreeBSD 3.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 23, 1999 at 02:59:22PM +0200, Mark Murray wrote: > >Hi > >I het a lot of this in my PLIP connection: > >Jan 23 14:44:00 gratis /kernel: X >Jan 23 14:44:00 gratis /kernel: X >Jan 23 14:44:01 gratis /kernel: RR >Jan 23 14:44:01 gratis /kernel: RR >Jan 23 14:44:02 gratis /kernel: X^RRR&RX^R >Jan 23 14:44:02 gratis /kernel: X^RRR&RX^R > >Seems that in src/sys/dev/ppbus/if_plip.c there is > >#ifndef DEBUG >#define DEBUG >#endif > >Is this really necessary? What do the letters actually mean? An error occured, timeout, incorrect handshake.. It was intended to catch potential problems of the plip driver. I should remove it now. Thanks for your note. > >M >-- >Mark Murray >Join the anti-SPAM movement: http://www.cauce.org > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > Nicholas. -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 07:26:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA11796 for freebsd-current-outgoing; Sat, 23 Jan 1999 07:26:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.128.29.136]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA11785 for ; Sat, 23 Jan 1999 07:26:12 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: (from mi@localhost) by kot.ne.mediaone.net (8.9.1a/8.9.1) id KAA02876; Sat, 23 Jan 1999 10:25:16 -0500 (EST) From: Mikhail Teterin Message-Id: <199901231525.KAA02876@kot.ne.mediaone.net> Subject: Re: softupdates bug shows on zip drive and parallel port in NIBBLE mode In-Reply-To: <19990123164908.45330@breizh.prism.uvsq.fr> from Nicolas Souchu at "Jan 23, 1999 04:49:08 pm" To: nsouch@teaser.fr (Nicolas Souchu) Date: Sat, 23 Jan 1999 10:25:16 -0500 (EST) Cc: current@FreeBSD.ORG X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"I tried both cam and bio -- no difference. It is not that it's =>slow -- I was prepared for that, it is that it totally hangs -- =>forever. => =>I narrowed it down to softupdates. If I disable the softupdates on =>the cartridge's filesystem copying finishes successfully. Somehow =>the `cp' process takes 150% of the CPU time (purely single CPU system), =>but that's a different story, I guess. =The drive is polling-capable only. So it makes no difference with the =cam/bio configuration. And it explains your performance result. I figured that. I only wonder if the driver can be made to poll less often -- yielding to others. But it works reliably now that I do not use SoftUpdates on it. Thanks! -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 07:43:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA13379 for freebsd-current-outgoing; Sat, 23 Jan 1999 07:43:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.mn.mediaone.net (h-182-40.mn.mediaone.net [209.32.182.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA13374 for ; Sat, 23 Jan 1999 07:43:27 -0800 (PST) (envelope-from veldy@visi.com) Received: from visi.com (localhost.mn.mediaone.net [127.0.0.1]) by rover.mn.mediaone.net (8.9.1/8.9.1) with ESMTP id JAA90562; Sat, 23 Jan 1999 09:44:00 -0600 (CST) (envelope-from veldy@visi.com) Message-ID: <36A9EE3F.FC4BFF86@visi.com> Date: Sat, 23 Jan 1999 09:44:00 -0600 From: "Thomas T. Veldhouse" X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Mark Murray , freebsd-current@FreeBSD.ORG Subject: Re: world broken References: <199901230807.KAA36520@greenpeace.grondar.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has this been done yet? It has been over 7 hours since the post and I have only seen two source changes, and they are in sys/pci by "roger". Tom Veldhouse veldy@visi.com Mark Murray wrote: > Julian Elischer wrote: > > can you announce when the fixes are in place? > > I'll do better; I am about to back it all out. > > M > -- > Mark Murray > Join the anti-SPAM movement: http://www.cauce.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 07:49:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA13748 for freebsd-current-outgoing; Sat, 23 Jan 1999 07:49:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.mn.mediaone.net (h-182-40.mn.mediaone.net [209.32.182.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA13743 for ; Sat, 23 Jan 1999 07:49:45 -0800 (PST) (envelope-from veldy@visi.com) Received: from visi.com (localhost.mn.mediaone.net [127.0.0.1]) by rover.mn.mediaone.net (8.9.1/8.9.1) with ESMTP id JAA90578 for ; Sat, 23 Jan 1999 09:50:34 -0600 (CST) (envelope-from veldy@visi.com) Message-ID: <36A9EFCA.B1820679@visi.com> Date: Sat, 23 Jan 1999 09:50:34 -0600 From: "Thomas T. Veldhouse" X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Re: world broken References: <199901230807.KAA36520@greenpeace.grondar.za> <36A9EE3F.FC4BFF86@visi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Never mind, I was using the RELENG_3 tag during CVSup. Sorry. "Thomas T. Veldhouse" wrote: > Has this been done yet? It has been over 7 hours since the post and I > have only seen two source changes, and they are in sys/pci by "roger". > > Tom Veldhouse > veldy@visi.com > > Mark Murray wrote: > > > Julian Elischer wrote: > > > can you announce when the fixes are in place? > > > > I'll do better; I am about to back it all out. > > > > M > > -- > > Mark Murray > > Join the anti-SPAM movement: http://www.cauce.org > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 07:56:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA14718 for freebsd-current-outgoing; Sat, 23 Jan 1999 07:56:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA14701 for ; Sat, 23 Jan 1999 07:56:23 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id PAA71747 for ; Sat, 23 Jan 1999 15:57:35 GMT Date: Sat, 23 Jan 1999 15:57:35 +0000 (GMT) From: Doug Rabson To: current@FreeBSD.ORG Subject: Device Framework Overview Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just posted a brief overview of the new device system in FreeBSD at http://www.freebsd.org/~dfr/devices.html. The information content is fairly small but it might help someone who is trying to understand the source code. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 08:11:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16216 for freebsd-current-outgoing; Sat, 23 Jan 1999 08:11:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA16210 for ; Sat, 23 Jan 1999 08:11:09 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.1) with ESMTP id SAA13753; Sat, 23 Jan 1999 18:10:54 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.2/8.9.2) with ESMTP id SAA54736; Sat, 23 Jan 1999 18:10:47 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199901231610.SAA54736@greenpeace.grondar.za> To: "Thomas T. Veldhouse" cc: freebsd-current@FreeBSD.ORG Subject: Re: world broken In-Reply-To: Your message of " Sat, 23 Jan 1999 09:44:00 CST." <36A9EE3F.FC4BFF86@visi.com> References: <199901230807.KAA36520@greenpeace.grondar.za> <36A9EE3F.FC4BFF86@visi.com> Date: Sat, 23 Jan 1999 18:10:44 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Thomas T. Veldhouse" wrote: > Has this been done yet? It has been over 7 hours since the post and I > have only seen two source changes, and they are in sys/pci by "roger". Hours ago :-). M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 08:49:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA20107 for freebsd-current-outgoing; Sat, 23 Jan 1999 08:49:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from darkstar.psa.at (darkstar.psa.at [194.152.163.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA20100 for ; Sat, 23 Jan 1999 08:49:51 -0800 (PST) (envelope-from entropy@compufit.at) Received: from unet3-203.univie.ac.at ([131.130.232.203] helo=entropy.quake.at) by darkstar.psa.at with esmtp (Exim 2.05 #1) id 1046Pl-0000zn-00 for current@freebsd.org; Sat, 23 Jan 1999 18:00:05 +0100 Received: from localhost ([127.0.0.1]) by entropy.quake.at with esmtp (Exim 2.05 #1) id 1046DO-000NkU-00 for current@freebsd.org; Sat, 23 Jan 1999 17:47:18 +0100 Date: Sat, 23 Jan 1999 17:47:18 +0100 (CET) From: Alexander Sanda X-Sender: root@darkstar.vmx To: current@FreeBSD.ORG Subject: -current (aka 4.x) breaks libtool Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi This isn't exactly topic here, but it might be useful as a little hint or warning... Even most recent versions of libtool (1.2e imho) fail to check for freebsd4* (as expected). As a result, they set can_build_shared to "no" which disables building of shared libraries. This affects most major projects like kde or gnome and can result in major abuse of disk- and memory space :) (some kde or gnome binaries tend to get *very* large when linked statically). Workarounds ? I'am currently using --host=i386-unknown-freebsd3 as a possible workaround, another way might be a small modification of ltconfig. Sorry, if this has been already mentioned... -- # /AS/ http://privat.schlund.de/entropy/ # # # # If Jesus was never born, we would not have a Y2K problem. # To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 08:52:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA20543 for freebsd-current-outgoing; Sat, 23 Jan 1999 08:52:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from callisto.geotec.net (callisto.geotec.net [208.244.246.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA20531 for ; Sat, 23 Jan 1999 08:52:04 -0800 (PST) (envelope-from tom@geotec.net) Received: from TOJ.org ([208.244.247.91]) by callisto.geotec.net (Post.Office MTA v3.5.3 release 223 ID# 0-58476U5000L500S0V35) with ESMTP id net; Sat, 23 Jan 1999 11:01:08 -0600 Received: (from tom@localhost) by TOJ.org (8.9.2/8.9.1) id KAA05796; Sat, 23 Jan 1999 10:32:45 -0600 (CST) (envelope-from tom) Date: Sat, 23 Jan 1999 10:32:08 -0600 From: tom@geotec.net (Tom Jackson) To: Victor Salaman Cc: "'freebsd-current@freebsd.org'" Subject: Re: Make world dies on 3.0 STABLE Message-ID: <19990123103208.A5770@peeper.TOJ.org> References: <608F4F76C94DD211B93100805F29063A8D35@teknos.teknos.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <608F4F76C94DD211B93100805F29063A8D35@teknos.teknos.com>; from Victor Salaman on Thu, Jan 21, 1999 at 07:41:20AM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 21, 1999 at 07:41:20AM -0400, Victor Salaman wrote: > I just csvup'ed the sources...(I had the sources from January 12's > snapshot). While trying to do a "make world", eventually I get this message. > > c++ -pg -I/usr/obj/usr/src/tmp/usr/include/g++ -nostdinc -O -pipe > -I/usr/src/gnu [snipped] > Stop. > *** Error code 1 > > Stop. > > > > > and then dies! > What's your migration path? I went from 3.0-current to 3.0-release and then to 3.0-stable successfully. I have noticed that 'ppp -auto -alias demand' no longer works for me, however. Anybody else experiencing this gremlin? -- Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 08:59:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA21857 for freebsd-current-outgoing; Sat, 23 Jan 1999 08:59:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles301.castles.com [208.214.167.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA21847 for ; Sat, 23 Jan 1999 08:59:31 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id IAA00613; Sat, 23 Jan 1999 08:55:54 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901231655.IAA00613@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Archie Cobbs cc: current@FreeBSD.ORG Subject: Re: kvm question In-reply-to: Your message of "Fri, 22 Jan 1999 23:48:50 PST." <199901230748.XAA14754@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 23 Jan 1999 08:55:53 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I ran into an interesting problem in the process of modifying > "netstat" to understand the PF_NETGRAPH protocol family. "netstat" > uses kvm_read(), etc. to read kernel symbols. However, this doesn't > work when the symbols you're looking for are in an KLD module (eg, > ng_socket.ko) -- the symbol will not be found. > > So I added some code/hackery to look for any loaded modules and if > on named "ng_socket.ko" was found, try finding the symbol in there. > > My question is, should kvm_read() and friends be "enhanced" with > this ability to find a symbol by searching through the loaded > KLD modules? Seems a bit hackish, but then again so is the whole > kvm() idea. No; you should be using sysctl to get at the information. > I'd be willing to add this code if so.. it's not much. > > Unrelated question: SYSINIT() doesn't work from KLD modules. > Is this problem being addressed? It does; it's critical to the functioning of KLD modules in general. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 09:02:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22405 for freebsd-current-outgoing; Sat, 23 Jan 1999 09:02:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles301.castles.com [208.214.167.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22399 for ; Sat, 23 Jan 1999 09:02:19 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id IAA00639; Sat, 23 Jan 1999 08:58:42 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901231658.IAA00639@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Archie Cobbs cc: julian@whistle.com (Julian Elischer), current@FreeBSD.ORG Subject: Re: kvm question In-reply-to: Your message of "Sat, 23 Jan 1999 01:12:11 PST." <199901230912.BAA15056@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 23 Jan 1999 08:58:41 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Julian Elischer writes: > > On Fri, 22 Jan 1999, Archie Cobbs wrote: > > > Unrelated question: SYSINIT() doesn't work from KLD modules. > > > Is this problem being addressed? > > > > you mean sysctl > > Oops, thanks.. SYSCTL() doesn't work from KLD modules but SYSINIT() does. What I get for being too fast. 8) Yes, there's a desire to see this fixed; it requires a significant rewrite of the sysctl stuff unfortunately. Mark Murray was working on this but probably as a 4.x feature; if you have something simpler you feel up to contributing in the short term you'd be very popular. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 09:33:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA25822 for freebsd-current-outgoing; Sat, 23 Jan 1999 09:33:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA25811 for ; Sat, 23 Jan 1999 09:33:41 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id RAA72214; Sat, 23 Jan 1999 17:34:23 GMT Date: Sat, 23 Jan 1999 17:34:23 +0000 (GMT) From: Doug Rabson To: Peter Wemm cc: Matthew Dillon , current@FreeBSD.ORG Subject: Re: panic: found dirty cache page 0xf046f1c0 In-Reply-To: <199901230925.RAA00489@spinner.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 23 Jan 1999, Peter Wemm wrote: > Matthew Dillon wrote: > > :It's definately happening still, sorry. :-( I recompiled a 100% static > > :kernel and have had three more explosions, usually after starting exmh. > > :(exmh takes 10 to 15MB of ram on this system due to my mailbox folder > > :sizes). > > : > > :However, a clue.. The SMP box that is doing fine is a P6, an NFS client > > :and server (loading nfs.ko, it fsck's fast, so I use that box for making > > :sure the modules work). The one that is crashing, is a P5, an NFS client > > :and server (static kernel), and with a MFS /tmp. Both run softupdates (up > > :to date src/contrib/sys). > > : > > :I suspect MFS is the key. There's the new VOP_FREEBLKS() stuff you added, > > :and the corresponding calls to madvise to free the pages. > > : > > :Given madvise()'s murky history, I can't help but feel suspicious about it. > > : > > :I've unmounted /tmp and am about to thrash the machine. At the > > :moment, it's sitting on: Swap: 120M Total, 376K Used, 120M Free > > : > > :Cheers, > > :-Peter > > > > Hmmm. It's possible. A quick look at the exmh source indicates that > > it uses /tmp a lot. I've been doing make buildworld's with a 300MB > > MFS /usr/obj, but those are typically nothing more then simple file > > creates, reads, and writes. Presumably exmh is doing something more > > sophisticated. > > I've since disabled MFS, compiled out a couple of other things I'm not > using very often and generally cleaned things up. I've had three more > panics since turning off MFS, so that wasn't it. :-( > > Anyway, I've just recompiled without SMP. There were some very strange > things happening on the serial console again that I really do not like the > look of. Console output has been disappearing and getting duplicated. > > > Try changing the panic in vm/vm_page.c to a printf() ( > > I'll do that. > > FWIW, this has happened while the system has been nearly quiescent all the > way through to being thrashed with parallel cvs updates etc running. Most > times it waits till exmh is running. Last time (when recompiling without > SMP) it crashed when it came to linking the kernel (and no exmh running). > > I'll see if it still crashes in uniprocessor mode, if so, I'll put some > debugging in and see if I can find anything out. The kernel was last > built on Jan 16, and that one works fine still, so I'm pretty sure it > isn't hardware. I just had one of these on one of my alphas. The machine is UP (obviously), no MFS, no dynamically loaded stuff. It was doing an installworld with NFSv3 mounted source, local obj. All filesystems were using softupdates. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 09:47:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA26911 for freebsd-current-outgoing; Sat, 23 Jan 1999 09:47:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA26903 for ; Sat, 23 Jan 1999 09:47:43 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id RAA72286; Sat, 23 Jan 1999 17:48:46 GMT Date: Sat, 23 Jan 1999 17:48:46 +0000 (GMT) From: Doug Rabson To: Peter Wemm cc: Matthew Dillon , current@FreeBSD.ORG Subject: Re: panic: found dirty cache page 0xf046f1c0 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 23 Jan 1999, Doug Rabson wrote: > I just had one of these on one of my alphas. The machine is UP > (obviously), no MFS, no dynamically loaded stuff. It was doing an > installworld with NFSv3 mounted source, local obj. All filesystems were > using softupdates. I made it happen again by doing the same installworld but this time I caught it in the debugger. I'll leave the machine up for a while in case someone has some idea of how to debug it. The stacktrace looks like this: #0 Debugger () at ../../alpha/alpha/db_interface.c:260 #1 0xfffffc000036c2c0 in panic () at ../../kern/kern_shutdown.c:444 #2 0xfffffc00004942fc in vm_page_alloc () at ../../vm/vm_page.c:1041 #3 0xfffffc00003a1b54 in allocbuf () at ../../kern/vfs_bio.c:1791 #4 0xfffffc00003a13d4 in getblk () at ../../kern/vfs_bio.c:1572 #5 0xfffffc000046a150 in ffs_balloc () at ../../ufs/ffs/ffs_balloc.c:170 #6 0xfffffc00004772dc in ffs_write () at vnode_if.h:1015 #7 0xfffffc00003b3c00 in vn_write () at vnode_if.h:331 #8 0xfffffc000037f72c in write () at ../../kern/sys_generic.c:270 #9 0xfffffc00004b0a4c in syscall () at ../../alpha/alpha/trap.c:620 #10 0xfffffc00004a416c in XentSys () at ../../alpha/alpha/exception.s:127 -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 10:11:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28782 for freebsd-current-outgoing; Sat, 23 Jan 1999 10:11:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28774 for ; Sat, 23 Jan 1999 10:11:03 -0800 (PST) (envelope-from randy@psg.com) Received: from localhost (1133 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Sat, 23 Jan 1999 10:10:53 -0800 (PST) (Smail-3.2.0.101 1997-Dec-17 #1 built 1998-Oct-13) Message-Id: Date: Sat, 23 Jan 1999 10:10:53 -0800 (PST) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-current@FreeBSD.ORG Subject: make aout-to-elf-bbuild failure Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -current as of early this morning % make aout-to-elf-bbuild ... cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 pccard/*.h /usr/obj/aout/usr/src/tmp/usr/include/pccard cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 posix4/*.h /usr/obj/aout/usr/src/tmp/usr/include/posix4 cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 sys/*.h /usr/obj/aout/usr/src/tmp/usr/include/sys cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 vm/*.h /usr/obj/aout/usr/src/tmp/usr/include/vm cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 isofs/cd9660/*.h /usr/obj/aout/usr/src/tmp/usr/include/isofs/cd9660 cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 ufs/ffs/*.h /usr/obj/aout/usr/src/tmp/usr/include/ufs/ffs install: ufs/ffs/ffs_softdep.h: No such file or directory *** Error code 71 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 11:05:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA03550 for freebsd-current-outgoing; Sat, 23 Jan 1999 11:05:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA03545 for ; Sat, 23 Jan 1999 11:05:18 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id LAA21931; Sat, 23 Jan 1999 11:04:28 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma021929; Sat, 23 Jan 99 11:04:15 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id LAA18363; Sat, 23 Jan 1999 11:04:15 -0800 (PST) From: Archie Cobbs Message-Id: <199901231904.LAA18363@bubba.whistle.com> Subject: Re: kvm question In-Reply-To: <199901231658.IAA00639@dingo.cdrom.com> from Mike Smith at "Jan 23, 99 08:58:41 am" To: mike@smith.net.au (Mike Smith) Date: Sat, 23 Jan 1999 11:04:15 -0800 (PST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: > Yes, there's a desire to see this fixed; it requires a significant > rewrite of the sysctl stuff unfortunately. Mark Murray was working on > this but probably as a 4.x feature; if you have something simpler you > feel up to contributing in the short term you'd be very popular. Peter pointed out that having the sysctl's as symbols was a nice advantage of the current system. How important is this? If we were willing to give this up, then the SYSCTL() macro could just expand to a SYSINIT() that called sysctl_add_subtree() (or whatever you want to call it) upon loading. This sysctl_add_subtree() would maintain the sysctl tree... it would allow new subtrees and nodes to be added when new KLD's were loaded. It could also subtree support removal when the KLD goes away. Seems pretty straightforward, but I'm probably missing something. I don't think any user-land programs would have to change. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 11:07:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA03933 for freebsd-current-outgoing; Sat, 23 Jan 1999 11:07:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA03923 for ; Sat, 23 Jan 1999 11:07:01 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id LAA48145; Sat, 23 Jan 1999 11:06:43 -0800 (PST) (envelope-from dillon) Date: Sat, 23 Jan 1999 11:06:43 -0800 (PST) From: Matthew Dillon Message-Id: <199901231906.LAA48145@apollo.backplane.com> To: Doug Rabson Cc: Peter Wemm , current@FreeBSD.ORG Subject: Re: panic: found dirty cache page 0xf046f1c0 References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I made it happen again by doing the same installworld but this time I :caught it in the debugger. I'll leave the machine up for a while in case :someone has some idea of how to debug it. The stacktrace looks like this: : :#0 Debugger () at ../../alpha/alpha/db_interface.c:260 :#1 0xfffffc000036c2c0 in panic () at ../../kern/kern_shutdown.c:444 :#2 0xfffffc00004942fc in vm_page_alloc () at ../../vm/vm_page.c:1041 :#3 0xfffffc00003a1b54 in allocbuf () at ../../kern/vfs_bio.c:1791 The panic message should be printing the address of the vm_page_t that it caught. From the debugger, dump that vm_page_t with 'print'. print *0xADDRESS Do about 8 print's bumping the address by 4 ( in hex ) for each. It would be even better if we could figure out the contents and type of the underlying object. -Matt Matthew Dillon :-- :Doug Rabson Mail: dfr@nlsystems.com :Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 11:07:57 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA04070 for freebsd-current-outgoing; Sat, 23 Jan 1999 11:07:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA04046 for ; Sat, 23 Jan 1999 11:07:52 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id LAA04595; Sat, 23 Jan 1999 11:07:40 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id LAA16027; Sat, 23 Jan 1999 11:07:40 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sat, 23 Jan 1999 11:07:40 -0800 (PST) Message-Id: <199901231907.LAA16027@vashon.polstra.com> To: randy@psg.com Subject: Re: make aout-to-elf-bbuild failure Newsgroups: polstra.freebsd.current In-Reply-To: Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Randy Bush wrote: > -current as of early this morning > > % make aout-to-elf-bbuild ... > cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 ufs/ffs/*.h /usr/obj/aout/usr/src/tmp/usr/include/ufs/ffs > install: ufs/ffs/ffs_softdep.h: No such file or directory > *** Error code 71 Judging from these messages, I'd guess that you have a symbolic link "/usr/src/sys/ufs/ffs/ffs_softdep.h" that points to a non-existent file. Delete it. The correct link names are "ffs_softdep.c" and "softdep.h". John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 11:13:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA04704 for freebsd-current-outgoing; Sat, 23 Jan 1999 11:13:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA04697 for ; Sat, 23 Jan 1999 11:13:20 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id TAA72540; Sat, 23 Jan 1999 19:13:27 GMT Date: Sat, 23 Jan 1999 19:13:27 +0000 (GMT) From: Doug Rabson To: Matthew Dillon cc: Peter Wemm , current@FreeBSD.ORG Subject: Re: panic: found dirty cache page 0xf046f1c0 In-Reply-To: <199901231906.LAA48145@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 23 Jan 1999, Matthew Dillon wrote: > > :I made it happen again by doing the same installworld but this time I > :caught it in the debugger. I'll leave the machine up for a while in case > :someone has some idea of how to debug it. The stacktrace looks like this: > : > :#0 Debugger () at ../../alpha/alpha/db_interface.c:260 > :#1 0xfffffc000036c2c0 in panic () at ../../kern/kern_shutdown.c:444 > :#2 0xfffffc00004942fc in vm_page_alloc () at ../../vm/vm_page.c:1041 > :#3 0xfffffc00003a1b54 in allocbuf () at ../../kern/vfs_bio.c:1791 > > The panic message should be printing the address of the vm_page_t that > it caught. > > From the debugger, dump that vm_page_t with 'print'. > > print *0xADDRESS > > Do about 8 print's bumping the address by 4 ( in hex ) for each. > > It would be even better if we could figure out the contents and type > of the underlying object. I have full symbols: (gdb) fr 2 #2 0xfffffc00004942fc in vm_page_alloc () at ../../vm/vm_page.c:1041 1041 panic("found dirty cache page %p", m); (gdb) l 1036 */ 1037 1038 if (qtype == PQ_CACHE) { 1039 #if !defined(MAX_PERF) 1040 if (m->dirty) 1041 panic("found dirty cache page %p", m); 1042 1043 #endif 1044 vm_page_busy(m); 1045 vm_page_protect(m, VM_PROT_NONE); (gdb) p m $4 = (struct vm_page *) 0xfffffe0000108f40 (gdb) p *m $5 = {pageq = {tqe_next = 0x0, tqe_prev = 0xfffffc000052ecc8}, hnext = 0x0, listq = {tqe_next = 0xfffffe0000090fe0, tqe_prev = 0xfffffe00000bb6b8}, object = 0xfffffe00050e2a10, pindex = 12, phys_addr = 88940544, queue = 172, flags = 128, pc = 41, wire_count = 0, hold_count = 0, act_count = 5 '\005', busy = 0 '\000', valid = 65535, dirty = 65535} -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 11:23:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05667 for freebsd-current-outgoing; Sat, 23 Jan 1999 11:23:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05662 for ; Sat, 23 Jan 1999 11:23:16 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id LAA22119; Sat, 23 Jan 1999 11:22:29 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma022115; Sat, 23 Jan 99 11:22:20 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id LAA18494; Sat, 23 Jan 1999 11:22:20 -0800 (PST) From: Archie Cobbs Message-Id: <199901231922.LAA18494@bubba.whistle.com> Subject: Re: kvm question In-Reply-To: <199901231655.IAA00613@dingo.cdrom.com> from Mike Smith at "Jan 23, 99 08:55:53 am" To: mike@smith.net.au (Mike Smith) Date: Sat, 23 Jan 1999 11:22:20 -0800 (PST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: > > My question is, should kvm_read() and friends be "enhanced" with > > this ability to find a symbol by searching through the loaded > > KLD modules? Seems a bit hackish, but then again so is the whole > > kvm() idea. > > No; you should be using sysctl to get at the information. Yes in *one particular application* using sysctl would be better.. but that's not the question. The question is, should this bug in libkvm be fixed? Until and unless someone is willing to convert every program that uses libkvm to use sysctl or procfs or whatever, I think this is a fair question. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 11:27:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06428 for freebsd-current-outgoing; Sat, 23 Jan 1999 11:27:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from jumping-spider.aracnet.com (jumping-spider.aracnet.com [205.159.88.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA06423 for ; Sat, 23 Jan 1999 11:27:54 -0800 (PST) (envelope-from beattie@aracnet.com) Received: from shell2.aracnet.com (IDENT:1728@shell2.aracnet.com [205.159.88.20]) by jumping-spider.aracnet.com (8.9.1/8.9.0) with ESMTP id LAA26258 for ; Sat, 23 Jan 1999 11:27:43 -0800 Received: from localhost by shell2.aracnet.com (8.8.7) id LAA22566; Sat, 23 Jan 1999 11:27:43 -0800 Date: Sat, 23 Jan 1999 11:27:43 -0800 (PST) From: Brian Beattie To: current@FreeBSD.ORG Subject: aic driver status Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For everybody who has been waiting for me finish the aic driver I thought I should give a status report. My move is mostly complete and I am trying to get back to working in the aic driver. Unfortunately I have run into hardware problems. Having just bought a house I can not afford to run out and buy all new hardware. I am currently trying to diagnose the problem, (it could be one or more of: controller, cpu, memory, motherboard). While I would still like to do the driver myself, if there is anybody out there who is itching to work on it themselves you might get in touch with me. Brian Beattie | The only problem with beattie@aracnet.com | winning the rat race ... www.aracnet.com/~beattie | in the end you're still a rat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 11:29:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06528 for freebsd-current-outgoing; Sat, 23 Jan 1999 11:29:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA06515 for ; Sat, 23 Jan 1999 11:29:02 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.2/8.9.2/Netplex) with ESMTP id DAA00732; Sun, 24 Jan 1999 03:28:28 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199901231928.DAA00732@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Doug Rabson cc: Matthew Dillon , current@FreeBSD.ORG Subject: Re: panic: found dirty cache page 0xf046f1c0 In-reply-to: Your message of "Sat, 23 Jan 1999 19:13:27 GMT." Date: Sun, 24 Jan 1999 03:28:27 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson wrote: > On Sat, 23 Jan 1999, Matthew Dillon wrote: > > > > > :I made it happen again by doing the same installworld but this time I > > :caught it in the debugger. I'll leave the machine up for a while in case > > :someone has some idea of how to debug it. The stacktrace looks like this: > > : > > :#0 Debugger () at ../../alpha/alpha/db_interface.c:260 > > :#1 0xfffffc000036c2c0 in panic () at ../../kern/kern_shutdown.c:444 > > :#2 0xfffffc00004942fc in vm_page_alloc () at ../../vm/vm_page.c:1041 > > :#3 0xfffffc00003a1b54 in allocbuf () at ../../kern/vfs_bio.c:1791 > > > > The panic message should be printing the address of the vm_page_t that > > it caught. > > > > From the debugger, dump that vm_page_t with 'print'. > > > > print *0xADDRESS > > > > Do about 8 print's bumping the address by 4 ( in hex ) for each. > > > > It would be even better if we could figure out the contents and type > > of the underlying object. > > I have full symbols: > > (gdb) fr 2 > #2 0xfffffc00004942fc in vm_page_alloc () at ../../vm/vm_page.c:1041 > 1041 panic("found dirty cache page %p", m); > (gdb) l > 1036 */ > 1037 > 1038 if (qtype == PQ_CACHE) { > 1039 #if !defined(MAX_PERF) > 1040 if (m->dirty) > 1041 panic("found dirty cache page %p", m); > 1042 > 1043 #endif > 1044 vm_page_busy(m); > 1045 vm_page_protect(m, VM_PROT_NONE); > (gdb) p m > $4 = (struct vm_page *) 0xfffffe0000108f40 > (gdb) p *m > $5 = {pageq = {tqe_next = 0x0, tqe_prev = 0xfffffc000052ecc8}, hnext = 0x0, > listq = {tqe_next = 0xfffffe0000090fe0, tqe_prev = 0xfffffe00000bb6b8}, > object = 0xfffffe00050e2a10, pindex = 12, phys_addr = 88940544, queue = 172 , > flags = 128, pc = 41, wire_count = 0, hold_count = 0, act_count = 5 '\005', > busy = 0 '\000', valid = 65535, dirty = 65535} > -- Doug, Matt wanted some things from m->object too.. If it's still there can you grab it? printf( "found dirty cache page %p (%p,%d,%x) obtype %d obflags %x", m, m->object, (int)m->pindex, (int)m->flags, (int)m->object->type, (int)m->object->flags ); BTW; in vm_map.c: /* * vm_map_clean * * Push any dirty cached pages in the address range to their pager. * If syncio is TRUE, dirty pages are written synchronously. * If invalidate is TRUE, any cached pages are freed as well. * * Returns an error if any part of the specified range is not mapped. */ This kinda suggests that dirty cached pages might not be all that unusual.. but the code in question seems to be working at a different level. Cheers, -Peter -- Peter Wemm Netplex Consulting "No coffee, No workee!" :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 11:42:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07824 for freebsd-current-outgoing; Sat, 23 Jan 1999 11:42:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cantor.boolean.net (cantor.boolean.net [209.133.111.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07819 for ; Sat, 23 Jan 1999 11:42:26 -0800 (PST) (envelope-from Kurt@OpenLDAP.Org) Received: from OpenLDAP.Org (localhost [127.0.0.1]) by cantor.boolean.net (8.9.1/8.9.1) with ESMTP id TAA40914; Sat, 23 Jan 1999 19:48:50 GMT (envelope-from Kurt@OpenLDAP.Org) Message-ID: <36AA2580.53EE5AAD@OpenLDAP.Org> Date: Sat, 23 Jan 1999 11:39:44 -0800 From: "Kurt D. Zeilenga" Organization: OpenLDAP X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en-GB,en-US,en,de-DE,de MIME-Version: 1.0 To: Alexander Sanda CC: current@FreeBSD.ORG Subject: Re: -current (aka 4.x) breaks libtool Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 05:47 PM 1/23/99 +0100, Alexander Sanda wrote: >Even most recent versions of libtool (1.2e imho) fail to check for >freebsd4* (as expected). As a result, they set can_build_shared to "no" >which disables building of shared libraries. Here is a simple patch (which I'll forward this to the libtool maintainers). I've just applied the following to the OpenLDAP copy of ltconfig. It should work for FreeBSD 4.0 and beyond... Index: ltconfig =================================================================== RCS file: /repo/OpenLDAP/pkg/ldap/build/ltconfig,v retrieving revision 1.4 diff -u -r1.4 ltconfig --- ltconfig 1998/12/21 22:08:06 1.4 +++ ltconfig 1999/01/23 19:38:42 @@ -776,8 +776,13 @@ hardcode_shlibpath_var=no ;; - # FreeBSD 3, at last, uses gcc -shared to do shared libraries. - freebsd3*) + freebsd1*) + ld_shlibs=no + can_build_shared=no + ;; + + # FreeBSD 3 and greater uses gcc -shared to do shared libraries. + freebsd* ) archive_cmds='$CC -shared -o $lib$libobjs' hardcode_libdir_flag_spec='-R$libdir' hardcode_direct=yes @@ -1129,8 +1134,12 @@ finish_cmds='PATH="$PATH:/sbin" ldconfig -m $libdir' shlibpath_var=LD_LIBRARY_PATH ;; + +freebsd1*) + dynamic_linker=no + ;; -freebsd3*) +freebsd*) version_type=freebsd library_names_spec='${libname}${release}.so.$versuffix $libname.so' if [ -x `/usr/bin/objformat` ]; then To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 11:43:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08102 for freebsd-current-outgoing; Sat, 23 Jan 1999 11:43:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA08093 for ; Sat, 23 Jan 1999 11:43:27 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.2/8.9.2/Netplex) with ESMTP id DAA00782; Sun, 24 Jan 1999 03:43:04 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199901231943.DAA00782@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon , current@FreeBSD.ORG Subject: Re: panic: found dirty cache page 0xf046f1c0 In-reply-to: Your message of "Sat, 23 Jan 1999 17:25:03 +0800." <199901230925.RAA00489@spinner.netplex.com.au> Date: Sun, 24 Jan 1999 03:43:03 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: > Matthew Dillon wrote: [..] > > Try changing the panic in vm/vm_page.c to a printf() ( > > I'll do that. BTW; what are the dangers of this? lost disk writes or corruption? Can we (as a workaround) push the page that we found back onto a dirty queue and try again after some diagnostics? > FWIW, this has happened while the system has been nearly quiescent all the > way through to being thrashed with parallel cvs updates etc running. Most > times it waits till exmh is running. Last time (when recompiling without > SMP) it crashed when it came to linking the kernel (and no exmh running). > > I'll see if it still crashes in uniprocessor mode, if so, I'll put some > debugging in and see if I can find anything out. The kernel was last > built on Jan 16, and that one works fine still, so I'm pretty sure it > isn't hardware. It crashed in uniprocessor mode about 60 seconds after sending this mail. It's got a really trimmed down kernel config and no modules loaded or in use. I have not disabled softupdates yet, that's next. This particular machine won't reboot by itself after it's been running in SMP mode (it's really old), so I have to manually reset it. I went to sleep straight after that, and it ran the whole time I was asleep. After getting up again, I started exmh, and it crashed 30 seconds later. There was no swapping in progress, I have been tunning top -s1 to see what the swap and memory state is when it dies. Unfortunately I lost the last one, but it generally looks like this: last pid: 6293; load averages: 0.51, 0.52, 0.65 up 0+01:40:54 14:19:06 40 processes: 1 running, 39 sleeping CPU states: 4.6% user, 0.0% nice, 11.8% system, 1.5% interrupt, 82.1% idle Mem: 19M Active, 9236K Inact, 13M Wired, 3068K Cache, 4691K Buf, 508K Free Swap: 120M Total, 128K Used, 120M Free This machine has 48M of ram, one swap partition only. Oh, one other thing that occurred to me.. Under 4.0-current, I regularly (ie: within 30 seconds of boot) get if_de tranmitter underflows. My console corruption was happening at the instant that de0 was being configured with ifconfig. exmh is running to a remote display over that de0 interface. Under Jan 16 3.0-current, I do not get that tranmitter underflow.. The only thin I can think of about if_de that's unusual that is VM related (apart from the complexity of the code) is that it uses configmalloc(). I wonder if this is somehow setting the scene for the later failures? It's certainly suspicious that has done strange things when being ifconfig'ed, including things like trashing the serial console on no less than a dozen occasions. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 11:44:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08215 for freebsd-current-outgoing; Sat, 23 Jan 1999 11:44:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA08206 for ; Sat, 23 Jan 1999 11:44:52 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id TAA72666; Sat, 23 Jan 1999 19:45:48 GMT Date: Sat, 23 Jan 1999 19:45:48 +0000 (GMT) From: Doug Rabson To: Peter Wemm cc: Matthew Dillon , current@FreeBSD.ORG Subject: Re: panic: found dirty cache page 0xf046f1c0 In-Reply-To: <199901231928.DAA00732@spinner.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 24 Jan 1999, Peter Wemm wrote: > Doug Rabson wrote: > > On Sat, 23 Jan 1999, Matthew Dillon wrote: > > > > > > > > :I made it happen again by doing the same installworld but this time I > > > :caught it in the debugger. I'll leave the machine up for a while in case > > > :someone has some idea of how to debug it. The stacktrace looks like this: > > > : > > > :#0 Debugger () at ../../alpha/alpha/db_interface.c:260 > > > :#1 0xfffffc000036c2c0 in panic () at ../../kern/kern_shutdown.c:444 > > > :#2 0xfffffc00004942fc in vm_page_alloc () at ../../vm/vm_page.c:1041 > > > :#3 0xfffffc00003a1b54 in allocbuf () at ../../kern/vfs_bio.c:1791 > > > > > > The panic message should be printing the address of the vm_page_t that > > > it caught. > > > > > > From the debugger, dump that vm_page_t with 'print'. > > > > > > print *0xADDRESS > > > > > > Do about 8 print's bumping the address by 4 ( in hex ) for each. > > > > > > It would be even better if we could figure out the contents and type > > > of the underlying object. > > > > I have full symbols: > > > > (gdb) fr 2 > > #2 0xfffffc00004942fc in vm_page_alloc () at ../../vm/vm_page.c:1041 > > 1041 panic("found dirty cache page %p", m); > > (gdb) l > > 1036 */ > > 1037 > > 1038 if (qtype == PQ_CACHE) { > > 1039 #if !defined(MAX_PERF) > > 1040 if (m->dirty) > > 1041 panic("found dirty cache page %p", m); > > 1042 > > 1043 #endif > > 1044 vm_page_busy(m); > > 1045 vm_page_protect(m, VM_PROT_NONE); > > (gdb) p m > > $4 = (struct vm_page *) 0xfffffe0000108f40 > > (gdb) p *m > > $5 = {pageq = {tqe_next = 0x0, tqe_prev = 0xfffffc000052ecc8}, hnext = 0x0, > > listq = {tqe_next = 0xfffffe0000090fe0, tqe_prev = 0xfffffe00000bb6b8}, > > object = 0xfffffe00050e2a10, pindex = 12, phys_addr = 88940544, queue = 172 > , > > flags = 128, pc = 41, wire_count = 0, hold_count = 0, act_count = 5 '\005', > > > busy = 0 '\000', valid = 65535, dirty = 65535} > > > -- > > Doug, Matt wanted some things from m->object too.. If it's still there > can you grab it? > > printf( > "found dirty cache page %p (%p,%d,%x) obtype %d obflags %x", > m, > m->object, > (int)m->pindex, > (int)m->flags, > (int)m->object->type, > (int)m->object->flags > ); He sent me private mail asking for m->object which I replied to. Here is *m->object: $6 = {object_list = {tqe_next = 0xfffffe0005369870, tqe_prev = 0xfffffe000527e0b8}, shadow_head = {tqh_first = 0x0, tqh_last = 0xfffffe00050e2a20}, shadow_list = {tqe_next = 0x0, tqe_prev = 0xfffffe00052d2020}, memq = {tqh_first = 0xfffffe00000c8f80, tqh_last = 0xfffffe0000115a78}, generation = 897, type = OBJT_DEFAULT, size = 23, ref_count = 1, shadow_count = 0, pg_color = 4, hash_rand = -15145890, flags = 8192, paging_in_progress = 0, behavior = 0, resident_page_count = 15, cache_count = 15, wire_count = 0, backing_object = 0x0, backing_object_offset = 0, last_read = 0, pager_object_list = {tqe_next = 0x0, tqe_prev = 0x0}, handle = 0x0, un_pager = {vnp = {vnp_size = 754}, devp = {devp_pglist = { tqh_first = 0x2f2, tqh_last = 0x0}}, swp = {swp_bcount = 754}}} > > BTW; in vm_map.c: > /* > * vm_map_clean > * > * Push any dirty cached pages in the address range to their pager. > * If syncio is TRUE, dirty pages are written synchronously. > * If invalidate is TRUE, any cached pages are freed as well. > * > * Returns an error if any part of the specified range is not mapped. > */ > This kinda suggests that dirty cached pages might not be all that > unusual.. but the code in question seems to be working at a different > level. I'm not too familiar with this code. It is only called from msync(2) as far as I can see. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 11:46:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08334 for freebsd-current-outgoing; Sat, 23 Jan 1999 11:46:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.mn.mediaone.net (h-182-40.mn.mediaone.net [209.32.182.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA08314 for ; Sat, 23 Jan 1999 11:46:06 -0800 (PST) (envelope-from veldy@visi.com) Received: from visi.com (localhost.mn.mediaone.net [127.0.0.1]) by rover.mn.mediaone.net (8.9.1/8.9.1) with ESMTP id NAA64780 for ; Sat, 23 Jan 1999 13:46:37 -0600 (CST) (envelope-from veldy@visi.com) Message-ID: <36AA271C.1BCFA7B7@visi.com> Date: Sat, 23 Jan 1999 13:46:36 -0600 From: "Thomas T. Veldhouse" X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-Current Subject: Failure to make buildworld on RELENG_3 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems to be the same problem we have been having with current. Should it be crypt stuff be backed out of here as well? ===> libpam/modules/pam_radius ===> libpam/modules/pam_skey ===> libpam/modules/pam_tacplus ===> libpam/modules/pam_unix ===> libpam/libpam ld -o pam_static_modules.o -r -Bforcearchive pam_static.o ../modules/pam_cleartext_pass_ok/libpam_cleart ext_pass_ok.a ../modules/pam_kerberosIV/libpam_kerberosIV.a ../modules/pam_radius/libpam_radius.a ../mod ules/pam_skey/libpam_skey.a ../modules/pam_tacplus/libpam_tacplus.a ../modules/pam_unix/libpam_unix.a ../modules/pam_cleartext_pass_ok/libpam_cleartext_pass_ok.a(pam_cleartext_pass_ok.o): Definition of symb ol `_pam_sm_authenticate' (multiply defined) ../modules/pam_cleartext_pass_ok/libpam_cleartext_pass_ok.a(pam_cleartext_pass_ok.o): Definition of symb ol `_pam_sm_setcred' (multiply defined) ../modules/pam_kerberosIV/libpam_kerberosIV.a(pam_kerberosIV.o): Definition of symbol `_pam_sm_authentic ate' (multiply defined) ../modules/pam_kerberosIV/libpam_kerberosIV.a(pam_kerberosIV.o): Definition of symbol `_pam_sm_setcred' (multiply defined) ../modules/pam_radius/libpam_radius.a(pam_radius.o): Definition of symbol `_pam_sm_authenticate' (multip ly defined) ../modules/pam_radius/libpam_radius.a(pam_radius.o): Definition of symbol `_pam_sm_setcred' (multiply de fined) ../modules/pam_skey/libpam_skey.a(pam_skey.o): Definition of symbol `_pam_sm_authenticate' (multiply def ined) ../modules/pam_skey/libpam_skey.a(pam_skey.o): Definition of symbol `_pam_sm_setcred' (multiply defined) ../modules/pam_tacplus/libpam_tacplus.a(pam_tacplus.o): Definition of symbol `_pam_sm_authenticate' (mul tiply defined) ../modules/pam_tacplus/libpam_tacplus.a(pam_tacplus.o): Definition of symbol `_pam_sm_setcred' (multiply defined) ../modules/pam_unix/libpam_unix.a(pam_unix.o): Definition of symbol `_pam_sm_authenticate' (multiply def ined) ../modules/pam_unix/libpam_unix.a(pam_unix.o): Definition of symbol `_pam_sm_setcred' (multiply defined) *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Tom Veldhoue veldy@visi.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 11:56:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09203 for freebsd-current-outgoing; Sat, 23 Jan 1999 11:56:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA09198 for ; Sat, 23 Jan 1999 11:56:10 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id LAA48625; Sat, 23 Jan 1999 11:55:49 -0800 (PST) (envelope-from dillon) Date: Sat, 23 Jan 1999 11:55:49 -0800 (PST) From: Matthew Dillon Message-Id: <199901231955.LAA48625@apollo.backplane.com> To: Peter Wemm Cc: current@FreeBSD.ORG Subject: Re: panic: found dirty cache page 0xf046f1c0 References: <199901231943.DAA00782@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :[..] :> > Try changing the panic in vm/vm_page.c to a printf() ( :> :> I'll do that. : :BTW; what are the dangers of this? lost disk writes or corruption? Can :we (as a workaround) push the page that we found back onto a dirty queue :and try again after some diagnostics? That's ok, don't worry about it... Doug's debug output gives me the same info. :It crashed in uniprocessor mode about 60 seconds after sending this mail. :It's got a really trimmed down kernel config and no modules loaded or in :use. I have not disabled softupdates yet, that's next. I don't get it.... why can't I reproduce this problem? Can you email me your kernel configuration? Are you using any special devices like vn or something ? :Oh, one other thing that occurred to me.. Under 4.0-current, I regularly :(ie: within 30 seconds of boot) get if_de tranmitter underflows. My :console corruption was happening at the instant that de0 was being :configured with ifconfig. exmh is running to a remote display over that :de0 interface. : :Under Jan 16 3.0-current, I do not get that tranmitter underflow.. : :The only thin I can think of about if_de that's unusual that is VM related :(apart from the complexity of the code) is that it uses configmalloc(). I :wonder if this is somehow setting the scene for the later failures? It's :certainly suspicious that has done strange things when being ifconfig'ed, :including things like trashing the serial console on no less than a dozen :occasions. : :Cheers, :-Peter Hmmm.. HMMMMMM. contigmalloc, eh? You might be onto something here. I will investigate it. The problem was are having is that, somehow, a vm_page_t in the PQ_CACHE is being set dirty. Sinc vm_page_cache() panics if m->dirty is set, then m->dirty must be getting set *after* the page has been moved to the cache. contigmalloc() looks suspicious. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 11:59:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09627 for freebsd-current-outgoing; Sat, 23 Jan 1999 11:59:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.128.29.136]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA09622 for ; Sat, 23 Jan 1999 11:59:10 -0800 (PST) (envelope-from mi@aldan.algebra.com) Received: from rtfm.ziplink.net (rtfm [10.10.0.1]) by kot.ne.mediaone.net (8.9.1a/8.9.1) with ESMTP id OAA04055 for ; Sat, 23 Jan 1999 14:58:49 -0500 (EST) From: Mikhail Teterin X-Relay-IP: 10.10.0.1 Received: (from mi@localhost) by rtfm.ziplink.net (8.9.2/8.9.1) id OAA71391 for current@freebsd.org; Sat, 23 Jan 1999 14:59:04 -0500 (EST) Message-Id: <199901231959.OAA71391@rtfm.ziplink.net> Subject: current version bump brakes libtool To: current@FreeBSD.ORG Date: Sat, 23 Jan 1999 14:59:04 -0500 (EST) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA10443 for freebsd-current-outgoing; Sat, 23 Jan 1999 12:07:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA10438 for ; Sat, 23 Jan 1999 12:07:16 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.2/8.9.2/Netplex) with ESMTP id EAA00970; Sun, 24 Jan 1999 04:06:49 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199901232006.EAA00970@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon cc: current@FreeBSD.ORG Subject: Re: panic: found dirty cache page 0xf046f1c0 In-reply-to: Your message of "Sat, 23 Jan 1999 11:55:49 PST." <199901231955.LAA48625@apollo.backplane.com> Date: Sun, 24 Jan 1999 04:06:48 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: [..] > :Oh, one other thing that occurred to me.. Under 4.0-current, I regularly > :(ie: within 30 seconds of boot) get if_de tranmitter underflows. My > :console corruption was happening at the instant that de0 was being > :configured with ifconfig. exmh is running to a remote display over that > :de0 interface. > : > :Under Jan 16 3.0-current, I do not get that tranmitter underflow.. > : > :The only thin I can think of about if_de that's unusual that is VM related > :(apart from the complexity of the code) is that it uses configmalloc(). I > :wonder if this is somehow setting the scene for the later failures? It's > :certainly suspicious that has done strange things when being ifconfig'ed, > :including things like trashing the serial console on no less than a dozen > :occasions. > : > :Cheers, > :-Peter > > Hmmm.. HMMMMMM. contigmalloc, eh? You might be onto something here. > I will investigate it. > > The problem was are having is that, somehow, a vm_page_t in the PQ_CACHE > is being set dirty. > > Sinc vm_page_cache() panics if m->dirty is set, then m->dirty must be get ting > set *after* the page has been moved to the cache. > > contigmalloc() looks suspicious. Damn, I must be loosing my mind. if_de doesn't use contigmalloc.. it either did, or was going to as a result of the problem of the transmit descriptor array crossing a page boundary that had to be contiguous. In the end there were two seperate malloc's, each less than PAGE_SIZE. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 12:13:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA10992 for freebsd-current-outgoing; Sat, 23 Jan 1999 12:13:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA10982 for ; Sat, 23 Jan 1999 12:13:18 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id UAA72779; Sat, 23 Jan 1999 20:14:29 GMT Date: Sat, 23 Jan 1999 20:14:29 +0000 (GMT) From: Doug Rabson To: Peter Wemm cc: Matthew Dillon , current@FreeBSD.ORG Subject: Re: panic: found dirty cache page 0xf046f1c0 In-Reply-To: <199901231943.DAA00782@spinner.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 24 Jan 1999, Peter Wemm wrote: > > Oh, one other thing that occurred to me.. Under 4.0-current, I regularly > (ie: within 30 seconds of boot) get if_de tranmitter underflows. My > console corruption was happening at the instant that de0 was being > configured with ifconfig. exmh is running to a remote display over that > de0 interface. > > Under Jan 16 3.0-current, I do not get that tranmitter underflow.. One of my alpha boxes has always got a few of these errors when it first transmits a largish packet. It happened under NetBSD and FreeBSD since I bought the machine (about June last year I think). Andrew Gallatin has seen similar errors on OSF1. I think its harmless. > > The only thin I can think of about if_de that's unusual that is VM related > (apart from the complexity of the code) is that it uses configmalloc(). I > wonder if this is somehow setting the scene for the later failures? It's > certainly suspicious that has done strange things when being ifconfig'ed, > including things like trashing the serial console on no less than a dozen > occasions. I can't see where if_de is using contigmalloc(). I thought the bus_dma code in there wasn't used on FreeBSD. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 12:27:41 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA11866 for freebsd-current-outgoing; Sat, 23 Jan 1999 12:27:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Wit401305.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA11860 for ; Sat, 23 Jan 1999 12:27:39 -0800 (PST) (envelope-from daeron@Wit401305.student.utwente.nl) Received: from localhost (daeron@localhost) by Wit401305.student.utwente.nl (8.9.2/8.9.2) with ESMTP id VAA00310 for ; Sat, 23 Jan 1999 21:27:28 +0100 (CET) (envelope-from daeron@Wit401305.student.utwente.nl) Date: Sat, 23 Jan 1999 21:27:27 +0100 (CET) From: Pascal Hofstee To: freebsd-current@FreeBSD.ORG Subject: Bootstrap loader problems on CURRENT Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As of Today's 4.0-CURRENT My system Halts on boot-up after the BTX Driver showing my BIOS-drives, with the following message: FreeBSD/i386 bootstrap loader, Revision 0.2 (daeron@shadowmere..... etc...) ficlExecFD: Error at line 1 then it shows a lot of Register-information with the message System halted this is when trying to execute boot/loader When I am fast enough on the Boot-Manager Boot-prompt .. I am able to simply type /kernel instead of 0:wd(0,a)/boot/loader and my System Will boot the 4.0-kernel and run fine. I CVSup-ed the sources earlier today .. (about 6-7 hours) -------------------- Pascal Hofstee - daeron@shadowmere.student.utwente.nl -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS d- s+: a-- C++ UB++++ P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP-- t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 12:53:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13920 for freebsd-current-outgoing; Sat, 23 Jan 1999 12:53:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA13914 for ; Sat, 23 Jan 1999 12:53:50 -0800 (PST) (envelope-from randy@psg.com) Received: from localhost (752 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Sat, 23 Jan 1999 12:53:39 -0800 (PST) (Smail-3.2.0.101 1997-Dec-17 #1 built 1998-Oct-13) Message-Id: Date: Sat, 23 Jan 1999 12:53:39 -0800 (PST) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: John Polstra Cc: current@FreeBSD.ORG Subject: Re: make aout-to-elf-build failure Newsgroups: polstra.freebsd.current References: <199901231907.LAA16027@vashon.polstra.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG an hour further on /usr/obj/aout/usr/src/tmp/usr/libexec/elf/ld: warning: libcrypt.so.2, needed by /usr/obj/elf/usr/src/kerberosIV/libexec/kauthd/../../lib/libkrb/libkrb.so, not found (try using --rpath) /usr/obj/elf/usr/src/kerberosIV/libexec/kauthd/../../lib/libkrb/libkrb.so: undefined reference to `crypt' *** Error code 1 Stop. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 12:57:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14641 for freebsd-current-outgoing; Sat, 23 Jan 1999 12:57:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14620 for ; Sat, 23 Jan 1999 12:57:22 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.1) with ESMTP id WAA14228; Sat, 23 Jan 1999 22:57:07 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.2/8.9.2) with ESMTP id WAA00334; Sat, 23 Jan 1999 22:57:05 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199901232057.WAA00334@greenpeace.grondar.za> To: "Thomas T. Veldhouse" cc: FreeBSD-Current Subject: Re: Failure to make buildworld on RELENG_3 In-Reply-To: Your message of " Sat, 23 Jan 1999 13:46:36 CST." <36AA271C.1BCFA7B7@visi.com> References: <36AA271C.1BCFA7B7@visi.com> Date: Sat, 23 Jan 1999 22:57:04 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Thomas T. Veldhouse" wrote: > It seems to be the same problem we have been having with current. > Should it be crypt stuff be backed out of here as well? _Completely_ Different issue. :-( M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 13:44:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20309 for freebsd-current-outgoing; Sat, 23 Jan 1999 13:44:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20300 for ; Sat, 23 Jan 1999 13:44:49 -0800 (PST) (envelope-from rock@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.2/1999010400) with ESMTP id WAA16483 for ; Sat, 23 Jan 1999 22:44:36 +0100 (CET) Received: from wurzelausix.cs.uni-sb.de (wurzelausix.cs.uni-sb.de [134.96.247.1]) by cs.uni-sb.de (8.9.2/1999010400) with ESMTP id WAA19450 for ; Sat, 23 Jan 1999 22:44:31 +0100 (CET) Received: (from rock@localhost) by wurzelausix.cs.uni-sb.de (8.9.1/wjp/19980821) id WAA10840 for current@freebsd.org; Sat, 23 Jan 1999 22:44:31 +0100 (CET) Date: Sat, 23 Jan 1999 22:44:31 +0100 (CET) From: "D. Rock" Message-Id: <199901232144.WAA10840@wurzelausix.cs.uni-sb.de> To: current@FreeBSD.ORG Subject: dirty fs after apm power off Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have noticed this behaviour on at least one machine. If I shutdown the machine with apm power off, the filesystem is dirty and has to been checked on the next reboot. It seems, the power is cut too fast. I don't have any problems with reboots. It seems the drive doesn't have the time to write the superblock back to disk. I simply put a DELAY(4000000) in the apm_power_off() routine and the problem fades away. Any thoughts on doing this a configurable option? It doesn't break anything, it only takes a few seconds longer for the machine to power off. The drive is a Maxtor Diamond Max (90432D2) 4GB IDE drive in an Asus SP98 board. Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 14:03:34 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA22026 for freebsd-current-outgoing; Sat, 23 Jan 1999 14:03:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA22019 for ; Sat, 23 Jan 1999 14:03:33 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA00373; Sat, 23 Jan 1999 13:55:48 -0800 (PST) Received: from s204m82.isp.whistle.com(207.76.204.82) via SMTP by alpo.whistle.com, id smtpdxDq364; Sat Jan 23 21:55:36 1999 Date: Sat, 23 Jan 1999 13:55:30 -0800 (PST) From: Julian Elischer X-Sender: julian@s204m82.isp.whistle.com To: "D. Rock" cc: current@FreeBSD.ORG Subject: Re: dirty fs after apm power off In-Reply-To: <199901232144.WAA10840@wurzelausix.cs.uni-sb.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG probably the drive needs write-caching turned off... On Sat, 23 Jan 1999, D. Rock wrote: > I have noticed this behaviour on at least one machine. > If I shutdown the machine with apm power off, the filesystem is dirty and > has to been checked on the next reboot. It seems, the power is cut too fast. > I don't have any problems with reboots. > It seems the drive doesn't have the time to write the superblock back to disk. > > I simply put a DELAY(4000000) in the apm_power_off() routine and the problem > fades away. > Any thoughts on doing this a configurable option? It doesn't break anything, > it only takes a few seconds longer for the machine to power off. > > The drive is a Maxtor Diamond Max (90432D2) 4GB IDE drive in an Asus SP98 > board. > > Daniel > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 14:51:57 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA27721 for freebsd-current-outgoing; Sat, 23 Jan 1999 14:51:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (tokyo-29.ppp.hooked.net [206.169.229.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27714 for ; Sat, 23 Jan 1999 14:51:53 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@zippy.dyn.ml.org [127.0.0.1]) by zippy.dyn.ml.org (8.9.1/8.8.8) with ESMTP id OAA15701; Sat, 23 Jan 1999 14:54:46 -0800 (PST) (envelope-from garbanzo@hooked.net) Date: Sat, 23 Jan 1999 14:54:45 -0800 (PST) From: Alex Zepeda X-Sender: garbanzo@zippy.dyn.ml.org To: "Kurt D. Zeilenga" cc: Alexander Sanda , current@FreeBSD.ORG Subject: Re: -current (aka 4.x) breaks libtool In-Reply-To: <36AA2580.53EE5AAD@OpenLDAP.Org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 23 Jan 1999, Kurt D. Zeilenga wrote: > At 05:47 PM 1/23/99 +0100, Alexander Sanda wrote: > >Even most recent versions of libtool (1.2e imho) fail to check for > >freebsd4* (as expected). As a result, they set can_build_shared to "no" > >which disables building of shared libraries. > > Here is a simple patch (which I'll forward this to the libtool > maintainers). I don't really like that because it assumes that FreeBSD 3.0 and greater will all have compatable binutils. Somehow I don't think this is going to be the case (or there's a strong chance that it won't be the case). That said, the following is what I've commited to the KDE tree. Index: ltconfig =================================================================== RCS file: /home/kde/kde-common/admin/ltconfig,v retrieving revision 1.14 retrieving revision 1.15 diff -u -r1.14 -r1.15 --- ltconfig 1998/12/16 13:55:25 1.14 +++ ltconfig 1999/01/21 07:17:16 1.15 @@ -1209,6 +1209,15 @@ hardcode_shlibpath_var=no ;; + # FreeBSD 4, uses gcc -shared to do shared libraries, for the time being. + freebsd4*) + archive_cmds='$CC -shared -o $lib$libobjs$deplibs' + hardcode_libdir_flag_spec='-R$libdir' + hardcode_direct=yes + hardcode_minus_L=no + hardcode_shlibpath_var=no + ;; + hpux9*) archive_cmds='$rm $objdir/$soname~$LD -b +s +b $install_libdir -o $objdir/$soname$libobjs$deplibs~test $objdir/$soname = $lib || mv $objdir/$soname $lib' hardcode_libdir_flag_spec='${wl}+b ${wl}$libdir' @@ -1606,7 +1615,7 @@ shlibpath_var=PATH ;; -freebsd2* | freebsd3*) +freebsd2* | freebsd3* | freebsd4*) objformat=`test -x /usr/bin/objformat && /usr/bin/objformat || echo aout` version_type=freebsd-$objformat library_names_spec='${libname}${release}.so$versuffix $libname.so' - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD http://www.freebsd.org/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 14:56:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28356 for freebsd-current-outgoing; Sat, 23 Jan 1999 14:56:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gina.neland.dk (mail.swimsuit.internet.dk [194.255.12.232]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28337 for ; Sat, 23 Jan 1999 14:56:00 -0800 (PST) (envelope-from root@swimsuit.internet.dk) Received: from gina (gina [192.168.0.14]) by gina.neland.dk (8.9.2/8.9.2) with ESMTP id XAA52915 for ; Sat, 23 Jan 1999 23:55:10 +0100 (CET) (envelope-from root@swimsuit.internet.dk) Date: Sat, 23 Jan 1999 23:55:09 +0100 (CET) From: Leif Neland X-Sender: root@gina.neland.dk To: freebsd-current@FreeBSD.ORG Subject: kernel 4, userland 3 = trouble? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I build a current-4 kernel on gina and installed it on arnold. Then I added 32MB ram. nfs'mounted gina's /usr/src and /usr/obj on arnold, and tried an installworld. But I got random reboots, I guess it was signal 11, segmentation fault. Could it be because I had a current-4 kernel, but a stable-3 userland? Or is it just bad ram? I downgraded /usr/src to stable-3, and made another kernel for arnold. I also removed the 32MB, leaving another 32 MB. Now I could do a complete installworld without errors. Which is the likely cause of the errors? bad ram or kernel and userland out of sync the wrong way? Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 15:02:43 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29110 for freebsd-current-outgoing; Sat, 23 Jan 1999 15:02:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA29104 for ; Sat, 23 Jan 1999 15:02:41 -0800 (PST) (envelope-from rock@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.2/1999010400) with ESMTP id AAA17228; Sun, 24 Jan 1999 00:02:23 +0100 (CET) Received: from wurzelausix (wurzelausix.cs.uni-sb.de [134.96.247.1]) by cs.uni-sb.de (8.9.2/1999010400) with ESMTP id AAA20590; Sun, 24 Jan 1999 00:02:23 +0100 (CET) Received: from vodix.aremorika (vodix [134.96.247.43]) by wurzelausix (8.9.1/wjp/19980821) with ESMTP id AAA12296; Sun, 24 Jan 1999 00:02:22 +0100 (CET) From: "D. Rock" Received: by vodix.aremorika; Sun, 24 Jan 1999 00:02:21 +0100 (MET) Date: Sun, 24 Jan 1999 00:02:21 +0100 (MET) Message-Id: <199901232302.AAA06978@vodix.aremorika> To: julian@whistle.com Cc: current@FreeBSD.ORG Subject: Re: dirty fs after apm power off Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is what I also thought. But how do I turn off write caching on IDE disks. I know how to do on SCSI bit (mode page 8 byte 2 bit 2 clear), but I have absolutely no clue how this can be achieved on IDE disks. I normally turn off write caching on all drives I install. The drive shouldn't shuffle the carefully sorted file system blocks. Daniel > probably the drive needs write-caching turned off... > > > On Sat, 23 Jan 1999, D. Rock wrote: > > > I have noticed this behaviour on at least one machine. > > If I shutdown the machine with apm power off, the filesystem is dirty and > > has to been checked on the next reboot. It seems, the power is cut too fast. > > I don't have any problems with reboots. > > It seems the drive doesn't have the time to write the superblock back to disk. > > > > I simply put a DELAY(4000000) in the apm_power_off() routine and the problem > > fades away. > > Any thoughts on doing this a configurable option? It doesn't break anything, > > it only takes a few seconds longer for the machine to power off. > > > > The drive is a Maxtor Diamond Max (90432D2) 4GB IDE drive in an Asus SP98 > > board. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 15:12:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00230 for freebsd-current-outgoing; Sat, 23 Jan 1999 15:12:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00224 for ; Sat, 23 Jan 1999 15:12:25 -0800 (PST) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (lxpxew.lx.ehu.es [158.227.99.226]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id AAA05310; Sun, 24 Jan 1999 00:12:00 +0100 (MET) Message-ID: <36AA573E.29040BCB@we.lc.ehu.es> Date: Sun, 24 Jan 1999 00:11:58 +0100 From: "José Mª Alcaide" Organization: Universidad del País Vasco - Dept. Electricidad y Electrónica X-Mailer: Mozilla 4.07 [en] (X11; U; FreeBSD 3.0-STABLE i386) MIME-Version: 1.0 To: "D. Rock" CC: julian@whistle.com, current@FreeBSD.ORG Subject: Re: dirty fs after apm power off References: <199901232302.AAA06978@vodix.aremorika> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG D. Rock wrote: > > This is what I also thought. But how do I turn off write caching on IDE > disks. I know how to do on SCSI bit (mode page 8 byte 2 bit 2 clear), but > I have absolutely no clue how this can be achieved on IDE disks. > > I normally turn off write caching on all drives I install. The drive shouldn't > shuffle the carefully sorted file system blocks. > Some BIOSes have an APM setting that forces a delay before turning the power supply off. -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | http://www.we.lc.ehu.es/~jose Dpto. de Electricidad y Electrónica | Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139 ----------------------------------------------------------------------- "Go ahead... make my day." - H. Callahan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 15:49:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03485 for freebsd-current-outgoing; Sat, 23 Jan 1999 15:49:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cerebus.nectar.com (nectar-gw.nectar.com [204.0.249.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03478 for ; Sat, 23 Jan 1999 15:49:56 -0800 (PST) (envelope-from nectar@nectar.com) Received: (from smap@localhost) by cerebus.nectar.com (8.9.1/8.9.1) id RAA15498 for ; Sat, 23 Jan 1999 17:49:45 -0600 (CST) (envelope-from nectar@nectar.com) Received: from spawn.nectar.com(10.0.0.101) by cerebus.nectar.com via smap (V2.1) id xma015496; Sat, 23 Jan 99 17:49:39 -0600 Received: from spawn.nectar.com (localhost [127.0.0.1]) by spawn.nectar.com (8.9.2/8.9.1) with ESMTP id RAA46060 for ; Sat, 23 Jan 1999 17:49:39 -0600 (CST) (envelope-from nectar@spawn.nectar.com) Message-Id: <199901232349.RAA46060@spawn.nectar.com> X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine Subject: ack! LaTeX? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii To: current@FreeBSD.ORG Date: Sat, 23 Jan 1999 17:49:39 -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Do any of the LaTeX ports work anymore, or do I have something grubby in my ${LOCALBASE}? I tried latex, teTeX, and teTeX-beta... each had one problem or another. latex can't be fetched, teTeX-beta can't build, and teTeX doesn't work after being installed. Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 15:55:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03984 for freebsd-current-outgoing; Sat, 23 Jan 1999 15:55:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03978 for ; Sat, 23 Jan 1999 15:55:47 -0800 (PST) (envelope-from loqaswe@pvtnet.cz) From: loqaswe@pvtnet.cz Received: from dellcity.com ([207.243.98.34]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id PAA06467 for ; Sat, 23 Jan 1999 15:55:46 -0800 (PST) Received: from default (mid-qbu-nqs-vty17.as.wcom.net [209.154.74.17]) by dellcity.com (8.8.8+Sun/8.8.8) with SMTP id QAA01423; Sat, 23 Jan 1999 16:39:23 -0700 (MST) Date: Sat, 23 Jan 1999 16:39:23 -0700 (MST) Message-Id: <199901232339.QAA01423@dellcity.com> To: loqaswe@pvtnet.cz Subject: $150K+ Per Year / Home-Based / NOT MLM Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We are sorry if you received this email in error. To be removed from this list please send an email to the address below. mailto:"getlost@tfz.net" $ ENTREPRENEURS $ *Tired of working for someone else and getting paid what "they" feel you're worth? *Tired of the "get-rich-quick" $5 fantasy programs? *Tired of the MLM "dream scene"? *Looking for a legitimate home-based enterprise that can generate you $10k-$20k+ monthly? THEN CHECK THIS OUT!!! >90% profit on all sales that pay you from $1250-$6250 per sale >No personal selling or "convince me" tactics involved >No special skills or equipment required or "inventory" to keep >Complete information system in place does the explaining for you >Free-enterprise in its purest form, not MLM or franchise >Full training and support in an environment of upmost integrity >Exceptional products, not "vitamins, lotions, and potions" >Lead generation system that brings qualified prospects to you >Multiple 6 figure income realistically attainable in 1st year >2 to 3 year retirement program... PERIOD! This program is all about money... how to make it, how to keep it, and how to make it work for you. CALL NOW!!! 1-888-316-1204 Leave your name and number. After a brief interview, I will get you all the information you need to make your own relaxed and intelligent decision about your future. (Serious inquiries only please) J. Hampton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 16:13:59 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA07505 for freebsd-current-outgoing; Sat, 23 Jan 1999 16:13:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from stade.demon.co.uk (stade.demon.co.uk [158.152.29.164]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA07498 for ; Sat, 23 Jan 1999 16:13:54 -0800 (PST) (envelope-from aw1@stade.co.uk) Received: (from aw1@localhost) by stade.demon.co.uk (8.9.2/8.9.1) id OAA03706 for current@FreeBSD.ORG; Sat, 23 Jan 1999 14:24:59 GMT (envelope-from aw1) Date: Sat, 23 Jan 1999 14:24:58 +0000 From: Adrian Wontroba To: current@FreeBSD.ORG Subject: Re: Heads up! New swapper and VM changes have been committed to -4.x Message-ID: <19990123142458.A36980@titus.stade.co.uk> Reply-To: aw1@stade.co.uk References: <199901210456.UAA10191@apollo.backplane.com> <199901210855.AAA05930@apollo.backplane.com> <19990123104630.A74306@titus.stade.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990123104630.A74306@titus.stade.co.uk>; from Adrian Wontroba on Sat, Jan 23, 1999 at 10:46:30AM +0000 X-Operating-System: FreeBSD 4.0-CURRENT Organization: Yes, I need some of that. X-Phone: +(44) 121 681 6677 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 23, 1999 at 10:46:30AM +0000, Adrian Wontroba wrote: > I've tried, with sources cvsupped at 0600 22/11/1999 UTC. On a 128MB ! 0 (sigh, up too late) -- Adrian Wontroba To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 16:33:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA09742 for freebsd-current-outgoing; Sat, 23 Jan 1999 16:33:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA09737 for ; Sat, 23 Jan 1999 16:33:28 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA02729; Sat, 23 Jan 1999 16:30:47 -0800 (PST) Received: from s204m82.isp.whistle.com(207.76.204.82) via SMTP by alpo.whistle.com, id smtpddM2726; Sun Jan 24 00:30:46 1999 Date: Sat, 23 Jan 1999 16:30:42 -0800 (PST) From: Julian Elischer X-Sender: julian@s204m82.isp.whistle.com To: Doug Rabson cc: current@FreeBSD.ORG Subject: Re: Device Framework Overview In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is this the first page of a 20 page document giving examples and pointers? :-) On Sat, 23 Jan 1999, Doug Rabson wrote: > I've just posted a brief overview of the new device system in FreeBSD at > http://www.freebsd.org/~dfr/devices.html. The information content is > fairly small but it might help someone who is trying to understand the > source code. > > -- > Doug Rabson Mail: dfr@nlsystems.com > Nonlinear Systems Ltd. Phone: +44 181 442 9037 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 16:44:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10627 for freebsd-current-outgoing; Sat, 23 Jan 1999 16:44:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA10617 for ; Sat, 23 Jan 1999 16:44:13 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id AAA73518; Sun, 24 Jan 1999 00:45:29 GMT Date: Sun, 24 Jan 1999 00:45:28 +0000 (GMT) From: Doug Rabson To: Julian Elischer cc: current@FreeBSD.ORG Subject: Re: Device Framework Overview In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 23 Jan 1999, Julian Elischer wrote: > Is this the first page of a 20 page document giving examples and pointers? > :-) No.. Its just an overview at the moment (it started off as some email explaining roughly how the thing fits together). Maybe I'll find the time to write some more sometime. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 16:45:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10961 for freebsd-current-outgoing; Sat, 23 Jan 1999 16:45:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA10954 for ; Sat, 23 Jan 1999 16:45:56 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id QAA52250; Sat, 23 Jan 1999 16:45:34 -0800 (PST) (envelope-from dillon) Date: Sat, 23 Jan 1999 16:45:34 -0800 (PST) From: Matthew Dillon Message-Id: <199901240045.QAA52250@apollo.backplane.com> To: Adrian Wontroba Cc: current@FreeBSD.ORG Subject: Re: Heads up! New swapper and VM changes have been committed to -4.x References: <199901210456.UAA10191@apollo.backplane.com> <199901210855.AAA05930@apollo.backplane.com> <19990123104630.A74306@titus.stade.co.uk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :swapinfo output looks a little odd: : : :Device 1K-blocks Used Avail Capacity Type :/dev/da0s2b 196608 19372 177108 10% Interleaved :/dev/da3b 196704 19140 177436 10% Interleaved :Total 393056 393056 0 100% : :The totals don't appear to add up. Make sure your /usr/src/lib/libkvm is updated. Also update /usr/src/include/kvm.h. Then update and recompile top, systat, and pstat. -Matt :-- :Adrian Wontroba : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-current" in the body of the message : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 16:54:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA11643 for freebsd-current-outgoing; Sat, 23 Jan 1999 16:54:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from liquid.tpb.net (drum-n-bass.party-animals.com [194.134.94.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA11638 for ; Sat, 23 Jan 1999 16:54:04 -0800 (PST) (envelope-from niels@bakker.net) Received: from localhost (niels@localhost) by liquid.tpb.net (8.9.1a/8.8.8/Debian/GNU) with SMTP id BAA27186; Sun, 24 Jan 1999 01:50:25 +0100 Date: Sun, 24 Jan 1999 01:50:24 +0100 (CET) From: N To: Peter Wemm cc: current@FreeBSD.ORG Subject: Re: panic: found dirty cache page 0xf046f1c0 In-Reply-To: <199901231943.DAA00782@spinner.netplex.com.au> Message-ID: <990124014147.27036A-100000@liquid.tpb.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 24 Jan 1999, Peter Wemm wrote: [..] > Oh, one other thing that occurred to me.. Under 4.0-current, I regularly > (ie: within 30 seconds of boot) get if_de tranmitter underflows. My > console corruption was happening at the instant that de0 was being > configured with ifconfig. exmh is running to a remote display over that > de0 interface. Here too... pretty quickly after boot on a SMP machine (current as of Jan 12) that pushes quite a bit of traffic, the following messages appear: de0: abnormal interrupt: transmit underflow (raising TX threshold to 96|256) de0: abnormal interrupt: transmit underflow (raising TX threshold to 128|512) de0: abnormal interrupt: transmit underflow (raising TX threshold to 160|1024) The card is: de0: rev 0x22 int a irq 16 on pci0.12.0 de0: 21140A [10-100Mb/s] pass 2.2 de0: address 00:c0:f0:1f:5d:0d de0: enabling Full Duplex 100baseTX port Actually a Kingston clone, not a real DEC (so 1/5th of the price - but the receiver doesn't go audibly *click* when it's autosensing). So far I've gotten this message once: de0: abnormal interrupt: transmit underflow (switching to store-and-forward mode) Any harm in them, or can I safely ignore them? Would it be a good idea to raise the TX threshold by default, if only to avoid the messages? It's plugged into a Catalyst switch, if it makes any difference... -- Niels. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 17:02:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA12858 for freebsd-current-outgoing; Sat, 23 Jan 1999 17:02:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA12849 for ; Sat, 23 Jan 1999 17:02:45 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id RAA53285; Sat, 23 Jan 1999 17:02:26 -0800 (PST) (envelope-from dillon) Date: Sat, 23 Jan 1999 17:02:26 -0800 (PST) From: Matthew Dillon Message-Id: <199901240102.RAA53285@apollo.backplane.com> To: N Cc: Peter Wemm , current@FreeBSD.ORG Subject: Re: panic: found dirty cache page 0xf046f1c0 References: <990124014147.27036A-100000@liquid.tpb.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, we're working on it in a sub-group. Since the panic message is a new one -- it's one I added that never existed in -3.x, it is possible that the bug is not related to my VM stuff but related to something else going on. I've found a number of other bugs in the greater VM system which I am comitting fixes for, *BUT* I don't think any of them are related to this particular panic. I am also comitting some very strict KASSERT checking to try to catch the problem earlier. Everyone running 4.x kernels should add the following options to your kernel config: options INVARIANTS options INVARIANT_SUPPORT -Matt Matthew Dillon :On Sun, 24 Jan 1999, Peter Wemm wrote: : :[..] :> Oh, one other thing that occurred to me.. Under 4.0-current, I regularly :> (ie: within 30 seconds of boot) get if_de tranmitter underflows. My :> console corruption was happening at the instant that de0 was being :> configured with ifconfig. exmh is running to a remote display over that :> de0 interface. : :Here too... pretty quickly after boot on a SMP machine (current as of Jan :12) that pushes quite a bit of traffic, the following messages appear: : :de0: abnormal interrupt: transmit underflow (raising TX threshold to 96|256) :de0: abnormal interrupt: transmit underflow (raising TX threshold to 128|512) :de0: abnormal interrupt: transmit underflow (raising TX threshold to 160|1024) : :The card is: : :de0: rev 0x22 int a irq 16 on pci0.12.0 :de0: 21140A [10-100Mb/s] pass 2.2 :de0: address 00:c0:f0:1f:5d:0d :de0: enabling Full Duplex 100baseTX port : :Actually a Kingston clone, not a real DEC (so 1/5th of the price - but the :receiver doesn't go audibly *click* when it's autosensing). : :So far I've gotten this message once: : :de0: abnormal interrupt: transmit underflow (switching to store-and-forward mode) : :Any harm in them, or can I safely ignore them? Would it be a good idea to :raise the TX threshold by default, if only to avoid the messages? :It's plugged into a Catalyst switch, if it makes any difference... : : : -- Niels. : : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-current" in the body of the message : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 17:03:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA12909 for freebsd-current-outgoing; Sat, 23 Jan 1999 17:03:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.adsu.bellsouth.com (ns1.adsu.bellsouth.com [205.152.173.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA12902 for ; Sat, 23 Jan 1999 17:03:11 -0800 (PST) (envelope-from ck@ns1.adsu.bellsouth.com) Received: (from ck@localhost) by ns1.adsu.bellsouth.com (8.9.1a/8.9.1) id UAA17955 for freebsd-current@freebsd.org; Sat, 23 Jan 1999 20:02:53 -0500 (EST) Date: Sat, 23 Jan 1999 20:02:52 -0500 From: Christian Kuhtz To: freebsd-current@FreeBSD.ORG Subject: fetch Message-ID: <19990123200252.D15805@ns1.adsu.bellsouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey guys: I thought I'd put this up for discussion here. Does anyone have objections to changing the default behavior for how the long password for fetch is chosen? Most FTP servers which do check the password given for an anonymous login, expect either 'username@' or 'username@valid.FQDN'. If the password is given just simply as 'username@host', login is refused. Can we do one of the following changes? a) make 'username@' the default b) leave 'username@domain' the default, as long as it can be verified to be a valid domain name, otherwise make it 'username@' Either way, the default could be overwritten by FTP_PASSWORD. Sure, I could achieve the above that way, too. However, it appears to make more sense to chose the described default than the current default, given the way anonymous FTP works. Please comment... Cheers, Chris -- "Economics is extremely useful as a form of employment for economists." -- John Kenneth Galbraith [Disclaimer: I speak for myself and my views are my own and not in any way to be construed as the views of BellSouth Corporation. ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 17:38:42 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17261 for freebsd-current-outgoing; Sat, 23 Jan 1999 17:38:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17251 for ; Sat, 23 Jan 1999 17:38:39 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id RAA54185; Sat, 23 Jan 1999 17:38:25 -0800 (PST) (envelope-from dillon) Date: Sat, 23 Jan 1999 17:38:25 -0800 (PST) From: Matthew Dillon Message-Id: <199901240138.RAA54185@apollo.backplane.com> To: N Cc: Peter Wemm , current@FreeBSD.ORG Subject: Re: panic: found dirty cache page 0xf046f1c0 References: <990124014147.27036A-100000@liquid.tpb.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Here too... pretty quickly after boot on a SMP machine (current as of Jan :12) that pushes quite a bit of traffic, the following messages appear: : :de0: abnormal interrupt: transmit underflow (raising TX threshold to 96|256) :de0: abnormal interrupt: transmit underflow (raising TX threshold to 128|512) :de0: abnormal interrupt: transmit underflow (raising TX threshold to 160|1024) : :The card is: : :de0: rev 0x22 int a irq 16 on pci0.12.0 :de0: 21140A [10-100Mb/s] pass 2.2 :de0: address 00:c0:f0:1f:5d:0d :de0: enabling Full Duplex 100baseTX port Three people getting these panics, three people with DEC ethernet cards. Random complaints about card during ifconfig: speaker goes click, console gets junked, etc etc etc. Is there anyone having this panic who does NOT have a DEC ethernet card ? I still don't think the card is causing the problem, but it would be nice if we could rule it out. -Matt : -- Niels. Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 17:43:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17604 for freebsd-current-outgoing; Sat, 23 Jan 1999 17:43:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from liquid.tpb.net (drum-n-bass.party-animals.com [194.134.94.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17594 for ; Sat, 23 Jan 1999 17:43:21 -0800 (PST) (envelope-from niels@bakker.net) Received: from localhost (niels@localhost) by liquid.tpb.net (8.9.1a/8.8.8/Debian/GNU) with SMTP id CAA27706; Sun, 24 Jan 1999 02:42:34 +0100 Date: Sun, 24 Jan 1999 02:42:33 +0100 (CET) From: N To: Matthew Dillon cc: current@FreeBSD.ORG Subject: Re: panic: found dirty cache page 0xf046f1c0 In-Reply-To: <199901240138.RAA54185@apollo.backplane.com> Message-ID: <990124023857.27664A-100000@liquid.tpb.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Here too... pretty quickly after boot on a SMP machine (current as of Jan >> 12) that pushes quite a bit of traffic, the following messages appear: >> de0: abnormal interrupt: transmit underflow (raising TX threshold to 96|256) [..] > Three people getting these panics, three people with DEC ethernet > cards. Random complaints about card during ifconfig: speaker goes click, > console gets junked, etc etc etc. Actually, I haven't had the console of that SMP machine junked yet, but that's because there is no console worth speaking of. Previous reboot was because processes like tail(1) only appeared to hang, unkillable except by -9, and after attaching monitor and keyboard, upon pressing at a login: prompt the cursor would only advance a line once... But that was a week ago, and it's a *busy* news server (that's not hitting swap), I was just curious about the error messages from the de driver. -- Niels. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 17:46:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA18187 for freebsd-current-outgoing; Sat, 23 Jan 1999 17:46:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA18176 for ; Sat, 23 Jan 1999 17:46:36 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id RAA54333; Sat, 23 Jan 1999 17:46:21 -0800 (PST) (envelope-from dillon) Date: Sat, 23 Jan 1999 17:46:21 -0800 (PST) From: Matthew Dillon Message-Id: <199901240146.RAA54333@apollo.backplane.com> To: N Cc: current@FreeBSD.ORG Subject: Re: panic: found dirty cache page 0xf046f1c0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :But that was a week ago, and it's a *busy* news server (that's not hitting :swap), I was just curious about the error messages from the de driver. : : -- Niels. The transmit underflow messages: de0: abnormal interrupt: transmit underflow (raising TX threshold to 96|256) de0: abnormal interrupt: transmit underflow (raising TX threshold to 128|512) de0: abnormal interrupt: transmit underflow (raising TX threshold to 160|1024) can typically be ignored. It simply means that the DEC card has too small a transmit FIFO and is getting DMA underflows. Stupid card. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 18:09:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20617 for freebsd-current-outgoing; Sat, 23 Jan 1999 18:09:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA20611 for ; Sat, 23 Jan 1999 18:09:29 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id VAA14692; Sat, 23 Jan 1999 21:07:40 -0500 (EST) Date: Sat, 23 Jan 1999 21:07:39 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Matthew Dillon cc: N , Peter Wemm , current@FreeBSD.ORG Subject: Re: panic: found dirty cache page 0xf046f1c0 In-Reply-To: <199901240102.RAA53285@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 23 Jan 1999, Matthew Dillon wrote: > Yes, we're working on it in a sub-group. > > Since the panic message is a new one -- it's one I added that never existed > in -3.x, it is possible that the bug is not related to my VM stuff but > related to something else going on. > > I've found a number of other bugs in the greater VM system which I am > comitting fixes for, *BUT* I don't think any of them are related to this > particular panic. > > I am also comitting some very strict KASSERT checking to try to catch > the problem earlier. Everyone running 4.x kernels should add the following Ahem, would you kindly define 'everyone'? > options to your kernel config: > > options INVARIANTS > options INVARIANT_SUPPORT > > > -Matt > Matthew Dillon > > > :On Sun, 24 Jan 1999, Peter Wemm wrote: > : > :[..] > :> Oh, one other thing that occurred to me.. Under 4.0-current, I regularly > :> (ie: within 30 seconds of boot) get if_de tranmitter underflows. My > :> console corruption was happening at the instant that de0 was being > :> configured with ifconfig. exmh is running to a remote display over that > :> de0 interface. > : > :Here too... pretty quickly after boot on a SMP machine (current as of Jan > :12) that pushes quite a bit of traffic, the following messages appear: > : > :de0: abnormal interrupt: transmit underflow (raising TX threshold to 96|256) > :de0: abnormal interrupt: transmit underflow (raising TX threshold to 128|512) > :de0: abnormal interrupt: transmit underflow (raising TX threshold to 160|1024) > : > :The card is: > : > :de0: rev 0x22 int a irq 16 on pci0.12.0 > :de0: 21140A [10-100Mb/s] pass 2.2 > :de0: address 00:c0:f0:1f:5d:0d > :de0: enabling Full Duplex 100baseTX port > : > :Actually a Kingston clone, not a real DEC (so 1/5th of the price - but the > :receiver doesn't go audibly *click* when it's autosensing). > : > :So far I've gotten this message once: > : > :de0: abnormal interrupt: transmit underflow (switching to store-and-forward mode) > : > :Any harm in them, or can I safely ignore them? Would it be a good idea to > :raise the TX threshold by default, if only to avoid the messages? > :It's plugged into a Catalyst switch, if it makes any difference... > : > : > : -- Niels. > : > : > :To Unsubscribe: send mail to majordomo@FreeBSD.org > :with "unsubscribe freebsd-current" in the body of the message > : > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 18:19:01 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA21523 for freebsd-current-outgoing; Sat, 23 Jan 1999 18:19:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA21518 for ; Sat, 23 Jan 1999 18:18:59 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id SAA54613; Sat, 23 Jan 1999 18:18:42 -0800 (PST) (envelope-from dillon) Date: Sat, 23 Jan 1999 18:18:42 -0800 (PST) From: Matthew Dillon Message-Id: <199901240218.SAA54613@apollo.backplane.com> To: Brian Feldman Cc: N , Peter Wemm , current@FreeBSD.ORG Subject: Re: panic: found dirty cache page 0xf046f1c0 References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :> I am also comitting some very strict KASSERT checking to try to catch :> the problem earlier. Everyone running 4.x kernels should add the following : :Ahem, would you kindly define 'everyone'? Anyone, everyone, everybody, all ... any individual using the -4.x kernels needs to understand the highly experimental nature of said kernels. Turning on INVARIANTS is just plain smart. For many reasons but I will give you the top two: * The sanity checks could save your disks when someone commits a major mistake. * The sanity checks make it easier for bugs to be found and fixed when they do occur. -4.x is just getting on its feet, nobody should be shipping product with it for a while ( if they are, they are insane ). -Matt Matthew Dillon :> options to your kernel config: :> :> options INVARIANTS :> options INVARIANT_SUPPORT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 18:39:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA24384 for freebsd-current-outgoing; Sat, 23 Jan 1999 18:39:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA24372 for ; Sat, 23 Jan 1999 18:39:08 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.2/8.9.2/Netplex) with ESMTP id KAA01206; Sun, 24 Jan 1999 10:13:33 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199901240213.KAA01206@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon cc: N , current@FreeBSD.ORG Subject: Re: panic: found dirty cache page 0xf046f1c0 In-reply-to: Your message of "Sat, 23 Jan 1999 17:46:21 PST." <199901240146.RAA54333@apollo.backplane.com> Date: Sun, 24 Jan 1999 10:13:32 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > :But that was a week ago, and it's a *busy* news server (that's not hitting > :swap), I was just curious about the error messages from the de driver. > : > : -- Niels. > > The transmit underflow messages: > > de0: abnormal interrupt: transmit underflow (raising TX threshold to 96|256) > de0: abnormal interrupt: transmit underflow (raising TX threshold to 128|512) > de0: abnormal interrupt: transmit underflow (raising TX threshold to 160|1024 ) > > can typically be ignored. It simply means that the DEC card has too smal l > a transmit FIFO and is getting DMA underflows. Stupid card. As I understand it, what's happening is that it's reacting to pci bus congestion by raising the preread threshholds. It degenerates to fetching the entire frame into on-card (or chip) memory before beginning transmission. On my system I can understand it, it's a 2xP5 with a shared L2 cache on a Neptune chipset - something that isn't known for speed. Once you get two processors hammering the system bus, *plus* mix in an EISA scsi controller, I could well imagine the memory bus getting thrashed. I'm not sure how to read the messages. Looking at the if_pn driver as well, it looks like both start with a FIFO threshold of 72 bytes. I think that '160|1024' (for example) means start transmitting when the FIFO has fetched 160 bytes and don't stop fetching unless we hit 1024 bytes in the fifo. Store and forward mode (I believe) is a degenerate case where it fetches the entire packet into the buffer before beginning transmission. Bill Paul's if_pn driver doesn't react to an underflow at all.. it stays at 72/128 permanently. For what it's worth, the de cards are the only ones I've found that can work at all on this system at 100Mbit. The realtek 8139 cards (cheap!) went belly-up on the spot, no suprise there. I don't have an fxp card to test. > -Matt Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 18:40:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA24888 for freebsd-current-outgoing; Sat, 23 Jan 1999 18:40:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA24853 for ; Sat, 23 Jan 1999 18:40:26 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id VAA99231; Sat, 23 Jan 1999 21:45:56 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Sat, 23 Jan 1999 21:45:56 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Matthew Dillon cc: N , Peter Wemm , current@FreeBSD.ORG Subject: 2Re: panic: found dirty cache page 0xf046f1c0 In-Reply-To: <199901240138.RAA54185@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 23 Jan 1999, Matthew Dillon wrote: i have 'ed' driver and mine blows up as well. > :Here too... pretty quickly after boot on a SMP machine (current as of Jan > :12) that pushes quite a bit of traffic, the following messages appear: > : > :de0: abnormal interrupt: transmit underflow (raising TX threshold to 96|256) > :de0: abnormal interrupt: transmit underflow (raising TX threshold to 128|512) > :de0: abnormal interrupt: transmit underflow (raising TX threshold to 160|1024) > : > :The card is: > : > :de0: rev 0x22 int a irq 16 on pci0.12.0 > :de0: 21140A [10-100Mb/s] pass 2.2 > :de0: address 00:c0:f0:1f:5d:0d > :de0: enabling Full Duplex 100baseTX port> > Three people getting these panics, three people with DEC ethernet > cards. Random complaints about card during ifconfig: speaker goes click, > console gets junked, etc etc etc. > > s there anyone having this panic who does NOT have a DEC ethernet > card ? > > I still 04don't think the card is causing the problem, but it > wouldif we could rule it out. :( FreeBSD bright.reserved 4.0-CURRENT FreeBSD 4.0-CURRENT #2: Sat Jan 23 20:55:25 EST 1999 perlsta@bright.reserved:/usr/src/sys/compile/bright i386 ~ # ifconfig -a ed1: flags=8843 mtu 1500 inet 192.168.2.20 netmask 0xffffff00 broadcast 192.168.2.255 ether 00:00:21:4e:29:c3 tun0: flags=8010 mtu 1500 sl0: flags=c012 mtu 552 ppp0: flags=8010 mtu 1500 lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 Make release made my machine reboot, i hooked up a serial consol to it, i'll show my backtrace/etc if it happens again... wh00ps :) it just did: (this is by hand) -- panic: found dirty cache page 0xf047ae60 Debugger("panic") Stopped at Debugger+0x37: movl $0, in_Debugger db> c syncing disks... panic: found dirty cache page 0xf047ae60 Debugger("panic") Stopped at Debugger+0x37: movl $0, in_Debugger db> c -- i'm enabling crash dumps, i hope to god it doesn't eat my machine again. btw, i'm hardly 'stressing' this machine it's a k6-233+96ram and i'm running X and doing a 'make release' Is it safe to enable crashdumps on IDE disks yet? -Alfred > > -Matt > > : -- Niels. > > Matthew Dillon > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 18:44:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA25312 for freebsd-current-outgoing; Sat, 23 Jan 1999 18:44:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peloton.physics.montana.edu (peloton.physics.montana.edu [153.90.192.177]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA25307 for ; Sat, 23 Jan 1999 18:44:43 -0800 (PST) (envelope-from brett@peloton.physics.montana.edu) Received: from localhost (brett@localhost) by peloton.physics.montana.edu (8.8.8/8.8.7) with SMTP id TAA22813; Sat, 23 Jan 1999 19:44:18 -0700 (MST) (envelope-from brett@peloton.physics.montana.edu) Date: Sat, 23 Jan 1999 19:44:17 -0700 (MST) From: Brett Taylor To: Jacques Vidrine cc: current@FreeBSD.ORG Subject: Re: ack! LaTeX? In-Reply-To: <199901232349.RAA46060@spawn.nectar.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > I tried latex, teTeX, and teTeX-beta... each had one problem or > another. latex can't be fetched, teTeX-beta can't build, and teTeX > doesn't work after being installed. How is teTeX not working? I'm using a month or so old version of -current (back in the 3.0 days) on my home machine and teTeX works fine there. Brett ****************************************************************** Brett Taylor brett@peloton.physics.montana.edu http://peloton.physics.montana.edu/brett/ "love isn't someplace that we fall, it's something that we do" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 18:52:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA26285 for freebsd-current-outgoing; Sat, 23 Jan 1999 18:52:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA26275 for ; Sat, 23 Jan 1999 18:52:16 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id SAA57298; Sat, 23 Jan 1999 18:51:54 -0800 (PST) (envelope-from dillon) Date: Sat, 23 Jan 1999 18:51:54 -0800 (PST) From: Matthew Dillon Message-Id: <199901240251.SAA57298@apollo.backplane.com> To: Alfred Perlstein Cc: N , Peter Wemm , current@FreeBSD.ORG Subject: Re: 2Re: panic: found dirty cache page 0xf046f1c0 References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :i have 'ed' driver and mine blows up as well. : :panic: found dirty cache page 0xf047ae60 :Debugger("panic") Ok, so much for if_de being the cause. BTW, for anybody who doesn't want to wait for us to find the bug, you can comment out the MADV_FREE code and that should put a stop to it. The MADV_FREE code isn't broken, but it seems to cause the bug to occur which is why *I* haven't commented it out - I'd rather find the bug. Also, update your kernel trees and turn on the INVARIANTS options: options INVARIANTS options INVARIANT_SUPPORT -Matt Matthew Dillon : :btw, i'm hardly 'stressing' this machine it's a k6-233+96ram and :i'm running X and doing a 'make release' : :Is it safe to enable crashdumps on IDE disks yet? : :-Alfred I don't know. I wasn't aware that there was a problem with crash dumps on ide disks. There shouldn't be. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 18:53:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA26377 for freebsd-current-outgoing; Sat, 23 Jan 1999 18:53:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA26358; Sat, 23 Jan 1999 18:53:11 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:GVFVrdSS6wpzRBKHU9G+e+2qRYlotMcA@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id LAA18211; Sun, 24 Jan 1999 11:52:43 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id LAA24094; Sun, 24 Jan 1999 11:55:20 +0900 (JST) Message-Id: <199901240255.LAA24094@zodiac.mech.utsunomiya-u.ac.jp> To: peter@netplex.com.au, sos@FreeBSD.ORG, des@FreeBSD.ORG cc: current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Death to LKM screen savers? (was: Re: HEADS UP: i386 a.out LKM support now an option..) In-reply-to: Your message of "Mon, 18 Jan 1999 03:25:14 +0800." <199901171925.DAA06456@spinner.netplex.com.au> References: <199901171925.DAA06456@spinner.netplex.com.au> Date: Sun, 24 Jan 1999 11:55:19 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What if we declare death to LKM screen savers and remove them from the source tree? After all KLD screen savers are working well. Kazu >As of a few minutes ago, I committed some changes that: >1: make the LKM code use the common VFS and syscall registration routines >2: make an 'options LKM' option. >3: build an 'lkm' loadable kld module > >This means that if you are still using an a.out kernel and are loading >LKM's specifically, you either need to add 'options LKM' to your config, >or do a 'kldload lkm' to load the /dev/lkm support routines. [...] >However, the thought has occurred on many occasions that it might be an >idea to make a stand on this and remove the LKM build support. It will >clean up a few interfaces. If this doesn't happen for 3.1, it's definately >on my agenda for after the branch. Converting the common LKM's to kld >modules is pretty easy, and even the ones with custom load/unload code are >not too hard. I'd be interested to get a feeling for whether this should >be done for 3.1 or later. (Remember, OSS have a KLD version now for 3.0). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 19:09:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27719 for freebsd-current-outgoing; Sat, 23 Jan 1999 19:09:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA27714 for ; Sat, 23 Jan 1999 19:09:32 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id TAA57441; Sat, 23 Jan 1999 19:08:49 -0800 (PST) (envelope-from dillon) Date: Sat, 23 Jan 1999 19:08:49 -0800 (PST) From: Matthew Dillon Message-Id: <199901240308.TAA57441@apollo.backplane.com> To: Peter Wemm Cc: N , current@FreeBSD.ORG Subject: Re: panic: found dirty cache page 0xf046f1c0 References: <199901240213.KAA01206@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On my system I can understand it, it's a 2xP5 with a shared L2 cache on a :Neptune chipset - something that isn't known for speed. Once you get two :processors hammering the system bus, *plus* mix in an EISA scsi :controller, I could well imagine the memory bus getting thrashed. When we started throwing together Duel-P-II machines, we basically had to throw away our DEC chipset cards... I think that the DEC chip cards, at least the older ones, have serious PCI spec bugs that cause them to operate incorrectly on duel-cpu machines when more then one cpu is populated. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 19:13:22 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA28276 for freebsd-current-outgoing; Sat, 23 Jan 1999 19:13:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA28268 for ; Sat, 23 Jan 1999 19:13:20 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id WAA99269; Sat, 23 Jan 1999 22:19:24 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Sat, 23 Jan 1999 22:19:23 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Matthew Dillon cc: current@FreeBSD.ORG Subject: Re: 2Re: panic: found dirty cache page 0xf046f1c0 In-Reply-To: <199901240251.SAA57298@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 23 Jan 1999, Matthew Dillon wrote: > > : > :i have 'ed' driver and mine blows up as well. > : > :panic: found dirty cache page 0xf047ae60 > :Debugger("panic") > > Ok, so much for if_de being the cause. > > BTW, for anybody who doesn't want to wait for us to find the > bug, you can comment out the MADV_FREE code and that should > put a stop to it. The MADV_FREE code isn't broken, but it seems > to cause the bug to occur which is why *I* haven't commented > it out - I'd rather find the bug. > > Also, update your kernel trees and turn on the INVARIANTS options: > > options INVARIANTS > options INVARIANT_SUPPORT cvsup'd and added, i'm going to run the code for a bit hopefully to get you some output from the INVARIANTS. > :Is it safe to enable crashdumps on IDE disks yet? > > I don't know. > > I wasn't aware that there was a problem with crash dumps on > ide disks. There shouldn't be. Last 3 times i enabled it, it dumped on the wrong partition because it got confused about LBA mode, anyone have a suggestion to test to make sure it won't dump on my /usr instead of swap? (i don't have LBA enabled in my IDE disk flags 0xe0ffe0ff) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 19:34:39 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA00702 for freebsd-current-outgoing; Sat, 23 Jan 1999 19:34:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA00690; Sat, 23 Jan 1999 19:34:34 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.1/8.9.1) id EAA53279; Sun, 24 Jan 1999 04:34:05 +0100 (CET) (envelope-from des) To: Kazutaka YOKOTA Cc: peter@netplex.com.au, sos@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Death to LKM screen savers? (was: Re: HEADS UP: i386 a.out LKM support now an option..) References: <199901171925.DAA06456@spinner.netplex.com.au> <199901240255.LAA24094@zodiac.mech.utsunomiya-u.ac.jp> From: Dag-Erling Smorgrav Date: 24 Jan 1999 04:34:04 +0100 In-Reply-To: Kazutaka YOKOTA's message of "Sun, 24 Jan 1999 11:55:19 +0900" Message-ID: Lines: 9 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kazutaka YOKOTA writes: > What if we declare death to LKM screen savers and remove them from > the source tree? After all KLD screen savers are working well. Sure. I don't see any reason to keep them. I'll do the deed. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 20:03:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA04159 for freebsd-current-outgoing; Sat, 23 Jan 1999 20:03:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA04152 for ; Sat, 23 Jan 1999 20:03:01 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id UAA06282; Sat, 23 Jan 1999 20:02:50 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id UAA16514; Sat, 23 Jan 1999 20:02:49 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sat, 23 Jan 1999 20:02:49 -0800 (PST) Message-Id: <199901240402.UAA16514@vashon.polstra.com> To: veldy@visi.com Subject: Re: Failure to make buildworld on RELENG_3 Newsgroups: polstra.freebsd.current In-Reply-To: <36AA271C.1BCFA7B7@visi.com> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <36AA271C.1BCFA7B7@visi.com>, Thomas T. Veldhouse wrote: > It seems to be the same problem we have been having with current. > Should it be crypt stuff be backed out of here as well? > > ===> libpam/modules/pam_radius > ===> libpam/modules/pam_skey > ===> libpam/modules/pam_tacplus > ===> libpam/modules/pam_unix > ===> libpam/libpam > ld -o pam_static_modules.o -r -Bforcearchive pam_static.o > ../modules/pam_cleartext_pass_ok/libpam_cleart > ext_pass_ok.a ../modules/pam_kerberosIV/libpam_kerberosIV.a > ../modules/pam_radius/libpam_radius.a ../mod > ules/pam_skey/libpam_skey.a ../modules/pam_tacplus/libpam_tacplus.a > ../modules/pam_unix/libpam_unix.a > ../modules/pam_cleartext_pass_ok/libpam_cleartext_pass_ok.a(pam_cleartext_pass_ok.o): > Definition of symb > ol `_pam_sm_authenticate' (multiply defined) ... Did you use -DNOCLEAN in your make world? (Or is it in your /etc/make.conf file?) It looks like it. Otherwise, why did nothing get built in the various "modules" subdirectories. And are you sure all of your sources are up to date? I tested this stuff with a full make world on a -current ELF system. In addition, I tested libpam and login for all combinations of {{aout,elf}{dynamic linking,NOSHARED=yes}}. The relevant sources are identical in the RELENG_3 branch, except for the RCS $Id$ strings of course. I'd recommend doing a "make clean cleandepend" in "src/lib/libpam" and trying again. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 20:07:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA04711 for freebsd-current-outgoing; Sat, 23 Jan 1999 20:07:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA04702; Sat, 23 Jan 1999 20:06:54 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.1/8.9.1) id FAA53334; Sun, 24 Jan 1999 05:06:37 +0100 (CET) (envelope-from des) To: Dag-Erling Smorgrav Cc: Kazutaka YOKOTA , peter@netplex.com.au, sos@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Death to LKM screen savers? (was: Re: HEADS UP: i386 a.out LKM support now an option..) References: <199901171925.DAA06456@spinner.netplex.com.au> <199901240255.LAA24094@zodiac.mech.utsunomiya-u.ac.jp> From: Dag-Erling Smorgrav Date: 24 Jan 1999 05:06:35 +0100 In-Reply-To: Dag-Erling Smorgrav's message of "24 Jan 1999 04:34:04 +0100" Message-ID: Lines: 13 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav writes: > Kazutaka YOKOTA writes: > > What if we declare death to LKM screen savers and remove them from > > the source tree? After all KLD screen savers are working well. > Sure. I don't see any reason to keep them. I'll do the deed. Doh, they were already axed by sos in late December. 'cvs co src/lkm' still creates directories for them though. I'm sure someone with more CVS experience than me will be able to explain why :) DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 20:40:34 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA08410 for freebsd-current-outgoing; Sat, 23 Jan 1999 20:40:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA08405 for ; Sat, 23 Jan 1999 20:40:32 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id NAA18904; Sun, 24 Jan 1999 13:40:15 +0900 (JST) Message-ID: <36AAA3F8.14D589D8@newsguy.com> Date: Sun, 24 Jan 1999 13:39:20 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Pascal Hofstee CC: freebsd-current@FreeBSD.ORG Subject: Re: Bootstrap loader problems on CURRENT References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pascal Hofstee wrote: > > As of Today's 4.0-CURRENT My system Halts on boot-up after the BTX Driver > showing my BIOS-drives, with the following message: > > FreeBSD/i386 bootstrap loader, Revision 0.2 > (daeron@shadowmere..... etc...) > ficlExecFD: Error at line 1 > > then it shows a lot of Register-information with the message > > System halted > > this is when trying to execute boot/loader > > When I am fast enough on the Boot-Manager Boot-prompt .. I am able to > simply type /kernel instead of 0:wd(0,a)/boot/loader and my System Will > boot the 4.0-kernel and run fine. This is most likely my fault. The only place where ficlExecFD gets executed is during initialization, when loading /boot/boot.4th. What do you have there? I suppose you have no trouble booting if you rename that file, correct? I suspect you have a "builtin command" (those shown by ?) in the first line of that file, and with my recent changes, these commands have evidenced a bug in ficl, which I have been delaying dealing with until I get an answer from ficl's author. If that file is essential to you (and it's contents cannot be placed in loader.rc), I'll send you a patch that should get you going, for now. BTW, ficl's builtin command behavior got changed. I was avoiding bugging Mike to up loader's version (which is now available with "loader_version environment?") until I could change "include" to process fourth source, instead of just builtins, and *that* depends on the above mentioned bug getting fixed. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com If you sell your soul to the Devil and all you get is an MCSE from it, you haven't gotten market rate. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 21:01:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA10259 for freebsd-current-outgoing; Sat, 23 Jan 1999 21:01:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA10254 for ; Sat, 23 Jan 1999 21:01:09 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id VAA06440; Sat, 23 Jan 1999 21:00:58 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id VAA16698; Sat, 23 Jan 1999 21:00:58 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sat, 23 Jan 1999 21:00:58 -0800 (PST) Message-Id: <199901240500.VAA16698@vashon.polstra.com> To: des@flood.ping.uio.no Subject: Re: Death to LKM screen savers? (was: Re: HEADS UP: i386 a.out LKM support now an option..) Newsgroups: polstra.freebsd.current In-Reply-To: References: <199901171925.DAA06456@spinner.netplex.com.au> <199901240255.LAA24094@zodiac.mech.utsunomiya-u.ac.jp> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Dag-Erling Smorgrav wrote: > > Doh, they were already axed by sos in late December. 'cvs co src/lkm' > still creates directories for them though. I'm sure someone with more > CVS experience than me will be able to explain why :) Always use "-P" when you check out sources: "cvs co -P src/lkm". And when you update sources already checked out, use "cvs upd -Pd". John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 21:13:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA11461 for freebsd-current-outgoing; Sat, 23 Jan 1999 21:13:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA11452 for ; Sat, 23 Jan 1999 21:13:23 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id AAA99392; Sun, 24 Jan 1999 00:19:18 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Sun, 24 Jan 1999 00:19:18 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: John Polstra cc: des@flood.ping.uio.no, current@FreeBSD.ORG Subject: Re: Death to LKM screen savers? (was: Re: HEADS UP: i386 a.out LKM support now an option..) In-Reply-To: <199901240500.VAA16698@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 23 Jan 1999, John Polstra wrote: > In article , > Dag-Erling Smorgrav wrote: > > > > Doh, they were already axed by sos in late December. 'cvs co src/lkm' > > still creates directories for them though. I'm sure someone with more > > CVS experience than me will be able to explain why :) > > Always use "-P" when you check out sources: "cvs co -P src/lkm". > > And when you update sources already checked out, use "cvs upd -Pd". cvs up (not cvsup) takes me a LONG time to execute, i've been using '-z3' for comppression because i'm on dialup, is this ok with you guys? (it doesn't help much though...) cvs -z3 up -Pd src i'm also using ssh for transport as rlogin doesn't work well for me. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 21:31:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA13770 for freebsd-current-outgoing; Sat, 23 Jan 1999 21:31:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA13757 for ; Sat, 23 Jan 1999 21:31:45 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id AAA25860; Sun, 24 Jan 1999 00:30:05 -0500 (EST) Date: Sun, 24 Jan 1999 00:30:05 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Matthew Dillon cc: Alfred Perlstein , N , Peter Wemm , current@FreeBSD.ORG Subject: Re: 2Re: panic: found dirty cache page 0xf046f1c0 In-Reply-To: <199901240251.SAA57298@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 23 Jan 1999, Matthew Dillon wrote: > > : > :i have 'ed' driver and mine blows up as well. > : > :panic: found dirty cache page 0xf047ae60 > :Debugger("panic") > > Ok, so much for if_de being the cause. > > BTW, for anybody who doesn't want to wait for us to find the > bug, you can comment out the MADV_FREE code and that should > put a stop to it. The MADV_FREE code isn't broken, but it seems > to cause the bug to occur which is why *I* haven't commented > it out - I'd rather find the bug. > > Also, update your kernel trees and turn on the INVARIANTS options: > > options INVARIANTS > options INVARIANT_SUPPORT > > -Matt > Matthew Dillon > > > : > :btw, i'm hardly 'stressing' this machine it's a k6-233+96ram and > :i'm running X and doing a 'make release' > : > :Is it safe to enable crashdumps on IDE disks yet? > : > :-Alfred > > I don't know. > > I wasn't aware that there was a problem with crash dumps on > ide disks. There shouldn't be. > Crashdumps on IDE disks never stopped working for me. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 21:34:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA13931 for freebsd-current-outgoing; Sat, 23 Jan 1999 21:34:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles94.castles.com [208.214.165.94]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA13920 for ; Sat, 23 Jan 1999 21:34:17 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id VAA00483; Sat, 23 Jan 1999 21:30:07 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901240530.VAA00483@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Alfred Perlstein cc: John Polstra , des@flood.ping.uio.no, current@FreeBSD.ORG Subject: Re: Death to LKM screen savers? (was: Re: HEADS UP: i386 a.out LKM support now an option..) In-reply-to: Your message of "Sun, 24 Jan 1999 00:19:18 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 23 Jan 1999 21:30:07 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, 23 Jan 1999, John Polstra wrote: > > > In article , > > Dag-Erling Smorgrav wrote: > > > > > > Doh, they were already axed by sos in late December. 'cvs co src/lkm' > > > still creates directories for them though. I'm sure someone with more > > > CVS experience than me will be able to explain why :) > > > > Always use "-P" when you check out sources: "cvs co -P src/lkm". > > > > And when you update sources already checked out, use "cvs upd -Pd". > > cvs up (not cvsup) takes me a LONG time to execute, i've been using '-z3' > for comppression because i'm on dialup, is this ok with you guys? (it > doesn't help much though...) > > cvs -z3 up -Pd src > > i'm also using ssh for transport as rlogin doesn't work well for me. There's no point using ssh and -z3, just compress the ssh session. Also, you should try running in readonly (cvs -R) mode - locking is expensive. Finally, why not just use a local repository you weenie? 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 21:35:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA14076 for freebsd-current-outgoing; Sat, 23 Jan 1999 21:35:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from st-lcremean.tidalwave.net (st-lcremean.tidalwave.net [208.213.203.186]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA14036 for ; Sat, 23 Jan 1999 21:35:02 -0800 (PST) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.9.1/8.8.8) id AAA19589; Sun, 24 Jan 1999 00:32:26 -0500 (EST) (envelope-from lee) Message-ID: <19990124003226.A19245@tidalwave.net> Date: Sun, 24 Jan 1999 00:32:26 -0500 From: Lee Cremeans To: Matthew Dillon , Alfred Perlstein Cc: N , Peter Wemm , current@FreeBSD.ORG Subject: Re: 2Re: panic: found dirty cache page 0xf046f1c0 Reply-To: lcremean@tidalwave.net References: <199901240251.SAA57298@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199901240251.SAA57298@apollo.backplane.com>; from Matthew Dillon on Sat, Jan 23, 1999 at 06:51:54PM -0800 X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 23, 1999 at 06:51:54PM -0800, Matthew Dillon wrote: > : > :btw, i'm hardly 'stressing' this machine it's a k6-233+96ram and > :i'm running X and doing a 'make release' > : > :Is it safe to enable crashdumps on IDE disks yet? > : > :-Alfred > > I don't know. > > I wasn't aware that there was a problem with crash dumps on > ide disks. There shouldn't be. FWIW, I've had crash dumps enabled on my IDE-based system for a long time, and never had a problem with them. -- +--------------------------------------------------------------------+ | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)| | lcremean@tidalwave.net| http://st-lcremean.tidalwave.net/~lee | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 21:54:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15228 for freebsd-current-outgoing; Sat, 23 Jan 1999 21:54:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles94.castles.com [208.214.165.94]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA15223 for ; Sat, 23 Jan 1999 21:54:17 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id VAA00672; Sat, 23 Jan 1999 21:50:35 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901240550.VAA00672@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "D. Rock" cc: current@FreeBSD.ORG Subject: Re: dirty fs after apm power off In-reply-to: Your message of "Sat, 23 Jan 1999 22:44:31 +0100." <199901232144.WAA10840@wurzelausix.cs.uni-sb.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 23 Jan 1999 21:50:35 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have noticed this behaviour on at least one machine. > If I shutdown the machine with apm power off, the filesystem is dirty and > has to been checked on the next reboot. It seems, the power is cut too fast. > I don't have any problems with reboots. > It seems the drive doesn't have the time to write the superblock back to disk. > > I simply put a DELAY(4000000) in the apm_power_off() routine and the problem > fades away. > Any thoughts on doing this a configurable option? It doesn't break anything, > it only takes a few seconds longer for the machine to power off. > > The drive is a Maxtor Diamond Max (90432D2) 4GB IDE drive in an Asus SP98 > board. Ok, simple programming project for you. Find a suitable location, and add a SYSCTL node (eg. kern.shutdown.poweroff_delay) and SYSINIT to register an at_shutdown function that delays that long just before the power-off routines are called. Test it, file a PR and gimme the PR number. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 22:15:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA18009 for freebsd-current-outgoing; Sat, 23 Jan 1999 22:15:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA18004 for ; Sat, 23 Jan 1999 22:15:12 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id WAA60278; Sat, 23 Jan 1999 22:14:57 -0800 (PST) (envelope-from dillon) Date: Sat, 23 Jan 1999 22:14:57 -0800 (PST) From: Matthew Dillon Message-Id: <199901240614.WAA60278@apollo.backplane.com> To: current@FreeBSD.ORG Subject: Re: panic: found dirty cache page 0xf046f1c0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've committed one bug fix to the 'found dirty cache page' bug -- turns out vm_map_split() was the culprit, renaming pages without removing them from PQ_CACHE. The bug was introduced in -3.0, and hit the KASSERT() I put in -4.x. I've committed a general inlining of 'changing the page dirty status to VM_PAGE_BITS_ALL' and put a sanity check in the inline. If this problem occurs again, you will get a different panic. One of: vm_page_dirty: page in cache! vm_page_busy: page already busy!!! vm_page_wakeup: page not busy!!! If your box drops into DDB, please get a backtrace and report it to the list or to me and we should be able to track down any remaining dirty-pages-in-PQ_CACHE bugs. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 22:26:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA19502 for freebsd-current-outgoing; Sat, 23 Jan 1999 22:26:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA19497 for ; Sat, 23 Jan 1999 22:25:58 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id BAA99465; Sun, 24 Jan 1999 01:31:43 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Sun, 24 Jan 1999 01:31:43 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Mike Smith cc: John Polstra , des@flood.ping.uio.no, current@FreeBSD.ORG Subject: Re: Death to LKM screen savers? (was: Re: HEADS UP: i386 a.out LKM support now an option..) In-Reply-To: <199901240530.VAA00483@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 23 Jan 1999, Mike Smith wrote: > > > Always use "-P" when you check out sources: "cvs co -P src/lkm". > > > > > > And when you update sources already checked out, use "cvs upd -Pd". > > > > cvs up (not cvsup) takes me a LONG time to execute, i've been using '-z3' > > for comppression because i'm on dialup, is this ok with you guys? (it > > doesn't help much though...) > > > > cvs -z3 up -Pd src > > > > i'm also using ssh for transport as rlogin doesn't work well for me. > > There's no point using ssh and -z3, just compress the ssh session. > Also, you should try running in readonly (cvs -R) mode - locking is > expensive. > > Finally, why not just use a local repository you weenie? 8) Because, certain other weenies :) have web pages up on http://www.freebsd.org/handbook that don't explain how to do this, and aren't very clear on the topics that ARE discussed. :) so.... can i overlay my cvsup and my cvs trees somehow? this would be ideal. -Alfred "why did i buy that sparc again?" Perlstein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 22:30:42 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA19972 for freebsd-current-outgoing; Sat, 23 Jan 1999 22:30:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA19967 for ; Sat, 23 Jan 1999 22:30:41 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id BAA99480; Sun, 24 Jan 1999 01:36:45 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Sun, 24 Jan 1999 01:36:45 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Brian Feldman cc: current@FreeBSD.ORG Subject: Re: 2Re: panic: found dirty cache page 0xf046f1c0 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 24 Jan 1999, Brian Feldman wrote: > > :btw, i'm hardly 'stressing' this machine it's a k6-233+96ram and > > :i'm running X and doing a 'make release' > > : > > :Is it safe to enable crashdumps on IDE disks yet? > > : > > :-Alfred > > > > I don't know. > > > > I wasn't aware that there was a problem with crash dumps on > > ide disks. There shouldn't be. > > > > Crashdumps on IDE disks never stopped working for me. gee, that's nice to know. Brian, search the -current lists about this, there was/is some confusion in the driver about LBA. Basically, LBA would work at ALL times for the disk, except during a crash dump where it would use those addresses as CHS or something and cream one of my partitions. This lovely affected 2 seperate machines. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 23 23:52:02 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA27155 for freebsd-current-outgoing; Sat, 23 Jan 1999 23:52:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA27136 for ; Sat, 23 Jan 1999 23:52:00 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id CAA99712 for ; Sun, 24 Jan 1999 02:58:05 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Sun, 24 Jan 1999 02:58:05 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: current@FreeBSD.ORG Subject: dummynet causes crash? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG .(02:36:11)(root@bright.reserved) ipfw add pipe 1 ip from server to cvsup.freebsd.org (long pause i assume DNS) 00000 pipe 1 ip from 192.168.2.20 to 198.104.92.71 .(02:36:26)(root@bright.reserved) ~perlsta # ipfw pipe 1 config bw 18Kbit/s delay 20ms .(02:36:45)(root@bright.reserved) ~perlsta # ipfw l 00100 pipe 1 ip from 192.168.2.20 to 198.104.92.71 65535 allow ip from any to any .(02:36:52)(root@bright.reserved) ~perlsta # *BAM* Fatal trap 12: page fault while in kernel mode fault virtual address = 0xdeadc116 fault code = supervisor read, page not present ip = 0x8:0xf0193f37 sp = 0x10:0xf028409c fp = 0x10:0xf02840c8 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interupt enabled, resume, IOPL = 0 current process = idle interupt mask = net tty kernel: type 12 trap, code=0 Stopped at ether_output+0x4b: testb $0x1,0x38(%ebx) the only thing i can think of is that dummynet doesn't like not being told if a pipe is 'in' or 'out' :/ my ether card is a: ed card, a 'realteck 8029' Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 4.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message