FreeBSD Foundation Flounders on 15 with Rust, pkgbase, and KDE

i had a zfs pool created out of a disk in other country (iscsi over ssh). but when connection broke it sucked. you had to reboot the iscsi initiator box to get rid of the unresponsive drive. even reboot wouldn't work at times, i had to panic it
 
So, unless you have a good remote access control mechanism in place, you can sit in Belgium, stick a USB stick into your physical machine, and forget about it. Then someone can, without flying in from the Australia, just format it, and even dd a fresh FreeBSD install iso on it. 😏 After all, as cracauer@ pointed out:
Doesn't NFS has less security.
 
I worked with SAN/NAS & ISCI in a public institution. It worked good. But was only used on the location.
Connection was with a fiber switch.
 
MacOS as a server during those times was pretty disastrous, especially NFS.
Remember when Apple used to sell rack-mounted Mac servers? 1U pizza boxes? I've heard from multiple sources that most of them were not actually run with MacOS on them; instead, people used them to boot AIX, since it was the cheapest way to get 1U PowerPC servers, and they were (like most Apple hardware) very well built, reliable, and fast. And a third or a fifth of the price of equivalent IBM gear.

After Apple moved to Intel CPUs, I think their rack-mount server business fell apart within about 5 years. They were trying to be competitive in a commodity market place, and that's not their DNA. Fortunately, they relatively quickly figured that out and abandoned the market.
 
MacOS servers were somewhat nice (not all config options were in the UI) but they would not keep the software updated properly (lagging security updates, skipping Java releases) and you couldn't configure it (unavailable PHP modules). Linux picked up steam and left them in the dust.
 
I'm 110% sure that the people against improving FreeBSD on desktop use either Windows or MacOS X.

And those of us who want it to succeed don't use either.
Well, you'd be wrong. I haven't touched a windoze or Mc-puter in several years. And what y'all seem to not understand is that it is NOT about improving desktop. It's about segregating and isolating application suites from the core OS. When you start to bundle is when you introduce a bias into the ecosystem toward certain functionalities. Everybody has their pet use, and hopefully the project leadership is wise and strong enough to keep those dogs at bay.
 
And what y'all seem to not understand is that it is NOT about improving desktop. It's about segregating and isolating application suites from the core OS. When you start to bundle is when you introduce a bias into the ecosystem toward certain functionalities.
Sorry, but allow me to disagree here... isolating GUI applications from the core OS is actually a fantastic design idea - Hell, this is how Firefox looks and works the same on FreeBSD and Windoze... Core OS provides the process space, then the application takes advantage of it. Same goes for WireShark.

At this point, I can say that functionalities and features are NOT the problem - they work fine on both UNIX and Windows. With FreeBSD, it's just a matter of shopping for compatible hardware. Lately, Microsoft gave up on license enforcement, and is now hiring malware writers so that it's easier to fingerprint a browser and log you into all kinds of places every time you reboot, without you even knowing that this is happening - unless you keep your eyes peeled.
 
Sorry, but allow me to disagree here... isolating GUI applications from the core OS is actually a fantastic design idea - Hell, this is how Firefox looks and works the same on FreeBSD and Windoze... Core OS provides the process space, then the application takes advantage of it. Same goes for WireShark.

At this point, I can say that functionalities and features are NOT the problem - they work fine on both UNIX and Windows. With FreeBSD, it's just a matter of shopping for compatible hardware. Lately, Microsoft gave up on license enforcement, and is now hiring malware writers so that it's easier to fingerprint a browser and log you into all kinds of places every time you reboot, without you even knowing that this is happening - unless you keep your eyes peeled.
no. we are saying the same thing so no need to disagree.
 
Well, you'd be wrong. I haven't touched a windoze or Mc-puter in several years. And what y'all seem to not understand is that it is NOT about improving desktop. It's about segregating and isolating application suites from the core OS. When you start to bundle is when you introduce a bias into the ecosystem toward certain functionalities. Everybody has their pet use, and hopefully the project leadership is wise and strong enough to keep those dogs at bay.
Such a valid point. This is why I think it may be in everyone's interest or preference to split such efforts into a separate distributed installation image. This way if the effort is ever dropped it will just kill an optional image from the build process.
 
I haven't used KDE since 3.5, but I'm wondering how well modern versions perform without hardware acceleration - especially on low end hardware. I've found support to be erratic.
 
Hell, this is how Firefox looks and works the same on FreeBSD and Windoze...
And how can Firefox work the same way, if I have repeatedly come across the statement on the forum that Firefox under FreeBSD is cut down (castrated). If this is so, then where can I read in detail about the fact that Firefox under FreeBSD is castrated and to what extent?
 
