First Turkish Conference on BSD Systems (BSDConTR'07)
Call for Papers
October 20 - 21, 2007
Marmara University, Goztepe Istanbul, Turkey
Sponsored by endersys Consultancy Ltd. (http://www.endersys.com)
We're proud to announce the first Turkish Conference on BSD
systems: BSDConTR.
Organized in
First Turkish Conference on BSD Systems (BSDConTR'07)
Call for Papers
October 20 - 21, 2007
Marmara University, Goztepe Istanbul, Turkey
Sponsored by endersys consultancy ltd. (http://www.endersys.com)
We're proud to announce the first of Turkish Conference on BSD
systems: B
On 2007-Apr-06 01:53:54 +0300, cihan <[EMAIL PROTECTED]> wrote:
>How can I convert c source code to plain binary file?
What do you mean by "plain binary"? From the context, it looks like
you want some sort of stand-alone executable but you don't say how
you intend to run it.
>But I give linker e
Hi all
How can I convert c source code to plain binary file?
gcc -s -o foo.S foo.c
as -o foo.o foo.S
ld -Ttext 0x0 -e main -s --oformat binary -o foo.bin foo.o
But I give linker error like a "undefined reference to putchar"
then I tried
ld -Ttext 0x0 -e main -s --oformat binary -o foo.bin
Using
http://lists.freebsd.org/pipermail/freebsd-bugs/2007-March/022753.html
I have been able to get my GPRS card to be recognized in
FreeBSD. However, the IRQ it has picked, seems to conflict with the
irq of the cardbus causing an interrupt storm. Is there a way to
make the card use a diff
"Kevin Sanders" <[EMAIL PROTECTED]> writes:
> I'm trying to gain a better understanding of how kqueue's work from the
> driver side. I've managed to glean enough information from the source of
> other drivers, but I'm having a problem in my own kernel module when it is
> unloaded. Specifically, w
In the last episode (Apr 05), Joe Marcus Clarke said:
> I noticed something weird with test(1) when I ran across a problem port
> Makefile. Our test(1) doesn't properly check to make sure there is an
> operand argument to unary operators like -f. For example:
>
> test -f
>
> Will print "TRUE" o
I noticed something weird with test(1) when I ran across a problem port
Makefile. Our test(1) doesn't properly check to make sure there is an
operand argument to unary operators like -f. For example:
test -f
Will print "TRUE" on FreeBSD. On Solaris, it will die:
/usr/bin/test[8]: test: argume
On Thu, 2007-04-05 at 03:12 -0400, Joe Marcus Clarke wrote:
> I noticed something weird with test(1) when I ran across a problem port
> Makefile. Our test(1) doesn't properly check to make sure there is an
> operand argument to unary operators like -f. For example:
>
> test -f
>
> Will print "T
On Wed, 4 Apr 2007, Coleman Kane wrote:
While it's true you can't run Linux binaries on Mac OS X, it's not for the
reason you're suggesting, and your statement regarding FreeBSD kernel code
in Mac OS X is simply incorrect. The Mac OS X kernel, XNU, contains
significant quantities of FreeBSD
Hello,
for learning about gdb macros
I looked through gdbinit-1.i386.
( or is there some secret gdb manual
that *explains* macros? :-)
The macros xp and xxp calculate
the number of possible arguments as:
((*(int*)$ebp)-(int)$ebp)/4-4
Let's see (assuming "char* ebp"):
*ebp : saved ebp from pr
I noticed something weird with test(1) when I ran across a problem port
Makefile. Our test(1) doesn't properly check to make sure there is an
operand argument to unary operators like -f. For example:
test -f
Will print "TRUE" on FreeBSD. On Solaris, it will die:
/usr/bin/test[8]: test: argume
12 matches
Mail list logo
