All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mikado <mikado4vn@gmail.com>
To: Amit Luniya <amit_31_08@yahoo.co.in>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Help related to socket creation in kernel space
Date: Sun, 26 Mar 2006 00:30:44 +0700	[thread overview]
Message-ID: <44257E44.70302@gmail.com> (raw)
In-Reply-To: <20060325050910.25509.qmail@web8705.mail.in.yahoo.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Amit Luniya wrote:
> Hello sir,
>       I am final year student of comp. engg. from pune
> university. My project is hibernation in network
> environment. Existing utility of hibernation using
> "swsusp.c" does not support ping operation or any
> other n/w related services after resume. 
>   Tell me whether could we create socket in code of
> resume in such a way that we can get image back from
> server? As ping is application layer program does not
> support operation after resume , so could we do
> creation of socket and write kernel level network
> program in resume process and can communicate with
> server?
>  We are working on linux kernel 2.6.14.5 .
> Please help us as we are hang over our project.
> Have a good day sir.....

And the last thing, I don't know if network codes is legal in resume
process or not.

Mikado.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEJX5ENWc9T2Wr2JcRAsheAJ94lPaw0Gn3B+D5JxyRYFapf6n3TQCg0GQX
Br6DYoO+f6w+rE+c3cZ4pWY=
=zYv4
-----END PGP SIGNATURE-----

      parent reply	other threads:[~2006-03-25 17:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-25  5:09 Help related to socket creation in kernel space Amit Luniya
2006-03-25 17:24 ` Mikado
2006-03-25 17:30 ` Mikado [this message]

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=44257E44.70302@gmail.com \
    --to=mikado4vn@gmail.com \
    --cc=amit_31_08@yahoo.co.in \
    --cc=linux-kernel@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.