Of course it's cool and tricky, but I would metaphorically smack anyone who did that up side the head, while yelling "bad engineer! no cookie!"
Actually, someone may come up with some esoteric need, but I'd more take offense to it if the...
Update 2:
In FreeBSD 15-STABLE loading from /etc/rc.conf
vboxguest_enable="YES"
vboxservice_enable="YES"
works okay with X/Plasma6 again, no need for using /etc/rc.local for vboxguest
Here in text form:
UNIX
The pfjson(1) Tool to Convert OpenBSD Packet Filter Configuration to/from JSON.
https://github.com/fleximus/pfjson
Modern Messaging: Running Your Own XMPP Server...
When we move to pkgbase, will we have all those few hundred system packages listed in pkg info, or will we have some sort of separation?
For example I dislike how dpkg -l on a minimal Debian install still spews out few screens of packages...
I always upgrade when the version I currently run is EOL at the earliest.
Especially in this case 15 seems to bring some major changes, so I expect it to still have some flaws left at official release. That ain't no malice insinuation. It's...
This is the exact reply I did not want to get. I'll refrain from posting sarcastic remarks about the discovery of grep.
It is what it is and I don't like it.
I am actually considering switching some of my machines to NetBSD, as I feel like FreeBSD is going down a road to Linux. NetBSD has a better non-linuxified X implementation, and no pkgbase. I fear I will have to stick on 14.x until it is EOLed...
in 15.0, our ancient Heimdal 1.5 was replaced with MIT Kerberos. this means we now support modern key types (Heimdal was limited to aes256-sha1, and defaulted to DES), and the new libgssapi implementation provides better compatibility with...
Exactly. I will stay on 13.x as long as there is a supported 13.x version. Then I will switch to 14.x, and stay on that as long as there is support, which I think is until 2028 or thereabouts. Not clear yet whether I will move to 15.x ever; that...
Most of the more complex drivers for Intel chips in the Linux kernel are written by Intel. It is simply unknown whether the documentation is sufficient for writing drivers without internal help.
Gotta be the gas stove. Concerns over nitrates leading to cognitive decline are overblown - that ship sailed long ago. When the power goes out (as it often does in my neighborhood) I can still have hot food.
Not sure I buy that. My limited understanding of compilers is high level language -> intermediate machine-agnostic representation -> machine-specific assembler code. Assembly is always there.
Design bug or not, it needs to be handled correctly without crashing. Going back to the Android OpenGL context example, the responsibility is on the app developer to handle lost GL contexts. There are i.e discussions like this.
That is my point...
Unfortunately Rust can't protect the data from being stripped out under it.
Same with the difficulty of using C (or traditional C++) middleware with smart pointers. Unless Rust "owns" the memory, it can still only make (educated) guesses at its...
This would be best achieved by separation of used language with whether or not the part can be memory safe or not. Keeping mutually memory unsafe parts in C and/or asm, other to some memory safe languge, in source file level.
This way, any part...
Yes. And now they want to burden those who do this on a daily basis with keeping the ffi up to date? Let's see how long it takes to turn into a fui, and the burden to keep it up is placed on the rust people. Then a stunt or two from the crowd...
Let the rust jerks go and write their own operating system then, instead of trying to get a free ride on the back of freebsd's success, which they never contributed to.
And remember: your turn will come, sunshine, nothing is more certain. Some...
This is the same problem DMD D had and why it was removed from ports when upstream failed to implement 64-bit inodes. They couldn't implement the ifuncs needed to allow both old and new support.
a radxa orion board which is basically the same thing sells for 400 euros on aliexpress.without case, ram, psu or storage. freebsd may somehow work on it with half the hw supported and it will probably be less usefull than a vm on apple silicon
High levels of confirmation bias politics in here.
sudo(8) was developed by Todd C. Miller (an OpenBSD developer) and released under a permissive licence.
I think much of the hate for it comes from the classic Ubuntu style implementation as a...
I had to restore the SourceSafe "database" from tape about once a month for a job I had early on. Yes, that would erase weeks' worth of the whole team's work. I think people kept local copies. Good luck when your workstation's hard drive fails...
My understanding is it's correct.
As BETA1 is built using releng/15.0 branch, which 15.0-Release is going to be built after several planned BETA and RC.
On the other hand, stable/15 should now be considered as "branch for preparaion of next...
Design bug or not, it needs to be handled correctly without crashing. Going back to the Android OpenGL context example, the responsibility is on the app developer to handle lost GL contexts. There are i.e discussions like this.
That is my point...
Confirmed that the following two sysctls, if their value is requested, will log a kernel message:
sys.device.drmn0.pp_mclk_od
sys.device.drmn0.pp_sclk_od
kernel: amdgpu: pp_dpm_get_mclk_od was not implemented.
kernel: amdgpu...
Yes and no. Do you have the constructs in a language to stop the code from using these pointers behind your back while you still figure out if they are valid?
Unfortunately Rust can't protect the data from being stripped out under it.
Same with the difficulty of using C (or traditional C++) middleware with smart pointers. Unless Rust "owns" the memory, it can still only make (educated) guesses at its...
Oh, you would be surprised what can happen. Consider this:
dma->src = source;
dma->dst = dest;
dma->size = len;
Now, these registers are right next to each other in the address space. The compiler could figure out that invoking the load store...
In case I wasn't clear, I tried tracking stable/15 to chase a nvme-related bug that crashes the system after the second suspend/resume cycle. The virtualbox module is the only one that I use which doesn't have a version 1500500 in the repos...
Here in a 14.3-p4 install I've tried a couple times now to build Firefox-esr from the port. Going from 1.28 to 1.40. It updates rust something else I can't recall, and then installs without issue. When I run it, either from a menu click or by...
That's exactly my point. I was expecting to find 1500500 in the repos (it is not there) and building from ports, with the appropriate kernel sources, I now have a functioning kernel module.
We don't have separate build for minor release on the same major releng version, this applies to stable too.
So for amd64 there is only 13.x, 14.y, 15.z and 16.w build, where x,y,z,w are the latest supported minor version respective to the major...
FYI: We are about to order a DL320 Gen11 with Gold 6548Y+, 128 GiB RAM, 2x300 GB HDD for OS and 6x2,4 TB (RAID Z2) on HPE MR408i-o Gen11 storage controller in HBA mode. Host will run bhyve for several virtual machines, no hyper threading. Will...
I'll give that a try later today. (US, EDT, about 6:00 AM right now, I'll probably get to it in the afternoon). I did already emerge the fbdev driver, that didn't do the trick, but going to try the --deep @world and see what happens.
You can try to set VIDEO_CARDS="fbdev" in /etc/portage/make.conf and */* VIDEO_CARDS: -* fbdev in /etc/portage/package.use/00video
and then
emerge --getbinpkg --ask --changed-use --deep @world
Also, if not already pulled by emerge, try...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.