In this example we install debian 10 with --variant=minbase which gives us a minimal/tiny install. Don't use variant if you want the full size install.
mkdir /tmp/deb10files
debootstrap --variant=minbase buster /tmp/deb10files/
Did you get an error?
debootstrap --variant=minbase buster /home/theuser/VMs/deb10files/
You'll get this error if you make a directory in your home........
Solution for python pip3 not working anymore
from pip._internal.cli.main import main
File "/usr/local/lib/python3.5/dist-packages/pip/_internal/cli/main.py", line 60
sys.stderr.write(f"ERROR: {exc}")
wget https://bootstrap.pypa.io/pip/3.5/get-pip.py
python3 get-pip.py
DEPRECATION: Python 3.5 reached the end of its life on September 13th, 20........
1.) Make sure your conf register is 0x2102
Do show version and at the very end of the output you will see the Configuration register.
show version
Configuration register is 0x2102
If the config register is not 0x2102 then enter this command:
r1#configure terminal
r1(config)#config-register 0x2102
r1(config)#end
2.) Let's Erase the NVRAM/flash........
It is a bit different and annoying here for these types of routers/models as you need to physically remove the CF (Compact Flash) and only then, will it enter ROMMON mode (Ctrl + Pause remotely over the console will not do it for us). This means you cannot do this remotely, or at least not without the help of a remote/physical helper.
Step 1.) Power off, router and remove CF Disk Slot#2
Go to the router and remove the slot#2 cover uses your hand or it may help to use a........
yum -y install gcc make gperf genisoimage flex bison ncurses ncurses-devel pcre-devel augeas-devel augeas readline-devel
checking for cpio... cpio
checking for gperf... no
configure: error: gperf must be installed
configure: error: Package requirements (augeas >= 1.2.0) were not met:
Requested 'augeas >= 1.2.0' but version of augeas is 1.0.0
yum remove augeas augeas-libs augeas-devel
wget http://downl........
The code may lead you to believe you have an incompatible template but if you are not trying to use an old template currently that is not the issue. I actually deleted all 3.x style templates to make sure.
What the issue is, is old plugins that are not compatible but Vbulletin does not seem to account for this except that you'll see a fatal PHPerror. You should disable all plugins and then enable one by one until you find the one that is causing the issue.
&........