digitalcourage.social

Camelia :alpine: :tranarchy_a_nonbinary: 🇵🇸I am now using <a href="https://fedi.camelia.dev/tags/alpinelinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#AlpineLinux</a> on my personal computer! :alpine:

https://purl.org/rzr#<a href="https://wiki.alpinelinux.org/wiki/Requirements#" rel="nofollow noopener" translate="no" target="_blank">https://wiki.alpinelinux.org/wiki/Requirements#</a> <a href="https://mastodon.social/tags/XcpNg" class="mention hashtag" rel="nofollow noopener" target="_blank">#XcpNg</a> can boot <a href="https://mastodon.social/tags/AlpineLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#AlpineLinux</a> (From <a href="https://mastodon.social/tags/NetbootXyz" class="mention hashtag" rel="nofollow noopener" target="_blank">#NetbootXyz</a> ram) since it only requires 128Mto install , probably more would work using the 32 bits versions

DajeLinux :linux: :fedilug:Sperimentare Alpine Linux su un vecchio Chromebook convertito a Linux è stato piuttosto "illuminante". Probabilmente seguiranno ulteriori articoli in merito; ma intanto iniziamo a saggiare le caratteristiche principali e lo script per l'installazione di quello che io ho chiamato in modo provocatorio "Il sistema operativo universale".<a href="https://dajelinux.it/archivio/alpine-linux-1" rel="nofollow noopener" translate="no" target="_blank">https://dajelinux.it/archivio/alpine-linux-1</a><a href="https://mastodon.uno/@linux" class="u-url mention" rel="nofollow noopener" target="_blank">@linux</a> <a href="https://diggita.com/c/linux" class="u-url mention" rel="nofollow noopener" target="_blank">@linux@diggita.com</a> <a href="https://diggita.com/c/opensource" class="u-url mention" rel="nofollow noopener" target="_blank">@opensource</a> <a href="https://diggita.com/c/tecnologia" class="u-url mention" rel="nofollow noopener" target="_blank">@tecnologia</a> <a href="https://mastodon.uno/tags/gnu" class="mention hashtag" rel="nofollow noopener" target="_blank">#gnu</a> <a href="https://mastodon.uno/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://mastodon.uno/tags/unolinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#unolinux</a> <a href="https://mastodon.uno/tags/unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#unix</a> <a href="https://mastodon.uno/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a> <a href="https://mastodon.uno/tags/foss" class="mention hashtag" rel="nofollow noopener" target="_blank">#foss</a> <a href="https://mastodon.uno/tags/floss" class="mention hashtag" rel="nofollow noopener" target="_blank">#floss</a> <a href="https://mastodon.uno/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#homelab</a> <a href="https://mastodon.uno/tags/alpinelinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#alpinelinux</a>

Camelia :alpine: :tranarchy_a_nonbinary: 🇵🇸I finally took some time to upgrade my <a href="https://fedi.camelia.dev/tags/alpinelinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#AlpineLinux</a> VPS :alpine: and everything went very smoothly! (I am not used to major upgrades because I prefer using rolling releases, but obviously for my VPS I wanted something a little lower-maintenance).I had to take ~10 min after it, to go through configs that had newer versions, and I had to upgrade my postgresql cluster as well. But that was it.I was honestly expecting that something would not work anymore after the upgrade but it was not the case! everything works wonderfully fine!

LinuxNews.deErstes Release: Wayback 0.1 erschienen <a href="https://linuxnews.de/wayback-0-1-erschienen/" rel="nofollow noopener" translate="no" target="_blank">https://linuxnews.de/wayback-0-1-erschienen/</a> <a href="https://social.anoxinon.de/tags/xorg" class="mention hashtag" rel="nofollow noopener" target="_blank">#xorg</a> <a href="https://social.anoxinon.de/tags/wayland" class="mention hashtag" rel="nofollow noopener" target="_blank">#wayland</a> <a href="https://social.anoxinon.de/tags/wayback" class="mention hashtag" rel="nofollow noopener" target="_blank">#wayback</a> <a href="https://social.anoxinon.de/tags/xwayland" class="mention hashtag" rel="nofollow noopener" target="_blank">#xwayland</a> <a href="https://social.anoxinon.de/tags/wlroots" class="mention hashtag" rel="nofollow noopener" target="_blank">#wlroots</a> <a href="https://social.anoxinon.de/tags/alpinelinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#alpinelinux</a> <a href="https://social.anoxinon.de/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a>

