done with pipe for single client-server-client
done with pipe for single client-server-client
Implemented single client server using pipes and execl command.
when i am trying to compile the kernel i am getting following error..
[root@vijay linux-2.6.3]# make menuconfig
HOSTCC scripts/fixdep
scripts/fixdep.c: In function ‘traps’:
scripts/fixdep.c:359:2: warning: dereferencing type-punned pointer will break strict-aliasing rules
scripts/fixdep.c:361:4: warning: dereferencing type-punned pointer will break strict-aliasing rules
HOSTCC scripts/kconfig/conf.o
HOSTCC scripts/kconfig/mconf.o
scripts/kconfig/mconf.c:91:21: error: static declaration of ‘current_menu’ follows non-static declaration
scripts/kconfig/lkc.h:63:21: note: previous declaration of ‘current_menu’ was here
make[1]: *** [scripts/kconfig/mconf.o] Error 1
make: *** [menuconfig] Error 2
completed compatibilty mode and byte mode with protocols.
In nibble mode data is transmitting successfully but there is prob with strobe pin…
When a program exits, it can return to the parent process a small amount of information about the cause of termination, using the exit status. This is a value between 0 and 255 that the exiting process passes as an argument to exit.
Normally you should use the exit status to report very broad information about success or failure. You can’t provide a lot of detail about the reasons for the failure, and most parent processes would not want much detail anyway.
There are conventions for what sorts of status values certain programs should return. The most common convention is simply 0 for success and 1 for failure. Programs that perform comparison use a different convention: they use status 1 to indicate a mismatch, and status 2 to indicate an inability to compare. Your program should follow an existing convention if an existing convention makes sense for it.
A general convention reserves status values 128 and up for special purposes. In particular, the value 128 is used to indicate failure to execute another program in a subprocess. This convention is not universally obeyed, but it is a good idea to follow it in your programs.
Warning: Don’t try to use the number of errors as the exit status. This is actually not very useful; a parent process would generally not care how many errors occurred. Worse than that, it does not work, because the status value is truncated to eight bits. Thus, if the program tried to report 256 errors, the parent would receive a report of 0 errors—that is, success.
i have implemente the lseek,thread synchronization ,semaphore ,completion ,spinlock,blocking io .
sir,
i have completed byte mode and the compatibility mode
Can anyone tell me what is the difference between i++ and ++i w.r.t compiler in C
compatible,nibble and byte modes are implemented with protocols.
Nibble mode has been implemented successfully with exact protocol.
completed the server client part but still getting problems with return or exit statements……
Can someone explain:
int y=10;
printf(“%d %d %d”,++y,y,++y);
answer is:
12 12 12
Both the modes have been implemented without nstrobe.
Amresh: work-out on array and string..
Gaurav :Completed 20qus of first assignment and string…
Sahil : work-out on array and string..
Anil : Completed first Assignment and work-out on string….
