=== zz_mwhudson is now known as mwhudson === mwhudson is now known as zz_mwhudson [19:15] is anybody else seeing a problem with latest kernels in trusty where filesystems are filling up with invisible usage, that clears up on reboot? [19:17] (problem seen with 3.13.0-4-generic; have just rebooted to 3.13.0-5-generic, waiting to see if the problem manifests again) === Traxer is now known as Traxer|on === Traxer|on is now known as Traxer [20:00] i would like to ask why ubuntu maintains the kernel themselfs [20:07] jarkko: Relative to what? [20:08] i just want to know why ubuntu maintains the kernel themself [20:08] or is it just backportig drivers? [20:09] jarkko, every distro does that ... you need to do packaging and testing to make sure it works in context of the rest of the distro [20:09] really? [20:09] The kernel configuration process is pretty complicated, and there are lots of decisions ot be made [20:10] (and you will also find that every distro maintains its own kernel config) [20:10] what features work, what features don't work, what features make sense for Ubuntu, what features do not [20:10] right [20:10] so basically the same kernel can be very different on other distro? [20:10] yes [20:10] well, differently configured [20:10] and differently patched [20:11] right [20:11] never thought that [20:11] although sharing (or poaching) patchsets is pretty common ;p [20:11] well i have compiled kernel few times and noticed lots of things i have no idea [20:11] "dicen, que el ser humano es un programa del universo; ¿sera que la muerte es solo un cambio de actividades?" bienvenidos: http://castroruben.com *temo_a_un_ser_sin_rival* [20:11] i mean the config [20:12] jarkko, fedora builds all its security in userspace around selinux ... ubuntu does the same with apparmor ... you cant have bot that the same time enabled in the kernel ... [20:12] just as an example [20:12] s/that the/at the/ [20:15] do you have any opinion replacing iptables? [20:16] not really ... [20:16] i dont use it [20:18] (not really necessary on ubuntu ... ports only get opened if a userspace process listens on them, in ubuntu there is a "no open ports by default" policy so the risk is pretty low) [20:18] really? [20:19] (unless you explicitly install something that is supposed to listen indeed ... like a webserver ... but then you should know that port 80 is open for it) [20:19] how can i confirm that? [20:19] use another machine ... get familiar with nmap and scan your ubuntu install from there [20:21] a default desktop install will only have DHCP and MDNS open ... [20:24] does every kernel release need hard patching? [20:27] thats something you should ask the kernel team during the workweek ... they are rarely around on weekends ;)