Thomas LiskeI got my HackberryPi CM5 <a href="https://github.com/ZitaoTech/HackberryPiCM5" rel="nofollow noopener" translate="no" target="_blank">https://github.com/ZitaoTech/HackberryPiCM5</a> for some time and the builtin display didn't work with <a href="https://ibh.social/tags/AlpineLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#AlpineLinux</a> 3.22.0 out of the box.With the today's <a href="https://fosstodon.org/@alpinelinux" class="u-url mention" rel="nofollow noopener" target="_blank">@alpinelinux</a> 3.22.1 point release the linux-rpi kernel package was bumped to 6.12.38 fixing the broken hyperpixel overlay <a href="https://github.com/raspberrypi/linux/issues/6878" rel="nofollow noopener" translate="no" target="_blank">https://github.com/raspberrypi/linux/issues/6878</a> 🥳

Debby🌟 Exciting News for X11 Enthusiasts! 🌟Have you heard about The Wayback Project? It's an innovative initiative aiming to save classic X11 desktops from becoming obsolete with the rise of Wayland. 💻The Wayback Project introduces an experimental Wayland compositor that hosts a "rootful" Xwayland instance. This means your favorite X11 desktop environments like Cinnamon, Xfce, LXDE, and even W3 can run seamlessly on Wayland 🚀Created by the talented Alpine Linux developer Ariadne Conill, this project is a game-changer for those of us who still rely on legacy desktops and apps. Early builds are already up and running, bugs and all, and the project is actively seeking testers and contributors to help refine and improve it.Check out this video to learn more: The Wayback Project wants to save X11 Desktops from the coming of Wayland <a href="https://youtu.be/6rEJI5oro8M" rel="nofollow noopener" translate="no" target="_blank">https://youtu.be/6rEJI5oro8M</a> Thanks to <a href="https://mast.linuxgamecast.com/@Jill_linuxgirl" class="u-url mention" rel="nofollow noopener" target="_blank">@Jill_linuxgirl</a> :blob_cat_heart: <a href="https://hear-me.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://hear-me.social/tags/Wayland" class="mention hashtag" rel="nofollow noopener" target="_blank">#Wayland</a> <a href="https://hear-me.social/tags/X11" class="mention hashtag" rel="nofollow noopener" target="_blank">#X11</a> <a href="https://hear-me.social/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> <a href="https://hear-me.social/tags/TechInnovation" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechInnovation</a> <a href="https://hear-me.social/tags/TheWaybackProject" class="mention hashtag" rel="nofollow noopener" target="_blank">#TheWaybackProject</a> <a href="https://hear-me.social/tags/AriadneConill" class="mention hashtag" rel="nofollow noopener" target="_blank">#AriadneConill</a> <a href="https://hear-me.social/tags/AlpineLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#AlpineLinux</a>

/dev/urandomread a blog article about <a href="https://toot.cat/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemd</a> that talked about how it ultimately makes a lot of things possible for sysadmins that were simply not possible or too hard to accomplish on other init systems, and i think this is just another classic example of the pareto principle ("80% of the users use 20% of the product's features -- BUT that 20% is not the same for all of them")to all the individuals, the fact that systemd does all those seemingly unnecessary things is annoying and they'd probably feel okay replicating one or two features it lacks using other means, but if you scale that up collectively, you'll end up with people whose systems are configured very differently, because they have different needs and requirementsso people whose job it is to actually support these set-ups (like redhat or distro maintainers) would much rather everyone use a single piece of software that does "too much" than have to solve a new mystery every single timei currently run <a href="https://toot.cat/tags/alpinelinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#alpinelinux</a>, which does not use systemd, and i'm fine with it, but this is a distro that's targeted to a specific set of users, i wouldn't advise a typical gamer or creator to install itand i think that should still remain an option, i like <code>openrc</code> and feel it does the things i specifically need well, and it's sad that some software now wants to specifically depend on systemd componentsin an ideal world, instead of developers just announcing "<code>$software</code> now requires <code>$systemd_component</code> to work", we would have a period of discussion where the devs would ask "we need this functionality to be available to our software, please come up with an API that would allow this to happen, then write software that would make it work", and instead of a hard dependency on a single component, you would have different programs that people can pick and choose, and one of them would still probably be a systemd componentbut this doesn't work in a "bazaar" model of development, where frequent releases are expected, and depending on what that functionality is needed for, you can't delay a security or accessibility improvement by a year or two!

__Miguel_Question for the <a href="https://tech.lgbt/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> peeps around here: how hard would it be for someone to get a distro running with a presentable desktop running <a href="https://tech.lgbt/tags/wayfire" class="mention hashtag" rel="nofollow noopener" target="_blank">#wayfire</a>?Raspberry Pi had a x86 version, but that was back on the Debian 11 era...It would be nice to have something like <a href="https://tech.lgbt/tags/alpinelinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#alpinelinux</a> with Wayfire on top, should make for a fairly small and lightweight option for older/simpler machines, no?

Thomas Liske<a href="https://ibh.social/tags/ifstate" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifstate</a> 1.13.7 was released: <a href="https://codeberg.org/liske/ifstate/releases/tag/1.13.7" rel="nofollow noopener" translate="no" target="_blank">https://codeberg.org/liske/ifstate/releases/tag/1.13.7</a>(already available in <a href="https://fosstodon.org/@alpinelinux" class="u-url mention" rel="nofollow noopener" target="_blank">@alpinelinux</a> edge + 3.22 + 3.21 + 3.20 + 3.19 and in <a href="https://c3d2.social/@m4rc3l" class="u-url mention" rel="nofollow noopener" target="_blank">@m4rc3l</a>'s Nix flake <a href="https://codeberg.org/m4rc3l/ifstate.nix" rel="nofollow noopener" translate="no" target="_blank">https://codeberg.org/m4rc3l/ifstate.nix</a>)This maintenance release fixes some minor netns and routing related issues.There is an open issue when using ifstate as a notify fifo script in keepalived: <a href="https://codeberg.org/liske/ifstate/issues/105" rel="nofollow noopener" translate="no" target="_blank">https://codeberg.org/liske/ifstate/issues/105</a> - when keepalived is reloaded any changes on vrrp constraint settings in ifstate may not apply.<a href="https://ibh.social/tags/linuxnetworking" class="mention hashtag" rel="nofollow noopener" target="_blank">#linuxnetworking</a> <a href="https://ibh.social/tags/keepalived" class="mention hashtag" rel="nofollow noopener" target="_blank">#keepalived</a> <a href="https://ibh.social/tags/AlpineLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#AlpineLinux</a>

bram dingelstad :nb_flag:yay, <a href="https://gamedev.lgbt/tags/Gnome" class="mention hashtag" rel="nofollow noopener" target="_blank">#Gnome</a> works again on <a href="https://gamedev.lgbt/tags/AsahiLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#AsahiLinux</a> / <a href="https://gamedev.lgbt/tags/AlpineLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#AlpineLinux</a> ✨ looks like the software supply chain just needed a few weeks to recover :)

samAlright I've got myself a 1GB RAM VPS for $12 for the year (a 4x increase over the Pi 😆). It's in London and everything for super low latency! I managed to get <a href="https://cablespaghetti.dev/fedi?t=alpinelinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#alpinelinux</a> installed through some hackery and migrate my blog and <a href="https://cablespaghetti.dev/fedi?t=snac" class="mention hashtag" rel="nofollow noopener" target="_blank">#snac</a> instance to it. One slightly weird thing I had is that inbound <a href="https://cablespaghetti.dev/fedi?t=ipv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#ipv6</a> traffic on both SSH and HTTPS was returning a "connection reset by peer" for a while. It seems to be working now, but if some IPv6 folks can check <a href="https://cablespaghetti.dev" rel="nofollow noopener" target="_blank">https://cablespaghetti.dev</a> loads properly over v6 for them now, it would put my mind at rest.

Wesley MooreChimera Linux has been using apk 3 for a long time. That's helped expose a few bugs, so hopefully the Alpine switch is smooth.<a href="https://fosstodon.org/@ncopa/114778452278033501" rel="nofollow noopener" translate="no" target="_blank">https://fosstodon.org/@ncopa/114778452278033501</a> <a href="https://mastodon.decentralised.social/tags/AlpineLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#AlpineLinux</a> <a href="https://mastodon.decentralised.social/tags/ChimeraLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#ChimeraLinux</a>

Natanael Copaapk-tools 3 was merged to <a href="https://fosstodon.org/tags/AlpineLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#AlpineLinux</a> edge. Hold on to your hats!Some of the new things are listed here: <a href="https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/82593#note_520288" rel="nofollow noopener" translate="no" target="_blank">https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/82593#note_520288</a>

Thomas Liske<a href="https://chaos.social/@dividuum" class="u-url mention" rel="nofollow noopener" target="_blank">@dividuum</a> Thank you for pointing me to this pull request! <a href="https://ibh.social/tags/AlpineLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#AlpineLinux</a> is sill on kernel version 6.12.31 and so the fix is missing. 😅

Thomas LiskeI'm trying to get a hyperpixel4 display working on RPi CM5 with <a href="https://ibh.social/tags/AlpineLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#AlpineLinux</a> 3.22 (or <a href="https://ibh.social/tags/pmos" class="mention hashtag" rel="nofollow noopener" target="_blank">#pmos</a>). While the console works on RPi OS it fails on Alpine - using identical config.txt tweaks. 🤔 drm_rp1_dpi and rp1_pio fails to load on Alpine. From loading with insmod it seems that rp1-pio fails due to unknown symbols.The symbols are provided by rp1.ko - but that cannot be loaded due to "module is already loaded" (which it is not ⁉️).Now I'm stucked an weird. Any ideas?<a href="https://ibh.social/tags/AskFedi" class="mention hashtag" rel="nofollow noopener" target="_blank">#AskFedi</a> <a href="https://ibh.social/tags/RaspberryPi" class="mention hashtag" rel="nofollow noopener" target="_blank">#RaspberryPi</a>

Thomas Adam<a href="https://bsd.network/tags/wayland" class="mention hashtag" rel="nofollow noopener" target="_blank">#wayland</a> <a href="https://bsd.network/tags/x11" class="mention hashtag" rel="nofollow noopener" target="_blank">#x11</a> <a href="https://bsd.network/tags/wm" class="mention hashtag" rel="nofollow noopener" target="_blank">#wm</a>Via: <a href="https://lobste.rs/s/qd78bl/wayback_experimental_x11_compatibility" rel="nofollow noopener" target="_blank">https://lobste.rs/s/qd78bl/wayback_experimental_x11_compatibility</a>It looks like <a href="https://bsd.network/tags/alpine" class="mention hashtag" rel="nofollow noopener" target="_blank">#alpine</a> linux are developing a wayland compositor to run a rootless <a href="https://bsd.network/tags/xwayland" class="mention hashtag" rel="nofollow noopener" target="_blank">#xwayland</a> instance as means of dropping X11/Xorg as packages from their repos.This is a crying shame for me, as I happen to use <a href="https://bsd.network/tags/alpinelinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#alpinelinux</a> on my Thinkpad.Why they just don't use cage though, is curious to me: <a href="https://github.com/cage-kiosk/cage" rel="nofollow noopener" target="_blank">https://github.com/cage-kiosk/cage</a>But anyway, that's their choice. Good luck to them.But one comment which came out of the lobsters post was this:<a href="https://sourceforge.net/projects/twelveto11/" rel="nofollow noopener" target="_blank">https://sourceforge.net/projects/twelveto11/</a>Which looks to be the promise of a wayland -> bridge, providing there's any xorg packages left in repos by then. But at least it would allow you to run waylaid-only applications on any X11 WM you wanted.I've forked the above project here:<a href="https://github.com/ThomasAdam/waylandx" rel="nofollow noopener" target="_blank">https://github.com/ThomasAdam/waylandx</a>Primarily so that I didn't have to use sourceforge, or SVN.I'm not sure why Imake was ever used, and awk for script generation -- that's just some of the minor things which I might change, along with the portals being upgraded.It'll be about an interesting project, and I'm just pleased someone started this, without the need for others (like myself) to have to do it from scratch.

