Posts by zirias@techhub.social
(DIR) Post #AZ6PhtSp5sKZmgh6Bs by zirias@techhub.social
2023-08-20T20:55:27Z
0 likes, 0 repeats
Today's achievement: We now have #OpenSSL (and #GNU coreutils built using it), plus grep, sed, awk, make, groff *and* man-db in #FreeBSD's #Linuxulator userland.But there's a catch π It doesn't build with #poudriere any more. Can be patched, and I guess I should soon look into getting this fixed... (**edit**: See answer, somewhat working without a patch now!)For details, see here:https://lists.freebsd.org/archives/freebsd-ports/2023-August/004286.html
(DIR) Post #AZ6PhudUjgSfQ4h8Sm by zirias@techhub.social
2023-08-21T18:01:57Z
0 likes, 1 repeats
For the next iteration, support #Linux 5.15 on #FreeBSD versions supporting it ... doing this full rebuild again to test. π₯±
(DIR) Post #AZ6PhusNqKN4AFf1fc by zirias@techhub.social
2023-08-19T19:50:04Z
0 likes, 0 repeats
And I still have NO idea where these errors regarding the ELF program interpreter come from when building #gcc and its libstdc++. They do NOT appear in the build log, they are somehow just spit to the controlling terminal of #poudriere. And I didn't find anything not working in these packages so far ... π€―
(DIR) Post #AZ6PhvUJZIiE3tPJnE by zirias@techhub.social
2023-08-23T21:03:26Z
0 likes, 0 repeats
In case anyone tried and wondered why the branch is currently broken π I'm working on adding a new USES for this #Linuxulator userland. It should hide all the "crap" needed to build it, and also help with creating new ports, either *for* it (e.g. shared libs), or just using it.So I have to rework each and every port now, including test builds...Right now, I'm test-building "native" gcc ... for the third time π so, native toolchain almost complete again.I hope to get the branch into sane shape tomorrow!#Linux #FreeBSD #Linuxulator
(DIR) Post #AZ6PhvvbvoXxQYB7L6 by zirias@techhub.social
2023-08-21T07:09:09Z
0 likes, 0 repeats
Good news, I found a workaround without patching poudriere, my branch is updated!poudriere-testport will probably fail, but poudriere-bulk works this way.
(DIR) Post #AZ6PhwKQRYOcfVmw1A by zirias@techhub.social
2023-08-24T20:17:18Z
0 likes, 1 repeats
Userland built from source for #FreeBSD's #Linuxulator is making progress again (and yes, my branch builds and works again!)βοΈ Metaports "linuxsrc_base" for a minimal base userland and "linuxsrc-devtools" for minimal basic tools needed to build #Linux software (just C and C++ and some common tools)βοΈ Automatic selection of the Linux kernel version based on target FreeBSD version, overridable in DEFAULT_VERSIONS (but checked for compatibility of course)βοΈ A new "USES=linuxsrc" to do all the ugly "plumbing" needed for building Linux software using FreeBSD #ports, offering different configurations.Guess now I could start adding some optional packages and try to get some *real* Linux application working π https://github.com/Zirias/zfbsd-ports/blob/linux/Mk/Uses/linuxsrc.mk
(DIR) Post #AZ6PhwSvvvCZ5tljHM by zirias@techhub.social
2023-08-19T21:05:13Z
0 likes, 0 repeats
Leisure Suit GNU looking for program interpreter in several wrong places πI *think* I'll "solve" that the way many #Linux distributions seem to do it nowadays -- add two symlinks: /lib -> usr/lib and lib64 -> usr/lib64.It's a horrible mess, but after already doing the same for bin and sbin, well ... maybe it's the "sane" solution π
(DIR) Post #AZ6Phxkh9N0H5H5QbQ by zirias@techhub.social
2023-08-25T18:10:18Z
0 likes, 0 repeats
Spent this day (besides work, hehe) simplifying a few ports and hunting down a few bugs and now, it all builds fine on all supported target systems (#FreeBSD {13.2,14.0}/{aarch64,amd64,i386}). Yay.So, just tried to create a *very* first port in "dist" mode (installed to Linuxulator prefix, but not part of the "base" system).Well, I guess the "interesting" issues just begin π https://lists.freebsd.org/archives/freebsd-current/2023-August/004433.html
(DIR) Post #AZ6PhyFtHNxOe1gLE8 by zirias@techhub.social
2023-08-20T11:38:24Z
0 likes, 0 repeats
Added these symlinks.#glibc needs some "convincing" to install *everything* to /usr, but it works.It solves the issue on #aarch64 and #i386 (which both install the program interpreter to /lib by default).It does NOT solve the issue on #amd64, where the program interpreter is installed to /lib64, but *something* during #GCC build insists on finding it in /usr/lib instead. π€―Trying a hack with a hardlink now (after learning that glibc's ldconfig just deletes symlinks to the program interpreter).
(DIR) Post #AaBrwbUhGUplIUgUrY by zirias@techhub.social
2023-09-27T10:57:09Z
0 likes, 1 repeats
@alelab @stefano @Anniiii my 2Β’ here (actually, indeed two remarks):1. What's "wrong" with #csh is it's a non-standard shell, many things work differently than in a #POSIX-compliant (bourne) shell, sometimes in subtle and surprising ways. For me, this is just unnecessary friction, you'll always use a bourne shell for scripting, and I want my interactive shell to work exactly the same (plus extensions of course). Regarding this, #fish is even worse, while #zsh by default is (almost) #POSIX-compliant, can emulate a lot (including #csh) and is comfortable by extensions.2. #FreeBSD offers "toor" as a second name for "root" with its own entry in the passwd database. If you activate it (by setting a password), you can change the shell of *one* of the accounts safely, as long as the *other* one keeps having the default shell from base.
(DIR) Post #AaDWIfv7gCdsij5HRA by zirias@techhub.social
2023-09-28T06:01:56Z
0 likes, 1 repeats
@grahamperrin @alelab @stefano @Anniiii thanks, added a comment @emaste π
(DIR) Post #AbOGLErzvmAr7UGKKO by zirias@techhub.social
2023-11-02T08:26:39Z
0 likes, 1 repeats
@stefano @marcan From the perspective of someone neither using #Apple silicon nor #Linux (where avoidable) who just found this "by accident" in his timeline: What a mess! πI'd say warning about using Apple silicon with some 3rd party OS isn't completely unfounded, after all, there's a history of Apple aiming for closed ecosystems. This doesn't necessarily mean putting down projects enabling to do that anyways...I think what we see here is a combination of confirmation bias (which, keep in mind, happens to *everyone*) with bad communication skills.First error: Instead of mistrusting your conclusions, you add some silly "told you so" paragraph. Even if the conclusions turned out to be correct, this would never look professional.Second error: Getting all defensive and playing the victim game when it turns out you were wrong.Confirmation bias is unavoidable. But there are much better ways to deal with it. π
(DIR) Post #Ac1b5kl4XDxXDzN9Zg by zirias@techhub.social
2023-11-21T07:44:23Z
0 likes, 1 repeats
So #FreeBSD 14 is finally announced π₯³ β I already made my mind to not immediately jump on it, because I couldn't see any "killer feature" for me while 13.2 is working just fine. Upgrading to 13.0-RELEASE back then, I ran into several surprising issues. I could find workarounds for all of them, still it was a bit annoying...But now, looking at the official announcement, this bullet point caught my attention:"ZFS has been upgraded to OpenZFS release 2.2, providing significant performance improvements."Performance of my #ZFS pool degrades badly under heavy I/O-load (a parallel poudriere build with lots of smaller ports and lots of ccache hits). The pool is backed by 4 spinning disks in a #raidz configuration.Could I expect 14.0 to improve performance in that specific scenario? π€
(DIR) Post #Ac4OWRZ7HlGFaW3a1A by zirias@techhub.social
2023-11-22T13:23:26Z
0 likes, 1 repeats
@herrbischoff @stefano @iasen_kostov I'd say these instructions are very complete and clear π€·ββοΈ They cover every edge case, maybe they could mention that in the common case (single boot system and no specific boot configuration), it's *much* simpler as there's typically just one single file on your EFI partition, the default bootloader, like in this example here on some aarch64 machine.
(DIR) Post #AcZf5vHuOLR94ZhnLE by zirias@techhub.social
2023-12-07T18:17:57Z
0 likes, 0 repeats
@mms Official packages are built from ports, using all default options. The official builders run ports-mgmt/poudriere-devel to build the package repositories.
(DIR) Post #AcawlLKFH8Yug8KsV6 by zirias@techhub.social
2023-12-08T09:10:38Z
0 likes, 0 repeats
@stefano Only remotely related, did you get the #Omada controller software to run on #FreeBSD? It's slightly annoying I need a #Linux vm currently to run some beast implemented in #Java π
(DIR) Post #AcaxDHoxtmG7uy1rqS by zirias@techhub.social
2023-12-08T09:15:41Z
0 likes, 0 repeats
@stefano Ok, so you're exactly where I finally gave up, my instance is running in a #Devuan vm (no docker involved) after I failed to both run it inside #FreeBSD and #Linuxulator jails π
(DIR) Post #AcfmErD1gVMcFwd5vM by zirias@techhub.social
2023-12-10T17:06:16Z
0 likes, 0 repeats
@jhx They're two completely different things.#Backups prevent loss of data for *any* reason (including e.g. admin's fat fingers)#RAID prevents outages / service downtime because of failing hardware, within certain limits. Some schemes may also improve storage performance (depending on several things...)Having one of them is never a reason for not needing the other one...Not questioning your actual reasoning for not needing RAID, that's probably a sane decision. Just saying backups don't give you "the same thing", completely different purpose π
(DIR) Post #Acj43b6xZpQdnFS7Tk by zirias@techhub.social
2023-12-12T07:10:03Z
0 likes, 0 repeats
@jhx @dch Wait, you're using a mirror? whether this is technically a kind of #RAID can be debated, but it *does* give you the same thing: avoid downtime within certain limits (here: the other disk doesn't fail before the failed one is fully resilvered).
(DIR) Post #AdZl6xtP8Agm9tKzM8 by zirias@techhub.social
2024-01-06T17:17:28Z
0 likes, 0 repeats
@stefano Helps understanding why a toothbrush is the ONE thing Jack #Reacher always carries .... π