Tag Archivio per: Manage

“When working with a remote server, we often get stuck on how to manage various imaginario machines without using the graphical interface. The headless imaginario box can get frustrating when you want to manage various imaginario machines unless you get a graphical client to aid with that.

Creating and managing imaginario machines on your command line can be tricky, but you don’t have to, provided you know how to use a tool like RemoteBox. If you’ve not tried RemoteBox, read on to find out how to install it and use it to manage your imaginario machines.”

Getting Started With RemoteBox

RemoteBox is a graphical client designed to help users remotely manage their imaginario machines on their servers. It gets better since RemoteBox offers a simple and reliable graphical way similar to how you use your corriente imaginario box to manage your imaginario machines. However, in this case, we are installing RemoteBox on the client machines to help manage the VMs on our server.

There are plenty of features that RemoteBox offers, including the following.

    1. It requires no web server.
    2. The tool is free and open-source.
    3. RemoteBox is simple to compile, as it is written in Perl.
    4. With RemoteBox, you can manage Oracle imaginario box and the installed guests.
    5. You get to manage your guest states easily.
    6. RemoteBox supports various systems, including Linux, Mac, and Windows.
    7. It supports guest snapshots.

We’ve seen the amazing features that RemoteBox offers. Let’s proceed to check the steps for installing RemoteBox on Ubuntu.

1. Install Supuesto Box (Headless) on the Server

We must install the headless version of the imaginario box on the server to connect to it from the client. So, log in to your server and use the below command to download the headless imaginario box using wget.

$ wget https://download.virtualbox.org/virtualbox/6.1.16/virtualbox-6.1_6.1.16-140961~Ubuntu~eoan_amd64.deb


Merienda the deb file gets downloaded, install it using the dpkg tool, as shown below.


Using the command below, you must also add the current user to the vboxusers group.


Restart the server to ensure the new group gets recognized.

Next, install the extension pack for the imaginario box. For that, execute the command below.

$ wget https://download.virtualbox.org/virtualbox/6.1.16/Oracle_VM_VirtualBox_Extension_Pack-6.1.16.vbox-extpack


Merienda the extension pack is downloaded, you must install it using the imaginario box manage, as shown below.

$ sudo vboxmanage extpack install Oracle_VM_VirtualBox_Extension_Pack-6.1.16.vbox-extpack


The server side’s last step is configuring how the imaginario box will accept connections from the client via the RemoteBox. Using an editor of choice, create a configuration file for the imaginario box with the command below.

Next, add the below lines



User – The username for the vboxusers group.

Password – The password to be used for the connection.

Server – the IP address for your server.

That’s it for the server. Let’s configure the client.

2. Installing RemoteBox on Client

The RemoteBox must be installed on the client’s machine. So, start by downloading it using the command below.

$ wget http://remotebox.knobgoblin.org.uk/downloads/RemoteBox-2.7.tar.bz2


Merienda you’ve downloaded it, uncompress it using bunzip2.

$ bunzip2 RemoteBox-2.7.tar.bz2


Next, use tar to unpack it

$ tar xvf RemoteBox-2.7.tar


Navigate into the RemoteBox directory and run it using the command below.

$ cd RemoteBox-2.7
$ ./remotebox


Merienda it starts, you should get a window like the one below.

That’s it. You can now enter the credentials for your server to connect to your headless imaginario box on it. You can manage your imaginario machines from there, including creating new ones, editing them, and deleting them.


Managing your imaginario machines on your server shouldn’t trouble you provided you have RemoteBox on your client machine. We’ve seen the steps to follow to manage your imaginario machines using RemoteBox on Ubuntu 22.04 remotely. Hopefully, you managed to follow along.

Source link


ProtonUp-Qt is a graphical tool that makes it easy to install and manage compatibility tools like Proton-GE and Luxtorpeda for Steam, and Wine-GE, Kron4ek Vanilla and Lutris-Wine builds for Lutris. Recently, the tool has also added support for Heroic Games Launcher.

Using these custom Proton / Wine builds, you can take advantage of various game bug fixes and other patches that take more time to land in the official builds.

