Mihai Don??u mihai.do...@gmail.com wrote:
I don't think the kernel is the one that initializes the
0, 1 and 2 file descriptors (stdin, stdout and stderr).
Correct so far.
I think you have to open them yourself ...
No, the shell does it. That's how it is able to set up
pipes and redirection.
Charlie Kester wrote:
On Wed 11 Nov 2009 at 17:32:41 PST Charlie Kester wrote:
One more thing:
Notice that the system call number (or any other dword) should also be
pushed onto the stack before the int 80h.
The reason for this is given at the top of the page:
although the kernel is
On Wed, 11 Nov 2009 14:43:21 -0500, David Jackson norsta...@gmail.com wrote:
I am having great difficulty running a very simple assembler program
on FreeBSD on x86 in my efforts to learn some assembly programming on
FreeBSD. I have tried to compile the following with nasm, however i
get
I am having great difficulty running a very simple assembler program on
FreeBSD on x86 in my efforts to learn some assembly programming on
FreeBSD. I have tried to compile the following with nasm, however i get
nothing in response when I attempt to run this program:
section .data
I am having great difficulty running a very simple assembler program on
FreeBSD on x86 in my efforts to learn some assembly programming on
FreeBSD. I have tried to compile the following with nasm, however i get
nothing in response when I attempt to run this program:
section .data
On Wednesday 11 November 2009 21:43:21 David Jackson wrote:
I am having great difficulty running a very simple assembler program on
FreeBSD on x86 in my efforts to learn some assembly programming on
FreeBSD. I have tried to compile the following with nasm, however i get
nothing in response
On Wed 11 Nov 2009 at 11:43:21 PST David Jackson wrote:
I am having great difficulty running a very simple assembler program
on FreeBSD on x86 in my efforts to learn some assembly programming on
FreeBSD. I have tried to compile the following with nasm, however i
get nothing in response when I
On Wed 11 Nov 2009 at 17:32:41 PST Charlie Kester wrote:
One more thing:
Notice that the system call number (or any other dword) should also be
pushed onto the stack before the int 80h.
The reason for this is given at the top of the page:
although the kernel is accessed using int 80h, it
