From owner-freebsd-current Sun Dec 20 00:13:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA16922 for freebsd-current-outgoing; Sun, 20 Dec 1998 00:13: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 AAA16916 for ; Sun, 20 Dec 1998 00:13:11 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id AAA30210; Sun, 20 Dec 1998 00:13:09 -0800 (PST) (envelope-from dillon) Date: Sun, 20 Dec 1998 00:13:09 -0800 (PST) From: Matthew Dillon Message-Id: <199812200813.AAA30210@apollo.backplane.com> To: Don Lewis Cc: freebsd-current@FreeBSD.ORG Subject: Re: asleep()/await(), M_AWAIT, etc... References: <199812191115.DAA12134@salsa.gv.tsc.tdk.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :One case that I thought of could cause you to spin. : : lock object (succeeds) : MALLOC(..., M_AWAIT) (succeeds) : MALLOC(..., M_AWAIT) (fails) : :After the second MALLOC fails, you'll free the first chunk of memory allocated :and unlock the object. When you call await(), it'll succeed because memory :is available because of the memory that was just freed. The first MALLOC() :will succeed, and the second one will fail again. The way this code is :written, it looks like only two levels, but it really is 3 by your criteria :and thus is getting into questionable territory. Hmm. This could theoretically cause a problem but the hysteresis in the memory subsystem ought to handle most cases. Still, I can see a potential problem if the allocation is big enough (i.e. larger then a few pages). :} describe is precisely the already-existant situation that asleep() and :} await() can be used to fix. This might sound expensive, but most :} of the places where we would need to use asleep()/await() would not :} actually have to pop back more then a few subroutine levels to be :} effective. : :For pathname traversal, if you give up a lock, I think you have to restart :from the beginning. This one could be solved by allocating a forward-looking namei entry to placemark the blocked operation. So if you are traversing a/b/c/d and while holding b you miss c, you would allocate a namei record for c to placemark the I/O and release b, then block normally (i.e. just use tsleep()). This would prevent a cascade. I do not think there are any path-oriented syscalls that need to lock a vnode prior to resolving the path, so asleep()/await() would not be necessary anyway. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 20 00:33:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA17987 for freebsd-current-outgoing; Sun, 20 Dec 1998 00:33:53 -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 AAA17981 for ; Sun, 20 Dec 1998 00:33:47 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (IDENT:vioZr54jkEhkSBDhnsDMV4TRpWWwqae3@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id KAA16151; Sun, 20 Dec 1998 10:33:42 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:d++3WtRQ4+Ji/wt9OPUc/x9+F5A7Fn3q@localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id KAA89829; Sun, 20 Dec 1998 10:33:37 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199812200833.KAA89829@greenpeace.grondar.za> To: Bruce Albrecht cc: freebsd-current@FreeBSD.ORG Subject: Re: GDBM_File and base perl In-Reply-To: Your message of " Sat, 19 Dec 1998 23:22:16 CST." <13948.35208.923734.90525@zuhause.zuhause.mn.org> References: <13948.35208.923734.90525@zuhause.zuhause.mn.org> Date: Sun, 20 Dec 1998 10:33:36 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Albrecht wrote: > Is there any way in the base perl build to recognize that gdbm has > been installed in /usr/local and include it when building perl? > Since it's part of the base perl distribution, there's no tidy way to > add it after the fact with something from CPAN. No, But I have plans to add/kluge it onto the gdbm port (or something). 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 Dec 20 03:03:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA26126 for freebsd-current-outgoing; Sun, 20 Dec 1998 03:03:40 -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 DAA26026 for ; Sun, 20 Dec 1998 03:03:33 -0800 (PST) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 985 invoked by uid 100); 20 Dec 1998 11:12:22 -0000 Date: Sun, 20 Dec 1998 03:12:21 -0800 To: freebsd-current@FreeBSD.ORG Subject: USB, scanners, and SANE? Message-ID: <19981220031221.A972@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.94.17i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been poking around the USB website and seperatedly noted the addition of support for USB under -current. Reading the www.usb.org site I mostly got the sense of Plug&Pray. Basically, plug it in, don't worry be happy. My wife as a HP Scanjet 4100CXI on her PC running [censored]. I'd like to take a stab at getting it to work under FreeBSD. I'm not above writing code. SANE has support for HP scanners of both SCSI and parallel port versions. Via the existing FreeBSD USB support will it be possible for me to create a communication channel for the SANE backend to talk to the scanner? HIDs and Classes (was it?) have me worried that I have to wait for particular support for scanner class devices. But on the other hand, maybe this is not that case, and perhaps I can use some generic interface to access the scanner. Any pointers or clarification on the FreeBSD USB interface would be appreciated. -- Brian Litzinger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 20 03:13:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA27530 for freebsd-current-outgoing; Sun, 20 Dec 1998 03:13:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles356.castles.com [208.214.167.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA27514 for ; Sun, 20 Dec 1998 03:13:18 -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 DAA43197; Sun, 20 Dec 1998 03:09:44 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812201109.DAA43197@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: brian@worldcontrol.com cc: freebsd-current@FreeBSD.ORG Subject: Re: USB, scanners, and SANE? In-reply-to: Your message of "Sun, 20 Dec 1998 03:12:21 PST." <19981220031221.A972@top.worldcontrol.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 20 Dec 1998 03:09:34 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've been poking around the USB website and seperatedly > noted the addition of support for USB under -current. > > Reading the www.usb.org site I mostly got the sense of Plug&Pray. > Basically, plug it in, don't worry be happy. > > My wife as a HP Scanjet 4100CXI on her PC running [censored]. > > I'd like to take a stab at getting it to work under FreeBSD. > I'm not above writing code. > > SANE has support for HP scanners of both SCSI and parallel port > versions. > > Via the existing FreeBSD USB support will it be possible for me > to create a communication channel for the SANE backend to talk > to the scanner? "a SANE backend", which someone will have to write. > HIDs and Classes (was it?) have me worried that I have to wait > for particular support for scanner class devices. But on the > other hand, maybe this is not that case, and perhaps I can use > some generic interface to access the scanner. You'll have to write a scanner class driver, yes. You *may* have to write scanner-specific code as well, depending on how nicely the scanner plays, and how useful the generic scanner class is (I haven't seen a document for it yet). > Any pointers or clarification on the FreeBSD USB interface > would be appreciated. Right now, the code is your friend. I think Nick is on the road for Christmas, but I could be wrong there. There are a couple of class drivers already implemented, so you've certainly got something to start with at least. -- \\ 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 Dec 20 04:00:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA03443 for freebsd-current-outgoing; Sun, 20 Dec 1998 04:00:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from newsguy.com (smtp.newsguy.com [207.211.168.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA03433 for ; Sun, 20 Dec 1998 04:00:13 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (tc-1-170.urawa.gol.ne.jp [203.216.60.170]) by newsguy.com (8.9.1a/8.9.1) with ESMTP id DAA05129; Sun, 20 Dec 1998 03:59:57 -0800 (PST) Message-ID: <367CE5E0.D2ACFAE2@newsguy.com> Date: Sun, 20 Dec 1998 20:56:16 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Andrzej Bialecki CC: freebsd-current@FreeBSD.ORG Subject: Re: BootFORTH - demo floppy References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki wrote: > > The built-ins I was talking about are the original bootloader commands, > such as set, show, load, boot, reboot, pnpscan, ls etc..., which need > closer integrations with Forth engine. Namely, they should recognize the > state (either interpretive, or compiling), and be able to accept > parameters either from command line (like: "load -t userconfig_script > kernel.config" when interpreting), or from the stack (like: > > s" kernel.config" > s" userconfig_script" > s" -t" > load > > when compiling). As it is now, we cannot use the full Forth power to > program booting behaviour because of this deficiency. Well, aside from being... well... ugly, you _can_ wrap it like: 80 constant Buffersize Create Buffer Buffersize allot : cat >r over >r \ save sizes dup >r \ save original append position swap move \ append r> r@ + \ skip newly added string bl over c! \ add a space... 1+ \ ...and skip it r> r> + 1+ \ new size ; : concatenate_command_and_arguments >r \ Save number of strings buffer 0 \ Destination of copy r> 0 do \ Copy all strings cat loop 0 rot c! \ Null-terminate the buffer, because of problems with evaluate Buffer swap \ return begin-of-buffer, size ; : insert_command rot 1+ ; : wrapper insert_command concatenate_command_and_arguments evaluate ; : wrap" postpone s" postpone wrapper ; immediate And then do: > s" kernel.config" > s" userconfig_script" > s" -t" 3 > wrap" load" in compile mode (inside a definition). I'll see what I can do after I get the source, but that will have to wait a new hd. Meanwhile... 1) Could someone please add a key pause to "words"? :-) 2) Could someone please add the 30-years old traditional "ok" prompt in interpreting mode? 3) I noticed "evaluate" is working with null-ended string, ignoring completely the count on the stack. Not good. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com "This never happened to the other fellow!" - The second James Bond To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 20 04:00:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA03472 for freebsd-current-outgoing; Sun, 20 Dec 1998 04:00:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from newsguy.com (smtp.newsguy.com [207.211.168.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA03464 for ; Sun, 20 Dec 1998 04:00:54 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (tc-1-170.urawa.gol.ne.jp [203.216.60.170]) by newsguy.com (8.9.1a/8.9.1) with ESMTP id EAA05189; Sun, 20 Dec 1998 04:00:33 -0800 (PST) Message-ID: <367CE654.CCB48556@newsguy.com> Date: Sun, 20 Dec 1998 20:58:12 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Andrzej Bialecki CC: freebsd-current@FreeBSD.ORG Subject: Re: BootFORTH - demo floppy References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki wrote: > > The built-ins I was talking about are the original bootloader commands, > such as set, show, load, boot, reboot, pnpscan, ls etc..., which need > closer integrations with Forth engine. Namely, they should recognize the > state (either interpretive, or compiling), and be able to accept > parameters either from command line (like: "load -t userconfig_script > kernel.config" when interpreting), or from the stack (like: > > s" kernel.config" > s" userconfig_script" > s" -t" > load > > when compiling). As it is now, we cannot use the full Forth power to > program booting behaviour because of this deficiency. Well, aside from being... well... ugly, you _can_ wrap it like: 80 constant Buffersize Create Buffer Buffersize allot : cat >r over >r \ save sizes dup >r \ save original append position swap move \ append r> r@ + \ skip newly added string bl over c! \ add a space... 1+ \ ...and skip it r> r> + 1+ \ new size ; : concatenate_command_and_arguments >r \ Save number of strings buffer 0 \ Destination of copy r> 0 do \ Copy all strings cat loop 0 rot c! \ Null-terminate the buffer, because of problems with evaluate Buffer swap \ return begin-of-buffer, size ; : insert_command rot 1+ ; : wrapper insert_command concatenate_command_and_arguments evaluate ; : wrap" postpone s" postpone wrapper ; immediate And then do: > s" kernel.config" > s" userconfig_script" > s" -t" 3 > wrap" load" in compile mode (inside a definition). I'll see what I can do after I get the source, but that will have to wait a new hd. Meanwhile... 1) Could someone please add a key pause to "words"? :-) 2) Could someone please add the 30-years old traditional "ok" prompt in interpreting mode? 3) I noticed "evaluate" is working with null-ended string, ignoring completely the count on the stack. Not good. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com "This never happened to the other fellow!" - The second James Bond To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 20 06:12:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA13740 for freebsd-current-outgoing; Sun, 20 Dec 1998 06:12:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA13735 for ; Sun, 20 Dec 1998 06:12:20 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id LAA18795; Sun, 20 Dec 1998 11:54:48 +0100 From: Luigi Rizzo Message-Id: <199812201054.LAA18795@labinfo.iet.unipi.it> Subject: Re: USB, scanners, and SANE? To: brian@worldcontrol.com Date: Sun, 20 Dec 1998 11:54:48 +0100 (MET) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <19981220031221.A972@top.worldcontrol.com> from "brian@worldcontrol.com" at Dec 20, 98 03:12:02 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > SANE has support for HP scanners of both SCSI and parallel port > versions. note (from the SANE pages) that parallel port support is limited to a models with a proprietary interface :( luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 20 09:12:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA29479 for freebsd-current-outgoing; Sun, 20 Dec 1998 09:12:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from salmon.hei.net (salmon.hei.net [209.222.163.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA29466 for ; Sun, 20 Dec 1998 09:12:50 -0800 (PST) (envelope-from john@hei.net) Received: from trout (hst-trout.hei.net [209.222.163.131]) by salmon.hei.net (8.8.8/8.8.5) with SMTP id JAA05336; Sun, 20 Dec 1998 09:12:33 -0800 (PST) From: "John Hengstler" To: "Mike Jackson" Cc: Subject: RE: Buildworld fails Date: Sun, 20 Dec 1998 09:45:18 -0800 Message-ID: <000001be2c40$8231e670$83a3ded1@trout.heicomm.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: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I added the noatime,async options to my /usr and rebooted, Everything Built and installed correctly.... So why would these options need to be added in order for the builds to work? In any case, thanks for the help. John > -----Original Message----- > From: owner-freebsd-current@FreeBSD.ORG > [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of Mike Jackson > Sent: Friday, December 18, 1998 8:14 PM > To: Alfred Perlstein > Cc: John A. Hengstler; freebsd-current@FreeBSD.ORG > Subject: Re: Buildworld fails > > > > > On Fri, 18 Dec 1998, Alfred Perlstein wrote: > > > > > On Fri, 18 Dec 1998, John A. Hengstler wrote: > > > > > Normally I would agree with this, except, 2.2.8 make buildworlds and > > > installworlds, work fine on same machine.. > > > > > > > hmmm, are you thrashing at all? how is your memory/swap? > maybe you have > > dying deamons, but with regular processes? > > > > can you successfully do a non-parallel build? > > > > Why don't you see what happens when you mount /usr with softupdates? Let > me guess, the build has been going on for quite some time before it dies? > Also, are you running X Windows at the same time as doing the make world? > Which would cause you to start swapping. > > I've seen the problems you describe on my machine, but have been able to > get around them by mounting /usr with softupdates/noatime and not using > the box when the world is being built (hence, very little swap space is > used). > > Mike > > > 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 Dec 20 10:31:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA06897 for freebsd-current-outgoing; Sun, 20 Dec 1998 10:31:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA06891 for ; Sun, 20 Dec 1998 10:31:09 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.56.64]) by smtp03.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA1895 for ; Sun, 20 Dec 1998 19:31:06 +0100 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: Sun, 20 Dec 1998 19:37:25 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: FreeBSD Current Subject: Problem with SCSI-bus and high diskaccess? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I just want some thoughts on this: In the last 24 hours my workstation is been going nuts, whereas it has been running along nicely for weeks before. The things that kept me bugging today were these happy messages: Dec 20 10:51:14 chronias /kernel: Unexpected busfree. LASTPHASE == 0xa0 Dec 20 10:51:15 chronias /kernel: SEQADDR == 0x157 Dec 20 10:51:15 chronias /kernel: (da1:ahc0:0:1:0): SCB 0x5 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0xc Dec 20 10:51:15 chronias /kernel: (da1:ahc0:0:1:0): Queuing a BDR SCB Dec 20 10:51:15 chronias /kernel: (da1:ahc0:0:1:0): Bus Device Reset Message Sent Dec 20 10:51:15 chronias /kernel: (da1:ahc0:0:1:0): no longer in timeout, status = 353 After which page and swap process were running wild. The weird thing is, these HD's (two SCSI Quantum Fireballs) have been checked, the HA (AHA 2940UW) is likewise in good shape and the memory chips have been tested as well... The mainboard is also in good shape and is cooled by a few fans (3) which all work, including the one on the CPU. The circumstances when this happened was when I did a locate.updatedb at the same time as downloading a PDF file to the HD, and then I opened a mailbox at which time the whole time went haywire... Unfortunately I wasn't able to write down the pager messages since they went by with warpspeed 9 and they weren't logged in /var/log/messages =\ Does anybody have any ideas what to check to narrow down the problem? --- Jeroen Ruigrok van der Werven Life is the only Pain asmodai(at)wxs.nl we endeavour... Network/Security Specialist BSD & picoBSD: 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 Dec 20 13:58:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26062 for freebsd-current-outgoing; Sun, 20 Dec 1998 13:58:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from esmeralda.xaa.iae.nl (esmeralda.xaa.iae.nl [194.151.75.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA26057 for ; Sun, 20 Dec 1998 13:58:27 -0800 (PST) (envelope-from freebsd@xaa.iae.nl) Received: from ariel.xaa.iae.nl (ariel.xaa.iae.nl [194.151.75.10]) by esmeralda.xaa.iae.nl (Postfix) with ESMTP id 2E5741E9; Sun, 20 Dec 1998 22:58:20 +0100 (MET) Received: by ariel.xaa.iae.nl (Postfix, from userid 1008) id 694FB3EBE; Sun, 20 Dec 1998 22:58:09 +0100 (CET) Date: Sun, 20 Dec 1998 22:58:09 +0100 From: Mark Huizer To: current@FreeBSD.ORG Subject: current problem -> process hanging on 'inode' state... Message-ID: <19981220225809.A1503@ariel.xaa.iae.nl> 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 Hi, my fileserver (running Current as of yesterday), is showing weird things, not sure if it's a problem with current or something bad in my fs. anyway: with intensive jobs like tar -cf - /, after a non-deterministic amount of time the process will hang, top showing that it is in the 'inode' blocked queue. Then other processes will start hanging too, making the machine useless. Weird thing: it will go on playing NFS-server without problems. Just starting new programs is impossible, ctrl-alt-del won't work, etc... config: single processor machine, using soft updates, used to run smoothly for weeks, now hangs on most really big disk jobs. Strange enough it seems to survive a make world. Does it ring a bel to anyone? -- Nice testing in little China... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 20 14:01:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA26548 for freebsd-current-outgoing; Sun, 20 Dec 1998 14:01:51 -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 OAA26537; Sun, 20 Dec 1998 14:01:48 -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 QAA06645; Sun, 20 Dec 1998 16:56:43 -0500 (EST) (envelope-from lee) Message-ID: <19981220165642.A6616@tidalwave.net> Date: Sun, 20 Dec 1998 16:56:42 -0500 From: Lee Cremeans To: Julian Elischer , lcremean@tidalwave.net Cc: Howard , current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c Reply-To: lcremean@tidalwave.net References: <19981219134118.A311@tidalwave.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Julian Elischer on Sat, Dec 19, 1998 at 11:48:49PM -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, Dec 19, 1998 at 11:48:49PM -0800, Julian Elischer wrote: > Whistle has some support for Cyrix 5530 UltraDMA support that will come in > when cleaned up. Hm, cool. I wonder if it's at all similar to the Acer UDMA engine, which btw I seem to have at least partially working at this point. (Streaming transfers -- i.e. dd if=/dev/rwd0 of=/dev/null -- work, but if you, say, run fsck or boot the system multi-user, it'll work fine for a few seconds, then get some interrupt timeouts, then work again for a bit, then the cycle repeats. I think the UDMA cycle time needs to be tweaked, but I'm not sure.) > Unfortunatly the 5530 UDMA engine has some serious bugs. > some of which can't be worked around from ide_pci.c alone.. Eeee, like what? -- +--------------------------------------------------------------------+ | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)| | lcremean@tidalwave.net| http://st-lcremean.tidalwave.net | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 20 14:29:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29279 for freebsd-current-outgoing; Sun, 20 Dec 1998 14:29: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 OAA29273; Sun, 20 Dec 1998 14:29:29 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id OAA05895; Sun, 20 Dec 1998 14:24:56 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdzu5891; Sun Dec 20 22:24:47 1998 Date: Sun, 20 Dec 1998 14:24:43 -0800 (PST) From: Julian Elischer To: lcremean@tidalwave.net cc: Howard , current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c In-Reply-To: <19981220165642.A6616@tidalwave.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 Sun, 20 Dec 1998, Lee Cremeans wrote: > On Sat, Dec 19, 1998 at 11:48:49PM -0800, Julian Elischer wrote: > > Whistle has some support for Cyrix 5530 UltraDMA support that will come in > > when cleaned up. > > Hm, cool. I wonder if it's at all similar to the Acer UDMA engine, which btw > I seem to have at least partially working at this point. (Streaming > transfers -- i.e. dd if=/dev/rwd0 of=/dev/null -- work, but if you, say, run > fsck or boot the system multi-user, it'll work fine for a few seconds, then > get some interrupt timeouts, then work again for a bit, then the cycle > repeats. I think the UDMA cycle time needs to be tweaked, but I'm not sure.) > > > > Unfortunatly the 5530 UDMA engine has some serious bugs. > > some of which can't be worked around from ide_pci.c alone.. > > Eeee, like what? > > -- > +--------------------------------------------------------------------+ > | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)| > | lcremean@tidalwave.net| http://st-lcremean.tidalwave.net | > > > try: limit the maximum transfer in param.h to 64KB (It's presently 128KB) try: altering ide_pci_dmaverify to not allow DMA on transfers not on 16 (or larger) byte boundaries. (presently only dissallows odd transfers) try: removing the following code from ide_pci.c /* * Coalesce if physically contiguous and not crossing * 64k boundary. */ if ((prd_base + prd_count == nbase) && ((((nend - 1) ^ prd_base) & ~0xffff) == 0)) { prd_count += ncount; } else try: the following change in wd.c: (note mail will have munged this. do it by hand) *** wd.c 1998/07/13 08:23:01 1.172 --- wd.c 1998/11/18 01:04:50 *************** *** 1253,1260 **** if (du->dk_flags & (DKFL_DMA|DKFL_USEDMA)) { /* XXX SMP boxes sometimes generate an early intr. Why? */ if((wddma[du->dk_interface].wdd_dmastatus(du->dk_dmacookie) & WDDS_INTERRUPT) ! == 0) ! return; dmastat = wddma[du->dk_interface].wdd_dmadone(du->dk_dmacookie); } --- 1263,1269 ---- if (du->dk_flags & (DKFL_DMA|DKFL_USEDMA)) { /* XXX SMP boxes sometimes generate an early intr. Why? */ if((wddma[du->dk_interface].wdd_dmastatus(du->dk_dmacookie) & WDDS_INTERRUPT) ! != 0) dmastat = wddma[du->dk_interface].wdd_dmadone(du->dk_dmacookie); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 20 15:50:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07664 for freebsd-current-outgoing; Sun, 20 Dec 1998 15:50:27 -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 PAA07655 for ; Sun, 20 Dec 1998 15:50:20 -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 AAA20588 for freebsd-current@FreeBSD.ORG; Mon, 21 Dec 1998 00:50:15 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 4151C1513; Mon, 21 Dec 1998 00:03:30 +0100 (CET) Date: Mon, 21 Dec 1998 00:03:30 +0100 From: Ollivier Robert To: "FreeBSD Current Users' list" Subject: Pb with COMPAT_LINUX_THREADS Message-ID: <19981221000330.A6587@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#4871 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I synced my sources with CTM delta #4910 (from 1998/12/20 08:11:37) and ran 'make world". After that, I built a kernel with COMPAT_LINUX_THREADS defined and now get this: 201 [23:58] roberto@tara:~> ps ax ps: proc size mismatch (16416 total, 672 chunks) Something is probably missing although adding "-DCOMPAT_LINUX_THREADS" to ps Makefile CFLAGS didn't help. Any idea ? FreeBSD tara 3.0-CURRENT FreeBSD 3.0-CURRENT #7: Sun Dec 20 14:42:57 CET 1998 roberto@tara:/src/src/sys/compile/TARA_SMP i386 -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #2: Sun Nov 8 01:22:20 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 Dec 20 16:26:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA12078 for freebsd-current-outgoing; Sun, 20 Dec 1998 16:26:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles336.castles.com [208.214.167.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA12069 for ; Sun, 20 Dec 1998 16:26: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 QAA47845; Sun, 20 Dec 1998 16:23:49 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812210023.QAA47845@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel C. Sobral" cc: Andrzej Bialecki , freebsd-current@FreeBSD.ORG Subject: Re: BootFORTH - demo floppy In-reply-to: Your message of "Sun, 20 Dec 1998 20:58:12 +0900." <367CE654.CCB48556@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 20 Dec 1998 16:23:48 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'll see what I can do after I get the source, but that will have to > wait a new hd. Meanwhile... > > 2) Could someone please add the 30-years old traditional > "ok" prompt in interpreting mode? The prompt is fully configurable; set it yourself if that's what you want. > 3) I noticed "evaluate" is working with null-ended string, ignoring > completely the count on the stack. Not good. Is this an implementation feature? Does the count on the stack ever not match the length of the string? -- \\ 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 Dec 20 19:38:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27538 for freebsd-current-outgoing; Sun, 20 Dec 1998 19:38:30 -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 TAA27529 for ; Sun, 20 Dec 1998 19:38:27 -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 WAA00355; Sun, 20 Dec 1998 22:38:14 -0500 (EST) (envelope-from lee) Message-ID: <19981220223813.A268@tidalwave.net> Date: Sun, 20 Dec 1998 22:38:13 -0500 From: Lee Cremeans To: Ollivier Robert , current@FreeBSD.ORG Subject: Re: Pb with COMPAT_LINUX_THREADS Reply-To: lcremean@tidalwave.net References: <19981221000330.A6587@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19981221000330.A6587@keltia.freenix.fr>; from Ollivier Robert on Mon, Dec 21, 1998 at 12:03:30AM +0100 X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 21, 1998 at 12:03:30AM +0100, Ollivier Robert wrote: > I synced my sources with CTM delta #4910 (from 1998/12/20 08:11:37) and ran > 'make world". After that, I built a kernel with COMPAT_LINUX_THREADS > defined and now get this: > > 201 [23:58] roberto@tara:~> ps ax > ps: proc size mismatch (16416 total, 672 chunks) > When you see this, it usually means libkvm needs to be rebuilt. Do that, then rebuild everything that uses it (ps, top, systat, several others). -- +--------------------------------------------------------------------+ | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)| | lcremean@tidalwave.net| http://st-lcremean.tidalwave.net | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 20 19:52:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA28598 for freebsd-current-outgoing; Sun, 20 Dec 1998 19:52:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from calvin.saturn-tech.com (calvin.saturn-tech.com [207.229.19.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA28593 for ; Sun, 20 Dec 1998 19:52:06 -0800 (PST) (envelope-from drussell@saturn-tech.com) Received: from localhost (drussell@localhost) by calvin.saturn-tech.com (8.8.8/8.8.8) with SMTP id UAA25962; Sun, 20 Dec 1998 20:51:27 -0700 (MST) (envelope-from drussell@saturn-tech.com) Date: Sun, 20 Dec 1998 20:51:27 -0700 (MST) From: Doug Russell To: Julian Elischer cc: current@FreeBSD.ORG Subject: Re: Appologies about commit screwup 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 > Considering how much I didn't want to screw up this one it's really quite > amazing how much it was screwed up. Doesn't everything always work that way? :) Later...... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 20 20:08:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA00378 for freebsd-current-outgoing; Sun, 20 Dec 1998 20:08:22 -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 UAA00373 for ; Sun, 20 Dec 1998 20:08:21 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id UAA11838; Sun, 20 Dec 1998 20:04:41 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdz11835; Mon Dec 21 04:04:34 1998 Date: Sun, 20 Dec 1998 20:04:31 -0800 (PST) From: Julian Elischer To: Ollivier Robert cc: "FreeBSD Current Users' list" Subject: Re: Pb with COMPAT_LINUX_THREADS In-Reply-To: <19981221000330.A6587@keltia.freenix.fr> 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 you need to recompile libkvm with the same options On Mon, 21 Dec 1998, Ollivier Robert wrote: > I synced my sources with CTM delta #4910 (from 1998/12/20 08:11:37) and ran > 'make world". After that, I built a kernel with COMPAT_LINUX_THREADS > defined and now get this: > > 201 [23:58] roberto@tara:~> ps ax > ps: proc size mismatch (16416 total, 672 chunks) > > Something is probably missing although adding "-DCOMPAT_LINUX_THREADS" to > ps Makefile CFLAGS didn't help. > > Any idea ? > > FreeBSD tara 3.0-CURRENT FreeBSD 3.0-CURRENT #7: Sun Dec 20 14:42:57 CET > 1998 roberto@tara:/src/src/sys/compile/TARA_SMP i386 > > -- > Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr > FreeBSD keltia.freenix.fr 3.0-CURRENT #2: Sun Nov 8 01:22:20 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 Sun Dec 20 20:47:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA02689 for freebsd-current-outgoing; Sun, 20 Dec 1998 20:47:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from daphne.bogus (dialup6.black-hole.com [206.145.13.26]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA02684 for ; Sun, 20 Dec 1998 20:47:02 -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 XAA30152; Sun, 20 Dec 1998 23:46:37 -0600 (CST) (envelope-from hank@black-hole.com) X-Authentication-Warning: daphne.bogus: hank owned process doing -bs Date: Sun, 20 Dec 1998 23:46:37 -0600 (CST) From: Henry Miller X-Sender: hank@daphne.bogus To: brian@worldcontrol.com cc: freebsd-current@FreeBSD.ORG Subject: Re: USB, scanners, and SANE? In-Reply-To: <19981220031221.A972@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 This was discussed on the sane mailing lists last month, and the concessious was USB support is desirable, but today there are several problems. a) nobody with an interest in writting a scanner backend has a USB scanner, b) the lack of stable implimentations of USB and unix. a) is the biggest thing getting in the way, but that is expected to change over the next year or so. I encourage you to get involved and write the backend. b) will be a big deal. The goal is to have standard functions for accessing the USB port, similear to what sane does for scsi. Before work in that direction can procede the operating systems SANE runs on need USB support. NetBSD is the only one that has USB support. FreeBSD and Linux were both noted as making progress, but not yet to the point where anyone can truely belive that they won't change their API 10 times a month for the next few months. Obviously things will settle down (and probably won't get that bad) but today the implimentation isn't truely ready for others to write protable programs on top of. on the other hand, b) should be solved in the next few months. (and if you read -current you probably know the state of USB in freeBSD, which is progressing nicely) Once the OS level implimentations are stable, SANE will write a wrapper API, and then things will be ready for a backends. You can short circuite this process, like the parrell drivers do, but remember that parrell scanners are generally unsupported, and considering manufactures additude always will be. USB scanners probably will be supported, therefore if you write something plan time to re-write it to a standard when sane releases one. Good luck! On Sun, 20 Dec 1998 brian@worldcontrol.com wrote: > I've been poking around the USB website and seperatedly > noted the addition of support for USB under -current. > > Reading the www.usb.org site I mostly got the sense of Plug&Pray. > Basically, plug it in, don't worry be happy. > > My wife as a HP Scanjet 4100CXI on her PC running [censored]. > > I'd like to take a stab at getting it to work under FreeBSD. > I'm not above writing code. > > SANE has support for HP scanners of both SCSI and parallel port > versions. > > Via the existing FreeBSD USB support will it be possible for me > to create a communication channel for the SANE backend to talk > to the scanner? > > HIDs and Classes (was it?) have me worried that I have to wait > for particular support for scanner class devices. But on the > other hand, maybe this is not that case, and perhaps I can use > some generic interface to access the scanner. > > Any pointers or clarification on the FreeBSD USB interface > would be appreciated. > > -- > Brian Litzinger > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- http://blugill.home.ml.org/ 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 Sun Dec 20 23:10:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA15140 for freebsd-current-outgoing; Sun, 20 Dec 1998 23:10:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shell2.la.best.com (shell2.la.best.com [209.24.216.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA15135 for ; Sun, 20 Dec 1998 23:10:43 -0800 (PST) (envelope-from nugundam@shell2.la.best.com) Received: from localhost (nugundam@localhost) by shell2.la.best.com (8.9.1/8.9.0/best.sh) with ESMTP id XAA00268 for ; Sun, 20 Dec 1998 23:10:40 -0800 (PST) Date: Sun, 20 Dec 1998 23:10:40 -0800 (PST) From: Joseph Lee To: freebsd-current@FreeBSD.ORG Subject: linking against libc_r 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 How do I link against libc_r instead of libc? Trying to build wine from the latest sources, and the configure complains about libc being non-reentrant, which is what libc_r is for, from what I've read. tia, -- Joseph nugundam =best=com==/==\=IIGS=/==\=Playstation=/==\=Civic HX CVT=/==\ # Anime Expo 1998 >> www.anime-expo.org/ > # Redline Games >> www.redlinegames.com/ > # Cal-Animage Epsilon >> www.best.com/~nugundam/epsilon/ > # EX: The Online World of Anime & Manga >> www.ex.org/ / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 20 23:49:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA18606 for freebsd-current-outgoing; Sun, 20 Dec 1998 23:49:22 -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 XAA18600 for ; Sun, 20 Dec 1998 23:49:19 -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 IAA05834 for freebsd-current@FreeBSD.ORG; Mon, 21 Dec 1998 08:49:14 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 78BBF1513; Mon, 21 Dec 1998 08:43:26 +0100 (CET) Date: Mon, 21 Dec 1998 08:43:26 +0100 From: Ollivier Robert To: "FreeBSD Current Users' list" Subject: Re: Pb with COMPAT_LINUX_THREADS Message-ID: <19981221084326.A9987@keltia.freenix.fr> Mail-Followup-To: FreeBSD Current Users' list References: <19981221000330.A6587@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Julian Elischer on Sun, Dec 20, 1998 at 08:04:31PM -0800 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4871 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Julian Elischer: > you need to recompile libkvm with the same options OK, that is working now. It should have been documented somewhere Julian :-) We need to find a way to make this kind of changes propagate through the rest of "make world"... if there is one. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #2: Sun Nov 8 01:22:20 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 00:07:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA19749 for freebsd-current-outgoing; Mon, 21 Dec 1998 00:07:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles336.castles.com [208.214.167.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA19742 for ; Mon, 21 Dec 1998 00:07: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 AAA50444; Mon, 21 Dec 1998 00:00:20 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812210800.AAA50444@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Ollivier Robert cc: "FreeBSD Current Users' list" Subject: Re: Pb with COMPAT_LINUX_THREADS In-reply-to: Your message of "Mon, 21 Dec 1998 08:43:26 +0100." <19981221084326.A9987@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Dec 1998 00:00:19 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > According to Julian Elischer: > > you need to recompile libkvm with the same options > > OK, that is working now. It should have been documented somewhere Julian > :-) > > We need to find a way to make this kind of changes propagate through the > rest of "make world"... if there is one. Remove the COMPAT_LINUX_THREADS #ifdefs. -- \\ 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 Dec 21 00:15:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA20615 for freebsd-current-outgoing; Mon, 21 Dec 1998 00:15:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA20610 for ; Mon, 21 Dec 1998 00:15:09 -0800 (PST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id JAA28678 for ; Mon, 21 Dec 1998 09:15:04 +0100 (MET) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma028675; Mon, 21 Dec 98 09:15:05 +0100 Received: from dibbs1.eur.cis.philips.com (dibbs1.eur.cis.philips.com [130.139.33.66]) by smtprelay-nl1.philips.com (8.8.5/8.6.10-1.2.2m-970826) with ESMTP id JAA25868 for ; Mon, 21 Dec 1998 09:15:02 +0100 (MET) Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by dibbs1.eur.cis.philips.com (8.8.8/8.8.8) with SMTP id JAA14207 for ; Mon, 21 Dec 1998 09:15:01 +0100 (MET) Received: (qmail 82761 invoked by uid 666); 21 Dec 1998 08:15:21 -0000 Date: Mon, 21 Dec 1998 09:15:21 +0100 From: Jos Backus To: freebsd-current@FreeBSD.ORG Subject: Interesting panic: Shouldn't get here! Message-ID: <19981221091521.A82746@hal.mpn.cp.philips.com> Reply-To: Jos Backus 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 Good morning all, This is with yesterday's world and today's kernel. The panic occurs in kern/init_main.c(274). Should I file a PR? Cheers, -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 00:29:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA22155 for freebsd-current-outgoing; Mon, 21 Dec 1998 00:29:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles336.castles.com [208.214.167.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA22150 for ; Mon, 21 Dec 1998 00:29:42 -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 AAA50600; Mon, 21 Dec 1998 00:27:22 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812210827.AAA50600@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Jos Backus cc: freebsd-current@FreeBSD.ORG Subject: Re: Interesting panic: Shouldn't get here! In-reply-to: Your message of "Mon, 21 Dec 1998 09:15:21 +0100." <19981221091521.A82746@hal.mpn.cp.philips.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Dec 1998 00:27:21 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Good morning all, > > This is with yesterday's world and today's kernel. The panic occurs in > kern/init_main.c(274). Should I file a PR? No, and particularly not with that singular lack of any useful information. -- \\ 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 Dec 21 00:41:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA23222 for freebsd-current-outgoing; Mon, 21 Dec 1998 00:41:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from newsguy.com (smtp.newsguy.com [207.211.168.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA23215 for ; Mon, 21 Dec 1998 00:41:44 -0800 (PST) (envelope-from dcsobral@newsguy.com) Received: (from dcsobral@localhost) by newsguy.com (8.9.1a/8.9.1) id AAA07194; Mon, 21 Dec 1998 00:41:02 -0800 (PST) Date: Mon, 21 Dec 1998 00:41:02 -0800 (PST) Message-Id: <199812210841.AAA07194@newsguy.com> X-Mailer: Direct Read Email by Newsguy News Service To: mike@smith.net.au From: "Daniel C. Sobral" Subject: Re: BootFORTH - demo floppy Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Sun, 20 Dec 1998 16:23:48 -0800, you wrote >> >> 2) Could someone please add the 30-years old traditional >> "ok" prompt in interpreting mode? > >The prompt is fully configurable; set it yourself if that's what you >want. Ok. I did not know the prompt was configurable. >> 3) I noticed "evaluate" is working with null-ended string, ignoring >> completely the count on the stack. Not good. > >Is this an implementation feature? Does the count on the stack ever >not match the length of the string? I'm not sure what do you mean with the first question. As for the second question... sure. Forth string operators are all count based. The null will not appear on the end of the string unless you put it there yourself. Now, adding nulls to the end of the string is very easy with count based strings (as long as you are not working with a substring), and I have nothing against doing it. But having "evaluate" operate on null-terminated strings is the same as having strncmp operate on null-terminated strings: it's against standard and intent. -- Daniel C. Sobral dcs@newsguy.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 00:44:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA23518 for freebsd-current-outgoing; Mon, 21 Dec 1998 00:44:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from newsguy.com (smtp.newsguy.com [207.211.168.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA23512 for ; Mon, 21 Dec 1998 00:44:37 -0800 (PST) (envelope-from dcsobral@newsguy.com) Received: (from dcsobral@localhost) by newsguy.com (8.9.1a/8.9.1) id AAA07313; Mon, 21 Dec 1998 00:44:01 -0800 (PST) Date: Mon, 21 Dec 1998 00:44:01 -0800 (PST) Message-Id: <199812210844.AAA07313@newsguy.com> X-Mailer: Direct Read Email by Newsguy News Service To: mike@smith.net.au From: "Daniel C. Sobral" Subject: Re: BootFORTH - demo floppy Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Sun, 20 Dec 1998 16:23:48 -0800, you wrote >> >> 2) Could someone please add the 30-years old traditional >> "ok" prompt in interpreting mode? Oh, btw, I meant this not as removing the prompt being used right now, but as having something to distinguish between compile and interpret modes. -- Daniel C. Sobral dcs@newsguy.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 00:47:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA23629 for freebsd-current-outgoing; Mon, 21 Dec 1998 00:47:48 -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 AAA23621 for ; Mon, 21 Dec 1998 00:47:44 -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 DAA01169 for current@freebsd.org; Mon, 21 Dec 1998 03:47:41 -0500 (EST) (envelope-from lee) Message-ID: <19981221034741.A958@tidalwave.net> Date: Mon, 21 Dec 1998 03:47:41 -0500 From: Lee Cremeans To: current@FreeBSD.ORG Subject: Acer UDMA status report Reply-To: lcremean@tidalwave.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've done some more experimentation, and it seems that what is happening is that reads work just fine (I get 13MB/s sustained from my Seagate Medalist Pro 9140). However, if I do anything that writes to the drive, the interrupt timeouts start. I'm not sure what I'm doing wrong here, since the UDMA switches seem to be set correctly, and while Acer's documentation covers the bits in the registers to set, it doesn't go into detail as to which registers go together, or if there is anything else needed to make UDMA work reliably. PS: I did find a bug in the unit handling for DMA-detected drives. Here goes: *** ide_pci.c Mon Dec 14 00:49:04 1998 --- ide_pci.c.new Mon Dec 21 03:42:10 1998 *************** *** 1195,1201 **** cp = softc.cookies.lh_first; while(cp) { ! if (cp->ctlr == unit && ((iobase_wd == 0) || (cp->iobase_wd == iobase_wd))) break; cp = cp->le.le_next; --- 1253,1259 ---- cp = softc.cookies.lh_first; while(cp) { ! if (cp->unit == unit && ((iobase_wd == 0) || (cp->iobase_wd == iobase_wd))) break; cp = cp->le.le_next; A PR for this will be forthcoming... -- +--------------------------------------------------------------------+ | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)| | lcremean@tidalwave.net| http://st-lcremean.tidalwave.net | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 00:51:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA23895 for freebsd-current-outgoing; Mon, 21 Dec 1998 00:51:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles336.castles.com [208.214.167.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA23890 for ; Mon, 21 Dec 1998 00:51: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 AAA50785; Mon, 21 Dec 1998 00:49:06 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812210849.AAA50785@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel C. Sobral" cc: current@FreeBSD.ORG Subject: Re: BootFORTH - demo floppy In-reply-to: Your message of "Mon, 21 Dec 1998 00:41:02 PST." <199812210841.AAA07194@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Dec 1998 00:49:05 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At Sun, 20 Dec 1998 16:23:48 -0800, you wrote > >> > >> 2) Could someone please add the 30-years old traditional > >> "ok" prompt in interpreting mode? > > > >The prompt is fully configurable; set it yourself if that's what you > >want. > > Ok. I did not know the prompt was configurable. 'help set prompt' then 'set prompt=ok\n' should do it. > >> 3) I noticed "evaluate" is working with null-ended string, ignoring > >> completely the count on the stack. Not good. > > > >Is this an implementation feature? Does the count on the stack ever > >not match the length of the string? > > I'm not sure what do you mean with the first question. As for the second > question... sure. Forth string operators are all count based. The null will > not appear on the end of the string unless you put it there yourself. We don't like counted strings. They suck for innumerable reasons, and if the only reason for having them there is "tradition" (ie. there is no reason *not* to take them away) then they can damn well die. 8) Having said that, I get the distinct impression that we're stuck with these deadweights. > Now, adding nulls to the end of the string is very easy with count based > strings (as long as you are not working with a substring), and I have nothing > against doing it. But having "evaluate" operate on null-terminated strings is > the same as having strncmp operate on null-terminated strings: it's against > standard and intent. That's something you're welcome to take up with Mr Ficl; bear in mind though that we're talking about something that has to work fairly close to a much more significant C application. If trading between the two formats is a good idea from the efficiency point of view, that's probably the way to go. If you have any more concrete reasons (like it breaks something significant), then that's something I'd be happy to address, but "it's not normally done like that" is perhaps less important than "it's easy to work with in this context". -- \\ 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 Dec 21 00:53:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA24331 for freebsd-current-outgoing; Mon, 21 Dec 1998 00:53:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles336.castles.com [208.214.167.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA24326 for ; Mon, 21 Dec 1998 00:53:12 -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 AAA50803; Mon, 21 Dec 1998 00:50:47 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812210850.AAA50803@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel C. Sobral" cc: mike@smith.net.au, current@FreeBSD.ORG Subject: Re: BootFORTH - demo floppy In-reply-to: Your message of "Mon, 21 Dec 1998 00:44:01 PST." <199812210844.AAA07313@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Dec 1998 00:50:47 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At Sun, 20 Dec 1998 16:23:48 -0800, you wrote > >> > >> 2) Could someone please add the 30-years old traditional > >> "ok" prompt in interpreting mode? > > Oh, btw, I meant this not as removing the prompt being used right now, but as > having something to distinguish between compile and interpret modes. Ah. Right now that's a little tough because the interpreter is literally handed input line-by-line from the host application. There's probably good cause to change that in the near future; in fact if you're at all interested in hacking on this I for one would be *very* happy to have you onboard. There's a lot of integration that really does need to be done, and it's going to take someone that's at least a little familiar with Forth. -- \\ 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 Dec 21 00:57:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA24614 for freebsd-current-outgoing; Mon, 21 Dec 1998 00:57:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles336.castles.com [208.214.167.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA24604 for ; Mon, 21 Dec 1998 00:57:51 -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 AAA50852; Mon, 21 Dec 1998 00:55:25 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812210855.AAA50852@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: lcremean@tidalwave.net cc: current@FreeBSD.ORG Subject: Re: Acer UDMA status report In-reply-to: Your message of "Mon, 21 Dec 1998 03:47:41 EST." <19981221034741.A958@tidalwave.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Dec 1998 00:55:24 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've done some more experimentation, and it seems that what is happening is > that reads work just fine (I get 13MB/s sustained from my Seagate Medalist > Pro 9140). However, if I do anything that writes to the drive, the interrupt > timeouts start. I'm not sure what I'm doing wrong here, since the UDMA > switches seem to be set correctly, and while Acer's documentation covers the > bits in the registers to set, it doesn't go into detail as to which > registers go together, or if there is anything else needed to make UDMA work > reliably. Ick. Have you tried talking to Acer? They've been pretty helpful recently; you ought to be able to get some help from them without too much trouble, especially if you sort of pretend to be official... > PS: I did find a bug in the unit handling for DMA-detected drives. Here > goes: > > *** ide_pci.c Mon Dec 14 00:49:04 1998 > --- ide_pci.c.new Mon Dec 21 03:42:10 1998 > *************** > *** 1195,1201 **** > > cp = softc.cookies.lh_first; > while(cp) { > ! if (cp->ctlr == unit && > ((iobase_wd == 0) || (cp->iobase_wd == iobase_wd))) > break; > cp = cp->le.le_next; > --- 1253,1259 ---- > > cp = softc.cookies.lh_first; > while(cp) { > ! if (cp->unit == unit && > ((iobase_wd == 0) || (cp->iobase_wd == iobase_wd))) > break; > cp = cp->le.le_next; > > A PR for this will be forthcoming... Don't bother; unless I'm missing something you're quite right here, so I've committed 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 From owner-freebsd-current Mon Dec 21 00:58:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA24503 for freebsd-current-outgoing; Mon, 21 Dec 1998 00:56:03 -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 AAA24478 for ; Mon, 21 Dec 1998 00:56:01 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id AAA80755; Mon, 21 Dec 1998 00:55:50 -0800 (PST) To: "Daniel C. Sobral" cc: mike@smith.net.au, current@FreeBSD.ORG Subject: Re: BootFORTH - demo floppy In-reply-to: Your message of "Mon, 21 Dec 1998 00:41:02 PST." <199812210841.AAA07194@newsguy.com> Date: Mon, 21 Dec 1998 00:55:50 -0800 Message-ID: <80751.914230550@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Now, adding nulls to the end of the string is very easy with count based > strings (as long as you are not working with a substring), and I have nothing > against doing it. But having "evaluate" operate on null-terminated strings is > the same as having strncmp operate on null-terminated strings: it's against > standard and intent. I'm all in favor of pushing FICL more in the direction of standards conformance, to be sure. The I/O model in particular is rather primitive since FICL was designed specifically to chew on strings rather than be a more traditional console-based forth and I'd love to see some of that brought back. My own forth skills have seriously atrophied, unfortunately, and I'm generally not up on the newer ANS standards or even the older stuff which wasn't explicitly covered in the Brodie book. :-) If you see such conformance violations, a precise description of what the primitive should be returning or taking instead would be appreciated. Diffs to the code are, of course, appreciated even more! :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 01:00:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA24924 for freebsd-current-outgoing; Mon, 21 Dec 1998 01:00:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles336.castles.com [208.214.167.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA24919 for ; Mon, 21 Dec 1998 01:00:43 -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 AAA50894; Mon, 21 Dec 1998 00:58:00 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812210858.AAA50894@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: sthaug@nethelp.no cc: mike@smith.net.au, dcs@newsguy.com, current@FreeBSD.ORG Subject: Re: BootFORTH - demo floppy In-reply-to: Your message of "Mon, 21 Dec 1998 09:55:15 +0100." <13310.914230515@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Dec 1998 00:58:00 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I'm not sure what do you mean with the first question. As for the second > > > question... sure. Forth string operators are all count based. The null will > > > not appear on the end of the string unless you put it there yourself. > > > > We don't like counted strings. They suck for innumerable reasons, and > > if the only reason for having them there is "tradition" (ie. there is > > no reason *not* to take them away) then they can damn well die. 8) > > Given the many buffer overflows that have been found in various Unix > applications through the years, and the recent cleanup of string handling > in the kernel, maybe this view should be reexamined? *groan* Counted strings aren't somehow magically immune to overflowing their buffers. Lousy programming technique will take you from behind no matter what technology you think you're using. (I am resisting the temptation to use the word "bonehead" in this 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 Mon Dec 21 01:02:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA25123 for freebsd-current-outgoing; Mon, 21 Dec 1998 01:02:03 -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 BAA25085 for ; Mon, 21 Dec 1998 01:01:59 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 13312 invoked by uid 1001); 21 Dec 1998 08:55:15 +0000 (GMT) To: mike@smith.net.au Cc: dcs@newsguy.com, current@FreeBSD.ORG Subject: Re: BootFORTH - demo floppy In-Reply-To: Your message of "Mon, 21 Dec 1998 00:49:05 -0800" References: <199812210849.AAA50785@dingo.cdrom.com> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Mon, 21 Dec 1998 09:55:15 +0100 Message-ID: <13310.914230515@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I'm not sure what do you mean with the first question. As for the second > > question... sure. Forth string operators are all count based. The null will > > not appear on the end of the string unless you put it there yourself. > > We don't like counted strings. They suck for innumerable reasons, and > if the only reason for having them there is "tradition" (ie. there is > no reason *not* to take them away) then they can damn well die. 8) Given the many buffer overflows that have been found in various Unix applications through the years, and the recent cleanup of string handling in the kernel, maybe this view should be reexamined? 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 Mon Dec 21 01:06:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA25821 for freebsd-current-outgoing; Mon, 21 Dec 1998 01:06:33 -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 BAA25816 for ; Mon, 21 Dec 1998 01:06:31 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 13403 invoked by uid 1001); 21 Dec 1998 09:06:28 +0000 (GMT) To: mike@smith.net.au Cc: dcs@newsguy.com, current@FreeBSD.ORG Subject: Re: BootFORTH - demo floppy In-Reply-To: Your message of "Mon, 21 Dec 1998 00:58:00 -0800" References: <199812210858.AAA50894@dingo.cdrom.com> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Mon, 21 Dec 1998 10:06:28 +0100 Message-ID: <13401.914231188@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > We don't like counted strings. They suck for innumerable reasons, and > > > if the only reason for having them there is "tradition" (ie. there is > > > no reason *not* to take them away) then they can damn well die. 8) > > > > Given the many buffer overflows that have been found in various Unix > > applications through the years, and the recent cleanup of string handling > > in the kernel, maybe this view should be reexamined? > > *groan* > > Counted strings aren't somehow magically immune to overflowing their > buffers. Lousy programming technique will take you from behind no > matter what technology you think you're using. Of course. But counted strings can make some buffer overflow issues more visible, and may get the programmer to *think* about this. As an example, qmail uses a library which reimplements a good bit of the string handling in stdio, using counted strings. If counted strings suck for innumerable reasons, are these reasons documented somewhere? 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 Mon Dec 21 01:09:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA26201 for freebsd-current-outgoing; Mon, 21 Dec 1998 01:09:03 -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 BAA26183 for ; Mon, 21 Dec 1998 01:09:01 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id BAA17396; Mon, 21 Dec 1998 01:07:16 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdI17388; Mon Dec 21 09:07:08 1998 Date: Mon, 21 Dec 1998 01:06:59 -0800 (PST) From: Julian Elischer To: Mike Smith cc: Ollivier Robert , "FreeBSD Current Users' list" Subject: Re: Pb with COMPAT_LINUX_THREADS In-Reply-To: <199812210800.AAA50444@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 I agree with your suggestion, as long as I don't get crucified for moving 300 bytes from the u area into malloc'd space. The ifdef'd version is to let people look at it and think about it.. possibly as has been suggested, the malloc'd space might only be used if there is a sharing of signals. Otherwise it might remain in the U area. On Mon, 21 Dec 1998, Mike Smith wrote: > > According to Julian Elischer: > > > you need to recompile libkvm with the same options > > > > OK, that is working now. It should have been documented somewhere Julian > > :-) > > > > We need to find a way to make this kind of changes propagate through the > > rest of "make world"... if there is one. > > Remove the COMPAT_LINUX_THREADS #ifdefs. > > -- > \\ 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 Dec 21 01:09:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA26241 for freebsd-current-outgoing; Mon, 21 Dec 1998 01:09:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smarter.than.nu (thought.calbbs.com [207.71.213.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA26228 for ; Mon, 21 Dec 1998 01:09:11 -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 BAA02248; Mon, 21 Dec 1998 01:08:54 -0800 (PST) (envelope-from brian@CSUA.Berkeley.EDU) Date: Mon, 21 Dec 1998 01:08:53 -0800 (PST) From: "Brian W. Buchanan" X-Sender: brian@smarter.than.nu To: Joseph Lee cc: freebsd-current@FreeBSD.ORG Subject: Re: linking against libc_r 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, 20 Dec 1998, Joseph Lee wrote: > How do I link against libc_r instead of libc? > > Trying to build wine from the latest sources, and the configure > complains about libc being non-reentrant, which is what libc_r is for, > from what I've read. You need to link with -pthread to get libc_r. I'm not sure that it will make the latest WINE work for you, though, as it seems that WINE has become increasingly Linux-specific in recent days. (The port hasn't been updated since the 9/27 version, I assume because it's becoming too difficult a task) If you do manage to get a fairly recent version of wine working, please let me know -- I've heard rumors that you can run StarCraft under it starting with one of the October snaps, and as soon as I can do that, I can newfs my Win95 partition for good. :) Good luck, -- Brian Buchanan brian@smarter.than.nu brian@CSUA.Berkeley.EDU "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -- Benjamin Franklin, 1759 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 01:10:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA26383 for freebsd-current-outgoing; Mon, 21 Dec 1998 01:10:30 -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 BAA26378 for ; Mon, 21 Dec 1998 01:10:29 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id BAA80967; Mon, 21 Dec 1998 01:10:14 -0800 (PST) To: sthaug@nethelp.no cc: mike@smith.net.au, dcs@newsguy.com, current@FreeBSD.ORG Subject: Re: BootFORTH - demo floppy In-reply-to: Your message of "Mon, 21 Dec 1998 10:06:28 +0100." <13401.914231188@verdi.nethelp.no> Date: Mon, 21 Dec 1998 01:10:14 -0800 Message-ID: <80963.914231414@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Of course. But counted strings can make some buffer overflow issues > more visible, and may get the programmer to *think* about this. Counted strings don't buy you anything at all. It's ridiculously easy to overflow the buffers they represent with or without a count field moderating the _corrent_ usage of the string. In other words, it generally makes a good programmer's jobs harder and helps the bad programmer to live only a few extra moments at best, if even that much. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 01:11:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA26454 for freebsd-current-outgoing; Mon, 21 Dec 1998 01:11:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles336.castles.com [208.214.167.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA26448 for ; Mon, 21 Dec 1998 01:11:29 -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 BAA51022; Mon, 21 Dec 1998 01:08:54 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812210908.BAA51022@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: sthaug@nethelp.no cc: mike@smith.net.au, dcs@newsguy.com, current@FreeBSD.ORG Subject: Re: BootFORTH - demo floppy In-reply-to: Your message of "Mon, 21 Dec 1998 10:06:28 +0100." <13401.914231188@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Dec 1998 01:08:54 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > We don't like counted strings. They suck for innumerable reasons, and > > > > if the only reason for having them there is "tradition" (ie. there is > > > > no reason *not* to take them away) then they can damn well die. 8) > > > > > > Given the many buffer overflows that have been found in various Unix > > > applications through the years, and the recent cleanup of string handling > > > in the kernel, maybe this view should be reexamined? > > > > *groan* > > > > Counted strings aren't somehow magically immune to overflowing their > > buffers. Lousy programming technique will take you from behind no > > matter what technology you think you're using. > > Of course. But counted strings can make some buffer overflow issues > more visible, and may get the programmer to *think* about this. > > As an example, qmail uses a library which reimplements a good bit of > the string handling in stdio, using counted strings. > > If counted strings suck for innumerable reasons, are these reasons > documented somewhere? Commonsense suggests the two major problems: - the count is usually too small (in the ANS Forth case, it's one byte) - the overhead for maintaining the count and working with it is often unconsionably high, ie. the tradeoffs aren't actually very good. This is something you usually learn when you try to do something useful with Pascal as a junior weenie. -- \\ 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 Dec 21 01:16:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA26975 for freebsd-current-outgoing; Mon, 21 Dec 1998 01:16:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles336.castles.com [208.214.167.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA26970 for ; Mon, 21 Dec 1998 01:16:23 -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 BAA51083; Mon, 21 Dec 1998 01:13:25 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812210913.BAA51083@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Julian Elischer cc: Mike Smith , Ollivier Robert , "FreeBSD Current Users' list" Subject: Re: Pb with COMPAT_LINUX_THREADS In-reply-to: Your message of "Mon, 21 Dec 1998 01:06:59 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Dec 1998 01:13:24 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I agree with your suggestion, as long as I don't get crucified for > moving 300 bytes from the u area into malloc'd space. < 300k on a system capable of supporting 1000 processes - there are other things that I'd be worrying about at that point (like the size of the pagetables, which basically dwarf any other per-process overhead). > The ifdef'd version is to let people look at it and think about it.. > possibly as has been suggested, the malloc'd space might only be used if > there is a sharing of signals. Otherwise it might remain in the U area. That's certainly one way of doing it. You could implement structure compression by COW off the parent's copy of the struct instead, that'd be even more efficient. -- \\ 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 Dec 21 01:25:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA27642 for freebsd-current-outgoing; Mon, 21 Dec 1998 01:25:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shell6.ba.best.com (shell6.ba.best.com [206.184.139.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA27637 for ; Mon, 21 Dec 1998 01:25:28 -0800 (PST) (envelope-from jkb@shell6.ba.best.com) Received: (from jkb@localhost) by shell6.ba.best.com (8.9.1/8.9.0/best.sh) id AAA26432 for current@freebsd.org; Mon, 21 Dec 1998 00:54:42 -0800 (PST) Message-ID: <19981221005441.A25379@best.com> Date: Mon, 21 Dec 1998 00:54:41 -0800 From: "Jan B. Koum " To: current@FreeBSD.ORG Subject: Re: Interesting panic: Shouldn't get here! References: <19981221091521.A82746@hal.mpn.cp.philips.com> <199812210827.AAA50600@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812210827.AAA50600@dingo.cdrom.com>; from Mike Smith on Mon, Dec 21, 1998 at 12:27:21AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 21, 1998 at 12:27:21AM -0800, Mike Smith wrote: > > Good morning all, > > > > This is with yesterday's world and today's kernel. The panic occurs in > > kern/init_main.c(274). Should I file a PR? > > No, and particularly not with that singular lack of any useful > information. > FWIW I got the same on my system. I had 3.0-CURRENT running from about two weeks ago. Decided today it was time to do another CVSup. Upon reboot the system only saw half amount of RAM (I have 128MB) and then said "panic: Shouldn't get here". The system has been running fine all along before. I am going to play with it more and see what works and what does not. Booting old (from snap of 11/23) a.out /kernel.GENERIC does bring the system up. By default /kernel is elf. The hardware is P-II 233MHz, 128RAM, IDE, fxp0, .. -- Yan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 01:25:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA27665 for freebsd-current-outgoing; Mon, 21 Dec 1998 01:25:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from newsguy.com (smtp.newsguy.com [207.211.168.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA27660 for ; Mon, 21 Dec 1998 01:25:58 -0800 (PST) (envelope-from dcsobral@newsguy.com) Received: (from dcsobral@localhost) by newsguy.com (8.9.1a/8.9.1) id BAA09284; Mon, 21 Dec 1998 01:25:21 -0800 (PST) Date: Mon, 21 Dec 1998 01:25:21 -0800 (PST) Message-Id: <199812210925.BAA09284@newsguy.com> X-Mailer: Direct Read Email by Newsguy News Service To: mike@smith.net.au From: "Daniel C. Sobral" Subject: Re: BootFORTH - demo floppy Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Mon, 21 Dec 1998 00:49:05 -0800, you wrote > >> >> 3) I noticed "evaluate" is working with null-ended string, ignoring >> >> completely the count on the stack. Not good. > >We don't like counted strings. They suck for innumerable reasons, and >if the only reason for having them there is "tradition" (ie. there is >no reason *not* to take them away) then they can damn well die. 8) Well, I have never seen a "reason" aside from needlessly limiting the size of one string (at 32 bits, that ought to be a joke, but...), which is well balanced by needlessly limiting what can be inside a string. But, as you say below, "having said that..." >Having said that, I get the distinct impression that we're stuck with >these deadweights. Hardly. ANS Forth removed the count from the string itself for this precise reason. So, s" " must return the memory to the string, as well as it's size. It is up to the implementation to decide whether a zero must be appended to the end (giving our specific application, sure it must), and the count being returned on the stack is a given (ie, you have that information as a side effect of parsing). Of course, "move" must act as strncpy, not strcpy, and so on. But you will notice that the words that assume a count with the string have been made obsolete. >> Now, adding nulls to the end of the string is very easy with count based >> strings (as long as you are not working with a substring), and I have nothing >> against doing it. But having "evaluate" operate on null-terminated strings is >> the same as having strncmp operate on null-terminated strings: it's against >> standard and intent. > >That's something you're welcome to take up with Mr Ficl; bear in mind >though that we're talking about something that has to work fairly close >to a much more significant C application. If trading between the two >formats is a good idea from the efficiency point of view, that's >probably the way to go. > >If you have any more concrete reasons (like it breaks something >significant), then that's something I'd be happy to address, but "it's >not normally done like that" is perhaps less important than "it's easy >to work with in this context". Nobody else seems to have trouble interfacing Forth with C, so I just don't see I case here. It's not "tradition". It is the ANS Forth standard. If you want an evaluate which works with null-terminated strings, go ahead and define evaluate0 or something. But needlessly making it incompatible with a published standard is, well, it is stupid. I did not have any trouble getting around the need for a null-terminated string, but it did took me some time to figure out what the "bug" in "my" code was. Do you see my point here? I'm not against making it easier to interface with the "C" environment. But you can do that without breaking compatibility. There is a lot of room for that. The standard words for allocating strings won't mind automatic appending a null, you can define words like "strcpy", "strlen" and "strcmp" doing exactly what you would expect them to, and there even some more obscure restrictions made in ANS Forth just so such interfacing can be made more painlessly. But if you change the behavior of a standard word, instead of just defining a new word, you not only make it "incompatible" with standard programs (or, more to the point to us, libraries). You make it incompatible with Forth programmers. Just for the sake of using "evaluate" instead of "evaluate0", I must say I don't really see a gain on _your_ side. create buffer buffersize allot : evaluate buffer over + 0 swap c! buffer swap move buffer evaluate0 ; Writing the two lines above is much faster than finding the "bug", I assure you. -- Daniel C. Sobral dcs@newsguy.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 01:28:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA27971 for freebsd-current-outgoing; Mon, 21 Dec 1998 01:28:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shell6.ba.best.com (shell6.ba.best.com [206.184.139.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA27966 for ; Mon, 21 Dec 1998 01:28:23 -0800 (PST) (envelope-from jkb@shell6.ba.best.com) Received: (from jkb@localhost) by shell6.ba.best.com (8.9.1/8.9.0/best.sh) id BAA01665 for current@freebsd.org; Mon, 21 Dec 1998 01:27:58 -0800 (PST) Message-ID: <19981221012758.A1470@best.com> Date: Mon, 21 Dec 1998 01:27:58 -0800 From: "Jan B. Koum " To: current@FreeBSD.ORG Subject: Re: Interesting panic: Shouldn't get here! References: <19981221091521.A82746@hal.mpn.cp.philips.com> <199812210827.AAA50600@dingo.cdrom.com> <19981221005441.A25379@best.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19981221005441.A25379@best.com>; from Jan B. Koum on Mon, Dec 21, 1998 at 12:54:41AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 21, 1998 at 12:54:41AM -0800, "Jan B. Koum " wrote: > On Mon, Dec 21, 1998 at 12:27:21AM -0800, Mike Smith wrote: > > > Good morning all, > > > > > > This is with yesterday's world and today's kernel. The panic occurs in > > > kern/init_main.c(274). Should I file a PR? > > > > No, and particularly not with that singular lack of any useful > > information. > > > I guess I should have waited first. Compiling kernel as a.out - and it boots and works like a charm. -- Yan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 01:45:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA29410 for freebsd-current-outgoing; Mon, 21 Dec 1998 01:45:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles336.castles.com [208.214.167.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA29403 for ; Mon, 21 Dec 1998 01:45: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 BAA00690; Mon, 21 Dec 1998 01:43:11 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812210943.BAA00690@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jan B. Koum " cc: current@FreeBSD.ORG Subject: Re: Interesting panic: Shouldn't get here! In-reply-to: Your message of "Mon, 21 Dec 1998 01:27:58 PST." <19981221012758.A1470@best.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Dec 1998 01:43:10 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, Dec 21, 1998 at 12:54:41AM -0800, "Jan B. Koum " wrote: > > On Mon, Dec 21, 1998 at 12:27:21AM -0800, Mike Smith wrote: > > > > Good morning all, > > > > > > > > This is with yesterday's world and today's kernel. The panic occurs in > > > > kern/init_main.c(274). Should I file a PR? > > > > > > No, and particularly not with that singular lack of any useful > > > information. > > > > > I guess I should have waited first. Compiling > kernel as a.out - and it boots and works like > a charm. Ok, I think I got this one. Sorry for the snippy initial response - it looks like Bruce broke SYSINITs for ELF. The quick fix is probably to go back to rev 1.47 of sys/sys/kernel.h, I'll try to confirm this in a moment. -- \\ 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 Dec 21 01:55:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA00575 for freebsd-current-outgoing; Mon, 21 Dec 1998 01:55:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA00570 for ; Mon, 21 Dec 1998 01:55:54 -0800 (PST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id KAA27336 for ; Mon, 21 Dec 1998 10:55:48 +0100 (MET) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma027329; Mon, 21 Dec 98 10:55:51 +0100 Received: from dibbs1.eur.cis.philips.com (dibbs1.eur.cis.philips.com [130.139.33.66]) by smtprelay-nl1.philips.com (8.8.5/8.6.10-1.2.2m-970826) with ESMTP id KAA22114 for ; Mon, 21 Dec 1998 10:55:44 +0100 (MET) Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by dibbs1.eur.cis.philips.com (8.8.8/8.8.8) with SMTP id KAA01635 for ; Mon, 21 Dec 1998 10:55:42 +0100 (MET) Received: (qmail 83167 invoked by uid 666); 21 Dec 1998 09:56:02 -0000 Date: Mon, 21 Dec 1998 10:56:02 +0100 From: Jos Backus To: Mike Smith Cc: freebsd-current@FreeBSD.ORG Subject: Re: Interesting panic: Shouldn't get here! Message-ID: <19981221105602.C82746@hal.mpn.cp.philips.com> Reply-To: Jos Backus References: <19981221091521.A82746@hal.mpn.cp.philips.com> <199812210827.AAA50600@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199812210827.AAA50600@dingo.cdrom.com>; from Mike Smith on Mon, Dec 21, 1998 at 12:27:21AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 21, 1998 at 12:27:21AM -0800, Mike Smith wrote: > No, and particularly not with that singular lack of any useful > information. Fair 'nuff. What do you want to know? Id strings? * $Id: init_main.c,v 1.101 1998/12/19 08:23:31 julian Exp $ Thanks, -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 01:59:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA00861 for freebsd-current-outgoing; Mon, 21 Dec 1998 01:59:13 -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 BAA00853 for ; Mon, 21 Dec 1998 01:59:12 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id BAA81124; Mon, 21 Dec 1998 01:59:00 -0800 (PST) To: "Daniel C. Sobral" cc: mike@smith.net.au, current@FreeBSD.ORG Subject: Re: BootFORTH - demo floppy In-reply-to: Your message of "Mon, 21 Dec 1998 01:25:21 PST." <199812210925.BAA09284@newsguy.com> Date: Mon, 21 Dec 1998 01:59:00 -0800 Message-ID: <81120.914234340@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > see I case here. It's not "tradition". It is the ANS Forth standard. If you > want an evaluate which works with null-terminated strings, go ahead and defin e > evaluate0 or something. But needlessly making it incompatible with a publishe d > standard is, well, it is stupid. Which is what I hopefully communicated in my other message. Mike is not a forth programmer, so he simply does not always know the distinction between something which is a standard core word and something which is an optional (and perhaps egregious) forth-ism. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 02:01:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA01143 for freebsd-current-outgoing; Mon, 21 Dec 1998 02:01:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from newsguy.com (smtp.newsguy.com [207.211.168.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA01128 for ; Mon, 21 Dec 1998 02:00:56 -0800 (PST) (envelope-from dcsobral@newsguy.com) Received: (from dcsobral@localhost) by newsguy.com (8.9.1a/8.9.1) id CAA10460 for current@freebsd.org; Mon, 21 Dec 1998 02:00:54 -0800 (PST) Date: Mon, 21 Dec 1998 02:00:54 -0800 (PST) Message-Id: <199812211000.CAA10460@newsguy.com> X-Mailer: Direct Read Email by Newsguy News Service To: current@FreeBSD.ORG From: "Daniel C. Sobral" Subject: Counted String (was: Re: BootFORTH - demo floppy) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike and Steinar said a number of things, which I'll left unquoted. I just want to say... PLEASE, NO DISCUSSIONS ON THE MERITS AND DEMERITS OF COUNTED STRINGS AND NULL-TERMINATED STRINGS! At least, not on freebsd-current. :-) -- Daniel C. Sobral dcs@newsguy.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 02:32:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA04784 for freebsd-current-outgoing; Mon, 21 Dec 1998 02:32:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles336.castles.com [208.214.167.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA04777 for ; Mon, 21 Dec 1998 02:32:12 -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 CAA00356; Mon, 21 Dec 1998 02:29:47 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812211029.CAA00356@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Jos Backus cc: Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: Interesting panic: Shouldn't get here! In-reply-to: Your message of "Mon, 21 Dec 1998 10:56:02 +0100." <19981221105602.C82746@hal.mpn.cp.philips.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Dec 1998 02:29:46 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, Dec 21, 1998 at 12:27:21AM -0800, Mike Smith wrote: > > No, and particularly not with that singular lack of any useful > > information. > > Fair 'nuff. What do you want to know? Id strings? > > * $Id: init_main.c,v 1.101 1998/12/19 08:23:31 julian Exp $ The problem was caused by Bruce's change in rev 1.131 of sys/i386/conf/Makefile.i386. Either back out to rev 1.130 or wait for 1.132 (just committed). You'll have to re-config your kernel at that point. -- \\ 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 Dec 21 02:32:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA05015 for freebsd-current-outgoing; Mon, 21 Dec 1998 02:32:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from newsguy.com (smtp.newsguy.com [207.211.168.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA05009 for ; Mon, 21 Dec 1998 02:32:40 -0800 (PST) (envelope-from dcsobral@newsguy.com) Received: (from dcsobral@localhost) by newsguy.com (8.9.1a/8.9.1) id CAA11540; Mon, 21 Dec 1998 02:32:03 -0800 (PST) Date: Mon, 21 Dec 1998 02:32:03 -0800 (PST) Message-Id: <199812211032.CAA11540@newsguy.com> X-Mailer: Direct Read Email by Newsguy News Service To: mike@smith.net.au From: "Daniel C. Sobral" Subject: Re: BootFORTH - demo floppy Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Mon, 21 Dec 1998 01:08:54 -0800, you wrote >Commonsense suggests the two major problems: [This is really irrelevant; in particular, my "experience" disagree with the "common sense" of the second statement; but the first statement must be correct for the sake of correct use of FICL. IMHO, anyway] > - the count is usually too small (in the ANS Forth case, it's one byte) Most string words in Forth take their count from the stack, so it's one cell, not byte. I suppose FICL uses 32 bits integers as cells, right? There is *one* word in ANS Forth that takes the count from the memory, as far as I can remember: count. This word is there for backward compatibility purposes. Even then, "it's one byte" it's rather incorrect. Let's see: "Return the character string specification for the counted string stored at c-addr1. c-addr2 is the address of the first character after c-addr1. u is the contents of the character at c-addr1, which is the length in characters of the string at c-addr2." Mind you, "character" is not "byte": "Characters shall be at least one address unit wide, contain at least eight bits, and have a size less than or equal to cell size. " Also, "counted string: A data structure consisting of one character containing a length followed by zero or more contiguous data characters. Normally, counted strings contain text. " "character: Depending on context, either 1) a storage unit capable of holding a character; or 2) a member of a character set. " "Table 3.5 - Environmental Query Strings String Value Constant? Meaning data type /COUNTED-STRING n yes maximum size of a counted string, in characters ... MAX-CHAR u yes maximum value of any character in the implementation-defined character set" So, Unicode Forths would have 65535-sized counted strings. Indeed, some Forths use 32 bits characters. Ok, ok, a brief search shows me a little bit incorrect. WORD and C" return memory-counted strings. C" is core ext and was replaced by S". Though WORD is core and PARSE is core ext, the same applies here (WORD is for compatibility, PARSE has been introduced to eliminate the need for count in memory). -- Daniel C. Sobral dcs@newsguy.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 02:34:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA05195 for freebsd-current-outgoing; Mon, 21 Dec 1998 02:34:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles336.castles.com [208.214.167.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA05165 for ; Mon, 21 Dec 1998 02:34: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 CAA00403; Mon, 21 Dec 1998 02:32:28 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812211032.CAA00403@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel C. Sobral" cc: mike@smith.net.au, current@FreeBSD.ORG Subject: Re: BootFORTH - demo floppy In-reply-to: Your message of "Mon, 21 Dec 1998 01:25:21 PST." <199812210925.BAA09284@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Dec 1998 02:32:27 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Do you see my point here? I'm not against making it easier to interface with > the "C" environment. But you can do that without breaking compatibility. There > is a lot of room for that. The standard words for allocating strings won't > mind automatic appending a null, you can define words like "strcpy", "strlen" > and "strcmp" doing exactly what you would expect them to, and there even some > more obscure restrictions made in ANS Forth just so such interfacing can be > made more painlessly. But if you change the behavior of a standard word, > instead of just defining a new word, you not only make it "incompatible" with > standard programs (or, more to the point to us, libraries). You make it > incompatible with Forth programmers. Cool. That's just the sort of explanation that I need. As Jordan pointed out, I have no real grounding in Forth so I'm still making perspective errors. And I'll ask again; are you interested in working on this? -- \\ 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 Dec 21 02:35:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA05242 for freebsd-current-outgoing; Mon, 21 Dec 1998 02:35:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from newsguy.com (smtp.newsguy.com [207.211.168.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA05229 for ; Mon, 21 Dec 1998 02:35:18 -0800 (PST) (envelope-from dcsobral@newsguy.com) Received: (from dcsobral@localhost) by newsguy.com (8.9.1a/8.9.1) id CAA11648; Mon, 21 Dec 1998 02:34:40 -0800 (PST) Date: Mon, 21 Dec 1998 02:34:40 -0800 (PST) Message-Id: <199812211034.CAA11648@newsguy.com> X-Mailer: Direct Read Email by Newsguy News Service To: mike@smith.net.au From: "Daniel C. Sobral" Subject: Re: Pb with COMPAT_LINUX_THREADS Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Mon, 21 Dec 1998 01:13:24 -0800, you wrote > >> The ifdef'd version is to let people look at it and think about it.. >> possibly as has been suggested, the malloc'd space might only be used if >> there is a sharing of signals. Otherwise it might remain in the U area. > >That's certainly one way of doing it. You could implement structure >compression by COW off the parent's copy of the struct instead, that'd >be even more efficient. I have been wondering about this... Multithreading is usually used to improve performance. Wouldn't this "on-demand" allocation of shared signals impact of performance? -- Daniel C. Sobral dcs@newsguy.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 02:37:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA05400 for freebsd-current-outgoing; Mon, 21 Dec 1998 02:37:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from minnie.comp.cs.gunma-u.ac.jp ([133.8.10.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA05395 for ; Mon, 21 Dec 1998 02:37:57 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (hercules.comp.cs.gunma-u.ac.jp [133.8.10.23]) by minnie.comp.cs.gunma-u.ac.jp (8.8.8+2.7Wbeta7/3.6W03/23/98) with ESMTP id TAA24762 for ; Mon, 21 Dec 1998 19:34:33 +0900 (JST) Message-ID: <367E25BA.5C386267@newsguy.com> Date: Mon, 21 Dec 1998 19:40:58 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win95; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: BootFORTH - demo floppy Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Mon, 21 Dec 1998 00:55:50 -0800, you wrote > >I'm all in favor of pushing FICL more in the direction of standards >conformance, to be sure. The I/O model in particular is rather >primitive since FICL was designed specifically to chew on strings >rather than be a more traditional console-based forth and I'd love to >see some of that brought back. Not sure what that means, but ANS Forth kind of makes Forth very string-chewing as far as the command interpreter/compiler goes. The old INTERPRET is obsolete, and the "heart" of the interpreter machine is now EVALUATE. Still, I expect to be a interpreting/compiling flag _somewhere_, that could be read by whatever is printing the prompt. But that's just a side not. What I really meant to say is... >My own forth skills have seriously atrophied, unfortunately, and I'm >generally not up on the newer ANS standards or even the older stuff >which wasn't explicitly covered in the Brodie book. :-) > >If you see such conformance violations, a precise description of what >the primitive should be returning or taking instead would be >appreciated. Diffs to the code are, of course, appreciated even more! :) The last draft of ANS Forth is available on the Internet (easily reachable from www.forth.org/literature.html -- html://www.forth.org/dpans/dpans.html for on-line reference) on a number of different printable formats. The final version of ANS Forth is very much like that draft, so it is quite useful. This might not be exactly the tool for learning Forth, but it does go to some extent to explain the Forth model, Forth assumptions, and differences between ANS Forth standard and the previous ones, so anyone As for the behavior of EVALUATE... Well it receives a buffer and a char count, and it should restrict itself to that. Currently, it just ignores the char count. This is not a problem with the old boot code commands, btw. I checked that (in fact, if I had not been experimenting with the old boot code commands, it would have taken me a lot more time to find the bug :). To quote from the above link: Relevant text from the Standard: 6.1.1360 EVALUATE ... Make the string described by c-addr and u both the 'input source' and 'input buffer' ... 6.1.2216 SOURCE ... c-addr is the address of, and u is the number of characters in, the 'input buffer'. 2.1 Definitions of Terms input source: The device, file, block, or other entity that supplies characters to refill the 'input buffer'. input buffer: A region of memory containing the sequence of characters from the input source that is currently accessible to a program. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com You can't modify a constant, float upstream, win an argument with the IRS, or satisfy this compiler To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 02:43:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA05756 for freebsd-current-outgoing; Mon, 21 Dec 1998 02:43:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles336.castles.com [208.214.167.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA05747 for ; Mon, 21 Dec 1998 02:43:10 -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 CAA00481; Mon, 21 Dec 1998 02:40:54 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812211040.CAA00481@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel C. Sobral" cc: current@FreeBSD.ORG Subject: Re: Pb with COMPAT_LINUX_THREADS In-reply-to: Your message of "Mon, 21 Dec 1998 02:34:40 PST." <199812211034.CAA11648@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Dec 1998 02:40:53 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At Mon, 21 Dec 1998 01:13:24 -0800, you wrote > > > >> The ifdef'd version is to let people look at it and think about it.. > >> possibly as has been suggested, the malloc'd space might only be used if > >> there is a sharing of signals. Otherwise it might remain in the U area. > > > >That's certainly one way of doing it. You could implement structure > >compression by COW off the parent's copy of the struct instead, that'd > >be even more efficient. > > I have been wondering about this... Multithreading is usually used to improve > performance. Wouldn't this "on-demand" allocation of shared signals impact of > performance? You typically thread for the concurrency win, and wear the startup cost as an overhead that you have to pay back with concurrency. Given that at the moment we're looking at a heavyweight thread implementation, this extra allocation is relatively trivial in the scheme of things. My real feeling at the moment is that we need to lurch forward and uncover the problems that these changes are bound to introduce, rather than sticking a few toes in it and letting the code and developers moulder. Just MHO of course. -- \\ 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 Dec 21 02:44:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA05973 for freebsd-current-outgoing; Mon, 21 Dec 1998 02:44:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from newsguy.com (smtp.newsguy.com [207.211.168.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA05968 for ; Mon, 21 Dec 1998 02:44:24 -0800 (PST) (envelope-from dcsobral@newsguy.com) Received: (from dcsobral@localhost) by newsguy.com (8.9.1a/8.9.1) id CAA11970; Mon, 21 Dec 1998 02:43:47 -0800 (PST) Date: Mon, 21 Dec 1998 02:43:47 -0800 (PST) Message-Id: <199812211043.CAA11970@newsguy.com> X-Mailer: Direct Read Email by Newsguy News Service To: mike@smith.net.au From: "Daniel C. Sobral" Subject: Re: BootFORTH - demo floppy Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Mon, 21 Dec 1998 02:32:27 -0800, you wrote > >Cool. That's just the sort of explanation that I need. As Jordan >pointed out, I have no real grounding in Forth so I'm still making >perspective errors. > >And I'll ask again; are you interested in working on this? Sure I'm interested. I resubscribed to -current for that precise reason (an announced it so) about... three weeks ago? Two weeks agon. Not even that much. Unfortunately, I'm out of touch with Free for the past eight months. I moved from my country to do my masters, and left my full-tower with all it's hard disks behind. Right now, I don't have FreeBSD (except for the demo floppy which initiated this thread :), nor the space to install it. It is my intention to correct both "problems" as soon as possible :-), but how soon _that_ will be I really don't know. And, *then*, there is the fact that my computer is a notebook, a _Compaq_ notebook, and I'm already dreading the incompatibility issues I fear will arise. (Hey, anyone, any tips on external harddisks?) -- Daniel C. Sobral dcs@newsguy.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 02:45:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA06102 for freebsd-current-outgoing; Mon, 21 Dec 1998 02:45:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles336.castles.com [208.214.167.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA06097 for ; Mon, 21 Dec 1998 02:45:25 -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 CAA00452; Mon, 21 Dec 1998 02:37:37 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812211037.CAA00452@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel C. Sobral" cc: mike@smith.net.au, current@FreeBSD.ORG Subject: Re: BootFORTH - demo floppy In-reply-to: Your message of "Mon, 21 Dec 1998 02:32:03 PST." <199812211032.CAA11540@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Dec 1998 02:37:36 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At Mon, 21 Dec 1998 01:08:54 -0800, you wrote > > >Commonsense suggests the two major problems: > > [This is really irrelevant; in particular, my "experience" disagree with the > "common sense" of the second statement; but the first statement must be > correct for the sake of correct use of FICL. IMHO, anyway] > > > - the count is usually too small (in the ANS Forth case, it's one byte) > > Most string words in Forth take their count from the stack, so it's one cell, > not byte. I suppose FICL uses 32 bits integers as cells, right? /* ** Strings in FICL are stored in Pascal style - with a count ** preceding the text. We'll also NULL-terminate them so that ** they work with the usual C lib string functions. (Belt & ** suspenders? You decide.) ** STRINGINFO hides the implementation with a couple of ** macros for use in internal routines. */ typedef unsigned char FICL_COUNT; #define FICL_STRING_MAX UCHAR_MAX typedef struct _ficl_string { FICL_COUNT count; char text[1]; } FICL_STRING; I *think* that Ficl will have to move to using 64-bit cells, at least on the Alpha (since it stores pointers in them). > So, Unicode Forths would have 65535-sized counted strings. Indeed, some Forths > use 32 bits characters. This is definitely something to take up with John Sadler. The whole reason that it's an issue from my perspective is that there are some cases where I can see it being desirable to be able to handle strings longer than 255 bytes with the bootloader, and that means that the scripting language has to be able to deal with them. Thanks for the clarification. -- \\ 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 Dec 21 02:53:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA06548 for freebsd-current-outgoing; Mon, 21 Dec 1998 02:53:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from newsguy.com (smtp.newsguy.com [207.211.168.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA06543 for ; Mon, 21 Dec 1998 02:53:52 -0800 (PST) (envelope-from dcsobral@newsguy.com) Received: (from dcsobral@localhost) by newsguy.com (8.9.1a/8.9.1) id CAA12289; Mon, 21 Dec 1998 02:53:15 -0800 (PST) Date: Mon, 21 Dec 1998 02:53:15 -0800 (PST) Message-Id: <199812211053.CAA12289@newsguy.com> X-Mailer: Direct Read Email by Newsguy News Service To: mike@smith.net.au From: "Daniel C. Sobral" Subject: Re: BootFORTH - demo floppy Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Mon, 21 Dec 1998 02:37:36 -0800, you wrote >> >> Most string words in Forth take their count from the stack, so it's one cell, >> not byte. I suppose FICL uses 32 bits integers as cells, right? > >/* >** Strings in FICL are stored in Pascal style - with a count >** preceding the text. We'll also NULL-terminate them so that >** they work with the usual C lib string functions. (Belt & >** suspenders? You decide.) >** STRINGINFO hides the implementation with a couple of >** macros for use in internal routines. >*/ Just to make sure there are no misunderstandings here, this does not invalidate my point above. I don't know where these "strings" are used (most likely, the dictionary), but, for instance, EVALUATE takes it's count from the stack, not from the memory (in fact, it doesn't even expect a count in the memory), and it is thus cell-limited in size. >I *think* that Ficl will have to move to using 64-bit cells, at least >on the Alpha (since it stores pointers in them). ANS Forth is perfectly capable of handling different-sized cells and characters. In the code I sent, for instance, "80 allot" would rather have to be written "80 chars allot", if I were doing anything but a hasty hack. >This is definitely something to take up with John Sadler. The whole >reason that it's an issue from my perspective is that there are some >cases where I can see it being desirable to be able to handle strings >longer than 255 bytes with the bootloader, and that means that the >scripting language has to be able to deal with them. Sure. As I said, there isn't anything expect COUNT, C" and WORD that use memory-counted strings (in the interface, at least), and you can easily stay away from those. >Thanks for the clarification. As I said, I really would like this to "work". Feel free to send me any questions. (As I said in another mail, real work from my part will have to wait for a hd.) -- Daniel C. Sobral dcs@newsguy.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 07:11:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA02825 for freebsd-current-outgoing; Mon, 21 Dec 1998 07:11:17 -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 HAA02813 for ; Mon, 21 Dec 1998 07:11:08 -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 QAA35578; Mon, 21 Dec 1998 16:10:41 +0100 (CET) (envelope-from des) To: Jeroen Ruigrok/Asmodai Cc: Mike Jackson , freebsd-current@FreeBSD.ORG, Alfred Perlstein , "John A. Hengstler" Subject: Re: Buildworld fails References: From: Dag-Erling Smorgrav Date: 21 Dec 1998 16:10:41 +0100 In-Reply-To: Jeroen Ruigrok/Asmodai's message of "Sat, 19 Dec 1998 12:12:29 +0100 (CET)" Message-ID: Lines: 11 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeroen Ruigrok/Asmodai writes: > And I can also not see what swapping should have to do with the failure of a > compiler pass. If your swap partition is rotten (i.e. if the disk it's on, or the controller, is rotten), you'll get SIGBUSes and/or SIGSEGVs under high load. 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 Mon Dec 21 07:12:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA03103 for freebsd-current-outgoing; Mon, 21 Dec 1998 07:12:09 -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 HAA03098 for ; Mon, 21 Dec 1998 07:12:04 -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 QAA35589; Mon, 21 Dec 1998 16:11:54 +0100 (CET) (envelope-from des) To: "John Hengstler" Cc: "Mike Jackson" , Subject: Re: Buildworld fails References: <000001be2c40$8231e670$83a3ded1@trout.heicomm.net> From: Dag-Erling Smorgrav Date: 21 Dec 1998 16:11:53 +0100 In-Reply-To: "John Hengstler"'s message of "Sun, 20 Dec 1998 09:45:18 -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 "John Hengstler" writes: > I added the noatime,async options to my /usr and rebooted, > > Everything Built and installed correctly.... > > So why would these options need to be added in order for the builds to work? By doing so, you significantly reduced the amount of I/O required by make world, and thus avoided a heisenbug probably caused by rotten hardware. 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 Mon Dec 21 07:21:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04004 for freebsd-current-outgoing; Mon, 21 Dec 1998 07:21:56 -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 HAA03999 for ; Mon, 21 Dec 1998 07:21:53 -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 QAA35692; Mon, 21 Dec 1998 16:21:34 +0100 (CET) (envelope-from des) To: Dmitrij Tejblum Cc: Poul-Henning Kamp , Bruce Evans , jkh@zippy.cdrom.com, current@FreeBSD.ORG Subject: Re: I almost hate to suggest this... References: <199812192154.AAA00405@tejblum.dnttm.rssi.ru> From: Dag-Erling Smorgrav Date: 21 Dec 1998 16:21:33 +0100 In-Reply-To: Dmitrij Tejblum's message of "Sun, 20 Dec 1998 00:54:50 +0300" Message-ID: Lines: 17 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dmitrij Tejblum writes: > Poul-Henning Kamp wrote: > > In difference from Bruce I think that mount_XXX is the primary interface, > > (and as such agree with jordan that mount_ufs should be there). Mount > > is just a backwards compatibility gadget now. > Most mount_XXX programs are somewhat broken if used as user interface. > Mount(8) is the only way to mount filesystems from /etc/fstab, anyhow. > I think, primary user interface is mount(8) combined with $EDITOR /etc/fstab > (unless we are talking about fixit floppy, of course). Nah, call it a front-end. Like the distinction between pw(8) and the abominable (unless it's been rewritten, ISTR it was a Tcl script but it seems to be Perl now) adduser(8) script. 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 Mon Dec 21 07:22:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04060 for freebsd-current-outgoing; Mon, 21 Dec 1998 07:22: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 HAA04028 for ; Mon, 21 Dec 1998 07:21: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 KAA18817; Mon, 21 Dec 1998 10:25:39 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Mon, 21 Dec 1998 10:25:39 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: "Brian W. Buchanan" cc: Joseph Lee , freebsd-current@FreeBSD.ORG Subject: Re: linking against libc_r 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 Mon, 21 Dec 1998, Brian W. Buchanan wrote: > On Sun, 20 Dec 1998, Joseph Lee wrote: > > > How do I link against libc_r instead of libc? > > > > Trying to build wine from the latest sources, and the configure > > complains about libc being non-reentrant, which is what libc_r is for, > > from what I've read. > > You need to link with -pthread to get libc_r. I'm not sure that it will > make the latest WINE work for you, though, as it seems that WINE has > become increasingly Linux-specific in recent days. (The port hasn't been > updated since the 9/27 version, I assume because it's becoming too > difficult a task) If you do manage to get a fairly recent version of wine > working, please let me know -- I've heard rumors that you can run > StarCraft under it starting with one of the October snaps, and as soon as > I can do that, I can newfs my Win95 partition for good. :) > With the recent addition of Linuxthreads to FreeBSD it may soon be possible to use a Wine rpm to play starcraft :) Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 07:27:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04687 for freebsd-current-outgoing; Mon, 21 Dec 1998 07:27: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 HAA04679 for ; Mon, 21 Dec 1998 07:27:05 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.1/8.9.1) id JAA00614 for freebsd-current@FreeBSD.ORG; Mon, 21 Dec 1998 09:26:55 -0600 (CST) (envelope-from dick) Message-ID: <19981221092655.B546@tar.com> Date: Mon, 21 Dec 1998 09:26:55 -0600 From: Richard Seaman To: "FreeBSD Current Users' list" Subject: Re: Pb with COMPAT_LINUX_THREADS References: <19981221000330.A6587@keltia.freenix.fr> <19981221084326.A9987@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19981221084326.A9987@keltia.freenix.fr>; from Ollivier Robert on Mon, Dec 21, 1998 at 08:43:26AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 21, 1998 at 08:43:26AM +0100, Ollivier Robert wrote: > OK, that is working now. It should have been documented somewhere Julian > :-) > > We need to find a way to make this kind of changes propagate through the > rest of "make world"... if there is one. At Julian's suggestion, I added the option -DCOMPAT_LINUX_THREADS to CFLAGS in /etc/make.conf. This seems to effectively propagate the option to "make world". To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 07:33:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA05833 for freebsd-current-outgoing; Mon, 21 Dec 1998 07:33:07 -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 HAA05828 for ; Mon, 21 Dec 1998 07:33:05 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.1/8.9.1) id JAA00638; Mon, 21 Dec 1998 09:32:41 -0600 (CST) (envelope-from dick) Message-ID: <19981221093241.C546@tar.com> Date: Mon, 21 Dec 1998 09:32:41 -0600 From: Richard Seaman To: Alfred Perlstein , "Brian W. Buchanan" Cc: Joseph Lee , freebsd-current@FreeBSD.ORG Subject: Re: linking against libc_r References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Alfred Perlstein on Mon, Dec 21, 1998 at 10:25:39AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 21, 1998 at 10:25:39AM -0500, Alfred Perlstein wrote: > > With the recent addition of Linuxthreads to FreeBSD it may soon be possible to use a Wine rpm to play starcraft :) I've had a report already from someone who took the linux threads patches and tried to compile the latest Linux version of WINE. The compilation went ok, but execution did not. WINE uses additional Linux syscalls that are not implemented in our emulator yet, apparently (modify_ldt being the offender that was discovered). -- 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 Mon Dec 21 07:56:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA10096 for freebsd-current-outgoing; Mon, 21 Dec 1998 07:56:07 -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 HAA10086 for ; Mon, 21 Dec 1998 07:56:05 -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 KAA18844; Mon, 21 Dec 1998 10:59:43 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Mon, 21 Dec 1998 10:59:43 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Richard Seaman cc: "Brian W. Buchanan" , Joseph Lee , freebsd-current@FreeBSD.ORG Subject: Re: linking against libc_r In-Reply-To: <19981221093241.C546@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 Mon, 21 Dec 1998, Richard Seaman wrote: > On Mon, Dec 21, 1998 at 10:25:39AM -0500, Alfred Perlstein wrote: > > > > With the recent addition of Linuxthreads to FreeBSD it may soon be possible to use a Wine rpm to play starcraft :) > > I've had a report already from someone who took the linux threads patches > and tried to compile the latest Linux version of WINE. The compilation > went ok, but execution did not. WINE uses additional Linux syscalls that > are not implemented in our emulator yet, apparently (modify_ldt being > the offender that was discovered). wow, everything AND the kitchen sink :/ I think that it's a linux libc call most likely can be munged together. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 08:07:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11448 for freebsd-current-outgoing; Mon, 21 Dec 1998 08:07:56 -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 IAA11443 for ; Mon, 21 Dec 1998 08:07:54 -0800 (PST) (envelope-from dick@tar.com) Received: from ppro.tar.com (ppro [204.95.187.9]) by ns.tar.com (8.9.1/8.9.1) with SMTP id KAA00770; Mon, 21 Dec 1998 10:07:49 -0600 (CST) (envelope-from dick@tar.com) Message-Id: <199812211607.KAA00770@ns.tar.com> From: "Richard Seaman, Jr." To: "Alfred Perlstein" Cc: "freebsd-current@FreeBSD.ORG" Date: Mon, 21 Dec 98 10:07:48 -0600 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: linking against libc_r Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- On Mon, 21 Dec 1998 10:59:43 -0500 (EST), Alfred Perlstein wrote: > >On Mon, 21 Dec 1998, Richard Seaman wrote: > >> On Mon, Dec 21, 1998 at 10:25:39AM -0500, Alfred Perlstein wrote: >> > >> > With the recent addition of Linuxthreads to FreeBSD it may soon be possible to use a Wine rpm to play starcraft :) >> >> I've had a report already from someone who took the linux threads patches >> and tried to compile the latest Linux version of WINE. The compilation >> went ok, but execution did not. WINE uses additional Linux syscalls that >> are not implemented in our emulator yet, apparently (modify_ldt being >> the offender that was discovered). > >wow, everything AND the kitchen sink :/ I think that it's a linux >libc call most likely can be munged together. Actually, on reading my own message it didn't quite make sense, so I actually checked the original message. :) He didn't compile anything, he tried to use a pre-compiled linux binary. Anyway, the basic idea still stands, that our linux emulator needs more upgrading. And, yes, there are already libc LDT routines, so it may be possible that that the upgrade isn't too hard. Dick Richard Seaman, Jr. dick@tar.com 5182 North Maple Lane voice: 414-367-5450 Nashotah, WI 53058 fax: 414-367-5852 PGP key available from: dick-pgp-key@tar.com -----BEGIN PGP SIGNATURE----- Version: 2.6.3a Charset: noconv iQCVAwUBNn5yVOi0Y7619PhpAQG5lQP/bojAPkiblrcx79A+Y54jH0A6SJdu1uOM SvjcGhfikyjUD6pWeQ3VT+Qi8WNfhb1x3Ayx7TFpago2wTaO9rUKHDiQLnsn7TC3 0zdacbMN3N8ipmou+VzrGnJfN/5TlpvT2Ena6iLzXxk0RNgmPjZ9SUBLYi5rr3AY z0UMMwVosb0= =fRcJ -----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 Mon Dec 21 08:31:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA14785 for freebsd-current-outgoing; Mon, 21 Dec 1998 08:31:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA14780 for ; Mon, 21 Dec 1998 08:31:51 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id LAA01708; Mon, 21 Dec 1998 11:30:25 -0500 (EST) Date: Mon, 21 Dec 1998 11:30:25 -0500 (EST) From: Chuck Robey To: Mike Smith cc: "Daniel C. Sobral" , current@FreeBSD.ORG Subject: Re: Pb with COMPAT_LINUX_THREADS In-Reply-To: <199812211040.CAA00481@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, 21 Dec 1998, Mike Smith wrote: > > At Mon, 21 Dec 1998 01:13:24 -0800, you wrote > > > > > >> The ifdef'd version is to let people look at it and think about it.. > > >> possibly as has been suggested, the malloc'd space might only be used if > > >> there is a sharing of signals. Otherwise it might remain in the U area. > > > > > >That's certainly one way of doing it. You could implement structure > > >compression by COW off the parent's copy of the struct instead, that'd > > >be even more efficient. > > > > I have been wondering about this... Multithreading is usually used to improve > > performance. Wouldn't this "on-demand" allocation of shared signals impact of > > performance? > > You typically thread for the concurrency win, and wear the startup cost > as an overhead that you have to pay back with concurrency. Given that > at the moment we're looking at a heavyweight thread implementation, > this extra allocation is relatively trivial in the scheme of things. My semester is over, I'm only now starting to catch up on the interesting stuff on threads ... for scheduling purposes, then, you want to keep track of how many active threads a threaded process has, and have the scheduler grab that many cpus when a context switch occurs? How is the time for the threaded process to be accounted? I see (for purposes of scheduler priorities) that either total cputime given, across all cpus, could be used, if you wanted to keep non-threaded apps on an even parity with threaded apps. Alternatively, if you wanted to give threaded apps a definite win, then you would only keep cpu stats, perhaps, on a parent thread? This topic seems to be going on in two lists concurrently (FreeBSD-smp). I'd think it belongs better in smp, right? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 09:04:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18781 for freebsd-current-outgoing; Mon, 21 Dec 1998 09:04:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA18766 for ; Mon, 21 Dec 1998 09:04:13 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac6.wam.umd.edu ((IDENT root)@rac6.wam.umd.edu [128.8.10.146]) by po3.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id MAA18331; Mon, 21 Dec 1998 12:03:57 -0500 (EST) Received: from rac6.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1]) by rac6.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id MAA19836; Mon, 21 Dec 1998 12:03:56 -0500 (EST) Received: from localhost by rac6.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id MAA19831; Mon, 21 Dec 1998 12:03:55 -0500 (EST) X-Authentication-Warning: rac6.wam.umd.edu: culverk owned process doing -bs Date: Mon, 21 Dec 1998 12:03:55 -0500 (EST) From: Kenneth Wayne Culver To: Alfred Perlstein cc: "Brian W. Buchanan" , Joseph Lee , freebsd-current@FreeBSD.ORG Subject: Re: linking against libc_r 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 Mon, 21 Dec 1998, Brian W. Buchanan wrote: > > > On Sun, 20 Dec 1998, Joseph Lee wrote: > > > > > How do I link against libc_r instead of libc? > > > > > > Trying to build wine from the latest sources, and the configure > > > complains about libc being non-reentrant, which is what libc_r is for, > > > from what I've read. > > > > You need to link with -pthread to get libc_r. I'm not sure that it will > > make the latest WINE work for you, though, as it seems that WINE has > > become increasingly Linux-specific in recent days. (The port hasn't been > > updated since the 9/27 version, I assume because it's becoming too > > difficult a task) If you do manage to get a fairly recent version of wine > > working, please let me know -- I've heard rumors that you can run > > StarCraft under it starting with one of the October snaps, and as soon as > > I can do that, I can newfs my Win95 partition for good. :) > > > > With the recent addition of Linuxthreads to FreeBSD it may soon be possible to use a Wine rpm to play starcraft :) > One thing though, in order for WINE to work with threads, you must get glibc. It won't work otherwise any differently than it will for FreeBSD. Also, the linux emulation must be updated to support USER_LDT's. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 09:30:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23545 for freebsd-current-outgoing; Mon, 21 Dec 1998 09:30:55 -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 JAA23540 for ; Mon, 21 Dec 1998 09:30:51 -0800 (PST) (envelope-from reg@shale.csir.co.za) Received: (from reg@localhost) by shale.csir.co.za (8.9.1/8.9.1) id TAA75028; Mon, 21 Dec 1998 19:27:35 +0200 (SAT) (envelope-from reg) Date: Mon, 21 Dec 1998 19:27:35 +0200 From: Jeremy Lea To: Richard Seaman Cc: Alfred Perlstein , "Brian W. Buchanan" , Joseph Lee , freebsd-current@FreeBSD.ORG Subject: Re: linking against libc_r Message-ID: <19981221192734.E4060@shale.csir.co.za> References: <19981221093241.C546@tar.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=4Ckj6UjgE2iN1+kY X-Mailer: Mutt 0.95i In-Reply-To: <19981221093241.C546@tar.com>; from Richard Seaman on Mon, Dec 21, 1998 at 09:32:41AM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --4Ckj6UjgE2iN1+kY Content-Type: text/plain; charset=us-ascii Hi, Please try the attached port upgrade... Works For Me(tm). On Mon, Dec 21, 1998 at 09:32:41AM -0600, Richard Seaman wrote: > On Mon, Dec 21, 1998 at 10:25:39AM -0500, Alfred Perlstein wrote: > > > > With the recent addition of Linuxthreads to FreeBSD it may soon be > > possible to use a Wine rpm to play starcraft :) > > I've had a report already from someone who took the linux threads patches > and tried to compile the latest Linux version of WINE. The compilation > went ok, but execution did not. WINE uses additional Linux syscalls that > are not implemented in our emulator yet, apparently (modify_ldt being > the offender that was discovered). Wine seems to want clone(), from a quick read of the man page. Does the native LinuxThreads stuff implement this as a FreeBSD syscall? Regards, -Jeremy -- | "Come home my prodigal son, come home and lets be one, --+-- don't want to see you cry, don't make me tell you why, | you've lived in a house with me, my blood has set you free, | in the world you'll surely die, nothing else will satisfy." -MIC --4Ckj6UjgE2iN1+kY Content-Type: application/x-tar-gz Content-Disposition: attachment; filename="wine.tgz" Content-Transfer-Encoding: base64 H4sIAFGDfjYAA+0c+3viNnJ/jf+KaTa3BxsefmDzyLLfsuCk3PLIh8mle7f9XGMLcOMHtU0S muZ/v5FsCCRsyfYSctcyIcgejzTSSDOakWSubI/kXz0vQIEvyjK8AhCKspCkPE3nwAMoioRI oaDgtcALcuEVyM9cLwbTMDICgFcBGW2gI0G4jQptF65o/7eNCzK0HfJMPASeVwqFr/a/IIrF ef/zCi8gRijyxVfAP1N9VuAv3v+voUOuYOIHUQim7zjEjGzfAzcZETD0gwrtJDpOuNfwTxQC fR6QX6Z2QCz2DMolXhaK+LhhRATMgGCSPKKgGZQGOv4lCOWyAjxfkcWKKEJb7WOm87HvVvb2 9kJkgLcHTcw6H5EZzJJTZJqvlBf4vCDh4KjwSoUvwM8hGZEA1OsJHGBOrlHrq9W9vXJJEAWB azS1fqfWRsw5Vj17cEMf33Knn05i7NUyto7fJ91eU9Wqe8SdOkbkByHXrml9tadrzT7FH9ws 3evaWYemt9wq8mOj2avu1Vqn39fyTLUsckkcf+ISL+KQttnp47+KNCH5cBwQ8lFr5Lq9E45r NT/qDfVU7TSQ1w8TN1eoHNycdnt9DYu8zY8CYzK2zTB/PXE57rz3SevVsbEHN3jJCFbac9I5 0+vdznHz5KyHbZ2RkDvTVP2kXfuU3LZrHQHz01w5geMmAckOprZjVbi9PdMCVi6yuIU3b4C2 /JN6CxaZEM9CYj+MsraHiuM4lP7gptnR+rVWS0futdu7zKxSOduzEXXaU4+bP9zmSWTGaNP3 hhyHT01nahF4NwitHB2HOffiPffSavGXATZIqaaFz+cFfNv8r1D7Lyq7+X8rsNT/rvVMAt8w /wMUC3H/F2QkFdn8L/K7+X8b0G7IkGIzZDxv5lAaudGvaaiCZcrCsDQ0DHFAhmVelkx5qAim JYlDQ7QUcWek/wTA9H9iROb4+WaAb7L/RYnqv0L9/539f35Y6X+WZg3riXlsiv94UUnsf7HI S7T/JUmQdvZ/G5DNZmHupef8wB7tnRMLumYEogBCqcJLFUFh4Rd3eHi4IN1rYxDYICajkisy UhViqg8fIFsoZIpwyL4/fOBAm4URcatm5Qtmt/yr8EvIMBz0iTupksoXDk6NaLxEcfSA+AjJ 6H9EwuhoiFmy2swd+E7fGDjkGB2Yai6OK8KZyx3ef5afhkHe8U3DyTv24I4QOPi3P6Ehb/gj BzUHSeLa1n0HQ8AqDl3WIlnOYOh5GCe0TQ0yNKZOhNMk6os/INnIdkmYZQXiSLENh8XUP3LZ uu8KVRoH5s2pwbN7cXEvcId3z6NoZvEMId4hBA4QIcUI17eIm5FKBawWRReW0Iz1xAgwKCML 5q1JlBTuTLDo5duIjys78X2HBNj61mlfqFR/cybBbmb/y8A6++8+MY9N/n+hIC38fxkJqf3n 5Z393wYk9p8a2ryFVssf5cx4HuhPCVuyEwsgihWxjJ+VeWAly/35oECX9xbzQTmjwGE5U2aW 8/VixcexXTsKc+P3y8gwstBCP0AGtjeiyMPX9tAiQ9D1ZPVM1yluQTgL8yQIPD+mJZ5lD5cK 2k/qnRvvL2OTVtxDBvYlobiX7qJnhXX67z0xj036L8t38b9CfUHq/4k7/d8GUP13iesHs/yl HURTw5nrv2ZEzA+UUKNRnfmKtKT/97Pc13/8lO70X+DLRWoCWBpbAQr2EFL+4Od0fHfDLcLB 5EH2fTSbEKhW4ZMkdj/+Q2+rbb1dOz1VG/pxs6WmmTXwqDloa7r2uVNHBN7hkJ4jgJ9bgQXJ gssSQ7ZLQaKWEUZqEPhBCtRer9vTa62eWmt81tUfmlpfg/TRapax4VkOVhC+r3UaLVVn/mMK Tnvduqppen0aBMSLUukMYGsy/5OGZJ3+B0/MY4P+K0JxPv8rSkESmf4Xdvq/FaD6T3di7NE0 ILHiHwc2U2WBqbKo4OdO8Re0KxqvVAr4WdJ4URFkGgMmKdV4qtSGqdP4LQ0BiaaBBxjcHM2v +SO45UDtHnNZJL2BFLk0HCDm2L9jilURyhX4sn+AJTm2d/FlPw3C+zfyUUI+x6dBZFi2f0VZ QjZkxbDwEaIx8bjDp2DzjkVT3tRxHsERB3vgQjYYLh68pTgszLzUTZ1cRyTw9EmAJuy6uj8j ITokxAlJIlJZiUXKUirSb5eewm9Feo9l85TSM0JXj/3ENaLDeYeJjqVUdH94ABZ5YRsifDSb pxSh5TgPZVeUSkx2cco02Yvgra4zP1uniyp0/SSVvknk+MadsUdHKE3XsOkT5OYRM0rxmcF0 mBFlOX0E5NqOUt8ltOmjx4i+IP7Xoqe4VC5/JxdaDZpjIcbf75bHVuFx3fKI2iw6js7UtJsw OjJ1jH28KDC8qEo385d6qyTFRiJO/5CRKBW2YiQezeYpRjgrcj8e58OpZ+q0eHpRvTfcJUEQ qQCTlAqQ9gmk+DQT3kbxYUblhUfp46vw9KO0siLLUimWZWluOiBWe5560puHoiSUX1rjH1+F p5dlPFxD+1fiD9HOeiP2Vf0JDe6iPKzDT8siFyWeiTxOqchDDH/ccJRKf6shwDIKWzAEj2fz 1IYALakelz7QL43ggSmQixKTZZxSWe6h1PY2C04uFl962D66Cs81bE39yg8u0BvDATwynAjD LPNixbt46dBnB6/Wxv8D44l5bIj/RVkU5/G/KBbF3frfFiGJ/0PfIXkafrrz5b/V8F4uVuTy yirAco4V4mKFLy/2jNnqn6BkynAYJ/O1v3XwNnSMS7qcNrTCI+pqfQ3oUgLlDN9VoXPWaqW5 7FdpE4jMkERGFAWpVMwmnX2v03Nvnp+Bfl2rdbrnGaCFomty+IdLe1jW7zYCtY9O79/QDts3 I2dtG5rdunbe7Gj/ykBS7GNasra8r5W2oUs8w11qyibOgMG6OZmxXBmYRKFOr5ALGzMFKVPC McOSe2Mm8WGOay1NXakTrUPq7cS2qkOcelLpNF065tNw81CsG4dDo1drdjLwJunFBwWEkwDD 4GGKxrOwn9Wur/9m7Wcg9dY1QsxzV9y6TtgwfO7xfpD9kbzXDT5yTUxnktpniot5FhesLNZx a3KpvV4qUXnMQugKeXzKH6f3+NBEPX4KrLgv3v563uj5C/MOVlhoECfrjMItt+4ytje6M3SM EfxWBbX+fXepd5YFe78jfl+2X8+5Nt/SqEuGY793prKg5qUt+rfBuvl/8MQ8Nu3/SaI8n/+l glCk879YLOzm/20Anf/pTI7xj2140brZv1jBz3w7j87+K/T3Scv01Zy7fQC29Y/fxXt7/3c7 +pv2/l0jGic7/3PU0PGN6B4ZPX/FUPj30kL9P4J1+39XT8xjk/4r8tz/l0VBSc5/7t7/2wpQ /U90KO9YqFSr+g9FEMRKoYQ+/Z3+r9Df3/kvV7BrF/pfkqj+47cgJovR8w36E7Wva2pLP27V TrRUSJw0joQUFqnTuT3UTX8y+zcSqPV+t6f3u7ra6fc+M8If0bncdBDIDwPiWEZE5oeGlggv k5cY34Eo8gh3pwaOmz2tr7ca/ZgbZVtrtbp1HJ6L00R3p4o2ZhKKtMX5tygf6jdQYqwINgHs EAyID7bSe2JG6FKl7BzJgedH4BqeMSIWDGZA381Iw9v8Mxm1WP8vRs/5Dvi3nP+Xefb+d1Hi d+f/twGL/q93220cv8/BY/P7X7T/RfzjC8UiPf8l8uLO/9sKtLXseXwmEqSckC/L+U4f5q9A 07e/4cyzryFVcyZjA2MdhxghSed2LtafBBb631C1eu95eGx6/0dQqP/HS7JUKCTv/yq79z+3 A+fMKaHeyNwMLJQ/mHoeXeCZehZJzAA6TbZUUiBleBaM7dGYBGmon56FOa4Z0WLCyHYciI3F L1PDsaNZBphbY/ne3yMg1xP0dcCOIPIpA5j50wCi2cQ2DQccIxgR4JZskjGZOHZ8wAQmhnmB XhFdq2IlIDvmgdkRcWasalEIV8YMcrkcx/V9wC5j7lMm5nJBAg9dLxd7HAYEbRn9wYMIruxo TPeu0Ng5jn9FW+xQoRiWRSwOq7mcOd5hA/bTGKk8PW1O5cH2xfLvPiNh2zDHmPt9usJxyYtF e3tnmtqjDiLHMXGjFbVJSGtM2c437eJGspKX3lZa+bkEFBqHaWTYHlyicC0wwtAeefTXJbC8 YdxJlh0wf5LywOo3uhqws+zgkAjd0DDD0d6jpt0kASvLx3oEkFQX0McmsI8uKDtyss8oLYKE ToiGHxuJeOxk10c5TgJ/YAxQ/GO6co/c8EMs2jlRBowhsmNtTH4sgvXMS4/4HSzDwv6ftpra s3h/m/0/YXH+X5Flgb3/jzc7+78NGNhe3vJD17c4esl+5mf1J1rm0T4bKYv3Zx6g6VF9iqev V+I/y29wKy9bvnRbd7CDHazCfwBUT/0IAFAAAA== --4Ckj6UjgE2iN1+kY-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 09:31:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23634 for freebsd-current-outgoing; Mon, 21 Dec 1998 09:31:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles130.castles.com [208.214.165.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA23629 for ; Mon, 21 Dec 1998 09:31: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 JAA02261; Mon, 21 Dec 1998 09:29:09 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812211729.JAA02261@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Chuck Robey cc: Mike Smith , "Daniel C. Sobral" , current@FreeBSD.ORG Subject: Re: Pb with COMPAT_LINUX_THREADS In-reply-to: Your message of "Mon, 21 Dec 1998 11:30:25 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Dec 1998 09:29:09 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I have been wondering about this... Multithreading is usually used to improve > > > performance. Wouldn't this "on-demand" allocation of shared signals impact of > > > performance? > > > > You typically thread for the concurrency win, and wear the startup cost > > as an overhead that you have to pay back with concurrency. Given that > > at the moment we're looking at a heavyweight thread implementation, > > this extra allocation is relatively trivial in the scheme of things. > > My semester is over, I'm only now starting to catch up on the > interesting stuff on threads ... for scheduling purposes, then, you want > to keep track of how many active threads a threaded process has, and > have the scheduler grab that many cpus when a context switch occurs? No. You want to schedule each individual thread as though it were a process in and of itself. > How is the time for the threaded process to be accounted? I see (for > purposes of scheduler priorities) that either total cputime given, > across all cpus, could be used, if you wanted to keep non-threaded apps > on an even parity with threaded apps. Alternatively, if you wanted to > give threaded apps a definite win, then you would only keep cpu stats, > perhaps, on a parent thread? In the current LinuxThreads support mode, threads are processes, so each thread's time is accounted against itself. -- \\ 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 Dec 21 09:34:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23898 for freebsd-current-outgoing; Mon, 21 Dec 1998 09:34:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles130.castles.com [208.214.165.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA23893 for ; Mon, 21 Dec 1998 09:34:05 -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 JAA02300; Mon, 21 Dec 1998 09:31:44 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812211731.JAA02300@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Richard Seaman cc: freebsd-current@FreeBSD.ORG Subject: Re: linking against libc_r In-reply-to: Your message of "Mon, 21 Dec 1998 09:32:41 CST." <19981221093241.C546@tar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Dec 1998 09:31:44 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, Dec 21, 1998 at 10:25:39AM -0500, Alfred Perlstein wrote: > > > > With the recent addition of Linuxthreads to FreeBSD it may soon be possible to use a Wine rpm to play starcraft :) > > I've had a report already from someone who took the linux threads patches > and tried to compile the latest Linux version of WINE. The compilation > went ok, but execution did not. WINE uses additional Linux syscalls that > are not implemented in our emulator yet, apparently (modify_ldt being > the offender that was discovered). We're fairly close to supporting these (they're not libc functions but syscalls), but it will require some surgery in our current LDT support functions, as they use copyin/out rather than uiomove, and as such you can't call them as-is from within the Linux emulator. This is all just brute-force work; if you have a little time to spare, diffs would be appreciated... -- \\ 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 Dec 21 09:39:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24423 for freebsd-current-outgoing; Mon, 21 Dec 1998 09:39:53 -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 JAA24417 for ; Mon, 21 Dec 1998 09:39:49 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac6.wam.umd.edu ((IDENT root)@rac6.wam.umd.edu [128.8.10.146]) by po4.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id MAA01183; Mon, 21 Dec 1998 12:07:32 -0500 (EST) Received: from rac6.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1]) by rac6.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id MAA19896; Mon, 21 Dec 1998 12:06:58 -0500 (EST) Received: from localhost by rac6.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id MAA19890; Mon, 21 Dec 1998 12:06:57 -0500 (EST) X-Authentication-Warning: rac6.wam.umd.edu: culverk owned process doing -bs Date: Mon, 21 Dec 1998 12:06:57 -0500 (EST) From: Kenneth Wayne Culver To: Alfred Perlstein cc: Richard Seaman , "Brian W. Buchanan" , Joseph Lee , freebsd-current@FreeBSD.ORG Subject: Re: linking against libc_r 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 > > > With the recent addition of Linuxthreads to FreeBSD it may soon be possible to use a Wine rpm to play starcraft :) > > > > I've had a report already from someone who took the linux threads patches > > and tried to compile the latest Linux version of WINE. The compilation > > went ok, but execution did not. WINE uses additional Linux syscalls that > > are not implemented in our emulator yet, apparently (modify_ldt being > > the offender that was discovered). > > wow, everything AND the kitchen sink :/ I think that it's a linux > libc call most likely can be munged together. I think it may be something that needs to go in the linux kernel emulation. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 09:48:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA25387 for freebsd-current-outgoing; Mon, 21 Dec 1998 09:48:48 -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 JAA25382 for ; Mon, 21 Dec 1998 09:48:47 -0800 (PST) (envelope-from erikf@visi.com) Received: from odin (h-178-184.mn.mediaone.net [209.32.178.184]) by chmls11.mediaone.net (8.8.7/8.8.7) with SMTP id MAA14599 for ; Mon, 21 Dec 1998 12:48:41 -0500 (EST) Message-ID: <003901be2d0a$6da7f800$0200a8c0@mn.mediaone.net> From: "Erik Funkenbusch" To: Subject: Broken ipfw? Date: Mon, 21 Dec 1998 11:47:15 -0600 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 After cvsuping on saturday natd has suddenly stopped working with the kernel I built on saturday and after cvsuping today and rebuilding as well. After executing an ipfw rule it responds with: ip_fw_ctl: empty interface name /sbin/ipfw: setsockopt(IP_FW_ADD): Invalid Argument and of course no routing occurs. Any ideas? I'm planning on rebuilding world to see if it was some fix to both kernel and natd, but I can't seem to find anything in the cvs list that would indicate a change here. I'm using the de0 driver on an Asante NIC. I can ping anything on that network, and I can ping stuff on my private network using the xl0 driver. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 09:49:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA25461 for freebsd-current-outgoing; Mon, 21 Dec 1998 09:49:54 -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 JAA25448 for ; Mon, 21 Dec 1998 09:49:44 -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 SAA17402; Mon, 21 Dec 1998 18:44:28 +0100 (MET) Message-ID: <367E88FB.B9F0D79@we.lc.ehu.es> Date: Mon, 21 Dec 1998 18:44:27 +0100 From: =?iso-8859-1?Q?Jos=E9=20M=AA?= Alcaide Organization: Universidad del =?iso-8859-1?Q?Pa=EDs?= Vasco - Dept. de Electricidad y =?iso-8859-1?Q?Electr=F3nica?= X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.8-RELEASE i386) X-Accept-Language: es-ES,es,en-US,en MIME-Version: 1.0 To: Stephen Palmer CC: gp@oitunix.oit.umass.edu, freebsd-current@FreeBSD.ORG Subject: Re: Request fo help with Zip Drive on vpo0 in -current] References: <19981219130349.11043.qmail@www0f.netaddress.usa.net> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > gp@oitunix.oit.umass.edu wrote: > > On Fri, Dec 18, 1998 at 02:46:24AM +0000, Stephen Palmer wrote: > > > Can someone offer assistance in getting a Parallel Port Zip Drive > > > working under FreeBSD 3.0-current? I've searched the mailing lists > > > and LINT, and added what I thought were the correct options. > > > As you can read in my dmesg output below, my ppbus and vpo0 do > > > get detected, but da0 and scbus do not. A gentle nudge in the right > > > direction would be most graciously appreciated! > > > > > > Stephen L. Palmer > > > slpalmer@netscape.net > > > > I think this got broken in -current. I had my ||-port zip running > > on -current from the last week or so of Nov., but it didn't work > > with sources from Dec. 12. > > > > I hope the cross-post is appropriate here. I thought some > > -current types should see this. > > I regret to say a "me, too", but this is the truth. We had a parallel ZIP working under FreeBSD-current. This morning we "made the world" and now it does not work. The parallel port and the ZIP drive are found, but the "da" device is not initialized. What happened? -- 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 Mon Dec 21 09:51:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA25662 for freebsd-current-outgoing; Mon, 21 Dec 1998 09:51: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 JAA25652 for ; Mon, 21 Dec 1998 09:51:47 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.1/8.9.1) id LAA05522; Mon, 21 Dec 1998 11:49:39 -0600 (CST) (envelope-from dick) Message-ID: <19981221114939.A5500@tar.com> Date: Mon, 21 Dec 1998 11:49:39 -0600 From: Richard Seaman To: Jeremy Lea Cc: Alfred Perlstein , "Brian W. Buchanan" , Joseph Lee , freebsd-current@FreeBSD.ORG Subject: Re: linking against libc_r References: <19981221093241.C546@tar.com> <19981221192734.E4060@shale.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19981221192734.E4060@shale.csir.co.za>; from Jeremy Lea on Mon, Dec 21, 1998 at 07:27:35PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 21, 1998 at 07:27:35PM +0200, Jeremy Lea wrote: > > Wine seems to want clone(), from a quick read of the man page. Does the > native LinuxThreads stuff implement this as a FreeBSD syscall? The FreeBSD "port" of Linux threads does not use nor implement a clone syscall. It uses rfork instead within pthread_create to simulate the clone call. If Wine calls "clone" directly, rather than via the phread_create call, it would be easy enough to implement a FreeBSD call, either in libc or as a syscall, that mimics clone. Actually, there are already two "clone" calls within Linux Threads right now. There is a wrapper "clone" call that wraps the clone syscall (see clone.S in the linux threads source). -- 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 Mon Dec 21 10:15:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29136 for freebsd-current-outgoing; Mon, 21 Dec 1998 10:15:34 -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 KAA29131 for ; Mon, 21 Dec 1998 10:15:29 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.1/8.9.1) id MAA05576; Mon, 21 Dec 1998 12:01:16 -0600 (CST) (envelope-from dick) Message-ID: <19981221120116.B5500@tar.com> Date: Mon, 21 Dec 1998 12:01:16 -0600 From: Richard Seaman To: Kenneth Wayne Culver , Alfred Perlstein Cc: "Brian W. Buchanan" , Joseph Lee , freebsd-current@FreeBSD.ORG Subject: Re: linking against libc_r References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Kenneth Wayne Culver on Mon, Dec 21, 1998 at 12:03:55PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 21, 1998 at 12:03:55PM -0500, Kenneth Wayne Culver wrote: > One thing though, in order for WINE to work with threads, you must get > glibc. It won't work otherwise any differently than it will for FreeBSD. > Also, the linux emulation must be updated to support USER_LDT's. It appears that glibc is already included in the linux emulation if you install the latest linux_lib port. However, it isn't fully identified as such (its just libc.so.6). It appears to work ok with linux threads based on preliminary testing (assuming you are using the very latest 3.0 with COMPAT_LINUX_THREADS enabled). As far as using the Linux threads "port", it doesn't need glibc to run threads. Is there something about Wine that is specfic to glibc? However, linking the Linux threads "port" with the FreeBSD libc will not get you a 100% thread safe solution, yet, as there are some libc functions that are not thread safe yet, and there is no implementation of cancellation points, yet. -- 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 Mon Dec 21 10:29:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA00891 for freebsd-current-outgoing; Mon, 21 Dec 1998 10:29:47 -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 KAA00870 for ; Mon, 21 Dec 1998 10:29:40 -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 UAA27068; Mon, 21 Dec 1998 20:29:13 +0200 (SAT) From: John Hay Message-Id: <199812211829.UAA27068@zibbi.mikom.csir.co.za> Subject: Re: Current Sync Serial Adapters Support In-Reply-To: <367A6DCB.3C7FD331@liberty.bulinfo.net> from Krassimir Slavchev at "Dec 18, 98 04:59:23 pm" To: krassi@liberty.bulinfo.net (Krassimir Slavchev) Date: Mon, 21 Dec 1998 20:29:13 +0200 (SAT) Cc: freebsd-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 > We have bought Digi Sync/570ip (PCI version) serial multiport adapter > but it is currently unsupported in the FreeBSD source tree. > Are there some plans for including such a driver in Current FreeBSD. If > anyone plans to make something about this, pls be so kind > to contact us. Well I wanted to do it, so I organised a card and got the hardware manual from their ftp site only to find that the manual is very outdated and unusable. After a few emails and forms filled in on their web site, the only thing that has happened is that they removed the file from their ftp site. :-( I have also tried the email adresses of the people that helped me when I wrote the ISA driver, but they must have left because those emails just bounced with an user unknown message. 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 Mon Dec 21 10:57:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA04858 for freebsd-current-outgoing; Mon, 21 Dec 1998 10:57:16 -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 KAA04850 for ; Mon, 21 Dec 1998 10:57:13 -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 TAA19274 for current@freebsd.org; Mon, 21 Dec 1998 19:02:34 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id CEA931513; Mon, 21 Dec 1998 08:58:41 +0100 (CET) Date: Mon, 21 Dec 1998 08:58:41 +0100 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: Pb with COMPAT_LINUX_THREADS Message-ID: <19981221085841.A10810@keltia.freenix.fr> Mail-Followup-To: current@freebsd.org References: <19981221000330.A6587@keltia.freenix.fr> <19981220223813.A268@tidalwave.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <19981220223813.A268@tidalwave.net>; from Lee Cremeans on Sun, Dec 20, 1998 at 10:38:13PM -0500 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4871 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Lee Cremeans: > When you see this, it usually means libkvm needs to be rebuilt. Do that, > then rebuild everything that uses it (ps, top, systat, several others). I did write this was _after_ "make world" so the problem cannot happen... unless there is an hidden catch which Julian explained. It works after recompiling libkvm with the COMPAT_LINUX_THREADS option of course. The problem is that the change is not transparent at all and we need to find a way to deal with it... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #2: Sun Nov 8 01:22:20 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 12:43:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA22200 for freebsd-current-outgoing; Mon, 21 Dec 1998 12:43:30 -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 MAA22194 for ; Mon, 21 Dec 1998 12:43:29 -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 PAA06696; Mon, 21 Dec 1998 15:45:11 -0500 (EST) Received: (from shmit@localhost) by natasya.noc.erols.net (8.9.1/8.9.1) id PAA22578; Mon, 21 Dec 1998 15:43:18 -0500 (EST) Message-ID: <19981221154318.B21819@kublai.com> Date: Mon, 21 Dec 1998 15:43:18 -0500 From: Brian Cully To: "Jordan K. Hubbard" , Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: I almost hate to suggest this... Reply-To: shmit@kublai.com References: <199812190832.TAA26239@godzilla.zeta.org.au> <81421.914056557@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <81421.914056557@zippy.cdrom.com>; from Jordan K. Hubbard on Sat, Dec 19, 1998 at 12:35:57AM -0800 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 Sat, Dec 19, 1998 at 12:35:57AM -0800, Jordan K. Hubbard wrote: > > mount_foo should almost never be used directly. It should be in /libexec > > Then why have mount_foo at all? I think the right question is `why have mount_foo in /sbin at all?' The answer for which I do not know. :-) Bruce is right (of course), mount_foo should be in /libexec and mount itself should only have enough code to call the right program (like it does now, except that the UFS code wouldn't be there). -- Brian Cully You think you're queer? I've got news for you: we're all queer. If you get befuddled by a middle class morality, shut it out. Shut it out.... Is there an absolute morality? I don't think so. You think so? Act that way. -- Glengarry Glen Ross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 14:00:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00919 for freebsd-current-outgoing; Mon, 21 Dec 1998 14:00:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shell2.la.best.com (shell2.la.best.com [209.24.216.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00910 for ; Mon, 21 Dec 1998 14:00:11 -0800 (PST) (envelope-from nugundam@shell2.la.best.com) Received: from localhost (nugundam@localhost) by shell2.la.best.com (8.9.1/8.9.0/best.sh) with ESMTP id OAA19700 for ; Mon, 21 Dec 1998 14:00:08 -0800 (PST) Date: Mon, 21 Dec 1998 14:00:08 -0800 (PST) From: Joseph Lee To: freebsd-current@FreeBSD.ORG Subject: Re: linking against libc_r In-Reply-To: <19981221120116.B5500@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 Mon, 21 Dec 1998, Richard Seaman wrote: > On Mon, Dec 21, 1998 at 12:03:55PM -0500, Kenneth Wayne Culver wrote: > > > One thing though, in order for WINE to work with threads, you must get > > glibc. It won't work otherwise any differently than it will for FreeBSD. > > Also, the linux emulation must be updated to support USER_LDT's. So building the kernel with USER_LDTs is only useful if wine is built under freebsd then. [snip] > as such (its just libc.so.6). It appears to work ok with linux threads > based on preliminary testing (assuming you are using the very latest > 3.0 with COMPAT_LINUX_THREADS enabled). I shall need to do this also then.. Current builds of wine that force configure to recognize that it can modify_ldt seems to compile fine, but the resulting executable still fails to start up the install.exe for starcraft. I'll update further after I finish a buildworld with recent sources. -- Joseph nugundam =best=com==/==\=IIGS=/==\=Playstation=/==\=Civic HX CVT=/==\ # Anime Expo 1998 >> www.anime-expo.org/ > # Redline Games >> www.redlinegames.com/ > # Cal-Animage Epsilon >> www.best.com/~nugundam/epsilon/ > # EX: The Online World of Anime & Manga >> www.ex.org/ / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 15:42:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA11990 for freebsd-current-outgoing; Mon, 21 Dec 1998 15:42:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from home.fiberia.com (home.fiberia.com [208.137.248.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA11975 for ; Mon, 21 Dec 1998 15:42:32 -0800 (PST) (envelope-from www@home.fiberia.com) Received: by home.fiberia.com (8.9.1/8.9.1) id QAA11290; Mon, 21 Dec 1998 16:42:35 -0800 (PST) Date: Mon, 21 Dec 1998 16:42:35 -0800 (PST) Message-Id: <199812220042.QAA11290@home.fiberia.com> X-Fiberia-User: ufa X-Fiberia-Real-Address: kat@diaspro.com To: freebsd-current@FreeBSD.ORG From: happyadmin@ufa.hypermart.net Subject: MARRY CHRISTMAS & Happy New Year! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ~ Ñ×ÀÑÒËÈÂÎÃÎ ÐÎÆÄÅÑÒÂÀ è ÍÎÂÎÃÎ ÃÎÄÀ! ~ ÑÄÅËÀÉÒÅ ÑÞÐÏÐÈÇ ÑÂÎÈÌ ÄÐÓÇÜßÌ! Ïîøëèòå Íîâîãîäíèå è Ðîæäåñòâåíñêèå Ïîñëàíèÿ ñ ìóçûêàëüíûì ñîïðîâîæäåíèåì, âîñïîëüçîâàâøèñü ÑËÓÆÁÎÉ ÂÈÐÒÓÀËÜÍÛÕ ÎÒÊÐÛÒÎÊ, àáñîëþòíî ÁÅÑÏËÀÒÍÎ !! --*( ÑËÓÆÁÀ ÂÈÐÒÓÀËÜÍÛÕ ÎÒÊÐÛÒÎÊ )*-- * http://ufa.hypermart.net * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 15:55:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13611 for freebsd-current-outgoing; Mon, 21 Dec 1998 15:55:00 -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 PAA13603 for ; Mon, 21 Dec 1998 15:54:59 -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 PAA01176 for ; Mon, 21 Dec 1998 15:52:47 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812212352.PAA01176@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: trap 12 with interrupts disabled Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Dec 1998 15:52:47 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just thought after all the discussion about X servers and interupts, this one might be interesting: pid 281 (Xaccel): trap 12 with interupts disabled -- \\ 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 Dec 21 17:09:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA23936 for freebsd-current-outgoing; Mon, 21 Dec 1998 17:09:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA23919 for ; Mon, 21 Dec 1998 17:09:14 -0800 (PST) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.8.8/8.8.8) with SMTP id JAA09380 for ; Tue, 22 Dec 1998 09:09:07 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id JAA09102; Tue, 22 Dec 1998 09:09:07 +0800 Message-Id: <199812220109.JAA09102@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: Recent kernels crash immediately Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 22 Dec 1998 09:09:07 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As at about cvs-cur.4912, I'm seeing kernels die upon booting just after the first line of kernel printfs "BIOS mumble mumble". This is on two separate machines. Anyone else seeing this? Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 17:29:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA26427 for freebsd-current-outgoing; Mon, 21 Dec 1998 17:29:59 -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 RAA26416 for ; Mon, 21 Dec 1998 17:29:57 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac10.wam.umd.edu ((IDENT root)@rac10.wam.umd.edu [128.8.10.150]) by po4.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id UAA24763 for ; Mon, 21 Dec 1998 20:30:26 -0500 (EST) Received: from rac10.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1]) by rac10.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id UAA29648 for ; Mon, 21 Dec 1998 20:29:51 -0500 (EST) Received: from localhost by rac10.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id UAA29642 for ; Mon, 21 Dec 1998 20:29:50 -0500 (EST) X-Authentication-Warning: rac10.wam.umd.edu: culverk owned process doing -bs Date: Mon, 21 Dec 1998 20:29:50 -0500 (EST) From: Kenneth Wayne Culver To: freebsd-current@FreeBSD.ORG Subject: recent linux emu 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 cvsupped the latest linux kernel, and now my WordPerfect 8 for linux doesn't work. I just thought that you all should know. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 18:07:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA01595 for freebsd-current-outgoing; Mon, 21 Dec 1998 18:07:36 -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 SAA01572 for ; Mon, 21 Dec 1998 18:07:33 -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 SAA02027 for ; Mon, 21 Dec 1998 18:05:20 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812220205.SAA02027@dingo.cdrom.com> Date: Mon, 21 Dec 1998 18:05:20 -0800 From: Mike Smith Subject: Re: recent linux emu Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To: undisclosed-recipients:; ------- Blind-Carbon-Copy X-Mailer: exmh version 2.0.2 2/24/98 To: Kenneth Wayne Culver cc: emulation@freebsd.org, sos@freebsd.org Subject: Re: recent linux emu In-reply-to: Your message of "Mon, 21 Dec 1998 20:29:50 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Dec 1998 18:05:20 -0800 From: Mike Smith > I cvsupped the latest linux kernel, and now my WordPerfect 8 for linux > doesn't work. I just thought that you all should know. Posting here on -current isn't going to help you much. You should be posting this on -emulation. I've copied Soren, as it's likely one of his changes that's done 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 ------- End of Blind-Carbon-Copy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 18:14:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA02752 for freebsd-current-outgoing; Mon, 21 Dec 1998 18:14:30 -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 SAA02742 for ; Mon, 21 Dec 1998 18:14: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 MAA01259; Tue, 22 Dec 1998 12:44:09 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id MAA08491; Tue, 22 Dec 1998 12:44:11 +1030 (CST) Message-ID: <19981222124410.R85005@freebie.lemis.com> Date: Tue, 22 Dec 1998 12:44:10 +1030 From: Greg Lehey To: Mike Smith , current@FreeBSD.ORG Subject: Re: trap 12 with interrupts disabled References: <199812212352.PAA01176@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199812212352.PAA01176@dingo.cdrom.com>; from Mike Smith on Mon, Dec 21, 1998 at 03:52:47PM -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 Monday, 21 December 1998 at 15:52:47 -0800, Mike Smith wrote: > > Just thought after all the discussion about X servers and interupts, > this one might be interesting: > > pid 281 (Xaccel): trap 12 with interupts disabled Yes, I've noticed this one too. It seems to have crept in relatively recently, and strangely seems not to cause any problems. 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 Mon Dec 21 18:17:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA03069 for freebsd-current-outgoing; Mon, 21 Dec 1998 18:17:55 -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 SAA03064 for ; Mon, 21 Dec 1998 18:17:54 -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 SAA02097; Mon, 21 Dec 1998 18:15:01 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812220215.SAA02097@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Stephen Hocking-Senior Programmer PGS Tensor Perth cc: current@FreeBSD.ORG Subject: Re: Recent kernels crash immediately In-reply-to: Your message of "Tue, 22 Dec 1998 09:09:07 +0800." <199812220109.JAA09102@ariadne.tensor.pgs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Dec 1998 18:15:01 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As at about cvs-cur.4912, I'm seeing kernels die upon booting just after the > first line of kernel printfs "BIOS mumble mumble". This is on two separate > machines. Anyone else seeing this? Can you expand on "die"? There was a fubar over the weekend which would result in a "shouldn't get here" panic immediately on startup, which is fixed in sys/i386/conf/Makefile.i386 rev 1.132. -- \\ 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 Dec 21 18:18:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA03138 for freebsd-current-outgoing; Mon, 21 Dec 1998 18:18:39 -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 SAA03127 for ; Mon, 21 Dec 1998 18:18:37 -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 SAA02117 for ; Mon, 21 Dec 1998 18:16:25 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812220216.SAA02117@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: Re: trap 12 with interrupts disabled In-reply-to: Your message of "Tue, 22 Dec 1998 12:44:10 +1030." <19981222124410.R85005@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Dec 1998 18:16:25 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Monday, 21 December 1998 at 15:52:47 -0800, Mike Smith wrote: > > > > Just thought after all the discussion about X servers and interupts, > > this one might be interesting: > > > > pid 281 (Xaccel): trap 12 with interupts disabled > > Yes, I've noticed this one too. It seems to have crept in relatively > recently, and strangely seems not to cause any problems. The diagnostic just warns of a bad situation (Xaccel has turned off interrupts for some reason, and then pagefaulted), it doesn't mention that it has in fact turned interrupts back on so that the pagefault can be safely completed. -- \\ 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 Dec 21 18:23:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA03709 for freebsd-current-outgoing; Mon, 21 Dec 1998 18:23:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA03704 for ; Mon, 21 Dec 1998 18:23:55 -0800 (PST) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.8.8/8.8.8) with SMTP id KAA02372; Tue, 22 Dec 1998 10:23:45 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id KAA09334; Tue, 22 Dec 1998 10:23:45 +0800 Message-Id: <199812220223.KAA09334@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith cc: current@FreeBSD.ORG Subject: Re: Recent kernels crash immediately In-reply-to: Your message of "Mon, 21 Dec 1998 18:15:01 PST." <199812220215.SAA02097@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 22 Dec 1998 10:23:45 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > As at about cvs-cur.4912, I'm seeing kernels die upon booting just after the > > first line of kernel printfs "BIOS mumble mumble". This is on two separate > > machines. Anyone else seeing this? > > Can you expand on "die"? There was a fubar over the weekend which > would result in a "shouldn't get here" panic immediately on startup, > which is fixed in sys/i386/conf/Makefile.i386 rev 1.132. Yes, that's the one. I read the current email this morning after sending the message (bad move!). I'll test it as soon as I get home, after fetching the latest cvs-cur update. My mistake. I'll also be giving this COMPAT_LINUX_THREADS stuff a whirl. Looks rather like the AIX 4.2.x thread model (each thread is a kernel thread, no mux'ing over userland threads) that I'm currently coping(!) with. Roll on AIX 4.3. Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 18:26:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA03650 for freebsd-current-outgoing; Mon, 21 Dec 1998 18:23: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 SAA03501 for ; Mon, 21 Dec 1998 18:21:36 -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 MAA01320; Tue, 22 Dec 1998 12:51:03 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id MAA08543; Tue, 22 Dec 1998 12:51:05 +1030 (CST) Message-ID: <19981222125104.V85005@freebie.lemis.com> Date: Tue, 22 Dec 1998 12:51:04 +1030 From: Greg Lehey To: Mike Smith , current@FreeBSD.ORG Subject: Re: trap 12 with interrupts disabled References: <19981222124410.R85005@freebie.lemis.com> <199812220216.SAA02117@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199812220216.SAA02117@dingo.cdrom.com>; from Mike Smith on Mon, Dec 21, 1998 at 06:16:25PM -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 Monday, 21 December 1998 at 18:16:25 -0800, Mike Smith wrote: >> On Monday, 21 December 1998 at 15:52:47 -0800, Mike Smith wrote: >>> >>> Just thought after all the discussion about X servers and interupts, >>> this one might be interesting: >>> >>> pid 281 (Xaccel): trap 12 with interupts disabled >> >> Yes, I've noticed this one too. It seems to have crept in relatively >> recently, and strangely seems not to cause any problems. > > The diagnostic just warns of a bad situation (Xaccel has turned off > interrupts for some reason, and then pagefaulted), it doesn't mention > that it has in fact turned interrupts back on so that the pagefault can > be safely completed. If my page fault fails because I've blocked the interrupt, I'd expect some serious damage to happen to the process environment.n 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 Mon Dec 21 18:28:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA04154 for freebsd-current-outgoing; Mon, 21 Dec 1998 18:28:59 -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 SAA04148 for ; Mon, 21 Dec 1998 18:28:58 -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 SAA02191; Mon, 21 Dec 1998 18:25:33 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812220225.SAA02191@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Greg Lehey cc: Mike Smith , current@FreeBSD.ORG Subject: Re: trap 12 with interrupts disabled In-reply-to: Your message of "Tue, 22 Dec 1998 12:51:04 +1030." <19981222125104.V85005@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Dec 1998 18:25:33 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >>> pid 281 (Xaccel): trap 12 with interupts disabled > >> > >> Yes, I've noticed this one too. It seems to have crept in relatively > >> recently, and strangely seems not to cause any problems. > > > > The diagnostic just warns of a bad situation (Xaccel has turned off > > interrupts for some reason, and then pagefaulted), it doesn't mention > > that it has in fact turned interrupts back on so that the pagefault can > > be safely completed. > > If my page fault fails because I've blocked the interrupt, I'd expect > some serious damage to happen to the process environment.n Usually you're lucky and something else turns them on unconditionally. This test simply makes damn sure that if you take a fault interrupts get turned back on. -- \\ 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 Dec 21 18:29:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA04175 for freebsd-current-outgoing; Mon, 21 Dec 1998 18:29:14 -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 SAA04166 for ; Mon, 21 Dec 1998 18:29:09 -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 MAA01344; Tue, 22 Dec 1998 12:58:56 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id MAA08577; Tue, 22 Dec 1998 12:58:58 +1030 (CST) Message-ID: <19981222125858.X85005@freebie.lemis.com> Date: Tue, 22 Dec 1998 12:58:58 +1030 From: Greg Lehey To: Mike Smith Cc: current@FreeBSD.ORG Subject: Re: trap 12 with interrupts disabled References: <19981222125104.V85005@freebie.lemis.com> <199812220225.SAA02191@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199812220225.SAA02191@dingo.cdrom.com>; from Mike Smith on Mon, Dec 21, 1998 at 06:25:33PM -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 Monday, 21 December 1998 at 18:25:33 -0800, Mike Smith wrote: >>>>> pid 281 (Xaccel): trap 12 with interupts disabled >>>> >>>> Yes, I've noticed this one too. It seems to have crept in relatively >>>> recently, and strangely seems not to cause any problems. >>> >>> The diagnostic just warns of a bad situation (Xaccel has turned off >>> interrupts for some reason, and then pagefaulted), it doesn't mention >>> that it has in fact turned interrupts back on so that the pagefault can >>> be safely completed. >> >> If my page fault fails because I've blocked the interrupt, I'd expect >> some serious damage to happen to the process environment.n > > Usually you're lucky and something else turns them on unconditionally. > This test simply makes damn sure that if you take a fault interrupts > get turned back on. Ah. You mean we don't block the fault, just other interrupts? That makes more sense. 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 Mon Dec 21 18:33:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA04502 for freebsd-current-outgoing; Mon, 21 Dec 1998 18:33:45 -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 SAA04496 for ; Mon, 21 Dec 1998 18:33:44 -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 SAA02237; Mon, 21 Dec 1998 18:30:20 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812220230.SAA02237@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Greg Lehey cc: Mike Smith , current@FreeBSD.ORG Subject: Re: trap 12 with interrupts disabled In-reply-to: Your message of "Tue, 22 Dec 1998 12:58:58 +1030." <19981222125858.X85005@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Dec 1998 18:30:20 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Monday, 21 December 1998 at 18:25:33 -0800, Mike Smith wrote: > >>>>> pid 281 (Xaccel): trap 12 with interupts disabled > >>>> > >>>> Yes, I've noticed this one too. It seems to have crept in relatively > >>>> recently, and strangely seems not to cause any problems. > >>> > >>> The diagnostic just warns of a bad situation (Xaccel has turned off > >>> interrupts for some reason, and then pagefaulted), it doesn't mention > >>> that it has in fact turned interrupts back on so that the pagefault can > >>> be safely completed. > >> > >> If my page fault fails because I've blocked the interrupt, I'd expect > >> some serious damage to happen to the process environment.n > > > > Usually you're lucky and something else turns them on unconditionally. > > This test simply makes damn sure that if you take a fault interrupts > > get turned back on. > > Ah. You mean we don't block the fault, just other interrupts? That > makes more sense. Yes; traps aren't interrupts. -- \\ 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 Dec 21 20:44:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA23438 for freebsd-current-outgoing; Mon, 21 Dec 1998 20:44:00 -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 UAA23424 for ; Mon, 21 Dec 1998 20:43:54 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id UAA52430; Mon, 21 Dec 1998 20:43:41 -0800 (PST) (envelope-from dillon) Date: Mon, 21 Dec 1998 20:43:41 -0800 (PST) From: Matthew Dillon Message-Id: <199812220443.UAA52430@apollo.backplane.com> To: sthaug@nethelp.no Cc: jkh@zippy.cdrom.com, bde@zeta.org.au, current@FreeBSD.ORG Subject: Re: I almost hate to suggest this... References: <81421.914056557@zippy.cdrom.com> <22994.914083025@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> > mount_foo should almost never be used directly. It should be in /libexec :> :> Then why have mount_foo at all? : :Please don't remove mount_foo. I've been able to save several installations :by using mount_nfs directly from a nearby FreeBSD box (and have been unable :to use the fixit floppy because of floppy drive problems). : :Steinar Haug, Nethelp consulting, sthaug@nethelp.no Just a quick side note: Many people forget that FreeBSD can boot into single user via a CDRom drive. *NOT* the BIOS here, the kernel. That is, if you have broken your system but you can still get a boot: prompt and load a kernel (from floppy or the HD), if you boot with the -C option from the boot: prompt and have the 'live filesystem' CDRom (CDRom #2 in the distribution set, I believe) in the CDRom drive, the system will come up single user with the CDRom mounted as root without mounting the hard drive (beyond possibly loading the kernel from it, that is). This makes it phenominally easy to fix a hard drive. Most of the time, the /kernel image on the HD still works and you don't even need a floppy based kernel! CDRom drives are extremely inexpensive these days: usually around $50 and I've started hearing friends say they've seen them down to $25. It is well worth having one installed even if you have an old BIOS that cannot boot directly from it. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 20:47:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA23921 for freebsd-current-outgoing; Mon, 21 Dec 1998 20:47:06 -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 UAA23909 for ; Mon, 21 Dec 1998 20:47:03 -0800 (PST) (envelope-from erikf@visi.com) Received: from odin (h-177-185.mn.mediaone.net [209.32.177.185]) by chmls11.mediaone.net (8.8.7/8.8.7) with SMTP id XAA26471 for ; Mon, 21 Dec 1998 23:46:57 -0500 (EST) Message-ID: <002101be2d66$660b8e20$0200a8c0@mn.mediaone.net> From: "Erik Funkenbusch" To: Subject: Broken ipfw - no Date: Mon, 21 Dec 1998 22:49:01 -0600 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 Thanks everyone for the info. rebuilding world solved my problem (of course it took all day on my crappy P100). I probably could have rebuilt ipfw and natd to test, but I didn't want to take the chance of having something screwed up. Thanks for the help everyone. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 20:47:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA23959 for freebsd-current-outgoing; Mon, 21 Dec 1998 20:47:21 -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 UAA23949 for ; Mon, 21 Dec 1998 20:47:17 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id UAA52455; Mon, 21 Dec 1998 20:47:14 -0800 (PST) (envelope-from dillon) Date: Mon, 21 Dec 1998 20:47:14 -0800 (PST) From: Matthew Dillon Message-Id: <199812220447.UAA52455@apollo.backplane.com> To: "Jay Nordwick" Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: I almost hate to suggest this... References: <199812191631.IAA10154@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :This was embarrasingly easy. I just got the binaries done in about 2 :minutes, but didn't do anything to the man pages. I can send a patch, :but sense I don't know where to even begin on hacking the man pages, :I didn't think that it was useful. It looks like it might have been :a seperate executable originally. : :-jay : :(P.S., for somebody who can fix the man page, here is how to do the rest: :in mount.c get rid of the 2 line test to see if type is ufs, :in mount_ufs.c change mount_ufs(int,char*[]) to main(int,char*[]), :of course fix the makefiles) Lets hold onto this thought until after the 3.0.1 release, then implement it. I see no reason why mount_ufs needs to be integrated into mount any more. I don't think the fixit floppy is squeezed for space (though I haven't checked recently). -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 21 22:41:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA07473 for freebsd-current-outgoing; Mon, 21 Dec 1998 22:41:42 -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 WAA07468 for ; Mon, 21 Dec 1998 22:41:40 -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 WAA46833 for freebsd-current@freebsd.org; Mon, 21 Dec 1998 22:49:20 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199812220649.WAA46833@troutmask.apl.washington.edu> Subject: Fortran conundrum To: freebsd-current@FreeBSD.ORG Date: Mon, 21 Dec 1998 22:49:19 -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 As I promised Mike Smith, I have been looking over the Fortran situation in -current. From the last round of email, we had essentially 3 opinions: (1) Status quo f77 (f2c+gcc) works for the majority of those who use Fortran. If someone wants more speed, power, or features, then they can choose to install gcc_2.8.x and g77+0.5.23, egcs-1.1.1, or purchase a commericial product. Unfortunately, there are a few problems with this plan. First, our version of f2c has suffered some bitrot. I've been merging the latest source available from netlib into my local src tree. Second, there are some underlying assumptions involving size of various types which may break under the DEC alpha port (this is documented in http://www.netlib.org/f2c/readme). Third, an upgrade of the core compiler technology may force a removal of the current Fortran language spec in gcc. (2) Upgrade to g77 -- g77 produces "better" code than f2c+gcc, and it is designed to integrate smoothly with the core compiler technology when an upgrad finally occurs. Unfortunately, g77+0.5.23 is designed to work with gcc+2.8.x, and the author(s) of g77 warn to not even try to back port g77 to any earlier version of gcc. (3) Rip Fortran out of the base distribution. This seem to be the logical choice (provided f2c can be converted to a port). I have been merging our f2c and the sources from netlib with the intend to produce a port. There is, however, one major caveat that needs to be address. /usr/bin/f77 is a driver program which sets up an execution of our Fortran-aware gcc frontend (see src/gnu/usr.bin/cc/f77). I have been unsuccessful in moving this driver out of src/gnu, and still retain its functionality. Thus, I recommend removal of f2c and libf2c, but we retain our current f77 and Fortran-aware gcc. I'll work on providing a a patch to gnu/usr.bin/cc/f77 (and its man page) to deal with the moving of f2c to the ports collection. Comments? -- 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 Mon Dec 21 23:53:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14607 for freebsd-current-outgoing; Mon, 21 Dec 1998 23:53:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from paert.tse-online.de (paert.tse-online.de [194.97.69.172]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA14602 for ; Mon, 21 Dec 1998 23:53:45 -0800 (PST) (envelope-from ab@paert.tse-online.de) Received: (qmail 25988 invoked by uid 1000); 22 Dec 1998 08:00:55 -0000 Message-ID: <19981222090055.A24544@paert.tse-online.de> Date: Tue, 22 Dec 1998 09:00:55 +0100 From: Andreas Braukmann To: current@FreeBSD.ORG Subject: Re: trap 12 with interrupts disabled Mail-Followup-To: current@FreeBSD.ORG References: <199812212352.PAA01176@dingo.cdrom.com> <19981222124410.R85005@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <19981222124410.R85005@freebie.lemis.com>; from Greg Lehey on Tue, Dec 22, 1998 at 12:44:10PM +1030 Organization: TSE TeleService GmbH Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Tue, Dec 22, 1998 at 12:44:10PM +1030, Greg Lehey wrote: > On Monday, 21 December 1998 at 15:52:47 -0800, Mike Smith wrote: > > > > Just thought after all the discussion about X servers and interupts, > > this one might be interesting: > > > > pid 281 (Xaccel): trap 12 with interupts disabled > > Yes, I've noticed this one too. It seems to have crept in relatively > recently, and strangely seems not to cause any problems. Since it crept in my Xaccel (plain 4.1) freezes my machine or at least the console from time to time. This is a mostly standalone machine (my home-office: one router and the machine). On two occurences I went straight to the main office just to test if the machine was still responding on the network -- it wasn't. Most of the times it goes together with a freeking out Netscape 4.5 or 4.07 (BSD libraries). system: dual p6, millenium II, xaccel 4.1, smp-kernel, complete aout XFree86 3.3.3 (built from ports) -Andreas -- /// TSE TeleService GmbH | Gsf: Arne Reuter | /// Hovestrasse 14 | Andreas Braukmann | We do it with /// D-48351 Everswinkel | HRB: 1430, AG WAF | FreeBSD/SMP /// ------------------------------------------------------------------- /// PGP-Key: http://www.tse-online.de/~ab/public-key /// Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 22 00:27:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA17615 for freebsd-current-outgoing; Tue, 22 Dec 1998 00:27:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.eecis.udel.edu (louie.udel.edu [128.175.2.33]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA17609 for ; Tue, 22 Dec 1998 00:27:51 -0800 (PST) (envelope-from alexandr@mail.eecis.udel.edu) Date: Tue, 22 Dec 1998 00:27:51 -0800 (PST) From: alexandr@mail.eecis.udel.edu Message-Id: <199812220827.AAA17609@hub.freebsd.org> Received: from ren.eecis.udel.edu by mail.eecis.udel.edu id aa28739; 22 Dec 1998 03:27 EST To: Steve Kargl Cc: freebsd-current@FreeBSD.ORG Subject: RE: Fortran conundrum Organization: Mos Eisley Candy Store Reply-To: alexandr@mail.eecis.udel.edu Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In Reply to Your Message of Mon, 21 Dec 1998 22: 49:19 PST Date: Tue, 22 Dec 1998 03:27:36 -0500 From: Jerry Alexandratos Message-ID: <199812220327.aa28739@mail.eecis.udel.edu> Steve Kargl says: : As I promised Mike Smith, I have been looking over the Fortran : situation in -current. From the last round of email, we had : essentially 3 opinions: : : (1) Status quo : (2) Upgrade to g77 -- g77 produces "better" code than f2c+gcc, and it : (3) Rip Fortran out of the base distribution. : : Comments? Hey, maybe this would be a good time to revisit the idea of moving to egcs as our compiler toolchain. 8) --Jerry 8) Jerry Alexandratos % - % "Nothing inhabits my (8 8) alexandr@louie.udel.edu % - % thoughts, and oblivion (8 8) darkstar@strauss.udel.edu % - % drives my desires." (8 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 22 03:46:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA03152 for freebsd-current-outgoing; Tue, 22 Dec 1998 03:46:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from asteroid.svib.ru (asteroid.svib.ru [195.151.166.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA03133; Tue, 22 Dec 1998 03:46:17 -0800 (PST) (envelope-from tarkhil@asteroid.svib.ru) Received: from minas-tirith.pol.ru (shuttle.svib.ru [195.151.166.144]) by asteroid.svib.ru (8.9.1a/8.9.1) with ESMTP id OAA09328; Tue, 22 Dec 1998 14:45:22 +0300 (MSK) Received: from minas-tirith.pol.ru (minas-tirith.pol.ru [127.0.0.1]) by minas-tirith.pol.ru (8.9.1/8.8.7) with ESMTP id MAA19305; Tue, 22 Dec 1998 12:56:51 +0300 (MSK) (envelope-from tarkhil@minas-tirith.pol.ru) Message-Id: <199812220956.MAA19305@minas-tirith.pol.ru> X-Mailer: exmh version 2.0.2 2/24/98 To: multimedia@FreeBSD.ORG cc: current@FreeBSD.ORG Reply-To: tarkhil@asteroid.svib.ru Subject: AverMedia TV Capture, remote control, iic, smb... X-URL: http://freebsd.svib.ru Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Date: Tue, 22 Dec 1998 12:56:46 +0300 From: Alex Povolotsky Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I've recently purchased AVerMedia TVCapture card with remote control, and I'm thinking on how to make remote control working. Looks like smbus and I2C have _some_ relation to it, but where can I get more info? Alex. -- Alexander B. Povolotsky [2:5020/145] [http://freebsd.svib.ru] [tarkhil@asteroid.svib.ru] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 22 04:45:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA11512 for freebsd-current-outgoing; Tue, 22 Dec 1998 04:45:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bsd1.gccs.com.au (router.gccs.com.au [203.17.152.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA11503 for ; Tue, 22 Dec 1998 04:45:46 -0800 (PST) (envelope-from starr3@gccs.com.au) Received: from lb50x (lb50x.gccs.com.au [203.17.152.10]) by bsd1.gccs.com.au (8.9.1/8.9.1) with SMTP id WAA01231 for ; Tue, 22 Dec 1998 22:45:38 +1000 (EST) Message-ID: <001501be2da8$fb35b830$0a9811cb@gccs.com.au> From: "Harry Starr" To: "current" Subject: Problems with CAM and ncr Date: Tue, 22 Dec 1998 22:45:38 +1000 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 There seems to be a major problem with the new CAM code and the ncr driver. Config: Asus SC200 (ncr810) in Asus P2L97 M/B with PII-300 and 128MB mem. With "hard" disk access (Make world; or Make release), more than likely, the ncr driver will give an error message of ncr:::queue empty, at which point the system will lock up (pager errors, etc). This is almost 100% reproducible. The SCSI drives are "old" Conner Cp3470. I'm not sure if there were problems with tagged queueing in this model; but they worked OK in a DG/UX system. The ncr driver previously reports that "tagged openings is now 31". Reverting to a kernel dated "8-Aug-1998" alleviates the problem. Any thoughts ?? Harry. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 22 05:29:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA16294 for freebsd-current-outgoing; Tue, 22 Dec 1998 05:29:15 -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 FAA16289 for ; Tue, 22 Dec 1998 05:29:13 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:myaDEKs+0sBP1SJ0jACVX3LroDWuZWKh@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 WAA10042 for ; Tue, 22 Dec 1998 22:29:08 +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 WAA09326; Tue, 22 Dec 1998 22:31:08 +0900 (JST) Message-Id: <199812221331.WAA09326@zodiac.mech.utsunomiya-u.ac.jp> To: current@FreeBSD.ORG cc: yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: future of syscons Date: Tue, 22 Dec 1998 22:31:07 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wrote some notes on the future development plan of our console driver syscons. I would appriciate if you could give me some comments. Kazu ---------------------------------------------------------------------- syscons the Next Generation 22 December 1998 Kazutaka YOKOTA yokota@FreeBSD.ORG I. Overview It has been pointed out in FreeBSD mailing lists over and over again that reorganization of our console driver is desired. The current version of syscons is very closely tied to the AT keyboard interface and the VGA video card. As the support for USB devices and the alpha architecture has been added to 3.0-CURRENT, it is now urgently needed to make syscons more portable, and add support for USB keyboards and video cards other than MDA/CGA/EGA/VGA. We need to decouple the main part of syscons and keyboard/video I/O code to this end. In the process, we shall also try to modularize syscons, so that it would become easier to maintain syscons than now. When we finish this, we should be able to use: 1. non-VGA type video cards for the console, 2. and non-AT type keyboards, such as the USB keyboard. There would also be possibilities of using multiple video cards and keyboards simultaneously. In the next couple of months we shall see dramatic changes in syscons in the following areas. a. Decouple keyboard and video I/O We shall have keyboard and video card drivers segregated from syscons. syscons will access the devices through abstracted interface. If the system has more than one keyboards or more than one video cards, the user should be allowed to specify which keyboard and video card will be used by syscons. We already have sys/i386/isa/kbdio and sys/i386/isa/videoio modules, but they are not sufficient and need to be extended. b. Modularized source files Split syscons.c into a several files of manageable size. c. Selectable features syscons accumulated a number of features over the years. However, it has become rather bloat as a result. The user should be allowed to choose which features to be loaded, by specifying kernel configuration options or by loading/unloading KLD modules. We should be able to bring the size of syscons down by substantial amount if only a set of basic features is selected. d. Terminal emulation Decouple the terminal emulation code from the main body of syscons, and make it possible to load alternative terminal emulator code or multiple emulator codes so that the user is allowed to choose favorite emulator other than the SCO console. The end result of the above improvement may not be as good as "the unified console driver" discussed a few years ago. But, I believe these changes are heading towards the right direction. The changes will first take place in i386, and will be incorporated into alpha and PC98. Most, if not all, code will be shared among these architectures. II. Details and time schedule 1. Keyboard driver Create the AT keyboard controller driver (kbdc) and the AT keyboard driver (atkbd). sys/i386/isa/kbdc.c sys/i386/isa/atkbd.c Update the USB keyboard driver (ukbd). sys/dev/usb/ukbd.c Keyboard drivers are managed and attached by the virtual keyboard driver (kbd). sys/dev/kbd/kbd.c The kernel configuration file should look: controller kbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty flags xxxx device psm0 at isa? tty flags yyy device sc0 at isa? tty flags zzz ... device ukbd0 ... The current keyboard access routines in kbdio.c are mostly moved to kbdc.c and kbdio.[ch] will be deprecated. Status: AT keyboard driver: in testing, given to several developers virtual keyboard driver: in testing, given to several developers USB keyboard driver: to be developed Commit schedule: early next year? NOTE: pcvt driver will still work after this change. But, it will not be able to use the USB keyboard. 2. Video card driver Create MDA/CGA/EGA/VGA driver (vga). sys/i386/isa/vga_isa.c DEC TGA driver? sys/pci/tga.c Ideally these driver should provide high-level, character drawing(rendering) functions as well as low-level I/O services. However, we shall start with basic set of low-level functions and gradually "grow" video card drivers because such incremental path will be easier to follow than doing everything at once. Video card drivers are managed and attached by the virtual frame buffer driver (fb). sys/dev/fb/fb.c The kernel configuration file should look: device vga0 at isa? ... device tga0 ... The current video I/O routines in videoio.c are mostly moved to vga_isa.c and fb.c. videoio.[ch] will be deprecated. Status: VGA driver: in testing frame buffer driver: in testing TGA driver: to be developed Commit schedule: towards the end of January? NOTE: the pcvt driver will still work after this change. It won't use the video card drivers and will access the video hardware directly as before. 3. Source file reorganization Split syscons.c into the following separate files. 1) main body 2) cut&paste, sysmouse support 3) scroll back buffer handling 4) renderer 5) terminal buffer manipulation routines Rendering function (4) should be moved to video card drivers in the future. Status: in testing Commit schedule: towards February? AFTER this step is completed we should be able to say that syscons is "mostly" architecture independent!! 4. Terminal emulator enhancement Nothing is done. That's all for now. ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 22 06:16:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA21652 for freebsd-current-outgoing; Tue, 22 Dec 1998 06:16:28 -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 GAA21638; Tue, 22 Dec 1998 06:16:26 -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.1/8.9.1) with ESMTP id GAA13956; Tue, 22 Dec 1998 06:16:17 -0800 (PST) To: current@FreeBSD.ORG cc: announce@FreeBSD.ORG Subject: Proposed date for creation of 3.0-stable Date: Tue, 22 Dec 1998 06:16:14 -0800 Message-ID: <13929.914336174@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since everyone is going to be off at Christmas or New Years parties and such for the next 10 days or so, it would be impractical to schedule the branch date any earlier than mid-January and so that is what I'm going to do. Unless circumstances dictate otherwise, 3.0 will depart the -current branch on January 15th, 1999 (sometime in the evening, west coast time). The 3.0.1 release will follow 30 days later, on Feb 15th. 1999. So, all you developers, please consider this your ADVANCE NOTICE of these events and don't come crying to me on January 14th about how you weren't given enough time to get your changes into 3.0. :-) Thanks! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 22 08:43:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA14326 for freebsd-current-outgoing; Tue, 22 Dec 1998 08:43:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from assurance.rstcorp.com (assurance.rstcorp.com [206.29.49.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA14321 for ; Tue, 22 Dec 1998 08:43:52 -0800 (PST) (envelope-from vshah@rstcorp.com) Received: (from uucp@localhost) by assurance.rstcorp.com (8.8.8/8.8.8) id LAA19553 for ; Tue, 22 Dec 1998 11:43:48 -0500 Received: from sandbox.rstcorp.com(206.29.49.63) by assurance.rstcorp.com via smap (V2.0) id xma019549; Tue, 22 Dec 98 11:42:54 -0500 Received: from jabberwock.rstcorp.com (jabberwock [206.29.49.98]) by sandbox.rstcorp.com (8.8.8/8.8.8) with ESMTP id LAA07742 for ; Tue, 22 Dec 1998 11:42:53 -0500 (EST) Received: (from vshah@localhost) by jabberwock.rstcorp.com (8.9.1/8.8.8) id LAA94393; Tue, 22 Dec 1998 11:42:54 -0500 (EST) Date: Tue, 22 Dec 1998 11:42:54 -0500 (EST) Message-Id: <199812221642.LAA94393@jabberwock.rstcorp.com> From: "Viren R. Shah" To: freebsd-current@FreeBSD.ORG Subject: error: configured irq 5 not in bitmap of probed irqs 0 X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: "Viren R. Shah" X-Face: )~y+U*K:yzjz{q<5lzpI_SVef'U.])9g[C9`1N@]u3,MHY7f*l7C)[_NjM4y4K8$uIUh|\u (K&&HS6,M!61&GMTk'mqmB/Qg]]X}"?TzsFl]"2v!bl8']dma.:^IY^a[lbOI>U:b<~FyK3q-p{HmZ mn~g.`~BE!5{2D:}Yi+\_KkWe?XaHj9$ko1k8iKLYv5*_2c8"G=?Up[}hn+7RNM(bzBZ_wWk6!Pf&B ?3Tcm7M7B~W%K/I0aX3]*=jP?aM]H6HBPT`oLk+0n^_;N\2\%|Rhy;p}34Q.jEsM\qtnxcm;ag%Nq Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just upgraded a system running 2.2.6 to -current (from 12/19) and sio1 is not found -- instead it gives the error msg: sio1: configured irq 5 not in bitmap of probed irqs 0 This serial port was found properly by 2.2.6. Any pointers or suggestions as to where to look (besides sio.c which I'm already trying to figure out)? No hardware has been changed on the machine during the upgrade to -current. In the meantime, I'll keep trying to figure it out. Thanks Viren -- Viren Shah | "No amount of source-level verification Research Associate, RST Inc. | or scrutiny will protect you from using viren@rstcorp.com | untrusted code." http://www.rstcorp.com/~vshah | - Ken Thompson "Reflections on Trusting Trust" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 22 08:56:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16227 for freebsd-current-outgoing; Tue, 22 Dec 1998 08:56:09 -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 IAA16221 for ; Tue, 22 Dec 1998 08:56:08 -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 JAA48584; Tue, 22 Dec 1998 09:03:42 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199812221703.JAA48584@troutmask.apl.washington.edu> Subject: Re: Fortran conundrum In-Reply-To: <199812220827.AAA17609@hub.freebsd.org> from "alexandr@mail.eecis.udel.edu" at "Dec 22, 1998 0:27:51 am" To: alexandr@mail.eecis.udel.edu Date: Tue, 22 Dec 1998 09:03:41 -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 According to alexandr@mail.eecis.udel.edu: > In Reply to Your Message of Mon, 21 Dec 1998 22: 49:19 PST > Date: Tue, 22 Dec 1998 03:27:36 -0500 > From: Jerry Alexandratos > Message-ID: <199812220327.aa28739@mail.eecis.udel.edu> > > Steve Kargl says: > : As I promised Mike Smith, I have been looking over the Fortran > : situation in -current. From the last round of email, we had > : essentially 3 opinions: > : > : (1) Status quo > : (2) Upgrade to g77 -- g77 produces "better" code than f2c+gcc, and it > : (3) Rip Fortran out of the base distribution. > : > : Comments? > > Hey, maybe this would be a good time to revisit the idea of moving to > egcs as our compiler toolchain. 8) > See last weeks email archive about this discussion. -- 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 Tue Dec 22 09:00:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA17004 for freebsd-current-outgoing; Tue, 22 Dec 1998 09:00:44 -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 JAA16998 for ; Tue, 22 Dec 1998 09:00:41 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from o2.cs.rpi.edu (root@o2.cs.rpi.edu [128.113.96.156]) by cs.rpi.edu (8.9.1/8.9.1) with ESMTP id MAA19272; Tue, 22 Dec 1998 12:00:33 -0500 (EST) From: "David E. Cross" Received: (from crossd@localhost) by o2.cs.rpi.edu (8.9.1a/8.9.1) id MAA03214; Tue, 22 Dec 1998 12:00:34 -0500 (EST) Date: Tue, 22 Dec 1998 12:00:34 -0500 (EST) Message-Id: <199812221700.MAA03214@o2.cs.rpi.edu> To: viren@rstcorp.com, freebsd-current@FreeBSD.ORG Subject: re: error: configured irq 5 not in bitmap of probed irqs 0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have had this problem too, and after digging through the sio.c source I discovered the following. After the base address of the UART is found the code issues a couple of to force the UART to generate an interupt request; all the interupts that are received during these probes are placed into a mask (16 hardware interupts total, fits nicely as a bitmask). The code then does a logical and with the configured IRQ (that was supplied either via config(8) or '-c'), if the result is true then it assigns the IRQ as specified, if false then it gives you that error. The remedy is to find what IRQ it is really using. When I had this problem I swore I knew what IRQ the UART was using, and that FreeBSD was wrong, after reviewing the code, and changing the IRQ (from 4 to 3 in this case), it worked fine. I did not dig through the code enough to notice if it traps ALL irqs during this test, or just the un-assigned ones. If it only traps unassigned ones check dmesg output for things prior to sio that are bound to IRQ 5. -- 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 Dec 22 09:33:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21532 for freebsd-current-outgoing; Tue, 22 Dec 1998 09:33:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from esmeralda.xaa.iae.nl (esmeralda.xaa.iae.nl [194.151.75.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21527 for ; Tue, 22 Dec 1998 09:33:07 -0800 (PST) (envelope-from freebsd@xaa.iae.nl) Received: by esmeralda.xaa.iae.nl (Postfix, from userid 1008) id 08D82183; Tue, 22 Dec 1998 18:33:01 +0100 (MET) Date: Tue, 22 Dec 1998 18:33:01 +0100 From: Mark Huizer To: Erik Funkenbusch , freebsd-current@FreeBSD.ORG Subject: Re: Broken ipfw? Message-ID: <19981222183301.A72204@esmeralda.xaa.iae.nl> References: <003901be2d0a$6da7f800$0200a8c0@mn.mediaone.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.10i In-Reply-To: <003901be2d0a$6da7f800$0200a8c0@mn.mediaone.net>; from Erik Funkenbusch on Mon, Dec 21, 1998 at 11:47:15AM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 21, 1998 at 11:47:15AM -0600, Erik Funkenbusch wrote: > After cvsuping on saturday natd has suddenly stopped working with the kernel > I built on saturday and after cvsuping today and rebuilding as well. > > After executing an ipfw rule it responds with: > > ip_fw_ctl: empty interface name > /sbin/ipfw: setsockopt(IP_FW_ADD): Invalid Argument > > and of course no routing occurs. > > Any ideas? I'm planning on rebuilding world to see if it was some fix to > both kernel and natd, but I can't seem to find anything in the cvs list that > would indicate a change here. > > I'm using the de0 driver on an Asante NIC. I can ping anything on that > network, and I can ping stuff on my private network using the xl0 driver. dummynet got included, rebuild your ipfw (after redoing the include files). Easiest is a make world :-) Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 22 09:56:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24234 for freebsd-current-outgoing; Tue, 22 Dec 1998 09:56:09 -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 JAA24227 for ; Tue, 22 Dec 1998 09:56: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 EAA04557; Wed, 23 Dec 1998 04:55:53 +1100 Date: Wed, 23 Dec 1998 04:55:53 +1100 From: Bruce Evans Message-Id: <199812221755.EAA04557@godzilla.zeta.org.au> To: crossd@cs.rpi.edu, freebsd-current@FreeBSD.ORG, viren@rstcorp.com Subject: re: error: configured irq 5 not in bitmap of probed irqs 0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >total, fits nicely as a bitmask). The code then does a logical and with the >configured IRQ (that was supplied either via config(8) or '-c'), if the result >is true then it assigns the IRQ as specified, if false then it gives you that >error. Actually, if false it gives you that warning and then assigns the IRQ as specified (unless there was a more serious error). The specified IRQ is unlikely to work if this warning is printed, but always setting it gives you control. In 2.2.7, this error was fatal and that was important for preventing IRQ conflicts for misconfigured kernels (ones that don't specify _all_ the serial ports with their correct IRQs). Now the probe believes the configuration but prints the warning to help debug misconfigurations. Booting in verbose mode gives more details. >I did not dig through the code enough to notice if it traps ALL irqs during >this test, or just the un-assigned ones. If it only traps unassigned ones check >dmesg output for things prior to sio that are bound to IRQ 5. It checks all IRQs without trapping, but the check (and normal operation) may be broken by almost any device physically bound to the same irq, independently of the probe order (exception: sio devices on the same irq but not yet probed are specially handled so that they don't interfere with previous probes). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 22 10:25:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27861 for freebsd-current-outgoing; Tue, 22 Dec 1998 10:25:14 -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 KAA27842 for ; Tue, 22 Dec 1998 10:25:12 -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 TAA45427; Tue, 22 Dec 1998 19:25:00 +0100 (CET) (envelope-from des) To: Kazutaka YOKOTA Cc: current@FreeBSD.ORG Subject: Re: future of syscons References: <199812221331.WAA09326@zodiac.mech.utsunomiya-u.ac.jp> From: Dag-Erling Smorgrav Date: 22 Dec 1998 19:24:59 +0100 In-Reply-To: Kazutaka YOKOTA's message of "Tue, 22 Dec 1998 22:31:07 +0900" Message-ID: Lines: 15 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kazutaka YOKOTA writes: > The kernel configuration file should look: > > controller kbdc0 at isa? port IO_KBD tty > device atkbd0 at isa? tty flags xxxx > device psm0 at isa? tty flags yyy Shouldn't it be: device atkbd0 at kbdc0 flags xxxx device psm0 at kbdc0 flags yyyy 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 Tue Dec 22 10:55:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02093 for freebsd-current-outgoing; Tue, 22 Dec 1998 10:55:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from knecht.Sendmail.ORG (knecht.sendmail.org [209.31.233.160]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02075 for ; Tue, 22 Dec 1998 10:55:05 -0800 (PST) (envelope-from mckusick@flamingo.McKusick.COM) Received: from flamingo.McKusick.COM (root@flamingo.mckusick.com [209.31.233.178]) by knecht.Sendmail.ORG (8.9.2.Beta4/8.9.2.Beta4) with ESMTP id KAA11091; Tue, 22 Dec 1998 10:54:55 -0800 (PST) Received: from flamingo.McKusick.COM (mckusick@localhost [127.0.0.1]) by flamingo.McKusick.COM (8.8.5/8.8.5) with ESMTP id JAA15538; Tue, 22 Dec 1998 09:31:39 -0800 (PST) Message-Id: <199812221731.JAA15538@flamingo.McKusick.COM> To: "Jordan K. Hubbard" Subject: Re: I almost hate to suggest this... cc: Matthew Dillon , current@FreeBSD.ORG In-reply-to: Your message of "Sat, 19 Dec 1998 02:00:39 PST." <81864.914061639.1@zippy.cdrom.com> Date: Tue, 22 Dec 1998 09:31:39 -0800 From: Kirk McKusick Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Date: Sat, 19 Dec 1998 02:00:39 -0800 From: "Jordan K. Hubbard" Subject: Re: I almost hate to suggest this... To: Matthew Dillon cc: current@FreeBSD.ORG Subject: Re: I almost hate to suggest this... In-reply-to: Your message of "Sat, 19 Dec 1998 01:55:09 PST." <199812190955.BAA07155@apollo.backplane.com> Date: Sat, 19 Dec 1998 02:00:39 -0800 Message-ID: <81864.914061639@zippy.cdrom.com> From: "Jordan K. Hubbard" MIME-Version: 1.0 > When someone has time available, making a separate mount_ufs > and rewriting mount itself to always exec a sub-mount binary > would be even better. But as a poor-man's fix the above Hmmm. I always got the feeling that the original CSRG folk deliberately stuck "ufs mounting" into mount(8) so that one binary could be copied around easily for fixit purposes, ufs being the one fs that could be deemed somewhat in the "bootstrap" class and perhaps worthy of special treatment. Then again, maybe not, I'm just saying that this most obvious lack of orthogonality (not writing mount(8) as a minimal wrapper) may well have been deliberate. I've bcc'd somebody who might know the real story in any case. :) - Jordan The intent was to one day break ufs out of mount. If you look at the sources for mount, you will find mount.c and mount_ufs.c. I think that the day has certainly come to consider making the divide, but it should be done properly, not by creating a link. Properly means moving mount_ufs.c to its own directory and building and installing it in its own right. The mount program should have the code deleted that calls mount_ufs internally. The only reason it was not done earlier was that it was deemed easier to copy just one program around (mount) than two (mount and mount_ufs) when making changes to the way ufs was mounted. I think that those considerations have faded. Kirk McKusick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 22 11:16:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05719 for freebsd-current-outgoing; Tue, 22 Dec 1998 11:16:17 -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 LAA05714 for ; Tue, 22 Dec 1998 11:16:12 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.1/8.9.1) id NAA13910 for current@freebsd.org; Tue, 22 Dec 1998 13:16:03 -0600 (CST) (envelope-from dick) Message-ID: <19981222131603.B13835@tar.com> Date: Tue, 22 Dec 1998 13:16:03 -0600 From: Richard Seaman To: current@FreeBSD.ORG Subject: Update on Linux Threads patches 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 The information at http://lt.tar.com has been updated somewhat. The most important changes are these: 1) The linuxthreads "port" did not work correctly with the patches incorporated into FreeBSD-current under the option COMPAT_LINUX_THREADS. I had accidentally deleted the code that permitted the ports to work without the "growable stack" patches. The port has been fixed. This had no effect on linux threads running in emulation mode. 2) It appears that the linux libraries included in the ports/emulators/linux_lib are buggy. I'm not sure if the problem is in glibc or libpthreads. These are apparently not the latest versions. The problem is that linux threads internal structures don't get freed when threads exit. Since there is a limit of 1024 threads, once you have created that many threads you can't create any more, even if some (or all) of the thread you created have been destroyed. The problem is fixed by installing updated linux libraries, such as those that accompany StarOffice 5.0. -- 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 Dec 22 11:19:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06060 for freebsd-current-outgoing; Tue, 22 Dec 1998 11:19:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from assurance.rstcorp.com (assurance.rstcorp.com [206.29.49.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA06036 for ; Tue, 22 Dec 1998 11:19:20 -0800 (PST) (envelope-from vshah@rstcorp.com) Received: (from uucp@localhost) by assurance.rstcorp.com (8.8.8/8.8.8) id OAA20970; Tue, 22 Dec 1998 14:17:49 -0500 Received: from sandbox.rstcorp.com(206.29.49.63) by assurance.rstcorp.com via smap (V2.0) id xma020964; Tue, 22 Dec 98 14:17:17 -0500 Received: from jabberwock.rstcorp.com (jabberwock [206.29.49.98]) by sandbox.rstcorp.com (8.8.8/8.8.8) with ESMTP id OAA10562; Tue, 22 Dec 1998 14:17:16 -0500 (EST) Received: (from vshah@localhost) by jabberwock.rstcorp.com (8.9.1/8.8.8) id OAA99020; Tue, 22 Dec 1998 14:17:17 -0500 (EST) Date: Tue, 22 Dec 1998 14:17:17 -0500 (EST) Message-Id: <199812221917.OAA99020@jabberwock.rstcorp.com> From: "Viren R. Shah" To: Bruce Evans Cc: crossd@cs.rpi.edu, freebsd-current@FreeBSD.ORG Subject: re: error: configured irq 5 not in bitmap of probed irqs 0 In-Reply-To: <199812221755.EAA04557@godzilla.zeta.org.au> References: <199812221755.EAA04557@godzilla.zeta.org.au> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: "Viren R. Shah" X-Face: )~y+U*K:yzjz{q<5lzpI_SVef'U.])9g[C9`1N@]u3,MHY7f*l7C)[_NjM4y4K8$uIUh|\u (K&&HS6,M!61&GMTk'mqmB/Qg]]X}"?TzsFl]"2v!bl8']dma.:^IY^a[lbOI>U:b<~FyK3q-p{HmZ mn~g.`~BE!5{2D:}Yi+\_KkWe?XaHj9$ko1k8iKLYv5*_2c8"G=?Up[}hn+7RNM(bzBZ_wWk6!Pf&B ?3Tcm7M7B~W%K/I0aX3]*=jP?aM]H6HBPT`oLk+0n^_;N\2\%|Rhy;p}34Q.jEsM\qtnxcm;ag%Nq Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "BDE" == Bruce Evans writes: >>>>> "DEC" == "David E. Cross" writes: DEC> The remedy is to find what IRQ it is really using. When I had DEC> this problem I swore I knew what IRQ the UART was using, and DEC> that FreeBSD was wrong, after reviewing the code, and changing DEC> the IRQ (from 4 to 3 in this case), it worked fine. BDE> It checks all IRQs without trapping, but the check (and normal operation) BDE> may be broken by almost any device physically bound to the same irq, BDE> independently of the probe order (exception: sio devices on the same BDE> irq but not yet probed are specially handled so that they don't interfere BDE> with previous probes). I'll check (as soon as I get home) whether there is anything else using irq 5. If not, I'll try changing things around (which will be fun, since this is an old EISA machine). Thanks guys Viren -- Viren Shah | "No amount of source-level verification Research Associate, RST Inc. | or scrutiny will protect you from using viren@rstcorp.com | untrusted code." http://www.rstcorp.com/~vshah | - Ken Thompson "Reflections on Trusting Trust" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 22 12:07:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA04197 for freebsd-current-outgoing; Tue, 22 Dec 1998 12:07: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 MAA04102 for ; Tue, 22 Dec 1998 12:07:49 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id MAA05514; Tue, 22 Dec 1998 12:07:40 -0800 (PST) (envelope-from dillon) Date: Tue, 22 Dec 1998 12:07:40 -0800 (PST) From: Matthew Dillon Message-Id: <199812222007.MAA05514@apollo.backplane.com> To: Kirk McKusick Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: I almost hate to suggest this... References: <199812221731.JAA15538@flamingo.McKusick.COM> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've created a gnats PR, assigned to myself, to split mount_ufs out of mount after the 3.0.1 release. I don't think we have to spend too much more time on it now. ( submitting a bug report and then assigning it to yourself is a great way to earmark things for TODO'ing later, at least if you are a committer, because you get nice weekly summaries of the bugs assigned to you :-) ). -Matt : Hmmm. I always got the feeling that the original CSRG folk : deliberately stuck "ufs mounting" into mount(8) so that one binary : could be copied around easily for fixit purposes, ufs being the one fs : that could be deemed somewhat in the "bootstrap" class and perhaps : worthy of special treatment. : : Then again, maybe not, I'm just saying that this most obvious lack of : orthogonality (not writing mount(8) as a minimal wrapper) may well : have been deliberate. I've bcc'd somebody who might know the real : story in any case. :) : : - Jordan : :The intent was to one day break ufs out of mount. If you look :at the sources for mount, you will find mount.c and mount_ufs.c. :I think that the day has certainly come to consider making the :divide, but it should be done properly, not by creating a link. :Properly means moving mount_ufs.c to its own directory and :building and installing it in its own right. The mount program :should have the code deleted that calls mount_ufs internally. :The only reason it was not done earlier was that it was deemed :easier to copy just one program around (mount) than two (mount :and mount_ufs) when making changes to the way ufs was mounted. :I think that those considerations have faded. : : Kirk McKusick : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-current" in the body of the message : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 22 13:01:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA27981 for freebsd-current-outgoing; Tue, 22 Dec 1998 13:01:14 -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 NAA27865 for ; Tue, 22 Dec 1998 13:00:46 -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 QAA27869; Tue, 22 Dec 1998 16:00:32 -0500 (EST) Date: Tue, 22 Dec 1998 16:00:32 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Henry Miller cc: brian@worldcontrol.com, freebsd-current@FreeBSD.ORG Subject: Re: USB, scanners, and SANE? 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, 20 Dec 1998, Henry Miller wrote: > > This was discussed on the sane mailing lists last month, and the > concessious was USB support is desirable, but today there are several > problems. a) nobody with an interest in writting a scanner backend has a > USB scanner, b) the lack of stable implimentations of USB and unix. > > a) is the biggest thing getting in the way, but that is expected to > change over the next year or so. I encourage you to get involved and > write the backend. > > b) will be a big deal. The goal is to have standard functions for > accessing the USB port, similear to what sane does for scsi. Before work > in that direction can procede the operating systems SANE runs on need USB > support. NetBSD is the only one that has USB support. FreeBSD and Linux > were both noted as making progress, but not yet to the point where anyone > can truely belive that they won't change their API 10 times a month for > the next few months. Obviously things will settle down (and probably > won't get that bad) but today the implimentation isn't truely ready for > others to write protable programs on top of. This is true, I'd like to see the user-level USB integration completed (i.e. usb supporting its devices _and_ MAKEDEV being able to create all the different USB nodes. I'm working on getting some USB hardware to test out with my new VIA chipset. > > on the other hand, b) should be solved in the next few months. (and if > you read -current you probably know the state of USB in freeBSD, which is > progressing nicely) Once the OS level implimentations are stable, SANE > will write a wrapper API, and then things will be ready for a backends. In addition, NetBSD is not the only one with USB support. NetBSD USB _IS_ FreeBSD USB, in actuality. Look at the code. So we use NetBSD's API. > > You can short circuite this process, like the parrell drivers do, but > remember that parrell scanners are generally unsupported, and considering > manufactures additude always will be. USB scanners probably will be > supported, therefore if you write something plan time to re-write it to a > standard when sane releases one. > > Good luck! > > On Sun, 20 Dec 1998 brian@worldcontrol.com wrote: > > > I've been poking around the USB website and seperatedly > > noted the addition of support for USB under -current. > > > > Reading the www.usb.org site I mostly got the sense of Plug&Pray. > > Basically, plug it in, don't worry be happy. > > > > My wife as a HP Scanjet 4100CXI on her PC running [censored]. > > > > I'd like to take a stab at getting it to work under FreeBSD. > > I'm not above writing code. > > > > SANE has support for HP scanners of both SCSI and parallel port > > versions. > > > > Via the existing FreeBSD USB support will it be possible for me > > to create a communication channel for the SANE backend to talk > > to the scanner? > > > > HIDs and Classes (was it?) have me worried that I have to wait > > for particular support for scanner class devices. But on the > > other hand, maybe this is not that case, and perhaps I can use > > some generic interface to access the scanner. > > > > Any pointers or clarification on the FreeBSD USB interface > > would be appreciated. > > > > -- > > 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 Tue Dec 22 13:10:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA02810 for freebsd-current-outgoing; Tue, 22 Dec 1998 13:10:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail2.lig.bellsouth.net (mail2.lig.bellsouth.net [205.152.0.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA02729 for ; Tue, 22 Dec 1998 13:09:45 -0800 (PST) (envelope-from glenn@bellsouth.net) Received: from gforce.johnson.home (host-209-214-153-191.sld.bellsouth.net [209.214.153.191]) by mail2.lig.bellsouth.net (8.8.8-spamdog/8.8.5) with ESMTP id QAA27243; Tue, 22 Dec 1998 16:09:16 -0500 (EST) Received: from bellsouth.net (localhost [127.0.0.1]) by gforce.johnson.home (8.9.1/8.9.1) with ESMTP id PAA36858; Tue, 22 Dec 1998 15:08:56 -0600 (CST) (envelope-from glenn@bellsouth.net) Message-Id: <199812222108.PAA36858@gforce.johnson.home> X-Mailer: exmh version 2.0.2 2/24/98 To: Steve Kargl cc: freebsd-current@FreeBSD.ORG From: Glenn Johnson Subject: Re: Fortran conundrum In-Reply-To: Message from Steve Kargl of "Mon, 21 Dec 1998 22:49:19 PST." <199812220649.WAA46833@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 22 Dec 1998 15:08:55 -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sgk@troutmask.apl.washington.edu wrote: > As I promised Mike Smith, I have been looking over the Fortran situation > in -current. From the last round of email, we had essentially 3 > opinions: > > (1) Status quo > > f77 (f2c+gcc) works for the majority of those who use Fortran. If > someone wants more speed, power, or features, then they can choose > to install gcc_2.8.x and g77+0.5.23, egcs-1.1.1, or purchase a > commericial product. > I have some Fortran programs that will not compile with f2c+gcc but compile fine with g77. The converse is also true however, but not as much. sgk@troutmask.apl.washington.edu wrote: > (2) Upgrade to g77 -- g77 produces "better" code than f2c+gcc, and it is > designed to integrate smoothly with the core compiler technology when an > upgrad finally occurs. > I find that g77 meets my needs more than f2c+gcc, so I would like to see g77 brought into the FreeBSD distribution when the upgrade to gcc2.8.x occurs. I have been using egcs-1.1.1 and that meets my needs. sgk@troutmask.apl.washington.edu wrote: > (3) Rip Fortran out of the base distribution. > This doesn't sound good to me. Wouldn't it be better to have g77 integrated in. Fortran is still important enough that it should be in the base distribution, IMHO. -- Glenn Johnson gljohns@bellsouth.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 22 13:15:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05921 for freebsd-current-outgoing; Tue, 22 Dec 1998 13:15:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alushta.NL.net (alushta.NL.net [193.78.240.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05817 for ; Tue, 22 Dec 1998 13:15:28 -0800 (PST) (envelope-from benst@terminus.stuyts.nl) Received: from stuyts by alushta.NL.net with UUCP id <4702-31410>; Tue, 22 Dec 1998 22:15:01 +0100 Received: from daneel.stuyts.nl (daneel.stuyts.nl [193.78.231.7]) by terminus.stuyts.nl (8.9.1/8.9.1) with ESMTP id WAA35931 for ; Tue, 22 Dec 1998 22:11:19 +0100 (MET) (envelope-from benst) Received: (from benst@localhost) by daneel.stuyts.nl (8.8.5/8.8.5) id WAA06117 for current@freebsd.org; Tue, 22 Dec 1998 22:11:14 +0100 (MET) Message-Id: <199812222111.WAA06117@daneel.stuyts.nl> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 3.3 v118.2) X-Nextstep-Mailer: Mail 3.3 (Enhance 1.2) Received: by NeXT.Mailer (1.118.2) From: Ben Stuyts Date: Tue, 22 Dec 98 22:11:13 +0100 To: current@FreeBSD.ORG Subject: Problem with newsyslog: preposterous process number. Reply-To: ben@stuyts.nl Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I just received the following from cron: newsyslog: preposterous process number: 35655 newsyslog: log not compressed because daemon not notified Looking in /usr/src/usr.sbin/newsyslog/newsyslog.c I see: #define MIN_PID 5 #define MAX_PID 30000 /* was 65534, see /usr/include/sys/proc.h */ However, in /usr/include/sys/proc.h I see: #define PID_MAX 99999 It seems these two files are no longer synced. (Perhaps newsyslog.c should just include sys/proc.h?) Regards, Ben To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 22 13:30:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16653 for freebsd-current-outgoing; Tue, 22 Dec 1998 13:30:26 -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 NAA16605 for ; Tue, 22 Dec 1998 13:30:15 -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 NAA11641; Tue, 22 Dec 1998 13:37:47 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199812222137.NAA11641@troutmask.apl.washington.edu> Subject: Re: Fortran conundrum In-Reply-To: <199812222108.PAA36858@gforce.johnson.home> from Glenn Johnson at "Dec 22, 1998 3: 8:55 pm" To: gljohns@bellsouth.net (Glenn Johnson) Date: Tue, 22 Dec 1998 13:37:47 -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 According to Glenn Johnson: > > sgk@troutmask.apl.washington.edu wrote: > > As I promised Mike Smith, I have been looking over the Fortran situation > > in -current. From the last round of email, we had essentially 3 > > opinions: > > > > (1) Status quo > > > > f77 (f2c+gcc) works for the majority of those who use Fortran. If > > someone wants more speed, power, or features, then they can choose > > to install gcc_2.8.x and g77+0.5.23, egcs-1.1.1, or purchase a > > commericial product. > > I have some Fortran programs that will not compile with f2c+gcc but > compile fine with g77. The converse is also true however, but not as much. This actually surprises me unless your Fortran code is using some nonstandard extensions to Fortran 77. What does /usr/ports/devel/ftnchek say about yor codes. > sgk@troutmask.apl.washington.edu wrote: > > (2) Upgrade to g77 -- g77 produces "better" code than f2c+gcc, and it is > > designed to integrate smoothly with the core compiler technology when an > > upgrad finally occurs. > > I find that g77 meets my needs more than f2c+gcc, so I would like to see > g77 brought into the FreeBSD distribution when the upgrade to gcc2.8.x > occurs. I have been using egcs-1.1.1 and that meets my needs. Indeed, I recommend that we (as community) try to keep somewhat current with egcs in the ports because development of g77 is done primarily within egcs now. > sgk@troutmask.apl.washington.edu wrote: > > (3) Rip Fortran out of the base distribution. > > This doesn't sound good to me. Wouldn't it be better to have g77 > integrated in. Fortran is still important enough that it should be in the > base distribution, IMHO. My impression is this won't happen -- 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 Tue Dec 22 14:13:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16847 for freebsd-current-outgoing; Tue, 22 Dec 1998 14: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 OAA16722 for ; Tue, 22 Dec 1998 14:13:28 -0800 (PST) (envelope-from reg@shale.csir.co.za) Received: (from reg@localhost) by shale.csir.co.za (8.9.1/8.9.1) id AAA68236; Wed, 23 Dec 1998 00:13:05 +0200 (SAT) (envelope-from reg) Date: Wed, 23 Dec 1998 00:13:05 +0200 From: Jeremy Lea To: Richard Seaman Cc: freebsd-current@FreeBSD.ORG Subject: Threads in WINE [was: linking against libc_r] Message-ID: <19981223001304.A319@shale.csir.co.za> References: <19981221093241.C546@tar.com> <19981221192734.E4060@shale.csir.co.za> <19981221114939.A5500@tar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <19981221114939.A5500@tar.com>; from Richard Seaman on Mon, Dec 21, 1998 at 11:49:39AM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Mon, Dec 21, 1998 at 11:49:39AM -0600, Richard Seaman wrote: > On Mon, Dec 21, 1998 at 07:27:35PM +0200, Jeremy Lea wrote: > > > > Wine seems to want clone(), from a quick read of the man page. Does the > > native LinuxThreads stuff implement this as a FreeBSD syscall? > > The FreeBSD "port" of Linux threads does not use nor implement a clone > syscall. It uses rfork instead within pthread_create to simulate > the clone call. If Wine calls "clone" directly, rather than via > the phread_create call, it would be easy enough to implement a > FreeBSD call, either in libc or as a syscall, that mimics clone. > > Actually, there are already two "clone" calls within Linux Threads > right now. There is a wrapper "clone" call that wraps the clone > syscall (see clone.S in the linux threads source). Well, I finally got to looking at the source. It uses clone() directly. In fact there is no mention of libpthread at all. But there is the following extract from wine-981211/include/threads.h: --- #ifdef linux #define HAVE_CLONE_SYSCALL #endif /* This is what we will use on *BSD, once threads using rfork() get * implemented: * * #if defined(__NetBSD__) || defined(__FreeBSD__) || defined(__OpenBSD__) * #define HAVE_RFORK * #endif */ #if (defined(HAVE_CLONE_SYSCALL) || defined(HAVE_RFORK)) && !defined(NO_REENTRANT_LIBC) #define USE_THREADS #endif --- and from wine-981211/scheduler/sysdeps.c: --- int SYSDEPS_SpawnThread( THDB *thread ) { #ifdef USE_THREADS #ifdef HAVE_CLONE_SYSCALL if (clone( (int (*)(void *))SYSDEPS_StartThread, thread->teb.stack_top, CLONE_VM | CLONE_FS | CLONE_FILES | SIGCHLD, thread ) < 0) return -1; /* FIXME: close the child socket in the parent process */ /* close( thread->socket );*/ #endif #ifdef HAVE_RFORK FIXME(thread, "Threads using rfork() not implemented\n" ); #endif #else /* !USE_THREADS */ FIXME(thread, "CreateThread: stub\n" ); #endif /* USE_THREADS */ return 0; --- These are the only mentions for HAVE_CLONE_SYSCALL and HAVE_RFORK. Does this make your mind tick any? The only other condition is a reentrant libc it would seem... Regards -Jeremy -- | "I could be anything I wanted to, but one things true --+-- Never gonna be as big as Jesus, never gonna hold the world in my hand | Never gonna be as big as Jesus, never gonna build a promised land | But that's, that's all right, OK with me..." -Audio Adrenaline To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 22 14:38:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09087 for freebsd-current-outgoing; Tue, 22 Dec 1998 14: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 OAA09046 for ; Tue, 22 Dec 1998 14:37:54 -0800 (PST) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 358 invoked by uid 100); 22 Dec 1998 22:45:26 -0000 Date: Tue, 22 Dec 1998 14:45:25 -0800 To: freebsd-current@FreeBSD.ORG Subject: SANE, USB, -current step 2 Message-ID: <19981222144525.A334@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.94.17i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok I plugged my wife's HP 4100cxi and booted with the USB extensions. The last line look promising: Dec 22 22:28:40 top /kernel: ugen0: Hewlett-Packard HP ScanJet 4100C (rev 1.00/1.00) addr 2 (device class 0/0) Now does anyone have a primer on using the ugen device to talk to the device? Perhaps /dev/ugen0 is dynamically created and I can talk serially to the device via read/write? Dec 22 22:28:39 top /kernel: usbd_match Dec 22 22:28:39 top /kernel: usb0: Dec 22 22:28:39 top /kernel: usbd_attach Dec 22 22:28:39 top /kernel: usbd_new_device bus=0xf07ba000 depth=0 lowspeed=0 Dec 22 22:28:39 top /kernel: usbd_setup_pipe: dev=0xf05ac780 iface=0 ep=0xf05ac79c pipe=0xf05ac788 Dec 22 22:28:39 top /kernel: uhci_open: pipe=0xf05ac700, addr=0, endpt=0 (0) Dec 22 22:28:39 top /kernel: usbd_new_device: adding unit addr=1, rev=100, class=9, subclass=1, protocol=0, maxpacket=64, ls=0 Dec 22 22:28:39 top /kernel: usbd_new_device: new dev (addr 1), dev=0xf05ac780, parent=0xf07b8780 Dec 22 22:28:39 top /kernel: usb1 at usb0 Dec 22 22:28:39 top /kernel: usb1: Intel UHCI root hub (class 9/1) (rev 1.00/1.00) addr 1 Dec 22 22:28:39 top /kernel: usbd_set_config_no: (addr 1) attr=0x40, selfpowered=1, power=0, powerquirk=0 Dec 22 22:28:39 top /kernel: usbd_set_config_no: setting new config 1 Dec 22 22:28:39 top /kernel: usb_init_hub: getting hub descriptor Dec 22 22:28:39 top /kernel: usbhub_init_hub: selfpowered=1, parent=0, parent->selfpowered=0 Dec 22 22:28:39 top /kernel: usbd_setup_pipe: dev=0xf05ac780 iface=0xf07b6da0 ep=0xf07b7ea0 pipe=0xf0283a14 Dec 22 22:28:39 top /kernel: uhci_open: pipe=0xf05ac600, addr=1, endpt=129 (1) Dec 22 22:28:39 top /kernel: usbd_init_port: adding hub port=1 status=0x0100 change=0x0000 Dec 22 22:28:39 top /kernel: usbd_init_port: adding hub port=2 status=0x0101 change=0x0001 Dec 22 22:28:39 top /kernel: uhub_explore: st Dec 22 22:28:39 top /kernel: atus change hub=1 port=2 Dec 22 22:28:39 top /kernel: usbd_reset_port: port 2 reset done, error=0 Dec 22 22:28:39 top /kernel: usbd_new_device bus=0xf07ba000 depth=1 lowspeed=0 Dec 22 22:28:39 top /kernel: usbd_setup_pipe: dev=0xf05ac500 iface=0 ep=0xf05ac51c pipe=0xf05ac508 Dec 22 22:28:39 top /kernel: uhci_open: pipe=0xf05ac480, addr=0, endpt=0 (1) Dec 22 22:28:39 top /kernel: usbd_new_device: adding unit addr=2, rev=100, class=0, subclass=0, protocol=0, maxpacket=8, ls=0 Dec 22 22:28:39 top /kernel: usbd_new_device: new dev (addr 2), dev=0xf05ac500, parent=0xf07b7eb0 Dec 22 22:28:39 top /kernel: usbd_new_device: no device driver found Dec 22 22:28:39 top /kernel: usbd_set_config_no: (addr 2) attr=0x60, selfpowered=1, power=0, powerquirk=0 Dec 22 22:28:39 top /kernel: usbd_set_config_no: setting new config 1 Dec 22 22:28:39 top /kernel: usbd_set_config_no: free old config Dec 22 22:28:40 top /kernel: usbd_set_config_no: (addr 2) attr=0x60, selfpowered=1, power=0, powerquirk=0 Dec 22 22:28:40 top /kernel: usbd_set_config_no: setting new config 1 Dec 22 22:28:40 top /kernel: usbd_new_device: no interface drivers found Dec 22 22:28:40 top /kernel: ugen0 Dec 22 22:28:40 top /kernel: ugen0: Hewlett-Packard HP ScanJet 4100C (rev 1.00/1.00) addr 2 (device class 0/0) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 22 15:09:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03612 for freebsd-current-outgoing; Tue, 22 Dec 1998 15:09:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03515 for ; Tue, 22 Dec 1998 15:09:18 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA042077056; Tue, 22 Dec 1998 12:17:36 -0500 Date: Tue, 22 Dec 1998 12:17:36 -0500 (EST) From: Bill Fumerola To: freebsd-current@FreeBSD.ORG Subject: re: bin/9091 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 PR references the fact that the automatic administration scripts, /etc/{daily,weekly,monthly,security} all only reference the machine name and not the FQDN of the machine it is run on. This can make centralized administration a pain. Without objections from this list, I will commit the patch contained in this PR. - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@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 Dec 22 15:32:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13567 for freebsd-current-outgoing; Tue, 22 Dec 1998 15:32:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles134.castles.com [208.214.165.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13537 for ; Tue, 22 Dec 1998 15:32: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 PAA01510; Tue, 22 Dec 1998 15:29:47 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812222329.PAA01510@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: brian@worldcontrol.com cc: freebsd-current@FreeBSD.ORG Subject: Re: SANE, USB, -current step 2 In-reply-to: Your message of "Tue, 22 Dec 1998 14:45:25 PST." <19981222144525.A334@top.worldcontrol.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 22 Dec 1998 15:29:46 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ok I plugged my wife's HP 4100cxi and booted with the USB extensions. > The last line look promising: > > Dec 22 22:28:40 top /kernel: ugen0: Hewlett-Packard HP ScanJet 4100C (rev 1.00/1.00) addr 2 (device class 0/0) > > Now does anyone have a primer on using the ugen device to talk to the > device? > > Perhaps /dev/ugen0 is dynamically created and I can talk serially to the > device via read/write? Dream on. 8) USB is not a simple, friendly interface like the adverts want you to think. It's fiendishly complex, and still less than completely designed. The 'ugen' driver is a catchall which will claim a device that nobody else has claimed. It supports nothing, basically. Go the the USB website (www.usb.org), hit the developer's section, and start looking for documents related to scanners. You should probably also talk to HP and ask them for scanner-specific stuff, because the generic scanner class is almost certainly only going to specify the basics of talking to the scanner; there are going to be commands and procedures which are unique to your device. -- \\ 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 Dec 22 15:40:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16799 for freebsd-current-outgoing; Tue, 22 Dec 1998 15:40:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles134.castles.com [208.214.165.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA16771 for ; Tue, 22 Dec 1998 15:40: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 PAA01569; Tue, 22 Dec 1998 15:38:08 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812222338.PAA01569@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Viren R. Shah" cc: freebsd-current@FreeBSD.ORG Subject: Re: error: configured irq 5 not in bitmap of probed irqs 0 In-reply-to: Your message of "Tue, 22 Dec 1998 11:42:54 EST." <199812221642.LAA94393@jabberwock.rstcorp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 22 Dec 1998 15:38:08 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I just upgraded a system running 2.2.6 to -current (from 12/19) and > sio1 is not found -- instead it gives the error msg: > > sio1: configured irq 5 not in bitmap of probed irqs 0 irq5 is almost certainly not the IRQ on which you have sio1. If the IRQ is wrong, the port may also be worong. Check your config... -- \\ 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 Dec 22 15:51:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19779 for freebsd-current-outgoing; Tue, 22 Dec 1998 15:51:17 -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 PAA19774 for ; Tue, 22 Dec 1998 15:51:13 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.1/8.9.1) id RAA69553; Tue, 22 Dec 1998 17:49:45 -0600 (CST) (envelope-from dick) Message-ID: <19981222174945.A69445@tar.com> Date: Tue, 22 Dec 1998 17:49:45 -0600 From: Richard Seaman To: Jeremy Lea Cc: freebsd-current@FreeBSD.ORG Subject: Re: Threads in WINE [was: linking against libc_r] References: <19981221093241.C546@tar.com> <19981221192734.E4060@shale.csir.co.za> <19981221114939.A5500@tar.com> <19981223001304.A319@shale.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19981223001304.A319@shale.csir.co.za>; from Jeremy Lea on Wed, Dec 23, 1998 at 12:13:05AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 23, 1998 at 12:13:05AM +0200, Jeremy Lea wrote: [snip] > > Actually, there are already two "clone" calls within Linux Threads > > right now. There is a wrapper "clone" call that wraps the clone > > syscall (see clone.S in the linux threads source). > > Well, I finally got to looking at the source. It uses clone() directly. In > fact there is no mention of libpthread at all. But there is the following > extract from wine-981211/include/threads.h: [snip] > --- > int SYSDEPS_SpawnThread( THDB *thread ) > { > #ifdef USE_THREADS > > #ifdef HAVE_CLONE_SYSCALL > if (clone( (int (*)(void *))SYSDEPS_StartThread, thread->teb.stack_top, > CLONE_VM | CLONE_FS | CLONE_FILES | SIGCHLD, thread ) < 0) > return -1; > /* FIXME: close the child socket in the parent process */ > /* close( thread->socket );*/ > #endif Ok. This is the wrapped clone call that is used in linux threads. It is also available in the latest glibc. The pure clone syscall only takes two arguments: the flags and the stack top. The liblinuxthreads "port" that I have posted at http://lt.tar.com wraps the rfork call into a call "thr_fork" that was originally posted to the -current list by John Dyson. It is contained in the file rf.S in that distribution, and the file internals.h has a declaration of it. I would say try using thr_fork instead of clone as follows: pid = thrfork( RFPROC | RFMEM | RFTHREAD | RFSIGSHARE, (caddr_t)thread->teb.stack_top, SYSDEPS_StartThread, (unsigned int)thread, NULL, NULL); if (pid < 0) return -1; You can just link against the libpthread that is generated by the port in liblinuxthreads as a quick way to access thr_fork, even if you don't use the other pthreads stuff. > These are the only mentions for HAVE_CLONE_SYSCALL and HAVE_RFORK. Does > this make your mind tick any? The only other condition is a reentrant libc > it would seem... The FreeBSD libc can be partly re-entrant now. In order to make the portions of libc that are designed to be re-entrannt actually behave in that manner, you need to satisfy the following three conditions: 1) You must set the libc variable (which is visible externally) __isthreaded to a non zero value. 2) You must provide an implementation of the function _spinlock which is declared in src/lib/libc/include/spinlock.h. The implementation probably needs to be "recursive" if you're going to get optimum results. _spinlock needs to override the weak aliased _spinlock that is implemented in libc as a stub function 3) You must provide implementations of flockfile, ftrylockfile, and funlockfile. Maybe also _flockfile_debug if you're going to use the debug version. These need to override the weak aliases for these functions in libc, which are also just stub functions. If you link with the libpthreads that is generated by the liblinuxthreads "port" noted above, you should get the three conditions met. Functions that are not re-entrant or thread safe yet (to the best of my knowledge) include: 1) readdir and the related dirent functions 2) localtime, asctime, ctime, etc (note that these are thread safe in libc_r, but you can't use libc_r with linuxthreads or any other kernel threads) 3) In general, any libc function for which the pthreads spec provides an "_r" function (eg. localtime_r). The "_r" functions are generally not provided, and their corresponding non "_r" functions are not thread safe. 4) I don't know about 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 Tue Dec 22 15:58:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20585 for freebsd-current-outgoing; Tue, 22 Dec 1998 15:58:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles134.castles.com [208.214.165.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20575 for ; Tue, 22 Dec 1998 15:58: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 PAA01687; Tue, 22 Dec 1998 15:56:18 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812222356.PAA01687@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Kazutaka YOKOTA cc: current@FreeBSD.ORG Subject: Re: future of syscons In-reply-to: Your message of "Tue, 22 Dec 1998 22:31:07 +0900." <199812221331.WAA09326@zodiac.mech.utsunomiya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 22 Dec 1998 15:56:18 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The kernel configuration file should look: > > controller kbdc0 at isa? port IO_KBD tty > device atkbd0 at isa? tty flags xxxx > device psm0 at isa? tty flags yyy Just to note that ultimately you won't specify the 'tty' mask here, but rather in the interrupt connection function, so: controller atkbdc0 at isa? port IO_KBD device atkbd0 at kbdc? device psm0 at kbdc? Also, since the atkbd and psm device interrupt handlers can only be called from the atkbdc driver, they don't register interrupts and thus don't have/need masks. > device sc0 at isa? tty flags zzz What's this? Don't you mean: pseudo-device syscons 1 (or whatever incantation you want to use to get it included)? > NOTE: pcvt driver will still work after this change. But, it will not > be able to use the USB keyboard. Hellmuth was making noises about working on pcvt. You might want to talk to him about having him focus on the vtxxx emulation features, and perhaps on the personality interface so that we end up with a quality vtxxx emulation as an option? (hm@freebsd.org) In general, excellent! It's great to see this happening at last. 8) Thanks for taking it on! -- \\ 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 Dec 22 19:22:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA15519 for freebsd-current-outgoing; Tue, 22 Dec 1998 19:22:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pinhead.parag.codegen.com (ppp-sfx201--085.sirius.net [205.134.235.85]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA15512 for ; Tue, 22 Dec 1998 19:22:24 -0800 (PST) (envelope-from parag@cgt.com) Received: from pinhead.parag.codegen.com (localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.9.1/8.8.8) with ESMTP id TAA72796 for ; Tue, 22 Dec 1998 19:22:32 -0800 (PST) (envelope-from parag@pinhead.parag.codegen.com) Message-Id: <199812230322.TAA72796@pinhead.parag.codegen.com> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG Subject: Re: More symptoms of VM (or related) oddities in 3.0-CURRENT In-Reply-To: Message from Parag Patel of "Sat, 19 Dec 1998 11:07:12 PST." X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm X-URL: http://www.codegen.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 22 Dec 1998 19:22:32 -0800 From: Parag Patel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To follow up on my own note, I have since discovered that the swap space usage on my disk reported by "top" is slowing increasing for no apparent reason. When I posted the note, the usage was up to 608K. This morning it was up to 8xxK, and right now it is 928K. I expect it to be over 1Mb in the morning. This is on a machine with 256Mb RAM and 256Mb swap. It shouldn't ever even need to touch swap, and with an Oct 23 kernel, never did. A Dec 18 kernel (ELF or AOUT) seems to keep growing. The machine isn't doing anything different nightly that it wasn't doing before, namely nightly "make -j8 buildworld". Any thoughts on where to start looking in the code for this? At least I know the timeframe in which to look (Oct23-Dec18), unless someone can narrow it further. Thanks! -- Parag To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 22 19:25:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA15903 for freebsd-current-outgoing; Tue, 22 Dec 1998 19:25:59 -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 TAA15895 for ; Tue, 22 Dec 1998 19:25:57 -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 TAA00736; Tue, 22 Dec 1998 19:22:56 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812230322.TAA00736@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Parag Patel cc: freebsd-current@FreeBSD.ORG Subject: Re: More symptoms of VM (or related) oddities in 3.0-CURRENT In-reply-to: Your message of "Tue, 22 Dec 1998 19:22:32 PST." <199812230322.TAA72796@pinhead.parag.codegen.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 22 Dec 1998 19:22:56 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > To follow up on my own note, I have since discovered that the swap > space usage on my disk reported by "top" is slowing increasing for no > apparent reason. > > When I posted the note, the usage was up to 608K. This morning it was > up to 8xxK, and right now it is 928K. I expect it to be over 1Mb in > the morning. > > This is on a machine with 256Mb RAM and 256Mb swap. It shouldn't ever > even need to touch swap, and with an Oct 23 kernel, never did. A Dec > 18 kernel (ELF or AOUT) seems to keep growing. The machine isn't doing > anything different nightly that it wasn't doing before, namely nightly > "make -j8 buildworld". This is probably just the proactive pushing out of idle stuff; unless the growth rate truly continues to rise, I wouldn't worry about 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 From owner-freebsd-current Tue Dec 22 19:35:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA16635 for freebsd-current-outgoing; Tue, 22 Dec 1998 19:35:32 -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 TAA16628 for ; Tue, 22 Dec 1998 19:35:28 -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 EAA11928 for ; Wed, 23 Dec 1998 04:35:23 +0100 (CET) (envelope-from girgen@partitur.se) Message-ID: <368064F8.DE58F4E4@partitur.se> Date: Wed, 23 Dec 1998 04:35:20 +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: make build fails on fresh 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! Thought I'd finally upgrade our server to 3.0. cvsupped just an hour ago, and build fails. Any ideas? usr/src is a symlink to /disk3/src, if that matters... uname -a: FreeBSD trumpet.partitur.se 2.2.7-STABLE FreeBSD 2.2.7-STABLE #0: Fri Oct 16 13:20:28 CEST 1998 girgen@trumpet.partitur.se:/disk3/src/sys/compile/TRUMPET i386 make.conf has nothing special, I think. -O -pipe on CFLAGS... and this is what happens: make aout-to-elf-build (also tried make buildworld): ... ===> librpcsvc rpcgen -C -c /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/klm_prot.x -o klm_prot_xdr.c cc -O -pipe -DYP -I/usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc -I/usr/obj/aout/disk3/src/tmp/usr/include -I/usr/obj/aout/disk3/src/tmp/usr/include -c klm_prot_xdr.c -o klm_prot_xdr.o rpcgen -C -c /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/mount.x -o mount_xdr.c cc -O -pipe -DYP -I/usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc -I/usr/obj/aout/disk3/src/tmp/usr/include -I/usr/obj/aout/disk3/src/tmp/usr/include -c mount_xdr.c -o mount_xdr.o rpcgen -C -c /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.x -o nfs_prot_xdr.c cc -O -pipe -DYP -I/usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc -I/usr/obj/aout/disk3/src/tmp/usr/include -I/usr/obj/aout/disk3/src/tmp/usr/include -c nfs_prot_xdr.c -o nfs_prot_xdr.o In file included from nfs_prot_xdr.c:6: /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:265: parse error before `uint64' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:265: warning: data definition has no type or storage class /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:267: parse error before `int64' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:267: warning: data definition has no type or storage class /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:277: parse error before `fileid3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:277: warning: data definition has no type or storage class /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:279: parse error before `cookie3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:279: warning: data definition has no type or storage class /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:291: parse error before `size3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:291: warning: data definition has no type or storage class /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:293: parse error before `offset3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:293: warning: data definition has no type or storage class /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:369: parse error before `size3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:369: warning: no semicolon at end of struct or union /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:370: warning: data definition has no type or storage class /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:372: parse error before `fsid' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:372: warning: data definition has no type or storage class /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:373: parse error before `fileid' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:373: warning: data definition has no type or storage class /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:376: `ctime' redeclared as different kind of symbol /usr/obj/aout/disk3/src/tmp/usr/include/time.h:126: previous declaration of `ctime' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:377: parse error before `}' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:383: field `attributes' has incomplete type /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:389: parse error before `size3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:389: warning: no semicolon at end of struct or union /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:392: parse error before `}' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:398: field `attributes' has incomplete type /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:451: parse error before `size3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:451: warning: no semicolon at end of struct or union /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:451: warning: no semicolon at end of struct or union /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:452: warning: data definition has no type or storage class /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:453: parse error before `}' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:476: field `size' has incomplete type /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:494: field `obj_attributes' has incomplete type /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:625: parse error before `offset3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:625: warning: no semicolon at end of struct or union /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:627: parse error before `}' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:664: parse error before `offset3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:664: warning: no semicolon at end of struct or union /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:671: parse error before `}' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:945: parse error before `cookie3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:945: warning: no semicolon at end of struct or union /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:948: parse error before `}' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:952: parse error before `fileid3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:952: warning: no semicolon at end of struct or union /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:954: parse error before `cookie' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:954: warning: data definition has no type or storage class /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:956: parse error before `}' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:988: parse error before `cookie3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:988: warning: no semicolon at end of struct or union /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:992: parse error before `}' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:996: parse error before `fileid3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:996: warning: no semicolon at end of struct or union /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:998: parse error before `cookie' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:998: warning: data definition has no type or storage class /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1001: conflicting types for `nextentry' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:955: previous declaration of `nextentry' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1002: parse error before `}' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1039: parse error before `size3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1039: warning: no semicolon at end of struct or union /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1040: warning: data definition has no type or storage class /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1041: parse error before `abytes' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1041: warning: data definition has no type or storage class /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1042: parse error before `tfiles' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1042: warning: data definition has no type or storage class /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1043: parse error before `ffiles' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1043: warning: data definition has no type or storage class /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1044: parse error before `afiles' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1044: warning: data definition has no type or storage class /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1046: parse error before `}' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1057: field `resok' has incomplete type /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1081: parse error before `size3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1081: warning: no semicolon at end of struct or union /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1084: parse error before `}' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1095: field `resok' has incomplete type /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1133: parse error before `offset3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1133: warning: no semicolon at end of struct or union /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1135: parse error before `}' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1450: parse error before `uint64' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1451: parse error before `int64' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1456: parse error before `fileid3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1457: parse error before `cookie3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1463: parse error before `size3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1464: parse error before `offset3' *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 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 Tue Dec 22 20:46:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA23805 for freebsd-current-outgoing; Tue, 22 Dec 1998 20:46:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hilda.sci.usq.edu.au (hilda.sci.usq.edu.au [139.86.144.152]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA23762 for ; Tue, 22 Dec 1998 20:45:59 -0800 (PST) (envelope-from vance@usq.edu.au) Received: (qmail 45206 invoked by uid 205); 23 Dec 1998 04:45:52 -0000 Message-ID: <19981223044552.45205.qmail@usq.edu.au> X-Mailer: exmh version 2.0.2 2/24/98 X-Face: VBG60|k'4FzQAk.lEL//A=jDc@.*^5c^^(#755qSb~E~lhP7%JOW!_)Oauu?Y(|)0Xn|UBK Wb$c5EvA>x<^g&TNFNLS9}\FDFw{F,b8%u%>Xb_2}4b}p Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After completing a successful make world on 3.0-CURRENT, I find a make most gives the following error -------------------------------------------------------------- >>> Building programs only -------------------------------------------------------------- cd /usr/src/bin; make all ===> cat ===> chio ===> chmod ===> cp ===> csh ===> date ===> dd cc -O -pipe -Wall -Wformat -c /usr/src/bin/dd/dd.c cc -O -pipe -Wall -Wformat -c /usr/src/bin/dd/position.c cc -O -pipe -Wall -Wformat -static -o dd args.o conv.o conv_tab.o dd.o misc.o position.o ===> df ===> domainname ===> echo ===> ed ===> expr ===> hostname ===> kill ===> ln ===> ls ===> mkdir ===> mv ===> pax cc -O -pipe -Wall -Wformat -c /usr/src/bin/pax/ar_io.c cc -O -pipe -Wall -Wformat -c /usr/src/bin/pax/options.c cc -O -pipe -Wall -Wformat -static -o pax ar_io.o ar_subs.o buf_subs.o cache.o cpio.o file_subs.o ftree.o gen_subs.o options.o pat_rep.o pax.o sel_subs.o tables.o tar.o tty_subs.o ===> ps *** Error code 2 Stop. *** Error code 1 Stop. *** Error code 1 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 Tue Dec 22 20:52:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA24161 for freebsd-current-outgoing; Tue, 22 Dec 1998 20:52:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pinhead.parag.codegen.com (ppp-sfx201--085.sirius.net [205.134.235.85]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA24156 for ; Tue, 22 Dec 1998 20:52:19 -0800 (PST) (envelope-from parag@cgt.com) Received: from pinhead.parag.codegen.com (localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.9.1/8.8.8) with ESMTP id UAA02634 for ; Tue, 22 Dec 1998 20:52:14 -0800 (PST) (envelope-from parag@pinhead.parag.codegen.com) Message-Id: <199812230452.UAA02634@pinhead.parag.codegen.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: Re: trap 12 with interrupts disabled In-Reply-To: Message from Andreas Braukmann of "Tue, 22 Dec 1998 09:00:55 +0100." <19981222090055.A24544@paert.tse-online.de> X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm X-URL: http://www.codegen.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 22 Dec 1998 20:52:14 -0800 From: Parag Patel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am getting "trap 25 with interrupts disabled" whenever I run "doscmd". Anyone else seen this? Perhaps these messages should only show up for a kernel booted with "-v"? (doscmd appears to run fine but tends to fill up the dmesg buffer.) -- Parag To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 22 23:36:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA10262 for freebsd-current-outgoing; Tue, 22 Dec 1998 23:36: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 XAA10256 for ; Tue, 22 Dec 1998 23:36:08 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id XAA12484; Tue, 22 Dec 1998 23:35:53 -0800 (PST) (envelope-from dillon) Date: Tue, 22 Dec 1998 23:35:53 -0800 (PST) From: Matthew Dillon Message-Id: <199812230735.XAA12484@apollo.backplane.com> To: Parag Patel Cc: freebsd-current@FreeBSD.ORG Subject: Re: More symptoms of VM (or related) oddities in 3.0-CURRENT References: <199812230322.TAA72796@pinhead.parag.codegen.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :To follow up on my own note, I have since discovered that the swap :space usage on my disk reported by "top" is slowing increasing for no :apparent reason. : :When I posted the note, the usage was up to 608K. This morning it was :up to 8xxK, and right now it is 928K. I expect it to be over 1Mb in :the morning. : :This is on a machine with 256Mb RAM and 256Mb swap. It shouldn't ever :even need to touch swap, and with an Oct 23 kernel, never did. A Dec :18 kernel (ELF or AOUT) seems to keep growing. The machine isn't doing :anything different nightly that it wasn't doing before, namely nightly :"make -j8 buildworld". : :Any thoughts on where to start looking in the code for this? At least :I know the timeframe in which to look (Oct23-Dec18), unless someone can :narrow it further. Thanks! : : : -- Parag I don't think you have to worry about this, it's probably just the system swapping out totally idle data. You can investigate it a bit if you want if you are have /proc mounted: foreach i ( /proc/* ) if ( -f $i/map ) then cat $i/status | awk '{ print $1 "\t" $2; }' fgrep swap $i/map endif end -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 23 00:52:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA15354 for freebsd-current-outgoing; Wed, 23 Dec 1998 00:49:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA15342 for ; Wed, 23 Dec 1998 00:48:58 -0800 (PST) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (2268 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Wed, 23 Dec 1998 09:48:33 +0100 (MET) (Smail-3.2.0.101 1997-Dec-17 #2 built 1998-Jun-26) Received: by hcswork.hcs.de (Smail3.1.29.0 #12) id m0zsk17-0000fiC; Wed, 23 Dec 98 09:51 MET Message-Id: From: hm@hcs.de (Hellmuth Michaelis) Subject: Re: future of syscons In-Reply-To: <199812222356.PAA01687@dingo.cdrom.com> from Mike Smith at "Dec 22, 98 03:56:18 pm" To: mike@smith.net.au (Mike Smith) Date: Wed, 23 Dec 1998 09:51:40 +0100 (MET) Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp, current@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (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 >From the keyboard of Mike Smith: > Hellmuth was making noises about working on pcvt. You might want to > talk to him about having him focus on the vtxxx emulation features, and > perhaps on the personality interface so that we end up with a quality > vtxxx emulation as an option? (hm@freebsd.org) At that time i worked on a version of pcvt containing all the patches and fixes people sent in and the ones i grabbed from PR's. Further, all the ifdef spaghetti is removed (and as a result, only FreeBSD is supported anymore) and all the dead code of the "old" way of X server interfacing. The result is available at http://www.hcs.de/users/hm/hm-projects.html Pcvt needs much more cleanup and some enhancements here and there, and when i realized how much work this would be, i stopped ;-) Instead of working on pcvt, i would let it rest in peace if it were possible to move its functionality to a new modularized and open console driver. The idea of such a modularized open console driver is nice and i certainly like to work on a (pc)VT emulation for it. hellmuth -- Hellmuth Michaelis Tel +49 40 559747-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 559747-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de 22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 23 01:03:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA16900 for freebsd-current-outgoing; Wed, 23 Dec 1998 01:03:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles349.castles.com [208.214.167.49]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA16894 for ; Wed, 23 Dec 1998 01:03:39 -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 BAA00688; Wed, 23 Dec 1998 01:01:19 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812230901.BAA00688@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Steve Kargl cc: freebsd-current@FreeBSD.ORG Subject: Re: Fortran conundrum In-reply-to: Your message of "Mon, 21 Dec 1998 22:49:19 PST." <199812220649.WAA46833@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 23 Dec 1998 01:01:18 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As I promised Mike Smith, I have been looking over the Fortran > situation in -current. From the last round of email, we had > essentially 3 opinions: > > (1) Status quo You make a good case for this being unsupportable. > (2) Upgrade to g77 -- g77 produces "better" code than f2c+gcc, and it > is designed to integrate smoothly with the core compiler technology > when an upgrad finally occurs. > > Unfortunately, g77+0.5.23 is designed to work with gcc+2.8.x, and > the author(s) of g77 warn to not even try to back port g77 to any > earlier version of gcc. The jury is still out on the gcc-2.8 vs. egcs issues. However, I think that the general feeling is that this is a bad trend. Fortran is an important application, but it's not part of the core system. > (3) Rip Fortran out of the base distribution. > > This seem to be the logical choice (provided f2c can be converted > to a port). I have been merging our f2c and the sources from netlib > with the intend to produce a port. There is, however, one major > caveat that needs to be address. /usr/bin/f77 is a driver program > which sets up an execution of our Fortran-aware gcc frontend > (see src/gnu/usr.bin/cc/f77). I have been unsuccessful in moving this > driver out of src/gnu, and still retain its functionality. Can you clarify on the problems inherent in moving the f77 executable? > Thus, I recommend removal of f2c and libf2c, but we retain our > current f77 and Fortran-aware gcc. I'll work on providing a > a patch to gnu/usr.bin/cc/f77 (and its man page) to deal with > the moving of f2c to the ports collection. > > Comments? Basically, I think that (3) is the approach of preference for now; it offers the best of all the possibilities - f77 remains available for those that want to continue to use it, and g77 (or any other enahced version) becomes a full alternative. It would be desirable to have f77 leave the main tree, but most definitely leave the Fortran awareness in the 'gcc' driver program, as well as the system Makefiles. -- \\ 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 Dec 23 01:08:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA17533 for freebsd-current-outgoing; Wed, 23 Dec 1998 01:08:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles349.castles.com [208.214.167.49]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA17527 for ; Wed, 23 Dec 1998 01:08: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 BAA00744; Wed, 23 Dec 1998 01:06:21 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812230906.BAA00744@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Ben Smithurst cc: freebsd-current@FreeBSD.ORG Subject: Re: CD-ROM drive stays locked In-reply-to: Your message of "Fri, 18 Dec 1998 20:30:23 GMT." <19981218203023.A315@scientia.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 23 Dec 1998 01:06:21 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If I do `mount /cdrom' without a CD-ROM in the (IDE) drive, the > drive remains locked, and I can't eject the drive after that without > disconnecting/reconnecting its power. The following patch seems to fix > it, although is it possible there will be some unwanted side-effects? > > (Also, why does the error message say `audio disc'? If there's no disc > in I don't see why it should care about it being an audio disc or not.) I think it's because some drives will return this sense key if the disk is an audio disk, but I don't actually have one like that. > --- wcd.c~ Fri Dec 18 19:31:34 1998 > +++ wcd.c Fri Dec 18 19:22:33 1998 > @@ -692,6 +692,7 @@ > if (result.error & ~AER_SKEY) { > /* Audio disc. */ > printf ("wcd%d: cannot read audio disc\n", t->lun); > + t->flags &= ~F_LOCKED; > return; > } > /* Tray open. */ Looks good, seems to work OK. Committed. -- \\ 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 Dec 23 01:48:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA21492 for freebsd-current-outgoing; Wed, 23 Dec 1998 01:48:46 -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 BAA21486 for ; Wed, 23 Dec 1998 01:48:44 -0800 (PST) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 752 invoked by uid 100); 23 Dec 1998 05:36:58 -0000 Date: Tue, 22 Dec 1998 21:36:58 -0800 To: Mike Smith Cc: freebsd-current@FreeBSD.ORG Subject: Re: SANE, USB, -current step 2 Message-ID: <19981222213658.A743@top.worldcontrol.com> Mail-Followup-To: Mike Smith , freebsd-current@FreeBSD.ORG References: <19981222144525.A334@top.worldcontrol.com> <199812222329.PAA01510@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.17i In-Reply-To: <199812222329.PAA01510@dingo.cdrom.com>; from Mike Smith on Tue, Dec 22, 1998 at 03:29:46PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [brian@litzinger.com wrote]: > > Now does anyone have a primer on using the ugen device to talk to the > > device? > > Perhaps /dev/ugen0 is dynamically created and I can talk serially to the > > device via read/write? On Tue, Dec 22, 1998 at 03:29:46PM -0800, Mike Smith wrote: > Dream on. 8) At some level isn't it a generic serial bus? Can't anyone ever do anything in an easy and straight forward manner? Shouldn't I be able to bypass the HID/Class stuff and talk directly to the device regardless of the hideously horrible manufacturer specific protocol it may speak? Then I could add the HID/Class stuff later. I promise. ;-) -- Brian Litzinger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 23 02:04:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA22985 for freebsd-current-outgoing; Wed, 23 Dec 1998 02:04:23 -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 CAA22966 for ; Wed, 23 Dec 1998 02:04:15 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40330>; Wed, 23 Dec 1998 21:03:18 +1100 Date: Wed, 23 Dec 1998 21:04:02 +1100 From: Peter Jeremy Subject: Re: Fortran conundrum To: current@FreeBSD.ORG Message-Id: <98Dec23.210318est.40330@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steve Kargl wrote: > essentially 3 opinions: > (1) Status quo > (2) Upgrade to g77 > (3) Rip Fortran out of the base distribution. FWIW, I'd support option 3, with the proviso that Fortran be available as a `supported' port. In general, I believe that the base system should remain as small as practical, with more emphasis on providing added functionality via ports (or a more finely-grained sysinstall). The approach used by Solaris is much nicer in principle (although the total lack of meaningful descriptions on the various packages makes it useless in practice). I also don't like the idea of an `it sort-of works' Fortran in the base distribution, with the side-note that you'll have to install g77 (or whatever) from the ports if you're going to be doing any serious development. This reminds me too much of the cc in SunOS 4.x. I'd prefer to have the option not to install UUCP, groff (unnecessary if you're installing cat* pages), sendmail, NIS, etc as well. Mike Smith wrote: >It would be desirable to have f77 leave the main tree, but most >definitely leave the Fortran awareness in the 'gcc' driver program, as >well as the system Makefiles. And add stub executables that say `X is not currently available, you can install it with "pkg_add foo" or "cd /usr/ports/bar/foo; make install"'. I'm not sure how much fortran awareness is actually coded into gcc. I suspect most (if not all) of it is (or could be) in the `specs' file that it reads on startup. 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 Dec 23 03:22:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA01144 for freebsd-current-outgoing; Wed, 23 Dec 1998 03:22:06 -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 DAA01139 for ; Wed, 23 Dec 1998 03:22:04 -0800 (PST) (envelope-from geoffb@gti.noc.demon.net) Received: by server.noc.demon.net; id LAA28838; Wed, 23 Dec 1998 11:21:59 GMT Received: from gti.noc.demon.net(195.11.55.101) by inside.noc.demon.net via smap (3.2) id xma028829; Wed, 23 Dec 98 11:21:50 GMT Received: (from geoffb@localhost) by gti.noc.demon.net (8.8.8/8.8.8) id LAA05903; Wed, 23 Dec 1998 11:21:47 GMT Message-ID: <19981223112147.B5215@gti.noc.demon.net> Date: Wed, 23 Dec 1998 11:21:47 +0000 From: Geoff Buckingham To: Harry Starr , current Subject: Re: Problems with CAM and ncr Reply-To: geoffb@demon.net References: <001501be2da8$fb35b830$0a9811cb@gccs.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <001501be2da8$fb35b830$0a9811cb@gccs.com.au>; from Harry Starr on Tue, Dec 22, 1998 at 10:45:38PM +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 22, 1998 at 10:45:38PM +1000, Harry Starr wrote: > There seems to be a major problem with the new CAM code and the ncr driver. > > Config: > > Asus SC200 (ncr810) in Asus P2L97 M/B with PII-300 and 128MB mem. > > With "hard" disk access (Make world; or Make release), more than likely, the > ncr driver will give an error message of ncr:::queue empty, at which point > the system will lock up (pager errors, etc). This is almost 100% > reproducible. > > The SCSI drives are "old" Conner Cp3470. I'm not sure if there were problems > with tagged queueing in this model; but they worked OK in a DG/UX system. > Someone more knowledgable than me will doubtless be along in a bit, but I have had the NCR driver working with CAM for build world etc without problems however that machine has a 'modern' drive. You may be able to eliminate TAG problems by adding a quirk to /usr/src/sys/cam/cam_xpt.c specifying a lower maxtags, then compiling a new kernel. I have one for a hardware RAID which was causing hangs: { /* Delf Stuff */ { T_ANY, SIP_MEDIA_REMOVABLE|SIP_MEDIA_FIXED, /*vendor*/"C_Design", /*product*/"DELFRaid", /*revision*/"0131 " }, /*quirks*/0, /*mintags*/24, /*maxtags*/28 }, This seems to have fixed it (one week uptime, was crashing within 30 mins of disk load) If someone from the CAM group happens along: Is there a methed for submision and review of such quirks? I have raised a non critical kernel PR for the above, although I must revise it as I have altered min/maxtags since submiting it. There is no scientific method for the values chosen above, they just seem to prevent the hangs and excesivly uneven distribution of TAGs between logical devices within the RAID. > The ncr driver previously reports that "tagged openings is now 31". > > Reverting to a kernel dated "8-Aug-1998" alleviates the problem. > > Any thoughts ?? > -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 23 04:26:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA08670 for freebsd-current-outgoing; Wed, 23 Dec 1998 04:26:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bsd1.gccs.com.au (router.gccs.com.au [203.17.152.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA08651 for ; Wed, 23 Dec 1998 04:25:57 -0800 (PST) (envelope-from starr3@gccs.com.au) Received: from lb50x (lb50x.gccs.com.au [203.17.152.10]) by bsd1.gccs.com.au (8.9.1/8.9.1) with SMTP id WAA02640; Wed, 23 Dec 1998 22:25:33 +1000 (EST) Message-ID: <002f01be2e6f$56a16d60$0a9811cb@gccs.com.au> From: "Harry Starr" To: , "current" Subject: Re: Problems with CAM and ncr Date: Wed, 23 Dec 1998 22:25:33 +1000 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 Actually, I did put a "disable tags" quirk into cam_xpt.c, and it seems to be stable now. Is/Has anyone had success using the CAM stuff against IBM Ultrastar drives (9GB, 18GB) ?? I plan on switching to those when I retire these "old", problematic CONNERs. Harry. ----- Original Message ----- From: Geoff Buckingham To: Harry Starr ; current Sent: Wednesday, December 23, 1998 9:21 PM Subject: Re: Problems with CAM and ncr >On Tue, Dec 22, 1998 at 10:45:38PM +1000, Harry Starr wrote: >> There seems to be a major problem with the new CAM code and the ncr driver. >> >> Config: >> >> Asus SC200 (ncr810) in Asus P2L97 M/B with PII-300 and 128MB mem. >> >> With "hard" disk access (Make world; or Make release), more than likely, the >> ncr driver will give an error message of ncr:::queue empty, at which point >> the system will lock up (pager errors, etc). This is almost 100% >> reproducible. >> >> The SCSI drives are "old" Conner Cp3470. I'm not sure if there were problems >> with tagged queueing in this model; but they worked OK in a DG/UX system. >> >Someone more knowledgable than me will doubtless be along in a bit, but >I have had the NCR driver working with CAM for build world etc without >problems however that machine has a 'modern' drive. > >You may be able to eliminate TAG problems by adding a quirk to >/usr/src/sys/cam/cam_xpt.c specifying a lower maxtags, then compiling >a new kernel. I have one for a hardware RAID which was causing hangs: > > { > /* Delf Stuff */ > { > T_ANY, SIP_MEDIA_REMOVABLE|SIP_MEDIA_FIXED, > /*vendor*/"C_Design", /*product*/"DELFRaid", /*revision*/"0131 >" > }, > /*quirks*/0, /*mintags*/24, /*maxtags*/28 > }, > >This seems to have fixed it (one week uptime, was crashing within 30 mins of >disk load) > >If someone from the CAM group happens along: Is there a methed for submision >and review of such quirks? I have raised a non critical kernel PR for the >above, although I must revise it as I have altered min/maxtags since >submiting it. > >There is no scientific method for the values chosen above, they just >seem to prevent the hangs and excesivly uneven distribution of TAGs >between logical devices within the RAID. > >> The ncr driver previously reports that "tagged openings is now 31". >> >> Reverting to a kernel dated "8-Aug-1998" alleviates the problem. >> >> Any thoughts ?? >> >-- >GeoffB > >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 Dec 23 04:51:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA11969 for freebsd-current-outgoing; Wed, 23 Dec 1998 04:51:45 -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 EAA11964 for ; Wed, 23 Dec 1998 04:51:43 -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.1a/8.9.1) with ESMTP id MAA31153; Wed, 23 Dec 1998 12:51:21 GMT Message-ID: <3680E749.B3B05412@tdx.co.uk> Date: Wed, 23 Dec 1998 12:51:21 +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: Harry Starr CC: geoffb@demon.net, current Subject: Re: Problems with CAM and ncr References: <002f01be2e6f$56a16d60$0a9811cb@gccs.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Harry Starr wrote: > > Actually, I did put a "disable tags" quirk into cam_xpt.c, and it seems to > be stable now. > > Is/Has anyone had success using the CAM stuff against IBM Ultrastar drives > (9GB, 18GB) ?? > I plan on switching to those when I retire these "old", problematic CONNERs. > > Harry. I have an UltraStar 2XP and an UltraStar 9ZX - (4.5/9Gb respectively). They are 'very fast' drives, the EZ especially - both appear to work with -current and CAM with no problems... Both report to be using 64 tag's after having been 'hammered' by a MakeWorld etc. In fact - I'd probably go as far as saying, they are the best drives on my system at the moment (out of our of Seagate, Quantum, Maxtor & WesternDigi) -Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 23 05:12:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA14396 for freebsd-current-outgoing; Wed, 23 Dec 1998 05:12:23 -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 FAA14390 for ; Wed, 23 Dec 1998 05:12:20 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.1/8.9.1) id HAA77531; Wed, 23 Dec 1998 07:10:40 -0600 (CST) (envelope-from dick) Date: Wed, 23 Dec 1998 07:10:40 -0600 From: Richard Seaman To: Jeremy Lea Cc: freebsd-current@FreeBSD.ORG Subject: Re: Threads in WINE [was: linking against libc_r] Message-ID: <19981223071040.A77487@ns.tar.com> References: <19981221093241.C546@tar.com> <19981221192734.E4060@shale.csir.co.za> <19981221114939.A5500@tar.com> <19981223001304.A319@shale.csir.co.za> <19981222174945.A69445@tar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <19981222174945.A69445@tar.com>; from Richard Seaman on Tue, Dec 22, 1998 at 05:49:45PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 22, 1998 at 05:49:45PM -0600, Richard Seaman wrote: > > The FreeBSD libc can be partly re-entrant now. In order to make the portions > of libc that are designed to be re-entrannt actually behave in that manner, > you need to satisfy the following three conditions: > > 1) You must set the libc variable (which is visible externally) > __isthreaded to a non zero value. > > 2) You must provide an implementation of the function _spinlock > which is declared in src/lib/libc/include/spinlock.h. The > implementation probably needs to be "recursive" if you're going > to get optimum results. > > _spinlock needs to override the weak aliased _spinlock that > is implemented in libc as a stub function > > 3) You must provide implementations of flockfile, ftrylockfile, > and funlockfile. Maybe also _flockfile_debug if you're going > to use the debug version. > > These need to override the weak aliases for these functions > in libc, which are also just stub functions. > > If you link with the libpthreads that is generated by the > liblinuxthreads "port" noted above, you should get the > three conditions met. My brain was only partly in gear when I wrote this. There is an important fourth condition imposed by the specific implementations of _spinlock, flockfile, ftrylockfile and funlockfile included with liblinuxthreads. They all use pthread_self, or its relative, thread_self. You must create your threads using pthread_create for pthread_self to 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 Wed Dec 23 05:52:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA19306 for freebsd-current-outgoing; Wed, 23 Dec 1998 05:52:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lion.plab.ku.dk (lion.plab.ku.dk [130.225.105.49]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA19290 for ; Wed, 23 Dec 1998 05:52:27 -0800 (PST) (envelope-from tobez@lion.plab.ku.dk) Received: from localhost (1703 bytes) by lion.plab.ku.dk via sendmail with P:stdio/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) (ident using unix) id for ; Wed, 23 Dec 1998 14:50:50 +0100 (CET) (Smail-3.2.0.101 1997-Dec-17 #1 built 1998-Nov-8) To: freebsd-current@FreeBSD.ORG Subject: Re: make build fails on fresh current References: <368064F8.DE58F4E4@partitur.se> From: Anton Berezin Date: 23 Dec 1998 14:50:47 +0100 In-Reply-To: Palle Girgensohn's message of Wed, 23 Dec 1998 04:35:20 +0100 Message-ID: <86g1a7klvs.fsf@lion.plab.ku.dk> Lines: 35 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Palle Girgensohn writes: > Thought I'd finally upgrade our server to 3.0. cvsupped just an hour > ago, and build fails. Any ideas? > > uname -a: > FreeBSD trumpet.partitur.se 2.2.7-STABLE FreeBSD 2.2.7-STABLE #0: Fri > Oct 16 13:20:28 CEST 1998 > girgen@trumpet.partitur.se:/disk3/src/sys/compile/TRUMPET i386 > > make.conf has nothing special, I think. -O -pipe on CFLAGS... > > and this is what happens: > > make aout-to-elf-build (also tried make buildworld): > In file included from nfs_prot_xdr.c:6: > /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:265: parse > error before `uint64' I've got _exactly_ the same results on my system yesterday. It looks like generated nfs_prot.h did not include some relevant header so that types like ulonglong_t were left undefined. Can a knowledgeable person on the list elaborate on this? Is it something 2.2.7 -> 3.0 specific? Or something wrong with cvsuped tree (December 22, Danish mirror)? (I am not the type doing cvsup and buildworld every day, I simply thought that following this way will make easier the upgrade of an existing system). Thank you in advance, -- Anton Berezin The Protein Laboratory, University of Copenhagen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 23 05:54:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA19522 for freebsd-current-outgoing; Wed, 23 Dec 1998 05:54:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from singularity.enigami.com (singularity.enigami.com [208.140.182.42]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA19492 for ; Wed, 23 Dec 1998 05:53:52 -0800 (PST) (envelope-from ckempf@singularity.enigami.com) Received: (from ckempf@localhost) by singularity.enigami.com (8.9.1/8.9.1) id IAA22829; Wed, 23 Dec 1998 08:53:41 -0500 (EST) To: freebsd-current@FreeBSD.ORG Subject: Wingz3 Permission problem From: Cory Kempf Date: 23 Dec 1998 08:53:41 -0500 Message-ID: Lines: 16 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I just downloaded the Linux version of Wingz3. It runs, if I attempt to run it as root, but not as a normal user. My guess is that there is some sort of permittion problem somewhere, but I can't find it. Anyone know what it might be? Or have suggestions of how to locate it? Thanks, +C -- Thinking of purchasing RAM from the Chip Merchant? Please read this first: Cory Kempf Macintosh / Unix Consulting & Software Development ckempf@enigami.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 23 06:28:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23627 for freebsd-current-outgoing; Wed, 23 Dec 1998 06:28:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from assurance.rstcorp.com (assurance.rstcorp.com [206.29.49.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA23616 for ; Wed, 23 Dec 1998 06:28:10 -0800 (PST) (envelope-from vshah@rstcorp.com) Received: (from uucp@localhost) by assurance.rstcorp.com (8.8.8/8.8.8) id JAA25840; Wed, 23 Dec 1998 09:28:04 -0500 Received: from sandbox.rstcorp.com(206.29.49.63) by assurance.rstcorp.com via smap (V2.0) id xma025835; Wed, 23 Dec 98 09:27:19 -0500 Received: from jabberwock.rstcorp.com (jabberwock [206.29.49.98]) by sandbox.rstcorp.com (8.8.8/8.8.8) with ESMTP id JAA22473; Wed, 23 Dec 1998 09:27:18 -0500 (EST) Received: (from vshah@localhost) by jabberwock.rstcorp.com (8.9.1/8.8.8) id JAA58921; Wed, 23 Dec 1998 09:27:19 -0500 (EST) Date: Wed, 23 Dec 1998 09:27:19 -0500 (EST) Message-Id: <199812231427.JAA58921@jabberwock.rstcorp.com> From: "Viren R. Shah" To: Mike Smith Cc: freebsd-current@FreeBSD.ORG Subject: Re: error: configured irq 5 not in bitmap of probed irqs 0 In-Reply-To: <199812222338.PAA01569@dingo.cdrom.com> References: <199812221642.LAA94393@jabberwock.rstcorp.com> <199812222338.PAA01569@dingo.cdrom.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: "Viren R. Shah" X-Face: )~y+U*K:yzjz{q<5lzpI_SVef'U.])9g[C9`1N@]u3,MHY7f*l7C)[_NjM4y4K8$uIUh|\u (K&&HS6,M!61&GMTk'mqmB/Qg]]X}"?TzsFl]"2v!bl8']dma.:^IY^a[lbOI>U:b<~FyK3q-p{HmZ mn~g.`~BE!5{2D:}Yi+\_KkWe?XaHj9$ko1k8iKLYv5*_2c8"G=?Up[}hn+7RNM(bzBZ_wWk6!Pf&B ?3Tcm7M7B~W%K/I0aX3]*=jP?aM]H6HBPT`oLk+0n^_;N\2\%|Rhy;p}34Q.jEsM\qtnxcm;ag%Nq Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Mike" == Mike Smith writes: >> >> >> I just upgraded a system running 2.2.6 to -current (from 12/19) and >> sio1 is not found -- instead it gives the error msg: >> >> sio1: configured irq 5 not in bitmap of probed irqs 0 Mike> irq5 is almost certainly not the IRQ on which you have sio1. If the Mike> IRQ is wrong, the port may also be worong. Check your config... Actually, it is on irq 5 (This is an old EISA machine -- the config is all screwed up). I finally got the error/warning to stop, and the internal modem working. Apparently, the main problem was that when setting up the pnp information for the modem, I was giving it irq4 and port 0x3f8 -- which is sio0. This seemed to cause grief. When I changed it to irq 5 and port 0x2f8, it works. Thanks Viren -- Viren R. Shah || "I wandered lonely as a cloud" viren@rstcorp.com || -- WW Research Associate, Reliable Software Technologies Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 23 07:34:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA29571 for freebsd-current-outgoing; Wed, 23 Dec 1998 07:30:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ramsack.baldcom.net (mail.BALDCOM.NET [205.232.46.4]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA29539 for ; Wed, 23 Dec 1998 07:30:01 -0800 (PST) (envelope-from klmac@baldcom.net) Received: from [10.0.1.82] [209.150.236.67] by ramsack.baldcom.net with ESMTP (SMTPD32-4.06) id AF2D27D40154; Wed, 23 Dec 1998 10:41:33 DT X-Sender: agent47@mail.baldcom.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 23 Dec 1998 10:31:08 -0500 To: freebsd-current@freebsd.org From: Ken McKittrick Subject: Problems compiling kernel for 3.0-19980804-SNAP system Sender: owner-freebsd-current@freebsd.org Precedence: bulk X-Loop: FreeBSD.ORG Hello I'm trying to patch a production machine running 3.0-19980804-SNAP with and SMP kernel. The system has not been upgraded since then. The last time I recompiled the kernel was Sep 5th. I have the source tree from 3.0-19980804-SNAP installed in /usr/src. I'm getting the following error. Kernel build directory is ../../compile/SMP-JANUS janus# cd ../../compile/SMP-JANUS janus# make depend cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitializ ed -Wformat -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../inc lude -DKERNEL -include opt_global.h -UKERNEL ../../i386/i386/genassym.c cc1: Invalid option `-fformat-extensions' *** Error code 1 What do I look for to make this work? Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 23 07:46:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA01196 for freebsd-current-outgoing; Wed, 23 Dec 1998 07:46:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.linet.it (relay.linet.it [194.185.24.71]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA01185 for ; Wed, 23 Dec 1998 07:46:36 -0800 (PST) (envelope-from andrea.franceschini@linet.it) Received: from oma.linet.it (unverified [194.185.24.77]) by relay.linet.it (EMWAC SMTPRS 0.83) with SMTP id ; Wed, 23 Dec 1998 16:35:59 +0100 Message-ID: <008601be3989$48cf4ac0$4d18b9c2@oma.linet.it> Reply-To: "andrea" From: "andrea" To: Subject: PPTP and FreeBSD Date: Wed, 6 Jan 1999 16:29:00 +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.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All I read in man -pages of ppp about the support for VPN . I wonder if is compatible with PPTP ,i tried some configuration but something goes wrong. There's any PPTP 'driver' for FreeBSD is it comaptible with the M$ one? Thank you! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 23 07:59:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA02770 for freebsd-current-outgoing; Wed, 23 Dec 1998 07:59:10 -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 HAA02763 for ; Wed, 23 Dec 1998 07:59:08 -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 IAA17637; Wed, 23 Dec 1998 08:06:06 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199812231606.IAA17637@troutmask.apl.washington.edu> Subject: Re: Fortran conundrum In-Reply-To: <199812230901.BAA00688@dingo.cdrom.com> from Mike Smith at "Dec 23, 1998 1: 1:18 am" To: mike@smith.net.au (Mike Smith) Date: Wed, 23 Dec 1998 08:06: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 According to Mike Smith: > > (3) Rip Fortran out of the base distribution. > > > > This seem to be the logical choice (provided f2c can be converted > > to a port). I have been merging our f2c and the sources from netlib > > with the intend to produce a port. There is, however, one major > > caveat that needs to be address. /usr/bin/f77 is a driver program > > which sets up an execution of our Fortran-aware gcc frontend > > (see src/gnu/usr.bin/cc/f77). I have been unsuccessful in moving this > > driver out of src/gnu, and still retain its functionality. > > Can you clarify on the problems inherent in moving the f77 executable? > f77.c contains #include "config.h", and I haven't located where this header lives. It defines preprocessor directives like HAVE_VPRINTF, but it may in fact contain other things that are less obvious to me. I'm still looking at what I can do with f77.c. I've submitted a PR that removes quite a bit of dead code in f77.c. -- 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 Wed Dec 23 08:26:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA05795 for freebsd-current-outgoing; Wed, 23 Dec 1998 08:25:55 -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 IAA05790 for ; Wed, 23 Dec 1998 08:25:53 -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 LAA02257; Wed, 23 Dec 1998 11:29:14 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Wed, 23 Dec 1998 11:29:14 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Ken McKittrick cc: freebsd-current@freebsd.org Subject: Re: Problems compiling kernel for 3.0-19980804-SNAP system 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 Wed, 23 Dec 1998, Ken McKittrick wrote: > Hello > > I'm trying to patch a production machine running 3.0-19980804-SNAP with and > SMP kernel. The system has not been upgraded since then. The last time I > recompiled the kernel was Sep 5th. > > I have the source tree from 3.0-19980804-SNAP installed in /usr/src. > > I'm getting the following error. > > Kernel build directory is ../../compile/SMP-JANUS > janus# cd ../../compile/SMP-JANUS > janus# make depend > cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline > -Wuninitializ > ed -Wformat -fformat-extensions -ansi -nostdinc -I- -I. -I../.. > -I../../../inc > lude -DKERNEL -include opt_global.h -UKERNEL ../../i386/i386/genassym.c > cc1: Invalid option `-fformat-extensions' > *** Error code 1 > > What do I look for to make this work? > I think you have /usr/local/bin in your path before /usr/bin and therefore are running egcs. check which cc you are using and fix your path. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current > Ken > > > > 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 Dec 23 08:42:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA07973 for freebsd-current-outgoing; Wed, 23 Dec 1998 08:42:23 -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 IAA07959 for ; Wed, 23 Dec 1998 08:42: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.1/8.9.1) with ESMTP id IAA30168; Wed, 23 Dec 1998 08:42:02 -0800 (PST) To: "andrea" cc: freebsd-current@FreeBSD.ORG Subject: Re: PPTP and FreeBSD In-reply-to: Your message of "Wed, 06 Jan 1999 16:29:00 +0100." <008601be3989$48cf4ac0$4d18b9c2@oma.linet.it> Date: Wed, 23 Dec 1998 08:42:02 -0800 Message-ID: <30164.914431322@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > There's any PPTP 'driver' for FreeBSD is it comaptible with the M$ one? There is not, I'm afraid. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 23 08:44:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA08342 for freebsd-current-outgoing; Wed, 23 Dec 1998 08:44:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles246.castles.com [208.214.165.246]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA08328 for ; Wed, 23 Dec 1998 08:44:42 -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 IAA02820; Wed, 23 Dec 1998 08:42:18 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812231642.IAA02820@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: brian@worldcontrol.com cc: freebsd-current@FreeBSD.ORG Subject: Re: SANE, USB, -current step 2 In-reply-to: Your message of "Tue, 22 Dec 1998 21:36:58 PST." <19981222213658.A743@top.worldcontrol.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 23 Dec 1998 08:42:17 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > [brian@litzinger.com wrote]: > > > Now does anyone have a primer on using the ugen device to talk to the > > > device? > > > > Perhaps /dev/ugen0 is dynamically created and I can talk serially to the > > > device via read/write? > > On Tue, Dec 22, 1998 at 03:29:46PM -0800, Mike Smith wrote: > > Dream on. 8) > > At some level isn't it a generic serial bus? Can't anyone ever do > anything in an easy and straight forward manner? No. No. > Shouldn't I be able to bypass the HID/Class stuff and talk directly > to the device regardless of the hideously horrible manufacturer > specific protocol it may speak? "Should?", perhaps. But you can't, so stop whining. 8) > Then I could add the HID/Class stuff later. I promise. ;-) Yeah, right. 8) Seriously, USB and its protocols have some fairly good reasons for existing, and making whiny compromises like you're proposing impossible is one of them. Most hardware vendors wouldn't make the promise you're making, and thus the protocols make cheating very difficult. -- \\ 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 Dec 23 09:31:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13733 for freebsd-current-outgoing; Wed, 23 Dec 1998 09:31:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13726 for ; Wed, 23 Dec 1998 09:31:45 -0800 (PST) (envelope-from vjs@calcite.rhyolite.com) Received: (from vjs@localhost) by calcite.rhyolite.com (8.9.0/calcite) id KAA25703 env-from ; Wed, 23 Dec 1998 10:30:55 -0700 (MST) Date: Wed, 23 Dec 1998 10:30:55 -0700 (MST) From: Vernon Schryver Message-Id: <199812231730.KAA25703@calcite.rhyolite.com> To: acee@raleigh.ibm.com, core@netBSD.org, freebsd-current@FreeBSD.ORG, humble@csd-31502.anf.unf.edu, pst@juniper.net, thorpej@nas.nasa.gov, wollman@lcs.mit.edu, works@calcite.rhyolite.com Subject: newer version of routed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I hope one or more of you are the right people I should notify of a new version of `routed`. ftp.rhyolite.com:src/routed.tar.Z (or via www.rhyolitec.com) contains what I've labeled version 2.16 (see `routed -v`). It has a few printf pattern bug fixes (including one potential core-dump) and a whole raft of pedantic fiddles to make some gcc warnings go away. As always, when and if you integrate this version into your tree(s), I would be glad to hear about any changes you find necessary. Vernon Schryver vjs@rhyolite.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 23 10:00:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17588 for freebsd-current-outgoing; Wed, 23 Dec 1998 10:00:36 -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 KAA17582 for ; Wed, 23 Dec 1998 10:00:35 -0800 (PST) (envelope-from rcarter@pinyon.org) Received: (from pinyon@localhost) by vip.consys.com (8.9.1/8.9.1) id LAA25024 for freebsd-current@freebsd.org; Wed, 23 Dec 1998 11:00:28 -0700 (MST) Date: Wed, 23 Dec 1998 11:00:28 -0700 (MST) From: "Russell L. Carter" Message-Id: <199812231800.LAA25024@vip.consys.com> To: freebsd-current@FreeBSD.ORG Subject: elf buildworld succeeds, aout buildworld fails Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I am trying to get a circa August -current aout system converted to ELF. I've got an ELF system that buildworld/installworld yesterday's -current just fine. The exact same source tree fails on my aout system in nfs_prot.h. I've appended the end of the build. It doesn't matter if I do an aout-to-elf-build or just a plain buildworld. -DCLOBBER has no effect. My $PATH looks fine. make install in src/share/mk had no effect. What have I screwed up? Thanks, Russell $ make -DCLOBBER buildworld >& make.out & $ tail -110 make.out | more ===> librpcsvc rpcgen -C -c /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/klm_prot.x -o klm_prot_xdr.c cc -O -m486 -pipe -DYP -I/usr/obj/aout/usr/src/tmp/usr/include/rpcsvc -I/usr/obj/aout/usr/src/tmp/usr/include -I/usr/obj/aout/ usr/src/tmp/usr/include -c klm_prot_xdr.c -o klm_prot_xdr.o rpcgen -C -c /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/mount.x -o mount_xdr.c cc -O -m486 -pipe -DYP -I/usr/obj/aout/usr/src/tmp/usr/include/rpcsvc -I/usr/obj/aout/usr/src/tmp/usr/include -I/usr/obj/aout/ usr/src/tmp/usr/include -c mount_xdr.c -o mount_xdr.o rpcgen -C -c /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.x -o nfs_prot_xdr.c cc -O -m486 -pipe -DYP -I/usr/obj/aout/usr/src/tmp/usr/include/rpcsvc -I/usr/obj/aout/usr/src/tmp/usr/include -I/usr/obj/aout/ usr/src/tmp/usr/include -c nfs_prot_xdr.c -o nfs_prot_xdr.o In file included from nfs_prot_xdr.c:6: /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:265: parse error before `uint64' /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:265: warning: data definition has no type or storage class /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:267: parse error before `int64' /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:267: warning: data definition has no type or storage class /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:277: parse error before `fileid3' /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:277: warning: data definition has no type or storage class /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:279: parse error before `cookie3' [end] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 23 10:58:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA23880 for freebsd-current-outgoing; Wed, 23 Dec 1998 10:58:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from curly.globaleyes.net (mail.globaleyes.net [209.60.64.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA23865; Wed, 23 Dec 1998 10:58:38 -0800 (PST) (envelope-from ed@schoolnews.com) From: ed@schoolnews.com Received: from schoolnews.com ([131.230.134.231]) by curly.globaleyes.net (Netscape Messaging Server 3.5) with SMTP id 93; Wed, 23 Dec 1998 12:58:31 -0600 To: ed@schoolnews.com Subject: Happy Holidays Date: Wed, 23 Dec 1998 12:58:31 -0600 Message-ID: <19981223183847488.AEE201.93@schoolnews.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thought I would give you something to look at over the holiday break. -Ed Hardware: Dell http://www.dell.com Apple http://www.apple.com DNS http://www.dns.com Software: Microsoft http://www.microsoft.com School Center http://www.schoolcenter.com Mac software http://www.macsoftware.apple.com K12 Schools: http://rhs.rowland.k12.ca.us/ http://www.trico.jacksn.k12.il.us/ http://www.abiqua.pvt.k12.or.us/ http://www.willard.k12.mo.us http://www.colleton.k12.sc.us To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 23 11:15:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25979 for freebsd-current-outgoing; Wed, 23 Dec 1998 11:15:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25974 for ; Wed, 23 Dec 1998 11:15:15 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.57.82]) by smtp02.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA55E6; Wed, 23 Dec 1998 20:15:10 +0100 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: <86g1a7klvs.fsf@lion.plab.ku.dk> Date: Wed, 23 Dec 1998 20:21:37 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Anton Berezin Subject: Re: make build fails on fresh current Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23-Dec-98 Anton Berezin wrote: > Palle Girgensohn writes: >> In file included from nfs_prot_xdr.c:6: >> /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:265: parse >> error before `uint64' > > I've got _exactly_ the same results on my system yesterday. It looks > like generated nfs_prot.h did not include some relevant header so that > types like ulonglong_t were left undefined. > > Can a knowledgeable person on the list elaborate on this? Is it > something 2.2.7 -> 3.0 specific? Or something wrong with cvsuped tree > (December 22, Danish mirror)? (I am not the type doing cvsup and > buildworld every day, I simply thought that following this way will > make easier the upgrade of an existing system). Ye might want to make and make install lex and yacc by hand and then try make world again. This solved a problem for me during make world. And from the error results it looks similar... Always worth a try... Then again, I could be dead wrong... --- Jeroen Ruigrok van der Werven Life is the only Pain asmodai(at)wxs.nl we endeavour... Network/Security Specialist BSD & picoBSD: 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 Dec 23 11:19:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA26464 for freebsd-current-outgoing; Wed, 23 Dec 1998 11:19:13 -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 LAA26440 for ; Wed, 23 Dec 1998 11:19:02 -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 UAA11953; Wed, 23 Dec 1998 20:18:39 +0100 (MET) Received: (from son@localhost) by teaser.fr (8.9.1/8.9.1) id BAA01799; Tue, 22 Dec 1998 01:04:50 GMT (envelope-from son) Message-ID: <19981222010450.23781@breizh.prism.uvsq.fr> Date: Tue, 22 Dec 1998 01:04:50 +0000 From: Nicolas Souchu To: =?iso-8859-1?Q?Jos=E9_M=AA_Alcaide?= Cc: Stephen Palmer , gp@oitunix.oit.umass.edu, freebsd-current@FreeBSD.ORG Subject: Re: Request fo help with Zip Drive on vpo0 in -current] References: <19981219130349.11043.qmail@www0f.netaddress.usa.net> <367E88FB.B9F0D79@we.lc.ehu.es> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.81e In-Reply-To: =?iso-8859-1?Q?=3C367E88FB=2EB9F0D79=40we=2Elc=2Eehu=2Ees=3E=3B_from_Jos?= =?iso-8859-1?Q?=E9_M=AA_Alcaide_on_Mon=2C_Dec_21=2C_1998_at_06=3A44=3A27?= =?iso-8859-1?Q?PM_+0100?= 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 Mon, Dec 21, 1998 at 06:44:27PM +0100, José Mª Alcaide wrote: [...] > >I regret to say a "me, too", but this is the truth. We had a parallel >ZIP working under FreeBSD-current. This morning we "made the world" >and now it does not work. The parallel port and the ZIP drive are >found, but the "da" device is not initialized. What happened? > Exactly the same problem here. What was your last vpo-running -current udpate? -- 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 Wed Dec 23 11:50:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29494 for freebsd-current-outgoing; Wed, 23 Dec 1998 11:50:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles246.castles.com [208.214.165.246]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA29486 for ; Wed, 23 Dec 1998 11:50:15 -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 LAA03735; Wed, 23 Dec 1998 11:47:41 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812231947.LAA03735@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Steve Kargl cc: mike@smith.net.au (Mike Smith), freebsd-current@FreeBSD.ORG Subject: Re: Fortran conundrum In-reply-to: Your message of "Wed, 23 Dec 1998 08:06:06 PST." <199812231606.IAA17637@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 23 Dec 1998 11:47:40 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > According to Mike Smith: > > > (3) Rip Fortran out of the base distribution. > > > > > > This seem to be the logical choice (provided f2c can be converted > > > to a port). I have been merging our f2c and the sources from netlib > > > with the intend to produce a port. There is, however, one major > > > caveat that needs to be address. /usr/bin/f77 is a driver program > > > which sets up an execution of our Fortran-aware gcc frontend > > > (see src/gnu/usr.bin/cc/f77). I have been unsuccessful in moving this > > > driver out of src/gnu, and still retain its functionality. > > > > Can you clarify on the problems inherent in moving the f77 executable? > > > > f77.c contains #include "config.h", and I haven't located where this > header lives. It defines preprocessor directives like HAVE_VPRINTF, > but it may in fact contain other things that are less obvious to me. It's a one-line file generated at build time by cc_tools/Makefile: config.h hconfig.h tconfig.h: echo '#include "${MACHINE_ARCH}/xm-freebsd.h"' > ${.TARGET} which includes src/contrib/gcc/config//xm-freebsd.h, which in turn includes src/contrib/gcc/config//xm-.h and src/contrib/gcc/config/xm-freebsd.h, which defines: #define HAVE_PUTENV #define HAVE_STRERROR #define DONT_DECLARE_SYS_SIGLIST #define HOST_PTR_PRINTF "%p" > I'm still looking at what I can do with f77.c. I've submitted a > PR that removes quite a bit of dead code in f77.c. If you're continuing on your way to extracting it completely from the tree, the PR should be ignored for now, correct? -- \\ 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 Dec 23 12:01:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA00740 for freebsd-current-outgoing; Wed, 23 Dec 1998 12:01:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles246.castles.com [208.214.165.246]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA00728 for ; Wed, 23 Dec 1998 12:01:10 -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 LAA03858; Wed, 23 Dec 1998 11:58:32 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812231958.LAA03858@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Cory Kempf cc: freebsd-current@FreeBSD.ORG Subject: Re: Wingz3 Permission problem In-reply-to: Your message of "23 Dec 1998 08:53:41 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 23 Dec 1998 11:58:32 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > I just downloaded the Linux version of Wingz3. It runs, if I attempt to > run it as root, but not as a normal user. My guess is that there is some > sort of permittion problem somewhere, but I can't find it. > > Anyone know what it might be? Or have suggestions of how to locate it? What fails when you run it as non-root? You can use 'truss' to watch what it's doing; I'd recommend the '-o' option to stuff the truss output into a file (as long as Wingz is exiting normally). You can also use 'ktrace' and the 'linux_kdump' port; this has about the same functionality and an output format that some people prefer. -- \\ 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 Dec 23 12:04:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA00894 for freebsd-current-outgoing; Wed, 23 Dec 1998 12:02:35 -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 MAA00889 for ; Wed, 23 Dec 1998 12:02:34 -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 MAA71623; Wed, 23 Dec 1998 12:09:53 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199812232009.MAA71623@troutmask.apl.washington.edu> Subject: Re: Fortran conundrum In-Reply-To: <199812231947.LAA03735@dingo.cdrom.com> from Mike Smith at "Dec 23, 1998 11:47:40 am" To: mike@smith.net.au (Mike Smith) Date: Wed, 23 Dec 1998 12:09:53 -0800 (PST) Cc: mike@smith.net.au, 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 According to Mike Smith: >> According to Mike Smith: >>>> (3) Rip Fortran out of the base distribution. >>>> >>>> (see src/gnu/usr.bin/cc/f77). I have been unsuccessful in moving this >>>> driver out of src/gnu, and still retain its functionality. >>> >>> Can you clarify on the problems inherent in moving the f77 executable? >>> >> >> f77.c contains #include "config.h", and I haven't located where this >> header lives. It defines preprocessor directives like HAVE_VPRINTF, >> but it may in fact contain other things that are less obvious to me. > > It's a one-line file generated at build time by cc_tools/Makefile: > > config.h hconfig.h tconfig.h: > echo '#include "${MACHINE_ARCH}/xm-freebsd.h"' > ${.TARGET} > Thanks for trip through include land ;-) > > I'm still looking at what I can do with f77.c. I've submitted a > > PR that removes quite a bit of dead code in f77.c. > > If you're continuing on your way to extracting it completely from the > tree, the PR should be ignored for now, correct? > Well, it's dead code (about 3.5KB). I'm not sure I will have f77, f2c, and libf2c removed by the 3.0.1 freeze because I need to re-learn how to do a port. However, I have a few days off over Xmas. It certainly isn't a critical fix, so you can opt to close the PR by noting a better solution is in the works. -- 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 Wed Dec 23 13:29:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10525 for freebsd-current-outgoing; Wed, 23 Dec 1998 13:29:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from poboxer.pobox.com (port34.prairietech.net [208.141.230.111]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA10519 for ; Wed, 23 Dec 1998 13:28:57 -0800 (PST) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.1/8.9.1) id PAA06269; Wed, 23 Dec 1998 15:28:41 -0600 (CST) (envelope-from alk) From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 23 Dec 1998 15:28:41 -0600 (CST) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: current@FreeBSD.ORG Subject: un-hexdump? X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13952.37524.42627.187779@avalon.east> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For stream-editing binaries in shell scripts, I find it useful to have a utility to invert hexdump (produce a binary from hexdump output). This seems to be a missing element in the toolkit which is the base OS. If I am not mistaken on this point, and it is deemed desirable, I will provide a basic utility of this sort. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 23 13:56:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA12948 for freebsd-current-outgoing; Wed, 23 Dec 1998 13:56:06 -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 NAA12942 for ; Wed, 23 Dec 1998 13:56:04 -0800 (PST) (envelope-from rcarter@pinyon.org) Received: (from pinyon@localhost) by vip.consys.com (8.9.1/8.9.1) id OAA25477; Wed, 23 Dec 1998 14:55:55 -0700 (MST) Date: Wed, 23 Dec 1998 14:55:55 -0700 (MST) From: "Russell L. Carter" Message-Id: <199812232155.OAA25477@vip.consys.com> To: asmodai@wxs.nl, tobez@plab.ku.dk Subject: Re: make build fails on fresh current Cc: freebsd-current@FreeBSD.ORG In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG |On 23-Dec-98 Anton Berezin wrote: |> Palle Girgensohn writes: |>> In file included from nfs_prot_xdr.c:6: |>> /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:265: parse |>> error before `uint64' |> |> I've got _exactly_ the same results on my system yesterday. It looks |> like generated nfs_prot.h did not include some relevant header so that |> types like ulonglong_t were left undefined. |> |> Can a knowledgeable person on the list elaborate on this? Is it |> something 2.2.7 -> 3.0 specific? Or something wrong with cvsuped tree |> (December 22, Danish mirror)? (I am not the type doing cvsup and |> buildworld every day, I simply thought that following this way will |> make easier the upgrade of an existing system). | |Ye might want to make and make install lex and yacc by hand and then try make |world again. This solved a problem for me during make world. And from the error |results it looks similar... Always worth a try... | |Then again, I could be dead wrong... Not this time. Your suggestion appears to have worked for me (at least I'm further along at this minute). Thanks! Russell | |--- |Jeroen Ruigrok van der Werven Life is the only Pain |asmodai(at)wxs.nl we endeavour... |Network/Security Specialist |BSD & picoBSD: The Power to Serve | |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 Dec 23 14:43:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17544 for freebsd-current-outgoing; Wed, 23 Dec 1998 14:43:32 -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 OAA17538 for ; Wed, 23 Dec 1998 14:43:29 -0800 (PST) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (lxpxcy.lx.ehu.es [158.227.99.176]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id XAA23856; Wed, 23 Dec 1998 23:43:12 +0100 (MET) Message-ID: <368171FF.B8A5B268@we.lc.ehu.es> Date: Wed, 23 Dec 1998 23:43:11 +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: Nicolas Souchu CC: Stephen Palmer , gp@oitunix.oit.umass.edu, freebsd-current@FreeBSD.ORG Subject: Re: Request fo help with Zip Drive on vpo0 in -current] References: <19981219130349.11043.qmail@www0f.netaddress.usa.net> <367E88FB.B9F0D79@we.lc.ehu.es> <19981222010450.23781@breizh.prism.uvsq.fr> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nicolas Souchu wrote: > > Exactly the same problem here. What was your last vpo-running -current > udpate? > I don't remember exactly... I think that it was FreeBSD-current as of November, 15th o 16th. I submitted a PR (kern/9174). -- 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 Wed Dec 23 15:32:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA22702 for freebsd-current-outgoing; Wed, 23 Dec 1998 15:32:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA22686; Wed, 23 Dec 1998 15:32:42 -0800 (PST) (envelope-from jmb) Date: Wed, 23 Dec 1998 15:32:42 -0800 (PST) Message-Id: <199812232332.PAA22686@hub.freebsd.org> From: "Jonathan M. Bresler" To: starr3@gccs.com.au CC: freebsd-current@FreeBSD.ORG In-reply-to: <001501be2da8$fb35b830$0a9811cb@gccs.com.au> (starr3@gccs.com.au) Subject: Re: Problems with CAM and ncr References: <001501be2da8$fb35b830$0a9811cb@gccs.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > From: "Harry Starr" > Date: Tue, 22 Dec 1998 22:45:38 +1000 > There seems to be a major problem with the new CAM code and the ncr driver. > > Config: > > Asus SC200 (ncr810) in Asus P2L97 M/B with PII-300 and 128MB mem. just finished a buildworld using Asus SC200 (ncr810) installed on a Asus SP3G motherboard and Am5x86-133MHz, 40MB, and SEAGATE ST15150N 0024 disk. no scsi problems. FreeBSD Aspen.USi.NET 3.0-CURRENT FreeBSD 3.0-CURRENT #14: Sat Dec 12 18:53:35 EST 1998 jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 23 17:33:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA07949 for freebsd-current-outgoing; Wed, 23 Dec 1998 17:33:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA07944 for ; Wed, 23 Dec 1998 17:32:59 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id CAA18310; Thu, 24 Dec 1998 02:32:52 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id CAA36824; Thu, 24 Dec 1998 02:32:51 +0100 (MET) Message-ID: <19981224023250.E30095@follo.net> Date: Thu, 24 Dec 1998 02:32:50 +0100 From: Eivind Eklund To: "Russell L. Carter" , freebsd-current@FreeBSD.ORG Subject: Re: elf buildworld succeeds, aout buildworld fails References: <199812231800.LAA25024@vip.consys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812231800.LAA25024@vip.consys.com>; from Russell L. Carter on Wed, Dec 23, 1998 at 11:00:28AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 23, 1998 at 11:00:28AM -0700, Russell L. Carter wrote: > > Hi, > I am trying to get a circa August -current aout system converted > to ELF. I've got an ELF system that buildworld/installworld yesterday's > -current just fine. The exact same source tree fails on my aout > system in nfs_prot.h. I've appended the end of the build. > It doesn't matter if I do an aout-to-elf-build or > just a plain buildworld. -DCLOBBER has no effect. My $PATH > looks fine. make install in src/share/mk had no effect. > What have I screwed up? Nothing. Someobyd has screwed up the build. I'm trying to trace down how and why right now; it is blowing away builds I need to be able to test my 'christmas gift' :-( Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 23 17:43:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08909 for freebsd-current-outgoing; Wed, 23 Dec 1998 17:43:33 -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 RAA08902 for ; Wed, 23 Dec 1998 17:43:30 -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 RAA04152; Wed, 23 Dec 1998 17:43:24 -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 RAA00401; Wed, 23 Dec 1998 17:43:23 -0800 (PST) (envelope-from jdp@polstra.com) Date: Wed, 23 Dec 1998 17:43:23 -0800 (PST) Message-Id: <199812240143.RAA00401@vashon.polstra.com> To: eivind@yes.no Subject: Re: elf buildworld succeeds, aout buildworld fails Newsgroups: polstra.freebsd.current In-Reply-To: <19981224023250.E30095@follo.net> References: <199812231800.LAA25024@vip.consys.com> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19981224023250.E30095@follo.net>, Eivind Eklund wrote: > On Wed, Dec 23, 1998 at 11:00:28AM -0700, Russell L. Carter wrote: > > > > Hi, > > I am trying to get a circa August -current aout system converted > > to ELF. I've got an ELF system that buildworld/installworld yesterday's > > -current just fine. The exact same source tree fails on my aout > > system in nfs_prot.h. I've appended the end of the build. > > It doesn't matter if I do an aout-to-elf-build or > > just a plain buildworld. -DCLOBBER has no effect. My $PATH > > looks fine. make install in src/share/mk had no effect. > > What have I screwed up? > > Nothing. Someobyd has screwed up the build. I'm trying to trace down > how and why right now; it is blowing away builds I need to be able to > test my 'christmas gift' :-( Strange. I updated my sources around 7:30 PST this morning, and was able to do a successful make {build,install}world (a.out). My system was running a.out -current from November 11. So the problem doesn't affect everybody. 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 Dec 23 18:26:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA13126 for freebsd-current-outgoing; Wed, 23 Dec 1998 18:26:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vanessa.eliuk.org (pme50.sunshine.net [209.17.178.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA13119 for ; Wed, 23 Dec 1998 18:26:21 -0800 (PST) (envelope-from kevin_eliuk@sunshine.net) Received: from localhost (cagey@localhost) by vanessa.eliuk.org (8.9.1/8.8.8) with SMTP id SAA00688 for ; Wed, 23 Dec 1998 18:26:22 -0800 (PST) (envelope-from cagey@vanessa.eliuk.org) Date: Wed, 23 Dec 1998 18:25:51 -0800 (PST) From: "Kevin G. Eliuk" Reply-To: "Kevin G. Eliuk" To: FreeBSD Current Subject: Once more - ACER ALI and second device 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 a build as of Dec 21 and after trying a number of different kernels and swapping positions I was only able to get the cdrom(4X ATAPI) to be recognized as a slave to the 8.4GB maxtor. ____ 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-CURRENT #0: Wed Dec 23 02:19:48 PST 1998 root@vanessa.eliuk.org:/usr/src/sys/compile/CATHERNA Timecounter "i8254" frequency 1193286 Hz Timecounter "TSC" frequency 99878456 Hz CPU: Pentium/P54C (99.88-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x526 Stepping=6 Features=0x1bf real memory = 33554432 (32768K bytes) avail memory = 30121984 (29416K bytes) Bad DMI table checksum! Probing for devices on PCI bus 0: chip0: rev 0xb3 on pci0.0.0 chip1: rev 0xb4 on pci0.2.0 vga0: rev 0x06 int a irq 0 on pci0.6.0 ide_pci0: rev 0x20 int a irq 0 on pci0.11.0 ide_pci: controller is simplex, no DMA on secondary channel Probing for PnP devices: CSN 1 Vendor ID: YMH0800 [0x0008a865] Serial 0xffffffff Comp ID: PNPb02f [0x2fb0d041] Probing for devices on the ISA bus: VESA: v1.2, 4096k memory, flags:0x0, mode table:0xf00c4ab5 (c0004ab5) VESA: S3 Incorporated. 86C325 sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio3 at 0x2e8-0x2ef irq 3 on isa sio3: tYpe 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface ... try to identify the yamaha pcm0 at 0x530 irq 5 drq 0 flags 0xc113 on isa mss_attach 0 at 0x530 irq 5 dma 0:3 flags 0xc113 setting up yamaha registers set yamaha master volume to max 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 flags 0xa0ff on isa ide_pci: generic_dmainit 01f0:0: warning, IDE controller timing not set wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 wd0: 8010MB (16406208 sectors), 16276 cyls, 16 heads, 63 S/T, 512 B/S wdc1 not found at 0x170 npx0 flags 0x1 on motherboard npx0: INT 16 interface Intel Pentium detected, installing workaround for F00F bug changing root device to wd0s2a wd0: reverting to PIO mode reading fsbn 0 (status 51 error 84) Currently: Primary Master: Maxtor 90840D6 No Slave Secondary Master: Maxtor 71084AP Secondary Slave: Torisan CDR-S1G 4X MB PCChips M560 Any suggestions to have my 1GB maxtor IDE to be recognized on the secondary? -- 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 Wed Dec 23 19:33:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA19061 for freebsd-current-outgoing; Wed, 23 Dec 1998 19:33:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Chuska.ConSys.COM (Chuska.ConSys.COM [209.141.107.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA19056 for ; Wed, 23 Dec 1998 19:33:24 -0800 (PST) (envelope-from rcarter@psf.Pinyon.ORG) Received: from psf.Pinyon.ORG (ip-17-088.prc.primenet.com [207.218.17.88]) by Chuska.ConSys.COM (8.9.1/8.9.1) with ESMTP id UAA19236; Wed, 23 Dec 1998 20:33:13 -0700 (MST) Received: from psf.Pinyon.ORG (localhost [127.0.0.1]) by psf.Pinyon.ORG (8.9.1/8.8.7) with ESMTP id UAA09151; Wed, 23 Dec 1998 20:30:22 -0700 (MST) Message-Id: <199812240330.UAA09151@psf.Pinyon.ORG> X-Mailer: exmh version 2.0.2 2/24/98 To: jesse@prinz-atm.CS.Uni-Magdeburg.De, current@FreeBSD.ORG cc: rcarter@pinyon.org Subject: Re: ACE 4.6 on -current (still) In-reply-to: Your message of "Wed, 23 Dec 1998 13:19:08 MST." <199812232019.NAA25305@vip.consys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 23 Dec 1998 20:30:22 -0700 From: "Russell L. Carter" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > | > |Russell, > | > |> ELF ACE 4.6 works fine (passes all the tests, including netscvs) > |> with the stock cc and egcs 1.1.1 too (modulo a couple of nits). > | > |Hhm, it does not for me as you can see in > |http://www.apfel.de/~jesse/gmake.ACE.out. > > This output doesn't look anything at all like mine. > > | > |Would you mind sharing your files? I would appreciate it. > > You bet. I'll post a pointer to these tonight. Wow. Reversing the path shows how much we need the POSIX sched stuff. These will get you started. I have a weird fix for the TAO idl compiler when somebody else gets that far (gperf enabled). Try: http://www.Pinyon.ORG/ace/config-freebsd3.h and http://www.Pinyon.ORG/ace/platform_freebsd3.GNU These are verified for ACE today, FreeBSD-current yesterday. Russell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 23 19:45:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA00581 for freebsd-current-outgoing; Wed, 23 Dec 1998 19:45:26 -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 TAA00567 for ; Wed, 23 Dec 1998 19:45:15 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:N/l5Fw+tVpSjuOAh59uodE1q6NlIHjV1@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 MAA14902; Thu, 24 Dec 1998 12:42:20 +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 MAA22380; Thu, 24 Dec 1998 12:44:27 +0900 (JST) Message-Id: <199812240344.MAA22380@zodiac.mech.utsunomiya-u.ac.jp> To: mike@smith.net.au, des@flood.ping.uio.no cc: current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: future of syscons In-reply-to: Your message of "Tue, 22 Dec 1998 15:56:18 PST." <199812222356.PAA01687@dingo.cdrom.com> References: <199812222356.PAA01687@dingo.cdrom.com> Date: Thu, 24 Dec 1998 12:44:26 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG des>> The kernel configuration file should look: des>> des>> controller kbdc0 at isa? port IO_KBD tty des>> device atkbd0 at isa? tty flags xxxx des>> device psm0 at isa? tty flags yyy des> des>Shouldn't it be: des> des>device atkbd0 at kbdc0 flags xxxx des>device psm0 at kbdc0 flags yyyy msmith>> controller kbdc0 at isa? port IO_KBD tty msmith>> device atkbd0 at isa? tty flags xxxx msmith>> device psm0 at isa? tty flags yyy msmith> msmith>Just to note that ultimately you won't specify the 'tty' mask here, but msmith>rather in the interrupt connection function, so: msmith> msmith>controller atkbdc0 at isa? port IO_KBD msmith>device atkbd0 at kbdc? msmith>device psm0 at kbdc? That's exactly what I want to do! What I proposed was merely an interim, compromise measure. Because of the current config(8) and the ISA bus code in i386, we cannot write flags like the following. device psm0 at kbdc? flags yyy (In alpha, this shouldn't be a problem, should it?) msmith>Also, since the atkbd and psm device interrupt handlers can only be msmith>called from the atkbdc driver, they don't register interrupts and thus msmith>don't have/need masks. There is a compromise here too. In i386, if atkbdc wants to have TWO interrupt handlers, it has to call register_intr() directly (and make sure that there won't be conflicts), rather than letting isa_configure() to do the deed, because isa_configure() can assign only one interrupt to a device. Am I wrong? I expect this can be solved once resource management code is fully utilized in i386. But, this is not yet happening. For the time being, psm and atkbd have to register their own interrupt handlers independently and share keyboard controller I/O routines in atkbdc, (just as syscons and psm have been doing until now via routines in kbdio). Again, alpha should be able to do it better, right? msmith>> device sc0 at isa? tty flags zzz msmith> msmith>What's this? Don't you mean: msmith> msmith>pseudo-device syscons 1 I thought I will do it like this first. But, again, I realized that we currently don't have a means to pass flags to the pseudo-device. The current syscons code still uses some flags bits. Once we eliminate these, we can declare it as a pseudo device. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 23 19:55:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA01330 for freebsd-current-outgoing; Wed, 23 Dec 1998 19:55:52 -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 TAA01325 for ; Wed, 23 Dec 1998 19:55:51 -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 TAA00736; Wed, 23 Dec 1998 19:51:15 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812240351.TAA00736@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Kazutaka YOKOTA cc: mike@smith.net.au, des@flood.ping.uio.no, current@FreeBSD.ORG Subject: Re: future of syscons In-reply-to: Your message of "Thu, 24 Dec 1998 12:44:26 +0900." <199812240344.MAA22380@zodiac.mech.utsunomiya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 23 Dec 1998 19:51:15 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > msmith>> controller kbdc0 at isa? port IO_KBD tty > msmith>> device atkbd0 at isa? tty flags xxxx > msmith>> device psm0 at isa? tty flags yyy > msmith> > msmith>Just to note that ultimately you won't specify the 'tty' mask here, but > msmith>rather in the interrupt connection function, so: > msmith> > msmith>controller atkbdc0 at isa? port IO_KBD > msmith>device atkbd0 at kbdc? > msmith>device psm0 at kbdc? ... > msmith>Also, since the atkbd and psm device interrupt handlers can only be > msmith>called from the atkbdc driver, they don't register interrupts and thus > msmith>don't have/need masks. > > There is a compromise here too. In i386, if atkbdc wants to have TWO > interrupt handlers, it has to call register_intr() directly (and make > sure that there won't be conflicts), rather than letting > isa_configure() to do the deed, because isa_configure() can assign > only one interrupt to a device. Am I wrong? No, you're right. But there's nothing stopping you have atkbdc do that right now; it should never take an interrupt from it's configuration - if it detects a kbdc, it should always take both implicitly. -- \\ 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 Dec 23 20:56:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA07376 for freebsd-current-outgoing; Wed, 23 Dec 1998 20:56:01 -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 UAA07338 for ; Wed, 23 Dec 1998 20:55:59 -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 XAA29514 for ; Wed, 23 Dec 1998 23:55:54 -0500 (EST) Date: Wed, 23 Dec 1998 23:55:54 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: current@FreeBSD.ORG Subject: K6-2 (3?) CPU_WT_ALLOC 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 CPU_WT_ALLOC does not work correctly for K6-2s of model 8+ and probably K6-3s when they appear on the market soon. In addition, print_AMD_info() incorrectly printfs write allocation's size. I've fixed them, so they now Do The Right Thing, and added a "NO_MEMORY_HOLE" option to easily allow 15-16mb range handling for us K6 and K6-2 users. A patch follows in cleartext and encoded forms. Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ --- src/sys/i386/conf/options.i386.orig Wed Dec 23 20:36:45 1998 +++ src/sys/i386/conf/options.i386 Wed Dec 23 20:36:56 1998 @@ -57,6 +57,7 @@ CPU_WT_ALLOC opt_cpu.h CYRIX_CACHE_WORKS opt_cpu.h CYRIX_CACHE_REALLY_WORKS opt_cpu.h +NO_MEMORY_HOLE opt_cpu.h # The CPU type affects the endian conversion functions all over the kernel. I386_CPU opt_global.h --- src/sys/i386/i386/identcpu.c.orig Mon Dec 21 23:12:18 1998 +++ src/sys/i386/i386/identcpu.c Wed Dec 23 20:30:39 1998 @@ -68,6 +68,7 @@ #if defined(I586_CPU) && defined(CPU_WT_ALLOC) void enable_K5_wt_alloc(void); void enable_K6_wt_alloc(void); +void enable_K6_2_wt_alloc(void); #endif void panicifcpuunsupported(void); static void identifycyrix(void); @@ -291,9 +292,11 @@ if ((cpu_id & 0xf00) == 0x500) { if (((cpu_id & 0x0f0) > 0) && ((cpu_id & 0x0f0) < 0x60) - && ((cpu_id & 0x00f) > 3)) { + && ((cpu_id & 0x00f) > 3)) enable_K5_wt_alloc(); - } else if ((cpu_id & 0x0f0) > 0x50) + else if ((cpu_id & 0x0f0) > 0x70) + enable_K6_2_wt_alloc(); + else if ((cpu_id & 0x0f0) > 0x50) enable_K6_wt_alloc(); } #endif @@ -860,18 +863,28 @@ switch (cpu_id & 0xFF0) { case 0x560: /* K6 0.35u */ case 0x570: /* K6 0.25u */ - case 0x580: /* K6-2 */ - case 0x590: /* K6-3 */ amd_whcr = rdmsr(0xc0000082); if (!(amd_whcr & 0x00fe)) { printf("Write Allocate Disable\n"); } else { printf("Write Allocate Enable Limit: %dM bytes\n", - (u_int32_t)(amd_whcr & 0x00fe) * 2); + (u_int32_t)(amd_whcr & 0x00fe) * 4); printf("Write Allocate 15-16M bytes: %s\n", (amd_whcr & 0x0001) ? "Enable" : "Disable"); printf("Hardware Write Allocate Control: %s\n", (amd_whcr & 0x0100) ? "Enable" : "Disable"); + } + break; + case 0x580: /* K6-2 */ + case 0x590: /* K6-3 */ + amd_whcr = rdmsr(0xc0000082); + if (!(amd_whcr & (0x3ff << 22))) { + printf("Write Allocate Disable\n"); + } else { + printf("Write Allocate Enable Limit: %dM bytes\n", + (u_int32_t)((amd_whcr & (0x3ff << 22)) >> 22) * 4); + printf("Write Allocate 15-16M bytes: %s\n", + (amd_whcr & (1 << 16)) ? "Enable" : "Disable"); } break; } --- src/sys/i386/i386/initcpu.c.orig Mon Dec 21 23:01:26 1998 +++ src/sys/i386/i386/initcpu.c Wed Dec 23 19:53:10 1998 @@ -44,6 +44,7 @@ #if defined(I586_CPU) && defined(CPU_WT_ALLOC) void enable_K5_wt_alloc(void); void enable_K6_wt_alloc(void); +void enable_K6_2_wt_alloc(void); #endif #ifdef I486_CPU @@ -628,8 +629,9 @@ whcr &= ~0x00feLL; whcr |= (size << 1); -#ifdef PC98 +#if defined(PC98) || defined(NO_MEMORY_HOLE) if (whcr & 0x00feLL) { +#ifdef PC98 /* * If bit 2 of port 0x43b is 0, disable wrte allocate for the * 15-16M range. @@ -637,6 +639,7 @@ if (!(inb(0x43b) & 4)) whcr &= ~0x0001LL; else +#endif whcr |= 0x0001LL; } #else @@ -644,7 +647,68 @@ * There is no way to know wheter 15-16M hole exists or not. * Therefore, we disable write allocate for this range. */ - whcr &= 0x00feLL; + whcr &= ~0x0001LL; +#endif + wrmsr(0x0c0000082, whcr); + + write_eflags(eflags); + enable_intr(); +} + +void +enable_K6_2_wt_alloc(void) +{ + quad_t size; + u_int64_t whcr; + u_long eflags; + + eflags = read_eflags(); + disable_intr(); + wbinvd(); + +#ifdef CPU_DISABLE_CACHE + /* + * Certain K6-2 box becomes unstable when write allocation is + * enabled. + */ + /* + * The AMD-K6 processer provides the 64-bit Test Register 12(TR12), + * but only the Cache Inhibit(CI) (bit 3 of TR12) is suppported. + * All other bits in TR12 have no effect on the processer's operation. + * The I/O Trap Restart function (bit 9 of TR12) is always enabled + * on the AMD-K6. + */ + wrmsr(0x0000000e, (u_int64_t)0x0008); +#endif + /* Don't assume that memory size is aligned with 4M. */ + if (Maxmem > 0) + size = ((Maxmem >> 8) + 3) >> 2; + else + size = 0; + + /* Limit is 4092M bytes. */ + size &= 0x3ff; + whcr = (rdmsr(0xc0000082) & ~(0x3ffLL << 22)) | (size << 22); + +#if defined(PC98) || defined(NO_MEMORY_HOLE) + if (whcr & (0x3ffLL << 22)) { +#ifdef PC98 + /* + * If bit 2 of port 0x43b is 0, disable wrte allocate for the + * 15-16M range. + */ + if (!(inb(0x43b) & 4)) + whcr &= ~(1LL << 16); + else +#endif + whcr |= 1LL << 16; + } +#else + /* + * There is no way to know wheter 15-16M hole exists or not. + * Therefore, we disable write allocate for this range. + */ + whcr &= ~(1LL << 16); #endif wrmsr(0x0c0000082, whcr); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 23 21:18:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA10053 for freebsd-current-outgoing; Wed, 23 Dec 1998 21:18:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA10045 for ; Wed, 23 Dec 1998 21:18:38 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id AAA04459; Thu, 24 Dec 1998 00:18:10 -0500 (EST) Date: Thu, 24 Dec 1998 00:18:10 -0500 (EST) From: Daniel Eischen Message-Id: <199812240518.AAA04459@pcnet1.pcnet.com> To: current@FreeBSD.ORG, jesse@prinz-atm.CS.Uni-Magdeburg.De, rcarter@pinyon.org Subject: Re: ACE 4.6 on -current (still) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Russell L. Carter wrote: > > |Russell, > > | > > |> ELF ACE 4.6 works fine (passes all the tests, including netscvs) > > |> with the stock cc and egcs 1.1.1 too (modulo a couple of nits). > > | > > |Hhm, it does not for me as you can see in > > |http://www.apfel.de/~jesse/gmake.ACE.out. > > > > This output doesn't look anything at all like mine. > > > > | > > |Would you mind sharing your files? I would appreciate it. > > > > You bet. I'll post a pointer to these tonight. > > Wow. Reversing the path shows how much we need the POSIX > sched stuff. These will get you started. I have a weird > fix for the TAO idl compiler when somebody else gets that > far (gperf enabled). > > Try: > > http://www.Pinyon.ORG/ace/config-freebsd3.h > > and > > http://www.Pinyon.ORG/ace/platform_freebsd3.GNU > > These are verified for ACE today, FreeBSD-current yesterday. I'm working on the libc_r scheduling stuff, if anyone cares. It includes all functions needed to allow defining _POSIX_THREAD_PRIORITY_SCHEDULING (pthread_getschedparam, pthread_setschedparam, etc), and also includes priority protection and inheritence mutexes. I just started writing some simple tests to verify the mutex implementation, but I'd like to eventually try out the ACE tests also. I'm not ready to release the changes yet, but contact me offline if you want, and I'll send you them when I'm done. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 23 21:23:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA10776 for freebsd-current-outgoing; Wed, 23 Dec 1998 21:23:45 -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 VAA10764 for ; Wed, 23 Dec 1998 21:23:38 -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 AAA00505 for ; Thu, 24 Dec 1998 00:23:34 -0500 (EST) Date: Thu, 24 Dec 1998 00:23:34 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: current@FreeBSD.ORG Subject: Re: K6-2 (3?) CPU_WT_ALLOC In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1280433323-914477014=:29349" 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-1280433323-914477014=:29349 Content-Type: TEXT/PLAIN; charset=US-ASCII Correction: I forget to include the encoded form before sending the message! *THWAP* People need something easy to save. Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ --0-1280433323-914477014=:29349 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="K6-2.patch" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="K6-2.patch" LS0tIHNyYy9zeXMvaTM4Ni9jb25mL29wdGlvbnMuaTM4Ni5vcmlnCVdlZCBE ZWMgMjMgMjA6MzY6NDUgMTk5OA0KKysrIHNyYy9zeXMvaTM4Ni9jb25mL29w dGlvbnMuaTM4NglXZWQgRGVjIDIzIDIwOjM2OjU2IDE5OTgNCkBAIC01Nyw2 ICs1Nyw3IEBADQogQ1BVX1dUX0FMTE9DCQkJb3B0X2NwdS5oDQogQ1lSSVhf Q0FDSEVfV09SS1MJCW9wdF9jcHUuaA0KIENZUklYX0NBQ0hFX1JFQUxMWV9X T1JLUwlvcHRfY3B1LmgNCitOT19NRU1PUllfSE9MRQkJCW9wdF9jcHUuaA0K IA0KICMgVGhlIENQVSB0eXBlIGFmZmVjdHMgdGhlIGVuZGlhbiBjb252ZXJz aW9uIGZ1bmN0aW9ucyBhbGwgb3ZlciB0aGUga2VybmVsLg0KIEkzODZfQ1BV CQlvcHRfZ2xvYmFsLmgNCi0tLSBzcmMvc3lzL2kzODYvaTM4Ni9pZGVudGNw dS5jLm9yaWcJTW9uIERlYyAyMSAyMzoxMjoxOCAxOTk4DQorKysgc3JjL3N5 cy9pMzg2L2kzODYvaWRlbnRjcHUuYwlXZWQgRGVjIDIzIDIwOjMwOjM5IDE5 OTgNCkBAIC02OCw2ICs2OCw3IEBADQogI2lmIGRlZmluZWQoSTU4Nl9DUFUp ICYmIGRlZmluZWQoQ1BVX1dUX0FMTE9DKQ0KIHZvaWQJZW5hYmxlX0s1X3d0 X2FsbG9jKHZvaWQpOw0KIHZvaWQJZW5hYmxlX0s2X3d0X2FsbG9jKHZvaWQp Ow0KK3ZvaWQJZW5hYmxlX0s2XzJfd3RfYWxsb2Modm9pZCk7DQogI2VuZGlm DQogdm9pZCBwYW5pY2lmY3B1dW5zdXBwb3J0ZWQodm9pZCk7DQogc3RhdGlj IHZvaWQgaWRlbnRpZnljeXJpeCh2b2lkKTsNCkBAIC0yOTEsOSArMjkyLDEx IEBADQogCQlpZiAoKGNwdV9pZCAmIDB4ZjAwKSA9PSAweDUwMCkgew0KIAkJ CWlmICgoKGNwdV9pZCAmIDB4MGYwKSA+IDApDQogCQkJICAgICYmICgoY3B1 X2lkICYgMHgwZjApIDwgMHg2MCkNCi0JCQkgICAgJiYgKChjcHVfaWQgJiAw eDAwZikgPiAzKSkgew0KKwkJCSAgICAmJiAoKGNwdV9pZCAmIDB4MDBmKSA+ IDMpKQ0KIAkJCQllbmFibGVfSzVfd3RfYWxsb2MoKTsNCi0JCQl9IGVsc2Ug aWYgKChjcHVfaWQgJiAweDBmMCkgPiAweDUwKQ0KKwkJCWVsc2UgaWYgKChj cHVfaWQgJiAweDBmMCkgPiAweDcwKQ0KKwkJCQllbmFibGVfSzZfMl93dF9h bGxvYygpOw0KKwkJCWVsc2UgaWYgKChjcHVfaWQgJiAweDBmMCkgPiAweDUw KQ0KIAkJCQllbmFibGVfSzZfd3RfYWxsb2MoKTsNCiAJCX0NCiAjZW5kaWYN CkBAIC04NjAsMTggKzg2MywyOCBAQA0KIAlzd2l0Y2ggKGNwdV9pZCAmIDB4 RkYwKSB7DQogCWNhc2UgMHg1NjA6CS8qIEs2IDAuMzV1ICovDQogCWNhc2Ug MHg1NzA6CS8qIEs2IDAuMjV1ICovDQotCWNhc2UgMHg1ODA6CS8qIEs2LTIg Ki8NCi0JY2FzZSAweDU5MDoJLyogSzYtMyAqLw0KIAkJYW1kX3doY3IgPSBy ZG1zcigweGMwMDAwMDgyKTsNCiAJCWlmICghKGFtZF93aGNyICYgMHgwMGZl KSkgew0KIAkJCXByaW50ZigiV3JpdGUgQWxsb2NhdGUgRGlzYWJsZVxuIik7 DQogCQl9IGVsc2Ugew0KIAkJCXByaW50ZigiV3JpdGUgQWxsb2NhdGUgRW5h YmxlIExpbWl0OiAlZE0gYnl0ZXNcbiIsDQotCQkJICAgICh1X2ludDMyX3Qp KGFtZF93aGNyICYgMHgwMGZlKSAqIDIpOw0KKwkJCSAgICAodV9pbnQzMl90 KShhbWRfd2hjciAmIDB4MDBmZSkgKiA0KTsNCiAJCQlwcmludGYoIldyaXRl IEFsbG9jYXRlIDE1LTE2TSBieXRlczogJXNcbiIsDQogCQkJICAgIChhbWRf d2hjciAmIDB4MDAwMSkgPyAiRW5hYmxlIiA6ICJEaXNhYmxlIik7DQogCQkJ cHJpbnRmKCJIYXJkd2FyZSBXcml0ZSBBbGxvY2F0ZSBDb250cm9sOiAlc1xu IiwNCiAJCQkgICAgKGFtZF93aGNyICYgMHgwMTAwKSA/ICJFbmFibGUiIDog IkRpc2FibGUiKTsNCisJCX0NCisJCWJyZWFrOw0KKwljYXNlIDB4NTgwOgkv KiBLNi0yICovDQorCWNhc2UgMHg1OTA6CS8qIEs2LTMgKi8NCisJCWFtZF93 aGNyID0gcmRtc3IoMHhjMDAwMDA4Mik7DQorCQlpZiAoIShhbWRfd2hjciAm ICgweDNmZiA8PCAyMikpKSB7DQorCQkJcHJpbnRmKCJXcml0ZSBBbGxvY2F0 ZSBEaXNhYmxlXG4iKTsNCisJCX0gZWxzZSB7DQorCQkJcHJpbnRmKCJXcml0 ZSBBbGxvY2F0ZSBFbmFibGUgTGltaXQ6ICVkTSBieXRlc1xuIiwNCisJCQkg ICAgKHVfaW50MzJfdCkoKGFtZF93aGNyICYgKDB4M2ZmIDw8IDIyKSkgPj4g MjIpICogNCk7DQorCQkJcHJpbnRmKCJXcml0ZSBBbGxvY2F0ZSAxNS0xNk0g Ynl0ZXM6ICVzXG4iLA0KKwkJCSAgICAoYW1kX3doY3IgJiAoMSA8PCAxNikp ID8gIkVuYWJsZSIgOiAiRGlzYWJsZSIpOw0KIAkJfQ0KIAkJYnJlYWs7DQog CX0NCi0tLSBzcmMvc3lzL2kzODYvaTM4Ni9pbml0Y3B1LmMub3JpZwlNb24g RGVjIDIxIDIzOjAxOjI2IDE5OTgNCisrKyBzcmMvc3lzL2kzODYvaTM4Ni9p bml0Y3B1LmMJV2VkIERlYyAyMyAxOTo1MzoxMCAxOTk4DQpAQCAtNDQsNiAr NDQsNyBAQA0KICNpZiBkZWZpbmVkKEk1ODZfQ1BVKSAmJiBkZWZpbmVkKENQ VV9XVF9BTExPQykNCiB2b2lkCWVuYWJsZV9LNV93dF9hbGxvYyh2b2lkKTsN CiB2b2lkCWVuYWJsZV9LNl93dF9hbGxvYyh2b2lkKTsNCit2b2lkCWVuYWJs ZV9LNl8yX3d0X2FsbG9jKHZvaWQpOw0KICNlbmRpZg0KIA0KICNpZmRlZiBJ NDg2X0NQVQ0KQEAgLTYyOCw4ICs2MjksOSBAQA0KIAl3aGNyICY9IH4weDAw ZmVMTDsNCiAJd2hjciB8PSAoc2l6ZSA8PCAxKTsNCiANCi0jaWZkZWYgUEM5 OA0KKyNpZiBkZWZpbmVkKFBDOTgpIHx8IGRlZmluZWQoTk9fTUVNT1JZX0hP TEUpDQogCWlmICh3aGNyICYgMHgwMGZlTEwpIHsNCisjaWZkZWYgUEM5OA0K IAkJLyoNCiAJCSAqIElmIGJpdCAyIG9mIHBvcnQgMHg0M2IgaXMgMCwgZGlz YWJsZSB3cnRlIGFsbG9jYXRlIGZvciB0aGUNCiAJCSAqIDE1LTE2TSByYW5n ZS4NCkBAIC02MzcsNiArNjM5LDcgQEANCiAJCWlmICghKGluYigweDQzYikg JiA0KSkNCiAJCQl3aGNyICY9IH4weDAwMDFMTDsNCiAJCWVsc2UNCisjZW5k aWYNCiAJCQl3aGNyIHw9ICAweDAwMDFMTDsNCiAJfQ0KICNlbHNlDQpAQCAt NjQ0LDcgKzY0Nyw2OCBAQA0KIAkgKiBUaGVyZSBpcyBubyB3YXkgdG8ga25v dyB3aGV0ZXIgMTUtMTZNIGhvbGUgZXhpc3RzIG9yIG5vdC4gDQogCSAqIFRo ZXJlZm9yZSwgd2UgZGlzYWJsZSB3cml0ZSBhbGxvY2F0ZSBmb3IgdGhpcyBy YW5nZS4NCiAJICovDQotCXdoY3IgJj0gMHgwMGZlTEw7DQorCXdoY3IgJj0g fjB4MDAwMUxMOw0KKyNlbmRpZg0KKwl3cm1zcigweDBjMDAwMDA4Miwgd2hj cik7DQorDQorCXdyaXRlX2VmbGFncyhlZmxhZ3MpOw0KKwllbmFibGVfaW50 cigpOw0KK30NCisNCit2b2lkDQorZW5hYmxlX0s2XzJfd3RfYWxsb2Modm9p ZCkNCit7DQorCXF1YWRfdAlzaXplOw0KKwl1X2ludDY0X3QJd2hjcjsNCisJ dV9sb25nCWVmbGFnczsNCisNCisJZWZsYWdzID0gcmVhZF9lZmxhZ3MoKTsN CisJZGlzYWJsZV9pbnRyKCk7DQorCXdiaW52ZCgpOw0KKw0KKyNpZmRlZiBD UFVfRElTQUJMRV9DQUNIRQ0KKwkvKg0KKwkgKiBDZXJ0YWluIEs2LTIgYm94 IGJlY29tZXMgdW5zdGFibGUgd2hlbiB3cml0ZSBhbGxvY2F0aW9uIGlzDQor CSAqIGVuYWJsZWQuDQorCSAqLw0KKwkvKg0KKwkgKiBUaGUgQU1ELUs2IHBy b2Nlc3NlciBwcm92aWRlcyB0aGUgNjQtYml0IFRlc3QgUmVnaXN0ZXIgMTIo VFIxMiksDQorCSAqIGJ1dCBvbmx5IHRoZSBDYWNoZSBJbmhpYml0KENJKSAo Yml0IDMgb2YgVFIxMikgaXMgc3VwcHBvcnRlZC4NCisJICogQWxsIG90aGVy IGJpdHMgaW4gVFIxMiBoYXZlIG5vIGVmZmVjdCBvbiB0aGUgcHJvY2Vzc2Vy J3Mgb3BlcmF0aW9uLg0KKwkgKiBUaGUgSS9PIFRyYXAgUmVzdGFydCBmdW5j dGlvbiAoYml0IDkgb2YgVFIxMikgaXMgYWx3YXlzIGVuYWJsZWQNCisJICog b24gdGhlIEFNRC1LNi4NCisJICovDQorCXdybXNyKDB4MDAwMDAwMGUsICh1 X2ludDY0X3QpMHgwMDA4KTsNCisjZW5kaWYNCisJLyogRG9uJ3QgYXNzdW1l IHRoYXQgbWVtb3J5IHNpemUgaXMgYWxpZ25lZCB3aXRoIDRNLiAqLw0KKwlp ZiAoTWF4bWVtID4gMCkNCisJICBzaXplID0gKChNYXhtZW0gPj4gOCkgKyAz KSA+PiAyOw0KKwllbHNlDQorCSAgc2l6ZSA9IDA7DQorDQorCS8qIExpbWl0 IGlzIDQwOTJNIGJ5dGVzLiAqLw0KKwlzaXplICY9IDB4M2ZmOw0KKwl3aGNy ID0gKHJkbXNyKDB4YzAwMDAwODIpICYgfigweDNmZkxMIDw8IDIyKSkgfCAo c2l6ZSA8PCAyMik7DQorDQorI2lmIGRlZmluZWQoUEM5OCkgfHwgZGVmaW5l ZChOT19NRU1PUllfSE9MRSkNCisJaWYgKHdoY3IgJiAoMHgzZmZMTCA8PCAy MikpIHsNCisjaWZkZWYgUEM5OA0KKwkJLyoNCisJCSAqIElmIGJpdCAyIG9m IHBvcnQgMHg0M2IgaXMgMCwgZGlzYWJsZSB3cnRlIGFsbG9jYXRlIGZvciB0 aGUNCisJCSAqIDE1LTE2TSByYW5nZS4NCisJCSAqLw0KKwkJaWYgKCEoaW5i KDB4NDNiKSAmIDQpKQ0KKwkJCXdoY3IgJj0gfigxTEwgPDwgMTYpOw0KKwkJ ZWxzZQ0KKyNlbmRpZg0KKwkJCXdoY3IgfD0gIDFMTCA8PCAxNjsNCisJfQ0K KyNlbHNlDQorCS8qDQorCSAqIFRoZXJlIGlzIG5vIHdheSB0byBrbm93IHdo ZXRlciAxNS0xNk0gaG9sZSBleGlzdHMgb3Igbm90LiANCisJICogVGhlcmVm b3JlLCB3ZSBkaXNhYmxlIHdyaXRlIGFsbG9jYXRlIGZvciB0aGlzIHJhbmdl Lg0KKwkgKi8NCisJd2hjciAmPSB+KDFMTCA8PCAxNik7DQogI2VuZGlmDQog CXdybXNyKDB4MGMwMDAwMDgyLCB3aGNyKTsNCiANCg== --0-1280433323-914477014=:29349-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 23 21:31:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA11503 for freebsd-current-outgoing; Wed, 23 Dec 1998 21:31:46 -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 VAA11494 for ; Wed, 23 Dec 1998 21:31:42 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:JbcfqIOLYRmXXLs1QwdFLwJUDbCeQtWV@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 OAA15357; Thu, 24 Dec 1998 14:31:00 +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 OAA25068; Thu, 24 Dec 1998 14:33:07 +0900 (JST) Message-Id: <199812240533.OAA25068@zodiac.mech.utsunomiya-u.ac.jp> To: Mike Smith cc: des@flood.ping.uio.no, current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: future of syscons In-reply-to: Your message of "Wed, 23 Dec 1998 19:51:15 PST." <199812240351.TAA00736@dingo.cdrom.com> References: <199812240351.TAA00736@dingo.cdrom.com> Date: Thu, 24 Dec 1998 14:32:56 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> msmith>controller atkbdc0 at isa? port IO_KBD >> msmith>device atkbd0 at kbdc? >> msmith>device psm0 at kbdc? >... >> msmith>Also, since the atkbd and psm device interrupt handlers can only be >> msmith>called from the atkbdc driver, they don't register interrupts and thu >s >> msmith>don't have/need masks. >> >> There is a compromise here too. In i386, if atkbdc wants to have TWO >> interrupt handlers, it has to call register_intr() directly (and make >> sure that there won't be conflicts), rather than letting >> isa_configure() to do the deed, because isa_configure() can assign >> only one interrupt to a device. Am I wrong? > >No, you're right. But there's nothing stopping you have atkbdc do that >right now; it should never take an interrupt from it's configuration - >if it detects a kbdc, it should always take both implicitly. I think it's dangerous to take both interrupts "automatically" when the keyboard controller is detected. It is true that IRQ 1 is always assigned to the keyboard controller on the AT motherboard and no device can claim it because IRQ 1 line is not available in expansion slots. The PS/2 mouse interrupt IRQ 12 is another story. IRQ 12 is available to ISA and PCI bus slots and you can assign it to a device! We shouldn't make the keyboard controller code to claim IRQ 12 when either 1) a PS/2 mouse is not detected, or 2) another device is using or going to use IRQ 12. I expect all these chores will be solved by decent config(8) and bus code...Then, we should do everything right :-) Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 23 21:57:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA14119 for freebsd-current-outgoing; Wed, 23 Dec 1998 21:57:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.hsonline.net (mail.hsonline.net [205.243.33.25]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA14114 for ; Wed, 23 Dec 1998 21:57:26 -0800 (PST) (envelope-from zamy27@hsonline.net) Received: from hsonline.net [208.10.214.31] by mail.hsonline.net with ESMTP (SMTPD32-4.07) id A0B3CE00148; Thu, 24 Dec 1998 00:52:03 -0500 Message-ID: <3681D7EA.DC7AA5F4@hsonline.net> Date: Thu, 24 Dec 1998 00:58:02 -0500 From: Scott Myron X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-RELEASE i386) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: problem with make buildworld Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, when i try to make buildworld, libc gives me an error somewhere down the line.. ' /usr/libexec/ld-elf.so.1 cannot open "/usr/lib/libc.so.3" but when i cd /usr/lib and ls libc.so.3 it shows it's there.... anyone ever get this problem? or know how to fix this problem? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 23 21:58:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA14217 for freebsd-current-outgoing; Wed, 23 Dec 1998 21:58:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA14212 for ; Wed, 23 Dec 1998 21:58:20 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.56.33]) by smtp05.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA6701; Thu, 24 Dec 1998 06:58:07 +0100 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: <199812232155.OAA25477@vip.consys.com> Date: Thu, 24 Dec 1998 07:04:37 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: "Russell L. Carter" Subject: Re: make build fails on fresh current Cc: freebsd-current@FreeBSD.ORG, tobez@plab.ku.dk Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23-Dec-98 Russell L. Carter wrote: >|Ye might want to make and make install lex and yacc by hand and then try make >|world again. This solved a problem for me during make world. And from the error >|results it looks similar... Always worth a try... >| >|Then again, I could be dead wrong... > > Not this time. Your suggestion appears to have worked for me > (at least I'm further along at this minute). OK, glad I am moving from clooless newbie status to just newbie status ;) Keep us informed... --- Jeroen Ruigrok van der Werven Life is the only Pain asmodai(at)wxs.nl we endeavour... Network/Security Specialist BSD & picoBSD: 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 Dec 23 22:16:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA15870 for freebsd-current-outgoing; Wed, 23 Dec 1998 22:16:42 -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 WAA15865 for ; Wed, 23 Dec 1998 22:16:41 -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 WAA13994; Wed, 23 Dec 1998 22:16:28 -0800 (PST) Date: Wed, 23 Dec 1998 22:16:27 -0800 (PST) From: Chris Timmons To: Scott Myron cc: freebsd-current@FreeBSD.ORG Subject: Re: problem with make buildworld In-Reply-To: <3681D7EA.DC7AA5F4@hsonline.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 Are your /etc files up-to-date? Just wondering if your ldconfig_paths rc.conf variable is correctly set. On Thu, 24 Dec 1998, Scott Myron wrote: > Hello, when i try to make buildworld, libc gives me an error somewhere > down the line.. > > ' /usr/libexec/ld-elf.so.1 cannot open "/usr/lib/libc.so.3" > > but when i cd /usr/lib and ls libc.so.3 > it shows it's there.... anyone ever get this problem? or know how to fix > this problem? > > > 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 Dec 23 23:53:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA28364 for freebsd-current-outgoing; Wed, 23 Dec 1998 23:53:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from poboxer.pobox.com (port35.prairietech.net [208.141.230.112]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA28355 for ; Wed, 23 Dec 1998 23:53:28 -0800 (PST) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.1/8.9.1) id BAA00659; Thu, 24 Dec 1998 01:53:09 -0600 (CST) (envelope-from alk) From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 24 Dec 1998 01:53:08 -0600 (CST) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: current@FreeBSD.ORG Subject: funky ide behaviour X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13953.56924.282054.550290@avalon.east> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When I try to mv a 145 MB file, I see this: wd2: interrupt timeout (status 50 error 0) wd2: wdtimeout() DMA status 1 wd2: interrupt timeout (status 50 error 0) wd2: wdtimeout() DMA status 1 wd2: Last time I say: interrupt timeout. Probably a portable PC. (status 50 error 0) wd2: wdtimeout() DMA status 1 doing the mv at nice -19 prevents such complaints. PR440FX dual PPro SMP, Dec 24 00:11:47 avalon /kernel: wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa Dec 24 00:11:47 avalon /kernel: wdc1: unit 0 (wd2): , DMA, 32-bit, multi-block-16 kernel is freshly cvsup'd and built (make world, make kernel as of) -rwxrwxr-x 2 alk wheel 1834143 Dec 22 11:38 kernel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 24 02:28:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA13112 for freebsd-current-outgoing; Thu, 24 Dec 1998 02:28:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from piccolo.rql.net.ua (piccolo.rql.net.ua [195.123.48.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA13104 for ; Thu, 24 Dec 1998 02:28:26 -0800 (PST) (envelope-from timt@rql.net.ua) Received: from rql.net.ua (monitor.rql.net.ua [195.123.48.88]) by piccolo.rql.net.ua (8.8.8/8.8.5) with ESMTP id MAA05568 for ; Thu, 24 Dec 1998 12:28:05 +0200 (EET) Message-ID: <368216EE.BA0A3932@rql.net.ua> Date: Thu, 24 Dec 1998 12:26:54 +0200 From: Tim Tretyak Organization: RQL-Ukraine X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: ru,en,uk MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Oracle8 for linux now working!!! References: <19981222131603.B13835@tar.com> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Congratulations! Oracle8 for linux now working with latest CURRENT Installation procedure is not trivial, but result is perfect. Special thanks to all, who realize linux-threads emulation in CURRENT. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 24 02:48:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA15067 for freebsd-current-outgoing; Thu, 24 Dec 1998 02:48:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebsd.dk (sos.freebsd.dk [212.242.42.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA15041 for ; Thu, 24 Dec 1998 02:48:13 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id LAA02161; Thu, 24 Dec 1998 11:46:18 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199812241046.LAA02161@freebsd.dk> Subject: Re: Oracle8 for linux now working!!! In-Reply-To: <368216EE.BA0A3932@rql.net.ua> from Tim Tretyak at "Dec 24, 1998 12:26:54 pm" To: timt@rql.net.ua (Tim Tretyak) Date: Thu, 24 Dec 1998 11:46:18 +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 Tim Tretyak wrote: > Congratulations! > > Oracle8 for linux now working with latest CURRENT I know :) > Installation procedure is not trivial, but result is perfect. Well, not yet, but we are close... > Special thanks to all, who realize linux-threads emulation in CURRENT. Erhm, Oracle doesn't use that, but its cool newertheless :) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@freebsd.org) FreeBSD Core Team member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 24 04:43:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA26848 for freebsd-current-outgoing; Thu, 24 Dec 1998 04:43:32 -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 EAA26840; Thu, 24 Dec 1998 04:43:29 -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 HAA85312; Thu, 24 Dec 1998 07:43:16 -0500 (EST) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: alpha@FreeBSD.ORG cc: current@FreeBSD.ORG From: "Gary Palmer" Subject: make world breakage on alpha Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 24 Dec 1998 07:43:16 -0500 Message-ID: <85308.914503396@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From this mornings make world on an Alphastation 600: cd /usr/src/lib/msun; /usr/obj/elf/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED cleandepend; /usr/obj/elf/usr/src/tmp/usr/bin/m ake -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED all; /usr/obj/elf/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -B install cleandir obj rm -f .depend /usr/obj/elf/usr/src/lib/msun/GRTAGS /usr/obj/elf/usr/src/lib/msun/GSYMS /usr/obj/elf/usr/src/lib/msun/GTAGS cc -O -pipe -mtrap-precision=i -mfp-trap-mode=su -D_IEEE_LIBM -D_ARCH_INDIRECT= -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/lib/msun/src/e_acos.c -o e_acos.o cc1: Invalid option `trap-precision=i' cc1: Invalid option `fp-trap-mode=su' cc -O -pipe -mtrap-precision=i -mfp-trap-mode=su -D_IEEE_LIBM -D_ARCH_INDIRECT= -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/lib/msun/src/e_acosf.c -o e_acosf.o cc1: Invalid option `trap-precision=i' cc1: Invalid option `fp-trap-mode=su' cc -O -pipe -mtrap-precision=i -mfp-trap-mode=su -D_IEEE_LIBM -D_ARCH_INDIRECT= -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/lib/msun/src/e_acosh.c -o e_acosh.o cc1: Invalid option `trap-precision=i' cc1: Invalid option `fp-trap-mode=su' cc -O -pipe -mtrap-precision=i -mfp-trap-mode=su -D_IEEE_LIBM -D_ARCH_INDIRECT= -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/lib/msun/src/e_acoshf.c -o e_acoshf.o cc -O -pipe -mtrap-precision=i -mfp-trap-mode=su -D_IEEE_LIBM -D_ARCH_INDIRECT= -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/lib/msun/src/e_asin.c -o e_asin.o cc -O -pipe -mtrap-precision=i -mfp-trap-mode=su -D_IEEE_LIBM -D_ARCH_INDIRECT= -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/lib/msun/src/e_asinf.c -o e_asinf.o cc -O -pipe -mtrap-precision=i -mfp-trap-mode=su -D_IEEE_LIBM -D_ARCH_INDIRECT= -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/lib/msun/src/e_atan2.c -o e_atan2.o *** Error code 1 cc -O -pipe -mtrap-precision=i -mfp-trap-mode=su -D_IEEE_LIBM -D_ARCH_INDIRECT= -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/lib/msun/src/e_atan2f.c -o e_atan2f.o cc1: Invalid option `trap-precision=i' cc1: Invalid option `trap-precision=i' cc1: Invalid option `trap-precision=i' cc1: Invalid option `trap-precision=i' cc1: Invalid option `fp-trap-mode=su' cc1: Invalid option `fp-trap-mode=su' cc1: Invalid option `fp-trap-mode=su' cc1: Invalid option `fp-trap-mode=su' cc1: Invalid option `trap-precision=i' cc1: Invalid option `fp-trap-mode=su' *** Error code 1 *** Error code 1 *** Error code 1 *** Error code 1 *** Error code 1 *** Error code 1 *** Error code 1 8 errors *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error 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 Dec 24 04:54:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA28009 for freebsd-current-outgoing; Thu, 24 Dec 1998 04:54: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 EAA28002 for ; Thu, 24 Dec 1998 04:54:29 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:EJu9KH8G1yoOeSUparwnJABVoMjOV9Gq@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 VAA16844; Thu, 24 Dec 1998 21:53:55 +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 VAA06222; Thu, 24 Dec 1998 21:56:02 +0900 (JST) Message-Id: <199812241256.VAA06222@zodiac.mech.utsunomiya-u.ac.jp> To: hm@hcs.de cc: mike@smith.net.au (Mike Smith), current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: future of syscons In-reply-to: Your message of "Wed, 23 Dec 1998 09:51:40 +0100." References: Date: Thu, 24 Dec 1998 21:55:01 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >At that time i worked on a version of pcvt containing all the patches and >fixes people sent in and the ones i grabbed from PR's. Further, all the >ifdef spaghetti is removed (and as a result, only FreeBSD is supported >anymore) and all the dead code of the "old" way of X server interfacing. >The result is available at http://www.hcs.de/users/hm/hm-projects.html > >Pcvt needs much more cleanup and some enhancements here and there, and when >i realized how much work this would be, i stopped ;-) > >Instead of working on pcvt, i would let it rest in peace if it were possible >to move its functionality to a new modularized and open console driver. Not much has been designed or decided about terminal emulation code yet. I have just a vague idea that the terminal emulator code shall write to the vty's internal buffer, rather than directly to the screen, and a timer routine will periodically render it to screen. Let's work together in designing this, shall we? Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 24 05:01:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA28662 for freebsd-current-outgoing; Thu, 24 Dec 1998 05:01:29 -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 FAA28657 for ; Thu, 24 Dec 1998 05:01:26 -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 IAA16147; Thu, 24 Dec 1998 08:01:20 -0500 (EST) (envelope-from lee) Message-ID: <19981224080120.B16063@tidalwave.net> Date: Thu, 24 Dec 1998 08:01:20 -0500 From: Lee Cremeans To: alk@pobox.com, current@FreeBSD.ORG Subject: Re: funky ide behaviour Reply-To: lcremean@tidalwave.net References: <13953.56924.282054.550290@avalon.east> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <13953.56924.282054.550290@avalon.east>; from Tony Kimball on Thu, Dec 24, 1998 at 01:53:08AM -0600 X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 24, 1998 at 01:53:08AM -0600, Tony Kimball wrote: > > When I try to mv a 145 MB file, I see this: > > wd2: interrupt timeout (status 50 error 0) > wd2: wdtimeout() DMA status 1 > wd2: interrupt timeout (status 50 error 0) > wd2: wdtimeout() DMA status 1 > wd2: Last time I say: interrupt timeout. Probably a portable PC. (status 50 error 0) > wd2: wdtimeout() DMA status 1 > > doing the mv at nice -19 prevents such complaints. PR440FX dual PPro SMP, > > Dec 24 00:11:47 avalon /kernel: wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa > Dec 24 00:11:47 avalon /kernel: wdc1: unit 0 (wd2): , DMA, 32-bit, multi-block-16 * What rev of ide_pci.c are you using? 1.19 fixed a unit-handling bug that kept UDMA from being enabled correctly. * Does this work without complaint? dd if=/dev/rwd2 of=/dev/null bs=1024k count=50 -- +--------------------------------------------------------------------+ | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)| | lcremean@tidalwave.net| http://st-lcremean.tidalwave.net | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 24 05:03:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA29035 for freebsd-current-outgoing; Thu, 24 Dec 1998 05:03:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA29030 for ; Thu, 24 Dec 1998 05:03:42 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from ben by scientia.demon.co.uk with local (Exim 2.10 #2) id 0zt9E6-0000B5-00 for freebsd-current@freebsd.org; Thu, 24 Dec 1998 11:46:46 +0000 Date: Thu, 24 Dec 1998 11:46:46 +0000 From: Ben Smithurst To: freebsd-current@FreeBSD.ORG Subject: buildworld fails in ficl with NOPERL set Message-ID: <19981224114646.A620@scientia.demon.co.uk> 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 subject says it all really... When NOPERL is defined, ficl can't be built since "perl" isn't in the path. Is there any reason why a simple patch like the following couldn't be applied? --- sys/boot/ficl/Makefile~ Thu Dec 24 10:58:15 1998 +++ sys/boot/ficl/Makefile Thu Dec 24 11:04:43 1998 @@ -16,8 +16,16 @@ .PATH: ${.CURDIR}/softwords CFLAGS+= -I${.CURDIR} +# If building the world with NOPERL, use the system's already installed +# perl, otherwise find perl in the build process's $PATH. +.if defined(NOPERL) +PERL=/usr/bin/perl +.else +PERL=perl +.endif + softcore.c: ${SOFTWORDS} softcore.pl - (cd ${.CURDIR}/softwords; perl softcore.pl ${SOFTWORDS}) > ${.TARGET} + (cd ${.CURDIR}/softwords; ${PERL} softcore.pl ${SOFTWORDS}) > ${.TARGET} .include This won't make any difference if NOPERL isn't defined. If someone is building the world with NOPERL, and they don't have /usr/bin/perl, they won't be any worse off either. (I know this was mentioned before, around 5th November, but I didn't see any reasons why this couldn't be fixed.) -- Ben Smithurst ben@scientia.demon.co.uk send a blank message to ben+pgp@scientia.demon.co.uk for PGP key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 24 05:16:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA00536 for freebsd-current-outgoing; Thu, 24 Dec 1998 05:16:36 -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 FAA00520; Thu, 24 Dec 1998 05:16:32 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id NAA01857; Thu, 24 Dec 1998 13:16:14 GMT Date: Thu, 24 Dec 1998 13:16:14 +0000 (GMT) From: Doug Rabson To: Gary Palmer cc: alpha@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: make world breakage on alpha In-Reply-To: <85308.914503396@gjp.erols.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, 24 Dec 1998, Gary Palmer wrote: > > >From this mornings make world on an Alphastation 600: > > cd /usr/src/lib/msun; /usr/obj/elf/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN > -DNOPIC -DNOPROFILE -DNOSHARED cleandepend; /usr/obj/elf/usr/src/tmp/usr/bin/m > ake -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED all; > /usr/obj/elf/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE > -DNOSHARED -B install cleandir obj > rm -f .depend /usr/obj/elf/usr/src/lib/msun/GRTAGS > /usr/obj/elf/usr/src/lib/msun/GSYMS /usr/obj/elf/usr/src/lib/msun/GTAGS > cc -O -pipe -mtrap-precision=i -mfp-trap-mode=su -D_IEEE_LIBM > -D_ARCH_INDIRECT= -I/usr/obj/elf/usr/src/tmp/usr/include -c > /usr/src/lib/msun/src/e_acos.c -o e_acos.o > cc1: Invalid option `trap-precision=i' > cc1: Invalid option `fp-trap-mode=su' Oh. It seems that the stock gcc-2.7.2.1 doesn't understand the -mtrap-precision and -mfp-trap-mode arguments. The gcc patches from http://www.freebsd.org/~dfr fix this. Unfortunately I use these patches all the time so I didn't notice that the unpatched compiler doesn't support software completion properly. I'll back out the Makefile change in msun until we upgrade to a decent compiler. -- 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 Dec 24 05:42:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA02604 for freebsd-current-outgoing; Thu, 24 Dec 1998 05:42:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebsd.dk (sos.freebsd.dk [212.242.42.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA02599 for ; Thu, 24 Dec 1998 05:42:28 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id OAA02436; Thu, 24 Dec 1998 14:21:13 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199812241321.OAA02436@freebsd.dk> Subject: Re: future of syscons In-Reply-To: <199812241256.VAA06222@zodiac.mech.utsunomiya-u.ac.jp> from Kazutaka YOKOTA at "Dec 24, 1998 9:55: 1 pm" To: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA) Date: Thu, 24 Dec 1998 14:21:13 +0100 (CET) Cc: hm@hcs.de, mike@smith.net.au, current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp 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 Kazutaka YOKOTA wrote: > Not much has been designed or decided about terminal emulation code > yet. I have just a vague idea that the terminal emulator code shall > write to the vty's internal buffer, rather than directly to the > screen, and a timer routine will periodically render it to screen. Thats how it allready works, updating the HWscreen is totally decoupled from the actual SWscreen buffer. Its only a matter of seperating the decode of ESC something chars into a module that then can be loaded with the required emulation functionality. Leave the simple ones (backspace, enter, etc) in the main code, and let the rest be handeled seperately. That way one can also have a very minimalistic console for X only workstations. So do I hear a volounteer to write a generic VTXXX emulator ?? -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@freebsd.org) FreeBSD Core Team member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 24 05:58:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA03954 for freebsd-current-outgoing; Thu, 24 Dec 1998 05:58:04 -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 FAA03921 for ; Thu, 24 Dec 1998 05:57:57 -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 TAA22227 for ; Thu, 24 Dec 1998 19:52:50 +0600 (NS) Date: Thu, 24 Dec 1998 19:52:50 +0600 (NS) From: Max Khon To: freebsd-current@FreeBSD.ORG Subject: if_arp.c from NetBSD 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! Is it planned to merge if_arp.c from NetBSD? I'm trying to port NetBSD/amiga if_bah driver (arcnet) and without generic arp (not that one in if_ether.c) it seems quite difficult to do that. I think FreeBSD Token Ring project needs generic arp too. /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 24 06:54:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA08461 for freebsd-current-outgoing; Thu, 24 Dec 1998 06:54:58 -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 GAA08449; Thu, 24 Dec 1998 06:54:55 -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 JAA87038; Thu, 24 Dec 1998 09:54:41 -0500 (EST) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: Doug Rabson cc: alpha@FreeBSD.ORG, current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: make world breakage on alpha In-reply-to: Your message of "Thu, 24 Dec 1998 13:16:14 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 24 Dec 1998 09:54:40 -0500 Message-ID: <87034.914511280@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson wrote in message ID : > Oh. It seems that the stock gcc-2.7.2.1 doesn't understand the > -mtrap-precision and -mfp-trap-mode arguments. The gcc patches from > http://www.freebsd.org/~dfr fix this. Unfortunately I use these patches > all the time so I didn't notice that the unpatched compiler doesn't > support software completion properly. I'll back out the Makefile change > in msun until we upgrade to a decent compiler. I seem to remember noises being made a while back that after 3.0 got cut we'd upgrade binutils and gcc ... I think the time to do that is before the 3.0.1 branch is taken (IMHO), so is there anyone working on this? 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 Dec 24 07:26:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA12107 for freebsd-current-outgoing; Thu, 24 Dec 1998 07:26:28 -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 HAA12102; Thu, 24 Dec 1998 07:26:24 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id PAA11791; Thu, 24 Dec 1998 15:26:01 GMT Date: Thu, 24 Dec 1998 15:26:01 +0000 (GMT) From: Doug Rabson To: Gary Palmer cc: alpha@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: make world breakage on alpha In-Reply-To: <87034.914511280@gjp.erols.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, 24 Dec 1998, Gary Palmer wrote: > Doug Rabson wrote in message ID > : > > Oh. It seems that the stock gcc-2.7.2.1 doesn't understand the > > -mtrap-precision and -mfp-trap-mode arguments. The gcc patches from > > http://www.freebsd.org/~dfr fix this. Unfortunately I use these patches > > all the time so I didn't notice that the unpatched compiler doesn't > > support software completion properly. I'll back out the Makefile change > > in msun until we upgrade to a decent compiler. > > I seem to remember noises being made a while back that after 3.0 got cut we'd > upgrade binutils and gcc ... I think the time to do that is before the 3.0.1 > branch is taken (IMHO), so is there anyone working on this? Our binutils is pretty up to date at version 2.9.1. I don't quite have the time to tackle upgrading the compiler (and to cope with the fallout from changing compilers). -- 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 Dec 24 07:37:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA13466 for freebsd-current-outgoing; Thu, 24 Dec 1998 07:37:23 -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 HAA13461; Thu, 24 Dec 1998 07:37:20 -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 QAA28888; Thu, 24 Dec 1998 16:36:59 +0100 (MET) Received: (from son@localhost) by teaser.fr (8.9.1/8.9.1) id RAA01257; Thu, 24 Dec 1998 17:37:39 GMT (envelope-from son) Message-ID: <19981224173739.62395@breizh.prism.uvsq.fr> Date: Thu, 24 Dec 1998 17:37:39 +0000 From: Nicolas Souchu To: tarkhil@asteroid.svib.ru Cc: multimedia@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: AverMedia TV Capture, remote control, iic, smb... References: <199812220956.MAA19305@minas-tirith.pol.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199812220956.MAA19305@minas-tirith.pol.ru>; from Alex Povolotsky on Tue, Dec 22, 1998 at 12:56:46PM +0300 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 Tue, Dec 22, 1998 at 12:56:46PM +0300, Alex Povolotsky wrote: > >Hello! > >I've recently purchased AVerMedia TVCapture card with remote control, and I'm >thinking on how to make remote control working. Try to find the I2C device on the board that is supposed to translate remote signals to I2C characters. Try Philips web site and see if in the list of I2C chips there's yours. > >Looks like smbus and I2C have _some_ relation to it, but where can I get more >info? Certainly. See iicbus(4) and iic(4) man pages and http://www.freebsd.org/~nsouch/iicbus.html for related links. 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 Thu Dec 24 07:50:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA14422 for freebsd-current-outgoing; Thu, 24 Dec 1998 07:50:06 -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 HAA14415 for ; Thu, 24 Dec 1998 07:50:04 -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.1/8.9.1) with ESMTP id HAA37309; Thu, 24 Dec 1998 07:47:40 -0800 (PST) To: S ren Schmidt cc: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA), hm@hcs.de, mike@smith.net.au, current@FreeBSD.ORG Subject: Re: future of syscons In-reply-to: Your message of "Thu, 24 Dec 1998 14:21:13 +0100." <199812241321.OAA02436@freebsd.dk> Date: Thu, 24 Dec 1998 07:47:39 -0800 Message-ID: <37305.914514459@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > So do I hear a volounteer to write a generic VTXXX emulator ?? I'm tempted, but last time I tackled this problem I ended up doing it with a runtime programming language. Are you sure you want this? :-) [see ports/x11/emu to see what I'm talking about]. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 24 08:03:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16297 for freebsd-current-outgoing; Thu, 24 Dec 1998 08:03:04 -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 IAA16271; Thu, 24 Dec 1998 08:03:01 -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.1/8.9.1) with ESMTP id IAA37365; Thu, 24 Dec 1998 08:02:43 -0800 (PST) To: "Gary Palmer" cc: current@FreeBSD.ORG Subject: Re: make world breakage on alpha In-reply-to: Your message of "Thu, 24 Dec 1998 09:54:40 EST." <87034.914511280@gjp.erols.com> Date: Thu, 24 Dec 1998 08:02:43 -0800 Message-ID: <37362.914515363@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I seem to remember noises being made a while back that after 3.0 got cut we'd > upgrade binutils and gcc ... I think the time to do that is before the 3.0.1 > branch is taken (IMHO), so is there anyone working on this? Actually, more realistically I don't think that this can happen until _after_ the branch. 3.0.x sort of missed its window for new compiler technology, I'm afraid. :-( - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 24 08:04:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16534 for freebsd-current-outgoing; Thu, 24 Dec 1998 08:04:57 -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 IAA16526 for ; Thu, 24 Dec 1998 08:04:55 -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 LAA19362 for ; Thu, 24 Dec 1998 11:04:45 -0500 (EST) Date: Thu, 24 Dec 1998 11:04:45 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: current@FreeBSD.ORG Subject: revoke of fifos 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 revoke(2) on VFIFO types is broken now, leading to stranded mbuf's. I suppose bde is tracking this down, but for now, why don't we return EINVAL in revoke(2)? /usr/src/sys/kern/vfs_syscalls.c: unmodified, readonly: line 2912 of 3038 [95%] if (vp->v_type == VFIFO) { error = EINVAL; goto out; } That should temporarily work to prevent the following easily reproducible mbuf- starvation crash case: (as any user) mkfifo fifo while true; do dd if=fifo of=/dev/null & dd if=/dev/zero of=fifo & ./revoke \ fifo; done where revoke.c is on the lines of #include #include int main(int argc, char **argv) { if (!argv[1]) exit(1); printf("revoke(%s) == %d\n", argv[1], revoke(argv[1])); exit(0); } 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 Thu Dec 24 08:11:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA17050 for freebsd-current-outgoing; Thu, 24 Dec 1998 08:11:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA17045 for ; Thu, 24 Dec 1998 08:11:39 -0800 (PST) (envelope-from arno@heho.snv.jussieu.fr) Received: from hall.snv.jussieu.fr (hall.snv.jussieu.fr [134.157.37.2]) by shiva.jussieu.fr (8.9.1a/jtpda-5.3.1) with ESMTP id RAA06559 for ; Thu, 24 Dec 1998 17:11:26 +0100 (CET) Received: from heho.snv.jussieu.fr (heho.snv.jussieu.fr [134.157.37.22]) by hall.snv.jussieu.fr (8.8.8/jtpda-5.2) with SMTP id RAA23227 for ; Thu, 24 Dec 1998 17:14:38 +0100 (CET) Received: by heho.snv.jussieu.fr (4.1/jf930126) at Thu, 24 Dec 98 17:11:25 +0100 To: current@FreeBSD.ORG Subject: Q: -DNOLIBG++ howto? From: arno@heho.snv.jussieu.fr (Arno J. Klaassen) Date: 24 Dec 1998 17:11:24 +0100 Message-Id: Lines: 20 X-Mailer: Gnus v5.5/Emacs 20.2 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm trying to compile the world with some egcs-binutils snapshot (not from the ports collection). Most assembler files won't compile, but all but a couple of c-files compile flawlessly. For the c++ files I'd like to add a -DNOLIBG++ option to the overall Makefile. Could someone eventually indicate me which files to alter to: - not build contrib/libg++ - not add -I/usr/obj//src/tmp/usr/include/g++ to the include paths - take away dependencies for g++-include and libg++* (the latter two are not really urgent since I can edit the groff and libc_r Makefiles by hand as well) Thanx a lot in advance. Amicalement, Arno Klaassen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 24 08:54:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA22749 for freebsd-current-outgoing; Thu, 24 Dec 1998 08:54:00 -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 IAA22737 for ; Thu, 24 Dec 1998 08:53:57 -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 RAA21307; Thu, 24 Dec 1998 17:53:30 +0100 (MET) Received: (from son@localhost) by teaser.fr (8.9.1/8.9.1) id SAA04257; Thu, 24 Dec 1998 18:19:48 GMT (envelope-from son) Message-ID: <19981224181948.61645@breizh.prism.uvsq.fr> Date: Thu, 24 Dec 1998 18:19:48 +0000 From: Nicolas Souchu To: =?iso-8859-1?Q?Jos=E9_M=AA_Alcaide?= Cc: Stephen Palmer , gp@oitunix.oit.umass.edu, freebsd-current@FreeBSD.ORG Subject: Re: Request fo help with Zip Drive on vpo0 in -current] References: <19981219130349.11043.qmail@www0f.netaddress.usa.net> <367E88FB.B9F0D79@we.lc.ehu.es> <19981222010450.23781@breizh.prism.uvsq.fr> <368171FF.B8A5B268@we.lc.ehu.es> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.81e In-Reply-To: =?iso-8859-1?Q?=3C368171FF=2EB8A5B268=40we=2Elc=2Eehu=2Ees=3E=3B_from_Jo?= =?iso-8859-1?Q?s=E9_M=AA_Alcaide_on_Wed=2C_Dec_23=2C_1998_at_11=3A43=3A1?= =?iso-8859-1?Q?1PM_+0100?= 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 Wed, Dec 23, 1998 at 11:43:11PM +0100, José Mª Alcaide wrote: > >Nicolas Souchu wrote: >> >> Exactly the same problem here. What was your last vpo-running -current >> udpate? >> Sorry, I'm wrong, it's ok here with December, 22th. So I can't really help you from there :( You may retry previous sys/ releases Dec, 1st, Nov, 15th to find out the bogus submit. > >I don't remember exactly... I think that it was FreeBSD-current as of >November, 15th o 16th. > >I submitted a PR (kern/9174). > >-- 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 > -- 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 Thu Dec 24 09:21:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24645 for freebsd-current-outgoing; Thu, 24 Dec 1998 09:21:43 -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 JAA24634 for ; Thu, 24 Dec 1998 09:21:40 -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 JAA07962; Thu, 24 Dec 1998 09:19:22 -0800 (PST) Date: Thu, 24 Dec 1998 09:19:22 -0800 (PST) From: Chris Timmons To: Max Khon cc: freebsd-current@FreeBSD.ORG Subject: Re: if_arp.c from NetBSD 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 Bill Fenner is generally our arp guy, and I got a note from his vacation program when I sent him mail the other day about something else. You might drop him a line after the new year if you don't hear anything from him. Better yet, file a PR and I'll give it to him for Christmas :) -Chris On Thu, 24 Dec 1998, Max Khon wrote: > hi, there! > > Is it planned to merge if_arp.c from NetBSD? > I'm trying to port NetBSD/amiga if_bah driver (arcnet) and without > generic arp (not that one in if_ether.c) it seems quite difficult > to do that. > I think FreeBSD Token Ring project needs generic arp too. > > /fjoe > > > 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 Dec 24 09:43:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA27423 for freebsd-current-outgoing; Thu, 24 Dec 1998 09:43:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www1.interdestination.net (www1.interdestination.net [209.12.127.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA27418 for ; Thu, 24 Dec 1998 09:43:17 -0800 (PST) (envelope-from zapper@idsmail.com) Received: from idsmail.com (zapper@id39.dialup.interdestination.com [209.12.192.119]) by www1.interdestination.net (8.9.1/8.9.1) with ESMTP id LAA26157 for ; Thu, 24 Dec 1998 11:56:42 -0600 (CST) Message-ID: <36827C72.8C7369AB@idsmail.com> Date: Thu, 24 Dec 1998 11:40:02 -0600 From: Zapper X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: FreeBSD Current Subject: ppp 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 almost positive this is not the correct mailing list for this question, so if it isn't will someone kindly point me in the right direction. Since I started getting this Warning after I upgraded from 2.2.7 to 3.0 I'll ask here first. I keep getting the following warning and I am at a loss as what to do to correct it ... Dec 23 20:45:47 zapper ppp[228]: Warning: Unrecognized CBCP packet (code 5, length 4) I'm actually using ppp.conf for my dial-up. I get disconnected after receiving this message. I don't know if it's a bad string from my isp or if it's an exploit but I do know that it only started since my upgrade to 3.0 Current. Thanks Zapper To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 24 10:44:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA04508 for freebsd-current-outgoing; Thu, 24 Dec 1998 10:44:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.hyd.rampnet.com ([208.240.44.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA04492 for ; Thu, 24 Dec 1998 10:44:42 -0800 (PST) (envelope-from ashok@rampnet.com) Received: from ns.hyd.rampnet.com (shakti.hyd.rampnet.com [208.240.44.77]) by ns.hyd.rampnet.com (8.8.7/8.8.5) with SMTP id AAA16151 for ; Fri, 25 Dec 1998 00:12:15 +0530 Message-ID: <03f501be2f6e$85e8ff20$4d2cf0d0@shakti.hyd.rampnet.com> From: "Ashok Ramchandra" To: Subject: subscribe Date: Fri, 25 Dec 1998 00:22:14 +0530 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_03F2_01BE2F9C.9F717890" 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 This is a multi-part message in MIME format. ------=_NextPart_000_03F2_01BE2F9C.9F717890 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable subscribe ashok@rampnet.com=20 ------=_NextPart_000_03F2_01BE2F9C.9F717890 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
subscribe ashok@rampnet.com=20
------=_NextPart_000_03F2_01BE2F9C.9F717890-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 24 11:19:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08349 for freebsd-current-outgoing; Thu, 24 Dec 1998 11:19:27 -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 LAA08343 for ; Thu, 24 Dec 1998 11:19:26 -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 LAA08101; Thu, 24 Dec 1998 11:19:12 -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 LAA01894; Thu, 24 Dec 1998 11:19:12 -0800 (PST) (envelope-from jdp@polstra.com) Date: Thu, 24 Dec 1998 11:19:12 -0800 (PST) Message-Id: <199812241919.LAA01894@vashon.polstra.com> To: mike@smith.net.au Subject: Re: trap 12 with interrupts disabled Newsgroups: polstra.freebsd.current In-Reply-To: <199812220225.SAA02191@dingo.cdrom.com> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199812220225.SAA02191@dingo.cdrom.com>, Mike Smith wrote: > > >>> pid 281 (Xaccel): trap 12 with interupts disabled > > >> > > >> Yes, I've noticed this one too. It seems to have crept in relatively > > >> recently, and strangely seems not to cause any problems. > > > > > > The diagnostic just warns of a bad situation (Xaccel has turned off > > > interrupts for some reason, and then pagefaulted), it doesn't mention > > > that it has in fact turned interrupts back on so that the pagefault can > > > be safely completed. > > > > If my page fault fails because I've blocked the interrupt, I'd expect > > some serious damage to happen to the process environment.n > > Usually you're lucky and something else turns them on unconditionally. > This test simply makes damn sure that if you take a fault interrupts > get turned back on. I'm still not entirely clear about the implications of this change. If I understand it right, the message is caused by a bug in Xaccel. The message and the re-enabling of interrupts was added in revision 1.129 of trap.c. The message now isn't particularly rare if you're running Xaccel. I got one almost immediately after updating my kernel. The bug didn't seem to hurt anything before. But now at least one person is reporting hangs on a system running Xaccel. That concerns me. Do the interrupts get turned back off again when control returns to Xaccel, or do they remain on? If Xaccel is assuming they're off, it seems bad to turn them on underfoot. Finally, do we have a contact at XiG to notify about this? 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 Dec 24 11:20:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08467 for freebsd-current-outgoing; Thu, 24 Dec 1998 11:20:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from detlev.UUCP (27-sweet.camalott.com [208.239.153.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA08462 for ; Thu, 24 Dec 1998 11:20:13 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id NAA12242; Thu, 24 Dec 1998 13:17:05 -0600 (CST) (envelope-from joelh) To: Søren Schmidt Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA), hm@hcs.de, mike@smith.net.au, current@FreeBSD.ORG Subject: Re: future of syscons References: <199812241321.OAA02436@freebsd.dk> From: Joel Ray Holveck Date: 24 Dec 1998 13:17:04 -0600 In-Reply-To: Søren Schmidt's message of "Thu, 24 Dec 1998 14:21:13 +0100 (CET)" Message-ID: <86soe5ic3z.fsf@detlev.UUCP> Lines: 24 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Not much has been designed or decided about terminal emulation code >> yet. I have just a vague idea that the terminal emulator code shall >> write to the vty's internal buffer, rather than directly to the >> screen, and a timer routine will periodically render it to screen. > Thats how it allready works, updating the HWscreen is totally decoupled > from the actual SWscreen buffer. Its only a matter of seperating the > decode of ESC something chars into a module that then can be loaded > with the required emulation functionality. Leave the simple ones > (backspace, enter, etc) in the main code, and let the rest be handeled > seperately. That way one can also have a very minimalistic console > for X only workstations. > So do I hear a volounteer to write a generic VTXXX emulator ?? Can you describe a little more what you mean by "a generic VTxxx emulator"? This may be an interesting project. Cheers, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 24 11:22:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08756 for freebsd-current-outgoing; Thu, 24 Dec 1998 11:22:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from poboxer.pobox.com (port22.prairietech.net [208.141.230.99]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA08744 for ; Thu, 24 Dec 1998 11:22:21 -0800 (PST) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.1/8.9.1) id NAA02808; Thu, 24 Dec 1998 13:21:54 -0600 (CST) (envelope-from alk) From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 24 Dec 1998 13:21:53 -0600 (CST) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: lcremean@tidalwave.net Cc: alk@pobox.com, current@FreeBSD.ORG Subject: Re: funky ide behaviour References: <13953.56924.282054.550290@avalon.east> <19981224080120.B16063@tidalwave.net> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13954.37866.317464.980472@avalon.east> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoth Lee Cremeans on Thu, 24 December: : * What rev of ide_pci.c are you using? 1.19 fixed a unit-handling bug that : kept UDMA from being enabled correctly. 1.19 : * Does this work without complaint? : : dd if=/dev/rwd2 of=/dev/null bs=1024k count=50 Yes, it does. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 24 12:01:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13544 for freebsd-current-outgoing; Thu, 24 Dec 1998 12:01:20 -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 MAA13539 for ; Thu, 24 Dec 1998 12:01:18 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA18159; Thu, 24 Dec 1998 11:57:21 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdK18155; Thu Dec 24 19:57:15 1998 Date: Thu, 24 Dec 1998 11:57:12 -0800 (PST) From: Julian Elischer To: Max Khon cc: freebsd-current@FreeBSD.ORG Subject: Re: if_arp.c from NetBSD 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 OSF1 had a generic arp capability. it seemed quite easy.. I think I have it sitting around here somewhere it's based on the 4.4 code but they've just done the usual things to break out code.. switch tables, method arrays etc. On Thu, 24 Dec 1998, Max Khon wrote: > hi, there! > > Is it planned to merge if_arp.c from NetBSD? > I'm trying to port NetBSD/amiga if_bah driver (arcnet) and without > generic arp (not that one in if_ether.c) it seems quite difficult > to do that. > I think FreeBSD Token Ring project needs generic arp too. > > /fjoe > > > 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 Dec 24 13:12:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20485 for freebsd-current-outgoing; Thu, 24 Dec 1998 13:12:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lion.plab.ku.dk (lion.plab.ku.dk [130.225.105.49]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20480 for ; Thu, 24 Dec 1998 13:12:20 -0800 (PST) (envelope-from tobez@lion.plab.ku.dk) Received: from localhost (3319 bytes) by lion.plab.ku.dk via sendmail with P:stdio/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) (ident using unix) id for ; Thu, 24 Dec 1998 22:10:34 +0100 (CET) (Smail-3.2.0.101 1997-Dec-17 #1 built 1998-Nov-8) To: Jeroen Ruigrok/Asmodai Cc: freebsd-current@FreeBSD.ORG, rcarter@pinyon.org Subject: Re: make build fails on fresh current References: From: Anton Berezin Date: 24 Dec 1998 22:10:33 +0100 In-Reply-To: Jeroen Ruigrok/Asmodai's message of Thu, 24 Dec 1998 07:04:37 +0100 (CET) Message-ID: <8667b1kzzq.fsf@lion.plab.ku.dk> Lines: 65 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeroen Ruigrok/Asmodai writes: > > On 23-Dec-98 Russell L. Carter wrote: > >|Ye might want to make and make install lex and yacc by hand and then try make > >|world again. This solved a problem for me during make world. And from the error > >|results it looks similar... Always worth a try... > >| > >|Then again, I could be dead wrong... > > > > Not this time. Your suggestion appears to have worked for me > > (at least I'm further along at this minute). > > OK, glad I am moving from clooless newbie status to just newbie status ;) > > Keep us informed... Uh oh. Bad luck for me... :-( I can make && make install yacc, but I cannot do this with lex: # pwd /usr/src/usr.bin/lex # make Warning: Object directory not changed from original /usr/src/usr.bin/lex cc -O -pipe -I. -I/usr/src/usr.bin/lex -c scan.c scan.l:33: parse.h: No such file or directory scan.l: In function `flexscan': scan.l:108: `SCDECL' undeclared (first use this function) scan.l:108: (Each undeclared identifier is reported only once scan.l:108: for each function it appears in.) scan.l:109: `XSCDECL' undeclared (first use this function) scan.l:125: `SECTEND' undeclared (first use this function) scan.l:131: `OPTION_OP' undeclared (first use this function) scan.l:144: `NAME' undeclared (first use this function) scan.l:275: `OPT_OUTFILE' undeclared (first use this function) scan.l:276: `OPT_PREFIX' undeclared (first use this function) scan.l:277: `OPT_YYCLASS' undeclared (first use this function) scan.l:393: `EOF_OP' undeclared (first use this function) scan.l:416: `PREVCCL' undeclared (first use this function) scan.l:470: `CHAR' undeclared (first use this function) scan.l:519: `CCE_ALNUM' undeclared (first use this function) scan.l:520: `CCE_ALPHA' undeclared (first use this function) scan.l:521: `CCE_BLANK' undeclared (first use this function) scan.l:522: `CCE_CNTRL' undeclared (first use this function) scan.l:523: `CCE_DIGIT' undeclared (first use this function) scan.l:524: `CCE_GRAPH' undeclared (first use this function) scan.l:525: `CCE_LOWER' undeclared (first use this function) scan.l:526: `CCE_PRINT' undeclared (first use this function) scan.l:527: `CCE_PUNCT' undeclared (first use this function) scan.l:528: `CCE_SPACE' undeclared (first use this function) scan.l:529: `CCE_UPPER' undeclared (first use this function) scan.l:530: `CCE_XDIGIT' undeclared (first use this function) scan.l:542: `NUMBER' undeclared (first use this function) *** Error code 1 Stop. # uname -a FreeBSD lion.plab.ku.dk 2.2.7-RELEASE FreeBSD 2.2.7-RELEASE #6: Thu Oct 15 18:09:41 CEST 1998 tobez@lion.plab.ku.dk:/usr/src/sys/compile/LION i386 Oops! Any clues? Thank you in advance. -- Anton Berezin The Protein Laboratory, University of Copenhagen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 24 13:31:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22408 for freebsd-current-outgoing; Thu, 24 Dec 1998 13:31:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www0j.netaddress.usa.net (www0j.netaddress.usa.net [204.68.24.39]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA22387 for ; Thu, 24 Dec 1998 13:31:29 -0800 (PST) (envelope-from eugene.k@lycosmail.com) From: eugene.k@lycosmail.com Received: from oleg-tchetchel by www0j.netaddress.usa.net (SMI-8.6/SMI-SVR4) id VAA11137; Thu, 24 Dec 1998 21:31:17 GMT Date: Thu, 24 Dec 1998 21:31:17 GMT To: freebsd-current@FreeBSD.ORG Subject: Holiday Greetings ! Message-Id: Content-Type: TEXT/PLAIN charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG One of the Christmas miracles: http://www3.mcps.k12.md.us/users/rsfay/magic/index.html Eugene K. http://www.nisco.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 24 14:08:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA27186 for freebsd-current-outgoing; Thu, 24 Dec 1998 14:08:55 -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 OAA27181 for ; Thu, 24 Dec 1998 14:08:53 -0800 (PST) (envelope-from obrien@nuxi.ucdavis.edu) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id OAA10939; Thu, 24 Dec 1998 14:08:38 -0800 (PST) (envelope-from obrien) Message-ID: <19981224140837.A10869@nuxi.com> Date: Thu, 24 Dec 1998 14:08:37 -0800 From: "David O'Brien" To: "Arno J. Klaassen" , current@FreeBSD.ORG Subject: Re: Q: -DNOLIBG++ howto? Reply-To: obrien@nuxi.ucdavis.edu References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Arno J. Klaassen on Thu, Dec 24, 1998 at 05:11:24PM +0100 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 trying to compile the world with some egcs-binutils snapshot (not > from the ports collection). Most assembler files won't compile, but I would 1st start with just compiling everything in place. (ie, cd /usr/src/*/foo ; make CC=egcc). Otherwise, you want to place EGCS in your world (ie, under /usr/src) and hack the `make world' Makefile's appropriately. Otherwise you are destined for doom. > Could someone eventually indicate me which files to alter to: > - not build contrib/libg++ WHY would you even try to compile libg++? What is in contrib/libg++ is part of EGCS. *IF* EGCS were to become the base compiler, contrib-/libg++ will be removed. Hack your /usr/src/*/Makefile's to skip this building step. > - not add -I/usr/obj//src/tmp/usr/include/g++ to the include paths Hack the Makefile's. > - take away dependencies for g++-include and libg++* ditto. -- -- David (obrien@NUXI.ucdavis.edu -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 Thu Dec 24 14:26:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28861 for freebsd-current-outgoing; Thu, 24 Dec 1998 14:26:48 -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 OAA28853 for ; Thu, 24 Dec 1998 14:26:44 -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 RAA17425; Thu, 24 Dec 1998 17:26:39 -0500 (EST) (envelope-from lee) Message-ID: <19981224172639.A16234@tidalwave.net> Date: Thu, 24 Dec 1998 17:26:39 -0500 From: Lee Cremeans To: alk@pobox.com, current@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: funky ide behaviour Reply-To: lcremean@tidalwave.net References: <13953.56924.282054.550290@avalon.east> <19981224080120.B16063@tidalwave.net> <13954.37866.317464.980472@avalon.east> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <13954.37866.317464.980472@avalon.east>; from Tony Kimball on Thu, Dec 24, 1998 at 01:21:53PM -0600 X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 24, 1998 at 01:21:53PM -0600, Tony Kimball wrote: > Quoth Lee Cremeans on Thu, 24 December: > : * What rev of ide_pci.c are you using? 1.19 fixed a unit-handling bug that > : kept UDMA from being enabled correctly. > > 1.19 > > : * Does this work without complaint? > : > : dd if=/dev/rwd2 of=/dev/null bs=1024k count=50 > > Yes, it does. Eeeee...this is the same problem I'm getting on my Acer chipset board when I enable UDMA. It seems to me that there's a problem here that isn't limited to the Acer chips, and I'm not really sure what...the bright side is that it seems to say my UDMA enable code in ide_pci.c is working. -- +--------------------------------------------------------------------+ | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)| | lcremean@tidalwave.net| http://st-lcremean.tidalwave.net | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 24 14:32:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29221 for freebsd-current-outgoing; Thu, 24 Dec 1998 14:32:17 -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 OAA29210 for ; Thu, 24 Dec 1998 14:32:10 -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 RAA02264; Thu, 24 Dec 1998 17:31:35 -0500 (EST) Message-ID: <19981224173135.D1333@ns1.adsu.bellsouth.com> Date: Thu, 24 Dec 1998 17:31:35 -0500 From: Christian Kuhtz To: "Jordan K. Hubbard" , andrea Cc: freebsd-current@FreeBSD.ORG Subject: Re: PPTP and FreeBSD References: <008601be3989$48cf4ac0$4d18b9c2@oma.linet.it> <30164.914431322@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <30164.914431322@zippy.cdrom.com>; from Jordan K. Hubbard on Wed, Dec 23, 1998 at 08:42:02AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 23, 1998 at 08:42:02AM -0800, Jordan K. Hubbard wrote: > > There's any PPTP 'driver' for FreeBSD is it comaptible with the M$ one? > > There is not, I'm afraid. It would be nice to have L2TP around, though. Anyone out there who has done work on an 'L2TP shim'? Cheers, Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 24 14:52:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA01081 for freebsd-current-outgoing; Thu, 24 Dec 1998 14:52:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA01063 for ; Thu, 24 Dec 1998 14:52:03 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.57.174]) by smtp01.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA1816; Thu, 24 Dec 1998 23:51:49 +0100 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: <8667b1kzzq.fsf@lion.plab.ku.dk> Date: Thu, 24 Dec 1998 23:58:24 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Anton Berezin Subject: Re: make build fails on fresh current Cc: rcarter@pinyon.org, freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24-Dec-98 Anton Berezin wrote: ># pwd > /usr/src/usr.bin/lex ># make > Warning: Object directory not changed from original /usr/src/usr.bin/lex > cc -O -pipe -I. -I/usr/src/usr.bin/lex -c scan.c > scan.l:33: parse.h: No such file or directory OK, the resulting errors are all because of the parse.h file Do ye see a parse.h in the lex directory? There's supposed to be one in there. --- Jeroen Ruigrok van der Werven Life is the only Pain asmodai(at)wxs.nl we endeavour... Network/Security Specialist BSD & picoBSD: 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 Thu Dec 24 15:40:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05812 for freebsd-current-outgoing; Thu, 24 Dec 1998 15:40:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Chuska.ConSys.COM (Chuska.ConSys.COM [209.141.107.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05802 for ; Thu, 24 Dec 1998 15:40:06 -0800 (PST) (envelope-from rcarter@psf.Pinyon.ORG) Received: from psf.Pinyon.ORG (ip-17-192.prc.primenet.com [207.218.17.192]) by Chuska.ConSys.COM (8.9.1/8.9.1) with ESMTP id QAA20689; Thu, 24 Dec 1998 16:39:50 -0700 (MST) Received: from psf.Pinyon.ORG (localhost [127.0.0.1]) by psf.Pinyon.ORG (8.9.1/8.8.7) with ESMTP id QAA02214; Thu, 24 Dec 1998 16:36:59 -0700 (MST) Message-Id: <199812242336.QAA02214@psf.Pinyon.ORG> X-Mailer: exmh version 2.0.2 2/24/98 To: Anton Berezin cc: Jeroen Ruigrok/Asmodai , freebsd-current@FreeBSD.ORG, rcarter@pinyon.org Subject: Re: make build fails on fresh current In-reply-to: Your message of "24 Dec 1998 22:10:33 +0100." <8667b1kzzq.fsf@lion.plab.ku.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 24 Dec 1998 16:36:59 -0700 From: "Russell L. Carter" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Jeroen Ruigrok/Asmodai writes: > > > > > On 23-Dec-98 Russell L. Carter wrote: > > >|Ye might want to make and make install lex and yacc by hand and then try make > > >|world again. This solved a problem for me during make world. And from the error > > >|results it looks similar... Always worth a try... > > >| > > >|Then again, I could be dead wrong... > > > > > > Not this time. Your suggestion appears to have worked for me > > > (at least I'm further along at this minute). > > > > OK, glad I am moving from clooless newbie status to just newbie status ;) > > > > Keep us informed... > > Uh oh. Bad luck for me... :-( Well, I was wrong about what I thought I saw scrolling by, and the build really did fail for me again in the same place. Rats! So... This is a circa August -current, aout, trying to upgrade to ELF, and yours is 2.2.7. Odd, as John sez. Russell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 24 17:30:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17260 for freebsd-current-outgoing; Thu, 24 Dec 1998 17:30:26 -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 RAA17251 for ; Thu, 24 Dec 1998 17:30:22 -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 RAA09058 for ; Thu, 24 Dec 1998 17:30: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 RAA00806; Thu, 24 Dec 1998 17:30:09 -0800 (PST) (envelope-from jdp@polstra.com) Date: Thu, 24 Dec 1998 17:30:09 -0800 (PST) Message-Id: <199812250130.RAA00806@vashon.polstra.com> To: current@FreeBSD.ORG Subject: Re: make world breakage on alpha Newsgroups: polstra.freebsd.current In-Reply-To: <37362.914515363@zippy.cdrom.com> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I seem to remember noises being made a while back that after 3.0 > > got cut we'd upgrade binutils and gcc ... Actually, we're already current with GNU on binutils. 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 Dec 24 18:12:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20982 for freebsd-current-outgoing; Thu, 24 Dec 1998 18:12:37 -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 SAA20976 for ; Thu, 24 Dec 1998 18:12:36 -0800 (PST) (envelope-from obrien@nuxi.ucdavis.edu) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id SAA11710; Thu, 24 Dec 1998 18:12:15 -0800 (PST) (envelope-from obrien) Message-ID: <19981224181214.A11566@nuxi.com> Date: Thu, 24 Dec 1998 18:12:14 -0800 From: "David O'Brien" To: Doug Rabson Cc: current@FreeBSD.ORG Subject: Re: Weird NFS error using Solaris 7 server Reply-To: obrien@nuxi.ucdavis.edu References: <199812162320.PAA01606@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Doug Rabson on Thu, Dec 17, 1998 at 11:34:12AM +0000 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 > Could someone test this patch and tell me if it improves things for > Solaris? > > Index: nfs_vnops.c > =================================================================== > RCS file: /home/ncvs/src/sys/nfs/nfs_vnops.c,v > retrieving revision 1.114 > diff -u -r1.114 nfs_vnops.c This patch, with rev 1.103 of src/sys/ufs/ufs/ufs_vnops.c fixes my problems with Solaris 7. (actually w/a ``cd src/sys/ufs/ufs ; cvs up'') Commit away! -- -- David (obrien@NUXI.ucdavis.edu -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 Thu Dec 24 18:22:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA21895 for freebsd-current-outgoing; Thu, 24 Dec 1998 18:22: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 SAA21889 for ; Thu, 24 Dec 1998 18:22:05 -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 VAA08879; Thu, 24 Dec 1998 21:21:52 -0500 (EST) Date: Thu, 24 Dec 1998 21:21:52 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: John Polstra cc: current@FreeBSD.ORG Subject: Re: make world breakage on alpha In-Reply-To: <199812250130.RAA00806@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 Thu, 24 Dec 1998, John Polstra wrote: > > > I seem to remember noises being made a while back that after 3.0 > > > got cut we'd upgrade binutils and gcc ... > > Actually, we're already current with GNU on binutils. We're not current enough to have the 3DNow! instructions in gas though, are we? Might be a nice thing before 3.0.1 to get in, along with the other K6-2-related patch I have that needs to get committed *ahem* :) > > 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 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 Thu Dec 24 18:47:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22845 for freebsd-current-outgoing; Thu, 24 Dec 1998 18:47: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 SAA22837 for ; Thu, 24 Dec 1998 18:47:02 -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 VAA09671 for ; Thu, 24 Dec 1998 21:46:56 -0500 (EST) Date: Thu, 24 Dec 1998 21:46:56 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: current@FreeBSD.ORG Subject: K6-2 (3?) CPU_WT_ALLOC Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-644874553-914554016=:9437" 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-644874553-914554016=:9437 Content-Type: TEXT/PLAIN; charset=US-ASCII CPU_WT_ALLOC does not work correctly for K6-2s of model 8+ and probably K6-3s (when they appear on the market soon). In addition, print_AMD_info() incorrectly printfs write allocation's size. I've fixed them, so they now Do The Right Thing, and added a "NO_MEMORY_HOLE" option to easily allow 15-16mb range handling for us K6 and K6-2 users. A patch follows in cleartext and encoded forms. Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ --- src/sys/i386/conf/options.i386.orig Wed Dec 23 20:36:45 1998 +++ src/sys/i386/conf/options.i386 Wed Dec 23 20:36:56 1998 @@ -57,6 +57,7 @@ CPU_WT_ALLOC opt_cpu.h CYRIX_CACHE_WORKS opt_cpu.h CYRIX_CACHE_REALLY_WORKS opt_cpu.h +NO_MEMORY_HOLE opt_cpu.h # The CPU type affects the endian conversion functions all over the kernel. I386_CPU opt_global.h --- src/sys/i386/i386/identcpu.c.orig Mon Dec 21 23:12:18 1998 +++ src/sys/i386/i386/identcpu.c Wed Dec 23 20:30:39 1998 @@ -68,6 +68,7 @@ #if defined(I586_CPU) && defined(CPU_WT_ALLOC) void enable_K5_wt_alloc(void); void enable_K6_wt_alloc(void); +void enable_K6_2_wt_alloc(void); #endif void panicifcpuunsupported(void); static void identifycyrix(void); @@ -291,9 +292,11 @@ if ((cpu_id & 0xf00) == 0x500) { if (((cpu_id & 0x0f0) > 0) && ((cpu_id & 0x0f0) < 0x60) - && ((cpu_id & 0x00f) > 3)) { + && ((cpu_id & 0x00f) > 3)) enable_K5_wt_alloc(); - } else if ((cpu_id & 0x0f0) > 0x50) + else if ((cpu_id & 0x0f0) > 0x70) + enable_K6_2_wt_alloc(); + else if ((cpu_id & 0x0f0) > 0x50) enable_K6_wt_alloc(); } #endif @@ -860,18 +863,28 @@ switch (cpu_id & 0xFF0) { case 0x560: /* K6 0.35u */ case 0x570: /* K6 0.25u */ - case 0x580: /* K6-2 */ - case 0x590: /* K6-3 */ amd_whcr = rdmsr(0xc0000082); if (!(amd_whcr & 0x00fe)) { printf("Write Allocate Disable\n"); } else { printf("Write Allocate Enable Limit: %dM bytes\n", - (u_int32_t)(amd_whcr & 0x00fe) * 2); + (u_int32_t)(amd_whcr & 0x00fe) * 4); printf("Write Allocate 15-16M bytes: %s\n", (amd_whcr & 0x0001) ? "Enable" : "Disable"); printf("Hardware Write Allocate Control: %s\n", (amd_whcr & 0x0100) ? "Enable" : "Disable"); + } + break; + case 0x580: /* K6-2 */ + case 0x590: /* K6-3 */ + amd_whcr = rdmsr(0xc0000082); + if (!(amd_whcr & (0x3ff << 22))) { + printf("Write Allocate Disable\n"); + } else { + printf("Write Allocate Enable Limit: %dM bytes\n", + (u_int32_t)((amd_whcr & (0x3ff << 22)) >> 22) * 4); + printf("Write Allocate 15-16M bytes: %s\n", + (amd_whcr & (1 << 16)) ? "Enable" : "Disable"); } break; } --- src/sys/i386/i386/initcpu.c.orig Mon Dec 21 23:01:26 1998 +++ src/sys/i386/i386/initcpu.c Wed Dec 23 19:53:10 1998 @@ -44,6 +44,7 @@ #if defined(I586_CPU) && defined(CPU_WT_ALLOC) void enable_K5_wt_alloc(void); void enable_K6_wt_alloc(void); +void enable_K6_2_wt_alloc(void); #endif #ifdef I486_CPU @@ -628,8 +629,9 @@ whcr &= ~0x00feLL; whcr |= (size << 1); -#ifdef PC98 +#if defined(PC98) || defined(NO_MEMORY_HOLE) if (whcr & 0x00feLL) { +#ifdef PC98 /* * If bit 2 of port 0x43b is 0, disable wrte allocate for the * 15-16M range. @@ -637,6 +639,7 @@ if (!(inb(0x43b) & 4)) whcr &= ~0x0001LL; else +#endif whcr |= 0x0001LL; } #else @@ -644,7 +647,68 @@ * There is no way to know wheter 15-16M hole exists or not. * Therefore, we disable write allocate for this range. */ - whcr &= 0x00feLL; + whcr &= ~0x0001LL; +#endif + wrmsr(0x0c0000082, whcr); + + write_eflags(eflags); + enable_intr(); +} + +void +enable_K6_2_wt_alloc(void) +{ + quad_t size; + u_int64_t whcr; + u_long eflags; + + eflags = read_eflags(); + disable_intr(); + wbinvd(); + +#ifdef CPU_DISABLE_CACHE + /* + * Certain K6-2 box becomes unstable when write allocation is + * enabled. + */ + /* + * The AMD-K6 processer provides the 64-bit Test Register 12(TR12), + * but only the Cache Inhibit(CI) (bit 3 of TR12) is suppported. + * All other bits in TR12 have no effect on the processer's operation. + * The I/O Trap Restart function (bit 9 of TR12) is always enabled + * on the AMD-K6. + */ + wrmsr(0x0000000e, (u_int64_t)0x0008); +#endif + /* Don't assume that memory size is aligned with 4M. */ + if (Maxmem > 0) + size = ((Maxmem >> 8) + 3) >> 2; + else + size = 0; + + /* Limit is 4092M bytes. */ + size &= 0x3ff; + whcr = (rdmsr(0xc0000082) & ~(0x3ffLL << 22)) | (size << 22); + +#if defined(PC98) || defined(NO_MEMORY_HOLE) + if (whcr & (0x3ffLL << 22)) { +#ifdef PC98 + /* + * If bit 2 of port 0x43b is 0, disable wrte allocate for the + * 15-16M range. + */ + if (!(inb(0x43b) & 4)) + whcr &= ~(1LL << 16); + else +#endif + whcr |= 1LL << 16; + } +#else + /* + * There is no way to know wheter 15-16M hole exists or not. + * Therefore, we disable write allocate for this range. + */ + whcr &= ~(1LL << 16); #endif wrmsr(0x0c0000082, whcr); --0-644874553-914554016=:9437 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="K6-2.patch" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="K6-2.patch" LS0tIHNyYy9zeXMvaTM4Ni9jb25mL29wdGlvbnMuaTM4Ni5vcmlnCVdlZCBE ZWMgMjMgMjA6MzY6NDUgMTk5OA0KKysrIHNyYy9zeXMvaTM4Ni9jb25mL29w dGlvbnMuaTM4NglXZWQgRGVjIDIzIDIwOjM2OjU2IDE5OTgNCkBAIC01Nyw2 ICs1Nyw3IEBADQogQ1BVX1dUX0FMTE9DCQkJb3B0X2NwdS5oDQogQ1lSSVhf Q0FDSEVfV09SS1MJCW9wdF9jcHUuaA0KIENZUklYX0NBQ0hFX1JFQUxMWV9X T1JLUwlvcHRfY3B1LmgNCitOT19NRU1PUllfSE9MRQkJCW9wdF9jcHUuaA0K IA0KICMgVGhlIENQVSB0eXBlIGFmZmVjdHMgdGhlIGVuZGlhbiBjb252ZXJz aW9uIGZ1bmN0aW9ucyBhbGwgb3ZlciB0aGUga2VybmVsLg0KIEkzODZfQ1BV CQlvcHRfZ2xvYmFsLmgNCi0tLSBzcmMvc3lzL2kzODYvaTM4Ni9pZGVudGNw dS5jLm9yaWcJTW9uIERlYyAyMSAyMzoxMjoxOCAxOTk4DQorKysgc3JjL3N5 cy9pMzg2L2kzODYvaWRlbnRjcHUuYwlXZWQgRGVjIDIzIDIwOjMwOjM5IDE5 OTgNCkBAIC02OCw2ICs2OCw3IEBADQogI2lmIGRlZmluZWQoSTU4Nl9DUFUp ICYmIGRlZmluZWQoQ1BVX1dUX0FMTE9DKQ0KIHZvaWQJZW5hYmxlX0s1X3d0 X2FsbG9jKHZvaWQpOw0KIHZvaWQJZW5hYmxlX0s2X3d0X2FsbG9jKHZvaWQp Ow0KK3ZvaWQJZW5hYmxlX0s2XzJfd3RfYWxsb2Modm9pZCk7DQogI2VuZGlm DQogdm9pZCBwYW5pY2lmY3B1dW5zdXBwb3J0ZWQodm9pZCk7DQogc3RhdGlj IHZvaWQgaWRlbnRpZnljeXJpeCh2b2lkKTsNCkBAIC0yOTEsOSArMjkyLDEx IEBADQogCQlpZiAoKGNwdV9pZCAmIDB4ZjAwKSA9PSAweDUwMCkgew0KIAkJ CWlmICgoKGNwdV9pZCAmIDB4MGYwKSA+IDApDQogCQkJICAgICYmICgoY3B1 X2lkICYgMHgwZjApIDwgMHg2MCkNCi0JCQkgICAgJiYgKChjcHVfaWQgJiAw eDAwZikgPiAzKSkgew0KKwkJCSAgICAmJiAoKGNwdV9pZCAmIDB4MDBmKSA+ IDMpKQ0KIAkJCQllbmFibGVfSzVfd3RfYWxsb2MoKTsNCi0JCQl9IGVsc2Ug aWYgKChjcHVfaWQgJiAweDBmMCkgPiAweDUwKQ0KKwkJCWVsc2UgaWYgKChj cHVfaWQgJiAweDBmMCkgPiAweDcwKQ0KKwkJCQllbmFibGVfSzZfMl93dF9h bGxvYygpOw0KKwkJCWVsc2UgaWYgKChjcHVfaWQgJiAweDBmMCkgPiAweDUw KQ0KIAkJCQllbmFibGVfSzZfd3RfYWxsb2MoKTsNCiAJCX0NCiAjZW5kaWYN CkBAIC04NjAsMTggKzg2MywyOCBAQA0KIAlzd2l0Y2ggKGNwdV9pZCAmIDB4 RkYwKSB7DQogCWNhc2UgMHg1NjA6CS8qIEs2IDAuMzV1ICovDQogCWNhc2Ug MHg1NzA6CS8qIEs2IDAuMjV1ICovDQotCWNhc2UgMHg1ODA6CS8qIEs2LTIg Ki8NCi0JY2FzZSAweDU5MDoJLyogSzYtMyAqLw0KIAkJYW1kX3doY3IgPSBy ZG1zcigweGMwMDAwMDgyKTsNCiAJCWlmICghKGFtZF93aGNyICYgMHgwMGZl KSkgew0KIAkJCXByaW50ZigiV3JpdGUgQWxsb2NhdGUgRGlzYWJsZVxuIik7 DQogCQl9IGVsc2Ugew0KIAkJCXByaW50ZigiV3JpdGUgQWxsb2NhdGUgRW5h YmxlIExpbWl0OiAlZE0gYnl0ZXNcbiIsDQotCQkJICAgICh1X2ludDMyX3Qp KGFtZF93aGNyICYgMHgwMGZlKSAqIDIpOw0KKwkJCSAgICAodV9pbnQzMl90 KShhbWRfd2hjciAmIDB4MDBmZSkgKiA0KTsNCiAJCQlwcmludGYoIldyaXRl IEFsbG9jYXRlIDE1LTE2TSBieXRlczogJXNcbiIsDQogCQkJICAgIChhbWRf d2hjciAmIDB4MDAwMSkgPyAiRW5hYmxlIiA6ICJEaXNhYmxlIik7DQogCQkJ cHJpbnRmKCJIYXJkd2FyZSBXcml0ZSBBbGxvY2F0ZSBDb250cm9sOiAlc1xu IiwNCiAJCQkgICAgKGFtZF93aGNyICYgMHgwMTAwKSA/ICJFbmFibGUiIDog IkRpc2FibGUiKTsNCisJCX0NCisJCWJyZWFrOw0KKwljYXNlIDB4NTgwOgkv KiBLNi0yICovDQorCWNhc2UgMHg1OTA6CS8qIEs2LTMgKi8NCisJCWFtZF93 aGNyID0gcmRtc3IoMHhjMDAwMDA4Mik7DQorCQlpZiAoIShhbWRfd2hjciAm ICgweDNmZiA8PCAyMikpKSB7DQorCQkJcHJpbnRmKCJXcml0ZSBBbGxvY2F0 ZSBEaXNhYmxlXG4iKTsNCisJCX0gZWxzZSB7DQorCQkJcHJpbnRmKCJXcml0 ZSBBbGxvY2F0ZSBFbmFibGUgTGltaXQ6ICVkTSBieXRlc1xuIiwNCisJCQkg ICAgKHVfaW50MzJfdCkoKGFtZF93aGNyICYgKDB4M2ZmIDw8IDIyKSkgPj4g MjIpICogNCk7DQorCQkJcHJpbnRmKCJXcml0ZSBBbGxvY2F0ZSAxNS0xNk0g Ynl0ZXM6ICVzXG4iLA0KKwkJCSAgICAoYW1kX3doY3IgJiAoMSA8PCAxNikp ID8gIkVuYWJsZSIgOiAiRGlzYWJsZSIpOw0KIAkJfQ0KIAkJYnJlYWs7DQog CX0NCi0tLSBzcmMvc3lzL2kzODYvaTM4Ni9pbml0Y3B1LmMub3JpZwlNb24g RGVjIDIxIDIzOjAxOjI2IDE5OTgNCisrKyBzcmMvc3lzL2kzODYvaTM4Ni9p bml0Y3B1LmMJV2VkIERlYyAyMyAxOTo1MzoxMCAxOTk4DQpAQCAtNDQsNiAr NDQsNyBAQA0KICNpZiBkZWZpbmVkKEk1ODZfQ1BVKSAmJiBkZWZpbmVkKENQ VV9XVF9BTExPQykNCiB2b2lkCWVuYWJsZV9LNV93dF9hbGxvYyh2b2lkKTsN CiB2b2lkCWVuYWJsZV9LNl93dF9hbGxvYyh2b2lkKTsNCit2b2lkCWVuYWJs ZV9LNl8yX3d0X2FsbG9jKHZvaWQpOw0KICNlbmRpZg0KIA0KICNpZmRlZiBJ NDg2X0NQVQ0KQEAgLTYyOCw4ICs2MjksOSBAQA0KIAl3aGNyICY9IH4weDAw ZmVMTDsNCiAJd2hjciB8PSAoc2l6ZSA8PCAxKTsNCiANCi0jaWZkZWYgUEM5 OA0KKyNpZiBkZWZpbmVkKFBDOTgpIHx8IGRlZmluZWQoTk9fTUVNT1JZX0hP TEUpDQogCWlmICh3aGNyICYgMHgwMGZlTEwpIHsNCisjaWZkZWYgUEM5OA0K IAkJLyoNCiAJCSAqIElmIGJpdCAyIG9mIHBvcnQgMHg0M2IgaXMgMCwgZGlz YWJsZSB3cnRlIGFsbG9jYXRlIGZvciB0aGUNCiAJCSAqIDE1LTE2TSByYW5n ZS4NCkBAIC02MzcsNiArNjM5LDcgQEANCiAJCWlmICghKGluYigweDQzYikg JiA0KSkNCiAJCQl3aGNyICY9IH4weDAwMDFMTDsNCiAJCWVsc2UNCisjZW5k aWYNCiAJCQl3aGNyIHw9ICAweDAwMDFMTDsNCiAJfQ0KICNlbHNlDQpAQCAt NjQ0LDcgKzY0Nyw2OCBAQA0KIAkgKiBUaGVyZSBpcyBubyB3YXkgdG8ga25v dyB3aGV0ZXIgMTUtMTZNIGhvbGUgZXhpc3RzIG9yIG5vdC4gDQogCSAqIFRo ZXJlZm9yZSwgd2UgZGlzYWJsZSB3cml0ZSBhbGxvY2F0ZSBmb3IgdGhpcyBy YW5nZS4NCiAJICovDQotCXdoY3IgJj0gMHgwMGZlTEw7DQorCXdoY3IgJj0g fjB4MDAwMUxMOw0KKyNlbmRpZg0KKwl3cm1zcigweDBjMDAwMDA4Miwgd2hj cik7DQorDQorCXdyaXRlX2VmbGFncyhlZmxhZ3MpOw0KKwllbmFibGVfaW50 cigpOw0KK30NCisNCit2b2lkDQorZW5hYmxlX0s2XzJfd3RfYWxsb2Modm9p ZCkNCit7DQorCXF1YWRfdAlzaXplOw0KKwl1X2ludDY0X3QJd2hjcjsNCisJ dV9sb25nCWVmbGFnczsNCisNCisJZWZsYWdzID0gcmVhZF9lZmxhZ3MoKTsN CisJZGlzYWJsZV9pbnRyKCk7DQorCXdiaW52ZCgpOw0KKw0KKyNpZmRlZiBD UFVfRElTQUJMRV9DQUNIRQ0KKwkvKg0KKwkgKiBDZXJ0YWluIEs2LTIgYm94 IGJlY29tZXMgdW5zdGFibGUgd2hlbiB3cml0ZSBhbGxvY2F0aW9uIGlzDQor CSAqIGVuYWJsZWQuDQorCSAqLw0KKwkvKg0KKwkgKiBUaGUgQU1ELUs2IHBy b2Nlc3NlciBwcm92aWRlcyB0aGUgNjQtYml0IFRlc3QgUmVnaXN0ZXIgMTIo VFIxMiksDQorCSAqIGJ1dCBvbmx5IHRoZSBDYWNoZSBJbmhpYml0KENJKSAo Yml0IDMgb2YgVFIxMikgaXMgc3VwcHBvcnRlZC4NCisJICogQWxsIG90aGVy IGJpdHMgaW4gVFIxMiBoYXZlIG5vIGVmZmVjdCBvbiB0aGUgcHJvY2Vzc2Vy J3Mgb3BlcmF0aW9uLg0KKwkgKiBUaGUgSS9PIFRyYXAgUmVzdGFydCBmdW5j dGlvbiAoYml0IDkgb2YgVFIxMikgaXMgYWx3YXlzIGVuYWJsZWQNCisJICog b24gdGhlIEFNRC1LNi4NCisJICovDQorCXdybXNyKDB4MDAwMDAwMGUsICh1 X2ludDY0X3QpMHgwMDA4KTsNCisjZW5kaWYNCisJLyogRG9uJ3QgYXNzdW1l IHRoYXQgbWVtb3J5IHNpemUgaXMgYWxpZ25lZCB3aXRoIDRNLiAqLw0KKwlp ZiAoTWF4bWVtID4gMCkNCisJICBzaXplID0gKChNYXhtZW0gPj4gOCkgKyAz KSA+PiAyOw0KKwllbHNlDQorCSAgc2l6ZSA9IDA7DQorDQorCS8qIExpbWl0 IGlzIDQwOTJNIGJ5dGVzLiAqLw0KKwlzaXplICY9IDB4M2ZmOw0KKwl3aGNy ID0gKHJkbXNyKDB4YzAwMDAwODIpICYgfigweDNmZkxMIDw8IDIyKSkgfCAo c2l6ZSA8PCAyMik7DQorDQorI2lmIGRlZmluZWQoUEM5OCkgfHwgZGVmaW5l ZChOT19NRU1PUllfSE9MRSkNCisJaWYgKHdoY3IgJiAoMHgzZmZMTCA8PCAy MikpIHsNCisjaWZkZWYgUEM5OA0KKwkJLyoNCisJCSAqIElmIGJpdCAyIG9m IHBvcnQgMHg0M2IgaXMgMCwgZGlzYWJsZSB3cnRlIGFsbG9jYXRlIGZvciB0 aGUNCisJCSAqIDE1LTE2TSByYW5nZS4NCisJCSAqLw0KKwkJaWYgKCEoaW5i KDB4NDNiKSAmIDQpKQ0KKwkJCXdoY3IgJj0gfigxTEwgPDwgMTYpOw0KKwkJ ZWxzZQ0KKyNlbmRpZg0KKwkJCXdoY3IgfD0gIDFMTCA8PCAxNjsNCisJfQ0K KyNlbHNlDQorCS8qDQorCSAqIFRoZXJlIGlzIG5vIHdheSB0byBrbm93IHdo ZXRlciAxNS0xNk0gaG9sZSBleGlzdHMgb3Igbm90LiANCisJICogVGhlcmVm b3JlLCB3ZSBkaXNhYmxlIHdyaXRlIGFsbG9jYXRlIGZvciB0aGlzIHJhbmdl Lg0KKwkgKi8NCisJd2hjciAmPSB+KDFMTCA8PCAxNik7DQogI2VuZGlmDQog CXdybXNyKDB4MGMwMDAwMDgyLCB3aGNyKTsNCiANCg== --0-644874553-914554016=:9437-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 24 19:15:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA25129 for freebsd-current-outgoing; Thu, 24 Dec 1998 19:15:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from blkbox.com (blkbox.com [206.109.97.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA25124 for ; Thu, 24 Dec 1998 19:15:51 -0800 (PST) (envelope-from phil@blkbox.com) Received: from localhost (phil@localhost) by blkbox.com (8.8.7/8.8.7) with SMTP id VAA25029 for ; Thu, 24 Dec 1998 21:15:37 -0600 (CST) Date: Thu, 24 Dec 1998 21:15:37 -0600 (CST) From: Phil Priest cc: current@FreeBSD.ORG Subject: buslogic 958 controller In-Reply-To: <199812250130.RAA00806@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 is the buslogic 958 supported in freebsd? -phil To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 24 20:48:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA01476 for freebsd-current-outgoing; Thu, 24 Dec 1998 20:48:08 -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 UAA01466 for ; Thu, 24 Dec 1998 20:48:06 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id VAA11952; Thu, 24 Dec 1998 21:47:46 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812250447.VAA11952@panzer.plutotech.com> Subject: Re: buslogic 958 controller In-Reply-To: from Phil Priest at "Dec 24, 98 09:15:37 pm" To: phil@blkbox.com (Phil Priest) Date: Thu, 24 Dec 1998 21:47:46 -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 Phil Priest wrote... > is the buslogic 958 supported in freebsd? > Yes, it's supported in both the 2.2.x releases and 3.x. 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 Dec 24 21:38:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06057 for freebsd-current-outgoing; Thu, 24 Dec 1998 21:38:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (pm3-4.ppp.wenet.net [206.15.85.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA06050 for ; Thu, 24 Dec 1998 21:38:55 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.9.1/8.8.8) with ESMTP id VAA01018; Thu, 24 Dec 1998 21:41:25 -0800 (PST) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Thu, 24 Dec 1998 21:41:25 -0800 (PST) From: Alex Zepeda X-Sender: garbanzo@zippy.dyn.ml.org To: "David O'Brien" cc: current Subject: Re: Q: -DNOLIBG++ howto? In-Reply-To: <19981224140837.A10869@nuxi.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, 24 Dec 1998, David O'Brien wrote: > WHY would you even try to compile libg++? What is in contrib/libg++ is > part of EGCS. *IF* EGCS were to become the base compiler, > contrib-/libg++ will be removed. Well if you're using a non egcs compat. compiler, or perhaps he's working on this before a newer compiler is integrated. Sheesh. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 24 21:52:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA07439 for freebsd-current-outgoing; Thu, 24 Dec 1998 21:52:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shell2.la.best.com (shell2.la.best.com [209.24.216.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA07434 for ; Thu, 24 Dec 1998 21:52:54 -0800 (PST) (envelope-from nugundam@shell2.la.best.com) Received: (from nugundam@localhost) by shell2.la.best.com (8.9.1/8.9.0/best.sh) id VAA17456 for current@FreeBSD.ORG; Thu, 24 Dec 1998 21:51:53 -0800 (PST) Message-ID: <19981224215153.A17337@la.best.com> Date: Thu, 24 Dec 1998 21:51:53 -0800 From: "Joseph T. Lee" To: current@FreeBSD.ORG Subject: Re: Problem with newsyslog: preposterous process number. References: <199812222111.WAA06117@daneel.stuyts.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812222111.WAA06117@daneel.stuyts.nl>; from Ben Stuyts on Tue, Dec 22, 1998 at 10:11:13PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 22, 1998 at 10:11:13PM +0100, Ben Stuyts wrote: > newsyslog: preposterous process number: 35655 > newsyslog: log not compressed because daemon not notified There is a PR on this. It seems to be a simple fix, but it doesn't seem like anybody had had time to get around to it yet. Hopefully soon though.. :) -- Joseph nugundam =best=com==/==\=IIGS=/==\=Playstation=/==\=Civic HX CVT=/==\ # Anime Expo 1998 >> www.anime-expo.org/ > # Redline Games >> www.redlinegames.com/ > # Cal-Animage Epsilon >> www.best.com/~nugundam/epsilon/ > # EX: The Online World of Anime & Manga >> www.ex.org/ / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 24 21:57:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA08034 for freebsd-current-outgoing; Thu, 24 Dec 1998 21:57:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shell2.la.best.com (shell2.la.best.com [209.24.216.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA08029 for ; Thu, 24 Dec 1998 21:57:54 -0800 (PST) (envelope-from nugundam@shell2.la.best.com) Received: (from nugundam@localhost) by shell2.la.best.com (8.9.1/8.9.0/best.sh) id VAA17547; Thu, 24 Dec 1998 21:57:08 -0800 (PST) Message-ID: <19981224215708.B17337@la.best.com> Date: Thu, 24 Dec 1998 21:57:08 -0800 From: "Joseph T. Lee" To: freebsd-current@FreeBSD.ORG Cc: freebsd-current@FreeBSD.ORG Subject: Re: Problems compiling kernel for 3.0-19980804-SNAP system References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Alfred Perlstein on Wed, Dec 23, 1998 at 11:29:14AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 23, 1998 at 11:29:14AM -0500, Alfred Perlstein wrote: > > cc1: Invalid option `-fformat-extensions' > > *** Error code 1 > > > > What do I look for to make this work? > > I think you have /usr/local/bin in your path before /usr/bin and therefore > are running egcs. Breaks on gcc2.8.1 also. None of the man files describes this extension though.. Maybe not necessary anymore for the new compilers? -- Joseph nugundam =best=com==/==\=IIGS=/==\=Playstation=/==\=Civic HX CVT=/==\ # Anime Expo 1998 >> www.anime-expo.org/ > # Redline Games >> www.redlinegames.com/ > # Cal-Animage Epsilon >> www.best.com/~nugundam/epsilon/ > # EX: The Online World of Anime & Manga >> www.ex.org/ / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 24 23:02:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA12978 for freebsd-current-outgoing; Thu, 24 Dec 1998 23:02: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 XAA12972 for ; Thu, 24 Dec 1998 23:02:04 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id XAA23992; Thu, 24 Dec 1998 23:01:44 -0800 (PST) (envelope-from dillon) Date: Thu, 24 Dec 1998 23:01:44 -0800 (PST) From: Matthew Dillon Message-Id: <199812250701.XAA23992@apollo.backplane.com> To: "Joseph T. Lee" Cc: current@FreeBSD.ORG Subject: Re: Problem with newsyslog: preposterous process number. References: <199812222111.WAA06117@daneel.stuyts.nl> <19981224215153.A17337@la.best.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> newsyslog: preposterous process number: 35655 :> newsyslog: log not compressed because daemon not notified : :There is a PR on this. It seems to be a simple fix, but it doesn't :seem like anybody had had time to get around to it yet. : :Hopefully soon though.. :) :Joseph nugundam =best=com==/==\=IIGS=/==\=Playstation=/==\=Civic HX CVT=/==\ Peter fixed it. -Matt ---------------------------- revision 1.21 date: 1998/12/23 12:03:33; author: peter; state: Exp; lines: +2 -2 The largest PID is now 99999 Reported by: Ben Stuyts ---------------------------- Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 24 23:38:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA15177 for freebsd-current-outgoing; Thu, 24 Dec 1998 23:38:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (tibet-56.ppp.hooked.net [206.80.9.184]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA15151 for ; Thu, 24 Dec 1998 23:37:59 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.9.1/8.8.8) with ESMTP id XAA01184; Thu, 24 Dec 1998 23:40:40 -0800 (PST) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Thu, 24 Dec 1998 23:40:39 -0800 (PST) From: Alex Zepeda X-Sender: garbanzo@zippy.dyn.ml.org To: "Joseph T. Lee" cc: freebsd-current@FreeBSD.ORG Subject: Re: Problems compiling kernel for 3.0-19980804-SNAP system In-Reply-To: <19981224215708.B17337@la.best.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, 24 Dec 1998, Joseph T. Lee wrote: > On Wed, Dec 23, 1998 at 11:29:14AM -0500, Alfred Perlstein wrote: > > > cc1: Invalid option `-fformat-extensions' > > > *** Error code 1 > > > > > > What do I look for to make this work? > > > > I think you have /usr/local/bin in your path before /usr/bin and therefore > > are running egcs. > > Breaks on gcc2.8.1 also. None of the man files describes this extension > though.. Maybe not necessary anymore for the new compilers? -fformat-extensions is a FreeBSDism, and so on a "stock" gcc of any version it is an invalid option. You can remove it, but then gcc won't recognize any of the odd format identifiers that are used in the kernel, and might generate warnings. - 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 Fri Dec 25 00:02:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA17048 for freebsd-current-outgoing; Fri, 25 Dec 1998 00:02:55 -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 AAA17043 for ; Fri, 25 Dec 1998 00:02:53 -0800 (PST) (envelope-from obrien@nuxi.ucdavis.edu) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id AAA12482; Fri, 25 Dec 1998 00:02:39 -0800 (PST) (envelope-from obrien) Message-ID: <19981225000239.A12470@nuxi.com> Date: Fri, 25 Dec 1998 00:02:39 -0800 From: "David O'Brien" To: Alex Zepeda Cc: current Subject: Re: Q: -DNOLIBG++ howto? Reply-To: obrien@FreeBSD.ORG References: <19981224140837.A10869@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Alex Zepeda on Thu, Dec 24, 1998 at 09:41:25PM -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 > > WHY would you even try to compile libg++? What is in contrib/libg++ is > > part of EGCS. *IF* EGCS were to become the base compiler, > > contrib-/libg++ will be removed. > > Well if you're using a non egcs compat. compiler, or perhaps he's working > on this before a newer compiler is integrated. Sheesh. Since you have such a good grasp of the situation, would you care to answer the original question? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 25 02:10:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA24178 for freebsd-current-outgoing; Fri, 25 Dec 1998 02:10:59 -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 CAA24173 for ; Fri, 25 Dec 1998 02:10:55 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id TAA27184; Fri, 25 Dec 1998 19:10:30 +0900 (JST) Message-ID: <368364F0.1111461F@newsguy.com> Date: Fri, 25 Dec 1998 19:12:00 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: obrien@nuxi.ucdavis.edu CC: "Arno J. Klaassen" , current@FreeBSD.ORG Subject: Re: Q: -DNOLIBG++ howto? References: <19981224140837.A10869@nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: > > > Could someone eventually indicate me which files to alter to: > > - not build contrib/libg++ > > WHY would you even try to compile libg++? What is in contrib/libg++ is > part of EGCS. *IF* EGCS were to become the base compiler, > contrib-/libg++ will be removed. > > Hack your /usr/src/*/Makefile's to skip this building step. > > > - not add -I/usr/obj//src/tmp/usr/include/g++ to the include paths > > Hack the Makefile's. > > > - take away dependencies for g++-include and libg++* > > ditto. It is my understanding he wanted to know which makefiles (and other files) he needed to change to accomplish all of the above. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com "Heart like a Gabriel, pure and white as ivory, soul like a lucifer, black and cold as a piece of lead." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 25 02:40:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA26485 for freebsd-current-outgoing; Fri, 25 Dec 1998 02:40: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 CAA26480 for ; Fri, 25 Dec 1998 02:40: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 KAA09120; Fri, 25 Dec 1998 10:39:34 GMT Date: Fri, 25 Dec 1998 10:39:34 +0000 (GMT) From: Doug Rabson To: Brian Feldman cc: John Polstra , current@FreeBSD.ORG Subject: Re: make world breakage on alpha 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, 24 Dec 1998, Brian Feldman wrote: > On Thu, 24 Dec 1998, John Polstra wrote: > > > > > I seem to remember noises being made a while back that after 3.0 > > > > got cut we'd upgrade binutils and gcc ... > > > > Actually, we're already current with GNU on binutils. > > We're not current enough to have the 3DNow! instructions in gas > though, are we? Might be a nice thing before 3.0.1 to get in, along > with the other K6-2-related patch I have that needs to get committed > *ahem* :) We have the latest full release version of binutils. I don't know what unreleased beta version of binutils the Linux folks have access to. -- 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 Dec 25 02:47:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA27005 for freebsd-current-outgoing; Fri, 25 Dec 1998 02:47:18 -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 CAA26994 for ; Fri, 25 Dec 1998 02:47:15 -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 VAA29549; Fri, 25 Dec 1998 21:47:00 +1100 Date: Fri, 25 Dec 1998 21:47:00 +1100 From: Bruce Evans Message-Id: <199812251047.VAA29549@godzilla.zeta.org.au> To: current@FreeBSD.ORG, green@unixhelp.org Subject: Re: revoke of fifos Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >revoke(2) on VFIFO types is broken now, leading to stranded mbuf's. I suppose I don't think it has ever worked in BSD. >bde is tracking this down, but for now, why don't we return EINVAL in revoke(2)? I thought it wasn't urgent because I thought that only root could revoke :-(. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 25 03:18:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA28749 for freebsd-current-outgoing; Fri, 25 Dec 1998 03:18:07 -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 DAA28732 for ; Fri, 25 Dec 1998 03:18:04 -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 WAA31256; Fri, 25 Dec 1998 22:17:50 +1100 Date: Fri, 25 Dec 1998 22:17:50 +1100 From: Bruce Evans Message-Id: <199812251117.WAA31256@godzilla.zeta.org.au> To: jdp@polstra.com, mike@smith.net.au Subject: Re: trap 12 with interrupts disabled Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> > If my page fault fails because I've blocked the interrupt, I'd expect >> > some serious damage to happen to the process environment.n >> >> Usually you're lucky and something else turns them on unconditionally. >> This test simply makes damn sure that if you take a fault interrupts >> get turned back on. > >I'm still not entirely clear about the implications of this change. >If I understand it right, the message is caused by a bug in Xaccel. Right. >.. >Do the interrupts get turned back off again when control returns to >Xaccel, or do they remain on? If Xaccel is assuming they're off, it >seems bad to turn them on underfoot. They get turned back off, but this might not help because control might not be returned to for Xaccel a long time. E.g., the kernel might decide to run 10 other processes for 100 msec each before returning to Xaccel. This might break whatever timing requirements Xaccel is attempting to meet by turning off interrupts. Before the change, the following could happen: 1) Benign case: the pagefault handler finds the page in the cache and completes fairly fast (< about 100 usec). 2) The pagefault handler runs for a long time without blocking. This causes slow response to interrupts. "A long time" can apparently be several 10's of msec so that clock interrupts are lost. I don't know how it can be so long (perhaps it is all in the application). 3) The pagefault handler blocks. Then interrupts are turned on underfoot when another process or idle() is run. Interrupts are "known" to be on already, and their state is "restored" to on when the blocked process is restarted in the kernel. They get turned back off when the process leaves the kernel. 4) The pagefault handler happens to calls something that "knows" that interrupts are on and "restores" their state to on after turning them off. This is essentially the same as the current behaviour. I'm not sure if it actually occurred. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 25 04:20:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA04226 for freebsd-current-outgoing; Fri, 25 Dec 1998 04:20:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebsd.dk (sos.freebsd.dk [212.242.42.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA04220 for ; Fri, 25 Dec 1998 04:20:15 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id NAA04572; Fri, 25 Dec 1998 13:19:30 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199812251219.NAA04572@freebsd.dk> Subject: Re: future of syscons In-Reply-To: <86soe5ic3z.fsf@detlev.UUCP> from Joel Ray Holveck at "Dec 24, 1998 1:17: 4 pm" To: joelh@gnu.org (Joel Ray Holveck) Date: Fri, 25 Dec 1998 13:19:30 +0100 (CET) Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp, hm@hcs.de, mike@smith.net.au, 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 Joel Ray Holveck wrote: > >> Not much has been designed or decided about terminal emulation code > >> yet. I have just a vague idea that the terminal emulator code shall > >> write to the vty's internal buffer, rather than directly to the > >> screen, and a timer routine will periodically render it to screen. > > Thats how it allready works, updating the HWscreen is totally decoupled > > from the actual SWscreen buffer. Its only a matter of seperating the > > decode of ESC something chars into a module that then can be loaded > > with the required emulation functionality. Leave the simple ones > > (backspace, enter, etc) in the main code, and let the rest be handeled > > seperately. That way one can also have a very minimalistic console > > for X only workstations. > > So do I hear a volounteer to write a generic VTXXX emulator ?? > > Can you describe a little more what you mean by "a generic VTxxx > emulator"? This may be an interesting project. For all its worth, an emulator thats compatible with what pcvt does today (vt220??), and maybe extended to support vt320 or whatever they arrived at in that camp. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@freebsd.org) FreeBSD Core Team member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 25 04:36:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA05244 for freebsd-current-outgoing; Fri, 25 Dec 1998 04:36:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from asteroid.svib.ru (asteroid.svib.ru [195.151.166.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA05238 for ; Fri, 25 Dec 1998 04:36:49 -0800 (PST) (envelope-from tarkhil@asteroid.svib.ru) Received: from minas-tirith.pol.ru (shuttle.svib.ru [195.151.166.144]) by asteroid.svib.ru (8.9.1a/8.9.1) with ESMTP id PAA04451 for ; Fri, 25 Dec 1998 15:36:27 +0300 (MSK) Received: from minas-tirith.pol.ru (minas-tirith.pol.ru [127.0.0.1]) by minas-tirith.pol.ru (8.9.1/8.8.7) with ESMTP id PAA03619 for ; Fri, 25 Dec 1998 15:36:33 +0300 (MSK) (envelope-from tarkhil@minas-tirith.pol.ru) Message-Id: <199812251236.PAA03619@minas-tirith.pol.ru> To: current@FreeBSD.ORG Reply-To: tarkhil@asteroid.svib.ru Subject: Install on 486SX X-URL: http://freebsd.svib.ru Date: Fri, 25 Dec 1998 15:36:33 +0300 From: Alex Povolotsky Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I am trying to install 3.0-RELEASE on 486SX, and it hangs on "probing devices"... Can it be because of lack of math emulator in install kernel? Alex. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 25 04:55:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA05895 for freebsd-current-outgoing; Fri, 25 Dec 1998 04:55:34 -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 EAA05890 for ; Fri, 25 Dec 1998 04:55: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 HAA27021; Fri, 25 Dec 1998 07:55:16 -0500 (EST) Date: Fri, 25 Dec 1998 07:55:16 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Doug Rabson cc: John Polstra , current@FreeBSD.ORG Subject: Re: make world breakage on alpha 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, 25 Dec 1998, Doug Rabson wrote: > On Thu, 24 Dec 1998, Brian Feldman wrote: > > > On Thu, 24 Dec 1998, John Polstra wrote: > > > > > > > I seem to remember noises being made a while back that after 3.0 > > > > > got cut we'd upgrade binutils and gcc ... > > > > > > Actually, we're already current with GNU on binutils. > > > > We're not current enough to have the 3DNow! instructions in gas > > though, are we? Might be a nice thing before 3.0.1 to get in, along > > with the other K6-2-related patch I have that needs to get committed > > *ahem* :) > > We have the latest full release version of binutils. I don't know what > unreleased beta version of binutils the Linux folks have access to. > At http://metalab.unc.edu/pub/Linux/GCC/ it seems the latest release is 2.9.1.0.19a. > -- > Doug Rabson Mail: dfr@nlsystems.com > Nonlinear Systems Ltd. Phone: +44 181 442 9037 > > > 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 Dec 25 04:58:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA06246 for freebsd-current-outgoing; Fri, 25 Dec 1998 04:58:14 -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 EAA06241 for ; Fri, 25 Dec 1998 04:58:12 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id MAA12801; Fri, 25 Dec 1998 12:57:56 GMT Date: Fri, 25 Dec 1998 12:57:56 +0000 (GMT) From: Doug Rabson To: Brian Feldman cc: John Polstra , current@FreeBSD.ORG Subject: Re: make world breakage on alpha 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, 25 Dec 1998, Brian Feldman wrote: > On Fri, 25 Dec 1998, Doug Rabson wrote: > > > On Thu, 24 Dec 1998, Brian Feldman wrote: > > > > > On Thu, 24 Dec 1998, John Polstra wrote: > > > > > > > > > I seem to remember noises being made a while back that after 3.0 > > > > > > got cut we'd upgrade binutils and gcc ... > > > > > > > > Actually, we're already current with GNU on binutils. > > > > > > We're not current enough to have the 3DNow! instructions in gas > > > though, are we? Might be a nice thing before 3.0.1 to get in, along > > > with the other K6-2-related patch I have that needs to get committed > > > *ahem* :) > > > > We have the latest full release version of binutils. I don't know what > > unreleased beta version of binutils the Linux folks have access to. > > > > At http://metalab.unc.edu/pub/Linux/GCC/ it seems the latest release is > 2.9.1.0.19a. Hmm. Smells like an alpha release. Does anyone know when 2.9.2 is scheduled? -- 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 Dec 25 08:20:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16404 for freebsd-current-outgoing; Fri, 25 Dec 1998 08:20:48 -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 IAA16399 for ; Fri, 25 Dec 1998 08:20:47 -0800 (PST) (envelope-from obrien@nuxi.ucdavis.edu) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id IAA13725; Fri, 25 Dec 1998 08:20:26 -0800 (PST) (envelope-from obrien) Message-ID: <19981225082026.A13703@nuxi.com> Date: Fri, 25 Dec 1998 08:20:26 -0800 From: "David O'Brien" To: "Daniel C. Sobral" Cc: "Arno J. Klaassen" , current@FreeBSD.ORG Subject: Re: Q: -DNOLIBG++ howto? Reply-To: obrien@FreeBSD.ORG References: <19981224140837.A10869@nuxi.com> <368364F0.1111461F@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <368364F0.1111461F@newsguy.com>; from Daniel C. Sobral on Fri, Dec 25, 1998 at 07:12:00PM +0900 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 > It is my understanding he wanted to know which makefiles (and other > files) he needed to change to accomplish all of the above. UTSL. $ cd /usr/src $ find . -name Makefile\* | xargs grep g++ $ find . -name Makefile\* | xargs grep c++ $ cd /usr/src/share/mk ; grep g++ you will get a find listing of files. All of these need to be patched up. -- -- David (obrien@NUXI.ucdavis.edu -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 Fri Dec 25 08:38:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA17224 for freebsd-current-outgoing; Fri, 25 Dec 1998 08:38:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA17219 for ; Fri, 25 Dec 1998 08:38:11 -0800 (PST) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id RAA12040; Fri, 25 Dec 1998 17:36:23 +0100 (MET) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.9.1/8.8.8) with ESMTP id RAA12096; Fri, 25 Dec 1998 17:25:06 +0100 (CET) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199812251625.RAA12096@semyam.dinoco.de> To: "Erik Funkenbusch" cc: freebsd-current@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: Re: Broken ipfw? In-reply-to: Your message of "Mon, 21 Dec 1998 11:47:15 CST." <003901be2d0a$6da7f800$0200a8c0@mn.mediaone.net> Date: Fri, 25 Dec 1998 17:25:05 +0100 From: Stefan Eggers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > After cvsuping on saturday natd has suddenly stopped working with the kernel > I built on saturday and after cvsuping today and rebuilding as well. > > After executing an ipfw rule it responds with: > > ip_fw_ctl: empty interface name > /sbin/ipfw: setsockopt(IP_FW_ADD): Invalid Argument Using a kernel module for ipfw? I used it preloaded by /boot/loader and with a world (and kernel, of course) from last weekend the kernel did see there was a preloaded ELF module but it never got integrated into the system - ipfw's initial message during startup was missing and I had a similar problem. The result was a kernel without working ipfw. See PR kern/9178. If anybody needs more details for this I can easily reproduce the problem. I still have a kernel w/o ipfw and could test it. > Any ideas? I'm planning on rebuilding world to see if it was some fix to > both kernel and natd, but I can't seem to find anything in the cvs list that Adding IPFW to the kernel instead of using a module is what I'd suggest to try. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 25 10:35:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA26156 for freebsd-current-outgoing; Fri, 25 Dec 1998 10:35:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ha1.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA26151 for ; Fri, 25 Dec 1998 10:35:53 -0800 (PST) (envelope-from ric@home.com) Received: from C870318-a ([24.2.138.46]) by ha1.rdc1.ct.home.com (Netscape Mail Server v2.02) with SMTP id AAA5645; Fri, 25 Dec 1998 10:35:39 -0800 Message-Id: <3.0.5.32.19981225133150.007ebd00@mail> X-Sender: ric@mail X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Fri, 25 Dec 1998 13:31:50 -0500 To: tarkhil@asteroid.svib.ru, current@FreeBSD.ORG From: Rick Subject: Re: Install on 486SX In-Reply-To: <199812251236.PAA03619@minas-tirith.pol.ru> 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 a 3Com 3C509B Card in your Machine? it dosent like to be probed. At 03:36 PM 12/25/98 +0300, Alex Povolotsky wrote: >Hello! > >I am trying to install 3.0-RELEASE on 486SX, and it hangs on "probing >devices"... > >Can it be because of lack of math emulator in install kernel? > >Alex. > >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 Dec 25 12:31:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01787 for freebsd-current-outgoing; Fri, 25 Dec 1998 12:31:26 -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 MAA01782 for ; Fri, 25 Dec 1998 12:31:24 -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 MAA11806; Fri, 25 Dec 1998 12:31:02 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id MAA01875; Fri, 25 Dec 1998 12:31:00 -0800 (PST) (envelope-from jdp@polstra.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 In-Reply-To: Date: Fri, 25 Dec 1998 12:30:59 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Brian Feldman Subject: Re: make world breakage on alpha Cc: current@FreeBSD.ORG, Doug Rabson Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 25-Dec-98 Brian Feldman wrote: >> We have the latest full release version of binutils. I don't know what >> unreleased beta version of binutils the Linux folks have access to. > > At http://metalab.unc.edu/pub/Linux/GCC/ it seems the latest release is > 2.9.1.0.19a. No thanks. I'm on their mailing list, and they come out with a flurry of new releases every month or so. A good many of them are to fix last-minute botches in their earlier releases. We're not going down that path if I have anything to say about it. 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 Dec 25 12:35:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA02138 for freebsd-current-outgoing; Fri, 25 Dec 1998 12:35:49 -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 MAA02133 for ; Fri, 25 Dec 1998 12:35:48 -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 PAA17157; Fri, 25 Dec 1998 15:35:09 -0500 (EST) Message-ID: <19981225153509.S1333@ns1.adsu.bellsouth.com> Date: Fri, 25 Dec 1998 15:35:09 -0500 From: Christian Kuhtz To: John Polstra , Brian Feldman Cc: current@FreeBSD.ORG, Doug Rabson Subject: Re: make world breakage on alpha References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from John Polstra on Fri, Dec 25, 1998 at 12:30:59PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 25, 1998 at 12:30:59PM -0800, John Polstra wrote: > > At http://metalab.unc.edu/pub/Linux/GCC/ it seems the latest release is > > 2.9.1.0.19a. > > No thanks. I'm on their mailing list, and they come out with a flurry > of new releases every month or so. A good many of them are to fix > last-minute botches in their earlier releases. We're not going down > that path if I have anything to say about it. I couldn't agree more. One of the worst irritating things about Linux is the flurry of new releases. It is the very reason why I use FreeBSD for production purposes. Thanks, Chris -- Frisbeetarianism, n.: The belief that when you die, your soul goes up on the roof and gets stuck. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 25 17:01:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA18799 for freebsd-current-outgoing; Fri, 25 Dec 1998 17:01:45 -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 RAA18794 for ; Fri, 25 Dec 1998 17:01:43 -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 UAA04677 for ; Fri, 25 Dec 1998 20:03:45 -0500 (EST) Received: (from shmit@localhost) by natasya.noc.erols.net (8.9.1/8.9.1) id UAA14488 for current@freebsd.org; Fri, 25 Dec 1998 20:01:28 -0500 (EST) Message-ID: <19981225200128.R21819@kublai.com> Date: Fri, 25 Dec 1998 20:01:28 -0500 From: Brian Cully To: current@FreeBSD.ORG Subject: Make installworld hangs Reply-To: shmit@kublai.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i 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 My installworld is hanging at: natasya:/usr/src# make installworld cd /usr/src; PATH=/usr/obj/elf/usr/src/tmp/sbin:/usr/obj/elf/usr/src/tmp/usr/sbin:/usr/obj/elf/usr/src/tmp/bin:/usr/obj/elf/usr/src/tmp/usr/bin BISON_SIMPLE=/usr/obj/elf/usr/src/tmp/usr/share/misc/bison.simple COMPILER_PATH=/usr/obj/elf/usr/src/tmp/usr/libexec:/usr/obj/elf/usr/src/tmp/usr/bin GCC_EXEC_PREFIX=/usr/obj/elf/usr/src/tmp/usr/lib:/usr/obj/elf/usr/src/tmp/usr/lib/ LD_LIBRARY_PATH=/usr/obj/elf/usr/src/tmp/usr/lib LIBRARY_PATH=/usr/obj/elf/usr/src/tmp/usr/lib:/usr/obj/elf/usr/src/tmp/usr/lib OBJFORMAT_PATH=/usr/obj/elf/usr/src/tmp/usr/libexec CFLAGS="-nostdinc -O2 -pipe" /usr/obj/elf/usr/src/tmp/usr/bin/make -f Makefile.inc1 reinstall -------------------------------------------------------------- >>> Making hierarchy -------------------------------------------------------------- cd /usr/src; /usr/obj/elf/usr/src/tmp/usr/bin/make -f Makefile.inc1 hierarchy cd /usr/src/etc; /usr/obj/elf/usr/src/tmp/usr/bin/make distrib-dirs mtree -deU -f /usr/src/etc/mtree/BSD.root.dist -p / -- Brian Cully You think you're queer? I'll tell you something: we're all queer. If you get befuddled by a middle class morality, get shut of it. Shut it out.... Is there an absolute morality? I don't think so. You think that? Act that way. -- Glengarry Glen Ross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 25 17:42:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA21293 for freebsd-current-outgoing; Fri, 25 Dec 1998 17:42:31 -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 RAA21288 for ; Fri, 25 Dec 1998 17:42:30 -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 UAA07172; Fri, 25 Dec 1998 20:45:51 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Fri, 25 Dec 1998 20:45:50 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Rick cc: tarkhil@asteroid.svib.ru, current@FreeBSD.ORG Subject: Re: Install on 486SX In-Reply-To: <3.0.5.32.19981225133150.007ebd00@mail> 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, 25 Dec 1998, Rick wrote: > At 03:36 PM 12/25/98 +0300, Alex Povolotsky wrote: > >Hello! > > > >I am trying to install 3.0-RELEASE on 486SX, and it hangs on "probing > >devices"... > > > >Can it be because of lack of math emulator in install kernel? > > > Do You have a 3Com 3C509B Card in your Machine? it dosent like to be probed. afaik 3.0-current boot.flp hasn't had the GPL'd math emulator in it for several months. you may want to try building a PICO-BSD kernel with the emulator in it to verify that it's just the missing emulator. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 25 19:00:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA25623 for freebsd-current-outgoing; Fri, 25 Dec 1998 19:00:44 -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 TAA25617 for ; Fri, 25 Dec 1998 19:00: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 WAA24454; Fri, 25 Dec 1998 22:00:24 -0500 (EST) Date: Fri, 25 Dec 1998 22:00:24 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Bruce Evans cc: current@FreeBSD.ORG Subject: Re: revoke of fifos In-Reply-To: <199812251047.VAA29549@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 Fri, 25 Dec 1998, Bruce Evans wrote: > >revoke(2) on VFIFO types is broken now, leading to stranded mbuf's. I suppose > > I don't think it has ever worked in BSD. Nor should it need to since, according to revoke.2: Access to a file may be revoked only by its owner or the super user. The revoke() function is currently supported only for block and character special device files. > > >bde is tracking this down, but for now, why don't we return EINVAL in revoke(2)? > > I thought it wasn't urgent because I thought that only root could revoke :-(. Nope. Also, to keep in accordance with the manpage, look at the code in -STABLE, which actually seems to be correct: vp = nd.ni_vp; if (vp->v_type != VCHR && vp->v_type != VBLK) { error = EINVAL; goto out; } error = VOP_GETATTR(vp, &vattr, p->p_ucred, p); > > 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 Fri Dec 25 20:52:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA01341 for freebsd-current-outgoing; Fri, 25 Dec 1998 20:52:34 -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 UAA01336 for ; Fri, 25 Dec 1998 20:52:31 -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 PAA17319; Sat, 26 Dec 1998 15:52:15 +1100 Date: Sat, 26 Dec 1998 15:52:15 +1100 From: Bruce Evans Message-Id: <199812260452.PAA17319@godzilla.zeta.org.au> To: bde@zeta.org.au, green@unixhelp.org Subject: Re: revoke of fifos Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >revoke(2) on VFIFO types is broken now, leading to stranded mbuf's. I suppose >> >> I don't think it has ever worked in BSD. > >Nor should it need to since, according to revoke.2: > Access to a file may be revoked only by its owner or the super user. The > revoke() function is currently supported only for block and character > special device files. The restriction to special files was removed in Lite2, but the man page was not updated and revoke on fifos didn't actually work. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 26 01:03:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA14534 for freebsd-current-outgoing; Sat, 26 Dec 1998 01:03:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail1.mclink.it (net128-007.mclink.it [195.110.128.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA14524 for ; Sat, 26 Dec 1998 01:03:23 -0800 (PST) (envelope-from mfubini@studenti.ing.uniroma1.it) Received: from mail.mclink.it (net138-086.mclink.it [195.110.138.86]) by mail1.mclink.it (8.9.1/8.9.0) with SMTP id KAA18105 for ; Sat, 26 Dec 1998 10:02:59 +0100 (CET) Date: Sat, 26 Dec 1998 09:01:14 +0100 From: Massimo Fubini X-Mailer: The Bat! (v1.017) UNREG Reply-To: Massimo Fubini Organization: Universita' "La Sapienza" Message-ID: <7375.981226@studenti.ing.uniroma1.it> To: freebsd-current@FreeBSD.ORG 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 subscibe Freebsd-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 26 08:43:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11069 for freebsd-current-outgoing; Sat, 26 Dec 1998 08:43:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp3.mindspring.com (smtp3.mindspring.com [207.69.200.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA11064 for ; Sat, 26 Dec 1998 08:43:31 -0800 (PST) (envelope-from brdean@mindspring.com) Received: from vger.foo.com (user-38ld95i.dialup.mindspring.com [209.86.164.178]) by smtp3.mindspring.com (8.8.5/8.8.5) with ESMTP id LAA26318 for ; Sat, 26 Dec 1998 11:43:15 -0500 (EST) Received: (from bsd@localhost) by vger.foo.com (8.9.1/8.9.1) id LAA29059; Sat, 26 Dec 1998 11:41:51 -0500 (EST) (envelope-from bsd) From: Brian Dean Message-Id: <199812261641.LAA29059@vger.foo.com> Subject: cvsup problems To: freebsd-current@FreeBSD.ORG Date: Sat, 26 Dec 1998 11:41:50 -0500 (EST) 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, I'm running an 11/21 SNAP of current and am trying to cvsup down the current sources to update my system. I'm following the directions in the handbook with the standard supfile, i.e.: cvsup -g -L 2 standard-supfile where 'standard-supfile' is: "# $Id: standard-supfile,v 1.12 1997/10/02 00:01:36 jkh Exp $" and my cvsup version is: [root@vger]:/bin- cvsup -v CVSup client, GUI version Software version: REL_15_4_2 Protocol version: 15.5 Here's the error I'm getting in my logfile: ---------------------------------------------------------------------- CVSup (source) update began at 1998/12/26 09:34:20 Parsing supfile "/mirror/etc/standard-supfile" Looking up address of cvsup.FreeBSD.org Connecting to cvsup.FreeBSD.org Connected to cvsup.FreeBSD.org Server software version: U_1998_12_24_22_09_14 Negotiating file attribute support Exchanging collection information Establishing active-mode data connection Running Updating collection src-all/cvs Detailer failed: Network write failure: Connection lost Will retry at 09:52:59 Retrying Looking up address of cvsup.FreeBSD.org Connecting to cvsup.FreeBSD.org Connected to cvsup.FreeBSD.org Server software version: U_1998_12_24_22_09_14 Negotiating file attribute support Exchanging collection information Establishing active-mode data connection Running Updating collection src-all/cvs Checkout src/contrib/binutils/binutils/objcopy.1 Checkout src/contrib/binutils/binutils/objdump.1 Checkout src/contrib/binutils/binutils/strings.c Edit src/contrib/binutils/binutils/strip.1 Add delta 1.2 98.12.03.19.54.43 billf Checkout src/contrib/binutils/gas/doc/as.1 Detailer failed: Network write failure: Connection timed out Will retry at 10:20:41 ---------------------------------------------------------------------- My connection is with a 56K modem via my ISP, and has been up for hours with no problems, i.e., mail, ftp, http, etc., all work fine. Any suggestions as to what I'm doing wrong? Thanks, -Brian -- Brian Dean brdean@mindspring.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 26 09:12:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA12981 for freebsd-current-outgoing; Sat, 26 Dec 1998 09:12:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12976 for ; Sat, 26 Dec 1998 09:12:02 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.57.29]) by smtp05.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA1F54; Sat, 26 Dec 1998 18:11:46 +0100 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: <199812261641.LAA29059@vger.foo.com> Date: Sat, 26 Dec 1998 18:18:31 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Brian Dean Subject: RE: cvsup problems Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 26-Dec-98 Brian Dean wrote: > Here's the error I'm getting in my logfile: > Detailer failed: Network write failure: Connection timed out OK, substitute cvsup.freebsd.org by cvsup2 or cvsup3.freebsd.org and try again cvsup.freebsd.org is VERY busy... Me? I just use my local mirror: cvsup.nl.freebsd.org --- Jeroen Ruigrok van der Werven Life is the only Pain asmodai(at)wxs.nl we endeavour... Network/Security Specialist BSD & picoBSD: 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 Dec 26 09:12:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13002 for freebsd-current-outgoing; Sat, 26 Dec 1998 09:12:08 -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 JAA12995 for ; Sat, 26 Dec 1998 09:12:06 -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 MAA21530; Sat, 26 Dec 1998 12:11:47 -0500 (EST) Date: Sat, 26 Dec 1998 12:11:46 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Bruce Evans cc: current@FreeBSD.ORG Subject: Re: revoke of fifos In-Reply-To: <199812260452.PAA17319@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 Sat, 26 Dec 1998, Bruce Evans wrote: > >> >revoke(2) on VFIFO types is broken now, leading to stranded mbuf's. I suppose > >> > >> I don't think it has ever worked in BSD. > > > >Nor should it need to since, according to revoke.2: > > Access to a file may be revoked only by its owner or the super user. The > > revoke() function is currently supported only for block and character > > special device files. > > The restriction to special files was removed in Lite2, but the man page was > not updated and revoke on fifos didn't actually work. So is the solution to update the manpage and: a. note that only revoking FIFOs doesn't work, also checking for vp->VFIFO in vfs_syscalls.c:/^revoke? or b. Take all notes about file revocation not working out, and correct the case of revoking VFIFOs by not stranding those mbufs? > > 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 Sat Dec 26 13:57:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06475 for freebsd-current-outgoing; Sat, 26 Dec 1998 13:57:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles325.castles.com [208.214.167.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA06462 for ; Sat, 26 Dec 1998 13:57: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 NAA01495; Sat, 26 Dec 1998 13:55:12 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812262155.NAA01495@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Feldman cc: current@FreeBSD.ORG Subject: Re: K6-2 (3?) CPU_WT_ALLOC In-reply-to: Your message of "Thu, 24 Dec 1998 21:46:56 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 26 Dec 1998 13:55:11 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > CPU_WT_ALLOC does not work correctly for K6-2s of model 8+ and probably K6-3s > (when they appear on the market soon). In addition, print_AMD_info() incorrectly > printfs write allocation's size. I've fixed them, so they now Do The Right > Thing, and added a "NO_MEMORY_HOLE" option to easily allow 15-16mb range > handling for us K6 and K6-2 users. A patch follows in cleartext and encoded > forms. Can anyone else using this patch speak up about their experiences? It'd be good to see it committed, but I have no hardware on which to test 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 From owner-freebsd-current Sat Dec 26 14:00:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA06720 for freebsd-current-outgoing; Sat, 26 Dec 1998 14:00:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles325.castles.com [208.214.167.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA06715 for ; Sat, 26 Dec 1998 14:00: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 NAA01523; Sat, 26 Dec 1998 13:57:37 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812262157.NAA01523@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Stefan Eggers cc: "Erik Funkenbusch" , freebsd-current@FreeBSD.ORG Subject: Re: Broken ipfw? In-reply-to: Your message of "Fri, 25 Dec 1998 17:25:05 +0100." <199812251625.RAA12096@semyam.dinoco.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 26 Dec 1998 13:57:37 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > After cvsuping on saturday natd has suddenly stopped working with the kernel > > I built on saturday and after cvsuping today and rebuilding as well. > > > > After executing an ipfw rule it responds with: > > > > ip_fw_ctl: empty interface name > > /sbin/ipfw: setsockopt(IP_FW_ADD): Invalid Argument > > Using a kernel module for ipfw? I used it preloaded by /boot/loader > and with a world (and kernel, of course) from last weekend the kernel > did see there was a preloaded ELF module but it never got integrated > into the system - ipfw's initial message during startup was missing > and I had a similar problem. The result was a kernel without working > ipfw. That's quite interesting. > See PR kern/9178. If anybody needs more details for this I can easily > reproduce the problem. I still have a kernel w/o ipfw and could test > it. Please do. It would be very useful to know if the SYSINIT for ipfw is being called correctly. -- \\ 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 Dec 26 22:10:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA15228 for freebsd-current-outgoing; Sat, 26 Dec 1998 22:10:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from garman.dyn.ml.org (pm510-10.dialip.mich.net [131.118.249.232]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA15223 for ; Sat, 26 Dec 1998 22:10:23 -0800 (PST) (envelope-from garman@earthling.net) From: garman@earthling.net Message-Id: <199812270610.WAA15223@hub.freebsd.org> Received: (qmail 37537 invoked from smtpd); 27 Dec 1998 06:10:04 -0000 Received: from localhost.garman.net (HELO earthling.net) (127.0.0.1) by localhost.garman.net with SMTP; 27 Dec 1998 06:10:04 -0000 Date: Sun, 27 Dec 1998 01:10:03 -0500 (EST) Reply-To: garman@earthling.net Subject: PR filed on dying daemons 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 I upgraded to a recent -current (as of two days ago) and found the dying daemons bug still exists :( I filed a PR on the subject since I couldn't find another which already addressed the issue. It's kern/9195. I'm more than willing to give people accounts, test patches, etc for the cause of trying to fix this bug, as myself as well as many others are still experiencing it on a regular basis. (funnily enough while trying to send this message inetd just gave me...) inetd in realloc(): warning: junk pointer, too low to make sense. inetd in free(): warning: junk pointer, too low to make sense. running bash$ ident /usr/sbin/inetd /usr/sbin/inetd: $Id: inetd.c,v 1.43 1998/12/15 23:12:33 dillon Exp $ enjoy -- 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 26 22:11:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA15492 for freebsd-current-outgoing; Sat, 26 Dec 1998 22:11:59 -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 WAA15485; Sat, 26 Dec 1998 22:11:48 -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 BAA95630; Sun, 27 Dec 1998 01:11:27 -0500 (EST) (envelope-from lee) Message-ID: <19981227011127.A95605@tidalwave.net> Date: Sun, 27 Dec 1998 01:11:27 -0500 From: Lee Cremeans To: current@FreeBSD.ORG Cc: foxfair@FreeBSD.ORG Subject: pcisupport.c 1.85 breaks ide_pci and USB on VIA boards Reply-To: lcremean@tidalwave.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The changes foxfair made in pcisupport.c for the VIA chipset included entries for the VIA Apollo IDE and USB controllers. This change breaks support for both of them on machines with VP1/VP2/[M]VP3 chipsets, since both functions have their own drivers. For future reference, I should note that only PCI north and south bridges, VGA cards, and things we don't have explicit driver support for elsewhere should be in pcisupport.c, since having them in there basically serves only to show people what chips are on their motherboards (and to work around quirks in a few chipsets). PCI IDE is in /sys/pci/ide_pci.c, USB is in /sys/dev/pci/ohci_pci.c and uhci_pci.c, and if there's an entry for a chip in pcisupport.c that another driver should be covering, that driver will never see the PCI probe--the buck stops at pcisupport.c. By the way, the other MVP3 ID patches seem to work fine here, on my shiny new Soyo SY-5EHM. :) Here's the patch to back out the changes pertinent to this. *** pcisupport.c.orig Sun Dec 27 01:05:24 1998 --- pcisupport.c Sun Dec 27 01:05:52 1998 *************** *** 342,352 **** /* XXX need info on the MVP3 -- any takers? */ case 0x30401106: return("VIA 82C586B ACPI interface"); - /* XXX New info added-in */ - case 0x05711106: - return("VIA 82C586B IDE controller"); - case 0x30381106: - return("VIA 82C586B USB controller"); /* XXX Here is MVP3, I got the datasheet but NO M/B to test it */ /* totally. Please let me know if anything wrong. -F */ case 0x05981106: --- 342,347 ---- -- +--------------------------------------------------------------------+ | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)| | lcremean@tidalwave.net| http://st-lcremean.tidalwave.net | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message