• 20 Posts
  • 16 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle


  • Not a bad idea… would be pretty cool and phtn.app is much more accessible than photon.xylight.dev.

    I guess a related question is what is your vision for how users would typically use Photon. Do you want to host a single/main application that many users end up using or would you rather have instances (or individuals) deploy their own applications (ie. nu.lemdro.id)? or possibly both?

    If the former, then phtn.app makes sense. Otherwise, just photon.xylight.dev is fine since it would sort of encourage others to deploy their own.

    Another thought: if you follow through on making Photon into a PWA, then phtn.app would probably fit into that branding, more so than photon.xylight.dev.













  • It’s unfortunate, but the reality is that many of the proprietary services are… free, convenient, and where the people are.

    Most projects do not have a lot of funding, so it makes sense to use low cost platforms with the least amount of friction. I think most developers are aware of the risks and trade-offs, but make a pragmatic decision to use these proprietary services b/c the benefits for them outweigh the costs.














  • Yes, I’ve run into this issue recently. The /boot/efi folder is actually its own partition, so removing packages from / will not give your more space for the efi partition. On my recentish Pop install, the /boot/efi partition is about 512MB which is just about enough space for two kernels but… not much else (they may have increased this to 1GB for new installs).

    The workaround I did was to simply delete one of the kernels in /boot/efi/EFI/Pop_OS-... (the ... is some string of letters). In this folder you should have the following:

    $ ls -l /boot/efi/EFI/Pop_OS-f2c685b9-a9c2-48f0-907b-ebe199e94a55
    total 289256
    -rwx------ 1 root root       167 Jul 12 15:24 cmdline
    -rwx------ 1 root root 134046998 Jul 12 15:24 initrd.img
    -rwx------ 1 root root 134449391 Jul 12 15:24 initrd.img-previous
    -rwx------ 1 root root  13844192 Jul 12 15:24 vmlinuz.efi
    -rwx------ 1 root root  13846496 Jul 12 15:24 vmlinuz-previous.efi
    

    As you can see, Pop stores the current kernel (vmlinuz) and ramdisk (initrd) along with the corresponding previous versions in case you need/want to revert back to the previous kernel. To free up some space, you can simply delete either the initrd.img-previous or vmlinuz-previous.efi file if you are not using the previous kernel. That should allow you to then download the firmware and update it.

    After the firmware update, if you want to restore the previous (backup) kernel, you can copy it from /boot back to the efi folder above. Otherwise, the next kernel update will replace it for you anyways.

    I hope this helps, good luck.