[00:45] *** chfoo-_ has quit IRC (Ping timeout: 606 seconds) [00:45] *** chfoo- has joined #warrior [00:47] *** brayden_ has quit IRC (Ping timeout: 606 seconds) [01:27] *** Start has joined #warrior [04:03] *** Start has quit IRC (Read error: Connection reset by peer) [04:05] *** Start has joined #warrior [04:11] *** aaaaaaaaa has quit IRC (Leaving) [04:11] *** Start has quit IRC (Read error: Connection reset by peer) [04:28] *** Start has joined #warrior [04:30] *** Start has quit IRC (Read error: Connection reset by peer) [05:20] *** Control-S has joined #warrior [05:28] *** Command-S has quit IRC (Ping timeout: 600 seconds) [06:05] *** Start has joined #warrior [06:06] *** Start has quit IRC (Client Quit) [06:06] *** Start has joined #warrior [11:36] *** Muad-Dib has quit IRC (Ping timeout: 252 seconds) [14:36] *** oldcad has joined #warrior [14:37] Hi, I had an idea. Has anyone tried to make a Raspberry Pi warrior? [14:44] *** toad2 has joined #warrior [14:50] *** toad1 has quit IRC (Read error: Operation timed out) [15:02] someone tried before. the framework itself is platform independent but the project themselves drop in and use a x86 binary [15:06] chfoo: what uses a x86 binary? [15:07] If i look at (e.g.) github.com/ArchiveTeam/zoocasa-grab, its written in lua, python and shell. Obviously one wouldn't run a VM on a Raspberry Pi, it would need to be a debian image with the warrior framework. And make sure to disallow the SD card as storage (for data integrity). [15:08] Im going to look more into it [15:12] A Raspberry Pi is cheap and would be ideal for a "set and forget" type of warrior appliance. Just plug a Ethernet cable in and leave it to do its job. One could even create a control panel of sorts to manage multiple RPi warriors. [15:55] *** brayden_ has joined #warrior [17:10] *** aaaaaaaaa has joined #warrior [17:12] oldcad: wget-lua for webgrabs gets compiled as part of the get-wget-lua.sh [17:13] you can build wget-lua for ARMv6, we just don't keep a binary around [17:14] oldcad: https://github.com/ArchiveTeam/warrior-dockerfile may be useful; not as-is, per se, but the Dockerfile encodes setup instructions that can be reused [17:15] right, I just wanted to make sure he didn't miss that step in reverse engineering as he specifically asked what of the warrior uses the x86 binary [17:15] actually I guess "you can build wget-lua for ARMv6" is contingent on Lua supporting ARMv6 [17:15] I'd be surprised if it didn't [17:15] aaaaaaaaa: ah ok [17:26] but yeah, I'm 90% sure that someone got it working at least once but who it was escapes me. [20:05] *** ete_ has joined #warrior