OSBoxes has tons of FREE preinstalled Linux VM Images in VMware or Virtual Box format for download

sudo -i
sudo passwd root

How to Reset Root Password On Ubuntu 18.04 / 20.04  LTS

05 : 23

How to Reset Root Password On Ubuntu 18.04 / 20.04 LTS

how to change or set the root password in any linux distribution(ubuntu, linux mint etc)

03 : 28

how to change or set the root password in any linux distribution(ubuntu, linux mint etc)

How to enable root login(GUI) in Ubuntu 20.04 | 2021

06 : 14

How to set a root password on Ubuntu 20.04

01 : 04

How to set a root password on Ubuntu 20.04

How to set root password for MySQL 8 root user in Ubuntu 20.04 LTS (Linux) [2021]

21 : 08


Once you download the image, you simply uncompress and add the VMDK to your existing Linux distro. The login/password for All VMs is identical:

As you can see, OSBoxes.org is a cool site where you find your favorite Linux distro or you can discover many others. All you need is a good internet connection for the downloads.

From the FAQ:

How to install VMware Tools?

  • Once you turn on virtual machine, Go to menu Player
  • Select Install VMware Tools under Manage section.
  • Go to VMware Tools where iso is mounted.
  • Right click on VMware-Tools-xxx.tar.gz file and select Extract To option then select directory and extract this archive.
  • Now open Terminal
  • Go to directory where you extracted tools from Terminal
  • Here you will find out vmware-install.pl file
  • Enter this command to install Vmware Tools sudo ./vmware-install.pl
  • And follow instructions (To install these tools you don’t even need to change any default option unless you need it).

Final words

I downloaded a prepackaged virtual machine (VM) from OSBoxes. This was a VirtualBox VDI image for Peppermint Linux, which seemed to be primarily an Ubuntu offshoot. So perhaps a solution for Peppermint would also be a solution for other Debian-family distributions.

To enter commands in Peppermint Linux, I could use the Terminal icon on the bottom bar, over by the Menu button. I could copy and paste commands to and from the VM with a right-click. Commands here are in italics when they aren’t set off as separate lines.

Right Way: Create ray Account, Delete osboxes Account

sudo adduser ray
sudo usermod -aG sudo ray
getent passwd | grep ray
getent passwd | grep osboxes
sudo deluser --remove-home osboxes
getent passwd | grep osboxes
grep osboxes /etc/group
groups ray
cat /etc/group | grep osboxes
sudo delgroup osboxes

The first one would reportedly list all members of a group, while the second one listed the groups in which ray was a member, and the third one (with or without the part after cat /etc/group) provided two ways of confirming that, actually, the osboxes group had now been removed; therefore I didn’t need the delgroup command.

sudo xed /etc/hostname
sudo xed /etc/hosts

Each of those commands opened a file for editing. The necessary edit, in each, apparently consisted of replacing all occurrences of “osboxes” with whatever I wanted the host name to be. I decided on “peppermint.” After the edit, I used File > Save in each case. That generated various warnings, but apparently these were unimportant. I rebooted and observed that the change seemed permanent.

Wrong Way: Rename osboxes Account to ray

For possible future references, this section describes the approach I took first, before figuring out the solution described above.

usermod -m -d /home/ray -l ray osboxes
usermod: user osboxes is currently used by process 1504
sudo adduser temp1
sudo usermod -aG sudo temp1
sudo usermod -m -d /home/ray -l ray osboxes

The more worrisome part of that StackExchange discussion was in what they said about changing the login name as I had done: “The change will break or potentially break various things in the system, and so is a bad idea.” I believed that. The conclusion seemed to be that I should not have tried to rename osboxes to be ray; I should instead have created a new ray account and deleted osboxes.

As discussed in another post, I was exploring the possibility of converting a Linux virtual machine (VM) to a physical installation (a/k/a V2P). For that effort, instead of installing my own Linux installation from scratch, I decided to experiment using a canned Ubuntu virtual machine (VM). According to MakeUseOf (Phillips, 2021), these were available for download from various sources, notably OSBoxes, VirtualBoxes, Virtual Disk Images, and Sysprobs.

On this occasion, I looked only at OSBoxes. OSBoxes offered Ubuntu 21.04 VMs for both VirtualBox and VMware. MakeUseOf (Phillips, 2021) offered brief instructions, as well as points of comparison between ISO and VDI downloads, along with a link to a more extensive though possibly dated guide to using VirtualBox (MakeUseOf, 2017).

