Re: [gentoo-user] Re: Trouble on the horizon!
On 25/09/18 05:49, Mark David Dumlao wrote: > On Mon, Sep 24, 2018 at 6:34 PM Nikos Chantziaras wrote: >> >> On 24/09/2018 13:11, R0b0t1 wrote: >>> On Mon, Sep 24, 2018 at 11:01 AM, Nikos Chantziaras >>> wrote: To me it looks like youtubers and some sites trying to make money through clickbait? >>> >>> If you had not heard of it elsewhere the Linux code of conduct was >>> amended. It makes the CoC similar to those of other projects where >>> there are a number of (usually nontechnical) contributors who identify >>> as a champion of social justice. >>> [...] >> Well, if kernel developers are fine with that, then I don't see how >> that's relevant to anyone who isn't a kernel dev. If they want to adopt >> social justice politics, that's really their prerogative. >> If you read LWN, actually a lot of kernel devs aren't fine with it - they didn't have any say, and don't like it. > > Actually, social justice politics didn't seem to have anything to do > with the CoC > adoption. It was more of Linus taking a backseat (due to how he self-assessed > his vacation behavior) and pretty soon after, they adopted CoC, most likely as > some kind of "standardization" > > Barely a week has passed since the CoC though, and already there are political > manuevers to oust high-profile kernel devs How are they going to achieve that? As has been pointed out, if Linus continues to trust them, and treat them as lieutenants, there's nothing the SJWs can do. There's also been comments that - actually - one person in particular who's been a bit of an SJW is actually in breach of the CoC herself, so those manoeuvres could backfire spectacularly. > to the point that some contributors > have started talks on exercising their copyright privileges and > withholding their > code. Which they have a right to do, by the way, if they feel the foundation > has betrayed them. Withholding their code FROM WHOM? > > So as esr has put it: >> First, let me confirm that this threat has teeth. I researched the relevant >> law >> when I was founding the Open Source Initiative. In the U.S. there is case law >> confirming that reputational losses relating to conversion of the rights of a >> contributor to a GPLed project are judicable in law. I do not know the case >> law >> outside the U.S., but in countries observing the Berne Convention without the >> U.S.’s opt-out of the “moral rights” clause, that clause probably gives the >> objectors an even stronger case. > > (http://esr.ibiblio.org/?p=8139) > > This is not a little online trollfest that only affects kernel devs. > This can affect > literally everything. Biblical proportions, dogs and cats living together, > etc. > As we know from the SCOG case, pretty much everything is judicable in American law, even when they have absolutely no case. Are you telling me that I can withdraw YOUR right to use my code, just because I dislike what some random 3rd party with no relationship to either of us has done? Surely that pretty blatantly falls foul of estoppel. Although of course that didn't stop SCOG ... Where's PJ when you need her ... As for "moral rights", I don't think that actually grants any extra rights or anything. It mostly says that if I am the author of something, I can NOT sign away my right to be credited as such. You can buy the copyright off me, at which point I have no rights to benefit further from the work, but you cannot buy the right to be credited as the author - that is not for sale under "moral rights" law. (Oh - and the linux trademark is apparently Linus' personal property, so that throws another hand grenade onto the table ... :-) Cheers, Wol
Re: [gentoo-user] ARM 17.0 profile change
Just a short update. The provided script worked like a charm!!! Thanks to all Devs involved. -- Dan On 22.09.2018 20:04, Corentin “Nado” Pazdera wrote: > September 22, 2018 5:36 PM, "Dan Johansson" wrote: > >> Hi, >> >> Today when I was preparing for a "emereg --update ..." on my Raspberry >> PI 2B I saw that there was a news item regarding >> "2018-09-07-arm-17-profile-migration" where it states (among other >> things) "In short, the tuple will change from >> armv7a-hardfloat-linux-gnueabi to >> armv7a-unknown-linux-gnueabihf or similar.". >> >> Today I have the profile set to "default/linux/arm/13.0/armv7a (dev)" >> and I have the following in make.conf >> CFLAGS="-O2 -pipe -march=armv7-a -mfpu=vfpv3-d16 -mfloat-abi=hard" >> CHOST="armv7a-hardfloat-linux-gnueabi" >> >> I am not 100% sure on what to set my profile & CHOST to for this Raspberry. >> >> So (some) of my questions are. >> 1) Which new profile should a use for a Raspberry PI 2B which runs as a >> headless "server" (i.e. now desktop environment running)? I suspect >> "default/linux/arm/17.0/armv7a" would be a good idea? >> 2) What would be the correct CFLAGS & CHOST in make.conf? > > Hi, > > The script linked in the news item should take care of that. > Don't forget to backup your packages (quickpkg */*) before doing the > migration, it will help in > case you need to rollback. > > Best regards, > Corentin “Nado” Pazdera > -- Dan Johansson *** This message is printed on 100% recycled electrons! ***
Re: [gentoo-user] OT: Noteworthy change in the way Chrome logs in
On Tuesday, 25 September 2018 13:29:14 BST Dale wrote: > Mick wrote: > > On Tuesday, 25 September 2018 12:02:48 BST Dale wrote: > >> Mick wrote: > >>> On Tuesday, 25 September 2018 03:11:38 BST Walter Dnes wrote: > On Mon, Sep 24, 2018 at 02:59:17PM +0100, Mick wrote > > > This is worse than I expected. OK, therefore never signing into > > Google's > > systems with Chromium is the only way to stop this invasion of > > privacy. > > Thankfully, we still have Firefox. ;-) > > Ahemm... > https://dustri.org/b/mozilla-is-still-screwing-around-with-privacy-in-f > ir > ef > ox.html > >>> > >>> Yes, there is this leaking agent running in FF, but I have (almost) > >>> disabled telemetry. The problem is this pesky entry which is shown as > >>> "locked" and therefore unable to be disabled in about:config > >>> > >>> Preference NameStatus Type Value > >>> = == === = > >>> toolkit.telemetry.enabled locked boolean true > >> > >> Just for giggles, I looked at my config and it shows a default status > >> and is set to false. Maybe it is a difference in version or could it be > >> a USE flag makes a difference or something else??? I'm on Firefox > >> 52.9.0. Maybe you are using the latest version. I'm stuck here due to > >> some add ons not ready for the newer versions. > >> > >> Dale > >> > >> :-) :-) > > > > I'm on 60.2.0 and although other telemetry entries are modifiable, the one > > I mention above is shown as locked. Apparently this is locked to 'true' > > for pre-release builds and 'false' for release builds: > > > > https://medium.com/georg-fritzsche/data-preference-changes-in-firefox-58-2 > > d5df9c428b5 > Ahhh. I was hoping that info might lead to a solution to it but I guess > not. Better to mention and it not matter than to not mention and it > would have helped. lol Heck, I get help from this list but I also try > to help when I can. All we can do is try. > > We tried. ;-) > > Dale > > :-) :-) Yes, this one is hardcoded and there doesn't seem to be a workaround, other than modifying the source code. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] stage3 does not have Gentoo signing keys, which is unacceptable!
On 25.09.18 08:15, gevisz wrote: > Gentoo handbook contains instructions that lead to downloading and > using unverified portage tree that is unacceptable [...] See https://bugs.gentoo.org/597918 (filed almost two years ago). -Ralph
Re: [gentoo-user] Specific MAKEOPTS for one package
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Thanks Dale and Michael, that was exactly I was searching for. (I think. ;-) Am Di den 25. Sep 2018 um 15:00 schrieb Peter Humphrey: > On Tuesday, 25 September 2018 14:25:50 BST Klaus Ethgen wrote: > > > Is there an option to set -j1 just for firefox package? (and rust, that > > has the same problem)? > > As Dale and Michael said, but you may find -j2 acceptable; It's what I use > for > everything here. No. Firefox and Rust is such a beast. It kills my machine even with -j2. Regards Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Comment: Charset: ISO-8859-1 iQGzBAEBCgAdFiEEMWF28vh4/UMJJLQEpnwKsYAZ9qwFAluqQKkACgkQpnwKsYAZ 9qz/fAwAi+ocD3k/0MlpsXn67vhM6vSYvZM9cqhWcDwhxZhRbjgmjYgfpeOe8JhE Rey7lrqm/K2HtNZQXSOWiR/pa4Qkgoa8fgV+eWROfYQsQeRM95AzMU+aBMr353BI mW1BWLzHBDt4N7zk9VIRDDji/2sqohpqyRo9AzzAmJMVtFEccJQjQO/ppcz1eMfg 4DdxBVB7UNoa35jKttCBMl4aEjHtYmw48WRNqjnZA1rnEgozLNn/R74uxfoILQRY 58qBZZjBucO7GSg6X9S8OAOosJmYxpXcih4uejiiWyKiUBN+JZo8XHrhyw2kUHZ0 dy8rSqx6cTE5ga0t5YClwlWxYz/l6iaQPqPG7IRZZUAz1Mfh4Dyc7SIcxA6eu0Z+ lYGxq6ZhXARxds/bjDGYdKK1lXS+AUvQCT3t8V8VwdmIV2yuPmC2Gtt2yiXiU3y8 ns0mel1hm8o16T1eprrQGahhc3ooBJrcE3/hCyIAYyz/RMyHfXzM4M9RVx1k7V7i JEHMQsoZ =qjIU -END PGP SIGNATURE-
Re: [gentoo-user] Specific MAKEOPTS for one package
On Tuesday, 25 September 2018 14:25:50 BST Klaus Ethgen wrote: > Is there an option to set -j1 just for firefox package? (and rust, that > has the same problem)? As Dale and Michael said, but you may find -j2 acceptable; It's what I use for everything here. -- Regards, Peter.
Re: [gentoo-user] Specific MAKEOPTS for one package
Klaus Ethgen wrote: > Hi Folks, > > I have set MAKEOPTS="-j3" in my make.conf. That is great for most > packages but when I compile firefox that makes my box exploding as it > consumes simply to much RAM. > > Is there an option to set -j1 just for firefox package? (and rust, that > has the same problem)? > > Regards > Klaus I think you are looking for this: https://wiki.gentoo.org/wiki//etc/portage/package.env It's been a while since I've had to do this but I'm fairly sure that will do what you want. Hope that helps. Dale :-) :-)
Re: [gentoo-user] Specific MAKEOPTS for one package
On 09/25/2018 09:25 AM, Klaus Ethgen wrote> > Is there an option to set -j1 just for firefox package? (and rust, that > has the same problem)? > https://wiki.gentoo.org/wiki//etc/portage/package.env
[gentoo-user] Specific MAKEOPTS for one package
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Folks, I have set MAKEOPTS="-j3" in my make.conf. That is great for most packages but when I compile firefox that makes my box exploding as it consumes simply to much RAM. Is there an option to set -j1 just for firefox package? (and rust, that has the same problem)? Regards Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Comment: Charset: ISO-8859-1 iQGzBAEBCgAdFiEEMWF28vh4/UMJJLQEpnwKsYAZ9qwFAluqN1YACgkQpnwKsYAZ 9qx9yQv/apT33rL87QFc7fwVCeIdSYE0VYHxyYpsh7W1lrgS2RiAqITpzY/cddXx CXe6ElUy86abSF+r4JCePuJ1Chg4aW2VT7Kwz36yxv7H1kGjViAnydXmFpVSeqd5 LUzKo9PLadNYg+nic0H2m/ssSfO2J0uabgPXXSN7wbDZUPiinglCG7sLtfJdLWqB vHeN6CamNfFgWX7AjOO+CU1PDqurHjNcsDyVxe48G11+9idqcHdzitl7q0Qw58JE scyuRCzWuOzM6g4ck59NRcTe9qKGYDVog7zC4/6r+4JEwygE+/IujwLyR/G6f4qC 1eg3Bj9lhTBIUgjoMNrhsccq37/xP+kicRaKYYH4GnnT+hB/9cviruXQHFOQL9kb ukalz5kJdSrsuiyJSetu6hjTnSASiVt5cxaO07uJPVzNS063KDylM+x/vuJwhkbz pt0IUBVUbn0Bs2L664sFYMBijgojeOH3zZCjQffa7+e92Izxzllt1494lVH4dDJh X5TNwDL6 =H7z8 -END PGP SIGNATURE-
Re: [gentoo-user] OT: Noteworthy change in the way Chrome logs in
Mick wrote: > On Tuesday, 25 September 2018 12:02:48 BST Dale wrote: >> Mick wrote: >>> On Tuesday, 25 September 2018 03:11:38 BST Walter Dnes wrote: On Mon, Sep 24, 2018 at 02:59:17PM +0100, Mick wrote > This is worse than I expected. OK, therefore never signing into > Google's > systems with Chromium is the only way to stop this invasion of privacy. > Thankfully, we still have Firefox. ;-) Ahemm... https://dustri.org/b/mozilla-is-still-screwing-around-with-privacy-in-fir ef ox.html >>> Yes, there is this leaking agent running in FF, but I have (almost) >>> disabled telemetry. The problem is this pesky entry which is shown as >>> "locked" and therefore unable to be disabled in about:config >>> >>> Preference NameStatus Type Value >>> = == === = >>> toolkit.telemetry.enabled locked boolean true >> Just for giggles, I looked at my config and it shows a default status >> and is set to false. Maybe it is a difference in version or could it be >> a USE flag makes a difference or something else??? I'm on Firefox >> 52.9.0. Maybe you are using the latest version. I'm stuck here due to >> some add ons not ready for the newer versions. >> >> Dale >> >> :-) :-) > I'm on 60.2.0 and although other telemetry entries are modifiable, the one I > mention above is shown as locked. Apparently this is locked to 'true' for > pre-release builds and 'false' for release builds: > > https://medium.com/georg-fritzsche/data-preference-changes-in-firefox-58-2d5df9c428b5 > Ahhh. I was hoping that info might lead to a solution to it but I guess not. Better to mention and it not matter than to not mention and it would have helped. lol Heck, I get help from this list but I also try to help when I can. All we can do is try. We tried. ;-) Dale :-) :-)
Re: [gentoo-user] OT: Noteworthy change in the way Chrome logs in
On Tuesday, 25 September 2018 12:02:48 BST Dale wrote: > Mick wrote: > > On Tuesday, 25 September 2018 03:11:38 BST Walter Dnes wrote: > >> On Mon, Sep 24, 2018 at 02:59:17PM +0100, Mick wrote > >> > >>> This is worse than I expected. OK, therefore never signing into > >>> Google's > >>> systems with Chromium is the only way to stop this invasion of privacy. > >>> Thankfully, we still have Firefox. ;-) > >> > >> Ahemm... > >> https://dustri.org/b/mozilla-is-still-screwing-around-with-privacy-in-fir > >> ef > >> ox.html > > > > Yes, there is this leaking agent running in FF, but I have (almost) > > disabled telemetry. The problem is this pesky entry which is shown as > > "locked" and therefore unable to be disabled in about:config > > > > Preference NameStatus Type Value > > = == === = > > toolkit.telemetry.enabled locked boolean true > > Just for giggles, I looked at my config and it shows a default status > and is set to false. Maybe it is a difference in version or could it be > a USE flag makes a difference or something else??? I'm on Firefox > 52.9.0. Maybe you are using the latest version. I'm stuck here due to > some add ons not ready for the newer versions. > > Dale > > :-) :-) I'm on 60.2.0 and although other telemetry entries are modifiable, the one I mention above is shown as locked. Apparently this is locked to 'true' for pre-release builds and 'false' for release builds: https://medium.com/georg-fritzsche/data-preference-changes-in-firefox-58-2d5df9c428b5 -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] OT: Noteworthy change in the way Chrome logs in
Mick wrote: > On Tuesday, 25 September 2018 03:11:38 BST Walter Dnes wrote: >> On Mon, Sep 24, 2018 at 02:59:17PM +0100, Mick wrote >> >>> This is worse than I expected. OK, therefore never signing into Google's >>> systems with Chromium is the only way to stop this invasion of privacy. >>> Thankfully, we still have Firefox. ;-) >> Ahemm... >> https://dustri.org/b/mozilla-is-still-screwing-around-with-privacy-in-firef >> ox.html > Yes, there is this leaking agent running in FF, but I have (almost) disabled > telemetry. The problem is this pesky entry which is shown as "locked" and > therefore unable to be disabled in about:config > > Preference NameStatus Type Value > = == === = > toolkit.telemetry.enabled locked boolean true > Just for giggles, I looked at my config and it shows a default status and is set to false. Maybe it is a difference in version or could it be a USE flag makes a difference or something else??? I'm on Firefox 52.9.0. Maybe you are using the latest version. I'm stuck here due to some add ons not ready for the newer versions. Dale :-) :-)
Re: [gentoo-user] OT: Noteworthy change in the way Chrome logs in
On Tuesday, 25 September 2018 03:11:38 BST Walter Dnes wrote: > On Mon, Sep 24, 2018 at 02:59:17PM +0100, Mick wrote > > > This is worse than I expected. OK, therefore never signing into Google's > > systems with Chromium is the only way to stop this invasion of privacy. > > Thankfully, we still have Firefox. ;-) > > Ahemm... > https://dustri.org/b/mozilla-is-still-screwing-around-with-privacy-in-firef > ox.html Yes, there is this leaking agent running in FF, but I have (almost) disabled telemetry. The problem is this pesky entry which is shown as "locked" and therefore unable to be disabled in about:config Preference NameStatus Type Value = == === = toolkit.telemetry.enabled locked boolean true -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] march cflag for Intel Pentium Dual-Core E2160 SLA8Z Malay processor
вт, 25 сент. 2018 г. в 7:07, gevisz : > > вс, 23 сент. 2018 г. в 10:10, Walter Dnes : > > > > On Thu, Sep 20, 2018 at 01:00:39AM +0300, gevisz wrote > > > , 19 . 2018 ??. ?? 11:38, Walter Dnes : > > > > > > According to > > > > http://www.cpu-world.com/sspec/SL/SLA8Z.html it has... > > > > > > > > MMX SSE SSE2 SSE3 SSSE3 > > > > > > Do you mean that it would be enough to set > > > CFLAGS="-O2 -pipe mmx sse sse2 sse3 ssse3" > > > without setting the march cflag at all? > > > > Yes, that would work. Remember also to include in make.conf > > > > CPU_FLAGS_X86="mmx mmxext sse sse2 sse3 ssse3" > > The target processor does not support mmxext. Strange enough but cpuid2cpuflags shows that it does: # cpuid2cpuflags CPU_FLAGS_X86: mmx mmxext sse sse2 sse3 ssse3 > > In your jpeg image, I see that the flags include mmx, sse, sse2, pni, > > and ssse3. "pni" == "Prescott New Instructions" == "SSE3". Looking at > > https://gcc.gnu.org/onlinedocs/gcc-7.3.0/gcc/x86-Options.html#x86-Options > > I suggest "-march=core2" with CPU_FLAGS_X86 same as above. The "core2" > > option uses MMX, SSE, SSE2, SSE3 and SSSE3 instructions, all of which > > show up in the listing on your jpeg. > > Thank you. Looking into https://wiki.gentoo.org/wiki/Safe_CFLAGS#Intel > I also concluded that for the target processor I should set "-march=core2" > but I did not know that core2 option is exactly equivalent to setting mmx, > sse, sse2, sse3 and ssse3 instructions. > > So, I decided to spend a day to get my hands on the target computer > and compile everything on it with "-march=native" no matter how much > time it takes. > > To conclude this thread, I will post the output of the commands > suggested in this thread later, after the system install will be finished, > just in case somebody will need them in the future.
Re: [gentoo-user] Re : kernel delay
On Monday, 24 September 2018 23:55:31 BST Philip Webb wrote: > 180924 J. Roeleveld wrote: > > On Monday, September 24, 2018 2:42:49 PM CEST Philip Webb wrote: > >> I did note in a msg to this list earlier this year (2018) > >> that there had been no kernel stabilised by Gentoo since spring 2017, > >> which suggested there had been some decline in kernel quality. > > > > Gentoo-sources-4.14.65 is stable in the tree. Which is quite recent. > > Which are you referring to? > > I wrote above 'had', not 'has' : look at the list archive for details. [OT] Unfortunately, Americans (and those others who have learned English from Americans) don't understand the pluperfect. They've thrown out four entire verb tenses just in my lifetime. [/OT] -- Regards, Peter.
Re: [gentoo-user] Trouble on the horizon!
вт, 25 сент. 2018 г. в 10:12, J. Roeleveld : > > On Tuesday, September 25, 2018 8:23:53 AM CEST gevisz wrote: > > вт, 25 сент. 2018 г. в 9:15, J. Roeleveld : > > > On September 25, 2018 4:36:27 AM UTC, gevisz wrote: > > > >пн, 24 сент. 2018 г. в 21:24, J. Roeleveld : > > > >> On Monday, September 24, 2018 2:42:49 PM CEST Philip Webb wrote: > > > >> > I did note in a msg to this list earlier this year (2018) > > > >> > that there had been no kernel stabilised by Gentoo > > > >> > since spring 2017, which suggested there had been some > > > >> > decline in kernel quality. > > > >> > > > >> Gentoo-sources-4.14.65 is stable in the tree. Which is quite recent. > > > > > > > >After I configured gentoo-sources-4.14.52 kernel with make oldconfig, > > > >it even could not shut down the computer. So, I came to the same > > > >decision about kernel quality and masked everything later than > > > >gentoo-sources-4.9.95. (My 5 cents. :) > > > > > > That is interesting. > > > I did not have that issue with .52 nor with .65. > > > > > > Where does the shutdown hang? > > > > Thank you for replying to my comment. Unfortunately, I already do not > > remember exactly what happend after the usual "shutdown -h now" > > command but as far as I can remember, it did not switched off the power > > at the end of the shutdown process. > > I did have this with older kernels. Think it's caused by missing ACPI options. My previous kernel was 4.9.95 and the system shut down ok with it. Then I configured 4.14.52 using make oldconfig and the old .config from 4.9.95 kernel. And, after the usual compilation and installation of the new kernel, the system could not shut down. To not clutter this mailing list, I will send the both kernel configutations only to your e-mail adress now.
Re: [gentoo-user] Trouble on the horizon!
On Tuesday, September 25, 2018 8:23:53 AM CEST gevisz wrote: > вт, 25 сент. 2018 г. в 9:15, J. Roeleveld : > > On September 25, 2018 4:36:27 AM UTC, gevisz wrote: > > >пн, 24 сент. 2018 г. в 21:24, J. Roeleveld : > > >> On Monday, September 24, 2018 2:42:49 PM CEST Philip Webb wrote: > > >> > I did note in a msg to this list earlier this year (2018) > > >> > that there had been no kernel stabilised by Gentoo since spring > > > > > >2017, > > > > > >> > which suggested there had been some decline in kernel quality. > > >> > > >> Gentoo-sources-4.14.65 is stable in the tree. Which is quite recent. > > > > > >After I configured gentoo-sources-4.14.52 kernel with make oldconfig, > > >it even could not shut down the computer. So, I came to the same > > >decision about kernel quality and masked everything later than > > >gentoo-sources-4.9.95. (My 5 cents. :) > > > > That is interesting. > > I did not have that issue with .52 nor with .65. > > > > Where does the shutdown hang? > > Thank you for replying to my comment. Unfortunately, I already do not > remember exactly what happend after the usual "shutdown -h now" > command but as far as I can remember, it did not switched off the power > at the end of the shutdown process. I did have this with older kernels. Think it's caused by missing ACPI options. -- Joost
Re: [gentoo-user] Trouble on the horizon!
вт, 25 сент. 2018 г. в 9:15, J. Roeleveld : > > On September 25, 2018 4:36:27 AM UTC, gevisz wrote: > >пн, 24 сент. 2018 г. в 21:24, J. Roeleveld : > >> On Monday, September 24, 2018 2:42:49 PM CEST Philip Webb wrote: > >> > I did note in a msg to this list earlier this year (2018) > >> > that there had been no kernel stabilised by Gentoo since spring > >2017, > >> > which suggested there had been some decline in kernel quality. > >> > >> Gentoo-sources-4.14.65 is stable in the tree. Which is quite recent. > > > >After I configured gentoo-sources-4.14.52 kernel with make oldconfig, > >it even could not shut down the computer. So, I came to the same > >decision about kernel quality and masked everything later than > >gentoo-sources-4.9.95. (My 5 cents. :) > > That is interesting. > I did not have that issue with .52 nor with .65. > > Where does the shutdown hang? Thank you for replying to my comment. Unfortunately, I already do not remember exactly what happend after the usual "shutdown -h now" command but as far as I can remember, it did not switched off the power at the end of the shutdown process.
[gentoo-user] stage3 does not have Gentoo signing keys, which is unacceptable!
Yesterday, I have found out that the first invocation of emerge-webrsync command can not download a snapshot of the portage tree if webrsync-gpg feature has been set in make.conf because stage3 does not have Gentoo signing keys and I can not install Gentoo package with Gentoo signing keys because there is no portage tree in stage3. (Just to remind: according to Gentoo handbook, the first invocation of emege-webrsync command is done after chrooting.) After disabling webrsync-gpg feature in make.conf emerge-wibrsync command worked as described in Gentoo handbook. However, as a result, the downloaded portage tree has not been verified! So, Gentoo handbook contains instructions that lead to downloading and using unverified portage tree that is unacceptable, especially taking into account the security issues Gentoo already had this year! P.S. I now recall that I hit the same issue in 2013 and earlier this year as well. Than I had to download, verify and untar a snapshot of the portage tree before chrooting, what never has been described in the Gentoo handbook.
Re: [gentoo-user] Trouble on the horizon!
On September 25, 2018 4:36:27 AM UTC, gevisz wrote: >пн, 24 сент. 2018 г. в 21:24, J. Roeleveld : >> On Monday, September 24, 2018 2:42:49 PM CEST Philip Webb wrote: >> > I did note in a msg to this list earlier this year (2018) >> > that there had been no kernel stabilised by Gentoo since spring >2017, >> > which suggested there had been some decline in kernel quality. >> >> Gentoo-sources-4.14.65 is stable in the tree. Which is quite recent. > >After I configured gentoo-sources-4.14.52 kernel with make oldconfig, >it even could not shut down the computer. So, I came to the same >decision about kernel quality and masked everything later than >gentoo-sources-4.9.95. (My 5 cents. :) That is interesting. I did not have that issue with .52 nor with .65. Where does the shutdown hang? -- Joost -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
