-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
5 changed files
with
100 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,33 @@ | ||
+++ | ||
title = 'Install Arch with SSH' | ||
date = 2024-06-22T07:33:40Z | ||
draft = false | ||
+++ | ||
|
||
My current Arch Linux installation has many years and I'd like to reinstall it using other technologies like LVM and BTRFS, but before reinstalling my laptop, I'm testing the installation process inside a VirtualBox VM. This morning I got bored of typing all the commands and in my head popped up [Powershell Direct with Hyper-V](https://learn.microsoft.com/en-us/virtualization/hyper-v-on-windows/user-guide/powershell-direct). Basically you can attach a Powershell session directly to the Hyper-V VM. | ||
|
||
I found a similar approach by configuring port forwarding in VirtualBox and connecting via SSH. | ||
|
||
## Getting started | ||
|
||
1. If you have configured the VM with the NIC in NAT, you will need to create a port forwarding, go to *Setting → Network → Advanced → Port forwarding*. Add a new rule with the following settings: | ||
|
||
* **Name**: ssh | ||
* **Protocol**: TCP | ||
* **Host Port**: 2222 | ||
* **Guest Port**: 22 | ||
* Leave others empty | ||
|
||
1. According to [Install Arch Linux via SSH](https://wiki.archlinux.org/title/Install_Arch_Linux_via_SSH) the default **root** password is empty, so we need to configure one: | ||
|
||
```bash | ||
# passwd | ||
``` | ||
|
||
1. From a terminal on the host system, run the following command to connect: | ||
|
||
```bash | ||
ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -p 2222 root@localhost | ||
``` | ||
|
||
The `-o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null` options will prevent verifying and writing the live environment's SSH host keys to `~/.ssh/known_hosts` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,50 @@ | ||
+++ | ||
title = 'Raspberry Pi Notes' | ||
date = 2024-05-31T10:27:03Z | ||
draft = true | ||
+++ | ||
|
||
These evolving personal notes document my journey and discoveries as I explore the versatile Raspberry Pi. At present, all information pertains specifically to the **Raspberry Pi 5**. | ||
|
||
## Hardware | ||
|
||
### Power | ||
|
||
* **Minimum required**: 5V / 3A (can't connect any bus-powered HDDs/SSDs) | ||
* **Best performance**: 5v / 5A | ||
|
||
Remainder: x Volt * y Amp = z Watt | ||
|
||
[Pogo Pin](https://upload.wikimedia.org/wikipedia/commons/thumb/f/f3/Pogo_Pin_Connectors.jpg/1920px-Pogo_Pin_Connectors.jpg): A pogo pin is a spring-loaded connector used to create reliable electrical connections in electronics without the need for soldering, commonly for programming and connecting peripherals. | ||
|
||
## Firmware | ||
|
||
```bash | ||
# Update Raspberry firmware | ||
rpi-update | ||
``` | ||
|
||
## Networking | ||
|
||
In Raspberry Pi OS 12 and later, dhcpcd is no longer used, everything goes through Network Manager, which is configured via nmcli or nmtui. | ||
|
||
```bash | ||
# View status | ||
nmcli device status | ||
|
||
# View NIC details | ||
nmcli device show eth0 | ||
|
||
# Configure networking | ||
sudo nmtui | ||
|
||
# Apply changes | ||
sudo systemctl restart NetworkManager | ||
``` | ||
|
||
## Shops | ||
|
||
* [Berrybase](https://www.berrybase.ch) | ||
* [PI-SHOP](https://www.pi-shop.ch) | ||
* [Pimoroni](https://shop.pimoroni.com) | ||
* [Geekworm](https://geekworm.com) & [Geekworm on AliExpress](https://geekworm.aliexpress.com/store/1048722) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
+++ | ||
title = 'VirtualBox Secure Boot & UEFI' | ||
date = 2024-05-20T16:44:23Z | ||
draft = true | ||
+++ | ||
|
||
This short article explains how to enable [Secure Boot](https://wiki.debian.org/SecureBoot) and [UEFI](https://wiki.debian.org/UEFI) for a Debian VM in VirtualBox. | ||
|
||
## Getting Started | ||
|
||
In the VirtualBox VM settings go to **System** and enable Extended Features: **Enable EFI (special OSes only) and **Enable Secure Boot**. | ||
|
||
## Inside the VM | ||
|
||
{{< gist Schwitzd c819f172ea2d407a47711172ddec0de1 >}} |