#tinkerbell — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #tinkerbell, aggregated by home.social.
-
Margaret Kerry, the actress, dancer, voice artist and ASIFA board member who inspired and brought to life Tinker Bell, has died at 97.
#MargaretKerry #Disney #PeterPan #TinkerBell
https://www.animationmagazine.net/2026/06/margaret-kerry-original-performer-of-disneys-tinker-bell-dies-age-97/ -
𝗗𝗶𝘀𝗻𝗲𝘆-𝗺𝗼𝗱𝗲𝗹 𝗮𝗰𝗵𝘁𝗲𝗿 𝗶𝗻𝘀𝗽𝗶𝗿𝗮𝘁𝗶𝗲 𝘃𝗼𝗼𝗿 𝗧𝗶𝗻𝗸𝗲𝗿 𝗕𝗲𝗹𝗹 𝗼𝘃𝗲𝗿𝗹𝗲𝗱𝗲𝗻
Margaret Kerry, de vrouw die model stond voor het Disney-personage Tinker Bell, is op 97-jarige leeftijd overleden. Ze leed aan longkanker, maakte haar familie op Facebook bekend. Zo'n drie weken geleden stierf Kerry's echtgenoot en WOII-veteraan Robert Boeke op 100-jarige leeftijd.
-
Margaret Kerry Dies: Model For Disney’s Animated Tinker Bell Was 97
#News #Obituaries #MargaretKerry #Obituary #PeterPan #TinkerBellhttps://deadline.com/2026/06/margaret-kerry-dead-tinker-bell-1236954680/
-
𝗗𝗶𝘀𝗻𝗲𝘆 𝘄𝗲𝗿𝗸𝘁 𝗮𝗮𝗻 𝗻𝗶𝗲𝘂𝘄𝗲 𝗹𝗶𝘃𝗲-𝗮𝗰𝘁𝗶𝗼𝗻𝘀𝗲𝗿𝗶𝗲 𝘃𝗮𝗻 𝗧𝗶𝗻𝗸𝗲𝗿 𝗕𝗲𝗹𝗹
Disney+ werkt aan een live-actionserie gebaseerd op het elfje Tinker Bell uit Peter Pan. Amerikaanse vakmedia melden dat de serie Tink in ontwikkeling is.
-
With most of the vacation chores out of the way, I can finally continue with the Tinkerbell Pi project. Sadly, I can only do it today, as I will be going on a family visit tomorrow, without my Pis.
The goal for today is to at least get a basic initramfs going that can mount the real HookOS initramfs and pivot into it.
-
New blog post: https://blog.mei-home.net/posts/tinkerbell-5-hookos-direct-boot/
I'm trying to directly boot Tinkerbell's HookOS without using EFI/iPXE. I'm failing to, but I have a plan.
This post is mostly a bit of detective work on why HookOS' initramfs is not booting properly. The answer is: The Raspberry Pi's firmware.
-
Hhhhm, problem discovered - I think. The initramfs unpacked on my local machine is 790 MB. But the entire / on the Pi, booted into said initramfs, is 404 MB. And that includes a weird 91 MB initrd.image. Something definitely is wrong here, but for the life of me I've got no idea what it might be.
-
Whoa, that was a quick piece of success! I've moved Getty to the "init" part of the LinuxKit template for HookOS, and I've now got a shell on the Pi through the USB-to-Serial adapter. 🎉
-
Time to don a sturdy helmet and bash my head against the "booting Tinkerbell's HookOS on a Pi 4 without UEFI" wall some more.
Plan is to see whether I can at least get Getty to start somehow so I can look around a bit more. Barring that, I will set up an arm64 VM and hopefully modify the LinuxKit image enough to get it to provide some more debug output.
-
New blog post: https://blog.mei-home.net/posts/tinkerbell-4-provisioning-pi4/
I'm provisioning a Pi 4 with a SATA SSD via Tinkerbell. Lots of DHCP.
It's below 20 minutes. Because with this heat, nobody will have the concentration for my normal tomes. For those who have given up reading for today, there are also pictures.
-
And there we are. Raspberry Pi 4 with an attached USB disk, provisioned without manual intervention with Tinkerbell to an Ubuntu Server Pi image, including initial user config via cloud-init. 🎉
The next goal is to finish the blog post about this. And then I have to see how to simplify it. Because there's way too many DHCP requests and PXE boots involved in getting to this stage.
-
Early Friday evening success! My Pi now boots Tinkerbell's HookOS in-memory OS for further provisioning.
-
And finally, the provisioning netboot/normal netboot issue should be fixable with a few changes in Tinkerbell. And I always wanted to learn Go. Plus I've got a slight hankering for a bit of programming.
So I haven't given up yet. But I'm also thinking that I perhaps should stop buying new Pis and SBCs in general. Their specialness is starting to go on my nerves.
/fin
-
But I also see a couple of interesting possibilities. First of all, an OS, including the in-memory Linux used for provisioning by Tinkerbell, doesn't *need* UEFI. It's just a kernel and an initrd, which the Pi 4 and 5 already know how to boot. So using that boot approach instead of the UEFI/iPXE process for Pis might be the ticket to not only simplify things, but also get the Pi5 on board.
But this would need some real work, as I would need full TFTP in Tinkerbell.4/x
-
But Tinkerbell itself doesn't make that info available to the DHCP component. Plus, for the Pis, I would have to use Dnsmasq, for the TFTP server. Because that's the only thing the Pis speak, and Tinkerbell's TFTP implementation is very rudimentary.
An additional complication is the Pi 4's UEFI/iPXE boot process. It ain't very pretty already, and as I said, I'm not even done yet.
3/x
-
Then there's the second problem: Storageless, netbooting hosts. For Tinkerbell provisioning, my hosts do a network boot. But at the same time, those same hosts would also do a network boot for their normal boot process. And here's the rub: There's really non-brittle way to distinguish the two. The only indicator for whether this is a normal netboot or a provisioning netboot would come from whether Tinkerbell has a pending workflow for the host.
2/x
-
Hm, I'm reconsidering the entire Tinkerbell project. There are two big problems. The more severe one I just became aware of: The Raspberry Pi 5 does not have UEFI support, and the project working on that folded after the Pi people broke their UEFI firmware. That also means: No iPXE. So no Tinkerbell. And I've already got four Raspberry Pi 5 in my Homelab, so I want to be able to use Tinkerbell on them.
1/x
-
Current status of trying to get a Pi 4 provisioned with Tinkerbell: I've now got more DHCP servers than actual hosts on this VLAN.
-
New blog post: https://blog.mei-home.net/posts/tinkerbell-3-install-and-first-provisioning/
In this one, I describe how I deployed Tinkerbell and install a VM with it, including cloud-init.
-
I'm currently doing some FOSS work on Tinkerbell's documentation, and it's already paying off for me. While spelunking through the code to check whether a few custom template functions still exist, I found out that, in contrast to what the docs say, the values from the Hardware spec can actually be used in the Template definitions. 🎉