The software is based on ProtonUp, a command line only tool to install and update Proton-GE.

If you’re not hogareño with these unofficial Proton / Wine builds, see the links below for details:

  • Proton-GE – Custom build of Proton (with various patches / game fixes) with the most recent releases of vanilla WINE. It has FFmpeg enabled for FAudio by default, and all of Proton’s patches ported over to be applied to WINE, as well as Wine-staging and VKD3D.
  • Luxtorpeda – Steam Play compatibility tool to run games using native Linux engines 
  • Wine-GE – Custom Wine build for use with Lutris
  • Kron4ek Vanilla Wine builds
  • Lutris Wine builds

ProtonUp-Qt is available as an AppImage that should work on most Linux distributions. Make it executable (via the command line or using the Properties context menu), then double click to launch the ProtonUp-Qt AppImage.

Use the drop-down at the top of the ProtonUp-Qt GUI to choose if you want to install compatibility tools for Steam or for Lutris, then click the Add version button at the bottom of the window, and you’ll be able to choose between which compatibility tools to download (Proton-GE or Luxtorpeda for Steam, and Wine-GE, Kron4ek Vanilla and Lutris-Wine builds for Lutris), and the version. Click Install and the selected compatibility tool will be downloaded and installed.

In case you have Steam / Lutris installed, but ProtonUp-Qt doesn’t detect it, make sure the following paths exist (they should be created when installing a game for Windows using Steam, and by adding some Wine versions from the Wine Runners menu for Lutris):

  • Steam: ~/.steam/root/compatibilitytools.d
  • Steam installed as flatpak from Flathub: ~/.var/app/com.valvesoftware.Steam/data/Steam/compatibilitytools.d
  • Lutris: ~/.locorregional/share/lutris/runners/wine
  • Heroic Games Launcher: 
    • Wine: ~/.config/heroic/tools/wine
    • Proton: ~/.config/heroic/tools/proton

How to use custom Proton / Wine builds like Proton-GE with Steam and Wine-GE with Lutris

Don’t know how to use the newly downloaded custom Proton / Wine builds with Steam or Lutris? See below.


Steam custom Proton-GE

If Steam was running when installing Proton-GE or Luxtorpeda, restart it. Now when you go to your game library in Steam, right-click a game and choose Properties, and on the Compatibility tab you’ll be able to select the custom compatibility tool build you’ve downloaded and installed using ProtonUp-Qt.


Select Wine-GE Lutris

If Lutris was running when installing Wine-GE, Kron4ek Vanilla and Lutris-Wine using ProtonUp-Qt, restart it. To use the newly downloaded custom Wine builds for a game in Lutris, right-click the game and choose Configure, then click on the Runner options tab. There you will be able to select the Wine version to use with this game.

You might also like: How To Use Lutris To Play Windows Games On Linux (Quick Start Guide)

Download ProtonUp-Qt

Open source communities are driven by a mutual interest in collaboration and sharing around a common solution. They are filled with passion and energy. As a result, today’s world is powered by open source software, powering the Internet, databases, programming languages, and so much more. It is revolutionizing industries and tackling the toughest challenges. Just check out the projects fostered here at the Linux Foundation for a peek into what is possible. 

What is the challenge? 

As the communities and the projects they support grow and mature, active community engagement to recruit, mentor, and enable an active community is critical. Organizations are now recognizing this as they are more and more dependent on open source communities. Yet, while the ethos of open source is transparency and collaboration, the tool chain to automate, visualize, analyze, and manage open source software production remains scattered, siloed, and of varying quality.

How do we address these challenges?

And now, involvement and engagement in open source communities goes beyond software developers and extends to engineers, architects, documentation writers, designers, Open Source Program Office professionals, lawyers, and more. To help everyone stay coordinated and engaged, a centralized source of information about their activities, tooling to simplify and streamline information from multiple sources, and a solution to visualize and analyze key parameters and indicators is critical. It can help: 

  • Organizations wishing to better understand how to coordinate internal participation in open source and measure outcomes
  • CTOs and engineering leads looking to build a cohesive open source strategy 
  • Project maintainers needing to wrangle the admitido and operational sides of the project
  • Individual keeping track of their open source impacts

