After upgrade Ubuntu would only boot readonly. 1.  First check to see the uuid entered in /etc/fstab: cat /etc/fstab revealed that the original uuid was different then the current uuid 2. Check to see what the current UUID is showing up as: blkid 3. If the UUID does not match, remount the filesystem to the

If you receive an error similar to this: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://dl.google.com/linux/earth/deb stable Release: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 1397BC53640DB551 W: Failed to fetch http://dl.google.com/linux/earth/deb/dists/stable/Release.gpg The following

List available timezone locations Type: timedatectl list-timezones Africa/Abidjan Africa/Accra Africa/Addis_Ababa Africa/Algiers Africa/Asmara … … … America/New_York set timezone Type:  timedatectl set-timezone America/New_York display settings Tyep: timedatectl Local time: Fri 2017-06-21 16:10:07 EDT Universal time: Fri 2017-06-21 07:10:07 UTC RTC time: Fri 2017-07-21 07:10:06 Time zone: America/New_York (EDT, -0400) Network time on: yes NTP synchronized: yes

Knockd was causing me a headache with the error “command returned non-zero status code (1)” when running with their stock init.d setup. Rather than troubleshooting their bug I decided to create my own service that would start using the /usr/sbin/knockd directly. Step (1) Create the startup script nano /etc/systemd/system/knockd-security.service [Unit] Description=knockdservice After=network-online.target [Service] Type=idle ExecStart=/usr/local/bin/knockd-security.sh

SSH won’t start at boot on Kali 2.0? Don’t worry, it’s because Kali 2.x is based on Debian 8, as opposed to Kali 1.x being based on Debian 7. Kali 1.x uses init/update-rc.d; For Kali 1.x, the command is update-rc.d ssh enable Kali 2.x uses systemd/systemctl For Kali 2.x, the command is systemctl enable ssh.service