[00:24] !no, neon is KDE Neon ( http://neon.kde.org/ ) is a KDE project to package the latest stable and development versions of KDE on top of an Ubuntu base. As it is not an official Ubuntu or Kubuntu project, please use #kde-neon for discussion and support. [00:24] I'll remember that dax [00:24] !no, neon is KDE Neon ( http://neon.kde.org/ ) is a KDE project to package the latest stable and development versions of KDE software on top of an Ubuntu base. As it is not an official Ubuntu or Kubuntu project, please use #kde-neon for discussion and support. [00:24] I'll remember that dax [00:25] saw the user edition packages for it started building today, good chance i'll be switching from stretch+KDE to them [17:03] phanes_ seems to just want to sit and snark rather than actually fix his issue === mquin is now known as evilmquin === evilmquin is now known as mquin [18:46] popey: known troll === StaffUnicorn is now known as nhandler [20:00] hello [20:00] why was i just banned in #ubuntu? [20:00] hello phanes_ [20:00] for refusing to drop a topic when asked multiple times [20:01] you said it was offtopic-- it was not, and you are misinforming users [20:01] so I forwarded you to this channel [20:01] the topic is not adhoc defined by you [20:01] if it is please correct me [20:01] the topic is set in the /topic command [20:01] correct [20:01] can you point out where it says that's offtopic? [20:01] (as in output) [20:01] and in the IRC wiki pages, although they could do with a tidy up [20:01] because i checked the topic [20:01] and i checked the irc wiki [20:01] and none of that says its offtopic [20:02] particularly as you were discussing it in the context of providing support for #ubuntu [20:02] phanes_: common sense, getting into a debate about safe compiling of kernels for a user who has zero idea about what the problem is, let alone how to fix it, is offtopic [20:02] and not going to help anyone [20:02] so in this case you have redefined the topic and are enforcing that redefinition with a ban [20:02] which is why I said I'd be happy to discuss it in an offtopic channel, but not divert the channel from what he was working on [20:02] no, I'm applying common sense [20:02] thats a buzzword that doesn't actually mean anything [20:02] you're using it to bend the rules [20:03] please link me to where it says that it is offtopic [20:03] because i just cant find it in the links in the topic [20:03] you could always lift the ban and enforce the channel rules like you were brought here to do? [20:04] it's not a buzz word at all [20:04] and then we can talk about why you're wrong about this kernel thing [20:04] a user who is struggling to even describe a problem should not be looking at kernel compiliation for no reason [20:04] and discussing that in a busy channel infront of the user is not really going to help him is it [20:04] is that offtopic? [20:04] no [20:04] hence why I offered to do this offtopic [20:04] it is not offtopic though you just wanted to move it there [20:04] and then you lied and called it offtopic [20:04] I think I'll leave it here [20:05] you seem to want to argue rather than add value [20:05] no i want you to follow your own rules [20:05] talk to one of the other ops - or part the channel [20:05] and lift my ban [20:05] this is ego [20:05] i told you that you were wrong and misinforming users (and you are) and you banned me for it [20:05] and you dont even know why compiling a kernel is dangerous, you're just saying that [20:05] phanes_: ok - lets talk about how wrong I am [20:06] are all kernels backward compatible with all underlying software components, eg: libc and compilers (for example) [20:06] so, to start out, let's get it out -- i do this for a living [20:06] are they all compatible ? [20:07] in major release versions yes, for the most part -- if you cross major releases you might run into issues, but going from like 4.1.x to 4.3.x isn't going to be a huge issue and as long as you are compiling target and source in the same environment you'll be fine [20:07] phanes_: are they all compatible ? [20:07] yes or no [20:08] i gave you your answer, and you're talking to someone who gets paid to do just this and probably knows more about it than you do, so you may want to adjust your tone unless you have any, any, any justification for saying what youre saying prior to lifting my ban and then un-misinforming that user [20:08] are they all compatible, yes or no [20:09] you can compile almost any kernel with a modern libc and compiler, if you're doing legacy environment work then you want to be more careful -- in the context of a modern distro the answer is no, in the context of a legacy environment the answer is yes [20:09] are they all compatible, yes/no [20:10] then lets go a step deeper [20:10] i have answered your question [20:10] thoroughly [20:10] do they all work with all binary blob firmware components [20:10] such as the network card you can't get working [20:10] or the video card he can't get working [20:10] is there a range of compatability there ? [20:10] or is that open for all [20:11] no but you'd run into that with precompiled kernels -- and you would with libc/gcc as well, your issue is not an issue specific to compilation of a kernel [20:11] no you don't [20:11] as ubuntu ships supported compatible components [20:11] so the answer is "yes, there is a risk of incompatbilitu" [20:12] if that were true neither he or i would be in that channel [20:12] and i suspect you know this [20:12] now - what about the risk to the ubuntu package manager packages and dependencies [20:12] he doesn't know [20:12] thats why he's asking [20:12] he can't even describe his own problem, let alone compile a kernel [20:12] wait. he doesn't know that your issue is also applicable to precompiled kernels so that's why he's asking? you should read what im saying more closely [20:13] no, you should pay attention [20:13] he has no idea what his problem is [20:13] or what a solution is [20:13] ok but that's not offtopic, and you should tell him not to compile a kernel, not misinform the whole channel and pretend its offtopic [20:13] as I've just said - there are risks [20:13] such as the ones I've mentioned, the package manager, the dependencies the support implications [20:13] it wont break the package manager or dependencies [20:14] it wont break support either [20:14] it will as #ubuntu doesn't support custom kernels [20:14] and it will put risk on the package manager [20:14] there is no issue youve described not also applicable to distro-provided precompiled kernels [20:14] what risk? [20:14] espeically on the update-grub side of the install [20:14] i suspect someone told you this and you dont know why [20:14] and there isn't the risk as the distro packages provide compatability with each other [20:14] I think you need to stop saying that [20:14] and to be honest - I'm going to stop discussing this with you [20:15] I've tried to explain in reasonable detail [20:15] I tried multiple times to stop you in the channel before you want this route [20:15] ah, so when someone notices that youre making things up, they get banned and lied to [20:15] so I'll leave it there [20:15] not making anything up - this is a logged channel so you can see what I've said and why [20:15] and I'm pretty confident it stands up [20:15] can we please get intervention from another operator? this guy does not need to be in there [20:15] I think thats a wise move, one of the other operators can assist you [20:15] good evening [20:16] he is misinforming users and banning people when they point it out [20:16] phanes_: You expect ikonia to take what you say for granted, that you know what you are talking about. The same respect should be given to ikonia. The ban stays. [20:16] Please part the channel now. [20:16] what are you talking about i just explained that every issue he described is applicable to precompiled kernels [20:17] i am fucking ceh and rhce certified i know wtf im talking about, there is no abi or dependency breakage from compiling a kernel [20:17] in fact you get MORE breakage concerns from package-provided kernels because youre guessing at what libc version and gcc version was used to compile [20:17] this is widely known and documented [20:18] now, sorry for the expletives, but its extremely frustrating to have someoen correct you with known bad information and treat you like this [20:18] please lift the ban or i will blatantly evade [20:19] i have done nothing wrong but point out that he was misinforming users [20:19] in a self-compiled kernel there can be no libc or gcc mismatch because you are literally using the system versions to do it [20:20] in a precompiled kernel you're hoping they used your same versions. this is entry-level linux [20:20] it was also ontopic, which is what the ban was for [20:21] now please, all of you, follow your own channel policies [20:23] lift the ban [20:23] read up on the kernel [20:24] i really dont want to have to waste a vps just to access one channel just because your op can't follow the rules [20:25] or do the ops not have to? [20:27] The ban is not going to be lifted anytime soon. Please part this channel. [20:28] i have purchased a vPS for the purpose of evading the ban. im already back in [20:28] pleased educate yourselves on proper system administration [20:28] this was stupid [20:29] and you guys should be ashamed of yourselves for treating your seniors like this [20:29] and i am obviously a senior [20:30] also, congratulations, this log is getting published [20:30] !logs [20:30] Official channel logs can be found at http://irclogs.ubuntu.com/ . LoCo channels are now logged there too. Meeting logs from meetingology at http://ubottu.com/meetingology/logs/ [20:41] yowza [21:41] i got banned in #ubuntu trying to find out so please go gentle [21:41] from #x [21:42] oh not that troll [21:43] As long as he is not a problem we should let him be [21:43] yea [21:45] i really dont like that "as long as he is not beeing a real pain in this channel it doesnt matter that he is insulting, threatening and plain just demotivating users and ops in other channels" policy. [21:45] i really dont think that is CoC compliant [21:47] IF he is not a problem, k1l_ [21:50] the basic routing issue he has should be a doddle for an RHCE [21:51] k1l_: "Don't fix what's not broken", tends to mean the line is quite tight on him, but if he doesn't do anything bad no point banning. [21:53] if he started any crap in #kubuntu I would mute him as soon as I noticed [21:53] that said, if he was polite and helpful, I would just let him be [22:46] I wondered how it would take for him to go back to standard behaviour [23:19] so it would appear he's still ranting on about this in other channels [23:20] and doesn't understand basic networking such as the link-local address range and fall back [23:20] I suspect pretty much everything he's saying is bluff [23:21] i gave up when he couldn't do simple things like pastebin things [23:21] which other channels? [23:21] for someone as skilled, certified and experienced as he claims, he's lacking the basics in every department [23:21] ##networking [23:22] b/c i would not call his messages in #xubuntu ranting personally [23:22] ah [23:22] everytime someone asks a question he doesn't know the answer to, he blames ubuntu, the operators and the fact that I don't know how to compile a kernel [23:22] despte the fact that I've never spoken [23:22] so it would appear he's trying to provoke for sport [23:22] and hide his lack of knowledge