| HOME | WHY | SUPPORT | DOWNLOAD | SOURCE | WIKI | NEWS | LOGO | pozol.eu |
For the latest news see here
jobbot11 buildbot chroot image
jobbot11.tar.xz (164MB)OSDN is giving us problems in accessing servers and uploading packages and images, we have provided new links to some mirror osdn uses that seems reliable at the moment.
The regular installation image (tar ball) is now a bit smaller, just under 100MB, you spring it open with tar -xf into a fresh partition, initialize and update pacman's repositories, install kernel, boot loader, run the jobo-setup script, and optionally add a graphic environment with the installX script (all scripts are now found in /usr/local/bin/).
After you tour the new installation with runit feel free to add s6 and 66 by simply running the add.66 script (also found in /usr/local/bin) and if you decide it is not for you simply run rm.66. Runit will still boot the system either way if the bootloader linux line includes init=/usr/bin/runit-init. With 66 installed and this command eliminated your system will boot with s6 and 66 already configured.
The build bot image jobbot11 is slightly over the last one due to many upgrades of core/base pkgs and a couple more dependencies. You unfold this image to your building chroot environment, run the script at /src/pkg/ for cloning and updating the 3 joborun source repositories, and off you go in building everything on your own, replacing ours or modifying what you wish.
52c81101cf2aad7579b47cf94d325be7a8ee1444b244a5e1ce7dd735b73081ed jobo-delta-20230605.tar.xz cfabfe80a1c2d6617b14daac2b4c29730f2b40c597aa4ce8c2cd3ae93262ada0 jobbot11.tar.xz
jobbot9 buildbot chroot image
jobbot9.tar.xz (166MB)Due to recent time consuming upgrades (glib2 llvm llvm14) we have released new images to save time and bandwidth post-installation.
The regular installation image (tar ball) is now a bit smaller, just over 100KB, you spring it open with tar -xf into a fresh partition, initialize and update pacman's repositories, install kernel, boot loader, run the jobo-setup script, and optionally add a graphic environment with the installX script (all scripts are now found in /usr/local/bin/).
The build bot image jobbot9 is slightly over the last one due to many upgrades of core/base pkgs. You unfold this image to your building chroot environment, run the script at /src/pkg/ for cloning and updating joborun 3 source repositories, and off you go in building everything on your own, replacing ours or modifying what you wish.
We have adopted a new naming scheme for the installation image (just add the kernel of choice joborun/arch boot loader, run jobo-setup and reboot)
The pkg building chroot image "jobbot" which will clone all our repositories in /src/pkg/ or update them with a simple script found in the same directory.
buildbot chroot image
jobbot8.tar.xz (166MB)sha256sums below:
https://osdn.net/projects/joborun/storage/tarballs/jobo-gamma-20230218.tar.xz.sum https://osdn.net/projects/joborun/storage/tarballs/jobbot8.tar.xz.sum 1a8985aba38e32b489031533b7058b9cb5becb874fe308344ae0020d75550da8 jobo-gamma-20230218.tar.xz 5cc08f3a28dc80d1c2d7c3ede9ccc31142071cd7f9fa58b81d626421210a684b jobbot8.tar.xz
Our binary repositories, previously out of reach for still unknown to us reasons, have returned back to full access since yesterday and all upgrades are currently available. Please use # pacman -Suy to get full upgrade or a list of upgradable packages for your installation you can build from source using our git git.disroot.org/joborun-pkg/
We know, you get what you pay for, but what can we say about disroot.org, they have been better than any paid service would have been. Reliable, responsive, responsible, and reliable again.
Big Bad News: Our binary repositories have been frozen still since early Feb 5th 2023.
Although the repositories are there and functional for downloads they don't reflect the available updates since then as OSDN has shut down access to server we upload and remove packages and the repo database files that make pacman carry upgrades. Our source repositories in git.disroot.org/joborun-pkg still work fine, and you can build everything you need. It will take you about two days for this past week's work, as Arch rebuilt the entire tool-chain (linux-api-headers, glibc, gcc, libtools, binutils) which take 2-3 runs of gcc of 6hr compiling each. The rest should be a breeze.
Since no email response, no ticket support on their site has materialized, no news or announcements anywhere about the status of osdn, and our patience running out has us looking desperately for alternative repository and mirrors. If you have any recommendations we are open to suggestions and ideas. Please use email or the reddit board to discuss.
We are planning to publish a list in which you can carry a massive upgrade by building everything in the correct sequence and a suggested script to do this semi-automatically without much editing.
We apologize and thank you for your patience and support. We know, you get what you pay for, but what can we say about disroot.org, they have been better than any paid service would have been. Reliable, responsive, responsible, and reliable again.
We will be back soon with more news and solutions. This is FOSS after all, and freedom always is a struggle, if it came easy it wouldn't matter as much.
This is the 2nd Gamma edition of system and build-chroot 10/24/2022
The anti-colinialist Joborun edition! Always!
Not much of a change other than upgrades to save you time and bandwidth since the upgrade procedure for the minimal system was more than 20% its "volume". We are always conscious and thoughtful of those with really low bandwidths and high cost of the luxury that remains unappreciated in N.American, European, and some pacific rim industrial economies. So don't expect to ever see a 3.5GB fluff desktop iso from us requiring 2GB more of upgrades the moment after.
An installation script was added since the previous Gamma edition to assist of remaking the bootstrap image into a bootable installation, instructing how to do it, not doing it for you, step by step providing a shell break to do so. The pkg is called jobo-setup and the script joborun-setup. You can install the pkg and run the script on any installation just to check if you have forgotten to do something to your otherwise perfectly running system :)
sha256sum: 62b86338a1e6f0079631c6bdd65433504ab917b6ac3ecf5b998f51da3586bd91
As for the joborun buildbot chroot the image was also updated to the 6th release:
sha256sum: 11a4c24f7514c48f5fd0acb4d9f89ea223dfa8780be3fc6460ad129c66f26324
Some elitist who doesn't perceive himself as an elitist, living in colonial lands as a member of the colonizing tribe, said it is "silly" to build pkgs in a bare-metal system and not in a container like docker.
If you build 4 pkgs that use go as a build dependency in docker, docker will each time (or try) download go then discard it at exit. It is nearly impossible to feed docker with a local repository (it can be done). Now that is an absolute waste of global bandwidth, which an elitist fails to recognize, or the time required for each download to execute.
After nearly a year of doing this, countless trials and installations by us and other people, would have reflected the weakness of building pkgs in bare-metal chroots. We are just too dumb to recognize the difference!
For details on installation go to the wiki link above, see the installation page.
This release was meant to end the beta-phase and to be released on 9/11 (commemorating the Allende (pr: Ayende) execution in Chile on Sept 11 1973 when 49y later the people of Chile have yet to recover) but it was casually delayed due to a storm of Arch upgrades that followed a grounds up build tools upgrade.
An installation script was added to assist of remaking the bootstrap image into a bootable installation, instructing how to do it, not doing it for you. The pkg is called jobo-setup and the script joborun-setup.
As for the joborun buildbot chroot the image was also updated to the 5th release:
jobbot5.tar.xzOther noteworthy news is the Arch struggle with mesa 22.2.0 have been breaking X in the past 2 releases, so we have kept mesa back to its last non-breaking stable form of 22.1.7 We have added a few packages on jobextra and jobcomm and we are pretty caught up with everything upstream.
One source of headache has been the parallel release of cups, libcups, and cups-filters, with and without dbus, how we version them and how do we stop each other from replacing each other during upgrades. We hope that a cups server without dbus running is as appealing to other users as it is to us :)
Our July images are still valid but due to the recent upgrade of the core build toolchain (linux-api-headers glibc libtool gcc binutils etc.) a new set should be expected soon. In the meantime just use the tarballs and upgrade, size is not that great. By the end of this week a new set of tarballs will be released.
We have concentrated efforts in what we believe is best to distribute build-times and quit chasing linux-5.15 or above. At this time and period it seems to us as linux-lts (linux 5.10) is the most reliable and worthy of kernels. If in the near future a new lts appears more promising we will add that kernel as well. Linux 5.15 has a shorter end date than even 5.4 or 4.19, so the team is not even evaluating it as worthy of keeping alive on the long term. 5.10 has an expected lifetime till mid 2026. Therefore don't expect any further upgrades of linux (5.15) at any time soon, if any. 5.19 appears to have some prospects of a next possible lts but it is too early to tell.
We have added dbus-broker built without systemd and other nyisances and we were surprised it built with such options. You may wonder why? First it is a core package for Arch and we suspect it will be a dependency for many packages soon, so we might as well jump in the bandwagon, although we are in favor of just keeping it installed and not running any form of dbus unless absolutely necessary (that is rare).
We hope everyone in the Northern hemisphere is having a great summer and those in the south not having too boring of a winter.
Late July issues. All installed systems with joborun function at 100% just like they do with Obarun. Only better since our core base is built without the pest of systemd among other things.
New images, for installation and for the buildbot (jobbot) are available.
Apart from upgrades of all packages on par with Arch-testing editions here is the list of currently available kernels and headers:
jobcore/linux 5.15.53-02
jobcore/linux-lts 5.10.132-01 We highly recommend this kernel over others, but try what works on your machine best.
jobcore/linux-lts54 5.4.204-01
Compare to https://kernel.org
We have added a few more packages to jobcomm and jobextra
Why are we still on beta and not move into stable? The system is stable as a rock as it is,
1. We promised that 9/11/22 would be our first official stable edition, according to schedule, and to provide the first ever complete bootable .iso image.
2. Providing publicly an .iso brings responsibility against all those who haven't tried joborun because they are too lazy or not knowledgeable enough to do a 5' installation with a tarball. This opens up a can of worms with "support". No matter what we may say and explain about building from source and do things the right way, we are sure this publicity will bring people asking why their LXQT desktop isn't functioning well and why can't they build pamac and run it on Joborun.
We are going to wait a little longer before we open up this much, in hope of community being formed of faithful users who can provide assistance to newcomers. No, not much of a bug fixing has been done, none reported. Things work just as well as beta01, we just thought of saving new users the enormous updates/upgrades and provide a fresher image.
June seasonal refreshment. All installed systems with joborun function at 100% just like they do with Obarun. Only better since our core base is built without the pest of systemd among other things.
New images, for installation and for the buildbot (jobbot) are available.
Apart from upgrades of all packages on par with Arch-testing editions, Linux kernel is 5.15.46 and linux-lts is 5.10-121. Compare to https://kernel.org/
We have added a few more packages to jobcomm, including a fresh stable edition of lightened Abiword, with add-ons turned-off at compile time (see the list and turn on what you like before you build) which after years of disappointments and lost work it now doesn't crash, So it is worth a new fresh try. We have also added a 2nd built on jobextra of cups/libcups built without dbus, For printers that don't seem to require dbus to print, this is good. One less reason to not run dbus in your window manager.
Why are we still on beta and not move into stable? The system is stable as a rock as it is,
1. We promised that 9/11/22 would be our first official stable edition, according to schedule, and to provide the first ever complete bootable .iso image.
2. Providing publicly an .iso brings responsibility against all those who haven't tried joborun because they are too lazy or not knowledgeable enough to do a 5' installation with a tarball. This opens up a can of worms with "support". No matter what we may say and explain about building from source and do things the right way, we are sure this publicity will bring people asking why their LXQT desktop isn't functioning well and why can't they build pamac and run it on Joborun.
We are going to wait a little longer before we open up this much, in hope of community being formed of faithful users who can provide assistance to newcomers. No, not much of a bug fixing has been done, none reported. Things work just as well as beta01, we just thought of saving new users the enormous updates/upgrades and provide a fresher image.
Hello again, we are still here, despite all odds. All installed systems with joborun function at 100% just like they did with Obarun. Glibc and gcc were recently updated and everything seems to be flowing fine. If you dare find any arch package in more advanced edition than our own, please report it publicly on our reddit/r/joborun board or through email (see above), and that is Arch-testing. We check and recheck, but you know how those things go, one may slip through the cracks.
Kernels: linux-lts (our favorite) 5.10.118 and linux 5.15.43 are to this moment the latest editions from kernel.org (check and see). Both tested in various machines without any issues.
We have placed a "Help Wanted" for packaging in reddit/r/joborun because although we want to expand to more dependent packages from extra, we have over completed our capacity. We can barely sleep while doing updates daily. So we are maintaining this momentum till interested parties undertake some routines.
We can't emphasize more the need to build a system from source and realize the difference. Also reveal and publicize the difference, safety, security, independence this brings. The more we build the more we realize everyone else's standards aren't what they seemed or claimed. For example packages whose sums are missing, are wrong, or gpg signatures been expired or replaced, while binaries are produced from the various distros. We can only promise that the PKGBUILD published is what built OUR OWN binaries. We can't say the same about everyone else. When reporting mistakes, incompatibilities to Arch or others, all we get is deletion of the messenger.
Hello again, we are still here. We announce our βeta-02 edition code named Iris-Danae after a developer we owe great gratitude to.
Due to a recent glibc/gcc upgrade from upstream the entire core building tool chain was replaced. So after the upgrades and various tests in various machines we decided to upgrade our image, and also make some less significant changes and corrections to how Openbox is setup and runs as default.
Also thank to a recent catchup run by Obarun to Arch upgrades, everything is cutting edge as arch-testing should be. Runit has no changes, it remains as it was. All in all this is an edition that will provide you with a fresher base to start you system and building engine.
Please see the wiki for installation details. For those using the more manual method of installation without image the additional scripts mentioned above will be in the wiki scripts page, so there is no need to download the image to use them, but 66 will take a more involved setup as described in the Obarun wiki (read the intro to 66 first).
user: root password: jobo user: make password: jobo
For details on installation go to the wiki link above, see the installation page.
Hello again, we are still here.
After a reported occasional bug with adding and removing s6/66 via the ~/add.66 script, while having the initial setup automated for immediate reboot, we modified the /home/make/add.66 and rm.66 scripts, also modified our own 66 package to ensure the s6log system user and environment will always be correct. In addition, we added a script in the user's home directory to remove trees, modules and services, recreate and enable them in the default Joborun way. If you alter the selection of trees and services it would be pretty obvious what you would need to modify the script as well. So instead of having a tedious series of commands to set the system up with 66, you just run the script and everything is reset.
In addition, removing 66 in case you didn't like it returns the system exactly as it was, no traces of trying s6/66 left behind and reliable runit as is. So experimenting with 66 for those in fear of the unknown, has become a 2 command and 2 reboot test. Install, reboot, play with it, remove, reboot, and you are back to where you started, with reliable Joborun, Arch-based, runit based, system. Reliable as a rock, familiar as Arch without systemd/elogind, zstd, ipv6, infestation and security risk.
For an advanced and arch-experienced user system we believe this has become very foul-proof, and hence we have decided to leave the Alpha stage behind and introduce the first Beta edition of Joborun-Linux, named Argyro after a great young woman having her birthday today. Please see the wiki for installation details. For those using the more manual method of installation without image the additional scripts mentioned above will be in the wiki scripts page, so there is no need to download the image to use them, but 66 will take a more involved setup as described in the Obarun wiki (read the intro to 66 first).
user: root password: jobo user: make password: jobo
For details on installation go to the wiki link above, see the installation page.
Hello friends.
If you have noticed the runit pkgs have received some needed attention. This brings the runit stack to a relative stability, as there is nothing that appears as not working. And since runit is not developing unless we find some juicy runscripts that we are missing, we hope not to deal with runit much.
This satisfactory runit setup allowed us to take a closer look to s6 and 66. Obarun usually takes some time with a new "stack" of skarnet's s6 packages. Eric Vidal goes line by line on the changes to see how it might affect 66 before he adopts the new releases. This time it seems he must be busier than normal and has delayed. Meanwhile Avyssos (our cousin Void project) has upped the s6 stack (skalibs, execline, s6, and s6 tools and utilities and mdevd) to the latest and rebuilt the 66 stack (oblibs, 66, 66-tools) based on the latest versions for all. Everything seems to be doing well, and I tried most combinations I know, and most 66 tools. Everything checks, but since this is jumping ahead of Obarun, consider the s6/66 in testing territory (bleeding edge of Obarun).
Other than upgrading make sure everyting will be OK for next reboot by issuing the command as root:
# 66-enable -v 2 -t boot -F boot@sys
If you run into any problems let us know in reddit.com/r/joborun or if you go to the 66 discussion list or Obarun forum, DO mention the versions of s6/skalibs/execline and oblibs/66 you have installed.
Jobbot image, the building chroot, ready to explode and build. Chroot, su make (the building user), cd /src/pkg, run the script that clones the three repositories, and start building. For details see the wiki building pages.
jobbot image 147MB
jobbot image 256sum
For details on installation go to the wiki link above, see the installation page.
A few things were rearranged in the 7th alpha edition.
Many many upgrades of the past week, minor corrections and changes.
The runit-service-scripts package undertook some drastic changes and corrections to address some problems that appeared with
service scripts int the past.
A new policy change swept all service files from the classic /etc/runit/sv location to /usr/lib/runit/sv, leaving the /etc/runit/sv area to the sys-admin to customize and store service scripts that will no longer be changed by the distribution's packaging. This makes the runit arrangement appear more consistent with the default 66 behavior, using /usr/lib/66/service for the distribution and /etc/66 for the sys-admin. The exception to this rule is runit's tty definitions and scripts which have remained in /etc/runit/sv. We don't expect those to be altered in the future.
A great many thanks to reddit.com/u/netphant and Saleem, who have taken an interest in
Joborun and catch problems and errors in this early phase of the system. Their
contribution is priceless and very appreciated. Hopefully the reward is a great
system that works for them on a daily basis.
New kernels are in place linux-lts= 5.10-109 and linux= 5.15-32, both have been tested in various machines and were performing well, with the lts being lighter in ram.
As previously the steps remain the same:
1st step is installing the tar ball in a blank partition
2nd step is installing kernel of choice and bootloader
3rd step, optional, installing Xorg openbox and jwm preconfigured
4th optional step is adding s6 and 66, or staying with runit.
Each step is a single command execution, then exit chroot and reboot with either s6/66 or runit.
user: root password: jobo user: make password: jobo
For details on installation go to the wiki link above, see the installation page.
.. ... of course, yesterday's news, were an April 1st joke, but imagine the horror!
Let's get serious again!
The images below, announced on March 30th are true, systemd/elogind/zstd free ipv4 only as far as we can disable ipv6, but you can never be sure anymore.
The reddit community reddit.com/r/joborun is active and feel free to ask anything, we will do our best. The project is maturing, core building dependencies are getting disinfected, daily, and you can safely step on joborun to built your own distro, add more repositories to the list, pacman doesn't seem to have a limit.
Major change in policy. We have decided it is too much work to avoid systemd, elogind, zstd, ipv6, etc. and it would make work so much easier to adopt all of those. This way the user benefits from "all those features" they provide us. They meaning IBM, Google, Facebook, Oracle, and the greatest of all governments home of the prior great companies.
So this way our users will be able to enjoy Gnome or Plasma desktops and guis, with all the benefits of telemetry, and instead of focusing on the core system and the software building environment, we can focus on backgrounds, color and icon themes, etc. Much more exciting graphic things beyond the boredom of compiling on an ugly terminal window.
You should be seeing the effects of changes beggining tomorrow, April 2nd, there will also be a 5.6GB .iso available with Calamares and you can net-install Gnome or Plasma from the live iso. Eat your heart outs Manjaros and Endeavours, our icon themes are better than yours.
We shall expect your feedback to our themes in our new Discord channel Joborun Discord Channel.
A few things were rearranged in the 6th alpha edition.
Many many upgrades of the past few weeks, minor corrections and changes.
A great many thanks to reddit.com/u/netphant and Saleem, who have taken an interest in
Joborun and catch problems and errors in this early phase of the system. Their
contribution is priceless and very appreciated. Hopefully the reward is a great
system that works for them on a daily basis.
New kernels are in place linux-lts= 5.10-109 and linux= 5.15-32, both have been tested in various machines and were performing well, with the lts being lighter in ram.
As previously the steps remain the same:
1st step is installing the tar ball in a blank partition
2nd step is installing kernel of choice and bootloader
3rd step, optional, installing Xorg openbox and jwm preconfigured
4th optional step is adding s6 and 66, or staying with runit.
Each step is a single command execution, then exit chroot and reboot with either s6/66 or runit.
user: root password: jobo user: make password: jobo
For details on installation go to the wiki link above, see the installation page.
A few things were rearranged in the 4th alpha edition.
1st step is installing the tar ball in a blank partition
2nd step is installing kernel of choice and bootloader
3rd step, optional, installing Xorg openbox and jwm preconfigured
4th optional step is adding s6 and 66, or staying with runit.
Each step is a single command execution, then exit chroot and reboot with either s6/66 or runit.
user: root password: jobo user: make password: jobo
For details on installation go to the wiki link above, see the installation page.
The following alpha 02 tarball image was published, our 2nd, and installing joborun is now relatively simple. There is a link to download the tarball followed by a sha256sum for the tarball (sha256sum jobo.alpha-02.tar.xz should give you an identical figure as the sum file contains, if not the image is either corrupted or not authentic).
Follow the wiki instruction on how to place the contents of the archive into a new partition, chroot, then move to the /home/make directory as user:make, and see the scripts about completing the installation, choosing whether to create a graphic environment, and also there is a script about installing the necessary s6/66 packages and rebooting. The 66 environment is already configured in an equivalent mix of services with that of runit.
Refer to the wiki on the link above on how to use this tarball from any unix/linux system, to install joborun-linux.
user: root password: jobo user: make password: jobo
| " # |
| mmm mmm #mmm mmm m mm m m m mm |
| # #" "# #" "# #" "# #" " # # #" # |
| # # # # # # # # # # # # |
| # "#m#" ##m#" "#m#" # "mm"# # # |
| # |
| "" |