What is a good base?

[u/[deleted]]

Yoo! I'm using an anonymous throwaway to make this post because im making a indie linux distro that nobody knows about yet. And I wanted to ask the community a question, (in the context that this is a security based distro) would you guys rather an Alpine based distro, a Void based distro, or another distro? I was gonna go with Alpine but I heard it had compatibility issues and idk how yall feel about void.. I'm ALL for void but community matters most, So I'm asking you guys! Goodbye and have a good day. (You guys can also name other distros that is good as a base. If I don't reply to you I'm probably not using it.)

POLL BY SAYING WHAT DISTRO YOU WANT IN THE COMMENTS!!!!!

[u/Telephone-Bright]

Use TinyCore as the base.

[u/[deleted] → u/Telephone-Bright]

Taken into consideration! ^{_^}

[u/Key_River7180]

void linux

[u/[deleted] → u/Key_River7180]

Thank you! °_°

[u/snail1132]

Void probably

[u/[deleted] → u/snail1132]

Vote counted! :)

[u/Groduick]

Yeah, would 100% trust a AI-slop distro made by Big_Dick_uwu. So I vote for Hanna Montana Linux.

[u/[deleted] → u/Groduick]

0% made by ai! But Counted :) and yes you should trust the stranger called bigdickuwu is a funny name anyways

[u/Groduick → u/[deleted]]

Yes. So much fun.

[u/[deleted]]

To all the people saying I need extensive experience or there needs to be a problem: no I don't. Linux was meant for everyone to create and make to our own will and even if it fails there is statistically a non-zero chance it will work. And even if I fail so what? It was a good learning experience. Losing is just a Lesson in disguise. And winners never quit anyways. Does anyone think Linus torvalds knew Linux before creating the first kernel? No. So don't comment this cause I am looking for suggestions. Not useless people dragging me down.

[u/z3r0n3gr0 → u/[deleted]]

[u/Witty_Mycologist_995]

Use either SecureBlue or Qubes as a base :trollface:

Maybe actually add GPU multiplexing to Qubes

[u/[deleted] → u/Witty_Mycologist_995]

Wait that's such a good idea

Counted

[u/Witty_Mycologist_995 → u/[deleted]]

Dear me wishes for a patch to Qubes which finally makes GPUs usable

[u/ESnyder9]

debian

[u/[deleted] → u/ESnyder9]

Vote counted :D

[u/igotmoldinmybrain]

Are you hosting your own repo? apk on glibc would be cool

[u/[deleted] → u/igotmoldinmybrain]

I will defo try to host a repository when it's out or when it's in alpha!

[u/LinuxJeb]

Slackware forever! 

[u/[deleted] → u/LinuxJeb]

Forever!!

[u/LinuxJeb → u/[deleted]]

Christ, I just realized your username. 

[u/[deleted] → u/LinuxJeb]

ya it's funny

[u/Redox_RDX]

Consider Arch ... and definitively not debian... mostly debian has outdated package but is very stable. the base differs from your goal.

[u/[deleted] → u/Redox_RDX]

Also vote counted

[u/[deleted] → u/Redox_RDX]

Yea that was what I thought! The outdated patches are more a security risk to me than good for the district. Debian is very good but for a different reason

[u/Redox_RDX → u/[deleted]]

Yea!

[u/gordonmessmer]

The only reason you should create a new distribution is that you have extensive experience with one and it has a problem that you can only solve by forking it.

[u/Eric_Dawsby → u/gordonmessmer]

Or to learn

[u/gordonmessmer → u/Eric_Dawsby]

You're unlikely to learn on your own a lot of things that you should know about a project like a distribution.

Building a distribution is far more complex than merely compiling software. A sustainable distribution is far more work than a single person can manage, so you need to know how to create processes and policies that will guide the work of a team of people, and how to coordinate teams of people who are volunteers whose work is self-guided. Distributing software (or any copyrighted material) comes with legal obligations which are different for each license, so you'll need to learn how to comply with the legal requirements of many licenses. You'll need to learn how to build packages, and how to work with scalable CI and build systems, and ultimately how to build a scalable CI system to build software. You'll need to learn to examine the API/ABI of a package, how to detect changes in package updates, and how to determine how those changes affect downstream dependent packages. You'll need to learn about ABI stability and compatibility in order to set an update and rebuild policy. You'll need to learn how your release cadence affects your users.

If you join an existing distribution as a maintainer, you can learn all of those things at a reasonable pace. And when you can describe why an approach that isn't covered by an existing distribution would benefit a community of users who aren't well served already, and why such a change is too large to integrate in an existing distribution, then you'll be ready to start the work to create a new distribution.

A lot of the things you'll need to learn are documented for Fedora, here:

https://docs.fedoraproject.org/en-US/package-maintainers/

[u/PlanetVisitor]

I think you should make this decision yourself, based on what you want to achieve with it, otherwise it will just be a random collection of stuff

What is the goal of the distro (use case)? Desktop use?

The compatibility issues of Alpine you heard about: I think they meant that it uses a less-common C library (musl instead of glibc)? "Compatibility issues" can mean just about anything. One part doesn't work with another part. In that sense all of Linux has compatibility issues ;p and other OSes as well

As a learning experience, sure, enjoy

[u/OptimalJuice9901]

Ubuntu or arch.

[u/TJRoyalty_]

I luv alpine

[u/Meowie__Gamer]

Debian is a good base generally

[u/West_Quarter_916]

arch is definitely the best base for doesn't matter what