[no subject]
Best regards, Maxim SamohinEnd user supportReemtsma KyrgyzstanPhone + 996 312 630006 (int. 504)e-mail: [EMAIL PROTECTED] The information in this Internet E-Mail is confidential and may be legally privileged. It is intended solely for the addressee. Access to this Internet E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful.
Re: Why did FreeBSD fail?
[ Redirected to -chat from -hackers; I'm not on -chat, keep me Cc'd. ] On Tue, 20 Aug 2002, Rik van Riel wrote: > On Tue, 20 Aug 2002, Mosko Bilekic wrote: > > > Gentlemen, it's time to explain why FreeBSD is such a > > failure. > > Maybe it's because the developers prefer to spend their > time and energy on gossip instead of technical issues ? > > No wait, those aren't the developers, can't be. Please > tell me those aren't really the developers... Those most certainly aren't the developers. I will go so far to say with great confidence that the people trolling the list have never written a decently impressive piece of code in their lives. The Internet was once a place where hackers could go about their business without being troubled by such lameness. Unfortunately, the rest of society has jumped onto the Internet and brought their baggage with them. Occasionally one of these non-hackers finds their way into a technical forum and is disappointed when they're made to feel excluded or inferior. They come to the Internet with the misguided notion that they are somehow entitled to some sort of respect or status -- either because they consider themselves of some import in the real world or because they feel that the Internet is their opportunity to grab the piece of the popularity pie that has been denied to them thusfar in life. Most of them experience a rude awakening when the technical forum doesn't even stop to notice them and they become very bitter and vindictive about this perceived "mistreatment". They go so far as to engage in activities such as trolling which drain the community's most valuable resources: it's communication channels and the time of the hackers therein. Behavior of this sort has become the unfortunate and quite obnoxious norm. What this influx of laypeople fail to realize is that the hackers who built and maintain this network built it as a tool for their own ends and have little time to care about the needs of the many. If a non-technical person needs help the prevailing attitude is and should be that that individual can pay for his support. This sense of entitlement to attention, respect or status among non-hackers is a byproduct of a societal emphasis on political correctness and subjectivism. It's annoying. VERY annoying. The engineering community is, has always been, and always should and shall be a meritocracy. There can be no other way. To the trolls I say this: go ahead and feel insulted that nobody paid attention to you. Go ahead and pout. Feel excluded if you must. Nobody excluded you on the basis of who you are. Nobody excluded you because you weren't on the guest list or someone didn't like you. You were excluded for the plain and simple reason that you have yet to demonstrate your worth. You're not entitled to anything. If you want to be part of the club, write some code. We're not elitists, we're practical. Our time is limited. We won't pay attention to you until you bother to demonstrate that you are worth our time. Trolling a mailing list might make you feel good, but nobody cares. Most of us hit delete and kept going without giving it a second thought. If you want people to pay attention to you, write good code or shut the fuck up. Brandon D. Valentine -- http://www.geekpunk.net [EMAIL PROTECTED] ++[>++<-]>[<++>-]<.>[>+<-]>[<+>-]<+.+++..++ +.>>+[<++>-]<++.<<+++.>.+++.--..>+. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Why did FreeBSD fail?
On Tue, 20 Aug 2002, Mosko Bilekic wrote: > Gentlemen, it's time to explain why FreeBSD is such a > failure. Maybe it's because the developers prefer to spend their time and energy on gossip instead of technical issues ? No wait, those aren't the developers, can't be. Please tell me those aren't really the developers... (now, can we end the trolling and talk techical stuff again? maybe I'll even join #bsdcode again ;)) cheers, Rik -- Bravely reimplemented by the knights who say "NIH". http://www.surriel.com/ http://distro.conectiva.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Why did FreeBSD fail?
:Matt Dillon, I had a lot of respect for you until you :replied to the Pythonstein troll, you SUCK This is almost as good as IRC, but I often find myself wishing for a return to the days before Jesus Monroy mellowed out. I mean, I *DO* have a reputation as a hothead to maintain now don't I! But the trolls these days are getting so bad I just can't do it with a straight face any more. I've been Ruined! :Alfred Perlstein, drunktard Careful, Alfred is (H'cup) bigger then you are! And he has Mr. A. Skul on his side. 50 pounds of titanium and lead opens a lot of doors. HiC'p. -Matt Matthew Dillon <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: can anyone help me on this ??
Shane Kinney writes: > Call me crazy, but this is a -FreeBSD- list. Maybe you should try > talking > to the RedHat people? > Because cvsup originated with FreeBSD ? > > On Tue, 20 Aug 2002, Moises Zanabria wrote: > > > Don't know if this is the correct list to ask this, I'm new in CVSUp and > > this is a newbie question, I have my Linux box , RedHat 7.3 > > CVS version 1.11.2 > > CVSup 16_1e > > > > and the following CVSup configuration: > > > > $pwd > > /usr2/CVSUp/cvsup_server/base/sup/test > > > > $ls -la test > > -rw-r--r-- 1 userid dev34 Aug 16 11:52 releases > > -rw-r--r-- 1 userid dev12 Aug 16 11:57 list.cvs > > On my server I have a directory called prefixes which contains symbolic links to the repositories. AFAIK cvsup needs these when it's run as a server. E.g.: garyj:peedub:mail:bash:19> ll /usr/local/etc/cvsup/prefixes/ total 0 lrwx-- 1 root wheel 8B Nov 25 2001 FreeBSD-crypto.cvs -> /u2/ncvs lrwx-- 1 root wheel 8B Nov 25 2001 FreeBSD.cvs -> /u2/ncvs --- Gary Jennejohn / [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Creating a sysctl? (mission impossible)
Hi, This is for -STABLE system as of August 15th. $ uname -a FreeBSD Here.here 4.6-STABLE FreeBSD 4.6-STABLE #8: Tue Aug 20 14:42:43 BRT 2002 [EMAIL PROTECTED]:/usr/src/sys/compile/LIOUX i386 I am trying to create one sysctl so that I can read information from a lottery scheduler that I am trying to write. The sysctl is very very simple. I add a lottery node under kern then add a member global_tickets under kern.lottery. Very simple stuff that is not working. Here follows the sample I am using. I used kern_poll.c as example. 1) Created a file kern_lottery.c which is attached. Then, placed this file under /usr/src/sys/kern/kern_lottery; 2) Then, added a reference for it in both /usr/src/sys/conf/files and /usr/src/sys/conf/options. Check attached patch-lottery; 3) Then, added "options SCHEDULER_LOTTERY" to a kernel config file. Compiled, installed, rebooted. Here follows the results after the reboot: $ nm /kernel | grep -i lotter c0237ee0 d sysctl___kern_lottery c0237f20 d sysctl___kern_lottery_global_tickets c0264238 B sysctl__kern_lottery_children $ sysctl -a | grep -i lot $ sysctl -A | grep -i lot As you can see, sysctl returns nothing even though the relevant symbols are in the kernel. It knows nothing about the lottery node. I can reproduce this "problem" in 2 different boxes with different versions of -STABLE. The relevant sysctl code follows: typedef _BSD_PID_T_ ticket_t; /* ticket type */ static ticket_t global_tickets = 0; /* XXX lottery */ SYSCTL_NODE(_kern, OID_AUTO, lottery, CTLFLAG_RW, 0, "Lottery scheduling parameters"); SYSCTL_UINT(_kern_lottery, OID_AUTO, global_tickets, CTLFLAG_RD, &global_tickets, 0, "Current global tickets") Any ideas why this is not working? Help plz. I hope you guys know what I am doing wrong. IF I add this code to kern_switch.c, everything works but it does not work when I add to kern_lottery.c My 1st thought is that it does not like the fact that I'm trying to create a node inside kern from another file. However, kern_poll.c works like a charm. Regards, ps: please CC: me in your replies since I only receive digests of this list. -- Mario S F Ferreira - DF - Brazil - "I guess this is a signature." Computer Science Undergraduate | FreeBSD Committer | CS Developer flames to beloved [EMAIL PROTECTED] feature, n: a documented bug | bug, n: an undocumented feature --- sys/conf/files.orig Tue Aug 20 14:48:54 2002 +++ sys/conf/files Tue Aug 20 14:37:49 2002 @@ -572,6 +572,8 @@ kern/kern_ktrace.c standard kern/kern_lock.c standard kern/kern_lockf.c standard +# XXX lottery +kern/kern_lottery.coptional scheduler_lottery kern/kern_malloc.c standard kern/kern_mib.cstandard kern/kern_ntptime.cstandard --- sys/conf/options.orig Tue Aug 20 14:49:02 2002 +++ sys/conf/optionsTue Aug 20 14:38:17 2002 @@ -468,3 +468,7 @@ # Polling device handling DEVICE_POLLING opt_global.h + +# XXX lottery +# Lottery scheduler +SCHEDULER_LOTTERY opt_sched_lottery.h /* * Copyright (c) 2001, 2002 * Mario Sergio Fujikawa Ferreira <[EMAIL PROTECTED]> * All rights reserved. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * 1. Redistributions of source code must retain the above copyright *notice, this list of conditions and the following disclaimer. * 2. Redistributions in binary form must reproduce the above copyright *notice, this list of conditions and the following disclaimer in the *documentation and/or other materials provided with the distribution. * * THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE * ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. * * $Fedaykin: src/sys/kern/kern_lottery.c,v 1.1.2.10 2002/08/19 19:37:34 lioux Exp $ */ #ifdef SMP #include "opt_lint.h" #ifndef COMPILING_LINT #error SCHEDULER_LOTTERY is not compatible with SMP yet #endif #endif #include #include #include /* the process structure */ #include #include #include #include typedef _BSD_PID_T_ ticket_t; /* ticket type */ static ticket_t global_tickets = 0; /* XXX l
³nÅé°ê¨ó³nÅé§ó·s 2002.08.20 Time:¤W¤È 01:36:27
Dear, Mr. haw845, ¥»´Á§ó·s¤T¦Ê¾l¤ù http://0933.to/snkcd To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: can anyone help me on this ??
Call me crazy, but this is a -FreeBSD- list. Maybe you should try talking to the RedHat people? On Tue, 20 Aug 2002, Moises Zanabria wrote: > Don't know if this is the correct list to ask this, I'm new in CVSUp and > this is a newbie question, I have my Linux box , RedHat 7.3 > CVS version 1.11.2 > CVSup 16_1e > > and the following CVSup configuration: > > $pwd > /usr2/CVSUp/cvsup_server/base/sup/test > > $ls -la test > -rw-r--r-- 1 userid dev34 Aug 16 11:52 releases > -rw-r--r-- 1 userid dev12 Aug 16 11:57 list.cvs > > $more releases > cvs list=list.cvs prefix=/tmp/cvs_test/src > > $ more list.cvs > upgrade bin > > $pwd > /usr2/CVSUp/cvsup_server/base/sup/test > > when I run the server "/usr/local/sbin/cvsupd -b test" I got: > 2002.08.20 08:48:06 CDT [26821]: CVSup server started > 2002.08.20 08:48:06 CDT [26821]: Software version: SNAP_16_1e > 2002.08.20 08:48:06 CDT [26821]: Protocol version: 17.0 > 2002.08.20 08:48:06 CDT [26821]: Ready to service requests > > > Same machine: > $pwd > > /usr2/CVSUp/client > > ls -lrt > -rw-r--r-- 1 userid dev97 Aug 19 10:30 supfile > > $more supfile > *default host=localhost > *default base=. > *default release=cvs > *default delete use-rel-suffix > test > > > $ cvsup supfile > Connected to localhost > Server message: Unknown collection "test" > Skipping collection test/cvs > Finished successfully > > > > In the Server. > > $ /usr/local/sbin/cvsupd -b test > 2002.08.20 08:48:06 CDT [26821]: CVSup server started > 2002.08.20 08:48:06 CDT [26821]: Software version: SNAP_16_1e > 2002.08.20 08:48:06 CDT [26821]: Protocol version: 17.0 > 2002.08.20 08:48:06 CDT [26821]: Ready to service requests > 2002.08.20 08:50:16 CDT [26821]: +0 [EMAIL PROTECTED] > (mydomain) [SNAP_16_1e/17.0] > 2002.08.20 08:50:16 CDT [26821]: =0 Unknown collection "test" > 2002.08.20 08:50:16 CDT [26821]: -0 [0Kin+0Kout] Finished successfully > 2002.08.20 08:50:16 CDT [26821]: Going down > > my repository have: > > $ls -lrt /tmp/cvs_test/src > drwxrwxr-x 2 userid dev 1024 Aug 16 11:49 CVSROOT > drwxr-xr-x 2 userid dev 1024 Aug 19 01:14 bin > > Directory that I want to mirror: > ls -lrt /tmp/cvs_test/src/bin > total 204 > -rw-r--r-- 1 useriddev 48551 Aug 16 11:42 BUILDNOTES,v > -rw-r--r-- 1 useriddev 741 Aug 16 11:42 cossdk.bat,v > -rw-r--r-- 1 useriddev104159 Aug 16 11:42 makefile,v > -rw-r--r-- 1 useriddev 2109 Aug 16 11:42 create_dist.bat,v > -rw-r--r-- 1 useriddev 2091 Aug 16 11:42 makefile.bridge,v > -rw-r--r-- 1 useriddev 1515 Aug 16 11:42 makefile.dscore,v > -rw-r--r-- 1 useriddev 1572 Aug 16 11:42 makefile.ds,v > -rw-r--r-- 1 useriddev 4835 Aug 16 11:42 makefile.kmp,v > -rw-r--r-- 1 useriddev 3192 Aug 16 11:42 makefile.project,v > -rw-r--r-- 1 useriddev 6358 Aug 16 11:42 makefile.migration,v > -rw-r--r-- 1 useriddev 5069 Aug 16 11:42 > makefile.regression,v > -rw-r--r-- 1 useriddev 18960 Aug 16 11:42 p4agent.dsw,v > > any Ideas what's wrong. > Thanks for you help. > Moises. > > > > > > _ > Chat with friends online, try MSN Messenger: http://messenger.msn.com > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
can anyone help me on this ??
Don't know if this is the correct list to ask this, I'm new in CVSUp and this is a newbie question, I have my Linux box , RedHat 7.3 CVS version 1.11.2 CVSup 16_1e and the following CVSup configuration: $pwd /usr2/CVSUp/cvsup_server/base/sup/test $ls -la test -rw-r--r-- 1 userid dev34 Aug 16 11:52 releases -rw-r--r-- 1 userid dev12 Aug 16 11:57 list.cvs $more releases cvs list=list.cvs prefix=/tmp/cvs_test/src $ more list.cvs upgrade bin $pwd /usr2/CVSUp/cvsup_server/base/sup/test when I run the server "/usr/local/sbin/cvsupd -b test" I got: 2002.08.20 08:48:06 CDT [26821]: CVSup server started 2002.08.20 08:48:06 CDT [26821]: Software version: SNAP_16_1e 2002.08.20 08:48:06 CDT [26821]: Protocol version: 17.0 2002.08.20 08:48:06 CDT [26821]: Ready to service requests Same machine: $pwd /usr2/CVSUp/client ls -lrt -rw-r--r-- 1 userid dev97 Aug 19 10:30 supfile $more supfile *default host=localhost *default base=. *default release=cvs *default delete use-rel-suffix test $ cvsup supfile Connected to localhost Server message: Unknown collection "test" Skipping collection test/cvs Finished successfully In the Server. $ /usr/local/sbin/cvsupd -b test 2002.08.20 08:48:06 CDT [26821]: CVSup server started 2002.08.20 08:48:06 CDT [26821]: Software version: SNAP_16_1e 2002.08.20 08:48:06 CDT [26821]: Protocol version: 17.0 2002.08.20 08:48:06 CDT [26821]: Ready to service requests 2002.08.20 08:50:16 CDT [26821]: +0 [EMAIL PROTECTED] (mydomain) [SNAP_16_1e/17.0] 2002.08.20 08:50:16 CDT [26821]: =0 Unknown collection "test" 2002.08.20 08:50:16 CDT [26821]: -0 [0Kin+0Kout] Finished successfully 2002.08.20 08:50:16 CDT [26821]: Going down my repository have: $ls -lrt /tmp/cvs_test/src drwxrwxr-x 2 userid dev 1024 Aug 16 11:49 CVSROOT drwxr-xr-x 2 userid dev 1024 Aug 19 01:14 bin Directory that I want to mirror: ls -lrt /tmp/cvs_test/src/bin total 204 -rw-r--r-- 1 useriddev 48551 Aug 16 11:42 BUILDNOTES,v -rw-r--r-- 1 useriddev 741 Aug 16 11:42 cossdk.bat,v -rw-r--r-- 1 useriddev104159 Aug 16 11:42 makefile,v -rw-r--r-- 1 useriddev 2109 Aug 16 11:42 create_dist.bat,v -rw-r--r-- 1 useriddev 2091 Aug 16 11:42 makefile.bridge,v -rw-r--r-- 1 useriddev 1515 Aug 16 11:42 makefile.dscore,v -rw-r--r-- 1 useriddev 1572 Aug 16 11:42 makefile.ds,v -rw-r--r-- 1 useriddev 4835 Aug 16 11:42 makefile.kmp,v -rw-r--r-- 1 useriddev 3192 Aug 16 11:42 makefile.project,v -rw-r--r-- 1 useriddev 6358 Aug 16 11:42 makefile.migration,v -rw-r--r-- 1 useriddev 5069 Aug 16 11:42 makefile.regression,v -rw-r--r-- 1 useriddev 18960 Aug 16 11:42 p4agent.dsw,v any Ideas what's wrong. Thanks for you help. Moises. _ Chat with friends online, try MSN Messenger: http://messenger.msn.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
GATOS + FreeBSD
Is there any successful attempts with FreeBSD to use video-in on: Matrox G450 eTV (marvel.sourceforge.net) G400-TV ATI Radeon 7500/8500 w video-in (gatos.sf.net) Or any other AGP card with video input? All support seems very linux centric.. /P To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: CAM "wiring", LUNs and duplicate wired entries
On Tue, Aug 20, 2002 at 08:30:29 -0400, Gardner Buchanan wrote: > Hi Ken, > > > -Original Message- > > From: Kenneth D. Merry [mailto:[EMAIL PROTECTED]] > > Sent: August 19, 2002 16:27 > > Subject: Re: CAM "wiring", LUNs and duplicate wired entries > > > > > > Try the attached patch and see if it fixes things for you. > > > > Thanks for this patch. I've built a new kernel with this in place and all > seems well; no Duplicate message and everything seems to be in the order I > expected. Thanks for the feedback, I'll get it committed. Ken -- Kenneth Merry [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
binary incompatible libc ???
Hi,
seems like libc version on 4.6 branch are binary incompatible. Doing a
simple malloc fails, when compiled on a newer version. Linking with
-static makes it work. Programs compiled on older version, work on the
newer one:
ralf@monster:~$ cat t.c
#include
#include
int main()
{
if (!malloc(100)) {
perror("malloc failed");
}
return 0;
}
ralf@monster:~$ gcc -v; uname -a
Using builtin specs.
gcc version 2.95.4 20020320 [FreeBSD]
FreeBSD monster.brainbot.com 4.6-STABLE FreeBSD 4.6-STABLE #19: Sun Aug 18 22:29:07
CEST 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MONSTER i386
ralf@monster:~$ gcc t.c
ralf@monster:~$ ./a.out
ralf@monster:~$ ssh nibbler
ralf@nibbler:~$ ./a.out
malloc failed: Cannot allocate memory
ralf@nibbler:~$ gcc -v; uname -a
Using builtin specs.
gcc version 2.95.3 20010315 (release) [FreeBSD]
FreeBSD nibbler.brainbot.com 4.6-STABLE FreeBSD 4.6-STABLE #1: Mon Jun 17 23:07:53
CEST 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386
ralf@nibbler:~$
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: CAM "wiring", LUNs and duplicate wired entries
On Tue, Aug 20, 2002 at 00:05:33 -0700, Peter Wemm wrote:
> "Kenneth D. Merry" wrote:
> > On Mon, Aug 19, 2002 at 13:52:33 -0700, Terry Lambert wrote:
> > > "Kenneth D. Merry" wrote:
> > > > I don't think that's the problem. I think the problem is that the device
> > > > at target 8 is getting identified to camperiphnextunit() as a wired devic
> e,
> > > > when it isn't.
> > > >
> > > > Try the attached patch and see if it fixes things for you.
> > > >
> > > > I haven't tried compiling or running this, so beware.
> > >
> > >
> > > That's some sneaky code. 8-). If this works and you commit it,
> > > can you add an expository comment?
> >
> > Maybe. Peter Wemm wrote the hardwiring code, and would likely be in a
> > slightly better position to explain it.
>
> Actually, Justin implemented the original design, I just changed the
> underlying mechanism that it uses. It still uses Justin's algorithms but
> looks in different places for the source data. I sort-of understand it,
> but it has been a while since I looked at it. :-)
>
> Regarding the patch, yes, it does look like the 'hit = 0' should go inside
> the loop. I would have done it more explicitly though, eg:
>
> +++ cam_periph.c2002/08/20 06:48:50
> @@ -332,3 +332,2 @@
> unit = 0;
> - hit = 0;
>
> @@ -338,2 +337,3 @@
> while ((i = resource_locate(i, periph_name)) != -1) {
> + hit = 0;
> dname = resource_query_name(i);
>
> The same problem is on -current too. It is probably worth changing "hit"
> to "wired" since that is what it means.
>
> I think this bug came from an earlier verson of the changes where this was
> a multi-layered loop, and the resetting of 'hit' got moved too far out when
> it collapsed to a single loop.
Justin had the above fix in his local tree, but after discussing it we
figured out that it wouldn't work in all cases.
The reason is, if you hit a partial match at the end of the resource list,
hit will still be set to something non-zero, since you won't be going back
through the loop again to reset hit.
Thus the reason for the for() loop -- it resets hit after each loop
iteration. So hit is always 0 when camperiphnextunit() is invoked, unless
you break out of the loop due to a match.
Ken
--
Kenneth Merry
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
RE: CAM "wiring", LUNs and duplicate wired entries
Hi Ken, > -Original Message- > From: Kenneth D. Merry [mailto:[EMAIL PROTECTED]] > Sent: August 19, 2002 16:27 > Subject: Re: CAM "wiring", LUNs and duplicate wired entries > > > Try the attached patch and see if it fixes things for you. > Thanks for this patch. I've built a new kernel with this in place and all seems well; no Duplicate message and everything seems to be in the order I expected. See you, Gardner Buchanan Adobe Systems Canada +1 613 751 4800 x5635 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Why did FreeBSD fail?
Original Message: - From: Mosko Bilekic [EMAIL PROTECTED] Date: Tue, 20 Aug 2002 12:39:08 +0100 (BST) To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Why did FreeBSD fail? Gentlemen, it's time to explain why FreeBSD is such a failure. In the following lines, David O'Brien explains why 5.0 is such a POS... <@motminh> -current is a fucking piece of shit right now. <@Keltia> hi motminh < gordont> motminh: no, it's just shitty for you, I just updated fine <@motminh> gordont: try using mucho scsi disks + IPFW <@motminh> gordont: isp(4) is shit. <@motminh> gordont: Oh, and on an SMP box <@motminh> gordont: we haven't been stable since June 27th (just before ipfw2 hit). * motminh *just* got a ffs block not freed panic with an hour old kernel. < gordont> motminh: hmm, well I can't attest for isp or ipfw, but my smp box works fine <@motminh> gordont: if I use an isp controller I can't even make it to single user <@motminh> gordont: you have a single ide disk in it? <@motminh> gordont: please do. <@motminh> gordont: we have noone (few) stress testing -current right now. <@motminh> for many the test is a basic PC and "make world". < gordont> motminh: I have to get FC down to my EMC box first though <@motminh> I hear more and more developers that only have a -current shitbox to make sure something compiles that was developed on -stable before they commit it to -current. < gordont> motminh: well, I'm proud to say my desktop at work is running -CURRENT <@motminh> Keltia: awake? <@Keltia> motminh: yes <@motminh> Keltia: are you running -current on your SMP box? <@Keltia> motminh: I'm afraid not <@motminh> Keltia: have you even seen the "launching CPU #1" message get fucked up in the middle of SCSI probe output? <@Keltia> motminh: I think I have seen it yes <@motminh> anordby: you have to `make depend' first. <@motminh> anordby: 1/2 ass commits broke building kernels <@anordby> motminh: hrrm ok <@anordby> motminh: i have a -current testing box that i intend to make rebuild world+kernel every night.. automatically from pxe installs. :) <@Keltia> motminh: still there ? <@motminh> 7ep <@motminh> Keltia: my box hasn't been stable enough <@motminh> Keltia: the /bin/sh bug that fubar'ed |'s kept me from build many ports <@Keltia> motminh: when you'll be able to try gcc33, see my message in -current - As you see, -CURRENT has been totally broken for almost two months now. And don't get me started on -STABLE. FreeBSD 4.x is such a joke... enterprise ready my ass! The other big problem that the FreeBSD project faces is that a lot of developers prefer to waste time flaming instead of coding. Mike Smith knew that, that's why he left. Jordan Hubbard is an asshole btw. As always, some greetings... Juli Mallett, sorry for the typo :) David O'Brien, you're a great hacker, but a real asshole Matt Dillon, I had a lot of respect for you until you replied to the Pythonstein troll, you SUCK Greg Lehey, MORON, don't feed the trolls! Alfred Perlstein, drunktard Hiten Pandya, IMBECILE Bosko Milekic, if I ever meet you, I'll kick your ass! Paul Saab, asshole Bill Fumerola, FUCK YOU Will Andrews, I suggest you join a real project Diane Bruce, the reason I never mentioned you is that you're so fucking ugly I felt sorry for you :) Yours, Mosko __ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message Uggh, folks does it really help us with anything to fall to the level of personal insults? I mean I doubt projects fail because someone thinks someone else is ugly. I might buy "Uh, you look like such a scary science fiction monster no could work with you..." but that's pushing it. It would be nice to hear good reasons why something works or doesn't. Not page after page of personl invective. Have Fun, Sends Steve mail2web - Check your email from the web at http://mail2web.com/ . To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Why did FreeBSD fail?
On Tuesday 20 August 2002 07:39 am, Mosko Bilekic wrote: | Gentlemen, it's time to explain why FreeBSD is such a | failure. | | In the following lines, David O'Brien explains why 5.0 | is such a POS... : | The other big problem that the FreeBSD project faces | is that a lot of developers prefer to waste time | flaming instead of coding. Mike Smith knew that, | that's why he left. Jordan Hubbard is an asshole btw. | | As always, some greetings... | | Juli Mallett, sorry for the typo :) | David O'Brien, you're a great hacker, but a real | asshole | Matt Dillon, I had a lot of respect for you until you | replied to the Pythonstein troll, you SUCK | Greg Lehey, MORON, don't feed the trolls! | Alfred Perlstein, drunktard | Hiten Pandya, IMBECILE | Bosko Milekic, if I ever meet you, I'll kick your ass! | Paul Saab, asshole | Bill Fumerola, FUCK YOU | Will Andrews, I suggest you join a real project | Diane Bruce, the reason I never mentioned you is that | you're so fucking ugly I felt sorry for you :) | | Yours, | Mosko On behalf of everybody even remotely involved with FreeBSD*, I'd like to thank you for this wonderful contribution to raising the level of debate. You have truly set a shining example of the way to move forward productively. If only everybody else could emulate your example then this problem that "a lot of developers prefer to waste time flaming instead of coding" would quickly be solved. -- Brian, the man from Babble-On . . . . [EMAIL PROTECTED] (personal) *And I certainly qualify since I'm *very* remotely involved in FreeBSD. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
4.6.1-rc2 booting
Hi, I donwloaded 4.6.1-rc2.ISO and tried to install it on machine with Solaris 8. Instalation went perfect, except that after booting FreeBSD boot-manager allows only to boot from Solaris x86 partition (1st partition). I can start FreeBSD from /dev/ad0s3a when boot from installation CDROM, but not from hard disk. Even on hand I've started boot0cfg -B -m 0xf -s 3 ad0 and disklabel -w -B /dev/ad0s3 but the effect were the same. Only the default slice moved from 1 to 3 (prompt: Default: F3). Did someone achieve similar problem and had it find some workaround. Here is the output of fdisk on this 10G hard disk. bsd# fdisk /dev/ad0 *** Working on device /dev/ad0 *** parameters extracted from in-core disklabel are: cylinders=1247 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=1247 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 190,(unknown) start 1008, size 21168 (10 Meg), flag 0 beg: cyl 0/ head 16/ sector 1; end: cyl 1/ head 96/ sector 63 The data for partition 2 is: sysid 130,(Linux swap or Solaris x86) start 22496, size 1048 (4882 Meg), flag 0 beg: cyl 1/ head 102/ sector 6; end: cyl 623/ head 222/ sector 63 The data for partition 3 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 10022544, size 10010511 (4887 Meg), flag 80 (active) beg: cyl 623/ head 223/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 4 is: To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Trolls
Guys, Getting a bit sick of this, can someone identify the protagonists and set up the necessary filters on mailhub please? Thanks - I will begin making judicious use of Mutt's spam key in the meantime. BMS To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Why did FreeBSD fail?
Gentlemen, it's time to explain why FreeBSD is such a failure. In the following lines, David O'Brien explains why 5.0 is such a POS... <@motminh> -current is a fucking piece of shit right now. <@Keltia> hi motminh < gordont> motminh: no, it's just shitty for you, I just updated fine <@motminh> gordont: try using mucho scsi disks + IPFW <@motminh> gordont: isp(4) is shit. <@motminh> gordont: Oh, and on an SMP box <@motminh> gordont: we haven't been stable since June 27th (just before ipfw2 hit). * motminh *just* got a ffs block not freed panic with an hour old kernel. < gordont> motminh: hmm, well I can't attest for isp or ipfw, but my smp box works fine <@motminh> gordont: if I use an isp controller I can't even make it to single user <@motminh> gordont: you have a single ide disk in it? <@motminh> gordont: please do. <@motminh> gordont: we have noone (few) stress testing -current right now. <@motminh> for many the test is a basic PC and "make world". < gordont> motminh: I have to get FC down to my EMC box first though <@motminh> I hear more and more developers that only have a -current shitbox to make sure something compiles that was developed on -stable before they commit it to -current. < gordont> motminh: well, I'm proud to say my desktop at work is running -CURRENT <@motminh> Keltia: awake? <@Keltia> motminh: yes <@motminh> Keltia: are you running -current on your SMP box? <@Keltia> motminh: I'm afraid not <@motminh> Keltia: have you even seen the "launching CPU #1" message get fucked up in the middle of SCSI probe output? <@Keltia> motminh: I think I have seen it yes <@motminh> anordby: you have to `make depend' first. <@motminh> anordby: 1/2 ass commits broke building kernels <@anordby> motminh: hrrm ok <@anordby> motminh: i have a -current testing box that i intend to make rebuild world+kernel every night.. automatically from pxe installs. :) <@Keltia> motminh: still there ? <@motminh> 7ep <@motminh> Keltia: my box hasn't been stable enough <@motminh> Keltia: the /bin/sh bug that fubar'ed |'s kept me from build many ports <@Keltia> motminh: when you'll be able to try gcc33, see my message in -current - As you see, -CURRENT has been totally broken for almost two months now. And don't get me started on -STABLE. FreeBSD 4.x is such a joke... enterprise ready my ass! The other big problem that the FreeBSD project faces is that a lot of developers prefer to waste time flaming instead of coding. Mike Smith knew that, that's why he left. Jordan Hubbard is an asshole btw. As always, some greetings... Juli Mallett, sorry for the typo :) David O'Brien, you're a great hacker, but a real asshole Matt Dillon, I had a lot of respect for you until you replied to the Pythonstein troll, you SUCK Greg Lehey, MORON, don't feed the trolls! Alfred Perlstein, drunktard Hiten Pandya, IMBECILE Bosko Milekic, if I ever meet you, I'll kick your ass! Paul Saab, asshole Bill Fumerola, FUCK YOU Will Andrews, I suggest you join a real project Diane Bruce, the reason I never mentioned you is that you're so fucking ugly I felt sorry for you :) Yours, Mosko __ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Problem building -STABLE
Hi hackers, I've cvsupped my 4.6.1-RC2 machine to -STABLE (I suppose it will be 4.6.2-STABLE). When I tryed to make buildworld I've got an error: cc -O -pipe -I. -I/usr/src/usr.bin/colldef -I/usr/src/usr.bin/colldef/../../lib/libc/locale -DCOLLATE_DEBUG -DYY_NO_UNPUT -D__FBSDID=__RCSID -c scan.c In file included from /usr/src/usr.bin/colldef/scan.l:40: /usr/src/usr.bin/colldef/y.tab.h:15: `STR_LEN' undeclared here (not in a function) *** Error code 1 Stop in /usr/src/usr.bin/colldef. *** Error code 1 I look at the code and saw STR_LEN is defined in collate.h which is included in scan.c before y.tab.h . I ran gcc -E scan.c and saw that collate.h isn't included for any reason ?!? What is the problem? Any ideas? Vladimir To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
