#YachaBlog
Last time I am working on a new Sophie update. The main purpose of it is to cover all of the problematic places with the current Sophie: 1. Typing system - the python's duck-typing (🦆) is pretty much okay and mostly reliable, but by default, it is not anyhow…
Talking about ASS, I had the idea of parsing arguments like that for more than 3 years and I'm finally happy there's something similar to it we're having now.
Here you can see an example of what ASS is able to do.
Here you can see an example of what ASS is able to do.
💩1
Regarding the bw.owo.family status.
Today it was re-provisioned, as I won't be able to restore the OS it was powered on for several reasons.
The general issue is that I lost root access to it.
That happened when I initially provisioned the VM of Bitwarden, I had to change the default Linux credentials, like I'm always doing, but due to password manager was, obviously, down, I had to note the passwords somewhere else and forgot them.
My usual setups also include SSH keys, which were also there, but due to my trying to log in, I was blocked by the tallow, so I had no way to login into the VM in any possible usual way.
Resetting root password on Linux.
The OS I'm using is openSUSE MicroOS which has an inbuilt btrfs snapshots file system, where every update creates a snapshot which contains changes over the previous one. The /etc is also a 2 directories overlay that contains changes over the last made snapshot. This mounting system works awesome when the system is unable to boot and requires a rollback, but not when you want to change the last snapshot. Why? Usually, you'd boot it with init=/bin/sh, where you had no systemd, and so on no D-Bus, which is required for a snapper, a SUSE tool to manage snapshots. You also cannot change /etc directory directly in the last snapshot, since it'll be overwritten by an overlay.
How it was restored.
By simply copying the files from a /var volume (which is a dedicated partition) and re-installing the OS.
What are the findings?
Do not lose access, obviously. The other thing is making a workaround to login into it.
The new OrangeFox's Virtual Machines now have LDAP access, which will settle the current issue.
The current state.
bw.owo.family instance is on, has all the user's data, and now fixes the issues with the latest Bitwarden apps.
Moreover, now not the OS only, but also the Bitwarden server is now updated automatically, thanks to podman-auto-update.
----
The next issue that was fixed is the unstable work of mail.orangefox.tech. The issue is basically with insufficient RAM, the mail server was moved to a more suitable place. Moreover, it now also does self-update itself.
Today it was re-provisioned, as I won't be able to restore the OS it was powered on for several reasons.
The general issue is that I lost root access to it.
That happened when I initially provisioned the VM of Bitwarden, I had to change the default Linux credentials, like I'm always doing, but due to password manager was, obviously, down, I had to note the passwords somewhere else and forgot them.
My usual setups also include SSH keys, which were also there, but due to my trying to log in, I was blocked by the tallow, so I had no way to login into the VM in any possible usual way.
Resetting root password on Linux.
The OS I'm using is openSUSE MicroOS which has an inbuilt btrfs snapshots file system, where every update creates a snapshot which contains changes over the previous one. The /etc is also a 2 directories overlay that contains changes over the last made snapshot. This mounting system works awesome when the system is unable to boot and requires a rollback, but not when you want to change the last snapshot. Why? Usually, you'd boot it with init=/bin/sh, where you had no systemd, and so on no D-Bus, which is required for a snapper, a SUSE tool to manage snapshots. You also cannot change /etc directory directly in the last snapshot, since it'll be overwritten by an overlay.
How it was restored.
By simply copying the files from a /var volume (which is a dedicated partition) and re-installing the OS.
What are the findings?
Do not lose access, obviously. The other thing is making a workaround to login into it.
The new OrangeFox's Virtual Machines now have LDAP access, which will settle the current issue.
The current state.
bw.owo.family instance is on, has all the user's data, and now fixes the issues with the latest Bitwarden apps.
Moreover, now not the OS only, but also the Bitwarden server is now updated automatically, thanks to podman-auto-update.
----
The next issue that was fixed is the unstable work of mail.orangefox.tech. The issue is basically with insufficient RAM, the mail server was moved to a more suitable place. Moreover, it now also does self-update itself.
💩2
Thanks @unfoxo and @h_2_o0 for their suggestions.
I have already fixed the CloudFlare CDN cache issue with orangefox.download. So the server will have less requests.
I have already fixed the CloudFlare CDN cache issue with orangefox.download. So the server will have less requests.
👍1💩1
I just found that orangefox.download// is not working. So yeah with double slash. Gonna fix that soon.
OrangeFox Recovery Downloads
Download OrangeFox Recovery
Download OrangeFox Recovery for your Android device
💩1
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Praesent auctor eu enim at vehicula. Vivamus a ipsum velit. Aliquam eu metus a enim consectetur tristique vitae id neque. Pellentesque eros massa, maximus a augue quis, luctus aliquet nulla. Nullam vel condimentum dolor. In vel ipsum id arcu venenatis suscipit. Fusce nunc massa, mattis ut odio ut, varius elementum massa. Suspendisse vel metus non nulla tincidunt congue. Curabitur venenatis mauris velit, id pellentesque dolor vestibulum eget. Nulla auctor tempor finibus. Maecenas elit magna, facilisis cursus finibus ut, porta sed nibh.
💩2
if anyone wonders, that's a native windows runned on the phone, and it even feels responsive. The same thing I did before, trying to boot Windows 10 on a raspberry pi
💩3👎2