Gee.. I seem to remember vividly that around the turn of the century, 10 major FreeBSD versions ago when the world was still mostly in sepia, FreeBSD already offered a choice of desktop environments right in the installer. As long as there's a "no thanks" button, who's actually getting hurt by this? The PkgBase development is also something I can see the merit of. FreeBSD has a reliable mechanism in place for binary-updating 3rd-party software. Why not use it for other software as well and get rid of functional duplication? Putting Base in packages does not automatically imply drift between the packages. They can (and should IMHO) still be tested and released as frozen-in-time complete sets so that "Base" only ever means one thing with a singular version number. Off the cuff I'm thinking a single metapackage for all of Base that carries the canonical version-of-base, having the actual software itself as run-deps below it.

That said, I respect everyone's use case for different upgrade paths. I, personally, wouldn't dare upgrade a production system of any kind directly from source though. Those system resources are there for the business workload, not for compiling LLVM. But YMMV of course, and one should not exclude the other.
 
And how can Firefox work the same way, if I have repeatedly come across the statement on the forum that Firefox under FreeBSD is cut down.
If this is so, then where can I read in detail about..?
For a start, looking in the ports directory for Makefiles, and Gecko. Also, looking at source code. It helps to document as you learn, and for some, I show what I learned so others can see the difference and understand the status of the software they're working with. In my experience, a combination of the internet, books if applicable, trial and error, mailing lists and documentation. You can try searching on Mozilla's website, and defining what features you believe are missing. You can also get hints and suggestions in IRC.
 
For a start, looking in the ports directory for Makefiles, and Gecko. Also, looking at source code. It helps to document as you learn, and for some, I show what I learned so others can see the difference and understand the status of the software they're working with. In my experience, a combination of the internet, books if applicable, trial and error, mailing lists and documentation. You can try searching on Mozilla's website, and defining what features you believe are missing. You can also get hints and suggestions in IRC.
I think that USerID wanted pointers to blogs and YouTube videos where people actually complain how a recent version of Firefox is so wonderful on Windows because it runs Flash and .webm animations - and that they cannot get the same thing on FreeBSD. But if you do just a little bit of research and problem solving (like people do on these Forums), most of those differences are actually easy to solve, and the experience is actually quite comparable.

No need to get as deep down as you describe. Very easy to take most of those blogs and YouTube videos and completely rip them apart with just a bit of problem solving. The "then where can I read in detail about.. ?" was really meant to be read as sarcasm.
 
I think that USerID wanted pointers to blogs and YouTube videos where people actually complain how a recent version of Firefox is so wonderful on Windows because it runs Flash and .webm animations - and that they cannot get the same thing on FreeBSD.
As for Flash, forget about it. It used to give me a headache, on rare occasions when I got it to work, it crashed my FreeBSD system. Flash only worked well on NetBSD then, bc the system's ports were more stable and standard, to compensate for the unstableness of Flash.
But if you do just a little bit of research and problem solving (like people do on these Forums), most of those differences are actually easy to solve, and the experience is actually quite comparable.
Steve Jobs' vision was to replace Flash with applications working with HTML 5. (I didn't like Steve Jobs at all, but he was correct to do this.) This got done years after his passing. Now that Flash is no longer mainstream, we don't need it. I won't use Adobe products, if I can help it. They didn't listen to users who wanted Flash support for FreeBSD. Adobe also makes things unnecessarily complicated for their idea of keeping market share.

If this is the case, I suggest using NetBSD. I'm completely uninterested if this is about Flash. I've used to want Flash, but common sense got around this for displaying video on the Internet, and we don't need it anymore. Flash belongs in the dustbin of computer history and historical use operating systems. I love NetBSD, but that is the place for running BSD on a toaster, and for running varying generations of software, including legacy software. NetBSD is the operating system museum to see Flash run, when it would crash other operating systems.

NetBSD is also the operating system to diagnose computer hardware, and run hardware which doesn't have drivers on other systems.
 
The only thing I can't do in FreeBSD firefox is watch netflix and I guess prime, but both of those can be done with linux-brave or linux-chrome. I imagine if someone had the itch, they could add a linux-firefox that would also do it. I believe USerID when they say they have often come across a statement that firefox is cut down, but I would wager that many of said statements were simply from lack of experience. Or perhaps, someone getting really aggravated that they can't watch netflix or prime--I'm not being nasty here, I'm just sort of referencing the fact that sometimes we get posts like Disaster! I can't do whatever, and said disaster is either due to inexperience or someone getting overly excited, or sometimes, even someone writing in English who doesn't speak it that well, and using disaster (or another extreme term) due to mistranslation.

And by now, this 18 page thread has gotten completely off the original subject (he types, adding to the problem with several barely relevant posts), so, I should probably stop posting in this thread. :)
 
Back
Top