Peter BuiI couldn't figure out how to add my <a href="https://social.ndlug.org/tags/matrix" class="mention hashtag" rel="nofollow noopener" target="_blank">#matrix</a> account to the Chats app, so that's why I fell back to using <a href="https://social.ndlug.org/tags/irc" class="mention hashtag" rel="nofollow noopener" target="_blank">#irc</a> That said, I'm surprised the <a href="https://social.ndlug.org/tags/gnome" class="mention hashtag" rel="nofollow noopener" target="_blank">#gnome</a> weather app worked... because it doesn't on normal <a href="https://social.ndlug.org/tags/alpinelinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#alpinelinux</a> o_O.I'll try to add my calendar and contacts later and see if I can make an actual phone call... crazy stuff :}

Peter BuiUpdating from my <a href="https://social.ndlug.org/tags/alpinelinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#alpinelinux</a> laptop... because typing on the <a href="https://social.ndlug.org/tags/postmarketos" class="mention hashtag" rel="nofollow noopener" target="_blank">#postmarketos</a> <a href="https://social.ndlug.org/tags/gnome" class="mention hashtag" rel="nofollow noopener" target="_blank">#gnome</a> shell is really challenging/unforgiving both in terms of latency and accuracy.I was not a fan of <a href="https://social.ndlug.org/tags/firefox" class="mention hashtag" rel="nofollow noopener" target="_blank">#firefox</a>, especially with the bottom address bar, so I used console to install <a href="https://social.ndlug.org/tags/epiphany" class="mention hashtag" rel="nofollow noopener" target="_blank">#epiphany</a> via:$ doas apk add epiphanyNot only does epiphany look better on the phone, but it also allows me to install web apps, which I did for <a href="https://social.ndlug.org/tags/thelounge" class="mention hashtag" rel="nofollow noopener" target="_blank">#thelounge</a>, a web-based <a href="https://social.ndlug.org/tags/irc" class="mention hashtag" rel="nofollow noopener" target="_blank">#irc</a> client.

zardoz.elI am trying to package a fetcher from a friend of mine, and I am erroring out with the following:The second image is the current APKBUILD. Note that it built without errors when I accidentally put the manpage in /usr/share/man1 and not /usr/share/man/man1, but now its failing. Now that its pointing to the correct location, its now erroring out with doc() failing...The APKBUILD is at <a href="https://0x0.st/8l7c.txt" rel="nofollow noopener" translate="no" target="_blank">https://0x0.st/8l7c.txt</a> for those looking to test on their machines.<a href="https://mastodon.online/tags/alpine" class="mention hashtag" rel="nofollow noopener" target="_blank">#alpine</a> <a href="https://mastodon.online/tags/alpinelinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#alpinelinux</a> <a href="https://mastodon.online/tags/packaging" class="mention hashtag" rel="nofollow noopener" target="_blank">#packaging</a>

Recent searches

Search options

Administered by:

Server stats:

#alpinelinux