901
Free Software Foundation Turns 40, Unveils LibrePhone
(linuxiac.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 06 Oct 2025
901 points (99.8% liked)
Open Source
41222 readers
390 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 6 years ago
MODERATORS
Why couldn't they just use usual Linux for that? Why a modified kernel? Is Linux as is not suitable for a phone?
Can't they just, idk, make a distro? Maybe from scratch? Pop!_OS is working on COSMIC. Can't they have their Linux-based OS, perhaps with its own things as needed, such as a phone-optimised DE? Or whatever the phone equivalent of a DESKTOP environment would be. A Mobile Environment, perhaps
If my laptop had touch screen with no other method of input built in, and were way smaller, could it not run Linux? Or is that different altogether?
Too many bits of a smartphone are proprietary hardware without open drivers.
I would assume that's the bit they're working on, otherwise there's no real point to the project IMO.
Linux by design gives the user enough rope to hang themselves with.
And that's certainly not a problem when dealing with tech enthusiasts who know what, when and where to touch to avoid messing things up. But when you're dealing with getting a phone into the hands of ordinary people, that isn't going to fly because all of those people will at some point start mucking around inside and then expect tech support when they mess up.
For mainstream adoption, the linux kernel must and the desktop environment must be at least somewhat locked down.
We have immutable distributions already, that is something that isn't a problem. It's replacing those pesky proprietary blobs used to talk to the hardware that is a headache.
Between capabilities, namespaces, control groups, mandatory access control (AppArmor etc) and other mechanisms, I think there are plenty of ways to reduce user access to any part of the system.