9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] factotum & invalid entries
Date: Mon,  7 Feb 2005 12:05:09 +0200	[thread overview]
Message-ID: <2872b3cbd27d48bc556bc9be60560d38@proxima.alt.za> (raw)
In-Reply-To: <d27a7e748cad46f195041c57a651ad70@ar.aichi-u.ac.jp>

> If factotum automatically changed
> 	key proto=p9sk1 dom=proxima.alt.za user=lucio !password?
> 	disabled key proto=p9sk1 dom=outside.plan9.bell-labs.com user=lucio
> !password?
> when it know the list is useless, you can add
> 	key proto=p9sk1 dom=outside.plan9.bell-labs.com user= proxima
> !password?
> at the place of disabled entry. this is what you desire.

It's not what I desire: I don't want erroneous records in the factotum
database and I fail to see why anyone else would.  It solves a
non-existent problem, as deleting the record has the same effect.

> What is the problem?

Ugliness?  Note that the record is the most recently added record, so
the sequence is not affected.

> If factotum have deleted erroneous record then factotum put next record
> only at the end.  If order is matter this make a problem.

But factotum always did that, and it's precisely what I would do
manually.  As I mentioned, the sequence is not altered, nor should it
really matter if it was altered.

++L



  reply	other threads:[~2005-02-07 10:05 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-06  2:45 YAMANASHI Takeshi
2005-02-06 16:12 ` Russ Cox
2005-02-06 20:00   ` Tiit Lankots
2005-02-07  5:25   ` Lucio De Re
2005-02-07  5:42     ` arisawa
2005-02-07  6:03       ` Lucio De Re
2005-02-07  6:47         ` arisawa
2005-02-07  7:26           ` Lucio De Re
2005-02-07  8:09             ` arisawa
2005-02-07  8:55               ` Lucio De Re
2005-02-07  9:15                 ` arisawa
2005-02-07 10:05                   ` Lucio De Re [this message]
2005-02-08  5:12                     ` Russ Cox
2005-02-08 16:36                       ` rog
2005-02-08 16:42                         ` Russ Cox
2005-02-08 16:55                           ` Lucio De Re
2005-02-08 16:51                             ` rog
2005-02-08 16:52                             ` Devon H. O'Dell
2005-02-08 17:08                               ` Lucio De Re
2005-02-08 17:10                                 ` rog
2005-02-13 20:03 ` Russ Cox
  -- strict thread matches above, loose matches on Subject: below --
2005-02-14  2:35 YAMANASHI Takeshi
2005-02-14  3:42 ` Russ Cox
2005-02-04  9:31 [9fans] netpbm C H Forsyth
2005-02-05 18:26 ` [9fans] factotum & invalid entries Tiit Lankots
2005-02-05 20:12   ` Russ Cox

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=2872b3cbd27d48bc556bc9be60560d38@proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --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).