1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
|
____________
NEWS INDEX
____________
[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.
[Sep 16, 2020] <file:20200916.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.
[Sep 03, 2020] <file:20200903.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-*'.
[Jul 27, 2020] <file:20200727.html>
[Jun 17, 2020]
==============
A new rootfs tarball including the changes to the core is released and
can be found on the downloads page.
[Jun 17, 2020] <file:20200617.html>
[May 26, 2020]
==============
An initial version for binary package management is released. It can
be found on the [GitHub page].
[May 26, 2020] <file:20200526.html>
[GitHub page] <https://github.com/CarbsLinux/kiss-bin>
[May 19, 2020]
==============
A rootfs tarball targeting the i686 architecture has been released. It
can be found on the downloads page.
[May 19, 2020] <file:20200519.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 [patch] to your
kernel sources.
**EDIT:** The patch is no longer necessary.
[May 10, 2020] <file:20200510.html>
[patch]
<https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/patch/?id=f670269a42bfdd2c83a1118cc3d1b475547eac22>
[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.
[Apr 27, 2020] <file:20200427.html>
[Apr 10, 2020]
==============
IRC channel can now be accessed from `#carbslinux' at freenode!
[Apr 10, 2020] <file:20200410.html>
[Apr 06, 2020]
==============
A new rootfs tarball has been released. See the downloads page.
[Apr 06, 2020] <file:20200406.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.
,----
| git remote set-url origin https://github.com/CarbsLinux/repository
`----
[Apr 05, 2020] <file:20200405.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.
[Feb 18, 2020] <file:20200218.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.
,----
| # 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.
`----
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.
[Feb 14, 2020] <file:20200214.html>
|
