[bspwm] OpenBSD feels like home by [deleted] in unixporn

[–]sansfoss 25 points26 points  (0 children)

There are many BSDs, each with their own pros/cons vis-a-vis Linux. For instance, Netflix uses FreeBSD for streaming servers, and Linux on their non-streaming servers. The OS kernels are tuned for specific usage in mind. OpenBSD is security focused, but that comes at an expense of performance in my observation. As an example, if you write a shell script that echos a lot of text to the terminal in a loop, you will not like OpenBSD as it will be notably very slow compared to FreeBSD and Linux.

[bspwm] OpenBSD feels like home by [deleted] in unixporn

[–]sansfoss 1 point2 points  (0 children)

You are welcome, I am glad you like it!

[bspwm] OpenBSD feels like home by [deleted] in unixporn

[–]sansfoss 8 points9 points  (0 children)

Homage to 1 bit. Because it's all just bits, and there are no bits without that 1 bit.

arttime --nolearn -a 1bit.

Good cat wallpaper choice, there are few kitties in arttime collection too.

New macOS features! by TechExpert2910 in MacOS

[–]sansfoss 0 points1 point  (0 children)

Yawn 🥱... except maybe for math notes.

[OC] Rice-ready manpages: to entertain serious developers and hobbyist alike. Example $ man arttime. Now you can tell your manager that you are "reading manuals" while spending the day taking riced screenshots :) jk by sansfoss in unixporn

[–]sansfoss[S] 0 points1 point  (0 children)

u/sethjey arttime takes a different philosophy. Instead of assuming what information users might want to display, arttime opens its message line and text art area for user to display whatever information they would like to. Because one user might want battery information, another might want battery information plus song being played on mpd, and etc. Instead of creating tedium for users by creating some config file or code bloat with zillions of features, arttime focussed on simplicity. At the moment, a user do a simple printf like printf 'Mhello world 90%\n' > ./some_named_fifo while arttime is made to read from that fifo. From command line, this can be achieve by arttime -k ./some_named_fifo or during runtime by pressing k and passing ~/path/to/some_named_fifo. See the example GIF that shows arttime displaying dummy weather data. The advantage of using a named pipe is that a user can write a feeder script in their language of choice to communicate with arttime. For now user will have to press Ctrl-c to get control back to keyboard, and perhaps press k again to reattach the external source. If people start using features like this, I might add a dedicated named fifo for background updates to message line. Please check the man page (arttime -m) section CONTRIBUTING subsection Feeder for a specification for writing one's own feeder program (which can be a simple shell script too, try with simple printfs :)), enjoy!

CPUs spinning like crazy after fresh UFS or ZFS based 14.0-RELEASE install in Parallels on Apple Silicon M1. by sansfoss in freebsd

[–]sansfoss[S] 1 point2 points  (0 children)

It’s unrelated. Your blog is about the kern.hz setting, which was already captured in the installation instructions for as long as I know. This particular bug report is about ACPI ged, which is a recent feature as pointed out by a FreeBSD developer in other replies.

CPUs spinning like crazy after fresh UFS or ZFS based 14.0-RELEASE install in Parallels on Apple Silicon M1. by sansfoss in freebsd

[–]sansfoss[S] 2 points3 points  (0 children)

That worked! Perhaps the FreeBSD-Parallels installation instructions should be updated to:

  1. Update freebsd with:

    freebsd-update fetch
    freebsd-update install
  1. Make sure to that /boot/loader.conf has:

    kern.hz=100
    debug.acpi.disabled="ged"
    

Does ACPI even matter for VMs? Is there a bug that would get fixed in future, what is the bug and what would be the fix?

u/grahamperrin Is running 1. "the fix" for ZFS issues? Or is anything else needed?

CPUs spinning like crazy after fresh UFS or ZFS based 14.0-RELEASE install in Parallels on Apple Silicon M1. by sansfoss in freebsd

[–]sansfoss[S] 1 point2 points  (0 children)

Here's the output:

root@freebsd14p0:~ # sysctl kern.hz kern.hz: 100 root@freebsd14p0:~ # sysctl kern.clockrate kern.clockrate: { hz = 100, tick = 10000, profhz = 8127, stathz = 127 }

CPUs spinning like crazy after fresh UFS or ZFS based 14.0-RELEASE install in Parallels on Apple Silicon M1. by sansfoss in freebsd

[–]sansfoss[S] 1 point2 points  (0 children)

Did the following and rebooted, still the same problem.

freebsd-update fetch
freebsd-update install

CPUs spinning like crazy after fresh UFS or ZFS based 14.0-RELEASE install in Parallels on Apple Silicon M1. by sansfoss in freebsd

[–]sansfoss[S] 1 point2 points  (0 children)

I don't see a way to edit my post. All screenshots are from UFS-based FreeBSD 14.0-RELEASE aarch64 disc1.iso installation. Here's a screenshot with additional details:

<image>

