Re: Adding a new FS to FreeBSD
In article by Greg Lehey: > That may be easier than you think. I'm copying Warren Toomey on > this. Warren is (a) a FreeBSD user and (b) the person who negotiated > these contracts in the first place. Warren, Peter is thinking of > porting the 2BSD file system (not sure whether that's UFS or the > original UNIX file system) to FreeBSD. As Terry observes, the current > license doesn't allow that. All, I've had a brief look at the UFS implementation in FreeBSD 4.x, 2.11BSD and a few other systems. I would say that there's enough in FreeBSD's /sys/ufs/ufs code that 2.11BSD's UFS code is not required. Perhaps you could read 2.11BSD's code just to cross check things in FreeBSD's UFS implementation. I've attached a GIF to show the relationship between the various systems al the way back to the UFS in 7th Edition (1979). I have also put up the code for comparison at: http://minnie.tuhs.org/UnixTree/ As per the Caldera license, you need to prove that you agree to this license to get access. This is easily done at: http://www.tuhs.org/archive_access.html and you will be e-mailed your username and password. Obviously, the codebase has diverged between FreeBSD and 2.11BSD, but I would say that FreeBSD already has a nearly-working UFS implementation. Also, the structure of UFS is so well documented in various books that, even if FreeBSD's UFS implementation was deficient, it could be rectified with reference to the books. Hope this helps, Warren ufsdiagram.gif Description: ufsdiagram.gif
Re: Caldera and the Ancient UNIX license
In article by Greg Lehey: [about if and how Caldera is enforcing the Ancient UNIX http://www2.caldera.com/offers/ancient.html. Note also that in fact they allow access to the code via license described at http://www2.caldera.com/offers/ancient001/ without you first agreeing to the license...] > That may be easier than you think. I'm copying Warren Toomey on > this. Warren is (a) a FreeBSD user and (b) the person who negotiated > these contracts in the first place. Warren, Peter is thinking of > porting the 2BSD file system (not sure whether that's UFS or the > original UNIX file system) to FreeBSD. As Terry observes, the current > license doesn't allow that. Firstly, call me crazy, but I thought the 2BSD filesystem layout was essentially UFS, i.e i-nodes at the start, and therefore would be pretty much the same as /sys/ufs/ufs in FreeBSD. I'll have to do a compare of the source code and get back to you I concur with Terry that as the license stands, you first have to prove that a person has agreed to the license before you can give them access to the source code. I would really like to get Caldera to at least remove _this_ condition, even if they left the remaining conditions. It would allow me to set up anonymous access to the old UNIX sources. As for commercial use, that's a separate issue. I don't know how easy it would be for us to talk Caldera into allowing that. Which brings me to the question, does anybody know a good contact at Caldera who can point us to the `right person' to negotiate on this. I knew the guy at SCO who dealt with this, but not at Caldera. > Note that Caldera is merely doing due diligence here; I don't think > that they really care too much. > Greg See me comment about URLs at the top about this :) I'll do a code comparison of FreeBSD /sys/ufs/ufs and 2.11BSD ufs while we wait for contact with Caldera. Cheers all, Warren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Found NFS data corruption bug... (was Re: NFS: How to makeFreeBSD fall on its face in one easy step )
:Once it runs aok for a few million operations, try concurrently running: : :#! /bin/sh :while : :do : sync : sleep 1 :done : :In OS X I used that to flush :) out a couple more bugs. : :-- :Conrad Minshall, [EMAIL PROTECTED], 408 974-2749 :Apple Computer, Mac OS X Core Operating Systems Ho! Will do. I'm going to try to speed things up a bit by having the NFS server export an MFS filesystem. -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Does anyone know if the Broadcom BCM5700 has problems with HW csum?
>David Greenman wrote: >> Alfred Perlstein wrote: >> >You're probably incorrect, it doesn't matter if vlan tags are active >> >or not, it's most likely wheather or not the firmware is being asked >> >to handle them at all. >> >>I would think it would get the checksum wrong most of the time if that >> were the case. It seems to only have problems with small packets, but the >> behavior is pretty strange, so who knows. Do you have some specific knowledge >> about Broadcom and brokeness related to VLAN tag support when not using >> VLANs? > >If it's very small payload, it's probably a byte-order-in-buffer >issue (several Eagle manufactured cards had similar problems, and >so did the NE1000, when it came to DMA transfers, back when 16 bit >transfers were new 8^). The packet itself is fine, it's just the checksum that the hardware calculates is wrong. >For VLANs, yes, there are specific problems known with the Broadcom >cards when the firmware support for VLANs is enabled. The first card >known to work with checksum offload enable and VLAN support enabled >(whether it's used or not) is the Tigon III. I don't know if Bill >Paul fixed the firmware for the Tigon II in this case (he has been >known to hack Tigon II firmware), but it could have been fixed by now. > >In any case, disabling it is what ClickArray ended up doing, as well, >for the Tigon II, until the firmware could be fixed. We're talking about the Tigon III (bge driver for Broadcom BCM5700/BCM5701). -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 3Com driver problems
[EMAIL PROTECTED] writes: > In a message dated 12/15/2001 1:07:28 PM Eastern Standard Time, "."@babalo.ru > writes: > > > At 06:41 PM 12/14/2001, you wrote: > > >[EMAIL PROTECTED] writes: > > > > Try to front end your machine with a switch...the 5 cards is most > > > likely your > > > > problem. With each device you increase your bus contention (ie worsen > > the > > > > worst case bus master scenario)...either that or get a 4 port card > that > > is > > > > more efficient than 5 individual cards. > > >I have some opposite expierence. > > >This is my biggest router: > > >0gw~(1)>uname -a > > >FreeBSD gw.pike 4.4-STABLE FreeBSD 4.4-STABLE #0: Wed Sep 19 06:29:38 MSD > > >2001 [EMAIL PROTECTED]:/tmp/babolo/usr/src/sys/gw i386 > > >0gw~(2)>ifconfig -a > > >dc0: flags=8843 mtu 1500 > > >dc1: flags=8802 mtu 1500 > > >dc2: flags=8843 mtu 1500 > > >dc3: flags=8843 mtu 1500 > > >xl0: flags=8843 mtu 1500 > > >xl1: flags=8843 mtu 1500 > > >xl2: flags=8843 mtu 1500 > > >6 used 100 M ethernet interfaces among others. > > >dc0..dc3 is one card. > > >xl0 cards are workaround for the fact that processor > > sty > > > >spent MUCH more time in interrupt state with dc driver > > >than with xl driver with the same load. > > >Yes, I try find xl x 4 card but no success > > Interrupt state and bus contention are 2 different problems...the problem > with referencing the dc driver is that there are lots of different cards with > different results. btw, the if_dc driver is one of the drivers optimized for > the alpha (note the m_devget calls)..and can use a bit of tuning. my > experience with dlink quad cards and xl is that they are similar in > performance if you account for the fact that the quad cards are going through > a pci bridge chip...and the reduction in bus contention versus using 4 cards. Mine 4 port card was bought as D-link... What is "a bit of tuning"? Yes, I played with shared and non-shared interrupts to assign non-shared to most loaded ports > One issue is that you (and alot of others) dont understand the physical I come to FreeBSD after I was a hardware developper. Hardware constraints are the things I understand well. I do not connect all high load interfaces to one router and this example has 3 relatively high load interfaces. > limits of your machine. putting 6 or more 100Mb/s ethernets on one 32bit bus > is simply asking for problems. You are dealing with a bus that BURSTs to a > bit more than a Gb and probably no more sustained throughput capability than > 500Mb/s (with 2 cards you'll get some errors at 400Mb/s and down from there > as you add cards)...so how do you expect to handle worst case DMA > requirements of 600-800Mb/s in half duplex or twice that if you run 100Mb/s > full duplex? Its just not physically possible. I have no problem with this router now. There is a home network, so no one want to pay more if quality is sufficient. The worst interface has about 1:1 loss - it's OK. Average packet rate for last 67 days is 860 pkt/sec only, burst rate is about 5 times more for 2 min intervals. Yes, I have no direct data about real (short) bursts, but total packet loss is sufficiently low. The real restriction is IP rule complexity. -- @BABOLO http://links.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: sha1 program
On 15-Dec-2001 Kris Kennaway wrote: > Or just ln -sf /usr/bin/openssl /usr/bin/sha1 > > OpenSSL already checks the name it's invoked under and behaves > accordingly. Does it grok the options for md5? :) -s would be easy to simulate in a shell script. -p would be much more difficult unless openssl supports it. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Does anyone know if the Broadcom BCM5700 has problems with HW csum?
>David Greenman wrote: >> >In any case, disabling it is what ClickArray ended up doing, as well, >> >for the Tigon II, until the firmware could be fixed. >> >>We're talking about the Tigon III (bge driver for Broadcom BCM5700/BCM5701). > >Crap. Thanks for the info. > >Have you manually calculated the checksum on a bad packet to see >how it's off? Yes. It's typically off by 0x1051, but varies depending on the TCP/IP header contents. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 3Com driver problems
On Sun, Dec 16, 2001 at 03:56:02AM +0300, "."@babolo.ru wrote: >> different results. btw, the if_dc driver is one of the drivers optimized for >> the alpha (note the m_devget calls)..and can use a bit of tuning. my this has been fixed recently in both stable and current. luigi To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: boot0
John Baldwin wrote: > No. It's the offset in memory of the number of hard drives in the BIOS. The > BIOS has a data segment at 0x40, and at 0x40:0x75 (whose physical address is > 0x475) it has a byte which is a count of the number of hard drives installed. Specifically, Hiten, see: Page 4-9, table 4.002 "BIOS Memory Usage Summary" The Programmers PC Sourcebook Thom Hogan Microsoft Press ISBN: 1-55615-321-X Or: Page 505, Table 11-9 "Hard Disk BIOS Data" The Undocumented PC Frank van Gilluwe Addison-Wesley ISBN: 0-201-62277-7 Seriously, you probably do not need to know how this works. If you are interested enough in PC hardware, and just want to know, you could do worse than buying one or both of these books. You might also want to do a web search for "Ralf Brown Interrupt List". -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Does anyone know if the Broadcom BCM5700 has problems with HW csum?
David Greenman wrote: > >In any case, disabling it is what ClickArray ended up doing, as well, > >for the Tigon II, until the firmware could be fixed. > >We're talking about the Tigon III (bge driver for Broadcom BCM5700/BCM5701). Crap. Thanks for the info. Have you manually calculated the checksum on a bad packet to see how it's off? PS: Is it -0 (0x)? Maybe they didn't use RFC 1936; maybe they used RFC 1141, which has a bug (RFC 1624 corrects the one's complement error of RFC 1141). -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Adding a new FS to FreeBSD
On Saturday, 15 December 2001 at 3:18:33 -0800, Terry Lambert wrote: > Greg Lehey wrote: >> Unfortunately, it's still copyrighted. You need an SCO license; want >> to go and get one of them? It doesn't cost anything, but I can't give >> the software to anybody who hasn't agreed to the conditions. > > 8.4(b) says you can't give it to anyone, even if they do have the > license, unless you contact Caldera first, and then maintain (in > perpeturity) a list of the sources made available. This is rather contradicted by the bottom of http://www2.caldera.com/offers/ancient001/: Now that you have agreed to the license you may choose to apply for access to their archive of older UNIX or request a CD of this archive. I'm one of the people who make the archive available, so feel free to contact me :-) > I think we are screwed by section 2.1(d) anyway: > > Commercial use by LICENSEE of SOURCE CODE PRODUCTS or > of any result, enhancement or modification associated > with the use of SOURCE CODE PRODUCTS under this AGREEMENT > is not permitted. > > Basically, I couldn't get an article out of it because I could't > disclose it to anyone but a licensesee, and only a licensee could > use the code, and I couldn't give source to the licensee without > the permission of Caldera, and once they had the code, they could > not use it for anything commercial unless they negotiated a seperate > commercial use license. That may be easier than you think. I'm copying Warren Toomey on this. Warren is (a) a FreeBSD user and (b) the person who negotiated these contracts in the first place. Warren, Peter is thinking of porting the 2BSD file system (not sure whether that's UFS or the original UNIX file system) to FreeBSD. As Terry observes, the current license doesn't allow that. Terry, the other thing you *can* do is access the source code once you have agreed to the conditions. See the reference to http://minnie.cs.adfa.edu.au/cgi-bin/pupsco.cgi at the bottom of the page http://www2.caldera.com/offers/ancient001/. Change this to http://minnie.tuhs.org/cgi-bin/pupsco.cgi and you should be able to access it. Again, Warren is the person to talk to if you have trouble. > Frankly, if you want to provide small disk images (preferrably, very > small, not multimegabyte) as I've described are needed anyway, along > with a description of the what's on the images, along with such > layout information as you feel comfortable providing, I'd pretty > much rather reverse engineer the stuff than get a Caldera license. It's a slow way of doing things. Of course, if this is an old version of UFS, you might find it easy enough to get our current UFS to grok the layout. Note that Caldera is merely doing due diligence here; I don't think that they really care too much. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
wchar.h, ports packages, and FBSD version?
Hi: I've installed the python-2.1.1 package on a 4.3-RELEASE system, and in the process of building zope, discovered that python is configured with: /* Define if the compiler provides a wchar.h header file. */ #define HAVE_WCHAR_H 1 ...Which I gather is a lie for 4.3. I'm assuming that either STABLE or CURRENT *does* have wchar.h. This leads to questions: 1 - Are port packages built on a CURRENT system? 2 - Is it wrong to install packages on anything but a bleedin' edge current system? 3 - If it isn't wrong, then what is the expected way of dealing with problems like the above? Maybe I'm goofy, but it seems like packages should be built for *compatibility* which would mean building them on something older than either STABLE or CURRENT, since they are then automatically compatible with newer systems. - Robert Withrow, R.W. Withrow Associates, Swampscott MA, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: boot0
On 15-Dec-01 Hiten Pandya wrote: > hi, > I found this piece of code in boot0.s, is it possible > if you could explain me a bit about it. > > .set NHRDRV,0x475# Number of hard drives > > The hex value comes out to: 1141. > > Does that mean, that this is the amound of maximum > hard drives a user can have on FreeBSD? No. It's the offset in memory of the number of hard drives in the BIOS. The BIOS has a data segment at 0x40, and at 0x40:0x75 (whose physical address is 0x475) it has a byte which is a count of the number of hard drives installed. -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Q: What's the purpose of "Attic" in CVS?
D J Hawkey Jr wrote: > > Hello All. > > The subject asks it all. Sorry if this is off-topic. I won't answer the other questions because they were already answered. The subject question, though.. The "Attic" is the directory where deleted files are moved. This is necessary, since a soruce code control system can be used to create the current version of the software... or the software from last month, where there used to be a seperate "ftp.c" instead of "a magic Makefile"... or the software as as it existed for the 3.1-RELEASE. For this to work, it has to be able to access instances of files which have been deleted or moved... so it looks in the directory where the files should be, except in the "Attic" subdirectory. You should really read the CVS FAQ... -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Q: What's the purpose of "Attic" in CVS?
Sorry, I mis-wrote: On Dec 15, at 01:12 PM, D J Hawkey Jr wrote: > > One other Q, as long as I'm posting: For those releases that have both a > RELENG_X_Y and a RELENG_X_Y_BP branch, what's the difference? AFAIK, the > first is for bug fixes; what's the second for? ^ should be "security fixes" Already got a reply stating the relationship; thanks Bruce. Dave -- __ __ \__ \D. J. HAWKEY JR. / __/ \/\ [EMAIL PROTECTED]/\/ http://www.visi.com/~hawkeyd/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Q: What's the purpose of "Attic" in CVS?
If memory serves me right, D J Hawkey Jr wrote: > One other Q, as long as I'm posting: For those releases that have both a > RELENG_X_Y and a RELENG_X_Y_BP branch, what's the difference? AFAIK, the > first is for bug fixes; what's the second for? RELENG_X_Y_BP represents the "Branch Point" where the RELENG_X_Y branch was created from the RELENG_X branch. > Well, now one more: What are RELENG_X and RELENG_X_BP as they relate to > RELENG_X_Y and RELENG_X_Y_BP? Similarly...RELENG_X_BP represents the point where the RELENG_X was branched from HEAD. *_BP is a FreeBSD convention...CVS doesn't have a way of expressing "the point where a branch was made", so we have to tag the tree explicitly. For more information, see Murray Stokely's excellent FreeBSD release engineering article: http://www.freebsd.org/internal/releng.html Bruce. msg30160/pgp0.pgp Description: PGP signature
Q: What's the purpose of "Attic" in CVS?
Hello All. The subject asks it all. Sorry if this is off-topic. One other Q, as long as I'm posting: For those releases that have both a RELENG_X_Y and a RELENG_X_Y_BP branch, what's the difference? AFAIK, the first is for bug fixes; what's the second for? Well, now one more: What are RELENG_X and RELENG_X_BP as they relate to RELENG_X_Y and RELENG_X_Y_BP? I'm rifling through CVS to see if the patchfiles I'm offering on the FreeBSD Backports site are applicable to many releases (some are, I've discovered), and I want to make sure I understand the meaning of these CVS branches. Thanks, Dave -- __ __ \__ \D. J. HAWKEY JR. / __/ \/\ [EMAIL PROTECTED]/\/ http://www.visi.com/~hawkeyd/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
re: Sherlock Wemm reports....
Sherlock Wemm writes >FYI, this is another [EMAIL PROTECTED] clone. and your point is? I dont see any of you helping this guy out; you apparently are a lot better at tracking me down than problems with ethernet drivers, which dont ever seem to get addressed unless some company that one of you is working for needs it. Some of you grumble that I dont donate code, but you dont agree that there are problems, so its a bit difficult to contribute something that noone thinks is needed. Im doing bandwidth management on full gigabit streams with FBSD 4.4..and I've come to a full understand of all of the bottlenecks regarding ethernet drivers. Frankly i couldnt give a rats ass if you like me or not or if you perceive that Im making money off of your work or whatever, but if you think that I dont know what im doing then you are either paying attention to the wrong set of issues or you are just plain stupid. DB To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 3Com driver problems
In a message dated 12/15/2001 1:07:28 PM Eastern Standard Time, "."@babalo.ru writes: > At 06:41 PM 12/14/2001, you wrote: > >[EMAIL PROTECTED] writes: > > > Try to front end your machine with a switch...the 5 cards is most > > likely your > > > problem. With each device you increase your bus contention (ie worsen > the > > > worst case bus master scenario)...either that or get a 4 port card that > is > > > more efficient than 5 individual cards. > >I have some opposite expierence. > >This is my biggest router: > >0gw~(1)>uname -a > >FreeBSD gw.pike 4.4-STABLE FreeBSD 4.4-STABLE #0: Wed Sep 19 06:29:38 MSD > >2001 [EMAIL PROTECTED]:/tmp/babolo/usr/src/sys/gw i386 > >0gw~(2)>ifconfig -a > >dc0: flags=8843 mtu 1500 > >dc1: flags=8802 mtu 1500 > >dc2: flags=8843 mtu 1500 > >dc3: flags=8843 mtu 1500 > >xl0: flags=8843 mtu 1500 > >xl1: flags=8843 mtu 1500 > >xl2: flags=8843 mtu 1500 > >6 used 100 M ethernet interfaces among others. > >dc0..dc3 is one card. > >xl0 cards are workaround for the fact that processor > sty > >spent MUCH more time in interrupt state with dc driver > >than with xl driver with the same load. > >Yes, I try find xl x 4 card but no success Interrupt state and bus contention are 2 different problems...the problem with referencing the dc driver is that there are lots of different cards with different results. btw, the if_dc driver is one of the drivers optimized for the alpha (note the m_devget calls)..and can use a bit of tuning. my experience with dlink quad cards and xl is that they are similar in performance if you account for the fact that the quad cards are going through a pci bridge chip...and the reduction in bus contention versus using 4 cards. One issue is that you (and alot of others) dont understand the physical limits of your machine. putting 6 or more 100Mb/s ethernets on one 32bit bus is simply asking for problems. You are dealing with a bus that BURSTs to a bit more than a Gb and probably no more sustained throughput capability than 500Mb/s (with 2 cards you'll get some errors at 400Mb/s and down from there as you add cards)...so how do you expect to handle worst case DMA requirements of 600-800Mb/s in half duplex or twice that if you run 100Mb/s full duplex? Its just not physically possible. DB To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Found NFS data corruption bug... (was Re: NFS: How to makeFreeBSD fall on its face in one easy step )
At 10:08 PM -0800 12/12/01, Matthew Dillon wrote: >Ok, here is the latest patch for -stable. Note that Kirk comitted a >slightly modified version of the softupdates fix to -current already >(the VOP_FSYNC stuff), which I will be MFCing in 3 days. > >This still doesn't fix all the problems the nfstest program that Jordan >posted finds, but it sure runs a hellofalot longer now before reporting >an error. 10,000+ tests now before failing (NFSv2 and NFSv3). Once it runs aok for a few million operations, try concurrently running: #! /bin/sh while : do sync sleep 1 done In OS X I used that to flush :) out a couple more bugs. -- Conrad Minshall, [EMAIL PROTECTED], 408 974-2749 Apple Computer, Mac OS X Core Operating Systems To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: NFS: How to make FreeBSD fall on its face in one easy step
At 8:19 PM -0800 12/12/01, Jordan Hubbard wrote: >> To be clear, what exactly are you doing? >> >> It sounds like you're exporting something from freebsd, mounting it on OSX >> and running this tool on OSX against the filesystem exported from freebsd ? >> >> If so, What mount options? NFSv2 or v3? > >That is correct. As to the NFS options used, I honestly couldn't say >since I'm getting at the filesystem through Netinfo and that's handled >by OS X's automount daemon, that having no relation whatsoever to AMD >and hence no amd.conf file or anything else I can easily look at to >determine how it's being mounted. Maybe Mike knows more about how to >find this out - he's not in management. :) In the absence of mount-options the OS X automount tries v3 first, followed by v2 if v3 appears not supported by the server. -- Conrad Minshall, [EMAIL PROTECTED], 408 974-2749 Apple Computer, Mac OS X Core Operating Systems To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: NFS: How to make FreeBSD fall on its face in one easy step
At 2:56 PM -0800 12/12/01, Jordan Hubbard wrote: >> The only thing I get is a math exception because "closeprob" is zero >> since no -c option was given. >> >> Can you provide some sample parameters please ? > >Hmmm, how strange, now that I look at the code it's obvious that a >divide by zero will occur with a zero closeprob and the docs state the >default to be "infinity", which is obviously not the case. The >strange part is that I ran this on freebsd.apple.com, which is running >4.4-stable, with one parameter (the filename) exactly as I pasted in >the usage instructions before. Perhaps all this time spent living >next to the Macintosh in my office has induced that copy of FreeBSD to >be more "friendly" and mask simple math errors. :-) > >In any case, -c 1 appears to work just fine. That gives a close/open between each "operation". Better is to fix the fsx.c source by inserting an "if" in main()... diff -u -d -b -w -r1.21 fsx.c --- fsx.c 2001/12/11 23:27:20 1.21 +++ fsx.c 2001/12/15 15:31:19 @@ -701,6 +701,7 @@ testcalls++; + if (closeprob) closeopen = (rv >> 3) < (1 << 28) / closeprob; if (debugstart > 0 && testcalls >= debugstart) -- Conrad Minshall, [EMAIL PROTECTED], 408 974-2749 Apple Computer, Mac OS X Core Operating Systems To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Does anyone know if the Broadcom BCM5700 has problems with HW csum?
David Greenman wrote: >>I am playing with a driver for the Broadcom 5700/5701. >> >>It recognizes the 5700 in my 3Com cards OK, but seems to screw up the >>TCP checksum. >> >>Switching off hardware checksum capability fixes it. >> >>Does anyone know the details of which stepping this stuff worked on? >> > > I haven't nailed down the problem that I've seen with them to a specific >chipset, but I can confirm that they incorrectly calculate the checksum on >input packets in some cases. It seems to be related to both packet size and >certain TCP options (or lack of them). I've only seen the problem occur with >very small (0-4 byte payload) packets. > In any case, after discussing this problem with Bill Paul, I disabled >input checksum in the -current driver and intend to merge that to -stable in >a few days. > OK, that makes sense, because I wasn't getting past first base. SYN ACK segments werre being rejected with bad checksum. The driver I modified is actually for the 5701, which works fine with all checksum offloading enabled. I will try to disable just receive TCP checksum and see what happens. -- Richard Sharpe, [EMAIL PROTECTED], LPIC-1 www.samba.org, www.ethereal.com, SAMS Teach Yourself Samba in 24 Hours, Special Edition, Using Samba To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: New feutures...........
On Fri, 14 Dec 2001, Jordan Hubbard wrote:
> {.. snip ..}
> > 2. I hope that in the furture the FreeBSD developers
> > will rewrite the system in C++.
>
> God, I certainly hope NOT.
Jordan, I do agree absolutely and hope your hopes will come true ... :-)
Konrad
Konrad HeuerPersonal Bookmarks:
Gesellschaft für wissenschaftliche
Datenverarbeitung mbH GÖttingen http://www.freebsd.org
Am Faßberg, D-37077 GÖttingen http://www.daemonnews.org
Deutschland (Germany)
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
subscribe
subscribe Jorge Augusto Teles - JFreeBSD Tecnólogo em Processamento de Dados - FATEC - Taquaritinga emails: [EMAIL PROTECTED] [EMAIL PROTECTED] __ Quer ter seu próprio endereço na Internet? Garanta já o seu e ainda ganhe cinco e-mails personalizados. DomíniosBOL - http://dominios.bol.com.br To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: sha1 program
On Sat, Dec 15, 2001 at 06:12:53PM +0100, Alson van der Meulen wrote: > > Why not have one program for all the supported hash algorithms as > > opposed to individual ones for each (md5, sha1) ? > > > > You could use something like: > > > > > hash -a md5 /some/file > > > hash -a sha1 /some/other/file > It's called openssl. > openssl dgst -md5 > openssl dgst -sha1 > ... > > You could write a wrapper for this, or just type the 14 extra characters > ;) Or just ln -sf /usr/bin/openssl /usr/bin/sha1 OpenSSL already checks the name it's invoked under and behaves accordingly. Kris msg30150/pgp0.pgp Description: PGP signature
Re: sha1 program
On Sat, Dec 15, 2001 at 11:58:14AM +, Dominic Marks wrote: > On Saturday 15 December 2001 11:34 am, Mike Wiacek wrote: > > We currently have a MD5 driver, but no SHA1 driver, even though > > we have SHA1 as part of libmd. So I took md5.c from > > /usr/src/sbin/md5 and made sha1.c as well as a respective man page. > > Attached is the source file, the manual page for it, as well as a > > makefile. > > > > Hope this is useful and makes its way into the tree. Md5 has some > > questionable attacks against it, and Schneier claims that > > sha is resillient to such attacks. > > > > mike > > Why not have one program for all the supported hash algorithms as > opposed to individual ones for each (md5, sha1) ? > > You could use something like: > > > hash -a md5 /some/file > > hash -a sha1 /some/other/file It's called openssl. openssl dgst -md5 openssl dgst -sha1 ... You could write a wrapper for this, or just type the 14 extra characters ;) HTH, Alson To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: New feutures...........
* Wilko Bulte ([EMAIL PROTECTED]) wrote: > On Sat, Dec 15, 2001 at 03:26:27PM +, George Reid wrote: > > On Fri, Dec 14, 2001 at 11:03:49PM +0800, Rafter Man wrote: > > > > > 2. I hope that in the furture the FreeBSD developers will rewrite > > > the system in C++. > > > > Geez, talk about a bleak outlook for the future. I see myself > > flying over a frozen Hell on the back of a pig before that happens. > > pig... hmmm. How about a pinguin instead? Sorry, the penguin's reserved for when we reimpliment it in Perl. -- Thomas 'Freaky' Hurst - [EMAIL PROTECTED] - http://www.aagh.net/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: New feutures...........
On Sat, Dec 15, 2001 at 03:26:27PM +, George Reid wrote: > On Fri, Dec 14, 2001 at 11:03:49PM +0800, Rafter Man wrote: > > > 2. I hope that in the furture the FreeBSD developers will rewrite the system > > in C++. > > Geez, talk about a bleak outlook for the future. I see myself flying over > a frozen Hell on the back of a pig before that happens. pig... hmmm. How about a pinguin instead? :) -- | / o / /_ _ email: [EMAIL PROTECTED] |/|/ / / /( (_) Bulte Arnhem, The Netherlands To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
¦æ·Rªº¯u¿Í--ºV¤Ñ°óªºªù
English
¦æ·Rªº¯u¿Í ºV¤Ñ°óªºªù
·R¬O«í¤[§Ô@¡A¤S¦³®¦·O¡A·R¬O¤£¶ú§ª¡C·R¬O¤£¦Û¸Ø¡A¤£±i¨g¡A¤£°µ®`²Ûªº¨Æ¡C¤£¨D¦Û¤vªº¯q³B¡A¤£»´©öµo«ã¡A¤£pºâ¤H®aªº´c¡A¤£³ßÅw¤£¸q¡A¥u³ßÅw¯u²z¡C¤Z¨Æ¥]®e¡A¤Z¨Æ¬Û«H¡A¤Z¨Æ¬ß±æ¡A¤Z¨Æ§Ô@¡A¤Z¨Æn§Ô@¡A·R¬O¥Ã¤£¤î®§¡C
¡u·Rªº¯u¿Í¡v¬O¸t¸g¤¤ªº¤@¬q¸Ü¡A¸g¤H¾ã²z«á¡AÃЦ¨¤@¦±µÎ½w°ÊÅ¥ªº¤H¶¡¤§ºq¡C³oººq±q¤p¦Ü¤µ²`Àò§Ú³ß·R¡A¦L¶H¤¤¬O¦b¤p¾Ç¦X°Û¹Î¾Çªº¡C¦o¨ºÀu¬ü¬X©Mªº±Û«ß¡B¤º²[Â×´Iªººqµü¤£¦ýÀRÀq¦a´þ¾iµÛ§Úµ£¦~ªº¤ßÆF¡A¤]³§Ú«×¹L¤FµL¼ÆÓ¤H¥Íªº®À§é»P¦ÒÅç¡A·í§Ú¾D³{W´o©Î±¹ïÆg´®É¡A§Úªº¤ß©³®É±`ÅT°_³oº¸t¼äµL¤ñªººq¡C
§Ú±`·t¦Û¨ØªA¨®Çªº°ò·þ±ÐªB¤Í¡A¦]¬°¯«n¦oÌ°µªº¤£¥u¬O´¶³qªº¦n¤H¡A¦Ó¬O¨¥¦æѬü¡B«~¼w°ª¼äªº¦n¤H¤¤ªº¦n¤H¡I«e¤@°}¤l¡A¤@¦ì°ò·þ±Ð¦P¾Çªº½Í¸Ü¡A«oµ¹¤F§Ú¤@¨Ç«ä¦ÒªºªÅ¶¡¡A§Ú¬ðµM¹ï¦o«H¥õ¤W«Òªº¤è¦¡·P¨ì¦³¨ÇºÃ´b¡C
¦o¸g±`¼ö¤ß¦a»P©P³òªº¤H¤À¨É¯«¦p¦ó·RÅ@¥L̾ãÓ®a®x¡B¦p¦ó±x¤ß¦w±Æ¦oªº¤H¥Í¾D¹J¡A¯u¤ß¦a¶D»¡µÛ¯«ªºµL¨p¡B°¶¤j»P¥]®e¡C¨º¤ÑÅ¥¨ì¦o»¡¡G¡u¡KµL½×§A¥H«e°µ¤F¤°»ò¤£¦nªº¨Æ¡A¥un§A«HÍ¢¡AÍ¢´N·|±a»â§A¨«¦V¤Ñ°ê¡C¡v¹ï¤è°Ý¦o¡G¡u´N³o»ò²³æ¶Ü¡H¥un§Ú¬Û«HÍ¢¡A´N¥i¥H¤W¤Ñ°ê¶Ü¡H¡v¦o¦^µª¡G¡u¬O°Ú¡I´N¬O³o»ò²³æ¡I§A¬Ý¤W«Ò¦h»ò°¶¤j§r¡I¡v
§Ú¥Íªø¦b¤@Ó¨S¦³¯«¦ò«H¥õ¡B¬Æ¤Ö©v±Ð»ö¦¡ªº®a®x¸Ì¡C¾¨ºÞ¦b¦¨ªø¹Lµ{¤¤¡A»P©v±Ðªº±µÄ²«D±`¦³¡A¦ý¬O§Ú¤@ª½²`«H¡A¤HÁ`¸Ón¦³ÄÝ©ó¦Û¤vªº«H¥õ¡A¤]¦]¦¹¡A§Ú«K¤£Â_´M§ä¥å¥j¤£Åܪº¯u²z¡C
¦]µÛ¦P¾Çªº½Í¸Ü¡A§Ú¦A¤@¦¸«ä¦Ò¤H̹ï©ó©v±Ðªº»{ª¾¡C¤H¯uªº¤F¸Ñ¯«ªº¦®·N¶Ü¡H§Ú·Q¡A¤£ºÞ¬OC¿q©Î¬OÄÀ{¦È¥§¡A¬°¤F±Ï´ç¥@¤H¦Ó¶Ç¹DÁ¿ªk®É¡AÀ³¸Ó¨S¦³»¡¹L¦Û¤v¬O°ò·þ±Ð©Î¬O¦ò±Ð§a¡I·í§Ú»{ÃѨì©v±Ð¬O«á¤H©Ò¦Û³Ðªº¦Wµü¡A»ö¦¡¤]¬O¦]µÛ®ÉªÅI´º©Ò¦Û¦æ«Ø¥ßªº¤HÃþ¦æ¬°¡A¦Ó«D¯«ªº¦®·N¡A¤HÌ«H©^¡BÅ@½Ãªº¬O©v±Ð§Î¦¡¡A¦Ó«D¨ä¤¤©ÒÄÄ´ªº¯u²z¡A¬è¨Dªº¬O¦Û¤v¦b¥@¶¡ªº¦UºØ²{¹ê§Q¯q®É¡A¹ï©ó²{¤µ½Ñ¦h©v±Ð¶Ã¶H¤]´N¤£¨º»òºN¤£µÛÀYºü¤F¡C¤]Ãø©Ç§Úªº¦P¾Ç·|¦p¦¹¤Ñ¯uªº¥H¬°¥u¦bªí±¤W¡B§Î¦¡¤W¡u«HC¿q´N±o¥Ã¥Í¡v¤F¡C
§Ú»{¬°«H¤£¥u¬Oºë¯«¤Wªº°í¦u¡A§ó¬O¦æ°Ê¤Wªº¸¨¹ê¡C´N¦p¦P§Ú̦b¾Ç®Õ¾Ç²ß¤@¼Ë¡A¦pªG§Ú¬Û«H¥un¦Ò¶i¤@¬y°ª¤¤¡A´N¥i¥H¥]¤¤½Ñ¦h¾Ç¤l¹Ú´K¥H¨Dªº¤j¾Ç¦W®Õ¡A¦Ó¤£¦b¤T¦~ªº°ª¤¤¥Í²P¤¤»{¯uÅ¥Á¿¡AºÉ¤O°µ¦n¤@Ӿǥͪº¥»¤À¡A¤S«ç¯à¹ê²{¦¨¬°¤j¾Ç·sÂA¤Hªº¬üÄR¹Ú·Q©O¡H¥¿½Tªº«ä¦Ò¦ñÀH¿n·¥ªº¦æ°Ê¡A¤£¥¿¬O¦¨´N½Ñ¦h¬ü¨Æªº¥ý¨Mn¥ó¶Ü¡H
§Ú·Q¤£ºÞ§Ų́Ӧۦó¤è¡A¹LµÛ¤°»ò¼Ëªº¥Í¬¡¡A¬O§_¾Ö¦³©v±Ð«H¥õ¡A§Ú´Á¬ß¤H̳£¯à±N¡u·Rªº¯u¿Í¡vªººë²`¤º²[»P¬ü¦n¼w¦æ¿Ä¤J¥Í¬¡ÂIºw¤§¤¤¡A°µÓ¯u¥¿¤ßÆF¼ä²b¡B¹D¼w°ª©|ªº¦n¤H¡C
(ºK¿ý¦Û¤j¬ö¤¸©P³ø)
¡·§Úı±o³o¬O¤@½g¦n¤å³¹¡A©Ò¥H·Q©M§ó¦hªº¤H¤À¨É¡A§Æ±æ¨S¦³¥´ÂZ¨ì§A¡CY§AÁÙ³ßÅw³o¤å³¹Åwªï¼g«H»P§Ú¤À¨É¡A Y§A¤£·Q¦A¦¬¨ìÃþ¦ü¤å³¹¤]½Ð¦^«Hµ¹§Ú¡CÁÂÁ§A¡I
Fa-yin
¡·¤W¦^¹q¸£·í¾÷¡A¦³¨Ç«H¤£¨£¤F¡A¥i§_½Ð§A¦A±H¤@¦¸µ¹§Ú¡C
¡° This is internet sharing, hope not bothering
you. If you can't understand Chinese,
please click here
reply me, and there will be no more e-mail from us. Thank
you!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: New feutures...........
On Fri, Dec 14, 2001 at 11:03:49PM +0800, Rafter Man wrote: > 2. I hope that in the furture the FreeBSD developers will rewrite the system > in C++. Geez, talk about a bleak outlook for the future. I see myself flying over a frozen Hell on the back of a pig before that happens. -- George C A ReidTel: (08701) 200870 Ext. 26654 FreeBSD Committer/Developer [EMAIL PROTECTED] Oriel College, Oxford University[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: sha1 program
On 15-Dec-2001 Dominic Marks wrote: > Why not have one program for all the supported hash algorithms as > opposed to individual ones for each (md5, sha1) ? > > You could use something like: > > > hash -a md5 /some/file > > hash -a sha1 /some/other/file Conceivably a fairly simple script or two could be written to use openssl instead. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: boot0
Hiten Pandya wrote: > I found this piece of code in boot0.s, is it possible > if you could explain me a bit about it. > > .set NHRDRV,0x475# Number of hard drives > > The hex value comes out to: 1141. > > Does that mean, that this is the amound of maximum > hard drives a user can have on FreeBSD? No. The BIOS bootstrap loaded passes the boot drive in the %DL; this gets pushed, and later poped for the byt compare; the compare is based on a storage location of a relative offset. Frankly, you don't need to understand this code if you are trying to get the boot loader to understand JFS; instead you want to add JFS support into boot1/2 via libstand in /usr/src/lib/libstand. See /usr/src/lib/libstand/ufs.c, and look at how the library is able to select the routines in ufs.c vs. cd9660.c. If you are serious about this, handle read-only non-root JFS mounts of Linux created disks, first, and then work up to read/write, root mount, and then booting (in that order). -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: sha1 program
On Saturday 15 December 2001 11:34 am, Mike Wiacek wrote: > We currently have a MD5 driver, but no SHA1 driver, even though > we have SHA1 as part of libmd. So I took md5.c from > /usr/src/sbin/md5 and made sha1.c as well as a respective man page. > Attached is the source file, the manual page for it, as well as a > makefile. > > Hope this is useful and makes its way into the tree. Md5 has some > questionable attacks against it, and Schneier claims that > sha is resillient to such attacks. > > mike Why not have one program for all the supported hash algorithms as opposed to individual ones for each (md5, sha1) ? You could use something like: > hash -a md5 /some/file > hash -a sha1 /some/other/file -- Dominic To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
sha1 program
We currently have a MD5 driver, but no SHA1 driver, even though
we have SHA1 as part of libmd. So I took md5.c from /usr/src/sbin/md5
and made sha1.c as well as a respective man page. Attached is the
source file, the manual page for it, as well as a makefile.
Hope this is useful and makes its way into the tree. Md5 has some
questionable attacks against it, and Schneier claims that
sha is resillient to such attacks.
mike
/*
* Derived from:
*
* MDDRIVER.C - test driver for MD2, MD4 and MD5
*/
/*
* Further dervied from the FreeBSD md5 driver program.
* Converted to generate SHA 160 bit hashes.
* Mike Wiacek <[EMAIL PROTECTED]> 12/14/2001
*/
#ifndef lint
static const char rcsid[] =
"$FreeBSD$";
#endif /* not lint */
#include
#include
#include
#include
#include
#include
#include
#include
/*
* Length of test block, number of test blocks.
*/
#define TEST_BLOCK_LEN 1
#define TEST_BLOCK_COUNT 10
int qflag;
int rflag;
static void SHAString(const char *);
static void SHATimeTrial(void);
static void SHATestSuite(void);
static void SHAFilter(int);
static void usage(void);
/* Main driver.
Arguments (may be any combination):
-sstring - digests string
-t - runs time trial
-x - runs test script
filename - digests file
(none) - digests standard input
*/
main(int argc, char *argv[])
{
int ch;
char *p;
unsigned char buf[41] = {0};
while ((ch = getopt(argc, argv, "pqrs:tx")) != -1)
switch (ch) {
case 'p':
SHAFilter(1);
break;
case 'q':
qflag = 1;
break;
case 'r':
rflag = 1;
break;
case 's':
SHAString(optarg);
break;
case 't':
SHATimeTrial();
break;
case 'x':
SHATestSuite();
break;
default:
usage();
}
argc -= optind;
argv += optind;
if (*argv) {
do {
p = SHA1_File(*argv, buf);
if (!p)
warn("%s", *argv);
else
if (qflag)
printf("%s\n", p);
else if (rflag)
printf("%s %s\n", p, *argv);
else
printf("SHA1 (%s) = %s\n", *argv, p);
} while (*++argv);
} else if (optind == 1 || qflag || rflag)
SHAFilter(0);
return (0);
}
/*
* Digests a string and prints the result.
*/
static void
SHAString(const char *string)
{
size_t len = strlen(string);
unsigned char buf[41] = {0};
if (qflag)
printf("%s\n", SHA1_Data(string, len, buf));
else if (rflag)
printf("%s \"%s\"\n", SHA1_Data(string, len, buf), string);
else
printf("SHA1 (\"%s\") = %s\n", string, SHA1_Data(string, len, buf));
}
/*
* Measures the time to digest TEST_BLOCK_COUNT TEST_BLOCK_LEN-byte blocks.
*/
static void
SHATimeTrial(void)
{
SHA_CTX context;
time_t endTime, startTime;
unsigned char block[TEST_BLOCK_LEN];
unsigned int i;
char *p;
unsigned char buf[41] = {0};
printf
("SHA1 time trial. Digesting %d %d-byte blocks ...",
TEST_BLOCK_COUNT, TEST_BLOCK_LEN);
fflush(stdout);
/* Initialize block */
for (i = 0; i < TEST_BLOCK_LEN; i++)
block[i] = (unsigned char) (i & 0xff);
/* Start timer */
time(&startTime);
/* Digest blocks */
SHA_Init(&context);
for (i = 0; i < TEST_BLOCK_COUNT; i++)
SHA_Update(&context, block, TEST_BLOCK_LEN);
p = SHA1_End(&context,buf);
/* Stop timer */
time(&endTime);
printf(" done\n");
printf("Digest = %s", p);
printf("\nTime = %ld seconds\n", (long) (endTime - startTime));
/* Be careful that endTime-startTime is not zero. (Bug fix from Ric
* Anderson, [EMAIL PROTECTED]) */
printf
("Speed = %ld bytes/second\n",
(long) TEST_BLOCK_LEN * (long) TEST_BLOCK_COUNT / ((endTime - startTime)
!= 0 ? (endTime - startTime) : 1));
}
/*
* Digests a reference suite of strings and prints the results.
*/
static void
SHATestSuite(void)
{
printf("SHA1 test suite:\n");
SHASt
Re: Does anyone know if the Broadcom BCM5700 has problems with HW csum?
David Greenman wrote: > Alfred Perlstein wrote: > >You're probably incorrect, it doesn't matter if vlan tags are active > >or not, it's most likely wheather or not the firmware is being asked > >to handle them at all. > >I would think it would get the checksum wrong most of the time if that > were the case. It seems to only have problems with small packets, but the > behavior is pretty strange, so who knows. Do you have some specific knowledge > about Broadcom and brokeness related to VLAN tag support when not using > VLANs? If it's very small payload, it's probably a byte-order-in-buffer issue (several Eagle manufactured cards had similar problems, and so did the NE1000, when it came to DMA transfers, back when 16 bit transfers were new 8^). For VLANs, yes, there are specific problems known with the Broadcom cards when the firmware support for VLANs is enabled. The first card known to work with checksum offload enable and VLAN support enabled (whether it's used or not) is the Tigon III. I don't know if Bill Paul fixed the firmware for the Tigon II in this case (he has been known to hack Tigon II firmware), but it could have been fixed by now. In any case, disabling it is what ClickArray ended up doing, as well, for the Tigon II, until the firmware could be fixed. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Adding a new FS to FreeBSD
Greg Lehey wrote: > Unfortunately, it's still copyrighted. You need an SCO license; want > to go and get one of them? It doesn't cost anything, but I can't give > the software to anybody who hasn't agreed to the conditions. 8.4(b) says you can't give it to anyone, even if they do have the license, unless you contact Caldera first, and then maintain (in perpeturity) a list of the sources made available. I think we are screwed by section 2.1(d) anyway: Commercial use by LICENSEE of SOURCE CODE PRODUCTS or of any result, enhancement or modification associated with the use of SOURCE CODE PRODUCTS under this AGREEMENT is not permitted. Basically, I couldn't get an article out of it because I could't disclose it to anyone but a licensesee, and only a licensee could use the code, and I couldn't give source to the licensee without the permission of Caldera, and once they had the code, they could not use it for anything commercial unless they negotiated a seperate commercial use license. Frankly, if you want to provide small disk images (preferrably, very small, not multimegabyte) as I've described are needed anyway, along with a description of the what's on the images, along with such layout information as you feel comfortable providing, I'd pretty much rather reverse engineer the stuff than get a Caldera license. At least that way, I can get an article out of doing the thing. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Does anyone know if the Broadcom BCM5700 has problems with HW csum?
David Greenman wrote: > >I believe you will find that the problem is related to the firmware > >handling of VLAN tagging, and that the problem only exists if VLAN > >tagging is enabled. > >You would believe wrongly, then, because the problem that I was seeing did > not involve VLAN tags. OK; it was worth a shot, since Broadcom was known to get that part wrong (they blew it big time on the Tigon II firmware). Too bad; the checksum offload is usually really helpful, if you can get arounf the quirks. 8^(. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
boot0
hi, I found this piece of code in boot0.s, is it possible if you could explain me a bit about it. .set NHRDRV,0x475# Number of hard drives The hex value comes out to: 1141. Does that mean, that this is the amound of maximum hard drives a user can have on FreeBSD? If that is so, is there a way to boost that value a bit higher, or am I just getting the whole point wrong? Thanks, =Hiten =<[EMAIL PROTECTED]> __ Do You Yahoo!? Check out Yahoo! Shopping and Yahoo! Auctions for all of your unique holiday gifts! Buy at http://shopping.yahoo.com or bid at http://auctions.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Does anyone know if the Broadcom BCM5700 has problems with HW csum?
>* David Greenman <[EMAIL PROTECTED]> [011215 03:12] wrote: >> >Brooks Davis wrote: >> >> There was a commit to current a few hours ago disabling hardware >> >> checksums on recieve due to corruption problems. It will be MFC'd in >> >> three days though it's a two line fix so you could apply it your self: >> >> >> >> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/if_bge.c.diff?r1=1.4&r2=1.5 >> > >> >I believe you will find that the problem is related to the firmware >> >handling of VLAN tagging, and that the problem only exists if VLAN >> >tagging is enabled. >> >>You would believe wrongly, then, because the problem that I was seeing did >> not involve VLAN tags. > >You're probably incorrect, it doesn't matter if vlan tags are active >or not, it's most likely wheather or not the firmware is being asked >to handle them at all. I would think it would get the checksum wrong most of the time if that were the case. It seems to only have problems with small packets, but the behavior is pretty strange, so who knows. Do you have some specific knowledge about Broadcom and brokeness related to VLAN tag support when not using VLANs? -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Does anyone know if the Broadcom BCM5700 has problems with HW csum?
>I am playing with a driver for the Broadcom 5700/5701. > >It recognizes the 5700 in my 3Com cards OK, but seems to screw up the >TCP checksum. > >Switching off hardware checksum capability fixes it. > >Does anyone know the details of which stepping this stuff worked on? I haven't nailed down the problem that I've seen with them to a specific chipset, but I can confirm that they incorrectly calculate the checksum on input packets in some cases. It seems to be related to both packet size and certain TCP options (or lack of them). I've only seen the problem occur with very small (0-4 byte payload) packets. In any case, after discussing this problem with Bill Paul, I disabled input checksum in the -current driver and intend to merge that to -stable in a few days. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Does anyone know if the Broadcom BCM5700 has problems with HW csum?
* David Greenman <[EMAIL PROTECTED]> [011215 03:12] wrote: > >Brooks Davis wrote: > >> There was a commit to current a few hours ago disabling hardware > >> checksums on recieve due to corruption problems. It will be MFC'd in > >> three days though it's a two line fix so you could apply it your self: > >> > >> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/if_bge.c.diff?r1=1.4&r2=1.5 > > > >I believe you will find that the problem is related to the firmware > >handling of VLAN tagging, and that the problem only exists if VLAN > >tagging is enabled. > >You would believe wrongly, then, because the problem that I was seeing did > not involve VLAN tags. You're probably incorrect, it doesn't matter if vlan tags are active or not, it's most likely wheather or not the firmware is being asked to handle them at all. -- -Alfred Perlstein [[EMAIL PROTECTED]] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' http://www.morons.org/rants/gpl-harmful.php3 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Does anyone know if the Broadcom BCM5700 has problems with HW csum?
>Brooks Davis wrote: >> There was a commit to current a few hours ago disabling hardware >> checksums on recieve due to corruption problems. It will be MFC'd in >> three days though it's a two line fix so you could apply it your self: >> >> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/if_bge.c.diff?r1=1.4&r2=1.5 > >I believe you will find that the problem is related to the firmware >handling of VLAN tagging, and that the problem only exists if VLAN >tagging is enabled. You would believe wrongly, then, because the problem that I was seeing did not involve VLAN tags. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Adding a new FS to FreeBSD
On Saturday, 15 December 2001 at 0:39:32 -0800, Terry Lambert wrote: > Greg Lehey wrote: >>> Do you have small images of this FS, as well as header files that >>> are redistributable (e.g. BSD license) and/or code? >>> >>> If you have the tools sources (e.g. "newfs", "fsck", etc.), this would >>> be useful, as well, since I could vnconfig a device and recreate an >>> empty FS image with native tools (self hosted), as well. >> >> I've got everything here, but it sounds like Jeremy does too. >> Depending on the value of 2, this is either the old 6th edition file >> system or an early variant of UFS; either's not difficult. > > If anyone wants to put this stuff up on a web site so I can grab > it before I go on vacation next week, I can work on it over the > break, since I will probably be going stir-crazy anyway, jonesing > for some code to write... Unfortunately, it's still copyrighted. You need an SCO license; want to go and get one of them? It doesn't cost anything, but I can't give the software to anybody who hasn't agreed to the conditions. Get the license at http://shop.caldera.com/caldera/ancient.html (yup, that's what SCO has become). Note that the link to PUPS in the follow-on page (http://www2.caldera.com/offers/ancient001/) is broken: it's now http://minnie.tuhs.org/PUPS/ Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Adding a new FS to FreeBSD
Greg Lehey wrote: > > Do you have small images of this FS, as well as header files that > > are redistributable (e.g. BSD license) and/or code? > > > > If you have the tools sources (e.g. "newfs", "fsck", etc.), this would > > be useful, as well, since I could vnconfig a device and recreate an > > empty FS image with native tools (self hosted), as well. > > I've got everything here, but it sounds like Jeremy does too. > Depending on the value of 2, this is either the old 6th edition file > system or an early variant of UFS; either's not difficult. If anyone wants to put this stuff up on a web site so I can grab it before I go on vacation next week, I can work on it over the break, since I will probably be going stir-crazy anyway, jonesing for some code to write... This works for either the 2BSD or the S51K stuff (or Acer FFS, if that is what was being referred to in the SCO case). -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
