The following format allows you to set the current date from a string;
sudo date -s '2023-01-14 11:22:00'
where the above date refers to 14th Jan 2023
Heisenberg - Digital Alchemist, Software Architect, Automation Specialist and Mechanical Engineer.
The following format allows you to set the current date from a string;
sudo date -s '2023-01-14 11:22:00'
where the above date refers to 14th Jan 2023
Debian archive for sources.list
http://archive.debian.org/debian-archive/debian/dists/
The sources.list file may look like (need to check the deb-src entries);
deb [trusted=yes] http://archive.debian.org/debian-archive/debian/ squeeze main non-free contrib
deb-src [trusted=yes] http://archive.debian.org/debian-archive/debian/ squeeze main non-free contrib
deb [trusted=yes] http://archive.debian.org/debian-archive/debian/ wheezy main non-free contrib
deb-src [trusted=yes] http://archive.debian.org/debian-archive/debian/ wheezy main non-free contrib
deb [trusted=yes] http://archive.debian.org/debian-archive/debian/ jessie main non-free contrib
deb-src [trusted=yes] http://archive.debian.org/debian-archive/debian/ jessie main non-free contrib
deb [trusted=yes] http://deb.debian.org/debian/ buster main non-free contrib
deb-src [trusted=yes] http://deb.debian.org/debian/ buster main non-free contrib
Also:
apt-key add /root/archive-key-6.0.asc (acquired from the keys.html link below *)
See also:
https://wiki.debian.org/SourcesList
https://ftp-master.debian.org/keys.html (* get key file from here and do apt-ket add key-file)
Attempts to do this through apt-get involved upgrading too many packages and in my opinion, was too risky. Therefor, an upgrade from Squeeze to Wheezy was done this way and from there, a kernel [5.15.94] was built on another box, in my case a Debian 11 VM running kernel [5.10.0-21]
There may be occasions where we need to boot manually from the GRUB menu and perhaps realize that you should just have installed LILO in the first place :)
TBA:
GRUB - Embedding is not possible
The following is the output of fdisk -l on both the machine to which the original backups were taken and also a machine to which a successful restoration has been carried out. In the case of the latter, both a physical and a VM.
![]() |
| FEC-A |
![]() |
| FEC-B |
The df output is the same for both physical machines, as in the device is /dev/cciss/c0d0p* which the VM follows the /dev/sda* format, which perhaps makes sense since the physical machines are the same and both have the same raid controller.
To put the cursor at the end of all lines in VS code, firstly, select all text and then do SHIFT+ALT+i
Additionally, to select multiple cursors anywhere in a vertical line, firstly, click the start point and then using SHIFT+CTRL click the second point
This method seems to work best for me;
There is a script /etc/profile that sets up environment variables and that also includes any scripts in /etc/profile.d so I chose to create a file /etc/profile.d/java.sh with 755 permissions with the following contents;
export JAVA_HOME="/opt/jdk1.8.0_341"
export PATH=$JAVA_HOME/bin:$PATH
On, we can check /etc/resolv.conf but how do we know which IP is actually being used?