Дополнительно:  Root для jelly bean

After considerable effort, I found that the OSBoxes VM was not useful for the purposes of that other post. The core problem was that it came configured with a half-dozen partitions, two of which were large dynamic partitions that disserved the purpose I was trying to achieve. I have preserved this post nonetheless, for reference by those who have other purposes in mind. But for those who are not sure, I would advise taking a look at the VM’s structure before proceeding too far with it.

Note: this post focuses on VirtualBox. I found that much of it applied in VMware Player as well. Another post specifies some points of difference.

In Windows 10

My first moves were to download a 2.2GB VirtualBox (VDI) image, and to make a backup copy of the download in case of later problems. At this point, I was working on a Windows 10 desktop computer. Later, as discussed below, I returned to this post and walked through a similar process on an Ubuntu 21.04 laptop.

In Windows, in VirtualBox, I varied somewhat from the OSBoxes instructions. The reason was for storage purposes: I liked to have all files related to a VM located in the same folder, and VirtualBox did not seem to find this natural. (My storage solution: sometimes for backup, and also when I stopped using a VM but wanted to keep it around for possible future use, I zipped all of its files into a single archive. As indicated below, these VMs were highly compressible.)

Instead of creating the desired VM folder myself, and getting into the difficulties just mentioned, the easier approach was to go into VirtualBox and click New. At the bottom of the resulting window, I clicked Expert Mode. (If the button said Guided Mode, that meant I was already in Expert Mode: the two buttons toggled back and forth.)

In Expert Mode, I entered Name: OSBoxes Ubuntu 21.04, Machine Folder: W:. That, by itself, was enough to tell VirtualBox to create a folder with the specified name.

VirtualBox defaulted to Linux, Ubuntu (64-bit). Possibly it remembered that from some prior use. I selected “Do not add a virtual hard disk” > Create. That put me back in the main window, with my newly created VM selected. I clicked Settings > Storage > Storage Devices. I saw that Controller: IDE had an Empty optical drive assigned, but Controller: SATA had nothing.

I clicked Controller: SATA > click the hard disk drive (HDD) icon (not the optical disc icon) > Add. It opened a window into W:\OSBoxes Ubuntu 21.04. As expected, there was nothing there. With the aid of a separate File Explorer window, I put my downloaded OSBoxes .vdi into that folder. Now I could select it > Open > Choose > OK > Start. And with those steps, the newly created VM worked: it gave me an Ubuntu login screen.

Now that I had a working VM, I closed it. (VM menu > File > Close > Power off the machine > OK.) Note: if I clicked inside the VM, it would seize control of the mouse and keyboard. In that case, the hotkey for regaining control was simply to hit the right Ctrl key. There was a reminder of that fact in the status bar at the bottom of the VM window.

Next, I could install the VirtualBox Extensions that I had downloaded along with VirtualBox. To do this, in the main VirtualBox Manager window, I went into menu > File > Preferences > Extensions tab > click the blue plus ( + ) icon at the right side > navigate to the downloaded Extensions file > select the Extension Pack > Open > Install > scroll through VirtualBox License > I Agree. That produced an indication that the Extension Pack installed successfully.

Now, back in the main VirtualBox Manager window, with this VM selected, I was ready to observe some of the OSBoxes instructions. Specifically, I went into Settings and made these changes:

  • General tab: Advanced tab: enable Shared Clipboard and Drag ‘n’ Drop: bidirectional. Note that this might not be advisable on a security-oriented system.
  • System tab: Motherboard tab: Base Memory = 4096 MB (on a system with 24GB RAM). Processor tab: assign up to half the number of CPUs shown. (See discussion of hyperthreading.) It appeared that I could always select PAE/NX. I wasn’t sure whether that was true of the option to Enable Nested VT-x/AMD-V.
  • Display tab: Screen tab: I was unsure; I set it at half the available total. I also selected Enabled 3D Acceleration.
  • Network tab: Adapter 1 tab: Enable Network Adapter was checked; I changed Attached To from NAT to Bridged Adapter.
  • USB tab: Option not available until Extension Pack (above) was installed: choose USB 3.0. Then OK.

