From owner-freebsd-current Sun Jun 22 04:22:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA27669 for current-outgoing; Sun, 22 Jun 1997 04:22:58 -0700 (PDT) Received: from ns1.netcologne.de (ns1.netcologne.de [194.8.194.70]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id EAA27391; Sun, 22 Jun 1997 04:21:44 -0700 (PDT) Received: from theseus.mediaconsult.de by ns1.netcologne.de (8.6.12/NetCologne/marvin/netsafe-a0020) id ; Sun, 22 Jun 1997 12:58:25 +0200 with ESMTP X-Ncc-Regid: de.netcologne Message-ID: <33AD0A8E.ED1452A0@netcologne.de> Date: Sun, 22 Jun 1997 13:20:46 +0200 From: Richard Cochius Reply-To: richard.cochius@netcologne.de Organization: Media Connect Cologne X-Mailer: Mozilla 4.0b5 [en] (Win95; I) MIME-Version: 1.0 To: FREEBSD-ADMIN@freebsd.org, FREEBSD-ANNOUNCE@freebsd.org, FREEBSD-ARCH@freebsd.org, FREEBSD-BUGS@freebsd.org, FREEBSD-CORE@freebsd.org, FREEBSD-CURRENT@freebsd.org, FREEBSD-CURRENT-DIGEST@freebsd.org, FREEBSD-STABLE@freebsd.org, FREEBSD-DOC@freebsd.org, FREEBSD-FS@freebsd.org, FREEBSD-HACKERS@freebsd.org, FREEBSD-HACKERS-DIGEST@freebsd.org, FREEBSD-HARDWARE@freebsd.org, FREEBSD-INSTALL@freebsd.org, FREEBSD-ISP@freebsd.org, FREEBSD-MULTIMEDIA@freebsd.org, FREEBSD-PLATFORMS@freebsd.org, FREEBSD-PORTS@freebsd.org, FREEBSD-QUESTIONS@freebsd.org, FREEBSD-QUESTIONS-DIGEST@freebsd.org, FREEBSD-SCSI@freebsd.org, FREEBSD-SECURITY@freebsd.org, FREEBSD-SECURITY-NOTIFICATIONS@freebsd.org, FREEBSD-USER-GROUPS@freebsd.org Subject: subscribe X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk From owner-freebsd-current Sun Jun 22 06:00:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA00967 for current-outgoing; Sun, 22 Jun 1997 06:00:27 -0700 (PDT) Received: from mailhost (user-37kbbhu.dialup.mindspring.com [207.69.174.62]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id GAA00962 for ; Sun, 22 Jun 1997 06:00:23 -0700 (PDT) Received: from rlb by mailhost with smtp (Smail3.1.29.1 #1) id m0wfmFz-000G0nC; Sun, 22 Jun 97 09:00 EDT Message-ID: <33AD21E8.5A06@mindspring.com> Date: Sun, 22 Jun 1997 09:00:24 -0400 From: Ron Bolin X-Mailer: Mozilla 3.01Gold (X11; I; SunOS 5.5.1 i86pc) MIME-Version: 1.0 To: FreeBSD Current Mailing List Subject: Makefile doc make problems Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In building RELENG_2_2 on (cvsup'd) on 6-21-97 I found that several Makefiles contained references to build "doc". However, the doc directory either did not exist or it was empty. This made the Make install fail for each Makefile. I had to go through each Makefile and comment out the offending "doc" entry. Where is the info or doc that I missed that caused this. Thank's in advance. Ron -- **************************************************************************** Ron Bolin rlb@mindspring.com, http://www.mindspring.com/~rlb/ http://rlb.users.mindspring.com gs01rlb@panther.gsu.edu rbolin@viewcall.net Home: 770-992-8877 Work: 770-729-2929 Ext 249 From owner-freebsd-current Sun Jun 22 06:48:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA02243 for current-outgoing; Sun, 22 Jun 1997 06:48:48 -0700 (PDT) Received: from gneiss.eps.nagoya-u.ac.jp (gneiss.eps.nagoya-u.ac.jp [133.6.57.99]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA02238 for ; Sun, 22 Jun 1997 06:48:42 -0700 (PDT) Received: from marble.eps.nagoya-u.ac.jp (localhost [127.0.0.1]) by gneiss.eps.nagoya-u.ac.jp (8.8.5/3.4W4) with ESMTP id WAA04676; Sun, 22 Jun 1997 22:48:39 +0900 (JST) Message-Id: <199706221348.WAA04676@gneiss.eps.nagoya-u.ac.jp> To: current@FreeBSD.org Cc: kato@migmatite.eps.nagoya-u.ac.jp Subject: Re: vm_bounce_alloc: Unmapped page From: KATO Takenori In-Reply-To: Your message of "Tue, 17 Jun 1997 19:24:47 +0900" References: <199706171024.TAA07709@ganko.eps.nagoya-u.ac.jp> X-Mailer: Mew version 1.70 on Emacs 19.28.1 / Mule 2.3 X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sun, 22 Jun 1997 22:48:38 +0900 Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk From: KATO Takenori Subject: vm_bounce_alloc: Unmapped page Date: Tue, 17 Jun 1997 19:24:47 +0900 > $11 = {b_hash = {le_next = 0x0, le_prev = 0x0}, b_vnbufs = { > le_next = 0x87654321, le_prev = 0x0}, b_freelist = {tqe_next = 0x0, > tqe_prev = 0x0}, b_act = {tqe_next = 0x0, tqe_prev = 0x0}, b_proc = 0x0, > b_flags = 1090519124, b_qindex = 0, b_usecount = 0 '\000', b_error = 0, > b_bufsize = 8192, b_bcount = 8192, b_resid = 0, b_dev = 197636, b_un = { > b_addr = 0xf3b99000
}, > b_kvabase = 0xf3b99000
, b_kvasize = 8192, The buffer whose b_addr = 0xf3b99000 was allocated by bp = trypbuf() in cluster_wbuild(). ---- KATO Takenori Dept. Earth Planet. Sci., Nagoya Univ., Nagoya, 464-01, Japan PGP public key: finger kato@eclogite.eps.nagoya-u.ac.jp ------------------- Powered by FreeBSD(98) ------------------- From owner-freebsd-current Sun Jun 22 06:58:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA02587 for current-outgoing; Sun, 22 Jun 1997 06:58:48 -0700 (PDT) Received: from freebsd.scds.com (scds.ziplink.net [206.15.128.34]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA02582 for ; Sun, 22 Jun 1997 06:58:45 -0700 (PDT) Received: (from jseger@localhost) by freebsd.scds.com (8.8.5/8.7.3) id JAA28424; Sun, 22 Jun 1997 09:09:53 -0400 (EDT) Date: Sun, 22 Jun 1997 09:09:53 -0400 (EDT) From: "Justin M. Seger" Message-Id: <199706221309.JAA28424@freebsd.scds.com> To: jseger@freebsd.scds.com, smp@csn.net Subject: Re: Activehome X10 Interface Cc: current@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, I think I'd like to try to tackle expanding the xtend daemon to work with the CM11A. Unfortunatly, I have very little experience with serial IO. If I could figure out how to send data to a serial port, and receive data from a serial port after a RI (ring) signal has been sent. Any ideas on where I should start? Thanks, -Justin Seger- From owner-freebsd-current Sun Jun 22 09:05:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA09354 for current-outgoing; Sun, 22 Jun 1997 09:05:31 -0700 (PDT) Received: from sanewo.ba2.so-net.or.jp (pppba0f.pppp.ap.so-net.or.jp [210.132.186.15]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA09339 for ; Sun, 22 Jun 1997 09:05:23 -0700 (PDT) Received: (from sanewo@localhost) by sanewo.ba2.so-net.or.jp (8.8.5/8.7.3) id JAA15793; Sun, 22 Jun 1997 09:02:56 +0900 (JST) To: freebsd-current@FreeBSD.ORG Subject: ppp 'Connect time' not logged when idle timer expired From: Takanori Saneto X-Emacs: Emacs 19.34.94, MULE 3.0 (MOMIJINOGA) Mime-Version: 1.0 (generated by SEMI MIME-Edit 0.82) Content-Type: text/plain; charset=ISO-2022-JP Date: 22 Jun 1997 09:02:55 +0900 Message-ID: <87iuz7v70w.fsf@sanewo.ba2.so-net.or.jp> Lines: 20 X-Mailer: Gnus v5.4.59 + SEMI patch (r2.1)/Emacs 19.34/Mule 3.0 (MOMIJINOGA) Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Using -current ppp (as of 6/19) in -auto mode, with "set log phase" in ~/.ppp.conf. When I terminates (kill `cat /var/run/tunN.pid`) it while modem is used, 'Connection time: xxx sec' is logged. When idle timer expired, it won't. I remember that it worked fine about several months ago, then it became unavailable (I'm sorry I don't remember when/wht version). At that time, I changed HangupModem() in modem.c so that it sleeps one more second after dropping DTR, which made logging of 'Connection time' work again. Recently (within a month, I think) such trick became not working. (Original source won't work, neither) Any ideas? -- さねを From owner-freebsd-current Sun Jun 22 09:34:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA11113 for current-outgoing; Sun, 22 Jun 1997 09:34:39 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA11108 for ; Sun, 22 Jun 1997 09:34:36 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wfpam-000416-00; Sun, 22 Jun 1997 10:34:20 -0600 To: current@freebsd.org Subject: login_getclass: unknown class '0 Date: Sun, 22 Jun 1997 10:34:19 -0600 From: Warner Losh Message-Id: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greetings, I've just upgraded my -current system and am now getting errors like: Jun 21 17:46:42 harmony sshd[18705]: login_getclass: unknown class '0 when I come in via ssh. And when I boot: Jun 17 21:31:51 harmony /kernel: pid 97 (cron), uid 0: exited on signal 12 (core dumped) These don't strike me as normal :-). I do have an /etc/login.access and /etc/login.conf, both owned by root.wheel copied directly from /usr/src/etc. Can someone comment on why I might be seeing these behaviors? Warner P.S. A search of the archives leaves me no wiser than I was before. P.P.S. Maybe I need to recompile sshd? From owner-freebsd-current Sun Jun 22 09:53:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA12142 for current-outgoing; Sun, 22 Jun 1997 09:53:07 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA12137 for ; Sun, 22 Jun 1997 09:52:57 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.5/8.8.5) with ESMTP id JAA13670; Sun, 22 Jun 1997 09:52:44 -0700 (PDT) Message-Id: <199706221652.JAA13670@austin.polstra.com> To: Bruce Evans cc: jkh@time.cdrom.com, current@FreeBSD.ORG Subject: Re: Hmmmm, this is new.. In-reply-to: Your message of "Sun, 22 Jun 1997 16:38:58 +1000." <199706220638.QAA23309@godzilla.zeta.org.au> References: <199706220638.QAA23309@godzilla.zeta.org.au> Date: Sun, 22 Jun 1997 09:52:43 -0700 From: John Polstra Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > It's probably a bug for it not to happen for every `make world'. > -nostdlib should be used to prevent old libraries being linked to. > Since libtcl is built before msun and there is no special bootstrapping > for msun, a new version of msun is guaranteed to not exist when > libtcl is linked. Right you are, Bruce. For starters, I'm going to change /usr/lib/Makefile so that the first three directories built are csu, libc, and , in that order. It should solve all existing dependency problems, even if it's not really a complete solution. Ultimately, all the libraries need to be reordered in the Makefile, based on their interdependencies. Most of the interdependencies are hidden currently, because they're not explicitly specified (as is the "-lm" in libtcl/Makefile). John P. From owner-freebsd-current Sun Jun 22 10:03:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA12795 for current-outgoing; Sun, 22 Jun 1997 10:03:07 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA12790 for ; Sun, 22 Jun 1997 10:03:04 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.5/8.8.5) with ESMTP id KAA13719; Sun, 22 Jun 1997 10:02:56 -0700 (PDT) Message-Id: <199706221702.KAA13719@austin.polstra.com> To: Bruce Evans cc: jkh@time.cdrom.com, current@FreeBSD.ORG Subject: Re: Hmmmm, this is new.. Date: Sun, 22 Jun 1997 10:02:55 -0700 From: John Polstra Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Ooops. I wrote: > > It's probably a bug for it not to happen for every `make world'. > > -nostdlib should be used to prevent old libraries being linked to. > > Since libtcl is built before msun and there is no special bootstrapping > > for msun, a new version of msun is guaranteed to not exist when > > libtcl is linked. > > Right you are, Bruce. For starters, I'm going to change > /usr/lib/Makefile so that the first three directories built are > csu, libc, and , in that order. It should solve all > existing dependency problems, even if it's not really a complete > solution. Never mind. That's not going to help anything. All the libraries are built before any is installed. A different solution is going to be needed. John P. From owner-freebsd-current Sun Jun 22 10:38:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA14550 for current-outgoing; Sun, 22 Jun 1997 10:38:40 -0700 (PDT) Received: from freebsd.scds.com (scds.ziplink.net [206.15.128.34]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA14544 for ; Sun, 22 Jun 1997 10:38:36 -0700 (PDT) Received: (from jseger@localhost) by freebsd.scds.com (8.8.5/8.7.3) id NAA00219 for current@freebsd.org; Sun, 22 Jun 1997 13:37:51 -0400 (EDT) Date: Sun, 22 Jun 1997 13:37:51 -0400 (EDT) From: "Justin M. Seger" Message-Id: <199706221737.NAA00219@freebsd.scds.com> To: current@freebsd.org Subject: Errors after doing a make world and building a new kernel on June 21 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On sources current as of June 21, I rebuilt the kernel and did a make world. After rebooting, I've gotten the following errors: On second thought, here's the dmesg log. It shows the error at the end. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #0: Sun Jun 22 08:50:47 EDT 1997 jseger@freebsd.scds.com:/usr/src/sys/compile/SCDS CPU: i486DX (486-class CPU) real memory = 25165824 (24576K bytes) avail memory = 22831104 (22296K bytes) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x340-0x35f irq 5 on isa ed0: address 00:40:33:30:b1:ea, type NE2000 (16 bit) sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16450 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 765 fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 814MB (1667232 sectors), 1654 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): wd1: 515MB (1056384 sectors), 1048 cyls, 16 heads, 63 S/T, 512 B/S npx0 on motherboard npx0: INT 16 interface WARNING: / was not properly dismounted. wd0: interrupt timeout: wd0: status 58 error 4 Please let me know what might be causing this.... Thanks, -justin Seger- From owner-freebsd-current Sun Jun 22 10:43:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA14751 for current-outgoing; Sun, 22 Jun 1997 10:43:13 -0700 (PDT) Received: from veda.is (ubiq.veda.is [193.4.230.60]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA14743 for ; Sun, 22 Jun 1997 10:43:06 -0700 (PDT) Received: (from adam@localhost) by veda.is (8.8.5/8.7.3) id SAA23147; Sun, 22 Jun 1997 18:11:01 GMT From: Adam David Message-Id: <199706221811.SAA23147@veda.is> Subject: Re: getty modem control In-Reply-To: <199706221146.VAA00338@labs.usn.blaze.net.au> from David Nugent at "Jun 22, 97 09:46:03 pm" To: davidn@labs.usn.blaze.net.au (David Nugent) Date: Sun, 22 Jun 1997 18:11:00 +0000 (GMT) Cc: freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [David Nugent] > [Adam David] > > I have reordered the flow of the chat support in main() and added :nb: > > to enable non-blocking use. > > I'm not sure what you mean. Non-blocking open, or non-blocking i/o? > chat.c does fiddle with non-blocking i/o, but only for preventing an > indefinite wait within the kernel should a signal occur. non-blocking open. Currently your code forces non-blocking open when answer chat is used. > > If no-one among the non-blocking crowd objects, I will commit the > > changes so that blocking use of the answer chat facilities > > is available by default. > > Again, I'm not sure what this means. How can you use answer chat > on a blocked open, assuming this is what you're referring to. Start with "" "\d\d\d+++\d\d\d" and end with "ATO" or am I missing something here? After the modem autoanswers the incoming call, the chat script can talk to the local modem and/or the remote equipment/person. It's purpose is not to pick up the phone but to interact with the incoming call on the answer event. In the case of non-blocking open, this requires the use of "ATA" to pick up the phone. [assume Hayes command set] > I'd also vote AGAINST any change to 'default' beahviour at all. > This is likely to upset people, and you can see from Joergs' > reaction as to how seriously people take it. No change to default behaviour, except where :ac=: is used, my change requires a :nb: to get the same effect with :ac=: as currently. > > Yes, it would definitely be nice to log the report strings. Is there a > > chance that CID will be available on broken implementations (such as > > Rockwell) when blocking on open() is used? > > Sure. It may be dependant on the modem, but when CD goes high, > the open succeeds. If the modem sends the connect strings after > that point (and I've never come across one that sends them before > then), they can be read - in fact, their presence in the first > place is what cause me to fix :de: so it flushed after the > delay. This was confusing getty's login prompt. There's > a secondary problem of possibly eating valid input (but the i/o > flush after the delay if you're using does that anyway), but this > is a configuration issue, not a software one. The connect strings are sent at that point, but CID is sent after the first ring so if ATS0=2 (or greater), CID is presented to the serial port before DCD is asserted. What happens when ATS0=1, is the CID sent by the telco (and usable) even when the call is answered on the first ring? > > To generify the question, if the serial input is not flushed > > on successful open, is that input > > available for reading if it originally occured after open() was first > > invoked but before the open() completed? > > Yes. The open would have completed anyway, but the timing issue > is more related to the modem than anything else. Do I understand correctly that data output from the modem during the period of open() being blocked, is available for reading once the open() completes? (assuming we don't flush the input) > > > I *hate* mgetty with a vengence - it is far too bloated and > > > difficult to configure. > > > > ... and still assumes primitive modem technology. It's fine to support > > older equipment, but too limiting when this is assumed. > > Absolutely. Like autoboard speed switching. We could probably rip > that out of FreeBSD's getty and noone would notice. Still, it is > a large part of the *noticable* interface to allow baud rate > switching, and it is "historical". Personally, I'd have more > objections to having that "bloat" in getty than something far > more useful like handling a modem. :-) > > Not to mention that this bloat causes a memory leak under 2.2 > (I fixed this in -current, but haven't yet merged it back into > the 2.2 branch; still waiting on feedback from Bruce on that). > > > > getty works for me, and very well, using a wide range of modems. > > > Its only problem is having to use cua* devices rather than tty* > > > devices, which I am fairly certain has to do with termios settings, > > > and in particular CLOCAL handling. It is in my todo list to fix. > > > > Ah, this is where I took a wrong turn. I was trying to use it with ttyd? > > devices. > > No, they definitely won't work right now. There's a hang on read in > spite of the non-blocking open(). > > > > when trying cuaa0 I found something had set /dev/cuaa0 to root.wheel 600 > > and I don't remember any other program than getty getting near it > > I don't have this problem at all. getty does reset the modes correctly, > and since it is running as root anyway, how are the tty modes relevant? It interferes with other programs that might want to talk to the port. The following snippet is from main.c, I don't see where the permissions are restored. if (strcmp(argv[0], "+") != 0) { chown(ttyn, 0, 0); chmod(ttyn, 0600); revoke(ttyn); /dev/ttyd? is already root.wheel 600 so this is simply reinforcing it. /dev/cuaa? is normally uucp.dialer 660 and changing it prevents other programs relying on uucp.dialer from using the port, even afterwards. > > went back to being stuck at getty chat on ttyd0 not working. Since people > > are using it with some success, I sat back to hear how this was done. > > Use the cua devices. > > I can send my gettytab and ttys if you like. They are fully working > examples used in a production environment. This would be helpful if you would. Relevant excerpts are sufficient. -- Adam David From owner-freebsd-current Sun Jun 22 10:51:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA15134 for current-outgoing; Sun, 22 Jun 1997 10:51:51 -0700 (PDT) Received: from helbig.informatik.ba-stuttgart.de (helbig.informatik.ba-stuttgart.de [141.31.166.22]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA15128 for ; Sun, 22 Jun 1997 10:51:45 -0700 (PDT) Received: (from helbig@localhost) by helbig.informatik.ba-stuttgart.de (8.8.5/8.8.5) id TAA23374; Sun, 22 Jun 1997 19:51:22 +0200 (MET DST) From: Wolfgang Helbig Message-Id: <199706221751.TAA23374@helbig.informatik.ba-stuttgart.de> Subject: Re: login_getclass: unknown class '0 In-Reply-To: from Warner Losh at "Jun 22, 97 10:34:19 am" To: imp@village.org (Warner Losh) Date: Sun, 22 Jun 1997 19:51:21 +0200 (MET DST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Greetings, > I've just upgraded my -current system and am now getting > errors like: > > Jun 21 17:46:42 harmony sshd[18705]: login_getclass: unknown class '0 A rebuild of ssh might help this one. > when I come in via ssh. And when I boot: > > Jun 17 21:31:51 harmony /kernel: pid 97 (cron), uid 0: exited on > signal 12 (core dumped) This is new to me, but my last ``make world'' is very old (more than a week). > These don't strike me as normal :-). I do have an /etc/login.access > and /etc/login.conf, both owned by root.wheel copied directly from > /usr/src/etc. > > Can someone comment on why I might be seeing these behaviors? > > Warner > > P.S. A search of the archives leaves me no wiser than I was before. > P.P.S. Maybe I need to recompile sshd? Yes! Wolfgang From owner-freebsd-current Sun Jun 22 11:07:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA15702 for current-outgoing; Sun, 22 Jun 1997 11:07:49 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA15696 for ; Sun, 22 Jun 1997 11:07:44 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wfr2o-00048Z-00; Sun, 22 Jun 1997 12:07:22 -0600 To: Wolfgang Helbig Subject: Re: login_getclass: unknown class '0 Cc: current@freebsd.org In-reply-to: Your message of "Sun, 22 Jun 1997 19:51:21 +0200." <199706221751.TAA23374@helbig.informatik.ba-stuttgart.de> References: <199706221751.TAA23374@helbig.informatik.ba-stuttgart.de> Date: Sun, 22 Jun 1997 12:07:22 -0600 From: Warner Losh Message-Id: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I hate to reply to my own message, so I'll use Wolfgang's instead :-) In message <199706221751.TAA23374@helbig.informatik.ba-stuttgart.de> Wolfgang Helbig writes: : > Jun 21 17:46:42 harmony sshd[18705]: login_getclass: unknown class '0 : : A rebuild of ssh might help this one. A rebuild of ssh did help this. : > when I come in via ssh. And when I boot: : > : > Jun 17 21:31:51 harmony /kernel: pid 97 (cron), uid 0: exited on : > signal 12 (core dumped) : : This is new to me, but my last ``make world'' is very old (more than a : week). sig 12 is SIGSYS which means that a non-existent system call invoked. A new kernel fixed this. Now I'm happy again. ps works again too (which was why I rebooted the new kernel, when I noticed the other problem was fixed thereby. Warner From owner-freebsd-current Sun Jun 22 12:36:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA19262 for current-outgoing; Sun, 22 Jun 1997 12:36:20 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA19257 for ; Sun, 22 Jun 1997 12:36:18 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA29222; Sun, 22 Jun 1997 12:24:46 -0700 From: Terry Lambert Message-Id: <199706221924.MAA29222@phaeton.artisoft.com> Subject: Re: getty modem control To: louie@TransSys.COM (Louis A. Mamakos) Date: Sun, 22 Jun 1997 12:24:46 -0700 (MST) Cc: terry@lambert.org, adam@veda.is, joerg_wunsch@uriah.heep.sax.de, freebsd-current@FreeBSD.ORG In-Reply-To: <199706220041.UAA25091@whizzo.TransSys.COM> from "Louis A. Mamakos" at Jun 21, 97 08:41:17 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Link-level compression is evil anyway; compression belongs on > > the host side of the host UART so that the datarate is not > > limited by the serial port rate. > > I disagree. Given that the modem is already doing V.42 link-level > reliablity, it fits in very nicely with it's segmentation. I can never exceed the DTE rate if the compression is done in the modem. If the compression is done in the host, I can routinely exceed the DTE rate. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Sun Jun 22 12:56:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA20058 for current-outgoing; Sun, 22 Jun 1997 12:56:47 -0700 (PDT) Received: from veda.is (ubiq.veda.is [193.4.230.60]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA20053 for ; Sun, 22 Jun 1997 12:56:42 -0700 (PDT) Received: (from adam@localhost) by veda.is (8.8.5/8.7.3) id UAA23414; Sun, 22 Jun 1997 20:24:39 GMT From: Adam David Message-Id: <199706222024.UAA23414@veda.is> Subject: Re: getty modem control In-Reply-To: <199706221834.EAA00522@labs.usn.blaze.net.au> from David Nugent at "Jun 23, 97 04:34:28 am" To: davidn@labs.usn.blaze.net.au (David Nugent) Date: Sun, 22 Jun 1997 20:24:37 +0000 (GMT) Cc: freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > I'm not sure what you mean. Non-blocking open, or non-blocking i/o? > > > chat.c does fiddle with non-blocking i/o, but only for preventing an > > > indefinite wait within the kernel should a signal occur. > > > > non-blocking open. Currently your code forces non-blocking open when > > answer chat is used. > > Right. But before you can get a carrier, you need to answer the line > by sending ATA. How can you do that without the port being open? ATS0=1 opens the port on an incoming call. > > > Again, I'm not sure what this means. How can you use answer chat > > > on a blocked open, assuming this is what you're referring to. > > > > Start with "" "\d\d\d+++\d\d\d" and end with "ATO" or am I missing something > > here? > > ? Go into command mode to talk to the modem, then back into data mode. Different data modes can perhaps be selected depending on the nature of the incoming call, even different programs started to take the call. > > After the modem autoanswers the incoming call, the chat script can > > talk to the local modem and/or the remote equipment/person. It's purpose > > is not to pick up the phone but to interact with the incoming call on the > > answer event. In the case of non-blocking open, this requires the use of > > "ATA" to pick up the phone. [assume Hayes command set] > > Yes, that was the intention. However, going into command mode at > this stage is both unnecessary and possibly dangerous. Unnecessary for your purposes, and dangerous --> risky (for modems that cannot handle it). Why else should there be any problem with skipping out to command mode? > > No change to default behaviour, except where :ac=: is used, my change > > requires a :nb: to get the same effect with :ac=: as currently. > > I must not understand exactly what it is you're trying to do. Why go > into command mode *after* you've established the connection? > The whole point of an answer chat is to answer the phone, no? You are operating on the assumption that manual answer is necessary. I am more interested in using auto-answer. The main point of answer chat (from my perspective) is to respond to the stimulus of an answer event. If the phone has not already been answered, it can be done at this stage. > > The connect strings are sent at that point, but CID is sent after the > > first ring so if ATS0=2 (or greater), CID is presented to the serial port > > before DCD is asserted. What happens when ATS0=1, is the CID sent by the > > telco (and usable) even when the call is answered on the first ring? > > No idea. I don't have the facility. The only time I've seen CID at > work is when the modem (which is CID savvy) sent it as part of the > connect string. So far then I have seen these different methods of handling CID: 1. Provide a command for displaying the last received CID 2. Display CID as it arrives (before connect) 3. Display CID with the connect string Simply not answering blocked numbers is not possible with the third method, for this the only way to block numbers is hanging up the phone after connect. > > Do I understand correctly that data output from the modem during the period > > of open() being blocked, is available for reading once the open() completes? > > (assuming we don't flush the input) > > I assume so yes, but I was only addressing data received after the > open succeeds. As for earlier data, I have no idea, but I suspect > not since there's no tty attached to the device at the time, and > therefore there can be no clists collected. I'm wondering about whether the modem will buffer the data until the port is fully open, relying on hardware handshaking to hold it back. -- Adam David From owner-freebsd-current Sun Jun 22 14:51:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA24729 for current-outgoing; Sun, 22 Jun 1997 14:51:41 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA24724 for ; Sun, 22 Jun 1997 14:51:38 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA17837; Sun, 22 Jun 1997 11:05:17 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd017834; Sun Jun 22 18:05:11 1997 Date: Sun, 22 Jun 1997 11:04:00 -0700 (PDT) From: Julian Elischer To: John Polstra cc: Bruce Evans , jkh@time.cdrom.com, current@FreeBSD.ORG Subject: Re: Hmmmm, this is new.. In-Reply-To: <199706221702.KAA13719@austin.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 22 Jun 1997, John Polstra wrote: > Ooops. I wrote: > Never mind. That's not going to help anything. All the libraries > are built before any is installed. A different solution is going to > be needed. include -L ${USR_OBJ}/lib/libc etc OSF1 builds a separate copy of usr/include and usr/lib within the obj tree specifically to use for this. julian From owner-freebsd-current Sun Jun 22 16:55:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA28823 for current-outgoing; Sun, 22 Jun 1997 16:55:20 -0700 (PDT) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA28818 for ; Sun, 22 Jun 1997 16:55:15 -0700 (PDT) Received: from [208.2.87.4] (cod.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.5/8.8.5) with ESMTP id SAA16687; Sun, 22 Jun 1997 18:54:44 -0500 (CDT) X-Sender: rkw@shrimp.dataplex.net Message-Id: In-Reply-To: References: <199706221702.KAA13719@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 22 Jun 1997 18:54:28 -0500 To: Julian Elischer From: Richard Wackerbarth Subject: Re: Hmmmm, this is new.. Cc: John Polstra , Bruce Evans , jkh@time.cdrom.com, current@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 1:04 PM -0500 6/22/97, Julian Elischer wrote: >On Sun, 22 Jun 1997, John Polstra wrote: > >> Ooops. I wrote: > >> Never mind. That's not going to help anything. All the libraries >> are built before any is installed. A different solution is going to >> be needed. > >include -L ${USR_OBJ}/lib/libc >etc > >OSF1 builds a separate copy of usr/include and usr/lib >within the obj tree specifically to use for this. This is the kind of approach that we need to take in order to allow a build to be done on a multi-user or production machine without destroying the underlying system. From owner-freebsd-current Sun Jun 22 19:33:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA05734 for current-outgoing; Sun, 22 Jun 1997 19:33:01 -0700 (PDT) Received: from watcher.isl.net (ppp-01.isl.net [199.3.25.50]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA05729 for ; Sun, 22 Jun 1997 19:32:58 -0700 (PDT) Received: (from ortmann@localhost) by watcher.isl.net (8.8.5/8.8.5) id VAA01183 for freebsd-current@freebsd.org; Sun, 22 Jun 1997 21:31:52 -0500 (CDT) From: Daniel Ortmann Message-Id: <199706230231.VAA01183@watcher.isl.net> Subject: list of fast modems? To: freebsd-current@freebsd.org Date: Sun, 22 Jun 1997 21:31:50 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Any recommendations for quick/reliable/common modems for under $200? Top 5? -- Daniel Ortmann 507.288.7732 (h) ortmann@isl.net 2414 30 av NW, #D 507.253.6795 (w) ortmann@vnet.ibm.com Rochester, MN 55901 "PERL: The Swiss Army Chainsaw" From owner-freebsd-current Sun Jun 22 19:46:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA06311 for current-outgoing; Sun, 22 Jun 1997 19:46:59 -0700 (PDT) Received: from watcher.isl.net (ppp-01.isl.net [199.3.25.50]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA06306 for ; Sun, 22 Jun 1997 19:46:55 -0700 (PDT) Received: (from ortmann@localhost) by watcher.isl.net (8.8.5/8.8.5) id VAA01232 for freebsd-current@freebsd.org; Sun, 22 Jun 1997 21:45:49 -0500 (CDT) From: Daniel Ortmann Message-Id: <199706230245.VAA01232@watcher.isl.net> Subject: mailing list suggestion? To: freebsd-current@freebsd.org Date: Sun, 22 Jun 1997 21:45:48 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Can majordomo return the standard "echo help | mail majordomo@freebsd.org" message to users sending directly to the mailing lists? (It would be nice if those requests were *not* passed on.) -- Daniel Ortmann 507.288.7732 (h) ortmann@isl.net 2414 30 av NW, #D 507.253.6795 (w) ortmann@vnet.ibm.com Rochester, MN 55901 "PERL: The Swiss Army Chainsaw" From owner-freebsd-current Sun Jun 22 20:26:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA08323 for current-outgoing; Sun, 22 Jun 1997 20:26:19 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA08318 for ; Sun, 22 Jun 1997 20:26:15 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/) with SMTP id XAA10815; Sun, 22 Jun 1997 23:26:13 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id XAA09077; Sun, 22 Jun 1997 23:26:11 -0400 Date: Sun, 22 Jun 1997 23:25:58 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Daniel Ortmann cc: freebsd-current@FreeBSD.ORG Subject: Re: list of fast modems? In-Reply-To: <199706230231.VAA01183@watcher.isl.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 22 Jun 1997, Daniel Ortmann wrote: > Any recommendations for quick/reliable/common modems for under $200? Modems are something that calls up religious type responses, so I expect at least one person to tell me how dumb my suggestions are here ... Anyhow, when it was time to buy another modem, I checked PC magazine, and caught their modem review. I was interested in two main things, what it's error rate in noise was, and what it's tested intercompatibility was. As I remember, PC magazine disappointed me in not directly testing the error rate versus noise (BER) but it did give the US Robotics modems pretty good intercompatibilty ratings. I've used Mutlitech modems, and personally tested their BER vs. noise specs, and liked them. I personally bought USR. Maybe that tells you something. > > Top 5? > > -- > Daniel Ortmann 507.288.7732 (h) ortmann@isl.net > 2414 30 av NW, #D 507.253.6795 (w) ortmann@vnet.ibm.com > Rochester, MN 55901 "PERL: The Swiss Army Chainsaw" > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-current Sun Jun 22 20:55:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA09442 for current-outgoing; Sun, 22 Jun 1997 20:55:39 -0700 (PDT) Received: from fredriks-1.pr.mcs.net (fredriks-1.pr.mcs.net [205.164.50.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA09437 for ; Sun, 22 Jun 1997 20:55:36 -0700 (PDT) Received: (from lars@localhost) by fredriks-1.pr.mcs.net (8.8.5/8.6.6) id WAA00616 for current@freebsd.org; Sun, 22 Jun 1997 22:55:35 -0500 (CDT) From: Lars Fredriksen Message-Id: <199706230355.WAA00616@fredriks-1.pr.mcs.net> Subject: Upping the dmesg buffer To: current@freebsd.org Date: Sun, 22 Jun 1997 22:55:35 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Currently the MSG_BSIZE in /usr/include/sys/msgbuf.h is defined as 8K. Would anyone have huge objections to making this 10-12-14-16K? Right now if you have a fair amount of scsi devices on connected to the machine (particularly if some of those devices have multiple luns) you end up loosing a lot of information ( and that is without the -v option). I set mine currently to 16k and that works fine( just need a rebuild of dmesg), and if this is something that people in general are not willing to spend their memory for, then I'll just have to modify it locally. Just thought I'd ask what others needs are in this regard. Lars -- ------------------------------------------------------------------- Lars Fredriksen fredriks@mcs.com (home) lars@fredriks-1.pr.mcs.net (home-home) From owner-freebsd-current Sun Jun 22 21:07:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA09938 for current-outgoing; Sun, 22 Jun 1997 21:07:52 -0700 (PDT) Received: from whizzo.TransSys.COM (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA09933 for ; Sun, 22 Jun 1997 21:07:48 -0700 (PDT) Received: from localhost.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.TransSys.COM (8.8.5/8.7.3) with SMTP id AAA10947; Mon, 23 Jun 1997 00:07:37 -0400 (EDT) Message-Id: <199706230407.AAA10947@whizzo.TransSys.COM> X-Mailer: exmh version 2.0delta 6/3/97 To: Chuck Robey cc: Daniel Ortmann , freebsd-current@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: list of fast modems? References: In-reply-to: Your message of "Sun, 22 Jun 1997 23:25:58 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Jun 1997 00:07:36 -0400 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Anyhow, when it was time to buy another modem, I checked PC magazine, and > caught their modem review. I was interested in two main things, what it's > error rate in noise was, and what it's tested intercompatibility was. As > I remember, PC magazine disappointed me in not directly testing the error > rate versus noise (BER) but it did give the US Robotics modems pretty good > intercompatibilty ratings. > > I've used Mutlitech modems, and personally tested their BER vs. noise > specs, and liked them. I personally bought USR. Maybe that tells you > something. Be aware, however, there is considerable difference in the quality of the analog front-ends in the USR product lines. The Courier is somewhat better than the wretched Sportster modem. louie From owner-freebsd-current Sun Jun 22 21:12:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA10270 for current-outgoing; Sun, 22 Jun 1997 21:12:17 -0700 (PDT) Received: from proxy4.ba.best.com (root@proxy4.ba.best.com [206.184.139.15]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA10255 for ; Sun, 22 Jun 1997 21:12:05 -0700 (PDT) Received: from bsampley.vip.best.com (bsampley.vip.best.com [206.184.160.196]) by proxy4.ba.best.com (8.8.5/8.8.3) with SMTP id VAA22626; Sun, 22 Jun 1997 21:09:24 -0700 (PDT) Date: Sun, 22 Jun 1997 21:06:17 -0700 (PDT) From: Burton Sampley X-Sender: burton@bsampley.vip.best.com To: support@xig.com cc: current@FreeBSD.org Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-493545271-867038777=:431" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk 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-493545271-867038777=:431 Content-Type: TEXT/PLAIN; charset=US-ASCII Greetings, I just finished installing FBSD 3.0-current with XFree86 3.3. When I attempt to start X (using 'startx') with Accelerated X v3.1 (correctly installed following the documented instructions) I keep getting the following error (actually in attached file). I recently 'nuked' my hard drives and did a new, clean install from the 3.0-SNAP 970618. Has anybody else had this problem (FYI: This message is being sent to both FreeBSD-current mailing list and support@xig.com)? If you've had the problem, what was your solution. X will start if I change the comma's separating the fontpath statements, but I can only use the 'fixed' font and nothing else. Before I 'nuked' my HD's I made a backup of my old /etc/Xaccel.ini file (and a few others). I renamed the new /etc/Xaccel.ini file and copied the old file into the /etc dir. I get the same results. I thought there might be a problem with X, so I D/L'ed the sources (using the ports collectio) and rebuilt X w/ all the fonts and I'm still getting the same results. I'm now out of ideas. Where/what should I do/check next? Thanks in advance, Burton Sampley Oh, BTW, I checked the xig web-page. I didn't see anything in the FAQ regarding XFree86 3.3. --0-493545271-867038777=:431 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="failed.X" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: DQpYYWNjZWwgMy4xIChidWlsZCAzMTAwKSBBY2NlbGVyYXRlZC1YIFNlcnZl ciANCkNvcHlyaWdodCAoYykgMTk5MCw5MSw5Miw5Myw5NCw5NSw5NiBieSBU aG9tYXMgUm9lbGwNCkNvcHlyaWdodCAoYykgMTk5Myw5NCw5NSw5NiAgICAg ICAgICBieSBYIEluc2lkZSBJbmMuDQpBbGwgUmlnaHRzIFJlc2VydmVkDQpV bnB1Ymxpc2hlZCAtLSBSaWdodHMgcmVzZXJ2ZWQgdW5kZXIgdGhlIENvcHly aWdodCBMYXdzIG9mIHRoZSBVbml0ZWQgU3RhdGVzDQoNClVzZXI6ICAgICAg ICAgIEJ1cnRvbiBTYW1wbGV5DQpPcmdhbmlzYXRpb246ICBteSBvd24gY29t cGFueQ0KU2VyaWFsIE51bWJlcjogMTIzMS0wMw0KDQpDb25maWd1cmF0aW9u IGZpbGU6IC9ldGMvWGFjY2VsLmluaQ0KRnJlZUJTRCB1c2luZyAvZGV2L3R0 eXYzDQoNClBDSSAoIzEvMCwgODAwMDAwMGIpDQpNQVRST1gsMTc6IDEwNjRT RyAoNDA5NmsgQGZiODAwMDAwLCBbMC4wMDAgLSAxMzUuMDAwTUh6XSkNCmZh aWxlZCB0byBzZXQgZGVmYXVsdCBmb250IHBhdGggJy91c3IvWDExUjYvbGli L1gxMS9BY2NlbGVyYXRlZFgvZm9udHMvbWlzYy8sL3Vzci9YMTFSNi9saWIv WDExL2ZvbnRzL21pc2MvLC91c3IvWDExUjYvbGliL1gxMS9mb250cy83NWRw aS8sL3Vzci9YMTFSNi9saWIvWDExL2ZvbnRzLzEwMGRwaS8nDQpGYXRhbCBz ZXJ2ZXIgZXJyb3I6DQpjb3VsZCBub3Qgb3BlbiBkZWZhdWx0IGZvbnQgJ2Zp eGVkJw0KWCBjb25uZWN0aW9uIHRvIDowLjAgYnJva2VuIChleHBsaWNpdCBr aWxsIG9yIHNlcnZlciBzaHV0ZG93bikuDQ0K --0-493545271-867038777=:431 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="Xaccel.ini" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Ly8NCi8vIEFjY2VsZXJhdGVkLVggMy4xLCBCdWlsZCAzMTAwDQovLw0KLy8g WGFjY2VsLmluaSBjcmVhdGVkIGF0IFN1biBKdW4gMjIgMTc6NDQ6MjQgMTk5 Nw0KLy8NCg0KW0ZPTlRQQVRIXQ0KICAgICIvdXNyL1gxMVI2L2xpYi9YMTEv QWNjZWxlcmF0ZWRYL2ZvbnRzL21pc2MvIiwNCiAgICAiL3Vzci9YMTFSNi9s aWIvWDExL2ZvbnRzL21pc2MvIiwNCiAgICAiL3Vzci9YMTFSNi9saWIvWDEx L2ZvbnRzLzc1ZHBpLyIsDQogICAgIi91c3IvWDExUjYvbGliL1gxMS9mb250 cy8xMDBkcGkvIjsNCg0KW1JHQlBBVEhdDQogICAgIi91c3IvWDExUjYvbGli L1gxMS9BY2NlbGVyYXRlZFgvZXRjL1hyZ2IiOw0KDQpbU0VUVElOR1NdDQog ICAgU25mRm9ybWF0ID0gSVNDOw0KDQpbS0VZQk9BUkRdDQogICAgTGF5b3V0 ID0gImVuX1VTLnhrbSI7DQoNCltNT1VTRV0NCiAgICBEZXZpY2UgICA9ICIv ZGV2L2N1YWExIjsNCiAgICBQcm90b2NvbCA9IE1pY3Jvc29mdDsNCg0KW1ND UkVFTl0NCiAgICBCb2FyZCAgID0gIm1hdHJveC9tZ2EtbXlzNC54cWEiOw0K ICAgIE1vbml0b3IgPSAibWZyZXEvbWZyZXE2NC52ZGEiOw0KICAgIFZpc3Vh bCAgPSBUcnVlQ29sb3I7DQogICAgRW5lcmd5U3RhciA9IFlFUzsNCiAgICBP dmVybGF5cyA9IFlFUzsNCg0KICAgIFtSRVNPTFVUSU9OU10NCiAgICAgICAg MTE1Mng5MDAsDQogICAgICAgIDEwMjR4NzY4LA0KICAgICAgICA4MDB4NjAw Ow0K --0-493545271-867038777=:431-- From owner-freebsd-current Sun Jun 22 21:28:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA10748 for current-outgoing; Sun, 22 Jun 1997 21:28:59 -0700 (PDT) Received: from shell.uniserve.com (tom@shell.uniserve.com [204.244.210.252]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA10743 for ; Sun, 22 Jun 1997 21:28:53 -0700 (PDT) Received: from localhost (tom@localhost) by shell.uniserve.com (8.8.5/8.8.5) with SMTP id VAA18670; Sun, 22 Jun 1997 21:26:37 -0700 (PDT) X-Authentication-Warning: shell.uniserve.com: tom owned process doing -bs Date: Sun, 22 Jun 1997 21:26:37 -0700 (PDT) From: Tom To: Lars Fredriksen cc: current@FreeBSD.ORG Subject: Re: Upping the dmesg buffer In-Reply-To: <199706230355.WAA00616@fredriks-1.pr.mcs.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 22 Jun 1997, Lars Fredriksen wrote: > Hi, > Currently the MSG_BSIZE in /usr/include/sys/msgbuf.h is defined > as 8K. Would anyone have huge objections to making this 10-12-14-16K? > > Right now if you have a fair amount of scsi devices on connected to the > machine (particularly if some of those devices have multiple luns) you > end up loosing a lot of information ( and that is without the -v option). > > I set mine currently to 16k and that works fine( just need a rebuild of > dmesg), and if this is something that people in general are not willing > to spend their memory for, then I'll just have to modify it locally. > > Just thought I'd ask what others needs are in this regard. > > Lars > -- > ------------------------------------------------------------------- > Lars Fredriksen fredriks@mcs.com (home) > lars@fredriks-1.pr.mcs.net (home-home) > Maybe it should be made into a kernel config item: options "MSGBUF=32767" and make the dmesg source able to deduce the size of the kernel buffer. Tom From owner-freebsd-current Sun Jun 22 21:49:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA11336 for current-outgoing; Sun, 22 Jun 1997 21:49:28 -0700 (PDT) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA11331 for ; Sun, 22 Jun 1997 21:49:24 -0700 (PDT) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with ESMTP id AAA13548; Mon, 23 Jun 1997 00:49:10 -0400 (EDT) Received: from orion.webspan.net (localhost [127.0.0.1]) by orion.webspan.net (WEBSPAN/970608) with ESMTP id AAA03484; Mon, 23 Jun 1997 00:49:09 -0400 (EDT) To: Lars Fredriksen cc: current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: Upping the dmesg buffer In-reply-to: Your message of "Sun, 22 Jun 1997 22:55:35 CDT." <199706230355.WAA00616@fredriks-1.pr.mcs.net> Date: Mon, 23 Jun 1997 00:49:08 -0400 Message-ID: <3481.867041348@orion.webspan.net> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Lars Fredriksen wrote in message ID <199706230355.WAA00616@fredriks-1.pr.mcs.net>: > Currently the MSG_BSIZE in /usr/include/sys/msgbuf.h is defined > as 8K. Would anyone have huge objections to making this 10-12-14-16K? I've been wanting to make a simple change for a while: Put a (read only) variable in sysctl that allows you to read the size of the message buffer. Then remove (or #ifndef out) the #define in msgbuf.h and put it in the kernel config file instead. This allows it to be tunable to local preferences, and without recompiling dmesg (you should recompile syslogd from memory also) Comments? Rotten fruit? Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-current Sun Jun 22 21:57:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA11686 for current-outgoing; Sun, 22 Jun 1997 21:57:31 -0700 (PDT) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA11673 for ; Sun, 22 Jun 1997 21:57:19 -0700 (PDT) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.8.5/8.8.2) id OAA00897; Mon, 23 Jun 1997 14:57:02 +1000 (EST) Message-ID: <19970623145702.17874@rf900.physics.usyd.edu.au> Date: Mon, 23 Jun 1997 14:57:02 +1000 From: David Dawes To: Burton Sampley Cc: current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from Burton Sampley on Sun, Jun 22, 1997 at 09:06:17PM -0700 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, Jun 22, 1997 at 09:06:17PM -0700, Burton Sampley wrote: >I just finished installing FBSD 3.0-current with XFree86 3.3. When I >attempt to start X (using 'startx') with Accelerated X v3.1 (correctly >installed following the documented instructions) I keep getting the >following error (actually in attached file). I recently 'nuked' my hard >drives and did a new, clean install from the 3.0-SNAP 970618. Has anybody >else had this problem (FYI: This message is being sent to both >FreeBSD-current mailing list and support@xig.com)? If you've had the >problem, what was your solution. X will start if I change the comma's >separating the fontpath statements, but I can only use the 'fixed' font >and nothing else. Before I 'nuked' my HD's I made a backup of my old Maybe xig's server doesn't like the gzip'd fonts that come with XFree86 3.3? David From owner-freebsd-current Sun Jun 22 22:07:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA12094 for current-outgoing; Sun, 22 Jun 1997 22:07:42 -0700 (PDT) Received: from fog.XiG.com (drang.xig.com [199.164.187.36]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA12089 for ; Sun, 22 Jun 1997 22:07:37 -0700 (PDT) Received: (from smap@localhost) by fog.XiG.com (8.8.3/8.7.3) id XAA03644; Sun, 22 Jun 1997 23:07:23 -0600 (MDT) X-Authentication-Warning: fog.XiG.com: smap set sender to using -f Received: from devserve.xig.com(192.168.208.222) by fog.XiG.com via smap (V1.3) id sma003637; Sun Jun 22 23:07:15 1997 Received: from chon.xig.com (chon.XiG.com [192.168.128.134]) by devserve.xig.com (8.7.5/8.6.12) with ESMTP id XAA26061; Sun, 22 Jun 1997 23:06:37 -0600 (MDT) Received: (from patrick@localhost) by chon.xig.com (8.8.4/8.6.12) id XAA01822; Sun, 22 Jun 1997 23:06:27 -0600 Date: Sun, 22 Jun 1997 23:06:27 -0600 Message-Id: <199706230506.XAA01822@chon.xig.com> From: Patrick Giagnocavo MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Burton Sampley , current@freebsd.org Subject: Accelerated-X v3.1 and XF86 3.3 In-Reply-To: References: X-Mailer: VM 6.22 under 19.15 XEmacs Lucid Reply-To: support@Xig.com Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Burton Sampley writes: > Greetings, > > I just finished installing FBSD 3.0-current with XFree86 3.3. When I > attempt to start X (using 'startx') with Accelerated X v3.1 (correctly > installed following the documented instructions) I keep getting the > following error (actually in attached file). I recently 'nuked' my hard > drives and did a new, clean install from the 3.0-SNAP 970618. Has anybody > else had this problem (FYI: This message is being sent to both > FreeBSD-current mailing list and support@xig.com)? If you've had the > problem, what was your solution. X will start if I change the comma's > separating the fontpath statements, but I can only use the 'fixed' font > and nothing else. Before I 'nuked' my HD's I made a backup of my old Hello Burton (and FreeBSD-current readers), The problem you are seeing is due to XF86 shipping their fonts in gzipped format. The X server does not know how to uncompress them. This is not of course something that we could know, since v3.1 shipped well before the XF86 release. And it is not something seen when running with AcceleratedX's CDE product, since we ship our own X libs and fonts with this. The solution: unix-prompt> cd /path/to/fonts unix-prompt> rm fonts.dir fonts.alias fonts.scale (note: not all files are necessarily present in each dir) unix-prompt> gzip -d * unix-prompt> compress * unix-prompt> mkfontdir Repeat for each font directory you are going to use - these are listed in the /etc/Xaccel.ini file... Cordially -- Patrick Giagnocavo - support@xig.com Xi Graphics - Accelerated X Servers Technical Support Department From owner-freebsd-current Sun Jun 22 23:34:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA15642 for current-outgoing; Sun, 22 Jun 1997 23:34:13 -0700 (PDT) Received: from baerle.indra.de (root@baerle.indra.de [193.158.1.6]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA15629 for ; Sun, 22 Jun 1997 23:34:07 -0700 (PDT) Received: (from deuerl@localhost) by baerle.indra.de (8.8.5/8.7.3) id IAA04523 for freebsd-current@freebsd.org; Mon, 23 Jun 1997 08:33:00 +0200 (MET DST) From: Robert Deuerling Message-Id: <199706230633.IAA04523@baerle.indra.de> Subject: inetd: login_getclass To: freebsd-current@freebsd.org Date: Mon, 23 Jun 1997 08:32:59 +0200 (MET DST) X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello :-) after upgrading from 2.2.1 to 2.2.2 i got messages on my console: inetd[4353]: login_getclass: unknown class 'root' and su: login_getclass: unknown class 'root' any suggestions how to fix ? -Robert From owner-freebsd-current Mon Jun 23 00:18:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA18233 for current-outgoing; Mon, 23 Jun 1997 00:18:13 -0700 (PDT) Received: from shell.uniserve.com (tom@shell.uniserve.com [204.244.210.252]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA18228 for ; Mon, 23 Jun 1997 00:18:11 -0700 (PDT) Received: from localhost (tom@localhost) by shell.uniserve.com (8.8.5/8.8.5) with SMTP id AAA19068; Mon, 23 Jun 1997 00:15:57 -0700 (PDT) X-Authentication-Warning: shell.uniserve.com: tom owned process doing -bs Date: Mon, 23 Jun 1997 00:15:57 -0700 (PDT) From: Tom To: Robert Deuerling cc: freebsd-current@FreeBSD.ORG Subject: Re: inetd: login_getclass In-Reply-To: <199706230633.IAA04523@baerle.indra.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 23 Jun 1997, Robert Deuerling wrote: > Hello :-) > > after upgrading from 2.2.1 to 2.2.2 i got messages on my console: > > inetd[4353]: login_getclass: unknown class 'root' > and > su: login_getclass: unknown class 'root' > > any suggestions how to fix ? > > -Robert This doesn't belong on freebsd-current. See ERRATA.TXT in the base of the 2.2.2-RELEASE tree. Tom From owner-freebsd-current Mon Jun 23 00:20:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA18422 for current-outgoing; Mon, 23 Jun 1997 00:20:37 -0700 (PDT) Received: from shell.uniserve.com (tom@shell.uniserve.com [204.244.210.252]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA18412 for ; Mon, 23 Jun 1997 00:20:29 -0700 (PDT) Received: from localhost (tom@localhost) by shell.uniserve.com (8.8.5/8.8.5) with SMTP id AAA19074; Mon, 23 Jun 1997 00:18:29 -0700 (PDT) X-Authentication-Warning: shell.uniserve.com: tom owned process doing -bs Date: Mon, 23 Jun 1997 00:18:29 -0700 (PDT) From: Tom To: Daniel Ortmann cc: freebsd-current@FreeBSD.ORG Subject: Re: list of fast modems? In-Reply-To: <199706230231.VAA01183@watcher.isl.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 22 Jun 1997, Daniel Ortmann wrote: > Any recommendations for quick/reliable/common modems for under $200? > > Top 5? > > -- > Daniel Ortmann 507.288.7732 (h) ortmann@isl.net > 2414 30 av NW, #D 507.253.6795 (w) ortmann@vnet.ibm.com > Rochester, MN 55901 "PERL: The Swiss Army Chainsaw" > Look for a modem that is software upgradable. Anything else will be obsolete in year, due to the rapidly shifting 56k standards (X2 vs K56FLEX vs K56PLUS). Tom From owner-freebsd-current Mon Jun 23 01:49:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA22556 for current-outgoing; Mon, 23 Jun 1997 01:49:13 -0700 (PDT) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA22547 for ; Mon, 23 Jun 1997 01:49:08 -0700 (PDT) Received: (from asami@localhost) by vader.cs.berkeley.edu (8.8.5/8.7.3) id BAA08936; Mon, 23 Jun 1997 01:48:55 -0700 (PDT) Date: Mon, 23 Jun 1997 01:48:55 -0700 (PDT) Message-Id: <199706230848.BAA08936@vader.cs.berkeley.edu> To: support@Xig.com CC: burton@bsampey.vip.best.com, current@FreeBSD.ORG In-reply-to: <199706230506.XAA01822@chon.xig.com> (message from Patrick Giagnocavo on Sun, 22 Jun 1997 23:06:27 -0600) Subject: Re: Accelerated-X v3.1 and XF86 3.3 From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * From: Patrick Giagnocavo * unix-prompt> rm fonts.dir fonts.alias fonts.scale ^^^^^^^^^^^ I beg your pardon? Satoshi From owner-freebsd-current Mon Jun 23 03:06:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA26199 for current-outgoing; Mon, 23 Jun 1997 03:06:44 -0700 (PDT) Received: from shadows.aeon.net (shadows.aeon.net [194.100.41.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA26191 for ; Mon, 23 Jun 1997 03:06:33 -0700 (PDT) Received: (from bsdcur@localhost) by shadows.aeon.net (8.8.5/8.8.3) id NAA15233 for current@freebsd.org; Mon, 23 Jun 1997 13:04:48 +0300 (EET DST) From: mika ruohotie Message-Id: <199706231004.NAA15233@shadows.aeon.net> Subject: Re: page fault In-Reply-To: <19970605223427.LN28350@uriah.heep.sax.de> from J Wunsch at "Jun 5, 97 10:34:27 pm" To: current@freebsd.org Date: Mon, 23 Jun 1997 13:04:48 +0300 (EET DST) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [older crash i had] > > #5 0xf0103e2c in cd9660_getattr (ap=0x0) > > at ../../isofs/cd9660/cd9660_vnops.c:253 > It looks suspicious regarding your hardware. If you never touched the > cd9660 filesystem code (which would at least require a previous mount i caught itcrashing again, with a dump... (kgdb) symbol-file kernel.debug Reading symbols from kernel.debug...done. (kgdb) exec-file /var/crash/kernel.3 (kgdb) core-file /var/crash/vmcore.3 IdlePTD 225000 current pcb at 203374 panic: page fault (see, i'm learning =) 'config -g' and 'strip -d' used) #0 boot (howto=256) at ../../kern/kern_shutdown.c:266 266 dumppcb.pcb_cr3 = rcr3(); (kgdb) where #0 boot (howto=256) at ../../kern/kern_shutdown.c:266 #1 0xf011523a in panic (fmt=0xf01c788f "page fault") at ../../kern/kern_shutdown.c:393 #2 0xf01c853a in trap_fatal (frame=0xf521bca3) at ../../i386/i386/trap.c:773 #3 0xf01c7fe9 in trap_pfault (frame=0xf521bca3, usermode=0) at ../../i386/i386/trap.c:680 #4 0xf01c7c1b in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = -267550720, tf_esi = -267976704, tf_ebp = -182338293, tf_isp = -182338357, tf_ebx = 1630872320, tf_edx = 768, tf_ecx = 0, tf_eax = -9021303, tf_trapno = 12, tf_err = 0, tf_eip = -267370639, tf_cs = 8, tf_eflags = 66194, tf_esp = -1759011088, tf_ss = 226492656}) at ../../i386/i386/trap.c:319 #5 0xf0103f71 in cd9660_getattr (ap=0x210620f0) at ../../isofs/cd9660/cd9660_vnops.c:286 #6 0x1d45d8f5 in ?? () Cannot access memory at address 0x21bd40f4. (kgdb) frame 5 #5 0xf0103f71 in cd9660_getattr (ap=0x210620f0) at ../../isofs/cd9660/cd9660_vnops.c:286 286 vap->va_type = vp->v_type; this is again as much as it was listing, nothing more. and it's NOT the first time i see that particular memory address in a crashing message. (0x21bd40f4) it's hardware, right? but if it's the memory, why am i not failing when i make world/kernel, or artificially fill the ram? just _occasionally_ it crashes the machine. my box itself is well cooled, there's an extra 80mm fan and everything feels cool. > cheers, J"org mickey From owner-freebsd-current Mon Jun 23 05:51:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA02389 for current-outgoing; Mon, 23 Jun 1997 05:51:40 -0700 (PDT) Received: (from jmb@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA02383; Mon, 23 Jun 1997 05:51:34 -0700 (PDT) From: "Jonathan M. Bresler" Message-Id: <199706231251.FAA02383@hub.freebsd.org> Subject: Re: mailing list suggestion? To: ortmann@sparc.isl.net (Daniel Ortmann) Date: Mon, 23 Jun 1997 05:51:33 -0700 (PDT) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <199706230245.VAA01232@watcher.isl.net> from "Daniel Ortmann" at Jun 22, 97 09:45:48 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Daniel Ortmann wrote: > > Can majordomo return the standard "echo help | mail majordomo@freebsd.org" > message to users sending directly to the mailing lists? > > (It would be nice if those requests were *not* passed on.) when we originally configured majordomo for the FreeBSD mailing lists we blocked (un)subscribe requests, as well as some others unfortunately the filter to too coarse to be useful without a quasi-moderator jmb From owner-freebsd-current Mon Jun 23 09:32:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA12552 for current-outgoing; Mon, 23 Jun 1997 09:32:56 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA12544 for ; Mon, 23 Jun 1997 09:32:50 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id SAA28227 for ; Mon, 23 Jun 1997 18:32:42 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.4/8.6.12) with UUCP id SAA29933 for current@FreeBSD.ORG; Mon, 23 Jun 1997 18:32:31 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.6/keltia-uucp-2.9) id IAA03941; Mon, 23 Jun 1997 08:16:30 +0200 (CEST) Message-ID: <19970623081629.15883@keltia.freenix.fr> Date: Mon, 23 Jun 1997 08:16:29 +0200 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: Warnings on mysql build References: <33ACA959.5205B0C1@nconnect.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: <33ACA959.5205B0C1@nconnect.net>; from Randall D DuCharme on Sat, Jun 21, 1997 at 11:26:01PM -0500 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3392 AMD-K6 MMX @ 208 MHz Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Randall D DuCharme: > perl: warning: Falling back to the standard locale ("C"). > perl: warning: Setting locale failed. > perl: warning: Please check that your locale settings: > LC_ALL = (unset), > LANG = "us" There is no working "us" locale. Please use either "C" or "en_US". -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #20: Fri Jun 13 00:16:13 CEST 1997 From owner-freebsd-current Mon Jun 23 11:30:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA20377 for current-outgoing; Mon, 23 Jun 1997 11:30:04 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA20363 for ; Mon, 23 Jun 1997 11:30:00 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA01042; Mon, 23 Jun 1997 11:18:33 -0700 From: Terry Lambert Message-Id: <199706231818.LAA01042@phaeton.artisoft.com> Subject: Re: getty modem control To: adam@veda.is (Adam David) Date: Mon, 23 Jun 1997 11:18:33 -0700 (MST) Cc: terry@lambert.org, freebsd-current@FreeBSD.ORG In-Reply-To: <199706212233.WAA19957@veda.is> from "Adam David" at Jun 21, 97 10:33:03 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Typically, command interchange with a modem does not involve data > > exchanges larger than the buffer size. The CTS/RTS should not be > > required until DCD is high, and thus the modem is doing data, not > > command, interchange. > > > > Typically, the symptoms are "no data back from modem until DCD > > is present". If you can't change the modem settings, then you > > will be limited to blind-dialing in all cases. > > I can cu the device and get a normal response without carrier present. > However, getty times out trying to send the data, with no flicker on the > modem TXD. I assume this is your modified getty, since regular getty doesn't send data, right? Look at how 'cu' opens the port. Pay special attention to the CLOCAL and HUPCL settings. Note that you MUST be -CLOCAL, HUPCL for correct dial-in operation (ie: a modem hangup without logout sends SIGHUP to all processes in the process group to cause a logout, and logging out drops DTR to modem to cause it to disconnect). Talking to the modem from getty is evil. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon Jun 23 11:33:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA20646 for current-outgoing; Mon, 23 Jun 1997 11:33:52 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA20641 for ; Mon, 23 Jun 1997 11:33:50 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA01064; Mon, 23 Jun 1997 11:22:09 -0700 From: Terry Lambert Message-Id: <199706231822.LAA01064@phaeton.artisoft.com> Subject: Re: Activehome X10 Interface To: jseger@freebsd.scds.com (Justin M. Seger) Date: Mon, 23 Jun 1997 11:22:08 -0700 (MST) Cc: jseger@freebsd.scds.com, smp@csn.net, current@FreeBSD.ORG In-Reply-To: <199706221309.JAA28424@freebsd.scds.com> from "Justin M. Seger" at Jun 22, 97 09:09:53 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Hi, I think I'd like to try to tackle expanding the xtend daemon to > work with the CM11A. Unfortunatly, > I have very little experience with serial IO. If I could figure out > how to send data to a serial port, and > receive data from a serial port after a RI (ring) signal has been sent. > > Any ideas on where I should start? The "xtend" daemon was already expanded in this way, according to a recent posting to this list. Sorry, but I did not save the posting. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon Jun 23 11:36:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA21007 for current-outgoing; Mon, 23 Jun 1997 11:36:13 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA20999 for ; Mon, 23 Jun 1997 11:36:09 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA01074; Mon, 23 Jun 1997 11:23:25 -0700 From: Terry Lambert Message-Id: <199706231823.LAA01074@phaeton.artisoft.com> Subject: Re: Hmmmm, this is new.. To: rkw@dataplex.net (Richard Wackerbarth) Date: Mon, 23 Jun 1997 11:23:25 -0700 (MST) Cc: julian@whistle.com, jdp@polstra.com, bde@zeta.org.au, jkh@time.cdrom.com, current@FreeBSD.ORG In-Reply-To: from "Richard Wackerbarth" at Jun 22, 97 06:54:28 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >OSF1 builds a separate copy of usr/include and usr/lib > >within the obj tree specifically to use for this. > > This is the kind of approach that we need to take in order to allow a build > to be done on a multi-user or production machine without destroying the > underlying system. Or a cross environment. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon Jun 23 11:36:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA21017 for current-outgoing; Mon, 23 Jun 1997 11:36:14 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA21002 for ; Mon, 23 Jun 1997 11:36:10 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA01086; Mon, 23 Jun 1997 11:25:00 -0700 From: Terry Lambert Message-Id: <199706231825.LAA01086@phaeton.artisoft.com> Subject: Re: list of fast modems? To: ortmann@sparc.isl.net (Daniel Ortmann) Date: Mon, 23 Jun 1997 11:25:00 -0700 (MST) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <199706230231.VAA01183@watcher.isl.net> from "Daniel Ortmann" at Jun 22, 97 09:31:50 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Any recommendations for quick/reliable/common modems for under $200? > > Top 5? I suggest looking at the Hylafax supported modems list (search for "hylafax" in your favorite search engine). I personally agree with their approval of the particualr Zyxel models on their list. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon Jun 23 12:01:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA22470 for current-outgoing; Mon, 23 Jun 1997 12:01:23 -0700 (PDT) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA22465 for ; Mon, 23 Jun 1997 12:01:17 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.5/8.8.5) with ESMTP id MAA06831; Mon, 23 Jun 1997 12:58:25 -0600 (MDT) Message-Id: <199706231858.MAA06831@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: Terry Lambert cc: jseger@freebsd.scds.com (Justin M. Seger), current@FreeBSD.ORG Subject: Re: Activehome X10 Interface In-reply-to: Your message of "Mon, 23 Jun 1997 11:22:08 PDT." <199706231822.LAA01064@phaeton.artisoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Jun 1997 12:58:24 -0600 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, > The "xtend" daemon was already expanded in this way, according to > a recent posting to this list. Sorry, but I did not save the > posting. I just looked over 3.0 src/libexec/xtend/* as supped earlier today and can see no sign of such extensions. It would have needed to have code that opens a serial device instead of /dev/tw (which wouldn't be able to deal with an activehome device). -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD From owner-freebsd-current Mon Jun 23 12:14:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA23209 for current-outgoing; Mon, 23 Jun 1997 12:14:18 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA23203 for ; Mon, 23 Jun 1997 12:14:15 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA01340; Mon, 23 Jun 1997 12:02:37 -0700 From: Terry Lambert Message-Id: <199706231902.MAA01340@phaeton.artisoft.com> Subject: Re: Activehome X10 Interface To: smp@csn.net (Steve Passe) Date: Mon, 23 Jun 1997 12:02:37 -0700 (MST) Cc: terry@lambert.org, jseger@freebsd.scds.com, current@FreeBSD.ORG In-Reply-To: <199706231858.MAA06831@Ilsa.StevesCafe.com> from "Steve Passe" at Jun 23, 97 12:58:24 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > The "xtend" daemon was already expanded in this way, according to > > a recent posting to this list. Sorry, but I did not save the > > posting. > > I just looked over 3.0 src/libexec/xtend/* as supped earlier today and can see > no sign of such extensions. It would have needed to have code > that opens a serial device instead of /dev/tw (which wouldn't be able to > deal with an activehome device). This was code which was announced, but not committed. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon Jun 23 12:14:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA23240 for current-outgoing; Mon, 23 Jun 1997 12:14:50 -0700 (PDT) Received: from veda.is (ubiq.veda.is [193.4.230.60]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA23230 for ; Mon, 23 Jun 1997 12:14:45 -0700 (PDT) Received: (from adam@localhost) by veda.is (8.8.5/8.7.3) id TAA26178; Mon, 23 Jun 1997 19:42:15 GMT From: Adam David Message-Id: <199706231942.TAA26178@veda.is> Subject: Re: getty modem control In-Reply-To: <199706231818.LAA01042@phaeton.artisoft.com> from Terry Lambert at "Jun 23, 97 11:18:33 am" To: terry@lambert.org (Terry Lambert) Date: Mon, 23 Jun 1997 19:42:14 +0000 (GMT) Cc: terry@lambert.org, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I can cu the device and get a normal response without carrier present. > > However, getty times out trying to send the data, with no flicker on the > > modem TXD. > > I assume this is your modified getty, since regular getty doesn't > send data, right? Mods by David Nugent, which have been in the tree for several months now already. Yes, this is a modified gettytab, since the standard gettytab doesn't cause any command data to be sent. > Look at how 'cu' opens the port. Pay special attention to the > CLOCAL and HUPCL settings. > > Note that you MUST be -CLOCAL, HUPCL for correct dial-in operation > (ie: a modem hangup without logout sends SIGHUP to all processes > in the process group to cause a logout, and logging out drops DTR > to modem to cause it to disconnect). Yes, this is probably where we need to be looking. > Talking to the modem from getty is evil. Something has to initialise it (and reassert initialisation). Also it is useful to interact with the modem on RING, CONNECT and hangup events. -- Adam David From owner-freebsd-current Mon Jun 23 12:23:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA23881 for current-outgoing; Mon, 23 Jun 1997 12:23:02 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA23862 for ; Mon, 23 Jun 1997 12:22:49 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA10231; Mon, 23 Jun 1997 21:22:36 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id VAA28200; Mon, 23 Jun 1997 21:21:16 +0200 (MET DST) Message-ID: <19970623212115.CY37600@uriah.heep.sax.de> Date: Mon, 23 Jun 1997 21:21:15 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: current@FreeBSD.ORG Cc: bsdcur@shadows.aeon.net (mika ruohotie) Subject: Re: page fault References: <19970605223427.LN28350@uriah.heep.sax.de> <199706231004.NAA15233@shadows.aeon.net> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199706231004.NAA15233@shadows.aeon.net>; from mika ruohotie on Jun 23, 1997 13:04:48 +0300 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As mika ruohotie wrote: > #6 0x1d45d8f5 in ?? () > Cannot access memory at address 0x21bd40f4. > (kgdb) frame 5 > #5 0xf0103f71 in cd9660_getattr (ap=0x210620f0) > at ../../isofs/cd9660/cd9660_vnops.c:286 > 286 vap->va_type = vp->v_type; > > > this is again as much as it was listing, nothing more. > > and it's NOT the first time i see that particular memory address in > a crashing message. (0x21bd40f4) > > it's hardware, right? No, probably not. But from the above trace, it's not guessable what has been the reason why your memory is trashed (nor is it intelligible for why the cd9660 code has been called at all). Anyway, if you're seeing it with the same failing address, it's not likely hardware. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Jun 23 13:02:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA26715 for current-outgoing; Mon, 23 Jun 1997 13:02:26 -0700 (PDT) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA26704 for ; Mon, 23 Jun 1997 13:02:14 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.5/8.8.5) with ESMTP id OAA07178; Mon, 23 Jun 1997 14:00:24 -0600 (MDT) Message-Id: <199706232000.OAA07178@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: Terry Lambert cc: jseger@freebsd.scds.com (Justin M. Seger), current@FreeBSD.ORG Subject: Re: Activehome X10 Interface In-reply-to: Your message of "Mon, 23 Jun 1997 11:22:08 PDT." <199706231822.LAA01064@phaeton.artisoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Jun 1997 14:00:24 -0600 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, >> > The "xtend" daemon was already expanded in this way, according to >> > a recent posting to this list. Sorry, but I did not save the >> > posting. >> >> I just looked over 3.0 src/libexec/xtend/* as supped earlier today and can see >> no sign of such extensions. It would have needed to have code >> that opens a serial device instead of /dev/tw (which wouldn't be able to >> deal with an activehome device). > >This was code which was announced, but not committed. I searched the list and the only reference I could find that came close was: ------------------------------------- cut ------------------------------------- To: "Justin M. Seger" Cc: current@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: Activehome X10 Interface Date: Sat, 14 Jun 1997 17:06:35 -0400 You need need any special kernel support for the CM11 interface; you just talk to it at 4800 bps. The CM11 is the two-way X10 computer interface with the easy-to-use serial interface. You can dig around and find the protocol description for it. Alternatively, there's a daemon which Dan Lanciani wrote, originally for the Lynx X10 interface and subsequently adapted for the CM11. Essentially, it runs in the background talking to the CM11 with it's mutant "protocol". Your applications each open a TCP connection to the the daemon, and send X10 commands to it ("A1 A ON") to cause X10 commands to be sent. It will also echo any X10 commands it hears to each of the applications which have a connection open to it. I've made some minor changes to it. You can find it on my web server as You'll need to know how X10 power line control stuff works to effectively be able to use this, but you shouldn't have much of a problem tracking that down. ------------------------------------- cut ------------------------------------- could this be the post you are thinking of? -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD From owner-freebsd-current Mon Jun 23 13:44:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA29422 for current-outgoing; Mon, 23 Jun 1997 13:44:02 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA29408 for ; Mon, 23 Jun 1997 13:44:00 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA01609; Mon, 23 Jun 1997 13:32:02 -0700 From: Terry Lambert Message-Id: <199706232032.NAA01609@phaeton.artisoft.com> Subject: Re: Activehome X10 Interface To: smp@csn.net (Steve Passe) Date: Mon, 23 Jun 1997 13:32:02 -0700 (MST) Cc: terry@lambert.org, jseger@freebsd.scds.com, current@FreeBSD.ORG In-Reply-To: <199706232000.OAA07178@Ilsa.StevesCafe.com> from "Steve Passe" at Jun 23, 97 02:00:24 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I searched the list and the only reference I could find that came close was: [ ... ] > could this be the post you are thinking of? Yes. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon Jun 23 13:54:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA29935 for current-outgoing; Mon, 23 Jun 1997 13:54:42 -0700 (PDT) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA29918 for ; Mon, 23 Jun 1997 13:54:27 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.5/8.8.5) with ESMTP id OAA07518; Mon, 23 Jun 1997 14:53:16 -0600 (MDT) Message-Id: <199706232053.OAA07518@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: Terry Lambert cc: jseger@freebsd.scds.com, current@FreeBSD.ORG Subject: Re: Activehome X10 Interface In-reply-to: Your message of "Mon, 23 Jun 1997 13:32:02 PDT." <199706232032.NAA01609@phaeton.artisoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Jun 1997 14:53:15 -0600 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, > > I searched the list and the only reference I could find that came close was: > > [ ... ] > > > could this be the post you are thinking of? > > Yes. I'm really too busy right now to look this code over in detail, but a quick scan failed to find any specific handling of the RI line from the activehome. I think this code polls the serial input every two seconds instead, which is what I suggest avoiding. For background the activehome expects that the PC may be turned off, and tries to get its attention via the RI line. I'm proposing that the proper solution is to attach RI to DCD, and use a signal catcher for SIGHUP to notice when the activehome has data instead of polling the activehome. When/if someone has time to read this code thru could they comment on how this issue is handled in the code? -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD From owner-freebsd-current Mon Jun 23 14:08:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA00554 for current-outgoing; Mon, 23 Jun 1997 14:08:13 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA00548 for ; Mon, 23 Jun 1997 14:08:11 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA01663; Mon, 23 Jun 1997 13:56:49 -0700 From: Terry Lambert Message-Id: <199706232056.NAA01663@phaeton.artisoft.com> Subject: Re: getty modem control To: adam@veda.is (Adam David) Date: Mon, 23 Jun 1997 13:56:49 -0700 (MST) Cc: terry@lambert.org, freebsd-current@FreeBSD.ORG In-Reply-To: <199706231942.TAA26178@veda.is> from "Adam David" at Jun 23, 97 07:42:14 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Talking to the modem from getty is evil. > > Something has to initialise it ... set settings ... AT&W > (and reassert initialisation). ... on-to-off transition of DTR causes modem reset as if powered off then back on ... > Also it is useful to interact with the modem on RING, ... off-to-on transition of RI ... This is most useful if you want to hang pending an inbound call, and *then* chat up the modem to direct the call once it is in progress, but allow outbound connections to occur without process contention for the port in the absence of an inbound call. > CONNECT ... off-to-on DCD transition ... > and hangup events. ... on-to-off DCD transition ... This is not to say that having a modem *driver* capable of caching caller ID (and called-ID) for late retrival of the data, and for multiplexing the modem into "outgoing", "inbound data", "inbound fax", and "inbound voice" as seperate devices so that each of the users of the inbound device can hang pending "DCD" instead of chatting up the modem... would not be useful. Only that your particular arguments for a talkative getty are invalid. 8-). Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon Jun 23 14:10:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA00658 for current-outgoing; Mon, 23 Jun 1997 14:10:36 -0700 (PDT) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA00651 for ; Mon, 23 Jun 1997 14:10:29 -0700 (PDT) Received: (from uucp@localhost) by frmug.org (8.8.5/8.8.5/frmug-2.0) with UUCP id XAA15200 for current@FreeBSD.org; Mon, 23 Jun 1997 23:06:43 +0200 (CEST) Received: (from charnier@localhost) by xp11.frmug.org (8.8.5/8.8.5/xp11-uucp-1.1) id UAA01560; Mon, 23 Jun 1997 20:38:05 +0200 (CEST) Date: Mon, 23 Jun 1997 20:38:05 +0200 (CEST) Message-Id: <199706231838.UAA01560@xp11.frmug.org> From: Philippe Charnier MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: current@FreeBSD.org Subject: boot2 is too big X-Mailer: VM 6.31 under Emacs 19.34.1 Reply-To: charnier@xp11.frmug.org Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hello While running make world this WE, I got: ===> sys/i386/boot/biosboot [...] cc -O2 -malign-functions=0 -malign-jumps=0 -malign-loops=0 -mno-486 -DDO_BAD144 -DBOOTWAIT=5000 -DTIMEOUT= -DBOOTSEG=0x1000 -DBOOTSTACK=0xFFF0 -I/usr/src/sys/i386/boot/biosboot/../../.. -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DBOOT_HD_BIAS=1 -N -T 0 -nostdlib -static -o boot start.o table.o boot2.o boot.o asm.o bios.o serial.o probe_keyboard.o io.o disk.o sys.o cp -p boot boot.strip strip boot.strip size boot.strip text data bss dec hex 7616 96 49052 56764 ddbc dd if=boot.strip of=boot.nohdr ibs=32 skip=1 obs=1024b 241+0 records in 0+1 records out 7712 bytes transferred in 0.007145 secs (1079349 bytes/sec) ls -l boot.nohdr -rw-rw-r-- 1 root bin 7712 Jun 20 21:42 boot.nohdr dd if=boot.nohdr of=boot1 bs=512 count=1 1+0 records in 1+0 records out 512 bytes transferred in 0.000305 secs (1678377 bytes/sec) dd if=boot.nohdr of=boot2 bs=512 skip=1 14+1 records in 14+1 records out 7200 bytes transferred in 0.001929 secs (3732648 bytes/sec) boot2 is too big *** Error code 2 (continuing) `all' not remade because of errors. -- ------ ------ Philippe Charnier charnier@lirmm.fr (smtp) charnier@xp11.frmug.org (uucp) ``a PC not running FreeBSD is like a venusian with no tentacles'' ------------------------------------------------------------------------ From owner-freebsd-current Mon Jun 23 14:22:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA01320 for current-outgoing; Mon, 23 Jun 1997 14:22:12 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA01310 for ; Mon, 23 Jun 1997 14:22:09 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA01692; Mon, 23 Jun 1997 14:10:27 -0700 From: Terry Lambert Message-Id: <199706232110.OAA01692@phaeton.artisoft.com> Subject: Re: Activehome X10 Interface To: smp@csn.net (Steve Passe) Date: Mon, 23 Jun 1997 14:10:27 -0700 (MST) Cc: terry@lambert.org, jseger@freebsd.scds.com, current@FreeBSD.ORG In-Reply-To: <199706232053.OAA07518@Ilsa.StevesCafe.com> from "Steve Passe" at Jun 23, 97 02:53:15 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > could this be the post you are thinking of? > > > > Yes. > > I'm really too busy right now to look this code over in detail, but a quick > scan failed to find any specific handling of the RI line from the activehome. > I think this code polls the serial input every two seconds instead, which > is what I suggest avoiding. For background the activehome expects that the > PC may be turned off, and tries to get its attention via the RI line. I'm > proposing that the proper solution is to attach RI to DCD, and use a signal > catcher for SIGHUP to notice when the activehome has data instead of > polling the activehome. This makes sense... RI is frequently used to wake up "green" machines in "standby" or other APM power-save modes. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon Jun 23 15:17:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA04192 for current-outgoing; Mon, 23 Jun 1997 15:17:33 -0700 (PDT) Received: from veda.is (ubiq.veda.is [193.4.230.60]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA04179 for ; Mon, 23 Jun 1997 15:17:27 -0700 (PDT) Received: (from adam@localhost) by veda.is (8.8.5/8.7.3) id WAA26521; Mon, 23 Jun 1997 22:45:07 GMT From: Adam David Message-Id: <199706232245.WAA26521@veda.is> Subject: Re: getty modem control In-Reply-To: <199706232056.NAA01663@phaeton.artisoft.com> from Terry Lambert at "Jun 23, 97 01:56:49 pm" To: terry@lambert.org (Terry Lambert) Date: Mon, 23 Jun 1997 22:45:06 +0000 (GMT) Cc: terry@lambert.org, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > Talking to the modem from getty is evil. > > > > Something has to initialise it > > ... set settings ... > AT&W AT&W0 > > (and reassert initialisation). > > ... on-to-off transition of DTR causes modem reset as > if powered off then back on ... AT&D3&W0 Sometimes a modem will hang beyond recovery with DTR toggle, or even with actual power-on reset (less likely). This is why it is useful to initialise on port open, rather than during pre-installation. It is undeniably useful to be able to reconfigure the modem by editing a parameter file, and have the new settings take effect on the next open. > > Also it is useful to interact with the modem on RING, > > ... off-to-on transition of RI ... When implemented. > This is most useful if you want to hang pending an inbound call, > and *then* chat up the modem to direct the call once it is in > progress, but allow outbound connections to occur without process > contention for the port in the absence of an inbound call. Exactly my own premise. > > CONNECT > > ... off-to-on DCD transition ... Yes. > > and hangup events. > > ... on-to-off DCD transition ... Yes. My point is that some _software_ has to respond to these events. Yes, it probably belongs in the modem driver, but we don't have a modem driver (yet). > This is not to say that having a modem *driver* capable of caching > caller ID (and called-ID) for late retrival of the data, and for > multiplexing the modem into "outgoing", "inbound data", "inbound > fax", and "inbound voice" as seperate devices so that each of the > users of the inbound device can hang pending "DCD" instead of > chatting up the modem... would not be useful. Definitely. > Only that your particular arguments for a talkative getty are > invalid. 8-). It's the best we have at this stage. There is no modem driver at the moment. -- Adam David From owner-freebsd-current Mon Jun 23 16:22:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA07503 for current-outgoing; Mon, 23 Jun 1997 16:22:42 -0700 (PDT) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA07493 for ; Mon, 23 Jun 1997 16:22:38 -0700 (PDT) Received: from pauling.salk.edu (pauling [198.202.70.108]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id QAA11719 for ; Mon, 23 Jun 1997 16:22:38 -0700 (PDT) Date: Mon, 23 Jun 1997 16:22:35 -0700 (PDT) From: Tom Bartol To: current@freebsd.org Subject: Bad bug in /usr/bin/install?! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi all, I just had the following happen to me in -current and it may be a bug in /usr/bin/install (or it might be me and my Dain Bramage). I just did the following as myself (i.e. not as root): /usr/bin/install -c -s -m 2755 -g kmem xsysinfo /usr/X11R6/bin/xsysinfo Trying to remake and install a fresh version of xsysinfo. The command failed as expected with an "Operation not permitted" but the pre-existing version of xsysinfo was deleted in the process as well!!! I am in group wheel on my system but the pre-existing version of xsysinfo was owned by root.kmem and the permissions on the dir /usr/X11R6/bin are 775 for root.wheel so I guess technically I could delete any file in /usr/X11R6/bin if I wanted to but it's rather nasty that /usr/bin/install deletes a file before checking whether I have permission to perform the other operations that must occur to honor my request to install a file. Or am I just being picky?? (P.S: when I rm a file in /usr/X11R6/bin I at least get prompted "override rw-r--r-- root/wheel for foo_bar?" ) Thanks in advance for flaming my ignorance, Tom From owner-freebsd-current Mon Jun 23 18:48:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA13353 for current-outgoing; Mon, 23 Jun 1997 18:48:42 -0700 (PDT) Received: from istari.flash.net (baasc5-223.flash.net [208.194.198.223]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA13347 for ; Mon, 23 Jun 1997 18:48:39 -0700 (PDT) Received: (from sjr@localhost) by istari.flash.net (8.8.5/8.8.5) id VAA18845 for freebsd-current@FreeBSD.ORG; Mon, 23 Jun 1997 21:48:29 -0400 (EDT) Date: Mon, 23 Jun 1997 21:48:29 -0400 (EDT) From: "Stephen J. Roznowski" Message-Id: <199706240148.VAA18845@istari.flash.net> To: freebsd-current@FreeBSD.ORG Subject: Vanishing PRs? Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I submitted a PR (docs/3875) on 15 Jun 1997, and received a response from FreeBSD-gnats@FreeBSD.ORG. I didn't see this PR in the recent list of open reports and can't seem to query for it on www.freebsd.org. Did some PRs disappear? Thanks, Stephen Roznowski (sjr1@flash.net) From owner-freebsd-current Mon Jun 23 18:53:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA13765 for current-outgoing; Mon, 23 Jun 1997 18:53:14 -0700 (PDT) Received: from istari.flash.net (baasc5-223.flash.net [208.194.198.223]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA13760 for ; Mon, 23 Jun 1997 18:53:10 -0700 (PDT) Received: (from sjr@localhost) by istari.flash.net (8.8.5/8.8.5) id VAA18862 for freebsd-current@FreeBSD.ORG; Mon, 23 Jun 1997 21:53:07 -0400 (EDT) Date: Mon, 23 Jun 1997 21:53:07 -0400 (EDT) From: "Stephen J. Roznowski" Message-Id: <199706240153.VAA18862@istari.flash.net> To: freebsd-current@FreeBSD.ORG Subject: Problem with newsyslog Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Since upgrading to 3.0, I keep getting the following messages from cron: Subject: Cron /usr/sbin/newsyslog /var/log/maillog.0: No such file or directory In /var/log I have: 168 -rw-rw-r-- 1 root bin 157488 Jun 23 21:48 maillog 1 -rw-r--r-- 1 root bin 88 Jun 23 01:00 maillog.0.gz 120 -rw-rw-r-- 1 root bin 114063 Jun 23 01:00 maillog.1 1 -rw-rw-r-- 1 root bin 95 Jun 22 01:00 maillog.2.gz 136 -rw-rw-r-- 1 root bin 127472 Jun 22 01:00 maillog.3 1 -rw-rw-r-- 1 root bin 94 Jun 21 01:00 maillog.4.gz 192 -rw-rw-r-- 1 root bin 187617 Jun 21 01:00 maillog.5 1 -rw-rw-r-- 1 root bin 92 Jun 20 01:00 maillog.6.gz 200 -rw-rw-r-- 1 root bin 189088 Jun 20 01:00 maillog.7 I've deleted all of the file in /var/log, but the problem keeps reappearing.... I know that I'm probably missing something simple, can anyone point me in the right direction? Thanks, Stephen Roznowski (sjr1@flash.net) From owner-freebsd-current Mon Jun 23 20:00:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA17153 for current-outgoing; Mon, 23 Jun 1997 20:00:35 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (ala-ca11-15.ix.netcom.com [199.35.209.175]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA17145 for ; Mon, 23 Jun 1997 20:00:32 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.5/8.6.9) id UAA04271; Mon, 23 Jun 1997 20:00:10 -0700 (PDT) Date: Mon, 23 Jun 1997 20:00:10 -0700 (PDT) Message-Id: <199706240300.UAA04271@silvia.HIP.Berkeley.EDU> To: sjr1@flash.net CC: freebsd-current@freebsd.org In-reply-to: <199706240148.VAA18845@istari.flash.net> (sjr1@flash.net) Subject: Re: Vanishing PRs? From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * To: freebsd-current@freebsd.org What does this have to do with -current? ;) * I submitted a PR (docs/3875) on 15 Jun 1997, and received a response * from FreeBSD-gnats@FreeBSD.ORG. I didn't see this PR in the recent * list of open reports and can't seem to query for it on www.freebsd.org. That is because you marked the PR "confidential: yes". I don't see anything confidential about it so I changed it to "no". It should show up on the list now. Satoshi From owner-freebsd-current Mon Jun 23 20:01:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA17198 for current-outgoing; Mon, 23 Jun 1997 20:01:05 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (ala-ca11-15.ix.netcom.com [199.35.209.175]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA17192 for ; Mon, 23 Jun 1997 20:01:01 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.5/8.6.9) id UAA04277; Mon, 23 Jun 1997 20:00:56 -0700 (PDT) Date: Mon, 23 Jun 1997 20:00:56 -0700 (PDT) Message-Id: <199706240300.UAA04277@silvia.HIP.Berkeley.EDU> To: sjr1@flash.net CC: freebsd-current@freebsd.org In-reply-to: <199706240153.VAA18862@istari.flash.net> (sjr1@flash.net) Subject: Re: Problem with newsyslog From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * I know that I'm probably missing something simple, can anyone point * me in the right direction? How about posting your /etc/newsyslog.conf? Satoshi From owner-freebsd-current Mon Jun 23 20:21:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA17976 for current-outgoing; Mon, 23 Jun 1997 20:21:10 -0700 (PDT) Received: from istari.flash.net (baasc1-21.flash.net [208.194.198.21]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA17969 for ; Mon, 23 Jun 1997 20:21:03 -0700 (PDT) Received: (from sjr@localhost) by istari.flash.net (8.8.5/8.8.5) id XAA19390; Mon, 23 Jun 1997 23:20:50 -0400 (EDT) Date: Mon, 23 Jun 1997 23:20:50 -0400 (EDT) From: "Stephen J. Roznowski" Message-Id: <199706240320.XAA19390@istari.flash.net> To: asami@cs.berkeley.edu Subject: Re: Problem with newsyslog In-Reply-To: Mail from 'asami@cs.berkeley.edu (Satoshi Asami)' dated: Mon, 23 Jun 1997 20:00:56 -0700 (PDT) Cc: freebsd-current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > From: asami@cs.berkeley.edu (Satoshi Asami) > Subject: Re: Problem with newsyslog > > * I know that I'm probably missing something simple, can anyone point > * me in the right direction? > > How about posting your /etc/newsyslog.conf? Here is what I was running: # configuration file for newsyslog # $Id: newsyslog.conf,v 1.11 1997/05/10 05:46:52 brian Exp $ # # logfilename owner.group mode count size time [ZB] [/pid_file] /var/cron/log 600 3 100 * Z #/var/log/amd.log 664 7 100 * Z #/var/log/kerberos.log 664 7 100 * Z /var/log/daemonlog 664 5 100 * Z /var/log/lpd-errs 664 7 100 * Z /var/log/maillog 664 7 * 24 Z /var/log/messages 664 5 100 * Z #/var/log/slip.log 600 3 100 * Z /var/log/ppp.tun0.log 600 3 100 * Z /var/run/ppp.tun0.pid /var/log/wtmp 664 7 * 168 ZB And I've just updated to 1.13... -SR From owner-freebsd-current Mon Jun 23 20:21:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA18025 for current-outgoing; Mon, 23 Jun 1997 20:21:44 -0700 (PDT) Received: from whizzo.TransSys.COM (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA18014 for ; Mon, 23 Jun 1997 20:21:36 -0700 (PDT) Received: from localhost.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.TransSys.COM (8.8.5/8.7.3) with SMTP id XAA22494; Mon, 23 Jun 1997 23:20:30 -0400 (EDT) Message-Id: <199706240320.XAA22494@whizzo.TransSys.COM> X-Mailer: exmh version 2.0delta 6/3/97 To: Steve Passe cc: Terry Lambert , jseger@freebsd.scds.com, current@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: Activehome X10 Interface References: <199706232053.OAA07518@Ilsa.StevesCafe.com> In-reply-to: Your message of "Mon, 23 Jun 1997 14:53:15 MDT." <199706232053.OAA07518@Ilsa.StevesCafe.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Jun 1997 23:20:30 -0400 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I just looked at this code again, and the CM11 protocol specification. I think that the whole RI issue is a bit of a red herring; it's useful in the instance where the attached computer is powered down, and needs to be poked to start up again to handle received X10 traffic. Based on the documentation (and consistent with the code) the RI signal is asserted when an X10 transmission begins to be received. Once the CM11 has received the multibyte sequence, it will begin to poll the computer once per second with a request (single byte of 0x5a) to have it's buffer read. I'm not sure if it makes sense to adapt the xtend program to talk to the CM11 interface, or teach the other daemon tricks. I'm probably going to do neither, and build a front-end with scotty to represent the state of all the x10 devices with a MIB. Applications would interact with it using SNMP. This separates the policy from the device, which seems to be a rather common theme for X10 software. (Given that most of the X10 computer interfaces have their own particular brain-damage, this is hardly surprising.) louie louie From owner-freebsd-current Mon Jun 23 20:51:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA19641 for current-outgoing; Mon, 23 Jun 1997 20:51:39 -0700 (PDT) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA19630 for ; Mon, 23 Jun 1997 20:51:31 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.5/8.8.5) with ESMTP id VAA09063; Mon, 23 Jun 1997 21:49:32 -0600 (MDT) Message-Id: <199706240349.VAA09063@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: "Louis A. Mamakos" cc: Terry Lambert , jseger@freebsd.scds.com, current@FreeBSD.ORG Subject: Re: Activehome X10 Interface In-reply-to: Your message of "Mon, 23 Jun 1997 23:20:30 EDT." <199706240320.XAA22494@whizzo.TransSys.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Jun 1997 21:49:31 -0600 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, > I just looked at this code again, and the CM11 protocol specification. I think > that the whole RI issue is a bit of a red herring; it's useful in the instance > where the attached computer is powered down, and needs to be poked to start up > again to handle received X10 traffic. > > Based on the documentation (and consistent with the code) the RI signal is > asserted when an X10 transmission begins to be received. Once the CM11 has > received the multibyte sequence, it will begin to poll the computer once > per second with a request (single byte of 0x5a) to have it's buffer read. you are correct. I dug up the doc and it basically says it will send POLL bytes once there is data, and that there is no specific responce to the RI signal. So forget my suggestion for handling the RI signal, IGNORE IT! the relevant part of the doc: 3. X-10 Reception. Whenever the interface begins to receive data from the power-line, it will immediately assert the serial ring (RI) signal to initiate the wake-up procedure for the PC. Once the data reception is complete, the interface will begin to poll the PC to upload its data buffer (maximum 10 bytes). If the PC does not respond, then the interface's data buffer will overrun, and additional data will not be stored within the buffer. 3.1 Interface Poll Signal. In order to poll the PC, the interface will continually send: Poll: 7 6 5 4 3 2 1 0 Value: 0 1 0 1 1 0 1 0 (0x5a) This signal will be repeated once every second until the PC responds. 3.2 PC Response to the Poll Signal. To terminate the interface's polling and initiate the data transfer, the PC must send an acknowledgement to the interface's poll signal. This acknowledgement is: Poll: 7 6 5 4 3 2 1 0 Value: 1 1 0 0 0 0 1 1 (0xc3) Notice that bit #2 of the PC transmission is not set, indicating that this cannot be the beginning of a transmission from the PC. 3.3 Interface Serial Data Buffer. The buffer consists of 10 bytes defined as follows: Byte Function 0 Upload Buffer Size 1 Function / Address Mask 2 Data Byte #0 3 Data Byte #1 4 Data Byte #2 5 Data Byte #3 6 Data Byte #4 7 Data Byte #5 8 Data Byte #6 9 Data Byte #7 The interface will only upload the specified number of bytes within the buffer, and will not default to uploading 10 bytes in every transmission. The number of bytes to receive is thus specified in byte 0 of the transmission. The function address mask indicates whether the following 8 bytes should be interpreted as an address or as a function. The position of the bit in the mask corresponds to the byte index within the data buffer. If the bit is set (1), the data byte is defined as a function, and if reset (0), the byte is an address. The data bytes are in the same format as for the Code byte in the X-10 transmissions (i.e. Housecode:Device Code or Housecode:Function). I just put the complete doc in: http://www.freebsd.org/~fsmp/HomeAuto/files/0711prot.txt -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD From owner-freebsd-current Mon Jun 23 22:48:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA24712 for current-outgoing; Mon, 23 Jun 1997 22:48:45 -0700 (PDT) Received: from veda.is (ubiq.veda.is [193.4.230.60]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA24704 for ; Mon, 23 Jun 1997 22:48:40 -0700 (PDT) Received: (from adam@localhost) by veda.is (8.8.5/8.7.3) id GAA27564; Tue, 24 Jun 1997 06:17:09 GMT From: Adam David Message-Id: <199706240617.GAA27564@veda.is> Subject: Re: Upping the dmesg buffer In-Reply-To: <199706240358.WAA03879@fredriks-1.pr.mcs.net> from Lars Fredriksen at "Jun 23, 97 10:58:25 pm" To: lars@fredriks-1.pr.mcs.net (Lars Fredriksen) Date: Tue, 24 Jun 1997 06:17:08 +0000 (GMT) Cc: freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > You lose it all anyway after a certain amount of system errors have occurred. > > Then the only recourse is scanning old logfiles for the boot messages, if > > those logs have not also been rotated out of existence by then. > > > > dmesg is a convenience but will never cover all needs. > > No but it is a handy debugging tool (and its output is saved in /var/log/dmesg..) > So I think it is a worthwhile investment to make it work. > > Lars I agree with you. Yes, /var/run/dmesg.boot was a great idea, and definitely even more reason for this not to overflow the buffer. -- Adam David From owner-freebsd-current Tue Jun 24 01:40:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA03395 for current-outgoing; Tue, 24 Jun 1997 01:40:43 -0700 (PDT) Received: from trifork.gu.net (trifork.gu.net [194.93.190.194]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA03390 for ; Tue, 24 Jun 1997 01:40:37 -0700 (PDT) Received: from localhost (localhost.gu.kiev.ua [127.0.0.1]) by trifork.gu.net (8.8.5/8.8.5) with SMTP id OAA00472; Tue, 24 Jun 1997 14:40:13 +0300 (EEST) Date: Tue, 24 Jun 1997 14:40:13 +0300 (EEST) From: Andrew Stesin Reply-To: stesin@gu.net To: Adam David cc: Terry Lambert , freebsd-current@FreeBSD.ORG Subject: Re: getty modem control In-Reply-To: <199706232245.WAA26521@veda.is> Message-ID: X-NCC-RegID: ua.gu MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 23 Jun 1997, Adam David wrote: > Sometimes a modem will hang beyond recovery with DTR toggle, or even with > actual power-on reset (less likely). This is why it is useful to initialise > on port open, rather than during pre-installation. Make sure your DTE lowers DTR for no less than 8 seconds, 20 seconds is almost bullet-proof. (I had the trouble you are describing, occasionally, on dialin access pools here, they are on cisco 2511. `pulse-time 20' interface command cured the problem almost totally). BTW are FreeBSD init & getty able to arrange this kind of a delay? And if the modem used in a production environment is broken, i.e. loses profiles on reset or powercycle, it should be replaced -- this is plain cheaper than fiddling with it. (That's my opinion, YMMV, sure... ;) > It is undeniably useful to be able to reconfigure the modem by editing a > parameter file, and have the new settings take effect on the next open. I'd doubt this. The only real use for "smart" getty I'm sure about is to catch fax calls. "Dumb" BSD-style getty covers 90% of usage patterns, anyway. Best regards, Andrew Stesin nic-hdl: ST73-RIPE From owner-freebsd-current Tue Jun 24 01:47:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA03637 for current-outgoing; Tue, 24 Jun 1997 01:47:30 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA03629 for ; Tue, 24 Jun 1997 01:47:26 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id SAA13026; Tue, 24 Jun 1997 18:40:49 +1000 Date: Tue, 24 Jun 1997 18:40:49 +1000 From: Bruce Evans Message-Id: <199706240840.SAA13026@godzilla.zeta.org.au> To: charnier@xp11.frmug.org, current@FreeBSD.ORG Subject: Re: boot2 is too big Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >===> sys/i386/boot/biosboot >[...] >cc -O2 -malign-functions=0 -malign-jumps=0 -malign-loops=0 -mno-486 > -DDO_BAD144 -DBOOTWAIT=5000 -DTIMEOUT= -DBOOTSEG=0x1000 -DBOOTSTACK=0xFFF0 > -I/usr/src/sys/i386/boot/biosboot/../../.. -Wreturn-type -Wcomment > -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 > -DBOOT_HD_BIAS=1 -N -T 0 -nostdlib -static -o boot start.o table.o boot2.o > boot.o asm.o bios.o serial.o probe_keyboard.o io.o disk.o sys.o >... >size boot.strip >text data bss dec hex >7616 96 49052 56764 ddbc >... >boot2 is too big The BOOT_HD_BIAS options makes it too big. In fact, almost any nonstandard option would make it too big. You have to remove a standard option, DO_BAD144 perhaps, to get it to fit. I will remove the BOOT_HD_BIAS option soon. Use boot.config instead. Bruce From owner-freebsd-current Tue Jun 24 02:17:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA05155 for current-outgoing; Tue, 24 Jun 1997 02:17:03 -0700 (PDT) Received: from gneiss.eps.nagoya-u.ac.jp (gneiss.eps.nagoya-u.ac.jp [133.6.57.99]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA05148; Tue, 24 Jun 1997 02:16:52 -0700 (PDT) Received: from marble.eps.nagoya-u.ac.jp (localhost [127.0.0.1]) by gneiss.eps.nagoya-u.ac.jp (8.8.5/3.4W4) with ESMTP id SAA09289; Tue, 24 Jun 1997 18:13:37 +0900 (JST) Message-Id: <199706240913.SAA09289@gneiss.eps.nagoya-u.ac.jp> To: current@freebsd.org Cc: kato@migmatite.eps.nagoya-u.ac.jp, dyson@freebsd.org Subject: Re: vm_bounce_alloc: Unmapped page From: KATO Takenori In-Reply-To: Your message of "Tue, 17 Jun 1997 19:24:47 +0900" References: <199706171024.TAA07709@ganko.eps.nagoya-u.ac.jp> X-Mailer: Mew version 1.70 on Emacs 19.28.1 / Mule 2.3 X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 24 Jun 1997 18:13:36 +0900 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As I wrote: > I got `vm_bounce_alloc: Unmapped page' panic when I compiled in > union mounted /usr/src/usr.sbin directory. It seems to be a cluster write related problem. I disabled cluster write by: #ifdef UNION int doclusterwrite = 0; #else int doclusterwrite = 1; #endif Then, I compiled in sbin and usr.sbin and didn't get any problem. ---- KATO Takenori Dept. Earth Planet. Sci., Nagoya Univ., Nagoya, 464-01, Japan PGP public key: finger kato@eclogite.eps.nagoya-u.ac.jp ------------------- Powered by FreeBSD(98) ------------------- From owner-freebsd-current Tue Jun 24 03:09:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA06937 for current-outgoing; Tue, 24 Jun 1997 03:09:15 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA06924; Tue, 24 Jun 1997 03:09:01 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id UAA15443; Tue, 24 Jun 1997 20:00:58 +1000 Date: Tue, 24 Jun 1997 20:00:58 +1000 From: Bruce Evans Message-Id: <199706241000.UAA15443@godzilla.zeta.org.au> To: current@FreeBSD.ORG, kato@migmatite.eps.nagoya-u.ac.jp Subject: Re: vm_bounce_alloc: Unmapped page Cc: dyson@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >It seems to be a cluster write related problem. I disabled cluster >write by: > >#ifdef UNION >int doclusterwrite = 0; >#else >int doclusterwrite = 1; >#endif It is easier to use the sysctl for this (vfs.ffs.doclusterwrite). This is new with Lite2. Only ffs supports this sysctl properly. ext2fs is the only other file system that supports clustered writes, and its doclusterwrite variable is hidden in an ifdef tangle. Bruce From owner-freebsd-current Tue Jun 24 07:25:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA16879 for current-outgoing; Tue, 24 Jun 1997 07:25:05 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA16874 for ; Tue, 24 Jun 1997 07:25:00 -0700 (PDT) Received: from gneiss.eps.nagoya-u.ac.jp (gneiss.eps.nagoya-u.ac.jp [133.6.57.99]) by agora.rdrop.com (8.8.5/8.8.5) with ESMTP id HAA14377 for ; Tue, 24 Jun 1997 07:24:54 -0700 (PDT) Received: from marble.eps.nagoya-u.ac.jp (localhost [127.0.0.1]) by gneiss.eps.nagoya-u.ac.jp (8.8.5/3.4W4) with ESMTP id XAA09857; Tue, 24 Jun 1997 23:22:25 +0900 (JST) Message-Id: <199706241422.XAA09857@gneiss.eps.nagoya-u.ac.jp> To: bde@zeta.org.au Cc: current@FreeBSD.ORG, kato@migmatite.eps.nagoya-u.ac.jp Subject: Re: vm_bounce_alloc: Unmapped page From: KATO Takenori In-Reply-To: Your message of "Tue, 24 Jun 1997 20:00:58 +1000" References: <199706241000.UAA15443@godzilla.zeta.org.au> X-Mailer: Mew version 1.70 on Emacs 19.28.1 / Mule 2.3 X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 24 Jun 1997 23:22:24 +0900 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk From: Bruce Evans Subject: Re: vm_bounce_alloc: Unmapped page Date: Tue, 24 Jun 1997 20:00:58 +1000 > ext2fs is the only other file system that supports clustered writes, > and its doclusterwrite variable is hidden in an ifdef tangle. Why doclusterread and doclusterwrite in ext2fs are macroized? They cannot be changed with sysctl :-(. Does ext2fs have same problem as ufs for accesing unionfs? I cannot test ext2fs by myself becasue I have no Linux partition. ---- KATO Takenori Dept. Earth Planet. Sci., Nagoya Univ., Nagoya, 464-01, Japan PGP public key: finger kato@eclogite.eps.nagoya-u.ac.jp ------------------- Powered by FreeBSD(98) ------------------- From owner-freebsd-current Tue Jun 24 10:00:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA25164 for current-outgoing; Tue, 24 Jun 1997 10:00:52 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA25157 for ; Tue, 24 Jun 1997 10:00:47 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id CAA28490; Wed, 25 Jun 1997 02:59:19 +1000 Date: Wed, 25 Jun 1997 02:59:19 +1000 From: Bruce Evans Message-Id: <199706241659.CAA28490@godzilla.zeta.org.au> To: bde@zeta.org.au, kato@migmatite.eps.nagoya-u.ac.jp Subject: Re: vm_bounce_alloc: Unmapped page Cc: current@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> ext2fs is the only other file system that supports clustered writes, >> and its doclusterwrite variable is hidden in an ifdef tangle. > >Why doclusterread and doclusterwrite in ext2fs are macroized? They >cannot be changed with sysctl :-(. ext2fs is not up to date. >Does ext2fs have same problem as ufs for accesing unionfs? I cannot >test ext2fs by myself becasue I have no Linux partition. I would expect it to have exactly the same problem unless the problem is related to block sizes or fragments. ext2fs is very similar to ufs except for block allocation and mapping. Bruce From owner-freebsd-current Tue Jun 24 10:34:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA26688 for current-outgoing; Tue, 24 Jun 1997 10:34:55 -0700 (PDT) Received: from cabri.obs-besancon.fr (cabri.obs-besancon.fr [193.52.184.3]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA26682 for ; Tue, 24 Jun 1997 10:34:52 -0700 (PDT) Received: by cabri.obs-besancon.fr (5.57/Ultrix3.0-C) id AA03444; Tue, 24 Jun 97 19:34:36 +0100 Date: Tue, 24 Jun 97 19:34:36 +0100 Message-Id: <9706241834.AA03444@cabri.obs-besancon.fr> From: Jean-Marc Zucconi To: freebsd-current@freebsd.org Subject: ncrcontrol X-Mailer: Emacs Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is with a kernel from june, 20 and a freshly rebuilt ncrcontrol: bash# ncrcontrol -u 1 -t 2 -s tags=0 bash# ncrcontrol -u 1 -i T:L Vendor Device Rev Speed Max Wide Tags 2:0 MICROP 4110-09TBCU0322J HT01 10.0 10.0 8 4 It silently ignores the tags=0 parameter :-( Jean-Marc _____________________________________________________________________________ Jean-Marc Zucconi Observatoire de Besancon F 25010 Besancon cedex PGP Key: finger jmz@cabri.obs-besancon.fr ============================================================================= From owner-freebsd-current Tue Jun 24 11:19:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA28602 for current-outgoing; Tue, 24 Jun 1997 11:19:07 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA28595 for ; Tue, 24 Jun 1997 11:18:56 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-46.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA14130 (5.67b/IDA-1.5 for ); Tue, 24 Jun 1997 20:18:52 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id UAA00570; Tue, 24 Jun 1997 20:19:00 +0200 (CEST) X-Face: " Date: Tue, 24 Jun 1997 20:18:59 +0200 From: Stefan Esser To: Jean-Marc Zucconi Cc: freebsd-current@FreeBSD.ORG Subject: Re: ncrcontrol References: <9706241834.AA03444@cabri.obs-besancon.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <9706241834.AA03444@cabri.obs-besancon.fr>; from Jean-Marc Zucconi on Tue, Jun 24, 1997 at 07:34:36PM +0100 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jun 24, Jean-Marc Zucconi wrote: > This is with a kernel from june, 20 and a freshly rebuilt ncrcontrol: > > bash# ncrcontrol -u 1 -t 2 -s tags=0 > bash# ncrcontrol -u 1 -i > T:L Vendor Device Rev Speed Max Wide Tags > 2:0 MICROP 4110-09TBCU0322J HT01 10.0 10.0 8 4 > > It silently ignores the tags=0 parameter :-( Ummm, that's bad ... Seems I broke this when I modified the driver to respect the "NOTAGS" quirk in scsiconf.c ... :( If your drive does not work reliably with tags enabled, then we should add it to scsiconf.c ! The patch for your drive would be: Index: scsiconf.c =================================================================== RCS file: /usr/cvs/src/sys/scsi/scsiconf.c,v retrieving revision 1.89 diff -C2 -r1.89 scsiconf.c *** scsiconf.c 1997/06/11 22:29:01 1.89 --- scsiconf.c 1997/06/24 18:16:23 *************** *** 451,454 **** --- 457,464 ---- { T_DIRECT, T_DIRECT, T_FIXED, "HP", "C372*", "*", + "sd", SC_ONE_LU, SD_Q_NO_TAGS + }, + { + T_DIRECT, T_DIRECT, T_FIXED, "MICROP", "4110*", "*", "sd", SC_ONE_LU, SD_Q_NO_TAGS }, If you want to enable/disable the use of tags at run-time, then you'll wait for me to fix the driver ... Sorry for the inconvenience! Regards, STefan From owner-freebsd-current Tue Jun 24 17:44:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA17419 for current-outgoing; Tue, 24 Jun 1997 17:44:18 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id RAA17414 for ; Tue, 24 Jun 1997 17:44:16 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA03874; Tue, 24 Jun 1997 13:47:48 -0700 From: Terry Lambert Message-Id: <199706242047.NAA03874@phaeton.artisoft.com> Subject: Re: getty modem control To: adam@veda.is (Adam David) Date: Tue, 24 Jun 1997 13:47:47 -0700 (MST) Cc: terry@lambert.org, freebsd-current@FreeBSD.ORG In-Reply-To: <199706232245.WAA26521@veda.is> from "Adam David" at Jun 23, 97 10:45:06 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > ... on-to-off transition of DTR causes modem reset as > > if powered off then back on ... > > Sometimes a modem will hang beyond recovery with DTR toggle, or even with > actual power-on reset (less likely). This is why it is useful to initialise > on port open, rather than during pre-installation. Replace the modem. It is defective. > It is undeniably useful to be able to reconfigure the modem by editing a > parameter file, and have the new settings take effect on the next open. I don't agree with this. Modems should have a single configuration at power on which works for all uses by the machine they are connected to. The reason you have configurability at all is because you can connect the things to different machines/OS's. > > > Also it is useful to interact with the modem on RING, > > > > ... off-to-on transition of RI ... > > When implemented. When not implemented, the hardware is not useful for interacting with the modem on RING. There's no appologizing for broken hardware. > > This is most useful if you want to hang pending an inbound call, > > and *then* chat up the modem to direct the call once it is in > > progress, but allow outbound connections to occur without process > > contention for the port in the absence of an inbound call. > > Exactly my own premise. So make sure RI is implemented on your serial port, and that the SIO driver can interrupt on it, and that the open call can be given a flag to cause it to hang pending RI instead of DCD. > My point is that some _software_ has to respond to these events. Yes, it > probably belongs in the modem driver, but we don't have a modem driver (yet). Well, my point is that if you are going to be hacking out new code to implement a feature, it ought to be good code and not kludge code. > > Only that your particular arguments for a talkative getty are > > invalid. 8-). > > It's the best we have at this stage. There is no modem driver at the moment. It's no harder to implement a modem driver than it is to implement a talkative getty, and the modem driver would introduce far fewer technical complications. It seems an easy call to me. If you are worried about send/expect sequences and whether or not the framework is generic, send me your specification for the grammar for a generic interface, and I'll turn it into Yacc and Lex code for you if you can't do it yourself. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Tue Jun 24 18:10:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA19285 for current-outgoing; Tue, 24 Jun 1997 18:10:54 -0700 (PDT) Received: from istari.flash.net (baasc2-98.flash.net [208.194.198.98]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA19277 for ; Tue, 24 Jun 1997 18:10:46 -0700 (PDT) Received: (from sjr@localhost) by istari.flash.net (8.8.5/8.8.5) id VAA23279 for freebsd-current@FreeBSD.ORG; Tue, 24 Jun 1997 21:10:43 -0400 (EDT) Date: Tue, 24 Jun 1997 21:10:43 -0400 (EDT) From: "Stephen J. Roznowski" Message-Id: <199706250110.VAA23279@istari.flash.net> To: freebsd-current@FreeBSD.ORG Subject: rc.conf vs rc.conf.local Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I was thinking about how "hard" it is to continually modify rc.conf as it is being updated.... I was wondering if anyone can see a problem with treating rc.conf as a set of defaults, and making local overrides in rc.conf.local. Stephen J. Roznowski (sjr1@flash.net) From owner-freebsd-current Tue Jun 24 18:20:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA19931 for current-outgoing; Tue, 24 Jun 1997 18:20:03 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA19879; Tue, 24 Jun 1997 18:19:54 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id KAA26979; Wed, 25 Jun 1997 10:49:42 +0930 (CST) From: Michael Smith Message-Id: <199706250119.KAA26979@genesis.atrad.adelaide.edu.au> Subject: Re: ncrcontrol In-Reply-To: <19970624201859.14377@mi.uni-koeln.de> from Stefan Esser at "Jun 24, 97 08:18:59 pm" To: se@FreeBSD.ORG (Stefan Esser) Date: Wed, 25 Jun 1997 10:49:41 +0930 (CST) Cc: jmz@cabri.obs-besancon.fr, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Stefan Esser stands accused of saying: > On Jun 24, Jean-Marc Zucconi wrote: > > This is with a kernel from june, 20 and a freshly rebuilt ncrcontrol: > > > > bash# ncrcontrol -u 1 -t 2 -s tags=0 > > bash# ncrcontrol -u 1 -i > > T:L Vendor Device Rev Speed Max Wide Tags > > 2:0 MICROP 4110-09TBCU0322J HT01 10.0 10.0 8 4 > > > > It silently ignores the tags=0 parameter :-( > > Ummm, that's bad ... > > Seems I broke this when I modified the driver > to respect the "NOTAGS" quirk in scsiconf.c ... :( > > If your drive does not work reliably with tags > enabled, then we should add it to scsiconf.c ! Please do _not_ add this drive as not supporting tags! silver:~>ncrcontrol T:L Vendor Device Rev Speed Max Wide Tags 0:0 MICROP 4110-09TBCU0322L HT01 10.0 10.0 8 4 2:0 CDC 94181-15 0293 ? 5.0 ? - 3:0 CDC 94181-15 0293 ? 5.0 ? - 4:0 CDC 94181-15 0293 ? 5.0 ? - 5:0 CDC 94181-15 0293 ? 5.0 ? - 6:0 iomega jaz 1GB H.62 10.0 10.0 8 4 This configuration is _very_ stable, and both the 4110 and the Jaz seem to handle tags Just Fine. Of course if I could make the SCSI-1 disks do TCQ as well, I'd be even happier 8) -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Wed Jun 25 01:53:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA11350 for current-outgoing; Wed, 25 Jun 1997 01:53:03 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id BAA11345 for ; Wed, 25 Jun 1997 01:53:00 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-4.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA24959 (5.67b/IDA-1.5 for ); Wed, 25 Jun 1997 10:52:52 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id KAA01589; Wed, 25 Jun 1997 10:52:59 +0200 (CEST) X-Face: " Date: Wed, 25 Jun 1997 10:52:57 +0200 From: Stefan Esser To: "Stephen J. Roznowski" Cc: freebsd-current@FreeBSD.ORG Subject: Re: rc.conf vs rc.conf.local References: <199706250110.VAA23279@istari.flash.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <199706250110.VAA23279@istari.flash.net>; from Stephen J. Roznowski on Tue, Jun 24, 1997 at 09:10:43PM -0400 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jun 24, "Stephen J. Roznowski" wrote: > > I was thinking about how "hard" it is to continually modify rc.conf > as it is being updated.... > > I was wondering if anyone can see a problem with treating rc.conf > as a set of defaults, and making local overrides in rc.conf.local. Is there a different way to do local modifications, at all ? :) Regards, STefan From owner-freebsd-current Wed Jun 25 01:59:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA11659 for current-outgoing; Wed, 25 Jun 1997 01:59:01 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id BAA11654 for ; Wed, 25 Jun 1997 01:58:55 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-4.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA25044 (5.67b/IDA-1.5 for ); Wed, 25 Jun 1997 10:58:39 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id KAA01615; Wed, 25 Jun 1997 10:58:45 +0200 (CEST) X-Face: " Date: Wed, 25 Jun 1997 10:58:43 +0200 From: Stefan Esser To: Michael Smith Cc: jmz@cabri.obs-besancon.fr, freebsd-current@FreeBSD.ORG Subject: Re: ncrcontrol References: <19970624201859.14377@mi.uni-koeln.de> <199706250119.KAA26979@genesis.atrad.adelaide.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <199706250119.KAA26979@genesis.atrad.adelaide.edu.au>; from Michael Smith on Wed, Jun 25, 1997 at 10:49:41AM +0930 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jun 25, Michael Smith wrote: > Stefan Esser stands accused of saying: > > On Jun 24, Jean-Marc Zucconi wrote: > > > This is with a kernel from june, 20 and a freshly rebuilt ncrcontrol: > > > > > > bash# ncrcontrol -u 1 -t 2 -s tags=0 > > > bash# ncrcontrol -u 1 -i > > > T:L Vendor Device Rev Speed Max Wide Tags > > > 2:0 MICROP 4110-09TBCU0322J HT01 10.0 10.0 8 4 > > > > > > It silently ignores the tags=0 parameter :-( > > > > Ummm, that's bad ... > > > > Seems I broke this when I modified the driver > > to respect the "NOTAGS" quirk in scsiconf.c ... :( > > > > If your drive does not work reliably with tags > > enabled, then we should add it to scsiconf.c ! > > Please do _not_ add this drive as not supporting tags! Ok. I was just not sure, why somebody wanted to disable tags for that drive. There definitely is a problem with dynamically adjusting the number of tags, and I know that I introduced it with some other changes, recently :( > silver:~>ncrcontrol > T:L Vendor Device Rev Speed Max Wide Tags > 0:0 MICROP 4110-09TBCU0322L HT01 10.0 10.0 8 4 > 2:0 CDC 94181-15 0293 ? 5.0 ? - > 3:0 CDC 94181-15 0293 ? 5.0 ? - > 4:0 CDC 94181-15 0293 ? 5.0 ? - > 5:0 CDC 94181-15 0293 ? 5.0 ? - > 6:0 iomega jaz 1GB H.62 10.0 10.0 8 4 > > This configuration is _very_ stable, and both the 4110 and the Jaz seem > to handle tags Just Fine. Of course if I could make the SCSI-1 disks > do TCQ as well, I'd be even happier 8) Well, those CDC drives are 1800RPM, 1MB/s, if I remember correctly ? Good drives at their time, but even tagged commands won't hide those ten years that went by, meanwhile :) Regards, STefan From owner-freebsd-current Wed Jun 25 03:26:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA15400 for current-outgoing; Wed, 25 Jun 1997 03:26:33 -0700 (PDT) Received: from korin.warman.org.pl (korin.warman.org.pl [148.81.160.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA15393 for ; Wed, 25 Jun 1997 03:26:16 -0700 (PDT) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.5/8.7.3) with SMTP id MAA00362 for ; Wed, 25 Jun 1997 12:25:36 +0200 (MET DST) Date: Wed, 25 Jun 1997 12:25:36 +0200 (MET DST) From: Andrzej Bialecki To: freebsd-current@freebsd.org Subject: Make world failing (histedit.h) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi! Make world as of today (an hour ago) fails on libedit: [..] cd /usr/src/lib/libedit && make beforeinstall [...] install -C -o bin -g bin -m 444 /usr/src/lib/libedit/histedit.h /usr/include install: /usr/src/lib/libedit/histedit.h: No such file or directory *** Error code 71 Shouldn't it be the "hist.h" instead? Sincerely yours, --- Andrzej Bialecki FreeBSD: Turning PCs Into Workstations http://www.freebsd.org Research and Academic Network in Poland From owner-freebsd-current Wed Jun 25 03:52:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA16505 for current-outgoing; Wed, 25 Jun 1997 03:52:09 -0700 (PDT) Received: from norden1.com (norden1.com [192.153.35.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA16499 for ; Wed, 25 Jun 1997 03:52:06 -0700 (PDT) Received: from hometeam.techpower.net (hometeam@techpower.net [206.244.73.241]) by norden1.com (8.8.5/8.8.5) with ESMTP id GAA01803 for ; Wed, 25 Jun 1997 06:49:20 -0400 (EDT) Received: from localhost (hometeam@localhost) by hometeam.techpower.net (8.8.5/8.8.5) with SMTP id GAA00341 for ; Thu, 26 Jun 1997 06:48:16 -0400 (EDT) Date: Thu, 26 Jun 1997 06:48:15 -0400 (EDT) From: User HOMETEAM To: current@FreeBSD.ORG Subject: pppd Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi all, I noticed this from my console when I connect I am Freebsd and my isp is also. Jun 26 06:24:20 hometeam pppd[176]: CCP: timeout sending Config-Requests My connection is fine no problems I just noticed this. anyone have any idea...? From owner-freebsd-current Wed Jun 25 18:52:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA26869 for current-outgoing; Wed, 25 Jun 1997 18:52:04 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA26844 for ; Wed, 25 Jun 1997 18:52:00 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id LAA03770; Thu, 26 Jun 1997 11:19:51 +0930 (CST) From: Michael Smith Message-Id: <199706260149.LAA03770@genesis.atrad.adelaide.edu.au> Subject: Re: Make world failing (histedit.h) In-Reply-To: from Andrzej Bialecki at "Jun 25, 97 12:25:36 pm" To: abial@korin.warman.org.pl (Andrzej Bialecki) Date: Thu, 26 Jun 1997 11:19:50 +0930 (CST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Andrzej Bialecki stands accused of saying: > > Hi! > > Make world as of today (an hour ago) fails on libedit: > > [..] > cd /usr/src/lib/libedit && make beforeinstall > [...] > install -C -o bin -g bin -m 444 /usr/src/lib/libedit/histedit.h > /usr/include > install: /usr/src/lib/libedit/histedit.h: No such file or directory > *** Error code 71 > > Shouldn't it be the "hist.h" instead? You appear to have fallen into a narrow crack when I was updating the libedit Makefile; update your source tree and try again. The histedit.h file should actually be in /usr/src/include. Sorry for the inconvenience. > Andrzej Bialecki FreeBSD: Turning PCs Into Workstations -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Thu Jun 26 15:24:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA15947 for current-outgoing; Thu, 26 Jun 1997 15:24:52 -0700 (PDT) Received: from freebsd.scds.com (scds.ziplink.net [206.15.128.34]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA15942 for ; Thu, 26 Jun 1997 15:24:42 -0700 (PDT) Received: (from jseger@localhost) by freebsd.scds.com (8.8.5/8.8.5) id SAA16780 for current@freebsd.org; Thu, 26 Jun 1997 18:24:15 -0400 (EDT) Date: Thu, 26 Jun 1997 18:24:15 -0400 (EDT) From: "Justin M. Seger" Message-Id: <199706262224.SAA16780@freebsd.scds.com> To: current@freebsd.org Subject: Adaptec 2920 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Do we currently support the Adaptec 2920 PCI SCSI card? If not, is there a driver in the works? Thanks in advance, -Justin Seger- From owner-freebsd-current Thu Jun 26 21:34:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA03521 for current-outgoing; Thu, 26 Jun 1997 21:34:57 -0700 (PDT) Received: from dolphin.neosoft.com (as5200-port-254.no.neosoft.com [206.27.167.254]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA03508 for ; Thu, 26 Jun 1997 21:34:51 -0700 (PDT) Received: (from conrads@localhost) by dolphin.neosoft.com (8.8.5/8.8.5) id XAA00793 for freebsd-current@freebsd.org; Thu, 26 Jun 1997 23:34:55 -0500 (CDT) Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 26 Jun 1997 23:31:15 -0500 (CDT) Organization: NeoSoft, Inc. From: Conrad Sabatier To: freebsd-current@freebsd.org Subject: CHILD_MAX/OPEN_MAX deprecated? Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Not to be found in LINT. I've been getting "too many open files" errors while running leafnode fetches since upgrading current. Increasing the values of these two variables in my kernel config seems to have no effect. What's the story on this? -- Conrad Sabatier http://www.neosoft.com/~conrads/ From owner-freebsd-current Thu Jun 26 21:45:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA03851 for current-outgoing; Thu, 26 Jun 1997 21:45:16 -0700 (PDT) Received: from dolphin.neosoft.com (as5200-port-254.no.neosoft.com [206.27.167.254]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA03843 for ; Thu, 26 Jun 1997 21:45:11 -0700 (PDT) Received: (from conrads@localhost) by dolphin.neosoft.com (8.8.5/8.8.5) id XAA00817 for freebsd-current@freebsd.org; Thu, 26 Jun 1997 23:45:20 -0500 (CDT) Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 26 Jun 1997 23:42:43 -0500 (CDT) Organization: NeoSoft, Inc. From: Conrad Sabatier To: freebsd-current@freebsd.org Subject: finger date problem Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Please excuse me if this has come up already; just joining the list. Since installing current, finger returns erroneous date info: # finger conrads Login Name TTY Idle Login Time Office Phone conrads Conrad Sabatier p1 Dec 31 1969 Same date every time. My system clock is properly set, and date returns the correct info. -- Conrad Sabatier http://www.neosoft.com/~conrads/ From owner-freebsd-current Thu Jun 26 21:59:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA04176 for current-outgoing; Thu, 26 Jun 1997 21:59:46 -0700 (PDT) Received: from dolphin.neosoft.com (as5200-port-254.no.neosoft.com [206.27.167.254]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA04149 for ; Thu, 26 Jun 1997 21:59:36 -0700 (PDT) Received: (from conrads@localhost) by dolphin.neosoft.com (8.8.5/8.8.5) id XAA00876 for freebsd-current@FreeBSD.ORG; Thu, 26 Jun 1997 23:59:43 -0500 (CDT) Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 26 Jun 1997 23:58:39 -0500 (CDT) Organization: NeoSoft, Inc. From: Conrad Sabatier To: freebsd-current@FreeBSD.ORG Subject: RE: CHILD_MAX/OPEN_MAX deprecated? Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 27-Jun-97 Conrad Sabatier wrote: >Not to be found in LINT. I've been getting "too many open files" errors >while running leafnode fetches since upgrading current. Increasing the >values of these two variables in my kernel config seems to have no effect. OK, found the answer in /usr/src/sys/kern/kern_opt.c. -- Conrad Sabatier http://www.neosoft.com/~conrads/ From owner-freebsd-current Thu Jun 26 22:45:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA05244 for current-outgoing; Thu, 26 Jun 1997 22:45:29 -0700 (PDT) Received: from forbidden-donut.anet-stl.com (forbidden-donut.anet-stl.com [206.114.203.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA05239 for ; Thu, 26 Jun 1997 22:45:27 -0700 (PDT) Received: from localhost (doogie@localhost) by forbidden-donut.anet-stl.com (8.8.6/8.8.5) with SMTP id AAA29394; Fri, 27 Jun 1997 00:42:18 GMT Date: Fri, 27 Jun 1997 00:42:14 +0000 (GMT) From: Jason Young To: Conrad Sabatier cc: freebsd-current@FreeBSD.ORG Subject: Re: finger date problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- On Thu, 26 Jun 1997, Conrad Sabatier wrote: > Please excuse me if this has come up already; just joining the list. > > Since installing current, finger returns erroneous date info: > > # finger conrads > Login Name TTY Idle Login Time Office Phone > conrads Conrad Sabatier p1 Dec 31 1969 > > Same date every time. My system clock is properly set, and date returns > the correct info. Recompile finger. The utmp/wtmp formats changed to deal with 16 char login names in -current. You will need to do this with any program that interacts with utmp or wtmp. ason Young ANET Technical Staff -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBM7MMaaInE6ybC66VAQGKEgL/cr73xuixFrx3oiKDZnmYsWqayBUxseca iMw3PuoRZXhA8TngUJEpKQzp8ZX1cF45NXARzhLVTNJ/gpkTjj8QMNTN2cHaLTm2 4EzYW1xJsZpgUPcszEATv7FSVwh5LNNK =cBpA -----END PGP SIGNATURE----- From owner-freebsd-current Fri Jun 27 01:52:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA12311 for current-outgoing; Fri, 27 Jun 1997 01:52:15 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id BAA12295 for ; Fri, 27 Jun 1997 01:52:04 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA14588; Fri, 27 Jun 1997 10:51:43 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id KAA26187; Fri, 27 Jun 1997 10:39:53 +0200 (MET DST) Message-ID: <19970627103953.OU49248@uriah.heep.sax.de> Date: Fri, 27 Jun 1997 10:39:53 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: current@FreeBSD.ORG Cc: jseger@freebsd.scds.com (Justin M. Seger) Subject: Re: Adaptec 2920 References: <199706262224.SAA16780@freebsd.scds.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199706262224.SAA16780@freebsd.scds.com>; from Justin M. Seger on Jun 26, 1997 18:24:15 -0400 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Justin M. Seger wrote: > Do we currently support the Adaptec 2920 PCI SCSI card? If not, is there a > driver in the works? I've got a driver contribution by Michael Ranner, but never made up my mind about where the various files should go to. It seems this driver is using some NetBSD-imported SCSI infrastructure (went there from the PAO distribution). I feel guilty for not importing it yet... -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Fri Jun 27 11:50:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA07505 for current-outgoing; Fri, 27 Jun 1997 11:50:36 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA07499 for ; Fri, 27 Jun 1997 11:50:32 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA24283 for ; Fri, 27 Jun 1997 11:29:25 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd024277; Fri Jun 27 18:29:15 1997 Message-ID: <33B4062C.773C2448@whistle.com> Date: Fri, 27 Jun 1997 11:27:56 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: current@freebsd.org Subject: osreldate.h HELP I give up Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk my -current machine NEVER has built a "Make World" correctl for months because I always have to hand push it past "osreldate.h: No such file or directory." the damned thing is there The sources make it but things dont seem to find it is there something funny about this file? was there an upgrade step I missed 3 months ago? sources are up-to-date via cvSUP. julian From owner-freebsd-current Sat Jun 28 05:11:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA18186 for current-outgoing; Sat, 28 Jun 1997 05:11:07 -0700 (PDT) Received: from shadows.aeon.net (bsdcur@shadows.aeon.net [194.100.41.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA18181 for ; Sat, 28 Jun 1997 05:11:03 -0700 (PDT) Received: (from bsdcur@localhost) by shadows.aeon.net (8.8.5/8.8.3) id PAA23523; Sat, 28 Jun 1997 15:11:15 +0300 (EET DST) From: mika ruohotie Message-Id: <199706281211.PAA23523@shadows.aeon.net> Subject: Re: osreldate.h HELP I give up In-Reply-To: <33B4062C.773C2448@whistle.com> from Julian Elischer at "Jun 27, 97 11:27:56 am" To: julian@whistle.com (Julian Elischer) Date: Sat, 28 Jun 1997 15:11:15 +0300 (EET DST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > my -current machine NEVER has built a "Make World" > correctl for months because I always have to > hand push it past > "osreldate.h: No such file or directory." hmm? i havent been able to complete world in ages coz of the tcl prob, but it's been the only one biting me from like february. and i make world weekly... ofcourse, since i use '-k' even the tcl doesnt stop me. general question, i assume that tcl thing is a "true" problem, anyone got anything that'd solve it? mickey From owner-freebsd-current Sat Jun 28 06:08:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA19187 for current-outgoing; Sat, 28 Jun 1997 06:08:53 -0700 (PDT) Received: from aleste.lovett.com (aleste.lovett.com [193.195.45.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id GAA19182 for ; Sat, 28 Jun 1997 06:08:47 -0700 (PDT) Received: from aleste.lovett.com [193.195.45.10] by aleste.lovett.com with esmtp (Exim 1.62 #1) id 0whxF5-0003Xz-00; Sat, 28 Jun 1997 14:08:43 +0100 To: freebsd-current@freebsd.org Subject: 3.0-current issues (build 97-06-28) Organization: Demon Internet Ltd. Reply-To: ade@demon.net Date: Sat, 28 Jun 1997 14:08:42 +0100 From: Ade Lovett Message-Id: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi all, this is my first posting here, so please be gentle :) I'm currently experimenting with a relatively large FreeBSD/SMP box as a dedicated nnrp server, with a remote NFS-mounted spool over FDDI. Machine is a PR440FX motherboard, with dual Intel Pentium-Pro 200MHz processors, 512Mb of main memory, Adaptec 3940 SCSI controller, a couple of DC21040 ethernet cards, and a DEFPA FDDI adapter. With kernel options: maxusers 512 options "MAXMEM=(512*1024)" I'm seeing a number of panic: kmem_malloc: kmem_map too small under even moderate network load (maybe 70 or so nnrp daemons, the machine should theoretically cope with at least 400 of them, with our modified news setup here) Looking back through the mailing list archives, the only references I can find to this type of panic have had suggested solutions about raising the NMBCLUSTERS option to 4096 (or so). Looking at the crash dumps of this machine, I see that nmbclusters is set to 8704 (which ties in with the code in conf/param.c) What am I doing wrong here? I've been beating my head against walls for a couple of days now with no success. -aDe -- Ade Lovett, Demon Internet Ltd. From owner-freebsd-current Sat Jun 28 06:41:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA19864 for current-outgoing; Sat, 28 Jun 1997 06:41:27 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA19857 for ; Sat, 28 Jun 1997 06:41:24 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with SMTP id GAA27918; Sat, 28 Jun 1997 06:42:07 -0700 (PDT) Message-Id: <199706281342.GAA27918@implode.root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: ade@demon.net cc: freebsd-current@FreeBSD.ORG Subject: Re: 3.0-current issues (build 97-06-28) In-reply-to: Your message of "Sat, 28 Jun 1997 14:08:42 BST." From: David Greenman Reply-To: dg@root.com Date: Sat, 28 Jun 1997 06:42:07 -0700 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >Hi all, this is my first posting here, so please be gentle :) > >I'm currently experimenting with a relatively large FreeBSD/SMP >box as a dedicated nnrp server, with a remote NFS-mounted spool >over FDDI. > >Machine is a PR440FX motherboard, with dual Intel Pentium-Pro 200MHz >processors, 512Mb of main memory, Adaptec 3940 SCSI controller, >a couple of DC21040 ethernet cards, and a DEFPA FDDI adapter. > >With kernel options: > > maxusers 512 > options "MAXMEM=(512*1024)" > >I'm seeing a number of > panic: kmem_malloc: kmem_map too small Find VM_KMEM_SIZE in /sys/i386/include/vmparam.h and double it to 64MB. The next problem you'll encounter is running out of kernel virtual memory, but hopefully you'll get by for now. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Sat Jun 28 10:11:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA27206 for current-outgoing; Sat, 28 Jun 1997 10:11:51 -0700 (PDT) Received: from korin.warman.org.pl (korin.warman.org.pl [148.81.160.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA27200 for ; Sat, 28 Jun 1997 10:11:46 -0700 (PDT) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.5/8.7.3) with SMTP id TAA04607; Sat, 28 Jun 1997 19:11:06 +0200 (MET DST) Date: Sat, 28 Jun 1997 19:11:06 +0200 (MET DST) From: Andrzej Bialecki To: mika ruohotie cc: Julian Elischer , current@FreeBSD.ORG Subject: Re: osreldate.h HELP I give up In-Reply-To: <199706281211.PAA23523@shadows.aeon.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 28 Jun 1997, mika ruohotie wrote: > > my -current machine NEVER has built a "Make World" > > correctl for months because I always have to > > hand push it past > > "osreldate.h: No such file or directory." > > hmm? > > i havent been able to complete world in ages coz of the tcl prob, > but it's been the only one biting me from like february. and i > make world weekly... Strange. I completed "make world" about two weeks ago with none of the above. I mean, there were no problems at all - I typed "make world" and then returned some 3 hours later to see "Make world completed". Of course tcl things are made as well :-) There are problems, though, with making world with -current sources on 2.2.2 machine. I think something wrongly assumes certain things about environment (such as existing /usr/include files). Sincerely yours, --- Andrzej Bialecki FreeBSD: Turning PCs Into Workstations http://www.freebsd.org Research and Academic Network in Poland From owner-freebsd-current Sat Jun 28 15:47:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA07299 for current-outgoing; Sat, 28 Jun 1997 15:47:52 -0700 (PDT) Received: from aleste.lovett.com (root@aleste.lovett.com [193.195.45.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA07294 for ; Sat, 28 Jun 1997 15:47:48 -0700 (PDT) Received: from aleste.lovett.com [193.195.45.10] (ade) by aleste.lovett.com with esmtp (Exim 1.62 #1) id 0wi6HH-00006Q-00; Sat, 28 Jun 1997 23:47:35 +0100 To: dg@root.com cc: freebsd-current@freebsd.org Subject: Re: 3.0-current issues (build 97-06-28) Organization: Demon Internet Ltd. Reply-To: ade@demon.net In-reply-to: Your message of "Sat, 28 Jun 1997 06:42:07 PDT." <199706281342.GAA27918@implode.root.com> Date: Sat, 28 Jun 1997 23:47:35 +0100 From: Ade Lovett Message-Id: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk David Greenman writes: > > Find VM_KMEM_SIZE in /sys/i386/include/vmparam.h and double it to 64MB. The >next problem you'll encounter is running out of kernel virtual memory, but >hopefully you'll get by for now. Many thanks, that seems to be working now (at least, the machine hasn't crashed in 6 hours or so, which is one hell of a lot better than previously :) And now, for another query. With the current -current, pstat -T falls over as follows: aleste 101# pstat -T 179/4136 files pstat: sysctl: KERN_VNODE: No such file or directory with a little bit of tracking down, this would appear to be because of the following code in sys/kern/vfs_subr.c, line 1858: ---------------------------------------------------------------------- /* * XXX * Exporting the vnode list on large systems causes them to crash. * Exporting the vnode list on medium systems causes sysctl to coredump. */ #if 0 SYSCTL_PROC(_kern, KERN_VNODE, vnode, CTLTYPE_OPAQUE|CTLFLAG_RD, 0, 0, sysctl_vnode, "S,vnode", ""); #endif ---------------------------------------------------------------------- This isn't really a big problem for me, since I only use pstat -T as a way of tracking swap file usage, and I can use swapinfo instead, but I'm a little confused as to why something that *seemed* to work flawlessy in 2.2.2-RELEASE has been commented out in 3.0-CURRENT. -aDe -- Ade Lovett, Demon Internet Ltd. From owner-freebsd-current Sat Jun 28 16:44:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA08815 for current-outgoing; Sat, 28 Jun 1997 16:44:52 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA08810 for ; Sat, 28 Jun 1997 16:44:50 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id QAA02926; Sat, 28 Jun 1997 16:45:37 -0700 (PDT) Message-Id: <199706282345.QAA02926@implode.root.com> To: ade@demon.net cc: freebsd-current@freebsd.org Subject: Re: 3.0-current issues (build 97-06-28) In-reply-to: Your message of "Sat, 28 Jun 1997 23:47:35 BST." From: David Greenman Reply-To: dg@root.com Date: Sat, 28 Jun 1997 16:45:37 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >And now, for another query. > >With the current -current, pstat -T falls over as follows: > > aleste 101# pstat -T > 179/4136 files > pstat: sysctl: KERN_VNODE: No such file or directory > >with a little bit of tracking down, this would appear to be because >of the following code in sys/kern/vfs_subr.c, line 1858: > >---------------------------------------------------------------------- >/* > * XXX > * Exporting the vnode list on large systems causes them to crash. > * Exporting the vnode list on medium systems causes sysctl to coredump. > */ >#if 0 >SYSCTL_PROC(_kern, KERN_VNODE, vnode, CTLTYPE_OPAQUE|CTLFLAG_RD, > 0, 0, sysctl_vnode, "S,vnode", ""); >#endif >---------------------------------------------------------------------- > >This isn't really a big problem for me, since I only use pstat -T >as a way of tracking swap file usage, and I can use swapinfo instead, Huh? That should be "pstat -s" to look at swap usage. >but I'm a little confused as to why something that *seemed* to work >flawlessy in 2.2.2-RELEASE has been commented out in 3.0-CURRENT. I was the one who commented it out. It caused sysctl on systems the size of yours to coredump, and caused systems larger than yours to panic. The vnode table on wcarchive, for instance, is 45000 entries large and the mechanism that is used to copy all of the many megabytes of kernel data structures out to the user process simply can't handle things this large. There are also security concerns when exporting detailed information about open files. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Sat Jun 28 16:58:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA09090 for current-outgoing; Sat, 28 Jun 1997 16:58:35 -0700 (PDT) Received: from aleste.lovett.com (root@aleste.lovett.com [193.195.45.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id QAA09085 for ; Sat, 28 Jun 1997 16:58:33 -0700 (PDT) Received: from aleste.lovett.com [193.195.45.10] (ade) by aleste.lovett.com with esmtp (Exim 1.62 #1) id 0wi7Nr-000086-00; Sun, 29 Jun 1997 00:58:27 +0100 To: dg@root.com cc: freebsd-current@freebsd.org Subject: Re: 3.0-current issues (build 97-06-28) Organization: Demon Internet Ltd. Reply-To: ade@demon.net In-reply-to: Your message of "Sat, 28 Jun 1997 16:45:37 PDT." <199706282345.QAA02926@implode.root.com> Date: Sun, 29 Jun 1997 00:58:26 +0100 From: Ade Lovett Message-Id: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk David Greenman writes: > >I wrote: >>This isn't really a big problem for me, since I only use pstat -T >>as a way of tracking swap file usage, and I can use swapinfo instead, > > Huh? That should be "pstat -s" to look at swap usage. Sorry, what I meant to say was that I grabbed the output of pstat -T at regular intervals as one way of keeping a track of overall system 'load' -- not just on FreeBSD boxes, but other (shock! horror! :) OS's as well. One of the stats that I was mainly interested in was swapfile usage, but the other numbers help as well. > I was the one who commented it out. It caused sysctl on systems the size of >yours to coredump, and caused systems larger than yours to panic. The vnode >table on wcarchive, for instance, is 45000 entries large and the mechanism >that is used to copy all of the many megabytes of kernel data structures out >to the user process simply can't handle things this large. There are also >security concerns when exporting detailed information about open files. Understood. The only question that remains is should the pstat source be modified to remove the offending sysctl() so that it at least returns a full (as much as possible) set of information, instead of barfing on the KERN_VNODE sysctl() ?? -aDe -- Ade Lovett, Demon Internet Ltd. From owner-freebsd-current Sat Jun 28 21:03:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA15504 for current-outgoing; Sat, 28 Jun 1997 21:03:05 -0700 (PDT) Received: from pent.vnet.net (pent.vnet.net [166.82.194.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA15498; Sat, 28 Jun 1997 21:02:40 -0700 (PDT) Received: from pent (localhost [127.0.0.1]) by pent.vnet.net (8.8.5/8.8.5) with ESMTP id AAA29410; Sun, 29 Jun 1997 00:02:05 -0400 (EDT) Message-Id: <199706290402.AAA29410@pent.vnet.net> To: freebsd-ports@freebsd.org From: "Adam W. Hawks" Reply-to: awhawks@vnet.net cc: freebsd-current@freebsd.org Subject: xfmail problems in current Date: Sun, 29 Jun 1997 00:02:04 -0400 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk xfmail will not compile in current. it gives the following errors. bash# make >> Checksum OK for xfmail-1.0.tar.gz. ===> Extracting for xfmail-1.0 ===> xfmail-1.0 depends on shared library: Xpm\.4\. - found ===> xfmail-1.0 depends on shared library: xforms\.0\. - found ===> Patching for xfmail-1.0 ===> Applying FreeBSD patches for xfmail-1.0 ===> Configuring for xfmail-1.0 ===> Building for xfmail-1.0 Warning: Object directory not changed from original /usr/ports/mail/xfmail/work/xfmail/ui cc -Wall -O2 -I../compface -DFACES -I/usr/X11R6/include -I/usr/X11R6/include/X11 -DUSE_SOUND -DHS_MADVISE -I. -I../mail -I../pixmap -I../editor -c xfmail.c xfmail.c: In function `display_msg': xfmail.c:209: warning: passing arg 2 of `fl_show_question' makes integer from pointer without a cast xfmail.c:209: too many arguments to function `fl_show_question' xfmail.c:211: warning: passing arg 2 of `fl_show_question' makes integer from pointer without a cast xfmail.c:211: too many arguments to function `fl_show_question' xfmail.c: In function `preemptive_handler': xfmail.c:430: warning: implicit declaration of function `ringbell' *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. bash# So I figured I would install the package. Below is the errors in current when I run the package. bash# xfmail XFMail 1.0 p0 - Xwindows e-mail client for FreeBSD (C) 1995,1996 Gennady B. Sorokopud Compiled at Tue Mar 25 05:42:43 PST 1997 by root@leia.cs.berkeley.edu X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 2 (X_ChangeWindowAttributes) Resource id in failed request: 0x0 Serial number of failed request: 816 Current serial number in output stream: 825 bash# I hope this gets fixed soon because it is my most used mail reader. Thanks Adam W. Hawks From owner-freebsd-current Sat Jun 28 22:44:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA18620 for current-outgoing; Sat, 28 Jun 1997 22:44:25 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id WAA18615 for ; Sat, 28 Jun 1997 22:44:21 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wiCm6-0002fL-00; Sat, 28 Jun 1997 23:43:50 -0600 To: Andrzej Bialecki Subject: Re: osreldate.h HELP I give up Cc: mika ruohotie , Julian Elischer , current@freebsd.org In-reply-to: Your message of "Sat, 28 Jun 1997 19:11:06 +0200." References: Date: Sat, 28 Jun 1997 23:43:49 -0600 From: Warner Losh Message-Id: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message Andrzej Bialecki writes: : Strange. I completed "make world" about two weeks ago with none of the : above. I mean, there were no problems at all - I typed "make world" and : then returned some 3 hours later to see "Make world completed". Of course : tcl things are made as well :-) Hmmm. I can't do a make resintall w/o doing it -k. Trouble is that we can't install off of a binary tree that isn't read/write :-(. At least I've hit a few bogons in this area. Next time I do it, I'll have to see if I can find what is going on and fix it... Warner