[00:19] <sbeattie> Knyaz: http://releases.ubuntu.com/
[00:40] <mason> Knyaz: also https://www.ubuntu.com/download/alternative-downloads
[06:26] <ChewyNoob> I tell ya what. When every single forum I read said not to try and set up a mail server, I should have listened.
[06:38] <lordievader> Good morning.
[13:11] <hypermist> why is my ubuntu deny sshing connections the last thing i did was disable docker
[13:28] <gddai> hi
[13:28] <gddai> something is keep setting my locales to POSIX no matter what i do
[16:25] <Mead> anyone know how I could find out if a used PCI (not pci express) graphics card will be supported by ubuntu server before I purchase it?
[16:32] <ppetraki> Mead, if it's that old it probably works
[16:59] <Mead> ppetraki: I discovered something can be too old, with trying to use old vga cards
[17:01] <ppetraki> Mead, the easiest thing to do is "just try it". Unless you can figure the pci vendor and device ID in advance, that's the only way you can determine if an X driver will support it. Otherwise it'll try to use the plain vga driver, which should work. but may not have enought color support to drive unity for example
[17:50] <compdoc> anyone have problems with the last qemu update? guests not booting?
[18:13] <b-yeezi> hello all. Anyone here ever setup a django app inside an LXD container?
[18:16] <b-yeezi> I have two containers on a host, one for db one for django/nginx. I can get the db to talk to the app. I can forward the app's port 80 to the host, but I cannot get allowed_hosts to work.
[19:50] <c0mrade> I've just inserted an Ubuntu 16.04.2 LTS DVD into my server and I have many installation options, one of them is Install Ubuntu Server with HWE kernel. What does that mean? How would it differ and why would it matter to me if I pick second option the one with "HWE Kernel"?
[19:53] <ikonia> c0mrade: do not cross post
[19:53] <ikonia> c0mrade: ask in #ubuntu OR here, not both
[19:54] <c0mrade> I asked in ubuntu and it didn't work. So I thought ubuntu-server would be great.
[19:54] <c0mrade> ikonia: Dude you're like my shadow :D
[19:55] <ikonia> c0mrade: no, you where discussing it in #ubuntu and people where responding, please use one channel
[19:55] <c0mrade> ikonia: Why is it that you're the only one concentrating and focusing on what am doing :P
[19:56] <ikonia> you're in channels I'm an operator for, we have a policy of not cross posting, I'm telling you not to do this, thats why
[19:56] <c0mrade> You're about to be promoted to like a freenode staff or aiming for a channel operator?
[19:56] <c0mrade> Oh you're an operator...
[19:56] <c0mrade> I get it.
[19:56] <c0mrade> You're an operator at #ubuntu then.
[19:56] <ikonia> you have a history of spamming your questions across multiple channels - you've continued to do this, hence why I'm telling you not to do this
[19:56] <ikonia> clear ?
[19:57] <c0mrade> I just asked in two channels. I used #ubuntu and apparently I remembered that my question is related to #ubuntu-server much more so I moved there.
[19:57] <ikonia> please don't lie
[19:57] <ikonia> you've just changed your story
[19:57] <ikonia> you said no-one was responding in #ubuntu a minute ago
[19:57] <c0mrade> What am I supposed to do in this situation. Join #ubuntu-server and tell them I apologize I just asked the same question in #ubuntu but I am not spamming it's just my question is more relevant here.
[19:58] <ikonia> please - pick a channel and use it
[19:58] <ikonia> no more discussion on it
[19:58] <c0mrade> What channels are you an operator in?
[19:59] <ikonia> you can search chanserv if you want
[19:59] <c0mrade> How many?
[19:59] <c0mrade> Like 5 channels?
[19:59] <ikonia> it doesn't matter
[19:59] <c0mrade> It does...
[20:00] <c0mrade> You have the right to tell me what to do in a channel you are an operator in.
[20:00] <ikonia> right, and I've just told you not to cross post, so please don't, discussion completed
[20:00] <c0mrade> But otherwise it's just simply no unless I hear a comment from the operator of that channel itself.
[20:01] <ikonia> it's up to you how you behave
[20:01] <c0mrade> I will respect your complaint in a channel you are an operator in but in a channel that you are not, you just simply can not tell me that unless again an operator of that channel did.
[20:02] <ikonia> as I said, it's up to you how you behave
[20:03] <c0mrade> ikonia: It's not that. If you're an op, one day you may ban me and tell everyone how wrong were I. Well I told you, I agree with you that I won't be cross posting in channels that you operate but otherwise no.
[20:04] <ikonia> c0mrade: I don't care, you've just got banned from other channels for cross posting, if you ignore it in other channels you'll get banned, I don't care, but this is why I'm telling you clearly not to do it here
[20:04] <c0mrade> And the only reason I don't want to get banned is because I gain experience from these channels.
[20:04] <b-yeezi> Anyway, to answer your question, HWE  basically means an updated kernel version on the 16.04 stack
[20:04] <c0mrade> b-yeezi: That's not only it.
[20:04] <ikonia> b-yeezi: it was already answered in #ubuntu before he posted here
[20:05] <c0mrade> I mean a sane person would then think well why the hell would they offer two kernel versions one is a bit older and the newest one, I mean the newest is the greatest, but there's one thing to it which google helped me to understand.
[20:05] <c0mrade> ikonia: It wasn't answered clearly neither in #ubuntu nor here.
[20:06] <ikonia> I disagree, but you have the answer now, so thats good
[20:06] <c0mrade> ikonia: How would you compare their answer with one like this:
[20:06] <c0mrade> " Ubuntu will offer at least two kernels: the General Availability (GA) kernel, i.e. the most stable kernel, which does not get updated to point releases; and the Hardware Enablement (HWE) kernel, i.e. the most recent kernel released. "
[20:06] <ikonia> c0mrade: pretty much exactly what b-yeezi just told you
[20:07] <c0mrade> [23:04] <b-yeezi> Anyway, to answer your question, HWE  basically means an updated kernel version on the 16.04 stack
[20:07] <c0mrade> I don't know how 'exact' that was.
[20:07] <c0mrade> Brand new hardware devices are released to the public always more frequently. And we want such hardware to be always working on Ubuntu, even if it has been released after an Ubuntu release. Six months (the time it takes for a new Ubuntu release to be made) is a very long period in the IT field.
[20:08] <ikonia> no it's not
[20:08] <c0mrade> Now, how does Ubuntu want to reach the goal of Hardware Enablement? Using rolling releases for the kernel: as soon as a new kernel is released, it is packaged for Ubuntu, tested (via the proposed pocket and special Q/A methodologies), and made available to Ubuntu users.
[20:08] <ikonia> 6 months is very acceptable, and few people will use that for production use
[20:08] <c0mrade> This method has of course some disadvantages: releasing a new kernel too quickly may introduce some bugs and issues, and may not be suitable for the enterprise.
[20:08] <ikonia> which is why people pick longer term distros which have mapped release cycles
[20:08] <ikonia> so I suggest you look at how people operate, and try to plan using their methods
[20:08] <c0mrade> The solution? Offering different kernels for different users.
[20:09] <ikonia> no
[20:09] <c0mrade> ikonia: I was expecting something like that.
[20:09] <c0mrade> Not a one-liner.
[20:09] <b-yeezi> For me, I use the rule of  "if I don't need HWE, I stick with the default kernel"
[20:09] <ikonia> b-yeezi: that seems wise
[20:09] <c0mrade> I disagree...
[20:10] <ikonia> then don't do it
[20:10] <ikonia> grab whatever kernel meets your needs
[20:10] <c0mrade> If I see an option that I don't understand, I investigate it, search about it.
[20:10] <c0mrade> I saw this option and I instantly stopped what am doing. I needed to know what is this option all about.
[20:10] <ikonia> great
[20:11] <ikonia> now you know
[20:11] <c0mrade> Yeah, but am just telling you that I didn't get clear answers, answers that I would perfectly understand what it is.
[20:12] <b-yeezi> I have a cheap asus laptop with 16.04. I enables HWE, it wouldn't boot. There is a bug in kernel 4.8 for the atom processor in it. Ever since then, I instituted the rule
[20:12] <c0mrade> Anyway. I'll say thanks to everyone who answered my question.
[20:12] <c0mrade> b-yeezi: Thanks for that tip!
[20:12] <c0mrade> ikonia: ^
[21:42] <l33n> "pm2 list" does nothing
[21:42] <l33n> it prints a new command line
[21:43] <l33n> same thing with "node server.js"
[21:46] <Guma> I was wondering if someone could help me out with figuring out or pointing me to source of problem I have. I just installed 16.04 with RAID 1+0. Installation and setup did go well. I also running KVM on it. My problem is that when I reboot machine RAId goes to rebuild.
[21:46] <Guma> Looking at /proc/mdstat after reboot I see % rebuild.
[21:47] <Guma> That takes about 40 min or so. I have 4 HDD in it and I see [UUUU] indicating it is ok
[21:47] <Guma> Before I reboot host I do shutdown manually guest.
[21:48] <Guma> Not sure where to start about this problem. I am using Intel RAID build to Asus motherboard