On Wed, Nov 2, 2011 at 4:56 PM, Alexander Best wrote:
> i sent the following message to freebsd-quaestions@ and got no answer. mybe it
> is better suited for freebsd-hackers@.
>
> hi there,
>
> i found hundreds of the following cases in the FreeBSD src:
>
> [...]
> struct periph_driver {
>
i sent the following message to freebsd-quaestions@ and got no answer. mybe it
is better suited for freebsd-hackers@.
hi there,
i found hundreds of the following cases in the FreeBSD src:
[...]
struct periph_driver {
periph_init_func_t init;
char*driver_n
On Mon, 31 Oct 2011 11:49:48 +0200 Kostik Belousov wrote:
KB> I think it is better to use sys/elf.h over the machine/elf.h.
KB> Please change the comment for PROC_AUXV_MAX to "Safety limit on auxv size".
KB> Also, it worth adding a comment saying that we are reading aux vectors
twice,
KB> f
On Wed, Nov 2, 2011 at 1:44 PM, Garrett Cooper wrote:
> On Wed, Nov 2, 2011 at 12:56 PM, Navdeep Parhar wrote:
>> I built a KLD with multiple firmware images, as shown here:
>>
>> KMOD=foo
>> FIRMWS= foo.bin:foo:1.0.0.0
>> FIRMWS+=bar.bin:bar:1.0.0.0
>> FIRMWS+= ...
>> .include
>>
>> "foo" is th
In the last episode (Nov 02), Dan Nelson said:
> In the last episode (Nov 02), Mark Saad said:
> > Hackers
> > What is going on here, if I run the following shell script, what is
> > the expected output . The script is named xxx
> >
> > #!/bin/sh
> > ps -ax | grep -v grep | grep xxx
> >
> > Here
On Wed, Nov 2, 2011 at 12:56 PM, Navdeep Parhar wrote:
> I built a KLD with multiple firmware images, as shown here:
>
> KMOD=foo
> FIRMWS= foo.bin:foo:1.0.0.0
> FIRMWS+=bar.bin:bar:1.0.0.0
> FIRMWS+= ...
> .include
>
> "foo" is the parent firmware and a firmware_get(foo) can autoload the
> KLD.
In the last episode (Nov 02), Mark Saad said:
> Hackers
> What is going on here, if I run the following shell script, what is
> the expected output . The script is named xxx
>
> #!/bin/sh
> ps -ax | grep -v grep | grep xxx
>
> Here is what I see
>
> # sh xxx
> 88318 p0 S+ 0:00.00 sh xxx
On Wed, Nov 2, 2011 at 1:37 PM, Garrett Cooper wrote:
> On Wed, Nov 2, 2011 at 1:28 PM, Mark Saad wrote:
>> Hackers
>> What is going on here, if I run the following shell script, what is
>> the expected output . The script is named xxx
>>
>> #!/bin/sh
>> ps -ax | grep -v grep | grep xxx
>>
>> He
On Wed, Nov 2, 2011 at 1:28 PM, Mark Saad wrote:
> Hackers
> What is going on here, if I run the following shell script, what is
> the expected output . The script is named xxx
>
> #!/bin/sh
> ps -ax | grep -v grep | grep xxx
>
> Here is what I see
>
>
> # sh xxx
> 88318 p0 S+ 0:00.00 sh x
On Wed, Nov 2, 2011 at 4:28 PM, Mark Saad wrote:
> Hackers
> What is going on here, if I run the following shell script, what is
> the expected output . The script is named xxx
>
> #!/bin/sh
> ps -ax | grep -v grep | grep xxx
>
> Here is what I see
>
>
> # sh xxx
> 88318 p0 S+ 0:00.00 sh x
On 11/02/2011 13:28, Mark Saad wrote:
> Hackers
> What is going on here, if I run the following shell script, what is
> the expected output . The script is named xxx
>
> #!/bin/sh
> ps -ax | grep -v grep | grep xxx
>
> Here is what I see
>
>
> # sh xxx
> 88318 p0 S+ 0:00.00 sh xxx
> 883
Hackers
What is going on here, if I run the following shell script, what is
the expected output . The script is named xxx
#!/bin/sh
ps -ax | grep -v grep | grep xxx
Here is what I see
# sh xxx
88318 p0 S+ 0:00.00 sh xxx
88320 p0 R+ 0:00.00 sh xxx
88321 p0 R+ 0:00.00 sh xxx
I built a KLD with multiple firmware images, as shown here:
KMOD=foo
FIRMWS= foo.bin:foo:1.0.0.0
FIRMWS+=bar.bin:bar:1.0.0.0
FIRMWS+= ...
.include
"foo" is the parent firmware and a firmware_get(foo) can autoload the
KLD. "bar" and the rest are available only if the KLD is loaded (by
whatever m
Excellent! Thanks for fixing that.
Lee Thomas
On Wed, 2 Nov 2011 11:01:22 +0100, Luca Pizzamiglio wrote:
Hi Lee,
On devel/gdb 7.3.1 there is big stability problem with threaded
application.
I experimented several segmentation faults using gdb 3.7.1
ports/162093 it's my mantainer-update PR t
Hi Lee,
On devel/gdb 7.3.1 there is big stability problem with threaded application.
I experimented several segmentation faults using gdb 3.7.1
ports/162093 it's my mantainer-update PR to solve this issue and it
closes the ports/157342 too.
You could already try it!
Regards
Luca Pizzamiglio
__
15 matches
Mail list logo