Re: [gentoo-user] OpenSource Cellular
On Tue, Sep 10, 2019 at 06:33:23PM -0400, james wrote > I have an expensive cellualr service and a Galaxy Note 9. > It SUCKS really bad. I spend way too much time, just dealing with > a close source system and way too many vendor traps. I'm done with with, > and am curious if others have similar experiences and are interested in > alternatives, that we the citizens control. In my newly forming > approach, there is room for vendors and consumers and open source > developers. I'm in the USA, but, there is absolutely no reason this > movement I am proposing, could not sweep the globe, IP centric, free and > open. I think Lineage OS is what you're looking for https://lineageos.org/ Open source, etc. The main problem is that OEM's are locking down their phones, and making it harder to reflash firmware. Plus, you've got to find somebody who knows what they're doing, and won't brick your phone. I'd be interested in anything you come up with. Here's why... I'm in suburban Toronto Canada. The CRTC (our equivalant of the FCC) have gone full asshole mode and decreed that *ALL* cellphone alerts are sent at the Presidential Alert level (it's re-labelled "Emergency Alert" up here). *ALL* means *ALL*. Yes that includes missing kid or child custody dispute several hundred miles away. What doesn't help is that the OPP (Ontario Provincial Police) has a policy that *THE ENTIRE PROVINCE* gets a Presidential-Alert-masquarading-as-an-Amber-Alert when one is launched. For the American audience, Ontario is intermediate in size between Alaska and Texas. To add insult to injury, an "Amber Alert" often results in 3 (***THREE***) Presidential alert messages, even in the middle of the night... * The original unblockable alert, sent in English * Oh yeah, Canada is officially bilingual, let's send out an unblockable message in French half an hour later * an hour later the kid is found, so send out an unblockable "All Clear" Fortunately, the Canadian system is relatively new (spring 2018) and is only designed to work with LTE. By forcing my phone (Alcatel Go Flip) down to 3G-only, I avoid these alerts. Eventually, 3G will go away, so I want a solution for that day. So far in my neck of the woods, there have been... * 7 missing-kid alerts * 2 test alerts * 0 nuclear plant meltdowns * 0 chemical spills * 0 terrorist attacks * 0 tornadoes * 0 partidges-in-a-pear-tree-e-e-e-e-e -- Walter Dnes I don't run "desktop environments"; I run useful applications
[gentoo-user] OpenSource Cellular
I have an expensive cellualr service and a Galaxy Note 9. It SUCKS really bad. I spend way too much time, just dealing with a close source system and way too many vendor traps. I'm done with with, and am curious if others have similar experiences and are interested in alternatives, that we the citizens control. In my newly forming approach, there is room for vendors and consumers and open source developers. I'm in the USA, but, there is absolutely no reason this movement I am proposing, could not sweep the globe, IP centric, free and open. Here is my posting to gentoo-embedded, as embedded, secure devices, that are kept secure by the device owner, are central to what I am proposing. Strong filters and other technologies to keep criminal activity, defince by the governments, courts and citizens of the various countries, are paramount to my (our?) vision. But the inherent right to security and hardware and software, is the right of the citizen, and must supercede corporate profit schemes, criminal activities and maligned actions of the collective governments. Time for FREEDOM to reign! (spell checker on thunderbird temporarily broken...). Be at peace, James Horton, PE Here's the gentoo-embedded posting:: Hello gentoo embedded, I've had a galaxy note 9 on Verizon for a year. As a unix variant user, since the early 80's, IT SUCKS, really bad; time to fix. Since, I am addicted to most things gentoo centric, I have a new plan to ease my cellular pains. What I'm thinking is a flip-cell-phone, just for robust converversation. It'd be nice if it had a data-port (serial, ?) to tether any number of tablet/laptop gentoo devices to as one pathway for mobile communications. A reliable, gentoo-friend wireless service, USA centric, would be another great pathway to facilitate mobile communications. Eventually, I intend to add other form of wireless connectivity, the more the better. Surely some work has preceeded this effort, links and suggestions are most welcome. I intend to collaborate with others that are just tired of the OS on top of most cell phones. They hinder my thoughts and efforts, and imho, it's just time for the open source communities to pull together and create viable alternatives, so we can control the software we use for wireless and mobile communications. Surely others have already blazed this pathway? I also have experience with embedded sytems communications devices and microcontrollers, running minimalistic codes, so prototyping an open source cellular device, is not a problem, just a lot of work and funding for the prototypes. Respond, or send me private email, if your circumstances warrant. I'm very tired of the hardware/firmware/software offernings of the commercial vendors. I'm so pissed, I just may run for public office, with the only goal is to fix our F.up communicaitons systems, and furthermore, bring privacy back to citizens that have no criminal past. I surely hope, and pray, that a few other talented hardware/firmware centric folks, feel the pain, and are ready to legally fix this bullshit of subversives controlling the airwave. There is plent of action where commercial entities can prosper, and we, the citizens in good standing, can have freedom of hardware and software, that WE control. Time to action! sincerely, James Horton, PE
Re: [gentoo-user] Docker + systemd since cgroups v2
On Tue, 10 Sep 2019 12:00:07 -0400, John Covici wrote: > > On Tue, 10 Sep 2019 10:12:08 -0400, > Andrew Udvare wrote: > > > > For reference: uname -r: 5.2.13-gentoo, systemd version > > 243_rc2-r1[cgroup-hybrid], ACCEPT_KEYWORDS="~amd64" > > > > My system started failing to start running docker.service automatically and > > the logs weren't too helpful. Finally I ran dockerd on its own and found > > that it gave me this error message: > > > > Devices cgroup isn't mounted > > > > This is not too easy to diagnose as there seem to be a set of solutions but > > none of the main two worked for me. One involved setting 2 options on the > > kernel command line: > > > > cgroup_enable=memory swapaccount=1 > > > > And the other was to add USE="cgroup-hybrid" to systemd. I did this, but it > > too it did not work. > > > > The other solution is to simply mount the cgroup manually and this works > > but I did not see why I'd have to do that now when I never had to in the > > past. > > > > I actually had to add this to my command line: > > > > systemd.legacy_systemd_cgroup_controller=yes > > > > This has been noted in other distros but from what I can tell this is > > solely because runc has not been updated to be able to use cgroups v2. > > > > Anyone else ran into this issue? Is there something I am missing so I > > wouldn't need to pass a kernel command line option? > > > > Reference links: > > > > https://docs.docker.com/install/linux/linux-postinstall/#your-kernel-does-not-support-cgroup-swap-limit-capabilities > > https://github.com/opencontainers/runc/issues/654 > > https://github.com/opencontainers/runc/issues/1175 > > https://wiki.gentoo.org/wiki/Docker#Docker_service_fails_because_cgroup_device_not_mounted_.28systemd.29 > > I ran into this issue when going from 4.19.56 to 4.19.68 kernel. > Perhaps I will try this option later on, but I wonder if we could file > a bug with sgentoo or somewhere? And furthermore its the same version of systemd 243_rc2 . -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una cov...@ccs.covici.com
Re: [gentoo-user] Docker + systemd since cgroups v2
On Tue, 10 Sep 2019 10:12:08 -0400, Andrew Udvare wrote: > > For reference: uname -r: 5.2.13-gentoo, systemd version > 243_rc2-r1[cgroup-hybrid], ACCEPT_KEYWORDS="~amd64" > > My system started failing to start running docker.service automatically and > the logs weren't too helpful. Finally I ran dockerd on its own and found that > it gave me this error message: > > Devices cgroup isn't mounted > > This is not too easy to diagnose as there seem to be a set of solutions but > none of the main two worked for me. One involved setting 2 options on the > kernel command line: > > cgroup_enable=memory swapaccount=1 > > And the other was to add USE="cgroup-hybrid" to systemd. I did this, but it > too it did not work. > > The other solution is to simply mount the cgroup manually and this works but > I did not see why I'd have to do that now when I never had to in the past. > > I actually had to add this to my command line: > > systemd.legacy_systemd_cgroup_controller=yes > > This has been noted in other distros but from what I can tell this is solely > because runc has not been updated to be able to use cgroups v2. > > Anyone else ran into this issue? Is there something I am missing so I > wouldn't need to pass a kernel command line option? > > Reference links: > > https://docs.docker.com/install/linux/linux-postinstall/#your-kernel-does-not-support-cgroup-swap-limit-capabilities > https://github.com/opencontainers/runc/issues/654 > https://github.com/opencontainers/runc/issues/1175 > https://wiki.gentoo.org/wiki/Docker#Docker_service_fails_because_cgroup_device_not_mounted_.28systemd.29 I ran into this issue when going from 4.19.56 to 4.19.68 kernel. Perhaps I will try this option later on, but I wonder if we could file a bug with sgentoo or somewhere? -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una cov...@ccs.covici.com
[gentoo-user] Docker + systemd since cgroups v2
For reference: uname -r: 5.2.13-gentoo, systemd version 243_rc2-r1[cgroup-hybrid], ACCEPT_KEYWORDS="~amd64" My system started failing to start running docker.service automatically and the logs weren't too helpful. Finally I ran dockerd on its own and found that it gave me this error message: Devices cgroup isn't mounted This is not too easy to diagnose as there seem to be a set of solutions but none of the main two worked for me. One involved setting 2 options on the kernel command line: cgroup_enable=memory swapaccount=1 And the other was to add USE="cgroup-hybrid" to systemd. I did this, but it too it did not work. The other solution is to simply mount the cgroup manually and this works but I did not see why I'd have to do that now when I never had to in the past. I actually had to add this to my command line: systemd.legacy_systemd_cgroup_controller=yes This has been noted in other distros but from what I can tell this is solely because runc has not been updated to be able to use cgroups v2. Anyone else ran into this issue? Is there something I am missing so I wouldn't need to pass a kernel command line option? Reference links: https://docs.docker.com/install/linux/linux-postinstall/#your-kernel-does-not-support-cgroup-swap-limit-capabilities https://github.com/opencontainers/runc/issues/654 https://github.com/opencontainers/runc/issues/1175 https://wiki.gentoo.org/wiki/Docker#Docker_service_fails_because_cgroup_device_not_mounted_.28systemd.29 -- Andrew Udvare
Re: [gentoo-user] Strange eix problem
On Monday, 9 September 2019 16:39:40 BST Jack wrote: > Have you added or deleted any repositories lately? This is just a wild > guess (and likely wrong) but I wonder if the eix database uses an index > into the list of repositories instead of text reference. Doesn't seem > likely, or there probably would have been other entries pointing to a > "wrong" repository. Check out eix-installed to see if you can find any > other anomalies. Nope. I don't think I've made any changes to portage's config this year; in fact the whole setup has been stable for as long as I can remember. Since reinstalling that one odd package yesterday, all is smooth again. Thanks for your interest. -- Regards, Peter.
