Latest activity

scottro had it mostly right. The Forums started out not only because other forums failed or went away, but also because people at FreeBSD felt it needed its own community support beyond the mailing lists. This was at a time when mailing lists...

scottro had it mostly right. The Forums started out not only because other forums failed or went away, but also because people at FreeBSD felt it needed its own community support beyond the mailing lists. This was at a time when mailing lists...

scottro had it mostly right. The Forums started out not only because other forums failed or went away, but also because people at FreeBSD felt it needed its own community support beyond the mailing lists. This was at a time when mailing lists...

scottro had it mostly right. The Forums started out not only because other forums failed or went away, but also because people at FreeBSD felt it needed its own community support beyond the mailing lists. This was at a time when mailing lists...

You can use openssl-x509 in a script and add it to periodic or cron. # openssl x509 -noout -dates -in domain.fullchain.pem notBefore=Oct 23 15:27:02 2025 GMT notAfter=Jan 21 15:27:01 2026 GMT

If you use security/py-certbot it already comes with a nice periodic weekly script. You just have to enable it in /etc/periodic.conf: weekly_certbot_enable="YES"

I didn't know that. I've been using old hardware for too long. :)

I want to install a periodic script to send out a reminder for certificates whose expiry is, say, imminent or recent, or a full list of certs with their expiry dates. A web search has only found (generic) solutions for checking active SSL certs...

Another favorite kitchen gadget: an old fashioned Mouli cheese grater. I use it for chopping up green chillies & garlic (used in a lot of Indian recipes)!

I also just tried to get SR-IOV working on 2 different hosts with X550 (x552 and x553) and on both the whole NIC goes completely silent as soon as VFs are created. Seems like either the ix driver or that chipset in general is buggy. With the...

Change firefox theme. There are three default themes in firefox: Light, Dark and System (light if GTK light theme, dark if GTK dark theme). Set System theme (it should be set by default) if does not work set the dark one. There is also an Firefox...

We have many different types of cheese. Of course cheddar is our national staple, and perhaps the best known worldwide. There are some special types of cheddar, such as cornish quartz cheddar from the Davidstow creamery. The quartz cheddar is...

Check out the Accel option from amdgpu(4). Occasionally I run into a flaky amd card and find I can prevent crashes whilst still benefitting from much of its functionality (resolution, power management) by simply disabling acceleration.

Another favorite kitchen gadget: an old fashioned Mouli cheese grater. I use it for chopping up green chillies & garlic (used in a lot of Indian recipes)!

Hello, All graphics card can work in vesa mode.

I do not have a Yubikey, but I wonder if the issue you have is related to security/keepassxc: Add PASSKEYS option. It adds passkey support with the browser integration. It is possible that it is needed for Yubikey too.

Original article here. Consider this when replying. FreeBSD, The FreeBSD Foundation, and The FreeBSD Forums are not associated with the content of this article.

Ken Thompson Recalls Unix’s Rowdy, Lock-Picking Origins.

It seems my end of the net is the problem. Thanks everybody for your help. I'll chase a little bit more what's funny here. I suspect the cause to be in the way my X11 is configured, or my xterm, or my environment, or my libc, or my Unicode, or my...

Don't even try. C can't give you that, it's your responsibility to keep track. The malloc function doesn't map directly to operating system calls. If you use it to allocate a few bytes, either there's already room left in your mapped address...

Desktop screenie from 20 years ago...

I don't know if I should mark this solved. I tried installing on qemu on Fedora, using virt-manager, and that worked with X without too much trouble. Pinging Charlie Brown just so he knows I did get X to work on qemu, so I guess it's a bhyve...

As long as you pick the right tag in the git tree (release, not stable) it should work. I don't think I have actually done that lately, though.

It appears that the nvidia-modeset module is included in any Nvidia driver. I recently upgraded to the latest Nvidia driver, which is version 580. Attempting to find nvidia-modeset on my system returns absolutely nothing. I am now wondering if...

Also, take a look at VirtualBox. This may fit the bill.

Ok, sorry, I found the mistake, I take everything back. :)

I am tracking the oldest STABLE version still supported, i.e. 13-STABLE at the moment, unless there is hardware not supported by the older version. That means that I have some systems on 14-STABLE and a single system on CURRENT. I build my...

It's a little less than that, that 512 byte block also includes the partition table. There's 446 bytes left for actual code.

Original article here. Consider this when replying. The FreeBSD Foundation is pleased to announce that it has completed work to build FreeBSD without requiring root privilege. We have implemented support for all source release builds to use...

I use the default Xorg cursor.

I have read the wiki pkgbase entry and the forum thread on the subject, and (assuming the information is up-to-date) I am worried. It looks much more complicated than freebsd-update and there are many pitfalls for the less competent. I did not...

Update: Plans have changed. freebsd-update will remain supported for the full 15.x branch, including for security updates. In 2003, freebsd-update arrived, allowing users to perform binary updates from one FreeBSD release to another. That's a...

Because the answer to your question is "No". Here's the code: https://cgit.freebsd.org/src/tree/stand/i386/boot0/boot0.S It simply looks at the partition info and does a bit of educated guessing. That's all it can do in a few bytes of code.

If the compiler chain is still working a `make buildworld && make installworld` is a safe option for a running system.

Original article here. Consider this when replying. FreeBSD, The FreeBSD Foundation, and The FreeBSD Forums are not associated with the content of this article.

It was just to trace the function to see the values of the variables. My guess is that you didn't copy/paste from the rc.conf on the machine and that there was a typo in wlans_ and we wouldn't have seen anything. I don't see an other reason here...

PCUser, you're replying to a year-old thread. Nowadays, the best advice when it comes to Xorg is to keep it without any configuration file at all, unless you're having an issue or you need to set some specific settings.

Steam is living on borrowed time. It is held together by a sane and relatively user-friendly owner. The moment there is a leadership or ownership change the general enshittification of the Internet will cover Steam.

If you configured the (wireless) network during the installation, the installer would have added them.

The message is shown because 14.1-RELEASE will be EoL at the end of March 2025 (in about 2 months; that's 3 months after the release of 14.2). Patch level has very little to do with it.

The first step toward security is data minimization. You can't get scammed by email if no one knows it.

Of course it's one way to solve the problem. But at the cost of complexity. One could use procmail or slocal. Both of which don't require admin access to any SMTP server. If you're so inclined, that's fine. If you're not, you're not hosed. You...

Yes, if an errata or security patch didn't involve the kernel it won't show the same patch level as the userland, that's normal. If you have 14.0, 14.1 or 14.2 though, then it's going to complain your system is outdated and needs to be upgraded...

dice@williscorto:~ % bash [dice@williscorto ~]$ printf '<\u2122>\n' <™> [dice@williscorto ~]$ echo $XTERM_VERSION XTerm(403) [dice@williscorto ~]$ echo $LANG C.UTF-8 Seems to do what it's supposed to do.

Will check when I have access. But yes, I guess the problem is that the kernel is "older" than the patchlevel. But the kernel isnt always updated by freebsd-install at every patchlevel.

Original article here. Consider this when replying. FreeBSD, The FreeBSD Foundation, and The FreeBSD Forums are not associated with the content of this article.

The heart of the matter is what you wrote isn't relevant to solving the problem. Why talk about? Why tell or even imply people must run their own SMTP server to solve the problem?

Use gpart. https://docs.freebsd.org/en/books/handbook/disks/#disks-adding

What does freebsd-version -urk show?

I also have this problem. I have freebsd-update cron in my crontab. Because of this I get emails from freebsd-update every day even though my machines are updated to the latest patchlevel. This cant be how freebsd-update cron should behave?