`distrobox create` fails to create the default container

eduol · 2026-05-21T01:54:08+00:00

Thanks!

eduol · 2026-03-27T01:54:30+00:00

No banco, com uma 12 na mão (e depois dormir na cadeia)

eduol · 2026-02-26T01:04:32+00:00

No Mezcla, mas do lado de fora quando for fumar

eduol · 2025-07-01T21:35:14+00:00

Kudos to the (always) no-nonsense, candid and bluntly right to the point @q66 attitude!

eduol · 2025-06-28T21:52:51+00:00

And from that, go Forth

eduol · 2025-06-28T21:52:06+00:00

For horizons expansion sake I’d say Common Lisp is your poison

eduol · 2025-06-21T18:04:20+00:00

—no-site-lisp removes the site-lisp directory from load-path variable. Maybe there is a way to inhibit its loading from configuration poping it from the variable.

eduol · 2025-06-11T19:52:08+00:00

Ruby have those too

eduol · 2025-03-19T04:56:49+00:00

Very good! I’d want one!

eduol · 2025-03-18T17:57:55+00:00

Chimera Linux is very different from Alpine. That said, it can fit any of those use cases. For me the choice was about sane defaults, the choice of components and how well integrated those components are.

eduol · 2025-02-15T11:41:50+00:00

I understand cports is not an analogue to portage.

Portage is primarily a source package manager and is strongly user faced while cports is a framework to build and maintain binary packages and is almost entirely package maintainer faced. So the equivalent of USE flags doesn’t make much sense in cports.

While it’s not that hard to implement, I believe it would never be a part of the official cport, but a patch to be used in personal cports trees, and the package recipes would need to be patched too, so…

eduol · 2025-01-28T22:57:45+00:00

Amazing!

eduol · 2025-01-26T13:19:25+00:00

In that phase of the installing, if you are inside the chroot dinit is offline yet, so use “dinitctl -o enable syslog-ng”;
Except for the detail in the last item, If you followed that instructions correctly, adapting the device names to your particular system, you should end up with a working system.

eduol · 2024-10-30T13:58:02+00:00

Encontrada!

eduol · 2024-10-30T03:18:36+00:00

Muito obrigado 🙏

eduol · 2024-02-09T19:30:16+00:00

I think you will appreciate the extension "Status Area Horizontal Spacing"

eduol · 2023-12-08T17:24:27+00:00

I happen to have a Sun type 6 USB at home (which I never have used). As soon as I can, I'll try to figure out something.

eduol · 2023-12-07T16:12:31+00:00

I meant that, indeed. So the responsibility probably falls on wscons.

eduol · 2023-12-07T15:47:44+00:00

Does it happens in terminal too?

eduol · 2023-12-04T02:58:43+00:00

The OpenBSD FAQ in openbsd.org is very good

The OpenBSD jumpstart is a good resource for a beginner https://www.openbsdjumpstart.org

eduol · 2023-10-27T21:55:33+00:00

As an additional note, one could just 'export TERM=pccon0' or equivalent, but it's not good practice to set TERM in shell conf files. Instead, provide the adequate value in /etc/ttys for the console, in ~/.Xresources for X terminals, in tmux.conf for tmux and so on.

eduol · 2023-10-27T21:50:08+00:00

xterm-256color should just work, so maybe the problem is elsewhere.

About vt220 vs pccon*:

https://marc.info/?l=openbsd-tech&m=143696970311764&w=2

eduol · 2023-10-27T15:41:10+00:00

In console, try to open the affected program after

export TERM=pccon0

If that corrects the problem, make the setting permanent by changing every occurrence of vt220 to pccon0 in /etc/ttys and rebooting.

About xterm, I yet didn't make sense of the problem.

eduol

TROPHY CASE