-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TODO #1
Comments
Could an installation guide be added to the repo in the form of a INSTALL.md doc? |
Oh.. Thanks, but I haven't released new rootfs for years, it is really a personal distro. I do have binary management(with some bugs though). But I lost most of my binary tarballs about one year ago. I'd need to build about 100 packages for your installation... If you are really interested, I could build one rootfs that you can chroot(probably one month later). And you need to build your own bootloader. |
Hmm, would such a setup be updateable? I was more interested in the package management and templates/recipes. I am also researching how to create my own Linux distro, I've tried with Alpine as a base before but I'd like something more hands-on. Thanks. (if the rootfs is complete, making it bootable with syslinux or oslo is not a problem, thanks for replying) :) |
Yes, of course. It mainly depends on your package manager: if it can uninstall/install packages. I made a very simple manager that stores a list of installed files, so it can uninstall/install packages. But my own package manager can't remove empty dir correctly.
If that is your goal, I don't recommend that you use my linux. My package manager sucks, haha. I would recommend that use apk/pacman or whatever package manager you like to build a complete different distro by writing recipes from scratch. You see, things really matter are recipes/templates. I use MUSL as base libc, so I need a lot of patches for lots of packages. And package management is, in fact, highly similar: add/del/query with hooks/chroot/build system, blah blah. I started my distro by chroot into alpine(or arch?) rootfs, then This process did not rely on any specific package manager, try follow LFS but with a package manager, you'll get what you want. Check eweOS, which is based on pacman obviously. But it is also highly customized. |
Thanks for the insight and consideration, I've already written a sort of "package manager", its called |
Cool. For linux distro, it usually comes with a handy As for me, I wrote them into one binary because I really don't want to maintain two programs. Once you got such a working system, you can start building your ports(slackware/bsd call the repo of recipes |
Would you mind adding an MIT license or 3BSD? So that I can feel confident in borrowing your code..? I really like the way the build recipes for your distro work |
It is MIT. Just borrow it. In fact, I did borrowed scripts/patches from arch/alpine/void/yocto/gentoo sometimes, and even clear-linux from intel(they have some highperf patches). |
common list:
special list(most are patches):
hack it in libc(in ext(), add them in dcngettext.c): https://raw.githubusercontent.com/xhebox/noname/master/ports/musl/Pkgfileit's now implemented in gettext-tiny#2 0x00007ffff7d82a6f in dcngettext (domainname=0x6737a0 "tar", msgid1=0x0, msgid2=0x0, n=1, category=5) at src/locale/dcngettext.c:211
check https://github.com/xhebox/libuargp
actually, it follows that, qtox may have a too small stack.
The text was updated successfully, but these errors were encountered: