[00:00] lol [00:01] i'm pretty sure it's not that 4U beast ;) [00:01] or what looks like 4U [00:01] it's a blade! [00:01] it's mounted vertically in that chassis [00:14] that size? [00:14] they seem too small [00:15] or am i too used to the monster Blade Center sized blades [00:15] yup, 8 servers in 3U [00:15] http://www.supermicro.com/products/system/3U/5038/SYS-5038ML-H8TRF.cfm [00:16] they are indeed tiny [00:17] *breathing intensifies* [00:17] LOL [00:19] damn [00:20] my how times have changed [00:22] I love servers that have a USB port on-board, internally, so you can put the OS on it, or recovery, or whatever... [00:49] that's pretty common bryce [00:49] i don't like it myself [00:50] i didn't think of recovery, but it's a pita to change [00:50] some kind of more secure slot or something woudl be nice though [00:50] an sdcard slot? [00:50] that pushes in like laptops [00:50] actually having more than one could be good too [00:52] i like the idea of pxe boot recovery best. [00:53] makes it easier to udpate etc. [01:11] mercutio: it didn't used to be common. :p [01:12] And presumably, it's not going to be changed often. Installed once when built, and it can be rewritten/changed later as-needed (if used for recovery/reinstall), or if it's used for OS install then it's simply there. [01:32] hp servers have for ages [01:49] *** dj_goku_ has joined #arpnetworks [01:49] *** dj_goku has quit IRC (Read error: Connection reset by peer) [01:52] ok dl380 g5s have them [01:52] trying to find a year for that though [01:52] 2006 [01:53] it seems g4 does too [04:14] *** DaCa_ has joined #arpnetworks [04:15] *** bitslip has joined #arpnetworks [04:21] *** bitslip_ has quit IRC (*.net *.split) [04:21] *** DaCa has quit IRC (*.net *.split) [10:52] *** mnathani_ has quit IRC (Ping timeout: 252 seconds) [12:37] *** mnathani_ has joined #arpnetworks [14:06] *** _Zodiac has joined #arpnetworks [14:06] *** _Zodiac has left [16:54] *** mnathani__ has joined #arpnetworks [16:54] *** mnathani_ has quit IRC (Read error: Connection reset by peer) [23:43] so does anyone know how the git /etc thing is meant to work? [23:44] do you just do it like any other git repository, or is there a way to make it more secure? [23:45] mercutio: you talking about git-annex? [23:45] https://git-annex.branchable.com/ [23:45] i dunno what i'm talking about [23:45] i just thought i should try using git for /etc [23:45] Then that's what you're talking abotu ;) [23:45] but i haven't looked into it before. [23:46] i found something called etckeeper so far [23:46] do you use /etc on git? [23:46] Me? I do not. [23:46] I knew someone else that used git-annex [23:46] does git-annex auto-commit? [23:47] mercutio: No. See https://git-annex.branchable.com/walkthrough/ [23:47] ok nice long wlakthrough [23:48] i will have to check it out tomorrow i think [23:48] heh, the core is in the first few examples, a quick skim is all that's needed [23:48] ahh [23:49] If you want to store the files too (full on git, not just git-annex), then it's a simple "cd /etc/ ; git init" (etc etc etc) [23:49] i'm mostly thinking about how to get it to automaically store stuff [23:49] and record changes [23:49] even if people don't commit every change [23:50] ie it's only updated from one place for one machine [23:50] http://evilrouters.net/2011/02/18/using-etckeeper-with-git-on-ubuntu/ [23:50] maybe git isn't the cleanest way? [23:50] what are you using it on? [23:50] the os, i mean? [23:50] You could put the commit in cron, or put some elaborate hook in your .profile... But I don't see any other "automatic" way [23:50] ubuntu [23:50] s/u/ew/ [23:50] ewbewntew [23:50] well, there ya go. see link. [23:50] haha [23:51] jlgaddis: are you using it? [23:51] yup [23:51] ahh this looks a little better [23:51] "Though I think we would all agree that it???s important, the unfortunate fact is that myself and other members of my ???team??? don???t necessarily document things as well as we always should. " [23:52] that's so prevalent. [23:54] As someone that's taking over the sysadmin role at a company with a surprisingly complex, and very interwoven with the product they sell, IT structure... Yeah, so true. [23:55] "How the fuck does that database replicate to that server? WHO KNOWS!" [23:55] once it's installed and initialized, you don't have to touch it. you *can* commit changes manually after you make them if you want (and i'd recommend it) but if you forget, they'll be auto-committed via a nightly cron job. [23:55] and apt hooks into etckeeper also, to do pre- and post- "apt stuff" commits [23:56] (There were some efforts to document the design aspects later on, but I still have to figure out all the little nuances and try and roll-out a duplicate environment)