Because Shiny Things Are Fun - The New New Windows v Linux Thread
GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
No, I actually stopped using FreeBSD as my desktop. I love Steam games too much so started using Void linux. Everything works perfectly except for Fallout 3 in wine - crashes immediately. I'll figure it out eventually, not a deal breaker. Wanted a non-systemd distro and it is perfect for me.
You said Mac before, that's a NeXT BSD bastard unix OS, no? What am I missing?
Not a clue - it's actually certified as "Unix" but only because Apple paid the OpenGroup to certify it. All I know is it just works, it works extremely well and it isn't any of the shite put out by those idiots in Redmond.
macOS's open source core ("Darwin") is loosely based on FreeBSD 5 if I remember correctly, but it has diverged a lot. Anyway, macOS - starting with "Mac OS X" which was the successor to NeXTSTEP with a thin Mac OS emulation layer - uses a hybrid kernel which is more similar to the Hurd than to both FreeBSD's kernel and Linux.
Interesting, so Wind River REAL TIME Linux, has a "bloatkernel", eh? I guess "bloatkernel" must be some phrase with I'm not familiar, some phrase which is a synonym for "really fast".
Did this because all my wifes friends and co-workers use this, She asked. So I complied. Have not used the app yet though.
Code:
Active apt repos in: /etc/apt/sources.list.d/teams.list
1: deb [arch=amd64] https://packages.microsoft.com/repos/ms-teams stable main
No active apt repos in: /etc/apt/sources.list.d/various.list
I can honestly state this came about during the corona virus outbreak. Conspiracy?
There are good reasons why microkernel systems like QNX are much more common in the Real Time world.
Unfortunately, there are almost always trade offs. Years ago I worked with a nice little RTOS known as pSOS. It was so nice it was even chosen to run on each of the processors of a supercomputer. But the less memory something takes, even if it's small because it's written in an assembly language, the less it is likely to be able to do. To do more, other code needed to be added to pSOS. AFAIK, you'll find pSOS isn't very popular today. As a separate issue, offloading what are classically kernel functions into User Space, then talking about a smaller kernel, is just sort of cheating by way of terminology.
Unfortunately, there are almost always trade offs. Years ago I worked with a nice little RTOS known as pSOS. It was so nice it was even chosen to run on each of the processors of a supercomputer. But the less memory something takes, even if it's small because it's written in an assembly language, the less it is likely to be able to do. To do more, other code needed to be added to pSOS. AFAIK, you'll find pSOS isn't very popular today. As a separate issue, offloading what are classically kernel functions into User Space, then talking about a smaller kernel, is just sort of cheating by way of terminology.
Although true, that does not negate the fact of a kernel being "light" if everything else that is needed is in some other place. "Don't worry sir, the back of the truck is not heavily loaded", but fail to tell him that the 20tons of good were loaded toward the front of the truck, which make no diff when on the scales.
To your point, looking at an OS from just the kernel view is often times pointless and/or just not meaningful, need to look at it from the "system" point of view. Input a problem and need an output, the in-between is what matters. I've done this exercise for a CAD system I put together. Using a Xeon cpu is kinda sucky in many ways, but great for CAD when coupled with ECC ram w/ tuned mem cache (TY to MS for out-of-the-box not supporting Xeon cache correctly).
Perhaps I was in too much of a hurry, as I often am. Maybe I should have quoted "There is only a bloatkernel Linux.", so that someone didn't have to go back to see the history of the comments. It was really about the phrase "bloatkernel" that I was commenting. Suppose someone wants to use purple paint. But instead of getting purple paint, they do this:
get red paint
get blue paint
mix red and blue to form purple
complain about having to mix red and blue paint
In that situation I would tend to think that the complaint is rather surprising and inappropriate.
When it comes to the phrase "bloatkernel", AFAIK the word "bloat" is a negative categorization. Yet there are quite a variety of established forms of Linux, even apart from what someone might produce via LFS. I feel that even if someone might consider some of them "bloated", there is such a variety of them, that it would seem hard to consider such a sweeping categorization as valid.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.