From: Steve Reid <sreid@sea-to-sky.net>
To: Andrej Borsenkow <Andrej.Borsenkow@mow.siemens.ru>
Cc: Vlad <tmd@tmd.df.ru>, zsh-users@sunsite.auc.dk
Subject: Re: HOW do i..
Date: Wed, 27 Dec 2000 14:32:46 -0800 [thread overview]
Message-ID: <20001227143246.A64501@grok.bc.hsia.telus.net> (raw)
In-Reply-To: <000001c06fd7$1134f930$21c9ca95@mow.siemens.ru>; from Andrej Borsenkow on Wed, Dec 27, 2000 at 10:31:46AM +0300
On Wed, Dec 27, 2000 at 10:31:46AM +0300, Andrej Borsenkow wrote:
> This can't be done, sorry. To save history entries in a file, this file should
> be user-writable. It does not matter, whom this file belongs to. History file
> is written (if at all) after every command. It means, user can edit it at any
> time and remove any entries. This applies to any logging.
Some operating systems allow you to set files append-only. For example,
under FreeBSD (and I think all 4.4-derived BSDs) the command "chflags
uappnd [file]" will set a file append-only, and only the owner or
superuser can remove the flag. "chflags sappnd [file]" and only the
superuser can remove the flag, and only if kern.securelevel is less
than one. I believe Linux has similar functionality.
I don't know whether or not this will work with the history mechanism.
If it can be set to append each line one at a time without trying to
re-write the entire file then it should work.
prev parent reply other threads:[~2000-12-27 22:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.BSF.4.21.0012261832580.18605-100000@tmd.df.ru>
2000-12-27 7:31 ` Andrej Borsenkow
2000-12-27 16:01 ` Vlad
2000-12-27 16:08 ` Thomas Köhler
2000-12-28 11:27 ` Andrej Borsenkow
2000-12-27 22:32 ` Steve Reid [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=20001227143246.A64501@grok.bc.hsia.telus.net \
--to=sreid@sea-to-sky.net \
--cc=Andrej.Borsenkow@mow.siemens.ru \
--cc=tmd@tmd.df.ru \
--cc=zsh-users@sunsite.auc.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).