|
Grex > Coop8 > #48: Should we put old agoras on-line? | |
|
| Author |
Message |
popcorn
|
|
Should we put old agoras on-line?
| 
Apr 7 17:02 UTC 1996 |
Would it be OK to put the old agora archives on-line, as read-only
conferences, now that we have more disk space?
Also, does anybody out there have a copy of Agora 7 or Kitchen 1?
Thanks!
|
| 54 responses total. |
scott
|
|
response 1 of 54:
|
Apr 7 17:45 UTC 1996 |
I think it would be wonderful to put the old agoras on line. Shouldn't be
a problem to make them read-only, since they can be FW'ed by cfadm and all
the items frozen.
What kind of naming system should be used? By number, or have some
year/season scheme? (yes, I'm aware that with aliases both are possible ;)
|
ajax
|
|
response 2 of 54:
|
Apr 7 18:04 UTC 1996 |
Sounds good to me too, though I'm wondering: how much disk space is free
on the partition they'd be restored to, and how much space do they take?
|
nephi
|
|
response 3 of 54:
|
Apr 7 19:10 UTC 1996 |
Having the old Agoras online would be So Cool! (I'd especially like to see
Agora 1, and Co-op 1, myself . . . make that *especially*.)
|
davel
|
|
response 4 of 54:
|
Apr 7 21:26 UTC 1996 |
I have a few more technical issues in mind, which I'm mailing to Valerie since
I don't know if they have merit.
|
mta
|
|
response 5 of 54:
|
Apr 7 21:35 UTC 1996 |
I like the idea!
|
kerouac
|
|
response 6 of 54:
|
Apr 7 21:42 UTC 1996 |
yeah, returning the old agoras and/or old coops is a terrific idea.
Does anyone have portions of the old sex conf downloaded? There were
some really good items in it as I recall
This also makes the storage conf idea more manageable because items from
agora (and coop?) would always be on-line in some self-contained form
and wouldnt have to be linked, leaving that conf for items from the other
confs
|
scott
|
|
response 7 of 54:
|
Apr 7 22:05 UTC 1996 |
In general, FW's shouldn't be killing items that much anyway. In retrospect,
selena should have asked for a restart of HSex instead of just killing all
the items, but I don't think anybody thought of that at the time.
|
nephi
|
|
response 8 of 54:
|
Apr 7 22:13 UTC 1996 |
(Don't ya just love that 20/20 hindsight? 8^)
|
kerouac
|
|
response 9 of 54:
|
Apr 7 22:30 UTC 1996 |
actually, couldnt someone upload the old sex conf from the tapes?
|
popcorn
|
|
response 10 of 54:
|
Apr 7 23:39 UTC 1996 |
Good point....
|
kerouac
|
|
response 11 of 54:
|
Apr 7 23:54 UTC 1996 |
what was the very first conf on grex? Was it agora? Might be
interesting to see the very first posts
|
popcorn
|
|
response 12 of 54:
|
Apr 8 00:17 UTC 1996 |
*That's* one I'd very much like to locate and put on-line. There was a
conference where the founders did some set-up stuff, even before the first
Agora. It was shut down when Grex opened to the public and Agora 1 opened.
I dunno if anybody has a copy of it. It would be cool to have it on-line.
It's got stuff like founders debating how the item and response separators
should look -- a topic that got a lot of attention before Grex went on-line
to the public, and then never again afterward, thank goodness! None of
the founders really liked the item and response separators we ended
up with, but we all agreed that we had found something we could live with.
And anyway most the founders use their own item and response separator
definitions, rather than the system-wide ones.
|
albaugh
|
|
response 13 of 54:
|
Apr 8 05:12 UTC 1996 |
If space *were* an issue in returning archived conferences to read-iness :-)
I propose, at the tradeoff of access time, some way to keep the responses
compressed, and dynamically decompress them as readers request 'em. (I am
certain this is not being done already for picospan normal, but if it is,
please flame me! :-)
|
scott
|
|
response 14 of 54:
|
Apr 8 10:55 UTC 1996 |
Disk space is pretty cheap. On the Sun3 we had an operating system problem
that *hated* big disks, so that we were losing files all the time. On the
Sun4 here we don't have that problem, so we can set up a big /bbs partition
without being too worried about it.
|
davel
|
|
response 15 of 54:
|
Apr 8 12:07 UTC 1996 |
Picospan is *not* using compression. You can read the raw files if you
prefer to do it that way, with cat or more or whatever. (They're named
/bbs/<confname>/_item#. The conference name may not be what you expect, so
you may have to look around. (For example, as I'm reading this item it's
/bbs/coop8/_48))
|
steve
|
|
response 16 of 54:
|
Apr 8 13:41 UTC 1996 |
I think this would be a neat thing to do. I'll bet that all the
previous agora's and coop's could fit into less than 150M. These days,
with disk being about $0.20/megabyte, it wouldn't cost much to keep
them around.
|
arthurp
|
|
response 17 of 54:
|
Apr 8 20:17 UTC 1996 |
I agree. I would love to see what went on here before I found you. :)
|
abchan
|
|
response 18 of 54:
|
Apr 9 00:15 UTC 1996 |
Good idea.
|
carson
|
|
response 19 of 54:
|
Apr 9 01:06 UTC 1996 |
Can PicoSpan do read-only?
The test conference has a lot of history left. It's the only conference
off-hand I can think of that really does. Oh, wait, the pseudo conference
does too.
|
scg
|
|
response 20 of 54:
|
Apr 9 05:34 UTC 1996 |
As does the History conference, I think.
(serously)
|
nephi
|
|
response 21 of 54:
|
Apr 9 07:33 UTC 1996 |
Regarding #19:
There are a couple of ways that the conferences could be made read-only.
First, is that all the items could be frozen. Second is that all the files
that make up the items (or perhaps the directory of the conference, itself)
could be permed to read-only.
|
scott
|
|
response 22 of 54:
|
Apr 9 11:04 UTC 1996 |
I had been wondering (but forgetting to ask) how to prevent people from adding
new items to a conference full of frozen items.
Marcus, would it be a problem for PicoSpan to make a conference directory
read-only? Let's assume that there isn't an FW to worry about.
|
remmers
|
|
response 23 of 54:
|
Apr 9 11:21 UTC 1996 |
Offhand I'd think that making the conference directory r-xr-xr-x
(i.e. no write permission) would prevent new items from being
entered.
|
davel
|
|
response 24 of 54:
|
Apr 9 11:41 UTC 1996 |
Wouldn't that also prevent items from being linked?
|