![]() When was this the case last time? I can't remember a case of dependency hell. Installing applications on Linux distros, even through supported repositories, can be a nightmare of dependencies, outdated libraries, fiddling with startup scripts, systemd, and permissions. Anyhow, feel free to disagree with that reading. I meant to say this in my first paragraph. You completely ignore the fact that it's a perfect self-contained application distribution channel, packaging not only your application but all of it's needed libraries along with version that are guaranteed to work with it. So if you're taking your time to setup everything new, you might also look into alternatives if you have the time. That being said I never had a problem with Sab. Personally, I switched from SabNZB to NZBGet because NZBGet is a lighter solution that does exactly what I want and it is in my distributor's repositories while Sab isn't. That will most likely be Ubuntu with a PPA, though I can't say how to do it exactly since I use something else. Which brings us to the last question: for a beginner, I'd recommend a Linux distribution that provides all the packages you need either in the distributor's repositories or via a 3rd party repository. That way, your packages will be updated using your package manager, as long as they're in the distributor's repository. I'd recommend setting up a classic Linux environment. The strength of containerization is consistency when you depend on given versions of complex software, like databases and big libraries that need to be carefully tuned to work with each other. I consider Docker to be an overkill solution for something as simple as this. ![]() I totally see how, if you were trying to do this on a budget/single box, and you did not know how to configure OS / config files / etc. So I guess my thought process is based on that "starting point". At home, I already have a pretty solid VM Host setup (3 host machines) and plenty of cpu/ram/disk/ssd resources to allocate, and I'm very familiar with VM tech (not so familiar with Docker). ![]() I've been using USENET for "linux ISOs" since the mid 1990's (anyone else remember manually decoding. This technique also works with the "more advanced" VM Technology as well.Īlso - I guess I should be clear - I'm a tech guy and have been for 2 decades. If you are not grossly oversubscribed on RAM the hit should be pretty minimal. ![]() It also helps mitigate some of the "heaviness" of VM tech, though you may sacrifice a slight bit of VM Guest performance doing so. Now, if you are talking about a different or consumer-level VM Host technology (think: KVM or Oracle VirtualBox or something else not mentioned), then I believe your premise stands that VM's are "heavier" than docker containers, memory-wise.Īlso - even with those "less advanced" VM Technology - you can always over-allocate your memory which will cause your VMs to balloon/share memory. So if you use "dynamic memory" it will/should have similar RAM usage to a docker container (at least from the hypervisor level looking down - multiple guest OS will still think they have all those "common" libraries in RAM, but truly they are only stored once at the hypervisor layer). I know for a fact that both VMWare and Hyper-V do memory de-duplication between VM guests - so OS-level stuff (like system DLLs, services, etc) is only stored in memory once. This includes hacking, using a loophole, or other methods not publicly advertised by the usenet provider.Īlthough my understanding is that your perceived "overhead" is not technically correct for all VM technology. No promoting of 'backdoor' access into usenet providers' networks. We do not allow attempts to request/offer/buy/sell/trade/share invites or accounts. We will even add flair to your username after verification. Message the mods and let them know who you are. However we want to verify the identity of anyone posting on behalf of a company/project. No discussion of specific media content names, titles, etc. We only have a few, but they are important. Please read over the rules before contributing. We are a thriving community dedicated to helping users old and new understand and use usenet.
0 Comments
Leave a Reply. |