2002Öйú£¨ÉϺ££©¹ú¼Ê¸øÅÅˮˮ´¦ÀíÕ¹ÀÀ»á
µÚÈý½ì 2002Öйú£¨ÉϺ££©¹ú¼Ê¸øÅÅˮˮ´¦ÀíÕ¹ÀÀ»á 2002Öйú£¨ÉϺ££©¹ú¼Ê»·±£¼¼ÊõÉ豸չÀÀ»á ×𾴵ĸ÷Ïà¹Øµ¥Î»£º ÄúºÃ£¡ Óɽ¨É貿ÐÅÏ¢ÖÐÐÄ¡¢Öйú»·¾³¿Æѧѧ»á¡¢ÉϺ£Êо»Ë®¼¼Êõѧ»á¡¢¶«ºÆ¼¯ ÍÅÉϺ£Íâ·þ¹ú¼ÊÕ¹ÀÀ¹ã¸æ¹«Ë¾µÈµ¥Î»Ö÷°ì£¬ÉϺ£ÖÐóչÀÀ·þÎñÓÐÏÞ¹«Ë¾³Ð°ì µÄ2002Öйú£¨ÉϺ££©¹ú¼Ê¸øÅÅˮˮ´¦ÀíÕ¹ÀÀ»á¼°2002Öйú£¨ÉϺ££©¹ú¼Ê»· ±£¼¼ÊõÉ豸չÀÀ»á½«ÓÚ2002Äê5ÔÂ15ÈÕ-17ÈÕÔÚÉϺ£ÊÀóÉ̳Ç¡Öؾٰ죬×÷ Ϊ½¨Éè¡¢»·±£Ö÷¹Ü²¿ÃÅÈ«Á¦Ö§³ÖÓëÖ÷°ìµÄÉϺ£¹ú¼Ê»·±£Ë®Õ¹Òѳɹ¦¾Ù°ìÁ½ ½ì£¬ÒÔÆä¹æÄ£´ó¡¢×¨ÒµË®×¼¸ß¡¢²ÎÕ¹³§É̶ࡢչ³ö²úƷжøÔÚÒµ½çÓ°ÏìÉîÔ¶¡¢ ÉùÓþ׿Öø¡£ ÖйúÈëÊÀ£¬È«Çò¾Û½¹×î¾ßDZÁ¦µÄÖйúÊг¡£¬±¾½ìÕ¹»áÏÖÒÑÎüÒýÁËÀ´×ÔÃÀ ¹ú¡¢º«¹ú¡¢ÈÕ±¾¡¢µÂ¹ú¡¢Òâ´óÀû¡¢·¨¹ú¡¢¼ÓÄôó¼°Öйų́ÍåµØÇøµÈ¹ú¼ÒÓëµØ Çø385¼Ò³§É̲ÎÕ¹£¬Õ¹³öÃæ»ý½ü9000ƽÃ×£¬Í¬Ê±Ö÷°ì»ú¹¹»¹½«ÑûÇëÏà¹ØÐÐÒµ ȨÍþÈËÊ¿¼°ÖªÃûÆóÒµ¾Ù°ìרÌⱨ¸æ»áºÍ¼¼Êõ½»Á÷»á¡£½ìʱ¹úÄÚÍâ»·±£¡¢Ë®ÐРҵרҵÂò¼ÒÔƼ¯Éê³Ç¡£ ±¾´ÎÕ¹»á½«³ÉΪÐÐÒµ²úÆ·¾º¼¼µÄÎę̀£¬´«µÝÊг¡ÐÅÏ¢ºÍ½»Á÷ÏȽø¼¼ÊõµÄ ´°¿Ú£¬Á¼»úÄѵã¬ÇÐĪ´íʧ£¡ »¶Ó¸÷Ïà¹Øµ¥Î»²Î¹Û¡¢²ÎÕ¹£¡ÎÒÃÇÆÚ´ýÄúµÄ²ÎÓë¼°Ö§³Ö£¡ ÉϺ£ÖÐóչÀÀ·þÎñÓÐÏÞ¹«Ë¾ Http:www.zhongmao.com.cn E-mail:[EMAIL PROTECTED] ÁªÏµµç»°£º021-54641713 ²ÎÕ¹¡¢²Î¹Û»ØÖ´ ÎÒµ¥Î»ÓÐÐËȤ²ÎÕ¹2002ÉϺ£¹ú¼Ê»·±£Ë®Õ¹£¬Çë¼Ä/´«ÕæÏêϸ×ÊÁÏ ÎÒµ¥Î»ÓÐÐËȤ²Î¹Û2002ÉϺ£¹ú¼Ê»·±£Ë®Õ¹£¬Çë¼Ä²Î¹Ûȯ ÕÅ µ¥Î»Ãû³Æ£º ÒµÎñ·¶Î§£º ÏêϸµØÖ·£º ÁªÏµÈË£º Óʱࣺ µç »°£º ´« Õ棺 E-mail£º To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: A few questions about a few includes
On Sun, 3 Mar 2002, Erik Trulsson wrote:
ETOn Sun, Mar 03, 2002 at 10:27:17AM -0700, Ian wrote:
ET
ET In sys/proc.h:
ET
ET /*
ET * pargs, used to hold a copy of the command line, if it had a sane
ET * length
ET */
ET struct pargs {
ET u_int ar_ref; /* Reference count */
ET u_int ar_length; /* Length */
ET u_char ar_args[0]; /* Arguments */
ET };
ET
ET This does indeed seem to make little or no sense. Could someone explain
ET this? Is ar_args supposed to be a pointer or what?
ET
ET This is a common technique for defining a structure which is some
ET descriptive information about an array of objects is followed by an
ET open-ended array of those objects. (In this case the objects are
ET characters.) The ar_args member of the structure gives a name to that
ET location in the structure without reserving any space (and thus when the
ET technique is used, there can only ever be one [0] member and it must be at
ET the end of the structure). You access the open-ended array of objects just
ET as you would any other array embedded within a structure, E.G.
ET instance-ar_args[n].
ET
ET Not all compilers support defining zero-length arrays like this. And that's
ET a pity; it's an incredibly useful technique, and the alternatives to it are
ET not nearly as elegant and generally involve ugly recasting of pointers.
ET
ETFor those compilers that don't support zero-length arrays one can still
ETuse the same trick but with a one-element array at the end of the
ETstruct. One just has to remember to that element into account when
ETallocating memory for the structure. Slightly uglier, but not much.
ET
ETIt might be worth mentioning that this trick is not actually allowed
ETaccording to the C standard and in principle invokes undefined
ETbehaviour. OTOH, AFAIK the trick does work on all existing compilers,
ETso while it is not standard-conforming it is quite portable.
My ISO-C draft copy allows in section 6.7.2.1 paragraph 2 the last member
of a structure to be an incomplete array type and paragraph 16 shows an
example. Was this removed from the final standard?
harti
--
harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
please review the manpage
Hello there! Excuse me if this is a wrong list for such submissions. A suggested manpage for EVENTHANDLER(9) is attached. It should be referenced from boot(9) instead of non-existent at_shutdown(9). at_shutdown(9) was retired even before 4.0-R, however, it's still referenced from boot(9) in -stable. By the way, is there any reason for at_fork/at_exec function not to be retired in favor of EVENTHANDLER_XXX macros? Regards, Alexey. -- - ) May the Sun and Water ( Regards, Alexey V. Neyman ) always fall upon you! ( mailto:[EMAIL PROTECTED] - EVENTHANDLER.9 Description: Troff document
Re: A few questions about a few includes
On Mon, Mar 04, 2002 at 10:29:18AM +0100, Harti Brandt wrote:
On Sun, 3 Mar 2002, Erik Trulsson wrote:
ETOn Sun, Mar 03, 2002 at 10:27:17AM -0700, Ian wrote:
ET
ET In sys/proc.h:
ET
ET /*
ET * pargs, used to hold a copy of the command line, if it had a sane
ET * length
ET */
ET struct pargs {
ET u_int ar_ref; /* Reference count */
ET u_int ar_length; /* Length */
ET u_char ar_args[0]; /* Arguments */
ET };
ET
ET This does indeed seem to make little or no sense. Could someone explain
ET this? Is ar_args supposed to be a pointer or what?
ET
ET This is a common technique for defining a structure which is some
ET descriptive information about an array of objects is followed by an
ET open-ended array of those objects. (In this case the objects are
ET characters.) The ar_args member of the structure gives a name to that
ET location in the structure without reserving any space (and thus when the
ET technique is used, there can only ever be one [0] member and it must be at
ET the end of the structure). You access the open-ended array of objects just
ET as you would any other array embedded within a structure, E.G.
ET instance-ar_args[n].
ET
ET Not all compilers support defining zero-length arrays like this. And that's
ET a pity; it's an incredibly useful technique, and the alternatives to it are
ET not nearly as elegant and generally involve ugly recasting of pointers.
ET
ETFor those compilers that don't support zero-length arrays one can still
ETuse the same trick but with a one-element array at the end of the
ETstruct. One just has to remember to that element into account when
ETallocating memory for the structure. Slightly uglier, but not much.
ET
ETIt might be worth mentioning that this trick is not actually allowed
ETaccording to the C standard and in principle invokes undefined
ETbehaviour. OTOH, AFAIK the trick does work on all existing compilers,
ETso while it is not standard-conforming it is quite portable.
My ISO-C draft copy allows in section 6.7.2.1 paragraph 2 the last member
of a structure to be an incomplete array type and paragraph 16 shows an
example. Was this removed from the final standard?
I think it is still there (and my draft copy says the same thing).
I was thinking about the original C89 standard which does not allow it
(and does not allow incomplete array types in structs). Guess I should
have said which standard I was referring to.
harti
--
harti brandt,
http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private
[EMAIL PROTECTED]
--
Insert your favourite quote here.
Erik Trulsson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Re: How to write code in FreeBSD
On Saturday 02 March 2002 09:41 am, Brian T. Schellenberger wrote: On Saturday 02 March 2002 06:57 am, Aleksander Rozman - Andy wrote: Hi ! I was wondering if there are any guidelines how to write code in FreeBSD. I have taken a look at several code of FreeBSD but each is written differently? Problem is I don't know which is preferred way. Reason I am asking this is that I am trying to add some code to kernel. Compile is OK, no error, no warning, but on link all variables defined with extern are marked as : undefined reference to 'variable', variable is extern and .h file which has it defined is included... Where can be the problem?? Another problem is that I get multiple definition error...how can I get over this. I got Andy to send his original code, and I believe that I've diagnosed the root of the problem: The code was assuming that KERNEL was defined when building the kernel (I gather that KERNEL is defined when building a Linux kernel), but under FreeBSD, it seems, KERNEL is *not* defined, but _KERNEL is defined instead. (Though I'm not sure whether it's defined under the same circumstances.) Even so I'm not sure that his code is perfectly correct ANSI C, technically speaking, since it then appears that it would wind up with multiple copies of the variables defined, but I'm pretty darn sure that gcc ld tolerate this just fine--the proximate cause of the difficulty lay in expecting KERNEL to be defined and having an #ifdef KERNEL check in the 'h' file that caused the definitions to never to be read. -- Brian T. Schellenberger . . . . . . . [EMAIL PROTECTED] (work) Brian, the man from Babble-On . . . . [EMAIL PROTECTED] (personal) ME -- http://www.babbleon.org http://www.eff.org -- GOOD GUYS -- http://www.programming-freedom.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: A few questions about a few includes
In message: [EMAIL PROTECTED]
Erik Trulsson [EMAIL PROTECTED] writes:
: I think it is still there (and my draft copy says the same thing).
: I was thinking about the original C89 standard which does not allow it
: (and does not allow incomplete array types in structs). Guess I should
: have said which standard I was referring to.
struct foo {
char array[0];
};
appears to be in C-99 but not C-89. If you have the draft, so far the
only thing I've noticed that is different between the draft and the
final standard is that there's 10-15 more footnotes in the final
standard than were in the final draft.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Re: A few questions about a few includes
On Mon, 4 Mar 2002, M. Warner Losh wrote:
MWLIn message: [EMAIL PROTECTED]
MWLErik Trulsson [EMAIL PROTECTED] writes:
MWL: I think it is still there (and my draft copy says the same thing).
MWL: I was thinking about the original C89 standard which does not allow it
MWL: (and does not allow incomplete array types in structs). Guess I should
MWL: have said which standard I was referring to.
MWL
MWLstruct foo {
MWL char array[0];
MWL};
MWL
MWLappears to be in C-99 but not C-89. If you have the draft, so far
MWLthe only thing I've noticed that is different between the draft
MWLand the final standard is that there's 10-15 more footnotes in the
MWLfinal standard than were in the final draft.
MWL
MWLWarner
This should be
struct foo {
char array[];
};
according to C-99, on which gcc2 barfs. Don't know, whether gcc3 can
handle this.
harti
--
harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Re: Re: A few questions about a few includes
On Mon, Mar 04, 2002 at 09:35:29AM -0700, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Erik Trulsson [EMAIL PROTECTED] writes:
: I think it is still there (and my draft copy says the same thing).
: I was thinking about the original C89 standard which does not allow it
: (and does not allow incomplete array types in structs). Guess I should
: have said which standard I was referring to.
struct foo {
char array[0];
};
appears to be in C-99 but not C-89. If you have the draft, so far the
only thing I've noticed that is different between the draft and the
final standard is that there's 10-15 more footnotes in the final
standard than were in the final draft.
Warner
Are you sure that is in C99?
What is allowed in C99 (but wasn't in C89) is
struct foo
{
int b;
char array[];
};
Note that you must have a 'normal' field before the incomplete array.
I don't think
char array[0];
is allowed in either of C89 or C99.
--
Insert your favourite quote here.
Erik Trulsson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Routing question, Routed using one interface (more info)
I'm making a new post to attach the network diagram in order to clarify my question. (fixed point font please) I have several bsd4.3 computers each with one NIC on a shared LAN as below: +-+ |10.1.1.1/24 | | +--+ | | | +-+ | | +-+ | |10.1.1.2/24 | | |10.2.2.2/24 +--+ | | | +-+ | | +-+ | |10.2.2.3/24 | | |10.3.3.3/24 +--+ | | | +-+ | | +-+ | |10.3.3.4/24 | | | +--+ | | +-+ Now I like to turn on Routed, and have the approperiate routes discovered. Then from the 10.1.1.1 computer I like to be able to run traceroute to the 10.3.3.4 computer and see the following: 10.1.1.1 - 10.1.1.2 -10.2.2.3-10.3.3.4 currently I've tried this, but the routing is not being discovered and the routing table remains unchanged. There are no default routes either. Can you tell me if this is possible? and if so what I need to do to get it to work? Hi All, I like to know why when I turn on ROUTED on my machines they don't discover the attached subnets to the link. The scenario is below: I' have several bsd computers each with one network card. All the computers sit on a shared Ethernet. I like to perform some routing simulations comparing ospf and rip. So I have setup the computers so that each NIC has several IP address aliases assigned. When I turn on ROUTED I see a few hello packets exchanged and very so often I see an IGMP multicast for the router discovery protocol. However, the routing tables remain as they were before I turnon ROUTED. So basically the aliased NIC IP addresses are not being advertised. Can you tell me how I can make routing work through these aliased addresses? Also I have addressed my computers in the 10.x.x.x range which is the private IP address range and not internet routable. Does ROUTED care about the range of addresses in use or all IP addresses are using in the routing table as valid routable addresses. Just wanted to make sure this wasn't my problem. Thanks in advance for taking the time to suggest solution, ~Koroush Saraf To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: periodic firewire max-out question
From: John Kozubik [EMAIL PROTECTED] I still do not yet own 63 firewire devices, and so, once again, I am wondering if anyone here has ever actually connected 128 devices to a Huh? How did you get from 63 devices to 128? I don't know of any multi-bus 1394 adapters on the consumer market. Adapters have multiple ports but all are on the same bus. I'd be curious to find one that actually has more than one bus. -James To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: A few questions about a few includes
Erik Trulsson [EMAIL PROTECTED] writes:
On Mon, Mar 04, 2002 at 09:35:29AM -0700, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Erik Trulsson [EMAIL PROTECTED] writes:
: I think it is still there (and my draft copy says the same thing).
: I was thinking about the original C89 standard which does not allow it
: (and does not allow incomplete array types in structs). Guess I should
: have said which standard I was referring to.
struct foo {
char array[0];
};
appears to be in C-99 but not C-89. If you have the draft, so far the
only thing I've noticed that is different between the draft and the
final standard is that there's 10-15 more footnotes in the final
standard than were in the final draft.
Warner
Are you sure that is in C99?
What is allowed in C99 (but wasn't in C89) is
struct foo
{
int b;
char array[];
};
Note that you must have a 'normal' field before the incomplete array.
I don't think
char array[0];
is allowed in either of C89 or C99.
Correct on all counts. I'll cite the letter of the law from C99 if
anybody really cares.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Re: A few questions about a few includes
Harti Brandt [EMAIL PROTECTED] writes:
This should be
struct foo {
char array[];
};
according to C-99, on which gcc2 barfs. Don't know, whether gcc3 can
handle this.
C-99 requires a fully specified type before the unspecified array (and
requires said array to be the last element in the structure). So this
example is *not* valid in C99, but the following would be:
struct foo {
int bar;
char array[];
};
[Which makes sense; it forces a structure to have a non-zero size.]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Intel 820 RNG
All, Apologies if this has been discussed before. The new Intel i820 motherboard chipset is due to ship with an on-board Random Number Generator (RNG)... are there any plans for us to support this, or does support already exist? thanks BMS To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
fish [continued]
Hi again, hackers, First of all, thanks a lot to those who gave me feedback about this little project. I've gathered ideas from several people and will implement them in the future. I specially liked Michael Lucas' idea about a drop down menu of possible values. Currently the parser is finished for the FreeBSD version, the NetBSD one still needs some minor fixes, and I hope to finish the callbacks of GTK frontend by tomorrow or wednesday, depending on how much spare time I can get. Haven't still started with the ncurses UI, that will be the next step. And once I have a first working prototype, my next idea is to move to the concept of groups: network interfaces, firewall, peripheals, you get the idea. I've setup a page were people interested can download the latest version and have a look at a pair of screenshots if they feel curious as what does it look like: http://energyhq.homeip.net/brain.html Still waiting for someone to come up with a cool name tho :) Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk FreeBSD - The power to serve! msg32353/pgp0.pgp Description: PGP signature
Re: fish [continued]
On Mon, Mar 04, 2002 at 10:53:57PM +0100, Miguel Mendez wrote: I've setup a page were people interested can download the latest version and have a look at a pair of screenshots if they feel curious as what does it look like: http://energyhq.homeip.net/brain.html one comment from the quick look at the screenshots. why bother having the 's around the strings? it would make more sense to me to just tack quotes on at the end when you're writing out the rc.conf file. other than that it looks cool though ;-) keep up the good work. Still waiting for someone to come up with a cool name tho :) wish i could help... i'm terrible at naming programs... -garrett -- garrett rooney Unix was not designed to stop you from [EMAIL PROTECTED] doing stupid things, because that would http://electricjellyfish.net/ stop you from doing clever things. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Intel 820 RNG
On Mon, 4 Mar 2002, Bruce M Simpson wrote: All, Apologies if this has been discussed before. The new Intel i820 motherboard chipset is due to ship with an on-board Random Number Generator (RNG)... are there any plans for us to support this, or does support already exist? thanks BMS I haven't had time to keep up with this, so please bear with me. Is the i820 actually a new chipset that includes the RNG? We've been having trouble getting boards that have the RNG capabilities, and I have been told by the person doing the research that Intel seemed to be dropping this feature from the newer chipsets. If not, then I'm most pleased to be corrected and would like some references that I can throw at someone until they find us the proper motherboards again for our product. But, back to the topic. We have taken the OpenBSD driver for the RNG on the i810 chipset (and some other i8x0 chipsets), and ported it to FreeBSD-4.4. We made some enhancements to get more of the available random data bandwidth. We want to clean them up a little and submit them as a PR, but have not had time to. If you're interested I can send you the patches and you can give them a try. Adrian -- [ [EMAIL PROTECTED] ] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Intel 820 RNG
But, back to the topic. We have taken the OpenBSD driver for the RNG on the i810 chipset (and some other i8x0 chipsets), and ported it to FreeBSD-4.4. We made some enhancements to get more of the available random data bandwidth. We want to clean them up a little and submit them as a PR, but have not had time to. If you're interested I can send you the patches and you can give them a try. Hi. Please send me what you have. Thanks! M -- o Mark Murray \_ O.\_Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Intel 820 RNG
But, back to the topic. We have taken the OpenBSD driver for the RNG on the i810 chipset (and some other i8x0 chipsets), and ported it to FreeBSD-4.4. We made some enhancements to get more of the available random data bandwidth. I ported the openbsd crypto stuff to -stable for the purpose of making the soekris vpn1211 card usable (Hifn 7951). As part of this I tied the RNG on the Hifn to /dev/random; all that was required was to add a call to inject the data as entropy (or so I believed). Sam To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Intel 820 RNG
Mark Murray wrote: But, back to the topic. We have taken the OpenBSD driver for the RNG on the i810 chipset (and some other i8x0 chipsets), and ported it to FreeBSD-4.4. We made some enhancements to get more of the available random data bandwidth. We want to clean them up a little and submit them as a PR, but have not had time to. If you're interested I can send you the patches and you can give them a try. Hi. Please send me what you have. I thought it was an add-on to the firmware hub rather than the 820 chipset proper. The firmware hubs seems to be just about everywhere these days on intel chipset motherboards.. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Intel 820 RNG
Mark Murray wrote: But, back to the topic. We have taken the OpenBSD driver for the RNG on the i810 chipset (and some other i8x0 chipsets), and ported it to FreeBSD-4.4. We made some enhancements to get more of the available random data bandwidth. We want to clean them up a little and submit them as a PR, but have not had time to. If you're interested I can send you the patches and you can give them a try. Hi. Please send me what you have. Agreed. Anything that stops the harvesting entropy from sitting in the interrupt processing path for the most important interrupts on the box can only be a good thing. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Realtime video capture/divx encoding (brooktree) beta testers required
Im looking for a few beta testers with Brooktree based capture cards to test out my modifications to mencoder and the brooktree device to enable realtime video playback and capture to divx (or any format really). Anyone interested with some technology background please drop me a line! -Crh Charles Henrich [EMAIL PROTECTED] http://www.sigbus.com:81/~henrich To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Realtime video capture/divx encoding (brooktree) beta testers required
On Monday 04 March 2002 07:47 pm, Charles Henrich wrote: Im looking for a few beta testers with Brooktree based capture cards to test out my modifications to mencoder and the brooktree device to enable realtime video playback and capture to divx (or any format really). Anyone interested with some technology background please drop me a line! -Crh Charles Henrich [EMAIL PROTECTED] http://www.sigbus.com:81/~henrich To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-multimedia in the body of the message I'd be interested, just tell me what I need to do to get your modifications working. -- Anish Mistry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: periodic firewire max-out question
typo. 63 is the number I intended in both cases. I am basically just inquiring as to the practical problems one might face when actually maxing out the spec, with 63 devices in one adaptor. You are correct - none of those multi-port adaptors actually have two buses. I am not sure if anyone has plans on a multi-bus adaptor. Since posting this question, I have received quite a bit of anecdotal evidence that suggests that actually having 63 devices on the chain at once is _very_ difficult. Most people report running into problems at around 20-30 devices. Power is also an issue, if the devices are bus-powered as opposed to wall-powered. - John Kozubik - [EMAIL PROTECTED] - http://www.kozubik.com On Mon, 4 Mar 2002, James wrote: From: John Kozubik [EMAIL PROTECTED] I still do not yet own 63 firewire devices, and so, once again, I am wondering if anyone here has ever actually connected 128 devices to a Huh? How did you get from 63 devices to 128? I don't know of any multi-bus 1394 adapters on the consumer market. Adapters have multiple ports but all are on the same bus. I'd be curious to find one that actually has more than one bus. -James 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: fish [continued]
On Mon, 4 Mar 2002, Garrett Rooney wrote: one comment from the quick look at the screenshots. why bother having the 's around the strings? it would make more sense to me to just perhaps the quotes would show up otherwise hidden spaces ? Regards, /\_/\ All dogs go to heaven. [EMAIL PROTECTED](0 0)http://www.alphaque.com/ +==oOO--(_)--OOo==+ | for a in past present future; do| | for b in clients employers associates relatives neighbours pets; do | | echo The opinions here in no way reflect the opinions of my $a $b. | | done; done | +=+ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
AW: httpd in malloc(): warning: recursive call (FreeBSD error??)
we moved the rewrite into the httpd.conf, this was the solution, works very well now! Thanks a lot for that Information guys! Ciao, Max -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]Im Auftrag von Thomas Hurst Gesendet: Samstag, 2. März 2002 14:30 An: [EMAIL PROTECTED] Betreff: Re: httpd in malloc(): warning: recursive call (FreeBSD error??) * Max David Krüper ([EMAIL PROTECTED]) wrote: I have a FreeBSD 4.5-STABLE box running, when i start apache first all works fine, but after like 3 minutes in the logfile i see this messages: httpd in free(): warning: chunk is already free httpd in free(): warning: recursive call httpd in malloc(): warning: recursive call httpd in malloc(): warning: recursive call [Fri Mar 1 19:49:16 2002] [alert] [client 195.93.64.xx] /usr/local/httpd/htdocs/qm-dev/.htaccess: RewriteRule: cannot compile regular expression 'F([0-9]+)(.htm(l)?)?' I've had lots of fun nuking Apache using mod_rewrite. It's can be fragile at times; the solution is usually to rewrite the regex. It's also a good idea to put it in httpd.conf on a production server, since .htaccess support is conciderably slower and more of a hack then anything. Also keep in mind with php embedded in the server, bugs in that and it's extensions (some of which are dodgy at the best of times, like XSLT) can show up as Apache errors. Try disabling it and seeing if it still happens (after mod_rewrite :) -- Thomas 'Freaky' Hurst - [EMAIL PROTECTED] - http://www.aagh.net/ - No problem is so formidable that you can't just walk away from it. 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
3.3 to 4.5 remote upgrade possible?
I am trying to remotely upgrade a 3.3-RELEASE box to 4.5-RELEASE. I upgraded the source tree with cvsup. I followed the instructions and the notes in UPGRADING, but I can't get the make buildword to complete without unresolved references. I then de-cvsup'd (to coin a phrase) to 3.5-RELEASE sources and did a buildworld and installworld, which went fine. I left the 3.3 kernel running, figuring the libs would turn the trick, but maybe this is not a good thing ? Trying to build 4.5 sources with the 3.5 libs installed showed no improvement. So, I decided to transfer the /usr/obj tree from a 4.5 box to the remote. machine. I then built a kernel and transferred the build directory to the remote box. Just being a cautious sort, I tried running a binary from the obj tree. It failed with a BRANDELF warning. Is this because I did not run 'mergemaster' after installing the 3.5 world? Is this Mission Impossible? I have no one at the site that can do this. If I say make installworld is the whole thing going to come to a grinding halt? -Jim Durham To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
4.5-RELEASE upgrade..didnt??
Ok..dumb question alert. (fair warning) I just did a 4.3 to 4.5 upgrade, and made sure the sys source was upgraded as well. Went in, and did a make on my config file from 4.3..and rebooted (made sure the new kernel was in / as well). Uname reports a 4.3 system..etc..etc..etc. What'd I miss? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Realtime video capture/divx encoding (brooktree) beta testers required
On Mon, 4 Mar 2002 16:47:57 -0800 Charles Henrich [EMAIL PROTECTED] wrote: CH Im looking for a few beta testers with Brooktree based capture cards to test CH out my modifications to mencoder and the brooktree device to enable realtime CH video playback and capture to divx (or any format really). Anyone interested CH with some technology background please drop me a line! Send it on - I'm still having no luck getting my ffmpeg grab from brooktree to sync properly (otherwise it works fine, AFAICT the bad sync is inherent in ffmpeg) - does your code sync properly ? PS: I am more interested in mpeg1 than DivX because with mpeg1 the stream can be watched as it is being made. -- C:WIN | Directable Mirrors The computer obeys and wins.|A Better Way To Focus The Sun You lose and Bill collects. | licenses available - see: | http://www.sohara.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
cannot get more than 32 PTYs in 4.4-RELEASE
In my kernel, I have: maxusers128 pseudo-device pty 128 In my /dev directory, I have used `sh MAKEDEV` to make all 256 /dev/pty files. They are all there, and all have correct major/minor numbers. I know I won't be using all 256 of them, but I just made them all anyway. In /etc/ptys, I didn't change anything, because all 256 pty entries are ALREADY in there: # Pseudo Terminals ttyp0 nonenetwork ttyp1 nonenetwork ... ttySu nonenetwork ttySv nonenetwork So those are all there. I have used `sysctl -a | grep maxuser` to verify that maxusers is indeed 128. BUT - if I log on via ssh and start screen, and start 31 new screen windows, then nobody else can log on to the system - I cannot create any more screen windows AND nobody else can ssh in - the machine has run out of ptys. I use `fstat` to inquire, and I am maxed out at exactly 32 ptys. SO THE question is, why am I stuck at 32 ptys ? I have done it all - everything that is in any doc or news post, and everything I was told to do here and on -hackers, and yet I am still stuck at 32 !!! Please tell me the secret lore for getting more than 32 ptys in 4.4-RELEASE. thanks, PT To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
