diff options
Diffstat (limited to 'news')
-rw-r--r-- | news/20191210.org | 4 | ||||
-rw-r--r-- | news/20191212.org | 6 | ||||
-rw-r--r-- | news/20191217.org | 5 | ||||
-rw-r--r-- | news/20191218.org | 4 | ||||
-rw-r--r-- | news/20200109.org | 13 | ||||
-rw-r--r-- | news/20200110.org | 4 | ||||
-rw-r--r-- | news/20200113.org | 23 | ||||
-rw-r--r-- | news/20200115.org | 4 | ||||
-rw-r--r-- | news/20200122.org | 5 | ||||
-rw-r--r-- | news/20200128.org | 10 | ||||
-rw-r--r-- | news/20200213.org | 6 | ||||
-rw-r--r-- | news/20200214.org | 50 | ||||
-rw-r--r-- | news/20200218.org | 10 | ||||
-rw-r--r-- | news/20200405.org | 14 | ||||
-rw-r--r-- | news/20200406.org | 4 | ||||
-rw-r--r-- | news/20200410.org | 4 | ||||
-rw-r--r-- | news/20200427.org | 7 | ||||
-rw-r--r-- | news/20200510.org | 7 | ||||
-rw-r--r-- | news/20200519.org | 5 | ||||
-rw-r--r-- | news/20200526.org | 5 | ||||
-rw-r--r-- | news/20200617.org | 5 | ||||
-rw-r--r-- | news/20200727.org | 7 | ||||
-rw-r--r-- | news/20200903.org | 6 | ||||
-rw-r--r-- | news/20200916.org | 6 | ||||
-rw-r--r-- | news/index.org | 107 | ||||
-rw-r--r-- | news/latest-news.org | 19 | ||||
-rw-r--r-- | news/news.org | 172 |
27 files changed, 512 insertions, 0 deletions
diff --git a/news/20191210.org b/news/20191210.org new file mode 100644 index 0000000..7e7c0c8 --- /dev/null +++ b/news/20191210.org @@ -0,0 +1,4 @@ +#+TITLE: {{{date(%b %d\, %Y)}}} +#+DATE: <2019-12-10 Tue> + +First alpha release was made. See the [[https://dl.carbslinux.org/releases][downloads page]]. diff --git a/news/20191212.org b/news/20191212.org new file mode 100644 index 0000000..df21941 --- /dev/null +++ b/news/20191212.org @@ -0,0 +1,6 @@ +#+TITLE: {{{date(%b %d\, %Y)}}} +#+DATE: <2019-12-12 Thu> + +Busybox and Busybox-init has been seperated into two different packages. +This is for adding standalone runit/runit-init to the repositories. + diff --git a/news/20191217.org b/news/20191217.org new file mode 100644 index 0000000..daa160b --- /dev/null +++ b/news/20191217.org @@ -0,0 +1,5 @@ +#+TITLE: {{{date(%b %d\, %Y)}}} +#+DATE: <2019-12-17 Tue> + +Installation instruction are now complete. A review would be greatly appreciated! + diff --git a/news/20191218.org b/news/20191218.org new file mode 100644 index 0000000..337cfdb --- /dev/null +++ b/news/20191218.org @@ -0,0 +1,4 @@ +#+TITLE: {{{date(%b %d\, %Y)}}} +#+DATE: <2019-12-18 Wed> + +carbs-rootfs-20191218.tar.xz was released. diff --git a/news/20200109.org b/news/20200109.org new file mode 100644 index 0000000..bb09f67 --- /dev/null +++ b/news/20200109.org @@ -0,0 +1,13 @@ +#+TITLE: {{{date(%b %d\, %Y)}}} +#+DATE: <2020-01-09 Thu> + +Happy new year, everyone! I am back after some long silence. I was unable to commit for a +while, but I have pulled some new updates from the KISS repository, added some of my own. +This week I will be changing/adding some things. + +Important things are, + +- Carbs-init was updated to 0.3. +- I will be adding an implementation of suckless.org's [[https://core.suckless.org/sinit][sinit]] as =carbs-sinit= +- Carbs Repository was added to [[https://repology.org/repository/carbs][repology.org]] +- A new rootfs tarball will be coming up tomorrow. diff --git a/news/20200110.org b/news/20200110.org new file mode 100644 index 0000000..0a83a3e --- /dev/null +++ b/news/20200110.org @@ -0,0 +1,4 @@ +#+TITLE: {{{date(%b %d\, %Y)}}} +#+DATE: <2020-01-10 Fri> + +carbs-rootfs-20200110.tar.xz was released. diff --git a/news/20200113.org b/news/20200113.org new file mode 100644 index 0000000..5fbdf9f --- /dev/null +++ b/news/20200113.org @@ -0,0 +1,23 @@ +#+TITLE: {{{date(%b %d\, %Y)}}} +#+DATE: <2020-01-13 Mon> + +**Busybox update reqires manual intervention** + +The new busybox package conflicts with the pre-update busybox-init. That's why +you should rebuild and install `busybox-init` before doing the update. + +#+BEGIN_SRC sh +# Do a kiss update first (but don't actually update it yet), or manually pull +# the git repository +kiss u # Cancel this operation after it asks for you to confirm the update + +# Install the busybox-init package +kiss b busybox-init && kiss i busybox-init + +# Continue your update as you normally would. +kiss u + +#+END_SRC + +I have moved runit and logging utilities from the busybox-init package to the busybox +package, which is the cause of these conflicts. diff --git a/news/20200115.org b/news/20200115.org new file mode 100644 index 0000000..8da8e13 --- /dev/null +++ b/news/20200115.org @@ -0,0 +1,4 @@ +#+TITLE: {{{date(%b %d\, %Y)}}} +#+DATE: <2020-01-15 Wed> + +sinit has been taken to =core=, and is now officially supported diff --git a/news/20200122.org b/news/20200122.org new file mode 100644 index 0000000..9e6b998 --- /dev/null +++ b/news/20200122.org @@ -0,0 +1,5 @@ +#+TITLE: {{{date(%b %d\, %Y)}}} +#+DATE: <2020-01-22 Wed> + +Expect downtime on Jan 24 2020 22:00 UTC as I will be migrating this web server +to my Carbs Linux server! diff --git a/news/20200128.org b/news/20200128.org new file mode 100644 index 0000000..e917fa3 --- /dev/null +++ b/news/20200128.org @@ -0,0 +1,10 @@ +#+TITLE: {{{date(%b %d\, %Y)}}} +#+DATE: <2020-01-28 Tue> + +Web Server is now on a Carbs Linux server. It is not complete yet, but I will be +adding a little more for the intended functionality. Downtimes can be expected. + +UPDATE: ssl is now working. + +UPDATE2: downloads are back again. + diff --git a/news/20200213.org b/news/20200213.org new file mode 100644 index 0000000..f37d9eb --- /dev/null +++ b/news/20200213.org @@ -0,0 +1,6 @@ +#+TITLE: {{{date(%b %d\, %Y)}}} +#+DATE: <2020-02-13 Thu> + +Runit is now released on the core repository! You can now replace busybox-init +with runit-init. You can also replace the busybox runit utilities with the +actual runit. This will reduce the dependency on busybox greatly. diff --git a/news/20200214.org b/news/20200214.org new file mode 100644 index 0000000..36b3325 --- /dev/null +++ b/news/20200214.org @@ -0,0 +1,50 @@ +#+TITLE: {{{date(%b %d\, %Y)}}} +#+DATE: <2020-02-14 Fri> + +**IMPORTANT!** Carbs-init update to be released on 17th of February +will require manual intervention. I am holding this update back so +people can see it before they update their system (even though the +update will show the same message as this). The rationale for the +update is explained below the intervention. + +#+BEGIN_SRC sh +# There is an explanation for each init You only need to follow the instructions +# for your own init-system + +## busybox-init +# If you did not edit your inittab simply move inittab.new to inittab +mv /etc/inittab.new /etc/inittab + +# If you did edit your inittab you can use a simple sed command to remove the +# necessary lines +sed -i '/getty/d;/runsvdir/d' /etc/inittab + + +## runit +# same as busybox-init, if you did not edit /etc/runit/2 move 2.new to 2 +mv /etc/runit/2.new /etc/runit/2 + +# else +vim /etc/runit/2 +# open your 2 file and remove the for loop containing getty commands. If you are +# using runit, it is recommended to comment out /etc/init/runit.boot + +## sinit/minit +# If you did not edit your {sinit-,}launch-services.boot you can simply remove +# it. +rm -f /etc/init/launch-services.boot /etc/init/sinit-launch-services.boot + +# This should leave you without any issues, and you can safely reboot. +#+END_SRC + +Carbs-init update is to make sure init systems do not clash, and do +not have to use different files. This is a sensible update both for +the user user and for the maintainer side. + +To give an example, before this update busybox-init was managing getty +through =inittab=, runit was managing through =/etc/runit/2=, and +minit/sinit were launching from =/etc/init/launch-services.boot=. This +is a configuration nightmare for everyone, and since I am maintaining +and constantly testing those init providers, a huge nightmare for me. +This is a Quality of Life update. + diff --git a/news/20200218.org b/news/20200218.org new file mode 100644 index 0000000..ee56dfd --- /dev/null +++ b/news/20200218.org @@ -0,0 +1,10 @@ +#+TITLE: {{{date(%b %d\, %Y)}}} +#+DATE: <2020-02-18 Tue> + +A new tarball is released. It can be found on [[https://dl.carbslinux.org]]. + +**edit:** I have removed the tarball because of a bootstrapping issue. I will be +re-adding it later today. + +**edit 2:** I have added a tarball (20200219) to reflect my recent changes on +Busybox. diff --git a/news/20200405.org b/news/20200405.org new file mode 100644 index 0000000..375a7ac --- /dev/null +++ b/news/20200405.org @@ -0,0 +1,14 @@ +#+TITLE: {{{date(%b %d\, %Y)}}} +#+DATE: <2020-04-05 Sun> + +Carbs Linux repositories will be hosted only on Github. Commits will be pushed +there, and not the repository. You have until May 4, 2020 Monday to switch your +remotes to [[https://github.com/CarbsLinux/repository]]. The git repository will +continue to be served until then (without additional commits). + +You can switch your remote by executing the following command on your repository +directory. + +#+BEGIN_SRC sh +git remote set-url origin https://github.com/CarbsLinux/repository +#+END_SRC diff --git a/news/20200406.org b/news/20200406.org new file mode 100644 index 0000000..31209ca --- /dev/null +++ b/news/20200406.org @@ -0,0 +1,4 @@ +#+TITLE: {{{date(%b %d\, %Y)}}} +#+DATE: <2020-04-06 Mon> + +A new rootfs tarball has been released. See the downloads page. diff --git a/news/20200410.org b/news/20200410.org new file mode 100644 index 0000000..fda05fb --- /dev/null +++ b/news/20200410.org @@ -0,0 +1,4 @@ +#+TITLE: {{{date(%b %d\, %Y)}}} +#+DATE: <2020-04-10 Fri> + +IRC channel can now be accessed from =#carbslinux= at freenode! diff --git a/news/20200427.org b/news/20200427.org new file mode 100644 index 0000000..867f83c --- /dev/null +++ b/news/20200427.org @@ -0,0 +1,7 @@ +#+TITLE: {{{date(%b %d\, %Y)}}} +#+DATE: <2020-04-27 Mon> + +A new rootfs tarball has been released! You can see it on +[[https://dl.carbslinux.org/releases]]! + +**EDIT:** A new bug fix release has been made. diff --git a/news/20200510.org b/news/20200510.org new file mode 100644 index 0000000..c7b7d32 --- /dev/null +++ b/news/20200510.org @@ -0,0 +1,7 @@ +#+TITLE: {{{date(%b %d\, %Y)}}} +#+DATE: <2020-05-10 Sun> + +A GCC 10.1.0 change causes a kernel panic for kernels built with GCC 10.1. This +issue can be resolved by applying this [[https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/patch/?id=f670269a42bfdd2c83a1118cc3d1b475547eac22][patch]] to your kernel sources. + +**EDIT:** The patch is no longer necessary. diff --git a/news/20200519.org b/news/20200519.org new file mode 100644 index 0000000..0583f19 --- /dev/null +++ b/news/20200519.org @@ -0,0 +1,5 @@ +#+TITLE: {{{date(%b %d\, %Y)}}} +#+DATE: <2020-05-19 Tue> + +A rootfs tarball targeting the i686 architecture has been released. It can be +found on the downloads page. diff --git a/news/20200526.org b/news/20200526.org new file mode 100644 index 0000000..70c4fec --- /dev/null +++ b/news/20200526.org @@ -0,0 +1,5 @@ +#+TITLE: {{{date(%b %d\, %Y)}}} +#+DATE: <2020-05-26 Tue> + +An initial version for binary package management is released. It can be found on +the [[https://github.com/CarbsLinux/kiss-bin][GitHub page]]. diff --git a/news/20200617.org b/news/20200617.org new file mode 100644 index 0000000..0aee0df --- /dev/null +++ b/news/20200617.org @@ -0,0 +1,5 @@ +#+TITLE: {{{date(%b %d\, %Y)}}} +#+DATE: <2020-06-17 Wed> + +A new rootfs tarball including the changes to the core is released and can be +found on the downloads page. diff --git a/news/20200727.org b/news/20200727.org new file mode 100644 index 0000000..0afe0b3 --- /dev/null +++ b/news/20200727.org @@ -0,0 +1,7 @@ +#+TITLE: {{{date(%b %d\, %Y)}}} +#+DATE: <2020-07-27 Mon> + +Carbs Linux's fork of the =kiss= package manager has been renamed to =Carbs +Packaging Tools= due to huge amount of changes. Your latest =kiss= update will +handle the bootstrapping. You will need to rename your =KISS-*= variables to +=CPT-*=. diff --git a/news/20200903.org b/news/20200903.org new file mode 100644 index 0000000..4c1941d --- /dev/null +++ b/news/20200903.org @@ -0,0 +1,6 @@ +#+TITLE: {{{date(%b %d\, %Y)}}} +#+DATE: <2020-09-03 Thu> + +The default TLS provider has been reverted to =libressl=. System update will +replace bearssl dependencies with libressl. You may choose to keep or remove +bearssl after the update. diff --git a/news/20200916.org b/news/20200916.org new file mode 100644 index 0000000..50e9ecb --- /dev/null +++ b/news/20200916.org @@ -0,0 +1,6 @@ +#+TITLE: {{{date(%b %d\, %Y)}}} +#+DATE: <2020-09-16 Wed> + +The libressl "revert" was reverted. System update will replace libressl +dependencies with bearssl. You may choose to keep or remove bearssl after the +update. diff --git a/news/index.org b/news/index.org new file mode 100644 index 0000000..3a09a0f --- /dev/null +++ b/news/index.org @@ -0,0 +1,107 @@ +#+TITLE: News Index + +* [[file:20200916.html][Sep 16, 2020]] +The libressl "revert" was reverted. System update will replace libressl +dependencies with bearssl. You may choose to keep or remove bearssl after the +update. +* [[file:20200903.html][Sep 03, 2020]] +The default TLS provider has been reverted to =libressl=. System update will +replace bearssl dependencies with libressl. You may choose to keep or remove +bearssl after the update. +* [[file:20200727.html][Jul 27, 2020]] +Carbs Linux's fork of the =kiss= package manager has been renamed to =Carbs + Packaging Tools= due to huge amount of changes. Your latest =kiss= update will +handle the bootstrapping. You will need to rename your =KISS-*= variables to +=CPT-*=. +* [[file:20200617.html][Jun 17, 2020]] +A new rootfs tarball including the changes to the core is released and can be +found on the downloads page. +* [[file:20200526.html][May 26, 2020]] +An initial version for binary package management is released. It can be found on +the [[https://github.com/CarbsLinux/kiss-bin][GitHub page]]. +* [[file:20200519.html][May 19, 2020]] +A rootfs tarball targeting the i686 architecture has been released. It can be +found on the downloads page. +* [[file:20200510.html][May 10, 2020]] +A GCC 10.1.0 change causes a kernel panic for kernels built with GCC 10.1. This +issue can be resolved by applying this [[https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/patch/?id=f670269a42bfdd2c83a1118cc3d1b475547eac22][patch]] to your kernel sources. + +**EDIT:** The patch is no longer necessary. +* [[file:20200427.html][Apr 27, 2020]] +A new rootfs tarball has been released! You can see it on +[[https://dl.carbslinux.org/releases]]! + +**EDIT:** A new bug fix release has been made. +* [[file:20200410.html][Apr 10, 2020]] +IRC channel can now be accessed from =#carbslinux= at freenode! +* [[file:20200406.html][Apr 06, 2020]] +A new rootfs tarball has been released. See the downloads page. +* [[file:20200405.html][Apr 05, 2020]] +Carbs Linux repositories will be hosted only on Github. Commits will be pushed +there, and not the repository. You have until May 4, 2020 Monday to switch your +remotes to [[https://github.com/CarbsLinux/repository]]. The git repository will +continue to be served until then (without additional commits). + +You can switch your remote by executing the following command on your repository +directory. + +#+begin_src sh + git remote set-url origin https://github.com/CarbsLinux/repository +#+end_src +* [[file:20200218.html][Feb 18, 2020]] +A new tarball is released. It can be found on [[https://dl.carbslinux.org]]. + +**edit:** I have removed the tarball because of a bootstrapping issue. I will be +re-adding it later today. + +**edit 2:** I have added a tarball (20200219) to reflect my recent changes on +Busybox. +* [[file:20200214.html][Feb 14, 2020]] +**IMPORTANT!** Carbs-init update to be released on 17th of February +will require manual intervention. I am holding this update back so +people can see it before they update their system (even though the +update will show the same message as this). The rationale for the +update is explained below the intervention. + +#+begin_src sh + # There is an explanation for each init You only need to follow the instructions + # for your own init-system + + ## busybox-init + # If you did not edit your inittab simply move inittab.new to inittab + mv /etc/inittab.new /etc/inittab + + # If you did edit your inittab you can use a simple sed command to remove the + # necessary lines + sed -i '/getty/d;/runsvdir/d' /etc/inittab + + + ## runit + # same as busybox-init, if you did not edit /etc/runit/2 move 2.new to 2 + mv /etc/runit/2.new /etc/runit/2 + + # else + vim /etc/runit/2 + # open your 2 file and remove the for loop containing getty commands. If you are + # using runit, it is recommended to comment out /etc/init/runit.boot + + ## sinit/minit + # If you did not edit your {sinit-,}launch-services.boot you can simply remove + # it. + rm -f /etc/init/launch-services.boot /etc/init/sinit-launch-services.boot + + # This should leave you without any issues, and you can safely reboot. +#+end_src + +Carbs-init update is to make sure init systems do not clash, and do +not have to use different files. This is a sensible update both for +the user user and for the maintainer side. + +To give an example, before this update busybox-init was managing getty +through =inittab=, runit was managing through =/etc/runit/2=, and +minit/sinit were launching from =/etc/init/launch-services.boot=. This +is a configuration nightmare for everyone, and since I am maintaining +and constantly testing those init providers, a huge nightmare for me. +This is a Quality of Life update. + + diff --git a/news/latest-news.org b/news/latest-news.org new file mode 100644 index 0000000..6922cf2 --- /dev/null +++ b/news/latest-news.org @@ -0,0 +1,19 @@ +* [[file:20200916.html][Sep 16, 2020]] +The libressl "revert" was reverted. System update will replace libressl +dependencies with bearssl. You may choose to keep or remove bearssl after the +update. +* [[file:20200903.html][Sep 03, 2020]] +The default TLS provider has been reverted to =libressl=. System update will +replace bearssl dependencies with libressl. You may choose to keep or remove +bearssl after the update. +* [[file:20200727.html][Jul 27, 2020]] +Carbs Linux's fork of the =kiss= package manager has been renamed to =Carbs + Packaging Tools= due to huge amount of changes. Your latest =kiss= update will +handle the bootstrapping. You will need to rename your =KISS-*= variables to +=CPT-*=. +* [[file:20200617.html][Jun 17, 2020]] +A new rootfs tarball including the changes to the core is released and can be +found on the downloads page. +* [[file:20200526.html][May 26, 2020]] +An initial version for binary package management is released. It can be found on +the [[https://github.com/CarbsLinux/kiss-bin][GitHub page]]. diff --git a/news/news.org b/news/news.org new file mode 100644 index 0000000..1934369 --- /dev/null +++ b/news/news.org @@ -0,0 +1,172 @@ +#+TITLE: Carbs Linux news +#+DESCRIPTION: a simple Linux distribution + +* {{{date(%b %d\, %Y)}}} +:PROPERTIES: +:RSS_PERMALINK: 20200916.html +:PUBDATE: 2020-09-16 +:ID: ab636904-61dd-4fba-934c-6d5e2e2c7a9e +:END: +The libressl "revert" was reverted. System update will replace libressl +dependencies with bearssl. You may choose to keep or remove bearssl after the +update. +* {{{date(%b %d\, %Y)}}} +:PROPERTIES: +:RSS_PERMALINK: 20200903.html +:PUBDATE: 2020-09-03 +:ID: fb6e737c-93d4-4010-a374-d395744563bf +:END: +The default TLS provider has been reverted to =libressl=. System update will +replace bearssl dependencies with libressl. You may choose to keep or remove +bearssl after the update. +* {{{date(%b %d\, %Y)}}} +:PROPERTIES: +:RSS_PERMALINK: 20200727.html +:PUBDATE: 2020-07-27 +:ID: b47e26d5-3210-4125-b41e-8654e1c1e319 +:END: +Carbs Linux's fork of the =kiss= package manager has been renamed to =Carbs + Packaging Tools= due to huge amount of changes. Your latest =kiss= update will +handle the bootstrapping. You will need to rename your =KISS-*= variables to +=CPT-*=. +* {{{date(%b %d\, %Y)}}} +:PROPERTIES: +:RSS_PERMALINK: 20200617.html +:PUBDATE: 2020-06-17 +:ID: 0fa2546c-3cec-42c3-a620-c44aeb14bd82 +:END: +A new rootfs tarball including the changes to the core is released and can be +found on the downloads page. +* {{{date(%b %d\, %Y)}}} +:PROPERTIES: +:RSS_PERMALINK: 20200526.html +:PUBDATE: 2020-05-26 +:ID: 327084ea-554d-4604-8d1d-27a9017fa4bf +:END: +An initial version for binary package management is released. It can be found on +the [[https://github.com/CarbsLinux/kiss-bin][GitHub page]]. +* {{{date(%b %d\, %Y)}}} +:PROPERTIES: +:RSS_PERMALINK: 20200519.html +:PUBDATE: 2020-05-19 +:ID: e3cc197e-693d-4ed4-a766-19ae94d4e655 +:END: +A rootfs tarball targeting the i686 architecture has been released. It can be +found on the downloads page. +* {{{date(%b %d\, %Y)}}} +:PROPERTIES: +:RSS_PERMALINK: 20200510.html +:PUBDATE: 2020-05-10 +:ID: 05213ce1-1eed-4736-8663-32c95e8f58a5 +:END: +A GCC 10.1.0 change causes a kernel panic for kernels built with GCC 10.1. This +issue can be resolved by applying this [[https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/patch/?id=f670269a42bfdd2c83a1118cc3d1b475547eac22][patch]] to your kernel sources. + +**EDIT:** The patch is no longer necessary. +* {{{date(%b %d\, %Y)}}} +:PROPERTIES: +:RSS_PERMALINK: 20200427.html +:PUBDATE: 2020-04-27 +:ID: 35dd49b7-15ed-4e17-8aaf-6b3331253a1f +:END: +A new rootfs tarball has been released! You can see it on +[[https://dl.carbslinux.org/releases]]! + +**EDIT:** A new bug fix release has been made. +* {{{date(%b %d\, %Y)}}} +:PROPERTIES: +:RSS_PERMALINK: 20200410.html +:PUBDATE: 2020-04-10 +:ID: e08b6a03-9967-4b72-aef3-5cafbe8fc926 +:END: +IRC channel can now be accessed from =#carbslinux= at freenode! +* {{{date(%b %d\, %Y)}}} +:PROPERTIES: +:RSS_PERMALINK: 20200406.html +:PUBDATE: 2020-04-06 +:ID: a62bac15-b653-4b2d-b9b0-d59a71718f6b +:END: +A new rootfs tarball has been released. See the downloads page. +* {{{date(%b %d\, %Y)}}} +:PROPERTIES: +:RSS_PERMALINK: 20200405.html +:PUBDATE: 2020-04-05 +:ID: 80ab6b81-ed74-4ccd-bae5-01a179864631 +:END: +Carbs Linux repositories will be hosted only on Github. Commits will be pushed +there, and not the repository. You have until May 4, 2020 Monday to switch your +remotes to [[https://github.com/CarbsLinux/repository]]. The git repository will +continue to be served until then (without additional commits). + +You can switch your remote by executing the following command on your repository +directory. + +#+begin_src sh + git remote set-url origin https://github.com/CarbsLinux/repository +#+end_src +* {{{date(%b %d\, %Y)}}} +:PROPERTIES: +:RSS_PERMALINK: 20200218.html +:PUBDATE: 2020-02-18 +:ID: 74395814-c8cc-4616-99ca-ce1f7b5d1f6e +:END: +A new tarball is released. It can be found on [[https://dl.carbslinux.org]]. + +**edit:** I have removed the tarball because of a bootstrapping issue. I will be +re-adding it later today. + +**edit 2:** I have added a tarball (20200219) to reflect my recent changes on +Busybox. +* {{{date(%b %d\, %Y)}}} +:PROPERTIES: +:RSS_PERMALINK: 20200214.html +:PUBDATE: 2020-02-14 +:ID: 17da458e-41cc-424d-ae9c-789720db202b +:END: +**IMPORTANT!** Carbs-init update to be released on 17th of February +will require manual intervention. I am holding this update back so +people can see it before they update their system (even though the +update will show the same message as this). The rationale for the +update is explained below the intervention. + +#+begin_src sh + # There is an explanation for each init You only need to follow the instructions + # for your own init-system + + ## busybox-init + # If you did not edit your inittab simply move inittab.new to inittab + mv /etc/inittab.new /etc/inittab + + # If you did edit your inittab you can use a simple sed command to remove the + # necessary lines + sed -i '/getty/d;/runsvdir/d' /etc/inittab + + + ## runit + # same as busybox-init, if you did not edit /etc/runit/2 move 2.new to 2 + mv /etc/runit/2.new /etc/runit/2 + + # else + vim /etc/runit/2 + # open your 2 file and remove the for loop containing getty commands. If you are + # using runit, it is recommended to comment out /etc/init/runit.boot + + ## sinit/minit + # If you did not edit your {sinit-,}launch-services.boot you can simply remove + # it. + rm -f /etc/init/launch-services.boot /etc/init/sinit-launch-services.boot + + # This should leave you without any issues, and you can safely reboot. +#+end_src + +Carbs-init update is to make sure init systems do not clash, and do +not have to use different files. This is a sensible update both for +the user user and for the maintainer side. + +To give an example, before this update busybox-init was managing getty +through =inittab=, runit was managing through =/etc/runit/2=, and +minit/sinit were launching from =/etc/init/launch-services.boot=. This +is a configuration nightmare for everyone, and since I am maintaining +and constantly testing those init providers, a huge nightmare for me. +This is a Quality of Life update. + |