Skip to main content

Posts

Experimenting with Archlinux on Legacy Bios system

nano /etc/wpa_suppplicant/wpa_supplicant.conf    ctrl_interface=/run/wpa_supplicant    update_config=1 wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf wpa_cli    scan    add_network    set_network 0 ssid "home_net"    set_network 0 psk "passphrase"    enable_network 0    save_config dhcpcd wlan0 mkswap /dev/sd# swapon /dev/sd# mkfs.ext4 /dev/sd* mkfs.ext4 /dev/sd* mount /dev/sd* /mnt mount /dev/sd* /mnt/home mount /dev/sd^ /mnt/boot pacstrap /mnt base genfstab -U /mnt >> /mnt/etc/fstab arch-chroot /mnt ln -sf /usr/share/zoneinfo/Region/City /etc/localtime timedatectl set-local-rtc 1 nano /etc/locale.gen locale-gen nano /etc/locale.conf    LANG=en_SG.UTF-8 nano /etc/vconsole.conf    KEYMAP=us-eng nano /etc/hostname    archlinux nano /etc/hosts    127.0.0.1 localhost.localdomain     :1 localhost.localdomain    127.0.1.1 archlinux.localdomain passwd pacman -S grub grub-install --target=i386-pc
Recent posts

Installing sshguard 2.4.0 on Fedora 30 using GNU Stow

Install GNU Stow to keep track of built-from-source-code applications using system default repository: sudo dnf install stow We install the following dependencies required for building sshguard application: sudo dnf install byacc flex gcc make We proceed to download sshguard 2.4.0 from sourceforge.net . We can then extract to default home location /home/username . Using terminal/console, set the location to the extracted folder using cd command: cd sshguard-2.4.0/ We proceed to build the sshguard using source makefile by running configure   with installation location set at /usr/local/stow/sshguard and make command: ./configure --prefix=/usr/local/stow/sshguard make We proceed to install the sshguard application using make install command: We edit the sshguard configuration file by setting backend executable file location at: BACKEND="/usr/local/libexec/sshg-fw-firewalld" We proceed to symlink the respective folders under /usr/local/stow/ssh

Configuring Edgerouter X: Part 1

Setting up ssh restricted access to Edgerouter Introduction to Edgerouter's EdgeOS commands Running '?' shows commands available on EdgeOS in operational (upon logging in) and configuration mode ('configure' command) Running 'configure' allows us to go into configure mode Running 'commit' allows us to commit changes  Running 'commit-confirm' allows the change to take effect before reboot (important if you are unsure of the changes made and the impact to the system) Running 'save' allows us to save the change to persistent boot configuration Creating ssh key ssh-keygen Setting permission on .ssh and its subfolders chown -R username:usergroup .ssh/ Upload ssh key ssh-copy-id -i ~/.ssh/clienthost.pub username@routerhostname Loadkey  configure loadkey  commit save Limit ssh to listen to one address set service ssh listen-address 192.168.0.1   Follow my blog with Bloglovin

3 Steps to Universal Grub Protection

In this instance we are using Parrot Security OS as the main OS for installing and updating grub bootloader. The main reference of this article is based on ' Grub2/Passwords '. First we run grub-mkpasswd-pbkdf2 by encrypting password for grub Next we add "superusers" and "password-pbkdf2" to /etc/grub.d/00_header. Finally, we run update-grub. Follow my blog with Bloglovin

Introduction to Solus on a Legacy Bios Machine

GNU/Linux Distro In Reference: Solus 3.99 Solus is a unique GNU/Linux OS. It seems to be independent of any popular distributions. Today, i will share what i have observed in my first month of using Solus 3.99.  Please note my reference is on a non-UEFI Samsung RF410 machine. 1st) Responsiveness My comment on Solus : It is fast relative to Fedora or Debian distro on a same device. I am using Cinnamon DE on Fedora and Mate DE on Parrot Security. For Solus, i also set it as Mate DE which i have used it previously on LMDE 2. 2nd) Unique package system It is using eopkg package system. The term 'eopkg' is derived from its historical beginning as "Evolve OS", hence we can surmise that 'eopkg' is an acronym for 'Evolve OS Package' system. Below is a few commands for handling eopkg system and it is pretty catchy as you need not key in the full command for certain keywords. 'Install': sudo eopkg install <packagename> or sudo eo

Use FWTS (firmware test suite) for ACPI Component Architecture diagnosis

My purpose for this snippet is to review the FWTS for diagnosing the ACPI error log during systemd bootup. ACPI is a complex system, what i had given here is really entry level to explore the firmware test suite on Ubuntu 16.04 LTS on my Lenovo T400 laptop. Hopefully you can venture even further than i do. Ahoy! less /sys/module/acpi/parameters/aml_debug_output if '0' then debug output is off. We can write '1' as a parameter to enable debug output less /sys/module/acpi/parameters/acpica_version The output shows the acpica version in use by the OS. sudo fwts oops acpiinfo fadt madt rsdp -f -r apic.log -D | dialog --gauge "FWTS" 10 90 This runs the ' acpiinfo ' ' fadt ' ' madt ' ' rsdp ' test of the fwts suite. The " dialog " command allows you to visually see the processing of the " fwts " command The acpidump command allows you to get the dump the debug output of acpi for analysis using "

Use Udev rules to set Intel Chip: Turbo Boost/Scaling Governor & Max Freq

In my Parrot Security workstation, the Intel Chip overheats quite easily, so i prefer to set a lower Max Frequency and turning Turbo Boost. However, if you have tried and tested on your laptop and you want to set the highest frequency your workstation or server Intel chip is capable off, you may glean some insight from the udev rules created here. Udevadm Info , Udevadm Control or Restart the Laptop Sometimes we may be clueless as to how to implement udev rules accordingly to type of sysfs devices. In this blog, we will be aiming specifically at the cpu devices. Running the below command gives you the key parameter you may insert into your udev rules for turning on or off Intel turbo boost techonology: udevadm info -a -p /sys/devices/system/cpu   The following is an example of what you may see in the terminal: Udevadm info starts with the device specified by the devpath and then walks up the chain of parent devices. It prints for every device found, all possible attribu