Search
483 results for “zirias”
-
Why in the world do companies continue to rely on the #Windows platform? 😠
At our place, the solution to work at home is "#Citrix Workspace" (which internally already got the nickname "shitrix" for the various/random issues it causes every few weeks). There's no version for #FreeBSD, and I didn't succeed running the #Linux version on FreeBSD yet (different story), so I grabbed a copy of "Windows Server 2022" from our MSDN subscription and installed it in a #bhyve VM. Of course, to use it, you also need a browser...
Two days ago, this machine installed some Windows updates again. Yesterday, I found my #Chromium broken (shows window, exits silently). Updating it to the latest version didn't help. Trying to run #IE11 (still linked as default browser on the server version) froze the whole machine, requiring a force-kill of the VM.
This morning, I found that #Edge works now (yay, I can access the workplace again), which it didn't few months ago for .... "reasons" 🤯
-
Why in the world do companies continue to rely on the #Windows platform? 😠
At our place, the solution to work at home is "#Citrix Workspace" (which internally already got the nickname "shitrix" for the various/random issues it causes every few weeks). There's no version for #FreeBSD, and I didn't succeed running the #Linux version on FreeBSD yet (different story), so I grabbed a copy of "Windows Server 2022" from our MSDN subscription and installed it in a #bhyve VM. Of course, to use it, you also need a browser...
Two days ago, this machine installed some Windows updates again. Yesterday, I found my #Chromium broken (shows window, exits silently). Updating it to the latest version didn't help. Trying to run #IE11 (still linked as default browser on the server version) froze the whole machine, requiring a force-kill of the VM.
This morning, I found that #Edge works now (yay, I can access the workplace again), which it didn't few months ago for .... "reasons" 🤯
-
Why in the world do companies continue to rely on the #Windows platform? 😠
At our place, the solution to work at home is "#Citrix Workspace" (which internally already got the nickname "shitrix" for the various/random issues it causes every few weeks). There's no version for #FreeBSD, and I didn't succeed running the #Linux version on FreeBSD yet (different story), so I grabbed a copy of "Windows Server 2022" from our MSDN subscription and installed it in a #bhyve VM. Of course, to use it, you also need a browser...
Two days ago, this machine installed some Windows updates again. Yesterday, I found my #Chromium broken (shows window, exits silently). Updating it to the latest version didn't help. Trying to run #IE11 (still linked as default browser on the server version) froze the whole machine, requiring a force-kill of the VM.
This morning, I found that #Edge works now (yay, I can access the workplace again), which it didn't few months ago for .... "reasons" 🤯
-
Why in the world do companies continue to rely on the #Windows platform? 😠
At our place, the solution to work at home is "#Citrix Workspace" (which internally already got the nickname "shitrix" for the various/random issues it causes every few weeks). There's no version for #FreeBSD, and I didn't succeed running the #Linux version on FreeBSD yet (different story), so I grabbed a copy of "Windows Server 2022" from our MSDN subscription and installed it in a #bhyve VM. Of course, to use it, you also need a browser...
Two days ago, this machine installed some Windows updates again. Yesterday, I found my #Chromium broken (shows window, exits silently). Updating it to the latest version didn't help. Trying to run #IE11 (still linked as default browser on the server version) froze the whole machine, requiring a force-kill of the VM.
This morning, I found that #Edge works now (yay, I can access the workplace again), which it didn't few months ago for .... "reasons" 🤯
-
@governa With the #CC65 compiler (#C only) already along for a long time, did anyone compare the results?
https://cc65.github.io/doc/cc65.html -
@governa With the #CC65 compiler (#C only) already along for a long time, did anyone compare the results?
https://cc65.github.io/doc/cc65.html -
@ojs @OpenBSDAms A C-Shell is a traditional default shell in #BSD systems (#FreeBSD uses the #tcsh implementation). So, finding at least a default configuration isn't too surprising.
-
@meka not really. In a jail, using Gentoo's "portage" to build packages probably would make sense. But the #Linuxulator userland should not run jailed but instead integrated (by means of the "overlay" that's by default in /compat/linux) with the #FreeBSD userland, so it can (mostly!) access the same files at the same paths. This comes with additional requirements and also additional challenges building the packages (so unmodified portage wouldn't work either). It makes more sense using #FreeBSD ports for that, as you probably want FreeBSD packages. Moreover, it's possible to "bootstrap" that without the need for any Linux binary, by first cross-compiling the #GNU toolchain, I got this part working somewhat well 😉
-
@meka Unfortunately, I hit a roadblock (needing #rust for #Linuxulator before getting to a point where I could actually test some closed-source #Linux software) and didn't find time to experiment building that on #FreeBSD. So, no conclusion yet, and to continue, I'd have to go through the whole branch again first and at least upgrade everything .... 😞
-
@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 😞
-
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? 🤔
-
@glitch25 it's just a side note, but IMHO, the #C64 *was* a game console.
I know ppl are surprised by that claim, but then look at the hardware first: The gfx chip #VIC (-II) controls the bus (CPU runs in sync with it), shares RAM with the CPU, offers versatile and efficient tiled display modes (as well as bitmapped), offers hardware interrupts, dedicates most of its silicon to #sprites, etc. The sound chip (#SID) offers a full programmable 3-channel synthesizer. There are I/O ports with both digital and analog lines suitable for lots of game controller devices. There's a clever banking logic allowing to make good use of the whole 64K RAM.
Now look at the half-assed OS. There's the #KERNAL (sic!) by #Commodore, mostly offering I/O streams and only using some timer interrupt, more or less what a #PET could do. On top of that, there's just Microsoft's #BASIC as the only user interface. None of that can make use of any of the hardware features described above. 😏
-
@CyDeFect @FiLiS In theory, yes. In practice, not so much. The #gvfs-based approach creates "weird" mountpoints in a user scope. The #smbnetfs variant creates some "dynamic" mountpoint where you have to access a hostname/ip-address using it as it was a subdirectory. Both not what I would have needed for home directories via #SMB3. Plus, they both perform badly.
So, in my case, just using #NFS for #FreeBSD clients (and still offering #SMB3 via #samba for #Windows clients) was the sanest solution.
-
@CyDeFect @FiLiS all of these are missing too many details to tell anything about them. Except for #CIFS (although you probably don't even want that but #SMB3 instead, #Linux just kept tthe "CIFS" name although supporting SMB3), all #FreeBSD offers is indeed #SMB1. Whether this is an issue or not depends on your scenario and environment. I just offer my shares via #NFS as well, problem solved for me.
BTW, #seamonkey was removed mainly because of a #python2 (EOL for a long time) build dependency. IIRC this is meanwhile solved, so the port *could* be readded, it's just someone would have to do it and maintain it. There's an inofficial port available, you'll find it on the forums.
-
@CyDeFect @FiLiS all of these are missing too many details to tell anything about them. Except for #CIFS (although you probably don't even want that but #SMB3 instead, #Linux just kept tthe "CIFS" name although supporting SMB3), all #FreeBSD offers is indeed #SMB1. Whether this is an issue or not depends on your scenario and environment. I just offer my shares via #NFS as well, problem solved for me.
BTW, #seamonkey was removed mainly because of a #python2 (EOL for a long time) build dependency. IIRC this is meanwhile solved, so the port *could* be readded, it's just someone would have to do it and maintain it. There's an inofficial port available, you'll find it on the forums.
-
@CyDeFect @FiLiS all of these are missing too many details to tell anything about them. Except for #CIFS (although you probably don't even want that but #SMB3 instead, #Linux just kept tthe "CIFS" name although supporting SMB3), all #FreeBSD offers is indeed #SMB1. Whether this is an issue or not depends on your scenario and environment. I just offer my shares via #NFS as well, problem solved for me.
BTW, #seamonkey was removed mainly because of a #python2 (EOL for a long time) build dependency. IIRC this is meanwhile solved, so the port *could* be readded, it's just someone would have to do it and maintain it. There's an inofficial port available, you'll find it on the forums.
-
@CyDeFect @FiLiS all of these are missing too many details to tell anything about them. Except for #CIFS (although you probably don't even want that but #SMB3 instead, #Linux just kept tthe "CIFS" name although supporting SMB3), all #FreeBSD offers is indeed #SMB1. Whether this is an issue or not depends on your scenario and environment. I just offer my shares via #NFS as well, problem solved for me.
BTW, #seamonkey was removed mainly because of a #python2 (EOL for a long time) build dependency. IIRC this is meanwhile solved, so the port *could* be readded, it's just someone would have to do it and maintain it. There's an inofficial port available, you'll find it on the forums.
-
@CyDeFect @FiLiS all of these are missing too many details to tell anything about them. Except for #CIFS (although you probably don't even want that but #SMB3 instead, #Linux just kept tthe "CIFS" name although supporting SMB3), all #FreeBSD offers is indeed #SMB1. Whether this is an issue or not depends on your scenario and environment. I just offer my shares via #NFS as well, problem solved for me.
BTW, #seamonkey was removed mainly because of a #python2 (EOL for a long time) build dependency. IIRC this is meanwhile solved, so the port *could* be readded, it's just someone would have to do it and maintain it. There's an inofficial port available, you'll find it on the forums.
-
@sourcerer @vermaden speaking of audio, the mess (really) started when #Linux devs deemed their #OSS variant "unfixable" and started with #ALSA. Introducing a shared lib here (libasound) lead to tighter coupling. And it got worse adding complex layers of "sound servers" on top.
#FreeBSD's native audio interface is still good old OSS/USS (based on /dev/dsp). It offers good quality, low latency AND "software mixing" of multiple playback clients out of the box, invalidating the reasons that in Linux world, the breaking change towards ALSA *had* to be done.
Still, what we see *now* is a decreasing number of applications supporting OSS, just because Linux typically doesn't offer it any more. 🙄
So far, I could make everything I needed work using either #sndio (a somewhat minimal sound server originating from #OpenBSD), native OSS, #SDL, and (rarely needed) ALSA using the OSS backend...
-
@nixCraft #FreeBSD user on both desktop and server (incl. firewall) as well as #ports maintainer here:
My answer (ASAP) is an approximation.
For the base system, I read the published #advisories ASAP. I decide whether I'm affected, and how exposed my different machines are. If necessary, I rebuild base from source and update all machines needing the update ASAP.
For ports, I try to keep an eye on "exposed services" (like e.g. my MTA) for servers and at least browsers for desktops. Actually installing an update can take two or three days because I'm building my own package repository using #poudriere.
-
From a profile post on FreeBSD #forums, I learned #FreeBSD had a driver to play "music" on the #PCspeaker from the very first version.
This is awesome 😂 Well, silly, almost entirely useless, but, awesome 😎
I just HAD to experiment with this while waiting for another large poudriere build, here's a first ugly result 🙈 (run after "kldload speaker")
https://people.freebsd.org/~zirias/nonsense/billie.sh -
CW: Honest Q about Unix vs Linux
@uma @kaleb_haugen "does not have any kind of upstream code" is not true. Every #BSD system includes *some* software in its base that's pulled from some other party. E.g. #FreeBSD has #OpenZFS, #Heimdal, #LLVM and #OpenSSL in its base, to name just a few.
But then, these aren't just "packaged", they're pulled into the single source repository from which the system is built and care is taken they integrate "perfectly".
-
@thindil I was talking about maintenance pain for devs btw. I assume much of it stems from having *most* of #LinuxKPI in the base kernel (where it actually belongs), but GPL-parts in the port, and also some fixes even duplicated (because the port must work on systems that didn't receive the fix from the main branch of base yet). With everything in the base kernel, you could maintain it in one place, and MFC fixes as a whole (and, if needed create ENs to also update RELEASE versions).
Of course, everyone wants a "reasonable" small base, discussions often evolve around what "reasonable" exactly is 😎
-
@thindil I was talking about maintenance pain for devs btw. I assume much of it stems from having *most* of #LinuxKPI in the base kernel (where it actually belongs), but GPL-parts in the port, and also some fixes even duplicated (because the port must work on systems that didn't receive the fix from the main branch of base yet). With everything in the base kernel, you could maintain it in one place, and MFC fixes as a whole (and, if needed create ENs to also update RELEASE versions).
Of course, everyone wants a "reasonable" small base, discussions often evolve around what "reasonable" exactly is 😎
-
@thindil I was talking about maintenance pain for devs btw. I assume much of it stems from having *most* of #LinuxKPI in the base kernel (where it actually belongs), but GPL-parts in the port, and also some fixes even duplicated (because the port must work on systems that didn't receive the fix from the main branch of base yet). With everything in the base kernel, you could maintain it in one place, and MFC fixes as a whole (and, if needed create ENs to also update RELEASE versions).
Of course, everyone wants a "reasonable" small base, discussions often evolve around what "reasonable" exactly is 😎
-
@thindil I was talking about maintenance pain for devs btw. I assume much of it stems from having *most* of #LinuxKPI in the base kernel (where it actually belongs), but GPL-parts in the port, and also some fixes even duplicated (because the port must work on systems that didn't receive the fix from the main branch of base yet). With everything in the base kernel, you could maintain it in one place, and MFC fixes as a whole (and, if needed create ENs to also update RELEASE versions).
Of course, everyone wants a "reasonable" small base, discussions often evolve around what "reasonable" exactly is 😎