From: Adam Thornton <athornton@gmail.com>
To: Al Kossow <aek@bitsavers.org>, tuhs@minnie.tuhs.org
Subject: Re: [TUHS] bitsavers.org down?
Date: Sat, 18 Jan 2020 13:35:17 -0700 [thread overview]
Message-ID: <D54CF1F7-200F-4AC4-8BA6-515DC23E9403@gmail.com> (raw)
In-Reply-To: <742d2a1f-c794-e2d4-4e21-c07d8e5db60c@bitsavers.org>
So…that’s not a lot of archive, so I’m guessing that it’s outbound bandwidth that will be the driving cost. But even that…how popular is it _really_ ?
It seems like, given the nature of the collection, it might not be hard to persuade one of the cloud providers into discounted rates for hosting, although…it’s so small that that might not work, because that little data, well, you’re not a customer big enough to have a Google or Amazon rep.
I’ll put out some feelers. Rough bandwidth data, if we can figure out some way to find it, would be good to have.
Adam
> On Jan 18, 2020, at 1:24 PM, Al Kossow <aek@bitsavers.org> wrote:
>
>
> On 1/18/20 12:19 PM, arnold@skeeve.com wrote:
>
>> Perhaps some sort of crowd-funding would let you continue running things?
>>
>
> Let's see what happens with the server first.
> I have a copy of the most recent data, and the mirrors are all still there.
> I've asked that we disable the rsyncs until we can do
> a fixity check.
>
> I have no idea how much bandwith is used. The archive is about 300gb
>
next prev parent reply other threads:[~2020-01-18 20:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 20:06 Warner Losh
2020-01-17 21:41 ` Gregg Levine
2020-01-17 22:02 ` Warner Losh
2020-01-17 23:24 ` Tomasz Rola
2020-01-18 18:20 ` Al Kossow
2020-01-18 20:04 ` Michael Kjörling
2020-01-18 20:13 ` Al Kossow
2020-01-18 20:19 ` arnold
2020-01-18 20:24 ` Al Kossow
2020-01-18 20:33 ` Jim Geist
2020-01-18 20:35 ` Adam Thornton [this message]
2020-01-18 20:53 ` Steve Nickolas
2020-01-18 21:04 ` Adam Thornton
2020-01-18 21:22 ` Toby Thain
2020-01-18 21:31 ` Michael Kjörling
2020-01-18 20:37 ` Toby Thain
2020-01-18 21:56 ` Tomasz Rola
2020-01-18 22:04 ` Al Kossow
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=D54CF1F7-200F-4AC4-8BA6-515DC23E9403@gmail.com \
--to=athornton@gmail.com \
--cc=aek@bitsavers.org \
--cc=tuhs@minnie.tuhs.org \
/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).