Skip to content

Blogs

5 Topics 25 Posts

Blog posts from individual members

This category can be followed from the open social web via the handle blogs@billboard.bsd.cafe

  • [Stephane HUC] (it-log.fr.eu.org)

    11
    0 Votes
    11 Posts
    688 Views
    CiotBSDC
    Weekly Echoes #2026W46: Open IT (Data, Hardware, Software, Standards) news, round-up, for the week 46; from 11/09 to 11/15. https://it-log.fr.eu.org/en/echoes/week-46-2026/
  • [in french] Installing dotclear on FreeBSD

    1
    0 Votes
    1 Posts
    156 Views
    UsulU
    For one of my blogs, I use dotclear, and wrote in french, notes when I did the installation at https://ludovic.hirlimann.net/2023/04/installer-dotclear-sur-freebsd-13.html #freebsd #dotclear
  • My initial thoughts about NomadBSD

    1
    0 Votes
    1 Posts
    117 Views
    UsulU
    https://ludovic.hirlimann.net/2024/05/giving-nomadbsd-spin.html I was unable to have it work on my latest work laptop, but I'll retry cause it was nice with the newer 15.1 based release. #nomadbsd
  • Monitor your devices with LibreNMS on FreeBSD

    8
    6 Votes
    8 Posts
    434 Views
    mware@ottawa.placeM
    @stefano there's even a port & pkg
  • Stop Opening Huge Files in Screen Editors

    4
    4 Votes
    4 Posts
    609 Views
    mhdM
    As another data point in comparing how different editors work, here's an old one by the author of the very undervalued joe editor. In general, there's nothing preventing screen editors from working properly and fast here, it's just not something they optimized for. If they did it at all, internal editor data structures tend to be quite simple these days, as virtual memory works for most cases. People had to get a lot more tricky on smaller devices (or they gave up early, cf. Windows Notepad). Heretically, I'd also like to say that a lot of files that aren't binary and huge, different tools often wouldn't point at e.g. sed, as you're running into the old "Now they have two problems." issue then.