9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] cpu server
Date: Mon,  9 Feb 2004 11:49:30 -0700	[thread overview]
Message-ID: <2567a7621663a382a760af64af957496@plan9.ucalgary.ca> (raw)
In-Reply-To: <6ea38d157a7cac487b3ebb0ba8467d6c@vitanuova.com>

>> put the wiki in a replica and you'll get updates unformation
>> automagically :)
>
> well... if wikifs provided date stamps.
>
>> I'm looking at the wikifs right now and it looks like there's enough
>> timestamps there to make such a script easy to write.
>
> to me, it looks as if wikifs doesn't maintain modification times
> or Qid version numbers.
>
> maybe that's the easiest modification to make;
> then a simple "ls -lt" would go a long way...

not at the top-level directory but on the ones underneath it does:

this ugly piece tells me the directories changed in the past week:

	#!/bin/rc

	rfork en
	ramfs

	test -e /srv/wiki || srv 'net!plan9.bell-labs.com!wiki' wiki || exit

	mount -c /srv/wiki /mnt/wiki
	cd /mnt/wiki

	for (i in *) {
		for(j in $i/*) {
				if(test '(' -d $j ')' -a '(' ! $j -older 7d ')')
					echo $i # or echo $j to see the actual timestamp
			}
		}
	}

if you run it you'll see at least two (so far) -- [dj]'s_jedimaters and grumpybear

both have nothing to do with plan9 :)



  reply	other threads:[~2004-02-09 18:49 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-07  0:24 vdharani
2004-02-06 22:50 ` Jim Choate
2004-02-07  3:41   ` Bruce Ellis
2004-02-07 14:48     ` Jim Choate
2004-02-07 15:21       ` Bruce Ellis
2004-02-07 16:05         ` Jim Choate
2004-02-07 19:54           ` Charles Forsyth
2004-02-07 22:26             ` a
2004-02-07 23:16               ` andrey mirtchovski
2004-02-09 17:47                 ` rog
2004-02-09 18:19                   ` andrey mirtchovski
2004-02-09 18:43                     ` rog
2004-02-09 18:49                       ` andrey mirtchovski [this message]
2004-02-09 18:49                     ` rog
2004-02-09 18:50                       ` andrey mirtchovski
2004-02-09 19:32                     ` 9nut
2004-02-09 18:44                       ` andrey mirtchovski
2004-02-10  1:38                     ` Kenji Okamoto
2004-02-10  1:40                       ` David Presotto
2004-02-10  1:50                       ` boyd, rounin
2004-02-10  1:11                         ` andrey mirtchovski
2004-02-10  3:03                           ` Lyndon Nerenberg
2004-02-10  5:00                           ` Geoff Collyer
2004-02-11  3:14                             ` Jack Johnson
2004-02-08  1:04               ` Taj Khattra
2004-02-08  1:20             ` Jim Choate
2004-02-08  2:56               ` Bruce Ellis
2004-02-08  2:40           ` Bruce Ellis
2004-02-07  8:18   ` andrey mirtchovski
2004-02-07 11:12     ` Bruce Ellis
2004-02-07 11:33     ` a
2004-02-07 13:30     ` boyd, rounin
2004-02-07 13:38     ` boyd, rounin
2004-02-07 14:51     ` Jim Choate
  -- strict thread matches above, loose matches on Subject: below --
2007-12-28  3:09 [9fans] CPU Server Joshua Wood
2007-12-22 23:12 "Rodolfo \"kix\" Garci­a"
2007-12-22 23:15 ` Iruata Souza
2007-12-23  3:13 ` John Soros
2007-12-23  3:35   ` erik quanstrom
2007-12-27 16:16     ` "Rodolfo \"kix\" Garci­a"
2007-08-15 22:13 Rodolfo (kix)
2007-08-16  1:26 ` geoff
2007-08-16 13:18   ` rob
2007-08-16 13:29     ` erik quanstrom
1998-07-13 15:46 Franklin

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=2567a7621663a382a760af64af957496@plan9.ucalgary.ca \
    --to=mirtchov@cpsc.ucalgary.ca \
    --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).