| jaeger | dirty secrets (tm) | 00:13 |
|---|---|---|
| jaeger | it's my work workstation for reference | 00:13 |
| diverse | ;) | 00:14 |
| diverse | I'm going to build another workstation as soon as my tech bench and motherboard arrives | 00:14 |
| Workster | more like a reimplementation than a rewrite | 00:15 |
| Workster | a rewrite is just cleaning up existing messy code to me | 00:15 |
| Workster | nothing out of the ordinary and a lot less than i'm using on my desktop jaeger | 00:16 |
| jaeger | no doubt :) | 00:16 |
| diverse | I see | 00:16 |
| diverse | then I guess a rewrite is more accurate to what I'm doing ;) | 00:18 |
| Workster | not even in the same language, but your copying the original in a way so partly both, while jaeger is going blind in on a total reimplementation | 00:29 |
| jaeger | on a side note I originally started this reimplementation in python but decided later to do C instead | 00:32 |
| *** Roosevelt has left #crux-devel ("Leaving") | 00:35 | |
| diverse | jaeger: that's a good idea, you abstract the code in a prototype state | 00:37 |
| diverse | btw, I'm planning on changing the name of my project | 00:38 |
| diverse | well have been planning | 00:39 |
| jaeger | to what? | 00:42 |
| diverse | I'm going to call it "metagear" now. The reason is, I'm planning to work on rewriting prt-get too. Calling my project "metapkg" has confused people thinking the binary is called metapkg, when really it's "pkg" for simplicity. | 00:43 |
| jaeger | snaaaaaaake! | 00:43 |
| jaeger | METAL GEAR?! | 00:43 |
| diverse | jaeger: hey you got it!!! | 00:43 |
| jaeger | sorry, couldn't resist | 00:43 |
| jaeger | mine's just called 'cpkg' for simplicity | 00:44 |
| diverse | well not just an implicit reference to the Metal Gear series, but also because the Rust mascot is a cogwheel gear too | 00:45 |
| jaeger | ah | 00:45 |
| jaeger | I'd nearly forgotten about it but the cruxppc folks had a new tool as well. ilenia or something like that | 00:46 |
| jaeger | I don't know the differences, though | 00:46 |
| diverse | ah | 00:47 |
| diverse | jaeger: also MGS is where I knew how to pronounce your nick because of Solid Snake's old rival/companion Gray Fox | 00:50 |
| jaeger | heh, nice | 00:50 |
| jaeger | time to leave work, AFK | 00:56 |
| diverse | oh that's why you had the domain name "crux.ninja" I just released that | 00:57 |
| diverse | jaeger: you are very clever | 00:57 |
| diverse | heh | 00:58 |
| diverse | lots of implicit meanings everywhere | 00:59 |
| *** crash_ has quit IRC | 01:02 | |
| jaeger | I just liked the sound of it, actually, it wasn't tied to anything | 01:37 |
| diverse | gotcha | 01:39 |
| jaeger | I like to think I'm a bit of a crux ninja by now but that may be too presumptuous :P | 01:39 |
| *** Feksclaus has joined #crux-devel | 01:40 | |
| diverse | hehe | 01:40 |
| diverse | jaeger: how does being a cyborg ninja sound though? | 02:04 |
| jaeger | expensive | 02:05 |
| diverse | good point | 02:05 |
| *** mavrick61 has quit IRC | 03:24 | |
| *** mavrick61 has joined #crux-devel | 03:25 | |
| *** Feksclaus has quit IRC | 05:44 | |
| *** irclogger_ has joined #crux-devel | 12:53 | |
| *** irclogger__ has joined #crux-devel | 12:54 | |
| *** deus_ex has joined #crux-devel | 14:22 | |
| *** Feksclaus has joined #crux-devel | 14:24 | |
| *** Workster has quit IRC | 16:26 | |
| *** teK_ has quit IRC | 19:36 | |
| *** teK_ has joined #crux-devel | 19:38 | |
| diverse | prologic: ping | 20:47 |
| *** frinnst has joined #crux-devel | 21:25 | |
| *** frinnst has quit IRC | 21:25 | |
| *** frinnst has joined #crux-devel | 21:25 | |
| prologic | diverse: pong | 21:25 |
| diverse | are you an expert on network programming? | 21:26 |
| prologic | sure why not | 21:30 |
| prologic | I'll pretend to be one today ;0 | 21:30 |
| diverse | sorry that I asked... | 21:31 |
| prologic | lol | 21:32 |
| prologic | no no ask away :) | 21:32 |
| prologic | I just don't believe in "exports" as such :) | 21:32 |
| prologic | let's just say I probably have spent several thousand hours programming network services (mostly in Python ofc) | 21:32 |
| prologic | spent many hundred hours debugging networks and packets with wireshark | 21:33 |
| prologic | and many thousand hours configuring networks :) | 21:33 |
| prologic | so they if you spend 10,000 hours doing something you're an expert | 21:33 |
| prologic | so *meh* :) | 21:33 |
| prologic | they say* | 21:33 |
| prologic | hmm need coffee | 21:33 |
| diverse | sorry that I asked... | 21:52 |
| diverse | whoops | 21:52 |
| diverse | damn history | 21:53 |
| diverse | prologic: well I got tired of waiting for leo, so I wanted to consult with you on how I should go with implementing code that downloads files | 21:54 |
| diverse | leo insists I use TLS code | 21:55 |
| prologic | I see | 21:56 |
| diverse | but we never delved further into the topic and I'm stuck | 21:56 |
| prologic | doesn't rust have something equivilent to requests or urllib? | 21:56 |
| prologic | or httplib | 21:56 |
| diverse | there is bindings to curl | 21:56 |
| prologic | yeah use that | 21:57 |
| prologic | let curl do the heavy lifting | 21:57 |
| prologic | there's also pycurl too :) | 21:57 |
| diverse | hmm | 21:58 |
| prologic | concerns? | 21:58 |
| diverse | thinking from a security pov, curl bindings also rely on the openssl bindings but I guess there is libressl's libssl, for security fixes that the openssl team is too lazy to fix | 22:00 |
| prologic | I wouldn't worry too much about it | 22:01 |
| prologic | or you'll spend far too much time doing something that should be simple :) | 22:01 |
| prologic | just use the curl bindings and be done with it | 22:01 |
| prologic | IIRC/AFAIK pkgmk right now uses curl as-is too calling out to /usr/bin/curl | 22:01 |
| diverse | I thought it was wget? | 22:02 |
| diverse | although I guess wget would use curl | 22:02 |
| *** Workster has joined #crux-devel | 22:02 | |
| jaeger | it uses wget | 22:02 |
| prologic | oh sorry wget :) | 22:06 |
| prologic | point is the same :) | 22:06 |
| diverse | well wget uses openssl | 22:06 |
| prologic | don't write your own http/ftp client code :) | 22:06 |
| diverse | prologic: keep in mind, my project isn't "real" so anything could go ;) | 22:07 |
| diverse | but if I want to get something done, I guess that's the path | 22:07 |
| diverse | unfortunately leo is too busy either | 22:08 |
| diverse | prologic: here is some examples https://github.com/carllerche/curl-rust | 22:12 |
| diverse | prologic: I would want to use the .get() method to pull files, correct? | 22:15 |
| diverse | (I wish there were api docs) | 22:15 |
| diverse | jaeger: even now I'm still don't know what I'm doing ;) | 22:19 |
| jaeger | it's a learning project :) | 22:20 |
| diverse | yep | 22:20 |
| *** leo-unglaub has joined #crux-devel | 22:24 | |
| diverse | hahahaha, look who came | 22:25 |
| Workster | on cue | 22:26 |
| prologic | diverse: sounds about right | 22:35 |
| Workster | hmm i like the idea of curl than wget. 1) better proxy support 2) meta4 support. | 22:38 |
| Workster | only down side of possibly using meta4 would be single point of failure or keepng meta4 files with the Pkgfile which isn't idea for auto regeneration due to mirror reliability updates. a cdn for that would solve it. | 22:40 |
| Workster | of course it'll be not supported by crux, most likely. | 22:40 |
| diverse | well I got enough info to get started | 22:46 |
| diverse | brb, I need food | 22:46 |
| *** deus_ex has quit IRC | 23:16 | |
| *** pitillo has quit IRC | 23:22 | |
| prologic | jaeger: if the CRUX 3.1 ISO successfully boots some arbitrary system and sees it's block device(s) -- Can one just zcay /proc/config.gz > /usr/src/linux/.config and build from that config without modifications and expect to get a bootable system? | 23:29 |
| prologic | I should think so (hopefully) | 23:29 |
| jaeger | almost. you'd need the ISO's initramfs as well | 23:30 |
| jaeger | however, the .config that the setup installs is the same as the running .config except for the necessity of the initramfs | 23:30 |
| jaeger | so there's no real benefit to doing what you're asking about unless you want to skip the kernel compile step | 23:31 |
| jaeger | make sense? | 23:32 |
| prologic | yeah | 23:35 |
| prologic | so I'd still need to configure the initramfs out of the config | 23:35 |
| prologic | oh well at least an initial build is done | 23:35 |
| jaeger | not much configuration needed; you'd copy it to the installed system and add it to your bootloader config with root=whatever | 23:35 |
| prologic | kk :) | 23:36 |
| prologic | anyway I'll finish this up later | 23:36 |
| prologic | I'm trying out vultr.com hosting | 23:36 |
| jaeger | if root=whatever is specified the initramfs tries that instead of its normal search and rescue | 23:36 |
| prologic | apparently they support uploading custom ISOs | 23:36 |
| prologic | so +1 | 23:36 |
| prologic | I want to construct a list of CRUX friendly hosting providers | 23:36 |
| prologic | and stick it up on our wiki | 23:36 |
| jaeger | the kernel thing might be a moot point if they use xen or whatever | 23:36 |
| jaeger | even with the custom iso you'd use their kernel | 23:36 |
| prologic | hmm? | 23:37 |
| prologic | I think it's full virtualization | 23:37 |
| jaeger | ok | 23:37 |
| jaeger | they use KVM | 23:38 |
| jaeger | according to their faq | 23:38 |
| prologic | yeah | 23:38 |
| prologic | was just looking at that | 23:38 |
| jaeger | should be relatively straightforward, then | 23:38 |
| prologic | so all good there | 23:38 |
| prologic | *nods* | 23:39 |
| prologic | be a similar setup/config to hetzne.de | 23:39 |
| prologic | sorry http://www.hetzner.de/ | 23:39 |
| prologic | I'll have to re-test/try out slicehost and linode again to be sure they're still CRUX friendly :) | 23:39 |
| prologic | haha | 23:39 |
| jaeger | linode is (that's what I use) with their kernels | 23:40 |
| prologic | might might make the list hetzner, slicehost, linode and now vultr | 23:40 |
| prologic | ahh cool | 23:40 |
| prologic | I remember slicehost was | 23:40 |
| jaeger | my IRC client runs on a crux linode VPS | 23:40 |
| prologic | used to use them | 23:40 |
| prologic | *nods* | 23:40 |
| jaeger | Linux ninja 3.15.4-x86_64-linode45 #1 SMP Mon Jul 7 08:42:36 EDT 2014 x86_64 Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz GenuineIntel GNU/Linux | 23:40 |
| prologic | so Linode use Xen? | 23:40 |
| jaeger | indeed | 23:41 |
| prologic | so with Xen virtualization no kernel is required by the guest? | 23:41 |
| prologic | the hypervisor boots a kernel | 23:41 |
| prologic | and you just build a filesystem on the block device? | 23:41 |
| jaeger | none that the user needs to install. a xen-compatible kernel is required but linode provides that | 23:41 |
| jaeger | (and doesn't give the option for custom ones) | 23:41 |
| jaeger | otherwise the install is as usual | 23:42 |
| prologic | right | 23:42 |
| jaeger | no kernel, no bootloader, configure those through their web UI | 23:42 |
| prologic | so still setup/configure lilo? | 23:42 |
| prologic | but no kernel | 23:42 |
| prologic | ahh | 23:42 |
| prologic | gotcha | 23:42 |
| prologic | weird :) | 23:42 |
| prologic | I guess Xen is still quite popular as a platform | 23:42 |
| jaeger | It's not weird if you're a xen hosting provider :D | 23:42 |
| prologic | true :) | 23:42 |
Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!