Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
simosx
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
12 ms
·
91.
▲
by
simosx
7y ago
By default, a snap package cannot touch your dot directories in your $HOME. That is good for your security. You would need to copy once (or `rsync`) from `~/.mozilla/firefox/` to `~/snap/firefox/current/.m
92.
▲
by
simosx
7y ago
$ snap info firefox ... channels: stable: 67.0.3-1 2019-06-18 (230) 221MB - It is already available to use.
93.
▲
by
simosx
7y ago
Damned if you do, damned if you don't. Regarding the reference to "like mounting the CD ISO" for AppImage. All three of them actually mount one or more filesystems in order to install the package.
94.
▲
by
simosx
7y ago
Snap is not "centralized". It comes with a default Store, and this helps most users that require modern package management. If you want to distribute manually your .snap packages, then you can certainly do so. For example, the lib
95.
▲
by
simosx
7y ago
I said that there is no "default" central store for package in AppImage. Which means that there is a "default" central store for snaps and flatpaks. And if you do not like the "default" central store, you are f
96.
▲
by
simosx
7y ago
Some version of LibreOffice is native to a distribution. Those new formats have benefits, including the ability to automate the processes of updates (mostly thanks to better tooling as they are newer), the ability for confinement, etc.
97.
▲
by
simosx
7y ago
Most likely it is a preload issue. With the apt version, the libraries are already preloaded on your system, because they are shared and in use. With the snap version, the application needs to load up the common core image, then load the s
98.
▲
by
simosx
7y ago
On Intellij, JetBrains are producing themselves snap packages for their whole range of products. It makes it so easy to install on your system, and updates happen automatically. Here is their initial announcement, https://blog.j
99.
▲
by
simosx
7y ago
You will most likely get a malicious AppImage from some website because there is no default central store with such packages. You could argue that there is a freedom with AppImage that you are not bound to a Store. But that would not be cor
100.
▲
by
simosx
7y ago
The "snap for servers" was an issue so long time ago. I do not think it is worth repeating. Both snaps and flatpaks require a core image (a rootfs), and each package sits on top of that rootfs. For snaps, there is the core16 (and
101.
▲
by
simosx
7y ago
For snap packages, you can use the build servers at https://snapcraft.io/build Point to your github repository with the snapcraft.yaml file and it will create the snap package for you. I think the publishing is very straig
102.
▲
by
simosx
8y ago
A post by Christian Brauner (LXC/LXD developer) on how LXC and LXD are affected. In summary, unprivileged containers (as found in LXD) are not affected. https://brauner.github.io/2019/02/12/privileged-co
103.
▲
Runtimes and the Curse of the Privileged Container
(brauner.github.io)
4 points
by
simosx
8y ago
|
0 comments
104.
▲
by
simosx
8y ago
Here is that feature request for the PROXY protocol, https://github.com/lxc/lxd/issues/4786 Was reported on July 14th and committed on July 19th.
105.
▲
by
simosx
8y ago
As a user you should be unaffected by the packaging of software as long as it works. A Linux distribution can repackage LXD in their native packaging format and some distributions are doing it already (Debian, Alpine, Fedora, etc). If you a
106.
▲
by
simosx
8y ago
If you use the command "lxc" to manage your container, then you are using LXD. The command "lxc" communicates with the LXD supervisor over REST for you. If instead you are using commands like "lxc-start", then
107.
▲
by
simosx
8y ago
Currently I think the official LXD packages will be snap packages for all distros, with the exception of the Ubuntu LTS releases. That is, in Ubuntu 16.04 LTS and Ubuntu 18.04 LTS you get LXD as an official deb package. Obviously, this does
108.
▲
by
simosx
8y ago
There were some issues with specific kernel features not being upstreamed timely. Having said that, here is a distribution usage for the snap package of LXD, https://snapcraft.io/lxd (see that the end of the page).
109.
▲
by
simosx
8y ago
I have written some entry-level tutorials shown at https://discuss.linuxcontainers.org/t/the-lxd-tutorials-of-s... I would like as well to see usage examples in the official documentation.
110.
▲
by
simosx
8y ago
LXD is used in Crostini ( https://www.reddit.com/r/Crostini/ ) as a way to be able to run Linux applications in chromebooks. In addition, Samsung is somehow using LXD in their new phones, with "Linux on DeX&quo
111.
▲
by
simosx
8y ago
LXD provides "system containers" in contrast to the "application containers" from Docker. You create a "system container" and it keeps running as a stock Linux distribution (many flavors are supported). It take
112.
▲
by
simosx
8y ago
The first commit for LXD on github is from November 2014: commit 3153b57369b7cf3e96979897c335a5c1d69e7f07 Author: Stéphane Graber Date: Wed Nov 5 10:09:28 2014 -0500 Add licensing and contributing guidelines Signed-off-by:
113.
▲
Screaming Channels: Radio Side-Channels in Mixed-Signal Chips
(github.com)
56 points
by
simosx
8y ago
|
1 comments
114.
▲
by
simosx
8y ago
Being pedantic here. It is in fact versus "Google's current business plan of Android", not Android per se.
115.
▲
by
simosx
8y ago
This Bloomberg article has several shortcomings. 1. "Android and Chrome OS are built on Linux, a widely used open-source programming language." Here they mix up the Linux kernel with the Java programming language. 2. "Moving
116.
▲
by
simosx
8y ago
The X11 protocol has been around several decades. The Wayland protocol has been around several years. There are more tools available for X11 and it's used extensively in all distributions. Even in those that are based on Wayland, those
117.
▲
by
simosx
8y ago
Thanks!
118.
▲
by
simosx
8y ago
Sandboxing (snap or flatpack) is more fragile than running the application in a GUI container. If you do not grant a permission, the application will fail. You will get to know about these issues from bug reports. With a GUI LXD container,
119.
▲
by
simosx
8y ago
There are two steps to set up your LXD installation in order to create GUI containers. If you are using the snap package of LXD, you only need to perform the second step. If you are using the deb package of LXD, you need to perform both ste
120.
▲
by
simosx
8y ago
As a sidenote, Chrome OS uses LXD in a similar way to run Linux GUI applications like the terminal application they showed in Google I/O 2018. Here is an article on how they do it, https://blog.simos.info/a-closer-look-
More ›