home.social

#booting — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #booting, aggregated by home.social.

fetched live
  1. 🤦‍♂️ Ah, yes, because what everyone really wants is an excruciating deep dive into #UEFI HTTP(S) #booting with QEMU/OVMF. How thrilling! 😴 If only booting systems over the internet could save us from the #boredom of reading this 📚.
    blog.yadutaf.fr/2026/06/12/int #HTTP #QEMU #OVMF #TechHumor #HackerNews #ngated

  2. 🤦‍♂️ Ah, yes, because what everyone really wants is an excruciating deep dive into #UEFI HTTP(S) #booting with QEMU/OVMF. How thrilling! 😴 If only booting systems over the internet could save us from the #boredom of reading this 📚.
    blog.yadutaf.fr/2026/06/12/int #HTTP #QEMU #OVMF #TechHumor #HackerNews #ngated

  3. AmigaSplash 1.0

    AmigaSplash is indended to show splash screen during boot process from HDD. For now it supports only OCS/ECS graphics and no HAM modes. Sound can be output via a WAV file (stereo, mono) and images can be displayed via an IFF file.

    amiga-news.de/en/news/AN-2026-

  4. AmigaSplash 1.0

    AmigaSplash is indended to show splash screen during boot process from HDD. For now it supports only OCS/ECS graphics and no HAM modes. Sound can be output via a WAV file (stereo, mono) and images can be displayed via an IFF file.

    amiga-news.de/en/news/AN-2026-

    #Amiga #booting #display

  5. Using dmesg, you can see it keeps getting reported even though there’s nothing seriously wrong. Luckily, you can suppress it with a kernel boot option, i.e.

    pci=noaer

    and that seems to have done the trick. I then recalled I had this issue way back when this machine was new but I forgot to add the parameter to the grub file after I had to do a complete system reinstall.

    #Linux #Fedora #Kernel #Booting

  6. Using dmesg, you can see it keeps getting reported even though there’s nothing seriously wrong. Luckily, you can suppress it with a kernel boot option, i.e.

    pci=noaer

    and that seems to have done the trick. I then recalled I had this issue way back when this machine was new but I forgot to add the parameter to the grub file after I had to do a complete system reinstall.

    #Linux #Fedora #Kernel #Booting

  7. I was #rebooting my computer and found an error that popped up, part of which said:
    Fedora PCIe Bus Error: severity=Correctable

    Anytime you get a bus error could be a sign that your hardware may be damaged. But it also said
    severity=Correctable
    which indicates that it’s not irreversible. A bit of digging online I found that it can indicate that the kernel is reporting errors and Advanced Error Reporting and is not of real concern but it can clutter up log files.

    #Linux #Fedora #Kernel #Booting

  8. I was #rebooting my computer and found an error that popped up, part of which said:
    Fedora PCIe Bus Error: severity=Correctable

    Anytime you get a bus error could be a sign that your hardware may be damaged. But it also said
    severity=Correctable
    which indicates that it’s not irreversible. A bit of digging online I found that it can indicate that the kernel is reporting errors and Advanced Error Reporting and is not of real concern but it can clutter up log files.

    #Linux #Fedora #Kernel #Booting

  9. Der Bootprozess von Windows 95 & 98 erklärt

    Im Grunde ist der Bootprozess von Windows 9x immer noch ähnlich zu dem, was Windows 10 & 11 veranstalten (UEFI-Spezialitäten ausgenommen).

    Der Startprozess von Windows 9x Systemen lässt sich in 6 Phasen einteilen:

    1. Phase der Stromversorgung
    2. BIOS-Phase
    3. Betriebssystem unabhängige Boot-Phase
    4. Betriebssystem Real-Modus-Phase
    5.Windows-Phase
    6. Windows Login

    creopard.de/der-bootprozess-mi

    #windows95 #windows98 #booting #bootprocess

  10. @alexia

    Easy to do if you do not control the bootloader and do not have root.

    #Booting #Coding #Root

  11. @alexia

    Easy to do if you do not control the bootloader and do not have root.

    #Booting #Coding #Root

  12. 🚀 Behold! The epic saga of building a "Hypervisor" in just 1,000 lines! 🤯 Marvel at the audacious claim of #booting #Linux with lines to spare! 😂 Spoiler alert: the book is still a "work in progress," but who needs completion when you have #ambition and optimism? 🥳
    1000hv.seiya.me/en #Hypervisor #WorkInProgress #TechSaga #HackerNews #ngated

  13. 🚀 Behold! The epic saga of building a "Hypervisor" in just 1,000 lines! 🤯 Marvel at the audacious claim of #booting #Linux with lines to spare! 😂 Spoiler alert: the book is still a "work in progress," but who needs completion when you have #ambition and optimism? 🥳
    1000hv.seiya.me/en #Hypervisor #WorkInProgress #TechSaga #HackerNews #ngated

  14. 🐌 "Nitro: Finally, an #init #system so #tiny it's practically microscopic! Clearly, what the world needed was another way to overcomplicate the already simple task of #booting a machine. 🤦‍♂️ Good luck configuring it with your directory of scripts—because nothing says 'user-friendly' like endless scripting! 🧩"
    git.vuxu.org/nitro/about/ #Nitro #scripts #tech #overcomplication #HackerNews #ngated

  15. 🐌 "Nitro: Finally, an #init #system so #tiny it's practically microscopic! Clearly, what the world needed was another way to overcomplicate the already simple task of #booting a machine. 🤦‍♂️ Good luck configuring it with your directory of scripts—because nothing says 'user-friendly' like endless scripting! 🧩"
    git.vuxu.org/nitro/about/ #Nitro #scripts #tech #overcomplication #HackerNews #ngated

  16. 🚀✨ Behold, the riveting saga of #booting #BeOS on a #Hitachi FLORA Prius—a task so thrilling it demands a 1999 user manual and a sprinkle of Japanese documentation. Because nothing screams cutting-edge #technology like juggling #floppy #disks and boot managers in the era of #Y2K panic. 🤖💾
    testou.free.fr/www.beatjapan.o #Prius #HackerNews #ngated

  17. 🚀✨ Behold, the riveting saga of #booting #BeOS on a #Hitachi FLORA Prius—a task so thrilling it demands a 1999 user manual and a sprinkle of Japanese documentation. Because nothing screams cutting-edge #technology like juggling #floppy #disks and boot managers in the era of #Y2K panic. 🤖💾
    testou.free.fr/www.beatjapan.o #Prius #HackerNews #ngated

  18. #Linux must be installed on a clean computer or a virtual machine in 2025.

    Dual #booting from internal or external drive, and UEFI boot loading fuck with disabling fast boot and safe boot makes the whole traversal process rotten to the core...

    Use Linux as default. #imho

  19. #Linux must be installed on a clean computer or a virtual machine in 2025.

    Dual #booting from internal or external drive, and UEFI boot loading fuck with disabling fast boot and safe boot makes the whole traversal process rotten to the core...

    Use Linux as default. #imho

  20. I could also mount the encrypted partitions on the #HardDrive and to recreate the symbolic link which I’d deleted. Luckily this allowed my original system to start #Booting again. However, something was still wrong with sudo but looking it up, there was ample help online about what was wrong: the #program has to be #setuid 0 and so once I was able to do that I recovered the system. Phew.

    #GNU #Linux #ShaggyDogStory

  21. I could also mount the encrypted partitions on the #HardDrive and to recreate the symbolic link which I’d deleted. Luckily this allowed my original system to start #Booting again. However, something was still wrong with sudo but looking it up, there was ample help online about what was wrong: the #program has to be #setuid 0 and so once I was able to do that I recovered the system. Phew.

    #GNU #Linux #ShaggyDogStory

  22. Ventoy
    Ventoy is an open source tool to create bootable USB drive for ISO/WIM/IMG/VHD(x)/EFI files. With ventoy, you don't need to format the disk over and over, you just need to copy the ISO/WIM/IMG/VHD(x)/EFI files to the USB drive and boot them directly. You can copy many files at a time and ventoy will give you a boot menu to select them (screenshot). You can also browse ISO/WIM/IMG/VHD(x)/EFI fi
    monodes.com/predaelli/2025/01/
    #Software #SoftwareLibero #Booting #USB

  23. Ventoy
    Ventoy is an open source tool to create bootable USB drive for ISO/WIM/IMG/VHD(x)/EFI files. With ventoy, you don't need to format the disk over and over, you just need to copy the ISO/WIM/IMG/VHD(x)/EFI files to the USB drive and boot them directly. You can copy many files at a time and ventoy will give you a boot menu to select them (screenshot). You can also browse ISO/WIM/IMG/VHD(x)/EFI fi
    monodes.com/predaelli/2025/01/
    #Software #SoftwareLibero #Booting #USB

  24. Because I need to dual boot #Windows11, I decided to bring #rEFInd to the game, and it’s awesome.👏

    With some minor tweaking, you can have any OS (even #Hackintosh) booting through their own EFI partition. And colors! And no more pressing FX to select the boot loader! USB compatible!

    It would be cool now to have a cross platform utility to pick which OS you want to boot tinto next.

    #Linux #FOSS #OSS #OpenSource #Fedora #EFI #UEFI #Windows #DualBoot #Booting #Bootloader #Ubuntu

  25. Because I need to dual boot #Windows11, I decided to bring #rEFInd to the game, and it’s awesome.👏

    With some minor tweaking, you can have any OS (even #Hackintosh) booting through their own EFI partition. And colors! And no more pressing FX to select the boot loader! USB compatible!

    It would be cool now to have a cross platform utility to pick which OS you want to boot tinto next.

    #Linux #FOSS #OSS #OpenSource #Fedora #EFI #UEFI #Windows #DualBoot #Booting #Bootloader #Ubuntu

  26. Hey #fedora #linux folks!

    I am running #btrfs of course and I am doing snapshots hourly and also prior to any dnf #updates. (Ask me why).

    So I have root #snaps like

    ID 495 gen 15736 top level 257 path mnt/backup/root/snapshot-2024-06-19_1400

    What is the correct way of #booting from a snapshot? Tried sysguides.com/install-fedora-w but boy, that went up in flames.

    Also, how to revert to a snapshot as "root" snapshot?

    Thanks!

  27. Hey #fedora #linux folks!

    I am running #btrfs of course and I am doing snapshots hourly and also prior to any dnf #updates. (Ask me why).

    So I have root #snaps like

    ID 495 gen 15736 top level 257 path mnt/backup/root/snapshot-2024-06-19_1400

    What is the correct way of #booting from a snapshot? Tried sysguides.com/install-fedora-w but boy, that went up in flames.

    Also, how to revert to a snapshot as "root" snapshot?

    Thanks!

  28. The recording of the 2024-06-06 bhyve Production User Call is up:

    youtu.be/jCP9L8mBZ9c

    We discussed aarch64 and amd64 boot stages in great detail (and would love to see more highly-verbose system boot documentation), read-only VM boot, PXE VM booting, continued Broadcom NIC issues with and without SR-IOV, a '-f (fib number)' option for ping, FreeBSD build options, 9front as a VM, VM termination options, and more!

    "Don't forget to slam those Like and Subscribe buttons."

    #FreeBSD #illumos #booting #tooting

  29. The recording of the 2024-06-06 bhyve Production User Call is up:

    youtu.be/jCP9L8mBZ9c

    We discussed aarch64 and amd64 boot stages in great detail (and would love to see more highly-verbose system boot documentation), read-only VM boot, PXE VM booting, continued Broadcom NIC issues with and without SR-IOV, a '-f (fib number)' option for ping, FreeBSD build options, 9front as a VM, VM termination options, and more!

    "Don't forget to slam those Like and Subscribe buttons."

    #FreeBSD #illumos #booting #tooting

  30. Reading Time: 2 minutes

    This morning I made PhotoPrism self-booting. I am not certain that this is the write term so I will specify what I mean. PhotoPrism, when run via docker boots, when we tell it to boot, like any other app on our laptop. This morning, after a little time spent with AI I found the solution.

    I used ChatGPT for this help but this is to give you an idea of how to enable docker containers to boot automatically rather than manually. It’s by a little trial and error that I suceeded in what I wanted to do.

    Boiled down Chat GPT gave this overview

    To start a service: sudo systemctl start servicename.service
    To stop a service: sudo systemctl stop servicename.service
    To restart a service: sudo systemctl restart servicename.service
    To enable a service to start on boot: sudo systemctl enable servicename.service
    To disable a service from starting on boot: sudo systemctl disable servicename service

    In concrete terms you need to “sudo nano /etc/systemd/system/photoprism.service” and add

    [Unit]Description=PhotoPrism Docker Compose Service
    Requires=docker.service
    After=docker.service

    [Service]Type=oneshot
    RemainAfterExit=yes
    ExecStart=/usr/local/bin/docker-compose -f /path/to/your/docker-compose.yml up -d
    ExecStop=/usr/local/bin/docker-compose -f /path/to/your/docker-compose.yml down

    [Install]WantedBy=default.target

    In my case it was /usr/bin rather than local bin. That’s a little thing to look out for. To double check use “which docker-compose” and you will see what to use for the execstart address.

    If you are using an external volume double check that the mount point is static. I rebooted twice and got three mount points as well as an “original picture folder empty” message due to the photo drive being mounted in the wrong place. To fix this I used.

    sudo blkid

    to locate the uuid of the hard drive before personalising this line:

    UUID= /path/to/mountpoint ext4 defaults 0 2
    I left the defaults behaviouts. The 0 is for fsck to check the file system and 2 is the backup priority number.

    This is added via:

    sudo nano /etc/fstab

    Once you have ensured that the drive mount point will remain the same, boot after boot you can run the next lines.

    Reload Systemd

    sudo systemctl daemon-reload

    Enable PhotoPrism to launch at boot

    sudo systemctl enable photoprism.service

    To start the service

    sudo systemctl start photoprism.service

    And finally you can run

    sudo systemctl status photoprism.service
    to check service status.

    And Finally

    When I set up a server for photoprism or other services I want it to boot automatically as soon as the computer is booted. I don’t want to have to start services manually. With this workflow I was able to setup PhotoPrism to boot automatically, as well as to make sure that the photo drive would mount to the right place each time I booted the system.

    https://www.main-vision.com/richard/blog/photoprism-self-boot/

    #booting #learning #photoprism #systemd #volumes #walkThru

  31. Reading Time: 2 minutes

    This morning I made PhotoPrism self-booting. I am not certain that this is the write term so I will specify what I mean. PhotoPrism, when run via docker boots, when we tell it to boot, like any other app on our laptop. This morning, after a little time spent with AI I found the solution.

    I used ChatGPT for this help but this is to give you an idea of how to enable docker containers to boot automatically rather than manually. It’s by a little trial and error that I suceeded in what I wanted to do.

    Boiled down Chat GPT gave this overview

    To start a service: sudo systemctl start servicename.service
    To stop a service: sudo systemctl stop servicename.service
    To restart a service: sudo systemctl restart servicename.service
    To enable a service to start on boot: sudo systemctl enable servicename.service
    To disable a service from starting on boot: sudo systemctl disable servicename service

    In concrete terms you need to “sudo nano /etc/systemd/system/photoprism.service” and add

    [Unit]Description=PhotoPrism Docker Compose Service
    Requires=docker.service
    After=docker.service

    [Service]Type=oneshot
    RemainAfterExit=yes
    ExecStart=/usr/local/bin/docker-compose -f /path/to/your/docker-compose.yml up -d
    ExecStop=/usr/local/bin/docker-compose -f /path/to/your/docker-compose.yml down

    [Install]WantedBy=default.target

    In my case it was /usr/bin rather than local bin. That’s a little thing to look out for. To double check use “which docker-compose” and you will see what to use for the execstart address.

    If you are using an external volume double check that the mount point is static. I rebooted twice and got three mount points as well as an “original picture folder empty” message due to the photo drive being mounted in the wrong place. To fix this I used.

    sudo blkid

    to locate the uuid of the hard drive before personalising this line:

    UUID= /path/to/mountpoint ext4 defaults 0 2
    I left the defaults behaviouts. The 0 is for fsck to check the file system and 2 is the backup priority number.

    This is added via:

    sudo nano /etc/fstab

    Once you have ensured that the drive mount point will remain the same, boot after boot you can run the next lines.

    Reload Systemd

    sudo systemctl daemon-reload

    Enable PhotoPrism to launch at boot

    sudo systemctl enable photoprism.service

    To start the service

    sudo systemctl start photoprism.service

    And finally you can run

    sudo systemctl status photoprism.service
    to check service status.

    And Finally

    When I set up a server for photoprism or other services I want it to boot automatically as soon as the computer is booted. I don’t want to have to start services manually. With this workflow I was able to setup PhotoPrism to boot automatically, as well as to make sure that the photo drive would mount to the right place each time I booted the system.

    https://www.main-vision.com/richard/blog/photoprism-self-boot/

    #booting #learning #photoprism #systemd #volumes #walkThru

  32. @Windows Come On Windows! I am not studying in school anymore 😉. You need to be #booting faster now.

  33. Raspberry Pi Booting QMLviewer on Mer -  
    Here is a Video of Raspberry Pi booting QMLviewer on Mer in 24 seconds.
     
    The vi... - readwrite.com/raspberry-pi-boo #raspberrypi #developer #qmlviewer #booting #mer