#ghostbsd — Public Fediverse posts

https://repo.or.cz/code-notes.git/blob_plain/HEAD:/notes/Unix_As_An_IDE.txt

#programming #UNIX #gcc #g++ #asm #ln #golang #lsd #ncdu #ncurses #BSD #freeBSD #ghostBSD #openBSD #Linux #OpenSource #POSIX

#programming #unix #gcc #g #asm #ln

Radio_Azureus @[email protected] · 2026-05-16 · 22:43 UTC

IDEs, UNIX, AND THE LEGACY WORKFLOW THAT NEVER WENT AWAY

Words of Wisdom are dispensed in the article

I have a workflow consisting of

screen
bash or one of
csh
ksh
zsh
vim or
vim.motif
function third(){ awk '{if (NR%3==0){print "\033[32m" $0 "\033[0m"} else{print}}'; }
function psgrep() { ps axuf | grep -v grep | grep "$@" -i --color=auto; }
function mkcd(){ [ ! -z "$1" ] && mkdir -p "$1" && cd "$_"; }
gcc
g++
asm
ln
go from golang
lsd
ncdu

These choices are deliberate. I want and demand the fastest programming ENV: which follow the UNIX principle & KISS

quotes

tl;dr*

Unix already solved many IDE problems decades ago using small cooperating tools instead of one large application.

bash
coreutils
less
tmux
nvialready form a complete and focused development environment for many Unix workflows.

The shell becomes the workspace, the terminal manages sessions, and the editor remains small and predictable

sources:

man sh(1)

man ls(1)

man coreutils(1)

man less(1)

man screen(1)

man tmux(1)

man vim(1)

https://repo.or.cz/code-notes.git/blob_plain/HEAD:/notes/Unix_As_An_IDE.txt

#programming #UNIX #gcc #g++ #asm #ln #golang #lsd #ncdu #ncurses #BSD #freeBSD #ghostBSD #openBSD #Linux #OpenSource #POSIX

#programming #unix #gcc #g #asm #ln

Radio_Azureus @[email protected] · 2026-05-16 · 22:43 UTC

IDEs, UNIX, AND THE LEGACY WORKFLOW THAT NEVER WENT AWAY

Words of Wisdom are dispensed in the article

I have a workflow consisting of

screen
bash or one of
csh
ksh
zsh
vim or
vim.motif
function third(){ awk '{if (NR%3==0){print "\033[32m" $0 "\033[0m"} else{print}}'; }
function psgrep() { ps axuf | grep -v grep | grep "$@" -i --color=auto; }
function mkcd(){ [ ! -z "$1" ] && mkdir -p "$1" && cd "$_"; }
gcc
g++
asm
ln
go from golang
lsd
ncdu

These choices are deliberate. I want and demand the fastest programming ENV: which follow the UNIX principle & KISS

quotes

tl;dr*

Unix already solved many IDE problems decades ago using small cooperating tools instead of one large application.

bash
coreutils
less
tmux
nvialready form a complete and focused development environment for many Unix workflows.

The shell becomes the workspace, the terminal manages sessions, and the editor remains small and predictable

sources:

man sh(1)

man ls(1)

man coreutils(1)

man less(1)

man screen(1)

man tmux(1)

man vim(1)

https://repo.or.cz/code-notes.git/blob_plain/HEAD:/notes/Unix_As_An_IDE.txt

#programming #UNIX #gcc #g++ #asm #ln #golang #lsd #ncdu #ncurses #BSD #freeBSD #ghostBSD #openBSD #Linux #OpenSource #POSIX

#posix #opensource #linux #openbsd #ghostbsd #freebsd

Radio_Azureus @[email protected] · 2026-05-16 · 22:43 UTC

IDEs, UNIX, AND THE LEGACY WORKFLOW THAT NEVER WENT AWAY

Words of Wisdom are dispensed in the article

I have a workflow consisting of

screen
bash or one of
csh
ksh
zsh
vim or
vim.motif
function third(){ awk '{if (NR%3==0){print "\033[32m" $0 "\033[0m"} else{print}}'; }
function psgrep() { ps axuf | grep -v grep | grep "$@" -i --color=auto; }
function mkcd(){ [ ! -z "$1" ] && mkdir -p "$1" && cd "$_"; }
gcc
g++
asm
ln
go from golang
lsd
ncdu

These choices are deliberate. I want and demand the fastest programming ENV: which follow the UNIX principle & KISS

