From: Heiko Dudzus <heiko.dudzus@gmx.de>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] secstored output to /dev/cons
Date: Thu, 6 Jan 2005 00:22:40 +0100 [thread overview]
Message-ID: <c03620340d937fab8b5f43f99679bc4c@voidness.de> (raw)
In-Reply-To: <cca9b61fac6aa1bee3be3be4c1286eac@plan9.ucalgary.ca>
> if you could add a note to the man page and submit it as a patch it'll
> be much easier to find next time :)
>
> i am trying to remember how i created my /sys/log/secstore but i
> can't. there doesn't seem to be any discussion on 9fans...
Done.
But perhaps it would be nicer to do it like it is done with all the
other log files: presented empty in a vanilla install (regardless if
needed or not)?
next prev parent reply other threads:[~2005-01-05 23:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-05 20:11 Heiko Dudzus
2005-01-05 20:14 ` Charles Forsyth
2005-01-05 20:24 ` Heiko Dudzus
2005-01-05 21:31 ` Heiko Dudzus
2005-01-05 21:38 ` andrey mirtchovski
2005-01-05 23:22 ` Heiko Dudzus [this message]
2005-01-05 23:29 ` andrey mirtchovski
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=c03620340d937fab8b5f43f99679bc4c@voidness.de \
--to=heiko.dudzus@gmx.de \
--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).