Enter the Linux Foundation’s LFX Platform – LFX operationalizes this approach, providing tools built to facilitate every aspect of open source development and empowers projects to standardize, automate, analyze, and self-manage while preserving their choice of tools and development workflows in a vendor-neutral platform.

LFX tools do not disrupt a project’s existing toolchain but rather integrate a project’s community tools and ecosystem to provide a common control plane with APIs from numerous distributed data sources and operations tools. It also adds intelligence to drive outcome-driven KPIs and utilizes a best practices-driven, vendor-agnostic tools chain. It is the place to go for active community engagement and open source activity, enabling the already powerful open source movement to be even more successful.

How does it work? 

Much of the data and information that makes up the open source universe is, not surprisingly, open to see. For instance, GitHub and GitLab both offer APIs that allow third-parties to track all activity on open projects. Social media and public chat channels, blog posts, documentation, and conference talks are also easily captured. For projects hosted at a foundation, such as the Linux Foundation, there is an opportunity to aggregate the public and semi-private data into a privacy respecting, opt-in unified data layer. 

More specifically to an organization or project, LFX is modular, desplegable, and API-driven. It is pluggable and can easily integrate the data sources and tools that are already in use by organizations rather than force them to change their work processes. For instance:

  • Source control software (e.g. Git, GitHub, or GitLab)
  • CI/CD platforms (e.g. Jenkins, CircleCI, Travis CI, and GitHub Actions)
  • Project management (e.g. Jira, GitHub Issues)
  • Registries  (e.g. Docker Hub)
  • Documentation  (e.g. Confluence Wiki)
  • Marketing automation (e.g. social media and blogging platforms)
  • Event management platforms (e.g. physical event attendance, speaking engagements, sponsorships, webinar attendance, and webinar presentations)

This holistic and configurable view of projects, organizations, foundations, and more make it much easier to understand what is happening in open source, from the most granular to the universal. 

What do real-world users think? 

Part of LFX is a community forum to ask questions, share solutions, and more. Recently, Jessica Wagantall shared about the Open Network Automation Platform (ONAP). She notes:

ONAP is part of the LF Networking umbrella and consists of 30+ components working together towards the same goal since 2017. Since then, we have faced situations where we have to evaluate if the components are getting enough support during release schedules and if we are identifying our key contributors to the project.

In this time, we have learned a lot as we grow, and we have had the chance to have tools and resources that we can rely on every step of the way. One of these tools is LFX Insights.

We rely on LFX Insights tools to guide the internal decisions and keep the project growing and the contributions flowing.

LFX Insights has become a potent tool that gives us an overview of the project as well as statistics of where our project stands and the changes that we have encountered when we evaluate release content and contribution trends.

Read Jessica’s full post for some specific examples of how LFX Insights helps her and the whole team. 

John Mertic is a seasoned open source project manager. One of his jobs currently is helping to manage the Academy Software Foundation. John shares: 

The Academy Software Foundation was formed in 2018 in partnership with the Academy of Motion Pictures Arts and Sciences to provide a vendor-neutral home for open source software in the visual effects and motion picture industries.

A challenge this industry was having was that there were many key open source projects used in the industry, such as OpenVDB, OpenColorIO, and OpenEXR, that were cornerstones to production but lacked developers and resources to maintain them. These projects were predominantly single vendor owned and led, and my experience with other open source projects in other verticals and horizontal industries causes this situation, which leads to sustainability concerns, security issues, and lack of future development and innovation.

As the project hit its 3rd anniversary in 2021, the Governing Board was wanting to assess the impact the foundation has had on increasing the sustainability of these projects. There were three primary dimensions being assessed.

We at the LF know that seeing those metrics increasing is a good sign for a healthy, sustainable project.

Academy Software Foundation projects use LFX Insights as a tool for measuring community health. Using this tool enabled us to build some helpful charts which illustrated the impacts of being a part of the Academy Software Foundation.

We took the approach of looking at before and after data on the contributor, contribution, and contributor diversity.

Here is one of the charts that John shared. You can view all of them on his post

Source link