GitHub's co-founder and former CEO launched the Ladybird initiative, a brand-new independent browser written from scratch and backed by a non-profit.
https://linuxiac.com/ladybird-is-a-new-browser-initiative-backed-up-by-1m/
I think, just based on experience on previous tech revolutions, that #AI is neither useless nor it is going to repeal and replace human labor.
It just hasn’t hit the its roof, or more precisely constraints, yet.
Media only giving voice to either AI companies or AI researchers turned into doomsday predictors, is at least quite strong signal of a bubble.
If you feel that AI is evil, here’s couple of suggestions what you can do:
Here’s a minimal shenanigans for #eBPF #C host, with bpftool
taking care of header generation.
Payload (payload.c
):
#include "vmlinux.h"
#include <bpf/bpf_helpers.h>
SEC("tracepoint/syscalls/sys_enter_execve")
int tracepoint__syscalls__sys_enter_execve(struct trace_event_raw_sys_enter *ctx)
{
bpf_printk("execve");
return 0;
}
char LICENSE[] SEC("license") = "GPL";
Host (main.c
):
#include <bpf/bpf.h>
#include <bpf/libbpf.h>
#include <signal.h>
#include "payload.h"
static volatile bool interrupted = false;
struct payload *obj;
void do_sigint(int value)
{
interrupted = true;
}
int main(void)
{
struct sigaction sa;
ssize_t ret;
obj = payload__open();
if (!obj)
exit(1);
ret = payload__load(obj);
if (ret)
goto err;
ret = payload__attach(obj);
if (ret)
goto err;
sa.sa_handler = do_sigint;
sigaction(SIGINT, &sa, NULL);
while (!interrupted);
fprintf(stderr, "\ndone\n");
payload__destroy(obj);
exit(0);
err:
payload__destroy(obj);
exit(1);
}
Build (build.sh
):
#!/usr/bin/env sh
# vmlinux
bpftool btf dump file /sys/kernel/btf/vmlinux format c > vmlinux.h
# payload
clang -g -O2 -target bpf -I . -c payload.c -o payload.o
bpftool gen skeleton payload.o > payload.h
# main
clang -g -O2 -Wall -I . -c main.c -o main.o
# hello-ebpf
clang -Wall -O2 -g main.o -lbpf -lelf -lz -o hello-ebpf
While running trace_pipe
is expected to have output like this:
cat-61135 [011] ....1 8303.116335: bpf_trace_printk: execve
zsh-61136 [002] ....1 8303.116691: bpf_trace_printk: execve
zsh-61139 [004] ....1 8303.118436: bpf_trace_printk: execve
I’ve been wondering over the years when being at #Airport check-ins how come these #PowerShell scripts can possibly ever work.
I know this because I’ve seen numerous times over the years crashed check-in machines. Latest one was late Spring when I visited #Ethprague at #Prague Airport.
I miss the “OS/2” and “Guru Meditation” times of my late 90s and early 00’s in vending machines etc. ;-)
Your local airport is actually airport.bat
!
Wrote a pretty good Windows emulator in {fmt}:
#include <fmt/color.h>
int main() {
fmt::print(bg(fmt::color::blue),
"{:1600}", "Your PC ran into a problem and needs to restart.");
}
Things that Mastodon spam accounts following me have put in their profiles today:
• "Passionate crypto trader, let's vibe"
• "Full Stack Digital Marketer Consultant"
What a world.
@pinkforest Well I used mutt 1999-22, and email workflow is the most critical thing in my life almost ;-) But I can still try it out and comment if I have anything to say.
What made me try out aerc in the first place was this blog post: http://www.kroah.com/log/blog/2019/08/14/patch-workflow-with-mutt-2019/, i.e. if aerc made any sense to Greg K-H, it might make sense to me, as Greg is a long-time mutt user :-)
IMHO, one place where there is a lot of room for improvement, and I don’t really have a fixed choice per se, is command-line / TUI address book with vCard support, which would integrate smoothly with these popular clients:
ATM, I’m using https://github.com/lucc/khard but I do not love it particularly.
Nice trick in Aerc that I just learned to share IMAP account for personal and kernel.org account:
~ main
❯ cat .config/aerc/folder-maps/kernel.map
personal = INBOX
INBOX = kernel
~ main
❯ grep folder\-map .config/aerc/accounts.conf
folder-map = ~/.config/aerc/folder-maps/kernel.map
Should be self-explanatory ;-)
One of the most important things to understand in Vim are @:
and @@
. After learning them, there is rarely need mapping ex-mode stuff to keyboard shortcuts.
Already plain vim has two languages: the operator language and vimscript. By learning all the cool tricks of the former, it is often case that there is no need to do anything with the latter. Often plugins are installed because of lack of knowledge in the operator-language ;-)