Re: X11/C++ question
In message [EMAIL PROTECTED] Chuck Robey writes: : Does anyone (anyone, that is, who's coded X11 applications) know how you : handle X11 callbacks to C++ object methods? OI_add_event(3OI) :-) Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: gas pseudo-ops
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of John Polstra Sent: Wednesday, November 03, 1999 1:54 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: gas pseudo-ops In article [EMAIL PROTECTED], Stephane E. Potvin [EMAIL PROTECTED] wrote: Does anyone have any idea where I could find some documentation about the following gas pseudo-ops? .type set,@object There is a type associated with symbol in the object files. It can be function (obvious), object (data), or other/unknown. This pseudo-op sets the type of a given symbol. .previous The assembler maintains a stack of sections. Each time you change to a new section, it pushes the previous one onto the stack. The ".previous" pseudo-op pops the stack and changes back to the previous section. Thanks for the answer! Do you think it would be possible to change the .type symbol,@object for .type symbol,object in gensetdef? By looking in the gas code I found that the assembler just ignores the @ character. The reason I ask this is because by default, the @ character is used by the ARM assembler to represent begin of comments. GCC/GAS could be hacked to avoid doing this but in the long run I think it would be easier just to remove the @ character. If I remember correctly it could be changed to `#object' or `%object' too but this could cause the same problem as with the @ character for other assemblers. P.S.: Sorry for the lack of diff, I'm currenty at work and don't have access to the source code Steph -- Stephane E. Potvin InnoMediaLogic Inc. - http://www.multichassis.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: X11/C++ question
On Wed, 3 Nov 1999, Warner Losh wrote: In message [EMAIL PROTECTED] Chuck Robey writes: : Does anyone (anyone, that is, who's coded X11 applications) know how you : handle X11 callbacks to C++ object methods? OI_add_event(3OI) :-) Uhhh? I've long since got the answer I wanted, but this seems a complete mystery, so I'll bite, what's a OI_add_event? From some package? Can't find a man page on it. Warner Chuck Robey| Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Netgear FA410 pccard ethernet?
On Wed, Nov 03, 1999 at 01:07:29AM -0500, Wes Peters wrote: As far as the FA410 goes, you might try some permutation of "ed". Their datasheet on the website is singularly unhelpful: http://www.netgearinc.com/products/ds_fa410tx/index.shtml You're right, there's no information there. I did get it going with the "ed" driver, after reading some old messages on the freebsd-mobile list. It seems to work only in one direction, however. Outgoing ping, telnet, ssh, http, all work, but incoming does not. When I try a different pccard ethernet (an NE4100, which also uses the "ed" driver), everything works fine, so the problem seems to be with the card. -Guy To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Netgear FA410 pccard ethernet?
Guy Middleton [EMAIL PROTECTED] wrote: On Wed, Nov 03, 1999 at 01:07:29AM -0500, Wes Peters wrote: As far as the FA410 goes, you might try some permutation of "ed". Their datasheet on the website is singularly unhelpful: http://www.netgearinc.com/products/ds_fa410tx/index.shtml You're right, there's no information there. I did get it going with the "ed" driver, after reading some old messages on the freebsd-mobile list. It seems to work only in one direction, however. Outgoing ping, telnet, ssh, http, all work, but incoming does not. When I try a different pccard ethernet (an NE4100, which also uses the "ed" driver), everything works fine, so the problem seems to be with the card. It is listed as a supported card in PAO. I have one as well but never got it to work. I haven't tried PAO yet as I have got a spare 3COM card, but it would be nice to be able to run at 100Mbps. Robert Swindells To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: X11/C++ question
In message [EMAIL PROTECTED] Chuck Robey writes: : Uhhh? I've long since got the answer I wanted, but this seems a complete : mystery, so I'll bite, what's a OI_add_event? From some package? Can't : find a man page on it. OI was a native C++ toolkit that had a nice interface and was ported to Linux and FreeBSD back in 1993 or so by yours truly. It was available from ParcPlace. Sadly, it never went anywhere and all efforts of the engineers to make it open sourced (this was in 1996) failed. It was ment as a joke for the long timers on the list... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: X11/C++ question
In message [EMAIL PROTECTED] Chuck Robey writes: : Uhhh? I've long since got the answer I wanted, but this seems a complete : mystery, so I'll bite, what's a OI_add_event? From some package? Can't : find a man page on it. OI was a native C++ toolkit that had a nice interface and was ported to Linux and FreeBSD back in 1993 or so by yours truly. It was available from ParcPlace. Sadly, it never went anywhere and all efforts of the engineers to make it open sourced (this was in 1996) failed. It was ment as a joke for the long timers on the list... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message Let me add that as a stock holder of ParcPlace (now ObjectShare) and one of the people who tried out OI - I was disappointed it didn't go anywhere. It seemed nice... (I wonder where it is now?) ObjectShare is trading right now at 44-cents/share - an amazing 18.92% increase so far for the day (up 7 cents). Perhaps that outstanding stock price reflects the outcome of some of their decisions? [I believe my last purchase of ObjectShare was somewhere in the $10 range... sigh.] - Dave Rivers - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Need help to run IP protocol 50 traceroute from Hong Kong
(Warning: Unrelated to FreeBSD except for the fact that FreeBSD-current and recent -stable traceroute supports the -P option.) I need to find out if IP protocol 50 (used by IPSec) is being blocked on the way from Hong Kong to a customer of Telia in Norway. Could somebody in or near Hong Kong, running FreeBSD-current or FreeBSD 3.3, please send me the output of "traceroute -P 50 flow1.telia.no". I'm particularly interested if you get a "!P" (protocol unreachable) on the way. This is what a normal traceroute looks like from Hongkong Telecom Netplus, http://traceroute.hkt.net/cgi-bin/nph-traceroute but of course this doesn't tell me anything about IP protocol 50. Thanks in advance! Steinar Haug, Nethelp consulting, [EMAIL PROTECTED] -- traceroute to flow1.telia.no (194.19.1.190): 1-30 hops, 38 byte packets 1 e1-3.tmh08.hkt.net (202.84.255.62) 1.24 ms 0.657 ms 0.722 ms 2 a5-0-1.yck05.hkt.net (205.252.130.82) 1.56 ms 4.21 ms 2.10 ms 3 f5-0.hk-T3.hkt.net (205.252.130.207) 2.10 ms 1.53 ms 1.95 ms 4 hssi8-0-0.paix-T3.hkt.net (202.84.128.254) 201 ms 207 ms 198 ms 5 915.Hssi5-0.GW1.PAO1.ALTER.NET (157.130.193.133) 195 ms (ttl=248!) 184 ms (ttl=248!) 181 ms (ttl=248!) 6 119.ATM3-0.XR2.PAO1.ALTER.NET (146.188.147.230) 187 ms (ttl=249!) 192 ms (ttl=249!) 184 ms (ttl=249!) 7 188.ATM7-0.XR2.SFO4.ALTER.NET (146.188.146.230) 185 ms 202 ms 189 ms 8 190.ATM11-0-0.GW4.SJC2.ALTER.NET (152.63.51.133) 206 ms 194 ms 189 ms 9 telia-gw.customer.ALTER.NET (157.130.229.118) 268 ms (ttl=246!) * 264 ms (ttl=246!) 10 sf-b1-atm3-0-103.telia.net (209.95.159.41) 266 ms 272 ms 265 ms 11 ny-b1-pos5-0-0.telia.net (209.95.159.22) 260 ms (ttl=247!) 261 ms (ttl=247!) 261 ms (ttl=247!) 12 sto-b1-pos1-0.telia.net (194.17.1.185) 363 ms (ttl=246!) 362 ms (ttl=246!) 361 ms (ttl=246!) 13 ov-i9-atm3-0-0-1.telia.net (194.17.1.110) 371 ms (ttl=245!) 368 ms (ttl=245!) * 14 no-oso-i1.telia.net (194.19.1.145) 398 ms (ttl=244!) 417 ms (ttl=244!) 389 ms (ttl=244!) 15 oslo-accl1.telia.net (194.19.1.116) 383 ms (ttl=243!) 379 ms (ttl=243!) 397 ms (ttl=243!) 16 flow1.telia.no (194.19.1.190) * 377 ms (ttl=242!) 378 ms (ttl=242!) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Granularity of disk I/O
On Tue, 2 Nov 1999, Greg Lehey wrote: On Tuesday, 2 November 1999 at 17:10:41 -0500, Zhihui Zhang wrote: It is said that the granularity of disk I/O is a sector. I read a little bit of the source code isa/wd.c, which I think is the driver of IDE disks. I find out that the disk can perform multi-block I/O sometimes. Does this mean the granularity of disk I/O can be multi-sector? I think you're getting bogged down in terminology. I understand "granularity" to imply the steps in which a quantity can be increased. In this case, a disk transfer is a whole number of sectors between 1 and 256 (though there's an artificial limit which makes it difficult to transfer more than 60 at a time). Using my definition, it would be correct to say that the granularity is 1 sector. If the disk can perform DMA, what is the usual DMA size? It's normally the size of the transfer, but in the case of IDE drives it can be limited to a maximum value by the the disk flags. If a buffer cache is larger than one sector, it should be split into sectors before I/O. No, that would give lousy performance. Buffer cache is also allocated in blocks corresponding to the transfer size. If an I/O on a buffer fails, can we tell which sector within that buffer fails? I don't think we do that. The way to recover would be to retry the I/O a sector at a time. That way, you waste time in the exceptional case only. Thanks for your reply. I know that directory entries are physically prevented from crossing device block boundaries in order to ensure atomic update. If I write a directory file with a buffer (using some kind of multi-sector transfer) and do not know which sector within the buffer fails, what will the filesystem do? -Zhihui To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Netgear FA410 pccard ethernet?
Robert Swindells wrote: Guy Middleton [EMAIL PROTECTED] wrote: On Wed, Nov 03, 1999 at 01:07:29AM -0500, Wes Peters wrote: As far as the FA410 goes, you might try some permutation of "ed". Their datasheet on the website is singularly unhelpful: http://www.netgearinc.com/products/ds_fa410tx/index.shtml You're right, there's no information there. I did get it going with the "ed" driver, after reading some old messages on the freebsd-mobile list. It seems to work only in one direction, however. Outgoing ping, telnet, ssh, http, all work, but incoming does not. When I try a different pccard ethernet (an NE4100, which also uses the "ed" driver), everything works fine, so the problem seems to be with the card. It is listed as a supported card in PAO. You might want to look at the flags settings and such in the PAO pccard configuration files. I have one as well but never got it to work. I haven't tried PAO yet as I have got a spare 3COM card, but it would be nice to be able to run at 100Mbps. If you're expecting to get anywhere near 100Mbps performance out of a PCCard, you're going to be shocked. These cards allow you to connect to a 100BaseTX port, but aren't going to deliver anywhere near 100Mbps throughput. I've seen figures like 16Mbps quoted, but haven't tried any measurments myself. CardBus will certainly help all this mess, when Warner and the gang have it really working. If you have a particular card you'd like to see work, talk to Warner about sending him one. He might even send it back when he's done with it. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC [EMAIL PROTECTED] http://softweyr.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Netgear FA410 pccard ethernet?
[EMAIL PROTECTED] said: :- Outgoing ping, telnet, ssh, http, all work, but incoming does not. :- When I try a different pccard ethernet (an NE4100, which also uses the :- "ed" driver), everything works fine, so the problem seems to be with :- the card. I don't think so. I've had lots of problems with the pccard system in the past (I havn't tried it with anything newer than 2.2.8PAO though so maybe things got better) that weren't the fault of the cards, primarily in IO addresses and Interrupt stuff. Anyway, I have this card running with 2.2.8 PAO. I remember I had to play with some options in the pccard.conf file because things wouldn't work without them. But that was so long ago I don't remember anymore what the exact problem was or if that was even what the issue was Sorry. # Generally available IO ports io 0x240-0x2e0 0x300-0x360 # Generally available IRQs (DEPRECATED, USE OF THE OPTION IS DISCOURAGED) irq 10 11 # Available memory slots memory 0xd4000 96k Other than that, the entry for the card is pretty basic. # BayNetworks NETGEAR FA410TXC Fast Ethernet card "NETGEAR" "FA410TX" "Fast Ethernet" config default "ed0" any insert echo NETGEAR FA410TX inserted insert /etc/pccard_ether $device remove echo NETGEAR FA410TX removed remove /etc/pccard_ether_remove $device When the card attaches it is called a Linksys and it runs with the ed driver, and gives me good performance on a 100Tx network. -- Robert Withrow -- (+1 978 288 8256) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Granularity of disk I/O
From the system's point of view, there is no difference in reliability between doing a single sector transfer and a multi-sector transfer except for the size of the retry. Since retries do not occur very often nobody really cares how big the retry is. Since there is a huge performance gain doing multi-sector transfers, that is what the system does. Thanks. It seems to me that for a filesystem, a block (or a fragment) is the unit of I/O. Even if a single byte is modified, an entire block probably consisting of multiple sectors must be written back to the disk. As you said, there is no differnce whether we write this block one sector at a time or in a single transfer. If so, I wonder whether the atomicity of a sector I/O required by a directory file is necessary any more. -Zhihui To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
nfs cookie spoofing patch
I was wondering if I could get some help. I am running a FreeBSD 2.2.8 machine configured as a nfs server. We are trying to get another machine running 2.2.8 to mount from the nfs server. Our challenge is that we are using a virtual ip and would like to mount the virtual ip. We are already doing this with SCO unix as well as Sun Solaris. The problem is that when I type mount -t argonnfs:/u /u (I have also tried with -o -i,-s,-r=1024,-w=1024 options and all permutation of the options, including mount_nfs -T) I'll hang waiting for the request to time out. After extensive trouble shooting, I think it is because of the "security feature" to prevent NFS cookie spoofing based attacks. Basically, there is an nfs check that will not allow freebsd nfs client to request an nfs mount and have the machine where the nfs request is being made to reply with its real ip instead of the virtual. It is as if freebsd hangs becuase the reply for the mount came from a second ip address. Please reference the following url from Terry Lambert. I tried to find the patch that was mentioned in the url, but could not. http://www.freebsd.org/cgi/mid.cgi?db=irt[EMAIL PROTECTED] Can anyone help me or point me in the right direction. I would like to disable the nfs check or find a work around. The reason we use the virtual ip address is because we have designed some failover code that allows us to failover nfs in about 3 seconds, from one system to another. By passing the virtual ip around from one machine to another, all the machine that had mounted the filesystem never really notice an outage. With a RAID attached and exporting the filesystem, we can achieve high availability of data (not quite fault tolerant, but getting there). Any help is appreciated. Thanks. Regards, -- Juan Lorenzana AG Communication Systems Phoenix, AZ 602-582-7442 [EMAIL PROTECTED]
Re: Granularity of disk I/O
:Thanks. It seems to me that for a filesystem, a block (or a fragment) is :the unit of I/O. Even if a single byte is modified, an entire block :probably consisting of multiple sectors must be written back to the disk. :As you said, there is no differnce whether we write this block one sector :at a time or in a single transfer. If so, I wonder whether the atomicity :of a sector I/O required by a directory file is necessary any more. : :-Zhihui The directory blocking is there for a different reason. Atomicy does not have much to do with it though perhaps it did at some point in the past. The reason directory entries are not allowed to cross a 'block' boundry is two fold: * First, to properly support the use of a directory offsets for seeking into directories when doing a complex directory scan. Since userland can supply any offset, even a garbage offset, the kernel code needs to be able to find a starting point from which it can scan forward to locate the directory entry the user is requesting and *be sure* that it is a legal entry. The filesystem avoids having to scan from the very beginning of a potentially huge directory by understanding that it can start at the beginning of the directory block containing the offset. * Second, to simplify the directory scanning code. The kernel maps filesystem buffers into memory on a filesystem block-by-block basis. The directory scanning code is greatly simplified by not allowing directory entries to cross a block boundry. There are also other issues involved relating to newer system calls and even NFS that pretty much requires directory entries to not cross block boundries, though in these cases the 'size' of the block is kinda fuzzy. There are also legacy issues. -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
(forw) Reversing 32Upgrade package
Is there anyway to reverse 32upgrade package after it has been installed on a 2.2.8-STABLE system. This is on a production box and rebuilding is not an option I have time to explore. -- --- Ron Rosson ... and a UNIX user said ... The InSaNe One rm -rf * [EMAIL PROTECTED]and all was /dev/null and *void() --- Eagles may soar, but weasels don't get sucked into jet engines. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Granularity of disk I/O
:Thanks. It seems to me that for a filesystem, a block (or a fragment) is :the unit of I/O. Even if a single byte is modified, an entire block :probably consisting of multiple sectors must be written back to the disk. :As you said, there is no differnce whether we write this block one sector :at a time or in a single transfer. If so, I wonder whether the atomicity :of a sector I/O required by a directory file is necessary any more. : :-Zhihui The directory blocking is there for a different reason. Atomicy does not have much to do with it though perhaps it did at some point in the past. I think atomicity is still the reason. The basic block size of a directory is still a 512-byte sector, and chances are we might write directory blocks one sector at a time (4k/512 formatted fs), so we have to guarantee directory entries don't cross the 512-byte sector boundary. On a 8k/1k fs, you probably could get away with crossing the odd 512-byte sector boundary though. -lq To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Linux* 2.2.x Driver inetl Etherexpress 1000
http://www.intel.com/support/network/adapter/1000/30363.htm -- Email: [EMAIL PROTECTED]Voice: +780 413 1910 Fax: +780 421 4929 #575 Sun Life Place * 10123 99 Street * Edmonton, AB * Canada * T5J 3H1 ---- When things can't get any worse, they simplify themselves by getting a whole lot worse then complicated. A complete and utter disaster is the simplest thing in the world; it's preventing one that's complex. (Janet Morris) Title: Linux* 2.2.x Driver Return to: Ethernet Adapters Home Gigabit Server Home Software Drivers Installation Use Manuals Literature Year 2000 Intel Forum White Papers Intel PRO/1000 Gigabit Server Adapter Linux* 2.2.x Driver Copyright (c) 1999, Intel Corporation All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 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. Neither the name of Intel Corporation nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 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. I Agree I Disagree Please tell us if the information provided here was useful. Yes No Partially I have to try it Please describe what you were looking for: * Legal Information and Privacy Policy 1999 Intel Corporation begin:vcard n:Skafte;Greg tel;pager:+1 (780) 491 4791 tel;cell:+1 (780) 718 1570 tel;fax:+1 (780) 421 4929 tel;work:+1 (780) 413 1910 x-mozilla-html:FALSE org:A HREF="http://www.worldgate.ca"IMG BORDER=0 SRC="http://dev.worldgate.ca/images/worldgate_black_200_bolder.gif"/A;Network Operations adr:;;#575 10123 99 Street;Edmonton;Alberta;T5J 3H1;Canada version:2.1 email;internet:[EMAIL PROTECTED] title:Operations Manager x-mozilla-cpt:;29088 fn:Greg Skafte end:vcard
Re: Linux* 2.2.x Driver inetl Etherexpress 1000
Yes, we know. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Linux* 2.2.x Driver inetl Etherexpress 1000
Matthew Jacob writes: Yes, we know. and PLEASE only send the URL in future ! I do not appreciate getting mails which cause my MUA (exmh) to dial out to grab some goddamned crap off the web. If I want to look at the URL, I will. --- Gary Jennejohn Home - [EMAIL PROTECTED] Work - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
becoming part of FreeBSD Developer
Dear gentleman, i have been using free for the last 12 months! I have never done anything in terms of system development, so i decide it was the time to get more involved with FBSD development. In repect to this regard, i sent a mail to Mr. David Greenman, whose response was: "The first step is to get involved with the development community by subscribing to the FreeBSD mailing lists such as freebsd-arch and freebsd-hackers." So here i am. But the doubts keeps on! I have a pretty small knownledge about SO internals, but nothing close to what many of you have, what you wizards suggest me? I have no ideia on where to start from! Can anyone here give a light? Any tips? Any advice? Every body had/has a start, isn't it? Thanks a lot for your time and cooperation (and *PATIENCE* too). best regards, Gustavo Rios -- Message of the day: The trouble with doing something right the first time is that nobody appreciates how difficult it was. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Netgear FA410 pccard ethernet?
On Wed, Nov 03, 1999 at 10:42:28AM -0500, Robert Swindells wrote: It is listed as a supported card in PAO. I have one as well but never got it to work. I haven't tried PAO yet as I have got a spare 3COM card, but it would be nice to be able to run at 100Mbps. I just installed PAO, and it now works fine. Thanks for everybody's help. -Guy To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Suggestion for servers running FreeBSD
Hello, We are thinking of getting new servers for our lab, and run FreeBSD on it. What kind of servers should we get, which will not cause too much headache, ie. can work reliablely? Any suggestion will be greatly appreciated! Cheers, -chen On Wed, 3 Nov 1999, Luoqi Chen wrote: :Thanks. It seems to me that for a filesystem, a block (or a fragment) is :the unit of I/O. Even if a single byte is modified, an entire block :probably consisting of multiple sectors must be written back to the disk. :As you said, there is no differnce whether we write this block one sector :at a time or in a single transfer. If so, I wonder whether the atomicity :of a sector I/O required by a directory file is necessary any more. : :-Zhihui The directory blocking is there for a different reason. Atomicy does not have much to do with it though perhaps it did at some point in the past. I think atomicity is still the reason. The basic block size of a directory is still a 512-byte sector, and chances are we might write directory blocks one sector at a time (4k/512 formatted fs), so we have to guarantee directory entries don't cross the 512-byte sector boundary. On a 8k/1k fs, you probably could get away with crossing the odd 512-byte sector boundary though. -lq 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
Re: aio Functions
On Tue, 2 Nov 1999, Ricardo Bernardini wrote: Hello list! I'm starting with aio functions (aio_read, aio_return, etc.), I've made them work with disk file I/O, now I'm trying with TCP sockets not with the same success. Does anyone know if it is posible to do what I'm trying? Or where to find more info about this function group? I'just read the man pages about them. Which version of FreeBSD are you using? Its best to be using -current from my experience. TCP sockets should work, but they'll be pretty crippled for certain kinds of uses (like trying to have an outstanding read on more than a couple dozen sockets, etc). I've got a set of patches that fix this and the fact that signals don't get issued for completion on certain types of requests. I'm hoping to get it committed, but feel free to contact me for the latest stuff until then. I just finished updating and consolidating my patches so they cleanly apply to -current of a week ago. Testing thus far appears promising--I'm balancing more than a few sockets and pushing 10MB/sec through them (disk to socket and the inverse). I killed the last bug I knew of this week (occasionally paniced under some wierd process shutdown conditions). I hope to try 1000 descriptors soon. -Chris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Linux* 2.2.x Driver inetl Etherexpress 1000
Matthew Jacob wrote: Yes, we know. Gee, the license terms look AWFULLY familiar. I'd like to think I had some long-lasting effect on the Intel legal department, but I doubt this was it. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC [EMAIL PROTECTED] http://softweyr.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: becoming part of FreeBSD Developer
I might suggest that development in FreeBSD has many faces.. those who go through the man pages and check that they accuratly describe the programs are as important as those who write new drivers. You could find some part of FreeBSD that has always annoyed you and decide to fix it.. this is how most work is done.. You do not need permission to fix anything. Though it is usually wise to ask first if someone else is already doing it, or if anyone wildly objects to your changes. regards, Julian On Wed, 3 Nov 1999, Gustavo V G C Rios wrote: Dear gentleman, i have been using free for the last 12 months! I have never done anything in terms of system development, so i decide it was the time to get more involved with FBSD development. In repect to this regard, i sent a mail to Mr. David Greenman, whose response was: "The first step is to get involved with the development community by subscribing to the FreeBSD mailing lists such as freebsd-arch and freebsd-hackers." So here i am. But the doubts keeps on! I have a pretty small knownledge about SO internals, but nothing close to what many of you have, what you wizards suggest me? I have no ideia on where to start from! Can anyone here give a light? Any tips? Any advice? Every body had/has a start, isn't it? Thanks a lot for your time and cooperation (and *PATIENCE* too). best regards, Gustavo Rios -- Message of the day: The trouble with doing something right the first time is that nobody appreciates how difficult it was. 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
Re: (forw) Reversing 32Upgrade package
Ron 'The InSaNe One' Rosson wrote: Is there anyway to reverse 32upgrade package after it has been installed on a 2.2.8-STABLE system. This is on a production box and rebuilding is not an option I have time to explore. If it's a production system you will have had backups from immediately before your upgrade, and reversing the upgrade will be a simple matter of restoring your backups. Why do you want to reverse it anyway? - mark Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: (forw) Reversing 32Upgrade package
On Thu, 04 Nov 1999, Mark Newton was heard blurting out: Ron 'The InSaNe One' Rosson wrote: Is there anyway to reverse 32upgrade package after it has been installed on a 2.2.8-STABLE system. This is on a production box and rebuilding is not an option I have time to explore. If it's a production system you will have had backups from immediately before your upgrade, and reversing the upgrade will be a simple matter of restoring your backups. Why do you want to reverse it anyway? - mark Well the custom software that is running on this box is only geared for 2.28 at the moment. Backup tapes do you know good if you are not sure what files got changed and how. Which is the reason for the question. TIA -- --- Ron Rosson ... and a UNIX user said ... The InSaNe One rm -rf * [EMAIL PROTECTED]and all was /dev/null and *void() --- The nice thing about Windows is: It does not just crash, it displays a dialog box and lets you press 'OK' first. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: aio Functions
In article [EMAIL PROTECTED], Christopher Sedore [EMAIL PROTECTED] wrote: I've got a set of patches that fix this and the fact that signals don't get issued for completion on certain types of requests. I'm hoping to get it committed, but feel free to contact me for the latest stuff until then. I just finished updating and consolidating my patches so they cleanly apply to -current of a week ago. Testing thus far appears promising--I'm balancing more than a few sockets and pushing 10MB/sec through them (disk to socket and the inverse). I killed the last bug I knew of this week (occasionally paniced under some wierd process shutdown conditions). I hope to try 1000 descriptors soon. That's great news! So have you gotten rid of some of these absurdly low fixed limits? vfs.aio.max_aio_per_proc: 32 vfs.aio.max_aio_queue_per_proc: 256 vfs.aio.max_aio_procs: 32 vfs.aio.max_aio_queue: 1024 vfs.aio.max_buf_aio: 16 And worst of all: #define AIO_LISTIO_MAX 16 John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "No matter how cynical I get, I just can't keep up."-- Nora Ephron To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: (forw) Reversing 32Upgrade package
On Wed, 3 Nov 1999, Ron 'The InSaNe One' Rosson wrote: On Thu, 04 Nov 1999, Mark Newton was heard blurting out: If it's a production system you will have had backups from immediately before your upgrade, and reversing the upgrade will be a simple matter of restoring your backups. Well the custom software that is running on this box is only geared for 2.28 at the moment. Backup tapes do you know good if you are not sure what files got changed and how. Which is the reason for the question. In that case the only sane thing to do is assume that every file on the box changed and rebuild it from scratch from the backups. Upgrading will touch nearly everything in /etc, /dev, /sbin/, /usr/bin/, /usr/sbin, /usr/lib, /modules, /usr/include, and so forth. It won't (or shouldn't...) touch antyhing in /usr/local, /home or in any filesystem not mentioned in hier(7). David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: (forw) Reversing 32Upgrade package
Is there anyway to reverse 32upgrade package after it has been installed on a 2.2.8-STABLE system. This is on a production box and rebuilding is not an option I have time to explore. If it's a production system you will have had backups from immediately before your upgrade, and reversing the upgrade will be a simple matter of restoring your backups. Why do you want to reverse it anyway? Well the custom software that is running on this box is only geared for 2.28 at the moment. Backup tapes do you know good if you are not sure what files got changed and how. Which is the reason for the question. The upgrade package is just that; a package. You can check what's in a package with pkg_info. You'll need access to a second 2.2.8 system to recover files that may have been overwritten. As a general rule, installing things blind on a production system is not a good idea. 8) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
kstat - an API for gathering kernel stats
I wrote kstat as a way to improve on the current BSD method of getting kernel statistics, which involves looking up a particular kernel symbol name and then getting the value from the symbol offset. This makes any performance monitoring tool or an application that gets kernel stats non-portable across different kernel versions if for some reason, the names of these variables happen to change. kstat derives some ideas from the Solaris kstat API, but is much simpler. It adds a new system call to the kernel. Any kernel module that wants to register a counter calls kstat_register, which makes an entry in the hash table, that maps the counter name to the address of the counter. A user program makes a system call with this string "cpu.system" to get the current value of user/system/nice time etc. A kernel module and a sample application can be downloaded from: http://members.home.net/adsharma/kstat.tar.gz Each system call currently costs a hash table lookup. A tool that may want to repeatedly get the value of the same counter over and over again may want to avoid that lookup everytime. I have some ideas on how to make that happen. Comments and suggestions are welcome. -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: kstat - an API for gathering kernel stats
On Wed, 3 Nov 1999, Arun Sharma wrote:
A user program makes a system call with this string "cpu.system" to get
the current value of user/system/nice time etc.
How is this different from doing:
# sysctl -a | grep load
vm.loadavg: { 0.15 0.09 0.04 }
Ideally we could have a syscall that could return the OID for a given name
to solve the portability and speed issues associated with doing repeated
lookups.
Seems like you've reinvented the wheel to me.
--
| Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD |
| [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever |
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