Back in the main VirtualBox Manager window, with this VM selected, I clicked Start. Before logging into the Ubuntu VM, the OSBoxes instructions told me to go to VM menu > Devices > Insert Guest Additions CD Image. (Unlike Ubuntu, apparently some OSs did not provide that as an option. In that case, the instructions suggested an alternate procedure.) To verify that that was successful, I went to VM menu > Machine > Settings > Storage. There, I saw that the formerly empty virtual disc under Controller: IDE was now replaced by VBoxGuestAdditions.iso.

Дополнительно:  Whea uncorrectable error в Windows 10: решение проблемы на примере

With that finished, I restarted the VM. (Restart and other power options were available in the upper right corner of the Ubuntu screen.) That enabled Guest Additions to adjust resolution so that the VM’s window was the right size for its contents. After this, Guest Additions would appear as a disc icon on the Ubuntu VM’s desktop.

sudo gedit /etc/hostname
sudo gedit /etc/hosts
  • Note that there might be only one line in these files, bearing the name to be changed.
  • After each, Save > close. Then reboot and check the Terminal prompt. Now it said “ray@UbuntuVM.”
  • sudo apt-get update && sudo apt-get upgrade

I confirmed the changes proposed by that last command. Those changes took some time, with seeming pauses as it installed larger packages.

Depending on your plans, that last command might not be ideal. It may have doubled the size of this installation. It would thus increase the time required for each experimental conversion to a physical machine, which was my primary purpose in going through these steps. On the other hand, it would give me a more up-to-date VM, for actual usage.

The upgrade command produced an indication that four packages were “not upgraded” because they were “kept back.” An Ask Ubuntu answer suggested various responses. I tried the first recommended solution: sudo apt-get –with-new-pkgs upgrade. That informed me that another 499MB would be required. I okayed it, reasoning at this point that at least I was confirming that the VM was in good condition, fully upgradeable and not having any of the problems that these commands might have identified.

That last command finished without any further problem indications. I rebooted the VM and re-ran sudo apt-get update && sudo apt-get upgrade just to be sure. Finally, I shut down the VM and used a file compression tool (in Windows, my preferred tool was WinRAR) to create a zipped backup of the folder containing this VM’s files. The original zipped OSBoxes download was 2.2 GB; unzipped, it was about 7.5GB; installed and upgraded as just described, it was 11.4GB; and in a compressed .rar backup file, it shrank to only 4.0GB.

As mentioned above, I returned to this post at a later date, this time seeking to set up and configure the VM in Ubuntu 21.04. VirtualBox was much the same in both operating systems, but there were some important differences. This section describes my Ubuntu setup process, but in more cursory fashion. The preceding section provides a more detailed elaboration of some steps mentioned here.

I began with the Ubuntu 21.04 VM that I had downloaded from OSBoxes and had already modified to some extent as described above. Now I copied that over from Windows to an ext4 folder on the laptop. Then, in the Ubuntu version of VirtualBox, I went into VirtualBox Manager > Add > navigate to the .vbox file > Open.

Next, I went into VirtualBox Manager > Settings. I had already changed Settings as described above. This had some negative consequences in the context of my laptop and a Linux host. For one thing, at the bottom of the Settings window, I saw, “Invalid settings detected.” To fix that, I went into Settings > System > Processor tab > reduce the number of CPUs (because the laptop’s CPU had fewer cores and/or because the Linux version of VirtualBox counted cores differently). While I was in Settings, I also saw that Storage > Controller: IDE had an error indicator next to VBoxGuestAdditions.iso. I right-clicked on that > Remove attachment. That seemed to take care of errors in Settings. Next, I went to VirtualBox Manager > menu > File > Virtual Media Manager > Optical Disks tab. There was an error for VBoxGuestAdditions.iso there too, so I removed it.

From the VirtualBox download page, I downloaded the VirtualBox Extension Pack. Clicking on the download link opened a dialog that defaulted to the option of opening with VirtualBox. I took that option. The dialog asked whether I wanted to upgrade from the existing version. I did. I scrolled down through the Virtual License dialog > I Agree. The result: an indication that it was installed successfully. Back in VirtualBox Manager, with this VM selected, I clicked Start. It aborted. Troubleshooting efforts failed.

Possibly the problem was the version mismatch discussed below, but I was not aware of that possibility at this point. Instead, I decided to start over. After a struggle to figure out how to uninstall VirtualBox, I finally arrived at this solution:

sudo apt-get purge virtualbox-\*
sudo rm -rf ~/.config/VirtualBox
sudo apt-get autoremove
sudo apt-get install virtualbox