quotes

tl;dr*

Unix already solved many IDE problems decades ago using small cooperating tools instead of one large application.

bash
coreutils
less
tmux
nvialready form a complete and focused development environment for many Unix workflows.

The shell becomes the workspace, the terminal manages sessions, and the editor remains small and predictable

sources:

man sh(1)

man ls(1)

man coreutils(1)

man less(1)

man screen(1)

man tmux(1)

man vim(1)

https://repo.or.cz/code-notes.git/blob_plain/HEAD:/notes/Unix_As_An_IDE.txt

#programming #UNIX #gcc #g++ #asm #ln #golang #lsd #ncdu #ncurses #BSD #freeBSD #ghostBSD #openBSD #Linux #OpenSource #POSIX

#programming #unix #gcc #g #asm #ln

Radio_Azureus @[email protected] · 2026-05-16 · 22:43 UTC

IDEs, UNIX, AND THE LEGACY WORKFLOW THAT NEVER WENT AWAY

Words of Wisdom are dispensed in the article

I have a workflow consisting of

screen
bash or one of
csh
ksh
zsh
vim or
vim.motif
function third(){ awk '{if (NR%3==0){print "\033[32m" $0 "\033[0m"} else{print}}'; }
function psgrep() { ps axuf | grep -v grep | grep "$@" -i --color=auto; }
function mkcd(){ [ ! -z "$1" ] && mkdir -p "$1" && cd "$_"; }
gcc
g++
asm
ln
go from golang
lsd
ncdu

These choices are deliberate. I want and demand the fastest programming ENV: which follow the UNIX principle & KISS

quotes

tl;dr*

Unix already solved many IDE problems decades ago using small cooperating tools instead of one large application.

bash
coreutils
less
tmux
nvialready form a complete and focused development environment for many Unix workflows.

The shell becomes the workspace, the terminal manages sessions, and the editor remains small and predictable

sources:

man sh(1)

man ls(1)

man coreutils(1)

man less(1)

man screen(1)

man tmux(1)

man vim(1)

https://repo.or.cz/code-notes.git/blob_plain/HEAD:/notes/Unix_As_An_IDE.txt

https://thehackernews.com/2026/05/linux-kernel-dirty-frag-lpe-exploit.html

#programming #UNIX #gcc #g++ #asm #ln #golang #lsd #ncdu #ncurses #BSD #freeBSD #ghostBSD #openBSD #Linux #OpenSource #POSIX

#programming #unix #gcc #g #asm #ln

mudala @[email protected] · 2026-05-14 · 19:22 UTC

A new, unpatched local privilege escalation (LPE) vulnerability impacting the Linux kernel.

Linux Kernel Dirty Frag LPE Exploit Enables Root Access Across Major Distributions.

Well, after reading "Integrated By Design", Vivian Voss's book...

...it's clear why. IMO the book is a must if you are working with #linux
or starting with #bsd #freeBSD #openbsd #ghostbsd

https://thehackernews.com/2026/05/linux-kernel-dirty-frag-lpe-exploit.html

#linux #bsd #freebsd #openbsd #ghostbsd #security

mudala @[email protected] · 2026-05-14 · 19:22 UTC

A new, unpatched local privilege escalation (LPE) vulnerability impacting the Linux kernel.

Linux Kernel Dirty Frag LPE Exploit Enables Root Access Across Major Distributions.

Well, after reading "Integrated By Design", Vivian Voss's book...

...it's clear why. IMO the book is a must if you are working with #linux
or starting with #bsd #freeBSD #openbsd #ghostbsd

https://thehackernews.com/2026/05/linux-kernel-dirty-frag-lpe-exploit.html

#linux #bsd #freebsd #openbsd #ghostbsd #security

mudala @[email protected] · 2026-05-14 · 19:22 UTC

A new, unpatched local privilege escalation (LPE) vulnerability impacting the Linux kernel.

Linux Kernel Dirty Frag LPE Exploit Enables Root Access Across Major Distributions.

Well, after reading "Integrated By Design", Vivian Voss's book...

...it's clear why. IMO the book is a must if you are working with #linux
or starting with #bsd #freeBSD #openbsd #ghostbsd

https://thehackernews.com/2026/05/linux-kernel-dirty-frag-lpe-exploit.html

#linux #bsd #freebsd #openbsd #ghostbsd #security

mudala @[email protected] · 2026-05-14 · 19:22 UTC

