public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Linux Geek <bourne@ToughGuy.net>
To: root@chaos.analogic.com
Cc: Maciej Soltysiak <solt@dns.toxicfilms.tv>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Tar'ing /proc ???
Date: Thu, 16 Jan 2003 20:02:26 +0530	[thread overview]
Message-ID: <3E26C27A.7040107@ToughGuy.net> (raw)
In-Reply-To: Pine.LNX.3.95.1030116091326.4430A-100000@chaos.analogic.com

>
>
>the read. The result is a deadlock. Since `cat` or `cp` use
>small blocks and never have to call the kernel for additional
>resources, you can use them to get a snapshot. 
>  
>
Cool , Understood now ! . Thanks a lot for the time.

>  
>



  reply	other threads:[~2003-01-16 14:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-16 14:02 Tar'ing /proc ??? Linux Geek
2003-01-16 14:04 ` Richard B. Johnson
2003-01-16 14:06   ` Maciej Soltysiak
2003-01-16 14:20     ` Richard B. Johnson
2003-01-16 14:32       ` Linux Geek [this message]
2003-01-16 16:30     ` Jesse Pollard
2003-01-16 14:20   ` Linux Geek
2003-01-16 14:25     ` Richard B. Johnson
2003-01-17 10:50 ` DervishD

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=3E26C27A.7040107@ToughGuy.net \
    --to=bourne@toughguy.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.com \
    --cc=solt@dns.toxicfilms.tv \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox