This may seem to some of you like a blast from a long forgotten past but that’s what an Enterprise world often looks like: I’ve been seeing scripting that creates a custom Linux installation ISO from given public images, adds extra software repositories, install automation, provisioning for delegating to a dedicated config management tool (Puppet,… Continue reading Recreating ISOs that boot from both DVD and mass storage such as USB sticks and in both legacy BIOS and UEFI environments
In a previous post I described the Mikrotik hAP lite (RB941-2nD-TC) and its RouterOS and already suggested that I prefer to run OpenWrt on it. Because Mikrotik routers behave a bit different than the usual TP-Link, GL.iNet etc. devices and because there were some pitfalls I had to master myself, here’s some advice to keep… Continue reading Bringing OpenWrt to the Mikrotik hAP lite (RB941-2nD-TC)
In a small series on rspamd configuration I did back in August last year I had a diagram illustrating the configuration file structure of the then-current rspamd version.
While working on my python-netsnmpagent project, I regularly smilint the MIBs used for conformance with the SMI spec to ensure they are proper MIBs.
More than once, a device rushed through my timeline that advertised itself through its minimal dimensions, its price and its OpenWrt capability: the GL.iNet AR-150. I now finally got around to have a use case, so I ordered one and had a closer look.
So far I’ve been an avid user of TP-Link gear when it comes to routers, for their price and feature set (e.g. USB ports) but most of all because you can rather easily run OpenWrt on them. A few times, however, GL.iNet has been rushing through my timeline.
Imagine you have a system to which you can only SSH inbound but which is unable to reach any host on the Internet outside the local network. For instance, you might have tightened down network access to secure a local CA. Or, like me, you have a Raspberry Pi that you carried around with you… Continue reading Using a reverse SSH tunnel to provide an isolated system such as a Raspberry Pi with network access (well, HTTP)
Here’s another tip related to AutoYast and scripts such as pre-install scripts, indirectly related to the previous post on error reporting.
After the opener on Retaining/reusing existing partitions and the followup on Partitioning that works on both real hardware and inside virtual machines, this post looks at error reporting in pre-install scripts.
Continuing a small series on Autoyast tips and tricks after the first post, Retaining/Reusing existing partitions, let’s look at another use case for dynamically modifying the Autoyast profile.