Once that was done, I went into the Ubuntu menu > System Tools > VirtualBox and, finally, blessedly, it did not start up with an existing memory of the failed starts of this VM. But the VM still failed to start.

Дополнительно:  Восстановление aoddriver2 sys Ошибка синего экрана

Therefore, I went all the way back to the VM in the virgin form that I had downloaded from OSBoxes. I repeated the steps described above, this time doing everything in the Ubuntu host. Folder creation for the new VM worked the same as in the Windows setting. To get the VM to start, I found it was helpful to go into Settings > USB > set it to 1.1. Once it started with that setting, I could install the Guest Additions.

But it still would not boot with any setting above USB 1.1. Eventually I found the problem: I had a mismatch. VirtualBox Manager > menu > Help > About VirtualBox said that I was running VirtualBox 6.1.18, whereas VirtualBox Manager > menu > File > Preferences > Extensions said that I had Extension Pack 6.1.24 installed. To get the right Extension Pack, I had to use the Old Builds page. Apparently the apt-get method of installing (as distinct from downloading from the downloads webpage) did not grab the latest version. Once I removed the 6.1.24 Extension Pack and installed the 6.1.18 Extension Pack from the Old Builds page, it booted normally with USB 3.0 enabled. (Probably the better approach at this point would have been, not to drag the Extension Pack backward in time, but instead to download and install the update to VirtualBox 6.1.24.)


Q: What is Osboxes Org Password?
A: Osboxes Org Password is a unique code that provides access to the Osboxes org website. It allows you to access files and other information that is stored on the website. It is important to keep your password secure to make sure your information is kept safe and cannot be accessed by anyone else.

Learn How to Reset Osboxes. org Passwords

If you want to change your Osboxes.org password but don’t know how to do it, we’ve got you covered! Resetting your password is easy and can be done quickly.

  • Go to www.osboxes.org and log in with your existing username and password
  • Once logged in, select the Account tab and choose the submenu labeled “Change Password”
  • Now enter your new password into the fields labeled “Old Password” and “New Password”
  • Click the “Confirm” button to save the changes

Your password has now been successfully reset. It’s recommended to use a unique and secure password to protect your account and keep your information safe. Be sure to include letters, numbers and symbols when you create your new Osboxes.org password.

Get Back into Your Osboxes. org Account in Minutes

  • Go to the official Osboxes.org website and locate the “Login” button at the top right of the website
  • Once you click on the “Login” button, a new page will open up. Here you will need to enter your registered username and password
  • If you’ve forgotten your username or password, you can click on “Forgot Password” and get your account information back in minutes
  • Check the “Remember Me” option box to ensure you stay logged in
  • Finally, click on the “Log In” button and you’re done!

Don’t Let Forgotten Passwords stop you! Unlock Osboxes. org Now!

Are you trying to access the content at Osboxes.org but you can’t seem to remember the password? Don’t worry, a forgotten password shouldn’t stop you from moving forward! Here are a few tips to unlock Osboxes.org:

  • Check your emails – Many accounts contain a password reset link sent to the email address associated with the account. Be sure to check your spam folder for any hidden emails that may have been missed.
  • Contact the site – Contact the website’s support team to get assistance with resetting the password.
  • Utilize a password manager – Password managers are a great tool to help keep track of all of your online accounts and passwords.

Never settle for a forgotten password again. With the help of these tips, you’ll be able to access Osboxes.org and all the content it has to offer!

The Quick and Easy Way to Reset Forgotten Passwords

In the modern world, there are countless opportunities to have our passwords forgotten. With passwords playing a major role in many aspects of our lives, having a forgotten password can be a major setback. Thankfully, resetting forgotten passwords is becoming increasingly streamlined and easy to do.

  • Go to the source of your forgotten password
  • Locate the “forgot password” link
  • Enter the required information
  • Follow the instructions


If you’re looking for a simple, fast, secure and free solution on how to reset your Osboxes Org Password, try using LogMeOnce! It is a great choice that can help you establish secure, unique passwords for each and every one of your online accounts, ensuring optimal password management and digital security. LogMeOnce is an excellent option to consider when managing your Osboxes Org Password. With a large range of secure and easy-to-use features, it is easy to see why LogMeOnce is the ideal choice for password management related to Osboxes Org.

Оцените статью
Master Hi-technology
Добавить комментарий