sbrabez

sbz@

[sbrabez @sbrabez]

@lea_linux Your welcome, pour illustrer avec un exemple simple https://t.co/zrnzkbAqnX. Enjoy!

[sbrabez @sbrabez]

@balajijegan Some references, you can have a look to @rakyll production readiness writings https://t.co/zjsjrk0HBw and @gruntwork https://t.co/PrwWj8SjAR on AWS

[sbrabez @sbrabez]

@oshogbovx Same, I particularly appreciate

Diff per file:
git diff HEAD~3 --stat rev -- path

Where is the file:
git ls-files|grep the_file

Cleanup current tree (removed unstaged and non versioned files) -i for interactive et -n dry run:
git clean -d -f -x

so much more too...

[sbrabez @sbrabez]

@koobs IMHO Users satisfaction, production readiness, reliability/durability and limitation of regressions. All help reducing the friction/churn, on-boarding, stress and streamline adoption more easier for newcomers and grow your users community

[sbrabez @sbrabez]

@cperciva Any comparative data with 13.x, 12.x and 11.x supported releases? Did you observe regressions?

[sbrabez @sbrabez]

@relistan Agreed, what I dislike with go modules, it's you need to create a module even if you just want to write a simple program to be able to build it. You can set GO111MODULE=off as a work around but it requires to have all deps in GOPATH. Before it was just invoke go build and *done*

[sbrabez @sbrabez]

@f0andrey @FreeBSDHelp In this case, it was "unplanned", so plan using a boot environment was not the adopted strategy. Thanks for sharing, I'll have a look.

[sbrabez @sbrabez]

Recently I had to deal with a ZFS panic on CURRENT and I had to recover my data because the bootloader couldn't load the kernel anymore 🤨. I wrote the following notes https://t.co/VmOYjbk55t to recover from the annoying situation. I'll share it in case you hit the same issue 🙂

[sbrabez @sbrabez]

@FreeBSDHelp Unfortunately not, I didn't investigate further as it was on a old CURRENT and I didn't keep the crashinfo vmcore. Next time, I'll do it. When it's unplanned like that, nothing much you can do except plan for backup, cry or restore.

[sbrabez @sbrabez]

@ed_maste @FreeBSDHelp @Stefar77 I wrote this simple python script sometime ago to capture similar data https://t.co/PBCuf2sLCl

[The Register @TheRegister]

License to thrill: Ahead of v13.0, the FreeBSD team talks about Linux and the completed toolchain project that chan… https://t.co/UBQEByye98

[sbrabez @sbrabez]

@saruspete + also, the env, arguments and the ELF auxiliary vector AT_*  are setup on the program stack. ET_DYN bins read PT_INTERP via load_elf_interp(), dynamic linker load shared libraries that the program depend, then the interpreter start the program at the entrypoint at AT_ENTRY value

[sbrabez @sbrabez]

@wxs You need to follow me to be able to DM. And Yes I am still doing it 😇

[sbrabez @sbrabez]

@wxs wxs@ I would be happy to take it if you want to ship it oversea in Dublin, IE. Otherwise I would understand that it goes to US-based person 🙂

[sbrabez @sbrabez]

I took a break of digital detox (Internet, social media, platforms, phone, etc.) to enjoy free time. It was totally revitalizing. Now I'm gonna resume my pending tasks and activities progressively. If you tried to reach me, please give me some time to backlog and reply.

[sbrabez @sbrabez]

@excalidraw for whiteboarding exercices is pretty nice. I spend time to walkthrough steps of an algorithm problem. I am very happy with the result. It works for architecture diagrams too. Kudos for this! https://t.co/tt7lm9OjEx

[sbrabez @sbrabez]

@innolocity Thanks @innolocity for introducing me to Advent of Code while we worked together at @NitroEng. It's a good exercice to do, so this year, I'm also focusing on solving the problems with python. You could have a look at https://t.co/PSEkz5refD

[sbrabez @sbrabez]

@ocochardlabbe @freebsd @FreeBSDHelp Yeah, I faced some issues with iwn0 lately. I wanted to understand and troubleshoot what was wrong 🤓

[sbrabez @sbrabez]

I started to compile the @freebsd commands I'm using regularly here https://t.co/TnSzEHemh3 cc @FreeBSDHelp