Sponsored Content
Top Forums UNIX for Dummies Questions & Answers What i have to do to b'com UA?? Post 302336520 by durden_tyler on Wednesday 22nd of July 2009 09:30:29 AM
Old 07-22-2009
Quote:
Originally Posted by ezee
...
But still I am unaware that how should i prepare my system to run UNIX, as it is most essential to get touch of UNIX. I am presently running 2 OS i.e UBUNTU x64 and Windows 7 x64.
...
Well, Linux is fun to learn as well ! And most distros have a huge fan following with dedicated question/answer forums for your help.

About how to prepare your system to run Unix, you could check out FreeBSD or Solaris and replace the Ubuntu in your dual boot system by one of these Unices. A simple google search will show several links to installation steps. (The simplest approach would be to just wipe out Windoze altogether !)

Quote:
...
I want to achieve practical knowledge....i don't want to learn boring theory contents.
...
Achieving practical knowledge entails learning boring theory contents. One classic Unix book for newbies is "The Unix Programming Environment" by Brian Kernighan and Rob Pike.

HTH,
tyler_durden
 
iv_timer(3)						    ivykis programmer's manual						       iv_timer(3)

NAME
iv_timer_register, iv_timer_unregister, iv_timer_registered - deal with ivykis timers SYNOPSIS
#include <iv.h> struct iv_timer { struct timespec expires; void *cookie; void (*handler)(void *); }; void IV_TIMER_INIT(struct iv_timer *timer); void iv_timer_register(struct iv_timer *timer); void iv_timer_unregister(struct iv_timer *timer); int iv_timer_registered(struct iv_timer *timer); DESCRIPTION
The functions iv_timer_register and iv_timer_unregister register, respectively unregister, a timer with the current thread's ivykis event loop. iv_timer_registered on a timer returns true if that timer is currently registered with ivykis. When a timer that is registered becomes 'ready', due to the current system clock value becoming greater than or equal to the timer's ->expires member field, the callback function specified by ->handler is called in the thread that the timer was registered in, with ->cookie as its first and sole argument. When this happens, the timer is transparently unregistered. The application is allowed to change the ->cookie and ->handler members at any time. The application is not allowed to change the ->expires member while the timer is registered. A given struct iv_timer can only be registered in one thread at a time, and a timer can only be unregistered in the thread that it was reg- istered from. There is no limit on the number of timers registered at once. See iv_examples(3) for programming examples. SEE ALSO
ivykis(3), iv_examples(3) ivykis 2010-08-15 iv_timer(3)
All times are GMT -4. The time now is 03:00 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy