From: DervishD <raul@pleyades.net>
To: Linux Geek <bourne@toughguy.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Tar'ing /proc ???
Date: Fri, 17 Jan 2003 11:50:30 +0100 [thread overview]
Message-ID: <20030117105030.GE47@DervishD> (raw)
In-Reply-To: <3E26BB8D.7070601@ToughGuy.net>
Hi Linux Geek :)
> I have been getting strange errors when i was trying to tar my /proc .
> Are there any known issues/problems when we do such a thing ?
Yes, the files under the procfs are *not* real files. I don't think
that taring /proc/kcore is a good idea, for example ;))
> Is it supposed to work at all ?
Don't think so.
> There is no reason as to why i am doing this :-) , just wanted to try out.
;))) Do any try you want with linux: if you don't do it as root,
you won't damage anything :))
Raúl
prev parent reply other threads:[~2003-01-17 11:03 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
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 [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=20030117105030.GE47@DervishD \
--to=raul@pleyades.net \
--cc=bourne@toughguy.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox