From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] rc - how to...
Date: Fri, 13 Sep 2002 16:09:56 +0200 [thread overview]
Message-ID: <4b18fee62c881bde79af19a33ac1b46a@plan9.escet.urjc.es> (raw)
If the input contains '; rm -rf *', I go and kill the user (not the
process). In a finite number of steps you get good input files.
next reply other threads:[~2002-09-13 14:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-13 14:09 Fco.J.Ballesteros [this message]
2002-09-14 0:16 ` Jim Choate
-- strict thread matches above, loose matches on Subject: below --
2002-09-13 13:50 rog
2002-09-13 8:01 Fco.J.Ballesteros
2002-09-12 14:42 rog
2002-09-12 14:10 Russ Cox
2002-09-12 14:03 steve.simon
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=4b18fee62c881bde79af19a33ac1b46a@plan9.escet.urjc.es \
--to=nemo@plan9.escet.urjc.es \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).