Add new post, work on CSS for posts
This commit is contained in:
parent
f415d78fba
commit
83f4f5767e
4
Gemfile
4
Gemfile
|
|
@ -5,4 +5,6 @@ source "https://rubygems.org"
|
|||
# gem "rails"
|
||||
|
||||
gem "jekyll", "~> 4.3"
|
||||
gem "jekyll-feed"
|
||||
gem "jekyll-feed"
|
||||
gem 'jekyll-thumbnail-img'
|
||||
gem 'jekyll-loading-lazy'
|
||||
38
Gemfile.lock
38
Gemfile.lock
|
|
@ -39,10 +39,23 @@ GEM
|
|||
webrick (~> 1.7)
|
||||
jekyll-feed (0.17.0)
|
||||
jekyll (>= 3.7, < 5.0)
|
||||
jekyll-loading-lazy (0.1.1)
|
||||
jekyll (>= 3.0, < 5.0)
|
||||
nokogiri (>= 1.10, < 2.0)
|
||||
jekyll-sass-converter (3.0.0)
|
||||
sass-embedded (~> 1.54)
|
||||
jekyll-thumbnail-img (0.1.2)
|
||||
jekyll
|
||||
mini_magick
|
||||
jekyll-watch (2.2.1)
|
||||
listen (~> 3.0)
|
||||
jekyll_picture_tag (2.1.2)
|
||||
addressable (~> 2.6)
|
||||
jekyll (~> 4.0)
|
||||
mime-types (~> 3.0)
|
||||
objective_elements (~> 1.1)
|
||||
rainbow (~> 3.0)
|
||||
ruby-vips (~> 2.2)
|
||||
kramdown (2.4.0)
|
||||
rexml
|
||||
kramdown-parser-gfm (1.1.0)
|
||||
|
|
@ -51,10 +64,29 @@ GEM
|
|||
listen (3.9.0)
|
||||
rb-fsevent (~> 0.10, >= 0.10.3)
|
||||
rb-inotify (~> 0.9, >= 0.9.10)
|
||||
logger (1.6.1)
|
||||
mercenary (0.4.0)
|
||||
mime-types (3.6.0)
|
||||
logger
|
||||
mime-types-data (~> 3.2015)
|
||||
mime-types-data (3.2024.1105)
|
||||
mini_magick (5.0.1)
|
||||
mini_portile2 (2.8.8)
|
||||
nokogiri (1.16.7)
|
||||
mini_portile2 (~> 2.8.2)
|
||||
racc (~> 1.4)
|
||||
nokogiri (1.16.7-arm64-darwin)
|
||||
racc (~> 1.4)
|
||||
nokogiri (1.16.7-x86_64-darwin)
|
||||
racc (~> 1.4)
|
||||
nokogiri (1.16.7-x86_64-linux)
|
||||
racc (~> 1.4)
|
||||
objective_elements (1.1.2)
|
||||
pathutil (0.16.2)
|
||||
forwardable-extended (~> 2.6)
|
||||
public_suffix (6.0.1)
|
||||
racc (1.8.1)
|
||||
rainbow (3.1.1)
|
||||
rake (13.2.1)
|
||||
rb-fsevent (0.11.2)
|
||||
rb-inotify (0.11.1)
|
||||
|
|
@ -62,6 +94,9 @@ GEM
|
|||
rexml (3.3.5)
|
||||
strscan
|
||||
rouge (4.3.0)
|
||||
ruby-vips (2.2.2)
|
||||
ffi (~> 1.12)
|
||||
logger
|
||||
safe_yaml (1.0.5)
|
||||
sass-embedded (1.69.5)
|
||||
google-protobuf (~> 3.23)
|
||||
|
|
@ -91,6 +126,9 @@ PLATFORMS
|
|||
DEPENDENCIES
|
||||
jekyll (~> 4.3)
|
||||
jekyll-feed
|
||||
jekyll-loading-lazy
|
||||
jekyll-thumbnail-img
|
||||
jekyll_picture_tag
|
||||
|
||||
BUNDLED WITH
|
||||
2.5.19
|
||||
|
|
|
|||
|
|
@ -9,3 +9,5 @@ sass:
|
|||
style: compressed
|
||||
plugins:
|
||||
- jekyll-feed
|
||||
- jekyll-thumbnail-img
|
||||
- jekyll-loading-lazy
|
||||
|
|
|
|||
|
|
@ -0,0 +1,6 @@
|
|||
<figure class="main">
|
||||
<a target="_blank" href="{{ include.src }}">
|
||||
<img src="{% thumbnail_img include.src 2000 %}" alt="{{ include.alt }}">
|
||||
</a>
|
||||
<figcaption>{{ include.caption }}</figcaption>
|
||||
</figure>
|
||||
|
|
@ -0,0 +1,6 @@
|
|||
<figure class="small-image">
|
||||
<a target="_blank" href="{{ include.src }}">
|
||||
<img src="{% thumbnail_img include.src 1200 %}" alt="{{ include.alt }}">
|
||||
</a>
|
||||
<figcaption>{{ include.caption }}</figcaption>
|
||||
</figure>
|
||||
|
|
@ -17,6 +17,7 @@
|
|||
<p style="text-align: right; font-style: italic;">This post was published on {{ page.date | date_to_string }}</p>
|
||||
|
||||
{{ content }}
|
||||
<div class="clearfix"></div>
|
||||
</div>
|
||||
|
||||
<footer>
|
||||
|
|
|
|||
|
|
@ -0,0 +1,44 @@
|
|||
---
|
||||
layout: post
|
||||
author: hexaitos
|
||||
title: Asahi Linux on my base model M1 MacBook Air
|
||||
excerpt: In this blog post I will be taking a quick look at Asahi Linux and my opinions on it so far. I have installed it on my base-model M1 MacBook Air and am planning of perhaps turning it into a very low-powered yet still powerful server.
|
||||
---
|
||||
{% include img/main.html src="/assets/images/blog_posts/asahi_mba_m1/20241118-WE2A1144.jpg" caption="A photo of my MacBook Air running Asahi Linux with KDE Plasma 6" alt="An opened MacBook Air M1 standing on a table. It is showing the desktop of KDE Plasma 6 with the floating task bar at the bottom. The desktop background is a bird of prey." %}
|
||||
|
||||
A couple of years ago – still during my apprenticeship and also during the pandemic – I bought a base model M1 MacBook Air with some bonus money that I got for finishing an important (to my boss, at any rate) project at work and it’s been my main laptop ever since and one that I’ve been using basically daily ever since. However, the fact that I only got a base model has been a bit problematic and, thefore, I decided to upgrade to the new M4 MacBook Pro this year. This, then, leaves me with my still more than capable MacBook Air and I’ve been thinking about what to do with it. Then I remembered the fact that I’ve always been wanting to try out Asahi Linux; and that coupled with the *very* low power consumption of these M-series chips made me think that it would probably make for a really good low-powered server that still has enough *oomph* for more heavy workloads (definitely more than my *actual* server that’s running an Intel N100). And so that’s exactly what I did!
|
||||
|
||||
## Installation
|
||||
The installation of Asahi is pretty straightforward in general, but having only a base model Mac (with a measly 256 GB SSD) does pose a bit of a problem: Asahi cannot be installed as the sole operating system; instead; it can only be installed *alongside* macOS. This, then, means that even after completely erasing my previous Sonoma install and then *only* running the Asahi Linux installer afterwards, I only have about 150 GB of usable disk space on my Asahi partition. Now that’s not that bad or anything, but it’s definitely not a lot of disk space in today’s world.
|
||||
|
||||
Speaking of the installation, it’s pretty much as simple as running `curl https://alx.sh | sh` in a terminal window and following the on-screen prompts (insert disclaimer about running running shell scripts without checking their contents first here). If you’re even remotely familiar with the command line (and are able to read), then the installation shouldn’t pose any significant problems. Still, I would not recommend installing this on your main machine that you use for other things as well as I’m sure it can quite easily render your macOS install useless if something goes wrong.
|
||||
|
||||
During the installation process, you’ll be given the opportunity to set a new size for the macOS partition and a size for the to-be-created Asahi Linux partition. Additionally, you can choose between either Gnome or KDE (if I remember correctly) as your desktop environment. Then, after some rebooting and changing of Mac security features, you’ll be greeted by an installer that you’re going to be very familar with if you’ve ever installed a Linux distribution. There you’ll choose a timezone and a username and password. Afterwards you can reboot and you should be greeted by a login window.
|
||||
|
||||
As a side note: Asahi used to be based on Arch Linux but they appear to have moved over to Fedora and the Fedora-based Asahi Linux is, as far as I can tell, the only <q>official</q>. There are some [community-maintained flavours](https://github.com/AsahiLinux/docs/wiki/SW:Alternative-Distros) but I haven’t tried out any of those yet; I am also guessing their installation process will differ quite significantly from that of the official Fedora-based version.
|
||||
|
||||
## The desktop experience
|
||||
I was honestly quite surprised at how *usable* it was in general, the only thing I still would very much like to see implemented is the ability to connect an external monitor through one of the USB-C ports of the MBA — that has (as of the publishing of this post) not yet been implemented. Other than that, however, everything worked pretty much as you’d expect: you can change the brightness of the keyboard and the screen; the trackpad works (and even has force feedback); the speakers work and sound as you would expect them to sound; the keys on the keyboard all work (including things like the media keys for playing/pausing videos or music); closing the lid makes the laptop reliably go to sleep and opening it wakes it up quite quickly … you get the idea. Even the battery life is as fantastic (KDE estimating 9-12 hours) despite this MacBook being 4-ish years old now. WiFi also works perfectly and at the the expected speed.
|
||||
|
||||
{% include img/small.html src="/assets/images/blog_posts/asahi_mba_m1/screenshot-fastfetch.png" caption="Fastfetch running on the MacBook Air" alt="A screenshot showing a full-screened terminal window and the output of the program fastfetch. The output shows some information about the machine, such as the processor and its speed, OS etc." %}
|
||||
|
||||
There are some strange behaviours here and there though. For example, whilst the trackpad does work, the palm rejection is, seemingly, non-existent, especially if you’re used to how well it works on macOS. Oh and speaking of the trackpad, it feels strangely laggy, almost as though it were connected through a terrible bluetooth connection (I’m pretty sensitive to input delay in general though, so you might not notice this at all). Also, you’re going to have to use regular Windows-style shortcuts, i. e. `⌃C` instead of `⌘C` for copying things, as an example.
|
||||
|
||||
Additionally, you might not have access to all the packages as, obviously, this isn’t an `x86_64`-based system but rather `aarch64`. I wanted to install Ruby on my system and I generally use `rbenv` to manage my Rubies. However, I first had a bit of trouble getting `rbenv` itself working and once I did, I had even *more* trouble getting it to actually compile Ruby 3.3.6 for me. At first, there were some problems with `openssl` that I managed to somehow fix by running `sudo dnf groupinstall "Development Tools"` but then it complained about `libffi` apparently missing (even though it wasn’t as far as I could tell) so I just ended up using `rvm` instead – that could compile Ruby 3.6.6 without any problems.
|
||||
|
||||
Most of the Flatpaks that I’ve tried worked without any problems except for the Flatpak for Telegram for some reason, but that might’ve just been my doing something wrong. LibreWolf, the browser I generally use on Linux, works fine and runs as expected, though also through a Flatpak. Tokodon, KDE’s own Mastodon / Fediverse client, also works quite well. The GPU, apparently, *also* works but I haven’t really tried that out yet. Watching YouTube videos, even at 4K, was not a problem however and I couldn’t detect any dropped frames.
|
||||
|
||||
A colleague of mine – who is also quite interested in both ARM and RISC-V – has told me about Box64 which allows you to run normal `x86_64`-based programs on an ARM-based processor. I haven’t yet tried this out myself but I definitely want to try it out and see if I can get some non-native programs running through that.
|
||||
|
||||
## And as a server?
|
||||
|
||||
{% include img/small.html src="/assets/images/blog_posts/asahi_mba_m1/screenshot-sensors.png" caption="The output of lm-sensors" alt="A screenshot showing a terminal window and the output of the sensors command. It is showing temperatures, voltages and a wattage." %}
|
||||
|
||||
I still haven’t done too much with regards to trying it out as a server, but I still feel like it should work quite well as long as all the software also works. I *really* wanted to get something like Proxmox or maybe even just YunoHost working, but I haven’t really found a way to do that yet. One thing I already did was change the charging limit from `100%` down to `80%`. I had to do this through the console by running `echo 80 |sudo tee /sys/class/power_supply/macsmc-battery/charge_control_end_threshold` in the terminal as changing the charging limit through KDE’s GUI settings did not seem to work.
|
||||
|
||||
I also installed `lm-sensors`. I did that mostly to see the temperatures at which the computer was running, but I was very surprised to see that it also provided me with a nice way of seeing how much power it was using at a given time. This showed me that the power usage even with the screen turned on was rather low! I, therefore, enabled ssh and ssh’d into the machine to see what its power usage would be when the screen was completely turned off; and I was very surprised to see that the idle power consumption appears to be around 1-2 W with the screen turned off. Now that’s *really* low value and something that you would *probably* have a hard time noticing on your monthly power bill.
|
||||
|
||||
If I were to actually start using this machine as a server, I would probably install a more minimal version of Asahi (probably without any DE whatsoever) and I would also need to get some sort of USB-C to ethernet adapater and *hope* that it works; though depending on what exactly I’ll end up using the server for, a decent WiFi connection might not be all that problematic either.
|
||||
|
||||
## Conclusion
|
||||
I was pleasantly surprised to see how well it works just out of the box and will definitely be keeping Asahi on my MBA. I’ll try out some more stuff, especially in regards to running it as a server or I might just keep it around as a nice Linux machine in general.
|
||||
|
|
@ -24,6 +24,7 @@
|
|||
|
||||
<p>Hello everyone! This is my first blog post, mostly just to try out how everything works.</p>
|
||||
|
||||
<div class="clearfix"></div>
|
||||
</div>
|
||||
|
||||
<footer>
|
||||
|
|
|
|||
|
|
@ -1,6 +1,8 @@
|
|||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
||||
<meta charset="UTF-8">
|
||||
<meta name="viewport" content="width=device-width,initial-scale=1">
|
||||
<meta name="description" content="">
|
||||
|
|
@ -9,6 +11,7 @@
|
|||
|
||||
<link rel="stylesheet" href="/assets/css/styles.css">
|
||||
|
||||
</head>
|
||||
<body>
|
||||
<div class="menu">
|
||||
<a href="/index.html">Home</a>
|
||||
|
|
@ -50,13 +53,13 @@
|
|||
|
||||
<p>What you have to do is go into your domain’s DNS settings and create <strong>only a single AAAA record with the proxy enabled</strong>. Do not add another <code class="language-plaintext highlighter-rouge">AAAA</code> record or even an <code class="language-plaintext highlighter-rouge">A</code> record; simply add a <code class="language-plaintext highlighter-rouge">AAAA</code> pointing to the IPv6 address of your server. This should look as follows:</p>
|
||||
|
||||
<p><img src="/assets/images/blog_posts/hosting_at_home/bateleur_org.png" alt="A screenshot from Cloudflare’s website showing a single AAAA record set for the domain bateleur.org" /></p>
|
||||
<p><img src="/assets/images/blog_posts/hosting_at_home/bateleur_org.png" alt="A screenshot from Cloudflare’s website showing a single AAAA record set for the domain bateleur.org" loading="lazy"></p>
|
||||
|
||||
<p>This is probably the most important aspect of this entire thing if you want your website to be reachable even in networks that do not support IPv6. If you only set a <code class="language-plaintext highlighter-rouge">AAAA</code> record and no <code class="language-plaintext highlighter-rouge">A</code> record, Cloudflare will automatically translate requests from IPv4 networks so that your website can be reached even from those networks.</p>
|
||||
|
||||
<p>You may also have to change the SSL settings of your domain. By default, the SSL setting is set to <q>flexible</q> which ended up not working for me and I had to set it to <q>full</q> instead:</p>
|
||||
|
||||
<p><img src="/assets/images/blog_posts/hosting_at_home/cloudflare_ssl.png" alt="A screenshot of Cloudflare’s SSL settings" width="30%" /></p>
|
||||
<p><img src="/assets/images/blog_posts/hosting_at_home/cloudflare_ssl.png" alt="A screenshot of Cloudflare’s SSL settings" width="30%" loading="lazy"></p>
|
||||
|
||||
<p>While you’re here, you might as well also create an API key either for your entire account or only for a particular zone / domain. For more information about what permissions need to be set, you can look at the <a href="https://github.com/caddy-dns/cloudflare">GitHub page for Caddy’s Cloudflare module</a>.</p>
|
||||
|
||||
|
|
@ -67,11 +70,11 @@
|
|||
|
||||
<p>To do this, you can simply create yet another alias that includes all the networks that Cloudflare uses. Luckily, Cloudflare publishes the list of their IPv6 subnets which you can find it here: <a href="https://www.cloudflare.com/ips-v6/#">https://www.cloudflare.com/ips-v6/#</a>. So all we need to do is create an alias that includes all seven (at the time of writing) subnets and put that alias into the <q>Source</q> field of our created WAN rules. The alias should end up looking as follows:</p>
|
||||
|
||||
<p><img src="/assets/images/blog_posts/hosting_at_home/cloudflare_ips.png" alt="A screenshot showing a firewall alias containing all of Cloudflare’s IPv6 subnets" /></p>
|
||||
<p><img src="/assets/images/blog_posts/hosting_at_home/cloudflare_ips.png" alt="A screenshot showing a firewall alias containing all of Cloudflare’s IPv6 subnets" loading="lazy"></p>
|
||||
|
||||
<p>And the rule should end up looking as follows:</p>
|
||||
|
||||
<p><img src="/assets/images/blog_posts/hosting_at_home/wan_rule.png" alt="A screenshot of an OPNsense rule" /></p>
|
||||
<p><img src="/assets/images/blog_posts/hosting_at_home/wan_rule.png" alt="A screenshot of an OPNsense rule" loading="lazy"></p>
|
||||
|
||||
<p>Additionally, you also have to set up the rules on the LAN interface. I created two LAN rules, one for the IPv6 and one for the IPv4 address of my webserver and I allowed only ports <code class="language-plaintext highlighter-rouge">443, 80, 123, 53</code> for both IPv4 TCP/UDP and IPv6 TCP/UDP. I also set up a LAN rule that blocks access from my webservers LAN network to all of my other LANs.</p>
|
||||
|
||||
|
|
@ -85,6 +88,7 @@
|
|||
<h2 id="conclusion">Conclusion</h2>
|
||||
<p>Your website should now be accessible from the Internet! I hope you enjoyed reading this and I hope it will end up helping someone in the future. If you have any further questions, critique or whatever, <a href="/contact">feel free to reach out to me</a>. This is the first blog post I have written in a <em>long</em> time, so if there’s anything you think could be improved in the next one, I would love to hear about it.</p>
|
||||
|
||||
<div class="clearfix"></div>
|
||||
</div>
|
||||
|
||||
<footer>
|
||||
|
|
@ -93,4 +97,4 @@
|
|||
<a rel="me" href="https://squawk.social/@hexaitos"></a>
|
||||
</footer>
|
||||
</body>
|
||||
</html>
|
||||
</html>
|
||||
|
|
|
|||
|
|
@ -0,0 +1,91 @@
|
|||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
||||
<meta charset="UTF-8">
|
||||
<meta name="viewport" content="width=device-width,initial-scale=1">
|
||||
<meta name="description" content="">
|
||||
|
||||
<title>Asahi Linux on my base model M1 MacBook Air</title>
|
||||
|
||||
<link rel="stylesheet" href="/assets/css/styles.css">
|
||||
|
||||
</head>
|
||||
<body>
|
||||
<div class="menu">
|
||||
<a href="/index.html">Home</a>
|
||||
<a href="/blog.html">Blog</a>
|
||||
<a href="/art.html">Art</a>
|
||||
<a href="/refsheet.html">Ref sheet</a>
|
||||
<a href="/contact.html">Contact</a>
|
||||
</div>
|
||||
|
||||
<div class="main">
|
||||
<h1>Asahi Linux on my base model M1 MacBook Air</h1>
|
||||
<p style="text-align: right; font-style: italic;">This post was published on 19 Nov 2024</p>
|
||||
|
||||
<figure class="main">
|
||||
<a target="_blank" href="/assets/images/blog_posts/asahi_mba_m1/20241118-WE2A1144.jpg">
|
||||
<img src="/assets/images/blog_posts/asahi_mba_m1/thumbnails/20241118-WE2A1144_2000w.jpg" alt="An opened MacBook Air M1 standing on a table. It is showing the desktop of KDE Plasma 6 with the floating task bar at the bottom. The desktop background is a bird of prey." loading="lazy">
|
||||
</a>
|
||||
<figcaption>A photo of my MacBook Air running Asahi Linux with KDE Plasma 6</figcaption>
|
||||
</figure>
|
||||
|
||||
<p>A couple of years ago – still during my apprenticeship and also during the pandemic – I bought a base model M1 MacBook Air with some bonus money that I got for finishing an important (to my boss, at any rate) project at work and it’s been my main laptop ever since and one that I’ve been using basically daily ever since. However, the fact that I only got a base model has been a bit problematic and, thefore, I decided to upgrade to the new M4 MacBook Pro this year. This, then, leaves me with my still more than capable MacBook Air and I’ve been thinking about what to do with it. Then I remembered the fact that I’ve always been wanting to try out Asahi Linux; and that coupled with the <em>very</em> low power consumption of these M-series chips made me think that it would probably make for a really good low-powered server that still has enough <em>oomph</em> for more heavy workloads (definitely more than my <em>actual</em> server that’s running an Intel N100). And so that’s exactly what I did!</p>
|
||||
|
||||
<h2 id="installation">Installation</h2>
|
||||
<p>The installation of Asahi is pretty straightforward in general, but having only a base model Mac (with a measly 256 GB SSD) does pose a bit of a problem: Asahi cannot be installed as the sole operating system; instead; it can only be installed <em>alongside</em> macOS. This, then, means that even after completely erasing my previous Sonoma install and then <em>only</em> running the Asahi Linux installer afterwards, I only have about 150 GB of usable disk space on my Asahi partition. Now that’s not that bad or anything, but it’s definitely not a lot of disk space in today’s world.</p>
|
||||
|
||||
<p>Speaking of the installation, it’s pretty much as simple as running <code class="language-plaintext highlighter-rouge">curl https://alx.sh | sh</code> in a terminal window and following the on-screen prompts (insert disclaimer about running running shell scripts without checking their contents first here). If you’re even remotely familiar with the command line (and are able to read), then the installation shouldn’t pose any significant problems. Still, I would not recommend installing this on your main machine that you use for other things as well as I’m sure it can quite easily render your macOS install useless if something goes wrong.</p>
|
||||
|
||||
<p>During the installation process, you’ll be given the opportunity to set a new size for the macOS partition and a size for the to-be-created Asahi Linux partition. Additionally, you can choose between either Gnome or KDE (if I remember correctly) as your desktop environment. Then, after some rebooting and changing of Mac security features, you’ll be greeted by an installer that you’re going to be very familar with if you’ve ever installed a Linux distribution. There you’ll choose a timezone and a username and password. Afterwards you can reboot and you should be greeted by a login window.</p>
|
||||
|
||||
<p>As a side note: Asahi used to be based on Arch Linux but they appear to have moved over to Fedora and the Fedora-based Asahi Linux is, as far as I can tell, the only <q>official</q>. There are some <a href="https://github.com/AsahiLinux/docs/wiki/SW:Alternative-Distros">community-maintained flavours</a> but I haven’t tried out any of those yet; I am also guessing their installation process will differ quite significantly from that of the official Fedora-based version.</p>
|
||||
|
||||
<h2 id="the-desktop-experience">The desktop experience</h2>
|
||||
<p>I was honestly quite surprised at how <em>usable</em> it was in general, the only thing I still would very much like to see implemented is the ability to connect an external monitor through one of the USB-C ports of the MBA — that has (as of the publishing of this post) not yet been implemented. Other than that, however, everything worked pretty much as you’d expect: you can change the brightness of the keyboard and the screen; the trackpad works (and even has force feedback); the speakers work and sound as you would expect them to sound; the keys on the keyboard all work (including things like the media keys for playing/pausing videos or music); closing the lid makes the laptop reliably go to sleep and opening it wakes it up quite quickly … you get the idea. Even the battery life is as fantastic (KDE estimating 9-12 hours) despite this MacBook being 4-ish years old now. WiFi also works perfectly and at the the expected speed.</p>
|
||||
|
||||
<figure class="small-image">
|
||||
<a target="_blank" href="/assets/images/blog_posts/asahi_mba_m1/screenshot-fastfetch.png">
|
||||
<img src="/assets/images/blog_posts/asahi_mba_m1/thumbnails/screenshot-fastfetch_1200w.png" alt="A screenshot showing a full-screened terminal window and the output of the program fastfetch. The output shows some information about the machine, such as the processor and its speed, OS etc." loading="lazy">
|
||||
</a>
|
||||
<figcaption>Fastfetch running on the MacBook Air</figcaption>
|
||||
</figure>
|
||||
|
||||
<p>There are some strange behaviours here and there though. For example, whilst the trackpad does work, the palm rejection is, seemingly, non-existent, especially if you’re used to how well it works on macOS. Oh and speaking of the trackpad, it feels strangely laggy, almost as though it were connected through a terrible bluetooth connection (I’m pretty sensitive to input delay in general though, so you might not notice this at all). Also, you’re going to have to use regular Windows-style shortcuts, i. e. <code class="language-plaintext highlighter-rouge">⌃C</code> instead of <code class="language-plaintext highlighter-rouge">⌘C</code> for copying things, as an example.</p>
|
||||
|
||||
<p>Additionally, you might not have access to all the packages as, obviously, this isn’t an <code class="language-plaintext highlighter-rouge">x86_64</code>-based system but rather <code class="language-plaintext highlighter-rouge">aarch64</code>. I wanted to install Ruby on my system and I generally use <code class="language-plaintext highlighter-rouge">rbenv</code> to manage my Rubies. However, I first had a bit of trouble getting <code class="language-plaintext highlighter-rouge">rbenv</code> itself working and once I did, I had even <em>more</em> trouble getting it to actually compile Ruby 3.3.6 for me. At first, there were some problems with <code class="language-plaintext highlighter-rouge">openssl</code> that I managed to somehow fix by running <code class="language-plaintext highlighter-rouge">sudo dnf groupinstall "Development Tools"</code> but then it complained about <code class="language-plaintext highlighter-rouge">libffi</code> apparently missing (even though it wasn’t as far as I could tell) so I just ended up using <code class="language-plaintext highlighter-rouge">rvm</code> instead – that could compile Ruby 3.6.6 without any problems.</p>
|
||||
|
||||
<p>Most of the Flatpaks that I’ve tried worked without any problems except for the Flatpak for Telegram for some reason, but that might’ve just been my doing something wrong. LibreWolf, the browser I generally use on Linux, works fine and runs as expected, though also through a Flatpak. Tokodon, KDE’s own Mastodon / Fediverse client, also works quite well. The GPU, apparently, <em>also</em> works but I haven’t really tried that out yet. Watching YouTube videos, even at 4K, was not a problem however and I couldn’t detect any dropped frames.</p>
|
||||
|
||||
<p>A colleague of mine – who is also quite interested in both ARM and RISC-V – has told me about Box64 which allows you to run normal <code class="language-plaintext highlighter-rouge">x86_64</code>-based programs on an ARM-based processor. I haven’t yet tried this out myself but I definitely want to try it out and see if I can get some non-native programs running through that.</p>
|
||||
|
||||
<h2 id="and-as-a-server">And as a server?</h2>
|
||||
|
||||
<figure class="small-image">
|
||||
<a target="_blank" href="/assets/images/blog_posts/asahi_mba_m1/screenshot-sensors.png">
|
||||
<img src="/assets/images/blog_posts/asahi_mba_m1/thumbnails/screenshot-sensors_1200w.png" alt="A screenshot showing a terminal window and the output of the sensors command. It is showing temperatures, voltages and a wattage." loading="lazy">
|
||||
</a>
|
||||
<figcaption>The output of lm-sensors</figcaption>
|
||||
</figure>
|
||||
|
||||
<p>I still haven’t done too much with regards to trying it out as a server, but I still feel like it should work quite well as long as all the software also works. I <em>really</em> wanted to get something like Proxmox or maybe even just YunoHost working, but I haven’t really found a way to do that yet. One thing I already did was change the charging limit from <code class="language-plaintext highlighter-rouge">100%</code> down to <code class="language-plaintext highlighter-rouge">80%</code>. I had to do this through the console by running <code class="language-plaintext highlighter-rouge">echo 80 |sudo tee /sys/class/power_supply/macsmc-battery/charge_control_end_threshold</code> in the terminal as changing the charging limit through KDE’s GUI settings did not seem to work.</p>
|
||||
|
||||
<p>I also installed <code class="language-plaintext highlighter-rouge">lm-sensors</code>. I did that mostly to see the temperatures at which the computer was running, but I was very surprised to see that it also provided me with a nice way of seeing how much power it was using at a given time. This showed me that the power usage even with the screen turned on was rather low! I, therefore, enabled ssh and ssh’d into the machine to see what its power usage would be when the screen was completely turned off; and I was very surprised to see that the idle power consumption appears to be around 1-2 W with the screen turned off. Now that’s <em>really</em> low value and something that you would <em>probably</em> have a hard time noticing on your monthly power bill.</p>
|
||||
|
||||
<p>If I were to actually start using this machine as a server, I would probably install a more minimal version of Asahi (probably without any DE whatsoever) and I would also need to get some sort of USB-C to ethernet adapater and <em>hope</em> that it works; though depending on what exactly I’ll end up using the server for, a decent WiFi connection might not be all that problematic either.</p>
|
||||
|
||||
<h2 id="conclusion">Conclusion</h2>
|
||||
<p>I was pleasantly surprised to see how well it works just out of the box and will definitely be keeping Asahi on my MBA. I’ll try out some more stuff, especially in regards to running it as a server or I might just keep it around as a nice Linux machine in general.</p>
|
||||
|
||||
<div class="clearfix"></div>
|
||||
</div>
|
||||
|
||||
<footer>
|
||||
<p>2024 - 2024 hexaitos.com</p>
|
||||
<p>Made with Jekyll</p>
|
||||
<a rel="me" href="https://squawk.social/@hexaitos"></a>
|
||||
</footer>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,6 +1,8 @@
|
|||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
||||
<meta charset="UTF-8">
|
||||
<meta name="viewport" content="width=device-width,initial-scale=1">
|
||||
<meta name="description" content="This page contains art that I have comissioned of Hexaitos.">
|
||||
|
|
@ -10,6 +12,7 @@
|
|||
<link rel="preload" as="style" href="/assets/css/styles.css">
|
||||
<link rel="stylesheet" href="/assets/css/styles.css">
|
||||
|
||||
</head>
|
||||
<body>
|
||||
<div class="menu">
|
||||
<a href="/index.html">Home</a>
|
||||
|
|
@ -27,7 +30,7 @@
|
|||
<div class="responsive">
|
||||
<div class="gallery">
|
||||
<a target="_blank" href="/assets/images/Hexaitos/FaultyArts/hexaitos_icon.png">
|
||||
<img src="/assets/images/Hexaitos/FaultyArts/hexaitos_icon_small.png" alt="A simple shaded icon of an anthropomorphic bateleur eagle" width="600" height="400">
|
||||
<img src="/assets/images/Hexaitos/FaultyArts/hexaitos_icon_small.png" alt="A simple shaded icon of an anthropomorphic bateleur eagle" width="600" height="400" loading="lazy">
|
||||
</a>
|
||||
<div class="desc">Hexaitos bonus icon – FaultyArts</div>
|
||||
</div>
|
||||
|
|
@ -36,7 +39,7 @@
|
|||
<div class="responsive">
|
||||
<div class="gallery">
|
||||
<a target="_blank" href="/assets/images/Hexaitos/Jagal/huevember_2024.jpg">
|
||||
<img src="/assets/images/Hexaitos/Jagal/huevember_2024_thumb.jpg" alt="A half-body painting of an anthropomorphic bateleur eagle walking through a field." width="600" height="400">
|
||||
<img src="/assets/images/Hexaitos/Jagal/huevember_2024_thumb.jpg" alt="A half-body painting of an anthropomorphic bateleur eagle walking through a field." width="600" height="400" loading="lazy">
|
||||
</a>
|
||||
<div class="desc">Huevember 2024 (Day 2) – Jagal</div>
|
||||
</div>
|
||||
|
|
@ -45,7 +48,7 @@
|
|||
<div class="responsive">
|
||||
<div class="gallery">
|
||||
<a target="_blank" href="/assets/images/Hexaitos/FaultyArts/hexaitos_bateleur.png">
|
||||
<img src="/assets/images/Hexaitos/FaultyArts/hexaitos_bateleur_thumb.jpg" alt="A reference sheet for an anthropomorphic bateleur eagle" width="600" height="400">
|
||||
<img src="/assets/images/Hexaitos/FaultyArts/hexaitos_bateleur_thumb.jpg" alt="A reference sheet for an anthropomorphic bateleur eagle" width="600" height="400" loading="lazy">
|
||||
</a>
|
||||
<div class="desc">Hexaitos ref sheet – FaultyArts</div>
|
||||
</div>
|
||||
|
|
@ -54,7 +57,7 @@
|
|||
<div class="responsive">
|
||||
<div class="gallery">
|
||||
<a target="_blank" href="/assets/images/Hexaitos/CZGoldEdition/spookyHexaitos_icon.png">
|
||||
<img src="/assets/images/Hexaitos/CZGoldEdition/spookyHexaitos_icon_thumb.jpg" alt="A spooky icon of an anthropomorphic bateleur eagle" width="600" height="400">
|
||||
<img src="/assets/images/Hexaitos/CZGoldEdition/spookyHexaitos_icon_thumb.jpg" alt="A spooky icon of an anthropomorphic bateleur eagle" width="600" height="400" loading="lazy">
|
||||
</a>
|
||||
<div class="desc">Spooky icon portrait 2024 – CZGoldEdition</div>
|
||||
</div>
|
||||
|
|
@ -71,4 +74,4 @@
|
|||
<a rel="me" href="https://squawk.social/@hexaitos"></a>
|
||||
</footer>
|
||||
</body>
|
||||
</html>
|
||||
</html>
|
||||
|
|
|
|||
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
Binary file not shown.
|
After Width: | Height: | Size: 3.8 MiB |
Binary file not shown.
|
After Width: | Height: | Size: 374 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 293 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 522 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 238 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 184 KiB |
|
|
@ -24,16 +24,21 @@
|
|||
|
||||
<ul>
|
||||
|
||||
<li>
|
||||
<a href="/2024/11/19/asahi-on-m1-mba.html">Asahi Linux on my base model M1 MacBook Air (19 Nov 2024)</a>
|
||||
<p>In this blog post I will be taking a quick look at Asahi Linux and my opinions on it so far. I have installed it on my base-model M1 MacBook Air and am planning of perhaps turning it into a very low-powered yet still powerful server.</p>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<a href="/2024/10/29/hosting_at_home.html">Hosting my websites at home but I only have a public IPv6 subnet (29 Oct 2024)</a>
|
||||
<p>I wanted to write a small series of blog posts detailing how I made it so that my websites that are hosted at the server in my apartment (which only has a public IPv6 address) can be accessed from the Internet even if you’re in an IPv4-only network and I wanted to start by writing a post about how I delegated an IPv6 prefix to my OPNsense installation from my FRITZ!Box. (Un)fortunately, just as I finished writing it, I found out that the official (I think) <a href="https://docs.opnsense.org/manual/how-tos/ipv6_fb.html">OPNsense documentation</a> has the <em>exact</em> thing I wrote about documented already, so there’s really no point in my posting my own version that is almost literally the same thing.</p>
|
||||
|
||||
<p><p>I wanted to write a small series of blog posts detailing how I made it so that my websites that are hosted at the server in my apartment (which only has a public IPv6 address) can be accessed from the Internet even if you’re in an IPv4-only network and I wanted to start by writing a post about how I delegated an IPv6 prefix to my OPNsense installation from my FRITZ!Box. (Un)fortunately, just as I finished writing it, I found out that the official (I think) <a href="https://docs.opnsense.org/manual/how-tos/ipv6_fb.html">OPNsense documentation</a> has the <em>exact</em> thing I wrote about documented already, so there’s really no point in my posting my own version that is almost literally the same thing.</p>
|
||||
</p>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<a href="/2024/09/30/first_blog_post.html">My first blog post (30 Sep 2024)</a>
|
||||
<p>Hello everyone! This is my first blog post, mostly just to try out how everything works.</p>
|
||||
|
||||
<p><p>Hello everyone! This is my first blog post, mostly just to try out how everything works.</p>
|
||||
</p>
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
|
|
|
|||
|
|
@ -1,4 +1,56 @@
|
|||
<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="4.3.4">Jekyll</generator><link href="https://hexaitos.com/feed.xml" rel="self" type="application/atom+xml" /><link href="https://hexaitos.com/" rel="alternate" type="text/html" /><updated>2024-11-12T22:01:42+01:00</updated><id>https://hexaitos.com/feed.xml</id><title type="html">Hexaitos’ Personal Website</title><entry><title type="html">Hosting my websites at home but I only have a public IPv6 subnet</title><link href="https://hexaitos.com/2024/10/29/hosting_at_home.html" rel="alternate" type="text/html" title="Hosting my websites at home but I only have a public IPv6 subnet" /><published>2024-10-29T00:00:00+01:00</published><updated>2024-10-29T00:00:00+01:00</updated><id>https://hexaitos.com/2024/10/29/hosting_at_home</id><content type="html" xml:base="https://hexaitos.com/2024/10/29/hosting_at_home.html"><![CDATA[<p>I wanted to write a small series of blog posts detailing how I made it so that my websites that are hosted at the server in my apartment (which only has a public IPv6 address) can be accessed from the Internet even if you’re in an IPv4-only network and I wanted to start by writing a post about how I delegated an IPv6 prefix to my OPNsense installation from my FRITZ!Box. (Un)fortunately, just as I finished writing it, I found out that the official (I think) <a href="https://docs.opnsense.org/manual/how-tos/ipv6_fb.html">OPNsense documentation</a> has the <em>exact</em> thing I wrote about documented already, so there’s really no point in my posting my own version that is almost literally the same thing.</p>
|
||||
<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="4.3.4">Jekyll</generator><link href="https://hexaitos.com/feed.xml" rel="self" type="application/atom+xml" /><link href="https://hexaitos.com/" rel="alternate" type="text/html" /><updated>2024-11-19T00:04:42+01:00</updated><id>https://hexaitos.com/feed.xml</id><title type="html">Hexaitos’ Personal Website</title><entry><title type="html">Asahi Linux on my base model M1 MacBook Air</title><link href="https://hexaitos.com/2024/11/19/asahi-on-m1-mba.html" rel="alternate" type="text/html" title="Asahi Linux on my base model M1 MacBook Air" /><published>2024-11-19T00:00:00+01:00</published><updated>2024-11-19T00:00:00+01:00</updated><id>https://hexaitos.com/2024/11/19/asahi-on-m1-mba</id><content type="html" xml:base="https://hexaitos.com/2024/11/19/asahi-on-m1-mba.html"><![CDATA[<figure class="main">
|
||||
<a target="_blank" href="/assets/images/blog_posts/asahi_mba_m1/20241118-WE2A1144.jpg">
|
||||
<img src="/assets/images/blog_posts/asahi_mba_m1/thumbnails/20241118-WE2A1144_2000w.jpg" alt="An opened MacBook Air M1 standing on a table. It is showing the desktop of KDE Plasma 6 with the floating task bar at the bottom. The desktop background is a bird of prey." />
|
||||
</a>
|
||||
<figcaption>A photo of my MacBook Air running Asahi Linux with KDE Plasma 6</figcaption>
|
||||
</figure>
|
||||
|
||||
<p>A couple of years ago – still during my apprenticeship and also during the pandemic – I bought a base model M1 MacBook Air with some bonus money that I got for finishing an important (to my boss, at any rate) project at work and it’s been my main laptop ever since and one that I’ve been using basically daily ever since. However, the fact that I only got a base model has been a bit problematic and, thefore, I decided to upgrade to the new M4 MacBook Pro this year. This, then, leaves me with my still more than capable MacBook Air and I’ve been thinking about what to do with it. Then I remembered the fact that I’ve always been wanting to try out Asahi Linux; and that coupled with the <em>very</em> low power consumption of these M-series chips made me think that it would probably make for a really good low-powered server that still has enough <em>oomph</em> for more heavy workloads (definitely more than my <em>actual</em> server that’s running an Intel N100). And so that’s exactly what I did!</p>
|
||||
|
||||
<h2 id="installation">Installation</h2>
|
||||
<p>The installation of Asahi is pretty straightforward in general, but having only a base model Mac (with a measly 256 GB SSD) does pose a bit of a problem: Asahi cannot be installed as the sole operating system; instead; it can only be installed <em>alongside</em> macOS. This, then, means that even after completely erasing my previous Sonoma install and then <em>only</em> running the Asahi Linux installer afterwards, I only have about 150 GB of usable disk space on my Asahi partition. Now that’s not that bad or anything, but it’s definitely not a lot of disk space in today’s world.</p>
|
||||
|
||||
<p>Speaking of the installation, it’s pretty much as simple as running <code class="language-plaintext highlighter-rouge">curl https://alx.sh | sh</code> in a terminal window and following the on-screen prompts (insert disclaimer about running running shell scripts without checking their contents first here). If you’re even remotely familiar with the command line (and are able to read), then the installation shouldn’t pose any significant problems. Still, I would not recommend installing this on your main machine that you use for other things as well as I’m sure it can quite easily render your macOS install useless if something goes wrong.</p>
|
||||
|
||||
<p>During the installation process, you’ll be given the opportunity to set a new size for the macOS partition and a size for the to-be-created Asahi Linux partition. Additionally, you can choose between either Gnome or KDE (if I remember correctly) as your desktop environment. Then, after some rebooting and changing of Mac security features, you’ll be greeted by an installer that you’re going to be very familar with if you’ve ever installed a Linux distribution. There you’ll choose a timezone and a username and password. Afterwards you can reboot and you should be greeted by a login window.</p>
|
||||
|
||||
<p>As a side note: Asahi used to be based on Arch Linux but they appear to have moved over to Fedora and the Fedora-based Asahi Linux is, as far as I can tell, the only <q>official</q>. There are some <a href="https://github.com/AsahiLinux/docs/wiki/SW:Alternative-Distros">community-maintained flavours</a> but I haven’t tried out any of those yet; I am also guessing their installation process will differ quite significantly from that of the official Fedora-based version.</p>
|
||||
|
||||
<h2 id="the-desktop-experience">The desktop experience</h2>
|
||||
<p>I was honestly quite surprised at how <em>usable</em> it was in general, the only thing I still would very much like to see implemented is the ability to connect an external monitor through one of the USB-C ports of the MBA — that has (as of the publishing of this post) not yet been implemented. Other than that, however, everything worked pretty much as you’d expect: you can change the brightness of the keyboard and the screen; the trackpad works (and even has force feedback); the speakers work and sound as you would expect them to sound; the keys on the keyboard all work (including things like the media keys for playing/pausing videos or music); closing the lid makes the laptop reliably go to sleep and opening it wakes it up quite quickly … you get the idea. Even the battery life is as fantastic (KDE estimating 9-12 hours) despite this MacBook being 4-ish years old now. WiFi also works perfectly and at the the expected speed.</p>
|
||||
|
||||
<figure class="small-image">
|
||||
<a target="_blank" href="/assets/images/blog_posts/asahi_mba_m1/screenshot-fastfetch.png">
|
||||
<img src="/assets/images/blog_posts/asahi_mba_m1/thumbnails/screenshot-fastfetch_1200w.png" alt="A screenshot showing a full-screened terminal window and the output of the program fastfetch. The output shows some information about the machine, such as the processor and its speed, OS etc." />
|
||||
</a>
|
||||
<figcaption>Fastfetch running on the MacBook Air</figcaption>
|
||||
</figure>
|
||||
|
||||
<p>There are some strange behaviours here and there though. For example, whilst the trackpad does work, the palm rejection is, seemingly, non-existent, especially if you’re used to how well it works on macOS. Oh and speaking of the trackpad, it feels strangely laggy, almost as though it were connected through a terrible bluetooth connection (I’m pretty sensitive to input delay in general though, so you might not notice this at all). Also, you’re going to have to use regular Windows-style shortcuts, i. e. <code class="language-plaintext highlighter-rouge">⌃C</code> instead of <code class="language-plaintext highlighter-rouge">⌘C</code> for copying things, as an example.</p>
|
||||
|
||||
<p>Additionally, you might not have access to all the packages as, obviously, this isn’t an <code class="language-plaintext highlighter-rouge">x86_64</code>-based system but rather <code class="language-plaintext highlighter-rouge">aarch64</code>. I wanted to install Ruby on my system and I generally use <code class="language-plaintext highlighter-rouge">rbenv</code> to manage my Rubies. However, I first had a bit of trouble getting <code class="language-plaintext highlighter-rouge">rbenv</code> itself working and once I did, I had even <em>more</em> trouble getting it to actually compile Ruby 3.3.6 for me. At first, there were some problems with <code class="language-plaintext highlighter-rouge">openssl</code> that I managed to somehow fix by running <code class="language-plaintext highlighter-rouge">sudo dnf groupinstall "Development Tools"</code> but then it complained about <code class="language-plaintext highlighter-rouge">libffi</code> apparently missing (even though it wasn’t as far as I could tell) so I just ended up using <code class="language-plaintext highlighter-rouge">rvm</code> instead – that could compile Ruby 3.6.6 without any problems.</p>
|
||||
|
||||
<p>Most of the Flatpaks that I’ve tried worked without any problems except for the Flatpak for Telegram for some reason, but that might’ve just been my doing something wrong. LibreWolf, the browser I generally use on Linux, works fine and runs as expected, though also through a Flatpak. Tokodon, KDE’s own Mastodon / Fediverse client, also works quite well. The GPU, apparently, <em>also</em> works but I haven’t really tried that out yet. Watching YouTube videos, even at 4K, was not a problem however and I couldn’t detect any dropped frames.</p>
|
||||
|
||||
<p>A colleague of mine – who is also quite interested in both ARM and RISC-V – has told me about Box64 which allows you to run normal <code class="language-plaintext highlighter-rouge">x86_64</code>-based programs on an ARM-based processor. I haven’t yet tried this out myself but I definitely want to try it out and see if I can get some non-native programs running through that.</p>
|
||||
|
||||
<h2 id="and-as-a-server">And as a server?</h2>
|
||||
|
||||
<figure class="small-image">
|
||||
<a target="_blank" href="/assets/images/blog_posts/asahi_mba_m1/screenshot-sensors.png">
|
||||
<img src="/assets/images/blog_posts/asahi_mba_m1/thumbnails/screenshot-sensors_1200w.png" alt="A screenshot showing a terminal window and the output of the sensors command. It is showing temperatures, voltages and a wattage." />
|
||||
</a>
|
||||
<figcaption>The output of lm-sensors</figcaption>
|
||||
</figure>
|
||||
|
||||
<p>I still haven’t done too much with regards to trying it out as a server, but I still feel like it should work quite well as long as all the software also works. I <em>really</em> wanted to get something like Proxmox or maybe even just YunoHost working, but I haven’t really found a way to do that yet. One thing I already did was change the charging limit from <code class="language-plaintext highlighter-rouge">100%</code> down to <code class="language-plaintext highlighter-rouge">80%</code>. I had to do this through the console by running <code class="language-plaintext highlighter-rouge">echo 80 |sudo tee /sys/class/power_supply/macsmc-battery/charge_control_end_threshold</code> in the terminal as changing the charging limit through KDE’s GUI settings did not seem to work.</p>
|
||||
|
||||
<p>I also installed <code class="language-plaintext highlighter-rouge">lm-sensors</code>. I did that mostly to see the temperatures at which the computer was running, but I was very surprised to see that it also provided me with a nice way of seeing how much power it was using at a given time. This showed me that the power usage even with the screen turned on was rather low! I, therefore, enabled ssh and ssh’d into the machine to see what its power usage would be when the screen was completely turned off; and I was very surprised to see that the idle power consumption appears to be around 1-2 W with the screen turned off. Now that’s <em>really</em> low value and something that you would <em>probably</em> have a hard time noticing on your monthly power bill.</p>
|
||||
|
||||
<p>If I were to actually start using this machine as a server, I would probably install a more minimal version of Asahi (probably without any DE whatsoever) and I would also need to get some sort of USB-C to ethernet adapater and <em>hope</em> that it works; though depending on what exactly I’ll end up using the server for, a decent WiFi connection might not be all that problematic either.</p>
|
||||
|
||||
<h2 id="conclusion">Conclusion</h2>
|
||||
<p>I was pleasantly surprised to see how well it works just out of the box and will definitely be keeping Asahi on my MBA. I’ll try out some more stuff, especially in regards to running it as a server or I might just keep it around as a nice Linux machine in general.</p>]]></content><author><name>hexaitos</name></author><summary type="html"><![CDATA[In this blog post I will be taking a quick look at Asahi Linux and my opinions on it so far. I have installed it on my base-model M1 MacBook Air and am planning of perhaps turning it into a very low-powered yet still powerful server.]]></summary></entry><entry><title type="html">Hosting my websites at home but I only have a public IPv6 subnet</title><link href="https://hexaitos.com/2024/10/29/hosting_at_home.html" rel="alternate" type="text/html" title="Hosting my websites at home but I only have a public IPv6 subnet" /><published>2024-10-29T00:00:00+01:00</published><updated>2024-10-29T00:00:00+01:00</updated><id>https://hexaitos.com/2024/10/29/hosting_at_home</id><content type="html" xml:base="https://hexaitos.com/2024/10/29/hosting_at_home.html"><
Binary file not shown.
|
After Width: | Height: | Size: 3.8 MiB |
Binary file not shown.
|
After Width: | Height: | Size: 374 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 293 KiB |
|
|
@ -9,7 +9,7 @@ description: "Hexaitos’ blog has posts on computers, languages and photography
|
|||
{% for post in site.posts %}
|
||||
<li>
|
||||
<a href="{{ post.url }}">{{ post.title }} ({{ post.date | date_to_string }})</a>
|
||||
{{ post.excerpt }}
|
||||
<p>{{ post.excerpt }}</p>
|
||||
</li>
|
||||
{% endfor %}
|
||||
</ul>
|
||||
Loading…
Reference in New Issue