If you use a lot of VBA codes like me then you need to have a place where you can store all of them and use them whenever you need.
But the question is, what’s the best place for this? PERSONAL MACRO WORKBOOK. Yes, that PERSONAL.XLBS workbook. Here’s the crazy thing:
Code for ARP is usually part of the OS kernel, specifically in the networking stack. In Ye Olden Daze, the MAC address was stored in a ROM on the NIC. These days, it's frequently found in flash, as part of the BIOS configuration, as the NIC has been absorbed into the motherboard. + Renew an IP address one time: Note: In this example we will be using the interface eth0. The interface must be configured for DHCP as up and running. Open a terminal and do sudo su to root. Type ifconfig to show the current IP address that you received from DHCP.
Creating a personal macro workbook and storing all the important macros in it can save you a ton of time and help you use them in all Excel files.
Isn’t that AWESOME?? And today in this post, I’ll be sharing with you everything you need to know about this file. So stay with me for the next 3 to 4 minutes.
What is PERSONAL MACRO WORKBOOK
Personal Macro Workbook is a file which can be the common storage place to store your all macros and use them. Although it’s a hidden file which opens when you start Excel in your system. And you don’t need to open it separately when you want to access any of the codes from it. All the codes from it can be seen in your macro list.
What’s the LOCATION of PERSONAL.XLSB Workbook
Here’s the bad news: Even though it’s such a useful thing to have, it’s not there in Excel by default, so you need to create it (I’ve shared the steps ahead in this post). But, you can check if it is already created or not.
The first method is to open your visual basic editor and if your project window you have listed a “PERSONAL.XLBS” named file.
That means it’s already there and there is no need to create it. The second method is to have a look at your XLSTART folder.
Note: If you put anything thing in the XLSTART folder that will open automatically when you launch Excel. If you are using Windows 10:
C:UsersPuneet GogiaAppDataRoamingMicrosoftExcelXLSTART
And if you are using MAC: Library ▸ Group Containers ▸ UBF8T346G9.Office ▸ User Content ▸ Startup ▸ Excel
If you aren’t able to find your Personal Macro Workbook using these methods then you need to follow the steps I’ve mentioned ahead to create a new one.
How to Create a Personal Macro Workbook in Excel
Creating a new personal macro workbook is simple. All you need to do is to record a macro, that’s it yes, that’s it.
Windows Version
Here are the simple steps you need to follow:
- First of all, go to the developer tab and click on the “Record Macros” button.
- After that, in the “Record Macro” dialog box:
- Enter a name for the Macro
- In the “Store macro in”, drop down select “Personal Dialog Box”.
- In the end, click OK.
Now you can record something or you can simply click on “Stop Recording”.
Your new “Personal Macro Workbook” created now. You can find the new PERSONAL.XLSB file in the XLSTART folder.
(MAC Version)
Below are the steps to create your Personal Macro Workbook in the MAC version of the Excel.
- First of all, go to the developer tab and click on the “Record Macro Button”.
- After that, enter the name of the macro and select the “Personal Macro Workbook” from the drop-down.
- In the end, click OK.
Now you can simply click on “Stop Recording” as your new personal macro workbook is created.
Why Should I have a Personal Macro Workbook?
This is the real question…
Well, if you love to use macros and have some useful codes which help you do your stuff with a click you must have a Personal Macro Workbook. You can store all those codes your personal workbook and can use them from any workbook on your system.
As I said when you open your Excel the “PERSONAL.XLSB” open with it so your codes will be accessible all the time when you are using Excel. So having it is a big WIN-WIN.
Can I Share My Personal Macro Workbook with Others?
It happens sometimes when you need to share your macros from Personal Macro Workbook with others or you just need to transfer it to a different system. Now in this situation, you can use do the following things:
(A) Export and Import the Module
Where Are Mac Addresses Stored For Future Reference In Excel
The best way to share or transfer your Personal Macro Workbook is to export the VB module from one system and import it in the other system. Below are the steps you can use to do this:
- First, open the VB editor and expand the tree of “Personal.xlsb” and right click on the module which you want to export.
- Now, select the “Export File” option and save it at the desktop and after that transfer it to the new system.
- Next, you need to import this module not the VB editor at the new system.
- For this, open VB editor and right click on the “Personal.xlsb” and select the “Import File”.
- After that, browse the module file and click OK to import.
Now, you have the new module in your Personal Macro Workbook where you have all the VBA codes and you can use them from the macros list.
(B) Copy-Paste Personal.xlsb File to the Startup Folder
If the new system where you want to transfer all the codes don’t have a Personal Macro Workbook then you can simply copy-paste personal.xlsb from the old system to new system’s Excel startup folder.
Yes, that’s it.
Delete Personal Macro Workbook
If you don’t want to have a Personal Macro Workbook you can simply delete it from your system. All you need to do is, open the Excel STARTUP folder and delete the file from there.
Where Are Mac Addresses Stored For Future Reference Online
And if the PERSONAL.XLSB file hidden then you simply unhide it and then delete it. The recommendation is to take a back of the Personal Macro Workbook so that you can restore it in future.
What if I’m Unable to Record a Macro in Personal Macro Workbook
There can be a situation where you aren’t able to record a macro in Personal Macro Workbook. Or, it doesn’t open when you launch Excel.
In this situation, you need to check if your Personal Macro Workbook isn’t under “Disabled Items”. If it is, then you need to enable it. To open “Disabled Items”, go to File Tab ➜ Options ➜ Add-Ins ➜ Manage ➜ Disabled Items.
From this dialog box, you can simply enable it.
Hide it if Excel Keep Opening it Every time
As you know, every time you open Excel, the Personal.xlsb file opens with it automatically but sometimes instead of open as a hidden file it will open in the front.
Well, you can make it hide back. All you need to do is when you open your Excel app go to the View Tab and click on the “Hide” and select the “Personal”.
In the end, click OK. Now, close the Excel and restart it. That’s it.
Transfer Other VBA Codes in Personal Macro Workbook
It’s always better to record and write your macro code in Personal.xlsb, but for all the code which you have before creating the PERSONAL MACRO WORKBOOK.
This thing is simple. All you need to do is create a new module and then paste all the code there.
Lock Personal.xlsb for Editing
If you want to make your Personal Macro Workbook locked so that it can’t be edited then you can simply follow below steps:
- First of all, go to the place where you have Personal.xlsb and right click and open its properties.
- After that, from the “Security” tab tick mark the “Read Only”.
- In the end, click OK.
Once you do this, you can be able to read macro from it but can’t able to save a new macro in it.
In the End,
A Personal Macro Workbook can be helpful for you to manage all the important macros in one place. The best way is to create a personal.xlsb is to simply record a macro in it. I hope you found this VBA tip will help you to Learn VBA, Faster.
But now, tell me one thing.
How you Manage all the VBA codes you use?
Make sure to share your views with me in the comment section, I’d love to hear from you and please, don’t forget to share this post with your friends, I am sure they will appreciate it.
More on VBA
- User Defined Function | Activate a Sheet using VBA| VBA Code to Search on Google| VBA IF | Pivot Table using VBA | VBA MsgBox Function | VBA New Sheet | Record a Macro | VBA Option Explicit
VBA is one of the Advanced Excel Skills.
Estimated reading time: 10 minutes
Ideally, very little data is written to a container’s writable layer, and youuse Docker volumes to write data. However, some workloads require you to be ableto write to the container’s writable layer. This is where storage drivers comein.
Docker supports several different storage drivers, using a pluggablearchitecture. The storage driver controls how images and containers are storedand managed on your Docker host.
After you have read the storage driver overview, thenext step is to choose the best storage driver for your workloads. In makingthis decision, there are three high-level factors to consider:
If multiple storage drivers are supported in your kernel, Docker has a prioritized list of which storage driver to use if no storage driver is explicitly configured, assuming that the storage driver meets the prerequisites.
Use the storage driver with the best overall performance and stability in the most usual scenarios.
Docker supports the following storage drivers:
overlay2is the preferred storage driver, for all currently supported Linux distributions, and requires no extra configuration.aufswas the preferred storage driver for Docker 18.06 and older, when running on Ubuntu 14.04 on kernel 3.13 which had no support foroverlay2.fuse-overlayfsis preferred only for running Rootless Dockeron a host that does not provide support for rootlessoverlay2.On Ubuntu and Debian 10, thefuse-overlayfsdriver does not need to beusedoverlay2works even in rootless mode.See Rootless mode documentation.devicemapperis supported, but requiresdirect-lvmfor production environments, becauseloopback-lvm, while zero-configuration, has very poor performance.devicemapperwas the recommended storage driver for CentOS and RHEL, as their kernel version did not supportoverlay2. However, current versions of CentOS and RHEL now have support foroverlay2, which is now the recommended driver.- The
btrfsandzfsstorage drivers are used if they are the backingfilesystem (the filesystem of the host on which Docker is installed).These filesystems allow for advanced options, such as creating “snapshots”,but require more maintenance and setup. Each of these relies on the backingfilesystem being configured correctly. - The
vfsstorage driver is intended for testing purposes, and for situationswhere no copy-on-write filesystem can be used. Performance of this storagedriver is poor, and is not generally recommended for production use.
Docker’s source code defines the selection order. You can see the order atthe source code for Docker Engine - Community 20.10
If you run a different version of Docker, you can use the branch selector at the top of the file viewer to choose a different branch.
Some storage drivers require you to use a specific format for the backing filesystem. If you have external requirements to use a specific backing filesystem, this may limit your choices. See Supported backing filesystems.
Where Are Mac Addresses Stored For Future Reference Chart
After you have narrowed down which storage drivers you can choose from, your choice is determined by the characteristics of your workload and the level of stability you need. See Other considerationsfor help in making the final decision.
NOTE: Your choice may be limited by your operating system and distribution. For instance, aufs is only supported on Ubuntu and Debian, and may require extra packages to be installed, while btrfs is only supported on SLES, which is only supported with DockerEnterprise. See Support storage drivers per Linux distribution for more information.
Supported storage drivers per Linux distribution
At a high level, the storage drivers you can use is partially determined bythe Docker edition you use.
In addition, Docker does not recommend any configuration that requires you todisable security features of your operating system, such as the need to disableselinux if you use the overlay or overlay2 driver on CentOS.
Docker Engine - Community
For Docker Engine - Community, only some configurations are tested, and your operatingsystem’s kernel may not support every storage driver. In general, the followingconfigurations work on recent versions of the Linux distribution:
| Linux distribution | Recommended storage drivers | Alternative drivers |
|---|---|---|
| Docker Engine - Community on Ubuntu | overlay2 or aufs (for Ubuntu 14.04 running on kernel 3.13) | overlay¹, devicemapper², zfs, vfs |
| Docker Engine - Community on Debian | overlay2 (Debian Stretch), aufs or devicemapper (older versions) | overlay¹, vfs |
| Docker Engine - Community on CentOS | overlay2 | overlay¹, devicemapper², zfs, vfs |
| Docker Engine - Community on Fedora | overlay2 | overlay¹, devicemapper², zfs, vfs |
¹) The overlay storage driver is deprecated, and will be removed in a futurerelease. It is recommended that users of the overlay storage driver migrate to overlay2.
²) The devicemapper storage driver is deprecated, and will be removed in a futurerelease. It is recommended that users of the devicemapper storage driver migrateto overlay2.
Note
Where Are Mac Addresses Stored For Future Reference
The comparison table above is not applicable for Rootless mode.For the drivers available in Rootless mode, see the Rootless mode documentation.
When possible, overlay2 is the recommended storage driver. When installingDocker for the first time, overlay2 is used by default. Previously, aufs wasused by default when available, but this is no longer the case. If you want touse aufs on new installations going forward, you need to explicitly configureit, and you may need to install extra packages, such as linux-image-extra.See aufs.
Where Are Mac Addresses Stored For Future References
On existing installations using aufs, it is still used.
When in doubt, the best all-around configuration is to use a modern Linuxdistribution with a kernel that supports the overlay2 storage driver, and touse Docker volumes for write-heavy workloads instead of relying on writing datato the container’s writable layer.
The vfs storage driver is usually not the best choice. Before using the vfsstorage driver, be sure to read aboutits performance and storage characteristics and limitations.
Expectations for non-recommended storage drivers: Commercial support isnot available for Docker Engine - Community, and you can technically use any storage driverthat is available for your platform. For instance, you can use btrfs withDocker Engine - Community, even though it is not recommended on any platform forDocker Engine - Community, and you do so at your own risk.
The recommendations in the table above are based on automated regressiontesting and the configurations that are known to work for a large number ofusers. If you use a recommended configuration and find a reproducible issue,it is likely to be fixed very quickly. If the driver that you want to use isnot recommended according to this table, you can run it at your own risk. Youcan and should still report any issues you run into. However, such issueshave a lower priority than issues encountered when using a recommendedconfiguration.
Docker Desktop for Mac and Docker Desktop for Windows
Docker Desktop for Mac and Docker Desktop for Windows are intended for development, ratherthan production. Modifying the storage driver on these platforms is notpossible.
Supported backing filesystems
With regard to Docker, the backing filesystem is the filesystem where/var/lib/docker/ is located. Some storage drivers only work with specificbacking filesystems.
| Storage driver | Supported backing filesystems |
|---|---|
overlay2, overlay | xfs with ftype=1, ext4 |
fuse-overlayfs | any filesystem |
aufs | xfs, ext4 |
devicemapper | direct-lvm |
btrfs | btrfs |
zfs | zfs |
vfs | any filesystem |
Other considerations
Suitability for your workload
Among other things, each storage driver has its own performance characteristicsthat make it more or less suitable for different workloads. Consider thefollowing generalizations:
overlay2,aufs, andoverlayall operate at the file level rather thanthe block level. This uses memory more efficiently, but the container’swritable layer may grow quite large in write-heavy workloads.- Block-level storage drivers such as
devicemapper,btrfs, andzfsperformbetter for write-heavy workloads (though not as well as Docker volumes). - For lots of small writes or containers with many layers or deep filesystems,
overlaymay perform better thanoverlay2, but consumes more inodes, whichcan lead to inode exhaustion. btrfsandzfsrequire a lot of memory.zfsis a good choice for high-density workloads such as PaaS.
More information about performance, suitability, and best practices is availablein the documentation for each storage driver.
Shared storage systems and the storage driver
If your enterprise uses SAN, NAS, hardware RAID, or other shared storagesystems, they may provide high availability, increased performance, thinprovisioning, deduplication, and compression. In many cases, Docker can work ontop of these storage systems, but Docker does not closely integrate with them.
Each Docker storage driver is based on a Linux filesystem or volume manager. Besure to follow existing best practices for operating your storage driver(filesystem or volume manager) on top of your shared storage system. Forexample, if using the ZFS storage driver on top of a shared storage system, besure to follow best practices for operating ZFS filesystems on top of thatspecific shared storage system.
Stability
For some users, stability is more important than performance. Though Dockerconsiders all of the storage drivers mentioned here to be stable, some are newerand are still under active development. In general, overlay2, aufs, overlay,and devicemapper are the choices with the highest stability.
Test with your own workloads
You can test Docker’s performance when running your own workloads on differentstorage drivers. Make sure to use equivalent hardware and workloads to matchproduction conditions, so you can see which storage driver offers the bestoverall performance.
Where Are Mac Addresses Stored For Future Reference Pdf
Check your current storage driver
The detailed documentation for each individual storage driver details all of theset-up steps to use a given storage driver.
Where Are Mac Addresses Stored For Future Reference In Word
To see what storage driver Docker is currently using, use docker info and lookfor the Storage Driver line:
To change the storage driver, see the specific instructions for the new storagedriver. Some drivers require additional configuration, including configurationto physical or logical disks on the Docker host.
Important: When you change the storage driver, any existing images andcontainers become inaccessible. This is because their layers cannot be usedby the new storage driver. If you revert your changes, you canaccess the old images and containers again, but any that you pulled orcreated using the new driver are then inaccessible.