diff --git a/blog/all_posts.html b/blog/all_posts.html index b40cb88..c7283c9 100644 --- a/blog/all_posts.html +++ b/blog/all_posts.html @@ -15,6 +15,10 @@

all posts

+

December 2021

+

November 2021

+

+GRU Devlog 19 - gic and several libs +

+ +
December 05, 2021 — +G1n +
+ + +

This week started with making gic (maybe name will be change). As I have written before +it is going to be suckless ii clone. Also I started making girclib - simple C library for irc +protocol. I think it will be published as separate project, because I would like to make it +for both: client and server. I don’t yet how it will be done but we will see…

+ +

Then I thought that would be cool to have own libc, but have no knowledge how it speaks with OS. +Then I understood that on linux it is working via syscalls. So started making liblinux - +C library for linux syscalls. Using it we won’t need to use assembly a lot in our libc. Currently +write and read syscalls are done and programmer can use it if passed -I, -L and -l flags to compiler. +And it is already published! (check codeberg or tildegit)

+ +

After understanding how to create proper makefile with liblinux, I started making olibc. Currently +it has very tiny number of features. But string.h is mostly done! I don’t know when I will fill that +it will be ready enough to be published, but hope to have useful functions and test suit there till +that time.

+ +

When olibc will be done enough I am going to start making C compiler (already have some code, but it +is old and I not understand how it works, so need to be rewritten). Also I hope that we will have +enough toolchain (or I will have enough knowledge to implement things that are not done faster) +for our own Linux or BSD distribution. But that will be in future…

+ +

Hope you liked this post! If you would like to help us, contact me via email, xmpp or irc :)

+ +

tags: gru, gic, girclib, liblinux, olibc, libs

+

GRU Devlog 17-18 - coreutils, EGG and ideas

@@ -248,27 +282,6 @@ for it, but after that i will need to understand more how vfs working and rewrit

tags: gru, orion, orsh, xmpp, tilde.tel, jitsi

-

-GRU Devlog 8 - orsh and published initrd -

- -
September 19, 2021 — -G1n -
- - -

This week I have published initrd, but it is not working as expected.

- -

Also I have started one more project - orsh. It is one more shell, but now in C. -Maybe it will be easier to port to Orion. It already supports ; but they are working a bit weird.

- -

Also in orsh you can work with environment variables. -From today’s morning I am trying to replace bash with it, but still a lot need to be done.

- -

Hope you liked this post and if you would like to help me, contact me via email, xmpp or irc :)

- -

tags: gru, orsh, orion

-
+

+GRU Devlog 19 - gic and several libs +

+ +
December 05, 2021 — +G1n +
+ + +

This week started with making gic (maybe name will be change). As I have written before +it is going to be suckless ii clone. Also I started making girclib - simple C library for irc +protocol. I think it will be published as separate project, because I would like to make it +for both: client and server. I don’t yet how it will be done but we will see…

+ +

Then I thought that would be cool to have own libc, but have no knowledge how it speaks with OS. +Then I understood that on linux it is working via syscalls. So started making liblinux - +C library for linux syscalls. Using it we won’t need to use assembly a lot in our libc. Currently +write and read syscalls are done and programmer can use it if passed -I, -L and -l flags to compiler. +And it is already published! (check codeberg or tildegit)

+ +

After understanding how to create proper makefile with liblinux, I started making olibc. Currently +it has very tiny number of features. But string.h is mostly done! I don’t know when I will fill that +it will be ready enough to be published, but hope to have useful functions and test suit there till +that time.

+ +

When olibc will be done enough I am going to start making C compiler (already have some code, but it +is old and I not understand how it works, so need to be rewritten). Also I hope that we will have +enough toolchain (or I will have enough knowledge to implement things that are not done faster) +for our own Linux or BSD distribution. But that will be in future…

+ +

Hope you liked this post! If you would like to help us, contact me via email, xmpp or irc :)

+ +

tags: gru, gic, girclib, liblinux, olibc, libs

+

GRU Devlog 17-18 - coreutils, EGG and ideas

diff --git a/blog/tag_liblinux.html b/blog/tag_liblinux.html new file mode 100644 index 0000000..3657525 --- /dev/null +++ b/blog/tag_liblinux.html @@ -0,0 +1,55 @@ + + + + + + + +~g1n's blog — posts tagged "liblinux" + +
+
+
+

~g1n's blog

+
~g1n's blog
+
+
+

+GRU Devlog 19 - gic and several libs +

+ +
December 05, 2021 — +G1n +
+ + +

This week started with making gic (maybe name will be change). As I have written before +it is going to be suckless ii clone. Also I started making girclib - simple C library for irc +protocol. I think it will be published as separate project, because I would like to make it +for both: client and server. I don’t yet how it will be done but we will see…

+ +

Then I thought that would be cool to have own libc, but have no knowledge how it speaks with OS. +Then I understood that on linux it is working via syscalls. So started making liblinux - +C library for linux syscalls. Using it we won’t need to use assembly a lot in our libc. Currently +write and read syscalls are done and programmer can use it if passed -I, -L and -l flags to compiler. +And it is already published! (check codeberg or tildegit)

+ +

After understanding how to create proper makefile with liblinux, I started making olibc. Currently +it has very tiny number of features. But string.h is mostly done! I don’t know when I will fill that +it will be ready enough to be published, but hope to have useful functions and test suit there till +that time.

+ +

When olibc will be done enough I am going to start making C compiler (already have some code, but it +is old and I not understand how it works, so need to be rewritten). Also I hope that we will have +enough toolchain (or I will have enough knowledge to implement things that are not done faster) +for our own Linux or BSD distribution. But that will be in future…

+ +

Hope you liked this post! If you would like to help us, contact me via email, xmpp or irc :)

+ +

tags: gru, gic, girclib, liblinux, olibc, libs

+ +
+ +
+ diff --git a/blog/tag_libs.html b/blog/tag_libs.html new file mode 100644 index 0000000..965710a --- /dev/null +++ b/blog/tag_libs.html @@ -0,0 +1,55 @@ + + + + + + + +~g1n's blog — posts tagged "libs" + +
+
+
+

~g1n's blog

+
~g1n's blog
+
+
+

+GRU Devlog 19 - gic and several libs +

+ +
December 05, 2021 — +G1n +
+ + +

This week started with making gic (maybe name will be change). As I have written before +it is going to be suckless ii clone. Also I started making girclib - simple C library for irc +protocol. I think it will be published as separate project, because I would like to make it +for both: client and server. I don’t yet how it will be done but we will see…

+ +

Then I thought that would be cool to have own libc, but have no knowledge how it speaks with OS. +Then I understood that on linux it is working via syscalls. So started making liblinux - +C library for linux syscalls. Using it we won’t need to use assembly a lot in our libc. Currently +write and read syscalls are done and programmer can use it if passed -I, -L and -l flags to compiler. +And it is already published! (check codeberg or tildegit)

+ +

After understanding how to create proper makefile with liblinux, I started making olibc. Currently +it has very tiny number of features. But string.h is mostly done! I don’t know when I will fill that +it will be ready enough to be published, but hope to have useful functions and test suit there till +that time.

+ +

When olibc will be done enough I am going to start making C compiler (already have some code, but it +is old and I not understand how it works, so need to be rewritten). Also I hope that we will have +enough toolchain (or I will have enough knowledge to implement things that are not done faster) +for our own Linux or BSD distribution. But that will be in future…

+ +

Hope you liked this post! If you would like to help us, contact me via email, xmpp or irc :)

+ +

tags: gru, gic, girclib, liblinux, olibc, libs

+ +
+ +
+ diff --git a/blog/tag_olibc.html b/blog/tag_olibc.html new file mode 100644 index 0000000..a3eba60 --- /dev/null +++ b/blog/tag_olibc.html @@ -0,0 +1,55 @@ + + + + + + + +~g1n's blog — posts tagged "olibc" + +
+
+
+

~g1n's blog

+
~g1n's blog
+
+
+

+GRU Devlog 19 - gic and several libs +

+ +
December 05, 2021 — +G1n +
+ + +

This week started with making gic (maybe name will be change). As I have written before +it is going to be suckless ii clone. Also I started making girclib - simple C library for irc +protocol. I think it will be published as separate project, because I would like to make it +for both: client and server. I don’t yet how it will be done but we will see…

+ +

Then I thought that would be cool to have own libc, but have no knowledge how it speaks with OS. +Then I understood that on linux it is working via syscalls. So started making liblinux - +C library for linux syscalls. Using it we won’t need to use assembly a lot in our libc. Currently +write and read syscalls are done and programmer can use it if passed -I, -L and -l flags to compiler. +And it is already published! (check codeberg or tildegit)

+ +

After understanding how to create proper makefile with liblinux, I started making olibc. Currently +it has very tiny number of features. But string.h is mostly done! I don’t know when I will fill that +it will be ready enough to be published, but hope to have useful functions and test suit there till +that time.

+ +

When olibc will be done enough I am going to start making C compiler (already have some code, but it +is old and I not understand how it works, so need to be rewritten). Also I hope that we will have +enough toolchain (or I will have enough knowledge to implement things that are not done faster) +for our own Linux or BSD distribution. But that will be in future…

+ +

Hope you liked this post! If you would like to help us, contact me via email, xmpp or irc :)

+ +

tags: gru, gic, girclib, liblinux, olibc, libs

+ +
+ +
+