8GB RAM, Quad Core Xeon, 1TB of space in RAID I, and a dedicated 1Gb/s port. This should hold up for most things. I'll also be looking into setting up file hosting for us, as well as hosting some repos, and maybe a hidden service interface.
>>4 Instead of jails I'll just deploy VMs since this is an insanely overpowered dedicated server. I'm not so sure if I want to give it out to everyone though, I can imagine someone using it to DoS or download CP or something and then we all suffer (me the most).
I can give out computational power though, more than networking.
>>5 Then ban the installation of some shits. But VM are more costly CPU cycle wise. But meh, you have more than one core, you are welcome to allot it.
We only need a compiler, maybe a multiplexer, a nice editor would do, ssh internal access, and a door/gateway to the BBS. What I am worried is malware in the playgrounds, not CP and DoS. You can remove CP with a file(1) daemon/cron, and DoS with well iptables/pf.
Am I missing something in my equation? Internal IRC server, or should we use write(1) like bastards? I feel like I am missing something, than the obvious repository and make template.
How about this, 1. USENET server, in VM, for sharing stuff we want excluding stuff illegal in Germany. Optional. 2. Playground in OpenAFS|Coda|MooseFS under a jail with Gnunet&Freenet uplinks. One Internal connection to IRC server. 3. Repository partition, also in Distributed FS with uplinks. 4. This temporary forum, another jailed partition. 5. Temporary hidden IRC server. Hopefully in the future using SILC, OTR, and later secushare. You can close|ban|shutdown as many times as you like, to prevent floods and DoS. If too much trouble, just ignore this option. EDIT: Just ignore this option. 6. Something I am missing, maybe an MPD|icecast server just for the ambiance. I sure the /mu/ lovers would appreciate a nice repository to upload their songs. Also in a Distributed FS under a jail. 7. I know I am missing something. I guess you can make another Jail partition for something.
7 Partition total. Partition Scheme (being extremely generous) Temporary ProgBBS* = 10 GB Repository* = 20GB Test Bed* = 30 GB A tunnel and VPN & Proxy = 1 GB File Sharing (USENET, /mu/, whatever) = 30 GB Maybe chat (maybe ignore) = 1 GB Something I know I am missing* = 10GB Your stuff = *
Sub total (!options)* = 40 GB Total 85 GB. You still got 900 GB to play with (I accounted for your OS and /usr/bin && $HOME ≃ 15 GB)
RAM partitioning Scheme Repository* = 1 GB or 768MB Test Bed* = 1 GB TemporaryBBS* = 1 GB or 768MB Server Firewall* = dedicated 1GB Fileshare = 1 GB Your stuff = * Sub Total = 4GB Total = 5GB You still got 3 GB to play with. Please not that we need in the test bed access to tmpfs|md(4) or at least make us one for testing. 512MB is enough for now.
Writing the list of tools we need (compilers and shit).
Name:
Anonymous2013-09-05 14:46
How about a bitcoin miner?
Name:
F40PH2013-09-05 14:58
1chan.net redirect topsite
Name:
>>92013-09-05 15:16
Think more on it, really ignore my IRC server comment. The testbed should only have an internal connection to the BBS, and we make a thread just for our repositories/questions/etc.. So that would mean a connection to http://bbs.progrider.org/prog/ ONLY. No other domains, or port connections, than the obvious inbound ssh. I can't think of anything else the testbed needs a connection for:
SSH Inbound Port 22 Internal Jail connection (IJC) for http://bbs.progrider.org/prog/ on "port 80" IJC port for the Repository on port 8080 Maybe another IJC on port 6600 for MPD
>>13 I just want it to be DDoS proof, really. It wasn't that expensive. Plus it's good for future expansion, I imagine I won't ever need to change server no matter how much the site grows.
>>14,15 So do you also want the source for each one of those packages? Or just for SQLite nd synchronet?
Name:
Anonymous2013-09-05 16:32
Oracle Enterprise Server VMWare ESX Windows 8 site license (for the VMs) Visual Studios 2013 site license vBulliten board Asterisk VoIP gateway GitHub enterprise
Name:
Anonymous2013-09-05 16:32
>>16 for synchronet, that is up to you. For SQLite, that is what we are going to use for the DB in the BBS, to make it ACID and portable enough. I only want the synchronet to compare the code that will be in scheme, and see why he made the move to C++ and Javascript. What I am most interested is how he made compartmentalized all the uplinks. I mean gopher, http, nntp, telnet, SSH, FTP, all on one db, and managing it all with javascript. The insanity that is.
>>19 It's still just a collection of textboards. I don't imagine that even the traffic of all of 2channel put together exceeds 1Gb/s. Realize how much that is. That's ~324TB per month.
A month or two ago I called Peer1Hosting which is one of the biggest hosting providers in the world for something work related and they can only really provide 20TB per month without setting up an entire network infrastructure just for you. This hosting provider has a 900Gb/s backbone connected to the all major exchanges and peering points in the region. It'll be able to take quite a bit.
>>18 I see. I was thinking about making my own minimal DB eventually, as well. We'll see.
>>22,23 My habitual mistake is to mistakenly think the tag slash is actually the second location slash. You can probably track me all through the db by searching for /prog
Name:
Anonymous2013-09-05 19:14
Since we have 8 gigabytes of RAM? Can we dedicate 2 gigabytes of those to virtual machines that are networked together running toy operating systems us /bbs/riders program?
How about 16 megabytes per operating system? Do you think we can fit a homebrew operating system, custom network stack and small toolchain in 16 megabytes?
That'd be an interesting experiment: Let all /bbs/riders implement their own operating system from scratch and let's see where we end up with standards.
Sounds a lot like DCPU-16, if Notch didn't stop developing...
Name:
Anonymous2013-09-05 19:16
>>25 The lazy Jew would have managed to make machine code lag. It's good the project is dead: A more competent programmer can resurrect it now.
>>25 Too late, I'm already running 5,000 copies of TempleOS simultaneously generating songs from God.
Networking together "toy" operating systems would be complicated. Writing a toy OS with networking support would not be a simple thing. How many people on this board are capable of it other than T. Davis? Maybe 2 or 3? I wrote a simple OS a while ago, it was interesting at first but then it quickly got incredibly annoying when it came to interfacing with anything but the processor itself. Ask T. Davis.