A new, unpatched local privilege escalation (LPE) vulnerability impacting the Linux kernel.

Linux Kernel Dirty Frag LPE Exploit Enables Root Access Across Major Distributions.

Well, after reading "Integrated By Design", Vivian Voss's book...

...it's clear why. IMO the book is a must if you are working with #linux
or starting with #bsd #freeBSD #openbsd #ghostbsd

https://thehackernews.com/2026/05/linux-kernel-dirty-frag-lpe-exploit.html

#lpe #hacking #vulnerability #security #ghostbsd #openbsd

mudala @[email protected] · 2026-05-14 · 19:22 UTC

A new, unpatched local privilege escalation (LPE) vulnerability impacting the Linux kernel.

Linux Kernel Dirty Frag LPE Exploit Enables Root Access Across Major Distributions.

Well, after reading "Integrated By Design", Vivian Voss's book...

...it's clear why. IMO the book is a must if you are working with #linux
or starting with #bsd #freeBSD #openbsd #ghostbsd

#linux #bsd #freebsd #openbsd #ghostbsd #security

Radio_Azureus @[email protected] · 2026-05-14 · 14:30 UTC

Init vs SystemD

This subject was highlighted in an interesting manner by the author.
The article is also very informative. You will learn a few to a lot of things about both systems.

From my perspective the author seems to have forgotten one important thing.

He stated himself that Init follows the UNIX, not Linux, principle of doing one thing good.

The UNIX principle is way older than Linux itself, which makes me think that the author has not been around long enough, to know how interesting of a monstrosity systemD has become.

Regardless whether you like Init or systemD, you have to know that they have totally different concepts with similar final goals but in different manners.

The philosophies coding styles, modus operandi & configuration, differ so wildly from one to another, that you should not compare them, AT ALL

Never compare systemD with Init!

Realize one thing, if you do not want to see systemD, ever you have to migrate to one of the more advanced Open Source environments.

You shall be safe in freeBSD, openBSD, netBSD, ghostBSD, Open Indiana, Tribblix, Illumos, or any of the others which have been around much longer than Linus Torvalds was even an ID {idea} in the balls of his father.
You can even go for Open DOS, sinds that's single tasking no Init is needed

You should also not forget that you can always, write & program your own Init system or modify the current Init system itself, if you are stuck on a Linux flavor.

Stop bitching about which system is better.

They are totally different.

Live with one of them or write your own

Init is Open Source
systemD is Open Source

Use the power, choose or fork your favourite

Sources:

#Init #systemD #Linux #POST #freeBSD #openBSD #netBSD #ghostBSD #programming #sh #C #Lang

#init #systemd #linux #post #freebsd #openbsd

Radio_Azureus @[email protected] · 2026-05-14 · 14:30 UTC

Init vs SystemD

This subject was highlighted in an interesting manner by the author.
The article is also very informative. You will learn a few to a lot of things about both systems.

From my perspective the author seems to have forgotten one important thing.

He stated himself that Init follows the UNIX, not Linux, principle of doing one thing good.

The UNIX principle is way older than Linux itself, which makes me think that the author has not been around long enough, to know how interesting of a monstrosity systemD has become.

Regardless whether you like Init or systemD, you have to know that they have totally different concepts with similar final goals but in different manners.

The philosophies coding styles, modus operandi & configuration, differ so wildly from one to another, that you should not compare them, AT ALL

Never compare systemD with Init!

Realize one thing, if you do not want to see systemD, ever you have to migrate to one of the more advanced Open Source environments.

You shall be safe in freeBSD, openBSD, netBSD, ghostBSD, Open Indiana, Tribblix, Illumos, or any of the others which have been around much longer than Linus Torvalds was even an ID {idea} in the balls of his father.
You can even go for Open DOS, sinds that's single tasking no Init is needed

You should also not forget that you can always, write & program your own Init system or modify the current Init system itself, if you are stuck on a Linux flavor.

Stop bitching about which system is better.

They are totally different.

Live with one of them or write your own

Init is Open Source
systemD is Open Source

Use the power, choose or fork your favourite

Sources:

#Init #systemD #Linux #POST #freeBSD #openBSD #netBSD #ghostBSD #programming #sh #C #Lang

#init #systemd #linux #post #freebsd #openbsd

Radio_Azureus @[email protected] · 2026-05-14 · 14:30 UTC

Init vs SystemD

This subject was highlighted in an interesting manner by the author.
The article is also very informative. You will learn a few to a lot of things about both systems.

