<    March 2017    >
Su Mo Tu We Th Fr Sa  
          1  2  3  4  
 5  6  7  8  9 10 11  
12 13 14 15 16 17 18  
19 20 21 22 23 24 25  
26 27 28 29 30 31
00:10 ogres joined
00:26 t0mmy joined
00:32 hackerhercules joined
00:41 grayhemp_ joined
00:55 cyteen joined
01:30 BitL0G1c joined
02:06 blueness joined
02:25 mdillon joined
02:32 Nobabs27 joined
02:44 tmh1999 joined
02:52 s33se joined
03:13 slowpak joined
03:15 mdillon joined
03:19 gopar joined
03:33 tmh1999 joined
04:04 mguentner joined
04:11 Guest32918 joined
04:26 slowpak joined
04:28 ammunta joined
04:32 ammunta joined
04:42 mguentner2 joined
04:47 jailbox joined
05:42 grayhemp joined
05:52 wonton joined
06:15 fabled joined
06:33 BitL0G1c joined
06:52 leprechau joined
07:00 mdillon joined
07:09 mdillon joined
07:15 czart_ joined
07:57 fekepp joined
08:08 grayhemp joined
08:09 grayhemp joined
08:10 royger joined
08:13 blueness joined
08:22 t0mmy joined
08:35 bOSKE joined
08:39 nanohest joined
09:14 nanohest joined
09:20 lesion joined
09:37 andypost joined
09:39 newbz joined
09:46 lesion joined
09:46 tmh1999 joined
10:02 lesion_ joined
10:04 lesion__ joined
10:15 t0mmy joined
10:17 lesion joined
10:29 atmoz_ joined
10:31 atmoz joined
10:45 lesion joined
10:52 lesion_ joined
10:59 blueness joined
11:07 fekepp joined
11:10 grayhemp joined
11:11 white_knight joined
11:12 nanohest joined
11:19 fcolista joined
11:19 rrx joined
11:19 chapui_s joined
11:21 <rrx> i've seen more people having segfaulting issues with the v4l-utils package recently (from http://dev.alpinelinux.org/irclogs/ back in febuary.) has there been any more digging into this, and did anyone figure out a fix / workaround?
11:36 Orianskij joined
11:51 <ScrumpyJack> o/
11:53 <fabled> rrx, is there a bug about it?
11:55 <ScrumpyJack> BitL0G1c: you about dude?
12:00 Orianskij_ joined
12:02 Orianskij_ left
12:09 <rrx> fabled: can't find one
12:17 BitL0G1c joined
12:18 rafalcpp joined
12:23 nanohest joined
12:25 MDrights joined
12:41 grayhemp joined
12:55 farosas joined
13:00 <^7heo> \o/
13:00 <algitbot> \o/
13:00 <^7heo> ok cool
13:00 <^7heo> \o/
13:00 <algitbot> \o/
13:01 <^7heo> perfect
13:01 <c00kiemon5ter> \o/
13:01 <algitbot> \o/
13:01 <^7heo> c00kiemon5ter: could you please try again? :)
13:01 <c00kiemon5ter> \o/
13:01 <algitbot> \o/
13:01 <^7heo> yeah great.
13:01 <^7heo> I'm now ignoring all the activity from algitbot
13:01 <^7heo> which is great :D
13:01 <c00kiemon5ter> o/ should produce o/\o aka hifive
13:02 <^7heo> well, nah, o/ should produce \o
13:02 <c00kiemon5ter> :P
13:02 <^7heo> because otherwise it looks like some weird bird face
13:02 <c00kiemon5ter> haha
13:03 <^7heo> unhappy weird bird face.
13:06 t0mmy joined
13:19 meena left
13:44 stwa joined
14:11 grayhemp joined
14:15 white_knight joined
14:16 andypost joined
14:20 stwa_ joined
14:51 aw1 joined
14:52 elroncio joined
14:52 xsteadfastx joined
14:56 xsteadfastx joined
14:57 blueness joined
14:59 xsteadfastx joined
15:03 cyborg-one joined
15:05 xsteadfastx joined
15:16 xsteadfastx joined
15:18 xsteadfastx joined
15:25 xsteadfastx joined
15:26 fekepp joined
15:28 minimalism joined
15:29 xsteadfastx joined
15:30 xsteadfastx joined
15:33 xsteadfastx joined
15:35 vidr joined
15:40 xsteadfastx joined
15:41 grayhemp joined
15:46 xsteadfastx joined
15:51 rollniak joined
16:25 gromero joined
16:59 celticman joined
17:06 grayhemp joined
17:27 Berra joined
17:31 grayhemp_ joined
17:42 grayhemp joined
17:43 fabled joined
17:43 scv joined
17:48 grayhemp_ joined
17:54 rollniak joined
17:59 grayhemp joined
17:59 cyteen joined
18:01 grayhemp_ joined
18:02 grayhemp_ joined
18:02 atmoz joined
18:09 tmh1999 joined
18:19 BitL0G1c joined
18:36 BitL0G1c joined
18:44 elroncio joined
18:49 nanohest joined
19:02 grayhemp joined
19:12 Skele joined
19:22 blueness joined
19:32 C745H joined
19:38 cyborg-one joined
19:38 avih joined
19:51 TemptorSent joined
19:55 orbiter joined
19:57 TemptorSent joined
20:15 Nobabs27 joined
20:17 grayhemp joined
20:33 rollniak joined
20:43 grayhemp joined
20:44 slowpak joined
20:48 blueness joined
20:53 wonton joined
20:54 grayhemp joined
21:01 rrx joined
21:04 grayhemp joined
21:04 grayhemp_ joined
21:07 grayhemp_ joined
21:07 grayhemp_ joined
21:11 grayhemp joined
21:25 <TBB> hey, has anybody thought of, seen mentions of or even attempted installing Alpine Linux to one of those QNAP SAN boxes?
21:25 <TemptorSent> TBB: Nope, haven't poked at those yet. What are they running stock?
21:26 <darkfader> SAN? you mean NAS, right?
21:26 <darkfader> unfortunately didn't read about it yet
21:26 <TBB> they can be seen as both
21:27 <darkfader> this one is tempting for me
21:27 <darkfader> https://twitter.com/FlorianHeigl1/status/835505949137907713
21:27 <TBB> TemptorSent: they've got their own environment in it, but it seems quite interesting... some of the more powerful models can run, say, Ubuntu, on KVM
21:28 <TemptorSent> TBB: Does it have ECC memory?
21:28 <TBB> their environment is just growing at a rate that might make them rather unsafe
21:29 <TBB> TemptorSent: I imagine the more expensive models would have that; the cheaper ones most probably not
21:29 <TemptorSent> TBB: Yeah, lack of ECC is a deal-breaker for me on storage systems.
21:29 <TBB> Alpine Linux would be a good match for some of their products tho; they're supposedly running on a CPU named Annapurna Alpine
21:30 <TemptorSent> :) Yeah, that's about as alpine as you get :)
21:30 <darkfader> it would be fun if we got a commercial LIO license for it that way
21:31 <TemptorSent> An amazon company... hmm.
21:32 grayhemp joined
21:34 <TemptorSent> Not much info on their site, but it looks like it's basicaly a custom arm platform with some fast networking.
21:34 <TBB> setting one up with a ZFS capable Alpine install would definitely make an interesting [NS]A[SN]
21:34 <TemptorSent> Agreed.
21:34 <^7heo> I yet have to try zfs in alpine
21:35 <^7heo> how well is it working?
21:35 <TemptorSent> ^7heo: I have it working, at least when my kernel matches my modules :/
21:35 <TBB> me too. in general ZFS is unfamiliar to me, although I've had a FreeBSD box running at home since 1998 or so
21:36 <TemptorSent> ^7heo: I got bit by a bug in the kernel package that gave me an out of sync set.
21:36 <TBB> which is down for the first time since btw; it's in the process of being replaced by an Alpine install...
21:36 <TemptorSent> But zfs generally works great, and acts pretty much like you'd expect it to if you were on sloaris.
21:36 <^7heo> ok
21:37 <^7heo> modulo linux
21:37 <^7heo> I get it
21:37 <^7heo> so basically
21:37 <TemptorSent> ^7heo: It's pretty solid as long as you don't do something stupid :)
21:37 <^7heo> (solaris)zfs == (linux)zfs
21:37 <^7heo> like using it on linux?
21:37 <^7heo> :D
21:38 <TemptorSent> ^7heo: The core code of zfs is essentially the same across platforms now, with the 'spl' being the solaris portability layer.
21:38 <TBB> "pretty solid" doesn't sound like something I'd want to put all my data on tho :)
21:39 <TemptorSent> TBB: I wouldn't go as far as calling ext4 'pretty solid' by comparison.
21:39 <^7heo> TBB: heard about backups?
21:40 <TemptorSent> TBB: and zfs-send is your new best friend :)
21:40 <TBB> backups are problematic when the amount of data grows beyond a certain point
21:40 <TemptorSent> TBB: That's why you only have to transfer deltas with ZFS.
21:40 <TBB> but naturally, yes; I keep my current data backed up on a medium that spends most of its time offline
21:42 <TemptorSent> TBB: In order of preference for stability/reliability, I'd put it zfs,xfs,ext3,ext2,ext4,btrfs,and on down from there for standard fses.
21:43 <TBB> my current setup is XFS
21:44 <TemptorSent> TBB: Yeah, that qualifies as 'pretty solid' too, but long term data integrity is a bit harder to ensure.
21:45 <TBB> most of bad rep XFS has with regards to that is unfounded tho, but fact is, there was a pretty big problem with XFS a bit over a decade ago
21:45 <TBB> which hit me as well
21:45 <TemptorSent> TBB: Yeah, I don't mean corruption by the fs, but bit-rot on disk, which is where ZFS shines.
21:47 <TBB> ZFS is hardcore tho, all that stuff about deduplication and everything does sounds very tempting
21:47 <TemptorSent> I got bit by just about every FS out there that I tried EXCEPT zfs. The worst I did with zfs was confuse my pool enough to need to mannually reimport it.
21:47 <TemptorSent> Do NOT attempt dedup.
21:48 grayhemp joined
21:48 <TemptorSent> Dedup is probably the one crappy implementation in ZFS (mostly because it's a BIG problem space), and will quickly burn through copious quantities of ram maintaing the tables.
21:49 <TBB> I mostly just need iSCSI really, it'll help me store storage in a place where I can't hear it :D
21:50 <TemptorSent> TBB: Yeah, iSCSI is good for that, but so are clustering fs systems and object stores with local fast caches.
21:51 <TBB> clustering filesystems are a bit overkill for home use tho
21:51 <TBB> but per se I'm not against any solution
21:52 <TBB> gotta keep an open mind if one wants to stay in this industry :)
21:53 <TemptorSent> It depends on how you're using the storage. Exposing a filesystem that knows about networks is a lot more flexible than a network block device in many respects.
21:53 <TemptorSent> iSCSI has some other layers, but I'm not aware of anything using them on the linux front currently.
21:55 <TBB> I guess my primary concern is security really. iSCSI would allow me to use a remote disk in an encrypted form without the disk provider ever knowing encryption keys and such. of course now that I type that thought out I can see various ways how that strategy could go horribly, horribly wrong
21:56 <TemptorSent> TBB: *LOL* Yeah, encrypt your data, not your block layout.
21:58 <TemptorSent> TBB: That's where object-stores make a lot of sense, you can encapsulate whatever you want in the object and it will still store, backup, reconstruct, etc without loosing the ability to decrypt.
21:58 <TBB> something like ecryptfs with a physical token would probably do the trick better too
21:59 <TemptorSent> Ceph or anything heavy like that is proably too much, but there are some less overwhelming options.
21:59 <TemptorSent> TBB: Ideally, multiple tokens, any two of which can decrypt.
22:00 <TBB> sure; you don't want to lose your data just because your token breaks :D
22:17 <TBB> I actually didn't read you carefully enough there
22:26 grayhemp joined
22:37 blueness joined
22:48 felixjet joined
22:53 blueness joined
22:55 FatalFUUU joined
23:16 lesion joined