rpm-ostree
vscode-remote-release
Our great sponsors
rpm-ostree | vscode-remote-release | |
---|---|---|
47 | 35 | |
813 | 3,477 | |
2.1% | 1.7% | |
9.6 | 3.5 | |
7 days ago | 5 days ago | |
C | ||
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rpm-ostree
-
What do you prefer more and why?
I definitely agree that immutability offers considerable value in regards to improving security. But arguably it's insufficient to pull the win over mutable Fedora due to the losses caused by the inability to install the kernel-hardened package and the lack of UKI (Unified Kernel Image) support.
-
Looking to test out fedora Silverblue. I have only 1 question
Issue: https://github.com/coreos/rpm-ostree/issues/3944
-
What is the difference between Immutable Desktops and non Immutable Desktops?
Oversimplifying might have been the most sensible in this context. However, you might have gone a little bit too far as your description fits only NixOS, Guix and distros that utilize rpm-ostree.
-
Universal Blue is a new paradigm for the Linux desktop and it's brilliant
here's the documentation of ostree (the package manager)
-
Fedora Silverblue 38: rpm-ostree crashes
Now... this was VERY alarming to say the least, so I went online and did indeed find an issue on GitHub.
- Fedora Linux 38 released!
-
The New website is here, with modern UI. And getfedora.org redirect to fedoraproject.org with fresh look.๐
And there are still some issues with layering. Some packages that don't behave or follow standards will modify files in /usr/local, which isn't supported, so you simply won't be able to install them on Silverblue. I think it's the same for /opt as well. (https://github.com/coreos/rpm-ostree/issues/233) This means it fundamentally can't do everything Workstation can, which is unfortunate.
-
Flatcar Container Linux
ublue is based off of fedora and rpm-ostree, which is what "CoreOS" is today.
What happened was old school CoreOS was A/B partition based: https://github.com/coreos/docs/blob/master/os/sdk-disk-parti...
My memory is hazy but here's how I remember it: After Red Hat acquired CoreOS they rebased the entire thing around rpm-ostree, which is the CoreOS people know today: https://coreos.github.io/rpm-ostree/
At the time there was some anxiety in the community as to what would happen, as there was no direct upgrade path from old CoreOS to new CoreOS. Theoretically if we all believed the kool-aid we were drinking it's just a redeploy, no pets!
Kinvolk came along, forked it, and made Flatcar Linux, which kept the A/B partitioning system, and more crucially, let you just change a config file and all your old CoreOS nodes would just move to Flatcar and then you were good to go. So now if you wanted to stay on the system you were comfortable with you could just use Flatcar. If the composability of rpm-ostree attracted you then new CoreOS have you covered. Red Hat deserves a hat tip here because in their documentation/blog they explicitly mentioned Flatcar as an option for people who wanted to stick with what they know, which I thought was cool and how I discovered it!
Later on Microsoft acquired Kinvolk and and then people raised eyebrows. I have not checked in a while but the folks involved continued to do their thing and run it like a good OSS project, hold public meetings, all that stuff.
I use both and they're both high quality.
-
Immutable Linux Distributions for Those Looking to Embrace the Future
Whenever I was looking at using CoreOS, I was somewhat disheartened that automatic reboots weren't built in: https://github.com/coreos/rpm-ostree/issues/2831. Has this changed? I know zincati has maintenance window support, which would also be nice to have.
-
[HELP] AMD REST BUG
Doesn't look like it https://github.com/coreos/rpm-ostree/issues/1091
vscode-remote-release
-
Code tunnel to local machine directly (without Azure)
It would be great, if people interested in this feature/having similar problems would consider pushing the following issue: https://github.com/microsoft/vscode-remote-release/issues/8373
-
xdg-open shim for remote ssh to headless server (VSCode)
The other option may require that you add the Remote X11 extension to VSCode (Unless Microsoft has undone the damage they did to their OpenSSH client in the last few years in which case you could just enable X11 forwarding in your ssh options) if you're trying to execute everything from VSCode, and you would have to have a suitable browser or viewer installed on the remote server along with the xdg-utils package (or whatever contains xdg-open if you're not running Debian).
- Remote VSCode over SSH crashes EC2 instance
-
How to execute a file that sets up the environment that is needed for intelisense to work properly?
Take a look at this: https://github.com/microsoft/vscode-remote-release/issues/6375
-
Host pty got disconnected
If it's "The connection to the terminal's pty host process is unresponsive, the terminals may stop working", apparently it's an old problem: https://github.com/microsoft/vscode-remote-release/issues/7964
- Requesting upvotes for vs code dev container postStartCommand issue
-
A step to step guide to set up Dev Container
VSCode with Remote-Container extension installed.
-
SSH on Raspberry Pi using VS Code
Possibly related github issue?
-
Connect from Visual Studio Code to FreeBSD
This might be it.
-
A way to connect to computers via SSH without VPN
Hello! I came across this Github issue that I think would be helpful for remote workers. It's about the possibility to connect to an existing tunnel by using the terminal of OS instead of VSCode UI. This would allow us to use tunnels as a full SSH replacement in scenarios where SSH itself isn't possible. If you think this would be helpful, please upvote the issue here: https://github.com/microsoft/vscode-remote-release/issues/8238
What are some alternatives?
ostree - Operating system and container binary deployment and upgrades
pylance-release - Documentation and issues for Pylance
openvpn-install - OpenVPN road warrior installer for Ubuntu, Debian, AlmaLinux, Rocky Linux, CentOS and Fedora
patchelf - A small utility to modify the dynamic linker and RPATH of ELF executables
cxx - Safe interop between Rust and C++
god-mode - Minor mode for God-like command entering
tectonic - A modernized, complete, self-contained TeX/LaTeX engine, powered by XeTeX and TeXLive.
pyright - Static Type Checker for Python
distrobox - Use any linux distribution inside your terminal. Enable both backward and forward compatibility with software and freedom to use whatever distribution youโre more comfortable with. Mirror available at: https://gitlab.com/89luca89/distrobox
com.unity.UnityHub
vscodium - binary releases of VS Code without MS branding/telemetry/licensing