From my perspective the author seems to have forgotten one important thing.

He stated himself that Init follows the UNIX, not Linux, principle of doing one thing good.

The UNIX principle is way older than Linux itself, which makes me think that the author has not been around long enough, to know how interesting of a monstrosity systemD has become.

Regardless whether you like Init or systemD, you have to know that they have totally different concepts with similar final goals but in different manners.

The philosophies coding styles, modus operandi & configuration, differ so wildly from one to another, that you should not compare them, AT ALL

Never compare systemD with Init!

Realize one thing, if you do not want to see systemD, ever you have to migrate to one of the more advanced Open Source environments.

You shall be safe in freeBSD, openBSD, netBSD, ghostBSD, Open Indiana, Tribblix, Illumos, or any of the others which have been around much longer than Linus Torvalds was even an ID {idea} in the balls of his father.
You can even go for Open DOS, sinds that's single tasking no Init is needed

You should also not forget that you can always, write & program your own Init system or modify the current Init system itself, if you are stuck on a Linux flavor.

Stop bitching about which system is better.

They are totally different.

Live with one of them or write your own

Init is Open Source
systemD is Open Source

Use the power, choose or fork your favourite

Sources:

#Init #systemD #Linux #POST #freeBSD #openBSD #netBSD #ghostBSD #programming #sh #C #Lang

#init #systemd #linux #post #freebsd #openbsd

Radio_Azureus @[email protected] · 2026-05-14 · 14:30 UTC

Init vs SystemD

This subject was highlighted in an interesting manner by the author.
The article is also very informative. You will learn a few to a lot of things about both systems.

From my perspective the author seems to have forgotten one important thing.

He stated himself that Init follows the UNIX, not Linux, principle of doing one thing good.

The UNIX principle is way older than Linux itself, which makes me think that the author has not been around long enough, to know how interesting of a monstrosity systemD has become.

Regardless whether you like Init or systemD, you have to know that they have totally different concepts with similar final goals but in different manners.

The philosophies coding styles, modus operandi & configuration, differ so wildly from one to another, that you should not compare them, AT ALL

Never compare systemD with Init!

Realize one thing, if you do not want to see systemD, ever you have to migrate to one of the more advanced Open Source environments.

You shall be safe in freeBSD, openBSD, netBSD, ghostBSD, Open Indiana, Tribblix, Illumos, or any of the others which have been around much longer than Linus Torvalds was even an ID {idea} in the balls of his father.
You can even go for Open DOS, sinds that's single tasking no Init is needed

You should also not forget that you can always, write & program your own Init system or modify the current Init system itself, if you are stuck on a Linux flavor.

Stop bitching about which system is better.

They are totally different.

Live with one of them or write your own

Init is Open Source
systemD is Open Source

Use the power, choose or fork your favourite

Sources:

#Init #systemD #Linux #POST #freeBSD #openBSD #netBSD #ghostBSD #programming #sh #C #Lang

#lang #c #sh #programming #ghostbsd #netbsd

Radio_Azureus @[email protected] · 2026-05-14 · 14:30 UTC

Init vs SystemD

This subject was highlighted in an interesting manner by the author.
The article is also very informative. You will learn a few to a lot of things about both systems.

From my perspective the author seems to have forgotten one important thing.

He stated himself that Init follows the UNIX, not Linux, principle of doing one thing good.

The UNIX principle is way older than Linux itself, which makes me think that the author has not been around long enough, to know how interesting of a monstrosity systemD has become.

Regardless whether you like Init or systemD, you have to know that they have totally different concepts with similar final goals but in different manners.

The philosophies coding styles, modus operandi & configuration, differ so wildly from one to another, that you should not compare them, AT ALL

Never compare systemD with Init!

Realize one thing, if you do not want to see systemD, ever you have to migrate to one of the more advanced Open Source environments.

You shall be safe in freeBSD, openBSD, netBSD, ghostBSD, Open Indiana, Tribblix, Illumos, or any of the others which have been around much longer than Linus Torvalds was even an ID {idea} in the balls of his father.
You can even go for Open DOS, sinds that's single tasking no Init is needed

You should also not forget that you can always, write & program your own Init system or modify the current Init system itself, if you are stuck on a Linux flavor.

Stop bitching about which system is better.

They are totally different.

Live with one of them or write your own

Init is Open Source
systemD is Open Source

Use the power, choose or fork your favourite

Sources: