[01:44] *** twoTBHetz has quit IRC (Quit: Leaving) [02:00] *** GitHub16 has joined #warrior [02:00] *** GitHub16 has left [02:03] *** GitHub29 has joined #warrior [02:03] *** GitHub29 has left [02:03] *** GitHub125 has joined #warrior [02:03] *** GitHub125 has left [03:17] *** nertzy has joined #warrior [03:32] *** nertzy has quit IRC (Quit: This computer has gone to sleep) [03:39] *** nertzy has joined #warrior [04:12] *** nertzy has quit IRC (Quit: This computer has gone to sleep) [04:16] *** nertzy has joined #warrior [04:26] instead of running multiple items at once, is there a way for one item to download multiple URLs at once? [04:34] sep332: For which project? [04:45] tumblr. just thought it might help to go faster without needing to multiply disk space for multiple items at once [05:47] *** hatman has joined #warrior [05:53] Is there any worry of legal issues using the Warrior? [06:02] *** hatman has quit IRC (Quit: http://www.mibbit.com ajax IRC Client) [06:09] *** nertzy has quit IRC (Quit: This computer has gone to sleep) [07:07] *** arlen has joined #warrior [07:42] *** arlen has quit IRC (arlen) [07:49] *** arlen has joined #warrior [08:01] *** Soulflare has joined #warrior [08:44] *** arlen has quit IRC (arlen) [11:07] *** aard has joined #warrior [11:44] *** nertzy has joined #warrior [14:43] *** arlen has joined #warrior [14:53] sep332: Nope, wget doesn't support concurrent downloads. [16:05] *** arlen has quit IRC (arlen) [16:10] > 11:04:35 is there an easy way to give the vm more than 60GB? I couldn't immediately figure it out. [16:10] zeraT: So... Have you tried using the VirtualBox settings? [16:10] Here: http://derekmolloy.ie/resize-a-virtualbox-disk/ [16:10] Have fun! [16:10] kiska: Thanks. [16:10] cool thanks [16:11] > 11:07:46 <@kiska> You can first tell virtualBox to allocate more space for the VM [16:11] > 11:08:02 <@kiska> Then you can tell Linux that the partition is bigger [16:11] That's what kiska said. [16:11] Now the thing is you must be comfortable with command line [16:12] Quite honestly, the warrior should probably come with more space. [16:12] The 60GB decision was made years ago, I think [16:12] I think VirtualBox can dynamically allocate the disk files anyways. [16:12] Oh, where can I get information on the decision? [16:12] Absolute max is 60GB [16:13] kiska: Can a new decsion be made? [16:13] decision* [16:13] Thats why this channel exists [16:13] I won't floudner in the command line. I just didn't want an issue with the 60GB disk since I just got done uploading a 9ishGB tumblr, and I'd really like to run some concurrent tasks without fear of getting a bunch that add up to mroe than 60 at a bad time [16:14] disk space isn't an issue, I easly can spare a TB or two if I really wanted to, it just seemed silly to have that concern [16:14] anyway thanks for the link, I'm on it [16:14] I think that's probably how VirtualBox made my macOS system crash twice. [16:15] It probably ran out of space. [16:17] I propose the warrior to a have dynamic disk allocation increased to 500 GB for now. [16:17] 60 GB is usually fine. There are very few projects which need more space. The only ones I can think of right now from the past 2 years are Vidme and Tumblr. [16:18] JAA: If VirtualBox dynamically allocates disk space on the host system, why not just set it to 500 GB and not worry about it so much? [16:19] Besides, the project is growing. I beleive the warrior should be able to work on multiple projects at once. This size increase will be beneficial for that goal. [16:21] I assume that the 60 GB choice was a compromise between "we need enough space" and "we don't want to eat up all of the space". [16:22] I think this FAQ sums it up: https://www.archiveteam.org/index.php?title=ArchiveTeam_Warrior#How_much_disk_space_will_the_warrior_use.3F [16:22] Also, I believe VirtualBox doesn't shrink disk images when the space use drops down, e.g. after a project with huge items (such as Tumblr) finishes. So it'd then always consume that amount of disk space until the user takes action to manually fix it. [16:23] I can verify that last bit to being true [16:23] We want to make it as simple as possible to contribute to the pool. "Give us 60 GB of your disk space" is simple. "You may have to run some weird voodoo magic in the terminal once in a while so we don't eat all your available disk space" isn't. [16:24] Regarding running multiple projects in parallel: if you want to do that, just run the scripts directly and save yourself the overhead of the warrior VM. [16:24] That is a good point. I usually restart the VM to the initial snapshot, so that was why I was able to avoid the space concerns. [16:24] And those who want to be adventurous in terminal can do so by running the scripts [16:25] JAA: You're right. I can see your point. I just can't run some of the scripts because they currently do not work on macOS. [16:26] Perhaps my frustration was that the Warrior was not doing enough. [16:26] And it was crashing my system. [16:27] On the initial creation of the VM it does ask you where you want to chuck it [16:27] kiska: What do you mean? [16:28] On appliance import it asks you where you want to put the VM stuff [16:28] Right after I import the VM appliance, I create a snapshot. Then whenever I close the VM window, it gives me the option to Power Off and restore to last snapshot. [16:29] kiska: I put the VirtualBox stuff in a folder ~/Documents/VirtualBox/ [16:30] I put it in E:/AT Warrior since it defaults to C drive for me and C drive is a SSD [16:37] Okay. So I will try to add some notes about the disk size on the wiki page? [16:43] The wiki (https://www.archiveteam.org/index.php?title=ArchiveTeam_Warrior) says "Any unused virtual machine disk space is not used on the host computer." [16:55] *** kbtoo_ has joined #warrior [19:04] *** jeekl has quit IRC (Remote host closed the connection) [19:38] *** jeekl has joined #warrior [21:00] *** GitHub4 has joined #warrior [21:00] *** GitHub4 has left