From owner-freebsd-current Sun Mar 21 0:48:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 4C65E150EB; Sun, 21 Mar 1999 00:48:26 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id AAA09712; Sun, 21 Mar 1999 00:48:07 -0800 (PST) (envelope-from dillon) Date: Sun, 21 Mar 1999 00:48:07 -0800 (PST) From: Matthew Dillon Message-Id: <199903210848.AAA09712@apollo.backplane.com> To: Brian Feldman , Alfred Perlstein , "John S. Dyson" , samit@usa.ltindia.com, commiters@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: rfork() References: <199903210743.XAA09505@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is an example only. It takes a *BUNCH* of arcane assembly to make it work. I would suggest *EXTREME* caution when using a completely cloned address space such as RFPROC|RFMEM generate. Normal library calls cannot be made by the child safely. Thread libraries will also not work since they expect the pthread model. This is not portable. The assembly is designed for ELF libraries. -Matt /* * FTEST.C */ #include #include #include #include void fubar(void *data); int main(int ac, char **av) { pid_t pid; int stackSize = 64 * 1024; char *stack = malloc(stackSize); volatile int v = 0; printf("parent pid %d\n", (int)getpid()); fflush(stdout); pid = ffork(fubar, &v, stack, stackSize); printf("child pid returned to parent %d\n", pid); /* * If stack is not split, then child should be able to * increment v. */ for (;;) { sleep(1); printf("%d\n", v); } exit(1); } void fubar(void *data) { int *pdata = data; for (;;) ++*pdata; _exit(0); } /* * FFORK.S */ .globl ffork .text /* * ffork(func, data, stack, stackSize) */ ffork: /* * Setup stack frame for new stack and store in register * which will not be destroyed by call to rfork, %ebx. * * newsp -> func * data */ pushl %ebx movl 12+4(%esp),%ebx addl 16+4(%esp),%ebx subl $16,%ebx /* newsp = %ebx = stack + stackSize - 16 */ movl 4+4(%esp),%eax movl %eax,0(%ebx) /* func */ movl 8+4(%esp),%eax movl %eax,4(%ebx) /* data */ /* * Call rfork() syscall. This is arcane I'm afraid because we cannot * use a 'call' due to possible stack reuse by one or the other * process. Instead we do a direct syscall. * * %edx is returned non-zero to the child, zero to the parent. %eax * is returned as the child pid to the parent, and garbage to the * child. */ pushl $48 /* RFPROC|RFMEM */ pushl $0 /* dummy */ movl $0xfb,%eax /* rfork syscall number */ int $0x80 /* syscall */ cmpl $0,%edx /* edx returns 0 to parent, pid in %eax */ jne child /* * parent returns pid of child in %eax ( returned by syscall ), and * controls original stack. */ addl $8,%esp /* scrap syscall args */ popl %ebx /* pop saved registers */ ret /* return to parent */ /* * child must run function in new stack frame without messing with * old stack frame ( which might already be popped and reused by the * parent ) */ child: movl %ebx,%esp /* switch stacks */ movl %esp,%ebp /* setup new frame pointer */ popl %eax /* pop function address */ call *%eax /* call function */ jmp __exit /* system exit on return*/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 1:50:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 6D6D415064 for ; Sun, 21 Mar 1999 01:50:56 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id KAA37222; Sun, 21 Mar 1999 10:50:25 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903210950.KAA37222@freebsd.dk> Subject: Re: How to add a new bootdevice to the new boot code ??? In-Reply-To: <199903201930.LAA12494@dingo.cdrom.com> from Mike Smith at "Mar 20, 1999 11:30:31 am" To: mike@smith.net.au (Mike Smith) Date: Sun, 21 Mar 1999 10:50:24 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Mike Smith wrote: > > > But hey, I don't have the time to work on ATAPI. Soren does, so he gets > > > to call the shots. > > > > Right :) > > ... so we lose. 8( Well, depends on POV I guess... > Soren, please take a little time to understand what Justin is talking > about. The parts of CAM that are relevant to you are the queueing > support, infrastructure, and the separation between the "interface > controller" and the "peripheral driver", something that you've > indicated to me several times that you simply don't grasp. The main driving force here is that I want as much performance as I can possibly get out of modern ATA/ATAPI hardware, plus have a driver as simple as possible to arrive at that goal. However, all that I've been doing so far is to get the lowlevel code redone so probes are faster etc etc, all the highlevel code is more or less reused old hat things for now. There is nothing that hinders anyone in doing all the (apparently) needed changes to CAM, and have it call what I've (re)done so far. However I dont have any plans for that on my whiteboard *currently*. If consensus can be reached that shows that the project is not interested in it being done this way, please, just tell me and I'll pack up my bits, I can deal with having yet another set of patches locally. Can you grasp that ?? (yes offence taken). > Taking advantage of all the code and design that's already been > implemented in the CAM framework will make your life easier, not > harder. It's not necessary to write a translation layer at all, if > such a thing offends your sensibilities. Maybe, later, but I still need to get all the lowlevel stuff into shape, and have it working on you average ATA/ATAPI iron, which is not exactly trivial, I need support for DMA on god knows which different PCI chipsets, I need the lowlevel code to deal with ATA4's braindead way of doing tagged queuing, etc etc etc.. Then when all this is working we can talk about having the top layer(s) redone in the CAM way or what we have at that point in time. OK ?? -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 1:58:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id A8B2914F9B for ; Sun, 21 Mar 1999 01:58:51 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id KAA37231; Sun, 21 Mar 1999 10:58:28 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903210958.KAA37231@freebsd.dk> Subject: Re: How to add a new bootdevice to the new boot code ??? In-Reply-To: <199903210109.SAA77557@pluto.plutotech.com> from "Justin T. Gibbs" at "Mar 20, 1999 6: 0:45 pm" To: gibbs@plutotech.com (Justin T. Gibbs) Date: Sun, 21 Mar 1999 10:58:28 +0100 (CET) Cc: gibbs@plutotech.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Justin T. Gibbs wrote: > >> My main complaint so far about the new ATAPI stuff is that it duplicates > >> or lacks (assuming it will be implemented) much of what CAM would have > >> given for almost free: > >> > >> - Interrupt driven configuration > > > >That there allready, if we mean the same thing here. > > Right. Its duplicated functionality. Nope, not exactly.. > >> - Peripheral driver to device routing > > > >Such as ? > > Such as the ability to have more than one driver share the > same device, command generation counts and priority queuing > to allow correct 'replay' of overlapped commands when an > error occurs, etc. See: > > http://www.freebsd.org/~gibbs/cam.html That will probably need changes to work with ATA4's tagged queing at least... > >> - an extensible error recovery framework > > > >Well, here is room for improvement, I haven't put any real error > >checking code in there by now, it will just fail and report that > >for now. This is alpha level code remember. > > But how will you deal with errors especially when there are overlapped > commands? CAM already deals with this in a very clean way. When an error > occurs, the controller driver freezes the queue of commands to the erring > device, notifies the peripheral driver of the error, and allows the driver > to insert error recovery actions before any other commands are ever > released to the device. This even allows you to toss back unexecuted but > queued commands at the controller level to be reinserted into the transport > layer's command queue to ensure proper ordering. This all plays off of the > priority features inherent in how transactions are queued. > > Command queuing was a major factor in why I wrote the CAM code. Solving > these issues is not trivial. Agreed, but have you looked at how ATA4 handles queing ?? > >> - an aplication pass-thru interface > > > >Hmm, what for ?? > > cdrecord, a userland disk format utility, camcontrol functionality, > etc. etc. He he, ATAPI dont need cdrecord as all ATAPI burners use the same command set (MMC), where your average SCSI burner has its own propietary command set (well, the ATA/ATAPI guys did get one thing right :) ), There might be an idea for formatting utils for LS120/ZIP drives, ATA harddisks should not be formatted, in fact the ignore the command more or less. OK, I'm done discussing this (se my other mail), I'd rater spend my (very limitted) time productively. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 2: 6:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 37525152AF; Sun, 21 Mar 1999 02:06:24 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id LAA37275; Sun, 21 Mar 1999 11:06:03 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903211006.LAA37275@freebsd.dk> Subject: Re: unable to use cdrecord on an ATAPI CD-R under 2.2.8. In-Reply-To: <000101be72e8$061d1160$0a00000a@maxpower.weeble.nws.net> from "Christopher J. Michaels" at "Mar 20, 1999 10:40:45 am" To: cjm2@earthling.net (Christopher J. Michaels) Date: Sun, 21 Mar 1999 11:06:03 +0100 (CET) Cc: questions@FreeBSD.ORG, alec@nikts.nk.ukrtel.net, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Christopher J. Michaels wrote: > Well, I'm sorry to say that it looks like I've found the answer to my own > question. I found after this posting (by looking at dmesg) that I was > getting the following error. > acd0: rezero failed > > I did some searching and found several postings in -current that said my > drive, a MITSUMI CR-2600TE, does not support the REZERO command and is > therefore not going to work, at least with the acd driver I have running > now. You could try to change the rezero function with a call to the start device function instead, that should work. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 2:48:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from nomad.dataplex.net (nomad.dataplex.net [216.140.184.163]) by hub.freebsd.org (Postfix) with ESMTP id DFC9E14EEC for ; Sun, 21 Mar 1999 02:48:27 -0800 (PST) (envelope-from rkw@dataplex.net) Received: from localhost (rkw@localhost) by nomad.dataplex.net (8.9.2/8.9.2) with ESMTP id EAA53750; Sun, 21 Mar 1999 04:48:05 -0600 (CST) (envelope-from rkw@dataplex.net) X-Authentication-Warning: nomad.dataplex.net: rkw owned process doing -bs Date: Sun, 21 Mar 1999 04:48:05 -0600 (CST) From: Richard Wackerbarth Reply-To: rkw@dataplex.net To: "Scot W. Hetzel" Cc: FreeBSD-Current Subject: Re: Possible fix for rc.conf In-Reply-To: <004001be732c$7960e0e0$8dfee0d1@westbend.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why do we need to have ANY of the file inclusion in /etc/defaults/rc.conf? Shouldn't that file simply be definitions of variables? IMHO, the "logic" should be in "rc" itself. On Sat, 20 Mar 1999, Scot W. Hetzel wrote: > What does everyone think about using this at the end of > /etc/defaults/rc.conf? > > for i in ${rc_conf_files}; do > if [ $0 != $i ]; then > if [ -f $i ]; then > . $i > fi > else > echo "Error: $0 isn't allowed to re-load $i." > echo "Error: Please do not copy /etc/defaults/rc.conf to > /etc/rc.conf" > fi > done > > If someone does copy the /etc/defaults/rc.conf to /etc/rc.conf, /etc/rc.conf > will not reload it's self, thus it will never get stuck in an endless loop. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 3:39:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from gina.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id BFEC514FA3; Sun, 21 Mar 1999 03:39:14 -0800 (PST) (envelope-from root@neland.dk) Received: from gina (gina [192.168.0.14]) by gina.neland.dk (8.9.3/8.9.3) with ESMTP id MAA11393; Sun, 21 Mar 1999 12:39:07 +0100 (CET) (envelope-from root@neland.dk) Date: Sun, 21 Mar 1999 12:39:07 +0100 (CET) From: Leif Neland To: freebsd-isp@freebsd.org, freebsd-current@freebsd.org Subject: frontpage and current 4.0 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A quick crossposted letter; continue in the most appropriate group at your choice. Will frontpage (fp30.bsdi3.tar.Z) run on current 4.0? I tried building apache13-fp from the ports. I had to edit apache's configure to accept the parameter i386--freebsd4.0 (I guess it should be i386-unknown-freebsd4.0) to compile. But fpsrvadm.exe just dumps core when make install runs. So is current 4.0 and fp30 compatible? leif@neland.dk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 4:39:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail5.svr.pol.co.uk (mail5.svr.pol.co.uk [195.92.193.20]) by hub.freebsd.org (Postfix) with ESMTP id 8A5E814E26; Sun, 21 Mar 1999 04:39:34 -0800 (PST) (envelope-from pierre.dampure@k2c.co.uk) Received: from modem-62.manganese.dialup.pol.co.uk ([62.136.12.62] helo=k2c.co.uk) by mail5.svr.pol.co.uk with esmtp (Exim 2.12 #1) id 10OhSX-0004O5-00; Sun, 21 Mar 1999 12:36:05 +0000 Message-ID: <36F4E756.7B43F050@k2c.co.uk> Date: Sun, 21 Mar 1999 12:34:30 +0000 From: "Pierre Y. Dampure" Organization: K2C Limited X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en, ja MIME-Version: 1.0 To: Leif Neland Cc: freebsd-isp@freebsd.org, freebsd-current@freebsd.org Subject: Re: frontpage and current 4.0 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Leif Neland wrote: > > But fpsrvadm.exe just dumps core when make install runs. > > So is current 4.0 and fp30 compatible? > Some mods were recently committed to cater for support of large (in terms of RAM) systems; these break BSDI compatibility and might be the root of your problems. Best Regards, PYD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 5:24:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 32FA414F53; Sun, 21 Mar 1999 05:24:53 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id OAA33154; Sun, 21 Mar 1999 14:23:18 +0100 (CET) (envelope-from des) To: Leif Neland Cc: freebsd-isp@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: frontpage and current 4.0 References: From: Dag-Erling Smorgrav Date: 21 Mar 1999 14:23:17 +0100 In-Reply-To: Leif Neland's message of "Sun, 21 Mar 1999 12:39:07 +0100 (CET)" Message-ID: Lines: 9 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Leif Neland writes: > Will frontpage (fp30.bsdi3.tar.Z) run on current 4.0? Only if your kernel is configured for a 256 MB address space. See section 13.15 in the FAQ for instructions on how to do this. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 5:48:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from tuminfo2.informatik.tu-muenchen.de (tuminfo2.informatik.tu-muenchen.de [131.159.0.81]) by hub.freebsd.org (Postfix) with ESMTP id 90FD114F53; Sun, 21 Mar 1999 05:48:22 -0800 (PST) (envelope-from langd@informatik.tu-muenchen.de) Received: from hpsystem14.informatik.tu-muenchen.de ([131.159.4.9] EHLO hpsystem14.informatik.tu-muenchen.de ident: root [port 2809]) by tuminfo2.informatik.tu-muenchen.de with ESMTP id <109623-225>; Sun, 21 Mar 1999 14:47:52 +0000 Received: from langd@localhost (fake: hprbg4.informatik.tu-muenchen.de) by hpsystem14.informatik.tu-muenchen.de id <12059-467>; Sun, 21 Mar 1999 14:47:38 +0100 Message-ID: <19990321144736.A21933@informatik.tu-muenchen.de> Date: Sun, 21 Mar 1999 14:47:36 +0100 From: Daniel Lang To: current@freebsd.org, questions@freebsd.org Subject: make release fails Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hiho, I'm using a 3.1-STABLE system, up to date with a current CVS-tree. No I would like to install a few other boxes as well, so I thought 'make release' would be the thing. I set the RELEASETAG to RELENG_3, make release then seems to run fine, until it wants to build kerberosIV. This fails with 'don't know how to make k_getpwuid.c' (or similar). Now the thing is, I'm not USA_RESDIDENT, so I don't have Kerberos installed, and I don't want it in the release anyway. I tried to set 'NOKERBEROS', 'NOCRYPT', etc, but it doesn't seem to work. But I have to admit, that I made a 'make rerelease' after the build broke down. I didn't want it to remove the whole chroot-tree and check the whole stuff out again, since this takes AGES (even on my sort of fast machine). If anyone has any hints, how to avoid building kerberos, preferrably without having to do a 'make release' and set the trees up from scratch again, I would be grateful. Any other general hints for 'make release' or some more documentation apart from /usr/src/release/Makefile would be nice, as well. Btw, I'm not subscribed to any of the mailing-lists, I'd rather browse the archives. So if anyone likes to answer, please include a cc: to my personal address, or at least give me hint like 'Watch the ...-list' or 'You _should_ be subscribed to ...'. Cheers, Daniel -- IRCnet: Mr-Spock - Agartim billiard bumba m'abdul in papejim twista - rumba rock n rolla. Leik'ab mai. Spirzon Heroin se'osit gaula. - - Marijuana esit gaula. Haschisch. Opis. - RL: Daniel Lang * dl@leo.org * +49 89 8540017 * http://www.leo.org/~dl/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 6: 2: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from zone.syracuse.net (zone.syracuse.net [209.2.141.6]) by hub.freebsd.org (Postfix) with ESMTP id 72F0A14FA3; Sun, 21 Mar 1999 06:02:03 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by zone.syracuse.net (8.9.2/8.9.2) with ESMTP id OAA01195; Sun, 21 Mar 1999 14:01:31 GMT (envelope-from green@unixhelp.org) Date: Sun, 21 Mar 1999 14:01:31 +0000 (GMT) From: Brian Feldman X-Sender: green@zone.syracuse.net To: Matthew Dillon Cc: Alfred Perlstein , "John S. Dyson" , samit@usa.ltindia.com, commiters@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: rfork() In-Reply-To: <199903210743.XAA09505@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 20 Mar 1999, Matthew Dillon wrote: > > :> > rfork(RFMEM) doesn't easily work from C. You need to > :> > create an assembly stub. > :> > > :> > -- > :> > John | Never try to teach a pig to sing, > :> > dyson@iquest.net | it makes one look stupid > :> > jdyson@nc.com | and it irritates the pig. > :> > > :> > :> I've seen about 6 people ask about this because the manual lies about > :> what is done. I asked a while back about it, and John was kind enough > :> to dig up some code that used rfork to properly split the stack should > :> I try to dig it up? > :> > :> In the meantime, can someone commit this or suggest something? > : > :For the suggest something, you realize that with Richard's VM_STACK code it > :should be relatively trivial to make this automatic (suggestion: add > :RFSTACK flag). > : > : Brian Feldman _ __ ___ ___ ___ > : green@unixhelp.org _ __ ___ | _ ) __| \ > : http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | > : FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ > > If the goal is to completely share the address space, which > RFMEM does, you can't split anything, not even the stack. It > sure would be useful if there were a standard clib call adequate > for calling rfork() and calling a function in the child w/ a new > stack. Hence the NEW flag RFSTACK. Why would this be a bad thing? This would keep the old behavior and allow much nicer new behavior. I didn't suggest changing the old behavior. This would just greatly simplify things so all of the assembly wouldn't be needed. Hmm... actually... if one were to mmap() a stack and as soon as the rfork() returned movl newstack,%esp and whatnot, wouldn't this be a pretty simple solution? > > -Matt > Matthew Dillon > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 6:10:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (Postfix) with ESMTP id 51036150F1 for ; Sun, 21 Mar 1999 06:10:43 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.3/8.9.3) id IAA48935; Sun, 21 Mar 1999 08:08:41 -0600 (CST) (envelope-from dick) Date: Sun, 21 Mar 1999 08:08:41 -0600 From: "Richard Seaman, Jr." To: Matthew Dillon Cc: Brian Feldman , Alfred Perlstein , "John S. Dyson" , samit@usa.ltindia.com, freebsd-current@FreeBSD.ORG Subject: Re: rfork() Message-ID: <19990321080841.E32029@tar.com> References: <199903210743.XAA09505@apollo.backplane.com> <199903210848.AAA09712@apollo.backplane.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=oJ71EGRlYNjSvfq7 X-Mailer: Mutt 0.95.4i In-Reply-To: <199903210848.AAA09712@apollo.backplane.com>; from Matthew Dillon on Sun, Mar 21, 1999 at 12:48:07AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --oJ71EGRlYNjSvfq7 Content-Type: text/plain; charset=us-ascii On Sun, Mar 21, 1999 at 12:48:07AM -0800, Matthew Dillon wrote: > This is an example only. It takes a *BUNCH* of arcane assembly to make > it work. > > I would suggest *EXTREME* caution when using a completely cloned address > space such as RFPROC|RFMEM generate. Normal library calls cannot be made > by the child safely. Thread libraries will also not work since they > expect the pthread model. > > This is not portable. The assembly is designed for ELF libraries. The linux threads "port" at http://lt.tar.com/linuxthreads.tar.gz contains an implementation of a linux clone call using rfork. An alternative assembly language interface to rfork, originally posted to -hackers by John Dyson last summer, is attached. This was part of a larger posting of some kthread code. Check the mail archives for the complete posting by John on August 20, titled "rfork stuff", which includes an example using thr_fork. No reason I can see that thr_fork and/or "clone" couldn't be added to libc. -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 --oJ71EGRlYNjSvfq7 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="rf.S" .file "rf.S" #include #include "DEFS.h" #include "SYS.h" #define KERNEL #include #undef KERNEL #undef DEBUG /* * 8 12 16 20 24 28 * thr_fork(flags, stack, startrtn, startarg, userrtn, arg); * * flags: RF* flags for rfork in unistd.h. * subr: subroutine to run as a thread. * stack: top of stack for thread. * arg: argument to thread. */ .stabs "rf.S",100,0,0,Ltext0 .text Ltext0: .type CNAME(thrfork),@function .stabd 68,0,1 ENTRY(thrfork) pushl %ebp movl %esp, %ebp pushl %esi /* * Push thread info onto the new thread's stack */ movl 12(%ebp), %esi / get stack addr subl $4, %esi movl 28(%ebp), %eax / get user argument movl %eax, (%esi) subl $4, %esi movl 24(%ebp), %eax / get user thread address movl %eax, (%esi) subl $4, %esi movl 20(%ebp), %eax / get internal argument movl %eax, (%esi) subl $4, %esi movl 16(%ebp), %eax / get internal subroutine movl %eax, (%esi) .stabd 68,0,2 /* * Prepare and execute rfork */ pushl 8(%ebp) pushl %esi leal SYS_rfork, %eax KERNCALL jb 2f .stabd 68,0,3 /* * Check to see if we are in the parent or child */ cmpl $0, %edx jnz 1f addl $8, %esp popl %esi movl %ebp, %esp popl %ebp ret .p2align 2 /* * If we are in the child (new thread), then * set-up the call to the internal subroutine. If it * returns, then call _exit. */ .stabd 68,0,4 1: movl %esi,%esp #ifdef DEBUG movl %esp, _stackaddr movl (%esp), %eax movl %eax, _stack movl 4(%esp), %eax movl %eax,_stack+4 movl 8(%esp), %eax movl %eax,_stack+8 movl 12(%esp), %eax movl %eax,_stack+12 #endif popl %eax #ifdef DEBUG movl %eax,_fcn #endif call %eax addl $12, %esp /* * Exit system call */ call PIC_PLT(_exit) .stabd 68,0,5 2: addl $8, %esp popl %esi movl %ebp, %esp popl %ebp jmp PIC_PLT(HIDENAME(cerror)) .stabs "thrfork:f67",36,0,6,CNAME(thrfork) Lfe1: .size CNAME(thrfork),Lfe1-CNAME(thrfork) #ifdef DEBUG .data .globl _stack _stack: .long 0 .long 0 .long 0 .long 0 .long 0 .globl _stackaddr _stackaddr: .long 0 .globl _fcn _fcn: .long 0 #endif --oJ71EGRlYNjSvfq7 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="thrfork.h" #include extern pid_t thrfork(int flags, caddr_t stack_top, void (*internal_fn)(void *, int (*)(void *), void*), void *internal_arg, int (*user_fn)(void *), void * user_arg); --oJ71EGRlYNjSvfq7-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 6:40:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id 84AA115060 for ; Sun, 21 Mar 1999 06:40:56 -0800 (PST) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id AAA17366; Mon, 22 Mar 1999 00:40:17 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) by ren.detir.qld.gov.au via smap (3.2) id xma017360; Mon, 22 Mar 99 00:39:48 +1000 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id AAA21503; Mon, 22 Mar 1999 00:39:48 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id AAA02692; Mon, 22 Mar 1999 00:39:47 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost.detir.qld.gov.au [127.0.0.1]) by nymph.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id AAA06704; Mon, 22 Mar 1999 00:39:46 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199903211439.AAA06704@nymph.detir.qld.gov.au> To: Richard Wackerbarth Cc: freebsd-current@freebsd.org, syssgm@detir.qld.gov.au Subject: Re: Possible fix for rc.conf References: In-Reply-To: from Richard Wackerbarth at "Sun, 21 Mar 1999 04:48:05 -0600" Date: Mon, 22 Mar 1999 00:39:46 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 21st March 1999, Richard Wackerbarth wrote: >Why do we need to have ANY of the file inclusion in /etc/defaults/rc.conf? >Shouldn't that file simply be definitions of variables? >IMHO, the "logic" should be in "rc" itself. Yeah! What he said! Having code in rc.conf sucks. If there is no logic, there can be no recursion. If you are going to mix code into rc.conf you may as well just suck it back into /etc/rc and get rid of it entirely. (*) Stephen. (*) Which is silly, of course. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 6:42:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5]) by hub.freebsd.org (Postfix) with ESMTP id 03ED915131; Sun, 21 Mar 1999 06:42:12 -0800 (PST) (envelope-from mmercer@ipass.net) Received: from ipass.net (ts3-186-ppp.ipass.net [207.120.205.186]) by pluto.ipass.net (8.9.1a/8.9.1) with ESMTP id JAA05887; Sun, 21 Mar 1999 09:38:16 -0500 (EST) Message-ID: <36F504F1.2F64CA2@ipass.net> Date: Sun, 21 Mar 1999 09:40:49 -0500 From: "Michael E. Mercer" Reply-To: mmercer@ipass.net X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Daniel Lang Cc: current@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: make release fails References: <19990321144736.A21933@informatik.tu-muenchen.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel, I'm guessing here, but check your existing make.conf file in /etc against the one in /usr/src/etc/make.conf. I know the newer one has an option MAKE_KERBEROSIV. See if that helps... As far as how to start where it failed, I have no idea..SORRY. I would like to know that myself. later Michael Mercer Daniel Lang wrote: > > Hiho, > > I'm using a 3.1-STABLE system, up to date with a current > CVS-tree. > No I would like to install a few other boxes as well, so I > thought 'make release' would be the thing. > > I set the RELEASETAG to RELENG_3, > make release then seems to run fine, until it wants to > build kerberosIV. This fails with > 'don't know how to make k_getpwuid.c' (or similar). > > Now the thing is, I'm not USA_RESDIDENT, so I don't have > Kerberos installed, and I don't want it in the release > anyway. I tried to set 'NOKERBEROS', 'NOCRYPT', etc, > but it doesn't seem to work. > But I have to admit, that I made a 'make rerelease' after > the build broke down. I didn't want it to remove the whole > chroot-tree and check the whole stuff out again, since this > takes AGES (even on my sort of fast machine). > > If anyone has any hints, how to avoid building kerberos, > preferrably without having to do a 'make release' and set > the trees up from scratch again, I would be grateful. > > Any other general hints for 'make release' or some > more documentation apart from /usr/src/release/Makefile > would be nice, as well. > > Btw, I'm not subscribed to any of the mailing-lists, I'd rather > browse the archives. So if anyone likes to answer, please include > a cc: to my personal address, or at least give me hint like > 'Watch the ...-list' or 'You _should_ be subscribed to ...'. > > Cheers, > Daniel > -- > IRCnet: Mr-Spock - Agartim billiard bumba m'abdul in papejim twista > - rumba rock n rolla. Leik'ab mai. Spirzon Heroin se'osit gaula. - > - Marijuana esit gaula. Haschisch. Opis. - > RL: Daniel Lang * dl@leo.org * +49 89 8540017 * http://www.leo.org/~dl/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 6:58:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (Postfix) with ESMTP id 5B3B115060; Sun, 21 Mar 1999 06:58:24 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.3/8.9.3) id IAA49101; Sun, 21 Mar 1999 08:56:34 -0600 (CST) (envelope-from dick) Date: Sun, 21 Mar 1999 08:56:34 -0600 From: "Richard Seaman, Jr." To: Matthew Dillon Cc: Brian Feldman , Alfred Perlstein , "John S. Dyson" , samit@usa.ltindia.com, commiters@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: rfork() Message-ID: <19990321085634.F32029@tar.com> References: <199903210743.XAA09505@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199903210743.XAA09505@apollo.backplane.com>; from Matthew Dillon on Sat, Mar 20, 1999 at 11:43:14PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 20, 1999 at 11:43:14PM -0800, Matthew Dillon wrote: > :For the suggest something, you realize that with Richard's VM_STACK code it > :should be relatively trivial to make this automatic (suggestion: add > :RFSTACK flag). > : > : Brian Feldman _ __ ___ ___ ___ > : green@unixhelp.org _ __ ___ | _ ) __| \ > : http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | > : FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ > > If the goal is to completely share the address space, which > RFMEM does, you can't split anything, not even the stack. It > sure would be useful if there were a standard clib call adequate > for calling rfork() and calling a function in the child w/ a new > stack. Possibilities for the clib call are noted in separate messages. The problem with adding an "RFSTACK" flag to the rfork call is that a lot of the time the caller of rfork wants to control the stack address. If you just add an "RFSTACK" flag, the system will have to pick the address. The linux clone syscall (different from the linux clone libc function) takes two additional parameters that rfork doesn't. One of those parameters is the stack TOS address, and the other is the exit signal the clone'd process should return (so "kthreads" can return different exist signals from child processes). As long as rfork doesn't take a TOS parameter as input, you will have to use an assembly language wrapper to rfork to graft the stack onto the child process. The primary reason I've seen, that the caller of rfork wants to control the TOS address, is so there is an efficient thread_self function. By marrying TLS to the stack, and using aligned/uniformly spaced stack addresses, thread_self can examine its stack, and derive the address of the TLS efficiently. Now, it would be very nice to find a better way to do the thread_self stuff. -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 9:22:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id BCED8151C2; Sun, 21 Mar 1999 09:22:16 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA13495; Sun, 21 Mar 1999 09:21:55 -0800 (PST) (envelope-from dillon) Date: Sun, 21 Mar 1999 09:21:55 -0800 (PST) From: Matthew Dillon Message-Id: <199903211721.JAA13495@apollo.backplane.com> To: Brian Feldman Cc: Alfred Perlstein , "John S. Dyson" , samit@usa.ltindia.com, commiters@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: rfork() References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hence the NEW flag RFSTACK. Why would this be a bad thing? This would keep :the old behavior and allow much nicer new behavior. I didn't suggest :changing the old behavior. This would just greatly simplify things so all of I think Richard Seaman has it right: the stack needs to be passed. Why don't we simply implement the linux clone()? It sounds to me that it would be trivial. :the assembly wouldn't be needed. Hmm... actually... if one were to mmap() a :stack and as soon as the rfork() returned movl newstack,%esp and whatnot, :wouldn't this be a pretty simple solution? No, because one of the processes may overrun the stack before the other one managed to return from rfork(). The child process cannot use the old stack at all. Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 9:44: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (Postfix) with SMTP id DF9E01511E for ; Sun, 21 Mar 1999 09:44:05 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id QAA03798; Sun, 21 Mar 1999 16:28:30 +0100 From: Luigi Rizzo Message-Id: <199903211528.QAA03798@labinfo.iet.unipi.it> Subject: 'de' driver not updating Opkts counters in netstat ? To: current@freebsd.org Date: Sun, 21 Mar 1999 16:28:30 +0100 (MET) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1144 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG as the subject says, i recently noticed that the 'de' driver on 3.1 machines seems not to update regularly the Opkt field as shown by netstat. I have seen this in two different ways; on a de-only machine, the count seems to be updated every few seconds (i.e. i see two-three times the same count doing a netstat despite i am connected via telnet so the fact that i see a response means i have at least one more pkt out). on another machine (dual homed, ed+de, running a multicast router) all the counters for the 'de' driver seem stuck and i can only get them to increase by running some savage ping e.g. ping -s 1000 myfriend Any ideas ? I have another 2.2.7 machine with the 'de' driver and mrouter online and counters seem to work fine there... luigi -----------------------------------+------------------------------------- Luigi RIZZO . EMAIL: luigi@iet.unipi.it . Dip. di Ing. dell'Informazione HTTP://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 9:48:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 2F6F314C24 for ; Sun, 21 Mar 1999 09:48:49 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA13708; Sun, 21 Mar 1999 09:48:27 -0800 (PST) (envelope-from dillon) Date: Sun, 21 Mar 1999 09:48:27 -0800 (PST) From: Matthew Dillon Message-Id: <199903211748.JAA13708@apollo.backplane.com> To: Luigi Rizzo Cc: current@FreeBSD.ORG Subject: Re: 'de' driver not updating Opkts counters in netstat ? References: <199903211528.QAA03798@labinfo.iet.unipi.it> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :as the subject says, i recently noticed that the 'de' driver on 3.1 :machines seems not to update regularly the Opkt field as shown :by netstat. I have seen this in two different ways; on a de-only :machine, the count seems to be updated every few seconds (i.e. i see :two-three times the same count doing a netstat despite i am connected :via telnet so the fact that i see a response means i have at least :one more pkt out). on another machine (dual homed, ed+de, running :a multicast router) all :the counters for the 'de' driver seem stuck and i can only get them to :increase by running some savage ping e.g. : : ping -s 1000 myfriend : :Any ideas ? : :I have another 2.2.7 machine with the 'de' driver and mrouter online :and counters seem to work fine there... : : luigi :-----------------------------------+------------------------------------- : Luigi RIZZO . I've noticed this also on the one machine I have left that uses the de driver. The Ipkt field is updated in realtime. The Opkt field is not. Very odd. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 10: 2:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from zone.syracuse.net (zone.syracuse.net [209.2.141.6]) by hub.freebsd.org (Postfix) with ESMTP id 7FA2B15175; Sun, 21 Mar 1999 10:02:56 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by zone.syracuse.net (8.9.2/8.9.2) with ESMTP id SAA02843; Sun, 21 Mar 1999 18:02:03 GMT (envelope-from green@unixhelp.org) Date: Sun, 21 Mar 1999 18:02:02 +0000 (GMT) From: Brian Feldman X-Sender: green@zone.syracuse.net To: Matthew Dillon Cc: Alfred Perlstein , "John S. Dyson" , samit@usa.ltindia.com, commiters@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: rfork() In-Reply-To: <199903211721.JAA13495@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 21 Mar 1999, Matthew Dillon wrote: > :Hence the NEW flag RFSTACK. Why would this be a bad thing? This would keep > :the old behavior and allow much nicer new behavior. I didn't suggest > :changing the old behavior. This would just greatly simplify things so all of > > I think Richard Seaman has it right: the stack needs to be passed. > > Why don't we simply implement the linux clone()? It sounds to me that > it would be trivial. Let's add another parameter to fork1/rfork(): pid_t rfork __P((int, ...)); for userland struct rfork_args { int flags; caddr_t extra; }; and in the kernel would be: fork1(p1, flags) register struct proc *p1; int flags; caddr_t extra; { foo } We, of course, have backward binary and code compatibility outside of the kernel with the ellipses, and inside the kernel we control it anyway so we can modify whatever needs to be changed. > > :the assembly wouldn't be needed. Hmm... actually... if one were to mmap() a > :stack and as soon as the rfork() returned movl newstack,%esp and whatnot, > :wouldn't this be a pretty simple solution? > > No, because one of the processes may overrun the stack before the other > one managed to return from rfork(). The child process cannot use the > old stack at all. Why would a simple movl be using the stack? > > Matthew Dillon > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 10: 6: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 691B614D1E; Sun, 21 Mar 1999 10:05:59 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA13805; Sun, 21 Mar 1999 10:05:38 -0800 (PST) (envelope-from dillon) Date: Sun, 21 Mar 1999 10:05:38 -0800 (PST) From: Matthew Dillon Message-Id: <199903211805.KAA13805@apollo.backplane.com> To: Brian Feldman Cc: Alfred Perlstein , "John S. Dyson" , samit@usa.ltindia.com, commiters@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: rfork() References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :the assembly wouldn't be needed. Hmm... actually... if one were to mmap() a :> :stack and as soon as the rfork() returned movl newstack,%esp and whatnot, :> :wouldn't this be a pretty simple solution? :> :> No, because one of the processes may overrun the stack before the other :> one managed to return from rfork(). The child process cannot use the :> old stack at all. : :Why would a simple movl be using the stack? If you are making a subroutine *call* to the rfork() routine, where do you think the return PC address is stored? On the stack. The rfork() routine is going to 'ret' *after* doing the rfork syscall. 'ret' pops the stack. While this in itself is not modifying the stack, you can still wind up with the situation where process A returns from the rfork and then does something else which overwrites the stack before process B has a chance to return from the rfork(). This is why, in my assembly example, I was forced to make the syscall manually rather then call the rfork() library function. :> : Brian Feldman _ __ ___ ___ ___ -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 10:58:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from zone.syracuse.net (zone.syracuse.net [209.2.141.6]) by hub.freebsd.org (Postfix) with ESMTP id B065014EC9; Sun, 21 Mar 1999 10:58:12 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by zone.syracuse.net (8.9.2/8.9.2) with ESMTP id SAA03148; Sun, 21 Mar 1999 18:57:01 GMT (envelope-from green@unixhelp.org) Date: Sun, 21 Mar 1999 18:57:01 +0000 (GMT) From: Brian Feldman X-Sender: green@zone.syracuse.net To: Matthew Dillon Cc: Alfred Perlstein , "John S. Dyson" , samit@usa.ltindia.com, commiters@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: rfork() In-Reply-To: <199903211805.KAA13805@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 21 Mar 1999, Matthew Dillon wrote: > :> :the assembly wouldn't be needed. Hmm... actually... if one were to mmap() a > :> :stack and as soon as the rfork() returned movl newstack,%esp and whatnot, > :> :wouldn't this be a pretty simple solution? > :> > :> No, because one of the processes may overrun the stack before the other > :> one managed to return from rfork(). The child process cannot use the > :> old stack at all. > : > :Why would a simple movl be using the stack? > > If you are making a subroutine *call* to the rfork() routine, where > do you think the return PC address is stored? On the stack. The > rfork() routine is going to 'ret' *after* doing the rfork syscall. > 'ret' pops the stack. While this in itself is not modifying the stack, > you can still wind up with the situation where process A returns from > the rfork and then does something else which overwrites the stack before > process B has a chance to return from the rfork(). Why does it matter if something munges the stack in proc A though before proc B returns since proc B is going to immediately switch over to a new stack? > > This is why, in my assembly example, I was forced to make the syscall > manually rather then call the rfork() library function. > > :> > : Brian Feldman _ __ ___ ___ ___ > > -Matt > > Matthew Dillon > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 11:58:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id B76FB14E93; Sun, 21 Mar 1999 11:58:30 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA14438; Sun, 21 Mar 1999 11:58:10 -0800 (PST) (envelope-from dillon) Date: Sun, 21 Mar 1999 11:58:10 -0800 (PST) From: Matthew Dillon Message-Id: <199903211958.LAA14438@apollo.backplane.com> To: Brian Feldman Cc: Alfred Perlstein , "John S. Dyson" , samit@usa.ltindia.com, commiters@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: rfork() References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> If you are making a subroutine *call* to the rfork() routine, where :> do you think the return PC address is stored? On the stack. The :> rfork() routine is going to 'ret' *after* doing the rfork syscall. :> 'ret' pops the stack. While this in itself is not modifying the stack, :> you can still wind up with the situation where process A returns from :> the rfork and then does something else which overwrites the stack before :> process B has a chance to return from the rfork(). : :Why does it matter if something munges the stack in proc A though before :proc B returns since proc B is going to immediately switch over to a new :stack? The return address for the procedure call is on the stack. If something munges the stack after the physical rfork occurs but before both processes can return from the rfork() clib function, then one of the processes attempting to return will pop a bogus return address and seg fault. -Matt Matthew Dillon : Brian Feldman _ __ ___ ___ ___ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 12: 8:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from zone.syracuse.net (zone.syracuse.net [209.2.141.6]) by hub.freebsd.org (Postfix) with ESMTP id F104114D1E; Sun, 21 Mar 1999 12:08:25 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by zone.syracuse.net (8.9.2/8.9.2) with ESMTP id UAA03732; Sun, 21 Mar 1999 20:07:16 GMT (envelope-from green@unixhelp.org) Date: Sun, 21 Mar 1999 20:07:16 +0000 (GMT) From: Brian Feldman X-Sender: green@zone.syracuse.net To: Matthew Dillon Cc: Alfred Perlstein , "John S. Dyson" , samit@usa.ltindia.com, commiters@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: rfork() In-Reply-To: <199903211958.LAA14438@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 21 Mar 1999, Matthew Dillon wrote: > :> If you are making a subroutine *call* to the rfork() routine, where > :> do you think the return PC address is stored? On the stack. The > :> rfork() routine is going to 'ret' *after* doing the rfork syscall. > :> 'ret' pops the stack. While this in itself is not modifying the stack, > :> you can still wind up with the situation where process A returns from > :> the rfork and then does something else which overwrites the stack before > :> process B has a chance to return from the rfork(). > : > :Why does it matter if something munges the stack in proc A though before > :proc B returns since proc B is going to immediately switch over to a new > :stack? > > The return address for the procedure call is on the stack. If something > munges the stack after the physical rfork occurs but before both processes > can return from the rfork() clib function, then one of the processes > attempting to return will pop a bogus return address and seg fault. What's to stop the RFSTACK from copying the stack itself into the new stack that is located elsewhere in RAM and attached to the vm space? Actually, rfork() would just set it in the trap frame anyway, so there would be no extra user code to do this. > > -Matt > Matthew Dillon > > > : Brian Feldman _ __ ___ ___ ___ > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 12:19:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id EE7811514E for ; Sun, 21 Mar 1999 12:19:51 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony [10.0.0.6]) by rover.village.org (8.9.3/8.6.6) with ESMTP id UAA97152; Sun, 21 Mar 1999 20:19:31 GMT Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA70907; Sun, 21 Mar 1999 13:19:42 -0700 (MST) Message-Id: <199903212019.NAA70907@harmony.village.org> To: Sheldon Hearn Subject: Re: Confused by wcd->acd in UPDATING Cc: current@FreeBSD.ORG In-reply-to: Your message of "Thu, 18 Mar 1999 17:35:35 +0200." <84061.921771335@axl.noc.iafrica.com> References: <84061.921771335@axl.noc.iafrica.com> Date: Sun, 21 Mar 1999 13:19:42 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <84061.921771335@axl.noc.iafrica.com> Sheldon Hearn writes: : 19990316: : The name of the old wd.c and atapi.c based CDROM driver has : been changed back to wcd. So update your config file to use : "device wcd" instead of "device acd". : : Am I right in thinking that this only applies to people who are _not_ : using Soren's new IDE/ATA/ATAPI driver? Yes. You are correct. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 12:40:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles212.castles.com [208.214.165.212]) by hub.freebsd.org (Postfix) with ESMTP id BD83E14BD4 for ; Sun, 21 Mar 1999 12:40:16 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA00655; Sun, 21 Mar 1999 12:34:17 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903212034.MAA00655@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "RT" Cc: current@FreeBSD.ORG Subject: Re: NetBoot & 3Com card. In-reply-to: Your message of "Sat, 20 Mar 1999 22:50:45 EST." <000101be734e$00eb0c40$63e9a4cf@a35.my.intranet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 21 Mar 1999 12:34:17 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have a couple of 905B 3com cards. I'm interested in running diskless > (especially since a harddisk in the one machine just died). > > After reading the handbook, I found the diskless information to be extreamly > outdated. Does netboot now support the 905 line of 3com cards? (Any test > drivers out there for it?) No. You might have some success with a commercial bootprom (eg. from www.incom.de) and a tftp'able boot image. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 13:57:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles212.castles.com [208.214.165.212]) by hub.freebsd.org (Postfix) with ESMTP id F2D7714CD4 for ; Sun, 21 Mar 1999 13:57:26 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id NAA01089; Sun, 21 Mar 1999 13:51:22 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903212151.NAA01089@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel C. Sobral" Cc: current@FreeBSD.ORG Subject: Re: How to add a new bootdevice to the new boot code ??? In-reply-to: Your message of "Sun, 21 Mar 1999 05:22:13 +0900." <36F40375.624C03D0@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 21 Mar 1999 13:51:21 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > However Justin's random number comment speaks back to a technique I was > > working on earlier, where such a number would be secreted in the > > disklabel of the disk to be booted. This number would have to be > > generated in a fairly unique fashion (I planned to use the TOD to try > > to keep it from wrapping), and it'd then be passed in in the > > environment or as an argument to the kernel. > > How would that work with netboot or booting from foreign fs, such as > FAT? Netbooting is easy, as we can pass an unmabiguous identifier for the remote filesystem to the kernel (the loader and the kernel share the same context on this). Booting from a FAT filesystem isn't a reality until DEVFS arrives, and at that point we have a pile more options available to us again. I wouldn't be too concerned about that just yet. > If we restrict ourselves to disklabel-carrying fs, an alternative > would be writing the date&time plus a semi-random number (such as > time down to ms) on the disklabel of the disk selected, and passing > this number to the kernel. > > [reads what you said again] > > Unless, of course, that's precisely what you are talking about... Correct. I was looking for a field in the disklabel that I could spam with a suitable number based on the time from the RTC, and I'd then pass that number and the disklabel checksum into the kernel. The only way that this would break would be in the face of tight circumstance and the clock going backwards. > > However, there's another technique which would work quite well, and one > > I'm actually moderately enamoured of (modulo it's ability to confuse > > the heck out of people). > > > > Use the "last mounted on" field to find and mount filesystems. > > Again, same objections... :-) Same solutions. Plus we'd be likely to place some metadata somewhere on a FAT filesystem, so it'd be trivial to put such a field there. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 14:30:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 633BB15058 for ; Sun, 21 Mar 1999 14:30:14 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id JAA27264; Mon, 22 Mar 1999 09:29:48 +1100 Date: Mon, 22 Mar 1999 09:29:48 +1100 From: Bruce Evans Message-Id: <199903212229.JAA27264@godzilla.zeta.org.au> To: dcs@newsguy.com, mike@smith.net.au Subject: Re: How to add a new bootdevice to the new boot code ??? Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Correct. I was looking for a field in the disklabel that I could spam >with a suitable number based on the time from the RTC, and I'd then There isn't one. Especially when there is no disklabel or a read-only disklabel. >> Again, same objections... :-) > >Same solutions. Plus we'd be likely to place some metadata somewhere >on a FAT filesystem, so it'd be trivial to put such a field there. Similar objections. Disks should be write protected to inhibit spam :-). I pass "foo" from 1:foo(2s1a)kernel in my version of the old boot blocks. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 15:17: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (Postfix) with ESMTP id D5C5B14BE2 for ; Sun, 21 Mar 1999 15:16:57 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.9.2/8.9.1) with ESMTP id QAA93579; Sun, 21 Mar 1999 16:15:35 -0700 (MST) (envelope-from gibbs@plutotech.com) Message-Id: <199903212315.QAA93579@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: S ren Schmidt Cc: gibbs@plutotech.com (Justin T. Gibbs), current@FreeBSD.ORG Subject: Re: How to add a new bootdevice to the new boot code ??? In-reply-to: Your message of "Sun, 21 Mar 1999 10:58:28 +0100." <199903210958.KAA37231@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Sun, 21 Mar 1999 16:06:34 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >> - Peripheral driver to device routing >> > >> >Such as ? >> = >> Such as the ability to have more than one driver share the >> same device, command generation counts and priority queuing >> to allow correct 'replay' of overlapped commands when an >> error occurs, etc. See: >> = >> http://www.freebsd.org/~gibbs/cam.html > >That will probably need changes to work with ATA4's tagged queing at >least... I just read the ATA5 draft (couldn't find the last ATA4 draft at the wdc website). I don't see any issues here other than the fact that the effec= t of overlapped commands on data integrity seems to be unspecified. Are th= ey always handled in FIFO order? Can reads be seek optimized? What happens= in the case of a queued write after a queued read to the same location? = My hope is that, since the spec does not allow you to specify the sorting restrictions on a per request basis as you can in SCSI, FIFO ordering is implied. They even mention that the feature is intended to overlap comman= d processing latency without mentioning the possibility of other optimizations, so perhaps this really is the case. Too bad they didn't ju= st define the two bits necessary (and left as spares in the tag specificatio= n register) to allow the same queuing feature set as SCSI. >> Command queuing was a major factor in why I wrote the CAM code. Solvi= ng >> these issues is not trivial. > >Agreed, but have you looked at how ATA4 handles queing ?? Yes. >> >> - an aplication pass-thru interface >> > >> >Hmm, what for ?? >> = >> cdrecord, a userland disk format utility, camcontrol functionality, >> etc. etc. > >He he, ATAPI dont need cdrecord as all ATAPI burners use the same >command set (MMC), where your average SCSI burner has its own >propietary command set (well, the ATA/ATAPI guys did get one thing >right :) ), Almost all newer SCSI cd burners use MMC now and cdrecord supports MMC devices. Why write another utility if there is already one that speaks t= he necessary language that our users are familiar with? >OK, I'm done discussing this (se my other mail), I'd rater spend >my (very limitted) time productively. Fair enough. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 15:36:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles212.castles.com [208.214.165.212]) by hub.freebsd.org (Postfix) with ESMTP id 6B2E214D48 for ; Sun, 21 Mar 1999 15:36:24 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id PAA01548; Sun, 21 Mar 1999 15:29:53 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903212329.PAA01548@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bruce Evans Cc: dcs@newsguy.com, mike@smith.net.au, current@FreeBSD.ORG Subject: Re: How to add a new bootdevice to the new boot code ??? In-reply-to: Your message of "Mon, 22 Mar 1999 09:29:48 +1100." <199903212229.JAA27264@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 21 Mar 1999 15:29:52 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Correct. I was looking for a field in the disklabel that I could spam > >with a suitable number based on the time from the RTC, and I'd then > > There isn't one. Especially when there is no disklabel or a read-only > disklabel. > > >> Again, same objections... :-) > > > >Same solutions. Plus we'd be likely to place some metadata somewhere > >on a FAT filesystem, so it'd be trivial to put such a field there. > > Similar objections. Disks should be write protected to inhibit spam :-). I'm happy to entertain any alternate solutions. > I pass "foo" from 1:foo(2s1a)kernel in my version of the old boot blocks. And you determine "foo" how? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 15:47: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id C7E5D14F31 for ; Sun, 21 Mar 1999 15:46:56 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id KAA04161; Mon, 22 Mar 1999 10:46:35 +1100 Date: Mon, 22 Mar 1999 10:46:35 +1100 From: Bruce Evans Message-Id: <199903212346.KAA04161@godzilla.zeta.org.au> To: bde@zeta.org.au, mike@smith.net.au Subject: Re: How to add a new bootdevice to the new boot code ??? Cc: current@FreeBSD.ORG, dcs@newsguy.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I pass "foo" from 1:foo(2s1a)kernel in my version of the old boot blocks. > >And you determine "foo" how? I type it into the config file or the command line. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 15:54: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles212.castles.com [208.214.165.212]) by hub.freebsd.org (Postfix) with ESMTP id D11B314D7F for ; Sun, 21 Mar 1999 15:53:55 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id PAA01670; Sun, 21 Mar 1999 15:47:37 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903212347.PAA01670@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bruce Evans Cc: mike@smith.net.au, current@FreeBSD.ORG, dcs@newsguy.com Subject: Re: How to add a new bootdevice to the new boot code ??? In-reply-to: Your message of "Mon, 22 Mar 1999 10:46:35 +1100." <199903212346.KAA04161@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 21 Mar 1999 15:47:36 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> I pass "foo" from 1:foo(2s1a)kernel in my version of the old boot blocks. > > > >And you determine "foo" how? > > I type it into the config file or the command line. And you submit that this is an acceptable solution? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 16:17:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from regret.globalserve.net (regret.globalserve.net [209.90.144.72]) by hub.freebsd.org (Postfix) with ESMTP id B28E814D3D for ; Sun, 21 Mar 1999 16:17:52 -0800 (PST) (envelope-from dm@regret.globalserve.net) Received: (from dm@localhost) by regret.globalserve.net (8.9.3/8.9.1) id UAA50657 for current@freebsd.org; Sun, 21 Mar 1999 20:27:37 GMT (envelope-from dm) Message-ID: <19990321202736.B50594@globalserve.net> Date: Sun, 21 Mar 1999 20:27:36 +0000 From: Dan Moschuk To: current@freebsd.org Subject: aic Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Any hope of the aic driver gracing -current anytime soon? I'm really itching to port my burning software over. Cheers, -- Dan Moschuk (TFreak!dm@globalserve.net) Senior Systems/Network Administrator Globalserve Communications Inc., a Primus Canada Company "If at first you don't succeed, redefine success" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 16:54:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from zone.syracuse.net (zone.syracuse.net [209.2.141.6]) by hub.freebsd.org (Postfix) with ESMTP id 0FEB214F88 for ; Sun, 21 Mar 1999 16:54:28 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by zone.syracuse.net (8.9.2/8.9.2) with ESMTP id AAA05734 for ; Mon, 22 Mar 1999 00:54:12 GMT (envelope-from green@unixhelp.org) Date: Mon, 22 Mar 1999 00:54:12 +0000 (GMT) From: Brian Feldman X-Sender: green@zone.syracuse.net To: current@freebsd.org Subject: CPUT_WT_ALLOC_DISABLE Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone want a CPU_WT_ALLOC_DISABLE and CPU_WT_ALLOC_ENABLE as separate options? I see a couple changes that should be made to the kernel now: CPU: AMD-K6(tm) 3D processor (300.69-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping=12 Features=0x8021bf There should be another line, formatted the same, that ALWAYS reports CPU_WT_ALLOC info. This will help in debugging problems with certain hardware, because on K6-2's I get unreliability with write allocation on. For instance, I updated my BIOS lately and observed a crash. On boot -v, I noted that the BIOS was kind enough to turn on write allocation, but on a CPU that it doesn't seem to work well on. I propose an option to turn OFF write allocation instead of just one to turn it on. I also propose the change in CPU info printouts to (more correct spacing and extra line): CPU: AMD-K6(tm) 3D processor (300.69-MHz 586-like CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features = 0x8021bf Write Allocation: Disabled 15-16M Caching Enable: No The changes would be better spacing, a write allocation line (for whatever CPUs are supported, notably the K5, K6, K6-[23]), and changing "class" to the more sensible "like" (i.e. a K6 really is 686-class, but being socket 7 is 586-like). Comments? Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 17:15:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id C3F46151B5 for ; Sun, 21 Mar 1999 17:15:10 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id LAA14236; Mon, 22 Mar 1999 11:44:50 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id LAA07433; Mon, 22 Mar 1999 11:44:45 +1030 (CST) Message-ID: <19990322114444.B429@lemis.com> Date: Mon, 22 Mar 1999 11:44:44 +1030 From: Greg Lehey To: Brian Feldman , current@FreeBSD.ORG Subject: Reporting AMD processors (was: CPUT_WT_ALLOC_DISABLE) References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Brian Feldman on Mon, Mar 22, 1999 at 12:54:12AM +0000 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 22 March 1999 at 0:54:12 +0000, Brian Feldman wrote: > Does anyone want a CPU_WT_ALLOC_DISABLE and CPU_WT_ALLOC_ENABLE as separate > options? I see a couple changes that should be made to the kernel now: > > CPU: AMD-K6(tm) 3D processor (300.69-MHz 586-class CPU) > Origin = "AuthenticAMD" Id = 0x58c Stepping=12 > Features=0x8021bf > > There should be another line, formatted the same, that ALWAYS reports > CPU_WT_ALLOC info. This will help in debugging problems with certain hardware, > because on K6-2's I get unreliability with write allocation on. For instance, > I updated my BIOS lately and observed a crash. On boot -v, I noted that > the BIOS was kind enough to turn on write allocation, but on a CPU that it > doesn't seem to work well on. What's wrong with leaving the message in the -v output? After all, it's debugging info. > I propose an option to turn OFF write allocation instead of just one to turn > it on. I also propose the change in CPU info printouts to (more correct spacing > and extra line): > > CPU: AMD-K6(tm) 3D processor (300.69-MHz 586-like CPU) > Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 > Features = 0x8021bf > Write Allocation: Disabled 15-16M Caching Enable: No > > The changes would be better spacing, a write allocation line (for whatever > CPUs are supported, notably the K5, K6, K6-[23]), and changing "class" to > the more sensible "like" (i.e. a K6 really is 686-class, but being socket 7 > is 586-like). You'd better pass the spacing issue past bde. Certainly it mathes the other messages. On the whole, I suppose this is reasonable info, but I wonder if we're not tending towards too much information anyway. I needed to increase the MSGBUF_SIZE on some machines just to get the total content of a non-verbose boot. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 17:47: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 7A7BD14BCD for ; Sun, 21 Mar 1999 17:46:39 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id MAA23082; Mon, 22 Mar 1999 12:46:17 +1100 Date: Mon, 22 Mar 1999 12:46:17 +1100 From: Bruce Evans Message-Id: <199903220146.MAA23082@godzilla.zeta.org.au> To: bde@zeta.org.au, mike@smith.net.au Subject: Re: How to add a new bootdevice to the new boot code ??? Cc: current@FreeBSD.ORG, dcs@newsguy.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >> I pass "foo" from 1:foo(2s1a)kernel in my version of the old boot blocks. >> > >> >And you determine "foo" how? >> >> I type it into the config file or the command line. > >And you submit that this is an acceptable solution? Of course. The FreeBSD device name won't change (modulo implementation bugs), and even when it does, changing the config file is easier than changing /etc/fstab. Note that there is, or should be, no problem here with the BIOS drive number. My example has "1:" in it to switch from the default BIOS drive of hard disk 0. The boot blocks should read the config file on the new drive[,slice,partition] to determine the FreeBSD device name (drive and unit number, but not slice or partition). Leave out "1:" from my example. Then booting will not be affected by changes in the BIOS drive number. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 17:55:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from zone.syracuse.net (zone.syracuse.net [209.2.141.6]) by hub.freebsd.org (Postfix) with ESMTP id 9F7AC15000 for ; Sun, 21 Mar 1999 17:55:20 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by zone.syracuse.net (8.9.2/8.9.2) with ESMTP id BAA06133; Mon, 22 Mar 1999 01:51:09 GMT (envelope-from green@unixhelp.org) Date: Mon, 22 Mar 1999 01:51:09 +0000 (GMT) From: Brian Feldman X-Sender: green@zone.syracuse.net To: Greg Lehey Cc: current@FreeBSD.ORG Subject: Re: Reporting AMD processors (was: CPUT_WT_ALLOC_DISABLE) In-Reply-To: <19990322114444.B429@lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Mar 1999, Greg Lehey wrote: > On Monday, 22 March 1999 at 0:54:12 +0000, Brian Feldman wrote: > > Does anyone want a CPU_WT_ALLOC_DISABLE and CPU_WT_ALLOC_ENABLE as separate > > options? I see a couple changes that should be made to the kernel now: > > > > CPU: AMD-K6(tm) 3D processor (300.69-MHz 586-class CPU) > > Origin = "AuthenticAMD" Id = 0x58c Stepping=12 > > Features=0x8021bf > > > > There should be another line, formatted the same, that ALWAYS reports > > CPU_WT_ALLOC info. This will help in debugging problems with certain hardware, > > because on K6-2's I get unreliability with write allocation on. For instance, > > I updated my BIOS lately and observed a crash. On boot -v, I noted that > > the BIOS was kind enough to turn on write allocation, but on a CPU that it > > doesn't seem to work well on. > > What's wrong with leaving the message in the -v output? After all, > it's debugging info. What's wrong is that this is info that should really be printed with the rest of the info. When people send PRs with the dmesg it will show what could possibly be wrong, and with this kind of change would show MORE of what could be wrong. > > > I propose an option to turn OFF write allocation instead of just one to turn > > it on. I also propose the change in CPU info printouts to (more correct spacing > > and extra line): > > > > CPU: AMD-K6(tm) 3D processor (300.69-MHz 586-like CPU) > > Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 > > Features = 0x8021bf > > Write Allocation: Disabled 15-16M Caching Enable: No > > > > The changes would be better spacing, a write allocation line (for whatever > > CPUs are supported, notably the K5, K6, K6-[23]), and changing "class" to > > the more sensible "like" (i.e. a K6 really is 686-class, but being socket 7 > > is 586-like). > > You'd better pass the spacing issue past bde. Certainly it mathes the > other messages. On the whole, I suppose this is reasonable info, but > I wonder if we're not tending towards too much information anyway. I > needed to increase the MSGBUF_SIZE on some machines just to get the > total content of a non-verbose boot. Yeah, I remember System 7's boot having about 1-3 lines, I don't recall exactly. But, having enough output is GOOD! Maybe MSGBUF_SIZE should be increased by default nowadays. > > Greg > -- > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 18: 9: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 3E8CC1532D for ; Sun, 21 Mar 1999 18:07:15 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA39220 for ; Sun, 21 Mar 1999 18:06:41 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: current@freebsd.org Subject: /etc/rc.conf, take 46! Date: Sun, 21 Mar 1999 18:06:41 -0800 Message-ID: <39218.922068401@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, so it seems everyone's found something to like and dislike about the new scheme. In that regard, it seems pretty much equivalent to the previous layout when that was first introduced. :) However, incremental refinement for this stuff has always been the order of the day, so in that spirit, here's my proposal to deal with the most recent set of gripes: That rc.conf contains "code" in addition to data. The following diffs make rc.conf a variable-only file, at the cost of distributing the hook-calling mechanism into all the former clients of rc.conf. That really doesn't bother me if it doesn't bother you, and further optimization of it can always be another future incremental refinement. Another incremental, albeit contraversial, refinement would be to change /etc/defaults/rc.conf and friends into something truely machine-parsable, changing statements like this: if [ -f /some/conf/file ]; then . /some/conf/file fi Into something like this: if [ -f /some/conf/file ]; then eval `/sbin/rcvtosh /some/conf/file` fi But these changes do not attempt to do that, they simply attempt to make the existing rc.conf format somewhat easier to parse. Comments requested. Index: netstart =================================================================== RCS file: /home/ncvs/src/etc/netstart,v retrieving revision 1.53 diff -u -u -r1.53 netstart --- netstart 1999/02/10 18:08:16 1.53 +++ netstart 1999/03/22 01:54:16 @@ -12,8 +12,11 @@ # If there is a global system configuration file, suck it in. if [ -f /etc/defaults/rc.conf ]; then . /etc/defaults/rc.conf -elif [ -f /etc/rc.conf ]; then - . /etc/rc.conf + for i in ${rc_conf_files}; do + if [ -f $i ]; then + . $i + fi + done fi if [ -f /etc/rc.network ]; then Index: pccard_ether =================================================================== RCS file: /home/ncvs/src/etc/pccard_ether,v retrieving revision 1.11 diff -u -u -r1.11 pccard_ether --- pccard_ether 1999/02/22 02:55:18 1.11 +++ pccard_ether 1999/03/22 01:55:27 @@ -7,11 +7,14 @@ # example: pccard_ether ep0 -link0 # -# Suck in the configuration variables +# If there is a global system configuration file, suck it in. if [ -f /etc/defaults/rc.conf ]; then . /etc/defaults/rc.conf -elif [ -f /etc/rc.conf ]; then - . /etc/rc.conf + for i in ${rc_conf_files}; do + if [ -f $i ]; then + . $i + fi + done fi if [ "x$pccard_ifconfig" != "xNO" ] ; then Index: rc =================================================================== RCS file: /home/ncvs/src/etc/rc,v retrieving revision 1.183 diff -u -u -r1.183 rc --- rc 1999/03/17 04:00:04 1.183 +++ rc 1999/03/22 01:56:24 @@ -33,11 +33,13 @@ fi # If there is a global system configuration file, suck it in. -# if [ -f /etc/defaults/rc.conf ]; then . /etc/defaults/rc.conf -elif [ -f /etc/rc.conf ]; then - . /etc/rc.conf + for i in ${rc_conf_files}; do + if [ -f $i ]; then + . $i + fi + done fi # Configure ccd devices. Index: rc.devfs =================================================================== RCS file: /home/ncvs/src/etc/rc.devfs,v retrieving revision 1.4 diff -u -u -r1.4 rc.devfs --- rc.devfs 1999/02/10 18:08:16 1.4 +++ rc.devfs 1999/03/22 01:56:39 @@ -1,11 +1,15 @@ # # $Id: rc.devfs,v 1.4 1999/02/10 18:08:16 jkh Exp $ # + # If there is a global system configuration file, suck it in. if [ -f /etc/defaults/rc.conf ]; then . /etc/defaults/rc.conf -elif [ -f /etc/rc.conf ]; then - . /etc/rc.conf + for i in ${rc_conf_files}; do + if [ -f $i ]; then + . $i + fi + done fi # Setup DEVFS, ie permisisons, links etc. Index: rc.diskless2 =================================================================== RCS file: /home/ncvs/src/etc/rc.diskless2,v retrieving revision 1.2 diff -u -u -r1.2 rc.diskless2 --- rc.diskless2 1999/02/10 18:08:16 1.2 +++ rc.diskless2 1999/03/22 01:57:04 @@ -2,11 +2,13 @@ # # If there is a global system configuration file, suck it in. -# if [ -f /etc/defaults/rc.conf ]; then . /etc/defaults/rc.conf -elif [ -f /etc/rc.conf ]; then - . /etc/rc.conf + for i in ${rc_conf_files}; do + if [ -f $i ]; then + . $i + fi + done fi mount_mfs -s ${var_run_sectors:=2048} -T qp120at dummy /var/run Index: rc.firewall =================================================================== RCS file: /home/ncvs/src/etc/rc.firewall,v retrieving revision 1.20 diff -u -u -r1.20 rc.firewall --- rc.firewall 1999/02/10 18:08:16 1.20 +++ rc.firewall 1999/03/22 01:57:16 @@ -2,11 +2,14 @@ # Setup system for firewall service. # $Id: rc.firewall,v 1.20 1999/02/10 18:08:16 jkh Exp $ -# Suck in the configuration variables. +# If there is a global system configuration file, suck it in. if [ -f /etc/defaults/rc.conf ]; then . /etc/defaults/rc.conf -elif [ -f /etc/rc.conf ]; then - . /etc/rc.conf + for i in ${rc_conf_files}; do + if [ -f $i ]; then + . $i + fi + done fi ############ Index: defaults/rc.conf =================================================================== RCS file: /home/ncvs/src/etc/defaults/rc.conf,v retrieving revision 1.4 diff -u -u -r1.4 rc.conf --- rc.conf 1999/03/17 04:00:04 1.4 +++ rc.conf 1999/03/22 01:58:02 @@ -202,16 +202,3 @@ kern_securelevel="-1" # range: -1..3 ; `-1' is the most insecure update_motd="YES" # update version info in /etc/motd (or NO) vinum_drives="" # put in names of disks containing vinum drives - -############################################################## -### Allow local configuration override at the very end here ## -############################################################## -# -# - -for i in ${rc_conf_files}; do - if [ -f $i ]; then - . $i - fi -done - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 18:10: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles212.castles.com [208.214.165.212]) by hub.freebsd.org (Postfix) with ESMTP id 395861524D for ; Sun, 21 Mar 1999 18:10:06 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id SAA02358; Sun, 21 Mar 1999 18:03:52 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903220203.SAA02358@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bruce Evans Cc: mike@smith.net.au, current@FreeBSD.ORG, dcs@newsguy.com Subject: Re: How to add a new bootdevice to the new boot code ??? In-reply-to: Your message of "Mon, 22 Mar 1999 12:46:17 +1100." <199903220146.MAA23082@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 21 Mar 1999 18:03:51 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> >> I pass "foo" from 1:foo(2s1a)kernel in my version of the old boot blocks. > >> > > >> >And you determine "foo" how? > >> > >> I type it into the config file or the command line. > > > >And you submit that this is an acceptable solution? > > Of course. The FreeBSD device name won't change (modulo implementation > bugs), and even when it does, changing the config file is easier than > changing /etc/fstab. Since this entire thread came about due to a device name change, and given that the last major upheaval in this domain was over a similar change, I'd say that was wishful thinking in the least. > Note that there is, or should be, no problem here with the BIOS drive > number. My example has "1:" in it to switch from the default BIOS > drive of hard disk 0. The boot blocks should read the config file on > the new drive[,slice,partition] to determine the FreeBSD device name > (drive and unit number, but not slice or partition). Leave out "1:" > from my example. Then booting will not be affected by changes in the > BIOS drive number. This presupposes that the configuration file is always right, ie. that it correctly describes the location of the disk. This isn't really a valid premise, and in any case does no better than to duplicate the 'last mounted on' field in the filesystem itself. I'm not sold, sorry. This isn't sufficiently automatable, nor does it remove the room for massive user error that I for one fear greatly. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 18:25:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 03BE114BE9 for ; Sun, 21 Mar 1999 18:25:40 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id NAA29947; Mon, 22 Mar 1999 13:25:20 +1100 Date: Mon, 22 Mar 1999 13:25:20 +1100 From: Bruce Evans Message-Id: <199903220225.NAA29947@godzilla.zeta.org.au> To: bde@zeta.org.au, mike@smith.net.au Subject: Re: How to add a new bootdevice to the new boot code ??? Cc: current@FreeBSD.ORG, dcs@newsguy.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >And you submit that this is an acceptable solution? >> >> Of course. The FreeBSD device name won't change (modulo implementation >> bugs), and even when it does, changing the config file is easier than >> changing /etc/fstab. > >Since this entire thread came about due to a device name change, and >given that the last major upheaval in this domain was over a similar >change, I'd say that was wishful thinking in the least. Driver name changes are implementation bugs. So are driver numbering changes. The latter are more serious, since you can't work around them by linking files in /dev if the new or old numbering is dynamic. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 19: 1: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from mx4.dynasty.net (mail.dynasty.net [208.200.172.236]) by hub.freebsd.org (Postfix) with ESMTP id A57F614BE9 for ; Sun, 21 Mar 1999 19:00:51 -0800 (PST) (envelope-from cpinckard@dynasty.net) Received: from dynasty.net ([12.14.196.145]) by mx4.dynasty.net (Netscape Messaging Server 3.52) with ESMTP id 257 for ; Sun, 21 Mar 1999 21:04:53 -0600 Message-ID: <36F5AF2D.E3E667FB@dynasty.net> Date: Sun, 21 Mar 1999 20:47:09 -0600 From: Chas X-Mailer: Mozilla 4.04 [en] (Win95; U) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: !!!! Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 19:12:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from quackerjack.cc.vt.edu (quackerjack.cc.vt.edu [198.82.160.250]) by hub.freebsd.org (Postfix) with ESMTP id 61FEC14C24 for ; Sun, 21 Mar 1999 19:12:23 -0800 (PST) (envelope-from jobaldwi@vt.edu) Received: from sable.cc.vt.edu (sable.cc.vt.edu [128.173.16.30]) by quackerjack.cc.vt.edu (8.8.8/8.8.8) with ESMTP id WAA18587; Sun, 21 Mar 1999 22:12:03 -0500 (EST) Received: from john.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.63]) by sable.cc.vt.edu (8.8.8/8.8.8) with ESMTP id WAA23015; Sun, 21 Mar 1999 22:12:02 -0500 (EST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <39218.922068401@zippy.cdrom.com> Date: Sun, 21 Mar 1999 22:12:03 -0500 (EST) From: John Baldwin To: "Jordan K. Hubbard" Subject: RE: /etc/rc.conf, take 46! Cc: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Mar-99 Jordan K. Hubbard wrote: > OK, so it seems everyone's found something to like and dislike about > the new scheme. In that regard, it seems pretty much equivalent to > the previous layout when that was first introduced. :) If it makes you feel any better, I kind of like the new system with the default setup in /etc/defaults and the customizations/overrides in /etc. Makes perfect sense to me and works well. I don't really care where the functionality of sucking in the configuration files is, but the obvious point seems to be that having the code duplicated in about six different places will make maintaining it a pain. Maybe a compromise would be to include a function in /etc/defaults/rc.conf that is called everywhere else so that at least you only have to change one function. IOW, /etc/defaults/rc.conf have: suck_in_files() { for i in ${rc_conf_files}; do if [ -f $i ]; then . $i fi done } And just have all the various files you had to patch below do the following: if [ -f /etc/defaults/rc.conf ]; then . /etc/defaults/rc.conf suck_in_files fi I guess it's still including "code" in /etc/rc.conf, but it doesn't execute it. So, if Joe Schmoe copies /etc/defaults/rc.conf to /etc/rc.conf it will still work. Actually, after some testing, this can be broken. If suck_in_files() is redefined in the included files there are weird side effects, ranging from seg faults to working properly to the function changing mid-stream. Then you could I suppose define _another_ file in /etc or /etc/defaults that defined suck_in_files() and other similar functions so that the if-statement above would become: if [ -f /etc/defaults/rc.conf ]; then . /etc/defaults/rc.conf . /etc/defaults/rc.functions suck_in_files fi Bleah.. Why can't we assume users can read and hold them accountable to that? At the very beginning of /etc/defaults/rc.conf it tells them that they shouldn't copy it to /etc/rc.conf. If they are too stubborn to do as they are told, they should either a) be using /stand/sysinstall, or b) be willing to accept the consequences. --- John Baldwin -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 19:35:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id 2536114F68; Sun, 21 Mar 1999 19:35:31 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.2/8.9.2/Netplex) with ESMTP id LAA52679; Mon, 22 Mar 1999 11:34:26 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199903220334.LAA52679@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon Cc: Brian Feldman , Alfred Perlstein , "John S. Dyson" , samit@usa.ltindia.com, commiters@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: rfork() In-reply-to: Your message of "Sun, 21 Mar 1999 09:21:55 PST." <199903211721.JAA13495@apollo.backplane.com> Date: Mon, 22 Mar 1999 11:34:25 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > :Hence the NEW flag RFSTACK. Why would this be a bad thing? This would keep > :the old behavior and allow much nicer new behavior. I didn't suggest > :changing the old behavior. This would just greatly simplify things so all of > > I think Richard Seaman has it right: the stack needs to be passed. > > Why don't we simply implement the linux clone()? It sounds to me that > it would be trivial. Doing clone() in libc that calls rfork(2) and doing all the stack setup should be pretty easy.. (Richard has done it already, yes?) On the other hand, the linux emulator needs it so there's a counter-argument for making it a proper syscall outright. Leaving the rfork(2) stuff unmolested and at least resembling it's plan9 origins probably has some merit - adding extra arguments would mess that up. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 20:38:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from detlev.UUCP (52-sweet.camalott.com [208.239.153.52]) by hub.freebsd.org (Postfix) with ESMTP id 5FD9C15171 for ; Sun, 21 Mar 1999 20:38:39 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.3/8.9.1) id WAA00694; Sun, 21 Mar 1999 22:38:17 -0600 (CST) (envelope-from joelh@gnu.org) Date: Sun, 21 Mar 1999 22:38:17 -0600 (CST) Message-Id: <199903220438.WAA00694@detlev.UUCP> X-Authentication-Warning: detlev.UUCP: joelh set sender to joelh@gnu.org using -f To: freebsd-current@freebsd.org Subject: syslogd meets The Sorcerer's Apprentice From: Joel Ray Holveck Reply-To: joelh@gnu.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'd like to add safeguards to keep syslogd from cascading its own error messages. To describe more fully: I just came back from a weekend getaway and discovered my crash box screaming bloody murder. I haven't had any odd experiments running for quite some time now. A quick look at the top of /var/log/messages.0 showed: Mar 18 00:00:00 detlev newsyslog[543]: logfile turned over Mar 21 15:44:25 detlev syslogd: /dev/ttyv1: Too many open files in system Mar 21 15:44:25 detlev syslogd: /dev/ttyv2: Too many open files in system Mar 21 15:44:25 detlev syslogd: /dev/ttyp0: Too many open files in system Mar 21 15:44:25 detlev syslogd: /dev/ttyp2: Too many open files in system Mar 21 15:44:25 detlev syslogd: /dev/ttyp3: Too many open files in system Mar 21 15:44:25 detlev syslogd: /dev/console: Too many open files in system: Too many open files in system Mar 21 15:44:25 detlev syslogd: /dev/ttyv1: Too many open files in system Mar 21 15:44:25 detlev syslogd: /dev/ttyv2: Too many open files in system Mar 21 15:44:25 detlev syslogd: /dev/ttyp0: Too many open files in system Mar 21 15:44:25 detlev syslogd: /dev/ttyp2: Too many open files in system Mar 21 15:44:25 detlev syslogd: /dev/ttyp3: Too many open files in system Mar 21 15:44:25 detlev /kernel: file: table is full Mar 21 15:44:25 detlev last message repeated 41 times Mar 21 15:44:25 detlev sendmail[17482]: PAA17481: SYSERR(UID0): Can't create transcript file xfPAA17482: Too many open files in system Mar 21 15:44:25 detlev sendmail[17482]: PAA17481: SYSERR(UID0): Can't open /dev/null: Too many open files in system Mar 21 15:44:26 detlev syslogd: /var/run/utmp: Too many open files in system Mar 21 15:44:26 detlev syslogd: /var/run/utmp: Too many open files in system Mar 21 15:44:26 detlev /kernel: file: table is full Mar 21 15:44:26 detlev syslogd: /var/run/utmp: Too many open files in system Mar 21 15:44:26 detlev last message repeated 3 times Mar 21 15:44:26 detlev /kernel: file: table is full Mar 21 15:44:26 detlev syslogd: /var/run/utmp: Too many open files in system Mar 21 15:44:26 detlev last message repeated 3 times After that it settled down to just repeating: Mar 21 15:45:30 detlev syslogd: /dev/ttyv1: Too many open files in system Mar 21 15:45:30 detlev syslogd: /dev/ttyv2: Too many open files in system Mar 21 15:45:30 detlev syslogd: /dev/ttyp0: Too many open files in system Mar 21 15:45:30 detlev syslogd: /dev/ttyp2: Too many open files in system Mar 21 15:45:30 detlev syslogd: /dev/ttyp3: Too many open files in system Mar 21 15:45:30 detlev /kernel: file: table is full Evidently it was recording about 125 log messages per second. I came home to discover a full /var, a 25 MB uncompressed messages.0, no /var/log/messages at all, and overall a fairly unhappy computer. (Evidently, when newsyslog ran, things were already hosed. It could move messages.0, but not gzip it or create /var/log/messages.) This is all from a March 13 build, I believe, if it matters. MAXUSERS is set to 20, and there were probably six logins including a small X session at the time. All had been idle for hours. (I figure something was leaking fd's bad.) Now, I don't know what set this off. I moved the messages.0 to another filesystem, rebooted, recreated /var/log/messages, and restarted syslogd. Like I say, I don't know what set this off. That's once concern, but will take more investigation. My concern is whether we should keep syslogd from going into Sorcerer's Apprentice mode like this. What do you think about adding safeguards against syslogd logging more than, say, thirty messages per hour saying why can't log messages? Cheers, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 21:10: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 2D11A14CFC for ; Sun, 21 Mar 1999 21:10:01 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id VAA39607; Sun, 21 Mar 1999 21:09:23 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: John Baldwin Cc: freebsd-current@freebsd.org Subject: Re: /etc/rc.conf, take 46! In-reply-to: Your message of "Sun, 21 Mar 1999 22:12:03 EST." Date: Sun, 21 Mar 1999 21:09:23 -0800 Message-ID: <39605.922079363@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The problem with putting code in /etc/defaults/rc.conf is that simplistic parsers which read it as ``var = value # optional comment'' get very confused by for loops or function declarations or what have you. It also makes it more difficult to read in /etc/{*,.}rc.conf from an admin program, permute it in some way, and then write out a whole new config file - you have to detect the meta-information somehow and preserve it across saves in addition to just parsing variables (which is more straight-forward to say the least). - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 21 23:49:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id BCE17150D3; Sun, 21 Mar 1999 23:49:38 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA16584; Sun, 21 Mar 1999 23:48:04 -0800 (PST) (envelope-from dillon) Date: Sun, 21 Mar 1999 23:48:04 -0800 (PST) From: Matthew Dillon Message-Id: <199903220748.XAA16584@apollo.backplane.com> To: Brian Feldman Cc: Alfred Perlstein , "John S. Dyson" , samit@usa.ltindia.com, commiters@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: rfork() References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :proc B returns since proc B is going to immediately switch over to a new :> :stack? :> :> The return address for the procedure call is on the stack. If something :> munges the stack after the physical rfork occurs but before both processes :> can return from the rfork() clib function, then one of the processes :> attempting to return will pop a bogus return address and seg fault. : :What's to stop the RFSTACK from copying the stack itself into the new stack :that is located elsewhere in RAM and attached to the vm space? Actually, :rfork() would just set it in the trap frame anyway, so there would be no :extra user code to do this. Why make rfork() a thousand times slower when performance is almost certainly an issue for the people using it? Since the one of the big points of using rfork() the way we are using it is to avoid copying pagetables, descriptor tables, and so forth, we sure don't want to add any back in! :> : Brian Feldman _ __ ___ ___ ___ :> : Brian Feldman _ __ ___ ___ ___ -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 22 0:44:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from stampede.cs.berkeley.edu (stampede.CS.Berkeley.EDU [128.32.45.124]) by hub.freebsd.org (Postfix) with ESMTP id E31AD14F9E; Mon, 22 Mar 1999 00:44:49 -0800 (PST) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca43-247.ix.netcom.com [209.111.209.247]) by stampede.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id AAA28529; Mon, 22 Mar 1999 00:44:29 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.2/8.6.9) id AAA29637; Mon, 22 Mar 1999 00:44:25 -0800 (PST) Date: Mon, 22 Mar 1999 00:44:25 -0800 (PST) Message-Id: <199903220844.AAA29637@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: current@freebsd.org Cc: ports@freebsd.org Subject: packages-4-current now being populated From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just started the first build of packages-4-current. I'm planning to recompile it and packages-3-stable once a week or so. Errors are at "http://bento.freebsd.org/~asami/errorlogs/", as usual. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 22 1: 9:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from nomad.dataplex.net (nomad.dataplex.net [216.140.184.163]) by hub.freebsd.org (Postfix) with ESMTP id 371DC14CE1 for ; Mon, 22 Mar 1999 01:09:37 -0800 (PST) (envelope-from rkw@dataplex.net) Received: from localhost (rkw@localhost) by nomad.dataplex.net (8.9.2/8.9.2) with ESMTP id DAA71699; Mon, 22 Mar 1999 03:09:03 -0600 (CST) (envelope-from rkw@dataplex.net) X-Authentication-Warning: nomad.dataplex.net: rkw owned process doing -bs Date: Mon, 22 Mar 1999 03:09:03 -0600 (CST) From: Richard Wackerbarth Reply-To: rkw@dataplex.net To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: /etc/rc.conf, take 46! In-Reply-To: <39218.922068401@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 21 Mar 1999, Jordan K. Hubbard wrote: > Index: netstart > =================================================================== > RCS file: /home/ncvs/src/etc/netstart,v > retrieving revision 1.53 > diff -u -u -r1.53 netstart > --- netstart 1999/02/10 18:08:16 1.53 > +++ netstart 1999/03/22 01:54:16 > @@ -12,8 +12,11 @@ > # If there is a global system configuration file, suck it in. > if [ -f /etc/defaults/rc.conf ]; then > . /etc/defaults/rc.conf > -elif [ -f /etc/rc.conf ]; then > - . /etc/rc.conf > + for i in ${rc_conf_files}; do > + if [ -f $i ]; then > + . $i > + fi > + done > fi There is a problem with this approach. /etc/defaults/rc.conf defines ${rc_conf_files} However, I have no chance to override it before it is used. When I wrote my comment about "code" in rc.conf, I was actually thinking about /etc/defaults/rc.conf and the recursion loop that that creates when someone copies it to /etc/rc.conf. You can, and IMHO should, make the defaults strictly variables. However, I fear that you need a bit more logic to allow the overriding of ${rc_conf_files}. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 22 1:13:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 013FF14D5C for ; Mon, 22 Mar 1999 01:13:54 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id SAA24104; Mon, 22 Mar 1999 18:13:48 +0900 (JST) Message-ID: <36F608F6.1F2C1160@newsguy.com> Date: Mon, 22 Mar 1999 18:10:14 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: "Jordan K. Hubbard" , current@freebsd.org Subject: Re: /etc/rc.conf, take 46! References: <39218.922068401@zippy.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Forget about code in rc.conf. Put the logic in the the scripts. Or, better, put the logic in rc.suck (well, find a better name... :), and . /etc/rc.suck instead. "Jordan K. Hubbard" wrote: > > OK, so it seems everyone's found something to like and dislike about > the new scheme. In that regard, it seems pretty much equivalent to > the previous layout when that was first introduced. :) > > However, incremental refinement for this stuff has always been the > order of the day, so in that spirit, here's my proposal to deal with > the most recent set of gripes: That rc.conf contains "code" in > addition to data. > > The following diffs make rc.conf a variable-only file, at the cost of > distributing the hook-calling mechanism into all the former clients of > rc.conf. That really doesn't bother me if it doesn't bother you, and > further optimization of it can always be another future incremental > refinement. Another incremental, albeit contraversial, refinement > would be to change /etc/defaults/rc.conf and friends into something > truely machine-parsable, changing statements like this: > > if [ -f /some/conf/file ]; then > . /some/conf/file > fi > > Into something like this: > > if [ -f /some/conf/file ]; then > eval `/sbin/rcvtosh /some/conf/file` > fi > > But these changes do not attempt to do that, they simply attempt to > make the existing rc.conf format somewhat easier to parse. Comments > requested. > > Index: netstart > =================================================================== > RCS file: /home/ncvs/src/etc/netstart,v > retrieving revision 1.53 > diff -u -u -r1.53 netstart > --- netstart 1999/02/10 18:08:16 1.53 > +++ netstart 1999/03/22 01:54:16 > @@ -12,8 +12,11 @@ > # If there is a global system configuration file, suck it in. > if [ -f /etc/defaults/rc.conf ]; then > . /etc/defaults/rc.conf > -elif [ -f /etc/rc.conf ]; then > - . /etc/rc.conf > + for i in ${rc_conf_files}; do > + if [ -f $i ]; then > + . $i > + fi > + done > fi > > if [ -f /etc/rc.network ]; then > Index: pccard_ether > =================================================================== > RCS file: /home/ncvs/src/etc/pccard_ether,v > retrieving revision 1.11 > diff -u -u -r1.11 pccard_ether > --- pccard_ether 1999/02/22 02:55:18 1.11 > +++ pccard_ether 1999/03/22 01:55:27 > @@ -7,11 +7,14 @@ > # example: pccard_ether ep0 -link0 > # > > -# Suck in the configuration variables > +# If there is a global system configuration file, suck it in. > if [ -f /etc/defaults/rc.conf ]; then > . /etc/defaults/rc.conf > -elif [ -f /etc/rc.conf ]; then > - . /etc/rc.conf > + for i in ${rc_conf_files}; do > + if [ -f $i ]; then > + . $i > + fi > + done > fi > > if [ "x$pccard_ifconfig" != "xNO" ] ; then > Index: rc > =================================================================== > RCS file: /home/ncvs/src/etc/rc,v > retrieving revision 1.183 > diff -u -u -r1.183 rc > --- rc 1999/03/17 04:00:04 1.183 > +++ rc 1999/03/22 01:56:24 > @@ -33,11 +33,13 @@ > fi > > # If there is a global system configuration file, suck it in. > -# > if [ -f /etc/defaults/rc.conf ]; then > . /etc/defaults/rc.conf > -elif [ -f /etc/rc.conf ]; then > - . /etc/rc.conf > + for i in ${rc_conf_files}; do > + if [ -f $i ]; then > + . $i > + fi > + done > fi > > # Configure ccd devices. > Index: rc.devfs > =================================================================== > RCS file: /home/ncvs/src/etc/rc.devfs,v > retrieving revision 1.4 > diff -u -u -r1.4 rc.devfs > --- rc.devfs 1999/02/10 18:08:16 1.4 > +++ rc.devfs 1999/03/22 01:56:39 > @@ -1,11 +1,15 @@ > # > # $Id: rc.devfs,v 1.4 1999/02/10 18:08:16 jkh Exp $ > # > + > # If there is a global system configuration file, suck it in. > if [ -f /etc/defaults/rc.conf ]; then > . /etc/defaults/rc.conf > -elif [ -f /etc/rc.conf ]; then > - . /etc/rc.conf > + for i in ${rc_conf_files}; do > + if [ -f $i ]; then > + . $i > + fi > + done > fi > > # Setup DEVFS, ie permisisons, links etc. > Index: rc.diskless2 > =================================================================== > RCS file: /home/ncvs/src/etc/rc.diskless2,v > retrieving revision 1.2 > diff -u -u -r1.2 rc.diskless2 > --- rc.diskless2 1999/02/10 18:08:16 1.2 > +++ rc.diskless2 1999/03/22 01:57:04 > @@ -2,11 +2,13 @@ > # > > # If there is a global system configuration file, suck it in. > -# > if [ -f /etc/defaults/rc.conf ]; then > . /etc/defaults/rc.conf > -elif [ -f /etc/rc.conf ]; then > - . /etc/rc.conf > + for i in ${rc_conf_files}; do > + if [ -f $i ]; then > + . $i > + fi > + done > fi > > mount_mfs -s ${var_run_sectors:=2048} -T qp120at dummy /var/run > Index: rc.firewall > =================================================================== > RCS file: /home/ncvs/src/etc/rc.firewall,v > retrieving revision 1.20 > diff -u -u -r1.20 rc.firewall > --- rc.firewall 1999/02/10 18:08:16 1.20 > +++ rc.firewall 1999/03/22 01:57:16 > @@ -2,11 +2,14 @@ > # Setup system for firewall service. > # $Id: rc.firewall,v 1.20 1999/02/10 18:08:16 jkh Exp $ > > -# Suck in the configuration variables. > +# If there is a global system configuration file, suck it in. > if [ -f /etc/defaults/rc.conf ]; then > . /etc/defaults/rc.conf > -elif [ -f /etc/rc.conf ]; then > - . /etc/rc.conf > + for i in ${rc_conf_files}; do > + if [ -f $i ]; then > + . $i > + fi > + done > fi > > ############ > Index: defaults/rc.conf > =================================================================== > RCS file: /home/ncvs/src/etc/defaults/rc.conf,v > retrieving revision 1.4 > diff -u -u -r1.4 rc.conf > --- rc.conf 1999/03/17 04:00:04 1.4 > +++ rc.conf 1999/03/22 01:58:02 > @@ -202,16 +202,3 @@ > kern_securelevel="-1" # range: -1..3 ; `-1' is the most insecure > update_motd="YES" # update version info in /etc/motd (or NO) > vinum_drives="" # put in names of disks containing vinum drives > - > -############################################################## > -### Allow local configuration override at the very end here ## > -############################################################## > -# > -# > - > -for i in ${rc_conf_files}; do > - if [ -f $i ]; then > - . $i > - fi > -done > - > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What happened?" "It moved, sir!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 22 1:59: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from quackerjack.cc.vt.edu (quackerjack.cc.vt.edu [198.82.160.250]) by hub.freebsd.org (Postfix) with ESMTP id 9BFEC1513B for ; Mon, 22 Mar 1999 01:58:58 -0800 (PST) (envelope-from jobaldwi@vt.edu) Received: from sable.cc.vt.edu (sable.cc.vt.edu [128.173.16.30]) by quackerjack.cc.vt.edu (8.8.8/8.8.8) with ESMTP id EAA15430; Mon, 22 Mar 1999 04:58:31 -0500 (EST) Received: from john.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.63]) by sable.cc.vt.edu (8.8.8/8.8.8) with ESMTP id EAA25633; Mon, 22 Mar 1999 04:58:30 -0500 (EST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 22 Mar 1999 04:58:29 -0500 (EST) From: John Baldwin To: Richard Wackerbarth Subject: Re: /etc/rc.conf, take 46! Cc: current@FreeBSD.ORG, "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Mar-99 Richard Wackerbarth wrote: > There is a problem with this approach. > > /etc/defaults/rc.conf defines ${rc_conf_files} > However, I have no chance to override it before it is used. > > When I wrote my comment about "code" in rc.conf, I was > actually thinking about /etc/defaults/rc.conf and the > recursion loop that that creates when someone copies it to > /etc/rc.conf. > > You can, and IMHO should, make the defaults strictly variables. > > However, I fear that you need a bit more logic to allow the > overriding of ${rc_conf_files}. Where are going to override it? If we use some other config file that gets sucked in to /etc/defaults/rc.conf we'd have a config file included in another config file that tells it what other config files to include. If this keeps up we'll end up with a bunch of config files floating around that config other config files, which will end up messy and confusing for newbies, IMHO. > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message --- John Baldwin -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 22 2:23:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from nomad.dataplex.net (nomad.dataplex.net [216.140.184.163]) by hub.freebsd.org (Postfix) with ESMTP id 760DA14A2F for ; Mon, 22 Mar 1999 02:23:37 -0800 (PST) (envelope-from rkw@dataplex.net) Received: from localhost (rkw@localhost) by nomad.dataplex.net (8.9.2/8.9.2) with ESMTP id EAA72082; Mon, 22 Mar 1999 04:23:15 -0600 (CST) (envelope-from rkw@dataplex.net) X-Authentication-Warning: nomad.dataplex.net: rkw owned process doing -bs Date: Mon, 22 Mar 1999 04:23:15 -0600 (CST) From: Richard Wackerbarth Reply-To: rkw@dataplex.net To: John Baldwin Cc: current@FreeBSD.ORG, "Jordan K. Hubbard" Subject: Re: /etc/rc.conf, take 46! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Mar 1999, John Baldwin wrote: > > On 22-Mar-99 Richard Wackerbarth wrote: > > There is a problem with this approach. > > > > /etc/defaults/rc.conf defines ${rc_conf_files} > > However, I have no chance to override it before it is used. > > > > However, I fear that you need a bit more logic to allow the > > overriding of ${rc_conf_files}. > > Where are going to override it? If we use some other config file that gets > sucked in to /etc/defaults/rc.conf we'd have a config file included in > another config file that tells it what other config files to include. If this > keeps up we'll end up with a bunch of config files floating around that config > other config files, which will end up messy and confusing for newbies, IMHO. Unless someone comes up with a scheme that tracks set membership and allows us to add to that set, I think that we should stick to the "simple" approach. /etc/defaults/rc.conf defines ${rc_conf_files} to be "/etc/rc.conf" /etc/rc.conf is allowed to override this definition to include additional files such as "/etc/rc.conf.local" Those files get sucked in. - - - An alternate, and perhaps cleaner approach would be to always suck in /etc/defaults/rc.conf and /etc/rc.conf. Then suck in those files specified in ${additional_rc_conf_files}. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 22 4:24: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from zone.syracuse.net (zone.syracuse.net [209.2.141.6]) by hub.freebsd.org (Postfix) with ESMTP id 8DCA714A09; Mon, 22 Mar 1999 04:24:00 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by zone.syracuse.net (8.9.2/8.9.2) with ESMTP id MAA10149; Mon, 22 Mar 1999 12:23:12 GMT (envelope-from green@unixhelp.org) Date: Mon, 22 Mar 1999 12:23:12 +0000 (GMT) From: Brian Feldman X-Sender: green@zone.syracuse.net To: Matthew Dillon Cc: Alfred Perlstein , "John S. Dyson" , samit@usa.ltindia.com, commiters@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: rfork() In-Reply-To: <199903220748.XAA16584@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 21 Mar 1999, Matthew Dillon wrote: > :> :proc B returns since proc B is going to immediately switch over to a new > :> :stack? > :> > :> The return address for the procedure call is on the stack. If something > :> munges the stack after the physical rfork occurs but before both processes > :> can return from the rfork() clib function, then one of the processes > :> attempting to return will pop a bogus return address and seg fault. > : > :What's to stop the RFSTACK from copying the stack itself into the new stack > :that is located elsewhere in RAM and attached to the vm space? Actually, > :rfork() would just set it in the trap frame anyway, so there would be no > :extra user code to do this. > > Why make rfork() a thousand times slower when performance is almost > certainly an issue for the people using it? Since the one of the big > points of using rfork() the way we are using it is to avoid copying > pagetables, descriptor tables, and so forth, we sure don't want to > add any back in! It wouldn't be appreciably slower. The only difference would be when one provides RFSTACK and extra arg stackaddr, which would simplify things for the coder greatly! This would allow the old method to still work, so what's the problem? If anything, it would save _human_ time. > > > :> : Brian Feldman _ __ ___ ___ ___ > :> > : Brian Feldman _ __ ___ ___ ___ > > -Matt > Matthew Dillon > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 22 4:29:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from zone.syracuse.net (zone.syracuse.net [209.2.141.6]) by hub.freebsd.org (Postfix) with ESMTP id 5DF66151C0; Mon, 22 Mar 1999 04:29:18 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by zone.syracuse.net (8.9.2/8.9.2) with ESMTP id MAA10180; Mon, 22 Mar 1999 12:27:52 GMT (envelope-from green@unixhelp.org) Date: Mon, 22 Mar 1999 12:27:52 +0000 (GMT) From: Brian Feldman X-Sender: green@zone.syracuse.net To: Peter Wemm Cc: Matthew Dillon , Alfred Perlstein , "John S. Dyson" , samit@usa.ltindia.com, commiters@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: rfork() In-Reply-To: <199903220334.LAA52679@spinner.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Mar 1999, Peter Wemm wrote: > Matthew Dillon wrote: > > :Hence the NEW flag RFSTACK. Why would this be a bad thing? This would keep > > :the old behavior and allow much nicer new behavior. I didn't suggest > > :changing the old behavior. This would just greatly simplify things so all of > > > > I think Richard Seaman has it right: the stack needs to be passed. > > > > Why don't we simply implement the linux clone()? It sounds to me that > > it would be trivial. > > Doing clone() in libc that calls rfork(2) and doing all the stack setup > should be pretty easy.. (Richard has done it already, yes?) On the other > hand, the linux emulator needs it so there's a counter-argument for making > it a proper syscall outright. Leaving the rfork(2) stuff unmolested and at > least resembling it's plan9 origins probably has some merit - adding extra > arguments would mess that up. If we do varargs, then nothing could notice the difference. It's still backward-compatible, but it would be more powerful. How could that break something? Remember that the traditional int open(const char *, int, int) was changed to int open(const char *, int, ...) without any incompatibilities. > > Cheers, > -Peter > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 22 5:10:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 25331150E5 for ; Mon, 22 Mar 1999 04:53:00 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id VAA19109; Mon, 22 Mar 1999 21:52:49 +0900 (JST) Message-ID: <36F63A35.CA7E8F82@newsguy.com> Date: Mon, 22 Mar 1999 21:40:21 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: rkw@dataplex.net Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: /etc/rc.conf, take 46! References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Richard Wackerbarth wrote: > > When I wrote my comment about "code" in rc.conf, I was > actually thinking about /etc/defaults/rc.conf and the > recursion loop that that creates when someone copies it to > /etc/rc.conf. > > You can, and IMHO should, make the defaults strictly variables. > > However, I fear that you need a bit more logic to allow the > overriding of ${rc_conf_files}. Which, btw, is how loader.conf works... :-) But, then again, that's a Forth program processing it. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What happened?" "It moved, sir!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 22 5:29: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from quackerjack.cc.vt.edu (quackerjack.cc.vt.edu [198.82.160.250]) by hub.freebsd.org (Postfix) with ESMTP id A65A614C13 for ; Mon, 22 Mar 1999 05:28:50 -0800 (PST) (envelope-from jobaldwi@vt.edu) Received: from sable.cc.vt.edu (sable.cc.vt.edu [128.173.16.30]) by quackerjack.cc.vt.edu (8.8.8/8.8.8) with ESMTP id IAA25361; Mon, 22 Mar 1999 08:28:30 -0500 (EST) Received: from john.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.63]) by sable.cc.vt.edu (8.8.8/8.8.8) with ESMTP id IAA27601; Mon, 22 Mar 1999 08:28:29 -0500 (EST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 22 Mar 1999 08:28:29 -0500 (EST) From: John Baldwin To: Richard Wackerbarth Subject: Re: /etc/rc.conf, take 46! Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG, John Baldwin Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Mar-99 Richard Wackerbarth wrote: > On Mon, 22 Mar 1999, John Baldwin wrote: > >> >> On 22-Mar-99 Richard Wackerbarth wrote: >> > There is a problem with this approach. >> > >> > /etc/defaults/rc.conf defines ${rc_conf_files} >> > However, I have no chance to override it before it is used. >> > >> > However, I fear that you need a bit more logic to allow the >> > overriding of ${rc_conf_files}. >> >> Where are going to override it? If we use some other config file that gets >> sucked in to /etc/defaults/rc.conf we'd have a config file included in >> another config file that tells it what other config files to include. If >> this >> keeps up we'll end up with a bunch of config files floating around that >> config >> other config files, which will end up messy and confusing for newbies, IMHO. > > Unless someone comes up with a scheme that tracks set membership and > allows us to add to that set, I think that we should stick to the "simple" > approach. > > /etc/defaults/rc.conf defines ${rc_conf_files} to be "/etc/rc.conf" > > /etc/rc.conf is allowed to override this definition to include additional > files such as "/etc/rc.conf.local" However, the original definition has already been used once the /etc/rc.conf has been read. Unless you are going to call the for loop twice, once after /etc/defaults/rc.conf to include /etc/rc.conf and once after /etc/rc.conf to include the extra stuff you define, your changes to ${rc_conf_files} in /etc/rc.conf will never take effect. > Those files get sucked in. > > - - - > > An alternate, and perhaps cleaner approach would be to always suck in > /etc/defaults/rc.conf and /etc/rc.conf. Then suck in those files specified > in ${additional_rc_conf_files}. That would work, but then we have two includes everywhere that we have 1 now. --- John Baldwin -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 22 5:29:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 58318151ED; Mon, 22 Mar 1999 05:29:15 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id OAA04282; Mon, 22 Mar 1999 14:28:55 +0100 (CET) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id OAA14971; Mon, 22 Mar 1999 14:28:50 +0100 (CET) (envelope-from phk@critter.freebsd.dk) Date: Mon, 22 Mar 1999 14:28:50 +0100 Message-ID: <14969.922109330.1@critter.freebsd.dk> From: Poul-Henning Kamp Subject: NTP kernel support in FreeBSD, a few notes... MIME-Version: 1.0 Content-Type: multipart/digest; boundary="----- =_aaaaaaaaaa" Content-Description: Blind Carbon Copy Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ------- =_aaaaaaaaaa Content-Type: message/rfc822 Content-Description: Original Message Subject: NTP kernel support in FreeBSD, a few notes... Date: Mon, 22 Mar 1999 14:28:50 +0100 Message-ID: <14969.922109330@critter.freebsd.dk> From: Poul-Henning Kamp Bcc: Blind Distribution List: ; MIME-Version: 1.0 I have just merged the recent modifications to the kernel support for NTPD from -current to -stable. We now fully support both XNTPD version 3 (as in usr/src/usr.sbin) and NTPD version 4 in both -current & -stable. In fact, we not only support it, we define state of the art performance when using the pci/xrpu.c driver. We have only adopted the PLL/FLL section of Dave Mills "nanokernel", the rest of the stuff is still "timecounter" based. We have PPS-API support on the parallel port and on the pci/xrpu.c driver, John Hay has submitted patches to me for PPS-API support on sio.c (DCD) these will be committed to -current once I have them tested. I may experient a bit with hardpps() in -current if I can find the time, but these experiments will not be reflected in -stable until some kind of conclusion has been reached. The issue at hand is if a "normal" 2nd order PLL would do better for precise-phase hardpps() signals ("prefer peers") Anyone out there with hardpps() able refclocks are invited to join in on these experients. If you want to try out the pci/xrpu.c timestamping function, send me email, I have not committed the VHDL & stuff to the tree yet. Hope you like it... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! ------- =_aaaaaaaaaa-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 22 5:59:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id D2C5514F95 for ; Mon, 22 Mar 1999 05:59:17 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id WAA00606; Mon, 22 Mar 1999 22:58:54 +0900 (JST) Message-ID: <36F64C3D.9369B963@newsguy.com> Date: Mon, 22 Mar 1999 22:57:17 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: John Baldwin Cc: Richard Wackerbarth , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: /etc/rc.conf, take 46! References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin wrote: > > However, the original definition has already been used once the /etc/rc.conf > has been read. Unless you are going to call the for loop twice, once after > /etc/defaults/rc.conf to include /etc/rc.conf and once after /etc/rc.conf to > include the extra stuff you define, your changes to ${rc_conf_files} in > /etc/rc.conf will never take effect. Make a sucking function (or separate script), call it recursively for each time rc_conf_files change. #!/bin/sh for file in $1 do . $file if [ "${rc_conf_files}X" != "$*X" ] then . $0 "${rc_conf_files}" fi done -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What happened?" "It moved, sir!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 22 6:27:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (Postfix) with ESMTP id E603814CFF for ; Mon, 22 Mar 1999 06:27:51 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.3/8.9.3) id IAA54119; Mon, 22 Mar 1999 08:26:01 -0600 (CST) (envelope-from dick) Date: Mon, 22 Mar 1999 08:26:01 -0600 From: "Richard Seaman, Jr." To: Peter Wemm Cc: Matthew Dillon , Brian Feldman , "John S. Dyson" , freebsd-current@FreeBSD.ORG Subject: Re: rfork() Message-ID: <19990322082601.L32029@tar.com> References: <199903211721.JAA13495@apollo.backplane.com> <199903220334.LAA52679@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199903220334.LAA52679@spinner.netplex.com.au>; from Peter Wemm on Mon, Mar 22, 1999 at 11:34:25AM +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 22, 1999 at 11:34:25AM +0800, Peter Wemm wrote: > Doing clone() in libc that calls rfork(2) and doing all the stack setup > should be pretty easy.. (Richard has done it already, yes?) Its in package at http://lt.tar.com/linuxthreads.tar.gz . If anyone wants to grab it out of there an put it into shape to commit it, be my guest. > On the other > hand, the linux emulator needs it so there's a counter-argument for making > it a proper syscall outright. Leaving the rfork(2) stuff unmolested and at > least resembling it's plan9 origins probably has some merit - adding extra > arguments would mess that up. I) clone syscall --------------------- The linux emulator needs (and has) a clone syscall: int linux_clone(int flags, void *stack) The value of an exit signal is passed in the lower 8 bits of the flags argument, the linux counterparts to the FreeBSD RF* flags are passed in the balance of the flags argument. I haven't seen or heard of a linux app that calls the clone syscall directly. I know of two "apps", linuxthreads and the linux version of WINE, that call the linux glibc version of clone (see below), which is a wrapper for the syscall. The only thing that the linux syscall does, that can't be done easily in FreeBSD using rfork and an appropriate wrapper to rfork, is pass in the exit signal. rfork does have a flag to set an exit signal of SIGUSR1, but it does not conveniently take a parameter to set it more flexibly. OTOH, the only FreeBSD app I know of that actually sets an exit signal other that the default SIGCHLD, is the linuxthreads port noted above. I'm not sure there is really a need for a "clone" syscall at this point, but if you wanted it, you could just copy the linux_clone code in linux_misc.c . You would have to decide if you want the flags parameter to take the linux flags values, or FreeBSD flags (the emulator has to take the linux values, obviously). My vote: don't bother with a syscall until there's a demonstrated need. II) clone in libc ----------------- Linux glibc has a clone call wrapper for the clone syscall, defined as: int clone (int (*fn) (void *arg), void *stack, int flags, void *arg) The stack and flags are passed directly to the clone syscall, and the fn(arg) is the user function the cloned process should execute. Its easy enough to implement this in FreeBSD as a wrapper for rfork. If you want to facilitate porting linux code, you would want the flags argument to take linux flags, which would then be translated into their FreeBSD counterparts before rfork is call. This is what the code in the linuxthreads port does, and you are welcome to commit it. The only issue here is whether people need to port linux code that calls clone directly. As noted above, the only code I know of that calls clone directly is WINE and linuxthreads. All the rest of the code uses pthread_create, which only indirectly calls clone. My vote: I haven't seen the need, but if there is one, lets do it. III) libc rfork wrapper ----------------------- It probably would be nice to have a libc rfork wrapper that grafts a stack and a user function onto the rfork'd child process. But, it should probably take FreeBSD flags, and there's no reason to call it "clone". John Dyson's thr_fork is one such implementation. Luoqi Chen posted another variation to either -hackers or -current maybe 6-9 months ago. Matt Dillon just posted yet another variation. Or, the linuxthreads port has a variation of the clone call that has the same API as the linux clone call, but takes FreeBSD flags (see clone.S). My vote: its worth doing, but not a top priority. The main issue is to decide what interface would be most convenient. Its not a top priority since the code already exists for those (rare) cases where someone really needs it. And, lets not call it "clone". -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 22 6:29: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from quackerjack.cc.vt.edu (quackerjack.cc.vt.edu [198.82.160.250]) by hub.freebsd.org (Postfix) with ESMTP id 54A6D14ED8 for ; Mon, 22 Mar 1999 06:28:57 -0800 (PST) (envelope-from jobaldwi@vt.edu) Received: from sable.cc.vt.edu (sable.cc.vt.edu [128.173.16.30]) by quackerjack.cc.vt.edu (8.8.8/8.8.8) with ESMTP id JAA06392; Mon, 22 Mar 1999 09:28:30 -0500 (EST) Received: from john.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.63]) by sable.cc.vt.edu (8.8.8/8.8.8) with ESMTP id JAA18595; Mon, 22 Mar 1999 09:28:26 -0500 (EST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <36F64C3D.9369B963@newsguy.com> Date: Mon, 22 Mar 1999 09:28:29 -0500 (EST) From: John Baldwin To: "Daniel C. Sobral" Subject: Re: /etc/rc.conf, take 46! Cc: current@FreeBSD.ORG, "Jordan K. Hubbard" , Richard Wackerbarth , John Baldwin Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Mar-99 Daniel C. Sobral wrote: > John Baldwin wrote: >> >> However, the original definition has already been used once the /etc/rc.conf >> has been read. Unless you are going to call the for loop twice, once after >> /etc/defaults/rc.conf to include /etc/rc.conf and once after /etc/rc.conf to >> include the extra stuff you define, your changes to ${rc_conf_files} in >> /etc/rc.conf will never take effect. > > Make a sucking function (or separate script), call it recursively > for each time rc_conf_files change. > >#!/bin/sh > for file in $1 > do > . $file > if [ "${rc_conf_files}X" != "$*X" ] then > . $0 "${rc_conf_files}" > fi > done I would move the if-statemeount outside the for loop. Say config file a defines rc_conf_files="b c", and config file b defines rc_conf_files="d". a is executed and then b is sucked in, rc_conf_files has changed, so the function calls itself to read in config file "d". Then the recursive call returns and "c" is read. Thus, the files would be read in the order a, b, d, c and "c" could possibly override customizations the user had put in d. To me the logical order for the files to be read in would be a, b, c, d. Moving the if-statement outside of the for loop would give the latter behavior. Other than that it works for me. > -- > Daniel C. Sobral (8-DCS) > dcs@newsguy.com > dcs@freebsd.org > > "What happened?" > "It moved, sir!" --- John Baldwin -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 22 6:55:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from nomad.dataplex.net (nomad.dataplex.net [216.140.184.163]) by hub.freebsd.org (Postfix) with ESMTP id AE56514ED8 for ; Mon, 22 Mar 1999 06:55:25 -0800 (PST) (envelope-from rkw@dataplex.net) Received: from localhost (rkw@localhost) by nomad.dataplex.net (8.9.2/8.9.2) with ESMTP id IAA73368; Mon, 22 Mar 1999 08:55:00 -0600 (CST) (envelope-from rkw@dataplex.net) X-Authentication-Warning: nomad.dataplex.net: rkw owned process doing -bs Date: Mon, 22 Mar 1999 08:55:00 -0600 (CST) From: Richard Wackerbarth Reply-To: rkw@dataplex.net To: John Baldwin Cc: current@FreeBSD.ORG Subject: Re: /etc/rc.conf, take 46! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Mar 1999, John Baldwin wrote: > > An alternate, and perhaps cleaner approach would be to always suck in > > /etc/defaults/rc.conf and /etc/rc.conf. Then suck in those files specified > > in ${additional_rc_conf_files}. > > That would work, but then we have two includes everywhere that we have 1 now. Then wrap the logic into a single call. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 22 7:30:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 9503114BD7 for ; Mon, 22 Mar 1999 07:30:35 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id AAA17303; Tue, 23 Mar 1999 00:30:24 +0900 (JST) Message-ID: <36F661B1.5961DD3E@newsguy.com> Date: Tue, 23 Mar 1999 00:28:49 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: John Baldwin Cc: current@FreeBSD.ORG, "Jordan K. Hubbard" , Richard Wackerbarth Subject: Re: /etc/rc.conf, take 46! References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin wrote: > > >#!/bin/sh > > for file in $1 > > do > > . $file > > if [ "${rc_conf_files}X" != "$*X" ] then > > . $0 "${rc_conf_files}" > > fi > > done > > I would move the if-statemeount outside the for loop. Say config file a defines > rc_conf_files="b c", and config file b defines rc_conf_files="d". a is > executed and then b is sucked in, rc_conf_files has changed, so the function > calls itself to read in config file "d". Then the recursive call returns and > "c" is read. Thus, the files would be read in the order a, b, d, c and "c" > could possibly override customizations the user had put in d. To me the > logical order for the files to be read in would be a, b, c, d. Moving the > if-statement outside of the for loop would give the latter behavior. Other > than that it works for me. So, if b define "d", and c define "e", you'll end up not loading "d". Aside from that, I like the behavior above for the same reason you don't. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What happened?" "It moved, sir!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 22 9:41:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from octopus.originative (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (Postfix) with ESMTP id 9167C15232 for ; Mon, 22 Mar 1999 09:41:38 -0800 (PST) (envelope-from paul@originative.co.uk) Received: by octopus with Internet Mail Service (5.5.2232.9) id ; Mon, 22 Mar 1999 17:39:32 -0000 Message-ID: From: paul@originative.co.uk To: rkw@dataplex.net Cc: current@freebsd.org Subject: RE: /etc/rc.conf, take 46! Date: Mon, 22 Mar 1999 17:39:31 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Richard Wackerbarth [mailto:rkw@dataplex.net] > Sent: 22 March 1999 10:23 > To: John Baldwin > Cc: current@FreeBSD.ORG; Jordan K. Hubbard > Subject: Re: /etc/rc.conf, take 46! > > > On Mon, 22 Mar 1999, John Baldwin wrote: > > > > > On 22-Mar-99 Richard Wackerbarth wrote: > > > There is a problem with this approach. > > > > > > /etc/defaults/rc.conf defines ${rc_conf_files} > > > However, I have no chance to override it before it is used. > > > > > > However, I fear that you need a bit more logic to allow the > > > overriding of ${rc_conf_files}. > > > > Where are going to override it? If we use some other > config file that gets > > sucked in to /etc/defaults/rc.conf we'd have a config file > included in > > another config file that tells it what other config files > to include. If this > > keeps up we'll end up with a bunch of config files floating > around that config > > other config files, which will end up messy and confusing > for newbies, IMHO. > > Unless someone comes up with a scheme that tracks set membership and > allows us to add to that set, I think that we should stick to > the "simple" > approach. > > /etc/defaults/rc.conf defines ${rc_conf_files} to be "/etc/rc.conf" > > /etc/rc.conf is allowed to override this definition to > include additional > files such as "/etc/rc.conf.local" > > Those files get sucked in. > > - - - > > An alternate, and perhaps cleaner approach would be to always suck in > /etc/defaults/rc.conf and /etc/rc.conf. Then suck in those > files specified > in ${additional_rc_conf_files}. I still think we're chasing our tails with all this configuration stuff. Why can't /etc/rc load /etc/defaults/rc.conf followed by /etc/rc.conf (if present). Don't have anything in /etc/defaults.rc.conf except default variable settings. The local admin can do what the hell they want in /etc/rc.conf, including putting in a bit of script to load /etc/rc.conf.local /etc/rc.conf.flavour_of_month etc. Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 22 9:48:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from rem.club.gagarinclub.ru (unknown [195.34.16.51]) by hub.freebsd.org (Postfix) with ESMTP id 14E2F155EC for ; Mon, 22 Mar 1999 09:47:34 -0800 (PST) (envelope-from firma@windoms.sitek.net) Received: from localhost (firma@localhost) by rem.club.gagarinclub.ru (8.9.3/8.9.3) with ESMTP id UAA00771 for ; Mon, 22 Mar 1999 20:49:32 +0300 (MSK) X-Authentication-Warning: rem.club.gagarinclub.ru: firma owned process doing -bs Date: Mon, 22 Mar 1999 20:49:32 +0300 (MSK) From: REM X-Sender: firma@rem.club.gagarinclub.ru To: current@FreeBSD.org Subject: Changing acd to wcd Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I'm FreeBSD-current (FreeBSD 4.0-current) user. The name of the wd.c and atapi.c based CDROM driver has been changed, but the file MAKEDEV has old structure. I can't make device wcd0! REM > 19990316: > The name of the old wd.c and atapi.c based CDROM driver has > been changed back to wcd. So update your config file to use > "device wcd" instead of "device acd". To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 22 10:31:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from ozz.etrust.ru (ozz.etrust.ru [195.2.84.116]) by hub.freebsd.org (Postfix) with ESMTP id 4B07F14BE2 for ; Mon, 22 Mar 1999 10:31:02 -0800 (PST) (envelope-from osa@etrust.ru) Received: from localhost (localhost [127.0.0.1]) by ozz.etrust.ru (Postfix) with ESMTP id A073E8D; Mon, 22 Mar 1999 21:30:41 +0300 (MSK) Date: Mon, 22 Mar 1999 21:30:41 +0300 (MSK) From: oZZ!!! To: REM Cc: current@FreeBSD.ORG Subject: Re: Changing acd to wcd In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Mar 1999, REM wrote: > Hi! > > I'm FreeBSD-current (FreeBSD 4.0-current) user. The name of the wd.c > and atapi.c based CDROM driver has been changed, but the file MAKEDEV > has old structure. I can't make device wcd0! > > REM > > > 19990316: > > The name of the old wd.c and atapi.c based CDROM driver has > > been changed back to wcd. So update your config file to use > > "device wcd" instead of "device acd". > > # cd /usr/src/etc/etc.i386 # % grep acd MAKEDEV # acd* "ATAPI CD-ROM disks" acd*|cd*|mcd*|scd*) acd*) units=`expr $i : '...\(.*\)'`; name=acd; blk=31; chr=117;; Rgdz, Sergey A. Osokin, osa@etrust.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 22 10:44: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id E893E14C20 for ; Mon, 22 Mar 1999 10:44:04 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id DAA03523; Tue, 23 Mar 1999 03:42:57 +0900 (JST) Message-ID: <36F68ECF.B9611A9A@newsguy.com> Date: Tue, 23 Mar 1999 03:41:19 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: "oZZ!!!" Cc: REM , current@FreeBSD.ORG Subject: Re: Changing acd to wcd References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "oZZ!!!" wrote: > > > I'm FreeBSD-current (FreeBSD 4.0-current) user. The name of the wd.c > > and atapi.c based CDROM driver has been changed, but the file MAKEDEV > > has old structure. I can't make device wcd0! > > > > REM > > > > > 19990316: > > > The name of the old wd.c and atapi.c based CDROM driver has > > > been changed back to wcd. So update your config file to use > > > "device wcd" instead of "device acd". > > > > > # cd /usr/src/etc/etc.i386 > # % grep acd MAKEDEV > # acd* "ATAPI CD-ROM disks" > acd*|cd*|mcd*|scd*) > acd*) units=`expr $i : '...\(.*\)'`; name=acd; blk=31; chr=117;; Since you did not pay attention to the commit message quoted, let me repeat it: "The name of the ... CDROM driver has been CHANGED BACK TO WCD." (My emphasis.) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Someone's trying to hack into our server." "Wow... How flattering!" "I know. There must be some mistake." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 22 12:55:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from mx4.dynasty.net (mail.dynasty.net [208.200.172.236]) by hub.freebsd.org (Postfix) with ESMTP id 4D74F15256 for ; Mon, 22 Mar 1999 12:55:14 -0800 (PST) (envelope-from cpinckard@dynasty.net) Received: from dynasty.net ([12.14.196.151]) by mx4.dynasty.net (Netscape Messaging Server 3.52) with ESMTP id 194; Mon, 22 Mar 1999 14:53:59 -0600 Message-ID: <36F6AB15.48DFD933@dynasty.net> Date: Mon, 22 Mar 1999 14:41:57 -0600 From: Chas X-Mailer: Mozilla 4.04 [en] (Win95; U) MIME-Version: 1.0 To: paul@originative.co.uk Cc: rkw@dataplex.net, current@freebsd.org Subject: Re: /etc/rc.conf, take 46! References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Now that sounz like a simple solution.:)) Paul... > > Unless someone comes up with a scheme that tracks set membership and > > allows us to add to that set, I think that we should stick to > > the "simple" > > approach. > > > > /etc/defaults/rc.conf defines ${rc_conf_files} to be "/etc/rc.conf" > > > > /etc/rc.conf is allowed to override this definition to > > include additional > > files such as "/etc/rc.conf.local" > > > > Those files get sucked in. > > > > - - - > > > > An alternate, and perhaps cleaner approach would be to always suck in > > /etc/defaults/rc.conf and /etc/rc.conf. Then suck in those > > files specified > > in ${additional_rc_conf_files}. > > I still think we're chasing our tails with all this configuration stuff. > > Why can't /etc/rc load /etc/defaults/rc.conf followed by /etc/rc.conf (if > present). Don't have anything in /etc/defaults.rc.conf except default > variable settings. > > The local admin can do what the hell they want in /etc/rc.conf, including > putting in a bit of script to load /etc/rc.conf.local > /etc/rc.conf.flavour_of_month etc. > > Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 22 12:55:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from Speed.FreeI.Net (speed.freei.net [209.162.132.18]) by hub.freebsd.org (Postfix) with ESMTP id 4B6BF152BA for ; Mon, 22 Mar 1999 12:55:30 -0800 (PST) (envelope-from gus@Speed.FreeI.Net) Received: from localhost (gus@localhost) by Speed.FreeI.Net (8.9.3/8.9.1) with ESMTP id MAA96845 for ; Mon, 22 Mar 1999 12:54:59 -0800 (PST) (envelope-from gus@Speed.FreeI.Net) Date: Mon, 22 Mar 1999 12:54:59 -0800 (PST) From: Gus R Bourg To: current@FreeBSD.Org Subject: ELF Question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a machine running a snap from back on 19981126. Is there still a problem moving from aout to elf. I remember a while back I had to on another machine do something weird to get the bootloader working. Thanks Gus To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 22 14:29:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from zone.syracuse.net (zone.syracuse.net [209.2.141.6]) by hub.freebsd.org (Postfix) with ESMTP id 1A1BA1532D for ; Mon, 22 Mar 1999 14:29:20 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by zone.syracuse.net (8.9.2/8.9.2) with ESMTP id WAA14733; Mon, 22 Mar 1999 22:28:35 GMT (envelope-from green@unixhelp.org) Date: Mon, 22 Mar 1999 22:28:35 +0000 (GMT) From: Brian Feldman X-Sender: green@zone.syracuse.net To: "Richard Seaman, Jr." Cc: Peter Wemm , Matthew Dillon , "John S. Dyson" , freebsd-current@FreeBSD.ORG Subject: Re: rfork() In-Reply-To: <19990322082601.L32029@tar.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Mar 1999, Richard Seaman, Jr. wrote: > On Mon, Mar 22, 1999 at 11:34:25AM +0800, Peter Wemm wrote: > > > Doing clone() in libc that calls rfork(2) and doing all the stack setup > > should be pretty easy.. (Richard has done it already, yes?) > > Its in package at http://lt.tar.com/linuxthreads.tar.gz . If anyone wants > to grab it out of there an put it into shape to commit it, be my guest. > > > On the other > > hand, the linux emulator needs it so there's a counter-argument for making > > it a proper syscall outright. Leaving the rfork(2) stuff unmolested and at > > least resembling it's plan9 origins probably has some merit - adding extra > > arguments would mess that up. > > I) clone syscall > --------------------- > The linux emulator needs (and has) a clone syscall: > > int linux_clone(int flags, void *stack) > > The value of an exit signal is passed in the lower 8 bits of the flags argument, > the linux counterparts to the FreeBSD RF* flags are passed in the balance > of the flags argument. > > I haven't seen or heard of a linux app that calls the clone syscall directly. > I know of two "apps", linuxthreads and the linux version of WINE, that call > the linux glibc version of clone (see below), which is a wrapper for the > syscall. > > The only thing that the linux syscall does, that can't be done easily in > FreeBSD using rfork and an appropriate wrapper to rfork, is pass in the > exit signal. rfork does have a flag to set an exit signal of SIGUSR1, but > it does not conveniently take a parameter to set it more flexibly. OTOH, > the only FreeBSD app I know of that actually sets an exit signal other > that the default SIGCHLD, is the linuxthreads port noted above. > > I'm not sure there is really a need for a "clone" syscall at this point, > but if you wanted it, you could just copy the linux_clone code in > linux_misc.c . You would have to decide if you want the flags parameter > to take the linux flags values, or FreeBSD flags (the emulator has > to take the linux values, obviously). > > My vote: don't bother with a syscall until there's a demonstrated need. > > II) clone in libc > ----------------- > Linux glibc has a clone call wrapper for the clone syscall, defined as: > > int clone (int (*fn) (void *arg), void *stack, int flags, void *arg) > > The stack and flags are passed directly to the clone syscall, and > the fn(arg) is the user function the cloned process should execute. > > Its easy enough to implement this in FreeBSD as a wrapper for rfork. > If you want to facilitate porting linux code, you would want the > flags argument to take linux flags, which would then be translated > into their FreeBSD counterparts before rfork is call. This is what > the code in the linuxthreads port does, and you are welcome to commit > it. > > The only issue here is whether people need to port linux code that > calls clone directly. As noted above, the only code I know of that > calls clone directly is WINE and linuxthreads. All the rest of the > code uses pthread_create, which only indirectly calls clone. > > My vote: I haven't seen the need, but if there is one, lets do it. > > III) libc rfork wrapper > ----------------------- > > It probably would be nice to have a libc rfork wrapper that grafts a > stack and a user function onto the rfork'd child process. But, it > should probably take FreeBSD flags, and there's no reason to > call it "clone". John Dyson's thr_fork is one such implementation. > Luoqi Chen posted another variation to either -hackers or -current > maybe 6-9 months ago. Matt Dillon just posted yet another variation. > Or, the linuxthreads port has a variation of the clone call that > has the same API as the linux clone call, but takes FreeBSD flags > (see clone.S). > > My vote: its worth doing, but not a top priority. The main issue > is to decide what interface would be most convenient. Its not a > top priority since the code already exists for those (rare) cases > where someone really needs it. And, lets not call it "clone". Let's call it "rfork() with one extra argument" instead then :) I don't see why this is a bad thing. Full backward compatibility is maintained, and it would be easy to implement. > > -- > Richard Seaman, Jr. email: dick@tar.com > 5182 N. Maple Lane phone: 414-367-5450 > Chenequa WI 53058 fax: 414-367-5852 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 22 15: 7:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from eterna.binary.net (eterna.binary.net [12.13.84.6]) by hub.freebsd.org (Postfix) with ESMTP id 66E68152B8 for ; Mon, 22 Mar 1999 15:07:04 -0800 (PST) (envelope-from nathan@rtfm.net) Received: from matrix.binary.net (nathan@matrix.binary.net [12.13.120.2]) by eterna.binary.net (8.9.1a/8.9.1) with ESMTP id RAA13415; Mon, 22 Mar 1999 17:06:45 -0600 (CST) Received: (from nathan@localhost) by matrix.binary.net (8.9.1a/8.9.1) id RAA26481; Mon, 22 Mar 1999 17:06:45 -0600 (CST) Date: Mon, 22 Mar 1999 18:06:45 -0500 From: Nathan Dorfman To: Dan Moschuk Cc: current@FreeBSD.ORG Subject: Re: aic Message-ID: <19990322180645.A24195@rtfm.net> References: <19990321202736.B50594@globalserve.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <19990321202736.B50594@globalserve.net>; from Dan Moschuk on Sun, Mar 21, 1999 at 08:27:36PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 21, 1999 at 08:27:36PM +0000, Dan Moschuk wrote: > > Any hope of the aic driver gracing -current anytime soon? I'm really itching > to port my burning software over. No one ever bothered to port the aic driver to the new CAM interface in 3.0 and 4.0. Since I know you're capable of it, I'm simply going to direct you to the appropriate mailing list (freebsd-scsi) and look away... ;) Otherwise, you're stuck with 2.2. It's not so bad, I'm running it on this laptop (since pccard doesn't work w/ -current or 3.1-R, I use 2.2.8 and PAO). > Cheers, > -- > Dan Moschuk (TFreak!dm@globalserve.net) > Senior Systems/Network Administrator > Globalserve Communications Inc., a Primus Canada Company > "If at first you don't succeed, redefine success" -- Nathan Dorfman The statements and opinions in my Unix Admin @ Frontline Communications public posts are mine, not FCC's. "The light at the end of the tunnel is the headlight of an approaching train." --/usr/games/fortune To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 22 22:37:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 75EBF1532B for ; Mon, 22 Mar 1999 22:37:35 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id RAA20664 for ; Tue, 23 Mar 1999 17:07:15 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id RAA57856 for FreeBSD-current@FreeBSD.ORG; Tue, 23 Mar 1999 17:07:13 +1030 (CST) Message-ID: <19990323170713.H442@lemis.com> Date: Tue, 23 Mar 1999 17:07:13 +1030 From: Greg Lehey To: FreeBSD current users Subject: Help needed with hangs associated with vfs locking Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A system I'm looking at continually runs into deadlocks when doing a 'make -j20 world'. This appears to happen only when the file system is mounted on a vinum volume, and it possibly also requires softupdates, though I haven't confirmed this yet. I initially thought that this was a vinum problem, and though I can't exclude the possibility, it's beginning to look less like it (since vinum doesn't perform this kind of locking). I currently suspect that vinum acts as a catalyst by issuing disk multiple I/O requests in a very short space of time. Typically, the hanging processes' stack looks like: pid proc addr uid ppid pgrp flag wchan stat comm wchan 65139 f3f6bd00 f3f6c000 0 0 556 004006 3 ld inode f0bb3e00 Check your .gdbinit, it contains a y command frame 0 at 0xf3f6dc10: ebp f3f6dc2c, eip 0xf0134141 : movb 0xfd(%ebx),%al frame 1 at 0xf3f6dc2c: ebp f3f6dc50, eip 0xf012dd23 : movl %eax,%esi frame 2 at 0xf3f6dc50: ebp f3f6dc74, eip 0xf012dfe5 : movl %eax,0xfffffffc(%ebp) frame 3 at 0xf3f6dc74: ebp f3f6dc98, eip 0xf015457d : leave frame 4 at 0xf3f6dc98: ebp f3f6dca4, eip 0xf01c8b35 : leave frame 5 at 0xf3f6dca4: ebp f3f6dccc, eip 0xf015d7dd : addl $0x4,%esp frame 6 at 0xf3f6dccc: ebp f3f6dcf0, eip 0xf01571a9 : movl %eax,%esi frame 7 at 0xf3f6dcf0: ebp f3f6dd3c, eip 0xf015300b : movl %eax,%ebx frame 8 at 0xf3f6dd3c: ebp f3f6dd48, eip 0xf01c8b35 : leave frame 9 at 0xf3f6dd48: ebp f3f6dd94, eip 0xf01557ad : movl %eax,0xffffffcc(%ebp) frame 10 at 0xf3f6dd94: ebp f3f6ddf0, eip 0xf0155182 : movl %eax,0xffffffc0(%ebp) frame 11 at 0xf3f6ddf0: ebp f3f6df54, eip 0xf012bef1 : movl %eax,0xfffffebc(%ebp) frame 12 at 0xf3f6df54: ebp f3f6dfa4, eip 0xf01f07ab : addl $0x8,%esp The lock manipulated by (debug)lockmgr shows: $1 = { lk_interlock = { lock_data = 0 }, lk_flags = 3146240, lk_sharecount = 1, lk_waitcount = 2, lk_exclusivecount = 0, lk_prio = 8, lk_wmesg = 0xf0216943 "inode", lk_timo = 0, lk_lockholder = -1, lk_filename = 0xf020fdfb "../../kern/vfs_subr.c", lk_lockername = 0xf020fa73 "vop_stdlock", lk_lineno = 1268 } The locker call was from vget(). The associated vnode shows that it's mounted on a vinum volume, which in this build was used for the /usr/obj hierarchy. In the example I'm showing here, the file was /usr/obj/usr/src/tmp/usr/libexec/elf/mld. I have lots more information available, but I don't want to put it all in here. If you think you recognize the problem, or if you have a suggestion about how to approach it, I'd be pleased to hear from you, either in this forum or privately. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 23 2:50:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 007FB14FF6 for ; Tue, 23 Mar 1999 02:50:30 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10POkq-0001ze-00; Tue, 23 Mar 1999 12:49:52 +0200 From: Sheldon Hearn To: "Jordan K. Hubbard" Cc: current@freebsd.org Subject: Re: /etc/rc.conf, take 46! In-reply-to: Your message of "Sun, 21 Mar 1999 18:06:41 PST." <39218.922068401@zippy.cdrom.com> Date: Tue, 23 Mar 1999 12:49:52 +0200 Message-ID: <7665.922186192@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 21 Mar 1999 18:06:41 PST, "Jordan K. Hubbard" wrote: > if [ -f /etc/defaults/rc.conf ]; then > . /etc/defaults/rc.conf > -elif [ -f /etc/rc.conf ]; then > - . /etc/rc.conf > + for i in ${rc_conf_files}; do > + if [ -f $i ]; then > + . $i > + fi > + done > fi Hi Jordan, What's the idea behind ignoring rc_conf_files just because we can't find /etc/defaults/rc.conf? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 23 2:53:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id B7DC9153C3 for ; Tue, 23 Mar 1999 02:52:58 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10POnH-000216-00; Tue, 23 Mar 1999 12:52:23 +0200 From: Sheldon Hearn To: "Jordan K. Hubbard" Cc: current@freebsd.org Subject: Re: /etc/rc.conf, take 46! In-reply-to: Your message of "Tue, 23 Mar 1999 12:49:52 +0200." <7665.922186192@axl.noc.iafrica.com> Date: Tue, 23 Mar 1999 12:52:23 +0200 Message-ID: <7755.922186343@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Mar 1999 12:49:52 +0200, Sheldon Hearn wrote: > What's the idea behind ignoring rc_conf_files just because we can't find > /etc/defaults/rc.conf? Please pretend I never said that. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 23 3: 2:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 88C4A14CCA for ; Tue, 23 Mar 1999 03:02:30 -0800 (PST) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id FAA11149; Tue, 23 Mar 1999 05:01:51 -0600 (CST) Date: Tue, 23 Mar 1999 05:01:51 -0600 From: "Matthew D. Fuller" To: Sheldon Hearn Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: /etc/rc.conf, take 46! Message-ID: <19990323050151.G17547@futuresouth.com> References: <39218.922068401@zippy.cdrom.com> <7665.922186192@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <7665.922186192@axl.noc.iafrica.com>; from Sheldon Hearn on Tue, Mar 23, 1999 at 12:49:52PM +0200 X-OS: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 23, 1999 at 12:49:52PM +0200, a little birdie told me that Sheldon Hearn remarked > On Sun, 21 Mar 1999 18:06:41 PST, "Jordan K. Hubbard" wrote: > > > if [ -f /etc/defaults/rc.conf ]; then > > . /etc/defaults/rc.conf > > -elif [ -f /etc/rc.conf ]; then > > - . /etc/rc.conf > > + for i in ${rc_conf_files}; do > > + if [ -f $i ]; then > > + . $i > > + fi > > + done > > fi > > Hi Jordan, > > What's the idea behind ignoring rc_conf_files just because we can't find > /etc/defaults/rc.conf? I have to jump in here and say 'Because that's where it's DEFINED'. Sorry, I had to stick my nose in somewhere ;) --- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | Matthew Fuller http://www.over-yonder.net/ | * fullermd@futuresouth.com fullermd@over-yonder.net * | UNIX Systems Administrator Specializing in FreeBSD | * FutureSouth Communications ISPHelp ISP Consulting * | "The only reason I'm burning my candle at both ends, | * is because I haven't figured out how to light the * | middle yet" | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 23 5: 3: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (Postfix) with ESMTP id 6A63014C2B for ; Tue, 23 Mar 1999 05:02:55 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id XAA07119 for ; Tue, 23 Mar 1999 23:33:43 +0930 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA16488; Tue, 23 Mar 1999 23:32:29 +0930 Date: Tue, 23 Mar 1999 23:32:28 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: current@freebsd.org Subject: Spontaneous reboots Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For about the past week I've been getting spontaneous reboots on my machine. As far as I can tell, there's no obvious common connection - most recently my box was under load at the time, but the time before that all I did was move the mouse (shades of Windows :-) and nothing else much was running. This does only seem to happen when I'm using the machine - after a few hours, a reboot is pretty much guaranteed (sounds like a resource leak of some kind to me). Beyond that, I don't know. My kernel and machine config haven't changed recently. Has anyone else been seeing this? What kind of information would help to narrow the problem down? Kris ----- The Feynman problem-solving algorithm: 1. Write down the problem 2. Think real hard 3. Write down the solution To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 23 6:34:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (Postfix) with ESMTP id 4BC9F14C87 for ; Tue, 23 Mar 1999 06:34:47 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.3/8.9.3/Kp) with ESMTP id OAA66051; Tue, 23 Mar 1999 14:34:04 GMT Message-ID: <36F7A65C.B438E07A@tdx.co.uk> Date: Tue, 23 Mar 1999 14:34:04 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway Cc: current@FreeBSD.ORG Subject: Re: Spontaneous reboots References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > > For about the past week I've been getting spontaneous reboots on my machine. > As far as I can tell, there's no obvious common connection - most recently my > box was under load at the time, but the time before that all I did was move > the mouse (shades of Windows :-) and nothing else much was running. > > This does only seem to happen when I'm using the machine - after a few hours, > a reboot is pretty much guaranteed (sounds like a resource leak of some kind > to me). Beyond that, I don't know. My kernel and machine config haven't > changed recently. > > Has anyone else been seeing this? What kind of information would help to > narrow the problem down? The sort of thing we're looking for is, Which version of FreeBSD (I'd assume something -current because you posted to the -current mailing list, but how current?), what hardware (i.e. CPU type [Intel/AMD/Cyrix]) etc. - how much memory, what types of hard drive (SCSI vs. IDE) etc. - if you have any 'weird' hardware in there? Also, you say "when I moved the mouse" - does that mean your machine lives in X-Windows all the time? - Does it crash when it's not running X etc? What type of video card does your machine have? The more detail you can provide (without going too OTT :-) - The more likely someone will be able to help :-) I have two boxes here tracking 4.0-current, and so far (looking for a nice piece of wood to touch), I've not seen any reboots on either for quite a long time (i.e>months) :) -Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 23 7:25:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail0.atl.bellsouth.net (mail0.atl.bellsouth.net [205.152.0.27]) by hub.freebsd.org (Postfix) with ESMTP id EA4691530B for ; Tue, 23 Mar 1999 07:25:33 -0800 (PST) (envelope-from wghicks@bellsouth.net) Received: from wghicks.bellsouth.net (host-209-214-70-39.atl.bellsouth.net [209.214.70.39]) by mail0.atl.bellsouth.net (8.8.8-spamdog/8.8.5) with ESMTP id KAA28906; Tue, 23 Mar 1999 10:24:46 -0500 (EST) Received: from localhost (wghicks@localhost [127.0.0.1]) by wghicks.bellsouth.net (8.9.2/8.9.2) with ESMTP id KAA06882; Tue, 23 Mar 1999 10:24:17 -0500 (EST) (envelope-from wghicks@wghicks.bellsouth.net) To: kkennawa@physics.adelaide.edu.au Cc: current@FreeBSD.ORG Subject: Re: Spontaneous reboots In-Reply-To: Your message of "Tue, 23 Mar 1999 23:32:28 +0930 (CST)" References: X-Mailer: Mew version 1.93 on XEmacs 20.4 (Emerald) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990323102417X.wghicks@wghicks.bellsouth.net> Date: Tue, 23 Mar 1999 10:24:17 -0500 From: W Gerald Hicks X-Dispatcher: imput version 980905(IM100) Lines: 39 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sounds like a NMI generated by memory parity errors or motherboard malfunction. Good Luck, Jerry Hicks wghicks@bellsouth.net From: Kris Kennaway Subject: Spontaneous reboots Date: Tue, 23 Mar 1999 23:32:28 +0930 (CST) > For about the past week I've been getting spontaneous reboots on my machine. > As far as I can tell, there's no obvious common connection - most recently my > box was under load at the time, but the time before that all I did was move > the mouse (shades of Windows :-) and nothing else much was running. > > This does only seem to happen when I'm using the machine - after a few hours, > a reboot is pretty much guaranteed (sounds like a resource leak of some kind > to me). Beyond that, I don't know. My kernel and machine config haven't > changed recently. > > Has anyone else been seeing this? What kind of information would help to > narrow the problem down? > > Kris > > ----- > The Feynman problem-solving algorithm: 1. Write down the problem > 2. Think real hard > 3. Write down the solution > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 23 7:31:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 3940A154A8 for ; Tue, 23 Mar 1999 07:31:11 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id AAA06957; Wed, 24 Mar 1999 00:30:59 +0900 (JST) Message-ID: <36F79AE1.1957DB6D@newsguy.com> Date: Tue, 23 Mar 1999 22:45:05 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Gus R Bourg Cc: current@FreeBSD.ORG Subject: Re: ELF Question References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gus R Bourg wrote: > > I have a machine running a snap from back on 19981126. Is there still a > problem moving from aout to elf. I remember a while back I had to on > another machine do something weird to get the bootloader working. Read /usr/src/UPDATING -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Someone's trying to hack into our server." "Wow... How flattering!" "I know. There must be some mistake." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 23 9:17:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id B802214C85 for ; Tue, 23 Mar 1999 09:17:50 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id JAA65429; Tue, 23 Mar 1999 09:16:24 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199903231716.JAA65429@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Cc: nick.hibma@jrc.it Subject: usb keyboard? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Mar 1999 09:16:24 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ls -ald /dev/kb* crw------- 1 root wheel 112, 0 Mar 23 23:29 /dev/kbd0 crw------- 1 root wheel 112, 1 Mar 23 23:29 /dev/kbd1 muadib# kbdcontrol -k /dev/kbd1 kbd1 ukbd0, type:generic (3) kbdcontrol: unable to set keyboard: Inappropriate ioctl for device Any clues as to how to switch from standard keyboard device to the usb keyboard? Tnks, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 23 10: 6:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 8BEB114EB0 for ; Tue, 23 Mar 1999 10:06:30 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id TAA25625 for FreeBSD-current@FreeBSD.ORG; Tue, 23 Mar 1999 19:05:59 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 938EF87B6; Tue, 23 Mar 1999 08:00:10 +0100 (CET) Date: Tue, 23 Mar 1999 08:00:10 +0100 From: Ollivier Robert To: FreeBSD current users Subject: Re: Help needed with hangs associated with vfs locking Message-ID: <19990323080010.A2391@keltia.freenix.fr> Mail-Followup-To: FreeBSD current users References: <19990323170713.H442@lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i In-Reply-To: <19990323170713.H442@lemis.com>; from Greg Lehey on Tue, Mar 23, 1999 at 05:07:13PM +1030 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5130 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Greg Lehey: > perform this kind of locking). I currently suspect that vinum acts as > a catalyst by issuing disk multiple I/O requests in a very short space > of time. I got two hanging processes too yesterday. rnews was unbatching news and I had a grep on my news log. syslogd was locked in "inode" as was "grep". I had to reboot. I don't have more data sorry, I don't have a serial console yet. > pid proc addr uid ppid pgrp flag wchan stat comm wchan > 65139 f3f6bd00 f3f6c000 0 0 556 004006 3 ld inode f0bb3e00 My current is unfortunately a bit old (see below). -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #70: Sat Feb 27 09:43:08 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 23 10:24:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 2D3751539A for ; Tue, 23 Mar 1999 10:24:11 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id KAA65718; Tue, 23 Mar 1999 10:22:45 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199903231822.KAA65718@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Cc: nick.hibma@jrc.it Subject: Re: usb keyboard? In-reply-to: Your message of "Tue, 23 Mar 1999 09:16:24 PST." <199903231716.JAA65429@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Mar 1999 10:22:45 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cool, I managed to get my usb board up and running. the problem was kbdcontrol or me 8) I try to switch keyboards "at" -> "usb" however I needed an at keboard to make the switch so I attached an at keyboard to my system and issue the silly command: kbdcontrol -k /dev/kbd1 The last time I tried to set the usb keyboard as the default the system crash hard perhaps this time around it will work. Enjoy, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 23 10:43:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from speed.rcc.on.ca (radio163.mipps.net [205.189.197.163]) by hub.freebsd.org (Postfix) with SMTP id 343DD152E8 for ; Tue, 23 Mar 1999 10:43:33 -0800 (PST) (envelope-from tr49986@rcc.on.ca) Received: from a35 ([207.164.233.96]) by speed.rcc.on.ca (8.6.12/8.6.9) with SMTP id PAA23596; Tue, 23 Mar 1999 15:00:00 -0500 Message-ID: <000f01be755c$8e12f280$60e9a4cf@a35.my.intranet> From: "RT" To: , "Chas" Subject: Re: /etc/rc.conf, take 46! Date: Mon, 22 Mar 1999 19:05:17 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I like it too... No code anywhere than needed. After all, if /etc/rc doesn't exist, everything's messed up anyway, so you mideswell make it more dependent upon that script. -----Original Message----- From: Chas To: paul@originative.co.uk Cc: rkw@dataplex.net ; current@FreeBSD.ORG Date: Monday, March 22, 1999 5:12 PM Subject: Re: /etc/rc.conf, take 46! >Now that sounz like a simple solution.:)) Paul... >> > >> > An alternate, and perhaps cleaner approach would be to always suck in >> > /etc/defaults/rc.conf and /etc/rc.conf. Then suck in those >> > files specified >> > in ${additional_rc_conf_files}. >> >> I still think we're chasing our tails with all this configuration stuff. >> >> Why can't /etc/rc load /etc/defaults/rc.conf followed by /etc/rc.conf (if >> present). Don't have anything in /etc/defaults.rc.conf except default >> variable settings. >> >> The local admin can do what the hell they want in /etc/rc.conf, including >> putting in a bit of script to load /etc/rc.conf.local >> /etc/rc.conf.flavour_of_month etc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 23 11:53:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 0451015469 for ; Tue, 23 Mar 1999 11:53:31 -0800 (PST) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it (va-139.skylink.it [194.177.113.139]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id UAA29586; Tue, 23 Mar 1999 20:51:55 +0100 Received: from localhost (localhost.plazza.it [127.0.0.1]) by heidi.plazza.it (8.8.8/8.8.5) with SMTP id VAA02198; Tue, 23 Mar 1999 21:04:27 +0100 (CET) Date: Tue, 23 Mar 1999 21:04:27 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: Amancio Hasty Cc: current@FreeBSD.ORG Subject: Re: usb keyboard? In-Reply-To: <199903231716.JAA65429@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Did you add options "KBD_INSTALL_CDEV" in your kernel config? Nick On Tue, 23 Mar 1999, Amancio Hasty wrote: > ls -ald /dev/kb* > crw------- 1 root wheel 112, 0 Mar 23 23:29 /dev/kbd0 > crw------- 1 root wheel 112, 1 Mar 23 23:29 /dev/kbd1 > > muadib# kbdcontrol -k /dev/kbd1 > kbd1 > ukbd0, type:generic (3) > kbdcontrol: unable to set keyboard: Inappropriate ioctl for device > > Any clues as to how to switch from standard keyboard device to the > usb keyboard? > > Tnks, > Amancio > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > -- e-Mail: hibma@skylink.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 23 12: 3:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id DC00914DD8 for ; Tue, 23 Mar 1999 12:03:35 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id MAA66147; Tue, 23 Mar 1999 12:02:06 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199903232002.MAA66147@rah.star-gate.com> To: Nick Hibma Cc: Amancio Hasty , current@FreeBSD.ORG, hasty@rah.star-gate.com Subject: Re: usb keyboard? In-reply-to: Your message of "Tue, 23 Mar 1999 21:04:27 +0100." Date: Tue, 23 Mar 1999 12:02:06 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, I have ""KBD_INSTALL_CDEV" in my kernel config file. Actually, my problem was that the default keyboard is the AT keyboard what I need is to have my default keyboard be the USB keyboard. Tnks, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 23 13: 2:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from zone.syracuse.net (zone.syracuse.net [209.2.141.6]) by hub.freebsd.org (Postfix) with ESMTP id 0C72714BEE for ; Tue, 23 Mar 1999 13:02:50 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by zone.syracuse.net (8.9.2/8.9.2) with ESMTP id VAA00645; Tue, 23 Mar 1999 21:02:12 GMT (envelope-from green@unixhelp.org) Date: Tue, 23 Mar 1999 21:02:12 +0000 (GMT) From: Brian Feldman X-Sender: green@zone.syracuse.net To: Karl Pielorz Cc: Kris Kennaway , current@FreeBSD.ORG Subject: Re: Spontaneous reboots In-Reply-To: <36F7A65C.B438E07A@tdx.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Mar 1999, Karl Pielorz wrote: > Kris Kennaway wrote: > > > > For about the past week I've been getting spontaneous reboots on my machine. > > As far as I can tell, there's no obvious common connection - most recently my > > box was under load at the time, but the time before that all I did was move > > the mouse (shades of Windows :-) and nothing else much was running. > > > > This does only seem to happen when I'm using the machine - after a few hours, > > a reboot is pretty much guaranteed (sounds like a resource leak of some kind > > to me). Beyond that, I don't know. My kernel and machine config haven't > > changed recently. > > > > Has anyone else been seeing this? What kind of information would help to > > narrow the problem down? > > The sort of thing we're looking for is, Which version of FreeBSD (I'd assume > something -current because you posted to the -current mailing list, but how > current?), what hardware (i.e. CPU type [Intel/AMD/Cyrix]) etc. - how much > memory, what types of hard drive (SCSI vs. IDE) etc. - if you have any 'weird' > hardware in there? > > Also, you say "when I moved the mouse" - does that mean your machine lives in > X-Windows all the time? - Does it crash when it's not running X etc? What type > of video card does your machine have? > > The more detail you can provide (without going too OTT :-) - The more likely > someone will be able to help :-) I have two boxes here tracking 4.0-current, > and so far (looking for a nice piece of wood to touch), I've not seen any > reboots on either for quite a long time (i.e>months) :) > > -Karl > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > He should proviide a full dmesg from bootverbose mode. One thing I've seen is that K6-2's in write allocated mode have big problems. Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 23 13:25:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id B3D7114D5E for ; Tue, 23 Mar 1999 13:25:20 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id HAA23790; Wed, 24 Mar 1999 07:55:00 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id HAA66991; Wed, 24 Mar 1999 07:54:57 +1030 (CST) Message-ID: <19990324075457.A425@lemis.com> Date: Wed, 24 Mar 1999 07:54:57 +1030 From: Greg Lehey To: Ollivier Robert , FreeBSD current users Subject: Re: Help needed with hangs associated with vfs locking References: <19990323170713.H442@lemis.com> <19990323080010.A2391@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990323080010.A2391@keltia.freenix.fr>; from Ollivier Robert on Tue, Mar 23, 1999 at 08:00:10AM +0100 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 23 March 1999 at 8:00:10 +0100, Ollivier Robert wrote: > According to Greg Lehey: >> perform this kind of locking). I currently suspect that vinum acts as >> a catalyst by issuing disk multiple I/O requests in a very short space >> of time. > > I got two hanging processes too yesterday. rnews was unbatching news and I > had a grep on my news log. syslogd was locked in "inode" as was "grep". I > had to reboot. I don't have more data sorry, I don't have a serial console > yet. If you can get a dump and let me look at it, it would help. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 23 16:33:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 452AD14DAD for ; Tue, 23 Mar 1999 16:33:53 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:Ww2d4rr/OG53LTx6HRHUiCd4Fg8niWCt@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id JAA10650; Wed, 24 Mar 1999 09:33:25 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id JAA16932; Wed, 24 Mar 1999 09:36:49 +0900 (JST) Message-Id: <199903240036.JAA16932@zodiac.mech.utsunomiya-u.ac.jp> To: Amancio Hasty Cc: current@freebsd.org, nick.hibma@jrc.it, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: usb keyboard? In-reply-to: Your message of "Tue, 23 Mar 1999 09:16:24 PST." <199903231716.JAA65429@rah.star-gate.com> References: <199903231716.JAA65429@rah.star-gate.com> Date: Wed, 24 Mar 1999 09:36:49 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ls -ald /dev/kb* >crw------- 1 root wheel 112, 0 Mar 23 23:29 /dev/kbd0 >crw------- 1 root wheel 112, 1 Mar 23 23:29 /dev/kbd1 > >muadib# kbdcontrol -k /dev/kbd1 >kbd1 > ukbd0, type:generic (3) >kbdcontrol: unable to set keyboard: Inappropriate ioctl for device > >Any clues as to how to switch from standard keyboard device to the >usb keyboard? You need to issue the kbdcontrol command from an vty. If you are running it from a serial or network terminal, redirect stdin as follows: kbdcontrol -k /dev/kbd1 < /dev/ttyv0 Any vty should work. Make also sure that "options KBD_INSTALL_CDEV" is in your kernel configuration file. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 23 16:38:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 1EA0314E59 for ; Tue, 23 Mar 1999 16:38:43 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:UEJFase4BZzrvze5yHSlls711HD8K+HX@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id JAA10718; Wed, 24 Mar 1999 09:38:19 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id JAA17027; Wed, 24 Mar 1999 09:41:44 +0900 (JST) Message-Id: <199903240041.JAA17027@zodiac.mech.utsunomiya-u.ac.jp> To: Amancio Hasty Cc: current@freebsd.org, nick.hibma@jrc.it, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: usb keyboard? In-reply-to: Your message of "Tue, 23 Mar 1999 10:22:45 PST." <199903231822.KAA65718@rah.star-gate.com> References: <199903231822.KAA65718@rah.star-gate.com> Date: Wed, 24 Mar 1999 09:41:43 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Cool, I managed to get my usb board up and running. the problem was >kbdcontrol or me 8) I try to switch keyboards "at" -> "usb" however I needed >an at keboard to make the switch so I attached an at keyboard to my system >and issue the silly command: >kbdcontrol -k /dev/kbd1 > >The last time I tried to set the usb keyboard as the default the system crash >hard perhaps this time around it will work. > > Enjoy, > Amancio Would send me the output from `dmesg' and describe the crash in more details? Do you have crash dump? Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 23 17:26:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from sorack.sparhawk.bc.ca (vic-53-0123.direct.ca [216.66.129.23]) by hub.freebsd.org (Postfix) with ESMTP id 8EF8014DB4 for ; Tue, 23 Mar 1999 17:26:38 -0800 (PST) (envelope-from sparhawk@sparhawk.bc.ca) Received: from sorack.sparhawk.bc.ca (localhost [127.0.0.1]) by sorack.sparhawk.bc.ca (8.9.3/8.9.3) with SMTP id RAA00376 for ; Tue, 23 Mar 1999 17:21:37 -0800 (PST) (envelope-from sparhawk@sparhawk.bc.ca) From: Sparhawk To: FreeBSD-current@FreeBSD.org Subject: sound on es1371 based sound Cards? Date: Tue, 23 Mar 1999 17:13:17 -0800 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99032317213700.00338@sorack.sparhawk.bc.ca> Content-Transfer-Encoding: 8bit X-KMail-Mark: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone gotten a sound card based on the Ensoniq es1371 chipset to work under FreeBSD, if so what Entries did you have to put in the kernel config file? The card I have is the Creative Ensoniq Audio PCI, on IO E400-E43F and at IRQ 10. Any help on this woudl be apreciated. Thanks Seamus -- Seamus Wassman http://www.sparhawk.bc.ca sparhawk@sparhawk.bc.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 23 18:41:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id EF77714C43 for ; Tue, 23 Mar 1999 18:41:12 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:Iy4FHNN6NwYsKj1UWIzCz5XtOepiKSPh@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id LAA11241; Wed, 24 Mar 1999 11:40:32 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id LAA18924; Wed, 24 Mar 1999 11:43:51 +0900 (JST) Message-Id: <199903240243.LAA18924@zodiac.mech.utsunomiya-u.ac.jp> To: Amancio Hasty Cc: Nick Hibma , current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: usb keyboard? In-reply-to: Your message of "Tue, 23 Mar 1999 12:02:06 PST." <199903232002.MAA66147@rah.star-gate.com> References: <199903232002.MAA66147@rah.star-gate.com> Date: Wed, 24 Mar 1999 11:43:50 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Yes, I have ""KBD_INSTALL_CDEV" in my kernel config file. > >Actually, my problem was that the default keyboard is the AT keyboard >what I need is to have my default keyboard be the USB keyboard. You want to use the USB keyboard as the only keyboard in the system, and want to get rid of the AT keyboard, right? Please try the following steps. I have not tested this configuration myself yet, but I expect it should work. 0. You said you have already done this, but I will write it for a record anyway... Make sure /dev/kbd* is present. If not go to /dev and ./MAKEDEV kbd0 kbd1 Also make sure options "KBD_INSTALL_CDEV" is included in your kernel configuration file. 1. Remove `atkbd0' from your kernel configuration file so that the AT keyboard won't be recognized. (Leave `atkbdc0' in, as it is used by the PS/2 mouse driver `psm'.) Then, you tell `syscons' to use the USB keyboard; this is necessary because the USB drivers have not been attached when syscons is being initialized, and syscons will not find the USB keyboard. Therefore, it will start without a keyboard and you have to explicitly tell syscons which keyboard to use. This can be done in one of the two ways. 2a. Explicitly run the following command as a part of start-up script (say, /etc/rc.i386). kbdcontrol -k /dev/kbd0 < /dev/ttyv0 > /dev/null Note that /dev/kbd0 is the USB keyboard as the AT keyboard will not be probed and attached. 2b. Specify a flag to `syscons' so that it will look for a keyboard. device sc0 at isa? tty flags 0x100 With this flag specified, `syscons' will periodically look for any available keyboard until it finds one. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 23 20: 4:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 913D315052 for ; Tue, 23 Mar 1999 20:04:30 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id UAA68013; Tue, 23 Mar 1999 20:02:57 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199903240402.UAA68013@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Kazutaka YOKOTA Cc: current@freebsd.org, nick.hibma@jrc.it Subject: Re: usb keyboard? In-reply-to: Your message of "Wed, 24 Mar 1999 09:36:49 +0900." <199903240036.JAA16932@zodiac.mech.utsunomiya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Mar 1999 20:02:56 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cool ! kbdcontrol -k /dev/kbd1 < /dev/ttyv0 Appears to work 8) Now I have to figure out how to add support for my mouse. Got no clue what protocol does it use . All I know is that is Macally USB mouse is going to be fun hunting for the mouse protocol 8) Enclosed is the output of dmesg: Enjoy, Amancio Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #5: Wed Mar 24 19:42:30 PST 1999 root@muadib.star-gate.com:/usr/src/sys/compile/CIOLOCO Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 451025177 Hz CPU: Pentium III (451.03-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x672 Stepping=2 Features=0x387f9ff,MMX,FXSR,> real memory = 134217728 (131072K bytes) avail memory = 127070208 (124092K bytes) Preloaded elf kernel "kernel" at 0xc0347000. Preloaded splash_image_data "/boot/matrix.bmp" at 0xc034709c. Preloaded elf module "vesa.ko" at 0xc03470ec. Preloaded elf module "splash_bmp.ko" at 0xc0347188. VESA: v0.20, 2560k memory, flags:0x731e0000, mode table:0xc0d78022 (50c000) VESA: NVidia module_register_init: module_register(splash_bmp, c03435dc, 0) error 19 Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x03 on pci0.1.0 chip2: rev 0x02 on pci0.7.0 ide_pci0: rev 0x01 on pci0.7.1 uhci0: rev 0x01 int d irq 10 on pci0.7.2 usb0: USB version 1.0, interrupting at 10 intpm0: rev 0x02 on pci0.7.3 intpm0: I/O mapped 5000 ALLOCED IRQ 0 intr IRQ 9 enabled revision 0 intsmb0: smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped 4000 bktr0: rev 0x11 int a irq 11 on pci0.15.0 bti2c0: iicbb0: on bti2c0 iicbus0: on iicbb0 master-only iicsmb0: on iicbus0 smbus1: on iicsmb0 smb1: on smbus1 iic0: on iicbus0 smbus2: on bti2c0 smb2: on smbus2 Hauppauge WinCast/TV, Philips NTSC tuner, dbx stereo. pn0: <82c168/82c169 PNIC 10/100BaseTX> rev 0x20 int a irq 11 on pci0.20.0 pn0: Ethernet address: 00:a0:cc:40:f0:5f pn0: autoneg complete, link status good (half-duplex, 10Mbps) Probing for devices on PCI bus 1: vga0: rev 0x04 int a irq 11 on pci1.0.0 Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x280 atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa kbd0 at atkbd0 psm0 not found sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 wd0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (atapi): , removable, accel, dma, iordis wdc0: ATAPI CD-ROMs not configured wdc1 not found at 0x170 ppc0 at 0x378 irq 7 on isa ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode plip0: on ppbus 0 ppi0: on ppbus 0 vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface usbd_match usb0: usbd_attach usbd_new_device bus=0xc0d7c000 depth=0 lowspeed=0 usbd_new_device: adding unit addr=1, rev=100, class=9, subclass=0, protocol=0, maxpacket=64, ls=0 usbd_new_device: new dev (addr 1), dev=0xc0d87e00, parent=0xc0d82c40 uhub0 at usb0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 usbd_set_config_index: (addr 1) attr=0x40, selfpowered=1, power=0, powerquirk=0 usbd_set_config_index: set config 1 usbd_set_config_index: setting new config 1 uhub0: 2 ports with 2 removable, self powered usbd_init_port: adding hub port=1 status=0x0301 change=0x0001 usbd_init_port: adding hub port=2 status=0x0301 change=0x0001 uhub_explore: status change hub=1 port=1 usbd_new_device bus=0xc0d7c000 depth=1 lowspeed=512 usbd_new_device: adding unit addr=2, rev=100, class=0, subclass=0, protocol=0, maxpacket=8, ls=1 usbd_new_device: new dev (addr 2), dev=0xc0d87b00, parent=0xc0d75be0 usbd_probe_and_attach: no device specific driver found usbd_set_config_index: (addr 2) attr=0x80, selfpowered=0, power=100, powerquirk=0 usbd_set_config_index: set config 1 usbd_set_config_index: setting new config 1 ums0 ums0: vendor 0x0618 product 0x0101, rev 1.00/0.14, addr 2, iclass 3/1 ums0: 6 buttons and Z dir. ums_attach: sc=0xc0d96400 ums_attach: X 8/8 ums_attach: Y 8/8 ums_attach: Z 24/8 ums_attach: B1 0/1 ums_attach: B2 1/1 ums_attach: B3 2/1 ums_attach: B4 3/1 ums_attach: B5 4/1 ums_attach: B6 5/1 ums_attach: size=4, id=0 uhub_explore: status change hub=1 port=2 usbd_new_device bus=0xc0d7c000 depth=1 lowspeed=512 usbd_new_device: adding unit addr=3, rev=100, class=0, subclass=0, protocol=0, maxpacket=8, ls=1 usbd_new_device: new dev (addr 3), dev=0xc0d87980, parent=0xc0d75be0 usbd_probe_and_attach: no device specific driver found usbd_set_config_index: (addr 3) attr=0xa0, selfpowered=0, power=100, powerquirk=0 usbd_set_config_index: set config 1 usbd_set_config_index: setting new config 1 ukbd0 ukbd0: Microsoft product 0x000b, rev 1.00/1.04, addr 3, iclass 3/1 ukbd:set_leds: state=0xc029b0b0 leds=0 kbd1 at ukbd0 changing root device to wd0s1a ffs_mountfs: superblock updated for soft updates ukbd:set_leds: state=0xc029b0b0 leds=1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 23 20:21: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id B3DA014BFC for ; Tue, 23 Mar 1999 20:21:03 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:BuQcwu+XHyZjg7UNtyO4KYNvOg8ca/zW@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id NAA11629; Wed, 24 Mar 1999 13:20:38 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id NAA21161; Wed, 24 Mar 1999 13:24:03 +0900 (JST) Message-Id: <199903240424.NAA21161@zodiac.mech.utsunomiya-u.ac.jp> To: Amancio Hasty Cc: current@freebsd.org, nick.hibma@jrc.it, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: usb keyboard? In-reply-to: Your message of "Tue, 23 Mar 1999 20:02:56 PST." <199903240402.UAA68013@rah.star-gate.com> References: <199903240402.UAA68013@rah.star-gate.com> Date: Wed, 24 Mar 1999 13:24:02 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Cool ! > > kbdcontrol -k /dev/kbd1 < /dev/ttyv0 > >Appears to work 8) > > >Now I have to figure out how to add support for my mouse. Got no clue what >protocol does it use . All I know is that is Macally USB mouse is going to be >fun hunting for the mouse protocol 8) No, you don't need to find out protocol :-) Run moused to see how it recognizes the USB mouse: moused -i all -p /dev/ums0 It will print some info. Then start the mouse daemon as: moused -p /dev/ums0 kbdcontrol -m on The mouse pointer is now available in the text console. In order to use the USB mouse in the X session, you tell the X server that the mouse is at /dev/sysmouse and its protocol type is "Auto" Device "/dev/sysmouse" Protocol "Auto" If you decide not to use the mouse daemon and let the X sever directly read from the USB mouse, you still tell the X server the mouse protocol type is "Auto". Device "/dev/ums0" Protocol "Auto" (If you are using XFree86 3.3.1 or earlier, the protocol type is "MouseSystems".) Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 23 20:33:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id C3F1814E1F for ; Tue, 23 Mar 1999 20:33:31 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id UAA68186; Tue, 23 Mar 1999 20:31:44 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199903240431.UAA68186@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Kazutaka YOKOTA Cc: current@freebsd.org, nick.hibma@jrc.it Subject: Re: usb keyboard? In-reply-to: Your message of "Wed, 24 Mar 1999 13:24:02 +0900." <199903240424.NAA21161@zodiac.mech.utsunomiya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Mar 1999 20:31:44 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, I owe you lots of kudos !! Did as you instructed: moused -p /dev/ums0 In my XF86Config file: Device "/dev/sysmouse" Protocol "Auto" One thing though: kbdcontrol appears not to have option : "-m on" So in summary I have my usb keyboard and usb mouse up and running and it works with X 8) Tnks! Amancio > > >Cool ! > > > > kbdcontrol -k /dev/kbd1 < /dev/ttyv0 > > > >Appears to work 8) > > > > > >Now I have to figure out how to add support for my mouse. Got no clue what > >protocol does it use . All I know is that is Macally USB mouse is going to be > >fun hunting for the mouse protocol 8) > > No, you don't need to find out protocol :-) > > Run moused to see how it recognizes the USB mouse: > > moused -i all -p /dev/ums0 > > It will print some info. Then start the mouse daemon as: > > moused -p /dev/ums0 > kbdcontrol -m on > > The mouse pointer is now available in the text console. In order to > use the USB mouse in the X session, you tell the X server that the > mouse is at /dev/sysmouse and its protocol type is "Auto" > > Device "/dev/sysmouse" > Protocol "Auto" > > If you decide not to use the mouse daemon and let the X sever directly > read from the USB mouse, you still tell the X server the mouse > protocol type is "Auto". > > Device "/dev/ums0" > Protocol "Auto" > > (If you are using XFree86 3.3.1 or earlier, the protocol type is > "MouseSystems".) > > Kazu > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 23 21:18:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 33E4C14E12 for ; Tue, 23 Mar 1999 21:18:37 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40374>; Wed, 24 Mar 1999 15:05:18 +1000 Date: Wed, 24 Mar 1999 15:18:08 +1000 From: Peter Jeremy Subject: Problems with ELF Emacs To: current@FreeBSD.ORG Message-Id: <99Mar24.150518est.40374@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running -current from a couple of weeks ago. I recently re-compiled XFree86 to ELF - which works, and re-compiled emacs-19.34b - which won't work with X11, though it does work inside an Xterm. My old aout emacs still works (with old aout libraries - the re-compiled aout libraries seem to be missing a symbol). When running as an X11 client, emacs opens the window and then nothing happens. Looking at a ktrace, it seems to be continuously sending GetInputFocus commands to the X-server, which are being correctly replied to (as far as I can tell). I haven't bumped into this problem with any other X clients. Has anyone else seen this, or have any ideas? Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 23 22: 2:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-35.ppp.wenet.net [206.15.85.35]) by hub.freebsd.org (Postfix) with ESMTP id D435E14EED for ; Tue, 23 Mar 1999 22:02:20 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id VAA01858; Tue, 23 Mar 1999 21:59:14 -0800 (PST) (envelope-from garbanzo@hooked.net) Date: Tue, 23 Mar 1999 21:59:14 -0800 (PST) From: Alex Zepeda To: Amancio Hasty Cc: Kazutaka YOKOTA , current@FreeBSD.ORG, nick.hibma@jrc.it Subject: Re: usb keyboard? In-Reply-To: <199903240431.UAA68186@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Mar 1999, Amancio Hasty wrote: > One thing though: > > kbdcontrol appears not to have option : "-m on" Should be vidcontrol -m on I think. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 23 22: 5:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id C8447153C7 for ; Tue, 23 Mar 1999 22:05:36 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id WAA68494; Tue, 23 Mar 1999 22:04:01 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199903240604.WAA68494@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Alex Zepeda Cc: Kazutaka YOKOTA , current@FreeBSD.ORG, nick.hibma@jrc.it Subject: Re: usb keyboard? In-reply-to: Your message of "Tue, 23 Mar 1999 21:59:14 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Mar 1999 22:04:01 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, 23 Mar 1999, Amancio Hasty wrote: > > > One thing though: > > > > kbdcontrol appears not to have option : "-m on" > > Should be vidcontrol -m on I think. > > - alex > Yes, it is . Kazutaka YOKOTA just mailed me the correction. I suggest someone should summarize and stick the USB setup information either on a web page or a README file. Best Regards, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 23 23:37:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id B57C714EFD for ; Tue, 23 Mar 1999 23:37:40 -0800 (PST) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it (va-175.skylink.it [194.177.113.175]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id IAA03739; Wed, 24 Mar 1999 08:36:04 +0100 Received: from localhost (localhost.plazza.it [127.0.0.1]) by heidi.plazza.it (8.8.8/8.8.5) with SMTP id JAA03500; Wed, 24 Mar 1999 09:35:16 +0100 (CET) Date: Wed, 24 Mar 1999 09:35:16 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: USB BSD list , FreeBSD current Mailing list Subject: Re: usb keyboard? (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for doing that :-) Send me the webpage and I'll stick on the back of www.etla.net/~n_hibma/usb/usb.pl If you want of course. Nick > Yes, it is . Kazutaka YOKOTA just mailed me the correction. I suggest someone > should > summarize and stick the USB setup information either on a web page or a > README file. > > Best Regards, > Amancio > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > -- e-Mail: hibma@skylink.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 24 2:23:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from quadrus.ru (unknown [195.133.77.43]) by hub.freebsd.org (Postfix) with ESMTP id 5DA751549E for ; Wed, 24 Mar 1999 02:23:21 -0800 (PST) (envelope-from blink@quadrus.ru) Received: from executive (deputy.quadrusm.ru [192.168.43.11]) by quadrus.ru (8.8.5/8.8.8) with SMTP id MAA12284 for ; Wed, 24 Mar 1999 12:37:29 +0300 (MSK) (envelope-from blink@quadrus.ru) Message-ID: <009601be75e0$2225f6b0$0b2ba8c0@executive.quadrusm.ru> From: "Inna V. Dotsenko" To: Subject: Date: Wed, 24 Mar 1999 13:21:50 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 24 2:26:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13]) by hub.freebsd.org (Postfix) with ESMTP id 97D9B14F61 for ; Wed, 24 Mar 1999 02:26:49 -0800 (PST) (envelope-from spud@i.am) Received: from john (RAS1-p20.hfa.netvision.net.il [62.0.145.20]) by alpha.netvision.net.il (8.9.3/8.8.6) with SMTP id MAA22290 for ; Wed, 24 Mar 1999 12:26:23 +0200 (IST) Message-ID: <000a01be75df$515f27e0$1491003e@john> From: "Tomer Weller" To: Subject: making world Date: Wed, 24 Mar 1999 12:15:52 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01BE75F0.0FAAB880" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.37 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.37 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0007_01BE75F0.0FAAB880 Content-Type: text/plain; charset="iso-8859-8" Content-Transfer-Encoding: quoted-printable i have a working 4.0-CURRENT snapshot and i've now cvsuped my src's, now = i just make a "make world" to update my system ?=20 ------=_NextPart_000_0007_01BE75F0.0FAAB880 Content-Type: text/html; charset="iso-8859-8" Content-Transfer-Encoding: quoted-printable
i have a working = 4.0-CURRENT snapshot=20 and i've now cvsuped my src's, now i just make a "make world" = to=20 update my system ?
------=_NextPart_000_0007_01BE75F0.0FAAB880-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 24 2:44:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from stephens.ml.org (cm2081634025.ponderosa.ispchannel.com [208.163.40.25]) by hub.freebsd.org (Postfix) with ESMTP id 7A71C1540C for ; Wed, 24 Mar 1999 02:44:11 -0800 (PST) (envelope-from tas@stephens.ml.org) Received: from stephens.ml.org (localhost [127.0.0.1]) by stephens.ml.org (8.9.2/8.9.2) with ESMTP id KAA09284; Wed, 24 Mar 1999 10:43:50 GMT (envelope-from tas@stephens.ml.org) Message-Id: <199903241043.KAA09284@stephens.ml.org> To: "Tomer Weller" Cc: freebsd-current@FreeBSD.ORG, Thomas Stephens From: Thomas Stephens Subject: Re: making world In-reply-to: Your message of "Wed, 24 Mar 1999 12:15:52 +0200." <000a01be75df$515f27e0$1491003e@john> Date: Wed, 24 Mar 1999 02:43:49 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Tomer Weller" wrote: > >i have a working 4.0-CURRENT snapshot and i've now cvsuped my src's, now >i just make a "make world" to update my system ? Unfortunately, there's a bit more to it than that. Take a look at the following URL: http://www.nothing-going-on.demon.co.uk/FreeBSD/make-world/make-world.html Thomas Stephens tas@stephens.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 24 3:22:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from quadrus.ru (unknown [195.133.77.43]) by hub.freebsd.org (Postfix) with ESMTP id F13A814D9A for ; Wed, 24 Mar 1999 03:22:14 -0800 (PST) (envelope-from blink@quadrus.ru) Received: from executive (deputy.quadrusm.ru [192.168.43.11]) by quadrus.ru (8.8.5/8.8.8) with SMTP id NAA12572 for ; Wed, 24 Mar 1999 13:36:27 +0300 (MSK) (envelope-from blink@quadrus.ru) Message-ID: <002801be75e8$5e68edf0$0b2ba8c0@executive.quadrusm.ru> From: "Inna V. Dotsenko" To: Subject: Date: Wed, 24 Mar 1999 14:20:48 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG auth c92316af subscribe freebsd-current blink@quadrus.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 24 14:11:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 6D16D14BE3; Wed, 24 Mar 1999 14:11:32 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.8.8/8.8.8) id VAA29865; Wed, 24 Mar 1999 21:34:35 GMT (envelope-from nik) Date: Wed, 24 Mar 1999 21:34:35 +0000 From: Nik Clayton To: doc@freebsd.org, current@freebsd.org Subject: LinuxDoc -> DocBook cutover Message-ID: <19990324213435.A21081@catkin.nothing-going-on.org> Reply-To: doc@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Organization: Nik at home, where there's nothing going on Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Folks, [ sent to -doc and -current, reply-to points back to -doc ] I'm reasonably happy with the state of the DocBook handbook now, and am about ready to do the cutover. This involves changes to the website and to "make release". I'm waiting for feedback on patches that make these changes from a few interested parties, and will then make the changes. Probably at around 20:00 GMT on Friday 26th March. There is one outstanding issue with the DocBook conversion that I am aware of; * Generating the PDF version does not work, due to an overflow in v1.33 of the DSSSL stylesheets that do the formatting. All other formats (Postscript, plain text, HTML, RTF) are generated correctly. This problem is fixed in v1.37 of the stylesheets, but that revision introduces a different problem that badly affects the formatting. I am collaborating with the stylesheet author on a fix. I do not consider this to be a showstopper. Any objections? N -- Bagel: The carbohydrate with the hole To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 24 16:56:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 93B9E14EA5; Wed, 24 Mar 1999 16:55:50 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id LAA29768; Thu, 25 Mar 1999 11:25:02 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id LAA47207; Thu, 25 Mar 1999 11:25:02 +1030 (CST) Message-ID: <19990325112502.U425@lemis.com> Date: Thu, 25 Mar 1999 11:25:02 +1030 From: Greg Lehey To: doc@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: LinuxDoc -> DocBook cutover References: <19990324213435.A21081@catkin.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990324213435.A21081@catkin.nothing-going-on.org>; from Nik Clayton on Wed, Mar 24, 1999 at 09:34:35PM +0000 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 24 March 1999 at 21:34:35 +0000, Nik Clayton wrote: > Folks, > > [ sent to -doc and -current, reply-to points back to -doc ] > > I'm reasonably happy with the state of the DocBook handbook now, and am > about ready to do the cutover. > > This involves changes to the website and to "make release". I'm waiting > for feedback on patches that make these changes from a few interested > parties, and will then make the changes. Probably at around 20:00 GMT on > Friday 26th March. > > There is one outstanding issue with the DocBook conversion that I am aware > of; > > * Generating the PDF version does not work, due to an overflow in v1.33 > of the DSSSL stylesheets that do the formatting. All other formats > (Postscript, plain text, HTML, RTF) are generated correctly. > > This problem is fixed in v1.37 of the stylesheets, but that revision > introduces a different problem that badly affects the formatting. > I am collaborating with the stylesheet author on a fix. > > I do not consider this to be a showstopper. > > Any objections? Go for it! Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 24 19:34:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipmma27.mate.polimi.it (ipmma27.mate.polimi.it [131.175.23.27]) by hub.freebsd.org (Postfix) with ESMTP id CEDB914E86 for ; Wed, 24 Mar 1999 19:34:45 -0800 (PST) (envelope-from ) Received: from primus (1Cust207.tnt3.binghamton.ny.da.uu.net [208.251.103.207]) by ipmma27.mate.polimi.it (8.8.4/8.8.5) with SMTP id EAA28852; Thu, 25 Mar 1999 04:32:00 +0100 Date: Thu, 25 Mar 1999 04:32:00 +0100 Message-Id: <199903250332.EAA28852@ipmma27.mate.polimi.it> To: 4you@usa.net Subject: ADV: 4000 Years of Design at Your Fingertips From: "" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----------------------------------------------------------------------- Note: We mail to people whom we feel are interested in what we have to offer and do not allow anyone else to use our list. Once in a while we'll notify you of web sites, products, services and promotions that could be of special interest to you. We respect your right to privacy. If you do not wish to receive these notices and prefer never to hear from us, simply click on the link provided and put REMOVE in the subject line mailto:info@target4u.com ----------------------------------------------------------------------- 4,000 YEARS OF DESIGN AT YOUR FINGERTIPS Dear Graphics Professional, Direct Imagination is pleased to offer: -Royalty free classic designs -Pattern art from all major cultures of the world throughout the ages -Award winning CD-ROMs that run on both MACs and PCs -High resolution scans and high quality Vector EPS drawings -Clip Art with a Pedigree + history lesson + high tech convenience + inspiration Log on to http://www.dimagin.com ~~~~~~~~~~~~~~~~~~~~~~ Call TOLL FREE (888) 793-8387 (9am-9pm)PST We have searched the world and throughout history to bring you the best in classic design motifs, textiles and graphics. Egypt, India, the Celts, Pompeii, Arabia, Victoriana, China and Japan, we have them all. Our CD-ROMs, based on high resolution scans, are beautiful reproductions of historic art portfolios. They include bitmaps, EPS drawings, the original text, and historical context. Runs on both MACs and PCs. Royalty free!! Our "Grammar of Ornament", from the 1856 Folio, has been nominated for the prestigious Computerworld Smithsonian award for excellence and Innovation and was a MacEddy finalist. It contains 2300 bitmaps from 20 cultures and 160 hand drawn EPS patterns. The best collection of world ornamentation available, The "Grammar of Ornament" has influenced designers from William Morris to Frank Lloyd Wright. Our "Father of Industrial Design, works with Christopher Dresser", was awarded 4 1/2 mice (MacUser). It contains 300 bitmaps and 160 EPS drawings as well as a wonderful survey of Dresser's life and works (long considered to be one of the "minor masters" of late 19th century design, he was also the first English designer to visit Japan). Dresser's designs range from Victorian to Art Deco and were a major influence on Louis Comfort Tiffany. Albert Racinet published one of the all time best collections of world costume. Our "China and Japan" cd reproduces his complete selection of Chinese and Japanese costume. It includes 120 EPS design motifs, high resolution scans of his brethtaking lithographs, and 100 photographs of the Utterbach collection of apparel. Also includes some of the original photographs, taken in the late 1800's, that Racinet used as a source material for his lithographs. For the 3D designer, we have the "DI3D" collection of 3D models and textures. Designed for Strata Studio Pro, it has 50 natural textures, 50 ornamental textures, and 50 useful shapes. Sorry for Mac's only (but it has a really cool browser built with MTropolis) If you are a diehard Fractal Design Expression user, we also have 100 of the Grammar's EPS patterns as Expression strokes. This is a really good deal. In the works, are the following: From Racinet; Oceania, Africa, the Celts and the Americas. From Verneuil; Etude de la Plante (killer art nouveau plant illustrations) To see pictures of the above, log on to: http://www.dimagin.com ~~~~~~~~~~~~~~~~~~~~~~ Call TOLL FREE in California (888) 793-8387 (9am-9pm)PST __________________________________________________________ This message complies with the proposed United States Federal requirements for commercial e-mail bill, Sec. 301 For additional info see: http://www.senate.gov?-murkowski/commercialemail/EmailAmendtext.html. Per section 301, Paragraph (a) (2) (C) of S. 1618, further transmissions to you by the sender of this e-mail may be stopped at no cost to you by sending a reply to this e-mail address with the word "REMOVE" in the subject line. Reply to info@target4u.com __________________________________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 24 21:31: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from psf.Pinyon.ORG (ip-17-089.prc.primenet.com [207.218.17.89]) by hub.freebsd.org (Postfix) with ESMTP id 523E614D76 for ; Wed, 24 Mar 1999 21:31:01 -0800 (PST) (envelope-from rcarter@psf.Pinyon.ORG) Received: from psf.Pinyon.ORG (localhost [127.0.0.1]) by psf.Pinyon.ORG (8.9.3/8.9.2) with ESMTP id WAA05533; Wed, 24 Mar 1999 22:27:32 -0700 (MST) (envelope-from rcarter@psf.Pinyon.ORG) Message-Id: <199903250527.WAA05533@psf.Pinyon.ORG> X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Jeremy Cc: current@FreeBSD.ORG Subject: Re: Problems with ELF Emacs In-reply-to: Your message of "Wed, 24 Mar 1999 15:18:08 +1000." <99Mar24.150518est.40374@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 24 Mar 1999 22:27:32 -0700 From: "Russell L. Carter" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG %I'm running -current from a couple of weeks ago. I recently re-compiled %XFree86 to ELF - which works, and re-compiled emacs-19.34b - which won't %work with X11, though it does work inside an Xterm. My old aout emacs %still works (with old aout libraries - the re-compiled aout libraries %seem to be missing a symbol). % %When running as an X11 client, emacs opens the window and then nothing %happens. Looking at a ktrace, it seems to be continuously sending %GetInputFocus commands to the X-server, which are being correctly %replied to (as far as I can tell). % %I haven't bumped into this problem with any other X clients. % %Has anyone else seen this, or have any ideas? Yes, and no. It happens for me only with an ssh1 forwarded xterm, with whatever the most recent emacs2 is. Checked, and fails with emacs19. Elf emacs works fine on a local xterm. Xemacs works fine. Everything else does too. At that point, I started exporting filesystems. Russell %Peter % % %To Unsubscribe: send mail to majordomo@FreeBSD.org %with "unsubscribe freebsd-current" in the body of the message % To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 24 22:37:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from yoshi.iq.org (yoshy.iq.org [203.4.184.224]) by hub.freebsd.org (Postfix) with ESMTP id 78AD614D49; Wed, 24 Mar 1999 22:37:49 -0800 (PST) (envelope-from proff@yoshi.iq.org) Received: (from proff@localhost) by yoshi.iq.org (8.8.8/8.8.8) id RAA23306; Thu, 25 Mar 1999 17:35:12 +1100 (EST) To: Fernando Schapachnik Cc: dv@dv.ru (Dmitry Valdov), freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: disk quota overriding References: <199903171150.IAA23361@ns1.sminter.com.ar> Cc: proff@iq.org From: Julian Assange Date: 25 Mar 1999 17:35:12 +1100 In-Reply-To: Fernando Schapachnik's message of "Wed, 17 Mar 1999 08:50:50 -0300 (GMT)" Message-ID: Lines: 7 User-Agent: Gnus/5.070066 (Pterodactyl Gnus v0.66) XEmacs/20.4 (Emerald) Mime-Version: 1.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Fernando Schapachnik writes: > Are you aware that, due to nature of hardlinks the only extra space is > same that for an empty file? Due to this, how many empty files do you No, it's actually 128 bytes less. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 25 3:38:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 227251533F for ; Thu, 25 Mar 1999 03:38:36 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10Q8Sj-000JUz-00 for current@freebsd.org; Thu, 25 Mar 1999 13:38:13 +0200 From: Sheldon Hearn To: current@freebsd.org Subject: Recent KVA increase allows maxusers>64 ? Date: Thu, 25 Mar 1999 13:38:09 +0200 Message-ID: <74934.922361889@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, I've gotten myself confused. Am I correct in thinking that dg's recent hike on KVA size allows for MAXUSERS > 64 without odd lock-ups? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 25 3:42: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13]) by hub.freebsd.org (Postfix) with ESMTP id 5298714D7E for ; Thu, 25 Mar 1999 03:41:59 -0800 (PST) (envelope-from spud@i.am) Received: from john (RAS3-p101.hfa.netvision.net.il [62.0.146.101]) by alpha.netvision.net.il (8.9.3/8.8.6) with SMTP id NAA05855 for ; Thu, 25 Mar 1999 13:41:37 +0200 (IST) Message-ID: <000901be76b2$f3f49020$6592003e@john> From: "Tomer Weller" To: "FreeBSD Current" Subject: sio, dca Date: Thu, 25 Mar 1999 13:30:55 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0006_01BE76C3.B60DA380" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.37 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.37 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0006_01BE76C3.B60DA380 Content-Type: text/plain; charset="iso-8859-8" Content-Transfer-Encoding: quoted-printable i have problems with sio and i read in the man something about dca(4), = is it a replacement ? does it work well ? is it included with = 4.0-CURRENT ? please reply ------=_NextPart_000_0006_01BE76C3.B60DA380 Content-Type: text/html; charset="iso-8859-8" Content-Transfer-Encoding: quoted-printable
i have problems with sio and i read in = the man=20 something about dca(4), is it a replacement ? does it work well ? is it = included=20 with 4.0-CURRENT ? please reply
------=_NextPart_000_0006_01BE76C3.B60DA380-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 25 4:25:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 56AF115019 for ; Thu, 25 Mar 1999 04:25:19 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10Q9Ba-0002Mh-00; Thu, 25 Mar 1999 14:24:34 +0200 From: Sheldon Hearn To: Blaz Zupan Cc: freebsd-current@freebsd.org Subject: Re: Postfix In-reply-to: Your message of "Sun, 14 Mar 1999 17:22:42 +0100." Date: Thu, 25 Mar 1999 14:24:34 +0200 Message-ID: <9093.922364674@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 14 Mar 1999 17:22:42 +0100, Blaz Zupan wrote: > We don't even have a Postfix port. Has anybody created a port or should I > go ahead and have a look at it? Hi Blaz, Have a look at the PR database, specifically at ports/10710. I haven't checked it out myself. Perhaps you'd like to try it out and send feedback to the freebsd-ports mailing list, which is a much more appropriate list through which to address this sort of issue. http://www.freebsd.org/cgi/query-pr.cgi?pr=10710 Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 25 6:17:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by hub.freebsd.org (Postfix) with ESMTP id AEB5314E2F for ; Thu, 25 Mar 1999 06:17:34 -0800 (PST) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.9.3/8.8.8) with SMTP id WAA14372; Thu, 25 Mar 1999 22:17:04 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id WAA16592; Thu, 25 Mar 1999 22:17:04 +0800 Message-Id: <199903251417.WAA16592@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Cc: wpaul@ctr.columbia.edu Subject: RealTek driver woes Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 25 Mar 1999 22:17:04 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running a RealTek ethernet card in a 486dx4-100 machine and am having some problems. Firstly, doing an ls on a nfs mounted directory exported from the RealTek machine hangs. According to tcpdump it is receiving the readdir packets. Secondly, it will hange solidly when acting as the receiver (haven't tried it as the sender) running the netpipe tests (NPtcp -s -r receiving, the sender runs NP -t -h host_rl -s) - no DDB, just a solid hang. An ISA SMC card in the same machine is fine. I've tried it with RL_USEIOSPACE defined and undefined. This is running a very current system, with the id string $Id: if_rl.c,v 1.12 1999/02/23 15:38:25 wpaul Exp$ Here's the dmesg output. Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #1: Thu Mar 25 21:37:03 WST 1999 toor@bloop.craftncomp.com:/data/src/sys/compile/bleep Timecounter "i8254" frequency 1193182 Hz CPU: AMD Enhanced Am486DX4 Write-Through (486-class CPU) Origin = "AuthenticAMD" Id = 0x484 Stepping=4 Features=0x1 real memory = 16777216 (16384K bytes) avail memory = 13750272 (13428K bytes) Preloaded elf kernel "kernel" at 0xc02c3000. Preloaded elf module "linux.ko" at 0xc02c309c. Probing for devices on PCI bus 0: chip0: rev 0x00 on pci0.0.0 rl0: rev 0x10 int a irq 9 on pci0.4.0 rl0: Ethernet address: 00:00:e8:53:a2:3e rl0: autoneg complete, link status good (half-duplex, 10Mbps) Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x280-0x29f irq 10 maddr 0xd8000 msize 16384 on isa ed0: address 00:00:c0:d2:b2:72, type SMC8216T (16 bit) atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa ppc0 at 0x378 irq 7 on isa ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: on ppbus 0 lpt0: Interrupt-driven port sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A pca0 on motherboard pca0: PC speaker audio driver ata0 at 0x1f0-0x1f7 irq 14 on isa fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fd0: 1.44MB 3.5in vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface IP packet filtering initialized, divert enabled, rule-based forwarding disabled, logging disabled ad0: ATA-4 disk at ata0 as master ad0: 4103MB (8404830 sectors), 8894 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue changing root device to ad0s2a Stephen -- The views expressed above are not those of PGS Tensor. "People often think of research as a form of development -- that it's about doing exactly what you planned, doing it on time, and doing it with resources that you said you'd use. But if you're going to do that, you have to know what you are doing, and if you know what you are doing, it isn't really research." --Dave Liddle, The New Yorker, Feb. 23/Mar.2, 1998, p 84 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 25 8:35:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from server.amis.net (server.amis.net [212.18.32.10]) by hub.freebsd.org (Postfix) with ESMTP id 837BB14EF6 for ; Thu, 25 Mar 1999 08:35:40 -0800 (PST) (envelope-from blaz@gold.amis.net) Received: (from uucp@localhost) by server.amis.net (8.8.8/8.8.8) with UUCP id RAA13795; Thu, 25 Mar 1999 17:37:10 +0100 (CET) Received: by gold.amis.net (Postfix, from userid 1000) id 7FACC2E; Thu, 25 Mar 1999 17:30:18 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by gold.amis.net (Postfix) with ESMTP id 680631E07; Thu, 25 Mar 1999 17:30:18 +0100 (CET) Date: Thu, 25 Mar 1999 17:30:18 +0100 (CET) From: Blaz Zupan To: Sheldon Hearn Cc: freebsd-current@FreeBSD.ORG Subject: Re: Postfix In-Reply-To: <9093.922364674@axl.noc.iafrica.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Have a look at the PR database, specifically at ports/10710. I haven't > checked it out myself. Perhaps you'd like to try it out and send > feedback to the freebsd-ports mailing list, which is a much more > appropriate list through which to address this sort of issue. If you had taken at look at the PR yourself, you'd notice that it was ME, who submited that PR :) Blaz Zupan, blaz@medinet.si, http://home.amis.net/blaz Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 25 8:41:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from bolero-x.rahul.net (bolero.rahul.net [192.160.13.1]) by hub.freebsd.org (Postfix) with SMTP id 015B115418 for ; Thu, 25 Mar 1999 08:41:42 -0800 (PST) (envelope-from dhesi@rahul.net) Received: from q.bolero.rahul.net (bolero.rahul.net) by bolero-x.rahul.net with SMTP id AA07426 (5.67b8/IDA-1.5 for ); Thu, 25 Mar 1999 08:41:23 -0800 Message-Id: <199903251641.AA07426@bolero-x.rahul.net> Received: (qmail 7422 invoked from network); 25 Mar 1999 16:41:22 -0000 Received: from waltz.rahul.net (192.160.13.9) by bolero.rahul.net with SMTP; 25 Mar 1999 16:41:22 -0000 To: freebsd-current@freebsd.org Subject: rc.conf issues: host identity vs host config Date: Thu, 25 Mar 1999 08:41:22 -0800 From: Rahul Dhesi Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The current rc.conf system doesn't seem to allow for separating out host identity from host configuration. As a result I'm not able to create a site-wide rc.conf file and rdist it to multiple machines, configured identically except for having distinct own host names. I think some very basic information identifying a host should be kept in its own place: host name and ip address for each network interface And I like the way SunOS does it: The file hostname. contains the machine's host name, where is the name of the network interface. E.g., if the only network interface is le0, the file hostname.le0 contains the host name. With multiple network interfaces you would have a distinct hostname. file for each one. Now you can rdist /etc/hosts containing all host names and IP addresses. At boot time we get the host name from hostname., look up the host name in /etc/hosts, and get our IP address. And non-default netmasks are listed in /etc/netmasks, which can also be propagated via rdist. To reassign IP addresses, simply rdist a new copy of /etc/hosts and reboot all machines. Rahul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 25 9:22:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id CAEF914BDB for ; Thu, 25 Mar 1999 09:22:23 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10QDpF-0006lZ-00; Thu, 25 Mar 1999 19:21:49 +0200 From: Sheldon Hearn To: Blaz Zupan Cc: freebsd-current@FreeBSD.ORG Subject: Re: Postfix In-reply-to: Your message of "Thu, 25 Mar 1999 17:30:18 +0100." Date: Thu, 25 Mar 1999 19:21:48 +0200 Message-ID: <26012.922382508@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 25 Mar 1999 17:30:18 +0100, Blaz Zupan wrote: > If you had taken at look at the PR yourself, you'd notice that it was ME, > who submited that PR :) I did take a look at it, that's how I know about it. You don't seriously expect me to notice the name of each originator for each PR I look at, do you? :-) Anyway, this is going to get silly soon. Everyone knows about the PR now, so it's really just a case of someone spending time on a commit. I'll bet you a noddy badge that it won't be jmb. ;-) Later, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 25 9:28:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 99ACD1526B for ; Thu, 25 Mar 1999 09:28:32 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10QDv1-00095O-00; Thu, 25 Mar 1999 19:27:47 +0200 From: Sheldon Hearn To: Rahul Dhesi Cc: freebsd-current@freebsd.org Subject: Re: rc.conf issues: host identity vs host config In-reply-to: Your message of "Thu, 25 Mar 1999 08:41:22 PST." <199903251641.AA07426@bolero-x.rahul.net> Date: Thu, 25 Mar 1999 19:27:47 +0200 Message-ID: <34929.922382867@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 25 Mar 1999 08:41:22 PST, Rahul Dhesi wrote: > The current rc.conf system doesn't seem to allow for separating out host > identity from host configuration. Use /etc/rc.conf for host configuration and /etc/rc.conf.local for host identity. Or whatever. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 25 10:16: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 623B315027 for ; Thu, 25 Mar 1999 10:15:51 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from scientia.demon.co.uk (ident=ben) by scientia.demon.co.uk with local (Exim 2.12 #4) id 10QEfA-00005t-00 for current@FreeBSD.ORG; Thu, 25 Mar 1999 18:15:28 +0000 (envelope-from ben@scientia.demon.co.uk) Date: Thu, 25 Mar 1999 18:15:28 +0000 From: Ben Smithurst To: current@FreeBSD.ORG Subject: Re: Spontaneous reboots Message-ID: <19990325181528.A310@scientia.demon.co.uk> References: <36F7A65C.B438E07A@tdx.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > Has anyone else been seeing this? What kind of information would help to > narrow the problem down? This has happened a few times on my -stable box, though not very often. It just happened a few minutes ago, I wasn't doing anything on the machine, I wasn't even logged in. No core dump or anything. :-( I'd think nothing of it on a -current box, but it seems a bit worrying that this sort of thing happens on a supposedly "stable" version. Mind you, it could be a hardware problem I suppose. Karl Pielorz wrote: > The sort of thing we're looking for is, Which version of FreeBSD > (I'd assume something -current because you posted to the -current > mailing list, but how current?), what hardware (i.e. CPU type > [Intel/AMD/Cyrix]) etc. - how much memory, what types of hard drive > (SCSI vs. IDE) etc. - if you have any 'weird' hardware in there? FreeBSD 3.1-STABLE, Cyrix 6x86 133MHz, 48MB RAM. I don't think I've got any hardware I'd class as weird. Disk info, $ mount /dev/wd0s2a on / (local, noatime, writes: sync 5 async 17) /dev/wd0s3c on /home (local, soft-updates, writes: sync 2 async 61) /dev/wd2s1c on /tmp (local, soft-updates, writes: sync 2 async 31) /dev/wd2s2e on /usr (local, soft-updates, writes: sync 2 async 86) /dev/wd2s3e on /var (local, nosuid, soft-updates, writes: sync 318 async 470) procfs on /proc (local) $ swapinfo Device 1K-blocks Used Avail Capacity Type /dev/wd2s4b 160650 0 160522 0% Interleaved I'm not sure how recent, the machine had been up for nearly 22 days, and I think I rebuilt the world soon before that, so it's as of around the beginning of March. Brian Feldman wrote: > He should proviide a full dmesg from bootverbose mode. OK, I wonder if anyone can spot the problem in this (if indeed there is something I've broken)... Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.1-STABLE #104: Tue Mar 2 18:29:08 GMT 1999 ben@scientia.demon.co.uk:/usr/src/sys/compile/SCIENTIA Calibrating clock(s) ... i8254 clock: 1193483 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CPU: Cyrix 6x86 (486-class CPU) Origin = "CyrixInstead" DIR=0x2231 Stepping=2 Revision=2 real memory = 50331648 (49152K bytes) Physical memory chunk(s): 0x00001000 - 0x0009ffff, 651264 bytes (159 pages) 0x00200000 - 0x02ffdfff, 48226304 bytes (11774 pages) avail memory = 47013888 (45912K bytes) Found BIOS32 Service Directory header at 0xf00fad20 Entry = 0xfb1a0 (0xf00fb1a0) Rev = 0 Len = 1 PCI BIOS entry at 0xb1d0 Other BIOS signatures found: ACPI: 00000000 $PnP: 000fbf50 pci_open(1): mode 1 addr port (0x0cf8) is 0x8000005c pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=70308086) Probing for devices on PCI bus 0: found-> vendor=0x8086, dev=0x7030, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 chip0: rev 0x02 on pci0.0.0 PCI Concurrency: enabled Cache: 256K pipelined-burst secondary; L1 enabled DRAM: no memory hole, 66 MHz refresh Read burst timing: x-2-2-2/x-3-3-3 Write burst timing: x-3-3-3 RAS-CAS delay: 3 clocks found-> vendor=0x8086, dev=0x7000, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 chip1: rev 0x01 on pci0.7.0 I/O Recovery Timing: 8-bit 2 clocks, 16-bit 1 clocks Extended BIOS: disabled Lower BIOS: disabled Coprocessor IRQ13: enabled Mouse IRQ12: disabled Interrupt Routing: A: disabled, B: disabled, C: IRQ11, D: disabled MB0: IRQ15, MB1: found-> vendor=0x8086, dev=0x7010, revid=0x00 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 4, range 32, base 0000f000, size 4 ide_pci0: rev 0x00 on pci0.7.1 intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: primary master fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: primary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 0 status: 04 from port: 0000f002 intel_piix_status: secondary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: secondary master fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled intel_piix_status: secondary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: secondary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 1 status: 04 from port: 0000f00a found-> vendor=0x5333, dev=0x8811, revid=0x54 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[0]: type 1, range 32, base e0000000, size 26 vga0: rev 0x54 int a irq 11 on pci0.10.0 Probing for devices on the ISA bus: atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa sc0 on isa sc0: fb0 kbd0 sc0: VGA color <8 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa kbd0: atkbd0, AT 101/102 (2), config:0x10000, flags:0x3d0000 sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio2: irq maps: 0x1 0x9 0x1 0x1 sio2 at 0x3e8-0x3ef irq 3 on isa sio2: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): , LBA, 32-bit, multi-block-16 wd0: 1628MB (3335472 sectors), 827 cyls, 64 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0003, dmamword = 0407, apio = 0003, udma = 0000 wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (wd2): , LBA, 32-bit, multi-block-16 wd2: 4892MB (10018890 sectors), 623 cyls, 255 heads, 63 S/T, 512 B/S wd2: ATA INQUIRE valid = 0007, dmamword = 0407, apio = 0003, udma = 0007 wdc1: unit 1 (atapi): , removable, dma, iordy acd0: drive speed 1375KB/sec, 86KB cache acd0: supported read types: CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked npx0 flags 0x1 on motherboard npx0: INT 16 interface vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xf00b8000 size:32k gran:32k, buf:0x0 size:0k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff imasks: bio c008c040, tty c003001a, net c0060000 BIOS Geometries: 0:03393f3f 0..825=826 cylinders, 0..63=64 heads, 1..63=63 sectors 1:026dfe3f 0..621=622 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. IP packet filtering initialized, divert disabled, rule-based forwarding disabled, logging limited to 5000 packets/entry bpf: tun0 attached bpf: lo0 attached Considering FFS root f/s. changing root device to wd0s2a wd0s1: type 0x6, start 63, end = 2088575, size 2088513 : OK wd0s2: type 0xa5, start 2088576, end = 2153087, size 64512 : OK wd0s3: type 0xa5, start 2153088, end = 3334463, size 1181376 : OK wd2s1: type 0xa5, start 63, end = 289169, size 289107 : OK wd2s2: type 0xa5, start 289170, end = 6554519, size 6265350 : OK wd2s3: type 0xa5, start 6554520, end = 9687194, size 3132675 : OK wd2s4: type 0xa5, start 9687195, end = 10008494, size 321300 : OK ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates splash: image decoder found: green_saver -- Ben Smithurst ben@scientia.demon.co.uk send a blank message to ben+pgp@scientia.demon.co.uk for PGP key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 25 10:34:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 280DC14F19 for ; Thu, 25 Mar 1999 10:34:12 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id TAA18390; Thu, 25 Mar 1999 19:33:48 +0100 (CET) (envelope-from des) To: Peter Jeremy Cc: current@FreeBSD.ORG Subject: Re: Problems with ELF Emacs References: <99Mar24.150518est.40374@border.alcanet.com.au> From: Dag-Erling Smorgrav Date: 25 Mar 1999 19:33:47 +0100 In-Reply-To: Peter Jeremy's message of "Wed, 24 Mar 1999 15:18:08 +1000" Message-ID: Lines: 13 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Jeremy writes: > I'm running -current from a couple of weeks ago. I recently re-compiled > XFree86 to ELF - which works, and re-compiled emacs-19.34b - which won't > work with X11, though it does work inside an Xterm. My old aout emacs > still works (with old aout libraries - the re-compiled aout libraries > seem to be missing a symbol). I run an Elf build of Emacs 19.34b daily on a completely Elf, very up-to-date 4.0-CURRENT box with Elf XFree86 3.3.3.1. No trouble at all. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 25 10:44:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 1FABC152E4 for ; Thu, 25 Mar 1999 10:44:26 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id KAA04454; Thu, 25 Mar 1999 10:44:06 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id KAA03085; Thu, 25 Mar 1999 10:44:06 -0800 (PST) (envelope-from jdp@polstra.com) Date: Thu, 25 Mar 1999 10:44:06 -0800 (PST) Message-Id: <199903251844.KAA03085@vashon.polstra.com> To: dg@root.com Subject: Re: latest -current doesn't execute BSDI-binary bladeenc In-Reply-To: <199903170258.SAA01200@implode.root.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199903170258.SAA01200@implode.root.com>, David Greenman wrote: > A much better solution would be for someone to spend the time to > implement the needed VM frobbing of modifying, at BSDI binary exec-time, > the ps_strings address constant in the binary's crt0 that is causing the > problem. Is that the only issue as far as the kernel is concerned? If so, there's an easy solution. If %ebx is nonzero on entry to a BSD/OS executable, it is taken to be the ps_strings constant. Otherwise a hard-coded value is used. So all we have to do is arrange for %ebx to have the right value on entry to the program. It looks easy to fix. Add a new member to struct image_params for the ps_strings value, and set it in the various image activators. It should be "PS_STRINGS" (from ) for a BSD/OS binary (a_midmag == 0314), and 0 for all others. Then in kern_exec.c:execve(), pass the value to setregs() as a new parameter. Stuff it into %ebx in i386/machdep.c:setregs(), and ignore it for the other architectures. That should do it. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 25 10:58:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from icicle.winternet.com (icicle.winternet.com [198.174.169.13]) by hub.freebsd.org (Postfix) with ESMTP id B40541503A for ; Thu, 25 Mar 1999 10:58:13 -0800 (PST) (envelope-from nrahlstr@mail.winternet.com) Received: (from adm@localhost) by icicle.winternet.com (8.8.8/8.8.8) id MAA21743; Thu, 25 Mar 1999 12:57:01 -0600 (CST) Received: from tundra.winternet.com(198.174.169.11) by icicle.winternet.com via smap (V2.0) id xma021723; Thu, 25 Mar 99 12:56:47 -0600 Received: (from nrahlstr@localhost) by tundra.winternet.com (8.8.7/8.8.4) id MAA00547; Thu, 25 Mar 1999 12:56:47 -0600 (CST) Message-ID: <19990325125646.A484@winternet.com> Date: Thu, 25 Mar 1999 12:56:46 -0600 From: Nathan Ahlstrom To: Ben Smithurst , current@FreeBSD.ORG Subject: Re: Spontaneous reboots References: <36F7A65C.B438E07A@tdx.co.uk> <19990325181528.A310@scientia.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990325181528.A310@scientia.demon.co.uk>; from Ben Smithurst on Thu, Mar 25, 1999 at 06:15:28PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There was another report of a similar problem on -hackers. Removing the 'pseudo-device splash' seemed to fix things. You might also try the patches in this thread. http://www.freebsd.org/cgi/getmsg.cgi?fetch=715663+0+archive/1999/freebsd-hackers/19990307.freebsd-hackers Nathan Ben Smithurst wrote: > Kris Kennaway wrote: > > > Has anyone else been seeing this? What kind of information would help to > > narrow the problem down? > > This has happened a few times on my -stable box, though not very > often. It just happened a few minutes ago, I wasn't doing anything on > the machine, I wasn't even logged in. No core dump or anything. :-( I'd > think nothing of it on a -current box, but it seems a bit worrying that > this sort of thing happens on a supposedly "stable" version. Mind you, > it could be a hardware problem I suppose. > > Karl Pielorz wrote: > > > The sort of thing we're looking for is, Which version of FreeBSD > > (I'd assume something -current because you posted to the -current > > mailing list, but how current?), what hardware (i.e. CPU type > > [Intel/AMD/Cyrix]) etc. - how much memory, what types of hard drive > > (SCSI vs. IDE) etc. - if you have any 'weird' hardware in there? > > FreeBSD 3.1-STABLE, Cyrix 6x86 133MHz, 48MB RAM. I don't think I've got > any hardware I'd class as weird. Disk info, > > $ mount > /dev/wd0s2a on / (local, noatime, writes: sync 5 async 17) > /dev/wd0s3c on /home (local, soft-updates, writes: sync 2 async 61) > /dev/wd2s1c on /tmp (local, soft-updates, writes: sync 2 async 31) > /dev/wd2s2e on /usr (local, soft-updates, writes: sync 2 async 86) > /dev/wd2s3e on /var (local, nosuid, soft-updates, writes: sync 318 async 470) > procfs on /proc (local) > $ swapinfo > Device 1K-blocks Used Avail Capacity Type > /dev/wd2s4b 160650 0 160522 0% Interleaved > > I'm not sure how recent, the machine had been up for nearly 22 days, and > I think I rebuilt the world soon before that, so it's as of around the > beginning of March. > > Brian Feldman wrote: > > > He should proviide a full dmesg from bootverbose mode. > > OK, I wonder if anyone can spot the problem in this (if indeed there is > something I've broken)... > > Copyright (c) 1992-1999 FreeBSD Inc. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 3.1-STABLE #104: Tue Mar 2 18:29:08 GMT 1999 > ben@scientia.demon.co.uk:/usr/src/sys/compile/SCIENTIA > Calibrating clock(s) ... i8254 clock: 1193483 Hz > CLK_USE_I8254_CALIBRATION not specified - using default frequency > Timecounter "i8254" frequency 1193182 Hz > CPU: Cyrix 6x86 (486-class CPU) > Origin = "CyrixInstead" DIR=0x2231 Stepping=2 Revision=2 > real memory = 50331648 (49152K bytes) > Physical memory chunk(s): > 0x00001000 - 0x0009ffff, 651264 bytes (159 pages) > 0x00200000 - 0x02ffdfff, 48226304 bytes (11774 pages) > avail memory = 47013888 (45912K bytes) > Found BIOS32 Service Directory header at 0xf00fad20 > Entry = 0xfb1a0 (0xf00fb1a0) Rev = 0 Len = 1 > PCI BIOS entry at 0xb1d0 > Other BIOS signatures found: > ACPI: 00000000 > $PnP: 000fbf50 > pci_open(1): mode 1 addr port (0x0cf8) is 0x8000005c > pci_open(1a): mode1res=0x80000000 (0x80000000) > pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=70308086) > Probing for devices on PCI bus 0: > found-> vendor=0x8086, dev=0x7030, revid=0x02 > class=06-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > chip0: rev 0x02 on pci0.0.0 > > PCI Concurrency: enabled > Cache: 256K pipelined-burst secondary; L1 enabled > DRAM: no memory hole, 66 MHz refresh > Read burst timing: x-2-2-2/x-3-3-3 > Write burst timing: x-3-3-3 > RAS-CAS delay: 3 clocks > found-> vendor=0x8086, dev=0x7000, revid=0x01 > class=06-01-00, hdrtype=0x00, mfdev=1 > subordinatebus=0 secondarybus=0 > chip1: rev 0x01 on pci0.7.0 > I/O Recovery Timing: 8-bit 2 clocks, 16-bit 1 clocks > Extended BIOS: disabled > Lower BIOS: disabled > Coprocessor IRQ13: enabled > Mouse IRQ12: disabled > Interrupt Routing: A: disabled, B: disabled, C: IRQ11, D: disabled > MB0: IRQ15, MB1: > found-> vendor=0x8086, dev=0x7010, revid=0x00 > class=01-01-80, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > map[0]: type 4, range 32, base 0000f000, size 4 > ide_pci0: rev 0x00 on pci0.7.1 > intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 > intel_piix_status: primary master fastDMAonly disabled, pre/post enabled, > intel_piix_status: IORDY sampling enabled, > intel_piix_status: fast PIO enabled > intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 > intel_piix_status: primary slave fastDMAonly disabled, pre/post disabled, > intel_piix_status: IORDY sampling disabled, > intel_piix_status: fast PIO disabled > ide_pci: busmaster 0 status: 04 from port: 0000f002 > intel_piix_status: secondary master/slave sample = 3, master/slave recovery = 1 > intel_piix_status: secondary master fastDMAonly disabled, pre/post enabled, > intel_piix_status: IORDY sampling enabled, > intel_piix_status: fast PIO enabled > intel_piix_status: secondary master/slave sample = 3, master/slave recovery = 1 > intel_piix_status: secondary slave fastDMAonly disabled, pre/post disabled, > intel_piix_status: IORDY sampling disabled, > intel_piix_status: fast PIO disabled > ide_pci: busmaster 1 status: 04 from port: 0000f00a > found-> vendor=0x5333, dev=0x8811, revid=0x54 > class=03-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=a, irq=11 > map[0]: type 1, range 32, base e0000000, size 26 > vga0: rev 0x54 int a irq 11 on pci0.10.0 > Probing for devices on the ISA bus: > atkbd: the current kbd controller command byte 0047 > atkbd: keyboard ID 0x41ab (2) > kbdc: RESET_KBD return code:00fa > kbdc: RESET_KBD status:00aa > sc0 on isa > sc0: fb0 kbd0 > sc0: VGA color <8 virtual consoles, flags=0x0> > atkbdc0 at 0x60-0x6f on motherboard > atkbd0 irq 1 on isa > kbd0: atkbd0, AT 101/102 (2), config:0x10000, flags:0x3d0000 > sio0: irq maps: 0x1 0x11 0x1 0x1 > sio0 at 0x3f8-0x3ff irq 4 on isa > sio0: type 16550A > sio2: irq maps: 0x1 0x9 0x1 0x1 > sio2 at 0x3e8-0x3ef irq 3 on isa > sio2: type 16550A > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > fd0: 1.44MB 3.5in > wdc0 at 0x1f0-0x1f7 irq 14 on isa > wdc0: unit 0 (wd0): , LBA, 32-bit, multi-block-16 > wd0: 1628MB (3335472 sectors), 827 cyls, 64 heads, 63 S/T, 512 B/S > wd0: ATA INQUIRE valid = 0003, dmamword = 0407, apio = 0003, udma = 0000 > wdc1 at 0x170-0x177 irq 15 on isa > wdc1: unit 0 (wd2): , LBA, 32-bit, multi-block-16 > wd2: 4892MB (10018890 sectors), 623 cyls, 255 heads, 63 S/T, 512 B/S > wd2: ATA INQUIRE valid = 0007, dmamword = 0407, apio = 0003, udma = 0007 > wdc1: unit 1 (atapi): , removable, dma, iordy > acd0: drive speed 1375KB/sec, 86KB cache > acd0: supported read types: CD-DA > acd0: Audio: play, 255 volume levels > acd0: Mechanism: ejectable tray > acd0: Medium: CD-ROM 120mm data disc loaded, unlocked > npx0 flags 0x1 on motherboard > npx0: INT 16 interface > vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa > fb0: vga0, vga, type:VGA (5), flags:0x7007f > fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 > fb0: init mode:24, bios mode:3, current mode:24 > fb0: window:0xf00b8000 size:32k gran:32k, buf:0x0 size:0k > VGA parameters upon power-up > 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 > bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 > b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c > 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff > VGA parameters in BIOS for mode 24 > 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 > bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 > b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c > 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff > EGA/VGA parameters to be used for mode 24 > 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 > bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 > b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c > 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff > imasks: bio c008c040, tty c003001a, net c0060000 > BIOS Geometries: > 0:03393f3f 0..825=826 cylinders, 0..63=64 heads, 1..63=63 sectors > 1:026dfe3f 0..621=622 cylinders, 0..254=255 heads, 1..63=63 sectors > 0 accounted for > Device configuration finished. > IP packet filtering initialized, divert disabled, rule-based forwarding disabled, logging limited to 5000 packets/entry > bpf: tun0 attached > bpf: lo0 attached > Considering FFS root f/s. > changing root device to wd0s2a > wd0s1: type 0x6, start 63, end = 2088575, size 2088513 : OK > wd0s2: type 0xa5, start 2088576, end = 2153087, size 64512 : OK > wd0s3: type 0xa5, start 2153088, end = 3334463, size 1181376 : OK > wd2s1: type 0xa5, start 63, end = 289169, size 289107 : OK > wd2s2: type 0xa5, start 289170, end = 6554519, size 6265350 : OK > wd2s3: type 0xa5, start 6554520, end = 9687194, size 3132675 : OK > wd2s4: type 0xa5, start 9687195, end = 10008494, size 321300 : OK > ffs_mountfs: superblock updated for soft updates > ffs_mountfs: superblock updated for soft updates > ffs_mountfs: superblock updated for soft updates > ffs_mountfs: superblock updated for soft updates > splash: image decoder found: green_saver > > -- > Ben Smithurst > ben@scientia.demon.co.uk > > send a blank message to ben+pgp@scientia.demon.co.uk for PGP key > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Nathan Ahlstrom nrahlstr@winternet.com http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 25 11: 0:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 09F2C14F4B for ; Thu, 25 Mar 1999 11:00:48 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id LAA71099; Thu, 25 Mar 1999 11:00:28 -0800 (PST) (envelope-from obrien) Date: Thu, 25 Mar 1999 11:00:28 -0800 From: "David O'Brien" To: Rahul Dhesi Cc: freebsd-current@FreeBSD.ORG Subject: Re: rc.conf issues: host identity vs host config Message-ID: <19990325110028.A71063@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <199903251641.AA07426@bolero-x.rahul.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199903251641.AA07426@bolero-x.rahul.net>; from Rahul Dhesi on Thu, Mar 25, 1999 at 08:41:22AM -0800 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think some very basic information identifying a host should be kept > in its own place: > > host name and ip address for each network interface > > And I like the way SunOS does it: The file hostname. contains the > machine's host name, where is the name of the network interface. In /etc/rc.conf have the typical network_interfaces="lo0 fxp0" line, but don't have a ifconfig_fxp0="...." this will cause ``/etc/rc.network'' to run this code: # Set up all the network interfaces, calling startup scripts if needed for ifn in ${network_interfaces}; do if [ -e /etc/start_if.${ifn} ]; then . /etc/start_if.${ifn} fi This is how DHCP users run ``/sbin/dhclient''. So in ``/etc/start_if.fxp0'' you can place ``hostname foo.bar.com'' along with a ``ifconfig fxp0'' line. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 25 11: 6: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 94E191540B for ; Thu, 25 Mar 1999 11:06:02 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id LAA71152; Thu, 25 Mar 1999 11:05:42 -0800 (PST) (envelope-from obrien) Date: Thu, 25 Mar 1999 11:05:42 -0800 From: "David O'Brien" To: Rahul Dhesi Cc: freebsd-current@FreeBSD.ORG Subject: Re: rc.conf issues: host identity vs host config Message-ID: <19990325110542.B71063@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <199903251641.AA07426@bolero-x.rahul.net> <19990325110028.A71063@relay.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990325110028.A71063@relay.nuxi.com>; from David O'Brien on Thu, Mar 25, 1999 at 11:00:28AM -0800 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry to reply to my own email, but there is an error. On Thu, Mar 25, 1999 at 11:00:28AM -0800, David O'Brien wrote: > In /etc/rc.conf have the typical > > network_interfaces="lo0 fxp0" > > line, but don't have a > > ifconfig_fxp0="...." > > this will cause ``/etc/rc.network'' to run this code: The error is, reguardless of any ``ifconfig_fxp0="....."'' lines in /etc/rc.conf, ``/etc/start_if.fxp0'' will be run (if it exists). Thus all you would need to do is put the ``hostname foo.bar.com'' in there. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 25 13:38:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from quackerjack.cc.vt.edu (quackerjack.cc.vt.edu [198.82.160.250]) by hub.freebsd.org (Postfix) with ESMTP id B85FE14D21 for ; Thu, 25 Mar 1999 13:38:04 -0800 (PST) (envelope-from jobaldwi@vt.edu) Received: from sable.cc.vt.edu (sable.cc.vt.edu [128.173.16.30]) by quackerjack.cc.vt.edu (8.8.8/8.8.8) with ESMTP id QAA26279; Thu, 25 Mar 1999 16:37:43 -0500 (EST) Received: from john.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.63]) by sable.cc.vt.edu (8.8.8/8.8.8) with ESMTP id QAA06143; Thu, 25 Mar 1999 16:37:43 -0500 (EST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199903251641.AA07426@bolero-x.rahul.net> Date: Thu, 25 Mar 1999 16:37:42 -0500 (EST) From: John Baldwin To: Rahul Dhesi Subject: RE: rc.conf issues: host identity vs host config Cc: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 25-Mar-99 Rahul Dhesi wrote: > The current rc.conf system doesn't seem to allow for separating out host > identity from host configuration. As a result I'm not able to create a > site-wide rc.conf file and rdist it to multiple machines, configured > identically except for having distinct own host names. I think some > very basic information identifying a host should be kept in its own > place: > > host name and ip address for each network interface Have you looked at DHCP? You don't even have to rdist a file for that to work. We use PicoBSD to clone 80 machines by dd'ing the drives over the network and then have each machine's IP assigned to its ether address and use DHCP to distribute hostnames and IPs to each computer. Works like a charm. --- John Baldwin -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 25 15: 9:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from hun.org (hun.org [207.49.60.254]) by hub.freebsd.org (Postfix) with ESMTP id B6BE415400 for ; Thu, 25 Mar 1999 15:08:54 -0800 (PST) (envelope-from attila@hun.org) Received: from localhost (attila@localhost) by hun.org (8.9.2/8.9.2) with ESMTP id XAA22589 for ; Thu, 25 Mar 1999 23:08:34 GMT (envelope-from attila@hun.org) Date: Thu, 25 Mar 1999 23:08:34 +0000 (GMT) From: attila Reply-To: attila@hun.org To: current@FreeBSD.ORG Subject: Re: "JAIL" code headed for -current. In-Reply-To: <19990127110254.D20146@gti.noc.demon.net> Message-ID: Owner: attila@hun.org Organization: home for unpenitent hackers and anarcho-cryptophreaks Encrypted: NO MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG add my vote for 3.1 chroot() has always been a little less than JAIL if the user so constrained expects/requires access to virtually anything. __________________________________________________________________________ go not unto usenet for advice, for the inhabitants thereof will say: yes, and no, and maybe, and I don't know, and fuck-off. _________________________________________________________________ attila__ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 25 16: 1: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 16B16153A3 for ; Thu, 25 Mar 1999 16:01:00 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id PAA01025; Thu, 25 Mar 1999 15:51:28 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903252351.PAA01025@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Rahul Dhesi Cc: freebsd-current@freebsd.org Subject: Re: rc.conf issues: host identity vs host config In-reply-to: Your message of "Thu, 25 Mar 1999 08:41:22 PST." <199903251641.AA07426@bolero-x.rahul.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 25 Mar 1999 15:51:28 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The current rc.conf system doesn't seem to allow for separating out host > identity from host configuration. Just to squash this; yes, it does. > As a result I'm not able to create a > site-wide rc.conf file and rdist it to multiple machines, configured > identically except for having distinct own host names. I think some > very basic information identifying a host should be kept in its own > place: You can do this trivially. Put the data in /etc/rc.conf.site, and include it at the end of /etc/rc.conf. rc.conf then contains per-system configuration information, and rc.conf.site can be rdist'ed around. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 25 16:15:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id C61FA14CD5 for ; Thu, 25 Mar 1999 16:15:42 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id JAA05055; Fri, 26 Mar 1999 09:15:32 +0900 (JST) Message-ID: <36FACF6E.CB20EC11@newsguy.com> Date: Fri, 26 Mar 1999 09:06:06 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Mike Smith Cc: Rahul Dhesi , freebsd-current@FreeBSD.ORG Subject: Re: rc.conf issues: host identity vs host config References: <199903252351.PAA01025@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > As a result I'm not able to create a > > site-wide rc.conf file and rdist it to multiple machines, configured > > identically except for having distinct own host names. I think some > > very basic information identifying a host should be kept in its own > > place: > > You can do this trivially. Put the data in /etc/rc.conf.site, and > include it at the end of /etc/rc.conf. rc.conf then contains > per-system configuration information, and rc.conf.site can be rdist'ed > around. Last I checked, rc.conf.site was referenced in defaults/rc.conf. Has this changed? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What kind of psychologist laughs at her patients?" "I don't laugh at all of them." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 25 16:19:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 186FB14CD5 for ; Thu, 25 Mar 1999 16:19:41 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10QKL7-000Ctp-00; Fri, 26 Mar 1999 02:19:09 +0200 From: Sheldon Hearn To: "Daniel C. Sobral" Cc: freebsd-current@FreeBSD.ORG Subject: Re: rc.conf issues: host identity vs host config In-reply-to: Your message of "Fri, 26 Mar 1999 09:06:06 +0900." <36FACF6E.CB20EC11@newsguy.com> Date: Fri, 26 Mar 1999 02:19:09 +0200 Message-ID: <49588.922407549@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 26 Mar 1999 09:06:06 +0900, "Daniel C. Sobral" wrote: > Last I checked, rc.conf.site was referenced in defaults/rc.conf. Has > this changed? Check again. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 25 16:53:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from hun.org (hun.org [207.49.60.254]) by hub.freebsd.org (Postfix) with ESMTP id DA15C15259 for ; Thu, 25 Mar 1999 16:53:22 -0800 (PST) (envelope-from attila@hun.org) Received: from localhost (attila@localhost) by hun.org (8.9.2/8.9.2) with ESMTP id AAA22871; Fri, 26 Mar 1999 00:52:54 GMT (envelope-from attila@hun.org) Date: Fri, 26 Mar 1999 00:52:54 +0000 (GMT) From: attila Reply-To: attila@hun.org To: Sean Eric Fagan Cc: current@FreeBSD.ORG Subject: Re: "JAIL" code headed for -current. In-Reply-To: <199901272302.PAA02846@kithrup.com> Message-ID: Owner: attila@hun.org Organization: home for unpenitent hackers and anarcho-cryptophreaks Encrypted: NO MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just noticed the date on this discussion was two months ago; so I referenced the code in kern_prot.c which indicates no decision was made on this item.... was another solution implemented? actually, in a more deliberate consideration of the implications of changing the suser() call, I agree with Eric, but the concept, including assigning an exclusive internal IP number is important enough to warrant implementation, but maybe not with a revision to the suser() arguments. perhaps consider implementing a structure which each suser() call, and any function in the chroot() space, can reference which would contain the value of NOJAIL, the IP number, and whatever other parameters are discovered to be needed later. the structure can be added to any number of the sys/ group includes (all though it must be individually static to each icidence of chroot(). Eric's suggestion of the macro solves two problems: finding all incidents of suser(), and ancilliary code added later which might fail to notice the additional argument for which they would receive the expected response... int new_suser(chroot, cred, acflag) struct uchroot *chroot; struct ucred *cred; u_short *acflag; { if (chroot->nojail) return (EPERM); /* I presume this is the check */ if (cred->cr_uid == 0) { if (acflag) *acflag |= ASU; return (0); } return (EPERM); } I always have a preference to structures despite the extra reference --you can always add variables of any type as required. with the CPU speeds approaching nirvana, every new project is coded with a single stucture passed to each procedure; in many cases passing an element or two is more efficient, but it breaks the model. in general it is no more expensive on cpu time than unravelling a string of variables or structure elements being passed in the call since each has a backward reference. On Wed, 27 Jan 1999, Sean Eric Fagan wrote: *In article <199901271944.LAA15317.kithrup.freebsd.current@kithrup.com> you write: *>>all over the kernel: *>> *>> suser(NOJAIL, bla, bla); *>>or *>> suser(0, bla, bla); *>Oh, goody, more gratuitious incomaptibilities with everyone else. * *And to followup to my own message, since nobody else has: * *This is stupid. While I don't object to the concept (and even know people who *have requested it), that particular implementation sucks. It breaks an *existing API *and* ABI. * *I would suggest using a different routine name than suser(); suser() can be *made into a macro or stub routine that calls the new routine with a first *argument of 0 (or, of course, both a macro *and* a stub routine). * *Any time there's a change, "all over the kernel," THIS SHOULD RAISE WARNING *FLAGS, PEOPLE! * * *To Unsubscribe: send mail to majordomo@FreeBSD.org *with "unsubscribe freebsd-current" in the body of the message * __________________________________________________________________________ go not unto usenet for advice, for the inhabitants thereof will say: yes, and no, and maybe, and I don't know, and fuck-off. _________________________________________________________________ attila__ The more things change, the more they stay insane. To be a ruler of men, you need at least 12 inches.... There is no safety this side of the grave. Never was; never will be. __________________________________________________________________________ "Microsoft isn't evil, they just make really crappy Operating Systems" -Linus Torvalds __________________________________________________________________________ Windows 98: n. useless extension to a minor patch release for 32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand for 1 bit of competition. - (c) 1999 Stan Brown. Redistribution via the Microsoft Network is prohibited. __________________________________________________________________________ (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. __________________________________________________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 25 17:25: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.6.53]) by hub.freebsd.org (Postfix) with ESMTP id D30D41545B for ; Thu, 25 Mar 1999 17:25:02 -0800 (PST) (envelope-from plm@smtp3.xs4all.nl) Received: from localhost. (dc2-isdn1971.dial.xs4all.nl [194.109.155.179]) by smtp3.xs4all.nl (8.8.8/8.8.8) with ESMTP id CAA17692 for ; Fri, 26 Mar 1999 02:24:41 +0100 (CET) Received: (from plm@localhost) by localhost. (8.9.3/8.9.1) id CAA00349; Fri, 26 Mar 1999 02:24:39 +0100 (MET) (envelope-from plm) To: freebsd-current@freebsd.org Subject: LZS (STAC) compression in i4b? From: Peter Mutsaers Date: 24 Mar 1999 23:21:45 +0100 Message-ID: <87u2vaplza.fsf@muon.xs4all.nl> X-Mailer: Gnus v5.6.45/Emacs 20.3 Lines: 15 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Does current i4b support LZS/STAC compression? My ISP just enabled it on their ISDN ports, I'd like to use it. Or is compression not necessary in the kernel driver, but in the userspace programs (ppp, pppd). When I grep through ppp sources I do see STAC mentioned somewhere. -- Peter Mutsaers | Abcoude (Utrecht), | Trust me, I know plm@xs4all.nl | the Netherlands | what I'm doing. ---------------+---------------------+------------------ Running FreeBSD-current UNIX. See http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 25 17:29:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 077CD154FF for ; Thu, 25 Mar 1999 17:29:00 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id UAA29640; Thu, 25 Mar 1999 20:28:52 -0500 (EST) Date: Thu, 25 Mar 1999 20:28:51 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Ben Smithurst Cc: current@FreeBSD.ORG Subject: Re: Spontaneous reboots In-Reply-To: <19990325181528.A310@scientia.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 25 Mar 1999, Ben Smithurst wrote: > Kris Kennaway wrote: > > > Has anyone else been seeing this? What kind of information would help to > > narrow the problem down? > > This has happened a few times on my -stable box, though not very > often. It just happened a few minutes ago, I wasn't doing anything on > the machine, I wasn't even logged in. No core dump or anything. :-( I'd > think nothing of it on a -current box, but it seems a bit worrying that > this sort of thing happens on a supposedly "stable" version. Mind you, > it could be a hardware problem I suppose. It could. Ahem... are you absolutely certain there are no messages in /var/log/messages that happen before the reboot? > > Karl Pielorz wrote: > > > The sort of thing we're looking for is, Which version of FreeBSD > > (I'd assume something -current because you posted to the -current > > mailing list, but how current?), what hardware (i.e. CPU type > > [Intel/AMD/Cyrix]) etc. - how much memory, what types of hard drive > > (SCSI vs. IDE) etc. - if you have any 'weird' hardware in there? > > FreeBSD 3.1-STABLE, Cyrix 6x86 133MHz, 48MB RAM. I don't think I've got > any hardware I'd class as weird. Disk info, > > $ mount > /dev/wd0s2a on / (local, noatime, writes: sync 5 async 17) > /dev/wd0s3c on /home (local, soft-updates, writes: sync 2 async 61) > /dev/wd2s1c on /tmp (local, soft-updates, writes: sync 2 async 31) > /dev/wd2s2e on /usr (local, soft-updates, writes: sync 2 async 86) > /dev/wd2s3e on /var (local, nosuid, soft-updates, writes: sync 318 async 470) > procfs on /proc (local) > $ swapinfo > Device 1K-blocks Used Avail Capacity Type > /dev/wd2s4b 160650 0 160522 0% Interleaved > > I'm not sure how recent, the machine had been up for nearly 22 days, and > I think I rebuilt the world soon before that, so it's as of around the > beginning of March. > > Brian Feldman wrote: > > > He should proviide a full dmesg from bootverbose mode. > > OK, I wonder if anyone can spot the problem in this (if indeed there is > something I've broken)... > > Copyright (c) 1992-1999 FreeBSD Inc. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 3.1-STABLE #104: Tue Mar 2 18:29:08 GMT 1999 > ben@scientia.demon.co.uk:/usr/src/sys/compile/SCIENTIA > Calibrating clock(s) ... i8254 clock: 1193483 Hz > CLK_USE_I8254_CALIBRATION not specified - using default frequency > Timecounter "i8254" frequency 1193182 Hz > CPU: Cyrix 6x86 (486-class CPU) > Origin = "CyrixInstead" DIR=0x2231 Stepping=2 Revision=2 > real memory = 50331648 (49152K bytes) > Physical memory chunk(s): > 0x00001000 - 0x0009ffff, 651264 bytes (159 pages) > 0x00200000 - 0x02ffdfff, 48226304 bytes (11774 pages) > avail memory = 47013888 (45912K bytes) > Found BIOS32 Service Directory header at 0xf00fad20 > Entry = 0xfb1a0 (0xf00fb1a0) Rev = 0 Len = 1 > PCI BIOS entry at 0xb1d0 > Other BIOS signatures found: > ACPI: 00000000 > $PnP: 000fbf50 > pci_open(1): mode 1 addr port (0x0cf8) is 0x8000005c > pci_open(1a): mode1res=0x80000000 (0x80000000) > pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=70308086) > Probing for devices on PCI bus 0: > found-> vendor=0x8086, dev=0x7030, revid=0x02 > class=06-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > chip0: rev 0x02 on pci0.0.0 > > PCI Concurrency: enabled > Cache: 256K pipelined-burst secondary; L1 enabled > DRAM: no memory hole, 66 MHz refresh > Read burst timing: x-2-2-2/x-3-3-3 > Write burst timing: x-3-3-3 > RAS-CAS delay: 3 clocks > found-> vendor=0x8086, dev=0x7000, revid=0x01 > class=06-01-00, hdrtype=0x00, mfdev=1 > subordinatebus=0 secondarybus=0 > chip1: rev 0x01 on pci0.7.0 > I/O Recovery Timing: 8-bit 2 clocks, 16-bit 1 clocks > Extended BIOS: disabled > Lower BIOS: disabled > Coprocessor IRQ13: enabled > Mouse IRQ12: disabled > Interrupt Routing: A: disabled, B: disabled, C: IRQ11, D: disabled > MB0: IRQ15, MB1: > found-> vendor=0x8086, dev=0x7010, revid=0x00 > class=01-01-80, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > map[0]: type 4, range 32, base 0000f000, size 4 > ide_pci0: rev 0x00 on pci0.7.1 > intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 > intel_piix_status: primary master fastDMAonly disabled, pre/post enabled, > intel_piix_status: IORDY sampling enabled, > intel_piix_status: fast PIO enabled > intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 > intel_piix_status: primary slave fastDMAonly disabled, pre/post disabled, > intel_piix_status: IORDY sampling disabled, > intel_piix_status: fast PIO disabled > ide_pci: busmaster 0 status: 04 from port: 0000f002 > intel_piix_status: secondary master/slave sample = 3, master/slave recovery = 1 > intel_piix_status: secondary master fastDMAonly disabled, pre/post enabled, > intel_piix_status: IORDY sampling enabled, > intel_piix_status: fast PIO enabled > intel_piix_status: secondary master/slave sample = 3, master/slave recovery = 1 > intel_piix_status: secondary slave fastDMAonly disabled, pre/post disabled, > intel_piix_status: IORDY sampling disabled, > intel_piix_status: fast PIO disabled > ide_pci: busmaster 1 status: 04 from port: 0000f00a > found-> vendor=0x5333, dev=0x8811, revid=0x54 > class=03-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=a, irq=11 > map[0]: type 1, range 32, base e0000000, size 26 > vga0: rev 0x54 int a irq 11 on pci0.10.0 > Probing for devices on the ISA bus: > atkbd: the current kbd controller command byte 0047 > atkbd: keyboard ID 0x41ab (2) > kbdc: RESET_KBD return code:00fa > kbdc: RESET_KBD status:00aa > sc0 on isa > sc0: fb0 kbd0 > sc0: VGA color <8 virtual consoles, flags=0x0> > atkbdc0 at 0x60-0x6f on motherboard > atkbd0 irq 1 on isa > kbd0: atkbd0, AT 101/102 (2), config:0x10000, flags:0x3d0000 > sio0: irq maps: 0x1 0x11 0x1 0x1 > sio0 at 0x3f8-0x3ff irq 4 on isa > sio0: type 16550A > sio2: irq maps: 0x1 0x9 0x1 0x1 > sio2 at 0x3e8-0x3ef irq 3 on isa > sio2: type 16550A > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > fd0: 1.44MB 3.5in > wdc0 at 0x1f0-0x1f7 irq 14 on isa > wdc0: unit 0 (wd0): , LBA, 32-bit, multi-block-16 > wd0: 1628MB (3335472 sectors), 827 cyls, 64 heads, 63 S/T, 512 B/S > wd0: ATA INQUIRE valid = 0003, dmamword = 0407, apio = 0003, udma = 0000 > wdc1 at 0x170-0x177 irq 15 on isa > wdc1: unit 0 (wd2): , LBA, 32-bit, multi-block-16 > wd2: 4892MB (10018890 sectors), 623 cyls, 255 heads, 63 S/T, 512 B/S > wd2: ATA INQUIRE valid = 0007, dmamword = 0407, apio = 0003, udma = 0007 > wdc1: unit 1 (atapi): , removable, dma, iordy > acd0: drive speed 1375KB/sec, 86KB cache > acd0: supported read types: CD-DA > acd0: Audio: play, 255 volume levels > acd0: Mechanism: ejectable tray > acd0: Medium: CD-ROM 120mm data disc loaded, unlocked > npx0 flags 0x1 on motherboard > npx0: INT 16 interface > vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa > fb0: vga0, vga, type:VGA (5), flags:0x7007f > fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 > fb0: init mode:24, bios mode:3, current mode:24 > fb0: window:0xf00b8000 size:32k gran:32k, buf:0x0 size:0k > VGA parameters upon power-up > 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 > bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 > b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c > 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff > VGA parameters in BIOS for mode 24 > 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 > bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 > b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c > 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff > EGA/VGA parameters to be used for mode 24 > 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 > bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 > b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c > 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff > imasks: bio c008c040, tty c003001a, net c0060000 > BIOS Geometries: > 0:03393f3f 0..825=826 cylinders, 0..63=64 heads, 1..63=63 sectors > 1:026dfe3f 0..621=622 cylinders, 0..254=255 heads, 1..63=63 sectors > 0 accounted for > Device configuration finished. > IP packet filtering initialized, divert disabled, rule-based forwarding disabled, logging limited to 5000 packets/entry > bpf: tun0 attached > bpf: lo0 attached > Considering FFS root f/s. > changing root device to wd0s2a > wd0s1: type 0x6, start 63, end = 2088575, size 2088513 : OK > wd0s2: type 0xa5, start 2088576, end = 2153087, size 64512 : OK > wd0s3: type 0xa5, start 2153088, end = 3334463, size 1181376 : OK > wd2s1: type 0xa5, start 63, end = 289169, size 289107 : OK > wd2s2: type 0xa5, start 289170, end = 6554519, size 6265350 : OK > wd2s3: type 0xa5, start 6554520, end = 9687194, size 3132675 : OK > wd2s4: type 0xa5, start 9687195, end = 10008494, size 321300 : OK > ffs_mountfs: superblock updated for soft updates > ffs_mountfs: superblock updated for soft updates > ffs_mountfs: superblock updated for soft updates > ffs_mountfs: superblock updated for soft updates > splash: image decoder found: green_saver > > -- > Ben Smithurst > ben@scientia.demon.co.uk > > send a blank message to ben+pgp@scientia.demon.co.uk for PGP key > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 25 18:31:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 8189C15614 for ; Thu, 25 Mar 1999 18:31:19 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10QMOh-000GKQ-00 for current@freebsd.org; Fri, 26 Mar 1999 04:30:59 +0200 From: Sheldon Hearn To: current@freebsd.org Subject: Testers wanted: misc/10566 Date: Fri, 26 Mar 1999 04:30:59 +0200 Message-ID: <62769.922415459@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, Can anyone using /etc/pccard_ether with a DHCP implementation _other_ than the one we have in the base system (isc-dhcp2) feed back on the diffs supplied in PR 10566, viewable at http://www.freebsd.org/cgi-bin/query-pr.cgi?pr=10566 Thanks, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 25 23:15:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 5127C14C2F for ; Thu, 25 Mar 1999 23:15:41 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id IAA08013; Fri, 26 Mar 1999 08:15:21 +0100 (CET) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id IAA01588; Fri, 26 Mar 1999 08:15:19 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: attila@hun.org Cc: Sean Eric Fagan , current@FreeBSD.ORG Subject: Re: "JAIL" code headed for -current. In-reply-to: Your message of "Fri, 26 Mar 1999 00:52:54 GMT." Date: Fri, 26 Mar 1999 08:15:18 +0100 Message-ID: <1586.922432518@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , attila writes: > > I just noticed the date on this discussion was two months ago; > so I referenced the code in kern_prot.c which indicates no > decision was made on this item.... > > was another solution implemented? It is on my machine here, It has just been preempted by things related to the real world (& life). Just be patient it is on the way. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 26 0:33:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from hcsext.hcs.de (hcsext.hcs.de [194.123.40.2]) by hub.freebsd.org (Postfix) with SMTP id 3EF70152F3 for ; Fri, 26 Mar 1999 00:33:40 -0800 (PST) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (1837 bytes) by hcsext.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Fri, 26 Mar 1999 09:33:20 +0100 (CET) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-11) Received: by hcswork.hcs.de (Smail3.1.29.0 #12) id m10QS3M-0000c6C; Fri, 26 Mar 99 09:33 MET Message-Id: From: hm@hcs.de (Hellmuth Michaelis) Subject: Re: LZS (STAC) compression in i4b? In-Reply-To: <87u2vaplza.fsf@muon.xs4all.nl> from Peter Mutsaers at "Mar 24, 99 11:21:45 pm" To: plm@xs4all.nl (Peter Mutsaers) Date: Fri, 26 Mar 1999 09:33:20 +0100 (MET) Cc: freebsd-current@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1015 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From the keyboard of Peter Mutsaers: > Does current i4b support LZS/STAC compression? No. > Or is compression not necessary in the kernel driver, but in the > userspace programs (ppp, pppd). When I grep through ppp sources I do > see STAC mentioned somewhere. i4b has nothing in common with userland PPP. It seems STAC makes a version of its compression routines available for noncommercial use, (see www.hifn.com) as i live in Europe, i was not even able to get databooks for the chips they make ..... :-( Because of patent laws, not even rewriting STAC from scratch will help, since it it illegal. I doubt, there will ever be STAC compression available in any free PPP implementation. hellmuth -- Hellmuth Michaelis Tel +49 40 559747-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 559747-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de 22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 26 3: 0:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 1AFC715430 for ; Fri, 26 Mar 1999 03:00:13 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40426>; Fri, 26 Mar 1999 20:46:46 +1000 Date: Fri, 26 Mar 1999 20:59:43 +1000 From: Peter Jeremy Subject: Re: Problems with ELF Emacs To: current@FreeBSD.ORG Message-Id: <99Mar26.204646est.40426@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: >Peter Jeremy writes: >> I'm running -current from a couple of weeks ago. I recently re-compiled >> XFree86 to ELF - which works, and re-compiled emacs-19.34b - which won't >> work with X11, though it does work inside an Xterm. > >I run an Elf build of Emacs 19.34b daily on a completely Elf, very >up-to-date 4.0-CURRENT box with Elf XFree86 3.3.3.1. No trouble at all. I've worked out that emacs is looping in xterm.c:x_make_frame_visible. It is apparently waiting for an input event indicating the the window has been mapped. It expects to get informed of this when a signal (presumably SIGIO) invokes XTread_socket() via input_available_signal(). The only problem is that input_available_signal() never seems to get called. (I haven't been able to track down where F_ASYNC is being set/cleared yet). I'll try another make world next week and see if that helps. Looking into this, I've found a few anomolies: 1) Trying to use the new aout X11 shared libraries reports an undefined ___error. My old shared libraries are OK. I suspect this isn't a major issue. 2) Running an ELF emacs inside gdb, when I set a breakpoint on sigaction, the breakpoint is never hit. Setting a breakpoint on signal and then stepping shows that sigaction (actually _sigaction) is executed - though at a radically different address to the breakpoint. Can one of the ELF experts explain this please. (Not having breakpoints behave as expected is very off-putting). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 26 3:58:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from venus.GAIANET.NET (venus.GAIANET.NET [207.211.200.74]) by hub.freebsd.org (Postfix) with ESMTP id 4E26A14F7F for ; Fri, 26 Mar 1999 03:58:31 -0800 (PST) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.9.1/8.9.1) with ESMTP id DAA09932 for ; Fri, 26 Mar 1999 03:58:13 -0800 (PST) (envelope-from vince@venus.GAIANET.NET) Date: Fri, 26 Mar 1999 03:58:12 -0800 (PST) From: Vincent Poy To: current@FreeBSD.ORG Subject: Curent kernel fails compiling Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As of 3:53AM 3/26/99 PST -Current Kernel compiling, it fails at: loading kernel lpt.o: In function `lpt_request_ppbus': lpt.o(.text+0x1c): undefined reference to `ppb_request_bus' lpt.o: In function `lpt_release_ppbus': lpt.o(.text+0x3c): undefined reference to `ppb_release_bus' lpt.o: In function `lptread': lpt.o(.text+0x6b6): undefined reference to `ppb_1284_negociate' lpt.o(.text+0x6f0): undefined reference to `ppb_1284_read' lpt.o(.text+0x726): undefined reference to `ppb_1284_terminate' lpt.o: In function `lptwrite': lpt.o(.text+0x7bb): undefined reference to `ppb_write' ioconf.o(.data+0x664): undefined reference to `lptdriver' *** Error code 1 Stop. Any ideas? Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 26 4:17:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id A6D9914EFC for ; Fri, 26 Mar 1999 04:17:54 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id NAA49289; Fri, 26 Mar 1999 13:17:30 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199903261217.NAA49289@freebsd.dk> Subject: Re: Curent kernel fails compiling In-Reply-To: from Vincent Poy at "Mar 26, 1999 3:58:12 am" To: vince@venus.GAIANET.NET (Vincent Poy) Date: Fri, 26 Mar 1999 13:17:30 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Vincent Poy wrote: Sounds an awfull lot like you are using the old lpt driver which is no longer present in -current. Look in GENERIC | LINT to see how parallel port are handled nowadays.... > As of 3:53AM 3/26/99 PST -Current Kernel compiling, it fails at: > > loading kernel > lpt.o: In function `lpt_request_ppbus': > lpt.o(.text+0x1c): undefined reference to `ppb_request_bus' > lpt.o: In function `lpt_release_ppbus': > lpt.o(.text+0x3c): undefined reference to `ppb_release_bus' > lpt.o: In function `lptread': > lpt.o(.text+0x6b6): undefined reference to `ppb_1284_negociate' > lpt.o(.text+0x6f0): undefined reference to `ppb_1284_read' > lpt.o(.text+0x726): undefined reference to `ppb_1284_terminate' > lpt.o: In function `lptwrite': > lpt.o(.text+0x7bb): undefined reference to `ppb_write' > ioconf.o(.data+0x664): undefined reference to `lptdriver' > *** Error code 1 > > Stop. > > Any ideas? > > Cheers, > Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ > Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] > GaiaNet Corporation - M & C Estate / / / / | / | __] ] > Beverly Hills, California USA 90210 / / / / / |/ / | __] ] > HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 26 4:48:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from venus.GAIANET.NET (venus.GAIANET.NET [207.211.200.74]) by hub.freebsd.org (Postfix) with ESMTP id BC9F815100 for ; Fri, 26 Mar 1999 04:48:30 -0800 (PST) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.9.1/8.9.1) with ESMTP id EAA10132; Fri, 26 Mar 1999 04:46:41 -0800 (PST) (envelope-from vince@venus.GAIANET.NET) Date: Fri, 26 Mar 1999 04:46:40 -0800 (PST) From: Vincent Poy To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: Curent kernel fails compiling In-Reply-To: <199903261217.NAA49289@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 26 Mar 1999, Soren Schmidt wrote: > It seems Vincent Poy wrote: > > Sounds an awfull lot like you are using the old lpt driver which > is no longer present in -current. Look in GENERIC | LINT to see how > parallel port are handled nowadays.... I'm using the GENERIC config file as of 3/16/99 as the base and the same problem still exists... Let me try again... Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] > > As of 3:53AM 3/26/99 PST -Current Kernel compiling, it fails at: > > > > loading kernel > > lpt.o: In function `lpt_request_ppbus': > > lpt.o(.text+0x1c): undefined reference to `ppb_request_bus' > > lpt.o: In function `lpt_release_ppbus': > > lpt.o(.text+0x3c): undefined reference to `ppb_release_bus' > > lpt.o: In function `lptread': > > lpt.o(.text+0x6b6): undefined reference to `ppb_1284_negociate' > > lpt.o(.text+0x6f0): undefined reference to `ppb_1284_read' > > lpt.o(.text+0x726): undefined reference to `ppb_1284_terminate' > > lpt.o: In function `lptwrite': > > lpt.o(.text+0x7bb): undefined reference to `ppb_write' > > ioconf.o(.data+0x664): undefined reference to `lptdriver' > > *** Error code 1 > > > > Stop. > > > > Any ideas? > > > > Cheers, > > Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ > > Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] > > GaiaNet Corporation - M & C Estate / / / / | / | __] ] > > Beverly Hills, California USA 90210 / / / / / |/ / | __] ] > > HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > -Søren > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 26 8:59:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from kirk.giovannelli.it (kirk.giovannelli.it [194.184.65.4]) by hub.freebsd.org (Postfix) with ESMTP id 4A9E315579 for ; Fri, 26 Mar 1999 08:58:41 -0800 (PST) (envelope-from gmarco@giovannelli.it) Received: from suzy (modem14.masternet.it [194.184.65.24]) by kirk.giovannelli.it (8.9.2/8.9.2) with SMTP id QAA03886 for ; Fri, 26 Mar 1999 16:58:11 GMT (envelope-from gmarco@giovannelli.it) Message-Id: <4.1.19990326175345.009f07d0@194.184.65.4> X-Sender: gmarco@194.184.65.4 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Fri, 26 Mar 1999 17:59:54 +0100 To: current@freebsd.org From: Gianmarco Giovannelli Subject: natd broke my make world (990326) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's more than one days that natd modifications break my make world... Anyone, other than me, has verified it ? (4.0-CURRENT) ===> sbin/natd cc -nostdinc -O -pipe -Wall -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sbin/natd/natd.c cc -nostdinc -O -pipe -Wall -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sbin/natd/icmp.c gzip -cn /usr/src/sbin/natd/natd.8 > natd.8.gz /usr/src/sbin/natd/natd.c:795: conflicting types for `Quit' /usr/src/sbin/natd/natd.h:20: previous declaration of `Quit' /usr/src/sbin/natd/natd.c: In function `Quit': /usr/src/sbin/natd/natd.c:796: warning: passing arg 1 of `Warn' discards `const' from pointer target type /usr/src/sbin/natd/natd.c: At top level: /usr/src/sbin/natd/natd.c:801: conflicting types for `Warn' /usr/src/sbin/natd/natd.h:21: previous declaration of `Warn' *** Error code 1 1 error *** Error code 2 Best Regards, Gianmarco Giovannelli , "Unix expert since yesterday" http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 26 10:15:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id D408114C08 for ; Fri, 26 Mar 1999 10:15:33 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from scientia.demon.co.uk (ident=ben) by scientia.demon.co.uk with local (Exim 2.12 #4) id 10QZ11-0006Cs-00; Fri, 26 Mar 1999 15:59:23 +0000 (envelope-from ben@scientia.demon.co.uk) Date: Fri, 26 Mar 1999 15:59:22 +0000 From: Ben Smithurst To: Brian Feldman Cc: current@FreeBSD.ORG Subject: Re: Spontaneous reboots Message-ID: <19990326155922.A23300@scientia.demon.co.uk> References: <19990325181528.A310@scientia.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Feldman wrote: > It could. Ahem... are you absolutely certain there are no messages in > /var/log/messages that happen before the reboot? Completely certain, there was nothing in /var/log/all either (which as the name suggests, all syslog messages are written to). -- Ben Smithurst ben@scientia.demon.co.uk send a blank message to ben+pgp@scientia.demon.co.uk for PGP key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 26 18:33:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5]) by hub.freebsd.org (Postfix) with ESMTP id D2F8214E75; Fri, 26 Mar 1999 18:33:54 -0800 (PST) (envelope-from mmercer@ipass.net) Received: from ipass.net (ts10-44-ppp.ipass.net [208.209.104.44]) by pluto.ipass.net (8.9.1a/8.9.1) with ESMTP id VAA05428; Fri, 26 Mar 1999 21:33:28 -0500 (EST) Message-ID: <36FC43F5.2DA10D7F@ipass.net> Date: Fri, 26 Mar 1999 21:35:34 -0500 From: "Michael E. Mercer" Reply-To: mmercer@ipass.net X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-questions@FreeBSD.ORG" , freebsd-current@FreeBSD.ORG Subject: What to make of the script /usr/src/tools/LibraryReport/LibraryReport.tcl? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Sorry for posting to two lists...not sure where this should go. I saw an email where someone mentioned this script... how do I make out what this script is telling me and even though this script says a library is stale, does this mean I can remove it??? Also I read someones post about the motherboard not getting enough power and causing things to run slow...how do I check if I fall into this catagory? and if I do fall into it, how do I remedy it? Thanks Michael Mercer mmercer@ipass.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 26 18:34:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id B3EAB1522A for ; Fri, 26 Mar 1999 18:34:57 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id SAA01134 for ; Fri, 26 Mar 1999 18:34:33 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199903270234.SAA01134@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: usb modems and usb soundcards?? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 26 Mar 1999 18:34:33 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since my USB keyboard and mouse are working like a charm , I am looking around for a USB modem and sound card 8) Tnks! Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 27 0:52:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id F086514D74 for ; Sat, 27 Mar 1999 00:52:19 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id IAA08376; Sat, 27 Mar 1999 08:52:11 GMT (envelope-from dfr@nlsystems.com) Date: Sat, 27 Mar 1999 08:52:11 +0000 (GMT) From: Doug Rabson To: Amancio Hasty Cc: current@freebsd.org Subject: Re: usb modems and usb soundcards?? In-Reply-To: <199903270234.SAA01134@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 26 Mar 1999, Amancio Hasty wrote: > > Since my USB keyboard and mouse are working like a charm , I am looking around > for a USB modem and sound card 8) I have some USB digital speakers (but no time to play with them...). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 27 5:12: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id 1BD5614F44 for ; Sat, 27 Mar 1999 05:11:59 -0800 (PST) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.2/8.9.2) with ESMTP id NAA76355; Sat, 27 Mar 1999 13:04:22 GMT (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id MAA03442; Fri, 26 Mar 1999 12:24:19 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199903261224.MAA03442@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: hm@hcs.de Cc: plm@xs4all.nl (Peter Mutsaers), freebsd-current@FreeBSD.ORG Subject: Re: LZS (STAC) compression in i4b? In-reply-to: Your message of "Fri, 26 Mar 1999 09:33:20 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 26 Mar 1999 12:24:19 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [.....] > I doubt, there will ever be STAC compression available in any free PPP > implementation. Agreed. I've talked to both Microsoft and Stac Electronics about this. The only mention in user-ppp is where it identifies frames and parses LCP requests. > hellmuth > -- > Hellmuth Michaelis Tel +49 40 559747-70 > HCS Hanseatischer Computerservice GmbH Fax +49 40 559747-77 > Oldesloer Strasse 97-99 Mail hm [at] hcs.de > 22457 Hamburg WWW http://www.hcs.de -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 27 5:15:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 4AD2C15327 for ; Sat, 27 Mar 1999 05:15:34 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id PAA51568 for ; Sat, 27 Mar 1999 15:15:14 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id PAA03569 for ; Sat, 27 Mar 1999 15:15:13 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199903271315.PAA03569@greenpeace.grondar.za> To: current@freebsd.org Subject: Panic in INTREN on an SMP box? Date: Sat, 27 Mar 1999 15:15:12 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I am getting a reliable "Page fault while in kernel mode" panic on a dual-cpu box running a really recent CURRENT. Doing a "nm /kernel | sort | less" and looking for the address suggests this is happening in INTREN(). Anyone else seeing this? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 27 7:20:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 6CC1914F6B for ; Sat, 27 Mar 1999 07:20:26 -0800 (PST) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it (va-142.skylink.it [194.177.113.142]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id QAA11523; Sat, 27 Mar 1999 16:18:54 +0100 Received: from localhost (localhost.plazza.it [127.0.0.1]) by heidi.plazza.it (8.8.8/8.8.5) with SMTP id QAA10418; Sat, 27 Mar 1999 16:07:55 +0100 (CET) Date: Sat, 27 Mar 1999 16:07:55 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: FreeBSD current Mailing list Subject: Re: usb modems and usb soundcards?? (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Since my USB keyboard and mouse are working like a charm , I am > looking around for a USB modem and sound card 8) Modem: The 3COM I have here. Allthough it is expensive, it is the one I am going to write a driver for next week. The good thing is that it has a serial connector as well. There is others around, and I have no idea whether these are standards compliant (Communication Class Spec.). http://www.usb.org (products section). But hey, I'd say go for it and maybe we get lucky :) Nick -- e-Mail: hibma@skylink.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 27 8:18: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (Postfix) with ESMTP id A8A74155C3 for ; Sat, 27 Mar 1999 08:18:00 -0800 (PST) (envelope-from matt@camtech.com.au) Received: from dialup-ad-10-11.camtech.net.au (dialup-ad-10-11.camtech.net.au [203.28.1.139]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id CAA15275; Sun, 28 Mar 1999 02:53:08 +1030 (CST) Date: Sun, 28 Mar 1999 02:49:01 +0930 (CST) From: Matthew Thyer X-Sender: matt@localhost Reply-To: thyerm@camtech.com.au To: current@freebsd.org Cc: luigi@labinfo.iet.unipi.it Subject: Soundblaster live soundcard support ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is the Creative Labs Soundblaster Live supported under FreeBSD-CURRENT ? This is a PCI card with 3D surround sound (4 speakers). Under Windows it has a soundblaster emulation mode where it emulates a Sound Blaster 16 but the PCI card normally uses a single interrupt and a single I/O port. -- /=======================================================================\ | Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au | \=======================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 27 8:23:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from hcsext.hcs.de (hcsext.hcs.de [194.123.40.2]) by hub.freebsd.org (Postfix) with SMTP id CBF6514D20 for ; Sat, 27 Mar 1999 08:23:31 -0800 (PST) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (1728 bytes) by hcsext.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Sat, 27 Mar 1999 17:21:51 +0100 (CET) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-11) Received: by hcswork.hcs.de (Smail3.1.29.0 #12) id m10QvqD-0000dmC; Sat, 27 Mar 99 17:21 MET Message-Id: From: hm@hcs.de (Hellmuth Michaelis) Subject: Re: LZS (STAC) compression in i4b? In-Reply-To: <199903261224.MAA03442@keep.lan.Awfulhak.org> from Brian Somers at "Mar 26, 99 12:24:19 pm" To: brian@Awfulhak.org (Brian Somers) Date: Sat, 27 Mar 1999 17:21:45 +0100 (MET) Cc: plm@xs4all.nl, freebsd-current@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 854 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I doubt, there will ever be STAC compression available in any free PPP > > implementation. > > Agreed. I've talked to both Microsoft and Stac Electronics about > this. The only mention in user-ppp is where it identifies frames and > parses LCP requests. Strange enough - i ftp'ed me the linux ISDN stuff, and there seem to be a STAC compression implementation based on the RFC in it. I'm really, _really_ interested in STAC's reaction to that, even more because the author seems to be fully aware of the patent situation. hellmuth -- Hellmuth Michaelis Tel +49 40 559747-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 559747-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de 22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 27 8:26:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id B577815252; Sat, 27 Mar 1999 08:26:19 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.8.8/8.8.8) id QAA19134; Sat, 27 Mar 1999 16:25:55 GMT (envelope-from nik) Date: Sat, 27 Mar 1999 16:25:55 +0000 From: Nik Clayton To: current@freebsd.org, doc@freebsd.org Subject: Handbook DocBook cutover complete Message-ID: <19990327162554.K3136@catkin.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Organization: Nik at home, where there's nothing going on Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ Sent to -current, and -doc Reply-to not set. Please reply only to the list appropriate for your comments. Thanks. ] Almost a year ago I started the project to switch the Handbook over from LinuxDoc to DocBook. I've pulled the big shiny lever, and the switch has now happened. This has meant that some URLs to pages within the Handbook have changed. Not many, but a few. For those not following the CVS lists, I've; * Removed this project as an entry from the Doc. Proj.'s "Current Projects" list at docproj/current.html * Checked every reference to the Handbook on the website and FAQ, and updated them where necessary to point to the new pages. * Updated the website make(1) infrastructure to use the DocBook Handbook instead of the LinuxDoc one. * Updated "make release" so that the DocBook Handbook is built. Reactivated the "distribute" target in doc/en/handbook/Makefile to make this happen. Turned off the LinuxDoc Handbook in doc/Makefile. * Edited doc/handbook/Makefile, so it's now a NOP. "make" in there will print a polite message and exit. You should be able to see the effect at roughly 0400 PST. If you can't wait that long, ftp://ftp.freebsd.org/pub/FreeBSD/doc/ *should* contain gzipped copies of the plain text, postscript, and HTML (split, and non split) versions. Assuming the feedback from this is positive I'll "cvs remove" doc/handbook from the repository in a few days time. I'll lift the Handbook freeze at the same point. Advocacy -------- I haven't (yet) put this on the announces page of the website, because I want people to beat up on it in the wild for a day or so first. I'm fairly hopeless at writing press releases, but I think we should shout about this at least a little bit. If anyone wants to volunteer one, please do. If not, could someone (anyone) please forward me a sample FreeBSD press release that I can crib boiler plate from. At the very least I'll try and get it posted to * The Davenport (maintainers of DocBook) mailing list * The SGMLTools mailing list * www.freebsdrocks.com * slashdot.org (they probably won't post it, but you never know) * comp.text.sgml * DaemonNews [ Any other suggestions? ] It's worth mentioning that SGML is the older brother of XML, which is getting quite a lot of press recently. I don't know whether we can leverage that in any way. Known bugs ---------- * I probably haven't caught all the references to old Handbook pages on the site, so there might be some broken links. But I don't think so. This will impact on people who've linked to the Handbook from outside the FreeBSD site though. Sorry 'bout that. * The non-English Handbook's haven't been converted. * PDF generation is broken. I've got a fix, but I haven't tested it yet, and it involves updating a port I don't maintain, so it'll have to wait a couple of days. Acknowledgements ---------------- My thanks to John Fieber, the previous Doc. Proj. manager. It's his fault I started doing this. I remember he thought it would take about 3 hours. 360 days later. . . Thanks also to James Clark, Norm Walsh, and Sebastian Rahtz. Respectively, they are resposible for Jade, which processes and formats the SGML source, the stylesheets which tell Jade how to format the document, and the TeX macros that allow pretty Postscript output. Finally, thanks to those other members of the FreeBSD community (particularly the TeX hackers) who were able to answer my questions when I stumbled in to areas way outside my sphere of competance. Right, I'm off to play Populous. . . -- Bagel: The carbohydrate with the hole To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 27 9: 6:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id 7338814E5D for ; Sat, 27 Mar 1999 09:06:36 -0800 (PST) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.7/8.8.7) with UUCP id RAA13370; Sat, 27 Mar 1999 17:06:14 GMT (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Sat, 27 Mar 1999 16:43:39 GMT X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <199903271315.PAA03569@greenpeace.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 27 Mar 1999 16:43:36 +0000 To: Mark Murray From: Bob Bishop Subject: Re: Panic in INTREN on an SMP box? Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, At 3:15 pm +0200 27/3/99, Mark Murray wrote: >Hi > >I am getting a reliable "Page fault while in kernel mode" panic >on a dual-cpu box running a really recent CURRENT. > >Doing a "nm /kernel | sort | less" and looking for the address >suggests this is happening in INTREN(). > >Anyone else seeing this? Not getting any problems here, cvsup'ed at Sat Mar 27 14:25:51 GMT 1999. Are you doing anything specific to provoke it? -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 27 9:12: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 2179E14E5D for ; Sat, 27 Mar 1999 09:11:39 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id TAA51957; Sat, 27 Mar 1999 19:11:16 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id TAA07884; Sat, 27 Mar 1999 19:11:16 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199903271711.TAA07884@greenpeace.grondar.za> To: Bob Bishop Cc: current@FreeBSD.ORG Subject: Re: Panic in INTREN on an SMP box? In-Reply-To: Your message of " Sat, 27 Mar 1999 16:43:36 GMT." References: Date: Sat, 27 Mar 1999 19:11:16 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bob Bishop wrote: > >Anyone else seeing this? > > Not getting any problems here, cvsup'ed at Sat Mar 27 14:25:51 GMT 1999. > > Are you doing anything specific to provoke it? Building a kernel and rebooting :-). It panics during the device probe phase. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 27 9:27:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-1.ppp.wenet.net [206.15.85.1]) by hub.freebsd.org (Postfix) with ESMTP id 8EAB714BE0 for ; Sat, 27 Mar 1999 09:27:45 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id JAA00402; Sat, 27 Mar 1999 09:27:00 -0800 (PST) (envelope-from garbanzo@hooked.net) Date: Sat, 27 Mar 1999 09:27:00 -0800 (PST) From: Alex Zepeda To: thyerm@camtech.com.au Cc: current@FreeBSD.ORG, luigi@labinfo.iet.unipi.it Subject: Re: Soundblaster live soundcard support ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 28 Mar 1999, Matthew Thyer wrote: > Is the Creative Labs Soundblaster Live supported under FreeBSD-CURRENT ? > > This is a PCI card with 3D surround sound (4 speakers). > > Under Windows it has a soundblaster emulation mode where it emulates > a Sound Blaster 16 but the PCI card normally uses a single interrupt > and a single I/O port. If it's based on the Ensoniq 1370 it's supported (might need to add a PCI ID), otherwise it's not. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 27 9:37:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 7850714D95 for ; Sat, 27 Mar 1999 09:37:09 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id MAA73870; Sat, 27 Mar 1999 12:36:42 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <199903271736.MAA73870@whizzo.transsys.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Alex Zepeda Cc: thyerm@camtech.com.au, current@FreeBSD.ORG, luigi@labinfo.iet.unipi.it From: "Louis A. Mamakos" Subject: Re: Soundblaster live soundcard support ? References: In-reply-to: Your message of "Sat, 27 Mar 1999 09:27:00 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 27 Mar 1999 12:36:42 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, 28 Mar 1999, Matthew Thyer wrote: > > > Is the Creative Labs Soundblaster Live supported under FreeBSD-CURRENT ? > > > > This is a PCI card with 3D surround sound (4 speakers). > > > > Under Windows it has a soundblaster emulation mode where it emulates > > a Sound Blaster 16 but the PCI card normally uses a single interrupt > > and a single I/O port. > > If it's based on the Ensoniq 1370 it's supported (might need to add a PCI > ID), otherwise it's not. No, it's based on the EMU 10K1 device, and as usual, Creative (who also owns EMU) isn't publishing documentation on the device. There's apparently work underway at Creative to build a Linux driver for it, but I haven't heard much about that lately. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 27 22:10:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (Postfix) with ESMTP id AC43914EF9; Sat, 27 Mar 1999 22:10:39 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id QAA21079; Sun, 28 Mar 1999 16:41:29 +0930 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA00589; Sun, 28 Mar 1999 16:40:22 +0930 Date: Sun, 28 Mar 1999 16:40:22 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: Nik Clayton Cc: current@freebsd.org, doc@freebsd.org Subject: Re: Handbook DocBook cutover complete In-Reply-To: <19990327162554.K3136@catkin.nothing-going-on.org> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 27 Mar 1999, Nik Clayton wrote: > Almost a year ago I started the project to switch the Handbook over > from LinuxDoc to DocBook. Can I ask what the differences and benefits are? Kris ----- The Feynman problem-solving algorithm: 1. Write down the problem 2. Think real hard 3. Write down the solution To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 27 23:13:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id BF45114EBE for ; Sat, 27 Mar 1999 23:13:23 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id BAA21948 for ; Sun, 28 Mar 1999 01:45:49 -0500 (EST) Date: Sun, 28 Mar 1999 01:45:48 -0500 (EST) From: Chuck Robey To: freebsd-current@FreeBSD.ORG Subject: ctm to jp.freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Before I start getting screams of rage about ctm being down, it isn't, but it looks like to world has lost net connectivity to jp.freebsd.org, so the last src and cvs-cur deltas have mail-bounced. They'll get thru when connectivity comes back. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message