From owner-freebsd-current Sun Jan 28 1: 2:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id B815437B69E; Sun, 28 Jan 2001 01:02:28 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id UAA32716; Sun, 28 Jan 2001 20:02:25 +1100 Date: Sun, 28 Jan 2001 20:02:13 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: current@freebsd.org Cc: des@freebsd.org Subject: man broken Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG man(1) was broken in rev.1.39 of src/gnu/usr.bin/man/man/man.c: $ man ls Syntax error: "(" unexpected (expecting ")") Error executing formatting or display command. system command exited with status 512 Syntax error: "(" unexpected (expecting ")") Error executing formatting or display command. system command exited with status 512 No manual entry for man $ man -d ls ... trying command: (cd /usr/share/man ; /usr/bin/zcat /usr/share/man/man1/ls.1.gz | /usr/bin/tbl | /usr/bin/groff -S -Wall -mtty-char -mandoc(null) | /usr/bin/col | less -i) Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 1:10: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from syncopation-01.iinet.net.au (syncopation-01.iinet.net.au [203.59.24.37]) by hub.freebsd.org (Postfix) with SMTP id 12DE537B69F for ; Sun, 28 Jan 2001 01:09:43 -0800 (PST) Received: (qmail 5361 invoked by uid 666); 28 Jan 2001 09:17:27 -0000 Received: from reggae-03-162.nv.iinet.net.au (HELO elischer.org) (203.59.78.162) by mail.m.iinet.net.au with SMTP; 28 Jan 2001 09:17:27 -0000 Message-ID: <3A71C728.BD4F4433@elischer.org> Date: Fri, 26 Jan 2001 10:51:20 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Idea Receiver Cc: freebsd-current@FreeBSD.ORG Subject: Re: about ppp.. References: Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Idea Receiver wrote: > > One of my current machines here are running PPPoE.. > for some reason, it will some times become extramly lag of its PPPoE > connection. (for example, from 25ns ping time become 2500ns ping > time). And will back to normal in few mins.. > However, i do not see the same problem on my 4.2 stable system. how 'current' are your systems? when did this behaviour start? (i.e. before or after the latest round of netgraph changes?) > > is this a known problem or just me? plz help! > > thx.. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ from Perth, presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 1:14: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from syncopation-03.iinet.net.au (syncopation-03.iinet.net.au [203.59.24.49]) by hub.freebsd.org (Postfix) with SMTP id BC02037B69E for ; Sun, 28 Jan 2001 01:13:44 -0800 (PST) Received: (qmail 10920 invoked by uid 666); 28 Jan 2001 09:22:13 -0000 Received: from reggae-03-162.nv.iinet.net.au (HELO elischer.org) (203.59.78.162) by mail.m.iinet.net.au with SMTP; 28 Jan 2001 09:22:13 -0000 Message-ID: <3A73E2B8.732057F9@elischer.org> Date: Sun, 28 Jan 2001 01:13:28 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: kernel threading: the first steps [patch] References: <9331.980586893@critter> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > > In message <200101270833.AAA75738@InterJet.elischer.org>, Root Dude writes: > > > >Here's a first step. > > > >I've broken the proc structure into 4 structures. [...] > > Uhm Julian, > > You are aware that other people are working on this stuff too ? well considering that I was int he discussions and since then no-one has said anything, no as far as I know, no-one is currently working on this... if htey are then hey shuld have mentionned it to dan eischen and me since we were leading the discussions. > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 1:14:20 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp.wanadoo.nl (smtp.wanadoo.nl [194.134.193.6]) by hub.freebsd.org (Postfix) with ESMTP id 1E16237B69F for ; Sun, 28 Jan 2001 01:13:56 -0800 (PST) Received: from ams-gw.sohara.org (p021.vcu.wanadoo.nl [194.134.200.21]) by smtp.wanadoo.nl (8.9.3/8.9.3) with SMTP id KAA25391 for ; Sun, 28 Jan 2001 10:13:53 +0100 (MET) Date: Sun, 28 Jan 2001 10:13:49 +0100 From: "Steve O'Hara-Smith" To: current@freebsd.org Subject: /etc/shells #include syntax support patch Message-Id: <20010128101349.2c94539f.steveo@eircom.net> X-Mailer: Sylpheed version 0.4.9 (GTK+ 1.2.8; FreeBSD 4.2-STABLE; i386) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Asbestos suit on, round two. The patch below changes getusershell to support a #include syntax in /etc/shells. It is against RELENG_4 and may require a bit of fiddling to apply to -current (because of nsdispatch()). Everything that I can find is using it (well adduser.perl has the same support written in perl) including sendmail although I cannot see why sendmail isn't using it's built in fallback code, but it isn't somewhere I haven't found HASGETUSERSHELL is being set or assumed. I'm not looking anymore. The changes are confined to adduser.perl, getusershell.c and shells. BTW: is there a reason for the avoidance of my in adduser.perl ? Index: etc/shells =================================================================== RCS file: /home/ncvs/src/etc/shells,v retrieving revision 1.3.2.1 diff -u -r1.3.2.1 shells --- etc/shells 2000/07/10 08:47:17 1.3.2.1 +++ etc/shells 2001/01/27 16:32:01 @@ -1,4 +1,4 @@ -# $FreeBSD: src/etc/shells,v 1.3.2.1 2000/07/10 08:47:17 obrien Exp $ +# $FreeBSD: src/etc/shells,v 1.3 1999/08/27 23:23:45 peter Exp $ # # List of acceptable shells for chpass(1). # Ftpd will not allow users to connect who are not using @@ -7,3 +7,4 @@ /bin/sh /bin/csh /bin/tcsh +#include /usr/local/etc/shells Index: lib/libc/gen/getusershell.c =================================================================== RCS file: /home/ncvs/src/lib/libc/gen/getusershell.c,v retrieving revision 1.3 diff -u -r1.3 getusershell.c --- lib/libc/gen/getusershell.c 1999/11/04 04:16:28 1.3 +++ lib/libc/gen/getusershell.c 2001/01/28 08:57:29 @@ -45,6 +45,7 @@ #include #include #include +#include /* * Local shells should NOT be added here. They should be added in @@ -52,8 +53,9 @@ */ static char *okshells[] = { _PATH_BSHELL, _PATH_CSHELL, NULL }; -static char **curshell, **shells, *strings; +static char **curshell, **shells; static char **initshells __P((void)); +static int shellslots = 0; /* * Get a list of shells from _PATH_SHELLS, if it exists. @@ -74,66 +76,87 @@ void endusershell() { - - if (shells != NULL) + char **sp; + if (shells != NULL) { + for (sp = shells; *sp; sp++) { + free (*sp); + } free(shells); + } shells = NULL; - if (strings != NULL) - free(strings); - strings = NULL; + shellslots = 0; curshell = NULL; } void setusershell() { - curshell = initshells(); } static char ** -initshells() +readshellfile (char *path) { - register char **sp, *cp; register FILE *fp; - struct stat statb; + static int sp; + register char *cp; + void *new; + char buf[MAXPATHLEN]; + char *st; + int newslots; - if (shells != NULL) - free(shells); - shells = NULL; - if (strings != NULL) - free(strings); - strings = NULL; - if ((fp = fopen(_PATH_SHELLS, "r")) == NULL) - return (okshells); - if (fstat(fileno(fp), &statb) == -1) { - (void)fclose(fp); - return (okshells); - } - if ((strings = malloc((u_int)statb.st_size)) == NULL) { - (void)fclose(fp); - return (okshells); + if (shellslots == 0) { + sp = 0; } - shells = calloc((unsigned)statb.st_size / 3, sizeof (char *)); - if (shells == NULL) { - (void)fclose(fp); - free(strings); - strings = NULL; - return (okshells); - } - sp = shells; - cp = strings; - while (fgets(cp, MAXPATHLEN + 1, fp) != NULL) { + if ((fp = fopen(path, "r")) == NULL) + return (NULL); + while (fgets(buf, MAXPATHLEN + 1, fp) != NULL) { + cp = buf; while (*cp != '#' && *cp != '/' && *cp != '\0') cp++; - if (*cp == '#' || *cp == '\0') + if (*cp == '#' || *cp == '\0') { + if (!strncmp (cp, "#include", 8)) { + cp++; + while (*cp != '#' && *cp != '/' && *cp != '\0') + cp++; + if (*cp == '/') { + char *fn = cp; + while (!isspace((unsigned char)*cp) && *cp != '#' && *cp != '\0') + cp++; + *cp++ = '\0'; + readshellfile (fn); + } + } continue; - *sp++ = cp; + } + if (sp >= (shellslots - 1)) { + newslots = shellslots ? 2*shellslots : 8; + new = realloc ((void *)shells, newslots * sizeof (char *)); + if (new == NULL) { + shells[sp] = NULL; + return shells; + } + shells = new; + shellslots = newslots; + } + st = cp; while (!isspace((unsigned char)*cp) && *cp != '#' && *cp != '\0') cp++; *cp++ = '\0'; + shells[sp++] = strdup (st); } - *sp = NULL; + shells[sp] = NULL; (void)fclose(fp); return (shells); +} + +static char ** +initshells() +{ + char **sp; + endusershell (); + if (!readshellfile (_PATH_SHELLS)) { + return (okshells); + } + return shells; } Index: usr.sbin/adduser/adduser.perl =================================================================== RCS file: /home/ncvs/src/usr.sbin/adduser/adduser.perl,v retrieving revision 1.44 diff -u -r1.44 adduser.perl --- usr.sbin/adduser/adduser.perl 1999/08/28 01:15:11 1.44 +++ usr.sbin/adduser/adduser.perl 2001/01/28 08:52:17 @@ -86,11 +86,26 @@ # read shell database, see also: shells(5) sub shells_read { - local($sh); local($err) = 0; + shells_file_read ($etc_shells); + + # Allow /nonexistent and /bin/date as a valid shell for system utils + push(@list, "/nonexistent"); + push(@shellpref, "no") if !grep(/^no$/, @shellpref); + $shell{"no"} = "/nonexistent"; + + push(@list, "/bin/date"); + push(@shellpref, "date") if !grep(/^date$/, @shellpref); + $shell{"date"} = "/bin/date"; +} + +sub shells_file_read { + my $shellsfile = shift; + local($sh); + local *S; - print "Check $etc_shells\n" if $verbose; - open(S, $etc_shells) || die "$etc_shells:$!\n"; + print "Check $shellsfile\n" if $verbose; + open(S, $shellsfile) || die "$shellsfile:$!\n"; while() { if (/^\s*\//) { @@ -102,18 +117,10 @@ warn "Shell: $sh not executable!\n"; $err++; } - } + } elsif (/\#include\s+(\S+)/) { + shells_file_read ($1); + } } - - # Allow /nonexistent and /bin/date as a valid shell for system utils - push(@list, "/nonexistent"); - push(@shellpref, "no") if !grep(/^no$/, @shellpref); - $shell{"no"} = "/nonexistent"; - - push(@list, "/bin/date"); - push(@shellpref, "date") if !grep(/^date$/, @shellpref); - $shell{"date"} = "/bin/date"; - return $err; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 1:24:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 15B6437B69F for ; Sun, 28 Jan 2001 01:24:32 -0800 (PST) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id f0S9O9T29141 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK) for ; Sun, 28 Jan 2001 10:24:26 +0100 (MET) Received: from cicely5.cicely.de (cicely5.cicely.de [fec0:0:0:104::5]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id f0S9OGA26952 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified NO) for ; Sun, 28 Jan 2001 10:24:19 +0100 (CET) Received: (from ticso@localhost) by cicely5.cicely.de (8.11.1/8.11.1) id f0S9OCW48583 for freebsd-current@freebsd.org; Sun, 28 Jan 2001 10:24:12 +0100 (CET) (envelope-from ticso) Date: Sun, 28 Jan 2001 10:24:12 +0100 From: Bernd Walter To: freebsd-current@freebsd.org Subject: ps -j broken Message-ID: <20010128102411.A48494@cicely5.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running -current source from 26th Jan 2001 on an alpha and getting the following error: # ps -j ps: sess: keyword not found USER PID PPID PGID JOBC STAT TT TIME COMMAND root 367 364 367 1 DW p0 0:00.02 msu (su2) root 368 367 368 1 DW+ p0 0:00.14 -csh (tcsh) [...] A verification with i386 and 7th Jan Source: # ps -j ps: sess: keyword not found USER PID PPID PGID JOBC STAT TT TIME COMMAND root 48574 2792 48574 1 S pg 0:00.16 /tcsh root 48577 48574 48577 1 R+ pg 0:00.01 ps -j [...] -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 1:27:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from syncopation-03.iinet.net.au (syncopation-03.iinet.net.au [203.59.24.49]) by hub.freebsd.org (Postfix) with SMTP id 55AA337B400 for ; Sun, 28 Jan 2001 01:27:21 -0800 (PST) Received: (qmail 11708 invoked by uid 666); 28 Jan 2001 09:35:49 -0000 Received: from reggae-03-162.nv.iinet.net.au (HELO elischer.org) (203.59.78.162) by mail.m.iinet.net.au with SMTP; 28 Jan 2001 09:35:49 -0000 Message-ID: <3A73E5E8.79891C01@elischer.org> Date: Sun, 28 Jan 2001 01:27:04 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Jason Evans Cc: current@freebsd.org Subject: Re: kernel threading: the first steps [patch] References: <200101270833.AAA75738@InterJet.elischer.org> <20010127041753.K87569@canonware.com> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jason Evans wrote: > > On Sat, Jan 27, 2001 at 12:33:23AM -0800, Root Dude wrote: > > > > Here's a first step. > > This is very disappointing, Julian. You've duplicated work that I've > already done, and if you've been paying attention at all, you know that it > was already done. Even if you haven't been paying attention, I find it > particularly telling that you never even sent me email about this. I didn't even know I was going to do it, How could I let you know I was going to :-) ... it only took 5 hours while sitting in economy class.. you couldn't tell, but I sent it from the passenger lounge at singapore airport. > > This is the single most flagrant lack of cooperation I have experienced > while working with the FreeBSD Project. I'm truly dumbfounded. It's not a lack of co-operation.. it's a lack of communication. I didn't see an any lists that anyone was doing this yet and thought I'd get the ball rolling to promote discussion.. I'm dumfounded to discover that you've done work here already as I thought I'd have heard of it. I'm sad you take it as an insult. All I want is to start discussion, and I was doing it as a way of clarifying my thoughts as to what wqas needed. > > Jason Jason,. how would I know you have done this? As the person who was leading the discussion on arch, I assumed that if anyone did it they would mention it at least and that I would hear about it.. I assumed that since no-one mentionned anything about it, that they were waiting until the SMP locking was a litlle more settled before starting. I've been paying attention in smp, arch and current, and seen no mention of it, and I sent an email on this 3 months ago that no-one really responded to.. Is there another list I should be on that I don't know about? And anyhow, It only took about 5 hours on a plane.. I was amazed at how little work it was and how quick it was.. I was doing it only as a thought exercise but to my amazement it actually worked !! If you've already done this, then 'great' but you could have answered my previous email asking if anyone was doing it yet.. You can hardly say that you didn't know I was interested in it.... (BTW The comments I made on your doc still stand, though I noticed the last I looked that the doc had'nt changed..) -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 1:58:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (grouter.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 7EA2A37B698 for ; Sun, 28 Jan 2001 01:58:38 -0800 (PST) Received: from grondar.za (root@gratis.grondar.za [196.7.18.133]) by gratis.grondar.za (8.11.1/8.11.1) with ESMTP id f0S9wDW18902; Sun, 28 Jan 2001 11:58:16 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200101280958.f0S9wDW18902@gratis.grondar.za> To: Julian Elischer Cc: current@FreeBSD.ORG Subject: Re: kernel threading: the first steps [patch] References: <3A73E5E8.79891C01@elischer.org> In-Reply-To: <3A73E5E8.79891C01@elischer.org> ; from Julian Elischer "Sun, 28 Jan 2001 01:27:04 PST." Date: Sun, 28 Jan 2001 11:58:18 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > This is the single most flagrant lack of cooperation I have experienced > > while working with the FreeBSD Project. I'm truly dumbfounded. > > It's not a lack of co-operation.. it's a lack of communication. I didn't > see an any lists that anyone was doing this yet and thought I'd get > the ball rolling to promote discussion.. I'm dumfounded to discover that you've > done work here already as I thought I'd have heard of it. I'm sad you > take it as an insult. All I want is to start discussion, and I was doing > it as a way of clarifying my thoughts as to what wqas needed. Um, Julian - I have known about this for a good couple of months. I can't remember specifically _how_ I know; suffice to say there has been a fair bit of dialogue on the lists and Jason's progress-page has a good overview. http://people.freebsd.org/~jasone/smp/ M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 3:20:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from syncopation-01.iinet.net.au (syncopation-01.iinet.net.au [203.59.24.37]) by hub.freebsd.org (Postfix) with SMTP id 0C46B37B400 for ; Sun, 28 Jan 2001 03:20:28 -0800 (PST) Received: (qmail 11902 invoked by uid 666); 28 Jan 2001 11:28:13 -0000 Received: from reggae-03-162.nv.iinet.net.au (HELO elischer.org) (203.59.78.162) by mail.m.iinet.net.au with SMTP; 28 Jan 2001 11:28:13 -0000 Message-ID: <3A74006C.518630F2@elischer.org> Date: Sun, 28 Jan 2001 03:20:12 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Mark Murray Cc: current@FreeBSD.ORG Subject: Re: kernel threading: the first steps [patch] References: <3A73E5E8.79891C01@elischer.org> <200101280958.f0S9wDW18902@gratis.grondar.za> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Murray wrote: > > > > This is the single most flagrant lack of cooperation I have experienced > > > while working with the FreeBSD Project. I'm truly dumbfounded. > > > > It's not a lack of co-operation.. it's a lack of communication. I didn't > > see an any lists that anyone was doing this yet and thought I'd get > > the ball rolling to promote discussion.. I'm dumfounded to discover that you've > > done work here already as I thought I'd have heard of it. I'm sad you > > take it as an insult. All I want is to start discussion, and I was doing > > it as a way of clarifying my thoughts as to what wqas needed. > > Um, Julian - I have known about this for a good couple of months. I > can't remember specifically _how_ I know; suffice to say there has > been a fair bit of dialogue on the lists and Jason's progress-page > has a good overview. > > http://people.freebsd.org/~jasone/smp/ Ok so I had another look and I was mostly right the first time.. That is the SMP page. This is kernel support for threading.. A differnt issue. There is no mention on the SMP progress page of ANYONE splitting the process structure. Looking around his site I found the 'kse' page http://people.freebsd.org/~jasone/kse previously I only knew of http://people.freebsd.org/~jasone/refs/freebsd_kse/freebsd_kse.html From the newly found page I see that indeed he has reported having done this.. But I didn't know about that page before. I sent a mail on the topic on November 26 to -arch (where threading conversation was based) and with JasonE specifically CC'd. So he cannot claim that he wasn't informed. (others reponded to the mail so I know it went out). (He didn't respond) If he had bothered to answer my mail with the fact that he had just done this a few days before, I would have been delighted. Since I was the person that was instrumental in pusing the KSE model forward, I find it strange that Jason didn't let me know what was going on. I only found this page because I figured that there must be something there that I didn't know about, after others (the first being phk) told me that "Hey Jason's already done that". I'm on -arch, -current and -smp and I didn't see any comments on this. Blaming me is the wrong direction to point the finger.. we just need to ensure that all players know what is currently being discussed where. In any case it was only a 5 hour hack so if I've duplicated his work I've only wasted 5 hours of my time. I'm pleased that Jason did this and I'm trying to find out where I can get a copy of his work to look at. > > M > -- > Mark Murray > Warning: this .sig is umop ap!sdn > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 3:38:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from urban.iinet.net.au (urban.iinet.net.au [203.59.24.231]) by hub.freebsd.org (Postfix) with ESMTP id 9857A37B402 for ; Sun, 28 Jan 2001 03:38:31 -0800 (PST) Received: from elischer.org (reggae-03-162.nv.iinet.net.au [203.59.78.162]) by urban.iinet.net.au (8.8.7/8.8.7) with ESMTP id TAA29222 for ; Sun, 28 Jan 2001 19:38:28 +0800 Message-ID: <3A7404A7.860FE118@elischer.org> Date: Sun, 28 Jan 2001 03:38:15 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: kernel threading: the first steps [patch] References: <3A73E5E8.79891C01@elischer.org> <200101280958.f0S9wDW18902@gratis.grondar.za> <3A74006C.518630F2@elischer.org> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG BTW Mark, your mail server is somehow incompatible with my ISP.. error message follows: -------- Hi. This is the qmail-send program at syncopation-01.iinet.net.au. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. : Connected to 196.7.18.141 but sender was rejected. Remote host said: 550 5.0.0 Access denied -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 3:52:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.ninth-circle.org (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id B710137B402 for ; Sun, 28 Jan 2001 03:52:38 -0800 (PST) Received: (from asmodai@localhost) by lucifer.ninth-circle.org (8.11.1/8.11.0) id f0SBqYk70477; Sun, 28 Jan 2001 12:52:34 +0100 (CET) (envelope-from asmodai) Date: Sun, 28 Jan 2001 12:52:34 +0100 From: Jeroen Ruigrok van der Werven To: Patrick Hartling Cc: freebsd-current@FreeBSD.ORG Subject: Re: Fixed: LyX 1.1.5.2 dumping core Message-ID: <20010128125234.A68355@lucifer.bart.nl> References: <20010127184654.C42CD5E32@tomservo.vrac.iastate.edu> <20010127212514.AF1425E2C@tomservo.vrac.iastate.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010127212514.AF1425E2C@tomservo.vrac.iastate.edu>; from patrick@137.org on Sat, Jan 27, 2001 at 03:25:14PM -0600 Organisation: VIA Net.Works The Netherlands Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20010127 22:30], Patrick Hartling (patrick@137.org) wrote: >Making a symlink from /usr/lib/libc.so.5 to /usr/lib/libc.so.3 seems to >have fixed my LyX problems. I'm guessing libc.so.5 and libc.so.3 were >causing conflicts, especially with the recent changes to libc, but I'm no >expert. Whatever the case, I can get back to work on my thesis now. :) Have you tried recompiling LyX with the new libc? That should normally clear any problems. I suspect from what you said above, that when you do ldd `which lyx` it will report lyx being linked against libc.so.3, but for some reason is trying to use the higher version libc. -- Jeroen Ruigrok van der Werven VIA Net.Works The Netherlands BSD: Technical excellence at its best Network- and systemadministrator D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 Misery loves company... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 4:34:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from RedDust.bluesky.net.au (CPE-61-9-140-158.vic.bigpond.net.au [61.9.140.158]) by hub.freebsd.org (Postfix) with ESMTP id 1963737B699 for ; Sun, 28 Jan 2001 04:34:36 -0800 (PST) Received: from localhost (receiver@localhost) by RedDust.bluesky.net.au (8.11.1/8.11.0) with ESMTP id f0SCVkk16481; Sun, 28 Jan 2001 22:31:46 +1000 (EST) (envelope-from receiver@blueskybbs.yi.org) Date: Sun, 28 Jan 2001 22:31:46 +1000 (EST) From: Idea Receiver To: Julian Elischer Cc: Idea Receiver , freebsd-current@FreeBSD.ORG Subject: Re: about ppp.. In-Reply-To: <3A71C728.BD4F4433@elischer.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 Fri, 26 Jan 2001, Julian Elischer wrote: > how 'current' are your systems? > when did this behaviour start? > (i.e. before or after the latest round of netgraph changes?) it is before new netgraph... i think the new netgraph cause the same problem as well.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 5:36:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from mamba.cids.org.za (mamba.cids.org.za [146.64.58.49]) by hub.freebsd.org (Postfix) with ESMTP id 54D2737B400 for ; Sun, 28 Jan 2001 05:36:18 -0800 (PST) Received: (from pallenby@localhost) by mamba.cids.org.za (8.11.1/8.9.1) id f0SDaAR31229 for current@freebsd.org; Sun, 28 Jan 2001 15:36:10 +0200 (SAT) (envelope-from pallenby) From: Paul Allenby Message-Id: <200101281336.f0SDaAR31229@mamba.cids.org.za> Subject: sh can't be exec'd To: current@freebsd.org Date: Sun, 28 Jan 2001 15:36:09 +0200 (SAT) X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all For the last week, each kernel built with fresh source code cannot exec sh. I've seen a lot of emails about this, but most were about the "correct" way to rebuild a system. Is this a problem affecting only me? Paul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 5:59:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from bodeca.talarion.com (mail.talarion.com [209.224.141.78]) by hub.freebsd.org (Postfix) with ESMTP id 8A6BC37B400 for ; Sun, 28 Jan 2001 05:59:20 -0800 (PST) Received: from default (c02-092.071.popsite.net [64.24.137.92]) by bodeca.talarion.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id D5DZWG8B; Sun, 28 Jan 2001 09:05:42 -0500 To: From: grobusc@yahoo.com Subject: I've got a feeling Date: Sun, 28 Jan 2001 08:05:12 -0600 Message-Id: <36919.336944907411200.9521461@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ..somebody's trying to sneak in our frat and it ain't gonna be nothing like that!! As a member of the same subscriber club YOU JUST GOTTA SEE THIS FRAT MOVIE at http://www.frat-movie.com I personally think each and every one of us must see it! SUPPORT BLACK MOVIES! This one IS A MUST SEE! 1Luv Grob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 7:22:21 2001 Delivered-To: freebsd-current@freebsd.org Received: from hera.drwilco.net (10dyn128.dh.casema.net [212.64.31.128]) by hub.freebsd.org (Postfix) with ESMTP id A232537B400 for ; Sun, 28 Jan 2001 07:22:01 -0800 (PST) Received: from ceres.drwilco.nl (ceres.drwilco.net [10.1.1.19]) by hera.drwilco.net (8.11.1/8.11.1) with ESMTP id f0SFhbb01705; Sun, 28 Jan 2001 16:43:47 +0100 (CET) (envelope-from drwilco@drwilco.nl) Message-Id: <4.3.2.7.0.20010128161923.00c74440@mail.bsdchicks.com> X-Sender: lists@mail.bsdchicks.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sun, 28 Jan 2001 16:22:09 +0100 To: Paul Allenby , current@FreeBSD.ORG From: "Rogier R. Mulhuijzen" Subject: Re: sh can't be exec'd In-Reply-To: <200101281336.f0SDaAR31229@mamba.cids.org.za> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >For the last week, each kernel built with fresh source code >cannot exec sh. I've seen a lot of emails about this, but >most were about the "correct" way to rebuild a system. >Is this a problem affecting only me? I haven't had any trouble. How do you rebuild your system? What is the exact error you get? And (at the risk of sounding stupid) what's the output of ls -l /bin/sh? DocWilco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 8:16:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from mamba.cids.org.za (mamba.cids.org.za [146.64.58.49]) by hub.freebsd.org (Postfix) with ESMTP id 0D18D37B402 for ; Sun, 28 Jan 2001 08:16:10 -0800 (PST) Received: (from pallenby@localhost) by mamba.cids.org.za (8.11.1/8.9.1) id f0SGFlT31423; Sun, 28 Jan 2001 18:15:47 +0200 (SAT) (envelope-from pallenby) From: Paul Allenby Message-Id: <200101281615.f0SGFlT31423@mamba.cids.org.za> Subject: Re: sh can't be exec'd To: drwilco@drwilco.nl (Rogier R. Mulhuijzen) Date: Sun, 28 Jan 2001 18:15:46 +0200 (SAT) Cc: current@FreeBSD.ORG In-Reply-To: <4.3.2.7.0.20010128161923.00c74440@mail.bsdchicks.com> from "Rogier R. Mulhuijzen" at Jan 28, 2001 04:22:09 PM X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Rogier R. Mulhuijzen wrote:" > > > >For the last week, each kernel built with fresh source code > >cannot exec sh. I've seen a lot of emails about this, but > >most were about the "correct" way to rebuild a system. > >Is this a problem affecting only me? > > I haven't had any trouble. > > How do you rebuild your system? What is the exact error you get? > And (at the risk of sounding stupid) what's the output of ls -l /bin/sh? > cd /usr/src/sys/i386/conf;config XXX;cd ../../compile/XXX; make depend; make No errors, just the usual prompt for a path to a shell, as if one had booted single user. 526188 sh, without resorting to a fixit disc. Thanks for your reply! Paul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 8:35:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 0F08B37B400; Sun, 28 Jan 2001 08:35:22 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id DAA19164; Mon, 29 Jan 2001 03:35:19 +1100 Date: Mon, 29 Jan 2001 03:35:06 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: current@freebsd.org Cc: marcel@freebsd.org Subject: new gensetdefs breaks booting Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The new gensetdefs gives unbootable kernels on i386's. They hang before printing anything. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 9: 5:57 2001 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 D7E8F37B6A1 for ; Sun, 28 Jan 2001 09:05:39 -0800 (PST) Received: (from uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id RAA18797 for current@freebsd.org; Sun, 28 Jan 2001 17:05:38 GMT (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] (eccles [194.32.164.2]) by seagoon.gid.co.uk (8.9.3/8.9.3) with ESMTP id QAA20309 for ; Sun, 28 Jan 2001 16:48:16 GMT (envelope-from rb@gid.co.uk) X-Sender: rb@194.32.164.1 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 28 Jan 2001 16:48:15 +0000 To: Jake Burkholder From: Bob Bishop Subject: Re: panic on last night's kernel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Jake Burkholder wrote: >Could you try this patch and let me know if it changes anything? > >Index: i386/isa/intr_machdep.c >=================================================================== >RCS file: /home/ncvs/src/sys/i386/isa/intr_machdep.c,v >retrieving revision 1.46 >diff -u -r1.46 intr_machdep.c >--- i386/isa/intr_machdep.c 2001/01/21 19:25:06 1.46 >+++ i386/isa/intr_machdep.c 2001/01/27 18:51:12 >@@ -704,6 +704,7 @@ > if ((idesc->ih_flags & INTR_FAST) == 0) { > mtx_enter(&sched_lock, MTX_SPIN); > if (ithd->it_proc->p_stat == SWAIT) { >+ ithd->it_proc->p_intr_nesting_level = 0; > ithd->it_proc->p_stat = SRUN; > setrunqueue(ithd->it_proc); > /* Yup, that does it. Thanks! -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 11:28:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from gypsy.vrac.iastate.edu (gypsy.vrac.iastate.edu [129.186.232.122]) by hub.freebsd.org (Postfix) with ESMTP id 5728C37B69B for ; Sun, 28 Jan 2001 11:28:04 -0800 (PST) Received: from tomservo.vrac.iastate.edu (tomservo.vrac.iastate.edu [129.186.232.121]) by gypsy.vrac.iastate.edu (Postfix) with ESMTP id 96ABA1A; Sun, 28 Jan 2001 13:28:04 -0600 (CST) Received: from tomservo.vrac.iastate.edu (localhost [127.0.0.1]) by tomservo.vrac.iastate.edu (Postfix) with ESMTP id 297935E30; Sun, 28 Jan 2001 13:28:03 -0600 (CST) To: Jeroen Ruigrok van der Werven Cc: freebsd-current@FreeBSD.ORG Subject: Re: Fixed: LyX 1.1.5.2 dumping core In-reply-to: "Sun, 28 Jan 2001 12:52:34 +0100." <20010128125234.A68355@lucifer.bart.nl> Date: Sun, 28 Jan 2001 13:28:03 -0600 From: Patrick Hartling Message-Id: <20010128192803.297935E30@tomservo.vrac.iastate.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeroen Ruigrok van der Werven wrote: } -On [20010127 22:30], Patrick Hartling (patrick@137.org) wrote: } >Making a symlink from /usr/lib/libc.so.5 to /usr/lib/libc.so.3 seems to } >have fixed my LyX problems. I'm guessing libc.so.5 and libc.so.3 were } >causing conflicts, especially with the recent changes to libc, but I'm no } >expert. Whatever the case, I can get back to work on my thesis now. :) } } Have you tried recompiling LyX with the new libc? I did try that initially, but the problems persisted until I made the symlink and relinked the executable. } That should normally clear any problems. } } I suspect from what you said above, that when you do ldd `which lyx` it } will report lyx being linked against libc.so.3, but for some reason is } trying to use the higher version libc. ldd was telling me that it had both libc.so.3 and libc.so.5 which seemed very bad to me. When I recomipled LyX to see if that would fix things, I noticed that ld was giving a warning about libc.so.3 and libc.so.5 potentially conflicting. It hadn't ever been a problem before, but it doesn't seem like the safest arrangment. With the symlink in place, ldd reports that only libc.so.5 is being used, and everything seems to be okay. -Patrick Patrick L. Hartling | Research Assistant, VRAC patrick@137.org | 2624 Howe Hall -- (515)294-4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 11:46:38 2001 Delivered-To: freebsd-current@freebsd.org Received: from dsl.MexComUSA.net (adsl-63-200-120-86.dsl.mtry01.pacbell.net [63.200.120.86]) by hub.freebsd.org (Postfix) with ESMTP id C44A437B404 for ; Sun, 28 Jan 2001 11:46:19 -0800 (PST) Received: (from root@localhost) by dsl.MexComUSA.net (8.11.2/8.11.1) id f0SJfcK04798 for Current@FreeBSD.Org; Sun, 28 Jan 2001 11:41:38 -0800 (PST) (envelope-from eculp@EnContacto.Net) Received: from 63.200.120.86 ( [63.200.120.86]) as user eculp@EnContacto.Net by Mail.MexComUSA.net with HTTP; Sun, 28 Jan 2001 11:41:36 -0800 Message-ID: <980710896.3a7475f0a9f7b@Mail.MexComUSA.net> Date: Sun, 28 Jan 2001 11:41:36 -0800 From: Edwin Culp To: Current@FreeBSD.Org Subject: Interesting "man" error. Current today. MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 2.3.6-cvs Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With this morning's make world, I get the following error with man. I've checked six different machines with slightly different cvsup and build times and using different cvsup locations. They all coincide. FreeBSD dsl.mexcomusa.net 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Fri Jan 19 07:52:22 PST 2001 root@dsl.mexcomusa.net:/usr/src/sys/compile/WIC i386 compiled this morning: /usr/local/etc/openldap # ls -l /usr/bin/man -r-sr-xr-x 1 man wheel 27768 Jan 28 07:11 /usr/bin/man ERROR: /usr/local/etc/openldap # man slapd.conf Formatting page, please wait...Syntax error: "(" unexpected (expecting ")") Failed. pclose: Device not configured Formatting page, please wait...Syntax error: "(" unexpected (expecting ")") Failed. pclose: Undefined error: 0 Syntax error: "(" unexpected (expecting ")") Error executing formatting or display command. system command exited with status 512 No manual entry for slapd.conf I also have a problem with my laptop that built world at the same time. Because of the above, I decided to restart it to put the kernel and programs in sync to see if that was causing the error. Murphy caught me in the act and my laptop now hangs on boot:-( I haven't tried rebooting any of the other machines, yet.) I get: FreeGSD/i386 bootstra loader, Revision 1.0 (root@laptop.mexcomusa.net, Sun Jan 28 05:29:35 PST 2001) /boot/kernel/kernel text=0x19af2a data=0x44224+0x1ba34 syms=[0x4+0x2b6c0+0x4+0x3344c] I had to right this and bring it to the office to send the email so there could be errors in the typing. I now have my laptop cvsuping again with an old kernel. Thanks, ed -- EnContacto.Net - InternetSalon.Org - CafeMania.Net -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 12:14: 7 2001 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 511EB37B404 for ; Sun, 28 Jan 2001 12:13:47 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id VAA07135; Sun, 28 Jan 2001 21:13:39 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Bruce Evans Cc: current@freebsd.org Subject: Re: man broken References: From: Dag-Erling Smorgrav Date: 28 Jan 2001 21:13:38 +0100 In-Reply-To: Bruce Evans's message of "Sun, 28 Jan 2001 20:02:13 +1100 (EST)" Message-ID: Lines: 8 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans writes: > man(1) was broken in rev.1.39 of src/gnu/usr.bin/man/man/man.c: Argh! I didn't test it with LC_* unset. Will fix. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 12:36:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from hera.drwilco.net (10dyn120.dh.casema.net [212.64.31.120]) by hub.freebsd.org (Postfix) with ESMTP id 1904437B400 for ; Sun, 28 Jan 2001 12:36:31 -0800 (PST) Received: from ceres.drwilco.nl (ceres.drwilco.net [10.1.1.19]) by hera.drwilco.net (8.11.1/8.11.1) with ESMTP id f0SKwbb02465; Sun, 28 Jan 2001 21:58:39 +0100 (CET) (envelope-from drwilco@drwilco.nl) Message-Id: <4.3.2.7.0.20010128213415.00c70a20@mail.bsdchicks.com> X-Sender: lists@mail.bsdchicks.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sun, 28 Jan 2001 21:37:04 +0100 To: Edwin Culp , Current@FreeBSD.ORG From: "Rogier R. Mulhuijzen" Subject: Re: Hanging on boot (Was: Interesting "man" error. Current today.) In-Reply-To: <980710896.3a7475f0a9f7b@Mail.MexComUSA.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I also have a problem with my laptop that built world at the same >time. Because >of the above, I decided to restart it to put the kernel and programs in >sync to >see if that was causing the error. Murphy caught me in the act and my laptop >now hangs on boot:-( I haven't tried rebooting any of the other machines, >yet.) Yup same here, boot hangs. Module preloading gives garbage for module names. I was able to boot with /boot/kernel.old/kernel though... Trying to find more clues. DocWilco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 13: 1:23 2001 Delivered-To: freebsd-current@freebsd.org Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (Postfix) with ESMTP id C119537B400; Sun, 28 Jan 2001 13:01:06 -0800 (PST) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel1.hp.com (Postfix) with ESMTP id 2BAF7208E; Sun, 28 Jan 2001 13:01:06 -0800 (PST) Received: from cup.hp.com (p1000181.nsr.hp.com [15.109.0.181]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id NAA13720; Sun, 28 Jan 2001 13:01:05 -0800 (PST) Message-ID: <3A74888F.E00F7161@cup.hp.com> Date: Sun, 28 Jan 2001 13:01:03 -0800 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Bruce Evans Cc: current@FreeBSD.ORG, marcel@FreeBSD.ORG Subject: Re: new gensetdefs breaks booting References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > > The new gensetdefs gives unbootable kernels on i386's. They hang before > printing anything. I verified that the output of gensetdefs.pl is identical to that of gensetdefs(1). Does the kernel boot if gensetdefs(1) is used? -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 13:11: 6 2001 Delivered-To: freebsd-current@freebsd.org Received: from io.yi.org (cr66388-a.rchrd1.on.wave.home.com [24.114.165.24]) by hub.freebsd.org (Postfix) with ESMTP id 4350737B698; Sun, 28 Jan 2001 13:10:47 -0800 (PST) Received: from io.yi.org (localhost.gvcl1.bc.wave.home.com [127.0.0.1]) by io.yi.org (Postfix) with ESMTP id 10981BA8A; Sun, 28 Jan 2001 16:10:46 -0500 (EST) X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.3 To: Marcel Moolenaar Cc: Bruce Evans , current@FreeBSD.ORG, marcel@FreeBSD.ORG Subject: Re: new gensetdefs breaks booting In-Reply-To: Message from Marcel Moolenaar of "Sun, 28 Jan 2001 13:01:03 PST." <3A74888F.E00F7161@cup.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 28 Jan 2001 16:10:46 -0500 From: Jake Burkholder Message-Id: <20010128211046.10981BA8A@io.yi.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Bruce Evans wrote: > > > > The new gensetdefs gives unbootable kernels on i386's. They hang before > > printing anything. > > I verified that the output of gensetdefs.pl is identical to that of > gensetdefs(1). Does the kernel boot if gensetdefs(1) is used? > Its not identical here, gensetdefs.pl uses .quad for the size of the linker set (?), which should be .long for x86. Also, I'm not sure if the calculation for pointer size is correct, all the numbers seemed 3 times too big in setdefs.h. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 13:41:20 2001 Delivered-To: freebsd-current@freebsd.org Received: from blizzard.sabbo.net (ns.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id F048B37B402; Sun, 28 Jan 2001 13:40:56 -0800 (PST) Received: from vic.sabbo.net (root@vic.sabbo.net [193.193.218.112]) by blizzard.sabbo.net (8.10.1/8.10.1) with ESMTP id f0SLerT32303; Sun, 28 Jan 2001 23:40:54 +0200 Received: (from max@localhost) by vic.sabbo.net (8.11.1/8.9.3) id f0SLeva12734; Sun, 28 Jan 2001 23:40:57 +0200 (EET) (envelope-from sobomax@FreeBSD.org) From: Maxim Sobolev Message-Id: <200101282140.f0SLeva12734@vic.sabbo.net> Subject: Segfaults and dmesg To: current@freebsd.org Date: Sun, 28 Jan 2001 23:40:57 +0200 (EET) Cc: phk@freebsd.org X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I wonder if anyone noticed that segfault messages are no longer appended to the dmesg output. For me it looks like serious POLA violation. The following script highlights the problem: --- kaboom.sh --- #!/bin/sh dmesg -a > dmesg.old cat > tst.c << EOF #include main () { return strlen((char *)NULL); } EOF cc tst.c -o tst ./tst dmesg -a > dmesg.new diff -d dmesg.old dmesg.new rm -f dmesg.old tst.c tst dmesg.new ------------------ On a 4-STABLE system: max@vic$ ./kaboom.sh ./kaboom.sh: line 7: 12717 Segmentation fault ./tst 345a345 > pid 12717 (tst), uid 1001: exited on signal 11 max@vic$ Whereas on a 5-CURRENT: max@notebook$ ./kaboom.sh ./kaboom.sh: line 7: 333 Segmentation fault ./tst max@notebook$ Please fix. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 13:55:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (Postfix) with ESMTP id 6F3B237B402; Sun, 28 Jan 2001 13:55:12 -0800 (PST) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel1.hp.com (Postfix) with ESMTP id E51AC1CD6; Sun, 28 Jan 2001 13:55:11 -0800 (PST) Received: from cup.hp.com (p1000181.nsr.hp.com [15.109.0.181]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id NAA14592; Sun, 28 Jan 2001 13:55:10 -0800 (PST) Message-ID: <3A74953E.C0FA47CB@cup.hp.com> Date: Sun, 28 Jan 2001 13:55:10 -0800 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Jake Burkholder Cc: Bruce Evans , current@FreeBSD.ORG, marcel@FreeBSD.ORG Subject: Re: new gensetdefs breaks booting References: <20010128211046.10981BA8A@io.yi.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jake Burkholder wrote: > > > Bruce Evans wrote: > > > > > > The new gensetdefs gives unbootable kernels on i386's. They hang before > > > printing anything. > > > > I verified that the output of gensetdefs.pl is identical to that of > > gensetdefs(1). Does the kernel boot if gensetdefs(1) is used? > > > > Its not identical here, gensetdefs.pl uses .quad for the size of > the linker set (?), which should be .long for x86. Also, I'm not > sure if the calculation for pointer size is correct, all the numbers > seemed 3 times too big in setdefs.h. Ok, thanks. The commit has been reverted for all platforms except ia64. I think I messed up my testing, but may easily have committed the wrong gensetdefs.pl. I'll check it out... -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 15:14:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id CF40737B404 for ; Sun, 28 Jan 2001 15:14:23 -0800 (PST) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id f0SNCMI18779 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Mon, 29 Jan 2001 00:12:24 +0100 (MET) Received: from cicely5.cicely.de (cicely5.cicely.de [fec0:0:0:104::5]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id f0SNCYA29566 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified NO); Mon, 29 Jan 2001 00:12:36 +0100 (CET) Received: (from ticso@localhost) by cicely5.cicely.de (8.11.1/8.11.1) id f0SNCTH49659; Mon, 29 Jan 2001 00:12:29 +0100 (CET) (envelope-from ticso) Date: Mon, 29 Jan 2001 00:12:29 +0100 From: Bernd Walter To: Paul Allenby Cc: "Rogier R. Mulhuijzen" , current@FreeBSD.ORG Subject: Re: sh can't be exec'd Message-ID: <20010129001228.A49531@cicely5.cicely.de> References: <4.3.2.7.0.20010128161923.00c74440@mail.bsdchicks.com> <200101281615.f0SGFlT31423@mamba.cids.org.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200101281615.f0SGFlT31423@mamba.cids.org.za>; from pallenby@mamba.cids.org.za on Sun, Jan 28, 2001 at 06:15:46PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 28, 2001 at 06:15:46PM +0200, Paul Allenby wrote: > "Rogier R. Mulhuijzen wrote:" > > > > > > >For the last week, each kernel built with fresh source code > > >cannot exec sh. I've seen a lot of emails about this, but > > >most were about the "correct" way to rebuild a system. > > >Is this a problem affecting only me? > > > > I haven't had any trouble. > > > > How do you rebuild your system? What is the exact error you get? > > And (at the risk of sounding stupid) what's the output of ls -l /bin/sh? > > > > cd /usr/src/sys/i386/conf;config XXX;cd ../../compile/XXX; make depend; make > > No errors, just the usual prompt for a path to a shell, as if one > had booted single user. > > 526188 sh, without resorting to a fixit disc. You shouldn't update only the kernel. See the Handbook about make world. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 17: 2:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from gw.nectar.com (gw.nectar.com [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id 27F8A37B6A6 for ; Sun, 28 Jan 2001 17:02:29 -0800 (PST) Received: by gw.nectar.com (Postfix, from userid 1001) id 116D319404; Sun, 28 Jan 2001 19:02:28 -0600 (CST) Date: Sun, 28 Jan 2001 19:02:27 -0600 From: "Jacques A. Vidrine" To: Steve O'Hara-Smith Cc: current@freebsd.org Subject: Re: /etc/shells #include syntax support patch Message-ID: <20010128190227.B25222@spawn.nectar.com> References: <20010128101349.2c94539f.steveo@eircom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010128101349.2c94539f.steveo@eircom.net>; from steveo@eircom.net on Sun, Jan 28, 2001 at 10:13:49AM +0100 X-Url: http://www.nectar.com/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 28, 2001 at 10:13:49AM +0100, Steve O'Hara-Smith wrote: > Hi, > > Asbestos suit on, round two. > > The patch below changes getusershell to support a #include syntax > in /etc/shells. I guess this is what I object to. I don't particularly like having a new directive in a configuration file which lots of applications read directly. I would rather that a separate configuration file be read, for example, with a list of shells(5) format files to consult. In current, this could be an optional thing, activated in nsswitch.conf, e.g. make a ports source for shells, and activate it with: shells: files ports or whatever you would like to call the source. -- Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 17: 9:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from mta5.snfc21.pbi.net (mta5.snfc21.pbi.net [206.13.28.241]) by hub.freebsd.org (Postfix) with ESMTP id 7DABC37B6A8 for ; Sun, 28 Jan 2001 17:09:16 -0800 (PST) Received: from zippy.pacbell.net ([207.214.149.219]) by mta5.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0G7W00147GC2QL@mta5.snfc21.pbi.net> for current@freebsd.org; Sun, 28 Jan 2001 17:04:52 -0800 (PST) Received: by zippy.pacbell.net (Postfix, from userid 1000) id 7708317EF; Sun, 28 Jan 2001 17:06:43 -0800 (PST) Date: Sun, 28 Jan 2001 17:06:24 -0800 From: Alex Zepeda Subject: Re: Fixed: LyX 1.1.5.2 dumping core In-reply-to: <20010128192803.297935E30@tomservo.vrac.iastate.edu>; from patrick@137.org on Sun, Jan 28, 2001 at 01:28:03PM -0600 To: Patrick Hartling Message-id: <20010128170624.A1193@zippy.pacbell.net> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <20010128125234.A68355@lucifer.bart.nl> <20010128192803.297935E30@tomservo.vrac.iastate.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 28, 2001 at 01:28:03PM -0600, Patrick Hartling wrote: > ldd was telling me that it had both libc.so.3 and libc.so.5 which seemed > very bad to me. When I recomipled LyX to see if that would fix things, > I noticed that ld was giving a warning about libc.so.3 and libc.so.5 > potentially conflicting. It hadn't ever been a problem before, but it > doesn't seem like the safest arrangment. With the symlink in place, ldd > reports that only libc.so.5 is being used, and everything seems to be > okay. Something that LyX is linking to is depending on libc v3. You should rebuild all of the dependencies, and then rebuild LyX. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 18:54:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from dante.naver.co.id (unknown [202.155.86.83]) by hub.freebsd.org (Postfix) with ESMTP id AEA4537B400 for ; Sun, 28 Jan 2001 18:53:54 -0800 (PST) Received: by dante.naver.co.id (Postfix, from userid 1000) id 0652F53543; Mon, 29 Jan 2001 09:54:04 +0700 (JAVT) Date: Mon, 29 Jan 2001 09:54:03 +0700 From: John Indra To: freebsd-current@freebsd.org Subject: DEVFS newbie... Message-ID: <20010129095403.A89648@naver.co.id> Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Mailer: Mutt 1.2.5i on FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I noticed that DEVFS has been the default in GENERIC kernel. I have been -CURRENT tracker for the past couple of months and things like DEVFS is still new to me. Thus, a couple of questions arise and I am very glad if someone want to explain it to me, or maybe point to docs that I should read. 1. Say I want to use DEVFS, what should I change? /etc/fstab? Should I nuke the current /dev? 2. If something change to the source tree's MAKEDEV, what should I do? Thanks... /john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 19:18:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id DC8AB37B402 for ; Sun, 28 Jan 2001 19:18:28 -0800 (PST) Received: (qmail 26663 invoked by uid 0); 29 Jan 2001 03:17:51 -0000 Received: from pd950884f.dip.t-dialin.net (HELO speedy.gsinet) (217.80.136.79) by mail.gmx.net (mp004-rz3) with SMTP; 29 Jan 2001 03:17:51 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id VAA07479 for current@FreeBSD.ORG; Sun, 28 Jan 2001 21:32:23 +0100 Date: Sun, 28 Jan 2001 21:32:23 +0100 From: Gerhard Sittig To: current@FreeBSD.ORG Subject: Re: sh can't be exec'd Message-ID: <20010128213223.V253@speedy.gsinet> Mail-Followup-To: current@FreeBSD.ORG References: <4.3.2.7.0.20010128161923.00c74440@mail.bsdchicks.com> <200101281615.f0SGFlT31423@mamba.cids.org.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200101281615.f0SGFlT31423@mamba.cids.org.za>; from pallenby@mamba.cids.org.za on Sun, Jan 28, 2001 at 06:15:46PM +0200 Organization: System Defenestrators Inc. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 28, 2001 at 18:15 +0200, Paul Allenby wrote: > "Rogier R. Mulhuijzen wrote:" > > > > >For the last week, each kernel built with fresh source code ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > >cannot exec sh. I've seen a lot of emails about this, but > > >most were about the "correct" way to rebuild a system. > > >Is this a problem affecting only me? Dumb question: You do build both world and kernel when you update your sources? And if it fails the way you do it, you fall back to the official method described in UPDATING before yelling "it's broken"? There must be a reason when a thousand answers are about how to update a system (and not just one part of it). > > I haven't had any trouble. > > > > How do you rebuild your system? What is the exact error you > > get? And (at the risk of sounding stupid) what's the output > > of ls -l /bin/sh? > > cd /usr/src/sys/i386/conf;config XXX;cd ../../compile/XXX; make depend; make I miss the "install" target here, unless it's so obvious for you that you don't mention it. Just like "buildworld" and "installworld". Maybe you should try one safe run of the suggested form. Cutting corners is not very efficient when problems keep you from simply running your new system. :) virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 20:52: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 1E26337B402 for ; Sun, 28 Jan 2001 20:51:47 -0800 (PST) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id PAA28199; Mon, 29 Jan 2001 15:51:06 +1100 (EDT) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37641) with ESMTP id <01JZHGWF7BJ4I8S1NY@cim.alcatel.com.au>; Mon, 29 Jan 2001 15:50:23 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.1/8.11.1) id f0T4oY565590; Mon, 29 Jan 2001 15:50:34 +1100 (EST envelope-from jeremyp) Content-return: prohibited Date: Mon, 29 Jan 2001 15:50:33 +1100 From: Peter Jeremy Subject: Re: kernel threading: the first steps [patch] In-reply-to: <200101270833.AAA75738@InterJet.elischer.org>; from julian@elischer.org on Sat, Jan 27, 2001 at 12:33:23AM -0800 To: Root Dude Cc: current@FreeBSD.ORG Mail-followup-to: Root Dude , current@FreeBSD.ORG Message-id: <20010129155033.K52423@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <200101270833.AAA75738@InterJet.elischer.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2001-Jan-27 00:33:23 -0800, Root Dude wrote: >I've broken the proc structure into 4 structures. Leaving aside the issue of whether or your efforts were a waste of time, I have some comments on the ordering of fields. Since the fields are being re-arranged anyway, I'd like to suggest that the implementation characteristics be taken into account. I'm mainly thinking of padding between fields here. A second, far less important issue is the interaction between field order and code size on the IA32. Given that most structure references are base+offset, there's an extra 3-byte overhead in accessing fields more than 127 bytes from the pointer - there's no direct speed penalty except on the 80386, but there is an indirect penalty for larger code (ie bigger cache footprint). This suggests that fields with a high static reference count should be towards the front of structures. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 20:54:18 2001 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 451DC37B400 for ; Sun, 28 Jan 2001 20:53:58 -0800 (PST) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.11.1/8.11.0) with ESMTP id f0T4roq13148; Sun, 28 Jan 2001 23:53:50 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200101290453.f0T4roq13148@whizzo.transsys.com> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: "Jacques A. Vidrine" Cc: "Steve O'Hara-Smith" , current@FreeBSD.ORG X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: /etc/shells #include syntax support patch References: <20010128101349.2c94539f.steveo@eircom.net> <20010128190227.B25222@spawn.nectar.com> In-reply-to: Your message of "Sun, 28 Jan 2001 19:02:27 CST." <20010128190227.B25222@spawn.nectar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 28 Jan 2001 23:53:50 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, Jan 28, 2001 at 10:13:49AM +0100, Steve O'Hara-Smith wrote: > > Hi, > > > > Asbestos suit on, round two. > > > > The patch below changes getusershell to support a #include syntax > > in /etc/shells. > > I guess this is what I object to. I don't particularly like having a > new directive in a configuration file which lots of applications read > directly. > > I would rather that a separate configuration file be read, for example, > with a list of shells(5) format files to consult. > > In current, this could be an optional thing, activated in nsswitch.conf, > e.g. make a ports source for shells, and activate it with: > shells: files ports > > or whatever you would like to call the source. Does this capability really need to exist (e.g., supporting many files)? It would seem like the additional complexity would be not what you want for what's essentially a security policy mechansim. Who gets to own these included files? What should their permissions be allowed to be? It doesn't seem unreasonable to have a single file with a list of allowable shells. Is this #include capability going to be added for other files that ports modify such as /etc/master.passwd and /etc/group? I dunno; maybe it's just me, but this really seems like a solution way out of proportion to the "problem" louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 21:16:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from lodge.guild.ab.ca (lodge.guild.ab.ca [209.91.118.66]) by hub.freebsd.org (Postfix) with ESMTP id BD80237B69B for ; Sun, 28 Jan 2001 21:16:03 -0800 (PST) Received: (from davidc@localhost) by lodge.guild.ab.ca (8.11.1/8.11.1) id f0T5G2V88524 for freebsd-current@freebsd.org; Sun, 28 Jan 2001 22:16:02 -0700 (MST) (envelope-from davidc) Date: Sun, 28 Jan 2001 22:16:02 -0700 From: Chad David To: freebsd-current@freebsd.org Subject: stange console problem Message-ID: <20010128221602.A88482@lodge.guild.ab.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On a current from last Sunday I recompiled a new kernel with just makeoptions DEBUG=-g and options DDB added to GENERIC and when I boot I see the first few spins of the loader booting the kernel and then all video output stops. After the boot finishs I get a login prompt but no keyboard response or video after that. I am able to ssh into the box, and all seems well from the "inside". If I recompile GENERIC it works just fine. Here is a dmesg, I noticed a few things but nothing I know how to fix.. Chad Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #2: Sun Jan 28 23:17:40 MST 2001 davidc@whisper.acns.ab.ca:/usr/src/sys/compile/DEBUG Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (367.50-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x660 Stepping = 0 Features=0x183f9ff real memory = 134152192 (131008K bytes) avail memory = 125595648 (122652K bytes) Preloaded elf kernel "kernel" at 0xc04e7000. Pentium Pro MTRR support enabled WARNING: Driver mistake: destroy_dev on 154/0 Using $PIR table, 6 entries at 0xc00fded0 apm0: on motherboard apm0: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xe000-0xe01f at device 7.2 on pci0 pci_cfgintr_virgin: using routable PCI-only interrupt 11 pci_cfgintr: 0:7 INTD routed to irq 11 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: at 7.3 (no driver attached) xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xe400-0xe47f mem 0xe5000000-0xe500007f irq 11 at device 9.0 on pci0 xl0: Ethernet address: 00:10:4b:6e:0a:87 miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x0> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sio0: <16550A-compatible COM port> at port 0x3f8-0x407 irq 4 on isa0 sio0: type 16550A fdc0: at port 0x3f2-0x3f5,0x3f7 irq 6 drq 2 on isa0 ppc0: at port 0x378-0x387 irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sio1: <16550A-compatible COM port> at port 0x2f8-0x307 irq 3 on isa0 sio1: type 16550A sbc0: at port 0x220-0x22f,0x331-0x332,0x388-0x38b irq 5 drq 1,5 on isa0 pcm0: on sbc0 xl0 XXX: driver didn't initialize queue mtx lp0 XXX: driver didn't initialize queue mtx gif0 XXX: driver didn't initialize queue mtx gif1 XXX: driver didn't initialize queue mtx gif2 XXX: driver didn't initialize queue mtx gif3 XXX: driver didn't initialize queue mtx lo0 XXX: driver didn't initialize queue mtx ppp0 XXX: driver didn't initialize queue mtx faith0 XXX: driver didn't initialize queue mtx ad0: 6187MB [13410/15/63] at ata0-master UDMA33 Mounting root from ufs:/dev/ad0s4a To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 22:16:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 4932037B404 for ; Sun, 28 Jan 2001 22:16:33 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f0T6GFK18336; Mon, 29 Jan 2001 07:16:17 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: John Indra Cc: freebsd-current@FreeBSD.ORG Subject: Re: DEVFS newbie... In-Reply-To: Your message of "Mon, 29 Jan 2001 09:54:03 +0700." <20010129095403.A89648@naver.co.id> Date: Mon, 29 Jan 2001 07:16:15 +0100 Message-ID: <18334.980748975@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010129095403.A89648@naver.co.id>, John Indra writes: >I noticed that DEVFS has been the default in GENERIC kernel. I have been >-CURRENT tracker for the past couple of months and things like DEVFS is >still new to me. Thus, a couple of questions arise and I am very glad if >someone want to explain it to me, or maybe point to docs that I should read. > >1. Say I want to use DEVFS, what should I change? Nothing. Just add DEVFS to your kernel config file. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 22:20:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from moby.geekhouse.net (moby.geekhouse.net [64.81.6.36]) by hub.freebsd.org (Postfix) with ESMTP id 730B537B698 for ; Sun, 28 Jan 2001 22:19:53 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp150.geekhouse.net [192.168.1.150]) by moby.geekhouse.net (8.11.0/8.9.3) with ESMTP id f0T6Jmc03424; Sun, 28 Jan 2001 22:19:50 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010129095403.A89648@naver.co.id> Date: Sun, 28 Jan 2001 22:19:34 -0800 (PST) From: John Baldwin To: John Indra Subject: RE: DEVFS newbie... Cc: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 29-Jan-01 John Indra wrote: > I noticed that DEVFS has been the default in GENERIC kernel. I have been > -CURRENT tracker for the past couple of months and things like DEVFS is > still new to me. Thus, a couple of questions arise and I am very glad if > someone want to explain it to me, or maybe point to docs that I should read. > > 1. Say I want to use DEVFS, what should I change? /etc/fstab? Should I nuke > the current /dev? Just put it in your kernel config, init(8) will mount it for you automagically. > 2. If something change to the source tree's MAKEDEV, what should I do? Nothing. With DEVFS, each driver in the kernel creates its own entries automatically, so MAKEDEV isn't used. > Thanks... > > /john -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/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 Sun Jan 28 22:20:19 2001 Delivered-To: freebsd-current@freebsd.org Received: from moby.geekhouse.net (moby.geekhouse.net [64.81.6.36]) by hub.freebsd.org (Postfix) with ESMTP id D1B6837B402 for ; Sun, 28 Jan 2001 22:19:47 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp150.geekhouse.net [192.168.1.150]) by moby.geekhouse.net (8.11.0/8.9.3) with ESMTP id f0T6Jhc03420; Sun, 28 Jan 2001 22:19:43 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200101290453.f0T4roq13148@whizzo.transsys.com> Date: Sun, 28 Jan 2001 22:19:29 -0800 (PST) From: John Baldwin To: "Louis A. Mamakos" Subject: Re: /etc/shells #include syntax support patch Cc: current@FreeBSD.org, "Steve O'Hara-Smith" , "Jacques A. Vidrine" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 29-Jan-01 Louis A. Mamakos wrote: >> On Sun, Jan 28, 2001 at 10:13:49AM +0100, Steve O'Hara-Smith wrote: >> > Hi, >> > >> > Asbestos suit on, round two. >> > >> > The patch below changes getusershell to support a #include syntax >> > in /etc/shells. >> >> I guess this is what I object to. I don't particularly like having a >> new directive in a configuration file which lots of applications read >> directly. >> >> I would rather that a separate configuration file be read, for example, >> with a list of shells(5) format files to consult. >> >> In current, this could be an optional thing, activated in nsswitch.conf, >> e.g. make a ports source for shells, and activate it with: >> shells: files ports >> >> or whatever you would like to call the source. > > Does this capability really need to exist (e.g., supporting many files)? It > would seem like the additional complexity would be not what you want for > what's > essentially a security policy mechansim. Who gets to own these included > files? > What should their permissions be allowed to be? > > It doesn't seem unreasonable to have a single file with a list of allowable > shells. > > Is this #include capability going to be added for other files that ports > modify such as /etc/master.passwd and /etc/group? > > I dunno; maybe it's just me, but this really seems like a solution way out > of proportion to the "problem" People whine about the problem though, so having no solution doesn't help either. Since #include is syntatically a comment, it shouldn't mess up other programs, though the idea is that they will all use the API in libc and not be reading the file themselves. However, I do think that doing it through nsswitch might be the best solution. > louie -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/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 Sun Jan 28 22:23:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43]) by hub.freebsd.org (Postfix) with ESMTP id 6C13737B400 for ; Sun, 28 Jan 2001 22:23:12 -0800 (PST) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.11.2/8.11.1) id f0T6N5d17700; Mon, 29 Jan 2001 12:23:05 +0600 (NOVT) (envelope-from nnd) Date: Mon, 29 Jan 2001 12:23:05 +0600 (NOVT) Message-Id: <200101290623.f0T6N5d17700@wint.itfs.nsk.su> From: nnd@mail.nsk.ru To: current@FreeBSD.ORG Subject: Re: cvs commit: src/usr.sbin/named Makefile In-Reply-To: <200101282321.f0SNL0f51582@freefall.freebsd.org> User-Agent: tin/1.5.8-20010108 ("Paradise Regained") (UNIX) (FreeBSD/5.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200101282321.f0SNL0f51582@freefall.freebsd.org> you wrote: > asmodai 2001/01/28 15:21:00 PST > > Modified files: > usr.sbin/named Makefile > Log: > Add static dependency on libisc.a to get isc_movefile() on which named > now depends. This keeps named the same as before the import, that is: only > linking against libc dynamically, at a little space increase, which might > be due to the source code changes anyway. Very neglectable space > difference. > > Some people might dub it a hack. It will do for now at least. > > Revision Changes Path > 1.26 +12 -1 src/usr.sbin/named/Makefile It seems to me that the same kind of libisc dependency must be provided for 'libexec/named-xfer', because it now stops buildworld with the 'isc_movefile' unresolved message. At the same time it seems to me that now 'lib/libbind' contains many files/functions which are also present in the newly created 'lib/libisc'. Is it right ? N.Dudorov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 22:39:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from kbtfw.kubota.co.jp (kbtfw.kubota.co.jp [133.253.102.202]) by hub.freebsd.org (Postfix) with ESMTP id F3C5B37B400; Sun, 28 Jan 2001 22:39:15 -0800 (PST) Received: by kbtfw.kubota.co.jp; id PAA14346; Mon, 29 Jan 2001 15:39:09 +0900 (JST) Received: from unknown(133.253.122.4) by kbtfw.kubota.co.jp via smap (V5.0) id xma013290; Mon, 29 Jan 01 15:38:14 +0900 Received: from ktkl129.tk.kubota.co.jp (IDENT:root@kbtgk.eto.kubota.co.jp [133.253.122.3]) by kbtmk.eto.kubota.co.jp (8.11.1/8.11.1) with ESMTP id f0T6cDT86398; Mon, 29 Jan 2001 15:38:13 +0900 (JST) Received: from jkpc11.tk.kubota.co.jp by ktkl129.tk.kubota.co.jp (8.6.13+2.4W/3.4W3-97053016) id PAA10915; Mon, 29 Jan 2001 15:36:08 +0900 Received: from localhost (localhost.tk.kubota.co.jp [127.0.0.1]) by jkpc11.tk.kubota.co.jp (8.11.2/3.7W-02/21/99) with ESMTP id f0T6bDU94091; Mon, 29 Jan 2001 15:37:13 +0900 (JST) To: Jeroen Ruigrok van der Werven Cc: current@FreeBSD.org Subject: buildworld failed with named-xfer. X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010129153713U.haro@kubota.co.jp> Date: Mon, 29 Jan 2001 15:37:13 +0900 From: Munehiro Matsuda X-Dispatcher: imput version 20000228(IM140) Lines: 44 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Buildworld failed with following error: cc -O -pipe -I/usr/src/libexec/named-xfer/../../contrib/bind/port/freebsd/include -I/usr/src/libexec/named-xfer/../../contrib/bind/bin/named -I/usr/src/libexec/named-xfer/../../contrib/bind/include -I. -o named-xfer named-xfer.o db_glue.o ns_glue.o tmp_version.o /usr/obj/usr/src/libexec/named-xfer/../../lib/libbind/libbind.a named-xfer.o: In function `main': named-xfer.o(.text+0xe4a): undefined reference to `isc_movefile' named-xfer.o(.text+0xede): undefined reference to `isc_movefile' named-xfer.o(.text+0xf54): undefined reference to `isc_movefile' /usr/obj/usr/src/libexec/named-xfer/../../lib/libbind/libbind.a(logging.o)(.text+0x98): undefined reference to `isc_movefile' /usr/obj/usr/src/libexec/named-xfer/../../lib/libbind/libbind.a(logging.o)(.text+0xca): undefined reference to `isc_movefile' *** Error code 1 Stop in /usr/src/libexec/named-xfer. Following patch seems to work. --- Makefile.ctm Wed May 24 03:17:07 2000 +++ Makefile Mon Jan 29 15:34:18 2001 @@ -12,4 +12,14 @@ named-xfer.c db_glue.c ns_glue.c tmp_version.c MAN8= named-xfer.8 +.if exists(${.OBJDIR}/../../lib/libisc) +LIBISCDIR:= ${.OBJDIR}/../../lib/libisc +.else +LIBISCDIR!= cd ${.CURDIR}/../../lib/libisc; make -V .OBJDIR +.endif +LIBISC:= ${LIBISCDIR}/libisc.a + +DPADD+= ${LIBISC} +LDADD+= ${LIBISC} + .include Thanks, Haro =------------------------------------------------------------------------------ _ _ Munehiro (haro) Matsuda -|- /_\ |_|_| Business Incubation Dept., Kubota Corp. /|\ |_| |_|_| 1-3 Nihonbashi-Muromachi 3-Chome Chuo-ku Tokyo 103-8310, Japan Tel: +81-3-3245-3318 Fax: +81-3-3245-3315 Email: haro@kubota.co.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 22:50:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp.wanadoo.nl (smtp.wanadoo.nl [194.134.193.6]) by hub.freebsd.org (Postfix) with ESMTP id EBB3337B400; Sun, 28 Jan 2001 22:50:19 -0800 (PST) Received: from ams-gw.sohara.org (p0776.vcu.wanadoo.nl [194.134.202.13]) by smtp.wanadoo.nl (8.9.3/8.9.3) with SMTP id HAA03756; Mon, 29 Jan 2001 07:50:14 +0100 (MET) Date: Mon, 29 Jan 2001 07:50:10 +0100 From: "Steve O'Hara-Smith" To: John Baldwin Cc: louie@TransSys.COM, current@FreeBSD.org, n@nectar.com Subject: Re: /etc/shells #include syntax support patch Message-Id: <20010129075010.67f1c27f.steveo@eircom.net> In-Reply-To: References: <200101290453.f0T4roq13148@whizzo.transsys.com> X-Mailer: Sylpheed version 0.4.9 (GTK+ 1.2.8; FreeBSD 4.2-STABLE; i386) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 28 Jan 2001 22:19:29 -0800 (PST) John Baldwin wrote: JB> People whine about the problem though, so having no solution doesn't JB> help either. Since #include is syntatically a comment, it shouldn't JB> mess up other programs, though the idea is that they will all use the JB> API in libc and not be reading the file themselves. However, I do JB> think that doing it through nsswitch might be the best solution. Everything in the tree uses the API apart from adduser.perl. Do many ports use /etc/shells ? On the security issue, I rather like the idea that a none root port administrator is possible, this doesn't really need multiple shells files though so nsswitch works for me. I can't set it up though (no -current box). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 22:52:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp.wanadoo.nl (smtp.wanadoo.nl [194.134.193.6]) by hub.freebsd.org (Postfix) with ESMTP id 930A537B400 for ; Sun, 28 Jan 2001 22:52:20 -0800 (PST) Received: from ams-gw.sohara.org (p0776.vcu.wanadoo.nl [194.134.202.13]) by smtp.wanadoo.nl (8.9.3/8.9.3) with SMTP id HAA03844; Mon, 29 Jan 2001 07:52:17 +0100 (MET) Date: Mon, 29 Jan 2001 07:52:13 +0100 From: "Steve O'Hara-Smith" To: "Louis A. Mamakos" Cc: n@nectar.com, current@FreeBSD.ORG Subject: Re: /etc/shells #include syntax support patch Message-Id: <20010129075213.75982219.steveo@eircom.net> In-Reply-To: <200101290453.f0T4roq13148@whizzo.transsys.com> References: <20010128101349.2c94539f.steveo@eircom.net> <20010128190227.B25222@spawn.nectar.com> <200101290453.f0T4roq13148@whizzo.transsys.com> X-Mailer: Sylpheed version 0.4.9 (GTK+ 1.2.8; FreeBSD 4.2-STABLE; i386) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 28 Jan 2001 23:53:50 -0500 "Louis A. Mamakos" wrote: LM> It doesn't seem unreasonable to have a single file with a list of allowable LM> shells. One thing - it is kind of cute having the allowable shells match the mounted shells. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 23:18:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from dante.naver.co.id (unknown [202.155.86.83]) by hub.freebsd.org (Postfix) with ESMTP id 5495237B6AD for ; Sun, 28 Jan 2001 23:18:25 -0800 (PST) Received: by dante.naver.co.id (Postfix, from userid 1000) id 2E8AF53547; Mon, 29 Jan 2001 14:19:06 +0700 (JAVT) Date: Mon, 29 Jan 2001 14:19:05 +0700 From: John Indra To: freebsd-current@freebsd.org Subject: buildworld failed Message-ID: <20010129141905.A14464@naver.co.id> Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Mailer: Mutt 1.2.5i on FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Latest -CURRENT died with this error messages: -- /usr/src/lib/libc_r/uthread/uthread_aio_suspend.c: In function `_aio_suspend': /usr/src/lib/libc_r/uthread/uthread_aio_suspend.c:45: warning: passing arg 1 of `__sys_aio_suspend' discards qualifiers from pointer target type /usr/src/lib/libc_r/uthread/uthread_aio_suspend.c:45: incompatible type for argument 3 of `__sys_aio_suspend' *** Error code 1 cc -fpic -DPIC -O -pipe -mcpu=i686 -march=i686 -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/include -DPTHREAD_KERNEL -D_THREAD_SAFE -I/usr/src/lib/libc_r/uthread -I/usr/src/lib/libc_r/../../include -D_LOCK_DEBUG -D_PTHREADS_INVARIANTS -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libc_r/uthread/uthread_attr_getdetachstate.c -o uthread_attr_getdetachstate.So /usr/src/lib/libc_r/uthread/uthread_aio_suspend.c: In function `_aio_suspend': /usr/src/lib/libc_r/uthread/uthread_aio_suspend.c:45: warning: passing arg 1 of `__sys_aio_suspend' discards qualifiers from pointer target type /usr/src/lib/libc_r/uthread/uthread_aio_suspend.c:45: incompatible type for argument 3 of `__sys_aio_suspend' *** Error code 1 2 errors *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error -- /john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 23:54:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 53C7237B69F for ; Sun, 28 Jan 2001 23:54:41 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f0T7sKP61966; Sun, 28 Jan 2001 23:54:20 -0800 (PST) (envelope-from dillon) Date: Sun, 28 Jan 2001 23:54:20 -0800 (PST) From: Matt Dillon Message-Id: <200101290754.f0T7sKP61966@earth.backplane.com> To: "Louis A. Mamakos" Cc: "Jacques A. Vidrine" , "Steve O'Hara-Smith" , current@FreeBSD.ORG Subject: Re: /etc/shells #include syntax support patch References: <20010128101349.2c94539f.steveo@eircom.net> <20010128190227.B25222@spawn.nectar.com> <200101290453.f0T4roq13148@whizzo.transsys.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG /etc/shells is such a simple file, I don't see much of point in polluting it. There is not much of difference having a port install: target edit /etc/shells verses editing /usr/local/etc/shells. It should just edit /etc/shells. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 28 23:59:29 2001 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.ninth-circle.org (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id A228E37B6A0 for ; Sun, 28 Jan 2001 23:59:00 -0800 (PST) Received: (from asmodai@localhost) by lucifer.ninth-circle.org (8.11.1/8.11.0) id f0T7wnC84082; Mon, 29 Jan 2001 08:58:49 +0100 (CET) (envelope-from asmodai) Date: Mon, 29 Jan 2001 08:58:49 +0100 From: Jeroen Ruigrok van der Werven To: Munehiro Matsuda Cc: current@FreeBSD.ORG Subject: Re: buildworld failed with named-xfer. Message-ID: <20010129085849.A83703@lucifer.bart.nl> References: <20010129153713U.haro@kubota.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010129153713U.haro@kubota.co.jp>; from haro@kubota.co.jp on Mon, Jan 29, 2001 at 03:37:13PM +0900 Organisation: VIA Net.Works The Netherlands Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Konnichiwa wa MATSUDA-san, -On [20010129 07:40], Munehiro Matsuda (haro@kubota.co.jp) wrote: >Buildworld failed with following error: > >cc -O -pipe -I/usr/src/libexec/named-xfer/../../contrib/bind/port/freebsd/include -I/usr/src/libexec/named-xfer/../../contrib/bind/bin/named -I/usr/src/libexec/named-xfer/../../contrib/bind/include -I. -o named-xfer named-xfer.o db_glue.o ns_glue.o tmp_version.o /usr/obj/usr/src/libexec/named-xfer/../../lib/libbind/libbind.a >named-xfer.o: In function `main': >named-xfer.o(.text+0xe4a): undefined reference to `isc_movefile' >named-xfer.o(.text+0xede): undefined reference to `isc_movefile' >named-xfer.o(.text+0xf54): undefined reference to `isc_movefile' >/usr/obj/usr/src/libexec/named-xfer/../../lib/libbind/libbind.a(logging.o)(.text+0x98): undefined reference to `isc_movefile' >/usr/obj/usr/src/libexec/named-xfer/../../lib/libbind/libbind.a(logging.o)(.text+0xca): undefined reference to `isc_movefile' >*** Error code 1 Thanks, applied the patch. The BIND import was kind of rushed due to the security stuff being released today. -- Jeroen Ruigrok van der Werven VIA Net.Works The Netherlands BSD: Technical excellence at its best Network- and systemadministrator D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 Misery loves company... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 29 0: 1:23 2001 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.ninth-circle.org (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 8D2DA37B6A0 for ; Mon, 29 Jan 2001 00:01:05 -0800 (PST) Received: (from asmodai@localhost) by lucifer.ninth-circle.org (8.11.1/8.11.0) id f0T811984154; Mon, 29 Jan 2001 09:01:01 +0100 (CET) (envelope-from asmodai) Date: Mon, 29 Jan 2001 09:01:01 +0100 From: Jeroen Ruigrok van der Werven To: nnd@mail.nsk.ru Cc: current@FreeBSD.ORG Subject: Re: cvs commit: src/usr.sbin/named Makefile Message-ID: <20010129090101.B83703@lucifer.bart.nl> References: <200101282321.f0SNL0f51582@freefall.freebsd.org> <200101290623.f0T6N5d17700@wint.itfs.nsk.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101290623.f0T6N5d17700@wint.itfs.nsk.su>; from nnd@mail.nsk.ru on Mon, Jan 29, 2001 at 12:23:05PM +0600 Organisation: VIA Net.Works The Netherlands Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20010129 07:25], nnd@mail.nsk.ru (nnd@mail.nsk.ru) wrote: >In article <200101282321.f0SNL0f51582@freefall.freebsd.org> you wrote: > It seems to me that the same kind of libisc dependency >must be provided for 'libexec/named-xfer', because it now stops >buildworld with the 'isc_movefile' unresolved message. Correct, fixed. > At the same time it seems to me that now 'lib/libbind' >contains many files/functions which are also present in the >newly created 'lib/libisc'. Is it right ? Could be. I have to look at that. I focused on getting the import done very quickly due to some security stuff coming out later. 3- and 4-STABLE will follow sooner than normal after I've done my make worlds and other tests on them today/tomorrow. -- Jeroen Ruigrok van der Werven VIA Net.Works The Netherlands BSD: Technical excellence at its best Network- and systemadministrator D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 Misery loves company... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 29 2: 0:21 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.mobilix.dk (unknown [194.234.53.85]) by hub.freebsd.org (Postfix) with ESMTP id 31E2937B6A4 for ; Mon, 29 Jan 2001 02:00:03 -0800 (PST) Received: from lflat.vas.mobilix.dk (gw-vas.mobilix.net [212.97.206.4]) by mail.mobilix.dk (8.8.7/8.8.7) with ESMTP id MAA14640; Mon, 29 Jan 2001 12:03:09 +0100 Received: by lflat.vas.mobilix.dk (Postfix, from userid 72044) id 8278EA89D; Mon, 29 Jan 2001 10:59:30 +0100 (CET) Date: Mon, 29 Jan 2001 10:59:30 +0100 From: Vadim Belman To: freebsd-current@freebsd.org Cc: "Louis A. Mamakos" Subject: Re: /etc/shells #include syntax support patch Message-ID: <20010129105930.C62046@lflat.vas.mobilix.dk> Mail-Followup-To: Vadim Belman , freebsd-current@freebsd.org, "Louis A. Mamakos" References: <20010128101349.2c94539f.steveo@eircom.net> <20010128190227.B25222@spawn.nectar.com> <200101290453.f0T4roq13148@whizzo.transsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200101290453.f0T4roq13148@whizzo.transsys.com>; from louie@TransSys.COM on Sun, Jan 28, 2001 at 11:53:50PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 28, 2001 at 11:53:50PM -0500, Louis A. Mamakos wrote: > Does this capability really need to exist (e.g., supporting many files)? It > would seem like the additional complexity would be not what you want for what's > essentially a security policy mechansim. Who gets to own these included files? > What should their permissions be allowed to be? > > It doesn't seem unreasonable to have a single file with a list of allowable > shells. It does if you think of mergemaster, for example. With any upgrade it consider /etc/shells as changed and prompts for replacing/merging/etc. -- /Voland Vadim Belman E-mail: voland@lflat.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 29 2:50: 6 2001 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 37F5B37B402 for ; Mon, 29 Jan 2001 02:49:44 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id LAA10291; Mon, 29 Jan 2001 11:49:36 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Vadim Belman Cc: freebsd-current@FreeBSD.ORG, "Louis A. Mamakos" Subject: Re: /etc/shells #include syntax support patch References: <20010128101349.2c94539f.steveo@eircom.net> <20010128190227.B25222@spawn.nectar.com> <200101290453.f0T4roq13148@whizzo.transsys.com> <20010129105930.C62046@lflat.vas.mobilix.dk> From: Dag-Erling Smorgrav Date: 29 Jan 2001 11:49:36 +0100 In-Reply-To: Vadim Belman's message of "Mon, 29 Jan 2001 10:59:30 +0100" Message-ID: Lines: 15 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Vadim Belman writes: > On Sun, Jan 28, 2001 at 11:53:50PM -0500, Louis A. Mamakos wrote: > > It doesn't seem unreasonable to have a single file with a list of allowable > > shells. > It does if you think of mergemaster, for example. With any upgrade > it consider /etc/shells as changed and prompts for replacing/merging/etc. No. Mergemaster doesn't care about the contents of the file, only about its $FreeBSD$ tag. As long as this stays the same, it'll leave the file alone. If you remove the $FreeBSD$ tag in the installed file or someone commits to src/etc/shells, mergemaster will prompt you. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 29 6:17:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id C91DF37B69E; Mon, 29 Jan 2001 06:17:37 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id BAA27550; Tue, 30 Jan 2001 01:17:34 +1100 Date: Tue, 30 Jan 2001 01:17:18 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: current@freebsd.org Cc: peter@freebsd.org Subject: config(8) broken Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Config now removes almost all headers: Removing stale header: apm.h Removing stale header: opt_userconfig.h Removing stale header: opt_syscons.h Removing stale header: opt_cpu.h Removing stale header: opt_clock.h ... make: don't know how to make opt_global.h(continuing) make: don't know how to make opt_user_ldt.h(continuing) make: don't know how to make opt_posix.h(continuing) make: don't know how to make opt_nfs.h(continuing) make: don't know how to make opt_bootp.h(continuing) ... This is starting from compile directory populated by a previous version of config. Starting from scratch, config seems to work for the first run. The second run complains about all headers, deletes them all, and doesn't create any. The third run seems to work... Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 29 7: 5:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from gypsy.vrac.iastate.edu (gypsy.vrac.iastate.edu [129.186.232.122]) by hub.freebsd.org (Postfix) with ESMTP id 6C4B537B6A0 for ; Mon, 29 Jan 2001 07:05:35 -0800 (PST) Received: from tomservo.vrac.iastate.edu (tomservo.vrac.iastate.edu [129.186.232.121]) by gypsy.vrac.iastate.edu (Postfix) with ESMTP id 74417C8 for ; Mon, 29 Jan 2001 09:05:35 -0600 (CST) Received: from tomservo.vrac.iastate.edu (localhost [127.0.0.1]) by tomservo.vrac.iastate.edu (Postfix) with ESMTP id 8A4E35E30 for ; Mon, 29 Jan 2001 09:05:34 -0600 (CST) To: freebsd-current@freebsd.org Subject: Re: Fixed: LyX 1.1.5.2 dumping core In-reply-to: "Sun, 28 Jan 2001 17:06:24 PST." <20010128170624.A1193@zippy.pacbell.net> Date: Mon, 29 Jan 2001 09:05:34 -0600 From: Patrick Hartling Message-Id: <20010129150534.8A4E35E30@tomservo.vrac.iastate.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alex Zepeda wrote: } On Sun, Jan 28, 2001 at 01:28:03PM -0600, Patrick Hartling wrote: } } > ldd was telling me that it had both libc.so.3 and libc.so.5 which seemed } > very bad to me. When I recomipled LyX to see if that would fix things, } > I noticed that ld was giving a warning about libc.so.3 and libc.so.5 } > potentially conflicting. It hadn't ever been a problem before, but it } > doesn't seem like the safest arrangment. With the symlink in place, ldd } > reports that only libc.so.5 is being used, and everything seems to be } > okay. } } Something that LyX is linking to is depending on libc v3. You should } rebuild all of the dependencies, and then rebuild LyX. Yes, I think it's the xforms library which is distributed only in binary form. All of the ports I build myself are linking to libc.so.4 (they were built before the version number was bumped) or to libc.so.5. The xforms website doesn't seem to have anything built for newer versions of FreeBSD. I just have to be patient while the LyX developers work on moving away from xforms to Motif or GTK+ or anything better. -Patrick Patrick L. Hartling | Research Assistant, VRAC patrick@137.org | 2624 Howe Hall -- (515)294-4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 29 7: 6:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from virtual-voodoo.com (virtual-voodoo.com [204.120.165.254]) by hub.freebsd.org (Postfix) with ESMTP id 4ED2537B6A3; Mon, 29 Jan 2001 07:06:08 -0800 (PST) Received: (from steve@localhost) by virtual-voodoo.com (8.11.2/8.11.1) id f0TF65a60475; Mon, 29 Jan 2001 10:06:05 -0500 (EST) (envelope-from steve) Date: Mon, 29 Jan 2001 10:06:05 -0500 From: Steve Ames To: John Baldwin Cc: John Indra , freebsd-current@FreeBSD.ORG Subject: Re: DEVFS newbie... Message-ID: <20010129100605.A30329@virtual-voodoo.com> References: <20010129095403.A89648@naver.co.id> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.ORG on Sun, Jan 28, 2001 at 10:19:34PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 28, 2001 at 10:19:34PM -0800, John Baldwin wrote: > > On 29-Jan-01 John Indra wrote: > > 2. If something change to the source tree's MAKEDEV, what should I do? > > Nothing. With DEVFS, each driver in the kernel creates its own > entries automatically, so MAKEDEV isn't used. Hrm... what about some custom entries or symlinks I may have? (/dev/cdrom for instance) -Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 29 7:10:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 863B537B6A3; Mon, 29 Jan 2001 07:10:22 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f0TFAOK21848; Mon, 29 Jan 2001 16:10:24 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Steve Ames Cc: John Baldwin , John Indra , freebsd-current@FreeBSD.ORG Subject: Re: DEVFS newbie... In-Reply-To: Your message of "Mon, 29 Jan 2001 10:06:05 EST." <20010129100605.A30329@virtual-voodoo.com> Date: Mon, 29 Jan 2001 16:10:24 +0100 Message-ID: <21846.980781024@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010129100605.A30329@virtual-voodoo.com>, Steve Ames writes: >On Sun, Jan 28, 2001 at 10:19:34PM -0800, John Baldwin wrote: >> >> On 29-Jan-01 John Indra wrote: >> > 2. If something change to the source tree's MAKEDEV, what should I do? >> >> Nothing. With DEVFS, each driver in the kernel creates its own >> entries automatically, so MAKEDEV isn't used. > >Hrm... what about some custom entries or symlinks I may have? >(/dev/cdrom for instance) You can create symlinks in /dev, you cannot mknod there. Create your symlinks in /etc/rc.devfs -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 29 7:27:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id 2E8E937B6B3 for ; Mon, 29 Jan 2001 07:27:24 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f0TFRK452905; Mon, 29 Jan 2001 07:27:21 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200101291527.f0TFRK452905@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Bruce Evans Cc: current@freebsd.org Subject: Re: config(8) broken In-Reply-To: Date: Mon, 29 Jan 2001 07:27:20 -0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > Config now removes almost all headers: > > Removing stale header: apm.h > Removing stale header: opt_userconfig.h > Removing stale header: opt_syscons.h > Removing stale header: opt_cpu.h > Removing stale header: opt_clock.h > ... > make: don't know how to make opt_global.h(continuing) > make: don't know how to make opt_user_ldt.h(continuing) > make: don't know how to make opt_posix.h(continuing) > make: don't know how to make opt_nfs.h(continuing) > make: don't know how to make opt_bootp.h(continuing) > ... > > This is starting from compile directory populated by a previous version > of config. Starting from scratch, config seems to work for the first > run. The second run complains about all headers, deletes them all, and > doesn't create any. The third run seems to work... > > Bruce What are the chances that you did this on a mount -o noatime file system? Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 29 7:45:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 354A737B69C for ; Mon, 29 Jan 2001 07:45:39 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id CAA31601; Tue, 30 Jan 2001 02:45:34 +1100 Date: Tue, 30 Jan 2001 02:45:21 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Peter Wemm Cc: current@freebsd.org Subject: Re: config(8) broken In-Reply-To: <200101291527.f0TFRK452905@mobile.wemm.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 Mon, 29 Jan 2001, Peter Wemm wrote: > Bruce Evans wrote: > > Config now removes almost all headers: > > ... > > This is starting from compile directory populated by a previous version > > of config. Starting from scratch, config seems to work for the first > > run. The second run complains about all headers, deletes them all, and > > doesn't create any. The third run seems to work... > > What are the chances that you did this on a mount -o noatime file system? Very high :-). I'm surprised the bug doesn't affect fast machines, since config doesn't seem to sleep for >= 1 second to ensure that the atimes advance with the standard mount options. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 29 8:21:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id 5497437B69E for ; Mon, 29 Jan 2001 08:21:07 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f0TGL4453408; Mon, 29 Jan 2001 08:21:04 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200101291621.f0TGL4453408@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Bruce Evans Cc: current@freebsd.org Subject: Re: config(8) broken In-Reply-To: Date: Mon, 29 Jan 2001 08:21:04 -0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > On Mon, 29 Jan 2001, Peter Wemm wrote: > > > Bruce Evans wrote: > > > Config now removes almost all headers: > > > ... > > > This is starting from compile directory populated by a previous version > > > of config. Starting from scratch, config seems to work for the first > > > run. The second run complains about all headers, deletes them all, and > > > doesn't create any. The third run seems to work... > > > > What are the chances that you did this on a mount -o noatime file system? > > Very high :-). Heh. :-) > I'm surprised the bug doesn't affect fast machines, since config doesn't > seem to sleep for >= 1 second to ensure that the atimes advance with > the standard mount options. I was primarily testing it on a dual P3-733 w/ 1G ram which was running config nearly instantly. I never saw this problem until I tested it on a fresh machine that (by sheer chance) happened to be running noatime (it was a laptop). For what it's worth, I did roll the start time back by one second to give a bit more comfort - getting rid of the trays isn't all that critical. For UFS at least, we seem to update the atime instantly but schedule writeback to the inode "whenever". 148# date ; ls -lutT foo1 ; cat foo1 ; ls -lutT foo1; date Mon Jan 29 08:18:02 PST 2001 -rw-r--r-- 1 root wheel 4 Jan 29 08:16:25 2001 foo1 foo -rw-r--r-- 1 root wheel 4 Jan 29 08:18:02 2001 foo1 Mon Jan 29 08:18:02 PST 2001 This is all within the same second "tick" and the atime change was visible. > Bruce Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 29 8:31:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 6F0BB37B402 for ; Mon, 29 Jan 2001 08:31:34 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id LAA34977; Mon, 29 Jan 2001 11:31:32 -0500 (EST) (envelope-from wollman) Date: Mon, 29 Jan 2001 11:31:32 -0500 (EST) From: Garrett Wollman Message-Id: <200101291631.LAA34977@khavrinen.lcs.mit.edu> To: "Jacques A. Vidrine" Cc: "Steve O'Hara-Smith" , current@FreeBSD.ORG Subject: Re: /etc/shells #include syntax support patch In-Reply-To: <20010128190227.B25222@spawn.nectar.com> References: <20010128101349.2c94539f.steveo@eircom.net> <20010128190227.B25222@spawn.nectar.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > I would rather that a separate configuration file be read, for example, > with a list of shells(5) format files to consult. I would rather have a single file, located in a directory intended for configuration files. Perhaps we could call it ``/etc/shells'' which seems to be popular. There is no inherent virtue in having (some subset of) configuration files on every partition. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 29 8:34:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from gw.nectar.com (gw.nectar.com [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id 7E37637B400 for ; Mon, 29 Jan 2001 08:34:25 -0800 (PST) Received: from hamlet.nectar.com (hamlet.nectar.com [10.0.1.102]) by gw.nectar.com (Postfix) with ESMTP id 8DCA1193E5; Mon, 29 Jan 2001 10:34:24 -0600 (CST) Received: (from nectar@localhost) by hamlet.nectar.com (8.11.1/8.9.3) id f0TGYOS05672; Mon, 29 Jan 2001 10:34:24 -0600 (CST) (envelope-from nectar@spawn.nectar.com) Date: Mon, 29 Jan 2001 10:34:24 -0600 From: "Jacques A. Vidrine" To: Garrett Wollman Cc: "Steve O'Hara-Smith" , current@FreeBSD.ORG Subject: Re: /etc/shells #include syntax support patch Message-ID: <20010129103424.A65461@hamlet.nectar.com> References: <20010128101349.2c94539f.steveo@eircom.net> <20010128190227.B25222@spawn.nectar.com> <200101291631.LAA34977@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101291631.LAA34977@khavrinen.lcs.mit.edu>; from wollman@khavrinen.lcs.mit.edu on Mon, Jan 29, 2001 at 11:31:32AM -0500 X-Url: http://www.nectar.com/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 29, 2001 at 11:31:32AM -0500, Garrett Wollman wrote: > < said: > > I would rather that a separate configuration file be read, for example, > > with a list of shells(5) format files to consult. > > I would rather have a single file, located in a directory intended for > configuration files. Perhaps we could call it ``/etc/shells'' which > seems to be popular. > > There is no inherent virtue in having (some subset of) configuration > files on every partition. Actually I agree: I don't think anything needs to change. But, if a `feature' such as this _does_ go in, I don't want it to mean that there is a `new' format for `/etc/shells'. -- Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 29 9:16: 6 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 7E5FD37B404 for ; Mon, 29 Jan 2001 09:15:45 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id JAA06230; Mon, 29 Jan 2001 09:15:36 -0800 Date: Mon, 29 Jan 2001 09:15:37 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Peter Wemm Cc: Bruce Evans , current@FreeBSD.ORG Subject: Re: config(8) broken In-Reply-To: <200101291621.f0TGL4453408@mobile.wemm.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 *groan* I'm having trouble believing that *config* of all things is now dependent on time to avoid bugs... This is *one* for the books.... On Mon, 29 Jan 2001, Peter Wemm wrote: > Bruce Evans wrote: > > On Mon, 29 Jan 2001, Peter Wemm wrote: > > > > > Bruce Evans wrote: > > > > Config now removes almost all headers: > > > > ... > > > > This is starting from compile directory populated by a previous version > > > > of config. Starting from scratch, config seems to work for the first > > > > run. The second run complains about all headers, deletes them all, and > > > > doesn't create any. The third run seems to work... > > > > > > What are the chances that you did this on a mount -o noatime file system? > > > > Very high :-). > > Heh. :-) > > > I'm surprised the bug doesn't affect fast machines, since config doesn't > > seem to sleep for >= 1 second to ensure that the atimes advance with > > the standard mount options. > > I was primarily testing it on a dual P3-733 w/ 1G ram which was running > config nearly instantly. I never saw this problem until I tested it > on a fresh machine that (by sheer chance) happened to be running noatime (it > was a laptop). For what it's worth, I did roll the start time back by one > second to give a bit more comfort - getting rid of the trays isn't all that > critical. > > For UFS at least, we seem to update the atime instantly but schedule > writeback to the inode "whenever". > > 148# date ; ls -lutT foo1 ; cat foo1 ; ls -lutT foo1; date > Mon Jan 29 08:18:02 PST 2001 > -rw-r--r-- 1 root wheel 4 Jan 29 08:16:25 2001 foo1 > foo > -rw-r--r-- 1 root wheel 4 Jan 29 08:18:02 2001 foo1 > Mon Jan 29 08:18:02 PST 2001 > > This is all within the same second "tick" and the atime change was visible. > > > Bruce > > > Cheers, > -Peter > -- > Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au > "All of this is for nothing if we don't go to the stars" - JMS/B5 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 29 9:46:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp03.mrf.mail.rcn.net (smtp03.mrf.mail.rcn.net [207.172.4.62]) by hub.freebsd.org (Postfix) with ESMTP id 3D8DD37B402 for ; Mon, 29 Jan 2001 09:46:28 -0800 (PST) Received: from 66-44-89-167.s548.tnt1.lnhva.md.dialup.rcn.com ([66.44.89.167] helo=eviplist.com) by smtp03.mrf.mail.rcn.net with smtp (Exim 3.16 #5) id 14NINn-000567-00 for current@freebsd.org; Mon, 29 Jan 2001 12:46:27 -0500 From: "eVIPlist.com" To: Subject: Mime-Version: 1.0 Content-Type: text/html; charset="ISO-8859-1" Date: Mon, 29 Jan 2001 12:45:23 -0500 Content-Transfer-Encoding: 8bit Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 8
 
 


You are invited to become a VIP member of www.eVIPlist.com, the "Robb Report" of urban events. Where membership certainly has it's privileges. This exclusive list is  "opt-in" only and you will not receive any further correspondence from eVIPlist.com if you do not register.

At www.eVIPlist.com  you can find the hottest parties and special events going on in your city and around country. This week we have a special feature on the hottest parties and special events at NBA All-Star Weekend 2001 in Washington, DC. In addition we offer you news, reviews and interviews on some of the biggest "movers and shakers" in urban America.  

If you enjoy www.eVIPlist.com  please feel free to forward the site to all co-workers, family, frats/soros and friends. Thank you for your time.

Respectfully yours,
eVIPlist Staff
info@eVIPlist.com 

"Providing progressive entertainment for progressive people"


To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 29 9:58:21 2001 Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id 1974A37B400 for ; Mon, 29 Jan 2001 09:58:02 -0800 (PST) Received: from dual.pozo.com (dual.pozo.com [216.101.162.51]) by pozo.com (8.11.2/8.11.2) with ESMTP id f0THw1w25597 for ; Mon, 29 Jan 2001 09:58:01 -0800 (PST) (envelope-from null@pozo.com) Message-Id: <5.0.2.1.2.20010129095217.00a6a858@pozo.com> X-Sender: null@pozo.com X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Mon, 29 Jan 2001 09:58:01 -0800 To: current@FreeBSD.ORG From: Manfred Antar Subject: libc_r broken Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG libc_r won't compile since changes made last night. (libc_r)504}make cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/include -DPTHREAD_KERNEL -D_THREAD_SAFE -I/usr/src/lib/libc_r/uthread -I/usr/src/lib/libc_r/../../include -D_LOCK_DEBUG -D_PTHREADS_INVARIANTS -c /usr/src/lib/libc_r/uthread/uthread_accept.c -o uthread_accept.o cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/include -DPTHREAD_KERNEL -D_THREAD_SAFE -I/usr/src/lib/libc_r/uthread -I/usr/src/lib/libc_r/../../include -D_LOCK_DEBUG -D_PTHREADS_INVARIANTS -c /usr/src/lib/libc_r/uthread/uthread_aio_suspend.c -o uthread_aio_suspend.o /usr/src/lib/libc_r/uthread/uthread_aio_suspend.c: In function `_aio_suspend': /usr/src/lib/libc_r/uthread/uthread_aio_suspend.c:45: warning: passing arg 1 of `__sys_aio_suspend' discards qualifiers from pointer target type /usr/src/lib/libc_r/uthread/uthread_aio_suspend.c:45: incompatible type for argument 3 of `__sys_aio_suspend' *** Error code 1 Stop in /usr/src/lib/libc_r. This also has other ramifications if you build the new libc from last night and are using a threaded version of perl Kernel build directory is ../../compile/pro2 rm -f *.o *.so *.So *.ko *.s eddep errs kernel.debug kernel linterrs makelinks param.c setdef[01].c setdefs.h tags vers.c vnode_if.c vnode_if.h device_if.c bus_if.c linker_if.c pci_if.c pcib_if.c ppbus_if.c ac97_if.c channel_if.c feeder_if.c mixer_if.c isa_if.c device_if.h bus_if.h linker_if.h pci_if.h pcib_if.h ppbus_if.h ac97_if.h channel_if.h feeder_if.h mixer_if.h isa_if.h aicasm aicasm_gram.c aicasm_scan.c y.tab.h aic7xxx_seq.h aic7xxx_reg.h cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../dev -I../../../include -I../../contrib/dev/acpica/Subsystem/Include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../i386/i386/genassym.c sh ../../kern/genassym.sh genassym.o > assym.s rm -f param.c cp ../../conf/param.c . perl5 ../../kern/vnode_if.pl -h ../../kern/vnode_if.src /usr/libexec/ld-elf.so.1: /usr/lib/libc_r.so.5: Undefined symbol "__sys__exit" *** Error code 1 Stop in /usr/src/sys/compile/pro2. Output from perl -version: (libc_r)506}perl -version This is perl, v5.6.0 built for i386-freebsd-thread (with 1 registered patch, see perl -V for more detail) Copyright 1987-2000, Larry Wall Perl may be copied only under the terms of either the Artistic License or the GNU General Public License, which may be found in the Perl 5.0 source kit. Complete documentation for Perl, including FAQ lists, should be found on this system using `man perl' or `perldoc perl'. If you have access to the Internet, point your browser at http://www.perl.com/, the Perl Home Page. /usr/libexec/ld-elf.so.1: /usr/lib/libc_r.so.5: Undefined symbol "__sys__exit" Manfred ================================== || null@pozo.com || || Ph. (415) 681-6235 || ================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 29 10: 0:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id 791AB37B698 for ; Mon, 29 Jan 2001 10:00:03 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f0THxw454602; Mon, 29 Jan 2001 09:59:58 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200101291759.f0THxw454602@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: mjacob@feral.com Cc: Bruce Evans , current@FreeBSD.ORG Subject: Re: config(8) broken In-Reply-To: Date: Mon, 29 Jan 2001 09:59:58 -0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Jacob wrote: > > *groan* I'm having trouble believing that *config* of all things is now > dependent on time to avoid bugs... This is *one* for the books.... Yep. That's why I disabled it and will replace it with something more robust. In hindsight it was Not A Good Thing. > On Mon, 29 Jan 2001, Peter Wemm wrote: > > > Bruce Evans wrote: > > > On Mon, 29 Jan 2001, Peter Wemm wrote: > > > > > > > Bruce Evans wrote: > > > > > Config now removes almost all headers: > > > > > ... > > > > > This is starting from compile directory populated by a previous versi on > > > > > of config. Starting from scratch, config seems to work for the first > > > > > run. The second run complains about all headers, deletes them all, a nd > > > > > doesn't create any. The third run seems to work... > > > > > > > > What are the chances that you did this on a mount -o noatime file syste m? > > > > > > Very high :-). > > > > Heh. :-) > > > > > I'm surprised the bug doesn't affect fast machines, since config doesn't > > > seem to sleep for >= 1 second to ensure that the atimes advance with > > > the standard mount options. > > > > I was primarily testing it on a dual P3-733 w/ 1G ram which was running > > config nearly instantly. I never saw this problem until I tested it > > on a fresh machine that (by sheer chance) happened to be running noatime (i t > > was a laptop). For what it's worth, I did roll the start time back by one > > second to give a bit more comfort - getting rid of the trays isn't all that > > critical. > > > > For UFS at least, we seem to update the atime instantly but schedule > > writeback to the inode "whenever". > > > > 148# date ; ls -lutT foo1 ; cat foo1 ; ls -lutT foo1; date > > Mon Jan 29 08:18:02 PST 2001 > > -rw-r--r-- 1 root wheel 4 Jan 29 08:16:25 2001 foo1 > > foo > > -rw-r--r-- 1 root wheel 4 Jan 29 08:18:02 2001 foo1 > > Mon Jan 29 08:18:02 PST 2001 > > > > This is all within the same second "tick" and the atime change was visible. > > > > > Bruce > > > > > > Cheers, > > -Peter > > -- > > Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au > > "All of this is for nothing if we don't go to the stars" - JMS/B5 > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 29 10:44:13 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp.wanadoo.nl (smtp.wanadoo.nl [194.134.193.6]) by hub.freebsd.org (Postfix) with ESMTP id 1C48337B783 for ; Mon, 29 Jan 2001 10:43:55 -0800 (PST) Received: from ams-gw.sohara.org (p010.vcu.wanadoo.nl [194.134.200.10]) by smtp.wanadoo.nl (8.9.3/8.9.3) with SMTP id TAA27542; Mon, 29 Jan 2001 19:43:41 +0100 (MET) Date: Mon, 29 Jan 2001 19:43:37 +0100 From: "Steve O'Hara-Smith" To: Garrett Wollman Cc: n@nectar.com, current@FreeBSD.ORG Subject: Re: /etc/shells #include syntax support patch Message-Id: <20010129194337.347ff30d.steveo@eircom.net> In-Reply-To: <200101291631.LAA34977@khavrinen.lcs.mit.edu> References: <20010128101349.2c94539f.steveo@eircom.net> <20010128190227.B25222@spawn.nectar.com> <200101291631.LAA34977@khavrinen.lcs.mit.edu> X-Mailer: Sylpheed version 0.4.9 (GTK+ 1.2.8; FreeBSD 4.2-STABLE; i386) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 29 Jan 2001 11:31:32 -0500 (EST) Garrett Wollman wrote: GW> I would rather have a single file, located in a directory intended for GW> configuration files. Perhaps we could call it ``/etc/shells'' which GW> seems to be popular. As you wish. I have no axe to grind, it was fun and instructive to do, seemed to fit the expressed wishes of some people and I could think of some uses for it. If opinions change you know where to find some code :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 29 10:48:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id BDD7937B8C8 for ; Mon, 29 Jan 2001 10:48:24 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA06743 for ; Mon, 29 Jan 2001 10:48:25 -0800 Date: Mon, 29 Jan 2001 10:48:24 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: current@freebsd.org Subject: just reporting.....fallout from DEVFS... 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 Just reporting.... farrago.feral.com > root vinum mkdir: /dev/vinum: Operation not supported mkdir: /dev/vinum: Operation not supported mkdir: /dev/vinum: Operation not supported mkdir: /dev/vinum: Operation not supported an't create /dev/vinum/Control: No such file or directory Can't create /dev/vinum/control: No such file or directory Can't create /dev/vinum/controld: No such file or directory Can't get vinum config: Bad file descriptor Can't open /dev/vinum/Control: Bad file descriptor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 29 11: 3:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 7BDBA37B699 for ; Mon, 29 Jan 2001 11:03:19 -0800 (PST) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id OAA29015; Mon, 29 Jan 2001 14:02:52 -0500 (EST) Date: Mon, 29 Jan 2001 14:02:52 -0500 (EST) From: Daniel Eischen To: Manfred Antar Cc: current@FreeBSD.ORG Subject: Re: libc_r broken In-Reply-To: <5.0.2.1.2.20010129095217.00a6a858@pozo.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, 29 Jan 2001, Manfred Antar wrote: > libc_r won't compile since changes made last night. > (libc_r)504}make > cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/include -DPTHREAD_KERNEL -D_THREAD_SAFE -I/usr/src/lib/libc_r/uthread -I/usr/src/lib/libc_r/../../include -D_LOCK_DEBUG -D_PTHREADS_INVARIANTS -c /usr/src/lib/libc_r/uthread/uthread_accept.c -o uthread_accept.o > cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/include -DPTHREAD_KERNEL -D_THREAD_SAFE -I/usr/src/lib/libc_r/uthread -I/usr/src/lib/libc_r/../../include -D_LOCK_DEBUG -D_PTHREADS_INVARIANTS -c /usr/src/lib/libc_r/uthread/uthread_aio_suspend.c -o uthread_aio_suspend.o > /usr/src/lib/libc_r/uthread/uthread_aio_suspend.c: In function `_aio_suspend': > /usr/src/lib/libc_r/uthread/uthread_aio_suspend.c:45: warning: passing arg 1 of `__sys_aio_suspend' discards qualifiers from pointer target type > /usr/src/lib/libc_r/uthread/uthread_aio_suspend.c:45: incompatible type for argument 3 of `__sys_aio_suspend' > *** Error code 1 > > Stop in /usr/src/lib/libc_r. Sorry, I committed (I think) the wrong copy of pthread_private.h. I just committed a fix for this. I'm away from my -current box right now, so let me know if this doesn't work. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 29 11:30: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id 0E4F837B699 for ; Mon, 29 Jan 2001 11:29:42 -0800 (PST) Received: from dual.pozo.com (dual.pozo.com [216.101.162.51]) by pozo.com (8.11.2/8.11.2) with ESMTP id f0TJTew28817; Mon, 29 Jan 2001 11:29:40 -0800 (PST) (envelope-from null@pozo.com) Message-Id: <5.0.2.1.2.20010129112853.00a6a9c8@pozo.com> X-Sender: null@pozo.com X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Mon, 29 Jan 2001 11:29:39 -0800 To: Daniel Eischen From: Manfred Antar Subject: Re: libc_r broken Cc: current@FreeBSD.ORG In-Reply-To: References: <5.0.2.1.2.20010129095217.00a6a858@pozo.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 02:02 PM 1/29/2001 -0500, Daniel Eischen wrote: >On Mon, 29 Jan 2001, Manfred Antar wrote: >> libc_r won't compile since changes made last night. >> (libc_r)504}make >> cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/include -DPTHREAD_KERNEL -D_THREAD_SAFE -I/usr/src/lib/libc_r/uthread -I/usr/src/lib/libc_r/../../include -D_LOCK_DEBUG -D_PTHREADS_INVARIANTS -c /usr/src/lib/libc_r/uthread/uthread_accept.c -o uthread_accept.o >> cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/include -DPTHREAD_KERNEL -D_THREAD_SAFE -I/usr/src/lib/libc_r/uthread -I/usr/src/lib/libc_r/../../include -D_LOCK_DEBUG -D_PTHREADS_INVARIANTS -c /usr/src/lib/libc_r/uthread/uthread_aio_suspend.c -o uthread_aio_suspend.o >> /usr/src/lib/libc_r/uthread/uthread_aio_suspend.c: In function `_aio_suspend': >> /usr/src/lib/libc_r/uthread/uthread_aio_suspend.c:45: warning: passing arg 1 of `__sys_aio_suspend' discards qualifiers from pointer target type >> /usr/src/lib/libc_r/uthread/uthread_aio_suspend.c:45: incompatible type for argument 3 of `__sys_aio_suspend' >> *** Error code 1 >> >> Stop in /usr/src/lib/libc_r. > >Sorry, I committed (I think) the wrong copy of pthread_private.h. >I just committed a fix for this. I'm away from my -current box >right now, so let me know if this doesn't work. > >-- >Dan Eischen Dan It works now with the new pthread_private.h. Thanks Manfred ================================== || null@pozo.com || || Ph. (415) 681-6235 || ================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 29 12:57:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.net022.co.yu (mail.net022.co.yu [212.200.44.4]) by hub.freebsd.org (Postfix) with ESMTP id 16E3A37B6A3 for ; Mon, 29 Jan 2001 12:56:31 -0800 (PST) Received: from phy.bg.ac.yu (dial-in07.net022.co.yu [212.200.44.16]) by mail.net022.co.yu (8.8.7/8.8.7) with ESMTP id WAA03606 for ; Mon, 29 Jan 2001 22:56:59 +0100 Message-ID: <3A75D876.762F58FA@phy.bg.ac.yu> Date: Mon, 29 Jan 2001 21:54:14 +0100 From: Rasa Karapandza X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: ctm_rmail Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How can I use Ctm_rmail on mail downloaded using netscape, i f it is not possible how can I retrive sources from mail? Please answer on mi personal mail to. Rasa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 29 17:19:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 7DD4337B400; Mon, 29 Jan 2001 17:19:20 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id BC32A6AC9D; Tue, 30 Jan 2001 11:48:48 +1030 (CST) Date: Tue, 30 Jan 2001 11:48:48 +1030 From: Greg Lehey To: Poul-Henning Kamp Cc: Steve Ames , John Baldwin , John Indra , freebsd-current@FreeBSD.ORG Subject: Re: DEVFS newbie... Message-ID: <20010130114848.B48269@wantadilla.lemis.com> References: <20010129100605.A30329@virtual-voodoo.com> <21846.980781024@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <21846.980781024@critter>; from phk@critter.freebsd.dk on Mon, Jan 29, 2001 at 04:10:24PM +0100 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 29 January 2001 at 16:10:24 +0100, Poul-Henning Kamp wrote: > In message <20010129100605.A30329@virtual-voodoo.com>, Steve Ames writes: >> On Sun, Jan 28, 2001 at 10:19:34PM -0800, John Baldwin wrote: >>> >>> On 29-Jan-01 John Indra wrote: >>>> 2. If something change to the source tree's MAKEDEV, what should I do? >>> >>> Nothing. With DEVFS, each driver in the kernel creates its own >>> entries automatically, so MAKEDEV isn't used. >> >> Hrm... what about some custom entries or symlinks I may have? >> (/dev/cdrom for instance) > > You can create symlinks in /dev, you cannot mknod there. What is the reason for this? How does a program or script know whether the system is running DEVFS or not? Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 29 18:38:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id AB2D237B69D; Mon, 29 Jan 2001 18:38:00 -0800 (PST) Received: by relay.butya.kz (Postfix, from userid 1000) id 520A0286FB; Tue, 30 Jan 2001 08:37:57 +0600 (ALMT) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id 283DF28679; Tue, 30 Jan 2001 08:37:57 +0600 (ALMT) Date: Tue, 30 Jan 2001 08:37:56 +0600 (ALMT) From: Boris Popov To: Greg Lehey Cc: Poul-Henning Kamp , Steve Ames , John Baldwin , John Indra , freebsd-current@FreeBSD.ORG Subject: Re: DEVFS newbie... In-Reply-To: <20010130114848.B48269@wantadilla.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 Tue, 30 Jan 2001, Greg Lehey wrote: > > You can create symlinks in /dev, you cannot mknod there. > > What is the reason for this? How does a program or script know > whether the system is running DEVFS or not? I don't see any good reason why this can't be supported. We may talk about 'broken' devices, etc., but while there any - mknod needs to be supported to make transition more smooth. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 29 18:41:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from junsai.is.akita-u.ac.jp (junsai.is.akita-u.ac.jp [158.215.93.31]) by hub.freebsd.org (Postfix) with ESMTP id CF72437B400 for ; Mon, 29 Jan 2001 18:40:55 -0800 (PST) Received: from lambda.is.akita-u.ac.jp (inukko.is.akita-u.ac.jp [158.215.93.38]) by junsai.is.akita-u.ac.jp (Postfix) with ESMTP id B069AA88E for ; Tue, 30 Jan 2001 11:40:52 +0900 (JST) Date: Tue, 30 Jan 2001 11:40:52 +0900 Message-ID: From: sig@is.akita-u.ac.jp To: freebsd-current@FreeBSD.ORG Subject: Re: /etc/shells #include syntax support patch In-Reply-To: In your message of "29 Jan 2001 11:49:36 +0100" References: <20010128101349.2c94539f.steveo@eircom.net> <20010128190227.B25222@spawn.nectar.com> <200101290453.f0T4roq13148@whizzo.transsys.com> <20010129105930.C62046@lflat.vas.mobilix.dk> User-Agent: Wanderlust/1.1.1 (Purple Rain) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) Emacs/20.7 (i386--freebsd) MULE/4.0 (HANANOEN) MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 29 Jan 2001 11:49:36 +0100, Dag-Erling Smorgrav wrote: > No. Mergemaster doesn't care about the contents of the file, only > about its $FreeBSD$ tag. As long as this stays the same, it'll leave > the file alone. If you remove the $FreeBSD$ tag in the installed file > or someone commits to src/etc/shells, mergemaster will prompt you. I want mergemaster(8) to have a list not to compare. It is not necessary for mergemaster(8) to compare host specific files, for example, /etc/hosts, /etc/printcap and /etc/shells, to their originals in /usr/src. I want that system managers for local hosts can decide which files follow the source and which files do not. -- SASAKI Shigeo Akita Univeristy, Japan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 29 18:52:59 2001 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 1ADA837B404; Mon, 29 Jan 2001 18:52:41 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 826A56AC9D; Tue, 30 Jan 2001 13:22:38 +1030 (CST) Date: Tue, 30 Jan 2001 13:22:38 +1030 From: Greg Lehey To: Boris Popov Cc: Poul-Henning Kamp , Steve Ames , John Baldwin , John Indra , freebsd-current@FreeBSD.ORG Subject: Re: DEVFS newbie... Message-ID: <20010130132238.H48490@wantadilla.lemis.com> References: <20010130114848.B48269@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from bp@butya.kz on Tue, Jan 30, 2001 at 08:37:56AM +0600 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 30 January 2001 at 8:37:56 +0600, Boris Popov wrote: > On Tue, 30 Jan 2001, Greg Lehey wrote: > >>> You can create symlinks in /dev, you cannot mknod there. >> >> What is the reason for this? How does a program or script know >> whether the system is running DEVFS or not? > > I don't see any good reason why this can't be supported. We may > talk about 'broken' devices, etc., but while there any - mknod needs to be > supported to make transition more smooth. I'm assuming that there's a good technical reason for the lack of mknod. It also seems that mkdir doesn't work in devfs. Let's give phk time to wake up and tell us. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 29 20: 2:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (okc-65-26-235-186.mmcable.com [65.26.235.186]) by hub.freebsd.org (Postfix) with SMTP id 6F44B37B400 for ; Mon, 29 Jan 2001 20:02:17 -0800 (PST) Received: (qmail 44232 invoked by uid 100); 30 Jan 2001 04:02:16 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14966.15560.809818.773206@guru.mired.org> Date: Mon, 29 Jan 2001 22:02:16 -0600 (CST) To: sig@is.akita-u.ac.jp Cc: freebsd-current@FreeBSD.ORG Subject: Re: /etc/shells #include syntax support patch In-Reply-To: References: <20010128101349.2c94539f.steveo@eircom.net> <20010128190227.B25222@spawn.nectar.com> <200101290453.f0T4roq13148@whizzo.transsys.com> <20010129105930.C62046@lflat.vas.mobilix.dk> X-Mailer: VM 6.75 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sig@is.akita-u.ac.jp types: > At 29 Jan 2001 11:49:36 +0100, > Dag-Erling Smorgrav wrote: > > No. Mergemaster doesn't care about the contents of the file, only > > about its $FreeBSD$ tag. As long as this stays the same, it'll leave > > the file alone. If you remove the $FreeBSD$ tag in the installed file > > or someone commits to src/etc/shells, mergemaster will prompt you. > I want mergemaster(8) to have a list not to compare. It is not > necessary for mergemaster(8) to compare host specific files, for > example, /etc/hosts, /etc/printcap and /etc/shells, to their > originals in /usr/src. I want that system managers for local > hosts can decide which files follow the source and which files > do not. There was some discussion of about this on -questions (I think it was) a while back, and the author commented on some things he was working on. You might look through those, then nudge him about it. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 29 20:25: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from wilson.acpub.duke.edu (wilson.acpub.duke.edu [152.3.233.69]) by hub.freebsd.org (Postfix) with ESMTP id 51A5637B402 for ; Mon, 29 Jan 2001 20:24:44 -0800 (PST) Received: from bobzilla.adsl.duke.edu (bobzilla.adsl.duke.edu [152.16.67.15]) by wilson.acpub.duke.edu (8.9.3/8.9.3/Duke-5.0.0) with ESMTP id XAA27006; Mon, 29 Jan 2001 23:24:41 -0500 (EST) Received: (from sto@localhost) by bobzilla.adsl.duke.edu (8.11.1/8.11.1) id f0U4OhC47088 for freebsd-current@FreeBSD.ORG; Mon, 29 Jan 2001 23:24:43 -0500 (EST) (envelope-from sto) Date: Mon, 29 Jan 2001 23:24:43 -0500 From: "Sean O'Connell" To: freebsd-current@FreeBSD.ORG Subject: Re: /etc/shells #include syntax support patch Message-ID: <20010129232443.A47058@stat.Duke.EDU> Reply-To: "Sean O'Connell" Mail-Followup-To: Sean O'Connell , freebsd-current@FreeBSD.ORG References: <20010128101349.2c94539f.steveo@eircom.net> <20010128190227.B25222@spawn.nectar.com> <200101290453.f0T4roq13148@whizzo.transsys.com> <20010129105930.C62046@lflat.vas.mobilix.dk> <14966.15560.809818.773206@guru.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <14966.15560.809818.773206@guru.mired.org>; from mwm@mired.org on Mon, Jan 29, 2001 at 10:02:16PM -0600 X-Organization: House of Schmutzli X-Kitties: Bitty Maya CJ Keisha Jacob Hopey X-Hounds: Bob Sheana X-OS-of-Choice: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Meyer stated: : sig@is.akita-u.ac.jp types: : > At 29 Jan 2001 11:49:36 +0100, : > Dag-Erling Smorgrav wrote: : > > No. Mergemaster doesn't care about the contents of the file, only : > > about its $FreeBSD$ tag. As long as this stays the same, it'll leave : > > the file alone. If you remove the $FreeBSD$ tag in the installed file : > > or someone commits to src/etc/shells, mergemaster will prompt you. : > I want mergemaster(8) to have a list not to compare. It is not : > necessary for mergemaster(8) to compare host specific files, for : > example, /etc/hosts, /etc/printcap and /etc/shells, to their : > originals in /usr/src. I want that system managers for local : > hosts can decide which files follow the source and which files : > do not. : : There was some discussion of about this on -questions (I think it was) : a while back, and the author commented on some things he was working : on. You might look through those, then nudge him about it. You have been able to do it with mergemaster for quite some time now. How I do this is to add MM_PRE_COMPARE_SCRIPT='/path/to/my/mmprecompare.sh' to my (and hence root .. I use sudo) .mergemasterrc file. And mmprecompare.sh consists of: <----------------- snip ----------------------------> #! /bin/sh # Create a log file ?? DATE=`date +%Y%m%d` LOGFILE="/tmp/mergemaster-${DATE}" # Ignore these files IGNORE_LIST="/.cshrc \ /etc/mail/aliases \ /etc/csh.cshrc \ /etc/csh.login \ /etc/dhclient.conf \ /etc/group \ /etc/hosts \ /etc/hosts.allow \ /etc/hosts.equiv \ /etc/hosts.lpd \ /etc/mail/sendmail.cf \ /etc/master.passwd \ /etc/namedb/PROTO.localhost.rev \ /etc/namedb/make-localhost \ /etc/namedb/named.conf \ /etc/namedb/named.root \ /etc/newsyslog.conf \ /etc/printcap \ /etc/ssh/ssh_config \ /etc/ssh/sshd_config \ /etc/syslog.conf \ /etc/ttys \ /root/.cshrc \ /root/.login" # # remove w/o complaint the files in question # for IGNORE in ${IGNORE_LIST} do # IDENT1=`ident "${DESTDIR}${IGNORE}" 2>&1` IDENT2=`ident "${TEMPROOT}${IGNORE}" 2>&1` case "${IDENT2}" in *'no id keywords'*) ;; ."${IDENT1}") # No worries ??? # echo " *** ${DESTDIR}${IGNORE} is the same ***" | tee "${LOGFILE}" ;; *) # Ruh-Roh! echo " *** ${DESTDIR}${IGNORE} has changed! ***" | tee "${LOGFILE}" ;; esac # rm "${TEMPROOT}${IGNORE}" done # <----------------- snip ----------------------------> -- 1--------01---------01--------01--------01--------01--------01--------0 Sean O'Connell sean@stat.Duke.EDU To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 29 22:23: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from dante.naver.co.id (unknown [202.155.86.83]) by hub.freebsd.org (Postfix) with ESMTP id 500D337B402; Mon, 29 Jan 2001 22:22:07 -0800 (PST) Received: by dante.naver.co.id (Postfix, from userid 1000) id BD67E53552; Tue, 30 Jan 2001 13:22:00 +0700 (JAVT) Date: Tue, 30 Jan 2001 13:22:00 +0700 From: John Indra To: freebsd-current@freebsd.org Cc: freebsd-stable@freebsd.org Subject: -CURRENT and -STABLE against XFree86 4.0.2 problem Message-ID: <20010130132200.A451@naver.co.id> Mail-Followup-To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="0F1p//8PRICkK4MW" Content-Disposition: inline X-Mailer: Mutt 1.2.5i on FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --0F1p//8PRICkK4MW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi... Forgive me if I'm being such a nuisance. I wish I can help but I don't have the strength to :( I have seen many responses that prove that there is something WRONG with agp support both in -CURRENT and -STABLE if used against XFree86 4.0.2. Here is another one: ----- Forwarded message from Andrea Campi ----- >From: Andrea Campi >To: Stijn Hoop >Cc: John Indra , freebsd-ports@freebsd.org >Subject: Re: -CURRENT and XFree86 4.0.2 problem >Date: Tue, 30 Jan 2001 03:04:30 +0100 > >> > I suspect (from the error log) that this has something to do with Intel 810 >> > chipset and -CURRENT agp module. >> >> FWIW, I have the same problem with a -STABLE from jan. 20th. So the bug is >> probably also in the -STABLE agp module, or else it is XFree86-4.0.2_5 >> (I also blew away /usr/local and /usr/X11R6 before installing it). > >I have been just bitten by the same problem, on -STABLE. Having rebuilt >the world I can not swear it's not a problem in the kernel, but: > >/usr/src/sys/pci/agp.c > >so, either changes to other parts of the system broke agp, or the port >is indeed broken. Quite a few changes to AGP GART configuration went in >from 4.0.1 to 4.0.2, and it's not very clear if they DTRT. > >Anybody has any hint, or at least the knowledge to investigate? If so, >I will send logfiles etc. >Otherwise I will have to try and get everything back to the time when we >had 4.0.1... > >Bye, > Andrea > >-- >Failure is not an option. It comes bundled with your Microsoft product. ----- End forwarded message ----- I have open up a PR, and I think that this problem is critical and must be addressed ASAP. Attached is a log file which I hope can be a help even maybe a little one. FYI Hardware is Intel 815 with latest -CURRENT as I'm writing this mail. Thanks... /john --0F1p//8PRICkK4MW Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="XFree86.0.log" XFree86 Version 4.0.2 / X Window System (protocol Version 11, revision 0, vendor release 6400) Release Date: 18 December 2000 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/FAQ) Operating System: FreeBSD 5.0-CURRENT i386 [ELF] Module Loader present (==) Log file: "/var/log/XFree86.0.log", Time: Tue Jan 30 13:08:04 2001 (==) Using config file: "/etc/X11/XF86Config" Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (??) unknown. (==) ServerLayout "Simple Layout" (**) |-->Screen "Screen 1" (0) (**) | |-->Monitor "My Monitor" (**) | |-->Device "My VGA Card" (**) |-->Input Device "Mouse0" (**) |-->Input Device "Keyboard1" (**) Option "AutoRepeat" "500 30" (WW) Option "XkbCompat" requires an string value (**) Option "XkbRules" "xfree86" (**) XKB: rules: "xfree86" (**) Option "XkbModel" "pc104" (**) XKB: model: "pc104" (**) Option "XkbLayout" "us" (**) XKB: layout: "us" (**) FontPath set to "unix/:7100" (**) RgbPath set to "/usr/X11R6/lib/X11/rgb" (==) ModulePath set to "/usr/X11R6/lib/modules" (II) xf86ReadBIOS(f8000, e80, Buf, 2)-> b4 09 2c fb... (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.3 XFree86 XInput driver : 0.1 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.2 (II) Loader running on freebsd (II) LoadModule: "bitmap" (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.2 (II) Loading font Bitmap (II) LoadModule: "pcidata" (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor="The XFree86 Project" compiled for 4.0.2, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.3 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x8000f948, mode1Res1 = 0x80000000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,1130 card 1043,8027 rev 02 class 06,00,00 hdr 00 (II) PCI: 00:02:0: chip 8086,1132 card 1043,8027 rev 02 class 03,00,00 hdr 00 (II) PCI: 00:1e:0: chip 8086,244e card 0000,0000 rev 01 class 06,04,00 hdr 01 (II) PCI: 00:1f:0: chip 8086,2440 card 0000,0000 rev 01 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,244b card 1043,8027 rev 01 class 01,01,80 hdr 00 (II) PCI: 00:1f:3: chip 8086,2443 card 1043,8027 rev 01 class 0c,05,00 hdr 00 (II) PCI: 01:0a:0: chip 10b7,9200 card 10b7,1000 rev 6c class 02,00,00 hdr 00 (II) PCI: 01:0b:0: chip 1274,5880 card 1274,2000 rev 02 class 04,01,00 hdr 00 (II) PCI: End of PCI scan (II) LoadModule: "scanpci" (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci: vendor="The XFree86 Project" compiled for 4.0.2, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.3 (II) UnloadModule: "scanpci" (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (II) Host-to-PCI bridge: (II) PCI-to-ISA bridge: (II) PCI-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x00 (VGA_EN is cleared) (II) Bus 0 I/O range: [0] -1 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0x00000000 - 0xffffffff (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0x00000000 - 0xffffffff (0x0) MX[B] (II) Bus 1: bridge is at (0:30:0), (0,1,1), BCTRL: 0x06 (VGA_EN is cleared) (II) Bus 1 I/O range: [0] -1 0x0000d000 - 0x0000d0ff (0x100) IX[B] [1] -1 0x0000d400 - 0x0000d4ff (0x100) IX[B] [2] -1 0x0000d800 - 0x0000d8ff (0x100) IX[B] [3] -1 0x0000dc00 - 0x0000dcff (0x100) IX[B] (II) Bus 1 non-prefetchable memory range: [0] -1 0xf6800000 - 0xf6ffffff (0x800000) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 0xf7f00000 - 0xf7ffffff (0x100000) MX[B] (II) Bus -1: bridge is at (0:31:0), (0,-1,0), BCTRL: 0x00 (VGA_EN is cleared) (II) Bus -1 I/O range: (II) Bus -1 non-prefetchable memory range: (II) Bus -1 prefetchable memory range: (--) PCI:*(0:2:0) Intel i815 rev 2, Mem @ 0xf8000000/26, 0xf7000000/19 (II) Addressable bus resource ranges are [0] -1 0x00000000 - 0xffffffff (0x0) MX[B] [1] -1 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) OS-reported resource ranges: [0] -1 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0x00000000 - 0x000001ff (0x200) IX[B]E (II) Active PCI resource ranges: [0] -1 0xf6800000 - 0xf6ffffff (0x800000) MX[B]E [1] -1 0xf7000000 - 0xf707ffff (0x80000) MX[B](B) [2] -1 0xf8000000 - 0xfbffffff (0x4000000) MX[B](B) [3] -1 0x0000d400 - 0x0000d4ff (0x100) IX[B]E [4] -1 0x0000d800 - 0x0000d8ff (0x100) IX[B]E [5] -1 0x0000e800 - 0x0000e8ff (0x100) IX[B]E [6] -1 0x0000b800 - 0x0000b8ff (0x100) IX[B]E (II) Active PCI resource ranges after removing overlaps: [0] -1 0xf6800000 - 0xf6ffffff (0x800000) MX[B]E [1] -1 0xf7000000 - 0xf707ffff (0x80000) MX[B](B) [2] -1 0xf8000000 - 0xfbffffff (0x4000000) MX[B](B) [3] -1 0x0000d400 - 0x0000d4ff (0x100) IX[B]E [4] -1 0x0000d800 - 0x0000d8ff (0x100) IX[B]E [5] -1 0x0000e800 - 0x0000e8ff (0x100) IX[B]E [6] -1 0x0000b800 - 0x0000b8ff (0x100) IX[B]E (II) OS-reported resource ranges after removing overlaps with PCI: [0] -1 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0x00000000 - 0x000001ff (0x200) IX[B]E (II) All system resource ranges: [0] -1 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0xf6800000 - 0xf6ffffff (0x800000) MX[B]E [6] -1 0xf7000000 - 0xf707ffff (0x80000) MX[B](B) [7] -1 0xf8000000 - 0xfbffffff (0x4000000) MX[B](B) [8] -1 0x00000000 - 0x000001ff (0x200) IX[B]E [9] -1 0x0000d400 - 0x0000d4ff (0x100) IX[B]E [10] -1 0x0000d800 - 0x0000d8ff (0x100) IX[B]E [11] -1 0x0000e800 - 0x0000e8ff (0x100) IX[B]E [12] -1 0x0000b800 - 0x0000b8ff (0x100) IX[B]E (II) LoadModule: "dbe" (II) Loading /usr/X11R6/lib/modules/extensions/libdbe.a (II) Module dbe: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.0.0 Module class: XFree86 Server Extension ABI class: XFree86 Server Extension, version 0.1 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: "extmod" (II) Loading /usr/X11R6/lib/modules/extensions/libextmod.a (II) Module extmod: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.0.0 Module class: XFree86 Server Extension ABI class: XFree86 Server Extension, version 0.1 (II) Loading extension SHAPE (II) Loading extension MIT-SUNDRY-NONSTANDARD (II) Loading extension BIG-REQUESTS (II) Loading extension SYNC (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XC-MISC (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-Misc (II) Loading extension DPMS (II) Loading extension FontCache (II) Loading extension TOG-CUP (II) Loading extension Extended-Visual-Information (II) Loading extension XVideo (II) LoadModule: "type1" (II) Loading /usr/X11R6/lib/modules/fonts/libtype1.a (II) Module type1: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.2 (II) Loading font Type1 (II) Loading font CID (II) LoadModule: "freetype" (II) Loading /usr/X11R6/lib/modules/fonts/libfreetype.a (II) Module freetype: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.1.8 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.2 (II) Loading font FreeType (II) LoadModule: "i810" (II) Loading /usr/X11R6/lib/modules/drivers/i810_drv.o (II) Module i810: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.0.0 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.3 (II) LoadModule: "mouse" (II) Loading /usr/X11R6/lib/modules/input/mouse_drv.o (II) Module mouse: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.0.0 Module class: XFree86 XInput Driver ABI class: XFree86 XInput driver, version 0.1 (II) I810: Driver for Intel i810 chipset: i810, i810-dc100, i810e, i815 (II) Primary Device is: PCI 00:02:0 (--) Assigning device section with no busID to primary device (--) Chipset i815 found (II) resource ranges after xf86ClaimFixedResources() call: [0] -1 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0xf6800000 - 0xf6ffffff (0x800000) MX[B]E [6] -1 0xf7000000 - 0xf707ffff (0x80000) MX[B](B) [7] -1 0xf8000000 - 0xfbffffff (0x4000000) MX[B](B) [8] -1 0x00000000 - 0x000001ff (0x200) IX[B]E [9] -1 0x0000d400 - 0x0000d4ff (0x100) IX[B]E [10] -1 0x0000d800 - 0x0000d8ff (0x100) IX[B]E [11] -1 0x0000e800 - 0x0000e8ff (0x100) IX[B]E [12] -1 0x0000b800 - 0x0000b8ff (0x100) IX[B]E (II) resource ranges after probing: [0] -1 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0xf6800000 - 0xf6ffffff (0x800000) MX[B]E [6] -1 0xf7000000 - 0xf707ffff (0x80000) MX[B](B) [7] -1 0xf8000000 - 0xfbffffff (0x4000000) MX[B](B) [8] 0 0x000a0000 - 0x000affff (0x10000) MS[B] [9] 0 0x000b0000 - 0x000b7fff (0x8000) MS[B] [10] 0 0x000b8000 - 0x000bffff (0x8000) MS[B] [11] -1 0x00000000 - 0x000001ff (0x200) IX[B]E [12] -1 0x0000d400 - 0x0000d4ff (0x100) IX[B]E [13] -1 0x0000d800 - 0x0000d8ff (0x100) IX[B]E [14] -1 0x0000e800 - 0x0000e8ff (0x100) IX[B]E [15] -1 0x0000b800 - 0x0000b8ff (0x100) IX[B]E [16] 0 0x000003b0 - 0x000003bb (0xc) IS[B] [17] 0 0x000003c0 - 0x000003df (0x20) IS[B] (II) Setting vga for screen 0. (II) Loading sub module "vgahw" (II) LoadModule: "vgahw" (II) Loading /usr/X11R6/lib/modules/libvgahw.a (II) Module vgahw: vendor="The XFree86 Project" compiled for 4.0.2, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.3 (**) I810(0): Depth 24, (--) framebuffer bpp 24 (==) I810(0): RGB weight 888 (==) I810(0): Default visual is TrueColor (--) I810(0): Chipset: "i815" (--) I810(0): Linear framebuffer at 0xF8000000 (--) I810(0): IO registers at addr 0xF7000000 (II) I810(0): I810CheckAvailableMemory: 98304k available (**) I810(0): Will alloc AGP framebuffer: 8192 kByte (==) I810(0): Using gamma correction (1.0, 1.0, 1.0) (II) I810(0): My Monitor: Using hsync range of 30.00-70.00 kHz (II) I810(0): My Monitor: Using vrefresh range of 50.00-160.00 Hz (II) I810(0): Clock range: 12.00 to 136.00 MHz (WW) I810(0): Default mode "1280x960" deleted (bad mode clock/interlace/doublescan) (WW) I810(0): Default mode "1280x1024" deleted (hsync out of range) (WW) I810(0): Default mode "1280x1024" deleted (bad mode clock/interlace/doublescan) (WW) I810(0): Default mode "1600x1200" deleted (bad mode clock/interlace/doublescan) (WW) I810(0): Default mode "1600x1200" deleted (bad mode clock/interlace/doublescan) (WW) I810(0): Default mode "1600x1200" deleted (bad mode clock/interlace/doublescan) (WW) I810(0): Default mode "1600x1200" deleted (bad mode clock/interlace/doublescan) (WW) I810(0): Default mode "1600x1200" deleted (bad mode clock/interlace/doublescan) (WW) I810(0): Default mode "1792x1344" deleted (bad mode clock/interlace/doublescan) (WW) I810(0): Default mode "1792x1344" deleted (bad mode clock/interlace/doublescan) (WW) I810(0): Default mode "1856x1392" deleted (bad mode clock/interlace/doublescan) (WW) I810(0): Default mode "1856x1392" deleted (bad mode clock/interlace/doublescan) (WW) I810(0): Default mode "1920x1440" deleted (bad mode clock/interlace/doublescan) (WW) I810(0): Default mode "1920x1440" deleted (bad mode clock/interlace/doublescan) (--) I810(0): Virtual size is 1024x768 (pitch 1024) (**) I810(0): Mode "1024x768": 85.0 MHz, 63.4 kHz, 79.4 Hz (==) I810(0): DPI set to (75, 75) (II) Loading sub module "fb" (II) LoadModule: "fb" (II) Loading /usr/X11R6/lib/modules/libfb.a (II) Module fb: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.0.0 ABI class: XFree86 ANSI C Emulation, version 0.1 (II) Loading sub module "xaa" (II) LoadModule: "xaa" (II) Loading /usr/X11R6/lib/modules/libxaa.a (II) Module xaa: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.3 (II) Loading sub module "ramdac" (II) LoadModule: "ramdac" (II) Loading /usr/X11R6/lib/modules/libramdac.a (II) Module ramdac: vendor="The XFree86 Project" compiled for 4.0.2, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.3 Symbol VBEInit from module /usr/X11R6/lib/modules/drivers/i810_drv.o is unresolved! Symbol vbeDoEDID from module /usr/X11R6/lib/modules/drivers/i810_drv.o is unresolved! (==) Depth 24 pixmap format is 32 bpp (II) do I need RAC? No, I don't. (II) resource ranges after preInit: [0] 0 0xf7000000 - 0xf707ffff (0x80000) MS[B] [1] 0 0xf8000000 - 0xfbffffff (0x4000000) MS[B] [2] -1 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [3] -1 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [4] -1 0x000f0000 - 0x000fffff (0x10000) MX[B] [5] -1 0x000c0000 - 0x000effff (0x30000) MX[B] [6] -1 0x00000000 - 0x0009ffff (0xa0000) MX[B] [7] -1 0xf6800000 - 0xf6ffffff (0x800000) MX[B]E [8] -1 0xf7000000 - 0xf707ffff (0x80000) MX[B](B) [9] -1 0xf8000000 - 0xfbffffff (0x4000000) MX[B](B) [10] 0 0x000a0000 - 0x000affff (0x10000) MS[B](OprD) [11] 0 0x000b0000 - 0x000b7fff (0x8000) MS[B](OprD) [12] 0 0x000b8000 - 0x000bffff (0x8000) MS[B](OprD) [13] -1 0x00000000 - 0x000001ff (0x200) IX[B]E [14] -1 0x0000d400 - 0x0000d4ff (0x100) IX[B]E [15] -1 0x0000d800 - 0x0000d8ff (0x100) IX[B]E [16] -1 0x0000e800 - 0x0000e8ff (0x100) IX[B]E [17] -1 0x0000b800 - 0x0000b8ff (0x100) IX[B]E [18] 0 0x000003b0 - 0x000003bb (0xc) IS[B](OprU) [19] 0 0x000003c0 - 0x000003df (0x20) IS[B](OprU) (==) I810(0): Write-combining range (0xf7000000,0x80000) was already clear (==) I810(0): Write-combining range (0xf8000000,0x2000000) was already set (==) I810(0): Write-combining range (0xa0000,0x10000) was already clear (II) I810(0): Setting dot clock to 84.9 MHz [ 0x2c 0xb 0x20 ] [ 46 13 2 ] (II) I810(0): chose watermark 0x22218000: (tab.freq 94.5) (WW) I810(0): xf86AllocateGARTMemory: allocation of 1024 pages failed (Cannot allocate memory) (II) I810(0): No physical memory available for 4194304 bytes of DCACHE (II) I810(0): Adding 512 scanlines for pixmap caching (II) I810(0): Allocated Scratch Memory (II) I810(0): Using XFree86 Acceleration Architecture (XAA) Screen to screen bit blits Solid filled rectangles 8x8 mono pattern filled rectangles Indirect CPU to Screen color expansion Solid Horizontal and Vertical Lines Offscreen Pixmaps (==) I810(0): Backing store disabled (==) I810(0): Silken mouse enabled (II) I810(0): direct rendering: Disabled (II) Initializing built-in extension MIT-SHM (II) Initializing built-in extension XInputExtension (II) Initializing built-in extension XTEST (II) Initializing built-in extension XKEYBOARD (II) Initializing built-in extension LBX (II) Initializing built-in extension XC-APPGROUP (II) Initializing built-in extension SECURITY (II) Initializing built-in extension XINERAMA (II) Initializing built-in extension XFree86-Bigfont (II) Initializing built-in extension RENDER (**) Option "Protocol" "MouseSystems" (**) Mouse0: Protocol: "MouseSystems" (**) Option "CorePointer" (**) Mouse0: Core Pointer (**) Option "Device" "/dev/sysmouse" (**) Option "BaudRate" "1200" (**) Option "StopBits" "2" (**) Option "DataBits" "8" (**) Option "Parity" "None" (**) Option "Vmin" "1" (**) Option "Vtime" "0" (**) Option "FlowControl" "None" (==) Mouse0: Buttons: 3 (**) Option "ZAxisMapping" "4 5" (**) Mouse0: ZAxisMapping: buttons 4 and 5 (**) Mouse0: BaudRate: 1200 (II) Keyboard "Keyboard1" handled by legacy driver (II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE) (**) Option "BaudRate" "1200" GetModeLine - scrn: 0 clock: 85000 GetModeLine - hdsp: 1024 hbeg: 1088 hend: 1196 httl: 1340 vdsp: 768 vbeg: 772 vend: 775 vttl: 799 flags: 0 (WW) I810(0): xf86BindGARTMemory: binding of gart memory with key 1 at offset 0x0 failed (No such file or directory) Fatal server error: EnterVT failed for screen 0 When reporting a problem related to a server crash, please send the full server output, not just the last messages. This can be found in the log file "/var/log/XFree86.0.log". Please report problems to xfree86@xfree86.org. pgetbl_ctl: 0x59b001 pgetbl_err: 0x19 ipeir: 0 iphdr: 0 LP ring tail: 8 head: 0 len: 0 start 0 eir: 0 esr: 10 emr: 3d instdone: ff7b instpm: 0 memmode: 24 instps: 0 hwstam: 9ac7 ier: 0 imr: 9ac7 iir: 0 space: 65520 wanted 65528 FatalError re-entered, aborting lockup --0F1p//8PRICkK4MW-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 29 22:40:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 2C8E637B400; Mon, 29 Jan 2001 22:40:01 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f0U6dsK26897; Tue, 30 Jan 2001 07:39:54 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Greg Lehey Cc: Steve Ames , John Baldwin , John Indra , freebsd-current@FreeBSD.ORG Subject: Re: DEVFS newbie... In-Reply-To: Your message of "Tue, 30 Jan 2001 11:48:48 +1030." <20010130114848.B48269@wantadilla.lemis.com> Date: Tue, 30 Jan 2001 07:39:54 +0100 Message-ID: <26895.980836794@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010130114848.B48269@wantadilla.lemis.com>, Greg Lehey writes: >> You can create symlinks in /dev, you cannot mknod there. > >What is the reason for this? How does a program or script know >whether the system is running DEVFS or not? The reson for not creating device nodes is that you don't have all the information you'll need to really do it. To find out if you are running on a DEVFS system, look for existence of the sysctl variable "vfs.devfs.generation" -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 29 22:41:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id E37F437B402; Mon, 29 Jan 2001 22:41:25 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f0U6fBK26966; Tue, 30 Jan 2001 07:41:11 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Boris Popov Cc: Greg Lehey , Steve Ames , John Baldwin , John Indra , freebsd-current@FreeBSD.ORG Subject: Re: DEVFS newbie... In-Reply-To: Your message of "Tue, 30 Jan 2001 08:37:56 +0600." Date: Tue, 30 Jan 2001 07:41:11 +0100 Message-ID: <26964.980836871@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Boris Popov writes: >On Tue, 30 Jan 2001, Greg Lehey wrote: > >> > You can create symlinks in /dev, you cannot mknod there. >> >> What is the reason for this? How does a program or script know >> whether the system is running DEVFS or not? > > I don't see any good reason why this can't be supported. We may >talk about 'broken' devices, etc., but while there any - mknod needs to be >supported to make transition more smooth. No, mknod needs to be broken so people fix all drivers to be DEVFS aware. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 29 23: 5:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from syncopation-01.iinet.net.au (syncopation-01.iinet.net.au [203.59.24.37]) by hub.freebsd.org (Postfix) with SMTP id E25E637B65D for ; Mon, 29 Jan 2001 23:04:52 -0800 (PST) Received: (qmail 2828 invoked by uid 666); 30 Jan 2001 07:12:23 -0000 Received: from reggae-02-108.nv.iinet.net.au (HELO elischer.org) (203.59.91.108) by mail.m.iinet.net.au with SMTP; 30 Jan 2001 07:12:23 -0000 Message-ID: <3A76677C.1F1EBFF1@elischer.org> Date: Mon, 29 Jan 2001 23:04:29 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Boris Popov Cc: Greg Lehey , Poul-Henning Kamp , Steve Ames , John Baldwin , John Indra , freebsd-current@FreeBSD.ORG Subject: Re: DEVFS newbie... References: Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Boris Popov wrote: > > On Tue, 30 Jan 2001, Greg Lehey wrote: > > > > You can create symlinks in /dev, you cannot mknod there. > > > > What is the reason for this? How does a program or script know > > whether the system is running DEVFS or not? > > I don't see any good reason why this can't be supported. We may > talk about 'broken' devices, etc., but while there any - mknod needs to be > supported to make transition more smooth. you can't.. what is the major number? You don't know because they will be dynamically assigned. Only the kernel knows. Eventually, major numbers may go away entirely, (or just be a comlpetely random meaningless number, present only to keep old programs like tar() happy). > > -- > Boris Popov > http://www.butya.kz/~bp/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 29 23: 9:59 2001 Delivered-To: freebsd-current@freebsd.org Received: from urban.iinet.net.au (urban.iinet.net.au [203.59.24.231]) by hub.freebsd.org (Postfix) with ESMTP id 36CC637B488; Mon, 29 Jan 2001 23:09:38 -0800 (PST) Received: from muzak.iinet.net.au (muzak.iinet.net.au [203.59.24.237]) by urban.iinet.net.au (8.8.7/8.8.7) with ESMTP id PAA06501; Tue, 30 Jan 2001 15:09:29 +0800 Received: from elischer.org (reggae-02-108.nv.iinet.net.au [203.59.91.108]) by muzak.iinet.net.au (8.8.5/8.8.5) with ESMTP id PAA07078; Tue, 30 Jan 2001 15:07:09 +0800 Message-ID: <3A766895.F8C55BCD@elischer.org> Date: Mon, 29 Jan 2001 23:09:09 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Greg Lehey Cc: Boris Popov , Poul-Henning Kamp , Steve Ames , John Baldwin , John Indra , freebsd-current@FreeBSD.ORG Subject: Re: DEVFS newbie... References: <20010130114848.B48269@wantadilla.lemis.com> <20010130132238.H48490@wantadilla.lemis.com> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > > On Tuesday, 30 January 2001 at 8:37:56 +0600, Boris Popov wrote: > > On Tue, 30 Jan 2001, Greg Lehey wrote: > > > >>> You can create symlinks in /dev, you cannot mknod there. > >> > >> What is the reason for this? How does a program or script know > >> whether the system is running DEVFS or not? > > > > I don't see any good reason why this can't be supported. We may > > talk about 'broken' devices, etc., but while there any - mknod needs to be > > supported to make transition more smooth. > > I'm assuming that there's a good technical reason for the lack of > mknod. It also seems that mkdir doesn't work in devfs. Let's give > phk time to wake up and tell us. I have no idea why mkdir doesnt' work.. (It worked in the old devfs, but I assume it's just that phk just hasn't had the time yet to do it.) mknod is nonsensical in a world wher the user cannot predict the major number, and where the dev entry is connected to the driver via a pointer inside the kernel rather than an index. (How do you create the pointer? (mknod tty2 c 0xc0123452d 2)?) > > Greg > -- > Finger grog@lemis.com for PGP public key > See complete headers for address and phone numbers > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 29 23:34: 0 2001 Delivered-To: freebsd-current@freebsd.org Received: from entropy.mx (CC2-2464.charter-stl.com [24.217.121.178]) by hub.freebsd.org (Postfix) with ESMTP id C613137B698; Mon, 29 Jan 2001 23:33:40 -0800 (PST) Received: (from ajh3@localhost) by entropy.mx (8.11.1/8.11.1) id f0U7Wx106896; Tue, 30 Jan 2001 01:32:59 -0600 (CST) (envelope-from ajh3) Date: Tue, 30 Jan 2001 01:32:59 -0600 From: Andrew Hesford To: John Indra Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: -CURRENT and -STABLE against XFree86 4.0.2 problem Message-ID: <20010130013259.A6855@cec.wustl.edu> References: <20010130132200.A451@naver.co.id> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010130132200.A451@naver.co.id>; from john@naver.co.id on Tue, Jan 30, 2001 at 01:22:00PM +0700 X-Loop: Andrew Hesford Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thank god other people are having trouble with XFree86 4.0.2 and the i810 chipset, I was beginning to think I was going crazy. Even the guys in #freebsd (irc.openprojects.net) think I'm an idiot because I can't get it working =) The problem is actually worse than a simple lockup. The server crashes whenever I change virtual terminals. When I try to go back to ttyv8 (which holds my Xserver), it crashes with a "Fatal Error: lockup" message. An attempt to restart the server will show me a garbled-color screen, and then my display shuts off altogether, until I reboot (my monitor tells me the scan frequency is out of range; I don't know what's going on in there). I'm certainly not a code warrior, and I have absolutely no experience with agp-related programming in X or otherwise, but I did try to patch it (failing miserably). I've noticed that the I810FreeGART function is commented out in the driver, which leads me to believe that Linux automatically handles GART cleanup when the memory is no longer needed. However, if the FreeBSD agpgart code does not handle cleanup, it could be the source of this bug, since the xserver would then be unable to gain access to memory. Just a thought, remember that I know nothing about AGP programming. I would really like to see this problem fixed. Currently I am using XFree86 4.0.1, which bothers me simply on principle that I can't upgrade :) Thanks, Andrew Hesford -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 30 0: 9:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from lodge.guild.ab.ca (lodge.guild.ab.ca [209.91.118.66]) by hub.freebsd.org (Postfix) with ESMTP id C65ED37B4E0 for ; Tue, 30 Jan 2001 00:09:35 -0800 (PST) Received: (from davidc@localhost) by lodge.guild.ab.ca (8.11.1/8.11.1) id f0U89YA93078 for freebsd-current@freebsd.org; Tue, 30 Jan 2001 01:09:34 -0700 (MST) (envelope-from davidc) Date: Tue, 30 Jan 2001 01:09:34 -0700 From: Chad David To: freebsd-current@freebsd.org Subject: Re: stange console problem Message-ID: <20010130010934.A93057@lodge.guild.ab.ca> References: <20010128221602.A88482@lodge.guild.ab.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010128221602.A88482@lodge.guild.ab.ca>; from davidc@lodge.guild.ab.ca on Sun, Jan 28, 2001 at 10:16:02PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to my own post (which nobody has replied to, perhaps because I never actually phrased a question :-) )... I have found that if the kernel config file is named GENERIC, it will boot just fine; otherwise, I loose the console. I have done a cvsup tonight as well as a make world and many different kernels. If I copy GENERIC to DEBUG and recompile the kernel it will not boot properly.... copy the file back to GENERIC and everything seems fine? I have searched the archives and read UPDATING, but nothing jumps out at me. Does anybody have any idea where I could look next? Chad On Sun, Jan 28, 2001 at 10:16:02PM -0700, Chad David wrote: > On a current from last Sunday I recompiled > a new kernel with just makeoptions DEBUG=-g > and options DDB added to GENERIC and when > I boot I see the first few spins of the loader > booting the kernel and then all video output stops. > After the boot finishs I get a login prompt but no > keyboard response or video after that. > > I am able to ssh into the box, and all seems well > from the "inside". If I recompile GENERIC it works > just fine. > > Here is a dmesg, I noticed a few things but nothing I know > how to fix.. > > Chad > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 30 2:15:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from hera.drwilco.net (10dyn62.dh.casema.net [212.64.31.62]) by hub.freebsd.org (Postfix) with ESMTP id EADA837B4E0 for ; Tue, 30 Jan 2001 02:15:31 -0800 (PST) Received: from ceres.drwilco.nl (ceres.drwilco.net [10.1.1.19]) by hera.drwilco.net (8.11.1/8.11.1) with ESMTP id f0UAbSb07644; Tue, 30 Jan 2001 11:37:37 +0100 (CET) (envelope-from drwilco@drwilco.nl) Message-Id: <4.3.2.7.0.20010130110516.00cd1100@mail.bsdchicks.com> X-Sender: lists@mail.bsdchicks.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 30 Jan 2001 11:16:05 +0100 To: Chad David From: "Rogier R. Mulhuijzen" Subject: Re: stange console problem Cc: freebsd-current@freebsd.org In-Reply-To: <20010130010934.A93057@lodge.guild.ab.ca> References: <20010128221602.A88482@lodge.guild.ab.ca> <20010128221602.A88482@lodge.guild.ab.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >If I copy GENERIC to DEBUG and recompile the kernel it will not >boot properly.... copy the file back to GENERIC and everything >seems fine? > >I have searched the archives and read UPDATING, but nothing jumps >out at me. > >Does anybody have any idea where I could look next? > >Chad > >On Sun, Jan 28, 2001 at 10:16:02PM -0700, Chad David wrote: > > On a current from last Sunday I recompiled > > a new kernel with just makeoptions DEBUG=-g > > and options DDB added to GENERIC and when > > I boot I see the first few spins of the loader > > booting the kernel and then all video output stops. > > After the boot finishs I get a login prompt but no > > keyboard response or video after that. Have you tried removing the 'makeoptions' line and using 'config -g ' instead? That's how I build my debug kernels, and that worked fine last time I did it (last week or so). Also, when you copy the GENERIC file to another name, do you update the ident line? This should normally not matter but you never know with debugging kernels. In both cases you would need to examine the config utility. DocWilco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 30 2:30:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 2BB5937B6BE for ; Tue, 30 Jan 2001 02:30:25 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f0UAUUK29879 for ; Tue, 30 Jan 2001 11:30:30 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: vn, vnconfig and MFS death-warrant! From: Poul-Henning Kamp Date: Tue, 30 Jan 2001 11:30:30 +0100 Message-ID: <29877.980850630@critter> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have made mount_mfs and vnconfig print a warning and sleep for 15 seconds before continuing. Please convert to using mdconfig(8) for TMPFS uses. March 1st I will remove the functionality from mount_mfs and vnconfig, leaving only the message which will be an error obviously. April 1st I will remove vn, vnconfig and mount_mfs entirely. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 30 3:49:40 2001 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 A3CE737B6B2 for ; Tue, 30 Jan 2001 03:49:22 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id MAA19746; Tue, 30 Jan 2001 12:49:09 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: "Rogier R. Mulhuijzen" Cc: Chad David , freebsd-current@freebsd.org Subject: Re: stange console problem References: <20010128221602.A88482@lodge.guild.ab.ca> <20010128221602.A88482@lodge.guild.ab.ca> <4.3.2.7.0.20010130110516.00cd1100@mail.bsdchicks.com> From: Dag-Erling Smorgrav Date: 30 Jan 2001 12:49:08 +0100 In-Reply-To: "Rogier R. Mulhuijzen"'s message of "Tue, 30 Jan 2001 11:16:05 +0100" Message-ID: Lines: 14 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Rogier R. Mulhuijzen" writes: > Have you tried removing the 'makeoptions' line and using 'config -g > ' instead? > [...] > Also, when you copy the GENERIC file to another name, do you update the > ident line? None of this has any bearing on the problem, which was caused by a bug in gensetdefs.pl. Please update your source tree and rebuild your kernel. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 30 3:57: 0 2001 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id E379637B6B6 for ; Tue, 30 Jan 2001 03:56:35 -0800 (PST) Received: (from jhay@localhost) by zibbi.icomtek.csir.co.za (8.11.0/8.11.0) id f0UBuQw75143 for current@FreeBSD.org; Tue, 30 Jan 2001 13:56:26 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200101301156.f0UBuQw75143@zibbi.icomtek.csir.co.za> Subject: lock order reversal message To: current@FreeBSD.org Date: Tue, 30 Jan 2001 13:56:26 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Booting with a kernel built from today's source (with devfs also in), I see this lock order reversal message: ################################### Routing daemons:. Doing IPv6 network setup:add net ::ffff:0.0.0.0: gateway ::1 add net ::0.0.0.0: gateway ::1 net.inet6.ip6.forwarding: 0 -> 0 net.inet6.ip6.accept_rtadv: 0 -> 0 net.inet6.ip6.accept_rtadv: 0 -> 1 lock order reversal 1st vnode interlock last acquired @ ../../kern/vfs_vnops.c:644 2nd 0xc02d5280 mntvnode @ ../../ufs/ffs/ffs_vfsops.c:940 3rd 0xc85d314c vnode interlock @ ../../ufs/ffs/ffs_vfsops.c:949 add net fe80::: gateway ::1 add net ff02::: gateway fe80::2a0:c9ff:fe8d:7c5f%fxp0 ND default interface = fxp0 IPv4 mapped IPv6 address support=YES. Additional daemons: syslogd. ################################### The machine is a SMP box, if that makes a difference. It does not seem to cause harm because it continue booting and I can log in. The disks are scsi on an adaptec ahc controller, with most partitions on da0 and /usr/obj a link to a partition on da2. John -- John Hay -- John.Hay@icomtek.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 30 7: 5:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from hera.drwilco.net (10dyn62.dh.casema.net [212.64.31.62]) by hub.freebsd.org (Postfix) with ESMTP id ECC0537B491 for ; Tue, 30 Jan 2001 07:04:51 -0800 (PST) Received: from ceres.drwilco.nl (ceres.drwilco.net [10.1.1.19]) by hera.drwilco.net (8.11.1/8.11.1) with ESMTP id f0UFQtb08138; Tue, 30 Jan 2001 16:26:57 +0100 (CET) (envelope-from drwilco@drwilco.nl) Message-Id: <4.3.2.7.0.20010130160129.00aca700@mail.bsdchicks.com> X-Sender: lists@mail.bsdchicks.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 30 Jan 2001 16:03:10 +0100 To: Dag-Erling Smorgrav From: "Rogier R. Mulhuijzen" Subject: Re: stange console problem Cc: Chad David , freebsd-current@FreeBSD.ORG In-Reply-To: References: <"Rogier R. Mulhuijzen"'s message of "Tue, 30 Jan 2001 11:16:05 +0100"> <20010128221602.A88482@lodge.guild.ab.ca> <20010128221602.A88482@lodge.guild.ab.ca> <4.3.2.7.0.20010130110516.00cd1100@mail.bsdchicks.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >None of this has any bearing on the problem, which was caused by a bug >in gensetdefs.pl. Please update your source tree and rebuild your >kernel. Eek. I had the gensetdefs.pl problem too, but my machine just seemed to lock. He says his machine does go on running. I have been pretty tied up lately, so maybe I read his post a bit too quickly. DocWilco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 30 7:52:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from modemcable101.200-201-24.mtl.mc.videotron.ca (modemcable140.61-201-24.mtl.mc.videotron.ca [24.201.61.140]) by hub.freebsd.org (Postfix) with SMTP id 85C1837B503 for ; Tue, 30 Jan 2001 07:52:33 -0800 (PST) Received: (qmail 74305 invoked from network); 30 Jan 2001 15:52:32 -0000 Received: from cognac.local.mindstep.com (HELO cognac) (192.168.10.9) by jacuzzi.local.mindstep.com with SMTP; 30 Jan 2001 15:52:32 -0000 From: "Patrick Bihan-Faou" To: Cc: Subject: Re: vn, vnconfig and MFS death-warrant! Date: Tue, 30 Jan 2001 10:53:53 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Poul-Henning Kamp" wrote in message news:<29877.980850630@critter>... > > I have made mount_mfs and vnconfig print a warning and sleep for 15 > seconds before continuing. > > Please convert to using mdconfig(8) for TMPFS uses. > > March 1st I will remove the functionality from mount_mfs and > vnconfig, leaving only the message which will be an error obviously. > > April 1st I will remove vn, vnconfig and mount_mfs entirely. Could these modifications be ported to -STABLE to ease up the transition from -STABLE to -CURRENT ? I don't know if this is tied deeply on other changes in -CURRENT, but if it is not I'd like to use the new facility. Let me know if you want me to do some testing prior to committing the changes to -STABLE. I will happily contribute any help I can. Patrick. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 30 7:53:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from twister.domainfactory.de (twister.domainfactory.de [212.84.255.3]) by hub.freebsd.org (Postfix) with SMTP id DA22937B503 for ; Tue, 30 Jan 2001 07:53:34 -0800 (PST) Received: (qmail 21585 invoked from network); 30 Jan 2001 15:53:30 -0000 Received: from blndi5-212-144-192-005.arcor-ip.net (HELO gizmo.quizbot.org) ([212.144.192.5]) (envelope-sender ) by twister.domainfactory.de (qmail-ldap-1.03) with SMTP for ; 30 Jan 2001 15:53:30 -0000 Message-ID: <3A76E389.5F62E41A@gizmo.quizbot.org> Date: Tue, 30 Jan 2001 16:53:45 +0100 From: Robert Drehmel X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 5.0-CURRENT i386) MIME-Version: 1.0 To: Beau Cc: current@FreeBSD.ORG Subject: Re: BSD Documentation References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In , Beau wrote: > Hi, I;m new to FreeBSD and want to have a read of the manual before I start > installing willy-nilly, and I was wondering if there is a version available > with the entire handbook in one html document? or a zip/tar containing it > all would be fine. > > Thanks for your help and I look forward to BSDing! ftp://ftp.freebsd.org/pub/FreeBSD/doc/handbook/ -Robert To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 30 8:43:13 2001 Delivered-To: freebsd-current@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id 9E1BB37B503; Tue, 30 Jan 2001 08:42:46 -0800 (PST) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id IAA29125; Tue, 30 Jan 2001 08:42:46 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda29123; Tue Jan 30 08:42:29 2001 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.11.2/8.9.1) id f0UGgOD30939; Tue, 30 Jan 2001 08:42:24 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdG30925; Tue Jan 30 08:42:05 2001 Received: (from uucp@localhost) by cwsys.cwsent.com (8.11.2/8.9.1) id f0UGg5S27339; Tue, 30 Jan 2001 08:42:05 -0800 (PST) Message-Id: <200101301642.f0UGg5S27339@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdu27275; Tue Jan 30 08:41:45 2001 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-Sender: schubert To: freebsd-stable@freebsd.org, freebsd-current@freebsd.org Subject: CONNER CFP1080 Filesystem Corruption Date: Tue, 30 Jan 2001 08:41:44 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just submitted a PR and patch in kern/24740 to fix a tagged queueing related filesystem corruption problem on CONNER CFP1080 drives. The patch adds an entry to the xpt_quirk_tabke. Anyone willing to commit this for me? Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/Alpha Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD, ISTA Province of BC ------- Forwarded Message [headers removed] Date: Tue, 30 Jan 2001 08:30:01 -0800 (PST) Message-Id: <200101301630.f0UGU1V98029@freefall.freebsd.org> To: Cy.Schubert@uumail.gov.bc.ca From: gnats-admin@FreeBSD.org Subject: Re: kern/24740: CONNER CFP1080 Tagged Queueing Filesystem Corruption Reply-To: gnats-admin@FreeBSD.org, freebsd-bugs@FreeBSD.org In-Reply-To: Your message of Tue, 30 Jan 2001 08:28:12 -0800 (PST) <200101301628.f0UGSCh11615@cwsys.cwsent.com> Sender: gnats@FreeBSD.org Resent-To: cy@passer.osg.gov.bc.ca Resent-Date: Tue, 30 Jan 2001 08:31:20 -0800 Resent-From: Cy Schubert Thank you very much for your problem report. It has the internal identification `kern/24740'. The individual assigned to look at your report is: freebsd-bugs. You can access the state of your problem report at any time via this link: http://www.freebsd.org/cgi/query-pr.cgi?pr=24740 >Category: kern >Responsible: freebsd-bugs >Synopsis: filesystem corruption CFP1080 CAM SCSI cam_xpt.c >Arrival-Date: Tue Jan 30 08:30:01 PST 2001 ------- End of Forwarded Message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 30 8:45:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id C076D37B65D for ; Tue, 30 Jan 2001 08:45:10 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f0UGj9K32189; Tue, 30 Jan 2001 17:45:09 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: "Patrick Bihan-Faou" Cc: freebsd-current@freebsd.org Subject: Re: vn, vnconfig and MFS death-warrant! In-Reply-To: Your message of "Tue, 30 Jan 2001 10:53:53 EST." Date: Tue, 30 Jan 2001 17:45:09 +0100 Message-ID: <32187.980873109@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , "Patrick Bihan-F aou" writes: >Could these modifications be ported to -STABLE to ease up the transition >from -STABLE to -CURRENT ? I don't know if this is tied deeply on other >changes in -CURRENT, but if it is not I'd like to use the new facility. I think I would rather leave -stable out of this for now. There are too many deployed production systems I think. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 30 9: 1:14 2001 Delivered-To: freebsd-current@freebsd.org Received: from tkc.att.ne.jp (tkc.att.ne.jp [165.76.16.7]) by hub.freebsd.org (Postfix) with ESMTP id 7E1E637B67D; Tue, 30 Jan 2001 09:00:56 -0800 (PST) Received: from localhost.mzaki.nom (166.pool5.ipctokyo.att.ne.jp [165.76.43.166]) by tkc.att.ne.jp (8.8.8+Spin/3.6W-CONS(10/06/00)) id CAA01666; Wed, 31 Jan 2001 02:00:54 +0900 (JST) Date: Wed, 31 Jan 2001 02:00:53 +0900 Message-ID: <86hf2hx9dm.wl@tkc.att.ne.jp> From: Motomichi Matsuzaki To: phk@freebsd.org Cc: current@freebsd.org Subject: Re: vn, vnconfig and MFS death-warrant! In-Reply-To: In your message of "Tue, 30 Jan 2001 11:30:30 +0100" <29877.980850630@critter> References: <29877.980850630@critter> X-Mailer: Wanderlust/1.1.1 (Purple Rain) XEmacs/21.1 (Channel Islands) MIME-Version: 1.0 (generated by WEMI 1.13.7 - "Shimada") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Tue, 30 Jan 2001 11:30:30 +0100, Poul-Henning Kamp wrote: > March 1st I will remove the functionality from mount_mfs and > vnconfig, leaving only the message which will be an error obviously. > April 1st I will remove vn, vnconfig and mount_mfs entirely. I think we should postpone the complete removing for a year (on release of 5.2), to give people a migration sugar. System upgrading (4.x -> 5.x) will cause confusing situation, for example, living old 4.x vnconfig binary and new and splendid mdconfig. -- Motomichi Matsuzaki Dept. of Biological Sciences, Grad. School of Science, Univ. of Tokyo, Japan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 30 9: 1:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from modemcable101.200-201-24.mtl.mc.videotron.ca (modemcable140.61-201-24.mtl.mc.videotron.ca [24.201.61.140]) by hub.freebsd.org (Postfix) with SMTP id B70A737B65D for ; Tue, 30 Jan 2001 09:01:00 -0800 (PST) Received: (qmail 77757 invoked from network); 30 Jan 2001 17:00:59 -0000 Received: from cognac.local.mindstep.com (HELO cognac) (192.168.10.9) by jacuzzi.local.mindstep.com with SMTP; 30 Jan 2001 17:00:59 -0000 From: "Patrick Bihan-Faou" To: "Poul-Henning Kamp" Cc: Subject: RE: vn, vnconfig and MFS death-warrant! Date: Tue, 30 Jan 2001 12:02:20 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <32187.980873109@critter> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > >Could these modifications be ported to -STABLE to ease up the transition > >from -STABLE to -CURRENT ? I don't know if this is tied deeply on other > >changes in -CURRENT, but if it is not I'd like to use the new facility. > > I think I would rather leave -stable out of this for now. There are > too many deployed production systems I think. Just to make my intentions clear, I am not asking to remove vn/vnconfig(8)/mfs from -STABLE, I was just asking for the inclusion of md/mdconfig in -STABLE so that people (at least me :) ) can get ready for the day 5.0 will becomes -STABLE... My other problem is that I use vn's heavily and I find that some of their limitations are really annoying. While I could hack the relevent code to make myself happy, I think that there is little value in me doing that when it is obvious that they are going away in the not so distant future (5.0). Anyway, this is not a big deal. Patrick. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 30 9:15:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from tkc.att.ne.jp (tkc.att.ne.jp [165.76.16.7]) by hub.freebsd.org (Postfix) with ESMTP id 30B2737B491 for ; Tue, 30 Jan 2001 09:14:54 -0800 (PST) Received: from localhost.mzaki.nom (166.pool5.ipctokyo.att.ne.jp [165.76.43.166]) by tkc.att.ne.jp (8.8.8+Spin/3.6W-CONS(10/06/00)) id CAA04131; Wed, 31 Jan 2001 02:14:51 +0900 (JST) Date: Wed, 31 Jan 2001 02:14:51 +0900 Message-ID: <86g0i1x8qc.wl@tkc.att.ne.jp> From: Motomichi Matsuzaki To: current@freebsd.org Subject: Re: vn, vnconfig and MFS death-warrant! In-Reply-To: In your message of "Wed, 31 Jan 2001 02:00:53 +0900" <86hf2hx9dm.wl@tkc.att.ne.jp> References: <29877.980850630@critter> <86hf2hx9dm.wl@tkc.att.ne.jp> X-Mailer: Wanderlust/1.1.1 (Purple Rain) XEmacs/21.1 (Channel Islands) MIME-Version: 1.0 (generated by WEMI 1.13.7 - "Shimada") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Uh, self castigation. Sorry for inconvenience. > At Tue, 30 Jan 2001 11:30:30 +0100, > Poul-Henning Kamp wrote: > > March 1st I will remove the functionality from mount_mfs and > > vnconfig, leaving only the message which will be an error obviously. > > April 1st I will remove vn, vnconfig and mount_mfs entirely. > I think we should postpone the complete removing for a year till > (on release of 5.2), to give people a migration sugar. == Otherwise > System upgrading (4.x -> 5.x) will cause confusing situation, ^ > for example, living old 4.x vnconfig binary and together > new and splendid mdconfig. ^ -- Motomichi Matsuzaki Dept. of Biological Sciences, Grad. School of Science, Univ. of Tokyo, Japan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 30 9:24:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id C558A37B491; Tue, 30 Jan 2001 09:23:49 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id KAA23065; Tue, 30 Jan 2001 10:22:12 -0700 (MST) (envelope-from ken) Date: Tue, 30 Jan 2001 10:22:12 -0700 From: "Kenneth D. Merry" To: Cy Schubert - ITSD Open Systems Group Cc: freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: CONNER CFP1080 Filesystem Corruption Message-ID: <20010130102212.A23045@panzer.kdm.org> References: <200101301642.f0UGg5S27339@cwsys.cwsent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200101301642.f0UGg5S27339@cwsys.cwsent.com>; from Cy.Schubert@uumail.gov.bc.ca on Tue, Jan 30, 2001 at 08:41:44AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 30, 2001 at 08:41:44 -0800, Cy Schubert - ITSD Open Systems Group wrote: > I just submitted a PR and patch in kern/24740 to fix a tagged queueing > related filesystem corruption problem on CONNER CFP1080 drives. The > patch adds an entry to the xpt_quirk_tabke. Anyone willing to commit > this for me? I'll handle it. See my reply to the PR. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 30 10:48: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.theinternet.com.au (zeus.theinternet.com.au [203.34.176.2]) by hub.freebsd.org (Postfix) with ESMTP id C558237B6A1 for ; Tue, 30 Jan 2001 10:47:36 -0800 (PST) Received: (from akm@localhost) by mail.theinternet.com.au (8.9.3/8.9.3) id EAA41606 for current@freebsd.org; Wed, 31 Jan 2001 04:54:30 +1000 (EST) (envelope-from akm) Date: Wed, 31 Jan 2001 04:54:30 +1000 From: Andrew Kenneth Milton To: current@freebsd.org Subject: Voodoo3 + XFree4 + DRM - simple_lock ? :-) Message-ID: <20010131045430.R11513@zeus.theinternet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've made a roadmap to getting hardware accel 3d support using a Voodoo3 under XFree-4. I've attached it in case anyone is interested. However, recently simple_lock and friends seem to have disappeared, and the kernel modules make some use of them (although there is still reference to it in machine/smptests.h) It looked like I could replace them with calls to mtx_* stuff Removing the calls to simple_lock etc sure made it run a lot faster though, but, I think I'd rather have the safety. What are the 'new' corresponding structures and calls for simple_lock ? ------------------------------------------------------------------------ This is a roadmap for getting a native 3d Accelerated XFree 4 under FreeBSD. The XFree4 port changes fairly regularly so patches might have proven difficult (and I don't want to maintain a patchset for every revision). The instructions here can be followed with any tree even if stuff moves. These won't work for a -current after the beginning of January 2001, since the simple_lock stuff has gone away in anticipation of SMPng I assume. I've only done this using a PCI Voodoo 3 2000 Card, but, I'd assume if your card is working correctly then this will probably also work for you with some minor modifications. If you're using a 3dfx card, you'll need to grab the Glide SDK and install the headers. And you'll need to grab the source for Glide 3 and install the libraries. It compiled ok here, so I don't anticipate too many problems. ------------------------------------------------------------------------ Glide Libraries: Glide3x_devel-2.2-2.i386.rpm to install; rpm2cpio Glide3x_devel-2.2-2.i386.rpm | cpio -i -d cp -r usr/include/glide3 /usr/include Glide_V3-DRI-3.10-6.src.rpm to install; rpm2cpio Glide_V3-DRI-3.10-6.src.rpm | cpio -i You'll get a Glide3.10.tar.gz unpack that in a new directory; mkdir glide3 cd glide3 tar zxvf ../Glide3.10.tar.gz make -f makefile.linux look in the lib directory some of the symlinks are hosed, and will need to be fixed cp the glide3 libraries to /usr/lib ------------------------------------------------------------------------ This is for XFree-4.0.1 port revision 9 through to (so far) XFree-4.0.2 port revision 5 cd /usr/ports/x11/XFree-4 make extract make patch make configure (answer the questions). edit work/xc/config/cf/FreeBSD.cf and add; #define BuildXF86DRM YES #define BuildXF86DRI YES #define HasGlide3 YES At the bottom before the #include cd work/xc/programs/Xserver/hw/xfree86/os-support/bsd/drm/kernel Someone fell asleep at the wheel here over at VA-Linux, I assume it was a CVS snapshot that was half finished... but, other than this thing, good work :-) Basically you want to change all references to SYSCTL_HANDLER_ARGS to (SYSCTL_HANDLER_ARGS) in; drmP.h drm/memory.c drm/sysctl.c edit tdfx/tdfx_drv.c and change callout_init(&dev->timer) to callout_init(&dev->timer,0) go back to the top of your XFree-4 tree and do; make make install (if you already have XFree 4 installed you can probably skip this and continue on from here to get the kernel modules you need). Now you have to wander back down to work/xc/programs/Xserver/hw/xfree86/os-support/bsd/drm/kernel copy drm.ko to /usr/local/modules (or somewhere else convenient). and copy tdfx/tdfx.ko to /usr/local/modules/tdfx_drm.ko (this clashes with an existing native tdfx module for 'older' hardware). If this wasn't built automatically just type make in the tdfx directory and it should be built for you. kldload drm.ko this requires the agp module to load, even if you don't have an agp card. kldload tdfx_drm.ko You should see similar to this; drm0: <3Dfx Voodoo 3 graphics accelerator> port 0xdc00-0xdcff mem 0xe8000000-0xe9ffffff,0xee000000-0xefffffff irq 0 at device 14.0 on pci0 info: [drm] Initialized tdfx 1.0.0 19991009 on minor 0 If all goes well make an entry in /usr/local/etc/rc.d that loads your local modules on boot (or edit your /boot/ files if you're really game). I have this in /usr/local/etc/rc.d/3dfx.sh ------------------------------------------------------------------------ #!/bin/sh case $1 in start) [ -d /usr/local/modules ] && ( [ -x /usr/local/modules/drm.ko ] && ( kldload /usr/local/modules/drm.ko ) [ -x /usr/local/modules/tdfx_drm.ko ] && ( kldload /usr/local/modules/tdfx_drm.ko ) echo -n ' XF86-DRI' ) ;; stop) kldunload tdfx_drm.ko kldunload drm.ko ;; *) echo "usage: `basename $0` {start|stop}" >&2 exit 64 ;; esac ------------------------------------------------------------------------ In your /etc/X11/XF86Config you need to also have Load "glx" Load "dri" If you have an existing libGL.so.14 in /usr/X11R6/lib mv it to libGL.so.14.old and symlink libGL.so.14 to libGL.so.1 (ports requiring Mesa check for libGL.so.14, and will link to the hardware accelerated version). 3D acceleration only works in 16bpp mode, so make sure you're running with your depth set to 16 when you start your XFree 4. You should see drm entries in /var/log/XFree86.0.log; (0): [drm] created "tdfx" driver at busid "PCI:0:14:0" (0): [drm] added 4096 byte SAREA at 0xce95e000 (0): [drm] mapped SAREA 0xce95e000 to 0x1826d000 (0): [drm] framebuffer handle = 0xe8000000 (0): [drm] added 1 reserved context for kernel and later... (0): [DRI] installation complete (II) TDFX(0): direct rendering enabled (0) is the card number, if you have more than one you should get the same comments with (1) (2) etc. You'll probably also want to fix GiveConsole in your xdm config to give permissions to /dev/dri/card* Finally when running a GL program that dumps the GL stuff, if you see this; GL_VENDOR: Precision Insight, Inc. GL_RENDERER: Mesa DRI Voodoo3 20000616 GL_VERSION: 1.2 Mesa 3.3 beta or in this format with glxinfo OpenGL vendor string: VA Linux Systems, Inc. OpenGL renderer string: Mesa DRI Voodoo3 20001101 OpenGL version string: 1.2 Mesa 3.4 Then it's hardware accelerated, otherwise its linked to an older software library. Strange things: glplanet only gives a white globe, no texture map (from xscreensaver) Having stuff like nuq-glx (latest standalone quake) running and then going to a fullscreen GL app (ala screen saver kicks in) and then back does weird things with the modes (so don't leave windowed gl applications running :-) Quitting the GL application generally gets you back to normal (that's if you can actually quit the application). -- Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew Milton The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | ACN: 082 081 472 ABN: 83 082 081 472 | M:+61 416 022 411 | Carpe Daemon PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 30 13:11:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id A44AE37B6A7 for ; Tue, 30 Jan 2001 13:11:20 -0800 (PST) Received: (qmail 41458 invoked by uid 1142); 30 Jan 2001 21:11:19 -0000 Date: 30 Jan 2001 13:11:19 -0800 Date: Tue, 30 Jan 2001 13:11:11 -0800 From: Jason Evans To: Andrew Kenneth Milton Cc: current@freebsd.org Subject: Re: Voodoo3 + XFree4 + DRM - simple_lock ? :-) Message-ID: <20010130131111.F17900@canonware.com> References: <20010131045430.R11513@zeus.theinternet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010131045430.R11513@zeus.theinternet.com.au>; from akm@mail.theinternet.com.au on Wed, Jan 31, 2001 at 04:54:30AM +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 31, 2001 at 04:54:30AM +1000, Andrew Kenneth Milton wrote: > However, recently simple_lock and friends seem to have disappeared, and the > kernel modules make some use of them (although there is still reference > to it in machine/smptests.h) > > It looked like I could replace them with calls to mtx_* stuff > Removing the calls to simple_lock etc sure made it run a lot faster though, > but, I think I'd rather have the safety. > > What are the 'new' corresponding structures and calls for simple_lock ? Mutexes should be used in places where simplelocks were used. With few exceptions, sleep mutexes should be used (even though simplelocks were spin locks). See mutex(9) for details. Be forewarned that there is work in progress to clean up the mutex API that will probably be checked in within a week. Transitioning from the current mutex API to the upcoming one will be trivial, but it will have to be done if you convert to mutexes in the next few days. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 30 13:12: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id 5652337B6A4 for ; Tue, 30 Jan 2001 13:11:20 -0800 (PST) Received: (qmail 41454 invoked by uid 1142); 30 Jan 2001 21:11:19 -0000 Date: 30 Jan 2001 13:11:19 -0800 Date: Tue, 30 Jan 2001 09:42:07 -0800 From: Jason Evans To: John Hay Cc: current@FreeBSD.org Subject: Re: lock order reversal message Message-ID: <20010130094207.E17900@canonware.com> References: <200101301156.f0UBuQw75143@zibbi.icomtek.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101301156.f0UBuQw75143@zibbi.icomtek.csir.co.za>; from jhay@icomtek.csir.co.za on Tue, Jan 30, 2001 at 01:56:26PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 30, 2001 at 01:56:26PM +0200, John Hay wrote: > Booting with a kernel built from today's source (with devfs also in), > I see this lock order reversal message: > > ################################### > Routing daemons:. > Doing IPv6 network setup:add net ::ffff:0.0.0.0: gateway ::1 > add net ::0.0.0.0: gateway ::1 > net.inet6.ip6.forwarding: 0 -> 0 > net.inet6.ip6.accept_rtadv: 0 -> 0 > net.inet6.ip6.accept_rtadv: 0 -> 1 > lock order reversal > 1st vnode interlock last acquired @ ../../kern/vfs_vnops.c:644 > 2nd 0xc02d5280 mntvnode @ ../../ufs/ffs/ffs_vfsops.c:940 > 3rd 0xc85d314c vnode interlock @ ../../ufs/ffs/ffs_vfsops.c:949 > add net fe80::: gateway ::1 > add net ff02::: gateway fe80::2a0:c9ff:fe8d:7c5f%fxp0 > ND default interface = fxp0 > IPv4 mapped IPv6 address support=YES. > Additional daemons: syslogd. > ################################### > > The machine is a SMP box, if that makes a difference. It does not seem > to cause harm because it continue booting and I can log in. This shouldn't be a problem. The lock order reversal has been there for a long time and hasn't caused any problems, but since simplelocks were used before, we didn't have any diagnostics to tell us it was there. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 30 13:18:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from syncopation-01.iinet.net.au (syncopation-01.iinet.net.au [203.59.24.37]) by hub.freebsd.org (Postfix) with SMTP id 3511A37B6A8 for ; Tue, 30 Jan 2001 13:18:26 -0800 (PST) Received: (qmail 17345 invoked by uid 666); 30 Jan 2001 21:25:56 -0000 Received: from reggae-03-52.nv.iinet.net.au (HELO elischer.org) (203.59.78.52) by mail.m.iinet.net.au with SMTP; 30 Jan 2001 21:25:56 -0000 Message-ID: <3A772F8D.76F3E6C1@elischer.org> Date: Tue, 30 Jan 2001 13:18:05 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Jason Evans Cc: Andrew Kenneth Milton , current@freebsd.org Subject: Re: Voodoo3 + XFree4 + DRM - simple_lock ? :-) References: <20010131045430.R11513@zeus.theinternet.com.au> <20010130131111.F17900@canonware.com> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jason Evans wrote: > > On Wed, Jan 31, 2001 at 04:54:30AM +1000, Andrew Kenneth Milton wrote: > > However, recently simple_lock and friends seem to have disappeared, and the > > kernel modules make some use of them (although there is still reference > > to it in machine/smptests.h) > > > > It looked like I could replace them with calls to mtx_* stuff > > Removing the calls to simple_lock etc sure made it run a lot faster though, > > but, I think I'd rather have the safety. > > > > What are the 'new' corresponding structures and calls for simple_lock ? > > Mutexes should be used in places where simplelocks were used. With few > exceptions, sleep mutexes should be used (even though simplelocks were spin > locks). See mutex(9) for details. Be forewarned that there is work in > progress to clean up the mutex API that will probably be checked in within > a week. Transitioning from the current mutex API to the upcoming one will > be trivial, but it will have to be done if you convert to mutexes in the > next few days. where can we see the new spec (or at least a sample)? > > Jason > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 30 13:31:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id DB9C737B6A8 for ; Tue, 30 Jan 2001 13:31:18 -0800 (PST) Received: (qmail 42487 invoked by uid 1142); 30 Jan 2001 21:31:18 -0000 Date: 30 Jan 2001 13:31:18 -0800 Date: Tue, 30 Jan 2001 13:31:11 -0800 From: Jason Evans To: Julian Elischer Cc: Andrew Kenneth Milton , current@freebsd.org Subject: Re: Voodoo3 + XFree4 + DRM - simple_lock ? :-) Message-ID: <20010130133111.G17900@canonware.com> References: <20010131045430.R11513@zeus.theinternet.com.au> <20010130131111.F17900@canonware.com> <3A772F8D.76F3E6C1@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A772F8D.76F3E6C1@elischer.org>; from julian@elischer.org on Tue, Jan 30, 2001 at 01:18:05PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 30, 2001 at 01:18:05PM -0800, Julian Elischer wrote: > Jason Evans wrote: > > > > Mutexes should be used in places where simplelocks were used. With few > > exceptions, sleep mutexes should be used (even though simplelocks were spin > > locks). See mutex(9) for details. Be forewarned that there is work in > > progress to clean up the mutex API that will probably be checked in within > > a week. Transitioning from the current mutex API to the upcoming one will > > be trivial, but it will have to be done if you convert to mutexes in the > > next few days. > > where can we see the new spec (or at least a sample)? This is the most recent patch. I expect that the final result will be pretty similar, though Bosko may still change a couple of details: http://people.freebsd.org/~bmilekic/code/mutex_cleanup-5.patch Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 30 14:13:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id 199F637B6B4 for ; Tue, 30 Jan 2001 14:13:38 -0800 (PST) Received: by freesbee.wheel.dk (Postfix, from userid 1002) id 86F683E68; Tue, 30 Jan 2001 23:13:36 +0100 (CET) Date: Tue, 30 Jan 2001 23:13:36 +0100 From: "Niels Chr. Bank-Pedersen" To: current@freebsd.org Subject: Fatal trap 12 panic when starting vinum plex Message-ID: <20010130231336.C75428@bank-pedersen.dk> Mail-Followup-To: "Niels Chr. Bank-Pedersen" , current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On a very current -current, I get this reproducable panic when I try to revive a vinum plex: kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 0; lapic.id = 01000000 fault virtual address = 0x1a0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc015f01d stack pointer = 0x10:0xdfad6ca0 frame pointer = 0x10:0xdfad6cac code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 612 (vinum) kernel: type 12 trap, code=0 CPU0 stopping CPUs: 0x00000002... stopped. Stopped at mtx_enter_hard+0x125: movl 0x1a0(%edx),%eax db> trace mtx_enter_hard(c28e3930,0,0,0,c28e3900) at mtx_enter_hard+0x125 _mtx_enter(c28e3930,0,c2830240,87,0) at _mtx_enter+0x132 lockrange(0,cec3f330,c28e3900,c25f6000,2) at lockrange+0x31 revive_block(2,c25f6000,c2816d00,dfa90a80,0) at revive_block+0x2f6 start_object(c25f6000,0,c2816d00,dfa90a80,d9d4ac30) at start_object+0x10d setstate(c25f6000,dfad6e08,c2816d00,c25f6000,dfad6dd8) at setstate+0x1fd vinumioctl(c2816d00,c400464c,c25f6000,3,dfa90a80) at vinumioctl+0x4c1 spec_ioctl(dfad6e08,dfad6df0,c020e5f1,dfad6e08,dfad6e98) at spec_ioctl+0x2c spec_vnoperate(dfad6e08,dfad6e98,c019e8ac,dfad6e08,c292ddc0) at spec_vnoperate+0x15 ufs_vnoperatespec(dfad6e08,c292ddc0,0,400,c0283780) at ufs_vnoperatespec+0x15 vn_ioctl(c292ddc0,c400464c,c25f6000,dfa90a80,dfa90a80) at vn_ioctl+0x110 ioctl(dfa90a80,dfad6f80,bfbff64c,bfbff1cc,2) at ioctl+0x20a syscall2(2f,2f,2f,2,bfbff1cc) at syscall2+0x2a0 Xint0x80_syscall() at Xint0x80_syscall+0x23 --- syscall 0x36, eip = 0x8072ecc, esp = 0xbfbff1a0, ebp = 0xbfbff68c --- db> Dunno if this is actually vinum, or it is caused by the mere fact that I'm trying to run -current. Anyway, it happens in UP as well as SMP, and I am not using DEVFS. Oh, one more thing: the vinum volume (raid01) apparantly runs without any problems - as long as I don't try to revive a faulty plex within the volume. /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. "Hey, are any of you guys out there actually *using* RFC 2549?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 30 15:20:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id 8109837B6D2 for ; Tue, 30 Jan 2001 15:20:26 -0800 (PST) Received: by shadowmere.student.utwente.nl (Postfix, from userid 1000) id 16EF41F9D; Wed, 31 Jan 2001 00:20:24 +0100 (CET) Date: Wed, 31 Jan 2001 00:20:24 +0100 From: Pascal Hofstee To: freebsd-current@freebsd.org Subject: Bug in tftpd ? Message-ID: <20010131002024.A77116@shadowmere.student.utwente.nl> Reply-To: daeron@shadowmere.student.utwente.nl Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I think i just encountered a bug in FreeBSD's tftpd-implementation. Actually it's a bug that i spotted a while back with a friend of mine in NetBSD's implementation, but never really bothered with it since i don't use tftpd myself, but i am in a position now where i need to with FreeBSD. The bug only triggers when trying to fetch files bigger than 32 MB. On NetBSD it happened around a 16 MB boundary ... (but i may have interpreted blocksizes wrong). The issue is located in a minor difference in tftpd's own "block" count and 's struct tftphdr 's "tu_block" type declaration defines the block count: unsigned short tu_block; /* block # */ tftpd.c 's xmitfile and recvfile functions define the block count: volatile int block; What happens is kinda obvious .... after quite a lot of data has been sent without any problems ... suddenly tftpd's block-counter starts wrapping while 's block counter does simply increase more. This results in "TIMEOUT errors" as the block-sequence numbers simply won't match any more. If patches are required let me know ... -- Pascal Hofstee < daeron @ shadowmere . student . utwente . nl > begin LOVE-LETTER-FOR-YOU.TXT.vbs I'm a signature virus. Please copy me and help me spread. end To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 30 16:40:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from updraft.jp.freebsd.org (updraft.jp.FreeBSD.ORG [210.157.158.42]) by hub.freebsd.org (Postfix) with ESMTP id 7B49A37B6A3 for ; Tue, 30 Jan 2001 16:40:26 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by updraft.jp.freebsd.org (8.11.2+3.4W/8.11.1) with ESMTP/inet id f0V0eNW64346 for ; Wed, 31 Jan 2001 09:40:24 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) In-Reply-To: <29877.980850630@critter> References: <29877.980850630@critter> X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.2 XEmacs/21.2 (Poseidon) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 14 From: Makoto MATSUSHITA To: current@FreeBSD.ORG Subject: Re: vn, vnconfig and MFS death-warrant! Date: Wed, 31 Jan 2001 09:40:05 +0900 Message-Id: <20010131094005W.matusita@jp.FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just a note. phk> March 1st I will remove the functionality from mount_mfs and phk> vnconfig, leaving only the message which will be an error obviously. Before March 1st, src/release/Makefile, src/release/scripts/doFS.sh, src/release/texts/FLOPPIES.TXT, and some PicoBSD stuffs need some work to convert from vnconfig(8) to mdconfig(8). Is Anybody working on this? -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 30 18:19: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.theinternet.com.au (zeus.theinternet.com.au [203.34.176.2]) by hub.freebsd.org (Postfix) with ESMTP id C157337B6B6 for ; Tue, 30 Jan 2001 18:18:47 -0800 (PST) Received: (from akm@localhost) by mail.theinternet.com.au (8.9.3/8.9.3) id MAA46680; Wed, 31 Jan 2001 12:25:35 +1000 (EST) (envelope-from akm) Date: Wed, 31 Jan 2001 12:25:35 +1000 From: Andrew Kenneth Milton To: Jason Evans Cc: Andrew Kenneth Milton , current@freebsd.org Subject: Re: Voodoo3 + XFree4 + DRM - simple_lock ? :-) Message-ID: <20010131122535.S11513@zeus.theinternet.com.au> References: <20010131045430.R11513@zeus.theinternet.com.au> <20010130131111.F17900@canonware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <20010130131111.F17900@canonware.com>; from Jason Evans on Tue, Jan 30, 2001 at 01:11:11PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG +-------[ Jason Evans ]---------------------- | | > What are the 'new' corresponding structures and calls for simple_lock ? | | Mutexes should be used in places where simplelocks were used. With few | exceptions, sleep mutexes should be used (even though simplelocks were spin | locks). See mutex(9) for details. Be forewarned that there is work in | progress to clean up the mutex API that will probably be checked in within | a week. Transitioning from the current mutex API to the upcoming one will | be trivial, but it will have to be done if you convert to mutexes in the | next few days. I can wait a week to fix the code, I guess I should send it back to VA to see if they'll actually include it in the base XFree Release. Someone else is already working on a Glide3 port, so X would be looking pretty useful for Voodoo3 owners d8) Too bad I need those locks, the pulsar hack that comes with xscreensaver normally runs around 50fps (or 0.5 fps w/o drm) -- I get way over 200fps with all the locks disabled d8) Of course if I suspend it while its running the machine freezes... I can live with that for a while anwyay. -- Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew Milton The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | ACN: 082 081 472 ABN: 83 082 081 472 | M:+61 416 022 411 | Carpe Daemon PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 30 19:14:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from sm5.texas.rr.com (unknown [24.93.35.219]) by hub.freebsd.org (Postfix) with ESMTP id 6636937B6A1 for ; Tue, 30 Jan 2001 19:14:39 -0800 (PST) Received: from bleep.craftncomp.com (cs2777-167.houston.rr.com [24.27.77.167]) by sm5.texas.rr.com (8.11.0/8.11.1) with ESMTP id f0V48De09469; Tue, 30 Jan 2001 22:08:13 -0600 Received: from bloop.craftncomp.com (bloop.craftncomp.com [202.12.111.1]) by bleep.craftncomp.com (8.11.1/8.9.3) with ESMTP id f0V3EIE02735; Tue, 30 Jan 2001 21:14:18 -0600 (CST) (envelope-from shocking@houston.rr.com) Received: from bloop.craftncomp.com (localhost [127.0.0.1]) by bloop.craftncomp.com (8.11.1/8.9.3) with ESMTP id f0V3EEH40319; Tue, 30 Jan 2001 21:14:14 -0600 (CST) (envelope-from shocking@bloop.craftncomp.com) Message-Id: <200101310314.f0V3EEH40319@bloop.craftncomp.com> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Andrew Kenneth Milton Cc: current@freebsd.org Subject: Voodoo3 + XFree4 + DRM - simple_lock ? :-) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 30 Jan 2001 21:14:14 -0600 From: Stephen Hocking Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey, I've been fooling with this (and Glide3) but under FBSD 4.2. Didn't have the time or inclination to do it under the latest current. Good to see someone's been crazy^Wbrave enough to try. It'd bee really nice if someone could make the kernel modules part of the current tree, the same way they are under Linux. Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 30 20:27:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from lodge.guild.ab.ca (lodge.guild.ab.ca [209.91.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 201C837B491 for ; Tue, 30 Jan 2001 20:27:24 -0800 (PST) Received: (from davidc@localhost) by lodge.guild.ab.ca (8.11.1/8.11.1) id f0V4Qx896894; Tue, 30 Jan 2001 21:26:59 -0700 (MST) (envelope-from davidc) Date: Tue, 30 Jan 2001 21:26:59 -0700 From: Chad David To: "Rogier R. Mulhuijzen" Cc: Dag-Erling Smorgrav , Chad David , freebsd-current@FreeBSD.ORG Subject: Re: stange console problem Message-ID: <20010130212659.B96856@lodge.guild.ab.ca> References: <"Rogier <20010128221602.A88482@lodge.guild.ab.ca> <20010128221602.A88482@lodge.guild.ab.ca> <4.3.2.7.0.20010130110516.00cd1100@mail.bsdchicks.com> <4.3.2.7.0.20010130160129.00aca700@mail.bsdchicks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <4.3.2.7.0.20010130160129.00aca700@mail.bsdchicks.com>; from drwilco@drwilco.nl on Tue, Jan 30, 2001 at 04:03:10PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Problem solved. cp GENERIC.hints DEBUG.hints Without them it isn't very happy... did I miss this as a requirement somewhere, or is my hardware/timing just a little funky? Chad On Tue, Jan 30, 2001 at 04:03:10PM +0100, Rogier R. Mulhuijzen wrote: > > >None of this has any bearing on the problem, which was caused by a bug > >in gensetdefs.pl. Please update your source tree and rebuild your > >kernel. > > Eek. I had the gensetdefs.pl problem too, but my machine just seemed to > lock. He says his machine does go on running. > > I have been pretty tied up lately, so maybe I read his post a bit too quickly. > > DocWilco > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 30 21:10:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id 614DD37B6A6 for ; Tue, 30 Jan 2001 21:10:27 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f0V5A6475024; Tue, 30 Jan 2001 21:10:06 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200101310510.f0V5A6475024@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Chad David Cc: "Rogier R. Mulhuijzen" , Dag-Erling Smorgrav , Chad David , freebsd-current@FreeBSD.ORG Subject: Re: stange console problem In-Reply-To: <20010130212659.B96856@lodge.guild.ab.ca> Date: Tue, 30 Jan 2001 21:10:06 -0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chad David wrote: > Problem solved. > > cp GENERIC.hints DEBUG.hints > > Without them it isn't very happy... did I miss this as a requirement > somewhere, or is my hardware/timing just a little funky? Yes, you were not reading the commit messages or UPDATING or -current. You should have a /boot/device.hints for your machine. You dont need GENERIC.hints or DEBUG.hints if you have this set up correctly. As a head start, you can cp GENERIC.hints to /boot/device.hints and you're done. config and 'make install' will not let you forget this.. Were you installing your kernel by hand or something? > Chad > > On Tue, Jan 30, 2001 at 04:03:10PM +0100, Rogier R. Mulhuijzen wrote: > > > > >None of this has any bearing on the problem, which was caused by a bug > > >in gensetdefs.pl. Please update your source tree and rebuild your > > >kernel. > > > > Eek. I had the gensetdefs.pl problem too, but my machine just seemed to > > lock. He says his machine does go on running. > > > > I have been pretty tied up lately, so maybe I read his post a bit too quick ly. > > > > DocWilco > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 31 2:27:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from webcom.it (brian.inet.it [213.92.4.195]) by hub.freebsd.org (Postfix) with SMTP id A45F937B698 for ; Wed, 31 Jan 2001 02:27:23 -0800 (PST) Received: (qmail 2662 invoked by uid 1000); 31 Jan 2001 10:21:05 -0000 Date: Wed, 31 Jan 2001 11:21:05 +0100 From: Andrea Campi To: freebsd-current@freebsd.org Subject: RFC: user-config alt path in Linux emulation Message-ID: <20010131112104.B2268@webcom.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Background: When running a Linux binary in Linux compat mode, all calls to open(), readdir() and such, end up calling linux_emul_find() from linux_util.c. This functions looks for a directory/file with the same name in the /compat/linux hierarchy. The net effect is that there is no way to, for instance, back up the real /usr from Tivoli, etc... as there is no way to get to a real path if there is anything with the same name inside /compat/linux. I'd like to understand if there is any accepted way to work around this limitation (no, symlinks are not an option :-p), I'm sure not. Proposal: Implement some way to make this behavior user configurable. The easiest way would probably involve a sysctl to turn it on/off but I would like to have more granularity. I could probably store a flag somewhere in elfhints_hdr.spare, but I'm sure there will be a lot of objections to this. I think this could be done in two parts: 1 - A flag to turn path transalation on/off 2 - A version of the syscalls which accept this flag 3 - A shared library implementing just the needed function calls and calling the new syscalls I don't know if I even understand this correctly, never done this before, but I could learn ;-) Another approach would be to somehow teach the kernel which processes to "let alone", but this would be tricky and probably slower. Alternate proposal: If everything else fails, what about mapping the real filesystems somewhere below /compat/linux? Something like: /compat/linux/native/root /compat/linux/native/usr /compat/linux/native/var Actually (I'm thinking about this just as I am writing) this could be the easier and cleaner solution. Note that these must appear to be real mountpoints. Does this need to go through userland NFS? So, let the discussion begin. If there is no interest, I will implement it in the way which is easier to me (which probably would be the last one). If there is interest and anybody volunteers, fine, otherwise I will implement it and put it up somewhere for review. Bye, Andrea -- Secret hacker rule #11: hackers read manuals. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 31 3:14:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id 7707E37B6A3 for ; Wed, 31 Jan 2001 03:13:55 -0800 (PST) Received: by shadowmere.student.utwente.nl (Postfix, from userid 1000) id 671122060; Wed, 31 Jan 2001 12:13:54 +0100 (CET) Date: Wed, 31 Jan 2001 12:13:54 +0100 From: Pascal Hofstee To: freebsd-current@freebsd.org Subject: Re: Bug in tftpd ? Message-ID: <20010131121353.A21533@shadowmere.student.utwente.nl> Reply-To: daeron@shadowmere.student.utwente.nl References: <20010131002024.A77116@shadowmere.student.utwente.nl> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="sdtB3X0nJg68CQEu" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010131002024.A77116@shadowmere.student.utwente.nl>; from daeron@shadowmere.student.utwente.nl on Wed, Jan 31, 2001 at 12:20:24AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --sdtB3X0nJg68CQEu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Patches attached: Obtained from: NetBSD (Committed there about 3 months ago after we first spotted the problem in their implementation) -- Pascal Hofstee < daeron @ shadowmere . student . utwente . nl > begin LOVE-LETTER-FOR-YOU.TXT.vbs I'm a signature virus. Please copy me and help me spread. end --sdtB3X0nJg68CQEu Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="tftpd.patch" --- tftpd.8.orig Wed Jan 31 11:59:57 2001 +++ tftpd.8 Wed Jan 31 12:04:55 2001 @@ -192,3 +192,9 @@ .Fl c option was introduced in .Fx 5.0 . +.Sh BUGS +Files larger than 33488896 octets (65535 blocks) cannot be transferred +without client and server supporting blocksize negotiation (RFC1783). +.Pp +Many tftp clients will not transfer files over 16744448 octets (32767 blocks). + --- tftpd.c.orig Wed Jan 31 11:55:53 2001 +++ tftpd.c Wed Jan 31 11:58:00 2001 @@ -501,7 +501,7 @@ struct tftphdr *dp, *r_init(); register struct tftphdr *ap; /* ack packet */ register int size, n; - volatile int block; + volatile unsigned int block; signal(SIGALRM, timer); dp = r_init(); @@ -571,7 +571,7 @@ struct tftphdr *dp, *w_init(); register struct tftphdr *ap; /* ack buffer */ register int n, size; - volatile int block; + volatile unsigned int block; signal(SIGALRM, timer); dp = w_init(); --sdtB3X0nJg68CQEu-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 31 3:33:25 2001 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 83E8E37B6A7; Wed, 31 Jan 2001 03:33:06 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id MAA25140; Wed, 31 Jan 2001 12:32:16 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Cy Schubert - ITSD Open Systems Group Cc: freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: CONNER CFP1080 Filesystem Corruption References: <200101301642.f0UGg5S27339@cwsys.cwsent.com> From: Dag-Erling Smorgrav Date: 31 Jan 2001 12:32:15 +0100 In-Reply-To: Cy Schubert - ITSD Open Systems Group's message of "Tue, 30 Jan 2001 08:41:44 -0800" Message-ID: Lines: 14 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cy Schubert - ITSD Open Systems Group writes: > I just submitted a PR and patch in kern/24740 to fix a tagged queueing > related filesystem corruption problem on CONNER CFP1080 drives. The > patch adds an entry to the xpt_quirk_tabke. Anyone willing to commit > this for me? Hmm, I've had a CFP1080S (Antigua) for years, and never experienced any trouble at all with it. It held my FreeBSD CVS repo mirror until I got a new desktop last fall, so it's seen some pretty heavy activity over the years. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 31 4:42:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id 5C12A37B491; Wed, 31 Jan 2001 04:42:10 -0800 (PST) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id EAA32418; Wed, 31 Jan 2001 04:41:37 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda32416; Wed Jan 31 04:41:28 2001 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.11.2/8.9.1) id f0VCfNM36477; Wed, 31 Jan 2001 04:41:23 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdy36475; Wed Jan 31 04:41:22 2001 Received: (from uucp@localhost) by cwsys.cwsent.com (8.11.2/8.9.1) id f0VCfLS13294; Wed, 31 Jan 2001 04:41:21 -0800 (PST) Message-Id: <200101311241.f0VCfLS13294@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdc12512; Wed Jan 31 04:40:28 2001 X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-Sender: schubert To: Dag-Erling Smorgrav Cc: Cy Schubert - ITSD Open Systems Group , freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: CONNER CFP1080 Filesystem Corruption In-reply-to: Your message of "31 Jan 2001 12:32:15 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 31 Jan 2001 04:40:28 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/Alpha Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD, ISTA Province of BC In message , Dag-Erling Smorgrav writes: > Cy Schubert - ITSD Open Systems Group writes: > > I just submitted a PR and patch in kern/24740 to fix a tagged queueing > > related filesystem corruption problem on CONNER CFP1080 drives. The > > patch adds an entry to the xpt_quirk_tabke. Anyone willing to commit > > this for me? > > Hmm, I've had a CFP1080S (Antigua) for years, and never experienced > any trouble at all with it. It held my FreeBSD CVS repo mirror until I > got a new desktop last fall, so it's seen some pretty heavy activity > over the years. I've got the same drive. Attached to a 1542B it works fine. Attached to a 2940U the filesystem is corrupted within minutes. Reducing the bus speed to 5 MB/S and turning off tagged queueing fixes the problem. W/O the patch, it claims to be capable of 254 device openings -- I would think that's a bit high for an old drive. Anyhow, I replaced the CFP1080S, which itself replaced a dead Quantum drive, with a brand new 4 GB Seagate -- replacing a 2 GB drive with a 1 GB drive caused a host of other problems not related to problem discussed here. :) Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/Alpha Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD, ISTA Province of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 31 4:49:35 2001 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 6DADC37B69B; Wed, 31 Jan 2001 04:49:16 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id NAA25411; Wed, 31 Jan 2001 13:48:20 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Cy Schubert - ITSD Open Systems Group Cc: freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: CONNER CFP1080 Filesystem Corruption References: <200101311241.f0VCfLS13294@cwsys.cwsent.com> From: Dag-Erling Smorgrav Date: 31 Jan 2001 13:48:19 +0100 In-Reply-To: Cy Schubert - ITSD Open Systems Group's message of "Wed, 31 Jan 2001 04:40:28 -0800" Message-ID: Lines: 16 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cy Schubert - ITSD Open Systems Group writes: > In message , Dag-Erling Smorgrav > writes: > > Hmm, I've had a CFP1080S (Antigua) for years, and never experienced > > any trouble at all with it. [...] > I've got the same drive. Attached to a 1542B it works fine. Attached > to a 2940U the filesystem is corrupted within minutes. I have it on a 2940UW (factory default settings, except maybe for >1GB support) which it shares with a Quantum Atlas II (XP4550W) and a Tecmar Travan streamer. Never any trouble. I can mail you a dmesg when I get home later tonight. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 31 5: 8:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id E46F737B6C4; Wed, 31 Jan 2001 05:08:31 -0800 (PST) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id FAA32487; Wed, 31 Jan 2001 05:07:58 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda32485; Wed Jan 31 05:07:39 2001 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.11.2/8.9.1) id f0VD7YA36695; Wed, 31 Jan 2001 05:07:34 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdi36693; Wed Jan 31 05:07:22 2001 Received: (from uucp@localhost) by cwsys.cwsent.com (8.11.2/8.9.1) id f0VD7LN21917; Wed, 31 Jan 2001 05:07:21 -0800 (PST) Message-Id: <200101311307.f0VD7LN21917@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdc21907; Wed Jan 31 05:06:48 2001 X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 X-Exmh-Isig-CompType: repl X-Exmh-Isig-Folder: inbox Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-Sender: schubert To: Dag-Erling Smorgrav Cc: Cy Schubert - ITSD Open Systems Group , freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: CONNER CFP1080 Filesystem Corruption In-reply-to: Your message of "31 Jan 2001 13:48:19 +0100." Mime-Version: 1.0 Content-Type: text/plain Date: Wed, 31 Jan 2001 05:06:47 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Dag-Erling Smorgrav writes: > Cy Schubert - ITSD Open Systems Group writes: > > In message , Dag-Erling Smorgrav > > writes: > > > Hmm, I've had a CFP1080S (Antigua) for years, and never experienced > > > any trouble at all with it. [...] > > I've got the same drive. Attached to a 1542B it works fine. Attached > > to a 2940U the filesystem is corrupted within minutes. > > I have it on a 2940UW (factory default settings, except maybe for >1GB > support) which it shares with a Quantum Atlas II (XP4550W) and a > Tecmar Travan streamer. Never any trouble. I can mail you a dmesg when > I get home later tonight. This is dmesg from when I still had the Conner drive installed. I've removed the redundant syslog header. Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.2-RELEASE #9: Tue Jan 30 06:59:46 PST 2001 root@:/opt/cvs-420r/src/sys/compile/CWSYS Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 119752645 Hz CPU: Pentium/P54C (119.75-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping = 12 Features=0x1bf real memory = 83886080 (81920K bytes) avail memory = 78356480 (76520K bytes) Preloaded elf kernel "kernel" at 0xc0337000. Intel Pentium detected, installing workaround for F00F bug md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 7.2 irq 9 xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0x6000-0x607f mem 0xe4001000-0xe400107f irq 5 at device 18.0 on pci0 xl0: Ethernet address: 00:50:da:80:28:96 miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus 0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100base TX-FDX, auto ahc0: port 0x6100-0x61ff mem 0xe4000000-0xe4000fff irq 5 at device 19.0 on pci0 aic7880: Wide Channel A, SCSI Id=7, 16/255 SCBs pci0: at 20.0 irq 12 fdc0: at port 0x3f0-0x3f5,0 x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 fd1: <1200-KB 5.25" drive> on fdc0 drive 1 aha0 at port 0x330-0x333 irq 11 drq 5 on isa0 aha0: AHA-1542CF FW Rev. C.0 (ID=45) SCSI Host Adapter, SCSI ID 7, 16 CCBs atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: on ppbus0 lpt0: Interrupt-driven port ep0: <3Com 3C509-Combo EtherLink III> at port 0x300-0x30f irq 10 on isa0 ep0: Ethernet address 00:60:97:d3:32:3e IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to deny, unlimited logging DUMMYNET initialized (000608) IP Filter: v3.4.16 initialized. Default = block all, Logging = enabled ad0: 2014MB [4092/16/63] at ata0-master WDMA2 ad2: 2441MB [4960/16/63] at ata1-master WDMA2 Waiting 15 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 4 lun 0 sa0: Removable Se quential Access SCSI-2 device sa0: 7.812MB/s transfers (7.812MHz, offset 15) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da1: 4340MB (8888924 512 byte sectors: 64H 32S/T 4340C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15) da0: 1030MB (2110812 512 byte sectors: 64H 32S/T 1030C) Mounting root from ufs:/dev/ad0s1a cd0 at ahc0 bus 0 target 2 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 4.032MB/s transfers (4.032MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present da2 at aha0 bus 0 target 6 lun 0 da2: Removable Direct Acces s SCSI-2 device da2: 3.300MB/s transfers da2: Attempt to query device size failed: NOT READY, Medium not present Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/Alpha Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD, ISTA Province of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 31 5:30:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 985BF37B6AB for ; Wed, 31 Jan 2001 05:30:36 -0800 (PST) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 14NxLH-0007TZ-00; Wed, 31 Jan 2001 14:30:35 +0100 Received: (from daemon@localhost) by kemoauc.mips.inka.de (8.11.1/8.11.1) id f0VCowS61806 for freebsd-current@freebsd.org; Wed, 31 Jan 2001 13:50:58 +0100 (CET) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: RFC: user-config alt path in Linux emulation Date: Wed, 31 Jan 2001 12:50:58 +0000 (UTC) Message-ID: <9591ni$1qrm$1@kemoauc.mips.inka.de> References: <20010131112104.B2268@webcom.it> Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrea Campi wrote: > The net effect is that there is no way to, for instance, back up the > real /usr from Tivoli, etc... as there is no way to get to a real path > if there is anything with the same name inside /compat/linux. Loopback NFS mount. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 31 6:45:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id 0A2C837B491 for ; Wed, 31 Jan 2001 06:45:18 -0800 (PST) Received: (from ache@localhost) by nagual.pp.ru (8.11.2/8.11.2) id f0VEj3E19357; Wed, 31 Jan 2001 17:45:04 +0300 (MSK) (envelope-from ache) Date: Wed, 31 Jan 2001 17:44:59 +0300 From: "Andrey A. Chernov" To: eischen@vigrid.com, current@freebsd.org Subject: New threads way questions Message-ID: <20010131174457.A19255@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have some questions about new threads way. Daniel says that new way is: > gcc -Wall -o foo foo.c -lc_r 1) What about libgcc_r.a? Is it picked automatically in this case or not? Is it ever needed now? 2) Is new way is backward-compatible with old way? I.e. can we just change ports to use new way and assume that still works on -stable? 3) Is -D_THREAD_SAFE required now? -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 31 6:46:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from mout0.freenet.de (mout0.freenet.de [194.97.50.131]) by hub.freebsd.org (Postfix) with ESMTP id 5998B37B503 for ; Wed, 31 Jan 2001 06:46:28 -0800 (PST) Received: from [194.97.50.136] (helo=mx3.freenet.de) by mout0.freenet.de with esmtp (Exim 3.20 #16) id 14NyWb-0000CC-00; Wed, 31 Jan 2001 15:46:21 +0100 Received: from b841e.pppool.de ([213.7.132.30] helo=Magelan.Leidinger.net) by mx3.freenet.de with esmtp (Exim 3.20 #17) id 14NyWZ-0002Vr-00; Wed, 31 Jan 2001 15:46:20 +0100 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.11.1/8.11.1) with ESMTP id f0VEO4f23653; Wed, 31 Jan 2001 15:24:05 +0100 (CET) (envelope-from netchild@Leidinger.net) Message-Id: <200101311424.f0VEO4f23653@Magelan.Leidinger.net> Date: Wed, 31 Jan 2001 15:24:03 +0100 (CET) From: Alexander Leidinger Subject: Re: Voodoo3 + XFree4 + DRM - simple_lock ? :-) To: akm@mail.theinternet.com.au Cc: current@FreeBSD.ORG In-Reply-To: <20010131045430.R11513@zeus.theinternet.com.au> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 31 Jan, Andrew Kenneth Milton wrote: > Glide Libraries: > > Glide3x_devel-2.2-2.i386.rpm > to install; > rpm2cpio Glide3x_devel-2.2-2.i386.rpm | cpio -i -d > cp -r usr/include/glide3 /usr/include Shouldn't this be /usr/local/include ... > Glide_V3-DRI-3.10-6.src.rpm > to install; > rpm2cpio Glide_V3-DRI-3.10-6.src.rpm | cpio -i > You'll get a Glide3.10.tar.gz > unpack that in a new directory; > mkdir glide3 > cd glide3 > tar zxvf ../Glide3.10.tar.gz > make -f makefile.linux > look in the lib directory > some of the symlinks are hosed, and will need to be fixed > cp the glide3 libraries to /usr/lib ... and /usr/local/lib? I tried to get the rpms from 3dfx.com, but it - didn't resolves linux.3dfx.com - isn't possible to get a response from ftp1.3dfx.com from here. I also tried to search it with google, but the first 10 results link either to linux.3dfx.com or 3dfxgamers.com (I can't get a response from 3dfxgamers too). Do you know of some other location where I can get the rpms from? It's not that important for me, I have to wait until there's a mtx_* version. Bye, Alexander. -- It is easier to fix Unix than to live with NT. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 31 6:53:49 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.theinternet.com.au (zeus.theinternet.com.au [203.34.176.2]) by hub.freebsd.org (Postfix) with ESMTP id 626CF37B491 for ; Wed, 31 Jan 2001 06:53:27 -0800 (PST) Received: (from akm@localhost) by mail.theinternet.com.au (8.9.3/8.9.3) id BAA55428; Thu, 1 Feb 2001 01:00:03 +1000 (EST) (envelope-from akm) Date: Thu, 1 Feb 2001 01:00:02 +1000 From: Andrew Kenneth Milton To: Alexander Leidinger Cc: akm@mail.theinternet.com.au, current@FreeBSD.ORG Subject: Re: Voodoo3 + XFree4 + DRM - simple_lock ? :-) Message-ID: <20010201010002.V11513@zeus.theinternet.com.au> References: <20010131045430.R11513@zeus.theinternet.com.au> <200101311424.f0VEO4f23653@Magelan.Leidinger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <200101311424.f0VEO4f23653@Magelan.Leidinger.net>; from Alexander Leidinger on Wed, Jan 31, 2001 at 03:24:03PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG +-------[ Alexander Leidinger ]---------------------- | On 31 Jan, Andrew Kenneth Milton wrote: | | > Glide Libraries: | > | > Glide3x_devel-2.2-2.i386.rpm | > to install; | > rpm2cpio Glide3x_devel-2.2-2.i386.rpm | cpio -i -d | > cp -r usr/include/glide3 /usr/include | | Shouldn't this be /usr/local/include ... *sigh* I wish... | | > Glide_V3-DRI-3.10-6.src.rpm | > to install; | > rpm2cpio Glide_V3-DRI-3.10-6.src.rpm | cpio -i | > You'll get a Glide3.10.tar.gz | > unpack that in a new directory; | > mkdir glide3 | > cd glide3 | > tar zxvf ../Glide3.10.tar.gz | > make -f makefile.linux | > look in the lib directory | > some of the symlinks are hosed, and will need to be fixed | > cp the glide3 libraries to /usr/lib | | ... and /usr/local/lib? Things that want glide look in only /usr/include/glide3 and /usr/lib (I suspect linuxism). For the pain it was causing it wasn't worth fretting over the location of a few files and a directory.... If I was making a port I'd probably make the effort to put things in their 'proper' place. | I tried to get the rpms from 3dfx.com, but it | - didn't resolves linux.3dfx.com | - isn't possible to get a response from ftp1.3dfx.com | from here. 3dfx.sourceforge.net is where they live now I believe... -- Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew Milton The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | ACN: 082 081 472 ABN: 83 082 081 472 | M:+61 416 022 411 | Carpe Daemon PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 31 7: 2: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from blizzard.sabbo.net (ns.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id 4743837B491 for ; Wed, 31 Jan 2001 07:00:27 -0800 (PST) Received: from vic.sabbo.net (root@vic.sabbo.net [193.193.218.112]) by blizzard.sabbo.net (8.10.1/8.10.1) with ESMTP id f0VExiT03601; Wed, 31 Jan 2001 16:59:59 +0200 Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.11.1/8.9.3) with ESMTP id f0VExn861426; Wed, 31 Jan 2001 16:59:49 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-ID: <3A782864.AE795925@FreeBSD.org> Date: Wed, 31 Jan 2001 16:59:49 +0200 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: "Andrey A. Chernov" Cc: eischen@vigrid.com, current@FreeBSD.org Subject: Re: New threads way questions References: <20010131174457.A19255@nagual.pp.ru> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Andrey A. Chernov" wrote: > I have some questions about new threads way. Daniel says that new way is: > > > gcc -Wall -o foo foo.c -lc_r > > 1) What about libgcc_r.a? Is it picked automatically in this case or > not? Is it ever needed now? libgcc_r is gone (merged into libgcc.a). In the meantime you should replace it manually with a symlink to libgcc.a (many ports still assume that gcc_r exists). > 2) Is new way is backward-compatible with old way? I.e. can we just change > ports to use new way and assume that still works on -stable? This issue is actually is more complicated than that. While this change has been MFC'ed to the stable, but this option is still required for the older versions (4.2-RELEASE and downward), so ideally __FreeBSD_version should be bumped and -lgcc_r placed into a conditional in all ports that make use of gcc_r. > 3) Is -D_THREAD_SAFE required now? AFAIK yes. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 31 7: 3:26 2001 Delivered-To: freebsd-current@freebsd.org Received: from hcarp00g.ca.nortel.com (unknown [47.248.133.58]) by hub.freebsd.org (Postfix) with ESMTP id 7455937B4EC for ; Wed, 31 Jan 2001 07:02:49 -0800 (PST) Received: from hcarp00g.ca.nortel.com (hcarp00g.ca.nortel.com [47.196.31.114]) by hcarp00g.ca.nortel.com (8.11.1/8.11.1) with ESMTP id f0VF6XE06180; Wed, 31 Jan 2001 10:06:34 -0500 (EST) (envelope-from atrens@nortelnetworks.com) Date: Wed, 31 Jan 2001 10:06:33 -0500 (EST) From: Andrew Atrens X-X-Sender: To: Andrew Kenneth Milton Cc: Subject: Re: Voodoo3 + XFree4 + DRM - simple_lock ? :-) In-Reply-To: <20010131045430.R11513@zeus.theinternet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-443972561-980953593=:5875" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-443972561-980953593=:5875 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 31 Jan 2001, Andrew Kenneth Milton wrote: > I've made a roadmap to getting hardware accel 3d support using a Voodoo3 > under XFree-4. I've attached it in case anyone is interested. I've made some patches for this that I submitted to the XFree guys about a month ago. On the glide side, I've been using the latest one in the DRI project's cvs - it requires a bunch of little patches that I'm now trying to get into shape. > I've only done this using a PCI Voodoo 3 2000 Card, but, I'd assume if your > card is working correctly then this will probably also work for you with > some minor modifications. Yup, I've tried a 3-2000, 3-3500, 4-4500, and a 5-5500, and they all work okay, with some minor nigglies. > > If you're using a 3dfx card, you'll need to grab the Glide SDK and install > the headers. And you'll need to grab the source for Glide 3 and install the > libraries. It compiled ok here, so I don't anticipate too many problems. > > ------------------------------------------------------------------------ > Glide Libraries: > You'll want to build the 'h5' library for the Voodoo4/5, the 'h3' library for Voodoo3, and the 'cvg' library for Voodoo2. The CVS build recipe (for linux) is at dri.sourceforge.net. > > ------------------------------------------------------------------------ > > This is for XFree-4.0.1 port revision 9 through to (so far) > XFree-4.0.2 port revision 5 > > cd /usr/ports/x11/XFree-4 > make extract > make patch > make configure (answer the questions). > > edit work/xc/config/cf/FreeBSD.cf > > and add; > > #define BuildXF86DRM YES > #define BuildXF86DRI YES > #define HasGlide3 YES > > At the bottom before the > > #include > > cd work/xc/programs/Xserver/hw/xfree86/os-support/bsd/drm/kernel > > Someone fell asleep at the wheel here over at VA-Linux, I assume it > was a CVS snapshot that was half finished... but, other than this > thing, good work :-) Moving target I suppose. Most of the work is older than 6 months. Doug Rabson appears to have done a lot of it. > > Basically you want to change all references to SYSCTL_HANDLER_ARGS > to (SYSCTL_HANDLER_ARGS) in; > drmP.h > drm/memory.c > drm/sysctl.c > I've attached a patch. > edit tdfx/tdfx_drv.c and change > callout_init(&dev->timer) to > callout_init(&dev->timer,0) this change is smp-ng specific (it's not in the 4.x tree). btw, it would be nice to be able to change that '0' to a '1' :) .. > > go back to the top of your XFree-4 tree and do; > make > make install (if you already have XFree 4 installed you can probably > skip this and continue on from here to get the kernel modules you need). > > Now you have to wander back down to > work/xc/programs/Xserver/hw/xfree86/os-support/bsd/drm/kernel in the XFree4.0.2-cvs you actually need to do a 'make -f Makefile.bsd' > > copy drm.ko to /usr/local/modules (or somewhere else convenient). > and copy tdfx/tdfx.ko to /usr/local/modules/tdfx_drm.ko (this clashes > with an existing native tdfx module for 'older' hardware). If this > wasn't built automatically just type make in the tdfx directory and it > should be built for you. ok. I didn't notice a clash. > 3D acceleration only works in 16bpp mode, so make sure you're running > with your depth set to 16 when you start your XFree 4. On the new Xfree it works in 24bpp mode too, but slightly slower - I see only about 40fps with the pulsar hack on my 5500. Andrew. --0-443972561-980953593=:5875 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="os-support.patch" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: os-support Content-Disposition: attachment; filename="os-support.patch" KioqIHhjL3Byb2dyYW1zL1hzZXJ2ZXIvaHcveGZyZWU4Ni9vcy1zdXBwb3J0 L2JzZC9kcm0va2VybmVsL2RybS9tZW1vcnkuYy5vbGQJRnJpIEp1biAxNiAy MDowMzozMCAyMDAwDQotLS0geGMvcHJvZ3JhbXMvWHNlcnZlci9ody94ZnJl ZTg2L29zLXN1cHBvcnQvYnNkL2RybS9rZXJuZWwvZHJtL21lbW9yeS5jCUZy aSBKYW4gIDUgMDA6MDA6MDggMjAwMQ0KKioqKioqKioqKioqKioqDQoqKiog OTUsMTAxICoqKioNCiAgDQogIC8qIGRybV9tZW1faW5mbyBpcyBjYWxsZWQg d2hlbmV2ZXIgYSBwcm9jZXNzIHJlYWRzIC9kZXYvZHJtL21lbS4gKi8NCiAg DQohIHN0YXRpYyBpbnQgX2RybV9tZW1faW5mbyBTWVNDVExfSEFORExFUl9B UkdTDQogIHsNCiAgCWRybV9tZW1fc3RhdHNfdCAqcHQ7DQogIAljaGFyIGJ1 ZlsxMjhdOw0KLS0tIDk1LDEwMSAtLS0tDQogIA0KICAvKiBkcm1fbWVtX2lu Zm8gaXMgY2FsbGVkIHdoZW5ldmVyIGEgcHJvY2VzcyByZWFkcyAvZGV2L2Ry bS9tZW0uICovDQogIA0KISBzdGF0aWMgaW50IF9kcm1fbWVtX2luZm8gKFNZ U0NUTF9IQU5ETEVSX0FSR1MpDQogIHsNCiAgCWRybV9tZW1fc3RhdHNfdCAq cHQ7DQogIAljaGFyIGJ1ZlsxMjhdOw0KKioqKioqKioqKioqKioqDQoqKiog MTI3LDEzMyAqKioqDQogIAlyZXR1cm4gMDsNCiAgfQ0KICANCiEgaW50IGRy bV9tZW1faW5mbyBTWVNDVExfSEFORExFUl9BUkdTDQogIHsNCiAgCWludCBy ZXQ7DQogIAkNCi0tLSAxMjcsMTMzIC0tLS0NCiAgCXJldHVybiAwOw0KICB9 DQogIA0KISBpbnQgZHJtX21lbV9pbmZvIChTWVNDVExfSEFORExFUl9BUkdT KQ0KICB7DQogIAlpbnQgcmV0Ow0KICAJDQoqKiogeGMvcHJvZ3JhbXMvWHNl cnZlci9ody94ZnJlZTg2L29zLXN1cHBvcnQvYnNkL2RybS9rZXJuZWwvZHJt L3N5c2N0bC5jLm9sZAlGcmkgSnVuIDE2IDIwOjAzOjMxIDIwMDANCi0tLSB4 Yy9wcm9ncmFtcy9Yc2VydmVyL2h3L3hmcmVlODYvb3Mtc3VwcG9ydC9ic2Qv ZHJtL2tlcm5lbC9kcm0vc3lzY3RsLmMJRnJpIEphbiAgNSAwMDowMDoxMyAy MDAxDQoqKioqKioqKioqKioqKioNCioqKiAzNSw1NSAqKioqDQogIA0KICBT WVNDVExfTk9ERShfaHcsIE9JRF9BVVRPLCBkcmksIENUTEZMQUdfUlcsIDAs ICJEUkkgR3JhcGhpY3MiKTsNCiAgDQohIHN0YXRpYyBpbnQJICAgZHJtX25h bWVfaW5mbyBTWVNDVExfSEFORExFUl9BUkdTOw0KISBzdGF0aWMgaW50CSAg IGRybV92bV9pbmZvIFNZU0NUTF9IQU5ETEVSX0FSR1M7DQohIHN0YXRpYyBp bnQJICAgZHJtX2NsaWVudHNfaW5mbyBTWVNDVExfSEFORExFUl9BUkdTOw0K ISBzdGF0aWMgaW50CSAgIGRybV9xdWV1ZXNfaW5mbyBTWVNDVExfSEFORExF Ul9BUkdTOw0KISBzdGF0aWMgaW50CSAgIGRybV9idWZzX2luZm8gU1lTQ1RM X0hBTkRMRVJfQVJHUzsNCiAgI2lmIERSTV9ERUJVR19DT0RFeHgNCiEgc3Rh dGljIGludAkgICBkcm1fdm1hX2luZm8gU1lTQ1RMX0hBTkRMRVJfQVJHUzsN CiAgI2VuZGlmDQogICNpZiBEUk1fRE1BX0hJU1RPR1JBTQ0KISBzdGF0aWMg aW50CSAgIGRybV9oaXN0b19pbmZvIFNZU0NUTF9IQU5ETEVSX0FSR1M7DQog ICNlbmRpZg0KICANCiAgc3RydWN0IGRybV9zeXNjdGxfbGlzdCB7DQogIAlj b25zdCBjaGFyICpuYW1lOw0KISAJaW50CSAgICgqZikgU1lTQ1RMX0hBTkRM RVJfQVJHUzsNCiAgfSBkcm1fc3lzY3RsX2xpc3RbXSA9IHsNCiAgCXsgIm5h bWUiLCAgICBkcm1fbmFtZV9pbmZvICAgIH0sDQogIAl7ICJtZW0iLCAgICAg ZHJtX21lbV9pbmZvICAgICB9LA0KLS0tIDM1LDU1IC0tLS0NCiAgDQogIFNZ U0NUTF9OT0RFKF9odywgT0lEX0FVVE8sIGRyaSwgQ1RMRkxBR19SVywgMCwg IkRSSSBHcmFwaGljcyIpOw0KICANCiEgc3RhdGljIGludAkgICBkcm1fbmFt ZV9pbmZvIChTWVNDVExfSEFORExFUl9BUkdTKTsNCiEgc3RhdGljIGludAkg ICBkcm1fdm1faW5mbyAoU1lTQ1RMX0hBTkRMRVJfQVJHUyk7DQohIHN0YXRp YyBpbnQJICAgZHJtX2NsaWVudHNfaW5mbyAoU1lTQ1RMX0hBTkRMRVJfQVJH Uyk7DQohIHN0YXRpYyBpbnQJICAgZHJtX3F1ZXVlc19pbmZvIChTWVNDVExf SEFORExFUl9BUkdTKTsNCiEgc3RhdGljIGludAkgICBkcm1fYnVmc19pbmZv IChTWVNDVExfSEFORExFUl9BUkdTKTsNCiAgI2lmIERSTV9ERUJVR19DT0RF eHgNCiEgc3RhdGljIGludAkgICBkcm1fdm1hX2luZm8gKFNZU0NUTF9IQU5E TEVSX0FSR1MpOw0KICAjZW5kaWYNCiAgI2lmIERSTV9ETUFfSElTVE9HUkFN DQohIHN0YXRpYyBpbnQJICAgZHJtX2hpc3RvX2luZm8gKFNZU0NUTF9IQU5E TEVSX0FSR1MpOw0KICAjZW5kaWYNCiAgDQogIHN0cnVjdCBkcm1fc3lzY3Rs X2xpc3Qgew0KICAJY29uc3QgY2hhciAqbmFtZTsNCiEgCWludAkgICAoKmYp IChTWVNDVExfSEFORExFUl9BUkdTKTsNCiAgfSBkcm1fc3lzY3RsX2xpc3Rb XSA9IHsNCiAgCXsgIm5hbWUiLCAgICBkcm1fbmFtZV9pbmZvICAgIH0sDQog IAl7ICJtZW0iLCAgICAgZHJtX21lbV9pbmZvICAgICB9LA0KKioqKioqKioq KioqKioqDQoqKiogMTM3LDE0MyAqKioqDQogIAlyZXR1cm4gMDsNCiAgfQ0K ICANCiEgc3RhdGljIGludCBkcm1fbmFtZV9pbmZvIFNZU0NUTF9IQU5ETEVS X0FSR1MNCiAgew0KICAJZHJtX2RldmljZV90ICpkZXYgPSBhcmcxOw0KICAJ Y2hhciBidWZbMTI4XTsNCi0tLSAxMzcsMTQzIC0tLS0NCiAgCXJldHVybiAw Ow0KICB9DQogIA0KISBzdGF0aWMgaW50IGRybV9uYW1lX2luZm8gKFNZU0NU TF9IQU5ETEVSX0FSR1MpDQogIHsNCiAgCWRybV9kZXZpY2VfdCAqZGV2ID0g YXJnMTsNCiAgCWNoYXIgYnVmWzEyOF07DQoqKioqKioqKioqKioqKioNCioq KiAxNTUsMTYxICoqKioNCiAgCXJldHVybiAwOw0KICB9DQogIA0KISBzdGF0 aWMgaW50IF9kcm1fdm1faW5mbyBTWVNDVExfSEFORExFUl9BUkdTDQogIHsN CiAgCWRybV9kZXZpY2VfdCAqZGV2ID0gYXJnMTsNCiAgCWRybV9tYXBfdCAg ICAqbWFwOw0KLS0tIDE1NSwxNjEgLS0tLQ0KICAJcmV0dXJuIDA7DQogIH0N CiAgDQohIHN0YXRpYyBpbnQgX2RybV92bV9pbmZvIChTWVNDVExfSEFORExF Ul9BUkdTKQ0KICB7DQogIAlkcm1fZGV2aWNlX3QgKmRldiA9IGFyZzE7DQog IAlkcm1fbWFwX3QgICAgKm1hcDsNCioqKioqKioqKioqKioqKg0KKioqIDE5 MiwxOTggKioqKg0KICAJcmV0dXJuIDA7DQogIH0NCiAgDQohIHN0YXRpYyBp bnQgZHJtX3ZtX2luZm8gU1lTQ1RMX0hBTkRMRVJfQVJHUw0KICB7DQogIAlk cm1fZGV2aWNlX3QgKmRldiA9IGFyZzE7DQogIAlpbnQJICAgICByZXQ7DQot LS0gMTkyLDE5OCAtLS0tDQogIAlyZXR1cm4gMDsNCiAgfQ0KICANCiEgc3Rh dGljIGludCBkcm1fdm1faW5mbyAoU1lTQ1RMX0hBTkRMRVJfQVJHUykNCiAg ew0KICAJZHJtX2RldmljZV90ICpkZXYgPSBhcmcxOw0KICAJaW50CSAgICAg cmV0Ow0KKioqKioqKioqKioqKioqDQoqKiogMjA1LDIxMSAqKioqDQogIH0N CiAgDQogIA0KISBzdGF0aWMgaW50IF9kcm1fcXVldWVzX2luZm8gU1lTQ1RM X0hBTkRMRVJfQVJHUw0KICB7DQogIAlkcm1fZGV2aWNlX3QgKmRldiA9IGFy ZzE7DQogIAlpbnQJICAgICBpOw0KLS0tIDIwNSwyMTEgLS0tLQ0KICB9DQog IA0KICANCiEgc3RhdGljIGludCBfZHJtX3F1ZXVlc19pbmZvIChTWVNDVExf SEFORExFUl9BUkdTKQ0KICB7DQogIAlkcm1fZGV2aWNlX3QgKmRldiA9IGFy ZzE7DQogIAlpbnQJICAgICBpOw0KKioqKioqKioqKioqKioqDQoqKiogMjQz LDI0OSAqKioqDQogIAlyZXR1cm4gMDsNCiAgfQ0KICANCiEgc3RhdGljIGlu dCBkcm1fcXVldWVzX2luZm8gU1lTQ1RMX0hBTkRMRVJfQVJHUw0KICB7DQog IAlkcm1fZGV2aWNlX3QgKmRldiA9IGFyZzE7DQogIAlpbnQJICAgICByZXQ7 DQotLS0gMjQzLDI0OSAtLS0tDQogIAlyZXR1cm4gMDsNCiAgfQ0KICANCiEg c3RhdGljIGludCBkcm1fcXVldWVzX2luZm8gKFNZU0NUTF9IQU5ETEVSX0FS R1MpDQogIHsNCiAgCWRybV9kZXZpY2VfdCAqZGV2ID0gYXJnMTsNCiAgCWlu dAkgICAgIHJldDsNCioqKioqKioqKioqKioqKg0KKioqIDI1NywyNjMgKioq Kg0KICAvKiBkcm1fYnVmc19pbmZvIGlzIGNhbGxlZCB3aGVuZXZlciBhIHBy b2Nlc3MgcmVhZHMNCiAgICAgaHcuZHJpLjAuYnVmcy4gKi8NCiAgDQohIHN0 YXRpYyBpbnQgX2RybV9idWZzX2luZm8gU1lTQ1RMX0hBTkRMRVJfQVJHUw0K ICB7DQogIAlkcm1fZGV2aWNlX3QJICpkZXYgPSBhcmcxOw0KICAJZHJtX2Rl dmljZV9kbWFfdCAqZG1hID0gZGV2LT5kbWE7DQotLS0gMjU3LDI2MyAtLS0t DQogIC8qIGRybV9idWZzX2luZm8gaXMgY2FsbGVkIHdoZW5ldmVyIGEgcHJv Y2VzcyByZWFkcw0KICAgICBody5kcmkuMC5idWZzLiAqLw0KICANCiEgc3Rh dGljIGludCBfZHJtX2J1ZnNfaW5mbyAoU1lTQ1RMX0hBTkRMRVJfQVJHUykN CiAgew0KICAJZHJtX2RldmljZV90CSAqZGV2ID0gYXJnMTsNCiAgCWRybV9k ZXZpY2VfZG1hX3QgKmRtYSA9IGRldi0+ZG1hOw0KKioqKioqKioqKioqKioq DQoqKiogMjkzLDI5OSAqKioqDQogIAlyZXR1cm4gMDsNCiAgfQ0KICANCiEg c3RhdGljIGludCBkcm1fYnVmc19pbmZvIFNZU0NUTF9IQU5ETEVSX0FSR1MN CiAgew0KICAJZHJtX2RldmljZV90ICpkZXYgPSBhcmcxOw0KICAJaW50CSAg ICAgcmV0Ow0KLS0tIDI5MywyOTkgLS0tLQ0KICAJcmV0dXJuIDA7DQogIH0N CiAgDQohIHN0YXRpYyBpbnQgZHJtX2J1ZnNfaW5mbyAoU1lTQ1RMX0hBTkRM RVJfQVJHUykNCiAgew0KICAJZHJtX2RldmljZV90ICpkZXYgPSBhcmcxOw0K ICAJaW50CSAgICAgcmV0Ow0KKioqKioqKioqKioqKioqDQoqKiogMzA1LDMx MSAqKioqDQogIH0NCiAgDQogIA0KISBzdGF0aWMgaW50IF9kcm1fY2xpZW50 c19pbmZvIFNZU0NUTF9IQU5ETEVSX0FSR1MNCiAgew0KICAJZHJtX2Rldmlj ZV90ICpkZXYgPSBhcmcxOw0KICAJZHJtX2ZpbGVfdCAgICpwcml2Ow0KLS0t IDMwNSwzMTEgLS0tLQ0KICB9DQogIA0KICANCiEgc3RhdGljIGludCBfZHJt X2NsaWVudHNfaW5mbyAoU1lTQ1RMX0hBTkRMRVJfQVJHUykNCiAgew0KICAJ ZHJtX2RldmljZV90ICpkZXYgPSBhcmcxOw0KICAJZHJtX2ZpbGVfdCAgICpw cml2Ow0KKioqKioqKioqKioqKioqDQoqKiogMzI3LDMzMyAqKioqDQogIAly ZXR1cm4gMDsNCiAgfQ0KICANCiEgc3RhdGljIGludCBkcm1fY2xpZW50c19p bmZvIFNZU0NUTF9IQU5ETEVSX0FSR1MNCiAgew0KICAJZHJtX2RldmljZV90 ICpkZXYgPSBhcmcxOw0KICAJaW50CSAgICAgcmV0Ow0KLS0tIDMyNywzMzMg LS0tLQ0KICAJcmV0dXJuIDA7DQogIH0NCiAgDQohIHN0YXRpYyBpbnQgZHJt X2NsaWVudHNfaW5mbyAoU1lTQ1RMX0hBTkRMRVJfQVJHUykNCiAgew0KICAJ ZHJtX2RldmljZV90ICpkZXYgPSBhcmcxOw0KICAJaW50CSAgICAgcmV0Ow0K KioqKioqKioqKioqKioqDQoqKiogMzQwLDM0NiAqKioqDQogIA0KICAjaWYg RFJNX0RFQlVHX0NPREV4eA0KICANCiEgc3RhdGljIGludCBfZHJtX3ZtYV9p bmZvIFNZU0NUTF9IQU5ETEVSX0FSR1MNCiAgew0KICAJZHJtX2RldmljZV90 CSAgICAgICpkZXYgPSBhcmcxOw0KICAJZHJtX3ZtYV9lbnRyeV90CSAgICAg ICpwdDsNCi0tLSAzNDAsMzQ2IC0tLS0NCiAgDQogICNpZiBEUk1fREVCVUdf Q09ERXh4DQogIA0KISBzdGF0aWMgaW50IF9kcm1fdm1hX2luZm8gKFNZU0NU TF9IQU5ETEVSX0FSR1MpDQogIHsNCiAgCWRybV9kZXZpY2VfdAkgICAgICAq ZGV2ID0gYXJnMTsNCiAgCWRybV92bWFfZW50cnlfdAkgICAgICAqcHQ7DQoq KioqKioqKioqKioqKioNCioqKiA0MTIsNDE4ICoqKioNCiAgCXJldHVybiAw Ow0KICB9DQogIA0KISBzdGF0aWMgaW50IGRybV92bWFfaW5mbyBTWVNDVExf SEFORExFUl9BUkdTDQogIHsNCiAgCWRybV9kZXZpY2VfdCAqZGV2ID0gYXJn MTsNCiAgCWludAkgICAgIHJldDsNCi0tLSA0MTIsNDE4IC0tLS0NCiAgCXJl dHVybiAwOw0KICB9DQogIA0KISBzdGF0aWMgaW50IGRybV92bWFfaW5mbyAo U1lTQ1RMX0hBTkRMRVJfQVJHUykNCiAgew0KICAJZHJtX2RldmljZV90ICpk ZXYgPSBhcmcxOw0KICAJaW50CSAgICAgcmV0Ow0KKioqKioqKioqKioqKioq DQoqKiogNDI2LDQzMiAqKioqDQogIA0KICANCiAgI2lmIERSTV9ETUFfSElT VE9HUkFNDQohIHN0YXRpYyBpbnQgX2RybV9oaXN0b19pbmZvIFNZU0NUTF9I QU5ETEVSX0FSR1MNCiAgew0KICAJZHJtX2RldmljZV90CSAqZGV2ID0gYXJn MTsNCiAgCWRybV9kZXZpY2VfZG1hX3QgKmRtYSA9IGRldi0+ZG1hOw0KLS0t IDQyNiw0MzIgLS0tLQ0KICANCiAgDQogICNpZiBEUk1fRE1BX0hJU1RPR1JB TQ0KISBzdGF0aWMgaW50IF9kcm1faGlzdG9faW5mbyAoU1lTQ1RMX0hBTkRM RVJfQVJHUykNCiAgew0KICAJZHJtX2RldmljZV90CSAqZGV2ID0gYXJnMTsN CiAgCWRybV9kZXZpY2VfZG1hX3QgKmRtYSA9IGRldi0+ZG1hOw0KKioqKioq KioqKioqKioqDQoqKiogNTQxLDU0NyAqKioqDQogIAlyZXR1cm4gMDsNCiAg fQ0KICANCiEgc3RhdGljIGludCBkcm1faGlzdG9faW5mbyBTWVNDVExfSEFO RExFUl9BUkdTDQogIHsNCiAgCWRybV9kZXZpY2VfdCAqZGV2ID0gYXJnMTsN CiAgCWludAkgICAgIHJldDsNCi0tLSA1NDEsNTQ3IC0tLS0NCiAgCXJldHVy biAwOw0KICB9DQogIA0KISBzdGF0aWMgaW50IGRybV9oaXN0b19pbmZvIChT WVNDVExfSEFORExFUl9BUkdTKQ0KICB7DQogIAlkcm1fZGV2aWNlX3QgKmRl diA9IGFyZzE7DQogIAlpbnQJICAgICByZXQ7DQoqKiogeGMvcHJvZ3JhbXMv WHNlcnZlci9ody94ZnJlZTg2L29zLXN1cHBvcnQvYnNkL2RybS9rZXJuZWwv Z2FtbWEvTWFrZWZpbGUub2xkCUZyaSBKdW4gMTYgMjA6MDM6MzEgMjAwMA0K LS0tIHhjL3Byb2dyYW1zL1hzZXJ2ZXIvaHcveGZyZWU4Ni9vcy1zdXBwb3J0 L2JzZC9kcm0va2VybmVsL2dhbW1hL01ha2VmaWxlCUZyaSBKYW4gIDUgMDA6 MDQ6NTkgMjAwMQ0KKioqKioqKioqKioqKioqDQoqKiogMyw5ICoqKioNCiAg S01PRAk9IGdhbW1hDQogIFNSQ1MgICAgPSBnYW1tYV9kcnYuYyBnYW1tYV9k bWEuYw0KICBTUkNTICAgKz0gZGV2aWNlX2lmLmggYnVzX2lmLmggcGNpX2lm LmgNCiEgQ0ZMQUdTICs9ICR7REVCVUdfRkxBR1N9IC1JLi4NCiAgS01PRERF UFMgPSBkcm0NCiAgDQogIEA6DQotLS0gMyw5IC0tLS0NCiAgS01PRAk9IGdh bW1hDQogIFNSQ1MgICAgPSBnYW1tYV9kcnYuYyBnYW1tYV9kbWEuYw0KICBT UkNTICAgKz0gZGV2aWNlX2lmLmggYnVzX2lmLmggcGNpX2lmLmgNCiEgQ0ZM QUdTICs9ICR7REVCVUdfRkxBR1N9IC1JLiAtSS4uDQogIEtNT0RERVBTID0g ZHJtDQogIA0KICBAOg0KKioqIHhjL3Byb2dyYW1zL1hzZXJ2ZXIvaHcveGZy ZWU4Ni9vcy1zdXBwb3J0L2JzZC9kcm0va2VybmVsL2dhbW1hL2dhbW1hX2Ry di5jLm9sZAlGcmkgSnVuIDE2IDIwOjAzOjMxIDIwMDANCi0tLSB4Yy9wcm9n cmFtcy9Yc2VydmVyL2h3L3hmcmVlODYvb3Mtc3VwcG9ydC9ic2QvZHJtL2tl cm5lbC9nYW1tYS9nYW1tYV9kcnYuYwlGcmkgSmFuICA1IDAwOjA1OjMxIDIw MDENCioqKioqKioqKioqKioqKg0KKioqIDIwOSwyMTUgKioqKg0KICAJZGV2 LT5sYXN0X2NvbnRleHQgICA9IDA7DQogIAlkZXYtPmxhc3Rfc3dpdGNoICAg ID0gMDsNCiAgCWRldi0+bGFzdF9jaGVja2VkICAgPSAwOw0KISAJY2FsbG91 dF9pbml0KCZkZXYtPnRpbWVyKTsNCiAgCWRldi0+Y29udGV4dF93YWl0ICAg PSAwOw0KICAjaWYgRFJNX0RNQV9ISVNUTw0KICAJbWVtc2V0KCZkZXYtPmhp c3RvLCAwLCBzaXplb2YoZGV2LT5oaXN0bykpOw0KLS0tIDIwOSwyMTUgLS0t LQ0KICAJZGV2LT5sYXN0X2NvbnRleHQgICA9IDA7DQogIAlkZXYtPmxhc3Rf c3dpdGNoICAgID0gMDsNCiAgCWRldi0+bGFzdF9jaGVja2VkICAgPSAwOw0K ISAJY2FsbG91dF9pbml0KCZkZXYtPnRpbWVyLCAwKTsNCiAgCWRldi0+Y29u dGV4dF93YWl0ICAgPSAwOw0KICAjaWYgRFJNX0RNQV9ISVNUTw0KICAJbWVt c2V0KCZkZXYtPmhpc3RvLCAwLCBzaXplb2YoZGV2LT5oaXN0bykpOw0KKioq IHhjL3Byb2dyYW1zL1hzZXJ2ZXIvaHcveGZyZWU4Ni9vcy1zdXBwb3J0L2Jz ZC9kcm0va2VybmVsL3RkZngvdGRmeF9kcnYuYy5vbGQJRnJpIEp1biAxNiAy MDowMzozMiAyMDAwDQotLS0geGMvcHJvZ3JhbXMvWHNlcnZlci9ody94ZnJl ZTg2L29zLXN1cHBvcnQvYnNkL2RybS9rZXJuZWwvdGRmeC90ZGZ4X2Rydi5j CUZyaSBKYW4gIDUgMDA6MDQ6MzEgMjAwMQ0KKioqKioqKioqKioqKioqDQoq KiogNjQsNjkgKioqKg0KLS0tIDY0LDczIC0tLS0NCiAgCWNhc2UgMHgwMDA1 MTIxYToNCiAgCQlzID0gIjNEZnggVm9vZG9vIDMgZ3JhcGhpY3MgYWNjZWxl cmF0b3IiOw0KICAJCWJyZWFrOw0KKyANCisgCWNhc2UgMHgwMDA5MTIxYToN CisgCQlzID0gIjNEZnggVm9vZG9vIDUgZ3JhcGhpY3MgYWNjZWxlcmF0b3Ii Ow0KKyAJCWJyZWFrOw0KICAJfQ0KICANCiAgCWlmIChzKSB7DQoqKioqKioq KioqKioqKioNCioqKiAyMTMsMjE5ICoqKioNCiAgCWRldi0+bGFzdF9jb250 ZXh0ICAgPSAwOw0KICAJZGV2LT5sYXN0X3N3aXRjaCAgICA9IDA7DQogIAlk ZXYtPmxhc3RfY2hlY2tlZCAgID0gMDsNCiEgCWNhbGxvdXRfaW5pdCgmZGV2 LT50aW1lcik7DQogIAlkZXYtPmNvbnRleHRfd2FpdCAgID0gMDsNCiAgDQog IAl0aW1lc3BlY2NsZWFyKCZkZXYtPmN0eF9zdGFydCk7DQotLS0gMjE3LDIy MyAtLS0tDQogIAlkZXYtPmxhc3RfY29udGV4dCAgID0gMDsNCiAgCWRldi0+ bGFzdF9zd2l0Y2ggICAgPSAwOw0KICAJZGV2LT5sYXN0X2NoZWNrZWQgICA9 IDA7DQohIAljYWxsb3V0X2luaXQoJmRldi0+dGltZXIsMCk7DQogIAlkZXYt PmNvbnRleHRfd2FpdCAgID0gMDsNCiAgDQogIAl0aW1lc3BlY2NsZWFyKCZk ZXYtPmN0eF9zdGFydCk7DQoqKiogeGMvcHJvZ3JhbXMvWHNlcnZlci9ody94 ZnJlZTg2L29zLXN1cHBvcnQvYnNkL2RybS9rZXJuZWwvdGRmeC9NYWtlZmls ZS5vbGQJRnJpIEp1biAxNiAyMDowMzozMiAyMDAwDQotLS0geGMvcHJvZ3Jh bXMvWHNlcnZlci9ody94ZnJlZTg2L29zLXN1cHBvcnQvYnNkL2RybS9rZXJu ZWwvdGRmeC9NYWtlZmlsZQlGcmkgSmFuICA1IDAwOjA0OjI4IDIwMDENCioq KioqKioqKioqKioqKg0KKioqIDMsOSAqKioqDQogIEtNT0QJPSB0ZGZ4DQog IFNSQ1MgICAgPSB0ZGZ4X2Rydi5jIHRkZnhfY29udGV4dC5jDQogIFNSQ1Mg ICArPSBkZXZpY2VfaWYuaCBidXNfaWYuaCBwY2lfaWYuaA0KISBDRkxBR1Mg Kz0gJHtERUJVR19GTEFHU30gLUkuLg0KICBLTU9EREVQUyA9IGRybQ0KICAN CiAgQDoNCi0tLSAzLDkgLS0tLQ0KICBLTU9ECT0gdGRmeA0KICBTUkNTICAg ID0gdGRmeF9kcnYuYyB0ZGZ4X2NvbnRleHQuYw0KICBTUkNTICAgKz0gZGV2 aWNlX2lmLmggYnVzX2lmLmggcGNpX2lmLmgNCiEgQ0ZMQUdTICs9ICR7REVC VUdfRkxBR1N9IC1JLiAtSS4uDQogIEtNT0RERVBTID0gZHJtDQogIA0KICBA Og0KKioqIHhjL3Byb2dyYW1zL1hzZXJ2ZXIvaHcveGZyZWU4Ni9vcy1zdXBw b3J0L2JzZC9kcm0va2VybmVsL2RybVAuaC5vbGQJRnJpIEp1biAxNiAyMDow MzoyOCAyMDAwDQotLS0geGMvcHJvZ3JhbXMvWHNlcnZlci9ody94ZnJlZTg2 L29zLXN1cHBvcnQvYnNkL2RybS9rZXJuZWwvZHJtUC5oCVRodSBKYW4gIDQg MjM6NTc6MzkgMjAwMQ0KKioqKioqKioqKioqKioqDQoqKiogNTk0LDYwMCAq KioqDQogIA0KICAJCQkJLyogTWVtb3J5IG1hbmFnZW1lbnQgc3VwcG9ydCAo bWVtb3J5LmMpICovDQogIGV4dGVybiB2b2lkCSAgICAgZHJtX21lbV9pbml0 KHZvaWQpOw0KISBleHRlcm4gaW50CSAgICAgZHJtX21lbV9pbmZvIFNZU0NU TF9IQU5ETEVSX0FSR1M7DQogIGV4dGVybiB2b2lkCSAgICAgKmRybV9hbGxv YyhzaXplX3Qgc2l6ZSwgaW50IGFyZWEpOw0KICBleHRlcm4gdm9pZAkgICAg ICpkcm1fcmVhbGxvYyh2b2lkICpvbGRwdCwgc2l6ZV90IG9sZHNpemUsIHNp emVfdCBzaXplLA0KICAJCQkJICBpbnQgYXJlYSk7DQotLS0gNTk0LDYwMCAt LS0tDQogIA0KICAJCQkJLyogTWVtb3J5IG1hbmFnZW1lbnQgc3VwcG9ydCAo bWVtb3J5LmMpICovDQogIGV4dGVybiB2b2lkCSAgICAgZHJtX21lbV9pbml0 KHZvaWQpOw0KISBleHRlcm4gaW50CSAgICAgZHJtX21lbV9pbmZvIChTWVND VExfSEFORExFUl9BUkdTKTsNCiAgZXh0ZXJuIHZvaWQJICAgICAqZHJtX2Fs bG9jKHNpemVfdCBzaXplLCBpbnQgYXJlYSk7DQogIGV4dGVybiB2b2lkCSAg ICAgKmRybV9yZWFsbG9jKHZvaWQgKm9sZHB0LCBzaXplX3Qgb2xkc2l6ZSwg c2l6ZV90IHNpemUsDQogIAkJCQkgIGludCBhcmVhKTsNCioqKiB4Yy9wcm9n cmFtcy9Yc2VydmVyL2h3L3hmcmVlODYvb3Mtc3VwcG9ydC94Zjg2X09TbGli Lmgub2xkCVR1ZSBOb3YgMTQgMTY6NTk6MjMgMjAwMA0KLS0tIHhjL3Byb2dy YW1zL1hzZXJ2ZXIvaHcveGZyZWU4Ni9vcy1zdXBwb3J0L3hmODZfT1NsaWIu aAlUaHUgSmFuICA0IDIzOjU1OjEwIDIwMDENCioqKioqKioqKioqKioqKg0K KioqIDQ2OSw0NzUgKioqKg0KICAjICAgaWZkZWYgU1lTQ09OU19TVVBQT1JU DQogICMgICAgZGVmaW5lIENPTVBBVF9TWVNDT05TDQogICMgICAgaWYgZGVm aW5lZChfX0ZyZWVCU0RfXykgfHwgZGVmaW5lZChfX05ldEJTRF9fKSB8fCBk ZWZpbmVkKF9fT3BlbkJTRF9fKQ0KISAjICAgICBpbmNsdWRlIDxtYWNoaW5l L2NvbnNvbGUuaD4NCiAgIyAgICBlbHNlDQogICMgICAgIGluY2x1ZGUgPHN5 cy9jb25zb2xlLmg+DQogICMgICAgZW5kaWYgLyogX19GcmVlQlNEX18gfHwg X19OZXRCU0RfXyB8fCBkZWZpbmVkKF9fT3BlbkJTRF9fKSAqLw0KLS0tIDQ2 OSw0ODAgLS0tLQ0KICAjICAgaWZkZWYgU1lTQ09OU19TVVBQT1JUDQogICMg ICAgZGVmaW5lIENPTVBBVF9TWVNDT05TDQogICMgICAgaWYgZGVmaW5lZChf X0ZyZWVCU0RfXykgfHwgZGVmaW5lZChfX05ldEJTRF9fKSB8fCBkZWZpbmVk KF9fT3BlbkJTRF9fKQ0KISAjICAgICAgIGlmIGRlZmluZWQoX19GcmVlQlNE X18pICYmICBfX0ZyZWVCU0RfXyA+PSA1DQohICMgICAgICAgICAgaW5jbHVk ZSA8c3lzL2NvbnNpby5oPg0KISAjICAgICAgICAgIGluY2x1ZGUgPHN5cy9r YmlvLmg+DQohICMgICAgICAgZWxzZQ0KISAjICAgICAgICAgIGluY2x1ZGUg PG1hY2hpbmUvY29uc29sZS5oPg0KISAjICAgICAgIGVuZGlmDQogICMgICAg ZWxzZQ0KICAjICAgICBpbmNsdWRlIDxzeXMvY29uc29sZS5oPg0KICAjICAg IGVuZGlmIC8qIF9fRnJlZUJTRF9fIHx8IF9fTmV0QlNEX18gfHwgZGVmaW5l ZChfX09wZW5CU0RfXykgKi8NCioqKioqKioqKioqKioqKg0KKioqIDUwNCw1 MTAgKioqKg0KICAjICAgZW5kaWYgLyogV1NDT05TX1NVUFBPUlQgKi8NCiAg IyAgIGlmIGRlZmluZWQoX19GcmVlQlNEX18pDQogICMgICAgdW5kZWYgTU9V U0VfR0VUSU5GTw0KISAjICAgIGluY2x1ZGUgPG1hY2hpbmUvbW91c2UuaD4N CiAgIyAgIGVuZGlmDQogICAgICAvKiBJbmNsdWRlIHRoZXNlIGRlZmluaXRp b25zIGluIGNhc2UgaW9jdGxfcGMuaCBkaWRuJ3QgZ2V0IGluY2x1ZGVkICov DQogICMgICBpZm5kZWYgQ09OU09MRV9YX01PREVfT04NCi0tLSA1MDksNTE5 IC0tLS0NCiAgIyAgIGVuZGlmIC8qIFdTQ09OU19TVVBQT1JUICovDQogICMg ICBpZiBkZWZpbmVkKF9fRnJlZUJTRF9fKQ0KICAjICAgIHVuZGVmIE1PVVNF X0dFVElORk8NCiEgIyAgICBpZiBfX0ZyZWVCU0RfXyA+PSA1DQohICMgICAg ICAgICBpbmNsdWRlIDxzeXMvbW91c2UuaD4NCiEgIyAgICBlbHNlDQohICMg ICAgICAgICBpbmNsdWRlIDxtYWNoaW5lL21vdXNlLmg+DQohICMgICAgZW5k aWYNCiAgIyAgIGVuZGlmDQogICAgICAvKiBJbmNsdWRlIHRoZXNlIGRlZmlu aXRpb25zIGluIGNhc2UgaW9jdGxfcGMuaCBkaWRuJ3QgZ2V0IGluY2x1ZGVk ICovDQogICMgICBpZm5kZWYgQ09OU09MRV9YX01PREVfT04NCg== --0-443972561-980953593=:5875 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="OS_386BSD.patch" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: superprobe patch Content-Disposition: attachment; filename="OS_386BSD.patch" LS0tIHhjL3Byb2dyYW1zL1hzZXJ2ZXIvaHcveGZyZWU4Ni9TdXBlclByb2Jl L09TXzM4NkJTRC5jLm9sZAlGcmkgSnVuIDIzIDE4OjQyOjAyIDIwMDANCisr KyB4Yy9wcm9ncmFtcy9Yc2VydmVyL2h3L3hmcmVlODYvU3VwZXJQcm9iZS9P U18zODZCU0QuYwlGcmkgSmFuICA1IDExOjQxOjQ2IDIwMDENCkBAIC04Myw3 ICs4MywxMiBAQA0KICMgIGVuZGlmDQogIyAgaWZkZWYgU1lTQ09OU19TVVBQ T1JUDQogICAgIC8qIGJvdGgsIEZyZWUgYW5kIE5ldEJTRCBoYXZlIHN5c2Nv bnMgKi8NCi0jICAgaW5jbHVkZSA8bWFjaGluZS9jb25zb2xlLmg+DQorIyAg IGlmIF9fRnJlZUJTRF9fID49IDUNCisjICAgICBpbmNsdWRlIDxzeXMvY29u c2lvLmg+DQorIyAgICAgaW5jbHVkZSA8c3lzL2tiaW8uaD4NCisjICAgZWxz ZQ0KKyMgICAgIGluY2x1ZGUgPG1hY2hpbmUvY29uc29sZS5oPg0KKyMgICBl bmRpZg0KICMgIGVuZGlmDQogIyBlbHNlDQogIyAgaWZkZWYgQ09EUlZfU1VQ UE9SVA0K --0-443972561-980953593=:5875-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 31 7:29:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.newst.irs.ru (newst.irs.ru [212.164.94.1]) by hub.freebsd.org (Postfix) with ESMTP id 266A037B491 for ; Wed, 31 Jan 2001 07:29:29 -0800 (PST) Received: from lark.nsk.bsgdesign.com (lark.nsk.bsgdesign.com [192.168.3.21]) by mail.newst.irs.ru (8.11.1/8.11.0) with ESMTP id f0VFT5487250; Wed, 31 Jan 2001 21:29:06 +0600 (NOVT) (envelope-from fjoe@newst.net) Date: Wed, 31 Jan 2001 21:28:29 +0600 (NOVT) From: Max Khon X-Sender: fjoe@localhost To: "Andrey A. Chernov" Cc: eischen@vigrid.com, current@FreeBSD.ORG Subject: Re: New threads way questions In-Reply-To: <20010131174457.A19255@nagual.pp.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! On Wed, 31 Jan 2001, Andrey A. Chernov wrote: > I have some questions about new threads way. Daniel says that new way is: > > > gcc -Wall -o foo foo.c -lc_r > 1) What about libgcc_r.a? Is it picked automatically in this case or > not? Is it ever needed now? we do not have libgcc_r.a in both -current and -stable anymore > 2) Is new way is backward-compatible with old way? I.e. can we just change > ports to use new way and assume that still works on -stable? no > 3) Is -D_THREAD_SAFE required now? no /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 31 7:32:23 2001 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 86C1837B491 for ; Wed, 31 Jan 2001 07:32:05 -0800 (PST) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id KAA12435; Wed, 31 Jan 2001 10:31:36 -0500 (EST) Date: Wed, 31 Jan 2001 10:31:36 -0500 (EST) From: Daniel Eischen To: "Andrey A. Chernov" Cc: current@freebsd.org Subject: Re: New threads way questions In-Reply-To: <20010131174457.A19255@nagual.pp.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 31 Jan 2001, Andrey A. Chernov wrote: > I have some questions about new threads way. Daniel says that new way is: > > > gcc -Wall -o foo foo.c -lc_r Only in -current, in -stable continue to use -pthread instead of -lc_r. > 1) What about libgcc_r.a? Is it picked automatically in this case or > not? Is it ever needed now? libgcc_r is gone in both -current and -stable. There is only libgcc.a. libgcc_r may still exist for sometime until folks manually delete it, so ports that are built to require it (-lgcc_r) will work on some systems and fail on others. > 2) Is new way is backward-compatible with old way? I.e. can we just change > ports to use new way and assume that still works on -stable? No, -lc_r will not work under -stable. What might make sense is to have a bsd.port.mk knob, THREADSLIB or something like that, that can be automatically set to -lc_r under -current or -pthread under stable. When we get a libpthread, or even if users want to use LinuxThreads, they can change this knob in /etc/make.conf and have their ports built with whatever threads library they want. Under -current, -pthread has been changed to Do The Right Thing and link in both libc_r and libc. All ports should work without changing them under -current, at least for now. But the -pthread option should go away at some point, so ports need to be changed eventually. > 3) Is -D_THREAD_SAFE required now? Not in -current. You should use it in -stable though. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 31 10:39:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id 5AE4137B491 for ; Wed, 31 Jan 2001 10:39:35 -0800 (PST) Received: by shadowmere.student.utwente.nl (Postfix, from userid 1000) id 7506A1F9D; Wed, 31 Jan 2001 19:39:34 +0100 (CET) Date: Wed, 31 Jan 2001 19:39:34 +0100 From: Pascal Hofstee To: freebsd-current@freebsd.org Subject: Re: Bug in tftpd ? Message-ID: <20010131193934.C68538@shadowmere.student.utwente.nl> Reply-To: daeron@shadowmere.student.utwente.nl References: <20010131002024.A77116@shadowmere.student.utwente.nl> <20010131121353.A21533@shadowmere.student.utwente.nl> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="OwLcNYc0lM97+oe1" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010131121353.A21533@shadowmere.student.utwente.nl>; from daeron@shadowmere.student.utwente.nl on Wed, Jan 31, 2001 at 12:13:54PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --OwLcNYc0lM97+oe1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Jan 31, 2001 at 12:13:54PM +0100, Pascal Hofstee wrote: > Patches attached: > Obtained from: NetBSD > > (Committed there about 3 months ago after we first spotted the problem in > their implementation) Ok .. I noticed a minor glitch in my previous patch .. the "unsigned int" should be "unsigned short" Apparently NetBSD still uses the "unsigned int" so may still show the same problem. New patche attached. -- Pascal Hofstee < daeron @ shadowmere . student . utwente . nl > begin LOVE-LETTER-FOR-YOU.TXT.vbs I'm a signature virus. Please copy me and help me spread. end --OwLcNYc0lM97+oe1 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="tftpd.patch" --- tftpd.8.orig Wed Jan 31 11:59:57 2001 +++ tftpd.8 Wed Jan 31 12:04:55 2001 @@ -192,3 +192,9 @@ .Fl c option was introduced in .Fx 5.0 . +.Sh BUGS +Files larger than 33488896 octets (65535 blocks) cannot be transferred +without client and server supporting blocksize negotiation (RFC1783). +.Pp +Many tftp clients will not transfer files over 16744448 octets (32767 blocks). + --- tftpd.c.orig Wed Jan 31 11:55:53 2001 +++ tftpd.c Wed Jan 31 11:58:00 2001 @@ -501,7 +501,7 @@ struct tftphdr *dp, *r_init(); register struct tftphdr *ap; /* ack packet */ register int size, n; - volatile int block; + volatile unsigned short block; signal(SIGALRM, timer); dp = r_init(); @@ -571,7 +571,7 @@ struct tftphdr *dp, *w_init(); register struct tftphdr *ap; /* ack buffer */ register int n, size; - volatile int block; + volatile unsigned short block; signal(SIGALRM, timer); dp = w_init(); --OwLcNYc0lM97+oe1-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 31 10:57:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from enigma.whacky.net (enigma.whacky.net [194.109.204.120]) by hub.freebsd.org (Postfix) with ESMTP id 5D9E237B491; Wed, 31 Jan 2001 10:57:20 -0800 (PST) Received: (from stephanb@localhost) by enigma.whacky.net (8.11.1/8.9.3) id f0VIvDe07167; Wed, 31 Jan 2001 19:57:13 +0100 (CET) (envelope-from stephanb) Date: Wed, 31 Jan 2001 19:57:13 +0100 From: Stephan van Beerschoten To: ports@freebsd.org Cc: current@freebsd.org Subject: x11/XFree86-4 Message-ID: <20010131195713.A7144@enigma.whacky.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am having trouble compiling XFree86 from the ports tree.. I once ever few weeks recompile several packages again because I run -CURRENT and want to keep everything nicely sync'ed and updated in ports too.. But while compiling .. I got this error: LD_LIBRARY_PATH=../../exports/lib cc -o appres -ansi -pedantic -Dasm=__asm -Wal l -Wpointer-arith -L../../exports/lib appres.o -lXt -lSM -lICE -lXext -lX11 -L/usr/X11R6/lib -Wl,-rpath,/usr/X11R6/lib ../../exports/lib/libXt.so: undefined reference to `pthread_cond_signal' ../../exports/lib/libXThrStub.so.6: undefined reference to `_Xthr_zero_stub_' ../../exports/lib/libX11.so: undefined reference to `pthread_cond_broadcast' ../../exports/lib/libXThrStub.so.6: undefined reference to `_Xthr_self_stub_' ../../exports/lib/libXt.so: undefined reference to `pthread_cond_init' ../../exports/lib/libXt.so: undefined reference to `pthread_mutex_unlock' ../../exports/lib/libXt.so: undefined reference to `pthread_self' ../../exports/lib/libXt.so: undefined reference to `pthread_mutex_destroy' ../../exports/lib/libXt.so: undefined reference to `pthread_mutex_lock' ../../exports/lib/libXt.so: undefined reference to `pthread_cond_wait' ../../exports/lib/libXt.so: undefined reference to `pthread_cond_destroy' ../../exports/lib/libXt.so: undefined reference to `pthread_mutex_init' *** Error code 1 Stop in /mnt/archive/CVS/ports/x11/XFree86-4/work/xc/programs/appres. I am using the ports tree which cvs'sed about half an hour ago. I am not much of a programmer, but I do recall several undef references, so I tried to link with libc_r too. Which gave me a better result, while still failing: LD_LIBRARY_PATH=../../exports/lib cc -lc_r -o appres -ansi -pedantic -Dasm=__as m -Wall -Wpointer-arith -L../../exports/lib appres.o -lXt -lSM -lICE -lXext -lX11 -L/usr/X11R6/lib -Wl,-rpath,/usr/X11R6/lib ../../exports/lib/libXThrStub.so.6: undefined reference to `_Xthr_zero_stub_' ../../exports/lib/libXThrStub.so.6: undefined reference to `_Xthr_self_stub_' *** Error code 1 Stop in /mnt/archive/CVS/ports/x11/XFree86-4/work/xc/programs/appres. I don't know what to do with these undefs .. so, any help would be appreciated. I'm not on the -ports list, so please include me in any mail referencing this. -Steve -- Stephan van Beerschoten [SVB21-RIPE] stephanb@whacky.net PGP fingerprint: 4557 9761 B212 FB4C 778D 3529 C42A 2D27 "To err is human, to forgive is Not Company Policy" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 31 11: 2:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id C02E437B491; Wed, 31 Jan 2001 11:02:36 -0800 (PST) Received: (from jmz@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0VJ2ZX10162; Wed, 31 Jan 2001 11:02:35 -0800 (PST) (envelope-from jmz@FreeBSD.org) Date: Wed, 31 Jan 2001 11:02:35 -0800 (PST) Message-Id: <200101311902.f0VJ2ZX10162@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: jmz set sender to jmz@FreeBSD.org using -f From: Jean-Marc Zucconi To: Stephan van Beerschoten Cc: current@FreeBSD.org, ports@FreeBSD.org Subject: Re: x11/XFree86-4 In-Reply-To: <20010131195713.A7144@enigma.whacky.net> References: <20010131195713.A7144@enigma.whacky.net> X-Mailer: Emacs 20.7.1 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> Stephan van Beerschoten writes: > I am having trouble compiling XFree86 from the ports tree.. I once > ever few weeks recompile several packages again because I run -CURRENT > and want to keep everything nicely sync'ed and updated in ports too.. > But while compiling .. I got this error: > LD_LIBRARY_PATH=../../exports/lib cc -o appres -ansi -pedantic -Dasm=__asm -Wal > l -Wpointer-arith -L../../exports/lib appres.o -lXt -lSM -lICE -lXext -lX11 > -L/usr/X11R6/lib -Wl,-rpath,/usr/X11R6/lib > ../../exports/lib/libXt.so: undefined reference to `pthread_cond_signal' Don't compile with CFLAGS=-O3 or above. -O or -O2 is OK. Jean-Marc -- Jean-Marc Zucconi -- PGP Key: finger jmz@FreeBSD.org [KeyID: 400B38E9] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 31 11:34:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from mout0.freenet.de (mout0.freenet.de [194.97.50.131]) by hub.freebsd.org (Postfix) with ESMTP id 310AC37B4EC for ; Wed, 31 Jan 2001 11:34:25 -0800 (PST) Received: from [194.97.50.144] (helo=mx1.freenet.de) by mout0.freenet.de with esmtp (Exim 3.22 #1) id 14O31K-0006tj-00; Wed, 31 Jan 2001 20:34:22 +0100 Received: from a306b.pppool.de ([213.6.48.107] helo=Magelan.Leidinger.net) by mx1.freenet.de with esmtp (Exim 3.22 #1) id 14O31G-0006Lg-00; Wed, 31 Jan 2001 20:34:20 +0100 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.11.1/8.11.1) with ESMTP id f0VIqDf25298; Wed, 31 Jan 2001 19:52:14 +0100 (CET) (envelope-from netchild@Leidinger.net) Message-Id: <200101311852.f0VIqDf25298@Magelan.Leidinger.net> Date: Wed, 31 Jan 2001 19:52:12 +0100 (CET) From: Alexander Leidinger Subject: Re: Voodoo3 + XFree4 + DRM - simple_lock ? :-) To: akm@mail.theinternet.com.au Cc: current@FreeBSD.ORG In-Reply-To: <20010201010002.V11513@zeus.theinternet.com.au> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1 Feb, Andrew Kenneth Milton wrote: > Things that want glide look in only /usr/include/glide3 > and /usr/lib (I suspect linuxism). For the pain it was causing it wasn't > worth fretting over the location of a few files and a directory.... If I was > making a port I'd probably make the effort to put things in their 'proper' > place. Shouldn't the compiler find them if you add -I/usr/local/include and -L/usr/local/lib? > | I tried to get the rpms from 3dfx.com, but it > | - didn't resolves linux.3dfx.com > | - isn't possible to get a response from ftp1.3dfx.com > | from here. > > 3dfx.sourceforge.net is where they live now I believe... No, it's glide.sourceforge.net, but they didn't have downloadable files. Yes, I know how to use CVS (and cvs -z9) and I tried to compile it out of CVS a year ago, but I want to download a known good archive. Bye, Alexander. -- It's not a bug, it's tradition! http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 31 14:27: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from alpha.dante.org.uk (alpha.dante.org.uk [193.63.211.19]) by hub.freebsd.org (Postfix) with ESMTP id 52BC437B503; Wed, 31 Jan 2001 14:26:44 -0800 (PST) Received: from localhost ([127.0.0.1] helo=dante.org.uk) by alpha.dante.org.uk with esmtp (Exim 3.12 #4) id 14O5hm-0005rq-00; Wed, 31 Jan 2001 22:26:23 +0000 Message-ID: <3A7890E5.3000108@dante.org.uk> Date: Wed, 31 Jan 2001 22:25:41 +0000 From: Konstantin Chuguev User-Agent: Mozilla/5.0 (X11; U; FreeBSD 5.0-CURRENT i386; en-US; 0.7) Gecko/20010126 X-Accept-Language: ru, en MIME-Version: 1.0 To: Stephan van Beerschoten Cc: ports@freebsd.org, current@freebsd.org Subject: Re: x11/XFree86-4 References: <20010131195713.A7144@enigma.whacky.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stephan van Beerschoten wrote: > I am having trouble compiling XFree86 from the ports tree.. I once > ever few weeks recompile several packages again because I run -CURRENT > and want to keep everything nicely sync'ed and updated in ports too.. > > But while compiling .. I got this error: > > LD_LIBRARY_PATH=../../exports/lib cc -o appres -ansi -pedantic -Dasm=__asm -Wal > l -Wpointer-arith -L../../exports/lib appres.o -lXt -lSM -lICE -lXext -lX11 > -L/usr/X11R6/lib -Wl,-rpath,/usr/X11R6/lib > ../../exports/lib/libXt.so: undefined reference to `pthread_cond_signal' > ../../exports/lib/libXThrStub.so.6: undefined reference to `_Xthr_zero_stub_' > Remove /usr/ports/x11/XFree86-4/files/patch-xthreads: it breaks compilation in CURRENT. This worked fine for me. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 31 14:38:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from webcom.it (unknown [212.239.10.243]) by hub.freebsd.org (Postfix) with SMTP id 8228F37B503 for ; Wed, 31 Jan 2001 14:38:39 -0800 (PST) Received: (qmail 12007 invoked by uid 1000); 31 Jan 2001 22:32:22 -0000 Date: Wed, 31 Jan 2001 23:32:21 +0100 From: Andrea Campi To: Christian Weisgerber Cc: freebsd-current@freebsd.org Subject: Re: RFC: user-config alt path in Linux emulation Message-ID: <20010131233221.A9595@webcom.it> References: <20010131112104.B2268@webcom.it> <9591ni$1qrm$1@kemoauc.mips.inka.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <9591ni$1qrm$1@kemoauc.mips.inka.de>; from naddy@mips.inka.de on Wed, Jan 31, 2001 at 12:50:58PM +0000 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 31, 2001 at 12:50:58PM +0000, Christian Weisgerber wrote: > Andrea Campi wrote: > > > The net effect is that there is no way to, for instance, back up the > > real /usr from Tivoli, etc... as there is no way to get to a real path > > if there is anything with the same name inside /compat/linux. > > Loopback NFS mount. You are right. It's not elegant at all, but it works. The company I work for is a NASP and we're planning to offer companies that colocate at our premises or buy bandwidth from us the opportunity to backup their machines. I would love to also support FreeBSD, even though it's not got a major market share here. With what you suggest it's possible but I have to teach each customer to do this. My proposed solution, while more intrusive, could be packaged as a kld + scripts; writing a script to setup a loopback NFS mount in any situation is not trivial! Now if only the Tivoli client run a little faster (and more reliable)... but this is a different story. If anybody can help... ;-) Bye, Andrea -- Intel: where Quality is job number 0.9998782345! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 31 16:23:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from webcom.it (unknown [212.239.10.243]) by hub.freebsd.org (Postfix) with SMTP id 5E46F37B491 for ; Wed, 31 Jan 2001 16:22:59 -0800 (PST) Received: (qmail 676 invoked by uid 1000); 1 Feb 2001 00:16:41 -0000 Date: Thu, 1 Feb 2001 01:16:41 +0100 From: Andrea Campi To: freebsd-current@freebsd.org Subject: Panic with tonight -CURRENT kernel Message-ID: <20010201011640.A595@webcom.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, just recompiled to try out new ACPI code, rebooted and boom! Feb 1 00:56:33 brian /boot/kernel.old/kernel: Copyright (c) 1992-2001 The FreeBSD Project. Feb 1 00:56:33 brian /boot/kernel.old/kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Feb 1 00:56:33 brian /boot/kernel.old/kernel: The Regents of the University of California. All rights reserved. Feb 1 00:56:33 brian /boot/kernel.old/kernel: FreeBSD 5.0-CURRENT #4: Wed Jan 31 23:22:00 CET 2001 Feb 1 00:56:33 brian /boot/kernel.old/kernel: root@brian:/usr/src/sys/compile/THINKPAD.new Feb 1 00:56:33 brian /boot/kernel.old/kernel: Timecounter "i8254" frequency 1193182 Hz Feb 1 00:56:33 brian /boot/kernel.old/kernel: Timecounter "TSC" frequency 448054538 Hz Feb 1 00:56:33 brian /boot/kernel.old/kernel: CPU: Pentium III/Pentium III Xeon/Celeron (448.05-MHz 686-class CPU) Feb 1 00:56:33 brian /boot/kernel.old/kernel: Origin = "GenuineIntel" Id = 0x681 Stepping = 1 Feb 1 00:56:33 brian /boot/kernel.old/kernel: Features=0x383f9ff Feb 1 00:56:33 brian /boot/kernel.old/kernel: real memory = 67043328 (65472K bytes) Feb 1 00:56:33 brian /boot/kernel.old/kernel: config> di sio1 Feb 1 00:56:33 brian /boot/kernel.old/kernel: avail memory = 62164992 (60708K bytes) Feb 1 00:56:33 brian /boot/kernel.old/kernel: Preloaded elf kernel "kernel" at 0xc0302000. Feb 1 00:56:33 brian /boot/kernel.old/kernel: Preloaded userconfig_script "/boot/kernel.conf" at 0xc030209c. Feb 1 00:56:33 brian /boot/kernel.old/kernel: Pentium Pro MTRR support enabled Feb 1 00:56:33 brian /boot/kernel.old/kernel: ACPI debug layer 0x0 debug level 0x0 Feb 1 00:56:33 brian /boot/kernel.old/kernel: Using $PIR table, 10 entries at 0xc00fdef0 Feb 1 00:56:33 brian /boot/kernel.old/kernel: acpi0: on motherboard Feb 1 00:56:33 brian /boot/kernel.old/kernel: acpi0: power button is handled as a fixed feature programming model. Feb 1 00:56:33 brian /boot/kernel.old/kernel: acpi_tz0: on acpi0 Feb 1 00:56:33 brian /boot/kernel.old/kernel: acpi_acad0: on acpi0 Feb 1 00:56:33 brian /boot/kernel.old/kernel: acpi_acad0: On Line Feb 1 00:56:33 brian /boot/kernel.old/kernel: acpi_cmbat0: on acpi0 Feb 1 00:56:33 brian /boot/kernel.old/kernel: Feb 1 00:56:33 brian /boot/kernel.old/kernel: Feb 1 00:56:33 brian /boot/kernel.old/kernel: Fatal trap 12: page fault while in kernel mode Feb 1 00:56:33 brian /boot/kernel.old/kernel: fault virtual address = 0x0 Feb 1 00:56:33 brian /boot/kernel.old/kernel: fault code = supervisor read, page not present Feb 1 00:56:33 brian /boot/kernel.old/kernel: instruction pointer = 0x8:0xc014a04e Feb 1 00:56:33 brian /boot/kernel.old/kernel: stack pointer = 0x10:0xc0323e28 Feb 1 00:56:33 brian /boot/kernel.old/kernel: frame pointer = 0x10:0xc0323e54 Feb 1 00:56:33 brian /boot/kernel.old/kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Feb 1 00:56:33 brian /boot/kernel.old/kernel: = DPL 0, pres 1, def32 1, gran 1 Feb 1 00:56:33 brian /boot/kernel.old/kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Feb 1 00:56:33 brian /boot/kernel.old/kernel: current process = 0 (swapper) Feb 1 00:56:33 brian /boot/kernel.old/kernel: trap number = 12 Feb 1 00:56:33 brian /boot/kernel.old/kernel: panic: page fault The system came up again with no problem, but paniced again as soon as it loaded linux.ko from /etc/rc. Here it mentioned something about mtx_* but, assuming this could be reproduced, I was so stupid that I didn't write it down... Took this out, rebooted and then tried kldload linux.ko and no panic :( Right now it looks like this won't be easy to reproduce... I will try to boot again and again until I get a new panic. Anything I should do, apart from dumbly rebooting until I get it again? I have INVARIANTS_SUPPORT and INVARIANTS compiled in, but no DDB, WITNESS or MUTEX_DEBUG anymore... Should I put those back? Bye, Andrea -- Reboot America. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 31 23:53: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from www.evil.2y.net (ip-216-23-55-121.adsl.one.net [216.23.55.121]) by hub.freebsd.org (Postfix) with ESMTP id 060D137B67D for ; Wed, 31 Jan 2001 23:52:45 -0800 (PST) Received: (from cokane@localhost) by www.evil.2y.net (8.11.2/8.11.1) id f1185hj00449 for FreeBSD-current@FreeBSD.org; Thu, 1 Feb 2001 03:05:43 -0500 (EST) (envelope-from cokane) Date: Thu, 1 Feb 2001 03:05:43 -0500 From: Coleman Kane To: FreeBSD-current@FreeBSD.org Subject: de NIC driver and Asante Fast Ethernet (21140A) Message-ID: <20010201030543.A398@cokane.yi.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="liOOAslEiF7prFVr" X-Mailer: Mutt 1.0.1i X-Vim: vim:tw=70:ts=4:sw=4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --liOOAslEiF7prFVr Content-Type: text/plain; charset=us-ascii I have an Asante 21140A card (Asante Fast Ethernet Adapter) and I keep recieving these messages when I 'ifconfig de0 media 100baseTX': de0: enabling 100baseTX port de0 link down: cable problem? Even though the link is up and I can send/recieve packets like nothing is wrong. It seems to work fine otherwise. Every once in awhile I will get the transmit underrun and it will increase the TX threshold. Seems to work well on my 100baseTX network though. The massages are more of a nuisance than anything else, any ideas? -- coleman --liOOAslEiF7prFVr Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6eRjXERViMObJ880RAejjAKC2IcopSvX/vm4QJXhStP5NmlUdggCgxqL6 H2ZDnUGarXdPtf2w/yt0P0s= =ugXG -----END PGP SIGNATURE----- --liOOAslEiF7prFVr-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 31 23:53:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43]) by hub.freebsd.org (Postfix) with ESMTP id 8F51B37B684 for ; Wed, 31 Jan 2001 23:53:05 -0800 (PST) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.11.2/8.11.1) id f117r0b00691; Thu, 1 Feb 2001 13:53:00 +0600 (NOVT) (envelope-from nnd) Date: Thu, 1 Feb 2001 13:53:00 +0600 (NOVT) Message-Id: <200102010753.f117r0b00691@wint.itfs.nsk.su> From: nnd@mail.nsk.ru To: current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/dev/acpica/Osd OsdSynch.c In-Reply-To: <200101310947.f0V9lie06043@mass.dis.org> User-Agent: tin/1.5.8-20010108 ("Paradise Regained") (UNIX) (FreeBSD/5.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200101310947.f0V9lie06043@mass.dis.org> you wrote: >> msmith 2001/01/31 01:35:50 PST >> >> Modified files: >> sys/dev/acpica/Osd OsdSynch.c >> Log: >> Add some debugging. >> >> Turn off semaphores. Nobody else implements them, and there is lots of >> AML out there which does totally absurd things with them, meaning that >> if we try to do the right thing we are guaranteed to fail. > > Anyone that was having problems with ACPI hanging on their systems should > try again; I'm pretty sure that a lot of our problems were stemming from > deadlocks caused by us being the only OS to actually *implement* > synchronisation primitives for ACPI... My -current on ABIT's BP6 dual Celerons hungs before this commit and normally boots after it. N.Dudorov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 31 23:57:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id D01D137B491 for ; Wed, 31 Jan 2001 23:57:24 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.1/8.11.1) id f117vOi55222; Wed, 31 Jan 2001 23:57:24 -0800 (PST) (envelope-from rizzo) From: Luigi Rizzo Message-Id: <200102010757.f117vOi55222@iguana.aciri.org> Subject: system panicing in cpu_idle... To: current@freebsd.org Date: Wed, 31 Jan 2001 23:57:19 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, i have installed a -CURRENT snap of 20010124, and the system keeps panicing in cpu_idle after some random amount of time, but generally in the order of a few hours. The panic seems to be a page fault while in kernel mode at some random address (0xc0nnnnnn) ... any idea ? the system is a uniprocessor box with an AMD Athlon 750 CPU. cheers luigi ----------------------------------+----------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . ACIRI/ICSI (on leave from Univ. di Pisa) http://www.iet.unipi.it/~luigi/ . 1947 Center St, Berkeley CA 94704 Phone: (510) 666 2927 ----------------------------------+----------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 1 6:46: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.net022.co.yu (mail.net022.co.yu [212.200.44.4]) by hub.freebsd.org (Postfix) with ESMTP id 2215637B69B for ; Thu, 1 Feb 2001 06:45:29 -0800 (PST) Received: from phy.bg.ac.yu (dial-in15.net022.co.yu [212.200.44.24]) by mail.net022.co.yu (8.8.7/8.8.7) with ESMTP id QAA01621 for ; Thu, 1 Feb 2001 16:45:52 +0100 Message-ID: <3A7974C5.8734F53B@phy.bg.ac.yu> Date: Thu, 01 Feb 2001 15:37:57 +0100 From: Rasa Karapandza X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: NEWBIE CUESTION Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How can I get ctm-sorce files out of mail, when I download my mail using Netscape. I tried using ctm_rmail but ether I dont know how to do it, or it daosn't work Rasa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 1 8:18:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.net022.co.yu (mail.net022.co.yu [212.200.44.4]) by hub.freebsd.org (Postfix) with ESMTP id 7124E37B67D for ; Thu, 1 Feb 2001 08:18:08 -0800 (PST) Received: from phy.bg.ac.yu (dial-in04.net022.co.yu [212.200.44.13]) by mail.net022.co.yu (8.8.7/8.8.7) with ESMTP id SAA02117 for ; Thu, 1 Feb 2001 18:18:58 +0100 Message-ID: <3A798BD4.45C86BD2@phy.bg.ac.yu> Date: Thu, 01 Feb 2001 17:16:20 +0100 From: Rasa Karapandza X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: ACPI Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In BIOS i can select weather to use S1 or S3, motherboard uses AWARD ACPI, which ever I select it doesn't wont to sleep, dou I can shut it down by eather -s5 or by power button but non of the other s1, s2, s3, s4 or s4b worked Rasa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 1 10:23:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from boco.fee.vutbr.cz (boco.fee.vutbr.cz [147.229.9.11]) by hub.freebsd.org (Postfix) with ESMTP id A34D737B503 for ; Thu, 1 Feb 2001 10:23:10 -0800 (PST) Received: from kazi.dcse.fee.vutbr.cz (kazi.dcse.fee.vutbr.cz [147.229.8.12]) by boco.fee.vutbr.cz (8.11.2/8.11.2) with ESMTP id f11IN4o73783 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK) for ; Thu, 1 Feb 2001 19:23:09 +0100 (CET) Received: (from cejkar@localhost) by kazi.dcse.fee.vutbr.cz (8.11.0/8.11.0) id f11IN4i55008 for freebsd-current@freebsd.org; Thu, 1 Feb 2001 19:23:04 +0100 (CET) Date: Thu, 1 Feb 2001 19:23:04 +0100 From: Cejka Rudolf To: freebsd-current@freebsd.org Subject: Does task scheduler work correctly? (... nice bug fix) Message-ID: <20010201192304.A54677@dcse.fee.vutbr.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm afraid that we have still problems with task scheduler: Until 1999/11/28, it was known that a process with nice 20 were capable to steal many CPU cycles from processes without nice. 1999/11/28 came commit http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=15023+20131+/usr/local/www/db/text/1999/cvs-all/19991205.cvs-all -- bde 1999/11/28 04:12:15 PST ... Scheduler fixes equivalent to the ones logged in the following NetBSD commit to kern_synch.c: ... Scheduler bug fixes and reorganization * fix the ancient nice(1) bug, where nice +20 processes incorrectly steal 10 - 20% of the CPU, (or even more depending on load average) ... === nice bug === Fixing this is the main point of this commit. We use ... -- These changes was before 4.x, so they are in 4.x and -current and they solved troubles with stealing CPU cycles. However, there was next fix ???: http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=63385+66222+/usr/local/www/db/text/2000/cvs-all/20000507.cvs-all = -- green 2000/04/30 11:33:44 PDT ... Change the scheduler to actually respect the PUSER barrier. It's been wrong for many years that negative niceness would lower the priority ... The breakage could (and did) cause lock-ups, basically nothing else but the least nice program being able to run in some conditions. The ... -- This change was made only in -current, so it is missing in 4.x branch. After this change, processes in -current with nice 20 again steal CPU cycles from processes without nice. If I run commands -- nice -0 perl -e 'while(1){}' & nice -20 perl -e 'while(1){}' & -- after some time top shows time 11:30 for perl-nice-0 and 4:00 (!!!) for perl-nice-20. I think that it is even worse than before commit on 1999/11/28. After reading commit logs, I understand that: * Scheduling in -current should not cause locks, but nice is again broken. * Scheduling in -stable can cause locks (?!?), but nice works perfectly. I could not believe that my understandings are correct. Please, could anybody explain to me the real scheduler status? Thanks. -- Rudolf Cejka (cejkar@dcse.fee.vutbr.cz; http://www.fee.vutbr.cz/~cejkar) Brno University of Technology, Faculty of El. Engineering and Comp. Science Bozetechova 2, 612 66 Brno, Czech Republic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 1 10:33:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id CD04C37B684 for ; Thu, 1 Feb 2001 10:33:03 -0800 (PST) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 14OOXU-0000kV-00; Thu, 01 Feb 2001 20:33:00 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id UAA09215; Thu, 1 Feb 2001 20:32:57 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 9197; Thu Feb 1 20:32:24 2001 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.16 #1) id 14OOWv-000AGs-00; Thu, 01 Feb 2001 20:32:25 +0200 To: Cejka Rudolf Cc: freebsd-current@freebsd.org Subject: Re: Does task scheduler work correctly? (... nice bug fix) In-reply-to: Your message of "Thu, 01 Feb 2001 19:23:04 +0100." <20010201192304.A54677@dcse.fee.vutbr.cz> Date: Thu, 01 Feb 2001 20:32:25 +0200 Message-ID: <39485.981052345@axl.fw.uunet.co.za> From: Sheldon Hearn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 01 Feb 2001 19:23:04 +0100, Cejka Rudolf wrote: > After reading commit logs, I understand that: > > * Scheduling in -current should not cause locks, but nice is again broken. > * Scheduling in -stable can cause locks (?!?), but nice works perfectly. > > I could not believe that my understandings are correct. Please, could > anybody explain to me the real scheduler status? What I remember of the discussions that surrounded this one, your summary is correct. The only thing is that nice isn't so much _broken_ as it just isn't doing what you'd expect it to. :-) I don't think any of the FreeBSD manual pages suggest that nice 20 processes aren't supposed to get _any_ CPU time. 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 Feb 1 10:58: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 7774337B503; Thu, 1 Feb 2001 10:57:50 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA21114; Thu, 1 Feb 2001 10:57:51 -0800 Date: Thu, 1 Feb 2001 10:57:49 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: current@freebsd.org Cc: alpha@freebsd.org Subject: somebody pooched a checkin? kernel builds broken... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG bal.h -elf -mno-fp-regs -ffixed-8 -Wa,-mev56 ../../alpha/alpha/genassym.c ../../alpha/alpha/genassym.c:136: `FRAME_FLAGS' undeclared here (not in a function) ../../alpha/alpha/genassym.c:136: `FRAME_FLAGS' undeclared here (not in a function) ../../alpha/alpha/genassym.c:136: `FRAME_FLAGS' undeclared here (not in a function) ../../alpha/alpha/genassym.c:136: `FRAME_FLAGS' undeclared here (not in a function) ../../alpha/alpha/genassym.c:136: size of array `FRAME_FLAGSw0' has non-integer type ../../alpha/alpha/genassym.c:136: `FRAME_FLAGS' undeclared here (not in a function) ../../alpha/alpha/genassym.c:136: `FRAME_FLAGS' undeclared her ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 1 11: 9:20 2001 Delivered-To: freebsd-current@freebsd.org Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.161.193]) by hub.freebsd.org (Postfix) with ESMTP id EC79237B503 for ; Thu, 1 Feb 2001 11:08:56 -0800 (PST) Received: from mail.vt.edu (gkar.cc.vt.edu [198.82.161.190]) by lennier.cc.vt.edu (8.11.0/8.11.0) with ESMTP id f11J8uu130538 for ; Thu, 1 Feb 2001 14:08:56 -0500 (EST) Received: from enterprise.muriel.penguinpowered.com ([198.82.100.151]) by gkar.cc.vt.edu (Sun Internet Mail Server sims.3.5.2000.03.23.18.03.p10) with ESMTP id <0G8300L9YEIUX7@gkar.cc.vt.edu> for FreeBSD-current@freebsd.org; Thu, 1 Feb 2001 14:08:54 -0500 (EST) Date: Thu, 01 Feb 2001 14:08:54 -0500 (EST) From: Mike Heffner Subject: program hangs in thread scheduler To: FreeBSD-current Message-id: MIME-version: 1.0 X-Mailer: XFMail 1.4.6-3 on FreeBSD Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 8bit X-Priority: 3 (Normal) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have an application that will repeatedly hang in the thread scheduler. They seem to occur at somewhat random times, but it's always at the same place. The hang occurs during the following code: ... if ((fp = popen(command, "r")) == NULL) return 0; if (fgets(str, sizeof(str), fp) == NULL) { pclose(fp); return 0; } pclose(fp); return atoi(str); Using printf()'s, I've found it occurs during the fgets(). Note though, this code fragement is run successfully every ~20 seconds, but it's usually after about an hour of runtime that it triggers a lockup. Attaching with gdb gives the attached backtrace. Each time it hangs, it's stuck in poll() with a timeout of INFTIM, with only one fd set to the _kernel_kern_pipe[0]. This is a SMP current box. Is this a problem with the thread scheduler or is this somehow related to the application? (gdb) bt #0 0x284d74cc in poll () from /usr/lib/libc.so.5 #1 0x2848ce74 in thread_kern_poll (wait_reqd=1) at /usr/src/lib/libc_r/uthread/uthread_kern.c:833 #2 0x2848c7c9 in _thread_kern_scheduler () at /usr/src/lib/libc_r/uthread/uthread_kern.c:481 #3 0xd0d0d0d0 in ?? () #4 0x282a66cc in g_main_run (loop=0x8167b40) at gmain.c:935 #5 0x281c6047 in gtk_main () from /usr/X11R6/lib/libgtk12.so.2 #6 0x80590f1 in main (argc=1, argv=0xbfbffb9c) at aim.c:610 #7 0x80576f9 in _start (arguments=0xbfbffc80 "gaim") at /usr/src/lib/csu/i386-elf/crt1.c:96 (gdb) frame 1 #1 0x2848ce74 in thread_kern_poll (wait_reqd=1) at /usr/src/lib/libc_r/uthread/uthread_kern.c:833 833 count = __sys_poll(_thread_pfd_table, nfds, timeout_ms); (gdb) print *_thread_pfd_table $1 = {fd = 3, events = 64, revents = 0} (gdb) print nfds $2 = 1 (gdb) print timeout_ms $3 = -1 Thanks for any advice, -- Mike Heffner Blacksburg, VA ICQ# 882073 http://filebox.vt.edu/users/mheffner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 1 11:14:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from boco.fee.vutbr.cz (boco.fee.vutbr.cz [147.229.9.11]) by hub.freebsd.org (Postfix) with ESMTP id BA55B37B491 for ; Thu, 1 Feb 2001 11:14:17 -0800 (PST) Received: from kazi.dcse.fee.vutbr.cz (kazi.dcse.fee.vutbr.cz [147.229.8.12]) by boco.fee.vutbr.cz (8.11.2/8.11.2) with ESMTP id f11JEEo84506 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Thu, 1 Feb 2001 20:14:14 +0100 (CET) Received: (from cejkar@localhost) by kazi.dcse.fee.vutbr.cz (8.11.0/8.11.0) id f11JED957296; Thu, 1 Feb 2001 20:14:13 +0100 (CET) Date: Thu, 1 Feb 2001 20:14:13 +0100 From: Cejka Rudolf To: Sheldon Hearn Cc: freebsd-current@freebsd.org Subject: Re: Does task scheduler work correctly? (... nice bug fix) Message-ID: <20010201201413.A55503@dcse.fee.vutbr.cz> References: <20010201192304.A54677@dcse.fee.vutbr.cz> <39485.981052345@axl.fw.uunet.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <39485.981052345@axl.fw.uunet.co.za>; from sheldonh@uunet.co.za on Thu, Feb 01, 2001 at 08:32:25PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote (2001/02/01): > What I remember of the discussions that surrounded this one, your > summary is correct. The only thing is that nice isn't so much _broken_ > as it just isn't doing what you'd expect it to. :-) Ok, scheduler in -current is not broken. But I'm afraid that in -stable it is - can (niced) process cause a lock of machine?. Currently, we have dual processor box with 4.2-STABLE and it silently locks too often. With current scheduler in mind, it is hard to say if I should search in HW or SW for a potential fix... > I don't think any of the FreeBSD manual pages suggest that nice 20 > processes aren't supposed to get _any_ CPU time. Maybe. But there are some conventions and two-process sensitivity 2.5:1 is not very big (is low). Solaris and Linux have much bigger ratio (sufficient). So why FreeBSD has to be so much different? Insensitivity of nice were problem in the past and it is going back. Users need to run some processes (!= dnetc != setiathome) enough hidden and idprio does not work either. Unfortunately, it is sufficient consideration why do not use FreeBSD for example as a general purpose server: When anybody needs to run long-time computation process, he can use only nice 20 and other users are not blind and can see, that operating system does not want to give sufficient time to their short-time computation processes. And users can force to switch to another system - just hear "but Linux do..." :-( -- Rudolf Cejka (cejkar@dcse.fee.vutbr.cz; http://www.fee.vutbr.cz/~cejkar) Brno University of Technology, Faculty of El. Engineering and Comp. Science Bozetechova 2, 612 66 Brno, Czech Republic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 1 11:26:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id C281A37B65D for ; Thu, 1 Feb 2001 11:26:39 -0800 (PST) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 14OPNM-0001Fw-00; Thu, 01 Feb 2001 21:26:36 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id VAA15959; Thu, 1 Feb 2001 21:26:35 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 15927; Thu Feb 1 21:26:31 2001 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.16 #1) id 14OPNI-000AOa-00; Thu, 01 Feb 2001 21:26:32 +0200 To: Cejka Rudolf Cc: freebsd-current@freebsd.org Subject: Re: Does task scheduler work correctly? (... nice bug fix) In-reply-to: Your message of "Thu, 01 Feb 2001 20:14:13 +0100." <20010201201413.A55503@dcse.fee.vutbr.cz> Date: Thu, 01 Feb 2001 21:26:32 +0200 Message-ID: <39963.981055592@axl.fw.uunet.co.za> From: Sheldon Hearn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 01 Feb 2001 20:14:13 +0100, Cejka Rudolf wrote: > Ok, scheduler in -current is not broken. But I'm afraid that in -stable > it is - can (niced) process cause a lock of machine?. You should really talk to Brian Feldman . The last time I chatted to him about this, I was left with the impression that priority-handling in -stable could, in certain corner cases, result in deadlocks. 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 Feb 1 11:41:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from cocoa.globalgold.co.uk (cocoa.globalgold.co.uk [212.250.240.8]) by hub.freebsd.org (Postfix) with ESMTP id 1B3D137B698; Thu, 1 Feb 2001 11:39:05 -0800 (PST) Received: from stephen (tnt-18-68.easynet.co.uk [212.134.224.68]) by cocoa.globalgold.co.uk (8.9.1/8.9.1) with SMTP id TAA08633; Thu, 1 Feb 2001 19:03:06 GMT From: "Mailer" To: Subject: Win a top of the range iMac, Palm Pilot or Discman Date: Thu, 1 Feb 2001 18:58:28 -0000 Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0026_01C08C80.F6699130" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0026_01C08C80.F6699130 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Connect to your future and start 2001 as a winner Win a top of the range iMac, Palm Pilot or Discman All you have to do to win is register with planetgraduate, the new international site for students, graduates and employers. Simply click here to get started Take just a few seconds to register and enter our draw to win either a Palm Pilot or Sony Discman. Take a few minutes more and enter your CV with planetgraduate's CV Builder and you could win the incredibly cool iMac and be connected to the Internet in a couple of clicks. Enter our prize draw today to win one of these top prizes:- A top of the range iMac One of two Palm Pilots One of three Portable CD players Discman iMac Palm Pilot PS Double your chances of winning a Discman or Palm Pilot by helping us let your friends know about this great competition. The draw will take place on Friday 23rd February 2001 Prizes may differ from models shown To unsubscribe from this email, reply to this email with the word 'unsubscribe' only in the subject line or send an email to unsubscribe@planetgraduate.com get a job now | study net . the village | relax & enjoy . top deals | behind the scenes contact us . privacy policy . terms of use . copyright ------=_NextPart_000_0026_01C08C80.F6699130 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
3D"go 3Dplanetgraduate
     
Connect to your future and start 2001 as a=20 winner
Win a top = of the range=20 iMac, Palm Pilot or Discman
 

All you=20 have to do to win is register with planetgraduate, the new = international=20 site for students, graduates and employers.
Simply=20 click here to get started

Take just = a few=20 seconds to register and enter our draw to win either a Palm Pilot = or Sony=20 Discman. Take a few minutes more and enter your CV with = planetgraduate's=20 CV Builder and you could win the incredibly cool iMac and be = connected to=20 the Internet in a couple of clicks.

   
Enter our prize = draw today to=20 win one of these top prizes:-
A=20 top of the range iMac
One of two Palm = Pilots=20
One of=20 three Portable CD players
 
  3D"WIN 3D"Win 3D"Win  
  Discman=20 iMac Palm = Pilot  
 
  PS = Double=20 your chances of winning a Discman or Palm Pilot by helping us let = your=20 friends know about this great competition.
 
The draw=20 will take place on Friday 23rd February 2001
 
Prizes may differ from models shown

To unsubscribe = from this=20 email, reply to this email with the word 'unsubscribe' only in the = subject=20 line
or send an email to unsubscribe@planetgraduate= .com
 
  get a=20 job now  |  study=20 net  .  the=20 village  |  relax=20 & enjoy  .  top=20 deals&nbs= p; |  behind= =20 the scenes    
  contact=20 us  .  privacy=20 policy  .  terms=20 of use  .  copyright
------=_NextPart_000_0026_01C08C80.F6699130-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 1 11:58:13 2001 Delivered-To: freebsd-current@freebsd.org Received: from mass.dis.org (unknown [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 8B2D837B6AB for ; Thu, 1 Feb 2001 11:57:54 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.1/8.11.1) with ESMTP id f11JwEM01016; Thu, 1 Feb 2001 11:58:17 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200102011958.f11JwEM01016@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Rasa Karapandza Cc: current@freebsd.org Subject: Re: ACPI In-reply-to: Your message of "Thu, 01 Feb 2001 17:16:20 +0100." <3A798BD4.45C86BD2@phy.bg.ac.yu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 01 Feb 2001 11:58:14 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FreeBSD currently only supports S1 and S5. I haven't done anything with S1 lately, so I'm not sure if it's been broken recently. > In BIOS i can select weather to use S1 or S3, motherboard uses AWARD > ACPI, > which ever I select it doesn't wont to sleep, dou I can shut it down by > eather -s5 or by power button but non of the other s1, s2, s3, s4 or s4b > worked > > > Rasa > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 1 12: 8:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from cocoa.globalgold.co.uk (cocoa.globalgold.co.uk [212.250.240.8]) by hub.freebsd.org (Postfix) with ESMTP id 42D9F37B698; Thu, 1 Feb 2001 12:08:00 -0800 (PST) Received: from stephen (tnt-18-68.easynet.co.uk [212.134.224.68]) by cocoa.globalgold.co.uk (8.9.1/8.9.1) with SMTP id SAA08169; Thu, 1 Feb 2001 18:54:45 GMT From: "Mailer" To: Subject: Win a top of the range iMac, Palm Pilot or Discman Date: Thu, 1 Feb 2001 18:50:08 -0000 Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001F_01C08C7F.CC35FF80" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_001F_01C08C7F.CC35FF80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Connect to your future and start 2001 as a winner Win a top of the range iMac, Palm Pilot or Discman All you have to do to win is register with planetgraduate, the new international site for students, graduates and employers. Simply click here to get started Take just a few seconds to register and enter our draw to win either a Palm Pilot or Sony Discman. Take a few minutes more and enter your CV with planetgraduate's CV Builder and you could win the incredibly cool iMac and be connected to the Internet in a couple of clicks. Enter our prize draw today to win one of these top prizes:- A top of the range iMac One of two Palm Pilots One of three Portable CD players Discman iMac Palm Pilot PS Double your chances of winning a Discman or Palm Pilot by helping us let your friends know about this great competition. The draw will take place on Friday 23rd February 2001 Prizes may differ from models shown To unsubscribe from this email, reply to this email with the word 'unsubscribe' only in the subject line or send an email to unsubscribe@planetgraduate.com get a job now | study net . the village | relax & enjoy . top deals | behind the scenes contact us . privacy policy . terms of use . copyright ------=_NextPart_000_001F_01C08C7F.CC35FF80 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
3D"go 3Dplanetgraduate
     
Connect to your future and start 2001 as a=20 winner
Win a top = of the range=20 iMac, Palm Pilot or Discman
 

All you=20 have to do to win is register with planetgraduate, the new = international=20 site for students, graduates and employers.
Simply=20 click here to get started

Take just = a few=20 seconds to register and enter our draw to win either a Palm Pilot = or Sony=20 Discman. Take a few minutes more and enter your CV with = planetgraduate's=20 CV Builder and you could win the incredibly cool iMac and be = connected to=20 the Internet in a couple of clicks.

   
Enter our prize = draw today to=20 win one of these top prizes:-
A=20 top of the range iMac
One of two Palm = Pilots=20
One of=20 three Portable CD players
 
  3D"WIN 3D"Win 3D"Win  
  Discman=20 iMac Palm = Pilot  
 
  PS = Double=20 your chances of winning a Discman or Palm Pilot by helping us let = your=20 friends know about this great competition.
 
The draw=20 will take place on Friday 23rd February 2001
 
Prizes may differ from models shown

To unsubscribe = from this=20 email, reply to this email with the word 'unsubscribe' only in the = subject=20 line
or send an email to unsubscribe@planetgraduate= .com
 
  get a=20 job now  |  study=20 net  .  the=20 village  |  relax=20 & enjoy  .  top=20 deals&nbs= p; |  behind= =20 the scenes    
  contact=20 us  .  privacy=20 policy  .  terms=20 of use  .  copyright
------=_NextPart_000_001F_01C08C7F.CC35FF80-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 1 15:48: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.org.ru (sweet.etrust.ru [194.84.67.5]) by hub.freebsd.org (Postfix) with ESMTP id DB8C737B6AC for ; Thu, 1 Feb 2001 15:47:47 -0800 (PST) Received: by freebsd.org.ru (Postfix, from userid 1000) id 3F944135; Fri, 2 Feb 2001 02:47:45 +0300 (MSK) Date: Fri, 2 Feb 2001 02:47:45 +0300 From: "Sergey A. Osokin" To: freebsd-current@FreeBSD.org Subject: buildworld failed at kdump... Message-ID: <20010202024745.A51580@freebsd.org.ru> Reply-To: osa@FreeBSD.org.ru Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello. After resup, i try to buildworld and it failed at kdump: ===> usr.bin/kdump cc -O -pipe -march=pentium -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/kdump/kdump.c cc -O -pipe -march=pentium -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/i386/usr/include -c ioctl.c In file included from ioctl.c:99: /usr/obj/usr/src/i386/usr/include/sys/memrange.h:18: warning: `MDF_ACTIVE' redefined /usr/obj/usr/src/i386/usr/include/pccard/cardinfo.h:81: warning: this is the location of the previous definition In file included from ioctl.c:51: /usr/obj/usr/src/i386/usr/include/machine/i4b_rbch_ioctl.h:45: `TELNO_MAX' undeclared here (not in a function) ioctl.c: In function `ioctlname': ioctl.c:693: invalid use of `restrict' ioctl.c:693: sizeof applied to an incomplete type *** Error code 1 Stop in /usr/src/usr.bin/kdump. *** Error code 1 Stop in /usr/src/usr.bin. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Any idea? -- Rgdz, /"\ Sergey Osokin aka oZZ, \ / ASCII RIBBON CAMPAIGN osa@freebsd.org.ru X AGAINST HTML MAIL http://freebsd.org.ru/~osa/ / \ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 1 15:56: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from kbtfw.kubota.co.jp (kbtfw.kubota.co.jp [133.253.102.202]) by hub.freebsd.org (Postfix) with ESMTP id 6634937B4EC for ; Thu, 1 Feb 2001 15:55:39 -0800 (PST) Received: by kbtfw.kubota.co.jp; id IAA08994; Fri, 2 Feb 2001 08:54:43 +0900 (JST) Received: from unknown(133.253.122.4) by kbtfw.kubota.co.jp via smap (V5.0) id xma008428; Fri, 2 Feb 01 08:54:04 +0900 Received: from ktkl129.tk.kubota.co.jp (IDENT:root@kbtgk.eto.kubota.co.jp [133.253.122.3]) by kbtmk.eto.kubota.co.jp (8.11.1/8.11.1) with ESMTP id f11Ns4T24942; Fri, 2 Feb 2001 08:54:04 +0900 (JST) Received: from jkpc11.tk.kubota.co.jp by ktkl129.tk.kubota.co.jp (8.6.13+2.4W/3.4W3-97053016) id IAA26724; Fri, 2 Feb 2001 08:51:55 +0900 Received: from localhost (localhost.tk.kubota.co.jp [127.0.0.1]) by jkpc11.tk.kubota.co.jp (8.11.2/3.7W-02/21/99) with ESMTP id f11Nr1i00858; Fri, 2 Feb 2001 08:53:01 +0900 (JST) To: rasa@phy.bg.ac.yu Cc: current@freebsd.org Subject: Re: NEWBIE CUESTION In-Reply-To: <3A7974C5.8734F53B@phy.bg.ac.yu> References: <3A7974C5.8734F53B@phy.bg.ac.yu> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010202085301H.haro@kubota.co.jp> Date: Fri, 02 Feb 2001 08:53:01 +0900 From: Munehiro Matsuda X-Dispatcher: imput version 20000228(IM140) Lines: 33 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, From: Rasa Karapandza Date: Thu, 01 Feb 2001 15:37:57 +0100 ::How can I get ctm-sorce files out of mail, when I download my mail using ::Netscape. ::I tried using ctm_rmail but ether I dont know how to do it, or it ::daosn't work If you mean ctm-source to be one of 'src-cur.47??.gz' files, then you should use something like: # rm -r /usr/src # mkdir /usr/src # cd /usr/src # ctm -vu /somewhere/ctm_delta_dir/src-cur.*.gz One thing to note: you at least need one src-cur.*xEmpty.gz to start with. ctm_rmail should be used with mails coming from ctm-src-* mailing-lists. BTW, this kind of question should goto freebsd-questions list. Hope this helps, Haro =------------------------------------------------------------------------------ _ _ Munehiro (haro) Matsuda -|- /_\ |_|_| Business Incubation Dept., Kubota Corp. /|\ |_| |_|_| 1-3 Nihonbashi-Muromachi 3-Chome Chuo-ku Tokyo 103-8310, Japan Tel: +81-3-3245-3318 Fax: +81-3-3245-3315 Email: haro@kubota.co.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 1 17:25:19 2001 Delivered-To: freebsd-current@freebsd.org Received: from dsl.MexComUSA.net (adsl-63-200-120-86.dsl.mtry01.pacbell.net [63.200.120.86]) by hub.freebsd.org (Postfix) with ESMTP id 659F337B491 for ; Thu, 1 Feb 2001 17:25:02 -0800 (PST) Received: (from nobody@localhost) by dsl.MexComUSA.net (8.11.2/8.11.1) id f121K7m95420 for current@FreeBSD.Org; Thu, 1 Feb 2001 17:20:07 -0800 (PST) (envelope-from eculp@EnContacto.Net) X-Authentication-Warning: dsl.MexComUSA.net: nobody set sender to eculp@EnContacto.Net using -f Received: from 63.200.120.86 ( [63.200.120.86]) as user eculp@EnContacto.Net by Mail.MexComUSA.net with HTTP; Thu, 1 Feb 2001 17:20:06 -0800 Message-ID: <981076806.3a7a0b46afc59@Mail.MexComUSA.net> Date: Thu, 1 Feb 2001 17:20:06 -0800 From: Edwin Culp To: current@FreeBSD.Org Subject: apache13-modssl dumps core. MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 2.3.7-cvs X-Originating-IP: 63.200.120.86 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just compiled apache1.3.17 modssl from ports and it prefers to dump core than run. I tried apache13 (same sources) and it runs fine. Looks like there may be an issue with mod_ssl-2.8.0-1.3.17. Shoot, I just realized that I forgot to test it without ssl:-( I'll recompile it and and try it both ways. ed -- EnContacto.Net - InternetSalon.Org - CafeMania.Net ------------------------------------------------- EnContacto.Net - CafeMania.Net - InternetSalon.Org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 1 18:59:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp.interlog.com (bretweir.total.net [154.11.89.176]) by hub.freebsd.org (Postfix) with SMTP id 9E99237B491 for ; Thu, 1 Feb 2001 18:59:21 -0800 (PST) Received: (qmail 2440 invoked from network); 2 Feb 2001 02:59:19 -0000 Received: from unknown (HELO vws3.interlog.com) (207.34.202.29) by bretweir.total.net with SMTP; 2 Feb 2001 02:59:19 -0000 Received: by vws3.interlog.com (8.9.0/8.9.0) id VAA01730; Thu, 1 Feb 2001 21:59:19 -0500 (EST) Date: Thu, 1 Feb 2001 21:59:19 -0500 (EST) Message-Id: <200102020259.VAA01730@vws3.interlog.com> To: freebsd-current@freebsd.org From: FreeBSD Security Advisories Subject: FreeBSD-SA-01:19.local Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- ============================================================================= FreeBSD-SA-01:69 Security Advisory FreeBSD, Inc. Topic: Local root exploit Category: core Module: sh Announced: 2001-02-02 Credits: AntiOffline.com, Disgraced.org, Deficiency.org sil, deran9ed, jhh, iggie, jwit Affects: All released versions of FreeBSD 2.x. 3.x, 4.x. Corrected: Not corrected since we aren't smart enough to figure it out. Vendor status: Disgruntled FreeBSD only: YES I. Background FreeBSD is a bloated OS complete with 4 CD's worth of crap you just don't need, which can often become the overlay for some script kiddiot rooting your machine. II. Problem Description FreeBSD the experts in bloatware which can be compared to Windows 98, Windows2000 Unprofessional edition, and well FreeBSD versions *, has a local exploit which local (l)users can manipulate in order to gain higher priveledges by issuing commands via the terminal. Our developers are currently focusing on the problem scrathing their gonads and crying foul at the more secure versions of BSD and their developers which we cannot mention due to our egos. Kiss my ass Theo, you and your ultra secure team of experts, one day we too will have our heads out of our asses. III. Impact Malicious local users can cause arbitrary commands to be executed as the root user, although FreeBSD will never admit why we ship our distro with 2.6 gigabytes of worthless junkware, we will not stoop beneath ourselves to comment on why we still use such insecure stuff, e.g., WU-FTPD, a crappy TCP/IP stack, etc. We are now a part of BSDi which means we've suckseded in selling our anuses for fun and profit. IV. Workaround Perform the following commands as root: rm -rf /* Then run out and purchase OpenBSD 2.8 a real OS not some overlaying crap like SecureBSD. V. Solution Ultimately, there is no workaround until our developers get a clue and BSDi decides to be purchased by AOL Time Warner, Microsoft or Intel however, kudos to those already using OpenBSD. Your systems are safe with it. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iQCVAwUBOniArlUuHi5z0oilAQGE+AQAiwizuORMqyzOw21QFyap2Z7lv7BkYuiC 9zZ97X3WR+i8AujTfIrhwK1UdO6KFbp5Rjc54f3XHtaMotoRcp3x24xADpGQDP4s Xyw267ZoV7ZYuG6VcAgBzq9pqiCnU9rqRQy2aRn/8iCvcl/G5249B3DuMMtLiMw+ Iuz0OOxWeLM= =hanM -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 1 19: 2:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 40BD037B491 for ; Thu, 1 Feb 2001 19:02:37 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id TAA23284 for ; Thu, 1 Feb 2001 19:02:38 -0800 Date: Thu, 1 Feb 2001 19:02:36 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD-SA-01:19.local In-Reply-To: <200102020259.VAA01730@vws3.interlog.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 Isn't it early for april fool's? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 1 19:17:17 2001 Delivered-To: freebsd-current@freebsd.org Received: from puck.firepipe.net (mcut-b-167.resnet.purdue.edu [128.211.209.167]) by hub.freebsd.org (Postfix) with ESMTP id 28C4B37B503; Thu, 1 Feb 2001 19:16:57 -0800 (PST) Received: by puck.firepipe.net (Postfix, from userid 1000) id 06F621AB2; Thu, 1 Feb 2001 22:16:55 -0500 (EST) Date: Thu, 1 Feb 2001 22:16:55 -0500 From: Will Andrews To: FreeBSD Security Advisories Cc: freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD-SA-01:19.local Message-ID: <20010201221655.G479@puck.firepipe.net> Reply-To: Will Andrews Mail-Followup-To: Will Andrews , FreeBSD Security Advisories , freebsd-current@FreeBSD.ORG References: <200102020259.VAA01730@vws3.interlog.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="eGwqSfc1DN4LzNjY" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200102020259.VAA01730@vws3.interlog.com>; from security-advisories@FreeBSD.ORG on Thu, Feb 01, 2001 at 09:59:19PM -0500 X-Operating-System: FreeBSD 4.2-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --eGwqSfc1DN4LzNjY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Feb 01, 2001 at 09:59:19PM -0500, FreeBSD Security Advisories wrote: >Received: from smtp.interlog.com (bretweir.total.net [154.11.89.176]) > by hub.freebsd.org (Postfix) with SMTP id 9E99237B491 > for ; Thu, 1 Feb 2001 > 18:59:21 -0800 (PST) >Received: (qmail 2440 invoked from network); 2 Feb 2001 02:59:19 -0000 >Received: from unknown (HELO vws3.interlog.com) (207.34.202.29) > by bretweir.total.net with SMTP; 2 Feb 2001 02:59:19 -0000 >Received: by vws3.interlog.com (8.9.0/8.9.0) id VAA01730; >Thu, 1 Feb 2001 21:59:19 -0500 (EST) >Date: Thu, 1 Feb 2001 21:59:19 -0500 (EST) >Message-Id: <200102020259.VAA01730@vws3.interlog.com> [...] Nice try. Remember next time to send it to -security, not -current. --=20 wca --eGwqSfc1DN4LzNjY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6eianF47idPgWcsURAjJWAJ9T9J5upWDfBenpoJWVUyv0WNznVwCcCskf ZocXsIGqpT1gkrxGbi4bCcs= =wxZr -----END PGP SIGNATURE----- --eGwqSfc1DN4LzNjY-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 1 19:19:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from netsrvr.ami.com.au (netsrvr.ami.com.au [203.55.31.38]) by hub.freebsd.org (Postfix) with ESMTP id 2464937B491 for ; Thu, 1 Feb 2001 19:19:16 -0800 (PST) Received: from emu.os2.ami.com.au (IDENT:root@c0s04.ami.com.au [203.55.31.69]) by netsrvr.ami.com.au (8.9.3/8.9.3) with ESMTP id LAA14546 for ; Fri, 2 Feb 2001 11:19:06 +0800 Received: from possum.os2.ami.com.au (IDENT:summer@possum.os2.ami.com.au [192.168.1.6]) by emu.os2.ami.com.au (8.10.0/8.10.0) with ESMTP id f123INQ05362 for ; Fri, 2 Feb 2001 11:18:43 +0800 Message-Id: <200102020318.f123INQ05362@emu.os2.ami.com.au> X-Mailer: exmh version 2.1.1 10/15/1999 To: freebsd-current@freebsd.org Subject: Re: FreeBSD-SA-01:19.local In-Reply-To: Your message of "Thu, 01 Feb 2001 19:02:36 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 02 Feb 2001 11:18:59 +0800 From: John Summerfield Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG mjacob@feral.com said: > Isn't it early for april fool's? Nah. Easter eggs are in the shops. -- Cheers John Summerfield http://www2.ami.com.au/ for OS/2 & linux information. Configuration, networking, combined IBM ftpsites index. Microsoft's most solid OS: http://www.geocities.com/rcwoolley/ Note: mail delivered to me is deemed to be intended for me, for my disposition. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 1 19:23:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from phouka.oss.uswest.net (phouka.oss.uswest.net [204.147.85.48]) by hub.freebsd.org (Postfix) with SMTP id 6BD4637B491 for ; Thu, 1 Feb 2001 19:23:15 -0800 (PST) Received: (qmail 28782 invoked by uid 1123); 2 Feb 2001 03:24:19 -0000 Message-ID: <20010202032419.28780.qmail@phouka.oss.uswest.net> To: freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD-SA-01:19.local In-reply-to: Your message of "Thu, 01 Feb 2001 19:02:36 PST." Date: Thu, 01 Feb 2001 21:24:19 -0600 From: Brett Rabe Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 01 Feb 2001 19:02:36 PST, "Matthew Jacob" wrote: > >Isn't it early for april fool's? Well c'mon, Matt. Given the lack of interesting content (geez, it wasn't even a Good Spoof), do you really think the perps are smart enough to know the difference 'tween 2/1 and 4/1? :) Yawn. Brett --- Brett Rabe brett@uswest.net / 612.664.3078 Senior Systems Engineer Qwest - Internet Services Una salus victus nullam sperare salutem To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 1 19:24:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (okc-65-26-235-186.mmcable.com [65.26.235.186]) by hub.freebsd.org (Postfix) with SMTP id 73D9A37B65D for ; Thu, 1 Feb 2001 19:24:05 -0800 (PST) Received: (qmail 684 invoked by uid 100); 2 Feb 2001 03:24:04 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14970.10324.330741.888469@guru.mired.org> Date: Thu, 1 Feb 2001 21:24:04 -0600 (CST) To: John Summerfield Cc: freebsd-current@freebsd.org Subject: Re: FreeBSD-SA-01:19.local In-Reply-To: <200102020318.f123INQ05362@emu.os2.ami.com.au> References: <200102020318.f123INQ05362@emu.os2.ami.com.au> X-Mailer: VM 6.75 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Summerfield types: > mjacob@feral.com said: > > Isn't it early for april fool's? > Nah. Easter eggs are in the shops. And the fools are forging mail. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 1 19:37:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 2B50037B4EC for ; Thu, 1 Feb 2001 19:37:19 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f123bJh09457 for current@freebsd.org; Thu, 1 Feb 2001 19:37:19 -0800 (PST) Date: Thu, 1 Feb 2001 19:37:19 -0800 From: Alfred Perlstein To: current@freebsd.org Subject: installable snapshot of -current? Message-ID: <20010201193718.X26076@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to install -current on a dual CPU machine with an Adaptec 7880, it's hanging somewhere after the scsi probe (no indication that it's over) and sysinstall starting up. Can anyone recommend a -current snapshot that will work? -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 1 23: 8:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from mgate08.so-net.ne.jp (mgate08.so-net.ne.jp [210.139.254.155]) by hub.freebsd.org (Postfix) with ESMTP id 9953437B491 for ; Thu, 1 Feb 2001 23:07:59 -0800 (PST) Received: from mail.ya3.so-net.ne.jp (mspool11.so-net.ne.jp [210.139.248.11]) by mgate08.so-net.ne.jp (8.8.8+3.0Wbeta9/3.6W00122022) with ESMTP id QAA14612 for ; Fri, 2 Feb 2001 16:07:58 +0900 (JST) Received: from localhost (p84e442.ykhmpc00.ap.so-net.ne.jp [210.132.228.66]) by mail.ya3.so-net.ne.jp (8.9.3/3.7W99092111) with ESMTP id QAA12897 for ; Fri, 2 Feb 2001 16:07:55 +0900 (JST) To: freebsd-current@FreeBSD.org Subject: pcm driver and DEVFS From: Yoshihiro Koya X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Multipart/Mixed; boundary="--Next_Part(Fri_Feb__2_16:07:18_2001_809)--" Content-Transfer-Encoding: 7bit Message-Id: <20010202161129Z.ipfw@ya3.so-net.ne.jp> Date: Fri, 02 Feb 2001 16:11:29 +0900 X-Dispatcher: imput version 990905(IM130) Lines: 253 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----Next_Part(Fri_Feb__2_16:07:18_2001_809)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello, I did make world a couple days ago. The system was built from cvsup'd source on Jan 30: >-------------------------------------------------------------- >>>> elf make world started on Tue Jan 30 06:23:38 JST 2001 >-------------------------------------------------------------- The system uses DEVFS. But I have some issue around sound drivers. I usually use mpg123(Version 0.59r (1999/Jun/15)) or x11amp(version 0.8). Before using DEVFS, I was able to adjust sound volume in the sophisticated manner. But, after installing DEVFS, I wasnt adjust sound volume. It might be difficult to run x11amp with DEVFS. On the other hand, mpg123 works. But, its sound is too loud. Added to this, before install DEVFS, I found /dev/dsp1 or /dev/dsp0 in /dev. But I only found the different kind of files: % ls /dev acd0a cuala0 ptyp0 ttyv3 acd0c dsp1.0 ptyp1 ttyv4 ad0 dsp1.1 random ttyv5 ad0s1g dspW1.0 sndstat ttyv6 ad0s2a dspW1.1 stderr@ ttyv7 ad0s2b fd/ stdin@ ttyv8 ad0s2e fd0 stdout@ ttyv9 ad0s2f io sysmouse ttyva apm kbd0 tty ttyvb apmctl klog ttyd0 ttyvc audio1.0 kmem ttyid0 ttyvd audio1.1 log@ ttyld0 ttyve bpsm0 mem ttyp0 ttyvf console mixer1 ttyp1 tun0 consolectl null ttyv0 urandom cuaa0 pci ttyv1 vga@ cuaia0 psm0 ttyv2 zero The files /dev/dsp1.0 and /dev/dsp1.1 are new to me. Of course, I tried to do % x11amp -e /dev/dsp1.0 % x11amp -e /dev/dsp1.1 % x11amp -e /dev/dspW1.0 % x11amp -e /dev/dspW1.1 But in vain. Does some have solution or suggestion? The output produce uname is as follows: % uname -a FreeBSD current.my.domain 5.0-CURRENT FreeBSD 5.0-CURRENT #0: \ Tue Jan 30 10:07:28 JST 2001 \ root@current.my.domain:/usr/obj/usr/src/sys/current i386 Other information relatated my -current box are attached at the end of this mail. koya ----Next_Part(Fri_Feb__2_16:07:18_2001_809)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Description: The output produced by dmesg Content-Disposition: attachment; filename="dmesg.output" Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Tue Jan 30 10:07:28 JST 2001 root@current.my.domain:/usr/obj/usr/src/sys/current Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (331.64-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0x80000800 real memory = 268435456 (262144K bytes) avail memory = 257638400 (251600K bytes) Preloaded elf kernel "kernel" at 0xc039d000. K6-family MTRR support enabled (2 registers) Using $PIR table, 6 entries at 0xc00fa040 apm0: on motherboard apm0: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 (no driver attached) pci0: at 3.0 (no driver attached) dc0: port 0x2000-0x207f mem 0x41200000-0x412003ff irq 10 at device 5.0 on pci0 dc0: Ethernet address: 00:40:d0:0d:e5:9e miibus0: on dc0 dcphy0: on miibus0 dcphy0: 10baseT, 10baseT-FDX, auto isab0: at device 20.0 on pci0 isa0: on isab0 atapci0: port 0x20a0-0x20af at device 20.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 20.2 (no driver attached) pci0: at 20.3 (no driver attached) atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model MouseMan+, device ID 0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources unknown: can't assign resources sbc0: at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,3 on isa0 pcm1: on sbc0 esscontrol0: at port 0x268-0x26f on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources IP packet filtering initialized, divert disabled, rule-based forwarding disabled, default to deny, logging limited to 100 packets/entry by default IPv6 packet filtering initialized, logging limited to 100 packets/entry dc0 XXX: driver didn't initialize queue mtx lo0 XXX: driver didn't initialize queue mtx ppp0 XXX: driver didn't initialize queue mtx faith0 XXX: driver didn't initialize queue mtx gif0 XXX: driver didn't initialize queue mtx gif1 XXX: driver didn't initialize queue mtx gif2 XXX: driver didn't initialize queue mtx gif3 XXX: driver didn't initialize queue mtx ad0: 19623MB [39870/16/63] at ata0-master UDMA33 acd0: CDROM at ata1-master using PIO4 Mounting root from ufs:/dev/ad0s2a WARNING: Driver mistake: repeat make_dev("tun0") ----Next_Part(Fri_Feb__2_16:07:18_2001_809)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Description: my kernel conf file Content-Disposition: attachment; filename="kernel.conf" # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the NOTES configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in NOTES. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.300 2001/01/27 08:18:36 phk Exp $ machine i386 cpu I586_CPU ident current maxusers 32 makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options DDB options INET #InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options DEVFS #Device Filesystem options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options KBD_INSTALL_CDEV # install a CDEV entry in /dev device isa device eisa device pci device fdc device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives options ATA_STATIC_ID #Static device numbering device atkbdc 1 # At keyboard controller device atkbd # at keyboard device psm # psm mouse device vga # VGA screen device splash device sc 1 device npx device apm device pmtimer device pcm device sio # 8250, 16[45]50 based serial ports device ppc device ppbus # Parallel port bus (required) device miibus # MII bus support device dc # DEC/Intel 21143 and various workalikes device random # Entropy device device loop # Network loopback device ether # Ethernet support device ppp 1 # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device gif 4 # IPv6 and IPv4 tunneling device faith 1 # IPv6-to-IPv4 relaying (translation) device bpf # Berkeley packet filter options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about options IPFIREWALL_VERBOSE_LIMIT=100 #limit verbosity options IPV6FIREWALL #firewall for IPv6 options IPV6FIREWALL_VERBOSE options IPV6FIREWALL_VERBOSE_LIMIT=100 ----Next_Part(Fri_Feb__2_16:07:18_2001_809)---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 2 0:23:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from matrix.eurocontrol.fr (matrix.eurocontrol.fr [147.196.254.254]) by hub.freebsd.org (Postfix) with ESMTP id F0FD837B491 for ; Fri, 2 Feb 2001 00:23:27 -0800 (PST) Received: from caerdonn.eurocontrol.fr (caerdonn.eurocontrol.fr [147.196.51.214]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "caerdonn.eurocontrol.fr", Issuer CN "CA ITM" (verified OK)) by matrix.eurocontrol.fr (Postfix/TLS) with ESMTP id 2B3EB5C54 for ; Fri, 2 Feb 2001 09:23:27 +0100 (CET) Received: by caerdonn.eurocontrol.fr (Postfix/TLS, from userid 1193) id 0B0E94E77; Fri, 2 Feb 2001 09:23:25 +0100 (CET) Date: Fri, 2 Feb 2001 09:23:25 +0100 From: Ollivier Robert To: FreeBSD Current Users' list Subject: Weird behaviour Message-ID: <20010202092325.A93583@caerdonn.eurocontrol.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 5.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I just upgraded with cvsup a June, 4th machine to the latest current and after installworld and buidling a new kernel, the damn thing boots weirdly. After /boot/loader, the kernel seems to boot but doesn't display anything. There's activity on the SCSI bus and on the disks but I can't see anything and the machine doesn't come up anyway. I've read UPDATING, creating /boot/device.hints, merged /etc and all that. What did I miss? -- Ollivier ROBERT -=- Eurocontrol EEC/ITM -=- Ollivier.Robert@eurocontrol.fr FreeBSD caerdonn.eurocontrol.fr 5.0-CURRENT #46: Wed Jan 3 15:52:00 CET 2001 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 2 2:11:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from ntexgswp02.DMZ (smtp.kpnqwest.com [193.242.92.8]) by hub.freebsd.org (Postfix) with ESMTP id A3D9137B6AC for ; Fri, 2 Feb 2001 02:11:16 -0800 (PST) Received: from ntexghub03.kpnqwest.com (unverified) by ntexgswp02.DMZ (Content Technologies SMTPRS 4.1.5) with ESMTP id for ; Fri, 2 Feb 2001 11:13:38 +0100 Received: by ntexghub03 with Internet Mail Service (5.5.2653.19) id ; Fri, 2 Feb 2001 11:11:50 +0100 Message-ID: <31FD3FA70CBED31189E700508B6401712C7398@ntexgpra01> From: "Kozlovsky, Marek" To: "'freebsd-current@freebsd.org'" Subject: RE: Weird behaviour Date: Fri, 2 Feb 2001 11:11:50 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, the same with me, but I cvsup'ed FreeBSD3.5-STABLE, make buildworld, make installworld, reboot .... than the machine boot up, seems to be running, but no services available. The problem is that the machine is a router and I did all the things remotely, so I cannot see console (I'm going there today in the evening). Other strange thing is that it obviously routes :-) but offers no services (sshd, pop3, smtp, nfs ... etc.) Marek Kozlovsky -----Original Message----- From: Ollivier Robert [mailto:roberto@eurocontrol.fr] Sent: Friday, February 02, 2001 9:23 AM To: FreeBSD Current Users' list Subject: Weird behaviour Hi, I just upgraded with cvsup a June, 4th machine to the latest current and after installworld and buidling a new kernel, the damn thing boots weirdly. After /boot/loader, the kernel seems to boot but doesn't display anything. There's activity on the SCSI bus and on the disks but I can't see anything and the machine doesn't come up anyway. I've read UPDATING, creating /boot/device.hints, merged /etc and all that. What did I miss? -- Ollivier ROBERT -=- Eurocontrol EEC/ITM -=- Ollivier.Robert@eurocontrol.fr FreeBSD caerdonn.eurocontrol.fr 5.0-CURRENT #46: Wed Jan 3 15:52:00 CET 2001 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 2 2:51: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from knight.cons.org (knight.cons.org [194.233.237.86]) by hub.freebsd.org (Postfix) with ESMTP id 180F837B4EC; Fri, 2 Feb 2001 02:50:47 -0800 (PST) Received: (from cracauer@localhost) by knight.cons.org (8.11.1/8.11.1) id f12AogV11573; Fri, 2 Feb 2001 11:50:42 +0100 (CET) Date: Fri, 2 Feb 2001 11:50:41 +0100 From: Martin Cracauer To: bde@freebsd.org Cc: current@freebsd.org Subject: Please review sh SIGSTOP fix Message-ID: <20010202115041.A11302@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce (or other -currenter's) would you please have a look at the following sh fix? My brain is a bit rusty and maybe I overlook a drawback. When a child is receiving SIGSTOP, eval continues with the next command. While that is correct for the interactive case (Control-Z and you get the prompt back), it is wrong for a shellscript, which just continues with the next command, never again waiting for the stopped child. Noted when childs from cronjobs were stopped, just to make more processes (by wosch). The fix is not to return from a job wait when the wait returned for a stopped child while in non-interactive mode. This bahaviour seems to be what bash2 and ksh implement. I tested for correct behaviour for finnaly killing the child with and without forgrounding it first. When not foregrouding before killing, the shell continues with the script, which is what the other shells do as well. Thanks Martin Index: jobs.c =================================================================== RCS file: /home/CVS-FreeBSD/src/bin/sh/jobs.c,v retrieving revision 1.27.2.1 diff -u -r1.27.2.1 jobs.c --- jobs.c 2000/06/14 13:42:25 1.27.2.1 +++ jobs.c 2001/02/02 10:28:08 @@ -782,7 +782,8 @@ do { pid = waitproc(block, &status); TRACE(("wait returns %d, status=%d\n", pid, status)); - } while (pid == -1 && errno == EINTR && breakwaitcmd == 0); + } while ((pid == -1 && errno == EINTR && breakwaitcmd == 0) || + (WIFSTOPPED(status) && !iflag)); in_dowait--; if (breakwaitcmd != 0) { breakwaitcmd = 0; -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ As far as I'm concerned, if something is so complicated that you can't ex- plain it in 10 seconds, then it's probably not worth knowing anyway -Calvin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 2 3:19:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from citadel.cequrux.com (citadel.cequrux.com [192.96.22.18]) by hub.freebsd.org (Postfix) with ESMTP id 7CAFA37B401 for ; Fri, 2 Feb 2001 03:19:12 -0800 (PST) Received: (from root@localhost) by citadel.cequrux.com (8.8.8/8.6.9) id NAA25548 for ; Fri, 2 Feb 2001 13:18:58 +0200 (SAST) Received: by citadel.cequrux.com via recvmail id 25546; Fri Feb 2 13:18:27 2001 Message-ID: <3A7A7F59.5785FCEF@cequrux.com> Date: Fri, 02 Feb 2001 11:35:21 +0200 From: Graham Wheeler Organization: Cequrux Technologies X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.0.36 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: /boot/device.hints file Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all I just cvsupped to FreeBSD-current yesterday, after running stable for quite a while, mostly because I'd like to try the ACPI support in the hope that I will extend the battery life on my laptop. When trying to compile the kernel, I get an error saying I should install a /boot/device.hints file first. I don't see anything in the manpages or archives about this. Can someone please enlighten me as to what this file should be? TIA gram -- Dr Graham Wheeler E-mail: gram@cequrux.com Director, Research and Development WWW: http://www.cequrux.com CEQURUX Technologies Phone: +27(21)423-6065 Firewalls/VPN Specialists Fax: +27(21)424-3656 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 2 3:26:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from teletubbie.het.net.je (teletubbie.het.net.je [192.87.110.29]) by hub.freebsd.org (Postfix) with ESMTP id A178937B491 for ; Fri, 2 Feb 2001 03:25:55 -0800 (PST) Received: by teletubbie.het.net.je (Postfix, from userid 500) id 50E191B20C; Fri, 2 Feb 2001 12:25:53 +0100 (CET) Date: Fri, 2 Feb 2001 12:25:53 +0100 To: Graham Wheeler Cc: freebsd-current@freebsd.org Subject: Re: /boot/device.hints file Message-ID: <20010202122553.A45375@teletubbie.het.net.je> References: <3A7A7F59.5785FCEF@cequrux.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3A7A7F59.5785FCEF@cequrux.com>; from gram@cequrux.com on Fri, Feb 02, 2001 at 11:35:21AM +0200 From: walter@belgers.com (Walter Belgers) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Graham Wheeler wrote: > When trying to compile the kernel, I get an error saying I should > install a /boot/device.hints file first. See the /usr/src/UPDATING file: 20000825: /boot/device.hints is now required for installkernel to succeed. You should copy GENERIC.hints for your architecture into /boot/device.hints. [..] Cheers, Walter. -- Walter Belgers "Si hoc signum legere potes, operis boni in rebus walter@belgers.com Latinis alacribus et fructuosis potiri potes!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 2 3:27:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from matrix.eurocontrol.fr (matrix.eurocontrol.fr [147.196.254.254]) by hub.freebsd.org (Postfix) with ESMTP id CCF0E37B491 for ; Fri, 2 Feb 2001 03:27:32 -0800 (PST) Received: from caerdonn.eurocontrol.fr (caerdonn.eurocontrol.fr [147.196.51.214]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "caerdonn.eurocontrol.fr", Issuer CN "CA ITM" (verified OK)) by matrix.eurocontrol.fr (Postfix/TLS) with ESMTP id 3352B5BFB for ; Fri, 2 Feb 2001 12:27:32 +0100 (CET) Received: by caerdonn.eurocontrol.fr (Postfix/TLS, from userid 1193) id 73FD34E77; Fri, 2 Feb 2001 12:27:31 +0100 (CET) Date: Fri, 2 Feb 2001 12:27:31 +0100 From: Ollivier Robert To: FreeBSD Current Users' list Subject: Wierd behaviour [UPDATE] Message-ID: <20010202122731.C93603@caerdonn.eurocontrol.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 5.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Update to my previous mail: trying a PRE_SMPNG kernel doesn't change anything, it still displays nothing. I've also updated my /boot/loader and bootblocks. Still no idea? -- Ollivier ROBERT -=- Eurocontrol EEC/ITM -=- Ollivier.Robert@eurocontrol.fr FreeBSD caerdonn.eurocontrol.fr 5.0-CURRENT #46: Wed Jan 3 15:52:00 CET 2001 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 2 3:38: 6 2001 Delivered-To: freebsd-current@freebsd.org Received: from sigma.buy.pl (sigma.buy.pl [213.77.43.210]) by hub.freebsd.org (Postfix) with ESMTP id F20F837B503 for ; Fri, 2 Feb 2001 03:37:37 -0800 (PST) Received: by sigma.buy.pl (Postfix, from userid 1002) id 98E92B790; Fri, 2 Feb 2001 12:37:16 +0100 (CET) Date: Fri, 2 Feb 2001 12:37:16 +0100 From: Karol Makowski To: Graham Wheeler Cc: freebsd-current@freebsd.org Subject: Re: /boot/device.hints file Message-ID: <20010202123716.A11423@sigma.buy.pl> References: <3A7A7F59.5785FCEF@cequrux.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline User-Agent: Mutt/1.3.12i In-Reply-To: <3A7A7F59.5785FCEF@cequrux.com>; from gram@cequrux.com on Fri, Feb 02, 2001 at 11:35:21AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 2001-02-02 at 11:35:21, Graham Wheeler wrote: [cut] > I don't see anything in the manpages or archives about this. Can someone > please enlighten me as to what this file should be? Try /usr/src/UPDATING -- Karol Makowski Market Internetowy Click And Buy sp z o.o. http://www.buy.pl GSM: +48 606 926599 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 2 4:45:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from server.bitmcnit.bryansk.su (bitmcnit.bryansk.ru [195.239.213.9]) by hub.freebsd.org (Postfix) with ESMTP id 619B437B4EC for ; Fri, 2 Feb 2001 04:44:06 -0800 (PST) Received: (from uucp@localhost) by server.bitmcnit.bryansk.su (8.9.3/8.9.3) with UUCP id PAA27764; Fri, 2 Feb 2001 15:27:13 +0300 Received: (from alex@localhost) by kapran.bitmcnit.bryansk.su (8.11.1/8.11.1) id f12CTAO01690; Fri, 2 Feb 2001 15:29:11 +0300 (MSK) (envelope-from kapr@acm.org) X-Authentication-Warning: kapran.bitmcnit.bryansk.su: alex set sender to kapr@acm.org using -f Date: Fri, 2 Feb 2001 15:29:09 +0300 From: Alex Kapranoff To: Yoshihiro Koya Cc: freebsd-current@FreeBSD.ORG Subject: Re: pcm driver and DEVFS Message-ID: <20010202152909.A1608@kapran.bitmcnit.bryansk.su> References: <20010202161129Z.ipfw@ya3.so-net.ne.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010202161129Z.ipfw@ya3.so-net.ne.jp>; from Yoshihiro.Koya@math.yokohama-cu.ac.jp on Fri, Feb 02, 2001 at 04:11:29PM +0900 X-Operating-System: FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Feb 02, 2001 at 04:11:29PM +0900, Yoshihiro Koya wrote: > Hello, > > I did make world a couple days ago. The system was built from cvsup'd > source on Jan 30: > >-------------------------------------------------------------- > >>>> elf make world started on Tue Jan 30 06:23:38 JST 2001 > >-------------------------------------------------------------- > > The system uses DEVFS. But I have some issue around sound drivers. > I usually use mpg123(Version 0.59r (1999/Jun/15)) > or x11amp(version 0.8). Before using DEVFS, I was able to adjust > sound volume in the sophisticated manner. > But, after installing DEVFS, I wasnt adjust sound volume. > It might be difficult to run x11amp with DEVFS. > On the other hand, mpg123 works. But, its sound is too loud. > > Added to this, before install DEVFS, I found /dev/dsp1 or /dev/dsp0 > in /dev. But I only found the different kind of files: > > % ls /dev [skip] > The files /dev/dsp1.0 and /dev/dsp1.1 are new to me. Of course, > I tried to do > % x11amp -e /dev/dsp1.0 > % x11amp -e /dev/dsp1.1 > % x11amp -e /dev/dspW1.0 > % x11amp -e /dev/dspW1.1 > But in vain. > > Does some have solution or suggestion? Yep. I have these in my /etc/rc.devfs: ================= ln -fs /dev/audio1.0 /dev/audio ln -fs /dev/dsp1.0 /dev/dsp ln -fs /dev/mixer1 /dev/mixer ================= This produces almost exactly same environment both with DEVFS and without. -- Alex Kapranoff, Voice: +7(0832)791845 We've lived 32 days in the brand new millenium... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 2 5:56:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from greenlamp.co.kr (unknown [211.104.114.67]) by hub.freebsd.org (Postfix) with SMTP id 562B237B401 for ; Fri, 2 Feb 2001 05:56:22 -0800 (PST) Received: Mail From: vishel@mypersonalemail.com To: yantil@techspot.com X-Mailer: Mozilla 3.0C-WorldNet (Win95; U) Message-Id: <5an51b.103l2c1v7u4x@yahoo.com> Date: Fri, 02 Feb 2001 05:55:46 -0800 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: 8BIT Subject: GET LOANS UP TO $1,000,000 Bad Credit OK! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG catalyst_mortgage

Mortgage Services 4 You

Helping To Make Your Dreams Come True

What are your immediate dreams? Do you want to Refinance your existing loan, purchase a new home, consolidate your bills, make home improvements or just want some extra cash for a vacation or to start a business? Whatever your needs we can help. It's easy to qualify and your loan review is FREE…

HOME IMPROVEMENT LOANS

                     DEBT CONSOLIDATION LOANS

                                                     REFINANCE LOANS

                                                                               CASH OUT LOANS

Qualifying is at your fingertips. Many of the NEW Loan Programs offer Home-Owners the ability to consolidate bills into ONE low monthly payment. Benefits of this type of loan include tax advantages and interest savings. Programs for Home-Owners only.

Pay off existing high-interest loans, credit cards, student loans, medical and personal bills. Purchase or payoff vehicles, motorcycles and RV's. Money for building pools, spas, decks, remodeling, tuition, weddings, vacations, business, or just about anything. Debt Consolidation, Home Improvement or Cash-Out Loans are available for qualified applicants. Re-finance your existing loan for a lower rate.

NO up-front fees, and in most cases approval is possible within 24 hours. CASH can be in your hands within a couple of weeks after approval.

Applying is EASY - just…  Click Here
To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 2 6:22:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from cocoa.globalgold.co.uk (cocoa.globalgold.co.uk [212.250.240.8]) by hub.freebsd.org (Postfix) with ESMTP id AF28F37B401; Fri, 2 Feb 2001 06:22:04 -0800 (PST) Received: from stephen (tnt-9-213.easynet.co.uk [195.40.198.213]) by cocoa.globalgold.co.uk (8.9.1/8.9.1) with SMTP id NAA08147; Fri, 2 Feb 2001 13:40:43 GMT From: "Mailer" To: Subject: Win a top of the range iMac, Palm Pilot or Discman Date: Fri, 2 Feb 2001 13:36:09 -0000 Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01C08D1D.1A005010" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0007_01C08D1D.1A005010 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Connect to your future and start 2001 as a winner Win a top of the range iMac, Palm Pilot or DiskMan All you have to do to win is register with planetgraduate, the new international site for students, graduates and employers. Simply click here to get started Take just a few seconds to register and enter our draw to win either a Palm Pilot or Sony DiskMan. Take a few minutes more and enter your CV with planetgraduate's CV Builder and you could win the incredibly cool iMac and be connected to the Internet in a couple of clicks. Enter our prize draw today to win one of these top prizes:- A top of the range iMac One of two Palm Pilots One of three Portable CD players DiskMan iMac Palm Pilot PS Double your chances of winning a DiskMan or Palm Pilot by helping us let your friends know about this great competition. The draw will take place on Friday 23rd February 2001 Prizes may differ from models shown get a job now | study net . the village | relax & enjoy . top deals | behind the scenes contact us . privacy policy . terms of use . copyright ------=_NextPart_000_0007_01C08D1D.1A005010 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
3D"go 3Dplanetgraduate
     
Connect to your=20 future and start 2001 as a winner
Win=20 a top of the range iMac, Palm Pilot or=20 DiskMan
 

All=20 you have to do to win is register with planetgraduate, the = new=20 international site for students, graduates and employers. =
S= imply=20 click here to get started

Take = just a few=20 seconds to register and enter our draw to win either a Palm = Pilot or=20 Sony DiskMan. Take a few minutes more and enter your CV with = planetgraduate's CV Builder and you could win the incredibly = cool=20 iMac and be connected to the Internet in a couple of clicks. =

   
Enter our = prize draw=20 today to win one of these top = prizes:-
A top of the range iMac
One of two = Palm Pilots=20
One of three Portable CD = players
 
  3D"WIN 3D"Win 3D"Win  
  DiskMan iMac Palm=20 Pilot  
 
  P= S=20 Double your chances of winning a DiskMan or Palm Pilot by = helping us=20 let your friends know about this great = competition.
 
The draw will take place on Friday 23rd February = 2001
 
Prizes may differ from models = shown
 
  get=20 a job now  |  study=20 net  .  the=20 village  |  relax=20 & enjoy  .  top=20 deals&nbs= p; |  behind= =20 the = scenes    
  contact=20 us  .  privacy=20 policy  .  terms=20 of use  .  copyright
 ------=_NextPart_000_0007_01C08D1D.1A005010-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 2 7:13: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from syncopation-01.iinet.net.au (syncopation-01.iinet.net.au [203.59.24.37]) by hub.freebsd.org (Postfix) with SMTP id D786437B401 for ; Fri, 2 Feb 2001 07:12:43 -0800 (PST) Received: (qmail 16746 invoked by uid 666); 2 Feb 2001 15:20:01 -0000 Received: from reggae-14-13.nv.iinet.net.au (HELO elischer.org) (203.59.77.13) by mail.m.iinet.net.au with SMTP; 2 Feb 2001 15:20:01 -0000 Message-ID: <3A7ACE50.7B13BFBB@elischer.org> Date: Fri, 02 Feb 2001 07:12:16 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Peter Jeremy Cc: current@FreeBSD.ORG Subject: Re: kernel threading: the first steps [patch] References: <200101270833.AAA75738@InterJet.elischer.org> <20010129155033.K52423@gsmx07.alcatel.com.au> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Jeremy wrote: > > On 2001-Jan-27 00:33:23 -0800, Root Dude wrote: > >I've broken the proc structure into 4 structures. > > Leaving aside the issue of whether or your efforts were a waste of time, > I have some comments on the ordering of fields. Since the fields are > being re-arranged anyway, I'd like to suggest that the implementation > characteristics be taken into account. I'm mainly thinking of padding > between fields here. > > A second, far less important issue is the interaction between field > order and code size on the IA32. Given that most structure references > are base+offset, there's an extra 3-byte overhead in accessing fields > more than 127 bytes from the pointer - there's no direct speed penalty > except on the 80386, but there is an indirect penalty for larger code > (ie bigger cache footprint). This suggests that fields with a high > static reference count should be towards the front of structures. to counter this, it has been reported that puting fields elsewher can reduce cache thrashing as most structures have the important fields at the front. It's hard to know which effect would be greater.. :-) > > Peter -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 2 7:31:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from syncopation-03.iinet.net.au (syncopation-03.iinet.net.au [203.59.24.49]) by hub.freebsd.org (Postfix) with SMTP id 381D437B491 for ; Fri, 2 Feb 2001 07:31:34 -0800 (PST) Received: (qmail 20823 invoked by uid 666); 2 Feb 2001 15:39:33 -0000 Received: from reggae-14-13.nv.iinet.net.au (HELO elischer.org) (203.59.77.13) by mail.m.iinet.net.au with SMTP; 2 Feb 2001 15:39:33 -0000 Message-ID: <3A7AD2BA.97D6F15C@elischer.org> Date: Fri, 02 Feb 2001 07:31:06 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Idea Receiver Cc: freebsd-current@FreeBSD.ORG Subject: Re: about ppp.. References: Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Idea Receiver wrote: > > On Fri, 26 Jan 2001, Julian Elischer wrote: > > how 'current' are your systems? > > when did this behaviour start? > > (i.e. before or after the latest round of netgraph changes?) > > it is before new netgraph... > i think the new netgraph cause the same problem as well.. can you give more information on this problem? -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 2 9: 9:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from cr66388-a.rchrd1.on.wave.home.com (cr66388-a.rchrd1.on.wave.home.com [24.114.165.24]) by hub.freebsd.org (Postfix) with ESMTP id B57B337B4EC for ; Fri, 2 Feb 2001 09:09:07 -0800 (PST) Received: from cr66388-a.rchrd1.on.wave.home.c (localhost [127.0.0.1]) by cr66388-a.rchrd1.on.wave.home.com (Postfix) with ESMTP id A0800BAAD; Fri, 2 Feb 2001 12:09:07 -0500 (EST) X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.3 To: Ollivier Robert Cc: "FreeBSD Current Users' list" Subject: Re: Wierd behaviour [UPDATE] In-Reply-To: Message from Ollivier Robert of "Fri, 02 Feb 2001 12:27:31 +0100." <20010202122731.C93603@caerdonn.eurocontrol.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 02 Feb 2001 12:09:07 -0500 From: Jake Burkholder Message-Id: <20010202170907.A0800BAAD@cr66388-a.rchrd1.on.wave.home.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Update to my previous mail: > > trying a PRE_SMPNG kernel doesn't change anything, it still displays > nothing. I've also updated my /boot/loader and bootblocks. > > Still no idea? Are you running a stripped down kernel? or generic? There's a problem with kernels that are too large not booting. If you bypass /boot/loader and load the kernel directly it should boot; then take everything you don't need out of the kernel config and build a new kernel. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 2 11:34: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 51CCD37B491 for ; Fri, 2 Feb 2001 11:33:51 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f12JXT389922; Fri, 2 Feb 2001 11:33:29 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010202161129Z.ipfw@ya3.so-net.ne.jp> Date: Fri, 02 Feb 2001 11:33:34 -0800 (PST) From: John Baldwin To: Yoshihiro Koya Subject: RE: pcm driver and DEVFS Cc: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 02-Feb-01 Yoshihiro Koya wrote: > Hello, > > I did make world a couple days ago. The system was built from cvsup'd > source on Jan 30: >>-------------------------------------------------------------- >>>>> elf make world started on Tue Jan 30 06:23:38 JST 2001 >>-------------------------------------------------------------- > > The system uses DEVFS. But I have some issue around sound drivers. > I usually use mpg123(Version 0.59r (1999/Jun/15)) > or x11amp(version 0.8). Before using DEVFS, I was able to adjust > sound volume in the sophisticated manner. > But, after installing DEVFS, I wasnt adjust sound volume. > It might be difficult to run x11amp with DEVFS. > On the other hand, mpg123 works. But, its sound is too loud. > > Added to this, before install DEVFS, I found /dev/dsp1 or /dev/dsp0 > in /dev. But I only found the different kind of files: > > % ls /dev > acd0a cuala0 ptyp0 ttyv3 > acd0c dsp1.0 ptyp1 ttyv4 > ad0 dsp1.1 random ttyv5 > ad0s1g dspW1.0 sndstat ttyv6 > ad0s2a dspW1.1 stderr@ ttyv7 > ad0s2b fd/ stdin@ ttyv8 > ad0s2e fd0 stdout@ ttyv9 > ad0s2f io sysmouse ttyva > apm kbd0 tty ttyvb > apmctl klog ttyd0 ttyvc > audio1.0 kmem ttyid0 ttyvd > audio1.1 log@ ttyld0 ttyve > bpsm0 mem ttyp0 ttyvf > console mixer1 ttyp1 tun0 > consolectl null ttyv0 urandom > cuaa0 pci ttyv1 vga@ > cuaia0 psm0 ttyv2 zero > > The files /dev/dsp1.0 and /dev/dsp1.1 are new to me. Of course, > I tried to do > % x11amp -e /dev/dsp1.0 > % x11amp -e /dev/dsp1.1 > % x11amp -e /dev/dspW1.0 > % x11amp -e /dev/dspW1.1 > But in vain. > > Does some have solution or suggestion? Add 'hw.snd.unit=1' to /boot/loader.conf. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/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 Fri Feb 2 11:36: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id 69F2037B491 for ; Fri, 2 Feb 2001 11:35:47 -0800 (PST) Received: (qmail 42522 invoked by uid 1142); 2 Feb 2001 19:35:44 -0000 Date: 2 Feb 2001 11:35:44 -0800 Date: Fri, 2 Feb 2001 11:35:38 -0800 From: Jason Evans To: Mike Heffner Cc: FreeBSD-current Subject: Re: program hangs in thread scheduler Message-ID: <20010202113538.Q17900@canonware.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from mheffner@vt.edu on Thu, Feb 01, 2001 at 02:08:54PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 01, 2001 at 02:08:54PM -0500, Mike Heffner wrote: > > Is this a problem with the thread scheduler or is this somehow related to the > application? > > (gdb) bt > #0 0x284d74cc in poll () from /usr/lib/libc.so.5 > #1 0x2848ce74 in thread_kern_poll (wait_reqd=1) > at /usr/src/lib/libc_r/uthread/uthread_kern.c:833 > #2 0x2848c7c9 in _thread_kern_scheduler () > at /usr/src/lib/libc_r/uthread/uthread_kern.c:481 > #3 0xd0d0d0d0 in ?? () > #4 0x282a66cc in g_main_run (loop=0x8167b40) at gmain.c:935 > #5 0x281c6047 in gtk_main () from /usr/X11R6/lib/libgtk12.so.2 > #6 0x80590f1 in main (argc=1, argv=0xbfbffb9c) at aim.c:610 > #7 0x80576f9 in _start (arguments=0xbfbffc80 "gaim") > at /usr/src/lib/csu/i386-elf/crt1.c:96 This stack trace looks more or less okay to me. The problem is probably in the application rather than in libc_r. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 2 12: 9: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 080CD37B401; Fri, 2 Feb 2001 12:08:44 -0800 (PST) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.1/8.11.1) with SMTP id f12K8gh33455; Fri, 2 Feb 2001 15:08:43 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Fri, 2 Feb 2001 15:08:42 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: freebsd-current@FreeBSD.org, freebsd-hackers@FreeBSD.org Subject: Watch your devfs permissions in driver make_dev calls 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 Driver developers! As you probably know by now, Poul-Henning has enabled DEVFS in the GENERIC kernel on FreeBSD 5.0-CURRENT. This is a strong feature and it's great to see it getting brought back to life. However! Many of consumers of make_dev() have chosen their default permissions somewhat sloppily, and the results have to be thought through a little. On my workstation, I found the following: crw-r--r-- 1 root operator 117, 0 Dec 31 1969 acd0a crw-r--r-- 1 root operator 117, 2 Dec 31 1969 acd0c .. crw-rw-rw- 1 root wheel 30, 20 Dec 31 1969 audio1.0 crw-rw-rw- 1 root wheel 30, 0x00010014 Dec 31 1969 audio1.1 .. crw-rw-rw- 1 root wheel 21, 0 Dec 31 1969 bpsm0 .. crw-rw-rw- 1 root wheel 30, 19 Dec 31 1969 dsp1.0 crw-rw-rw- 1 root wheel 30, 0x00010013 Dec 31 1969 dsp1.1 crw-rw-rw- 1 root wheel 30, 21 Dec 31 1969 dspW1.0 crw-rw-rw- 1 root wheel 30, 0x00010015 Dec 31 1969 dspW1.1 .. crw-rw-rw- 1 root wheel 30, 16 Dec 31 1969 mixer1 .. crw-r--r-- 1 root wheel 78, 0 Dec 31 1969 pci .. cr--r--r-- 1 root wheel 30, 6 Dec 31 1969 sndstat .. crw-r--r-- 1 root operator 108, 255 Dec 31 1969 usb crw-r--r-- 1 root operator 108, 0 Dec 31 1969 usb0 I've done a brief grep through src/sys/dev/* and noticed a lot of other potential problems. I realize the permissions on a sound device seem a bit trivial, but consider the following scenario: Due to a bug in fingerd, a set of workstations in a mail/phone order center is compromised. The attacker uses the bug in fingerd to gain read access to /dev/audio or /dev/dsp, and streams recordings of all conversations in the room to a remote site where he types in credit card numbers and personal information as he sees fit. Or maybe he exploits the same bugs to listen to administrator conversations in a NOC and pick up router passwords. Some of the permissions above are probably fine, as they're for getting status on busses, etc, but generally speaking, excessively liberal permissions can be a serious problem in /dev. Allow direct read access from CDROM media can give them access to keying material or password crypts for CDROM-booted workstations, or access to 1-time pad data stored on the CD. Or to licensed commercial software or intellectual property. I'm not familiar with the fbtab mechanism, but it may be that we should be adding support for the audiot devices (etc) to it, or making this part of an eventual devd. In any case, the default devfs permissions should be intended to be closed, and then opened as needed by privileged software, rather than open and then closed. Otherwise you introduce race conditions, and unintended consequences. Also, I realize that we have constants in kernel for the wheel and operator groups, but ideally, I'd like to see those be purely userland concepts. The kernel security model generally recognizes one uid, the superuser, as having special privileges over others. Hardcoding other user or group id's into the kernel pushes userland concepts (/etc/passwd, /etc/group, /usr/sbin/login) into the kernel. Setting additional rights for specific groups (operator, tty, etc) can be done as part of a userland boot or login process. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 2 14:11:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (awfulhak.demon.co.uk [194.222.196.252]) by hub.freebsd.org (Postfix) with ESMTP id 3BCEA37B491 for ; Fri, 2 Feb 2001 14:11:13 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.1/8.11.1) with ESMTP id f12MBOv22552; Fri, 2 Feb 2001 22:11:25 GMT (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.2/8.11.1) with ESMTP id f12MCp606056; Fri, 2 Feb 2001 22:12:51 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200102022212.f12MCp606056@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Alex Kapranoff Cc: Yoshihiro Koya , freebsd-current@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: pcm driver and DEVFS In-Reply-To: Message from Alex Kapranoff of "Fri, 02 Feb 2001 15:29:09 +0300." <20010202152909.A1608@kapran.bitmcnit.bryansk.su> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Fri, 02 Feb 2001 22:12:50 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, Feb 02, 2001 at 04:11:29PM +0900, Yoshihiro Koya wrote: > > Hello, > > = > > I did make world a couple days ago. The system was built from cvsup'= d = > > source on Jan 30: > > >-------------------------------------------------------------- > > >>>> elf make world started on Tue Jan 30 06:23:38 JST 2001 > > >-------------------------------------------------------------- > > = > > The system uses DEVFS. But I have some issue around sound drivers. > > I usually use mpg123(Version 0.59r (1999/Jun/15)) > > or x11amp(version 0.8). Before using DEVFS, I was able to adjust > > sound volume in the sophisticated manner. > > But, after installing DEVFS, I wasnt adjust sound volume. > > It might be difficult to run x11amp with DEVFS. > > On the other hand, mpg123 works. But, its sound is too loud. > > = > > Added to this, before install DEVFS, I found /dev/dsp1 or /dev/dsp0 = > > in /dev. But I only found the different kind of files: > > = > > % ls /dev > [skip] > > The files /dev/dsp1.0 and /dev/dsp1.1 are new to me. Of course, > > I tried to do > > % x11amp -e /dev/dsp1.0 > > % x11amp -e /dev/dsp1.1 > > % x11amp -e /dev/dspW1.0 > > % x11amp -e /dev/dspW1.1 > > But in vain. > > = > > Does some have solution or suggestion? > = > Yep. I have these in my /etc/rc.devfs: > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > ln -fs /dev/audio1.0 /dev/audio > ln -fs /dev/dsp1.0 /dev/dsp > ln -fs /dev/mixer1 /dev/mixer > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > = > This produces almost exactly same environment both with DEVFS and witho= ut. Strange. I have a stock rc.devfs and get the above links too :-) $ cd /sys/dev/sounds/pcm $ fgrep make_dev_alias *.c sound.c: dsp =3D make_dev_alias(pdev, "dsp"); sound.c: dspW =3D make_dev_alias(pdev, "dspW"); sound.c: audio =3D make_dev_alias(pdev, "audio"); sound.c: mixer =3D make_dev_alias(pdev, "mixer"); > -- = > Alex Kapranoff, Voice: +7(0832)791845 > We've lived 32 days in the brand new millenium... -- = 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 Fri Feb 2 14:22:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from matrix.eurocontrol.fr (matrix.eurocontrol.fr [147.196.254.254]) by hub.freebsd.org (Postfix) with ESMTP id 85FCF37B401 for ; Fri, 2 Feb 2001 14:22:33 -0800 (PST) Received: from caerdonn.eurocontrol.fr (caerdonn.eurocontrol.fr [147.196.51.214]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "caerdonn.eurocontrol.fr", Issuer CN "CA ITM" (verified OK)) by matrix.eurocontrol.fr (Postfix/TLS) with ESMTP id E3A5F5BEA; Fri, 2 Feb 2001 23:22:32 +0100 (CET) Received: by caerdonn.eurocontrol.fr (Postfix/TLS, from userid 1193) id BD7A84E7F; Fri, 2 Feb 2001 23:22:31 +0100 (CET) Date: Fri, 2 Feb 2001 23:22:31 +0100 From: Ollivier Robert To: Jake Burkholder Cc: FreeBSD Current Users' list Subject: Re: Wierd behaviour [UPDATE] Message-ID: <20010202232231.A48840@caerdonn.eurocontrol.fr> References: <20010202170907.A0800BAAD@cr66388-a.rchrd1.on.wave.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010202170907.A0800BAAD@cr66388-a.rchrd1.on.wave.home.com>; from jburkholder0829@home.com on Fri, Feb 02, 2001 at 12:09:07PM -0500 X-Operating-System: FreeBSD 5.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Jake Burkholder: > Are you running a stripped down kernel? or generic? Heavily trimmed down kernel. I can still boot my June, 4th kernel just fine.... (and it had more things in it). I'm looking at the hints (will try to compile them statically) because it is close to what the comment in UPDATING speaks about but I'm lost if it isn't that... -- Ollivier ROBERT -=- Eurocontrol EEC/ITM -=- Ollivier.Robert@eurocontrol.fr FreeBSD caerdonn.eurocontrol.fr 5.0-CURRENT #46: Wed Jan 3 15:52:00 CET 2001 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 2 16:20:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from hera.drwilco.net (10dyn211.dh.casema.net [212.64.31.211]) by hub.freebsd.org (Postfix) with ESMTP id 2E48937B4EC; Fri, 2 Feb 2001 16:20:29 -0800 (PST) Received: from ceres.drwilco.net (ceres.drwilco.net [10.1.1.19]) by hera.drwilco.net (8.11.1/8.11.1) with ESMTP id f130h2b74340; Sat, 3 Feb 2001 01:43:03 +0100 (CET) (envelope-from drwilco@drwilco.net) Message-Id: <4.3.2.7.0.20010202205233.00d51c30@mail.drwilco.net> X-Sender: drwilco@mail.drwilco.net X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 02 Feb 2001 20:55:37 +0100 To: freebsd-current@freebsd.org, freebsd-net@freebsd.org From: "Rogier R. Mulhuijzen" Subject: Patch for non-netgraph bridge code worthy of attention for people experimenting with bridging setups (including ng_bridge) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I found this while experimenting with both "legacy" bridge and ng_bridge. The bridging code doesn't check its activation everywhere so when I started using an ng_bridge node I started getting weird errors. Patch is rather simple, can someone submit this? DocWilco >Date: Mon, 29 Jan 2001 08:20:01 -0800 (PST) >To: drwilco@drwilco.net >From: gnats-admin@FreeBSD.org >Subject: Re: kern/24720: Bridging code does not always check activation >(w/patch) >Reply-To: gnats-admin@FreeBSD.org, freebsd-bugs@FreeBSD.org >Sender: gnats@FreeBSD.org > >Thank you very much for your problem report. >It has the internal identification `kern/24720'. >The individual assigned to look at your >report is: freebsd-bugs. > >You can access the state of your problem report at any time >via this link: > >http://www.freebsd.org/cgi/query-pr.cgi?pr=24720 > > >Category: kern > >Responsible: freebsd-bugs > >Synopsis: Bridging code does not always check activation (w/patch) > >Arrival-Date: Mon Jan 29 08:20:01 PST 2001 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 2 17: 2:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from volatile.chemikals.org (ci391991-a.grnvle1.sc.home.com [24.9.31.75]) by hub.freebsd.org (Postfix) with ESMTP id 9F20C37B503 for ; Fri, 2 Feb 2001 17:02:19 -0800 (PST) Received: (from morganw@localhost) by volatile.chemikals.org (8.11.1/8.11.1) id f1312I948495; Fri, 2 Feb 2001 20:02:18 -0500 (EST) (envelope-from morganw) Date: Fri, 2 Feb 2001 20:02:18 -0500 (EST) From: Wesley Morgan To: Subject: DEVFS Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With devfs "default" in -current, I have a question about permissions. I know that rc.devfs will set up custom permissions at boot... But what about a device that detaches? When you re-attach, it goes back to the default permissions. This is a bit annoying; is there a workaround for it? Should this be handled by something that does the re-attaching? -- _ __ ___ ____ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ morganw@chemikals.org _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 2 18:14:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id D54B337B401 for ; Fri, 2 Feb 2001 18:14:29 -0800 (PST) Received: from slave (Studded@slave [10.0.0.1]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id SAA47904 for ; Fri, 2 Feb 2001 18:14:29 -0800 (PST) (envelope-from DougB@gorean.org) Date: Fri, 2 Feb 2001 18:14:29 -0800 (PST) From: Doug Barton X-X-Sender: To: Subject: devfs not making vn devices Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been using devfs for a long time without problems. I had device vn in my kernel conf since the pre-devfs days, and today I needed to use a vn device to build picobsd. Lo and behold, I don't have any vn devices of any sort in /dev. I tried 'vnconfig -c /dev/vn0' but it also complained that the device didn't exist. I know that the goal is for vn to be phased out (at least that's my impression) but what do we do in the meantime? Doug -- "Pain heals. Chicks dig scars. Glory . . . lasts forever." -- Keanu Reeves as Shane Falco in "The Replacements" Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 2 18:21:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id 767A737B401 for ; Fri, 2 Feb 2001 18:20:55 -0800 (PST) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id EE09BD06; Fri, 2 Feb 2001 18:20:54 -0800 (PST) Received: from cup.hp.com (gauss.cup.hp.com [15.28.97.152]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id SAA04084; Fri, 2 Feb 2001 18:20:53 -0800 (PST) Message-ID: <3A7B6B05.D1C1A88@cup.hp.com> Date: Fri, 02 Feb 2001 18:20:53 -0800 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Andrea Campi Cc: freebsd-current@FreeBSD.ORG Subject: Re: RFC: user-config alt path in Linux emulation References: <20010131112104.B2268@webcom.it> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrea Campi wrote: > > When running a Linux binary in Linux compat mode, all calls to open(), > readdir() and such, end up calling linux_emul_find() from linux_util.c. > This functions looks for a directory/file with the same name in the > /compat/linux hierarchy. > The net effect is that there is no way to, for instance, back up the > real /usr from Tivoli, etc... as there is no way to get to a real path > if there is anything with the same name inside /compat/linux. > > I'd like to understand if there is any accepted way to work around this > limitation (no, symlinks are not an option :-p), I'm sure not. /compat is already a symlink (to /usr/compat to be precise). What's with symlinks that it can't be an option? -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 2 18:24:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from RedDust.bluesky.net.au (CPE-61-9-140-11.vic.bigpond.net.au [61.9.140.11]) by hub.freebsd.org (Postfix) with ESMTP id 3446137B401 for ; Fri, 2 Feb 2001 18:23:57 -0800 (PST) Received: from localhost (receiver@localhost) by RedDust.bluesky.net.au (8.11.1/8.11.0) with ESMTP id f132M5k41343; Sat, 3 Feb 2001 12:22:05 +1000 (EST) (envelope-from receiver@blueskybbs.yi.org) Date: Sat, 3 Feb 2001 12:22:05 +1000 (EST) From: Idea Receiver To: Julian Elischer Cc: Idea Receiver , freebsd-current@FreeBSD.ORG Subject: Re: about ppp.. In-Reply-To: <3A7AD2BA.97D6F15C@elischer.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 Fri, 2 Feb 2001, Julian Elischer wrote: > Idea Receiver wrote: > > > > On Fri, 26 Jan 2001, Julian Elischer wrote: > > > how 'current' are your systems? > > > when did this behaviour start? > > > (i.e. before or after the latest round of netgraph changes?) > > > > it is before new netgraph... > > i think the new netgraph cause the same problem as well.. > > > can you give more information on this problem? i cant remember when the exact day the problem started. i did a cvsup/make world recently, the problem is still exist. btw, i am running PPPoE. but the problem also exists in simple PPP (modem) connection as well. btw, i have found, if I try to download something like 1G, I havnt see any problem occer, the download speed is fairly constant. however, the problem always happen when someone try to play on-line game, or maybe try to receive/sent icq files, or reading web pages, or even just doing a dns request, then this lagging problem often happen. the ppp.config is fairly stander shows as follow, set device PPPoE:rl0 set mru 1454 set mtu 1454 set speed sync enable lqr set cd 4 set authname xxxxxxx set authkey xxxxxxxxx set dial set login set redial 30 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 2 18:28:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 84B2F37B401 for ; Fri, 2 Feb 2001 18:28:34 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f132SC301387; Fri, 2 Feb 2001 18:28:12 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 02 Feb 2001 18:28:21 -0800 (PST) From: John Baldwin To: Doug Barton Subject: RE: devfs not making vn devices Cc: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-Feb-01 Doug Barton wrote: > I've been using devfs for a long time without problems. I had > device vn in my kernel conf since the pre-devfs days, and today I needed > to use a vn device to build picobsd. Lo and behold, I don't have any vn > devices of any sort in /dev. I tried 'vnconfig -c /dev/vn0' but it also > complained that the device didn't exist. > > I know that the goal is for vn to be phased out (at least that's > my impression) but what do we do in the meantime? > > Doug mdconfig(8) has all of the functionality of vnconfig now, along with all the functionality of the old md(4) driver. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/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 Fri Feb 2 19:23: 7 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp.interlog.com (bretweir.total.net [154.11.89.176]) by hub.freebsd.org (Postfix) with SMTP id F0C6237B401 for ; Fri, 2 Feb 2001 19:22:49 -0800 (PST) Received: (qmail 24585 invoked from network); 3 Feb 2001 03:22:46 -0000 Received: from unknown (HELO vws3.interlog.com) (207.34.202.29) by bretweir.total.net with SMTP; 3 Feb 2001 03:22:46 -0000 Received: by vws3.interlog.com (8.9.0/8.9.0) id WAA17731; Fri, 2 Feb 2001 22:22:48 -0500 (EST) Date: Fri, 2 Feb 2001 22:22:48 -0500 (EST) Message-Id: <200102030322.WAA17731@vws3.interlog.com> To: freebsd-current@FreeBSD.ORG From: FreeBSD Security Advisories Subject: FreeBSD Security Advisory: FreeBSD-SA-01:20.egos Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ============================================================================= FreeBSD-SA-01:09 Security Advisory FreeBSD, Inc. Topic: Local ego exploit Category: (l)users Announced: 2001-02-03 Credits: AntiOffline.com, Disgraced.org, Deficiency.org sil, deran9ed Affects: All released (l)users of FreeBSD Corrected: (l)Users should seek psychotherapy shock therapy, along with multiple doses of Thorazine chased by 2 shots of Liquid Draino for maximum effectivity Vendor status: Feelings still hurting while crying over spilled milk. FreeBSD only: YES and some of their (l)users I. Background FreeBSD (l)users became disgruntled about the original advisory concerning the bloated remarks aimed towards their chopperating sysdumb. This became an issue for some on Internet Relay Chat, and caused them to ban others' connection since their ego's had been hurt. (boo fsckin hoo) II. Problem Description Penis envy seems to be the number one cause, and we are trying to differentiate between the women who still have penises, that are crying (game) foul. For the hermies we suggest counseling, and estrogen treatment followed by a visit to fellow hermie JP @ AntiOnline.com as well as the switch hitting lesbo at http://www.happyhacker.org in an effort to ass!ess their sexualities. Egos can be strengthened by practicing humility and learning that once in a while it is a good thing to actually have a good laugh, although to those whose egos' that have been hurt we suggest that you replace the batteries in your dildos and reinsert them into your anal crevices. III. Impact None to those with a sense of humor, although those without them will grow old and become miserable rootards, capable of placing razor blades, crushed glass, and cyanide, in the bags of small children who are out for Halloween Trick or Treating. IV. Workaround Take a look at your own shortcomings before judging others. V. Solution Socialize a bit more. VI. Shouts Marshall Mathers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 2 20: 6:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id 0D02837B401 for ; Fri, 2 Feb 2001 20:06:30 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f1346LW35039; Fri, 2 Feb 2001 20:06:23 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200102030406.f1346LW35039@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Doug Barton Cc: freebsd-current@FreeBSD.ORG Subject: Re: devfs not making vn devices In-Reply-To: Date: Fri, 02 Feb 2001 20:06:21 -0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Barton wrote: > I've been using devfs for a long time without problems. I had > device vn in my kernel conf since the pre-devfs days, and today I needed > to use a vn device to build picobsd. Lo and behold, I don't have any vn > devices of any sort in /dev. I tried 'vnconfig -c /dev/vn0' but it also > complained that the device didn't exist. > > I know that the goal is for vn to be phased out (at least that's > my impression) but what do we do in the meantime? In the meantime? besides using mdconfig, try this: mkdir /dev2 cd /dev2 sh /usr/src/etc/MAKEDEV vn0 vnconfig -c /dev2/vn0 .... > Doug Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 2 20:10:29 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id EA3AC37B401; Fri, 2 Feb 2001 20:10:10 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f134AAW35066; Fri, 2 Feb 2001 20:10:10 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200102030410.f134AAW35066@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Robert Watson Cc: freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Watch your devfs permissions in driver make_dev calls In-Reply-To: Date: Fri, 02 Feb 2001 20:10:10 -0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert Watson wrote: > crw-r--r-- 1 root wheel 78, 0 Dec 31 1969 pci This one may appear harmless, but it is not. It is trivially easy to create an alignment fault (fatal on an alpha) with the userland pciconf tool. We must not allow this to be used by users until the kernel part is fixed. Eg: try this on an alpha: pciconf -r -l pci0:x:x 0x3 - ie: read a longword at byte offset 3 in configuration space.. kaboom! Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 2 20:16:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 3B1D737B401 for ; Fri, 2 Feb 2001 20:15:52 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f134Dd949495; Fri, 2 Feb 2001 21:13:40 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200102030413.f134Dd949495@harmony.village.org> To: Poul-Henning Kamp Subject: Re: DEVFS newbie... Cc: John Indra , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Mon, 29 Jan 2001 07:16:15 +0100." <18334.980748975@critter> References: <18334.980748975@critter> Date: Fri, 02 Feb 2001 21:13:39 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <18334.980748975@critter> Poul-Henning Kamp writes: : >1. Say I want to use DEVFS, what should I change? : : Nothing. Just add DEVFS to your kernel config file. So it updates /dev all by itself? What if I want dev nodes elsewhere in the tree, say for a jail? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 2 20:19:20 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 2C20037B491 for ; Fri, 2 Feb 2001 20:19:02 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f134It949537; Fri, 2 Feb 2001 21:18:55 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200102030418.f134It949537@harmony.village.org> To: Julian Elischer Subject: Re: DEVFS newbie... Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Mon, 29 Jan 2001 23:04:29 PST." <3A76677C.1F1EBFF1@elischer.org> References: <3A76677C.1F1EBFF1@elischer.org> Date: Fri, 02 Feb 2001 21:18:55 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3A76677C.1F1EBFF1@elischer.org> Julian Elischer writes: : you can't.. what is the major number? : : You don't know because they will be dynamically assigned. : Only the kernel knows. : Eventually, major numbers may go away entirely, (or just be a : comlpetely random meaningless number, present only to keep old : programs like tar() happy). What if I want to create a few devices (eg not all in the system) in a chroot'd environment? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 3 0:24:35 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 46B4C37B67D for ; Sat, 3 Feb 2001 00:24:14 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f138OHB11750; Sat, 3 Feb 2001 09:24:17 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Doug Barton Cc: freebsd-current@FreeBSD.ORG Subject: Re: devfs not making vn devices In-Reply-To: Your message of "Fri, 02 Feb 2001 18:14:29 PST." Date: Sat, 03 Feb 2001 09:24:17 +0100 Message-ID: <11748.981188657@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Doug Barton writes: > I've been using devfs for a long time without problems. I had >device vn in my kernel conf since the pre-devfs days, and today I needed >to use a vn device to build picobsd. Lo and behold, I don't have any vn >devices of any sort in /dev. I tried 'vnconfig -c /dev/vn0' but it also >complained that the device didn't exist. Use md instead of vn, it has all the same (and more) functionality. See mdconfig(8). -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 3 0:28: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id C287A37B401 for ; Sat, 3 Feb 2001 00:27:47 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f138RgB11877; Sat, 3 Feb 2001 09:27:42 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Warner Losh Cc: John Indra , freebsd-current@FreeBSD.ORG Subject: Re: DEVFS newbie... In-Reply-To: Your message of "Fri, 02 Feb 2001 21:13:39 MST." <200102030413.f134Dd949495@harmony.village.org> Date: Sat, 03 Feb 2001 09:27:42 +0100 Message-ID: <11875.981188862@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200102030413.f134Dd949495@harmony.village.org>, Warner Losh writes: >In message <18334.980748975@critter> Poul-Henning Kamp writes: >: >1. Say I want to use DEVFS, what should I change? >: >: Nothing. Just add DEVFS to your kernel config file. > >So it updates /dev all by itself? What if I want dev nodes elsewhere >in the tree, say for a jail? mount -t devfs devfs /home/jail/dev would work, but all dynamic devices would appear there too. Once we have an extensible facility for mount options, you will be able to say: mount -t devfs devfs /home/jail/dev ( cd /home/jail/dev ; rm $devices_i_dont_want_in_my_jails ) mount -u -o nonewdev /home/jail/dev To solve that problem. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 3 0:35:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from pascal.math.yokohama-cu.ac.jp (unknown [163.212.93.141]) by hub.freebsd.org (Postfix) with ESMTP id 8980F37B401; Sat, 3 Feb 2001 00:35:35 -0800 (PST) Received: from localhost (pluto [163.212.97.157]) by pascal.math.yokohama-cu.ac.jp (8.9.3/3.7W) with ESMTP id RAA03626; Sat, 3 Feb 2001 17:37:11 +0900 (JST) To: jhb@FreeBSD.org, kapr@acm.org, brian@Awfulhak.org Cc: Yoshihiro.Koya@math.yokohama-cu.ac.jp, freebsd-current@FreeBSD.org Subject: RE: pcm driver and DEVFS From: Yoshihiro Koya In-Reply-To: References: <20010202161129Z.ipfw@ya3.so-net.ne.jp> <20010202152909.A1608@kapran.bitmcnit.bryansk.su> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010203174049B.koya@math.yokohama-cu.ac.jp> Date: Sat, 03 Feb 2001 17:40:49 +0900 X-Dispatcher: imput version 990905(IM130) Lines: 41 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Thank you for advices. Now I obtain same environment as of pre-devfs days. From: Alex Kapranoff Date: Fri, 2 Feb 2001 15:29:09 +0300 > Yep. I have these in my /etc/rc.devfs: > ================= > ln -fs /dev/audio1.0 /dev/audio > ln -fs /dev/dsp1.0 /dev/dsp > ln -fs /dev/mixer1 /dev/mixer > ================= > > This produces almost exactly same environment both with DEVFS and without. I tried this solusion. Everything around sound drivers works. But, the another solution From: John Baldwin Date: Fri, 02 Feb 2001 11:33:34 -0800 (PST) > Add 'hw.snd.unit=1' to /boot/loader.conf. also works fine. The links suggested by the above also created automatically. In order to examin this, I commented out the lines looks like: > ln -fs /dev/audio1.0 /dev/audio > ln -fs /dev/dsp1.0 /dev/dsp > ln -fs /dev/mixer1 /dev/mixer and reboot the system, I found actually /dev/dsp, /dev/audio and so on. Finally, please let me point out that there are no description about hw.snd.unit MIB in sysctl(8) manpage yet. Thanks!! koya To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 3 0:49:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from syncopation-01.iinet.net.au (syncopation-01.iinet.net.au [203.59.24.37]) by hub.freebsd.org (Postfix) with SMTP id 675EE37B4EC for ; Sat, 3 Feb 2001 00:48:47 -0800 (PST) Received: (qmail 27006 invoked by uid 666); 3 Feb 2001 08:55:48 -0000 Received: from reggae-08-177.nv.iinet.net.au (HELO elischer.org) (203.59.3.177) by mail.m.iinet.net.au with SMTP; 3 Feb 2001 08:55:48 -0000 Message-ID: <3A7BC5C4.75247E49@elischer.org> Date: Sat, 03 Feb 2001 00:48:04 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: "Rogier R. Mulhuijzen" Cc: freebsd-current@freebsd.org, freebsd-net@freebsd.org Subject: Re: Patch for non-netgraph bridge code worthy of attention forpeople experimenting with bridging setups (including ng_bridge) References: <4.3.2.7.0.20010202205233.00d51c30@mail.drwilco.net> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Rogier R. Mulhuijzen" wrote: > > I found this while experimenting with both "legacy" bridge and ng_bridge. > The bridging code doesn't check its activation everywhere so when I started > using an ng_bridge node I started getting weird errors. > > Patch is rather simple, can someone submit this? I'm a litle confused when I look at this patch. I think this is the wrong fix. I see that you are accounting for packets coming in on two interfaces, but the aim of the netgraph bridging is to make it look as if the packets are all coming in off one interface. Theoretically the bridging code should be attached to only one 'upper' part of a driver and all packets should arrive at higher levels, looking as if they have all come in through that one interface. The other interfaces in the bridge will never receive anything because their input has been diverted. To the system it should look as if the entire bridged network is on that one interface. If this is not the case then we need to fix the bridging code so that it is true, rather than clutter up higher level code trying to account for a bug in the lower code. So how can an incoming packet look like it is not coming from that single interface? 1/ ifnet pointer. The function ng_ether_rcv_upper() adjust this, so that's not the problem. 2/ rcv interface MAC address. This is stripped off before arp gets it (also in ng_ether_rcv_upper()). 3/ the tha[] or sha[] fields may contain a MAC address for some other interface. (depending on how the remote mechine fills out those fields), but our outgoing packets should have the MAC address of the interface we have selected as out main interface, independent of which interface it actually goes out of, (unless the hardware over-writes it). so even that should point to the single interface. The other interfaces should (maybe) beb ifconfigged 'UP' but they should not have IP addresses assigned tp them, as they are being slaved from the main interface by the ng_bridging code so everything comes and goes via that one. so I'm slightly confused as to what problem this solves. (I'm not saying there isn't one, just that I con't figure out what it is). Everything should act as if there is just one interface when netgraph bridging is turned on. > > DocWilco > > >Date: Mon, 29 Jan 2001 08:20:01 -0800 (PST) > >To: drwilco@drwilco.net > >From: gnats-admin@FreeBSD.org > >Subject: Re: kern/24720: Bridging code does not always check activation > >(w/patch) > >Reply-To: gnats-admin@FreeBSD.org, freebsd-bugs@FreeBSD.org > >Sender: gnats@FreeBSD.org > > > >Thank you very much for your problem report. > >It has the internal identification `kern/24720'. > >The individual assigned to look at your > >report is: freebsd-bugs. > > > >You can access the state of your problem report at any time > >via this link: > > > >http://www.freebsd.org/cgi/query-pr.cgi?pr=24720 > > > > >Category: kern > > >Responsible: freebsd-bugs > > >Synopsis: Bridging code does not always check activation (w/patch) > > >Arrival-Date: Mon Jan 29 08:20:01 PST 2001 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 3 1:22:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id A117537B401 for ; Sat, 3 Feb 2001 01:22:15 -0800 (PST) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f139I8P82171; Sat, 3 Feb 2001 01:18:08 -0800 (PST) (envelope-from jkh@winston.osd.bsdi.com) To: Poul-Henning Kamp Cc: Warner Losh , John Indra , freebsd-current@FreeBSD.ORG Subject: Re: DEVFS newbie... In-Reply-To: Message from Poul-Henning Kamp of "Sat, 03 Feb 2001 09:27:42 +0100." <11875.981188862@critter> Date: Sat, 03 Feb 2001 01:18:08 -0800 Message-ID: <82167.981191888@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Once we have an extensible facility for mount options, you will be > able to say: > > mount -t devfs devfs /home/jail/dev > ( cd /home/jail/dev ; rm $devices_i_dont_want_in_my_jails ) > mount -u -o nonewdev /home/jail/dev Couldn't you also do "mount -t devfs -o nonewdev devfs /home/jail/dev" and then cd /home/jail/dev ; rm $devices_i_dont_want_in_my_jails ? It seems that "read my lips: no new devices" should be an option you can set from the very initial mount so that people can't also figure out how to get root, remove a /dev entry and replace it with one of their own. Come to think of it, there should also be a -o staticdev option to disallow *any* changes after the initial mount. That would make some of our more paranoid sysadmins happy. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 3 2:37: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 6464B37B401 for ; Sat, 3 Feb 2001 02:36:51 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f13AajB12373; Sat, 3 Feb 2001 11:36:47 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Jordan Hubbard Cc: Warner Losh , John Indra , freebsd-current@FreeBSD.ORG Subject: Re: DEVFS newbie... In-Reply-To: Your message of "Sat, 03 Feb 2001 01:18:08 PST." <82167.981191888@winston.osd.bsdi.com> Date: Sat, 03 Feb 2001 11:36:45 +0100 Message-ID: <12371.981196605@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <82167.981191888@winston.osd.bsdi.com>, Jordan Hubbard writes: >> Once we have an extensible facility for mount options, you will be >> able to say: >> >> mount -t devfs devfs /home/jail/dev >> ( cd /home/jail/dev ; rm $devices_i_dont_want_in_my_jails ) >> mount -u -o nonewdev /home/jail/dev > >Couldn't you also do "mount -t devfs -o nonewdev devfs /home/jail/dev" >and then cd /home/jail/dev ; rm $devices_i_dont_want_in_my_jails ? It >seems that "read my lips: no new devices" should be an option you can >set from the very initial mount so that people can't also figure out >how to get root, remove a /dev entry and replace it with one of their >own. Come to think of it, there should also be a -o staticdev option >to disallow *any* changes after the initial mount. That would make >some of our more paranoid sysadmins happy. That's called "mount -o ro" :-) I have not finalized the workings of the options, right now we have a 32-bit bitmap of mountoptions and they're all used up, and I don't have the time and bikeshedcarpenter hours to design a new mount option implementation. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 3 4:27:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from hera.drwilco.net (10dyn211.dh.casema.net [212.64.31.211]) by hub.freebsd.org (Postfix) with ESMTP id 7054B37B4EC; Sat, 3 Feb 2001 04:27:12 -0800 (PST) Received: from ceres.drwilco.net (ceres.drwilco.net [10.1.1.19]) by hera.drwilco.net (8.11.1/8.11.1) with ESMTP id f13Cnbb78302; Sat, 3 Feb 2001 13:49:38 +0100 (CET) (envelope-from drwilco@drwilco.net) Message-Id: <4.3.2.7.0.20010203122412.00cd4b30@mail.drwilco.net> X-Sender: drwilco@mail.drwilco.net X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sat, 03 Feb 2001 13:26:27 +0100 To: Julian Elischer From: "Rogier R. Mulhuijzen" Subject: Re: Patch for non-netgraph bridge code worthy of attention forpeople experimenting with bridging setups (including ng_bridge) Cc: freebsd-current@freebsd.org, freebsd-net@freebsd.org In-Reply-To: <3A7BC5C4.75247E49@elischer.org> References: <4.3.2.7.0.20010202205233.00d51c30@mail.drwilco.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 00:48 3-2-01 -0800, Julian Elischer wrote: >"Rogier R. Mulhuijzen" wrote: > > > > I found this while experimenting with both "legacy" bridge and ng_bridge. > > The bridging code doesn't check its activation everywhere so when I started > > using an ng_bridge node I started getting weird errors. > > > > Patch is rather simple, can someone submit this? > >I'm a litle confused when I look at this patch. > >I think this is the wrong fix. > >I see that you are accounting for packets coming in on two interfaces, >but the aim of the netgraph bridging is to make it look as if the >packets are all coming in off one interface. Theoretically the >bridging code should be attached to only one 'upper' part of a driver >and all packets should arrive at higher levels, looking as if they have >all come in through that one interface. The other interfaces in the bridge >will never receive anything because their input has been diverted. To the >system it should look as if the entire bridged network is on that one >interface. > >If this is not the case then we need to fix the bridging code so that >it is true, rather than clutter up higher level code trying to >account for a bug in the lower code. I found out this bug while using ng_bridge with BRIDGE in the kernel but turned off with the sysctl. Like I say in the problem report, this could easily be true if you take 2 NICs and wire them both up to the same switch, each using a different IP. (Something we do at QuakeCon for instance. We run a lot of servers per box, so we spread them out over 3 IPs, each with it's own NIC. Worked very well). Netgraph has nothing to do with this. I'm just warning people who are experimenting with the netgraph bridge because they will probably still have BRIDGE in their kernel. Let's run through this example of 2 NICs. Let's say I have BRIDGE in the kernel. I would not want to enable bridging in this case, because I would get a packet storm because of the loop between the machine and the switch. So I turn it off. But the checks for incoming interface are still switched off in the ethernet code. Checks that ARE executed when compiling without BRIDGE. NIC1 has 10.1.1.2 and NIC2 10.1.1.3. An ARP request is sent for 10.1.1.2, and since it's a broadcast it will arrive on both NIC1 and NIC2. Without the checks for what interface a packet came in on, the kernel will send 2 ARP replies, one saying 10.1.1.3 is on NIC1, the other that 10.1.1.3 is on NIC2. The last ARP reply to be sent will be used by the other machines on the network. Now with switches, they will probably handle broadcast packets the same way each time, so the same NIC on our machine will always get the ARP after the other got it. So the same NIC will always win the battle over an IP, resulting in ALL traffic for the machine, no matter what IP it was sent to, to go over a single NIC. That's a BAD(tm) thing. Now if you compare the code that my patch effects from before and after the patch you will see the following changes: original code: blabla(); #ifndef BRIDGE doCheck(); #endif dumDeDum(); my code blabla(); #ifdef BRIDGE if (do_bridge) { /* signifies whether bridging is switched on or off by the sysctl */ #else { #endif doCheck(); } dumDeDum(); This will make the ethernet code behave EXACTLY the same when bridging is switched off with the sysctl and when BRIDGE is NOT compiled into the kernel. Now, on the netgraph stuff. >So how can an incoming packet look like it is not coming from that single >interface? >1/ ifnet pointer. The function ng_ether_rcv_upper() adjust this, so that's >not the problem. >2/ rcv interface MAC address. This is stripped off before arp gets it >(also in ng_ether_rcv_upper()). >3/ the tha[] or sha[] fields may contain a MAC address for >some other interface. (depending on how the remote mechine fills out >those fields), but our outgoing packets should have the MAC address >of the interface we have selected as out main interface, independent of >which interface it actually goes out of, (unless the hardware >over-writes it). so even that should point to the single interface. > >The other interfaces should (maybe) beb ifconfigged 'UP' but they should >not have IP addresses assigned tp them, as they are being slaved from >the main interface by the ng_bridging code so everything comes and >goes via that one. > >so I'm slightly confused as to what problem this solves. >(I'm not saying there isn't one, just that I con't figure out what it is). >Everything should act as if there is just one interface when netgraph >bridging is turned on. Exactly if there's just one interface when netgraph bridging is on. Why? Why just one interface? Now that my kernel is patched to behave like BRIDGE wasn't compiled in when I switch it off I can include the upper's of multiple interfaces in a single netgraph bridge. If you think about it, this should not even be a problem. Look at this diagram http://www.bsdchicks.com/bridge-examples.gif (my apologies to everyone who can't look at graphical stuff) What is the difference between figures 1 and 2? Except that one uses a switch, and the other uses just a FreeBSD box. The way packets travel is almost identical. Why wouldn't it be a valid setup? You say that interfaces included in the ng_bridge should not have their upper's included as well, except for one. That's all fine for a static setup, but I'm dealing with a setup where I have a box that's a router between 2 networks, but sometimes needs to be a bridge as well. If I don't include the upper for one of the interfaces, outgoing packets on that interface will not pass my netgraph bridge, resulting in returning packets to be sent to all hooks on the bridge. I could of course hook my upper to a hole node, but then I'd have to move it's IP to the other interface. When I nuke the bridge I'd have to move it back. Why do that if including the upper in the bridge does the trick. Right now my FreeBSD box is routing between 3 networks and sometimes even bridging between all 3 and it works perfectly. I don't see any reason why multiple uppers can't be included. But like I said, my patch has nothing to do with netgraph. When net.link.ether.bridge == 0 the kernel should behave like a kernel that doesn't have BRIDGE compiled in it. That's currently not the case and my patch fixes that. DocWilco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 3 5:22:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43]) by hub.freebsd.org (Postfix) with ESMTP id 42A0137B401 for ; Sat, 3 Feb 2001 05:22:11 -0800 (PST) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.11.2/8.11.1) id f13DM5J00403; Sat, 3 Feb 2001 19:22:05 +0600 (NOVT) (envelope-from nnd) Date: Sat, 3 Feb 2001 19:22:05 +0600 (NOVT) Message-Id: <200102031322.f13DM5J00403@wint.itfs.nsk.su> From: nnd@mail.nsk.ru To: current@freebsd.org Subject: Re: DEVFS In-Reply-To: User-Agent: tin/1.5.8-20010108 ("Paradise Regained") (UNIX) (FreeBSD/5.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you wrote: > With devfs "default" in -current, I have a question about permissions. I > know that rc.devfs will set up custom permissions at boot... But what > about a device that detaches? When you re-attach, it goes back to the > default permissions. This is a bit annoying; is there a workaround for it? > Should this be handled by something that does the re-attaching? At least for the USB devices this can be done with the 'usbd' daemon. N.Dudorov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 3 7:11:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (grouter.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 174E937B491 for ; Sat, 3 Feb 2001 07:11:24 -0800 (PST) Received: from grondar.za (root@gratis.grondar.za [196.7.18.133]) by gratis.grondar.za (8.11.1/8.11.1) with ESMTP id f13FBEC24492 for ; Sat, 3 Feb 2001 17:11:17 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200102031511.f13FBEC24492@gratis.grondar.za> To: current@freebsd.org Subject: Kernel hackers, please review. Date: Sat, 03 Feb 2001 17:11:34 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Please review the patch at http://people.freebsd.org/~markm/no_lock_h.diff. the idea is to remove sys/*/include/lock.h. I tested it with the usual i386 stuff, and it is known to break the cy driver because of the COM_(UN)LOCK macros (which is another issue). M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 3 8:39:55 2001 Delivered-To: freebsd-current@freebsd.org Received: from amsmta04-svc.chello.nl (mail-out.chello.nl [213.46.240.7]) by hub.freebsd.org (Postfix) with ESMTP id A2C0B37B401 for ; Sat, 3 Feb 2001 08:39:36 -0800 (PST) Received: from stack.nl ([213.46.110.240]) by amsmta04-svc.chello.nl (InterMail vK.4.02.00.10 201-232-116-110 license 85b07e7cd9378159aa6ecc9a5634d971) with ESMTP id <20010203164115.QCLB21484.amsmta04-svc@stack.nl> for ; Sat, 3 Feb 2001 17:41:15 +0100 Message-ID: <3A7C3413.1178B57A@stack.nl> Date: Sat, 03 Feb 2001 17:38:43 +0100 From: Willem van Engen X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: reading /dev/dsp crashes system Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just installed cvsupped and installed a new world&kernel at 3feb2000. Everything works fine, but reading /dev/dsp (cat /dev/dsp e.g.) gives some thousands of bytes output, but then totally crashes the system; it doesn't even break to the debugger when pressing Ctrl-Alt-Esc. It worked fine on my world&kernel from end december. - Willem cat /dev/sndstat gives: FreeBSD Audio Driver (newpcm) Feb 3 2001 12:56:43 Installed devices: pcm0: at memory 0xfedf8000 irq 9 (4p/2 channels duplex) Dmesg output about sound device: pcm0: port 0xf08c-0xf08f,0xf0c0-0xf0ff mem 0xfedf8000-0xfedfffff irq 9 at device 13.0 on pci0 And the obligatory uname -a output: FreeBSD jeremy.dyn.dhs.org 5.0-CURRENT FreeBSD 5.0-CURRENT #14: Sat Feb 3 12:48:10 CET 2001 wvengen@jeremy.dyn.dhs.org:/usr/src/.CURRENT/src/sys/compile/JEREMY i386 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 3 9: 7:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from syncopation-03.iinet.net.au (syncopation-03.iinet.net.au [203.59.24.49]) by hub.freebsd.org (Postfix) with SMTP id 97C7337B4EC for ; Sat, 3 Feb 2001 09:06:49 -0800 (PST) Received: (qmail 27044 invoked by uid 666); 3 Feb 2001 17:14:41 -0000 Received: from reggae-22-22.nv.iinet.net.au (HELO elischer.org) (203.59.87.22) by mail.m.iinet.net.au with SMTP; 3 Feb 2001 17:14:41 -0000 Message-ID: <3A7C3A89.AC30DFDA@elischer.org> Date: Sat, 03 Feb 2001 09:06:17 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: "Rogier R. Mulhuijzen" Cc: freebsd-current@freebsd.org, freebsd-net@freebsd.org Subject: Re: Patch for non-netgraph bridge code worthy of attentionforpeople experimenting with bridging setups (including ng_bridge) References: <4.3.2.7.0.20010202205233.00d51c30@mail.drwilco.net> <4.3.2.7.0.20010203122412.00cd4b30@mail.drwilco.net> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Rogier R. Mulhuijzen" wrote: > [explanation] ok I understand now... I thought you were saying that the netgraph code was acting differently to how I belive it should act. > > > > > Exactly if there's just one interface when netgraph bridging is on. Why? > Why just one interface? Now that my kernel is patched to behave like BRIDGE > wasn't compiled in when I switch it off I can include the upper's of > multiple interfaces in a single netgraph bridge. sure you can. that isn't a problem. It would be a 'brouter' bridging non IP protocols and routing IP. > > If you think about it, this should not even be a problem. > > Look at this diagram http://www.bsdchicks.com/bridge-examples.gif (my > apologies to everyone who can't look at graphical stuff) ok I understan.. my question is: Do you know the girl on http://www.bsdchicks.com/ and is she single? :-) It should be valid.. and I start to see your point. by adding the checks back in (or compiling without BRIDGE) you can have both interfaces.... > > What is the difference between figures 1 and 2? Except that one uses a > switch, and the other uses just a FreeBSD box. yep > > The way packets travel is almost identical. Why wouldn't it be a valid setup? Another possibility would be to make a change to the netgraph bridge code so that it only delivers a broadcast packet to ONE local 'upper' hook. > > You say that interfaces included in the ng_bridge should not have their > upper's included as well, except for one. I didn't mean that they COULDN'T but only that they didn't NEED it > That's all fine for a static > setup, but I'm dealing with a setup where I have a box that's a router > between 2 networks, but sometimes needs to be a bridge as well. If I don't > include the upper for one of the interfaces, outgoing packets on that > interface will not pass my netgraph bridge, resulting in returning packets > to be sent to all hooks on the bridge. I could of course hook my upper to a > hole node, but then I'd have to move it's IP to the other interface. When I > nuke the bridge I'd have to move it back. Why do that if including the > upper in the bridge does the trick. > > Right now my FreeBSD box is routing between 3 networks and sometimes even > bridging between all 3 and it works perfectly. > Using netgraph or the other bridging? I presume Netgraph. > I don't see any reason why multiple uppers can't be included. neither do I, In fact I recommented it to someone yesterday. > > But like I said, my patch has nothing to do with netgraph. When > net.link.ether.bridge == 0 the kernel should behave like a kernel that > doesn't have BRIDGE compiled in it. That's currently not the case and my > patch fixes that. OK I will commit it. > > DocWilco -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 3 9:21:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from hera.drwilco.net (10dyn211.dh.casema.net [212.64.31.211]) by hub.freebsd.org (Postfix) with ESMTP id DE33737B401; Sat, 3 Feb 2001 09:20:48 -0800 (PST) Received: from ceres.drwilco.nl (ceres.drwilco.net [10.1.1.19]) by hera.drwilco.net (8.11.1/8.11.1) with ESMTP id f13HhDb23397; Sat, 3 Feb 2001 18:43:15 +0100 (CET) (envelope-from drwilco@drwilco.nl) Message-Id: <4.3.2.7.0.20010203180653.00afda70@mail.bsdchicks.com> X-Sender: lists@mail.bsdchicks.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sat, 03 Feb 2001 18:15:06 +0100 To: Julian Elischer From: "Rogier R. Mulhuijzen" Subject: Re: Patch for non-netgraph bridge code worthy of attentionforpeople experimenting with bridging setups (including ng_bridge) Cc: freebsd-net@FreeBSD.ORG, freebsd-current@FreeBSD.ORG In-Reply-To: <3A7C3A89.AC30DFDA@elischer.org> References: <4.3.2.7.0.20010202205233.00d51c30@mail.drwilco.net> <4.3.2.7.0.20010203122412.00cd4b30@mail.drwilco.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >ok I understand now... >I thought you were saying that the netgraph code was acting differently >to how I belive it should act. Nope that was the legacy bridge. > > Exactly if there's just one interface when netgraph bridging is on. Why? > > Why just one interface? Now that my kernel is patched to behave like BRIDGE > > wasn't compiled in when I switch it off I can include the upper's of > > multiple interfaces in a single netgraph bridge. > >sure you can. >that isn't a problem. >It would be a 'brouter' bridging non IP protocols and routing IP. > > > > > If you think about it, this should not even be a problem. > > > > Look at this diagram http://www.bsdchicks.com/bridge-examples.gif (my > > apologies to everyone who can't look at graphical stuff) > >ok I understan.. my question is: >Do you know the girl on http://www.bsdchicks.com/ >and is she single? :-) Hahahaha, I don't have a clue who she is, and I'd love to know too =) >It should be valid.. and I start to see your point. > >by adding the checks back in (or compiling without BRIDGE) >you can have both interfaces.... Exactly > > What is the difference between figures 1 and 2? Except that one uses a > > switch, and the other uses just a FreeBSD box. > >yep > > > > > The way packets travel is almost identical. Why wouldn't it be a valid > setup? > >Another possibility would be to make a change to the netgraph bridge code >so that it only delivers a broadcast packet to ONE local 'upper' hook. I wouldn't do that. You'd be adding behaviour that people wouldn't expect, and make it a messy unlogical thing. If people want it delivered on one upper hook, they should include just that one hook. Why make "user friendly" logic that makes it complicated and bothersome for people who want to do more than just the standard things. > > You say that interfaces included in the ng_bridge should not have their > > upper's included as well, except for one. > >I didn't mean that they COULDN'T but only that they didn't NEED it Eek. Misunderstood, my apologies. > > Right now my FreeBSD box is routing between 3 networks and sometimes even > > bridging between all 3 and it works perfectly. > > > >Using netgraph or the other bridging? I presume Netgraph. You are correct. Because I also have my uplink to the internet and I don't want packets "leaking" out to there. My provider might want to start wondering what all these subnets are etc. 2 of the three networks are even on the other side of tunnels built with vtun to Linux and other FreeBSD boxes. Those other networks are also linked to more. Among other things we can now play IPX games over the internet without any hassle =) > > But like I said, my patch has nothing to do with netgraph. When > > net.link.ether.bridge == 0 the kernel should behave like a kernel that > > doesn't have BRIDGE compiled in it. That's currently not the case and my > > patch fixes that. > >OK I will commit it. Thanks. DocWilco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 3 9:31:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 4340F37B4EC for ; Sat, 3 Feb 2001 09:31:39 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f13HTL960996; Sat, 3 Feb 2001 10:29:21 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200102031729.f13HTL960996@harmony.village.org> To: Jordan Hubbard Subject: Re: DEVFS newbie... Cc: Poul-Henning Kamp , John Indra , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sat, 03 Feb 2001 01:18:08 PST." <82167.981191888@winston.osd.bsdi.com> References: <82167.981191888@winston.osd.bsdi.com> Date: Sat, 03 Feb 2001 10:29:21 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <82167.981191888@winston.osd.bsdi.com> Jordan Hubbard writes: : Couldn't you also do "mount -t devfs -o nonewdev devfs /home/jail/dev" : and then cd /home/jail/dev ; rm $devices_i_dont_want_in_my_jails ? It : seems that "read my lips: no new devices" should be an option you can : set from the very initial mount so that people can't also figure out : how to get root, remove a /dev entry and replace it with one of their : own. Come to think of it, there should also be a -o staticdev option : to disallow *any* changes after the initial mount. That would make : some of our more paranoid sysadmins happy. My concern is that I usually know what devices I want (/dev/null, /dev/zero, /dev/tty). That makes it harder to delete all of them not on the list. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 3 9:37:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 6701F37B503 for ; Sat, 3 Feb 2001 09:36:52 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f13HamB14459; Sat, 3 Feb 2001 18:36:48 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Warner Losh Cc: Jordan Hubbard , John Indra , freebsd-current@FreeBSD.ORG Subject: Re: DEVFS newbie... In-Reply-To: Your message of "Sat, 03 Feb 2001 10:29:21 MST." <200102031729.f13HTL960996@harmony.village.org> Date: Sat, 03 Feb 2001 18:36:48 +0100 Message-ID: <14457.981221808@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200102031729.f13HTL960996@harmony.village.org>, Warner Losh writes: >In message <82167.981191888@winston.osd.bsdi.com> Jordan Hubbard writes: >: Couldn't you also do "mount -t devfs -o nonewdev devfs /home/jail/dev" >: and then cd /home/jail/dev ; rm $devices_i_dont_want_in_my_jails ? It >: seems that "read my lips: no new devices" should be an option you can >: set from the very initial mount so that people can't also figure out >: how to get root, remove a /dev entry and replace it with one of their >: own. Come to think of it, there should also be a -o staticdev option >: to disallow *any* changes after the initial mount. That would make >: some of our more paranoid sysadmins happy. > >My concern is that I usually know what devices I want (/dev/null, >/dev/zero, /dev/tty). That makes it harder to delete all of them not >on the list. I have seriously been thinking about some way to say something like mount -t devfs -o jailset /home/jail/dev but an elegant implementation evades me at this moment. And again, it hinges on an extensible set of mount options. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 3 9:49:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id B761737B503 for ; Sat, 3 Feb 2001 09:49:16 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f13HmuW44694; Sat, 3 Feb 2001 09:48:56 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200102031748.f13HmuW44694@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Poul-Henning Kamp Cc: Warner Losh , Jordan Hubbard , John Indra , freebsd-current@FreeBSD.ORG Subject: Re: DEVFS newbie... In-Reply-To: <14457.981221808@critter> Date: Sat, 03 Feb 2001 09:48:56 -0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > In message <200102031729.f13HTL960996@harmony.village.org>, Warner Losh write s: > >In message <82167.981191888@winston.osd.bsdi.com> Jordan Hubbard writes: > >: Couldn't you also do "mount -t devfs -o nonewdev devfs /home/jail/dev" > >: and then cd /home/jail/dev ; rm $devices_i_dont_want_in_my_jails ? It > >: seems that "read my lips: no new devices" should be an option you can > >: set from the very initial mount so that people can't also figure out > >: how to get root, remove a /dev entry and replace it with one of their > >: own. Come to think of it, there should also be a -o staticdev option > >: to disallow *any* changes after the initial mount. That would make > >: some of our more paranoid sysadmins happy. > > > >My concern is that I usually know what devices I want (/dev/null, > >/dev/zero, /dev/tty). That makes it harder to delete all of them not > >on the list. > > I have seriously been thinking about some way to say something like > mount -t devfs -o jailset /home/jail/dev > but an elegant implementation evades me at this moment. As bizzare as it sounds, I like Julian's hack for populating this stuff... ie: use a hard link to propagate nodes to the jailed /dev. eg: mount -t devfs -o empty /home/jail/dev ln /dev/null /home/jail/dev/null ln /dev/zero /home/jail/dev/zero ... mount -u -o ro /home/jail/dev It solves several problems, but is kinda odd as it involves a cross-filesystem hard link. This is another way oround the "oops, I didn't mean to rm /dev/null" - ie: mount -t devfs /mnt ln /mnt/null /dev umount /mnt The VOP_LINK() stuff has access to the source and destination, so it doesn't have to guess what do do on incomplete information (eg: fake major number). On the other hand... Suppose whiteouts were implemented... mount -t devfs -o empty /home/jail/dev cd /home/jail/dev rm -W null zero log .... mount -u -o ro /home/jail/dev ie: start with the initial state as "whiteouts on everything" and then selectively remove the whiteout for things you actually want... Then freeze it by flipping on the readonly bit. > And again, it hinges on an extensible set of mount options. Yeah. Maybe pass in arbitary strins "empty" instead of trying to convert everything to a flag bit? I've been bothered about this for a while. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 3 9:54:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 7AD2237B4EC for ; Sat, 3 Feb 2001 09:54:24 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f13Hs5B14531; Sat, 3 Feb 2001 18:54:05 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Peter Wemm Cc: Warner Losh , Jordan Hubbard , John Indra , freebsd-current@FreeBSD.ORG Subject: Re: DEVFS newbie... In-Reply-To: Your message of "Sat, 03 Feb 2001 09:48:56 PST." <200102031748.f13HmuW44694@mobile.wemm.org> Date: Sat, 03 Feb 2001 18:54:05 +0100 Message-ID: <14529.981222845@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I have seriously been thinking about some way to say something like >> mount -t devfs -o jailset /home/jail/dev >> but an elegant implementation evades me at this moment. > >As bizzare as it sounds, I like Julian's hack for populating this stuff... >ie: use a hard link to propagate nodes to the jailed /dev. > >eg: mount -t devfs -o empty /home/jail/dev >ln /dev/null /home/jail/dev/null >ln /dev/zero /home/jail/dev/zero >... >mount -u -o ro /home/jail/dev > >It solves several problems, but is kinda odd as it involves a >cross-filesystem hard link. unwhiteout(2) has more promise I think. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 3 11:33:29 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 1373037B4EC for ; Sat, 3 Feb 2001 11:33:06 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f13JWo961621; Sat, 3 Feb 2001 12:32:52 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200102031932.f13JWo961621@harmony.village.org> To: Peter Wemm Subject: Re: DEVFS newbie... Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sat, 03 Feb 2001 09:48:56 PST." <200102031748.f13HmuW44694@mobile.wemm.org> References: <200102031748.f13HmuW44694@mobile.wemm.org> Date: Sat, 03 Feb 2001 12:32:50 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200102031748.f13HmuW44694@mobile.wemm.org> Peter Wemm writes: : As bizzare as it sounds, I like Julian's hack for populating this stuff... : ie: use a hard link to propagate nodes to the jailed /dev. : : eg: mount -t devfs -o empty /home/jail/dev : ln /dev/null /home/jail/dev/null : ln /dev/zero /home/jail/dev/zero : ... : mount -u -o ro /home/jail/dev But you can't do hard links accross file systems. Or is that a hack of devfs to allow it, and if so does that create any other security problems. Recall the security implications of having procfs's 'file' file. He made a hard link to the file in question, and exposed many different classes of problem: unwanted disclosure, failure to take into account directory permissions, the ability to hard link to the file and execute it later (bad for setuid programs), etc. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 3 11:35:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id CEF3B37B491 for ; Sat, 3 Feb 2001 11:35:17 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f13JZHB14762; Sat, 3 Feb 2001 20:35:17 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Warner Losh Cc: Peter Wemm , freebsd-current@FreeBSD.ORG Subject: Re: DEVFS newbie... In-Reply-To: Your message of "Sat, 03 Feb 2001 12:32:50 MST." <200102031932.f13JWo961621@harmony.village.org> Date: Sat, 03 Feb 2001 20:35:17 +0100 Message-ID: <14760.981228917@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200102031932.f13JWo961621@harmony.village.org>, Warner Losh writes: >In message <200102031748.f13HmuW44694@mobile.wemm.org> Peter Wemm writes: >: As bizzare as it sounds, I like Julian's hack for populating this stuff... >: ie: use a hard link to propagate nodes to the jailed /dev. >: >: eg: mount -t devfs -o empty /home/jail/dev >: ln /dev/null /home/jail/dev/null >: ln /dev/zero /home/jail/dev/zero >: ... >: mount -u -o ro /home/jail/dev > >But you can't do hard links accross file systems. Or is that a hack >of devfs to allow it, [...] Yes, it was a hack, and it will not be hacked that way in my DEVFS. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 3 11:49:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id BC3A737B4EC for ; Sat, 3 Feb 2001 11:49:13 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f13JnMB14845 for ; Sat, 3 Feb 2001 20:49:22 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: API cleanup patch. From: Poul-Henning Kamp Date: Sat, 03 Feb 2001 20:49:21 +0100 Message-ID: <14843.981229761@critter> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have created a patch which goes a long way to clean up the the usage of the API. The patch is generated automatically and the objectfiles are identical if line numbers are preserved by breaking style(9). You can find the script and the patch here: http://phk.freebsd.dk/patch Please email your comments to me before 07-02-2001 where I plan to commit the patch. I've included the list of files affected below. Poul-Henning Index: alpha/tc/esp.c Index: cam/cam_periph.c Index: cam/cam_xpt.c Index: cam/scsi/scsi_cd.c Index: cam/scsi/scsi_da.c Index: cam/scsi/scsi_low.c Index: cam/scsi/scsi_low_pisa.c Index: cam/scsi/scsi_pt.c Index: coda/coda_subr.c Index: dev/aic7xxx/aicasm/aicasm.c Index: dev/aic7xxx/aicasm/aicasm_symbol.c Index: dev/asr/asr.c Index: dev/ed/if_ed.c Index: dev/eisa/eisaconf.c Index: dev/ex/if_ex.c Index: dev/fe/if_fe.c Index: dev/ie/if_ie.c Index: dev/pdq/pdq_ifsubr.c Index: dev/sn/if_sn.c Index: dev/usb/uhci.c Index: dev/xe/if_xe.c Index: fs/hpfs/hpfs_hash.c Index: gnu/ext2fs/ext2_vfsops.c Index: i386/isa/if_le.c Index: i386/isa/if_wl.c Index: i386/isa/bs/bs.c Index: i386/isa/bs/bs_pisa.c Index: i386/isa/bs/bsfunc.c Index: i4b/driver/i4b_ispppsubr.c Index: kern/kern_linker.c Index: kern/kern_module.c Index: kern/kern_sysctl.c Index: kern/vfs_subr.c Index: miscfs/fdesc/fdesc_vnops.c Index: miscfs/nullfs/null_subr.c Index: miscfs/procfs/procfs_vnops.c Index: miscfs/umapfs/umap_subr.c Index: miscfs/union/union_vfsops.c Index: msdosfs/msdosfs_vfsops.c Index: net/bridge.c Index: net/if.c Index: net/if_ef.c Index: net/if_fddisubr.c Index: net/if_vlan.c Index: net/pfil.c Index: net/rtsock.c Index: netatalk/aarp.c Index: netinet/fil.c Index: netinet/if_ether.c Index: netinet/in.c Index: netinet/in_pcb.c Index: netinet/ip_divert.c Index: netinet/ip_dummynet.c Index: netinet/ip_encap.c Index: netinet/ip_fw.c Index: netinet/ip_icmp.c Index: netinet/ip_input.c Index: netinet/ip_output.c Index: netinet/raw_ip.c Index: netinet/tcp_subr.c Index: netinet/udp_usrreq.c Index: netipx/ipx_input.c Index: netipx/ipx_ip.c Index: netipx/ipx_usrreq.c Index: netnatm/natm_pcb.c Index: netncp/ncp_conn.c Index: netncp/ncp_subr.c Index: ntfs/ntfs_ihash.c Index: ntfs/ntfs_subr.c Index: nwfs/nwfs_node.c Index: nwfs/nwfs_vfsops.c Index: pci/if_de.c Index: pci/if_sf.c Index: pci/if_sk.c Index: pci/if_ti.c Index: pci/if_tl.c Index: pci/if_wx.c Index: ufs/ffs/ffs_softdep.c Index: ufs/ffs/ffs_vfsops.c Index: ufs/ufs/ufs_extattr.c Index: ufs/ufs/ufs_ihash.c Index: ufs/ufs/ufs_quota.c Index: vm/vm_meter.c Index: vm/vm_object.c Index: vm/vm_pageout.c Index: vm/vm_pager.c -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 3 11:50:59 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id BC41837B401 for ; Sat, 3 Feb 2001 11:50:40 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f13Jm1961781; Sat, 3 Feb 2001 12:48:01 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200102031948.f13Jm1961781@harmony.village.org> To: Poul-Henning Kamp Subject: Re: DEVFS newbie... Cc: Peter Wemm , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sat, 03 Feb 2001 20:35:17 +0100." <14760.981228917@critter> References: <14760.981228917@critter> Date: Sat, 03 Feb 2001 12:48:00 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <14760.981228917@critter> Poul-Henning Kamp writes: : In message <200102031932.f13JWo961621@harmony.village.org>, Warner Losh writes: : >In message <200102031748.f13HmuW44694@mobile.wemm.org> Peter Wemm writes: : >: As bizzare as it sounds, I like Julian's hack for populating this stuff... : >: ie: use a hard link to propagate nodes to the jailed /dev. : >: : >: eg: mount -t devfs -o empty /home/jail/dev : >: ln /dev/null /home/jail/dev/null : >: ln /dev/zero /home/jail/dev/zero : >: ... : >: mount -u -o ro /home/jail/dev : > : >But you can't do hard links accross file systems. Or is that a hack : >of devfs to allow it, [...] : : Yes, it was a hack, and it will not be hacked that way in my DEVFS. I seem to recall talking to you about having symbolic links in your devfs mean something "special" as a way around this problem. As you know, but others might not, the device name space is flat an unique (well, except for maybe /dev/fd, which is just unique and can be viewed as flat for the purposes of this discussion). As such, ln -s /dev/null /jail/dev/null could also be expressed as ln -s null /jail/dev/null. The symlink means not "follow this filesystem name space link" but instead "lookup this device name in your device namespace table." But I'm not sure that would work (being only dimly aware of the details of vfs layers and all). Nor am I sure about all the security implications of it (I'm not seeing any at the moment, since you could mount it empty, do the symlinks then remount it r/o). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 3 12: 4: 0 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 4E2A937B401 for ; Sat, 3 Feb 2001 12:03:42 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f13K3gB14920; Sat, 3 Feb 2001 21:03:42 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Warner Losh Cc: Peter Wemm , freebsd-current@FreeBSD.ORG Subject: Re: DEVFS newbie... In-Reply-To: Your message of "Sat, 03 Feb 2001 12:48:00 MST." <200102031948.f13Jm1961781@harmony.village.org> Date: Sat, 03 Feb 2001 21:03:42 +0100 Message-ID: <14918.981230622@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200102031948.f13Jm1961781@harmony.village.org>, Warner Losh writes: >In message <14760.981228917@critter> Poul-Henning Kamp writes: >: In message <200102031932.f13JWo961621@harmony.village.org>, Warner Losh writes: >: >In message <200102031748.f13HmuW44694@mobile.wemm.org> Peter Wemm writes: >: >: As bizzare as it sounds, I like Julian's hack for populating this stuff... >: >: ie: use a hard link to propagate nodes to the jailed /dev. >: >: >: >: eg: mount -t devfs -o empty /home/jail/dev >: >: ln /dev/null /home/jail/dev/null >: >: ln /dev/zero /home/jail/dev/zero >: >: ... >: >: mount -u -o ro /home/jail/dev >: > >: >But you can't do hard links accross file systems. Or is that a hack >: >of devfs to allow it, [...] >: >: Yes, it was a hack, and it will not be hacked that way in my DEVFS. > >I seem to recall talking to you about having symbolic links in your >devfs mean something "special" as a way around this problem. No that was another, and probably too avant garde idea Julian and I have discussed: Basically device-drivers create devices in a private namespace, in /dev you link from the filesystem namespace to the private namespace with a kind of symbolic link. It has too many "issues" with standards and VOP's to be viable right now. Doing straight symlinks would not work. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 3 12:20:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail2.iadfw.net (smtp.pdq.net [206.66.12.234]) by hub.freebsd.org (Postfix) with SMTP id 615E337B503; Sat, 3 Feb 2001 12:20:34 -0800 (PST) Received: from jason from [64.31.207.237] by mail2.iadfw.net (/\##/\ Smail3.1.30.16 #30.47) with smtp for sender: id ; Sat, 3 Feb 2001 14:20:38 -0600 (CST) Message-ID: <006001c08e1e$be6188c0$edcf1f40@pdq.net> From: "Jason Smethers" To: , "Poul-Henning Kamp" References: <14843.981229761@critter> Subject: Re: API cleanup patch. Date: Sat, 3 Feb 2001 14:20:24 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: "Poul-Henning Kamp" > I have created a patch which goes a long way to clean up the the > usage of the API. The patch is generated automatically > and the objectfiles are identical if line numbers are preserved by > breaking style(9). > > You can find the script and the patch here: > > http://phk.freebsd.dk/patch > Index: netinet/fil.c This is part of ipfilter. Ipfilter #ifdef's usage of depending on the OS and OS revision. If we are going to make queue changes to it, we may as well also rip out the #ifdef's around queue usage based on other OS's and OS revisions. - Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 3 12:23:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id C371D37B4EC for ; Sat, 3 Feb 2001 12:23:36 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f13KLQ962051; Sat, 3 Feb 2001 13:21:26 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200102032021.f13KLQ962051@harmony.village.org> To: Poul-Henning Kamp Subject: Re: DEVFS newbie... Cc: Peter Wemm , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sat, 03 Feb 2001 21:03:42 +0100." <14918.981230622@critter> References: <14918.981230622@critter> Date: Sat, 03 Feb 2001 13:21:26 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <14918.981230622@critter> Poul-Henning Kamp writes: : Doing straight symlinks would not work. OK. The other idea that I had was a cpdev. It would be like a templated mknod. It would stat the first argument and do a mknod with the st_rdev from the stat, eg: #include #include #include #include #include int main(char *argv[], int argc) { struct stat sbuf; if (argc != 3) errx(1, "usage: cpdev src dst"); if (stat(argv[1], &sbuf)) err(1, "stat"); if (!S_ISCHR(sbuf.st_mode)) errx(1, "source must be a character device"); if (mknod(argv[2], sbuf.st_mode, sbuf.st_rdev)) err(1, "mknod"); exit(0); } This would mean we could export whatever we wanted from the kernel and something like this would preserve it. It would mean allowing mknodo n non-readonly devfs mounts. If there was a cheap way to determine if the rdev was legitimate, it would be the best way to go. However, that's the rub with this solution: we need to keep a table of devices (like major numbers today and export them as major numbers) or we need to know with certainty that a pointer is good, which traditionally has had its share of security problems. Well, I suppose that the major number thing could be a special case of returning a hash as well, but that still requires a kernel table of some flavor. Notice I don't bother with major/minor numbers at all, but just use the raw rdev (which I hope is the right dev to use, since I think st_dev is the device the filesystem is mounted on) so it doesn't matter what we export as long as we can swallow what we export. Of course this does assume that all devfs instances export the same cookies for the same device. Warner P.S. I do hope someone will tell me if this is becoming too bikeshedish. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 3 12:27:35 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 7E2D537B4EC for ; Sat, 3 Feb 2001 12:27:16 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f13KR9962347; Sat, 3 Feb 2001 13:27:11 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200102032027.f13KR9962347@harmony.village.org> To: nnd@mail.nsk.ru Subject: Re: DEVFS Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sat, 03 Feb 2001 19:22:05 +0600." <200102031322.f13DM5J00403@wint.itfs.nsk.su> References: <200102031322.f13DM5J00403@wint.itfs.nsk.su> Date: Sat, 03 Feb 2001 13:27:09 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200102031322.f13DM5J00403@wint.itfs.nsk.su> nnd@mail.nsk.ru writes: : At least for the USB devices this can be done with the : 'usbd' daemon. And pccardd can handle this for OLDCARD users. NEWCARD users will need to cope until something comes alone :-(. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 3 12:28:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 046F037B4EC for ; Sat, 3 Feb 2001 12:28:32 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f13KSWB15141; Sat, 3 Feb 2001 21:28:32 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Warner Losh Cc: Peter Wemm , freebsd-current@FreeBSD.ORG Subject: Re: DEVFS newbie... In-Reply-To: Your message of "Sat, 03 Feb 2001 13:21:26 MST." <200102032021.f13KLQ962051@harmony.village.org> Date: Sat, 03 Feb 2001 21:28:32 +0100 Message-ID: <15139.981232112@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200102032021.f13KLQ962051@harmony.village.org>, Warner Losh writes: >In message <14918.981230622@critter> Poul-Henning Kamp writes: >: Doing straight symlinks would not work. > >OK. > >The other idea that I had was a cpdev. It would be like a templated >mknod. It would stat the first argument and do a mknod with the >st_rdev from the stat, eg: It's really very simple, if I get my way, this will be possible: # rm /dev/null # echo 'OOPS!' # rm -W /dev/null # ls -l /dev/null crw-rw-rw- 1 root wheel 2, 2 3 Feb 21:25 /dev/null # mount -t devfs devfs /home/jail/dev # cd /home/jail/dev # rm -f * # rm -W null zero tty console # ls -l crw------- 1 phk wheel 0, 0 2 Feb 01:09 console drwxr-xr-x 2 root wheel 0 2 Feb 01:06 fd crw-rw-rw- 1 root wheel 2, 2 3 Feb 21:25 null crw-rw-rw- 1 root wheel 1, 0 3 Feb 17:27 tty crw-rw-rw- 1 root wheel 2, 12 1 Jan 1970 zero # >P.S. I do hope someone will tell me if this is becoming too >bikeshedish. It is :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 3 12:32:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 7D10B37B491; Sat, 3 Feb 2001 12:08:13 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA30139; Sat, 3 Feb 2001 12:08:15 -0800 Date: Sat, 3 Feb 2001 12:08:12 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: API cleanup patch. In-Reply-To: <14843.981229761@critter> 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 not the 'audit' list which is what audit is for I thought? Other than if_wx which breaks cstyling, looks okay to me To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 3 14:24:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.net022.co.yu (mail.net022.co.yu [212.200.44.4]) by hub.freebsd.org (Postfix) with ESMTP id 73AFD37B491 for ; Sat, 3 Feb 2001 14:24:06 -0800 (PST) Received: from phy.bg.ac.yu (dial-in26.net022.co.yu [212.200.44.35]) by mail.net022.co.yu (8.8.7/8.8.7) with ESMTP id AAA04083 for ; Sun, 4 Feb 2001 00:24:32 +0100 Message-ID: <3A7C7F4D.3A7BF5EB@phy.bg.ac.yu> Date: Sat, 03 Feb 2001 22:59:41 +0100 From: Rasa Karapandza X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: ACPI S1 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone see acpi S1 mode realy work? Rasa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 3 14:39:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from ntlg.sibnet.ru (dns.sibnet.ru [217.70.96.34]) by hub.freebsd.org (Postfix) with ESMTP id CA5C137B401; Sat, 3 Feb 2001 14:39:23 -0800 (PST) Received: from tlg2-ppp5.sibnet.ru (tlg2-ppp5.sibnet.ru [217.70.97.116]) by ntlg.sibnet.ru (8.9.3+Sun/8.9.3) with ESMTP id BAA00646; Sun, 4 Feb 2001 01:39:21 +0300 (MSK) Date: Sun, 4 Feb 2001 04:44:30 +0600 (GMT+6) From: "Semen A. Ustimenko" X-Sender: semenu@default To: freebsd-current@FreeBSD.org Cc: freebsd-hackers@FreeBSD.org, Michael Smith Subject: PCI bus code & SMC9432 behaviour 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 got into a following problem with subj: During boot process, the card can be in power down mode. This can be cause MEMEN and PORTEN bits not set up correctly (set to 0) during boot. This bits not set will cause no resources for this device, thus later a bus_alloc_resource() call will fail. I succeed to with adding resources manualy by calling bus_set_resource(), but it seems to me a wrong idea. I supposed the pci code analyze that driver sets/clears PORTEN or MEMEN bit, and thus add/remove appropriate resources... This wont be difficult. If you say this is a good idea, i can provide a patch myself, though i haven't thouched the pci code before. Good luck! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 3 14:50:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from moby.geekhouse.net (moby.geekhouse.net [64.81.6.36]) by hub.freebsd.org (Postfix) with ESMTP id 9910837B65D for ; Sat, 3 Feb 2001 14:50:25 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp151.geekhouse.net [192.168.1.151]) by moby.geekhouse.net (8.11.0/8.9.3) with ESMTP id f13Moic20369; Sat, 3 Feb 2001 14:50:44 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3A7C7F4D.3A7BF5EB@phy.bg.ac.yu> Date: Sat, 03 Feb 2001 14:49:53 -0800 (PST) From: John Baldwin To: Rasa Karapandza Subject: RE: ACPI S1 Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-Feb-01 Rasa Karapandza wrote: > Has anyone see acpi S1 mode realy work? Sort of. It works on my laptop if I'm in X with my wavelan plugged in. At a console with no devices plugged in it will immediately resume after suspend. > Rasa -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/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 Sat Feb 3 15:24:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from updraft.jp.freebsd.org (updraft.jp.FreeBSD.ORG [210.157.158.42]) by hub.freebsd.org (Postfix) with ESMTP id F3F1737B491; Sat, 3 Feb 2001 15:24:26 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by updraft.jp.freebsd.org (8.11.2+3.4W/8.11.1) with ESMTP/inet id f13NONW49406; Sun, 4 Feb 2001 08:24:24 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) Cc: phk@freebsd.org X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.2 XEmacs/21.2 (Poseidon) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 36 From: Makoto MATSUSHITA To: current@freebsd.org Subject: doFS.sh should obey MDDEVICE if available Date: Sun, 04 Feb 2001 08:24:09 +0900 Message-Id: <20010204082409C.matusita@jp.FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG src/release/scripts/doFS.sh rev. 1.6 doesn't consider MDDEVICE variable (formaly, VNDEVICE). Here is a sample fix to use MDDEVICE variable to configure md -- trivial, add '-u' option if MDDEVICE is already defined. -- - Makoto `MAR' MATSUSHITA Index: doFS.sh =================================================================== RCS file: /pub/cvsup/FreeBSD.cvs/src/release/scripts/doFS.sh,v retrieving revision 1.29 diff -c -r1.29 doFS.sh *** doFS.sh 2001/01/31 22:58:39 1.29 --- doFS.sh 2001/02/03 23:16:51 *************** *** 37,43 **** awk 'BEGIN {printf "%c%c", 85, 170}' |\ dd of=${FSIMG} obs=1 seek=510 conv=notrunc 2>/dev/null ! MDDEVICE=`mdconfig -a -t vnode -f ${FSIMG}` if [ ! -c /dev/${MDDEVICE} ] ; then if [ -f /dev/MAKEDEV ] ; then ( cd /dev && sh MAKEDEV ${MDDEVICE} ) --- 37,47 ---- awk 'BEGIN {printf "%c%c", 85, 170}' |\ dd of=${FSIMG} obs=1 seek=510 conv=notrunc 2>/dev/null ! if [ "x${MDDEVICE}" != "x" ] ; then ! mdconfig -a -t vnode -f ${FSIMG} -u ${MDDEVICE} ! else ! MDDEVICE=`mdconfig -a -t vnode -f ${FSIMG}` ! fi if [ ! -c /dev/${MDDEVICE} ] ; then if [ -f /dev/MAKEDEV ] ; then ( cd /dev && sh MAKEDEV ${MDDEVICE} ) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 3 15:45:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from moby.geekhouse.net (moby.geekhouse.net [64.81.6.36]) by hub.freebsd.org (Postfix) with ESMTP id 60FE237B491; Sat, 3 Feb 2001 15:44:54 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp151.geekhouse.net [192.168.1.151]) by moby.geekhouse.net (8.11.0/8.9.3) with ESMTP id f13NjSc20470; Sat, 3 Feb 2001 15:45:28 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010204082409C.matusita@jp.FreeBSD.org> Date: Sat, 03 Feb 2001 15:44:37 -0800 (PST) From: John Baldwin To: Makoto MATSUSHITA Subject: RE: doFS.sh should obey MDDEVICE if available Cc: phk@FreeBSD.org, current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-Feb-01 Makoto MATSUSHITA wrote: > > src/release/scripts/doFS.sh rev. 1.6 doesn't consider MDDEVICE variable > (formaly, VNDEVICE). Here is a sample fix to use MDDEVICE variable to > configure md -- trivial, add '-u' option if MDDEVICE is already defined. But you shouldn't need this. The only reason for the old VNDEVICE was because the release process couldn't automatically find an unused device to use, so it had to have help if vn0 is used. The current method always finds an unused device to use, so the old VNDEVICE-style hack is no longer needed. There's no point to setting an explicit device to use. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/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 Sat Feb 3 16:53: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from iip-lab.ics.es.osaka-u.ac.jp (inoueke-n.ics.es.osaka-u.ac.jp [133.1.240.231]) by hub.freebsd.org (Postfix) with ESMTP id C34E037B4EC; Sat, 3 Feb 2001 16:52:51 -0800 (PST) Received: from localhost (kir.ics.es.osaka-u.ac.jp [133.1.12.129]) by iip-lab.ics.es.osaka-u.ac.jp (8.11.1/3.7W/INO-1.0v9-IIP-LAB) with ESMTP id f140qn448149; Sun, 4 Feb 2001 09:52:49 +0900 (JST) Cc: phk@FreeBSD.ORG, current@FreeBSD.ORG X-Newsgroups: freebsd.current Distribution: freebsd In-Reply-To: References: <20010204082409C.matusita@jp.FreeBSD.org> X-User-Agent: Mew/1.94.2 XEmacs/21.2 (Poseidon) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Organization: Dept. of Information & Computer Sciences, Osaka Univ., JAPAN X-Dispatcher: imput version 20000228(IM140) Lines: 24 From: Makoto MATSUSHITA To: jhb@FreeBSD.ORG Subject: RE: doFS.sh should obey MDDEVICE if available Date: 04 Feb 2001 09:52:41 +0900 Message-Id: <20010204095241U.matusita@ics.es.osaka-u.ac.jp> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG jhb> The current method always finds an unused device to use, so the jhb> old VNDEVICE-style hack is no longer needed. There's no point to jhb> setting an explicit device to use. But I want to ensure that all used md(4) devices is unconfigured after it is used. Imagine you run 'make release' for your own release. If something is trouble in doFS.sh ('kernel size exceeds 1.44MB floppy size' is a typical example), make will exit without umounting /mnt and unconfigureing /dev/mdX, where X is dynamically allocated (and no way to know what X is outside of doFS.sh). If I can say 'doFS.sh, your md device number is X', it's obviously easy to umount /mnt and unconfigure md devices after the script runs. My mother tolds me that I should put away my toys after I play with them, so I want to do a sure way to unconfigure md device. BTW, how many md devices can we configure at the same time? What's happen if a file of md's backing store is removed? -- - Makoto MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 3 17: 5: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from moby.geekhouse.net (moby.geekhouse.net [64.81.6.36]) by hub.freebsd.org (Postfix) with ESMTP id A6CA337B503; Sat, 3 Feb 2001 17:04:46 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp151.geekhouse.net [192.168.1.151]) by moby.geekhouse.net (8.11.0/8.9.3) with ESMTP id f1415Mc20602; Sat, 3 Feb 2001 17:05:23 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010204095241U.matusita@ics.es.osaka-u.ac.jp> Date: Sat, 03 Feb 2001 17:04:29 -0800 (PST) From: John Baldwin To: Makoto MATSUSHITA Subject: RE: doFS.sh should obey MDDEVICE if available Cc: current@FreeBSD.org, phk@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 04-Feb-01 Makoto MATSUSHITA wrote: > > jhb> The current method always finds an unused device to use, so the > jhb> old VNDEVICE-style hack is no longer needed. There's no point to > jhb> setting an explicit device to use. > > But I want to ensure that all used md(4) devices is unconfigured after > it is used. > > Imagine you run 'make release' for your own release. If something is > trouble in doFS.sh ('kernel size exceeds 1.44MB floppy size' is a > typical example), make will exit without umounting /mnt and > unconfigureing /dev/mdX, where X is dynamically allocated (and no way > to know what X is outside of doFS.sh). If I can say 'doFS.sh, your md > device number is X', it's obviously easy to umount /mnt and > unconfigure md devices after the script runs. If it is still mounted, you can see the device by just typing 'mount' to get a list of mounted filesystems. You will have something like: /dev/md0 on /mnt (ufs, local) Also, I think that this isn't the right fix to a bigger problem. Instead, it shouldn't be hard to get a list of configured devices out of mdconfig via an ioctl on /dev/mdctl. This would be the right fix, as it would fix the general case problem you describe, not just one instance of it. mdconfig wont' be able to tell you what file it is attached to by filename, but it should be able to ask /dev/mdctl for a list of devices and report at least the type of each device (swap, file, etc.). -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/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 Sat Feb 3 17:30:17 2001 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id A0F7137B4EC for ; Sat, 3 Feb 2001 17:29:59 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 4 Feb 2001 01:29:58 +0000 (GMT) Date: Sun, 4 Feb 2001 01:29:57 +0000 From: David Malone To: Warner Losh Cc: Peter Wemm , freebsd-current@FreeBSD.ORG Subject: Re: DEVFS newbie... Message-ID: <20010204012957.A96268@walton.maths.tcd.ie> References: <200102031748.f13HmuW44694@mobile.wemm.org> <200102031932.f13JWo961621@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200102031932.f13JWo961621@harmony.village.org>; from imp@harmony.village.org on Sat, Feb 03, 2001 at 12:32:50PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Feb 03, 2001 at 12:32:50PM -0700, Warner Losh wrote: > In message <200102031748.f13HmuW44694@mobile.wemm.org> Peter Wemm writes: > : As bizzare as it sounds, I like Julian's hack for populating this stuff... > : ie: use a hard link to propagate nodes to the jailed /dev. > : > : eg: mount -t devfs -o empty /home/jail/dev > : ln /dev/null /home/jail/dev/null > : ln /dev/zero /home/jail/dev/zero > : ... > : mount -u -o ro /home/jail/dev > > But you can't do hard links accross file systems. Actually, you've always been able to do things like this. For example: ln /proc/curproc/file /test on a 3.X machine will produce a hard link to ln in / - it doesn't work any more 'cos /proc/curproc/file is now a soft link. I presume the same thing works with fdescfs. This is actually one nice feature Linux procfs has: I once was asked to look at a Linux box someone had broken into. They'd deleted all the files in /var/log, but hadn't HUPed syslogd - so I just hard linked them all back into place again. Not an every day use, but... David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 3 18: 5:20 2001 Delivered-To: freebsd-current@freebsd.org Received: from updraft.jp.freebsd.org (updraft.jp.FreeBSD.ORG [210.157.158.42]) by hub.freebsd.org (Postfix) with ESMTP id 86FB437B503; Sat, 3 Feb 2001 18:04:58 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by updraft.jp.freebsd.org (8.11.2+3.4W/8.11.1) with ESMTP/inet id f1424sW60485; Sun, 4 Feb 2001 11:04:55 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) Cc: current@FreeBSD.org, phk@FreeBSD.org In-Reply-To: References: <20010204095241U.matusita@ics.es.osaka-u.ac.jp> X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.2 XEmacs/21.2 (Poseidon) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 32 From: Makoto MATSUSHITA To: jhb@FreeBSD.org Subject: RE: doFS.sh should obey MDDEVICE if available Date: Sun, 04 Feb 2001 11:04:31 +0900 Message-Id: <20010204110431M.matusita@jp.FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oops, sorry that From: address was different from the first email... jhb> Instead, it shouldn't be hard to get a list of configured devices jhb> out of mdconfig via an ioctl on /dev/mdctl. This would be the jhb> right fix, as it would fix the general case problem you describe, jhb> not just one instance of it. Agreed. We can also detect 'umounted, but configured md devices' with the output of mount(8) and a list mentioned above. jhb> mdconfig wont' be able to tell you what file it is attached to by jhb> filename, but it should be able to ask /dev/mdctl for a list of jhb> devices and report at least the type of each device (swap, file, jhb> etc.). It maybe a stupid question (sorry I have few knowledge about kernel internal)... Can't we add a space for filename in the structure of md device? It would be wonderful if 'mdconfig -l' says: unit mounted type option 0 /tmp malloc -s=65535,reserve 1 none file /home/matusita/fdimage 2 none swap none or something like that. If we have a configulation file for mdconfig(8), this output will be the same of its file format. -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 3 19: 6:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id A51F437B491 for ; Sat, 3 Feb 2001 19:05:54 -0800 (PST) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.11.2/8.11.2) id f14381q07982 for freebsd-current@freebsd.org; Sat, 3 Feb 2001 19:08:01 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <200102040308.f14381q07982@troutmask.apl.washington.edu> Subject: kernel trap 26 panic To: FreeBSD Current Date: Sat, 3 Feb 2001 19:08:01 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG lpt gives an instant panic with sources from this afternoon (3 Feb 01 pst). So far, I can boot the system if I disable lpd in /etc/rc.conf. If I start lpd from the command, I get %lpd stray irq 7 stray irq 7 stray irq 7 stray irq 7 kernel trap 26 with interrupts disabled panic: mutex sched lock recursed at /usr/src/sys/kern/kern_synch.c:918 kargl[202] uname -a FreeBSD C456086-A.bllvu1.wa.home.com 5.0-CURRENT FreeBSD 5.0-CURRENT\ #3: Sat Feb 3 13:59:49 GMT 2001 kargl@C456086-A.bllvu1.wa.home.com\ :/usr/obj/usr/src/sys/C456086-A i386 I have a crash dump. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 3 19:20:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id 268BE37B4EC; Sat, 3 Feb 2001 19:20:27 -0800 (PST) Received: by bazooka.unixfreak.org (Postfix, from userid 1000) id E43153E02; Sat, 3 Feb 2001 19:20:26 -0800 (PST) Received: from unixfreak.org (localhost [127.0.0.1]) by bazooka.unixfreak.org (Postfix) with ESMTP id E2C903C10B; Sat, 3 Feb 2001 19:20:26 -0800 (PST) To: John Baldwin Cc: Makoto MATSUSHITA , current@FreeBSD.org, phk@FreeBSD.org Subject: Re: doFS.sh should obey MDDEVICE if available In-Reply-To: Message from John Baldwin of "Sat, 03 Feb 2001 17:04:29 PST." Date: Sat, 03 Feb 2001 19:20:21 -0800 From: Dima Dorfman Message-Id: <20010204032026.E43153E02@bazooka.unixfreak.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Also, I think that this isn't the right fix to a bigger problem. > Instead, it shouldn't be hard to get a list of configured devices > out of mdconfig via an ioctl on /dev/mdctl. This would be the right > fix, as it would fix the general case problem you describe, not just > one instance of it. mdconfig wont' be able to tell you what file it > is attached to by filename, but it should be able to ask /dev/mdctl > for a list of devices and report at least the type of each device > (swap, file, etc.). I think I can do this, possibly with a little help. md(4) keeps a list of md_s structures. From these, I think you can fill in the majority (if not all) of the fields in an md_ioctl structure. I tried this, and I can successfully return one almost-filled md_ioctl structure. If someone can suggest a method for returning an arbitrary number of md_ioctl's (a list), I think I may be able to implement this. Any pointers? Thanks Dima Dorfman dima@unixfreak.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 3 21:19: 7 2001 Delivered-To: freebsd-current@freebsd.org Received: from sydney.worldwide.lemis.com (unknown [192.109.197.194]) by hub.freebsd.org (Postfix) with ESMTP id E173737B491; Sat, 3 Feb 2001 21:18:44 -0800 (PST) Received: (from grog@localhost) by sydney.worldwide.lemis.com (8.11.1/8.9.3) id f141Rfe27754; Sun, 4 Feb 2001 12:27:41 +1100 (EST) (envelope-from grog) Date: Sun, 4 Feb 2001 11:57:41 +1030 From: Greg Lehey To: Peter Wemm Cc: Robert Watson , freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Watch your devfs permissions in driver make_dev calls Message-ID: <20010204115741.G27504@sydney.worldwide.lemis.com> References: <200102030410.f134AAW35066@mobile.wemm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200102030410.f134AAW35066@mobile.wemm.org>; from peter@netplex.com.au on Fri, Feb 02, 2001 at 08:10:10PM -0800 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 2 February 2001 at 20:10:10 -0800, Peter Wemm wrote: > Robert Watson wrote: > >> crw-r--r-- 1 root wheel 78, 0 Dec 31 1969 pci > > This one may appear harmless, but it is not. It is trivially easy to create > an alignment fault (fatal on an alpha) with the userland pciconf tool. > We must not allow this to be used by users until the kernel part is fixed. > > Eg: try this on an alpha: pciconf -r -l pci0:x:x 0x3 - ie: read a longword > at byte offset 3 in configuration space.. kaboom! This looks like a separate issue. Presumably you can do this as root as well. pciconf should check the parameters. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 3 22:55: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from moby.geekhouse.net (moby.geekhouse.net [64.81.6.36]) by hub.freebsd.org (Postfix) with ESMTP id AC41137B401 for ; Sat, 3 Feb 2001 22:54:43 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp151.geekhouse.net [192.168.1.151]) by moby.geekhouse.net (8.11.0/8.9.3) with ESMTP id f146tQc21149; Sat, 3 Feb 2001 22:55:26 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200102040308.f14381q07982@troutmask.apl.washington.edu> Date: Sat, 03 Feb 2001 22:54:33 -0800 (PST) From: John Baldwin To: Steve Kargl Subject: RE: kernel trap 26 panic Cc: FreeBSD Current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 04-Feb-01 Steve Kargl wrote: > lpt gives an instant panic with sources from this > afternoon (3 Feb 01 pst). So far, I can boot the > system if I disable lpd in /etc/rc.conf. If I start > lpd from the command, I get > > %lpd > stray irq 7 > stray irq 7 > stray irq 7 > stray irq 7 > kernel trap 26 with interrupts disabled > panic: mutex sched lock recursed at /usr/src/sys/kern/kern_synch.c:918 > > kargl[202] uname -a > FreeBSD C456086-A.bllvu1.wa.home.com 5.0-CURRENT FreeBSD 5.0-CURRENT\ >#3: Sat Feb 3 13:59:49 GMT 2001 kargl@C456086-A.bllvu1.wa.home.com\ >:/usr/obj/usr/src/sys/C456086-A i386 > > I have a crash dump. The ppbus does painful things with its interrupt handlers. This is a known problem and on the todo list, just not fixed yet. > -- > Steve > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/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