aboutsummaryrefslogtreecommitdiff
path: root/news/news.org
diff options
context:
space:
mode:
Diffstat (limited to 'news/news.org')
-rw-r--r--news/news.org172
1 files changed, 0 insertions, 172 deletions
diff --git a/news/news.org b/news/news.org
deleted file mode 100644
index 4361e70..0000000
--- a/news/news.org
+++ /dev/null
@@ -1,172 +0,0 @@
-#+TITLE: Carbs Linux news
-#+DESCRIPTION: a simple Linux distribution
-
-* {{{date(%b %d\, %Y)}}}
-:PROPERTIES:
-:RSS_PERMALINK: 20200916.html
-:PUBDATE: 2020-09-16
-:ID: 1b068ea7-ef38-4eb7-a3cc-36a3585823d1
-: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: 2000a109-f125-4e8f-9458-a6ac995cb70f
-: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: b3f1fc2a-09b7-4895-9c81-5c912aba63ea
-: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: 347ee0df-a4b7-42bc-8a6d-a26a39336954
-: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: 557f67e8-9d80-483b-859e-89f82d19fdd8
-: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: 6a8f3d80-6d73-4e97-b7c0-d1b6fccbf27d
-: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: c574a132-47b7-4e14-a740-10fd9ec5a279
-: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: 8d85adcc-3c03-406f-8901-4da9b3b8596c
-: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: f90898fb-362d-42cb-82d7-f40f9e73e7b3
-: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: b50fa538-5896-4483-a12b-ca8c4c6c2a53
-: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: 3ce41a15-5ca6-4ea1-b7b9-01e1b2a5c60f
-: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: c05366a9-7175-48a6-b37c-366e61b62e1a
-: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: f9a58bcf-b300-4502-9981-c030710cb5e8
-: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.
-