From: "Kelly Prescott" <prescott@deltav.org>
To: <tyler@tysdomain.com>,
"'Speakup is a screen review system for Linux.'"
<speakup@braille.uwo.ca>
Subject: RE: dedicated servers?
Date: Mon, 16 Jan 2012 13:11:33 -0600 [thread overview]
Message-ID: <000001ccd482$aa11c4f0$fe354ed0$@org> (raw)
In-Reply-To: <4F146C9D.3080700@tysdomain.com>
Use aws.amazon.com or rackspace.com
Amazon has the lowest entry price.
If you need more details, let me know.
-----Original Message-----
From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca]
On Behalf Of Littlefield, Tyler
Sent: Monday, January 16, 2012 12:30 PM
To: Speakup is a screen review system for Linux.
Subject: dedicated servers?
Hello all:
I'm currently with linode and arpnetworks for my linux and bsd systems
respectively.
I'm running into an issue though; I like having a spare linode for testing,
but what I really need is a box with a couple gigs of ram and decent storage
for what I'm doing. I'm currently running OpenVPN, email, web and a couple
other main services off my main server, and there will be more eventually.
My stoarage space is limited quite a lot, which is a problem since I'm also
using the server as my svn repository and I will be hosting projects for
download there soon.
I'm looking for a cost-affective dedicated server. I know you kind of get
what you pay for, but I don't have $100+ a month to drop on a box.
Any advice/ideas would be appreciated.
--
Take care,
Ty
Web: http://tds-solutions.net
The Aspen project: a light-weight barebones mud engine
http://code.google.com/p/aspenmud
Sent from my toaster.
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
prev parent reply other threads:[~ UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
Littlefield, Tyler
` Kelly Prescott [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='000001ccd482$aa11c4f0$fe354ed0$@org' \
--to=prescott@deltav.org \
--cc=speakup@braille.uwo.ca \
--cc=tyler@tysdomain.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).