The way forward is to create Termux like apps in Java/Kotlin.
POSIX is anyway not part of official stable APIs.
61–70 of 329 posts
The way forward is to create Termux like apps in Java/Kotlin.
POSIX is anyway not part of official stable APIs.
I'm really starting to despise most OS's for having such an overbearing security policy. I think it's really why I've stuck with Windows for so long. For sure Windows is not as user-stupid as something like macOS, iOS, Android, etc... but for me as a power user it's just about as powerful as I need to be. I'm not even considering *nix distros here because honestly the market for every day users for something like Ubu…
As someone who has been on Linux a long time, but still has to support family members using Windows, here's my perspective: 1) Linux is usually easier in the "happy case", where everything works as it should, and it supports everything that the user needs. 2) Linux is way way way less likely to just change something and break the whole system while the user is sleeping. (This was REAL fun with my grandparents-in-law…
7) It's way easier to find someone you know to help you on Windows than Linux, for now.
I visit my parents once a year and always mark out a day to spend fixing/updating/removing junk on my dad's Windows laptop. Three times I installed Linux and when I came back the following year Windows was back on the laptop. The reason being people just know Windows where I am from and the moment they see Linux they feel that's the problem. Even if my dad is struggling to print something which has nothing to do with Linux, the first thing they do is remove Linux.nvm
Earlier quoted context omitted.
I don't think it's very alarmist or an overstatement though. An android 10 app is no longer allowed to do what termux does. I guess with more reading they are saying they need to declare themselves as targeting android 9 or lower until they find a solution. At some point, I imagine, that will not be an option. To some degree it should also be on Google to ensure that tightening security (or perceived tightening of se…
It's still possible, you just have to dance around a little more In one project we work around this by shipping a tiny wrapper in the APK to exec that then uses dlopen() on the target, which is now built as a library. Pretty sure a generic hack could be made to run unmodified executables this way. Certainly in the security community userland ELF loaders are very old news, even X11R6 had its own at one point
And then at some point you realize that, like Cygwin, you have built a system where fork() fails randomly by design.
And then Google blacklists both fork and exec.
Earlier quoted context omitted.
where do chrome books fall on this spectrum?
Depends on whether you have bothered to open them up and remove the hardware-based firmware write protect. The process is highly device-dependent, and seems to be entirely undocumented for many Chromebooks and other ChromeOS devices. YMMV.
You don't need to open it up for developer mode, which lets you mess around as root, chroot into a Linux distro, give the chroot control of the screen...
I really can't be arsed with this stuff any more.
Why are the developers at Google acting in such boneheaded ways? Is it literally just "I get paid loads of money, lol"? Do people not grow out of that eventually when they have enough?
Like, you're literally a developer. Why would you make something you wouldn't want to use? Is the company just wholly made up of people who actually don't care about computing?
I ordered a PinePhone the other day and I'm going to do as much as I can to try and make it my daily driver. I really can't be arsed with this stuff any more. Why are the developers at Google acting in such boneheaded ways? Is it literally just "I get paid loads of money, lol"? Do people not grow out of that eventually when they have enough? Like, you're literally a developer. Why would you make something you wouldn'…
Earlier quoted context omitted.
Depends on whether you have bothered to open them up and remove the hardware-based firmware write protect. The process is highly device-dependent, and seems to be entirely undocumented for many Chromebooks and other ChromeOS devices. YMMV.
That's a pretty high standard. You don't need to open it up for developer mode, which lets you mess around as root, chroot into a Linux distro, give the chroot control of the screen...
I'm really starting to despise most OS's for having such an overbearing security policy. I think it's really why I've stuck with Windows for so long. For sure Windows is not as user-stupid as something like macOS, iOS, Android, etc... but for me as a power user it's just about as powerful as I need to be. I'm not even considering *nix distros here because honestly the market for every day users for something like Ubu…
As someone who has been on Linux a long time, but still has to support family members using Windows, here's my perspective: 1) Linux is usually easier in the "happy case", where everything works as it should, and it supports everything that the user needs. 2) Linux is way way way less likely to just change something and break the whole system while the user is sleeping. (This was REAL fun with my grandparents-in-law…