- Go into settings of the VirtualBox console manager and go into Storage settings. Copy the position path of your current controller. The file can be *.vdi or *.vmdk or others.
- Shut down VirtualBox again.
- Make a copy of the VDI file – just in case (“C:\Users\Administrator\VirtualBox VMs\vm\Windows10TeamSystem-disk1.vdi” -> “C:\Users\Administrator\VirtualBox VMs\vm\Windows10TeamSystem-disk1Copy.vdi“)
- Go into the Windows command prompt (Start->type “cmd” into the box)
- cd C:\Users\Administrator\VirtualBox VMs\vm\ the location of the VDI file that you wish to resize.
- At the Windows command prompt, type:
D:\>"C:\Program Files\Oracle\VirtualBox\VBoxmanage" modifyhd Windows10TeamSystem-disk1.vdi --resize 358400
this will re-size the drive to 350 GB(1024 * 350 = 358400). Pick a value that suits you. Note, your vdi file will not change in size at this point. The output should look like:
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
-
Enlarge the Virtual Machine’s Partition
You now have a larger virtual hard disk. However, the operating system’s partition on your virtual hard disk is the same size, so you won’t be able to access any of this space yet.
- You’ll now need to extend the guest operating system’s partition as if you were enlarging a partition on a real hard disk in a physical computer. You can’t enlarge the partition while the guest operating system is running, just as you can’t enlarge your C:\ partition while Windows is running on your computer.You can use a GParted live CD to resize your virtual machine’s partition – simply boot the GParted ISO image in your virtual machine and you’ll be taken to the GParted partition editor in a live Linux environment. GParted will be able to enlarge the partition on the virtual hard disk.First, download the GParted live CD’s ISO file from here.Load the ISO file into your virtual machine by going into the virtual machine’s settings window, selecting your virtual CD drive, and browsing to the ISO file on your computer.
Boot (or restart) your virtual machine after inserting the ISO image and the virtual machine will boot from the ISO image. GParted’s live CD will ask you several questions while booting – you can press Enter to skip them for the default options.
Once GParted is booted, right-click the partition you want to enlarge and select Resize/Move.
Specify a new size for the partition – for example, drag the slider all the way to the right to use all the available space for the partition. Click the Resize/Move button after you’ve specified the space you want to use.
Finally, click the Apply button to apply your changes and enlarge the partition.
After the resize operation completes, restart your virtual machine and remove the GParted ISO file. Windows will check the file system in your virtual machine to ensure it’s working properly — don’t interrupt this check.
The virtual machine’s partition will now take up the entire virtual hard disk, so you’ll have access to the additional space.
Create the Google site verification record
https://search.google.com/search-console
Using the Bootstrap 4 Grid | BOOTSTRAP 4 TUTORIAL
Very well bootstrap tutorial
<!DOCTYPE html>
<html lang=”en”>
<head>
<meta charset=”UTF-8″>
<meta name=”viewport” content=”width=device-width, initial-scale=1.0″>
<meta http-equiv=”X-UA-Compatible” content=”ie=edge”>
<title>Bootstrap 4 Introduction</title>
<link rel=”stylesheet” href=”https://maxcdn.bootstrapcdn.com/bootstrap/4.0.0/css/bootstrap.min.css” integrity=”sha384-Gn5384xqQ1aoWXA+058RXPxPg6fy4IWvTNh0E263XmFcJlSAwiGgFAW/dAiS6JXm”
crossorigin=”anonymous”>
<style>
body {
margin: 30px;
}
.my-container {
border: 1px solid green;
}
.my-row {
border: 3px solid red;
height: 300px;
}
.my-col {
border: 3px dotted blue;
}
</style>
</head>
<body>
<div class=”container my-container”>
<div class=”row my-row”>
<div class=”col-md-4 col-sm-6 my-col”>
Row 1 Col 1
</div>
<div class=”col-md-8 col-sm-6 my-col”>
Row 1 Col 2
</div>
</div>
<div class=”row justify-content-between align-items-stretch my-row”>
<div class=”col-4 my-col order-md-12″>
Row 2 Col 1
</div>
<div class=”col-4 offset-md-2 my-col align-self-start order-md-2″>
Row 2 Col 2
</div>
</div>
</div>
</body>
</html>
How to Use Virtual Environments
Useful command for python system environment or custom environment.
When any environment is not activated you are using the system environment.
pip list
pip3 list
create new environment :
python3 -m venv env_name
create a directory env_name
activate the env_name :
source env_name/bin/activate
show which python :
which python
deactivate environment :
deactivate
create an environment with the same packages of the system environment :
python3 -m venv env_name –system-site-packages
how to show the only packages installed in the env_name environment
pip list –local
ES:
python3.6 -m venv pgAdminEnv
source pgAdminEnv/bin/activate
Yum clean package and fix duplicate packages
From time to time, the yum package manager may encounter issues with duplicate packages that are erroneously installed on a system. This manifests in a yum update going awry, telling us something along the lines of this:
1
2
3
4
5
6
7
8
9
10
11
12
|
yum update
...
—> Finished Dependency Resolution
Error: Package: ntp–4.2.6p5–22.el7.centos.2.x86_64 (@updates)
Requires: ntpdate = 4.2.6p5–22.el7.centos.2
Removing: ntpdate–4.2.6p5–22.el7.centos.2.x86_64 (@updates)
ntpdate = 4.2.6p5–22.el7.centos.2
Updated By: ntpdate–4.2.6p5–25.el7.centos.x86_64 (base)
ntpdate = 4.2.6p5–25.el7.centos
You could try using —skip–broken to work around the problem
** Found 41 pre–existing rpmdb problem(s), ‘yum check’ output follows:
// huge scary list of packages follows
|
You may at times install all other packages via yum update –skip-broken, but it will still leave some trouble on the system. Best to take care of it.
Here’s how I’ve managed to do it on many occasions:
Installing yum-utils
The utility that will help us fix these issues is called package-cleanup, and it’s part of the yum-utils package. Let’s install that first before we continue:
1
|
yum install yum–utils
|
Next, let’s see what’s wrong with our system. package-cleanup –dupes will show us duplicate packages on the system:
1
2
3
4
5
6
7
8
9
10
|
package–cleanup —dupes
Loaded plugins: fastestmirror
parted–3.1–23.el7.x86_64
parted–3.1–28.el7.x86_64
tar–1.26–31.el7.x86_64
tar–1.26–29.el7.x86_64
lvm2–2.02.130–5.el7_2.5.x86_64
lvm2–2.02.166–1.el7_3.1.x86_64
...
|
The list could go on. Here we see that several packages are seemingly installed more than once. The –cleandupes parameter will take care of this, erasing such superfluous packages:
1
|
package–cleanup —cleandupes
|
The process will look very similar to a yum update, with yum verifying and erasing the duplicates. It doesn’t hurt to make a note of the erased packages and check if the latest version is still installed. Should this not be the case, you can bring those packages back with “yum reinstall packagename”.
Finishing Up
At this point, let’s try to update the system again with a standard yum update command. This should take care of any missing dependencies that may have been removed in the previous process, and of course it’ll update the rest of your system too, hopefully taking care of the initial problem.
1
|
yum update
|
Finally, to see if there’s any remaining trouble with the yum database, we can issue the following and are – hopefully – greeted with the same message:
1
2
3
4
|
package–cleanup —problems
Loaded plugins: fastestmirror
No Problems Found
|