Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 10 submissions in the queue.

Snap Removed from Mint

posted by Fnord666 on Thursday July 09 2020, @06:27PM   Printer-friendly
from the working-behind-your-back dept.

hendrikboom writes:

Linux reviews notes that

The popular Linux Mint operating system has decided to purge the snap package manager from its repositories and forbid installation of it. The motivation for this drastic move is that the upstream Ubuntu Linux distribution Linux Mint is based on will stealthily install snapd and use that to install Chromium from the Canonical-controlled SnapCraft instead of installing a regular Chromium package like most users expect.

The Linux Mint blog has this to say about Ubuntu's use of snap to use their chromium package to subvert apt:

You've as much empowerment with this as if you were using proprietary software, i.e. none. This is in effect similar to a commercial proprietary solution, but with two major differences: It runs as root, and it installs itself without asking you.

Is Ubuntu turning evil?

Original Submission

 
This discussion has been archived. No new comments can be posted.
Snap Removed from Mint | Log In/Create an Account | Top | 96 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 4, Interesting) by RamiK on Friday July 10 2020, @02:18AM

    by RamiK (1813) on Friday July 10 2020, @02:18AM (#1018929)

    Actually in Plan 9 applications did in fact expose much of their interfaces via the 9p protocol for the explicit purpose of being mounted in the filesystem for both IPC, network transparency and user interactivity. e.g. Your text editor would have its file menu and window content (buffers/tabs) as files nested in directories and (union) mounted in the namespace so you could write scripts using whatever you want to program new commands (buttons) so there was no need for macro or extension languages. Another example was how this was applied to the windowing system so you could dispense with header files and specialized protocols and just walk the filesystem and modify a few files to manipulate window positioning and the likes...

    So, while linux containers and namespaces are bastardizing plan9, the way plan9port was made, how many Bell Labs veterans use OSX and how Go compiles statically are clear indication the Labs veterans aren't too shy from deviating from Unix, POSIX or Plan9 when they want to get something done.

    Bib:
    https://web.archive.org/web/20140906153815/http://www.cs.bell-labs.com/sys/doc/names.html [archive.org]

    --
    compiling...
    Starting Score:    1  point
    Moderation   +2  
       Interesting=2, Total=2
    Extra 'Interesting' Modifier   0  
    Karma-Bonus Modifier   +1  
    Total Score:   4