From: Maciej Hrebien <m_hrebien@wp.pl>
To: Harmeet Uppal <Harmeet_Uppal@KeaneIndia.com>
Cc: linux-assembly@vger.kernel.org, linux-assembly@mlists.in-berlin.de
Subject: Re: Need Some Linux Internal help
Date: Thu, 21 Aug 2003 16:56:32 +0200 [thread overview]
Message-ID: <3F44DDA0.5E270F77@wp.pl> (raw)
In-Reply-To: 8EA11405E59BD611BA7100104B93C26001EF5EEB@exdel01.del.mgsl.com
Harmeet Uppal wrote:
>
> I need some help on Linux internals where in the I can get some
> documentation on the Internals of (IPC handling Internal level) etc and
> needs and advantages etc.I am currently placed at a place where I have just
> no access to the Internet. I also need to understand the methods of
> implementation of various synchronization techniques.
If you are without the net the only recomendation is the literature. Any
book about the Linux kernel internals or internals of the Unix System or
any book about process communication in those systems and
synchronization like ie. semaphores or even the Linux kernel source
files may be useful for you.
> Could you kindly help
> me or put me through some one who can help me on this.
If you are newbie in this theme, you should read some book(s) first i
think. And if you will have more questions you may ask it on some
mailing lists like: linux-assembly@vger.kernel.org or
linux-assembly@mlists.in-berlin.de. I think the whole group of people in
there will help you better than me if you stuck on something serious.
Note also that some of the people subscribed to those lists enjoy their
vacation time right now ;)
> I know it really is bad to be without a google.
>
> Thanks and Regards,
> Harmeet Uppal
Regards,
--
Maciej Hrebien
parent reply other threads:[~2003-08-21 14:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <8EA11405E59BD611BA7100104B93C26001EF5EEB@exdel01.del.mgsl.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F44DDA0.5E270F77@wp.pl \
--to=m_hrebien@wp.pl \
--cc=Harmeet_Uppal@KeaneIndia.com \
--cc=linux-assembly@mlists.in-berlin.de \
--cc=linux-assembly@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.