Re: [gentoo-user] [~and64] Headsup for google-chrome users
Mick wrote: On Friday 22 May 2015 00:49:54 Dale wrote: Mike Gilbert wrote: On Thu, May 21, 2015 at 3:44 PM, waben...@gmail.com wrote: walt w41...@gmail.com wrote: [...] Then, after I figured out that CONFIG_USER_NS is a kernel config item, requiring reinstallation of my kernel, I wasted more time figuring out (for the n'th time) that you shouldn't just change a single kernel config item and do make because that shortcut can break important things. No, you should do make clean first, and then do make etc. [...] I haven't done a make clean for years when I compiled a kernel and I never had any problems. Then you have not made any critical config changes, or you have been very lucky. Then so have I. I have changed one thing a lot of times over the years, run make and it work fine. Most of the time, it is when emerge spits out that a option is needed for a package to work. Honestly, this is the first time I recall hearing this should even be done. Dale :-) :-) I knew it should be done, but thought it ought to be done when you want to start with a clean slate and I didn't know if I needed to do this, or what a clean slate involved exactly. Since I run 'make oldconfig' I always assumed that I don't need a clean slate, plus updating minor versions takes seconds. So I'm the 3rd one in row to state that I haven't had any deleterious effects that I noticed. When I first emerge a new kernel, I run make mrproper to get a good clean start. I then copy my old config over to the new kernel. After that, I don't run clean or mrproper again for that version. If I change something, I run menuconfig, make the change, run make all make modules_install and then copy it over. I don't even want to try and count the number of times I've changed just one setting because some package needed it before it would update. Sometimes, I may change a kernel several times before I update to a new version. I been doing this the same way ever since about 2003. As some know, if it would cause a problem, I should have found it by now, at least once. ;-) Dale :-) :-)
Re: [gentoo-user] [~and64] Headsup for google-chrome users
On Fri, 22 May 2015 02:53:17 -0500, Dale wrote: So I'm the 3rd one in row to state that I haven't had any deleterious effects that I noticed. Make that 4. When I first emerge a new kernel, I run make mrproper to get a good clean start. There's no point in that. When you have just emerged the sources, there is nothing for mrproper to remove. -- Neil Bothwick B?#$^f, said Pooh, as line noise garbled his transmission. pgpy2uirGsAsf.pgp Description: OpenPGP digital signature
Re: [gentoo-user] [~and64] Headsup for google-chrome users
Neil Bothwick wrote: On Fri, 22 May 2015 02:53:17 -0500, Dale wrote: So I'm the 3rd one in row to state that I haven't had any deleterious effects that I noticed. Make that 4. When I first emerge a new kernel, I run make mrproper to get a good clean start. There's no point in that. When you have just emerged the sources, there is nothing for mrproper to remove. Sometimes, it prints that it removed stuff. Usually not but once in a while it says it removed something. No clue what that was tho. Dale :-) :-)
Re: [gentoo-user] [~and64] Headsup for google-chrome users
On Friday 22 May 2015 00:49:54 Dale wrote: Mike Gilbert wrote: On Thu, May 21, 2015 at 3:44 PM, waben...@gmail.com wrote: walt w41...@gmail.com wrote: [...] Then, after I figured out that CONFIG_USER_NS is a kernel config item, requiring reinstallation of my kernel, I wasted more time figuring out (for the n'th time) that you shouldn't just change a single kernel config item and do make because that shortcut can break important things. No, you should do make clean first, and then do make etc. [...] I haven't done a make clean for years when I compiled a kernel and I never had any problems. Then you have not made any critical config changes, or you have been very lucky. Then so have I. I have changed one thing a lot of times over the years, run make and it work fine. Most of the time, it is when emerge spits out that a option is needed for a package to work. Honestly, this is the first time I recall hearing this should even be done. Dale :-) :-) I knew it should be done, but thought it ought to be done when you want to start with a clean slate and I didn't know if I needed to do this, or what a clean slate involved exactly. Since I run 'make oldconfig' I always assumed that I don't need a clean slate, plus updating minor versions takes seconds. So I'm the 3rd one in row to state that I haven't had any deleterious effects that I noticed. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] [~and64] Headsup for google-chrome users
On 05/22/2015 10:21 AM, Dale wrote: I have always copied mine over manually too. I keep quite a few spares laying around, just in case. I had one that got corrupted a long time ago. After I booted another kernel and looked at the one I was trying to boot, it was only a few kilo bytes worth. No clue what happened there. I just copied it over again and the size was right. Then it booted fine. Weird. I've manually copied the kernel .config over and had that happen. I remember thinking why is it so small, then I opened it with vim and went O. ;-) Dan
Re: [gentoo-user] [~and64] Headsup for google-chrome users
Daniel Frey wrote: On 05/22/2015 10:21 AM, Dale wrote: I have always copied mine over manually too. I keep quite a few spares laying around, just in case. I had one that got corrupted a long time ago. After I booted another kernel and looked at the one I was trying to boot, it was only a few kilo bytes worth. No clue what happened there. I just copied it over again and the size was right. Then it booted fine. Weird. I've manually copied the kernel .config over and had that happen. I remember thinking why is it so small, then I opened it with vim and went O. ;-) Dan . Well, I think something went goofy at some point since it wasn't the config. I did try to open it and got the usual garbage stuff not a text file. If I recall correctly, that was on a drive that later died. It very well could be that it just went corrupt. Also, that kernel had been used before, it just didn't work that time. It's been a while back and was on another machine. So far, the last time I had a kernel fail on first boot was waaay back when I was first creating my own kernels and was learning what options were a must have. That would be back around 2003 or so. Dang, I'm getting to be a old Linux fart. ROFL :-( Dale :-) :-)
Re: [gentoo-user] [~and64] Headsup for google-chrome users
On 22/05/2015 10:38, Neil Bothwick wrote: On Fri, 22 May 2015 02:53:17 -0500, Dale wrote: So I'm the 3rd one in row to state that I haven't had any deleterious effects that I noticed. Make that 4. /raises hand: 5 Seems like there's a lot of cargo-cult advice around about how to configure a kernel When I first emerge a new kernel, I run make mrproper to get a good clean start. There's no point in that. When you have just emerged the sources, there is nothing for mrproper to remove. -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] [~and64] Headsup for google-chrome users
On Friday 22 May 2015 09:38:46 Neil Bothwick wrote: On Fri, 22 May 2015 02:53:17 -0500, Dale wrote: So I'm the 3rd one in row to state that I haven't had any deleterious effects that I noticed. Make that 4. When I first emerge a new kernel, I run make mrproper to get a good clean start. There's no point in that. When you have just emerged the sources, there is nothing for mrproper to remove. So, coming back to the OP, is it advisable to ignore this message: * Messages for package www-client/chromium-43.0.2357.65: [27/1984] * USER_NS is required for sandbox to work * Please check to make sure these options are set correctly. * Failure to do so may cause unexpected problems. which doesn't even advise where to find USER_NS, or will chromium no longer work as it did in the past? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] [~and64] Headsup for google-chrome users
On 22/05/2015 12:44, Mick wrote: On Friday 22 May 2015 09:38:46 Neil Bothwick wrote: On Fri, 22 May 2015 02:53:17 -0500, Dale wrote: So I'm the 3rd one in row to state that I haven't had any deleterious effects that I noticed. Make that 4. When I first emerge a new kernel, I run make mrproper to get a good clean start. There's no point in that. When you have just emerged the sources, there is nothing for mrproper to remove. So, coming back to the OP, is it advisable to ignore this message: No. It's in the ebuild and we assume the ebuild writer had a reason for putting it there. The usual reason is that upstream has said their code requires an option to be set. Where would you have gotten the idea that ignoring it is good advice? * Messages for package www-client/chromium-43.0.2357.65: [27/1984] * USER_NS is required for sandbox to work * Please check to make sure these options are set correctly. * Failure to do so may cause unexpected problems. which doesn't even advise where to find USER_NS, or will chromium no longer work as it did in the past? -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] [~and64] Headsup for google-chrome users
On Fri, May 22 2015, Alan McKinnon wrote: On 22/05/2015 10:38, Neil Bothwick wrote: On Fri, 22 May 2015 02:53:17 -0500, Dale wrote: So I'm the 3rd one in row to state that I haven't had any deleterious effects that I noticed. Make that 4. /raises hand: 5 ++1 allan
Re: [gentoo-user] [~and64] Headsup for google-chrome users
On Friday 22 May 2015 12:09:34 Alan McKinnon wrote: On 22/05/2015 12:44, Mick wrote: On Friday 22 May 2015 09:38:46 Neil Bothwick wrote: On Fri, 22 May 2015 02:53:17 -0500, Dale wrote: So I'm the 3rd one in row to state that I haven't had any deleterious effects that I noticed. Make that 4. When I first emerge a new kernel, I run make mrproper to get a good clean start. There's no point in that. When you have just emerged the sources, there is nothing for mrproper to remove. So, coming back to the OP, is it advisable to ignore this message: No. It's in the ebuild and we assume the ebuild writer had a reason for putting it there. The usual reason is that upstream has said their code requires an option to be set. Where would you have gotten the idea that ignoring it is good advice? Because the emerge did not stop to warn me about it, or require me to acknowledge before proceeding. Furthermore it tells me that bad things may happen, but doesn't explain what kind of bad things, referring to a URL if space does not allow. At this stage I am guessing that chromium's sandboxing mechanism is changed and it now requires a different memory allocation mechanism than what I had previously configured in my kernel. Having to configure my kernel to get a browser working sounds quite intrusive so I am worried some more. Looking at the changelog and then at bugs referred to there, I eventually arrived at CVE-2015-1252 [1] where the problem is explained: In any case, I think that something like this should invite user input at the start of the ebuild, rather than at the end? I haven't figured out yet if I will need to reinstall chromium after I have reconfigured my kernel ... in which case the warning should definitely come at the start of the ebuild. [1] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1252 -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] [~and64] Headsup for google-chrome users
On 05/22/2015 02:19 AM, Alan McKinnon wrote: On 22/05/2015 10:38, Neil Bothwick wrote: On Fri, 22 May 2015 02:53:17 -0500, Dale wrote: So I'm the 3rd one in row to state that I haven't had any deleterious effects that I noticed. Make that 4. /raises hand: 5 /raises hand too Make that 6. I've been compiling kernels since 2003 and never used make clean or make mrproper. I use make oldconfig all the time. I didn't even know about make install until I read this thread, I always manually copied kernels over. Dan
Re: [gentoo-user] [~and64] Headsup for google-chrome users
On Thursday, May 21, 2015 05:55:52 AM walt wrote: Thanks. I also saw that message, but after checking the kernel, ignored it! I just wasted some time figuring out this mess: I just updated google-chrome, which printed this confusing warning message: CONFIG_USED_NS not seen when it should be First, there's a typo: it should read CONFIG_USER_NS ^ Then, after I figured out that CONFIG_USER_NS is a kernel config item, requiring reinstallation of my kernel, I wasted more time figuring out (for the n'th time) that you shouldn't just change a single kernel config item and do make because that shortcut can break important things. No, you should do make clean first, and then do make etc. Then, after finishing that mess, you then need to re-install ati-drivers (if you use them) because CONFIG_USER_NS breaks the ati-drivers too. So, re-install ati-drivers, reboot, etc, all of which will make you late for work, like I am now :p
Re: [gentoo-user] [~and64] Headsup for google-chrome users
Daniel Frey wrote: On 05/22/2015 02:19 AM, Alan McKinnon wrote: On 22/05/2015 10:38, Neil Bothwick wrote: On Fri, 22 May 2015 02:53:17 -0500, Dale wrote: So I'm the 3rd one in row to state that I haven't had any deleterious effects that I noticed. Make that 4. /raises hand: 5 /raises hand too Make that 6. I've been compiling kernels since 2003 and never used make clean or make mrproper. I use make oldconfig all the time. I didn't even know about make install until I read this thread, I always manually copied kernels over. Dan . I have always copied mine over manually too. I keep quite a few spares laying around, just in case. I had one that got corrupted a long time ago. After I booted another kernel and looked at the one I was trying to boot, it was only a few kilo bytes worth. No clue what happened there. I just copied it over again and the size was right. Then it booted fine. Weird. Dale :-) :-)
Re: [gentoo-user] [~and64] Headsup for google-chrome users
On Thu, 21 May 2015 09:57:57 -0500, Dale wrote: No, you should do make clean first, and then do make etc. Doesn't make clean clear out your config? I've changed one thing before and just run make and it work just fine. No. % make help Cleaning targets: clean - Remove most generated files but keep the config and enough build support to build external modules mrproper- Remove all generated files + config + various backup files distclean - mrproper + remove editor backup and patch files -- Neil Bothwick Joystick: (n.) a device essential for performing business tasks and training exercises esp. favored by pilots, tank commanders, riverboat gamblers, and medieval warlords. pgp51vmIfrEPx.pgp Description: OpenPGP digital signature
Re: [gentoo-user] [~and64] Headsup for google-chrome users
On 21/05/2015 14:55, walt wrote: I just wasted some time figuring out this mess: I just updated google-chrome, which printed this confusing warning message: CONFIG_USED_NS not seen when it should be First, there's a typo: it should read CONFIG_USER_NS ^ Then, after I figured out that CONFIG_USER_NS is a kernel config item, requiring reinstallation of my kernel, I wasted more time figuring out (for the n'th time) that you shouldn't just change a single kernel config item and do make because that shortcut can break important things. No, you should do make clean first, and then do make etc. Then, after finishing that mess, you then need to re-install ati-drivers (if you use them) because CONFIG_USER_NS breaks the ati-drivers too. So, re-install ati-drivers, reboot, etc, all of which will make you late for work, like I am now :p Ah, the joys of using Gentoo and having to figure that shit out :-) At least you now know you are on par with maintainers of binary distros. And that makes you a rock star! -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] [~and64] Headsup for google-chrome users
On Thu, May 21, 2015 at 3:44 PM, waben...@gmail.com wrote: walt w41...@gmail.com wrote: [...] Then, after I figured out that CONFIG_USER_NS is a kernel config item, requiring reinstallation of my kernel, I wasted more time figuring out (for the n'th time) that you shouldn't just change a single kernel config item and do make because that shortcut can break important things. No, you should do make clean first, and then do make etc. [...] I haven't done a make clean for years when I compiled a kernel and I never had any problems. Then you have not made any critical config changes, or you have been very lucky.
Re: [gentoo-user] [~and64] Headsup for google-chrome users
On 05/21/15 10:57, Dale wrote: walt wrote: I just wasted some time figuring out this mess: I just updated google-chrome, which printed this confusing warning message: CONFIG_USED_NS not seen when it should be First, there's a typo: it should read CONFIG_USER_NS ^ Then, after I figured out that CONFIG_USER_NS is a kernel config item, requiring reinstallation of my kernel, I wasted more time figuring out (for the n'th time) that you shouldn't just change a single kernel config item and do make because that shortcut can break important things. No, you should do make clean first, and then do make etc. Doesn't make clean clear out your config? I've changed one thing before and just run make and it work just fine. Dale :-) :-) No, make clean does not clear your config. It depends on what you change - I guess their Makefiles/Kconfig doesn't specify all the dependencies for CONFIG_USER_NS. If you're on a decent machine, the kernel builds pretty quick anyways, and a clean build will always be correct. Alec
Re: [gentoo-user] [~and64] Headsup for google-chrome users
walt wrote: I just wasted some time figuring out this mess: I just updated google-chrome, which printed this confusing warning message: CONFIG_USED_NS not seen when it should be First, there's a typo: it should read CONFIG_USER_NS ^ Then, after I figured out that CONFIG_USER_NS is a kernel config item, requiring reinstallation of my kernel, I wasted more time figuring out (for the n'th time) that you shouldn't just change a single kernel config item and do make because that shortcut can break important things. No, you should do make clean first, and then do make etc. Doesn't make clean clear out your config? I've changed one thing before and just run make and it work just fine. Dale :-) :-)
Re: [gentoo-user] [~and64] Headsup for google-chrome users
On Thu, May 21, 2015 at 8:55 AM, walt w41...@gmail.com wrote: I just wasted some time figuring out this mess: I just updated google-chrome, which printed this confusing warning message: CONFIG_USED_NS not seen when it should be First, there's a typo: it should read CONFIG_USER_NS ^ Sorry about that. It's been fixed.
Re: [gentoo-user] [~and64] Headsup for google-chrome users
Mike Gilbert wrote: On Thu, May 21, 2015 at 3:44 PM, waben...@gmail.com wrote: walt w41...@gmail.com wrote: [...] Then, after I figured out that CONFIG_USER_NS is a kernel config item, requiring reinstallation of my kernel, I wasted more time figuring out (for the n'th time) that you shouldn't just change a single kernel config item and do make because that shortcut can break important things. No, you should do make clean first, and then do make etc. [...] I haven't done a make clean for years when I compiled a kernel and I never had any problems. Then you have not made any critical config changes, or you have been very lucky. Then so have I. I have changed one thing a lot of times over the years, run make and it work fine. Most of the time, it is when emerge spits out that a option is needed for a package to work. Honestly, this is the first time I recall hearing this should even be done. Dale :-) :-)
Re: [gentoo-user] [~and64] Headsup for google-chrome users
walt w41...@gmail.com wrote: [...] Then, after I figured out that CONFIG_USER_NS is a kernel config item, requiring reinstallation of my kernel, I wasted more time figuring out (for the n'th time) that you shouldn't just change a single kernel config item and do make because that shortcut can break important things. No, you should do make clean first, and then do make etc. [...] I haven't done a make clean for years when I compiled a kernel and I never had any problems. -- Regards wabe
