touch 'C:\WINDOWS\SYSTEM32'
touch 'C:\WINDOWS\SYSTEM32'
Read above please. You cannot import GPL code into BSD licensed code without restricting the code distribution. In the other direction, you can do it and just add a notice about the license. It does not add restrictions to the distribution. Otherwise Linux distributions wouldn’t even have OpenSSH in base install images.
Of other software, yes. For example Linux distributions can use the BSD or MIT licensed code without any problems.
But it does not allow to remove the license from the software.
On the other hand GPL code cannot be imported into BSD code without introducing restrictions.
If you think about how many people use proprietary Android by Google, it is exactly comparable.
Comparing numbers is pointless here. Fact is that GPL has more conditions when you’re allowed to use and modify the code. More conditions means more restrictions. And this means, less freedom.
At the moment large companies sponsor the development, without being forced to do so. And they allow developers to spend time on the project for free.
The foundation also makes sure that devs sign an agreement otherwise the code is not accepted.
So where is this all proprietary?
So it’s an argument against restrictive licenses? The more freedom the better? I mean Unix in this case had a too restrictive license?
Hi. Nobody here. Do you know that if you own a PS5 or Nintendo Switch, you’re a FreeBSD user?
Maybe we’ve got a different idea what it means to be a user.
Many manufacturers offer product sheets. You can also use price comparison websites. They sometimes offer an easy way to look at the specs or even compare them side by side.
Some hard drives are built for 24/7 operation. They have higher MTBF ratings and longer guarantees.
Hard drives are very different. Many of them waste energy, lie in the SMART log or just are weird (spin up and down, lose speed, get incredibly hot etc.)
I’ve been self-hosting Postfix for several years and it’s not difficult, if you’re absolutely confident what you do. I don’t recommend it if you don’t know basic behaviors and internals of SMTP and relaying. Also you need to know how to secure your server so you don’t get spammed a lot and getting hammered with brute force attacks.
From time to time you need to react to delivery problems. Most interesting one is perhaps Microsoft, which you need to ask to whitelist your server or your email won’t be accepted.
Stable is for servers, unstable for desktop. It has worked for 20 years. I actually installed two further Debian workstations recently after trying and failing with Kubuntu. So … no, I don’t have this problem.
No idea why busybox is needed. Is this is your emergency boot environment like initramfs? Sometimes it’s nice that Linux boots up and offers an environment to fix stuff while some modules are broken.
I recently removed my 25Gbps PCIe dual port cards from my 2 servers because they were using 20W more. My entire rack including 2 UniFi PoE connections uses 90 W now (so 110 W just for having 25 Gpbs).
There is some heat from such cards, but usually it gets transported outside fine. The ones I bought did not come with a fan. I think you cannot operate them without one. The heat sinks get very hot.
(Oops… wrong thread, I’ll leave it here)
I’ve been using FreeBSD for 20 years on my desktop. I’ve been also mainly using it because I was literally afraid of using Linux filesystems for data storage, when I learned how ZFS works.
Now with bcachefs the situation is different. It’s nice to see an advanced filesystem on Linux, even it’s still beta. I migrated my desktop to Linux, but will keep FreeBSD on my servers for a while, because it’s less hassle for me.
Actually I stopped liking the FreeBSD community. They made a lot of drama in the past years and I stopped being active there. I haven’t reported bugs anymore and fixed them privately or reported directly to upstream. I have many nice things running on servers, but I’m thinking about moving to Debian entirely.
You don’t want it until something fails. SystemD often doesn’t let you log in to fix it. It just shows a “infinitely bouncing asterisk” and hopes it will magically get better.
I had numerous situations where systemd didn’t let me abort a hanging service startup during boot or stop during shutdown.
So what do I do now, systemd? Wait till infinity??
That never happened while using other init systems. Because they simply fail properly (“sorry I did my best to stop this, I needed a SIGKILL finally”). Or simply let me log in: “sorry, some services failed to start and now it’s a huge mess, but at least you can log in and fix it.”.
You forgot: use as many dependencies as you need. For example, my init system does not use xz-utils
.
To keep the system simple and transparent.
Did you use iperf
? It makes sure that HDD/SSD is not the bottleneck.
You can also check the statistics and watch for uncommon errors. Or trace the connection with tcpdump
.
Yep. Unreal Tournament was also great and Neverwinter Nights.
Are you looking for something like cached credentials?