Source code?

This forum is dedicated to discussing issues related to the use and development of the Peropesis Linux operating system.

I’m interested in seeing how Peropesis was built from the ground up. Could you please share the source code or repository that you used to create the ISO? I think this would enhance the security and transparency of your project.

Also, could you please make the source files or code for the user manual available? I would love to collaborate with you and other users on improving the documentation. It would be great if you could host the source text on a repo that allows merge requests.

Post reply

1610 views

Hello, s,

Thank you for your suggestions.

1. Sorry, the ISO image / distribution building documentation, without personal individual notes, does not exist at this time. It's possible that documentation will be prepared and made public in the future. Currently, as an alternative, I can only suggest to answer to specific questions of ISO building nuances you are interested.

2. For the user manual: over the next week I'll try to create a repository containing HTML and CSS files, which belonging to the user manual (when I do it, I'll write message in this forum).

3. In addition, I think, in the user manual, under each newly created chapter, there could be specified an authors name, e-mail, etc., who has prepared a new chapter. What do you think about this?

4. Do you have idea, what new topic would you like to add to user manual?

Post reply

1586 views

g, thanks for clearing some points out.

I guess you build the distro image by using some scripts that you run locally. IOW, I doubt you enter/rerun all the commands by hand every time the image is released.

So us (who loves chain-of-trust) getting able to look at these scripts (or at least at the sequence of commands from your terminal sessions) would feel a bit more confident. (Or maybe even let us to rebuild it for ourselves:)

Shape/form of the command execution doesn't matter as much as their exact sequence + a comment here and there, allowing us to build the same behaving image.

And publishing it via some Git frontend would be ideal. Maybe self-hosted, like cgit, gitweb, Pagure, Gitea, Gogs (like every other function on this site). Using some public service (like GitHub and Gitlab) would do too.

And the respective documentation might only come later and be a bonus.

That would make distro more accessible/transparent to the devs/sysops.

Thanks.

Post reply

1461 views

PS. Of course, running fully featured Git web frontend is not necessary.

Headless Git hosting via Apache would be enough to track the changes. Eg:

https://wiki.archlinux.org/title/Git_server#Smart_HTTP
https://man.archlinux.org/man/git-http-backend.1#EXAMPLES

(In case your requirement is to self-host everything instead of relying on the 3rd party, public services)

Post reply

1500 views

sskras,

The ISO image / distribution building documentation, without personal individual notes, does not exist at this time. It's possible that documentation will be prepared and made public in the future (or maybe not. To create a detail documentation, step by step and to maintain it is a new project and it should be mature). As an alternative, I can answer to specific questions of Peropesis ISO building nuances you are interested.

For the "chain-of-trust":
Peropesis ISO is not compiled, it can be unpacked. The Peropesis filesystem also can be extracted. In the filesystem all plain text files are freely readable and all compiled software has freely available source code (except firmware of course). There is ability to see compilation options of many compiled programs. The user manual and the news contain a fairly broad description of how was created and how is working system. So the Peropesis distribution is open in many sense.

Post reply

1410 views

Hi! Since it's been a few months, I was wondering if this has changed at all? Because of how minimal the project is, I think it could be amazing for people interested in OS development who don't want to do Linux from Scratch (LFS).

Post reply

71 views

Thank you for your message. I'm going to think about your suggestion.

Post reply

24 views

Sorry, I'm a little late. A Public Git repository for common development of Peropesis user manual I created on an external Git hosting site. So, I invite all to collaborate for creating this user manual collectively:

git clone git://repo.or.cz/peropesis-user-manual.git

I hope this solution will be acceptable, if not I will wait for advice.

edited by g (Fri, 2023-05-05):
I changed repository address.
If someone needs push access, please, write a user name that I could add to the repository list.
In the README file the license has author Peropesis*. This means that if new authors become available in the future, they would be listed in the Peropesis user manual author list below. Those who will provide user manual corrections should probably be presented as editors on the next list.

Post reply

1513 views