fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

8.8K
active users

#bullseye

1 post1 participant0 posts today
Replied in thread

🖥️ Ein uralter iMac Core Duo dient via #Yunohost (#Debian #Bookworm) als #MastodonServer , beherbergt ein #WordPress und eine #NextCloud , administriert mit #Webmin – leider fehlt bisher eine Steuerung des Bildschirms, so dass ca. 10 Zeilen Linux-Start-Meldungen immer sichtbar sind, wodurch sich diese vermutlich einbrennen werden.
Per DualBoot läuft auch ein Debian #BullsEye, mit dem zur Not das primäre System repariert werden kann.

@heise_ct

Argh -- I bought a vintage #Marchisio thread-on freewheel in excellent condition for my #Bullseye #MTB hubs on eBay. It came today in the mail, and to my relief it looked ~exactly~ like the old one I want to replace.

But when I tried to screw the freewheel onto the hub, it didn't fit. 🤔

Turns out there were different standards back in the day, two of which are ISO (34.92mm) and “Italian” (35mm). 😭

sheldonbrown.com/freewheels.ht

sheldonbrown.comTraditional Thread-on FreewheelsInformation on how to rebuild freewheels, which were very common on derailer-equipped bicycles and which offer a great variety of options for sprocket sizes.

An incredible sports Thursday (SF Giants dramatic opening day win, Texas Tech win in OT at March Madness in San Francisco) culminated in this incredible finish in Chicago. Josh Giddey does to the Lakers what LeBron and LA did to the Pacers earlier this week—only this was more dramatic and unreal. #bulls #bullseye #joshgiddey #nba

A little group I am part of has its own server. It hosts our website and a nextcloud instance. It is on a Hetzner machine. OK so far so good. The problem is that the person who set it up has left and I am the only one foolish enough to try to maintain it. The problem though is that I don't know how.

It is still running Debian Buster. I tried to follow a guide to at least upgrade it to bullseye, but something breaks. I think that it is something to do with its network configuration. This is mostly because I saw a comment that said if you are using a KVM Host with bridged networking, then you need to add bridge_hw eth0 (or whatever your network interface is called) to your network config otherwise the network won't start and you won't be able to reach the server. Weirdly I can SSH in after the upgrade, but the console shows lots of networky error messages and the website and nextcloud become unreachable.

Fine, I doubt any one will be able to help from that error description, but maybe you can point me at a foolproof guide to upgrading. I can't find one in the Hetzner docs.

#HelpNeeded, #PleaseHelp, #Debian, #Hetzner, #Buster, #Bullseye, #HelpMyServerIsARadioactiveDisasterZone

I shouldn't rush that much to upgrade my Pi-Hole 🥧🕳️ to the never v6 version after 1-2 day after it released in February 18th, just to end up brooking my existing setup. I had to start over since I was dumb enough to not make a backup of my existing working setup, I don't know what I expected. While the update was nearly fished the gravity updated failed and I had to stop the it with CTRL-C after waiting for hours to complete, it was stuck for some reason. After rebooting my pi the pihole service still started up but slowed down my pi and got completely unresponsive. I had run Bullseye on my Pi Zero W v1.1 board and either way I still wanted to upgrade to Bookworm. I had an older backup of my pi's sdcard with Bullseye and pihole v5 on it that I could flash back to use while I finish setting up the new image with Bookworm and pihole v6. I know I could avoid complicating things if I had another sdcard that I could use for the new image, not having to copy back and fourth different images while making lots of backups frequently of the new image after working on it for a couple of hours.
The only thing that made less painful doing it this was using pishrink that spared me hours whenever I needed to copy back the new image making it way faster then copying back 32 GB that takes a long time. I'm can't be happier that I found this nice tool that speed up significantly copying the images and swapping between the old perfectly working one and the new one until the new one was set up fully. ☺️
It took me days regardless to finish the new image because of lack of time to sit down and work on it until it's done, only doing small steps at a time. Now everything is working fine, I'm running the latest pihole version on bookworm for just about two weeks. 😃
But probably I had to start from an fresh new install, because I tried upgrading from bullseye to bookworm and it wasn't end up well, probably there was lots changes between the two.