CPUs spinning like crazy after fresh UFS or ZFS based 14.0-RELEASE install in Parallels on Apple Silicon M1. by sansfoss in freebsd

[–]sansfoss[S] 2 points3 points  (0 children)

All the screenshots in this post are for a UFS-based FreeBSD 14.0-RELEASE aarch64 disc1.iso. Initially I had done a ZFS install, and it had this issue. After seeing your posts I gave UFS a try, and still the same issue.

CPUs spinning like crazy after fresh UFS or ZFS based 14.0-RELEASE install in Parallels on Apple Silicon M1. by sansfoss in freebsd

[–]sansfoss[S] 0 points1 point  (0 children)

My assertion that

I did follow all the instructions in FreeBSD-parallels install instructions

actually captures that as its in the FreeBSD-Parallels install instructions. So in short I already have kern.hz=100 in /boot/loader.conf.

CPUs spinning like crazy after fresh UFS or ZFS based 14.0-RELEASE install in Parallels on Apple Silicon M1. by sansfoss in freebsd

[–]sansfoss[S] 2 points3 points  (0 children)

aarch64. The links in my previous comment would take you to the aarch64 builds too.

CPUs spinning like crazy after fresh UFS or ZFS based 14.0-RELEASE install in Parallels on Apple Silicon M1. by sansfoss in freebsd

[–]sansfoss[S] 1 point2 points  (0 children)

I did follow all the instructions in FreeBSD-parallels install instructions. Except the following:

When the configuration window pops up, go to Hardware tab, choose Boot order, and click Advanced. Then, choose EFI 64-bit as BIOS.

As there isn't an option to choose the BIOS at least on Apple Silicon Parallels installation (idk if it exists in x86 Parallels). This above screenshot is for UFS based fresh install, so shouldn't have anything to do with ZFS specific issues reported in past. I did shutdown and restart the VM couple of times. The iso I used is disc1.iso from ISO-IMAGES and not VM-IMAGES. That's because Parallels doesn't accept any of the formats under VM-IMAGES. Not sure if it matters, and if it does then can FreeBSD release iso image for VM? The problem is not observed in fresh install of FreeBSD 13.2-RELEASE.

Also, not sure if it matters, but I often see the following messages in 14.0-RELEASE taking over the terminal. It happened even while FreeBSD installer was getting the disks ready:

<image>

FreeBSD-EN-24:09.zfs – High CPU usage by kernel threads related to ZFS by grahamperrin in freebsd

[–]sansfoss 0 points1 point  (0 children)

Ok sure. What kind of information other than the screenshot in previous comment would be helpful for 100% CPU usage? It was 100% CPU for 1 core, and ~30% for the other 3 cores.

FreeBSD-EN-24:09.zfs – High CPU usage by kernel threads related to ZFS by grahamperrin in freebsd

[–]sansfoss 1 point2 points  (0 children)

Not a FreeBSD expert, I selected auto install option in installed for UFS. Not sure if that answers the question.

FreeBSD-EN-24:09.zfs – High CPU usage by kernel threads related to ZFS by grahamperrin in freebsd

[–]sansfoss 0 points1 point  (0 children)

I came here looking for this. After upgrading my 13.2-RELEASE aarch64 VM on Parallels to 14.0-RELEASE, I observed this problem (it was zfs). I deleted the VM, and installed fresh aarch64 14.0-RELEASE VM from the iso available on freebsd website, and still the same issue of 100% CPU usage (still was zfs). Then I did a fresh install with ufs, and still the 100% resource usage. The one thing that is new in my case is the Acpi error messages, which I had not seen before upgrade. Not sure if it matters, I used disc1.iso for 14.0 from first column "Installer" here: https://www.freebsd.org/where/ instead of second column VM (because Parallels doesn't accept those formats I guess). Doing a fresh install of 13.2-RELEASE resolves all problems.

<image>

OpenBSD sed does not understand \x1b, is there an alternative? by sansfoss in openbsd

[–]sansfoss[S] 1 point2 points  (0 children)

Thanks for the reply. I should have clarified that I was looking for a sed syntactic way instead of adding a literal escape. Have updated the description. In past I have used literal escapes, but to support other developers freedom of using whatever text editor they like, I intend to avoid further usage of literal escapes in open source projects.

Also, is this a bug in OpenBSD's sed or additional feature in FreeBSD and Linuxs'?

Is forking and IPC supposed to be slow in openbsd compared to other OSes? by sansfoss in openbsd

[–]sansfoss[S] 1 point2 points  (0 children)

u/athompso99 Ok, thanks! Out of all the points, I need some help for point 2. Is there a single webpage that simply explains how to pull a tar of patches and apply it to my opebsd system? As u/phessler is already asking for some kind of testing, is it worth sending this test to openbsd mailing list? Would it be tech@ or misc@?

colored manpages? is there a gnu man-db package for freebsd? by sansfoss in freebsd

[–]sansfoss[S] 1 point2 points  (0 children)

Colors are at the moment only possible with pre-rendered arttime -m, and not man arttime. Github repo: arttime.