From 95f85480de7eec5ba26fd54b7d8994f09e550225 Mon Sep 17 00:00:00 2001 From: Cem Keylan Date: Tue, 2 Feb 2021 09:40:22 +0300 Subject: site: remove generated files I will be publishing the website through post-receive hooks so that every minor change doesn't generate thousands of lines of git logs. --- news/index.org | 107 --------------------------------------------------------- 1 file changed, 107 deletions(-) delete mode 100644 news/index.org (limited to 'news/index.org') diff --git a/news/index.org b/news/index.org deleted file mode 100644 index 3a09a0f..0000000 --- a/news/index.org +++ /dev/null @@ -1,107 +0,0 @@ -#+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. - - -- cgit v1.2.3