aka @rotopenguin@mastodon.social

  • 0 Posts
  • 279 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle












  • It’s fucking crazy how much work goes into shitting out thousands and thousands of slightly different models of android phone and tablet and chromebook. Slap together a board design based on buying two trays of some SOC. Open up the Android source, slap some NDA drivers in, build an image, burn it into a production run. Don’t bother saving your changes, these devices will never get an update. Two weeks later, change out the whole design for a different chip, repeat.







  • Is there a reason to install one(1) singular OS across multiple partitions? Is it just because that’s how our ancestors did things?

    Partitions are crude buckets that tell Operating Systems that “this lump is a filesystem that you know how to read” or “you don’t know how to read this, leave it alone”. Partitions tell UEFI that it should only use this special FAT32 chunk. A partition is not a good mechanism to set quotas, as you can see from how difficult it is to expand. A bunch of partitions that are all mounted together does little to isolate against failures.

    If you want to run an OS across two filesystems that provide different characteristics (one provides atomic snapshots, the other provides ??), that would have to live on different partitions. Would you be better served by putting it all on the more modern FS? Is the older filesystem only kept around because it straddles “what my OS knows” and “what my bootloader knows”? If it’s just for the bootloader’s sake, that’s why we have /boot.