#warrior 2013-04-22,Mon

↑back Search

Time Nickname Message
00:26 🔗 shaqfu Anyway, I think that once I track down css.c, this'll build and run fine
00:28 🔗 omf_ wget has a css.c in the src/ dir
00:29 🔗 shaqfu So copy that over from my wget sources?
00:30 🔗 shaqfu Sweet, worked; thanks
00:30 🔗 shaqfu Back to brutalizing this poor system :)
00:30 🔗 omf_ were you just working the wget-lua source still?
00:31 🔗 shaqfu Yeah
00:31 🔗 shaqfu Grabbed the sources, bootstrap, configure, make
00:31 🔗 omf_ yeah I know the wget source pretty well from study.
00:34 🔗 shaqfu Yay, built
08:20 🔗 Smiley woo :)
20:01 🔗 mhouston Hey, is it possible to run Warrior inside an LXC container, rather than VBox? That's just what I have set up on my server already.
21:10 🔗 alard mhouston: I think you would be the first to do that. Does LXC take OVF/OVA files?
21:20 🔗 mhouston No, I don't think so, it might be possible to convert it though - LXC isn't a full virtual machine, so it just runs a new linux 'init' process inside a sandbox.
21:20 🔗 mhouston Assuming the ova has a filesystem with a linux distro inside, it might be an easy port. I will investigate!
21:26 🔗 alard mhouston: It's a normal 32-bit Debian linux.
21:26 🔗 alard The boot scripts are here: https://github.com/ArchiveTeam/warrior-code2 (starts with boot.sh)
21:27 🔗 mhouston Ah, in that case I will start from there with a fresh container and install the scripts - thanks!
21:28 🔗 alard Here's the EC2 version: https://github.com/ArchiveTeam/warrior-code2/tree/ec2
21:29 🔗 alard Debian installer preseed: https://github.com/ArchiveTeam/warrior-preseed
21:30 🔗 alard If it's possible, it's best to stay with 32-bit Debian. Most warrior projects come with a precompiled Wget+Lua that expects that environment.
21:44 🔗 mhouston alard: I've got it to start up a 64bit debian container, but if it's a problem I think I can get the template to use 32-bit - the documentation is a bit sketchy.

irclogger-viewer